Communication method and device between applications, non-volatile storage medium, and processor

By adopting publish subscription communication method between microservices, checking the subscription status of sub-applications and temporarily storing publish events when necessary, the problem of poor communication quality between microservices is solved, and loose coupling and independent operation deployment between applications is realized.

CN115580642BActive Publication Date: 2024-11-19BEIJING INTELLIGENT BUILDING TECH CO LTD
View PDF 7 Cites 0 Cited by

Patent Information

Application Number
CN202211152973.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-09-21
Publication Date
2024-11-19
Estimated Expiration
2042-09-21

AI Technical Summary

Technical Problem

In the prior art, the failure of publish subscription between microservices to use leads to poor communication quality, affecting the maintainability and communication efficiency between applications.

Method used

By checking whether the sub-application completes the subscription task of publishing events, the main application saves the publishing event in the first target file until the sub-application completes the subscription and then uploads it to the second target file. The sub-application listens through the microservice's objective function And execute publish events, using publish subscription communication between applications.

Benefits of technology

The number of communications between applications is reduced, the effects of loose coupling and independent operation and independent deployment are achieved, and the communication quality is improved.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115580642B_ABST
    Figure CN115580642B_ABST
Patent Text Reader

Abstract

The present application discloses a communication method and device between applications, a non-volatile storage medium, and a processor. The method includes: checking whether the sub-application of a microservice has completed the subscription task for the published event, wherein the subscription task is for the sub-application to receive the published event; when the sub-application has not completed the subscription task for the published event, the main application saves the published event in the first target file, and when the published event exists in the first target file, the sub-application executes the subscription task and publishes the event; when the sub-application completes the subscription task for the published event, the main application uploads the published event to the second target file through the application programming interface, and the sub-application executes the published event by monitoring the target function of the microservice in the second target file. The present application solves the technical problem of poor communication quality caused by the failure to adopt the publish-subscribe communication method between the applications in the microservice.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular, to a communication method and device between applications, a non-volatile storage medium, and a processor. Background Art

[0002] In related technologies, front-end microservices use the postMessage method provided by the browser to implement cross-text document, multi-window, and cross-domain message transmission. However, as the application volume increases, frequent calls will lead to a decrease in the maintainability of the project communication module, and there will also be problems with poor communication quality between applications.

[0003] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0004] The embodiments of the present application provide a method and device for communication between applications, a non-volatile storage medium, and a processor, so as to at least solve the technical problem of poor communication quality caused by the failure to adopt a publish-subscribe communication method between applications in a microservice.

[0005] According to one aspect of an embodiment of the present application, a method for communication between applications is provided, including: checking whether a sub-application of a microservice has completed a subscription task for a published event, wherein the subscription task is for the sub-application to receive the published event; when the sub-application has not completed the subscription task for the published event, the main application saves the published event in a first target file, and when the published event exists in the first target file, the sub-application executes the subscription task and the published event; when the sub-application completes the subscription task for the published event, the main application uploads the published event to a second target file through an application programming interface, and the sub-application executes the published event by monitoring the target function of the microservice in the second target file.

[0006] Optionally, the microservice is a front-end microservice, and the sub-applications are multiple applications obtained by splitting the front-end page by the front-end microservice, wherein the sub-applications are registered in the main application.

[0007] Optionally, the in-application data between sub-applications is shared data; the in-application data between the main application and the sub-applications is shared data.

[0008] Optionally, the execution stacks of the scripts between the sub-applications are in a mutually isolated state; the execution stacks of the scripts between the main application and the sub-applications are in a mutually isolated state.

[0009] Optionally, the sub-application is composed of multiple functional modules, wherein the functional modules are prohibited from communicating with each other through the local cache of the browser.

[0010] Optionally, the target function includes at least a callback function of the microservice during its life cycle.

[0011] Optionally, at least a temporary token for computer identity authentication stored in data on the target object's local terminal is shared between sub-applications; at least a temporary token for computer identity authentication stored in data on the target object's local terminal is shared between the main application and the sub-application.

[0012] According to another aspect of the embodiments of the present application, a non-volatile storage medium is provided, the storage medium includes a stored program, wherein when the program is executed, the device where the storage medium is located is controlled to execute the above-mentioned communication method between applications.

