CN117784988A

CN117784988A - Application connection method and terminal equipment

Info

Publication number: CN117784988A
Application number: CN202211192937.4A
Authority: CN
Inventors: 王冬伟
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2022-09-28
Filing date: 2022-09-28
Publication date: 2024-03-29
Also published as: WO2024067205A1

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 method and terminal equipment

Technical Field

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

Background

In the multi-device scenario, the terminal devices are divided into a source device, which is a transmitting end device, and a counterpart device, which is a receiving end device. When the source terminal device and the opposite terminal device log in the same account number and the source terminal device and the opposite terminal device are in the same local area network, the connection condition is triggered by a user, and the application on the source terminal device and the opposite terminal device can realize connection. For example, the source device is a computer, the opposite device is a mobile phone, the user logs in the same account number in the computer and the mobile phone, the computer and the mobile phone are in the same local area network, if the video playing software of the user on the computer plays the video, the video playing software of the user on the mobile phone can synchronously play the video, and if the user is editing text on the computer, the user can synchronously display the edited text on the mobile phone.

For an application, application connection requires that both the source device and the peer device install the application. When the opposite terminal equipment does not install (or uninstall) the application, the source terminal equipment sends an application connection request of the application, and the opposite terminal equipment cannot connect the application, so that user experience is affected.

Disclosure of Invention

The application connection method and the terminal equipment can realize connection of the application which is not installed on the opposite terminal equipment, so that user experience is improved.

In a first aspect, an application connection method is provided, applied to a system including a first terminal device and a second terminal device, where a user logs 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, the method includes: the first terminal device sends a broadcast connection notification to the second terminal device, wherein the broadcast connection notification is used for requesting to connect the first connection application of the first terminal device to the second terminal device; the second terminal equipment receives the broadcast connection notification, acquires an icon of a second connection application based on the broadcast connection notification, and displays a contact button in the form of the icon of the second connection application; the second terminal equipment responds to the clicking operation of the contact button by a user and displays a guide 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 the connection data of the first connection application to the second terminal equipment based on the connection data request message; the second terminal equipment receives the connection data and displays the connection data.

According to the application connection method, under the condition that the second connection application is not installed in the second terminal equipment (namely the opposite terminal equipment), the first terminal equipment (namely the source terminal equipment) sends a broadcast connection notification to the opposite terminal equipment, the opposite terminal equipment obtains an icon of the second connection application based on the broadcast connection notification, a contact button is displayed in the form of the icon, and the opposite terminal equipment responds to the clicking operation of a user on the contact button to install the second connection application, so that connection of the application which is not installed on the opposite terminal equipment can be achieved, and user experience is improved.

With reference to the first aspect, in certain implementation manners of the first aspect, the broadcast connection notification includes: an application identifier and a connection policy of the first connection application; wherein the splicing policy comprises at least one of the following: the connection state identification, the package name or process name of the first connection application, the application market shelf policy of the first connection application, and the minimum version of the support connection.

It should be appreciated that the splice state identifier may be a flag bit for identifying the splice policy state. For example, a flag bit of 0 may indicate that no connection is supported, a flag bit of 1 may indicate that connection is applied, and a flag bit of 3 may indicate that connection is browser. It can be understood that the specific value of the flag bit can be set arbitrarily, and different states can be distinguished, and the embodiment of the application is not limited specifically.

It should also be understood that if the first connection application is an application of the Android platform, the connection policy includes a package name of the first connection application in the Android platform; if the first continuing application is an application of the windows platform, the continuing policy includes a continuing process name of the first continuing application in the windows platform.

The application market place policy may be any of the following: the method comprises the following steps of not putting on shelf, overseas application market 1, domestic application market 2 and overseas application market 2.

The minimum version supporting the splicing application may be represented by a minimum version number supporting the splicing application, for representing the minimum version when the second splicing application is spliceable.

With reference to the first aspect, in some implementations of the first aspect, the obtaining, based on the broadcast connection notification, an icon of the second connection application includes: the second terminal equipment judges whether a second continuous application is installed or not; under the condition that the second connection application is not installed, the second terminal equipment 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 packet name and the signature information and performs white list verification on the second continuous application; if the verification is passed, the cloud server sends an icon of a second continuous application to the second terminal equipment; the second terminal device receives the icon of the second continued application.

It should be understood that the second terminal device may obtain the icon of the second continuous application from the cloud server.

It should also be understood that, in the case where 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 installs the second connection application, and otherwise, considers that the second terminal device does not install the second connection application.

With reference to the first aspect, in some implementations of the first aspect, the broadcast connection notification further includes an icon of the first connection application.

It should be understood that the second terminal device may obtain the icon of the second continued application from the first terminal device. The first terminal equipment sends a succession broadcast notice which also comprises an icon of a first succession application, and the second terminal equipment receives the icon of the first succession application and takes the icon of the first succession application as an icon of a second succession application.

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

With reference to the first aspect, in some implementation manners of the first aspect, the installing, by the second terminal device, a second connection application in response to a user operation of installing a window, includes: and under the condition that the second continuous application is the system application, the second terminal equipment responds to the operation of the user on the guiding installation of the popup window, and resumes the installation of the second continuous application.

With reference to the first aspect, in some implementation manners of the first aspect, the installing, by the second terminal device, a second connection application in response to a user operation of installing a window, includes: and in the case that the second continuous application is a third party application, the second terminal equipment responds to the operation of the user on the guiding installation of the popup window, downloads an installation package of the second continuous application from the application market and installs the second continuous application.

With reference to the first aspect, in certain implementation manners of the first aspect, before sending the connection data request message to the first terminal device, the method includes: the second terminal equipment displays a contact button on the desktop in the form of an icon of a second continuous application; transmitting a connection data request message to a first terminal device, including: and the second terminal equipment responds to the clicking operation of the contact button by the user and sends a connection data request to the first terminal equipment.

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

In a second aspect, an application connection method is provided, applied to a system including a first terminal device and a second terminal device, where a user logs 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 equipment receives a broadcast connection notification from the first terminal equipment, acquires an icon of a second connection application based on the broadcast connection notification, and displays a contact button in the form of the icon of the second connection application, wherein the broadcast connection notification is used for requesting the connection of the first connection application of the first terminal equipment to the second terminal equipment; the second terminal equipment responds to the clicking operation of the contact button by a user and displays a guide 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 second terminal equipment receives the connection data of the first connection application from the first terminal equipment and displays the connection data.

With reference to the second aspect, in some implementations of the second aspect, the broadcast connection notification includes: an application identifier and a connection policy of the first connection application; wherein the splicing policy comprises at least one of the following: the connection state identification, the package name or process name of the first connection application, the application market shelf policy of the first connection application, and the minimum version of the support connection.

With reference to the second aspect, in some implementations of the second aspect, the obtaining, based on the broadcast connection notification, an icon of the second connection application includes: the second terminal equipment judges whether a second continuous application is installed or not; under the condition that the second connection application is not installed, the second terminal equipment sends the package name and signature information of the second connection application to the cloud server based on the broadcast connection notification; and the second terminal equipment receives the icon of the second continuous application which passes the white list verification from the cloud server.

With reference to the second aspect, in some implementations of the second aspect, the broadcast connection notification further includes an icon of the first connection application.

With reference to the second aspect, in some implementations of the second aspect, the second terminal device installs a second connection application in response to a user operation of the above-mentioned guided installation of the window, including: and if the second continuous application is the system application, the second terminal equipment responds to the operation of the user on the guiding installation of the popup window and resumes the installation of the second continuous application.

With reference to the second aspect, in some implementations of the second aspect, the second terminal device installs a second connection application in response to a user operation of the above-mentioned guided installation of the window, including: and in the case that the second continuous application is a third party application, the second terminal equipment responds to the operation of the user on the guiding installation popup window, downloads an installation package of the second continuous application from an application market and installs the second continuous application.

With reference to the second aspect, in some implementations of the second aspect, before the sending of the connection data request message to the first terminal device, the method includes: the second terminal equipment displays a contact button on the desktop in the form of an icon of a second continuous application; transmitting a connection data request message to a first terminal device, including: and the second terminal equipment responds to the clicking operation of the contact button by the user and sends a connection data request to the first terminal equipment.

In a third aspect, a terminal device is provided for performing the method in any of the possible implementations of the second aspect. In particular, the terminal device comprises means for performing the method in any of the possible implementations of the second aspect described above.

In one design, the terminal device may include modules corresponding to the methods/operations/steps/actions described in the above aspects, where the modules may be hardware circuits, software, or a combination of hardware circuits and software.

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

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

In a fourth aspect, a terminal device is provided comprising a processor and a memory. The processor is configured to read instructions stored in the memory and to receive signals via the receiver and to transmit signals via the transmitter to perform the method of any one of the possible implementations of the second aspect described above.

Optionally, the processor is one or more and the memory is one or more.

Alternatively, the memory may be integrated with the processor or the memory may be separate from the processor.

In a specific implementation process, the memory may be a non-transient (non-transitory) memory, for example, a Read Only Memory (ROM), which may be integrated on the same chip as the processor, or may be separately disposed on different chips.

It should be appreciated that the related data interaction process, such as sending the continuation data request information, may be a process of outputting the indication information from the processor, and the receiving capability information may be a process of receiving the input capability information by the processor. Specifically, the data output by the processing may be output to the transmitter, and the input data received by the processor may be from the receiver. Wherein the transmitter and receiver may be collectively referred to as a transceiver.

The terminal device in the fourth aspect may be a chip, and the processor may be implemented by hardware or software, and when implemented by hardware, the processor may be a logic circuit, an integrated circuit, or the like; when implemented in software, the processor may be a general-purpose processor, implemented by reading software code stored in a memory, which may be integrated in the processor, or may reside outside the processor, and exist separately.

In a fifth aspect, there is provided a computer program product comprising: a computer program (which may also be referred to as code, or instructions) which, when executed, causes a computer to perform the method of any one of the possible implementations of the second aspect described above.

In a sixth aspect, a computer readable storage medium is provided, which stores a computer program (which may also be referred to as code, or instructions) which, when run on a computer, causes the computer to perform the method of any one of the possible implementations of the second aspect described above.

Drawings

Fig. 1 is a schematic view of an application scenario in an embodiment of the present application;

Fig. 2 is a schematic structural diagram of a terminal device provided in an embodiment of the present application;

fig. 3 is a schematic software structure of a terminal device according to an embodiment of the present application;

fig. 4 is a schematic diagram of another software structure of a terminal device according to an embodiment of the present application;

FIG. 5 is a schematic flow chart diagram of an application splicing method provided in an embodiment of the present application;

FIG. 6 is a schematic flow chart diagram of another method of application connectivity provided by an embodiment of the present application;

fig. 7 is an interface schematic diagram of a source device according to an embodiment of the present application;

fig. 8 is a schematic diagram of an interface change of a peer device according to an embodiment of the present application;

fig. 9 is another interface schematic diagram of a source device provided in an embodiment of the present application;

fig. 10 is another schematic diagram of interface change of the peer device according to the embodiment of the present application;

fig. 11 is a block diagram of a connection service manager of a terminal device according to an embodiment of the present application;

FIG. 12 is a schematic flow chart diagram of another method of application connectivity provided by an embodiment of the present application;

FIG. 13 is a schematic flow chart of a method for obtaining icons of a second continuous application according to an embodiment of the present application;

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

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

Detailed Description

The technical solutions in the present application will be described below with reference to the accompanying drawings.

In order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, the words "first", "second", etc. are used to distinguish the same item or similar items having substantially the same function and effect. It will be appreciated by those of skill in the art that the words "first," "second," and the like do not limit the amount and order of execution, and that the words "first," "second," and the like do not necessarily differ.

In this application, the terms "exemplary" or "such as" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "for example" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.

Furthermore, "at least one" means one or more, and "a plurality" means two or more. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a alone, a and B together, and B alone, wherein a, B may be singular or plural. The character "/" generally indicates that the context-dependent object is an "or" relationship. "at least one of" or the like means any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (one) of a, b, and c may represent: a, b, or c, or a and b, or a and c, or b and c, or a, b and c, wherein a, b and c can be single or multiple.

In order to facilitate understanding of the present application, an application scenario according to an embodiment of the present application is described below with reference to fig. 1.

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

Optionally, the application scenario 100 further includes a third terminal device 103. The third terminal device 103 may be used as a peer device, the user logs in the same account number 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, and the first terminal device 101 may connect the data of the application to the third terminal device 103.

It should be understood that in the scenario of multi-device application succession, 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 plurality of peer devices are all located under the same lan as the source device, for example, the first terminal device 101 and the second terminal device 102 may be located on one lan (e.g. WiFi), the first terminal device 101 and the third terminal device 103 may be located on another lan (e.g. bluetooth), and the first terminal device 101 may connect the data of the application 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 following describes the hardware structure of the terminal device in the embodiment of the present application.

Fig. 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 (universal serial bus, USB) interface 230, a charge management module 240, a power management module 241, a battery 242, an antenna 1, an antenna 2, a mobile communication module 250, a wireless communication module 260, an audio module 270, a speaker 270A, a receiver 270B, a microphone 270C, an earphone interface 270D, a sensor module 280, keys 290, a motor 291, an indicator 292, a camera 293, a display 294, and a subscriber identity module (subscriber identification module, SIM) card interface 295, etc. The sensor module 280 may include a pressure sensor 280A, a gyroscope sensor 280B, a barometric sensor 280C, a magnetic sensor 280D, an acceleration sensor 280E, a distance sensor 280F, a proximity sensor 280G, a fingerprint sensor 280H, a temperature sensor 280J, a touch sensor 280K, an ambient light sensor 280L, a bone conduction sensor 280M, and the like.

It is to be understood that the structure illustrated in the embodiments 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 illustrated, or certain components may be combined, or certain components may be split, or different arrangements of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

Processor 210 may include one or more processing units such as, for example: the processor 210 may include an application processor (application processor, AP), a modem processor, a graphics processor (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), a controller, a video codec, a digital signal processor (digital signal processor, DSP), a baseband processor, and/or a neural network processor (neural-network processing unit, NPU), etc. Wherein the different processing units may be separate devices or may be integrated in one or more processors.

