IPv6 address allocation and management method based on unique identifier of cross-protocol terminal

Abstract

The invention relates to the technical field of computer networks, in particular to an IPv6 address allocation and management method based on a cross-protocol terminal unique identifier, which comprises the following steps of: accessing a terminal to a network, acquiring multi-dimensional feature information in a DHCPv4 message and a DHCPv6 message, processing an acquired public feature field according to a preset rule, and sending the processed public feature field to the terminal; the method comprises the following steps of: obtaining a standardized feature sequence, carrying out address allocation of IPv6 and IPv4 by taking a TUID as a core main key, establishing logic association of the IPv6 address and the IPv4 address in an IPAM system, generating the TUID through multi-dimensional terminal feature collection, feature processing, similarity matching and hash, and realizing strong association and traceable management of the IPv4 and IPv6 addresses in a dual-stack environment by taking the TUID as a terminal main key. Dependence of DUID and MAC binding is completely got rid of, and the problem that dual stack addresses cannot be associated in creative and multi-protocol networks in a traditional method is solved.

Description

Technical Field

[0001] This invention relates to the field of computer network technology, and in particular to a method for IPv6 address allocation and management based on cross-protocol terminal unique identifiers. Background Technology

[0002] In a dual-stack environment, enterprises and government agencies need to manage both IPv4 and IPv6 addresses simultaneously. Existing technologies typically employ the following methods: IPv4 address allocation: Based on the terminal's MAC address, it is allocated via the DHCP protocol.

[0003] IPv6 address allocation: Allocation is performed via the DHCPv6 protocol, based on the terminal's DUID (DHCP Unique Identifier).

[0004] In traditional network environments, DUID is typically associated with MAC address, allowing the same terminal to be identified through both DUID and MAC. This, in turn, enables the indirect association between IPv4 and IPv6 addresses assigned to a terminal, facilitating unified management of dual-stack addresses by the IPAM system. However, in domestically developed operating systems and some enterprise equipment, the fixed association between DUID and MAC address no longer exists, and the traditional reliance on... The failure of the bound IPv4 / IPv6 address allocation and management method makes it impossible for the IPAM system to uniformly manage dual-stack addresses. This results in the inability to associate IPv4 and IPv6 addresses of the same terminal, complicating service tracing, address lookup, and management operations, increasing network operation and maintenance difficulty, and potentially affecting service continuity and security management. In summary, existing technologies cannot solve the IPv4 / IPv6 address association problem under the decoupling of DUID and MAC. Therefore, there is an urgent need for an IPv6 address allocation and management method based on cross-protocol terminal unique identifiers to solve the above problems. Summary of the Invention

[0005] In view of the deficiencies of the prior art described above, the purpose of this invention is to provide an IPv6 address allocation and management method based on cross-protocol terminal unique identifiers, which is used to solve the problem of IPv4 / IPv6 address association in the case of DUID and MAC decoupling in the prior art.

[0006] To achieve the above and other related objectives, the present invention provides the following technical solution: A method for IPv6 address allocation and management based on cross-protocol terminal unique identifiers includes the following steps: a. When a terminal accesses the network, it collects multi-dimensional feature information from DHCPv4 and DHCPv6 messages. The multi-dimensional feature information includes a core identifier as a high-weight feature, a device family identifier as a medium-weight feature, an enhanced unique identifier as a medium-low weight feature, and behavioral and metadata features as auxiliary weight features. The core identifier includes the client hostname and parameter request list. The device family identifier includes the manufacturer category identifier and hardware type. The enhanced unique identifier includes manufacturer-specific information and the client domain name. The behavioral and metadata features include lease identity association type, message statistical features, timing, and network context. b. Process the collected common feature fields according to preset rules to obtain a standardized feature sequence. The preset rules include complete field extraction, format standardization, missing data handling, and length verification. When extracting complete fields, standard fields and option content in DHCP messages are extracted first to ensure that the original values ​​are preserved. If a field does not exist in the message, it is recorded as "empty value + missing mark" to ensure that the subsequent algorithm can identify the missing state instead of discarding it directly. If the field length does not conform to the protocol specification (too short or too long), it is truncated according to the maximum legal length of the protocol and an "abnormal mark" is added. c. Calculate the weighted similarity between the standardized DHCPv4 feature sequence and the DHCPv6 feature sequence, and compare the weighted similarity with a preset threshold to determine whether they are the same terminal. d. Concatenate the DHCPv4 feature sequence and the DHCPv6 feature sequence of the same terminal, and generate a unique terminal identifier (TUID) using a two-layer hash algorithm; e. Use TUID as the core primary key to allocate IPv6 and IPv4 addresses, and establish a logical association between IPv6 and IPv4 addresses in the IPAM system.

