Patent Application
20240007399
This disclosure relates to the field of communication technologies, and in particular, to a message processing method, a network device, and a controller.
A network slice (or a logically isolated network partition) refers to a complete, autonomous, and independently operated and maintained logical network formed by organizing related service functions and network resources that are on a physical network. Based on a network slicing technology, a same physical network can form a plurality of virtual networks that have independent management, independent control, and independent forwarding capabilities and that are isolated from each other. In this way, services with differentiated bearer requirements can be supported. Therefore, network slicing has become a key technology in a future network architecture.
Information about a network slice on a control plane is often inconsistent with information about the network slice on a forwarding plane, which affects an effect of controlling a message forwarding path by the control plane.
Embodiments of this disclosure provide a message processing method, a network device, and a controller, to help improve an effect of controlling a message forwarding path by the controller. The technical solutions are described below.
According to a first aspect, a message processing method is provided. The method includes a network device that generates an advertisement message. The advertisement message includes an identifier of a network slice and path information of one or more paths in the network slice. The network device sends the advertisement message to a controller.
In the foregoing method, the network device includes slice information, such as the identifier of the network slice and the information about the path in the network slice, in the message, and reports the message to the controller, so that slice information on a forwarding plane is consistent with slice information on a control plane, and the controller controls a message forwarding path based on the slice information on the network device. Therefore, this helps improve the effect of controlling the message forwarding path by the controller.
Optionally, the advertisement message may be a Border Gateway Protocol (BGP)-Link State (LS) message.
A protocol message, such as the BGP-LS message, is extended to report the identifier of the network slice, so that an existing protocol can be reused, and implementation complexity is reduced.
Optionally, the identifier of the network slice is carried in a segment routing (SR) policy candidate path descriptor type-length-value (TLV) of the BGP-LS message.
Optionally, the identifier of the network slice is carried in a sub-TLV of the SR policy candidate path descriptor TLV. The sub-TLV includes a slice identifier (ID) field, and the slice ID field stores the identifier of the network slice.
A sub-TLV is extended to carry a slice identifier, so that overheads are low, and implementation complexity is low.
Optionally, the path information includes a segment ID (SID) list corresponding to the one or more paths.
The SID list of the path and the identifier of the network slice are reported to the controller together, to indicate a network slice to which the SID list belongs, which helps use the SID list to perform path computation, path optimization, and the like in the network slice.
Optionally, the path information further includes status information of the one or more paths.
The status information of the path and the identifier of the network slice are reported to the controller together, to indicate a status of the path in the network slice, which helps the controller monitor the status of the path in the network slice in real time.
Optionally, the status information includes one or more of the following information: at least one of traffic statistics information, network performance information, and connectivity information.
The identifier of the network slice, together with the traffic statistics information, the network performance information, the connectivity information, or the like, is reported to the controller, which helps the controller perform traffic statistics collection, performance monitoring, connectivity monitoring, and the like on the network slice, to support more application scenarios.
Optionally, the connectivity information identifies whether a corresponding path is available or unavailable.
Optionally, the advertisement message indicates the controller to control a message forwarding path based on the identifier of the network slice and the path information.
Optionally, the network device is an ingress node of an SR network.
The identifier of the network slice and the path information of the path in the network slice are reported through the ingress node of the SR network. Because the ingress node is a node responsible for encapsulating path information, such as a SID list, when a service message enters the SR network, it is beneficial to improving accuracy of reported information.
According to a second aspect, a message processing method is provided and the message processing method includes the following.
A controller receives an advertisement message sent by a network device. The advertisement message includes an identifier of a network slice and path information of one or more paths in the network slice.
The controller controls a message forwarding path based on the identifier of the network slice and the path information of the one or more paths in the network slice.
Optionally, the advertisement message may be a BGP-LS message.
Optionally, the identifier of the network slice is carried in an SR policy candidate path descriptor TLV of the BGP-LS message.
Optionally, the identifier of the network slice is carried in a sub-TLV of the SR policy candidate path descriptor TLV. The sub-TLV includes a slice ID field, and the slice ID field stores the identifier of the network slice.
Optionally, the path information includes a SID list corresponding to the one or more paths.
Optionally, the path information further includes status information of the one or more paths.
Optionally, the status information includes one or more of the following information: at least one of traffic statistics information, network performance information, and connectivity information.
Optionally, the connectivity information identifies whether a corresponding path is available or unavailable.
Optionally, that the controller controls a message forwarding path based on the identifier of the network slice and the path information of the one or more paths in the network slice includes the following.
The controller obtains a second path when determining that a first path in the one or more paths is unavailable. The second path is configured to bear traffic forwarded on the first path.
Optionally, that the controller controls a message forwarding path based on the identifier of the network slice and the path information of the one or more paths in the network slice includes the following.
The controller obtains the second path when determining that a bandwidth utilization rate of the first path in the one or more paths reaches a threshold. The second path is configured to bear the traffic forwarded on the first path.
Optionally, the bandwidth utilization rate of the first path is a bandwidth utilization rate of one or more links on the first path.
Optionally, the second path is a path in a network slice corresponding to the identifier of the network slice.
Optionally, the second path is calculated by the controller based on a network topology of the network slice corresponding to the identifier of the network slice.
Optionally, the method further includes that the controller sends a SID list corresponding to the second path to the network device.
According to a third aspect, a network device is provided configured to perform the first aspect or any possible implementation of the first aspect. Further, the network device includes a unit configured to perform the method according to the first aspect or any possible implementation of the first aspect.
In some embodiments, the unit in the network device is implemented through software, and the unit in the network device is a program module. In some other embodiments, the unit in the network device is implemented through hardware or firmware. For specific details of the network device provided in the third aspect, refer to the first aspect or any possible implementation of the first aspect. Details are not described herein again.
According to a fourth aspect, a controller is provided configured to perform the method in the second aspect or any possible implementation of the second aspect. Further, the controller includes a unit configured to perform the method in the second aspect or any possible implementation of the second aspect.
In some embodiments, the unit in the controller is implemented through software, and the unit in the controller is a program module. In some other embodiments, the unit in the controller is implemented through hardware or firmware. For specific details of the controller provided in the fourth aspect, refer to the second aspect or any possible implementation of the second aspect. Details are not described herein again.
According to a fifth aspect, a network device is provided. The network device includes a processor and a communication interface. The processor is configured to execute instructions, so that the network device is enabled to perform the method according to the first aspect or any possible implementation of the first aspect. The communication interface is configured to send or receive a message. For specific details of the network device provided in the fifth aspect, refer to the first aspect or any possible implementation of the first aspect or the second aspect or any possible implementation of the second aspect. Details are not described herein again.
According to a sixth aspect, a controller is provided. The controller includes a processor and a communication interface. The processor is configured to execute instructions, so that the controller is enabled to perform the method according to the second aspect or any possible implementation of the second aspect. The communication interface is configured to send or receive a message. For specific details of the controller provided in the sixth aspect, refer to the second aspect or any possible implementation of the second aspect. Details are not described herein again.
According to a seventh aspect, a computer-readable storage medium is provided. The storage medium stores at least one instruction. When the at least one instruction is executed on a network device, the network device is enabled to perform the method according to the first aspect or any possible implementation of the first aspect.
According to an eighth aspect, a computer-readable storage medium is provided. The storage medium stores at least one instruction. When the at least one instruction is executed on a controller, the controller is enabled to perform the method according to the second aspect or any possible implementation of the second aspect.
According to a ninth aspect, a computer program product is provided. The computer program product includes computer instructions. The computer instructions are stored in a computer-readable storage medium. A processor of a network device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the network device is enabled to perform the method according to the first aspect or any possible implementation of the first aspect.
According to a tenth aspect, a computer program product is provided. The computer program product includes computer instructions. The computer instructions are stored in a computer-readable storage medium. A processor of a controller reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the controller is enabled to perform the method according to the second aspect or any possible implementation of the second aspect.
According to an eleventh aspect, a chip is provided. When the chip runs on a network device, the network device is enabled to perform the method according to the first aspect or any possible implementation of the first aspect.
According to a twelfth aspect, a chip is provided. When the chip runs on a controller, the controller is enabled to perform the method according to the second aspect or any possible implementation of the second aspect.
According to a thirteenth aspect, a network system is provided. The network system includes a network device and a controller. The network device is configured to perform the first aspect or any possible implementation of the first aspect. The controller is configured to perform the method according to the second aspect or any possible implementation of the second aspect.
To make the objectives, technical solutions, and advantages of this disclosure clearer, the following further describes the implementations of this disclosure in detail with reference to the accompanying drawings.
The following explains and describes some terms and concepts in embodiments of this disclosure.
(1) Network slice:
A network slice, also referred to as network slicing, is a logical network. Network slicing enables an operator to build a plurality of dedicated, virtualized, and isolated logical networks on a general physical network to meet different requirements of different customers for network resources. For example, a physical network is divided into three network slices: a network slice A, a network slice B, and a network slice C. The network slice A is configured to bear traffic of a video service. The network slice B is configured to bear traffic of an automatic driving service, and the network slice C is configured to bear traffic of a voice call service.
(2) SR:
SR is a technology of forwarding a message based on source routing. A basic principle of the SR is to include a segment list in a header of a data message and transmit it together with the message. The segment list is an ordered list including a segment. The SR technology includes SR Multi-Protocol Label Switching (MPLS) technology and SR over Internet Protocol (IP) version 6 (IPv6) (or SRv6) technology. In SR-MPLS, the segment list is a label stack. In SRv6, the segment list is an IPv6 address list.
(3) SRv6:
SRv6 is a technology of forwarding an IPv6 message based on source routing. A basic principle of the SRv6 is that a head node adds a SR header (SRH) or a routing extension header to an IPv6 message. The SRH includes a SID list. An intermediate node uses the SID in the SRH to update a destination address in an IPv6 basic header of the IPv6 message, to implement hop-by-hop forwarding.
(4) Sr Policy:
An SR policy is a technology of including a segment list in a data message to implement traffic engineering. The traffic engineering is a technology of supporting forwarding of specified traffic through a specified path in a network based on an optimization objective. The specified path is generally a non-Internal Gateway Protocol (IGP) shortest path. The SR policy includes an MPLS-based SR-MPLS policy and an SRv6-based SRv6 policies. An SR policy includes at least one or more candidate paths. A candidate path includes one or more segment lists. An SR policy is generally identified by three types of information: a headend, a color, and an endpoint.
(5) Headend:
A headend is a node on which an SR policy is generated. The headend is responsible of importing a data message to the SR policy. In other words, in a tunnel created based on the SR policy, the headend is a source device of the tunnel.
(6) Color:
A color is for distinguishing different SR policies between a headend and an endpoint in a same pair. The color is generally a 32-bit value. The color generally represents an intention, that is, a condition that needs to be met for the data message to reach the endpoint from the headend. For example, there are two SR policies between the headend and the endpoint. A color of an SR policy A is a color 10. A color of an SR policy B is a color 20. The color 10 indicates that a delay is less than a specified delay threshold, and the color 20 indicates that a specified node is not passed through.
(7) Endpoint:
An endpoint is an end node of an SR policy. In other words, in a tunnel created based on the SR policy, the endpoint is a destination device of the tunnel. The endpoint is generally represented by an IP address.
(8) Candidate Path:
A candidate path is a path that can be selected in an SR policy. The candidate path indicates a manner in which the data message is forwarded from a headend of the SR policy to an endpoint of the SR policy. Each candidate path has a priority. The priority is for selecting the candidate path from the SR policy. An effective candidate path with a highest priority in an SR policy is a primary path in the SR policy. The candidate path may be learned in different manners such as a local configuration, a Network Configuration Protocol (NETCONF), a Path Computation Element Communication protocol (PCEP), or a BGP.
(9) Telemetry:
Telemetry is a technology of collecting data from a device remotely. A basic principle of telemetry is that a network device actively reports collected data in a push mode. The collected data includes, but is not limited to, traffic statistics information, a message loss rate, a central processing unit (CPU) occupancy rate, a memory occupancy rate, and the like. Based on the telemetry, a more real-time and higher-speed data collection function is provided, which helps quickly locate a network fault.
(10) Sid List:
A SID list indicates a message forwarding path. The SID list is an ordered list including one or more SIDs. The SID list indicates a corresponding path. Each SID is in a form of an IPv6 address. Therefore, the SID list can be understood as an explicit IPv6 address stack. The SID list is inserted into a data message on an ingress node of an SR network.
(11) SID:
A SID is an identifier of a segment (or a fragment). The segment represents a specified operation. The operation represents by the segment may be any operation related to message processing. For example, the segment represents forwarding a message to a specified node, forwarding a message through a specified egress interface, and the like. Optionally, when being applied to an SRv6 scenario, the SID is an IPv6 address. Alternatively, when being applied to an SR-MPLS scenario, the SID is an MPLS label.
(12) Endpoint (End) SID:
An End SID identifies a destination node in an SR network.
(13) Endpoint with Layer-3 Cross-Connect (End.X) SID:
An End.X SID identifies a link in the SR network.
As demands for mobile and fixed network services of operators continuously increase, it often happens that a plurality of services is deployed on a same network. To ensure that bandwidths of various services are not preempted by other services, bandwidths of different services need to be isolated from each other. There are great differences between traffic characteristics of different types of services borne on the network. For example, it is difficult to estimate the bandwidth of personal fixed broadband services, which are mainly Internet access traffic, requiring large-bandwidth, large-burst, and best-effort services. These services are insensitive to a delay, which may reach 50 milliseconds (ms). Enterprise services include both delay-sensitive services and delay-insensitive services, and generally have a specific bandwidth-delay service level agreement (SLA). Mobile carrier services include delay-sensitive services and delay-insensitive services. Convergence ratios of different service types are quite different.
The requirements in the preceding scenarios can be met through the network slicing technology. In the network slicing technology, Flexible Ethernet (FlexE) interfaces or channelized interfaces are used to divide a physical network into a plurality of hard-isolated network slices. Each network slice independently has a service deployed. Bandwidths of different network slices are hard-isolated and do not affect each other. In addition, mapping between services and physical slices may be implemented through the SRv6, to meet demands of customers for guaranteeing differentiated service SLAs.
Information about a network slice configured on a forwarding plane (for example, a network device) is often inconsistent with information about the network slice on a control plane (for example, a controller).
There are two typical reasons for the slice information inconsistency. One typical reason is that after the controller delivers slice information to the network device, the network device subsequently updates slice information. For example, the controller delivers slice information A to the network device through a BGP-LS message. After obtaining the slice information A sent by the controller, the network device obtains slice information B by using protocols such as NETCONF and PCEP. The network device updates locally configured slice information from the slice information A to the slice information B. As a result, the slice information on the network device is inconsistent with the slice information on the controller. The other typical reason is that the control plane includes a plurality of controllers. After a controller A delivers slice information to the network device, only the controller A on the control plane has the slice information on the network device, and controllers other than the controller A do not have the slice information on the network device.
The slice information inconsistency causes many problems. For example, when the controller performs path computation or optimization based on slice information, because the slice information used by the controller is not actual slice information on the network device, the path computation or optimization performance of the controller has a poor effect.
In embodiments of this disclosure, the network device reports to the controller the slice information such as the identifier of the network slice and the information about the path in the network slice, so that the slice information on the forwarding plane is consistent with the slice information on the control plane. Therefore, the controller can perform tasks of controlling a message forwarding path, such as path computation or path optimization, based on the actual slice information on the network device, so that path control performance of the controller is improved.
A system architecture in embodiments of this disclosure is described below by using an example.
The controller 11 includes, but is not limited to, a server, a personal computer, a host, or the like. The controller 11 is configured to deploy a network slice in a network system, and deploy one or more paths in the network slice to bear a service. Optionally, the controller 11 is further configured to monitor and optimize the one or more paths in the network slice.
The network device 21, the network device 22, and the network device 23 include, but are not limited to, a switch, a router, and the like. The network device 21, the network device 22, and the network device 23 are configured to forward a data message based on the path in the network slice.
Optionally, the network device 21, the network device 22, and the network device 23 play different roles. The network device 21 is an ingress node of the network. The network device 21 is configured to add an identifier of the network slice and path information of the path in the network slice to the data message. The network device 22 is an intermediate node of the network. The network device 22 is configured to forward the data message along the path corresponding to the path information based on the identifier of the network slice and the path information in the data message. The network device 23 is an egress node of the network. The network device 23 is configured to remove the identifier of the network slice and the path information from the data message, and then forward the data message from the network.
Optionally, the system architecture shown in
A method procedure in an embodiment of this disclosure is described below by using an example.
Optionally,
Optionally, the method shown in
Step S201: A network device generates an advertisement message.
A protocol type of the advertisement message includes many cases. Optionally, the advertisement message is a BGP-LS message. The BGP-LS is a protocol obtained by extending the BGP. The BGP-LS is generally configured to report topology information to the controller. The BGP-LS is extended for reporting an identifier of a network slice and information about a path to the controller, so that an existing protocol can be reused as much as possible, and implementation complexity is reduced. Alternatively, the advertisement message is a PCEP message, a Simple Network Management Protocol (SNMP) message, or another protocol message.
The advertisement message includes the identifier of the network slice and path information of one or more paths in the network slice.
The identifier of the network slice identifies the network slice. The network device may obtain the identifier of the network slice in many manners. For example, the network device obtains the identifier of the network slice in a manner such as static configuration, dynamic delivery, or learning from a neighbor. The static configuration manner means that an administrator configures the identifier of the network slice on the network device through a command-line interface, a web interface, or the like. The dynamic delivery manner means that the controller device sends the identifier of the network slice to the network device by using NETCONF, BGP, PCEP, or another protocol that supports interaction between the control plane and the data plane. The manner of learning from a neighbor is that, for example, the network device obtains the identifier of the network slice from a message sent by a neighboring node in the network slice.
The path in the network slice is optionally a tunnel. The tunnel is an end-to-end path. For example, the tunnel includes, but is not limited to, a label switching path (LSP) tunnel, a traffic engineering (TE) tunnel, a policy tunnel, and the like. Optionally, the path in the network slice is a path in the SR policy. For example, one or more paths in the network slice are one or more candidate paths in the SR policy. For another example, one or more paths in the network slice are paths corresponding to one or more SID lists in the SR policy.
Optionally, the path information in the advertisement message includes a SID list corresponding to one or more paths. Further, the SID list includes a SID corresponding to a node or a link on the path. For example, when being applied to an SRv6 scenario, the SID list includes an End SID of one or more nodes on the path or an End.X SID of one or more links on the path. The SID list is carried in the message, so that the SR scenario is supported.
The network device may obtain the SID list in many manners. For example, the network device obtains the SID list in a manner such as static configuration, dynamic delivery, or learning from a neighbor. For another example, the network device performs path computation based on a topology of the network slice, to obtain the SID list.
Optionally, the path information in the advertisement message includes status information corresponding to one or more paths. The status information is for describing a status of a corresponding path.
Optionally, the status information of the path in the advertisement message includes one or more of the following information: at least one of traffic statistics information, network performance information, and connectivity information.
The traffic statistics information identifies traffic of the corresponding path. Optionally, the traffic statistics information is obtained by the network device by sampling and counting forwarded messages.
The network performance information identifies network performance of the corresponding path. For example, the network performance information includes a bandwidth, a delay, a message loss rate, a jitter, and the like of the path. Optionally, the network performance information is obtained by the network device by sending a performance detection message to a destination device of the path. The performance detection message includes, but is not limited to, an operations, administration, and maintenance (OAM) message, a Two-Way Active Measurement Protocol (TWAMP) message, and the like.
The connectivity information identifies whether a corresponding path is available (UP) or unavailable (down). Path unavailability is that, for example, one or more nodes on the path fail, or one or more links are disconnected. Optionally, the connectivity information is obtained by the network device by sending a connectivity detection message to the destination device of the path. The connectivity detection message includes, but is not limited to, a bidirectional forwarding detection (BFD) message, an Internet Control Message Protocol (ICMP) request message (ping), and the like.
Step S202: The network device sends the advertisement message to a controller.
Optionally, the advertisement message indicates the controller to control a message forwarding path based on the identifier of the network slice and the path information.
Step S203: The controller receives the advertisement message sent by the network device.
The controller can obtain the identifier of the network slice and the path information of the one or more paths in the network slice from the advertisement message. For example, with reference to
Step S204: The controller controls a message forwarding path based on the identifier of the network slice and the path information of the one or more paths in the network slice.
Because the network device reports the identifier of the network slice to the controller, the controller can control the message forwarding path based on the identifier of the network slice reported by the network device. There is a plurality of implementations of controlling a forwarding path. For example, the controlling a forwarding path includes, but is not limited to, path optimization, transmission resource allocation for the forwarding path, monitoring and recording a status of the forwarding path, presenting a topology view of a network topology to which the forwarding path belongs, and the like.
The path optimization refers to switching a path on which traffic is borne. To distinguish different paths, the following uses “first path” and “second path” to refer to paths that bear traffic before and after optimization respectively. A second path is configured to bear traffic forwarded on a first path. For example, a data flow A is originally forwarded through the first path. After path optimization, the data flow A is forwarded through the second path.
A scenario to which path optimization is applicable to includes, but is not limited to, the following scenario 1 and scenario 2.
Scenario 1: The controller performs path optimization when a path is unavailable.
Further, the controller determines whether one or more paths in the network slice are available based on connectivity information of the one or more paths in the advertisement message sent by the network device. When the controller determines that a first path in the one or more paths is unavailable, a second path is obtained.
Scenario 2: The controller performs path optimization when a bandwidth utilization rate reaches a threshold.
Further, the controller determines whether a bandwidth utilization rate of one or more paths in the network slice reaches the threshold based on network performance information of the one or more paths in the advertisement message sent by the network device. When the controller determines that a bandwidth utilization rate of a first path in the one or more paths reaches the threshold, a second path is obtained. Optionally, the threshold of the bandwidth utilization rate is a value pre-configured by a user.
In some embodiments, the bandwidth utilization rate of the first path is a bandwidth utilization rate of one or more links on the first path. For example, when the controller determines that a bandwidth utilization rate of one link on the first path reaches the threshold, the second path is obtained. For another example, when the controller determines that bandwidth utilization rates of a plurality of links on the first path reaches the threshold, the second path is obtained. Optionally, when being applied to the SR scenario, the first path is represented by a SID list. A link is represented by an End.X SID. The bandwidth utilization rate of the first path is a bandwidth utilization rate corresponding to one or more End.X SIDs in the SID list.
In some embodiments, after the controller obtains the second path, the controller generates and sends a path switching instruction to the network device. The path switching instruction includes path information of the second path. The path switching instruction indicates the network device to switch the message forwarding path to the second path. The network device receives the path switching instruction sent by the controller, and switches the path bearing traffic from the first path to the second path.
For example, the path information of the second path in the path switching instruction sent by the controller includes a SID list of the second path. The network device switches the path bearing traffic from the first path to the second path based on the SID list of the second path. Further, when the network device receives the traffic, if the traffic is traffic originally to be borne by the first path, the network device adds the SID list of the second path to each message in the traffic, and forwards the traffic that carries the SID List of the second path, so that the traffic is forwarded along the second path based on the SID list of the second path.
The path optimization manner includes, but is not limited to, an intra-slice optimization manner and an inter-slice optimization manner, which are described below respectively using (1) and (2).
(1) Intra-Slice Optimization:
Intra-slice optimization refers to switching different message forwarding paths in a same network slice. When intra-slice optimization is used, the second path is a path in a network slice corresponding to the identifier of the network slice. In other words, the second path and the first path are different paths in the same network slice. For example, a manner in which the controller obtains the second path includes the following. The controller uses the identifier of the network slice as an index to search for topology information of the network slice corresponding to the identifier of the network slice. The controller determines a path different from the first path based on the topology information of the network slice, and obtains the second path.
(2) Inter-Slice Optimization:
Inter-slice optimization refers to switching a message forwarding path in one network slice to a message forwarding path in another network slice. For example, when intra-slice optimization is used, the advertisement message includes an identifier of a first network slice and path information of a first path in the first network slice. The second path is a path in a second network slice, and the second network slice is different from the first network slice. Optionally, inter-slice optimization is applicable to a case in which one service has a plurality of network slices. For example, the first network slice and the second network slice correspond to a same service type. For another example, the first network slice and the second network slice correspond to a same user identifier.
Optionally, the second path is calculated by the controller based on a network topology of the network slice corresponding to the identifier of the network slice. For example, based on the topology of the network slice, the controller uses a flexible algorithm (FlexAlgo) to perform path computation, to obtain the second path. Optionally, a constraint condition used by the controller during the path computation includes not passing a link whose bandwidth utilization rate reaches the threshold on the first path.
According to the method provided in this embodiment, the network device includes slice information, such as an identifier of a network slice and information about a path in the network slice, in a message, and reports the message to the controller, so that slice information on a forwarding plane is consistent with slice information on a control plane, and the controller controls a message forwarding path based on slice information on the network device. Therefore, this helps improve an effect of controlling the message forwarding path by the controller.
A message format included in embodiments of this disclosure is described below.
In some embodiments of this disclosure, the BGP-LS protocol is extended, so that the network device can report an identifier of a network slice including an SR policy candidate path to the controller. Further, the identifier of the network slice is carried in an SR policy candidate path descriptor TLV of the BGP-LS message.
A protocol ID (protocol-ID) field identifies a protocol from which a TE policy comes. For example, if content of the protocol ID field is 9, it indicates that the protocol from the TE policy comes is SR.
An identifier field is an identifier of the BGP-LS in a protocol for collecting topologies. The identifier field occupies 64 bits.
The headend field carries information about the head end. The headend field includes at least one node descriptor.
A TE policy descriptor (TE policy descriptors) field is configured to describe the TE policy. The TE policy descriptor field includes one or more TLVs.
The type field carries a type of the SR policy candidate path TLV. For example, content of the type field is 554.
The length field identifies a length of the SR policy candidate path TLV.
The protocol origin (protocol-origin) field identifies a protocol or a path through which the candidate path is generated. For example, when the SR policy is received through the BGP, content of the protocol origin field is 2. When the SR policy is configured locally, content of the protocol origin field is 3.
The endpoint field carries an address of a destination device in the SR policy. The endpoint field occupies 4 or 16 bytes.
The flag (flags) field includes one or more flag bits.
The policy color field carries a color of the SR policy. The color field occupies 4 bytes.
The originator AS number field carries an AS number (ASN) of the candidate path. The originator AS number field occupies four bytes.
The originator address field carries an address identifier of the candidate path. The originator address occupies 4 or 16 bytes.
The discriminator field identifies the candidate path. Different candidate paths in a same SR policy can be distinguished by a discriminator. For example, a device advertises three candidate paths in the SR policy through the BGP. The three candidate paths correspond to three different discriminators. The three candidate paths are distinguished by their respective discriminators.
In some embodiments, a sub-TLV is extended in the SR policy candidate path descriptor TLV to report the identifier of the network slice. Further, the identifier of the network slice is carried in the sub-TLV of the SR policy candidate path descriptor TLV.
For example,
It can be learned from the message formats shown in
The method shown in
An SRv6 policy tunnel in the following procedure is a path in the network slice in the method shown in
A network slice deployment procedure is described below. Referring to
Further, the controller configures the SRv6 policy tunnel, and specifies a mapping relationship between an SRv6 policy and the identifier of the network slice. The controller performs SRv6 policy path computation in the slice topology based on path computation requirements (such as a delay and a bandwidth) input by a user.
An SID list of the SRv6 policy tunnel in the foregoing configuration is segment-list list1, and the identifier of the network slice is 1. The SID list of the SRv6 policy tunnel includes two SIDs. One SID is 2::2:100 and the other SID is 3::3:100.
A tunnel monitoring procedure is described below.
For example, the head node router reports the following content:
The foregoing content reported by the head node router indicates that a SID list of a path includes SID 2::2:100 and SID 2::2:100. An SR policy to which the path belongs is policy1. An IP address of an endpoint (destination device) of the path is 3::3. A color corresponding to the path is green. A priority of a candidate path is 1 3::3. The identifier of the network slice is 1.
Optionally, the content reported by the head node router is the same as the content delivered by the controller in the slice deployment procedure. Optionally, the content reported by the head node router further includes a status of the SID list, for example, UP or down. The status of the SID list is obtained by the head node router through a BFD.
Optionally, the head node router reports traffic statistics information of an SRv6 policy to the controller by using the telemetry protocol.
A tunnel optimization procedure is described below.
Optionally, the threshold of the bandwidth utilization rate is from a bandwidth optimization policy configured by a user on the controller. The bandwidth optimization policy includes the threshold of the bandwidth utilization rate of the link. The bandwidth optimization policy indicates the controller to trigger path switching when a bandwidth utilization rate of a link reaches the threshold.
By performing traffic optimization, it can be ensured that bandwidth utilization rates of all links in the network slice are lower than a specified threshold, to balance the bandwidth utilization rates of all the links in the network slice.
A basic hardware structure of a network device and a controller is described below using an example.
Optionally, with reference to
Optionally, with reference to
The device 600 includes at least one processor 601, a memory 602, and at least one network interface 603.
If the device 600 is configured as a network device, the processor 601 is configured to generate an advertisement message, and the network interface 603 is configured to send the advertisement message.
If the device 600 is configured as a controller, the network interface 603 is configured to receive an advertisement message, and the processor 601 is configured to control a message forwarding path based on an identifier of a network slice and path information of one or more paths in the network slice.
The processor 601 is, for example, a general-purpose CPU, a network processor (NP), a graphics processing unit (GPU), a neural processing unit (NPU), a data processing unit (DPU), a microprocessor, or one or more integrated circuits configured to implement the solutions of this disclosure. For example, the processor 601 includes an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The PLD is, for example, a complex PLD (CPLD), a field-programmable gate array (FPGA), generic array logic (GAL), or any combination thereof.
The network interface 603 is any apparatus of a transceiver type, and is configured to communicate with another device or a communication network. The network interface 603 includes, for example, at least one of a wired network interface or a wireless network interface. The wired network interface is, for example, an Ethernet interface. The Ethernet interface is, for example, an optical interface, an electrical interface, or a combination thereof. The wireless network interface is, for example, a wireless local area network (WLAN) interface, a cellular network interface, or a combination thereof.
In some embodiments, the processor 601 includes one or more CPUs, for example, a CPU 0 and a CPU 1 shown in
In some embodiments, the device 600 optionally includes a plurality of processors, such as the processor 601 and a processor 605 shown in
In some embodiments, the device 600 further includes an internal connection 604. The processor 601, the memory 602, and the at least one network interface 603 are connected by the internal connection 604. The internal connection 604 includes a channel for transmitting information between the foregoing components. Optionally, the internal connection 604 is a board or a bus. Optionally, the internal connection 604 is classified into an address bus, a data bus, a control bus, and the like.
Optionally, the processor 601 reads program code 610 stored in the memory 602 to implement the method in the foregoing embodiments, or the processor 601 uses internally stored program code to implement the method in the foregoing embodiments. When the processor 601 reads the program code 610 stored in the memory 602 to implement the methods in the foregoing embodiments, the memory 602 stores program code for implementing the message processing method provided in embodiments of this disclosure.
The memory 602 is, for example, a read-only memory (ROM) or another type of static storage device that can store static information and instructions, or a random-access memory (RAM) or another type of dynamic storage device that can store information and instructions, or an electrically erasable programmable ROM (EEPROM), a compact disc (CD) ROM (CD-ROM) or another CD storage, an optical disc storage (including a CD, a laser disc, an optical disc, a DIGITAL VERSATILE DISC (DVD), a BLU-RAY disc, and the like), a magnetic disk storage medium or another magnetic storage device, or any other medium that can be configured to carry or store desired program code in a form of instructions or a data structure and that can be accessed by a computer, but is not limited thereto. Optionally, the memory 602 exists independently, and is connected to the processor 601 by the internal connection 604. Alternatively, the memory 602 and the processor 601 may optionally be integrated together.
In some embodiments, the device 600 further includes an input/output interface 606. The input/output interface 606 is connected to the internal connection 604.
For more details of implementing the foregoing functions by the processor 601, refer to the descriptions in the foregoing method embodiments. Details are not described herein again.
Optionally, with reference to
Optionally, with reference to
The device 700 includes a main control board 710 and an interface board 730.
The main control board 710 is also referred to as a main processing unit (MPU) or a route processing card. The main control board 710 is configured to control and manage all components in the device 700, including route computation, device management, device maintenance, and protocol processing functions. The main control board 710 includes a central processing unit 711 and a memory 712.
The interface board 730 is also referred to as a line interface processing unit (LPU), a line card, or a service board. The interface board 730 is configured to provide various service interfaces and implement data message forwarding. The service interface includes, but is not limited to, an Ethernet interface, a packet over Synchronous Optical Networking (SONET)/Synchronous Digital Hierarchy (SDH) (POS) interface, and the like. The Ethernet interface is, for example, a flexible Ethernet service interface (e.g., flexible Ethernet client or FlexE client). The interface board 730 includes a central processing unit 731, a network processor 732, a forwarding table entry memory 734, and a physical interface card (PIC) 733.
The central processing unit 731 on the interface board 730 is configured to control and manage the interface board 730 and communicate with the central processing unit 711 on the main control board 710.
The network processor 732 is configured to implement message forwarding processing. A form of the network processor 732 is, for example, a forwarding chip. Further, the network processor 732 is configured to forward a received message based on a forwarding table stored in the forwarding table entry memory 734. If a destination address of the message is an address of the device 700, the message is reported to a CPU (for example, the central processing unit 711) for processing. If the destination address of the message is not the address of the device 700, a next hop and an egress interface corresponding to the destination address are found in the forwarding table based on the destination address. The message is forwarded to the egress interface corresponding to the destination address. Processing on an uplink message includes processing on a message ingress interface and forwarding table lookup. Processing on a downlink message includes forwarding table lookup and the like.
The physical interface card 733 is configured to implement a physical layer interconnection function. Original traffic enters the interface board 730 from the physical interface card 733, and a processed message is sent out from the physical interface card 733. The physical interface card 733, also referred to as a subcard, may be mounted on the interface board 730, and is responsible for converting an optical/electrical signal into a message, performing validity check on the message, and forwarding the message to the network processor 732 for processing. In some embodiments, the central processing unit may also perform a function of the network processor 732, for example, implement software forwarding based on a general CPU. Therefore, the network processor 732 is not required in the physical interface card 733.
Optionally, the device 700 includes a plurality of interface boards. For example, the device 700 further includes an interface board 740. The interface board 740 includes a central processing unit 741, a network processor 742, a forwarding table entry memory 744, and a physical interface card 743.
Optionally, the device 700 further includes a switch fabric board 720. The switch fabric board 720 is also referred to as, for example, a switch fabric unit (SFU). When the network device has the plurality of interface boards 730, the switch fabric board 720 is configured to complete data exchange between the interface boards. For example, the interface board 730 and the interface board 740 communicate with each other, for example, through the switch fabric board 720.
The main control board 710 is coupled to the interface board 730. For example, the main control board 710, the interface board 730, the interface board 740, and the switch fabric board 720 are connected to a system backplane by a system bus to implement interworking. In a possible implementation, an Inter-Process Communication (IPC) protocol channel is established between the main control board 710 and the interface board 730, and communication is performed between the main control board 710 and the interface board 730 through the IPC channel.
Logically, the device 700 includes a control plane and a forwarding plane. The control plane includes the main control board 710 and the central processing unit 731. The forwarding plane includes components for forwarding, for example, the forwarding table entry memory 734, the physical interface card 733, and the network processor 732. The control plane performs functions such as routing, generating a forwarding table, processing signaling and a protocol message, and configuring and maintaining a device status. The control plane delivers the generated forwarding table to the forwarding plane. On the forwarding plane, by performing table lookup based on the forwarding table delivered by the control plane, the network processor 732 forwards a message received by the physical interface card 733. The forwarding table delivered by the control plane is, for example, stored in the forwarding table entry memory 734. In some embodiments, the control plane and the forwarding plane are, for example, completely separated, and are not on a same device.
Operations on the interface board 740 are the same as operations on the interface board 730. For brevity, details are not described again. The device 700 may correspond to the network device or the controller in the foregoing method embodiments. The main control board 710, the interface board 730, and/or the interface board 740 in the device 700 implement, for example, functions and/or various steps implemented by the network device or the controller in the foregoing method embodiments. For brevity, details are not described herein again.
It should be noted that there may be one or more main control boards. When there is a plurality of main control boards, the main control boards may include, for example, an active main control board and a standby main control board. There may be one or more interface boards. A network device having a stronger data processing capability provides more interface boards. There may also be one or more physical interface cards on the interface board. There may be no switch fabric board or one or more switch fabric boards. When there is a plurality of switch fabric boards, load balancing and redundancy backup may be implemented together. In a centralized forwarding architecture, the network device may not need the switch fabric board, and the interface board provides a function of processing service data in an entire system. In a distributed forwarding architecture, the network device may have at least one switch fabric board, and data exchange between a plurality of interface boards is implemented through the switch fabric board, to provide a large-capacity data exchange and processing capability. Therefore, a data access and processing capability of a network device in the distributed architecture is better than that of a device in the centralized architecture. Optionally, the network device may alternatively be in a form in which there is only one card. To be specific, there is no switch fabric board, and functions of the interface board and the main control board are integrated on the card. In this case, the central processing unit on the interface board and the central processing unit on the main control board may be combined into one central processing unit on the card, to perform functions obtained after the two central processing units are combined. The device in this form (for example, a network device such as a low-end switch or router) has a weak data exchange and processing capability. A specific architecture that is to be used depends on a specific networking deployment scenario. This is not limited herein.
Referring to
The apparatus embodiment described in
Referring to
Optionally, the controller 900 further includes a sending unit, and the sending unit is configured to support the controller 900 in sending the SID list corresponding to the second path to the network device.
The apparatus embodiment described in
Embodiments of this specification are all described in a progressive manner, for same or similar parts in the embodiments, refer to these embodiments, and descriptions of each embodiment focus on a difference from other embodiments. A refers to B means that A is the same as B or A is a simple variation of B.
In the specification and claims in embodiments of this disclosure, the terms “first”, “second”, and the like are for distinguishing between different objects, but are not intended to describe a specific order of the objects, and cannot be understood as an indication or implication of relative importance. For example, the first path and the second path are for distinguishing between different paths, but are not intended to describe a specific order of the paths, and cannot be understood that the first path is more important than the second path.
In embodiments of this disclosure, unless otherwise specified, “a plurality of” means two or more. For example, a plurality of paths refers to two or more paths.
All or some of the foregoing embodiments may be implemented through software, hardware, firmware, or any combination thereof. When software is used to implement the embodiments, all or a part of the embodiments may be implemented in a form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or some of the procedures or functions described in embodiments of this disclosure are generated. The computer may be a general-purpose computer, a dedicated computer, a computer network, or other programmable apparatuses. The computer instructions may be stored in a computer-readable storage medium or may be transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center in a wired (for example, a coaxial cable, an optical fiber, or a digital subscriber line (DSL)) or wireless (for example, infrared, radio, or microwave) manner. The computer-readable storage medium may be any usable medium accessible by the computer, or a data storage device, for example, a server or a data center, integrating one or more usable media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, or a magnetic tape), an optical medium (for example, DVD), a semiconductor medium (for example, a solid-state drive (SSD)), or the like.
In conclusion, the foregoing embodiments are merely intended for describing the technical solutions of this disclosure, but not for limiting this disclosure. Although this disclosure is described in detail with reference to the foregoing embodiments, a person of ordinary skill in the art should understand that they may still make modifications to the technical solutions described in the foregoing embodiments or make equivalent replacements to some technical features thereof, without departing from the scope of the technical solutions of embodiments of this disclosure.
| Number | Date | Country | Kind |
|---|---|---|---|
| 202110281996.8 | Mar 2021 | CN | national |
This is a continuation of International Patent Application No. PCT/CN2022/080185 filed on Mar. 10, 2022, which claims priority to Chinese Patent Application No. 202110281996.8 filed on Mar. 16, 2021. The disclosures of the aforementioned applications are hereby incorporated by reference in their entireties.
| Number | Date | Country | |
|---|---|---|---|
| Parent | PCT/CN2022/080185 | Mar 2022 | US |
| Child | 18469078 | US |
