CN109219105B - Route switching method and route switching system - Google Patents
Route switching method and route switching system Download PDFInfo
- Publication number
- CN109219105B CN109219105B CN201710518731.9A CN201710518731A CN109219105B CN 109219105 B CN109219105 B CN 109219105B CN 201710518731 A CN201710518731 A CN 201710518731A CN 109219105 B CN109219105 B CN 109219105B
- Authority
- CN
- China
- Prior art keywords
- route
- heartbeat
- routing
- network node
- fault
- 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
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W40/00—Communication routing or communication path finding
- H04W40/34—Modification of an existing route
- H04W40/36—Modification of an existing route due to handover
Abstract
The invention discloses a route switching method and a route switching system, and relates to the field of mobile communication. The method comprises the following steps: routing heartbeat servers are respectively arranged in a network node and a plurality of client systems; the routing heartbeat server positioned at the network node is respectively communicated with the routing heartbeat servers positioned at the plurality of client systems through heartbeat messages, and the fault service route is determined according to the heartbeat response message of the heartbeat messages; the backup traffic route is used instead of the failed traffic route. Therefore, disaster recovery routing switching of a service layer is realized, and blind-spot-free fault link detection of the whole routing is realized.
Description
Technical Field
The present invention relates to the field of mobile communications, and in particular, to a route switching method and a route switching system.
Background
The industry short message service refers to non-operational short message service which is oriented to internal staff of a client, the client and related staff and meets the requirements of daily work management, information publishing and the like. According to the sending direction of industry short messages, the method can be divided into an MT (terminal user to be sent by an enterprise) type and an MO (terminal user to be sent by the enterprise) type.
The industry short message service mainly provides the industry short message service for important customers such as banks, insurance, fund, major parts and the like. With the increasing use of industry short messages by more and more key customers, the safety and the stability of the industry short messages are important, the requirement of the industry short message routing disaster recovery is provided, and the rapid response is realized when sudden accidents happen.
Disclosure of Invention
The invention solves the technical problem of how to realize disaster recovery route switching of a service layer.
According to an aspect of the embodiments of the present invention, there is provided a route switching method, including: routing heartbeat servers are respectively arranged in a network node and a plurality of client systems; the routing heartbeat server positioned at the network node is respectively communicated with the routing heartbeat servers positioned at the plurality of client systems through heartbeat messages, and the fault service route is determined according to the heartbeat response message of the heartbeat messages; the backup traffic route is used instead of the failed traffic route.
In one embodiment, determining the failed traffic route from a heartbeat response message of the heartbeat message comprises: and determining a fault link in the fault service route according to whether the heartbeat response message of the route heartbeat server positioned in a plurality of client systems is received.
In one embodiment, replacing the failed traffic route with the backup traffic route comprises: if a failed link exists in the route between the client system and the network node, the backup route between the client system and the network node is used for replacing the failed service route.
In one embodiment, the heartbeat message contains a specific string so that the network node preferentially processes heartbeat messages containing the specific string.
In one embodiment, heartbeat messages are sent periodically or manually to determine the failed traffic route.
According to another aspect of the embodiments of the present invention, there is provided a route switching system, including: the system comprises a network node, a plurality of client systems and a routing heartbeat server; the routing heartbeat server is arranged in the network node and a plurality of client systems; the routing heartbeat server includes: the system comprises a heartbeat communication module, a failure service route determining module and a failure service route determining module, wherein the heartbeat communication module is configured to realize that a routing heartbeat server positioned at a network node is respectively communicated with routing heartbeat servers positioned at a plurality of client systems through heartbeat messages; a traffic route replacement module configured to replace the failed traffic route with the backup traffic route.
In one embodiment, the failed traffic routing determination module is configured to: and determining a fault link in the fault service route according to whether the heartbeat response message of the route heartbeat server positioned in a plurality of client systems is received.
In one embodiment, the traffic routing replacement module is configured to: if a failed link exists in the route between the client system and the network node, the backup route between the client system and the network node is used for replacing the failed service route.
In one embodiment, the heartbeat message contains a specific string so that the network node preferentially processes heartbeat messages containing the specific string.
In one embodiment, the routing heartbeat server is configured to: and sending heartbeat messages regularly or manually to determine the fault service route.
According to another aspect of the embodiments of the present invention, there is provided a route switching system, including: a memory; and a processor coupled to the memory, the processor configured to perform the aforementioned route switching method based on instructions stored in the memory.
According to still another aspect of the embodiments of the present invention, there is provided a computer-readable storage medium storing computer instructions, which when executed by a processor, implement the aforementioned route switching method.
The route switching method provided by the invention can realize disaster recovery route switching of a service layer and realize blind-spot-free fault link detection of the whole route.
Other features of the present invention and advantages thereof will become apparent from the following detailed description of exemplary embodiments thereof, which proceeds with reference to the accompanying drawings.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without inventive exercise.
Fig. 1 is a schematic diagram illustrating an embodiment of a method for switching a route of an industry sms in the prior art.
Fig. 2 is a schematic diagram illustrating another embodiment of a method for switching a route of an industry sms in the prior art.
Fig. 3 is a flowchart illustrating a route switching method according to an embodiment of the present invention.
Fig. 4 shows a schematic diagram of a network node performing route switching when a failure a occurs.
Fig. 5 shows a schematic diagram of a network node performing route switching when a failure b occurs.
Fig. 6 is a schematic structural diagram of a routing system according to an embodiment of the present invention.
Fig. 7 is a schematic structural diagram of a routing heartbeat server according to an embodiment of the present invention.
Fig. 8 is a schematic structural diagram of a routing system according to another embodiment of the present invention.
Fig. 9 is a schematic structural diagram of a routing system according to yet another embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the invention, its application, or uses. 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 invention.
The inventor finds that the existing industry short message disaster recovery routing has the following problems:
first, only the disaster recovery routing of the link layer can be provided, and the disaster recovery routing of the service layer cannot be realized.
Fig. 1 is a schematic diagram illustrating an embodiment of a method for switching a route of an industry sms in the prior art. As shown in fig. 1, the industry short message configures a link-level disaster recovery route. The solid line part represents the primary route, and the dotted line part represents the backup route. The primary route has X, Y and other clients, and if only the route from the X client to the network node 1 has a fault, the standby route switching cannot be performed only for the X client.
For example, if a failure a occurs, the network node 1 can only perform a link-level route switching to simultaneously switch the industry short messages of the customer X and the customer Y to the standby route.
Secondly, only the link fault connected with the network node 1 can be detected, the fault of the industry short message downstream path or node cannot be detected, and a routing fault blind area exists.
Fig. 2 is a schematic diagram illustrating another embodiment of a method for switching a route of an industry sms in the prior art. As shown in fig. 2, the industry sms configures a link-level disaster recovery route. The solid line part represents the primary route, and the dotted line part represents the backup route.
For example, if a fault b occurs, at this time, only the industry short message route of the client Y has a fault, the industry short message route of the client is still normal, but the network node 1 does not sense the fault b, and does not know the link fault at the position b nor the industry short message route of the client Y has a fault. The network node 1 can perform neither the route switching of the link layer nor the route switching of the client Y service layer.
The route switching method according to an embodiment of the present invention is described below with reference to fig. 3.
Fig. 3 is a flowchart illustrating a route switching method according to an embodiment of the present invention. As shown in fig. 3, the route switching method of this embodiment includes:
step S302, route heartbeat servers are respectively arranged in the network node and the plurality of client systems.
The industry short message routing heartbeat server is mainly respectively arranged in a network node with a routing function and a client system. The industry short message routing heartbeat server is used for sending heartbeat short messages, receiving heartbeat short messages and responding heartbeat short messages.
Step S304, the routing heartbeat server at the network node communicates with the routing heartbeat servers at the plurality of client systems respectively through heartbeat messages, and determines the fault service route according to the heartbeat response messages of the heartbeat messages.
For example, a failed link in a failed traffic route may be determined based on whether heartbeat response messages are received from routing heartbeat servers located on multiple client systems.
Step S306, the standby service route is used to replace the failure service route.
For example, if a failed link exists in a route between a client system to a network node, the failed traffic route may be replaced with a backup route between the client system to the network node.
A specific application example of the route switching method is described below with reference to fig. 4 and 5. Fig. 4 shows a schematic diagram of a network node performing route switching when a failure a occurs. Fig. 5 shows a schematic diagram of a network node performing route switching when a failure b occurs.
Taking the uplink short message as an example, the routing heartbeat server in the network node 1 may simulate a terminal user to periodically send heartbeat short messages to all client systems, the client systems submit the heartbeat short messages to the routing heartbeat server in the client systems for processing after receiving the heartbeat short messages, and the routing heartbeat server in the client systems responds to acknowledgement information (for example, ACK, OK or an extended status code).
Whether a fault a or b occurs, the routing heartbeat server of the network node 1 cannot detect the response of the routing heartbeat short message of the client Y, and judges that the main route is abnormal, so that the routing switching of a service layer is performed on the industrial short message. As shown in fig. 4, if the routing heartbeat server of the network node 1 cannot detect the responses of the routing heartbeat messages of the client X and the client Y, it is determined that a failure a occurs, and the routing heartbeat server of the network node 1 performs route switching on both the client X and the client Y. As shown in fig. 5, if the routing heartbeat server of the network node 1 detects the response of the routing heartbeat short message of the client X but cannot detect the response of the routing heartbeat short message of the client Y, it determines that a failure b occurs, and performs routing switching only on the client Y.
In the embodiment, the routing heartbeat server is arranged in the industrial short message system, and the fault service route is determined through the heartbeat response message of the heartbeat message, so that the fault service route is replaced by the standby service route, the disaster recovery route switching of a service layer is realized, and the blind-spot-free fault link detection of the whole route is realized. Meanwhile, the technical scheme is realized in the existing network, hardware equipment is not required to be added, the existing network is slightly changed, only route heartbeat server software is required to be added, and therefore the implementation cost is low.
Preferably, in one embodiment, the heartbeat message may contain a specific character string, so that the network node preferentially processes the heartbeat message containing the specific character string.
For example, the content of the heartbeat short message may contain a specific character string. All network nodes through which the heartbeat short message passes can identify the content of the heartbeat short message, and the heartbeat short message containing the specific character string is processed with the highest priority, so that the heartbeat short message can be sent in priority.
By setting the specific character string in the heartbeat message, the heartbeat message can be transmitted preferentially, so that the existing fault can be detected as soon as possible in the network, and the delay of route switching is reduced.
Preferably, in one embodiment, heartbeat messages may be sent periodically or manually to determine the failed traffic route.
The heartbeat messages may be timed according to a preset event period, and the time period may be set to be timed to day, hour, minute, or second. Or manually to immediately detect whether the route is normal. And if the routing heartbeat server in the network node cannot receive the heartbeat response message within a period of time, performing routing switching of a service layer.
The above embodiments all take the route detection of the uplink as an example. It should be understood by those skilled in the art that, when detecting a failure in the network, a routing heartbeat server in the client system may also initiate downlink routing detection, send a heartbeat message to a routing heartbeat server in the network node, and determine whether a failure exists in the routing through a received heartbeat response message.
The routing system of one embodiment of the present invention is described below with reference to fig. 6.
Fig. 6 is a schematic structural diagram of a routing system according to an embodiment of the present invention. As shown in fig. 6, the routing system 60 of the present embodiment includes: a network node 602, a plurality of client systems 604, and a routing heartbeat server 606. The routing heartbeat server 606 is located within the network node as well as within a plurality of client systems.
The following describes a routing heartbeat server according to an embodiment of the present invention with reference to fig. 7.
Fig. 7 is a schematic structural diagram of a routing heartbeat server according to an embodiment of the present invention. As shown in fig. 7, the routing heartbeat server 606 of the present embodiment includes:
a heartbeat communication module 7062 configured to enable the routing heartbeat server at the network node to communicate with the routing heartbeat servers at the plurality of client systems respectively through heartbeat messages.
A failed traffic route determination module 7064 configured to determine a failed traffic route from a heartbeat response message of the heartbeat message.
A traffic route replacement module 7066 configured to replace the failed traffic route with the alternate traffic route.
In the embodiment, the routing heartbeat server is arranged in the industrial short message system, and the fault service route is determined through the heartbeat response message of the heartbeat message, so that the fault service route is replaced by the standby service route, the disaster recovery route switching of a service layer is realized, and the blind-spot-free fault link detection of the whole route is realized. Meanwhile, the technical scheme is realized in the existing network, hardware equipment is not required to be added, the existing network is slightly changed, only route heartbeat server software is required to be added, and therefore the implementation cost is low.
In one embodiment, the failed traffic routing determination module 7064 is configured to: a failed link in the failed traffic route is determined based on whether heartbeat response messages are received from routing heartbeat servers located at the plurality of client systems 504.
In one embodiment, the traffic routing replacement module 7066 is configured to: if a failed link exists in the route between the client system and the network node, the backup route between the client system and the network node is used for replacing the failed service route.
In one embodiment, the heartbeat message contains a specific string so that the network node preferentially processes heartbeat messages containing the specific string.
By setting the specific character string in the heartbeat message, the heartbeat message can be transmitted preferentially, so that the existing fault can be detected as soon as possible in the network, and the delay of route switching is reduced.
In one embodiment, the routing heartbeat server 506 is configured to: and sending heartbeat messages regularly or manually to determine the fault service route.
The heartbeat messages may be timed according to a preset event period, and the time period may be set to be timed to day, hour, minute, or second. Or manually to immediately detect whether the route is normal. And if the routing heartbeat server in the network node cannot receive the heartbeat response message within a period of time, performing routing switching of a service layer.
Fig. 8 is a schematic structural diagram of another embodiment of the route switching system of the present invention. As shown in fig. 8, the route switching system 80 of this embodiment includes: a memory 810 and a processor 820 coupled to the memory 810, the processor 820 being configured to execute the route switching method in any of the foregoing embodiments based on instructions stored in the memory 810.
Fig. 9 is a schematic structural diagram of a route switching system according to another embodiment of the present invention. As shown in fig. 9, the route switching system 90 of this embodiment includes: the memory 810 and the processor 820 may further include an input/output interface 930, a network interface 940, a storage interface 950, and the like. These interfaces 930, 940, 950 and the memory 810 and the processor 820 may be connected by a bus 950, for example. The input/output interface 930 provides a connection interface for input/output devices such as a display, a mouse, a keyboard, and a touch screen. The network interface 940 provides a connection interface for various networking devices. The storage interface 950 provides a connection interface for external storage devices such as an SD card and a usb disk.
The present invention also includes a computer readable storage medium having stored thereon computer instructions which, when executed by a processor, implement the method of route switching in any of the foregoing embodiments.
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 non-transitory storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
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.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like that fall within the spirit and principle of the present invention are intended to be included therein.
Claims (8)
1. A method for switching a route, comprising:
routing heartbeat servers are respectively arranged in a network node and a plurality of client systems;
the routing heartbeat server positioned at the network node is respectively communicated with the routing heartbeat servers positioned at the plurality of client systems through heartbeat messages, and a fault link in the fault service route is determined according to whether heartbeat response messages of the routing heartbeat servers positioned at the plurality of client systems are received or not;
if a fault link exists in the route from the first client system to the network node and a fault link does not exist in the route from the second client system to the network node, the standby route from the first client system to the network node is used for replacing the fault service route, and the route from the second client system to the network node is unchanged.
2. The route switching method according to claim 1, wherein the heartbeat message contains a specific character string, so that the network node preferentially processes the heartbeat message containing the specific character string.
3. The route switching method according to claim 1, wherein heartbeat messages are sent periodically or manually to determine the failed traffic route.
4. A route switching system, comprising: the system comprises a network node, a plurality of client systems and a routing heartbeat server;
the routing heartbeat server is arranged in a network node and a plurality of client systems;
the routing heartbeat server includes:
a heartbeat communication module configured to enable a routing heartbeat server located at a network node to communicate with routing heartbeat servers located at a plurality of client systems, respectively, via heartbeat messages,
a failure service route determining module configured to determine a failure link in a failure service route according to whether a heartbeat response message of a route heartbeat server located in a plurality of client systems is received;
and the service route replacing module is configured to replace the fault service route by using a standby route between the first client system and the network node if a fault link exists in the route between the first client system and the network node and a fault link does not exist in the route between the second client system and the network node, and the route between the second client system and the network node is unchanged.
5. The route switching system according to claim 4, wherein the heartbeat message contains a specific character string, so that the network node preferentially processes the heartbeat message containing the specific character string.
6. The route switching system of claim 4, wherein the route heartbeat server is configured to: and sending heartbeat messages regularly or manually to determine the fault service route.
7. A route switching system, comprising:
a memory; and
a processor coupled to the memory, the processor configured to perform the route switching method of any of claims 1 to 3 based on instructions stored in the memory.
8. A computer-readable storage medium storing computer instructions which, when executed by a processor, implement the route switching method of any one of claims 1 to 3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710518731.9A CN109219105B (en) | 2017-06-30 | 2017-06-30 | Route switching method and route switching system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710518731.9A CN109219105B (en) | 2017-06-30 | 2017-06-30 | Route switching method and route switching system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109219105A CN109219105A (en) | 2019-01-15 |
| CN109219105B true CN109219105B (en) | 2020-11-27 |
Family
ID=64976876
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710518731.9A Active CN109219105B (en) | 2017-06-30 | 2017-06-30 | Route switching method and route switching system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109219105B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111371680B (en) * | 2020-03-04 | 2022-04-29 | 深信服科技股份有限公司 | Route management method, device, equipment and storage medium for dual-computer hot standby |
| CN113794507B (en) * | 2021-09-10 | 2024-01-09 | 上海卫星工程研究所 | Autonomous fault processing method and system based on-orbit route switching |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101860492A (en) * | 2010-06-28 | 2010-10-13 | 中兴通讯股份有限公司 | Quick switching method, device and system |
| CN102308536A (en) * | 2009-02-09 | 2012-01-04 | 日本电气株式会社 | Communication system, communication unit, control unit, and controlling method |
| CN103036701A (en) * | 2012-04-01 | 2013-04-10 | 浙江宇视科技有限公司 | Network segment crossing N+1 backup method and network segment crossing N+1 backup device |
| CN105634832A (en) * | 2016-03-16 | 2016-06-01 | 浙江宇视科技有限公司 | Server backup method and device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9325622B2 (en) * | 2013-12-03 | 2016-04-26 | International Business Machines Corporation | Autonomic traffic load balancing in link aggregation groups |
-
2017
- 2017-06-30 CN CN201710518731.9A patent/CN109219105B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102308536A (en) * | 2009-02-09 | 2012-01-04 | 日本电气株式会社 | Communication system, communication unit, control unit, and controlling method |
| CN101860492A (en) * | 2010-06-28 | 2010-10-13 | 中兴通讯股份有限公司 | Quick switching method, device and system |
| CN103036701A (en) * | 2012-04-01 | 2013-04-10 | 浙江宇视科技有限公司 | Network segment crossing N+1 backup method and network segment crossing N+1 backup device |
| CN105634832A (en) * | 2016-03-16 | 2016-06-01 | 浙江宇视科技有限公司 | Server backup method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109219105A (en) | 2019-01-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10462027B2 (en) | Cloud network stability | |
| CN106487486B (en) | Service processing method and data center system | |
| JP6431197B2 (en) | Snapshot processing methods and associated devices | |
| CN109921942B (en) | Cloud platform switching control method, device and system and electronic equipment | |
| US10102088B2 (en) | Cluster system, server device, cluster system management method, and computer-readable recording medium | |
| CN110457176A (en) | For the monitoring method of distributed system, device, storage medium and electronic equipment | |
| CN111130821B (en) | Power failure alarm method, processing method and device | |
| CN107688547B (en) | Method and system for switching between main controller and standby controller | |
| CN112527567A (en) | System disaster tolerance method, device, equipment and storage medium | |
| CN109219105B (en) | Route switching method and route switching system | |
| CN111565133B (en) | Private line switching method and device, electronic equipment and computer readable storage medium | |
| WO2023185802A1 (en) | Data processing method and apparatus | |
| CN106878096B (en) | VNF state detection notification method, device and system | |
| CN111083049A (en) | User table item recovery method and device, electronic equipment and storage medium | |
| CN112615700B (en) | Data sending method, gateway, system, electronic equipment and readable storage medium | |
| WO2014050493A1 (en) | Backup device, main device, redundancy configuration system, and load dispersion method | |
| CN112468342B (en) | Fault tolerant design of clock synchronization system | |
| CN103414591A (en) | Method and system for fast converging when port failure is recovered | |
| CN114679295B (en) | Firewall security configuration method and device | |
| CN106326042B (en) | Method and device for determining running state | |
| CN114091909A (en) | Collaborative development method, system, device and electronic equipment | |
| CN113238893A (en) | Disaster recovery system, method, computer device and medium for multiple data centers | |
| US10740199B2 (en) | Controlling device, controlling method, and fault tolerant apparatus | |
| CN105306256B (en) | A kind of two-node cluster hot backup implementation method based on VxWorks equipment | |
| JP2017183905A (en) | Communication device, method for recovering from communication failure, and program for recovering from communication failure |
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 |