[0013] According to yet another aspect of the embodiments of the present application, a processor is provided, which is used to run a program stored in a memory, wherein the above inter-application communication method is executed when the program is running.

[0014] In an embodiment of the present application, a method is adopted to check whether the sub-application of the microservice has completed the subscription task for the published event, wherein the subscription task is for the sub-application to receive the published event; when the sub-application has not completed the subscription task for the published event, the main application saves the published event in the first target file, and when the published event exists in the first target file, the sub-application executes the subscription task and publishes the event; when the sub-application completes the subscription task for the published event, the main application uploads the published event to the second target file through the application programming interface, and the sub-application monitors the target function of the microservice in the second target file and executes the published event. Through the publish-subscribe communication method between applications, the purpose of reducing the number of communications between applications is achieved, thereby achieving the technical effect of loose coupling between applications and independent operation and independent deployment, and further solving the technical problem of poor communication quality caused by the failure to adopt the publish-subscribe communication method between applications in the microservice. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0016] Figure 1 is a flow chart of a communication method between applications according to an embodiment of the present application;

[0017] Figure 2 is a structural diagram of an inter-application communication device according to an embodiment of the present application;

[0018] Figure 3 It is a hardware structure block diagram of a computer terminal (or electronic device) according to an inter-application communication method of an embodiment of the present application.

[0019] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0020] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0021] According to an embodiment of the present application, a method embodiment of a communication method between applications is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0022] The most common solution for web front-end is to use iframe to embed the front-end page of other modules, but there are some main problems with using iframe:

[0023] 1. Page communication problem: When the iframe and the parent window are from different sources, the parent window cannot be directly operated. In this scenario, postMessage can only be used to achieve communication, and the transmitted data can only be strings, making the communication between pages more cumbersome;

[0024] 2. Layout issues: The iframe must be given a specified height, otherwise it will collapse. In some cases, multiple scroll bars will appear on the page, resulting in a poor user experience.

[0025] Web front-end projects did not use front-end microservices in the early stage, which resulted in the overall project being large and redundant, and the update, deployment and release were also cumbersome. The introduction of front-end microservices mainly solved the following problems:

[0026] 1. Independent technology stack: The main framework does not restrict the technology stack of the sub-applications that can be accessed. The technology stack selection for each application can be coordinated with the business team to choose and use;

[0027] 2. Independent development and deployment: The sub-application warehouse is independent and can be split according to business modules to refine each sub-application. The front-end and back-end can be developed independently. After the deployment is completed, the main framework will update the sub-application synchronously.

[0028] 3. Independent operation: The status of each sub-application is isolated, and the failure of a single sub-application will not affect other projects;

[0029] 4. Data sharing: Sub-applications can share the data of the main application, and can also share the data of sibling sub-applications.

[0030] The main application and sub-applications between microservices communicate through the publish-subscribe method, which achieves the effect of minimizing communication between the main application and the sub-application, loose coupling between the main application and the sub-application, and independent operation and deployment of the main application and the sub-application.

[0031] When the main application and the sub-application communicate through publish and subscribe, if some subscription events are asynchronous tasks, the sub-application cannot predict the completion time of the asynchronous task. It is possible that when the main application publishes, the sub-application has not completed the subscription. This application provides an effective solution for this situation. Among them, synchronous tasks are tasks that are not suspended by the engine and queued for execution on the main thread. Only when the previous task is completed can the next task be executed; asynchronous tasks are tasks that are put on hold by the engine and do not enter the main thread, but enter the task queue. Only when the engine believes that an asynchronous task can be executed, the task will enter the main thread for execution.

[0032] Figure 1 is a flow chart of a communication method between applications according to an embodiment of the present application. Figure 1 As shown, the method comprises the following steps:

[0033] Step S102, checking whether the sub-application of the microservice has completed the subscription task for the published event, wherein the subscription task is for the sub-application to receive the published event.

[0034] According to an optional embodiment of the present application, if some subscription events are asynchronous tasks, the sub-application cannot predict the completion time of the asynchronous task. There may be a situation where the sub-application has not completed the subscription when the main application publishes. In this case, the main application needs to check whether the sub-application of the microservice has completed the subscription task for the published event before uploading the published event.

