Message forwarding method, device and system

By carrying slice identifiers in the message header, slice identifier switching between network nodes is solved, and the problem of cross-domain interoperability of network slices in the prior art is improved, and the efficiency of message forwarding and end-to-end slice guarantee of services is improved. It is suitable for VLAN , VXLAN and other network scenarios.

CN119011337APending Publication Date: 2024-11-22HUAWEI TECH CO LTD
View PDF 0 Cites 4 Cited by

Patent Information

Application Number
CN202310575254.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-05-19
Publication Date
2024-11-22

AI Technical Summary

Technical Problem

The existing slicing technology cannot achieve cross-domain interoperability of network slicing, resulting in the need to re-recognize services when packets are cross-domain, and the complex configuration and forwarding efficiency are deteriorated, making it difficult to achieve end-to-end slicing guarantee of services in VLAN, VXLAN and other networks.

Method used

By carrying slice identification in the message header, slice identification switching between network nodes is realized, allowing the first network slice and the second network slice to communicate across domains, avoiding re-service identification and complex configuration, and improving forwarding efficiency.

Benefits of technology

It realizes interoperability of network slices across VLAN, VXLAN, GENEVE, SRv6, and IPv6 domains, improves packet forwarding efficiency, simplifies the maintenance and management of network slices, and ensures the SLA quality of high-priority services.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119011337A_ABST
    Figure CN119011337A_ABST
Patent Text Reader

Abstract

The invention discloses a message forwarding method, device and system, and belongs to the technical field of networks. A first network node located at the junction of a first network domain and a second network domain receives a first message from the first network domain, the first message comprises a first message header matched with the first network domain, and the first message header comprises a first slice identifier used for indicating a first network slice; the first network node obtains a second message based on the second network domain and the first message, the second message comprises a second message header matched with the second network domain, the second message header comprises a second slice identifier used for indicating a second network slice, and the second message header is different from the first message header; and the first network node sends the second message in the second network domain based on the second slice identifier. According to the invention, cross-domain intercommunication of network slices can be realized.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

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

[0002] A network slice is a virtual network obtained by dividing the resources of a physical network. Different network slices obtained by dividing the same physical network are isolated from each other, and different network slices are used to meet the needs of different services. Network nodes can forward messages through network slices to prevent messages from different services from occupying resources.

[0003] In mainstream slicing technology, a slice identifier is carried in a message to guide the message to the network slice indicated by the slice identifier for forwarding. However, the current method of carrying a slice identifier in a message cannot achieve cross-domain interoperability of network slices. Summary of the invention

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

[0005] 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 receives a first message from the first network domain, the first message includes a first message header matching the first network domain, the first message header includes a first slice identifier (slice identifier, slice ID) for indicating a first network slice; 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 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 a 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.

[0006] 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 switching between 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 complex configuration of network nodes for re-identifying services and degradation of forwarding efficiency when messages cross domains, and improving message forwarding efficiency.

[0007] Optionally, 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 the first mapping relationship, 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. 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.

[0008] 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 according to the first mapping relationship and the first slice identifier in the first message header included in the first message, which 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 network nodes to re-identify services and the degradation of forwarding efficiency when the message crosses domains, thereby improving the message forwarding efficiency.

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

[0010] 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 the 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, the intercommunication between the first network slice and the second network slice across the VLAN domain and the VXLAN domain is realized. Therefore, the present application can realize the intercommunication between network slices across the VLAN domain and the VXLAN domain. Moreover, in the present application, a slice identifier can be carried in the ETH header or the VXLAN header, and the network node can forward the message according to the slice identifier carried in the ETH header or the VXLAN header, so that the technical solution of the present application can be applied to VLAN networks and VXLAN networks.

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

