CN103475582B - The synchronous method of a kind of LSP data and equipment - Google Patents
The synchronous method of a kind of LSP data and equipment Download PDFInfo
- Publication number
- CN103475582B CN103475582B CN201310428476.0A CN201310428476A CN103475582B CN 103475582 B CN103475582 B CN 103475582B CN 201310428476 A CN201310428476 A CN 201310428476A CN 103475582 B CN103475582 B CN 103475582B
- Authority
- CN
- China
- Prior art keywords
- pce
- database
- pcc
- lsp data
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 230000001360 synchronised effect Effects 0.000 title claims abstract description 87
- 238000000034 method Methods 0.000 title claims abstract description 27
- 238000010586 diagram Methods 0.000 description 5
- 238000004891 communication Methods 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses synchronous method and the equipment of a kind of LSP data, the method includes: when the overall version number of PCC database is newer than the overall version number of PCE database, and PCC notice PCE starts to synchronize LSP data；The sequence number information of other LSP data in PCC database to PCE, and is synchronized to PCE by LSP data newer than the overall version number of PCE database for sequence number in PCC database and corresponding sequence number synchronization by PCC；PCC notice PCE terminates to synchronize LSP data.In the embodiment of the present invention, when PCC needs to synchronize LSP data to PCE, have only to the sequence number synchronization of LSP data newer than the overall version number of PCE database for sequence number in PCC database and correspondence to PCE, and by the sequence number segment sync of other LSP data in PCC database to PCE, thus significantly reduce and between PCC with PCE, need Tong Bu data volume.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a method and an apparatus for synchronizing LSP data.
Background
MPLS (Multi-Protocol Label Switching) is a system for fast packet Switching and routing, and provides network data traffic with the capabilities of destination, routing, forwarding, and Switching. In an MPLS network, data transmission occurs on an LSP (Label Switch Path), which is a sequence of labels for each node along the Path from a source to a terminal.
In an MPLS network, in order to better calculate an LSP, a computation function based on a constrained shortest Path is currently provided by a PCE (Path computation element). Based on this, each PCC (Path Computation Client) needs to synchronize its own relevant LSP data to the PCE, and the PCE performs Path selection optimization using the LSP data of each PCC.
In the prior art, the process of synchronizing LSP data to a PCE by a PCC includes: when the global version number of the PCC database is newer than the global version number of the PCE database, the PCC synchronizes all LSP data in the PCC database and the corresponding serial numbers to the PCE, the PCE updates the PCE database by utilizing all the received LSP data and the corresponding serial numbers, and the PCE updates the global version number of the PCE database.
However, even if there is only a small amount of LSP data inconsistency between the PCC database and the PCE database, the above-described approach synchronizes all LSP data in the PCC database to the PCE, and the amount of synchronized data is large.
Disclosure of Invention
Embodiments of the present invention provide a method and an apparatus for synchronizing LSP data, so as to reduce the amount of data that needs to be synchronized between a PCC and a PCE, and enable the PCC to synchronize LSP data to the PCE as soon as possible.
In order to achieve the above object, an embodiment of the present invention provides a method for synchronizing label switched path LSP data, which is applied in a network including a path computation client PCC and a path computation element PCE, and includes the following steps:
the PCC compares the global version number of the PCC database with the global version number of the PCE database;
when the comparison result shows that the global version number of the PCC database is newer than the global version number of the PCE database, the PCC informs the PCE to start synchronizing the LSP data, and the PCE sets the states of all LSP data in the PCE database to be unsynchronized states;
the PCC synchronizes LSP data with a sequence number in the PCC database which is newer than the global version number of the PCE database and the corresponding sequence number to the PCE, and synchronizes sequence number information of other LSP data in the PCC database to the PCE; the PCE updates a PCE database by utilizing the received LSP data and the corresponding serial number, sets the state of the current updated LSP data to be a synchronized state, and adjusts the state of the LSP data corresponding to the serial number information of other LSP data to be the synchronized state;
and the PCC informs the PCE of finishing synchronizing the LSP data, the PCE deletes the LSP data which is in an unsynchronized state currently in the PCE database, and the global version number of the PCE database is updated.
The process of the PCC comparing the global version number of the PCC database with the global version number of the PCE database specifically includes: the PCC periodically acquires the global version number of the PCC database and the global version number of the PCE database, and compares the global version number of the PCC database with the global version number of the PCE database; or when LSP data in the PCC database changes, the PCC updates the global version number of the PCC database, and when the global version number of the PCC database changes, the global version number of the PCE database is obtained, and the global version number of the PCC database is compared with the global version number of the PCE database; wherein the changing of the LSP data in the PCC database includes: and adding new LSP data and corresponding sequence numbers in the PCC database, modifying the LSP data and the corresponding sequence numbers which currently exist in the PCC database, and deleting the LSP data and the corresponding sequence numbers which currently exist in the PCC database.
The step of synchronizing, by the PCC, sequence number information of other LSP data in the PCC database to the PCE specifically includes: and the PCC synchronizes sequence number segments of other LSP data in the PCC database to the PCE.
The embodiment of the invention provides a method for synchronizing Label Switched Path (LSP) data, which is applied to a network comprising a Path Computation Client (PCC) and a Path Computation Element (PCE), and comprises the following steps:
the PCE receives a notice of starting to synchronize the LSP data from the PCC and sets the state of all LSP data in a PCE database to be an unsynchronized state; wherein the notification is sent by the PCC when the global version number of the PCC database is newer than the global version number of the PCE database;
the PCE receives LSP data with a sequence number which is synchronized by the PCC to the PCC database of the PCE and is newer than the global version number of the PCE database and a corresponding sequence number, and receives sequence number information of other LSP data synchronized by the PCC to the PCC database of the PCE;
the PCE updates the PCE database by utilizing the received LSP data and the corresponding serial number, sets the state of the current updated LSP data to be a synchronized state, and adjusts the state of the LSP data corresponding to the serial number information of other LSP data from an unsynchronized state to a synchronized state;
and the PCE receives the notice of finishing synchronizing the LSP data from the PCC, deletes the LSP data in the PCE database which is in an unsynchronized state at present, and updates the global version number of the PCE database.
The process that the PCE receives sequence number information of other LSP data in the PCC database, and adjusts the state of LSP data corresponding to the sequence number information of other LSP data from an unsynchronized state to a synchronized state specifically includes: and the PCE receives the serial number section of other LSP data synchronized by the PCC to the PCC database of the PCE, and adjusts the state of the LSP data of which the serial number is positioned in the serial number section in the PCE database from an unsynchronized state to a synchronized state.
An embodiment of the present invention provides a PCC for a path computation client, where the PCC is applied to a network including the PCC and a path computation element PCE, and the PCC specifically includes:
the comparison module is used for comparing the global version number of the PCC database with the global version number of the PCE database;
a first notification module, configured to notify the PCE of starting synchronizing Label Switched Path (LSP) data when the comparison result indicates that the global version number of the PCC database is newer than the global version number of the PCE database, where the PCE sets states of all LSP data in the PCE database to be an unsynchronized state;
a synchronization module, configured to synchronize, to the PCE, LSP data with a sequence number that is newer than the global version number of the PCE database and a corresponding sequence number, and synchronize sequence number information of other LSP data in the PCC database to the PCE; the PCE updates a PCE database by utilizing the received LSP data and the corresponding serial number, sets the state of the current updated LSP data to be a synchronized state, and adjusts the state of the LSP data corresponding to the serial number information of other LSP data to be the synchronized state;
and the second notification module is used for notifying the PCE of finishing synchronizing the LSP data, deleting the LSP data which is in an unsynchronized state in the PCE database by the PCE, and updating the global version number of the PCE database.
The comparison module is specifically used for periodically acquiring the global version number of the PCC database and the global version number of the PCE database, and comparing the global version number of the PCC database with the global version number of the PCE database; or when LSP data in the PCC database changes, updating the global version number of the PCC database, and when the global version number of the PCC database changes, acquiring the global version number of the PCE database, and comparing the global version number of the PCC database with the global version number of the PCE database;
wherein the changing of the LSP data in the PCC database includes: and adding new LSP data and corresponding sequence numbers in the PCC database, modifying the LSP data and the corresponding sequence numbers which currently exist in the PCC database, and deleting the LSP data and the corresponding sequence numbers which currently exist in the PCC database.
The synchronization module is specifically configured to synchronize sequence number segments of other LSP data in the PCC database to the PCE.
An embodiment of the present invention provides a path computation element PCE, which is applied to a network including a path computation client PCC and the PCE, where the PCE specifically includes:
a receiving module, configured to receive a notification of starting synchronous Label Switched Path (LSP) data from the PCC; wherein the notification is sent by the PCC when the global version number of the PCC database is newer than the global version number of the PCE database; receiving LSP data with a sequence number which is newer than the global version number of the PCE database and is synchronized by the PCC into the PCE database and a corresponding sequence number, and receiving sequence number information of other LSP data synchronized by the PCC into the PCE database; and receiving a notification of ending synchronous LSP data from the PCC;
the processing module is used for setting the states of all LSP data in the PCE database to be unsynchronized states after receiving the notice of starting to synchronize the LSP data; after receiving LSP data with a sequence number which is newer than the global version number of the PCE database and corresponding sequence numbers in the PCC database and sequence number information of other LSP data in the PCC database, updating the PCE database by using the received LSP data and the corresponding sequence numbers, setting the state of the current updated LSP data to be a synchronized state, and adjusting the state of the LSP data corresponding to the sequence number information of the other LSP data from an unsynchronized state to a synchronized state; and deleting the LSP data which is in an unsynchronized state currently in the PCE database after receiving the notice of finishing synchronizing the LSP data, and updating the global version number of the PCE database.
The receiving module is specifically configured to receive a sequence number segment of other LSP data synchronized by the PCC to the PCC database of the PCE;
the processing module is specifically configured to adjust the state of the LSP data in which the serial number in the PCE database is located in the serial number segment from an unsynchronized state to a synchronized state.
Compared with the prior art, the embodiment of the invention at least has the following advantages: in the embodiment of the invention, when the PCC needs to synchronize the LSP data to the PCE, only LSP data with a sequence number which is newer than the global version number of the PCE database and a corresponding sequence number are needed to be synchronized to the PCE, and sequence number sections of other LSP data in the PCC database are synchronized to the PCE, so that the data volume needing to be synchronized between the PCC and the PCE is obviously reduced, the synchronous communication traffic between the PCC and the PCE is reduced, the PCC can synchronize the LSP data to the PCE as soon as possible, and the network overhead and the network bandwidth are saved.
Drawings
Fig. 1 is a flowchart of a method for synchronizing LSP data according to an embodiment of the present invention;
FIGS. 2A and 2B are schematic diagrams of LSP data in a PCC database and LSP data in a PCE database in an embodiment of the present invention;
FIG. 3 is a schematic structural diagram illustrating a tree-shaped sequence number segment storage according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of a PCC provided in an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a PCE according to an embodiment of the present invention.
Detailed Description
To solve the problems in the prior art, an embodiment of the present invention provides a method for synchronizing LSP data, which is applied in a network (e.g., an MPLS network) including a PCC and a PCE, and is used for synchronizing LSP data between the PCC and the PCE, as shown in fig. 1, where the method includes the following steps:
step 101, the PCC compares the global version number of the PCC database with the global version number of the PCE database. The PCE database is used for recording all the received LSP data from the PCC and the corresponding serial numbers, and the PCC needs to synchronize the LSP data in the PCC database to the PCE database of the PCE.
Further, the PCC database corresponds to a global version number, which is usually a serial number corresponding to the latest LSP data in the PCC database; similarly, the PCE database has a global version number corresponding thereto, and the global version number is usually a sequence number corresponding to the latest LSP data in the PCE database.
In the preferred embodiment of the present invention, the process of comparing, by the PCC, the global version number of the PCC database with the global version number of the PCE database specifically includes, but is not limited to, the following processing modes:
and in the first mode, the PCC periodically acquires the global version number of the PCC database and the global version number of the PCE database, and compares the global version number of the PCC database with the global version number of the PCE database.
When LSP data in the PCC database changes, the PCC updates the global version number of the PCC database, and when the global version number of the PCC database changes, the global version number of the PCE database is obtained, and the global version number of the PCC database is compared with the global version number of the PCE database; wherein the changing of the LSP data in the PCC database includes: and adding new LSP data and corresponding sequence numbers in the PCC database, modifying the LSP data and the corresponding sequence numbers which currently exist in the PCC database, and deleting the LSP data and the corresponding sequence numbers which currently exist in the PCC database.
After the last time of LSP data synchronization is completed, the LSP data in the PCC database and the PCE database is as shown in fig. 2A, at this time, the global version number of the PCC database and the PCE database is 6, and the LSP data in the PCC database and the PCE database includes: LSP Data 1 (Key =10, Data = 300), LSP Data 2 (Key =20, Data = 300), LSP Data 3 (Key =30, Data = 300), LSP Data 4 (Key =40, Data = 300), LSP Data 5 (Key =50, Data = 300), LSP Data 6 (Key =60, Data = 300). Further, the sequence number corresponding to LSP data 1 is 1 (SeqNum = 1), the sequence number corresponding to LSP data 2 is 2 (SeqNum = 2), the sequence number corresponding to LSP data 3 is 3 (SeqNum = 3), the sequence number corresponding to LSP data 4 is 4 (SeqNum = 4), the sequence number corresponding to LSP data 5 is 5 (SeqNum = 5), and the sequence number corresponding to LSP data 6 is 6 (SeqNum = 6).
On this basis, if the PCC updates the LSP Data in the PCC database, and the updated LSP Data in the PCC database and the PCE database are as shown in fig. 2B, the PCC deletes LSP Data 2 (Key =20, Data = 300) and corresponding sequence number 2; the PCC modifies LSP Data 3 (Key =30, Data = 300) into LSP Data 7 (Key =30, Data = 400) and modifies the sequence number corresponding to the LSP Data from sequence number 3 (SeqNum = 3) into sequence number 7 (SeqNum = 7); the PCC adds LSP Data 8 (Key =70, Data = 300), and sets the sequence number corresponding to LSP Data 8 to 8 (SeqNum = 8). Further, since the LSP data in the PCC database changes, the PCC needs to update the global version number of the PCC database, and at this time, the global version number of the PCC database is updated to 8.
In the embodiment of the present invention, when the comparison result is that the global version number of the PCC database is the same as the global version number of the PCE database, the PCC does not need to synchronize LSP data to the PCE, and the process is terminated, which is not described in detail again. When the comparison result shows that the global version number of the PCC database is newer than the global version number of the PCE database, as shown in fig. 2B, the global version number of the PCC database is 8, the global version number of the PCE database is 6, and at this time, the global version number of the PCC database is newer than the global version number of the PCE database, and the PCC needs to synchronize LSP data to the PCE, that is, the subsequent step 102 needs to be performed.
Step 102, when the global version number of the PCC database is newer than the global version number of the PCE database, the PCC notifies the PCE of starting synchronizing the LSP data, the PCE receives the notification of starting synchronizing the LSP data from the PCC, and sets the state of all LSP data in the PCE database to be an unsynchronized state. For example, after receiving the notification to start synchronizing the LSP data, the PCE sets the state of LSP data 1 in the PCE database to an unsynchronized state, the state of LSP data 2 to an unsynchronized state, the state of LSP data 3 to an unsynchronized state, the state of LSP data 4 to an unsynchronized state, the state of LSP data 5 to an unsynchronized state, and the state of LSP data 6 to an unsynchronized state.
103, the PCC synchronizes the LSP data with the serial number in the PCC database, which is newer than the global version number of the PCE database, and the corresponding serial number to the PCE, and synchronizes the serial number information of other LSP data in the PCC database to the PCE; and receiving, by the PCE, LSP data with a sequence number newer than the global version number of the PCE database synchronized to the PCE database and a corresponding sequence number by the PCC, and receiving sequence number information of other LSP data synchronized by the PCC to the PCE database.
In the embodiment of the present invention, the synchronizing, by the PCC, the sequence number information of the other LSP data in the PCC database to the PCE specifically includes: the PCC synchronizes the sequence numbers of other LSP data in the PCC database to the PCE directly, and the PCE receives the sequence numbers of other LSP data in the PCC database synchronized by the PCC to the PCE; or, the PCC synchronizes the sequence number segments of other LSP data in the PCC database to the PCE, and the PCE receives the sequence number segments of other LSP data in the PCC database synchronized to the PCE.
As shown in fig. 2B, since the global version number of the PCE database is 6, the serial number 7 and the serial number 8 are newer than the global version number of the PCE database, and thus the PCC needs to synchronize to the PCE the LSP Data 7 (Key =30, Data = 400) and the corresponding serial number 7 and LSP Data 8 (Key =70, Data = 300) and the corresponding serial number 8, which have a newer serial number than the global version number of the PCE database, and receive by the PCE the LSP Data 7 (Key =30, Data = 400) and the corresponding serial number 7 and LSP Data 8 (Key =70, Data = 300) and the corresponding serial number 8, which are synchronized to the PCE by the PCC.
Further, the PCC also needs to synchronize sequence numbers (1, 4, 5, 6) of other LSP data in the PCC database directly to the PCE, and the PCE receives sequence numbers (1, 4, 5, 6) of other LSP data in the PCC database that the PCC synchronizes to the PCE; or, the PCC needs to synchronize the sequence number fields (1-1, 4-6) of other LSP data in the PCC database to the PCE, and the PCE receives the sequence number fields (1-1, 4-6) of other LSP data in the PCC database synchronized to the PCE.
Step 104, the PCE updates the PCE database with the received LSP data and the corresponding sequence number, sets the state of the currently updated LSP data to a synchronized state, and adjusts the state of the LSP data corresponding to the sequence number information of other LSP data from an unsynchronized state to a synchronized state.
As shown in fig. 2B, after receiving LSP Data 7 (Key =30, Data = 400) and the corresponding sequence number 7, the PCE needs to update the PCE database with LSP Data 7 (Key =30, Data = 400) and the corresponding sequence number 7. Specifically, the PCE queries the PCE database through Key =30, and since there is a corresponding record in the PCE database, the PCE determines that it needs to modify LSP Data 3 (Key =30, Data = 300) in the PCE database by using LSP Data 7 (Key =30, Data = 400), modify LSP Data 3 (Key =30, Data = 300) into LSP Data 7 (Key =30, Data = 400), and modify a sequence number corresponding thereto from sequence number 3 (SeqNum = 3) into sequence number 7 (SeqNum = 7).
Further, after receiving LSP Data 8 (Key =70, Data = 300) and the corresponding sequence number 8, the PCE also needs to update the PCE database with LSP Data 8 (Key =70, Data = 300) and the corresponding sequence number 8. Specifically, the PCE queries the PCE database through Key =70, and since there is no corresponding record in the PCE database, the PCE determines that LSP Data 8 (Key =70, Data = 300) and a corresponding sequence number 8 need to be added to the PCE database, and adds the same to the PCE database.
Further, the PCE needs to set the state of the LSP Data 7 to the synchronized state and the state of the LSP Data 8 to the synchronized state after adding the LSP Data 7 (Key =30, Data = 400) and LSP Data 8 (Key =70, Data = 300) to the PCE database.
In the embodiment of the present invention, the PCE further needs to adjust the state of the LSP data corresponding to the sequence number information of the other LSP data from an unsynchronized state to a synchronized state. When the PCE receives the serial number field of other LSP data synchronized by the PCC in the PCE PCC database, the state of the LSP data of which the serial number is positioned in the serial number field in the PCE database needs to be adjusted from an unsynchronized state to a synchronized state. For example, after receiving the sequence numbers (1, 4, 5, 6) or the sequence number segments (1-1, 4-6) of other LSP data in the PCC database, the PCE adjusts the state of LSP data 1 corresponding to sequence number 1 from the unsynchronized state to the synchronized state, adjusts the state of LSP data 4 corresponding to sequence number 4 from the unsynchronized state to the synchronized state, adjusts the state of LSP data 5 corresponding to sequence number 5 from the unsynchronized state to the synchronized state, and adjusts the state of LSP data 6 corresponding to sequence number 6 from the unsynchronized state to the synchronized state.
Based on the above processing, the PCE database contains LSP data 1 (serial number 1), LSP data 2 (serial number 2), LSP data 4 (serial number 4), LSP data 5 (serial number 5), LSP data 6 (serial number 6), LSP data 7 (serial number 7), and LSP data 8 (serial number 8); the state of the LSP data 1 is a synchronized state, the state of the LSP data 2 is an unsynchronized state, the state of the LSP data 4 is a synchronized state, the state of the LSP data 5 is a synchronized state, the state of the LSP data 6 is a synchronized state, the state of the LSP data 7 is a synchronized state, and the state of the LSP data 8 is a synchronized state.
Step 105, the PCC informs the PCE of the end of the synchronized LSP data, the PCE receives the notification of the end of the synchronized LSP data from the PCC, deletes the LSP data in the PCE database whose current state is an unsynchronized state, and updates the global version number of the PCE database. For example, after receiving the notification of ending the synchronization of the LSP Data, the PCE deletes LSP Data 2 in the PCE database because the state of LSP Data 2 (Key =20, Data = 300) is an unsynchronized state; because the sequence number corresponding to the latest LSP data in the PCE database is 8, the PCE updates the global version number of the PCE database to 8.
In summary, in the embodiment of the present invention, when the PCC needs to synchronize LSP data to the PCE, only LSP data with a sequence number that is newer than the global version number of the PCE database and corresponding sequence numbers (LSP data 7 and sequence number 7, LSP data 8, and sequence number 8) in the PCC database need to be synchronized to the PCE, and sequence number segments (1-1, 4-6) of other LSP data in the PCC database need to be synchronized to the PCE, so that the amount of data that needs to be synchronized between the PCC and the PCE is significantly reduced, and the amount of traffic synchronized between the PCC and the PCE is reduced, so that the PCC can synchronize LSP data to the PCE as soon as possible.
The effect of the embodiment of the present invention will be further described with reference to the structure of fig. 3 for storing serial number segments in a tree form. Suppose that the LSP data in the PCC database corresponds to fig. 3, the global version number of the PCC database is 446, and the PCC database includes LSP data corresponding to sequence numbers 1-30, LSP data corresponding to 55-67, LSP data corresponding to 80-93, LSP data corresponding to 100-104, and LSP data corresponding to 115-446; assume that the global version number of the PCE database is 440.
Based on this, in the embodiment of the present invention, the contents of synchronization from the PCC to the PCE are as follows:
(1) the LSP data with serial numbers 441, 442, 443, 444, 445, 446 and the corresponding serial numbers are all notified in this context, both in the embodiments of the present invention and in the prior art.
(2) Sequence number segments (115-440), (100-104), (80-93), (55-67), (1-30) consuming a number of bytes: 8 × 2 × 5=80 bytes; in the prior art, assuming that the size of each LSP data is 64 bytes, the number of consumed bytes is: 64 × ((440-; it is apparent that embodiments of the present invention significantly reduce the amount of data that needs to be synchronized between a PCC and a PCE as compared to the prior art.
Based on the same inventive concept as the above method, an embodiment of the present invention further provides a path computation client PCC, which is applied to a network including the PCC and a path computation element PCE, as shown in fig. 4, where the PCC specifically includes:
a comparison module 11, configured to compare the global version number of the PCC database with the global version number of the PCE database;
a first notification module 12, configured to notify the PCE to start synchronizing label switched path LSP data when the comparison result indicates that the global version number of the PCC database is newer than the global version number of the PCE database, where the PCE sets states of all LSP data in the PCE database to be an unsynchronized state;
a synchronization module 13, configured to synchronize, to the PCE, LSP data with a sequence number that is newer than the global version number of the PCE database and a corresponding sequence number, and synchronize sequence number information of other LSP data in the PCC database to the PCE; the PCE updates a PCE database by utilizing the received LSP data and the corresponding serial number, sets the state of the current updated LSP data to be a synchronized state, and adjusts the state of the LSP data corresponding to the serial number information of other LSP data to be the synchronized state;
and a second notification module 14, configured to notify the PCE to finish synchronizing the LSP data, where the PCE deletes LSP data in the PCE database that is currently in an unsynchronized state, and updates a global version number of the PCE database.
The comparison module 11 is specifically configured to periodically obtain a global version number of the PCC database and a global version number of the PCE database, and compare the global version number of the PCC database with the global version number of the PCE database; or when LSP data in the PCC database changes, updating the global version number of the PCC database, and when the global version number of the PCC database changes, acquiring the global version number of the PCE database, and comparing the global version number of the PCC database with the global version number of the PCE database;
wherein the changing of the LSP data in the PCC database includes: and adding new LSP data and corresponding sequence numbers in the PCC database, modifying the LSP data and the corresponding sequence numbers which currently exist in the PCC database, and deleting the LSP data and the corresponding sequence numbers which currently exist in the PCC database.
The synchronization module 13 is specifically configured to synchronize sequence number segments of other LSP data in the PCC database to the PCE.
The modules of the device can be integrated into a whole or can be separately deployed. The modules can be combined into one module, and can also be further split into a plurality of sub-modules.
Based on the same inventive concept as the above method, an embodiment of the present invention further provides a path computation element PCE, which is applied to a network including a path computation client PCC and the PCE, as shown in fig. 5, where the PCE specifically includes:
a receiving module 21, configured to receive a notification of starting synchronous label switched path LSP data from the PCC; wherein the notification is sent by the PCC when the global version number of the PCC database is newer than the global version number of the PCE database; receiving LSP data with a sequence number which is newer than the global version number of the PCE database and is synchronized by the PCC into the PCE database and a corresponding sequence number, and receiving sequence number information of other LSP data synchronized by the PCC into the PCE database; and receiving a notification of ending synchronous LSP data from the PCC;
a processing module 22, configured to set the states of all LSP data in the PCE database to an unsynchronized state after receiving the notification of starting to synchronize LSP data; after receiving LSP data with a sequence number which is newer than the global version number of the PCE database and corresponding sequence numbers in the PCC database and sequence number information of other LSP data in the PCC database, updating the PCE database by using the received LSP data and the corresponding sequence numbers, setting the state of the current updated LSP data to be a synchronized state, and adjusting the state of the LSP data corresponding to the sequence number information of the other LSP data from an unsynchronized state to a synchronized state; and deleting the LSP data which is in an unsynchronized state currently in the PCE database after receiving the notice of finishing synchronizing the LSP data, and updating the global version number of the PCE database.
The receiving module 21 is specifically configured to receive a sequence number segment of other LSP data in the PCC database synchronized by the PCC to the PCE;
the processing module 22 is specifically configured to adjust the state of the LSP data in which the serial number in the PCE database is located in the serial number segment from an unsynchronized state to a synchronized state.
The modules of the device can be integrated into a whole or can be separately deployed. The modules can be combined into one module, and can also be further split into a plurality of sub-modules.
Through the above description of the embodiments, those skilled in the art will clearly understand that the present invention may be implemented by software plus a necessary general hardware platform, and certainly may also be implemented by hardware, but in many cases, the former is a better embodiment. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute the methods according to the embodiments of the present invention.
Those skilled in the art will appreciate that the drawings are merely schematic representations of one preferred embodiment and that the blocks or flow diagrams in the drawings are not necessarily required to practice the present invention.
Those skilled in the art will appreciate that the modules in the devices in the embodiments may be distributed in the devices in the embodiments according to the description of the embodiments, and may be correspondingly changed in one or more devices different from the embodiments. The modules of the above embodiments may be combined into one module, or further split into multiple sub-modules.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
The above disclosure is only for a few specific embodiments of the present invention, but the present invention is not limited thereto, and any variations that can be made by those skilled in the art are intended to fall within the scope of the present invention.
Claims (10)
1. A method for synchronizing label switched path, LSP, data, for use in a network comprising a path computation client, PCC, and a path computation element, PCE, characterized in that the method comprises the steps of:
the PCC compares the global version number of the PCC database with the global version number of the PCE database;
when the comparison result shows that the global version number of the PCC database is newer than the global version number of the PCE database, the PCC informs the PCE to start synchronizing the LSP data, and the PCE sets the states of all LSP data in the PCE database to be unsynchronized states;
the PCC synchronizes LSP data with a sequence number in the PCC database which is newer than the global version number of the PCE database and the corresponding sequence number to the PCE, and synchronizes sequence number information of other LSP data in the PCC database to the PCE; the PCE updates a PCE database by utilizing the received LSP data and the corresponding serial number, sets the state of the current updated LSP data to be a synchronized state, and adjusts the state of the LSP data corresponding to the serial number information of other LSP data to be the synchronized state;
and the PCC informs the PCE of finishing synchronizing the LSP data, the PCE deletes the LSP data which is in an unsynchronized state currently in the PCE database, and the global version number of the PCE database is updated.
2. The method of claim 1, wherein the process of the PCC comparing the global version number of the PCC database to the global version number of the PCE database specifically comprises:
the PCC periodically acquires the global version number of the PCC database and the global version number of the PCE database, and compares the global version number of the PCC database with the global version number of the PCE database; or,
when LSP data in the PCC database changes, the PCC updates the global version number of the PCC database, and when the global version number of the PCC database changes, the global version number of the PCE database is obtained, and the global version number of the PCC database is compared with the global version number of the PCE database;
wherein the changing of the LSP data in the PCC database includes: and adding new LSP data and corresponding sequence numbers in the PCC database, modifying the LSP data and the corresponding sequence numbers which currently exist in the PCC database, and deleting the LSP data and the corresponding sequence numbers which currently exist in the PCC database.
3. The method of claim 1, wherein the synchronizing, by the PCC to the PCE, sequence number information for other LSP data within the PCC database specifically comprises:
and the PCC synchronizes sequence number segments of other LSP data in the PCC database to the PCE.
4. A method for synchronizing label switched path, LSP, data, for use in a network comprising a path computation client, PCC, and a path computation element, PCE, characterized in that the method comprises the steps of:
the PCE receives a notice of starting to synchronize the LSP data from the PCC and sets the state of all LSP data in a PCE database to be an unsynchronized state; wherein the notification is sent by the PCC when the global version number of the PCC database is newer than the global version number of the PCE database;
the PCE receives LSP data with a sequence number which is synchronized by the PCC to the PCC database of the PCE and is newer than the global version number of the PCE database and a corresponding sequence number, and receives sequence number information of other LSP data synchronized by the PCC to the PCC database of the PCE;
the PCE updates the PCE database by utilizing the received LSP data and the corresponding serial number, sets the state of the current updated LSP data to be a synchronized state, and adjusts the state of the LSP data corresponding to the serial number information of other LSP data from an unsynchronized state to a synchronized state;
and the PCE receives the notice of finishing synchronizing the LSP data from the PCC, deletes the LSP data in the PCE database which is in an unsynchronized state at present, and updates the global version number of the PCE database.
5. The method of claim 4, wherein the PCE receives sequence number information of other LSP data in the PCC database, and adjusts the state of LSP data corresponding to the sequence number information of other LSP data from an unsynchronized state to a synchronized state, specifically comprising:
and the PCE receives the serial number section of other LSP data synchronized by the PCC to the PCC database of the PCE, and adjusts the state of the LSP data of which the serial number is positioned in the serial number section in the PCE database from an unsynchronized state to a synchronized state.
6. A path computation client PCC, applied to a network comprising the PCC and a path computation element, PCE, wherein the PCC specifically comprises:
the comparison module is used for comparing the global version number of the PCC database with the global version number of the PCE database;
a first notification module, configured to notify the PCE of starting synchronizing Label Switched Path (LSP) data when the comparison result indicates that the global version number of the PCC database is newer than the global version number of the PCE database, where the PCE sets states of all LSP data in the PCE database to be an unsynchronized state;
a synchronization module, configured to synchronize, to the PCE, LSP data with a sequence number that is newer than the global version number of the PCE database and a corresponding sequence number, and synchronize sequence number information of other LSP data in the PCC database to the PCE; the PCE updates a PCE database by utilizing the received LSP data and the corresponding serial number, sets the state of the current updated LSP data to be a synchronized state, and adjusts the state of the LSP data corresponding to the serial number information of other LSP data to be the synchronized state;
and the second notification module is used for notifying the PCE of finishing synchronizing the LSP data, deleting the LSP data which is in an unsynchronized state in the PCE database by the PCE, and updating the global version number of the PCE database.
7. The PCC according to claim 6,
the comparison module is specifically used for periodically acquiring the global version number of the PCC database and the global version number of the PCE database, and comparing the global version number of the PCC database with the global version number of the PCE database; or when LSP data in the PCC database changes, updating the global version number of the PCC database, and when the global version number of the PCC database changes, acquiring the global version number of the PCE database, and comparing the global version number of the PCC database with the global version number of the PCE database;
wherein the changing of the LSP data in the PCC database includes: and adding new LSP data and corresponding sequence numbers in the PCC database, modifying the LSP data and the corresponding sequence numbers which currently exist in the PCC database, and deleting the LSP data and the corresponding sequence numbers which currently exist in the PCC database.
8. The PCC according to claim 6,
the synchronization module is specifically configured to synchronize sequence number segments of other LSP data in the PCC database to the PCE.
9. A Path Computation Element (PCE) is applied to a network comprising a Path Computation Client (PCC) and the PCE, and is characterized in that the PCE specifically comprises:
a receiving module, configured to receive a notification of starting synchronous Label Switched Path (LSP) data from the PCC; wherein the notification is sent by the PCC when the global version number of the PCC database is newer than the global version number of the PCE database; receiving LSP data with a sequence number which is newer than the global version number of the PCE database and is synchronized by the PCC into the PCE database and a corresponding sequence number, and receiving sequence number information of other LSP data synchronized by the PCC into the PCE database; and receiving a notification of ending synchronous LSP data from the PCC;
the processing module is used for setting the states of all LSP data in the PCE database to be unsynchronized states after receiving the notice of starting to synchronize the LSP data; after receiving LSP data with a sequence number which is newer than the global version number of the PCE database and corresponding sequence numbers in the PCC database and sequence number information of other LSP data in the PCC database, updating the PCE database by using the received LSP data and the corresponding sequence numbers, setting the state of the current updated LSP data to be a synchronized state, and adjusting the state of the LSP data corresponding to the sequence number information of the other LSP data from an unsynchronized state to a synchronized state; and deleting the LSP data which is in an unsynchronized state currently in the PCE database after receiving the notice of finishing synchronizing the LSP data, and updating the global version number of the PCE database.
10. The PCE of claim 9, wherein,
the receiving module is specifically configured to receive a sequence number segment of other LSP data synchronized by the PCC to the PCC database of the PCE;
the processing module is specifically configured to adjust the state of the LSP data in which the serial number in the PCE database is located in the serial number segment from an unsynchronized state to a synchronized state.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310428476.0A CN103475582B (en) | 2013-09-18 | 2013-09-18 | The synchronous method of a kind of LSP data and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310428476.0A CN103475582B (en) | 2013-09-18 | 2013-09-18 | The synchronous method of a kind of LSP data and equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103475582A CN103475582A (en) | 2013-12-25 |
| CN103475582B true CN103475582B (en) | 2016-08-31 |
Family
ID=49800288
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310428476.0A Active CN103475582B (en) | 2013-09-18 | 2013-09-18 | The synchronous method of a kind of LSP data and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103475582B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110245149A (en) * | 2019-06-25 | 2019-09-17 | 北京明略软件系统有限公司 | The method for edition management and device of metadata |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105634951B (en) * | 2014-11-05 | 2020-08-04 | 南京中兴软件有限责任公司 | Method and device for recovering Graceful Restart (GR) of label switched path L SP |
| WO2017190573A1 (en) * | 2016-05-03 | 2017-11-09 | Huawei Technologies Co., Ltd. | Label database synchronization in a packet switched communication network |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101170457A (en) * | 2007-11-22 | 2008-04-30 | 中兴通讯股份有限公司 | A method and device for detecting label configuration confliction in router system |
| CN101834855A (en) * | 2010-04-14 | 2010-09-15 | 杭州华三通信技术有限公司 | Method and equipment for preventing serial number from being attacked |
| CN102647473A (en) * | 2012-04-11 | 2012-08-22 | 北京星网锐捷网络技术有限公司 | Information synchronization method, device and communication equipment |
-
2013
- 2013-09-18 CN CN201310428476.0A patent/CN103475582B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101170457A (en) * | 2007-11-22 | 2008-04-30 | 中兴通讯股份有限公司 | A method and device for detecting label configuration confliction in router system |
| CN101834855A (en) * | 2010-04-14 | 2010-09-15 | 杭州华三通信技术有限公司 | Method and equipment for preventing serial number from being attacked |
| CN102647473A (en) * | 2012-04-11 | 2012-08-22 | 北京星网锐捷网络技术有限公司 | Information synchronization method, device and communication equipment |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110245149A (en) * | 2019-06-25 | 2019-09-17 | 北京明略软件系统有限公司 | The method for edition management and device of metadata |
| CN110245149B (en) * | 2019-06-25 | 2021-09-17 | 北京明略软件系统有限公司 | Metadata version management method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103475582A (en) | 2013-12-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9270395B2 (en) | Method for robust PTP synchronization with default 1588V2 profile | |
| CN106815276B (en) | Page skipping method and device | |
| CN102036361B (en) | Processing method, device and system for clock source selection | |
| EP3440807B1 (en) | Label database synchronization in a packet switched communication network | |
| EP3125501A1 (en) | File synchronization method, server, and terminal | |
| CN103731452A (en) | File synchronization system and method | |
| CN103475582B (en) | The synchronous method of a kind of LSP data and equipment | |
| WO2017162079A1 (en) | Data synchronization method and apparatus | |
| CN104796445A (en) | Resource synchronization method and device by server nodes | |
| CN109672712A (en) | Method of data synchronization, device, super controller, domain controller and storage medium | |
| CN108075914B (en) | Dynamic capacity expansion and reduction method and network equipment | |
| CN103312489A (en) | Method and device for synchronizing terminal and server | |
| WO2017166773A1 (en) | Terminal information synchronization method and apparatus, information synchronization system, and electronic device | |
| CN105007310A (en) | Information synchronization method, device and system | |
| US9743371B2 (en) | Control apparatus, communication system, synchronization method and program | |
| CN102170398B (en) | The reverse method of external time port and device | |
| CN106941450B (en) | Route synchronization method, equipment and communication system | |
| CN103685191A (en) | Data synchronizing system and method | |
| CN103117883B (en) | A kind of packet equipment running status synchronous method | |
| CN105162843B (en) | A kind of rapid data synchronous method based on Dynamic Programming | |
| CN110768811A (en) | Method, device and system for updating YANG model file library | |
| CN105119675B (en) | A kind of synchronous method and synchronization system of target device | |
| CN108462548B (en) | Time synchronization method and device | |
| CN102378161A (en) | User equipment and method for determining TA (Timing Advance) value by using same | |
| US11368406B2 (en) | Methods and apparatus for path computation in a telecommunications network |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CP03 | Change of name, title or address |
Address after: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Patentee after: Xinhua three Technology Co., Ltd. Address before: 310053 Hangzhou hi tech Industrial Development Zone, Zhejiang province science and Technology Industrial Park, No. 310 and No. six road, HUAWEI, Hangzhou production base Patentee before: Huasan Communication Technology Co., Ltd. |
|
| CP03 | Change of name, title or address |