Cloud-based diagnostic device registration method and device
By verifying the legitimacy of registration requests for cloud-based diagnostic devices and dynamically assigning identifiers, the problems of reliance on manual operation for cloud-based diagnostic device registration and the vulnerability of identifiers to theft have been solved. This has enabled secure and automated device registration, improving operational efficiency and system security.
Patent Information
- Application Number
- CN202611132012.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-07-28
- Publication Date
- 2026-11-17
AI Technical Summary
In existing technologies, cloud-based diagnostic device registration relies on manual operation, which cannot achieve automated deployment. Furthermore, hard-coded serial numbers are easily stolen and forged, leading to security threats and low operational efficiency.
By verifying the legitimacy of registration requests from cloud-based diagnostic devices, dynamically binding network addresses and allocation identifiers, limiting the cumulative number of allocations for the same network address, and generating on-demand allocation identifiers, automated registration is achieved.
It enables secure and automated registration of cloud-based diagnostic devices, prevents identifier theft, improves operational efficiency and system security, and supports elastic scaling of cloud clusters.
Smart Images

Figure CN123123422A_ABST
Abstract
Description
Technical Field
[0001] This application belongs to the technical field of device registration in automotive remote cloud diagnostic systems, and particularly relates to a cloud-based diagnostic device registration method and apparatus. Background Technology
[0002] With the rapid development of automotive remote cloud diagnostic technology, cloud-based diagnostic devices (such as cloud phone instances) are widely used due to their elastic scaling and on-demand creation capabilities. Unlike traditional physical diagnostic devices, cloud-based diagnostic devices are typically dynamically generated using software-defined methods, and the way their identity identifiers are assigned directly affects the system's operational efficiency and security.
[0003] Currently, the existing technology generally adopts a hard-coded pre-allocation scheme to handle device registration. Specifically, the administrator pre-generates a unique identifier (such as a hard-coded serial number) for each physical or virtual device, and then solidifies the identifier in the device image or firmware through burning or configuration files. After the device starts up, it directly reads the unique identifier to complete the registration.
[0004] However, this traditional method has the following drawbacks: when the cloud cluster needs to be elastically expanded (e.g., temporarily adding a large number of cloud phone instances), the administrator needs to generate identifiers one by one, manually distribute configurations and restart nodes. The whole process relies on manual operation and cannot achieve automated and agile deployment. In addition, once the device image or firmware is cracked, the identifiers are easily stolen and forged. Attackers can use the stolen identifiers to impersonate legitimate devices to access the diagnostic network, causing serious security threats such as diagnostic data leakage and system integrity damage.
[0005] Therefore, in the actual operation of automotive remote cloud diagnostic systems, how to achieve safe and automated registration of cloud-based diagnostic devices has become a pressing technical problem to be solved. Summary of the Invention
[0006] This application provides a cloud-based diagnostic device registration method and apparatus, which can achieve secure and automated registration of cloud-based diagnostic devices.
[0007] In a first aspect, embodiments of this application provide a cloud-based diagnostic device registration method, including: Responding to the current registration request from the cloud-based diagnostic device, the system verifies the validity of the current registration request; the current registration request includes the network address of the cloud-based diagnostic device. When the current registration request passes the legality verification, the cumulative number of allocated identifiers corresponding to the current network address is determined, and if the cumulative number of allocated identifiers is not greater than the preset number of allocated identifiers, the allocation identifier corresponding to the current registration request is generated. The assigned identifier is sent to the cloud diagnostic device; the cloud diagnostic device is used to complete the current registration based on the assigned identifier.
[0008] In the embodiments of this application, In one possible implementation of the first aspect, the current registration request is validated for legality, including: when the network address matches the preset network address, the current registration request passes the validity verification; when the network address does not match the preset network address, the current registration request fails the validity verification and is rejected.
[0009] In one possible implementation of the first aspect, when the network address and the preset network address do not match successfully, the method further includes: responding to an audit operation on the network address; when the audit operation indicates that the network address has passed the audit, using the network address as the new preset network address; responding to the next registration request from the cloud diagnostic device, using the next registration request as the new current registration request, and returning to the steps of performing a legality verification of the current registration request and subsequent steps.
[0010] In one possible implementation of the first aspect, determining the cumulative number of allocation identifiers corresponding to the current network address includes: querying the historical allocation records of the cloud diagnostic device; when there are no historical allocation identifiers of the cloud diagnostic device in the historical allocation records, determining the cumulative number of allocation identifiers corresponding to the current network address.
[0011] In one possible implementation of the first aspect, the current registration request also includes the identification information of the cloud diagnostic device; querying the historical allocation records of the cloud diagnostic device includes: using the identification information as an index to retrieve historical allocation records that match the identification information.
[0012] In one possible implementation of the first aspect, the method further includes: when a historical allocation identifier of a cloud diagnostic device exists in the historical allocation record, sending the historical allocation identifier to the cloud diagnostic device; the cloud diagnostic device is used to complete the current registration based on the historical allocation identifier.
[0013] In one possible implementation of the first aspect, the method further includes: rejecting the current registration request when the cumulative number of allocated identifiers exceeds the preset number of allocated identifiers.
[0014] In one possible implementation of the first aspect, generating the allocation identifier corresponding to the current registration request includes: creating an allocation record corresponding to the current registration request; generating an allocation record number based on the allocation record; and concatenating the allocation record number and a preset business identifier in a preset order to generate the allocation identifier corresponding to the current registration request.
[0015] Secondly, embodiments of this application provide a cloud-based diagnostic device registration apparatus, comprising: The verification module is used to respond to the current registration request from the cloud-based diagnostic device and verify the legitimacy of the current registration request; wherein, the current registration request includes the network address of the cloud-based diagnostic device; The identifier generation module is used to determine the cumulative number of allocated identifiers corresponding to the current network address when the current registration request passes the legality verification, and to generate the allocation identifier corresponding to the current registration request if the cumulative number of allocated identifiers is not greater than the preset number of allocated identifiers. The registration module is used to send the assigned identifier to the cloud diagnostic device; the cloud diagnostic device is used to complete the current registration based on the assigned identifier.
[0016] Thirdly, embodiments of this application provide a terminal device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the cloud diagnostic device registration method as described in any of the first aspects.
[0017] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the cloud-based diagnostic device registration method as described in any of the first aspects.
[0018] Fifthly, embodiments of this application provide a computer program product that, when run on a terminal device, causes the terminal device to execute the cloud diagnostic device registration method described in any of the first aspects above.
[0019] The beneficial effects of the embodiments in this application compared with the prior art are: The aforementioned cloud-based diagnostic device registration method and apparatus, by verifying the legitimacy of the current registration request in response to the cloud-based diagnostic device's current registration request, can quickly filter illegal or forged registration sources, effectively ensuring the legitimacy of the cloud-based diagnostic device. After the current registration request passes the legitimacy verification, the cumulative number of allocated identifiers corresponding to the current network address is determined. If the cumulative number of allocated identifiers does not exceed a preset number of allocated identifiers, an allocation identifier corresponding to the current registration request is generated, thereby dynamically binding the registration quota to the network address of the cloud-based diagnostic device. This effectively prevents theft caused by the cracking of hard-coded serial numbers. By limiting the cumulative number of allocated identifiers under the same network address, capacity control of the resources corresponding to that network address is achieved, effectively preventing resource overload and waste caused by excessive registration of devices under a single network address. It also supports automatic allocation on demand, eliminating the need for manual pre-generation and burning by administrators, enabling automated deployment during elastic expansion of the cloud cluster. Finally, the allocation identifier is sent to the cloud-based diagnostic device, enabling the cloud-based diagnostic device to complete registration based on the allocation identifier, ensuring the entire registration process is secure, efficient, and scalable. Therefore, this invention not only eliminates the reliance on manual operation and maintenance in traditional hard-coded pre-allocation schemes and solves the defect of not being able to register automatically, but also improves the anti-counterfeiting and anti-theft capabilities of serial numbers through a dynamic quota verification mechanism based on network addresses, thereby realizing secure and automated registration of cloud-based diagnostic devices. Attached Figure Description
[0020] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0021] Figure 1 This is an application environment diagram of the cloud-based diagnostic device registration method provided in this application; Figure 2 A flowchart illustrating the cloud-based diagnostic device registration method provided in this application; Figure 3 A flowchart illustrating another cloud-based diagnostic device registration method provided in this application; Figure 4 A flowchart illustrating the process for determining the cumulative number of allocated identifiers is provided in this application; Figure 5 A flowchart illustrating the process of generating allocation identifiers provided in this application; Figure 6 A structural block diagram of the cloud-based diagnostic device registration apparatus provided in this application; Figure 7 An internal structural diagram of the terminal device provided in this application. Detailed Implementation
[0022] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail.
[0023] It should be understood that, when used in this application specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or a collection thereof.
[0024] It should also be understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.
[0025] As used in this application specification and the appended claims, the term "if" may be interpreted, depending on the context, as "when," "once," "in response to determination," or "in response to detection." Similarly, the phrase "if determined" or "if detected [the described condition or event]" may be interpreted, depending on the context, as meaning "once determined," "in response to determination," "once detected [the described condition or event]," or "in response to detection [the described condition or event]."
[0026] Furthermore, in the description of this application and the appended claims, the terms "first," "second," "third," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.
[0027] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.
[0028] Traditional cloud-based diagnostic device registration methods employ a hard-coded pre-allocation scheme, where administrators pre-generate unique identifiers for each device and embed them in the device image or firmware via flashing or configuration files. In cloud cluster elastic scaling scenarios, this method requires manual generation of identifiers, manual configuration distribution, and node restarts, failing to achieve automated deployment. Furthermore, if the device image or firmware is compromised, the identifiers are easily stolen and forged, increasing security risks and impacting system maintenance efficiency and diagnostic network security.
[0029] For example, in a remote cloud diagnostic system for automobiles, when additional cloud phone instances need to be added temporarily during peak business periods, the administrator must manually handle the identifier allocation process for each instance, including generating a unique identifier, configuring it to the image, and restarting the node. During this process, if the device image is accessed without authorization, an attacker can extract the identifier and impersonate a legitimate device to access the diagnostic network, resulting in unauthorized operations.
[0030] If the above problems are not resolved, the system will rely on manual intervention for a long time, and the complexity of operation and maintenance will continue to increase. At the same time, the risk of identity theft may lead to the theft of diagnostic data or malicious intrusion into the network, which will damage the reliability of the system and the security of user data.
[0031] To overcome the aforementioned shortcomings and achieve secure and automated registration of cloud-based diagnostic devices, thereby addressing the issues of manual operation, lack of automated deployment, and susceptibility to theft and forgery of identifiers in existing technologies, the cloud-based diagnostic device registration method provided in this application can be applied to, for example... Figure 1 In the application environment shown, the cloud diagnostic device 102 communicates with the server 104 via a network. A data storage system can store the data that the server 104 needs to process. The data storage system can be integrated onto the server 104, or it can be located in the cloud or on another network server. The cloud diagnostic device 102 initiates a current registration request to the server 104. Upon receiving the current registration request, the server 104 verifies its validity. If the current registration request passes the validity verification, it determines the cumulative number of allocated identifiers corresponding to the current network address, and generates an allocation identifier corresponding to the current registration request if the cumulative number of allocated identifiers is not greater than a preset number of allocation identifiers. The allocation identifier is then sent to the cloud diagnostic device 102. The cloud diagnostic device 102 completes the current registration based on the allocation identifier. The server 104 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud computing services.
[0032] In one exemplary embodiment, such as Figure 2 As shown, a cloud-based diagnostic device registration method is provided, which can be applied to... Figure 1Taking server 104 as an example, the explanation includes the following steps S201 to S203. Wherein: S201, responding to the current registration request from the cloud-based diagnostic device, verifies the legitimacy of the current registration request.
[0033] The current registration request includes the network address of the cloud-based diagnostic device.
[0034] Cloud-based diagnostic devices refer to virtualized diagnostic tools or instances running in a cloud computing environment, such as cloud phone instances. These devices feature elastic scaling and on-demand creation capabilities, and are used for remote diagnostics of vehicles or other devices.
[0035] A current registration request refers to a connection request sent to the registration service by a cloud-based diagnostic device when it is first started or needs to reconnect to the diagnostic system, containing its basic information (such as its network address).
[0036] Legitimacy verification refers to the process of performing a security check on the current registration request issued by the cloud-based diagnostic device to confirm whether the request comes from an authorized and trusted source, thus preventing unauthorized devices from accessing the site.
[0037] A network address is a unique identifier for a cloud-based diagnostic device within a network. This can be an IP (Internet Protocol) address, a MAC (Media Access Control) address, or other logical or physical addresses used for network communication. This address is used to locate and identify the device within the network.
[0038] When server 104 receives a registration request from a cloud-based diagnostic device, it can verify the validity of the registration request. For example, when a cloud-based diagnostic device starts up for the first time, it can send a registration request to server 104, which carries the network address of the cloud-based diagnostic device. After receiving the registration request, server 104 will perform a preliminary validity verification.
[0039] Optionally, legitimacy verification can be implemented in various ways. For example, server 104 can check whether the registration request contains a preset shared key, or verify whether the registration request comes from a known, trusted network area. If the registration request lacks the necessary security credentials, or its source does not conform to the preset security policy, the registration request will be considered illegitimate.
[0040] S202, when the current registration request passes the legality verification, determine the cumulative number of allocated identifiers corresponding to the current network address, and generate the allocation identifier corresponding to the current registration request if the cumulative number of allocated identifiers is not greater than the preset number of allocated identifiers.
[0041] The cumulative number of allocated identifiers refers to the total number of registered identifiers successfully assigned to cloud-based diagnostic devices for a specific network address. This number is used to limit the number of devices registered from the same network address.
[0042] The preset number of allocated identifiers refers to the maximum number of cloud diagnostic devices allowed to register from the same network address, as pre-set by the system administrator or policy. This maximum number is a threshold for judging the cumulative number of allocated identifiers, used to limit the number of registration identifiers that a single network address or device can obtain, to prevent excessive resource consumption or malicious registration. This preset number of allocated identifiers can be set according to actual needs, and its specific value is not limited here.
[0043] An allocation identifier is a unique identity credential generated and assigned to a diagnostic device by the registration service after the device has passed legitimacy verification and met the allocation conditions in the cloud. This allocation identifier is used for subsequent authentication and identification of the device in the diagnostic system.
[0044] When a current registration request passes the validity verification, the cumulative number of allocated identifiers corresponding to that network address is determined. Then, if the cumulative number of allocated identifiers is not greater than a preset number of allocated identifiers, an allocation identifier corresponding to the current registration request is generated. For example, after the above validity verification passes, server 104 will query internal records to understand how many cloud diagnostic devices have previously successfully registered and obtained allocated identifiers for that network address. This query can be easily implemented by maintaining a mapping table between network addresses and the number of allocated identifiers. If the query result shows that the cumulative number of allocated identifiers for that network address has not yet reached the preset number of allocated identifiers (for example, each IP address is allowed to register a maximum of 50 cloud diagnostic devices), server 104 will generate a new allocation identifier for that cloud diagnostic device. This allocation identifier can be a randomly generated string or a unique code based on a combination of a timestamp and the device's network address.
[0045] S203, send the assigned identifier to the cloud diagnostic device.
[0046] Among them, the cloud-based diagnostic device is used to complete the current registration based on the assigned identifier.
[0047] Completed registration means that after the cloud-based diagnostic device receives the assigned identifier, it stores and configures it into its own system, thus officially becoming a member of the diagnostic network and able to begin performing diagnostic tasks.
[0048] Server 104 sends an allocation identifier to the cloud diagnostic device, enabling the device to complete its current registration. For example, once the allocation identifier is successfully generated, server 104 can send it to the cloud diagnostic device that initiated the registration request via a secure, encrypted channel. Upon receiving the allocation identifier, the cloud diagnostic device stores it in its local configuration and uses it as its unique identity credential within the diagnostic system. Subsequently, the cloud diagnostic device will use this allocation identifier for authentication during subsequent interactions with the diagnostic system, thus completing its registration process within the entire diagnostic system.
[0049] The following example will provide a more detailed explanation of the above technical solution: Suppose a remote automotive diagnostics system needs to dynamically deploy a batch of cloud-based diagnostic devices to handle unexpected diagnostic tasks. The system administrator has preset that each network address can register a maximum of 100 cloud-based diagnostic devices.
[0050] When a new cloud-based diagnostic device A is instantiated and started, a registration request is automatically sent to the diagnostic system's server 104. This registration request contains the current network address of cloud-based diagnostic device A.
[0051] After receiving the registration request from cloud-based diagnostic device A, server 104 first verifies its legitimacy. For example, server 104 checks whether the registration request carries a valid API (Application Programming Interface) key, which is pre-configured in all legitimate cloud-based diagnostic device images. If the registration request contains the correct API key, the legitimacy verification passes.
[0052] After the legitimacy verification is successful, server 104 will query its internal database to determine how many allocation identifiers have been assigned to the IP address. Let's assume the query result shows that the IP address has currently been assigned 95 allocation identifiers. Since 95 is no greater than the preset number of 100 allocation identifiers, it is determined that a new allocation identifier can be assigned to cloud diagnostic device A.
[0053] Subsequently, server 104 will generate a brand new, unique allocation identifier. This allocation identifier can be a randomly generated string to ensure its uniqueness.
[0054] After generating the allocation identifier, server 104 sends it back to cloud-based diagnostic device A via the network. Upon receiving the allocation identifier, cloud-based diagnostic device A stores it in its local configuration file and uses it as its identity credential within the diagnostic system. At this point, cloud-based diagnostic device A has completed its registration and can begin receiving and executing diagnostic tasks.
[0055] The method provided in this embodiment ensures that only authorized cloud diagnostic devices can initiate registration by introducing a validity verification of the current registration request. Simultaneously, by determining the cumulative number of allocated identifiers corresponding to a network address and setting a preset upper limit for the number of allocated identifiers, it effectively prevents malicious devices from registering in large numbers through forged requests, thereby enhancing system security. For example, in the above example, if the registration request of cloud diagnostic device A fails the validity verification, or if the IP address has reached its allocation limit, cloud diagnostic device A will not be able to obtain an allocated identifier, thus being blocked from registration. This mechanism avoids the problem of unauthorized device access that may result from identifier theft in existing technologies. Furthermore, this method achieves automated generation and distribution of allocated identifiers without manual intervention, greatly improving the automation level and deployment efficiency of cloud diagnostic device registration, and solving the problems of cumbersome manual operations and the inability to achieve automated deployment in existing technologies. Therefore, the technical solution of this embodiment demonstrates significant progress and practicality in achieving secure and automated registration of cloud diagnostic devices.
[0056] Based on the above embodiments, in an exemplary embodiment, the legality verification process in S201 is further refined. Optionally, it may include: when the network address and the preset network address match successfully, the current registration request passes the legality verification; when the network address and the preset network address do not match successfully, the current registration request fails the legality verification and is rejected.
[0057] The preset network addresses refer to a list of network addresses considered legitimate, pre-stored, configured, or maintained by the system or server 104. These preset network addresses can be in the form of a whitelist, meaning only preset network addresses on the whitelist are allowed to register, while network addresses not included in the whitelist are prohibited from registration. Preset network addresses can be maintained through manual entry, import from the authorization database, or configuration via other management interfaces.
[0058] The system can use any method, such as exact matching, fuzzy matching, or subnet matching, to match network addresses with preset network addresses. When the preset network address is in whitelist form, a successful match means that the current network address exists in the preset whitelist, and server 104 confirms that the registration request comes from an authorized or trusted cloud diagnostic device, and the current registration request meets the legitimacy verification. If the match fails, it means that the current network address does not exist in the preset whitelist, and server 104 confirms that the registration request comes from an unauthorized or untrusted cloud diagnostic device, and the current registration request fails the legitimacy verification and is rejected. The rejection operation can include directly disconnecting the connection, returning an error code, or logging.
[0059] The following is a concrete example. When a cloud-based diagnostic device attempts to connect to the cloud-based diagnostic platform and sends a registration request, the request first reaches a server 104. Server 104 resolves the IP address of the cloud-based diagnostic device from the registration request as its network address. Then, server 104 queries an internally maintained whitelist of authorized IP addresses, which includes the default network addresses. If the resolved IP address is found in the whitelist, the match is considered successful, and the registration request passes the validity verification. Server 104 then proceeds to the subsequent process of assigning and sending identifiers. If the resolved IP address is not in the whitelist, the match is considered unsuccessful, and the registration request fails the validity verification. In this case, server 104 immediately returns a registration failure error code to the cloud-based diagnostic device and disconnects, thus rejecting the registration request.
[0060] The proposed solution refines the verification of the legitimacy of the current registration request in the cloud-based diagnostic device registration method into a network address-based matching mechanism. This mechanism can effectively identify and distinguish between legitimate and illegitimate registration requests. When the network address matches successfully, legitimate devices are allowed to smoothly enter the subsequent registration process; when the network address matches unsuccessfully, illegitimate requests are directly rejected. This effectively filters out illegal or unauthorized registration attempts, thereby ensuring the security of the cloud-based diagnostic system and the rational use of resources, and avoiding problems such as data leakage, service interruption, or resource abuse that may result from illegal registration.
[0061] In some embodiments described above, a method is proposed to verify the legitimacy of registration requests for cloud-based diagnostic devices. If the network address of the cloud-based diagnostic device does not match a preset network address, the registration request will be rejected. However, this mechanism may prevent new or legitimate cloud-based diagnostic devices with changed network addresses from successfully registering.
[0062] Therefore, based on the above embodiments, in an exemplary embodiment, when the network address and the preset network address fail to match, such as... Figure 3 As shown, the method also includes: S301, responding to the audit operation of the network address.
[0063] The review process refers to the manual or semi-automatic review of network addresses that do not match the preset network address to determine whether they are legitimate cloud diagnostic devices.
[0064] When the network address of the cloud-based diagnostic device does not match the preset network address, server 104 will no longer directly reject the registration request, but will instead respond with an audit operation. For example, server 104 can send a notification to an authorized administrator, who can then review the network address through the management interface and submit the audit results; alternatively, server 104 can add the network address to the list of pending audits and provide an interface for authorized users to audit and make decisions.
[0065] S302, when the audit operation indicates that the network address has passed the audit, the network address will be used as the new preset network address.
[0066] When the review process indicates that the network address has passed the review, server 104 will store the network address as a new preset network address. This can be achieved by automatically adding the network address to a database or configuration file that stores preset network addresses, or by having server 104 call the corresponding application programming interface to write the network address into the preset network address set after the administrator confirms approval on the review interface.
[0067] Optionally, when the preset network address is in the form of a whitelist, and when the network address is not in the whitelist, the network address and the registration request time are written to the interception log database, and the status is marked as "pending processing".
[0068] After the operations and maintenance personnel view the pending interception records in the backend and confirm that the network address belongs to the newly expanded cloud diagnostic device, they click "Approve and Release". Server 104 dynamically adds the network address to the whitelist and marks its historically blocked requests as "Released" in batches.
[0069] S303 responds to the next registration request from the cloud-based diagnostic device, treats the next registration request as the new current registration request, and returns to execute the steps for validating the validity of the current registration request and subsequent steps.
[0070] When the cloud-based diagnostic device initiates a registration request again, server 104 will reprocess the registration request starting from the legitimacy verification step based on the updated preset network address.
[0071] This application's solution introduces an audit process and a mechanism for dynamically updating preset network addresses, enabling the system to flexibly handle unknown but legitimate cloud diagnostic device network addresses. When a cloud diagnostic device initiates a registration request and its network address does not match the existing preset network address, the system does not immediately reject it but triggers an audit process. Once the network address passes the audit, the system dynamically adds it to the preset network address list. Subsequently, when the cloud diagnostic device initiates a registration request again, its network address will be able to match the updated preset network address, thus successfully passing the legitimacy verification and continuing to execute the subsequent steps of assigning identifiers and sending them. This mechanism effectively combines manual auditing with an automated registration process, forming a closed-loop, adaptive registration management system. It avoids legitimate device registration failures due to incomplete preset lists, significantly improving the system's robustness and user experience.
[0072] Based on the above embodiments, in an exemplary embodiment, the process of determining the cumulative number of allocated identifiers in step S202 is further refined. Optionally, such as Figure 4 As shown, it includes: S401, query the historical allocation records of cloud-based diagnostic devices.
[0073] Among them, historical allocation records refer to the past registration or identification allocation information of cloud-based diagnostic devices, which provide a basis for subsequent judgments on whether to allow the allocation of new identifications.
[0074] Historical allocation records can be queried by maintaining a device registration database on server 104. This database stores information such as the network address, allocation identifier, and registration time for each registered device. When a registration request is received, server 104 can retrieve the data from this database based on the network address or unique device identifier in the request. Alternatively, a distributed storage system can be used to distribute the registration history of cloud-based diagnostic devices across multiple nodes, and aggregate queries can be performed through a specific query interface.
[0075] As an optional implementation, the current registration request also includes the identification information of the cloud-based diagnostic device. Based on this, the historical allocation records of the cloud-based diagnostic device are queried, including: using the identification information as an index to retrieve historical allocation records that match the identification information.
[0076] The identification information of the cloud diagnostic device refers to specific data used to uniquely identify the cloud diagnostic device. This identification information can be a hardware serial number, such as the device's MAC address, CPU serial number, or motherboard serial number. This information is usually fixed during the manufacturing of the cloud diagnostic device and has global uniqueness. In this embodiment, the unique_id (device unique identifier) of the cloud diagnostic device can be selected as its identification information. The unique_id is a globally unique ID generated based on the device's hardware characteristics and is used to identify an independent device.
[0077] Using the identification information of cloud-based diagnostic devices as query criteria, all relevant historical allocation records for that device can be located from stored historical data. Specifically, in a database system, an index can be created for the table storing the device's historical allocation records, using the identification information as the key. When a query is needed, it can be performed quickly directly through this index. Furthermore, in distributed storage or big data scenarios, hash mapping or key-value storage can be used to directly map the identification information as the key to the corresponding historical allocation record data block or storage location, thereby achieving fast retrieval.
[0078] S402, when there is no historical allocation identifier for cloud diagnostic devices in the historical allocation record, determine the cumulative number of allocation identifiers corresponding to the current network address.
[0079] When there is no historical allocation identifier for the cloud diagnostic device in the historical allocation record, the step of determining the cumulative number of allocation identifiers corresponding to the current network address provides a clear mechanism for determining the cumulative number of allocation identifiers for devices registering for the first time or without historical records. This ensures that the device can successfully complete its initial registration and avoids the inability to perform subsequent judgments due to the lack of historical records. In this case, server 104 counts the cumulative number of allocation identifiers corresponding to the network address at the current moment to determine whether the cloud diagnostic device can obtain a new allocation identifier.
[0080] As an optional implementation, when a historical allocation identifier of the cloud diagnostic device exists in the historical allocation record, the historical allocation identifier is sent to the cloud diagnostic device; the cloud diagnostic device is used to complete the current registration based on the historical allocation identifier.
[0081] The historical allocation record contains historical allocation identifiers for cloud-based diagnostic devices. These identifiers are valid identifiers that have been previously allocated and can be found in the system's stored dataset of allocated identifiers by querying the database. This historical allocation record can be stored in a database.
[0082] When a valid historical allocation identifier for the cloud diagnostic device is confirmed in the historical allocation record, server 104 transmits this identifier to the cloud diagnostic device that initiated the registration request via network communication. Upon receiving the historical allocation identifier, the cloud diagnostic device uses it as an identity credential to complete its current registration process, thereby authenticating and authorizing it during subsequent interactions with server 104. This transmission process can be implemented using various communication protocols. For example, it can transmit the identifier information encapsulated in JSON (JavaScript Object Notation) or XML (Extensible Markup Language) format via HTTP (Hypertext Transfer Protocol) / HTTPS (Hypertext Transfer Protocol Secure); or it can publish a message containing the identifier information via MQTT (Message Queuing Telemetry Transport); or it can use a custom binary protocol for efficient transmission. The transmission channel should ensure data security and integrity, for example, by using TLS (Transport Layer Security) / SSL (Secure Sockets Layer) encryption.
[0083] The following is a concrete example. Suppose a cloud-based diagnostic device successfully registers for the first time and obtains an allocation identifier "DIAG-ABC-001". Due to network fluctuations or a device restart, the cloud-based diagnostic device needs to re-initiate a registration request to the cloud registration service. When the cloud registration service receives the current registration request from the cloud-based diagnostic device, it first verifies the validity of its network address. Assuming the verification passes, the system further queries the historical allocation records of the cloud-based diagnostic device. If the system finds the historical allocation identifier "DIAG-ABC-001" in the historical allocation records, and the historical allocation identifier is still valid, the system will directly send "DIAG-ABC-001" back to the cloud-based diagnostic device. After receiving "DIAG-ABC-001", the cloud-based diagnostic device uses it as an identity credential to complete the subsequent registration process, such as establishing a secure connection with server 104 and starting data transmission.
[0084] The proposed solution, upon receiving a current registration request from a cloud-based diagnostic device and completing its legality verification, determines whether the device has previously been assigned an allocation identifier by querying its historical allocation records. If a valid historical allocation identifier is found, the system does not generate a new identifier but directly sends the existing one to the device. Upon receiving this identifier, the cloud-based diagnostic device can then use it to complete its current registration. This mechanism enables the system to intelligently identify already registered devices and reuse their existing historical allocation identifiers, avoiding the duplication of identifier generation and ensuring that retries for the same cloud-based diagnostic device do not consume additional resources, thus saving system resources. Simultaneously, this also helps maintain the stability and consistency of the cloud-based diagnostic device's identity identifier, simplifies the device re-registration process, and improves registration efficiency and user experience. Only when the query results show that the historical allocation identifier of the cloud diagnostic device does not exist in the historical allocation record is the cumulative number of allocation identifiers corresponding to the current network address determined. This lays the foundation for determining whether to allocate a new allocation identifier to the cloud device based on the cumulative number of allocation identifiers. This ensures that when any legitimate cloud diagnostic device faces network jitter, APP (Application) reinstallation, or malicious retries, the system always returns only the uniquely bound allocation identifier, avoiding the generation of dirty data in the database and the waste of resources.
[0085] In some of the embodiments described above in this application, a technical solution is proposed to verify the legitimacy of registration requests for cloud-based diagnostic devices and generate allocated identifiers when the cumulative number of allocated identifiers does not exceed a preset number of allocated identifiers. However, in practical applications, if the cumulative number of allocated identifiers exceeds the preset limit, the system may face risks such as resource abuse, reduced security, or unpredictable behavior, and there is a lack of clear response mechanisms to effectively manage and control the allocation of identifiers.
[0086] In this regard, based on the above embodiments, in an exemplary embodiment, the method further includes: rejecting the current registration request when the cumulative number of allocated identifiers is greater than a preset number of allocated identifiers.
[0087] When server 104 detects that the cumulative number of allocated identifiers corresponding to the current network address exceeds the preset number of allocated identifiers, it takes explicit processing measures for registration requests that exceed the allocation limit in order to prevent non-compliant registration behavior and maintain the reasonable allocation and security of system resources.
[0088] Optionally, server 104 can return an error code or rejection message to the cloud diagnostic device that initiated the registration request, clearly indicating the reason for the registration failure, such as returning a "resource limit exceeded" message. In addition, server 104 can record this rejection operation and trigger an alarm mechanism to notify the administrator that a device has attempted to register beyond the limits. Simultaneously, no allocation identifier is generated, and no registration status is updated.
[0089] The proposed solution explicitly stipulates that when the cumulative number of allocated identifiers exceeds the preset limit, the system will cease generating new identifiers and directly reject the current registration request. This mechanism ensures that the system can effectively manage and control resource allocation, preventing a single device or network address from acquiring registration identifiers without restriction, thereby avoiding resource exhaustion, system overload, or potential security risks. By introducing this judgment and rejection logic after legitimacy verification and before identifier generation, the proposed solution ensures the security of the registration process while also achieving refined management of system resources. This ensures the stability and controllability of the system when handling a large number of registration requests, thereby improving the robustness and security of the entire cloud-based diagnostic device registration system.
[0090] Based on the above embodiments, in an exemplary embodiment, the process of generating the allocation identifier in step S202 is further refined. Optionally, such as Figure 5 As shown, it includes: S501, Create the allocation record corresponding to the current registration request.
[0091] The allocation record refers to structured data used to store information related to cloud-based diagnostic device registration requests. This information may include, but is not limited to, request time, requesting device network address, requesting device identification information (such as device serial number, MAC address, etc.), request status, and subsequently generated allocation identifiers.
[0092] This can be achieved by inserting a new data record into the database on server 104, which contains the parameters of the registration request; or by creating a new file or record item in the distributed file system to store the metadata of the registration request.
[0093] S502, Generate an allocation record number based on the allocation record.
[0094] The allocation record number is a string or number sequence used to uniquely identify an allocation record. It can be generated based on certain fields in the allocation record, using a specific algorithm or rule.
[0095] You can use an auto-incrementing ID from the database as the allocation record number to ensure its uniqueness; or you can combine the creation timestamp of the allocation record, the hash value of the device network address, and a random number to generate a globally unique allocation record number using a hash algorithm.
[0096] S503, the allocation record number and the preset business identifier are concatenated in a preset order to generate the allocation identifier corresponding to the current registration request.
[0097] Among them, the preset business identifier is a predefined unique identifier used to distinguish different business types or application scenarios. The allocation identifier is the credential ultimately sent to the cloud diagnostic device for registration; it combines the allocation record number and the business identifier. The preset order refers to the order in which the allocation record number and the preset business identifier are arranged during the assembly process.
[0098] The allocation record number can be used as a prefix, the preset business identifier as a suffix, and a specific separator (such as "-") can be used in between; or the preset business identifier can be used as a prefix, the allocation record number as a suffix, or a more complex encoding rule can be adopted, such as performing an XOR operation on the two before encoding, to increase the security of the identifier.
[0099] In some of the embodiments described above in this application, when the current registration request of the cloud diagnostic device passes the legality verification and the cumulative number of allocated identifiers corresponding to the current network address does not exceed a preset limit, the system needs to generate an allocation identifier to complete the registration. To ensure that the generated allocation identifier has good traceability, uniqueness, and business relevance, this application proposes a structured generation mechanism. First, the system creates a detailed allocation record for the current registration request, which contains all the key information of this registration request, such as the request time and device network address. This allocation record is the basis for the generation of all subsequent identifiers, ensuring that every registration behavior is traceable. Next, based on this newly created allocation record, the system generates a unique allocation record number. This record number is an abstract and unique identifier of a specific registration behavior, enabling the rapid location of the specific allocation event even among a large number of registration requests. Finally, to ensure that the final allocation identifier is not only unique but also carries business-level information, the system concatenates this allocation record number with a preset business identifier in a specific order. This concatenation method ensures that the generated allocation identifier contains both the unique identification information of the underlying registration behavior and the classification or attribution information of the upper-layer business logic. In this way, the generated allocation identifiers not only effectively guide cloud-based diagnostic devices to complete registration, but also facilitate subsequent device classification management, access control, and diagnostic service scheduling for different business scenarios, avoiding the complexity of additional queries and related operations. Therefore, this solution not only improves the practicality and management efficiency of allocation identifiers, but also lays a solid foundation for the full lifecycle management of cloud-based diagnostic devices, enabling the system to identify and manage cloud-based diagnostic devices more efficiently and accurately.
[0100] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.
[0101] Corresponding to the cloud-based diagnostic device registration method in the above embodiments, Figure 6 The diagram shows a schematic of a cloud-based diagnostic device registration apparatus according to an embodiment of this application. For ease of explanation, only the parts related to the embodiment of this application are shown.
[0102] Reference Figure 6 The cloud-based diagnostic device registration apparatus of this embodiment includes: The verification module 601 is used to respond to the current registration request from the cloud diagnostic device and verify the legitimacy of the current registration request; wherein, the current registration request includes the network address of the cloud diagnostic device.
[0103] The identifier generation module 602 is used to determine the cumulative number of allocated identifiers corresponding to the current network address when the current registration request passes the legality verification, and generate the allocation identifier corresponding to the current registration request if the cumulative number of allocated identifiers is not greater than the preset number of allocated identifiers.
[0104] The registration module 603 is used to send the allocation identifier to the cloud diagnostic device; the cloud diagnostic device is used to complete the current registration based on the allocation identifier.
[0105] As an optional implementation, the verification module 601 is specifically used to: when the network address and the preset network address do not match successfully, the current registration request fails the legality verification and the current registration request is rejected.
[0106] As an optional implementation, when the network address and the preset network address fail to match, the cloud diagnostic device registration device further includes: an audit module for responding to the audit operation on the network address; an update module for using the network address as the new preset network address when the audit operation indicates that the network address has passed the audit; and a request processing module for responding to the next registration request from the cloud diagnostic device, using the next registration request as the new current registration request, and returning to the steps of performing legality verification on the current registration request and subsequent steps.
[0107] As an optional implementation, the identifier generation module 602 includes: a query unit for querying historical allocation records of cloud diagnostic devices; and a statistics unit for determining the cumulative number of allocation identifiers corresponding to the current network address when there are no historical allocation identifiers of cloud diagnostic devices in the historical allocation records.
[0108] As an optional implementation, the current registration request also includes the identification information of the cloud diagnostic device; the query unit is specifically used to: use the identification information as an index to retrieve historical allocation records that match the identification information.
[0109] As an optional implementation, the cloud diagnostic device registration device further includes: a historical identifier module, used to send the historical allocation identifier to the cloud diagnostic device when a historical allocation identifier of the cloud diagnostic device exists in the historical allocation record; the cloud diagnostic device is used to complete the current registration based on the historical allocation identifier.
[0110] As an optional implementation, the cloud-based diagnostic device registration apparatus further includes a request rejection module, used to reject the current registration request when the cumulative number of allocated identifiers exceeds a preset number of allocated identifiers.
[0111] As an optional implementation, the identifier generation module 602 is specifically used to: create an allocation record corresponding to the current registration request; generate an allocation record number based on the allocation record; and concatenate the allocation record number and the preset business identifier in a preset order to generate the allocation identifier corresponding to the current registration request.
[0112] It should be noted that the information interaction and execution process between the modules in the above-mentioned cloud diagnostic device registration device are based on the same concept as the method embodiment of this application. For details on their specific functions and technical effects, please refer to the method embodiment section, which will not be repeated here.
[0113] This application also provides a terminal device, such as... Figure 7 As shown, Figure 7 This is a schematic diagram of the structure of a terminal device provided in an embodiment of this application. (Refer to...) Figure 7 The terminal device includes a processor, memory, input / output (I / O) interfaces, and a communication interface. The processor, memory, and I / O interfaces are connected via a system bus, and the communication interface is also connected to the system bus via the I / O interfaces. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The database stores data from the cloud-based diagnostic device registration method. The I / O interfaces are used for information exchange between the processor and external devices. The communication interface is used for communication with external terminals via a network connection. When the computer program is executed by the processor, it implements the steps in any of the above-described embodiments of the cloud-based diagnostic device registration method.
[0114] Those skilled in the art will understand that Figure 7 The structure shown is merely a block diagram of a portion of the structure related to the solution of this application and does not constitute a limitation on the terminal device to which the solution of this application is applied. A specific terminal device may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.
[0115] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, can implement the steps in the above-described method embodiments.
[0116] This application provides a computer program product that, when run on a mobile terminal, enables the mobile terminal to implement the steps described in the various method embodiments.
[0117] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments of this application can be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include at least: any entity or device capable of carrying the computer program code to a photographic device / terminal device, a recording medium, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier signal, a telecommunication signal, and a software distribution medium. Examples include USB flash drives, portable hard drives, magnetic disks, or optical disks.
[0118] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.
[0119] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0120] In the embodiments provided in this application, it should be understood that the disclosed apparatus / network devices and methods can be implemented in other ways. For example, the apparatus / network device embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.
[0121] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0122] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.
Claims
1. A cloud diagnostic device registration method, characterized by, include: In response to a current registration request from a cloud-based diagnostic device, the system verifies the validity of the current registration request; the current registration request includes the network address of the cloud-based diagnostic device. When the current registration request passes the legality verification, the cumulative number of allocated identifiers corresponding to the current network address is determined, and if the cumulative number of allocated identifiers is not greater than the preset number of allocated identifiers, an allocation identifier corresponding to the current registration request is generated; The allocation identifier is sent to the cloud diagnostic device; the cloud diagnostic device is used to complete the current registration based on the allocation identifier.
2. The cloud diagnostic device registration method of claim 1, wherein, The process of validating the legality of the current registration request includes: When the network address matches the preset network address, the current registration request passes the legality verification. When the network address and the preset network address do not match successfully, the current registration request fails the validity verification and is rejected. 3.The cloud diagnostic device registration method of claim 2, wherein, When the network address and the preset network address fail to match, the method further includes: Respond to the audit operation on the network address; When the audit operation indicates that the network address has passed the audit, the network address will be used as the new preset network address; In response to the next registration request from the cloud-based diagnostic device, the next registration request is treated as the new current registration request, and the process returns to perform the step of verifying the legality of the current registration request and subsequent steps.
4. The cloud-based diagnostic device registration method according to any one of claims 1-3, characterized in that, Determining the cumulative number of allocated identifiers corresponding to the current network address includes: Query the historical allocation records of the cloud-based diagnostic devices; When the historical allocation record does not contain the historical allocation identifier of the cloud diagnostic device, the cumulative number of allocation identifiers corresponding to the current network address is determined.
5. The cloud-based diagnostic device registration method according to claim 4, characterized in that, The current registration request also includes the identification information of the cloud diagnostic device; querying the historical allocation records of the cloud diagnostic device includes: Using the identification information as an index, retrieve historical allocation records that match the identification information.
6. The cloud-based diagnostic device registration method according to claim 4, characterized in that, Also includes: When the historical allocation record contains the historical allocation identifier of the cloud diagnostic device, the historical allocation identifier is sent to the cloud diagnostic device; the cloud diagnostic device is used to complete the current registration based on the historical allocation identifier.
7. The cloud-based diagnostic device registration method according to any one of claims 1-3, characterized in that, Also includes: When the cumulative number of allocated identifiers exceeds the preset number of allocated identifiers, the current registration request is rejected.
8. The cloud-based diagnostic device registration method according to any one of claims 1-3, characterized in that, The generation of the allocation identifier corresponding to the current registration request includes: Create an allocation record corresponding to the current registration request; Generate an allocation record number based on the allocation record; The allocation record number and the preset business identifier are concatenated in a preset order to generate the allocation identifier corresponding to the current registration request.
9. A cloud-based diagnostic device registration device, characterized in that, include: The verification module is used to respond to the current registration request from the cloud-based diagnostic device and verify the legitimacy of the current registration request; wherein, the current registration request includes the network address of the cloud-based diagnostic device; The identifier generation module is used to determine the cumulative number of allocated identifiers corresponding to the current network address when the current registration request passes the legality verification, and generate the allocation identifier corresponding to the current registration request if the cumulative number of allocated identifiers is not greater than the preset number of allocated identifiers. The registration module is used to send the allocation identifier to the cloud diagnostic device; the cloud diagnostic device is used to complete the current registration based on the allocation identifier.
10. A terminal device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the method as described in any one of claims 1 to 8.
