CN115454667A - Concurrent remote calling system and method based on message queue - Google Patents
Concurrent remote calling system and method based on message queue Download PDFInfo
- Publication number
- CN115454667A CN115454667A CN202211051281.4A CN202211051281A CN115454667A CN 115454667 A CN115454667 A CN 115454667A CN 202211051281 A CN202211051281 A CN 202211051281A CN 115454667 A CN115454667 A CN 115454667A
- Authority
- CN
- China
- Prior art keywords
- message
- calling
- module
- callback
- call
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 43
- 238000006243 chemical reaction Methods 0.000 claims abstract description 29
- 238000012545 processing Methods 0.000 claims abstract description 8
- 238000004891 communication Methods 0.000 claims abstract description 7
- 238000012544 monitoring process Methods 0.000 claims abstract description 7
- 230000006870 function Effects 0.000 claims description 42
- 230000008569 process Effects 0.000 claims description 19
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
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/547—Remote procedure calls [RPC]; Web services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/547—Messaging middleware
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/548—Queue
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Telephonic Communication Services (AREA)
Abstract
The invention discloses a concurrent remote call system and a method based on a message queue, belonging to the technical field of the message queue, aiming at solving the technical problem that how to ensure that an RPC system can realize multithread concurrent processing and call both sides decoupling, the adopted technical scheme is as follows: the system comprises a message middleware arranged between RPC units of a calling party and a called party, wherein the message middleware is used for calling communication channels of the calling party and the called party, temporarily storing and managing messages and decoupling the two parties receiving and transmitting the messages; the RPC unit comprises a callback registration module, a call conversion module, a message distribution module and a message receiving module; the callback registration module is used for recording callback information of a calling party; the calling conversion module is used for converting calling information into a message; the message distribution module is used for distributing the received message to a target thread; the message receiving module is used for monitoring a message queue in the message middleware and receiving messages.
Description
Technical Field
The invention relates to the technical field of message queues, in particular to a concurrent remote call system and a concurrent remote call method based on a message queue.
Background
In recent years, distributed systems have been increasingly used due to the rapid development of the internet. Since the whole system is composed of a plurality of distributed modules, a service often runs through a plurality of modules in the system, and the modules need to have the capability of mutual calling. Remote Procedure Call (RPC) systems are generated as they are.
The conventional RPC system has the following disadvantages:
(1) the traffic cannot be serialized: the callee needs to start an independent processing thread for each concurrent call, and in a scenario of high concurrency, the callee may crash because too many threads are started.
(2) Caller and callee are highly coupled: when RPC calling is carried out, if the called party is off-line or the network is interrupted, the RPC calling cannot be carried out, and the service fails as a whole.
Therefore, how to enable the RPC system to realize both multithreading concurrent processing and call both sides decoupling is a technical problem to be solved urgently at present.
Patent document No. CN112685190a discloses a synchronous calling method, system, computer device and storage medium based on message queue, which includes sending the current message to a server, and locking the current thread according to the message ID; receiving a back packet message sent by a server; merging the back packet message with the current message to obtain a merged message; and acquiring the message ID corresponding to the repackaging message and the receiving time of the repackaging message, and performing corresponding target operation according to the time interval between the receiving time of the repackaging message and the sending time corresponding to the current message. Although the technical scheme uses the message queue to realize the serialization of the RPC, the called party can finish the RPC calling by using a single thread; however, the technical scheme limits the concurrency performance of the called party and has the problem of coupling of the two parties.
Disclosure of Invention
The technical task of the invention is to provide a concurrent remote call system and a method based on a message queue to solve the problem of how to enable an RPC system to realize both multithread concurrent processing and call decoupling of both parties.
The technical task of the invention is realized in the following way, the concurrent remote call system based on the message queue comprises a message middleware arranged between RPC units of a calling party and a called party, wherein the message middleware is used for calling communication channels of the two parties, temporarily storing and managing messages and decoupling the two parties receiving and transmitting the messages;
the RPC unit comprises a callback registration module, a call conversion module, a message distribution module and a message receiving module;
the callback registration module is used for recording callback information of a calling party;
the call conversion module is used for converting RPC unit call information into a message;
the message distribution module is used for distributing the received message to a target thread;
the message receiving module is used for monitoring a message queue in the message middleware and receiving the message.
Preferably, after receiving the message, the message middleware temporarily stores the message in a computer memory, so that a receiver of the message does not need to immediately process the message. The process is similar to the short message of a mobile phone, and the user can process the short message at a convenient time; the message middleware organizes the messages into a queue according to the sending time, when the receiver obtains the messages, the messages are obtained according to the time sequence, the correct sequence of the messages is ensured, by the means, the message middleware decouples the sender and the receiver, when the sender sends the messages, whether the receiver is on line or not does not need to be considered, only the message middleware is ensured to be on line, when the receiver receives the messages, the sender does not need to be accessed, and only the message middleware needs to be accessed.
Preferably, the callback registration module records callback information of a caller by adopting a HashMap data structure;
the HashMap is a Key Value pair type data structure consisting of a Key and a Value; in the callback registration module, key represents a call ID, and Value represents a callback function pointer; the method comprises the following specific steps:
when calling is sent, a calling party generates a calling ID and puts the calling ID into a message;
after the calling result is returned, the message distribution module can analyze the calling ID in the message and find out the relevant key value pair in the HashMap, namely find out the pointer of the callback function;
and calling the callback function through the callback function pointer.
Preferably, the call conversion module uses JSON specification to convert the PRC unit call information into a character string, the character string is used as a message body, and the call ID is used as a message header, so that the character string and the call ID form a complete message.
Preferably, after receiving the message, the message distribution module accesses the HashMap in the callback registration module, finds the pointer of the callback function, and calls the callback function through the callback function pointer.
Preferably, the message receiving module is a message client that implements the AMQP protocol, and uses Pull mode to periodically access the message middleware and Pull the message temporarily stored in the message middleware to the local.
More preferably, the working process of the system is as follows:
(1) The calling party calls the thread to register the self information in the callback registration module;
(2) The calling conversion module of the calling party converts the calling information into a message;
(3) Sending the message to message middleware;
(4) The message receiving module of the called party receives the message from the message middleware;
(5) The message distribution module of the called party determines the called thread and executes calling;
(6) The called thread processing service;
(7) After the called thread processes the service, the calling result is transmitted back to the calling conversion module of the called party;
(8) The calling conversion module of the called party converts the calling result into a message and sends the message to the message middleware;
(9) Receiving the message by a message receiving module of the calling party;
(10) The message distribution module of the calling party finds an initial calling thread according to the callback information registered before;
(11) And the calling thread receives the calling result and completes the calling.
A remote concurrent call method based on message queue, the method is to introduce message middleware between the caller and the callee as the communication channel of both callers, and to convert the RPC unit call into message, and to send the call information and the call result through the sending and the return of the message; the method comprises the following specific steps:
after receiving the message, the message middleware temporarily stores the message in a computer memory, so that a receiver of the message does not need to immediately process the message. The process is similar to the short message of a mobile phone, and the user can process the short message at a convenient time;
the message middleware organizes the messages into a queue according to the sending time, when the receiver obtains the messages, the messages are obtained according to the time sequence, the correct sequence of the messages is ensured, by the means, the message middleware decouples the sender and the receiver, when the sender sends the messages, whether the receiver is on line or not does not need to be considered, only the message middleware is ensured to be on line, when the receiver receives the messages, the sender does not need to be accessed, and only the message middleware needs to be accessed.
Preferably, the RPC unit comprises a callback registration module, a call conversion module, a message distribution module and a message receiving module;
the callback registration module is used for recording callback information of a calling party;
the call conversion module is used for converting RPC unit call information into a message;
the message distribution module is used for distributing the received message to a target thread;
the message receiving module is used for monitoring a message queue in the message middleware and receiving messages.
Preferably, the callback registration module records callback information of a caller by adopting a HashMap data structure;
the HashMap is a Key Value pair type data structure consisting of Key and Value; in a callback registration module, key represents a call ID, and Value represents a callback function pointer; the method comprises the following specific steps:
when the call is sent, the calling party generates a call ID and puts the call ID into a message;
after the calling result is returned, the message distribution module can analyze the calling ID in the message and find out the relevant key value pair in the HashMap, namely find out the pointer of the callback function;
calling a callback function through a callback function pointer;
the calling conversion module converts the PRC unit calling information into a character string by using JSON specification, the character string is used as a message body, and the calling ID is used as a message header, so that the character string and the calling ID form a complete message;
after receiving the message, the message distribution module accesses the HashMap in the callback registration module, finds a pointer of a callback function, and calls the callback function through the callback function pointer;
the message receiving module is a message client side which realizes an AMQP protocol, uses a Pull mode to access the message middleware regularly and draws the message temporarily stored in the message middleware to the local.
The concurrent remote call system and method based on the message queue have the following advantages that:
the invention can realize multithreading concurrent processing of the RPC unit and the decoupling of calling two parties;
the invention can fully decouple the calling party and the called party through the message middleware, and can send the call as long as the message middleware is on-line when the called party is off-line or the network is interrupted;
the called party of the invention does not need to respond to the call immediately, and can utilize the characteristics of the message middleware to use single thread to execute the call in series or use a thread pool to limit the concurrency of the call;
the invention fully utilizes the serialization and the decoupling characteristics of the message queue system, utilizes the message distribution mechanism and considers the concurrency characteristics of the call, so that the remote process call can consider the decoupling and the concurrency characteristics.
Drawings
The invention is further described below with reference to the accompanying drawings.
FIG. 1 is a schematic diagram of a message queue based concurrent remote invocation system.
Detailed Description
The concurrent remote invocation message queue-based system and method of the present invention are described in detail below with reference to the figures and the detailed description of the preferred embodiments.
Example 1:
as shown in fig. 1, the embodiment provides a concurrent remote invocation system based on a message queue, which includes a message middleware arranged between RPC units of a caller and a callee, where the message middleware is used to invoke communication channels of both parties, temporarily store and manage messages, and decouple both parties receiving and sending messages;
the RPC unit comprises a callback registration module, a call conversion module, a message distribution module and a message receiving module;
the callback registration module is used for recording callback information of a calling party;
the call conversion module is used for converting RPC unit call information into a message;
the message distribution module is used for distributing the received message to a target thread;
the message receiving module is used for monitoring a message queue in the message middleware and receiving messages.
After receiving the message, the message middleware in this embodiment temporarily stores the message in a memory of the computer, so that a receiver of the message does not need to immediately process the message. The process is similar to the short message of a mobile phone, and a user can process the short message at a convenient time; the message middleware organizes the messages into a queue according to the sending time, when the receiver obtains the messages, the messages are obtained according to the time sequence, the correct sequence of the messages is ensured, by the means, the message middleware decouples the sender and the receiver, when the sender sends the messages, whether the receiver is on line or not does not need to be considered, only the message middleware is ensured to be on line, when the receiver receives the messages, the sender does not need to be accessed, and only the message middleware needs to be accessed.
The callback registration module in the embodiment records callback information of a calling party by adopting a HashMap data structure;
the HashMap is a Key Value pair type data structure consisting of Key and Value; in the callback registration module, key represents a call ID, and Value represents a callback function pointer; the method comprises the following specific steps:
when the call is sent, the calling party generates a call ID and puts the call ID into a message;
after the calling result is returned, the message distribution module can analyze the calling ID in the message and find out the relevant key value pair in the HashMap, namely find out the pointer of the callback function;
and calling the callback function through the callback function pointer.
In this embodiment, the call conversion module converts the PRC unit call information into a character string using the JSON specification, where the character string is used as a message body, and the call ID is used as a message header, so that the character string and the call ID form a complete message.
After receiving the message, the message distribution module in this embodiment accesses the HashMap in the callback registration module, finds the pointer of the callback function, and calls the callback function through the callback function pointer.
The message receiving module in this embodiment is a message client that implements the AMQP protocol, and uses the Pull mode to periodically access the message middleware and Pull the message temporarily stored in the message middleware to the local.
The working process of the system is as follows:
(1) The calling party calls the thread to register the self information in the callback registration module;
(2) The calling conversion module of the calling party converts the calling information into a message;
(3) Sending the message to message middleware;
(4) The message receiving module of the called party receives the message from the message middleware;
(5) The message distribution module of the called party determines the called thread and executes calling;
(6) The called thread processing service;
(7) After the called thread processes the service, the calling result is transmitted back to the calling conversion module of the called party;
(8) The calling conversion module of the called party converts the calling result into a message and sends the message to the message middleware;
(9) Receiving the message by a message receiving module of the calling party;
(10) The message distribution module of the calling party finds an initial calling thread according to the callback information registered before;
(11) And the calling thread receives the calling result and completes the calling.
Example 2:
the embodiment provides a concurrent remote calling method based on a message queue, which is characterized in that a message middleware is introduced between a calling party and a called party and is used as a communication channel of the calling party and the called party, RPC unit calls are converted into messages, and calling information and a call return result are sent and returned through the sending of the messages; the method comprises the following specific steps:
after receiving the message, the message middleware temporarily stores the message in a computer memory, so that a receiver of the message does not need to immediately process the message. The process is similar to the short message of a mobile phone, and the user can process the short message at a convenient time;
the message middleware organizes the messages into a queue according to the sending time, when the receiver obtains the messages, the messages are obtained according to the time sequence, the correct sequence of the messages is ensured, by the means, the message middleware decouples the sender and the receiver, when the sender sends the messages, whether the receiver is on line or not does not need to be considered, only the message middleware is ensured to be on line, when the receiver receives the messages, the sender does not need to be accessed, and only the message middleware needs to be accessed.
The RPC unit in the embodiment comprises a callback registration module, a call conversion module, a message distribution module and a message receiving module;
the callback registration module is used for recording callback information of a calling party;
the call conversion module is used for converting RPC unit call information into a message;
the message distribution module is used for distributing the received message to a target thread;
the message receiving module is used for monitoring a message queue in the message middleware and receiving messages.
The callback registration module in the embodiment records callback information of a calling party by adopting a HashMap data structure;
the HashMap is a Key Value pair type data structure consisting of Key and Value; in the callback registration module, key represents a call ID, and Value represents a callback function pointer; the method comprises the following specific steps:
when calling is sent, a calling party generates a calling ID and puts the calling ID into a message;
after the calling result is returned, the message distribution module can analyze the calling ID in the message and find out the relevant key value pair in the HashMap, namely find out the pointer of the callback function;
calling a callback function through a callback function pointer;
the calling conversion module in the embodiment converts the PRC unit calling information into a character string by using JSON specification, the character string is used as a message body, and meanwhile, the calling ID is used as a message header, so that the character string and the calling ID form a complete message;
after receiving the message, the message distribution module in the embodiment accesses the HashMap in the callback registration module, finds the pointer of the callback function, and calls the callback function through the callback function pointer;
the message receiving module in this embodiment is a message client that implements the AMQP protocol, and uses the Pull mode to periodically access the message middleware and Pull the message temporarily stored in the message middleware to the local.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; while the invention has been described in detail and with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and these modifications or substitutions do not depart from the spirit of the corresponding technical solutions of the embodiments of the present invention.
Claims (10)
1. A concurrent remote call system based on message queue is characterized in that a message middleware is arranged between RPC units of a calling party and a called party, and the message middleware is used for calling communication channels of the calling party and the called party, temporarily storing and managing messages and decoupling the two parties receiving and transmitting the messages;
the RPC unit comprises a callback registration module, a call conversion module, a message distribution module and a message receiving module;
the callback registration module is used for recording callback information of a calling party;
the calling conversion module is used for converting calling information into a message;
the message distribution module is used for distributing the received message to a target thread;
the message receiving module is used for monitoring a message queue in the message middleware and receiving messages.
2. The message queue-based concurrent remote invocation system according to claim 1, wherein the message middleware temporarily stores a message in a computer memory after receiving the message; the message middleware organizes the messages into a queue according to the sending time, and when the receiving party obtains the messages, the messages are obtained according to the time sequence.
3. The message queue-based concurrent remote invocation system according to claim 1, wherein the callback registration module records callback information of the caller using a HashMap data structure;
the HashMap is a Key Value pair type data structure consisting of a Key and a Value; in the callback registration module, key represents a call ID, and Value represents a callback function pointer; the method comprises the following specific steps:
when the call is sent, the calling party generates a call ID and puts the call ID into a message;
when the calling result is returned, the message distribution module can analyze the calling ID in the message and find out the relevant key value pair in the HashMap, namely, the pointer of the callback function can be found out;
and calling the callback function through the callback function pointer.
4. The message queue-based concurrent remote invocation system according to claim 1, wherein the invocation conversion module uses JSON specification to convert the PRC unit invocation information into a string, the string being used as a message body, and the invocation ID being used as a message header, so that the string and the invocation ID form a complete message.
5. The message queue-based concurrent remote call system according to claim 1, wherein the message distribution module accesses the HashMap in the callback registration module after receiving the message, finds the pointer of the callback function, and calls the callback function through the callback function pointer.
6. The message queue-based concurrent remote invocation system according to any one of the claims 1 to 5, wherein the message receiving module is a message client which implements AMQP protocol, and uses Pull mode to periodically access the message middleware and Pull the message temporarily stored in the message middleware to the local.
7. The message queue-based concurrent remote invocation system according to claim 6, wherein the working process of the system is as follows:
(1) The calling party calls the thread to register the self information in the callback registration module;
(2) The calling conversion module of the calling party converts the calling information into a message;
(3) Sending the message to message middleware;
(4) The message receiving module of the called party receives the message from the message middleware;
(5) The message distribution module of the called party determines the called thread and executes calling;
(6) The called thread processing service;
(7) After the called thread processes the service, the calling result is transmitted back to the calling conversion module of the called party;
(8) The calling conversion module of the called party converts the calling result into a message and sends the message to the message middleware;
(9) Receiving the message by a message receiving module of the calling party;
(10) The message distribution module of the calling party finds an initial calling thread according to the callback information registered before;
(11) And the calling thread receives the calling result and completes the calling.
8. A concurrent remote calling method based on message queue is characterized in that a message middleware is introduced between a calling party and a called party and used as a communication channel of the calling party and the called party, RPC unit call is converted into a message, and calling information and a call return result are sent and returned through the message; the method comprises the following specific steps:
after receiving the message, the message middleware temporarily stores the message in a memory of a computer;
the message middleware organizes the messages into a queue according to the sending time, and when the receiving party obtains the messages, the messages are obtained according to the time sequence.
9. The message queue-based concurrent remote call method according to claim 8, wherein the RPC unit comprises a callback registration module, a call conversion module, a message distribution module, and a message reception module;
the callback registration module is used for recording callback information of a calling party;
the calling conversion module is used for converting calling information into a message;
the message distribution module is used for distributing the received message to a target thread;
the message receiving module is used for monitoring a message queue in the message middleware and receiving messages.
10. The message queue-based concurrent remote invocation method according to the claims 8 or 9, wherein the callback registration module records callback information of a caller by using a HashMap data structure;
the HashMap is a Key Value pair type data structure consisting of Key and Value; in the callback registration module, key represents a call ID, and Value represents a callback function pointer; the method comprises the following specific steps:
when the call is sent, the calling party generates a call ID and puts the call ID into a message;
after the calling result is returned, the message distribution module can analyze the calling ID in the message and find out the relevant key value pair in the HashMap, namely find out the pointer of the callback function;
calling a callback function through a callback function pointer;
the calling conversion module converts the PRC unit calling information into a character string by using JSON specification, the character string is used as a message body, and the calling ID is used as a message header, so that the character string and the calling ID form a complete message;
after receiving the message, the message distribution module accesses the HashMap in the callback registration module, finds a pointer of a callback function, and calls the callback function through the callback function pointer;
the message receiving module is a message client side which realizes an AMQP protocol, uses a Pull mode to access the message middleware regularly and draws the message temporarily stored in the message middleware to the local.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211051281.4A CN115454667A (en) | 2022-08-31 | 2022-08-31 | Concurrent remote calling system and method based on message queue |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211051281.4A CN115454667A (en) | 2022-08-31 | 2022-08-31 | Concurrent remote calling system and method based on message queue |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115454667A true CN115454667A (en) | 2022-12-09 |
Family
ID=84301238
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211051281.4A Pending CN115454667A (en) | 2022-08-31 | 2022-08-31 | Concurrent remote calling system and method based on message queue |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115454667A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116643870A (en) * | 2023-07-24 | 2023-08-25 | 北方健康医疗大数据科技有限公司 | Method, system and device for processing long-time task distribution and readable storage medium |
-
2022
- 2022-08-31 CN CN202211051281.4A patent/CN115454667A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116643870A (en) * | 2023-07-24 | 2023-08-25 | 北方健康医疗大数据科技有限公司 | Method, system and device for processing long-time task distribution and readable storage medium |
| CN116643870B (en) * | 2023-07-24 | 2023-11-10 | 北方健康医疗大数据科技有限公司 | Method, system and device for processing long-time task distribution and readable storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6999997B2 (en) | Method and apparatus for communication of message data using shared queues | |
| WO2021088641A1 (en) | Data transmission method, data processing method, data reception method and device, and storage medium | |
| CN110958281B (en) | Data transmission method and communication device based on Internet of things | |
| CN110134534B (en) | System and method for optimizing message processing for big data distributed system based on NIO | |
| CN110413424B (en) | Configurable third-party message callback method, device, server and storage medium | |
| US10454795B1 (en) | Intermediate batch service for serverless computing environment metrics | |
| CN1939035B (en) | Method and apparatus for communicating data between computer devices | |
| US6466660B1 (en) | Method and apparatus for retroactively updating a communication billing system | |
| CN115454667A (en) | Concurrent remote calling system and method based on message queue | |
| CN106936896A (en) | Kafka cluster data transmission method and device | |
| US7941134B2 (en) | Push-to-talk communication system and push-to-talk communication method | |
| CN111200606A (en) | Deep learning model task processing method, system, server and storage medium | |
| US20070240170A1 (en) | Computer implemented method and system for processing an event notification within a notification infrastructure of a database system using a persistent queue | |
| CN113824653A (en) | Method and system compatible with multi-protocol service access | |
| CN116800787A (en) | Vehicle-mounted communication method and system based on Ethernet communication protocol | |
| WO2019201111A1 (en) | Information processing method, apparatus and device, and computer-readable storage medium | |
| CA3196744C (en) | Method and system to seamlessly upgrade cloud-based call processing services | |
| CN110809020B (en) | High-reliability data transmission method based on redundant network asynchronous communication | |
| CN101938496A (en) | Call control method, device and system for attendant console | |
| US8046419B2 (en) | Method of processing open asynchronous application service event and open web service gateway implementing the same | |
| CN114938387B (en) | Data transmission method, device, system and storage medium | |
| CN113098792B (en) | Interface data communication method and system based on token binding | |
| KR102134552B1 (en) | System and method for transmitting message capable of seperate accounting | |
| CN117573396B (en) | Distributed workflow event processing method, device and medium | |
| KR102340954B1 (en) | Apparatus and method for transmitting message |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20240729 Address after: Room 305-22, Building 2, No. 1158 Zhangdong Road and No. 1059 Dangui Road, China (Shanghai) Pilot Free Trade Zone, Pudong New Area, Shanghai, 200120 Applicant after: Shanghai Yunxi Technology Co.,Ltd. Country or region after: China Address before: 250100 Ji'nan hi tech Zone No. 2877, Shandong Province Applicant before: INSPUR SOFTWARE GROUP Co.,Ltd. Country or region before: China |