[0007] To achieve the above technical solution, TUID is used as the terminal primary key to realize strong association and traceable management of IPv4 and IPv6 addresses in a dual-stack environment. This completely eliminates the dependency of DUID and MAC binding, solves the problem that traditional methods cannot associate dual-stack addresses in domestically developed and multi-protocol networks, and improves the intelligence and applicability of the IPAM system.

[0008] In one embodiment of the present invention, in step b, the format standardization specifically includes: unifying the extracted string or byte sequence to lowercase, removing delimiters and spaces, deleting padding bytes, and unifying the encoding method to UTF-8.

[0009] In one embodiment of the present invention, in step c, in the DHCPv4 and DHCPv6 messages of the same terminal, corresponding weights are assigned to different fields according to weight characteristics.

[0010] To implement the above technical solution, the common parameter set collected from DHCPv4 and DHCPv6 messages includes: ClientIdentifier (CID / DUID), Parameter Request List (PRL), Vendor Class Identifier (VCI), Hardware Type (HT), Vendor-Specific Information (VSI), Domain Name (DN), Identity Association Type (IAT), Packet Statistical Features (PSF), Temporal & Network. Context(TNC) yields the standardized feature sequence: Feature_Vector=[CID_norm,PRL_norm,VCI_norm,HT_norm,VSI_norm,DName_norm,IAT_norm,PSF_norm,TNC_norm]. Weights are assigned to each feature field: CID / DUID: 0.2, PRL: 0.2, VCI: 0.15, HT: 0.1, VSI: 0.1, DN: 0.1, IAT: 0.05, PSF: 0.05, TNC: 0.05.

[0011] In one embodiment of the present invention, in step c, a preset threshold is set to 0.9, and the weighted similarity calculation formula is as follows: Where Wi is the weight of the i-th feature field, and Sim(Field_v4_i,Field_v6_i) is the similarity of the corresponding feature fields of DHCPv4 and DHCPv6. If Sim(v4,v6)≥threshold T(0.9), then they are determined to be the same terminal.

[0012] In one embodiment of the present invention, step d further includes TUID calibration and update. If the terminal feature fields collected subsequently change, the system determines whether they are the same terminal based on the comparison result of weighted similarity and preset threshold, and performs TUID calibration and update based on the determination result.

[0013] To achieve the above technical solution, if the terminal feature fields collected subsequently change, but the weighted similarity is still greater than or equal to the preset threshold, it is determined to be the same terminal, and the historical feature database is updated. If the similarity is lower than the preset threshold, but the MAC address or IP address shows the same physical terminal, the calibration mode is triggered, the feature weights are readjusted, and the similarity is recalculated to avoid misjudgment.

[0014] In one embodiment of the present invention, the two-layer hash algorithm described in step d is specifically as follows: Step 1: Use the SHA-256 algorithm to perform a hash operation on the concatenated feature string to obtain the intermediate hash value H1; The second step is to use the HMAC-SHA1 algorithm to encrypt H1 with the system key as the key, and then use Base64 encoding to obtain TUID, which serves as a unique terminal identifier across protocols.

[0015] To implement the above technical solution, when the terminals are determined to be the same, the v4 and v6 feature sequences are concatenated to form a cross-protocol feature string Concat_Feature=CID_v4||CID_v6||VCI_v4||VCI_v6||.....|TNC_v6|. A two-layer hash algorithm is used to generate a unique terminal identifier TUID, where CID_v4 is the client identifier under the DHCPv4 protocol after standardization according to the "terminal feature collection rules", and CID_v6 is the client identifier under the DHCPv6 protocol after standardization according to the "terminal feature collection rules". All fields must be standardized according to the "terminal feature collection rules" before being concatenated in order to ensure that the dual-protocol data of each type of feature is included in Concat_Feature.

[0016] Step1:H1=SHA-256(Concat_Feature) Step2:TUID=Base64(HMAC-SHA1(H1,System_Secret_Key)) SHA-256: Guarantees the uniqueness and collision resistance of the input sequence.