[0035] In software architecture, publish-subscribe is a messaging paradigm where the sender (publisher) of a message does not send the message directly to a specific receiver (subscriber). Instead, the published messages are divided into different categories without knowing which subscribers may exist. Similarly, subscribers can express interest in one or more categories and only receive messages of interest without knowing which publishers exist. In an embodiment of the present application, the publisher is the main application of the front-end microservice, and the subscriber is a sub-application of the front-end microservice.

[0036] Step S104, when the sub-application has not completed the subscription task for the publishing event, the main application saves the publishing event in the first target file, and when the publishing event exists in the first target file, the sub-application executes the subscription task and the publishing event.

[0037] According to another optional embodiment of the present application, when the subscriber (sub-application) has not completed the subscription to the published event, the main application will first temporarily store the published event in a certain file, namely the first target file. When subscribing, the sub-application checks whether there is a task published in advance by the main application in the first target file. If there is a task published in advance by the main application in the first target file, the sub-application will execute the published event at the same time as executing the subscription task. It should be noted that the task published in advance by the main application is the task published by the main application when the sub-application has not completed the subscription task for the published event.

[0038] Step S106, when the sub-application completes the subscription task for the published event, the main application uploads the published event to the second target file through the application programming interface, and the sub-application executes the published event by monitoring the target function of the microservice in the second target file.

[0039] In some optional embodiments of the present application, when the subscriber (sub-application) completes the subscription task for the published event, the main application defines the global state through initGlobalState and uploads the subscription task to the second target file. Wherein, initGlobalState is an application programming interface under the qiankun framework.

[0040] As an optional embodiment of the present application, the method provided in step S102 to step S106 can be implemented by the following code:

[0041]

[0042]

[0043] Among them, the layout processing of the above code is:

[0044]

[0045] According to the above steps, the purpose of reducing the number of communications between applications is achieved through the publish-subscribe communication method between applications, thereby achieving the technical effects of loose coupling between applications and independent operation and independent deployment, and further solving the technical problem of poor communication quality caused by the failure to adopt the publish-subscribe communication method between applications in microservices.

[0046] According to an optional embodiment of the present application, the microservice is a front-end microservice, and the sub-application is a plurality of applications obtained by splitting the front-end page by the front-end microservice, wherein the sub-application is registered in the main application.

[0047] In some optional embodiments of the present application, the in-application data between sub-applications is shared data; the in-application data between the main application and the sub-applications is shared data.

[0048] According to an optional embodiment of the present application, the in-application data includes user information and other data, and the in-application data between sub-applications can be shared with each other. Similarly, the in-application data of the main application and the in-application data of the sub-application can also be shared with each other.

[0049] In some optional embodiments of the present application, the execution stacks of scripts between sub-applications are in a mutually isolated state; the execution stacks of scripts between the main application and the sub-applications are in a mutually isolated state.

[0050] As another optional embodiment of the present application, the scripting language is JS, namely javascript. JavaScript is a scripting language developed from Netscape's LiveScript, and its main purpose is to solve the speed problem left over from the server terminal language.

[0051] According to an optional embodiment of the present application, the sub-application is composed of multiple functional modules, wherein the functional modules are prohibited from communicating through the local cache of the browser.

[0052] According to another optional embodiment of the present application, the business modules constituting the sub-applications are also referred to as components, and it is agreed that the components are prohibited from communicating through the local cache of the browser. Because any code in the local cache can be changed, it is difficult to track the change history, and it will also cause the front-end page to lose its responsive layout.

[0053] As an optional embodiment of the present application, the communication between the front-end microservice applications should also follow the following convention: the microservice file access path of all sub-applications and the uniform resource locator access path of the microservice are unified paths.

[0054] In some optional embodiments of the present application, the target function includes at least a callback function of the microservice within its life cycle.

[0055] As another optional embodiment of the present application, the microservice can use the callback function to filter all messages and events at the system level and access messages that are normally inaccessible. The callback function is also called a hook function, and the essence of the hook is a program for processing system messages.

[0056] In some optional embodiments of the present application, at least a temporary token for computer identity authentication stored in data on the local terminal of the target object is shared between sub-applications; at least a temporary token for computer identity authentication stored in data on the local terminal of the target object is shared between the main application and the sub-application.