[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 GENEVE domain, the first network node realizes the 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, the intercommunication between the first network slice and the second network slice across the VLAN domain and the GENEVE domain. Therefore, the present application can realize the intercommunication between network slices across the VLAN domain and the GENEVE domain. Moreover, in the present application, a slice identifier can be carried in the ETH header or the GENEVE header, and the network node can forward the message according to the slice identifier carried in the ETH header or the GENEVE header, so that the technical solution of the present application can be applied to VLAN networks and GENEVE 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 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.

[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 an SRv6 domain, the first network node realizes the 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, the intercommunication between the first network slice and the second network slice across the VLAN domain and the SRv6 domain. Therefore, the present application can realize the intercommunication between network slices across the VLAN domain and the SRv6 domain. Moreover, in the present application, the 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, so that the technical solution of the present application can be applied to VLAN networks and SRv6 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 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.

[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 IPv6 domain, the first network node realizes the 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, the intercommunication between the first network slice and the second network slice across the VLAN domain and the IPv6 domain. Therefore, the present application can realize the intercommunication between network slices across the VLAN domain and the IPv6 domain. Moreover, in the present application, the slice identifier can be carried in the ETH header or the 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, so that the technical solution of the present application can be applied to VLAN networks and IPv6 networks.

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

[0018] 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 the 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, the 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 the intercommunication between network slices across the VXLAN domain and the VLAN domain. Moreover, in the present application, a slice identifier can be carried in a VXLAN header or an ETH header, and the network node can forward the message according to the slice identifier carried in the VXLAN header or the ETH header, so that the technical solution of the present application can be applied to VXLAN networks and VLAN networks.

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

[0020] 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 the 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, the 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 the 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, so that the technical solution of the present application can be applied to GENEVE networks and VLAN networks.

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

[0022] 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 the 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, the 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 the intercommunication between network slices across the SRv6 domain and the VLAN domain. Moreover, in the present application, the 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, so that the technical solution of the present application can be applied to SRv6 networks and VLAN networks.

[0023] 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, and the IPv6 extension header 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.

[0024] 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 the 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, the 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 the intercommunication between network slices across the IPv6 domain and the VLAN domain. Moreover, in the present application, the 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, so that the technical solution of the present application can be applied to IPv6 networks and VLAN networks.

[0025] In a second aspect, a message forwarding method is provided, which is applied to a second network node located at an entrance of a first network domain, the method comprising: the second network node obtains a first message based on an original message from a user device, the first message 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; the second network node sends the first message in the first network domain based on the second slice identifier. The first network slice is deployed in the first network domain.

[0026] Optionally, the second network node sending the first message in the first network domain based on the first slice identifier includes: the second network node sending 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. The second network domain is deployed with a second network slice.

[0027] 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 network nodes to re-identify services and the degradation of forwarding efficiency when the messages cross domains, and improving the message forwarding efficiency.

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

[0029] The technical solution provided by the present application, when the first network domain is a VLAN domain, can carry a slice identifier in the ETH header of the VLAN message, 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.

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

[0031] The technical solution provided by the present application, when the first network domain is a VXLAN domain, can carry a slice identifier in the VXLAN header of the VXLAN message, 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.

[0032] 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 an extension field of the GENEVE header is used to carry a first slice identifier.

[0033] The technical solution provided by the present application, when the first network domain is a GENEVE domain, can carry a slice identifier in the GENEVE header of the GENEVE message, 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.

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

[0035] The technical solution provided by the present application, when the first network domain is an SRv6 domain, can carry a slice identifier in the HBH or DOH of the SRv6 message, 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.

[0036] 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, and the IPv6 extension header is used to carry a first slice identifier.

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

[0038] 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, and 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.

[0039] 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, a 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, a SRv6 domain or an IPv6 domain, so the type of the first network domain is different from the type of the second network domain. For 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, a SRv6 domain or an IPv6 domain; when the first network domain is a GENEVE domain, the second network domain can be a VXLAN domain, a SRv6 domain or an IPv6 domain.

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

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

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

[0043] In a 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 a method provided in the first aspect or any optional manner of the first aspect, or so that the message forwarding device executes a method provided in the second aspect or any optional manner of the second aspect.

[0044] 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 by 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 by the above-mentioned second aspect or any optional method of the second aspect.

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

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

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

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

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

[0050] 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 switching between 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 complex configuration of network nodes for re-identifying services and degradation of forwarding efficiency when messages cross domains, and improving 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

[0051] Figure 1 It is a schematic diagram of the underlying implementation of network slicing;

[0052] Figure 2 It is a schematic diagram of an application scenario provided by an embodiment of the present application;

[0053] Figure 3 is a schematic diagram of another application scenario provided by an embodiment of the present application;

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

[0055] Figure 5 It is a flow chart of a message forwarding method provided in an embodiment of the present application;

[0056] Figure 6 is a schematic diagram of an original message provided in an embodiment of the present application;

[0057] Figure 7 is a schematic diagram of a first message provided in an embodiment of the present application;

[0058] Figure 8 is a schematic diagram of another first message provided in an embodiment of the present application;

[0059] Fig. 9 is a schematic diagram of another first message provided in an embodiment of the present application;

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

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

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

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

[0064] Fig.14 It is a schematic diagram of a message forwarding method provided in an embodiment of the present application;

[0065] Fig.15 It is a schematic diagram of a message forwarding device provided in an embodiment of the present application;

[0066] Fig.16 is a schematic diagram of another message forwarding device provided in an embodiment of the present application;

[0067] Fig.17 It is a schematic diagram of another message forwarding device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0068] The implementation methods of the present application will be further described below in conjunction with the accompanying drawings.

[0069] The Internet Protocol (IP) bearer network is a resource-sharing network, which causes different services to occupy network resources. In order to ensure the service-level agreement (SLA) quality of high-priority services, quality of service (QoS) technology and hierarchical quality of service (HQoS) technology are proposed. These technologies guarantee the SLA quality of high-priority services by forwarding high-priority services first. However, in these technologies, low-priority services and high-priority services will still occupy network resources, making it difficult to ensure the deterministic SLA quality and service experience of high-priority services. Among them, high-priority services include services with higher priority and services of users with higher priority, and low-priority services include services with lower priority and services of users with lower priority. For example, the priority of video services is higher than that of email services, video services are high-priority services, and email services are low-priority services. For another example, for video service 1, the priority of user A is higher than that of user B, user A's video service 1 is a high-priority service, and user B's video service 1 is 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.

[0070] In order to provide deterministic SLA quality for high-priority services, slicing technology is proposed. Slicing technology is a "hard" isolation technology for resource reservation. This technology reserves network resources for high-priority services, allowing high-priority services to monopolize network resources and prevent low-priority services from competing with high-priority services for network resources, thereby ensuring the SLA quality of high-priority services. Slicing technology is of great value in isolating different services and ensuring the SLA quality of high-priority services.

[0071] The underlying technologies used to implement resource reservation and service isolation in slicing technology include flexible Ethernet (FlexE) technology, channelized sub-interface technology, and flexible channel (FlexChannel) technology. General network devices (such as routers and switches) can support one or more of these three underlying technologies, and these three underlying technologies can be nested to implement "slices within slices". Among them, the nested use of these three underlying technologies is as follows: Figure 1 Reference 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. A network slice deployed based on a flexible channel or a channelized sub-interface is a sub-slice in a network slice deployed based on the FlexE interface to which the flexible channel or the channelized sub-interface belongs, thereby realizing "slices within slices".

[0072] The industry's slice control solutions include: slice control solutions based on flexible algorithms (Flex-Algo), slice control solutions based on interface slice identifiers, slice control solutions based on routing affinity attributes, and slice control solutions based on data planes carrying slice identifiers. These slice control solutions are used to control message forwarding so that messages 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 the 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 planes carrying slice identifiers controls the forwarding of messages by carrying slice identifiers in messages. This slice control solution is simple and efficient, and has a wider range of applicable scenarios. However, the current slice control scheme 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 scheme 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 of 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. Among them, the reasons why campus networks are generally Layer 2 VLAN networks or large virtual Layer 2 networks based on VXLAN and GENEVE include: simplifying network operations and achieving plug-and-play (that is, devices can be used as soon as they are connected to the network); for security reasons, campus networks use MAC to identify, authenticate, and trace terminals and users; for flexible business planning and deployment, the upper-layer business network and the underlying physical network (that is, the underlay network) are decoupled. Campus VLAN, VXLAN, GENEVE Layer 2 or large Layer 2 networking will exist and evolve for a long time.

[0073] The embodiment of the present application provides a message forwarding solution, and 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, so as to realize the switching of the message between the network slices of different network domains, realize the intercommunication of network slices across domains, avoid the complex configuration and forwarding efficiency degradation of the network nodes re-identifying the service when the message crosses the domain, and improve 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, and avoid the complex configuration and forwarding efficiency degradation of the re-identification of the service 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.

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

[0075] The 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.

[0076] 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. Here, only the combination of the first network domain and the second network domain is exemplarily described, 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 the embodiments of the present application do not limit this.

[0077] Among them, the VLAN domain is a layer 2 network domain, the SRv6 domain and the IPv6 domain are both layer 3 network domains, and the VXLAN domain and the GENEVE domain are both overlay network domains. The overlay network domain is an upper-layer virtual network built based on the underlying (underlay) network. The overlay network domain is also called the overlay virtual network domain, the 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, the underlying physical network, the lower-layer bearer network, the lower-layer physical network, etc. Optionally, the layer 3 network domain is the Internet, the operator's private network, the wide area network (WAN), the software defined wide area network (SDWAN), etc.

[0078] Optionally, the at least two network domains further include a cloud network, which is used to provide various cloud services, which may include cloud computing services, cloud storage services, etc. In the present application, the at least two network domains include a campus network, which may be a VLAN domain, a VXLAN domain, or a GENEVE domain. Different campus networks are directly interconnected, or different campus networks are interconnected through SRv6 domains, IPv6 domains, etc., so that different campus networks can visit each other. The campus network can be interconnected with the cloud network through SRv6 domains, IPv6 domains, etc., so that the campus network can access various cloud services provided by the cloud network.

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

[0080] As an example, see 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, and 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.

[0081] As another example, see 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 VLAN domains, VXLAN domains, GENEVE domains, SRv6 domains or IPv6 domains, respectively, 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 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 Figure 1 As shown, 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, so that network node B is located at the junction of network domain 1 and network domain 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, 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, 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 entrance node of network domain 1 and the exit node of network domain 2, and network node C is the entrance 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.

[0082] See also Figure 3 , take network domain 1 as a VLAN domain and network domain 2 as a VXLAN domain as an example. 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. Network node A receives a message from a user device (the user device is connected to network node A and accesses network domain 1 through network node A, Figure 3After receiving the original message P0 from the user device (the user device is not shown for simplicity), network node A obtains message P1 based on the original message P0. Message P1 includes an ETH header matching network domain 1 (VLAN domain). The ETH header includes a slice identifier 1 for indicating network slice 1. Network node A determines network slice 1 according to slice identifier 1. 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 a slice identifier 2 for indicating network slice 2 according to 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 matching network domain 2. The VXLAN header includes slice identifier 2. Network node B determines network slice 2 according to slice identifier 2. 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 the VLAN domain and / or the VXLAN domain. 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, so as to realize the switching of messages between network slice 1 and network slice 2, realize cross-domain intercommunication between network slice 1 and network slice 2, avoid the complex configuration of network nodes to re-identify services and the degradation of forwarding efficiency when messages cross domains, and improve the message forwarding efficiency.

[0083] As another example, see 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 VLAN domains, VXLAN domains, GENEVE domains, SRv6 domains or IPv6 domains respectively, 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 Figure 1As shown, 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, so that network node B is located at the junction of network domain 1 and network domain 2, and network node C is located at the junction of network domain 2 and network domain 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, 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 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, network node C is located at the entrance of network domain 2 and at the exit of network domain 3, network node D is located at the entrance of network domain 3, network node A is the exit node of network domain 1, network node B is the entrance node of network domain 1 and the exit node of network domain 2, network node C is the entrance node of network domain 2 and the exit node of network domain 3, and network node D is the entrance 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.

[0084] See also Figure 4 , take network domain 1 as a VLAN domain, network domain 2 as an IPv6 domain, and network domain 3 as a GENEVE domain as an example. 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 and the entry node of network domain 3, network node D is the exit 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. Network node A receives a message from a user device (the user device is connected to network node A and accesses network domain 1 through network node A), Figure 4After receiving the original message P0 from the user equipment (the user equipment is not shown for simplicity), network node A obtains message P1 based on the original message P0, message P1 includes an ETH header matching network domain 1 (VLAN domain), the ETH header includes slice identifier 1 for indicating network slice 1, network node A determines network slice 1 according to 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 according to 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 matching network domain 2, the IPv6 extension header includes slice identifier 2, network node B determines network slice 2 according to 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 determines slice identifier 3 for indicating network slice 3 according to 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 matching network domain 3, the GENEVE header includes slice identifier 3, network node C determines network slice 3 according to slice identifier 3, and 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 original message P0, and forwards original message P0. Therefore, the present application carries a slice identifier in an ETH header, an IPv6 extension header or a 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 a VLAN domain and / or an IPv6 domain and / or a GENEVE header. In addition, the network node B located at the junction of network domain 1 and network domain 2 can switch slice identifier 1 and slice identifier 2, so as to switch the message between network slice 1 and network slice 2, and realize cross-domain intercommunication between network slice 1 and network slice 2; the network node C located at the junction of network domain 2 and network domain 3 can switch slice identifier 2 and slice identifier 3, so as to switch the message between network slice 2 and network slice 3, and realize cross-domain intercommunication between network slice 2 and network slice 3. Finally, cross-domain intercommunication between network slices 1 to 3 can be realized, avoiding the complex configuration of network nodes to re-identify services and the degradation of forwarding efficiency when messages cross domains.

[0085] Figures 2 to 4 The message forwarding system shown is only used as an example and is not intended to limit the technical solution of the present application. In the implementation process, the message forwarding system may include Figures 2 to 4The message forwarding system may further include a control device to control the network domains in the message forwarding system, which is not limited in the embodiments of the present application.

[0086] The above is an introduction to the application scenarios of the present application. The following is an introduction to the method implementation examples of the present application.

[0087] Please refer to Figure 5 , which shows a flow chart of a message forwarding method provided by 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 a first network domain and a second network domain, and the second network node is located at the entrance of the first network domain. In an example, the message forwarding system is as follows Figure 3 As shown, 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 as follows Figure 4 As shown, 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. Figure 5 As shown, the method includes the following steps S501 to S506.

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

[0089] 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 entry node of the 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.

[0090] 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, a SRv6 domain or an IPv6 domain, and correspondingly, the first tunnel is a VLAN tunnel, a VXLAN tunnel, a GENEVE tunnel, a SRv6 tunnel or an IPv6 tunnel.

[0091] In an embodiment of the present application, the original message from the user equipment 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 may be an ETH message, and the layer 3 message may 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, and 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, and 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, and the UDP header is used to carry the UDP information of the original message, and 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. Take the original message as an example, the original message is a layer 3 message. Figure 6 The original message includes a payload Q and a UDP header 1, an IP header 1, and an ETH header 1 which are sequentially 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. Figure 6 The original message shown is for example only. The original message may also include Figure 6 This application does not limit the contents not shown.

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

[0093] 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, and 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 quintuple, an IP triplet, etc., and the MAC information includes SMAC, DMAC, etc.

[0094] In an embodiment of the present application, the first message includes a first message header that matches the 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 is different and the first message header is different. The following takes the first network domain as a VLAN domain, a VXLAN domain, a GENEVE domain, an SRv6 domain, and an IPv6 domain as an example, and describes the implementation process of S502 in five embodiments.

[0095] First embodiment: the first network domain is a VLAN domain, the first message is a VLAN message (the VLAN message is a layer 2 message), the first message header is an ETH header (the 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.

[0096] In one example, the first message is Figure 7 As shown, 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), and 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, and the slice indication field includes an Ethernet type subfield and a slice identification 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 identification subfield is used to carry a slice identification. Reference Figure 6 and Figure 7 , the second network node can be Figure 6 The VLAN tag field and the slice indication field are added to the ETH header 1 of the original message, and a VLAN tag is added to the VLAN tag field, and the second network node sets the value of the Ethernet type subfield to 0x8100 or a newly defined value, and the second network node adds the first slice identifier to the slice identifier subfield, and the result is as follows: Figure 7 The first message is shown.

[0097] In another example, the first message is as follows: Figure 8As shown, 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), and 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, and 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. Figure 8 As shown, the DIP subfield includes an Ethernet type space, a tiger (Tiger, T) space, a label (Lable) space, a next header (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 identifier subfield. Figure 6 and Figure 8 , the second network node can be Figure 6 The VLAN tag field and the slice indication field are added to the ETH header 1 of the original message, and a VLAN tag is added to the VLAN tag field, and the second network node sets the value of the Ethernet type space to 0x8888, and sets the next header space to indicate the slice identification subfield, and the second network node adds the first slice identification in the slice identification subfield, and obtains the following: Figure 8 The first message is shown.

[0098] exist Figure 7 and Figure 8 In the first message shown, 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, which are not shown in the figure for brevity. Figure 7 and Figure 8 These subfields are shown in the figure. For the meaning of each subfield in the VLAN tag field, please refer to the VLAN protocol. Optionally, ETH header 2 includes an outer VLAN tag field and an inner VLAN tag field. Figure 7 and Figure 8 The VLAN tag field shown in is an outer VLAN tag field, and the slice indication field may be an inner VLAN tag field. Figure 8 For the first message shown in FIG. 1 , the DIP subfield is also called a DIP header. Figure 7In the first message shown, 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. Figure 7 In the first message shown, 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 (that is, the slice indication field) carrying the slice identifier and the double-layer VLAN characteristics, 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. Figure 7 In the first message shown, the value of the Ethernet type subfield is a newly defined value. The scalability of the implementation method is high. The NP chip can support the implementation method, or the relevant capabilities are pre-embedded in the ASIC chip in advance to support the implementation method, or the implementation method is supported by an external field-programmable gate array (FPGA) chip. Figure 8 As shown in the first message, the NP chip can support the implementation, or the relevant capabilities can be pre-embedded in the ASIC chip to support the implementation, or the implementation can be supported by an external FPGA chip.

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

[0100] In one example, the first message is Fig. 9 As shown, 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 among the 8 flag bits is used to indicate the legitimacy of the VXLAN ID. The remaining flag bits among the 8 flag bits are 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. Reference Figure 6 and Fig. 9 , the second network node can be Figure 6 The original message is encapsulated in sequence with a VXLAN header, a UDP header 2, an IP header 2, and an ETH header 3. The second network node adds the first slice identifier to the reserved field 1 in the VXLAN header, and obtains the following Fig. 9 The first message is shown. Fig. 9 Taking the example of carrying a slice identifier in reserved field 1, a slice identifier can also be carried in reserved field 2. Since the length of reserved field 1 is greater than the length of reserved field 2 (the length of reserved field 1 is 24 bits, and the length of reserved field 2 is 8 bits), compared with reserved field 2, reserved field 1 can support longer slice identifiers and can support cross-domain unified planning of slice identifiers.

[0101] In another example, the first message is as follows: Fig.10As shown, 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 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, and 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 flag 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). The slice identifier subfield is used to carry a slice identifier. Reference Figure 6 and Fig.10 , the second network node can be Figure 6 The original message is encapsulated in sequence with a VXLAN header, a UDP header 2, an IP header 2, and an ETH header 3. The second network node sets an extension field in the VXLAN header and adds a first slice identifier to the extension field to obtain the following: Fig.10 The first message is shown.

[0102] In another example, the first message is as follows Fig.11As shown, 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 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 reserved field 2 is a bitmap field, and the bitmap field is used to indicate which service information is included in the extension field. For example, the bitmap field includes multiple bits, each bit corresponds to a service, and each bit is used to indicate whether the extension field includes service information of the corresponding service. The value of each bit can be 0 or 1, "1" is used to indicate that the extension field includes service information of the service corresponding to each bit, and "0" is used to indicate that the extension field does not include service information of 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 extension field carries a slice identifier. In one example, the first bit indicates that the extended field includes a slice indication field, 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 the slice identification. Figure 6 and Fig.11 , the second network node can be Figure 6 The original message is encapsulated in sequence with a VXLAN header, a UDP header 2, an IP header 2, and an ETH header 3. The second network node sets an extension field in the VXLAN header. The second network node sets the value of the first bit in the bitmap field to 1, and sets the extension field to include a slice indication field. The second network node adds a first slice identifier to the slice indication field, and obtains the following: Fig.11 The first message shown in the figure. By setting the bitmap field, the present application can encapsulate the service information of multiple services in an integrated manner in the extension field, thereby improving the message encapsulation efficiency.

[0103] A third embodiment: the first network domain is a GENEVE domain, the first message is a GENEVE message, the first message header is a GENEVE header, the GENEVE header includes an extension field, the extension field is used to carry 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 the second network node adds the first slice identifier to the GENEVE header to obtain the first message.

[0104] In one example, the first message is Fig.12 or Fig.13As shown, the first message 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), and 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 is used to carry version information. The option length field is used to indicate the length of the option field, and the length of the option field is variable. The O field is used to indicate that the message including the O field is an operation administration and maintenance (OAM) message. The C field is used to indicate that there are one or more critical options in the option field. The protocol type field is used to carry the protocol type. The VNI field is used to carry 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. Fig.12 and Fig.13 It can be seen that in Fig.12 In the first message shown, the extended subfield also includes a reserved space, and the length of the slice identification space is relatively large. Fig.12 The length of the slice identification space in the first message is 32 bits. Fig.13 The length of the slice identification space in the first message shown is 24 bits. Figure 6 , Fig.12 and Fig.13 , the second network node can be Figure 6 The original message is encapsulated in sequence with a GENEVE header, a UDP header 2, an IP header 2, and an ETH header 3. The second network node adds the first slice identifier to the extended subfield in the GENEVE header, and obtains the following: Fig.12 or Fig.13 The first message is shown.

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

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

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

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

[0109] above Figures 9 to 11 The first message shown is a second network node pair Figure 6 The original message shown is obtained by performing VXLAN encapsulation. When the second network node performs VXLAN encapsulation on the original message, it sequentially encapsulates a VXLAN header, a UDP header 2, an IP header 2, and an ETH header 3 outside the original message. Figure 12 to Figure 13 The first message shown is a second network node pair Figure 6 The original message shown in FIG. is GENEVE encapsulated and obtained. When the second network node performs GENEVE encapsulation on the original message, it sequentially encapsulates a GENEVE header, a UDP header 2, an IP header 2, and an ETH header 3 outside the original message. Figures 9 to 13 As shown, 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 refer to the VXLAN protocol and relevant standard documents on VXLAN encapsulation, which will not be repeated here.

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

[0111] Optionally, the second network node sends a 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. For example, the second network node determines the first network slice according to the first slice identifier, and the second network node sends and 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 to the message queue, and the second network node sends the first message to the first network node according to the order of the first message in the message queue.

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

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

[0114] In an embodiment of the present application, the first network node is located at the junction of the first network domain and the second network domain, and the first network node is not only an egress node of the first network domain, but also an entry node of the second network domain. In one embodiment, the first network node is the head node of the second tunnel in the second network domain. Wherein, 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 another example, the second network domain is a GENEVE domain, and the second tunnel is a GENEVE tunnel. In another example, the second network domain is an SRv6 domain, and the second tunnel is an SRv6 tunnel. In another example, the second network domain is an IPv6 domain, and the second tunnel is an IPv6 tunnel.

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

[0116] Optionally, the first network node determines the second slice identifier according to 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.

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

[0118] In an embodiment of the present application, the first mapping relationship is a mapping relationship generated according to the configuration information sent 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 sent 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 according to the configuration information including the first slice identifier and the second slice identifier. 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.

[0119] 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 matching the second network domain is an ETH header, a VXLAN header, a GENEVE header, an HBH (or DOH), and an IPv6 extension header. Among them, 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 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.

[0120] Among them, 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.

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

[0122] In another embodiment, the first network domain is a VLAN domain, the second network domain is a GENEVE domain, and the first message is as follows: Figure 7 or Figure 8 As shown, the first network node performs VLAN decapsulation on the first message to obtain the following Figure 5 The first network node performs GENEVE encapsulation on the original message to obtain a second message. The structure of the second message can be referred to Fig.12 or Fig.13 The first message is shown.

[0123] In another embodiment, the first network domain is a VLAN domain, the second network domain is an SRv6 domain, and the first message is as follows: Figure 7 or Figure 8 As shown, the first network node performs VLAN decapsulation on the first message to obtain the following Figure 5 The original message shown, 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.

[0124] In another embodiment, the first network domain is a VLAN domain, the second network domain is an IPv6 domain, and the first message is as follows: Figure 7 or Figure 8 As shown, the first network node performs VLAN decapsulation on the first message to obtain the following Figure 5The original message shown, 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.

[0125] In another embodiment, the first network domain is a VXLAN domain, the second network domain is a VLAN domain, and the first message is as follows: Figures 9 to 11 As shown in any one, 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 Figure 5 The first network node performs VLAN encapsulation on the original message to obtain a second message. The structure of the second message can be referred to Figure 7 or Figure 8 The first message is shown.

[0126] In another embodiment, the first network domain is a VXLAN domain, the second network domain is a GENEVE domain, and the first message is as follows: Figures 9 to 11 As shown in any one of the above, the first network node performs VXLAN decapsulation on the first message to obtain the following Figure 5 The first network node performs GENEVE encapsulation on the original message to obtain a second message. The structure of the second message can be referred to Fig.12 or Fig.13 The first message is shown.

[0127] In another embodiment, the first network domain is a VXLAN domain, the second network domain is an SRv6 domain, and the first message is as follows: Figures 9 to 11 As shown in any one of the above, the first network node performs VXLAN decapsulation on the first message to obtain the following Figure 5 The original message shown, 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.

[0128] In another embodiment, the first network domain is a VXLAN domain, the second network domain is an IPv6 domain, and the first message is as follows: Figures 9 to 11 As shown in any one of the above, the first network node performs VXLAN decapsulation on the first message to obtain the following Figure 5 The original message shown, 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.

[0129] In another embodiment, the first network domain is a GENEVE domain, the second network domain is a VLAN domain, and the first message is as follows: Fig.12 or Fig.13As shown, 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 following Figure 5 The first network node performs VLAN encapsulation on the original message to obtain a second message. The structure of the second message can be referred to Figure 7 or Figure 8 The first message is shown.

[0130] In another embodiment, the first network domain is a GENEVE domain, the second network domain is a VXLAN domain, and the first message is as follows: Fig.12 or Fig.13 As shown, the first network node performs GENEVE decapsulation on the first message to obtain the following Figure 5 The first network node performs VXLAN encapsulation on the original message to obtain a second message. The structure of the second message can be referred to Figures 9 to 11 Any first message shown.

[0131] In another embodiment, the first network domain is a GENEVE domain, the second network domain is an SRv6 domain, and the first message is as follows: Fig.12 or Fig.13 As shown, the first network node performs GENEVE decapsulation on the first message to obtain the following Figure 5 The original message shown, 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.

[0132] In another embodiment, the first network domain is a GENEVE domain, the second network domain is an IPv6 domain, and the first message is as follows: Fig.12 or Fig.13 As shown, the first network node performs GENEVE decapsulation on the first message to obtain the following Figure 5 The original message shown, 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.

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

[0134] In another embodiment, the first network domain is an SRv6 domain, the second network domain is a VXLAN domain, and the first network node performs SRv6 decapsulation on the first message to obtain the following Figure 5 The first network node performs VXLAN encapsulation on the original message to obtain a second message. The structure of the second message can be referred to Figures 9 to 11 Any first message shown.

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

[0136] In another embodiment, the first network domain is an SRv6 domain, the second network domain is an IPv6 domain, and the first network node performs SRv6 decapsulation on the first message to obtain the following Figure 5 The original message shown, 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.

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

[0138] In another embodiment, the first network domain is an IPv6 domain, the second network domain is a VXLAN domain, and the first network node performs IPv6 decapsulation on the first message to obtain the following Figure 5 The first network node performs VXLAN encapsulation on the original message to obtain a second message. The structure of the second message can be referred to Figures 9 to 11 Any first message shown.

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

[0140] In another embodiment, the first network domain is an IPv6 domain, the second network domain is an SRv6 domain, and the first network node performs IPv6 decapsulation on the first message to obtain the following Figure 5 The original message shown, 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.

[0141] In an optional embodiment, before S505, the slice switching function is enabled in the first network node in advance, 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 can enable the slice switching function according to control information sent by the control device, which is not limited in this embodiment of the present application.

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

[0143] The first network node determines the second network slice according to 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 to the message queue, and the first network node sends the second message according to the order of the second message in the message queue.

[0144] To summarize, the technical solution provided by the embodiment of the present application is that the first message obtained by the second network node at the entrance of the first network domain based on the original message 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, 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 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, 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, and SRv6 networks, 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, and 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, and SRv6 networks, thereby implementing secure isolation of network resources for different services and ensuring the SLA quality of high-priority services. The switching solution for slice identifiers provided in the present application is suitable for different campus network interconnection scenarios and campus network and cloud network interconnection scenarios.

[0145] In order to facilitate understanding of the technical solution of this application, Figure 4 For example, network domain 1 is a VLAN domain, network domain 2 is an IPv6 domain, and network domain 3 is a VXLAN domain / GENEVE domain (VXLAN domain or GENEVE domain). Fig.14 Introduce the message forwarding method of this application. Fig.14 As shown, network node A is the entry node of the VLAN domain, network node B is the exit node of the VLAN domain and the entry node of the IPv6 domain, network node C is the exit node of the IPv6 domain and the entry node of the VXLAN domain / GENEVE domain, and network node D is the exit node of the VXLAN domain / GENEVE domain.

[0146] like Fig.14 As shown, the original message P0 includes a payload Q and a UDP header 1, an IP header 1, and an ETH header 1 that are sequentially encapsulated outside the payload Q. After network node A receives message P0, network node A performs VLAN encapsulation on message P0 to obtain message P1. Message P1 includes a payload Q and a UDP header 1, an IP header 1, and an ETH header 2 that are sequentially encapsulated outside the payload Q. ETH header 2 carries slice ID1, and slice ID1 indicates network slice 1 in the VLAN domain. Network node A determines network slice 1 based on slice ID1, and sends message P1 to network node B through network slice 1.

[0147] After network node B receives message P1, network node B determines slice ID2 for indicating network slice 2 in the IPv6 domain based on slice ID1 carried in message P1, performs VLAN decapsulation on message P1 to obtain message P0, and 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 encapsulated outside payload Q in sequence. The IPv6 extension header carries slice ID2, and slice ID2 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.

[0148] After network node C receives message P2, network node C determines slice ID3 for indicating network slice 3 in the VXLAN domain / GENEVE domain according to slice ID2 carried by message P2, and network node C performs IPv6 decapsulation on message P2 to obtain message P0, and network node C performs VXLAN encapsulation / GENEVE encapsulation (VXLAN encapsulation or GENEVE encapsulation) on message P0 based on slice ID3 to obtain message P3. Message P3 includes payload Q and 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 encapsulated outside payload Q in sequence, and the VXLAN header / GENEVE header carries slice ID3, and slice ID3 indicates network slice 3 in the VXLAN domain / GENEVE domain. Network node C determines network slice 3 according to slice ID3, and forwards message P3 to network node D through network slice 3.

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

[0150] 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 switch the slice ID, so as to realize the switching of messages between network slices in different network domains and realize the cross-domain intercommunication of network slices.

[0151] 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, which is convenient for 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 the degradation of message forwarding efficiency. In the 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 re-identifying the service, which can avoid the complex configuration and forwarding efficiency degradation of the network node re-identifying the service when the message crosses the domain, and improve the message forwarding efficiency.

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

[0153] The above is an introduction to the method embodiment of the present application. The following is an introduction to the device embodiment of the present application. The device of the present application can be used to execute the method of the present application. For details not disclosed in the device embodiment of the present application, please refer to the method embodiment.

[0154] Please refer to Fig.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, and 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. Fig.15 As shown, the message forwarding device 1500 includes a receiving module 1510 , a processing module 1520 and a sending module 1530 .

[0155] The receiving module 1510 is used to receive a first message from the first network domain, 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. For the functional implementation of the receiving module 1510, please refer to the description in S504.

[0156] The processing module 1520 is used 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, and the second message header includes a second slice identifier for indicating the second network slice. For the functional implementation of the processing module 1520, please refer to the description in S505.

[0157] The sending module 1530 is used 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.

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

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

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

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

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

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

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

[0165] 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 header is an Ethernet header, and the slice indication field of the Ethernet header is used to carry a second slice identifier.

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

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

[0168] To summarize, the technical solution provided by the embodiment of 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 obtains a second message based on the second network domain and the first message, and sends a 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. Thus, 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.

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

[0170] The processing module 1610 is used to obtain a first message based on the original message from the 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 the first network slice. For the functional implementation of the processing module 1610, please refer to the description in S502.

[0171] The sending module 1620 is used 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.

[0172] 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, and the second network domain is different from the first network domain.

[0173] 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 a slice indication field of the Ethernet header is used to carry a first slice identifier.

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

[0175] 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 an extension field of the GENEVE header is used to carry a first slice identifier.

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

[0177] 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, and the IPv6 extension header is used to carry a first slice identifier.

[0178] To summarize, 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.

[0179] The message forwarding device provided in the embodiment of the present application can also be implemented by ASIC or programmable logic device (PLD). The above PLD can be a complex programmable logical device (CPLD), FPGA, generic array logic (GAL) or any combination thereof. The method provided in the above method embodiment can also be implemented by software. When the method provided in the above method embodiment is implemented by software, each module in the above message forwarding device can also be a software module.

[0180] An embodiment of the present application provides a message forwarding device, including 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 method embodiment.

[0181] As an example, see Fig.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, such as Fig.17 As shown, 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 ( Fig.17 The switching network board is used to complete data exchange between the interface boards (the interface board is also called a line card or a service board).

[0182] The main control board 1710 is used to complete system management, equipment maintenance, protocol processing and other functions. The interface board 1730 and the interface board 1740 are used to provide various business interfaces (for example, POS interface, GE interface, ATM interface, etc.) and realize message forwarding. There are mainly three types of functional units on the main control board 1710: system management control unit, system clock unit and system maintenance unit. The main control board 1710, interface board 1730 and interface board 1740 are connected to the system backplane through the system bus to achieve intercommunication. The interface board 1730 includes one or more processors 1731. The processor 1731 is 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 the first mapping relationship described in the above embodiment, etc. As Fig.17 As shown, the main control board 1710 may include a memory 1714, and the memory 1714 on the main control board 1710 may also be used to store the first mapping relationship, etc., which is not limited in this embodiment of the present application.

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

[0184] It is understandable that Fig.17 As shown, this embodiment includes multiple interface boards and adopts a distributed forwarding mechanism. Under this mechanism, the operation on the interface board 1740 is basically similar to the operation on the interface board 1730, and for the sake of brevity, it will not be repeated. In addition, it can be understood that Fig.17 The processor 1731 in the interface board 1730 and / or the processor 1741 in the interface board 1740 may be dedicated hardware or chips, such as a network processor or a dedicated integrated circuit to implement the above functions. This implementation is what is commonly referred to as a forwarding plane using dedicated hardware or chip processing. In another embodiment, the processor 1731 in the interface board 1730 and / or the processor 1741 in the interface board 1740 may also be a general-purpose processor, such as a general-purpose central processing unit (CPU) to implement the above-described functions.

[0185] In addition, it should be pointed out that there may be one or more main control boards, and when there are multiple boards, they may include a main main control board and a standby main control board. There may be one or more interface boards. The stronger the data processing capability of the network node, the more interface boards are provided. In the case of multiple interface boards, the multiple interface boards can communicate with each other through one or more switching network boards, and when there are multiple boards, they can jointly realize load sharing and redundant backup. Under the centralized forwarding architecture, the network node may not need a switching network board, and the interface board is responsible for the processing function of the service data of the entire system. Under the distributed forwarding architecture, the network node includes multiple interface boards, and data exchange between multiple interface boards can be realized through the switching network board, providing large-capacity data exchange and processing capabilities. Therefore, the data access and processing capabilities of the network nodes of the distributed architecture are greater than those of the nodes of the centralized architecture. Which architecture to adopt depends on the networking deployment scenario, and no limitation is made here.

[0186] In an optional embodiment, the memory 1732 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices 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, optical disc storage (including compressed optical disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a disk or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory 1732 may exist independently and be connected to the processor 1731 via a communication bus. The memory 1732 may also be integrated with the processor 1731.

[0187] The memory 1732 is used to store program codes, and the processor 1731 controls the execution to execute some or all steps of the message forwarding method provided in the above embodiment. The processor 1731 is used to execute the program codes stored in the memory 1732. The program codes may include one or more software modules. The one or more software modules may be the above Fig.15 or Fig.16 The memory 1714 can also be used to store program codes, and the central processor 1712 controls the execution to execute part or all of the steps of the message forwarding method provided in the above embodiment.

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

[0189] The 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 a first network domain and a second network domain, the second network node is located at the entrance of the first network domain, and the first network node includes Fig.15 or Fig.17 The message forwarding device shown in the figure, the second network node includes Fig.16 or Fig.17 The message forwarding device shown.

[0190] In one example, the message forwarding system is as follows: Figure 2 As shown, 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.

[0191] In another example, the message forwarding system is as follows: Figure 3 As shown, 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.

[0192] In another example, the message forwarding system is as follows: 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.

[0193] 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, executed by a network node, one or more processors, etc.), all or part of the steps of the method provided in the above method embodiment are implemented.

[0194] 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, executed 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.

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

[0196] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product, and the computer program product 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 may be a general-purpose computer, a computer network, or other programmable device. The computer instructions may 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 may be transmitted from a website site, a computer, a server or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server, a data center, etc. that contains one or more available media integrated. The available medium may 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), etc.

[0197] It should be understood that the term "at least one" in this application refers to one or more, and "multiple" 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 may represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, in order to facilitate clear description, in this application, the words "first", "second", "third" and the like are used to distinguish between identical or similar items with substantially the same functions and effects. Those skilled in the art will understand that the words "first", "second", "third" and the like do not limit the quantity and execution order.

[0198] The different types of embodiments such as the method embodiments and device embodiments provided in the embodiments of the present application can refer to each other, and the embodiments of the present application are not limited thereto. The sequence of operations of the method embodiments provided in the embodiments of the present application can be appropriately adjusted, and the operations can also be increased or decreased in response to the situation. Any technician familiar with the technical field can easily think of the changed methods within the technical scope disclosed in the present application, and they should be included in the protection scope of the present application, so they will not be repeated.

[0199] In the corresponding embodiments provided in the present application, it should be understood that the disclosed devices and the like can be implemented by other configuration methods. For example, the device embodiments described above are only illustrative, for example, the division of modules is only a logical function division, and there may be other division methods in actual implementation, for example, multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed.

[0200] The modules described as separate components may or may not be physically separated, and the components described as modules may or may not be physical modules, and may be located in one place or distributed on multiple devices. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0201] The above is only an exemplary embodiment of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope 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 to: 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 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.

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

Cited By

  • Network slicing implementation method based on VxLAN (Virtual Extensible Local Area Network)

    CN117424819A

  • A method for implementing network slicing based on VxLAN

    CN117424819B

  • Message forwarding method, apparatus and system

    EP4701140A1

  • Message forwarding method, apparatus and system

    WO2024239721A1