[0017] HMAC-SHA1: Adds a system-level key to avoid identifier conflicts in cross-system environments and enhance security.

[0018] Base64: Facilitates storage and transmission.

[0019] Ultimately, a TUID is obtained, which serves as a unique terminal identifier across protocols.

[0020] In one embodiment of the present invention, in step e, when a DHCPv6 request arrives at the IPAM system, all IPv6 addresses are bound to the corresponding TUID to achieve unified management at the terminal level. The IPAM system allocates IPv6 addresses according to the terminal service type, network topology and security policy.

[0021] To achieve the above technical solution, TUID is used as the unique primary key for terminal IPv6 address allocation, without relying on the traditional MAC / DUID binding logic. The system intelligently allocates IPv6 addresses based on service type, network topology, service importance, and security policies, supporting dynamic address allocation, static binding, continuity assurance, and global optimization strategies. This enables efficient management of large-scale IPv6 networks. The system can intelligently allocate, dynamically recycle, and manage the IPv6 address pool throughout its entire lifecycle, supporting cross-data center and multi-service scenarios.

[0022] In one embodiment of the present invention, IPv6 addresses are managed on a lifecycle basis based on TUID, including address allocation, reclamation, migration and historical record archiving.

[0023] Implementing the above technical solutions will automatically generate address usage reports and traceability records, thereby improving the manageability and security of enterprise networks.

[0024] In one embodiment of the present invention, in step e, when a DHCPv4 request arrives, an IPv4 address is allocated using the same TUID as the core identifier, and a logical association is established with the IPv6 address in the IPAM system.

[0025] The above technical solution enables unified management, querying, and tracing of the same terminal in both IPv4 and IPv6 dual-stack environments, solving the address association failure problem caused by the decoupling of DUID and MAC in traditional methods.

[0026] In one embodiment of the present invention, it also includes a global IPv4 / IPv6 address mapping query based on TUID, which supports IPv4 / IPv6 address aggregation analysis by terminal, department, and business system dimensions, provides a visual management interface, displays the IPv6 address deployment status, and the IPv4 / IPv6 address association relationship.

[0027] The above technical solution provides highly reliable and available dual-stack address management capabilities, while ensuring business continuity, network security, and optimal utilization of address resources, achieving an innovative breakthrough in IPv6 network management.

[0028] As described above, this invention provides an IPv6 address allocation and management method based on cross-protocol terminal unique identifiers, which has the following beneficial effects: Through multi-dimensional terminal feature collection, feature processing, similarity matching, and hash generation of TUIDs, and by using TUIDs as terminal primary keys, a strong association and traceable management of IPv4 and IPv6 addresses in a dual-stack environment is achieved. This completely eliminates the dependency between DUID and MAC binding, solving the problem that traditional methods cannot associate dual-stack addresses in domestically developed and multi-protocol networks, and improving the intelligence and applicability of the IPAM system. The system can intelligently allocate, dynamically recycle, and manage the IPv6 address pool, supporting cross-data center and multi-service scenarios, providing highly reliable and highly available dual-stack address management capabilities, while ensuring business continuity, network security, and optimal utilization of address resources, achieving an innovative breakthrough in IPv6 network management. Attached Figure Description

[0029] Figure 1 The diagram shown is a schematic representation of the principle of the IPv6 address allocation and management method based on cross-protocol terminal unique identifiers disclosed in this embodiment of the invention. Detailed Implementation

[0030] The following specific embodiments illustrate the implementation of the present invention. Those skilled in the art can easily understand other advantages and effects of the present invention from the content disclosed in this specification.

[0031] Please see Figure 1 This invention provides a method for IPv6 address allocation and management based on cross-protocol terminal unique identifiers, comprising the following steps: When a terminal accesses the network, it collects multi-dimensional feature information from DHCPv4 and DHCPv6 messages. The multi-dimensional feature information includes a core identifier as a high-weight feature, a device family identifier as a medium-weight feature, an enhanced unique identifier as a medium-low weight feature, and behavioral and metadata features as auxiliary weight features. The core identifier includes the client hostname and parameter request list. The device family identifier includes the manufacturer category identifier and hardware type. The enhanced unique identifier includes manufacturer-specific information and the client domain name. The behavioral and metadata features include lease identity association type, message statistical features, timing, and network context. Taking a MacBook as an example, the client hostname is: The DHCPv4 request message, through the client hostname field Option12, retrieved the hostname as Jacks-MacBook-Pro. The DHCPv6 request message, through the client hostname field Option39, retrieves the v4 hostname: Jacks-MacBook-Pro, which can be customized by the user in the phone's network settings.

