Ipv6 source address programming information notification method, and ipv6 source address programming capability notification method

Abstract

Embodiments of the present disclosure provide an IPv6 source address programming information notification method, and an IPv6 source address programming capability notification method. A second node receives, from a first node, by means of an IGP, a notification concerning IPv6 source address programming information, and constructs an IPv6 source address programming information table on the basis of the IPv6 source address programming information; and the second node receives a service packet from the first node, and parses the service packet on the basis of the IPv6 source address programming information table, so as to obtain the IPv6 source address programming information.

Description

Methods for announcing IPv6 source address programming information and programming capabilities

[0001] Cross-reference to related applications

[0002] This disclosure is based on and claims priority to Chinese patent application CN202410506371.0, filed on April 25, 2024, entitled “Method for announcing IPv6 source address programming information and programming capabilities”, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This disclosure relates to the field of communications, and more specifically, to a method for announcing IPv6 source address programming information and programming capabilities. Background Technology

[0004] In related technologies, when controllers or devices calculate IPv6 source address slicing paths, they may not know whether the device supports IPv6 source address slicing. Therefore, they might calculate paths for devices that do not support IPv6 source address slicing, leading to service disruption. The fixed location and length of slice information in IPv6 source addresses cannot meet the needs of flexible deployment. To determine whether an IPv6 source address carries slice information, all dedicated IPv6 address prefixes for each slice need to be configured on all nodes in the network. This involves a large amount of configuration, poor scalability, and is prone to omissions when adding or deleting entries.

[0005] In summary, among the related technologies, the methods for announcing IPv6 source address programming capabilities and programming information suffer from complex processes and poor user experience. Summary of the Invention

[0006] This disclosure provides a method for announcing IPv6 source address programming information and programming capabilities, at least to solve the problems of complex announcement processes and poor user experience in related technologies.

[0007] According to one embodiment of this disclosure, a method for announcing IPv6 source address programming information is provided, comprising: a second node receiving an announcement of IPv6 source address programming information from a first node via an Interior Gateway Protocol (IGP), and constructing an IPv6 source address programming information table based on the IPv6 source address programming information; the second node receiving a service packet from the first node, and parsing the service packet according to the IPv6 source address programming information table to obtain the IPv6 source address programming information.

[0008] According to another embodiment of this disclosure, a method for announcing IPv6 source address programming information is provided, comprising: a first node flooding IPv6 source address programming information to a second node via an Internal Gateway Protocol (IGP), such that the first node and the second node construct an IPv6 source address programming information table based on the IPv6 source address programming information; the first node sending a service packet to the second node, such that the second node parses the service packet and obtains the IPv6 source address programming information based on the IPv6 source address programming information table.

[0009] According to another embodiment of this disclosure, a method for announcing IPv6 source address programming capability is provided, comprising: a sixth node receiving an announcement of IPv6 source address programming capability from a fifth node via an Interior Gateway Protocol (IGP); the sixth node reporting the IPv6 source address programming capability to a controller via a Border Gateway Protocol-Link State (BGP-LS).

[0010] According to yet another embodiment of this disclosure, a computer-readable storage medium is also provided, wherein a computer program is stored therein, wherein the computer program is configured to perform the steps in any of the above method embodiments when it is run.

[0011] According to yet another embodiment of this disclosure, an electronic device is also provided, including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0012] According to yet another embodiment of this disclosure, a computer program product is also provided, including a computer program / instructions that are executed by a processor using the steps of any of the above method embodiments. Attached Figure Description

[0013] Figure 1 is a schematic diagram of the IPv6 packet format that carries the slice ID via the IPv6 source address in related technologies;

[0014] Figure 2 is a schematic diagram of the composition of slice source address in related technologies;

[0015] Figure 3 is a schematic diagram of the IPv6 packet encapsulation and decapsulation principle in related technologies;

[0016] Figure 4 is a hardware structure block diagram of a mobile terminal for an IPv6 source address programming information notification method according to an embodiment of the present disclosure.

