[go: up one dir, main page]

WO2022166465A1 - 一种报文处理方法及相关装置 - Google Patents

一种报文处理方法及相关装置 Download PDF

Info

Publication number
WO2022166465A1
WO2022166465A1 PCT/CN2021/141540 CN2021141540W WO2022166465A1 WO 2022166465 A1 WO2022166465 A1 WO 2022166465A1 CN 2021141540 W CN2021141540 W CN 2021141540W WO 2022166465 A1 WO2022166465 A1 WO 2022166465A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
identifier
slice
packet
network device
Prior art date
Application number
PCT/CN2021/141540
Other languages
English (en)
French (fr)
Inventor
李振斌
董杰
韩涛
杨平安
胡志波
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP21924458.9A priority Critical patent/EP4270897A4/en
Priority to KR1020237027873A priority patent/KR20230128564A/ko
Priority to JP2023546511A priority patent/JP2024504845A/ja
Publication of WO2022166465A1 publication Critical patent/WO2022166465A1/zh
Priority to US18/228,503 priority patent/US20230412508A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/76—Routing in software-defined topologies, e.g. routing between virtual machines
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/82—Miscellaneous aspects
    • H04L47/829—Topology based
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22—Parsing or analysis of headers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • H04L45/036—Updating the topology between route computation elements, e.g. between OpenFlow controllers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/302—Route determination based on requested QoS
    • H04L45/306—Route determination based on the nature of the carried application
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/302—Route determination based on requested QoS
    • H04L45/308—Route determination based on user's profile, e.g. premium users
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/34—Source routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/74—Address processing for routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/72—Admission control; Resource allocation using reservation actions during connection setup
    • H04L47/724—Admission control; Resource allocation using reservation actions during connection setup at intermediate nodes, e.g. resource reservation protocol [RSVP]

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a message processing method and related apparatus.
  • Network slicing is a form of virtualization that allows multiple logical networks to run on top of a shared physical network infrastructure. That is to say, based on a shared physical network, corresponding network slices (or virtual networks) are cut out through virtualization technology to meet the differentiated needs of users. Each virtual network slice is logically resource isolated, independent of each other, and does not affect each other.
  • the solution for implementing packet forwarding based on network slices in the bearer network is as follows: the controller uniformly assigns a slice identifier to each network slice; the packets received by the network device carry the slice identifier, and the network device determines the slice identifier according to the slice identifier. network slice, and use the resource corresponding to the determined network slice to forward the packet.
  • the current slice identifier is a global identifier, which requires all devices in the network to consistently understand the meaning of the slice identifier, and use the resources indicated by the slice identifier to forward packets.
  • the slice capabilities supported by different devices in the network may be different, and the number of slices supported by different devices may also be different. It is difficult to ensure that all devices can use the same slice ID to perform corresponding packet forwarding behaviors.
  • the present application provides a packet processing method.
  • the packet carries a slice identifier including a plurality of sub identifiers, and different sub identifiers indicate different attributes of network slices, ensuring that devices with different slice capabilities can also use the slice identifiers as indicated by the slice identifiers. properties of the network slice to perform the corresponding packet forwarding behavior.
  • a first aspect of the present application provides a packet processing method.
  • the method includes: a first network device obtains a first packet, where the first packet includes a first slice identifier.
  • the first slice identifier is used to identify the first network slice to which the first packet belongs.
  • the first slice identifier includes a plurality of consecutive sub-identities, and each sub-identity may be represented by a field, so the first slice identifier may be represented by a plurality of consecutive fields.
  • the multiple sub-identities in the first slice identifier are respectively used to represent different attributes of the first network slice, such as attributes such as topology, path calculation algorithm, or forwarding resources of the first network slice.
  • the first network device forwards the first packet according to the first slice identifier in the first packet. Specifically, the first network device can determine the first network slice to which the first packet belongs based on the first slice identifier in the first packet. Therefore, the first network device can forward the first packet based on the resource corresponding to the first network slice.
  • the multiple sub-identities include topology identifiers and resource identifiers.
  • the topology identifier is used to represent the topology of the first network slice, that is, the topology to which the first network slice belongs in the network domain.
  • the resource identifier is used to represent the forwarding resource of the first network slice.
  • the forwarding resources of the first network slice include, for example, a physical interface, a logical sub-interface, and/or a packet queue.
  • the slice identifier in the packet that is forwarded in the network domain may include a topology identifier and a resource identifier.
  • the network device determines the topology of the network slice through the topology identifier, and further determines the forwarding resource corresponding to the network slice based on the resource identifier.
  • network slices with different topologies and different forwarding resources can use the same destination IP address, MPLS label or SID to identify the same destination IP address, MPLS label or SID.
  • by carrying the topology identifier and the resource identifier separately it is possible to use forwarding entries of the same topology to perform forwarding processing on multiple slices with the same topology, reducing the impact of slices on the increase in the number of forwarding entries.
  • the plurality of sub-identities further include an algorithm identification, where the algorithm identification is used to indicate a path calculation algorithm of the first network slice. That is, the first slice identifier includes a topology identifier, an algorithm identifier, and a resource identifier.
  • the first network device first determines the purpose of the first packet according to the information (for example, the above-mentioned destination address, MPLS label, or SID) used to indicate the forwarding path in the first packet.
  • the information for example, the above-mentioned destination address, MPLS label, or SID
  • the first network device determines the topology used to go to the destination node according to the topology identifier in the first message, and determines the route calculation algorithm used to go to the destination node based on the algorithm identifier in the first message, so as to obtain the the interface for forwarding the packet; finally, the first network device determines the corresponding forwarding resource (eg, logical sub-interface or queue) on the interface according to the resource identifier in the first packet, thereby implementing the forwarding of the first packet.
  • the corresponding forwarding resource eg, logical sub-interface or queue
  • the same information can be used to identify the same destination node in network slices with different topologies, using different algorithms, and having different resources, avoiding the need for Slicing plans a larger number of destination node information.
  • forwarding entries with the same topology or the same algorithm can be used to forward multiple slices with the same topology or algorithm, reducing the impact of slices on the increase in the number of forwarding entries. .
  • the multiple sub-identities include an algorithm identification and a resource identification
  • the algorithm identification is used to indicate the path calculation algorithm of the first network slice
  • the resource identification is used to indicate the forwarding resource of the first network slice.
  • the first network device first determines the first packet according to the information (for example, the above-mentioned destination address, MPLS label or SID) used to indicate the forwarding path in the first packet. the destination node of the message; then, the first network device determines the route calculation algorithm used to reach the destination node according to the algorithm identifier in the first packet, so as to obtain the interface corresponding to the forwarding path obtained when the route calculation algorithm is adopted; finally, The first network device determines a corresponding forwarding resource (for example, a logical sub-interface or a queue) on the interface according to the resource identifier in the first packet, thereby implementing forwarding of the first packet.
  • the information for example, the above-mentioned destination address, MPLS label or SID
  • network slices with different topologies and different forwarding resources can use the same information to identify the same destination node, avoiding the need for Slicing plans a larger number of destination node information.
  • forwarding entries with the same algorithm can be used to forward multiple slices with the same path calculation algorithm, reducing the impact of slices on the increase in the number of forwarding entries.
  • the multiple sub-identities further include a domain identifier, and the domain identifier is used to indicate a network domain in which the first slice identifier is valid.
  • the multiple sub-identities include domain identification, topology identification, and resource identification; or, the multiple sub-identifications include domain identification, algorithm identification, and resource identification; or, the multiple sub-identifications include domain identification, topology identification, algorithm identification Identity and resource identity.
  • the multiple sub-identities include a domain identifier and a resource identifier
  • the domain identifier is used to indicate the network domain in which the first slice identifier is valid
  • the resource identifier is used to indicate the forwarding of the first network slice.
  • resource is used to represent the network domain in which the first slice identifier is valid
  • the resource identifier is used to represent the forwarding resources of the first network slice.
  • the combination of sub-identifications including domain identification and resource identification in the slice identification may be applicable to network slice scenarios spanning multiple network domains.
  • network slices in each network domain can use different domain IDs and resource IDs.
  • Network slices of multiple network domains are spliced to form cross-domain network slices.
  • the forwarding resources include physical interfaces, logical sub-interfaces and/or packet queues.
  • the first network device forwarding the first packet according to the first slice identifier includes: the first network device, according to the sub-identity and the mapping table in the first slice identifier, determining an interface for forwarding the first packet and a forwarding resource of the interface; the first network device forwards the first packet to a second network device according to the forwarding resource of the interface; wherein the The mapping table includes the mapping relationship between the plurality of sub-identities and interfaces.
  • the mapping table may be a mapping relationship including multiple sub-identities and interfaces and forwarding resources of the interface at the same time, and the mapping table may also include multiple sub-mapping tables, and the multiple sub-mapping tables respectively include each sub-identity and interface. mapping relationship between them.
  • the plurality of sub-identities further include flag identifiers.
  • the first slice identifier in addition to the topology identifier and the resource identifier, also includes a flag bit identifier.
  • the first slice identifier includes a domain identifier, a topology identifier, an algorithm identifier, and a resource identifier, and the first slice identifier also includes a flag bit identifier.
  • the flag bit identifier is used to indicate a sub-identity in the first slice identifier used to direct forwarding and a forwarding policy corresponding to the first slice identifier.
  • the sub-identity used to guide forwarding refers to the sub-identity selected by the network device to guide the forwarding of the packet in the first slice identifier.
  • the sub-identities used to direct forwarding may be one or more sub-identities other than the flag bit identification in the first slice identification.
  • the sub-identities used to direct forwarding may be a topology identifier and an algorithm identifier;
  • the sub-identities can be topology identification, algorithm identification and resource identification.
  • the flag bit identifier is used to indicate which sub-identifiers in the slice identifier need to be used by the network device to perform packet forwarding.
  • the forwarding policy represented by the flag bit identifier is used to indicate the forwarding behavior after the interface is determined according to the sub-identity used to direct forwarding.
  • the forwarding behavior may refer to: if the first network device cannot find the interface for forwarding according to the first slice identifier, the first network device may not determine the interface for forwarding according to the first slice identifier, The first network device may forward the packet based on a default slice; or, if the first network device cannot find an interface for forwarding according to the first slice identifier, the first network device discards the first packet.
  • the network device can perform packet forwarding based on different strategies, thereby satisfying the diversification in the packet forwarding process. business requirements.
  • the method further includes: receiving, by the first network device, a second packet, where the second packet includes a second slice identifier;
  • the second slice identifier is updated to the first slice identifier to obtain the first packet.
  • the second slice identifier is valid in the second network domain, and the first slice identifier is valid in the first network domain where the first network device is located.
  • the first slice identifier is used to indicate the first network slice in the first network domain
  • the second slice identifier is used to indicate the second network slice in the second network domain
  • the second slice identifier is used to indicate the second network slice in the second network domain.
  • the Service-Level Agreement (SLA) of one network slice is the same as the SLA of the second network slice. That is, the network quality of the first network slice is the same as the network quality of the second network slice.
  • SLA Service-Level Agreement
  • the first network device is a border node in the bearer network, and the first network device receives a packet sent by a network device in a network other than the bearer network, and the packet carries a slice identifier of the entire network.
  • the first network device can receive the second packet sent by the network device in the access network or the core network.
  • the packet carries the second slice identifier, and the second slice identifier is valid in the entire network, that is, the first slice identifier is valid in the entire network.
  • the two-slice identifier is valid in the access network, bearer network, and core network.
  • the second slice identifier is a single network slice selection support information (Single Network Slice Selection Assistance Information, S-NSSAI) or an application-aware network (Application-Aware Networking, APN) identifier.
  • S-NSSAI Single Network Slice Selection Assistance Information
  • APN Application-Aware Networking
  • the first network device is a border node in the bearer network
  • the second packet obtained by the first network device carries a second slice identifier that is valid in the bearer network including multiple network domains.
  • the second slice identifier can indicate the network slice to which the second packet belongs in multiple network domains of the entire bearer network.
  • the format of the second slice identifier may be the same as that of the first slice identifier, and the format of the second slice identifier may also be different from that of the first slice identifier. In this way, the first network device can convert the second slice identifier valid in multiple network domains into the first slice identifier valid in the network domain where the first network device is located.
  • the first network device may be a network domain located in the bearer network, and the first network device receives packets sent by network devices outside the network domain. Specifically, the first network device receives the third packet, and determines the network slice to which the third packet belongs. The third packet comes from a network device outside the network domain to which the first network device belongs. The first network device then adds the first slice identifier to the third packet according to the network slice to which the third packet belongs to obtain the first packet.
  • the determining, by the first network device, the network slice to which the third packet belongs includes: the first network device determining, according to information in the third packet, the network slice to which the third packet belongs.
  • Network slice wherein, the information in the third packet includes one or more of the following information: source address, destination address, protocol number, Differentiated Services Code Point (Differentiated Services Code Point, DSCP) field, traffic level ( Traffic Class) field, Virtual Local Area Network identifier (VLAN ID), and port number.
  • DSCP Differentiated Services Code Point
  • Traffic Class Traffic Class
  • VLAN ID Virtual Local Area Network identifier
  • the first network device adding the first slice identifier to the third packet according to the network slice to which the third packet belongs including: the first network device according to the The network slice to which the third packet belongs, the first slice identifier and the fourth slice identifier are added to the third packet to obtain the first packet; the fourth slice identifier is used to The bearer network of each network domain identifies the network slice to which the third packet belongs.
  • the determining, by the first network device, the network slice to which the third packet belongs includes: determining, by the first network device, the third packet according to a third slice identifier in the third packet.
  • the third slice identifier in the third packet is a global identifier in the bearer network and takes effect in multiple network domains of the entire bearer network, that is, the third slice identifier can identify the third packet in the bearer network.
  • the first network device may determine the network slice to which the third packet belongs based on the third slice identifier, so as to obtain the first slice identifier valid in the network domain where the first network device is located. Then, the first network device adds the first slice identifier to the third packet to obtain the first packet, where the first packet includes both the third slice identifier and the first slice identifier.
  • the first network device When the third packet received by the first network device only includes the third slice identifier, the first network device adds the first slice identifier on the basis of the third slice identifier, so that the obtained first packet includes Two slice identifiers, the third slice identifier and the first slice identifier.
  • the first network device determines the first slice identifier according to the third slice identifier, and replaces another slice identifier in the third packet with the first slice identifier, so that the obtained first packet includes the third slice identifier and the first slice identifier.
  • Slice ID These two slice IDs.
  • a second aspect of the present application provides a network device, including a transceiver unit and a processing unit.
  • the transceiver unit is configured to acquire a first packet, where the first packet includes a first slice identifier, and the first slice identifier includes multiple consecutive sub-identities, and the multiple sub-identities are used to represent the first Different attributes of network slices, the first slice identifier is used to identify the first network slice to which the first packet belongs; the transceiver unit is further configured to forward the first network slice according to the first slice identifier message.
  • the multiple sub-identities include a topology identifier and a resource identifier, where the topology identifier is used to represent the topology of the first network slice, and the resource identifier is used to represent forwarding resources of the first network slice.
  • the plurality of sub-identities further include an algorithm identification, where the algorithm identification is used to indicate a path calculation algorithm of the first network slice.
  • the multiple sub-identities include an algorithm identification and a resource identification
  • the algorithm identification is used to indicate the path calculation algorithm of the first network slice
  • the resource identification is used to indicate the forwarding resource of the first network slice.
  • the multiple sub-identities further include a domain identifier, where the domain identifier is used to indicate a network domain in which the first slice identifier is valid.
  • the multiple sub-identities include a domain identifier and a resource identifier, the domain identifier is used to indicate the network domain in which the first slice identifier is valid, and the resource identifier is used to indicate the forwarding of the first network slice. resource.
  • the forwarding resources include physical interfaces, logical sub-interfaces and/or packet queues.
  • the processing unit is configured to determine an interface for forwarding the first packet and a forwarding resource of the interface according to the sub-identity in the first slice identifier and the mapping table; the forwarding The unit is further configured to forward the first packet to the second network device according to the forwarding resource of the interface; wherein the mapping table includes the mapping relationship between the multiple sub-identities and the interface.
  • the multiple sub-identities further include a flag bit identification, and the flag bit identification is used to indicate a forwarding strategy corresponding to the first slice identification, and the forwarding strategy is used to indicate that according to the sub-identity used for guiding forwarding Forwarding behavior after an interface is determined.
  • the forwarding behavior includes: if the interface for forwarding cannot be found according to the first slice identifier, the interface for forwarding is not determined according to the first slice identifier; or, if the interface for forwarding cannot be determined according to the first slice identifier; If the first slice identifier cannot find an interface for forwarding, the first packet is discarded.
  • the transceiver unit is further configured to receive a second packet, where the second packet includes a second slice identifier; the processing unit is further configured to update the second slice identifier to the first slice identifier The slice identifier is obtained, and the first packet is obtained.
  • the first slice identifier is used to indicate the first network slice in the first network domain
  • the second slice identifier is used to indicate the second network slice in the second network domain
  • the second slice identifier is used to indicate the second network slice in the second network domain.
  • the service level agreement SLA of one network slice is the same as the SLA of the second network slice.
  • the first network device is a border node of a bearer network
  • the second slice identifier is a single network slice selection support information S-NSSAI or an application aware network APN identifier.
  • the transceiver unit is further configured to receive a third packet; the processing unit is further configured to determine the network slice to which the third packet belongs; the processing unit is further configured to determine the network slice to which the third packet belongs; For the network slice to which it belongs, add the first slice identifier to the third packet to obtain the first packet.
  • the processing unit is further configured to determine, according to the information in the third packet, the network slice to which the third packet belongs; wherein the information in the third packet includes one of the following information: One or more of: source address, destination address, protocol number, Differentiated Services Code Point DSCP field, traffic class TC field, VLAN ID and port number.
  • the processing unit is further configured to add the first slice identifier and the fourth slice identifier to the third packet according to the network slice to which the third packet belongs, to obtain the first slice. packet; the fourth slice identifier is used to identify the network slice to which the third packet belongs in a bearer network including multiple network domains.
  • the processing unit is further configured to determine, according to the third slice identifier in the third packet, the network slice to which the third packet belongs; wherein the third slice identifier is used to include multiple slices.
  • the bearer network of each network domain identifies the network slice to which the third packet belongs.
  • a third aspect of the present application provides a network device, where the network device includes: a processor, configured to enable the network device to implement the method described in any possible implementation manner of the foregoing first aspect.
  • the device may further include a memory, the memory is coupled to the processor, and when the processor executes the instructions stored in the memory, the network device can implement the method described in any possible implementation manner of the foregoing first aspect.
  • the device may also include a communication interface for the apparatus to communicate with other devices, for example, the communication interface may be a transceiver, circuit, bus, module or other type of communication interface.
  • the instructions in the memory may be stored in advance, or may be downloaded from the Internet and stored after using the network device.
  • This application does not specifically limit the source of the instructions in the memory.
  • the coupling in this application is an indirect coupling or connection between devices, units or modules, which may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules.
  • a fourth aspect of the present application provides a network system, where the network system includes multiple network devices, and the multiple network devices include the network device described in the foregoing third aspect.
  • the network device acquires the message, the network device can implement the method described in any possible implementation manner of the foregoing first aspect.
  • a fifth aspect of the present application provides a computer storage medium, where the computer storage medium may be non-volatile; computer-readable instructions are stored in the computer storage medium, and when the computer-readable instructions are executed by a processor, the first aspect is implemented The method described in any of the possible implementations of .
  • a sixth aspect of the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform a method as described in any possible implementation of the first aspect.
  • FIG. 1 is a schematic structural diagram of a network according to an embodiment of the present application.
  • FIG. 2 is a schematic flowchart of a packet processing method 200 provided by an embodiment of the present application.
  • 3a is a schematic structural diagram of a slice identifier provided by an embodiment of the present application.
  • 3b is a schematic structural diagram of another slice identifier provided by an embodiment of the present application.
  • FIG. 3c is a schematic diagram of forwarding a message according to an embodiment of the present application.
  • FIG. 4a is a schematic structural diagram of a slice identifier provided by an embodiment of the present application.
  • FIG. 4b is a schematic diagram of another packet forwarding provided by an embodiment of the present application.
  • FIG. 5a is a schematic structural diagram of a slice identifier provided by an embodiment of the present application.
  • FIG. 5b is a schematic diagram of another packet forwarding provided by an embodiment of the present application.
  • 5c is a schematic diagram of a network device forwarding a packet based on a slice identifier according to an embodiment of the present application
  • FIG. 6 is a schematic structural diagram of another slice identifier provided by an embodiment of the present application.
  • FIG. 7 is another schematic structural diagram of a first slice identifier provided in an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a first slice identifier provided by an embodiment of the present application.
  • FIG. 9a is a schematic diagram of division of a network domain according to an embodiment of the present application.
  • FIG. 9b is a schematic diagram of another network domain division provided by an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a network device 1000 according to an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of a network device 1100 provided by an embodiment of the application.
  • FIG. 12 provides a schematic structural diagram of a network system 1200 according to an embodiment of the present application.
  • the naming or numbering of the steps in this application does not mean that the steps in the method flow must be executed in the time/logical sequence indicated by the naming or numbering, and the named or numbered process steps can be implemented according to the The technical purpose is to change the execution order, as long as the same or similar technical effects can be achieved.
  • the division of units in this application is a logical division. In practical applications, there may be other division methods. For example, multiple units may be combined or integrated into another system, or some features may be ignored. , or not implemented, in addition, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, and the indirect coupling or communication connection between units may be electrical or other similar forms. There are no restrictions in the application.
  • units or sub-units described as separate components may or may not be physically separated, may or may not be physical units, or may be distributed into multiple circuit units, and some or all of them may be selected according to actual needs. unit to achieve the purpose of the scheme of this application.
  • enhanced mobile broadband enhanced mobile broadband
  • eMBB enhanced mobile broadband
  • massive machine type communication mMTC
  • uRLLC ultra-reliable and low latency communications
  • Network slicing refers to the logical network customized according to different business requirements on the physical or virtual network infrastructure.
  • Network slicing can be a complete end-to-end network including an access network, a bearer network, a core network, and an application server, which can provide complete communication services and have certain network capabilities.
  • Network slicing can also be any combination of access network, bearer network, core network and application server.
  • a network slice can often be thought of as an instantiated 5G network.
  • Such a network structure allows operators to provide the network as a service to users, and can freely combine physical networks according to indicators such as rate, capacity, coverage, delay, reliability, security, and availability to meet the needs of different users. Require.
  • a solution for implementing packet forwarding based on network slices in a bearer network is as follows: the controller uniformly assigns a slice identifier to each network slice.
  • the packet received by the network device carries a slice identifier, and the slice identifier and other fields in the packet indicating the destination address or path determine the forwarding behavior of the packet.
  • a network device forwards a packet, it determines the packet according to the destination address field, Multi-Protocol Label Switching (MPLS) label stack or Segment Routing header (SRH) and other information in the packet. Interface.
  • MPLS Multi-Protocol Label Switching
  • SSH Segment Routing header
  • the current slice identifier is a global identifier, which requires all devices in the network to consistently understand the meaning of the slice identifier, and use the resources indicated by the slice identifier to forward packets.
  • the slice capabilities supported by different devices in the network may be different, and the number of slices supported by different devices may also be different. It is difficult to ensure that all devices can use the same slice ID to perform corresponding packet forwarding behaviors.
  • the same forwarding action can be performed for a group of network slices, that is, packets are forwarded based on the same interface.
  • the network device cannot obtain common features between slices based on the slice identifiers.
  • the network device also needs to combine other identifiers in the packet, such as the destination IP address field, MPLS label or segment identifier (segment ID, SID) shared by the same group of slices to guide the forwarding of slices.
  • IP addresses, MPLS labels or SIDs to be planned and allocated based on some attributes of the slice, such as assigning different IP addresses, MPLS labels or SIDs to identify different topologies or algorithms, thus increasing the planning difficulty and quantity of IP addresses or labels .
  • an embodiment of the present application provides a packet processing method, by carrying a slice identifier including a plurality of sub identifiers in a packet, and different sub identifiers indicate different attributes of network slices, ensuring devices with different slice capabilities. Corresponding packet forwarding behavior can also be performed according to the attributes of the network slice indicated by the slice identifier.
  • FIG. 1 is a schematic structural diagram of a network according to an embodiment of the present application.
  • the network shown in FIG. 1 includes a network device 1 - a network device 8 .
  • the network device 1 is the head node in the network
  • the network device 2 - the network device 7 are the intermediate nodes in the network
  • the network device 8 is the tail node in the network.
  • the network device 1 encapsulates a slice identifier including a plurality of consecutive sub-IDs in the message, and sends the message to the intermediate node in the network domain.
  • the intermediate node in the network domain forwards the message according to the slice identifier in the message, so as to realize forwarding the message to the network device 8 serving as the tail node.
  • the network device 8 forwards the packet to other network domains according to the slice identifier in the packet.
  • FIG. 2 is a schematic flowchart of a packet processing method 200 provided by an embodiment of the present application.
  • the packet processing method 200 can be applied to the network structure shown in FIG. 1 .
  • the packet processing method 200 at least includes the following steps.
  • Step 201 the first network device obtains a first packet, the first packet includes a first slice identifier, the first slice identifier includes multiple consecutive sub-identities, and the multiple sub-identities are used to represent different attributes of the first network slice, The first slice identifier is used to identify the first network slice to which the first packet belongs.
  • the first network device is a network in a bearer network.
  • the first network device may be a network device in an MPLS network, an Internet Protocol version 4 (Internet Protocol version 4, IPv4) network, or an Internet Protocol version 6 (Internet Protocol version 6, IPv6) network.
  • the first network device may be, for example, a physical device such as a router, a switch, or a gateway, or a virtual device that supports packet forwarding. This embodiment does not limit the specific type of the first network device.
  • the manner in which the first network device obtains the first packet may be by receiving the first packet sent by other network devices, for example, receiving a data packet sent by a network device located outside the MPLS network, or by generating the first packet by itself, Or the first packet is received from a network device on the access network side.
  • the first packet includes a first slice identifier for identifying the first network slice to which the first packet belongs.
  • the first slice identifier includes a plurality of consecutive sub-identities, and each sub-identity may be represented by a field, so the first slice identifier may be represented by a plurality of consecutive fields.
  • the multiple sub-identities in the first slice identifier are respectively used to represent different attributes of the first network slice, such as attributes such as the topology of the first network slice, a path calculation algorithm, or a forwarding resource.
  • the first slice identifier may be carried in different positions in different types of data packets, and this embodiment does not specifically limit the carrying manner of the first slice identifier.
  • the first packet may be an IPv6 data packet.
  • the first slice identifier may be carried in some fields of the fixed packet header of the IPv6 data packet, for example, the flow label (Flow label) field, the source address field or the destination address field of the fixed packet header.
  • the first slice identifier can also be carried in the extension header of the IPv6 data message, and the extension header of the IPv6 data message can be, for example, a hop by hop (HBH) header, a routing extension header or Purpose extension header.
  • HBV hop by hop
  • the first packet may be an MPLS data packet.
  • the first slice identifier may be carried in the MPLS label stack of the MPLS packet header of the MPLS data packet.
  • the first slice identifier may also be carried in a control word field or an extension header located after the MPLS packet header.
  • the extension header in the MPLS data packet is located between the MPLS label and the payload.
  • Step 202 the first network device forwards the first packet according to the first slice identifier.
  • the first network device can determine the first network slice to which the first packet belongs based on the first slice identifier in the first packet. Therefore, the first network device can forward the first packet based on the resource corresponding to the first network slice.
  • different sub identifiers indicate different attributes of the network slice, ensuring that devices with different slice capabilities can also use the slice identifier to indicate the network slice. attribute to perform the corresponding packet forwarding behavior.
  • Scenario 1 The multiple sub-identities in the first slice identifier include topology identifiers and resource identifiers.
  • FIG. 3a is a schematic structural diagram of a slice identification provided by an embodiment of the present application.
  • the first slice identifier includes a topology identifier and a resource identifier.
  • the topology identifier is used to indicate the topology of the first network slice, that is, the topology to which the first network slice belongs in the network domain.
  • the resource identifier is used to represent the forwarding resource of the first network slice.
  • the forwarding resources of the first network slice include, for example, a physical interface, a logical sub-interface, and/or a packet queue.
  • the resource identifier may include multiple levels of sub-identities, and sub-identities of different levels represent different forwarding resources. More fine-grained forwarding resources can be indicated based on the multi-level sub-identification in the resource identifier.
  • FIG. 3b is a schematic structural diagram of another slice identifier provided by an embodiment of the present application.
  • the resource identifier in the first slice identifier may include a primary resource identifier and a secondary resource identifier, and the primary resource identifier and the secondary resource identifier represent different forwarding resources.
  • the resource indicated by the primary resource identifier is the logical sub-interface corresponding to the interface
  • the resource indicated by the secondary resource identifier is the queue resource corresponding to the logical sub-interface; in this way, based on the primary resource identifier and the secondary resource identifier, the first The network device can determine specific forwarding resources on the interface for forwarding the first packet.
  • the network domain where the first network device is located may be a topology that uses a multi-topology (Multi-topology) technology to divide network slices in the network domain.
  • Multi-topology multi-topology
  • Different network slices in the network domain can correspond to different topologies; different network slices in the network domain can also correspond to the same topology, but the forwarding resources allocated to different network slices on the network device are different. Forwarding resources allocated for different network slices are distinguished based on resource identifiers.
  • the slice identifier in the packet that is forwarded in the network domain may include a topology identifier and a resource identifier.
  • the network device determines the topology of the network slice through the topology identifier, and further determines the forwarding resource corresponding to the network slice based on the resource identifier.
  • the process of forwarding the first packet by the first network device based on the first slice identifier is as follows: the first network device first The destination node of the first packet is determined according to the information used to indicate the forwarding path, such as the destination address, MPLS label, or segment ID (SID) in the first packet; then, the first network device determines the destination node of the first packet according to the information in the first packet The topology identifier determines the topology used to go to the destination node, so as to obtain the interface to the destination node under this topology; finally, the first network device determines to use the corresponding forwarding resource (for example, logical) on the interface according to the resource identifier in the first message. sub-interface or queue) to forward the first packet.
  • the corresponding forwarding resource for example, logical
  • a mapping table for guiding packet forwarding may be preset in the first network device, and the mapping table may be delivered by the controller or manually configured, for example.
  • the mapping table of the first network device includes mapping relationships between multiple sub-identities in the first slice identifier and interfaces.
  • the first network device first determines one or more interfaces to the destination node of the first packet according to information such as the destination address, MPLS label, or SID in the first packet. Then, the first network device determines, according to the topology identifier, the resource identifier and the mapping table, an interface for forwarding the first packet and a forwarding resource corresponding to the interface in one or more interfaces to the destination node of the first packet. Finally, the first network device forwards the first packet to the second network device according to the determined interface and the forwarding resource corresponding to the interface.
  • the mapping table in the first network device may simultaneously include mapping relationships between multiple sub-identities and interfaces and forwarding resources of the interfaces. That is, the mapping table includes different sub-identity combinations, each sub-identity combination has a corresponding interface and forwarding resources of the interface, and different sub-identity combinations correspond to different interfaces or different forwarding resources. For example, topology ID 1 and resource ID 1 correspond to interface 1 and queue 1 on interface 1; topology ID 1 and resource ID 2 correspond to queue 2 on interface 1 and interface 1; topology ID 2 and resource ID 3 correspond to interfaces 2 and queue 3 on interface 2.
  • the first network device may determine, based on the multiple sub-identities in the first slice identifier and the mapping table, the interface in the mapping table that uniquely corresponds to the multiple sub-identities and the forwarding resources of the interface.
  • the mapping table in the first network device may also include multiple different sub-mapping tables, and the different sub-mapping tables include mapping relationships between different sub-identities and interfaces or forwarding resources.
  • the mapping table in the first network device includes sub-mapping table 1 and sub-mapping table 2, where sub-mapping table 1 includes a mapping relationship between topology identifiers and interfaces, and sub-mapping table 2 includes a mapping relationship between resource identifiers and forwarding resources.
  • the first network device may determine the interface based on the topology identifier and the sub-mapping table 1, and then determine the forwarding resource corresponding to the interface based on the resource identifier and the sub-mapping table 2.
  • FIG. 3c is a schematic diagram of packet forwarding provided by an embodiment of the present application.
  • the network structure shown in Fig. 1 is topologically divided by using the multi-topology technology, and the topology 1 and the topology 2 are obtained.
  • topology 1 includes network device 1, network device 2, network device 3, network device 4, and network device 8;
  • topology 2 includes network device 1, network device 5, network device 6, network device 7, and network device 8.
  • network device 1 obtains a packet, and the destination node of the packet is network device 8; and the topology identifier in the packet is used to represent topology 1, and the resource identifier in the packet is used to represent queue 1. Then, based on the destination node of the packet, the network device 1 can determine that the interfaces for forwarding the packet include the interface between the network device 1 and the network device 2 and the interface between the network device 1 and the network device 5 .
  • network device 1 determines to use topology 1 to forward the message based on the topology identifier in the message, thereby determining that the interface for forwarding the message is the interface between network device 1 and network device 2; further, the network Device 1 determines, based on the resource identifier in the packet, to finally use queue 1 corresponding to the interface between network device 1 and network device 2 to forward the packet.
  • network slices with different topologies and different forwarding resources can be identified by the same destination IP address, MPLS label or SID.
  • the same destination node avoids planning a larger number of IP addresses, MPLS labels or SIDs for slices.
  • by carrying the topology identifier and the resource identifier separately it is possible to use forwarding entries of the same topology to perform forwarding processing on multiple slices with the same topology, reducing the impact of slices on the increase in the number of forwarding entries.
  • Scenario 2 The multiple sub-identities in the first slice identifier include algorithm identifiers and resource identifiers.
  • FIG. 4a is a schematic structural diagram of a slice identification provided by an embodiment of the present application.
  • the first slice identifier includes an algorithm identifier and a resource identifier.
  • the algorithm identifier is used to indicate a path calculation algorithm of the first network slice, that is, an algorithm used by the first network slice to perform path calculation in the network domain.
  • the resource identifier is used to represent the forwarding resource of the first network slice.
  • the forwarding resources of the first network slice include, for example, a physical interface, a logical sub-interface, and/or a packet queue.
  • the resource identifier in the first slice identifier may also include multi-level sub-identities, and sub-identities at different levels represent different forwarding resources.
  • the specific manner in which the resource identifier includes multi-level sub-identities may refer to the above-mentioned embodiments, and details are not described herein again.
  • the network domain where the first network device is located may adopt a flexible algorithm (Flex-Algo) or other specific algorithms and other route calculation algorithms to define the route calculation constraints of the network slices in the network domain.
  • Different network slices in the network domain may use different path calculation algorithms to calculate paths.
  • Different network slices in the network domain can also use the same route calculation algorithm to calculate the route, but the forwarding resources allocated for different network slices on the network device are different, and the network device can be divided into different network slices based on resource identifiers Allocated forwarding resources.
  • the process of forwarding the first packet by the first network device based on the first slice identifier is as follows: the first network device first The destination node of the first packet is determined according to the information (for example, the above-mentioned destination address, MPLS label or SID) used to indicate the forwarding path in the first packet; then, the first network device determines the destination node according to the algorithm identifier in the first packet Go to the path calculation algorithm used by the destination node, so as to obtain the interface corresponding to the forwarding path obtained when the path calculation algorithm is adopted; finally, the first network device determines the corresponding forwarding resource on the interface according to the resource identifier in the first message ( For example, a logical sub-interface or a queue), so as to realize the forwarding of the first packet.
  • the resource identifier for example, a logical sub-interface or a queue
  • the first network device may forward the first packet based on the preset mapping table and the algorithm identifier and the resource identifier in the first packet.
  • the mapping table in the first network device may include both the algorithm identifier and the resource identifier and the interface and the mapping relationship between the forwarding resources of the interface, and the mapping table in the first network device may also include multiple sub-mapping tables.
  • the mapping table respectively includes a mapping relationship between algorithm identifiers and interfaces, and a mapping relationship between resource identifiers and forwarding resources.
  • FIG. 4b is a schematic diagram of another packet forwarding provided by this embodiment of the present application.
  • the network structure in FIG. 4b can use different path calculation algorithms to calculate the packet path.
  • network device 1 obtains the packet
  • the destination node of the packet is network device 8.
  • the calculated forwarding path of the packet is: network device 1 > network device 2 > network device 3 > network device 4 > network device 8.
  • the network device adopts Algorithm 2 to calculate the forwarding path of the packet the calculated forwarding path of the packet is: network device 1 > network device 5 > network device 6 > network device 7 > network device 8.
  • the packet obtained by the network device 1 includes an algorithm identifier and a resource identifier
  • the path calculation algorithm indicated by the algorithm identifier is algorithm 1
  • the forwarding resource indicated by the resource identifier is queue 2.
  • network device 1 determines that the interface forwarding the message is the interface between network device 1 and network device 2; further, network device 1 determines based on the resource identifier in the message
  • the queue 2 corresponding to the interface between the network device 1 and the network device 2 is used to forward the packet.
  • network slices with different topologies and different forwarding resources can use the same information to identify the same destination node, avoiding the need for Plan a larger number of destination node information for slices.
  • forwarding entries with the same algorithm can be used to forward multiple slices with the same path calculation algorithm, reducing the impact of slices on the increase in the number of forwarding entries.
  • the multiple sub-identities in the first slice identifier include topology identifiers, algorithm identifiers, and resource identifiers.
  • FIG. 5a is a schematic structural diagram of a slice identification provided by an embodiment of the present application.
  • the first slice identifier includes a topology identifier, an algorithm identifier and a resource identifier.
  • the algorithm identifier and the resource identifier reference may be made to the above-mentioned embodiments, which will not be repeated here.
  • the network domain where the first network device is located may be a topology in which a multi-topology (Multi-topology) technology is used to divide network slices in the network domain, and a flexible algorithm (Flex-Algo) or other specific algorithms, etc. is used.
  • the path calculation algorithm is used to define the path calculation constraints for network slices in the network domain.
  • the network domain where the first network device is located includes multiple topologies, and one or more path calculation algorithms may be used in each topology to perform path calculation.
  • Different network slices in the network domain where the first network device is located may correspond to different topologies, or different network slices may respectively use different path calculation algorithms to perform path calculation.
  • Different network slices in the network domain may also correspond to the same topology and path calculation algorithm, but the forwarding resources allocated to different network slices on the network device are different, and the network device can be differentiated into different network slices based on resource identifiers. Allocated forwarding resources.
  • the process of forwarding the first packet by the first network device based on the first slice identifier is as follows: first The network device first determines the destination node of the first packet according to the information used to indicate the forwarding path in the first packet (for example, the above-mentioned destination address, MPLS label, or SID); then, the first network device determines the destination node of the first packet according to the information in the first packet.
  • the information used to indicate the forwarding path in the first packet for example, the above-mentioned destination address, MPLS label, or SID
  • the topology identifier determines the topology used to go to the destination node, and determines the route calculation algorithm used to go to the destination node based on the algorithm identifier in the first message, so as to obtain an interface for forwarding the message;
  • the resource identifier in a packet determines the corresponding forwarding resource (for example, a logical sub-interface or a queue) on the interface, thereby implementing the forwarding of the first packet.
  • the first network device may forward the first packet based on a preset mapping table and a topology identifier, an algorithm identifier, and a resource identifier in the first packet.
  • the mapping table in the first network device may also include a topology identifier, an algorithm identifier, and a mapping relationship between resource identifiers and interfaces and forwarding resources of the interfaces, and the mapping table in the first network device may also include multiple sub-mapping tables,
  • the multiple sub-mapping tables respectively include a mapping relationship between topology identifiers and interfaces, a mapping relationship between algorithm identifiers and interfaces, and a mapping relationship between resource identifiers and forwarding resources.
  • FIG. 5b is a schematic diagram of another packet forwarding provided by an embodiment of the present application.
  • the network structure in FIG. 5b is divided into two different topologies (ie, topology 1 and topology 2), and different path calculation algorithms are used to calculate the path of the message.
  • topology 1 includes network device 1, network device 2, network device 3, network device 4, network device 6, network device 7 and network device 8
  • topology 2 includes network device 1, network device 3, network device 4, network device 8 5.
  • the network device 1 obtains the packet, and the destination node of the packet is the network device 8 .
  • the forwarding path of the packet calculated by the network device based on the topology identifier and the algorithm identifier is: network device 1 > network device 2 > network device 3>Network Device 4>Network Device 8.
  • the forwarding path of the packet calculated by the network device based on the topology identifier and the algorithm identifier is: network device 1 > network device 2 > network device 3>Network Device 6>Network Device 7>Network Device 8.
  • the forwarding path of the packet calculated by the network device based on the topology identifier and the algorithm identifier is: network device 1 > network device 5 > network device 6>Network Device 3>Network Device 4>Network Device 8.
  • the forwarding path of the packet calculated by the network device based on the topology identifier and the algorithm identifier is: network device 1 > network device 5 > network device 6>Network Device 7>Network Device 8.
  • Algorithm 1 and Algorithm 2 are different types of path calculation algorithms
  • Algorithm 3 and Algorithm 4 are also different types of path calculation algorithms.
  • Algorithm 1 and Algorithm 3 or Algorithm 4 may be different types of path calculation algorithms, or may be the same type of path calculation algorithms.
  • the packet obtained by network device 1 includes a topology identifier, an algorithm identifier, and a resource identifier, and the topology indicated by the topology identifier is topology 1, the path calculation algorithm indicated by the algorithm identifier is algorithm 1, and the forwarding resource indicated by the resource identifier for queue 2.
  • network device 1 determines that the interface forwarding the message is the interface between network device 1 and network device 2; further, network device 1 determines based on the The resource identifier is determined to finally use the queue 2 corresponding to the interface between the network device 1 and the network device 2 to forward the packet.
  • the same information can be used to identify the same destination node in network slices with different topologies, using different algorithms, and having different resources, avoiding the need for Plan a larger number of destination node information for slices.
  • forwarding entries with the same topology or the same algorithm can be used to forward multiple slices with the same topology or algorithm, reducing the impact of slices on the increase in the number of forwarding entries. .
  • different forwarding policies may be configured on different network devices in the same network domain, so that different network devices perform packet forwarding according to different sub-identities in the slice identifier.
  • the network device may perform packet forwarding based on all sub-identities in the slice identifier, or the network device may be based on some sub-identities in the slice identifier. to perform packet forwarding.
  • the network device may determine sub-identities in the slice identifier for guiding packet forwarding based on the configured forwarding policy, and then forward the packet according to these sub-identities for guiding packet forwarding.
  • FIG. 5c is a schematic diagram of a network device forwarding a packet based on a slice identifier according to an embodiment of the present application.
  • the network structure shown in FIG. 5c includes network device 1-network device 8, and the slice identifiers carried by the packets forwarded in the network structure include topology identifiers, algorithm identifiers, primary resource identifiers and secondary resource identifiers.
  • the granularity of the slices supported by the network device 1, the network device 2 and the network device 5 is relatively fine, and supports the allocation of fine-grained resources for different slices on the same node or link. Therefore, network device 1, network device 2, and network device 5 can forward packets using all sub-identities (ie, topology identification, algorithm identification, primary resource identification, and secondary resource identification) in the slice identification. Specifically, network device 1, network device 2, and network device 5 can determine the topology of the slice and the path calculation algorithm based on the topology identifier and the algorithm identifier, so as to use the corresponding path calculation algorithm to calculate the path in the specified topology, and obtain a path for forwarding. The interface of the packet; then, use the primary resource identifier and the secondary resource identifier to determine the resources allocated for the slice, and finally realize the forwarding of the packet.
  • sub-identities ie, topology identification, algorithm identification, primary resource identification, and secondary resource identification
  • network device 3 and network device 6 do not support allocating fine-grained resources to different slices on the same node or link. Therefore, the network device 3 and the network device 6 can use some of the sub-identities in the slice identification, that is, the topology identification and the algorithm identification, to forward the packet. Specifically, the network device 3 and the network device 6 can determine the topology of the slice and the path calculation algorithm based on the topology identifier and the algorithm identifier, so as to use the corresponding path calculation algorithm to perform path calculation in the specified topology, and obtain an interface for forwarding packets. , and forward packets based on this interface.
  • the network device 4, the network device 7 and the network device 8 support the allocation of fine-grained resources for different slices on the same node or link, but the granularity of resource allocation is relatively coarse. Therefore, the network device 4, the network device 7, and the network device 8 can use the topology identifier, algorithm identifier, and primary resource identifier in the slice identifier to forward the packet. Specifically, the network device 4, the network device 7, and the network device 8 can determine the topology and the path calculation algorithm of the slice based on the topology identifier and the algorithm identifier, so as to use the corresponding path calculation algorithm to calculate the path in the specified topology, and obtain a path for forwarding. The interface of the packet; then, use the first-level resource identifier to determine the resources allocated for the slice, and finally realize the forwarding of the packet.
  • network devices with different forwarding capabilities in the same network domain can forward packets based on the same slice identifier, which ensures normal packet forwarding .
  • Scenario 4 The multiple sub-identities in the first slice identifier include domain identifiers and resource identifiers.
  • FIG. 6 is a schematic structural diagram of another slice identifier provided by an embodiment of the present application.
  • the first slice identifier includes a domain identifier and a resource identifier.
  • the domain identifier is used to represent the network domain in which the first slice identifier is valid, and the resource identifier is used to represent the forwarding resources of the first network slice.
  • the domain identifier may be a global identifier, that is, the domain identifier indicates that the network domains in which the first slice identifier takes effect are all network domains in the bearer network.
  • the domain identifier may be a default value of 0, and the default value is used to indicate that the network domains in which the slice identifier is valid are all network domains in the bearer network.
  • the resource identifier may be a globally valid resource identifier, that is, network devices in all network domains in the bearer network can be based on This resource identifier is used to forward packets.
  • the domain identifier may be an area identifier, that is, the domain identifier indicates that the network domain where the first slice identifier is valid is a part of the network domain in the bearer network. For example, when the value of the domain identifier is 1, the domain identifier indicates that the network domain where the first slice identifier takes effect is the first network domain in the bearer network; when the value of the domain identifier is 2, the domain identifier represents the first slice identifier The effective network domain is the second network domain in the bearer network.
  • the resource identifier may be a resource identifier valid for a specific area, that is, the resource identifier is valid only in the network domain indicated by the domain identifier. .
  • the combination of sub-identifications including domain identification and resource identification in the slice identification may be applicable to network slice scenarios spanning multiple network domains.
  • network slices in each network domain can use different domain IDs and resource IDs.
  • Network slices of multiple network domains are spliced to form cross-domain network slices.
  • the process of forwarding the packet by the network device based on the slice identifier is specifically as follows.
  • a network device located at the boundary of a network domain receives a packet, and the packet may include a domain identifier and a resource identifier.
  • the network device determines the valid domain ID and resource ID in the current network domain according to the locally maintained mapping relationship and the domain ID in the message, and updates the slice ID in the message, or adds the valid slice ID in the current network domain to the message.
  • the network device determines the destination node of the packet according to information indicating the path such as the destination IP address, MPLS label or SID in the packet, and determines the interface to the destination node according to the default topology and default algorithm.
  • the network device determines to use the corresponding forwarding resource on the interface to forward the packet according to the resource identifier.
  • the network device inside the network domain receives the packet including the domain ID and resource ID
  • the network device determines the destination node of the packet according to the information indicating the path, such as the destination IP address, MPLS label or SID in the packet, and determines the destination node according to the missing information.
  • the provincial topology and default algorithm determine the interface to the destination node.
  • the network device determines to use the corresponding forwarding resource on the interface to forward the packet according to the resource identifier.
  • the multiple sub-identities in the first slice identifier include a domain identifier and a resource identifier, and the multiple sub-identities further include one or more of a topology identifier and an algorithm identifier.
  • the multiple sub-identifications in the first slice identification have various combinations.
  • FIG. 7 is another schematic structural diagram of the first slice identifier provided in this embodiment of the present application.
  • the multiple sub-identities in the first slice identifier include a domain identifier, a topology identifier, and a resource identifier.
  • the multiple sub-identities in the first slice identifier include a domain identifier, an algorithm identifier, and a resource identifier.
  • the multiple sub-identities in the first slice identifier include a domain identifier, a topology identifier, an algorithm identifier, and a resource identifier.
  • the various sub-identity combinations shown in FIG. 7 may be applicable to network slicing scenarios spanning multiple network domains.
  • network slices in each network domain may use different domain identifiers, and the topology identifiers, algorithm identifiers, and resource identifiers corresponding to each network slice may also be different.
  • Network slices of multiple network domains are spliced to form cross-domain network slices.
  • Scenario 6 On the basis of Scenario 1 to Scenario 5, the plurality of sub-identifications in the first slice identifier also include a flag bit identifier.
  • the first slice identification also includes a flag bit identification.
  • the first slice identifier includes a topology identifier and a resource identifier
  • the first slice identifier also includes a flag bit identifier.
  • the first slice identifier includes a domain identifier, a topology identifier, an algorithm identifier and a resource identifier
  • the first slice identifier also includes a flag bit identifier.
  • FIG. 8 is a schematic structural diagram of a first slice identifier according to an embodiment of the present application.
  • the first slice identifier includes a domain identifier, a topology identifier, an algorithm identifier, a resource identifier, and a flag bit identifier.
  • the flag bit identifier is used to indicate a sub-identity in the first slice identifier used to guide forwarding and a forwarding policy corresponding to the first slice identifier.
  • the sub-identity used to guide forwarding refers to the sub-identity selected by the network device to guide the forwarding of the packet in the first slice identifier.
  • the sub-identities used to direct forwarding may be one or more sub-identities other than the flag bit identification in the first slice identification.
  • the sub-identities used to direct forwarding may be a topology identifier and an algorithm identifier;
  • the sub-identities can be topology identification, algorithm identification and resource identification.
  • the flag bit identifier is used to indicate which sub-identifiers in the slice identifier need to be used by the network device to perform packet forwarding.
  • the forwarding policy represented by the flag bit identifier is used to indicate the forwarding behavior after the interface is determined according to the sub-identity used to direct forwarding.
  • the forwarding behavior may refer to: if the first network device cannot find the interface for forwarding according to the first slice identifier, the first network device may not determine the interface for forwarding according to the first slice identifier, The first network device may forward the packet based on a default slice; or, if the first network device cannot find an interface for forwarding according to the first slice identifier, the first network device discards the first packet.
  • the first network device is a boundary device of a network domain, and the first network device receives packets from other network domains, and updates the received packets, so that the updated packets carry the above-mentioned The first slice identifier of . Then, the first network device performs packet forwarding based on the updated packet.
  • Cross-domain scenario 1 The first network device is located in the first network domain in the bearer network, and the first network device receives a packet sent by a network device in the second network domain in the bearer network, and the packet carries the information in the first network domain. 2.
  • the slice identifier valid in the network domain.
  • the first network device acts as a border node between the first network domain and the second network domain.
  • the first network device updates the packet received in the second network domain to obtain the updated packet, and
  • the network domain generated by the updated message is the first network domain.
  • the first network device is preconfigured with mapping relationships between slice identifiers of different network domains. Based on the mapping relationship, the first network device can convert the slice identifier valid in the second network domain into the slice identifier valid in the first network domain. Specifically, the first network device receives a second packet sent by the second network device, where the second packet includes a second slice identifier, and the second slice identifier includes multiple sub-identities. Then, the first network device updates the second slice identifier in the second packet to the first slice identifier based on the preconfigured mapping relationship to obtain the first packet.
  • the first slice identifier is valid in the first network domain and is used to indicate the first network slice in the first network domain; the second slice identifier is valid in the second network domain and used to indicate in the second network domain Second network slice.
  • the Service-Level Agreement (SLA) of the first network slice is the same as the SLA of the second network slice, that is, the network quality of the first network slice and the network quality of the second network slice are the same.
  • SLA Service-Level Agreement
  • FIG. 9a is a schematic diagram of network domain division according to an embodiment of the present application.
  • network device 1, network device 2, network device 3 and network device 4 are located in the second network domain;
  • network device 5, network device 6, network device 7 and network device 8 are located in the first network domain;
  • network Device 9, network device 10, network device 11 and network device 12 are located in the third network domain.
  • the network device 5 and the network device 6 in the first network domain are domain boundary nodes. After the network device 5 and the network device 6 receive the message from the second network domain, they need to update the received message to obtain the The updated message that takes effect in the first network domain.
  • network devices in different network domains may forward packets based on different combinations of sub-identities.
  • the network device in each network domain can select one or more sub-identifiers in the packet to determine the interface to forward the packet according to the forwarding policy in the current network domain, thereby realizing packet forwarding.
  • FIG. 9b is a schematic diagram of network domain division according to an embodiment of the present application.
  • network device 1, network device 2, network device 3, and network device 4 in the second network domain select the topology identifier, algorithm identifier, and resource identifier in the slice identifier to determine the interface of the packet, and based on the obtained interface forwards packets.
  • network device 5, network device 6, network device 7, and network device 8 in the first network domain select the topology identifier and algorithm identifier in the slice identifier to determine the interface of the packet, and forward the packet based on the obtained interface. message.
  • network device 9, network device 10, network device 11, and network device 12 in the third network domain select the algorithm identifier and resource identifier in the slice identifier to determine the interface of the packet, and forward the packet based on the obtained interface. message.
  • Cross-domain scenario 2 The first network device is a border node in the bearer network, and the first network device receives a packet sent by a network device in a network other than the bearer network, and the packet carries the network-wide slice identifier .
  • the first network device may receive a second packet sent by a network device in an access network or a core network, where the second packet carries a second slice identifier, and the second slice identifier is Effective in the entire network, that is, the second slice identifier is effective in the access network, bearer network, and core network.
  • the first network device updates the second slice identifier to the first slice identifier to obtain the first packet.
  • the second slice identifier is a single network slice selection support information (Single Network Slice Selection Assistance Information, S-NSSAI) or an application-aware network (Application-Aware Networking, APN) identifier.
  • S-NSSAI Single Network Slice Selection Assistance Information
  • APN Application-Aware Networking
  • the second slice identifier can indicate the network slice to which the second packet belongs in multiple network domains of the entire bearer network
  • the format of the second slice identifier may be the same as that of the first slice identifier
  • the second slice identifier The format can also be different from the first slice identifier. In this way, the first network device can convert the second slice identifier valid in multiple network domains into the first slice identifier valid in the network domain where the first network device is located.
  • the first network device receives the third packet, and determines the network slice to which the third packet belongs. The first network device then adds the first slice identifier to the third packet according to the network slice to which the third packet belongs to obtain the first packet.
  • the third packet includes a third slice identifier, and the third slice identifier is used to identify the network slice to which the third packet belongs in a bearer network including multiple network domains.
  • the third slice identifier can be an S-NSSAI or APN identifier, and the third slice identifier can also be in the same format as the first slice identifier.
  • the third slice identifier includes a plurality of sub identifiers, and the third slice identifier can indicate the third packet. Network slices belonging to multiple network domains of the entire bearer network.
  • the third slice identifier in the third packet is a global identifier in the bearer network and takes effect in multiple network domains of the entire bearer network, that is, the third slice identifier can identify the third packet in the bearer network.
  • the first network device may determine the network slice to which the third packet belongs based on the third slice identifier, so as to obtain the first slice identifier valid in the network domain where the first network device is located. Then, the first network device adds the first slice identifier to the third packet to obtain the first packet, where the first packet includes both the third slice identifier and the first slice identifier.
  • Cross-domain scenario 3 The first network device is located in a network domain of the bearer network, and the first network device receives a packet sent by a network device outside the network domain, and the packet does not carry a slice identifier.
  • the first network device receives the third packet, and determines the network slice to which the third packet belongs.
  • the third packet comes from a network device outside the network domain to which the first network device belongs, and the third packet does not carry a slice identifier.
  • the first network device then adds the first slice identifier to the third packet according to the network slice to which the third packet belongs to obtain the first packet.
  • the first network device may also add the first slice identifier and the fourth slice identifier to the third packet according to the network slice to which the third packet belongs to obtain the first packet.
  • the fourth slice identifier is used to identify the network slice to which the third packet belongs in a bearer network including multiple network domains. That is, the first packet generated by the first network device includes the first slice identifier and the fourth slice identifier.
  • the first slice identifier is valid only in the network domain where the first network device is located, and is used to instruct network devices in the network domain where the first network device is located to forward packets; the fourth slice identifier can take effect in multiple network domains and is used for Instructs the boundary nodes of a network domain to update the slice identities valid within a single network domain.
  • a policy for determining a network slice may be preconfigured in the first network device, and the first network device may, under the instruction of the policy, determine the network slice to which the third packet belongs according to the information in the third packet .
  • the information in the third packet includes one or more of the following information: source address, destination address, protocol number, Differentiated Services Code Point (DSCP) field, Traffic Class (Traffic Class) field, Virtual Local Area Network identifier (VLAN ID) and port number.
  • DSCP Differentiated Services Code Point
  • Traffic Class Traffic Class
  • VLAN ID Virtual Local Area Network identifier
  • the source address may be, for example, a source Internet (Internet Protocol, IP) address or a source media access control (Media Access Control, MAC) address, such as the address of a user host or a base station, for sending the message.
  • the destination address may be, for example, the destination IP address or destination MAC address of the packet.
  • the first network device may also determine the network slice to which the third packet belongs according to some other fields in the third packet. For example, the DSCP field or the TC field in the IPv4 or IPv6 packet header in the third packet, the VLAN ID in the Ethernet header, and the like. Specifically, the first network device may determine the network to which the third packet belongs according to one of the above fields (for example, source address, destination address, protocol number, DSCP field or TC field, etc.), or a combination of certain fields. slice.
  • Cross-domain scenario 4 The first network device is located in a network domain in the bearer network, and the first network device receives a packet sent by a network device outside the network domain, and the packet includes a packet that takes effect in multiple network domains.
  • the slice identifier and the slice identifier that is valid only in the network domain preceding the network domain where the first network is located.
  • the first network device receives the third packet, and determines the network slice to which the third packet belongs.
  • the third packet comes from a network device outside the network domain to which the first network device belongs, and the third packet carries two slice identifiers, a third slice identifier and a fourth slice identifier.
  • the third slice identifier carried in the third packet takes effect in the bearer network including multiple network domains, and the fourth slice identifier takes effect only in the network domain preceding the network domain where the first network is located.
  • the first network device determines the network slice to which the third packet belongs according to the third slice identifier, updates the fourth slice identifier in the third packet to the first slice identifier, and obtains a network slice including the third slice identifier and The first packet identified by the first slice.
  • the packets forwarded in the bearer network including multiple network domains include two slice identifiers.
  • One slice identifier can take effect in multiple network domains, and is used to guide the update of border nodes in a network domain to take effect in a single network domain.
  • the slice identifier of the other slice identifier is valid only in one network domain and is used to instruct network devices in the current network domain to forward packets.
  • FIG. 10 is a schematic structural diagram of a network device 1000 according to an embodiment of the present application.
  • network device 1000 includes one or more processing units (cpus) 1001, a network interface 1002, a programming interface 1003, memory 1004, and one or more communication buses 1005 for connecting various component interconnection.
  • processing units cpus
  • network interface 1002 a network interface 1002
  • programming interface 1003 a programming interface 1003
  • memory 1004 a programming interface for connecting various component interconnection.
  • communication buses 1005 for connecting various component interconnection.
  • the network device 1000 may also omit or add some functional components or units based on the foregoing examples.
  • the network interface 1002 is used, among other things, to interface with one or more other network devices/servers in the network system.
  • the communication bus 1005 includes circuitry that interconnects and controls communication between system components.
  • Memory 1004 may include non-volatile memory such as read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM) , Electrically Erasable Programmable Read-Only Memory (electrically EPROM, EEPROM) or flash memory.
  • Memory 1004 may also include volatile memory, which may be random access memory (RAM), which acts as an external cache.
  • memory 1004 or a non-transitory computer-readable storage medium of memory 1004 stores the following programs, modules, and data structures, or subsets thereof, including, for example, a transceiver unit (not shown), an acquisition unit 10041, and a process Unit 10042.
  • the network device 1000 may have any function of the network device 2 in the method embodiment corresponding to FIG. 2 above.
  • the network device 1000 corresponds to the first network device in the foregoing method embodiments, and each module and the foregoing other operations and/or functions in the network device 1000 are respectively implemented to implement the first network device in the foregoing method embodiments.
  • each module and the foregoing other operations and/or functions in the network device 1000 are respectively implemented to implement the first network device in the foregoing method embodiments.
  • transceiver unit can be realized by the processor calling the program code in the memory, and cooperate with the network interface 1002 when needed; it can also be the network interface 1002 on the network device 1000 to complete the data transceiver operation .
  • the network device 1000 is configured to execute the packet processing method provided by the embodiment of the present application, for example, execute the packet processing method corresponding to the embodiment shown in FIG. 2 above.
  • the embodiments of the present application further provide a network device, and the hardware structure of the network device is introduced below.
  • FIG. 11 is a schematic structural diagram of a network device 1100 according to an embodiment of the present application, and the network device 1100 may be configured as the first network device in the foregoing method embodiments.
  • the network device 1100 may correspond to the first network device in the above method embodiments, and each hardware, module, and other operations and/or functions in the network device 1100 are respectively implemented to implement the first network device in the method embodiments.
  • each step of the method embodiment corresponding to FIG. 2 above is completed by an integrated logic circuit of hardware in the processor of the network device 1100 or an instruction in the form of software.
  • the steps of the methods disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware processor, or executed by a combination of hardware and software modules in the processor.
  • the software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art.
  • the storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware. To avoid repetition, detailed description is omitted here.
  • the network device 1100 may also correspond to the network device 1100 in the foregoing virtual appliance embodiment, and each functional module in the network device 1100 is implemented by software and hardware of the network device 1100 .
  • the functional modules included in the network device 1100 are generated after the processor of the network device 1100 reads the program code stored in the memory, or the processor of the network device 1100 reads the program code stored in the memory, and It is realized together with the communication interface.
  • the network device 1100 includes: a main control board 1110 and an interface board 1130 .
  • the main control board 1110 is also called the main processing unit (main processing unit, MPU) or the route processor card (route processor card). Equipment maintenance, protocol processing functions.
  • the main control board 1110 includes: a central processing unit 1111 and a memory 1112 .
  • the interface board 1130 is also referred to as a line processing unit (LPU), a line card or a service board.
  • the interface board 1130 is used to provide various service interfaces and implement data packet forwarding.
  • the service interface includes but is not limited to an Ethernet interface, a POS (Packet over SONET/SDH) interface, etc.
  • the Ethernet interface is, for example, a flexible Ethernet service interface (Flexible Ethernet Clients, FlexE Clients).
  • the interface board 1130 includes: a central processing unit 1131 , a network processor 1132 , a forwarding table entry memory 1134 and a physical interface card (ph11sical interface card, PIC) 1133 .
  • the central processing unit 1131 on the interface board 1130 is used to control and manage the interface board 1130 and communicate with the central processing unit 1111 on the main control board 1110 .
  • the network processor 1132 is used to implement packet forwarding processing.
  • the form of the network processor 1132 may be a forwarding chip.
  • the processing of the uplink packet includes: processing of the incoming interface of the packet, and searching of the forwarding table; processing of the downlink packet: searching of the forwarding table, and so on.
  • the physical interface card 1133 is used to realize the interconnection function of the physical layer, the original traffic enters the interface board 1130 through this, and the processed packets are sent from the physical interface card 1133 .
  • the physical interface card 1133 includes at least one physical interface, and the physical interface is also called a physical port.
  • the physical interface card 1133 corresponds to the FlexE physical interface in the system architecture.
  • the physical interface card 1133 is also called a daughter card, which can be installed on the interface board 1130, and is responsible for converting the photoelectric signal into a message, checking the validity of the message, and forwarding it to the network processor 1132 for processing.
  • the central processing unit 1131 of the interface board 1103 can also perform the functions of the network processor 1132 , such as implementing software forwarding based on a general-purpose CPU, so that the network processor 1132 is not required in the physical interface card 1133 .
  • the network device 1100 includes multiple interface boards.
  • the network device 1100 further includes an interface board 1140 .
  • the interface board 1140 includes a central processing unit 1141 , a network processor 1142 , a forwarding table entry storage 1144 and a physical interface card 1143 .
  • the network device 1100 further includes a switch fabric board 1120 .
  • the switch fabric unit 1120 may also be referred to as a switch fabric unit (switch fabric unit, SFU).
  • SFU switch fabric unit
  • the switching network board 1120 is used to complete data exchange between the interface boards.
  • the interface board 1130 and the interface board 1140 can communicate through the switch fabric board 1120 .
  • the main control board 1110 and the interface board 1130 are coupled.
  • the main control board 1110, the interface board 1130, the interface board 1140, and the switch fabric board 1120 are connected to the system backplane through a system bus to implement intercommunication.
  • an inter-process communication (inter-process communication, IPC) channel is established between the main control board 1110 and the interface board 1130, and the main control board 1110 and the interface board 1130 communicate through the IPC channel.
  • IPC inter-process communication
  • the network device 1100 includes a control plane and a forwarding plane
  • the control plane includes the main control board 1110 and the central processing unit 1131
  • the forwarding plane includes various components that perform forwarding, such as the forwarding entry storage 1134, the physical interface card 1133 and the network processing device 1132.
  • the control plane executes functions such as routers, generating forwarding tables, processing signaling and protocol packets, and configuring and maintaining device status.
  • the control plane delivers the generated forwarding tables to the forwarding plane.
  • the network processor 1132 based on the control plane
  • the delivered forwarding table forwards the packets received by the physical interface card 1133 by looking up the table.
  • the forwarding table issued by the control plane may be stored in the forwarding table entry storage 1134 .
  • the control plane and forwarding plane may be completely separate and not on the same device.
  • the transceiver unit in the network device 1100 may be equivalent to the physical interface card 1133 or the physical interface card 1143 in the network device 1100 ; the acquiring unit 11041 and the processing unit 11042 in the network device 1100 may be equivalent to the central processing unit in the network device 1100 controller 1111 or central processing unit 1131.
  • the operations on the interface board 1140 in the embodiment of the present application are the same as the operations on the interface board 1130, and are not repeated for brevity.
  • the network device 1100 in this embodiment may correspond to the first network device in the foregoing method embodiments, and the main control board 1110 , the interface board 1130 and/or the interface board 1140 in the network device 1100 may implement the foregoing methods
  • the functions possessed by the first network device and/or the various steps implemented in the embodiments are not repeated here.
  • main control boards there may be one or more main control boards, and when there are multiple main control boards, they may include the main main control board and the backup main control board.
  • a network device may have at least one switching network board, and the switching network board realizes data exchange between multiple interface boards, providing large-capacity data exchange and processing capabilities. Therefore, the data access and processing capabilities of network devices in a distributed architecture are greater than those in a centralized architecture.
  • the network device can also be in the form of only one board, that is, there is no switching network board, and the functions of the interface board and the main control board are integrated on this board.
  • the central processing unit and the main control board on the interface board The central processing unit on the board can be combined into a central processing unit on this board to perform the functions of the two superimposed, the data exchange and processing capacity of this form of equipment is low (for example, low-end switches or routers and other networks. equipment).
  • the specific architecture used depends on the specific networking deployment scenario, and is not uniquely limited here.
  • the above-mentioned first network device may be implemented as a virtualized device.
  • the virtualization device may be a virtual machine (English: Virtual Machine, VM) running a program for sending a message, and the virtual machine is deployed on a hardware device (for example, a physical server).
  • a virtual machine refers to a complete computer system with complete hardware system functions simulated by software and running in a completely isolated environment.
  • the virtual machine can be configured as the first network device.
  • the first network device may be implemented based on a general physical server combined with a Network Functions Virtualization (NFV) technology.
  • the first network device is a virtual host, a virtual router or a virtual switch.
  • An embodiment of the present application provides a computer program product, which, when the computer program product runs on a network device, enables the network device to execute the method performed by the network device 2 in the method embodiment corresponding to FIG. 2 above.
  • an embodiment of the present application provides a network system 1200 .
  • the system 1200 includes: a network device 1201 , a network device 1202 , and a network device 1203 .
  • the network device 1201 is connected to the network device 1202 and the network device 1203, respectively.
  • the network device 1201 may be the first network device in the method embodiment corresponding to FIG. 2 .
  • Embodiments of the present application further provide a chip, including a processor and an interface circuit, where the interface circuit is configured to receive instructions and transmit them to the processor.
  • the processor is coupled to a memory, and the memory is used to store programs or instructions, and when the programs or instructions are executed by the processor, the chip system enables the method in any of the foregoing method embodiments.
  • the number of processors in the chip system may be one or more.
  • the processor can be implemented by hardware or by software.
  • the processor may be a logic circuit, an integrated circuit, or the like.
  • the processor may be a general-purpose processor implemented by reading software codes stored in memory.
  • the number of memories in the system-on-chip may also be one or more.
  • the memory may be integrated with the processor, or may be provided separately from the processor, which is not limited in this application.
  • the memory can be a non-transitory processor, such as a read-only memory ROM, which can be integrated with the processor on the same chip, or can be provided on different chips.
  • the setting method of the processor is not particularly limited.
  • the system-on-chip may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or a system on chip (SoC), It can also be a central processing unit (CPU), a network processor (NP), a digital signal processing circuit (DSP), or a microcontroller (microcontroller).
  • controller unit, MCU it can also be a programmable logic device (PLD) or other integrated chips.
  • B corresponding to A means that B is associated with A, and B can be determined according to A.
  • determining B according to A does not mean that B is only determined according to A, and B may also be determined according to A and/or other information.
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of units is only a logical function division.
  • there may be other division methods for example, multiple units or components may be combined or integrated. to another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • Units described as separate components may or may not be physically separated, and components shown as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.
  • the integrated unit if implemented as a software functional unit and sold or used as a stand-alone product, may be stored in a computer-readable storage medium.
  • the technical solutions of the present application can be embodied in the form of software products in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, and the computer software products are stored in a storage medium , including several instructions to cause a computer device (which may be a personal computer, a server, or a network device/server, etc.) to execute all or part of the steps of the methods of the various embodiments of the present application.
  • the aforementioned storage medium includes: a U disk, a removable hard disk, a read-only memory, a random access memory, a magnetic disk or an optical disk and other media that can store program codes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请公开了一种报文处理方法及相关装置，应用于网络切片中。该方法包括：第一网络设备获取第一报文，所述第一报文包括第一切片标识，所述第一切片标识包括连续的多个子标识，所述多个子标识用于表示第一网络切片不同的属性，所述第一切片标识用于标识所述第一报文所属的第一网络切片；所述第一网络设备根据所述第一切片标识转发所述第一报文。本方案中，通过在报文中携带包括多个子标识的切片标识，不同的子标识指示了网络切片不同的属性，保证了切片能力不同的设备也能够根据切片标识所指示的网络切片的属性来执行相应的报文转发行为。

Description

一种报文处理方法及相关装置
本申请要求于2021年2月2日提交中国专利局、申请号为202110143450.6、发明名称为“一种层次化的网络切片标识携带方法和设备”的中国专利申请的优先权和于2021年4月27日提交中国专利局、申请号为202110461985.8、发明名称为“一种报文处理方法及相关装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种报文处理方法及相关装置。
背景技术
网络切片(Network Slicing)是一种虚拟化形式，允许多个逻辑网络在共享的物理网络基础设施之上运行。也就是说，基于一个共享的物理网络，通过虚拟化技术切割出相应的网络切片(或虚拟网络)来满足用户差异化的需求。每个虚拟的网络切片之间逻辑上资源隔离、各自独立、互不影响。
目前，在承载网中实现报文基于网络切片转发的方案为：控制器统一给每个网络切片分配一个切片标识；网络设备所接收到的报文中携带切片标识，网络设备根据该切片标识确定网络切片，并使用与所确定的网络切片对应的资源转发报文。
然而，目前的切片标识为一个全局的标识，要求网络中的所有设备都能一致地理解切片标识的含义，并使用该切片标识所指示的资源转发报文。但网络中不同设备所支持的切片能力可能存在差异，且不同设备所支持的切片数量也可能不同，难以保证所有设备都能够使用同一个切片标识执行相应的报文转发行为。
发明内容
本申请提供了一种报文处理方法，在报文中携带包括多个子标识的切片标识，不同的子标识指示了网络切片不同的属性，保证了切片能力不同的设备也能够根据切片标识所指示的网络切片的属性来执行相应的报文转发行为。
本申请第一方面提供一种报文处理方法，该方法包括：第一网络设备获取第一报文，所述第一报文包括第一切片标识。其中，所述第一切片标识用于标识所述第一报文所属的第一网络切片。所述第一切片标识包括连续的多个子标识，每个子标识可以是用一个字段来表示，因此该第一切片标识可以用多个连续的字段来表示。第一切片标识中的多个子标识分别用于表示第一网络切片不同的属性，例如第一网络切片的拓扑、算路算法或者是转发资源等属性。在得到第一报文后，第一网络设备根据第一报文中的第一切片标识转发第一报文。具体地，第一网络设备基于第一报文中的第一切片标识，能够确定第一报文所属的第一网络切片。因此，第一网络设备能够基于第一网络切片对应的资源转发第一报文。
本方案中，通过在报文中携带包括多个子标识的切片标识，不同的子标识指示了网络切片不同的属性，保证了切片能力不同的设备也能够根据切片标识所指示的网络切片的属性来执行相应的报文转发行为。
可选的，所述多个子标识包括拓扑标识和资源标识。其中，拓扑标识用于表示第一网 络切片的拓扑，即第一网络切片在网络域中所属的拓扑。资源标识用于表示第一网络切片的转发资源。第一网络切片的转发资源例如包括物理接口、逻辑子接口和/或报文队列。
在网络域划分有多个拓扑的场景下，在该网络域中执行转发的报文中的切片标识可以是包括拓扑标识和资源标识。网络设备通过拓扑标识来确定网络切片的拓扑，并进一步基于资源标识来确定网络切片对应的转发资源。
本方案中，通过在报文中携带拓扑标识和资源标识来指示报文所属的网络切片，可以使具有不同拓扑以及不同转发资源的网络切片使用相同的目的IP地址、MPLS标签或SID来标识同一个目的节点，避免了为切片规划更多数量的IP地址、MPLS标签或SID。此外，通过将拓扑标识和资源标识分开携带，可以实现使用相同拓扑的转发表项对拓扑相同的多个切片进行转发处理，降低切片对于转发表项数量增加的影响。
可选的，所述多个子标识还包括算法标识，所述算法标识用于表示所述第一网络切片的算路算法。即，第一切片标识中包括拓扑标识、算法标识和资源标识。
具体地，在转发第一报文的过程中，第一网络设备首先根据第一报文中用于指示转发路径的信息(例如上述的目的地址、MPLS标签或SID)确定第一报文的目的节点；然后，第一网络设备根据第一报文中的拓扑标识确定前往目的节点所使用的拓扑，并基于第一报文中的算法标识确定前往目的节点所使用的算路算法，从而获得用于转发报文的接口；最后，第一网络设备根据第一报文中的资源标识确定接口上对应的转发资源(例如逻辑子接口或队列)，从而实现第一报文的转发。
本方案中，通过在报文中携带拓扑标识、算法标识和资源标识，可以在具有不同拓扑、使用不同算法且有不同资源的网络切片中使用相同的信息来标识同一个目的节点，避免了为切片规划更多数量的目的节点信息。此外，通过将拓扑标识、算法标识和资源标识分开携带，可以实现使用相同拓扑或者相同算法的转发表项对拓扑或算法相同的多个切片进行转发处理，降低切片对于转发表项数量增加的影响。
可选的，所述多个子标识包括算法标识和资源标识，所述算法标识用于表示所述第一网络切片的算路算法，所述资源标识用于表示所述第一网络切片的转发资源。
在第一切片标识包括算法标识和资源标识的情况下，第一网络设备首先根据第一报文中用于指示转发路径的信息(例如上述的目的地址、MPLS标签或SID)确定第一报文的目的节点；然后，第一网络设备根据第一报文中的算法标识确定前往目的节点所使用的算路算法，从而获得在采用该算路算法时得到的转发路径对应的接口；最后，第一网络设备根据第一报文中的资源标识确定接口上对应的转发资源(例如逻辑子接口或队列)，从而实现第一报文的转发。
本方案中，通过在报文中携带算法标识和资源标识来指示报文所属的网络切片，可以使具有不同拓扑以及不同转发资源的网络切片使用相同的信息来标识同一个目的节点，避免了为切片规划更多数量的目的节点信息。此外，通过将算法标识和资源标识分开携带，可以实现使用相同算法的转发表项对算路算法相同的多个切片进行转发处理，降低切片对于转发表项数量增加的影响。
可选的，所述多个子标识还包括域标识，所述域标识用于表示所述第一切片标识生效 的网络域。例如，所述多个子标识包括域标识、拓扑标识和资源标识；或，所述多个子标识包括域标识、算法标识和资源标识；又或者，所述多个子标识包括域标识、拓扑标识、算法标识和资源标识。
本方案中，通过在切片标识中携带域标识，能够指示切片标识所生效的网络域，保证报文在各个不同的网络域中能够顺利转发。
可选的，所述多个子标识包括域标识和资源标识，所述域标识用于表示所述第一切片标识生效的网络域，所述资源标识用于表示所述第一网络切片的转发资源。其中，域标识用于表示第一切片标识生效的网络域，资源标识用于表示第一网络切片的转发资源。
切片标识中包括域标识和资源标识的子标识组合方式可以适用于跨多个网络域的网络切片场景。在该场景下，每个网络域内的网络切片可以使用不同的域标识和资源标识。多个网络域的网络切片拼接组成跨域网络切片。
可选的，所述转发资源包括物理接口、逻辑子接口和/或报文队列。
可选的，所述第一网络设备根据所述第一切片标识转发所述第一报文，包括：所述第一网络设备根据所述第一切片标识中的子标识以及映射表，确定用于转发所述第一报文的接口以及所述接口的转发资源；所述第一网络设备根据所述接口的转发资源向第二网络设备转发所述第一报文；其中，所述映射表包括所述多个子标识与接口之间的映射关系。所述映射表可以是同时包括多个子标识与接口以及接口的转发资源之间的映射关系，所述映射表也可以是包括多个子映射表，所述多个子映射表分别包括各个子标识与接口之间的映射关系。
可选的，所述多个子标识还包括标志位标识。例如，第一切片标识除了包括拓扑标识和资源标识，第一切片标识还包括标志位标识。又例如，第一切片标识除了包括域标识、拓扑标识、算法标识和资源标识，第一切片标识还包括标志位标识。其中，标志位标识用于表示第一切片标识中用于指导转发的子标识以及第一切片标识对应的转发策略。
其中，用于指导转发的子标识是指第一切片标识中被网络设备选择来指导转发报文的子标识。用于指导转发的子标识可以是第一切片标识中除标志位标识之外的一个或多个子标识。例如，在第一切片标识包括域标识、拓扑标识、算法标识、资源标识和标志位标识的情况下，用于指导转发的子标识可以为拓扑标识和算法标识；或者，用于指导转发的子标识可以为拓扑标识、算法标识和资源标识。简单来说，标志位标识用于指示网络设备需要采用切片标识中的哪些子标识来执行报文的转发。
标志位标识所表示的转发策略用于指示根据用于指导转发的子标识确定接口后的转发行为。
可选的，转发行为可以是指：若第一网络设备根据第一切片标识无法查找到用于转发的接口，则第一网络设备可以不根据第一切片标识确定用于转发的接口，第一网络设备可以是基于默认的切片来转发报文；或，若第一网络设备根据第一切片标识无法查找到用于转发的接口，则第一网络设备丢弃第一报文。
本方案中，通过在切片标识中携带标志位标识来指示用于指导转发的子标识以及转发策略，能够使得网络设备基于不同的策略来执行报文的转发，从而满足报文转发过程中多 样化的业务要求。
可选的，在跨域场景下，所述方法还包括：所述第一网络设备接收第二报文，所述第二报文包括第二切片标识；所述第一网络设备将所述第二切片标识更新为所述第一切片标识，得到所述第一报文。其中，第二切片标识是在第二网络域中生效，第一切片标识是在第一网络设备所在的第一网络域中生效。
可选的，所述第一切片标识用于在第一网络域中指示所述第一网络切片，所述第二切片标识用于在第二网络域中指示第二网络切片，所述第一网络切片的服务等级协议(Service-Level Agreement，SLA)与所述第二网络切片的SLA相同。即，第一网络切片的网络质量与第二网络切片的网络质量是相同的。
可选的，第一网络设备为承载网中的边界节点，第一网络设备接收承载网之外的网络中的网络设备所发送的报文，且该报文中携带有全网的切片标识。第一网络设备可以接收接入网或核心网中的网络设备所发送的第二报文，该报文中携带有第二切片标识，且第二切片标识是在全网中生效的，即第二切片标识在接入网、承载网和核心网中都是生效的。例如，第二切片标识为单网络切片选择支撑信息(Single Network Slice Selection Assistance Information，S-NSSAI)或应用感知网络(Application-Aware Networking，APN)标识。
可选的，第一网络设备为承载网中的边界节点，第一网络设备所获取到的第二报文中携带有在包括多个网络域的承载网中生效的第二切片标识。第二切片标识能够指示第二报文在整个承载网的多个网络域中所属的网络切片。第二切片标识的格式可以是与第一切片标识的格式相同，第二切片标识的格式也可以是与第一切片标识不同。这样，第一网络设备能够将在多个网络域中生效的第二切片标识转换为在第一网络设备所在的网络域生效的第一切片标识。
可选的，第一网络设备可以是位于承载网中的网络域，第一网络设备接收该网络域之外的网络设备所发送的报文。具体地，第一网络设备接收第三报文，并确定第三报文所属的网络切片。第三报文来自于第一网络设备所属的网络域之外的网络设备。第一网络设备再根据第三报文所属的网络切片，在第三报文中添加第一切片标识，得到第一报文。
可选的，所述第一网络设备确定所述第三报文所属的网络切片，包括：所述第一网络设备根据所述第三报文中的信息，确定所述第三报文所属的网络切片；其中，所述第三报文中的信息包括以下信息的一种或多种：源地址、目的地址、协议号、差分服务代码点(Differentiated Services Code Point，DSCP)字段、流量等级(Traffic Class)字段、虚拟局域网标识(Virtual Local Area Network identifier，VLAN ID)和端口号。
可选的，所述第一网络设备根据所述第三报文所属的网络切片，在所述第三报文中添加所述第一切片标识，包括：所述第一网络设备根据所述第三报文所属的网络切片，在所述第三报文中添加所述第一切片标识和第四切片标识，得到所述第一报文；所述第四切片标识用于在包括多个网络域的承载网中标识所述第三报文所属的网络切片。
可选的，所述第一网络设备确定所述第三报文所属的网络切片，包括：所述第一网络设备根据所述第三报文中的第三切片标识，确定所述第三报文所属的网络切片；其中，所 述第三切片标识用于在包括多个网络域的承载网中标识所述第三报文所属的网络切片。
简单来说，第三报文中的第三切片标识是承载网中的全局标识，在整个承载网的多个网络域中生效，即第三切片标识能够标识所述第三报文在承载网的多个网络域中所属的网络切片。
因此，第一网络设备可以基于第三切片标识确定第三报文所属的网络切片，从而得到在所述第一网络设备所在的网络域内生效的第一切片标识。然后，第一网络设备在第三报文中添加第一切片标识，得到第一报文，所述第一报文中同时包括第三切片标识以及第一切片标识。
当第一网络设备接收到的第三报文中仅包括第三切片标识时，第一网络设备则在第三切片标识的基础上添加第一切片标识，使得得到的第一报文中包括第三切片标识和第一切片标识这两个切片标识。
当第一网络设备接收到的第三报文中包括第三切片标识和另一个切片标识时，即第一网络设备从上一个网络域的网络设备处接收到了第三报文，那么第一网络设备就根据第三切片标识确定第一切片标识，并且将第三报文中的另一个切片标识替换为第一切片标识，使得得到的第一报文中包括第三切片标识和第一切片标识这两个切片标识。
本申请第二方面提供一种网络设备，包括收发单元和处理单元。所述收发单元，用于获取第一报文，所述第一报文包括第一切片标识，所述第一切片标识包括连续的多个子标识，所述多个子标识用于表示第一网络切片不同的属性，所述第一切片标识用于标识所述第一报文所属的第一网络切片；所述收发单元，还用于根据所述第一切片标识转发所述第一报文。
可选的，所述多个子标识包括拓扑标识和资源标识，所述拓扑标识用于表示所述第一网络切片的拓扑，所述资源标识用于表示所述第一网络切片的转发资源。
可选的，所述多个子标识还包括算法标识，所述算法标识用于表示所述第一网络切片的算路算法。
可选的，所述多个子标识包括算法标识和资源标识，所述算法标识用于表示所述第一网络切片的算路算法，所述资源标识用于表示所述第一网络切片的转发资源。
可选的，所述多个子标识还包括域标识，所述域标识用于表示所述第一切片标识生效的网络域。
可选的，所述多个子标识包括域标识和资源标识，所述域标识用于表示所述第一切片标识生效的网络域，所述资源标识用于表示所述第一网络切片的转发资源。
可选的，所述转发资源包括物理接口、逻辑子接口和/或报文队列。
可选的，所述处理单元，用于根据所述第一切片标识中的子标识以及映射表，确定用于转发所述第一报文的接口以及所述接口的转发资源；所述转发单元，还用于根据所述接口的转发资源向第二网络设备转发所述第一报文；其中，所述映射表包括所述多个子标识与接口之间的映射关系。
可选的，所述多个子标识还包括标志位标识，所述标志位标识用于表示所述第一切片 标识对应的转发策略，所述转发策略用于指示根据用于指导转发的子标识确定接口后的转发行为。
可选的，所述转发行为包括：若根据所述第一切片标识无法查找到用于转发的接口，则不根据所述第一切片标识确定用于转发的接口；或，若根据所述第一切片标识无法查找到用于转发的接口，则丢弃所述第一报文。
可选的，所述收发单元还用于接收第二报文，所述第二报文包括第二切片标识；所述处理单元还用于将所述第二切片标识更新为所述第一切片标识，得到所述第一报文。
可选的，所述第一切片标识用于在第一网络域中指示所述第一网络切片，所述第二切片标识用于在第二网络域中指示第二网络切片，所述第一网络切片的服务等级协议SLA与所述第二网络切片的SLA相同。
可选的，所述第一网络设备为承载网的边界节点，所述第二切片标识为单网络切片选择支撑信息S-NSSAI或应用感知网络APN标识。
可选的，所述收发单元还用于接收第三报文；所述处理单元还用于确定所述第三报文所属的网络切片；所述处理单元还用于根据所述第三报文所属的网络切片，在所述第三报文中添加所述第一切片标识，得到所述第一报文。
可选的，所述处理单元还用于根据所述第三报文中的信息，确定所述第三报文所属的网络切片；其中，所述第三报文中的信息包括以下信息的一种或多种：源地址、目的地址、协议号、差分服务代码点DSCP字段、流量等级TC字段、虚拟局域网标识和端口号。
可选的，所述处理单元还用于根据所述第三报文所属的网络切片，在所述第三报文中添加所述第一切片标识和第四切片标识，得到所述第一报文；所述第四切片标识用于在包括多个网络域的承载网中标识所述第三报文所属的网络切片。
可选的，所述处理单元还用于根据所述第三报文中的第三切片标识，确定所述第三报文所属的网络切片；其中，所述第三切片标识用于在包括多个网络域的承载网中标识所述第三报文所属的网络切片。
本申请第三方面提供一种网络设备，该网络设备包括：处理器，用于使得网络设备实现如前述第一方面的任一可能的实现方式中描述的方法。该设备还可以包括存储器，存储器与处理器耦合，处理器执行存储器中存储的指令时，可以使得网络设备实现前述第一方面任一种可能的实现方式描述的方法。该设备还可以包括通信接口，通信接口用于该装置与其它设备进行通信，示例性的，通信接口可以是收发器、电路、总线、模块或其它类型的通信接口。
本申请中存储器中的指令可以预先存储也可以使用该网络设备时从互联网下载后存储，本申请对于存储器中指令的来源不进行具体限定。本申请中的耦合是装置、单元或模块之间的间接耦合或连接，其可以是电性，机械或其它的形式，用于装置、单元或模块之间的信息交互。
本申请第四方面提供一种网络系统，该网络系统包括多个网络设备，该多个网络设备中包括如前述第三方面所述的网络设备。当该网络设备获取到报文时，该网络设备能够实 现前述第一方面任一种可能的实现方式描述的方法。
本申请第五方面提供一种计算机存储介质，该计算机存储介质可以是非易失性的；该计算机存储介质中存储有计算机可读指令，当该计算机可读指令被处理器执行时实现第一方面的任一可能的实现方式中描述的方法。
本申请第六方面提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行如第一方面任一可能的实现方式中描述的方法。
上述第二方面至第六方面提供的方案，用于实现或配合实现上述第一方面提供的方法，因此可以与第一方面达到相同或相应的有益效果，此处不再进行赘述。
附图说明
图1为本申请实施例提供的一种网络的结构示意图；
图2为本申请实施例提供的一种报文处理方法200的流程示意图；
图3a为本申请实施例提供的一种切片标识的结构示意图；
图3b为本申请实施例提供的另一种切片标识的结构示意图；
图3c为本申请实施例提供的一种报文的转发示意图；
图4a为本申请实施例提供的一种切片标识的结构示意图；
图4b为本申请实施例提供的另一种报文的转发示意图；
图5a为本申请实施例提供的一种切片标识的结构示意图；
图5b为本申请实施例提供的另一种报文的转发示意图；
图5c为本申请实施例提供的一种网络设备基于切片标识转发报文的示意图；
图6为本申请实施例提供的另一种切片标识的结构示意图；
图7为本申请实施例提供的第一切片标识的另一种结构示意图；
图8为本申请实施例提供的能够第一切片标识的结构示意图；
图9a为本申请实施例提供的一种网络域的划分示意图；
图9b为本申请实施例提供的另一种网络域的划分示意图；
图10为本申请实施例提供的一种网络设备1000的结构示意图；
图11为本申请实施例提供的一种网络设备1100的结构示意图；
图12为本申请实施例提供了一种网络系统1200的结构示意图。
具体实施方式
为了使本申请的目的、技术方案及优点更加清楚明白，下面结合附图，对本申请的实施例进行描述，显然，所描述的实施例仅仅是本申请一部分的实施例，而不是全部的实施例。本领域普通技术人员可知，随着新应用场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的实施例能够以除了在这里图示或描述的内容以外的顺序实 施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或模块的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或模块，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或模块。在本申请中出现的对步骤进行的命名或者编号，并不意味着必须按照命名或者编号所指示的时间/逻辑先后顺序执行方法流程中的步骤，已经命名或者编号的流程步骤可以根据要实现的技术目的变更执行次序，只要能达到相同或者相类似的技术效果即可。本申请中所出现的单元的划分，是一种逻辑上的划分，实际应用中实现时可以有另外的划分方式，例如多个单元可以结合成或集成在另一个系统中，或一些特征可以忽略，或不执行，另外，所显示的或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，单元之间的间接耦合或通信连接可以是电性或其他类似的形式，本申请中均不作限定。并且，作为分离部件说明的单元或子单元可以是也可以不是物理上的分离，可以是也可以不是物理单元，或者可以分布到多个电路单元中，可以根据实际的需要选择其中的部分或全部单元来实现本申请方案的目的。
在5G网络中，多样化的业务需求对网络在速度、性能、安全、可靠性、时延等方面的需求各不相同。例如，增强移动宽带(enhanced mobile broadband，eMBB)场景(例如虚拟现实，增强现实等场景)，对带宽要求较高，需要xGbps级的带宽。再例如，海量机器类通信(massive machine type communication，mMTC)场景(例如可穿戴场景，智能电网等场景)，需要支持海量的设备接入，例如需要支持数亿或数十亿的设备接入。再例如，超可靠低时延(ultrareliable and low latency communications，uRLLC)场景(例如自动驾驶，远程手术，工业控制等场景)，需要支持1ms的超低时延。面对不同的场景、不同的要求以及极致体验的需求，网络切片应运而生，它可以基于不同的场景和需求灵活构建不同特征的网络。
网络切片，是指在物理或者虚拟的网络基础设施上，根据不同的业务需求而定制的逻辑网络。网络切片可以是一个包括了接入网、承载网、核心网以及应用服务器的完整的端到端网络，能够提供完整的通信服务，具有一定网络能力。网络切片也可以是接入网、承载网、核心网和应用服务器的任意组合。
一个网络切片通常可以视为一个实例化的5G网络。这样的网络结构允许运营商将网络作为一种服务提供给用户，并可以根据速率、容量、覆盖性、延迟、可靠性、安全性和可用性等指标对实体网络进行自由组合，从而满足不同用户的要求。
目前，在承载网中实现报文基于网络切片转发的方案为：控制器统一给每个网络切片分配一个切片标识。网络设备所接收到的报文中携带切片标识，该切片标识与报文中指示目的地址或路径的其他字段共同确定报文的转发行为。网络设备在转发报文时，根据报文中的目的地址字段、多协议标签交换(Multi-Protocol Label Switching，MPLS)标签栈或分段路由头(Segment Routing header，SRH)等信息确定该报文的接口。然后，网络设备根据报文中的切片标识确定该报文所属的网络切片，并使用接口上与该网络切片对应的资源对报文进行转发。
然而，目前的切片标识为一个全局的标识，要求网络中的所有设备都能一致地理解切 片标识的含义，并使用该切片标识所指示的资源转发报文。但网络中不同设备所支持的切片能力可能存在差异，且不同设备所支持的切片数量也可能不同，难以保证所有设备都能够使用同一个切片标识执行相应的报文转发行为。
此外，当多个不同的网络切片具有相同的某种属性时，例如拓扑或算法属性，对一组网络切片可以执行相同的转发动作，即基于同一个接口转发报文。但是由于每个网络切片对应的切片标识都是相互独立的不同取值，因此网络设备无法基于切片标识获取切片之间的共性特征。在这种情况下，网络设备还需要结合报文中的其他标识，例如同一组切片共用的目的IP地址字段、MPLS标签或段标识(segment ID，SID)来指导切片的转发。这要求IP地址、MPLS标签或SID基于切片的部分属性进行规划和分配，例如分配不同的IP地址、MPLS标签或SID来标识不同的拓扑或算法，从而增加了IP地址或标签的规划难度和数量。
有鉴于此，本申请实施例提供了一种报文处理方法，通过在报文中携带包括多个子标识的切片标识，不同的子标识指示了网络切片不同的属性，保证了切片能力不同的设备也能够根据切片标识所指示的网络切片的属性来执行相应的报文转发行为。
可以参阅图1，图1为本申请实施例提供的一种网络的结构示意图。图1所示的网络中包括网络设备1-网络设备8。网络设备1为网络中的头节点，网络设备2-网络设备7为网络中的中间节点，网络设备8为网络中的尾节点。网络设备1在报文中封装包括连续的多个子标识的切片标识，并向网络域中的中间节点发送报文。网络域中的中间节点根据报文中的切片标识转发报文，从而实现将报文转发至作为尾节点的网络设备8。网络设备8根据报文中的切片标识，将报文转发至其他的网络域中。
可以参阅图2，图2为本申请实施例提供的一种报文处理方法200的流程示意图。该报文处理方法200可以应用于图1所示的网络结构中。如图2所示，该报文处理方法200至少包括以下步骤。
步骤201，第一网络设备获取第一报文，第一报文包括第一切片标识，第一切片标识包括连续的多个子标识，多个子标识用于表示第一网络切片不同的属性，第一切片标识用于标识第一报文所属的第一网络切片。
本实施例中，第一网络设备为承载网中的网络。例如，第一网络设备可以为MPLS网络、第四版互联网协议(Internet Protocol version 4，IPv4)网络或第六版互联网协议(Internet Protocol version 6，IPv6)网络中的网络设备。第一网络设备例如可以为路由器、交换机或网关等物理设备，也可以是支持报文转发的虚拟设备等。本实施例对第一网络设备的具体类型不做限定。
第一网络设备获取第一报文的方式可以是接收其他网络设备发送的第一报文，例如接收位于MPLS网络之外的网络设备所发送的数据报文，或者是自身生成第一报文，或者是从接入网侧的网络设备接收第一报文。
第一报文中包括用于标识第一报文所属的第一网络切片的第一切片标识。第一切片标识中包括连续的多个子标识，每个子标识可以是用一个字段来表示，因此该第一切片标识可以用多个连续的字段来表示。第一切片标识中的多个子标识分别用于表示第一网络切片 不同的属性，例如第一网络切片的拓扑、算路算法或者是转发资源等属性。
第一切片标识可以携带在不同类型的数据报文中的不同位置，本实施例并不对第一切片标识的携带方式做具体限定。
在一些可能的实现方式中，第一报文可以为IPv6数据报文。第一切片标识可以携带于IPv6数据报文的固定报文头的某些字段中，例如固定报文头的流标签(Flow label)字段、源地址字段或目的地址字段。第一切片标识还可以携带于IPv6数据报文的扩展报文头中，该IPv6数据报文的扩展报文头例如可以为逐跳(hop by hop，HBH)报文头、路由扩展头或目的扩展头。
在另一些可能的实现方式中，第一报文可以为MPLS数据报文。第一切片标识可以携带于MPLS数据报文的MPLS报文头的MPLS标签栈中。第一切片标识也可以是携带于位于MPLS报文头之后的控制字字段或扩展头中。其中，MPLS数据报文中的扩展头位于MPLS标签和有效载荷之间。
步骤202，第一网络设备根据第一切片标识转发第一报文。
本实施例中，第一网络设备基于第一报文中的第一切片标识，能够确定第一报文所属的第一网络切片。因此，第一网络设备能够基于第一网络切片对应的资源转发第一报文。
在本实施例中，通过在报文中携带包括多个子标识的切片标识，不同的子标识指示了网络切片不同的属性，保证了切片能力不同的设备也能够根据切片标识所指示的网络切片的属性来执行相应的报文转发行为。
为了便于理解，以下将详细介绍在不同场景下，第一切片标识中所包括的多个子标识。
场景一：第一切片标识中的多个子标识包括拓扑标识和资源标识。
可以参阅图3a，图3a为本申请实施例提供的一种切片标识的结构示意图。如图3a所示，第一切片标识中包括拓扑标识和资源标识。其中，拓扑标识用于表示第一网络切片的拓扑，即第一网络切片在网络域中所属的拓扑。资源标识用于表示第一网络切片的转发资源。第一网络切片的转发资源例如包括物理接口、逻辑子接口和/或报文队列。
可选的，在第一切片标识中，资源标识可以包括多级子标识，且不同级的子标识表示不同的转发资源。基于资源标识中的多级子标识，能够指示更细粒度的转发资源。可以参阅图3b，图3b为本申请实施例提供的另一种切片标识的结构示意图。如图3b所示，第一切片标识中的资源标识可以包括一级资源标识和二级资源标识，一级资源标识和二级资源标识表示不同的转发资源。例如，一级资源标识所指示的资源为接口对应的逻辑子接口，二级资源标识所指示的资源为逻辑子接口对应的队列资源；这样，基于一级资源标识和二级资源标识，第一网络设备能够确定接口上用于转发第一报文的具体转发资源。
在场景一中，第一网络设备所在的网络域可以是使用多拓扑(Multi-topology)技术来划分网络域中的网络切片的拓扑。网络域中不同的网络切片可以对应于不同的拓扑；网络域中不同的网络切片也可以是对应于同一个拓扑，但是网络设备上为不同网络切片所分配的转发资源是不同的，网络设备可以基于资源标识来区分为不同网络切片所分配的转发资源。
也就是说，在网络域划分有多个拓扑的场景下，在该网络域中执行转发的报文中的切片标识可以是包括拓扑标识和资源标识。网络设备通过拓扑标识来确定网络切片的拓扑，并进一步基于资源标识来确定网络切片对应的转发资源。
在一种可能的实现方式中，在第一切片标识包括拓扑标识和资源标识的情况下，第一网络设备基于第一切片标识转发第一报文的过程具体如下：第一网络设备首先根据第一报文中的目的地址、MPLS标签或段标识(segment ID，SID)等用于指示转发路径的信息确定第一报文的目的节点；然后，第一网络设备根据第一报文中的拓扑标识确定前往目的节点所使用的拓扑，从而获得在该拓扑下前往目的节点的接口；最后，第一网络设备根据第一报文中的资源标识确定使用接口上对应的转发资源(例如逻辑子接口或队列)转发第一报文。
在具体实现中，第一网络设备中可以预置有用于指导报文转发的映射表，该映射表例如可以为控制器下发的或者是人工手动配置的。第一网络设备的映射表中包括第一切片标识中的多个子标识与接口之间的映射关系。第一网络设备先根据第一报文中的目的地址、MPLS标签或SID等信息确定前往第一报文的目的节点的一个或多个接口。然后，第一网络设备根据拓扑标识、资源标识以及映射表，在前往第一报文的目的节点的一个或多个接口中确定用于转发第一报文的接口以及该接口对应的转发资源。最后，第一网络设备根据所确定的接口以及该接口对应的转发资源向第二网络设备转发第一报文。
可选的，第一网络设备中的映射表中可以是同时包括多个子标识与接口以及接口的转发资源之间的映射关系。即该映射表中包括不同的子标识组合，每个子标识组合具有对应的接口以及接口的转发资源，且不同的子标识组合对应于不同的接口或者不同的转发资源。例如，拓扑标识1和资源标识1对应于接口1和接口1上的队列1；拓扑标识1和资源标识2对应于接口1和接口1上的队列2；拓扑标识2和资源标识3对应于接口2和接口2上的队列3。这样，第一网络设备可以基于第一切片标识中的多个子标识以及映射表，确定映射表中与多个子标识唯一对应的接口以及接口的转发资源。
可选的，第一网络设备中的映射表也可以是包括多个不同的子映射表，且不同的子映射表包括了不同的子标识与接口或转发资源之间的映射关系。例如，第一网络设备中的映射表包括子映射表1和子映射表2，子映射表1包括拓扑标识与接口之间的映射关系，子映射表2包括资源标识与转发资源的映射关系。第一网络设备可以是基于拓扑标识和子映射表1确定接口，然后再基于资源标识和子映射表2确定接口对应的转发资源。
示例性地，可以参阅图3c，图3c为本申请实施例提供的一种报文的转发示意图。在图3c中，采用多拓扑技术对图1所示的网络结构进行了拓扑划分，得到拓扑1和拓扑2。其中，拓扑1包括网络设备1、网络设备2、网络设备3、网络设备4和网络设备8；拓扑2包括网络设备1、网络设备5、网络设备6、网络设备7和网络设备8。
假设网络设备1获取到了报文，该报文的目的节点为网络设备8；并且，该报文中的拓扑标识用于表示拓扑1，该报文中的资源标识用于表示队列1。那么，网络设备1基于报文的目的节点，可以确定用于转发报文的接口包括网络设备1和网络设备2之间的接口以及网络设备1与网络设备5之间的接口。在此基础上，网络设备1基于报文中的拓扑标识 确定使用拓扑1来转发报文，从而确定用于转发报文的接口为网络设备1和网络设备2之间的接口；进一步地，网络设备1基于报文中的资源标识确定最终使用网络设备1和网络设备2之间的接口对应的队列1来转发报文。
在场景一中，通过在报文中携带拓扑标识和资源标识来指示报文所属的网络切片，可以使具有不同拓扑以及不同转发资源的网络切片使用相同的目的IP地址、MPLS标签或SID来标识同一个目的节点，避免了为切片规划更多数量的IP地址、MPLS标签或SID。此外，通过将拓扑标识和资源标识分开携带，可以实现使用相同拓扑的转发表项对拓扑相同的多个切片进行转发处理，降低切片对于转发表项数量增加的影响。
场景二：第一切片标识中的多个子标识包括算法标识和资源标识。
可以参阅图4a，图4a为本申请实施例提供的一种切片标识的结构示意图。如图4a所示，第一切片标识中包括算法标识和资源标识。其中，算法标识用于表示第一网络切片的算路算法，即第一网络切片在网络域中用于进行算路的算法。资源标识用于表示第一网络切片的转发资源。第一网络切片的转发资源例如包括物理接口、逻辑子接口和/或报文队列。其中，第一切片标识中的资源标识也可以是包括多级子标识，且不同级的子标识表示不同的转发资源。资源标识包括多级子标识的方式具体可以参考上述的实施例，在此不再赘述。
在场景二中，第一网络设备所在的网络域可以是采用灵活算法(Flex-Algo)或者其他的特定算法等算路算法来定义网络域中的网络切片的算路约束。网络域中不同的网络切片可以是分别采用不同的算路算法来进行算路。网络域中不同的网络切片也可以是采用相同的算路算法来进行算路，但是网络设备上为不同网络切片所分配的转发资源是不同的，网络设备可以基于资源标识来区分为不同网络切片所分配的转发资源。
在一种可能的实现方式中，在第一切片标识包括算法标识和资源标识的情况下，第一网络设备基于第一切片标识转发第一报文的过程具体如下：第一网络设备首先根据第一报文中用于指示转发路径的信息(例如上述的目的地址、MPLS标签或SID)确定第一报文的目的节点；然后，第一网络设备根据第一报文中的算法标识确定前往目的节点所使用的算路算法，从而获得在采用该算路算法时得到的转发路径对应的接口；最后，第一网络设备根据第一报文中的资源标识确定接口上对应的转发资源(例如逻辑子接口或队列)，从而实现第一报文的转发。
具体地，第一网络设备可以是基于预置的映射表以及第一报文中的算法标识和资源标识，来转发第一报文。第一网络设备中的映射表可以是同时包括算法标识和资源标识与接口以及接口的转发资源之间的映射关系，第一网络设备中的映射表也可以是包括多个子映射表，该多个子映射表分别包括算法标识与接口之间的映射关系以及资源标识与转发资源的映射关系。第一网络设备基于映射表来转发第一报文的过程可以参考上述的场景一，在此不再赘述。
示例性地，可以参阅图4b，图4b为本申请实施例提供的另一种报文的转发示意图。如图4b所示，图4b中的网络结构可以采用不同的算路算法来进行报文的算路。假设网络 设备1获取到了报文，该报文的目的节点为网络设备8。当网络设备采用算法1来计算报文的转发路径时，计算得到的报文的转发路径为：网络设备1>网络设备2>网络设备3>网络设备4>网络设备8。当网络设备采算法2来计算报文的转发路径时，计算得到的报文的转发路径为：网络设备1>网络设备5>网络设备6>网络设备7>网络设备8。
假设网络设备1所获取到的报文中包括算法标识和资源标识，且算法标识所指示的算路算法是算法1，资源标识指示的转发资源为队列2。那么，网络设备1基于该报文中的算法标识和资源标识，确定转发报文的接口为网络设备1和网络设备2之间的接口；进一步地，网络设备1基于报文中的资源标识确定最终使用网络设备1和网络设备2之间的接口对应的队列2来转发报文。
在场景二中，通过在报文中携带算法标识和资源标识来指示报文所属的网络切片，可以使具有不同拓扑以及不同转发资源的网络切片使用相同的信息来标识同一个目的节点，避免了为切片规划更多数量的目的节点信息。此外，通过将算法标识和资源标识分开携带，可以实现使用相同算法的转发表项对算路算法相同的多个切片进行转发处理，降低切片对于转发表项数量增加的影响。
场景三：第一切片标识中的多个子标识包括拓扑标识、算法标识和资源标识。
可以参阅图5a，图5a为本申请实施例提供的一种切片标识的结构示意图。如图5a所示，第一切片标识中包括拓扑标识、算法标识和资源标识。其中，拓扑标识、算法标识和资源标识具体的具体介绍可以参考上述的实施例，在此不再赘述。
在场景三中，第一网络设备所在的网络域可以是使用多拓扑(Multi-topology)技术来划分网络域中的网络切片的拓扑，并且采用灵活算法(Flex-Algo)或者其他的特定算法等算路算法来定义网络域中的网络切片的算路约束。简单来说，第一网络设备所在的网络域中包括多个拓扑，每个拓扑中可以采用一种或多种算路算法来进行算路。
第一网络设备所在的网络域中不同的网络切片可以是对应于不同的拓扑，或者不同的网络切片可以是分别采用不同的算路算法来进行算路。网络域中不同的网络切片也可以是对应于相同的拓扑和算路算法，但是网络设备上为不同网络切片所分配的转发资源是不同的，网络设备可以基于资源标识来区分为不同网络切片所分配的转发资源。
在一种可能的实现方式中，在第一切片标识包括拓扑标识、算法标识和资源标识的情况下，第一网络设备基于第一切片标识转发第一报文的过程具体如下：第一网络设备首先根据第一报文中用于指示转发路径的信息(例如上述的目的地址、MPLS标签或SID)确定第一报文的目的节点；然后，第一网络设备根据第一报文中的拓扑标识确定前往目的节点所使用的拓扑，并基于第一报文中的算法标识确定前往目的节点所使用的算路算法，从而获得用于转发报文的接口；最后，第一网络设备根据第一报文中的资源标识确定接口上对应的转发资源(例如逻辑子接口或队列)，从而实现第一报文的转发。
具体地，第一网络设备可以是基于预置的映射表以及第一报文中的拓扑标识、算法标识和资源标识，来转发第一报文。第一网络设备中的映射表可以是同时包括拓扑标识、算法标识和资源标识与接口以及接口的转发资源之间的映射关系，第一网络设备中的映射表 也可以是包括多个子映射表，该多个子映射表分别包括拓扑标识与接口之间的映射关系、算法标识与接口之间的映射关系以及资源标识与转发资源的映射关系。第一网络设备基于映射表来转发第一报文的过程可以参考上述的场景一，在此不再赘述。
示例性地，可以参阅图5b，图5b为本申请实施例提供的另一种报文的转发示意图。如图5b所示，图5b中的网络结构划分了两个不同的拓扑(即拓扑1和拓扑2)，且采用不同的算路算法来进行报文的算路。其中，拓扑1包括网络设备1、网络设备2、网络设备3、网络设备4、网络设备6、网络设备7和网络设备8；拓扑2包括网络设备1、网络设备3、网络设备4、网络设备5、网络设备6、网络设备7和网络设备8。
假设网络设备1获取到了报文，该报文的目的节点为网络设备8。
当报文中的拓扑标识指示拓扑1，报文中的算法标识指示算法1时，网络设备基于拓扑标识和算法标识计算得到的报文的转发路径为：网络设备1>网络设备2>网络设备3>网络设备4>网络设备8。
当报文中的拓扑标识指示拓扑1，报文中的算法标识指示算法2时，网络设备基于拓扑标识和算法标识计算得到的报文的转发路径为：网络设备1>网络设备2>网络设备3>网络设备6>网络设备7>网络设备8。
当报文中的拓扑标识指示拓扑2，报文中的算法标识指示算法3时，网络设备基于拓扑标识和算法标识计算得到的报文的转发路径为：网络设备1>网络设备5>网络设备6>网络设备3>网络设备4>网络设备8。
当报文中的拓扑标识指示拓扑2，报文中的算法标识指示算法4时，网络设备基于拓扑标识和算法标识计算得到的报文的转发路径为：网络设备1>网络设备5>网络设备6>网络设备7>网络设备8。
其中，算法1与算法2是不同类型的算路算法，算法3与算法4也是不同类型的算路算法。算法1与算法3或算法4可以是不同类型的算路算法，也可以是相同类型的算路算法。
假设网络设备1所获取到的报文中包括拓扑标识、算法标识和资源标识，且拓扑标识所指示的拓扑为拓扑1，算法标识所指示的算路算法是算法1，资源标识指示的转发资源为队列2。那么，网络设备1基于该报文中的拓扑标识、算法标识和资源标识，确定转发报文的接口为网络设备1和网络设备2之间的接口；进一步地，网络设备1基于报文中的资源标识确定最终使用网络设备1和网络设备2之间的接口对应的队列2来转发报文。
在场景三中，通过在报文中携带拓扑标识、算法标识和资源标识，可以在具有不同拓扑、使用不同算法且有不同资源的网络切片中使用相同的信息来标识同一个目的节点，避免了为切片规划更多数量的目的节点信息。此外，通过将拓扑标识、算法标识和资源标识分开携带，可以实现使用相同拓扑或者相同算法的转发表项对拓扑或算法相同的多个切片进行转发处理，降低切片对于转发表项数量增加的影响。
可选的，在场景三中，同一个网络域中的不同网络设备上可以配置不同的转发策略，以使得不同网络设备根据切片标识中不同的子标识来执行报文的转发。简单来说，对于同一个网络域中的网络设备来说，该网络设备可以是基于切片标识中的所有子标识来执行报 文的转发，该网络设备也可以是基于切片标识中的部分子标识来执行报文的转发。在实际转发过程中，网络设备可以基于所配置的转发策略确定切片标识中用于指导报文转发的子标识，然后根据这些用于指导报文转发的子标识来转发报文。
示例性地，可以参阅图5c，图5c为本申请实施例提供的一种网络设备基于切片标识转发报文的示意图。图5c所示的网络结构包括网络设备1-网络设备8，且在该网络结构中所转发的报文携带的切片标识包括拓扑标识、算法标识、一级资源标识和二级资源标识。
在该网络结构中，网络设备1、网络设备2和网络设备5所支持的切片粒度较细，且支持在同一节点或链路上为不同切片分配细粒度的资源。因此，网络设备1、网络设备2和网络设备5可以使用切片标识中所有子标识(即拓扑标识、算法标识、一级资源标识和二级资源标识)来转发报文。具体地，网络设备1、网络设备2和网络设备5可以基于拓扑标识和算法标识确定切片的拓扑和算路算法，从而在指定的拓扑中使用相应的算路算法进行算路，得到用于转发报文的接口；然后，使用一级资源标识和二级资源标识确定为切片所分配的资源，最终实现报文的转发。
在该网络结构中，网络设备3和网络设备6不支持在同一节点或链路上为不同切片分配细粒度的资源。因此，网络设备3和网络设备6则可以使用切片标识中的部分子标识，即拓扑标识和算法标识，来转发报文。具体地，网络设备3和网络设备6可以基于拓扑标识和算法标识确定切片的拓扑和算路算法，从而在指定的拓扑中使用相应的算路算法进行算路，得到用于转发报文的接口，并基于该接口转发报文。
在该网络结构中，网络设备4、网络设备7和网络设备8支持在同一节点或链路上为不同切片分配细粒度的资源，但是资源分配的粒度较粗。因此，网络设备4、网络设备7和网络设备8可以使用切片标识中的拓扑标识、算法标识、一级资源标识来转发报文。具体地，网络设备4、网络设备7和网络设备8可以基于拓扑标识和算法标识确定切片的拓扑和算路算法，从而在指定的拓扑中使用相应的算路算法进行算路，得到用于转发报文的接口；然后，使用一级资源标识确定为切片所分配的资源，最终实现报文的转发。
本实施例中，通过在不同的网络设备上配置不同的转发策略，能够使得同一个网络域中转发能力不同的网络设备可以基于相同的切片标识实现报文的转发，保障了报文的正常转发。
场景四：第一切片标识中的多个子标识包括域标识和资源标识。
可以参阅图6，图6为本申请实施例提供的另一种切片标识的结构示意图。如图6所示，第一切片标识中包括域标识和资源标识。其中，域标识用于表示第一切片标识生效的网络域，资源标识用于表示第一网络切片的转发资源。
可选的，域标识可以为全局标识，即域标识表示第一切片标识生效的网络域为承载网中所有的网络域。例如，域标识可以为缺省值0，该缺省值用于表示片标识生效的网络域为承载网中所有的网络域。在域标识表示第一切片标识生效的网络域为承载网中所有的网络域的情况下，资源标识可以为全局有效的资源标识，即承载网中的所有网络域中的网络设备均可以基于该资源标识来转发报文。
可选的，域标识可以为区域标识，即域标识表示第一切片标识生效的网络域为承载网中的部分网络域。例如，在域标识的值为1时，域标识表示第一切片标识生效的网络域为承载网中的第一网络域；在域标识的值为2时，域标识表示第一切片标识生效的网络域为承载网中的第二网络域。在域标识表示第一切片标识生效的网络域为承载网中的部分网络域的情况下，资源标识可以为特定区域有效的资源标识，即资源标识仅在域标识所指示的网络域中生效。
切片标识中包括域标识和资源标识的子标识组合方式可以适用于跨多个网络域的网络切片场景。在该场景下，每个网络域内的网络切片可以使用不同的域标识和资源标识。多个网络域的网络切片拼接组成跨域网络切片。
在一种可能的实现方式中，在切片标识中包括域标识和资源标识的情况下，网络设备基于切片标识转发报文的过程具体如下所述。
位于网络域边界的网络设备接收报文，该报文可以是包括域标识和资源标识。网络设备根据本地维护的映射关系以及报文中的域标识确定当前网络域内有效的域标识和资源标识，并更新报文中的切片标识，或在报文中添加当前网络域内有效的切片标识。然后，网络设备根据报文中的目的IP地址、MPLS标签或SID等指示路径的信息确定报文的目的节点，并根据缺省拓扑和缺省算法确定前往目的节点的接口。最后，网络设备根据资源标识确定使用接口上对应的转发资源来转发报文。
位于网络域内部的网络设备接收到包括域标识和资源标识的报文后，网络设备根据报文中的目的IP地址、MPLS标签或SID等指示路径的信息确定报文的目的节点，并根据缺省拓扑和缺省算法确定前往目的节点的接口。最后，网络设备再根据资源标识确定使用接口上对应的转发资源来转发报文。
场景五：第一切片标识中的多个子标识包括域标识和资源标识，且该多个子标识还包括拓扑标识和算法标识中的一个或多个。
简单来说，在场景五中，第一切片标识中的多个子标识具有多种组合方式。
可以参阅图7，图7为本申请实施例提供的第一切片标识的另一种结构示意图。
在方式一中，第一切片标识中的多个子标识包括域标识、拓扑标识和资源标识。
在方式二中，第一切片标识中的多个子标识包括域标识、算法标识和资源标识。
在方式三中，第一切片标识中的多个子标识包括域标识、拓扑标识、算法标识和资源标识。
其中，域标识、拓扑标识、算法标识和资源标识具体的具体介绍可以参考上述的实施例，在此不再赘述。
图7中所示的多种子标识组合方式可以适用于跨多个网络域的网络切片场景。在该场景下，每个网络域内的网络切片可以使用不同的域标识，且每个网络切片对应的拓扑标识、算法标识和资源标识也可以是不同的。多个网络域的网络切片拼接组成跨域网络切片。
场景六：在场景一至场景五的基础上，第一切片标识中的多个子标识还包括标志位标 识。
简单来说，在场景一至场景五对应的子标识的多种组合方式的基础上，第一切片标识中还包括标志位标识。例如，在场景一的基础上，第一切片标识除了包括拓扑标识和资源标识，第一切片标识还包括标志位标识。又例如，在场景五的方式三的基础上，第一切片标识除了包括域标识、拓扑标识、算法标识和资源标识，第一切片标识还包括标志位标识。可以参阅图8，图8为本申请实施例提供的能够第一切片标识的结构示意图。在图8中，第一切片标识包括域标识、拓扑标识、算法标识、资源标识和标志位标识。
本实施例中，标志位标识用于表示第一切片标识中用于指导转发的子标识以及第一切片标识对应的转发策略。其中，用于指导转发的子标识是指第一切片标识中被网络设备选择来指导转发报文的子标识。用于指导转发的子标识可以是第一切片标识中除标志位标识之外的一个或多个子标识。例如，在第一切片标识包括域标识、拓扑标识、算法标识、资源标识和标志位标识的情况下，用于指导转发的子标识可以为拓扑标识和算法标识；或者，用于指导转发的子标识可以为拓扑标识、算法标识和资源标识。简单来说，标志位标识用于指示网络设备需要采用切片标识中的哪些子标识来执行报文的转发。
标志位标识所表示的转发策略用于指示根据用于指导转发的子标识确定接口后的转发行为。具体来说，转发行为可以是指：若第一网络设备根据第一切片标识无法查找到用于转发的接口，则第一网络设备可以不根据第一切片标识确定用于转发的接口，第一网络设备可以是基于默认的切片来转发报文；或，若第一网络设备根据第一切片标识无法查找到用于转发的接口，则第一网络设备丢弃第一报文。
以上实施例介绍了在网络设备在同一个网络域内执行报文转发的过程，以下将介绍网络设备在跨域场景下执行报文转发的过程。
在跨域场景下，第一网络设备为网络域的边界设备，第一网络设备从其他的网络域接收报文，并对接收到的报文进行更新，以使得更新后的报文中携带上述的第一切片标识。然后，第一网络设备再基于更新后的报文执行报文转发。
为便于理解，以下将分别介绍本实施例中所涉及的多种跨域场景。
跨域场景1：第一网络设备位于承载网中的第一网络域，第一网络设备接收承载网中第二网络域中的网络设备所发送的报文，且该报文中携带有在第二网络域中生效的切片标识。
在跨域场景1中，第一网络设备作为第一网络域和第二网络域的边界节点，第一网络设备对第二网络域接收到的报文进行更新，得到更新后的报文，且更新后的报文所生成的网络域为第一网络域。
示例性地，第一网络设备中预先配置有不同网络域的切片标识之间的映射关系。基于该映射关系，第一网络设备能够将在第二网络域生效的切片标识转换为在第一网络域生效的切片标识。具体地，第一网络设备接收第二网络设备发送的第二报文，第二报文包括第二切片标识，所述第二切片标识包括多个子标识。然后，第一网络设备基于预先配置的映射关系将第二报文中的第二切片标识更新为第一切片标识，得到第一报文。其中，第一切 片标识在第一网络域中生效，用于在第一网络域中指示第一网络切片；第二切片标识在第二网络域中生效，用于在第二网络域中指示第二网络切片。第一网络切片的服务等级协议(Service-Level Agreement，SLA)与第二网络切片的SLA相同，即第一网络切片的网络质量与第二网络切片的网络质量是相同的。最后，第一网络设备根据第一切片标识转发第一报文。
可以参阅图9a，图9a为本申请实施例提供的一种网络域的划分示意图。在图9a中，网络设备1、网络设备2、网络设备3和网络设备4位于第二网络域中；网络设备5、网络设备6、网络设备7和网络设备8位于第一网络域中；网络设备9、网络设备10、网络设备11和网络设备12位于第三网络域中。第一网络域中的网络设备5和网络设备6为域边界节点，网络设备5和网络设备6从第二网络域中接收到报文后，需要对接收到的报文进行更新，以得到在第一网络域中生效的更新后的报文。
在跨域场景下，不同网络域中的网络设备可以是基于不同的子标识组合来转发报文。简单来说，每个网络域中的网络设备都可以根据当前网络域内的转发策略，选择报文中的一个或多个子标识来确定转发报文的接口，从而实现报文的转发。
示例性地，可以参阅图9b，图9b为本申请实施例提供的一种网络域的划分示意图。第二网络域中的网络设备1、网络设备2、网络设备3和网络设备4在转发报文时，选择切片标识中的拓扑标识、算法标识和资源标识来确定报文的接口，并基于得到的接口转发报文。
第一网络域中的网络设备5、网络设备6、网络设备7和网络设备8在转发报文时，选择切片标识中的拓扑标识和算法标识来确定报文的接口，并基于得到的接口转发报文。
第三网络域中的网络设备9、网络设备10、网络设备11和网络设备12在转发报文时，选择切片标识中的算法标识和资源标识来确定报文的接口，并基于得到的接口转发报文。
跨域场景2：第一网络设备为承载网中的边界节点，第一网络设备接收承载网之外的网络中的网络设备所发送的报文，且该报文中携带有全网的切片标识。
在一个可能的示例中，第一网络设备可以接收接入网或核心网中的网络设备所发送的第二报文，该第二报文中携带有第二切片标识，且第二切片标识是在全网中生效的，即第二切片标识在接入网、承载网和核心网中都是生效的。所述第一网络设备将所述第二切片标识更新为所述第一切片标识，得到所述第一报文。
例如，第二切片标识为单网络切片选择支撑信息(Single Network Slice Selection Assistance Information，S-NSSAI)或应用感知网络(Application-Aware Networking，APN)标识。又例如，第二切片标识能够指示第二报文在整个承载网的多个网络域中所属的网络切片，第二切片标识的格式可以是与第一切片标识的格式相同，第二切片标识的格式也可以是与第一切片标识不同。这样，第一网络设备能够将在多个网络域中生效的第二切片标识转换为在第一网络设备所在的网络域生效的第一切片标识。
在另一个可能的示例中，第一网络设备接收第三报文，并确定第三报文所属的网络切片。第一网络设备再根据第三报文所属的网络切片，在第三报文中添加第一切片标识，得 到第一报文。其中，第三报文中包括第三切片标识，所述第三切片标识用于在包括多个网络域的承载网中标识所述第三报文所属的网络切片。第三切片标识可以为S-NSSAI或APN标识，第三切片标识也可以是与第一切片标识的格式相同，第三切片标识中包括多个子标识，第三切片标识能够指示第三报文在整个承载网的多个网络域中所属的网络切片。
简单来说，第三报文中的第三切片标识是承载网中的全局标识，在整个承载网的多个网络域中生效，即第三切片标识能够标识所述第三报文在承载网的多个网络域中所属的网络切片。
因此，第一网络设备可以基于第三切片标识确定第三报文所属的网络切片，从而得到在所述第一网络设备所在的网络域内生效的第一切片标识。然后，第一网络设备在第三报文中添加第一切片标识，得到第一报文，所述第一报文中同时包括第三切片标识以及第一切片标识。
跨域场景3：第一网络设备位于承载网中的网络域，第一网络设备接收该网络域之外的网络设备所发送的报文，且该报文中并不携带有切片标识。
在一个可能的示例中，第一网络设备接收第三报文，并确定第三报文所属的网络切片。第三报文来自于第一网络设备所属的网络域之外的网络设备，且第三报文中不携带切片标识。第一网络设备再根据第三报文所属的网络切片，在第三报文中添加第一切片标识，得到第一报文。
可选的，第一网络设备还可以是根据第三报文所属的网络切片，在第三报文中同时添加第一切片标识和第四切片标识，得到第一报文。其中，所述第四切片标识用于在包括多个网络域的承载网中标识所述第三报文所属的网络切片。也就是说，在第一网络设备所生成的第一报文中包括第一切片标识和第四切片标识。第一切片标识仅在第一网络设备所在的网络域中生效，用于指导第一网络设备所在的网络域内的网络设备转发报文；第四切片标识能够在多个网络域内生效，用于指导网络域的边界节点更新在单个网络域内生效的切片标识。
具体地，在第一网络设备中可以预先配置有用于确定网络切片的策略，第一网络设备可以在该策略的指示下，根据第三报文中的信息，确定第三报文所属的网络切片。其中，第三报文中的信息包括以下信息的一种或多种：源地址、目的地址、协议号、差分服务代码点(Differentiated Services Code Point，DSCP)字段、流量等级(Traffic Class)字段、虚拟局域网标识(Virtual Local Area Network identifier，VLAN ID)和端口号。
其中，源地址例如可以为发送报文的源互联网(Internet Protocol，IP)地址或者源媒体接入控制(Media Access Control，MAC)地址，如用户主机或基站的地址。目的地址例如可以为报文的目的IP地址或目的MAC地址。第一网络设备也可以是根据第三报文中的其他一些字段，来确定第三报文所属的网络切片。例如第三报文中的IPv4或IPv6报文头中的DSCP字段或TC字段，以太头中的VLAN ID等。第一网络设备具体可以是根据上述字段中的某一个字段(例如源地址、目的地址、协议号、DSCP字段或者TC字段等)，或者某几个字段的组合来确定第三报文所属的网络切片。
跨域场景4：第一网络设备位于承载网中的网络域，第一网络设备接收该网络域之外的网络设备所发送的报文，且该报文中包括在多个网络域中生效的切片标识以及仅在第一网络所在的网络域的上一个网络域中生效的切片标识。
示例性地，第一网络设备接收第三报文，并确定第三报文所属的网络切片。第三报文来自于第一网络设备所属的网络域之外的网络设备，且第三报文中携带第三切片标识和第四切片标识这两个切片标识。第三报文中携带的第三切片标识在包括多个网络域的承载网内生效，第四切片标识则仅在第一网络所在的网络域的上一个网络域中生效。
然后，第一网络设备再根据第三切片标识，确定第三报文所属的网络切片，并将第三报文中的第四切片标识更新为第一切片标识，得到包括第三切片标识和第一切片标识的第一报文。
简单来说，在包括多个网络域的承载网中转发的报文中包括两个切片标识，一个切片标识能够在多个网络域内生效，用于指导网络域的边界节点更新在单个网络域内生效的切片标识；另一个切片标识则仅在一个网络域中生效，用于指导当前网络域内网络设备转发报文。
为了实现上述实施例，本申请还提供了一种网络设备。可以参阅图10，图10为本申请实施例提供的一种网络设备1000的结构示意图。
图10所示的网络设备1000尽管示出了某些特定特征，但是本领域的技术人员将从本申请实施例中意识到，为了简洁起见，图10未示出各种其他特征，以免混淆本申请实施例所公开的实施方式的更多相关方面。为此，作为示例，在一些实现方式中，网络设备1000包括一个或多个处理单元(cpu)1001、网络接口1002、编程接口1003、存储器1004和一个或多个通信总线1005，用于将各种组件互连。在另一些实现方式中，网络设备1000也可以在上述示例基础上省略或增加部分功能部件或单元。
在一些实现方式中，网络接口1002除其他用途外，用于在网络系统中和一个或多个其他的网络设备/服务器连接。在一些实现方式中，通信总线1005包括互连和控制系统组件之间的通信的电路。存储器1004可以包括非易失性存储器，例如，只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。存储器1004也可以包括易失性存储器，易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。
在一些实现中，存储器1004或存储器1004的非暂时性计算机可读存储介质存储以下程序、模块和数据结构，或其子集，例如包括收发单元(图中未示出)、获取单元10041和处理单元10042。
在一个可能的实施例中，该网络设备1000可以具有上述图2对应的方法实施例中的网络设备2的任意功能。
应理解，网络设备1000对应于上述方法实施例中的第一网络设备，网络设备1000中的各模块和上述其他操作和/或功能分别为了实现上述方法实施例中的第一网络设备所实 施的各种步骤和方法，具体细节可参见上述图2对应的方法实施例，为了简洁，在此不再赘述。
应理解，以上的收发单元的功能可以是由处理器调用存储器中的程序代码来实现，并在需要时配合网络接口1002；也可以是由网络设备1000上的网络接口1002来完成数据的收发操作。
在各种实现中，网络设备1000用于执行本申请实施例提供的报文处理方法，例如是执行上述图2所示的实施例所对应的报文处理方法。
与本申请提供的方法实施例以及虚拟装置实施例相对应，本申请实施例还提供了一种网络设备，下面对网络设备的硬件结构进行介绍。
可以参阅图11，图11为本申请实施例提供的一种网络设备1100的结构示意图，该网络设备1100可以配置为上述方法实施例中的第一网络设备。
网络设备1100可以对应于上述方法实施例中的第一网络设备，网络设备1100中的各硬件、模块和上述其他操作和/或功能分别为了实现方法实施例中的第一网络设备所实施的各种步骤和方法，关于网络设备1100如何转发报文的详细流程，具体细节可参见上述方法实施例，为了简洁，在此不再赘述。其中，上述图2对应的方法实施例的各步骤通过网络设备1100处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。为避免重复，这里不再详细描述。
网络设备1100也可以对应于上述虚拟装置实施例中的网络设备1100，网络设备1100中的每个功能模块采用网络设备1100的软硬件实现。作为可能的实现方式，网络设备1100包括的功能模块为网络设备1100的处理器读取存储器中存储的程序代码后生成的，或者为网络设备1100的处理器读取存储器中存储的程序代码，以及配合通信接口共同实现的。
网络设备1100包括：主控板1110和接口板1130。
主控板1110也称为主处理单元(main processing unit，MPU)或路由处理卡(route processor card)，主控板1110对网络设备1100中各个组件的控制和管理，包括路由计算、设备管理、设备维护、协议处理功能。主控板1110包括：中央处理器1111和存储器1112。
接口板1130也称为线路接口单元卡(line processing unit，LPU)、线卡(line card)或业务板。接口板1130用于提供各种业务接口并实现数据包的转发。业务接口包括但不限于以太网接口、POS(Packet over SONET/SDH)接口等，以太网接口例如是灵活以太网业务接口(Flexible Ethernet Clients，FlexE Clients)。接口板1130包括：中央处理器1131、网络处理器1132、转发表项存储器1134和物理接口卡(ph11sical interface  card，PIC)1133。
接口板1130上的中央处理器1131用于对接口板1130进行控制管理并与主控板1110上的中央处理器1111进行通信。
网络处理器1132用于实现报文的转发处理。网络处理器1132的形态可以是转发芯片。具体而言，上行报文的处理包括：报文入接口的处理，转发表查找；下行报文的处理：转发表查找等等。
物理接口卡1133用于实现物理层的对接功能，原始的流量由此进入接口板1130，以及处理后的报文从该物理接口卡1133发出。物理接口卡1133包括至少一个物理接口，物理接口也称物理口，物理接口卡1133对应于系统架构中的FlexE物理接口。物理接口卡1133也称为子卡，可安装在接口板1130上，负责将光电信号转换为报文并对报文进行合法性检查后转发给网络处理器1132处理。在一些实施例中，接口板1103的中央处理器1131也可执行网络处理器1132的功能，比如基于通用CPU实现软件转发，从而物理接口卡1133中不需要网络处理器1132。
可选的，网络设备1100包括多个接口板，例如网络设备1100还包括接口板1140，接口板1140包括：中央处理器1141、网络处理器1142、转发表项存储器1144和物理接口卡1143。
可选的，网络设备1100还包括交换网板1120。交换网板1120也可以称为交换网板单元(switch fabric unit，SFU)。在网络设备有多个接口板1130的情况下，交换网板1120用于完成各接口板之间的数据交换。例如，接口板1130和接口板1140之间可以通过交换网板1120通信。
主控板1110和接口板1130耦合。例如，主控板1110、接口板1130和接口板1140，以及交换网板1120之间通过系统总线与系统背板相连实现互通。在一种可能的实现方式中，主控板1110和接口板1130之间建立进程间通信协议(inter-process communication，IPC)通道，主控板1110和接口板1130之间通过IPC通道进行通信。
在逻辑上，网络设备1100包括控制面和转发面，控制面包括主控板1110和中央处理器1131，转发面包括执行转发的各个组件，比如转发表项存储器1134、物理接口卡1133和网络处理器1132。控制面执行路由器、生成转发表、处理信令和协议报文、配置与维护设备的状态等功能，控制面将生成的转发表下发给转发面，在转发面，网络处理器1132基于控制面下发的转发表对物理接口卡1133收到的报文查表转发。控制面下发的转发表可以保存在转发表项存储器1134中。在有些实施例中，控制面和转发面可以完全分离，不在同一设备上。
应理解，网络设备1100中的收发单元可以相当于网络设备1100中的物理接口卡1133或物理接口卡1143；网络设备1100中的获取单元11041和处理单元11042可以相当于网络设备1100中的中央处理器1111或中央处理器1131。
应理解，本申请实施例中接口板1140上的操作与接口板1130的操作一致，为了简洁，不再赘述。应理解，本实施例的网络设备1100可对应于上述各个方法实施例中的第一网络设备，该网络设备1100中的主控板1110、接口板1130和/或接口板1140可以实现 上述各个方法实施例中的第一网络设备所具有的功能和/或所实施的各种步骤，为了简洁，在此不再赘述。
值得说明的是，主控板可能有一块或多块，有多块的时候可以包括主用主控板和备用主控板。接口板可能有一块或多块，网络设备的数据处理能力越强，提供的接口板越多。接口板上的物理接口卡也可以有一块或多块。交换网板可能没有，也可能有一块或多块，有多块的时候可以共同实现负荷分担冗余备份。在集中式转发架构下，网络设备可以不需要交换网板，接口板承担整个系统的业务数据的处理功能。在分布式转发架构下，网络设备可以有至少一块交换网板，通过交换网板实现多块接口板之间的数据交换，提供大容量的数据交换和处理能力。所以，分布式架构的网络设备的数据接入和处理能力要大于集中式架构的设备。可选的，网络设备的形态也可以是只有一块板卡，即没有交换网板，接口板和主控板的功能集成在该一块板卡上，此时接口板上的中央处理器和主控板上的中央处理器在该一块板卡上可以合并为一个中央处理器，执行两者叠加后的功能，这种形态设备的数据交换和处理能力较低(例如，低端交换机或路由器等网络设备)。具体采用哪种架构，取决于具体的组网部署场景，此处不做唯一限定。
在一些可能的实施例中，上述第一网络设备可以实现为虚拟化设备。例如，虚拟化设备可以是运行有用于发送报文功能的程序的虚拟机(英文：Virtual Machine，VM)，虚拟机部署在硬件设备上(例如，物理服务器)。虚拟机指通过软件模拟的具有完整硬件系统功能的、运行在一个完全隔离环境中的完整计算机系统。可以将虚拟机配置为第一网络设备。例如，可以基于通用的物理服务器结合网络功能虚拟化(Network Functions Virtualization，NFV)技术来实现第一网络设备。第一网络设备为虚拟主机、虚拟路由器或虚拟交换机。本领域技术人员通过阅读本申请即可结合NFV技术在通用物理服务器上虚拟出具有上述功能的第一网络设备。此处不再赘述。
应理解，上述各种产品形态的网络设备，分别具有上述方法实施例中第一网络设备的任意功能，此处不再赘述。
本申请实施例提供了一种计算机程序产品，当该计算机程序产品在网络设备上运行时，使得网络设备执行上述图2对应的方法实施例中网络设备2执行的方法。
参见图12，本申请实施例提供了一种网络系统1200，系统1200包括：网络设备1201、网络设备1202和网络设备1203。网络设备1201分别与网络设备1202和网络设备1203连接。可选的，网络设备1201可以为图2对应的方法实施例中的第一网络设备。
本申请实施例还提供了一种芯片，包括处理器和接口电路，接口电路，用于接收指令并传输至处理器。其中，所述处理器与存储器耦合，所述存储器用于存储程序或指令，当所述程序或指令被所述处理器执行时，使得该芯片系统实现上述任一方法实施例中的方法。
可选的，该芯片系统中的处理器可以为一个或多个。该处理器可以通过硬件实现也可以通过软件实现。当通过硬件实现时，该处理器可以是逻辑电路、集成电路等。当通过软 件实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现。
可选的，该芯片系统中的存储器也可以为一个或多个。该存储器可以与处理器集成在一起，也可以和处理器分离设置，本申请并不限定。示例性的，存储器可以是非瞬时性处理器，例如只读存储器ROM，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请对存储器的类型，以及存储器与处理器的设置方式不作具体限定。
示例性的，该芯片系统可以是现场可编程门阵列(field programmable gate array，FPGA)，可以是专用集成芯片(application specific integrated circuit，ASIC)，还可以是系统芯片(system on chip，SoC)，还可以是中央处理器(central processor unit，CPU)，还可以是网络处理器(network processor，NP)，还可以是数字信号处理电路(digital signal processor，DSP)，还可以是微控制器(micro controller unit，MCU)，还可以是可编程控制器(programmable logic device，PLD)或其他集成芯片。
以上对本申请实施例进行了详细介绍，本申请实施例方法中的步骤可以根据实际需要进行顺序调度、合并或删减；本申请实施例装置中的模块可以根据实际需要进行划分、合并或删减。
应理解，说明书通篇中提到的“一个实施例”或“一实施例”意味着与实施例有关的特定特征、结构或特性包括在本申请的至少一个实施例中。因此，在整个说明书各处出现的“在一个实施例中”或“在一实施例中”未必一定指相同的实施例。此外，这些特定的特征、结构或特性可以任意适合的方式结合在一个或多个实施例中。应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
应理解，在本申请实施例中，“与A相应的B”表示B与A相关联，根据A可以确定B。但还应理解，根据A确定B并不意味着仅仅根据A确定B，还可以根据A和/或其它信息确定B。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、计算机软件或者二者的结合来实现，为了清楚地说明硬件和软件的可互换性，在上述说明中已经按照功能一般性地描述了各示例的组成及步骤。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统，装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统，装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件 可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备/服务器等)执行本申请各个实施例方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器、随机存取存储器、磁碟或者光盘等各种可以存储程序代码的介质。

