CN113179211B - Method and device for routing and for setting up a communication connection - Google Patents
Method and device for routing and for setting up a communication connection Download PDFInfo
- Publication number
- CN113179211B CN113179211B CN202110441896.7A CN202110441896A CN113179211B CN 113179211 B CN113179211 B CN 113179211B CN 202110441896 A CN202110441896 A CN 202110441896A CN 113179211 B CN113179211 B CN 113179211B
- Authority
- CN
- China
- Prior art keywords
- notification
- smooth
- smooth restart
- restart
- response
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 87
- 238000004891 communication Methods 0.000 title claims description 38
- 230000004044 response Effects 0.000 claims abstract description 73
- 230000005540 biological transmission Effects 0.000 claims abstract description 10
- 230000002093 peripheral effect Effects 0.000 claims description 43
- 230000007246 mechanism Effects 0.000 claims description 16
- 230000005856 abnormality Effects 0.000 claims description 13
- 238000012790 confirmation Methods 0.000 claims description 12
- 238000000605 extraction Methods 0.000 claims description 10
- 238000004590 computer program Methods 0.000 claims description 8
- 230000010355 oscillation Effects 0.000 abstract description 8
- 239000000284 extract Substances 0.000 description 18
- 238000010586 diagram Methods 0.000 description 11
- 238000012217 deletion Methods 0.000 description 10
- 230000037430 deletion Effects 0.000 description 10
- 230000008569 process Effects 0.000 description 8
- 238000012545 processing Methods 0.000 description 8
- 230000000694 effects Effects 0.000 description 6
- 230000006870 function Effects 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 3
- 238000004364 calculation method Methods 0.000 description 2
- 238000001514 detection method Methods 0.000 description 2
- 239000000835 fiber Substances 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 239000004973 liquid crystal related substance Substances 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000014759 maintenance of location Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 239000004065 semiconductor 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/02—Topology update or discovery
- H04L45/04—Interdomain routing, e.g. hierarchical 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/02—Topology update or discovery
-
- 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/14—Routing performance; Theoretical aspects
-
- 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 embodiment of the disclosure discloses a method and a device for routing. One embodiment of the method comprises the following steps: in response to receiving a smooth restart notification for a target protocol, extracting flag bit information for characterizing whether a pre-smooth restart transmission notification is supported based on the smooth restart notification; responsive to determining that the flag bit information meets a preset smooth restart condition, reserving a routing path to the device indicated by the smooth restart notification; and deleting the route advertised by the device indicated by the smooth restart notification in response to determining that the flag bit information does not meet the preset smooth restart condition. The embodiment can reduce route oscillation on the premise of avoiding packet loss.
Description
Technical Field
Embodiments of the present disclosure relate to the field of computer technology, and in particular, to methods and apparatuses for routing and for establishing a communication connection.
Background
With the rapid development of internet technology, how to ensure as stable a communication connection between a plurality of devices as possible becomes a problem to be considered.
In the prior art, graceful Restart provides a mechanism for ensuring that forwarding traffic is not interrupted when a protocol is restarted. Because route oscillation is not generated in the whole protocol restarting process, forwarding route is not changed, and equipment can keep uninterrupted forwarding of data, so that uninterrupted operation of forwarding service can be realized.
Disclosure of Invention
Embodiments of the present disclosure propose methods, apparatuses, systems, electronic devices and media for routing and for establishing a communication connection.
In a first aspect, embodiments of the present disclosure provide a method for routing, the method comprising: in response to receiving a smooth restart notification for a target protocol, extracting flag bit information for characterizing whether a pre-smooth restart transmission notification is supported based on the smooth restart notification; in response to determining that the flag bit information meets a preset smooth restart condition, reserving a routing path to the device indicated by the smooth restart notification; and deleting the route advertised by the device indicated by the smooth restart notification in response to determining that the flag bit information does not meet the preset smooth restart condition.
In some embodiments, after maintaining the routing path to the device indicated by the graceful restart notification, the method further comprises: sending smooth restart confirmation information to the device indicated by the smooth restart notification; and in response to receiving the first information to be forwarded, forwarding the message according to the reserved routing path.
In some embodiments, after deleting the route advertised by the device indicated by the graceful restart notification, the method further comprises: responding to the received second information to be forwarded, and selecting a target route from a route table after deleting the route advertised by the device indicated by the smooth restart notification; and forwarding the message according to the routing path indicated by the target route.
In some embodiments, in response to receiving the graceful restart notification for the target protocol, extracting flag bit information for characterizing whether to support a graceful restart pre-sent notification based on the graceful restart notification includes: in response to receiving the message of the target protocol, extracting a message type from the message of the target protocol according to the message format of the target protocol; in response to determining that the message type is used to indicate a graceful restart notification, the target protocol based message extracts flag bit information that characterizes whether a graceful restart pre-sent notification is supported.
In some embodiments, the target protocol comprises a border gateway protocol; and extracting the flag bit information for representing whether the smooth restart pre-sending notification is supported based on the message of the target protocol, including: extracting a preset field from a message for establishing a border gateway protocol connection; and selecting a value corresponding to the target bit from the preset field as the zone bit information.
In some embodiments, the method further comprises: responsive to detecting the connection interruption of the target protocol and not receiving the graceful restart notification, the connected peer device advertised route is deleted.
In a second aspect, embodiments of the present disclosure provide a method for establishing a communication connection, the method comprising: responsive to determining that the graceful restart condition for the target protocol is satisfied and that the at least one peripheral device supports a graceful restart mechanism, sending a graceful restart notification for the target protocol to the at least one peripheral device; and executing a smooth restarting procedure.
In some embodiments, the performing the smooth restart procedure includes: and restarting the target protocol in response to receiving smooth restarting confirmation information corresponding to the smooth restarting notification sent by at least one peripheral device.
In a third aspect, embodiments of the present disclosure provide an apparatus for routing, the apparatus comprising: an extraction unit configured to extract, based on the smooth restart notification, flag bit information for characterizing whether or not a pre-smooth restart transmission notification is supported, in response to receiving the smooth restart notification for the target protocol; a reservation unit configured to reserve a routing path to the device indicated by the smooth restart notification in response to determining that the flag bit information meets a preset smooth restart condition; and a first deleting unit configured to delete the route advertised by the device indicated by the smooth restart notification, in response to determining that the flag bit information does not meet a preset smooth restart condition.
In some embodiments, the apparatus further comprises: an information transmitting unit configured to transmit smooth restart confirmation information to the device indicated by the smooth restart notification; and the first forwarding unit is configured to forward the message according to the reserved routing path in response to receiving the first information to be forwarded.
In some embodiments, the apparatus further comprises: a selecting unit configured to select a target route from a route table after deleting the route advertised by the device indicated by the smooth restart notification in response to receiving the second information to be forwarded; and a second forwarding unit configured to forward the message according to the routing path indicated by the target route.
In some embodiments, the extracting unit includes: a first extraction module configured to extract a message type from a message of a target protocol in accordance with a message format of the target protocol in response to receiving the message of the target protocol; and a second extraction module configured to extract, based on the message of the target protocol, flag bit information for characterizing whether the smooth pre-restart transmission notification is supported, in response to determining that the message type is used for indicating the smooth restart notification.
In some embodiments, the target protocol comprises a border gateway protocol; the second extraction module is further configured to: extracting a preset field from a message for establishing a border gateway protocol connection; and selecting a value corresponding to the target bit from the preset field as the zone bit information.
In some embodiments, the apparatus further comprises: and a second deleting unit configured to delete the route advertised by the connected peer device, in response to detecting the connection interruption of the target protocol and not receiving the smooth restart notification.
In a fourth aspect, embodiments of the present disclosure provide an apparatus for establishing a communication connection, the apparatus comprising: a notification transmission unit configured to transmit a smooth restart notification for the target protocol to at least one peripheral device in response to determining that the smooth restart condition for the target protocol is satisfied and that the at least one peripheral device supports the smooth restart mechanism; and the restarting unit is configured to execute a smooth restarting procedure.
In some embodiments, the above-described restart unit is further configured to: and restarting the target protocol in response to receiving smooth restarting confirmation information corresponding to the smooth restarting notification sent by at least one peripheral device.
In a fifth aspect, embodiments of the present application provide a system for communication, the system comprising: a first device configured to perform a method as described in any implementation of the first aspect; a second device configured to perform a method implementing the second aspect as described.
In a sixth aspect, embodiments of the present disclosure provide an electronic device, comprising: one or more processors; a storage device having one or more programs stored thereon; the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method as described in any of the implementations of the first aspect.
In a seventh aspect, embodiments of the present disclosure provide a computer readable medium having stored thereon a computer program which, when executed by a processor, implements a method as described in any of the implementations of the first or second aspects.
The method, the device, the system, the electronic equipment and the medium for routing and establishing communication connection provided by the embodiments of the present disclosure achieve the technical effects of reserving an original route for a smooth restart condition to avoid route oscillation, deleting the original route for a non-smooth restart condition to avoid packet loss by extracting flag bit information for characterizing whether to support smooth restart before-sending notification based on a received smooth restart notification, and performing reservation or deletion of a route advertised by an opposite terminal device according to a connection interruption reason (e.g., whether caused by smooth restart) indicated by the flag bit information. By firstly sending the smooth restart notification for the target protocol to the peripheral equipment under the condition that the smooth restart condition for the target protocol is met and the smooth restart mechanism is supported by at least one peripheral equipment, and then executing the step of the smooth restart flow, the equipment with the neighbor relation executing the smooth restart flow can be informed of whether the local connection interruption is caused by the smooth restart, so that a reference basis is provided for corresponding route reservation or deletion processing of the opposite terminal equipment.
Drawings
Other features, objects and advantages of the present disclosure will become more apparent upon reading of the detailed description of non-limiting embodiments, made with reference to the following drawings:
FIG. 1 is an exemplary system architecture diagram in which an embodiment of the present disclosure may be applied;
fig. 2 is a flow chart of one embodiment of a method for routing according to the present disclosure;
FIG. 3 is a schematic diagram of one application scenario of a method for routing according to an embodiment of the present disclosure;
fig. 4 is a flow chart of yet another embodiment of a method for establishing a communication connection according to the present disclosure;
FIG. 5 is a schematic structural diagram of one embodiment of an apparatus for routing according to the present disclosure;
fig. 6 is a schematic structural diagram of one embodiment of an apparatus for establishing a communication connection according to the present disclosure;
FIG. 7 is a timing diagram of interactions between various devices in one embodiment of a system for communication according to the present application;
fig. 8 is a schematic structural diagram of an electronic device suitable for use in implementing embodiments of the present disclosure.
Detailed Description
The present disclosure is described in further detail below with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be noted that, for convenience of description, only the portions related to the present invention are shown in the drawings.
It should be noted that, without conflict, the embodiments of the present disclosure and features of the embodiments may be combined with each other. The present disclosure will be described in detail below with reference to the accompanying drawings in conjunction with embodiments.
Fig. 1 illustrates an exemplary architecture 100 to which the methods of the present disclosure for routing and for establishing a communication connection or apparatuses for routing and for establishing a communication connection may be applied.
As shown in fig. 1, system architecture 100 may include network devices 101, 102, 103, 104 and a network 105. The network 105 serves as a medium to provide communication links between the network devices 101, 102, 103, 104. The network 105 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
The network devices 101, 102, 103, 104 may interact through the network 105 to receive or send messages, etc. The network devices 101, 102, 103, 104 may be hardware or software. When the network devices 101, 102, 103, 104 are hardware, they may be various electronic devices with data forwarding capabilities, including but not limited to smartphones, tablets, laptop computers, desktop computers, routers, and the like. When the network devices 101, 102, 103, 104 are software, they can be installed in the above-listed electronic devices. Which may be implemented as multiple software or software modules (e.g., software or software modules for providing distributed services) or as a single software or software module. The present invention is not particularly limited herein.
It should be noted that the method for routing and the method for establishing a communication connection provided by the embodiments of the present disclosure are generally performed by the network devices 101, 102, 103, 104, and accordingly, the method for routing and the apparatus for establishing a communication connection are generally provided in the network devices 101, 102, 103, 104.
It should be understood that the number of network devices, networks in fig. 1 is merely illustrative. There may be any number of network devices and networks as desired for implementation.
With continued reference to fig. 2, a flow 200 of one embodiment of a method for routing according to the present disclosure is shown. The method for routing comprises the following steps:
in step 201, in response to receiving the graceful restart notification for the target protocol, flag bit information for characterizing whether or not the graceful restart pre-sending notification is supported is extracted based on the graceful restart notification.
In the present embodiment, in response to receiving the smooth restart notification for the target protocol, the execution body of the method for routing (one of the network devices 101, 102, 103, 104 shown in fig. 1) may extract flag bit information for characterizing whether or not the smooth restart pre-sending notification is supported based on the smooth restart notification in various ways. The target protocol may be a routing protocol that is pre-specified according to an actual application requirement. In general, the above-described target protocols may include various external gateway protocols (EGP, exterior Gateway Protocol).
The execution body may determine a message type of the received notification (notification) according to a preset message format. In response to determining that the received notification belongs to a graceful restart notification for the target protocol, the executing body may extract flag bit information indicating whether to support a graceful restart pre-sent notification in various manners based on the graceful restart notification. As an example, the execution body may extract a value of a field corresponding to a flag bit from a specified message as the flag bit information according to the convention of the target protocol. The flag bit information may be used to characterize whether to support sending notification before smooth restart. As an example, a "1" may be used to indicate that the supporting device sends a notification before a smooth restart, i.e., the device will send a notification message before the smooth restart and then make the smooth restart. As yet another example, a "0" may be used to indicate that the device is not supported to send notifications before a graceful restart, i.e., the device is not sending notification messages before a graceful restart.
In some optional implementations of this embodiment, the executing entity may extract the flag bit information for characterizing whether to support the smooth restart pre-sending notification based on the smooth restart notification according to the following steps:
In a first step, in response to receiving a message of a target protocol, a message type is extracted from the message of the target protocol according to a message format of the target protocol.
In these implementations, in response to receiving a message of the target protocol, the execution body may extract a message type from the message of the target protocol in accordance with a message format of the target protocol. Wherein the message type may be used to indicate whether the message is used to indicate a smooth restart notification.
As an example, the above-mentioned target protocol may be (Border Gateway Protocol, BGP). The execution body may extract the "TYPE" field from the BGP header. For example, when the value corresponding to the "TYPE" field is "3", the execution body may determine that the message is a NOTIFICATION (NOTIFICATION) message. Furthermore, the execution body may further extract a message type from a message content (including Error Code, error Subcode, data) of the notification message.
Six Error codes are defined in RFC (Request For Comments ) 4271. The execution body may extract Cease Notification message with Error Code of 6 as the message type.
Based on the optional implementation manner, the scheme provides a message type judging method compatible with the existing RFC standard, and the compatibility and the expandability of a communication manner are improved.
And a second step of extracting, based on the message of the target protocol, flag bit information for characterizing whether the notification is sent before the smooth restart is supported or not, in response to determining that the message type is used for indicating the smooth restart notification.
In these implementations, in response to determining that the type of message extracted in the first step is used to indicate a graceful restart notification, the executing entity may extract flag bit information for characterizing whether or not a graceful restart pre-sent notification is supported based on the message of the target protocol in various ways. The execution body may extract a value of a field corresponding to a flag bit from the specified message as the flag bit information according to the convention of the target protocol.
Optionally, based on the optional implementation manner, the target protocol may include a border gateway protocol, and the executing body may further extract flag bit information for characterizing whether to support smooth pre-restart sending notification based on a message of the target protocol according to the following steps:
s1, extracting a preset field from a message for establishing the border gateway protocol connection.
In these implementations, the messages used to establish the border gateway protocol connection may include open messages (TYPE "1" in the header). RFC4274 and RFC8538 define the field (Restart flag) in the open message described above for characterizing smooth Restart capability. The field has 4 bits in total, with bits 0 and 1 being defined in the RFC.
S2, selecting a value corresponding to the target bit from the preset field as the flag bit information.
In these implementations, the target bit may be at least one of bit 2 and bit 3 in the Restart flag field. For example, the field may be bit 2, and the execution body may select a value corresponding to bit 2 from the Restart flag field as the flag information.
Based on the optional implementation manner, the scheme provides a flag bit information acquisition method compatible with the existing RFC standard, and the compatibility and the expandability of a communication manner are improved.
Step 202, in response to determining that the flag bit information meets a preset graceful restart condition, reserving a routing path to a device indicated by a graceful restart notification.
In this embodiment, in response to determining that the flag bit information extracted in step 201 meets a preset graceful restart condition, the execution body may reserve a routing path to the device indicated by the graceful restart notification. The preset smooth restart conditions may include various conditions for triggering smooth restart. As an example, in some scenarios, the restart procedure needs to preserve routes for normal message forwarding, and the smooth restart conditions may be consistent with the above scenarios. The smooth restart condition may be that it is detected that an attribute of the BGP connection is modified. The modified attribute is validated by a smooth restart.
In this embodiment, the executing body may implement normal forwarding of the message in the BGP connection establishment process by reserving a routing path leading to the device indicated by the smooth restart notification, so as to avoid cancelling the route advertised by the opposite end due to detection of the BGP connection terminal, and re-perform the route selection calculation.
In some optional implementations of this embodiment, after the routing path to the device indicated by the graceful restart notification is reserved, i.e. in response to determining that the flag information meets the preset graceful restart condition, the execution body may further continue to execute the following steps:
first, smooth restart confirmation information is sent to the device indicated by the smooth restart notification.
In these implementations, the executing body may send smooth restart confirmation information to the device indicated by the smooth restart notification in step 201. The smooth restart confirmation information is used for indicating that the smooth restart notification sent by the device is received.
And secondly, in response to receiving the first information to be forwarded, forwarding the message according to the reserved routing path.
In these implementations, in response to receiving the first information to be forwarded, the execution body may forward the message according to the reserved routing path.
Based on the above optional implementation manner, the scheme can feed back acknowledgement information and forward the message according to the original route when receiving the notification which is sent by other devices and is used for representing that the device is about to execute smooth restarting, and can avoid route oscillation.
In step 203, in response to determining that the flag bit information does not meet the preset graceful restart condition, the route advertised by the device indicated by the graceful restart notification is deleted.
In this embodiment, in response to determining that the flag bit information extracted in step 201 does not meet the preset graceful restart condition, the executing body may delete the route advertised by the device indicated by the graceful restart notification to modify the routing table.
In this embodiment, the executing body may delete the route advertised by the device indicated by the graceful restart notification, reserve the route path leading to the device indicated by the graceful restart notification, and implement normal forwarding of the message in the BGP connection establishment process, so as to avoid the withdrawal of the route advertised by the opposite terminal due to the detection of the BGP connection terminal, and perform the route selection calculation again.
In some optional implementations of this embodiment, after deleting the route advertised by the device indicated by the graceful restart notification, that is, in response to determining that the flag bit information does not meet the preset graceful restart condition, the executing body may further continue to execute the following steps:
And the first step is to respond to the received second information to be forwarded and select a target route from a route table after deleting the route advertised by the device indicated by the smooth restart notification.
In these implementations, in response to receiving the second to-be-forwarded information, the executing body may select the target route from the route table after deleting the route advertised by the device indicated by the graceful restart notification. The second information to be forwarded may be the same as or different from the first information to be forwarded, which is not limited herein. Wherein the target route may be used to replace a device advertised route indicated by the deleted smooth restart notification.
And secondly, forwarding the message according to the routing path indicated by the target route.
In these implementations, the executing body may forward the message according to the path indicated by the target route selected in the first step, that is, forward the second information to be forwarded.
Based on the optional implementation manner, the method and the device can adopt the target route to replace the withdrawn route in time under the condition that the abnormal connection of the opposite terminal equipment caused by non-smooth restarting is determined, so that the problem of packet loss is effectively reduced.
In some optional implementations of this embodiment, in response to detecting a connection interruption of the target protocol and not receiving the smooth restart notification, the executing body may further delete the route advertised by the peer device of the interrupted connection.
Based on the above optional implementation manner, the method and the device can delete the corresponding route under the condition that the connection interruption of the target protocol is detected and the smooth restart notification is not received, thereby effectively reducing the packet loss problem.
With continued reference to fig. 3, fig. 3 is a schematic illustration of an application scenario of a method for routing according to an embodiment of the present disclosure. In the application scenario of fig. 3, the routing device 301 is connected to the routing devices 302, 304, respectively, and the routing device 303 is connected to the routing devices 302, 304, respectively. When an abnormality occurs in the connection of the routing device 301 with the routing device 302, the routing device 301 sends a smooth restart notification 305 for the established connection protocol to the routing device 302. After receiving the smooth restart notification 305, the routing device 302 extracts, based on the smooth restart notification 305, flag bit information for indicating whether the routing device 301 supports smooth pre-restart transmission notification. If the flag bit information is "1", the routing device 302 may reserve the routing path "302→301". If the flag bit information is "0", the routing device 302 may delete the routing path "302→301".
Currently, one of the existing technologies is to determine whether to reserve the route advertised by the peer device only according to whether the peer device supports smooth restart, which results in forwarding traffic according to the original route under some conditions of connection interruption caused by non-smooth restart, and causing a packet loss phenomenon. The method provided by the above embodiment of the present disclosure extracts the flag bit information used for characterizing whether to support the smooth restart before sending the notification based on the received smooth restart notification, and performs the reservation or deletion of the route advertised by the peer device according to the connection interruption reason indicated by the flag bit information (for example, whether caused by the smooth restart), thereby realizing the technical effects of reserving the original route for the smooth restart condition, avoiding route oscillation, deleting the original route for the non-smooth restart condition, and avoiding packet loss.
With further reference to fig. 4, a flow 400 of yet another embodiment of a method for establishing a communication connection is shown. The flow 400 of the method for establishing a communication connection comprises the steps of:
in response to determining that the graceful restart condition for the target protocol is satisfied and that the at least one peripheral device supports a graceful restart mechanism, step 401, a graceful restart notification for the target protocol is sent to the at least one peripheral device.
In the present embodiment, an execution subject of the method for establishing a communication connection (such as one of the network devices 101, 102, 103, 104 shown in fig. 1) may determine whether a smooth restart condition for a target protocol is satisfied and whether at least one peripheral device supports a smooth restart mechanism in various ways. The peripheral device may be, for example, a device that establishes a neighbor relation with the execution subject. The above-mentioned smooth restart condition may be identical to the corresponding description of step 202 in the foregoing embodiment, and will not be repeated here. As an example, the target protocol may be BGP, and the executing entity may extract a preset corresponding field from an open packet (e.g., see corresponding description in the alternative implementation of step 201 in the foregoing embodiment) used when establishing BGP connection with the at least one peripheral device, so as to determine whether the peer device that performs communication connection supports the graceful restart mechanism.
In response to determining that the graceful restart condition for the target protocol is satisfied and that the graceful restart mechanism is supported by the at least one peripheral device, the execution body may send a graceful restart notification for the target protocol to the at least one peripheral device. The smooth restart notification is used for notifying the at least one peripheral device of the reason for causing the connection interruption before the device performs smooth restart.
Step 402, a smooth restart procedure is performed.
In this embodiment, the execution body may execute the smooth restart procedure after sending the smooth restart notification for the target protocol.
In some optional implementations of this embodiment, the executing body may restart the target protocol in response to receiving smooth restart confirmation information corresponding to a smooth restart notification sent by at least one peripheral device. The smooth restart confirmation information may be consistent with the corresponding description of the optional implementation manner of step 202 in the foregoing embodiment, which is not repeated herein.
Based on the above optional implementation manner, the method can execute the smooth restart flow after receiving the smooth restart notification sent by the peripheral equipment acknowledgement, and can ensure the delivery of the smooth restart notification, thereby avoiding the route oscillation caused by the fact that the peripheral equipment does not receive the smooth restart notification.
As can be seen from fig. 4, a flow 400 of the method for establishing a communication connection in this embodiment shows steps of sending a smooth restart notification for a target protocol to a peripheral device and then executing the smooth restart flow under the condition that a smooth restart condition for the target protocol is satisfied and at least one peripheral device supports a smooth restart mechanism. Therefore, the scheme described in the embodiment can inform the device with the neighbor relation executing the smooth restart flow whether the local connection interruption is caused by the smooth restart, so as to provide a reference basis for corresponding route reservation or deletion processing of the opposite terminal device.
With further reference to fig. 5, as an implementation of the method shown in the foregoing figures, the present disclosure provides an embodiment of an apparatus for routing, which corresponds to the method embodiment shown in fig. 2, and which is particularly applicable to various electronic devices.
As shown in fig. 5, the apparatus 500 for routing provided in this embodiment includes an extracting unit 501, a retaining unit 502, and a first deleting unit 503. Wherein the extracting unit 501 is configured to extract, in response to receiving the smooth restart notification for the target protocol, flag bit information for characterizing whether or not the smooth restart pre-sending notification is supported based on the smooth restart notification; a retaining unit 502 configured to retain a routing path to the device indicated by the smooth restart notification in response to determining that the flag bit information meets a preset smooth restart condition; the first deleting unit 503 is configured to delete the route advertised by the device indicated by the smooth restart notification, in response to determining that the flag bit information does not meet a preset smooth restart condition.
In this embodiment, in the apparatus 500 for routing: the specific processes of the extracting unit 501, the retaining unit 502 and the first deleting unit 503 and the technical effects thereof may refer to the descriptions related to step 201, step 202 and step 203 in the corresponding embodiment of fig. 2, and are not repeated herein.
In some optional implementations of this embodiment, the apparatus 500 for routing may further include: an information transmitting unit (not shown in the figure) configured to transmit smooth restart confirmation information to the device indicated by the smooth restart notification; a first forwarding unit (not shown in the figure) is configured to forward the message according to the reserved routing path in response to receiving the first information to be forwarded.
In some optional implementations of this embodiment, the apparatus 500 for routing may further include: a selecting unit (not shown in the figure) configured to select, in response to receiving the second information to be forwarded, a target route from the route table after deleting the route advertised by the device indicated by the graceful restart notification; a second forwarding unit (not shown in the figure) configured to forward the message according to the routing path indicated by the target route.
In some optional implementations of this embodiment, the extracting unit 501 may include: a first extraction module (not shown) configured to extract a message type from the message of the target protocol in accordance with a message format of the target protocol in response to receiving the message of the target protocol; a second extraction module (not shown in the figure) is configured to extract, based on the message of the target protocol, flag bit information for characterizing whether the smooth pre-restart send notification is supported, in response to determining that the message type is used for indicating the smooth restart notification.
In some alternative implementations of the present embodiment, the target protocol may include a border gateway protocol. The second extraction module may be further configured to: extracting a preset field from a message for establishing a border gateway protocol connection; and selecting a value corresponding to the target bit from the preset field as the zone bit information.
In some optional implementations of this embodiment, the apparatus 500 for routing may further include: and a second deleting unit configured to delete the route advertised by the connected peer device, in response to detecting the connection interruption of the target protocol and not receiving the smooth restart notification.
The apparatus provided in the foregoing embodiments of the present disclosure extracts, by the extracting unit 501, flag bit information for characterizing whether to support a smooth restart pre-sending notification based on a received smooth restart notification, and performs reservation by the reservation unit 502 or deletion of a route advertised by an opposite device by the deletion unit 503 according to a connection interruption reason indicated by the flag bit information (e.g., whether to be caused by a smooth restart), thereby implementing a technical effect of reserving an original route for a smooth restart condition to avoid route oscillation, deleting an original route for a non-smooth restart condition to avoid packet loss.
With further reference to fig. 6, as an implementation of the method shown in the above figures, the present disclosure provides an embodiment of an apparatus for establishing a communication connection, which corresponds to the method embodiment shown in fig. 4, and which is particularly applicable in various electronic devices.
As shown in fig. 6, the apparatus 600 for establishing a communication connection provided in the present embodiment includes a notification transmission unit 601 and a restart unit 602. Wherein the notification sending unit 601 is configured to send a smooth restart notification for the target protocol to at least one peripheral device in response to determining that a smooth restart condition for the target protocol is satisfied and that the at least one peripheral device supports a smooth restart mechanism; the restart unit 602 is configured to perform a smooth restart procedure.
In the present embodiment, in the apparatus 600 for establishing a communication connection: the specific processing of the notification sending unit 601 and the restarting unit 602 and the technical effects thereof may refer to the relevant descriptions of the step 401 and the step 402 in the corresponding embodiment of fig. 4, and are not repeated herein.
In the apparatus provided in the foregoing embodiments of the present disclosure, by notifying the sending unit 601, under the condition that the smooth restart condition for the target protocol is satisfied and the at least one peripheral device supports the smooth restart mechanism, first sending a smooth restart notification for the target protocol to the peripheral device, and then executing the smooth restart procedure by the restart unit 602, it may be notified to a device having a neighbor relation that executes the smooth restart procedure whether the local connection interruption is caused by the smooth restart, so as to provide a reference basis for performing corresponding route reservation or deletion processing for the peer device.
With further reference to fig. 7, illustrated is a timing 700 of interactions between various devices in one embodiment of a system for communication. The system for communication may include: a first device (e.g., network devices 101, 102, 103, 104 shown in fig. 1), and a second device (e.g., a device different from the first device among network devices 101, 102, 103, 104 shown in fig. 1). Wherein the first device described above may be configured to implement the method for routing as described in the previous embodiments. The second device described above may be configured to implement the method for establishing a communication connection as described in the previous embodiments.
As shown in fig. 7, in step 701, in response to determining that the graceful restart condition for the target protocol is satisfied and that the at least one peripheral device supports a graceful restart mechanism, the second device sends a graceful restart notification for the target protocol to the at least one peripheral device (e.g., the first device).
In step 702, in response to receiving the graceful restart notification for the target protocol, the first device extracts flag bit information characterizing whether or not a graceful restart pre-send notification is supported based on the graceful restart notification.
In step 703, in response to determining that the flag bit information meets a preset graceful restart condition, the first device reserves a routing path to the device indicated by the graceful restart notification.
In step 704, in response to determining that the flag bit information does not meet the preset graceful restart condition, the first device deletes the device advertised route indicated by the graceful restart notification.
In step 705, the second device performs a smooth restart procedure.
The steps 701 and 705, and the steps 702 to 704 may be respectively identical to the steps 401 and 402, the steps 201 to 203 and the optional implementation manners in the foregoing embodiments, and the descriptions of the steps 401 and 402, the steps 201 to 203 and the optional implementation manners in the foregoing embodiments are also applicable to the steps 701 and 705, and the steps 702 to 704, which are not repeated herein.
According to the system for communication provided by the embodiment of the application, under the condition that the second device meets the smooth restarting condition for the target protocol and at least one peripheral device (for example, the first device) supports the smooth restarting mechanism, the second device firstly sends the smooth restarting notification for the target protocol to the peripheral device, and then executes the smooth restarting process, so that whether the local connection interruption is caused by the smooth restarting or not can be informed to the device with the neighbor relation executing the smooth restarting process, and a reference basis is provided for corresponding route reservation or deletion processing of the opposite terminal device. The first device extracts the zone bit information used for representing whether the second device supports the sending notification before the smooth restarting or not based on the received smooth restarting notification, and performs the reservation or deletion of the route advertised by the opposite terminal device according to the connection interruption reason (such as whether the connection interruption is caused by the smooth restarting) indicated by the zone bit information, thereby realizing the technical effects of reserving the original route for the smooth restarting condition, avoiding route oscillation, deleting the original route for the non-smooth restarting condition, and avoiding packet loss.
Referring now to fig. 8, a schematic diagram of a configuration of an electronic device (e.g., network devices 101, 102, 103, 104 in fig. 1) 800 suitable for use in implementing embodiments of the present application is shown. The server illustrated in fig. 8 is merely an example, and should not impose any limitation on the functionality and scope of use of embodiments of the present application.
As shown in fig. 8, the electronic device 800 may include a processing means (e.g., a central processor, a graphics processor, etc.) 801, which may perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 802 or a program loaded from a storage means 808 into a Random Access Memory (RAM) 803. In the RAM803, various programs and data required for the operation of the electronic device 800 are also stored. The processing device 801, the ROM 802, and the RAM803 are connected to each other by a bus 804. An input/output (I/O) interface 805 is also connected to the bus 804.
In general, the following devices may be connected to the I/O interface 805: input devices 806 including, for example, a touch screen, touchpad, keyboard, mouse, etc.; an output device 807 including, for example, a liquid crystal display (LCD, liquid Crystal Display), speakers, vibrators, and the like; storage 808 including, for example, magnetic tape, hard disk, etc.; communication means 809. The communication means 809 may allow the electronic device 800 to communicate wirelessly or by wire with other devices to exchange data. While fig. 8 shows an electronic device 800 having various means, it is to be understood that not all of the illustrated means are required to be implemented or provided. More or fewer devices may be implemented or provided instead. Each block shown in fig. 8 may represent one device or a plurality of devices as needed.
In particular, according to embodiments of the present application, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present application include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flowcharts. In such an embodiment, the computer program may be downloaded and installed from a network via communication device 809, or installed from storage device 808, or installed from ROM 802. When being executed by the processing device 801, performs the above-described functions defined in the methods of the embodiments of the present application.
It should be noted that, the computer readable medium according to the embodiments of the present disclosure may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In an embodiment of the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. Whereas in embodiments of the present disclosure, the computer-readable signal medium may comprise a data signal propagated in baseband or as part of a carrier wave, with computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, fiber optic cables, RF (Radio Frequency), and the like, or any suitable combination thereof.
The computer readable medium may be contained in the electronic device; or may exist alone without being incorporated into the electronic device. The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: in response to receiving a smooth restart notification for a target protocol, extracting flag bit information for characterizing whether a pre-smooth restart transmission notification is supported based on the smooth restart notification; in response to determining that the flag bit information meets a preset smooth restart condition, reserving a routing path to the device indicated by the smooth restart notification; deleting the route advertised by the device indicated by the smooth restart notification in response to determining that the flag bit information does not meet a preset smooth restart condition; alternatively, the electronic device is caused to: responsive to determining that the graceful restart condition for the target protocol is satisfied and that the at least one peripheral device supports a graceful restart mechanism, sending a graceful restart notification for the target protocol to the at least one peripheral device; and executing a smooth restarting procedure.
Computer program code for carrying out operations of embodiments of the present disclosure may be written in one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C", python, or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider).
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units involved in the embodiments described in the present disclosure may be implemented by means of software, or may be implemented by means of hardware. The described units may also be provided in a processor, for example, described as: a processor comprises an extraction unit, a retention unit and a first deletion unit; alternatively, it can be described as: a processor includes a notification transmission unit and a restart unit. Wherein the names of these units do not constitute a limitation of the unit itself in some cases, for example, the extraction unit may also be described as "in response to receiving a smooth restart notification for a target protocol, extracting, based on the smooth restart notification, a unit for characterizing whether or not the flag information of the notification sent before the smooth restart is supported".
The foregoing description is only of the preferred embodiments of the present disclosure and description of the principles of the technology being employed. It will be appreciated by those skilled in the art that the scope of the invention in the embodiments of the present disclosure is not limited to the specific combination of the above technical features, but encompasses other technical features formed by any combination of the above technical features or their equivalents without departing from the spirit of the invention. Such as the above-described features, are mutually substituted with (but not limited to) the features having similar functions disclosed in the embodiments of the present disclosure.
Claims (13)
1. A method for routing, comprising:
in response to receiving a smooth restart notification for a target protocol, extracting flag bit information used for representing whether a smooth restart pre-sending notification is supported or not based on the smooth restart notification, wherein when a device indicated by the smooth restart notification sends the notification before supporting smooth restart, the device indicated by the smooth restart notification sends the smooth restart notification for the target protocol to at least one peripheral device, and the target protocol is a BGP protocol;
in response to detecting that an abnormality occurs in connection with the device indicated by the smooth restart notification, and in response to determining that the flag bit information meets a preset smooth restart condition, determining that the abnormality is caused by a smooth restart of the device indicated by the smooth restart notification, and reserving a routing path to the device indicated by the smooth restart notification;
In response to detecting that an abnormality occurs in connection with the device indicated by the smooth restart notification, and in response to determining that the flag bit information does not meet the preset smooth restart condition, determining that the abnormality is not caused by a smooth restart of the device indicated by the smooth restart notification, and deleting a route advertised by the device indicated by the smooth restart notification.
2. The method of claim 1, wherein after the reserving of the routing path to the device indicated by the smooth restart notification, the method further comprises:
sending smooth restart confirmation information to the device indicated by the smooth restart notification;
and in response to receiving the first information to be forwarded, forwarding the message according to the reserved routing path.
3. The method of claim 1, wherein after the deleting the device advertised route indicated by the smooth restart notification, the method further comprises:
responding to the received second information to be forwarded, and selecting a target route from a route table after deleting the route advertised by the device indicated by the smooth restart notification;
and forwarding the message according to the routing path indicated by the target route.
4. The method of claim 1, wherein the extracting flag bit information for characterizing whether a smooth pre-restart send notification is supported based on the smooth restart notification in response to receiving a smooth restart notification for a target protocol comprises:
extracting a message type from the message of the target protocol according to the message format of the target protocol in response to receiving the message of the target protocol;
and in response to determining that the message type is used for indicating a smooth restart notification, extracting flag bit information used for representing whether to support a smooth restart pre-sending notification based on the message of the target protocol.
5. The method of claim 4, wherein the target protocol comprises a border gateway protocol; and
the message extraction based on the target protocol is used for representing whether to support the smooth restart and sending the zone bit information of the notification before the restart, and comprises the following steps:
extracting a preset field from a message for establishing the border gateway protocol connection;
and selecting a value corresponding to the target bit from the preset field as the zone bit information.
6. The method according to one of claims 1-5, wherein the method further comprises:
responsive to detecting a connection interruption of the target protocol and not receiving the graceful restart notification, deleting a route advertised by a peer device of the connection.
7. A method for establishing a communication connection, comprising:
responsive to determining that an abnormality occurs in a connection with at least one peripheral device, and responsive to determining that a graceful restart condition for a target protocol is satisfied and that the at least one peripheral device supports a graceful restart mechanism, sending a graceful restart notification for the target protocol to the at least one peripheral device, wherein the at least one peripheral device determines from the graceful restart notification whether the abnormality is due to a graceful restart, the target protocol being a BGP protocol;
executing a smooth restarting procedure;
wherein the at least one peripheral device is configured to perform the method of one of claims 1-6.
8. The method of claim 7, wherein the performing the smooth restart procedure comprises:
and restarting the target protocol in response to receiving smooth restart confirmation information corresponding to the smooth restart notification sent by the at least one peripheral device.
9. An apparatus for routing, comprising:
an extracting unit configured to extract, based on a smooth restart notification, flag bit information for characterizing whether or not a smooth restart pre-sending notification is supported, in response to receiving the smooth restart notification for a target protocol, wherein the smooth restart notification indicates that a device sends a smooth restart notification for the target protocol to at least one peripheral device when the smooth restart notification indicates that the device sends a notification before supporting a smooth restart, the target protocol being a BGP protocol;
A reservation unit configured to determine that the abnormality is caused by a smooth restart of the device indicated by the smooth restart notification and to reserve a routing path to the device indicated by the smooth restart notification in response to detecting that an abnormality occurs in connection with the device indicated by the smooth restart notification and in response to determining that the flag bit information meets a preset smooth restart condition;
a first deleting unit configured to, in response to detecting that an abnormality occurs in connection with the device indicated by the smooth restart notification, and in response to determining that the flag bit information does not meet the preset smooth restart condition, determine that the abnormality is not caused by a smooth restart of the device indicated by the smooth restart notification, and delete a route advertised by the device indicated by the smooth restart notification.
10. An apparatus for establishing a communication connection, comprising:
a notification transmission unit configured to, in response to determining that a smooth restart condition for a target protocol is satisfied and that at least one peripheral device supports a smooth restart mechanism, transmit a smooth restart notification for the target protocol to the at least one peripheral device, wherein the at least one peripheral device determines, in accordance with the smooth restart notification, whether or not the abnormality is caused by a smooth restart in accordance with detecting an abnormality in connection with a device indicated by the smooth restart notification, the target protocol being a BGP protocol;
A restart unit configured to perform a smooth restart procedure;
wherein the at least one peripheral device comprises the apparatus of claim 9.
11. A system for communication, comprising:
a first device configured to perform a method implementing one of claims 1-6;
a second device configured to perform a method implementing the method of claim 7 or 8.
12. An electronic device, comprising:
one or more processors;
a storage device having one or more programs stored thereon;
when executed by the one or more processors, causes the one or more processors to implement the method of any of claims 1-8.
13. A computer readable medium having stored thereon a computer program, wherein the program when executed by a processor implements the method of any of claims 1-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110441896.7A CN113179211B (en) | 2021-04-23 | 2021-04-23 | Method and device for routing and for setting up a communication connection |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110441896.7A CN113179211B (en) | 2021-04-23 | 2021-04-23 | Method and device for routing and for setting up a communication connection |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113179211A CN113179211A (en) | 2021-07-27 |
| CN113179211B true CN113179211B (en) | 2024-04-09 |
Family
ID=76924645
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110441896.7A Active CN113179211B (en) | 2021-04-23 | 2021-04-23 | Method and device for routing and for setting up a communication connection |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113179211B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101741738A (en) * | 2009-12-15 | 2010-06-16 | 中兴通讯股份有限公司 | Method and device for realizing graceful restart of link state routing protocol |
| CN102447587A (en) * | 2012-02-02 | 2012-05-09 | 杭州华三通信技术有限公司 | Graceful restart method based on OSPF (Open Shortest Path First Interior Gateway Protocol) protocol and router thereof |
| CN103973562A (en) * | 2014-05-20 | 2014-08-06 | 杭州华三通信技术有限公司 | Method and device avoiding service interruption in smooth restart process |
| CN105591892A (en) * | 2015-09-16 | 2016-05-18 | 杭州华三通信技术有限公司 | Graceful Restart (GR) process starting method and device |
| CN106209469A (en) * | 2016-07-21 | 2016-12-07 | 杭州迪普科技有限公司 | The method and device that process is restarted |
| WO2017184112A1 (en) * | 2016-04-18 | 2017-10-26 | Arista Networks, Inc. | System and method of a graceful reboot of a network controller |
| EP3582454A1 (en) * | 2018-06-13 | 2019-12-18 | Juniper Networks, Inc. | Graceful restart procedures for label switched paths with label stacks |
-
2021
- 2021-04-23 CN CN202110441896.7A patent/CN113179211B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101741738A (en) * | 2009-12-15 | 2010-06-16 | 中兴通讯股份有限公司 | Method and device for realizing graceful restart of link state routing protocol |
| CN102447587A (en) * | 2012-02-02 | 2012-05-09 | 杭州华三通信技术有限公司 | Graceful restart method based on OSPF (Open Shortest Path First Interior Gateway Protocol) protocol and router thereof |
| CN103973562A (en) * | 2014-05-20 | 2014-08-06 | 杭州华三通信技术有限公司 | Method and device avoiding service interruption in smooth restart process |
| CN105591892A (en) * | 2015-09-16 | 2016-05-18 | 杭州华三通信技术有限公司 | Graceful Restart (GR) process starting method and device |
| WO2017184112A1 (en) * | 2016-04-18 | 2017-10-26 | Arista Networks, Inc. | System and method of a graceful reboot of a network controller |
| CN106209469A (en) * | 2016-07-21 | 2016-12-07 | 杭州迪普科技有限公司 | The method and device that process is restarted |
| EP3582454A1 (en) * | 2018-06-13 | 2019-12-18 | Juniper Networks, Inc. | Graceful restart procedures for label switched paths with label stacks |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113179211A (en) | 2021-07-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109474688B (en) | Method, device, equipment and medium for sending instant communication network request message | |
| CN110750393B (en) | Method, device, medium and equipment for avoiding network service double-machine hot standby brain cracking | |
| CN115004673B (en) | Message pushing method, device, electronic equipment and computer readable medium | |
| CN111694674A (en) | Message distribution processing method, device, equipment and storage medium | |
| CN112583529B (en) | Data processing method, device, equipment and storage medium | |
| WO2023202276A1 (en) | Domain name resolution request processing method and apparatus, and device, medium and program product | |
| CN114938395A (en) | Service response method, device, equipment and storage medium | |
| CN107818027B (en) | Method and device for switching main name node and standby name node and distributed system | |
| CN113179211B (en) | Method and device for routing and for setting up a communication connection | |
| WO2024066374A1 (en) | Service degradation method and apparatus, device, computer-readable medium and program product | |
| CN112713969A (en) | Data transmission method and device and system using same | |
| CN107342981B (en) | Sensor data transmission method and device and virtual reality head-mounted equipment | |
| JP2008197885A (en) | Application abnormal end processing system method therefor and program | |
| CN113300950B (en) | Data processing method and device, electronic equipment and computer readable medium | |
| CN113722126A (en) | Request processing method and device | |
| CN111225423B (en) | Method and device for forwarding data | |
| CN114697339A (en) | Load balancing method and device under centralized architecture | |
| WO2021126400A1 (en) | Preventing notification loss during temporary network disconnection | |
| CN110764932A (en) | Data processing method, system, medium and computing device | |
| CN113238808A (en) | Message pushing method and device | |
| CN115499489B (en) | Method, device, equipment and readable medium for managing sub-network in link | |
| CN111314457B (en) | Method and device for setting virtual private cloud | |
| CN110011767B (en) | Method and apparatus for TCP connection backup | |
| CN112162868B (en) | Data communication method, device and storage medium applied to cluster processing | |
| CN113535428B (en) | Method, device, equipment and medium for processing request message and response message |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |