WO2024087691A1 - 一种报文处理方法及相关设备 - Google Patents

一种报文处理方法及相关设备 Download PDF

Info

Publication number
WO2024087691A1
WO2024087691A1 PCT/CN2023/103105 CN2023103105W WO2024087691A1 WO 2024087691 A1 WO2024087691 A1 WO 2024087691A1 CN 2023103105 W CN2023103105 W CN 2023103105W WO 2024087691 A1 WO2024087691 A1 WO 2024087691A1
Authority
WO
WIPO (PCT)
Prior art keywords
slice
message
network
network device
information
Prior art date
Application number
PCT/CN2023/103105
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 华为技术有限公司
Publication of WO2024087691A1 publication Critical patent/WO2024087691A1/zh

Links

Classifications

    • 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/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
    • 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/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements

Definitions

  • the present application relates to the field of communication technology, and in particular to a message processing method and related equipment.
  • multiple slices are deployed on the interfaces of network devices, and sufficient resources are reserved for each slice to ensure that the network can carry services well.
  • traffic carries a slice identity (slice ID), and the network device uses the resources reserved for the slice corresponding to the slice ID to forward the traffic, thereby ensuring the service quality of the traffic.
  • slice ID slice identity
  • the network device uses the resources reserved for the slice corresponding to the slice ID to forward the traffic, thereby ensuring the service quality of the traffic.
  • the slice corresponding to the slice ID in the traffic fails, the traffic is switched to a public channel by default.
  • the public channel uses the remaining resources after allocating resources to the network slice to forward the traffic. This method cannot guarantee the service quality of the traffic and affects the service experience.
  • the present application provides a message processing method and related equipment, which can switch the traffic to the protection slice of the slice when a slice fails, solving the service guarantee problem in the slice failure scenario.
  • the present application provides a message processing method, which may include, for example: a network device obtains a first message including first slice information and second slice information, the first slice information indicates the first network slice, and the second slice information indicates the second network slice; when determining that the first network slice fails, the network device uses the second network slice to forward the first message.
  • a network device obtains a first message including first slice information and second slice information, the first slice information indicates the first network slice, and the second slice information indicates the second network slice; when determining that the first network slice fails, the network device uses the second network slice to forward the first message.
  • the network device determines that the main slice fails, it can easily obtain the slice information indicating the protection slice from the message, and use the resources on the protection slice corresponding to the main slice to forward the message.
  • the method provided in the embodiment of the present application can guarantee the service quality of the service when the main slice fails, and guarantee the service experience.
  • the "failure" of the first network slice may refer to the unavailability of the first network slice or the congestion of the first network slice.
  • the “failure of the first network slice” may refer to the failure of the primary slice (i.e., the first network slice) on the primary interface of the first message on the network device on the forwarding path of the first message determined by the network device.
  • each primary path in the network may be configured with at least one backup path. When the determined primary path of the first message fails, the first message can be imported into the backup path corresponding to the primary path to ensure normal service provision.
  • the "failure of the first network slice” may also refer to the network device determining that the primary path of the first message fails, and importing the first message into a backup path of the primary path, while the first network slice is not deployed on the backup path, or the first network slice deployed on the backup path also fails.
  • the method may further include: the network device obtains a second message including the first slice information and the second slice information, and the destination of the first message and the second message are the same; if the first network slice is normal, then the network device determines the first output interface and the first next hop according to the first slice information; thereby, the network device sends the second message from the first output interface to the first next hop.
  • the network device forwards the first message using the second network slice, which may include: the network device determines the second output interface and the second next hop according to the second slice information; thereby, the network device sends the first message from the second output interface to the second next hop.
  • the second next hop and the first next hop may be the same or different, and the first output interface and the second output interface may be the same or different. In this way, it can be ensured that messages with the same destination and including slice information are effectively forwarded, and the quality of service during message forwarding is correspondingly guaranteed.
  • the first message may be a Segment Routing Internet Protocol version 6 (SRv6) message, and the first message may carry the second slice information through an Internet Protocol version 6 (IPv6) extension header.
  • SRv6 Segment Routing Internet Protocol version 6
  • IPv6 Internet Protocol version 6
  • the first packet may carry the second slice information via a hop-by-hop (HBH) header.
  • the first message may carry the second slice information through the Virtual Transport Network Option (VTN Option) of the HBH header.
  • VTN Option Virtual Transport Network Option
  • the first message may also carry the second slice information through the VTN Protection Option extended by the HBH header.
  • the first message may carry the second slice information through a Slice Protection Option extended by a Destination Options Header (DOH).
  • DOH Destination Options Header
  • the first message may be a Segment Routing Multi-Protocol Label Switching (SR MPLS) message.
  • SR MPLS Segment Routing Multi-Protocol Label Switching
  • the first message may carry the second slice information via an MPLS label.
  • the first message may carry the second slice information via a VTN Protection ID of an MPLS VTN extension header.
  • the first message may also carry the second slice information through an extension header after the MPLS label stack.
  • MPLS Label Stack For example, after the label stack (MPLS Label Stack) in the first message, there are multiple available Extension Headers, and the first message may use any unused Extension Header to carry the second slice information.
  • the method may also include a process in which the network device obtains first slice information and second slice information.
  • the network device obtains the first slice information and the second slice information, which may be that the network device locally configures the first slice information and the second slice information.
  • the network device obtains the first slice information and the second slice information, or the network device receives a control message sent by the control entity, and the control message includes the first slice information and the second slice information.
  • the control message is a Border Gateway Protocol update (BGP update) message or a Path Computation Element Communication Protocol (PCEP) message.
  • BGP update Border Gateway Protocol update
  • PCEP Path Computation Element Communication Protocol
  • the control entity may extend the BGP update message containing the forwarding path related information of the first slice information (such as the Slice ID of the first network slice), for example, by adding a protection slice information (such as a Protection Slice ID) field in the BGP update message, and carrying the second slice information in the protection slice information field.
  • a protection slice information such as a Protection Slice ID
  • control entity may expand the PCEP message containing forwarding path related information of the first slice information (such as the Slice ID of the first network slice), for example, by adding a Protection Slice ID field to the PCEP message and carrying the second slice information in the Protection Slice ID field.
  • first slice information such as the Slice ID of the first network slice
  • the network device after the network device obtains the first slice information and the second slice information, the network device creates a protection slice (i.e., the second network slice) corresponding to the first network slice, which may include: Method 1, pre-allocating resources for the protection slice, that is, after the network device obtains the first slice information and the second slice information, before using the second network slice, the network device allocates resources for the second network slice.
  • Method 1 pre-allocating resources for the protection slice, that is, after the network device obtains the first slice information and the second slice information, before using the second network slice, the network device allocates resources for the second network slice.
  • Method 2 dynamically triggering the deployment of resources for the protection slice, that is, after the network device obtains the first slice information and the second slice information, only deploying the second network slice without allocating resources for the second network slice, and when it is determined that the first network slice protected by the second network slice is faulty, dynamically triggering the allocation of resources for the second network slice; when the first network slice fault is repaired, the resources of the second network slice are recovered.
  • Method 1 pre-allocates resources for the protection slice, so that the service can be imported into the protection slice in time when the main slice fails, which provides sufficient preparation for ensuring the service quality of the service.
  • Method 2 dynamically allocates resources for the protection slice, and triggers the allocation of corresponding resources to the protection slice only when the active slice fails, and triggers the recovery of the resources allocated to the protection slice when the main slice returns to normal, so as to achieve the purpose of resource allocation on demand and improve resource utilization.
  • a multi-level protection mechanism may be set, for example, the second network slice is set as the protection slice of the first network slice, and the third network slice is set as the protection slice of the second network slice.
  • the first message may also include third slice information, and the third slice information indicates the third network slice.
  • the network device uses the second network slice to forward the first message, for example, it may include: when the first network slice failure and the second network slice failure are determined, the network device uses the third network slice to forward the first message. In this way, through the multi-level protection mechanism, the slice network can more reliably guarantee the service quality of the business.
  • a mutual protection relationship between network slices can also be set.
  • the second network slice and the first network slice are each other's protection slices.
  • the method may also include: the network device obtains a third message, the third message includes the first slice information and the second slice information, and the second network slice in the third message is the main slice; when it is determined that the second network slice fails, the network device uses the first network slice to forward the third message. In this way, not only can the service quality of the services carried by each network slice be guaranteed, but also the resource utilization can be improved to a certain extent.
  • multiple primary slices that meet the conditions can be allocated.
  • the same protection slice is allocated to two main slices) of the first network slice, for example, the second network slice is not only the protection slice of the first network slice, but also the protection slice of the fourth network slice.
  • the method may also include: the network device obtains a fourth message, the fourth message includes fourth slice information and second slice information, and the fourth slice information indicates the fourth network slice; when determining that the fourth network slice fails, the network device uses the second network slice to forward the fourth message. In this way, since the probability of the first network slice and the fourth network slice failing at the same time is low, this embodiment can also ensure the service quality of the services carried by each network slice, and also improve resource utilization to a certain extent.
  • the protected network slice can be at the same level as the protecting slice, for example, both are main slices or sub-slices; or, the protected network slice can also be a sub-slice of the protecting slice, for example, the first network slice is a sub-slice of the second network slice.
  • the present application also provides a message processing method, which may include, for example: a network device obtains a first message including first slice information, the first slice information indicating a first network slice; when determining that the first network slice fails, the network device determines the second slice information according to the first slice information and the mapping relationship, the mapping relationship includes the corresponding relationship between the first slice information and the second slice information, and the second slice information indicates the second network slice; the network device uses the second network slice to forward the first message.
  • the resources on the protection slice are isolated resources, and there is no need to expand the message of the service to carry the slice information of the protection slice, but through the corresponding relationship between the slice information of the main slice and the slice information of the protection slice maintained locally, the purpose of using the protection slice to forward the message when the network device determines that the main slice fails is achieved.
  • the method provided in the embodiment of the present application can guarantee the service quality of the service when the main slice fails, and guarantee the service experience.
  • the message received by the network device may also include indication information. If the first message is an SRv6 message, and the VTN Option of the HBH header in the SRv6 message is used to carry the first slice information, then the first flag bit may be any undefined flag bit in the VTN Option of the HBH header, such as any one of the 7 undefined flag bits in the Flags of the VTN Option, or any bit in the Reserved field of the VTN Option.
  • the indication information is used to indicate whether to perform slice protection on the first network slice.
  • the indication information in the first message may include a first value of a first flag bit, the first flag bit is used to indicate whether slice protection needs to be performed, and the first flag bit is a first value used to indicate that slice protection needs to be performed. Then, when determining the failure of the first network slice, the network device determines the second slice information according to the first slice information and the mapping relationship, for example, it may include: the network device determines the need to perform slice protection based on the first value of the first flag bit in the first message; the network device obtains the second network slice corresponding to the first slice information from the locally stored mapping relationship.
  • the indication information in the message received by the network device may also include the fourth value of the first flag bit.
  • the main slice of the message is the first network slice
  • the protection slice is the second network slice. Then, when the network device determines that the first network slice fails, the network device can import the first message into the public channel for subsequent transmission based on the current implementation method.
  • the indication information may also be used to indicate whether to refresh the slice information.
  • the indication information in the first message may also include a second flag bit, the second flag bit is used to indicate whether the slice information needs to be refreshed, the second flag bit is a second value used to indicate that the slice information needs to be refreshed, and the second flag bit is a third value used to indicate that the slice information does not need to be refreshed.
  • the network device uses the second network slice to forward the first message, which may include: the network device replaces the first slice information in the first message with the second slice information to obtain the second message; the network device uses the second network slice to forward the second message.
  • the network device uses the second network slice to forward the first message, which may include: the network device obtains the indication information in the first message, determines that the indication information indicates that the first network slice needs to be slice protected but the slice information does not need to be refreshed, and then, uses the second network slice to forward the first message.
  • the method may further include: the network device obtains the first slice information and the second slice information of the network device; the network device saves the correspondence between the first slice information and the second slice information in a mapping relationship.
  • the network device obtains the first slice information and the second slice information, which may be the first slice information and the second slice information obtained by the configuration on the network device, or the network device receives a control message sent by a control entity, the control message including the first slice information and the second slice information.
  • the control message may be a BGP update message or a PCEP message.
  • the network device may create a protection slice (i.e., the second network slice) corresponding to the first network slice in a manner that: Method 1, pre-allocating resources of the protection slice, i.e., after the network device obtains the first slice information and the second slice information, After obtaining the first slice information and the second slice information, the network device allocates resources to the second network slice before using the second network slice.
  • Method 2 Dynamically trigger the deployment of resources to protect the slice, that is, after the network device obtains the first slice information and the second slice information, it only deploys the second network slice without allocating resources to the second network slice. When it is determined that the first network slice protected by the second network slice has a fault, it dynamically triggers the allocation of resources to the second network slice; when the fault of the first network slice is repaired, the resources of the second network slice are recovered.
  • a multi-level protection mechanism may be set up, for example, the second network slice is set as a protection slice of the first network slice, and the third network slice is set as a protection slice of the second network slice.
  • a mutual protection relationship between network slices may also be set.
  • the second network slice and the first network slice are each other's protection slices.
  • the same protection slice can be assigned to multiple qualified primary slices (such as multiple primary slices belonging to the same tenant).
  • the second network slice is not only a protection slice for the first network slice, but also a protection slice for the fourth network slice.
  • the present application also provides a message processing device, which is applied to a network device, and the device may include, for example: a receiving unit and a sending unit.
  • the receiving unit is used to obtain a first message, the first message includes first slice information and second slice information, the first slice information indicates a first network slice, and the second slice information indicates a second network slice; the sending unit is used to forward the first message using the second network slice when determining that the first network slice fails.
  • the device further includes: a processing unit.
  • the receiving unit is further configured to obtain a second message before obtaining the first message, wherein the second message includes the first slice information and the second slice information, and the first message and the second message have the same destination;
  • the processing unit is configured to determine a first output interface and a first next hop according to the first slice information;
  • the sending unit is further configured to send the second message from the first output interface to the first next hop.
  • the sending unit is specifically used to: determine a second output interface and a second next hop based on the second slice information; and send the first message from the second output interface to the second next hop.
  • the first message is an SRv6 message
  • the first message carries the second slice information via an IPv6 extension header.
  • the first message carries the second slice information through the VTN Option of the HBH header; or, the first message carries the second slice information through the VTN Protection Option of the HBH header.
  • the first message carries the second slice information through the Slice Protection Option of DOH.
  • the first message is an SR MPLS message.
  • the first message carries the second slice information through an MPLS label, or the first message carries the second slice information through an extension header after an MPLS label stack.
  • the receiving unit is further configured to receive a control message sent by a control entity before obtaining the first message, wherein the control message includes the first slice information and the second slice information.
  • the control message is a BGP update message or a PCEP message.
  • the apparatus further includes: a processing unit.
  • the processing unit is configured to allocate resources to the second network slice after receiving a control message sent by the control entity and before using the second network slice to forward the first message when determining that the first network slice is faulty.
  • the sending unit is specifically used to: when it is determined that the first network slice fails, allocate resources to the second network slice, and use the second network slice to forward the first message.
  • the first message also includes third slice information, and the third slice information indicates a third network slice.
  • the sending unit is specifically used to: when determining that the first network slice fails and the second network slice fails, use the third network slice to forward the first message.
  • the receiving unit is further used to obtain a third message, wherein the third message includes the first slice information and the second slice information; the sending unit is further used to use the first network slice to forward the third message when it is determined that the second network slice fails.
  • the receiving unit is further used to obtain a fourth message, wherein the fourth message includes fourth slice information and the second slice information, and the fourth slice information indicates a fourth network slice; the sending unit is further used to use the second network slice to forward the fourth message when it is determined that the fourth network slice fails.
  • the first network slice is a sub-slice of the second network slice.
  • the present application also provides a message processing device, which is applied to a network device, and the device may include: a receiving unit, a processing unit, and a sending unit.
  • the receiving unit is used to obtain a first message, the first message includes first slice information, and the first slice identifier indicates the first network slice;
  • the processing unit is used to determine the second slice information according to the first slice information and the mapping relationship when determining that the first network slice fails, the mapping relationship includes the corresponding relationship between the first slice information and the second slice information, and the second slice information indicates the second network slice;
  • the sending unit is used to forward the first message using the second network slice.
  • the first message also includes indication information, and the indication information is used to indicate slice protection for the first network slice.
  • the indication information includes a first value of a first flag bit, where the first flag bit is used to indicate whether slice protection needs to be performed, and the first flag bit is the first value used to indicate that slice protection needs to be performed.
  • the processing unit is specifically used to: determine the need to perform slice protection based on the first value of the first flag bit in the first message; and obtain the second network slice corresponding to the first slice information from the mapping relationship stored locally.
  • the indication information is also used to indicate whether to refresh the slice information.
  • the indication information also includes a second flag bit, the second flag bit is used to indicate whether the slice information needs to be refreshed, the second flag bit is a second value used to indicate that the slice information needs to be refreshed, and the second flag bit is a third value used to indicate that the slice information does not need to be refreshed.
  • the sending unit is specifically used to: replace the first slice information in the first message with the second slice information to obtain a second message; and use the second network slice to forward the second message.
  • the first message may be an SRv6 message, and the first message carries the indication information through the VTN Option of the HBH header.
  • the receiving unit is further configured to receive a control message sent by a control entity before obtaining the first message, wherein the control message includes the first slice information and the second slice information; and the processing unit is further configured to save the correspondence between the first slice information and the second slice information in the mapping relationship.
  • the control message may be a BGP update message or a PCEP message.
  • the present application provides a network device, comprising a processor and a memory, the memory being used to store instructions or program codes, and the processor being used to call and run the instructions or program codes from the memory to execute the method in the first aspect, any possible implementation of the first aspect, the second aspect, or any possible implementation of the second aspect.
  • the present application provides a computer-readable storage medium, characterized in that it includes instructions, programs or codes, which, when executed on a computer, enable the computer to execute the method in the first aspect, any possible implementation of the first aspect, the second aspect or any possible implementation of the second aspect.
  • the present application provides a computer program product.
  • the computer program product runs on a network device
  • the network device executes the method in the first aspect, any possible implementation of the first aspect, the second aspect, or any possible implementation of the second aspect.
  • FIG1 is a schematic diagram of a slicing network scenario in an embodiment of the present application.
  • FIG2a is a schematic diagram of current message processing in a situation in the scenario of FIG1 according to an embodiment of the present application;
  • FIG2b is a schematic diagram of a first possible implementation method in a situation in the scenario of FIG1 in an embodiment of the present application;
  • FIG2c is a schematic diagram of a second possible implementation method in a situation in the scenario of FIG1 in an embodiment of the present application;
  • FIG3a is a schematic diagram of current message processing in another case in the scenario of FIG1 according to an embodiment of the present application.
  • FIG3b is a schematic diagram of a first possible implementation method in another case in the scenario of FIG1 in an embodiment of the present application;
  • FIG3c is a schematic diagram of a second possible implementation method in another case in the scenario of FIG1 in an embodiment of the present application;
  • FIG4 is a flow chart of a message processing method 100 in an embodiment of the present application.
  • Figure 5a is a schematic diagram of the format of a BGP update message in an embodiment of the present application.
  • FIG5 b is a schematic diagram of the format of a PCEP message in an embodiment of the present application.
  • Figure 6a is a schematic diagram of the format of VTN Option in an embodiment of the present application.
  • FIG6b is a schematic diagram of the format of the VTN Protection Option in an embodiment of the present application.
  • Figure 6c is a schematic diagram of the format of Slice Protection Option in an embodiment of the present application.
  • Figure 7a is a schematic diagram of the format of the MPLS VTN Extension Header in an embodiment of the present application.
  • FIG7b is a schematic diagram of the format of the first message in an embodiment of the present application.
  • FIG8 is a flow chart of another message processing method 200 in an embodiment of the present application.
  • Figure 9a is a schematic diagram of a format of a VTN Option in an embodiment of the present application.
  • FIG9b is a schematic diagram of another format of VTN Option in an embodiment of the present application.
  • FIG10 is a schematic structural diagram of a message processing device 1000 in the present application.
  • FIG11 is a schematic structural diagram of another message processing device 1100 in the present application.
  • FIG12 is a schematic diagram of the structure of a network device 1200 in the present application.
  • FIG13 is a schematic diagram of the structure of another network device 1300 in the present application.
  • Network slicing refers to the technology of separating multiple virtual end-to-end networks based on the network topology to achieve on-demand networking.
  • Each virtual end-to-end network can be called a network slice, and the separated network can be called a slice network.
  • Deploying multiple network slices in the network and reserving sufficient resources for each network slice can ensure the service quality of the services carried on each network slice.
  • VTN is a network slicing technology that can reserve sufficient resources for each VTN slice according to the resource requirements of the VTN slice.
  • the network device uses the resources reserved for the slice corresponding to the VTN ID or Slice ID to forward the traffic of the service, ensuring that the processing of the traffic of the service can meet the resource requirements of the service, so that the service quality of the service corresponding to the traffic of the service can be guaranteed.
  • resources can refer to the indicators that the network device in the slice network needs to rely on to process the traffic of the service, for example, it can include but not be limited to: bandwidth or scheduling priority.
  • bandwidth the larger the reserved bandwidth value is, the larger the reserved resources are; when the resource is scheduling priority, the reserved scheduling priority value indicates that it will be scheduled first, which indicates that the reserved resources are larger.
  • bandwidth bandwidth
  • the reserved bandwidth value indicates that it will be scheduled first, which indicates that the reserved resources are larger.
  • a network device determines that the primary slice of a service (i.e., the network slice that carries the traffic of the service) fails, the network device will steer the traffic of the service into a public channel in a default manner.
  • the public channel is the forwarding channel corresponding to the remaining resources after the resources of the primary interface of the service on the network device are removed from the slice resources that have been allocated to the primary slice.
  • the resources on the public channel are not exclusive resources for a certain service, but channels for carrying regular service traffic.
  • Regular service traffic may include, but is not limited to, Internet Protocol (IP) traffic formed by routing and low-value service traffic.
  • IP Internet Protocol
  • the main interface of the service on the network device may refer to the physical interface when the network device determines the traffic of the service to be transmitted on the network device based on the way of querying the route.
  • At least one network slice can be deployed on the main interface, and each network slice corresponds to a logical interface (also called a sub-interface) on the main interface.
  • the network device guides the traffic of the service to be transmitted through the corresponding network slice by maintaining the route and the correspondence between the slice information, sub-interface and next hop on each main interface, wherein the slice information is used to uniquely identify the network slice.
  • the processing process of the traffic of the received service by the network device can be understood as follows: first, the network device determines the main interface of the traffic of the service by querying the route, and then, in the correspondence between the slice information, sub-interface and next hop on the main interface, determines the sub-interface and next hop corresponding to the slice information of the main slice of the service, and then forwards the traffic of the service to the next hop through the determined sub-interface.
  • an embodiment of the present application provides a message processing method, in which a corresponding protection slice is configured for the main slice of the service.
  • the network device finds that the main slice of the service fails, the network device can import the traffic of the service into the protection slice corresponding to the active slice, and forward the traffic of the service through the protection slice.
  • the resources on the protection slice are isolated resources.
  • the traffic of the service can be transmitted through the resources on the protection slice corresponding to the main slice. Since the protection slice has isolation resources, compared with importing the traffic of the service into the public channel, the method provided by the embodiment of the present application can ensure the service quality of the service when the main slice fails.
  • a network device determines that a "primary slice failure" may refer to a primary slice failure on the primary interface of the service on the network device on the forwarding path of the traffic of the service determined by the network device.
  • each primary path in the network may be configured with at least one backup path. When the primary path fails, the traffic of the service can be directed to the backup path corresponding to the primary path to ensure normal provision of the service.
  • a network device determines that a "primary slice failure" may also refer to a network device determining that the primary path of the service fails, directing the traffic of the service to a backup path of the primary path, while the primary slice is not deployed on the backup path, or the primary slice deployed on the backup path also fails.
  • the "failure" of the primary slice may refer to the unavailability of the primary slice, or it may refer to congestion in the primary slice.
  • the at least two slice information is carried in the message belonging to the service, and the at least two slice information include a slice information for indicating a primary slice and at least one slice information for indicating a protection slice.
  • the protection slice of the primary slice can be used to continue forwarding the message. For example, the network device receives a first message including first slice information and second slice information, the first slice information indicates a first network slice, and the second slice information indicates a second network slice; when determining that the first network slice is faulty, the network device uses the second network slice to forward the first message.
  • the network device can easily obtain the slice information for indicating the protection slice from the message, and use the protection slice to forward the message, so that the network device can provide the service quality that meets the service requirements for the service to which the message belongs, and ensure the service experience.
  • each network device in the slice network can locally maintain the mapping relationship between the primary slice and the protection slice. Then, when the network device determines that the primary slice indicated by the slice information in the received message is faulty, it can determine the protection slice corresponding to the primary slice in the locally maintained mapping relationship, and continue to forward the message using the determined protection slice.
  • a network device receives a first message including first slice information, and the first slice identifier indicates a first network slice; when determining that the first network slice is faulty, the network device determines the second slice information based on the first slice information and the mapping relationship, and the mapping relationship includes at least the correspondence between the first slice information and the second slice information, and the second slice information indicates the second network slice; then, the network device uses the second network slice to forward the first message. In this way, there is no need to expand the service message to carry the slice information of the protection slice.
  • the purpose of using the protection slice to forward the message is achieved when the network device determines that the primary slice has failed, so that the network device can provide the service to which the message belongs with a service quality that meets the service requirements, thereby ensuring the service experience.
  • the slice network may include: a primary path 1, and a backup path 1 corresponding to the primary path 1, wherein the network devices included in the primary path 1 are: network device 1, network device 2, network device 3, and network device 4, respectively, and the network devices included in the backup path 1 are: network device 1, network device 2, network device 5, and network device 4, respectively.
  • the slice network may also include a control entity 6, and the control entity 6 is used to control each network device in the slice network. Assume that the primary slice of service 1 is slice 1, and the protection slice of service 1 is slice 2.
  • Network device 2 is connected to network device 3 through main interface 1, and network device 2 is also connected to network device 5 through main interface 2.
  • Main interface 1 includes slice 1 and slice 2, and main interface 2 includes slice 2.
  • both slice 1 and slice 2 reserve a bandwidth of 10 Mbps, and the total bandwidth of main interface 1 and main interface 2 are 25 Mbps and 50 Mbps, respectively. If message 1 of service 1 enters the slice network from network device 1, and the destination node in the slice network is network device 4, the method provided in the embodiment of the present application is explained below by taking the example of network device 2 determining the failure of the main slice 1 from network device 2 to network device 3.
  • the processing strategy for message 1 includes: first checking whether there is a protection slice of the main slice 1 on the main path 1; if so, continue to use the protection slice of the main slice 1 on the main path 1 to forward the message 1; if not, import the message 1 into the backup path 1.
  • the network device 2 processes the message 1 in the way shown in Figure 2a.
  • the network device 2 imports the message 1 to the public channel 1 of the main interface 1.
  • the resources of the public channel 1 are not isolated resources and need to carry the resources on the main interface 1.
  • the public channel 1 can only transmit IP traffic and low-value business traffic formed by the routing, so the public channel 1 cannot meet the 10Mbps bandwidth requirement of business 1.
  • Message 1 may include slice information 1 and slice information 2.
  • Slice information 1 indicates slice 1
  • slice information 2 indicates slice 2.
  • Network device 2 parses message 1 to obtain slice information 1 and slice information 2, thereby importing message 1 to slice 2 indicated by slice information 2 on the main interface 1.
  • the resource of slice 2 is 10Mbps, which can meet the 10Mbps bandwidth requirement of service 1.
  • Message 1 may include slice information 1, slice information 1 indicates slice 1, each network device in the slice network includes a mapping relationship, the mapping relationship includes a correspondence 1 between slice information 1 and slice information 2, slice information 2 indicates slice 2, network device 2 parses message 1 to obtain slice information 1, searches for a correspondence 1 matching slice information 1 from the mapping relationship, and obtains slice information 2 from the correspondence 1, thereby importing message 1 to slice 2 indicated by slice information 2 on the main interface 1, and the resource of slice 2 is 10Mbps, which can meet the 10Mbps bandwidth requirement of service 1.
  • the network device 2 determines that the processing strategy for message 1 after the main slice 1 fails includes: preferentially switching service 1 from the main path 1 to the backup path 1, and then checking whether the backup path 1 has the main slice 1. If so, the main slice 1 is used to forward the message 1 on the backup path 1; if not, the message 1 is imported into the protection slice 2 of the main slice 1 on the backup path 1, and the message 1 is forwarded using slice 2.
  • the network device 2 processes the message 1 as shown in Figure 3a.
  • the network device 2 imports the message 1 to the public channel 2 of the main interface 2.
  • the resources of the public channel 2 are not isolated resources, and need to carry regular business traffic such as IP traffic and low-value business traffic formed by the routing on the main interface 2. Therefore, the public channel 2 cannot meet the 10Mbps bandwidth requirement of service 1.
  • Message 1 may include slice information 1 and slice information 2.
  • Slice information 1 indicates slice 1
  • slice information 2 indicates slice 2.
  • Network device 2 parses message 1 to obtain slice information 1 and slice information 2, and determines that slice 1 is not deployed on the main interface 2 corresponding to the backup path 1.
  • message 1 is imported into slice 2 indicated by slice information 2 on the main interface 2.
  • the resource of slice 2 is 10Mbps, which can meet the 10Mbps bandwidth requirement of service 1.
  • Message 1 may include slice information 1, slice information 1 indicates slice 1, each network device in the slice network includes a mapping relationship, the mapping relationship includes a correspondence relationship 1 between slice information 1 and slice information 2, slice information 2 indicates slice 2, network device 2 parses message 1 to obtain slice information 1, and determines that slice 1 is not deployed on the main interface 2 corresponding to the backup path 1, thereby searching for a correspondence relationship 1 matching the slice information 1 from the mapping relationship, and obtaining slice information 2 from the correspondence relationship 1, thereby importing message 1 to the slice 2 indicated by the slice information 2 on the main interface 2, and the resource of slice 2 is 10Mbps, which can meet the 10Mbps bandwidth requirement of service 1.
  • the method provided in the embodiments of the present application can better guarantee the service quality of the business compared to the current solution, making it possible for the slice network to stably carry the business.
  • the network device may refer to a communication device with a message forwarding function such as a switch, a router, a virtual routing device or a virtual forwarding device.
  • control entity in the embodiments of the present application may, in one case, be an independently set controller, network manager or route reflector (RR); in another case, it may be a network device having the function of the control entity in the embodiments of the present application.
  • control entity may be an entry node of a slice network.
  • control entity may also be a network device outside the slice network.
  • FIG4 is a flow chart of a message processing method 100 provided in an embodiment of the present application.
  • the method 100 corresponds to the embodiment of the present application.
  • the network device refers to the network device that determines the failure of the primary slice (i.e., the first network slice described below), that is, the network device is the entry node of the failed link, corresponding to the slice network shown in Figure 1, and the network device can be the network device 2 in the slice network shown in Figure 1.
  • the method 100 may include, for example, the following S101 to S102:
  • a network device obtains a first message, the first message includes first slice information and second slice information, the first slice information indicates a first network slice, and the second slice information indicates a second network slice.
  • the control entity may send a control message to each network device included in the slice network, and the control message includes the first slice information and the second slice information, so that each network device included in the slice network can deploy the network slice based on the control message.
  • the network devices included in the slice network include the network device in S101.
  • the control message may be a message for a control entity to send a forwarding path to a slice network, or may be other control messages associated with a message carrying a forwarding path.
  • the forwarding path may be a segment routing (SR) path, such as a segment routing (Segment Routing Internet Protocol version 6, SRv6) tunnel based on the sixth version of the Internet Protocol or a segment routing (Segment Routing Multi-Protocol Label Switching, SR MPLS) tunnel based on multi-protocol label switching.
  • SR segment routing
  • the forwarding path mentioned in the embodiment of the present application may also be expressed as an SR policy.
  • the control message may be, for example, a BGP update message or a PCEP message.
  • the control entity may expand the BGP update message containing forwarding path related information of the first slice information (such as the Slice ID of the first network slice), for example, by adding a protection slice information (such as a Protection Slice ID) field in the BGP update message and carrying the second slice information in the protection slice information field.
  • the format of the BGP update message in the embodiment of the present application can be seen in Figure 5a.
  • a Protection Slice ID field is added by extending the Network Resource Partition Sub Type Length Value (NRP Sub-TLV), wherein the NRP Sub-TLV includes a type (Type) field, a length (Length) field, a flag (Flags), a reserved (Reserved) field and a value (Value) field, wherein the value of the Type field is used to indicate that the NRP Sub-TLV carries the slice information of the forwarding path, the value of the Length field is used to indicate the length of the NRP Sub-TLV, the Value field may include an NRP ID field and an extended Protection Slice ID field, the NRP ID field carries the slice information of the primary slice, and the Protection Slice ID field carries the slice information of the protection slice of the primary slice, for example, the NRP ID field carries the first slice information, and the Protection Slice ID field carries the second slice information.
  • BGP update message can refer to BGP SR Policy Extensions for Network Resource Partition draft-d
  • the control entity may extend the PCEP message containing the forwarding path related information of the first slice information (such as the Slice ID of the first network slice), for example, by adding a Protection Slice ID field in the PCEP message, and carrying the second slice information in the Protection Slice ID field.
  • the format of the PCEP message in the embodiment of the present application can be seen in FIG. 5b, in which the Protection Slice ID field is extended and added in the VTN TLV in the PCEP message, wherein the VTN TLV includes a Type field, a Length field, a VTN ID field, a Protection Slice ID field, Flags, a Reserved field, and an optional sub-type length value (Optional sub-TLV(s)) field.
  • the VTN ID field carries the slice information of the primary slice
  • the Protection Slice ID field carries the slice information of the protection slice of the primary slice
  • the VTN ID field carries the first slice information
  • the Protection Slice ID field carries the second slice information.
  • VTN Virtual Transport Network
  • PCEP Path Computation Element Communication Protocol
  • the network device may create a protection slice (i.e., the second network slice) corresponding to the first network slice in the following manner: Mode 1: pre-allocate resources for the protection slice, i.e., after the network device receives the control message, before using the second network slice, the network device allocates resources for the second network slice.
  • Mode 2 dynamically trigger the deployment of resources for the protection slice, i.e., after the network device receives the control message, it only deploys the second network slice without allocating resources for the second network slice, and when it is determined that the first network slice protected by the second network slice fails, it dynamically triggers the allocation of resources for the second network slice; when the first network slice fails, the resources of the second network slice are recovered.
  • Mode 1 allocates resources to the protection slice in advance, so that when the main slice fails, the service can be imported into the protection slice in time, which provides sufficient preparation for ensuring the service quality of the service;
  • Mode 2 allocates resources to the protection slice dynamically, so that the allocation of corresponding resources to the protection slice is triggered only when the active slice fails, and when the main slice returns to normal, the resources allocated to the protection slice are triggered to be recovered, so as to achieve the purpose of resource allocation on demand and improve resource utilization.
  • S101 may include: the network device processes the message entering the slice network.
  • the network device processes the message entering the slice network, and the network device may determine that the primary slice of the network device is the first network slice based on a route query, and the protection slice of the first network slice includes the second network slice. Then, the first slice information and the second slice information are added to the message entering the slice network to obtain the first message.
  • S101 may include: the network device receives a first message, wherein the first message may be obtained by an ingress node of the slice network processing a message entering the slice network.
  • the first slice information may be information indicating a first network slice, for example, a Slice ID of the first network slice.
  • the second slice information may be information indicating a second network slice, for example, a Slice ID of the second network slice.
  • the following is an exemplary introduction to the manner in which the first message carries the second slice information in various scenarios.
  • the first message may carry the second slice information via an Internet Protocol version 6 (IPv6) extension header.
  • IPv6 Internet Protocol version 6
  • the IPv6 extension header carrying the second slice information may be a hop-by-hop (HBH) header in the first message.
  • the first message may carry the second slice information through the VTN Option of the HBH header.
  • the format of the VTN Option may be shown in FIG6a.
  • the VTN Option may include a Next Header field, an Hdr Ext Len field, an Option Type field, an Option Date Len field, a Flags field, a Reserved field, a Slice ID field, and a Protection Slice ID field.
  • the Slice ID field carries the first slice information
  • the Protection Slice ID field carries the second slice information.
  • the first message may also carry the second slice information through the VTN Protection Option of the HBH header.
  • the VTN Protection Option may be a newly added Option in the HBH header.
  • the VTN Protection Option may be shown in Figure 6b.
  • the VTN Protection Option may include a Next Header field, an Hdr Ext Len field, an Option Type field, an Option DateLen field and a Protection Slice ID field.
  • the Protection Slice ID field carries the second slice information.
  • the first slice information may be carried in the VTN Option of the HBH header of the first message.
  • the VTN Option is only less than the VTN Option shown in Figure 6a in terms of the Protection Slice ID field.
  • the IPv6 extension header carrying the second slice information may be a Destination Options Header (DOH) in the first message.
  • DOH Destination Options Header
  • the first message may carry the second slice information through the Slice Protection Option of the DOH.
  • the format of the Slice Protection Option may be shown in FIG6c.
  • the Slice Protection Option may include a Next Header field, an Hdr Ext Len field, an Option Type field, an Option Date Len field, and a Protection Slice ID field.
  • the Protection Slice ID field carries the second slice information.
  • the first slice information may be carried in the VTN Option of the HBH header of the first message.
  • the VTN Option is only less than the VTN Option shown in FIG6a in terms of the Protection Slice ID field.
  • the first message may carry the second slice information via an MPLS label or an extension header.
  • the MPLS label in the first message may carry the second slice information.
  • the first message may carry the second slice information through the VTN Protection ID of the MPLS VTN Extension Header.
  • the format of the MPLS VTN Extension Header may be shown in FIG7a.
  • the MPLS VTN Extension Header may include a Next Header (also denoted as NH) field, a header length (also denoted as HLEN) field, Flags, a Reserved field, a VTN ID field, and a VTN Protection ID field.
  • the VTN ID field carries the first slice information
  • the VTN Protection ID field carries the second slice information.
  • VTN Virtual Transport Network
  • the extension header after the MPLS label stack in the first message may carry the second slice information.
  • the format of the first message may be shown in FIG. 7b.
  • Extension Header After the MPLS Label Stack in the first message, there are multiple available extension headers (Extension Header). The first message may use any unoccupied Extension Header to carry the second slice information.
  • the structure of the first message in FIG. 7b may be seen in MPLS Network Actions using Post-Stack Extension Headers draft-song-mpls-extension-header-11.
  • the network device determines that the first network slice fails, which may refer to the network device determining that the first network slice is unavailable or that the first network slice is congested. Alternatively, the network device determines that the first network slice fails, which may refer to the network device determining that the primary path fails, and determining that the first network slice is not deployed on the primary interface corresponding to the backup path of the primary path on the network, or that the deployed first network slice is unavailable or that the deployed first network slice is congested.
  • the method 100 may further include: the network device obtains a second message that also includes the first slice information and the second slice information, and the second message has the same destination as the first message in S101; when determining that the first network slice is normal, the network device determines the first output interface and the first next hop according to the first slice information; and the network device sends the second message from the first output interface to the first next hop.
  • S102 may include, for example: the network device determines the second output interface and the second next hop according to the second slice information; and the network device sends the first message from the second output interface to the second next hop.
  • the second next hop and the first next hop may be the same or different, and the first output interface and the second output interface may be the same or different.
  • the first network slice corresponds to slice 1
  • the second network slice corresponds to slice 2
  • the first output interface is the primary interface 1
  • the first next hop is the network device 3
  • the second output interface is the primary interface 1
  • the second next hop is the network device 3.
  • the first network slice corresponds to slice 1
  • the second network slice corresponds to slice 2
  • when the second message corresponds to message 1 the first output interface is the main interface 1
  • the first next hop is network device 3
  • the second output interface is the main interface 2
  • the second next hop is network device 5.
  • one protection slice when allocating protection slices of network slices, one protection slice may be allocated to one primary slice.
  • the first network slice is the primary slice
  • the second network slice is the protection slice of the first network slice.
  • the two network slices can also be set to protect each other.
  • the first network device is the protection slice of the second network slice
  • the second network device is the protection slice of the first network slice.
  • the first message in the above S101 ⁇ S102 is a message with the first network slice as the main slice, and the first message can be imported into the second network slice after the failure of the first network slice is determined.
  • the method 100 can also include: the network device receives a third message including the first slice information and the second slice information, and when the failure of the second network slice is determined, the network device uses the first network slice to forward the third message. In this way, not only can the service quality of the services carried by each network slice be guaranteed, but also the resource utilization can be improved to a certain extent.
  • the same protection slice can be allocated to multiple main slices that meet the conditions (such as multiple main slices belonging to the same tenant).
  • the second network slice is not only a protection slice of the first network slice, but also a protection slice of the fourth network slice.
  • the first message in the above S101 to S102 is a message with the first network slice as the main slice, and the first message can be imported into the second network slice after the failure of the first network slice is determined.
  • the method 100 can also include: the network device receives a fourth message including the fourth slice information and the second slice information, and when the failure of the fourth network slice is determined, the network device uses the second network slice to forward the fourth message.
  • this embodiment can also ensure the service quality of the services carried by each network slice, and to a certain extent improve resource utilization.
  • multiple protection slices may be allocated to a primary slice, and there may be a protection priority relationship between the multiple protection slices.
  • the first network slice is the main slice
  • the second network slice is the protection slice of the first network slice.
  • other protection slices may be allocated to the first network slice, and the other protection slices may include a third network slice.
  • the first message may also include third slice information, and the third slice information indicates the third network slice.
  • the way in which the first message carries the third slice information can refer to the way in which the first message carries the second slice information.
  • S102 may include: if the first network device determines that the first network slice fails, it may check whether the second network slice fails.
  • the second network slice does not fail, the second network slice is used to forward the first message. If the second network slice also fails, the third network slice is used to forward the first message. In this way, by performing at least two levels of protection on the network slice, the service quality of the services carried on each network slice can be more reliably guaranteed.
  • multiple network slices with a protection relationship can be network slices of the same level, or can also be network slices with sub-slice relationships.
  • the first network slice and the second network slice may be slice 1 and slice 2 in FIG. 1, respectively; for another example, the first network slice may be a sub-slice of slice 1 in FIG. 1, and the second network slice may be slice 1 or slice 2; for another example, the first network slice may be a sub-slice of slice 2 in FIG. 1, and the second network slice may be slice 1 or slice 2.
  • the message by carrying the slice information of the main slice and the slice information of the protection slice in the message, when the message encounters a main slice failure during transmission in the slice network, the message can be timely and accurately imported into the protection slice based on the slice information of the protection slice carried in the message, and the message can be transmitted using the resources of the protection slice, thereby ensuring the service quality requirements of the business to which the message belongs when the main slice fails.
  • Figure 8 is a flow chart of a message processing method 200 provided in an embodiment of the present application.
  • Figure 8 describes the interaction between the control entity and the network device in the network.
  • the method 200 corresponds to the second possible implementation provided in an embodiment of the present application.
  • the network device refers to a network device that determines the failure of the primary slice (i.e., the first network slice described below), that is, the network device is the entry node of the failed link, corresponding to the slice network shown in Figure 1, and the network device can be the network device 2 in the slice network shown in Figure 1; the control entity can correspond to the control entity 6 in Figure 1.
  • the method 200 may include, for example, the following S201 to S206:
  • a control entity sends a control message to a network device, where the control message includes first slice information and second slice information.
  • S202 The network device receives the control message sent by the control entity.
  • control message the first slice information, the second slice information, and the manner of carrying the first slice information and the second slice information in the control message can be referred to the introduction in the embodiment shown in FIG. 4 .
  • the network device saves the correspondence between the first slice information and the second slice information in a mapping relationship.
  • the slice information corresponding to the protection slice of the main slice is not carried in the message, and the correspondence between the slice information of the network slices with a protection relationship needs to be maintained locally in the network device.
  • the set of these corresponding relationships is called a mapping relationship, and the mapping relationship can be reflected in the network device as a mapping relationship table.
  • the network device when it receives a control message, it obtains the first slice information and the second slice information by parsing the control message, thereby saving the correspondence between the first slice information and the second slice information in a mapping relationship. In this way, preparations are made for the subsequent use of the correspondence for slice protection.
  • the network device obtains a first message, where the first message includes first slice information, and the first slice information indicates a first network slice.
  • the first message transmitted in the slice network may include not only the slice information indicating the main slice (i.e., the first slice information indicating the first network slice), but also indication information, which is used to indicate whether to perform slice protection on the first network slice. If the indication information in the first message obtained by the network device indicates that the first network slice needs to be slice protected, the following S205 to S206 are executed; if the indication information in the first message obtained by the network device indicates that the first network slice does not need to be slice protected, then when the network device determines that the first network slice fails, the network device can import the first message into the public channel for subsequent transmission based on the current implementation.
  • the indication information may include a first flag bit, and different contents indicated by the indication information are expressed by different values of the first flag bit.
  • the first value may be, for example, 1, and the fourth value may be, for example, 0.
  • LP can be any undefined flag bit in the VTN Option.
  • LP can be, for example, any one of the 7 undefined flag bits in Flags, or LP can be, for example, any bit in the Reserved field.
  • the indication information that may be included in the first message may not only be used to indicate whether to perform slice protection on the first network slice, but may also indicate whether to refresh the slice information when indicating that the first network slice needs to be slice protected. If the indication information in the first message obtained by the network device indicates that the first network slice needs to be slice protected and the slice information needs to be refreshed, then after executing S205 below, S206 may refresh the slice information carried in the first message based on the indication information and the slice information of the determined protected slice before transmitting it. In this way, when it is determined that the resources of the protected slice are more stable, This makes the network devices on the subsequent transmission path more reliable and better guarantees the service quality of the business. If the indication information in the first message obtained by the network device indicates that the first network slice needs to be sliced and protected, but the slice information does not need to be refreshed, then S205 to S206 can be directly executed.
  • the indication information may include a second flag bit, and different contents indicated by the indication information are expressed by different values of the second flag bit.
  • the second value may be, for example, 1, and the third value may be, for example, 0.
  • SU can be any undefined flag bit in the VTN Option.
  • SU can be, for example, any one of the 7 undefined flag bits in Flags, or SU can be, for example, any bit in the Reserved field.
  • the indication information includes LP and SU
  • LP and SU can be carried through different flag bits of the first message; they can also be carried through the same field of the first message, and different values of the field carrying LP and SU correspond to different indications of LP and SU.
  • the indication information may only include LP but not SU. Then, it can be determined by the default setting configuration whether the slice information in the message needs to be refreshed after the slice protection is performed. For example, the default setting indicates that the slice information needs to be refreshed. Then, even if the indication information of the message does not include SU, the slice information can be automatically refreshed after the slice protection is performed. For another example, the default setting indicates that the slice information does not need to be refreshed. Then, when SU is not included in the indication information of the message, the slice information is not refreshed after the slice protection is performed. Alternatively, the indication information may only include SU but not LP. Then, it can be determined by the default setting configuration whether the slice protection needs to be performed.
  • the default setting indicates that slice protection needs to be performed. Then, even if LP is not included in the indication information of the message, slice protection can be performed after the main slice failure is determined. For another example, the default setting indicates that slice protection is not required. Then, when LP is not included in the indication information of the message, slice protection is performed even if the main slice failure is determined.
  • the indication information may include LP and SU. Then, the indications of LP and SU do not interfere with each other, and related operations can be performed based on the indications of their respective values.
  • the network device determines the second slice information based on the first slice information and a mapping relationship, where the mapping relationship includes a correspondence between the first slice information and the second slice information, and the second slice information indicates the second network slice.
  • the network device may perform slice protection for messages transmitted in the slice network based on a locally maintained mapping relationship by default. Then, after the network device obtains the first message, it parses the first message to obtain the first message's primary slice as the first network slice; when the network device determines that the first network slice is faulty, it searches for a corresponding relationship that matches the first slice information from the locally maintained mapping relationship, and determines the second network slice based on the second slice information in the matched corresponding relationship. In this way, the network device determines the protection slice of the primary slice of the first message, and is ready for the subsequent quality transmission of the first message.
  • the first message includes LP
  • S205 may include: when determining that the first network slice fails, the network device determines the need to perform slice protection based on the value of LP; then, the network device obtains the second network slice corresponding to the first slice information from the mapping relationship stored locally.
  • the network device imports the first message into the public channel for subsequent transmission. In this way, by carrying LP in the first message, the slice network can process the first message more flexibly.
  • the network device uses the second network slice to forward the first message.
  • the network device may set a default setting of whether to refresh the slice information in the message after performing slice protection. If it is believed that the protection slices in the network are more reliable after performing slice protection, then the slice information in the message may be refreshed by default after performing slice protection.
  • S206 may include: the network device refreshes the first slice information in the first message to the second slice information, obtains the second message, and then the network device forwards the second message using the second network slice. If it is believed that the slice protection is the network device's own behavior, and the subsequent network device does not need to switch the corresponding network slice for the message, then the slice information in the message may be set by default not to be refreshed after performing slice protection.
  • S206 may include: the network device keeps the slice information of the main slice in the first message as the first slice information, and then the network device forwards the first message using the second network slice. In this way, the network device can configure its own default settings according to actual needs, which provides a basis for the execution of S206.
  • the first message includes SU
  • S206 may include: if the network device determines that the slice information needs to be refreshed based on the value of SU, then the network device refreshes the first slice information in the first message to the second slice information, and obtains the second message. The network device then forwards the second message using the second network slice; if the network device determines that the slice information does not need to be refreshed based on the value of SU, the network device keeps the slice information of the primary slice in the first message as the first slice information, and then forwards the first message using the second network slice. In this way, by carrying SU in the first message, the slice network can process the first message more flexibly after slice protection.
  • method 200 for relevant instructions such as the way in which the network device creates a protection slice corresponding to the main slice and the slice protection mode, please refer to method 100.
  • a mapping relationship is locally maintained by a network device, and the mapping relationship includes a corresponding relationship between slice information with a protection relationship, so that when a message encounters a primary slice failure during transmission in a slice network, the protection slice of the primary slice can be determined based on the slice information of the primary slice carried in the message and the locally maintained mapping relationship, thereby accurately importing the message into the protection slice, and using the resources of the protection slice to transmit the message, thereby ensuring the service quality requirements of the business to which the message belongs when the primary slice fails, and there is no need to carry the slice information of the protection slice in the transmitted message, which saves the network transmission resources to a certain extent.
  • the embodiment of the present application further provides a message processing device 1000, which is applied to a network device, as shown in FIG10.
  • the device 1000 may include: a receiving unit 1001 and a sending unit 1002. Among them:
  • the receiving unit 1001 is configured to obtain a first message, wherein the first message includes first slice information and second slice information, wherein the first slice information indicates a first network slice, and the second slice information indicates a second network slice.
  • the receiving unit 1001 may execute S101 shown in FIG. 4 .
  • the sending unit 1002 is used to forward the first message using the second network slice when determining that the first network slice fails.
  • the sending unit 1002 can execute S102 shown in Figure 4.
  • the apparatus 1000 further includes: a processing unit.
  • the receiving unit 1001 is further configured to obtain a second message before obtaining the first message, wherein the second message includes the first slice information and the second slice information, and the first message and the second message have the same destination;
  • a processing unit is configured to determine a first output interface and a first next hop according to the first slice information; and a sending unit 1002 is further configured to send the second message from the first output interface to the first next hop.
  • the sending unit 1002 is specifically used to: determine a second output interface and a second next hop based on the second slice information; and send the first message from the second output interface to the second next hop.
  • the first message is an SRv6 message
  • the first message carries the second slice information via an IPv6 extension header.
  • the first message carries the second slice information through the VTN Option of the HBH header; or, the first message carries the second slice information through the VTN Protection Option of the HBH header.
  • the first message carries the second slice information through the Slice Protection Option of DOH.
  • the first message is an SR MPLS message.
  • the first message carries the second slice information through an MPLS label, or the first message carries the second slice information through an extension header after an MPLS label stack.
  • the receiving unit 1001 is further configured to receive a control message sent by a control entity before obtaining the first message, wherein the control message includes the first slice information and the second slice information.
  • the control message is a BGP update message or a PCEP message.
  • the apparatus 1000 further includes: a processing unit.
  • the processing unit is configured to allocate resources to the second network slice after receiving a control message sent by the control entity and before using the second network slice to forward the first message when determining that the first network slice fails.
  • the sending unit 1002 is specifically used to: when it is determined that the first network slice fails, allocate resources to the second network slice, and use the second network slice to forward the first message.
  • the first message also includes third slice information, and the third slice information indicates a third network slice.
  • the sending unit 1002 is specifically used to: when determining that the first network slice fails and the second network slice fails, use the third network slice to forward the first message.
  • the receiving unit 1001 is further used to obtain a third message, wherein the third message includes the first slice information and the second slice information; the sending unit 1002 is further used to forward the third message using the first network slice when it is determined that the second network slice fails.
  • the receiving unit 1001 is further used to obtain a fourth message, wherein the fourth message includes fourth slice information and the second slice information, and the fourth slice information indicates a fourth network slice; the sending unit 1002 is further used to use the second network slice to forward the fourth message when it is determined that the fourth network slice fails.
  • the first network slice is a sub-slice of the second network slice.
  • the embodiment of the present application further provides a message processing device 1100, which is applied to a network device, as shown in FIG11.
  • the device 1100 may include: a receiving unit 1101, a processing unit 1102, and a sending unit 1103. Among them:
  • the receiving unit 1101 is configured to obtain a first message, where the first message includes first slice information, and the first slice identifier indicates a first network slice.
  • the receiving unit 1101 may execute S204 shown in FIG8 .
  • the processing unit 1102 is used to determine the second slice information according to the first slice information and the mapping relationship when determining the failure of the first network slice, wherein the mapping relationship includes a corresponding relationship between the first slice information and the second slice information, and the second slice information indicates the second network slice.
  • the processing unit 1102 can execute S205 shown in Figure 8.
  • the sending unit 1103 is configured to forward the first message using the second network slice.
  • the sending unit 1103 may execute S206 shown in FIG8 .
  • the first message also includes indication information, and the indication information is used to indicate slice protection for the first network slice.
  • the indication information includes a first value of a first flag bit, where the first flag bit is used to indicate whether slice protection needs to be performed, and the first flag bit is the first value used to indicate that slice protection needs to be performed.
  • the processing unit 1102 is specifically used to: determine the need to perform slice protection based on the first value of the first flag bit in the first message; and obtain the second network slice corresponding to the first slice information from the mapping relationship stored locally.
  • the indication information is also used to indicate whether to refresh the slice information.
  • the indication information also includes a second flag bit, the second flag bit is used to indicate whether the slice information needs to be refreshed, the second flag bit is a second value used to indicate that the slice information needs to be refreshed, and the second flag bit is a third value used to indicate that the slice information does not need to be refreshed.
  • the sending unit 1103 is specifically used to: replace the first slice information in the first message with the second slice information to obtain a second message; and use the second network slice to forward the second message.
  • the first message may be an SRv6 message, and the first message carries the indication information through the VTN Option of the HBH header.
  • the receiving unit 1101 is further used to receive a control message sent by the control entity before obtaining the first message, and the control message includes the first slice information and the second slice information; the processing unit 1102 is further used to save the correspondence between the first slice information and the second slice information in the mapping relationship.
  • the control message may be a BGP update message or a PCEP message.
  • the receiving unit 1101 may execute S201 to S202 shown in FIG8
  • the processing unit 1102 may execute S203 shown in FIG8 .
  • an embodiment of the present application provides a network device 1200 (also referred to as a communication device 1200).
  • the network device 1200 may be the network device in any of the above-mentioned embodiments, for example, it may be the network devices in Figure 1; for example, it may also be the network device in method 100; for example, it may also be the network device in method 200.
  • the network device 1200 may implement the functions of various network devices in the above-mentioned embodiments.
  • the network device 1200 may be the control entity in any of the above-mentioned embodiments, for example, it may be the control entity 6 in Figure 1; for example, it may also be the control entity in method 100; for example, it may also be the control entity in method 200.
  • the network device 1200 may implement the functions of each control entity in the above-mentioned embodiments.
  • the network device 1200 includes at least one processor 1201, a bus system 1202, A memory 1203 and at least one communication interface 1204 .
  • the network device 1200 is a device of a hardware structure, which can be used to implement the functional modules in the message processing device 1000 shown in FIG10.
  • the processing unit in the message processing device 1000 shown in FIG10 can be implemented by the at least one processor 1201 calling the code in the memory 1203.
  • the network device 1200 is a device of a hardware structure, which can be used to implement the functional modules in the message processing device 1100 shown in FIG11.
  • the processing unit 1102 in the message processing device 1100 shown in FIG11 can be implemented by the at least one processor 1201 calling the code in the memory 1203.
  • the network device 1200 may also be used to implement the functions of the network device in any of the above embodiments.
  • the processor 1201 may be a general-purpose central processing unit (CPU), a network processor (NP), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present application.
  • CPU general-purpose central processing unit
  • NP network processor
  • ASIC application-specific integrated circuit
  • the bus system 1202 may include a path for transmitting information between the components.
  • the communication interface 1204 is used to communicate with other devices or communication networks.
  • the memory 1203 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto.
  • the memory may be independent and connected to the processor through a bus.
  • the memory may also be integrated with the processor.
  • the memory 1203 is used to store the application code for executing the solution of the present application, and the execution is controlled by the processor 1201.
  • the processor 1201 is used to execute the application code stored in the memory 1203, so as to realize the functions in the method of the present application.
  • the processor 1201 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 12 .
  • the network device 1200 may include multiple processors, such as the processor 1201 and the processor 1207 in Figure 10. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor.
  • the processor here may refer to one or more devices, circuits, and/or processing cores for processing data (such as computer program instructions).
  • FIG13 is a schematic diagram of the structure of another network device 1300 (also referred to as communication device 1300) provided in an embodiment of the present application.
  • the network device 1300 may be a network device or control entity in any of the above embodiments, and may be each network device or control entity 6 in FIG1 ; for example, it may also be a network device or control entity in method 100; for example, it may also be a network device or control entity in method 200.
  • the network device 1300 may implement the functions of various network devices or control entities in the above embodiments.
  • the network device 1300 includes a main control board 1310 and an interface board 1330 .
  • the main control board 1310 is also called a main processing unit (MPU) or a route processor card.
  • the main control board 1310 controls and manages various components in the network device 1300, including routing calculation, device management, device maintenance, and protocol processing functions.
  • the main control board 1310 includes: a central processing unit 1311 and a memory 1312.
  • the interface board 1330 is also called a line processing unit (LPU), a line card or a service board.
  • the interface board 1330 is used to provide various service interfaces and implement data packet forwarding.
  • Service interfaces include but are not limited to Ethernet interfaces, POS (Packet over SONET/SDH) interfaces, etc., and Ethernet interfaces are, for example, Flexible Ethernet Clients (FlexE Clients).
  • the interface board 1330 includes: a central processor 1331, a network processor 1332, a forwarding table entry memory 1334 and a physical interface card (PIC) 1333.
  • PIC physical interface card
  • the central processor 1331 on the interface board 1330 is used to control and manage the interface board 1330 and communicate with the central processor 1311 on the main control board 1310 .
  • the network processor 1332 is used to implement message forwarding processing.
  • the network processor 1332 may be in the form of a forwarding chip.
  • the processing of uplink messages includes: message inbound interface processing, forwarding table search; the processing of downlink messages: forwarding table search, etc.
  • the physical interface card 1333 is used to implement the docking function of the physical layer, from which the original traffic enters the interface board 1330, and the processed message is sent from the physical interface card 1333.
  • the physical interface card 1333 includes at least one physical interface, which is also called a physical port.
  • the physical interface card 1333 corresponds to the FlexE physical interface in the system architecture.
  • the physical interface card 1333 is also called a daughter card, which can be installed on the interface board 1330 and is responsible for converting the optical signal into a message and forwarding the message to the network processor 1332 for processing after checking the legitimacy of the message.
  • the central processor 1331 of the interface board 1330 can also perform the functions of the network processor 1332, such as implementing software forwarding based on a general-purpose CPU, so that the network processor 1332 is not required in the physical interface card 1333.
  • the network device 1300 includes multiple interface boards.
  • the network device 1300 further includes an interface board 1340 .
  • the interface board 1340 includes a central processor 1341 , a network processor 1342 , a forwarding table entry memory 1344 , and a physical interface card 1343 .
  • the network device 1300 further includes a switching fabric board 1320.
  • the switching fabric board 1320 may also be referred to as a switch fabric unit (SFU).
  • SFU switch fabric unit
  • the switching fabric board 1320 is used to complete data exchange between the interface boards.
  • the interface board 1330 and the interface board 1340 may communicate through the switching fabric board 1320.
  • the main control board 1310 and the interface board 1330 are coupled.
  • the main control board 1310, the interface board 1330, the interface board 1340, and the switching network board 1320 are connected to the system backplane through a system bus to achieve intercommunication.
  • an inter-process communication (IPC) channel is established between the main control board 1310 and the interface board 1330, and the main control board 1310 and the interface board 1330 communicate through the IPC channel.
  • IPC inter-process communication
  • the network device 1300 includes a control plane and a forwarding plane.
  • the control plane includes a main control board 1310 and a central processor 1331.
  • the forwarding plane includes various components for performing forwarding, such as a forwarding table entry memory 1334, a physical interface card 1333, and a network processor 1332.
  • the control plane performs functions such as a router, generating a forwarding table, processing signaling and protocol messages, and configuring and maintaining the status of the device.
  • the control plane sends the generated forwarding table to the forwarding plane.
  • the network processor 1332 forwards the message received by the physical interface card 1333 based on the forwarding table sent by the control plane.
  • the forwarding table sent by the control plane can be stored in the forwarding table entry memory 1334. In some embodiments, the control plane and the forwarding plane can be completely separated and not on the same device.
  • the network processor 1332 can trigger the physical interface card 1333 to obtain a first message, the first message includes first slice information and second slice information, the first slice information indicates a first network slice, and the second slice information indicates a second network slice; the network processor 1332 can also trigger the physical interface card 1333 to forward the first message using the second network slice when determining that the first network slice fails.
  • the network processor 1332 can trigger the physical interface card 1333 to obtain a second message before obtaining the first message, the second message includes the first slice information and the second slice information, and the first message and the second message have the same destination; the central processor 1311 can determine the first output interface and the first next hop according to the first slice information; the network processor 1332 can also trigger the physical interface card 1333 to send the second message from the first output interface to the first next hop.
  • the receiving unit 1001, the sending unit 1102 in the message processing device 1000, and the communication interface 1204 in the network device 1200 can be equivalent to the physical interface card 1333 or the physical interface card 1343 in the network device 1300; the processing unit in the message processing device 1000 and the processor 1201 in the network device 1200 can be equivalent to the central processing unit 1311 or the central processing unit 1331 in the network device 1300.
  • the operation on the interface board 1340 in the embodiment of the present application is consistent with the operation of the interface board 1330, and for the sake of brevity, it will not be repeated.
  • the network device 1300 of this embodiment can correspond to the message processing device 1000 or the network device 1200 in the above-mentioned embodiments, and the main control board 1310, the interface board 1330 and/or the interface board 1340 in the network device 1300 can implement the functions and/or various steps implemented in the message processing device 1000 or the network device 1200 in the above-mentioned embodiments, and for the sake of brevity, it will not be repeated here.
  • the network processor 1332 can trigger the physical interface card 1333 to obtain a first message, the first message includes first slice information, and the first slice identifier indicates the first network slice; when determining that the first network slice fails, the central processor 1311 can determine the second slice information based on the first slice information and the mapping relationship, the mapping relationship includes a correspondence between the first slice information and the second slice information, and the second slice information indicates the second network slice; the network processor 1332 can also trigger the physical interface card 1333 to use the second network slice to forward the first message.
  • the receiving unit 1101, the sending unit 1103 in the message processing device 1100, and the communication interface 1101 in the network device 1200 are The interface 1204 may be equivalent to the physical interface card 1333 or the physical interface card 1343 in the network device 1300 ; the processing unit 1102 in the message processing apparatus 1100 , and the processor 1201 in the network device 1200 may be equivalent to the central processor 1311 or the central processor 1331 in the network device 1300 .
  • the operation on the interface board 1340 in the embodiment of the present application is consistent with the operation of the interface board 1330, and for the sake of brevity, it will not be repeated.
  • the network device 1300 of this embodiment can correspond to the message processing device 1100 or the network device 1200 in the above-mentioned embodiments, and the main control board 1310, the interface board 1330 and/or the interface board 1340 in the network device 1300 can implement the functions and/or various steps implemented in the message processing device 1100 or the network device 1200 in the above-mentioned embodiments, and for the sake of brevity, it will not be repeated here.
  • main control boards there may be one or more main control boards, and when there are multiple boards, they may include a primary main control board and a backup main control board.
  • the network device may have at least one switching network board, and the switching network board is used to realize data exchange between multiple interface boards, providing large-capacity data exchange and processing capabilities. Therefore, the data access and processing capabilities of network devices with a distributed architecture are greater than those of devices with a centralized architecture.
  • the network device may have only one board, that is, no switching board, and the functions of the interface board and the main control board are integrated on the board.
  • the central processor on the interface board and the central processor on the main control board can be combined into one central processor on the board to perform the functions of the two.
  • This type of device has low data exchange and processing capabilities (for example, low-end switches or routers and other network devices).
  • the specific architecture to be adopted depends on the specific networking deployment scenario.
  • each of the above-mentioned network devices or network devices can be implemented as a virtualized device.
  • a virtualized device can be a virtual machine (English: Virtual Machine, VM) running a program for sending message functions, 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 each network device or control entity in the embodiments of the present application.
  • each network device or network device can be implemented based on a general physical server in combination with network function virtualization (NFV) technology.
  • NFV network function virtualization
  • Each network device or network device is a virtual host, a virtual router or a virtual switch.
  • network devices in the above-mentioned various product forms have any functions of the network devices or communication devices in the above-mentioned method embodiments, which will not be repeated here.
  • the embodiment of the present application also provides a chip, including a processor and an interface circuit, the interface circuit is used to receive instructions and transmit them to the processor; the processor, for example, can be a specific implementation form of the message processing device in the embodiment of the present application, and can be used to execute the above-mentioned routing method.
  • the processor is coupled to a memory, and the memory is used to store programs or instructions. When the program or instruction is executed by the processor, the chip system implements the method in any of the above-mentioned method embodiments.
  • the processor in the chip system may be one or more.
  • the processor may be implemented by hardware or by software.
  • the processor may be a logic circuit, an integrated circuit, etc.
  • the processor may be a general-purpose processor implemented by reading software code stored in a memory.
  • the memory in the chip system may be one or more.
  • the memory may be integrated with the processor or may be separately provided with the processor, which is not limited in the present application.
  • the memory may be a non-transient processor, such as a read-only memory ROM, which may be integrated with the processor on the same chip or may be provided on different chips.
  • the present application does not specifically limit the type of memory and the arrangement of the memory and the processor.
  • the chip system can be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD) or other integrated chips.
  • FPGA field programmable gate array
  • ASIC application specific integrated circuit
  • SoC system on chip
  • CPU central processor unit
  • NP network processor
  • DSP digital signal processor
  • MCU microcontroller unit
  • PLD programmable logic device
  • the embodiment of the present application further provides a computer-readable storage medium, in which a program code or instruction is stored, and when the program code or instruction is executed on a computer, the computer executes the method in any one of the implementation modes in the embodiments shown in FIG. 4 or FIG. 8 above. Law.
  • an embodiment of the present application also provides a computer program product, which, when executed on a computer, enables the computer to execute any one of the implementation methods of the aforementioned method 100 or method 200.
  • the technical solution of the present application can be embodied in the form of a software product, which can be stored in a storage medium, such as a read-only memory (ROM)/RAM, a magnetic disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network communication device such as a router) to execute the methods described in each embodiment of the present application or some parts of the embodiments.
  • ROM read-only memory
  • RAM magnetic disk
  • optical disk etc.
  • a computer device which can be a personal computer, a server, or a network communication device such as a router

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种报文处理方法及相关设备，为业务的主用切片配置对应的保护切片，当网络设备发现业务的主用切片故障时，网络设备即可将业务的流量导入主用切片对应的保护切片，通过保护切片转发业务的流量。这样，通过预先为承载业务的主用切片划分保护切片，保护切片上的资源为隔离资源，在主用切片故障时，能够通过主用切片对应的保护切片上的资源传输业务的流量，由于保护切片上拥有隔离资源，所以，能够在主用切片故障时保障业务的服务质量。

