CN117784988A - Application connection method and terminal equipment - Google Patents

Abstract

The embodiment of the application continuing method and the terminal equipment can realize the continuing of the uninstalled application on the opposite terminal equipment, thereby improving the user experience. The method is applied to a system comprising a first terminal device and a second terminal device, and comprises the following steps: the first terminal equipment sends a broadcast connection notification to the second terminal equipment; the second terminal equipment obtains 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 clicking operation of the contact button by a user and displays a guiding installation popup window of a second continuous application; the second terminal equipment responds to the operation of the user on the guiding and installing the popup window, installs a second connection application and sends a connection data request message to the first terminal equipment; the first terminal equipment sends connection data of a first connection application to the second terminal equipment based on the connection data request message; the second terminal device receives the connection data and displays the connection data.

Description

Application connection methods and terminal equipment

Technical field

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

Background technique

In a multi-device scenario, the terminal device is divided into a source device and a peer device. 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 with the same account, and the source device and the peer device are in the same LAN, the application on the source device and the peer device can achieve connection by triggering the connection condition by the user. For example, the source device is a computer and the peer device is a mobile phone. The user has logged in to the same account on the computer and mobile phone, and the computer and mobile phone are in the same local area network. If the user plays the video using the video playback software on the computer, the user's mobile phone will The video playback software can play the video synchronously. If the user is editing text on the computer, the text being edited can be displayed simultaneously on the user's mobile phone.

For a certain application, application connection requires that both the source device and the peer device have the application installed. When the application is not installed (or uninstalled) on the peer device, the source device sends an application connection request for the application, and the peer device cannot connect the application, which affects the user experience.

Contents of the invention

This application provides an application connection method and a terminal device, which can realize the connection of applications not installed on the peer device, thereby improving user experience.

In a first aspect, an application connection method is provided, which is applied to a system including a first terminal device and a second terminal device. The user logs in the same account on the first terminal device and the second terminal device, and the first terminal device Being in the same local area network as the second terminal device, the method includes: the first terminal device sends a broadcast connection notification to the second terminal device, the broadcast connection notification is used to request that the first connection application of the first terminal device be connected to the second terminal device. ; The second terminal device receives the above-mentioned broadcast connection notification, obtains the icon of the second connection application based on the broadcast connection notification, and displays the contact button in the form of the icon of the second connection application; the second terminal device responds to the user's response to the above-mentioned touch The click operation of the button displays a guidance installation pop-up window for the second connection application; the second terminal device responds to the user's operation on the above-mentioned guidance installation pop-up window, installs the second connection application, and sends a connection data request message to the first terminal device; Based on the above connection data request message, the first terminal device sends the connection data of the first connection application to the second terminal device; the second terminal device receives the above connection data and displays the connection data.

The application connection method of the embodiment of the present application sends a broadcast connection notification to the opposite device through the first terminal device (that is, the source device) when the second terminal device (ie, the opposite end device) does not install the second connection application. Based on the broadcast connection notification, the peer device obtains the icon of the second connection application and displays the contact button in the form of the icon. The peer device responds to the user's click operation on the contact button, installs the second connection application, and can Realize the connection of uninstalled applications on the peer device, thereby improving user experience.

With reference to the first aspect, in some implementations of the first aspect, the above broadcast connection notification includes: an application identifier of the first connection application and a connection strategy; wherein the connection strategy includes at least one of the following: a connection status identifier, a first connection The package name or process name of the application, the application market listing strategy of the first connected application, and the minimum version that supports 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 that supports the connection application can be represented by the minimum version number that supports the connection application, which is used to indicate the minimum version when the second connection application can be connected.

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 connection application from the cloud server.

It should also be understood that when the second connection application is installed on the second terminal device and the version of the second connection application is greater than or equal to the minimum version of the second connection application that supports connection, the embodiment of the present application considers that the second terminal device The second connection application is installed, otherwise, it is considered that the second terminal device does not have the second connection application installed.

With reference to the first aspect, in some implementations of the first aspect, the above 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 connection broadcast notification sent by the first terminal device also includes the icon of the first connection application. 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 connection application and displays the contact button on the desktop in the form of the icon of the second connection application, the second connection application has not yet been installed.

In connection with the first aspect, in some implementations of the first aspect, the above-mentioned second terminal device responds to the user's operation on the guided installation pop-up window and installs the second connection application, including: when the second connection application is a system application Next, the second terminal device resumes installation of the second connection application in response to the user's operation on the guidance installation pop-up window.

In connection with the first aspect, in some implementations of the first aspect, the above-mentioned second terminal device responds to the user's operation on the guided installation pop-up window and installs the second connection application, including: when the second connection application is a third-party application In this case, in response to the user's operation on the guided installation pop-up window, the second terminal device downloads the installation package of the second connection application from the application market and installs the second connection application.

In conjunction with the first aspect, in some implementations of the first aspect, before sending the connection data request message to the first terminal device, the method includes: the second terminal device displays a contact button on the desktop in the form of an icon of the second connection application. ; Sending a connection data request message to the first terminal device includes: the second terminal device sends a connection data request to the first terminal device in response to the user's click operation on the contact button.

It should be understood that after the second continuation application is installed, the second terminal device displays a contact button on the desktop in the form of an icon of the second continuation application. The user clicks the contact button to open the second continuation application. The second terminal device responds to the user's operation and sends a continuation data request message to the first terminal device.

In a second aspect, an application connection method is provided, which is applied to a system including a first terminal device and a second terminal device. The user logs in the same account on the first terminal device and the second terminal device, and the first terminal device Being in the same local area network as the second terminal device, the method includes: the second terminal device receives a broadcast connection notification from the first terminal device, obtains the icon of the second connection application based on the broadcast connection notification, and uses the icon of the second connection application to The contact button is displayed in the form of The guidance installation pop-up window of the connection application; the second terminal device responds to the user's operation on the above-mentioned guidance installation pop-up window, installs the second connection application, and sends a connection data request message to the first terminal device; the second terminal device receives the connection data request message from the first terminal The connection data of the device's first connection application and displays the connection data.

Combined with the second aspect, in some implementations of the second aspect, the above broadcast connection notification includes: an application identifier of the first connection application and a connection strategy; wherein the connection strategy includes at least one of the following: a connection status identifier, a first connection The package name or process name of the application, the application market listing strategy of the first connected application, and the minimum version that supports the connection.