The controller can generate operation control signals according to the instruction operation codes and the time sequence signals to finish the control of instruction fetching and instruction execution.

A memory may also be provided in the processor 210 for storing instructions and data. In some embodiments, the memory in the processor 210 is a cache memory. The memory may hold instructions or data that the processor 210 has just used or recycled. If the processor 210 needs to reuse the instruction or data, it may be called directly from the memory. Repeated accesses are avoided and the latency of the processor 210 is reduced, thereby improving the efficiency of the system.

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

It should be understood that the connection relationship between the modules illustrated in the embodiments of the present application is only illustrative, and does not constitute a structural limitation of the terminal device. In other embodiments of the present application, the terminal device may also use different interfacing manners in the foregoing embodiments, or a combination of multiple interfacing manners.

The terminal device implements display functions through a GPU, a display screen 294, an application processor, and the like. The GPU is a microprocessor for image processing, and is connected to the display screen 294 and the application processor. The GPU is 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 change display information.

The terminal device may implement a photographing function through the ISP, the camera 293, the video codec, the GPU, the display 294, the application processor, and the like.

The external memory interface 220 may be used to connect an external memory card, such as a Micro SD card, to realize expansion of the memory capability of the terminal device. The external memory card communicates with the processor 210 through an external memory interface 220 to implement data storage functions. For example, files such as music, video, etc. are stored in an external memory card.

The internal memory 221 may be used to store computer executable program code that includes instructions. The internal memory 221 may include a storage program area and a storage data area. The storage program area may store an application program (such as a sound playing function, an image playing function, etc.) required for at least one function of the operating system, etc. The storage data area may store data created during use of the terminal device (such as audio data, phonebook, etc.), etc. In addition, the internal memory 221 may include a high-speed random access memory, and may further include a nonvolatile memory such as at least one magnetic disk storage device, a flash memory device, a universal flash memory (universal flash storage, UFS), and the like. The processor 210 performs various functional applications of the terminal device and data processing by executing instructions stored in the internal memory 221 and/or instructions stored in a memory provided in the processor. For example, the application continuation method of the embodiment of the present application may be performed.

The terminal equipment can be used as source equipment and opposite equipment. The source device may also be referred to as a transmitting end, and the opposite device may also be referred to as a receiving end. 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. Fig. 3 in this embodiment illustrates a software structure of a sending end and a receiving end by taking an Android system with a layered architecture as an example.

As shown in fig. 3, taking the transmitting end as an example, the layered architecture divides the software into several layers, each layer having a clear role and division. The layers are in data transmission and communication through a software interface. In some embodiments, the Android system is divided into five layers, from top to bottom, an application layer, an application framework layer, an Zhuoyun rows (Android run) and system libraries, a hardware abstraction layer (hardware abstract layer, HAL), and a kernel layer, respectively.

The application layer may include a series of application packages. As shown in fig. 3, the application packages may include third party applications, software development kits (software development kit, SDK), bluetooth, WIFI, memo, video, game, etc. applications. For example, in the embodiment of the present application, in the application layer, the connection application may access the connection service SDK, and the connection application may be a system application in the terminal device, or may be a third party application, or may be a system application or a third party application.

The application framework layer provides an application programming interface (application programming interface, API) and programming framework for application programs of the application layer. The application framework layer includes a number of predefined functions.

As shown in fig. 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, and the like. Wherein the manager may also be referred to as a module in some application scenarios.

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

The communication service manager may be used to implement data transmission between devices, for example, in the embodiment of the present application, the communication service manager may implement security authentication and account authentication of devices with the same account, self-discovery and ad hoc network of devices, data transmission between devices, access of communication service, and so on.

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

The notification manager allows the application to display notification information in a status bar, can be used to communicate notification type messages, can automatically disappear after a short dwell, and does not require user interaction. Such as notification manager is used to inform that the download is complete, message alerts, etc. The notification manager may also be a notification in the form of a chart or scroll bar text that appears on the system top status bar, such as a notification of a background running application, or a notification that appears on the screen in the form of a dialog window. For example, prompting text information in a status bar, giving out a prompt tone, vibrating a terminal device, flashing an indicator light, 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 task bar.

The window manager is used for managing window programs. The window manager may obtain the display screen size, determine if there is a status bar, lock screen, touch screen, drag screen, intercept screen, etc.

The resource manager provides various resources for the application program, such as localization strings, icons, pictures, layout files, video files, and the like.

The content provider is used for realizing the function of data sharing among different application programs, allowing one program to access the data in the other program, and simultaneously ensuring the safety of the accessed data.

The view system may be responsible for interface rendering and event handling for the application. For example, in the embodiment of the present application, the view system may be used to process event processing after the user clicks the notification icon of the continuation application.

Android runtimes include core libraries and virtual machines. Android run time is responsible for scheduling and management of the Android system.

The core library consists of two parts: one part is a function which needs to be called by java language, and the other part is a core library of android.

The application layer and the application framework layer run in a virtual machine. The virtual machine executes java files of the application program layer and the application program framework layer as binary files. The virtual machine is used for executing the functions of object life cycle management, stack management, thread management, security and exception management, garbage collection and the like.

The system library may include a plurality of functional modules. For example: media Libraries (Media Libraries), function Libraries (Function Libraries) graphics processing Libraries (e.g., openGL ES), etc.

Media libraries support a variety of commonly used audio, video format playback and recording, still image files, and the like. The media library may support a variety of audio video encoding formats, such as: MPEG4, h.264, MP3, AAC, AMR, JPG, PNG, etc.

The function library provides multiple service API interfaces for the developer, and is convenient for the developer to integrate and realize various functions quickly.

Graphics processing libraries are used to implement graphics drawing, image rendering, compositing, and layer processing, among others.

The hardware abstraction layer is a layer of abstracted structure between the kernel layer and the Android run. The hardware abstraction layer may be a package for hardware drivers that provides a unified interface for the invocation of upper layer applications. The hardware abstraction layer may include a bluetooth module, a WIFI module, a hardware configuration module, and the like. For example, in the embodiment of the present application, the bluetooth module and the WIFI module in the hardware abstraction layer may shield specific hardware implementation details of the bluetooth driver and the WIFI driver in the kernel layer, and the upper layer application may implement the bluetooth function and the WIFI function by calling the interface without knowing a specific implementation manner of the kernel layer hardware driver.

The kernel layer is a layer between hardware and software. The kernel layer may include a display driver, a camera driver, an audio driver, a bluetooth driver, a WiFi driver, a central processor driver, and the like. For example, in the embodiment of the application, the communication service manager may perform connection between devices through relevant modules such as bluetooth driver and WiFi driver, so as to realize discovery and ad hoc network of the devices.

The transmission flow of the connection data in the Android system layered framework is illustrated by combining the scene of connection notification display in the application connection process between the terminal devices.

As shown in fig. 3, in the application layer of the transmitting end, the application may implement data transmission with the connection service by accessing the connection service SDK. The connection service SDK can send a connection service binding request and an application registration connection service request to the connection service manager, so that connection application registration and bound data transmission between the application layer and the application framework layer are realized.

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

