Mapping relation notification method and device, storage medium and electronic device

Abstract

The embodiment of the invention provides a mapping relation announcement method and device, a storage medium and an electronic device. The method comprises the steps of announcing a mapping relation between a segment identifier SI D and an under l ay network path to target equipment through a southbound interface protocol. By adopting the technical scheme, the problem of a mapping relation between a segment identifier SI D and an under l ay network path in a related node and / or a controller in a network is solved, the mapping relation between the segment identifier SI D and the under l ay network path is notified, so that the segment identifier SI D is arranged into an end-to-end path, and besides boundary nodes simultaneously supporting SR and under l ay network technologies in the network, the problem of the mapping relation between the segment identifier SI D and the under l ay network path is solved. And other nodes do not sense the under l ay network path.

Description

Technical Field

[0001] The present application relates to the field of communications, and in particular to a method, device, storage medium, and electronic device for notifying a mapping relationship. Background Art

[0002] For non-IP links, which can be LO optical links WDM / PON; wireless links (5G / Wifi), space links, L1 tunnels and L2 links, etc. coexist with SRv6 networks and SR networks are integrated with non-IP networks (such as optical networks). Currently, when the head node or controller orchestrates end-to-end SRv6 paths, a mapping relationship between END.BXC SID and underlying path (e.g., MTN path) is required to achieve end-to-end SRv6 path orchestration and orchestrate END.BXC SID into the SRv6 path. In addition, the boundary nodes that support both SR and underlay network technologies require a mapping relationship between END.BXC SID and underlying path (e.g., MTN path). The END.BXC SID in the SRH header is used to find the corresponding MTN path for message forwarding.

[0003] In the related art, there is no effective solution to the problem that there is no mapping relationship between SID and underlay network path in the relevant nodes and / or controllers in the network. Summary of the Invention

[0004] The embodiments of the present application provide a method, device, storage medium and electronic device for notifying a mapping relationship, so as to at least solve problems such as the mapping relationship between the segment identifier SID and the underlay network path in relevant nodes and / or controllers in the network.

[0005] According to one aspect of an embodiment of the present application, a method for notifying a mapping relationship is provided, comprising: notifying a mapping relationship between a segment identifier SID and an underlay network path to a target device through a southbound interface protocol.

[0006] In an exemplary embodiment, the method further includes: the southbound interface protocol includes any one of the following protocols: Extended Path Computation Element Communication Protocol (PCEP) and Network Configuration Protocol (NETCONF).

[0007] In an exemplary embodiment, the target device includes: a controller, or a PCE, or a head node, or an edge node supporting both SR and underlay network technologies.

[0008] In an exemplary embodiment, the method further includes: when the target device is the controller or the PCE, for the extended PCEP, notifying the SID and the path identifier of the underlay network path through a PCRpt message to indicate a mapping relationship between the SID and the underlay network path.

[0009] In an exemplary embodiment, the method further includes: carrying the SID and the path identifier of the underlay network path via a TLV in a label switched path (LSP) object; and advertising the LSP object carrying the SID and the path identifier of the underlay network path.

[0010] In an exemplary embodiment, the method further includes: when the target device is the head node, or a border node that supports both SR and underlay network technologies, for the extended PCEP, announcing the path identifier of the underlay network path and the SID through a PCInitiate message or a PCUpd message to indicate a mapping relationship between the SID and the underlay network path.

[0011] In an exemplary embodiment, the method further includes: carrying the path identifier of the underlay network path by using an underlay network identifier TLV extended in the LSP Object.

[0012] In an exemplary embodiment, the method further includes: the allocation node corresponding to the SID includes: a border node supporting both SR and underlay network technologies, or a controller, or a PCE.

[0013] In an exemplary embodiment, the method further includes: when the allocation node needs to modify the previously allocated SID, when the allocation node is a border node that supports SR and underlay network technologies, sending a PCRpt message to the controller or PCE, wherein the PCRpt message carries the updated SID; when the allocation node is a controller or PCE, sending a PCUpd message to the controller, wherein the PCUpd message carries the updated SID.

[0014] In an exemplary embodiment, the method further includes: receiving a request sent by a path calculation client PCE, wherein the request is used to request a border node supporting SR and underlay network technology to allocate a specific SID of a specific underlay network; when the border node supporting SR and underlay network technology determines that allocation of the specific SID is allowed, the border node supporting SR and underlay network technology allocates the specific SID and notifies the controller of the mapping relationship between the specific SID and the underlay network path; when the border node supporting SR and underlay network technology determines that the specific SID to be allocated is invalid, sending a PCErr message carrying the failure to allocate the specific SID to the path calculation client PCE.

[0015] In an exemplary embodiment, the method further includes: the path computation client PCE sending a PCUpd or PCInitiate message carrying a specific SID allocated for a specific underlay network to a border node supporting SR and underlay network technology to request allocation of the SID for the specific underlay network.

[0016] According to another aspect of an embodiment of the present application, a mapping relationship notification device is provided, including: a notification module, configured to notify a target device of a mapping relationship between a segment identifier SID and an underlay network path via a southbound interface protocol.

[0017] According to another aspect of the embodiments of the present application, a computer-readable storage medium is provided, in which a computer program is stored. The computer program is configured to execute the above-mentioned mapping relationship notification method during runtime.

[0018] According to another aspect of an embodiment of the present application, an electronic device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the method for notifying the mapping relationship through the computer program.

[0019] In an embodiment of the present application, the mapping relationship between the segment identifier (SID) and the underlay network path is announced to the target device via a southbound interface protocol. This technical solution solves the problem of the lack of a mapping relationship between the segment identifier (SID) and the underlay network path in the relevant nodes and / or controllers in the network. The above method implements the announcement of the mapping relationship between the segment identifier (SID) and the underlay network path, allowing the segment identifier (SID) to be incorporated into the end-to-end path. Except for the boundary nodes that support both SR and underlay network technologies, other nodes in the network are unaware of the underlay network path. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The exemplary embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0021] Figure 1 This is a schematic diagram of the hardware environment of a terminal device for a method for notifying a mapping relationship according to an embodiment of the present invention;

[0022] Figure 2 This is a network diagram showing the coexistence of underlay networks and SRv6 networks in related technologies.

[0023] Figure 3 Schematic diagram of a scenario in which an SR network and an optical network are integrated according to an embodiment of the present invention;

[0024] Figure 4 is a flowchart of a method for notifying a mapping relationship according to the first embodiment of the present application;

[0025] Figure 5 is a flowchart of a method for notifying a mapping relationship according to a second embodiment of the present application;

[0026] Figure 6 is a flowchart of a method for notifying a mapping relationship according to a third embodiment of the present application;

[0027] Figure 7 is a flowchart of a method for notifying a mapping relationship according to a fourth embodiment of the present application;

[0028] Figure 8 is a flowchart of a method for notifying a mapping relationship according to a fifth embodiment of the present application;

[0029] Figure 9 is a schematic diagram of a method for notifying a mapping relationship according to an embodiment of the present application;

[0030] Figure 10 is another schematic diagram of a method for notifying a mapping relationship according to an embodiment of the present application;

[0031] Figure 11 is a flowchart of a method for notifying a mapping relationship according to a sixth embodiment of the present application;

[0032] Figure 12 It is a structural block diagram of a notification device according to a mapping relationship in an embodiment of the present application. DETAILED DESCRIPTION

[0033] In order to enable those skilled in the art to better understand the present invention, the following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments in the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of this application.

[0034] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in a sequence other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0035] According to one aspect of an embodiment of the present application, a method for notifying a mapping relationship is provided. The method for notifying a mapping relationship can be executed in a terminal device or a similar computing device, for example, running on a terminal device. Figure 1 This is a hardware structure diagram of a terminal device of a method for notifying a mapping relationship according to an embodiment of the present invention. Figure 1 As shown, the terminal device may include one or more ( Figure 1 Only one is shown in the figure) processor 102 (processor 102 may include but is not limited to a microprocessor (Microprocessor Unit, referred to as MPU) or a programmable logic device (Programmable logic device, referred to as PLD)) and a memory 104 for storing data. In an exemplary embodiment, the terminal device may also include a transmission device 106 and an input / output device 108 for communication functions. It will be understood by those skilled in the art that Figure 1The structure shown is only for illustration and does not limit the structure of the above terminal device. Figure 1 More or fewer components than shown, or with Figure 1 Equivalent functions or comparisons shown Figure 1 Shown are different configurations with more functionality.