[0057] According to the above steps, the purpose of reducing the number of communications between applications is achieved, thereby achieving the technical effect of loose coupling between applications and independent operation and deployment, and further solving the technical problem of poor communication quality caused by the failure to adopt the publish-subscribe communication method between applications in microservices.

[0058] Figure 2 is a structural diagram of an inter-application communication device according to an embodiment of the present application, such as Figure 2 As shown, the device comprises:

[0059] The checking module 202 is used to check whether the sub-application of the microservice has completed the subscription task for the published event, wherein the subscription task is that the sub-application receives the published event;

[0060] A saving module 204, configured to cause the main application to save the publishing event in the first target file when the sub-application has not completed the subscription task for the publishing event, and to cause the sub-application to execute the subscription task and publish the event when the publishing event exists in the first target file;

[0061] The execution module 206 is used for when the sub-application completes the subscription task of the published event, the main application uploads the published event to the second target file through the application programming interface, and the sub-application executes the published event by monitoring the target function of the microservice in the second target file.

[0062] It should be noted that Figure 2 The preferred implementation of the illustrated embodiment can be found in Figure 1 The relevant description of the illustrated embodiment will not be repeated here.

[0063] Front-end microservices mainly solve the following problems:

[0064] 1. Independent technology stack: The main framework does not restrict the technology stack of the sub-applications that can be accessed. The technology stack selection for each application can be coordinated with the business team to choose and use;

[0065] 2. Independent development and deployment: The sub-application warehouse is independent and can be split according to business modules to refine each sub-application. The front-end and back-end can be developed independently. After the deployment is completed, the main framework will update the sub-application synchronously.

[0066] 3. Independent operation: The status of each sub-application is isolated, and the failure of a single sub-application will not affect other projects;

[0067] 4. Data sharing: Sub-applications can share the data of the main application, and can also share the data of sibling sub-applications.

[0068] Figure 3 According to an embodiment of the present application, a hardware structure block diagram of a computer terminal (or electronic device) for a communication method between applications is provided. Figure 3 As shown, the computer terminal 30 (or electronic device 30) may include one or more (302a, 302b, ..., 302n are used to illustrate) processors (the processor may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 304 for storing data, and a transmission module 306 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the I / O interface), a network interface, a power supply and / or a camera. It can be understood by those skilled in the art that Figure 3 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 3 More or fewer components as shown, or with Figure 3 Different configurations are shown.

[0069] It should be noted that the one or more processors and / or other data processing circuits described above may generally be referred to herein as "data processing circuits". The data processing circuits may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. In addition, the data processing circuit may be a single independent processing module, or may be incorporated in whole or in part into any of the other components in the computer terminal 30 (or electronic device). As described in the embodiments of the present application, the data processing circuit acts as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0070] The memory 304 can be used to store software programs and modules of application software, such as program instructions / data storage devices corresponding to the communication method between applications in the embodiment of the present application. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory 304, that is, realizing the communication method between the above-mentioned applications. The memory 304 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 304 may further include a memory remotely arranged relative to the processor, and these remote memories may be connected to the computer terminal 30 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0071] The transmission module 306 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the computer terminal 30. In one example, the transmission device 306 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 306 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0072] The display may be, for example, a touch screen liquid crystal display (LCD) that enables a user to interact with a user interface of the computer terminal 30 (or electronic device).

[0073] It should be noted that, in some optional embodiments, the above Figure 3 The computer device (or electronic device) shown may include hardware elements (including circuits), software elements (including computer code stored on a computer-readable medium), or a combination of hardware elements and software elements. It should be noted that Figure 3 This is merely one example of a particular embodiment and is intended to illustrate the types of components that may be present in the above-described computer device (or electronic device).

[0074] It should be noted that Figure 3 The electronic device shown is used to perform Figure 1 The communication method between applications shown in the figure, therefore the relevant explanations in the execution method of the above command are also applicable to the electronic device and will not be repeated here.

[0075] An embodiment of the present application further provides a non-volatile storage medium, which includes a stored program, wherein when the program is running, the device where the storage medium is located is controlled to execute the above-mentioned communication method between applications.

