A message forwarding method and device, a storage medium and an electronic device

Abstract

The embodiment of the application provides a message forwarding method and device, a storage medium and an electronic device. The method comprises the following steps: an SRv6 and a domain boundary node of a non-IP network receive an SRv6 message, and the SRv6 message is forwarded according to the behavior indication of the SRv6 SID of the SRv6 message. The method can solve the problem of how the SRv6 message passes through the SRv6 and the domain boundary node of the non-IP network and crosses the non-IP network in the prior art, and realizes message forwarding across the non-IP network.

Description

Technical Field

[0001] This application relates to the field of communications, and more specifically, to a message forwarding method, apparatus, storage medium, and electronic device. Background Technology

[0002] In network communication, Segment Routing (SR) is a source routing technology. When using this technology, forwarding points do not need to be aware of the service status; they only need to maintain topology point information. This decouples the number of service instances from the network, greatly improving the network's ability to support ubiquitous connectivity and its scalability. The principle of SR is that the source node pushes instructions carrying routing information onto the packet header, and intermediate forwarding points pop the relevant instructions hop by hop to forward the packet.

[0003] SR technology considers two encapsulation methods on the data plane: Multi-Protocol Label Switching (MPLS) encapsulation, reusing the MPLS data plane, and SRv6 encapsulation, using Internet Protocol Version 6 (IPv6). The SR architecture can run on both data planes. The MPLS forwarding plane can be applied to the SR model without any modifications. SRv6 technology adds an SRH (Segment Routing Header) header to IPv6 packets to store a list of 128-bit SRv6 SIDs (segment IDs) in IPv6 address format. A 128-bit SRv6 SID mainly consists of three parts: the LOC field (IPv6 prefix format, routable) identifying the node's location, the FUNC field (local identification) identifying the service and function, and the ARG field storing relevant parameters. A standard SRv6 SID can define the path information, service, and function information of a specific node.

[0004] The network currently supports Slicing Packet Network (SPN) networks. SPN networks can be SR-MPLS-enabled networks or Layer 1 networks, such as MTN / OTN networks. Deploying SRv6 to an existing network requires the coexistence and interoperability of the SRv6 network and the SPN network. Figure 1 This is a schematic diagram illustrating the interoperability between the L1 layer network and SRv6 in related technologies, such as... Figure 1 The image shows one scenario of interoperability between an L1 layer network and SRv6. Figure 1This is just an example diagram of an L1 network (MTN / OTN / small granularity). The network in the middle could also be an L2 network, or other non-IP networks, such as optical links for LO, Wavelength Division Multiplexing (WDM) / Passive Optical Network (PON), wireless links (5G / Wifi), space links, etc. Nodes 1, 2, 3, and 4 belong to SRv6 network 1; 4, 5, 6, and 7 belong to L1 layer networks; 7, 8, 9, and 10 belong to SRv6 network 2. Nodes 4 and 7 are boundary nodes belonging to both SRv6 and L1 layer networks. However, for nodes in both SRv6 and L1 layer networks, when data packets are forwarded from the boundary node between the SRv6 and L1 layer networks to nodes within the L1 layer domain, there is currently no protocol or solution to address how data packets traverse the L1 network after leaving nodes 4 / 7.

[0005] There is currently no solution to the problem of how SRv6 messages can pass through domain boundary nodes of non-IP networks via SRv6 and non-IP networks. Summary of the Invention

[0006] This application provides a message forwarding method, apparatus, storage medium, and electronic device to at least solve the problem in the related art of how SRv6 messages can pass through SRv6 and domain boundary nodes of non-IP networks and traverse non-IP networks.

[0007] According to one embodiment of this application, a message forwarding method is provided, applied to a domain boundary node between SRv6 and a non-IP network, the method comprising:

[0008] Receive SRv6 messages;

[0009] The SRv6 message is forwarded according to the behavior instruction of the SRv6 SID of the SRv6 message.

