CN109981467B

CN109981467B - Static route updating method and route centralized management distribution method

Info

Publication number: CN109981467B
Application number: CN201910251381.3A
Authority: CN
Inventors: 不公告发明人
Original assignee: PEOPLE'S BANK OF CHINA NATIONAL CLEARING CENTER
Current assignee: PEOPLE'S BANK OF CHINA NATIONAL CLEARING CENTER
Priority date: 2019-03-29
Filing date: 2019-03-29
Publication date: 2022-02-11
Anticipated expiration: 2039-03-29
Also published as: CN109981467A

Abstract

The invention provides a static route updating method and a route centralized management distribution method, wherein the static route updating method for a route node comprises the following steps: acquiring a static route updating message issued by a route management node; updating a local routing configuration file according to the static routing update message; and loading the updated local routing configuration file to obtain an updated static routing table. When a static routing update message sent by a routing management node is received, the static routing table in the memory is maintained unchanged, the local configuration file is modified, and then the static routing table is reloaded according to the modified local routing configuration file, so that routing information can be updated without restarting application software in the node, the service is ensured not to be interrupted, and the application requirements are met.

Description

Static route updating method and route centralized management distribution method

Technical Field

The invention relates to the field of internet data transmission, in particular to a static route updating method and a route centralized management and distribution method.

Background

With the continuous development of the internet, the application range of a data transmission system is wider and wider, and matched data transmission systems are developed in the industries of banks, catering, logistics and the like for realizing the hierarchical unified management of data, wherein the existing data transmission system mainly adopts a convergent architecture, as shown in fig. 1, a plurality of subordinate nodes converge layer by layer, the number of superior nodes is less than that of the subordinate nodes, the subordinate nodes send monitoring data messages to the superior nodes to realize data summary transmission, and the superior nodes send monitoring management messages to the subordinate nodes to realize data distribution and node management.

At present, routing of each node is not managed in a centralized manner, routing information of lower nodes in a controlled area is managed by each node, all routing configuration needs to be statically set in a configuration file, and when routing confidence needs to be changed, application software in the nodes needs to be restarted, so that service interruption is caused, and application requirements cannot be met.

Disclosure of Invention

In view of the above, the present invention provides a static routing update method and apparatus for a routing node, a routing centralized management distribution method and apparatus for a routing management node, an electronic device, and a computer-readable storage medium, where a static routing table is formed by loading a local routing configuration file into a memory when a node is started, and when a static routing update message sent by a routing management node is received, the static routing table in the memory is maintained unchanged, the local configuration file is modified, and then the static routing table is reloaded according to the modified local routing configuration file, so that routing information can be updated without restarting application software in the node, thereby ensuring that a service is not interrupted and satisfying application requirements.

In order to achieve the purpose, the invention adopts the following technical scheme:

in a first aspect, a static route update method for a routing node is provided, including:

acquiring a static routing update message, wherein the static routing update message is generated by a routing management node when the topology of a routing network changes;

updating a local routing configuration file according to the static routing update message;

and loading the updated local routing configuration file to obtain an updated static routing table.

Further, before obtaining the static route update packet sent by the route management node, the method further includes:

acquiring a local routing configuration file;

and loading the local routing configuration file to obtain a static routing table.

Further, the static route update packet includes: a plurality of pieces of static route update information,

the updating the local routing configuration file according to the static routing update message includes:

comparing each static route updating information with each static route information in the local route configuration file one by one;

if the local routing configuration file already has the static routing information which is the same as the static routing updating information, the static routing information is marked as an updating state;

if the local routing configuration file does not have the static routing information which is the same as the static routing updating information, writing the static routing updating information into the local routing configuration file and identifying the static routing updating information as an increasing state;

and if the static routing information in the local routing configuration file does not appear in the plurality of static routing updating information, identifying the static routing information as a deleted state.

Further, the static routing information and the static routing update information each include: current node, target node, neighboring node, hop count.

Further, the loading the updated local routing configuration file to obtain an updated static routing table includes:

loading the static routing information marked as an updating state and an adding state in the updated local routing configuration file to obtain an updated static routing table;

and replacing the original static routing table by using the updated static routing table.

In a second aspect, a method for centralized management and distribution of routes for a route management node is provided, which includes:

when the topology of the routing network changes, inquiring the affected routing nodes;

generating a corresponding static routing update message according to the affected routing node;

and sending the static routing update message layer by layer until the affected routing node.

Further, when the routing network topology changes, querying the affected routing node includes:

and inquiring the affected routing nodes and the corresponding static routing information to be added and static routing information to be deleted by adopting a depth-first traversal mode.

Further, the generating of the corresponding static route update packet according to the affected routing node includes:

acquiring original static routing information according to the identification of the influenced routing node;

and generating a static routing update message of the influenced routing node according to the original static routing information, the static routing information to be added and the static routing information to be deleted.

Further, the generating the static routing update packet of the affected routing node according to the original static routing information, the static routing information to be added, and the static routing information to be deleted includes:

deleting static routing information to be deleted and adding static routing information to be added in the original static routing information to obtain static routing updating information;

and obtaining a static routing updating message according to the static routing updating information.

In a third aspect, a static route updating apparatus for a routing node is provided, including:

the updating message acquisition module is used for acquiring a static routing updating message which is generated by the routing management node when the topology of the routing network changes;

the configuration file updating module updates the local routing configuration file according to the static routing updating message;

and the routing table updating module loads the updated local routing configuration file to obtain an updated static routing table.

Further, the static route updating apparatus for a routing node further includes:

the configuration file acquisition module is used for acquiring a local routing configuration file;

and the routing table generation module loads the local routing configuration file to obtain a static routing table.

the configuration file updating module comprises:

the message comparison unit compares each static route updating information with each static route information in the local route configuration file one by one;

a first identification unit, which identifies the static routing information as an update state if the static routing information identical to the static routing update information already exists in the local routing configuration file;

a second identification unit, for writing the static route update information into the local route configuration file and identifying it as an added state if the static route information identical to the static route update information does not exist in the local route configuration file;

and the third identification unit is used for identifying the static routing information as a deleted state if the static routing information in the local routing configuration file does not appear in the plurality of static routing updating information.

Further, the routing table updating module comprises:

the routing table updating unit loads the static routing information marked as the updating state and the adding state in the updated local routing configuration file to obtain an updated static routing table;

and the routing table replacing unit replaces the original static routing table by using the updated static routing table.

In a fourth aspect, a centralized routing management distribution apparatus for a routing management node is provided, including:

the analysis module is used for inquiring the affected routing nodes when the topology of the routing network changes;

the generating module generates a corresponding static routing updating message according to the influenced routing node;

and the sending module sends the static routing update message layer by layer until the affected routing node.

Further, the analysis module includes:

and the depth-first traversal unit queries the affected routing nodes and the corresponding static routing information to be added and static routing information to be deleted in a depth-first traversal mode.

Further, the generating module includes:

the obtaining unit is used for obtaining the original static routing information according to the identification of the influenced routing node;

and the message generating unit is used for generating a static routing updating message of the influenced routing node according to the original static routing information, the static routing information to be added and the static routing information to be deleted.

Further, the message generating unit includes:

the data increase and decrease subunit deletes the static routing information to be deleted and increases the static routing information to be added in the original static routing information to obtain static routing update information;

and the message packaging subunit obtains a static route updating message according to the static route updating information.

In a fifth aspect, an electronic device is provided, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor executes the program, the processor implements the steps of the static route update method for a routing node or implements the route centralized management distribution method for a route management node.

In a sixth aspect, a computer-readable storage medium is provided, on which a computer program is stored, which, when being executed by a processor, implements the steps of the static route update method for a routing node or implements the route centralized management distribution method for a route management node.

The invention provides a static route updating method and a static route updating device for a route node, a route centralized management distribution method and a route centralized management distribution device for a route management node, an electronic device and a computer-readable storage medium, wherein the static route updating method for the route node comprises the following steps: acquiring a static route updating message issued by a route management node; updating a local routing configuration file according to the static routing update message; and loading the updated local routing configuration file to obtain an updated static routing table. When a static routing update message sent by a routing management node is received, the static routing table in the memory is maintained unchanged, the local configuration file is modified, and then the static routing table is reloaded according to the modified local routing configuration file, so that routing information can be updated without restarting application software in the node, the service is ensured not to be interrupted, and the application requirements are met.

In order to make the aforementioned and other objects, features and advantages of the invention comprehensible, preferred embodiments accompanied with figures are described in detail below.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts. In the drawings:

fig. 1 is an architecture diagram of a conventional data transmission system;

FIG. 2 is a schematic diagram of a communication link between two nodes;

FIG. 3 is a schematic diagram of the communication links between three levels of nodes;

FIG. 4 is an architecture diagram of a data transmission system in an embodiment of the present invention;

fig. 5 is a first flowchart illustrating a static route update method for a routing node according to an embodiment of the present invention;

fig. 6 is a second flowchart illustrating a static route updating method for a routing node according to an embodiment of the present invention;

fig. 7 shows the specific steps of step S200 in fig. 5 or 6;

fig. 8 shows the specific steps of step S100 in fig. 5 or 6;

fig. 9 is a flowchart illustrating a route centralized management distribution method for a route management node according to an embodiment of the present invention;

fig. 10 shows the detailed steps of step S2000 in fig. 9;

fig. 11 shows the detailed steps of step S2200 in fig. 10;

fig. 12 is a structural diagram of a static route update apparatus for a routing node in an embodiment of the present invention;

fig. 13 is a structural diagram of a route centralized management distribution apparatus for route management nodes in the embodiment of the present invention;

fig. 14 is a block diagram of an electronic device according to an embodiment of the invention.

Detailed Description

In order to make the technical solutions better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only partial embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

It should be noted that the terms "comprises" and "comprising," and any variations thereof, in the description and claims of this application and the above-described drawings, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present application will be described in detail below with reference to the embodiments with reference to the attached drawings.

It should be noted that, without specific description, the routes mentioned herein refer to static routes, that is, configuration relationships allowing links to be established between nodes, and not to link states in which links have been created between nodes.

In the existing network topology, the routing of each node is not managed in a centralized way, each node manages the routing information of subordinate nodes in the area under the jurisdiction by itself, all the routing configuration needs to be statically set in a configuration file, and when the routing confidence needs to be changed, application software in the node needs to be restarted, so that the service is interrupted, and the application requirements cannot be met.

Fig. 2 is a schematic diagram of a communication link between two nodes, where the node may be a server S1, and referring to fig. 2, the server B1 (may be understood as a node B1) may be communicatively connected to at least one terminal device C2 (may be understood as a node C2), the terminal device C2 may send a monitoring data packet to the server B1 through the communication link therebetween, and the server B1 receives the monitoring data packet through the communication link therebetween, and may also send a monitoring management packet to the terminal device C2 through the communication link therebetween. The terminal device C2 provides an input interface for the user.

In addition, referring to fig. 3, the server B1 may further be communicatively connected to at least one server a1, where the server a1 is configured to store data and manage B1 and C2, and the monitoring data packets in C2 may be summarized to a1 through B1.

Based on the above, the terminal device C2 may have a display interface so that the user can operate according to the interface.

It is understood that the terminal device C2 may include a smart phone, a tablet electronic device, a network set-top box, a portable computer, a desktop computer, a Personal Digital Assistant (PDA), a vehicle-mounted device, a smart wearable device, and the like. Wherein, intelligence wearing equipment can include intelligent glasses, intelligent wrist-watch, intelligent bracelet etc..

The server may communicate with the terminal device C2 and between servers using any suitable network protocol, including network protocols not yet developed at the filing date of the present application. Such as the TCP/IP protocol.

The embodiment of the invention provides a static routing updating method for a routing node and a routing centralized management and distribution method for the routing management node.

In practical applications, part of the static route updating method or the route centralized management distribution method may be performed on the side of the terminal device C2 as described above, that is, the architecture shown in fig. 2 or fig. 3, or all the operations may be performed in the server.

That is, both the server and the terminal in the architecture shown in fig. 2 or fig. 3 may be regarded as nodes in the network topology, and execute the static route updating method or the route centralized management distribution method provided in the embodiment of the present invention.

Fig. 4 is an architecture diagram of a data transmission system according to an embodiment of the present invention. As shown in fig. 4, the network topology includes three levels of nodes, a1 and a2 represent top level nodes, which are upper level nodes of B1, B2, and B3, and C1, C2, C3, and C4 are bottom level nodes, which are lower level nodes of B1, B2, and B3.

A1 may act as a route management node responsible for maintaining static route information throughout the network.

In the figure, the solid line represents the route information already existing, and the dotted line represents the new route information gradually added.

The a-level node needs to aggregate the messages of all the lower-level nodes, wherein a2 has the same function as the backup node of a1, and there is no difference in sending the messages of the lower-level nodes to a1 or a 2. The B-level nodes are different from each other, and not only need to send respective messages to the a-level nodes, but also need to forward uplink messages of the lower-level nodes. The C-level nodes are different and all need to send messages to the A-level node through the B-level node, and no lower-level node exists. The scenario is only used as a simple example of the description function, the scheme actually supports a scenario with any number of layers, and is not limited to three layers, the top-level node (a-level) is not limited to master/standby configuration, and also supports multi-activity (multi-activity means that one lower-level node corresponds to multiple upper-level nodes, and communication links are simultaneously established with the multiple upper-level nodes, and during operation, messages are transmitted to the upper-level nodes through the multiple communication links).

It should be noted that the scenario shown in fig. 4 does not have information interaction between peer nodes.

The lower nodes are provided with a plurality of upper nodes, and when one upper node is abnormal, other nodes can be selected to transmit information, so that information interruption is avoided.

In addition, each node can be realized by adopting a server or a terminal.

Each node is provided with software (APP) for executing the static route updating method or the route centralized management distribution method provided by the embodiment of the invention, the APPs used by the nodes at all levels are completely the same, and only static configurations are different.

In order to update routing information without restarting application software in a node, an embodiment of the present invention provides a static routing update method for a routing node, where the static routing update method for a routing node may be executed in any node in a network topology shown in fig. 4, and referring to fig. 5, the static routing update method for a routing node specifically includes the following contents:

step S100: and acquiring a static routing update message, wherein the static routing update message is generated by the routing management node when the topology of the routing network changes.

Wherein, the static route updating message includes all static route information required by the node.

Specifically, after the static routing update packet received by the current routing node is processed by the main thread of the node APP.

Step S200: and updating a local routing configuration file according to the static routing update message.

The configuration file comprises a configuration relation which represents that the node and the upper node and the lower node of the node are allowed to establish a link.

Step S300: and loading the updated local routing configuration file to obtain an updated static routing table.

Specifically, the static reason information indicating the configuration relationship of the node and the upper node and the lower node of the node, which allows establishing the link, in the local routing configuration file is loaded in a table form, so that the static routing table can be obtained.

In the static route updating method provided in the embodiment of the present invention, when a node is started, a local routing configuration file is loaded into a memory to form a static routing table, and when a static routing update message sent by a routing management node is received, the static routing table in the memory is maintained unchanged, the local configuration file is modified, and then the static routing table is reloaded according to the modified local routing configuration file, so that routing information can be updated without restarting application software in the node, thereby ensuring that a service is not interrupted and meeting application requirements.

In addition, the static route updating method provided by the embodiment of the invention enables the route configuration scheme to be simple and dynamically modifiable, and is beneficial to horizontal and vertical extension.

Fig. 6 is a second flowchart illustrating a static route updating method for a routing node according to an embodiment of the present invention. As shown in fig. 6, the static route updating method may further include the following contents based on the static route updating method shown in fig. 5:

step S10: and acquiring a local routing configuration file.

The local routing configuration file can be issued by the routing management node.

Step S20: and loading the local routing configuration file to obtain a static routing table.

Specifically, when an APP in a node is started, a local configuration file is loaded into a memory to form a static routing table.

Fig. 7 shows a specific step of step S200 in fig. 5 or 6. As shown in fig. 7, the step S200 specifically includes the following steps:

step S210: and comparing each piece of static route updating information with each piece of static route information in the local route configuration file one by one.

Wherein, the static route updating message includes: a plurality of static route update messages. Each piece of static route update information may be expressed as: current node | neighbor node | target node | hop count.

Specifically, the current node represents a node for executing the present invention, the target node represents a target node of the route, the neighboring node represents a node that the current node needs to pass through to reach the target node, and the node is located between the current node and the target node and is adjacent to both the current node and the target node (the neighboring means an adjacent layer).

Step S220: and if the local routing configuration file already has the static routing information which is the same as the static routing updating information, identifying the static routing information as an updating state.

If the local routing configuration file already has the static routing information which is the same as the static routing updating information, the routing is not changed, and at the moment, the static routing information is marked as an updating state to indicate that the static routing information is updated or does not need to be updated.

Step S230: and if the local routing configuration file does not have the static routing information which is the same as the static routing updating information, writing the static routing updating information into the local routing configuration file and identifying the static routing updating information as an increasing state.

If the local routing configuration file does not have the static routing information which is the same as the static routing update information, the static routing update information is the information of the newly-built route, and at the moment, the static routing update information is written into the local routing configuration file and is marked as an adding state.

Step S240: and if the static routing information in the local routing configuration file does not appear in the plurality of static routing updating information, identifying the static routing information as a deleted state.

If the static routing information in the local routing configuration file does not appear in the multiple static routing update information, it indicates that the route may have been deleted, and at this time, the static routing information is identified as a deleted state.

Fig. 8 shows a specific step of step S100 in fig. 5 or 6. As shown in fig. 8, the step S100 specifically includes the following steps:

step S110: and loading the static routing information marked as the updating state and the adding state in the updated local routing configuration file to obtain an updated static routing table.

It will be understood by those skilled in the art that if a static route has been deleted, the route information need not be displayed in the static route table, and therefore, only the static route information identified as the updated state and the added state in the updated local route configuration file needs to be loaded.

Step S120: and replacing the original static routing table by using the updated static routing table.

It is worth to be noted that the time for replacing the original static routing table by the updated static routing table is short and can be ignored, and the system operation is not affected, so that the service interruption can be avoided while the static routing update is realized.

Fig. 9 is a flowchart illustrating a route centralized management distribution method for a route management node according to an embodiment of the present invention. As shown in fig. 9, the method for centralized management and distribution of routes for a route management node specifically includes the following steps:

step S1000: when the topology of the routing network changes, the affected routing nodes are queried.

Specifically, when a node leaves the network or a topology relationship needs to be reduced or increased, the routing network topology inevitably changes, and at this time, the situation needs to be explained to the affected node so as to smoothly perform data transmission while the traffic is in progress.

The affected routing nodes and the corresponding static routing information to be added and static routing information to be deleted can be inquired in a depth-first traversal mode.

Step S2000: and generating a corresponding static routing update message according to the influenced routing node.

After the affected routing node is queried, the changed static routing information needs to be calculated, and a corresponding static routing update message is generated.

Step S3000: and sending the static routing update message layer by layer until the affected routing node.

After a static routing update message corresponding to an affected node is generated, the message is sent layer by layer until the message is sent to the affected node, the affected node generates an update local configuration file according to the static routing update message, and then the updated local configuration file is loaded to obtain an updated static routing table, so that routing information can be updated without restarting application software in the node, service interruption is guaranteed, and application requirements are met.

Fig. 10 shows the specific steps of step S2000 in fig. 9. As shown in fig. 10, the step S2000 specifically includes the following steps:

step S2100: and acquiring the original static routing information according to the identification of the influenced routing node.

The routing management node stores the static routing information of all routing nodes in the domain.

Step S2200: and generating a static routing update message of the influenced routing node according to the original static routing information, the static routing information to be added and the static routing information to be deleted.

Specifically, referring to fig. 11, the step S2200 includes the following specific steps:

step S2201: and deleting the static routing information to be deleted and adding the static routing information to be added in the original static routing information to obtain static routing updating information.

Step S2202: and obtaining a static routing updating message according to the static routing updating information.

Specifically, the static route update information is encapsulated to obtain a static route update message.

The following description will be given by way of example with reference to fig. 4:

when a D1 node needs to communicate with a C2 node, the influencing nodes include B1, C2 and D1 (do not include a1, because a1 can reach D1 through 3 hops through an adjacent node B1 without change), B1 adds a route B1| C2| D1|2, C2 adds a route C2| D1| D1|1, and D1 adds a route D1| C2| C2|1, D1| C2| B1|2, D1| C2| a1| 3; and then generating static routing update messages aiming at the nodes B1, C2 and D1 according to the information, and respectively sending the static routing update messages to the nodes B1, C2 and D1.

When B accesses, the influencing node includes A, B, C and C, routes are sent in a hierarchy, A adds routes A | B | B |1, A | B | C |2, A | B | D |3, B adds routes B | A | A |1, B | C | C |1, B | C | D |2, C adds routes C | B |1, C | B | A |2, and C adds routes C | B | B |1, C | B | A | 1.

When C3 is accessed, the influencing nodes include a1, B2, C3 and D2, routes are sent in a hierarchical order, a1 adds route a1| B2| C3|2, B2 adds route B2| C3| C3|1, B2| C3| D2|2, C3 adds route C3| B2| B2|1, C3| B2| a1|2, C3| D2| D2|1, D2 adds route D2| C3| C3|1, D2| C3| B2|2, D2| C3| a1| 3.

Based on the same inventive concept, the present application further provides a static route updating apparatus for a routing node, which can be used to implement the methods described in the foregoing embodiments, as described in the following embodiments. Because the principle of solving the problem of the static route updating device for the routing node is similar to that of the method, the implementation of the static route updating device for the routing node can refer to the implementation of the method, and repeated details are not repeated. As used hereinafter, the term "unit" or "module" may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated.

Fig. 12 is a block diagram of a static route update apparatus for a routing node in an embodiment of the present invention. As shown in fig. 12, the static route updating apparatus for a routing node includes: an update message acquisition module 10, a configuration file update module 20 and a routing table update module 30.

The update message obtaining module 10 obtains a static route update message, where the static route update message is generated by a route management node when a topology of a routing network changes.

The configuration file updating module 20 updates the local routing configuration file according to the static routing update message.

The routing table updating module 30 loads the updated local routing configuration file to obtain the updated static routing table.

The static routing updating device provided in the embodiment of the present invention forms a static routing table by loading a local routing configuration file into a memory when a node is started, and when a static routing update message sent by a routing management node is received, the static routing table in the memory is maintained unchanged, the local configuration file is modified, and then the static routing table is reloaded according to the modified local routing configuration file, so that routing information can be updated without restarting application software in the node, thereby ensuring that a service is not interrupted and satisfying application requirements.

In addition, the static route updating device provided by the embodiment of the invention enables the route configuration scheme to be simple and dynamically modifiable, and is beneficial to horizontal and vertical extension.

In an optional embodiment, the static route updating apparatus for a routing node may further include: the device comprises a configuration file acquisition module and a routing table generation module.

The configuration file acquisition module acquires a local routing configuration file.

And the routing table generation module loads the local routing configuration file to obtain the static routing table.

In an optional embodiment, the static route update message includes: a plurality of static route update messages, the profile update module 20 comprising: the message comparison unit, the first identification unit, the second identification unit and the third identification unit.

And the message comparison unit compares the updating information of each static route with the information of each static route in the local route configuration file one by one.

When the local routing configuration file already contains the static routing information which is the same as the static routing updating information, the first identification unit identifies the static routing information as an updating state.

And when the second identification unit does not have the static routing information which is the same as the static routing update information in the local routing configuration file, writing the static routing update information into the local routing configuration file and identifying the static routing update information as an increased state.

And the third identification unit identifies the static routing information in the local routing configuration file as a deleted state when the static routing information does not appear in the plurality of static routing update information.

In an alternative embodiment, the routing table updating module 30 may include: a routing table updating unit and a routing table replacing unit.

And the routing table updating unit loads the static routing information marked as the updating state and the adding state in the updated local routing configuration file to obtain an updated static routing table.

Based on the same inventive concept, the embodiment of the present application further provides a centralized routing management distribution apparatus for a routing management node, which can be used to implement the methods described in the foregoing embodiments, as described in the following embodiments. Because the principle of solving the problem of the route centralized management and distribution device for the route management node is similar to that of the method, the implementation of the route centralized management and distribution device for the route management node can refer to the implementation of the method, and repeated details are not described again. As used hereinafter, the term "unit" or "module" may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated.