[0036] The memory 104 can be used to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the exposure and dotting method for the scrolling element in the edge area of ​​the embodiment of the present invention. The processor 102 executes the computer program stored in the memory 104 to execute various functional applications and data processing, thereby implementing the above-mentioned method. The memory 104 may include high-speed random access memory and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories may be connected to the terminal device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0037] The transmission device 106 is used to receive or transmit data via a network. A specific example of the aforementioned network may include a wireless network provided by a communications provider of a switching device. In one embodiment, the transmission device 106 includes a network interface controller (NIC), which can be connected to other network devices via a base station to enable communication with the Internet. In another embodiment, the transmission device 106 may be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0038] In related technologies, Segment Routing (SR) is a source routing technology used in network communications. This technology eliminates the need for forwarding nodes to be aware of service status and only requires maintaining topology information. This decouples service instances from the network, significantly improving the network's ability to support ubiquitous connectivity and scalability. SR works by pushing instructions carrying routing information into the packet header at the source node, and intermediate forwarding nodes pop up the relevant instructions hop by hop to forward the packet.

[0039] Currently, networks support Slicing Packet Networks (SPNs). SPNs can be networks that support SR-MPLS or underlay networks, such as MTN / OTN networks. If SR is deployed in an existing network, the SR and SPN networks must coexist and interoperate.

[0040] Figure 2 This is a network diagram of the coexistence of underlay network and SRv6 network in related technologies. Users hope to adopt end-to-end SRv6 deployment to achieve fast deployment / end-to-end fault monitoring and operation and maintenance. Figure 2 As shown, Figure 2 This is just an example diagram of an underlay network (MTN / OTN / small-granularity). The intermediate network can also be an L2 network or other non-IP networks, such as LO optical links, wavelength division multiplexing (WDM) / passive optical networks (PON); wireless links (5G / Wi-Fi); space links, etc. Nodes 1, 2, 3, and 4 belong to SRv6 network 1; 4, 5, 6, and 7 belong to the underlay network. While the underlay network cannot be fully upgraded to support SRv6, it can be enabled at the network edges (4 and 7) through upgrades or new equipment. Nodes 7, 8, 9, and 10 belong to SRv6 network 2. The established end-to-end SRv6 path is {SID1, SID 2, END.BXC SID (4, 5, 7), SID 10}, where END.BXC SID (4, 5, 7) represents the MTN path from 4 to 7. Therefore, the head node or controller orchestrating the end-to-end SRv6 path needs to obtain the mapping between the END.BXC SID and the underlying path (e.g., the MTN path) to orchestrate the end-to-end SRv6 path and integrate the END.BXC SID into the SRv6 path. Currently, there is no method to advertise the mapping between the END.BXC SID and the MTN path. Note that END.BXCSID is just a name; its behavior is to forward the message according to the underlay network mapped by the SID.

[0041] Figure 3 This is a schematic diagram of the scenario of integrating SR network and optical network. Figure 3In this example, nodes 1-7 are SR network nodes, and nodes 01-04 are optical network nodes. The user requires a low-latency link between nodes 6 and 7. The underlying optical network between nodes 1-4 can guarantee a low-latency link. The established path is {SID6, SID 1, END.BXC SID (01, 02, 04), SID4, SID7}, where END.BXC SID (01, 02, 04) represents the MTN path from node 01 to node 04. Therefore, the head node or controller orchestrating the end-to-end SRv6 path needs to obtain the mapping between the END.BXC SID and the underlying path (e.g., the MTN path). Currently, there is no method to advertise the mapping between the END.BXC SID and the MTN path. Note that the END.BXC SID is only a name; its behavior is to forward the packet according to the underlay network mapped to the SID.

[0042] In this embodiment, a method for notifying a mapping relationship is provided. The method can be applied to the above-mentioned terminal device or configured in a server. The terminal device can be a PC or a mobile terminal. This embodiment of the application does not limit this. Figure 4 4 is a flowchart of a method for notifying a mapping relationship according to a first embodiment of the present invention, the process including the following steps:

[0043] S402: Notify the target device of the mapping relationship between the segment identifier SID and the underlay network path through the southbound interface protocol.

[0044] The southbound interface protocol includes any one of the following protocols: PCEP (Extended Path Computation Element Protocol) and NETCONF (Network Configuration Protocol).

[0045] The segment identifier SID includes END.BXC SID.

[0046] The target devices include: controllers, PCEs, head nodes, or edge nodes that support both SR and underlay network technologies.

[0047] In an embodiment of the present application, a terminal device may notify a target device of a mapping relationship between a segment identifier (SID) and an underlay network path via a southbound interface protocol. The underlay network includes an L1 layer network, an L2 layer network, and an L3 layer network. The terminal device is a network-side device.

[0048] It should be noted that underlay usually refers to the underlying network infrastructure. It is the foundation of network communications, used to transmit data and support various communication protocols. Underlay networks can be physical networks (such as fiber optics, Ethernet, etc.), virtual networks (such as software-defined networks), or combinations thereof. Underlay networks provide basic connectivity capabilities, enabling different devices and nodes to communicate with each other. In network architecture, underlay networks usually correspond to overlay networks. Overlay networks are logical networks built on top of underlay networks to provide more advanced services and functions.

[0049] In an embodiment of the present application, a request sent by a path calculation client PCE can be received, wherein the request is used to request a border node supporting SR and underlay network technology to allocate a specific SID of a specific underlay network; when the border node supporting SR and underlay network technology determines that allocation of the specific SID is allowed, the border node supporting SR and underlay network technology allocates the specific SID and notifies the controller of the mapping relationship between the specific SID and the underlay network path; when the border node supporting SR and underlay network technology determines that the specific SID to be allocated is invalid, a PCErr message carrying a failure to allocate the specific SID is sent to the path calculation client PCE.

[0050] There are two types of requests for allocation of a specific SID to a border node that supports SR and underlay network technologies: one is that the PCE requests the PCC to allocate the SID without specifying the SID value; the other is that the PCE requests allocation of a specific value, in which case the value must be carried.

[0051] In an embodiment of the present application, the path computation client PCE sends a PCUpd or PCInitiate message carrying a specific SID allocated for a specific underlay network to a border node supporting SR and underlay network technology to request allocation of the SID for the specific underlay network.

[0052] In the embodiments of the present application, different target devices have different implementations of notifying the target device of the mapping relationship between the segment identifier SID and the underlay network path through the southbound interface protocol. To make it easier for those skilled in the art to understand the present application, Figure 5 is a flowchart of a method for notifying a mapping relationship according to a second embodiment of the present application. Figure 5As shown, when the target device is a controller or PCE, the implementation method of notifying the target device of the mapping relationship between the segment identifier SID and the underlay network path through the southbound interface protocol includes:

[0053] S502 : When the target device is a controller or a PCE, for the extended PCEP, the SID and the path identifier of the underlay network path are announced through a PCRpt message to indicate a mapping relationship between the SID and the underlay network path.

[0054] In the embodiment of the present application, the SID and the path identifier of the underlay network path are carried by TLV in the label switching path LSP object; and the LSP object carrying the SID and the path identifier of the underlay network path is advertised.

[0055] The allocation node corresponding to the SID includes: a controller or a PCE.

[0056] In the case where the allocating node needs to modify the previously allocated SID, a PCRpt message is sent to the target device, wherein the PCRpt message carries the updated SID.

[0057] Figure 6 is a flowchart of a method for notifying a mapping relationship according to the third embodiment of the present application. Figure 6 As shown in the figure, when the target device is a head node or an edge node that supports both SR and underlay network technologies, the implementation method of notifying the target device of the mapping relationship between the segment identifier SID and the underlay network path through the southbound interface protocol includes:

[0058] S602: When the target device is a head node or a border node that supports both SR and underlay network technologies, for the extended PCEP, the path identifier and SID of the underlay network path are announced through a PCInitiate message or a PCUpd message to indicate the mapping relationship between the SID and the underlay network path.

[0059] In the embodiment of the present application, the path identifier of the underlay network path is carried by the underlay network identifier TLV extended in the LSP Object.

[0060] The allocation nodes corresponding to the SID include: edge nodes that support both SR and underlay network technologies.

[0061] Among them, when the allocation node needs to modify the previously allocated SID, when the allocation node is a border node that supports SR and underlay network technology, a PCRpt message is sent to the controller or PCE, wherein the PCRpt message carries the updated SID; when the allocation node is a controller or PCE, a PCUpd message is sent to, wherein the PCUpd message carries the updated SID.

[0062] In an embodiment of the present application, the mapping relationship between the segment identifier (SID) and the underlay network path is announced to the target device via a southbound interface protocol. This technical solution solves the problem of the lack of a mapping relationship between the segment identifier (SID) and the underlay network path in the relevant nodes and / or controllers in the network. The above method implements the announcement of the mapping relationship between the segment identifier (SID) and the underlay network path, allowing the segment identifier (SID) to be incorporated into the end-to-end path. Except for the boundary nodes that support both SR and underlay network technologies, other nodes in the network are unaware of the underlay network path.

[0063] Next, the method for notifying the mapping relationship will be further described in conjunction with the following embodiments.

[0064] Example 1

[0065] The END.BXC SID can be locally assigned by the PCC. It is essential to notify the PCE of this information and the mapping relationship between the underlay network path. If the PCE assigns the END.BXC SID, the mapping relationship between the END.BXC SID and the underlay network path must be sent to the PCC for path forwarding. However, the existing technology does not yet implement the notification of the mapping relationship between the END.BXC SID and the underlay network path. The END.BXC SID can be understood as the segment identifier SID in the above embodiment.

[0066] Figure 7 is a flowchart of a method for notifying a mapping relationship according to the fourth embodiment of the present application, such as Figure 7 As shown in the figure, the mapping relationship between the segment identifier SID and the underlay network path is announced to the target device through the southbound interface protocol, including:

[0067] S702: The scheduled node 1 obtains underlay network path information.

[0068] The underlay network path information may be configured, and may also be sent to the predetermined node 1 through a network management or controller. The predetermined node 1 may be understood as the terminal device in the above embodiment.

[0069] S704 , the scheduled node 1 allocates an END.BXC SID and notifies the scheduled node 2 of the association between the END.BXC SID and the underlay network path.

[0070] The predetermined node 1 may notify the END.BXC SID to the predetermined node 2 via extended PCEP, BGP, and NETCONF. The predetermined node 2 may be understood as the target device in the above embodiment.

[0071] Among them, when the predetermined node 1 can be a border node that supports both SR and underlay network technologies, and the predetermined node 2 is a controller:

[0072] For the PCEP protocol, the END.BXC SID is announced via the PCRpt message. Furthermore, the END.BXC SID is carried in an extended TLV format within the LSP object. The protocol also carries the underlay network path identifier within the ERO object to associate the END.BXC SID with the underlay network path.

[0073] When the scheduled node 1 is a PCE and the scheduled node 2 is a border node or a head node that supports both SR and underlay network technologies:

[0074] For the PCEP protocol, in the PCInitiate / PCUpd messages, specifically, a new LSP-IDENTIFIERS TLV is added to the LSP object. The L1 Network Identifier TLV carries the underlay network identifier. Additionally, a new Mapping TLV is added to the LSP object to carry the END.BXC SID value. This extension associates the END.BXC SID with the underlay network path and notifies the predefined node 2.

[0075] Example 2

[0076] The following uses the PCEP protocol as the interactive signaling between network nodes and the controller. Node 1 allocates END.BXCSID. The underlay network refers to the L1 optical network. Figure 3 As shown in the figure, nodes 1-6 are SR network nodes, and nodes 01-04 are optical network nodes. A low-latency link is required to be deployed between 6 and 7. The underlying optical network between 1-4 can guarantee the low-latency link. Figure 8 is a flowchart of a method for notifying a mapping relationship according to a fifth embodiment of the present application, such as Figure 8As shown in the figure, the mapping relationship between the segment identifier SID and the underlay network path is announced to the target device through the southbound interface protocol, including:

[0077] S801, node 1 configures optical network path information.

[0078] Node 1 can be configured with optical network path information, such as underlay ID 1, through a controller or a network management system. Node 1 can be understood as the terminal device in the above embodiment.

[0079] S802: Node 1 allocates an END.BXC SID and notifies the controller of the association between the END.BXC SID and the optical network path.

[0080] Node 1 allocates END.BXC SID1 to the channel ID1 and notifies the association between the END.BXC SID and the optical network path to the controller, where the controller can be understood as the target device in the above embodiment.

[0081] Node 1 reports the association between the END.BXC SID and the optical network path through the PCRpt message. Specifically, in the LSP Object, a new LSP-IDENTIFIERS TLVs is extended, which is the path identifier TLV of the underlay network and carries the underlay network identifier. The format is as follows: Figure 9 As shown, Figure 9 This is a schematic diagram of a method for announcing mapping relationships in an embodiment of the present application. The type field indicates an underlay network. The specific underlay network type is defined in the flags field. For example, a set M indicates an MTN network, and a set O indicates an OTN network. The underlay network path identifier is carried in the underlay ID.

[0082] Among them, a new mapping TLV is extended in the LSP object to carry END.BXC SID. A possible format is as follows Figure 10 Wherein, END.BXC SID carries the SID value, and Endpoint Behavior carries the behavior type of END.BXC SID. In the embodiment of the present application, the behavior of END.BXC SID is: forwarding the message according to the underlay network mapped by the SID.

[0083] At the same time, the underlay ID and the END.BXC SID are carried in the LSP object, thereby associating the END.BXC SID with the underlay network path.

[0084] Example 3

[0085] Example 3 is based on Example 2. If node 1 wants to modify the previously allocated END.BXC SID, node 1 needs to rewrite and send a PCRpt message, and the PCRpt message carries the updated END.BXC SID value.

[0086] Example 4

[0087] Based on Example 2, if the PCE requests Node 1 to assign a specific END.BXC SID to a path in an underlay network, the PCE needs to send a PCUpd or PCInitiate message carrying the extended underlay network path identifier TLV and mapping TLV. If Node 1 can assign the END.BXC SID, Node 1 proceeds with the process of Example 2, i.e., Node 1 assigns the END.BXC SID and notifies the controller of the association between the END.BXC SID and the optical network path. If Node 1 deems the END.BXC SID requested by the PCE invalid, it needs to send a PCErr message to the PCE carrying END.BXC SID failure information. Node 1 can be understood as the terminal device in the above example, and the controller can be understood as the target device in the above example.

[0088] Example 5

[0089] The following uses the PCEP protocol as the interactive signaling between network nodes and the controller. PCE allocates END.BXC SID. The underlay network refers to the L1 optical network, such as Figure 3 As shown in the figure, nodes 1-6 are SR network nodes, and nodes 01-04 are optical network nodes. The user requires a low-latency link to be deployed between nodes 6 and 7. The underlying optical network between nodes 1-4 can guarantee a low-latency link. Figure 11 is a flowchart of a method for notifying a mapping relationship according to a sixth embodiment of the present application, such as Figure 11 As shown in the figure, the mapping relationship between the segment identifier SID and the underlay network path is announced to the target device through the southbound interface protocol, including:

[0090] S1102, node 1 configures optical network path information.

[0091] Node 1 can be configured with optical network path information, such as underlay ID 1, through a controller or a network management system. Node 1 can be understood as the terminal device in the above embodiment.

[0092] S1104 , the PCE allocates an END.BXC SID, and notifies the association between the END.BXC SID and the optical network path to node 1 .

[0093] S1106 , allocate END.BXC SID1 to underlay ID1 , and notify the controller of the association between END.BXC SID and the optical network path.

[0094] The controller may be understood as the target device in the above embodiments.

[0095] The controller uses the PCInitiate / PCUpd message to extend the new LSP-IDENTIFIERS TLVs (L1 network identifier TLV) in the path LSP Object to carry the underlay network identifier. The format is as follows: Figure 9 At the same time, the new mapping TLV is extended and carried in the LSP object. The mapping TLV format is as follows Figure 10 As shown, Figure 10 This is another schematic diagram of the notification method of the mapping relationship in an embodiment of the present application, which is mainly used to carry the END.BXC SID.

[0096] In addition, in addition to the PCE actively allocating the END.BXC SID, the node 1 may also request the PCE to allocate the END.BXC SID by sending a PCReq or PCRpt message carrying the mapping TLV and / or the underlay network identifier TLV.

[0097] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus the necessary general hardware platform, and of course it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods of each embodiment of the present application.

[0098] Figure 12 is a structural block diagram of a notification device according to a mapping relationship of an embodiment of the present application; Figure 12 Shown, including:

