Network resource partition information reporting method and apparatus

Abstract

Provided in the embodiments of the present application is an NRP information reporting method. The method comprises: a first network device acquiring a BGP LS message, which comprises first NLRI, wherein the first NLRI comprises link description information and NRP description information, the link description information is used for indicating a first link, and the NRP description information is used for describing a first NRP associated with the first link; and after acquiring the BGP LS message, the first network device sending the BGP LS message to a controller. It can be seen therefrom that in the solution, NLRI of a BGP LS is expanded, and first NLRI is expanded to bear link description information and NRP description information, thereby implementing the reporting of the NRP description information. In a scenario in which an NRP resource and topological information are changed, the solution can make a controller obtain the changed NRP resource and the changed topological information in a timely manner.

Description

Method and device for reporting network resource fragmentation information

[0001] This application claims priority from the following Chinese patent applications, the entire contents of which are incorporated herein by reference.

[0002] 1. Priority of the Chinese patent application filed with the State Intellectual Property Office on February 20, 2024, with application number 202410191610.8 and invention name “A method and device for reporting network slicing information”.

[0003] 2. Priority of the Chinese patent application submitted to the State Intellectual Property Office on March 4, 2024, with application number 202410248962.2 and invention name “A method and device for reporting network resource fragmentation information”. Technical Field

[0004] The present application relates to the field of communications, and in particular to a method and device for reporting network resource fragmentation information. Background Art

[0005] With the development of network technology, the services supported by networks are becoming increasingly diverse. For example, services supported by networks can include virtual reality (VR), augmented reality (AR), remote industrial control, autonomous driving, and the Internet of Things (IoT).

[0006] Because different services have vastly different network requirements, network resource partitioning (NRP) technology can be applied to meet these needs. NRP consists of a collection of resources and associated policies allocated across a group of connected links in the underlay network. These resources can include one or more of cache, queues, and scheduling. In some scenarios, NRP is also referred to as a "network slice."

[0007] For networks that apply NRP technology, the controller can calculate the service transmission path for the service based on the pre-collected NRP resources and topology information, and notify the network devices on the service transmission path to reserve resources so that the network devices can forward the service traffic based on the reserved resources in the subsequent service forwarding phase.

[0008] Currently, when NRP resources and topology information change, the controller cannot detect it in time. Consequently, the controller cannot calculate the service transmission path for the service based on the changed NRP resources and topology information. Therefore, a solution is urgently needed to solve this problem. Summary of the Invention

[0009] The embodiments of the present application provide a method and apparatus for reporting NRP information, which enable a network device to report NRP information to a controller, thereby enabling the controller to obtain NRP resources and topology information.

[0010] In the first aspect, the present application provides a method for reporting NRP information, wherein a first network device can obtain a Border Gateway Protocol Link State (BGP LS) message, and the BGP LS message includes first network layer reachability information (NLRI). The first NLRI includes link description information and NRP description information, the link description information is used to indicate the first link, and the NRP description information is used to describe the first NRP associated with the first link. After the first network device obtains the BGP LS message, it can send the BGP LS message to the controller. It can be seen that in this solution, the NLRI of BGP LS is extended, and the first NLRI is extended to carry link description information and NRP description information, thereby realizing the reporting of NRP description information. In a scenario where NRP resources and topology information change, this solution enables the controller to obtain the NRP resources and topology information after the change in a timely manner.

[0011] On the second aspect, an embodiment of the present application provides a method for receiving NRP information, which can be applied to a controller. The controller can receive a BGP LS message sent by a first network device, and the BGP LS message includes a first NLRI. The first NLRI includes link description information and NRP description information, the link description information is used to indicate the first link, and the NRP description information is used to describe the first NRP associated with the first link. It can be seen that in this solution, the NLRI of BGP LS is extended, and the first NLRI is extended to carry link description information and NRP description information, so that the first network device can report NRP information to the controller based on the extended first NLRI. In a scenario where NRP resources and topology information change, this solution enables the controller to obtain the NRP resources and topology information after the change in a timely manner. Accordingly, the controller can promptly calculate the service transmission path for the service based on the NRP resources and topology information after the change, thereby ensuring the quality of service provided to the service.

[0012] Regarding the first and second aspects above:

[0013] In one possible implementation, the first NLRI includes an NLRI type field, which is used to indicate the type of the first NLRI. In a specific example, the NLRI type field indicates that the first NLRI is a link NLRI. In other words, in this embodiment of the present application, the link NLRI is extended so that the link NLRI can be used to carry link description information and NRP description information, thereby enabling the first network device to use the link NLRI to report NRP information to the controller.

[0014] In one possible implementation, a new BGP LS NLRI type, NRP link NLRI, can be added. In this scenario, the NLRI type field included in the first NLRI indicates that the first NLRI is an NRP link NLRI. In other words, in this embodiment of the present application, a new BGP LS NLRI, NRP link NLRI, is added. This NRP link NLRI can be used to carry link description information and NRP description information, thereby enabling the first network device to use the NRP link NLRI to report NRP information to the controller.

[0015] In one possible implementation, the first NLRI is an NLRI at the NRP granularity. In other words, when the first network device reports NRP information to the controller, it can use the NRP as the reporting granularity and report the NRP information to the controller on demand. For example, the first network device can report changed NRP information to the controller. This allows the controller to obtain changed NRP resources and topology information in a timely manner, while also reducing invalid information exchange between the first network device and the controller.

[0016] In one possible implementation, considering that an NRP identifier (ID) can uniquely identify an NRP, the NRP description information may include an NRP ID for identifying the first NRP. As an example, the first NLRI may include a first type length value (TLV), for example, the aforementioned NRP description field includes a first TLV, and the first TLV is used to carry the NRP ID.

[0017] In one possible implementation, the NRP description information may include, in addition to the NRP ID, other additional description information of the first NRP. For example, the NRP description information may also include the name of the NRP and / or the type of the NRP. The name of the NRP mentioned here may be the name of the first NRP, and the type of the NRP mentioned here is used to indicate the purpose of the first NRP, wherein the purpose of the first NRP may also be the industry corresponding to the first NRP. As a specific example, the purpose of the first NRP may be one of education, medical care, or manufacturing.

[0018] In one possible implementation, in addition to the first NLRI, the BGP LS message may also include a BGP LS attribute, which is used to carry the attributes of the first NRP. In this way, the description information of the first NRP and the attributes of the first NRP can be carried in the BGP LS message and reported to the controller, so that the controller can obtain the ID of the first NRP and the attributes of the first NRP from the BGP LS message. The attributes of the first NRP may include at least one attribute of the first NRP. As an example, the attributes of the first NRP may include one or more of the resource information of the first NRP, the status information of the first NRP, and the hierarchical information of the first NRP.

[0019] In one possible implementation, the resource information of the first NRP is used to indicate the resources associated with the first NRP. As a specific example, the resources associated with the first NRP may include a logical interface associated with the first NRP and / or resources allocated to the first NRP. The logical interface associated with the first NRP mentioned here may also be referred to as an NRP interface (or NRP interface resources) or a slice interface (or slice interface resources). The resources allocated to the first NRP can be understood as forwarding resources allocated by the first NRP. The resources allocated to the first NRP include, but are not limited to, one or more of the bandwidth, cache, and queue allocated to the first NRP.

[0020] In a possible implementation, the hierarchical information of the first NRP is used to indicate the level or grade of the first NRP. In the embodiment of the present application, the grade of the first NRP can be a primary NRP or a secondary NRP.

[0021] In one possible implementation, the status information of the first NRP is used to indicate the status of the first NRP. As a specific example, the status information of the first NRP may be the resource status of the first NRP, that is, the status information of the first NRP may be used to indicate the status of the resources possessed by the first NRP. In one example, the status of the resources possessed by the first NRP may indicate whether the resources possessed by the first NRP are available. For example, the status of the resources possessed by the first NRP indicates that the resources possessed by the first NRP are available, indicating that the network device has successfully reserved resources for the first NRP; the status of the resources possessed by the first NRP indicates that the resources possessed by the first NRP are unavailable, indicating that the network device has failed to reserve resources for the first NRP. In another example, the status of the resources possessed by the first NRP may indicate the occupancy status of the resources possessed by the first NRP. The occupancy status may, for example, indicate the resources currently occupied in the first NRP.

[0022] In a possible implementation, the first network device may obtain the BGP LS message when its own NRP information changes, so that the controller can obtain the changed NRP resources and topology information in a timely manner when the NRP resources and topology information change.

[0023] As a specific example, a change in the NRP information of a first network device can occur in two situations: one is that the first network device is configured with an NRP, and the other is that an NRP interface associated with the NRP in the first network device fails or a resource associated with the NRP is unavailable. In other words, in one example, the first network device obtains the BGP LS message in response to a failure of an interface associated with the first NRP or unavailability of a resource associated with the first NRP. In another example, the first network device may obtain the BGP LS message in response to being configured with the first NRP.

[0024] In one possible implementation, the configuration of the first NRP on the first network device can be implemented through the controller. Specifically, the controller can send the configuration information of the first NRP to the first network device, thereby configuring the first NRP on the first network device. In other words, the first network device can receive the configuration information of the first NRP sent by the controller, and, based on the first NRP configuration information, configure the first NRP locally, and further obtain the BGP LS message. The configuration information of the first NRP at least includes the description information of the aforementioned first NRP. The configuration information of the first NRP may also include other information related to the first NRP, for example, one or more of the resource information of the first NRP, the status information of the first NRP, and the hierarchical information of the first NRP.

[0025] In one possible implementation, the first NRP configuration information is sent by the controller to the first network device after calculating a service transmission path for the service based on NRP resources and topology information. The configuration information is used by the first network device to reserve resources for the first NRP. In this case, the first NRP may be, for example, a secondary NRP. Accordingly, in this scenario, the resource information of the first NRP included in the configuration information can be understood as the required resources of the first NRP. In this scenario, after receiving the first NRP configuration information sent by the controller, the first network device may reserve resources for the first NRP based on the first NRP configuration information. Furthermore, the first network device may also determine the status information of the first NRP based on the result of reserving resources for the first NRP. If the resource reservation for the first NRP is successful, the status information of the first NRP indicates that the resources of the first NRP are available; if the resource reservation for the first NRP fails, the status information of the first NRP indicates that the resources of the first NRP are unavailable. Accordingly, when obtaining the BGP LS message, the BGP LS message including the determined status information of the first NRP may be obtained based on the determined status information of the first NRP.

[0026] In one possible implementation, the NRP description information in the aforementioned first NLRI can be used to indicate not only the first NRP associated with the first link, but also the second NRP associated with the first link. As a specific example, if both the second NRP and the first NRP associated with the first link have changed, the NRP description information in the first NLRI is also used to indicate the second NRP associated with the first link. In this way, information about multiple NRPs that have changed on the first network device can be reported to the controller via a single BGP LS message, thereby reducing the number of messages exchanged between the first network device and the controller.

[0027] On the third aspect, the present application provides a method for reporting NRP information, wherein a first network device can obtain a BGP LS message, and the BGP LS message includes a first NLRI. The first NLRI includes node description information and NRP description information, the node description information is used to indicate the first network device, and the NRP description information is used to describe the first NRP associated with the first network device. After the first network device obtains the BGP LS message, it can send the BGP LS message to the controller. It can be seen that in this solution, the NLRI of BGP LS is extended, and the first NLRI is extended to carry node description information and NRP description information, thereby realizing the reporting of NRP description information. In a scenario where NRP resources and topology information change, this solution enables the controller to obtain the NRP resources and topology information after the change in a timely manner.

[0028] In the fourth aspect, an embodiment of the present application provides a method for receiving NRP information, which can be applied to a controller. The controller can receive a BGP LS message sent by a first network device, and the BGP LS message includes a first NLRI. The first NLRI includes node description information and NRP description information, the node description information is used to indicate the first network device, and the NRP description information is used to describe the first NRP associated with the first network device. It can be seen that in this solution, the NLRI of BGP LS is extended, and the first NLRI is extended to carry node description information and NRP description information, so that the first network device can report NRP information to the controller based on the extended first NLRI. In a scenario where NRP resources and topology information change, this solution enables the controller to obtain the NRP resources and topology information after the change in a timely manner. Accordingly, the controller can promptly calculate the service transmission path for the service based on the NRP resources and topology information after the change, thereby ensuring the quality of service provided to the service.

[0029] Regarding the third and fourth aspects above:

[0030] In one possible implementation, the first NLRI includes an NLRI type field, which is used to indicate the type of the first NLRI. In a specific example, the NLRI type field indicates that the first NLRI is a node NLRI. In other words, in this embodiment of the present application, the node NLRI is extended so that the node NLRI can be used to carry link description information and NRP description information, thereby enabling the first network device to use the node NLRI to report NRP information to the controller.

[0031] In one possible implementation, a new BGP LS NLRI type, NRP node NLRI, can be added. In this scenario, the NLRI type field included in the first NLRI indicates that the first NLRI is an NRP node NLRI. In other words, in this embodiment of the present application, a new BGP LS NLRI, NRP node NLRI, is added. This NRP node NLRI can be used to carry link description information and NRP description information, thereby enabling the first network device to use the NRP node NLRI to report NRP information to the controller.

[0032] In one possible implementation, the first NLRI is an NLRI at the NRP granularity. In other words, when the first network device reports NRP information to the controller, it can use the NRP as the reporting granularity and report the NRP information to the controller on demand. For example, the first network device can report changed NRP information to the controller. This allows the controller to obtain changed NRP resources and topology information in a timely manner, while also reducing invalid information exchange between the first network device and the controller.

[0033] In a possible implementation, the NRP description information includes: an NRP identification ID, where the NRP ID is used to identify the first NRP.

[0034] In a possible implementation, the NRP description information further includes: the name of the NRP and / or the type of the NRP, where the name of the NRP is the name of the first NRP, and the type of the NRP indicates the purpose of the first NRP, which includes: education, medical treatment, or manufacturing.

[0035] In one possible implementation, the BGP LS message also includes BGP LS attributes, and the BGP LS attribute information is used to carry the attributes of the first NRP, and the attributes of the first NRP include at least one of the following: resource information of the first NRP, status information of the first NRP, and hierarchical information of the first NRP.

[0036] In a possible implementation manner, the resource information includes: a logical interface associated with the first NRP and / or resources allocated to the first NRP.

[0037] In a possible implementation, the status information of the first NRP includes: status of resources owned by the first NRP, where the status of the resources indicates whether the resources are available and / or the occupancy status of the resources.

[0038] In a possible implementation manner, the hierarchy information of the first NRP indicates that the first NRP is a first-level NRP or a second-level NRP.

[0039] In a possible implementation, the first network device obtains a Border Gateway Protocol Link State (BGP LS) message, including: the first network device obtains the BGP LS message in response to being configured with the first NRP.

[0040] In a possible implementation, configuring the first NRP on the first network device includes: the first network device receiving configuration information of the first NRP sent by a controller, where the configuration information includes at least the NRP description information.

[0041] In one possible implementation, the method further includes: the first network device reserves resources for the first NRP based on the configuration information of the first NRP, and determines the status information of the first NRP based on the result of reserving resources for the first NRP, wherein if the resources are successfully reserved for the first NRP, the status information of the first NRP indicates that the resources of the first NRP are available; if the resources are reserved for the first NRP fails, the status information of the first NRP indicates that the resources of the first NRP are unavailable; accordingly, the first network device obtains a Border Gateway Protocol Link State BGP LS message, including: the first network device obtains a BGP LS message including the status information of the first NRP.

[0042] In a possible implementation, the first network device obtains a Border Gateway Protocol Link State (BGP LS) message, including: the first network device obtains the BGP LS message in response to a failure of an interface associated with the first NRP or unavailability of resources associated with the first NRP.

[0043] In a possible implementation manner, the NRP description information is further used to indicate a second NRP associated with the first link.

[0044] In the fifth aspect, an embodiment of the present application provides a network resource fragmentation information reporting device, which is applied to a first network device, and the device includes: a processing unit, used to obtain a border gateway protocol link state BGP LS message, the BGP LS message includes a first network layer reachability information NLRI, the first NLRI includes link description information and network resource fragment NRP description information, the link description information is used to indicate the first link, and the NRP description information is used to indicate the first NRP associated with the first link; a sending unit, used to send the BGP LS message to the controller.

[0045] In a possible implementation manner, the NLRI type field included in the first NLRI indicates that the first NLRI is a link NLRI.

[0046] In a possible implementation manner, the NLRI type field included in the first NLRI indicates that the first NLRI is an NRP link NLRI.

[0047] In a possible implementation, the NRP description information includes: an NRP identification ID, where the NRP ID is used to identify the first NRP.

[0048] In a possible implementation, the NRP description information further includes: the name of the NRP and / or the type of the NRP, where the name of the NRP is the name of the first NRP, and the type of the NRP indicates the purpose of the first NRP, which includes: education, medical treatment, or manufacturing.

[0049] In one possible implementation, the BGP LS message also includes BGP LS attributes, and the BGP LS attribute information is used to carry the attributes of the first NRP, and the attributes of the first NRP include at least one of the following: resource information of the first NRP, status information of the first NRP, and hierarchical information of the first NRP.

[0050] In a possible implementation manner, the resource information includes: a logical interface associated with the first NRP and / or resources allocated to the first NRP.

[0051] In a possible implementation, the status information of the first NRP includes: status of resources owned by the first NRP, where the status of the resources indicates whether the resources are available and / or the occupancy status of the resources.

[0052] In a possible implementation manner, the hierarchy information of the first NRP indicates that the first NRP is a first-level NRP or a second-level NRP.

[0053] In a possible implementation, the processing unit is configured to: in response to being configured with the first NRP, obtain the BGP LS message.

[0054] In a possible implementation, the configuring the first NRP includes: receiving configuration information of the first NRP sent by a controller, where the configuration information includes at least the NRP description information.

[0055] In one possible implementation, the processing unit is used to: reserve resources for the first NRP based on the configuration information of the first NRP, and determine the status information of the first NRP based on the result of reserving resources for the first NRP, wherein if the resources are successfully reserved for the first NRP, the status information of the first NRP indicates that the resources of the first NRP are available; if the resources are reserved for the first status information fails, the status information of the first NRP indicates that the resources of the first NRP are unavailable; obtain a BGP LS message including the status information of the first NRP.

[0056] In a possible implementation, the processing unit is configured to: obtain the BGP LS message in response to a failure of an interface associated with the first NRP or unavailability of resources associated with the first NRP.

[0057] In a possible implementation manner, the NRP description information is further used to indicate a second NRP associated with the first link.

[0058] In the sixth aspect, an embodiment of the present application provides a network resource fragmentation information reporting device, which is applied to a first network device, and the device includes: a processing unit, used to obtain a border gateway protocol link state BGP LS message, the BGP LS message includes a first network layer reachability information NLRI, the first NLRI includes node description information and network resource fragment NRP description information, the node description information is used to indicate the first network device, and the NRP description information is used to indicate the first NRP associated with the first network device; a sending unit, used to send the BGP LS message to the controller.

[0059] In a possible implementation manner, the NLRI type field included in the first NLRI indicates that the first NLRI is a node NLRI.

[0060] In a possible implementation manner, the NLRI type field included in the first NLRI indicates that the first NLRI is an NRP node NLRI.

[0061] In a possible implementation, the NRP description information includes: an NRP identification ID, where the NRP ID is used to identify the first NRP.

[0062] In a possible implementation, the NRP description information further includes: the name of the NRP and / or the type of the NRP, where the name of the NRP is the name of the first NRP, and the type of the NRP indicates the purpose of the first NRP, which includes: education, medical treatment, or manufacturing.

[0063] In one possible implementation, the BGP LS message also includes BGP LS attributes, and the BGP LS attribute information is used to carry the attributes of the first NRP, and the attributes of the first NRP include at least one of the following: resource information of the first NRP, status information of the first NRP, and hierarchical information of the first NRP.

[0064] In a possible implementation manner, the resource information includes: a logical interface associated with the first NRP and / or resources allocated to the first NRP.

[0065] In a possible implementation, the status information of the first NRP includes: status of resources owned by the first NRP, where the status of the resources indicates whether the resources are available and / or the occupancy status of the resources.

[0066] In a possible implementation manner, the hierarchy information of the first NRP indicates that the first NRP is a first-level NRP or a second-level NRP.

[0067] In a possible implementation, the processing unit is configured to: in response to being configured with the first NRP, obtain the BGP LS message.

[0068] In a possible implementation, the configuring the first NRP includes: receiving configuration information of the first NRP sent by a controller, where the configuration information includes at least the NRP description information.

[0069] In one possible implementation, the processing unit is configured to: reserve resources for the first NRP based on the configuration information of the first NRP, and determine the status information of the first NRP based on the result of reserving resources for the first NRP, wherein if the resources are successfully reserved for the first NRP, the status information of the first NRP indicates that the resources of the first NRP are available; if the resources are failed to be reserved for the first NRP, the status information of the first NRP indicates that the resources of the first NRP are unavailable; and obtain a BGP LS message including the status information of the first NRP.

[0070] In a possible implementation, the processing unit is configured to: obtain the BGP LS message in response to a failure of an interface associated with the first NRP or unavailability of resources associated with the first NRP.

[0071] In a possible implementation manner, the NRP description information is further used to indicate a second NRP associated with the first link.

[0072] In the seventh aspect, an embodiment of the present application provides a device comprising: a processor and a memory; the memory is used to store instructions or computer programs; the processor is used to execute the instructions or computer programs, execute the method described in the first aspect and any one of the above first aspects, or execute the method described in the second aspect and any one of the above second aspects.

[0073] In an eighth aspect, an embodiment of the present application provides a computer-readable storage medium, comprising instructions or a computer program, which, when executed on a computer, enables the computer to execute the method described in the first aspect and any one of the above first aspects, or enables the computer to execute the method described in the second aspect and any one of the above second aspects.

[0074] In the ninth aspect, an embodiment of the present application provides a computer program product comprising instructions or computer programs, which, when run on a computer, enables the computer to execute the method described in the first aspect and any one of the items of the first aspect, or enables the computer to execute the method described in the second aspect and any one of the items of the second aspect.

[0075] In a tenth aspect, an embodiment of the present application provides a communication system, the communication system comprising:

[0076] A first network device that executes the method described in the first aspect and any one of the above first aspects, and a controller that executes the method described in the second aspect and any one of the above second aspects; or

[0077] A first network device that executes the method described in the third aspect and any one of the third aspects, and a controller that executes the method described in the fourth aspect and any one of the fourth aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0078] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments recorded in this application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0079] FIG1 is a schematic diagram of an exemplary application scenario provided by an embodiment of the present application;

[0080] FIG2a is a schematic diagram of the structure of a BGP message header provided in an embodiment of the present application;

[0081] FIG2 b is a schematic diagram of the structure of an MP_REACH_NLRI provided in an embodiment of the present application;

[0082] FIG2c is a schematic diagram of the structure of a link state NLRI provided in an embodiment of the present application;

[0083] FIG3 is a flow chart of a method for reporting NRP information according to an embodiment of the present application;

[0084] FIG4a is a schematic diagram of an exemplary application scenario provided in an embodiment of the present application;

[0085] FIG4 b is a schematic diagram of the reporting process of NRP information provided in an embodiment of the present application;

[0086] FIG4c is a schematic structural diagram of a first NLRI provided in an embodiment of the present application;

[0087] FIG5a is a schematic diagram of an exemplary application scenario provided by an embodiment of the present application;

[0088] FIG5 b is a schematic diagram of the reporting process of NRP information provided in an embodiment of the present application;

[0089] FIG6 is a flow chart of a method for reporting NRP information according to an embodiment of the present application;

[0090] FIG7a is a schematic diagram of another NRP information reporting process provided in an embodiment of the present application;

[0091] FIG7 b is a schematic structural diagram of another first NLRI provided in an embodiment of the present application;

[0092] FIG7c is a schematic diagram of the reporting process of NRP information provided in an embodiment of the present application;

[0093] FIG8 is a schematic structural diagram of an NRP information reporting device provided in an embodiment of the present application;

[0094] FIG9 is a schematic structural diagram of a device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0095] The embodiments of the present application provide a method and apparatus for reporting NRP information, which can implement reporting of NRP information.

[0096] To facilitate understanding, we first introduce the relevant content of NRP.

[0097] Currently, the bearer network can be divided into multiple NRPs with isolated resources by dividing the interface forwarding resources of the network device. This can be understood by referring to FIG1 , which is a schematic diagram of an exemplary application scenario provided by an embodiment of the present application.

[0098] As shown in Figure 1, network device A includes protocol port 110, and network device B includes protocol port 120. For network device A, based on protocol port 110, two corresponding logical interfaces 111 and 112 can be partitioned, and resources can be allocated to logical interfaces 111 and 112, respectively. Similarly, for network device B, based on protocol port 120, two logical interfaces 121 and 122 can be partitioned, and resources can be allocated to logical interfaces 121 and 122, respectively. Logical interfaces 111 and 121 are both associated with NRP 1, and logical interfaces 112 and 122 are both associated with NRP 2. In other words, the logical link between logical interfaces 111 and 121 is associated with NRP 1, and the logical link between logical interfaces 112 and 122 is associated with NRP 2. Each protocol port of any group of devices in a network that utilizes NRP technology can be partitioned in this manner, resulting in multiple NRPs with isolated resources. The first link between the protocol port 110 and the protocol port 120 may include a logical link between the logical interface 111 and the logical interface 121 , and a logical link between the logical interface 112 and the logical interface 122 .

