WO2020177731A1

WO2020177731A1 - Real-time communication method between hosted applications

Info

Publication number: WO2020177731A1
Application number: PCT/CN2020/077897
Authority: WO
Inventors: 崔英林
Original assignee: 上海连尚网络科技有限公司
Priority date: 2019-03-07
Filing date: 2020-03-05
Publication date: 2020-09-10
Also published as: CN109933444A

Abstract

Provided is a real-time communication method between hosted applications. Said method comprises receiving, by means of a real-time communication API interface, a call instruction transmitted by a first hosted application being executed on a default execution stack, said call instruction comprising the identifier information of a second hosted application; executing, according to the call instruction, the second hosted application on an auxiliary execution stack; forwarding, by means of the real-time communication API interface, communication messages between the first hosted application and the second hosted application. The present invention enables the delivery of messages between hosted applications being executed on the execution stacks of a host application, and enables real-time exchange.

Description

An instant communication method between boarding applications

【Technical Field】

This application relates to the field of Internet applications, and in particular to an instant messaging recommendation method between boarding applications.

【Background technique】

Boarding applications such as small programs are a new open capability, and developers can quickly develop a small program. Mini programs can be easily acquired and disseminated in host applications such as WeChat and Baidu App, and have an excellent user experience. Mini program developers can provide convenient and rich services in the mini program, such as reservations, product purchases, games, etc. Therefore, it has been more and more widely used.

However, in the current host application, only one host application can be run at the same time, and it is impossible to realize message transfer between different host applications and realize instant interaction.

[Content of the invention]

Various aspects of the present application provide an instant communication method between boarding applications, which is used to solve the problem that real-time interaction between boarding applications cannot be realized.

One aspect of this application provides an instant messaging method between host applications, which is applied to a host application. The host application includes a plurality of runtime stacks for running the host application; including receiving and running on the default runtime stack through an instant messaging API interface The call instruction sent by the first host application on the above, the call instruction includes the identification information of the second host application; according to the call instruction, run the second host application on the auxiliary running stack; forward the call via the instant messaging API interface A communication message between the first host application and the second host application.

In another aspect of the present application, there is provided an instant messaging method between host applications, which is applied to a first host application, and the first host application runs on the default runtime stack of the host application; including sending a call instruction through an instant messaging API interface , The call instruction includes the identification information of the second host application; so that the host application runs the second host application on the auxiliary execution stack according to the call instruction; wherein, the host application includes a plurality of host applications for running the host application The runtime stack; receiving the execution result returned after executing the call instruction sent by the second host application forwarded by the host application through the instant messaging API interface.

In another aspect of the present application, there is provided an instant messaging method between host applications, which is applied to a second host application, and the second host application runs on the auxiliary runtime stack of the host application; including receiving and executing via an instant messaging API interface The call instruction sent by the first host application running on the default run stack forwarded by the host application; wherein the host application includes multiple run stacks for running the host application; the execution result is returned through the instant messaging API interface so that The host application returns the execution result to the first host application.

In another aspect of the present application, a device is provided. The device includes: one or more processors; a storage device for storing one or more programs. When the one or more programs are used by the one or more Execution by two processors, so that the one or more processors implement any of the above-mentioned methods.

In another aspect of the present application, there is provided a computer-readable storage medium on which a computer program is stored, characterized in that, when the program is executed by a processor, any of the above methods is implemented.

It can be seen from the technical solution that, in the above-mentioned embodiments of the present application, instant communication between host applications can be realized.

【Explanation of drawings】

In order to more clearly describe the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the drawings in the following description are of the present application. For some embodiments, for those of ordinary skill in the art, other drawings can be obtained from these drawings without creative labor.

FIG. 1 is a schematic flowchart of an instant messaging method between host applications applied to a host application according to some embodiments of this application;

FIG. 2 is a schematic flowchart of an instant messaging method between boarding applications applied to a first boarding application according to some embodiments of this application;

FIG. 3 is a schematic flow chart of a method for instant messaging between boarding applications applied to a second boarding application according to some embodiments of this application;

Figure 4 is a block diagram of an exemplary computer system/server suitable for implementing some embodiments of the present invention.

【detailed description】

In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in some embodiments of the present application will be described clearly and completely in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described The embodiments are a part of the embodiments of the present application, but not all the embodiments. Based on the embodiments in this application, all other embodiments obtained by a person of ordinary skill in the art without creative work shall fall within the protection scope of this application.

In addition, the term "and/or" in this article is only an association relationship describing associated objects, which means that there can be three types of relationships, for example, A and/or B, which can mean: A alone exists, and both A and B exist. There are three cases of B alone. In addition, the character "/" in this text generally indicates that the associated objects before and after are in an "or" relationship.

