Global unique identifier generation method and system under edge calculation

Abstract

The invention discloses a global unique identifier generation method and system under edge computing, belongs to the technical field of edge computing, and aims to solve the technical problem of how to generate a unique identifier under edge computing according to the environmental characteristics of edge computing, and the method has high efficiency, uniqueness, incremental performance and safety at the same time. According to the technical scheme, the method comprises the following steps: applying for a unique identifier: an edge node sends a node ID of the edge node to a center node, and further applies for a global unique identifier from the center node; calculating a timestamp: after the center node receives the application of the edge node, acquiring the current accurate time, and calculating the timestamp with the length of 40 bits; determining a service number: directly using the ID submitted by the edge node as a 12-bit service number by the center node; acquiring and progressively increasing a serial number: acquiring the current serial number from the database by the central node, and progressively increasing the current serial number by 1 to obtain a 12-bit serial number; encrypting the confused ID; and returning the unique identifier.

Description

Technical Field

[0001] The present invention relates to the field of edge computing technology, and specifically to a method and system for generating a globally unique identifier under edge computing. Background Art

[0002] The generation of globally unique identifiers (GUIDs) is crucial in today's systems. An ideal GUID should be unique, have an increasing trend, be secure (unpredictable and unguessable), have a numeric type, high performance, and high availability. Common generation strategies include database auto-increment sequences, UUIDs, and Twitter's SnowFlake algorithm. While simple, database auto-increment sequences pose the security issue of continuous guessability. While UUIDs guarantee global uniqueness, they lack an increasing trend when used as primary keys and are not numeric. The SnowFlake algorithm generates unique IDs using timestamps but relies on the system clock, potentially leading to uniqueness issues when the clock is set back.

[0003] In summary, the prior art has the following defects:

[0004] ① Uniqueness issue: Traditional unique identifiers generated based on a combination of timestamps, machine identifiers, and random numbers may have potential duplication and conflict issues in high-concurrency edge computing.

[0005] ②Performance issues: Some unique identifier generation methods may perform poorly in a high-concurrency environment. For example, a unique identifier generated by a database may become a performance bottleneck, thereby affecting the operating efficiency of the entire system.

[0006] ③ Security Issues: Some traditional methods may have security vulnerabilities, such as being easily predictable or vulnerable to attacks, which may lead to ID conflicts or system security issues. For example, a hacker could obtain an order ID and calculate a merchant's actual order volume for the day.

[0007] Therefore, how to generate a unique identifier under edge computing based on the environmental characteristics of edge computing, while being efficient, unique, incremental and secure, is a technical problem that needs to be solved urgently. Summary of the Invention

[0008] The technical task of the present invention is to provide a method and system for generating a globally unique identifier under edge computing to solve the problem of how to generate a unique identifier under edge computing according to the environmental characteristics of edge computing, while having high efficiency, uniqueness, incrementality and security.

[0009] The technical task of the present invention is achieved in the following manner: a method for generating a globally unique identifier under edge computing, the method is as follows:

[0010] Apply for a unique identifier: The edge node sends its own node ID to the central node, and then applies for a globally unique identifier from the central node;

[0011] Calculate timestamp: After receiving the request from the edge node, the central node obtains the current precise time and calculates a 40-bit timestamp;

[0012] Determine the service number: The central node directly uses the ID submitted by the edge node as the 12-digit service number;

[0013] Obtain and increment the serial number: The central node obtains the current serial number from the database and increments it by 1 to obtain a 12-digit serial number.

[0014] Encrypted obfuscated ID: The central node uses an encryption algorithm to encrypt the timestamp, service number, and serial number to generate an obfuscated ID;

[0015] Returning a unique identifier: The central node returns the encrypted globally unique identifier to the edge node. The edge node receives the globally unique identifier and uses it for subsequent operations or communications.

[0016] Preferably, each time a new identifier is generated, a current timestamp (V) is calculated.

[0017] Preferably, the service number (S) is used to identify a specific service instance; in edge computing, each edge node has a unique service number to ensure the global uniqueness of the identifier.

[0018] Preferably, the sequence number (N) is used to distinguish different identifiers generated under the same timestamp and service number; the sequence number is incremented for each timestamp and service number combination, supporting identifier generation in a high-concurrency environment.

[0019] As an advantage, the timestamp is also used to detect clock rollback. Specifically, if the NTP service fails and the system clock rolls back, resulting in duplicate or disordered node IDs, before generating the node ID, check whether the current timestamp is less than the last recorded timestamp.

[0020] If so, throw an exception or wait until the time is restored to the last recorded time.