[0032] b. Parameter Request List Pattern DHCPv4 (Option 55): 23, 24, 39 (Request DNS server, domain name lookup list, FQDN); DHCPv6 (Option 6): 23,24,39 (Request DNS server, domain name lookup list, FQDN); In DHCPv4, this feature is carried via Option 55, and in DHCPv6, it is carried via Option 6. This is a key high-weight feature for determining if it is the same terminal (the weight is the same as the client hostname, both are 0.2).

[0033] Vendor Class Identifier, for example, for iPhone: DHCPv4(Option60): Apple; DHCPv6(Option16): Apple.

[0034] Hardware type is obtained directly from the htype field in the packet header in DHCPv4, while in DHCPv6 it needs to be resolved from the DUID-LLT link layer timestamp type DUID structure. DHCPv4 (htype field): 1 (representing Ethernet); DHCPv6 (resolved from DUID-LLT): also contains 1 (representing Ethernet).

[0035] Vendor-Specific Information: DHCPv4 (Option 125): May contain sub-options, such as {Device:CP-7841,Serial:ABC12345678}; DHCPv6 (Option 17): It may also contain {Device:CP-7841,Serial:ABC12345678}.

[0036] Client Domain Name: DHCPv4(Option15): mycompany.com; DHCPv6(Option24 or Option39): mycompany.com.

[0037] Lease and Identity Association Type: A server: In a DHCPv6 request, it will request IA_NA (non-temporary address) in the hope of obtaining a fixed IPv6 address; An employee's mobile phone might only request an IA_TA (temporary address) to obtain a temporary, more private IPv6 address.

[0038] Packet Statistical Features: A complex network device (such as a video conferencing terminal) may send a long DHCP request message containing a large number of options (such as Option125, 42, 15, etc.), and the order of the options may also follow a specific pattern.

[0039] A simple IoT sensor: its DHCP request messages are very short, containing only the most basic Options (e.g., Option 55 only requests 3 and 6).

[0040] Temporal and Network Context: Scenario: Accessing the GigabitEthernet1 / 0 / 24 port of Switch-A.

[0041] log: [T+0.000s] DHCPv4 Discover (from Host) received from port 1 / 0 / 24.

[0042] [T+0.150s] DHCPv6 Solicit (from Host) received from the same port 1 / 0 / 24.

[0043] b. Process the collected common feature fields according to preset rules to obtain a standardized feature sequence. The preset rules include complete field extraction, format standardization, missing data handling, and length verification. When extracting complete fields, standard fields and option content in DHCP messages are extracted first to ensure that the original values ​​are preserved. If a field does not exist in the message, it is recorded as "empty value + missing mark" to ensure that the subsequent algorithm can identify the missing state instead of discarding it directly. If the field length does not conform to the protocol specification (too short or too long), it is truncated according to the maximum legal length of the protocol and an "abnormal mark" is added. c. Calculate the weighted similarity between the standardized DHCPv4 feature sequence and the DHCPv6 feature sequence, and compare the weighted similarity with a preset threshold to determine whether they are the same terminal. d. Concatenate the DHCPv4 feature sequence and the DHCPv6 feature sequence of the same terminal, and generate a unique terminal identifier (TUID) using a two-layer hash algorithm; e. Use TUID as the core primary key to allocate IPv6 and IPv4 addresses, and establish a logical association between IPv6 and IPv4 addresses in the IPAM system.

[0044] By using TUID as the terminal primary key, a strong association and traceable management of IPv4 and IPv6 addresses in a dual-stack environment are achieved, completely eliminating the dependency on DUID and MAC binding. This solves the problem that traditional methods cannot associate dual-stack addresses in domestically developed and multi-protocol networks, and improves the intelligence and applicability of the IPAM system.

[0045] In step b, the format standardization specifically includes: unifying the extracted strings or byte sequences to lowercase, removing delimiters and spaces, deleting padding bytes, and unifying the encoding method to UTF-8.

[0046] In step c, in the DHCPv4 and DHCPv6 messages of the same terminal, corresponding weights are assigned to different fields according to the weight characteristics.