Description

一种报文处理方法及相关设备
本申请要求于2022年10月28日提交中国国家知识产权局、申请号为202211336208.1、申请名称为“一种网络切片间保护的方法及相关设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
本申请要求于2022年12月16日提交中国国家知识产权局、申请号为202211625229.5、申请名称为“一种报文处理的方法及相关设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，特别是涉及一种报文处理方法及相关设备。
背景技术
通常，在网络设备的接口上部署多个切片，并为每个切片预留足够的资源，以保证网络能够很好的承载业务。在流量转发过程中，流量携带切片标识(slice identity，slice ID)，网络设备使用为该slice ID对应的切片预留的资源转发该流量，从而确保该流量的服务质量。但是，当流量中slice ID对应的切片故障时，按照缺省的方式通过将该流量切换到公共通道上，该公共通道使用为网络切片分配资源之后的剩余资源转发该流量，该方式无法保障该流量的服务质量，影响业务体验。
发明内容
基于此，本申请提供了一种报文处理方法及相关设备，能够在切片故障时将流量切换到该切片的保护切片，解决了切片故障场景中的业务保障问题。
第一方面，本申请提供了一种报文处理方法，该方法例如可以包括：网络设备获得包括第一切片信息和第二切片信息的第一报文，第一切片信息指示第一网络切片，第二切片信息指示第二网络切片；在确定第一网络切片故障时，该网络设备采用第二网络切片转发第一报文。这样，通过预先为承载业务的主用切片划分保护切片，保护切片上的资源为隔离资源，在报文中携带预先为主用切片分配的保护切片的切片标识，当网络设备确定主用切片故障时，能够方便的从报文中获得用于指示保护切片的切片信息，采用该主用切片对应的保护切片上的资源转发该报文，相比确定网络切片发生故障时将业务导入公共通道的处理方式，本申请实施例提供的方法能够在主用切片故障时保障该业务的服务质量，保障了业务体验。
其中，第一网络切片“故障”，可以指第一网络切片不可用或第一网络切片拥塞。“第一网络切片故障”，一种情况下，可以指网络设备确定的第一报文的转发路径上，该网络设备上该第一报文的主接口上的主用切片(即第一网络切片)故障。另一种情况下，为提高网络的可靠性，网络中的每条主用路径可以配置至少一条备用路径，当所确定的第一报文的主用路径发生故障时，能够将第一报文导入到该主用路径对应的备用路径，保证正常提供业务，那么，“第一网络切片故障”，也可以指网络设备确定第一报文的主用路径故障，将该第一报文导入该主用路径的一条备用路径上，而该备用路径上未部署该第一网络切片，或者，该备用路径上部署的第一网络切片也发生故障。
在一些实现方式中，在网络设备获得第一报文之前，该方法还可以包括：网络设备获得包括第一切片信息和第二切片信息的第二报文，该第一报文和第二报文的目的地相同；如果第一网络切片正常，那么，网络设备根据第一切片信息确定第一出接口和第一下一跳；从而，该网络设备从第一出接口向第一下一跳发送第二报文。作为一个示例，上述在确定第一网络切片故障时，网络设备采用第二网络切片转发第一报文，可以包括：网络设备根据第二切片信息确定第二出接口和第二下一跳；从而，网络设备从第二出接口向第二下一跳发送第一报文。其中，第二下一跳和第一下一跳可以相同也可以不同，第一出接口和第二出接口可以相同也可以不同。如此，能够确保具有相同目的地且包括的切片信息的报文均实现有效的转发，且报文转发时的服务质量得到相应的保障。
在一些实现方式中，第一报文可以为基于第六版互联网协议的分段路由(Segment Routing Internet Protocol version 6，SRv6)报文，第一报文可以通过第六版互联网协议(Internet Protocol version 6，IPv6)扩展头携带第二切片信息。
作为一个示例，第一报文可以通过逐跳(hop-by-hop，HBH)头携带第二切片信息。例如，第一报 文可以通过HBH头的虚拟传输网络选项(Virtual Transport Network Option，VTN Option)携带第二切片信息。又例如，第一报文也可以通过HBH头扩展的VTN Protection Option携带第二切片信息。
作为另一个示例，第一报文可以通过目的选项头(Destination Options Header，DOH)扩展的切片保护选项(Slice Protection Option)携带第二切片信息。
在另一些实现方式中，第一报文可以为基于多协议标签交换的分段路由(Segment Routing Multi-Protocol Label Switching，SR MPLS)报文。
作为一个示例，第一报文可以通过MPLS标签携带第二切片信息，例如，第一报文可以通过MPLS VTN扩展头(Extension Header)的VTN Protection ID携带第二切片信息。
作为另一个示例，第一报文也可以通过MPLS标签栈后的扩展头携带第二切片信息。例如，第一报文中的标签栈(MPLS Label Stack)之后，包括多个可使用的Extension Header，第一报文可以使用任意一个未被占用的Extension Header携带第二切片信息。
在一些实现方式中，在网络设备获得第一报文之前，该方法还可以包括网络设备获得第一切片信息和第二切片信息的过程。
作为一个示例，网络设备获得第一切片信息和第二切片信息，可以是网络设备在本地配置第一切片信息和第二切片信息。
作为另一个示例，网络设备获得第一切片信息和第二切片信息，也可以是网络设备接收控制实体发送的控制消息，控制消息包括第一切片信息和第二切片信息。其中，控制消息为边界网关协议更新(Border Gateway Protocol update，BGP update)报文或路径计算单元通信协议(Path Computation Element Communication Protocol，PCEP)报文。如果控制消息为BGP update报文，控制实体可以将包含第一切片信息(如第一网络切片的Slice ID)的转发路径相关信息的BGP update报文进行扩展，例如在BGP update报文中增加保护切片信息(如Protection Slice ID)字段，在保护切片信息字段中携带第二切片信息。如果控制消息为PCEP报文，控制实体可以将包含第一切片信息(如第一网络切片的Slice ID)的转发路径相关信息的PCEP报文进行扩展，例如在PCEP报文中增加Protection Slice ID字段，在Protection Slice ID字段中携带第二切片信息。
作为一个示例，在网络设备获得第一切片信息和第二切片信息后，网络设备创建第一网络切片对应的保护切片(即第二网络切片)的方式可以包括：方式一，预分配保护切片的资源，即，在网络设备获得第一切片信息和第二切片信息后，在使用第二网络切片之前，网络设备为第二网络切片分配资源。方式二，动态触发部署保护切片的资源，即，在网络设备获得第一切片信息和第二切片信息后，只是部署第二网络切片而不为第二网络切片分配资源，当确定第二网络切片所保护的第一网络切片故障后，再动态触发为第二网络切片分配资源；当第一网络切片故障修复后，对第二网络切片的资源进行回收。其中，方式一通过预先为保护切片分配资源的方式，在主用切片故障时能够及时的将业务导入到保护切片，为保障业务的服务质量提供了充分的准备。方式二通过动态为保护切片分配资源的方式，在主动切片故障时才触发为保护切片分配对应的资源，当主用切片恢复正常后又触发收回为该保护切片分配的资源，以此达到资源按需分配的目的，提升了资源利用率。
在一些实现方式中，可以为设置多级保护的机制，例如，设置第二网络切片为第一网络切片的保护切片，第三网络切片为第二网络切片的保护切片。那么，第一报文还可以包括第三切片信息，第三切片信息指示第三网络切片。这样，在确定第一网络切片故障时，网络设备采用第二网络切片转发第一报文，例如可以包括：在确定第一网络切片故障和第二网络切片故障时，网络设备采用第三网络切片转发第一报文。如此，通过多级保护的机制，使得该切片网络能够更加可靠的保障业务的服务质量。
在一些实现方式中，为了能够更好的利用资源，还可以设置网络切片之间的互为保护关系。例如，第二网络切片和第一网络切片互为对方的保护切片。那么，该方法还可以包括：网络设备获得第三报文，第三报文包括第一切片信息和第二切片信息，第三报文中的第二网络切片为主用切片；在确定第二网络切片故障时，网络设备采用第一网络切片转发第三报文。如此，不仅能够保障承载于各网络切片的业务的服务质量，还能够一定程度上提高资源利用率。
在一些实现方式中，为了更好的利用资源，可以为符合条件的多个主用切片(如属于同一租户的多 个主用切片)分配同一个保护切片，例如，第二网络切片不仅为第一网络切片的保护切片，还作为第四网络切片的保护切片。该方法还可以包括：网络设备获得第四报文，第四报文包括第四切片信息和第二切片信息，第四切片信息指示第四网络切片；在确定第四网络切片故障时，网络设备采用第二网络切片转发第四报文。如此，由于第一网络切片和第四网络切片同时故障的几率较低，所以，该实施例也能够保障承载于各网络切片的业务的服务质量，并且在一定程度上也提高资源利用率。
其中，被保护的网络切片可以与保护切片处于同等级别，例如，均为主切片或子切片；或者，被保护的网络切片也可以是保护切片的子切片，例如，第一网络切片为第二网络切片的子切片。
第二方面，本申请还提供了一种报文处理方法，该方法例如可以包括：网络设备获得包括第一切片信息的第一报文，该第一切片信息指示第一网络切片；在确定第一网络切片故障时，网络设备根据第一切片信息和映射关系，确定第二切片信息，映射关系包括第一切片信息和第二切片信息之间的对应关系，第二切片信息指示第二网络切片；网络设备采用第二网络切片转发第一报文。这样，通过预先为承载业务的主用切片划分保护切片，保护切片上的资源为隔离资源，无需对业务的报文进行扩展以携带保护切片的切片信息，而是通过本地维护的主用切片的切片信息和保护切片的切片信息之间的对应关系，实现了在网络设备确定主用切片故障时采用保护切片转发该报文的目的，相比确定网络切片发生故障时将业务导入公共通道的处理方式，本申请实施例提供的方法能够在主用切片故障时保障该业务的服务质量，保障了业务体验。
在一些实现方式中，为了使得本申请实施例提供的网络切片的保护方案能够更加灵活，网络设备所接收的报文中还可以包括指示信息。如果第一报文是SRv6报文，用于携带第一切片信息的是SRv6报文中HBH头的VTN Option，那么，第一标志位可以是HBH头的VTN Option中任何一个未被定义的标志位，如VTN Option的Flags中未被定义的7个标志位中的任意一个，或者，VTN Option的Reserved字段中的任意一个比特位。
在一些实现方式中，指示信息用于指示是否对第一网络切片进行切片保护。
作为一个示例，第一报文中的指示信息可以包括第一标志位的第一值，第一标志位用于指示是否需要执行切片保护，第一标志位为第一值用于指示需要执行切片保护。那么，上述在确定第一网络切片故障时，网络设备根据第一切片信息和映射关系，确定第二切片信息，例如可以包括：网络设备基于第一报文中第一标志位的第一值，确定需求执行切片保护；网络设备从本地保存的映射关系中，获得与第一切片信息对应的第二网络切片。
作为另一个示例，网络设备所接收的报文中的指示信息还可以包括第一标志位的第四值，该报文的主用切片是第一网络切片，保护切片为第二网络切片，那么，网络设备在确定第一网络切片故障时，该网络设备可以基于目前的实现方式，将第一报文导入到公共通道进行后续传输。
在一些实现方式中，该指示信息还可以用于指示是否刷新切片信息。
作为一个示例，第一报文中的指示信息还可以包括第二标志位，第二标志位用于指示是否需要刷新切片信息，第二标志位为第二值用于指示需要刷新切片信息，第二标志位为第三值用于指示不需要刷新切片信息。一种情况下，若第一报文中第二标志位为第二值，网络设备采用第二网络切片转发第一报文，可以包括：网络设备将第一报文中的第一切片信息替换为第二切片信息，获得第二报文；网络设备采用第二网络切片转发第二报文。另一种情况下，若第一报文中第二标志位为第三值，网络设备采用第二网络切片转发第一报文，可以包括：网络设备获得的第一报文中的指示信息，确定该指示信息指示需要对第一网络切片进行切片保护但是不需要刷新切片信息，则，使用第二网络切片转发第一报文。
在一些实现方式中，在网络设备获得第一报文之前，该方法还可以包括：网络设备获得网络设备第一切片信息和第二切片信息；网络设备将第一切片信息和第二切片信息的对应关系保存在映射关系中。其中，网络设备获得第一切片信息和第二切片信息，可以是网络设备上配置获得的第一切片信息和第二切片信息，或者，也可以是网络设备接收控制实体发送的控制消息，该控制消息包括第一切片信息和第二切片信息。其中，控制消息可以为BGP update报文或PCEP报文。
作为一个示例，在网络设备获得第一切片信息和第二切片信息后，网络设备创建第一网络切片对应的保护切片(即第二网络切片)的方式可以包括：方式一，预分配保护切片的资源，即，在网络设备获 得第一切片信息和第二切片信息后，在使用第二网络切片之前，网络设备为第二网络切片分配资源。方式二，动态触发部署保护切片的资源，即，在网络设备获得第一切片信息和第二切片信息后，只是部署第二网络切片而不为第二网络切片分配资源，当确定第二网络切片所保护的第一网络切片故障后，再动态触发为第二网络切片分配资源；当第一网络切片故障修复后，对第二网络切片的资源进行回收。
在一些实现方式中，可以为设置多级保护的机制，例如，设置第二网络切片为第一网络切片的保护切片，第三网络切片为第二网络切片的保护切片。
在一些实现方式中，为了能够更好的利用资源，还可以设置网络切片之间的互为保护关系。例如，第二网络切片和第一网络切片互为对方的保护切片。
在一些实现方式中，为了更好的利用资源，可以为符合条件的多个主用切片(如属于同一租户的多个主用切片)分配同一个保护切片，例如，第二网络切片不仅为第一网络切片的保护切片，还作为第四网络切片的保护切片。
第三方面，本申请还提供了一种报文处理装置，该装置应用于网络设备，该装置例如可以包括：接收单元和发送单元。其中，接收单元，用于获得第一报文，第一报文包括第一切片信息和第二切片信息，第一切片信息指示第一网络切片，第二切片信息指示第二网络切片；发送单元，用于在确定第一网络切片故障时，采用第二网络切片转发第一报文。
在一些实现方式中，所述装置还包括：处理单元。接收单元，还用于在获得第一报文之前，获得第二报文，所述第二报文包括所述第一切片信息和所述第二切片信息，所述第一报文和所述第二报文的目的地相同；处理单元，用于根据所述第一切片信息确定第一出接口和第一下一跳；发送单元，还用于从所述第一出接口向所述第一下一跳发送所述第二报文。
在一些实现方式中，发送单元，具体用于：根据所述第二切片信息确定第二出接口和第二下一跳；从所述第二出接口向所述第二下一跳发送所述第一报文。
在一些实现方式中，所述第一报文为SRv6报文，所述第一报文通过IPv6扩展头携带所述第二切片信息。
作为一个示例，所述第一报文通过HBH头的VTN Option携带所述第二切片信息；或者，所述第一报文通过所述HBH头的VTN Protection Option携带所述第二切片信息。
作为另一个示例，所述第一报文通过DOH的Slice Protection Option携带所述第二切片信息。
在一些实现方式中，所述第一报文为SR MPLS报文。作为一个示例，所述第一报文通过MPLS标签携带所述第二切片信息，或者，所述第一报文通过MPLS标签栈后的扩展头携带所述第二切片信息。
在一些实现方式中，接收单元，还用于在获得第一报文之前，接收控制实体发送的控制消息，所述控制消息包括所述第一切片信息和所述第二切片信息。其中，所述控制消息为BGP update报文或PCEP报文。
在一些实现方式中，所述装置还包括：处理单元。该处理单元，用于在接收控制实体发送的控制消息之后，所述在确定所述第一网络切片故障时采用所述第二网络切片转发所述第一报文之前，为所述第二网络切片分配资源。
在一些实现方式中，发送单元，具体用于：在确定所述第一网络切片故障时，为所述第二网络切片分配资源，并且，采用所述第二网络切片转发所述第一报文。
在一些实现方式中，所述第一报文还包括第三切片信息，所述第三切片信息指示第三网络切片，发送单元，具体用于：在确定所述第一网络切片故障和所述第二网络切片故障时，采用所述第三网络切片转发所述第一报文。
在一些实现方式中，接收单元，还用于获得第三报文，所述第三报文包括所述第一切片信息和所述第二切片信息；发送单元，还用于在确定所述第二网络切片故障时，采用所述第一网络切片转发所述第三报文。
在一些实现方式中，接收单元，还用于获得第四报文，所述第四报文包括第四切片信息和所述第二切片信息，所述第四切片信息指示第四网络切片；发送单元，还用于在确定所述第四网络切片故障时，采用所述第二网络切片转发所述第四报文。
其中，第一网络切片为第二网络切片的子切片。
需要说明的是，本申请提供的装置的具体实现方式以及达到的技术效果，可以参见第一方面提供的方法。
第四方面，本申请还提供了一种报文处理装置，该装置应用于网络设备，该装置可以包括：接收单元、处理单元和发送单元。其中，接收单元，用于获得第一报文，第一报文包括第一切片信息，第一切片标识指示第一网络切片；处理单元，用于在确定第一网络切片故障时，根据第一切片信息和映射关系，确定第二切片信息，映射关系包括第一切片信息和第二切片信息之间的对应关系，第二切片信息指示第二网络切片；发送单元，用于采用第二网络切片转发第一报文。
在一些实现方式中，所述第一报文还包括指示信息，所述指示信息用于指示对所述第一网络切片进行切片保护。
作为一个示例，所述指示信息包括第一标志位的第一值，所述第一标志位用于指示是否需要执行切片保护，所述第一标志位为所述第一值用于指示需要执行切片保护。
在一些实现方式中，处理单元，具体用于：基于所述第一报文中所述第一标志位的第一值，确定需求执行切片保护；从本地保存的所述映射关系中，获得与所述第一切片信息对应的所述第二网络切片。
在一些实现方式中，所述指示信息还用于指示是否刷新切片信息。
作为一个示例，所述指示信息还包括第二标志位，所述第二标志位用于指示是否需要刷新切片信息，所述第二标志位为第二值用于指示需要刷新切片信息，所述第二标志位为第三值用于指示不需要刷新切片信息。
作为另一个示例，若所述第一报文中所述第二标志位为所述第二值，发送单元，具体用于：将所述第一报文中的所述第一切片信息替换为所述第二切片信息，获得第二报文；采用所述第二网络切片转发所述第二报文。
其中，所述第一报文可以为SRv6报文，所述第一报文通过HBH头的VTN Option携带所述指示信息。
在一些实现方式中，接收单元，还用于在获得第一报文之前，接收控制实体发送的控制消息，所述控制消息包括所述第一切片信息和所述第二切片信息；处理单元，还用于将所述第一切片信息和所述第二切片信息的对应关系保存在所述映射关系中。其中，控制消息可以为BGP update报文或PCEP报文。
需要说明的是，本申请提供的装置的具体实现方式以及达到的技术效果，可以参见第二方面提供的方法。
第五方面，本申请提供一种网络设备，所述网络设备包括处理器和存储器，存储器用于存储指令或程序代码，处理器用于从存储器中调用并运行所述指令或程序代码，以执行第一方面、第一方面的任意一种可能的实现、第二方面或第二方面的任意一种可能的实现中的所述方法。
第六方面，本申请提供一种计算机可读存储介质，其特征在于，包括指令、程序或代码，当其在计算机上执行时，使得所述计算机执行第一方面、第一方面的任意一种可能的实现中、第二方面或第二方面的任意一种可能的实现中的所述方法。
第七方面，本申请提供一种计算机程序产品，当所述计算机程序产品在网络设备上运行时，使得所述网络设备执行第一方面、第一方面的任意一种可能的实现中、第二方面或第二方面的任意一种可能的实现中的所述方法。
附图说明
图1为本申请实施例中的一种切片网络的场景示意图；
图2a为本申请实施例中图1的场景中一种情况下目前的报文处理示意图；
图2b为本申请实施例中图1的场景中一种情况下第一种可能的实现方式的示意图；
图2c为本申请实施例中图1的场景中一种情况下第二种可能的实现方式的示意图；
图3a为本申请实施例中图1的场景中另一种情况下目前的报文处理示意图；
图3b为本申请实施例中图1的场景中另一种情况下第一种可能的实现方式的示意图；
图3c为本申请实施例中图1的场景中另一种情况下第二种可能的实现方式的示意图；
图4为本申请实施例中一种报文处理方法100的流程示意图；
图5a为本申请实施例中BGP update报文的格式示意图；
图5b为本申请实施例中PCEP报文的格式示意图；
图6a为本申请实施例中VTN Option的格式示意图；
图6b为本申请实施例中VTN Protection Option的格式示意图；
图6c为本申请实施例中Slice Protection Option的格式示意图；
图7a为本申请实施例中MPLS VTN Extension Header的格式示意图；
图7b为本申请实施例中第一报文的格式示意图；
图8为本申请实施例中另一种报文处理方法200的流程示意图；
图9a为本申请实施例中VTN Option的一格式示意图；
图9b为本申请实施例中VTN Option的另一格式示意图；
图10为本申请中一种报文处理装置1000的结构示意图；
图11为本申请中又一种报文处理装置1100的结构示意图；
图12为本申请中一种网络设备1200的结构示意图；
图13为本申请中另一种网络设备1300的结构示意图。
具体实施方式
网络切片，是指在网络拓扑的基础上分离出多个虚拟的端到端网络以实现按需组网的技术，每个虚拟的端到端网络可以称为一个网络切片，被分离的网络可以称为切片网络。在网络中部署多个网络切片，为每个网络切片预留足够的资源，能够保证该各网络切片上承载的业务的服务质量。例如，VTN是一种网络切片技术，可以为每个VTN切片按照该VTN切片的资源需求预留足够的资源，从而，通过在业务的流量中携带VTN标识(VTN ID或Slice ID)，使得网络设备使用为VTN ID或Slice ID对应的切片预留的资源转发该业务的流量，确保对该业务的流量的处理能够满足该业务的资源需求，从而使得该业务的流量对应的业务的服务质量得以保障。其中，资源，可以指切片网络中网络设备处理业务的流量需要依赖的指标，例如可以包括但不限于：带宽或调度优先级。资源为带宽时，预留的带宽的值越大，表征预留的资源越大；资源为调度优先级时，预留的调度优先级的值指示会越优先被调度，表征预留的资源越大。为了更加方便描述，下文中以资源为带宽为例进行说明。
目前，当网络设备确定业务的主用切片(即承载该业务的流量的网络切片)故障时，该网络设备将按照缺省的方式将该业务的流量导入(steer)公共通道，该公共通道为网络设备上该业务的主接口的资源去掉已经为主用切片分配了切片资源后的剩余资源对应的转发通道，公共通道上的资源，不是给某个业务的独享资源，而是用于承载常规的业务流量的通道，常规的业务流量例如可以包括但不限于：路由形成的互联网协议(Internet Protocol，IP)流量和低价值的业务流量。那么，当业务的主用切片故障时，网络设备将主用切片上承载的该业务的流量切换到公共通道，该公共通道无法保证该业务的服务质量。
其中，网络设备上业务的主接口，可以指网络设备基于查路由的方式确定该业务的流量在该网络设备上传输时的物理接口。该主接口上可以部署至少一个网络切片，每个网络切片对应该主接口上的一个逻辑接口(也可以称为子接口)。网络设备通过维护路由、以及各主接口上切片信息、子接口和下一跳的对应关系，指导业务的流量通过对应的网络切片传输，其中，切片信息用于唯一标识网络切片。例如，网络设备对所接收的业务的流量的处理过程可以理解为：首先，网络设备通过查路由的方式确定该业务的流量的主接口，接着，在该主接口上切片信息、子接口和下一跳的对应关系中，确定与该业务的主用切片的切片信息对应的子接口和下一跳，然后，通过所确定的该子接口向该下一跳转发该业务的流量。
基于此，本申请实施例提供了一种报文处理方法，该方法中，为业务的主用切片配置对应的保护切片，当网络设备发现业务的主用切片故障时，该网络设备即可将该业务的流量导入主动切片对应的保护切片，通过保护切片转发该业务的流量。这样，通过预先为承载业务的主用切片划分保护切片，保护切片上的资源为隔离资源，在主用切片故障时，能够通过该主用切片对应的保护切片上的资源传输该业务的流量，由于保护切片上拥有隔离资源，相比将业务的流量导入公共通道，本申请实施例提供的方法能够在主用切片故障时保障该业务的服务质量。
本申请实施例中，一种情况下，网络设备确定“主用切片故障”，可以指网络设备确定业务的流量的转发路径上，该网络设备上该业务的主接口上的主用切片故障。另一种情况下，为提高网络的可靠性，网络中的每条主用路径可以配置至少一条备用路径，当主用路径发生故障时，能够将业务的流量导入到该主用路径对应的备用路径，保证正常提供业务。那么，网络设备确定“主用切片故障”，也可以指网络设备确定业务的主用路径故障，将该业务的流量导入该主用路径的一条备用路径上，而该备用路径上未部署该主用切片，或者，该备用路径上部署的主用切片也发生故障。
本申请实施例中，主用切片“故障”，可以指主用切片不可用，或者，也可以指主用切片发生拥塞。
第一种可能的实现方式中，业务在通过切片网络转发的过程中，属于该业务的报文中就携带了至少两个切片信息，所述至少两个切片信息包括一个用于指示主用切片的切片信息、以及至少一个用于指示保护切片的切片信息，在报文的转发过程中，当网络设备确定该报文的主用切片故障时，即可采用该主用切片的保护切片继续转发该报文。例如，网络设备接收包括第一切片信息和第二切片信息的第一报文，第一切片信息指示第一网络切片，第二切片信息指示第二网络切片；在确定所述第一网络切片故障时，该网络设备采用第二网络切片转发第一报文。如此，通过在报文中携带预先为主用切片分配的保护切片的切片标识，当网络设备确定主用切片故障时，网络设备能够方便的从报文中获得用于指示保护切片的切片信息，采用保护切片转发该报文，从而，使得网络设备能够为该报文所属的业务提供满足该业务需求的服务质量，保障了业务体验。
第二种可能的实现方式中，切片网络中的各网络设备在获得主用切片和保护切片的对应关系后，可以在本地维护主用切片和保护切片之间的映射关系，那么，当网络设备确定所接收的报文中的切片信息所指示的主用切片故障时，可以在本地维护的映射关系中确定该主用切片对应的保护切片，从而采用所确定的保护切片继续转发该报文。例如，网络设备接收包括第一切片信息的第一报文，该第一切片标识指示第一网络切片；在确定第一网络切片故障时，该网络设备根据第一切片信息和映射关系，确定第二切片信息，该映射关系至少包括第一切片信息和第二切片信息之间的对应关系，第二切片信息指示第二网络切片；那么，该网络设备采用第二网络切片转发第一报文。如此，无需对业务的报文进行扩展以携带保护切片的切片信息，而是通过本地维护的主用切片的切片信息和保护切片的切片信息之间的对应关系，实现了在网络设备确定主用切片故障时采用保护切片转发该报文的目的，使得网络设备能够为该报文所属的业务提供满足该业务需求的服务质量，保障了业务体验。
为了让本申请实施例提供的方法更加清楚，下面结合图1所示的切片网络对本申请实施例提供的方法进行说明。
参见图1，切片网络中可以包括：主用路径1、主用路径1对应的备用路径1，其中，主用路径1包括的网络设备依次为：网络设备1、网络设备2、网络设备3和网络设备4，备用路径1包括的网络设备依次为：网络设备1、网络设备2、网络设备5和网络设备4。该切片网络还可以包括控制实体6，控制实体6用于对该切片网络中的各网络设备进行控制。假设业务1的主用切片为切片1，业务1的保护切片为切片2，网络设备2通过主接口1连接网络设备3，网络设备2还通过主接口2连接网络设备5，主接口1上包括切片1和切片2，主接口2上包括切片2。假设业务1的资源需求为10兆比特每秒(Mbps)，切片1和切片2均预留10Mbps的带宽，主接口1和主接口2的总带宽分别为25Mbps和50Mbps。如果业务1的报文1从网络设备1进入该切片网络，在该切片网络中的目的节点为网络设备4，下面以网络设备2确定网络设备2到网络设备3上主用切片1故障为例，对本申请实施例提供的方法进行说明。
一种情况下，假设网络设备2确定主用切片1故障后对报文1的处理策略包括：优先在主用路径1上查看是否存在主用切片1的保护切片，如果存在，则，继续在主用路径1上采用主用切片1的保护切片转发该报文1，如果不存在，则，将报文1导入备用路径1。
该情况下，网络设备2接收到包括用于指示主用切片1的切片信息1的报文1后，确定主用切片1故障后，按照目前的方式，网络设备2处理报文1的方式参见图2a所示，网络设备2将报文1导入到主接口1的公共通道1上，该公共通道1的资源为主接口1的资源去掉切片1和切片2的资源后的剩余资源(即25Mbps-10Mbps-10Mbps＝5Mbps)，该公共通道1的资源不是隔离资源，需要承载主接口1上 的路由形成的IP流量和低价值的业务流量等常规的业务流量，所以，该公共通道1无法满足业务1的10Mbps的带宽需求。
基于本申请实施例中的第一种可能的实现方式所提供的方法，网络设备2处理报文1的方式参见图2b所示，报文1可以包括切片信息1和切片信息2，切片信息1指示切片1，切片信息2指示切片2，网络设备2解析报文1获得切片信息1和切片信息2，从而，将报文1导入到主接口1上切片信息2所指示的切片2上，该切片2的资源为10Mbps，能够满足业务1的10Mbps的带宽需求。
基于本申请实施例中的第二种可能的实现方式所提供的方法，网络设备2处理报文1的方式参见图2c所示，报文1可以包括切片信息1，切片信息1指示切片1，切片网络中各网络设备包括映射关系，该映射关系包括切片信息1和切片信息2的对应关系1，切片信息2指示切片2，网络设备2解析报文1获得切片信息1，从映射关系中查找与切片信息1匹配的对应关系1，从对应关系1中获得切片信息2，从而，将报文1导入到主接口1上切片信息2所指示的切片2上，该切片2的资源为10Mbps，能够满足业务1的10Mbps的带宽需求。
另一种情况下，假设网络设备2确定主用切片1故障后对报文1的处理策略包括：优先将业务1从主用路径1切换到备用路径1上，再查看备用路径1是否存在主用切片1，如果存在，则，在备用路径1上采用主用切片1转发该报文1，如果不存在，则，将报文1导入备用路径1上主用切片1的保护切片2，采用切片2转发报文1。
该情况下，网络设备2接收到包括用于指示主用切片1的切片信息1的报文1后，确定主用切片1故障后，按照目前的方式，网络设备2处理报文1的方式参见图3a所示，网络设备2将报文1导入到主接口2的公共通道2上，该公共通道2的资源为主接口2的资源去掉切片2的资源后的剩余资源(即50Mbps-10Mbps＝40Mbps)，该公共通道2的资源不是隔离资源，需要承载主接口2上的路由形成的IP流量和低价值的业务流量等常规的业务流量，所以，该公共通道2无法满足业务1的10Mbps的带宽需求。
基于本申请实施例中的第一种可能的实现方式所提供的方法，网络设备2处理报文1的方式参见图3b所示，报文1可以包括切片信息1和切片信息2，切片信息1指示切片1，切片信息2指示切片2，网络设备2解析报文1获得切片信息1和切片信息2，确定备用路径1对应的主接口2上未部署切片1，从而，将报文1导入到主接口2上切片信息2所指示的切片2上，该切片2的资源为10Mbps，能够满足业务1的10Mbps的带宽需求。
基于本申请实施例中的第二种可能的实现方式所提供的方法，网络设备2处理报文1的方式参见图3c所示，报文1可以包括切片信息1，切片信息1指示切片1，切片网络中各网络设备包括映射关系，该映射关系包括切片信息1和切片信息2的对应关系1，切片信息2指示切片2，网络设备2解析报文1获得切片信息1，确定备用路径1对应的主接口2上未部署切片1，从而，从映射关系中查找与切片信息1匹配的对应关系1，从对应关系1中获得切片信息2，从而，将报文1导入到主接口2上切片信息2所指示的切片2上，该切片2的资源为10Mbps，能够满足业务1的10Mbps的带宽需求。
通过上述场景实施例的描述可知，本申请实施例提供的方法相比目前的解决方式，能够很好的保障业务的服务质量，使得切片网络稳定的承载业务成为可能。
需要说明的是，本申请实施例中的网络设备和节点指代相同的含义，可以相互交替理解和使用。网络设备，可以指交换机、路由器、虚拟路由设备或虚拟转发设备等具有报文转发功能的通信设备。
需要说明的是，本申请实施例中的控制实体，一种情况下，可以是独立设置的控制器、网络管理器或路由反射器(Route Reflector，RR)；另一种情况下，也可以是具有本申请实施例中控制实体功能的网络设备，例如，控制实体可以是切片网络的入口节点，又例如，控制实体也可以是切片网络以外的网络设备。
以上为以场景实施例的形式对本申请实施例的介绍，下面结合附图详细说明本申请实施例的具体实现方式。
图4为本申请实施例提供的一种报文处理方法100的流程示意图。该方法100对应本申请实施例提 供的第一种可能的实现方式。该方法100中，网络设备指确定主用切片(即下述第一网络切片)故障的网络设备，也就是说，该网络设备是发生故障的链路的入口节点，对应到图1所示的切片网络，网络设备可以是图1所示的切片网络中的网络设备2。
如图4所示，该方法100例如可以包括下述S101～S102：
S101，网络设备获得第一报文，所述第一报文包括第一切片信息和第二切片信息，所述第一切片信息指示第一网络切片，所述第二切片信息指示第二网络切片。
作为一个示例，在S101之前，控制实体可以向切片网络包括的各网络设备发送控制消息，该控制消息包括第一切片信息和第二切片信息，如此，切片网络包括的各网络设备可以基于该控制消息部署网络切片。切片网络包括的各网络设备中包括S101中的网络设备。
控制消息可以是控制实体向切片网络发送转发路径的消息，也可以是与携带转发路径的消息关联的其他控制消息。其中，转发路径可以是分段路由(segment routing，SR)路径，例如可以是基于第六版互联网协议的分段路由(Segment Routing Internet Protocol version 6，SRv6)隧道或基于多协议标签交换的分段路由(Segment Routing Multi-Protocol Label Switching，SR MPLS)隧道。本申请实施例提及的转发路径也可以表示为SR策略(policy)。
控制消息例如可以为BGP update报文或PCEP报文。
如果控制消息为BGP update报文，控制实体可以将包含第一切片信息(如第一网络切片的Slice ID)的转发路径相关信息的BGP update报文进行扩展，例如在BGP update报文中增加保护切片信息(如Protection Slice ID)字段，在保护切片信息字段中携带第二切片信息。作为一个示例，本申请实施例中BGP update报文的格式可以参见图5a，BGP update报文中通过在网络资源分区子类型长度值(Network Resource Partition Sub Type Length Value，NRP Sub-TLV)中扩展增加Protection Slice ID字段，其中，NRP Sub-TLV中包括类型(Type)字段、长度(Length)字段、标志位(Flags)、预留(Reserved)字段和值(Value)字段，其中，Type字段的值用于指示该NRP Sub-TLV携带该转发路径的切片信息，Length字段的值用于指示该NRP Sub-TLV的长度，Value字段可以包括NRP ID字段和扩展的Protection Slice ID字段，NRP ID字段携带主用切片的切片信息，Protection Slice ID字段携带主用切片的保护切片的切片信息，例如，NRP ID字段携带第一切片信息，Protection Slice ID字段携带第二切片信息。其中，BGP update报文可以参见BGP SR Policy Extensions for Network Resource Partition draft-dong-idr-sr-policy-nrp-01。
如果控制消息为PCEP报文，控制实体可以将包含第一切片信息(如第一网络切片的Slice ID)的转发路径相关信息的PCEP报文进行扩展，例如在PCEP报文中增加Protection Slice ID字段，在Protection Slice ID字段中携带第二切片信息。作为一个示例，本申请实施例中PCEP报文的格式可以参见图5b，PCEP报文中通过在VTN TLV中扩展增加Protection Slice ID字段，其中，VTN TLV中包括Type字段、Length字段、VTN ID字段、Protection Slice ID字段、Flags、Reserved字段和可选的子类型长度值(Optional sub-TLV(s))字段。其中，VTN ID字段携带主用切片的切片信息，Protection Slice ID字段携带主用切片的保护切片的切片信息，例如，VTN ID字段携带第一切片信息，Protection Slice ID字段携带第二切片信息。其中，PCEP报文可以参见Support for Virtual Transport Network(VTN)in the Path Computation Element Communication Protocol(PCEP)draft-dong-pce-pcep-vtn-01。
在网络设备接收到控制消息后，网络设备创建第一网络切片对应的保护切片(即第二网络切片)的方式可以包括：方式一，预分配保护切片的资源，即，在网络设备接收到控制消息后，在使用第二网络切片之前，网络设备为第二网络切片分配资源。方式二，动态触发部署保护切片的资源，即，在网络设备接收到控制消息后，只是部署第二网络切片而不为第二网络切片分配资源，当确定第二网络切片所保护的第一网络切片故障后，再动态触发为第二网络切片分配资源；当第一网络切片故障修复后，对第二网络切片的资源进行回收。两种方式各种优势，方式一通过预先为保护切片分配资源的方式，在主用切片故障时能够及时的将业务导入到保护切片，为保障业务的服务质量提供了充分的准备；方式二通过动态为保护切片分配资源的方式，在主动切片故障时才触发为保护切片分配对应的资源，当主用切片恢复正常后又触发收回为该保护切片分配的资源，以此达到资源按需分配的目的，提升了资源利用率。
如果网络设备是切片网络的入口节点，那么，S101可以包括：网络设备对进入该切片网络的报文进 行处理，获得第一报文。其中，网络设备对进入该切片网络的报文进行处理，可以是网络设备基于查路由的方式确定网络设备的主用切片为第一网络切片，第一网络切片的保护切片包括第二网络切片，那么，在进入该切片网络的报文中添加第一切片信息和第二切片信息，获得第一报文。
如果网络设备是切片网络的中间节点，那么，S101可以包括：网络设备接收第一报文。其中，第一报文可以是切片网络的入口节点对进入该切片网络的报文进行处理获得的。
第一切片信息，可以是用于指示第一网络切片的信息，例如可以是第一网络切片的Slice ID。第二切片信息，可以是用于指示第二网络切片的信息，例如可以是第二网络切片的Slice ID。
下面对各种场景下第一报文携带第二切片信息的方式进行示例性的介绍。
在一些实现方式中，如果第一报文为SRv6报文，那么，第一报文可以通过第六版互联网协议(Internet Protocol version 6，IPv6)扩展头携带第二切片信息。
作为一个示例，携带第二切片信息的IPv6扩展头可以是第一报文中的逐跳(hop-by-hop，HBH)头。例如，第一报文可以通过HBH头的VTN Option携带第二切片信息，VTN Option的格式可以参见图6a所示，该VTN Option可以包括下一个头类型(Next Header)字段、扩展头长度(Hdr Ext Len)字段、选项类型(Option Type)字段、选项数据长度(OptionDateLen)字段、标志位(Flags)、预留(Reserved)字段、Slice ID字段和Protection Slice ID字段，Slice ID字段携带第一切片信息，Protection Slice ID字段携带第二切片信息。又例如，第一报文也可以通过HBH头的VTN Protection Option携带所述第二切片信息，VTN Protection Option可以是HBH头中新增的Option，该VTN Protection Option可以参见图6b所示，该VTN Protection Option可以包括Next Header字段、Hdr Ext Len字段、Option Type字段、OptionDateLen字段和Protection Slice ID字段，Protection Slice ID字段携带第二切片信息，该情况下，第一切片信息可以携带在第一报文的HBH头的VTN Option中，该VTN Option比图6a所示的VTN Option仅少Protection Slice ID字段。
作为另一个示例，携带第二切片信息的IPv6扩展头可以是第一报文中的目的选项头(Destination Options Header，DOH)。例如，第一报文可以通过DOH的Slice Protection Option携带第二切片信息，Slice Protection Option的格式可以参见图6c所示，该Slice Protection Option可以包括Next Header字段、Hdr Ext Len字段、Option Type字段、OptionDateLen字段和Protection Slice ID字段，Protection Slice ID字段携带第二切片信息，该情况下，第一切片信息可以携带在第一报文的HBH头的VTN Option中，该VTN Option比图6a所示的VTN Option仅少Protection Slice ID字段。
上述图6a～图6c中除了本申请实施例扩展增加的用于携带第二切片信息的字段或Option，其他内容可以参见Carrying Virtual Transport Network(VTN)Information in IPv6Extension Header draft-ietf-6man-enhanced-vpn-vtn-id-02。
在另一些实现方式中，如果第一报文为SR MPLS报文，那么，第一报文可以通过MPLS标签或扩展头携带第二切片信息。
作为一个示例，携带第二切片信息的可以是第一报文中的MPLS标签。例如，第一报文可以通过MPLS VTN Extension Header的VTN Protection ID携带第二切片信息，MPLS VTN Extension Header的格式可以参见图7a所示，该MPLS VTN Extension Header可以包括Next Header(也可以记作NH)字段、头长度(也可以记作HLEN)字段、Flags、Reserved字段、VTN ID字段和VTN Protection ID字段，VTN ID字段携带第一切片信息，VTN Protection ID字段携带第二切片信息。图7a中除了本申请实施例扩展增加的VTN Protection ID字段，其他内容可以参见Carrying Virtual Transport Network(VTN)Information in MPLS Packet draft-li-mpls-enhanced-vpn-vtn-id-03。
作为另一个示例，携带第二切片信息的可以是第一报文中MPLS标签栈后的扩展头。例如，第一报文的格式可以参见图7b所示，该第一报文中的MPLS Label Stack(标签栈)之后，包括多个可使用的扩展头(Extension Header)，第一报文可以使用任意一个未被占用的Extension Header携带第二切片信息。图7b中第一报文的结构可以参见MPLS Network Actions using Post-Stack Extension Headers draft-song-mpls-extension-header-11。
S102，在确定所述第一网络切片故障时，所述网络设备采用所述第二网络切片转发所述第一报文。
网络设备确定第一网络切片故障，可以指网络设备确定第一网络切片不可用或第一网络切片发生拥塞。或者，网络设备确定第一网络切片故障，也可以指网络设备确定主用路径故障，并且确定该网络网络上与该主用路径的备用路径对应的主接口上未部署第一网络切片或部署的第一网络切片不可用又或部署的第一网络切片发生拥塞。
在一些实现方式中，在S101之前，该方法100还可以包括：网络设备获得同样包括第一切片信息和第二切片信息的第二报文，该第二报文和S101中的第一报文的目的地相同；在确定第一网络切片正常时，该网络设备根据第一切片信息确定第一出接口和第一下一跳；并且，该网络设备从所述第一出接口向所述第一下一跳发送所述第二报文。而对于S101获得的第一报文，S102例如可以包括：该网络设备根据第二切片信息确定第二出接口和第二下一跳；并且，网络设备从所述第二出接口向所述第二下一跳发送所述第一报文。其中，第二下一跳和第一下一跳可以相同也可以不同，第一出接口和第二出接口可以相同也可以不同。例如，对应到图2b所示的场景中，第一网络切片对应切片1，第二网络切片对应切片2，第二报文对应报文1时，第一出接口为主接口1，第一下一跳为网络设备3；第一报文对应报文1时，第二出接口为主接口1，第二下一跳为网络设备3。又例如，对应到图3b所示的场景中，第一网络切片对应切片1，第二网络切片对应切片2，第二报文对应报文1时，第一出接口为主接口1，第一下一跳为网络设备3；第一报文对应报文1时，第二出接口为主接口2，第二下一跳为网络设备5。
下面对可能的切片保护模式进行示例性的介绍。
在一些实现方式中，在分配网络切片的保护切片时，可以为一个主用切片分配一个保护切片。方法100的S101～S102中，第一网络切片为主用切片，第二网络切片为第一网络切片的保护切片。
作为一个示例，由于在主用切片正常的情况下，保护切片通常是空闲状态，那么，为了更好的利用资源，还可以设置两个网络切片互为保护关系，例如，第一网络设备为第二网络切片的保护切片，第二网络设备为第一网络切片的保护切片。那么，上述S101～S102中第一报文是以第一网络切片为主用切片的报文，能够在确定第一网络切片故障后将第一报文导入到第二网络切片，同理，对于以第二网络切片为主用切片的第三报文，该方法100还可以包括：网络设备接收包括第一切片信息和第二切片信息的第三报文，在确定第二网络切片故障时，该网络设备采用第一网络切片转发所述第三报文。如此，不仅能够保障承载于各网络切片的业务的服务质量，还能够一定程度上提高资源利用率。
作为另一个示例，由于在主用切片正常的情况下，保护切片通常是空闲状态，那么，可以为符合条件的多个主用切片(如属于同一租户的多个主用切片)分配同一个保护切片，例如，第二网络切片不仅为第一网络切片的保护切片，还作为第四网络切片的保护切片。那么，上述S101～S102中第一报文是以第一网络切片为主用切片的报文，能够在确定第一网络切片故障后将第一报文导入到第二网络切片，同理，对于以第四网络切片为主用切片的第四报文，该方法100还可以包括：网络设备接收包括第四切片信息和第二切片信息的第四报文，在确定第四网络切片故障时，该网络设备采用第二网络切片转发所述第四报文。如此，由于第一网络切片和第四网络切片同时故障的几率较低，所以，该实施例也能够保障承载于各网络切片的业务的服务质量，并且在一定程度上也提高资源利用率。
在另一些实现方式中，在分配网络切片的保护切片时，可以为一个主用切片分配多个保护切片，多个保护切片之间可以具有保护的优先级关系。
作为一个示例，该方法100中，第一网络切片为主用切片，第二网络切片为第一网络切片的保护切片，此外，还可以为第一网络切片分配其他的保护切片，所述其他的保护切片可以包括第三网络切片。那么，第一报文除了包括第一切片信息和第二切片信息，还可以包括第三切片信息，第三切片信息指示第三网络切片。第一报文携带第三切片信息的方式，可以参见上述第一报文携带第二切片信息的方式。假设第一网络切片的保护切片中，第二网络切片的优先级高于第三网络切片，那么，S102可以包括：若第一网络设备确定第一网络切片故障，可以查看第二网络切片是否故障，如果第二网络切片没有发生故障，则采用第二网络切片转发第一报文，如果第二网络切片也故障，则采用第三网络切片转发第一报文。如此，通过对网络切片进行至少两个层级的保护，能够更可靠的保障承载于各网络切片的业务的服务质量。
其中，具有保护关系的多个网络切片，可以是相同等级的网络切片，或者，也可以是具有子切片关 系的网络切片。例如，第一网络切片、第二网络切片可以分别是图1中的切片1和切片2；又例如，第一网络切片可以是图1中切片1的子切片，第二网络切片可以是切片1或切片2；再例如，第一网络切片可以是图1中切片2的子切片，第二网络切片可以是切片1或切片2。
可见，该方法100中，通过在报文中携带主用切片的切片信息和保护切片的切片信息，使得报文在切片网络中传输时遇到主用切片故障的情况，能够基于报文中携带的保护切片的切片信息，及时、准确的将报文导入到保护切片中，采用保护切片的资源对该报文进行传输，保障了主用切片故障时报文所属的业务的服务质量要求。
图8为本申请实施例提供的一种报文处理方法200的流程示意图。图8为了更加清楚的介绍本申请实施例提供的方法200，以网络中控制实体和网络设备交互的方式进行描述。该方法200对应本申请实施例提供的第二种可能的实现方式。该方法200中，网络设备指确定主用切片(即下述第一网络切片)故障的网络设备，也就是说，该网络设备是发生故障的链路的入口节点，对应到图1所示的切片网络，网络设备可以是图1所示的切片网络中的网络设备2；控制实体可以对应图1中的控制实体6。
如图8所示，该方法200例如可以包括下述S201～S206：
S201，控制实体向网络设备发送控制消息，该控制消息包括第一切片信息和第二切片信息。
S202，网络设备接收控制实体发送的所述控制消息。
需要说明的是，控制消息、第一切片信息、第二切片信息以及控制消息中携带第一切片信息和第二切片信息的方式，可以参见图4所示的实施例中的介绍。
S203，网络设备将第一切片信息和第二切片信息的对应关系保存在映射关系中。
本申请实施例中，为了节约网络的传输资源，不将主用切片的保护切片对应的切片信息携带在报文中，需要在网络设备本地维护具有保护关系的网络切片的切片信息之间的对应关系，这些对应关系的集合称为映射关系，映射关系在网络设备中可以体现为映射关系表。
具体实现时，当网络设备接收到控制消息后，通过解析控制消息，获得第一切片信息和第二切片信息，从而，将第一切片信息和第二切片信息的对应关系保存在映射关系中，这样，为后续使用该对应关系进行切片保护的场景作好了准备。
S204，网络设备获得第一报文，该第一报文包括第一切片信息，第一切片信息指示第一网络切片。
在一些实现方式中，为了使得本申请实施例提供的网络切片的保护方案能够更加灵活，切片网络中传输的第一报文中除了包括指示主用切片的切片信息(即指示第一网络切片的第一切片信息)之外，还可以包括指示信息，该指示信息用于指示是否对第一网络切片进行切片保护。如果网络设备获得的第一报文中的指示信息指示需要对第一网络切片进行切片保护，则执行下述S205～S206；如果网络设备获得的第一报文中的指示信息指示不需要对第一网络切片进行切片保护，则在网络设备确定第一网络切片故障时，该网络设备可以基于目前的实现方式，将第一报文导入到公共通道进行后续传输。
作为一个示例，指示信息可以包括第一标志位，通过第一标志位的不同取值表达指示信息所指示的不同内容，第一标志位可以记作本地保护(Local Protection，LP)。例如，LP＝第一值时，指示需要对第一网络切片进行切片保护；LP＝第四值时，指示不需要对第一网络切片进行切片保护。其中，第一值例如可以是1，第四值例如可以是0。
举例来说，如果第一报文是SRv6报文，用于携带第一切片信息的是SRv6报文中HBH头的VTN Option，那么，LP可以是VTN Option中任何一个未被定义的标志位。如图9a所示的SRv6报文中HBH头的VTN Option中，LP例如可以是Flags中未被定义的7个标志位中的任意一个，或者，LP例如也可以是Reserved字段中的任意一个比特位。
在另一些实现方式中，第一报文中可能包括的指示信息，除了用于指示是否对第一网络切片进行切片保护，还可以在指示需要对第一网络切片进行切片保护的情况下，指示是否需要刷新切片信息。如果网络设备获得的第一报文中的指示信息指示需要对第一网络切片进行切片保护，并且需要刷新切片信息，那么，在执行完下文中的S205之后，S206中可以基于该指示信息以及确定的保护切片的切片信息，对第一报文中携带的切片信息进行刷新后再进行传输，这样，在确定保护切片的资源更加稳定的情况下， 使得后续传输路径上的网络设备更加可靠，更好的保障了业务的服务质量。如果网络设备获得的第一报文中的指示信息指示需要对第一网络切片进行切片保护，但是不需要刷新切片信息，则后续直接执行S205～S206即可。
作为一个示例，指示信息可以包括第二标志位，通过第二标志位的不同取值表达指示信息所指示的不同内容，第二标志位可以记作切片刷新(Slice Update，SU)。例如，SU＝第二值时，指示需要刷新切片信息；SU＝第三值时，指示不需要刷新切片信息。其中，第二值例如可以是1，第三值例如可以是0。
举例来说，如果第一报文是SRv6报文，用于携带第一切片信息的是SRv6报文中HBH头的VTN Option，那么，SU可以是VTN Option中任何一个未被定义的标志位。如图9b所示的SRv6报文中HBH头的VTN Option中，SU例如可以是Flags中未被定义的7个标志位中的任意一个，或者，SU例如也可以是Reserved字段中的任意一个比特位。
需要说明的是，如果指示信息包括LP和SU，那么，LP和SU可以通过第一报文的不同标志位承载；也可以通过第一报文的相同字段承载，该承载LP和SU的字段的不同取值对应LP和SU的不同指示。
需要说明的是，指示信息可以仅包括LP不包括SU，那么，可以通过默认设置的配置确定在进行切片保护后是否需要刷新报文中的切片信息，例如，默认设置指示需要刷新切片信息，那么，即使报文的指示信息中不包括SU，也可以在进行切片保护后自动刷新切片信息；又例如，默认设置指示不需要刷新切片信息，那么，在报文的指示信息中不包括SU时，在进行切片保护后不刷新切片信息。或者，指示信息可以仅包括SU不包括LP，那么，可以通过默认设置的配置确定是否需要进行切片保护，例如，默认设置指示需要进行切片保护，那么，即使报文的指示信息中不包括LP，也可以在确定主用切片故障后进行切片保护；又例如，默认设置指示不需要进行切片保护，那么，在报文的指示信息中不包括LP时，即使确定主用切片故障也进行切片保护。又或者，指示信息可以包括LP和SU，那么，LP和SU的指示不相互干扰，可以基于各自的取值的指示进行相关操作。
S205，在确定第一网络切片故障时，网络设备根据第一切片信息和映射关系，确定第二切片信息，该映射关系包括第一切片信息和第二切片信息之间的对应关系，第二切片信息指示第二网络切片。
在一些实现方式中，网络设备可以默认基于本地维护的映射关系对切片网络中传输的报文进行切片保护。那么，网络设备获得第一报文后，通过解析第一报文获得第一报文的主用切片为第一网络切片；网络设备确定第一网络切片故障时，从本地维护的映射关系中查找与第一切片信息匹配的对应关系，并根据所匹配到的对应关系中的第二切片信息确定第二网络切片。这样，网络设备确定了第一报文的主用切片的保护切片，为后续第一报文有质量的传输作好了准备。
在另一些实现方式中，第一报文中包括LP，那么，S205可以包括：在确定第一网络切片故障时，网络设备基于LP的取值，确定需求执行切片保护；那么，该网络设备从本地保存的所述映射关系中，获得与第一切片信息对应的第二网络切片。在确定第一网络切片故障时，若网络设备基于LP的取值确定不需求执行切片保护，则该网络设备将第一报文导入公共通道进行后续传输。这样，通过在第一报文中携带LP，使得切片网络对第一报文的处理更加灵活。
S206，网络设备采用第二网络切片转发第一报文。
在一些实现方式中，网络设备可以默认在进行切片保护后是否刷新报文中的切片信息。如果认为在进行切片保护后网络中的保护切片更加可靠，那么，可是设置默认在进行切片保护后刷新报文中的切片信息，S205执行之后，S206可以包括：网络设备将第一报文中的第一切片信息刷新为第二切片信息，获得第二报文，然后，该网络设备采用第二网络切片转发第二报文。如果认为进行切片保护后是网络设备自己的行为，后续网络设备无需对报文进行相应的网络切片的切换，那么，可是设置默认在进行切片保护后不刷新报文中的切片信息，S205执行之后，S206可以包括：网络设备保持第一报文中主用切片的切片信息为第一切片信息，然后，该网络设备采用第二网络切片转发第一报文。这样，网络设备能够按照实际需求配置自身的默认设置，为S206的执行提供了依据。
在另一些实现方式中，第一报文中包括SU，那么，S206可以包括：若网络设备基于SU的取值确定需求刷新切片信息，则，该网络设备将第一报文中的第一切片信息刷新为第二切片信息，获得第二报 文，然后，该网络设备采用第二网络切片转发第二报文；若网络设备基于SU的取值确定不需求刷新切片信息，则，该网络设备保持第一报文中主用切片的切片信息为第一切片信息，然后，该网络设备采用第二网络切片转发第一报文。这样，通过在第一报文中携带SU，使得切片网络在进行切片保护后对第一报文的处理更加灵活。
需要说明的是，该方法200中，网络设备创建主用切片对应的保护切片的方式、切片保护模式等相关说明，可以参见方法100。
可见，该方法200中，通过网络设备本地维护映射关系，该映射关系中包括具有保护关系的切片信息之间的对应关系，使得报文在切片网络中传输时遇到主用切片故障的情况，能够基于报文中携带的主用切片的切片信息和本地维护的映射关系确定主用切片的保护切片，从而准确的将报文导入到保护切片中，采用保护切片的资源对该报文进行传输，保障了主用切片故障时报文所属的业务的服务质量要求，无需在传输的报文中携带保护切片的切片信息，一定程度上节约了网络的传输资源。
相应的，本申请实施例还提供了一种报文处理装置1000，该装置1000应用于网络设备，如图10所示。该装置1000可以包括：接收单元1001和发送单元1002。其中：
接收单元1001，用于获得第一报文，第一报文包括第一切片信息和第二切片信息，第一切片信息指示第一网络切片，第二切片信息指示第二网络切片。该接收单元1001可以执行图4所示的S101。
发送单元1002，用于在确定第一网络切片故障时，采用第二网络切片转发第一报文。该发送单元1002可以执行图4所示的S102。
在一些实现方式中，所述装置1000还包括：处理单元。接收单元1001，还用于在获得第一报文之前，获得第二报文，所述第二报文包括所述第一切片信息和所述第二切片信息，所述第一报文和所述第二报文的目的地相同；处理单元，用于根据所述第一切片信息确定第一出接口和第一下一跳；发送单元1002，还用于从所述第一出接口向所述第一下一跳发送所述第二报文。
在一些实现方式中，发送单元1002，具体用于：根据所述第二切片信息确定第二出接口和第二下一跳；从所述第二出接口向所述第二下一跳发送所述第一报文。
在一些实现方式中，所述第一报文为SRv6报文，所述第一报文通过IPv6扩展头携带所述第二切片信息。
作为一个示例，所述第一报文通过HBH头的VTN Option携带所述第二切片信息；或者，所述第一报文通过所述HBH头的VTN Protection Option携带所述第二切片信息。
作为另一个示例，所述第一报文通过DOH的Slice Protection Option携带所述第二切片信息。
在一些实现方式中，所述第一报文为SR MPLS报文。作为一个示例，所述第一报文通过MPLS标签携带所述第二切片信息，或者，所述第一报文通过MPLS标签栈后的扩展头携带所述第二切片信息。
在一些实现方式中，接收单元1001，还用于在获得第一报文之前，接收控制实体发送的控制消息，所述控制消息包括所述第一切片信息和所述第二切片信息。其中，所述控制消息为BGP update报文或PCEP报文。
在一些实现方式中，所述装置1000还包括：处理单元。该处理单元，用于在接收控制实体发送的控制消息之后，所述在确定所述第一网络切片故障时采用所述第二网络切片转发所述第一报文之前，为所述第二网络切片分配资源。
在一些实现方式中，发送单元1002，具体用于：在确定所述第一网络切片故障时，为所述第二网络切片分配资源，并且，采用所述第二网络切片转发所述第一报文。
在一些实现方式中，所述第一报文还包括第三切片信息，所述第三切片信息指示第三网络切片，发送单元1002，具体用于：在确定所述第一网络切片故障和所述第二网络切片故障时，采用所述第三网络切片转发所述第一报文。
在一些实现方式中，接收单元1001，还用于获得第三报文，所述第三报文包括所述第一切片信息和所述第二切片信息；发送单元1002，还用于在确定所述第二网络切片故障时，采用所述第一网络切片转发所述第三报文。
在一些实现方式中，接收单元1001，还用于获得第四报文，所述第四报文包括第四切片信息和所述第二切片信息，所述第四切片信息指示第四网络切片；发送单元1002，还用于在确定所述第四网络切片故障时，采用所述第二网络切片转发所述第四报文。
其中，第一网络切片为第二网络切片的子切片。
需要说明的是，本申请提供的装置1000的具体实现方式以及达到的技术效果，可以参见图4所示的方法100的相关说明。
相应的，本申请实施例还提供了一种报文处理装置1100，该装置1100应用于网络设备，如图11所示。该装置1100可以包括：接收单元1101、处理单元1102和发送单元1103。其中：
接收单元1101，用于获得第一报文，第一报文包括第一切片信息，第一切片标识指示第一网络切片。该接收单元1101可以执行图8所示的S204。
处理单元1102，用于在确定第一网络切片故障时，根据第一切片信息和映射关系，确定第二切片信息，映射关系包括第一切片信息和第二切片信息之间的对应关系，第二切片信息指示第二网络切片。该处理单元1102可以执行图8所示的S205。
发送单元1103，用于采用第二网络切片转发第一报文。发送单元1103可以执行图8所示的S206。
在一些实现方式中，所述第一报文还包括指示信息，所述指示信息用于指示对所述第一网络切片进行切片保护。
作为一个示例，所述指示信息包括第一标志位的第一值，所述第一标志位用于指示是否需要执行切片保护，所述第一标志位为所述第一值用于指示需要执行切片保护。
在一些实现方式中，处理单元1102，具体用于：基于所述第一报文中所述第一标志位的第一值，确定需求执行切片保护；从本地保存的所述映射关系中，获得与所述第一切片信息对应的所述第二网络切片。
在一些实现方式中，所述指示信息还用于指示是否刷新切片信息。
作为一个示例，所述指示信息还包括第二标志位，所述第二标志位用于指示是否需要刷新切片信息，所述第二标志位为第二值用于指示需要刷新切片信息，所述第二标志位为第三值用于指示不需要刷新切片信息。
作为另一个示例，若所述第一报文中所述第二标志位为所述第二值，发送单元1103，具体用于：将所述第一报文中的所述第一切片信息替换为所述第二切片信息，获得第二报文；采用所述第二网络切片转发所述第二报文。
其中，所述第一报文可以为SRv6报文，所述第一报文通过HBH头的VTN Option携带所述指示信息。
在一些实现方式中，接收单元1101，还用于在获得第一报文之前，接收控制实体发送的控制消息，所述控制消息包括所述第一切片信息和所述第二切片信息；处理单元1102，还用于将所述第一切片信息和所述第二切片信息的对应关系保存在所述映射关系中。其中，控制消息可以为BGP update报文或PCEP报文。该实现方式中，接收单元1101可以执行图8所示的S201～S202，处理单元1102可以执行图8所示的S203。
需要说明的是，本申请提供的装置1100的具体实现方式以及达到的技术效果，可以参见图8所示的方法200的相关说明。
参见图12，本申请实施例提供了一种网络设备1200(也可以称为通信设备1200)。该网络设备1200可以是上述任一实施例中的网络设备，例如可以是图1中的各网络设备；又例如也可以是方法100中的网络设备，又例如也可以是方法200中的网络设备。网络设备1200可以实现上述实施例中各种网络设备的功能。或者，该网络设备1200可以是上述任一实施例中的控制实体，例如可以是图1中的控制实体6，又例如也可以是方法100中的控制实体，又例如也可以是方法200中的控制实体。网络设备1200可以实现上述实施例中各控制实体的功能。该网络设备1200包括至少一个处理器1201，总线系统1202， 存储器1203以及至少一个通信接口1204。
该网络设备1200是一种硬件结构的装置，可以用于实现图10所示的报文处理装置1000中的功能模块。例如，本领域技术人员可以想到图10所示的报文处理装置1000中的处理单元可以通过该至少一个处理器1201调用存储器1203中的代码来实现。或者，该网络设备1200是一种硬件结构的装置，可以用于实现图11所示的报文处理装置1100中的功能模块。例如，本领域技术人员可以想到图11所示的报文处理装置1100中的处理单元1102可以通过该至少一个处理器1201调用存储器1203中的代码来实现。
可选的，该网络设备1200还可用于实现上述任一实施例中网络设备的功能。
可选的，上述处理器1201可以是一个通用中央处理器(central processing unit，CPU)，网络处理器(network processor，NP)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本申请方案程序执行的集成电路。
上述总线系统1202可包括一通路，在上述组件之间传送信息。
上述通信接口1204，用于与其他设备或通信网络通信。
上述存储器1203可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过总线与处理器相连接。存储器也可以和处理器集成在一起。
其中，存储器1203用于存储执行本申请方案的应用程序代码，并由处理器1201来控制执行。处理器1201用于执行存储器1203中存储的应用程序代码，从而实现本申请方法中的功能。
在具体实现中，作为一种实施例，处理器1201可以包括一个或多个CPU，例如图12中的CPU0和CPU1。
在具体实现中，作为一种实施例，该网络设备1200可以包括多个处理器，例如图10中的处理器1201和处理器1207。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
图13是本申请实施例提供的另一种网络设备1300(也可以称为通信设备1300)的结构示意图，网络设备1300可以是上述任一实施例中的网络设备或控制实体，可以是图1中的各网络设备或控制实体6；又例如也可以是方法100中的网络设备或控制实体；又例如也可以是方法200中的网络设备或控制实体。网络设备1300可以实现上述实施例中各种网络设备或控制实体的功能。
网络设备1300包括：主控板1310和接口板1330。
主控板1310也称为主处理单元(main processing unit，MPU)或路由处理卡(route processor card)，主控板1310对网络设备1300中各个组件的控制和管理，包括路由计算、设备管理、设备维护、协议处理功能。主控板1310包括：中央处理器1311和存储器1312。
接口板1330也称为线路接口单元卡(line processing unit，LPU)、线卡(line card)或业务板。接口板1330用于提供各种业务接口并实现数据包的转发。业务接口包括而不限于以太网接口、POS(Packet over SONET/SDH)接口等，以太网接口例如是灵活以太网业务接口(Flexible Ethernet Clients，FlexE Clients)。接口板1330包括：中央处理器1331、网络处理器1332、转发表项存储器1334和物理接口卡(ph8sical interface card，PIC)1333。
接口板1330上的中央处理器1331用于对接口板1330进行控制管理并与主控板1310上的中央处理器1311进行通信。
网络处理器1332用于实现报文的转发处理。网络处理器1332的形态可以是转发芯片。具体而言，上行报文的处理包括：报文入接口的处理，转发表查找；下行报文的处理：转发表查找等等。
物理接口卡1333用于实现物理层的对接功能，原始的流量由此进入接口板1330，以及处理后的报文从该物理接口卡1333发出。物理接口卡1333包括至少一个物理接口，物理接口也称物理口，物理接口卡1333对应于系统架构中的FlexE物理接口。物理接口卡1333也称为子卡，可安装在接口板1330上，负责将光电信号转换为报文并对报文进行合法性检查后转发给网络处理器1332处理。在一些实施例中，接口板1330的中央处理器1331也可执行网络处理器1332的功能，比如基于通用CPU实现软件转发，从而物理接口卡1333中不需要网络处理器1332。
可选地，网络设备1300包括多个接口板，例如网络设备1300还包括接口板1340，接口板1340包括：中央处理器1341、网络处理器1342、转发表项存储器1344和物理接口卡1343。
可选地，网络设备1300还包括交换网板1320。交换网板1320也可以称为交换网板单元(switch fabric unit，SFU)。在网络设备有多个接口板1330的情况下，交换网板1320用于完成各接口板之间的数据交换。例如，接口板1330和接口板1340之间可以通过交换网板1320通信。
主控板1310和接口板1330耦合。例如。主控板1310、接口板1330和接口板1340，以及交换网板1320之间通过系统总线与系统背板相连实现互通。在一种可能的实现方式中，主控板1310和接口板1330之间建立进程间通信协议(inter-process communication，IPC)通道，主控板1310和接口板1330之间通过IPC通道进行通信。
在逻辑上，网络设备1300包括控制面和转发面，控制面包括主控板1310和中央处理器1331，转发面包括执行转发的各个组件，比如转发表项存储器1334、物理接口卡1333和网络处理器1332。控制面执行路由器、生成转发表、处理信令和协议报文、配置与维护设备的状态等功能，控制面将生成的转发表下发给转发面，在转发面，网络处理器1332基于控制面下发的转发表对物理接口卡1333收到的报文查表转发。控制面下发的转发表可以保存在转发表项存储器1334中。在一些实施例中，控制面和转发面可以完全分离，不在同一设备上。
如果网络设备1300被配置为网络设备，网络处理器1332可以触发物理接口卡1333获得第一报文，所述第一报文包括第一切片信息和第二切片信息，所述第一切片信息指示第一网络切片，所述第二切片信息指示第二网络切片；网络处理器1332还可以触发物理接口卡1333在确定所述第一网络切片故障时，采用所述第二网络切片转发所述第一报文。可选地，网络处理器1332可以触发物理接口卡1333在获得第一报文之前，获得第二报文，所述第二报文包括所述第一切片信息和所述第二切片信息，所述第一报文和所述第二报文的目的地相同；中央处理器1311可以根据所述第一切片信息确定第一出接口和第一下一跳；网络处理器1332还可以触发物理接口卡1333从所述第一出接口向所述第一下一跳发送所述第二报文。
应理解，报文处理装置1000中的接收单元1001、发送单元1102、以及网络设备1200中的通信接口1204可以相当于网络设备1300中的物理接口卡1333或物理接口卡1343；报文处理装置1000中的处理单元、以及网络设备1200中的处理器1201可以相当于网络设备1300中的中央处理器1311或中央处理器1331。
应理解，本申请实施例中接口板1340上的操作与接口板1330的操作一致，为了简洁，不再赘述。应理解，本实施例的网络设备1300可对应于上述各个实施例中的报文处理装置1000或网络设备1200，该网络设备1300中的主控板1310、接口板1330和/或接口板1340可以实现上述各个实施例中的报文处理装置1000或网络设备1200中所具有的功能和/或所实施的各种步骤，为了简洁，在此不再赘述。
如果网络设备1300被配置为网络设备，网络处理器1332可以触发物理接口卡1333获得第一报文，第一报文包括第一切片信息，第一切片标识指示第一网络切片；中央处理器1311可以在确定第一网络切片故障时，根据第一切片信息和映射关系，确定第二切片信息，映射关系包括第一切片信息和第二切片信息之间的对应关系，第二切片信息指示第二网络切片；网络处理器1332还可以触发物理接口卡1333采用第二网络切片转发第一报文。
应理解，报文处理装置1100中的接收单元1101、发送单元1103、以及网络设备1200中的通信接 口1204可以相当于网络设备1300中的物理接口卡1333或物理接口卡1343；报文处理装置1100中的处理单元1102、以及网络设备1200中的处理器1201可以相当于网络设备1300中的中央处理器1311或中央处理器1331。
应理解，本申请实施例中接口板1340上的操作与接口板1330的操作一致，为了简洁，不再赘述。应理解，本实施例的网络设备1300可对应于上述各个实施例中的报文处理装置1100或网络设备1200，该网络设备1300中的主控板1310、接口板1330和/或接口板1340可以实现上述各个实施例中的报文处理装置1100或网络设备1200中所具有的功能和/或所实施的各种步骤，为了简洁，在此不再赘述。
应理解，主控板可能有一块或多块，有多块的时候可以包括主用主控板和备用主控板。接口板可能有一块或多块，网络设备的数据处理能力越强，提供的接口板越多。接口板上的物理接口卡也可以有一块或多块。交换网板可能没有，也可能有一块或多块，有多块的时候可以共同实现负荷分担冗余备份。在集中式转发架构下，网络设备可以不需要交换网板，接口板承担整个系统的业务数据的处理功能。在分布式转发架构下，网络设备可以有至少一块交换网板，通过交换网板实现多块接口板之间的数据交换，提供大容量的数据交换和处理能力。所以，分布式架构的网络设备的数据接入和处理能力要大于集中式架构的设备。可选地，网络设备的形态也可以是只有一块板卡，即没有交换网板，接口板和主控板的功能集成在该一块板卡上，此时接口板上的中央处理器和主控板上的中央处理器在该一块板卡上可以合并为一个中央处理器，执行两者叠加后的功能，这种形态设备的数据交换和处理能力较低(例如，低端交换机或路由器等网络设备)。具体采用哪种架构，取决于具体的组网部署场景。
在一些可能的实施例中，上述各网络设备或网络设备可以实现为虚拟化设备。例如，虚拟化设备可以是运行有用于发送报文功能的程序的虚拟机(英文：Virtual Machine，VM)，虚拟机部署在硬件设备上(例如，物理服务器)。虚拟机指通过软件模拟的具有完整硬件系统功能的、运行在一个完全隔离环境中的完整计算机系统。可以将虚拟机配置为本申请实施例中的各网络设备或控制实体。例如，可以基于通用的物理服务器结合网络功能虚拟化(Network Functions Virtualization，NFV)技术来实现各网络设备或网络设备。各网络设备或网络设备为虚拟主机、虚拟路由器或虚拟交换机。本领域技术人员通过阅读本申请即可结合NFV技术在通用物理服务器上虚拟出具有上述功能的各网络设备或网络设备，此处不再赘述。
应理解，上述各种产品形态的网络设备，分别具有上述方法实施例中各网络设备或通信设备的任意功能，此处不再赘述。
本申请实施例还提供了一种芯片，包括处理器和接口电路，接口电路，用于接收指令并传输至处理器；处理器，例如可以是本申请实施例中报文处理装置的一种具体实现形式，可以用于执行上述路由选路的方法。其中，所述处理器与存储器耦合，所述存储器用于存储程序或指令，当所述程序或指令被所述处理器执行时，使得该芯片系统实现上述任一方法实施例中的方法。
可选地，该芯片系统中的处理器可以为一个或多个。该处理器可以通过硬件实现也可以通过软件实现。当通过硬件实现时，该处理器可以是逻辑电路、集成电路等。当通过软件实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现。
可选地，该芯片系统中的存储器也可以为一个或多个。该存储器可以与处理器集成在一起，也可以和处理器分离设置，本申请并不限定。示例性的，存储器可以是非瞬时性处理器，例如只读存储器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)或其他集成芯片。
此外，本申请实施例还提供了一种计算机可读存储介质，计算机可读存储介质中存储有程序代码或指令，当其在计算机上运行时，使得计算机执行以上图4或图8所示实施例中任意一种实现方式下的方 法。
此外，本申请实施例还提供了一种计算机程序产品，当其在计算机上运行时，使得计算机执行前述方法100或方法200中任意一种实现方式的方法。
应理解，本申请实施例中提到的“基于根据A确定B”并不意味着仅仅根据A确定B，还可以根据A和/或其它信息确定B。
本申请中提到的“第一报文”、“第一切片信息”等名称中的“第一”只是用来做名字标识，并不代表顺序上的第一。该规则同样适用于“第二”等。
通过以上的实施方式的描述可知，本领域的技术人员可以清楚地了解到上述实施例方法中的全部或部分步骤可借助软件加通用硬件平台的方式来实现。基于这样的理解，本申请的技术方案可以以软件产品的形式体现出来，该计算机软件产品可以存储在存储介质中，如只读存储器(英文：read-only memory，ROM)/RAM、磁碟、光盘等，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者诸如路由器等网络通信设备)执行本申请各个实施例或者实施例的某些部分所述的方法。
本说明书中的各个实施例均采用递进的方式描述，各个实施例之间相同相似的部分互相参见即可，每个实施例重点说明的都是与其他实施例的不同之处。尤其，对于系统实施例和设备实施例而言，由于其基本相似于方法实施例，所以描述得比较简单，相关之处参见方法实施例的部分说明即可。以上所描述的设备及系统实施例仅仅是示意性的，其中作为分离部件说明的模块可以是或者也可以不是物理上分开的，作为模块显示的部件可以是或者也可以不是物理模块，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
以上所述仅是本申请的优选实施方式，并非用于限定本申请的保护范围。应当指出，对于本技术领域的普通技术人员来说，在不脱离本申请的前提下，还可以作出若干改进和润饰，这些改进和润饰也应视为本申请的保护范围。

Claims (30)

  1. 一种报文处理方法，其特征在于，所述方法包括：
    网络设备获得第一报文，所述第一报文包括第一切片信息和第二切片信息，所述第一切片信息指示第一网络切片，所述第二切片信息指示第二网络切片；
    在确定所述第一网络切片故障时，所述网络设备采用所述第二网络切片转发所述第一报文。
  2. 根据权利要求1所述的方法，其特征在于，在所述网络设备获得第一报文之前，所述方法还包括：
    所述网络设备获得第二报文，所述第二报文包括所述第一切片信息和所述第二切片信息，所述第一报文和所述第二报文的目的地相同；
    所述网络设备根据所述第一切片信息确定第一出接口和第一下一跳；
    所述网络设备从所述第一出接口向所述第一下一跳发送所述第二报文。
  3. 根据权利要求2所述的方法，其特征在于，所述在确定所述第一网络切片故障时，所述网络设备采用所述第二网络切片转发所述第一报文，包括：
    所述网络设备根据所述第二切片信息确定第二出接口和第二下一跳；
    所述网络设备从所述第二出接口向所述第二下一跳发送所述第一报文。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，所述第一报文为基于第六版互联网协议的分段路由SRv6报文，所述第一报文通过第六版互联网协议IPv6扩展头携带所述第二切片信息。
  5. 根据权利要求4所述的方法，其特征在于，所述第一报文通过逐跳HBH头的虚拟传输网络选项VTN Option携带所述第二切片信息；或者，所述第一报文通过所述HBH头的虚拟传输网络保护选项VTN Protection Option携带所述第二切片信息。
  6. 根据权利要求4所述的方法，其特征在于，所述第一报文通过所述目的选项头DOH的切片保护选项Slice Protection Option携带所述第二切片信息。
  7. 根据权利要求1-3任一项所述的方法，其特征在于，所述第一报文为基于多协议标签交换的分段路由SR MPLS报文。
  8. 根据权利要求7所述的方法，其特征在于，所述第一报文通过MPLS标签携带所述第二切片信息，或者，所述第一报文通过MPLS标签栈后的扩展头携带所述第二切片信息。
  9. 根据权利要求1-8任一项所述的方法，其特征在于，在所述网络设备获得第一报文之前，所述方法还包括：
    所述网络设备接收控制实体发送的控制消息，所述控制消息包括所述第一切片信息和所述第二切片信息。
  10. 根据权利要求9所述的方法，其特征在于，所述控制消息为边界网关协议更新BGP update报文或路径计算单元通信协议PCEP报文。
  11. 根据权利要求9或10所述的方法，其特征在于，在所述网络设备接收控制实体发送的控制消息之后，所述在确定所述第一网络切片故障时，所述网络设备采用所述第二网络切片转发所述第一报文之前，所述方法还包括：
    所述网络设备为所述第二网络切片分配资源。
  12. 根据权利要求1-10任一项所述的方法，其特征在于，所述在确定所述第一网络切片故障时，所述网络设备采用所述第二网络切片转发所述第一报文，包括：
    在确定所述第一网络切片故障时，所述网络设备为所述第二网络切片分配资源，并且，所述网络设备采用所述第二网络切片转发所述第一报文。
  13. 根据权利要求1-12任一项所述的方法，其特征在于，所述第一报文还包括第三切片信息，所述第三切片信息指示第三网络切片，所述在确定所述第一网络切片故障时，所述网络设备采用所述第二网络切片转发所述第一报文，包括：
    在确定所述第一网络切片故障和所述第二网络切片故障时，所述网络设备采用所述第三网络切片转发所述第一报文。
  14. 根据权利要求1-13任一项所述的方法，其特征在于，所述方法还包括：
    所述网络设备获得第三报文，所述第三报文包括所述第一切片信息和所述第二切片信息；
    在确定所述第二网络切片故障时，所述网络设备采用所述第一网络切片转发所述第三报文。
  15. 根据权利要求1-14任一项所述的方法，其特征在于，所述方法还包括：
    所述网络设备获得第四报文，所述第四报文包括第四切片信息和所述第二切片信息，所述第四切片信息指示第四网络切片；
    在确定所述第四网络切片故障时，所述网络设备采用所述第二网络切片转发所述第四报文。
  16. 根据权利要求1-15任一项所述的方法，其特征在于，所述第一网络切片为所述第二网络切片的子切片。
  17. 一种报文处理方法，其特征在于，所述方法包括：
    网络设备获得第一报文，所述第一报文包括第一切片信息，所述第一切片信息指示第一网络切片；
    在确定所述第一网络切片故障时，所述网络设备根据所述第一切片信息和映射关系，确定第二切片信息，所述映射关系包括所述第一切片信息和所述第二切片信息之间的对应关系，所述第二切片信息指示第二网络切片；
    所述网络设备采用所述第二网络切片转发所述第一报文。
  18. 根据权利要求17所述的方法，其特征在于，所述第一报文还包括指示信息，所述指示信息用于指示对所述第一网络切片进行切片保护。
  19. 根据权利要求18所述的方法，其特征在于，所述指示信息包括第一标志位的第一值，所述第一标志位用于指示是否需要执行切片保护，所述第一标志位为所述第一值用于指示需要执行切片保护。
  20. 根据权利要求19所述的方法，其特征在于，所述在确定所述第一网络切片故障时，所述网络设备根据所述第一切片信息和映射关系，确定第二切片信息，包括：
    所述网络设备基于所述第一报文中所述第一标志位的第一值，确定需求执行切片保护；
    所述网络设备从本地保存的所述映射关系中，获得与所述第一切片信息对应的所述第二网络切片。
  21. 根据权利权利要求18-20任一项所述的方法，其特征在于，所述指示信息还用于指示是否刷新切片信息。
  22. 根据权利要求21所述的方法，其特征在于，所述指示信息还包括第二标志位，所述第二标志位用于指示是否需要刷新切片信息，所述第二标志位为第二值用于指示需要刷新切片信息，所述第二标志位为第三值用于指示不需要刷新切片信息。
  23. 根据权利要求22所述的方法，其特征在于，若所述第一报文中所述第二标志位为所述第二值，所述网络设备采用所述第二网络切片转发所述第一报文，包括：
    所述网络设备将所述第一报文中的所述第一切片信息替换为所述第二切片信息，获得第二报文；
    所述网络设备采用所述第二网络切片转发所述第二报文。
  24. 根据权利要求18-23任一项所述的方法，其特征在于，所述第一报文为基于第六版互联网协议的分段路由SRv6报文，所述第一报文通过逐跳HBH头的虚拟传输网络选项VTN Option携带所述指示信息。
  25. 根据权利要求17-24任一项所述的方法，其特征在于，在网络设备获得第一报文之前，所述方法还包括：
    所述网络设备接收控制实体发送的控制消息，所述控制消息包括所述第一切片信息和所述第二切片信息；
    所述网络设备将所述第一切片信息和所述第二切片信息的对应关系保存在所述映射关系中。
  26. 根据权利要求25所述的方法，其特征在于，所述控制消息为边界网关协议更新BGP update报文或路径计算单元通信协议PCEP报文。
  27. 一种报文处理装置，其特征在于，应用于网络设备，所述装置包括：
    接收单元，用于获得第一报文，所述第一报文包括第一切片信息和第二切片信息，所述第一切片信息指示第一网络切片，所述第二切片信息指示第二网络切片；
    发送单元，用于在确定所述第一网络切片故障时，采用所述第二网络切片转发所述第一报文。
  28. 一种报文处理装置，其特征在于，应用于网络设备，所述装置包括：
    接收单元，用于获得第一报文，所述第一报文包括第一切片信息，所述第一切片标识指示第一网络切片；
    处理单元，用于在确定所述第一网络切片故障时，根据所述第一切片信息和映射关系，确定第二切片信息，所述映射关系包括所述第一切片信息和所述第二切片信息之间的对应关系，所述第二切片信息指示第二网络切片；
    发送单元，用于采用所述第二网络切片转发所述第一报文。
  29. 一种网络设备，其特征在于，所述网络设备包括存储器和处理器；
    所述存储器，用于存储指令；
    所述处理器，用于执行所述存储器中的所述指令，执行权利要求1-26任一项所述的方法。
  30. 一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得所述计算机执行以上权利要求1-26任一项所述的方法。
