CN116700552B - Application connection method and terminal device - Google Patents

Abstract

The embodiment of the present application provides an application continuation method and a terminal device, which can realize the continuation of an application not installed on the opposite terminal device, thereby improving the user experience. The method is applied to a system including a first terminal device and a second terminal device, and includes: the first terminal device sends a broadcast continuation notification to the second terminal device; the second terminal device obtains the icon of the second continuation application based on the broadcast continuation notification, and displays a contact button in the form of the icon of the second continuation application; the second terminal device responds to the user's click operation on the contact button, displays a guide installation pop-up window of the second continuation application, and sends a continuation request message to the first terminal device, and the first terminal device sends continuation data and an installation package to the second terminal device based on the continuation request message; the second terminal device receives the continuation data and the installation package; the second terminal device responds to the user's operation on the guide installation pop-up window, installs the second continuation application, and displays the continuation data.

Description

Application connection method and terminal device

Technical Field

The present application relates to the field of terminal technology, and in particular to an application connection method and a terminal device.

Background technique

In a multi-device scenario, terminal devices are divided into source devices and peer devices. The source device is the sending device, and the peer device is the receiving device. When the source device and the peer device are logged in to the same account, and the source device and the peer device are in the same local area network, the applications on the source device and the peer device can be connected by the user triggering the connection conditions. For example, the source device is a computer, and the peer device is a mobile phone. The user logs in to the same account on the computer and the mobile phone, and the computer and the mobile phone are in the same local area network. If the user plays a video on the video player software on the computer, the video player software on the user's mobile phone can play the video synchronously. If the user is editing text on the computer, the text being edited can be displayed synchronously on the user's mobile phone.

For a certain application, application continuation requires that both the source device and the peer device have the application installed. When the peer device does not have (or has uninstalled) the application, the source device sends an application continuation request for the application, and the peer device cannot continue the application, affecting the user experience.

Summary of the invention

The present application provides an application continuation method and a terminal device, which can realize the continuation of applications that are not installed on the opposite device, thereby improving the user experience.

In a first aspect, an application continuation method is provided, which is applied to a system including a first terminal device and a second terminal device, wherein a user logs in to the same account on the first terminal device and the second terminal device, and the first terminal device and the second terminal device are in the same local area network, the method comprising: the first terminal device sends a broadcast continuation notification to the second terminal device, the broadcast continuation notification being used to request that a first continuation application of the first terminal device be continuation to the second terminal device; the second terminal device receives the above-mentioned broadcast continuation notification, obtains an icon of the second continuation application based on the broadcast continuation notification, and displays a contact button in the form of an icon of the second continuation application; the second terminal device displays a guide installation pop-up window of the second continuation application in response to a user clicking the above-mentioned contact button, and sends a continuation request message to the first terminal device, the continuation request message being used to request continuation data of the first continuation application and an installation package of the first continuation application; the first terminal device sends the continuation data and the installation package to the second terminal device based on the above-mentioned continuation request message; the second terminal device receives the above-mentioned continuation data and the above-mentioned installation package; the second terminal device installs the second continuation application in response to the user operating the above-mentioned guide installation pop-up window, and displays the continuation data.

The application continuation method of the embodiment of the present application sends a broadcast continuation notification to the opposite device through the first terminal device (i.e., the source device) when the second continuation application is not installed on the second terminal device (i.e., the opposite device). The opposite device obtains the icon of the second continuation application based on the broadcast continuation notification and displays a contact button in the form of the icon. The opposite device installs the second continuation application in response to the user clicking the contact button, which can realize the continuation of the application that is not installed on the opposite device, thereby improving the user experience.

In combination with the first aspect, in certain implementations of the first aspect, the above-mentioned broadcast connection notification includes: an application identifier and a connection policy of the first connection application; wherein the connection policy includes at least one of the following: a connection status identifier, a package name or process name of the first connection application, an application market listing policy of the first connection application, and a minimum version supporting the connection.

It should be understood that the connection status identifier can be a flag bit used to identify the connection policy status. For example, a flag bit of 0 can indicate that the connection is not supported, a flag bit of 1 can indicate application connection, and a flag bit of 3 can indicate browser connection. It is understood that the specific value of the flag bit can be set arbitrarily as long as it can distinguish different states, and the embodiment of the present application does not make specific limitations.

It should also be understood that if the first continuation application is an application on the Android platform, the continuation policy includes the package name of the first continuation application on the Android platform; if the first continuation application is an application on the Windows platform, the continuation policy includes the continuable process name of the first continuation application on the Windows platform.

The application market listing strategy can be any of the following: not listed, overseas application market 1, domestic application market 1, domestic application market 2, overseas application market 2.

The minimum version of the application that supports the continuation can be represented by the minimum version number of the application that supports the continuation, which is used to represent the minimum version when the second continuation application can be continued.

In combination with the first aspect, in certain implementation methods of the first aspect, the above-mentioned obtaining the icon of the second connection application based on the broadcast connection notification includes: the second terminal device determines whether the second connection application is installed; if the second connection application is not installed, the second terminal device sends the package name and signature information of the second connection application to the cloud server based on the above-mentioned broadcast connection notification; the cloud server receives the above-mentioned package name and signature information, and performs a whitelist check on the second connection application; if the check passes, the cloud server sends the icon of the second connection application to the second terminal device; the second terminal device receives the icon of the second connection application.

It should be understood that the second terminal device can obtain the icon of the second follow-up application from the cloud server.

In combination with the first aspect, in some implementations of the first aspect, the broadcast connection notification further includes an icon of the first connection application.

It should be understood that the second terminal device can obtain the icon of the second connection application from the first terminal device. The broadcast connection notification sent by the first terminal device also includes the icon of the first connection application, and the second terminal device receives the icon of the first connection application and uses the icon of the first connection application as the icon of the second connection application.

It should be understood that when the second terminal device obtains the icon of the second continuation application and displays the contact button on the desktop in the form of the icon of the second continuation application, the second continuation application has not been installed.

In combination with the first aspect, in certain implementations of the first aspect, the above-mentioned display of a pop-up window to guide the installation of the second continuation application and sending a continuation request message to the first terminal device include: when the second terminal device has not installed the second continuation application, the second terminal device displays a pop-up window to guide the installation of the second continuation application and sends a continuation request message to the first terminal device.

In a second aspect, an application continuation method is provided, which is applied to a system including a first terminal device and a second terminal device, a user logs in to the same account on the first terminal device and the second terminal device, and the first terminal device and the second terminal device are in the same local area network, the method comprising: the second terminal device receives a broadcast continuation notification from the first terminal device, the broadcast continuation notification is used to request that a first continuation application of the first terminal device be connected to the second terminal device; the second terminal device obtains an icon of the second continuation application based on the above-mentioned broadcast continuation notification, and displays a contact button in the form of an icon of the second continuation application; the second terminal device displays a guide installation pop-up window of the second continuation application in response to a user clicking the contact button; the second terminal device sends a continuation request message to the first terminal device, the continuation request message is used to request the continuation data of the first continuation application and the installation package of the first continuation application; the second terminal device receives the continuation data of the first continuation application and the installation package of the first continuation application from the first terminal device; the second terminal device installs the second continuation application in response to the user operating the above-mentioned guide installation pop-up window, and displays the continuation data.

In combination with the second aspect, in certain implementations of the second aspect, the above-mentioned broadcast connection notification includes: an application identifier and a connection policy of the first connection application; wherein the connection policy includes at least one of the following: a connection status identifier, a package name or process name of the first connection application, an application market listing policy of the first connection application, and a minimum version that supports the connection.

In combination with the second aspect, in certain implementation methods of the second aspect, the above-mentioned obtaining the icon of the second continuation application based on the broadcast continuation notification includes: the second terminal device determines whether the second continuation application is installed; if the second continuation application is not installed, the second terminal device sends the package name and signature information of the second continuation application to the cloud server based on the above-mentioned broadcast continuation notification; the second terminal device receives the icon of the second continuation application that has passed the whitelist verification from the cloud server.

In combination with the second aspect, in some implementations of the second aspect, the broadcast connection notification further includes an icon of the first connection application.

In combination with the second aspect, in certain implementations of the second aspect, the above-mentioned display of a pop-up window to guide the installation of the second continuation application and sending a continuation request message to the first terminal device include: when the second terminal device has not installed the second continuation application, the second terminal device displays a pop-up window to guide the installation of the second continuation application and sends a continuation request message to the first terminal device.

In a third aspect, a terminal device is provided, which is used to execute the method in any possible implementation of the second aspect. Specifically, the terminal device includes a module for executing the method in any possible implementation of the second aspect.

In one design, the terminal device may include a module that executes the methods/operations/steps/actions described in the second aspect above, and the module may be a hardware circuit, software, or a combination of hardware circuit and software.

In another design, the terminal device is a communication chip, which may include an input circuit or interface for sending information or data, and an output circuit or interface for receiving information or data.

In another design, the terminal device is a communication device, which may include a transmitter for sending information or data, and a receiver for receiving information or data.

In a fourth aspect, a terminal device is provided, comprising a processor and a memory. The processor is used to read instructions stored in the memory, and can receive signals through a receiver and transmit signals through a transmitter to execute the method in any possible implementation of the second aspect.

Optionally, there are one or more processors and one or more memories.

Optionally, the memory may be integrated with the processor, or the memory may be provided separately from the processor.

In the specific implementation process, the memory can be a non-transitory memory, such as a read-only memory (ROM), which can be integrated with the processor on the same chip or can be set on different chips respectively. The embodiments of the present application do not limit the type of memory and the setting method of the memory and the processor.

It should be understood that the relevant data interaction process, such as sending the connection data request information, can be a process of outputting the indication information from the processor, and receiving the capability information can be a process of receiving the input capability information from the processor. Specifically, the processed output data can be output to the transmitter, and the input data received by the processor can come from the receiver. Among them, the transmitter and the receiver can be collectively referred to as a transceiver.

The terminal device in the fourth aspect mentioned above can be a chip, and the processor can be implemented by hardware or by software. When implemented by hardware, the processor can be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor can be a general-purpose processor, which is implemented by reading the software code stored in the memory. The memory can be integrated in the processor or can be located outside the processor and exist independently.

In a fifth aspect, a computer program product is provided, the computer program product comprising: a computer program (also referred to as code, or instruction), which, when executed, enables a computer to execute a method in any possible implementation of the second aspect.

In a sixth aspect, a computer-readable storage medium is provided, which stores a computer program (also referred to as code or instruction), which, when executed on a computer, enables the computer to execute a method in any possible implementation of the second aspect.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic diagram of an application scenario of an embodiment of the present application;

FIG2 is a schematic diagram of the structure of a terminal device provided in an embodiment of the present application;

FIG3 is a schematic diagram of the software structure of a terminal device provided in an embodiment of the present application;

FIG4 is a schematic diagram of another software structure of a terminal device provided in an embodiment of the present application;

FIG5 is a schematic flow chart of an application connection method provided in an embodiment of the present application;

FIG6 is a schematic flow chart of another application connection method provided in an embodiment of the present application;

FIG7 is a schematic diagram of an interface of a source device provided in an embodiment of the present application;

FIG8 is a schematic diagram of an interface change of a peer device provided in an embodiment of the present application;

FIG9 is a schematic flow chart of another application connection method provided in an embodiment of the present application;

FIG10 is a schematic flow chart of another application connection method provided in an embodiment of the present application;

11 is a schematic flow chart of a method for obtaining an icon of a second subsequent application provided in an embodiment of the present application;

FIG12 is a schematic block diagram of a terminal device provided in an embodiment of the present application;

FIG13 is a schematic block diagram of another terminal device provided in an embodiment of the present application.

Detailed ways

The technical solution in this application will be described below in conjunction with the accompanying drawings.

In order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as "first" and "second" are used to distinguish the same or similar items with substantially the same functions and effects. Those skilled in the art can understand that words such as "first" and "second" do not limit the quantity and execution order, and words such as "first" and "second" do not necessarily limit the difference.

It should be noted that, in this application, words such as "exemplarily" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described as "exemplarily" or "for example" in this application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplarily" or "for example" is intended to present related concepts in a specific way.

In addition, "at least one" means one or more, and "plurality" means two or more. "And/or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and/or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character "/" generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b and c can mean: a, or b, or c, or a and b, or a and c, or b and c, or a, b and c, where a, b, c can be single or multiple.

In a multi-device scenario, terminal devices are divided into source devices and peer devices. The source device is the sending device, and the peer device is the receiving device. When the source device and the peer device are logged in to the same account, and the source device and the peer device are in the same local area network, the applications on the source device and the peer device can be connected by the user triggering the connection conditions. For example, the source device is a computer, and the peer device is a mobile phone. The user logs in to the same account on the computer and the mobile phone, and the computer and the mobile phone are in the same local area network. If the user plays a video on the video player software on the computer, the video player software on the user's mobile phone can play the video synchronously. If the user is editing text on the computer, the text being edited can be displayed synchronously on the user's mobile phone.

To facilitate understanding of the present application, the application scenarios involved in the embodiments of the present application are introduced below in conjunction with FIG. 1 .

Fig. 1 shows a schematic diagram of an application scenario 100 of an embodiment of the present application. The application scenario includes a first terminal device 101 and a second terminal device 102, wherein the first terminal device 101 can be used as a source device, the second terminal device 102 can be used as a peer device, the user logs in to the same account on the first terminal device 101 and the second terminal device 102, and the first terminal device 101 and the second terminal device 102 are in the same local area network, and the first terminal device can connect the application data to the second terminal device 102.

Optionally, the above application scenario 100 further includes a third terminal device 103. The third terminal device 103 can be used as a peer device. If the user logs in to the same account on the first terminal device 101 and the third terminal device 103, and the first terminal device 101 and the third terminal device 103 are in the same local area network, the first terminal device 101 can connect the application data to the third terminal device 103.

It should be understood that in a scenario where multiple devices are connected, the number of peer devices may be one or more, and this is not limited in the embodiments of the present application.

It should also be understood that the present application does not require that the above-mentioned multiple opposite-end devices are all in the same local area network as the source-end device. For example, the above-mentioned first terminal device 101 and the second terminal device 102 may be in one local area network (such as WiFi), and the first terminal device 101 and the third terminal device 103 may be in another local area network (such as Bluetooth). The first terminal device 101 may connect the application data to the second terminal device 102 and the third terminal device 103 respectively.

In order to better understand the terminal device in the embodiment of the present application, the hardware structure of the terminal device in the embodiment of the present application is introduced below.

FIG. 2 shows a schematic structural diagram of a terminal device 200 .

The terminal device 200 may include a processor 210, an external memory interface 220, an internal memory 221, a universal serial bus (USB) interface 230, a charging management module 240, a power management module 241, a battery 242, an antenna 1, an antenna 2, a mobile communication module 250, a wireless communication module 260, an audio module 270, a speaker 270A, a receiver 270B, a microphone 270C, an earphone interface 270D, a sensor module 280, a button 290, a motor 291, an indicator 292, a camera 293, a display screen 294, and a subscriber identification module (SIM) card interface 295, etc. Among them, the sensor module 280 may include a pressure sensor 280A, a gyroscope sensor 280B, an air pressure sensor 280C, a magnetic sensor 280D, an acceleration sensor 280E, a distance sensor 280F, a proximity light sensor 280G, a fingerprint sensor 280H, a temperature sensor 280J, a touch sensor 280K, an ambient light sensor 280L, a bone conduction sensor 280M, etc.

It is understood that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the terminal device 200. In other embodiments of the present application, the terminal device 200 may include more or fewer components than shown in the figure, or combine some components, or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