[0021] Preferably, based on the edge node, the service number generation is associated with the edge node information; specifically: each edge node is assigned a unique service number in the system, and the service number is generated based on the node's geographical location, service type or node identification to ensure uniqueness in the entire system; and then the edge node ID is used as the service number, which is less than 12 digits and is padded with 0s in front.

[0022] More preferably, when encrypting the obfuscated ID, the timestamp, service number, and serial number are concatenated to obtain the concatenated data, which is then encrypted using the SHA-256 hash algorithm to obtain a globally unique identifier, thereby improving security.

[0023] A globally unique identifier generation system under edge computing, the system comprising:

[0024] The unique identification application module is used by the edge node to send its own node ID to the central node, and then apply for a globally unique identification from the central node;

[0025] The timestamp calculation module is used to obtain the current precise time and calculate a 40-bit timestamp after the central node receives the application from the edge node;

[0026] The service number determination module is used to directly use the ID submitted by the edge node as the 12-digit service number through the central node;

[0027] The serial number acquisition and increment module is used to obtain the current serial number from the database through the central node and increment the current serial number by 1 to obtain a 12-digit serial number;

[0028] Obfuscated ID encryption module, used by the central node to encrypt the timestamp, service number and serial number using an encryption algorithm to generate an obfuscated ID;

[0029] The unique identifier returning module is used to return the encrypted global unique identifier to the edge node through the central node. The edge node receives the global unique identifier and uses it for subsequent operations or communications.

[0030] Preferably, each time a new identifier is generated, a current timestamp is calculated;

[0031] Timestamps are also used to detect clock rollback. Specifically, if NTP service failure causes the system clock to roll back, resulting in duplicate or disordered node IDs, before generating a node ID, check whether the current timestamp is less than the last recorded timestamp.

[0032] If so, throw an exception or wait until the time is restored to the last recorded time.

[0033] Preferably, the service number (S) is used to identify a specific service instance. In edge computing, each edge node has a unique service number to ensure the global uniqueness of the identifier. Based on the edge node, the service number generation is associated with the edge node information. Specifically, each edge node is assigned a unique service number in the system. The service number is generated based on the node's geographic location, service type, or node identifier to ensure uniqueness across the entire system. The edge node ID is then used as the service number. If it is less than 12 digits, the leading digits are padded with zeros.

[0034] The sequence number (N) is used to distinguish different identifiers generated under the same timestamp and service number; the sequence number increases with each timestamp and service number combination, supporting identifier generation in a high-concurrency environment.

[0035] The edge computing method and system for generating a globally unique identifier have the following advantages:

[0036] (1) The present invention uses an obfuscation algorithm and generation rule encryption to improve the security of identifiers and prevent attackers from obtaining generation strategies through pattern analysis;

[0037] (2) The present invention associates service numbers with edge computing node information for easy tracking and management. The introduction of obfuscation algorithms and generation rule encryption greatly enhances system security and prevents ID generation strategies from being maliciously analyzed and exploited. Overall, the present invention is more efficient, secure, and reliable, and is suitable for complex edge computing environments.

[0038] (3) With the vigorous development of technologies such as cloud computing and edge computing, the construction of distributed systems has become increasingly common, and the demand for globally unique identifiers has also surged. Especially in cutting-edge fields such as the Internet of Things, big data, and blockchain, the demand for efficient, reliable, and unique identifier generation solutions cannot be underestimated, which provides a broad market prospect and a huge market scale for unique identifier generation solutions. By adopting the solution of the present invention, enterprises can not only obtain efficient and reliable unique identifier generation services, but also significantly reduce the cost in the generation process. On the one hand, it avoids the waste of resources caused by repeated or incorrect generation of identifiers. On the other hand, by optimizing mechanisms such as clock synchronization and service number allocation, the generation efficiency is further improved, thereby helping enterprises reduce operating costs and achieving the significant advantages of reducing costs and increasing efficiency. In summary, the present invention has huge market potential and commercial value. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] The present invention will be further described below with reference to the accompanying drawings.

[0040] Attachment Figure 1 A flowchart of a method for generating a globally unique identifier under edge computing;

[0041] Attachment Figure 2 A globally unique identifier placeholder. DETAILED DESCRIPTION

[0042] The method and system for generating a globally unique identifier under edge computing of the present invention are described in detail below with reference to the accompanying drawings and specific embodiments of the specification.

[0043] Example 1:

[0044] As attached Figure 1As shown, this embodiment provides a method for generating a globally unique identifier under edge computing, which is specifically as follows:

[0045] S1. Apply for a unique identifier: The edge node sends its own node ID to the central node, and then applies for a globally unique identifier from the central node;

[0046] S2. Calculate timestamp: After receiving the request from the edge node, the central node obtains the current precise time and calculates a 40-bit timestamp.

