Link local IPv6 address automatic configuration method

Abstract

The invention discloses a link local IPv6 address automatic configuration method, and belongs to the technical field of communication. The method comprises the following steps: firstly, acquiring position information of satellite nodes in a constellation, forming a unique satellite node configuration triple for each satellite node, and acquiring an interface code of each interface of the satellite node; then, a link local IPv6 address is automatically generated based on constellation configuration, satellite node position information and spacecraft information; and finally, automatic configuration and uniqueness guarantee of the local IPv6 address of the link are carried out. The address generated by the method supports accurate identification of satellite node position information, uniqueness of the address can be guaranteed, automatic configuration efficiency is improved, and the method is suitable for any type of links of a satellite network, including an AOS link and an Ethernet link.

Description

Technical Field

[0001] The present invention belongs to the field of communication technology, and in particular relates to a link-local IPv6 address automatic configuration method. Background Art

[0002] Stateless Address Autoconfiguration (SLAAC) is a key feature of IPv6 network autoconfiguration. It automatically generates link-local IPv6 addresses, enabling plug-and-play local communication. Link-local IPv6 addresses can be used for communication between nodes on the same link (e.g., file sharing and routing protocols).

[0003] RFC 4291, "IPv6 Addressing Architecture," defines the global structure of IPv6 addresses, including the FE80:: / 10 prefix for link-local IPv6 addresses. It also specifies the EUI-64 format for generating interface identifiers (IIDs). This method uses MAC address expansion to generate the last 64 bits of the address. For example, the 48-bit MAC address is split into two parts, with FFFE inserted between them. The seventh bit, the U / L bit, is then inverted. This creates a 64-bit interface ID. This is then combined with the link-local prefix to form a complete IPv6 address.

[0004] RFC 4862 - "IPv6 Stateless Address Autoconfiguration" describes the process of automatically generating link-local IPv6 addresses without the need for Dynamic Host Configuration Protocol version 6 (DHCPv6).

[0005] RFC 7217 - "A Method for Generating Semantically Opaque Interface Identifiers" proposes an interface ID generation method (such as randomization and cryptographic hashing) to replace EUI-64 to enhance privacy protection, but EUI-64 remains the default method for generating link-local IPv6 addresses.

[0006] However, satellite network interfaces typically use microwave and laser links, and the link layer protocol uses the CCSDS Advanced Operating System (AOS) protocol. The AOS protocol lacks MAC addresses, and the randomly generated interface IDs can conflict. Unique IP addresses at both ends of a link cannot be guaranteed, leading to IP address conflicts. Manually configuring interface IPv6 addresses would be prohibitively complex given the tens of thousands of satellites in the LEO constellation.

[0007] Therefore, a method is needed to automatically generate link-local IPv6 addresses that does not rely on the traditional SLAAC mechanism, has topological stability, automatic uniqueness guarantee, and supports any link type in satellite constellation networks. Summary of the Invention

[0008] This paper addresses the poor adaptability and automation of existing link-local IPv6 address configuration methods in satellite networks. This paper proposes an automatic link-local IPv6 address configuration method based on constellation configuration, satellite node location information, and spacecraft identification. The generated addresses feature a clear structure, reversible mapping, and global uniqueness. Without requiring MAC addresses or random numbers, a unique address is generated for each node interface. This method is applicable to various satellite link environments and meets the requirements for automated configuration and efficient management of large-scale constellation networks.