[0047] The common parameter set collected from DHCPv4 and DHCPv6 messages—Client Identifier (CID / DUID), Parameter Request List (PRL), Vendor Class Identifier (VCI), Hardware Type (HT), Vendor-Specific Information (VSI), Domain Name (DN), Identity Association Type (IAT), Packet Statistical Features (PSF), and Temporal & Network Context (TNC)—is used to obtain the standardized feature sequence: Feature_Vector=[CID_norm,PRL_norm,VCI_norm,HT_norm,VSI_norm,DName_norm,IAT_norm,PSF_norm,TNC_norm]. Weights are assigned to each feature field: CID / DUID: 0.2, PRL: 0.2, VCI: 0.15, HT: 0.1, VSI: 0.1, DN: 0.1, IAT: 0.05, PSF: 0.05, TNC: 0.05.

[0048] In step c, the preset threshold is set to 0.9, and the weighted similarity calculation formula is as follows: Where Wi is the weight of the i-th feature field, representing the importance of different fields in calculating similarity. For example, CID / DUID has high stability, so it is given 0.2; IAT has high variability, so it is given only 0.05. The sum of the weights = 1. Field_v4_i and Field_v6_i represent the feature fields in DHCPv4 and DHCPv6, respectively. Sim(Field_v4_i, Field_v6_i) is the similarity between the corresponding feature fields of DHCPv4 and DHCPv6, with a value range of 0 to 1. For example: if the two fields are completely the same → Sim=1; if they are partially similar (e.g., the string edit distance is very small) → Sim=0.6 (for specific calculation methods, see Similarity Calculation (partial examples)); if they are completely different → Sim=0.

[0049] Suppose the DHCPv4 and DHCPv6 fields of a certain terminal are compared as follows: Fields Similarity Sim Weight W Contribution value CID / DUID 0.9 0.2 0.18 PRL 1.0 0.2 0.20 VCI 1.0 0.15 0.15 HT 1.0 0.1 0.10 VSI 0.0 0.1 0.00 DN 0.8 0.1 0.08 IAT 1.0 0.05 0.05 PSF 1.0 0.05 0.05 TNC 1.0 0.05 0.05 Overall similarity: Sim(v4,v6)=0.18+0.20+0.15+0.10+0+0.08+0.05+0.05+0.05=0.86. If the threshold is set to 0.9, since 0.96≦0.9, it cannot be determined that they are the same terminal.

[0050] Similarity calculation: Complete consistency determination: If the contents of two fields are exactly the same: Sim=1, the method is: complete byte sequence matching, or complete UTF-8 string matching.

[0051] For partial similarity determination, in text fields, if the field is a string but not completely identical, then "edit distance similarity" is calculated using the formula: For example: A="ABCDEF" and B="ABXDEF", only one replacement is needed (replacing C with X), the edit distance is 1, the maximum length is 6, and the similarity is: Sim=1-1 / 6≈0.83.

[0052] Prefix matching, commonly found in vendor fields, is used for Vendor Class Identifier and User Class Identifier. The formula is: For example: string A (e.g., MSFT-WIN10-Clientv4), string B (e.g., MSFT-WIN10-Clientv6), common prefix length = 18, longer field length = 19, Sim = 18 / 19 ≈ 0.95.

[0053] Normalized similarity of numeric fields, used for "sets of numbers" such as parameter request lists (PRLs), is calculated by using the Jaccard similarity coefficient of the set. For example: v4PRL={1,3,6,15}, v6PRL={6,15,23}, intersection={6,15}→2, union={1,3,6,15,23}→5, Sim=2 / 5=0.4.

[0054] If Sim(v4,v6)≥threshold T(0.9), then it is determined to be the same terminal. Here, "_" is a connector symbol, indicating that this variable is composed of three parts: "field", "v6" and "i", where "i" is the variable.

[0055] Step d also includes TUID calibration and update. Specifically, if the terminal feature fields collected subsequently change, but the weighted similarity is still greater than or equal to the preset threshold T, it is determined to be the same terminal, and the historical feature database is updated. If the similarity is lower than the preset threshold, but the MAC address or IP address shows the same physical terminal, the calibration mode is triggered, the feature weights are readjusted, and the similarity is recalculated to avoid misjudgment.

[0056] The two-level hash algorithm described in step d is as follows: Step 1: Use the SHA-256 algorithm to perform a hash operation on the concatenated feature string to obtain the intermediate hash value H1; The second step is to use the HMAC-SHA1 algorithm to encrypt H1 with the system key as the key, and then use Base64 encoding to obtain TUID, which serves as a unique terminal identifier across protocols.

[0057] When the same terminal is identified, the v4 and v6 feature sequences are concatenated to form a cross-protocol feature string Concat_Feature=CID_v4||CID_v6||VCI_v4||VCI_v6||.....|TNC_v6|. A two-layer hash algorithm is used to generate a unique terminal identifier TUID, where CID_v4 is the client identifier under the DHCPv4 protocol after standardization according to the "terminal feature collection rules", and CID_v6 is the client identifier under the DHCPv6 protocol after standardization according to the "terminal feature collection rules". All fields must be standardized according to the "terminal feature collection rules" before being concatenated in order to ensure that the dual-protocol data of each type of feature is included in Concat_Feature.

[0058] Step1:H1=SHA-256(Concat_Feature) Step2:TUID=Base64(HMAC-SHA1(H1,System_Secret_Key)) SHA-256: Guarantees the uniqueness and collision resistance of the input sequence.

[0059] HMAC-SHA1: Adds a system-level key to avoid identifier conflicts in cross-system environments and enhance security.

[0060] Base64: Facilitates storage and transmission.

[0061] Ultimately, a TUID is obtained, which serves as a unique terminal identifier across protocols.

[0062] In step e, when a DHCPv6 request arrives at the IPAM system, all IPv6 addresses are bound to the corresponding TUID, achieving unified management at the terminal level. The IPAM system allocates IPv6 addresses based on the terminal service type, network topology, and security policy.

[0063] TUID is used as a unique primary key for terminal IPv6 address allocation, without relying on the traditional MAC / DUID binding logic. The system achieves intelligent IPv6 address allocation based on service type, network topology, service importance, and security policies. It supports dynamic address allocation, static binding, continuity assurance, and global optimization strategies, enabling efficient management of large-scale IPv6 networks. The system can perform intelligent policy allocation, dynamic recycling, and full lifecycle management of the IPv6 address pool, supporting cross-data center and multi-service scenarios.

[0064] Based on TUID, IPv6 addresses are managed throughout their lifecycle, including address allocation, reclamation, migration, and historical record archiving. Address usage reports and traceability records are automatically generated, improving the manageability and security of enterprise networks.

[0065] In step e, when a DHCPv4 request arrives, an IPv4 address is assigned using the same TUID as the core identifier, and a logical association is established with the IPv6 address in the IPAM system.

[0066] This enables unified management, querying, and tracing of the same terminal in both IPv4 and IPv6 dual-stack environments, resolving the address association failure problem caused by the decoupling of DUID and MAC in traditional methods.

[0067] It also includes a global IPv4 / IPv6 address mapping query based on TUID, supports IPv4 / IPv6 address aggregation analysis by terminal, department, and business system, provides a visual management interface to display the IPv6 address deployment status and IPv4 / IPv6 address relationships.

[0068] It provides highly reliable and available dual-stack address management capabilities, while ensuring business continuity, network security, and optimal utilization of address resources, achieving an innovative breakthrough in IPv6 network management.

[0069] This invention achieves strong association and traceable management of IPv4 and IPv6 addresses in a dual-stack environment by collecting, processing, matching, and hashing multi-dimensional terminal features, similarity matching, and hashing. By using TUID as the terminal primary key, it completely eliminates the dependency of DUID and MAC binding, solves the problem that traditional methods cannot associate dual-stack addresses in domestically developed and multi-protocol networks, and improves the intelligence and applicability of the IPAM system.

[0070] The system can intelligently allocate, dynamically recycle, and manage the IPv6 address pool throughout its entire lifecycle. It supports cross-data center and multi-service scenarios, providing highly reliable and highly available dual-stack address management capabilities. At the same time, it ensures business continuity, network security, and optimal utilization of address resources, achieving an innovative breakthrough in IPv6 network management.

[0071] The above embodiments are merely illustrative of the principles and effects of the present invention and are not intended to limit the invention. Any person skilled in the art can modify or alter the above embodiments without departing from the spirit and scope of the present invention. Therefore, all equivalent modifications or alterations made by those skilled in the art without departing from the spirit and technical concept disclosed in the present invention should still be covered by the claims of the present invention.

Claims

1. A method for IPv6 address allocation and management based on cross-protocol terminal unique identifiers, characterized in that, Includes the following steps: a. When a terminal accesses the network, it collects multi-dimensional feature information from DHCPv4 and DHCPv6 messages. The multi-dimensional feature information includes a core identifier as a high-weight feature, a device family identifier as a medium-weight feature, an enhanced unique identifier as a medium-low weight feature, and behavioral and metadata features as auxiliary weight features. The core identifier includes the client hostname and parameter request list. The device family identifier includes the manufacturer category identifier and hardware type. The enhanced unique identifier includes manufacturer-specific information and the client domain name. The behavioral and metadata features include lease identity association type, message statistical features, timing, and network context. b. Process the collected common feature fields according to preset rules to obtain a standardized feature sequence. The preset rules include complete field extraction, format standardization, missing data handling, and length verification. c. Calculate the weighted similarity between the standardized DHCPv4 feature sequence and the DHCPv6 feature sequence, and compare the weighted similarity with a preset threshold to determine whether they are the same terminal. d. Concatenate the DHCPv4 feature sequence and the DHCPv6 feature sequence of the same terminal, and generate a unique terminal identifier (TUID) using a two-layer hash algorithm; e. Use TUID as the core primary key to allocate IPv6 and IPv4 addresses, and establish a logical association between IPv6 and IPv4 addresses in the IPAM system.

2. The method for IPv6 address allocation and management based on cross-protocol terminal unique identifiers according to claim 1, characterized in that, In step b, the format standardization specifically includes: unifying the extracted strings or byte sequences to lowercase, removing delimiters and spaces, deleting padding bytes, and unifying the encoding method to UTF-8.

3. The IPv6 address allocation and management method based on cross-protocol terminal unique identifiers according to claim 1, characterized in that, In step c, in the DHCPv4 and DHCPv6 messages of the same terminal, corresponding weights are assigned to different fields according to the weight characteristics.

4. The method for IPv6 address allocation and management based on cross-protocol terminal unique identifiers according to claim 1, characterized in that, In step c, the preset threshold is set to 0.9, and the weighted similarity calculation formula is as follows: Where Wi is the weight of the i-th feature field, and Sim(Field_v4_i,Field_v6_i) is the similarity of the corresponding feature fields of DHCPv4 and DHCPv6. If Sim(v4,v6)≥threshold T(0.9), then they are determined to be the same terminal.

5. The method for IPv6 address allocation and management based on cross-protocol terminal unique identifiers according to claim 1, characterized in that, In step d, TUID calibration and update are also included. If the terminal feature fields collected subsequently change, the comparison results of weighted similarity and preset threshold are used to determine whether they are the same terminal, and TUID calibration and update are performed based on the determination results.

6. The method for IPv6 address allocation and management based on cross-protocol terminal unique identifiers according to claim 1, characterized in that, The two-level hash algorithm described in step d is specifically as follows: Step 1: Use the SHA-256 algorithm to perform a hash operation on the concatenated feature string to obtain the intermediate hash value H1; The second step is to use the HMAC-SHA1 algorithm to encrypt H1 with the system key as the key, and then use Base64 encoding to obtain TUID, which serves as a unique terminal identifier across protocols.

7. The method for IPv6 address allocation and management based on cross-protocol terminal unique identifiers according to claim 1, characterized in that, In step e, when a DHCPv6 request arrives at the IPAM system, all IPv6 addresses are bound to the corresponding TUID, achieving unified management at the terminal level. The IPAM system allocates IPv6 addresses based on the terminal service type, network topology, and security policy.

8. The method for IPv6 address allocation and management based on cross-protocol terminal unique identifiers according to claim 6, characterized in that, TUID is used to manage the lifecycle of IPv6 addresses, including address allocation, reclamation, migration, and historical record archiving.

9. The method for IPv6 address allocation and management based on cross-protocol terminal unique identifiers according to claim 1, characterized in that, In step e, when a DHCPv4 request arrives, an IPv4 address is assigned using the same TUID as the core identifier, and a logical association is established with the IPv6 address in the IPAM system.

10. The method for IPv6 address allocation and management based on cross-protocol terminal unique identifiers according to claim 1, characterized in that, It also includes a global IPv4 / IPv6 address mapping query based on TUID, supports IPv4 / IPv6 address aggregation analysis by terminal, department, and business system, provides a visual management interface to display the IPv6 address deployment status and IPv4 / IPv6 address relationships.

Images