[0099] The protocol ports mentioned in the embodiments of the present application can run control messages of the three-layer control protocol and the interaction protocol. Of course, in addition to transmitting control information, the protocol ports can also be used to transmit traffic during the traffic forwarding phase. The control protocols mentioned herein include but are not limited to BGP and / or Interior Gateway Protocol (IGP). In a specific example, the protocol port can be a layer 3 interface.

[0100] In addition, to facilitate NRP planning and management, you can set NRP hierarchies. These hierarchies distinguish the levels and nesting relationships of resource partitioning. NRP hierarchies can include primary, secondary, and tertiary NRPs, among others. For example, a primary NRP is set up on a Layer 3 interface to allocate resources such as bandwidth. A secondary NRP can then be further partitioned within the primary NRP, creating a nested relationship between the two resources. Similarly, a tertiary NRP can be further partitioned within the secondary NRP, and so on.

[0101] The first-level NRP can be a private network NRP or a dedicated line NRP, and the second-level NRP can also be a private network NRP or a dedicated line NRP. Among them: the private network NRP is used to provide a larger granularity NRP for specific purposes, usually in the form of a multi-point to multi-point mesh connection; the dedicated line NRP is used to divide fine-grained NRPs for different users (such as enterprise users), usually in the form of a point-to-point linear connection. Private network NRP and dedicated line NRP may have a nested relationship. In this case, the private network NRP can be called the main NRP and the dedicated line NRP can be called the child NRP. Private network NRP and dedicated line NRP can also be in a parallel relationship. Each NRP is identified by an NRP ID.

[0102] For example, a protocol port is divided into two master NRPs with different uses, whose IDs are 200 and 300 respectively. Then, within master NRP 200, sub-NRP 210 is created for user A, and sub-NRP 220 is created for user B. Within master NRP 300, sub-NRP 310 is created for user C.

[0103] When deploying NRP services, IGP or BGP is generally used to open up routing. When forwarding service traffic, at the head node of the forwarding path, the next hop and outbound interface are first found through the routing table. The outbound interface here is the aforementioned protocol port. Then, according to the NRP ID set in the matching diversion policy (such as SR Policy), the resource corresponding to the NRP ID under the outbound interface is found for forwarding. The diversion policy mentioned here can be, for example, a segment routing policy (SR policy).

[0104] For networks that apply NRP technology, the controller can calculate the service transmission path for the service based on the pre-collected NRP resources and topology information, and notify the network devices on the service transmission path to reserve resources so that the network devices can forward the service traffic based on the reserved resources in the subsequent service forwarding phase.

[0105] In practice, NRP resources and topology information may change. For example, if an NRP-associated interface on a network device fails, or if an NRP configuration is added or modified on a network device. Currently, the controller cannot detect these changes in a timely manner. Consequently, the controller cannot calculate service transmission paths based on the changed NRP resources and topology information. This can lead to service interruptions, reduced service quality, and inefficient use of network resources.

[0106] To address the above issues, in some embodiments, network devices can report NRP resources and topology information to the controller via BGP-LS, triggering the controller to recalculate routes. Specifically, refer to Request for Comments (RFC) 9085. New TLVs or sub-TLVs can be defined in the routing attributes corresponding to the BGP-LS link NLRI to carry NRP information for reporting.

[0107] However, in this manner, NRP information needs to be reported along with the link status information of the protocol port associated with the NRP, and the link status information of the protocol port itself needs to include information of all NRPs associated with the protocol port.

[0108] On the one hand, since a protocol port can be associated with multiple NRPs, as long as the status information of the interface associated with one of the NRPs changes, the link status information corresponding to the protocol port needs to be reported to the controller. As mentioned above, the link status information needs to include the information of all NRPs associated with the protocol port, which results in a large amount of data reported by the network device to the controller. In addition, most of the data reported by the network device to the controller contains invalid update data. The invalid update data mentioned here can be the NRP information corresponding to the interface whose status information in the protocol port has not changed. The NRP-associated interface mentioned here refers to the logical interface divided on the protocol port. In some scenarios, it can also be called an NRP interface (or NRP interface resource) or a slice interface (or slice interface resource). In other words, using this method will cause a large amount of unnecessary data interaction between the network device and the controller.

[0109] Furthermore, according to RFC4271, a single BGP message cannot exceed 4096 bytes. Limited by the BGPLS message size limit, the maximum amount of NRP information that can be carried in a BGP update message with a Link NLRI is limited. In other words, if a large number of NRPs are associated with the aforementioned protocol port, the aforementioned method cannot report information about all NRPs associated with the protocol port to the controller, preventing the controller from obtaining complete NRP resource and topology information.

[0110] In view of this, an embodiment of the present application provides an NRP information reporting method and apparatus, which enables network devices to report NRP information to a controller, so that the controller can obtain complete NRP resources and topology information, and can also avoid a large amount of unnecessary data interaction between the network device and the controller.

[0111] Before introducing the NRP information reporting method provided in the embodiment of the present application, the technology related to this solution is first introduced.

[0112] 1.BGP

[0113] BGP is a dynamic routing protocol used between autonomous systems (ASs). As a standard for external internet routing, BGP is widely used between internet service providers (ISPs). Currently, the most widely used version is Multi-Protocol Extensions for BGP (MP-BGP), which is an extension of BGP version 4 (BGP-4).

[0114] A BGP message consists of a BGP message header and message content. The BGP message header can be shown in Figure 2a, which is a schematic diagram of the structure of a BGP message header provided in an embodiment of the present application. As shown in Figure 2a, the BGP message header includes three parts: a marker field, a length field, and a type field. The three parts of the BGP message header can be understood in conjunction with Table 1 below.

[0115] Table 1

[0116] As shown in Table 2 below, BGP has five message types, all of which share the same BGP message header. These messages are transmitted via the Transmission Control Protocol (TCP). The maximum length of a message is 65,535 bytes, and the minimum is 19 bytes (including only the BGP message header).

[0117] Table 2

[0118] in:

[0119] BGP open messages, BGP notification messages, BGP keepalive messages, and BGP route refresh messages are not described in detail here.

[0120] BGP update messages are used to advertise routes;

[0121] In one example, routes can be announced between communication devices via MP-BGP. Specifically, the BGP messages for announcing routes exchanged between communication devices include multi-protocol reach network layer reachability information (MP_REACH_NLRI), and MP_REACH_NLRI is used to carry routes. In one example, the structure of MP_REACH_NLRI is shown in Figure 2b, which is a structural diagram of an MP_REACH_NLRI provided in an embodiment of the present application. As shown in Figure 2b, the MP_REACH_NLRI includes an address family identifier (AFI), a subsequent address family identifier (SAFI), a next hop information length field, a next hop information field, and an NLRI domain.

[0122] As an example, the AFI field can identify the network layer protocol. For example, the value of the AFI field is 1 to identify IPv4, and the value of the AFI field is 2 to identify IPv6. The value of the AFI field can refer to the relevant description of the address family number in RFC1700, which is not described in detail here. The SAFI field identifies the type of the sub-address family. For example, the value of the SAFI field is 1 to identify unicast, the value of the SAFI field is 2 to identify multicast, the value of the SAFI field is 74 to identify SD-WAN, and the value of the SAFI field is 128 to identify a virtual private network (VPN).

[0123] In one example, the aforementioned next-hop network address may refer to the network address of the next device on the path to the destination device.

[0124] In an example, the NLRI field may include one or more NLRIs, each NLRI includes a length field and an NLRI value field, and the specific content of the NLRI value may be determined according to a combination of the AFI field and the SAFI field.

[0125] The NLRI information field may include a route type field, a length field, and a type specific value field. The route type field is used to indicate the route type, the length field is the length of the type specific value field, and the type specific value field is used to carry a value related to the type corresponding to the route type field.

[0126] 2. BGP LS

[0127] BGP-LS is a method for collecting network topology, which can make topology collection simpler and more efficient.

[0128] Based on the original BGP, BGP-LS introduces a series of new NLRIs to carry information about links, nodes, and IPv4 or IPv6 prefixes. These new NLRIs are called link-state NLRIs. In one example, BGP-LS uses the MP_REACH_NLRI attribute as a container for link-state NLRIs. This means that link-state NLRIs can be carried in BGP Update messages as an MP_REACH_NLRI attribute. In another example, BGP-LS uses the MP_UNREACH_NLRI attribute as a container for link-state NLRIs. This means that link-state NLRIs can be carried in BGP Update messages as an MP_UNREACH_NLRI attribute.

[0129] See Figure 2c, which is a schematic diagram of the structure of a link state NLRI provided in an embodiment of the present application. As shown in Figure 2c, the link state NLRI includes an NLRI type field, a total NLRI length field, and a link-state NLRI field.

[0130] The NLRI type field is used to indicate the NLRI type. The current value of the NLRI type field can be understood by referring to Table 3 below.

[0131] The total NLRI length field indicates the length of the entire NLRI;

[0132] The link-state NLRI field is used to carry specific content. The content of the link-state NLRI field is determined by the value of the NLRI type field.

[0133] Table 3

[0134] Next, with reference to FIG3 , the NRP information reporting method provided in an embodiment of the present application is introduced.

[0135] FIG3 is a flow chart of an NRP information reporting method provided in an embodiment of the present application.

[0136] The NRP information reporting method shown in FIG3 may be applied to a first network device. The first network device may be a device that applies the NRP technology. For example, the first network device includes but is not limited to a router or a switch.

[0137] The method shown in FIG3 may include the following S101 - S102 .

[0138] S101: A first network device obtains a BGP LS message, where the BGP LS message includes a first NLRI. The first NLRI includes link description information and NRP description information. The link description information is used to indicate a first link, and the NRP description information is used to indicate a first NRP associated with the first link.

[0139] The first NLRI is the NLRI of the BGP LS. The first NLRI includes an NLRI type field. The NLRI type field is used to indicate a type of the first NLRI.

[0140] In an example, the NLRI type field included in the first NLRI indicates that the first NLRI is a link NLRI. For example, as shown in Table 3 above, the value of the NLRI type field included in the first NLRI may be 2, indicating that the first NLRI is a link NLRI.

[0141] In another example, a new BGP LS NLRI type may be extended: NRP link NLRI. The value of the NLRI type field corresponding to the newly extended BGP LS NLRI type may be, for example, 5. In this case, the NLRI type field included in the first NLRI indicates that the first NLRI is an NRP link NLRI.

[0142] In the embodiment of the present application, the first NLRI may be an NLRI at the NRP granularity, that is, the NRP information may be reported at the NRP granularity using the first NLRI.

[0143] In one example, the first NLRI includes a link description field and an NRP description field. The link description field is used to carry the link description information, which may include information about the two endpoints of the first link connection, for example, the IP addresses of the two endpoints of the first link connection. The NRP description field is used to carry the NRP description information.

[0144] In an embodiment of the present application, the NRP description information is used to describe a first NRP, and the NRP description information includes at least information that can uniquely identify the first NRP. As a specific example, considering that the NRP ID can uniquely identify the NRP, the NRP description information may include an NRP ID for identifying the first NRP. As an example, the first NLRI may include a first TLV, for example, the aforementioned NRP description field includes a first TLV, and the first TLV is used to carry the NRP ID. In a scenario where the NRP is referred to as a network slice, the NRP ID may be a network slice ID.

[0145] In an embodiment of the present application, the first NRP is the NRP between the first network device and the second network device. The second network device and the first network device may belong to the same network domain or different network domains, which is not specifically limited in the embodiment of the present application.

[0146] In one example, in addition to the NRP ID, the NRP description information may also include other additional descriptive information of the first NRP. For example, the NRP description information may also include the name of the NRP and / or the type of the NRP. The name of the NRP mentioned here may be the name of the first NRP, and the type of the NRP mentioned here is used to indicate the purpose of the first NRP. The purpose of the NRP mentioned here may be the industry corresponding to the NRP. As a specific example, the purpose of the first NRP may be one of education, medical care, or manufacturing.

[0147] As an example, the first NLRI may include a second TLV and / or a third TLV. For example, the aforementioned NRP description field includes, in addition to the first TLV, a second TLV and / or a third TLV. The second TLV is used to carry the NRP name, and the third TLV is used to carry the type of the NRP.

