CN107193663B - Service message processing method and device - Google Patents
Service message processing method and device Download PDFInfo
- Publication number
- CN107193663B CN107193663B CN201710003279.2A CN201710003279A CN107193663B CN 107193663 B CN107193663 B CN 107193663B CN 201710003279 A CN201710003279 A CN 201710003279A CN 107193663 B CN107193663 B CN 107193663B
- Authority
- CN
- China
- Prior art keywords
- message
- service
- micro
- type
- module
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/546—Message passing systems or structures, e.g. queues
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer And Data Communications (AREA)
- Multi Processors (AREA)
Abstract
The embodiment of the invention discloses a method and a device for processing a service message, which are applied to a micro-service module. The system where the micro service module is located further comprises a message scheduling module and a message bus. The method comprises the following steps: monitoring a service message issued on a message bus; when the message type of the service message is the message type subscribed by the micro-service module on the message bus, processing the service message according to the message type; and publishing the processed service message to a message bus so that when other micro-service modules subscribing to the message type of the processed service message hear the processed service message, the processed service message is processed, or when the message scheduling module determines that the processed service message is a result type message, the processed service message is pushed to a client. The embodiment of the invention can improve the fault tolerance and the expansibility of the micro-service application.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a method and an apparatus for processing a service message.
Background
The micro-service application is an application constructed by a group of micro-service modules, each micro-service module runs in an independent process, namely each micro-service module is independently deployed, and the micro-service modules can communicate with each other.
Currently, during a process of processing a service message, each micro service module in a micro service application mainly communicates with each other in a REST (Representational State Transfer) mode and an RPC (Remote Procedure Call Protocol) mode.
Take the example of communication between the micro service modules through REST. Supposing that the micro service application comprises 4 micro service modules, namely a micro service module 1, a micro service module 2, a micro service module 3 and a micro service module 4, respectively, it is supposed that after receiving a service message from a client, a routing device or a gateway needs to send the service message to the micro service module 1 for processing, the micro service module 1 determines that the micro service module 2, the micro service module 3 and the micro service module 4 need to perform cooperative processing according to the service message to feed back a final result to the client, the micro service module 2 needs the micro service module 4 to perform cooperative processing, and the micro service module 3 also needs the micro service module 4 to perform cooperative processing. Then, the micro service module 1 needs to interact with the micro service module 2 first, after the interaction, the micro service module 2 interacts with the micro service module 4, and the micro service module 2 feeds back the processing result after the interaction to the micro service module 1; the micro service module 1 interacts with the micro service module 3, after interaction, the micro service module 3 interacts with the micro service module 4, and the micro service module 3 feeds back the processing result after interaction to the micro service module 1; the micro-service module 1 finally interacts with the micro-service module 4, and the micro-service module 4 feeds back the processing result after interaction to the micro-service module 1; and finally, the micro-service module 1 feeds back a final result to the client according to the collected processing result. The 4 micro service modules are in communication interaction as shown in fig. 1.
Therefore, in the above service message processing process, when the micro service modules need to perform cooperative processing, the micro service modules are dependent on each other. Once one of the micro service modules is blocked, the whole service processing fails, and the fault tolerance is poor; and when the micro service application needs to add a micro service module (micro service extension) corresponding to a new function, other micro service modules may depend on the newly extended micro service module, and then the service logic of the micro service modules needs to be changed. With the expansion of the micro-service, the business logic also needs to be changed continuously, and the expansibility of the micro-service application is not strong.
Disclosure of Invention
The embodiment of the invention aims to provide a method and a device for processing service messages so as to improve the fault tolerance and the expansibility of micro-service application.
In order to achieve the above object, an embodiment of the present invention discloses a method for processing a service message, which is applied to a micro service module, wherein a system in which the micro service module is located further includes a message scheduling module and a message bus, and the method includes:
monitoring a service message issued on the message bus, wherein the service message is sent to the message scheduling module by a client and issued to the message bus by the message scheduling module, or issued to the message bus by other micro-service modules in the system;
when the message type of the service message is the message type subscribed by the micro-service module on the message bus, processing the service message according to the message type;
and publishing the processed service message to the message bus so as to process the processed service message when other micro-service modules subscribing to the message type of the processed service message monitor the processed service message, or pushing the processed service message to the client when the message scheduling module determines that the processed service message is a result type message.
In order to achieve the above object, an embodiment of the present invention discloses a service message processing apparatus, which is applied to a micro service module, wherein a system in which the micro service module is located further includes a message scheduling module and a message bus, and the apparatus includes: a listening unit, a processing unit and an issuing unit, wherein,
the monitoring unit is used for monitoring the service messages issued on the message bus, wherein the service messages are sent to the message scheduling module by a client and issued to the message bus by the message scheduling module, or issued to the message bus by other micro-service modules in the system;
the processing unit is used for processing the service message according to the message type when the message type of the service message is the message type subscribed by the micro-service module on the message bus;
the publishing unit is configured to publish the processed service message to the message bus, so that when other micro-service modules subscribing to the message type of the processed service message monitor the processed service message, the processed service message is processed, or when the message scheduling module determines that the processed service message is a result type message, the processed service message is pushed to the client.
According to the technical scheme, each micro-service module only processes the business messages of the message types subscribed by the micro-service module on the message bus. When a micro-service module is blocked, the business message processing of other micro-service modules which are not subscribed to the message type of the business message obtained by the micro-service module can not be influenced, the success of local/partial business processing can be ensured, the failure of the whole business processing is avoided, and the fault tolerance of the micro-service application is improved. And when the micro service application expands the micro service module, the expanded micro service module only needs to subscribe the message type of the service message from the message bus, and when the message bus has the service message of the message type subscribed by the expanded micro service module, the service message is processed without modifying the service logics of all other micro service modules or only modifying the service logics of a few micro service modules, so that the expansibility of the micro service application is improved.
Of course, it is not necessary for any product or method of practicing the invention to achieve all of the above-described advantages at the same time.
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, 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 the drawings without creative efforts.
FIG. 1 is a schematic diagram of communication interaction of a micro service module provided in the prior art;
fig. 2 is a schematic structural diagram of a system in which a micro service module according to an embodiment of the present invention is located;
fig. 3 is a schematic flowchart of a method for processing a service message according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of a service message processing apparatus according to an 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. 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.
In order to solve the problem of the prior art, embodiments of the present invention provide a method and an apparatus for processing a service message. First, a method for processing a service message according to an embodiment of the present invention is described below.
It should be noted that the method and apparatus for processing a service message provided in the embodiments of the present invention are preferably applied to a micro service module, where a system in which the micro service module is located further includes a message scheduling module and a message bus. Fig. 2 shows a structure of a system in which the micro service module is located, and fig. 2 is a schematic structural diagram of the system in which the micro service module is located according to an embodiment of the present invention. The system where the micro-service module is located comprises: a message scheduling module 201, a plurality of micro-service modules (e.g., micro-service module 1, micro-service module 2, micro-service module 3 … … micro-service module N), and a message bus 202.
Fig. 3 is a schematic flowchart of a method for processing a service message according to an embodiment of the present invention; the method can comprise the following steps:
s301: and monitoring the service messages issued on the message bus.
The service message is sent to the message scheduling module by the client, and is issued to the message bus by the message scheduling module, or is issued to the message bus by other micro-service modules in the system.
In practical application, the service messages issued on the Message bus are monitored, and the service messages issued on the Message bus can be monitored through an Advanced Message Queuing Protocol (AMQP).
S302: and when the message type of the service message is the message type subscribed by the micro-service module on the message bus, processing the service message according to the message type.
In practical application, the service message is processed according to the message type, and when it is determined that other micro-service modules do not need to perform cooperative processing according to the message type, the service message is processed to obtain a corresponding result type message; when determining that other micro-service modules need to perform cooperative processing according to the message type, determining other micro-service modules needing to perform cooperative processing; constructing a service message of which the message type is the message type subscribed by the determined micro-service module; processing the service message to obtain a corresponding result type message; and taking the constructed service message and the result type message as the service message obtained after processing.
S303: and publishing the processed service message to the message bus so as to process the processed service message when other micro-service modules subscribing to the message type of the processed service message monitor the processed service message, or pushing the processed service message to the client when the message scheduling module determines that the processed service message is a result type message.
For example, it is assumed that the system in which the micro service module shown in fig. 2 is located includes 4 micro service modules, which are micro service module 1, micro service module 2, micro service module 3, and micro service module 4. In this case, the micro service module 1, the micro service module 2, the micro service module 3, and the micro service module 4 may subscribe to the message bus 202 for the message type of the service message processed by each module, assuming that the service of the micro service module 1 needs to be assisted by the micro service module 2 and the micro service module 3, and the services of the micro service module 2 and the micro service module 3 need to be assisted by the micro service module 4.
It should be noted that after the micro service module 1 processes the service message that needs to be processed, the service message that has the message type that needs to be processed by the micro service module 2 and the micro service module 3 is included in the obtained service message, and after the micro service module 2 and the micro service module 3 process the service message that needs to be processed, the service message that has the message type that needs to be processed by the micro service module 4 is included in the obtained service message.
The following takes the micro service module 1, the micro service module 2, the micro service module 3, and the micro service module 4 as an example to describe the above service message processing flow in detail.
First, the message scheduling module 201 receives a service message 1 sent by a client, and publishes the service message 1 onto the message bus 202. The service message 1 carries the client identifier and the service identifier corresponding to the service message 1, so that the message scheduling module 201 sends the result type message to the corresponding client according to the client identifier and the service identifier when it subsequently monitors that the result type message exists on the message bus 202.
Next, the micro service module 1 monitors that a service message 1 which needs to be processed by itself is issued on the message bus 202 (the message type of the service message 1 needs to be processed by the micro service module 1), processes the service message 1 to obtain a result-like message 1.0, a service message 2 (the message is constructed when the micro service module 1 determines that the micro service module 2 needs to perform cooperative processing according to the message type of the service message 1) and a service message 3 (the message is constructed when the micro service module 1 determines that the micro service module 3 needs to perform cooperative processing according to the message type of the service message 1), and issues the result-like message 1.0, the service message 2 and the service message 3 on the message bus 202.
Then, the message scheduling module 201 monitors that the result type message 1.0 is issued on the message bus 202, and sends the result type message 1.0 to the client.
The micro service module 2 monitors that the message bus 202 issues a service message 2 which needs to be processed by itself (the message type of the service message 2 needs to be processed by the micro service module 2), processes the service message 2 to obtain a result type message 2.0 and a service message 4 (the message is constructed when the micro service module 2 determines that the micro service module 4 needs to perform cooperative processing according to the message type of the service message 2), and issues the result type message 2.0 and the service message 4 to the message bus 202.
The micro-service module 3 monitors that the message bus 202 issues the service message 3 which needs to be processed by itself (the message type of the service message 3 needs to be processed by the micro-service module 3), processes the service message 3 to obtain a result type message 3.0 and a service message 5 (the message is constructed when the micro-service module 3 determines that the micro-service module 4 needs to perform cooperative processing according to the message type of the service message 3), and issues the result type message 3.0 and the service message 5 to the message bus 202.
The subsequent message scheduling module 201 will listen to the result type message 2.0 and the result type message 3.0 issued on the message bus 202 and send them to the client.
The microservice module 4 monitors that the message bus 202 issues the service message 4 and the service message 5 which need to be processed by the microservice module 4 (the message types of the two service messages are the types which need to be processed by the microservice module 4), processes the service message 4 and the service message 5 to obtain a result type message 4.0 and a result type message 5.0, and issues the result type message 4.0 and the result type message 5.0 to the message bus 202.
Finally, the message scheduling module 201 listens to the message bus 202, where the result type message 4.0 and the result type message 5.0 are issued, and sends them to the client.
By applying the embodiment shown in fig. 3 of the present invention, each microservice module only processes the service messages of the message types subscribed by the microservice module itself on the message bus. When a micro-service module is blocked, the business message processing of other micro-service modules which are not subscribed to the message type of the business message obtained by the micro-service module can not be influenced, the success of local/partial business processing can be ensured, the failure of the whole business processing is avoided, and the fault tolerance of the micro-service application is improved. And when the micro service application expands the micro service module, the expanded micro service module only needs to subscribe the message type of the service message from the message bus, and when the message bus has the service message of the message type subscribed by the expanded micro service module, the service message is processed without modifying the service logics of all other micro service modules or only modifying the service logics of a few micro service modules, so that the expansibility of the micro service application is improved.
Corresponding to the implementation of the method, the embodiment of the invention also provides a service message processing device.
Fig. 4 is a schematic structural diagram of a service message processing apparatus according to an embodiment of the present invention, where the apparatus may include: a listening unit 401, a processing unit 402 and an issuing unit 403, wherein,
a monitoring unit 401, configured to monitor a service message issued on the message bus, where the service message is sent to the message scheduling module by a client, and is issued to the message bus by the message scheduling module, or is issued to the message bus by another micro-service module in the system;
the monitoring unit 401 provided in the embodiment of the present invention may be specifically configured to:
and monitoring the service messages issued on the message bus through an advanced message queue protocol.
A processing unit 402, configured to process the service message according to a message type subscribed by the microservice module on the message bus when the message type of the service message is the message type;
the processing unit 402 provided in the embodiment of the present invention may be specifically configured to:
and when the message type of the service message is the message type subscribed by the micro-service module on the message bus, processing the service message to obtain a corresponding result type message when determining that the cooperative processing of other micro-service modules is not needed according to the message type.
The processing unit 402 provided in the embodiment of the present invention may be further specifically configured to:
when determining that other micro-service modules need to perform cooperative processing according to the message type, determining other micro-service modules needing to perform cooperative processing;
constructing a service message of which the message type is the message type subscribed by the determined micro-service module;
processing the service message to obtain a corresponding result type message;
and taking the constructed service message and the result type message as the service message obtained after processing.
A publishing unit 403, configured to publish the processed service message to the message bus, so that when other micro-service modules subscribing to the message type of the processed service message monitor the processed service message, the processed service message is processed, or when the message scheduling module determines that the processed service message is a result type message, the processed service message is pushed to the client.
Preferably, in the embodiment of the present invention, when the monitoring unit monitors the service message that needs to be processed by the micro service module on the message bus, the monitoring unit may also issue the service message to the message bus in the micro service module, and after being processed by the corresponding processing unit, the monitoring unit issues the service message to the message bus through the message bus in the micro service module.
By applying the embodiment shown in fig. 4 of the present invention, each microservice module only processes the service messages of the message types subscribed by its microservice module on the message bus. When a micro-service module is blocked, the business message processing of other micro-service modules which are not subscribed to the message type of the business message obtained by the micro-service module can not be influenced, the success of local/partial business processing can be ensured, the failure of the whole business processing is avoided, and the fault tolerance of the micro-service application is improved. And when the micro service application expands the micro service module, the expanded micro service module only needs to subscribe the message type of the service message from the message bus, and when the message bus has the service message of the message type subscribed by the expanded micro service module, the service message is processed without modifying the service logics of all other micro service modules or only modifying the service logics of a few micro service modules, so that the expansibility of the micro service application is improved.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
All the embodiments in the present specification are described in a related manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments.
The above description is only for the preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention shall fall within the protection scope of the present invention.
Claims (6)
1. A business message processing method is applied to a micro-service module, a system where the micro-service module is located further comprises a message scheduling module and a message bus, and the method comprises the following steps:
monitoring a service message issued on the message bus, wherein the service message is sent to the message scheduling module by a client and issued to the message bus by the message scheduling module, or issued to the message bus by other micro-service modules in the system;
when the message type of the service message is the message type subscribed by the micro-service module on the message bus, processing the service message according to the message type;
the processed service message is published to the message bus, so that when other micro-service modules subscribing to the message type of the processed service message monitor the processed service message, the processed service message is processed, or when the message scheduling module determines that the processed service message is a result type message, the processed service message is pushed to the client;
the processing the service message according to the message type specifically includes:
when determining that other micro-service modules need to perform cooperative processing according to the message type, determining other micro-service modules needing to perform cooperative processing;
constructing a service message of which the message type is the message type subscribed by the determined micro-service module;
processing the service message to obtain a corresponding result type message;
and taking the constructed service message and the result type message as the service message obtained after processing.
2. The method according to claim 1, wherein the monitoring of the service messages issued on the message bus specifically includes:
and monitoring the service messages issued on the message bus through an advanced message queue protocol.
3. The method according to claim 1, wherein the processing the service message according to the message type specifically includes:
and processing the service message to obtain a corresponding result type message when determining that the cooperative processing of other micro service modules is not needed according to the message type.
4. A business message processing device is applied to a micro-service module, a system where the micro-service module is located further comprises a message scheduling module and a message bus, and the device comprises: a listening unit, a processing unit and an issuing unit, wherein,
the monitoring unit is used for monitoring the service messages issued on the message bus, wherein the service messages are sent to the message scheduling module by a client and issued to the message bus by the message scheduling module, or issued to the message bus by other micro-service modules in the system;
the processing unit is used for processing the service message according to the message type when the message type of the service message is the message type subscribed by the micro-service module on the message bus;
the publishing unit is configured to publish the processed service message to the message bus, so that when other micro-service modules subscribing to the message type of the processed service message monitor the processed service message, the processed service message is processed, or when the message scheduling module determines that the processed service message is a result type message, the processed service message is pushed to the client;
the processing unit is specifically configured to:
when determining that other micro-service modules need to perform cooperative processing according to the message type, determining other micro-service modules needing to perform cooperative processing;
constructing a service message of which the message type is the message type subscribed by the determined micro-service module;
processing the service message to obtain a corresponding result type message;
and taking the constructed service message and the result type message as the service message obtained after processing.
5. The apparatus according to claim 4, wherein the listening unit is specifically configured to:
and monitoring the service messages issued on the message bus through an advanced message queue protocol.
6. The apparatus according to claim 4, wherein the processing unit is specifically configured to:
and when the message type of the service message is the message type subscribed by the micro-service module on the message bus, processing the service message to obtain a corresponding result type message when determining that the cooperative processing of other micro-service modules is not needed according to the message type.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710003279.2A CN107193663B (en) | 2017-01-04 | 2017-01-04 | Service message processing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710003279.2A CN107193663B (en) | 2017-01-04 | 2017-01-04 | Service message processing method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107193663A CN107193663A (en) | 2017-09-22 |
| CN107193663B true CN107193663B (en) | 2021-03-12 |
Family
ID=59871586
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710003279.2A Active CN107193663B (en) | 2017-01-04 | 2017-01-04 | Service message processing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107193663B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110516897A (en) * | 2019-06-03 | 2019-11-29 | 武汉市自来水有限公司 | A kind of water utilities nested type micro services system |
| CN110442481B (en) * | 2019-07-10 | 2023-09-22 | 创新先进技术有限公司 | Service processing method, service component container and electronic equipment |
| CN111786886B (en) * | 2020-06-30 | 2022-09-06 | 京东科技控股股份有限公司 | Message processing method, device and system, electronic equipment and storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104954469A (en) * | 2015-06-19 | 2015-09-30 | 长沙廖氏软件科技有限公司 | Information exchange method for heterogeneous system |
| CN105162884A (en) * | 2015-09-25 | 2015-12-16 | 浪潮(北京)电子信息产业有限公司 | Cloud management platform based on micro-service architecture |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP6561555B2 (en) * | 2015-04-20 | 2019-08-21 | 富士通株式会社 | Information processing apparatus, operation verification method, and operation verification program |
-
2017
- 2017-01-04 CN CN201710003279.2A patent/CN107193663B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104954469A (en) * | 2015-06-19 | 2015-09-30 | 长沙廖氏软件科技有限公司 | Information exchange method for heterogeneous system |
| CN105162884A (en) * | 2015-09-25 | 2015-12-16 | 浪潮(北京)电子信息产业有限公司 | Cloud management platform based on micro-service architecture |
Non-Patent Citations (1)
| Title |
|---|
| "基于总线的消息服务(BBMS)的设计与实现";iteye_7030;《https://blog.csdn.net/iteye_7030/article/details/81956137》;20101026;第1-4页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107193663A (en) | 2017-09-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8914449B2 (en) | Push messaging platform with high scalability and high availability | |
| CN107193663B (en) | Service message processing method and device | |
| CN104077181A (en) | Status consistent maintaining method applicable to distributed task management system | |
| CN109783427A (en) | Implementation method, server and the system of coordinated type calendar prompting | |
| CN116420347A (en) | Method and apparatus for multicast service support in a time sensitive network | |
| CN106453539A (en) | Method and system for processing node registration notice | |
| CN111818131A (en) | Message pushing and scheduling system and method | |
| CN101437297B (en) | Method, apparatus and system for processing business | |
| CN109474471A (en) | The RTPS agreement accelerated method and its node and system of a kind of DDS network | |
| KR101272077B1 (en) | System and method for providing push service | |
| US9912782B2 (en) | Method and apparatus for recovery in a communication system employing redundancy | |
| CN110581828B (en) | Time synchronization method and device for private network cluster terminal | |
| CN103209213A (en) | Data transmission method and system for data subscription | |
| EP3723393A1 (en) | Method, device and system for transmitting multicast group information | |
| KR101407597B1 (en) | System and method for providing push service | |
| CN107423131B (en) | Sharing method and server | |
| CN105306350A (en) | Message interaction method, device and system | |
| CN105049255A (en) | Net element data synchronization method and device thereof | |
| CN110635986B (en) | Network access method and equipment | |
| CN108989467B (en) | Centralized addressing method | |
| CN112437146A (en) | Equipment state synchronization method, device and system | |
| WO2020015606A1 (en) | Communication method, device and system | |
| CN104753747A (en) | Gateway and device connecting method and device and gateway device | |
| CN114884966B (en) | Subway scheduling server system adopting distributed software and implementation method | |
| CN106992889B (en) | Multi-server switching method and system |
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 |