A method, system and apparatus for efficient recovery of PCEP tunnels

Abstract

The present application relates to a kind of high-efficiency recovery PCEP tunnel method, system and device.Its method part mainly includes: abstract PCEP model is mapped to uniform configuration model;PCE creates tunnel and routing result with uniform configuration model format is persisted storage;When version upgrade, PCEP tunnel is recovered directly through the persistent file generated by uniform configuration model;After upgrade and restart, only the tunnel that has changed during restart is issued, and full-amount synchronization of tunnel is not carried out.The present application recovers service data and PCEP tunnel through uniform persistent file when device version is upgraded, solves the multi-source recovery timing problem, greatly speeds up the service recovery speed;After device upgrade and start, PCE only needs to synchronize the tunnel that has changed during restart, thereby significantly reducing the data amount between PCC and PCE synchronization, saves network overhead and network bandwidth.

Description

Technical Field

[0001] This invention relates to the field of communication technology, and in particular to a method, system, and apparatus for efficiently restoring a PCEP tunnel. Background Technology

[0002] Segment Routing (SR) employs source routing principles and tunneling technology. It guides packet forwarding by pre-encapsulating segment identifiers (SIDs) assigned to nodes along the path at the source node. Combined with a centralized routing module, it allows for flexible and convenient path control and adjustment. Currently, SR supports both MPLS (Multi-Protocol Label Switching) and IPv6 (Internet Protocol version 6) data planes. Based on the MPLS data plane, SR-TE (Segment Routing Traffic Engineering) tunnels and SR-MPLS Policy tunnels use MPLS labels as SIDs. Based on the IPv6 data plane, SRv6 Policy (SegmentRouting using IPv6 Data Plane Policy) tunnels use IPv6 addresses as SIDs.

[0003] In an MPLS / SRv6 network that supports the Path Computation Element Protocol (PCEP), the SR / SRv6 tunnel creation can be triggered by the PCE server on the controller in the Active Stateful PCE (Path Computation Element) mode based on the PCEP protocol: PCE Initiated LSP, that is, the PCE server is responsible for the creation, path calculation and management of these tunnels.

[0004] During device version upgrades, all tunnels created using the PCE Initiated method will be lost, requiring the PCE server to reissue tunnels to restore services, severely impacting upgrade speed. For PCC clients supporting incremental synchronization (RFC8232), the LSP database version number on the device is reset to 1 after the upgrade, necessitating the synchronization of all LSP data, significantly increasing the burden on the PCE server.

[0005] Existing technical issues:

[0006] like Figure 1As shown, in a VPN (Virtual Private Network) topology, on the Provider Edge (PE) devices of the service provider network, MPLS networks can deploy SR-TE or SR-MPLS Policy tunnels via the PCEP protocol, and SRv6 networks can deploy SRv6 Policy tunnels via the PCEP protocol to carry Layer 2 and 3 services. When PE devices undergo version upgrades, because the tunnels created during PCE initialization on the device are dynamically created by the PCC client, all PCEP tunnels and routing results on the device will be lost after the upgrade and restart. Tunnel recovery depends entirely on the PCE server re-issuing the information. If multiple PE devices are upgraded simultaneously, after the devices start up, the PCE server needs to re-establish session connections with the PCC client of each device. The PCE needs to fully distribute tunnel initialization and path information to each PE device, which involves a very large amount of data synchronization, placing significant performance pressure on the PCE server. Service interruption during this process will severely impact the version upgrade speed and potentially affect customer experience.

[0007] Service configurations can originate from various mechanisms, such as CLI (Command Line Interface) configuration, the YANG model based on the NETCONF (Network Configuration Protocol), and the PCEP protocol. In existing technologies, SR / SRv6 tunnel and path information on PE devices can be distributed via the PCEP protocol, while other service data is distributed via the YANG model or CLI commands. During device version upgrades, the recovery order of service data and tunnel data from different tools is uncontrollable, resulting in multi-source recovery timing issues.

[0008] In view of this, how to overcome the defects and solve the problems of existing technologies is a difficult problem to be solved in this technical field. Summary of the Invention