[0017] Figure 5 is a flowchart of a method for announcing IPv6 source address programming information according to an embodiment of this disclosure;

[0018] Figure 6 is another flowchart of the method for announcing IPv6 source address programming information according to an embodiment of the present disclosure;

[0019] Figure 7 is another flowchart of the method for announcing IPv6 source address programming information according to an embodiment of the present disclosure;

[0020] Figure 8 is a flowchart of a method for announcing IPv6 source address programming capabilities according to an embodiment of this disclosure;

[0021] Figure 9 is a schematic diagram illustrating the notification principle of IPv6 source address programming capability according to an embodiment of this disclosure;

[0022] Figure 10 is a schematic diagram illustrating the principle of flooding IPv6 source address programming information via the IGP protocol according to an embodiment of this disclosure.

[0023] Figure 11 is a schematic diagram illustrating the principle of announcing IPv6 source address programming information via BGP protocol according to an embodiment of this disclosure;

[0024] Figure 12 is a schematic diagram illustrating the construction principle of the source address slice path in an embodiment of this disclosure;

[0025] Figure 13 is a schematic diagram illustrating the construction principle of IPv6 source address slicing according to an embodiment of this disclosure;

[0026] Figure 14 is a schematic diagram of another construction principle of IPv6 source address slicing according to an embodiment of this disclosure;

[0027] Figure 15 is a schematic diagram illustrating the construction principle of end-to-end IPv6 source address slicing according to an embodiment of this disclosure. Detailed Implementation

[0028] The embodiments of this disclosure will be described in detail below with reference to the accompanying drawings and examples.

[0029] It should be noted that the terms "first," "second," etc., in the specification, claims, and drawings of this disclosure are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0030] Figure 1 is a schematic diagram of the IPv6 packet format carrying a slice ID via the IPv6 source address in related technologies. As shown in Figure 1, the following parameters are used: Version: Represents the version number of the IPv6 protocol, generally a fixed value used to identify the IPv6 protocol version. Traffic Class: Used to distinguish different types of data flows, similar to the Type of Service field in IPv4, specifying packet priority or distinguishing service types. Flow Label: Used to identify the data flow to which the packet belongs, used to achieve flow-level load balancing or quality of service assurance. Payload Length: Represents the effective payload length of the IPv6 packet, i.e., the length of the data portion. Next Header: Indicates the type of the next extension header or upper-layer protocol following the IPv6 header in the IPv6 packet. Hop Limit: Similar to the Time-to-Live field in IPv4, indicating the maximum number of router hops the packet is allowed to traverse during transmission. Source Address: Represents the IP address of the sender of the IPv6 packet. Padding: Used to pad the IPv6 packet header to ensure the header length is a multiple of 8 bytes. Destination Address: The destination address, representing the IP address of the recipient of the IPv6 packet. Segment Routing Header (SRH): Used for flexible control and optimization of network paths, as well as the payload.

[0031] Figure 2 illustrates the structure of a slice source address in related technologies. As shown in Figure 2, it includes: a slice-specific source prefix (variable length) used by the chip to identify whether the source address carries a slice ID; a source address identifier (Node ID) (variable length) used to distinguish source address identifiers from different devices; and padding (variable length). The slice ID is located in the lower 32 bits of the IPv6 source address. The highest bit is used as a strict mode flag. Nodes use the slice ID in the lower 31 bits to find the corresponding slice resource interface or sub-channel. When the slice resource interface or sub-channel does not exist: if the Strict-Flag is 1, the packet is discarded; if the Strict-Flag is 0, the packet is forwarded using a non-sliced ​​channel.

