Message forwarding method, apparatus and system

By carrying slice identifiers in the message header and switching slice identifiers, the problem of cross-domain interoperability of network slices in the prior art is solved, efficient message forwarding and service isolation are achieved, and it is suitable for a variety of network scenarios.

WO2024239721A1PCT designated stage expired Publication Date: 2024-11-28HUAWEI TECH CO LTD
6 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2024/076352
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-19
Filing Date
2024-02-06
Publication Date
2024-11-28

Smart Images

  • Figure CN2024076352_28112024_PF_FP_ABST
    Figure CN2024076352_28112024_PF_FP_ABST
Patent Text Reader

Abstract

A message forwarding method, apparatus and system, which belong to the technical field of networks. The method comprises: a first network node, which is located at the boundary of a first network domain and a second network domain, receiving a first message from the first network domain, wherein the first message comprises a first message header, which matches the first network domain, and the first message header comprises a first slice identifier for indicating a first network slice; the first network node obtaining a second message on the basis of the second network domain and the first message, wherein the second message comprises a second message header, which matches the second network domain, the second message header comprises a second slice identifier for indicating a second network slice, and the second message header is different from the first message header; and the first network node sending the second message in the second network domain on the basis of the second slice identifier. The present application can achieve cross-domain interworking between network slices.
Need to check novelty before this filing date? Find Prior Art

Description

Message forwarding method, device and system

[0001] This application claims priority to Chinese patent application filed on May 19, 2023, with application number 202310575254.5 and application name “Message Forwarding Method, Device and System”, all contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of network technology, and in particular to a message forwarding method, device and system. Background Art

[0003] A network slice is a virtual network created by partitioning physical network resources. Different network slices created from the same physical network are isolated from each other and used to meet the needs of different services. Network nodes can forward packets through network slices to prevent packets from different services from competing for resources.

[0004] In mainstream slicing technology, a message is forwarded to the network slice indicated by the slice identifier by carrying the slice identifier in the message. However, the current method of carrying the slice identifier in the message cannot achieve cross-domain interoperability of network slices.

[0005] Summary of the Invention

[0006] The present application provides a message forwarding method, device and system. The technical solution of the present application is as follows.

[0007] In a first aspect, a message forwarding method is provided, which is applied to a first network node at the junction of a first network domain and a second network domain, the method comprising: the first network node receiving a first message from the first network domain, the first message including a first message header matching the first network domain, the first message header including a first slice identifier (slice ID) for indicating a first network slice; the first network node obtaining a second message based on the second network domain and the first message, the second message including a second message header matching the second network domain, the second message header including a second slice identifier for indicating a second network slice, the second message header being different from the first message header; the first network node sending the second message in the second network domain based on the second slice identifier. The first network slice is deployed in the first network domain, and the second network slice is deployed in the second network domain.

[0008] The technical solution provided by the present application is that a first message from a first network domain includes a first message header matching the first network domain, the first message header includes a first slice identifier for indicating a first network slice, and a first network node at the junction of the first network domain and the second network domain receives the first message and obtains a second message based on the second network domain and the first message, and sends the second message in the second network domain based on the second slice identifier for indicating the second network slice in the second message header included in the second message. In this way, the first network node can realize the switching of the first network slice in the first network domain and the second network slice in the second network domain, thereby realizing cross-domain intercommunication between the first network slice and the second network slice, avoiding the complex configuration of the network node to re-identify the service and the degradation of forwarding efficiency when the message crosses domains, and improving the message forwarding efficiency.

[0009] Optionally, the first network node obtaining the second message based on the second network domain and the first message includes: the first network node determining the second slice identifier based on the first slice identifier and the first mapping relationship, where the first mapping relationship includes a mapping relationship between the first slice identifier and the second slice identifier; and the first network node obtaining the second message based on the first message, the second slice identifier, and the second network domain. For example, the first network node encapsulates the first message based on the second network domain and the second slice identifier to obtain the second message.

[0010] The technical solution provided in the present application is that the first network node determines the second slice identifier used to indicate the second network slice based on the first mapping relationship and the first slice identifier in the first message header included in the first message. This can facilitate the first network node to switch the first slice identifier and the second slice identifier, thereby realizing cross-domain intercommunication between the first network slice and the second network slice, avoiding the complex configuration of the network node to re-identify the service and the degradation of forwarding efficiency when the message crosses the domain, and improving the message forwarding efficiency.

[0011] Optionally, the first network domain is a virtual local area network (VLAN) domain, the first message is a VLAN message, the first message header is an Ethernet (ETH) header, and the slice indication field of the ETH header is used to carry a first slice identifier; the second network domain is a virtual extensible local area network (VXLAN) domain, the second message is a VXLAN message, the second message header is a VXLAN header, and the reserved field or extended field of the VXLAN header is used to carry a second slice identifier.

[0012] The technical solution provided by the present application is that, when the first network domain is a VLAN domain and the second network domain is a VXLAN domain, the first network node realizes cross-domain intercommunication between the first network slice in the first network domain and the second network slice in the second network domain, that is, realizes cross-VLAN domain and VXLAN domain intercommunication between the first network slice and the second network slice. Therefore, the present application can realize cross-VLAN domain and VXLAN domain intercommunication between network slices. Moreover, in the present application, a slice identifier can be carried in an ETH header or a VXLAN header, and the network node can forward the message according to the slice identifier carried in the ETH header or the VXLAN header, thereby making the technical solution of the present application applicable to VLAN networks and VXLAN networks.

[0013] Optionally, the first network domain is a VLAN domain, the first message is a VLAN message, the first message header is an ETH header, and the slice indication field of the ETH header is used to carry a first slice identifier; the second network domain is a generic network virtualization encapsulation (GENEVE) domain, the second message is a GENEVE message, the second message header is a GENEVE header, and the extension field of the GENEVE header is used to carry a second slice identifier.

[0014] The technical solution provided by the present application is that, when the first network domain is a VLAN domain and the second network domain is a GENEVE domain, the first network node realizes cross-domain intercommunication between the first network slice in the first network domain and the second network slice in the second network domain, that is, realizes cross-VLAN domain and GENEVE domain intercommunication between the first network slice and the second network slice. Therefore, the present application can realize cross-VLAN domain and GENEVE domain intercommunication between network slices. Moreover, in the present application, a slice identifier can be carried in an ETH header or a GENEVE header, and the network node can forward the message according to the slice identifier carried in the ETH header or the GENEVE header, thereby making the technical solution of the present application applicable to VLAN networks and GENEVE networks.

[0015] Optionally, the first network domain is a VLAN domain, the first message is a VLAN message, the first message header is an ETH header, and the slice indication field of the ETH header is used to carry a first slice identifier; the second network domain is a segment routing (SRv6) domain based on Internet Protocol version 6 (IPv6), the second message is an SRv6 message, and the second message header is a hop by hop options header (HBH) or a destination options header (DOH), and the HBH or the DOH is used to carry a second slice identifier.

[0016] The technical solution provided by the present application is that, when the first network domain is a VLAN domain and the second network domain is an SRv6 domain, the first network node realizes cross-domain intercommunication between the first network slice in the first network domain and the second network slice in the second network domain, that is, realizes cross-VLAN domain and SRv6 domain intercommunication between the first network slice and the second network slice. Therefore, the present application can realize cross-VLAN domain and SRv6 domain intercommunication between network slices. Moreover, in the present application, a slice identifier can be carried in the ETH header, HBH or DOH, and the network node can forward the message according to the slice identifier carried in the ETH header, the HBH or the DOH, thereby making the technical solution of the present application applicable to VLAN networks and SRv6 networks.

[0017] Optionally, the first network domain is a VLAN domain, the first message is a VLAN message, the first message header is an ETH header, and the slice indication field of the ETH header is used to carry a first slice identifier; the second network domain is an Internet Protocol version 6 (IPv6) domain, the second message is an IPv6 message, the second message header is an IPv6 extension header, and the IPv6 extension header is used to carry a second slice identifier.

[0018] The technical solution provided by the present application is that, when the first network domain is a VLAN domain and the second network domain is an IPv6 domain, the first network node realizes cross-domain intercommunication between the first network slice in the first network domain and the second network slice in the second network domain, that is, realizes cross-VLAN domain and IPv6 domain intercommunication between the first network slice and the second network slice. Therefore, the present application can realize cross-VLAN domain and IPv6 domain intercommunication between network slices. Moreover, in the present application, a slice identifier can be carried in an ETH header or an IPv6 extension header, and the network node can forward the message according to the slice identifier carried in the ETH header or the IPv6 extension header, thereby making the technical solution of the present application applicable to VLAN networks and IPv6 networks.

[0019] Optionally, the first network domain is a VXLAN domain, the first message is a VXLAN message, the first message header is a VXLAN header, and the reserved field or extended field of the VXLAN header is used to carry a first slice identifier; the second network domain is a VLAN domain, the second message is a VLAN message, the second message header is an ETH header, and the slice indication field of the ETH header is used to carry a second slice identifier.

[0020] The technical solution provided by the present application is that, when the first network domain is a VXLAN domain and the second network domain is a VLAN domain, the first network node realizes cross-domain intercommunication between the first network slice in the first network domain and the second network slice in the second network domain, that is, realizes intercommunication between the first network slice and the second network slice across the VXLAN domain and the VLAN domain. Therefore, the present application can realize intercommunication between network slices across the VXLAN domain and the VLAN domain. Moreover, in the present application, a slice identifier can be carried in the VXLAN header or the ETH header, and the network node can forward the message according to the slice identifier carried in the VXLAN header or the ETH header, thereby making the technical solution of the present application applicable to VXLAN networks and VLAN networks.

[0021] Optionally, the first network domain is a GENEVE domain, the first message is a GENEVE message, the first message header is a GENEVE header, and the extended field of the GENEVE header is used to carry a first slice identifier; the second network domain is a VLAN domain, the second message is a VLAN message, the second message header is an Ethernet header, and the slice indication field of the Ethernet header is used to carry a second slice identifier.

[0022] The technical solution provided by the present application is that, when the first network domain is a GENEVE domain and the second network domain is a VLAN domain, the first network node realizes cross-domain intercommunication between the first network slice in the first network domain and the second network slice in the second network domain, that is, realizes intercommunication between the first network slice and the second network slice across the GENEVE domain and the VLAN domain. Therefore, the present application can realize intercommunication between network slices across the GENEVE domain and the VLAN domain. Moreover, in the present application, a slice identifier can be carried in a GENEVE header or an ETH header, and the network node can forward the message according to the slice identifier carried in the GENEVE header or the ETH header, thereby making the technical solution of the present application applicable to GENEVE networks and VLAN networks.

[0023] Optionally, the first network domain is an SRv6 domain, the first message is an SRv6 message, the first message header is HBH or DOH, and the HBH or the DOH is used to carry the first slice identifier; the second network domain is a VLAN domain, the second message is a VLAN message, the second message header is an Ethernet header, and the slice indication field of the Ethernet header is used to carry the second slice identifier.

[0024] The technical solution provided by the present application is that, when the first network domain is an SRv6 domain and the second network domain is a VLAN domain, the first network node realizes cross-domain intercommunication between the first network slice in the first network domain and the second network slice in the second network domain, that is, realizes intercommunication between the first network slice and the second network slice across the SRv6 domain and the VLAN domain. Therefore, the present application can realize intercommunication between network slices across the SRv6 domain and the VLAN domain. Moreover, in the present application, a slice identifier can be carried in the HBH, DOH or ETH header, and the network node can forward the message according to the slice identifier carried in the HBH, DOH or ETH header, thereby making the technical solution of the present application applicable to SRv6 networks and VLAN networks.

[0025] Optionally, the first network domain is an IPv6 domain, the first message is an IPv6 message, and the first message header is an IPv6 extension header, which is used to carry a first slice identifier; the second network domain is a VLAN domain, the second message is a VLAN message, and the second message header is an ETH header, and the slice indication field of the ETH header is used to carry the second slice identifier.

[0026] The technical solution provided by the present application is that, when the first network domain is an IPv6 domain and the second network domain is a VLAN domain, the first network node realizes cross-domain intercommunication between the first network slice in the first network domain and the second network slice in the second network domain, that is, realizes intercommunication between the first network slice and the second network slice across the IPv6 domain and the VLAN domain. Therefore, the present application can realize intercommunication between network slices across the IPv6 domain and the VLAN domain. Moreover, in the present application, a slice identifier can be carried in the IPv6 extension header or the ETH header, and the network node can forward the message according to the slice identifier carried in the IPv6 extension header or the ETH header, thereby making the technical solution of the present application applicable to IPv6 networks and VLAN networks.

[0027] In a second aspect, a message forwarding method is provided, applied to a second network node located at an ingress of a first network domain. The method includes: the second network node obtaining a first message based on an original message from a user equipment, the first message including a first message header matching the first network domain, the first message header including a first slice identifier indicating a first network slice; and the second network node sending the first message to the first network domain based on the second slice identifier. The first network slice is deployed in the first network domain.

[0028] Optionally, the sending of the first message by the second network node in the first network domain based on the first slice identifier includes: the sending of the first message by the second network node to a first network node located at a junction of the first network domain and a second network domain based on the first slice identifier, where the second network domain is different from the first network domain. The second network domain is deployed with a second network slice.

[0029] The technical solution provided by the present application is that after the second network node located at the entrance of the first network domain obtains the first message, it sends the first message to the first network node located at the junction of the first network domain and the second network domain based on the first slice identifier in the first message header included in the first message. After receiving the first message, the first network node can obtain the second message based on the second network domain and the first message, and send the second message in the second network domain based on the second slice identifier for indicating the second network slice in the second message header included in the second message, thereby realizing the switching of the first network slice in the first network domain and the second network slice in the second network domain, thereby realizing cross-domain intercommunication between the first network slice and the second network slice, avoiding the complex configuration of the network node to re-identify the service and the degradation of forwarding efficiency when the message crosses domains, and improving the message forwarding efficiency.