Figure 1 is a schematic flow chart of an instant messaging method between hosted applications according to some embodiments of the application. The method is applied to a host application, and the host application includes a plurality of runtime stacks for running the hosted application; including the following steps :

Step S11: Receive a call instruction sent by the first host application running on the default running stack through the instant messaging API interface, where the call instruction includes identification information of the second host application;

Step S12, according to the call instruction, run the second host application on the auxiliary running stack;

Step S13: Forward the communication between the first host application and the second host application through the instant messaging API interface.

In some embodiments, the host application is an application (APP) client installed on the wireless device, such as WeChat, or the operating system of the wireless device; the host application is an application that depends on the operation of the host application, such as an applet in WeChat, etc. . The host application includes a plurality of runtime stacks for running the hosted application, for example, a default runtime stack for running a first hosted application, and an auxiliary runtime stack for running a second hosted application.

Wherein, the wireless device includes, but is not limited to, any kind of smart terminal device that can interact with the user and realize the wireless communication function, such as smart phone, tablet computer, notebook computer, etc., of course, it can also be other similar Functional equipment is not limited in this embodiment. The smart terminal device can adopt any operating system, such as Android operating system, iOS operating system, Windows operating system, and so on.

In a preferred implementation of step S11,

The host application receives the call instruction sent by the first host application running on the default running stack through the instant messaging API interface, and the call instruction includes the second host application identification information.

Preferably, the first host application runs on the first run stack of the host application; the first run stack is the default run stack of the host application.

Preferably, the host application starts the first running stack in response to the user's triggering of the first hosting application, and runs the first hosting application on the first running stack.

Preferably, the host application receives a call instruction issued by the first host application running on the execution stack, and the call instruction is used to instruct to call the second host application.

Preferably, the call instruction structure is as follows: instruction header, separator, data; wherein,

The command header part is used to mark the second host application so that the host application can run the second host application; preferably, the command header is the AppID of the second host application, and different host applications use their AppID to perform Logo

The data part is used to instruct the second hosting application to perform a corresponding operation.

Preferably, the first host application sends a call instruction to the second host application through its instant messaging API interface; the host application receives and processes the call instruction through its instant messaging API interface. For the first boarding application, it is only necessary to issue a call instruction through its instant messaging API interface, and there is no need to understand the specific receiving and forwarding process of the call instruction.

In a preferred implementation of step S12,

The host application runs the second host application on the auxiliary running stack according to the call instruction;

The host application starts the auxiliary run stack according to the call instruction; the auxiliary run stack is used to run the second host application on the auxiliary run stack while the default run stack runs the first host application. Preferably, there are one or more auxiliary running stacks that can be started by the host application, so that different hosting applications can be run on the one or more auxiliary running stacks; that is, instant communication between multiple hosting applications can be realized .

Preferably, after the auxiliary running stack is started, the second host application marked by the call instruction is run on the auxiliary running stack.

Preferably, the host application receives the message sent by the first host application through the instant messaging API interface, and determines the specific type of the message by analyzing the message; if the structure of the message includes a command header, a separator, and data, then Indicates that it is a call instruction; if the message is not a call instruction, it will be processed according to the normal flow.

In a preferred embodiment of the present application, there are one or more auxiliary runtime stacks that can be started by the host application. After the call to a host application ends, the host application is not stopped, but in its corresponding The boarding application continues to run on the auxiliary running stack; so that the boarding application can be called at any time without re-running.

Preferably, after the host application receives the call instruction, according to the AppID included in the call instruction, checks whether there is a corresponding second host application running on the auxiliary running stack;

If the corresponding second host application is already running in the auxiliary running stack, the call instruction may be forwarded to the second host application, so that the second host application executes the call instruction;

If the corresponding second host application is not running on the auxiliary run stack, the auxiliary run stack is started, the second host application is run in the auxiliary run stack, and the call instruction is forwarded to the second host application so that all The second host application executes the call instruction.

In a preferred embodiment of the present application, after the call ends, the host application stops the hosting application, and the auxiliary running stack is cleared instead of destroying, so that the required hosting application can be quickly run on the auxiliary running stack.

Preferably, if the second hosted application is not started, it is determined whether there is an activated and emptied auxiliary running stack; if it exists, the second hosted application is directly run on the auxiliary running stack; if it does not exist, the auxiliary running is started Stack, running the second hosting application on the auxiliary running stack.

Preferably, the host application calls the second host application in the background, that is, the interface of the first host application remains unchanged.