[0032] Figure 3 illustrates the encapsulation and decapsulation principles of IPv6 packets in related technologies. As shown in Figure 3, the ingress node encapsulates the outer IPv6 header, fills in the slice-specific source address in the source address field, and carries the slice ID in the last 32 bits. Intermediate nodes match the IPv6 source address of the received packet with the slice-specific source prefix. If a match is found, it indicates that the IPv6 source address contains a Slice ID. Therefore, the Slice ID is extracted from the lower 32 bits of the IPv6 source address, and the corresponding slice resource interface is searched for to forward the packet. The egress node decapsulates the outer IPv6 header. The slice packet identifier is used to plan the slice-specific source prefix. During forwarding, the IPv6 source address is matched with the slice-specific source prefix to identify the slice packet. The Slice-ID encapsulation uses the last 32 bits of the IPv6 source address to encapsulate the slice ID. The routable prefix consists of the slice prefix and the Node ID, and its length is the sum of the slice prefix length and the Node ID length. The routable prefix is ​​advertised via the Interior Gateway Protocol (IGP) and used for source address routing between devices. At the same time, it generates a local address table entry on the local device.

[0033] The method embodiments provided in this disclosure can be executed in a mobile terminal, computer terminal, or similar computing device. Taking a mobile terminal as an example, FIG4 is a hardware structure block diagram of a mobile terminal for the notification method of IPv6 source address programming information according to an embodiment of this disclosure. As shown in FIG4, the mobile terminal may include one or more (only one is shown in FIG4) processors 402 (processor 402 may include, but is not limited to, processing devices such as microprocessors MCUs or programmable logic devices FPGAs) and a memory 404 for storing data. The mobile terminal may also include a transmission device 406 for communication functions and an input / output device 408. It will be understood by those skilled in the art that the structure shown in FIG4 is only illustrative and does not limit the structure of the mobile terminal. For example, the mobile terminal may also include more or fewer components than shown in FIG4, or have a different configuration than shown in FIG4.

[0034] The memory 404 can be used to store computer programs, such as application software programs and modules, like the computer program corresponding to the IPv6 source address programming information notification method in this embodiment. The processor 402 executes various functional applications and data processing by running the computer program stored in the memory 404, thus implementing the above-described method. The memory 404 may include high-speed random access memory and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 404 may further include memory remotely located relative to the processor 402, and these remote memories can be connected to the mobile terminal via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0035] The transmission device 406 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the mobile terminal's communication provider. In one example, the transmission device 406 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 406 may be a Radio Frequency (RF) module, used for wireless communication with the Internet.

[0036] This disclosure provides a method for announcing IPv6 source address programming information. Figure 5 is a flowchart of the method for announcing IPv6 source address programming information according to this disclosure. As shown in Figure 5, the process includes the following steps:

[0037] In step S502, the second node receives the notification of IPv6 source address programming information from the first node via IGP, and constructs an IPv6 source address programming information table based on the IPv6 source address programming information.

[0038] In one exemplary embodiment, the number of second nodes is one or more.

[0039] In this embodiment of the disclosure, the second node and the first node can be different nodes in the same IGP domain, wherein the first node floods the IPv6 source address programming information to the second node through the IGP protocol, and the number of second nodes can be multiple.

[0040] In one exemplary embodiment, the IPv6 source address programming information includes at least one of the following: a source address private prefix; a programming type; the location of the programming content; and the length of the programming content.

[0041] In this embodiment of the disclosure, IPv6 source address programming information is designed and announced through a control plane protocol. The IPv6 source address programming information includes at least one of the following: a dedicated source address prefix; a programming type; the location of the programming content; and the length of the programming content.

[0042] In one exemplary embodiment, the IPv6 source address programming information further includes: source address ignoring information, wherein the source address ignoring information is information content ignored during the IPv6 source address matching process.

[0043] In this embodiment of the disclosure, the IPv6 source address programming information may include prefix-match-ignore-info, which indicates the part that needs to be ignored when performing IPv6 source address matching. This part is optional, and not carrying this information indicates that it is not ignored.

[0044] In one exemplary embodiment, the IPv6 source address programming information carries slice identification information.

[0045] In this embodiment, the IPv6 source address programming information carries slice identification information. This is merely an example and not a specific limitation. In actual implementation, the IPv6 source address programming information may carry different information. Step S504: The second node receives the service packet from the first node and parses the service packet according to the IPv6 source address programming information table to obtain the IPv6 source address programming information.