Combined with the second aspect, in some implementations of the second aspect, 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; In the case of connecting the application, the second terminal device sends the package name and signature information of the second connecting application to the cloud server based on the above broadcast connection notification; the second terminal device receives the package name and signature information of the second connecting application from the cloud server that passes the whitelist verification. icon.

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 second terminal device installs a second follow-up application in response to the user's operation on the above-mentioned boot installation pop-up window, including: when the second follow-up application is a system application, the second terminal device responds to the user's operation on the above-mentioned boot installation pop-up window to resume the installation of the second follow-up application.

In combination with the second aspect, in certain implementations of the second aspect, the second terminal device installs a second succession application in response to the user's operation on the above-mentioned boot installation pop-up window, including: when the second succession application is a third-party application, the second terminal device downloads the installation package of the second succession application from the application market and installs the second succession application in response to the user's operation on the above-mentioned boot installation pop-up window.

In conjunction with the second aspect, in some implementations of the second aspect, before sending the connection data request message to the first terminal device, the method includes: the second terminal device displays a contact point on the desktop in the form of an icon of the second connection application. button; sending a connection data request message to the first terminal device, including: the second terminal device sends a connection data request to the first terminal device in response to the user's click operation on the contact button.

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 performs one-to-one correspondence with the methods/operations/steps/actions described in the above aspects. The module may be a hardware circuit, software, or a combination of hardware circuits. Software Implementation.

In another design, the terminal device is a communication chip, and the communication chip 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, and the communication device may include a transmitter for sending information or data, and a receiver for receiving information or data.

The fourth aspect provides a terminal device including 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 of the possible implementations of the second aspect.

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

Alternatively, 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 on the same chip as the processor, or can be set in different On the chip, the embodiment of the present application does not limit the type of memory and the arrangement of the memory and the processor.

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

The terminal device in the above fourth aspect can be a chip, and the processor can be implemented by hardware or software. When implemented by hardware, the processor can be a logic circuit, an integrated circuit, etc.; when implemented by software, When implemented, 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. The computer-readable storage medium stores a computer program (which can also be called a code, or an instruction). When run on a computer, it causes the computer to execute the above-mentioned second aspect. Any of the possible implementation methods.

Description of drawings

Figure 1 is a schematic diagram of an application scenario according to an embodiment of the present application;

Figure 2 is a schematic structural diagram of a terminal device provided by an embodiment of the present application;

Figure 3 is a schematic diagram of the software structure of the terminal device provided by the embodiment of the present application;

Figure 4 is a schematic diagram of another software structure of a terminal device provided by an embodiment of the present application;

Figure 5 is a schematic flow chart of an application connection method provided by an embodiment of the present application;

Figure 6 is a schematic flow chart of another application connection method provided by an embodiment of the present application;

Figure 7 is a schematic interface diagram of a source device provided by an embodiment of the present application;

Figure 8 is a schematic diagram of an interface change of the peer device provided by the embodiment of the present application;

Figure 9 is another schematic interface diagram of a source device provided by an embodiment of the present application;

Figure 10 is a schematic diagram of another interface change of the peer device provided by the embodiment of the present application;

Figure 11 is a structural block diagram of the connection service manager of the terminal device provided by the embodiment of the present application;

Figure 12 is a schematic flow chart of another application connection method provided by an embodiment of the present application;

Figure 13 is a schematic flow chart of a method for obtaining an icon for a second connection application provided by an embodiment of the present application;

Figure 14 is a schematic block diagram of a terminal device provided by an embodiment of the present application;

Figure 15 is a schematic block diagram of another terminal device provided by 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 facilitate a clear description of 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 basically the same functions and effects. Those skilled in the art can understand that words such as "first" and "second" do not limit the number and execution order, and words such as "first" and "second" do not limit the number and execution order.

It should be noted that in this application, words such as "exemplarily" or "for example" are used to represent examples, illustrations or explanations. Any embodiment or design described herein as "exemplary" or "such as" is not intended to be construed as preferred or advantageous over other embodiments or designs. Rather, the use of the words "exemplarily" or "for example" is intended to present the relevant concepts in a concrete manner.

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, the terminal device is divided into a source device and a peer device. 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 with the same account, and the source device and the peer device are in the same LAN, the application on the source device and the peer device can achieve connection by triggering the connection condition by the user. For example, the source device is a computer and the peer device is a mobile phone. The user has logged in to the same account on the computer and mobile phone, and the computer and mobile phone are in the same local area network. If the user plays the video using the video playback software on the computer, the user's mobile phone will The video playback software can play the video synchronously. If the user is editing text on the computer, the text being edited can be displayed simultaneously 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 the scenario of multi-device application connection, the number of peer devices may be one or more, which is not limited in this embodiment 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.

Figure 2 shows a schematic structural diagram of the terminal device 200.

The terminal device 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, Mobile communication module 250, wireless communication module 260, audio module 270, speaker 270A, receiver 270B, microphone 270C, headphone interface 270D, sensor module 280, button 290, motor 291, indicator 292, camera 293, display screen 294, and user Identification module (subscriber identification module, SIM) card interface 295, etc. The sensor module 280 may include a pressure sensor 280A, a gyro 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, and ambient light. Sensor 280L, bone conduction sensor 280M, etc.

It can be understood that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the terminal device. In other embodiments of the present application, the terminal device may include more or less components than shown in the figures, or some components may be combined, or some components may be separated, or may be arranged differently. The components illustrated 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 based on the instruction operation code and timing signals to complete the control of fetching and executing instructions.

The processor 210 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in processor 210 is cache memory. This memory may hold instructions or data that have been recently used or recycled by processor 210 . If the processor 210 needs to use the instruction or data again, it can be directly called from the above-mentioned memory. Repeated access is avoided and the waiting time of the processor 210 is reduced, thus improving the efficiency of the system.

In some embodiments, processor 210 may include one or more interfaces. The interface may include an integrated circuit (inter-integrated circuit, I2C) interface, an integrated circuit built-in audio (inter-integrated circuitsound, I2S) interface, a pulse code modulation (PCM) interface, and a universal asynchronous receiver (universal asynchronous receiver) /transmitter, UART) interface, mobile industry processor interface (MIPI), general-purpose input/output (GPIO) interface, subscriber identity module (subscriber identity module, SIM) interface, and/or 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 only a schematic illustration and does not constitute a structural limitation on the terminal device. In other embodiments of the present application, the terminal device may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

