CN109933444A - An instant communication method between boarding applications - Google Patents

Abstract

This application provides the instant communication methods between a kind of boarding application, and the call instruction sent the method includes receiving the first boarding application operated on default running stack by instant messaging api interface, the call instruction includes the second boarding application identification information；According to the call instruction, the second boarding application is run on auxiliary running stack；The communication message between the first boarding application and the second boarding application is forwarded by instant messaging api interface.It can be realized the message transmission between the boarding application on the running stack for operating in host's application, realize real-time interaction.

Description

An instant communication method between boarding applications

【Technical field】

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

【Background technique】

Homestay applications such as Mini Programs are a new open capability, and developers can quickly develop a Mini Program. Mini Programs can be easily acquired and disseminated in host applications such as WeChat and Baidu App, and at the same time have an excellent user experience. Mini Program developers can provide convenient and rich services within Mini Programs, such as reservations, commodity purchases, and games. Therefore, it has been more and more widely used.

However, in the current host application, only one host application can 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 instant interaction cannot be realized between boarding applications.

In one aspect of the present application, an instant messaging method between host applications is provided, which is applied to a host application, where the host application includes a plurality of running stacks for running the host application; the method includes receiving an instant messaging API interface running on a default running stack. The calling instruction sent by the first boarding application on the server, the calling instruction includes the identification information of the second boarding application; according to the calling instruction, the second boarding application is run on the auxiliary running stack; the instant messaging API interface is used to forward the A communication message between the first hosting application and the second hosting application.

Another aspect of the present application provides an instant messaging method between host applications, which is applied to a first host application, where the first host application runs on a default running stack of the host application; including sending a calling 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 running stack according to the call instruction; wherein, the host application includes a plurality of host applications for running the host application Receive the execution result returned after executing the calling instruction and sent by the second host application forwarded by the host application through the instant messaging API interface.

Another aspect of the present application provides an instant messaging method between host applications, which is applied to a second host application, where the second host application runs on an auxiliary running stack of the host application; the method includes receiving and executing an instant messaging API interface through an instant messaging API interface. The calling instruction sent by the first host application running on the default running stack forwarded by the host application; wherein, the host application includes a plurality of 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.

Another aspect of the present application provides an apparatus, the apparatus comprising: one or more processors; a storage device for storing one or more programs, when the one or more programs are executed by the one or more programs The execution of the one or more processors causes the one or more processors to implement any of the above-described methods.

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

As can be seen from the technical solutions, in the above-mentioned embodiments of the present application, instant communication between boarding applications can be realized.

【Description of drawings】

In order to illustrate the technical solutions in the embodiments of the present application more clearly, the following briefly introduces the accompanying drawings that are required in the description of the embodiments or the prior art. Obviously, the drawings in the following description are from the present application. In some embodiments, for those of ordinary skill in the art, other drawings can also be obtained according to these drawings without any creative effort.

FIG. 1 is a schematic flowchart of a method for instant messaging between host applications applied to a host application provided by some embodiments of the present application;

2 is a schematic flowchart of a method for instant messaging between boarding applications applied to a first boarding application provided by some embodiments of the present application;

3 is a schematic flowchart of a method for instant messaging between boarding applications applied to a second boarding application provided by some embodiments of the present application;

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

【Detailed ways】

In order to make the purposes, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in some embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described The embodiments are some of the embodiments of the present application, but not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by persons of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

In addition, the term "and/or" in this article is only an association relationship to describe the associated objects, indicating that there can be three kinds of relationships, for example, A and/or B, it can mean that A exists alone, A and B exist at the same time, There are three cases of B alone. In addition, the character "/" in this document generally indicates that the related objects are an "or" relationship.

1 is a schematic flowchart of a method for instant messaging between host applications provided by some embodiments of the present application. The method is applied to a host application, and the host application includes a plurality of runtime stacks for running the host application; including the following steps :

Step S11, receiving a calling instruction sent by the first hosting application running on the default running stack through the instant messaging API interface, where the calling instruction includes the identification information of the second hosting application;

Step S12, run the second boarding application on the auxiliary running stack according to the calling instruction;

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

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

