Cloud license key binding system and implementation method thereof
The cloud license key binding system integrates mobile devices and cloud servers with encryption and whitelist management to address security and automation challenges in vehicle key systems, ensuring secure and convenient vehicle operation.
Patent Information
- Application Number
- JP2024112369
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-07-12
- Publication Date
- 2026-01-23
- Estimated Expiration
- 2044-07-12
AI Technical Summary
Existing vehicle key systems face issues of security risks, lack of automation, and reliance on network connectivity, with traditional keys being simple but insecure, wireless keys posing security threats, and smartphone apps needing robust authentication.
A cloud license key binding system that integrates a mobile device, motorized vehicle, and cloud server, utilizing communication modules, whitelist management, and asymmetric encryption to securely bind and authenticate devices, enabling keyless operation.
Provides secure, convenient, and automated vehicle access by ensuring only authorized devices can operate vehicles, reducing theft risks and enhancing security through encrypted communication and whitelist authentication.
Smart Images

Figure 2026011616000001_ABST
Abstract
Description
[Technical Field]
[0001] The present invention relates to a cloud license key binding system and its implementation method, and in particular to a system for binding electronic devices by pre-licensing them so that vehicle owners do not need to re-authenticate every time they drive a powered vehicle. [Background technology]
[0002] Before the invention of the cloud license key binding system, various technologies were used for device licensing and secure communication. These prior technologies include: 1. Traditional key lock system: Traditional motorcycles and automobiles typically use a physical key lock system to control vehicle entry and startup. Users must insert and turn a physical key into the key cylinder to unlock and start the vehicle. While such systems are simple and reliable, they lack remote control or automation capabilities and are prone to cloning and theft. 2. Wireless Key (RFID / NFC): As technology advances, many vehicles now use wireless key systems such as RFID and NFC technology. These systems allow users to carry a small wireless key that automatically unlocks and activates the vehicle when they approach it. While wireless key systems have improved convenience, they still pose security risks such as relay attacks and signal interception. 3. Control via smartphone app: Some modern vehicles allow users to control vehicle functions using a smartphone app. These apps typically connect to the vehicle via Bluetooth or Wi-Fi, allowing users to remotely unlock, start, and otherwise control the vehicle. However, these systems rely on the security of the smartphone and app, and proper authentication and encryption measures are required to prevent unauthorized access. Summary of the Invention [Problem to be solved by the invention]
[0003] Among the above-mentioned conventional technologies, each system has its own advantages and disadvantages. For example, traditional key systems are simple but lack modern features. Wireless keys and smartphone apps have improved convenience but face security challenges. Cloud authentication offers higher security but relies on network connectivity. The newly invented cloud license key binding system combines various technologies to provide a more secure, convenient, and automated solution. [Means for solving the problem]
[0004] The present invention provides a cloud license key binding system, which includes: a mobile electronic device; a motorized vehicle including a communication module for wirelessly establishing an information link with the mobile electronic device; a key database in which at least one piece of key information is stored and transmitted to the mobile electronic device via the communication module; and a whitelist management module for binding licensed mobile electronic devices and broadcasting the binding information in a whitelist manner; and a cloud server capable of receiving key information and identification information of the mobile electronic device, the cloud server including an authentication module in which at least one piece of authentication information is pre-stored and for matching the received identification information with the authentication information; and a license key generation module information-linked with the authentication module, for receiving the key information, and if the identification information is successfully authenticated, encrypting and decrypting the key information to generate a license key and transmitting the license key to the mobile electronic device. The mobile electronic device transmits the received license key to the motorized vehicle to obtain a license binding for the motorized vehicle, allowing the user to perform related operations on the motorized vehicle using the mobile electronic device.
[0005] In one embodiment, the cloud license key binding system further includes an external licensing device including an external authentication module and an external license key generation module, wherein the external licensing device can establish an information link with the mobile electronic device in a non-network connection manner, and the mobile electronic device can complete authentication and license key generation through the external authentication module and the external license key generation module.
[0006] In one embodiment, the communication module is one or a combination of a Bluetooth module, a Wi-Fi module, or an NFC module.
[0007] In one embodiment, the license key generation module performs key encryption and decryption operations using an asymmetric encryption algorithm.
[0008] The present invention also provides a method for implementing a cloud license key binding system, the method including: establishing a connection between a mobile electronic device and a motorized vehicle; receiving key information from the motorized vehicle; and generating identification information from the mobile electronic device; the mobile electronic device requests authentication and a license key from a cloud server via the Internet; the cloud server authenticates the identity information through an authentication module; if the authentication is successful, a license key generation module of the cloud server receives the key information, calculates and generates a license key, encrypts the license key, and sends it to the mobile electronic device; the mobile electronic device sends the encrypted license key to the motorized vehicle; the motorized vehicle receives and decrypts the license key and verifies the validity of the license key; after verifying the validity, binding the mobile electronic device that sent the license key to a whitelist management module and broadcasting the whitelist.
[0009] In one embodiment, an authentication module in the cloud server verifies the identity by checking against pre-stored authentication information.
[0010] In one embodiment, the license key generation module performs key encryption and decryption operations using an asymmetric encryption algorithm.
[0011] In one embodiment, the mobile electronic device transmits the license key to the motor vehicle via one of the following wireless communication methods: Bluetooth, Wi-Fi, or NFC.
[0012] In one embodiment, when the whitelist management module broadcasts a whitelist, the content of the broadcasted whitelist includes unique identification information of the licensed device, where the identification information is one or any combination of the MAC address, UUID, and IMSI of the mobile electronic device.
[0013] In one embodiment, if the mobile electronic device cannot connect to a network, an external licensing device establishes an information link with the mobile electronic device to complete the authentication of the mobile electronic device and the generation of a licensing key.
[0014] To enable a detailed understanding of the features described herein, the above brief summary of the invention, but a more particular description thereof, can be made by reference to embodiments, some of which are illustrated in the drawings. It should be noted, however, that the drawings illustrate only typical embodiments of the invention and should not be considered as limiting its scope, since the invention is susceptible to other embodiments that are equally effective. [Brief explanation of the drawings]
[0015] [Figure 1] 1 is a schematic diagram of a system configuration of the present invention. [Figure 2] 1 is an embodiment of the present invention when the mobile electronic device is unable to connect to a network. [Figure 3] 1 is a schematic diagram of the steps of carrying out the present invention. DETAILED DESCRIPTION OF THE INVENTION
[0016] The following description includes specific information related to exemplary embodiments of the present invention. The drawings and detailed description of the present invention are merely exemplary embodiments. However, the present invention is not limited to these exemplary embodiments. Other variations and embodiments of the present invention will occur to those skilled in the art. Unless otherwise stated, like or corresponding elements in the drawings may be indicated by like or corresponding reference numerals. Additionally, the drawings and illustrations of the present invention are generally not drawn to scale and do not necessarily correspond to actual relative sizes.
[0017] For purposes of consistency and ease of understanding, like features are designated by numerals in the exemplary drawings (although in some instances they are not so designated), but should not be limited narrowly to the features shown in the drawings, as features in different embodiments may differ in other respects.
[0018] Terms such as "at least one embodiment," "one embodiment," "multiple embodiments," "different embodiments," "some embodiments," "the present embodiment," and the like can indicate that the embodiments of the invention so described may include a particular feature, structure, or characteristic, but not all possible embodiments of the invention must include that particular feature, structure, or characteristic. Furthermore, repeated use of the phrases "in one embodiment" and "in this embodiment" does not necessarily refer to the same embodiment, even if they may be the same. Furthermore, when used in the context of "the present invention," phrases such as "embodiment" and "present embodiment" do not imply that all embodiments of the invention must include that particular feature, structure, or characteristic; rather, "at least some embodiments of the present invention" should be understood to include the described particular feature, structure, or characteristic. The term "coupled" is defined as connected, whether directly or indirectly through intervening elements, and is not necessarily limited to a physical connection. When the term "comprising" is used, it means "including, but not limited to," and explicitly indicates an open-ended inclusion or relationship of listed combinations, groups, series, and equivalents.
[0019] Also, for purposes of explanation and not limitation, specific details of functional entities, techniques, protocols, standards, etc. are set forth to provide an understanding of the described technology. In other instances, detailed descriptions of well-known methods, techniques, systems, architectures, etc. are omitted so as not to obscure the description with unnecessary detail.
[0020] As shown in FIG. 1, FIG. 1 is a schematic diagram of the system configuration of the present invention. The cloud license key binding system 10 of the present invention mainly includes a mobile electronic device 101, a motorized vehicle 102, a key database 1022, a whitelist management module 1023, a trigger intent detection module 1024, a distance determination module 1025, a cloud server 103, and a license key generation module 1032. The mobile electronic device 101 can generate identification information M1 and is mainly an electronic device with wireless information access capabilities, such as a mobile phone or tablet. The motorized vehicle 102 may be a vehicle with a motor engine, such as a car or motorcycle, or may be an electric vehicle model. The motorized vehicle 102 includes a communication module 1021 for wirelessly establishing an information link with the mobile electronic device 101. In one embodiment, the communication module 1021 is one or a combination of a Bluetooth module, a Wi-Fi module, or an NFC module. The key database 1022 stores at least one key information M2, which is transmitted to the mobile electronic device 101 via the communication module 1021. The key information M2 stored in the key database 1022 is primarily used for license matching with electronic devices provided by new owners of motorized vehicles 102 when the motorized vehicle 102 is newly shipped and sold. The whitelist management module 1023 is used for binding licensed mobile electronic devices 101 and broadcasts the information in the form of a whitelist. The trigger intent detection module 1024 detects the motorized vehicle 102's intention to move and triggers corresponding actions. The movement intent primarily refers to situations in which the motorized vehicle 102's body is moved by other external forces. For example, if the motorized vehicle 102 is a motorcycle, it refers to situations such as whether the body is tilted or whether the head of the body is rotating. In one embodiment, the trigger intent detection module 1024 includes a gyroscope, a collision sensor, and a vehicle tilt sensor, which detect the real-time status of the motorized vehicle's body.The distance determination module 1025 is used to determine the distance between the mobile electronic device 101 and the motorized vehicle 102. In one embodiment, the distance determination module 1025 is one of a Bluetooth low energy module, an ultra-wideband module, a radio frequency identification module, and a GPS module. The cloud server 103 can receive key information M2 and identification information M1 of the mobile electronic device 101. The cloud server 103 includes an authentication module 1031 that pre-stores at least one piece of authentication information M3 and matches the received identification information M1 with the authentication information M3. The authentication information M3 mainly includes information related to the vehicle owner, such as name, telephone number, address, and ID number, which can be used to authenticate the vehicle owner. The license key generation module 1032 is information-linked with the authentication module 1031 and is used to receive the key information M2. If the identification information M1 is successfully authenticated, the license key generation module 1032 encrypts and decrypts the key information M2 to generate a license key M4, and transmits the license key M4 to the mobile electronic device 101. In one embodiment, the license key generation module 1032 performs key encryption and decryption operations using an asymmetric encryption algorithm. The mobile electronic device 101 transmits the received license key M4 to the motorized vehicle 102 to obtain a license binding for the motorized vehicle 102, allowing the user to perform related operations on the motorized vehicle 102 using the mobile electronic device 101. The mobile electronic device 101 has already been bound to the whitelist management module 1023. Simply put, only devices registered on the whitelist can receive and decrypt broadcast messages. When the motorized vehicle 102 broadcasts in a whitelist manner, not only can the mobile electronic device 101 ensure a fast and accurate connection with the motorized vehicle 102, but also significantly reduce the risk of being searched by others and the possibility of being subject to malicious attacks. Encryption of broadcast content and whitelist authentication can prevent malicious attackers from intercepting or forging messages, improving the security of the overall system.
[0021] Another object of the present invention is to monitor the security status of the motorized vehicle 102 by combining the trigger intent detection module 1024 and the distance determination module 1025 of the motorized vehicle 102. For example, the trigger intent detection module 1024 can detect whether there is any movement, collision, etc. of the motorized vehicle 102 to determine whether the motorized vehicle 102 is in an activated state or whether there is any potential intention to move. If there is, the distance determination module 1025 can determine the distance of the licensed mobile electronic device 101. If it is within a safe range, it indicates that the vehicle owner has come to activate the motorized vehicle 102; if not, a situation may occur in which the motorized vehicle 102 is crashed or stolen, and the motorized vehicle 102 can send a warning message to the mobile electronic device 101 to warn it.
[0022] Referring to FIG. 2, FIG. 2 illustrates an embodiment of the present invention in which the mobile electronic device cannot connect to a network. In one embodiment, the cloud license key binding system 10 further includes an external licensing device 104 including an external authentication module 1041 and an external license key generation module 1042. The external licensing device 104 can establish an information link with the mobile electronic device 101 in a non-network-connected manner, and the external licensing device 104 can be a physical server installed in a store. This embodiment is mainly intended to enable the mobile electronic device 101 to complete license binding with the motorized vehicle 102 in a state in which the mobile electronic device 101 cannot connect to a network. To this end, the mobile electronic device 101 can establish a link with the external licensing device 104 in a manner such as a Bluetooth module, a Wi-Fi module, or an NFC module, so that the external authentication module 1041 and the external license key generation module 1042 can complete authentication and license key generation. The operation patterns of the external authentication module 1041 and the external license key generation module 1042 are similar to those of the authentication module 1031 and the license key generation module 1032 of the cloud server 103, and therefore will not be described again here.
[0023] Referring to Fig. 3, Fig. 3 is a schematic diagram of the steps of carrying out the present invention. Referring also to Figs. 1 and 2, the steps of carrying out the present invention are as follows. First step S1: The mobile electronic device 101 establishes a link with the motor vehicle 102, and can receive key information M2 from the motor vehicle 102 and generate identification information M1. Second step S2: The mobile electronic device 101 requests authentication and a license key from the cloud server 103 via the Internet, and the cloud server 103 authenticates the identity M1 via the authentication module 1031. In one embodiment, the authentication module 1031 verifies the identity M1 by matching it with pre-stored authentication information M3. Third step S3: If the authentication is successful, the license key generation module 1032 of the cloud server 103 receives the key information M2, calculates and generates a license key M4, encrypts the license key, and then sends it to the mobile electronic device 101. In one embodiment, the license key generation module 1032 uses an asymmetric encryption algorithm to perform the key encryption and decryption operations. Fourth step S4: The mobile electronic device 101 transmits the encrypted license key M4 to the motor vehicle 102. In one embodiment, the mobile electronic device 101 transmits the license key M4 to the motor vehicle 102 via one of the following wireless communication methods: Bluetooth, Wi-Fi, or NFC. Fifth step S5: The motor vehicle 102 receives and decrypts the license key M4, and verifies the validity of the license key M4. In one embodiment, the mobile electronic device 101 performs relevant operations on the motor vehicle 102 based on the received license key M4 (including, but not limited to, unlocking the motor vehicle and starting the engine of the motor vehicle). In one embodiment, if the mobile electronic device 101 cannot connect to a network, it establishes an information link with the mobile electronic device 101 via the external licensing device 104 to complete the authentication of the mobile electronic device 101 and the generation of the license key M4. A sixth step S6: After the validity is confirmed, the mobile electronic device 101 that sends the license key M4 is added to the whitelist management module 1023 by binding, and broadcasts the whitelist. In one embodiment, when the whitelist management module 1023 broadcasts the whitelist, the content of the broadcasted whitelist includes the unique identification information of the licensed device, which is one or any combination of the MAC address, UUID, and IMSI of the mobile electronic device 101. Seventh step S7: The motor vehicle 102 detects the motor vehicle 102's intention to move via the trigger intent detection module 1024. In one embodiment, the trigger intent detection module 1024 includes an accelerometer, a gyroscope, a collision sensor, a GPS module, an ultrasonic sensor, a wheel rotation speed sensor, and a vehicle tilt sensor, and is used to detect the motor vehicle 102's intention to move and trigger a start or stop operation. Eighth step S8: If an intention to move is detected, the motorized vehicle 102 determines the distance between the mobile electronic device 101 and the motorized vehicle 102 by the distance determination module 1025 to determine whether to send a warning signal to the mobile electronic device 101 or whether to unlock and operate the motorized vehicle 102. In one embodiment, the distance determination module 1025 determines the distance between the mobile electronic device 101 and the motorized vehicle 102 by Received Signal Strength Indicator (RSSI) or Ultra-Wideband (UWB) technology.
[0024] To sum up, the cloud license key binding system of the present invention mainly uses whitelist management, encrypted communication, trigger intent detection and distance judgment technologies to realize secure binding and operation of licensed devices, prevent unauthorized access and attacks, and improve system security, so that the cloud license key binding system of the present invention can truly achieve the goal of improving the overall keyless unlocking system.
[0025] The scope of these embodiments and patent applications does not necessarily need to achieve all of the disclosed technical advantages or technical features. Furthermore, the abstracts and titles are merely intended to facilitate searching of patent application documents and are not intended to limit the category of the present invention in any way. [Explanation of symbols]
[0026] 10: Cloud license key binding system 101: Mobile Electronic Devices 102: Powered vehicle 1021: Communication module 1022: Key database 1023: Whitelist management module 1024: Trigger Intent Detection Module 1025: Distance judgment module 103: Cloud Server 1031: Authentication module 1032: License key generation module 104: External license device 1041: External authentication module 1042: External license key generation module M1: Identification information M2: Key information M3:Authentication Information M4: License key S1: First step S2: Second step S3: The third step S4: The fourth step S5: The fifth step S6: The Sixth Step S7: The Seventh Step S8: The Eighth Step
Claims
1. a mobile electronic device; a motor vehicle including a communication module for wirelessly establishing an information link with the mobile electronic device, a key database in which at least one piece of key information is stored and transmitted to the mobile electronic device by the communication module, and a whitelist management module for binding the licensed mobile electronic device and broadcasting in a whitelist manner; a cloud server capable of receiving the key information and identification information of the mobile electronic device, the cloud server including an authentication module storing at least one piece of authentication information in advance and verifying the authentication information after receiving the identification information; and a license key generation module linked with the authentication module, receiving the key information, and, if the identification information is successfully authenticated, generating a license key from the key information by encryption and decryption, and transmitting the license key to the mobile electronic device; The mobile electronic device transmits the received license key to the motor vehicle to obtain a license binding for the motor vehicle, thereby allowing the user to perform related operations on the motor vehicle through the mobile electronic device. Cloud license key binding system.
2. The cloud license key binding system further includes an external licensing device including an external authentication module and an external license key generation module, wherein the external licensing device can establish an information link with the mobile electronic device in a non-network connection manner, and the mobile electronic device can complete authentication and license key generation through the external authentication module and the external license key generation module. The cloud license key binding system of claim 1 .
3. The communication module is one or a combination of a Bluetooth module, a Wi-Fi module, or an NFC module. The cloud license key binding system of claim 1 .
4. The license key generation module performs key encryption and decryption operations using an asymmetric encryption algorithm. The cloud license key binding system of claim 1 .
5. establishing a connection between a mobile electronic device and a motorized vehicle, receiving key information by the motorized vehicle, and enabling the mobile electronic device to generate identification information; The mobile electronic device requests authentication and a license key from a cloud server via the Internet, and the cloud server authenticates the identity information through an authentication module; If the authentication is successful, a license key generation module of the cloud server receives the key information, calculates and generates a license key, and then encrypts and sends the license key to the mobile electronic device; the mobile electronic device transmitting the encrypted license key to the motor vehicle; the motor vehicle receiving and decrypting the license key and verifying the validity of the license key; After verifying the validity, binding and adding the mobile electronic device that transmits the license key to a whitelist management module, and broadcasting a whitelist. A method for implementing a cloud license key binding system.
6. The authentication module of the cloud server verifies the identity by matching it with pre-stored authentication information. The method for implementing a cloud license key binding system according to claim 5.
7. The license key generation module performs key encryption and decryption operations using an asymmetric encryption algorithm. The method for implementing a cloud license key binding system according to claim 5.
8. The mobile electronic device transmits the license key to the motor vehicle via one of Bluetooth, Wi-Fi, or NFC wireless communication methods. The method for implementing a cloud license key binding system according to claim 5.
9. When the whitelist management module broadcasts a whitelist, the content of the broadcasted whitelist includes unique identification information of the licensed device, and the identification information is one or any combination of a MAC address, a UUID, and an IMSI of the mobile electronic device. The method for implementing a cloud license key binding system according to claim 5.
10. If the mobile electronic device cannot connect to a network, an external license device establishes an information link with the mobile electronic device to complete the authentication of the mobile electronic device and the generation of the license key. The method for implementing a cloud license key binding system according to claim 5.
Citation Information
Cited By
System for real-time object replacement and volatile rendering based on user device unique identification and license level
KR103000206B1