[0047] S3. Determine the service number: The central node directly uses the ID submitted by the edge node as the 12-digit service number;

[0048] S4. Obtain and increment the sequence number: The central node obtains the current sequence number from the database and increments the current sequence number by 1 to obtain a 12-digit sequence number;

[0049] S5. Encrypted obfuscated ID: The central node uses an encryption algorithm to encrypt the timestamp, service number, and serial number to generate an obfuscated ID.

[0050] S6. Returning the unique identifier: The central node returns the encrypted globally unique identifier to the edge node. The edge node receives the globally unique identifier and uses it for subsequent operations or communications.

[0051] As attached Figure 2 As shown, the identifier in this embodiment consists of three parts: a timestamp, a service number, and a sequence number.

[0052] Timestamp (V): Each time a new identifier is generated, the current timestamp is calculated.

[0053] Service ID (S): Used to identify a specific service instance. In edge computing, each edge node has a unique service ID to ensure the global uniqueness of the identifier.

[0054] Sequence number (N): Used to distinguish different identifiers generated with the same timestamp and service number. The sequence number increments for each timestamp and service number combination, supporting identifier generation in highly concurrent environments.

[0055] The timestamp in this embodiment is also used to detect clock rollback. Specifically, if the NTP service fails and the system clock rolls back, resulting in duplicate or disordered node IDs, before generating a node ID, the current timestamp is checked to see if it is less than the last recorded timestamp.

[0056] If so, throw an exception or wait until the time is restored to the last recorded time.

[0057] In this embodiment, based on the edge node, the service number generation is associated with the edge node information; specifically: each edge node is assigned a unique service number in the system, and the service number is generated based on the node's geographical location, service type or node identification to ensure uniqueness in the entire system; then, the edge node ID is used as the service number, and if it is less than 12 digits, the leading 0 is used.

[0058] In this embodiment, when encrypting the obfuscated ID, the timestamp, service number and serial number are concatenated to obtain the concatenated data, which is then encrypted using the SHA-256 hash algorithm to obtain a globally unique identifier, thereby improving security.

[0059] Example:

[0060] Timestamp V = 1633072800;

[0061] Service number S = 12345;

[0062] Serial number N = 67890;

[0063] Splicing data: "1633072800_12345_67890";

[0064] Use SHA-256 encryption: SHA-256 is used to encrypt the concatenated data to obtain the obfuscated ID.

[0065] Clock synchronization optimization: Although clock rollback detection can prevent ID duplication, relying on the NTP service may present a single point of failure. This embodiment can also consider using a distributed clock synchronization algorithm, such as Raft or Paxos, to improve the reliability and stability of clock synchronization.

[0066] Encryption algorithm selection: Although SHA-256 has high security, it has high computational overhead. This embodiment can also select a lighter encryption algorithm based on actual needs to improve the efficiency and performance of ID generation.

[0067] Example 2:

[0068] This embodiment provides a system for generating a globally unique identifier in edge computing, the system including:

[0069] The unique identification application module is used by the edge node to send its own node ID to the central node, and then apply for a globally unique identification from the central node;

[0070] The timestamp calculation module is used to obtain the current precise time and calculate a 40-bit timestamp after the central node receives the application from the edge node;

[0071] The service number determination module is used to directly use the ID submitted by the edge node as the 12-digit service number through the central node;

[0072] The serial number acquisition and increment module is used to obtain the current serial number from the database through the central node and increment the current serial number by 1 to obtain a 12-digit serial number;

[0073] Obfuscated ID encryption module, used by the central node to encrypt the timestamp, service number and serial number using an encryption algorithm to generate an obfuscated ID;

[0074] The unique identifier returning module is used to return the encrypted global unique identifier to the edge node through the central node. The edge node receives the global unique identifier and uses it for subsequent operations or communications.

[0075] In this embodiment, each time a new identifier is generated, the current timestamp is calculated;

[0076] Timestamps are also used to detect clock rollback. Specifically, if NTP service failure causes the system clock to roll back, resulting in duplicate or disordered node IDs, before generating a node ID, check whether the current timestamp is less than the last recorded timestamp.

[0077] If so, throw an exception or wait until the time is restored to the last recorded time.

[0078] The service number (S) in this embodiment is used to identify a specific service instance; in edge computing, each edge node has a unique service number to ensure the global uniqueness of the identifier; based on the edge node, the service number generation is associated with the information of the edge node; specifically: each edge node is assigned a unique service number in the system, and the service number is generated based on the node's geographical location, service type or node identification to ensure uniqueness in the entire system; then the edge node ID is used as the service number, and if it is less than 12 digits, it is padded with 0s in front.