[0148] In one example, the first NLRI also includes local node description information and remote node description information, and the first link is a link between the local node and the remote node. Specifically, the first NLRI also includes a local node description field and a remote node description field, the local node description field is used to carry the local node description information, and the remote node description field is used to carry the remote node description information. The local node description information can be the intermediate system to intermediate system (ISIS) system identifier (sys-ID) corresponding to the local node or the BGP router identifier (router ID) corresponding to the local node. Similarly, the remote node description information can be the ISIS sys-ID corresponding to the remote node or the BGP router ID corresponding to the remote node. In one example, the local node mentioned here can be a first network device, and the remote node mentioned here can be a second network device.

[0149] In an embodiment of the present application, in addition to the first NLRI, the BGP LS message may also include a BGP LS attribute, which is used to carry the attributes of the first NRP. In this way, the description information of the first NRP and the attributes of the first NRP can be carried in the BGP LS message.

[0150] In an embodiment of the present application, the attribute of the first NRP may include at least one attribute of the first NRP. As an example, the attribute of the first NRP may include one or more of the resource information of the first NRP, the state information of the first NRP, and the hierarchical information of the first NRP.

[0151] The resource information of the first NRP is used to indicate the resources associated with the first NRP. As a specific example, the resources associated with the first NRP may include the logical interface associated with the first NRP and / or the resources allocated to the first NRP. The logical interface associated with the first NRP mentioned here may also be referred to as an NRP interface (or NRP interface resources) or a slice interface (or slice interface resources). The resources allocated to the first NRP can be understood as the forwarding resources allocated by the first NRP. The resources allocated to the first NRP include, but are not limited to, one or more of the bandwidth, cache, and queue allocated to the first NRP.

[0152] The hierarchy information of the first NRP is used to indicate the hierarchy or level of the first NRP. In the embodiment of the present application, the hierarchy of the first NRP can be a primary NRP or a secondary NRP, which is not specifically limited in the embodiment of the present application.

[0153] For example, the NRP hierarchy information is represented by a numerical value. If the hierarchy information of the first NRP is 1, it indicates that the hierarchy of the first NRP is a first-level NRP; if the hierarchy information of the first NRP is 2, it indicates that the hierarchy of the first NRP is a second-level NRP. For another example, the NRP hierarchy information is represented by a flag bit. If the hierarchy information of the first NRP is 010, it indicates that the hierarchy of the first NRP is a second-level NRP.

[0154] When the attributes of the first NRP include the hierarchical information of the first NRP, the attributes of the first NRP also include a parent NRP ID, which is used to indicate the NRP of the previous level of the NRP. For example, the ID of the first-level NRP is 100, the ID of the second-level NRP is 200, and the first-level NRP is the parent NRP of the second-level NRP. Therefore, the hierarchical information of the NRP is 2, indicating the second-level NRP, and accordingly, the value of the parent NRP ID is 100, indicating the parent NRP of the second-level NRP, that is, the first-level NRP.

[0155] The parent NRP identifier may be included in the hierarchical information of the first NRP. For example, the hierarchical information of the first NRP is represented as (2, 100), where "2" represents the second-level NRP and "100" represents the parent NRP of the second-level NRP, i.e., the first-level NRP.

[0156] The state information of the first NRP is used to indicate the state of the first NRP. As a specific example, the state information of the first NRP may be the resource state of the first NRP, that is, the state information of the first NRP may be used to indicate the state of the resources of the first NRP.

[0157] In one example, the status of the resources possessed by the first NRP may indicate whether the resources possessed by the first NRP are available. For example, the status of the resources possessed by the first NRP indicates that the resources possessed by the first NRP are available, indicating that the network device has successfully reserved resources for the first NRP; the status of the resources possessed by the first NRP indicates that the resources possessed by the first NRP are unavailable, indicating that the network device has failed to reserve resources for the first NRP.

[0158] In another example, the status of the resources possessed by the first NRP may indicate the occupancy status of the resources possessed by the first NRP. The occupancy status may, for example, indicate the resources currently occupied in the first NRP. For example, when the first NRP is a first-level NRP, the status of the resources possessed by the first NRP may be used to indicate the resources currently occupied in the first NRP (for example, resources that have been allocated to a second-level NRP).

[0159] In one implementation, the BGP LS attribute may include multiple TLVs, each TLV being used to carry an attribute of the first NRP. For example, the BGP LS may include at least one of a fourth TLV, a fifth TLV, and a sixth TLV, wherein the fourth TLV is used to carry resource information of the first NRP, the fifth TLV is used to carry state information of the first NRP, and the sixth TLV is used to carry hierarchical information of the first NRP.

[0160] In addition, the BGP LS attribute may also carry the segment identifier (SID) of the first NRP. For example, the BGP LS attribute includes a SID TLV for carrying the SID of the first NRP. The embodiment of the present application does not specifically limit the SID TLV. In one example, the SID TLV may be an Adjacency Segment Identifier (Adj-SID) TLV defined in RFC 9085. In another example, the SID TLV may be an Endpoint with L3 cross-connect (End.X) SID TLV defined in RFC 9514, which is not described in detail here.

[0161] In an embodiment of the present application, the first network device may obtain the BGP LS message when its own NRP information changes. The obtaining of the BGP LS message mentioned herein may, for example, generate the BGP LS message. The change in the NRP information of the first network device itself may include two situations: one is that the first network device is configured with NRP, and the other is that the NRP interface associated with the NRP in the first network device fails or the resources associated with the NRP are unavailable.

[0162] As a specific example, the first network device may obtain the BGP LS message in response to being configured with the first NRP. In this case, the first NLRI may be carried in the MP-REACH-NLRI of the BGP LS message.

[0163] The embodiments of the present application do not specifically limit the specific implementation method of configuring the first NRP on the first network device. For example, the first NRP can be configured on the first network device through a network management or controller. For another example, the first NRP can be configured on the first network device through a command line. In the scenario where the first NRP is configured on the first network device through a controller, the controller can send the configuration information of the first NRP to the first network device, thereby configuring the first NRP on the first network device. In other words, the first network device can receive the configuration information of the first NRP sent by the controller, and, based on the first NRP configuration information, configure the first NRP locally, and further obtain the BGP LS message.

[0164] In the embodiment of the present application, the configuration information of the first NRP includes at least the description information of the first NRP. Of course, the configuration information of the first NRP may also include other information related to the first NRP, for example, one or more of the resource information of the first NRP, the status information of the first NRP, and the hierarchical information of the first NRP.

[0165] In a specific example, the configuration information of the first NRP may be sent by the controller to the first network device after the user completes the NRP setting (eg, initialization setting) on ​​the controller side.

[0166] In another specific example, the configuration information of the first NRP is sent to the first network device by the controller after calculating the service transmission path for the service based on the NRP resources and topology information. The configuration information is used by the first network device to reserve resources for the first NRP. In this case, the first NRP can be, for example, a secondary NRP. Accordingly, in this scenario, the resource information of the first NRP included in the configuration information can be understood as the required resources of the first NRP.

[0167] In this scenario, after the first network device receives the configuration information of the first NRP sent by the controller, it can reserve resources for the first NRP according to the configuration information of the first NRP. The first network device can determine whether there are enough resources to be reserved for the first NRP based on its own resource occupancy. In addition, the first network device can also determine the status information of the first NRP based on the result of reserving resources for the first NRP, wherein if the resources are successfully reserved for the first NRP, the status information of the first NRP indicates that the resources of the first NRP are available, and if the resources are reserved for the first NRP fails, the status information of the first NRP indicates that the resources of the first NRP are unavailable. Accordingly, when obtaining the BGP LS message, a BGP LS message including the determined status information of the first NRP can be obtained based on the determined status information of the first NRP.

[0168] As another specific example, the first network device may obtain the BGP LS message in response to a failure of an interface associated with the first NRP or unavailability of resources associated with the first NRP. For example, upon detecting a failure of an interface associated with the first NRP, the first network device immediately obtains the BGP LS message. In this case, the first NLRI may be included in the MP-UNREACH-NLRI of the BGP LS message to indicate that the first NRP is an unavailable NRP.

[0169] S102: The first network device sends the BGP LS message to the controller.

[0170] After the first network device obtains the BGP LS message, it can send the BGP LS message to the controller, thereby reporting the first NRP-related information to the controller. Accordingly, after receiving the BGP LS message, the controller can update the NRP resources and topology information to facilitate subsequent calculation of the service transmission path for the service based on the updated NRP resources and topology information.

[0171] By utilizing the solution of the embodiment of the present application, when the network device reports NRP information to the controller, NRP can be used as the granularity for reporting NRP information. The network device can report the changed NRP information to the controller, and the unchanged NRP information does not need to be reported to the controller. In this way, on the one hand, the controller can obtain the changed NRP resources and topology information in a timely manner, and on the other hand, unnecessary information interaction between the network device and the controller can be reduced.

[0172] In one example, the NRP description information in the aforementioned first NLRI can be used to indicate the second NRP associated with the first link in addition to the first NRP associated with the first link. As a specific example, if both the second NRP and the first NRP associated with the first link have changed, the NRP description information in the first NLRI is also used to indicate the second NRP associated with the first link. In this way, the information of multiple NRPs that have changed on the first network device can be reported to the controller through a BGP LS message, which can reduce the number of messages exchanged between the first network device and the controller. Of course, a BGP LS message can also carry the information of only one NRP, and the information of the aforementioned second NRP can be reported to the controller through another BGP LS message. This is not specifically limited in the embodiments of the present application.

[0173] In one example, if the NRP description information in the aforementioned first NLRI is also used to indicate a second NRP associated with the first link, the aforementioned NRP description field further includes the ID of the second NRP, the name of the second NRP, and / or the type of the second NRP. Regarding the manner in which the ID, name, and type of the second NRP are carried in the first NLRI, reference may be made to the aforementioned manner in which the ID, name, and type of the first NRP are carried in the first NLRI, and no repeated description will be given here.

[0174] Correspondingly, the aforementioned BGP LS attribute information is also used to carry the attributes of the second NRP. For the specific content of the attributes of the second NRP and its specific carrying method in the BGP LS attributes, please refer to the relevant description of the attributes of the first NRP above, which will not be repeated here.

[0175] In addition, the aforementioned BGP LS attribute information is also used to carry the SID of the second NRP. For the specific carrying method of the second NRP SID in the BGP LS attribute, please refer to the relevant description of the first NRP SID above, which will not be repeated here.

[0176] The above introduces the NRP information reporting method provided in the embodiment of the present application. Next, the solution provided in the embodiment of the present application is introduced in combination with specific scenarios.

[0177] See Figure 4a, which is a schematic diagram of an exemplary application scenario provided in an embodiment of the present application.

[0178] As shown in FIG4 a , network device A and network device B belong to the same network domain.

[0179] Next, the method provided in the embodiment of the present application is introduced by taking network device A corresponding to the first network device mentioned in the above method embodiment as an example.

[0180] The protocol port of network device A is configured with an Internet Protocol version 6 (IPv6) address of 1000:1::1 / 64, and the IPv6 address of the BGP protocol port on network device B that is connected to the BGP protocol port of network device A is 1000:1::2 / 64.

[0181] Configure the basic NRP ID on the protocol port of network device A to 1. Two NRP interfaces are associated with this protocol port:

[0182] The interface index of NRP interface 1 is 10, the primary NRP ID configured on it is 100, and the allocated bandwidth is 100M.

[0183] The interface index of NRP interface 2 is 20, the primary NRP ID configured on it is 200, and the allocated bandwidth is 200M.

[0184] The above information can be flooded and announced to all network devices in the network domain to which network device A belongs via an IGP message. The IGP message mentioned here can be, for example, an ISIS protocol message.

[0185] Referring to Figures 4b and 4c, Figure 4b is a schematic diagram of the NRP information reporting process provided in an embodiment of the present application. Figure 4c is a schematic diagram of the structure of a first NLRI provided in an embodiment of the present application. Next, in conjunction with Figures 4b and 4c, the solution provided in an embodiment of the present application is introduced.

[0186] S1: Network device A obtains BGP LS message 1 containing NLRI 1 and reports the NRP information corresponding to NRP interface 1 to the controller. The specific information reported is as follows:

[0187] NLRI type: If the NLRI 1 is a link NLRI, the value of the NLRI type field is 2; if the NLRI 1 is an NRP link NLRI, the value of the NLRI type field is 5, for example.

[0188] Local description information: ISIS SysId 0000.0000.0001.00;

[0189] Remote description information: ISIS SysId 0000.0000.0002.00;

[0190] Local IPv6 address: 1000:1::1

[0191] Peer IPv6 address: 1000:1::2

[0192] Topology ID: 2 (optional field);

[0193] NRP ID: 100;

[0194] NRP level: Level 1 NRP;

[0195] Bandwidth: 100M;

[0196] NRP interface identifier (optional): 10;

[0197] The link-state NLRI shown in FIG4c is specifically NLRI 1, which includes the following fields:

[0198] Protocol ID field, identifier field, local node descriptors field, remote node descriptors field, and NRP descriptors field.

[0199] The protocol ID field, identifier field, local node descriptors field, and remote node descriptors field can use the definitions of these fields in the existing link NLRI. The NRP descriptors field is used to carry NRP description information. The above information reported to the controller:

[0200] The NLRI type can be carried by the NLRI type field shown in Figure 4c;

[0201] The local description information can be carried by the local node description field shown in Figure 4c;

[0202] The remote description information can be carried by the remote node description field shown in Figure 4c;

[0203] The local IPv6 address, the remote IPv6 address, and the topology ID can all be carried in the link description field shown in Figure 4c;

[0204] The NRP ID can be carried by the NRP description field shown in Figure 4c;

[0205] The NRP level, bandwidth, and NRP interface identifier can all be carried through BGP LS attributes (not shown in FIG4c ). In one example, the BGP LS attributes can be located in BGP LS message 1, for example, immediately following the NLRI 1. In other words, the BGP LS attributes can be the next field of the first NLRI in the BGP LS message 1.

[0206] The NLRI 1 mentioned here may correspond to the first NLRI in the above embodiment.

[0207] NLRI 1 may be carried by MP-REACH-NLRI of the BGP LS message 1;

[0208] In the case where the network domain to which the network device A belongs applies multi-topology technology, the topology ID can be used to indicate the network topology to which the network device belongs. The network domain to which the network device A belongs mentioned here may be, for example, an ISIS network domain.

[0209] S2: Network device A obtains BGP LS message 2 including NLRI 2 and reports the NRP information corresponding to NRP interface 2 to the controller. The specific information reported is as follows:

[0210] NLRI type: If the NLRI 2 is a link NLRI, the value of the NLRI type field is 2; if the NLRI 2 is an NRP link NLRI, the value of the NLRI type field is, for example, 5;

[0211] Local description information: ISIS SysId 0000.0000.0001.00;

[0212] Remote description information: ISIS SysId 0000.0000.0002.00;

[0213] Local IPv6 address: 1000:1::1

[0214] Peer IPv6 address: 1000:1::2

[0215] Topology ID: 2;

[0216] NRP ID: 200;

[0217] NRP level: Level 1 NRP;

[0218] Bandwidth: 200M;

[0219] NRP interface ID: 20 (optional);

[0220] Regarding the fields carrying the various information reported in S2, please refer to the relevant description in S1, and no repeated description is given here.

[0221] The NLRI 2 mentioned here may correspond to the first NLRI in the above embodiment.

[0222] The NLRI 2 may be carried by the MP-REACH-NLRI of the BGP LS message 2 .

[0223] S3: After receiving the NRP information reported by network device A, the controller calculates a service transmission path for the service.

[0224] Assume that the result of calculating the transmission path for the service is:

[0225] On the NRP interface with the NRP interface ID 10, allocate 50M bandwidth to the secondary NRP with the NRP ID 150 within the primary NRP 100.

[0226] You need to allocate 80M bandwidth to the secondary NRP with NRP ID 250 within the primary NRP 200 on the interface with NRP interface ID 20.

[0227] The controller sends the NRP configuration information to network device A through the Network Configuration Protocol (NETCONF), BGP, or Path Computation Element Communication Protocol (PCEP).

[0228] S4: After receiving the NRP configuration information sent by the controller, network device A performs local NRP configuration.

[0229] Network device A configures a secondary NRP with NRP ID 150 on NRP interface 10 and attempts to allocate a bandwidth of 50 Mbps. It also configures a secondary NRP with NRP ID 250 on NRP interface 20 and attempts to allocate a bandwidth of 80 Mbps.

[0230] S5: Network device A reports NRP information to the controller based on the result of reserving resources for the secondary NRP. The NRP information includes the result of reserving resources for the secondary NRP.

[0231] Specifically: S5 may include S51 and S52.

[0232] S51: Network device A obtains BGP LS message 3 including NLRI 3 and reports NRP information corresponding to NRP ID 150 to the controller. The specific reported information is as follows:

[0233] NLRI type: If the NLRI 3 is a link NLRI, the value of the NLRI type field is 2; if the NLRI 3 is an NRP link NLRI, the value of the NLRI type field is, for example, 5;

[0234] Local description information: ISIS SysId 0000.0000.0001.00;

[0235] Remote description information: ISIS SysId 0000.0000.0002.00;

[0236] Local IPv6 address: 1000:1::1

[0237] Peer IPv6 address: 1000:1::2

[0238] Topology ID: 2 (optional field);

[0239] NRP ID: 150;

[0240] NRP level: Secondary NRP;

[0241] Bandwidth: 50M;

[0242] NRP interface ID: 10;

[0243] Resource status: Available.

[0244] The NLRI3 mentioned here may correspond to the first NLRI in the above embodiment.

[0245] NLRI 3 can be carried by MP-REACH-NLRI in the BGP LS message 3

[0246] S52: Network device A obtains BGP LS message 4 including NLRI 4 and reports NRP information corresponding to NRP ID 250 to the controller. The specific reported information is as follows:

[0247] NLRI type: If the NLRI 4 is a link NLRI, the value of the NLRI type field is 2; if the NLRI 4 is an NRP link NLRI, the value of the NLRI type field is, for example, 5;

[0248] Local description information: ISIS SysId 0000.0000.0001.00;

[0249] Remote description information: ISIS SysId 0000.0000.0002.00;

[0250] Local IPv6 address: 1000:1::1

[0251] Peer IPv6 address: 1000:1::2

[0252] Topology ID: 2 (optional field);

[0253] NRP ID: 250;

[0254] NRP level: Secondary NRP;

[0255] Bandwidth: 80M;

[0256] NRP interface ID: 20;

[0257] Resource status: Available.

[0258] The NLRI 4 mentioned here may correspond to the first NLRI in the above embodiment.

[0259] Regarding the fields carrying the various information reported in S51 and S52, please refer to the relevant description in S1, and no repeated description is given here.

[0260] The NLRI 4 may be carried by the MP-REACH-NLRI of the BGP LS message 4 .

[0261] After receiving the NRP information reported by the network device A, the controller may obtain the latest NRP resources and topology information based on the received NRP information, so as to subsequently calculate a service transmission path for the service based on the latest NRP resources and topology information.

[0262] In one example, if the resource status of the NRP indicates that the resources possessed by the NRP are unavailable, it means that the network device has failed to reserve resources for the NRP. In this case, after the controller receives the NRP information sent by the network device, it can output an alarm message, or recalculate the service transmission path for the service (for example, reduce the required bandwidth and recalculate the service transmission path for the service).

[0263] In addition, if a certain NRP interface of network device A, such as NRP interface 1, fails, network device A may execute:

[0264] S6: Obtain BGP LS message 5 including NLRI 5, and report the NRP information corresponding to NRP interface 1 to the controller. The specific information reported is the same as the information reported in BGP LS message 1 in S1. For the specific reporting content, please refer to the description of S1 above and will not be repeated here.

[0265] The difference between S6 and S1 is that in S1, NLRI 1 can be carried by MP-REACH-NLRI of BGP LS message 1. In S6, NLRI 5 is carried by MP-UNREACH-NLRI of BGP LS message 5.

[0266] See Figure 5a, which is a schematic diagram of an exemplary application scenario provided in an embodiment of the present application.

[0267] As shown in Figure 5a, network device A and network device B belong to different network domains. Network device A belongs to network domain A, and network device B belongs to network domain B. The two can interact through BGP.

[0268] Next, the method provided in the embodiment of the present application is introduced by taking network device A corresponding to the first network device mentioned in the above method embodiment as an example.

[0269] The protocol port on network device A is configured with the Internet Protocol version 6 (IPv6) address 1000:1::1 / 64. The IPv6 address of the BGP protocol port on network device B connected to the BGP protocol port on network device A is 1000:1::2 / 64. The BGP router ID of network device A is 1.1.1.1, and the BGP router ID of network device B is 2.2.2.2. The BGP ID of the protocol port on network device A is 1, and the BGP ID of the protocol port on network device B is 0.

[0270] Configure the basic NRP ID on the protocol port of network device A to 1. Two NRP interfaces are associated with this protocol port:

[0271] The interface index of NRP interface 1 is 10, the primary NRP ID configured on it is 100, and the allocated bandwidth is 100M.

[0272] The interface index of NRP interface 2 is 20, the primary NRP ID configured on it is 200, and the allocated bandwidth is 200M.

[0273] See Figure 5b, which is a schematic diagram of the NRP information reporting process provided by the embodiment of the present application. Next, the solution provided by the embodiment of the present application is introduced in conjunction with Figure 5b and Figure 4c.

[0274] S1': Network device A obtains BGP LS message 1 including NLRI 1 and reports the NRP information corresponding to NRP interface 1 to the controller. The specific information reported is as follows:

[0275] NLRI type: If the NLRI 1 is a link NLRI, the value of the NLRI type field is 2; if the NLRI 1 is an NRP link NLRI, the value of the NLRI type field is 5, for example.

[0276] Local description information: BGP router ID 1.1.1.1;

[0277] Remote description information: BGP router ID 2.2.2.2;

[0278] Local IPv6 address: 1000:1::1

[0279] Peer IPv6 address: 1000:1::2

[0280] Local BGP node ID: 1;

[0281] Peer BGP node ID: 0;

[0282] NRP ID: 100;

[0283] NRP level: Level 1 NRP;

[0284] Bandwidth: 100M;

[0285] NRP interface identifier (optional): 10;

[0286] in:

[0287] The NLRI type can be carried by the NLRI type field shown in Figure 4c;

[0288] The local description information can be carried by the local node description field shown in Figure 4c;

[0289] The remote description information can be carried by the remote node description field shown in Figure 4c;

[0290] The local IPv6 address, the remote IPv6 address, the local BGP node identifier, and the remote BGP node identifier can all be carried in the link description field shown in FIG4 c ;

[0291] The NRP ID can be carried by the NRP description field shown in Figure 4c;

[0292] The NRP level, bandwidth, and NRP interface identifier can all be carried through BGP LS attributes (not shown in FIG4c ). In one example, the BGP LS attributes can be located in BGP LS message 1, for example, immediately following the NLRI 1. In other words, the BGP LS attributes can be the next field of the first NLRI in the BGP LS message 1.

[0293] The NLRI 1 mentioned here may correspond to the first NLRI in the above embodiment.

[0294] The NLRI 1 may be carried by the MP-REACH-NLRI of the BGP LS message 1 .

[0295] S2': Network device A obtains BGP LS message 2 including NLRI 2 and reports the NRP information corresponding to NRP interface 2 to the controller. The specific information reported is as follows:

[0296] NLRI type: If the NLRI 2 is a link NLRI, the value of the NLRI type field is 2; if the NLRI 2 is an NRP link NLRI, the value of the NLRI type field is, for example, 5;

[0297] Local description information: BGP router ID 1.1.1.1;

[0298] Remote description information: BGP router ID 2.2.2.2;

[0299] Local IPv6 address: 1000:1::1

[0300] Peer IPv6 address: 1000:1::2

[0301] Local BGP node ID: 1;

[0302] Peer BGP node ID: 0;

[0303] NRP level: Level 1 NRP;

[0304] Bandwidth: 200M;

[0305] NRP interface ID: 20 (optional);

[0306] Regarding the fields carrying various information reported in S2', please refer to the relevant description in S1', and no repeated description is given here.

[0307] The NLRI 2 mentioned here may correspond to the first NLRI in the above embodiment.

[0308] The NLRI 2 may be carried by the MP-REACH-NLRI of the BGP LS message 2 .

[0309] S3': After receiving the NRP information reported by network device A, the controller calculates a service transmission path for the service.

[0310] Assume that the result of calculating the transmission path for the service is:

[0311] On the NRP interface with the NRP interface ID 10, allocate 50M bandwidth to the secondary NRP with the NRP ID 150 within the primary NRP 100.

[0312] You need to allocate 80M bandwidth to the secondary NRP with NRP ID 250 within the primary NRP 200 on the interface with NRP interface ID 20.

[0313] The controller delivers the NRP configuration information to network device A through NETCONF, BGP, or PCEP.

[0314] S4': After receiving the NRP configuration information sent by the controller, network device A performs local NRP configuration.