[0009] Addressing the shortcomings or improvement needs of existing technologies, this invention provides a method, system, and apparatus for efficiently restoring PCEP tunnels. It maps the PCEP model to a unified configuration model for persistent storage, enabling efficient restoration of tunnels created during PCE initialization, while simultaneously resolving timing issues related to multi-source service recovery.

[0010] The present invention adopts the following technical solution:

[0011] In a first aspect, the present invention provides a method for efficiently restoring a PCEP tunnel, comprising:

[0012] Map the abstract PCEP model to a unified configuration model;

[0013] The tunnels and routing results created by PCE are persistently stored in a unified configuration model format;

[0014] During version upgrades, the PCEP tunnel is restored directly through the persistent files generated by the unified configuration model;

[0015] After the upgrade and restart, only the tunnels that changed during the restart period will be distributed; full tunnel synchronization will not be performed.

[0016] Furthermore, the mapping of the abstract PCEP model to a unified configuration model specifically includes:

[0017] Establish an association mapping between the PCEP model's object collection and the unified configuration model's UIM class collection, perform model mapping processing using XML data encoding, and store the model mapping relationship as an XML file.

[0018] Secondly, this invention provides a system for efficiently restoring PCEP tunnels, employing the method for efficiently restoring PCEP tunnels as described in the first aspect. The system includes a configuration mapping layer, a configuration data management layer, and a service processing layer, wherein:

[0019] The configuration mapping layer is responsible for mapping various information models, including the PCEP model, to the unified configuration model.

[0020] The configuration data management layer is responsible for the unified management, distribution, and storage of configuration model data;

[0021] The business processing layer manages business based on the distributed unified configuration model data.

[0022] Furthermore, the configuration mapping layer includes a PCEP model mapping processing unit, which is responsible for establishing an association mapping between the set of objects of the PCEP model and the set of UIM classes of the unified configuration model.

[0023] Furthermore, the PCEP model mapping processing unit performs model mapping processing using XML data encoding, storing the model mapping relationship as an XML file.

[0024] Furthermore, the configuration data management layer includes a configuration data management unit, which has a unified configuration model data receiving and processing interface for obtaining the unified configuration model data of the configuration mapping layer.

[0025] Furthermore, the PCEP model mapping processing unit obtains the element mapping relationship between the PCEP model and the unified configuration model by reading the XML file, and converts the PCEP message into a collection of UIM classes of the unified configuration model.

[0026] Furthermore, through the unified configuration model data receiving and processing interface provided by the configuration data management unit, the PCEP tunnel and the UIM class collection of routing results are stored in the configuration data management unit, thereby realizing the persistent storage of the PCEP model and the distribution of the service processing unit.

[0027] Furthermore, when upgrading the router device version, the PCEP tunnel is restored directly through the persistent file generated by the unified configuration model in the configuration data management unit without relying on the PCE server. After the router device is upgraded and restarted, the PCE server only distributes the tunnels that have changed during the restart period, and does not perform full tunnel synchronization.

[0028] On the other hand, the present invention provides an apparatus for efficiently restoring a PCEP tunnel, specifically comprising at least one processor and a memory, wherein the at least one processor and the memory are connected via a data bus, the memory stores instructions that can be executed by the at least one processor, and the instructions, after being executed by the processor, are used to complete the method for efficiently restoring a PCEP tunnel in the first aspect.

[0029] Compared with the prior art, the beneficial effects of the present invention are as follows:

[0030] This invention maps the PCEP model to a unified configuration model for persistent storage. By using a unified configuration model, the differences between PCEP, CLI, and YANG information models are masked, achieving unified business interfaces and unified storage units. This reduces redundant process handling and significantly lowers maintenance costs.

[0031] The tunnels and dynamic routing results created during the initialization of the PCE server are persistently stored in a unified configuration model format. When the device version is upgraded, business data and PCEP tunnels are restored through a unified persistent file, which solves the multi-source recovery timing problem and greatly speeds up the business recovery. After the device upgrade is started, PCE only needs to synchronize the tunnels that have changed during the restart, which significantly reduces the amount of data synchronized between PCC and PCE, saving network overhead and network bandwidth. Attached Figure Description

[0032] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the embodiments of the present invention will be briefly described below. Obviously, the drawings described below are merely some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without any creative effort.

[0033] Figure 1 A schematic diagram of the VPN network topology of the PCEP protocol provided by this invention;