In a preferred implementation of step S13,

The host application forwards the call instruction to the second host application through the instant messaging API interface, so that the second host application executes the call instruction.

Preferably, the host application forwards the call instruction to the second host application through its instant messaging API interface; so that the second host application receives the call instruction through a unified default message receiving interface.

Preferably, the unified default message receiving interface may be an instant messaging API interface of the second host application.

Preferably, the second host application executes corresponding operations according to the data part in the call instruction structure, and returns the operation result to the first host application through a unified default result return interface.

Preferably, the data part may be an instruction instructing the second host application to read the data in the data sharing area of the first host application, so as to realize the communication between the first host application and the second host application. Data transfer.

The host application receives the execution result returned by the second host application after executing the call instruction through the instant messaging API interface, and returns the execution result to the first host application.

Preferably, the host application receives the operation result returned by the second host application through a unified default message receiving interface; forwards the operation result to the first host application through the result return interface, and the first host application The application receives the operation result through a unified default message receiving interface.

Preferably, the operation result may be the operation result of the corresponding operation performed by the second host application according to the data part in the call instruction structure; or the feedback information returned after the second host application performs the corresponding operation , The feedback information is used to indicate that the operation of the first hosted application has been executed successfully, or the execution failed.

Preferably, the unified default message receiving interface is an instant messaging API interface; the result return interface is an instant messaging API interface.

Preferably, the method further includes:

Preferably, after receiving the execution result returned by the second hosting application, the host application stops the second hosting application.

Preferably, after the first host application receives the operation result, it issues a call end instruction, and the call end instruction is used to instruct to stop the corresponding second host application. The call end instruction includes identification information of the second host application. After receiving the call end instruction, the host application stops the second host application.

Preferably, the second host application identification information is the AppID of the second host application.

Preferably, after the host application stops the second host application, the auxiliary running stack is cleared.

In the above process, the first host application running on the default runtime stack is not affected. When the host application again receives the call instruction sent by the first host application, the auxiliary running stack is called again, and the above operation is repeated.

In this embodiment, the host application starts the auxiliary runtime stack, runs the second host application on the auxiliary runtime stack, and forwards the communication message between the first host application and the second host application, thus realizing the real-time communication between the host applications communication.

2 is a schematic flow chart of an instant messaging method between hosted applications according to some embodiments of this application. The method is applied to a first hosted application, and the first hosted application runs on the default running stack of the host application; including The following steps:

Step S21: Send a call instruction through the instant messaging API interface, where the call instruction includes the identification information of the second host application; so that the host application runs the second host application on the auxiliary running stack according to the call instruction; wherein, The host application includes multiple running stacks for running the host application;

Step S22: Receive the execution result returned after executing the call instruction sent by the second host application forwarded by the host application through the instant messaging API interface.

In a preferred implementation of step S21,

Preferably, the host application starts the first running stack in response to the user's triggering of the first hosting application, and runs the first hosting application on the first running stack. The first running stack is the default running stack of the host application.

The first host application sends a call instruction through the instant messaging API interface, and the call instruction is used to instruct to call the second host application.

The host application runs a second host application on the auxiliary execution stack according to the call instruction; the host application forwards the call instruction to the second host application so that the second host application executes the call instruction. The host application receives the execution result returned after the second host application executes the call instruction, and returns the execution result to the first host application.

For specific steps, please refer to the corresponding part of the foregoing embodiment, which will not be repeated here.

In a preferred implementation of step S22,

The first host application receives the execution result returned after the execution of the call instruction sent by the second host application forwarded by the host application through an instant messaging API interface.

Preferably, the first host application receives the operation result through a unified default message receiving interface.

In this embodiment, the first host application sends a call instruction for the second host application, the host application starts the auxiliary run stack, runs the second host application on the auxiliary run stack, and forwards the first host application and the second host application. The communication messages between the boarding applications realize the instant communication between the first boarding application and the second boarding application.

FIG. 3 is a schematic flowchart of an instant messaging method between hosted applications according to some embodiments of this application. The method is applied to a second hosted application, and the second hosted application runs on the auxiliary running stack of the host application; The following steps:

Step S31: Receive and execute the call instruction sent by the first host application running on the default running stack and forwarded by the host application through the instant messaging API interface; wherein the host application includes multiple running stacks for running the host application;

Step S32: Return the execution result through the instant messaging API interface, so that the host application returns the execution result to the first host application.

In a preferred implementation of step S31,

The host application runs the second host application on the auxiliary running stack according to the call instruction sent by the first host application;