[0099] The notification module 1202 is configured to notify the target device of the mapping relationship between the segment identifier SID and the underlay network path through the southbound interface protocol.

[0100] The above-mentioned device notifies the target device of the mapping relationship between the segment identifier SID and the underlay network path via the southbound interface protocol, thereby solving the problem of the lack of a mapping relationship between the segment identifier SID and the underlay network path in the relevant nodes and / or controllers in the network. The above-mentioned method realizes the notification of the mapping relationship between the segment identifier SID and the underlay network path, so that the segment identifier SID is arranged into the end-to-end path. Except for the boundary nodes in the network that support both SR and underlay network technologies, other nodes are not aware of the underlay network path.

[0101] In an exemplary embodiment, the southbound interface protocol includes any one of the following protocols: Extended Path Computation Element Communication Protocol (PCEP) and Network Configuration Protocol (NETCONF).

[0102] In an exemplary embodiment, the target device includes: a controller, or a PCE, or a head node, or an edge node supporting both SR and underlay network technologies.

[0103] In an exemplary embodiment, the apparatus further includes: a first indication module, wherein the first indication module is configured to, when the target device is the controller or the PCE, notify the SID and the path identifier of the underlay network path for the extended PCEP through a PCRpt message to indicate a mapping relationship between the SID and the underlay network path.

[0104] In an exemplary embodiment, the device further includes: a first carrying module, which is used to carry the SID and the path identifier of the underlay network path through a TLV in a label switching path LSP object; and announce the LSP object carrying the SID and the path identifier of the underlay network path.

[0105] In an exemplary embodiment, the apparatus further includes: a second indication module, wherein the second indication module is configured to, when the target device is the head node or a border node that supports both SR and underlay network technologies, notify the path identifier of the underlay network path and the SID for the extended PCEP through a PCInitiate message or a PCUpd message to indicate a mapping relationship between the SID and the underlay network path.

[0106] In an exemplary embodiment, the apparatus further includes: a second carrying module, configured to carry the path identifier of the underlay network path through an underlay network identifier TLV extended in the LSP Object.

[0107] In an exemplary embodiment, the allocation node corresponding to the SID includes: a border node, a controller, or a PCE that supports both SR and underlay network technologies.

[0108] In an exemplary embodiment, the device also includes: a sending module, which is used to send a PCRpt message to the controller or PCE when the allocation node needs to modify the SID previously allocated, when the allocation node is a border node that supports SR and underlay network technology, wherein the PCRpt message carries the updated SID; when the allocation node is a controller or PCE, send a PCUpd message to, wherein the PCUpd message carries the updated SID.

[0109] In an exemplary embodiment, the device also includes: a receiving module, which is used to receive a request sent by a path calculation client PCE, wherein the request is used to request a border node that supports SR and underlay network technology to allocate a specific SID of a specific underlay network; when the border node that supports SR and underlay network technology determines that the allocation of the specific SID is allowed, the border node that supports SR and underlay network technology allocates the specific SID and notifies the controller of the mapping relationship between the specific SID and the underlay network path; when the border node that supports SR and underlay network technology determines that the specific SID to be allocated is invalid, it sends a PCErr message carrying the failure of allocating the specific SID to the path calculation client PCE.

[0110] In an exemplary embodiment, the device further includes: a request module, which is used by the path computation client PCE to send a PCUpd or PCInitiate message carrying a specific SID allocated for a specific underlay network to a border node supporting SR and underlay network technology to request allocation of the SID for the specific underlay network.

[0111] Optionally, in this embodiment, the storage medium may be configured to store program codes for executing the following steps:

[0112] S1: Notifies the target device of the mapping between the segment identifier (SID) and the underlay network path through the southbound interface protocol.

[0113] An embodiment of the present application further provides an electronic device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0114] Optionally, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor.

[0115] Optionally, in this embodiment, the processor may be configured to execute the following steps through a computer program:

[0116] S1: Notifies the target device of the mapping between the segment identifier (SID) and the underlay network path through the southbound interface protocol.

[0117] An embodiment of the present application further provides an electronic device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0118] Optionally, in this embodiment, the above-mentioned storage medium may include but is not limited to: a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk, and other media that can store program codes.