[0030] Optionally, the first network domain is a VLAN domain, the first message is a VLAN message, the first message header is an ETH header, and the slice indication field of the ETH header is used to carry a first slice identifier.

[0031] The technical solution provided by the present application can carry a slice identifier in the ETH header of the VLAN message when the first network domain is a VLAN domain, and the network node can forward the VLAN message according to the slice identifier carried in the ETH header, thereby making the technical solution of the present application applicable to the VLAN network.

[0032] Optionally, the first network domain is a VXLAN domain, the first message is a VXLAN message, the first message header is a VXLAN header, and the reserved field or extended field of the VXLAN header is used to carry the first slice identifier.

[0033] The technical solution provided by the present application can carry a slice identifier in the VXLAN header of the VXLAN message when the first network domain is a VXLAN domain, and the network node can forward the VXLAN message according to the slice identifier carried in the VXLAN header, thereby making the technical solution of the present application applicable to the VXLAN network.

[0034] Optionally, the first network domain is a GENEVE domain, the first message is a GENEVE message, the first message header is a GENEVE header, and the extension field of the GENEVE header is used to carry the first slice identifier.

[0035] The technical solution provided by the present application can carry a slice identifier in the GENEVE header of the GENEVE message when the first network domain is a GENEVE domain, and the network node can forward the GENEVE message according to the slice identifier carried in the GENEVE header, thereby making the technical solution of the present application applicable to the GENEVE network.

[0036] Optionally, the first network domain is an SRv6 domain, the first message is an SRv6 message, the first message header is HBH or DOH, and the HBH or the DOH is used to carry the first slice identifier.

[0037] The technical solution provided by the present application can carry a slice identifier in the HBH or DOH of the SRv6 message when the first network domain is an SRv6 domain, and the network node can forward the SRv6 message according to the slice identifier carried in the HBH or the DOH, thereby making the technical solution of the present application applicable to the SRv6 network.

[0038] Optionally, the first network domain is an IPv6 domain, the first message is an IPv6 message, and the first message header is an IPv6 extension header, which is used to carry a first slice identifier.

[0039] The technical solution provided by the present application can carry a slice identifier in the IPv6 extension header of the IPv6 message when the first network domain is an IPv6 domain, and the network node can forward the IPv6 message according to the slice identifier carried in the IPv6 extension header, thereby making the technical solution of the present application applicable to the IPv6 network.

[0040] The VLAN domain provided in the above optional technical solution of the present application is a layer-2 network domain, and correspondingly, the ETH header is a layer-2 message header. The SRv6 domain and the IPv6 domain are both layer-3 network domains, and correspondingly, the HBH, DOH, and IPv6 extension headers are all layer-3 message headers. The VXLAN domain and the GENEVE domain are both upper-layer (overlay) network domains, and correspondingly, the VXLAN header and the GENEVE domain are both overlay message headers. Among them, the overlay network is an upper-layer virtual network built based on the underlying (underlay) network. The underlay network can be a layer-2 network or a layer-3 network. The underlay network is also called the underlying bearer network, the underlying physical network, the lower-layer bearer network, the lower-layer physical network, etc. The above-mentioned VXLAN domain and GENEVE domain are only optional implementations of the overlay network domain. The overlay network domain may also include other upper-layer virtual networks built based on the underlay network.

[0041] In addition, in the above optional technical solutions of the present application, when the first network domain is a VLAN domain, the second network domain can be a VXLAN domain, a GENEVE domain, an SRv6 domain, or an IPv6 domain; when the second network domain is a VLAN domain, the first network domain can be a VXLAN domain, a GENEVE domain, an SRv6 domain, or an IPv6 domain; therefore, the type of the first network domain is different from the type of the second network domain. Regarding the combination of the first network domain and the second network domain, in addition to the combination provided by the above optional technical solutions, the combination of the first network domain and the second network domain can also be other combination methods. For example, when the first network domain is a VXLAN domain, the second network domain can be a GENEVE domain, an SRv6 domain, or an IPv6 domain; when the first network domain is a GENEVE domain, the second network domain can be a VXLAN domain, an SRv6 domain, or an IPv6 domain.

[0042] In a third aspect, a message forwarding device is provided, comprising modules for executing the method provided in the first aspect or any optional manner of the first aspect.

[0043] In a fourth aspect, a message forwarding device is provided, comprising modules for executing the method provided in the second aspect or any optional manner of the second aspect.

[0044] The modules in the third and fourth aspects above may be implemented based on software, hardware, or a combination of software and hardware, and the modules may be arbitrarily combined or divided based on specific implementations.

[0045] In the fifth aspect, a message forwarding device is provided, comprising a memory and a processor; the memory is used to store a computer program; the processor is used to execute the computer program stored in the memory, so that the message forwarding device executes the method provided in the first aspect or any optional manner of the first aspect, or so that the message forwarding device executes the method provided in the second aspect or any optional manner of the second aspect.

[0046] In the sixth aspect, a message forwarding device is provided, including a main control board and an interface board, wherein the main control board and the interface board are used to implement the method provided in the above-mentioned first aspect or any optional method of the first aspect, or the main control board and the interface board are used to implement the method provided in the above-mentioned second aspect or any optional method of the second aspect.

[0047] In the seventh aspect, a message forwarding system is provided, including a first network node and a second network node, the first network node includes the message forwarding device provided in the third aspect, fifth aspect or sixth aspect above, and the second network node includes the message forwarding device provided in the fourth aspect, fifth aspect or sixth aspect above.

[0048] In an eighth aspect, a computer-readable storage medium is provided, in which a computer program is stored. When the computer program is executed, it implements the method provided in the first aspect or any optional manner of the first aspect, or implements the method provided in the second aspect or any optional manner of the second aspect.

[0049] In the ninth aspect, a computer program product is provided, which includes a program or code, and when the program or code is executed, it implements the method provided by the first aspect or any optional manner of the first aspect, or implements the method provided by the second aspect or any optional manner of the second aspect.

[0050] In the tenth aspect, a chip is provided, which includes a programmable logic circuit and / or program instructions. When the chip is running, it is used to implement the method provided by the first aspect or any optional method of the first aspect, or to implement the method provided by the second aspect or any optional method of the second aspect.

[0051] The beneficial effects of the technical solution provided by this application include:

[0052] The technical solution provided by the present application is that a first message from a first network domain includes a first message header matching the first network domain, the first message header includes a first slice identifier for indicating a first network slice, and a first network node at the junction of the first network domain and the second network domain receives the first message and obtains a second message based on the second network domain and the first message, and sends the second message in the second network domain based on the second slice identifier for indicating the second network slice in the second message header included in the second message. In this way, the first network node can realize the switching of the first network slice in the first network domain and the second network slice in the second network domain, thereby realizing cross-domain intercommunication between the first network slice and the second network slice, avoiding the complex configuration of the network node to re-identify the service and the degradation of forwarding efficiency when the message crosses domains, and improving the message forwarding efficiency. In addition, the present application can carry slice identifiers in message headers such as ETH headers, VXLAN headers, GENEVE headers, IPv6 extension headers, HBH or DOH, and network nodes can forward messages according to the slice identifiers carried in these message headers, thereby making the technical solution of the present application applicable to network scenarios such as VLAN networks, VXLAN networks, GENEVE networks, IPv6 networks, and SRv6 networks. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] FIG1 is a schematic diagram of the underlying implementation of a network slice;

[0054] FIG2 is a schematic diagram of an application scenario provided by an embodiment of the present application;

[0055] FIG3 is a schematic diagram of another application scenario provided by an embodiment of the present application;

[0056] FIG4 is a schematic diagram of another application scenario provided by an embodiment of the present application;

[0057] FIG5 is a flow chart of a message forwarding method provided in an embodiment of the present application;

[0058] FIG6 is a schematic diagram of an original message provided in an embodiment of the present application;

[0059] FIG7 is a schematic diagram of a first message provided in an embodiment of the present application;

[0060] FIG8 is a schematic diagram of another first message provided in an embodiment of the present application;

[0061] FIG9 is a schematic diagram of another first message provided in an embodiment of the present application;

[0062] FIG10 is a schematic diagram of another first message provided in an embodiment of the present application;

[0063] FIG11 is a schematic diagram of another first message provided in an embodiment of the present application;

[0064] FIG12 is a schematic diagram of another first message provided in an embodiment of the present application;

[0065] FIG13 is a schematic diagram of another first message provided in an embodiment of the present application;

[0066] FIG14 is a schematic diagram of a message forwarding method provided in an embodiment of the present application;

[0067] FIG15 is a schematic diagram of a message forwarding device provided in an embodiment of the present application;

[0068] FIG16 is a schematic diagram of another message forwarding device provided in an embodiment of the present application;

[0069] FIG17 is a schematic diagram of another message forwarding device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0070] The embodiments of the present application will be further described below with reference to the accompanying drawings.

[0071] The Internet Protocol (IP) bearer network is a resource-sharing network, which means that different services may compete for network resources. To ensure the service-level agreement (SLA) quality of high-priority services, quality of service (QoS) and hierarchical quality of service (HQoS) technologies have been proposed. These technologies prioritize forwarding high-priority services to ensure SLA quality for high-priority services. However, these technologies still prevent low-priority services from competing with high-priority services, making it difficult to guarantee deterministic SLA quality and service experience for high-priority services. High-priority services include higher-priority services and services for higher-priority users, while low-priority services include lower-priority services and services for lower-priority users. For example, video services have a higher priority than email services, making video services a high-priority service and email services a low-priority service. For another example, for video service 1, user A's priority is higher than user B's, making user A's video service 1 a high-priority service and user B's video service 1 a low-priority service. For another example, for the email service 2, the priority of user A is lower than that of user B. The email service 2 of user A is a low-priority service, and the email service 2 of user B is a high-priority service.

[0072] To ensure deterministic SLA quality for high-priority services, slicing technology has been introduced. Slicing is a "hard" isolation technology that reserves resources for high-priority services. This technology allows them to exclusively use network resources, preventing low-priority services from competing for network resources and thus ensuring the SLA quality of high-priority services. Slicing technology is crucial for isolating different services and ensuring the SLA quality of high-priority services.

[0073] The underlying technologies used to achieve resource reservation and service isolation in slicing technology include flexible Ethernet (FlexE) technology, channelized sub-interface technology and flexible channel (FlexChannel) technology. General network equipment (such as routers, switches) can support one or more of the three underlying technologies, and these three underlying technologies can be nested to achieve "slice within a slice". The nested use of these three underlying technologies is shown in Figure 1. Referring to Figure 1, a physical interface is divided into multiple FlexE interfaces, a FlexE interface is divided into multiple channelized sub-interfaces or multiple flexible channels, and a channelized sub-interface can be divided into multiple flexible channels. Network slices can be deployed based on FlexE interfaces, channelized sub-interfaces or multiple flexible channels. Network slices deployed based on flexible channels or channelized sub-interfaces are sub-slices in the network slice deployed based on the FlexE interface to which the flexible channel or the channelized sub-interface belongs, thereby achieving "slice within a slice".

[0074] The industry's slice control solutions include: a slice control solution based on a flexible algorithm (Flex-Algo), a slice control solution based on an interface slice identifier, a slice control solution based on routing affinity attributes, and a slice control solution based on data plane slice identifiers. These slice control solutions are used to control packet forwarding so that packets of different services go through different network slice "hard pipes". Among them, the slice control solution based on Flex-Algo and the slice control solution based on routing affinity attributes both require running an interior gateway protocol (IGP) in the network, resulting in high complexity and limited applicable scenarios for these two slice control solutions. The slice control solution based on interface slice identifiers requires configuring slice identifiers on the interfaces of network devices, and the actual implementation is complex. The slice control solution based on data plane slice identifiers controls the forwarding of packets by carrying slice identifiers in the packets. This slice control solution is simple and efficient, and has a wider range of applicable scenarios. However, the current slice control solution based on the data plane carrying slice identifiers cannot achieve cross-domain interoperability of network slices, resulting in the need for network nodes to re-identify services when messages cross domains. The service identification process requires complex configuration, and the re-identification of services by network nodes is likely to affect the efficiency of message forwarding, making it difficult to achieve end-to-end (E2E) service slice protection. In addition, the current slice control solution based on the data plane carrying slice identifiers cannot be implemented in Layer 2 networks such as VLAN and overlay networks such as VXLAN and GENEVE networks. The current campus networks are generally VLAN or VXLAN, and the next generation VXLAN determined by the Internet Engineering Task Force (IETF) is GENEVE. Therefore, to achieve E2E service slice protection, the data plane solution needs to solve the problem of carrying slice identifiers (sliceID) on the VLAN, VXLAN or GENEVE data plane. Campus networks are generally Layer 2 VLAN networks or large virtual Layer 2 networks based on VXLAN and GENEVE. These networks simplify network operations and enable plug-and-play (i.e., devices can be used as soon as they are connected to the network). For security reasons, campus networks use MAC addresses for terminal and user identification, authentication, and secure traceability. Furthermore, they enable flexible service planning and deployment by decoupling the upper-layer service network from the underlying physical network (also known as the underlay network). Campus VLAN, VXLAN, and GENEVE Layer 2 or large Layer 2 networks will continue to exist and evolve over time.

[0075] The embodiment of the present application provides a message forwarding solution, in which the network nodes at the junction of different network domains can switch the slice identifier carried in the message when the message crosses the domain, thereby realizing the switching of the message between network slices in different network domains, realizing cross-domain intercommunication of network slices, avoiding the complex configuration of network nodes re-identifying services and the degradation of forwarding efficiency when the message crosses the domain, and improving the message forwarding efficiency. In addition, the different network domains in the present application may include VLAN domain, VXLAN domain, GENEVE domain, SRv6 domain, IPv6 domain, so the present application can realize the intercommunication of network slices across VLAN domain, VXLAN domain, GENEVE domain, SRv6 domain, and IPv6 domain, avoiding the complex configuration of re-identifying services and the degradation of forwarding efficiency when the message crosses the VLAN domain, VXLAN domain, GENEVE domain, SRv6 domain, and IPv6 domain. In addition, in the message forwarding solution provided by the present application, the slice identifier can be carried in the message headers such as the ETH header, VXLAN header, GENEVE header, IPv6 extension header, HBH or DOH, and the network node can forward the message according to the slice identifier carried in these message headers, thereby making the technical solution of the present application applicable to network scenarios such as VLAN network, VXLAN network, GENEVE network, IPv6 network, SRv6 network, etc.

[0076] The technical solution of this application is introduced below, and the application scenario of this application is first introduced.

[0077] An application scenario of an embodiment of the present application provides a message forwarding system, which includes at least two network domains. The at least two network domains are interconnected, and the at least two network domains may include network domains of different types.

[0078] Optionally, the at least two network domains include a first network domain and a second network domain, and the type of the first network domain is different from the type of the second network domain. In one example, the first network domain is a VLAN domain, and the second network domain is a VXLAN domain, a GENEVE domain, an SRv6 domain, or an IPv6 domain. In another example, the second network domain is a VLAN domain, and the first network domain is a VXLAN domain, a GENEVE domain, an SRv6 domain, or an IPv6 domain. The combination of the first network domain and the second network domain is only exemplified here, and the combination of the first network domain and the second network domain can also be other combinations. For example, the first network domain is a VXLAN domain, and the second network domain is a GENEVE domain, an SRv6 domain, or an IPv6 domain; for another example, when the first network domain is a GENEVE domain, the second network domain can be a VXLAN domain, an SRv6 domain, or an IPv6 domain, and this embodiment of the present application does not limit this.

[0079] Among them, the VLAN domain is a Layer 2 network domain, the SRv6 domain and IPv6 domain are both Layer 3 network domains, and the VXLAN domain and GENEVE domain are both overlay network domains. The overlay network domain is an upper-layer virtual network built on the underlying (underlay) network. The overlay network domain is also called the overlay virtual network domain, overlay service network domain, etc. The underlay network can be a Layer 2 network or a Layer 3 network. The underlay network is also called the underlying bearer network, underlying physical network, lower-layer bearer network, lower-layer physical network, etc. Optionally, the Layer 3 network domain is the Internet, carrier private network, wide area network (WAN), software-defined wide area network (SDWAN), etc.

[0080] Optionally, the at least two network domains further include a cloud network, which is used to provide various cloud services, including cloud computing services, cloud storage services, and the like. In the present application, the at least two network domains include a campus network, which can be a VLAN domain, a VXLAN domain, or a GENEVE domain. Different campus networks can be directly interconnected, or different campus networks can be interconnected via an SRv6 domain, an IPv6 domain, or the like, thereby enabling mutual access between different campus networks. The campus network can be interconnected with the cloud network via an SRv6 domain, an IPv6 domain, or the like, enabling the campus network to access various cloud services provided by the cloud network.

[0081] Each of the at least two network domains includes multiple network nodes. Network nodes can be physical nodes or virtual nodes. Physical nodes can be network devices such as switches and routers, while virtual nodes can be virtual switches and routers created within physical nodes. Network nodes in a cloud network can be cloud servers, each of which can provide at least one cloud service. The multiple cloud servers are interconnected to form the cloud network.

[0082] As an example, please refer to Figure 2, which shows a schematic diagram of a message forwarding system provided in an embodiment of the present application. The message forwarding system includes campus networks 1 to 3 (i.e., campus network 1, campus network 2, and campus network 3), the Internet / private network / WAN (i.e., the Internet or private network or WAN), and a cloud network. Campus network 1 is a VLAN domain. Campus network 2 is a VXLAN domain. Campus network 3 is a GENEVE domain. Campus networks 1 to 3 and the cloud network are interconnected through the Internet / private network / WAN. Any two network domains in campus networks 1 to 3 can access each other through the Internet / private network / WAN, and campus networks 1 to 3 can access the cloud services provided by the cloud network through the Internet / private network / WAN.

[0083] As another example, please refer to Figure 3, which shows a schematic diagram of another message forwarding system provided by an embodiment of the present application. The message forwarding system includes network domain 1 and network domain 2, and network domain 1 and network domain 2 are interconnected. Network domain 1 and network domain 2 are respectively VLAN domains, VXLAN domains, GENEVE domains, SRv6 domains, or IPv6 domains, and the type of network domain 1 is different from the type of network domain 2. For example, network domain 1 is a VLAN domain, and network domain 2 is a VXLAN domain, GENEVE domain, SRv6 domain, or IPv6 domain. For another example, network domain 2 is a VLAN domain, and network domain 1 is a VXLAN domain, GENEVE domain, SRv6 domain, or IPv6 domain. For another example, network domain 1 is a VXLAN domain, and network domain 2 is a GENEVE domain, SRv6 domain, or IPv6 domain. For another example, network domain 1 is a GENEVE domain, and network domain 2 is a VXLAN domain, SRv6 domain, or IPv6 domain. As shown in Figure 1, network node A and network node B are both located at the edge of network domain 1, and network node B and network node C are both located at the edge of network domain 2. Therefore, network node B is located at the junction of network domains 1 and 2. In one example, network node A is located at the entrance of network domain 1, network node B is located at the exit of network domain 1 and at the entrance of network domain 2, and network node C is located at the exit of network domain 2. Network node A is the entrance node of network domain 1, network node B is the exit node of network domain 1 and the entrance node of network domain 2, and network node C is the exit node of network domain 2. In another example, network node A is located at the exit of network domain 1, network node B is located at the entrance of network domain 1 and at the exit of network domain 2, and network node C is located at the entrance of network domain 2. Network node A is the exit node of network domain 1, network node B is the entry node of network domain 1 and the exit node of network domain 2, and network node C is the entry node of network domain 2. Optionally, network node A and network node C are client provider edge (CPE) devices, and network node B is a point-of-presence (POP) device.

[0084] Referring to Figure 3, network domain 1 is a VLAN domain and network domain 2 is a VXLAN domain. For example, network node A is the entry node of network domain 1, network node B is the exit node of network domain 1 and the entry node of network domain 2, network node C is the exit node of network domain 2, network slice 1 is deployed in network domain 1, and network slice 2 is deployed in network domain 2. After network node A receives the original message P0 from the user device (the user device is connected to network node A and accesses network domain 1 through network node A, and the user device is not shown in Figure 3 for simplicity), network node A obtains message P1 based on the original message P0. Message P1 includes an ETH header that matches network domain 1 (VLAN domain), and the ETH header includes a slice identifier 1 for indicating network slice 1. Network node A determines network slice 1 based on slice identifier 1, and network node A forwards message P1 to network node B through network slice 1. After network node B receives message P1, network node B determines slice identifier 2 for indicating network slice 2 based on slice identifier 1 in message P1. Network node B obtains message P2 based on message P1, slice identifier 2 and network domain 2 (VXLAN domain). Message P2 includes a VXLAN header that matches network domain 2, and the VXLAN header includes slice identifier 2. Network node B determines network slice 2 based on slice identifier 2, and network node B forwards message P2 to network node C through network slice 2. After network node C receives message P2, network node C performs VXLAN decapsulation on message P2 to obtain the original message P0, and forwards the original message P0. Therefore, the present application carries a slice identifier in the ETH header or the VXLAN header, so that the network node can forward the message according to the slice identifier carried in the ETH header or the VXLAN header, so that the present application can be applied to VLAN domains and / or VXLAN domains. In addition, the network node B located at the junction of network domain 1 and network domain 2 can switch between slice identifier 1 and slice identifier 2, thereby enabling the switching of messages between network slice 1 and network slice 2, and realizing cross-domain intercommunication between network slice 1 and network slice 2, avoiding the complex configuration of network nodes to re-identify services and the degradation of forwarding efficiency when messages cross domains, thereby improving message forwarding efficiency.

[0085] As another example, please refer to Figure 4, which shows a schematic diagram of another message forwarding system provided by an embodiment of the present application. The message forwarding system includes network domain 1, network domain 2, and network domain 3, and network domain 2 is interconnected with network domain 1 and network domain 3 respectively. Network domain 1, network domain 2, and network domain 3 are respectively VLAN domains, VXLAN domains, GENEVE domains, SRv6 domains, or IPv6 domains, and at least two of network domains 1, network domain 2, and network domain 3 are of different types. For example, network domain 1 is a VLAN domain, network domain 2 is an IPv6 domain, and network domain 3 is a GENEVE domain. For another example, network domain 1 is a VXLAN domain, network domain 2 is an IPv6 domain, and network domain 3 is a GENEVE domain. For another example, network domain 1 is a VLAN domain, network domain 2 is a VXLAN domain, and network domain 3 is a GENEVE domain. As shown in Figure 1, network node A and network node B are both located at the edge of network domain 1, network node B and network node C are both located at the edge of network domain 2, and network node C and network node D are both located at the edge of network domain 3. Thus, network node B is located at the junction of network domains 1 and 2, and network node C is located at the junction of network domains 2 and 3. In one example, network node A is located at the entrance of network domain 1, network node B is located at the exit of network domain 1 and at the entrance of network domain 2, network node C is located at the exit of network domain 2 and at the entrance of network domain 3, and network node D is located at the exit of network domain 3. Network node A is the entrance node of network domain 1, network node B is the exit node of network domain 1 and the entrance node of network domain 2, network node C is the exit node of network domain 2 and the entrance node of network domain 3, and network node D is the exit node of network domain 3. In another example, network node A is located at the egress of network domain 1, network node B is located at the ingress of network domain 1 and at the egress of network domain 2, network node C is located at the ingress of network domain 2 and at the egress of network domain 3, and network node D is located at the ingress of network domain 3. Network node A is the egress node of network domain 1, network node B is the ingress node of network domain 1 and the egress node of network domain 2, network node C is the ingress node of network domain 2 and the egress node of network domain 3, and network node D is the ingress node of network domain 3. Optionally, network node A and network node D are CPE devices, and network node B and network node C are POP devices.

[0086] Referring to Figure 4, network domain 1 is a VLAN domain, network domain 2 is an IPv6 domain, and network domain 3 is a GENEVE domain. For example, network node A is the entry node of network domain 1, network node B is the egress node of network domain 1 and the entry node of network domain 2, network node C is the egress node of network domain 2 and the entry node of network domain 3, network node D is the egress node of network domain 3, network slice 1 is deployed in network domain 1, network slice 2 is deployed in network domain 2, and network slice 3 is deployed in network domain 3. After network node A receives an original message P0 from a user device (the user device is connected to network node A and accesses network domain 1 through network node A; the user device is not shown in FIG4 for simplicity), network node A obtains message P1 based on original message P0. Message P1 includes an ETH header that matches network domain 1 (VLAN domain). The ETH header includes slice identifier 1 for indicating network slice 1. Network node A determines network slice 1 based on slice identifier 1, and network node A forwards message P1 to network node B via network slice 1. After network node B receives message P1, network node B determines slice identifier 2 for indicating network slice 2 based on slice identifier 1 in message P1. Network node B obtains message P2 based on message P1, slice identifier 2, and network domain 2 (IPv6 domain). Message P2 includes an IPv6 extension header that matches network domain 2. The IPv6 extension header includes slice identifier 2. Network node B determines network slice 2 based on slice identifier 2, and network node B forwards message P2 to network node C via network slice 2. After network node C receives message P2, network node C determines slice identifier 3 for indicating network slice 3 based on slice identifier 2 in message P2. Network node C obtains message P3 based on message P2, slice identifier 3 and network domain 3 (GENEVE domain). Message P3 includes a GENEVE header that matches network domain 3. The GENEVE header includes slice identifier 3. Network node C determines network slice 3 based on slice identifier 3. Network node C forwards message P3 to network node D through network slice 3. After network node D receives message P3, network node D performs GENEVE decapsulation on message P3 to obtain the original message P0, and forwards the original message P0. Therefore, the present application carries a slice identifier in the ETH header, IPv6 extension header or GENEVE header, so that the network node can forward the message according to the slice identifier carried in the ETH header, the IPv6 extension header or the GENEVE header, so that the present application can be applied to the VLAN domain and / or IPv6 domain and / or GENEVE header.Furthermore, network node B located at the junction of network domain 1 and network domain 2 can switch slice ID 1 and slice ID 2, thereby enabling message switching between network slice 1 and network slice 2, and achieving cross-domain intercommunication between network slice 1 and network slice 2. Network node C located at the junction of network domain 2 and network domain 3 can switch slice ID 2 and slice ID 3, thereby enabling message switching between network slice 2 and network slice 3, and achieving cross-domain intercommunication between network slice 2 and network slice 3. Ultimately, cross-domain intercommunication between network slices 1 and 3 can be achieved, avoiding the complex configuration of network nodes re-identifying services and the degradation of forwarding efficiency when messages cross domains.