Preferably, the host application starts the auxiliary run stack according to the call instruction; the auxiliary run stack is used to run the second host application on the auxiliary run stack while the default run stack runs the first host application. Preferably, there are one or more auxiliary running stacks that can be started by the host application, so that different hosting applications can be run on the one or more auxiliary running stacks; that is, instant communication between multiple hosting applications can be realized .

Preferably, the host application forwards the call instruction to the second host application through its instant messaging API interface; the second host application receives the call instruction through a unified default message receiving interface.

Preferably, the second host application performs corresponding operations according to the data part in the call instruction structure.

Preferably, the data part of the call instruction may be an instruction instructing the second host application to read the data in the data sharing area of the first host application, so as to realize the first host application and the second host application Data transfer between.

In a preferred implementation of step S32,

The second host application returns to the first host application according to the data part in the call instruction structure, that is, the operation result of executing the corresponding operation, through the unified default result return interface.

Preferably, the host application stops the second host application after receiving the execution result returned by the second host application.

In this embodiment, the first host application sends a call instruction for the second host application, the host application starts the auxiliary running stack, and the second host application runs on the auxiliary running stack. The second host application receives the call instruction forwarded by the host application to perform corresponding operations, and feeds back the execution result to the first host application through the host application, thereby realizing instant communication between the first host application and the second host application.

Figure 4 shows a block diagram of an exemplary computer system/server 012 suitable for implementing embodiments of the present invention. The computer system/server 012 shown in FIG. 4 is only an example, and should not bring any limitation to the function and application scope of the embodiment of the present invention.

As shown in Figure 4, the computer system/server 012 is represented in the form of a general-purpose computing device. The components of the computer system/server 012 may include, but are not limited to: one or more processors or processing units 016, a system memory 028, and a bus 018 connecting different system components (including the system memory 028 and the processing unit 016).

The bus 018 represents one or more of several types of bus structures, including a memory bus or a memory controller, a peripheral bus, a graphics acceleration port, a processor, or a local bus using any bus structure among multiple bus structures. For example, these architectures include but are not limited to industry standard architecture (ISA) bus, microchannel architecture (MAC) bus, enhanced ISA bus, Video Electronics Standards Association (VESA) local bus, and peripheral component interconnection ( PCI) bus.

The computer system/server 012 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by the computer system/server 012, including volatile and nonvolatile media, removable and non-removable media.

The system memory 028 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 030 and/or cache memory 032. The computer system/server 012 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. For example only, the storage system 034 may be used to read and write non-removable, non-volatile magnetic media (not shown in FIG. 4, usually referred to as "hard drives"). Although not shown in FIG. 4, a disk drive for reading and writing to removable non-volatile disks (such as "floppy disks") and a removable non-volatile optical disk (such as CD-ROM, DVD-ROM) can be provided. Or other optical media) read and write optical disc drives. In these cases, each drive can be connected to the bus 018 through one or more data media interfaces. The memory 028 may include at least one program product, and the program product has a set (for example, at least one) program modules, which are configured to perform the functions of the embodiments of the present invention.

A program/utility tool 040 with a set of (at least one) program module 042 can be stored in, for example, the memory 028. Such program module 042 includes, but is not limited to, an operating system, one or more host applications, and other programs Modules and program data, each of these examples or some combination may include the realization of a network environment. The program module 042 generally executes the functions and/or methods in the described embodiments of the present invention.

The computer system/server 012 can also communicate with one or more external devices 014 (such as a keyboard, pointing device, display 024, etc.). In the present invention, the computer system/server 012 communicates with an external radar device, and can also communicate with one or Multiple devices that enable users to interact with the computer system/server 012, and/or communicate with any devices that enable the computer system/server 012 to communicate with one or more other computing devices (such as network cards, modems, etc.) Communication. This communication can be performed through an input/output (I/O) interface 022. In addition, the computer system/server 012 can also communicate with one or more networks (for example, a local area network (LAN), a wide area network (WAN), and/or a public network, such as the Internet) through the network adapter 020. As shown in FIG. 4, the network adapter 020 communicates with other modules of the computer system/server 012 through the bus 018. It should be understood that although not shown in FIG. 4, other hardware and/or software modules can be used in conjunction with the computer system/server 012, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems , Tape drives and data backup storage systems.

The processing unit 016 executes the functions and/or methods in the described embodiments of the present invention by running a program stored in the system memory 028.

The above-mentioned computer program may be set in a computer storage medium, that is, the computer storage medium is encoded with a computer program. When the program is executed by one or more computers, one or more computers can execute the above-mentioned embodiments of the present invention. The method flow and/or device operation.