The processor 210 may include one or more processing units, for example, the processor 210 may include an application processor (AP), a modem processor, a graphics processor (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and/or a neural-network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.

The controller can generate operation control signals according to the instruction operation code and timing signal to complete the control of instruction fetching and execution.

The processor 210 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 210 is a cache memory. The memory may store instructions or data that the processor 210 has just used or cyclically used. If the processor 210 needs to use the instruction or data again, it may be called from the memory. This avoids repeated access, reduces the waiting time of the processor 210, and thus improves the efficiency of the system.

In some embodiments, the processor 210 may include one or more interfaces. The interface may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver/transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input/output (GPIO) interface, a subscriber identity module (SIM) interface, and/or a universal serial bus (USB) interface, etc.

It is understandable that the interface connection relationship between the modules illustrated in the embodiment of the present application is a schematic illustration and does not constitute a structural limitation on the terminal device 200. In other embodiments of the present application, the terminal device 200 may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

The terminal device implements the display function through a GPU, a display screen 294, and an application processor. The GPU is a microprocessor for image processing, which connects the display screen 294 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 210 may include one or more GPUs, which execute program instructions to generate or change display information.

The terminal device can realize the shooting function through the ISP, the camera 293, the video codec, the GPU, the display screen 294 and the application processor.

The external memory interface 220 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the terminal device. The external memory card communicates with the processor 210 through the external memory interface 220 to implement a data storage function. For example, files such as music and videos can be stored in the external memory card.

The internal memory 221 can be used to store computer executable program codes, and the executable program codes include instructions. The internal memory 221 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area may store data created during the use of the terminal device (such as audio data, a phone book, etc.), etc. In addition, the internal memory 221 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc. The processor 210 executes various functional applications and data processing of the terminal device by running instructions stored in the internal memory 221, and/or instructions stored in a memory provided in the processor. For example, the application continuation method of an embodiment of the present application may be executed.

The terminal device of the present application can be used as a source device or as a peer device. The source device can also be called a sender, and the peer device can also be called a receiver. The software system of the terminal device can adopt a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. FIG. 3 of the embodiment of the present application takes the Android system of the layered architecture as an example to illustrate the software structure of the sender and the receiver.

As shown in Figure 3, taking the sending end as an example, the layered architecture divides the software into several layers, each with clear roles and division of labor. Data transmission and communication are carried out between layers through software interfaces. In some embodiments, the Android system is divided into five layers, from top to bottom, namely, the application layer, the application framework layer, the Android runtime (Androidruntime) and the system library, the hardware abstract layer (HAL), and the kernel layer.

The application layer may include a series of application packages. As shown in FIG3 , the application package may include third-party applications, software development kits (SDKs), Bluetooth, WIFI, memos, videos, games and other applications. For example, in the embodiment of the present application, in the application layer, the continuation application may access the continuation service SDK, the continuation application may be a system application in the terminal device, or a third-party application, and the memos, videos, games and other applications may also be system applications or third-party applications.

The application framework layer provides an application programming interface (API) and a programming framework for the applications in the application layer. The application framework layer includes some predefined functions.

As shown in Figure 3, the application framework layer may include a connection service manager, a communication service manager, an authentication service manager, a notification manager, a window manager, a resource manager, a content provider, and a view system, etc. The manager may also be referred to as a module in some application scenarios.

The connection service manager can be responsible for the management of connection tasks and can be the core of the overall connection service framework. For example, in the embodiment of the present application, the connection service manager can be responsible for the access of connection applications, the authentication of connection applications, the icon management of connection applications, and the transmission of connection data across devices.

The communication service manager can be used to realize data transmission across devices. For example, in the embodiment of the present application, the communication service manager can realize security authentication and account authentication of devices with the same account, self-discovery and self-organizing networking of devices, data transmission between devices, and access to communication services.

The authentication service manager may be responsible for verifying the legitimacy of the application. For example, in an embodiment of the present application, the application may be allowed to access the subsequent service after the authentication service manager passes the verification.

The notification manager enables applications to display notification information in the status bar. It can be used to convey notification-type messages and can automatically disappear after a short stay without user interaction. For example, the notification manager is used to notify the completion of downloads, message reminders, etc. The notification manager can also be a notification that appears in the system top status bar in the form of a chart or scroll bar text, such as a notification of an application running in the background, or a notification that appears on the screen in the form of a dialog window. For example, a text message is prompted in the status bar, a prompt tone is issued, the terminal device vibrates, the indicator light flashes, etc. For example, in an embodiment of the present application, when the second terminal device receives a follow-up notification, the notification manager can display the follow-up notification in the taskbar.

The window manager is used to manage window programs. The window manager can obtain the display screen size, determine whether there is a status bar, lock the screen, capture the screen, etc.

Content providers are used to store and retrieve data and make it accessible to applications. The data may include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

The view system includes visual controls, such as controls for displaying text, controls for displaying images, etc. The view system can be used to build applications. A display interface can be composed of one or more views. For example, a display interface including a text notification icon can include a view for displaying text and a view for displaying images.

The phone manager is used to provide communication functions of the terminal device 200, such as management of call status (including connection, disconnection, etc.).

The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, and so on.

Android runtime includes core libraries and virtual machines. Android runtime is responsible for scheduling and management of the Android system.

The core library consists of two parts: one part is the function that needs to be called by the Java language, and the other part is the Android core library.

The application layer and the application framework layer run in a virtual machine. The virtual machine executes the Java files of the application layer and the application framework layer as binary files. The virtual machine is used to perform functions such as object life cycle management, stack management, thread management, security and exception management, and garbage collection.

The system library may include multiple functional modules, such as media libraries, function libraries, graphics processing libraries (such as OpenGL ES), etc.

The media library supports playback and recording of a variety of commonly used audio and video formats, as well as static image files, etc. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

The function library provides developers with API interfaces for multiple services, making it easy for developers to quickly integrate and implement various functions.

The graphics processing library is used to implement graphics drawing, image rendering, synthesis and layer processing.

The hardware abstraction layer is an abstracted structure between the kernel layer and the Android runtime. The hardware abstraction layer can be a package of the hardware driver, providing a unified interface for the call of the upper layer application. The hardware abstraction layer may include a Bluetooth module, a WIFI module, a hardware configuration module, etc. For example, in the embodiment of the present application, the Bluetooth module and the WIFI module in the hardware abstraction layer can shield the specific hardware implementation details of the Bluetooth driver and the WIFI driver in the kernel layer, and the upper layer application can implement the Bluetooth function and the WIFI function by calling the interface without having to know the specific implementation method of the kernel layer hardware driver.

The kernel layer is a layer between hardware and software. The kernel layer may include display drivers, camera drivers, audio drivers, Bluetooth drivers, WiFi drivers, CPU drivers, etc. For example, in the embodiment of the present application, the communication service manager can connect across devices through relevant modules such as Bluetooth drivers and WiFi drivers to achieve self-discovery and self-organizing networking of devices.

The following is an example of the transmission process of connection data in the Android system layered framework, combining the scenario of displaying the connection notification during the application connection process between terminal devices.

As shown in Figure 3, in the application layer of the sending end, the application can realize data transmission with the continuation service by accessing the continuation service SDK. The continuation service SDK can send a continuation service binding and application registration continuation service request to the continuation service manager, thereby realizing the continuation application registration and binding data transmission between the application layer and the application framework layer.

In the application framework layer, the connection service manager can complete the binding of communication services by performing signaling transmission and data transmission with the communication service manager. The connection service manager can also bind authentication services and application authentication with the authentication service manager.

After the follow-up application is successfully registered, the communication service manager can call the Bluetooth module interface and the WIFI module interface provided by the hardware abstraction layer to realize the self-discovery and self-organizing network of the device, and realize the session connection, message transmission, and transmission of the follow-up content between terminal devices through the Bluetooth driver and WIFI driver in the kernel layer.

When the receiving end receives the connection-related data transmitted from the sending end based on the kernel layer, the data can be transmitted to the relevant modules in the hardware abstraction layer. In the application framework layer of the receiving end, the communication service manager can obtain the transmitted connection data through the interface provided in the hardware abstraction layer, and perform signaling and data transmission with the connection service manager. After receiving the connection-related data, the connection service manager can bind the authentication service and apply authentication with the authentication service manager. Furthermore, the connection service manager can instruct the desktop launcher to display the connection notification in the form of an icon.

It can be understood that the sending end or the receiving end of the embodiment of the present application can also adopt the Windows system. As shown in Figure 4, the difference from the Android system is that the layered architecture of the Windows system is mainly divided into user state and kernel state. The user state can include user application processes, system processes, service processes, etc.; the kernel state can include the kernel and device driver layer, as well as the hardware abstraction layer, etc.

The user application process can execute a series of applications. The specific executable application types can be the same as the application types in the application layer of the Android system, which will not be repeated here.

The system process and service process may include a connection service manager, a communication service manager, an authentication service manager, a system process, a notification manager, a window manager, etc., which can provide corresponding services for the execution of user application processes. The functions of the connection service manager, the communication service manager, the authentication service manager and other processes related to the embodiment of the present application can be found in the description of the relevant managers in Android, which will not be repeated here.

The kernel layer and device driver layer may include Bluetooth driver, WiFi driver, display driver, etc. The hardware abstraction layer may include Bluetooth module, WiFi module, hardware configuration module, etc. The functions of specific functional modules can be found in the relevant description in Android, which will not be repeated here.

The following will describe the interaction process between the modules in detail in conjunction with a system for implementing a method for connecting content across devices. The following embodiments may be implemented in combination with each other or independently, and the same or similar concepts or processes may not be described in detail in some embodiments.

FIG5 is a schematic flow chart of an application continuation method provided by an embodiment of the present application. The method can be applied to the above-mentioned scenario 100, and the hardware structure of the terminal device involved in the method can be as described in FIG2, and the software structure can be as shown in FIG3 or FIG4. The first terminal device can correspond to the transmitting end of FIG3 or FIG4, and the second terminal device can correspond to the receiving end of FIG3 or FIG4. The first terminal device and the second terminal device can both include various functional modules for implementing the continuation service, for example, a continuation service SDK, a continuation service manager, a communication service manager, and an authentication service manager, etc.

For the sake of ease of description, the connection application of the first terminal device will be referred to as the first connection application, the connection service SDK of the first terminal device will be referred to as the first connection service SDK, the connection service manager of the first terminal device will be referred to as the first connection service manager, the communication service manager of the first terminal device will be referred to as the first communication service manager, and the authentication service manager of the first terminal device will be referred to as the first authentication service manager.

The continuation application of the second terminal device is called the second continuation application, the continuation service SDK of the second terminal device is called the second continuation service SDK, the continuation service manager of the second terminal device is called the second continuation service manager, the communication service manager of the second terminal device is called the second communication service manager, and the authentication service manager of the second terminal device is called the second authentication service manager.

It should be understood that the first continuation application and the second continuation application correspond to the same, for example, the first continuation application is a memo, and the second continuation application is also a memo.

The implementation process of the application connection method can be divided into three stages: the first stage is the registration and binding of the connection application, the second stage is the display of the connection notification, and the third stage is the acquisition and loading of the connection data. Each stage is described below in conjunction with FIG. 5 .

The first stage is to register and bind the subsequent application.

When the first continuation application of the first terminal device monitors some user behaviors, the first continuation application can access the continuation service by calling the registration interface of the first continuation service SDK. It is understandable that the first continuation application can carry information such as the application package name of the first continuation application when registering the continuation service. The user behavior can be the user clicking the first continuation application icon to start the application, or the user performing editing and other operations in the first continuation application, or the user clicking the play button in the first continuation application to play videos, music or other media. The specific monitored user behavior can be customized by the continuation application, and the embodiments of the present application are not limited here.

In a possible implementation, the first connection service SDK can exchange data with other function managers through the first connection service manager. Exemplarily, the first connection service SDK can send a request to bind the connection service and apply the registration connection service to the first connection service manager. After receiving the request from the first connection service SDK, the first connection service manager can interact with the first communication service manager to bind the communication service. After the binding is successful, the first connection service manager can receive a successful binding message from the first communication service manager.

Furthermore, the first connection service manager can bind the authentication service and perform application authentication by calling the interface provided by the first authentication service manager. After receiving the authentication request, the first authentication service manager can complete the binding and authentication of the first connection application by exchanging data with the cloud authentication server. It can be understood that in the process of binding the authentication service, the cloud authentication server can obtain the user identification (UID) according to the package name of the first connection application, and then perform application authentication according to the UID. When the first connection application is authenticated successfully, the cloud authentication server can store the application information such as the icon of the first connection application, and return the authentication result to the first connection service manager.

After the first connection service manager receives the authentication result of the first connection application, it will pass the message to the first connection application. The authentication result may include authentication success and authentication failure. If the result received by the first connection application is authentication success, it means that the application registration is successful and the application connection method can be continued; if the result received by the first connection application is authentication failure, it means that the application registration fails and the application connection method will not be continued.

After the application registration of the first terminal device is successful, the first communication service manager and the second communication service manager can perform self-discovery and self-networking through Bluetooth or WIFI, as well as account authentication. Furthermore, the first communication service manager can send information indicating that the second terminal device is online to the first connection service manager. For example, the information indicating that the second terminal device is online may include information such as the device identification (DevID) of the second terminal device.

After the first connection service manager receives the information sent by the first communication service manager indicating that the second terminal device is online, the information of the second terminal device can be stored and managed to execute the subsequent application data connection process.

The second stage is the display of the follow-up notification.

When the first connection application is successfully registered, a broadcast connection notification may be periodically sent to the first connection service manager. The broadcast connection notification may carry information such as the package name of the first connection application, the connection policy, and the connection content summary (such as the title). The first connection service manager may confirm the connectable device according to the connection policy of the first connection application.

Exemplarily, when the connection policy includes the device types supported by the application, for example, the connection policy includes that the first connection application can support the implementation of connection services on mobile phones, tablet computers, televisions, computers, etc., then when the first connection service manager confirms that the second terminal device is a mobile phone, tablet computer, television or computer, etc., the first connection service manager can instruct the first communication service manager and the second communication service manager to establish a session path.

Exemplarily, when the continuation policy includes a minimum version number or a minimum version, for example, the continuation policy includes that the first continuation application can support a minimum version number of A, or a minimum version of B, then when the first continuation service manager confirms that the version number of the second continuation application is greater than or equal to A, or the version of the second continuation application is greater than or equal to B, the first continuation service manager can instruct the first communication service manager and the second communication service manager to establish a session path.

A session path may be established between the first communication service manager and the second communication service manager to facilitate application connection-related message delivery and data transmission.

After the session channel is successfully established, the first communication service manager can indicate to the first connection service manager that the channel is successfully established. The first connection service manager can, based on the broadcast connection notification sent by the first connection application, send a broadcast connection notification carrying information such as the package name of the first connection application and a summary of the connection content to the first communication service manager. The first communication service manager sends information such as the package name of the first connection application and a summary of the connection content to the second communication service manager through the established session channel. The second communication service manager further reports information such as the package name of the first connection application and a summary of the connection content to the second connection service manager.

The second connection service manager can parse the package name of the first connection application, and carry the package name information of the first connection application to bind and authenticate with the second authentication service manager. The implementation related to binding and authentication is similar to the authentication steps in the first terminal device, which will not be repeated here.

When the application authentication is successful, the second connection service manager can obtain the application icon through any possible implementation.

In a possible implementation, the second connection service manager can search whether the icon of the first connection application is stored locally in the second terminal device based on the application information such as the package name of the first connection application. If the icon of the first connection application can be found, the second connection service manager can notify the desktop launcher to use the icon of the first connection application to display the connection notification; if the icon of the first connection application is not found, the second connection service manager can obtain the icon of the first connection application and other related information through the cloud authentication server. Furthermore, when the cloud authentication server sends the icon of the first connection application to the second connection service manager, the second connection service manager can store the icon of the first connection application and other related information locally on the second terminal device, and the second connection service manager can notify the desktop launcher to display the connection notification on the second terminal device.

In another possible implementation, the second connection service manager may obtain relevant information such as the icon of the first connection application through the cloud authentication server.

In another possible implementation, the second connection service manager can search for a second connection application with the same package name as the first connection application in the second terminal device. If the second connection application can be found, the second connection service manager can notify the desktop launcher to use the icon of the second connection application stored locally on the second terminal device to display the connection notification; if the second connection application is not found, the second connection service manager can obtain the icon and other related information of the first connection application by searching for application information locally on the second terminal device or in the cloud authentication server, and notify the desktop launcher to use the icon of the first connection application to display the connection notification.

It is understandable that when the desktop launcher controls the display of the continuation notification, the continuation notification can be displayed in the recent tasks, task bar, quick window or other interface entrance of the second terminal device, and the specific way of displaying the continuation notification is not limited by the embodiment of the present application. The continuation notification can be displayed in the form of a continuation application icon, or can be displayed by the application name, prompt or other forms, and the specific way of displaying the continuation notification is not limited by the embodiment of the present application.

The third stage is to obtain and load the subsequent data.

When the second terminal device receives the event that the user clicks the icon of the continuation application, in a possible implementation, if the second continuation application is not installed in the second terminal device, the second terminal device may prompt the user to install the second continuation application. The specific method of prompting the user to install the application is not limited in the embodiment of the present application. If the second continuation application is already installed in the second terminal device, or the installation of the second continuation application is completed based on the prompt, the following steps may be performed.

The second connection service manager can pull up the second connection application and instruct the second connection application to load the transition animation effect, so that the second connection application can start and load the transition animation effect, and the transition animation effect can include prompt information such as "loading...". Further, the second connection application can access the connection service by calling the registration interface of the second connection service SDK. It is understandable that the second connection application can carry information such as the application package name of the second connection application when registering the connection service.

The second connection service SDK can send a request to bind the connection service to the second connection service manager. After receiving the request to bind the connection service, the second connection service manager can send a request to bind the communication service to the second communication service manager. When the second communication service manager is successfully bound, the second communication service manager can send a binding success message to the second connection service SDK through the second connection service manager. After receiving the binding success message, the second connection service SDK sends a registration message to the second connection service manager. After the second connection service manager is successfully registered, the registration success message can be returned to the second connection application through the second connection service SDK.

During the startup of the second continuation application, the second continuation service manager can also send request continuation data to the first continuation service manager through the session path established between the first terminal device and the second terminal device. After the first continuation service manager receives the request continuation data, it can report the request continuation data to the first continuation application through the first continuation service SDK. The first continuation application can package and encrypt related continuation data such as the continuation content, and send the continuation data to the first continuation service manager through the first continuation service SDK. The first continuation service manager can send the continuation data to the second continuation service manager through the session path established between the first terminal device and the second terminal device.

Furthermore, the second continuation service manager notifies the second continuation application of the continuation data through the second continuation service SDK. After successful registration, the second continuation application can load the continuation data and control the second terminal device to display the continuation data, and transmit information indicating the successful continuation to the first terminal device's first continuation application, so that the first continuation application can execute processes such as exiting the page of the first continuation application.

It should be noted that in the application continuation method of the embodiment of the present application, if the first continuation application has already registered and bound to the continuation service, then when the first continuation application of the first terminal device monitors some user behaviors, the first continuation application does not need to re-register and bind to the continuation service, or it is understood that there is no need to execute the above-mentioned first stage, and the first continuation application can skip the first stage and execute the second and third stages, etc., which will not be repeated.

The above is a general introduction to the application connection method. The following is a detailed introduction to the specific connection method for the application not installed on the peer device in conjunction with Figures 6 to 11.

For a certain application, application continuation requires that both the source device and the peer device have the application installed. When the peer device does not have (or has uninstalled) the application, the source device sends an application continuation request for the application, and the peer device cannot continue the application, affecting the user experience. In view of this, the present application provides an application continuation method that can achieve the continuation of an application that is not installed on the peer device, thereby improving the user experience.

FIG6 is a schematic flow chart of another application connection method 600 provided in an embodiment of the present application. The method 600 can be applied to the above scenario 100. The hardware structure of the terminal device involved in the method can be shown in FIG2 , and the software structure of the terminal device involved in the method can be shown in FIG3 or FIG4 . The method 600 includes the following steps:

S601: The first terminal device sends a broadcast connection notification to the second terminal device.

Exemplarily, when the first terminal device and the second terminal device are powered on, the first terminal device and the second terminal device are logged into the same account, and the first terminal device and the second terminal device are in the same local area network, and the user is editing text or playing a video on a first connection application of the first terminal device, the first terminal device sends a broadcast connection notification to the second terminal device, and the broadcast connection notification is used to indicate that the first connection application of the first terminal device requests to connect data to the second connection application of the second terminal device.

Optionally, the broadcast connection notification includes: an application identification (APPID) of the first connection application and a connection policy; wherein the connection policy includes at least one of the following: a connection status identification, a package name or process name of the first connection application, an application market listing policy of the first connection application, and a minimum version supporting the connection.

It should be understood that the above-mentioned first subsequent application can be a system application or a third-party application, and the embodiment of the present application does not limit this.

S602: The second terminal device receives the broadcast connection notification, obtains an icon of a second connection application based on the broadcast connection notification, and displays a contact button on the desktop in the form of the icon of the second connection application.

Specifically, when the second connection application is not installed, the second terminal device obtains the icon of the second connection application based on the broadcast connection notification, and displays a contact button on the desktop in the form of the icon. At this time, the second connection application has not been installed.

It should be understood that if the second continuation application is installed on the second terminal device, and the version of the second continuation application is greater than or equal to the minimum version of the second continuation application that supports continuation, the embodiment of the present application considers that the second terminal device has installed the second continuation application, otherwise, the second terminal device is considered not to have installed the second continuation application. For example, if the minimum version of the second continuation application that supports continuation is v3.0, if the second terminal device has installed v2.0 of the second continuation application and application continuation cannot be achieved, then the second terminal device is considered not to have installed the second continuation application, and if the second terminal device has installed v4.0 of the second continuation application, then the second terminal device is considered to have installed the second continuation application.

Optionally, the second terminal device may obtain the icon of the second follow-up application through the cloud server.

Optionally, the broadcast connection notification further includes an icon of the first connection application. The second terminal device may obtain the icon of the first connection application from the first terminal device and use the icon as the icon of the second connection application.

S603: The second terminal device displays a pop-up window for guiding installation of a second follow-up application in response to a user clicking the touch button.

Specifically, the user clicks the contact button of the second continuation application, and the second terminal device determines whether the second continuation application is installed. Since the second continuation application is not installed on the second terminal device, the second terminal device displays a pop-up window for guiding installation of the second continuation application.

S604, the second terminal device sends a connection request message to the first terminal device, requesting the connection data of the first connection application and the installation package of the first connection application. Correspondingly, the first terminal device receives the connection request message.

S605, the first terminal device sends the connection data and the installation package of the first connection application to the second terminal device based on the connection request message, and correspondingly, the second terminal device receives the connection data and the installation package.

It should be understood that the second terminal device receives the installation package of the first follow-up application and saves the installation package to a designated path.

S606: The second terminal device installs the second connection application in response to the user's operation on the pop-up window guiding the installation, and displays the connection data.

Exemplarily, the user can click the restore button on the installation guide pop-up window, and the second terminal device responds to the user's operation and installs the second continuation application based on the installation package in the specified path. After the installation is complete, the second terminal device displays the continuation data.

The application continuation method of the embodiment of the present application sends a broadcast continuation notification to the opposite device through the first terminal device (i.e., the source device) when the second continuation application is not installed on the second terminal device (i.e., the opposite device). The opposite device obtains the icon of the second continuation application based on the broadcast continuation notification and displays a contact button in the form of the icon. The opposite device installs the second continuation application in response to the user clicking the contact button, which can realize the continuation of the application that is not installed on the opposite device, thereby improving the user experience.

Below, an exemplary description is given by taking the case where the first terminal device (ie, the source device) is a tablet computer, the second terminal device (ie, the opposite device) is a mobile phone, and the connecting application is a system application (eg, a memo).

FIG7 is a schematic diagram of an interface of a source device provided in an embodiment of the present application, which is used to introduce an interface of a tablet computer as a source device responding to user operations. In the interface shown in FIG7, the user is editing text in a memo, and the tablet computer displays the text edited by the user accordingly, and the position of the cursor changes with the position edited by the user. Since the tablet computer is editing the memo text, a memo continuation request can be sent to the mobile phone.

FIG8 is a schematic diagram of an interface change of a peer device provided in an embodiment of the present application, which is used to introduce the interface change of a mobile phone as a peer device in response to a user operation. In interface a of FIG8, since the mobile phone receives a memo continuation request sent by a tablet computer, a contact button of the memo is displayed on the recent taskbar, and the contact button displays the icon of the memo and the title "Let's go far away together". In addition, a bright spot (such as a black dot in interface a of FIG8) and "Tablet" are also displayed on the contact button to prompt the user that the memo from the tablet computer and the title "Let's go far away together" wants to be continued with the memo of the mobile phone. The user clicks the above-mentioned contact button, and the mobile phone responds to the user's click on the contact button operation and displays interface b of FIG8. In interface b of FIG8, a guide installation pop-up window is displayed on the mobile phone desktop. The user clicks "Restore" in the guide installation pop-up window. The mobile phone responds to the user's click restore operation, restores the installation application, and displays interface c of FIG8. In interface c of FIG8, the memo page is displayed, and "Loading the continuation content" is displayed on the memo page. After the content is loaded, interface d of FIG8 is displayed. In interface d of FIG. 8 , the same memo content and the same cursor position are displayed on the tablet computer.

It should be understood that the above examples are only illustrated by taking the continued application as a system application as an example, and the continued application can be a third-party application, such as WeChat, Weibo, etc., and the embodiments of the present application do not limit this. It should also be understood that the contact button of the continued application can be in the recent taskbar or on the desktop, and the embodiments of the present application do not limit this.

Next, the specific process of the application connection method is further described in conjunction with FIG. 9 .

FIG9 is a schematic flow chart of another application connection method 900 provided in an embodiment of the present application. The method 900 can be applied to the above-mentioned scenario 100. The hardware structure of the terminal device involved in the method 900 is shown in FIG2, and the software structure is shown in FIG3 or FIG4. The method 900 includes the following steps:

S901, the user is editing text or playing a video in the first continuation application of the first terminal device, and the first continuation application of the first terminal device sends a broadcast continuation notification to the continuation service manager of the first terminal device, and the broadcast continuation notification includes: the application identifier and the continuation policy of the first continuation application; wherein the continuation policy includes at least one of the following: the continuation status identifier, the package name or process name of the first continuation application, the application market listing policy of the first continuation application, and the minimum version supporting the continuation.

For example, the message body carried by the broadcast connection notification is as follows:

{

"PolicyDescription":"0:mute, or, 1:AppHandoff",

"Policy":1,

"Package":"com.phone.app1",

"AppId":220482320,

"AppMarketDescription":"0: Not available, 1: Overseas application market 1, 2: Domestic application market 1, 3: Domestic application market 2, 4: Overseas application market 2",

"AppMarket":[1,2],

"MinVersionCode":"110100121",

"MinVersion":"11.1.0.121"

}

S902: After receiving the broadcast connection notification, the connection service manager of the first terminal device sends the broadcast connection notification to the communication service manager of the first terminal device.

S903: After receiving the broadcast connection notification, the communication service manager of the first terminal device sends the broadcast connection notification to the communication service manager of the second terminal device.

S904: After receiving the broadcast connection notification, the communication service manager of the second terminal device sends the broadcast connection notification to the connection service manager of the second terminal device.

S905: After receiving the broadcast connection notification, the connection service manager of the second terminal device obtains the icon of the second connection application.

S906: The connection service manager of the second terminal device sends an icon of the second connection application to the desktop launcher of the second terminal device.

S907: The desktop launcher of the second terminal device receives the icon of the second connection application and displays the connection contact button of the second connection application in the form of an icon.

S908: In response to the user's click operation on the touch button, the desktop launcher of the second terminal device notifies the connection service manager of the second terminal device of the latest state of the touch button.

S909: The connection service manager of the second terminal device determines whether the second connection application is installed or whether the version of the second connection application supports the connection.

S910: When the second connection application is not installed or the version does not support connection, the connection service manager of the second terminal device performs a pull-up operation and sends a first call message to the application installation dialog box.

S911, the application installation dialog box receives the first call message, displays a pop-up window for guiding the installation of the second follow-up application, and guides the installation of the second follow-up application.

S912, the connection service manager of the second terminal device sends a connection request message to the communication service manager of the second terminal device, requesting data of the first connection application and an installation package of the first connection application.

The above-mentioned connection request message may include the following information: the package name of the second connection application, the APPID of the second connection application, and indication information that the second connection application is not installed.

S913: After receiving the connection request message, the communication service manager of the second terminal device sends the connection request message to the communication service manager of the first terminal device.

S914: After receiving the connection request message, the communication service manager of the first terminal device sends the connection request message to the connection service manager of the first terminal device.

S915: After receiving the connection request message, the connection service manager of the first terminal device sends the connection request message to the first connection application of the first terminal device.

S916: After receiving the connection request message, the first connection application of the first terminal device packages the connection data and the installation package of the first connection application to obtain a first data packet.

S917: The first connection application of the first terminal device sends the first data message to the connection service manager of the first terminal device.

S918: After receiving the first data packet, the connection service manager of the first terminal device sends the first data packet to the communication service manager of the first terminal device.

S919: After receiving the first data packet, the communication service manager of the first terminal device sends the first data packet to the communication service manager of the second terminal device.

S920: After receiving the first data packet, the communication service manager of the second terminal device sends the first data packet to the connection service manager of the second terminal device.

S921, after receiving the first data packet, the connection service manager of the second terminal device parses the first data packet to obtain connection data and an installation package. Optionally, the second terminal device can save the installation package to a specified path.

S922, in response to the user clicking to restore the installation guidance pop-up window displayed in S911, the application installation dialog box sends a second call message to the management system of the second terminal device.

S923: After receiving the second call message, the management system of the second terminal device installs the second follow-up application based on the installation package.

S924, after the installation of the second connection application is completed, the management system of the second terminal device sends an installation completion message to the connection service manager of the second terminal device, where the installation completion message is used to indicate that the installation of the second connection application is complete.

S925: After receiving the installation completion message, the connection service manager of the second terminal device sends the connection data to the second connection application of the second terminal device.

S926, after receiving the connection data, the second connection application of the second terminal device loads and displays the connection data to complete the connection.

Optionally, after the connection is completed, the second terminal device may also send a connection success notification to the first terminal device, which is similar to FIG. 5 and will not be described in detail here.

The application continuation method of the embodiment of the present application is that when the second terminal device has not installed the application, the second terminal device sends a continuation request message to the first terminal device, the second terminal device receives the continuation data and installation package sent by the first terminal device, completes the installation of the second continuation application, and displays the continuation data, which can realize the continuation of the application that is not installed on the opposite terminal device, thereby improving the user experience.

It should be understood that when the second continuation application has been installed and its version supports continuation, the continuation service manager of the second terminal device sends a continuation data request message to the communication service manager of the second terminal device, which is only used to request continuation data; after the communication service manager of the second terminal device receives the continuation data request message, it sends the above-mentioned continuation data request message to the first continuation application through the communication service manager of the first terminal device and the continuation service manager of the first terminal device; after the first continuation application receives the continuation data request message, it sends the continuation data to the continuation service manager of the first terminal device; after the continuation service manager of the first terminal device receives the continuation data, it sends the continuation data to the second continuation application through the communication service manager of the first terminal device, the communication service manager of the second terminal device and the continuation service manager of the second terminal device; after the second continuation application receives the continuation data, it loads and displays the continuation data.

For the case of the mini program, there is a sandbox isolation between the mini program and the connection service manager, and they cannot communicate directly, so the cloud server is needed to assist in the connection. The specific process of this situation is further explained below in conjunction with Figure 10.

FIG10 is a schematic flow chart of another application connection method 1000 provided in an embodiment of the present application. The method 1000 can be applied to the above scenario 100. The hardware structure of the terminal device involved in the method 1000 is shown in FIG2 , and the software structure is shown in FIG3 or FIG4 . The method 1000 includes the following steps:

S1001, a user is editing text or playing a video in a first connection application of a first terminal device, and the first connection application of the first terminal device sends a broadcast connection notification to a first cloud server.

It should be understood that the first connection application is a small program application and cannot communicate directly with the connection service manager of the first terminal device. It needs to communicate with the connection service manager of the first terminal device through the cloud server.

It should also be understood that the first connection application corresponds to the first cloud server and is provided by the same service provider, and the first cloud server may be a third-party cloud server.

S1002: After receiving the broadcast connection notification, the first cloud server sends the broadcast connection notification to the second cloud server.

It should be understood that the second cloud server is another server different from the first cloud server, and the second cloud server can provide connection services for the terminal device.

S1003, after receiving the broadcast connection notification, the second cloud server sends the broadcast connection notification to the connection service manager of the first terminal device.

S1004: After receiving the broadcast connection notification, the connection service manager of the first terminal device sends a broadcast connection notification to the communication service manager of the first terminal device.

S1005: After receiving the broadcast connection notification, the communication service manager of the first terminal device sends a broadcast connection notification to the communication service manager of the second terminal device.

S1006: After receiving the broadcast connection notification, the communication service manager of the second terminal device sends a broadcast connection notification to the connection service manager of the second terminal device.

S1007: After the connection service manager of the second terminal device receives the broadcast connection notification, the connection service manager of the second terminal device sends the package name and signature information of the first connection application to the second cloud server.

S1008, the second cloud server receives the package name and signature information of the first follow-up application, and performs authentication based on the package name and signature information.

S1009, the second cloud server sends an authentication result to the connection service manager of the second terminal device, where the authentication result is authentication success or authentication failure.

S1010: When the authentication is successful, the connection service manager of the second terminal device obtains an icon of the second connection application.

S1011: The connection service manager of the second terminal device sends an icon of the second connection application to the desktop launcher of the second terminal device.

S1012: The desktop launcher of the second terminal device receives the icon of the second connection application and displays the connection contact button of the second connection application in the form of an icon.

S1013: In response to a user clicking the contact button, the desktop launcher of the second terminal device sends a pull-up notification to the second follow-up application.

S1014: The desktop launcher of the second terminal device sends a connection data request message to the connection service manager of the second terminal device to request connection data. The connection data request message carries the package name of the second connection application.

S1015, after receiving the connection data request message, the connection service manager of the second terminal device sends a connection data request message to the second cloud server.

S1016: After receiving the data connection request message, the second cloud server sends a data connection request message to the first cloud server.

S1017, after receiving the connection data request message, the first cloud server sends a connection data request message to the first connection application of the first terminal device.

S1018: After receiving the connection data request message, the first connection application of the first terminal device sends the connection data to the first cloud server.

S1019, after receiving the connection data, the first cloud server sends the connection data to the second connection application of the second terminal device.

It should be understood that the second connection application and the first connection application are essentially the same application, the only difference is that they are installed on different terminal devices. The second connection application and the first connection application are both provided with services by the first cloud server. Therefore, the first cloud server can directly send connection data to the second connection application of the second terminal device.

S1020: After receiving the connection data, the second connection application loads and displays the connection data to complete the connection.

Optionally, after the connection is completed, the second terminal device may also send a connection success notification to the first terminal device, which is similar to FIG. 5 and will not be described in detail here.

In a possible implementation, the second terminal device may obtain the icon of the second continuation application from the first terminal device. Specifically, the broadcast continuation notification in the above-mentioned application continuation methods 900 and 1000 also includes the icon of the first continuation application. In S905 and S1010, the continuation service manager of the second terminal device may obtain the icon of the first continuation application from the broadcast continuation notification, and send the icon of the first continuation application as the icon of the second continuation application to the desktop launcher.

In another possible implementation, the second terminal device can obtain the icon of the second connection application from the cloud server. In the following, in conjunction with FIG. 11 , a method for the second terminal device to obtain the icon of the second connection application from the cloud server is described in detail.

The application continuation method of the embodiment of the present application enables the second terminal device to receive the continuation data of the first terminal device when the first continuation application cannot directly communicate with the continuation service manager of the first terminal device, thereby achieving the continuation of the application on the opposite device, thereby improving the user experience.

FIG11 is a schematic flow chart of a method 1100 for obtaining an icon of a second subsequent application provided in an embodiment of the present application. The method 1100 comprises the following steps:

S1101, a connection service manager of a second terminal device determines whether a second connection application is installed locally.

S1102: When the second connection application is not installed locally, the connection service manager of the second terminal device sends the package name and signature information of the second connection application to the second cloud server.

S1103, after receiving the package name and signature information of the second follow-up application, the second cloud server performs a whitelist check on the second follow-up application.

S1104, after the whitelist verification of the second connection application is passed, the second cloud server sends the package name and icon information of the second connection application to the connection service manager of the second terminal device.

It should be understood that the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

The above, in combination with Figures 6 to 11, describes in detail the application continuation method of an embodiment of the present application. The following will describe in detail the terminal device of an embodiment of the present application in combination with Figures 12 and 13.

Fig. 12 is a terminal device 1200 provided in an embodiment of the present application, and the terminal device 1200 includes: a transceiver module 1201 and a processing module 1202. The terminal device 1200 is used to implement the steps corresponding to the second terminal device in the above method 600.

The transceiver module 1201 is used to: receive a broadcast connection notification from the first terminal device, the broadcast connection notification is used to request that the first connection application of the first terminal device be connected to the terminal device 1200; the processing module 1202 is used to: based on the broadcast connection notification, obtain the icon of the second connection application, and display the contact button in the form of the icon of the second connection application; in response to the user clicking the above-mentioned contact button, display the guide installation pop-up window of the second connection application; the transceiver module 1201 is also used to: send a connection request message to the first terminal device, the connection request message is used to request the connection data of the first connection application and the installation package of the first connection application; receive the connection data of the first connection application and the installation package of the first connection application from the first terminal device; the processing module 1202 is also used to: in response to the user's operation on the guide installation pop-up window, install the second connection application, and display the connection data.

Optionally, the above-mentioned broadcast connection notification includes: an application identifier and a connection policy of the first connection application; wherein the connection policy includes at least one of the following: a connection status identifier, a package name or process name of the first connection application, an application market listing policy of the first connection application, and a minimum version supporting the connection.

Optionally, the above-mentioned processing module 1202 is also used to: determine whether a second continuation application is installed; the transceiver module 1201 is also used to: when the second continuation application is not installed, based on the above-mentioned broadcast continuation notification, send the package name and signature information of the second continuation application to the cloud server; receive the icon of the second continuation application that has passed the whitelist verification from the cloud server.

Optionally, the broadcast connection notification further includes an icon of the first connection application.

Optionally, the above-mentioned processing module 1202 is also used to: when the terminal device 1200 has not installed the second continuation application, display a pop-up window to guide the installation of the second continuation application; the transceiver module 1201 is also used to: when the terminal device 1200 has not installed the second continuation application, send the above-mentioned continuation request message to the first terminal device.

It should be understood that the terminal device 1200 here is embodied in the form of a functional module. The term "module" here may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a proprietary processor or a group processor, etc.) and a memory for executing one or more software or firmware programs, a merged logic circuit and/or other suitable components that support the described functions. In an optional example, those skilled in the art can understand that the terminal device 1200 can be specifically the second terminal device in the above-mentioned embodiment, and the terminal device 1400 can be used to execute the various processes and/or steps corresponding to the second terminal device in the above-mentioned method embodiment. To avoid repetition, it will not be repeated here.

The terminal device 1200 has the function of implementing the corresponding steps performed by the second terminal device in the above method; the above function can be implemented by hardware, or by hardware executing the corresponding software. The hardware or software includes one or more modules corresponding to the above function. For example, the transceiver module 1202 may include a sending module and a receiving module, the sending module can be used to implement the various steps and/or processes for performing the sending action corresponding to the above transceiver module, and the receiving module can be used to implement the various steps and/or processes for performing the receiving action corresponding to the above transceiver module. The sending module can be replaced by a transmitter, and the receiving module can be replaced by a receiver, respectively performing the sending and receiving operations and related processing operations in each method embodiment.

In the embodiment of the present application, the terminal device 1200 in Fig. 12 may also be a chip or a chip system, such as a system on chip (SOC). Correspondingly, the transceiver module 1202 may be a transceiver circuit of the chip, which is not limited here.

FIG13 is another terminal device 1300 provided in an embodiment of the present application. The terminal device 1300 includes a processor 1301, a transceiver 1302, and a memory 1303. The processor 1301, the transceiver 1302, and the memory 1303 communicate with each other through an internal connection path, the memory 1303 is used to store instructions, and the processor 1301 is used to execute the instructions stored in the memory 1303 to control the transceiver 1302 to send signals and/or receive signals.

It should be understood that the terminal device 1300 can be specifically the second terminal device in the above embodiment, and can be used to execute the various steps and/or processes corresponding to the second terminal device in the above method embodiment. Optionally, the memory 1303 may include a read-only memory and a random access memory, and provide instructions and data to the processor. A part of the memory may also include a non-volatile random access memory. For example, the memory may also store information about the device type. The processor 1301 may be used to execute instructions stored in the memory, and when the processor 1301 executes the instructions stored in the memory, the processor 1301 is used to execute the various steps and/or processes of the above method embodiment corresponding to the second terminal device. The transceiver 1302 may include a transmitter and a receiver, the transmitter may be used to implement the various steps and/or processes corresponding to the above transceiver for performing the sending action, and the receiver may be used to implement the various steps and/or processes corresponding to the above transceiver for performing the receiving action.

It should be understood that in the embodiments of the present application, the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware in a processor or an instruction in the form of software. The steps of the method disclosed in conjunction with the embodiment of the present application can be directly embodied as a hardware processor for execution, or a combination of hardware and software modules in a processor for execution. The software module can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in a memory, and the processor executes the instructions in the memory, and completes the steps of the above method in conjunction with its hardware. To avoid repetition, it is not described in detail here.

The present application also provides a computer-readable storage medium, which is used to store a computer program, and the computer program is used to implement the method corresponding to the second terminal device in the above embodiment.