[0010] According to another embodiment of this application, a message forwarding method is also provided, applied to a first node, the method comprising:

[0011] Generate an SRv6 message containing an SRv6 SID;

[0012] Send the SRv6 message, wherein the SRv6 SID is used to indicate the mapping of the SRv6 SID to the non-IP channel.

[0013] According to another embodiment of this application, a message forwarding device is also provided, applied to a domain boundary node between SRv6 and a non-IP network, the device comprising:

[0014] The receiving module is used to receive SRv6 messages;

[0015] The forwarding module is used to forward the SRv6 message according to the behavior indication of the SRv6 SID of the SRv6 message.

[0016] According to another embodiment of this application, a message forwarding device is also provided, applied to a head node, the device comprising:

[0017] The generation module is used to generate SRv6 messages containing SRv6 SIDs;

[0018] A sending module is used to send the SRv6 message, wherein the SRv6 SID is used to indicate the mapping between the SRv6 SID and the non-IP channel.

[0019] According to yet another embodiment of this application, 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.

[0020] According to yet another embodiment of this application, 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.

[0021] In this embodiment, the SRv6 and non-IP network domain boundary node receive SRv6 packets and forward the SRv6 packets according to the behavior indication of the SRv6 SID of the SRv6 packets. This can solve the problem in related technologies of how SRv6 packets can pass through the SRv6 and non-IP network domain boundary node and cross the non-IP network, and realize packet forwarding across the non-IP network. Attached Figure Description

[0022] Figure 1 This is a schematic diagram illustrating the interoperability between the L1 layer network and SRv6 in related technologies;

[0023] Figure 2 This is a hardware structure block diagram of a mobile terminal for the message forwarding method according to an embodiment of this application;

[0024] Figure 3 This is a flowchart of the message forwarding method according to the embodiments of this application. Figure 1 ;

[0025] Figure 4 This is a flowchart of the message forwarding method according to the embodiments of this application. Figure 2 ;

[0026] Figure 5 This is a flowchart of a message forwarding method according to an embodiment of the present invention;

[0027] Figure 6 This is a schematic diagram of the SID according to this embodiment;

[0028] Figure 7 This is a schematic diagram of channel types and channel identifiers according to this embodiment;

[0029] Figure 8 This is a frame of a message forwarding apparatus according to an embodiment of this application. Figure 1 ;

[0030] Figure 9 This is a frame of a message forwarding apparatus according to an embodiment of this application. Figure 2 . Detailed Implementation

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

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

[0033] The methods and embodiments provided in this application can be executed on a mobile terminal, computer terminal, or similar computing device. Taking running on a mobile terminal as an example, Figure 2 This is a hardware structure block diagram of a mobile terminal for the message forwarding method according to an embodiment of this application, as shown below. Figure 2 As shown, a mobile terminal may include one or more ( Figure 2 Only one is shown in the diagram. A processor 102 (which may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.) and a memory 104 for storing data are also shown. The mobile terminal may further include a transmission device 106 for communication functions and an input / output device 108. Those skilled in the art will understand that... Figure 2 The structure shown is for illustrative purposes only and does not limit the structure of the mobile terminal described above. For example, the mobile terminal may also include components that are more... Figure 2 The more or fewer components shown, or having the same Figure 2 The different configurations shown.

[0034] The memory 104 can be used to store computer programs, such as application software programs and modules, like the computer program corresponding to the message forwarding method in this embodiment. The processor 102 executes various functional applications and service chain address pool slicing processing by running the computer program stored in the memory 104, thus implementing the above-described method. The memory 104 may include high-speed random access memory and 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 104 may further include memory remotely located relative to the processor 102, 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 106 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 106 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 106 may be a Radio Frequency (RF) module, used for wireless communication with the Internet.

[0036] This embodiment provides a packet forwarding method that operates on the aforementioned mobile terminal or network architecture. Figure 3 This is a flowchart of the message forwarding method according to the embodiments of this application. Figure 1 ,like Figure 3 As shown, this process, applied to domain boundary nodes in SRv6 and non-IP networks, includes the following steps:

[0037] Step S302: Receive SRv6 message;

[0038] Step S304: Forward the SRv6 message according to the behavior indication of the SRv6 SID of the SRv6 message;

[0039] The SRv6 SID behavior indicator here is only used to tell the node that it needs to map a non-IP channel for continued forwarding. See step S306 for the specific non-IP channel to be mapped.

[0040] In this embodiment, the aforementioned SRv6 SID defines new behavioral indication information, which represents the mapping between the SRv6 SID and non-IP channels. The non-IP channels in this embodiment include at least one of the following: an LO optical link (WDM / PON), a wireless link, a spatial link, an L1 tunnel, and an L2 link.

[0041] By using the steps S302 to S304 above, the problem of how SRv6 packets can pass through the domain boundary nodes of SRv6 and non-IP networks and traverse non-IP networks can be solved, thus realizing packet forwarding across non-IP networks.

[0042] In one embodiment, step S304 may specifically include: determining a non-IP channel based on the behavior indication of the SRv6 SID of the SRv6 packet; and mapping the SRv6 packet to the non-IP channel for forwarding.

[0043] If a behavior indication is defined for two or more non-IP networks, the above-mentioned determination of a non-IP channel based on the behavior indication of the SRv6 SID in the SRv6 message may specifically include: extracting the channel type and channel identifier from the SRv6 SID; and determining the non-IP channel based on the channel type and the channel identifier.

[0044] In another embodiment, if a behavior indication is defined for a specific type of non-IP network, such as a behavior indication for a Metro Transport Network (MTN), an OTN, or an optical link, then it is not necessary to extend the SRv6 SID to carry the channel type. Determining a non-IP channel based on the behavior indication of the SRv6 SID in the SRv6 message may specifically include: extracting a channel identifier from the SRv6 SID; and determining the non-IP channel based on the channel identifier.

[0045] In another embodiment, if the mapping relationship between SRv6 SID and non-IP channel is stored locally, it is not necessary to extend the SID to carry the channel type and channel identifier. This mapping relationship is stored locally before step S304 above. Specifically, the mapping relationship between SRv6 SID and non-IP channel issued by the receiving controller is stored locally. Correspondingly, the above-mentioned determination of non-IP channel based on the behavior indication of SRv6 SID in SRv6 message may specifically include: determining the non-IP channel based on the locally stored mapping relationship between SRv6 SID and non-IP channel.

[0046] According to another aspect of the embodiments of this application, a message forwarding method is also provided. Figure 4 This is a flowchart of the message forwarding method according to the embodiments of this application. Figure 2 ,like Figure 4 As shown, applied to the first node, the process includes the following steps:

[0047] Step S402: Generate an SRv6 message containing an SRv6 SID;

[0048] Step S404: Send the SRv6 message, wherein the SRv6 SID is used to indicate the mapping between the SRv6 SID and the non-IP channel.

[0049] In step S404 above, the SRv6 message can be sent to the domain boundary node of the SRv6 and non-IP networks. The SRv6 SID is used to instruct the domain boundary node to identify the non-IP channel and map the SRv6 message to the non-IP channel for forwarding. The first node may directly send the SRv6 message to the domain boundary node, or it may forward it to the domain boundary node through other nodes.

[0050] By using the steps S402 to S404 above, the problem of how SRv6 packets can pass through the domain boundary nodes of SRv6 and non-IP networks and traverse non-IP networks can be solved, thus realizing packet forwarding across non-IP networks.

[0051] In this embodiment, step S402 may specifically include: obtaining SID list information carrying new SID behavior indication information sent by the controller; specifically, obtaining a message sent by the controller through an extended protocol, wherein the message carries the new SID behavior indication information, and the extended protocol is a routing protocol-based protocol, such as PCEP and / or BGP; generating a SID list containing the new SID behavior indication information; and generating an SRv6 message containing the SRv6 SID based on the SID list, wherein the SRv6 SID defines the new SID behavior indication information. The new SID behavior indication information is used to represent the mapping between the SRv6 SID and non-IP channels.

[0052] In this embodiment, at least one SID in the SID list is the SID of the new SID behavior indication information.

[0053] In this embodiment, SRv6 is bound to a non-IP link, which can be an optical link (WDM / PON) of the LO; a wireless link (5G / Wifi); a spatial link; an L1 tunnel; and an L2 link, etc.

[0054] Regarding the issue of how non-IP network boundary nodes encapsulate and forward data packets in cross-domain scenarios, such as... Figure 1 As shown, Figure 1 This is a cross-domain network diagram. This invention provides a message forwarding method in its embodiments. Figure 5 This is a flowchart of a message forwarding method according to an embodiment of the present invention, such as... Figure 5 As shown, the process includes the following steps:

[0055] Step S502: The cross-domain orchestrator implements end-to-end orchestration of SRv6 paths.

[0056] In step S504, the orchestrator does not focus on the internal connections of the non-IP network, but only specifies the start and end nodes of the non-IP network, bandwidth, isolation requirements, etc. The domain controller of the non-IP network creates tunnels as needed, which can be L1 tunnels and L2 links.

[0057] In step S506, the domain controller in the non-IP network creates an L1 tunnel / L2 Ethernet link and reports the behavior indication information of SRv6 and the domain boundary node of the non-IP network to the orchestrator. At the same time, the configuration is sent to the domain boundary node of SRv6 and the non-IP network. The controller can send the behavior indication information to the node through the Path Computation Element Communication Protocol (PCEP) and the Border Gateway Protocol (BGP).

[0058] This is an example of the controller actively allocating behavior indication information between SRv6 and domain boundary nodes in non-IP networks. In one possible scenario, the domain boundary nodes themselves can allocate the information and report it to the controller, which then reports it to the orchestrator. Nodes can report to the controller via PCEP and BGP-LS protocols.

[0059] In step S508, the orchestrator incorporates the nodes with behavior indication information of domain boundary nodes into the SR List and sends it to the first node of SRv6 through the controller.

[0060] Step S509: The first node generates an SR List containing the SRv6 SID behavior indication information.

[0061] The controller can send commands to the SRv6 head node via interfaces such as PCEP, BGP, and NETCONF.

[0062] Figure 6 This is a schematic diagram of the SID according to this embodiment, as shown below. Figure 6 As shown, the SRv6 Segment Identifier (SID) is used to identify an SRv6 segment. An SRv6 SID is a 128-bit IPv6 address. In SRv6 network programming, it typically consists of three parts, formatted as follows: Figure 6 As shown:

[0063] The meanings of each field are as follows:

[0064] Locator: An identifier assigned to a network node in the network topology, used to forward data packets to that node. The route corresponding to the Locator can be advertised in the network via IGP, helping other devices forward data packets to the node that advertised the Locator. In SRv6 SIDs, the Locator length is variable to adapt to networks of different sizes.

[0065] The Function is used to express the forwarding action to be performed by the instruction, equivalent to the opcode of a computer instruction. In SRv6 network programming, different forwarding behaviors are described by the Function section, such as forwarding a data packet to a specified link, or forwarding a packet by looking up a data packet in a specified table.

[0066] Arguments (Args) is an optional field. It consists of the arguments that the instruction takes when it is executed, and these arguments may contain streams, services, or any other relevant information.

[0067] In this embodiment, a new behavior indication information for nodes is defined: indicating the binding / mapping of SRv6 paths with non-IP pipes.

[0068] Define the behavior type of the new SID: End.BNI (Binding non-IP), a variant of the End.B6 function. End.BNI represents the binding / mapping of an SRv6 path to a non-IP pipeline, including optical links (WDM / PON) for LOs; wireless links (5G / Wifi); spatial links; L1 tunnels; and L2 links, etc. Define the specific channel type (MTN / FGU / ODUk / OSU / Ethernet, etc.) + channel identifier in the SRv6 SID. The specific details can be carried in the Argu or function. Figure 7 This is a schematic diagram of the channel type and channel identifier according to this embodiment, as shown below. Figure 7 As shown, Type: 8 bits are recommended, which can represent MTN, FGU, ODUk, OSU, and Ethernet, etc.; Channel ID: 24 bits are recommended.

[0069] When N receives a message pointing to S (S is a local End.BNI SID), N will execute the following instructions:

[0070] 1. IF NH = SRH and SL > 0;

[0071] 2. Decrement SL by 1 and update the IPv6 destination address to SRH[SL];

[0072] 3. Locate the corresponding L1 pipe / L2 link based on the TYPE+Channel ID in the End.BNI SID;

[0073] 4. Map SRv6 packets to L1 pipes / L2 links for forwarding according to the service mapping rules of the corresponding L1 pipes / L2 links;

[0074] 5. ELSE;

[0075] 6. Send an ICMP parameter problem message;

[0076] 7. Discard the message.

[0077] The above describes how to extend the SID to carry the channel type and channel identifier. In another possible implementation, the mapping relationship between the End.BNI SID and the channel is stored locally, so it is not necessary to extend the SID to carry the channel type and channel identifier.

[0078] The above embodiments define a behavior indicator for at least two types of non-IP networks. Multiple behavior indicators can also be defined for specific types of non-IP networks, such as one behavior indicator for MTN, one for OTN, and one for optical links. In this case, it is not necessary to extend the SRv6SID to carry the channel type. Only the channel identifier needs to be carried. Alternatively, if the local device has a mapping relationship between the End.BNI SID and the channel, it is also not necessary to carry the channel identifier.

[0079] Another possible implementation defines a completely new SR node behavior: specifically for non-IP network scenarios, tentatively named End.CNI (crossing non-IP), indicating forwarding to the non-IP link associated with End.CNI. Similarly, a behavior indicator can be defined for at least two types of non-IP networks, or multiple behavior indicators can be defined for specific types of non-IP networks. For example, one behavior indicator can be defined for MTN, another for Optical Transport Network (OTN), and yet another for optical links. The End.CNI SID can carry the specific channel type (MTN / FGU / ODUk / OSU / Ethernet, etc.) + channel identifier, or it can be omitted, depending on the specific implementation.

[0080] Another aspect of the embodiments of this application also provides a message forwarding device. Figure 8 This is a frame of a message forwarding apparatus according to an embodiment of this application. Figure 1 ,like Figure 8 As shown, the device, applied to a domain boundary node between SRv6 and non-IP networks, includes:

[0081] Receiver module 82 is used to receive SRv6 messages;

[0082] The forwarding module 84 is used to forward the SRv6 message according to the behavior indication of the SRv6 SID of the SRv6 message.

[0083] In this embodiment, the SRv6 SID defines new behavioral indication information, which represents the mapping between the SRv6 SID and the non-IP channel.

[0084] In this embodiment, the non-IP channel includes at least one of the following: an LO optical link WDM / PON, a wireless link, a spatial link, an L1 tunnel, and an L2 link.

[0085] In this embodiment, the forwarding module 84 includes:

[0086] The determination submodule is used to determine the non-IP channel based on the behavior indication of the SRv6 SID of the SRv6 message;

[0087] The forwarding submodule is used to map the SRv6 packets to the non-IP channel for forwarding.

[0088] In one embodiment, the determining submodule is further configured to extract the channel type and channel identifier from the SRv6 SID; and determine the non-IP channel based on the channel type and the channel identifier.

[0089] In another embodiment, the determining submodule is further configured to extract a channel identifier from the SRv6 SID and determine the non-IP channel based on the channel identifier.

[0090] In another embodiment, the determining submodule is further configured to determine the non-IP channel based on the mapping relationship between the locally stored SRv6 SID and the non-IP channel.

[0091] In an optional embodiment, the device further includes:

[0092] The receiving module is used to receive the mapping relationship between the SRv6 SID and the non-IP channel sent by the controller;

[0093] The storage module is used to store the mapping relationship between the SRv6 SID and the non-IP channel locally.

[0094] Another aspect of the embodiments of this application also provides a message forwarding device. Figure 9 This is a frame of a message forwarding apparatus according to an embodiment of this application. Figure 2 ,like Figure 9 As shown, applied to the first node, the device includes:

[0095] Generation module 92 is used to generate SRv6 messages containing SRv6 SIDs;

[0096] The sending module 94 is used to send the SRv6 message, wherein the SRv6 SID is used to indicate the mapping between the SRv6 SID and the non-IP channel.

[0097] In one embodiment, the generation module 92 includes:

[0098] The acquisition submodule is used to acquire the SID list information sent by the controller, which carries the new SID behavior indication information;

[0099] A generation submodule is used to generate a SID list containing the new SID behavior indication information; and to generate an SRv6 message containing the SRv6 SID based on the SID list, wherein the SRv6 SID defines the new SID behavior indication information.

[0100] In this embodiment, the new SID behavior indication information is used to represent the mapping between SRv6 SID and non-IP channels.

[0101] In one embodiment, the acquisition submodule is further configured to acquire a message sent by the controller through an extended protocol, wherein the message carries the new SID behavior indication information, and the extended protocol is a protocol based on a routing protocol.

[0102] In this embodiment, the extended protocol is the PCEP protocol and / or the BGP protocol.

[0103] In this embodiment, at least one SID in the SID list is the SID of the new SID behavior indication information.

[0104] Embodiments of this application also provide a computer-readable storage medium storing a computer program, wherein the computer program is configured to execute the steps in any of the above method embodiments when run.

[0105] 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 drive, magnetic disk, or optical disk.

[0106] Embodiments of this application also provide an electronic device 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.

[0107] 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.

[0108] 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.

[0109] Obviously, those skilled in the art should understand that the modules or steps of this application 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 here, 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 application is not limited to any particular combination of hardware and software.

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

Claims

1. A message forwarding method, characterized in that, The method, applied to domain boundary nodes in SRv6 and non-IP networks, includes: Receive SRv6 messages, wherein the SRv6 SID of the SRv6 message defines the channel type and channel identifier, or the SRv6 SID defines the channel identifier; The SRv6 message is forwarded according to the behavior indication of the SRv6 SID of the SRv6 message. The SRv6 SID defines new behavior indication information, which represents the mapping between the SRv6 SID and the non-IP channel. Forwarding the SRv6 message according to the behavior indication of the SRv6 SID of the SRv6 message includes: The non-IP channel is determined based on the behavior indication of the SRv6 SID in the SRv6 message; The SRv6 message is mapped to the non-IP channel for forwarding; The determination of the non-IP channel based on the behavior indication of the SRv6 SID in the SRv6 message includes: Extract the channel type and channel identifier from the SRv6 SID; determine the non-IP channel based on the channel type and channel identifier; or Extract the channel identifier from the SRv6 SID; determine the non-IP channel based on the channel identifier.

2. The method according to claim 1, characterized in that, The non-IP channel is determined to include, based on the behavior indication of the SRv6 SID in the SRv6 message: The non-IP channel is determined based on the mapping relationship between the locally stored SRv6 SID and the non-IP channel.

3. The method according to claim 2, characterized in that, The method further includes: The mapping relationship between the SRv6 SID and the non-IP channel sent by the receiver controller; The mapping relationship between the SRv6 SID and the non-IP channel is stored locally.

4. The method according to any one of claims 1 to 3, characterized in that, The non-IP channel includes at least one of the following: LO optical link WDM / PON, wireless link, spatial link, L1 tunnel, L2 link.

5. A message forwarding method, characterized in that, Applied to the first node, the method includes: Generate an SRv6 message containing an SRv6 SID, wherein the SRv6 SID is used to indicate the mapping between the SRv6 SID and a non-IP channel, and the SRv6 SID defines a channel type and a channel identifier; or, the SRv6 SID defines a channel identifier, and the channel type and the channel identifier are used to instruct the SRv6 and the domain boundary node of the non-IP network to determine the non-IP channel; or the channel identifier is used to instruct the SRv6 and the domain boundary node of the non-IP network to determine the non-IP channel. Send the SRv6 message.

6. The method according to claim 5, characterized in that, Generating an SRv6 message containing an SRv6 SID includes: Obtain the SID list information sent by the controller, which carries the new SID behavior indication information; Generate a list of SIDs containing the new SID behavior indication information; An SRv6 message containing the SRv6 SID is generated based on the SID list, wherein the SRv6 SID defines the new SID behavior indication information.

7. The method according to claim 6, characterized in that, The new SID behavior indication information is used to represent the mapping between SRv6 SIDs and non-IP channels.

8. The method according to claim 6, characterized in that, The SID list information sent by the controller, which carries the new SID behavior indication information, includes: Obtain the message sent by the controller through an extended protocol, wherein the message carries the new SID behavior indication information, and the extended protocol is a protocol based on a routing protocol.

9. The method according to claim 8, characterized in that, The extended protocol is the PCEP protocol and / or the BGP protocol.

10. The method according to claim 6, characterized in that, At least one SID in the SID list is a new SID behavior indication information SID.

11. A message forwarding device, characterized in that, The device, applied to domain boundary nodes in SRv6 and non-IP networks, includes: A receiving module is used to receive SRv6 messages, wherein the SRv6 SID of the SRv6 message defines the channel type and the channel identifier, or the SRv6 SID defines the channel identifier; The forwarding module is used to forward the SRv6 packet according to the behavior indication of the SRv6 SID of the SRv6 packet. The SRv6 SID defines new behavior indication information, which represents the mapping between the SRv6 SID and the non-IP channel. The forwarding module includes: The determination submodule is used to determine the non-IP channel based on the behavior indication of the SRv6 SID of the SRv6 message; The forwarding submodule is used to map the SRv6 packets to the non-IP channel for forwarding; The determining submodule is further configured to extract the channel type and channel identifier from the SRv6 SID; determine the non-IP channel based on the channel type and channel identifier; or The determining submodule is further configured to extract the channel identifier from the SRv6 SID; and determine the non-IP channel based on the channel identifier.

12. The apparatus according to claim 11, characterized in that, The determining submodule is further configured to determine the non-IP channel based on the mapping relationship between the locally stored SRv6 SID and the non-IP channel.

13. A message forwarding device, characterized in that, Applied to the first node, the device includes: A generation module is used to generate an SRv6 message containing an SRv6 SID, wherein the SRv6 SID is used to indicate the mapping between the SRv6 SID and a non-IP channel, and the SRv6 SID defines a channel type and a channel identifier; or, the SRv6 SID defines a channel identifier, and the channel type and the channel identifier are used to instruct the SRv6 and the domain boundary node of the non-IP network to determine the non-IP channel; or the channel identifier is used to instruct the SRv6 and the domain boundary node of the non-IP network to determine the non-IP channel. The sending module is used to send the SRv6 message.

14. The apparatus according to claim 13, characterized in that, The generation module is further configured to obtain SID list information carrying new SID behavior indication information sent by the controller; generate a SID list containing the new SID behavior indication information; and generate an SRv6 message containing the SRv6 SID based on the SID list, wherein the SRv6 SID defines the new SID behavior indication information.

15. A computer-readable storage medium storing a computer program, wherein, The computer program is configured to execute the method described in any one of claims 1 to 4, 5 to 10 when it is run.

16. An electronic device comprising a memory and a processor, the memory storing a computer program, the processor being configured to run the computer program to perform the method of any one of claims 1 to 4, 5 to 10.

Images