After the continuing application is successfully registered, the communication service manager can call the Bluetooth module interface and the WIFI module interface provided by the hardware abstraction layer to realize the discovery and the self-networking of the equipment, and realize the session connection and the message transmission among the terminal equipment, the transmission of continuing content and the like through the Bluetooth driver and the WIFI driver in the kernel layer.

After the receiving end receives the continuous related data transmitted by the transmitting end based on the kernel layer, the data can be transmitted to a related module in the hardware abstraction layer. In the application program framework layer of the receiving end, the communication service manager can acquire the transmitted connection data through an interface provided in the hardware abstraction layer, and perform signaling transmission and data transmission with the connection service manager. After receiving the data related to the connection, the connection service manager can perform binding authentication service and application authentication with the authentication service manager. Further, the connection service manager may instruct the desktop initiator to display the connection notification in the form of an icon.

It can be understood that, as shown in fig. 4, the sending end or the receiving end of the embodiment of the present application may also adopt a Windows system, and the layered architecture of the Windows system is different from that of the Android system and is mainly divided into a user state and a kernel state, where the user state may include a user application program process, a system process, a service process, and the like; kernel states may include kernel and device driver layers, as well as hardware abstraction layers, etc.

The user application process may execute a series of applications. The specific executable application program type may be the same as the application program type in the application program layer in the Android system, and will not be described herein.

The system process and the service process can comprise a connection service manager, a communication service manager, an authentication service manager, a system process, a notification manager, a window manager and the like, and can provide corresponding services for the execution of the user application program process. The processes of the connection service manager, the communication service manager, the authentication service manager, and the like, which are specifically related to the embodiments of the present application, may be described by related managers in Android, and are not described herein again.

The kernel layer and the device driving layer may include a bluetooth driver, a WiFi driver, a display driver, and the like, and the hardware abstraction layer may include a bluetooth module, a WiFi module, a hardware configuration module, and the like. The specific function modules can be referred to the relevant description in Android, and are not described herein.

The interaction process between the modules will be described in detail below in connection with a system implementing a method of content continuation across devices. The following embodiments may be combined with each other or implemented independently, and the same or similar concepts or processes may not be described in detail in some embodiments.

Fig. 5 is a schematic flowchart of an application splicing method provided in an embodiment of the present application. The method may be applied to the scenario 100 described above, where the hardware structure of the terminal device involved in the method may be as described in fig. 2, and the software structure may be as shown in fig. 3 or fig. 4. The first terminal device may correspond to the transmitting end of fig. 3 or fig. 4, and the second terminal device may correspond to the receiving end of fig. 3 or fig. 4. Each of the first terminal device and the second terminal device may include respective functional modules for implementing a connection service, for example, may include a connection service SDK, a connection service manager, a communication service manager, an authentication service manager, and the like.

For convenience of description, the subsequent connection application of the first terminal device is referred to as a first connection application, the connection service SDK of the first terminal device is referred to as a first connection service SDK, the connection service manager of the first terminal device is referred to as a first connection service manager, the communication service manager of the first terminal device is referred to as a first communication service manager, and the authentication service manager of the first terminal device is referred to as a first authentication service manager.

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

It should be appreciated that the first continuation application and the second continuation application are the same application, e.g., the first continuation application is a memo and the second continuation application is also a memo.

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

The first stage, registration and binding of successive applications.

When the first connection application of the first terminal device monitors some user actions, the first connection application can access the connection service by calling the registration interface of the first connection service SDK. It may be appreciated that the first connection application may carry information such as an application package name of the first connection application when registering for the connection service. The user behavior may be that the user clicks the first connection application icon to start an application, or may be that the user performs operations such as editing in the first connection application, or may be that the user clicks a play button in the first connection application to perform operations such as video playing, music playing, or other media playing, and the specific monitored user behavior may be set by the connection application in a user-defined manner.

In a possible implementation, the first connection service SDK may perform data interaction with other function managers through the first connection service manager. For example, the first connection service SDK may send a request for binding the connection service and registering the connection service with the first connection service manager, and after receiving the request for the first connection service SDK, the first connection service manager may interact with the first communication service manager to bind the communication service, and after successful binding, the first connection service manager may receive a message that the binding returned by the first communication service manager is successful.

Further, the first connection service manager may perform binding authentication service and application authentication by calling an interface provided by the first authentication service manager. After receiving the authentication request, the first authentication service manager can complete binding and authentication of the first continuous application through data interaction with the cloud authentication server. It can be appreciated that in the process of binding the authentication service, the cloud authentication server may obtain the user identifier (user identification, UID) according to the packet name of the first continuous application, and then perform application authentication according to the UID. After the authentication of the first continuous application is successful, the cloud authentication server can store application information such as icons of the first continuous application and returns an authentication result to the first continuous service manager.

After the first connection service manager receives the authentication result of the first connection application, the message is transmitted to the first connection application. The authentication result may include authentication success and authentication failure, and if the result received by the first continuing application is authentication success, the application registration is successful, and the method of continuing the application may be continuously executed; if the result received by the first continuing application is authentication failure, indicating that the application registration fails, and not continuing to execute the method of application continuing.

After the application of the first terminal device is successfully registered, the first communication service manager and the second communication service manager can perform self-discovery and self-networking and account authentication through bluetooth or WIFI, and further, the first communication service manager can send information for representing that the second terminal device is online to the first connection service manager. For example, the information for indicating that the second terminal device is online may include information such as a device identification (device identification, devID) of the second terminal device.

After the first connection service manager receives the information sent by the first communication service manager and used for indicating that the second terminal equipment is on line, the information of the second terminal equipment can be stored and managed so as to execute a flow of carrying out subsequent application data connection.

And displaying a continuous notice in the second stage.

When the first connection application is successfully registered, a broadcast connection notification may be periodically sent to the first connection service manager. The broadcast connection notification may carry information such as an application identifier of the first connection application, a connection policy, and a connection content summary (e.g., a header). The first connectivity service manager may identify the devices that are capable of connectivity based on the connectivity policy of the first connectivity application.

The connection policy is used to determine the devices that can be connected, and each application program can correspond to its own connection policy. Illustratively, the connection policy of the application may relate to one or more of the following fields:

the connection state identification, the device type supported by the application program, the package name or the process name of the first connection application, the application market shelf policy of the first connection application, the browser starting parameter, the minimum version supporting connection, and the like.

The splice status identifier may be a flag bit for identifying a splice policy status. For example, a flag bit of 0 may indicate that no connection is supported, a flag bit of 1 may indicate that connection is applied, and a flag bit of 3 may indicate that connection is browser. It can be understood that the specific value of the flag bit can be set arbitrarily, and different states can be distinguished, and the embodiment of the application is not limited specifically.

For example, when the connection policy includes a device type supported by the application program, for example, the connection policy includes that the first connection application may support implementation of the connection service on the mobile phone, the tablet computer, the television, the computer, and the like, the first connection service manager may instruct the first communication service manager and the second communication service manager to establish a session path when confirming that the second terminal device is the mobile phone, the tablet computer, the television, the computer, and the like.

