CN116886606A - Link management method and device - Google Patents
Link management method and device Download PDFInfo
- Publication number
- CN116886606A CN116886606A CN202310755525.5A CN202310755525A CN116886606A CN 116886606 A CN116886606 A CN 116886606A CN 202310755525 A CN202310755525 A CN 202310755525A CN 116886606 A CN116886606 A CN 116886606A
- Authority
- CN
- China
- Prior art keywords
- link
- target
- message
- target link
- interface
- 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.)
- Pending
Links
- 238000007726 management method Methods 0.000 title abstract description 20
- 238000000034 method Methods 0.000 claims abstract description 30
- 230000032683 aging Effects 0.000 claims description 14
- 239000000872 buffer Substances 0.000 claims description 13
- 238000012217 deletion Methods 0.000 claims description 4
- 230000037430 deletion Effects 0.000 claims description 4
- 230000003139 buffering effect Effects 0.000 claims description 2
- 238000005516 engineering process Methods 0.000 abstract description 3
- 238000010586 diagram Methods 0.000 description 11
- 238000012545 processing Methods 0.000 description 11
- 238000004590 computer program Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 6
- 230000006855 networking Effects 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 230000007246 mechanism Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 239000002071 nanotube Substances 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 239000004744 fabric Substances 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/76—Routing in software-defined topologies, e.g. routing between virtual machines
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/34—Source routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/74—Address processing for routing
Abstract
The present application relates to the field of network communications technologies, and in particular, to a link management method and device. The method comprises the following steps: if BGP-LS information for adding a target link sent by network equipment is received, judging whether information of a target interface corresponding to the target link is maintained in an interface database; if the interface database is judged to not maintain the information of the target interface corresponding to the target link, caching the target link into a link discovery list; and if the NETCONF message of adding the target interface, which is sent by the network equipment, is received, adding the target link to a link list.
Description
Technical Field
The present application relates to the field of network communications technologies, and in particular, to a link management method and device.
Background
SDN (Software Defined Network, software defined networking) technology is currently widely used in various fields and various user actual networks, where BGP-LS (Border Gateway Protocol-Link State) protocol is generally used in a wide area network bearer SR (Segment Routing) solution to collect network topology data, including collection of information about devices, links, labels, tunnel states, tunnel paths, and so on.
And establishing BGP-LS connection between PE devices, and simultaneously establishing BGP-LS connection between part of devices and RR devices. The controller establishes a BGP-LS connection with the RR device. When the topology of the networking changes, the RR equipment reports information to the controller. The controller processes the corresponding service according to the received message.
When the controller receives the BGP-LS message of adding or deleting the link, adding or deleting the link in the controller. However, when the interface is added immediately after the interface is deleted on the device, since the interface is changed in a NETCONF (XML-based network configuration) subscription mode, the link reported by the NETCONF and the BGP-LS message is not a set of mechanism, and the problem of time sequence exists, the link discovered by the BGP-LS is deleted due to probability, so that the link data is lost, and the service is influenced. This problem easily arises in the context of network slicing.
Disclosure of Invention
The application provides a link management method and device.
In a first aspect, the present application provides a link management method, applied to a controller, the method comprising:
if BGP-LS information for adding a target link sent by network equipment is received, judging whether information of a target interface corresponding to the target link is maintained in an interface database;
if the interface database is judged to not maintain the information of the target interface corresponding to the target link, caching the target link into a link discovery list;
and if the NETCONF message of adding the target interface, which is sent by the network equipment, is received, adding the target link to a link list.
Optionally, before receiving the BGP-LS message sent by the network device and added to the target link, the method further includes:
and if the BGP-LS message for deleting the target link or the NETCONF message of the target interface corresponding to the target link, which is sent by the network equipment, is received, the target link is cached to a link discovery list, and the target link is deleted from the link list.
Optionally, the method further comprises:
and if the NETCONF message of deleting the target interface corresponding to the target link or the BGP-LS message of deleting the target link, which is sent by the network equipment, is received, deleting the target link from the link discovery list.
Optionally, if it is determined that the information of the target interface corresponding to the target link is maintained in the interface database, the target link is added to the link list.
Optionally, setting an aging time of the target link when caching the target link to a link discovery list; and if the NETCONF message added with the target interface corresponding to the target link is not received within the aging time, deleting the target link from the link discovery list.
In a second aspect, the present application provides a link management apparatus for use in a controller, the apparatus comprising:
a receiving unit, configured to receive a BGP-LS message sent by a network device and added to a target link;
the judging unit is used for judging whether the information of the target interface corresponding to the target link is maintained in the interface database;
the buffer unit is used for buffering the target link to a link discovery list if the judging unit judges that the information of the target interface corresponding to the target link is not maintained in the interface database;
and the adding unit is used for adding the target link to a link list if the receiving unit receives the NETCONF message of adding the target interface sent by the network equipment.
Optionally, the apparatus further comprises a deletion unit; the receiving unit receives the BGP-LS message sent by the network device and adding the target link,
and if the receiving unit receives the BGP-LS message for deleting the target link or the netcon f message for deleting the target interface corresponding to the target link, which is sent by the network device, the caching unit is configured to cache the target link to a link discovery list, and the deleting unit is configured to delete the target link from the link list.
Optionally, if the receiving unit receives a netcon f message sent by the network device to delete a target interface corresponding to the target link, or deletes a BGP-LS message of the target link, the deleting unit is configured to delete the target link from the link discovery list.
Optionally, if the judging unit judges that the information of the target interface corresponding to the target link is maintained in the interface database, the adding unit is configured to add the target link to the link list.
Optionally, when the buffer unit is configured to buffer the target link to a link discovery list, the buffer unit is further configured to set an aging time of the target link; and if the NETCONF message of the target interface corresponding to the target link is not received in the aging time, the deleting unit is used for deleting the target link from the link discovery list.
In a third aspect, an embodiment of the present application provides a link management apparatus, including:
a memory for storing program instructions;
a processor for invoking program instructions stored in said memory, performing the steps of the method according to any of the first aspects above in accordance with the obtained program instructions.
In a fourth aspect, embodiments of the present application also provide a computer-readable storage medium storing computer-executable instructions for causing a computer to perform the steps of the method according to any one of the first aspects.
As can be seen from the foregoing, the link management method provided by the embodiment of the present application is applied to a controller, and the method includes: if BGP-LS information for adding a target link sent by network equipment is received, judging whether information of a target interface corresponding to the target link is maintained in an interface database; if the interface database is judged to not maintain the information of the target interface corresponding to the target link, caching the target link into a link discovery list; and if the NETCONF message of adding the target interface, which is sent by the network equipment, is received, adding the target link to a link list.
By adopting the link management method provided by the embodiment of the application, the link information in the temporary non-effective state is cached through the newly added link discovery list, the link is discovered when the existence of the interface information in the interface database is determined, and the link is set in the effective state, so that the problem that the controller is scheduled under the condition that the interfaces are frequently added and deleted is avoided, the controller can be ensured to normally manage the link, and the problem is prevented from being caused under the condition that the link is not discovered.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following description will briefly describe the drawings required to be used in the embodiments of the present application or the description in the prior art, and it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings may be obtained according to these drawings of the embodiments of the present application for a person having ordinary skill in the art.
FIG. 1 is a schematic diagram of a controller nanotube fabric;
fig. 2 is a detailed flowchart of a link management method according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of a link management device according to an embodiment of the present application;
fig. 4 is a schematic hardware architecture of a link management device according to an embodiment of the present application.
Detailed Description
The terminology used in the embodiments of the application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to any or all possible combinations including one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used in embodiments of the present application to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the application. Depending on the context, furthermore, the word "if" used may be interpreted as "at … …" or "at … …" or "in response to a determination".
Referring now to fig. 1, a schematic diagram of a controller nanotube network is shown; in the networking of the controller for collecting network topology data by adopting a BGP-LS protocol, BGP-LS connection is established between PE devices, meanwhile, BGP-LS connection is established between part of PE devices and RR devices, and BGP-LS connection is established between the controller and RR devices. When the topology of the networking changes, the RR equipment reports information to the controller. The controller processes the corresponding service according to the received message.
When an interface is added immediately after an interface is deleted on a device, since the change of the interface adopts a netcon subscription manner (for example, when the interface 1 is deleted, the network device sends a netcon message for deleting the interface 1 to the controller, when the interface 1 is added, the network device sends a netcon message for adding the interface 1 to the controller, the two netcon messages are time-sequential), the link is reported by a BGP-LS message (when the link 1 corresponding to the interface 1 is deleted, the network device sends a BGP-LS message for deleting the link 1 to the controller, when the link 1 is added, the network device sends a BGP-LS message for adding the link 1 to the controller, the two BGP-LS messages are time-sequential), which is not a set of mechanism, and thus, the problem that the link discovered by the BGP-LS message is deleted possibly and the link data is lost is caused, and the service is affected is possibly caused.
For example, when the link 1 is directly deleted after receiving the netcon message for deleting the link 1/the BGP-LS message for deleting the link 1, and then the BGP-LS message for adding the link 1 is received, the information of the interface 1 corresponding to the link 1 does not exist in the interface database, and at this time, the link 1 is not added (that is, the controller cannot find the link 1).
In the related art, the controller does not make a guarantee on the time sequence of the device message, and after a problem occurs, the connection is reestablished to receive all BGP-LS information by disconnecting the BGP-LS connection between the device and the controller. Thus, the connection needs to be re-established, and experience is poor in terms of usability; the full message of all network devices is required to be received again and then matched with the data in the controller, so that the system resources are wasted; in the disconnection process, BGP-LS messages cannot be received, and delay exists for the reported information processing.
In order to ensure that the controller can discover links in time, when the deletion of interfaces on two devices is increased again, the application ensures that the links discovered by BGP-LS are not lost under the condition that BGP-LS neighbors are online by adopting the cached BGP-LS link discovery information.
Referring to fig. 2, a detailed flowchart of a link management method according to an embodiment of the present application is shown, where the method is applied to a controller, and the method includes the following steps:
step 200: if BGP-LS information for adding the target link sent by the network equipment is received, judging whether information of a target interface corresponding to the target link is maintained in an interface database.
Specifically, if the controller receives a BGP-LS message for adding the target link, it needs to determine whether the interface database maintains the interface information of the target interface corresponding to the target link.
In practical application, when a link is added, the controller calculates an effective link only when the interface corresponding to the link is added and the interface is normal, and maintains the link to the link list, that is, each link maintained in the link list is an effective link, and interface information corresponding to each effective link is normally maintained in the interface database.
In the embodiment of the application, before receiving the BGP-LS message of adding the target link sent by the network device, the method further includes the following steps:
and if the BGP-LS message for deleting the target link or the NETCONF message of the target interface corresponding to the target link, which is sent by the network equipment, is received, the target link is cached to a link discovery list, and the target link is deleted from the link list.
And if the NETCONF message of deleting the target interface corresponding to the target link or the BGP-LS message of deleting the target link, which is sent by the network equipment, is received, deleting the target link from the link discovery list.
Case one:
and if the controller receives the BGP-LS message which is sent by the network equipment and is used for deleting the target link, the target link is cached to a link discovery list, and the target link is deleted from the link list.
That is, if the controller receives only the BGP-LS message for deleting the target link and does not receive the netcon f message for deleting the target interface corresponding to the target link, the controller does not delete the target link directly and buffers the target link from the link list to the link discovery list.
And if the NETCONF message for deleting the target interface corresponding to the target link is received later, deleting the target link from the link discovery list.
And a second case:
and if the controller receives the NETCONF message which is sent by the network equipment and is used for deleting the target interface corresponding to the target link, the target link is cached to a link discovery list, and the target link is deleted from the link list.
That is, if the controller receives only the netcon f message for deleting the target interface corresponding to the target link, it does not receive the BGP-LS message for deleting the target link, and does not delete the target link directly, and the target link is cached from the link list to the link discovery list.
And deleting the target link from the link discovery list if the BGP-LS message for deleting the target link is received later.
Step 210: and if the interface database is judged to not maintain the information of the target interface corresponding to the target link, caching the target link into a link discovery list.
In the embodiment of the application, if the controller determines that the target interface corresponding to the target link is not maintained in the interface database, determining that the target link is not an effective link, at this time, the effective link is not added into the link list, and caching the target link into the link discovery list when processing the BGP-LS message for adding the target link.
In the embodiment of the application, a link discovery list (link cache list) is newly added on the controller, and when one link is determined to be an inactive link, the link is not deleted directly, but the inactive link is cached in the link discovery list.
Step 220: and if the NETCONF message of adding the target interface, which is sent by the network equipment, is received, adding the target link to a link list.
In the embodiment of the application, after the controller caches the target link in the link discovery list, if the netcon f message of the target interface corresponding to the added target link is received, the controller indicates that the target link is changed from the non-effective link to the effective link, and at this time, the target link can be added in the link discovery list.
Further, in the embodiment of the present application, when the target link is cached to the link discovery list, the aging time of the target link is set; and if the NETCONF message added with the target interface corresponding to the target link is not received within the aging time, deleting the target link from the link discovery list.
For example, the aging time is set to 3 seconds, and if no netcon message for adding the target interface corresponding to the target link is received within 3 seconds, the target link is deleted from the link discovery list.
In the embodiment of the application, if the controller determines that the information of the target interface corresponding to the target link is maintained in the interface database, the target link is added to the link list.
That is, if the BGP-LS message for adding the target link is received and the interface information and the link information are matched, the controller determines that the target link is an active link and directly adds the target link to the link list.
The link management method provided by the embodiment of the application is described in detail below in connection with a specific application scenario.
The application ensures that the links can be found by processing the mechanism of the cache link discovery list according to different conditions, and ensures that the service is not affected under the condition of frequently adding and deleting links in a network slice scene.
After deleting the interface, the controller receives NETCONF subscription message of deleting the interface and adding the interface, and BGP-LS message of deleting the link and adding the link under the scene of adding the interface immediately. The NETCONF subscription messages deleted and added by the interface are time-ordered, and the messages deleted and added by the BGP-LS are time-ordered. Two different types of messages are unordered, coexisting in the 6-combined case.
Time sequence 1:
a. the controller receives the netcon f delete interface message, caches the link corresponding to the interface to the link discovery list (not deleted first (preferably, the aging time can also be set)), and updates the database interface information (deletes the interface information).
b. The controller receives BGP-LS delete link (link corresponding to the interface) message, and the matching cached link discovery list deletes the link from the controller (deletes the link from the link discovery list).
c. The controller receives the netcon f add interface message and updates the database interface information (adds the interface information).
d. And the controller receives a BGP-LS link adding (link corresponding to the interface) message, judges that the interface exists in the database interface information, and adds the link to a link list (link library).
Time sequence 2:
a. and the controller receives the NETCONF deleting interface message, caches the link corresponding to the interface into a link discovery list, and updates the database interface information.
b. The controller receives BGP-LS delete link (link corresponding to the interface) message, and the matching cached link discovery list deletes the link from the controller (deletes the link from the link discovery list).
c. The controller receives BGP-LS add link (link corresponding to the interface) message, buffers the link (not discarded, buffered first (optionally for a certain time)) to the link discovery list, and periodically checks the interface information (in the interface database).
d. And the controller receives the NETCONF adding interface message, updates the database interface information, polls at regular time and then adds the information to the link list.
Time sequence 3:
a. and the controller receives the NETCONF deleting interface message, caches the link corresponding to the interface into a link discovery list, and updates the database interface information.
b. The controller receives the netcon f add interface message, updates the database interface information, and adds the link from the link discovery list to the link list.
c. The controller receives the BGP-LS delete link message and caches the link from the link list to the link discovery list.
d. The controller receives the BGP-LS add link message and adds the link from the link discovery list to the link list.
Time sequence 4:
a. the controller receives the BGP-LS delete link message and caches the link from the link list to the link discovery list.
b. And the controller receives the interface message corresponding to the NETCONF deleting the link, updates the database interface information and deletes the link from the link discovery list.
c. The controller receives the NETCONF increment interface message and updates the database interface information.
d. The controller receives the BGP-LS add link message, periodically checks the link discovery list, and adds the link to the link list.
Time sequence 5:
a. the controller receives the BGP-LS delete link message and caches the link in the link discovery list.
b. And the controller receives the interface message corresponding to the NETCONF deleting the link, updates the database interface information and deletes the link from the link discovery list.
c. The controller receives the BGP-LS add-link message and caches the link to the link discovery list.
d. The controller receives the netcon f add interface message, updates the database interface information, periodically checks the link discovery list, and adds the link to the link list.
Time sequence 6:
a. the controller receives the BGP-LS delete link message and caches the link from the link list to the link discovery list.
b. The controller receives the BGP-LS add-to-link message and adds the link from the link discovery list to the link list.
In practical application, at this time, whether the IP address of the matched BGP-LS message is consistent with the IP address of the interface corresponding to the link in the interface database is required, if so, the IP address is directly put back into the library (link list) of the link, if not, the IP address is firstly cached in the link discovery list, and finally, when the message of adding the interface is received, the IP address is added into the link list.
In the embodiment of the present application, an example will be described in which the IP address of the interface corresponding to the link is unchanged. If the IP address of the interface changes, before determining to add the link corresponding to the interface to the link list, it is necessary to determine whether the IP address carried by the BGP-LS message for adding the link is consistent with the IP address of the interface corresponding to the link in the database interface, if so, the link is valid, and if not, the link is not valid.
c. The controller receives the netcon f delete interface message, updates the database interface information, and caches the link from the link list to the link discovery list.
d. The controller receives the netcon f add interface message, updates the database interface information, periodically checks the link discovery list, and adds the link to the link list.
As can be seen from the above, by adopting the link management method provided by the present application, for the controller, no matter what the receiving timing sequence of the BGP-LS delete/add link message and the netcon delete/add interface message is, the controller can discover the link through BGP-LS.
Referring to fig. 3, an exemplary structure diagram of a link management device according to an embodiment of the present application is shown, where the device is applied to a controller, and the device includes:
a receiving unit 30, configured to receive a BGP-LS message sent by a network device and added to a target link;
a judging unit 31, configured to judge whether information of a target interface corresponding to the target link is maintained in an interface database;
a buffer unit 32, where if the judging unit 31 judges that the information of the target interface corresponding to the target link is not maintained in the interface database, the buffer unit 32 is configured to buffer the target link to a link discovery list;
and an adding unit 33, where if the receiving unit 30 receives a netcon f message for adding a target interface sent by a network device, the adding unit 33 is configured to add the target link to a link list.
Optionally, the apparatus further comprises a deletion unit; the receiving unit 30 receives the BGP-LS message sent by the network device and adding the target link,
if the receiving unit 30 receives the BGP-LS message sent by the network device to delete the target link or the netcon f message of the target interface corresponding to the target link, the caching unit 32 is configured to cache the target link to a link discovery list, and the deleting unit is configured to delete the target link from the link list.
Optionally, if the receiving unit 30 receives a netcon f message sent by the network device to delete a target interface corresponding to the target link, or deletes a BGP-LS message of the target link, the deleting unit is configured to delete the target link from the link discovery list.
Alternatively, if the determining unit 31 determines that the information of the target interface corresponding to the target link is maintained in the interface database, the adding unit 33 is configured to add the target link to the link list.
Optionally, when the buffer unit 32 is configured to buffer the target link to a link discovery list, the buffer unit 32 is further configured to set an aging time of the target link; and if the NETCONF message of the target interface corresponding to the target link is not received in the aging time, the deleting unit is used for deleting the target link from the link discovery list.
The above units may be one or more integrated circuits configured to implement the above methods, for example: one or more application specific integrated circuits (Application Specific Integrated Circuit, abbreviated as ASIC), or one or more microprocessors (digital singnal processor, abbreviated as DSP), or one or more field programmable gate arrays (Field Programmable Gate Array, abbreviated as FPGA), or the like. For another example, when a unit is implemented in the form of a processing element scheduler code, the processing element may be a general purpose processor, such as a central processing unit (Central Processing Unit, CPU) or other processor that may invoke the program code. For another example, the units may be integrated together and implemented in the form of a system-on-a-chip (SOC).
Further, in the link management device provided by the embodiment of the present application, from a hardware level, a hardware architecture schematic diagram of the link management device may be shown in fig. 4, and the link management device may include: a memory 40 and a processor 41,
memory 40 is used to store program instructions; the processor 41 invokes the program instructions stored in the memory 40 to execute the above-described method embodiments in accordance with the obtained program instructions. The specific implementation manner and the technical effect are similar, and are not repeated here.
Optionally, the present application also provides a controller comprising at least one processing element (or chip) for performing the above-described method embodiments.
Alternatively, the application also provides a program product, such as a computer-readable storage medium, having stored thereon computer-executable instructions for causing a computer to perform the above-described method embodiments.
Here, a machine-readable storage medium may be any electronic, magnetic, optical, or other physical storage device that may contain or store information, such as executable instructions, data, or the like. For example, a machine-readable storage medium may be: RAM (Radom Access Memory, random access memory), volatile memory, non-volatile memory, flash memory, a storage drive (e.g., hard drive), a solid state drive, any type of storage disk (e.g., optical disk, dvd, etc.), or a similar storage medium, or a combination thereof.
The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. A typical implementation device is a computer, which may be in the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being functionally divided into various units, respectively. Of course, the functions of each element may be implemented in the same piece or pieces of software and/or hardware when implementing the present application.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the application may take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
Moreover, these computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The foregoing description of the preferred embodiments of the application is not intended to be limiting, but rather to enable any modification, equivalent replacement, improvement or the like to be made within the spirit and principles of the application.
Claims (12)
1. A method of link management, applied to a controller, the method comprising:
if BGP-LS information for adding a target link sent by network equipment is received, judging whether information of a target interface corresponding to the target link is maintained in an interface database;
if the interface database is judged to not maintain the information of the target interface corresponding to the target link, caching the target link into a link discovery list;
and if the NETCONF message of adding the target interface, which is sent by the network equipment, is received, adding the target link to a link list.
2. The method of claim 1, wherein prior to receiving the BGP-LS message sent by the network device to add the target link, the method further comprises:
and if the BGP-LS message for deleting the target link or the NETCONF message of the target interface corresponding to the target link, which is sent by the network equipment, is received, the target link is cached to a link discovery list, and the target link is deleted from the link list.
3. The method of claim 2, wherein the method further comprises:
and if the NETCONF message of deleting the target interface corresponding to the target link or the BGP-LS message of deleting the target link, which is sent by the network equipment, is received, deleting the target link from the link discovery list.
4. The method of claim 1, wherein the target link is added to a link list if it is determined that information of a target interface corresponding to the target link is maintained in an interface database.
5. The method according to claim 1 or 2, wherein the aging time of the target link is set when the target link is cached in a link discovery list; and if the NETCONF message added with the target interface corresponding to the target link is not received within the aging time, deleting the target link from the link discovery list.
6. A link management apparatus for use with a controller, the apparatus comprising:
a receiving unit, configured to receive a BGP-LS message sent by a network device and added to a target link;
the judging unit is used for judging whether the information of the target interface corresponding to the target link is maintained in the interface database;
the buffer unit is used for buffering the target link to a link discovery list if the judging unit judges that the information of the target interface corresponding to the target link is not maintained in the interface database;
and the adding unit is used for adding the target link to a link list if the receiving unit receives the NETCONF message of adding the target interface sent by the network equipment.
7. The apparatus of claim 6, wherein the apparatus further comprises a deletion unit; the receiving unit receives the BGP-LS message sent by the network device and adding the target link,
and if the receiving unit receives the BGP-LS message for deleting the target link or the netcon f message for deleting the target interface corresponding to the target link, which is sent by the network device, the caching unit is configured to cache the target link to a link discovery list, and the deleting unit is configured to delete the target link from the link list.
8. The apparatus of claim 7, wherein,
and if the receiving unit receives the NETCONF message of deleting the target interface corresponding to the target link or the BGP-LS message of deleting the target link, which is sent by the network equipment, the deleting unit is used for deleting the target link from the link discovery list.
9. The apparatus according to claim 6, wherein the adding unit is configured to add the target link to the link list if the judging unit judges that information of a target interface corresponding to the target link is maintained in the interface database.
10. The apparatus according to claim 6 or 7, wherein the caching unit is configured to set an aging time of the target link when the caching unit is configured to cache the target link to a link discovery list; and if the NETCONF message of the target interface corresponding to the target link is not received in the aging time, the deleting unit is used for deleting the target link from the link discovery list.
11. A link management apparatus, the link management apparatus comprising:
a memory for storing program instructions;
a processor for invoking program instructions stored in the memory and performing the steps of the method according to any of claims 1-5 in accordance with the obtained program instructions.
12. A computer readable storage medium storing computer executable instructions for causing a computer to perform the steps of the method according to any one of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310755525.5A CN116886606A (en) | 2023-06-26 | 2023-06-26 | Link management method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310755525.5A CN116886606A (en) | 2023-06-26 | 2023-06-26 | Link management method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116886606A true CN116886606A (en) | 2023-10-13 |
Family
ID=88255918
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310755525.5A Pending CN116886606A (en) | 2023-06-26 | 2023-06-26 | Link management method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116886606A (en) |
-
2023
- 2023-06-26 CN CN202310755525.5A patent/CN116886606A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR100912213B1 (en) | Apparatus, and associated method, for facilitating delivery and processing of push content | |
| US20140229626A1 (en) | Re-establishing push notification channels via user identifiers | |
| CN111787069A (en) | Method, device and equipment for processing service access request and computer storage medium | |
| CN111431800B (en) | Method, device and equipment for establishing path and machine-readable storage medium | |
| US10120872B2 (en) | Data caching based on requestor identity | |
| CN106878184B (en) | Data message transmission method and device | |
| US20210329093A1 (en) | Methods and apparatuses for identifying to-be-filtered transaction based on blockchain integrated station | |
| WO2020249129A1 (en) | Network routing method and apparatus | |
| US20110208823A1 (en) | Method and apparatus for improving data transfers in peer-to-peer networks | |
| EP3701735A1 (en) | Methods and apparatus for use in reducing signal latency in a mobile network with use of localized unified data management (udm) entities | |
| CN101317370A (en) | Method and management agent for event notifications correlation | |
| KR20150111952A (en) | Method and system for using a recursive event listener on a node in hierarchical data structure | |
| US20190349436A1 (en) | Methods, apparatus and systems for resuming transmission link | |
| CN111464352A (en) | Call link data processing method and device | |
| CN109982034A (en) | Access request processing method and processing device in video monitoring system | |
| CN112968945B (en) | Current limiting method and device, electronic equipment and storage medium | |
| CN113507431B (en) | Message management method, device, equipment and machine-readable storage medium | |
| CN110581784B (en) | Node health check method, device and equipment | |
| CN110209986A (en) | Internal storage state method of data synchronization and device | |
| US9043274B1 (en) | Updating local database and central database | |
| CN116886606A (en) | Link management method and device | |
| CN107846476B (en) | Information synchronization method, equipment and storage medium | |
| CN107547605A (en) | A kind of message reading/writing method and node device based on node queue | |
| CN111314432B (en) | Message processing method and device | |
| CN111669320A (en) | Method for processing message and network equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |