CN109885334B - Version compatible system and message sending and receiving method - Google Patents
Version compatible system and message sending and receiving method Download PDFInfo
- Publication number
- CN109885334B CN109885334B CN201811644514.5A CN201811644514A CN109885334B CN 109885334 B CN109885334 B CN 109885334B CN 201811644514 A CN201811644514 A CN 201811644514A CN 109885334 B CN109885334 B CN 109885334B
- Authority
- CN
- China
- Prior art keywords
- message
- version
- version container
- low
- container
- 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
Landscapes
- Information Transfer Between Computers (AREA)
- Computer And Data Communications (AREA)
Abstract
The embodiment of the invention provides a version compatible system and a message sending and receiving method, wherein a connecting component is respectively registered in a high version container and a low version container; the connecting component is used for realizing message transmission between the high-version container and the low-version container. According to the connecting component, the message sending method, the message receiving method and the version compatible system, message transmission is carried out between the high-version container and the low-version container through the connecting component, the high-version container can normally receive and send ActiveMQ messages on the premise of not influencing the existing code structure, third-party service is not required to be introduced, extra project system dependence is not increased, the problem of message drop caused by system problems or network problems is solved, the reliability is high, and the maintenance cost is low.
Description
Technical Field
The embodiment of the invention relates to the technical field of software version compatibility, in particular to a connecting component, a message sending and receiving method and a version compatibility system.
Background
Existing project systems may need to process messages based on twice-encapsulated ActiveMQ message middleware, while accessing ActiveMQ requires the introduction of twice-encapsulated jar packages. The jar packet is realized based on Spring 3. When the item upgraded to Spring4 needs to access the ActiveMQ, the item cannot be directly accessed due to the inconsistent Spring versions, and needs to be accessed after being converted by means of a third-party service.
At present, a method for solving the problem that ActiveMQ cannot be accessed due to the Spring version problem is to specially build a third-party service access ActiveMQ message middleware realized by Spring 3. When the upgraded project needs to receive the ActiveMQ message, the upgraded project is answered by a third-party service, and then converted into a mode that the upgraded project can accept and transmitted to the upgraded project; when the upgraded project needs to send the message, the message is sent to the third-party service, and then the message is sent after being converted by the third-party service.
The method leads to more project system dependence and increases the system complexity. In addition, in the process of third-party service transfer, messages may be dropped due to system problems or network problems, and reliability is low. Furthermore, depending on the development resources of the third party service, maintenance costs are increased.
Disclosure of Invention
The embodiment of the invention provides a connecting component, a message sending method, a message receiving method and a version compatible system, which are used for solving the problem that the existing Spring version is inconsistent and needs to be converted by means of a third-party service.
In a first aspect, an embodiment of the present invention provides a connection component, where the connection component is registered in the high version container and the low version container respectively;
the connecting component is used for realizing message transmission between the high-version container and the low-version container.
In a second aspect, an embodiment of the present invention provides a method for sending a message based on a connection component as provided in the first aspect, including:
a first receiving step of receiving a message to be sent injected by a high-version container;
and a calling step of calling a low version container so that the message to be sent can be converted into an MQ message through the low version container and sent.
In a third aspect, an embodiment of the present invention provides a method for receiving a message based on a connection component as provided in the first aspect, including:
a second receiving step, receiving the event message transmitted by the low-version container; the event message is obtained by converting the MQ message based on a preset type after the low-version container receives the MQ message;
and a forwarding step of transmitting the event message to a high-version container.
In a fourth aspect, an embodiment of the present invention provides a message sending apparatus based on the connection component as provided in the first aspect, including:
the first receiving unit is used for receiving the message to be sent injected by the high-version container;
and the calling unit is used for calling the low-version container so that the message to be sent can be converted into an MQ message through the low-version container and sent.
In a fifth aspect, an embodiment of the present invention provides a message receiving apparatus based on the connection component as provided in the first aspect, including:
the second receiving unit is used for receiving the event message transmitted by the low-version container; the event message is obtained by converting the MQ message based on a preset type after the low-version container receives the MQ message;
a forwarding unit, configured to transmit the event message to a high version container.
In a sixth aspect, an embodiment of the present invention provides a version-compatible system, including a high-version container, a low-version container, and the connection component as provided in the first aspect.
In a seventh aspect, an embodiment of the present invention provides an electronic device, including a processor, a communication interface, a memory, and a bus, where the processor, the communication interface, and the memory complete communication with each other through the bus, and the processor may call a logic instruction in the memory to perform the steps of the method as provided in the second aspect or the third aspect.
In an eighth aspect, embodiments of the present invention provide a non-transitory computer readable storage medium, on which a computer program is stored, which when executed by a processor, implements the steps of the method as provided in the second or third aspect.
According to the connecting component, the message sending method, the message receiving method and the version compatible system, message transmission is carried out between the high-version container and the low-version container through the connecting component, the high-version container can normally receive and send the ActiveMQ messages on the premise that an existing code framework is not influenced, third-party service is not required to be introduced, extra project system dependence is not increased, the problem of message drop caused by system problems or network problems is solved, the reliability is high, and the maintenance cost is low.
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 some embodiments of the present invention, and those skilled in the art can also obtain other drawings according to the drawings without creative efforts.
Fig. 1 is a schematic view of a connection structure of a connection assembly according to an embodiment of the present invention;
fig. 2 is a schematic flowchart of a method for sending a message based on a connection component according to an embodiment of the present invention;
fig. 3 is a schematic flowchart of a message receiving method based on a connection component according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of a version compatible system according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a message sending apparatus based on a connection component according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of a message receiving apparatus based on a connection component according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, 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 some, but not all, embodiments of the present invention. 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.
Aiming at solving the problems of more system dependence, high system complexity, low reliability, high maintenance cost and the like of the method which cannot access the ActiveMQ due to the Spring version problem by accessing a third party service at present, the embodiment of the invention provides a connection component. Fig. 1 is a schematic diagram of a connection structure based on a connection component according to an embodiment of the present invention, as shown in fig. 1, a connection component 130 is respectively registered in a high version container 110 and a low version container 120; the connection component 130 is used to implement message transmission between the high version container 110 and the low version container 120.
In order to solve the problem that Spring in the project cannot directly access ActiveMQ message middleware, the high version container 110 in the embodiment of the present invention refers to a container of a Spring version incompatible with ActiveMQ, and the low version container 120 refers to a container of a Spring version compatible with ActiveMQ. The high version container 110 is independent of the low version container 120.
The message transmission is performed between the high version container 110 and the low version container 120 through the connection component 130. Here, the connection component 130 is registered in the high version container 110 so that a message that the high version container 110 needs to transmit can be acquired and the message can be transmitted to the high version container 110. In addition, the connection component 130 is also registered in the low version container 120, so that a message that needs to be transmitted by the low version container 120 can be acquired and the message can be transmitted to the low version container 120. The connection component 130 can transmit the messages that the high-version container 110 needs to transmit to the low-version container 120, convert the messages into MQ messages through the low-version container 120, and convert the MQ messages that the high-version container 110 needs to receive into a format that the high-version container 110 can support, and transmit the MQ messages to the high-version container 110 through the low-version container 120, so as to implement the compatibility of the high-version container 110 with ActiveMQ without accessing a third-party service.
The connection component provided by the embodiment of the invention enables the high-version container 110 to normally receive and send the ActiveMQ message by transmitting the message between the high-version container 110 and the low-version container 120 on the premise of not influencing the existing code architecture, does not need to introduce a third-party service, does not increase additional project system dependence, avoids the problem of message drop caused by system problems or network problems, and has strong reliability and low maintenance cost.
Based on the embodiment, the connecting component comprises a compatible service component and an event bus, and the event bus is injected into the compatible service component; the compatible service component is used for calling the low version container for the high version container; the event bus is used for realizing message transmission between the high-version container and the low-version container.
In particular, the compatible services component is used to invoke the low version container for the high version container. When the high-version container in the project needs to send the MQ message, the high-version container injects the message to be sent into the compatible service component, the compatible service component immediately acquires the component capable of converting the message to be sent into the MQ message from the low-version container, and reflects the interface of the component capable of converting the message to be sent into the MQ message, so that the message to be sent can be converted into the MQ message by the corresponding component in the low-version container and sent.
The event bus is used for realizing message transmission between the high-version container and the low-version container. When the high-version container in the project needs to receive the MQ message, the high-version container listens to the message corresponding to the event bus. The low-version container is directly connected with the ActiveMQ message middleware in an interfacing mode, and after the low-version container receives the MQ message, the MQ message is converted into a format which can be supported by the high-version container and is transmitted to the high-version container through the event bus.
Based on any one of the foregoing embodiments, fig. 2 is a schematic flowchart of a message sending method based on a connection component according to an embodiment of the present invention, and as shown in fig. 2, an execution main body of the message sending method is the connection component, and the message sending method includes:
Specifically, when the high-version container in the project needs to send MQ messages, the high-version container injects the messages to be sent into the compatible service components. Here, the message to be sent is a message in a format supported by the high-version container, and needs to be converted into an MQ message through the format and sent to ActiveMQ message middleware.
Specifically, after receiving the message to be sent injected by the high-version container, the compatible service component reflects the low-version container interface, so that the message to be sent can be converted into an MQ message through the low-version container and sent to the ActiveMQ message middleware through the low-version container.
According to the message sending method provided by the embodiment of the invention, the low-version container is called through the connecting component, so that the message to be sent can be converted into the MQ message to be sent, a third-party service is not required to be introduced, additional project system dependence is not increased, the problem of message drop caused by system problems or network problems is avoided, the reliability is high, and the maintenance cost is low.
Based on any of the above embodiments, step 220 specifically includes: selecting a corresponding sending component from the low-version container based on the type of the message to be sent; the sending component is invoked to enable the message to be sent to be converted to an MQ message and sent by the sending component.
Specifically, after the compatible service component receives the message to be sent injected into the high-version container, the compatible service component acquires the type of the message to be sent, and selects a sending component corresponding to the type from the low-version container according to the type of the message to be sent. Here, the sending component corresponding to the type has a function of converting the type of message to be sent into an MQ message. After the sending component corresponding to the type of the message to be sent is determined, the component interface is reflected, so that the message to be sent can be converted into an MQ message through the sending component corresponding to the type in the low-version container and sent to ActiveMQ message middleware.
Based on any of the foregoing embodiments, fig. 3 is a schematic flowchart of a message receiving method based on a connection component according to an embodiment of the present invention, and as shown in fig. 3, an execution main body of the message receiving method is the connection component, and the message receiving method includes:
In particular, the ActiveMQ message middleware interfaces directly with the low version container, the MQ messages issued by the ActiveMQ message middleware are first received by the low version container. And after the low-version container receives the MQ message, converting the MQ message into an event message and sending the event message to the connection component. Here, the event message is an MQ message of a preset type, and the preset type is a format type supported by a preset high-version container.
Specifically, after receiving the event message converted by the low version container, the event message is transmitted to the high version container, and the receiving and converting of the MQ message are completed.
According to the message receiving method provided by the embodiment of the invention, the MQ message converted by the low-version container is transmitted to the high-version container through the connecting component, a third-party service is not required to be introduced, additional project system dependence is not increased, the problem of message drop caused by system problems or network problems is avoided, the reliability is high, and the maintenance cost is low.
Based on any embodiment, the version compatible system comprises a high version container, a low version container and a connecting component.
According to any one of the above embodiments, in the system, the low-version container is constructed based on an xml configuration injection mode.
Specifically, in order to avoid that a component (bean) planned in the low-version container is automatically scanned and injected by the high-version container originally existing in the project, all beans in the low-version container are not added with @ Service annotation, and the method is realized by adopting an xml configuration injection mode.
Based on any of the above embodiments, fig. 4 is a schematic structural diagram of a version compatible system provided in an embodiment of the present invention, and as shown in fig. 4, the version compatible system includes a high version container 110, a low version container 120, and a connection component 130. The high-version container 110 is a Spring4 container applied in the project, and Spring4 cannot be directly accessed to the ActiveMQ. The low version container 120 is a Spring3 container, and Spring3 can directly access the ActiveMQ. The connection component 130 includes a compatible service component DyMQService for maintaining separate low-version containers 120 and an event bus EventBus for communicating messages in the high-version and low- version containers 110 and 120. The DyMQService and EventBus are registered in the high-version container 110 and the low-version container 120, respectively. In addition, eventBus was injected into the DyMQService.
Wherein, the low version container 120 is a Spring3 container started by ClassPathXmlApplicationContext based on the jms jar packet of the introduced Spring3 at the construction stage of the DyMQService. In order to avoid that beans planned in the low-version container 120 are automatically scan-injected by the high-version container 110, all beans in the low-version container 120 do not add @ Service annotation, and the method is implemented by adopting xml configuration injection.
When the signschedule services in the high-version container 110 in the project need to send messages, the messages to be sent are injected into the dymqservices service to call interfaces of corresponding messages. The DyMQService acquires a corresponding bean from the low-version container 120 according to the type of the message to be sent, and reflects an interface for executing message sending. The message to be sent is converted to an MQ message by shouhouschedule sender in the low-version container 120 and sent to an ActiveMQ middleware. The entire process of sending messages is synchronous, and if the sending is not successful, an exception is thrown.
And when the SynCaseRiskMarkerEventHandler service in the high-version container 110 in the project needs to receive the message, monitoring an event message corresponding to EventBus. In the low version container 120, the actual ActiveMQ message snoops are registered by the HouseRiskListener. After the low version container 120 receives the MQ message, the MQ message is encapsulated into an event message of a preset type and is delivered to the high version container 110 through eventBus. The syncaseriskmakereventhandler in the high-version container 110 receives the corresponding event message for subsequent processing. In the process of receiving the message, event bus processing events are synchronous, event bus receiving messages are asynchronous, and event buses realize the function of a buffer queue.
The version compatible system provided by the embodiment of the invention transmits the messages between the high-version container 110 and the low-version container 120 through the connecting component 130, so that the high-version container 110 can normally receive and send the ActiveMQ messages on the premise of not influencing the conventional code structure, a third-party service is not required to be introduced, additional project system dependence is not increased, the problem of message drop caused by system problems or network problems is avoided, the reliability is high, and the maintenance cost is low.
Based on any of the above embodiments, fig. 5 is a schematic structural diagram of a message sending apparatus based on a connection component according to an embodiment of the present invention, as shown in fig. 5, the message sending apparatus includes a first receiving unit 510 and a calling unit 520;
the first receiving unit 510 is configured to receive a message to be sent, which is injected by a high-version container;
the invoking unit 520 is configured to invoke a low version container, so that the message to be sent can be converted into an MQ message through the low version container and sent.
The message sending device based on the connection component provided by the embodiment of the invention calls the low-version container through the connection component, so that the message to be sent can be converted into the MQ message to be sent, a third-party service is not required to be introduced, additional project system dependence is not increased, the problem of message drop caused by system problems or network problems is avoided, the reliability is high, and the maintenance cost is low.
Based on any of the above embodiments, the invoking unit 520 is specifically configured to: selecting a corresponding sending component from the low-version container based on the type of the message to be sent; and calling the sending component to enable the message to be sent to be converted into an MQ message through the sending component and sent.
Based on any of the foregoing embodiments, fig. 6 is a schematic structural diagram of a message receiving apparatus based on a connection component according to an embodiment of the present invention, and as shown in fig. 6, the message receiving apparatus includes a second receiving unit 610 and a forwarding unit 620;
wherein, the second receiving unit 610 receives the event message transmitted by the low version container; the event message is obtained by converting the MQ message based on a preset type after the low-version container receives the MQ message;
the forwarding unit 620 is configured to transmit the event message to the high version container.
The message receiving device based on the connecting component provided by the embodiment of the invention transmits the MQ message converted by the low-version container to the high-version container through the connecting component without introducing a third-party service or adding additional project system dependence, thereby avoiding the problem of message drop caused by system problems or network problems, and having strong reliability and low maintenance cost.
Fig. 7 is a schematic entity structure diagram of an electronic device according to an embodiment of the present invention, and as shown in fig. 7, the electronic device may include: a processor (processor) 701, a communication Interface (Communications Interface) 702, a memory (memory) 703 and a communication bus 704, wherein the processor 701, the communication Interface 702 and the memory 703 complete communication with each other through the communication bus 704. The processor 701 may call a computer program stored in the memory 703 and executable on the processor 701 to execute the connected component-based message sending method provided by the foregoing embodiments, for example, including: receiving a message to be sent injected by a high-version container; and calling a low-version container to enable the message to be sent to be converted into an MQ message through the low-version container and sent.
In addition, the processor 701 may call a computer program stored on the memory 703 and executable on the processor 701 to execute the connected component-based message receiving method provided by the foregoing embodiments, for example, including: receiving an event message transmitted by a low-version container; the event message is obtained by converting the MQ message based on a preset type after the low-version container receives the MQ message; transmitting the event message to a high version container.
In addition, the logic instructions in the memory 703 can be implemented in the form of software functional units and stored in a computer readable storage medium when the software functional units are sold or used as independent products. Based on such understanding, the technical solutions of the embodiments of the present invention may be substantially or partially contributed to by the prior art, or may be embodied in a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to perform all or part of the steps of the methods described in the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
Embodiments of the present invention further provide a non-transitory computer-readable storage medium, on which a computer program is stored, where the computer program is implemented to, when executed by a processor, perform the connected component-based message sending method provided in the foregoing embodiments, for example, including: receiving a message to be sent injected by a high-version container; and calling a low-version container to enable the message to be sent to be converted into an MQ message through the low-version container and sent.
Embodiments of the present invention further provide a non-transitory computer-readable storage medium, on which a computer program is stored, where the computer program is implemented to, when executed by a processor, execute the message receiving method based on the connection component provided in the foregoing embodiments, for example, including: receiving an event message transmitted by a low-version container; the event message is obtained by converting the MQ message based on a preset type after the low-version container receives the MQ message; transmitting the event message to a high version container.
The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware. Based on the understanding, the above technical solutions substantially or otherwise contributing to the prior art may be embodied in the form of a software product, which may be stored in a computer-readable storage medium, such as ROM/RAM, magnetic disk, optical disk, etc., and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method according to the various embodiments or some parts of the embodiments.
Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.
Claims (8)
1. A version compatible system comprising a high version container, a low version container, and a connection component;
the connection component is respectively registered in the high version container and the low version container; wherein, the high-version container is a Spring version container incompatible with ActiveMQ, and the low-version container is a Spring version container compatible with ActiveMQ;
the connecting component is used for realizing message transmission between the high-version container and the low-version container;
the connection component comprises a compatible service component, and the compatible service component is used for acquiring a component capable of converting messages from the low version container based on messages to be transmitted, so that the messages to be transmitted are converted into MQ messages by corresponding components in the low version container, wherein the messages to be transmitted are injected into the compatible service component by the high version container;
the connection component further comprises an event bus that injects into the compatible service component; the event bus is used for realizing message transmission between the high-version container and the low-version container.
2. A message transmission method based on the version compatible system of claim 1, comprising:
a first receiving step of receiving a message to be sent injected by a high-version container;
and calling, based on the message to be sent, obtaining a component capable of converting the message from a low-version container, so that the message to be sent can be converted into an MQ message through the low-version container and sent.
3. The message sending method according to claim 2, wherein the invoking step specifically comprises:
selecting a corresponding sending component from the low-version container based on the type of the message to be sent;
and calling the sending component to enable the message to be sent to be converted into an MQ message through the sending component and sent.
4. A message receiving method based on the version compatible system of claim 1, comprising:
a second receiving step, receiving the event message transmitted by the low-version container; the event message is obtained by converting the MQ message based on a preset type after the low-version container receives the MQ message;
and a forwarding step of transmitting the event message to a high-version container.
5. A message transmission apparatus based on the version compatible system according to claim 1, comprising:
the first receiving unit is used for receiving the message to be sent injected by the high-version container;
and the calling unit is used for acquiring a component capable of converting the message from the low-version container based on the message to be sent, so that the message to be sent can be converted into an MQ message through the low-version container and sent.
6. A message receiving apparatus based on the version compatible system of claim 1, comprising:
the second receiving unit is used for receiving the event message transmitted by the low-version container; the event message is obtained by converting the MQ message based on a preset type after the low-version container receives the MQ message;
and the forwarding unit is used for transmitting the event message to the high-version container.
7. An electronic device, comprising a processor, a communication interface, a memory and a bus, wherein the processor, the communication interface, the memory communicate with each other via the bus, and the processor invokes logic instructions in the memory to perform the method of any of claims 2 to 4.
8. A non-transitory computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 2 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811644514.5A CN109885334B (en) | 2018-12-30 | 2018-12-30 | Version compatible system and message sending and receiving method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811644514.5A CN109885334B (en) | 2018-12-30 | 2018-12-30 | Version compatible system and message sending and receiving method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109885334A CN109885334A (en) | 2019-06-14 |
| CN109885334B true CN109885334B (en) | 2022-10-04 |
Family
ID=66925429
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811644514.5A Active CN109885334B (en) | 2018-12-30 | 2018-12-30 | Version compatible system and message sending and receiving method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109885334B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111131425B (en) * | 2019-12-18 | 2022-08-30 | 东软集团股份有限公司 | Distributed system and communication method for distributed system |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105656947A (en) * | 2016-03-30 | 2016-06-08 | 深圳市金证科技股份有限公司 | Method, device and system for interaction between transaction middleware and third-party system |
| CN107154931A (en) * | 2017-03-31 | 2017-09-12 | 北京奇艺世纪科技有限公司 | A kind of compatible method and device of client release |
| CN107783849A (en) * | 2017-09-27 | 2018-03-09 | 武汉斗鱼网络科技有限公司 | Event-handling method and client |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8855601B2 (en) * | 2009-02-17 | 2014-10-07 | Lookout, Inc. | System and method for remotely-initiated audio communication |
-
2018
- 2018-12-30 CN CN201811644514.5A patent/CN109885334B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105656947A (en) * | 2016-03-30 | 2016-06-08 | 深圳市金证科技股份有限公司 | Method, device and system for interaction between transaction middleware and third-party system |
| CN107154931A (en) * | 2017-03-31 | 2017-09-12 | 北京奇艺世纪科技有限公司 | A kind of compatible method and device of client release |
| CN107783849A (en) * | 2017-09-27 | 2018-03-09 | 武汉斗鱼网络科技有限公司 | Event-handling method and client |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109885334A (en) | 2019-06-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2018059137A1 (en) | Internet of things terminal access device and method, and computer storage medium | |
| CN111813724B (en) | HIDL interface adapting system, method, corresponding equipment and storage medium | |
| JP5676655B2 (en) | Mobile broadband device and method for managing mobile broadband device | |
| CN114124451B (en) | Data processing method and system for Internet of things equipment and computer storage medium | |
| CN112596931B (en) | Cross-process communication method and device, electronic equipment and storage medium | |
| CN110138753B (en) | Distributed message service system, method, apparatus, and computer-readable storage medium | |
| CN113821363B (en) | Inter-process communication method and system | |
| CN102779071A (en) | Method, device and system for calling software interface | |
| CN109885334B (en) | Version compatible system and message sending and receiving method | |
| CN105165035A (en) | Transmission of multimedia message doubled with transmission of text message | |
| CN109408251B (en) | Message sending method and device and message receiving processing method and device | |
| CN106357654B (en) | Remote procedure calling method, device and communication system | |
| CN113791920A (en) | Dual-system communication method, device, electronic equipment and computer readable storage medium | |
| CN114356774A (en) | Target service test method, device, equipment and storage medium | |
| CN114816785A (en) | Service data processing method and device, electronic equipment and storage medium | |
| CN113806117A (en) | Dual system broadcasting method, apparatus, electronic device and computer readable storage medium | |
| CN117336346A (en) | IPPBX and PMS docking state conversion method, terminal equipment and medium | |
| CN115361263A (en) | AT command processing system and method based on embedded system | |
| WO2018133828A1 (en) | Data processing method and device utilized in client terminal | |
| CN114827916A (en) | Method and system for realizing cloud mobile phone short message function | |
| CN111371823B (en) | Method for client to access micro-service in non-WEB scene | |
| CN101631303A (en) | Method for processing interception, apparatus and system thereof | |
| CN110008032B (en) | Communication mode realization method and electronic equipment | |
| US8943125B2 (en) | Method of handling step execution result in software and application control management object | |
| CN117201577B (en) | Communication method and system of cross-platform API and SPI based on PISA |
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 |