WO2020177731A1 - Procédé de communication en temps réel entre applications hébergées - Google Patents

Procédé de communication en temps réel entre applications hébergées Download PDF

Info

Publication number
WO2020177731A1
WO2020177731A1 PCT/CN2020/077897 CN2020077897W WO2020177731A1 WO 2020177731 A1 WO2020177731 A1 WO 2020177731A1 CN 2020077897 W CN2020077897 W CN 2020077897W WO 2020177731 A1 WO2020177731 A1 WO 2020177731A1
Authority
WO
WIPO (PCT)
Prior art keywords
host application
running
application
stack
call instruction
Prior art date
Application number
PCT/CN2020/077897
Other languages
English (en)
Chinese (zh)
Inventor
崔英林
Original Assignee
上海连尚网络科技有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 上海连尚网络科技有限公司 filed Critical 上海连尚网络科技有限公司
Publication of WO2020177731A1 publication Critical patent/WO2020177731A1/fr

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/54Interprogram communication

Definitions

  • This application relates to the field of Internet applications, and in particular to an instant messaging recommendation method between boarding applications.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • a device in another aspect of the present application, includes: one or more processors; a storage device for storing one or more programs.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • step S11 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.
  • 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.
  • 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 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.
  • 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.
  • 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.
  • 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.
  • step S12 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.
  • 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.
  • the second host application marked by the call instruction is run on the auxiliary running stack.
  • 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.
  • 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.
  • the host application 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;
  • the call instruction may be forwarded to the second host application, so that the second host application executes the call instruction;
  • 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.
  • 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.
  • 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.
  • the host application calls the second host application in the background, that is, the interface of the first host application remains unchanged.
  • step S13 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.
  • 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.
  • the unified default message receiving interface may be an instant messaging API interface of the second host application.
  • 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.
  • 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.
  • 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.
  • 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.
  • the unified default message receiving interface is an instant messaging API interface
  • the result return interface is an instant messaging API interface
  • the method further includes:
  • the host application stops the second hosting application.
  • the first host application 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.
  • the second host application identification information is the AppID of the second host application.
  • the auxiliary running stack is cleared.
  • the first host application running on the default runtime stack is not affected.
  • 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.
  • 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.
  • FIG. 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.
  • step S21 In a preferred implementation of step S21,
  • 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 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.
  • 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.
  • 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.
  • 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.
  • step S22 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.
  • the first host application receives the operation result through a unified default message receiving interface.
  • 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.
  • the unified default message receiving interface is an instant messaging API interface
  • the result return interface is an instant messaging API interface
  • the first host application 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.
  • the first host application sends a call instruction for the second host application
  • the host application starts the auxiliary run stack
  • 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.
  • step S31 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;
  • 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.
  • the second host application marked by the call instruction is run on the auxiliary running stack.
  • 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.
  • the unified default message receiving interface may be an instant messaging API interface of the second host application.
  • the second host application performs corresponding operations according to the data part in the call instruction structure.
  • 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.
  • step S32 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.
  • 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.
  • the unified default message receiving interface is an instant messaging API interface
  • the result return interface is an instant messaging API interface
  • 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.
  • the host application stops the second host application after receiving the execution result returned by the second host application.
  • the first host application 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.
  • 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.
  • FIG. 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.
  • 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.
  • 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.
  • ISA industry standard architecture
  • MAC microchannel architecture
  • VESA Video Electronics Standards Association
  • PCI peripheral component interconnection
  • 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.
  • 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").
  • a disk drive for reading and writing to removable non-volatile disks such as "floppy disks”
  • a removable non-volatile optical disk such as CD-ROM, DVD-ROM
  • other optical media read and write optical disc drives.
  • 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.).
  • 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.
  • I/O input/output
  • 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.
  • networks for example, a local area network (LAN), a wide area network (WAN), and/or a public network, such as the Internet
  • the network adapter 020 communicates with other modules of the computer system/server 012 through the bus 018.
  • 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.
  • 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.
  • 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.
  • 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.
  • RAM random access memory
  • ROM read-only memory
  • EPROM or flash memory Erasable programmable read-only memory
  • CD-ROM compact disk read-only memory
  • 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.
  • 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).
  • LAN local area network
  • WAN wide area network

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)
  • Telephonic Communication Services (AREA)

Abstract

L'invention concerne un procédé de communication en temps réel entre applications hébergées. Ledit procédé comporte les étapes consistant à recevoir, au moyen d'une interface d'API de communication en temps réel, une instruction d'appel transmise par une première application hébergée en cours d'exécution sur une pile d'exécution par défaut, ladite instruction d'appel comportant les informations d'identifiant d'une seconde application hébergée; exécuter, selon l'instruction d'appel, la seconde application hébergée sur une pile d'exécution auxiliaire; réacheminer, au moyen de l'interface d'API de communication en temps réel, des messages de communication entre la première application hébergée et la seconde application hébergée. La présente invention permet la remise de messages entre des applications hébergées en cours d'exécution sur les piles d'exécution d'une application hôte, et permet un échange en temps réel.
PCT/CN2020/077897 2019-03-07 2020-03-05 Procédé de communication en temps réel entre applications hébergées WO2020177731A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910172844.7 2019-03-07
CN201910172844.7A CN109933444A (zh) 2019-03-07 2019-03-07 一种寄宿应用间的即时通讯方法

Publications (1)

Publication Number Publication Date
WO2020177731A1 true WO2020177731A1 (fr) 2020-09-10

Family

ID=66986634

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/077897 WO2020177731A1 (fr) 2019-03-07 2020-03-05 Procédé de communication en temps réel entre applications hébergées

Country Status (2)

Country Link
CN (1) CN109933444A (fr)
WO (1) WO2020177731A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109933444A (zh) * 2019-03-07 2019-06-25 上海连尚网络科技有限公司 一种寄宿应用间的即时通讯方法
CN112565466B (zh) * 2021-02-20 2021-04-27 支付宝(杭州)信息技术有限公司 跨应用关联用户的方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170337094A1 (en) * 2016-04-08 2017-11-23 Efilecabinet, Inc. Systems, methods, and devices for integrated program interfaces and operation
CN108683700A (zh) * 2018-04-03 2018-10-19 四川新网银行股份有限公司 一种基于微信小程序及金融开放平台的金融能力输出模式
CN109933444A (zh) * 2019-03-07 2019-06-25 上海连尚网络科技有限公司 一种寄宿应用间的即时通讯方法
CN110083465A (zh) * 2019-04-26 2019-08-02 上海连尚网络科技有限公司 一种寄宿应用间的数据传递方法

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8856534B2 (en) * 2010-05-21 2014-10-07 Intel Corporation Method and apparatus for secure scan of data storage device from remote server
CN106598655B (zh) * 2016-12-05 2020-02-14 腾讯科技(深圳)有限公司 应用程序页面处理方法和装置
CN108196930B (zh) * 2018-01-18 2020-04-03 腾讯科技(深圳)有限公司 应用程序处理方法、装置、存储介质和计算机设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170337094A1 (en) * 2016-04-08 2017-11-23 Efilecabinet, Inc. Systems, methods, and devices for integrated program interfaces and operation
CN108683700A (zh) * 2018-04-03 2018-10-19 四川新网银行股份有限公司 一种基于微信小程序及金融开放平台的金融能力输出模式
CN109933444A (zh) * 2019-03-07 2019-06-25 上海连尚网络科技有限公司 一种寄宿应用间的即时通讯方法
CN110083465A (zh) * 2019-04-26 2019-08-02 上海连尚网络科技有限公司 一种寄宿应用间的数据传递方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
WECHAT TEAM: "wx.navigateToMiniProgram(Object object)", WX.NAVIGATETOMINIPROGRAM, 21 October 2018 (2018-10-21), XP009523016 *

Also Published As

Publication number Publication date
CN109933444A (zh) 2019-06-25

Similar Documents

Publication Publication Date Title
WO2021036228A1 (fr) Procédé et appareil de téléversement de fichiers, terminal, serveur, système et moyen de stockage
WO2020216166A1 (fr) Procédé de transfert de données entre des applications d'hébergement
WO2020177698A1 (fr) Procédé et dispositif de communication inter-platformes de mini-programmes et support de stockage informatique
US20200301648A1 (en) Method of operating a shared object in a video call
WO2020177734A1 (fr) Procédé de déclenchement d'application, dispositif informatique et support de stockage
WO2020135245A1 (fr) Procédé et dispositif de traitement d'application d'hébergement et support de stockage lisible par ordinateur
US10693816B2 (en) Communication methods and systems, electronic devices, and computer clusters
CN109947408B (zh) 消息推送方法及装置、存储介质和电子设备
WO2020177697A1 (fr) Procédé de découverte entre des mini-plateformes de programme, dispositif et support d'enregistrement informatique
WO2020177731A1 (fr) Procédé de communication en temps réel entre applications hébergées
US8533734B2 (en) Application programming interface for managing time sharing option address space
WO2021088671A1 (fr) Procédé d'appel d'une fonction de terminal, dispositif et support de stockage informatique
CN113691602B (zh) 基于云手机的业务处理方法、系统、装置、设备及介质
CN114124929A (zh) 跨网络的数据处理方法和装置
WO2019136821A1 (fr) Procédé de sélection de réseau et appareil de terminal, dispositif informatique et support de stockage
CN112769876B (zh) 一种设备通道信息获取方法、装置、设备和介质
US20200220824A1 (en) Method, a device and a storage medium of forwarding voice information in instant messaging
CN107817962B (zh) 一种远程控制方法、装置、控制服务器及存储介质
TW200425691A (en) Time-to-disconnect enforcement when communicating with wireless devices that have transient network addresses
CN110113246B (zh) 一种保护会话隐私的方法
WO2024061308A1 (fr) Procédé de traitement de notification, dispositif terminal, côté serveur et support de stockage informatique
CN107733781B (zh) 一种即时通信的处理方法、设备和计算机存储介质
CN113452948B (zh) 会议终端的控制方法、装置、设备及存储介质
KR102428652B1 (ko) 마이크로소프트 엑셀을 이용한 문자정보처리시스템
CN114827268A (zh) 远程调试方法和设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20767035

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205 DATED 28/10/2021)

122 Ep: pct application non-entry in european phase

Ref document number: 20767035

Country of ref document: EP

Kind code of ref document: A1