[0087] The message forwarding system shown in Figures 2 to 4 is for illustrative purposes only and is not intended to limit the technical solutions of this application. During implementation, the message forwarding system may include more or fewer network domains than those shown in Figures 2 to 4. The message forwarding system may also include a control device to control the network domains in the message forwarding system, which is not limited in this embodiment of the application.

[0088] The above is an introduction to the application scenarios of this application. The following introduces the method embodiments of this application.

[0089] Please refer to Figure 5, which shows a flowchart of a message forwarding method provided in an embodiment of the present application. The message forwarding method is applied to a message forwarding system including a first network node and a second network node, the first network node is located at the junction of the first network domain and the second network domain, and the second network node is located at the entrance of the first network domain. In one example, the message forwarding system is shown in Figure 3, the first network domain is network domain 1, the second network domain is network domain 2, the first network node is network node B, and the second network node is network node A. In another example, the message forwarding system is shown in Figure 4, the first network domain is network domain 1, the second network domain is network domain 2, the first network node is network node B, and the second network node is network node A; or, the first network domain is network domain 2, the second network domain is network domain 3, the first network node is network node C, and the second network node is network node B. As shown in Figure 5, the method includes the following steps S501 to S506.

[0090] S501. The second network node receives an original message from a user equipment.

[0091] The second network node receives an original message from a user equipment from a previous-hop node of the second network node. The second network node is an ingress node of a first network domain, and the previous-hop node is located outside the first network domain. For example, the previous-hop node is the user equipment or another node or device connected between the user equipment and the second network node.

[0092] Optionally, the second network node is a head node of the first tunnel in the first network domain. For example, the first network domain is a VLAN domain, a VXLAN domain, a GENEVE domain, an SRv6 domain, or an IPv6 domain, and correspondingly, the first tunnel is a VLAN tunnel, a VXLAN tunnel, a GENEVE tunnel, an SRv6 tunnel, or an IPv6 tunnel.

[0093] In an embodiment of the present application, the original message from the user device is a layer 2 message or a layer 3 message, and the original message includes a payload and a message header. The layer 2 message can be an ETH message, and the layer 3 message can be an IP message. In one example, the original message is a layer 2 message, and the original message includes a payload, a user datagram protocol (UDP) header, and an ETH header. The UDP header is used to carry the UDP information of the original message, and the ETH header is used to carry the layer 2 information of the original message. The layer 2 information includes a source media access control (SMAC) address, a destination media access control (DMAC) address, etc. In another example, the original message is a layer 3 message, and the original message includes a payload, a UDP header, an IP header, and an ETH header. The UDP header is used to carry the UDP information of the original message, the IP header is used to carry the layer 3 information of the original message, and the layer 3 information includes an IP five-tuple, etc., and the ETH header is used to carry the layer 2 information of the original message. Taking the original message as a Layer 3 message as an example, the original message is shown in Figure 6. The original message includes a payload Q and, in sequence, a UDP header 1, an IP header 1, and an ETH header 1 encapsulated outside the payload Q. The ETH header 1 includes an SMAC field and a DMAC field. The SMAC field is used to carry the SMAC address of the original message, and the DMAC field is used to carry the DMAC address of the original message. The original message shown in Figure 6 is for example only. The original message may also include content not shown in Figure 6, and this application does not limit this.

[0094] S502. The second network node obtains a first message based on the original message, where the first message includes a first message header that matches the first network domain, and the first message header includes a first slice identifier for indicating a first network slice.

[0095] The second network node may add a first slice identifier for indicating a first network slice to the original message to obtain a first message, where the first network slice is deployed in the first network domain. Optionally, the first network slice is a network slice within the first tunnel. In one embodiment, the second network node determines the first network slice for forwarding the original message based on the traffic characteristic information of the original message, and the second network node adds a first slice identifier for indicating the first network slice to the original message to obtain the first message. The traffic characteristic information includes at least one of IP information and MAC information. For example, the IP information includes an IP five-tuple, an IP triplet, etc., and the MAC information includes SMAC, DMAC, etc.

[0096] In an embodiment of the present application, the first message includes a first message header that matches a first network domain, and the first slice identifier is included in the first message header. The first network domain is a VLAN domain, a VXLAN domain, a GENEVE domain, an SRv6 domain, or an IPv6 domain. Depending on the first network domain, the first message and the first message header are different. The following describes the implementation process of S502 in five embodiments, taking the first network domain as an example, namely, a VLAN domain, a VXLAN domain, a GENEVE domain, an SRv6 domain, and an IPv6 domain.

[0097] First embodiment: The first network domain is a VLAN domain, the first message is a VLAN message (a VLAN message is a layer 2 message), the first message header is an ETH header (an ETH header is a layer 2 message header), the ETH header includes a slice indication field, the slice indication field is used to carry a slice identifier, and the first slice identifier is carried in the slice indication field. Optionally, the first message header also includes a VLAN tag, and the slice indication field is located between the VLAN tag and the payload of the first message. Optionally, the original message includes an ETH header, and the second network node adds the VLAN tag and the slice indication field to the ETH header of the original message, and adds the first slice identifier to the slice indication field to obtain the first message.

[0098] In one example, a first message is shown in FIG7 . The first message includes a payload Q, a UDP header 1, an IP header 1, and an ETH header 2. The ETH header 2 is the first message header that matches the first network domain (VLAN domain). The ETH header 2 includes a DMAC field, an SMAC field, a VLAN tag field, and a slice indication field. The VLAN tag field is used to carry a VLAN tag. The slice indication field includes an Ethernet type subfield and a slice identifier subfield. The Ethernet type subfield is used to indicate the slice indication field. The value of the Ethernet type subfield can be 0x8100 or a newly defined value. The slice identifier subfield is used to carry a slice identifier. Referring to FIG6 and FIG7 , the second network node can add a VLAN tag field and a slice indication field to the ETH header 1 of the original message shown in FIG6 , and add a VLAN tag to the VLAN tag field. The second network node also sets the value of the Ethernet type subfield to 0x8100 or a newly defined value. Furthermore, the second network node adds the first slice identifier to the slice identifier subfield, thereby obtaining the first message shown in FIG7 .

[0099] In another example, the first message is shown in Figure 8. The first message includes a payload Q, a UDP header 1, an IP header 1, and an ETH header 2. The ETH header 2 is the first message header that matches the first network domain (VLAN domain). The ETH header 2 includes a DMAC field, an SMAC field, a VLAN tag field, and a slice indication field. The VLAN tag field is used to carry a VLAN tag. The slice indication field includes a deterministic IP (DIP) subfield, a reserved subfield, and a slice identification subfield. The DIP subfield is used to carry DIP information, and the slice identification subfield is used to carry a slice identification. As shown in Figure 8, the DIP subfield includes an Ethernet type space, a tiger (T) space, a label space, a next header space, and two reserved spaces. The value of the Ethernet type space is 0x8888 to indicate the DIP subfield. The T space is used to indicate whether the DIP subfield is enabled, and the next header space is used to indicate the slice identification subfield. 6 and 8 , the second network node may add a VLAN tag field and a slice indication field to the ETH header 1 of the original message shown in FIG6 , and add a VLAN tag to the VLAN tag field, and the second network node may set the value of the Ethernet type space to 0x8888, and set the next header space to indicate the slice identifier subfield, and the second network node may add a first slice identifier to the slice identifier subfield to obtain the first message shown in FIG8 .

[0100] In the first message shown in Figures 7 and 8, the VLAN tag field may include an Ethernet type subfield, a priority (PRI) subfield, a canonical format indicator (CFI) subfield, and a VLAN identifier (VID) subfield. For the sake of simplicity, these subfields are not shown in Figures 7 and 8. For the meaning of each subfield in the VLAN tag field, please refer to the VLAN protocol. Optionally, the ETH header 2 includes an outer VLAN tag field and an inner VLAN tag field. The VLAN tag field shown in Figures 7 and 8 is the outer VLAN tag field, and the slice indication field may be the inner VLAN tag field. For the first message shown in Figure 8, the above-mentioned DIP subfield is also called a DIP header. For the first message shown in Figure 7, the format of the slice indication field can also be set to be the same as the format of the VLAN tag field. In the slice indication field, the PRI subfield and the CFI subfield can be reserved, and the VID subfield can be used as the slice identification field to carry the first slice identification. Furthermore, for the first message shown in Figure 7, in the implementation method where the value of the Ethernet type subfield is 0x8100, in order to avoid the conflict between the inner VLAN tag field (i.e., the slice indication field) carrying the slice identifier and the double-layer VLAN feature, a control table item can be configured inside the device to distinguish whether the inner VLAN tag field carries a slice identifier or a VLAN tag; for example, a slice control table item and a VLAN control table item are configured inside the device. If the content carried by the inner VLAN tag field hits the slice control table item, it is determined that the content carried by the inner VLAN tag field is a slice identifier; if the content carried by the inner VLAN tag field hits the VLAN control table item, it is determined that the content carried by the inner VLAN tag field is a VLAN tag. Network processor (NP) chips and most application-specific integrated circuit (ASIC) chips support this implementation method. For the first message shown in FIG7 , the implementation method of using a newly defined value for the Ethernet type subfield has high scalability. NP chips can support this implementation method, or relevant capabilities can be pre-embedded in ASIC chips to support this implementation method, or an external field-programmable gate array (FPGA) chip can support this implementation method. For the first message shown in FIG8 , NP chips can support this implementation method, or relevant capabilities can be pre-embedded in ASIC chips to support this implementation method, or an external FPGA chip can support this implementation method.

[0101] Second embodiment: The first network domain is a VXLAN domain, the first message is a VXLAN message, the first message header is a VXLAN header, the VXLAN header includes a reserved field or an extended field, the reserved field or the extended field is used to carry a slice identifier, and the first slice identifier is carried in the reserved field or the extended field. In one example, the VXLAN header includes a reserved field, and the first slice identifier is carried in the reserved field. In another example, the VXLAN header includes an extended field, and the first slice identifier is carried in the extended field. Optionally, the second network node encapsulates the VXLAN header in the original message, and the second network node adds the first slice identifier in the VXLAN header to obtain the first message.

[0102] In an example, the first message is shown in Figure 9, and the first message includes a payload Q, a UDP header 1, an IP header 1, an ETH header 1, a VXLAN header, a UDP header 2, an IP header 2, and an ETH header 3. The VXLAN header is the first message header that matches the first network domain (VXLAN domain), and the VXLAN header includes a flag field, a VXLAN network identifier (VNI) field, and two reserved fields. The VNI field is used to carry the VXLAN ID, and the flag field is used to indicate the legitimacy of the VXLAN ID. For example, the flag field includes 8 flag bits, and the third flag bit arranged from low to high in the 8 flag bits is used to indicate the legitimacy of the VXLAN ID. The remaining flag bits in the 8 flag bits are all reserved flag bits. Typically, the third flag bit is set to 1 to indicate that the VXLAN ID carried by the VNI field is legal. Reserved field 1 is used to carry a slice identifier. 6 and 9, the second network node can encapsulate the VXLAN header, UDP header 2, IP header 2 and ETH header 3 in sequence outside the original message shown in FIG6, and the second network node adds the first slice identifier in the reserved field 1 in the VXLAN header to obtain the first message shown in FIG9. FIG9 takes the example of carrying the slice identifier in the reserved field 1, and the slice identifier can also be carried in the reserved field 2. Since the length of the reserved field 1 is greater than the length of the reserved field 2 (the length of the reserved field 1 is 24 bits, and the length of the reserved field 2 is 8 bits), compared with the reserved field 2, the reserved field 1 can support longer slice identifiers and can support cross-domain unified planning of slice identifiers.

[0103] In another example, the first message is shown in Figure 10. The first message includes a payload Q, a UDP header 1, an IP header 1, an ETH header 1, a VXLAN header, a UDP header 2, an IP header 2, and an ETH header 3. The VXLAN header is the first message header that matches the first network domain (VXLAN domain). The VXLAN header includes a flag field, a VNI field, two reserved fields, and an extension field. The VNI field is used to carry the VXLAN ID, and the flag field is used to indicate the legitimacy of the VXLAN ID. The extension field is a message header extended in the VXLAN header. The extension field is also called a VXLAN extension header. The extension field needs to be processed hop by hop, and the reserved field 2 is used to indicate that the extension field needs to be processed hop by hop. The extension field includes a next header subfield, a length subfield, an option type subfield, an option data length subfield, a flags subfield, a reserved subfield, and a slice identifier subfield. The next header subfield is used to indicate the extension field. The length subfield is used to indicate the total length of the data subfield in the extension field (that is, the total length of the subfields in the extension field excluding the next header subfield and the length subfield). The option type subfield, the option data length subfield, the flag subfield, the reserved subfield and the slice identifier subfield constitute an option subfield, the option type subfield is used to indicate the type of the option subfield, the option data length subfield is used to indicate the length of the data subfield in the option subfield (that is, the total length of the subfields in the option subfield excluding the option type subfield and the option data length subfield), and the slice identifier subfield is used to carry a slice identifier. Referring to Figures 6 and 10, the second network node can encapsulate the VXLAN header, UDP header 2, IP header 2 and ETH header 3 in sequence outside the original message shown in Figure 6. The second network node sets an extension field in the VXLAN header and adds a first slice identifier in the extension field to obtain the first message shown in Figure 10.