Wherein, the wireless device includes but is not limited to any intelligent terminal device that can perform human-computer interaction with the user and can realize wireless communication functions, such as smart phones, tablet computers, notebook computers, etc. Of course, it can also be other devices with similar functional device, which is not limited in this embodiment. The intelligent terminal device may adopt any operating system, such as Android operating system, iOS operating system, Windows operating system, and the like.

In a preferred implementation of step S11,

The host application receives 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 the identification information of the second host application.

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 a first run stack in response to a user triggering the first host application, and runs the first host application on the first run stack.

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

Preferably, the calling instruction structure is as follows: instruction header, delimiter, data; wherein,

The instruction header part is used to mark the second hosted application, so that the host application runs the second hosted application; preferably, the instruction header is the AppID of the second hosted application, and different hosted applications use their AppIDs to perform operations. identification;

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 calling instruction through its instant messaging API interface, and there is no need to know the specific receiving and forwarding process of the calling instruction.

In a preferred implementation of step S12,

The host application runs the second host application on the auxiliary operating stack according to the calling instruction;

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

Preferably, after the auxiliary running stack is started, the second hosted application marked by the calling 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 its specific type by parsing the message; if the structure of the message includes an instruction header, a separator, and data, then Indicates that it is a calling instruction; if the message is not a calling instruction, it is processed according to the normal flow.

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

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

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 hosted application is not running on the auxiliary running stack, the auxiliary running stack is started, the second hosted application is run in the auxiliary running stack, and the calling instruction is forwarded to the second hosted application, so that all The second host application executes the calling instruction.

In a preferred embodiment of the present application, after the call ends, the host application stops the host application, clears the auxiliary running stack instead of destroying it, and can quickly run the required host application on the auxiliary running stack.

Preferably, if the second boarding application is not started, it is judged whether there is an auxiliary running stack that has been started and emptied; if so, the second boarding application is directly run on the auxiliary running stack; if it does not exist, the auxiliary running stack is started. stack, and run the second host 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 calling instruction to the second hosting application through the instant messaging API interface, so that the second hosting application executes the calling instruction.

Preferably, the host application forwards the calling instruction to the second hosting application through its instant messaging API interface; so that the second hosting application receives the calling 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 hosting application.

Preferably, the second hosting application performs a corresponding operation according to the data part in the calling instruction structure, and returns the operation result to the first hosting application through a unified default result return interface.

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

The host application receives the execution result returned by the second host application after executing the calling 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 second hosting application performing the corresponding operation according to the data part in the calling instruction structure; it may also be the feedback information returned by the second hosting application after performing the corresponding operation , the feedback information is used to indicate that the operation of the first hosting application has been successfully executed, or that the execution has failed.

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

Preferably, the method further includes:

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

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

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

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

In the above process, the first hosted application running on the default running stack is not affected. When the host application receives the calling instruction sent by the first host application again, it calls the auxiliary runtime stack again, and repeats the above operations.

In this embodiment, the host application starts the auxiliary running stack, runs the second hosting application on the auxiliary running stack, and forwards the communication message between the first hosting application and the second hosting application, so as to realize the instant connection between the hosting applications. communication.

2 is a schematic flowchart of an instant messaging method between host applications provided by some embodiments of the present application, the method is applied to a first host application, and the first host application runs on the default running stack of the host application; including The following steps:

Step S21, sending a calling instruction through the instant messaging API interface, where the calling instruction includes the identification information of the second hosting application; so that the host application runs the second hosting application on the auxiliary running stack according to the calling instruction; The host application includes a plurality of runtime stacks for running the host application;

Step S22: Receive, through an instant messaging API interface, an execution result returned by the second host application and forwarded by the host application after executing the calling instruction.

In a preferred implementation of step S21,

Preferably, the host application starts a first run stack in response to a user triggering the first host application, and runs the first host application on the first run stack. The first run stack is the default run stack of the host application.

The first hosting application sends a calling instruction through an instant messaging API interface, where the calling instruction is used to instruct the second hosting application to be called.

Preferably, the calling instruction structure is as follows: instruction header, delimiter, data; wherein,

The instruction header part is used to mark the second hosted application, so that the host application runs the second hosted application; preferably, the instruction header is the AppID of the second hosted application, and different hosted applications use their AppIDs to perform operations. identification;

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 calling instruction through its instant messaging API interface, and there is no need to know the specific receiving and forwarding process of the calling instruction.