PCT/CN2023/103105 2022-10-28 2023-06-28 一种报文处理方法及相关设备 WO2024087691A1 (zh)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202211336208.1 2022-10-28
CN202211336208 2022-10-28
CN202211625229.5A CN117955814A (zh) 2022-10-28 2022-12-16 一种报文处理方法及相关设备
CN202211625229.5 2022-12-16

Publications (1)

Publication Number Publication Date
WO2024087691A1 true WO2024087691A1 (zh) 2024-05-02

Family

ID=90797146

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/103105 WO2024087691A1 (zh) 2022-10-28 2023-06-28 一种报文处理方法及相关设备

Country Status (2)

Country Link
CN (1) CN117955814A (zh)
WO (1) WO2024087691A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112995030A (zh) * 2021-02-07 2021-06-18 中兴通讯股份有限公司 一种业务处理方法、装置、存储介质及电子装置
US20210321325A1 (en) * 2020-04-10 2021-10-14 Cisco Technology, Inc. Failover and management of multi-vendor network slices
CN113542114A (zh) * 2020-04-20 2021-10-22 华为技术有限公司 路由配置方法和路由配置装置
CN113973062A (zh) * 2021-10-27 2022-01-25 中国联合网络通信集团有限公司 一种网络切换方法、装置及计算机可读存储介质
CN114826918A (zh) * 2021-01-29 2022-07-29 华为技术有限公司 一种报文转发的方法、报文处理方法及设备
CN115473765A (zh) * 2021-06-11 2022-12-13 北京华为数字技术有限公司 报文传输方法、设备及系统

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210321325A1 (en) * 2020-04-10 2021-10-14 Cisco Technology, Inc. Failover and management of multi-vendor network slices
CN113542114A (zh) * 2020-04-20 2021-10-22 华为技术有限公司 路由配置方法和路由配置装置
CN114826918A (zh) * 2021-01-29 2022-07-29 华为技术有限公司 一种报文转发的方法、报文处理方法及设备
CN112995030A (zh) * 2021-02-07 2021-06-18 中兴通讯股份有限公司 一种业务处理方法、装置、存储介质及电子装置
CN115473765A (zh) * 2021-06-11 2022-12-13 北京华为数字技术有限公司 报文传输方法、设备及系统
CN113973062A (zh) * 2021-10-27 2022-01-25 中国联合网络通信集团有限公司 一种网络切换方法、装置及计算机可读存储介质