[0315] Network device A configures a secondary NRP with NRP ID 150 on NRP interface 10 and attempts to allocate a bandwidth of 50 Mbps. It also configures a secondary NRP with NRP ID 250 on NRP interface 20 and attempts to allocate a bandwidth of 80 Mbps.

[0316] S5': Network device A reports NRP information to the controller based on the result of reserving resources for the secondary NRP. The NRP information includes the result of reserving resources for the secondary NRP.

[0317] Specifically: S5 may include S51 and S52.

[0318] S51′: Network device A obtains BGP LS message 3 including NLRI 3 and reports NRP information corresponding to NRP ID 150 to the controller. The specific reported information is as follows:

[0319] NLRI type: If the NLRI 3 is a link NLRI, the value of the NLRI type field is 2; if the NLRI 3 is an NRP link NLRI, the value of the NLRI type field is, for example, 5;

[0320] Local description information: BGP router ID 1.1.1.1;

[0321] Remote description information: BGP router ID 2.2.2.2I;

[0322] Local IPv6 address: 1000:1::1

[0323] Peer IPv6 address: 1000:1::2

[0324] Local BGP node ID: 1;

[0325] Peer BGP node ID: 0; NRP ID: 150;

[0326] NRP level: Secondary NRP;

[0327] Bandwidth: 50M;

[0328] NRP interface ID: 10;

[0329] Resource status: Available.

[0330] The NLRI3 mentioned here may correspond to the first NLRI in the above embodiment.

[0331] The NLRI 3 may be carried by the MP-REACH-NLRI of the BGP LS message 3 .

[0332] S52': Network device A obtains BGP LS message 4 including NLRI 4 and reports NRP information corresponding to NRP ID 250 to the controller. The specific reported information is as follows:

[0333] NLRI type: If the NLRI 4 is a link NLRI, the value of the NLRI type field is 2; if the NLRI 4 is an NRP link NLRI, the value of the NLRI type field is, for example, 5;

[0334] Local description information: router ID 1.1.1.1;

[0335] Remote description information: BGP router ID 2.2.2.2;

[0336] Local IPv6 address: 1000:1::1

[0337] Peer IPv6 address: 1000:1::2

[0338] Local BGP node ID: 1;

[0339] Peer BGP node ID: 0;

[0340] NRP ID: 250;

[0341] NRP level: Secondary NRP;

[0342] Bandwidth: 80M;

[0343] NRP level interface ID: 20;

[0344] Resource status: Available.

[0345] The NLRI 4 mentioned here may correspond to the first NLRI in the above embodiment.

[0346] Regarding the fields carrying various information reported in S51 ′ and S52 ′, reference may be made to the relevant description in S1 ′, and a repeated description will not be given here.

[0347] The NLRI 4 may be carried by the MP-REACH-NLRI of the BGP LS message 4 .

[0348] After receiving the NRP information reported by the network device A, the controller may obtain the latest NRP resources and topology information based on the received NRP information, so as to subsequently calculate a service transmission path for the service based on the latest NRP resources and topology information.

[0349] In one example, if the resource status of the NRP indicates that the resources possessed by the NRP are unavailable, it means that the network device has failed to reserve resources for the NRP. In this case, after the controller receives the NRP information sent by the network device, it can output an alarm message, or recalculate the service transmission path for the service (for example, reduce the required bandwidth and recalculate the service transmission path for the service).

[0350] In addition, if a certain NRP interface of network device A, such as NRP interface 1, fails, network device A may execute:

[0351] S6': Obtain BGP LS message 5 including NLRI 5, and report the NRP information corresponding to NRP interface 1 to the controller. The specific information reported is the same as the information reported in BGP LS message 1 in S1'. For the specific reporting content, please refer to the description of S1' above and will not be repeated here.

[0352] The difference between S6′ and S1′ is that in S1′, NLRI 1 can be carried by MP-REACH-NLRI of BGP LS message 1. In S6′, NLRI 5 is carried by MP-UNREACH-NLRI of BGP LS message 5.

[0353] The embodiment of the present application also provides a method for reporting NRP information. Next, the method is described in conjunction with the accompanying drawings.

[0354] Referring to Figure 6, which is a flow chart of a method for reporting NRP information provided by an embodiment of the present application, the method shown in Figure 6 may include the following steps S201-S202.

[0355] S201: A first network device obtains a BGP LS message, where the BGP LS message includes a first NLRI. The first NLRI includes node description information and NRP description information. The node description information is used to indicate the first network device, and the NRP description information is used to indicate a first NRP associated with the first network device.

[0356] The first NLRI is the NLRI of the BGP LS. The first NLRI includes an NLRI type field. The NLRI type field is used to indicate a type of the first NLRI.

[0357] In an example, the NLRI type field included in the first NLRI indicates that the first NLRI is a node NLRI. For example, as shown in Table 3 above, the value of the NLRI type field included in the first NLRI may be 1, indicating that the first NLRI is a node NLRI.

[0358] In another example, a new BGP LS NLRI type may be extended: the NRP node NLRI type. The value of the NLRI type field corresponding to the newly extended BGP LS NLRI type may be, for example, 6. In this case, the NLRI type field included in the first NLRI indicates that the first NLRI is an NRP node NLRI.

[0359] In the embodiment of the present application, the first NLRI may be an NLRI at the NRP granularity, that is, the NRP information may be reported at the NRP granularity using the first NLRI.

[0360] In one example, the first NLRI includes a node description field and an NRP description field. The node description field is used to carry information about the first network device, such as an identifier of the first network device. The NRP description field is used to carry the NRP description information. For details about the NRP description information, please refer to the relevant description of the method shown in Figure 3 above and will not be repeated here.

[0361] In one example, in addition to the first NLRI, the BGP LS message may also include a BGP LS attribute, which is used to carry the attributes of the first NRP. In this way, both the description information of the first NRP and the attributes of the first NRP can be carried in the BGP LS message. For details about the BGP LS attributes and the first NRP attributes, please refer to the relevant description of the method shown in Figure 3 above, and will not be repeated here.

[0362] In one example, the BGP LS attribute is also used to carry the SID of the first NRP. For the specific implementation of the BGP LS attribute carrying the SID of the first NRP, please refer to the description of the embodiment shown in Figure 3 above, which will not be repeated here.

[0363] In the embodiment of the present application, the first network device can obtain the BGP LS message when its own NRP information changes. Regarding the scenario in which the first network device's own NRP information changes, please refer to the relevant description of the method shown in Figure 3 above, and will not be repeated here.

[0364] In one example, the first NLRI also includes local node description information. Specifically, the first NLRI also includes a local node description field, which is used to carry the local node description information. The local node mentioned here may be the first network device.

[0365] S202: The first network device sends the BGP LS message to the controller.

[0366] After the first network device obtains the BGP LS message, it can send the BGP LS message to the controller, thereby reporting the first NRP-related information to the controller. Accordingly, after receiving the BGP LS message, the controller can update the NRP resources and topology information to facilitate subsequent calculation of the service transmission path for the service based on the updated NRP resources and topology information.

[0367] By utilizing the solution of the embodiment of the present application, when the network device reports NRP information to the controller, NRP can be used as the granularity for reporting NRP information. The network device can report the changed NRP information to the controller. In this way, on the one hand, the controller can obtain the changed NRP resources and topology information in a timely manner, and on the other hand, unnecessary information interaction between the network device and the controller can be reduced.

[0368] Next, in combination with the network scenarios shown in FIG. 4 a and FIG. 5 a , the method shown in FIG. 6 is introduced by taking the network device A corresponding to the first network device mentioned in the method embodiment corresponding to FIG. 6 as an example.

[0369] First, the reporting process of NRP information corresponding to the network scenario shown in FIG4a is introduced.

[0370] Referring to Figures 7a and 7b, Figure 7a is a schematic diagram of another NRP information reporting process provided in an embodiment of the present application. Figure 7b is a schematic diagram of the structure of another first NLRI provided in an embodiment of the present application. Next, in conjunction with Figures 7a and 7b, the solution provided in an embodiment of the present application is introduced.

[0371] S7: Network device A obtains BGP LS message 1 including NLRI 1 and reports the NRP information corresponding to NRP interface 1 to the controller. The specific information reported is as follows:

[0372] NLRI type: If the NLRI 1 is a node NLRI, the value of the NLRI type field is 1; if the NLRI 1 is an NRP node NLRI, the value of the NLRI type field is, for example, 6.

[0373] Local description information: ISIS SysId 0000.0000.0001.00;

[0374] NRP ID: 100;

[0375] NRP level: Level 1 NRP;

[0376] Bandwidth: 100M;

[0377] in:

[0378] The link-state NLRI shown in FIG7b is specifically NLRI 1, which includes the following fields:

[0379] Protocol ID field, identifier field, local node descriptors field, and NRP descriptors field.

[0380] The protocol ID field, identifier field, and local node descriptors field can use the definitions of these fields in the existing node NLRI. The NRP descriptors field is used to carry NRP description information. The above information reported to the controller:

[0381] The NLRI type can be carried by the NLRI type field shown in Figure 7b;

[0382] The local description information can be carried by the local node description field shown in Figure 7b;

[0383] The NRP ID can be carried by the NRP description field shown in Figure 7b;

[0384] Both the NRP level and bandwidth can be carried through BGP LS attributes (not shown in Figure 7b). In one example, the BGP LS attribute can be located in BGP LS message 1, for example, immediately following the NLRI 1. In other words, the BGP LS attribute can be the next field of the first NLRI in the BGP LS message 1.

[0385] The NLRI 1 mentioned here may correspond to the first NLRI in the embodiment corresponding to FIG. 6 .

[0386] The NLRI 1 may be carried by the MP-REACH-NLRI of the BGP LS message 1 .

[0387] S8: Network device A obtains BGP LS message 2 including NLRI 2 and reports the NRP information corresponding to NRP interface 2 to the controller. The specific reported information is as follows:

[0388] NLRI type: If the NLRI 2 is a node NLRI, the value of the NLRI type field is 1; if the NLRI 2 is an NRP node NLRI, the value of the NLRI type field is, for example, 6;

[0389] Local description information: ISIS SysId 0000.0000.0001.00;

[0390] NRP ID: 200;

[0391] NRP level: Level 1 NRP;

[0392] Bandwidth: 200M;

[0393] Regarding the fields carrying various information reported in S8, please refer to the relevant description in S7, which will not be repeated here.

[0394] The NLRI 2 mentioned here may correspond to the first NLRI in the embodiment corresponding to FIG. 6 .

[0395] The NLRI 2 may be carried by the MP-REACH-NLRI of the BGP LS message 2 .

[0396] S9: After receiving the NRP information reported by network device A, the controller calculates a service transmission path for the service.

[0397] Assume that the result of calculating the transmission path for the service is:

[0398] On the NRP interface with the NRP interface ID 10, allocate 50M bandwidth to the secondary NRP with the NRP ID 150 within the primary NRP 100.

[0399] You need to allocate 80M bandwidth to the secondary NRP with NRP ID 250 within the primary NRP 200 on the interface with NRP interface ID 20.

[0400] The controller delivers the NRP configuration information to network device A through NETCONF, BGP, or PCEP.

[0401] S10: After receiving the NRP configuration information sent by the controller, network device A performs local NRP configuration.

[0402] Network device A configures a secondary NRP with NRP ID 150 on NRP interface 10 and attempts to allocate a bandwidth of 50 Mbps. It also configures a secondary NRP with NRP ID 250 on NRP interface 20 and attempts to allocate a bandwidth of 80 Mbps.

[0403] S11: Network device A reports NRP information to the controller based on the result of reserving resources for the secondary NRP. The NRP information includes the result of reserving resources for the secondary NRP.

[0404] Specifically: S11 may include S111 and S112.

[0405] S111: Network device A obtains BGP LS message 3 including NLRI 3 and reports NRP information corresponding to NRP ID 150 to the controller. The specific reported information is as follows:

[0406] NLRI type: If the NLRI 3 is a node NLRI, the value of the NLRI type field is 1; if the NLRI 3 is an NRP node NLRI, the value of the NLRI type field is, for example, 6;

[0407] Local description information: ISIS SysId 0000.0000.0001.00;

[0408] NRP ID: 150;

[0409] NRP level: Secondary NRP;

[0410] Bandwidth: 50M;

[0411] Resource status: Available.

[0412] The NLRI3 mentioned here may correspond to the first NLRI in the embodiment corresponding to FIG. 6 .

[0413] NLRI 3 can be carried by MP-REACH-NLRI in the BGP LS message 3

[0414] S112: Network device A obtains BGP LS message 4 including NLRI 4 and reports NRP information corresponding to NRP ID 250 to the controller. The specific reported information is as follows:

[0415] NLRI type: If the NLRI 4 is a node NLRI, the value of the NLRI type field is 1; if the NLRI 4 is an NRP node NLRI, the value of the NLRI type field is, for example, 6;

[0416] Local description information: ISIS SysId 0000.0000.0001.00;

[0417] NRP ID: 250;

[0418] NRP level: Secondary NRP;

[0419] Bandwidth: 80M;

[0420] Resource status: Available.

[0421] The NLRI 4 mentioned here may correspond to the first NLRI in the embodiment corresponding to FIG. 6 .

[0422] Regarding the fields carrying various information reported in S111 and S112, please refer to the relevant description in S7, which will not be repeated here.

[0423] The NLRI 4 may be carried by the MP-REACH-NLRI of the BGP LS message 4 .

[0424] After receiving the NRP information reported by the network device A, the controller may obtain the latest NRP resources and topology information based on the received NRP information, so as to subsequently calculate a service transmission path for the service based on the latest NRP resources and topology information.

[0425] In one example, if the resource status of the NRP indicates that the resources possessed by the NRP are unavailable, it means that the network device has failed to reserve resources for the NRP. In this case, after the controller receives the NRP information sent by the network device, it can output an alarm message, or recalculate the service transmission path for the service (for example, reduce the required bandwidth and recalculate the service transmission path for the service).

[0426] In addition, if a certain NRP interface of network device A, such as NRP interface 1, fails, network device A may execute:

[0427] S12: Obtain BGP LS message 5 including NLRI 5, and report the NRP information corresponding to NRP interface 1 to the controller. The specific information reported is the same as the information reported in BGP LS message 1 in S7. For the specific reporting content, please refer to the description of S7 above and will not be repeated here.

[0428] The difference between S12 and S7 is that in S7, NLRI 1 can be carried by MP-REACH-NLRI of BGP LS message 1. In S12, NLRI 5 can be carried by MP-UNREACH-NLRI of BGP LS message 5.

[0429] Next, the reporting process of NRP information corresponding to the network scenario shown in FIG5a is introduced.

[0430] See Figure 7c, which is a schematic diagram of the reporting process of NRP information provided by the embodiment of the present application. Next, the solution provided by the embodiment of the present application is introduced in conjunction with Figures 7b and 7c.

[0431] S7': Network device A obtains BGP LS message 1 including NLRI 1 and reports the NRP information corresponding to NRP interface 1 to the controller. The specific reported information is as follows:

[0432] NLRI type: If the NLRI 1 is a node NLRI, the value of the NLRI type field is 1; if the NLRI 1 is an NRP node NLRI, the value of the NLRI type field is, for example, 6.

[0433] Local description information: BGP router ID 1.1.1.1;

[0434] NRP ID: 100;

[0435] NRP level: Level 1 NRP;

[0436] Bandwidth: 100M;

[0437] in:

[0438] The NLRI type can be carried by the NLRI type field shown in Figure 7b;

[0439] The local description information can be carried by the local node description field shown in Figure 7b;

[0440] The NRP ID can be carried by the NRP description field shown in Figure 7b;

[0441] Both the NRP level and bandwidth can be carried through BGP LS attributes (not shown in Figure 7b). In one example, the BGP LS attribute can be located in BGP LS message 1, for example, immediately following the NLRI 1. In other words, the BGP LS attribute can be the next field of the first NLRI in the BGP LS message 1.

[0442] The NLRI 1 mentioned here may correspond to the first NLRI in the embodiment corresponding to FIG. 6 .

[0443] The NLRI 1 may be carried by the MP-REACH-NLRI of the BGP LS message 1 .

[0444] S8': Network device A obtains BGP LS message 2 including NLRI 2 and reports NRP information corresponding to NRP interface 2 to the controller. The specific reported information is as follows:

[0445] NLRI type: If the NLRI 2 is a node NLRI, the value of the NLRI type field is 1; if the NLRI 2 is an NRP node NLRI, the value of the NLRI type field is, for example, 6;

[0446] Local description information: BGP router ID 1.1.1.1;

[0447] NRP level: Level 1 NRP;

[0448] Bandwidth: 200M;

[0449] Regarding the fields carrying various information reported in S8', please refer to the relevant description in S7', and no repeated description is given here.

[0450] The NLRI 2 mentioned here may correspond to the first NLRI in the embodiment corresponding to FIG. 6 .

[0451] The NLRI 2 may be carried by the MP-REACH-NLRI of the BGP LS message 2 .

[0452] S9': After receiving the NRP information reported by the network device A, the controller calculates a service transmission path for the service.

[0453] Assume that the result of calculating the transmission path for the service is:

[0454] On the NRP interface with the NRP interface ID 10, allocate 50M bandwidth to the secondary NRP with the NRP ID 150 within the primary NRP 100.

[0455] You need to allocate 80M bandwidth to the secondary NRP with NRP ID 250 within the primary NRP 200 on the interface with NRP interface ID 20.

[0456] The controller delivers the NRP configuration information to network device A through NETCONF, BGP, or PCEP.

[0457] S10': After receiving the NRP configuration information sent by the controller, network device A performs local NRP configuration.

[0458] Network device A configures a secondary NRP with NRP ID 150 on NRP interface 10 and attempts to allocate a bandwidth of 50 Mbps. It also configures a secondary NRP with NRP ID 250 on NRP interface 20 and attempts to allocate a bandwidth of 80 Mbps.

[0459] S11': Network device A reports NRP information to the controller based on the result of reserving resources for the secondary NRP. The NRP information includes the result of reserving resources for the secondary NRP.

[0460] Specifically: S11 may include S111 and S112.

[0461] S111': Network device A obtains BGP LS message 3 including NLRI 3 and reports NRP information corresponding to NRP ID 150 to the controller. The specific reported information is as follows:

[0462] NLRI type: If the NLRI 3 is a node NLRI, the value of the NLRI type field is 1; if the NLRI 3 is an NRP node NLRI, the value of the NLRI type field is, for example, 6;

[0463] Local description information: BGP router ID 1.1.1.1;

[0464] NRP ID: 150;

[0465] NRP level: Secondary NRP;

[0466] Bandwidth: 50M;

[0467] Resource status: Available.

[0468] The NLRI3 mentioned here may correspond to the first NLRI in the embodiment corresponding to FIG. 6 .

[0469] The NLRI 3 may be carried by the MP-REACH-NLRI of the BGP LS message 3 .

[0470] S112': Network device A obtains BGP LS message 4 including NLRI 4 and reports NRP information corresponding to NRP ID 250 to the controller. The specific reported information is as follows:

[0471] NLRI type: If the NLRI 4 is a node NLRI, the value of the NLRI type field is 1; if the NLRI 4 is an NRP node NLRI, the value of the NLRI type field is, for example, 6;

[0472] Local description information: router ID 1.1.1.1;

[0473] NRP ID: 250;

[0474] NRP level: Secondary NRP;

[0475] Bandwidth: 80M;

[0476] Resource status: Available.

[0477] The NLRI 4 mentioned here may correspond to the first NLRI in the embodiment corresponding to FIG. 6 .

[0478] Regarding the fields carrying various information reported in S111' and S112', reference may be made to the relevant description in S7', which will not be repeated here.

[0479] The NLRI 4 may be carried by the MP-REACH-NLRI of the BGP LS message 4 .

[0480] After receiving the NRP information reported by the network device A, the controller may obtain the latest NRP resources and topology information based on the received NRP information, so as to subsequently calculate a service transmission path for the service based on the latest NRP resources and topology information.

[0481] In one example, if the resource status of the NRP indicates that the resources possessed by the NRP are unavailable, it means that the network device has failed to reserve resources for the NRP. In this case, after the controller receives the NRP information sent by the network device, it can output an alarm message, or recalculate the service transmission path for the service (for example, reduce the required bandwidth and recalculate the service transmission path for the service).

[0482] In addition, if a certain NRP interface of network device A, such as NRP interface 1, fails, network device A may execute:

[0483] S12': Obtain BGP LS message 5 including NLRI 5, and report the NRP information corresponding to NRP interface 1 to the controller. The specific reported information is the same as the information reported in BGP LS message 1 in S7'. For the specific reporting content, please refer to the description of S7' above and will not be repeated here.

[0484] The difference between S12′ and S7′ is that in S7′, NLRI 1 can be carried by MP-REACH-NLRI of BGP LS message 1. In S12′, NLRI 5 is carried by MP-UNREACH-NLRI of BGP LS message 5.

[0485] Based on the method provided in the above method embodiment, the embodiment of the present application also provides a corresponding device. Next, the device is introduced in conjunction with the accompanying drawings.

[0486] See Figure 8, which is a schematic diagram of the structure of a network resource fragmentation information reporting device provided in an embodiment of the present application. The device 800 shown in Figure 8 can be used to perform the method provided in the above method embodiment. Specifically, the device 800 can be used to perform the method shown in Figure 3 or the method shown in Figure 6. As shown in Figure 8, the device 800 includes: a processing unit 801 and a sending unit 802.

[0487] As a specific example, when the apparatus 800 is used to execute the method shown in FIG3 :

[0488] The processing unit 801 is configured to obtain a Border Gateway Protocol Link State (BGP) LS message, where the BGP LS message includes first Network Layer Reachability Information (NLRI), the first NLRI including link description information and Network Resource Fragment (NRP) description information, the link description information indicating a first link, and the NRP description information indicating a first NRP associated with the first link;

[0489] The sending unit 802 is configured to send the BGP LS message to the controller.

[0490] In a possible implementation manner, the NLRI type field included in the first NLRI indicates that the first NLRI is a link NLRI.

[0491] In a possible implementation manner, the NLRI type field included in the first NLRI indicates that the first NLRI is an NRP link NLRI.

[0492] In a possible implementation, the NRP description information includes: an NRP identification ID, where the NRP ID is used to identify the first NRP.

[0493] In a possible implementation, the NRP description information further includes: the name of the NRP and / or the type of the NRP, where the name of the NRP is the name of the first NRP, and the type of the NRP indicates the purpose of the first NRP, which includes: education, medical treatment, or manufacturing.

[0494] In one possible implementation, the BGP LS message also includes BGP LS attributes, and the BGP LS attribute information is used to carry the attributes of the first NRP, and the attributes of the first NRP include at least one of the following: resource information of the first NRP, status information of the first NRP, and hierarchical information of the first NRP.

[0495] In a possible implementation manner, the resource information includes: a logical interface associated with the first NRP and / or resources allocated to the first NRP.

[0496] In a possible implementation, the status information of the first NRP includes: status of resources owned by the first NRP, where the status of the resources indicates whether the resources are available and / or the occupancy status of the resources.

[0497] In a possible implementation manner, the hierarchy information of the first NRP indicates that the first NRP is a first-level NRP or a second-level NRP.

[0498] In a possible implementation, the processing unit 801 is configured to: in response to being configured with the first NRP, obtain the BGP LS message.

[0499] In a possible implementation, the configuring the first NRP includes: receiving configuration information of the first NRP sent by a controller, where the configuration information includes at least the NRP description information.

[0500] In one possible implementation, the processing unit 801 is used to: reserve resources for the first NRP based on the configuration information of the first NRP, and determine the status information of the first NRP based on the result of reserving resources for the first NRP, wherein if the resources are successfully reserved for the first NRP, the status information of the first NRP indicates that the resources of the first NRP are available; if the resources are reserved for the first status information fails, the status information of the first NRP indicates that the resources of the first NRP are unavailable; obtain a BGP LS message including the status information of the first NRP.

[0501] In a possible implementation, the processing unit 801 is configured to obtain the BGP LS message in response to a failure of an interface associated with the first NRP or unavailability of resources associated with the first NRP.

[0502] In a possible implementation manner, the NRP description information is further used to indicate a second NRP associated with the first link.

[0503] As another specific example, when the apparatus 800 is used to perform the method shown in FIG6 :

[0504] The processing unit 801 is configured to obtain a Border Gateway Protocol Link State (BGP) LS message, where the BGP LS message includes first network layer reachability information (NLRI), where the first NLRI includes node description information and network resource fragment (NRP) description information, where the node description information is used to indicate the first network device, and the NRP description information is used to indicate a first NRP associated with the first network device.

[0505] The sending unit 802 is configured to send the BGP LS message to the controller.

[0506] In a possible implementation manner, the NLRI type field included in the first NLRI indicates that the first NLRI is a node NLRI.

[0507] In a possible implementation manner, the NLRI type field included in the first NLRI indicates that the first NLRI is an NRP node NLRI.

[0508] In a possible implementation, the NRP description information includes: an NRP identification ID, where the NRP ID is used to identify the first NRP.