[0104] In another example, a first message is shown in FIG11 . The first message includes a payload Q, a UDP header 1, an IP header 1, an ETH header 1, a VXLAN header, a UDP header 2, an IP header 2, and an ETH header 3. The VXLAN header is the first message header that matches the first network domain (VXLAN domain). The VXLAN header includes a flag field, a VNI field, two reserved fields, and an extension field. The VNI field is used to carry the VXLAN ID, and the flag field is used to indicate the validity of the VXLAN ID. Reserved field 2 is a bitmap field that is used to indicate which service information is included in the extension field. For example, the bitmap field includes multiple bits, each bit corresponding to a service, and each bit is used to indicate whether the extension field includes service information for the corresponding service. The value of each bit can be 0 or 1, with "1" indicating that the extension field includes service information for the service corresponding to each bit, and "0" indicating that the extension field does not include service information for the service corresponding to each bit. For example, the first bit (for example, the highest bit) in the bitmap field corresponds to the slice service, and the first bit indicates that the extended field carries a slice identifier. In one example, the first bit indicates that the extended field includes a slice indication field, and the slice indication field includes a flag subfield and a slice identification subfield. The flag subfield is used to indicate the slice identification subfield, and the slice identification subfield is used to carry a slice identifier. Referring to Figures 6 and 11, the second network node can encapsulate the VXLAN header, UDP header 2, IP header 2, and ETH header 3 in sequence outside the original message shown in Figure 6. The second network node sets an extended field in the VXLAN header, and the second network node sets the value of the first bit in the bitmap field to 1, and sets the extended field to include a slice indication field. The second network node adds the first slice identifier to the slice indication field to obtain the first message shown in Figure 11. By setting the bitmap field, the present application can encapsulate the service information of multiple services in the extended field in an integrated manner, thereby improving the message encapsulation efficiency.

[0105] In a third embodiment, the first network domain is a GENEVE domain, the first message is a GENEVE message, and the first message header is a GENEVE header. The GENEVE header includes an extension field for carrying a slice identifier, and the first slice identifier is carried in the extension field. Optionally, the second network node encapsulates the GENEVE header in the original message and adds the first slice identifier to the GENEVE header to obtain the first message.

[0106] In one example, a first message, as shown in FIG12 or FIG13 , includes a payload Q, a UDP header 1, an IP header 1, an ETH header 1, a GENEVE header, a UDP header 2, an IP header 2, and an ETH header 3. The GENEVE header is the first message header that matches the first network domain (GENEVE domain). The GENEVE header includes a version field, an option length field, an O field, a C field, a protocol type field, a VNI field, two reserved fields, and an option field. The version field carries version information. The option length field indicates the length of the option field, which is variable in length. The O field indicates that the message including the O field is an operations administration and maintenance (OAM) message. The C field indicates that one or more critical options are present in the option field. The protocol type field carries the protocol type. The VNI field carries the VXLAN ID. The option field includes an option class subfield, a C subfield, a type subfield, a reserved subfield, a length subfield, and an extension subfield. The extended subfield includes a flag space and a slice identification space, the flag space is used to indicate the slice identification space, and the slice identification space is used to carry the slice identification. Comparing Figures 12 and 13, it can be seen that in the first message shown in Figure 12, the extended subfield also includes a reserved space, and the length of the slice identification space is relatively large. For example, the length of the slice identification space in the first message shown in Figure 12 is 32 bits, and the length of the slice identification space in the first message shown in Figure 13 is 24 bits. With reference to Figures 6, 12 and 13, the second network node can encapsulate the GENEVE header, UDP header 2, IP header 2 and ETH header 3 in sequence outside the original message shown in Figure 6, and the second network node adds the first slice identification in the extended subfield in the GENEVE header to obtain the first message shown in Figure 12 or Figure 13.

[0107] Fourth embodiment: The first network domain is an SRv6 domain, the first message is an SRv6 message, the first message header is an HBH or a DOH, the HBH or the DOH is used to carry a slice identifier, and the first slice identifier is carried in the HBH or the DOH. For example, the HBH or the DOH includes an option field, and the first slice identifier is carried in the option field.

[0108] Optionally, the second network node encapsulates the HBH or the DOH in the original message, and the second network node sets an option field for carrying a slice identifier in the HBH or the DOH, and the second network node adds a first slice identifier in the option field to obtain a first message.

[0109] A fifth embodiment: the first network domain is an IPv6 domain, the first message is an IPv6 message, the first message header is an IPv6 extension header, the IPv6 extension header is used to carry a slice identifier, and the first slice identifier is carried in the IPv6 extension header. For example, the IPv6 extension header includes an option field, and the first slice identifier is carried in the option field.

[0110] Optionally, the second network node encapsulates the IPv6 extension header in the original message, and the second network node sets an option field for carrying a slice identifier in the IPv6 extension header, and the second network node adds a first slice identifier in the option field to obtain a first message.

[0111] The first message shown in Figures 9 to 11 is the message obtained by the second network node performing VXLAN encapsulation on the original message shown in Figure 6. When the second network node performs VXLAN encapsulation on the original message, it sequentially encapsulates the VXLAN header, UDP header 2, IP header 2, and ETH header 3 outside the original message. The first message shown in Figures 12 and 13 is the message obtained by the second network node performing GENEVE encapsulation on the original message shown in Figure 6. When the second network node performs GENEVE encapsulation on the original message, it sequentially encapsulates the GENEVE header, UDP header 2, IP header 2, and ETH header 3 outside the original message. As shown in Figures 9 to 13, in some embodiments, UDP header 1 is called an inner UDP header, IP header 1 is called an inner IP header, ETH header 1 is called an inner ETH header, UDP header 2 is called an outer UDP header, IP header 2 is called an outer IP header, and ETH header 3 is called an outer ETH header. The process of the second network node performing VXLAN encapsulation on the original message, the process of the second network node performing GENEVE encapsulation on the original message, and the specific contents of UDP header 2, IP header 2, and ETH header 3 can be referred to the VXLAN protocol and relevant standard documents on VXLAN encapsulation, which will not be repeated here.

[0112] S503. The second network node sends a first message in the first network domain based on the first slice identifier.

[0113] Optionally, the second network node sends the first message to the first network node located at the junction of the first network domain and the second network domain based on the first slice identifier. For example, the second network node determines the first network slice based on the first slice identifier, and the second network node forwards the first message to the first network node through the first network slice. In one embodiment, the second network node includes a message queue corresponding to the first network slice, the second network node caches the first message in the message queue, and the second network node sends the first message to the first network node according to the order of the first messages in the message queue.

[0114] S504. The first network node receives a first message from the first network domain.

[0115] The first network node receives a first message from a previous hop node of the first network node, the first network node is an egress node of a first network domain, and the previous hop node is located in the first network domain. Optionally, the first network node is an end node of a first tunnel.

[0116] In an embodiment of the present application, a first network node is located at the junction of a first network domain and a second network domain. The first network node is not only an egress node of the first network domain, but also an ingress node of the second network domain. In one embodiment, the first network node is the head node of a second tunnel in the second network domain. The second network domain is a VLAN domain, a VXLAN domain, a GENEVE domain, an SRv6 domain, or an IPv6 domain, and correspondingly, the second tunnel is a VLAN tunnel, a VXLAN tunnel, a GENEVE tunnel, an SRv6 tunnel, or an IPv6 tunnel. In one example, the second network domain is a VLAN domain, and the second tunnel is a VLAN tunnel. In another example, the second network domain is a VXLAN domain, and the second tunnel is a VXLAN tunnel. In yet another example, the second network domain is a GENEVE domain, and the second tunnel is a GENEVE tunnel. In yet another example, the second network domain is an SRv6 domain, and the second tunnel is an SRv6 tunnel. In yet another example, the second network domain is an IPv6 domain, and the second tunnel is an IPv6 tunnel.

[0117] S505. The first network node obtains a second message based on the second network domain and the first message, the second message includes a second message header that matches the second network domain, the second message header includes a second slice identifier for indicating the second network slice, and the second message header is different from the first message header.

[0118] Optionally, the first network node determines the second slice identifier based on the first slice identifier in the first message header included in the first message, and the first network node obtains the second message based on the first message, the second slice identifier, and the second network domain. The second network slice is deployed in the second network domain, and optionally, the second network slice is a network slice within the second tunnel.

[0119] In one embodiment, the first network node includes a first mapping relationship, the first mapping relationship includes a mapping relationship between a first slice identifier and a second slice identifier, and the first network node determines the second slice identifier based on the first slice identifier and the first mapping relationship. Optionally, the first network node searches the first mapping relationship based on the first slice identifier, and the first network node determines the slice identifier corresponding to the first slice identifier in the first mapping relationship as the second slice identifier for indicating the second network slice.

[0120] In an embodiment of the present application, the first mapping relationship is a mapping relationship generated according to the configuration information issued by the control device or the first mapping relationship is a statically configured mapping relationship. In one embodiment, the first mapping relationship is a mapping relationship generated according to the configuration information issued by the control device, and the first network node receives the configuration information from the control device, and the configuration information includes a first slice identifier and a second slice identifier. The first network node generates the first mapping relationship based on the first slice identifier and the second slice identifier included in the configuration information. In another embodiment, the user statically configures the first mapping relationship in the first network node through a command line, and the first network node obtains the first mapping relationship statically configured by the user through the command line.

[0121] In an embodiment of the present application, the second network domain is a VLAN domain, a VXLAN domain, a GENEVE domain, an SRv6 domain, or an IPv6 domain, and correspondingly, the second message is a VLAN message, a VXLAN message, a GENEVE message, an SRv6 message, or an IPv6 message, and correspondingly, the second message header that matches the second network domain is an ETH header, a VXLAN header, a GENEVE header, an HBH (or DOH), or an IPv6 extension header. The type of the second network domain is different from the type of the first network domain, and correspondingly, the second message header is different from the first message header. In one example, the first network domain is a VLAN domain, and the second network domain is a VXLAN domain, a GENEVE domain, an SRv6 domain, or an IPv6 domain. In another example, the first network domain is a VXLAN domain, a GENEVE domain, an SRv6 domain, or an IPv6 domain, and the second network domain is a VLAN domain. In yet another example, the first network domain is a GENEVE domain, and the second network domain is a VLAN domain, a VXLAN domain, an SRv6 domain, or an IPv6 domain.

[0122] In which, the first network node is located at the junction of the first network domain and the second network domain, the first network node is the egress node of the first network domain, and the first network node is the ingress node of the second network domain, and the first network node obtains the second message based on the first message, the second slice identifier and the second network domain, which may include: the first network node decapsulates the first message based on the type of the first network domain to obtain the original message, the first network node encapsulates the original message based on the type of the second network domain to obtain the second message, and the second message header of the second message includes a second slice identifier for indicating the second network slice.

[0123] In one embodiment, the first network domain is a VLAN domain, the second network domain is a VXLAN domain, the first message is shown in Figure 7 or Figure 8, the first network node performs VLAN decapsulation on the first message (for example, removes the VLAN tag field and slice indication field in the ETH header 2) to obtain the original message as shown in Figure 5, and the first network node performs VXLAN encapsulation on the original message to obtain a second message. The structure of the second message can refer to the first message shown in any one of Figures 9 to 11.

[0124] In another embodiment, the first network domain is a VLAN domain, the second network domain is a GENEVE domain, the first message is shown in Figure 7 or Figure 8, the first network node performs VLAN decapsulation on the first message to obtain the original message as shown in Figure 5, and the first network node performs GENEVE encapsulation on the original message to obtain the second message. The structure of the second message can refer to the first message shown in Figure 12 or Figure 13.

[0125] In another embodiment, the first network domain is a VLAN domain, the second network domain is an SRv6 domain, the first message is as shown in Figure 7 or Figure 8, the first network node performs VLAN decapsulation on the first message to obtain the original message as shown in Figure 5, and the first network node performs SRv6 encapsulation on the original message to obtain a second message, the second message includes HBH or DOH, and the HBH or the DOH includes a second slice identifier.

[0126] In another embodiment, the first network domain is a VLAN domain, the second network domain is an IPv6 domain, the first message is as shown in Figure 7 or Figure 8, the first network node performs VLAN decapsulation on the first message to obtain the original message as shown in Figure 5, and the first network node performs IPv6 encapsulation on the original message to obtain a second message, the second message includes an IPv6 extension header, and the IPv6 extension header includes a second slice identifier.

[0127] In another embodiment, the first network domain is a VXLAN domain, the second network domain is a VLAN domain, the first message is as shown in any one of Figures 9 to 11, the first network node performs VXLAN decapsulation on the first message (for example, removes the VXLAN header, UDP header 2, IP header 2 and ETH header 3) to obtain the original message as shown in Figure 5, and the first network node performs VLAN encapsulation on the original message to obtain a second message. The structure of the second message can refer to the first message shown in Figure 7 or 8.

[0128] In another embodiment, the first network domain is a VXLAN domain, the second network domain is a GENEVE domain, the first message is as shown in any one of Figures 9 to 11, the first network node performs VXLAN decapsulation on the first message to obtain the original message as shown in Figure 5, and the first network node performs GENEVE encapsulation on the original message to obtain a second message. The structure of the second message can refer to the first message shown in Figure 12 or 13.

[0129] In another embodiment, the first network domain is a VXLAN domain, the second network domain is an SRv6 domain, the first message is as shown in any one of Figures 9 to 11, the first network node performs VXLAN decapsulation on the first message to obtain the original message as shown in Figure 5, and the first network node performs SRv6 encapsulation on the original message to obtain a second message, the second message includes HBH or DOH, and the HBH or the DOH includes a second slice identifier.

[0130] In another embodiment, the first network domain is a VXLAN domain, the second network domain is an IPv6 domain, the first message is as shown in any one of Figures 9 to 11, the first network node performs VXLAN decapsulation on the first message to obtain the original message as shown in Figure 5, and the first network node performs IPv6 encapsulation on the original message to obtain a second message, the second message includes an IPv6 extension header, and the IPv6 extension header includes a second slice identifier.