The host application runs the second host application on the auxiliary operating 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 an execution result returned by the second host application after executing the calling instruction, and returns the execution result to the first host application.

For specific steps, reference may be made to the corresponding parts of the foregoing embodiments, which will not be repeated here.

In a preferred implementation of step S22,

The first host application receives, through an instant messaging API interface, an execution result returned by the second host application and sent by the host application after executing the calling instruction.

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

Preferably, the operation result may be the operation result of the second hosting application performing the corresponding operation according to the data part in the calling instruction structure; it may also be the feedback information returned by the second hosting application after performing the corresponding operation , the feedback information is used to indicate that the operation of the first hosting application has been successfully executed, or that the execution has failed.

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

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

In this embodiment, the first hosted application sends a call instruction for the second hosted application, the host application starts an auxiliary running stack, runs the second hosted application on the auxiliary running stack, and forwards the first hosted application and the second hosted application The communication message between the boarding applications realizes the instant communication between the first boarding application and the second boarding application.

3 is a schematic flowchart of a method for instant messaging between host applications provided by some embodiments of the present application, the method is applied to a second host application, and the second host application runs on an auxiliary running stack of the host application; including The following steps:

Step S31, receiving and executing the calling instruction sent by the first host application running on the default running stack forwarded by the host application through the instant messaging API interface; wherein, the host application includes a plurality of running stacks for running the host application;

Step S32, returning 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 operating stack according to the calling instruction sent by the first host application;

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

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

Preferably, the host application forwards the calling instruction to the second hosting application through its instant messaging API interface; the second hosting application receives the calling 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 hosting application.

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

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

In a preferred implementation of step S32,

The second hosting application returns the operation result of executing the corresponding operation according to the data part in the calling instruction structure to the first hosting application through a unified default result return interface.

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 unified default message receiving interface is an instant messaging API interface; the result returning interface is an instant messaging API interface.

Preferably, the operation result may be the operation result of the second hosting application performing the corresponding operation according to the data part in the calling instruction structure; it may also be the feedback information returned by the second hosting application after performing the corresponding operation , the feedback information is used to indicate that the operation of the first hosting application has been successfully executed, or that the execution has failed.

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

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

In this embodiment, the first hosted application sends a call instruction for the second hosted application, the host application starts an auxiliary running stack, and the second hosted application runs on the auxiliary running stack. The second host application receives the calling 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 use in implementing embodiments of the present invention. The computer system/server 012 shown in FIG. 4 is only an example, and should not impose any limitation on the function and scope of use of the embodiments of the present invention.

As shown in FIG. 4, computer system/server 012 takes the form of a general-purpose computing device. Components of computer system/server 012 may include, but are not limited to, one or more processors or processing units 016, system memory 028, and bus 018 connecting various system components including system memory 028 and processing unit 016.

Bus 018 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, a graphics acceleration port, a processor, or a local bus using any of a variety of bus structures. By way of example, these architectures include, but are not limited to, Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MAC) bus, Enhanced ISA bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect ( PCI) bus.

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 both volatile and non-volatile media, removable and non-removable media.

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 . Computer system/server 012 may further include other removable/non-removable, volatile/non-volatile computer system storage media. For example only, storage system 034 may be used to read and write to non-removable, non-volatile magnetic media (not shown in FIG. 4, commonly referred to as a "hard disk drive"). Although not shown in FIG. 4, a disk drive may be provided for reading and writing to removable non-volatile magnetic disks (eg "floppy disks"), as well as removable non-volatile optical disks (eg CD-ROM, DVD-ROM) or other optical media) to read and write optical drives. In these cases, each drive may be connected to bus 018 through one or more data media interfaces. Memory 028 may include at least one program product having a set (eg, at least one) of program modules configured to perform the functions of various embodiments of the present invention.

A program/utility 040 having a set (at least one) of program modules 042, which may be stored, for example, in memory 028, such program modules 042 including, but not limited to, an operating system, one or more hosted applications, other programs Modules and program data, each or some combination of these examples may include an implementation of a network environment. Program modules 042 generally perform the functions and/or methods of the described embodiments of the present invention.