[0034] Figure 2This is a schematic diagram illustrating the multi-source configuration distribution of the PCEP model, CLI command line, and YANG model provided by the present invention.

[0035] Figure 3 This invention provides an example diagram of the unified configuration model for issuing SRv6Policy tunnels and mapping using three information models: PCEP, CLI command line, and YANG.

[0036] Figure 4 This is a system block diagram for efficiently restoring a PCEP tunnel, provided in Embodiment 1 of the present invention.

[0037] Figure 5 This is a schematic diagram of the unified configuration model XML file for PCEP model mapping provided in Embodiment 1 of the present invention;

[0038] Figure 6 This is a sequence diagram of PCEP tunnel creation and update, model mapping, and persistence processing provided in Embodiment 1 of the present invention.

[0039] Figure 7 This is a flowchart of the PCEP tunnel recovery process during device version upgrade provided in Embodiment 1 of the present invention;

[0040] Figure 8 This is a flowchart of a method for efficiently restoring a PCEP tunnel provided in Embodiment 2 of the present invention;

[0041] Figure 9 This is a schematic diagram of a device for efficiently restoring a PCEP tunnel, provided in Embodiment 3 of the present invention. Detailed Implementation

[0042] refer to Figure 1 As shown, this embodiment of the invention is applied to an MPLS network or SRv6 network including a PCE server and a PCC client. This embodiment of the invention is applicable to SR tunnels and SRv6 tunnels created on the PE device through the PCE Initiated LSP method. The PCE stores the network topology and link resource information of the entire network. According to the user service configuration, the PCE server triggers tunnel creation and tunnel path calculation, and updates the tunnel path calculation results in real time according to the network status, and notifies the PCC client of tunnel creation and path update.

[0043] refer to Figure 2As shown, business data supports distribution from various tools. For example, the controller can distribute various business and tunnel data to the device via the YANG model, tunnel and centralized routing results via the PCEP model, or configuration can be directly distributed on the device via CLI command line. In existing technologies, after the YANG model is distributed to the device via Netconf messages, it can be converted into a CLI command line template on the device. However, tunnels created by the PCE Initiated LSP method are automatically created on the device after being parsed by the PCC client. These tunnels are not displayed to the user on the device, and the user cannot directly modify the PCEP tunnel configuration on the device via command line. The inconsistent interfaces when processing tunnel configurations from different tools lead to redundancy in the business processing flow.

[0044] refer to Figure 3 As shown, SRv6 Policy tunnel configuration can be distributed through three methods: PCEP model PCInitiate message, YANG model Netconf message, and CLI command line. This embodiment of the invention achieves the unification of PCEP, YANG, and CLI command information models through a unified configuration model, so that the business processing unit does not need to be aware of the differences in information models.

[0045] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the invention.

[0046] This invention is an architecture of a specific functional system. Therefore, the specific embodiments mainly describe the functional logic relationship of each structural module, and do not limit the specific software and hardware implementation methods.

[0047] Furthermore, the technical features involved in the various embodiments of the present invention described below can be combined with each other as long as they do not conflict with each other, and the order of the steps can be changed as long as they are logical and do not conflict. The present invention will now be described in detail with reference to the accompanying drawings and embodiments.

[0048] Example 1:

[0049] This invention provides a system for efficiently restoring PCEP tunnels, comprising a configuration mapping layer, a configuration data management layer, and a service processing layer. The configuration mapping layer is responsible for mapping various information models, including the PCEP model, to a unified configuration model. The configuration data management layer is responsible for the management, distribution, and storage of the unified configuration model data. The service processing layer performs service management based on the distributed unified configuration model data.

[0050] For details, please refer to Figure 4 As shown, the system in this preferred embodiment comprises two layers: a controller and a router device. The controller includes a PCE server, and the router device includes a configuration mapping layer, a configuration data management layer, and a service processing layer.