[0009] A link-local IPv6 address automatic configuration method is disclosed. The method automatically configures link-local IPv6 addresses based on constellation configuration, satellite node location information, and spacecraft information. The method is applicable to any type of link in a satellite network, including AOS links and Ethernet links. The constellation configuration consists of a constellation type, a constellation number, and a mission number. The constellation type refers to the orbital category of the satellite network and is derived from the classification of orbital types in a mission planning system. The constellation number is in decimal format, consists of three digits, and is uniformly assigned by a constellation design and operation and maintenance platform. The mission number is in English abbreviation form, indicating a specific mission type and is defined by a mission scheduling system. The spacecraft information refers to a spacecraft identifier, which is a unique number of a satellite-type spacecraft and is used to identify each satellite node in the orbital constellation. Preferably, the Spacecraft_ID assigned by the CCSDS organization is used as the source of the unique spacecraft identifier. The method specifically comprises the following steps: S1. Obtain the location information of the satellite node in the constellation, including the orbital layer number shell_id, orbit number orbit_id, and satellite node number sat_id in the orbital plane. Form a unique satellite node configuration triplet [shell_id, orbit_id, sat_id] for each satellite node, and obtain the interface code dir of each interface of the satellite node. The interface code is used to uniquely identify different interfaces of the satellite, including interfaces between satellites in the same orbit, interfaces between satellites in different orbits, and inter-layer interfaces. S2: Automatically generate link-local IPv6 addresses based on constellation configuration, satellite node location information, and spacecraft information: S2.1 The link-local IPv6 address is 128 bits long and is divided into eight fields, each of which occupies 16 bits. These fields are named Field 1 through Field 8. Fields 1 through 4 are fixed as the link-local IPv6 address prefix, and Fields 5 through 8 are the link-local interface identifier (IID). S2.2 Generate a link-local IPv6 address prefix: fix the values of fields 1 to 4 to FE80:0:0:0; S2.3 Generate a link-local interface identifier IID: Field 5 stores the hash value of the constellation configuration. The constellation configuration consists of the constellation type, constellation number, and mission number. These three are sequentially connected with a hyphen "-" to form the constellation configuration identification string "constellation type-constellation number-mission number". This string is then hashed using the standard hash function CRC-16 to obtain a 16-bit hash value, which is entered into Field 5. Field 6 stores the orbital layer number shell_id, orbit number orbit_id, and satellite node number sat_id in the orbital plane; the interface code dir is stored in the last 4 bits of field 8; The remaining fields of field 7 and field 8 store spacecraft information, and the Spacecraft_ID is padded on the right with 0 to 28 bits to fill in the remaining fields of field 7 and field 8 to generate the link local interface identifier IID; S2.4 Generate a link-local IPv6 address: The link-local IPv6 address prefix is concatenated with the link-local interface identifier IID to generate the link-local IPv6 address interface_ip.

[0010] S2.5 interface_ip maps the satellite node configuration triple [shell_id, orbit_id, sat_id] and the interface code dir: Interface_ip can map the satellite node location information and interface code dir. By extracting the first two bits of field 6 in interface_ip, the orbital layer number shell_id of the satellite node can be obtained. By extracting the last p bits of field 6 in interface_ip, the satellite node number sat_id in the orbital plane of the satellite node can be obtained. By extracting the middle 14-p bits of field 6 in interface_ip, the orbital number orbit_id of the satellite node can be obtained. By extracting the last 4 bits of field 8 in interface_ip, the interface code of each interface of the satellite node can be obtained.

[0011] Therefore, the link-local IPv6 address can be used to map the satellite node configuration triple [shell_id, orbit_id, sat_id] and interface code dir of the satellite node, thereby accurately identifying the location and interface information of the satellite node. Extracting field 5 can obtain the constellation configuration, and extracting field 7 and the rest of field 8 can obtain spacecraft related information.

[0012] S3. Link-local IPv6 address auto-configuration and uniqueness guarantee: When a satellite node cold starts, changes its interface status, or adjusts its orbit, the link-local IPv6 address autoconfiguration method in step S2 is automatically executed. The interface_ip in step S2.4 is assigned to the link-local interface and directly marked as preferred. The IPv6 network protocol stack duplicate address detection process is omitted. The interface_ip can then be used for neighbor discovery and control plane configuration of the neighbor cache, and can also directly participate in IPv6 routing protocol communications. S3.1 Address State Lifecycle Management The link-local IPv6 address is generated based on the constellation configuration, the satellite node configuration triple [shell_id, orbit_id, sat_id] and the spacecraft identifier, and is persistent and stable. The system regularly performs neighbor unreachability detection on neighbors. When the detection result shows that the neighbor is unreachable, the system marks it as unreachable. At this time, if one of the link status changes, orbit adjustments, and satellite node restart events occurs, the system will automatically re-execute the address generation and configuration process to quickly restore neighbor reachability, and has good autonomy and rapid recovery capabilities.