[0119] Optionally, specific examples in this embodiment may refer to the examples described in the above embodiments and optional implementation modes, and this embodiment will not be described in detail here.

[0120] Obviously, those skilled in the art should understand that the modules or steps of the present application described above can be implemented using a general-purpose computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices. Alternatively, they can be implemented using program code executable by the computing device, so that they can be stored in a storage device and executed by the computing device. In some cases, the steps shown or described can be performed in a different order than herein, or they can be made into separate integrated circuit modules, or multiple modules or steps can be made into a single integrated circuit module for implementation. Thus, the present application is not limited to any specific combination of hardware and software.

[0121] The above is only a preferred embodiment of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A method for notifying a mapping relationship, characterized in that: include: The mapping relationship between the segment identifier SID and the underlay network path is notified to the target device through the southbound interface protocol.

2. The method for notifying a mapping relationship according to claim 1, characterized in that: The method further comprises: The southbound interface protocol includes any one of the following protocols: Extended Path Computation Element Communication Protocol PCEP, Network Configuration Protocol NETCONF.

3. The method for notifying a mapping relationship according to claim 2, characterized in that: The target device includes: a controller, or a PCE, or a head node, or a border node that supports both SR and underlay network technologies.

4. The method for notifying a mapping relationship according to claim 3, characterized in that: The method further comprises: In the case where the target device is the controller or the PCE, for the extended PCEP, the SID and the path identifier of the underlay network path are notified through a PCRpt message to indicate a mapping relationship between the SID and the underlay network path.

5. The method for notifying a mapping relationship according to claim 4, characterized in that: The method further comprises: Carrying the SID and the path identifier of the underlay network path by TLV in the label switching path LSP object; An LSP object carrying the SID and the path identifier of the underlay network path is announced.

6. The method for notifying a mapping relationship according to claim 3, characterized in that: The method further comprises: When the target device is the head node, or a border node that supports both SR and underlay network technologies, for the extended PCEP, the path identifier of the underlay network path and the SID are announced through a PCInitiate message or a PCUpd message to indicate a mapping relationship between the SID and the underlay network path.

7. The method for notifying a mapping relationship according to claim 6, characterized in that: The method further comprises: The path identifier of the underlay network path is carried by the underlay network identifier TLV extended in the LSP Object.

8. The method for notifying a mapping relationship according to any one of claims 1 to 7, characterized in that: The method further comprises: The allocation node corresponding to the SID includes: a border node that supports both SR and underlay network technologies, or a controller, or a PCE.

9. The method for notifying a mapping relationship according to claim 8, characterized in that: The method further comprises: In the case where the allocating node needs to modify the previously allocated SID, When the allocation node is a border node that supports SR and underlay network technologies, a PCRpt message is sent to the controller or PCE, wherein the PCRpt message carries an updated SID; When the allocation node is a controller or a PCE, a PCUpd message is sent to the SID, wherein the PCUpd message carries an updated SID.

10. The method for notifying a mapping relationship according to claim 1, characterized in that: The method further comprises: Receive a request sent by a path computation client PCE, wherein the request is used to request a border node supporting SR and underlay network technology to allocate the specific SID of a specific underlay network; In a case where the border node supporting the SR and underlay network technologies determines that the specific SID is allowed to be allocated, the border node supporting the SR and underlay network technologies allocates the specific SID and notifies the mapping relationship between the specific SID and the underlay network path to the controller; When the border node supporting the SR and underlay network technologies determines that the specific SID to be allocated is invalid, a PCErr message carrying the specific SID allocation failure is sent to the path calculation client PCE.

11. The method for notifying a mapping relationship according to claim 1, characterized in that: The method further comprises: The path calculation client PCE sends a PCUpd or PCInitiate message carrying a specific SID allocated for a specific underlay network to a border node supporting SR and underlay network technology, so as to request allocation of the SID for the specific underlay network.

12. A mapping relationship notification device, characterized in that: include: The notification module is used to notify the target device of the mapping relationship between the segment identifier SID and the underlay network path through the southbound interface protocol.

13. A computer-readable storage medium, characterized in that: The storage medium stores a computer program, wherein the computer program is configured to execute the method according to any one of claims 1 to 11 when executed.

14. An electronic device, characterized in that: The method comprises a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the method according to any one of claims 1 to 11 through the computer program.

Images