[0131] In another embodiment, the first network domain is a GENEVE domain, the second network domain is a VLAN domain, the first message is shown in Figure 12 or Figure 13, the first network node performs GENEVE decapsulation on the first message (for example, removes the GENEVE header, UDP header 2, IP header 2 and ETH header 3) to obtain the original message as shown in Figure 5, and the first network node performs VLAN encapsulation on the original message to obtain a second message. The structure of the second message can refer to the first message shown in Figure 7 or Figure 8.

[0132] In another embodiment, the first network domain is a GENEVE domain, the second network domain is a VXLAN domain, the first message is shown in Figure 12 or Figure 13, the first network node performs GENEVE decapsulation on the first message to obtain the original message as shown in Figure 5, and the first network node performs VXLAN encapsulation on the original message to obtain the second message. The structure of the second message can refer to the first message shown in any one of Figures 9 to 11.

[0133] In another embodiment, the first network domain is a GENEVE domain, the second network domain is an SRv6 domain, the first message is as shown in Figure 12 or Figure 13, the first network node performs GENEVE decapsulation on the first message to obtain the original message as shown in Figure 5, and the first network node performs SRv6 encapsulation on the original message to obtain a second message, the second message includes HBH or DOH, and the HBH or the DOH includes a second slice identifier.

[0134] In another embodiment, the first network domain is a GENEVE domain, the second network domain is an IPv6 domain, the first message is as shown in Figure 12 or Figure 13, the first network node performs GENEVE decapsulation on the first message to obtain the original message as shown in Figure 5, the first network node performs IPv6 encapsulation on the original message to obtain a second message, the second message includes an IPv6 extension header, and the IPv6 extension header includes a second slice identifier.

[0135] In another embodiment, the first network domain is an SRv6 domain, the second network domain is a VLAN domain, the first network node performs SRv6 decapsulation on the first message to obtain the original message as shown in Figure 5, and the first network node performs VLAN encapsulation on the original message to obtain a second message. The structure of the second message can refer to the first message shown in Figure 7 or Figure 8.

[0136] In another embodiment, the first network domain is an SRv6 domain, the second network domain is a VXLAN domain, the first network node performs SRv6 decapsulation on the first message to obtain the original message as shown in Figure 5, and the first network node performs VXLAN encapsulation on the original message to obtain a second message. The structure of the second message can refer to the first message shown in any one of Figures 9 to 11.

[0137] In another embodiment, the first network domain is an SRv6 domain, the second network domain is a GENEVE domain, the first network node performs SRv6 decapsulation on the first message to obtain the original message as shown in Figure 5, and the first network node performs GENEVE encapsulation on the original message to obtain a second message. The structure of the second message can refer to the first message shown in Figure 12 or Figure 13.

[0138] In another embodiment, the first network domain is an SRv6 domain, the second network domain is an IPv6 domain, the first network node performs SRv6 decapsulation on the first message to obtain the original message as shown in Figure 5, and the first network node performs IPv6 encapsulation on the original message to obtain a second message, the second message includes an IPv6 extension header, and the IPv6 extension header includes a second slice identifier.

[0139] In another embodiment, the first network domain is an IPv6 domain, the second network domain is a VLAN domain, the first network node performs IPv6 decapsulation on the first message to obtain the original message as shown in Figure 5, and the first network node performs VLAN encapsulation on the original message to obtain a second message. The structure of the second message can refer to the first message shown in Figure 7 or Figure 8.

[0140] In another embodiment, the first network domain is an IPv6 domain, the second network domain is a VXLAN domain, the first network node performs IPv6 decapsulation on the first message to obtain the original message as shown in Figure 5, and the first network node performs VXLAN encapsulation on the original message to obtain a second message. The structure of the second message can refer to the first message shown in any one of Figures 9 to 11.

[0141] In another embodiment, the first network domain is an IPv6 domain, the second network domain is a GENEVE domain, the first network node performs IPv6 decapsulation on the first message to obtain the original message as shown in Figure 5, and the first network node performs GENEVE encapsulation on the original message to obtain a second message. The structure of the second message can refer to the first message shown in Figure 12 or Figure 13.

[0142] In another embodiment, the first network domain is an IPv6 domain, the second network domain is an SRv6 domain, the first network node performs IPv6 decapsulation on the first message to obtain the original message as shown in Figure 5, and the first network node performs SRv6 encapsulation on the original message to obtain a second message, the second message includes HBH or DOH, and the HBH or the DOH includes a second slice identifier.

[0143] In an optional embodiment, before S505, the slice switching function is pre-enabled in the first network node, so that the first network node can execute S505 when receiving the first message. The first network node can enable the slice switching function according to user configuration information or according to control information issued by the control device, which is not limited in this embodiment of the present application.

[0144] S506. The first network node sends a second message in the second network domain based on the second slice identifier.

[0145] The first network node determines the second network slice based on the second slice identifier, and then sends the second message through the second network slice. In one embodiment, the first network node includes a message queue corresponding to the second network slice, the first network node caches the second message in the message queue, and the first network node sends the second message according to the order of the second messages in the message queue.

[0146] To sum up, the technical solution provided by the embodiment of the present application is that the second network node located at the entrance of the first network domain obtains the first message based on the original message, including a first message header matching the first network domain, the first message header including a first slice identifier for indicating the first network slice, the second network node sends the first message in the second network domain based on the first slice identifier, and the first network node located at the junction of the first network domain and the second network domain receives the first message and obtains the second message based on the second network domain and the first message, and sends the second message in the second network domain based on the second slice identifier for indicating the second network slice in the second message header included in the second message, thereby realizing the switching of the first network slice in the first network domain and the second network slice in the second network domain, thereby realizing cross-domain intercommunication between the first network slice and the second network slice, avoiding the complex configuration of the network node to re-identify the service and the degradation of forwarding efficiency when the message crosses the domain, and improving the message forwarding efficiency. In addition, the present application can carry slice identifiers in message headers such as ETH headers, VXLAN headers, GENEVE headers, IPv6 extension headers, HBH or DOH, and network nodes can forward messages based on the slice identifiers carried in these message headers, so that the technical solution of the present application can be applied to network scenarios such as VLAN networks, VXLAN networks, GENEVE networks, IPv6 networks, SRv6 networks, etc., and implement hard isolation of forwarding resources (bandwidth, cache, etc.) based on slicing technology in network scenarios such as VLAN networks, VXLAN networks, GENEVE networks, IPv6 networks, SRv6 networks. In addition, in the present application, network nodes can process messages carrying slice identifiers hop by hop to implement hard isolation of network resources hop by hop. The present application can implement different network slices for different services such as production services and office services carried by VLAN networks, VXLAN networks, GENEVE networks, IPv6 networks, SRv6 networks, etc., to achieve secure isolation of network resources for different services and ensure the SLA quality of high-priority services. The slice identifier switching solution provided by the present application is applicable to different campus network interconnection scenarios and campus network and cloud network interconnection scenarios.

[0147] To facilitate understanding of the technical solution of the present application, the following takes the example of network domain 1 being a VLAN domain, network domain 2 being an IPv6 domain, and network domain 3 being a VXLAN domain / GENEVE domain (VXLAN domain or GENEVE domain) in FIG4 , and describes the message forwarding method of the present application in conjunction with FIG14 . As shown in FIG14 , network node A is the entry node of the VLAN domain, network node B is the egress node of the VLAN domain and the entry node of the IPv6 domain, network node C is the egress node of the IPv6 domain and the entry node of the VXLAN domain / GENEVE domain, and network node D is the egress node of the VXLAN domain / GENEVE domain.

[0148] As shown in Figure 14, the original message P0 includes a payload Q and, in sequence, UDP header 1, IP header 1, and ETH header 1 encapsulated outside of the payload Q. After network node A receives message P0, it performs VLAN encapsulation on message P0 to obtain message P1. Message P1 includes a payload Q and, in sequence, UDP header 1, IP header 1, and ETH header 2 encapsulated outside of the payload Q. ETH header 2 carries slice ID 1, which indicates network slice 1 in the VLAN domain. Network node A determines network slice 1 based on slice ID 1 and sends message P1 to network node B via network slice 1.

[0149] After network node B receives message P1, it determines slice ID2, which indicates network slice 2 in the IPv6 domain, based on slice ID1 carried in message P1. Network node B performs VLAN decapsulation on message P1 to obtain message P0. Network node B performs IPv6 encapsulation on message P0 based on slice ID2 to obtain message P2. Message P2 includes payload Q and UDP header 1, IP header 1, ETH header 1, IPv6 extension header, IPv6 header, and ETH header 3, which are sequentially encapsulated outside payload Q. The IPv6 extension header carries slice ID2, which indicates network slice 2 in the IPv6 domain. Network node B determines network slice 2 based on slice ID2 and sends message P2 to network node C through network slice 2.

[0150] After network node C receives message P2, it determines slice ID3, which indicates network slice 3 in the VXLAN / GENEVE domain, based on slice ID2 carried in message P2. Network node C decapsulates message P2 in IPv6 to obtain message P0. Based on slice ID3, network node C performs VXLAN / GENEVE encapsulation (VXLAN encapsulation or GENEVE encapsulation) on message P0 to obtain message P3. Message P3 includes payload Q and, encapsulated in sequence within payload Q, UDP header 1, IP header 1, ETH header 1, VXLAN header / GENEVE header (VXLAN header or GENEVE header), UDP header 2, IP header 2, and ETH header 3. The VXLAN / GENEVE header carries slice ID3, which indicates network slice 3 in the VXLAN / GENEVE domain. Network node C determines network slice 3 based on slice ID3 and forwards message P3 to network node D via network slice 3.

[0151] After network node D receives message P3, it performs VXLAN decapsulation / GENEVE decapsulation on message P3 to obtain message P0, and then forwards message P0.

[0152] It can be seen that the technical solution provided by the embodiment of the present application can carry the slice ID in the ETH header, VXLAN header, GENEVE header or IPv6 extension header, and the network node can forward the message according to the slice ID carried in the ETH header, the VXLAN header, the GENEVE header or the IPv6 extension header, so that the technical solution of the present application can be applied to VLAN network, VXLAN network, GENEVE network, IPv6 network. In addition, the network node B located at the junction of the VLAN domain and the IPv6 domain and the network node C located at the junction of the IPv6 domain and the VXLAN domain / GENEVE domain can both switch the slice ID, thereby realizing the switching of messages between network slices in different network domains and realizing cross-domain intercommunication of network slices.

[0153] In the related art, when a data flow enters another network domain from a certain network domain, the egress node of the certain network domain terminates the network slice in the certain network domain for the certain data flow, and the ingress device of the other network domain allocates a network slice to the certain data flow through a flow strategy based on the traffic characteristic information of the certain data flow. This can achieve the decoupling of network slices in different network domains, facilitating the independent management and maintenance of each network domain. However, when the message crosses the domain, the network node needs to re-identify the service, which requires complex configuration and easily leads to degradation of message forwarding efficiency. In an embodiment of the present application, when the message crosses the domain, the network node can switch the slice identifier according to the mapping relationship between the slice identifiers, without the need to re-identify the service. This can avoid the complex configuration and forwarding efficiency degradation of the network node re-identifying the service when the message crosses the domain, thereby improving the message forwarding efficiency.

[0154] The above embodiment takes the case where the first network slice and the second network slice are different network slices, and the first slice identifier and the second slice identifier are different slice identifiers as an example. In some embodiments, network slices and slice identifiers can be uniformly planned for the entire network. In this way, when a message crosses domains, network nodes located at the boundaries of different network domains do not need to re-identify the service, which can avoid the complex configuration and forwarding efficiency degradation of network nodes re-identifying the service when the message crosses domains, improve message forwarding efficiency, and simplify the maintenance and management of network slices. For example, network slices can be planned to cross VLAN domains, VXLAN domains, GENEVE domains, SRv6 domains, IPv6 domains, etc., so that network nodes at the intersection of VLAN domains, VXLAN domains, GENEVE domains, SRv6 domains, and IPv6 domains do not need to perform slice identifier switching and service identification.

[0155] The above is an introduction to the method embodiments of the present application. The following describes the device embodiments of the present application. The device of the present application can be used to perform the method of the present application. For details not disclosed in the device embodiments of the present application, please refer to the method embodiments.

[0156] Please refer to Figure 15, which shows a schematic diagram of a message forwarding device 1500 provided in an embodiment of the present application. The message forwarding device 1500 is applied to the first network node in the above embodiment. The first network node is located at the junction of the first network domain and the second network domain. The message forwarding device 1500 is used to execute the relevant steps performed by the first network node in the message forwarding method provided in the above embodiment. For example, the message forwarding device 1500 is the first network node or a functional component in the first network node. As shown in Figure 15, the message forwarding device 1500 includes a receiving module 1510, a processing module 1520, and a sending module 1530.

[0157] Receiving module 1510 is configured to receive a first message from a first network domain, the first message including a first message header that matches the first network domain, the first message header including a first slice identifier that indicates a first network slice. For the functional implementation of receiving module 1510, please refer to the description in S504.

[0158] Processing module 1520 is configured to obtain a second message based on the second network domain and the first message, where the second message includes a second message header that matches the second network domain, and the second message header includes a second slice identifier that indicates the second network slice. For the functional implementation of processing module 1520, please refer to the description in S505.

[0159] The sending module 1530 is configured to send the second message in the second network domain based on the second slice identifier. For the functional implementation of the sending module 1530, please refer to the description in S506.

[0160] Optionally, the processing module 1520 is used to: determine the second slice identifier based on the first slice identifier and the first mapping relationship, where the first mapping relationship includes a mapping relationship between the first slice identifier and the second slice identifier; and obtain the second message based on the first message, the second slice identifier and the second network domain.