With the development of time and technology, the meaning of media has become more and more extensive, and the dissemination of computer programs is no longer limited to tangible media, and can also be downloaded directly from the Internet. Any combination of one or more computer-readable media can be used. The computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium may be, for example, but not limited to, an electric, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples (non-exhaustive list) of computer-readable storage media include: electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), Erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the above. In this document, the computer-readable storage medium can be any tangible medium that contains or stores a program, and the program can be used by or in combination with an instruction execution system, apparatus, or device.

The computer-readable signal medium may include a data signal propagated in baseband or as a part of a carrier wave, and computer-readable program code is carried therein. This propagated data signal can take many forms, including, but not limited to, electromagnetic signals, optical signals, or any suitable combination of the foregoing. The computer-readable signal medium may also be any computer-readable medium other than the computer-readable storage medium. The computer-readable medium may send, propagate or transmit the program for use by or in combination with the instruction execution system, apparatus, or device .

The program code contained on the computer-readable medium can be transmitted by any suitable medium, including, but not limited to, wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

The computer program code used to perform the operations of the present invention can be written in one or more programming languages or a combination thereof. The programming languages include object-oriented programming languages-such as Java, Smalltalk, C++, and also conventional Procedural programming language-such as "C" language or similar programming language. The program code can be executed entirely on the user's computer, partly on the user's computer, executed as an independent software package, partly on the user's computer and partly executed on a remote computer, or entirely executed on the remote computer or server. In the case of a remote computer, the remote computer can be connected to the user's computer through any kind of network-including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computer (for example, using an Internet service provider to pass the Internet connection).

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the application, not to limit them; although the application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: The technical solutions recorded in the foregoing embodiments are modified, or some of the technical features are equivalently replaced; and these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

A method for instant messaging between boarding applications, applied to a host application, the host application including a plurality of runtime stacks for running the boarding application; characterized in that it includes:

Receiving, through an instant messaging API interface, a call instruction sent by the first host application running on the default runtime stack, where the call instruction includes identification information of the second host application;

According to the call instruction, run the second host application on the auxiliary run stack;

Forward the communication message between the first host application and the second host application through an instant messaging API interface.
The method according to claim 1, wherein the running a second host application on an auxiliary running stack according to the calling instruction comprises:

According to the call instruction, an auxiliary running stack is started, and the second host application is run on the auxiliary running stack.
The method of claim 2, wherein the method further comprises:

According to the identification information of the second host application, it is checked whether there is a corresponding second host application running on the auxiliary running stack; if the corresponding second host application is not running on the auxiliary running stack, the auxiliary running stack is started. The second host application is run on the auxiliary run stack.
The method according to claim 1, wherein the forwarding of the communication message between the first host application and the second host application through an instant messaging API interface comprises:

Forward the call instruction to the second host application through an instant messaging API interface, so that the second host application executes the call instruction;

Receive the execution result returned by the second host application after executing the call instruction through the instant messaging API interface; return the execution result to the first host application.
The method of claim 1, wherein the method further comprises:

Receive the execution result returned after the second host application executes the call instruction through the instant messaging API interface, or receive the call end instruction sent by the first host application; exit the second host application.
The method of claim 5, wherein the method further comprises:

Clear the auxiliary running stack.
An instant communication method between host applications, applied to a first host application, the first host application running on the default running stack of the host application; characterized in that it includes:

Send a call instruction through the instant messaging API interface, the call instruction includes the identification information of the second host application; so that the host application runs the second host application on the auxiliary execution stack according to the call instruction; wherein, the host application Including multiple runtime stacks for running boarding applications;

Receive the execution result returned after executing the call instruction sent by the second host application forwarded by the host application through an instant messaging API interface.
The method according to claim 7, wherein the method further comprises:

Send a call end instruction through the instant messaging API interface, so that the host application stops the second host application and clears the auxiliary running stack.
An instant messaging method between boarding applications, applied to a second boarding application, the second boarding application running on the auxiliary running stack of the host application; characterized by comprising:

Receiving and executing the call instruction sent by the first host application running on the default running stack and forwarded by the host application through the instant messaging API interface; wherein the host application includes multiple running stacks for running the host application;

The execution result is returned through the instant messaging API interface, so that the host application returns the execution result to the first host application.
The method according to claim 9, wherein:

The second host application is run on the auxiliary running stack by the host application according to the call instruction sent by the first host application.
A device, characterized in that the device includes:

One or more processors;

Storage device for storing one or more programs,

When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1-10.
A computer-readable storage medium having a computer program stored thereon, wherein the program is executed by a processor to implement the method according to any one of claims 1-10.