If the first connection application is an application of the Android platform, the connection policy comprises a package name of the first connection application in the Android platform; if the first continuing application is an application of the windows platform, the continuing policy includes a continuing process name of the first continuing application in the windows platform. The application market place policy may be any of the following: the method comprises the following steps of not putting on shelf, overseas application market 1, domestic application market 2 and overseas application market 2.

The minimum version supporting the splicing application may be represented by a minimum version number supporting the splicing application, for representing the minimum version when the second splicing application is spliceable. For example, when the connection policy includes that the minimum version number of the first connection application may support a or the minimum version number of the first connection application may support B, the first connection service manager may instruct the first communication service manager and the second communication service manager to establish a session path when confirming that the version number of the second connection application is greater than or equal to a or that the version number of the second connection application is greater than or equal to B.

A session path may be established between the first communication service manager and the second communication service manager for application-connection related messaging and data transmission.

After the session path is established successfully, the first communication service manager can indicate that the channel is established successfully to the first connection service manager, the first connection service manager can inform the first communication service manager of the broadcast connection carrying the information such as the packet name and the connection content outline of the first connection application according to the broadcast connection notification sent by the first connection application, the first communication service manager sends the information such as the packet name and the connection content outline of the first connection application to the second communication service manager through the established session path, and the second communication service manager further reports the information such as the packet name and the connection content outline of the first connection application to the second connection service manager.

The second connection service manager may analyze the packet name of the first connection application, and carry the packet name information of the first connection application to bind and authenticate with the second authentication service manager, where the implementation of binding and authentication is similar to the authentication step in the first terminal device, and will not be described herein.

After the application authentication is successful, the second connection service manager may 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 locally stored in the second terminal device according to the obtained application information such as the packet name of the first connection application. If the icon of the first continuous application can be found, the second continuous service manager can inform the desktop starter to display a continuous notification by using the icon of the first continuous application; if the icon of the first continuous application is not found, the second continuous service manager can acquire related information such as the icon of the first continuous application 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 may store related information such as the icon of the first connection application locally in the second terminal device, and the second connection service manager may notify the desktop initiator to display a connection notification on the second terminal device.

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

In yet another possible implementation, the second connection service manager may search for a second connection application in the second terminal device that has the same package name as the first connection application. If the second connection application can be found, the second connection service manager can inform the desktop starter to display connection notification by using the icon of the second connection application locally stored by the second terminal equipment; if the second connection application is not found, the second connection service manager may obtain related information such as an icon of the first connection application by searching application information in the local area of the second terminal device or in the cloud authentication server, and notify the desktop initiator to display a connection notification using the icon of the first connection application.

It may be understood that, when the desktop initiator controls to display the connection notification, the connection notification may be displayed in the latest task, the task bar, the shortcut window, or other interface entries of the second terminal device, and the manner of specifically displaying the connection notification is not limited in the embodiment of the present application. 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, and specifically, the connection notification is displayed.

And thirdly, acquiring and loading continuous data.

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

The second connection service manager may pull up the second connection application and instruct the second connection application to load the transitional animation effect, and then the second connection application may start and load the transitional action, where the transitional action may include, for example, prompt information such as "in-load …". Further, the second connection application may access the connection service by calling the registration interface of the second connection service SDK, and it may be understood that the second connection application may carry information such as an application package name of the second connection application when registering the connection service.

The second connection service SDK may send a request for binding a connection service to the second connection service manager, and the second connection service manager may send a request for binding a communication service to the second communication service manager after receiving the request for binding a connection service. After the second communication service manager is successfully bound, the second communication service manager may send a message of successful binding to the second connection service SDK through the second connection service manager. After receiving the message of successful binding, the second connection service SDK sends a message of registering connection service to the second connection service manager, and after successful registration, the second connection service manager can return the message of successful registration to the second connection application through the second connection service SDK.

In the process of starting the second connection application, the second connection service manager can also send request connection data to the first connection service manager through a session path established between the first terminal equipment and the second terminal equipment, when the first connection service manager receives the request connection data and reports the request connection data to the first connection application through the first connection service SDK, the first connection application can package and encrypt relevant connection data such as connection content and send the connection data to the first connection service manager through the first connection service SDK, and 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 equipment and the second terminal equipment.

Further, the second connection service manager notifies the second connection application of connection data through the second connection service SDK, and after the second connection application is successfully registered, the second connection application may load the connection data and control the second terminal device to display the connection data, and transmit information for indicating that the connection is successful to the first connection application of the first terminal device, so that the first connection application may execute a procedure of exiting from a page of the first connection application, and the like.

It should be noted that, in the application connection method in the embodiment of the present application, if the first connection application has already registered and bound the connection service, when the first connection application of the first terminal device monitors some user actions, the first connection application does not need to re-register and bind the connection service, or understand that the first phase does not need to be executed, and the first connection application may skip the first phase to execute the second phase, the third phase, and so on, which is not repeated.

The general flow of the application connection method is described above, and a specific connection method of an uninstalled application on the peer device is described in detail below with reference to fig. 6 to 13.

For an application, application connection requires that both the source device and the peer device install the application. When the opposite terminal equipment does not install (or uninstall) the application, the source terminal equipment sends an application connection request of the application, and the opposite terminal equipment cannot connect the application, so that user experience is affected. In view of this, the application connection method provided by the present application can realize connection of the application not installed on the opposite terminal device, thereby improving user experience.

Fig. 6 is a schematic flow chart diagram of another method 600 of application connectivity provided in an embodiment of the present application. The method 600 may be applied to the scenario 100 described above, where the hardware structure of the terminal device involved in the method may be shown in fig. 2, and the software structure of the terminal device involved in the method may be shown in fig. 3 or fig. 4. The method 600 includes the steps of:

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

In an exemplary embodiment, when the first terminal device and the second terminal device are in a power-on state, the first terminal device and the second terminal device log on 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 video on a first connection application of the first terminal device, and the first terminal device sends a broadcast connection notification to the second terminal device, where the broadcast connection notification is used to indicate that the first connection application of the first terminal device requests to connect data to a second connection application of the second terminal device.

Optionally, broadcasting the connection notification includes: an application identification (application identification, APPID) and a splicing policy of the first splicing application; wherein the splicing policy comprises at least one of the following: the connection state identification, the package name or process name of the first connection application, the application market shelf policy of the first connection application, and the minimum version of the support connection.

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

Specifically, in the case where the second connection application is not installed, the second terminal device acquires an icon of the second connection application based on the broadcast connection notification, and displays a contact button in the form of the icon on the desktop, at which time the second connection application has not been installed yet.

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

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

And S603, the second terminal equipment responds to the clicking operation of the contact button by a user and displays the guide installation popup window of the second continuous application.

Specifically, the user clicks a contact button of the second connection application, and the second terminal device determines whether the second connection application is installed, and since the second terminal device does not install the second connection application, the second terminal device displays a guide installation popup window of the second connection application.

And S604, the second terminal equipment responds to the operation of the user on the guiding and installing the popup window to install a second continuous application.