[0079] The serial number (N) in this embodiment is used to distinguish different identifiers generated under the same timestamp and service number; the serial number increases with each combination of timestamp and service number, supporting identifier generation in a high-concurrency environment.

[0080] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the above embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the above embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for generating a globally unique identifier under edge computing, characterized in that: The method is as follows: Apply for a unique identifier: The edge node sends its own node ID to the central node, and then applies for a globally unique identifier from the central node; Calculate timestamp: After receiving the request from the edge node, the central node obtains the current precise time and calculates a 40-bit timestamp; Determine the service number: The central node directly uses the ID submitted by the edge node as the 12-digit service number; Obtain and increment the serial number: The central node obtains the current serial number from the database and increments it by 1 to obtain a 12-digit serial number. Encrypted obfuscated ID: The central node uses an encryption algorithm to encrypt the timestamp, service number, and serial number to generate an obfuscated ID; Returning a unique identifier: The central node returns the encrypted globally unique identifier to the edge node. The edge node receives the globally unique identifier and uses it for subsequent operations or communications.

2. The method for generating a globally unique identifier under edge computing according to claim 1, characterized in that: Each time a new identifier is generated, the current timestamp is calculated.

3. The method for generating a globally unique identifier under edge computing according to claim 1, characterized in that: The service number is used to identify a specific service instance. In edge computing, each edge node has a unique service number to ensure the global uniqueness of the identifier.

4. The method for generating a globally unique identifier under edge computing according to claim 1, wherein: The sequence number is used to distinguish different identifiers generated under the same timestamp and service number; the sequence number increments for each timestamp and service number combination, supporting identifier generation in a high-concurrency environment.

5. The method for generating a globally unique identifier under edge computing according to claim 1, wherein: Timestamps are also used to detect clock rollback. Specifically, if NTP service failure causes the system clock to roll back, resulting in duplicate or disordered node IDs, before generating a node ID, check whether the current timestamp is less than the last recorded timestamp. If so, throw an exception or wait until the time is restored to the last recorded time.

6. The method for generating a globally unique identifier under edge computing according to claim 1, characterized in that: Based on the edge node, the service number generation is associated with the edge node information; specifically: each edge node is assigned a unique service number in the system. The service number is generated based on the node's geographical location, service type or node identification to ensure uniqueness in the entire system; then the edge node ID is used as the service number. If it is less than 12 digits, the leading 0 is used.

7. The method for generating a globally unique identifier under edge computing according to any one of claims 1 to 6, characterized in that: When encrypting the obfuscated ID, the timestamp, service number, and serial number are concatenated to obtain the concatenated data, which is then encrypted using the SHA-256 hash algorithm to obtain a globally unique identifier, thereby improving security.

8. A globally unique identifier generation system under edge computing, characterized in that: The system includes: The unique identification application module is used by the edge node to send its own node ID to the central node, and then apply for a globally unique identification from the central node; The timestamp calculation module is used to obtain the current precise time and calculate a 40-bit timestamp after the central node receives the application from the edge node; The service number determination module is used to directly use the ID submitted by the edge node as the 12-digit service number through the central node; The serial number acquisition and increment module is used to obtain the current serial number from the database through the central node and increment the current serial number by 1 to obtain a 12-digit serial number; Obfuscated ID encryption module, used by the central node to encrypt the timestamp, service number and serial number using an encryption algorithm to generate an obfuscated ID; The unique identifier returning module is used to return the encrypted global unique identifier to the edge node through the central node. The edge node receives the global unique identifier and uses it for subsequent operations or communications.

9. The edge computing globally unique identifier generation system according to claim 8, characterized in that: Every time a new identifier is generated, the current timestamp is calculated; Timestamps are also used to detect clock rollback. Specifically, if NTP service failure causes the system clock to roll back, resulting in duplicate or disordered node IDs, before generating a node ID, check whether the current timestamp is less than the last recorded timestamp. If so, throw an exception or wait until the time is restored to the last recorded time.

10. The edge computing global unique identifier generation system according to claim 8 or 9, characterized in that: The service number is used to identify a specific service instance. In edge computing, each edge node has a unique service number to ensure the global uniqueness of the identifier. Based on the edge node, the service number is generated and associated with the edge node information. Specifically, each edge node is assigned a unique service number in the system. The service number is generated based on the node's geographic location, service type, or node identifier to ensure uniqueness across the entire system. The edge node ID is then used as the service number. If it is less than 12 digits, the leading digits are padded with zeros. The sequence number is used to distinguish different identifiers generated under the same timestamp and service number; the sequence number increments for each timestamp and service number combination, supporting identifier generation in a high-concurrency environment.

Images