[0046] Figure 6 is another flowchart of the method for announcing IPv6 source address programming information according to an embodiment of this disclosure. As shown in Figure 6, the process includes the following steps:

[0047] In step S602, the second node receives the notification of IPv6 source address programming information from the first node via IGP, and constructs an IPv6 source address programming information table based on the IPv6 source address programming information.

[0048] In step S604, the second node announces the IPv6 source address programming information to the third node through the Border Gateway Protocol (BGP), so that the third node floods the IPv6 source address programming information to the fourth node through IGP, and the third and fourth nodes construct the IPv6 source address programming information table based on the IPv6 source address programming information.

[0049] In this embodiment of the disclosure, the second node is still in the same IGP domain as the first node, but the second node can also be a boundary node, the third node is a boundary node in another IGP domain, and the fourth node is a node in the same IGP domain as the first node.

[0050] Figure 7 is another flowchart of the method for announcing IPv6 source address programming information according to an embodiment of the present disclosure. As shown in Figure 7, the process includes the following steps:

[0051] In step S702, the first node floods the IPv6 source address programming information to the second node through the Interior Gateway Protocol (IGP), so that the first node and the second node can construct an IPv6 source address programming information table based on the IPv6 source address programming information.

[0052] In step S704, the first node sends the service message to the second node, so that the second node can parse the service message and obtain the IPv6 source address programming information according to the IPv6 source address programming information table.

[0053] The above steps provide a method for announcing IPv6 source address programming information. The second node receives the IPv6 source address programming information announcement from the first node via the IGP protocol and constructs an IPv6 source address programming information table based on the information. The second node also receives service packets from the first node and parses them according to the IPv6 source address programming information table to obtain the IPv6 source address programming information. This method solves the problems of complex IPv6 source address programming information announcement processes and poor user experience in related technologies, achieving the effect of simplifying the announcement process and improving the user experience.

[0054] Figure 8 is a flowchart of a method for announcing IPv6 source address programming capabilities according to an embodiment of this disclosure. As shown in Figure 8, the process includes the following steps:

[0055] In step S802, the sixth node receives an announcement from the fifth node regarding the IPv6 source address programming capability via the Interior Gateway Protocol (IGP).

[0056] In this embodiment of the disclosure, the announcement of IPv6 source address programming capabilities is described using a fifth node and a sixth node, wherein the fifth node and the sixth node may be the same node as the first node and the second node. That is, the fifth node and the sixth node are different nodes in the same IGP domain.

[0057] In one exemplary embodiment, the IPv6 source address programming capability includes at least the IPv6 source address slicing programming capability.

[0058] In this embodiment of the disclosure, the IPv6 source address programming capability includes the IPv6 source address slicing programming capability. This is only an example and is not intended to be specific. In actual implementation, the IPv6 source address programming capability may include different capabilities.

[0059] In one exemplary embodiment, the number of fifth nodes and / or sixth nodes is one or more.

[0060] In this embodiment of the disclosure, the IPv6 source address programming capability is flooded through the IGP protocol, and the number of the corresponding fifth and sixth nodes can be one or more.

[0061] In step S804, the sixth node reports the IPv6 source address programming capability to the controller via the Border Gateway Link State Protocol (BGP-LS).

[0062] In one exemplary embodiment, the sixth node reports its IPv6 source address programming capability to the controller via BGP-LS, including: the sixth node reporting its own IPv6 source address programming capability and that of other nodes to the controller via BGP-LS, wherein the other nodes include at least one or more fifth nodes.

[0063] In this embodiment of the disclosure, other nodes may include a sixth node in addition to one or more fifth nodes. The fifth or sixth node is merely for distinguishing different nodes within the IGP domain and does not serve a specific differentiating or limiting function. In this embodiment, the sixth node may be a border gateway node, and if it is a border node, it will report the capability information of other sixth nodes, i.e., non-border nodes.

[0064] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this disclosure, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this disclosure.

[0065] This embodiment also provides a device for announcing IPv6 source address programming information (or capabilities), which is used to implement the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0066] This disclosure provides an IPv6 source address programming information notification device, comprising: a first receiving module configured to receive notifications of IPv6 source address programming information from a first node via IGP, and to construct an IPv6 source address programming information table based on the IPv6 source address programming information; and a second receiving module configured to receive service packets from the first node at the second node, and to parse the service packets according to the IPv6 source address programming information table to obtain the IPv6 source address programming information.

[0067] In this embodiment of the disclosure, the above-mentioned notification device for IPv6 source address programming information can be set at the second node, that is, any node in the IGP domain.

[0068] This disclosure provides an IPv6 source address programming capability notification device, comprising: a third receiving module configured to receive an IPv6 source address programming capability notification from a fifth node via Interior Gateway Protocol (IGP); and a reporting module configured to report the IPv6 source address programming capability to a controller via Border Gateway Link State Protocol (BGP-LS).

[0069] In this embodiment of the disclosure, the above-mentioned notification device for IPv6 source address programming capability can be set at the sixth node, that is, any node in the IGP domain.

[0070] It should be noted that the above modules can be implemented by software or hardware. For the latter, implementation can be achieved in the following ways, but is not limited to: all modules are located in the same processor; or, the modules are located in different processors in any combination. In this embodiment, the naming conventions and functional divisions of the different modules in the notification device are only illustrative and not specific limitations. The location of the notification device is not limited to nodes in the IGP domain. In actual implementation, different naming conventions and functional divisions can be used, as long as the steps in the above method embodiments can be achieved.

[0071] Embodiments of this disclosure also provide a computer-readable storage medium storing a computer program configured to perform the steps in any of the above method embodiments when executed.

[0072] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.

[0073] Embodiments of this disclosure also provide an electronic device including a memory and a processor, the memory storing a computer program and the processor being configured to run the computer program to perform the steps in any of the above method embodiments.

[0074] In one exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor and the input / output device is connected to the processor.

[0075] Embodiments of this disclosure also provide a computer program product, including a computer program / instructions, which are executed by a processor using the steps of any of the method embodiments described above.

[0076] Specific examples in this embodiment can be found in the examples described in the above embodiments and exemplary implementations, and will not be repeated here.

[0077] It is obvious to those skilled in the art that the modules or steps of this disclosure described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. They can be implemented using computer-executable program code, and thus can be stored in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those presented herein, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, this disclosure is not limited to any particular combination of hardware and software.

[0078] To enable those skilled in the art to better understand the technical solutions of this disclosure, the technical solutions of this disclosure will be described below in conjunction with specific embodiments.

[0079] Example 1

[0080] This disclosure optimizes path calculation, simplifies configuration, and improves deployment flexibility by extending the control plane protocol to announce IPv6 source address programming capabilities and programming information. Figure 9 is a schematic diagram of the announcement principle of IPv6 source address programming capabilities according to this disclosure. As shown in Figure 9, white nodes represent nodes that support IPv6 source address slicing programming, and black nodes represent nodes that do not support IPv6 source address slicing programming.

[0081] This disclosure extends the IGP protocol to flood the IPv6 source address slicing programming capability of each node within the IGP domain, and extends the BGP-LS protocol to report the IPv6 source address slicing programming capability of each node to the controller. When calculating the IPv6 source address slicing path, the controller filters out nodes that do not support IPv6 source address slicing programming and selects nodes that do support IPv6 source address slicing programming, thereby ensuring that a path that meets the requirements is constructed.

[0082] In this embodiment of the disclosure, IPv6 source address programming information is designed and announced via a control plane protocol. The IPv6 source address programming information includes at least one of the following: a dedicated source address prefix; a programming type; the location of the programming content; and the length of the programming content. The field structure of the IPv6 source address programming information (IPv6 source prefix structure) provided in this embodiment of the disclosure is as follows:

[0083] IPv6 source prefix structure:

[0084] IPv6 source prefix:x:y:z:: / 48;