The terminal device implements display functions through the GPU, the display screen 294, and the application processor. The GPU is an image processing microprocessor and is connected to the display screen 294 and the application processor. GPUs are used to perform mathematical and geometric calculations for graphics rendering. Processor 210 may include one or more GPUs that execute program instructions to generate or alter display information.

The terminal device can realize the shooting function through the ISP, camera 293, video codec, GPU, display screen 294 and 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 the data storage function. Such as saving music, videos, etc. files in external memory card.

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

The terminal device of this application can be used as a source device or as a peer device. The source device can also be called the sender, and the peer device can also be called the receiver. The software system of the terminal device can adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. Figure 3 of the embodiment of this application takes the Android system with a layered architecture as an example to illustrate the software structure of the sending end and the receiving end.

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 can include a series of application packages. As shown in Figure 3, the application package can include third-party applications, software development kit (SDK), Bluetooth, WIFI, memo, video, games and other applications. For example, in the embodiment of this application, in the application layer, the connection application can access the connection service SDK. The connection application can be a system application in the terminal device or a third-party application. Applications such as memos, videos, and games can also be System applications or third-party applications.

The application framework layer provides an application programming interface (API) and programming framework for 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, a view system, etc. Among them, managers can also be called modules 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 this application, the connection service manager may be responsible for the access of the connection application, the authentication of the connection application, the icon management of the connection application, 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 validity of the application. For example, in the embodiment of the present application, the application may be allowed to access the connection service after the authentication service manager passes the verification.

The notification manager allows applications to display notification information in the status bar, which 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 download completion, message reminders, etc. The notification manager can also be notifications that appear in the status bar at the top of the system in the form of charts or scroll bar text, such as notifications for applications running in the background, or notifications that appear on the screen in the form of conversation windows. For example, text information is prompted in the status bar, a prompt sound is emitted, the terminal device vibrates, and the indicator light flashes, etc. For example, in the embodiment of the present application, when the second terminal device receives the connection notification, the notification manager may display the connection notification in the taskbar.

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

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

Content providers are used to implement data sharing functions between different applications, allowing one program to access data in another program while ensuring the security of the accessed data.

The view system can be responsible for the interface drawing and event processing of the application program. For example, in the embodiment of the present application, the view system can be used to process the event processing after the user clicks the notification icon of the subsequent application.

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

The core library contains two parts: one is the functional functions that need to be called by the Java language, and the other is the core library of Android.

The application layer and application framework layer run in virtual machines. The virtual machine executes the java files of the application layer and application framework layer into binary files. The virtual machine is used to perform object life cycle management, stack management, thread management, security and exception management, and garbage collection and other functions.