Also Published As

Publication number Publication date
CN117955814A (zh) 2024-04-30

Similar Documents

Publication Publication Date Title
US20220255862A1 (en) Packet forwarding method, device, storage medium, and system
US20230018292A1 (en) Packet transmission method and apparatus, and network device
WO2022078415A1 (zh) 报文转发方法以及网络设备
WO2022105927A1 (zh) 一种通告网络设备处理能力的方法、设备和系统
US20230208751A1 (en) Packet forwarding method, device, and system
US10778544B2 (en) Dynamic allocation of processing queues for control packets in software defined networks
US20230412508A1 (en) Packet processing method and related apparatus
US20230224241A1 (en) Path Identity Allocation Method, System, and Apparatus, Device, and Storage Medium
WO2024087691A1 (zh) 一种报文处理方法及相关设备
US20220255864A1 (en) Service packet forwarding method, apparatus, and computer storage medium
WO2022143572A1 (zh) 一种报文处理方法及相关设备
CN112104539B (zh) 分段ngmvpn中的信息交互方法、装置和系统
US20230224245A1 (en) Packet Transmission Method and Apparatus
WO2023213216A1 (zh) 一种报文处理的方法及相关设备
WO2023116449A1 (zh) 一种控制网络切片状态的方法及相关设备
CN113381930B (zh) 用于虚拟路由器冗余的组负载均衡
WO2024021976A1 (zh) 一种报文处理的方法及相关设备
WO2023130957A1 (zh) 一种路由选路的方法及相关设备
US20240214298A1 (en) Method, apparatus, device, and system for transmitting network layer reachability information, and medium
US20220174013A1 (en) Communication Method and Apparatus
CN116389381A (zh) 一种共享切片资源的方法及相关设备
JP2024500907A (ja) ルート伝送方法および装置
CN114915518A (zh) 一种报文传输方法、系统及设备
CN114143142A (zh) 一种报文传输方法及装置
CN116938800A (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: 23881280

Country of ref document: EP

Kind code of ref document: A1