In one possible implementation, if the second connection application is a system application, the user clicks to resume on the boot installation window, and the second terminal device resumes the installation of the second connection application in response to the operation of the user.

In another possible implementation manner, if the second continuous application is a third party application, the user clicks to download on the guide installation window, and the second terminal device jumps to the application market page to download and install in response to the operation of the user.

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

It should also be understood that, in the case where 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 installs the second connection application, and otherwise, considers that the second terminal device does not install the second connection application. For example, the minimum version of the second connection application supporting connection is v3.0, if the second terminal device installs v2.0 of the second connection application, and cannot realize application connection, the second terminal device is considered to be not installed with the second connection application, and if the second terminal device installs v4.0 of the second connection application, the second terminal device is considered to be installed with the second connection application.

S605, the second terminal device sends a connection data 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 receives the connection data and displays the connection data.

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

In the following, an example will be described in which a first terminal device (i.e., a source device) is a tablet computer, a second terminal device (i.e., a peer device) is a mobile phone, and a subsequent application is a system application (e.g., a memo).

Fig. 7 is an interface schematic diagram of a source device according to an embodiment of the present application, which is used to introduce a tablet computer as an interface of the source device in response to a user operation. In the interface shown in fig. 7, where the user is editing text in the memo, the tablet computer correspondingly displays the text edited by the user, and the position of the cursor changes with the position edited by the user. Since the tablet computer is in the memo text editing, a memo connection request can be sent to the mobile phone.

Fig. 8 is a schematic diagram of an interface change of a peer device according to an embodiment of the present application, which is used to introduce a mobile phone as an interface change of the peer device in response to a user operation. In the interface a of fig. 8, since the mobile phone receives the memo connection request sent by the tablet computer, a memo contact button is displayed on the latest taskbar, and the contact button displays the icon of the memo and the title "go to the distant place together". In addition, the touch point button also displays a bright spot (such as a black dot in interface a of fig. 8) and a memo from "tablet" to prompt the user that the memo from the tablet computer and the heading "go far together" wants to be continued with the memo of the mobile phone. The user clicks the contact button, and the mobile phone displays the interface b of fig. 8 in response to the user clicking the contact button. In the interface b of fig. 8, a guide installation window is displayed on the desktop of the mobile phone, the user clicks "resume" in the guide installation window, and the mobile phone resumes the installation of the application in response to the click resume operation of the user, and the interface c of fig. 8 is displayed. In the interface c of fig. 8, a memo page is displayed, and "continuing content is being loaded" is displayed on the memo page, and after content loading, the interface d of fig. 8 is displayed. In interface d of fig. 8, the same memo content and the same cursor position of the tablet computer are displayed.

The application connection interface when the connection application is a system application is described above with reference to fig. 7 and 8, and the application connection interface when the connection application is a third party application (e.g., WPS Office) is described below with reference to fig. 9 and 10.

Fig. 9 is another interface schematic diagram of a source device according to an embodiment of the present application, which is used to introduce a tablet computer as an interface of the source device in response to a user operation. In the interface of fig. 9, the tablet computer opens the WPS Office in response to the user's operation, and may send a WPS Office connection request to the mobile phone since the WPS Office is already open.

Fig. 10 is another schematic diagram of interface changes of the peer device according to the embodiment of the present application, which is used to introduce the mobile phone as the interface change of the peer device in response to the user operation. In interface a of fig. 10, since the handset receives the WPS Office connection request sent by the tablet computer, a contact button of WPS Office is displayed in the latest taskbar, and an icon of WPS Office and the title "AI creativity culture future" are displayed on the contact button. In addition, the touch point button also displays a bright spot (such as a black dot in the interface a of fig. 9) and a touch screen from a tablet to prompt the user that the user wants to connect with the WPS Office of the mobile phone from the tablet and the heading "AI creativity cultivation future". The user clicks the contact button, and the mobile phone displays the interface b of fig. 10 in response to the user clicking the contact button. In interface b of fig. 10, the handset desktop displays a guide mounting window, the user clicks the "forward download" button in the guide mounting window, and the handset displays interface c of fig. 10 in response to the user clicking the "forward download" button operation. In the interface c of fig. 10, a WPS Office page in the application market is displayed, and an "install" button is displayed on the page, and the user clicks the "install" button, and the mobile phone displays the interface d of fig. 10 in response to the user clicking the "install" button. In interface d of fig. 10, a touch button of WPS Office is displayed on the desktop, and the user clicks the touch button, and the mobile phone displays interface e of fig. 10 in response to the user's operation. In the interface e of fig. 10, the WPS Office homepage is displayed, and "continuing content is being loaded", and after the content is loaded, the interface f of fig. 10 is displayed. In interface f of fig. 10, the same WPS Office page as the tablet is displayed.

It should be appreciated that the contact buttons of successive applications may be on the nearest taskbar or on the desktop, which is not limited in this embodiment of the present application.

Next, the internal structure of the connection service manager of the terminal device will be described with reference to fig. 11.

Fig. 11 is a block diagram of a connection service manager of a terminal device according to 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. The continuous broadcast manager is used for managing the transmission of a plurality of continuous broadcasts of a plurality of devices or the same device in a multi-window scene. The file transmission manager is used for transmitting data such as pictures, texts and the like. The application download manager is used for managing the downloaded application and guiding the downloading of the uninstalled application. The splice contact manager is used to determine installation and version information for the application.

For convenience of description, the connection broadcast manager in the second connection service manager is hereinafter referred to as a second connection broadcast manager, the file transfer manager in the second connection service manager is referred to as a second file transfer manager, the application download manager in the second connection service manager is referred to as a second application download manager, and the connection contact manager in the second connection service manager is referred to as a second connection contact manager.

Next, a specific flow of the application connection method will be further described by taking the internal device shown in fig. 11 as an example.

Fig. 12 is a schematic flow chart diagram of another method 1200 of applying a splice method provided by an embodiment of the present application. The method 1200 may be applied to the scenario 100 described above, where the hardware structure of the terminal device involved in the method 1200 is shown in fig. 2, and the software structure is shown in fig. 3 or fig. 4. The method 1200 includes the steps of:

s1201, the user is editing text or playing video in the first connection application of the first terminal device, and the first connection application of the first terminal device sends a broadcast connection notification to the connection service manager of the first terminal device, where the broadcast connection notification includes: an application identifier and a connection policy of the first connection application; wherein the splicing policy comprises at least one of the following: the connection state identification, the package name or process name of the first connection application, the application market shelf policy of the first connection application, and the minimum version of the support connection.

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