System libraries can include multiple functional modules. For example: Media Libraries, Function Libraries, graphics processing libraries (for example: 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, composition, layer processing, etc.

The hardware abstraction layer is an abstract layer between the kernel layer and the Android runtime. The hardware abstraction layer can be an encapsulation of the hardware driver and provide a unified interface for calls to upper-layer applications. The hardware abstraction layer can include Bluetooth module, WIFI module, hardware configuration module, etc. For example, in the embodiment of this application, the Bluetooth module and WIFI module in the hardware abstraction layer can shield the specific hardware implementation details of the Bluetooth driver and WIFI driver in the kernel layer. The upper-layer application does not need to know the specific implementation of the kernel layer hardware driver. Bluetooth function and WIFI function can be realized by calling the interface.

The kernel layer is the layer between hardware and software. The kernel layer can include display drivers, camera drivers, audio drivers, Bluetooth drivers, WiFi drivers, central processing unit drivers, etc. For example, in the embodiment of this application, the communication service manager can perform cross-device connections through related modules such as Bluetooth drivers and WiFi drivers to realize self-discovery and self-organizing networks of devices.

The following is an example of the connection data transmission process in the layered framework of the Android system based on the scenario where connection notifications are displayed 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 connection service by accessing the connection service SDK. The connection service SDK can send binding connection service and application registration connection service requests to the connection service manager, thereby realizing data transmission of application registration and binding 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 connection application is successfully registered, the communication service manager can call the Bluetooth module interface and WIFI module interface provided by the hardware abstraction layer to realize the self-discovery and self-organizing network of the device, and realize the communication between terminal devices through the Bluetooth driver and WIFI driver in the kernel layer. Session connection, message delivery, and transmission of continued content, etc.

When the receiving end receives the connection-related data passed by the sending end based on the kernel layer, it can transmit the data 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 conduct signaling transmission 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. Further, 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 receiving end of the embodiment of the present application can also use the Windows system, as shown in Figure 4. Different from the Android system, the layered architecture of the Windows system is mainly divided into user mode and kernel mode. The user mode It can include user application processes, as well as system processes and service processes, etc.; the kernel state can include kernel and device driver layers, as well as hardware abstraction layers, 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.

System processes and service processes can include connection service managers, communication service managers, authentication service managers, system processes, notification managers, window managers, etc., which can provide corresponding services for the execution of user application processes. For the specific functions of processes such as the connection service manager, communication service manager, and authentication service manager related to the embodiments of the present application, please refer to the description of the relevant managers in Android, and will not be described again here.

The kernel layer and device driver layer can include Bluetooth drivers, WiFi drivers, display drivers, etc., and the hardware abstraction layer can include Bluetooth modules, WIFI modules, hardware configuration modules, etc. For the specific function modules, please refer to the relevant descriptions in Android and will not be repeated here.

The interaction process between each module will be described in detail below in conjunction with a system that implements a cross-device content connection method. The following embodiments may be combined with each other or implemented independently, and the same or similar concepts or processes may not be described again in some embodiments.

Figure 5 is a schematic flow chart of an application connection method provided by an embodiment of the present application. This method can be applied to the above scenario 100. The hardware structure of the terminal device involved in this method can be as shown in Figure 2, and the software structure can be as shown in Figure 3 or Figure 4. The first terminal device may correspond to the sending end of FIG. 3 or FIG. 4 , and the second terminal device may correspond to the receiving end of FIG. 3 or FIG. 4 . Both the first terminal device and the second terminal device may include various functional modules for implementing the connection service. For example, they may include a connection service SDK, a connection service manager, a communication service manager, and an authentication service manager.

For the convenience of description, the connection application of the first terminal device will be called the first connection application, the connection service SDK of the first terminal device will be called the first connection service SDK, and the connection service manager of the first terminal device will be called the first connection Service manager, the communication service manager of the first terminal device is called the first communication service manager, and the authentication service manager of the first terminal device is called the first authentication service manager.

The connection application of the second terminal device is called the second connection application, the connection service SDK of the second terminal device is called the second connection service SDK, and the connection service manager of the second terminal device is called the second connection 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 follow-up application and the second follow-up application are the same application. For example, the first follow-up application is a memo, and the second follow-up application is also a memo.

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

The first stage is to continue the registration and binding of the application.

When the first connection application of the first terminal device monitors some user behaviors, the first connection application can access the connection service by calling the registration interface of the first connection service SDK. It can be understood that the first connection application may carry information such as the application package name of the first connection application when registering for the connection service. The user behavior can be for the user to click on the first connected application icon to start the application, or for the user to perform editing and other operations in the first connected application, or for the user to click the play button in the first connected application for video playback, music playback or other operations. Media playback and other operations, and the specific monitored user behavior can be customized by the subsequent application, and the embodiments of this application are not limited here.

In a possible implementation, the first connection service SDK can interact with other function managers through the first connection service manager. For example, the first connection service SDK may 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 may contact the first connection service manager. The first communication service manager interacts and binds the communication service. After the binding is successful, the first connection service manager can receive a binding success message replied by the first communication service manager.

Further, the first connection service manager can bind the authentication service and apply the 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 through data interaction with the cloud authentication server. It can be understood that during the process of binding the authentication service, the cloud authentication server can obtain the user identification (UID) based on the package name of the first connected application, and then perform application authentication based on the UID. When the first connection application is successfully authenticated, the cloud authentication server may store application information such as the icon of the first connection application and return the authentication result to the first connection service manager.

After receiving the authentication result of the first connection application, the first connection service manager will deliver the message to the first connection application. The authentication results 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 continue to be executed; if the first connection application receives the authentication result If the result is authentication failure, it means that the application registration failed and the application connection method will not continue.

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-organizing network through Bluetooth or WIFI, and perform account authentication. Further, the first communication service The manager may send information indicating that the second terminal device is online to the first connection service manager. For example, the information used to indicate that the second terminal device is online may include information such as a device identification (DeviceIdentification, DevID) of the second terminal device.

After the first connection service manager receives the information sent by the first communication service manager to indicate that the second terminal device is online, it can store and manage the information of the second terminal device in order to perform subsequent application data connection. process.

The second stage is the display of the continuation notification.

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

The connection policy is used to determine the devices that can be connected, and each application can correspond to its own connection policy. For example, the application's connection policy can be related to one or more of the following fields:

The connection status identifier, the device type supported by the application, the package name or process name of the first connected application, the application market listing strategy of the first connected application, browser startup parameters, the minimum version that supports the connection, etc.

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

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.

If the first connection application is an application on the Android platform, the connection policy includes the package name of the first connection application on the Android platform; if the first connection application is an application on the windows platform, the connection policy includes the package name of the first connection application on the windows platform. Continue process name. 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 of the second continuation application that can be continuation. Exemplarily, the continuation policy includes that the first continuation application can support a minimum version number of A, or a minimum version of B. 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 can be established between the first communication service manager and the second communication service manager to facilitate application connection-related messaging and data transmission.

After the session path is successfully established, the first communication service manager may indicate to the first connection service manager that the channel is successfully established, and the first connection service manager may send the broadcast connection notification carrying the first connection application according to the broadcast connection notification sent by the first connection application. The broadcast connection notification of the package name and the summary of the connection content and other information is sent to the first communication service manager. The first communication service manager sends the package name of the first connection application and the summary of the connection content and other information to the first communication service manager through the established session path. The second communication service manager further reports information such as the package name of the first connection application and the connection content summary 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 for binding and authentication with the second authentication service manager. The implementation of binding and authentication is the same. The authentication steps in the first terminal device are similar and will not be described again.

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

In one possible implementation, the second connection service manager may search whether the icon of the first connection application is stored locally in the second terminal device based on the obtained 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 The manager can obtain the icon of the first connected application and other related information through the cloud authentication server. Further, 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 can obtain the icon and other related information of the first connection application through the cloud authentication server.

In another possible implementation, the second connection service manager may search the second terminal device for a second connection application with the same package name as the first connection application. If the second connection application can be found, the second connection service manager may notify the desktop launcher to display the connection notification using the icon of the second connection application stored locally on the second terminal device; if the second connection application is not found, the second connection application may be found. The second connection service manager can obtain the icon of the first connection application and other related information by searching the 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. Display the connection notification.

It can be understood that when the desktop launcher controls the display of the connection notification, the connection notification can be displayed in the recent task, taskbar, shortcut window or other interface entry of the second terminal device. The specific method of displaying the connection notification is not specified in the embodiment of this application. Make restrictions. The connection notification may be displayed in the form of a connection application icon, or may be displayed in the form of an application name, a prompt, or other forms. The specific display format of the connection notification is not limited by the embodiments of this application.

The third stage is the acquisition and loading of continued data.

After the second terminal device receives the event that the user clicks the connection application icon, in a possible implementation, if the second connection application is not installed in the second terminal device, the second terminal device may prompt the user to install the second connection application. The specific method of prompting for application installation is not limited in the embodiments of this application. If the second connection application is already installed in the second terminal device, or the installation of the second connection application is completed based on prompts, the following steps can be performed.

The second connection service manager can launch the second connection application and instruct the second connection application to load the transition animation effect. Then the second connection application can start and load the transition animation effect. The transition animation effect can include, for example, "Loading..." etc. Prompt information. Further, the second connection application can access the connection service by calling the registration interface of the second connection service SDK. It can be understood 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 binding communication to the second communication service manager. Service requests. When the second communication service manager is successfully bound, the second communication service manager may 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 connection service message to the second connection service manager. After the second connection service manager successfully registers, the second connection service manager can send the registration success message through the second connection service manager. The service SDK is returned to the second connection application.

During the startup process of the second connection application, the second connection service manager may also send connection request data to the first connection service manager through the session path established between the first terminal device and the second terminal device. When the first connection service manager After receiving the request connection data, the service manager can report the request connection data to the first connection application through the first connection service SDK. Then the first connection application can package and encrypt the connection content and other related connection data, and pass the first connection service SDK to the first connection application. The connection service SDK sends the connection data to the first connection service manager. The first connection service manager can send the connection data to the second connection service manager through the session path established between the first terminal device and the second terminal device. .

Further, the second connection service manager notifies the second connection application of the connection data through the second connection service SDK. After successful registration, the second connection application can load the connection data and control the second terminal device to display the connection data, and send the connection data to the second connection application. The first connection application of a terminal device transmits information indicating successful connection, and then the first connection application can execute processes such as exiting the page of the first connection application.

It should be noted that in the application connection method of the embodiment of the present application, if the first connection application has been registered and bound to the connection service, when the first connection application of the first terminal device monitors some user behaviors, the first connection application The connection application does not need to re-register and bind the connection service, or it is understood that it does not need to execute the above-mentioned first phase. The first connection application can skip the first phase and execute the second and third phases, etc., which will not be described again.

The overall process of the application connection method has been introduced above. The specific connection method for applications not installed on the peer device will be introduced in detail below with reference to Figures 6 to 13.

For a certain application, application connection requires that both the source device and the peer device have the application installed. When the application is not installed (or uninstalled) on the peer device, the source device sends an application connection request for the application, and the peer device cannot connect the application, which affects the user experience. In view of this, this application provides an application connection method, which can realize the connection of applications that are not installed on the peer device, thereby improving user experience.

Figure 6 is a schematic flow chart of another application connection method 600 provided by 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 Figure 2, and the software structure of the terminal device involved in the method can be shown in Figure 3 or Figure 4. The method 600 includes the following steps:

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

For example, when the first terminal device and the second terminal device are powered on, the first terminal device and the second terminal device are logged in with the same account, and the first terminal device and the second terminal device are in the same local area network, The user is editing text or playing a video on the first connection application of the first terminal device. The first terminal device sends a broadcast connection notification to the second terminal device. The broadcast connection notification is used to represent the first connection application request of the first terminal device. Connect the 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.

S602: The second terminal device receives the broadcast connection notification, 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 an 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 the contact button on the desktop in the form of an icon. At this time, the second connection application It has not been installed yet.

Optionally, the second terminal device can obtain the icon of the second connection application through the cloud server.

Optionally, the above broadcast connection notification also includes an icon of the first connection application, and the second terminal device can 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 connection application, and the second terminal device determines whether the second connection application is installed. Since the second connection application is not installed on the second terminal device, the second terminal device displays the guidance of the second connection application. Install pop-ups.

S604: The second terminal device responds to the user's operation on the guidance installation pop-up window and installs the second connection application.

In a possible implementation, if the second connection application is a system application and the user clicks resume on the guidance installation pop-up window, the second terminal device resumes installation of the second connection application in response to the user's operation.

In another possible implementation, if the second connected application is a third-party application, the user clicks download on the guidance installation pop-up window, and the second terminal device responds to the user's operation and jumps to the application market page to download and install.

It should be understood that the above installation of the second connection application is for the case where the second terminal device does not have the second connection application installed.

It should also 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.

S605: The second terminal device sends a data connection request message to the first terminal device.

Specifically, after the second terminal device completes the installation of the second connection application, the second terminal device sends a connection data request message to the first terminal device.

S606: The first terminal device sends the connection data of the first connection application to the second terminal device.

S607: The second terminal device receives the connection data and displays the connection data.

Specifically, the second terminal device receives and displays the connection data to complete the application connection.

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 explanation will be given, taking the first terminal device (ie, the source device) as a tablet, the second terminal device (ie, the peer device) as a mobile phone, and the connected application as a system application (eg, memo).

Figure 7 is a schematic diagram of an interface of a source device provided by an embodiment of the present application, used to introduce a tablet computer as an interface for the source device to respond to user operations. In the interface shown in Figure 7, the user is editing text in the memo, 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 is editing the memo text, a memo connection 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.

The application connection interface when the connected application is a system application is introduced above with reference to Figures 7 and 8. The application connection interface when the connected application is a third-party application (such as WPS Office) is introduced below with reference to Figures 9 and 10.

FIG. 9 is another schematic diagram of an interface of a source device provided by an embodiment of the present application, which is used to introduce a tablet computer as an interface for the source device to respond to user operations. In the interface of Figure 9, the tablet computer opens WPS Office in response to the user's operation. Since WPS Office is already open, it can send a WPS Office connection request to the mobile phone.

Figure 10 is a schematic diagram of another interface change of the peer device provided by an embodiment of the present application, used to introduce the interface changes of the mobile phone as the peer device in response to user operations. In interface a in Figure 10, since the mobile phone receives the WPS Office connection request sent by the tablet, the contact button of WPS Office is displayed in the recent taskbar. The contact button displays the icon of WPS Office and the title "AI Creativity Cultivates the Future" . In addition, the contact button also displays a bright spot (the black dot in interface a in Figure 9) and "from tablet" to remind the user that the WPS Office idea is from a tablet and titled "AI Creativity Cultivates the Future" To connect with the WPS Office of the mobile phone. The user clicks the above-mentioned contact button, and the mobile phone displays the interface b in Figure 10 in response to the user's operation of clicking the contact button. In interface b in Figure 10, the mobile phone desktop displays a guidance installation pop-up window. The user clicks the "Go to Download" button in the guidance installation pop-up window. In response to the user's click on the "Go to Download" button, the mobile phone displays the interface c in Figure 10. . In interface c in Figure 10, the WPS Office page in the application market is displayed, and an "Install" button is displayed on the page. The user clicks the "Install" button, and the mobile phone responds to the user's click on the "Install" button, and displays the image shown in Figure 10. 10 interface d. In interface d in Figure 10, the WPS Office contact button is displayed on the desktop. The user clicks the contact button, and the mobile phone responds to the user's operation by displaying the interface e in Figure 10. In the interface e in Figure 10, the WPS Office homepage is displayed, and "Loading continued content" is displayed. After the content is loaded, the interface f in Figure 10 is displayed. In interface f in Figure 10, the same WPS Office page as on the tablet is displayed.

It should be understood that the contact button for connecting the application can be on the recent taskbar or on the desktop, which is not limited in the embodiment of the present application.

Next, the internal structure of the connection service manager of the terminal device is introduced in conjunction with FIG. 11 .

11 is a block diagram of the connection service manager of a terminal device provided in an embodiment of the present application. The connection service manager of the terminal device includes: a connection broadcast manager, a file transfer manager, an application download manager, and a connection contact manager. Among them, the connection broadcast manager is used to manage the sending of multiple connection broadcasts of multiple devices or the same device in a multi-window scenario. The file transfer manager is used to transmit data such as pictures and text. The application download manager is used to manage downloaded applications and guide the download of applications that are not installed. The connection contact manager is used to determine the installation and version information of the application.

For the sake of ease of description, the connection broadcast manager in the second connection service manager will be referred to as the second connection broadcast manager, the file transfer manager in the second connection service manager will be referred to as the second file transfer manager, the application download manager in the second connection service manager will be referred to as the second application download manager, and the connection contact manager in the second connection service manager will be referred to as the second connection contact manager.

Next, taking the internal device shown in Figure 11 as an example, the specific process of applying the connection method will be further explained.

Figure 12 is a schematic flow chart of another application connection method 1200 provided by the embodiment of the present application. This method 1200 can be applied to the above scenario 100. The hardware structure of the terminal device involved in this method 1200 is shown in Figure 2, and the software structure is shown in Figure 3 or Figure 4. The method 1200 includes the following steps:

S1201. The user is editing text or playing a video in the first connection application of the first terminal device. The first connection application of the first terminal device sends a broadcast connection notification to the connection service manager of the first terminal device. The broadcast connection notification Including: the application identification and connection strategy of the first connection application; wherein the connection strategy includes at least one of the following: connection status identification, package name or process name of the first connection application, application market listing strategy of the first connection application, and support for connection minimal version.

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 on the shelves, 1: Overseas App Market 1, 2: Domestic App Market 1, 3: Domestic App Market 2, 4: Overseas App Market 2",

"AppMarket":[1,2],

"MinVersionCode":"110100121",

"MinVersion":"11.1.0.121"

}