Fig. 13 is a configuration diagram of a route centralized management distribution apparatus for a route management node in the embodiment of the present invention. As shown in fig. 13, the route centralized management distribution apparatus for a route management node includes: an analysis module 100, a generation module 200 and a sending module 300.

The analysis module 100 queries the affected routing nodes when the routing network topology changes.

Specifically, when a node leaves the network or a topology relationship needs to be reduced or increased, the routing network topology will inevitably change, and at this time, the request needs to be explained to the affected node so as to smoothly transmit data when traffic is in progress.

Among them, the analysis module 100 may include: and the depth-first traversal unit queries the affected routing nodes and the corresponding static routing information to be added and static routing information to be deleted in a depth-first traversal mode.

The generating module 200 generates a corresponding static routing update packet according to the affected routing node.

The sending module 300 sends the static route update message layer by layer to the affected routing node.

In an alternative embodiment, the generation module 200 may include: the device comprises an acquisition unit and a message generation unit.

The obtaining unit obtains the original static routing information according to the identification of the affected routing node.

And the message generating unit generates a static routing update message of the influenced routing node according to the original static routing information, the static routing information to be added and the static routing information to be deleted.

In an optional embodiment, the message generating unit may include: a data increase and decrease subunit and a message encapsulation subunit.

The apparatuses, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or implemented by a product with certain functions. A typical implementation device is an electronic device, which may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

In a typical example, the electronic device specifically includes a memory, a processor, and a computer program stored on the memory and executable on the processor, and the processor implements the following steps when executing the program:

Alternatively, the processor implements the following steps when executing the program:

As can be seen from the above description, the electronic device provided in the embodiment of the present invention may be used for static route update of a routing node or for route centralized management and distribution of a routing management node, and the static routing table is formed by loading a local route configuration file into a memory when the node is started, and when a static route update message sent by the routing management node is received, the static routing table in the memory is first maintained unchanged, the local configuration file is modified, and then the static routing table is reloaded according to the modified local route configuration file, so that routing information can be updated without restarting application software in the node, thereby ensuring that a service is not interrupted, and satisfying application requirements.

Referring now to FIG. 14, shown is a schematic diagram of an electronic device 600 suitable for use in implementing embodiments of the present application.

As shown in fig. 14, the electronic apparatus 600 includes a Central Processing Unit (CPU)601 that can perform various appropriate works and processes according to a program stored in a Read Only Memory (ROM)602 or a program loaded from a storage section 608 into a Random Access Memory (RAM)) 603. In the RAM603, various programs and data necessary for the operation of the system 600 are also stored. The CPU601, ROM602, and RAM603 are connected to each other via a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.

The following components are connected to the I/O interface 605: an input portion 606 including a keyboard, a mouse, and the like; an output portion 607 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section 608 including a hard disk and the like; and a communication section 609 including a network interface card such as a LAN card, a modem, or the like. The communication section 609 performs communication processing via a network such as the internet. The driver 610 is also connected to the I/O interface 606 as needed. A removable medium 611 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 610 as necessary, so that a computer program read out therefrom is mounted as necessary on the storage section 608.

In particular, according to an embodiment of the present invention, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, an embodiment of the invention includes a computer-readable storage medium having a computer program stored thereon, which when executed by a processor, performs the steps of:

Alternatively, the computer program when executed by a processor implements the steps of: when the topology of the routing network changes, inquiring the affected routing nodes;

As can be seen from the above description, the computer-readable storage medium provided in the embodiment of the present invention may be used for static route update of a routing node or for route centralized management and distribution of a routing management node, and forms a static routing table by loading a local routing configuration file into a memory when the node is started, and when a static routing update message sent by the routing management node is received, the static routing table in the memory is maintained unchanged, the local configuration file is modified, and then the static routing table is reloaded according to the modified local routing configuration file, so that routing information can be updated without restarting application software in the node, thereby ensuring that a service is not interrupted, and satisfying application requirements.

In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 609, and/or installed from the removable medium 611.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functionality of the units may be implemented in one or more software and/or hardware when implementing the present application.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams 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.

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.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

As will be appreciated by one skilled in the art, 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, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.

The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A static route update method for a routing node, comprising:

maintaining a static routing table in a memory unchanged, and updating a local routing configuration file according to the static routing update message, wherein the local routing configuration file comprises a configuration relation which indicates that a current node and a superior node of the current node and a subordinate node of the current node are allowed to establish a link;

loading the updated local routing configuration file to obtain an updated static routing table;

and the route management node is used for maintaining the static route information of the whole network.

2. The static route updating method for the routing node according to claim 1, wherein before obtaining the static route update packet sent by the route management node, the method further comprises:

acquiring a local routing configuration file;

3. The static route update method for routing nodes according to claim 1, wherein the static route update packet includes: a plurality of pieces of static route update information,

comparing each piece of static route updating information with each piece of static route information in the local route configuration file one by one;

if the local routing configuration file already has the static routing information which is the same as the static routing updating information, identifying the static routing information as an updating state;

4. The static route update method for a routing node of claim 3, wherein the static route information and the static route update information each comprise: current node, target node, neighboring node, hop count.

5. The static routing update method for routing nodes of claim 3, wherein the loading of the updated local routing configuration file results in an updated static routing table, comprising:

6. A method for centralized management and distribution of routes for a route management node, comprising:

sending the static routing update message layer by layer to the affected routing node, so that the affected routing node updates a local routing configuration file according to the static routing update message, and loads the updated local routing configuration file to obtain an updated static routing table, wherein the local routing configuration file comprises a configuration relation which indicates that a link is allowed to be established between a current node and a superior node of the current node and a subordinate node of the current node;

7. The method according to claim 6, wherein the querying affected routing nodes when the routing network topology changes comprises:

8. The method according to claim 7, wherein the generating the corresponding static route update packet according to the affected routing node comprises:

9. The method according to claim 8, wherein the generating the static routing update packet of the affected routing node according to the original static routing information, the static routing information to be added, and the static routing information to be deleted includes:

10. A static route update apparatus for a routing node, comprising:

a configuration file updating module for maintaining a static routing table in a memory unchanged, and updating a local routing configuration file according to the static routing update message, wherein the local routing configuration file comprises a configuration relation which indicates that a current node and a superior node of the current node and a subordinate node of the current node are allowed to establish a link;

the routing table updating module loads the updated local routing configuration file to obtain an updated static routing table;

11. The static route update apparatus for a routing node of claim 10, further comprising:

12. The static route update apparatus for a routing node according to claim 10, wherein the static route update packet comprises: a plurality of pieces of static route update information,

the configuration file updating module comprises:

the message comparison unit is used for comparing each piece of static route updating information with each piece of static route information in the local route configuration file one by one;

a first identification unit, configured to identify the static routing information as an update state if the static routing information that is the same as the static routing update information already exists in the local routing configuration file;

a second identification unit, configured to, if static route information that is the same as the static route update information does not exist in the local route configuration file, write the static route update information into the local route configuration file and identify the static route update information as an added state;

13. The static routing update apparatus for a routing node of claim 12, wherein the static routing information and the static routing update information each comprise: current node, target node, neighboring node, hop count.

14. The static routing update apparatus for a routing node of claim 12, wherein the routing table update module comprises:

and the routing table replacing unit is used for replacing the original static routing table by using the updated static routing table.

15. A route centralized management distribution apparatus for a route management node, comprising:

the sending module sends the static routing update messages layer by layer to the affected routing nodes so that the affected routing nodes update local routing configuration files according to the static routing update messages, and loads the updated local routing configuration files to obtain updated static routing tables, wherein the local routing configuration files comprise configuration relations which represent that a current node and a superior node of the current node and a subordinate node of the current node are allowed to establish links;

16. The apparatus for centralized management of routing and distribution for a route management node according to claim 15, wherein said analyzing module comprises:

17. The apparatus for centralized management of routing and distribution for a route management node according to claim 16, wherein said generating module comprises:

18. The apparatus for centralized management and distribution of routes for route management node according to claim 17, wherein the packet generating unit comprises:

19. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor when executing the program implements the steps of the static route update method for a routing node of any one of claims 1 to 5 or implements the route centralized management distribution method for a route management node of any one of claims 6 to 9.

20. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the static route update method for a routing node of any one of claims 1 to 5 or carries out the route centralized management distribution method for a route management node of any one of claims 6 to 9.