Claims (20)

  1. 一种报文处理方法，其特征在于，包括：
    第一网络设备获取第一报文，所述第一报文包括第一切片标识，所述第一切片标识包括连续的多个子标识，所述多个子标识用于表示第一网络切片不同的属性，所述第一切片标识用于标识所述第一报文所属的第一网络切片；
    所述第一网络设备根据所述第一切片标识转发所述第一报文。
  2. 根据权利要求1所述的方法，其特征在于，所述多个子标识包括拓扑标识和资源标识，所述拓扑标识用于表示所述第一网络切片的拓扑，所述资源标识用于表示所述第一网络切片的转发资源。
  3. 根据权利要求2所述的方法，其特征在于，所述多个子标识还包括算法标识，所述算法标识用于表示所述第一网络切片的算路算法。
  4. 根据权利要求1所述的方法，其特征在于，所述多个子标识包括算法标识和资源标识，所述算法标识用于表示所述第一网络切片的算路算法，所述资源标识用于表示所述第一网络切片的转发资源。
  5. 根据权利要求2-4任意一项所述的方法，其特征在于，所述多个子标识还包括域标识，所述域标识用于表示所述第一切片标识生效的网络域。
  6. 根据权利要求1所述的方法，其特征在于，所述多个子标识包括域标识和资源标识，所述域标识用于表示所述第一切片标识生效的网络域，所述资源标识用于表示所述第一网络切片的转发资源。
  7. 根据权利要求1-6任意一项所述的方法，其特征在于，所述转发资源包括物理接口、逻辑子接口和/或报文队列。
  8. 根据权利要求1-7任意一项所述的方法，其特征在于，所述第一网络设备根据所述第一切片标识转发所述第一报文，包括：
    所述第一网络设备根据所述第一切片标识中的子标识以及映射表，确定用于转发所述第一报文的接口以及所述接口的转发资源；
    所述第一网络设备根据所述接口的转发资源向第二网络设备转发所述第一报文；
    其中，所述映射表包括所述多个子标识与接口之间的映射关系。
  9. 根据权利要求1-8任意一项所述的方法，其特征在于，所述多个子标识还包括标志位标识，所述标志位标识用于表示所述第一切片标识对应的转发策略，所述转发策略用于 指示根据用于指导转发的子标识确定接口后的转发行为。
  10. 根据权利要求9所述的方法，其特征在于，所述转发行为包括：若根据所述第一切片标识无法查找到用于转发的接口，则不根据所述第一切片标识确定用于转发的接口；
    或，若根据所述第一切片标识无法查找到用于转发的接口，则丢弃所述第一报文。
  11. 根据权利要求1-10任意一项所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备接收第二报文，所述第二报文包括第二切片标识；
    所述第一网络设备将所述第二切片标识更新为所述第一切片标识，得到所述第一报文。
  12. 根据权利要求11所述的方法，其特征在于，所述第一切片标识用于在第一网络域中指示所述第一网络切片，所述第二切片标识用于在第二网络域中指示第二网络切片，所述第一网络切片的服务等级协议SLA与所述第二网络切片的SLA相同。
  13. 根据权利要求11所述的方法，其特征在于，所述第一网络设备为承载网的边界节点，所述第二切片标识为单网络切片选择支撑信息S-NSSAI或应用感知网络APN标识。
  14. 根据权利要求1-10任意一项所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备接收第三报文；
    所述第一网络设备确定所述第三报文所属的网络切片；
    所述第一网络设备根据所述第三报文所属的网络切片，在所述第三报文中添加所述第一切片标识，得到所述第一报文。
  15. 根据权利要求14所述的方法，其特征在于，所述第一网络设备确定所述第三报文所属的网络切片，包括：
    所述第一网络设备根据所述第三报文中的信息，确定所述第三报文所属的网络切片；
    其中，所述第三报文中的信息包括以下信息的一种或多种：源地址、目的地址、协议号、差分服务代码点DSCP字段、流量等级TC字段、虚拟局域网标识和端口号。
  16. 根据权利要求14或15所述的方法，其特征在于，所述第一网络设备根据所述第三报文所属的网络切片，在所述第三报文中添加所述第一切片标识，包括：
    所述第一网络设备根据所述第三报文所属的网络切片，在所述第三报文中添加所述第一切片标识和第四切片标识，得到所述第一报文；
    所述第四切片标识用于在包括多个网络域的承载网中标识所述第三报文所属的网络切片。
  17. 根据权利要求14所述的方法，其特征在于，所述第一网络设备确定所述第三报文 所属的网络切片，包括：
    所述第一网络设备根据所述第三报文中的第三切片标识，确定所述第三报文所属的网络切片；
    其中，所述第三切片标识用于在包括多个网络域的承载网中标识所述第三报文所属的网络切片。
  18. 一种网络设备，其特征在于，包括：处理器和存储器；所述存储器用于存储指令；所述处理器用于执行存储器中的指令，使得所述网络设备执行如权利要求1至17任意一项所述的方法。
  19. 一种计算机可读存储介质，其特征在于，所述计算机存储介质中存储有计算机可读指令，当所述计算机可读指令被处理器执行时实现如权利要求1至17任意一项所述的方法。
  20. 一种计算机程序产品，其特征在于，所述计算机程序产品中存储有计算机可读指令，当所述计算机可读指令被处理器执行时实现如权利要求1至17任意一项所述的方法。
PCT/CN2021/141540 2021-02-02 2021-12-27 一种报文处理方法及相关装置 WO2022166465A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP21924458.9A EP4270897A4 (en) 2021-02-02 2021-12-27 MESSAGE PROCESSING METHOD AND ASSOCIATED APPARATUS
KR1020237027873A KR20230128564A (ko) 2021-02-02 2021-12-27 패킷 처리 방법 및 관련 장치
JP2023546511A JP2024504845A (ja) 2021-02-02 2021-12-27 パケット処理方法および関連装置
US18/228,503 US20230412508A1 (en) 2021-02-02 2023-07-31 Packet processing method and related apparatus

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202110143450 2021-02-02
CN202110143450.6 2021-02-02
CN202110461985.8 2021-04-27
CN202110461985.8A CN114844962A (zh) 2021-02-02 2021-04-27 一种报文处理方法及相关装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/228,503 Continuation US20230412508A1 (en) 2021-02-02 2023-07-31 Packet processing method and related apparatus

Publications (1)

Publication Number Publication Date
WO2022166465A1 true WO2022166465A1 (zh) 2022-08-11

Family

ID=82562498

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/141540 WO2022166465A1 (zh) 2021-02-02 2021-12-27 一种报文处理方法及相关装置

Country Status (6)

Country Link
US (1) US20230412508A1 (zh)
EP (1) EP4270897A4 (zh)
JP (1) JP2024504845A (zh)
KR (1) KR20230128564A (zh)
CN (1) CN114844962A (zh)
WO (1) WO2022166465A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117041259A (zh) * 2023-09-28 2023-11-10 新华三技术有限公司 计算资源的调度方法及装置
WO2024147477A1 (ko) * 2023-01-03 2024-07-11 삼성전자주식회사 네트워크 슬라이스에 대한 자원을 식별하기 위한 방법 및 장치

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116761208A (zh) * 2020-03-17 2023-09-15 华为技术有限公司 报文处理方法、装置、设备及存储介质
CN119011337A (zh) * 2023-05-19 2024-11-22 华为技术有限公司 报文转发方法、装置及系统
CN118677858B (zh) * 2024-08-19 2024-11-08 北京开源芯片研究院 一种数据转递方法、装置、电子设备及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107517488A (zh) * 2016-06-15 2017-12-26 华为技术有限公司 报文处理的方法及设备
US20190141760A1 (en) * 2015-11-18 2019-05-09 Telefonaktiebolaget Lm Ericsson (Publ) First Network Node, Receiving Network Node and Methods Performed Therein
CN110912795A (zh) * 2018-09-14 2020-03-24 中兴通讯股份有限公司 一种传输控制方法、节点、网络系统及存储介质
CN111050361A (zh) * 2018-10-12 2020-04-21 中国移动通信有限公司研究院 一种报文传送方法、装置及系统
CN111835637A (zh) * 2019-04-15 2020-10-27 华为技术有限公司 一种基于SRv6的数据处理方法及相关网络设备

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107659419B (zh) * 2016-07-25 2021-01-01 华为技术有限公司 网络切片方法和系统
US11588733B2 (en) * 2019-05-14 2023-02-21 Vmware, Inc. Slice-based routing

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190141760A1 (en) * 2015-11-18 2019-05-09 Telefonaktiebolaget Lm Ericsson (Publ) First Network Node, Receiving Network Node and Methods Performed Therein
CN107517488A (zh) * 2016-06-15 2017-12-26 华为技术有限公司 报文处理的方法及设备
CN110912795A (zh) * 2018-09-14 2020-03-24 中兴通讯股份有限公司 一种传输控制方法、节点、网络系统及存储介质
CN111050361A (zh) * 2018-10-12 2020-04-21 中国移动通信有限公司研究院 一种报文传送方法、装置及系统
CN111835637A (zh) * 2019-04-15 2020-10-27 华为技术有限公司 一种基于SRv6的数据处理方法及相关网络设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4270897A4

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024147477A1 (ko) * 2023-01-03 2024-07-11 삼성전자주식회사 네트워크 슬라이스에 대한 자원을 식별하기 위한 방법 및 장치
CN117041259A (zh) * 2023-09-28 2023-11-10 新华三技术有限公司 计算资源的调度方法及装置
CN117041259B (zh) * 2023-09-28 2024-01-12 新华三技术有限公司 计算资源的调度方法及装置