S1202: 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.

S1203: 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.

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

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

S1206: The connection broadcast manager of the second terminal device sends the icon of the second connection application to the desktop launcher of the second terminal device.

S1207: 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.

S1208: In response to the user's click operation on the contact button, the desktop launcher of the second terminal device sends the signature and package name information of the second connection application to the contact point manager of the second terminal device.

S1209: The connection contact manager of the second terminal device receives the signature and package name information, and determines whether the second connection application can be connected by judging whether the second connection application is installed or whether the version of the second connection application supports connection.

When the second connection application has been installed and the version supports connection, the second terminal device directly jumps to the connection interface.

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

S1210: When the second connection application is not installed or the version does not support connection, the connection contact manager of the second terminal device sends the signature and package name information of the second connection application to the application download manager of the second terminal device.

S1211. The application download manager of the second terminal device receives the signature and package name information of the second connection application, and verifies the installation and version of the above-mentioned second connection application by checking the downloaded application and the version information corresponding to the downloaded application. information.

S1212. When the second connection application is not installed or the version does not support connection, the application download manager of the second terminal device brings up the application installation dialog box of the second terminal device to guide the installation of the second connection application.

S1213. The application installation dialog box of the second terminal device determines the type of the second connected application. The type of the second connected application is a system application or a third-party application.