[0509] In a possible implementation, the NRP description information further includes: the name of the NRP and / or the type of the NRP, where the name of the NRP is the name of the first NRP, and the type of the NRP indicates the purpose of the first NRP, which includes: education, medical treatment, or manufacturing.

[0510] In one possible implementation, the BGP LS message also includes BGP LS attributes, and the BGP LS attribute information is used to carry the attributes of the first NRP, and the attributes of the first NRP include at least one of the following: resource information of the first NRP, status information of the first NRP, and hierarchical information of the first NRP.

[0511] In a possible implementation manner, the resource information includes: a logical interface associated with the first NRP and / or resources allocated to the first NRP.

[0512] In a possible implementation, the status information of the first NRP includes: status of resources owned by the first NRP, where the status of the resources indicates whether the resources are available and / or the occupancy status of the resources.

[0513] In a possible implementation manner, the hierarchy information of the first NRP indicates that the first NRP is a first-level NRP or a second-level NRP.

[0514] In a possible implementation, the processing unit 801 is configured to: in response to being configured with the first NRP, obtain the BGP LS message.

[0515] In a possible implementation, the configuring the first NRP includes: receiving configuration information of the first NRP sent by a controller, where the configuration information includes at least the NRP description information.

[0516] In one possible implementation, the processing unit 801 is used to: reserve resources for the first NRP based on the configuration information of the first NRP, and determine the status information of the first NRP based on the result of reserving resources for the first NRP, wherein if the resources are successfully reserved for the first NRP, the status information of the first NRP indicates that the resources of the first NRP are available; if the resources are failed to be reserved for the first NRP, the status information of the first NRP indicates that the resources of the first NRP are unavailable; obtain a BGP LS message including the status information of the first NRP.

[0517] In a possible implementation, the processing unit 801 is configured to obtain the BGP LS message in response to a failure of an interface associated with the first NRP or unavailability of resources associated with the first NRP.

[0518] In a possible implementation manner, the NRP description information is further used to indicate a second NRP associated with the first link.

[0519] It should be noted that the hardware structure of the aforementioned device 800 can be the structure shown in FIG9 , which is a schematic diagram of the structure of a device provided in an embodiment of the present application.

[0520] As shown in Figure 9 , device 900 includes a processor 910, a communication interface 920, and a memory 930. The number of processors 910 in device 900 may be one or more, and Figure 9 illustrates a single processor as an example. In embodiments of the present application, processor 910, communication interface 920, and memory 930 may be connected via a bus system or other means, and Figure 9 illustrates a connection via bus system 940 as an example.

[0521] Processor 910 may be a central processing unit (CPU), an NP, or a combination of a CPU and an NP. Processor 910 may further include a hardware chip. The hardware chip may be an ASIC, a programmable logic device (PLD), or a combination thereof. The PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

[0522] Memory 930 may include volatile memory, such as random-access memory (RAM); non-volatile memory, such as flash memory, a hard disk drive (HDD), or a solid-state drive (SSD); or a combination of the aforementioned types of memory. Memory 930 may, for example, store the identifier of the first NRP and the attributes of the first NRP.

[0523] Optionally, the memory 930 stores an operating system and programs, executable modules or data structures, or subsets thereof, or extended sets thereof, wherein the programs may include various operating instructions for implementing various operations. The operating system may include various system programs for implementing various basic services and processing hardware-based tasks. The processor 910 can read the programs in the memory 930 to implement the methods provided in the embodiments of the present application.

[0524] Bus system 940 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. Bus system 940 may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, FIG9 shows only one thick line, but this does not mean that there is only one bus or only one type of bus.

[0525] An embodiment of the present application provides a computer-readable storage medium, including instructions or a computer program, which, when executed on a computer, enables the computer to execute the method described in the above method embodiment.

[0526] An embodiment of the present application provides a computer program product comprising instructions or a computer program, which, when executed on a computer, enables the computer to execute the method described in the above method embodiment.

[0527] The terms "first," "second," "third," "fourth," and the like (if any) in the specification and claims of this application and in the accompanying drawings are used to distinguish similar objects and are not necessarily used to describe a particular order or sequential sequence. It should be understood that the terms used in this manner are interchangeable where appropriate so that the embodiments described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "including" and "having," and any variations thereof, are intended to cover non-exclusive inclusions, e.g., a process, method, system, product, or apparatus comprising a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0528] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0529] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of units is only a logical business division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interface, device or unit, which can be electrical, mechanical or other forms.

[0530] Units described as separate components may or may not be physically separate, and components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0531] In addition, each business unit in each embodiment of the present application can be integrated into a processing unit, each unit can exist physically separately, or two or more units can be integrated into a single unit. The above-mentioned integrated units can be implemented in the form of hardware or software business units.

[0532] If the integrated unit is implemented in the form of a software business unit and sold or used as a separate product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0533] Those skilled in the art will appreciate that, in one or more of the above examples, the services described herein can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these services can be stored on a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, including any medium that facilitates the transmission of computer programs from one location to another. Storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0534] The above specific implementation methods further illustrate the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above are only specific implementation methods of the present invention.

[0535] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for reporting network resource fragmentation information, characterized in that: The method comprises: The first network device obtains a Border Gateway Protocol Link State (BGP) LS message, where the BGP LS message includes first network layer reachability information (NLRI), the first NLRI including link description information and network resource fragment (NRP) description information, the link description information indicating a first link, and the NRP description information indicating a first NRP associated with the first link; The first network device sends the BGP LS message to the controller.

2. The method according to claim 1, characterized in that The NLRI type field included in the first NLRI indicates that the first NLRI is a link NLRI.

3. The method according to claim 1, characterized in that The NLRI type field included in the first NLRI indicates that the first NLRI is an NRP link NLRI.

4. The method according to any one of claims 1 to 3, characterized in that The NRP description information includes: an NRP identification ID, where the NRP ID is used to identify the first NRP.

5. The method according to claim 4, characterized in that The NRP description information also includes: The name of the NRP and / or the type of the NRP, where the name of the NRP is the name of the first NRP, and the type of the NRP indicates the purpose of the first NRP, where the purpose of the first NRP includes: education, medical treatment, or manufacturing.

6. The method according to any one of claims 1 to 5, characterized in that The BGP LS message further includes a BGP LS attribute, where the BGP LS attribute information is used to carry attributes of the first NRP. The attributes of the first NRP include at least one of the following: Resource information of the first NRP, state information of the first NRP, and hierarchy information of the first NRP.

7. The method according to claim 6, characterized in that The resource information includes: The logical interface associated with the first NRP and / or the resources allocated by the first NRP.

8. The method according to claim 6, characterized in that The status information of the first NRP includes: The first NRP has a resource status, where the resource status indicates whether the resource is available and / or an occupancy status of the resource.

9. The method according to claim 6, characterized in that The hierarchical information of the first NRP indicates a level of the first NRP.

10. The method according to any one of claims 1 to 9, characterized in that: The first network device obtains a Border Gateway Protocol Link State (BGP LS) message, including: In response to being configured with the first NRP, the first network device obtains the BGP LS message.

11. The method according to claim 10, characterized in that The network device is configured with the first NRP, including: The first network device receives configuration information of the first NRP sent by the controller, where the configuration information at least includes the NRP description information.

12. The method according to claim 11, characterized in that The method further comprises: The first network device reserves resources for the first NRP based on the configuration information of the first NRP, and determines status information of the first NRP according to a result of reserving resources for the first NRP, wherein if reserving resources for the first NRP succeeds, the status information of the first NRP indicates that the resources of the first NRP are available; if reserving resources for the first status information fails, the status information of the first NRP indicates that the resources of the first NRP are unavailable; Accordingly, the first network device obtains a Border Gateway Protocol Link State BGP LS message, including: The first network device obtains a BGP LS message including the state information of the first NRP.

13. The method according to any one of claims 1 to 9, characterized in that: The first network device obtains a Border Gateway Protocol Link State (BGP LS) message, including: The first network device obtains the BGP LS message in response to a failure of an interface associated with the first NRP or unavailability of a resource associated with the first NRP.

14. The method according to any one of claims 1 to 13, characterized in that The NRP description information is further used to indicate a second NRP associated with the first link.

15. A method for reporting network resource fragmentation information, characterized in that: The method comprises: The first network device obtains a Border Gateway Protocol Link State (BGP) LS message, where the BGP LS message includes first Network Layer Reachability Information (NLRI), where the first NLRI includes node description information and Network Resource Fragment (NRP) description information, where the node description information is used to indicate the first network device, and the NRP description information is used to indicate a first NRP associated with the first network device. The first network device sends the BGP LS message to the controller.

16. The method according to claim 15, characterized in that The NLRI type field included in the first NLRI indicates that the first NLRI is a node NLRI.

17. The method according to claim 15, characterized in that The NLRI type field included in the first NLRI indicates that the first NLRI is an NRP node NLRI.

18. The method according to any one of claims 15 to 17, characterized in that: The NRP description information includes: an NRP identification ID, where the NRP ID is used to identify the first NRP.

19. The method according to claim 18, characterized in that The NRP description information also includes: The name of the NRP and / or the type of the NRP, where the name of the NRP is the name of the first NRP, and the type of the NRP indicates the purpose of the first NRP, where the purpose of the first NRP includes: education, medical treatment, or manufacturing.

20. The method according to any one of claims 15 to 19, characterized in that: The BGP LS message further includes a BGP LS attribute, where the BGP LS attribute information is used to carry attributes of the first NRP. The attributes of the first NRP include at least one of the following: Resource information of the first NRP, state information of the first NRP, and hierarchy information of the first NRP.

21. The method according to claim 20, characterized in that The resource information includes: The logical interface associated with the first NRP and / or the resources allocated by the first NRP.

22. The method according to claim 20, characterized in that The status information of the first NRP includes: The first NRP has a resource status, where the resource status indicates whether the resource is available and / or an occupancy status of the resource.

23. The method according to claim 20, characterized in that The hierarchical information of the first NRP indicates a level of the first NRP.

24. The method according to any one of claims 15 to 23, characterized in that: The first network device obtains a Border Gateway Protocol Link State (BGP LS) message, including: In response to being configured with the first NRP, the first network device obtains the BGP LS message.

25. The method according to claim 24, characterized in that The network device is configured with the first NRP, including: The first network device receives configuration information of the first NRP sent by the controller, where the configuration information at least includes the NRP description information.

26. The method according to claim 25, characterized in that The method further comprises: The first network device reserves resources for the first NRP based on the configuration information of the first NRP, and determines, according to a result of reserving resources for the first NRP, status information of the first NRP, wherein if reserving resources for the first NRP succeeds, the status information of the first NRP indicates that the resources of the first NRP are available; and if reserving resources for the first NRP fails, the status information of the first NRP indicates that the resources of the first NRP are unavailable; Accordingly, the first network device obtains a Border Gateway Protocol Link State BGP LS message, including: The first network device obtains a BGP LS message including the state information of the first NRP.

27. The method according to any one of claims 15 to 23, characterized in that: The first network device obtains a Border Gateway Protocol Link State (BGP LS) message, including: The first network device obtains the BGP LS message in response to a failure of an interface associated with the first NRP or unavailability of a resource associated with the first NRP.

28. The method according to any one of claims 15 to 27, characterized in that: The NRP description information is further used to indicate a second NRP associated with the first link.

29. A network resource fragmentation information reporting device, characterized in that: Applied to a first network device, the apparatus includes: a processing unit, configured to obtain a Border Gateway Protocol Link State (BGP) LS message, wherein the BGP LS message includes first network layer reachability information (NLRI), the first NLRI including link description information and network resource fragment (NRP) description information, the link description information indicating a first link, and the NRP description information indicating a first NRP associated with the first link; The sending unit is configured to send the BGP LS message to the controller.

30. A network resource fragmentation information reporting device, characterized in that: Applied to a first network device, the apparatus includes: a processing unit, configured to obtain a Border Gateway Protocol Link State (BGP) LS message, wherein the BGP LS message includes first network layer reachability information (NLRI), the first NLRI including node description information and network resource fragment (NRP) description information, the node description information being used to indicate the first network device, and the NRP description information being used to indicate a first NRP associated with the first network device; The sending unit is configured to send the BGP LS message to the controller.

31. A device, characterized in that include: processor and memory; The memory is used to store instructions or computer programs; The processor is configured to execute the instructions or computer program and perform the method according to any one of claims 1 to 28.

32. A computer-readable storage medium, characterized in that The method comprises instructions or computer programs which, when executed on a computer, cause the computer to execute the method according to any one of claims 1 to 28.

33. A computer program product, characterized in that The invention comprises a computer program which, when executed on a processor, executes the method according to any one of claims 1 to 28.

Images