[0085] prefix-match-ignore-info(optional);

[0086] start-bit: 17;

[0087] length: 16;

[0088] information position structure:

[0089] type: slice-id;

[0090] start-bit: 97;

[0091] length: 32.

[0092] The IPv6 source prefix structure includes: `IPv6 source prefix` represents the IPv6 source address network segment; `prefix-match-ignore-info` indicates the part to be ignored during IPv6 source address matching (optional; omitting this information means it is not ignored; multiple `prefix-match-ignore-info` entries can be included when ignoring multiple non-contiguous parts); `start-bit` indicates the starting position of the ignored information in the IPv6 source address; and `length` indicates the length of the ignored information. The `type` in the information position structure indicates the type of information carried in the IPv6 source address. When the type is `slice-id`, it means the IPv6 source address carries a `Slice-ID`. New information types can be defined as needed. `start-bit` indicates the starting position of this information in the IPv6 source address; and `length` indicates the length of this information. In practical implementation, when the IPv6 source address carries multiple types of information simultaneously, multiple information position structures can be used to describe the type and position of each type of information.

[0093] Figure 10 is a schematic diagram illustrating the principle of flooding IPv6 source address programming information via the IGP protocol according to an embodiment of this disclosure. As shown in Figure 10, only one node in the network needs to be configured with an IPv6 source prefix structure. Flooding is then performed via IGP, enabling all nodes in the network to learn the IPv6 source prefix structure information and generate an IPv6 source prefix structure table. When a node receives a packet, it can use this table to determine whether the IPv6 source address carries a Slice ID and the position of the Slice ID in the IPv6 source address.

[0094] Figure 11 is a schematic diagram illustrating the principle of advertising IPv6 source address programming information via the BGP protocol according to an embodiment of this disclosure. As shown in Figure 11, in order to achieve network-wide advertising of IPv6 source prefix structure information, domain boundary nodes can redistribute the IPv6 source prefix structure learned from IGP to BGP and advertise it to BGP neighbors. Domain boundary nodes can also redistribute the IPv6 source prefix structure learned from BGP to IGP and flood it within the IGP domain.

[0095] In this embodiment of the disclosure, IPv6 source address programming information is flooded within the IGP domain via the IGP protocol, and the IPv6 source address programming information is advertised to neighboring nodes across the IGP domain via the BGP protocol. Carrying or advertising IPv6 source address programming information requires extensions to the IGP and BGP protocols. In this embodiment of the disclosure, no restrictions are placed on the specific extension methods.

[0096] Example 2

[0097] In this embodiment of the disclosure, the IPv6 source address programming information carries slice identification information, and the IPv6 source address programming capability includes the IPv6 source address slice programming capability. This is only an example and is not a specific limitation. In actual implementation, the IPv6 source address programming information may carry different information, and the IPv6 source address programming capability may include different capabilities.

[0098] Figure 12 is a schematic diagram illustrating the construction principle of the source address slicing path in this embodiment of the present disclosure. The controller constructs a source address slicing path that meets the requirements based on the device's source address slicing programming capability. As shown in Figure 12, an IPv6 source address slicing path needs to be established from node 1 to node 3. Node 4 in the network does not support IPv6 source address slicing, while other nodes do. Nodes supporting IPv6 source address slicing announce their support for IPv6 source address slicing capability through IGP, and node 2 reports this to the controller via the BGP-LS protocol. When the controller calculates the IPv6 source address slicing path from node 1 to node 3, it finds that node 4 does not support IPv6 source address slicing, therefore node 4 can be bypassed. Ultimately, an IPv6 source address slicing path from node 1 to node 3 is successfully created as: Node 1 -> Node 2 -> Node 3.

[0099] Example 3

[0100] In this embodiment of the disclosure, the IPv6 source address programming information carries slice identification information, and the IPv6 source address programming capability includes the IPv6 source address slice programming capability. This is only an example and is not a specific limitation. In actual implementation, the IPv6 source address programming information may carry different information, and the IPv6 source address programming capability may include different capabilities.