When the second connection application is a system application, the second terminal device executes S1214 to S1224.

S1214. The application installation dialog box of the second terminal device sends a calling message to the management system of the second terminal device.

Optionally, the second terminal device may first display a pop-up window for guiding installation, and then call the management system of the second terminal device in response to the user's click-to-restore operation.

S1215: After receiving the call message, the management system of the second terminal device resumes installing the second follow-up application.

S1216. After the installation of the second connection application is completed, the management system of the second terminal device sends a first installation completion message to the connection broadcast manager of the second terminal device. The first installation completion message is used to indicate that the installation of the second connection application has been completed.

S1217: After receiving the first installation completion message, the connection broadcast manager of the second terminal device sends a first connection data request message to the communication service manager of the second terminal device, requesting the connection of data of the first connection application.

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

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

S1220. After receiving the first connection request message, the connection service manager of the first terminal device sends the first connection data of the first connection application to the communication service manager of the first terminal device. The first connection data is the first connection application. Continuation data.

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

S1222: After receiving the first connection data, the communication service manager of the second terminal device sends the first connection data to the file transfer manager of the second terminal device.

S1223: After receiving the first connection data, the file transfer manager of the second terminal device sends the first connection data to the system application of the second terminal device.

S1224. After receiving the first connection data, the system application of the second terminal device loads and displays the first connection data, and the second connection application completes the connection.

When the second connected application is a third-party application, the second terminal device executes S1225 to S1237.

S1225, when the second connected application is a third-party application, in response to the user's click download operation, the application installation dialog interface of the second terminal device jumps to the application market interface of the second terminal device.

S1226. In the application market interface of the second terminal device, in response to the user's click installation operation, the second terminal device downloads and installs the third-party application.

S1227. After the installation of the second connection application is completed, the application market of the second terminal device sends a second installation completion message to the connection broadcast manager of the second terminal device. The second installation completion message is used to indicate that the third-party application has been installed.

S1228: After receiving the second installation completion message, the connection broadcast manager of the second terminal device sends the second installation completion message to the desktop launcher of the second terminal device.

S1229: After receiving the second installation completion message, the desktop launcher of the second terminal device displays the contact button of the third-party application.

S1230. In response to the user's click button operation, the desktop launcher of the second terminal device sends a second connection data request message to the connection broadcast manager of the second terminal device, requesting the connection of data of the first connection application.

In another possible implementation, after receiving the second installation completion message, the connection broadcast manager of the second terminal device can directly send the second connection data request message to the communication service manager of the second terminal device. Requires the user to click a touch button.