[0051] In this preferred embodiment, the configuration mapping layer includes a PCC client, a Netconf adaptation processing unit, a CLI command-line adaptation processing unit, and a unified configuration model-UIM class collection. The PCC client includes a PCEP model mapping processing unit, which is used to map PCEP objects to the unified configuration model. Specifically, the PCEP model mapping processing unit is responsible for establishing an association mapping between the PCEP model's object collection (OBJ / TLV collection) and the unified configuration model's UIM class collection. The PCEP model and the configuration model may have many-to-one and one-to-many relationships. To reduce coding complexity and improve mapping efficiency, the PCEP model mapping processing unit performs model mapping processing using XML data encoding, storing the model mapping relationship as an XML file. (Reference) Figure 5 As shown, a portion of the XML file is extracted, recording the mapping relationship between the SRv6 Policy tunnel PCEP TLV and UIM model elements. Figure 5 In the example, the color of the TLV element is mapped to element1 of the UIM class, the end-point of the TLV element is mapped to element2 of the UIM class, the policy-name of the TLV element is mapped to element3 of the UIM class, and the preference of the TLV element is mapped to element4 of the UIM class. Through XML data encoding, the PCEP model TLV objects are associated one-to-one with the Unified Configuration Model (UIM) elements, and this model mapping relationship is stored as an XML file. By reading the XML file, the PCEP model data can be converted into Unified Configuration Model data.

[0052] In this preferred embodiment, when the PCC client parses the PCEP message, it quickly obtains the element mapping relationship between the PCEP model and the unified configuration model by reading the XML file, writes the corresponding element values ​​into the UIM model, and stores them in the configuration data management unit. After the PCEP tunnel is converted into the unified configuration model, it can be presented to the user via CLI command line on the device, improving the user's operational flexibility. On the device, the CLI command itself supports functions such as configuration validity checking, database storage, and configuration rollback. After the PCEP tunnel is converted into the CLI command line, the above functions can be implemented directly using the existing architecture.

[0053] Continue to refer to Figure 4In this preferred embodiment, the configuration data management layer includes a configuration data management unit. This unit has a unified configuration model data receiving and processing interface for acquiring the unified configuration model data of the configuration mapping layer and storing it in a database. In this preferred embodiment, the PCEP model mapping processing unit obtains the element mapping relationship between the PCEP model and the unified configuration model by reading an XML file, and converts the PCEP message into a collection of UIM classes of the unified configuration model. Through the unified configuration model data receiving and processing interface provided by the configuration data management unit, the collection of PCEP tunnel and routing results UIM classes is stored in the configuration data management unit, realizing persistent storage of the PCEP model and the delivery of the service processing unit.

[0054] In existing technologies, PCEP tunnel recovery during device upgrades suffers from long recovery times and low efficiency. While business data from CLI commands and the YANG model can be persistently stored using CLI command-line text, tunnel data created during PCE initialization cannot be saved as command-line text. After a device upgrade and restart, the PCEP tunnel and routing results are completely lost, requiring a full re-deployment of tunnel data via PCE, resulting in a large amount of synchronized data and severely impacting upgrade speed. Furthermore, because PCEP tunnel and business data recovery originate from different sources, the recovery order becomes uncontrollable during multi-site upgrades. However, in this preferred embodiment, by mapping the PCEP tunnel to a unified configuration model, the PCEP tunnel can also be stored as a command-line text file. After the device upgrade starts, all business data, including the PCEP tunnel, is directly recovered through the persistent file generated by the configuration model, resolving the multi-source business recovery timing problem and significantly accelerating business recovery speed.

[0055] In Active Stateful PCE mode, PCInitiate messages are used for tunnel creation and deletion, while PCUpt messages are used for updating tunnel attributes, paths, and status.

[0056] refer to Figure 6 As shown, after the PCE server and PCC client establish a session connection with SR and SRv6 capabilities via messages, the PCE sends tunnel creation, deletion, and modification messages (i.e., tunnel initialization creation, tunnel update, and tunnel deletion messages) to the PCC via PCInitiate / PCUpt. The PCC is responsible for parsing the PCEP protocol messages, converting them into a unified configuration model by reading the model mapping relationship recorded in the model mapping XML file, and sending it to the configuration data management unit, which then sends it to the business processing unit. The business processing unit parses the configuration model, updates the tunnel information, and the configuration data management unit performs persistent disk storage using the configuration model. Before the device upgrade, all configurations on the device are saved, and the PCEP tunnel storage method is no different from other business storage methods.

[0057] refer to Figure 7 As shown, after the device version upgrade starts, the device does not need to rely on the controller PCE server. It can directly restore the PCEP tunnel and service data through the persistent files generated by the configuration model, thereby improving the service recovery speed. After the PCE and PCC re-establish the session connection, the PCE only needs to synchronize the tunnel that changed during the restart, thereby saving network overhead and network bandwidth.

[0058] In summary, this embodiment of the invention maps the PCEP model to a unified configuration model for persistent storage. By using a unified configuration model to shield the differences between PCEP, CLI, and YANG information models, it achieves unified business interfaces and unified storage units, reduces redundant process handling, greatly reduces maintenance costs, can efficiently restore tunnels created during PCE initialization, and solves the timing problem of multi-source business recovery.

[0059] Example 2:

[0060] like Figure 8 As shown in the figure, this embodiment of the invention provides a method for efficiently restoring a PCEP tunnel, which includes the following steps.

[0061] Step 100: Map the abstract PCEP model to a unified configuration model.

[0062] Step 200: Persistently store the tunnels and routing results created by PCE in a unified configuration model format.

[0063] Step 300: During version upgrade, the PCEP tunnel is restored directly through the persistent file generated by the unified configuration model.

[0064] Step 400: After the upgrade and restart, only the tunnels that changed during the restart period will be distributed; full tunnel synchronization will not be performed.

[0065] Specifically, for step 100 (mapping the abstract PCEP model to the unified configuration model), this preferred embodiment establishes an association mapping between the object set of the PCEP model and the UIM class set of the unified configuration model. Model mapping is performed using XML data encoding, and the model mapping relationship is stored as an XML file. (See reference...) Figure 5 As shown, this preferred embodiment stores the mapping relationship between the PCEP model object (PCEP message TLV) and the unified configuration model element as an XML file using XML data encoding. When the PCC client parses the PCEP message, it can quickly obtain the model mapping relationship by reading the XML file.

[0066] For step 200 (persistently storing the tunnels and routing results created by PCE in a unified configuration model format), this preferred embodiment maps the PCEP model to a set of Unified Information Model (UIM) classes, and then persistently stores and distributes the PCEP tunnels and routing results to the business processing unit through the unified interface provided by the configuration data management unit.

[0067] refer to Figure 3 The SRv6 Policy tunneling example diagram illustrates how, after the PCEP, CLI, and YANG models are converted to a unified configuration model, services are unaware of the differences between the three information models and only need to process the unified configuration model data issued by the data management unit. This embodiment achieves unified processing and storage units for PCEP, CLI, and YANG information model data, and also unifies the business interfaces.

[0068] In summary, during device version upgrades, the device does not need to rely on the PCE server and can directly restore the PCEP tunnel through the persistent files generated by the configuration model. After the device upgrade and restart, the PCE server only needs to distribute the tunnels that changed during the restart, without needing to perform full tunnel synchronization, which greatly speeds up the business recovery. Business data and tunnel data distributed from different source ends (PCEP, CLI, YANG) are restored from the same storage unit in the configuration data management layer, and their recovery sequence is controllable.

[0069] In summary, this embodiment of the invention maps the PCEP model to a unified configuration model for persistent storage. By using a unified configuration model to mask the differences between PCEP, CLI, and YANG information models, it achieves unified business interfaces and storage units, reducing redundant processing and significantly lowering maintenance costs. The tunnels and dynamic routing results created during PCE server initialization are persistently stored in a unified configuration model format. During device upgrades, business data and PCEP tunnels are restored through a unified persistent file, resolving multi-source recovery timing issues and greatly accelerating business recovery. After device upgrade startup, PCE only needs to synchronize the tunnels that changed during the restart, significantly reducing the amount of data synchronized between PCC and PCE, saving network overhead and bandwidth.

[0070] Example 3:

[0071] Based on the efficient PCEP tunnel recovery method provided in Embodiment 2 above, the present invention also provides an apparatus for efficiently recovering PCEP tunnels that can be used to implement the above method and system, such as... Figure 9 The diagram shown is a schematic representation of the device architecture according to an embodiment of the present invention. The device for efficiently restoring a PCEP tunnel in this embodiment includes one or more processors 21 and a memory 22. Figure 9 Take a processor 21 as an example.