The computer system/server 012 may also communicate with one or more external devices 014 (eg, keyboard, pointing device, display 024, etc.), in the present invention, the computer system/server 012 communicates with external radar devices, and may also communicate with one or more Multiple devices that enable a user to interact with the computer system/server 012, and/or any device (eg, network card, modem, etc.) that enables the computer system/server 012 to communicate with one or more other computing devices communication. Such communication may take place through input/output (I/O) interface 022 . Also, computer system/server 012 may communicate with one or more networks (eg, a local area network (LAN), a wide area network (WAN), and/or a public network such as the Internet) through a network adapter 020 . As shown in FIG. 4 , network adapter 020 communicates with other modules of computer system/server 012 via bus 018 . It should be understood that, although not shown in Figure 4, other hardware and/or software modules may be used in conjunction with 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 programs stored in the system memory 028 .

The above-mentioned computer program may be provided in a computer storage medium, that is, the computer storage medium is encoded with a computer program, which, when executed by one or more computers, causes one or more computers to execute the programs shown in the foregoing 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 network. Any combination of one or more computer-readable media may be employed. The computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus or device, or a combination of any of the above. More specific examples (a non-exhaustive list) of computer readable storage media include: electrical connections having 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 devices, magnetic storage devices, or any suitable combination of the foregoing. In this document, a computer-readable storage medium can be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

A computer-readable signal medium may include a propagated data signal in baseband or as part of a carrier wave, with computer-readable program code embodied thereon. Such propagated data signals may take a variety of forms including, but not limited to, electromagnetic signals, optical signals, or any suitable combination of the foregoing. A computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device .

Program code embodied on a computer readable medium may be transmitted using any suitable medium including, but not limited to, wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Computer program code for carrying out operations of the present invention may be written in one or more programming languages, including object-oriented programming languages—such as Java, Smalltalk, C++, but also conventional Procedural programming language - such as the "C" language or similar programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer, or entirely on the remote computer or server. In the case of a remote computer, the remote computer may 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 may be connected to an external computer (eg, using an Internet service provider through the Internet connect).

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

Claims (12)

1. an instant messaging method between boarding applications, applied to a host application, the host application comprising a plurality of running stacks for running the boarding application; it is characterized in that, comprising: 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 the identification information of the second host application; According to the calling instruction, run the second host application on the auxiliary running stack; The communication message between the first hosting application and the second hosting application is forwarded through the instant messaging API interface. 2. The method according to claim 1, wherein, according to the calling instruction, running the second boarding application on the auxiliary running stack comprises: According to the calling instruction, an auxiliary running stack is started, and the second hosting application is run on the auxiliary running stack. 3. The method according to claim 2, wherein the method further comprises: According to the second boarding application identification information, it is checked whether there is a corresponding second boarding application running on the auxiliary running stack; if the corresponding second boarding application is not running on the auxiliary running stack, the auxiliary running The second host application is run on the auxiliary run stack. 4. The method according to claim 1, wherein the forwarding of the communication message between the first hosting application and the second hosting application through an instant messaging API interface comprises: forwarding the calling instruction to the second hosting application through the instant messaging API interface, so that the second hosting application executes the calling instruction; Receive the execution result returned by the second hosting application after executing the calling instruction through the instant messaging API interface; and return the execution result to the first hosting application. 5. The method according to claim 1, wherein the method further comprises: Receive the execution result returned by the second host application after executing the call instruction through the instant messaging API interface, or receive the call end instruction sent by the first host application; and exit the second host application. 6. The method according to claim 5, wherein the method further comprises: The auxiliary run stack is emptied. 7. An instant messaging method between host applications, applied to a first host application, the first host application running on the default running stack of the host application; it is characterized in that, comprising: 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 operating stack according to the call instruction; wherein, the host application Includes multiple runtime stacks for running hosted applications; The execution result returned after executing the calling instruction and sent by the second host application forwarded by the host application is received through the instant messaging API interface. 8. 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. 9. An instant messaging method between host applications, applied to a second host application, the second host application running on an auxiliary running stack of the host application; it is characterized in that, comprising: 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 a plurality of 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. 10. The method of claim 9, wherein: The second host application is executed by the host application on the auxiliary running stack according to the calling instruction sent by the first host application. 11. A device, characterized in that the device comprises: one or more processors; storage means for storing one or more programs, The one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-10. 12. A computer-readable storage medium on which a computer program is stored, characterized in that, when the program is executed by a processor, the method according to any one of claims 1-10 is implemented.