[0161] Optionally, the first mapping relationship is a mapping relationship generated according to configuration information delivered by the control device, or the first mapping relationship is a statically configured mapping relationship.

[0162] Optionally, the first network domain is a VLAN domain, the first message header is an Ethernet header, and the slice indication field of the Ethernet header is used to carry a first slice identifier; the second network domain is a VXLAN domain, the second message is a VXLAN message, the second message header is a VXLAN header, and the reserved field or extended field of the VXLAN header is used to carry a second slice identifier.

[0163] Optionally, the first network domain is a VLAN domain, the first message header is an Ethernet header, and the slice indication field of the Ethernet header is used to carry a first slice identifier; the second network domain is a GENEVE domain, the second message is a GENEVE message, the second message header is a GENEVE header, and the extension field of the GENEVE header is used to carry a second slice identifier.

[0164] Optionally, the first network domain is a VLAN domain, the first message header is an Ethernet header, and the slice indication field of the Ethernet header is used to carry a first slice identifier; the second network domain is an SRv6 domain, the second message is an SRv6 message, and the second message header is HBH or DOH, and the HBH or the DOH is used to carry a second slice identifier.

[0165] Optionally, the first network domain is a VLAN domain, the first message header is an Ethernet header, and the slice indication field of the Ethernet header is used to carry a first slice identifier; the second network domain is an IPv6 domain, the second message is an IPv6 message, and the second message header is an IPv6 extension header, and the IPv6 extension header is used to carry a second slice identifier.

[0166] Optionally, the first network domain is a VXLAN domain, the first message is a VXLAN message, the first message header is a VXLAN header, and the reserved field or extended field of the VXLAN header is used to carry a first slice identifier; the second network domain is a VLAN domain, the second message header is an Ethernet header, and the slice indication field of the Ethernet header is used to carry a second slice identifier.

[0167] Optionally, the first network domain is a GENEVE domain, the first message is a GENEVE message, the first message header is a GENEVE header, and the extension field of the GENEVE header is used to carry a first slice identifier; the second network domain is a VLAN domain, the second message header is an Ethernet header, and the slice indication field of the Ethernet header is used to carry a second slice identifier.

[0168] Optionally, the first network domain is an SRv6 domain, the first message is an SRv6 message, the first message header is HBH or DOH, and the HBH or the DOH is used to carry a first slice identifier; the second network domain is a VLAN domain, the second message header is an Ethernet header, and the slice indication field of the Ethernet header is used to carry a second slice identifier.

[0169] Optionally, the first network domain is an IPv6 domain, the first message is an IPv6 message, the first message header is an IPv6 extension header, and the IPv6 extension header is used to carry a first slice identifier; the second network domain is a VLAN domain, the second message header is an Ethernet header, and the slice indication field of the Ethernet header is used to carry a second slice identifier.

[0170] To sum up, the technical solution provided by the embodiment of the present application is that the first message from the first network domain includes a first message header matching the first network domain, the first message header includes a first slice identifier for indicating the first network slice, and the first network node at the junction of the first network domain and the second network domain obtains a second message based on the second network domain and the first message, and sends the second message in the second network domain based on the second slice identifier for indicating the second network slice in the second message header included in the second message. In this way, the first network node can realize the switching of the first network slice in the first network domain and the second network slice in the second network domain, thereby realizing cross-domain intercommunication between the first network slice and the second network slice, avoiding the complex configuration of the network node to re-identify the service and the degradation of forwarding efficiency when the message crosses domains, and improving the message forwarding efficiency. In addition, the present application can carry slice identifiers in message headers such as ETH headers, VXLAN headers, GENEVE headers, IPv6 extension headers, HBH or DOH, and network nodes can forward messages according to the slice identifiers carried in these message headers, thereby making the technical solution of the present application applicable to network scenarios such as VLAN networks, VXLAN networks, GENEVE networks, IPv6 networks, and SRv6 networks.

[0171] Please refer to Figure 16, which shows a schematic diagram of another message forwarding device 1600 provided in an embodiment of the present application. Message forwarding device 1600 is applied to the second network node in the above embodiment. The second network node is located at the entrance of the first network domain. Message forwarding device 1600 is configured to execute the relevant steps performed by the second network node in the message forwarding method provided in the above embodiment. For example, message forwarding device 1600 is the second network node or a functional component within the second network node. As shown in Figure 16, message forwarding device 1600 includes a processing module 1610 and a sending module 1620.

[0172] Processing module 1610 is configured to obtain a first message based on an original message from a user device, where the first message includes a first message header that matches a first network domain, and the first message header includes a first slice identifier that indicates a first network slice. For the functional implementation of processing module 1610, please refer to the description in S502.

[0173] The sending module 1620 is configured to send the first message in the first network domain based on the first slice identifier. For the functional implementation of the sending module 1620, please refer to the description in S503.

[0174] Optionally, the sending module 1620 is used to send a first message to a first network node located at the junction of a first network domain and a second network domain based on a first slice identifier, where the second network domain is different from the first network domain.

[0175] Optionally, the first network domain is a VLAN domain, the first message is a VLAN message, the first message header is an Ethernet header, and the slice indication field of the Ethernet header is used to carry a first slice identifier.

[0176] Optionally, the first network domain is a VXLAN domain, the first message is a VXLAN message, the first message header is a VXLAN header, and the reserved field or extended field of the VXLAN header is used to carry the first slice identifier.

[0177] Optionally, the first network domain is a GENEVE domain, the first message is a GENEVE message, the first message header is a GENEVE header, and the extension field of the GENEVE header is used to carry the first slice identifier.

[0178] Optionally, the first network domain is an SRv6 domain, the first message is an SRv6 message, the first message header is HBH or DOH, and the HBH or the DOH is used to carry the first slice identifier.

[0179] Optionally, the first network domain is an IPv6 domain, the first message is an IPv6 message, and the first message header is an IPv6 extension header, which is used to carry a first slice identifier.

[0180] To sum up, the technical solution provided by the embodiment of the present application is that after the second network node located at the entrance of the first network domain obtains the first message, it can send the first message to the first network node located at the junction of the first network domain and the second network domain based on the first slice identifier in the first message header included in the first message. The first network node can obtain the second message based on the second network domain and the first message, and send the second message in the second network domain based on the second slice identifier for indicating the second network slice in the second message header included in the second message, thereby realizing the switching of the first network slice in the first network domain and the second network slice in the second network domain, thereby realizing cross-domain intercommunication between the first network slice and the second network slice, avoiding the complex configuration of the network node to re-identify the service and the degradation of forwarding efficiency when the message crosses domains. In addition, the present application can carry slice identifiers in message headers such as ETH headers, VXLAN headers, GENEVE headers, IPv6 extension headers, HBH or DOH, and network nodes can forward messages according to the slice identifiers carried in these message headers, thereby making the technical solution of the present application applicable to network scenarios such as VLAN networks, VXLAN networks, GENEVE networks, IPv6 networks, and SRv6 networks.

[0181] The message forwarding device provided in the embodiments of the present application can also be implemented using an ASIC or a programmable logic device (PLD). The PLD can be a complex programmable logical device (CPLD), an FPGA, a generic array logic (GAL), or any combination thereof. The methods provided in the above method embodiments can also be implemented using software. When the methods provided in the above method embodiments are implemented using software, the various modules in the message forwarding device can also be software modules.

[0182] An embodiment of the present application provides a message forwarding device, comprising a memory and a processor; the memory is used to store a computer program; the processor is used to execute the computer program stored in the memory so that the message forwarding device performs all or part of the steps of the message forwarding method provided in the above-mentioned method embodiment.

[0183] As an example, please refer to Figure 17, which shows a schematic diagram of another message forwarding device 1700 provided in an embodiment of the present application. The message forwarding device 1700 is a network node or a partial component in a network node. The message forwarding device 1700 is used to execute the above-mentioned message forwarding method embodiment. As shown in Figure 17, the message forwarding device 1700 includes: a main control board 1710, an interface board 1730 and an interface board 1740. In the case of multiple interface boards, a switching network board (not shown in Figure 17) may be included. The switching network board is used to complete data exchange between each interface board (the interface board is also called a line card or service board).

[0184] The main control board 1710 is used to perform functions such as system management, device maintenance, and protocol processing. The interface boards 1730 and 1740 are used to provide various service interfaces (e.g., POS interfaces, GE interfaces, ATM interfaces, etc.) and implement message forwarding. The main control board 1710 primarily includes three functional units: a system management and control unit, a system clock unit, and a system maintenance unit. The main control board 1710, interface boards 1730, and interface boards 1740 are interconnected via a system bus and the system backplane. The interface board 1730 includes one or more processors 1731. Processors 1731 are used to control and manage the interface board 1730 and communicate with the central processing unit 1712 on the main control board 1710. The memory 1732 on the interface board 1730 is used to store, among other things, the first mapping relationship described in the above embodiment. As shown in FIG. 17 , the main control board 1710 may include a memory 1714 . The memory 1714 on the main control board 1710 may also be used to store the first mapping relationship, etc. This embodiment of the present application does not limit this.

[0185] The interface board 1730 includes one or more network interfaces 1733 for receiving and sending messages. The processor 1731 can process the messages received by the network interface 1733, such as encapsulating slice identifiers in the messages, converting the slice identifiers carried in the messages, etc. The specific implementation process will not be described here one by one.

[0186] It is understood that, as shown in FIG17 , this embodiment includes multiple interface boards and employs a distributed forwarding mechanism. Under this mechanism, the operations on interface board 1740 are substantially similar to those on interface board 1730 and, for the sake of brevity, are not further described. Furthermore, it is understood that the processor 1731 in interface board 1730 and / or the processor 1741 in interface board 1740 in FIG17 may be dedicated hardware or chips, such as a network processor or an application-specific integrated circuit, to implement the aforementioned functions. This implementation is what is commonly referred to as the forwarding plane employing dedicated hardware or chip processing. In another embodiment, the processor 1731 in interface board 1730 and / or the processor 1741 in interface board 1740 may also employ a general-purpose processor, such as a general-purpose central processing unit (CPU), to implement the aforementioned functions.

[0187] It should also be noted that there may be one or more main control boards, which may include a primary and a backup main control board. There may also be one or more interface boards. The higher the data processing capabilities of a network node, the more interface boards are provided. With multiple interface boards, they can communicate with each other through one or more switching fabric boards, and when there are multiple boards, they can collectively implement load balancing and redundant backup. In a centralized forwarding architecture, the network node may not require a switching fabric board; the interface board handles the service data processing for the entire system. In a distributed forwarding architecture, the network node includes multiple interface boards, which can exchange data between them through the switching fabric board, providing high-capacity data exchange and processing capabilities. Therefore, network nodes with a distributed architecture have greater data access and processing capabilities than nodes with a centralized architecture. The specific architecture to adopt depends on the network deployment scenario and is not limited here.

[0188] In an optional embodiment, the memory 1732 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type of dynamic storage device that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, an optical disc storage (including a compact disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited to these. The memory 1732 can exist independently and be connected to the processor 1731 via a communication bus. The memory 1732 can also be integrated with the processor 1731.

[0189] Memory 1732 is used to store program code and is controlled by processor 1731 for execution to perform some or all of the steps of the message forwarding method provided in the above embodiments. Processor 1731 is used to execute the program code stored in memory 1732. The program code may include one or more software modules. These one or more software modules may be the functional modules provided in the embodiments shown in Figures 15 or 16 above. Memory 1714 may also be used to store program code and is controlled by central processing unit 1712 for execution to perform some or all of the steps of the message forwarding method provided in the above embodiments.

[0190] In an optional embodiment, the network interface 1733 can be a device such as any transceiver for communicating with other nodes or communication networks, such as Ethernet, radio access network (RAN), wireless local area network (WLAN), etc.

[0191] An embodiment of the present application provides a message forwarding system, including a first network node and a second network node, the first network node is located at the junction of the first network domain and the second network domain, the second network node is located at the entrance of the first network domain, the first network node includes a message forwarding device as shown in Figure 15 or Figure 17, and the second network node includes a message forwarding device as shown in Figure 16 or Figure 17.

[0192] In an example, the message forwarding system is shown in FIG2 , where the first network domain is campus network 1, campus network 2, or campus network 3, and the second network domain is the Internet / private network / WAN.

[0193] In another example, the message forwarding system is shown in FIG3 , the first network domain is network domain 1 , the second network domain is network domain 2 , the first network node is network node B, and the second network node is network node A.

[0194] In another example, the message forwarding system is shown in Figure 4. For example, the first network domain is network domain 1, the second network domain is network domain 2, the first network node is network node B, and the second network node is network node A. For another example, the first network domain is network domain 2, the second network domain is network domain 3, the first network node is network node C, and the second network node is network node B.

[0195] An embodiment of the present application provides a computer-readable storage medium, which stores a computer program. When the computer program is executed (for example, by a network node, one or more processors, etc.), it implements all or part of the steps of the method provided in the above method embodiment.

[0196] An embodiment of the present application provides a computer program product, which includes a program or code. When the program or code is executed (for example, by a network node, one or more processors, etc.), it implements all or part of the steps of the method provided in the above method embodiment.

[0197] An embodiment of the present application provides a chip, which includes a programmable logic circuit and / or program instructions. When the chip is running, it is used to implement all or part of the steps of the method provided in the above method embodiment.

[0198] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product, which includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website, computer, server or data center to another website, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) mode. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium, or a semiconductor medium (e.g., a solid-state hard disk).