[0072] Processor 21 and memory 22 can be connected via a bus or other means. Figure 9 Taking the example of a connection between China and Israel via a bus.

[0073] The memory 22, as a non-volatile computer-readable storage medium, can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules, such as the method for efficiently restoring the PCEP tunnel in Embodiment 1. The processor 21 executes various functional applications and data processing of the apparatus for efficiently restoring the PCEP tunnel by running the non-volatile software programs, instructions, and modules stored in the memory 22, thereby implementing the method for efficiently restoring the PCEP tunnel in Embodiment 2.

[0074] Memory 22 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some embodiments, memory 22 may optionally include memory remotely located relative to processor 21, which can be connected to processor 21 via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0075] The program instructions / modules are stored in memory 22. When executed by one or more processors 21, they perform the efficient PCEP tunnel recovery method described in Embodiment 2 above, for example, executing the method described above. Figure 8 The steps shown.

[0076] Those skilled in the art will understand that all or part of the steps in the various methods of the embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, which may include: read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0077] The above description is merely a preferred embodiment of the present invention and is not intended to limit the invention. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention should be included within the scope of protection of the present invention. Contents not described in detail in this specification are prior art known to those skilled in the art.

Claims

1. A method for efficiently restoring a PCEP tunnel, characterized in that, include: Mapping the abstract PCEP model to a collection of UIM (Unified Information Model) classes in the unified configuration model includes: establishing an association mapping between the collection of objects in the PCEP model and the collection of UIM classes in the unified configuration model, performing model mapping processing through XML data encoding, and storing the model mapping relationship as an XML file. The tunnels and routing results created by PCE are persistently stored in a unified configuration model format; During version upgrades, the PCEP tunnel is restored directly through the persistent files generated by the unified configuration model; After the upgrade and restart, only the tunnels that changed during the restart period will be distributed; full tunnel synchronization will not be performed.

2. A system for efficiently restoring a PCEP tunnel, employing the method for efficiently restoring a PCEP tunnel as described in claim 1, characterized in that, It includes a configuration mapping layer, a configuration data management layer, and a business processing layer, among which: The configuration mapping layer is responsible for mapping various information models, including the PCEP model, to the unified configuration model. The configuration data management layer is responsible for the unified management, distribution, and storage of configuration model data; The business processing layer manages business based on the distributed unified configuration model data.

3. The system for efficiently restoring a PCEP tunnel according to claim 2, characterized in that, The configuration mapping layer includes a PCEP model mapping processing unit, which is responsible for establishing an association mapping between the set of objects of the PCEP model and the set of UIM classes of the unified configuration model.

4. The system for efficiently restoring a PCEP tunnel according to claim 3, characterized in that, The PCEP model mapping processing unit performs model mapping processing using XML data encoding and stores the model mapping relationship as an XML file.

5. The system for efficiently restoring a PCEP tunnel according to claim 4, characterized in that, The configuration data management layer includes a configuration data management unit, which has a unified configuration model data receiving and processing interface for obtaining the unified configuration model data of the configuration mapping layer.

6. The system for efficiently restoring a PCEP tunnel according to claim 5, characterized in that, The PCEP model mapping processing unit obtains the element mapping relationship between the PCEP model and the unified configuration model by reading the XML file, and converts the PCEP message into a collection of UIM classes of the unified configuration model.

7. The system for efficiently restoring a PCEP tunnel according to claim 6, characterized in that, Through the unified configuration model data receiving and processing interface provided by the configuration data management unit, the PCEP tunnel and the UIM class collection of path calculation results are stored in the configuration data management unit to achieve persistent storage of the PCEP model.

8. The system for efficiently restoring a PCEP tunnel according to claim 6, characterized in that, When upgrading the router device version, the PCEP tunnel is restored directly through the persistent file generated by the unified configuration model in the configuration data management unit without relying on the PCE server. After the router device is upgraded and restarted, the PCE server only distributes the tunnels that have changed during the restart period and does not perform full tunnel synchronization.

9. A device for efficiently restoring a PCEP tunnel, characterized in that: The method includes at least one processor and a memory, which are connected via a data bus. The memory stores instructions that can be executed by the at least one processor. After being executed by the processor, the instructions are used to complete the method for efficiently restoring the PCEP tunnel as described in claim 1.

Images