[0101] Figure 13 is a schematic diagram illustrating the construction principle of IPv6 source address slicing according to an embodiment of this disclosure. IPv6 source address slicing information is advertised via IGP to construct the IPv6 source address slicing. As shown in Figure 13, Slice 10 is created between nodes 1, 2, and 3, with 10MB of bandwidth reserved. A tunnel is created on node 1, and the tunnel is associated with Slice 10. Node 1 specifies that Slice ID information is carried via IPv6 source address, configures the IPv6 source prefix structure, and advertises it via IGP. IPv6 source prefix structure tables are generated on nodes 1, 2, and 3. Node 1 encapsulates the service packet with the IPv6 source address as IPv6 source prefix + Slice ID = 2023:1:2::10. When node 2 receives the packet, it matches the IPv6 source address 2023:1:2::10 against node 2's IPv6 source prefix structure table, and a match is found. 2023:1:2::10 is an IPv6 slice source address. Slice ID 10 is obtained from the lower 32 bits of the source address. The corresponding slice channel on node 2 is obtained through Slice ID 10, and the packet is forwarded through this channel.

[0102] Example 4

[0103] In this embodiment of the disclosure, the IPv6 source address programming information carries slice identification information, and the IPv6 source address programming capability includes the IPv6 source address slice programming capability. This is only an example and is not a specific limitation. In actual implementation, the IPv6 source address programming information may carry different information, and the IPv6 source address programming capability may include different capabilities.

[0104] Figure 14 is a schematic diagram illustrating another construction principle of IPv6 source address slicing according to an embodiment of this disclosure. IPv6 source address slicing information is advertised via IGP to construct IPv6 source address slicing, supporting the ignoring of certain bits in the source prefix. As shown in Figure 14, Slice 10 is created between nodes 1, 2, and 3, with 10MB of bandwidth reserved. A tunnel is created on node 1 and associated with Slice 10. Node 1 specifies that Slice ID information is carried via the IPv6 source address, configures the IPv6 source prefix structure, and advertises it via IGP. An IPv6 source prefix structure table is generated on nodes 1, 2, and 3. Node 1 encapsulates the service packet's IPv6 source address as IPv6 source prefix + Slice ID = 2023:1:2::10. When node 2 receives the packet, it matches the IPv6 source address 2023:1:2::10 against node 2's IPv6 source prefix structure table, and a match is found. 2023:1:2::10 is obtained as an IPv6 slice source address, and Slice ID 10 is obtained. The corresponding slice channel on node 2 is obtained through Slice ID 10, and the packet is forwarded through this channel.

[0105] Example 5

[0106] In this embodiment of the disclosure, the IPv6 source address programming information carries slice identification information, and the IPv6 source address programming capability includes the IPv6 source address slice programming capability. This is only an example and is not a specific limitation. In actual implementation, the IPv6 source address programming information may carry different information, and the IPv6 source address programming capability may include different capabilities.

[0107] Figure 15 is a schematic diagram illustrating the construction principle of an end-to-end IPv6 source address slice according to an embodiment of this disclosure. The end-to-end IPv6 source address slice is constructed by advertising IPv6 source address slice information via IGP and BGP. As shown in Figure 15, Slice 10 is created between nodes 1, ASBR1, ASBR2, and 2, with 10MB of bandwidth reserved. A tunnel is created on node 1 and associated with Slice 10. Node 1 specifies that Slice ID information is carried via IPv6 source address, configures the IPv6 source prefix structure, and advertises it via IGP. Node ASBR1 redistributes the IPv6 source prefix structure information received from the IGP1 domain to its BGP and advertises it to ASBR2 via BGP. The BGP on node ASBR2 redistributes the received IPv6 source prefix structure to its IGP, flooding it within the IGP2 domain. An IPv6 source prefix structure table is generated on nodes 1, ASBR1, ASBR2, and 2. Node 1 encapsulates the service packet with an IPv6 source address of IPv6 source prefix + Slice ID = 2023:1:2::10. When nodes ASBR1 and ASBR2 receive the packet, they match the IPv6 source address 2023:1:2::10 against Node 2's IPv6 source prefix structure table, and a match is found. This indicates that 2023:1:2::10 is an IPv6 slice source address. The lower 32 bits of the source address are used to obtain Slice ID 10. The corresponding slice channel on Node 2 is then retrieved using Slice ID 10, and the packet is forwarded through this channel.