[0199] It should be understood that the term "at least one" in this application refers to one or more, and "a plurality of" refers to two or more. The term "and / or" in this application is merely a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, for the sake of clarity of description, in this application, words such as "first", "second", and "third" are used to distinguish between identical or similar items with substantially the same functions and effects. Those skilled in the art will understand that words such as "first", "second", and "third" do not limit the quantity and execution order.

[0200] The different types of embodiments, such as the method embodiments and device embodiments provided in the embodiments of this application, can refer to each other, and the embodiments of this application are not limited thereto. The order of the operations of the method embodiments provided in the embodiments of this application can be appropriately adjusted, and the operations can be increased or decreased in response to the circumstances. Any person skilled in the art who can easily think of a method of variation within the technical scope disclosed in this application should be included in the scope of protection of this application, and therefore will not be described in detail.

[0201] In the corresponding embodiments provided in this application, it should be understood that the disclosed devices, etc. can be implemented through other configurations. For example, the device embodiments described above are merely illustrative. For example, the module division is merely a logical function division. In actual implementation, other division methods may be used, such as combining or integrating multiple modules or components into another system, or ignoring or not implementing certain features.

[0202] Modules described as separate components may or may not be physically separate, and components described as modules may or may not be physical modules. They may be located in one place or distributed across multiple devices. Some or all of these modules may be selected to achieve the purpose of this embodiment based on actual needs.

[0203] The above description is merely an exemplary embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or replacements within the technical scope disclosed in this application, and these modifications or replacements should be included within the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A message forwarding method, characterized in that: Applied to a first network node located at the junction of a first network domain and a second network domain, the method comprises: The first network node receives a first message from the first network domain, where the first message includes a first message header matching the first network domain, and the first message header includes a first slice identifier for indicating a first network slice; The first network node obtains a second message based on the second network domain and the first message, where the second message includes a second message header matching the second network domain, the second message header includes a second slice identifier for indicating a second network slice, and the second message header is different from the first message header; The first network node sends the second message in the second network domain based on the second slice identifier.

2. The method according to claim 1, characterized in that The first network node obtaining the second message based on the second network domain and the first message includes: The first network node determines the second slice identifier according to the first slice identifier and a first mapping relationship, where the first mapping relationship includes a mapping relationship between the first slice identifier and the second slice identifier; The first network node obtains the second message based on the first message, the second slice identifier and the second network domain.

3. The method according to claim 1 or 2, characterized in that: The first network domain is a virtual local area network (VLAN) domain, the first message header is an Ethernet header, and the slice indication field of the Ethernet header is used to carry the first slice identifier; The second network domain is a virtual extended local area network VXLAN domain, the second message is a VXLAN message, the second message header is a VXLAN header, and the reserved field or extended field of the VXLAN header is used to carry the second slice identifier.

4. The method according to claim 1 or 2, characterized in that: The first network domain is a virtual local area network (VLAN) domain, the first message header is an Ethernet header, and the slice indication field of the Ethernet header is used to carry the first slice identifier; The second network domain is a general network virtual encapsulation GENEVE domain, the second message is a GENEVE message, the second message header is a GENEVE header, and the extension field of the GENEVE header is used to carry the second slice identifier.

5. The method according to claim 1 or 2, characterized in that: The first network domain is a virtual local area network (VLAN) domain, the first message header is an Ethernet header, and the slice indication field of the Ethernet header is used to carry the first slice identifier; The second network domain is a segment routing SRv6 domain based on Internet Protocol version 6 IPv6, the second message is an SRv6 message, the second message header is a hop-by-hop options header or a destination options header DOH, and the hop-by-hop options header or the DOH is used to carry the second slice identifier.

6. The method according to claim 1 or 2, characterized in that: The first network domain is a virtual local area network (VLAN) domain, the first message header is an Ethernet header, and the slice indication field of the Ethernet header is used to carry the first slice identifier; The second network domain is an Internet Protocol version 6 IPv6 domain, the second message is an IPv6 message, the second message header is an IPv6 extension header, and the IPv6 extension header is used to carry the second slice identifier.

7. The method according to claim 1 or 2, characterized in that: The first network domain is a virtual extended local area network VXLAN domain, the first message is a VXLAN message, the first message header is a VXLAN header, and the reserved field or extended field of the VXLAN header is used to carry the first slice identifier; The second network domain is a virtual local area network (VLAN) domain, the second message header is an Ethernet header, and the slice indication field of the Ethernet header is used to carry the second slice identifier.

8. The method according to claim 1 or 2, characterized in that: The first network domain is a general network virtual encapsulation GENEVE domain, the first message is a GENEVE message, the first message header is a GENEVE header, and the extension field of the GENEVE header is used to carry the first slice identifier; The second network domain is a virtual local area network (VLAN) domain, the second message header is an Ethernet header, and the slice indication field of the Ethernet header is used to carry the second slice identifier.

9. The method according to claim 1 or 2, characterized in that: The first network domain is a segment routing SRv6 domain based on Internet Protocol version 6 IPv6, the first message is an SRv6 message, the first message header is a hop-by-hop option header or a destination option header DOH, and the hop-by-hop option header or the DOH is used to carry the first slice identifier; The second network domain is a virtual local area network (VLAN) domain, the second message header is an Ethernet header, and the slice indication field of the Ethernet header is used to carry the second slice identifier.

10. The method according to claim 1 or 2, characterized in that: The first network domain is an Internet Protocol version 6 IPv6 domain, the first message is an IPv6 message, the first message header is an IPv6 extension header, and the IPv6 extension header is used to carry the first slice identifier; The second network domain is a virtual local area network (VLAN) domain, the second message header is an Ethernet header, and the slice indication field of the Ethernet header is used to carry the second slice identifier.

11. A message forwarding method, characterized in that: Applied to a second network node located at an entrance of a first network domain, the method comprises: The second network node obtains a first message based on an original message from the user equipment, where the first message includes a first message header matching the first network domain, and the first message header includes a first slice identifier for indicating a first network slice; The second network node sends the first message in the first network domain based on the first slice identifier.

12. The method according to claim 11, characterized in that The second network node sending the first message in the first network domain based on the first slice identifier includes: Based on the first slice identifier, the second network node sends the first message to a first network node located at the junction of the first network domain and a second network domain, where the second network domain is different from the first network domain.

13. The method according to claim 11 or 12, characterized in that: The first network domain is a virtual local area network (VLAN) domain, the first message header is an Ethernet header, and the slice indication field of the Ethernet header is used to carry the first slice identifier.

14. The method according to claim 11 or 12, characterized in that: The first network domain is a virtual extended local area network VXLAN domain, the first message is a VXLAN message, the first message header is a VXLAN header, and the reserved field or extended field of the VXLAN header is used to carry the first slice identifier.

15. The method according to claim 11 or 12, characterized in that: The first network domain is a general network virtual encapsulation GENEVE domain, the first message is a GENEVE message, the first message header is a GENEVE header, and the extension field of the GENEVE is used to carry the first slice identifier.

16. The method according to claim 11 or 12, characterized in that: The first network domain is a segment routing SRv6 domain based on Internet Protocol version 6 IPv6, the first message is an SRv6 message, the first message header is a hop-by-hop options header or a destination options header DOH, and the hop-by-hop options header or the DOH is used to carry the first slice identifier.

17. The method according to claim 11 or 12, characterized in that: The first network domain is an Internet Protocol version 6 IPv6 domain, the first message is an IPv6 message, the first message header is an IPv6 extension header, and the IPv6 extension header is used to carry the first slice identifier.

18. A message forwarding device, characterized in that: Applied to a first network node located at the junction of a first network domain and a second network domain, the device comprises: A receiving module, used to receive a first message from the first network domain, where the first message includes a first message header matching the first network domain, and the first message header includes a first slice identifier for indicating a first network slice; A processing module, configured to obtain a second message based on the second network domain and the first message, wherein the second message includes a second message header matching the second network domain, the second message header includes a second slice identifier for indicating a second network slice, and the second message header is different from the first message header; A sending module, used to send the second message in the second network domain based on the second slice identifier.

19. The device according to claim 18, characterized in that The processing module is used for: Determine the second slice identifier according to the first slice identifier and a first mapping relationship, where the first mapping relationship includes a mapping relationship between the first slice identifier and the second slice identifier; Based on the first message, the second slice identifier and the second network domain, obtain the second message.

20. The device according to claim 18 or 19, characterized in that The first network domain is a virtual local area network (VLAN) domain, the first message header is an Ethernet header, and the slice indication field of the Ethernet header is used to carry the first slice identifier; The second network domain is a virtual extended local area network VXLAN domain, the second message is a VXLAN message, the second message header is a VXLAN header, and the reserved field or extended field of the VXLAN header is used to carry the second slice identifier.

21. The device according to claim 18 or 19, characterized in that The first network domain is a virtual local area network (VLAN) domain, the first message header is an Ethernet header, and the slice indication field of the Ethernet header is used to carry the first slice identifier; The second network domain is a general network virtual encapsulation GENEVE domain, the second message is a GENEVE message, the second message header is a GENEVE header, and the extension field of the GENEVE header is used to carry the second slice identifier.

22. The device according to claim 18 or 19, characterized in that The first network domain is a virtual local area network (VLAN) domain, the first message header is an Ethernet header, and the slice indication field of the Ethernet header is used to carry the first slice identifier; The second network domain is a segment routing SRv6 domain based on Internet Protocol version 6 IPv6, the second message is an SRv6 message, The second message header is a hop-by-hop option header or a destination option header DOH, and the hop-by-hop option header or the DOH is used to carry the second slice identifier.

23. The device according to claim 18 or 19, characterized in that The first network domain is a virtual local area network (VLAN) domain, the first message header is an Ethernet header, and the slice indication field of the Ethernet header is used to carry the first slice identifier; The second network domain is an Internet Protocol version 6 IPv6 domain, the second message is an IPv6 message, the second message header is an IPv6 extension header, and the IPv6 extension header is used to carry the second slice identifier.

24. The device according to claim 18 or 19, characterized in that The first network domain is a virtual extended local area network VXLAN domain, the first message is a VXLAN message, the first message header is a VXLAN header, and the reserved field or extended field of the VXLAN header is used to carry the first slice identifier; The second network domain is a virtual local area network (VLAN) domain, the second message header is an Ethernet header, and the slice indication field of the Ethernet header is used to carry the second slice identifier.

25. The device according to claim 18 or 19, characterized in that The first network domain is a general network virtual encapsulation GENEVE domain, the first message is a GENEVE message, the first message header is a GENEVE header, and the extension field of the GENEVE header is used to carry the first slice identifier; The second network domain is a virtual local area network (VLAN) domain, the second message header is an Ethernet header, and the slice indication field of the Ethernet header is used to carry the second slice identifier.

26. The device according to claim 18 or 19, characterized in that The first network domain is a segment routing SRv6 domain based on Internet Protocol version 6 IPv6, the first message is an SRv6 message, the first message header is a hop-by-hop option header or a destination option header DOH, and the hop-by-hop option header or the DOH is used to carry the first slice identifier; The second network domain is a virtual local area network (VLAN) domain, the second message header is an Ethernet header, and the slice indication field of the Ethernet header is used to carry the second slice identifier.

27. The device according to claim 18 or 19, characterized in that The first network domain is an Internet Protocol version 6 IPv6 domain, the first message is an IPv6 message, the first message header is an IPv6 extension header, and the IPv6 extension header is used to carry the first slice identifier; The second network domain is a virtual local area network (VLAN) domain, the second message header is an Ethernet header, and the slice indication field of the Ethernet header is used to carry the second slice identifier.

28. A message forwarding device, characterized in that: Applied to a second network node located at an entrance of a first network domain, the device comprises: A processing module, configured to obtain a first message based on an original message from a user equipment, wherein the first message includes a first message header matching the first network domain, and the first message header includes a first slice identifier for indicating a first network slice; A sending module, used to send the first message in the first network domain based on the first slice identifier.

29. The device according to claim 28, characterized in that The sending module is used to send the first message to a first network node located at the junction of the first network domain and the second network domain based on the first slice identifier, and the second network domain is different from the first network domain.

30. The device according to claim 28 or 29, characterized in that The first network domain is a virtual local area network (VLAN) domain, the first message header is an Ethernet header, and the slice indication field of the Ethernet header is used to carry the first slice identifier.

31. The device according to claim 28 or 29, characterized in that The first network domain is a virtual extended local area network VXLAN domain, the first message is a VXLAN message, the first message header is a VXLAN header, and the reserved field or extended field of the VXLAN header is used to carry the first slice identifier.

32. The device according to claim 28 or 29, characterized in that The first network domain is a general network virtual encapsulation GENEVE domain, the first message is a GENEVE message, the first message header is a GENEVE header, and the extension field of the GENEVE is used to carry the first slice identifier.

33. The device according to claim 28 or 29, characterized in that The first network domain is a segment routing SRv6 domain based on Internet Protocol version 6 IPv6, the first message is an SRv6 message, the first message header is a hop-by-hop options header or a destination options header DOH, and the hop-by-hop options header or the DOH is used to carry the first slice identifier.

34. The device according to claim 28 or 29, characterized in that The first network domain is an Internet Protocol version 6 IPv6 domain, the first message is an IPv6 message, the first message header is an IPv6 extension header, and the IPv6 extension header is used to carry the first slice identifier.

Citation Information

Patent Citations

  • Message forwarding method, device and system

    CN119011337A

  • Cross-network slice segment routing forwarding method and device

    CN110266594A

  • Data transmission method and device based on segment routing

    CN114629836A

  • Message processing method and related device

    CN114844962A

  • Mapping and stitching network slices across various domains based on a border gateway protocol attribute

    US20230007568A1