[0013] S3.2 Analysis of Link-Local IPv6 Address Uniqueness The link-local IPv6 address generated in step S2 consists of the following two parts: The address prefix, that is, fields 1 to 4, is fixed at FE80:0:0:0 and is used to identify the link-local scope. The interface identifier part, i.e., fields 5 to 8, includes the constellation configuration, satellite node configuration triplet [shell_id, orbit_id, sat_id], interface code dir, and spacecraft information; From the result design level, through the unique location information, constellation configuration, and spacecraft identification of each satellite node, each interface is unique within the local node, preventing link-local interface identifier (IID) conflicts and ensuring the uniqueness of the link-local IPv6 address.

[0014] Beneficial effects

[0015] 1. The present invention provides a method for automatically configuring link-local IPv6 addresses based on satellite node location information and spacecraft information. By embedding the satellite node's orbital layer number, orbit number, satellite node number within the orbit, interface, constellation configuration, and spacecraft identifier, a unique interface identifier is constructed to ensure that the link-local IPv6 address corresponding to each node and each interface is unique across the entire network. This eliminates the need for duplicate address detection in the traditional IPv6 network protocol stack, reduces protocol overhead, improves configuration efficiency and reliability, and supports bidirectional mapping of addresses to node information, thereby enhancing the management capabilities of large-scale satellite networks.

[0016] 2. The present invention does not rely on MAC addresses and management servers. Satellite nodes can automatically generate link-local IPv6 addresses when their status changes, meeting the plug-and-play requirements of large-scale constellation networks. Combined with the neighbor unreachable detection mechanism, it automatically reconfigures addresses and restores communications when any of the following events occur: link status changes, orbit adjustments, or satellite node restarts. It has good autonomy and fault tolerance and is applicable to various link types including the AOS protocol, laser links, and Ethernet, solving the problem of limited automatic address generation in a MAC-free environment. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 It is an overall solution for link-local IPv6 address autoconfiguration; Figure 2 The link-local interface identifier IID is automatically generated; Figure 3 The link-local IPv6 address is automatically generated; Figure 4 This is an example of automatic generation of a link-local IPv6 address. DETAILED DESCRIPTION

[0018] To further clarify the objectives, technical solutions, and advantages of the present invention, a detailed description of an embodiment of the present invention is provided, using a two-layer 10×10 low-orbit satellite constellation network consisting of 200 LEO satellite nodes as an example, and a 10×10 layer of 100 LEO satellite nodes close to the ground as an example. This embodiment is implemented based on the technical solutions of the present invention, and provides a detailed implementation method and specific operating procedures. The specific examples described herein are merely for illustrative purposes, and the scope of protection of the present invention is not limited to the following embodiments.

[0019] S1. Obtain the location information of the satellite node in the constellation, including the orbital layer number shell_id, orbit number orbit_id, and satellite node number sat_id in the orbital plane. Form a unique satellite node configuration triplet [shell_id, orbit_id, sat_id] for each satellite node, and obtain the interface code dir of each interface of the satellite node. The interface code is used to uniquely identify different interfaces of the satellite, including interfaces between satellites in the same orbit, interfaces between satellites in different orbits, and inter-layer interfaces. In this embodiment, a 10×10 layer of 100 LEO satellite nodes close to the ground is defined as the first layer, and a layer of LEO satellite nodes far from the ground is defined as the second layer. The position information of the satellite nodes in the first layer in the constellation and the interface code dir of each interface are obtained. It is defined that each satellite node in the first layer has 6 interfaces, including two interfaces between satellites in the same orbit, int-1 and int-2, two interfaces between satellites in different orbits, int-3 and int-4, and two inter-layer interfaces, int-up and int-down. The interfaces between satellites in the same orbit include an interface int-1 in the along-orbit direction and an interface int-2 in the opposite-orbit direction, with interface codes dir of 1 and 2, respectively. The interfaces between satellites in different orbits include an interface int-3 on the left side of the orbit and an interface int-4 on the right side of the orbit, with interface codes dir of 3 and 4, respectively. The inter-layer interfaces include an interface int-up connecting to the upper orbit and an interface int-down connecting to the ground, with interface codes dir of 5 and 6, respectively. The obtained position information and interface codes of some satellite nodes in the constellation are listed in Table 1: Table 1 Location information and interface codes of some satellite nodes