Also Published As

Publication number Publication date
KR20230128564A (ko) 2023-09-05
US20230412508A1 (en) 2023-12-21
EP4270897A4 (en) 2024-05-29
EP4270897A1 (en) 2023-11-01
JP2024504845A (ja) 2024-02-01
CN114844962A (zh) 2022-08-02

Similar Documents

Publication Publication Date Title
WO2022166465A1 (zh) 一种报文处理方法及相关装置
JP2022532729A (ja) スライスベースルーティング
CN113973082A (zh) 一种报文处理方法及网络设备
US11663052B2 (en) Adaptive application assignment to distributed cloud resources
US20220255862A1 (en) Packet forwarding method, device, storage medium, and system
WO2021143279A1 (zh) 段路由业务处理方法和装置、路由设备及存储介质
WO2022222750A1 (zh) 报文转发方法、装置、网络设备及存储介质
CN113395735A (zh) 一种报文传输方法、装置和网络设备
CN111654441A (zh) 伪线负载分担的方法和设备
WO2022048418A1 (zh) 一种转发报文的方法、设备和系统
US20230155930A1 (en) Packet Processing Method and Network Device
WO2022188530A1 (zh) 一种路由处理方法及网络设备
CN112822097A (zh) 报文转发的方法、第一网络设备以及第一设备组
CN114301839A (zh) 一种组播报文传输方法及装置
US20230224236A1 (en) Routing Information Transmission Method and Apparatus
CN112751766A (zh) 报文转发方法、装置及计算机存储介质
WO2023213216A1 (zh) 一种报文处理的方法及相关设备
CN114338518B (zh) 一种路由处理方法及网络设备
CN117097818A (zh) 一种报文处理的方法及相关设备
JP2023538688A (ja) 通信方法および関連装置
CN115811499A (zh) 指定转发者df选举的方法及设备
WO2022143572A1 (zh) 一种报文处理方法及相关设备
CN114697220B (zh) 一种报文处理方法及相关装置
EP4525400A1 (en) Message sending method, network device and system
WO2024002101A1 (zh) 报文传输方法、装置、相关设备及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21924458

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2023546511

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 202317052000

Country of ref document: IN

ENP Entry into the national phase

Ref document number: 2021924458

Country of ref document: EP

Effective date: 20230726

ENP Entry into the national phase

Ref document number: 20237027873

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 1020237027873

Country of ref document: KR

NENP Non-entry into the national phase

Ref country code: DE