Method and system for updating network topology in multi-protocol label switching system
Abstract
A method for updating a network topology in a multi-protocol label switching system includes that network management system obtains network topology data from a node, then judges whether the current network topology is changed, and when changed, update the local network topology data with the network topology data. A corresponding system is also provided, including an obtaining unit to obtain network topology data from a node, a judgment unit to judge whether the current network topology is changed according to the network topology data and to trigger the update unit when it is changed, and a update unit to update the network topology data in the network management system with the network topology data. In the disclosure, the reality of the Multi-Protocol Label Switching Transport Profile (MPLS-TP) network topology is greatly improved, and it is more convenient and accurate when the network management system is utilized to perform network management.
Claims
exact text as granted — not AI-modified1 . A method for updating a network topology in a multi-protocol label switching system, comprising:
a network management system obtaining network topology data from a node, then judging whether the current network topology is changed, and updating local network topology data with the network topology data when the current network topology is changed.
2 . The method according to claim 1 , wherein the network management system obtaining the network topology data from the node comprises:
the node, when determining that the network topology is changed, sending its own current network topology data to the network management system.
3 . The method according to claim 2 , wherein the change of the network topology comprises:
a new node accessing the network, or decreasing of a number of nodes in the network; or increasing or deleting of a connection in the network, or changing of routing information; or changing of type or state of a protected link in the network.
4 . The method according to claim 1 , wherein the network management system obtaining the network topology data from the node comprises:
the network management system sending a query request for the network topology data to the node, and the node reporting its own current network topology data in response to the query request.
5 . The method according to claim 2 , wherein the network topology data comprises at least one of the following data: local node identification (ID), local node address, local label switching router (LSR) ID, local LSR address, service layer connection point ID corresponding to the local node, neighbor node ID, neighbor node address, neighbor LSR ID, neighbor LSR address, and service layer connection point ID corresponding to the neighbor node; or
the network topology data comprises at least one of the following data: label switching path (LSP) ID, local LSR ID, neighbor LSR ID, and label; or the network topology data comprises at least one of the following data: protected group ID, working LSP ID, protected LSP ID, neighbor LSR ID in the protected group, protection type, and current protection condition.
6 . The method according to claim 2 , wherein the network topology data comprises at least one of the following data: local node ID, local node address, local provider edge (PE) router ID, local PE router address, service layer connection point ID corresponding to the local node, neighbor node ID, neighbor node address, neighbor PE router ID, neighbor PE router address, and service layer connection point ID corresponding to the neighbor node; or
the network topology data comprises at least one of the following data: pseudowire (PW) ID, local PE ID, and neighbor PE ID.
7 . A system for updating a network topology in a multi-protocol label switching system, comprising an obtaining unit, a judgment unit and an update unit, wherein
the obtaining unit is configured to obtain network topology data from a node; the judgment unit is configured to judge whether the current network topology is changed, and to trigger the update unit when the current network topology is changed; and the update unit is configured to update local network topology data in the network management system with the network topology data.
8 . The system according to claim 7 , further comprising a determination unit and a first sending unit; wherein
the determination unit is configured to determine whether the network topology is changed, and to trigger the first sending unit when the network topology is changed; and the first sending unit is configured to send the current network topology data of the node to the obtaining unit.
9 . The system according to claim 8 , wherein the change of the network topology includes:
a new node accessing the network or decreasing of a number of nodes in the network; or increasing or deleting of a connection in the network, or changing of routing information; or changing of type or state of a protected link in the network.
10 . The system according to claim 7 , further comprising a second sending unit and a reporting unit, wherein
the second sending unit is configured to send a query request for the network topology data to the node; the reporting unit is configured to report the current network topology data of the node in response to the query request.
11 . The system according to claim 8 , wherein the network topology data comprises at least one of the following data: local node identification (ID), local node address, local Label Switch Router (LSR) ID, local LSR address, service layer connection point ID corresponding to the local node, neighbor node ID, neighbor node address, neighbor LSR ID, neighbor LSR address, and service layer connection point ID corresponding to the neighbor node; or
the network topology data comprises at least one of the following data: label switching path (LSP) ID, local LSR ID, neighbor LSR ID, and label; or the network topology data comprises at least one of the following data: protected group ID, working LSP ID, protected LSP ID, neighbor LSR ID in the protected group, protection type, and current protection condition.
12 . The system according to claim 8 , wherein the network topology data comprises at least one of the following data: local node ID, local node address, local provider edge (PE) router ID, local PE router address, service layer connection point ID corresponding to the local node, neighbor node ID, neighbor node address, neighbor PE router ID, neighbor PE router address, and service layer connection point ID corresponding to the neighbor node; or
the network topology data comprises at least one of the following data: pseudowire (PW) ID, local PE ID, and neighbor PE ID.
13 . The method according to claim 3 , wherein the network topology data comprises at least one of the following data: local node identification (ID), local node address, local label switching router (LSR) ID, local LSR address, service layer connection point ID corresponding to the local node, neighbor node ID, neighbor node address, neighbor LSR ID, neighbor LSR address, and service layer connection point ID corresponding to the neighbor node; or
the network topology data comprises at least one of the following data: label switching path (LSP) ID, local LSR ID, neighbor LSR ID, and label; or the network topology data comprises at least one of the following data: protected group ID, working LSP ID, protected LSP ID, neighbor LSR ID in the protected group, protection type, and current protection condition.
14 . The method according to claim 4 , wherein the network topology data comprises at least one of the following data: local node identification (ID), local node address, local label switching router (LSR) ID, local LSR address, service layer connection point ID corresponding to the local node, neighbor node ID, neighbor node address, neighbor LSR ID, neighbor LSR address, and service layer connection point ID corresponding to the neighbor node; or
the network topology data comprises at least one of the following data: label switching path (LSP) ID, local LSR ID, neighbor LSR ID, and label; or the network topology data comprises at least one of the following data: protected group ID, working LSP ID, protected LSP ID, neighbor LSR ID in the protected group, protection type, and current protection condition.
15 . The method according to claim 3 , wherein the network topology data comprises at least one of the following data: local node ID, local node address, local provider edge (PE) router ID, local PE router address, service layer connection point ID corresponding to the local node, neighbor node ID, neighbor node address, neighbor PE router ID, neighbor PE router address, and service layer connection point ID corresponding to the neighbor node; or
the network topology data comprises at least one of the following data: pseudowire (PW) ID, local PE ID, and neighbor PE ID.
16 . The method according to claim 4 , wherein the network topology data comprises at least one of the following data: local node ID, local node address, local provider edge (PE) router ID, local PE router address, service layer connection point ID corresponding to the local node, neighbor node ID, neighbor node address, neighbor PE router ID, neighbor PE router address, and service layer connection point ID corresponding to the neighbor node; or
the network topology data comprises at least one of the following data: pseudowire (PW) ID, local PE ID, and neighbor PE ID.
17 . The system according to claim 9 , wherein the network topology data comprises at least one of the following data: local node identification (ID), local node address, local Label Switch Router (LSR) ID, local LSR address, service layer connection point ID corresponding to the local node, neighbor node ID, neighbor node address, neighbor LSR ID, neighbor LSR address, and service layer connection point ID corresponding to the neighbor node; or
the network topology data comprises at least one of the following data: label switching path (LSP) ID, local LSR ID, neighbor LSR ID, and label; or the network topology data comprises at least one of the following data: protected group ID, working LSP ID, protected LSP ID, neighbor LSR ID in the protected group, protection type, and current protection condition.
18 . The system according to claim 10 , wherein the network topology data comprises at least one of the following data: local node identification (ID), local node address, local Label Switch Router (LSR) ID, local LSR address, service layer connection point ID corresponding to the local node, neighbor node ID, neighbor node address, neighbor LSR ID, neighbor LSR address, and service layer connection point ID corresponding to the neighbor node; or
the network topology data comprises at least one of the following data: label switching path (LSP) ID, local LSR ID, neighbor LSR ID, and label; or the network topology data comprises at least one of the following data: protected group ID, working LSP ID, protected LSP ID, neighbor LSR ID in the protected group, protection type, and current protection condition.
19 . The system according to claim 9 , wherein the network topology data comprises at least one of the following data: local node ID, local node address, local provider edge (PE) router ID, local PE router address, service layer connection point ID corresponding to the local node, neighbor node ID, neighbor node address, neighbor PE router ID, neighbor PE router address, and service layer connection point ID corresponding to the neighbor node; or
the network topology data comprises at least one of the following data: pseudowire (PW) ID, local PE ID, and neighbor PE ID.
20 . The system according to claim 10 , wherein the network topology data comprises at least one of the following data: local node ID, local node address, local provider edge (PE) router ID, local PE router address, service layer connection point ID corresponding to the local node, neighbor node ID, neighbor node address, neighbor PE router ID, neighbor PE router address, and service layer connection point ID corresponding to the neighbor node; or
the network topology data comprises at least one of the following data: pseudowire (PW) ID, local PE ID, and neighbor PE ID.Join the waitlist — get patent alerts
Track US2012300783A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.