[0020] S2: Automatically generate link-local IPv6 addresses based on constellation configuration, satellite node location information, and spacecraft information: S2.1 The link-local IPv6 address is 128 bits long and is divided into 8 fields, each of which occupies 16 bits. They are named field 1 to field 8. Fields 1 to 4 are fixed as the link-local IPv6 address prefix, and fields 5 to 8 are the link-local interface identifiers (IIDs). Figure 1 As shown; S2.2 Generate a link-local IPv6 address prefix: fix the values of fields 1 to 4 to FE80:0:0:0; S2.3 Generate a link-local interface identifier IID: Map the satellite node configuration triple [shell_id, orbit_id, sat_id] to the link local interface identifier IID: As attached Figure 2 As shown, the link-local interface identifier (IID) is a 64-bit address. The first two 16 bits of the IID correspond to fields 5 and 6 of the link-local IPv6 address, respectively, and the last two 16 bits correspond to fields 7 and 8 of the link-local IPv6 address, respectively. Field 5 stores the hash value of the constellation configuration. The constellation configuration consists of the constellation type, constellation number, and mission number. These three are sequentially concatenated with a hyphen (-) to form the constellation configuration identification string "constellation type-constellation number-mission number". This string is then hashed using the standard hash function CRC-16 to obtain a 16-bit hash value, which is then entered into Field 5. In this embodiment, LEO is used to represent the constellation type, 001 is used to represent the constellation number, and COM is used to represent the mission number. These three are sequentially concatenated with a hyphen (-) to form the constellation configuration identification string "LEO-001-COM". This is then compressed into 16 bits using the standard hash function CRC-16 and entered into Field 5. In this embodiment, abcd is used to fill in Field 5 for illustrative purposes only; the actual value is generated based on the system configuration. Field 6 stores the shell_id, orbital number orbit_id, and satellite node number sat_id within the orbital plane. The shell_id bit width is 2 bits; in this embodiment, the orbit_id bit width is 6 bits, and the sat_id bit width is 8 bits. The interface code dir is stored in the last 4 bits of field 8. The remaining fields of field 8 and field 7 store spacecraft information. In this embodiment, the remaining fields of field 8 are set to 0, and 1a2b is used as field 7 to refer to spacecraft information. This is for illustration only; the actual value is generated based on the system configuration. This generates the link-local interface identifier IID. For example, the satellite node configuration triplet [shell_id, orbit_id, sat_id] is [1,3,5], and the interface code dir is 1,2,3,4,5,6. Convert shell_id to hexadecimal and fill in the first 2 bits of field 6: 01; Convert orbit_id to hexadecimal and fill in the middle 6 bits of field 6: 000011; Convert sat_id to hexadecimal and fill in the last 8 bits of field 6: 00000101; Convert dir to hexadecimal and fill in the last 4 bits of field 8: 0001, 0010, 0011, 0100, 0101, 0110; Therefore, if field 6 is filled with 0100001100000101, the corresponding hexadecimal value is 0x4305. If field 6 is filled with 4305, the IID of the satellite interface j is abcd:4305:1a2b:j, where the value range of j is dir, as shown in the attached figure. Figure 4 shown.

[0021] Examples of link-local interface identifiers (IIDs) are shown in Table 2.

[0022] Table 2 Examples of link-local interface identifiers (IIDs)

[0023] For example, the six interfaces of a satellite node with a satellite node configuration triplet of [1,3,5] are the interfaces int-1 and int-2 between satellites in the same orbit, int-3 and int-4 between satellites in different orbits, and int-up and int-down between layers. The corresponding dirs are 1, 2, 3, 4, 5, and 6 respectively. According to the above-mentioned link local interface identifier IID generation method, the link local interface identifiers IID of the six interfaces of the satellite node are obtained as listed in Table 3.

[0024] Table 3 Link local interface identifier IID of satellite nodes at [1,3,5]

[0025] S2.4 Generate a link-local IPv6 address: The link-local IPv6 address prefix is concatenated with the link-local interface identifier IID to generate the link-local IPv6 address interface_ip, as shown in the attached figure. Figure 3 shown.

[0026] Table 4 shows an example of the link-local IPv6 address interface_ip.

[0027] Table 4 Example of link-local IPv6 address interface_ip

[0028] For example, for a satellite node with a satellite node configuration triplet of [1,3,5], the link-local IPv6 address prefix and the link-local interface identifier IID are concatenated end to end, as shown in the attached figure. Figure 4 As shown, the link-local IPv6 addresses of the six interfaces of the satellite node are obtained as listed in Table 5.

[0029] Table 5 Link-local IPv6 addresses of each interface of the satellite node at [1,3,5]

[0030] S2.5 interface_ip maps the satellite node configuration triple [shell_id, orbit_id, sat_id] and the interface code dir: For example, the link-local IPv6 address interface_ip of a satellite node is FE80:0:0:0:abcd:460A:1a2b:1: Extracting the first 2 bits of field 6 yields:

[0031] Extracting the middle 6 bits of field 6 yields:

[0032] Extracting the last 8 bits of field 6 yields:

[0033] The configuration triplet of the satellite node is [1,6,10]; By extracting the last 4 bits of field 8, it can be obtained that the interface is an interface in the same track and along the track direction.

[0034] Therefore, according to interface_ip, the unique satellite node configuration triple [shell_id, orbit_id, sat_id] and interface code dir of the satellite node in the network topology can be obtained.

[0035] S3, Link-local IPv6 address automatic configuration and uniqueness guarantee When a satellite node cold start, interface status change, or orbit adjustment occurs, the link-local IPv6 address automatic configuration method in step S2 is automatically executed. The interface_ip described in step S2.4 is configured to the link-local interface and directly marked as the preferred state, omitting the traditional IPv6 network protocol stack duplicate address detection process.

[0036] Taking the satellite node configuration triplet [1,3,5] as an example, the link-local IPv6 addresses corresponding to the six interfaces of the node are defined in S2 as listed in Table 4. The addresses in Table 4 will be written into the interface address list, as listed in Table 6: Table 6 Satellite node interface address list at [1,3,5]

[0037] This address can then be used for neighbor discovery and control plane configuration neighbor cache, and can also directly participate in IPv6 routing protocol communications including OSPFv3, Babel, and BGP.

[0038] S3.1 Address State Lifecycle Management The link-local IPv6 address generated by this method is based on the constellation configuration, the satellite node configuration triplet [shell_id, orbit_id, sat_id] and the spacecraft identifier, and is persistent and stable. The system regularly performs neighbor unreachability checks on neighbors. When the test result indicates that the neighbor is unreachable, the system marks it as unreachable. At this time, if any of the link status changes, orbit adjustments, and satellite node restart events occur, the system will automatically re-execute the address generation and configuration process to quickly restore neighbor reachability, and has good autonomy and rapid recovery capabilities.

[0039] S3.2 Analysis of Link-Local IPv6 Address Uniqueness The link-local IPv6 address generated in step S2 consists of the following two parts: The address prefix, that is, fields 1 to 4, is fixed as FE80:0:0:0 and is used to identify the link-local scope.

[0040] The interface identifier part, i.e., fields 5 to 8, includes the constellation configuration, satellite node configuration triplet [shell_id, orbit_id, sat_id], interface code dir, and spacecraft information.

[0041] Each satellite in a constellation has a unique configuration triplet [shell_id, orbit_id, sat_id]; each interface code dir is unique within the local node; each satellite has a unique spacecraft identifier; and each constellation has a unique constellation configuration. Therefore, the structural design prevents the possibility of IID conflicts, and link-local IPv6 addresses are globally unique.

Claims

1. A link-local IPv6 address automatic configuration method, characterized in that: Automatically configure link-local IPv6 addresses based on constellation configuration, satellite node location information, and spacecraft information, applicable to any type of satellite network link, including AOS links and Ethernet links. The constellation configuration consists of a constellation type, a constellation number, and a mission number. The constellation type refers to the orbital category of the satellite network and is derived from the classification of orbital types in the mission planning system. The constellation number is in decimal format, consisting of three digits and uniformly assigned by the constellation design and operation and maintenance platform. The mission number is in English abbreviation form, indicating the specific mission type and is defined by the mission scheduling system. The spacecraft information refers to the spacecraft identifier, which is a unique number of a satellite-type spacecraft and is used to identify each satellite node in the orbital constellation. The method comprises the following steps: S1. Obtain the location information of the satellite node in the constellation, including the orbital layer number shell_id, orbit number orbit_id, and satellite node number sat_id in the orbital plane. Form a unique satellite node configuration triplet [shell_id, orbit_id, sat_id] for each satellite node, and obtain the interface code dir of each interface of the satellite node. The interface code is used to uniquely identify different interfaces of the satellite, including interfaces between satellites in the same orbit, interfaces between satellites in different orbits, and inter-layer interfaces. S2, automatically generates link-local IPv6 addresses based on constellation configuration, satellite node location information, and spacecraft information; S3. Automatic configuration and uniqueness guarantee of link-local IPv6 addresses.