[0076] A program for executing the following functions on a non-volatile storage medium: checking whether a sub-application of a microservice has completed a subscription task for a published event, wherein the subscription task is for the sub-application to receive the published event; when the sub-application has not completed the subscription task for the published event, the main application saves the published event in a first target file, and when the published event exists in the first target file, the sub-application executes the subscription task and publishes the event; when the sub-application completes the subscription task for the published event, the main application uploads the published event to a second target file through an application programming interface, and the sub-application executes the published event by monitoring a target function of the microservice in the second target file.

[0077] An embodiment of the present application further provides a processor, which is used to run a program stored in a memory, wherein the above-mentioned communication method between applications is executed when the program is running.

[0078] The processor is used to run a program that performs the following functions: checking whether the sub-application of the microservice has completed the subscription task for the published event, wherein the subscription task is for the sub-application to receive the published event; when the sub-application has not completed the subscription task for the published event, the main application saves the published event in the first target file, and when the published event exists in the first target file, the sub-application executes the subscription task and publishes the event; when the sub-application completes the subscription task for the published event, the main application uploads the published event to the second target file through the application programming interface, and the sub-application executes the published event by monitoring the target function of the microservice in the second target file.

[0079] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0080] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0081] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0082] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0083] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0084] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the relevant technology or all or part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk, etc. Various media that can store program codes.

[0085] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A communication method between applications, It is characterized in that include: Check whether the sub-application of the microservice has completed the subscription task for the published event, wherein the subscription task is that the sub-application receives the published event; When the sub-application has not completed the subscription task for the published event, the main application of the microservice saves the published event in the first target file, and when the published event exists in the first target file, the sub-application executes the subscription task and the published event; When the sub-application completes the subscription task for the published event, the main application uploads the published event to the second target file through the application programming interface, and the sub-application executes the published event by monitoring the target function of the microservice in the second target file.

2. The method according to claim 1, It is characterized in that The microservice is a front-end microservice, and the sub-applications are multiple applications obtained by splitting the front-end page by the front-end microservice, wherein the sub-applications are registered in the main application.

3. The method according to claim 2, It is characterized in that The in-application data between the sub-applications is shared data; The in-application data between the main application and the sub-application is shared data.

4. The method according to claim 3, It is characterized in that The execution stacks of the scripts between the sub-applications are in a mutually isolated state; The execution stacks of the scripts between the main application and the sub-application are in a mutually isolated state.

5. The method according to claim 1, It is characterized in that The sub-application is composed of a plurality of functional modules, wherein the functional modules are prohibited from communicating with each other through the local cache of the browser.

6. The method according to claim 1, It is characterized in that The target function at least includes a callback function of the microservice within its life cycle.

7. The method according to claim 1, It is characterized in that The sub-applications are at least used to share a temporary token for computer identity authentication stored in data on a local terminal of the target object; The main application and the sub-application are at least used to share the temporary token for computer identity authentication stored in the data on the local terminal of the target object.

8. A communication device between applications, It is characterized in that include: A checking module, used to check whether the sub-application of the microservice has completed the subscription task for the published event, wherein the subscription task is that the sub-application receives the published event; A saving module, configured to cause the main application of the microservice to save the publishing event in a first target file when the sub-application has not completed the subscription task for the publishing event, and when the publishing event exists in the first target file, cause the sub-application to execute the subscription task and the publishing event; An execution module is used for, when the sub-application completes the subscription task for the published event, the main application uploads the published event to the second target file through the application programming interface, and the sub-application executes the published event by monitoring the target function of the microservice in the second target file.

9. A non-volatile storage medium, It is characterized in that The non-volatile storage medium includes a stored program, wherein when the program is executed, the device where the non-volatile storage medium is located is controlled to execute the method for communication between applications as claimed in any one of claims 1 to 7.

10. An electronic device, It is characterized in that include: A memory and a processor, wherein the processor is used to run a program stored in the memory, wherein the program executes the communication method between applications described in any one of claims 1 to 7 when running.

Citation Information

Patent Citations

  • Stream processing utilizing virtual processing agents

    CN106663039A

  • Communication method and device for multiple sub-applications, electronic device and storage medium

    CN112148501A

  • Communication method, communication device and communication system

    CN113067831A

  • Front-end-based micro-service design method

    CN113448702A

  • Wireless messaging services using publish / subscribe systems

    US20040254993A1