{

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

"Policy":1,

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

"AppId":220482320,

the AppMarketDescription is 0 that the device is not put on shelf, 1 that the overseas application market is 1,2 that the domestic application market is 1,3 that the domestic application market is 2,4 that the overseas application market is 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 connection broadcast manager of the second terminal device.

S1205, the connection broadcast manager of the second terminal device receives the broadcast connection notification and then obtains the icon of the second connection application.

S1206, the connection broadcast manager of the second terminal device sends an icon of the second connection application to the desktop initiator of the second terminal device.

S1207, the desktop initiator of the second terminal device receives the icon of the second continuous application and displays the continuous contact button of the second continuous application in the form of the icon.

S1208, the desktop starter of the second terminal equipment responds to the clicking operation of the contact button by the user and sends the signature and package name information of the second continuous application to the continuous contact manager of the second terminal equipment.

S1209, the connection contact manager of the second terminal device receives the signature and the packet name information, and determines whether the second connection application is connectable by determining whether the second connection application is installed or whether the version of the second connection application supports connection.

And under the condition that the second connection application is installed and the version supports connection, the second terminal equipment directly jumps to the connection interface.

It should be understood that, in the case where 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 application considers that the second terminal device installs the second connection application, and otherwise, considers that the second terminal device does not install the second connection application. For example, the minimum version of the second connection application supporting connection is v3.0, if the second terminal device installs v2.0 of the second connection application, and cannot realize application connection, the second terminal device is considered to be not installed with the second connection application, and if the second terminal device installs v4.0 of the second connection application, the second terminal device is considered to be installed with the second connection application.

S1210, in case that 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 continuous application, and checks the installation and version information of the second continuous application by checking the downloaded application and the version information corresponding to the downloaded application.

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 pulls up an application installation dialog box of the second terminal device, and guides the installation of the second connection application.

S1213, the application installation dialog box of the second terminal device determines the type of the second connection application, which is the system application or the third party application.

In the case where the second continuous 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 call message to the management system of the second terminal device.

Optionally, the second terminal device may display the guide installation window first, and call the management system of the second terminal device in response to the click recovery operation of the user.

S1215, after receiving the call message, the management system of the second terminal device resumes installing the second connection 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, where the first installation completion message is used to indicate that the installation of the second connection application is 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 to connect the 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 first connection data of the first connection application to the communication service manager of the first terminal device, where the first connection data is connection data of the first connection application.

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 transmission manager of the second terminal device.

S1223, after receiving the first connection data, the file transmission 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 connection.

In the case where the second continued application is a third party application, the second terminal device performs S1225 to S1237.

S1225, in the case that the second continuous application is a third party application, responding to the click downloading operation of the user, and jumping the application installation dialog box interface of the second terminal device to the application market interface of the second terminal device.

S1226, in the application market interface of the second terminal device, responding to the click installation operation of the user, the second terminal device downloads and installs the third party application.

S1227, after the second continuous application is installed, the application market of the second terminal device sends a second installation completion message to the continuous broadcast manager of the second terminal device, where 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 initiator of the second terminal device.

S1229, after receiving the second installation completion message, the desktop starter of the second terminal device displays the contact button of the third party application.

S1230, the desktop initiator of the second terminal device responds to the click of the contact button operation of the user and sends a second connection data request message to the connection broadcast manager of the second terminal device to request the connection of the data of the first connection application.

In another possible implementation manner, after the connection broadcast manager of the second terminal device receives the second installation completion message, the second connection data request message may be directly sent to the communication service manager of the second terminal device, and the user may not need to click the contact 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 second connection data of the first connection application to the communication service manager of the first terminal device, where the second connection data is connection data of a third party application on the first terminal device.

S1235, after the communication service manager of the first terminal device receives the second connection data, the communication service manager of the second 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 transmission manager of the second terminal device.

S1237, after receiving the second connection data, the file transmission manager of the second terminal device sends the second connection data to the third party application of the second terminal device.

S1238, after the third party application of the second terminal equipment receives the second connection data, the second connection data is loaded and displayed, and the second connection application completes connection.

According to the application connection method, under the condition that the second terminal equipment is not provided with the system application or the third party application, the second terminal equipment guides a user to install the system application or the third party application, and after the installation is completed, connection data are requested to the first terminal equipment, connection of the application which is not installed on the opposite terminal equipment can be achieved, and therefore user experience is improved.

In one possible implementation, the second terminal device may obtain an icon of the second continued application from the first terminal device. Specifically, the broadcast connection notification in S1205 further includes an icon of the first connection application, and the connection broadcast manager of the second terminal device may obtain the icon of the first connection application from the broadcast connection notification, and send the icon of the first connection application to the desktop initiator as an icon of the second connection application.

In another possible implementation manner, the second terminal device may obtain the icon of the second continuous application from the cloud server. Next, a detailed description will be given of an icon obtaining method for obtaining the second connection application from the cloud server by the second terminal device with reference to fig. 13.

Fig. 13 is a schematic flowchart of a method 1300 for obtaining an icon of a second continuous application according to an embodiment of the present application. The method 1300 includes the steps of:

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

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

And S1303, after receiving the packet name and the signature information of the second continuous application, the cloud server performs white list verification on the second continuous application.

And S1304, after the white list of the second continuous application passes verification, the cloud server sends the packet name and icon information of the second continuous application to a continuous broadcast manager of the second terminal device.

It should be understood that the sequence numbers of the above processes do not mean the order of execution, and the execution order of the processes should be determined by the functions and internal logic of the processes, and should not constitute any limitation on the implementation process of the embodiments of the present application.

The application connection method of the embodiment of the present application is described in detail above with reference to fig. 6 to 13, and the terminal device of the embodiment of the present application will be described in detail below with reference to fig. 14 and 15.

Fig. 14 is a terminal device 1400 provided in an embodiment of the present application, where the terminal device 1400 includes: a processing module 1401 and a transceiver module 1402. The terminal device 1400 is configured to implement the steps corresponding to the second terminal device in the method 600.

The transceiver module 1402 is configured to: receiving a broadcast connection notification from a first terminal device, and obtaining an icon of a second connection application based on the broadcast connection notification, wherein the broadcast connection notification is used for requesting the first connection application of the first terminal device to be connected to the second terminal device; the processing module 1401 is configured to: displaying the contact button in the form of an icon of a second successive application; responding to the clicking operation of the contact button by a user, and displaying a guide installation popup window of a second continuous application; installing the second continuous application in response to the user operation of installing the popup window; the transceiver module 1402 is further configured to: transmitting a connection data request message to a first terminal device; receiving connection data of a first connection application from a first terminal device; the processing module 1401 is further configured to: and displaying the continuous data.

Optionally, the broadcast connection notification includes: an application identifier and a connection policy of the first connection application; wherein the splicing policy comprises at least one of the following: the connection state identification, the package name or process name of the first connection application, the application market shelf policy of the first connection application, and the minimum version of the support connection.

Optionally, the processing module 1401 is further configured to: judging whether a second continuing application is installed or not; the transceiver module 1402 is further configured to: under the condition that the second connection application is not installed, based on the broadcast connection notification, sending the packet name and signature information of the second connection application to a cloud server; and receiving the icon of the second continuous application which passes the white list verification from the cloud server.

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

Optionally, the processing module 1401 is further configured to: and in the case that the second continuous application is a system application, the installation of the second continuous application is resumed in response to the user operation of installing the popup window.

Optionally, the processing module 1401 is further configured to: and in the case that the second continuous application is a third party application, responding to the operation of the user on the guiding installation popup window, downloading an installation package of the second continuous application from an application market and installing the second continuous application.

Optionally, the processing module 1401 is further configured to: displaying a contact button on the desktop in the form of an icon of a second successive application; the transceiver module 1402 is further configured to: and responding to the clicking operation of the contact button by a user, and sending a connection data request to the first terminal equipment.

It should be understood that the terminal device 1400 herein is embodied in the form of functional modules. The term module herein may refer to an application specific integrated circuit (application specific integrated circuit, ASIC), an electronic circuit, a processor (e.g., a shared, dedicated, or group processor, etc.) and memory that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that support the described functionality. In an alternative example, it will be understood by those skilled in the art that the terminal device 1400 may be specifically the second terminal device in the foregoing embodiment, and the terminal device 1400 may be configured to perform each flow and/or step corresponding to the second terminal device in the foregoing method embodiment, which is not repeated herein.

The terminal device 1400 has a function of implementing the corresponding steps performed by the second terminal device in the method; the above functions may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above. For example, the transceiver module 1402 may include a transmitting module and a receiving module, where the transmitting module may be configured to implement respective steps and/or processes for performing a transmitting action corresponding to the transceiver module, and the receiving module may be configured to implement respective steps and/or processes for performing a receiving action corresponding to the transceiver module. The transmitting module may be replaced by a transmitter, and the receiving module may be replaced by a receiver, for performing the transceiving operations and the associated processing operations in the respective method embodiments, respectively.

In an embodiment of the present application, the terminal device 1400 in fig. 14 may also be a chip or a chip system, for example: system On Chip (SOC). Correspondingly, the transceiver module 1402 may be a transceiver circuit of the chip, which is not limited herein.

Fig. 15 is another terminal device 1500 provided in an embodiment of the present application. The terminal device 1500 includes a processor 1501, a transceiver 1502 and a memory 1503. Wherein the processor 1501, the transceiver 1502 and the memory 1503 are in communication with each other through an internal connection path, the memory 1503 is used for storing instructions, and the processor 1501 is used for executing the instructions stored in the memory 1503 to control the transceiver 1502 to transmit signals and/or receive signals.

It should be understood that the terminal device 1500 may be specifically a second terminal device in the foregoing embodiment, and may be configured to perform the steps and/or flows corresponding to the second terminal device in the foregoing method embodiment. Alternatively, the memory 1503 may include read-only memory and random access memory, and may 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 information of the device type. The processor 1501 may be configured to execute instructions stored in a memory, and when the processor 1501 executes instructions stored in a memory, the processor 1501 is configured to perform the steps and/or flows of the method embodiment corresponding to the second terminal device described above. The transceiver 1502 may include a transmitter that may be used to implement various steps and/or processes for performing transmit actions corresponding to the transceiver described above, and a receiver that may be used to implement various steps and/or processes for performing receive actions corresponding to the transceiver described above.

It should be appreciated that in embodiments of the present application, the processor may be a central processing unit (central processing unit, CPU), the processor may also be other general purpose processors, digital Signal Processors (DSPs), application Specific Integrated Circuits (ASICs), field Programmable Gate Arrays (FPGAs) 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 or the like.

In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in a processor or by instructions in the form of software. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in the processor for execution. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor executes instructions in the memory to perform the steps of the method described above in conjunction with its hardware. To avoid repetition, a detailed description is not provided herein.

The present application also provides a computer-readable storage medium for storing a computer program for implementing the method corresponding to the second terminal device in the above embodiment.

The present application also provides a computer program product comprising a computer program (which may also be referred to as code, or instructions) which, when run on a computer, is capable of performing the method corresponding to the second terminal device as shown in the above embodiments.

Those of ordinary skill in the art will appreciate that the various illustrative modules and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clearly understood by those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described system, apparatus and module may refer to corresponding procedures in the foregoing method embodiments, which are not repeated herein.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, and for example, the division of the modules is merely a logical function division, and there may be additional divisions when actually implemented, for example, multiple modules or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or modules, which may be in electrical, mechanical, or other forms.

The modules described as separate components may or may not be physically separate, and components shown as modules may or may not be physical modules, i.e., may be located in one place, or may be distributed over a plurality of network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

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

The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a read-only memory (ROM), a random access memory (random access memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely specific embodiments of the present application, but the scope of the embodiments of the present application is not limited thereto, and any person skilled in the art may easily think about changes or substitutions within the technical scope of the embodiments of the present application, and the changes or substitutions are intended to be covered by the scope of the embodiments of the present application. Therefore, the protection scope of the embodiments of the present application shall be subject to the protection scope of the claims.

Claims

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

the first terminal device sends a broadcast connection notification to the second terminal device, wherein the broadcast connection notification is used for requesting to connect a first connection application of the first terminal device to the second terminal device;

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

The second terminal equipment responds to the clicking operation of the contact button by a user and displays a guide installation popup window of the second continuous application;

the second terminal equipment responds to the operation of the user on the guiding installation popup window, installs the second connection application and sends a connection data request message to the first terminal equipment;

the first terminal equipment sends the connection data of the first connection application to the second terminal equipment based on the connection data request message;

and the second terminal equipment receives the connection data and displays the connection data.

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

wherein the splicing policy includes at least one of:

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

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

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

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

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

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

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

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

5. The method according to any one of claims 1 to 4, wherein the second terminal device installing the second continued application in response to a user operation of the guided installation of the window, comprises:

and under the condition that the second continuous application is a system application, the second terminal equipment responds to the operation of the user on the guiding installation popup window and resumes the installation of the second continuous application.

6. The method according to any one of claims 1 to 4, wherein the second terminal device installing the second continued application in response to a user operation of the guided installation of the window, comprises:

and in the case that the second continuous application is a third party application, the second terminal equipment responds to the operation of the user on the guide installation popup window, downloads an installation package of the second continuous application from an application market and installs the second continuous application.

7. The method according to any of claims 1 to 6, characterized in that before said sending of a splice data request message to said first terminal device, the method further comprises:

the second terminal equipment displays the contact button on a desktop in the form of an icon of the second continuous application;

the sending a connection data request message to the first terminal device includes:

and the second terminal equipment responds to the clicking operation of the contact button by a user and sends a connection data request to the first terminal equipment.

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

The second terminal equipment receives a broadcast connection notification from the first terminal equipment, acquires an icon of a second connection application based on the broadcast connection notification, and displays a contact button in the form of the icon of the second connection application, wherein the broadcast connection notification is used for requesting the first connection application of the first terminal equipment to be connected to the second terminal equipment;

the second terminal equipment receives the connection data of the first connection application from the first terminal equipment and displays the connection data.

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

wherein the splicing policy includes at least one of:

10. The method according to claim 8 or 9, wherein the obtaining the icon of the second connection application based on the broadcast connection notification comprises:

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

11. The method according to claim 8 or 9, wherein the broadcast connection notification further comprises an icon of the first connection application.

12. The method according to any one of claims 8 to 11, wherein the second terminal device installing the second continued application in response to a user operation of the guided installation of the window, comprises:

13. The method according to any one of claims 8 to 11, wherein the second terminal device installing the second continued application in response to a user operation of the guided installation of the window, comprises:

14. The method according to any of claims 8 to 13, characterized in that before said sending of a splice data request message to said first terminal device, the method further comprises:

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

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

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