S1231: After receiving the second connection data request message, the connection broadcast manager of the second terminal device sends the second connection data request message to the communication service manager of the second terminal device.

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

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

S1234. After receiving the second connection data request message, the connection service manager of the first terminal device sends the second connection data of the first connection application to the communication service manager of the first terminal device. The second connection data is the first terminal Connection data for third-party applications on the device.

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

S1236: After receiving the second connection data, the communication service manager of the second terminal device sends the second connection data to the file transfer manager of the second terminal device.

S1237: After receiving the second connection data, the file transfer manager of the second terminal device sends the second connection data to the third-party application of the second terminal device.

S1238, after receiving the second connection data, the third-party application of the second terminal device loads and displays the second connection data, and the second connection application completes the connection.

In the application connection method of the embodiment of the present application, when the second terminal device does not install the system application or the third-party application, the second terminal device guides the user to install the system application or the third-party application, and after the installation is completed, the second terminal device Requesting connection data can realize the connection of applications that are not installed on the peer device, thus improving the user experience.

In a possible implementation, the second terminal device can obtain the icon of the second connection application from the first terminal device. Specifically, the broadcast connection notification in S1205 above also includes the icon of the first connection application. The broadcast connection manager of the second terminal device can obtain the icon of the first connection application from the broadcast connection notification and add the icon of the first connection application to the broadcast connection notification. The icon is sent to the desktop launcher as the icon of the second connected application.

In another possible implementation, the second terminal device can obtain the icon of the second connection application from the cloud server. Next, the method for obtaining the icon of the second connection application from the cloud server by the second terminal device will be introduced in detail with reference to FIG. 13 .

FIG. 13 is a schematic flowchart of a method 1300 for obtaining an icon of a second connected application provided by an embodiment of the present application. The method 1300 includes the following steps:

S1301. The connection broadcast manager of the second terminal device determines whether the second connection application is installed locally.

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

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

S1304. After the whitelist verification of the second connection application passes, the cloud server sends the package name and icon information of the second connection application to the connection broadcast 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 functions and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application.

The above, in combination with Figures 6 to 13, 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 14 and 15.

Figure 14 is a terminal device 1400 provided by an embodiment of the present application. The terminal device 1400 includes: a processing module 1401 and a transceiver module 1402. The terminal device 1400 is used to implement the steps corresponding to the second terminal device in the above method 600.

The transceiver module 1402 is configured to: receive a broadcast connection notification from the first terminal device, and obtain an icon of the second connection application based on the broadcast connection notification. The above broadcast connection notification is used to request that the first connection application of the first terminal device be connected to The second terminal device; the processing module 1401 is configured to: display a contact button in the form of an icon of the second connection application; in response to the user's click operation on the above-mentioned contact button, display a guide installation pop-up window of the second connection application; in response to The user operates the above-mentioned guided installation pop-up window to install the second connection application; the transceiver module 1402 is also used to: send a connection data request message to the first terminal device; receive the connection data from the first connection application of the first terminal device ; The processing module 1401 is also used to: display the above-mentioned 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 processing module 1401 is also configured to determine whether the second connection application is installed; the transceiver module 1402 is also configured to: if the second connection application is not installed, based on the above broadcast connection notification, send the second connection application to the cloud server. Receive the package name and signature information of the connected application; receive the icon of the second connected application that passes the whitelist verification from the cloud server.

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

Optionally, the processing module 1401 is also configured to: when the second connected application is a system application, in response to the user's operation on the above-mentioned guide installation pop-up window, resume the installation of the second connected application.

Optionally, the processing module 1401 is also configured to: when the second connected application is a third-party application, in response to the user's operation on the above-mentioned guided installation pop-up window, download the installation package of the second connected application from the application market and install the third connected application. 2. Continue to apply.

Optionally, the processing module 1401 is also configured to: display the contact button on the desktop in the form of an icon of the second connected application; the transceiver module 1402 is also configured to: in response to the user's click operation on the above-mentioned contact button, send a message to the first terminal The device sends a data connection request.

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

The terminal device 1400 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 1402 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 this embodiment of the present application, the terminal device 1400 in Figure 14 may also be a chip or a chip system, such as a system on chip (SOC). Correspondingly, the transceiver module 1402 may be the transceiver circuit of the chip, which is not limited here.

Figure 15 is another terminal device 1500 provided by an embodiment of the present application. The terminal device 1500 includes a processor 1501, a transceiver 1502 and a memory 1503. Among them, the processor 1501, the transceiver 1502 and the memory 1503 communicate with each other through internal connection paths. The memory 1503 is used to store instructions. The processor 1501 is used to execute the instructions stored in the memory 1503 to control the transceiver 1502 to send signals and /or receive a signal.

It should be understood that the terminal device 1500 may be specifically the second terminal device in the above embodiment, and may be used to perform various steps and/or processes corresponding to the second terminal device in the above method embodiment. Optionally, the memory 1503 may include read-only memory and random access memory and provide instructions and data to the processor. A portion of the memory may also include non-volatile random access memory. For example, the memory may also store device type information. The processor 1501 may be used to execute instructions stored in the memory, and when the processor 1501 executes the instructions stored in the memory, the processor 1501 is used to execute each step of the above method embodiment corresponding to the second terminal device. and/or process. The transceiver 1502 may include a transmitter and a receiver. The transmitter may be used to implement the steps and/or processes corresponding to the above-mentioned transceiver for performing sending actions. The receiver may be used to implement the functions corresponding to the above-mentioned transceiver. To perform various steps and/or processes of receiving actions.