2. The link-local IPv6 address automatic configuration method according to claim 1, characterized in that: The spacecraft information described above uses the Spacecraft_ID assigned by the CCSDS organization as the source of the unique spacecraft identification.

3. The link-local IPv6 address automatic configuration method according to claim 1, wherein: The specific process of step S2 is as follows: S2.1 The link-local IPv6 address is 128 bits long and is divided into eight fields, each of which occupies 16 bits. These fields are named Field 1 through Field 8. Fields 1 through 4 are fixed as the link-local IPv6 address prefix, and Fields 5 through 8 are the link-local interface identifier (IID). S2.2 Generate a link-local IPv6 address prefix: fix the values of fields 1 to 4 to FE80:0:0:0; S2.3 Generate a link-local interface identifier IID: Field 5 stores the hash value of the constellation configuration. The constellation configuration consists of the constellation type, constellation number, and mission number. These three are sequentially connected with a hyphen "-" to form the constellation configuration identification string "constellation type-constellation number-mission number". This string is then hashed using the standard hash function CRC-16 to obtain a 16-bit hash value, which is entered into Field 5. Field 6 stores the orbital layer number shell_id, orbit number orbit_id, and satellite node number sat_id in the orbital plane; the interface code dir is stored in the last 4 bits of field 8; The remaining fields of field 7 and field 8 store spacecraft information, and the Spacecraft_ID is padded on the right with 0 to 28 bits to fill in the remaining fields of field 7 and field 8 to generate the link local interface identifier IID; S2.4 Generate a link-local IPv6 address: Concatenate the link-local IPv6 address prefix with the link-local interface identifier IID to generate the link-local IPv6 address interface_ip; S2.5 interface_ip maps the satellite node configuration triple [shell_id, orbit_id, sat_id] and the interface code dir.

4. The link-local IPv6 address automatic configuration method according to claim 3, characterized in that: The interface_ip mapping described in step S2.5 to the satellite node configuration triple [shell_id, orbit_id, sat_id] and the interface code dir can reflect the satellite node configuration triple [shell_id, orbit_id, sat_id] and the interface code dir of the satellite node in the constellation from the link-local IPv6 address, that is, it can parse the orbital layer number shell_id, orbit number orbit_id, satellite node number sat_id in the orbital plane, and interface information of the satellite node corresponding to any link-local IPv6 address.

5. The link-local IPv6 address automatic configuration method according to claim 3, characterized in that: The specific process of step S3 is as follows: When a satellite node cold starts, changes its interface status, or adjusts its orbit, the link-local IPv6 address autoconfiguration method in step S2 is automatically executed. The interface_ip in step S2.4 is assigned to the link-local interface and directly marked as preferred. The IPv6 network protocol stack duplicate address detection process is omitted. The interface_ip can then be used for neighbor discovery and control plane configuration of the neighbor cache, and can also directly participate in IPv6 routing protocol communications. S3.1 Address state lifecycle management: The link-local IPv6 address is generated based on the constellation configuration, the satellite node configuration triple [shell_id, orbit_id, sat_id], and the spacecraft identifier. The system regularly performs neighbor unreachability checks on neighbors. When the test result indicates that the neighbor is unreachable, the system marks it as unreachable. At this time, if any of the link status changes, orbit adjustments, and satellite node restart events occur, the system will automatically re-execute the address generation and configuration process to quickly restore neighbor reachability. S3.2 Link-local IPv6 address uniqueness analysis: The link-local IPv6 address generated in step S2 consists of the following two parts: The address prefix, that is, fields 1 to 4, is fixed at FE80:0:0:0 and is used to identify the link-local scope. The interface identifier part, i.e., fields 5 to 8, includes the constellation configuration, satellite node configuration triplet [shell_id, orbit_id, sat_id], interface code dir, and spacecraft information.

Images