[0108] In summary, the IPv6 source address programming information and programming capability announcement method provided in this disclosure proposes a structure representing IPv6 source address programming information by extending the control plane protocol to announce the device's IPv6 source address programming capability, extending the control plane protocol to announce this information, and defining the processing method for this information. This solves the problems of complex IPv6 source address programming information announcement processes and poor service experience in related technologies, achieving the effect of simplifying the IPv6 source address programming information and programming capability announcement process and improving service experience.

[0109] The above description is merely a preferred embodiment of this disclosure and is not intended to limit this disclosure. Various modifications and variations can be made to this disclosure by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the principles of this disclosure should be included within the scope of protection of this disclosure.

Claims

1. A method for announcing IPv6 source address programming information, comprising: The second node receives the notification of IPv6 source address programming information from the first node through the Interior Gateway Protocol (IGP), and constructs an IPv6 source address programming information table based on the IPv6 source address programming information. The second node receives service packets from the first node and parses the service packets according to the IPv6 source address programming information table to obtain the IPv6 source address programming information.

2. The method according to claim 1, wherein, The number of the second node is one or more.

3. The method according to claim 1, wherein, The IPv6 source address programming information includes at least one of the following: Source address-specific prefix; Programming type; The location of the programming content; The length of the programming content.

4. The method according to claim 3, wherein, The IPv6 source address programming information also includes: Source address ignore information, wherein the source address ignore information is information content ignored during the IPv6 source address matching process.

5. The method according to claim 1, wherein, The IPv6 source address programming information carries slice identification information.

6. The method according to claim 1, wherein, After the second node receives an announcement of IPv6 source address programming information from the first node via Interior Gateway Protocol (IGP), the method further includes: The second node announces the IPv6 source address programming information to the third node through the Border Gateway Protocol (BGP), so that the third node floods the IPv6 source address programming information to the fourth node through IGP, and the third node and the fourth node construct an IPv6 source address programming information table based on the IPv6 source address programming information.

7. A method for announcing IPv6 source address programming information, comprising: The first node floods the IPv6 source address programming information to the second node through the Interior Gateway Protocol (IGP), so that the first node and the second node can construct an IPv6 source address programming information table based on the IPv6 source address programming information. The first node sends the service message to the second node, so that the second node can parse the service message and obtain the IPv6 source address programming information according to the IPv6 source address programming information table.

8. A method for announcing IPv6 source address programming capability, comprising: The sixth node receives an announcement from the fifth node regarding the ability to program IPv6 source addresses via the Interior Gateway Protocol (IGP). The sixth node reports the IPv6 source address programming capability to the controller via the Border Gateway Link State Protocol (BGP-LS).

9. The method according to claim 8, wherein, The IPv6 source address programming capability includes at least the following: IPv6 source address slicing programming capabilities.

10. The method according to claim 8, wherein, The number of the fifth nodes is one or more, or the number of the sixth nodes is one or more.

11. The method according to claim 8, wherein, The sixth node reports the IPv6 source address programming capability to the controller via the Border Gateway Link State Protocol (BGP-LS), including: The sixth node reports the IPv6 source address programming capability of itself and other nodes to the controller via BGP-LS, wherein the other nodes include at least one or more of the fifth nodes.

12. A computer-readable storage medium storing a computer program, wherein, When the computer program is executed by a processor, it implements the method described in any one of claims 1 to 11.

13. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the method of any one of claims 1 to 11.

14. A computer program product comprising a computer program or instructions that, when executed by a processor, implement the steps of the method of any one of claims 1 to 11.

Images