It should be understood that in the embodiment of the present application, the processor may be a central processing unit (CPU), or other general-purpose processor, digital signal processor (DSP), or application specific integrated circuit (ASIC). , field programmable gate array (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.

During the implementation process, each step of the above method can be completed by instructions in the form of hardware integrated logic circuits or software in the processor. The steps of the methods disclosed in conjunction with the embodiments of the present application can be directly implemented by a hardware processor for execution, or can be executed by a combination of hardware and software modules in the processor. The software module can be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other mature storage media in this field. The storage medium is located in the memory, and the processor executes the instructions in the memory and completes the steps of the above method in combination with its hardware. To avoid repetition, it will not be 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.

This application also provides a computer program product. The computer program product includes a computer program (which can also be called a code, or an instruction). When the computer program is run on a computer, the computer can execute the first step shown in the above embodiment. Methods corresponding to the two terminal devices.

Those of ordinary skill in the art can appreciate that the modules and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented with 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. Skilled artisans may implement the described functionality using different methods for each specific application, but such implementations should not be considered beyond the scope of this application.

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

In the several embodiments provided in this 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 illustrative. For example, the division of modules is only a logical function division. In actual implementation, there may be other division methods. For example, multiple modules or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, indirect coupling or communication connection of devices or modules, and may be in 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 they may be distributed to multiple network modules. Some or all of the modules can 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 can be integrated into one processing module, or each module can exist physically alone, or two or more modules can 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 is essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program code. .

The above are only specific implementation modes of the present application, but the protection scope of the embodiments of the present application is not limited thereto. Any person familiar with the technical field can easily think of changes within the technical scope disclosed in the embodiments of the present application. or replacement, all should be covered by the protection scope of the embodiments of this application. Therefore, the protection scope of the embodiments of the present application shall be subject to the protection scope of the claims.

Claims (17)

1. An application connection method, characterized in that it is applied to a system including a first terminal device and a second terminal device, the user has logged in 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, and the method includes: The first terminal device sends a broadcast connection notification to the second terminal device, where the broadcast connection notification is used to request that the first connection application of the first terminal device be connected to the second terminal device; The second terminal device receives the broadcast connection notification, obtains an icon of the second connection application based on the broadcast connection notification, and displays a contact button in the form of an icon of the second connection application; The second terminal device displays a guidance installation pop-up window for the second connection application in response to the user's click operation on the contact button; The second terminal device responds to the user's operation on the guidance installation pop-up window, installs the second connection application, and sends a connection data request message to the first terminal device; The first terminal device sends the connection data of the first connection application to the second terminal device based on the connection data request message; The second terminal device receives the connection data and displays the connection data. 2. The method according to claim 1, characterized in that the broadcast connection notification comprises: an application identifier and a connection strategy of the first connection application; Wherein, the connection strategy includes at least one of the following: The connection status identifier, the package name or process name of the first connection application, the application market listing policy of the first connection application, and the minimum version supporting the connection. 3. The method according to claim 1 or 2, characterized in that, based on the broadcast connection notification, obtaining the icon of the second connection application includes: The second terminal device determines whether the second connection application is installed; In the case where 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 broadcast connection notification; The cloud server receives the package name and signature information, and performs whitelist verification on the second connection application; If the verification 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. 4. The method according to claim 1 or 2, wherein the broadcast connection notification further includes an icon of the first connection application. 5. The method according to any one of claims 1 to 4, wherein the second terminal device installs the second connection application in response to the user's operation on the guide installation pop-up window, including: When the second connection application is a system application, the second terminal device resumes installation of the second connection application in response to the user's operation on the guidance installation pop-up window. 6. The method according to any one of claims 1 to 4, wherein the second terminal device installs the second connection application in response to the user's operation on the guide installation pop-up window, including: In the case where the second connecting application is a third-party application, the second terminal device downloads the installation package of the second connecting application from the application market and installs the installation package in response to the user's operation on the guided installation pop-up window. Describe the second continuation application. 7. The method according to any one of claims 1 to 6, characterized in that, before sending the connection data request message to the first terminal device, the method further includes: The second terminal device displays the contact button on the desktop in the form of an icon of the second connection application; The sending a data connection request message to the first terminal device includes: The second terminal device sends a connection data request to the first terminal device in response to a user clicking operation on the contact button. 8. An application connection method, characterized in that it is applied to a system including a first terminal device and a second terminal device, the user has logged in 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, and the method includes: The second terminal device receives a broadcast connection notification from the first terminal device, obtains 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, wherein the broadcast connection notification is used to request that the first connection application of the first terminal device be connected to the second terminal device; The second terminal device displays a guidance installation pop-up window for the second connection application in response to the user's click operation on the contact button; The second terminal device responds to the user's operation on the guidance installation pop-up window, installs the second connection application, and sends a connection data request message to the first terminal device; The second terminal device receives connection data from the first connection application of the first terminal device and displays the connection data. 9. The method according to claim 8, characterized in that the broadcast connection notification comprises: an application identifier and a connection strategy of the first connection application; The connection strategy includes at least one of the following: The connection status identifier, the package name or process name of the first connection application, the application market listing strategy of the first connection application, and the minimum version that supports connection. 10. The method according to claim 8 or 9, characterized in that the acquiring the icon of the second connection application based on the broadcast connection notification comprises: The second terminal device determines whether the second connection application is installed; In the case where 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 broadcast connection notification; The second terminal device receives the icon of the second connection application that passes the whitelist verification from the cloud server. 11. The method according to claim 8 or 9, wherein the broadcast connection notification further includes an icon of the first connection application. 12. The method according to any one of claims 8 to 11, characterized in that the second terminal device installs the second follow-up application in response to the user's operation on the installation guidance pop-up window, comprising: When the second connection application is a system application, the second terminal device resumes installation of the second connection application in response to the user's operation on the guidance installation pop-up window. 13. The method according to any one of claims 8 to 11, wherein the second terminal device installs the second connection application in response to the user's operation on the guide installation pop-up window, including: In the case where the second connecting application is a third-party application, the second terminal device downloads the installation package of the second connecting application from the application market and installs the installation package in response to the user's operation on the guided installation pop-up window. Describe the second continuation application. 14. The method according to any one of claims 8 to 13, characterized in that, before sending the connection data request message to the first terminal device, the method further includes: The second terminal device displays the contact button on the desktop in the form of an icon of the second connection application; The sending a data connection request message to the first terminal device includes: The second terminal device sends a connection data request to the first terminal device in response to the user's click operation on the contact button. 15. A terminal device, characterized in that it includes: a processor, the processor is coupled to a memory, the memory is used to store a computer program, and when the processor calls the computer program, the terminal device causes A method as claimed in any one of claims 8 to 14 is performed. 16. A computer-readable storage medium, characterized in that it is used to store a computer program, the computer program comprising instructions for implementing the method according to any one of claims 8 to 14. 17. A computer program product, characterized in that the computer program product comprises computer program code, and when the computer program code is executed on a computer, the computer is enabled to implement the method according to any one of claims 8 to 14.