The present application also provides a computer program product, which includes a computer program (also referred to as code or instruction). When the computer program runs on a computer, the computer can execute the method corresponding to the second terminal device shown in the above embodiment.

Those of ordinary skill in the art will appreciate that the modules and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and modules described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

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

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

In addition, each functional module in each embodiment of the present application may be integrated into one processing module, or each module may exist physically separately, or two or more modules may be integrated into one module.

If the functions are implemented in the form of software function modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

The above is only a specific implementation of the present application, but the protection scope of the embodiments of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the embodiments of the present application, which should be included in the protection scope of the embodiments of the present application. Therefore, the protection scope of the embodiments of the present application should be based on the protection scope of the claims.

Claims (11)

1. An application connection method, applied to a system including a first terminal device and a second terminal device, where a user logs in the same account number on the first terminal device and the second terminal device, and where the first terminal device and the second terminal device are in the same local area network, the method comprising:

the first connection application of the first terminal device sends a broadcast connection notification to a first cloud server, wherein the broadcast connection notification is used for requesting to connect the first connection application of the first terminal device to the second terminal device, the first connection application is an applet application, and the first connection application corresponds to the first cloud server;

after receiving the broadcast connection notification, the first cloud server sends the broadcast connection notification to a second cloud server, wherein the second cloud server is another server different from the first cloud server;

After receiving the broadcast connection notification, the second cloud server sends the broadcast connection notification to a connection service manager of the first terminal equipment;

After receiving the broadcast connection notification, the connection service manager of the first terminal device sends the broadcast connection notification to the communication service manager of the first terminal device;

After receiving the broadcast connection notification, the communication service manager of the first terminal device sends the broadcast connection notification to the second terminal device;

the second terminal equipment receives the broadcast connection notification, acquires an icon of a second connection application based on the broadcast connection notification, and displays a contact button in the form of the icon of the second connection application;

The second terminal equipment responds to the clicking operation of the contact button by a user and sends a connection request message to the second cloud server, wherein the connection request message is used for requesting connection data of the first connection application;

After receiving the connection data request message, the second cloud server sends the connection data request message to the first cloud server;

After receiving the connection data request message, the first cloud server sends the connection data request message to a first connection application of the first terminal equipment;

After receiving the connection data request message, the first connection application of the first terminal equipment sends connection data to the first cloud server;

after receiving the connection data, the first cloud server sends the connection data to a second connection application of the second terminal equipment;

And after the second connection application of the second terminal equipment receives the connection data, loading and displaying the connection data to finish connection.

2. The method of claim 1, wherein broadcasting the connection notification comprises: the application identifier and the connection strategy of the first connection application;

wherein the splicing policy includes at least one of:

the connection state identification, the package name or the process name of the first connection application, the application market shelf policy of the first connection application and the minimum version supporting connection.

3. The method according to claim 1 or 2, wherein the obtaining the icon of the second connection application based on the broadcast connection notification comprises:

the second terminal equipment judges whether the second continuous application is installed or not;

The second terminal equipment sends packet name and signature information of the second connection application to a cloud server based on the broadcast connection notification under the condition that the second connection application is not installed;

The cloud server receives the package name and the signature information and performs white list verification on the second continuous application;

If the verification is passed, the cloud server sends an icon of the second continuous application to the second terminal equipment;

and the second terminal equipment receives the icon of the second continuous application.

4. The method according to claim 1 or 2, wherein the broadcast connection notification further comprises an icon of the first connection application.

5. An application connection method, applied to a system including a first terminal device and a second terminal device, where a user logs in the same account number on the first terminal device and the second terminal device, and where the first terminal device and the second terminal device are in the same local area network, the method comprising:

The second terminal device receives a broadcast connection notification from the first terminal device, where the broadcast connection notification is used for requesting to connect a first connection application of the first terminal device to the second terminal device, the broadcast connection notification is sent to the second terminal device by a first cloud server, a second cloud server, a connection service manager of the first terminal device, and a communication service manager of the first terminal device, the first connection application is an applet application, the first connection application corresponds to the first cloud server, and the second cloud server is another server different from the first cloud server;

The second terminal equipment acquires an icon of a second continuous application based on the broadcast continuous notification, and displays a contact button in the form of the icon of the second continuous application;

The second terminal equipment responds to the click operation of the contact button by a user and sends a connection request message to the second cloud server, wherein the connection request message is used for requesting connection data of the first connection application and an installation package of the first connection application;

After receiving the connection data request message, the second cloud server sends the connection data request message to the first cloud server;

After receiving the connection data request message, the first cloud server sends the connection data request message to a first connection application of the first terminal equipment;

The second terminal equipment receives connection data of a first connection application from the first terminal equipment, wherein the connection data is sent to a second connection application of the second terminal equipment by the first connection application of the first terminal equipment through the first cloud server;

And loading and displaying the connection data by the second connection application of the second terminal equipment to finish connection.

6. The method of claim 5, wherein broadcasting the connection notification comprises: the application identifier and the connection strategy of the first connection application;

wherein the splicing policy includes at least one of:

the connection state identification, the package name or the process name of the first connection application, the application market shelf policy of the first connection application and the minimum version supporting connection.

7. The method according to claim 5 or 6, wherein the obtaining the icon of the second connection application based on the broadcast connection notification comprises:

the second terminal equipment judges whether the second continuous application is installed or not;

The second terminal equipment sends packet name and signature information of the second connection application to a cloud server based on the broadcast connection notification under the condition that the second connection application is not installed;

And the second terminal equipment receives the icon of the second continuous application which passes the white list verification from the cloud server.

8. The method of claim 5 or 6, wherein the broadcast connection notification further comprises an icon for the first connection application.

9. A terminal device, comprising: a processor coupled to a memory for storing a computer program which, when invoked by the processor, causes the terminal device to perform the method of any of claims 5 to 8.

10. A computer readable storage medium storing a computer program comprising instructions for implementing the method of any one of claims 5 to 8.

11. A computer program product comprising computer program code embodied therein, which when run on a computer causes the computer to carry out the method according to any one of claims 5 to 8.