CN115941674B

CN115941674B - Multi-device application connection method, device and storage medium

Info

Publication number: CN115941674B
Application number: CN202310144702.6A
Authority: CN
Inventors: 陈聪聪; 张之伟
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2023-02-21
Filing date: 2023-02-21
Publication date: 2023-07-14
Anticipated expiration: 2043-02-21
Also published as: CN115941674A

Abstract

The application provides a multi-device application connection method, a device and a storage medium. In the method, the device initiating the application connection request determines whether the file subjected to the secondary connection transmission is subjected to the connection transmission for the first time or not, and further directly performs application connection with the receiving end in a differential transmission mode after receiving the application connection response made by the receiving end under the condition that the file is subjected to the non-first transmission, namely the receiving end already has the file before the current edition, namely differential data which is different from the current edition is only transmitted to the receiving end, so that the time consumption of data transmission in the application connection process is greatly shortened.

Description

Multi-device application connection method, device and storage medium

Technical Field

The present disclosure relates to the field of multi-device communication technologies, and in particular, to a multi-device application connection method, a device, and a storage medium.

Background

The multi-device application connection is a seamless circulation of connection tasks among a plurality of devices under the near field same account number. For example, when a user edits a content by operating an application supporting connection in the device a and generates a need for switching devices, the user can continue to operate the content on the device B by responding to a connection request in a device to be switched, such as the device B.

However, in an actual usage scenario, the user may frequently make successive transmissions of the same content handled by the same application in device a and device B. Therefore, it is important to shorten the time consumption of the continuous transmission of the multi-device application and to ensure the success rate of the continuous transmission of the multi-device application.

Disclosure of Invention

In order to solve the technical problems, the application provides a multi-device application connection method, a device and a storage medium, which aim to shorten the time consumption of multi-device application connection transmission and simultaneously ensure the success rate of multi-device application connection transmission.

In a first aspect, the present application provides a multi-device application connection method, which is applied to a first device. The method comprises the following steps: in the process of editing a first file by using a first application registered as a continuing application, sending an application continuing request aiming at the first application to second equipment; when the first file is not subjected to continuous transmission for the first time, after receiving an application continuous response of the second equipment for an application continuous request, adopting a differential transmission mode to transmit differential data in the first file to the second equipment; when the first file is not transmitted continuously for the first time, the time for transmitting the first file by adopting the differential transmission mode is smaller than the time for transmitting the first file by adopting the full transmission mode.

Therefore, when the first file to be continuously transmitted is not continuously transmitted for the first time, the differential transmission mode is directly adopted to transmit differential data, and all data of the first file is not transmitted to the second device, so that the time spent for continuously transmitting the files in the process of continuously applying and connecting multiple devices is greatly shortened.

In addition, as the differential transmission mode is adopted for the repeated continuous transmission of the first file between the first device and the second device, the data volume of each continuous transmission is much smaller than that of the whole first file, thereby effectively avoiding the condition of transmission failure in the process of continuous application of multiple devices and greatly improving the success rate of continuous application transmission of the multiple devices.

According to the first aspect, whether a file data information table corresponding to the first file exists locally or not is detected, information in the file data information table is used for indicating the second equipment to start a first application installed on the second equipment after application continuing response is made, and the first file is loaded; when a file data information table corresponding to the first file exists, determining that the first file is not first transmitted continuously; and when the file data information table corresponding to the first file does not exist, determining the first file as the first continuous transmission.

Therefore, only the first file which is transmitted continuously for the first time is transmitted in a full transmission mode, and when the first file is transmitted continuously subsequently, the differential part transmitted in a differential transmission mode is directly adopted, so that the time spent for continuously transmitting the files in the process of continuously applying multiple devices is greatly shortened.

According to the first aspect, or any implementation manner of the first aspect, after determining that the first file is transmitted continuously for the first time, the method further includes: constructing a file data information table corresponding to the first file according to the first application and the first file, wherein the file data information table carries all data of the first file; and after receiving an application continuing response of the second equipment for the application continuing request, transmitting the file data information table to the second equipment by adopting a full transmission mode.

According to the first aspect, or any implementation manner of the first aspect, according to the first application and the first file, a file data information table corresponding to the first file is constructed, including: generating a file unique identifier according to the first application and the first file, wherein the file unique identifier indicates the relationship between the first file and the first application; generating file basic public information and a data atom set according to the first file, wherein the data atom set carries all data of the first file; generating a file data feature code according to the data in the data atom set, wherein the file data feature code is used for identifying the data in the first file; and generating a file data information table according to the file unique identifier, the file basic public information, the data atom set and the file data feature codes.

According to the first aspect, or any implementation manner of the first aspect, before the delta data in the first file is transmitted to the second device in the delta transmission manner, the method further includes: randomly scanning the first file to generate a temporary data atom set; generating a temporary file data feature code according to the data in the temporary data atom set; when the temporary file data feature code is different from the file data feature code recorded in the file data information table, executing a step of transmitting the differential data in the first file to the second device by adopting a differential transmission mode; when the temporary file data feature code is the same as the file data feature code recorded in the file data information table, the data of the first file is not transmitted to the second device.

According to the first aspect, or any implementation manner of the first aspect, the method further includes: after the differential data in the first file is transmitted to the second device by adopting a differential transmission mode, or the file data information table is transmitted to the second device by adopting a full transmission mode, the first file is saved, and an interface capable of editing the first file is exited.

Thus, when the first file is continued to the first application editing process in the second device, the interface for editing the first file in the first device is exited, so that the first device is prevented from continuously carrying out data transmission with the second device, and the power consumption of the device and the occupation of resources are reduced.

According to the first aspect, or any implementation manner of the first aspect, after exiting the interface where the first file may be edited, the method further includes: when receiving an application connection request for the first application sent by the second device when the first application is not in a foreground operation, adding an application connection identifier on a first application icon corresponding to the first application; and responding to the operation of the first application icon added with the application connection identifier, switching the first application into foreground operation, loading a local first file, and transmitting differential data of the first file by the second equipment in a differential transmission mode. In other words, in the scenario of multi-device application connection, the first device may serve as a transmitting end of data or may serve as a receiving end of data, so that seamless collaborative operation of application connection service is better implemented between the first device and the second device.

According to the first aspect, or any implementation manner of the first aspect, the file data information table is updated according to the delta data.

Therefore, when the application connection is carried out later, whether data need to be transmitted or not can be accurately judged.

According to the first aspect, or any implementation manner of the first aspect, after adding an application connection identifier to a first application icon corresponding to a first application, the method further includes: when the operation of the first application icon added with the application continuing identification is not received within the set time, canceling the application continuing identification on the first application icon; after the application connection identifier is canceled, the first device and the second device cannot conduct application connection aiming at the first application.

In this way, the first equipment and the second equipment are allowed to carry out application connection in the set time, if the user does not make application connection response to the application connection request in the set time, namely, the first application icon carrying the application connection identifier is triggered, the application connection identifier is canceled, the first equipment is prevented from being in a state of waiting for the user to make application response all the time, and the power consumption of the first equipment is reduced.

According to the first aspect, or any implementation manner of the first aspect, the method further includes: after the differential transmission mode is adopted to transmit differential data in the first file to the second equipment or the full transmission mode is adopted to transmit the file data information table to the second equipment, the file data information table is continuously remained on an interface capable of editing the first file; the content of the first file displayed in the interface of the first file is kept synchronous with the content of the first file in the second device.

Thereby, a seamless co-processing of the first application is achieved between the first device and the second device.

It can be understood that after the second device displays the first file, the user edits the first file at which terminal device, and the device serves as a transmitting end of data in the application connection process, and the other device serves as a receiving end.

According to the first aspect, or any implementation manner of the first aspect, before sending an application connection request for the first application to the second device, the method further includes: the first device and the second device are ensured to start the application connection function, the Bluetooth function and the wireless local area network function.

Thus, the first equipment and the second equipment can form a super terminal, and seamless collaborative operation of application connection service is realized between the first equipment and the second equipment.

In a second aspect, the present application provides a multi-device application connection method, which is applied to a second device. The method comprises the following steps: under the condition that the second device installs the first application, when receiving an application connection request for the first application sent by the first device, adding an application connection identifier on a first application icon corresponding to the first application; responding to the operation of the first application icon added with the application connection identifier, sending an application connection response made for the application connection request to the first equipment, and switching the first application to be operated in the foreground; after receiving a file data information table transmitted by a first device in a full transmission mode, analyzing all data of a first file from a data atom set in the file data information table, loading and displaying the data, and storing the file data information table to a local place; after receiving the differential data of the first file transmitted by the first device in the differential transmission mode, loading the differential data, displaying the locally stored first file, and updating the locally stored file data information table according to the differential data.

Therefore, only when the first file which is transmitted continuously for the first time is transmitted in a full transmission mode, the first file needs to be waited for loading, when the first file is transmitted continuously subsequently, the differential part transmitted by the differential transmission mode is directly loaded by the first equipment, and the rest identical parts are loaded locally, so that the time spent for transmitting the files continuously in the process of multi-equipment application connection is greatly shortened.

According to a second aspect, the method further comprises: after receiving an application connection request for a first application sent by a first device, canceling the application connection identifier on the first application icon when the operation of the first application icon added with the application connection identifier is not received within a set time; after the application connection identifier is canceled, the second device cannot connect with the first device for the first application.

In this way, the second device and the first device are allowed to carry out application connection within the set time, if the user does not make application connection response to the application connection request in the second device within the set time, namely, the first application icon carrying the application connection identifier is triggered, the application connection identifier is canceled, the second device is prevented from being in a state of waiting for the user to make application response all the time, and the power consumption of the second device is reduced.

According to a second aspect, or any implementation manner of the second aspect above, the method further comprises: under the condition that the second device does not install the first application, when an application connection request for the first application sent by the first device is received, prompting a user to install the first application.

Therefore, after the user is reminded of installing the first application, the subsequent first equipment and the second equipment can conduct application connection aiming at the first application, seamless switching of the first file in the first application in the first equipment and the second equipment is achieved, and the first equipment and the second equipment cooperate with each other.

In a third aspect, the present application provides a terminal device. The terminal device includes: a memory and a processor, the memory and the processor coupled; the memory stores program instructions that, when executed by the processor, cause the terminal device to perform the instructions of the method of the first aspect or any of the possible implementations of the first aspect, or cause the terminal device to perform the instructions of the method of the second aspect or any of the possible implementations of the second aspect.

The terminal device may be the first device or the second device.

Illustratively, when the terminal device is the first device, any implementation manner of the third aspect and any implementation manner of the third aspect correspond to any implementation manner of the first aspect and the first aspect, respectively. Therefore, the technical effects corresponding to the third aspect and any implementation manner of the third aspect may be referred to the technical effects corresponding to the first aspect and any implementation manner of the first aspect, which are not described herein.

Illustratively, when the terminal device is the second device, any implementation manner of the third aspect and any implementation manner of the third aspect correspond to any implementation manner of the second aspect and the second aspect, respectively. Therefore, the technical effects corresponding to any implementation manner of the third aspect and the third aspect may refer to the technical effects corresponding to any implementation manner of the second aspect and the second aspect, which are not described herein.

In a fourth aspect, the present application provides a computer readable medium storing a computer program comprising instructions for performing the method of the first aspect or any possible implementation of the first aspect, or instructions for performing the method of the second aspect or any possible implementation of the second aspect.

Illustratively, when the computer program stored in the computer readable storage medium is instructions for performing the method of the first aspect or any of the possible implementations of the first aspect, any of the implementations of the fourth aspect corresponds to any of the implementations of the first aspect and the first aspect, respectively. Therefore, the technical effects corresponding to the fourth aspect and any implementation manner of the fourth aspect may be referred to the technical effects corresponding to the first aspect and any implementation manner of the first aspect, which are not described herein.

Illustratively, when the computer program stored in the computer readable storage medium is instructions for performing the second aspect or any of the possible implementations of the second aspect, any of the fourth aspect and any of the implementation of the fourth aspect corresponds to any of the second aspect and any of the implementation of the second aspect, respectively. Therefore, the technical effects corresponding to any implementation manner of the fourth aspect may be referred to the technical effects corresponding to any implementation manner of the second aspect, and are not described herein.

In a fifth aspect, the present application provides a computer program comprising instructions for performing the method of the first aspect or any possible implementation of the first aspect, or for performing the method of the second aspect or any possible implementation of the second aspect.

Illustratively, when the computer program is instructions for performing the first aspect or any of the possible implementations of the first aspect, any of the fifth aspect and any of the implementations of the fifth aspect correspond to the first aspect and any of the implementations of the first aspect, respectively. Technical effects corresponding to any implementation manner of the fifth aspect may be referred to the technical effects corresponding to any implementation manner of the first aspect, and are not described herein.

Illustratively, when the computer program is instructions for performing the second aspect or any of the possible implementations of the second aspect, any of the fifth aspect and any of the implementations of the fifth aspect correspond to the second aspect and any of the implementations of the second aspect, respectively. Technical effects corresponding to any implementation manner of the fifth aspect may be referred to technical effects corresponding to any implementation manner of the second aspect, and will not be described herein.

In a sixth aspect, the present application provides a chip comprising processing circuitry, a transceiver pin. Wherein the transceiver pin and the processing circuit communicate with each other via an internal connection path, the processing circuit performing the method of the first aspect or any one of the possible implementation manners of the first aspect, or the method of the second aspect or any one of the possible implementation manners of the second aspect, to control the receiving pin to receive signals, to control the transmitting pin to transmit signals.

Illustratively, when the processing circuitry in the chip performs the method of the first aspect or any one of the possible implementations of the first aspect, the sixth aspect and any one of the implementations of the sixth aspect correspond to the first aspect and any one of the implementations of the first aspect, respectively. Therefore, the technical effects corresponding to the sixth aspect and any implementation manner of the sixth aspect may be referred to the technical effects corresponding to the first aspect and any implementation manner of the first aspect, which are not described herein.

Illustratively, when the processing circuit in the chip performs the method of the second aspect or any one of the possible implementations of the second aspect, the sixth aspect and any one of the implementations of the sixth aspect correspond to the second aspect and any one of the implementations of the second aspect, respectively. Thus, the method is simple. Technical effects corresponding to any implementation manner of the sixth aspect may be referred to technical effects corresponding to any implementation manner of the second aspect and the second aspect, and are not described herein.

Drawings

FIG. 1 is a schematic diagram of a scenario illustrating an exemplary multi-device application splice;

fig. 2 is a schematic diagram of a hardware structure of an exemplary terminal device;

fig. 3 is a schematic diagram of a software architecture of an exemplary terminal device;

FIG. 4 is a schematic diagram of an exemplary illustrated superterminal;

FIGS. 5-10 are user interface diagrams illustrating exemplary set-up preconditions for a multi-device application continuation implementation;

FIGS. 11 and 12 are diagrams of exemplary user interfaces for triggering an application continuation request;

fig. 13-16 are user interface diagrams illustrating response to an application continuation request;

FIG. 17 is a diagram illustrating a user interface as a receiving end after starting an application connection;

FIG. 18 is a diagram illustrating a user interface as a sender after displaying successively transmitted data as a receiver;

FIG. 19 is a schematic diagram of an exemplary user interface for editing in a device that receives successively transmitted data;

FIG. 20 is a diagram illustrating a user interface as a receiving end after a re-trigger application connection is illustratively shown;

fig. 21 is a schematic diagram illustrating a multi-device application connection method provided in an embodiment of the present application;

fig. 22 is a schematic diagram illustrating a multi-device application connection method provided in an embodiment of the present application;

fig. 23 is a schematic diagram illustrating a multi-device application connection method according to an embodiment of the present application.

Detailed Description

The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.

The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone.

The terms first and second and the like in the description and in the claims of embodiments of the present application are used for distinguishing between different objects and not necessarily for describing a particular sequential order of objects. For example, the first target object and the second target object, etc., are used to distinguish between different target objects, and are not used to describe a particular order of target objects.

In the embodiments of the present application, words such as "exemplary" or "such as" are used to mean serving as examples, illustrations, or descriptions. 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.

In the description of the embodiments of the present application, unless otherwise indicated, the meaning of "a plurality" means two or more. For example, the plurality of processing units refers to two or more processing units; the plurality of systems means two or more systems.

In order to better understand the technical scheme provided by the embodiment of the application, before the technical scheme provided by the embodiment of the application is described, a multi-equipment application connection scene related to the application is described.

Specifically, the multi-device application connection is seamless circulation of connection tasks among a plurality of devices under the near-field same account number. As shown in fig. 1, assuming that a user operates an application editing document 1 (the size of the document 1 is 100M) supporting connection in a mobile phone a, when a requirement of switching equipment is generated, the user only needs to respond to a connection request in equipment to be switched to, such as a computer B, and can continuously transmit the document 1 with the size of 100M in the mobile phone a to the computer B, so that the user can continuously edit the document 1 in the computer B, thereby being capable of meeting the requirement that the user edits the document 1 by using different equipment in different scenes, such as editing the document 1 by using the mobile phone a which is convenient to carry in a scene without the computer B, and editing the document 1 by using the computer B in a scene with the computer B.

It should be noted that in the actual application scenario, in most cases, the same content may be transmitted in the multi-device application connection process, that is, the user only performs partial new and modification on the content in different devices. However, in the current multi-device application connection process, the connection transmission between different devices uses a full-volume rewriting manner. Taking the content continuously transmitted by the user in the mobile phone A and the computer B as the document 1 as an example, when the content is continuously transmitted between the mobile phone A and the computer B in a full-volume rewriting mode, no matter how much content is newly added or modified in the document 1, the document 1 of 100M is completely transmitted to the computer B each time, for example, when the content is continuously transmitted from the mobile phone A to the computer B, the user deletes the content of 2M in the document 1 by using the computer B, and the updated document 1 is continuously transmitted to the mobile phone A, the document 1 of 98M is completely transmitted to the mobile phone A, or when the user uses the computer B to continuously transmit the updated document 1 to the mobile phone A, the document 1 of 105M is completely transmitted to the mobile phone A.

Therefore, the multi-device application continuous transmission is carried out based on the full-volume rewriting mode, and for repeated continuous transmission of the same content, a great amount of time is required to be spent each time, the time consumption is long, and the user experience is poor.

In addition, for the scene that the content continuously transmitted by the multi-device application is a large-capacity file, the transmission is repeated in full quantity, and the transmission failure is easy to occur.

In view of this, the present application provides a multi-device application connection method, which aims to shorten the time consumed by repeatedly performing application connection transmission on the same content between different devices, and to ensure the success rate of multi-device application connection transmission.

In order to better understand the technical solution provided in the embodiments of the present application, before describing the technical solution of the embodiments of the present application, a hardware structure of a terminal device applicable to the embodiments of the present application is first described with reference to the accompanying drawings.

The terminal device applicable to the embodiment of the present application may be, for example, a mobile phone, a tablet computer, a notebook computer, a desktop computer, a smart watch, etc., which are not listed here, but the embodiment is not limited thereto. For convenience of explanation, this embodiment will be described by taking a mobile phone as an example.

Referring to fig. 2, the terminal device 100 may include: processor 110, external memory interface 120, internal memory 121, universal serial bus (universal serial bus, USB) interface 130, charge management module 140, power management module 141, battery 142, antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, headset interface 170D, sensor module 180, keys 190, motor 191, indicator 192, camera 193, display 194, and subscriber identity module (subscriber identificationmodule, SIM) card interface 195, etc.

By way of example, in some implementations, the sensor module 180 may include a pressure sensor, a gyroscope sensor, a barometric sensor, a magnetic sensor, an acceleration sensor, a distance sensor, a proximity sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, etc., which are not further illustrated herein.

Furthermore, it should be noted that the processor 110 may include one or more processing units, for example: the processor 110 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 memory, 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.

It is understood that the controller may be a neural hub and command center of the terminal device 100. In practical application, the controller can generate operation control signals according to the instruction operation codes and the time sequence signals to complete instruction fetching and instruction execution control.

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

For example, in some implementations, the processor 110 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 asynchronousreceiver/transmitter, UART) interface, a mobile industry processor interface (mobile industry processorinterface, 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.

With continued reference to fig. 2, the exemplary charge management module 140 is operable to receive a charge input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging implementations, the charge management module 140 may receive a charging input of the wired charger through the USB interface 130. In some wireless charging implementations, the charging management module 140 may receive wireless charging input through a wireless charging coil of the terminal device 100. The charging management module 140 may also supply power to the terminal device through the power management module 141 while charging the battery 142.

With continued reference to fig. 2, an exemplary power management module 141 is used to connect the battery 142, the charge management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and/or the charge management module 140 and provides power to the processor 110, the internal memory 121, the external memory, the display 194, the camera 193, the wireless communication module 160, and the like. The power management module 141 may also be configured to monitor battery capacity, battery cycle number, battery health (leakage, impedance) and other parameters. In other implementations, the power management module 141 may also be provided in the processor 110. In other implementations, the power management module 141 and the charge management module 140 may also be disposed in the same device.

With continued reference to fig. 2, exemplary wireless communication functions of the terminal device 100 may be implemented by an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, a modem processor, a baseband processor, and the like.

The

antennas

1 and 2 are used to transmit and receive electromagnetic wave signals. Each antenna in the terminal device 100 may be used to cover a single or multiple communication bands. Different antennas may also be multiplexed to improve the utilization of the antennas. For example: the antenna 1 may be multiplexed into a diversity antenna of a wireless local area network. In other implementations, the antenna may be used in conjunction with a tuning switch.

With continued reference to fig. 2, the mobile communication module 150 may provide an exemplary solution for wireless communication including 2G/3G/4G/5G, etc. applied on the terminal device 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (low noise amplifier, LNA), etc. The mobile communication module 150 may receive electromagnetic waves from the antenna 1, perform processes such as filtering, amplifying, and the like on the received electromagnetic waves, and transmit the processed electromagnetic waves to the modem processor for demodulation. The mobile communication module 150 can amplify the signal modulated by the modem processor, and convert the signal into electromagnetic waves through the antenna 1 to radiate. In some implementations, at least some of the functional modules of the mobile communication module 150 may be disposed in the processor 110. In some implementations, at least some of the functional modules of the mobile communication module 150 may be disposed in the same device as at least some of the modules of the processor 110.

In addition, the modem processor may include a modulator and a demodulator. The modulator is used for modulating the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used for demodulating the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low frequency baseband signal to the baseband processor for processing. The low frequency baseband signal is processed by the baseband processor and then transferred to the application processor. The application processor outputs sound signals through an audio device (not limited to the speaker 170A, the receiver 170B, etc.), or displays images or video through the display screen 194. In some implementations, the modem processor may be a stand-alone device. In other implementations, the modem processor may be provided in the same device as the mobile communication module 150 or other functional module, independent of the processor 110.

With continued reference to fig. 2, the exemplary wireless communication module 160 may provide solutions for wireless communication including wireless local area network (wireless local area networks, WLAN) (e.g., wireless fidelity (wireless fidelity, wi-Fi) network), bluetooth (BT), global navigation satellite system (global navigation satellite system, GNSS), frequency modulation (frequency modulation, FM), near field wireless communication technology (near field communication, NFC), infrared technology (IR), etc., as applied on the terminal device 100. The wireless communication module 160 may be one or more devices that integrate at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, modulates the electromagnetic wave signals, filters the electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be transmitted from the processor 110, frequency modulate it, amplify it, and convert it to electromagnetic waves for radiation via the antenna 2.

Specifically, in the technical solution provided in the embodiment of the present application, the terminal device 100 may determine, through the wireless communication module 160, specifically WLAN and BT, whether other terminal devices that meet the near field communication condition are located around. And when other terminal devices meeting near field communication conditions are determined to exist around the terminal device, and the terminal devices and the terminal device 100 are logged in to be the same user account, application connection between the terminal devices is realized.

In addition, it should be noted that the terminal device 100 implements a display function through the GPU, the display screen 194, the application processor, and the like. The GPU is a microprocessor for image processing, and is connected to the display 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or change display information.

With continued reference to FIG. 2, exemplary display 194 is used to display images, videos, and the like. The display 194 includes a display panel. The display panel may employ a liquid crystal display (liquid crystal display, LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED) or an active-matrix organic light-emitting diode (matrix organic light emitting diode), a flexible light-emitting diode (flex), a mini, a Micro led, a Micro-OLED, a quantum dot light-emitting diode (quantum dot light emitting diodes, QLED), or the like. In some implementations, the terminal device 100 may include 1 or N display screens 194, N being a positive integer greater than 1.

In addition, it should be noted that the terminal apparatus 100 may implement a photographing function through an ISP, a camera 193, a video codec, a GPU, a display 194, an application processor, and the like.

In addition, the ISP is used to process data fed back from the camera 193. For example, when photographing, the shutter is opened, light is transmitted to the camera photosensitive element through the lens, the optical signal is converted into an electric signal, and the camera photosensitive element transmits the electric signal to the ISP for processing and is converted into an image visible to naked eyes. ISP can also optimize the noise, brightness and skin color of the image. The ISP can also optimize parameters such as exposure, color temperature and the like of a shooting scene. In some implementations, the ISP may be provided in the camera 193.

In addition, it is also noted that the camera 193 is used for capturing still images or videos. The object generates an optical image through the lens and projects the optical image onto the photosensitive element. The photosensitive element may be a charge coupled device (charge coupled device, CCD) or a Complementary Metal Oxide Semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, which is then transferred to the ISP to be converted into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV, or the like format. In some implementations, the terminal device 100 may include 1 or N cameras 193, N being a positive integer greater than 1.

In addition, the digital signal processor is used to process digital signals, and may process other digital signals in addition to digital image signals. For example, when the terminal device 100 selects a frequency bin, the digital signal processor is used to fourier transform the frequency bin energy, or the like.

Furthermore, it should be noted that video codecs are used for compressing or decompressing digital video. The terminal device 100 may support one or more video codecs. In this way, the terminal device 100 can play or record video in various encoding formats, for example: dynamic picture experts group (moving picture experts group, MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

With continued reference to fig. 2, the external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, to extend the memory capabilities of the terminal device 100, as an example. The external memory card communicates with the processor 110 through an external memory interface 120 to implement data storage functions. For example, files such as music, video, etc. are stored in an external memory card.

With continued reference to fig. 2, by way of example, the internal memory 121 may be used to store computer executable program code that includes instructions. The processor 110 executes various functional applications of the terminal device 100 and data processing by executing instructions stored in the internal memory 121. The internal memory 121 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 (such as audio data, phonebook, etc.) created during use of the terminal device 100, and the like. In addition, the internal memory 121 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.

In addition, it should be noted that the terminal device 100 may implement audio functions through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the earphone interface 170D, and the application processor. Such as music playing, recording, etc.

In addition, it should be noted that the audio module 170 is configured to convert digital audio information into an analog audio signal output, and also configured to convert an analog audio input into a digital audio signal. The audio module 170 may also be used to encode and decode audio signals. In some implementations, the audio module 170 may be disposed in the processor 110, or some functional modules of the audio module 170 may be disposed in the processor 110.

With continued reference to fig. 2, exemplary keys 190 include a power-on key, a volume key, and the like. The keys 190 may be mechanical keys. Or may be a touch key. The terminal device 100 may receive key inputs, generating key signal inputs related to user settings and function controls of the terminal device 100.

With continued reference to FIG. 2, exemplary, motor 191 may generate a vibration alert. The motor 191 may be used for incoming call vibration alerting as well as for touch vibration feedback. For example, touch operations acting on different applications (e.g., photographing, audio playing, etc.) may correspond to different vibration feedback effects. The motor 191 may also correspond to different vibration feedback effects by touching different areas of the display screen 194. Different application scenarios (such as time reminding, receiving information, alarm clock, game, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect may also support customization.

With continued reference to fig. 2, the indicator 192 may be, for example, an indicator light, may be used to indicate a state of charge, a change in charge, may be used to indicate a message, missed call, notification, or the like.

As to the hardware structure of the terminal device 100, it should be understood that the terminal device 100 shown in fig. 2 is only one example, and in a specific implementation, the terminal device 100 may have more or fewer components than shown in the drawings, may combine two or more components, or may have different component configurations. The various components shown in fig. 2 may be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and/or application specific integrated circuits.

In addition, it should be noted that, in the actual application, the terminal device 100 may be a terminal device that initiates a multi-device application connection request, that is, a sending end of a file, or may be a terminal device that responds to a multi-device application connection request, that is, a receiving end of a file.

In order to better understand the software structure of the terminal device 100 shown in fig. 2, the software structure of the terminal device 100 will be described below. Before explaining the software structure of the terminal device 100, an architecture that the software system of the terminal device 100 can employ will be first described.

Specifically, in practical applications, the software system of the terminal device 100 may adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture.

Furthermore, it is understood that software systems currently used by mainstream terminal devices include, but are not limited to, windows systems, android systems, and iOS systems. For convenience of explanation, the embodiment of the present application takes an Android system with a layered architecture as an example, and illustrates a software structure of the terminal device 100.

In addition, the multi-device application connection scheme provided in the embodiments of the present application is applicable to other systems in specific implementations.

Referring to fig. 3, a software structure block diagram of the terminal device 100 according to an embodiment of the present application is shown.

As shown in fig. 3, the layered architecture of the terminal device 100 divides the software into several layers, each of which has a clear role and division of labor. The layers communicate with each other through a software interface. In some implementations, the Android system is divided into four layers, from top to bottom, an application layer, an application framework layer, an Zhuoyun row (Android run) and system libraries, and a kernel layer, respectively.

The application layer may include a series of application packages, among other things. As shown in fig. 3, the application package may include applications such as memo, WLAN, bluetooth, setup, etc., which are not to be construed as limiting the application.

It is understood that the memo application shown in fig. 3 may be an application registered in advance to the multi-device application connection server, that is, in this embodiment, the memo application is a connection application supporting file connection transmission.

In addition, as can be seen from the description of the above hardware structure, one condition for implementing multi-device application connection is that multiple devices of the same user account are logged in, so as to satisfy the near field communication condition. In the present embodiment, the near field communication condition is, for example, WLAN and bluetooth are turned on.

Further, in a specific operation, on the premise that application connection can be directly performed, a plurality of devices which are required to meet near field communication conditions access the same WLAN, and bluetooth pairing is established.

Further, regarding the setting shown in fig. 3, in the present embodiment, an entry for opening an application connection is specifically provided so that a user opens an application connection function through the setting application.

It is appreciated that for opening of an application-continued function, in some implementations, the corresponding application may also be provided separately for the user to open the function.

With continued reference to FIG. 3, by way of example, the application framework layer shown in FIG. 3 provides an application programming interface (application programminginterface, API) and programming framework for application programs of the application layer. In some implementations, these programming interfaces and programming frameworks can be described as functions. As shown in FIG. 3, the application framework layer may include functions of a notification manager, a content provider, a window manager, a resource manager, a multi-device application connectivity module, etc., which are not to be limiting in this application.

The multi-device application connection module is specifically configured to detect whether a near field communication condition is currently satisfied after a user opens a multi-device application connection function, and whether devices satisfying the near field communication condition all log in the same user account.

In addition, the multi-device application connection module is further configured to determine, when it is determined that the application parsing request is satisfied, which transmission mode is adopted for the file that is transmitted in connection, for example, a transmission mode of full transmission or a transmission mode of delta transmission, and then perform connection transmission on the file according to the determined transmission mode.

The operation of the multi-device application continuation module process, and specific processing details, are described in detail below for a multi-device application continuation method.

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.

The content provider is used to store and retrieve data and make such data accessible to applications. The data may include video, image, audio, phone calls made and received, browsing history and bookmarks, phone book, etc., which are not listed here, but are not limiting in this application.

The window manager is used for managing window programs. The window manager can acquire the size of the display screen, judge whether a status bar exists, lock the screen, intercept the screen and the like.

The resource manager provides various resources for the application program, such as localization strings, icons, pictures, layout files, video files, etc., which are not listed here, but are not limiting in this application.

It should be understood that the above description is only an example for better understanding of the technical solution of the present embodiment, and is not to be taken as the only limitation of the present embodiment.

It should be understood that the above-mentioned division of the functional modules is merely an example for better understanding the technical solution of the present embodiment, and is not the only limitation of the present embodiment. In practical applications, the above functions may also be integrated into one functional module, which is not limited in this embodiment.

With continued reference to FIG. 3, for the exemplary system library and An Zhuoyun rows, the installation row (Android run) includes a core library and virtual machines. Android run is responsible for scheduling and management of the Android system.

Specifically, the core library comprises 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.

Further, it is understood that the application layer and the application framework layer run in virtual machines. 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.

With continued reference to FIG. 3, for an exemplary system library and An Zhuoyun rows, the system library may include a plurality of functional modules. For example: surface manager (surface manager), media Libraries (Media Libraries), three-dimensional (3D) graphics processing Libraries (e.g., openGL ES), two-dimensional (2D) graphics engines (e.g., SGL), etc.

In particular, the surface manager is used to manage the display subsystem and provides a fusion of 2D and 3D layers for multiple applications.

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 three-dimensional graphic processing library is used for realizing three-dimensional graphic drawing, image rendering, synthesis, layer processing and the like.

It will be appreciated that the 2D graphics engine described above is a drawing engine for 2D drawing.

Furthermore, it can be appreciated that the kernel layer in the Android system is a layer between hardware and software. The kernel layer at least comprises a display driver, a Bluetooth driver, a WIFI driver and the like. The WIFI driver is used to drive the WIFI chip to enable the terminal device to access the WLAN network, and the bluetooth driver is used to drive the bluetooth chip to search for terminal devices that can be paired around and connect with the terminal device that satisfies the near field communication condition in a pairing manner, so that the multi-device application connection can be realized in the case of opening the multi-device application connection function.

As to the software structure of the terminal device 100, it will be understood that the layers and the components included in the layers in the software structure shown in fig. 3 do not constitute a specific limitation on the terminal device 100. In other embodiments of the present application, terminal device 100 may include more or fewer layers than shown, and more or fewer components may be included in each layer, as the present application is not limited.

With respect to the above scenario, based on the hardware structure and the software structure of the terminal device described in fig. 2 and fig. 3, a specific description is given below for implementing the multi-device application connection method provided in the embodiment of the present application.

Referring to fig. 4, a super terminal formed by a plurality of terminal devices, such as device 10, device 20 and device 30, which log in to the same user account and access the same WLAN, within a range that can be searched by bluetooth is exemplarily shown.

It should be noted that, in this embodiment, the super terminal specifically refers to that seamless cooperation operation can be implemented between any two terminal devices that compose the super terminal.

By way of example, the scenario of seamless collaborative operation supported by the super terminal may include call sharing, notification sharing, mouse sharing, and the above-mentioned application connection, for example. In particular, in the embodiment provided in the present application, in order to implement multi-device application connection, it is necessary to ensure that the terminal device opens an application connection function provided in the super terminal function.

Regarding the manner in which the super terminal function and the application connection function are turned on, the apparatus 10 constituting the super terminal in fig. 4 is exemplified, and is described with reference to fig. 5 to 10.

Referring to fig. 5 (1), one interface (hereinafter referred to as the main interface) of the apparatus 10 is exemplarily shown. For example, one or more controls may be included in the main interface. Controls include, but are not limited to: network controls, power controls, application icon controls, and the like.

With continued reference to the main interface shown in fig. 5 (1), exemplary application icon controls include, but are not limited to: clock application icon controls, calendar application icon controls, gallery application icon controls, memo application icon controls, file management application icon controls, email application icon controls, music application icon controls, calculator application icon controls, weather application icon controls, browser application icon controls, setup application icon controls, and the like, to name but a few.

With continued reference to the main interface shown in fig. 5 (1), the device 10, illustratively, initiates the setup interface shown in fig. 5 (2) in response to a user operation after the user clicks the setup application icon control.

Referring to the setup interface shown in fig. 5 (2), one or more controls may be included in the setup interface, for example. Controls include, but are not limited to: the present application is not limited in this regard, and the control for exiting the setup interface, the control for entering the account center interface 10a-1, the control for entering the super terminal interface 10a-2, the control for entering the WLAN interface 10a-3, the control for entering the bluetooth interface 10a-4, the control for entering the smart multi-window interface 10a-5, the control for entering the display and brightness interface, the control for entering the sound and vibration interface, the control for entering the notification interface, the control for entering the battery interface, the control for entering the storage interface, the control for entering the security interface, and the like are not specifically recited herein.

It can be understood that, by operating each control in the setting interface, the user jumps from the setting interface to the interface corresponding to the operated control in response to the operation behavior of the user by using the device 10 in the setting interface, so that the user sets the corresponding setting on the jumped interface, for example, the screen brightness, the text size, the automatic locking time, the lift-up wake-up function, etc. of the device 10 are set on the display and brightness interface, which is not limited herein.

With continued reference to the setup interface shown in fig. 5 (2), the device 10 initiates the account center interface shown in fig. 6 in response to a user operation, illustratively after the user clicks on the control 10 a-1.

Referring to the account center interface shown in fig. 6, one or more controls may be included in the account center interface, for example. Controls include, but are not limited to: the control for exiting the account center interface to return to the setting interface, various controls for setting information related to the user account, such as personal information control, account and security control, login device management control, data synchronization control, search device control, member center control, privacy center control, and exit account control for exiting the currently logged-in user account, etc., are not listed here any more, and the application is not limited to this.

With continued reference to fig. 6, the user account currently logged in by the device 10 is illustratively shown as "Zhang San123". Based on the above description of the constituent super terminals shown in fig. 4, it is known that the devices 10, 20 and 30 want to constitute the super terminal shown in fig. 4, and in the case that the user account registered by the device 10 is "Zhang san 123", the devices 20 and 30 also need to register the user account of "Zhang san 123". Similar to the device 10, the method for logging in the user account by the device 20 and the device 30 starts the interface for logging in the user account by operating the corresponding control, and inputs the password corresponding to the user account of "Zhang San123" and "Zhang San123" in the interface, and then logs in, which is specific implementation details, and details are not repeated here, and the application is not limited.

Thus, device 10, device 20, and device 30 complete one of the requirements that make up the super terminal by logging in to the same user account, such as "Zhang San123".

For example, after the device 10, the device 20, and the device 30 are all logged into the user account "Zhang San123", the three terminal devices may be sequentially operated to start the application connection function. The start-up entry for the application connection function is specifically entered from the super terminal interface, and for convenience of explanation, the manner in which the application connection function is started will be explained below by taking the device 10 as an example.

Referring to fig. 7 (1), exemplary, upon a user clicking on control 10a-2, device 10 initiates the superterminal interface shown in fig. 7 (2) in response to a user operation.

Referring to the superterminal interface shown in fig. 7 (2), one or more controls may be included in the superterminal interface, as an example. Controls include, but are not limited to: the control for backing from the super terminal interface to the setting interface, the control 10b-1 for entering the application connection interface, the control for entering the call sharing interface, the control for entering the notification sharing interface, the control for entering the mouse sharing interface, and the like are not specifically mentioned herein.

With continued reference to the super terminal interface shown in fig. 7 (2), illustratively, after the user clicks the control 10b-1, the device starts the application connection interface shown in fig. 8 (1) or fig. 8 (2) in response to the user's operation.

It should be noted that, the device supporting the function of the super terminal, the functions of application connection, call sharing, notification sharing, and mouse sharing supported by the super terminal are usually opened by default. That is, after clicking the control of the corresponding function on the interface of the super terminal and entering the corresponding interface, the switch control in the interface is in an on state, such as control 10c-1 shown in fig. 8 (1).

For example, in a practical application, the user may manually turn off a function supported by the super terminal, such as turning off an application connection function. In response to this situation, when the user clicks the control 10b-1, the device responds to the user operation, and the application connection interface started is as shown in fig. 8 (2), that is, the control 10c-1 is in the closed state. For this case, if the user wants to connect the device 10, the device 20, and the device 30, he needs to enter the application connection interface for managing the application connection function by the above operation, and by operating the control 10c-1, he opens the application connection function, i.e., switches the control 10c-1 from the state shown in fig. 8 (2) to the state shown in fig. 8 (1).

Similar to the device 10, the device 20 and the device 3 start the application connection function by operating the corresponding control to start the application connection interface, and in this interface, the application connection function is started by operating the control similar to the control 10c-1, which is specific implementation details, and details are not repeated here, and the application is not limited.

Therefore, the device 10, the device 20 and the device 30 supporting the super terminal function are all set to start the application connection function, and a necessary condition for realizing the multi-device application connection method provided by the embodiment of the application is completed.

In addition, it should be noted that, as is apparent from the description of the constituent super terminals in fig. 4, the devices 10, 20 and 30 implement seamless cooperative operation, such as application connection, and not only need to start the application connection function, but also need to satisfy the near field communication condition. In the multi-device application connection scenario, the terminal device that requires application connection needs to turn on both bluetooth and WLAN functions.

Based on this, when the devices 20 and 30 do not turn on the bluetooth function and the WLAN function, the user may be prompted at the super terminal interface that the reason for the device being cooperated is not currently searched. Taking the device 10 as an example, when the user account registered by the device 10 is "Zhang San123", if the device 20 and the device 30 that can cooperate are not searched, a possible reason may be that the device 20 and the device 30 do not register the user account "Zhang San123", or the device 20 and the device 30 do not turn on the WLAN and bluetooth functions, as shown in (1) of fig. 9.

For example, in the case that no collaborative device is searched, the user may respectively go to the account centers of the device 20 and the device 30 according to the prompt given in the super terminal interface to determine whether the user account logged in by these 2 devices is "Zhang san 123", and when the user account is not "Zhang san 123", log in the user account of "Zhang san 123" again by the exit account control in the account center interface similar to that shown in fig. 6, which is described above, so as to solve the first reason given in fig. 9 (1).

For example, if the first reason given in (1) in fig. 9 is solved, that is, after the user account numbers logged in by the device 10, the device 20 and the device 30 are guaranteed to be "Zhang san 123", the device 20 and the device 30 capable of collaborative operation are still not displayed in the super terminal interface of the device 10. It may be further checked whether bluetooth and WLAN of device 10, device 20 and device 30 are all on.

Illustratively, still taking the device 10 as an example, regarding the turning on of bluetooth and WLAN, in some implementations, by sliding down in the direction of the arrow from the upper edge of the display interface of the device 10 as shown in fig. 10 (1), the device 10 displays a pull-down notification bar in the upper edge region of the display interface in response to this operation behavior, as shown in fig. 10 (2).

Referring to fig. 10 (2), illustratively, after displaying the drop-down notification bar, the user may directly click on the WLAN control and the bluetooth control in the drop-down notification bar, turning on the WLAN function and the bluetooth function with one button.

It will be appreciated that if the device 20 and the device 30 were previously worn by the device 10 in pairs and the WIFI to which the device 10 is currently connected was accessed, after the WLAN function and the bluetooth function are turned on, the device 20 and the device 30 will automatically access the WIFI to which the device 10 is currently connected and connect with each other and bluetooth with the device 10.

In addition, it can be understood that, in other implementation manners, the WLAN may be opened by operating the control 10a-3 that enters the WLAN interface in the setting interface, further entering the WLAN interface, operating the corresponding control in the interface to open the WLAN, and selecting an appropriate WIFI access, which is not described herein in detail, but the application is not limited.

Correspondingly, the Bluetooth can be started, the control 10a-4 entering the Bluetooth interface in the interface can be set by operating, the Bluetooth interface can be further entered, the corresponding control is operated in the interface to start the Bluetooth, and proper equipment is selected to finish Bluetooth wearing, so that details of specific implementation are not repeated here, and the Bluetooth wearing device is not limited in the application.

Thus, in turning on the WLAN and bluetooth of the device 10, the device 20, and the device 30 in any of the above manners, the 3 devices will search for each other as a cooperative device, respectively. Still taking device 10 as an example, at the super terminal interface of device 10, the searched collaborative devices are shown as device 20 and device 30, as shown in fig. 9 (2).

Regarding the manner in which the device 20 and the device 3 turn on bluetooth and WLAN, similar to the device 10, a bluetooth interface and a WLAN interface are started by operating corresponding controls, in which the device 20 and the device 30 turn on bluetooth and access corresponding WLAN by operating corresponding controls, or directly click on the controls for turning on WLAN and bluetooth by pulling down a notification bar, details of specific implementation are not repeated herein, and the application is not limited.

Thus, the device 10, the device 20 and the device 30 for setting the application connection starting function all start bluetooth and WLAN, and another necessary condition for realizing the multi-device application connection method provided in the embodiment of the application is completed.

It should be understood that the foregoing description is only an example given for better understanding of the premise that the technical solution of the present embodiment should be provided before implementing the present embodiment, and is not the only limitation of the present embodiment.

In addition, it should be noted that, in order to implement the multi-device application connection method provided in the embodiment of the present application, another requirement is that an application supporting application connection needs to be registered in advance to a corresponding server. Specifically, the precondition may be that the application developer registers the application supporting the application connection, such as a memo application, various audio and video applications, an application capable of viewing a file, and the like, to the corresponding server through the corresponding registration platform. In this way, after the super terminal is formed later, when a user uses an application registered as a connection application at one of the terminal devices (the transmitting end), other terminal devices in the super terminal receive an application connection request initiated by the terminal device, and when the user responds at the corresponding terminal device (the receiving end), the file checked and edited in the application at the transmitting end can be connected to the same application at the receiving end for displaying, so that the user can edit the file at the receiving end.

Furthermore, for different successive applications, the files that it can successively transmit are different. Therefore, when the application continues to be registered, the file types which can be checked and edited by the application can be registered and bound, for example, the office software such as WPS can be registered and bound with files in a plurality of formats such as PDF format, word format, PPT format, excel format and the like. When the subsequent application connection is carried out, when the file transmitted by connection is a word file, the office software of WPS can be directly started at the receiving end by judging and determining that the file is in a file format registered and bound with the office software of WPS, and the word file transmitted by the transmitting end is loaded in the software for display.

Based on the above premise, a scenario in which, when the user operates the application of memo in the device 10 shown in fig. 4, notes edited by the memo are seamlessly coordinated to the devices 20 and 30 constituting the super terminal will be described specifically with reference to the drawings.

Referring to fig. 11 (1), for example, after the user clicks the memo application control on the main interface of the device 10, the device 10 starts the memo application in response to the operation, and the interface of the device 10 switches from the main interface shown in fig. 11 (1) to the memo interface shown in fig. 11 (2) that displays all notes.

Referring to FIG. 11 (2), for example, if the user needs to create a new note, the user may click on control 10d-1 in the interface, such that device 10, in response to the action, creates a new note, switching the interface to the note interface shown in FIG. 12 (1).

Referring to fig. 12 (1), one or more controls are illustratively included in the note interface. These controls include, but are not limited to: controls for rewinding to the full note interface, controls 10d-2 for saving the current note content, controls 10d-3 for editing the note title, controls 10d-4 for editing the data content of the note, etc., which are not listed here, and are not limiting in this application.

Illustratively, if the user clicks the control 10d-3 on the note interface shown in fig. 12 (1), clicks the control 10d-4 on the control 10d-4 by editing the current note named "note 3", clicks the control 10d-4, and clicks the cursor on the control 10d-4 by editing the "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa", the note interface shown in fig. 12 (1) is updated to the note interface shown in fig. 12 (2), and at the same time, the control 10d-5 is displayed on the note interface while editing the content, and the creation time named "note 3" is displayed on the control 10d-5, such as "2023 year 2 month 6 day 16" shown in fig. 12 (2). 13".

In addition, it should be noted that, in actual operation, if note 3 is edited, such as adding or deleting some content, the time displayed in control 10d-5 will be updated to the latest update time of note 3.

With continued reference to fig. 4, since the device 10, the device 20 and the device 30 are the super terminals formed by the method of logging in the same user account and opening WLAN and bluetooth, when the user edits the note 3 in the memo application of the device 10 in the case that all the 3 terminal devices start the application connection function, the content of the note 3 is synchronized into the memos of the device 20 and the device 30 in the case that the device 20 and the device 30 in the super terminal have the same memo application, thereby realizing seamless cooperation operation between the devices in the super terminal.

For convenience of explanation, in this embodiment, a terminal device that performs application connection with the device 10 is taken as an example of the device 20, and a process of implementing memo connection by the device 10 and the device 20 is specifically explained based on the multi-device application connection method provided in this embodiment.

Specifically, when the user edits note 3 using the memo application in device 10, device 10 initiates an application continuation request for the memo application to device 20. It will be appreciated that in practice the device 10 will initiate the application connection request to each of the terminal devices that make up the super terminal.

Accordingly, device 20 receives an application continuation request for the memo application sent by device 10 and responds.

For example, in some implementations, for a case where a memo application is not installed in device 20, device 20 may directly pop-up the user in the interface to download the installed memo application in response to an application continuation request for the memo application sent by device 10, as shown in fig. 13.

Referring to fig. 13, for example, a control 20a-1 for agreeing to download the installation memo application and a control 20a-2 for refusing to download the installation memo application may be provided in the prompt window.

For example, in some implementations, when the user clicks on control 20a-1, the application marketplace for downloading applications installed in device 20 may be launched directly, where the memo application is automatically downloaded, and installed after the download is completed.

For example, in other implementations, device 20 may also obtain the download address of the memo application from device 10 after the user clicks control 20a-1, then download the memo application in the browser according to the download address, and install it after the download is completed.

In addition, it should be noted that, after the user installs the memo application according to the prompt, in some implementations, the triggering application connection may be directly performed, that is, the installed memo application is started. For the operation performed after the memo application is started, see the description after clicking the memo application carrying the small icon 20b-1, which will not be repeated here.

For example, in another implementation, after the user installs the memo application according to the prompt, the user may not automatically trigger the application connection, i.e. whether to select to connect with the device 10, which is determined by the user. For this case, after the memo application is installed, a small icon 20b-1 as described below may be displayed on the memo application icon. Specific implementation details may be found below, and are not described here again.

Illustratively, when the user clicks on control 20a-2, the prompt window displayed in the interface of device 20 is dismissed.

In addition, in order not to affect the normal use of the device 20 by the user, the prompt window may be set to automatically disappear from the interface of the device 20 when the operation of the control 20a-1 by the user is not received within a set time, for example, 10 s.

For example, in other implementations, for the case where the memo application is installed in the device 20, the device 20 may display a small icon, such as 20b-1 in fig. 14, on the memo application icon in response to the application continuation request for the memo application sent by the device 10.

It should be noted that, in practical application, in order to better remind the user that the memo in the device 20 can be currently operated to perform application connection, the small icon 20b-1 may be in a shrunken state, that is, in the process that the user edits the note through the memo application in the device 10, the small icon 20b-1 on the memo application icon in the device 20 may be shrunken all the time. Other terminal devices that make up the super terminal, such as device 30, can be understood to also display a small icon 20b-1 on the memo application icon, similar to that shown in fig. 14, if the memo application is installed; otherwise, if the device 30 does not install the memo application, a prompt window like that shown in fig. 13 is popped up.

For example, in other implementations, where the memo application is installed in the device 20, the device 20 may also display a small icon on the memo application icon in response to an application continuation request sent by the device 10 for the memo application, as still 20b-1 in fig. 14. However, in order to facilitate the user to quickly start the memo application in the device 20 in the case where the user is currently in the other operation interface, i.e., not in the main interface shown in fig. 14, the smart multi-window function may be opened by setting the control 10a-5 for entering the smart multi-window interface in the interface.

Illustratively, in some implementations, after the smart multi-window function is turned on, when the user views video in the device 20 at the video playback interface shown in FIG. 15 (1), sliding in the direction of the arrow from the right edge of the display screen of the device 20, the device 20 pulls out the sidebar 20b-2 shown in FIG. 15 (2) in response to this operational behavior.

It should be noted that, if a user adds a part of applications in the sidebar 20b-2 by dragging after opening the smart multi-window function, icons corresponding to the added applications are displayed in the sidebar 20b-2, and in fig. 15, (2) a memo application, an email application, and a gallery application are added to the sidebar.

In addition, it should be noted that, regarding the manner of adding an application in the sidebar, it is also possible to select an application installed by the device 20 in the smart multi-window interface as an application to be added to the sidebar.

With continued reference to fig. 15 (2), when the memo application icon is displayed in the pulled side bar 20b-1, a small icon 20b-1 is illustratively displayed on the memo application icon to prompt the user that the current triggering of the memo application may enable a connection with other terminal devices, such as device 10, for the current edited note in the memo application.

For example, in other implementations, where the memo application is installed in the device 20, the device 20 may also display a small icon on the memo application icon in response to an application continuation request sent by the device 10 for the memo application, as still 20b-1 in fig. 14. However, in the case where the user is currently in the other operation interface, i.e., not in the main interface shown in fig. 14, in order to facilitate the user to quickly start the memo application in the device 20, a hover-ball control operable by the user, such as the control 20b-3 shown in fig. 16, may also be displayed directly on the current interface.

It should be understood that the above-mentioned various response manners for the application connection request are merely examples listed for better understanding of the technical solution of the present embodiment, and are not the only limitation of the present embodiment.

Taking the scenario illustrated in fig. 14 as an example, when the user clicks on the memo application icon displaying the small icon 20b-1, the device 20 responds to the operation, and makes a response to the application connection request of the memo application, where the response is fed back to the device 10 based on the near field communication technology, i.e., the bluetooth channel established by pairing and/or through the wireless network. At this time, the multi-device application connection module in the device 10 performs the following operations according to the multi-device application connection method provided in the present embodiment: first, it is determined whether note 3 is the first transmission. Since note 3 is the first transmission, there is no data in device 20 that is related to note 3. In this case, based on the multi-device application connection method provided in this embodiment, the device 10 transmits the entire content related to the note 3 to the device 10 in a full-volume transmission manner, and the device 10 starts the memo application installed thereon to enter the note interface corresponding to the note 3.

It can be appreciated that in practical applications, if the data content transmitted by the device 10 is more, the note interface of the device 20 may not be able to immediately load the data content transmitted by the device 10, so a loading prompt box 20c-1 as shown in fig. 17 (1) may be displayed on the note interface of the device 20 to prompt the user that the note content is currently being loaded.

Illustratively, after the data is loaded successfully, the note interface of the device 20 is updated from that shown in fig. 17 (1) to that shown in fig. 17 (2), that is, the same note content as that of the note interface of the device 10 shown in fig. 12 (2) is displayed, so that seamless collaboration of editing the note 3 by the device 10 and the device 20 using the memo application is realized.

For example, in some implementations, after note 3 is seamlessly connected from device 10 to device 20, device 10 may automatically save note 3 and go back to the interface of all notes, at which point the interface of all notes in device 10 may be as shown in FIG. 18.

For example, in other implementations, after note 3 is seamlessly connected from device 10 to device 20, device 10 may continue to stay at the interface of note 3, i.e., the interface shown in (2) of fig. 12, in synchronization with device 20, i.e., the content of note 3 in device 10 is updated in synchronization as the user edits the content of note 3 at the note interface of device 20. It can be understood that, for this scenario, the device 20 is used as a transmitting end, and the device 10 is used as a receiving end, that is, the device 20 will transmit the updated note 3 to the device 10 by applying the connection method to the multiple devices provided in this embodiment in the process that the device 20 edits the note 3, and since only the difference content is transmitted, the speed is fast, the device 10 can realize synchronous display with the device 20, and the user experience is better.

For convenience of explanation, this embodiment takes the example that the user exits the memo application after continuing the note 3 edited by the memo application in the device 10 to the device 20. For such usage scenario, when the user edits the note by using the device 20, for example, after the original note content is added with "bb" as shown in fig. 19, the device 20 switches the initiating terminal for application connection, and at this time, the device 20 may initiate an application connection request for the memo application to each terminal device in the super terminal.

Taking the example of the user performing multi-device application connection with the device 10 using the device 10, after the device 20 initiates an application connection request for the memo application, a small icon for prompting the user that the current memo application can perform application connection is displayed on the memo application icon of the device 10, as shown in fig. 20 (1) by the small icon 10b-1.

Referring to fig. 20 (1), for example, after the user clicks the memo application icon in the main interface, the device 10 responds to the operation, and makes a response to the application connection request of the memo application, and the response is fed back to the device 20 based on the near field communication technology, that is, the bluetooth channel established by pairing and/or through the wireless network. At this time, the multi-device application connection module in the device 20 performs the following operations according to the multi-device application connection method provided in the present embodiment: first, it is determined whether note 3 is the first transmission. Since note 3 is not first transmitted, it is further determined whether the content of note 3 is updated, such as newly added content or uploaded content. Taking the content of note 3 shown in fig. 19 as an example, it can be determined that note 3 has been newly increased by "bbbb" as compared with the last transmission. In this case, based on the multi-device application connection method provided in the present embodiment, the device 20 transmits only the updated portion, such as "bbbb," and the updated time, location, etc. of the content to the device 10 in a delta transmission manner, and the device 10 starts the memo application installed thereon to enter the note interface corresponding to the note 3.

In addition, it can be understood that, since the device 20 performs data transmission in the delta transmission mode, other contents of the note 3 exist in the device 10, and the transmitted updated contents are smaller, so that the transmission speed is faster, so that the device 10 starts the memo application installed on the device, and after entering the note interface corresponding to the note 3, the latest contents of the note 3 can be directly loaded, that is, the interface shown in fig. 20 (1) can be directly switched to the note interface corresponding to the note 3 shown in fig. 20 (2), so that the user cannot perceive the process of data loading, and the user experience is greatly improved.

In addition, even if the data of the differential transmission is larger, compared with the existing direct full transmission mode, the time consumption for loading the data is shorter, and the waiting time of a user is shorter.

In addition, it should be further noted that, according to the multi-device application transmission method provided by the embodiment, when the multi-device application connection module in the terminal device serving as the transmitting end determines that there is no update in the data to be transmitted currently, the transmitting end may not transmit the data content of note 3, so that after the terminal device serving as the receiving end starts the memo application, the content of note 3 may be directly loaded from the local area.

It should be understood that the above description is only an example for better understanding of the technical solution of the present embodiment, and is not the only limitation of the present embodiment. For better understanding of the multi-device application connection method provided in the present application, the following description is made with reference to the implementation flows shown in fig. 21 to 23.

Referring to fig. 21, a flow of implementing the multi-device application connection method provided in this embodiment is exemplarily shown as applied to a first device, that is, a terminal device (may also be referred to as a transmitting end) that is responsible for transmitting data to be connected as an application connection request initiator. As shown in fig. 21, the multi-device application connection method applied to the first device specifically includes:

s101, in the process of editing a first file by using a first application registered as a connection application, an application connection request for the first application is sent to second equipment.

For specific details of registering the first application as a continuation application, reference may be made to the description of the above embodiments, which are not repeated here.

For example, the first device may be, for example, the device 10 in the foregoing embodiment, the first application may be, for example, a memo application in the foregoing embodiment, and the first file may be, for example, note 3 in the foregoing embodiment, and in the process that the first device edits the first file using the first application registered as a continuation application, implementation details of an application continuation request for the first application is sent to the second device, which will be specifically referred to the description of the foregoing embodiment and will not be repeated herein.

In addition, it should be noted that, since the technical solution provided in the present embodiment is continuous for multiple devices, when the first device is, for example, the device 10 in the above embodiment, the second device may be, for example, the device 20 and the device 30 that form the super terminal with the device 10 in the above embodiment.

Based on the description above for the super terminal and the premise of implementing multi-device application connection, before sending an application connection request for the first application to the second device, it is required to ensure that the first device and the second device start an application connection function, a bluetooth function, and a Wireless Local Area Network (WLAN) function (WIFI).

For a description of the starting application connection function, setting the first device and the second device to start the bluetooth function and the WLAN function may refer to the above embodiments, and will not be described herein.

S102, when the first file is not first transmitted in a continuous mode, after receiving an application continuous response of the second device for the application continuous request, transmitting differential data in the first file to the second device in a differential transmission mode.

Specifically, in this embodiment, whether the first file is transmitted continuously for the first time or not is determined by detecting whether a file data information table corresponding to the first file exists locally.

Accordingly, when detecting that the file data information table corresponding to the first file exists locally, determining that the first file is not subjected to continuous transmission for the first time. Otherwise, when the fact that the file data information table corresponding to the first file does not exist locally is detected, the first file is determined to be continuously transmitted for the first time.

The file data information table corresponding to the first file specifically carries identification information for identifying the uniqueness of the first file, file public basic information of the first file, a data atom set carrying data content in the first file, and file data feature codes generated based on data in the data atom set and describing file features. When the second device makes an application connection response, the first application installed on the second device can be started and the first file can be loaded based on the information.

As can be seen from the above description, after determining that the first file is transmitted for the first time, it may be determined that the file data information table corresponding to the first file does not exist in the first device, and the application connection between the second device and the first device needs to be based on the file data information table, so that after determining that the first file is transmitted for the first time, the first device needs to construct the file data information table corresponding to the first file first.

Because the first file has a relation with the first application, the second device determines the application to be pulled up according to the file data information table after responding to the application connection request, and then can load the correct file. Therefore, the file data information table corresponding to the first file needs to be constructed according to the related information of the first application and the first file.

For example, a relationship file unique identification indicating the first file and the first application is generated from the first application and the first file.

For example, file basic public information is generated according to information such as file name, path, file authority, creation and update time, hash value and the like of the first file, and a data atom set is generated according to actual file content in the first file, namely the data atom set carries all data of the first file.

Also for example, a file data signature for identifying data in the first file is generated from the data in the set of data atoms.

And finally, generating a file data information table according to the unique file identifier, the file basic public information, the data atom set and the file data feature codes.

For a better understanding of the file data information table, a specific form of the file data information table including the unique identification of the file, the common basic information of the file, the data atom set and the file data feature code is given below.

file: file data information table

{

"id": "File unique primary key id",

"uuid": "File unique identification",

"note_file_base": "File base public information"

{

"id": "File base public information primary key id",

"file_name": "File unique name",

"file_path": "File Path",

"file_size": "File size",

"authmode": "File read write rights",

"create_time": "File creation time",

"update_time": "file last update time",

"file_md5": "File md5 value"

}，

"atomic_dataset": data atom set, operation for controlling file data flow "

{

"id": "primary key id",

"file_header": "File stream header File",

"byte_code": "bytecode, binary file",

"FileStream": "create file stream and control the operation of file data stream",

"read_file": "read data in file",

"write_file": "write file byte data into file stream",

"byte_file": "File data content"

}，

"attribute_code": file data feature code, corresponding to a string of binary strings of a file data stream "

}

The unique file identifier is a hash function value generated by the current terminal equipment product serial number and the timestamp, for example, a 32-bit sequence generated by an md5 method has uniqueness.

Recorded in the data atom set is the content corresponding to the above-mentioned respective fields obtained based on the file to be transmitted, such as the hash value of the above-mentioned first file. A series of operations for controlling file data flow may be accomplished based on the data atom set.

It should be noted that, when the file to be transmitted, such as the first file, is first connected, the data atom set is a set of all data of the first file, which is intercepted from the first file in a full-size transmission manner, that is, all data of the first file carried in the data atom set.

Accordingly, when the file to be transmitted, such as the first file, is not first connected, the data atom set is a set of delta data intercepted from the first file in a delta transmission mode, that is, for the first file which is not first connected, delta data transmitted in a delta transmission mode is actually an atomic data set in which delta data is recorded.

The file data feature code is obtained by scanning the whole file content, namely all data in a byte_file field, then scanning the information such as the unique name of the file corresponding to the file_name field, the file path corresponding to the file_path field, the last update time of the file corresponding to the update_time field and the like in the file basic public information, performing hash calculation by using a set algorithm such as a secure hash algorithm 1 (Secure Hash Algorithm 1, SHA 1), further obtaining a hash function value, and finally taking the hash function value as the file data feature code. .

Correspondingly, after the file data information table corresponding to the first file is built, the first device can adopt a full transmission mode to transmit the file data information table to the second device after receiving an application connection response of the second device for the application connection request.

In addition, it can be understood that, when the first file is not transmitted continuously for the first time, the user may edit the first file in the first device or may not edit the first file in the first device, so the first device may determine whether there is a difference between the content of the first file to be transmitted continuously currently and the content of the first file transmitted to the second device before transmitting the delta data in the first file to the second device by adopting the delta transmission method. When the difference exists, the difference data in the first file is transmitted to the second device by adopting a difference transmission mode.

The manner of determining whether there is a difference between the content of the first file currently to be transmitted successively and the content of the first file previously transmitted to the second device may be as follows:

(1) And randomly scanning the first file to generate a temporary data atom set.

That is, the data content in the first file, such as the data content in the control 10d-3, the file name in the control 10d-3, the time information in the control 10d-5, etc. in the interface corresponding to the note 3 in the above embodiment, is scanned, and the data related to the first file is scanned, so as to generate a temporary spare data atom set, that is, a temporary data atom set.

The fields included in the temporary data atom set are the same as those in the generated data atom set when the file data information table corresponding to the first file is generated for the first time as described above, and are not described herein.

(2) And generating a temporary file data feature code according to the data in the temporary data atom set.

For example, in some implementations, according to a generating manner of a file data feature code recorded in a file data information table, data with the same position and the same length in a "byte_file" field in a temporary data atom set may be intercepted, and then, in combination with information such as a file unique name corresponding to a "file_name" field, a file path corresponding to a "file_path" field, and a last update time of a file corresponding to an "update_time" field in file basic public information, the same algorithm, such as a secure hash algorithm 1 (Secure Hash Algorithm, sha1), may be used to generate a hash function value, and the hash function value may be used as the temporary file data feature code.

For example, in other implementations, according to the generation mode of the file data feature code recorded in the file data information table, all data in the "byte_file" field may be intercepted, and then, in combination with the information of the file unique name corresponding to the "file_name" field, the file path corresponding to the "file_path" field, the last update time of the file corresponding to the "update_time" field in the file base public information, the same algorithm, such as the secure hash algorithm 1 (Secure Hash Algorithm, sha1), may be used to generate a hash function value, and the hash function value may be used as the temporary file data feature code.

Accordingly, when the temporary file data feature code is different from the file data feature code recorded in the file data information table, the differential transmission mode is adopted to transmit differential data in the first file to the second device. Otherwise, when the temporary file data feature code is the same as the file data feature code recorded in the file data information table, that is, the first file is not edited currently, the content is added or deleted, that is, the first file currently viewed in the first device is the same as the content of the first file previously transmitted to the second device, so that the first device does not need to transmit the data of the first file to the second device.

In addition, it should be noted that, in some implementations, in order to avoid that the first device continuously performs data transmission with the second device, and reduce power consumption and resource occupation of the device, the first device may use a differential transmission mode to transmit differential data in the first file to the second device, or use a full transmission mode to transmit the file data information table to the second device, and then may set the first device to save the first file, and exit an interface capable of editing the first file, such as returning to the interface shown in fig. 18 in the above embodiment.

In addition, it should be noted that, in the actual operation, any one of the first devices may also be used as the second device, that is, the first device may be used as the initiator of the application connection request to send the first file, or may be used as the responder of the application connection request to receive the first file. Therefore, when the first device transmits the first file (the differential transmission mode or the full transmission mode) to the second device, the first device is switched to the background operation, and after the first device exits the first application, that is, when the first application is not in the foreground operation, if the first device receives the application connection request for the first application sent by the second device, at this time, the first device serves as a receiving end of the first file, and an application connection identifier may be added to a first application icon corresponding to the first application installed in the first device, such as a small icon 10b-1 shown in (1) in fig. 20.

Accordingly, after the user clicks the first application icon added with the application connection identifier, the first device responds to the operation of the first application icon added with the application connection identifier, and switches the first application to the foreground operation again, for example, switches the first application from the background to the foreground, or restarts the first application, loads a local first file, and the second device adopts the differential data of the first file transmitted in the differential transmission mode.

It can be understood that if the second device does not edit the first file, that is, if there is no delta data, the first device only needs to load the local first file.

In addition, after the first device finishes the operation of loading the first file, the file data information table can be updated according to the difference data transmitted by the second device. Therefore, when the application connection is carried out later, whether data need to be transmitted or not can be accurately judged.

It will be appreciated that when the delta data of the first file is transmitted by the delta transmission method, the first device or the second device may not only transmit the specific modified content of the first file, but also refer to editing time, that is, the last update time of the first file, etc. Therefore, the delta data in this embodiment is the total difference content between the first file currently to be transmitted and the first file before editing.

In addition, it should be noted that, in some implementations, the display time of the application connection identifier may also be set. In this way, the first device and the second device are allowed to carry out application connection within the set time, if the user does not make application connection response to the application connection request in the first device within the set time, namely, the first application icon carrying the application connection identifier is triggered, the application connection identifier is canceled, so that the first device can be prevented from being in a state of waiting for the user to make application response all the time, and the power consumption of the first device can be reduced.

In addition, it should be noted that in some implementations, the first device may be further configured to transmit the delta data in the first file to the second device by adopting a delta transmission manner, or to continue to stay on the interface where the first file can be edited after transmitting the file data information table to the second device by adopting a full-scale transmission manner. In this way, the first device and the second device can continue to perform application connection, so that the content of the first file displayed in the interface capable of editing the first file in the first device is synchronous with the content displayed in the interface capable of editing the first file in the second device, and seamless cooperative processing of the first application is realized between the first device and the second device.

In addition, for details not shown in the present embodiment in the multi-device application connection process, reference may be made to the above embodiment, and details are not repeated here.

Referring to fig. 22, a flow of implementing the multi-device application connection method provided in this embodiment is exemplarily shown as applied to a first device, that is, a terminal device (may also be referred to as a transmitting end) that is responsible for transmitting data to be connected as an application connection request initiator. As shown in fig. 22, the multi-device application connection method applied to the first device specifically includes:

S201, when receiving an application connection request for a first application sent by a first device under the condition that the first application is installed by a second device, adding an application connection identifier on a first application icon corresponding to the first application.

For example, taking the second device as an example of the device 20 described in the above embodiment, the first application is taken as an example of the memo application, and the application connection identifier added on the first application icon corresponding to the first application may be the small icon 20b-1 added on the memo application icon described in the above embodiment.

For a description of the application continuation icon, reference is made to the description section above for the small icon 20b-1, and no further description is given here.

S202, in response to the operation of the first application icon added with the application connection identifier, an application connection response made for the application connection request is sent to the first device, and the first application is switched to be operated in the foreground.

In connection with the above description of the embodiments, the operation described herein is responsive to the first application icon to which the application continuation identifier is added, for example, a memo application icon to which the small icon 20b-1 is added is clicked by the user in the device 20.

In addition, it should be noted that, in the actual application, there may be a case where the first application, such as the memo application, is already started, but is running in the background, and the front interface does not display the interface corresponding to the memo application, or the memo application is not started. Therefore, the first application is switched to the foreground operation, and the first application is essentially switched to the foreground operation in the case of being operated in the background, and the first application is started to be operated in the foreground in the case of not being operated.

S203, after receiving the file data information table transmitted by the first device in a full-volume transmission mode, analyzing all data of the first file from the data atom set in the file data information table, loading and displaying the data, and storing the file data information table locally.

For example, in the case where the data of the first file is parsed from the file data information table, as described in the foregoing embodiment, it is known that the first file is continuously transmitted for the first time, and thus, all the data of the first file is continuously transmitted, so that in the loading process, a situation of waiting for loading may occur, and the user interface of the second device may occur as shown in (1) in fig. 17.

Accordingly, when all the data of the first file is parsed from the file data information table and loaded successfully, the interface is switched to the case shown in fig. 17 (2).

For the interface changes involved in the transmission and loading process of the first file for the first subsequent transmission, refer to the above embodiment, and are not described herein again.

In addition, since the second device receives the first file for the first time, the second device does not have a file data information table corresponding to the first file locally, so that the second device can save the file data information table transmitted by the first device, so that when the subsequent second device serves as an initiator of an application connection request, that is, a transmitting end for transmitting the first file, whether delta data needs to be transmitted can be determined according to the file data feature code recorded in the file data information table and the newly generated temporary file data feature code.

S204, after receiving the differential data of the first file transmitted by the first device in the differential transmission mode, loading the differential data, displaying the locally stored first file, and updating the locally stored file data information table according to the differential data.

For example, in the case of the received delta data of the first file, since the first file of one version is already stored locally, after the second device switches the first application to the foreground operation, the second device directly loads the part without change to obtain the first file locally, and loads the delta data transmitted by the first device to fuse, so that the updated first file in the first device can be displayed.

In addition, in order to facilitate the subsequent second device to be used as the initiator of the application connection request, that is, when the sender of the first file is sent, whether the differential data needs to be transmitted or not can be determined according to the file data feature code recorded in the file data information table and the newly generated temporary file data feature code, after the differential data transmitted by the first device is received each time, the second device can update the file data information table once according to the differential data after loading and displaying, for example, update the last update time of the file corresponding to the "update_time" field in the file data information table according to the update time corresponding to the differential data, update the file data content corresponding to the "byte_file" field according to the finally loaded and displayed content, update the updated file data feature code corresponding to the "attribute_code" field, and the like.

In addition, in some implementations, the second device may be further configured to cancel the application connection identifier on the first application icon when the operation on the first application icon to which the application connection identifier is added is not received within a set time after receiving the application connection request for the first application sent by the first device.

Specifically, after the application connection identifier is cancelled, the second device cannot connect with the first device for the first application.

In addition, it should be noted that, in the case that the second device does not install the first application, when receiving an application connection request for the first application sent by the first device, the user may be prompted to install the first application. For implementation details of the second device prompting the user to install the first application, reference may be made to the description part of fig. 13, which is not repeated here.

Since the multi-device application connection method applied to the second device is performed in cooperation with the first device, the details not described in detail in this embodiment may be referred to the above embodiment for implementing the multi-device application connection method for the first device, and the details corresponding to fig. 23 described below are not repeated here.

In order to better understand the multi-device application connection method provided in the present application, taking the application connection in the above example as an example for a memo application, in the case that two terminal devices performing application connection install a memo application capable of performing application connection, a specific description is given of a multi-device application connection method implemented by a transmitting end and a receiving end with reference to fig. 23.

Referring to fig. 23, for a transmitting end, a method for implementing multi-device application connection specifically includes:

s301, whether a file data information table exists in the note to be transmitted.

Specifically, when the user operates the note to be transmitted at the transmitting end, such as note 3 in the above embodiment, the application connection identifier is displayed on the memo application icon on the receiving end, such as the small icon 20b-1 displayed on the memo application icon in the above embodiment of the device 20. At this time, the surface transmitting terminal initiates an application connection request to other terminal devices (as receiving terminals) in the super terminal.

For example, when the user operates the receiving end to make an application connection response to the application connection request, as described in the above embodiment, after clicking the memo application icon in the device 20, as an initiator of the application connection request, the sending section performs two logic judgments, to judge whether the note to be transmitted next time is first connected, and further judge whether the content of the note to be transmitted next time is the same as the content of the note transmitted last time to the receiving end making the application connection response when the note is not first connected.

As for the first determination, it is known from the description of the above embodiment that specifically, it is determined whether or not there is a file data information table corresponding to the note to be transmitted locally. Details of the file data information table are described in the above embodiments, and are not repeated here.

Correspondingly, if the file data information table does not exist locally through judgment, the first connection of the connection task aiming at the note to be transmitted is indicated. For this case, a full-scale transmission method is required to transmit notes to be transmitted.

Specifically, when the full-scale transmission mode is adopted to transmit the note to be transmitted, a file data information table is required to be created for the note to be transmitted, and then the full-scale transmission is performed on the note content based on the file data information table, that is, step S302 and step S303 are executed.

The creation of the file data information table and the manner of transmitting the note content based on the file data information table are described in detail in the above embodiments, and are not repeated here.

In addition, if the local file data information table is determined through judgment, the connection task for the note to be transmitted is not first connection. For this case, it is necessary to transmit the note to be transmitted by differential transmission.

Specifically, when the note to be transmitted is transmitted in the delta transmission mode, it is further determined whether the content of the note to be transmitted next time is the same as the content of the note transmitted last time to the receiving end that makes the application connection response, that is, the second logic judgment is performed. For the implementation of the second logic determination, see step S304 and step S305 for details.

S302, creating a file data information table for the note to be transmitted.

S303, transmitting the total amount of the note content.

S304, randomly scanning files to be transmitted, generating a temporary data atom set, and generating temporary file data feature codes according to data in the temporary data atom set.

For the generation of the temporary file data feature code, reference may be made to the above embodiment, and details are not repeated here.

S305, whether the temporary file data feature code is the same as the file data feature code recorded in the file data information table.

Specifically, if the temporary file data feature code is not identical to the file data feature code recorded in the file data information table, step S206 is performed. Otherwise, step S307 is performed.

S306, note content delta transmission.

S307, no note content is transmitted.

With continued reference to fig. 23, for the receiving end, a method for implementing multi-device application connection specifically includes:

S401, pulling up a memo application through a file unique identifier of a transmitting end, loading the note content of full transmission after the memo application is pulled up, and copying a file data information table.

As can be seen from the description of the above embodiments, for the scenario that the note to be transmitted is first connected, when the sending end performs multi-device application connection with the receiving end, the sending end transmits the file data information table carrying the entire data content of the note to be transmitted to the receiving end in a full-scale transmission manner. In the file data information table, identification information capable of identifying the uniqueness of the file is recorded in the "uuid" field, and the identification information is generated based on the relation between the note to be transmitted and the application editing the note, such as a memo application, so that after the file data information table is received, it can be determined which application needs to be pulled up, i.e., which application is switched to the foreground operation, according to the identification information recorded in the "uuid" field.

Therefore, when the identification information recorded in the "uuid" field in the file data information table indicates the memo application, the receiving end can directly switch the memo application to the foreground operation.

In addition, as can be seen from the description of the file data information table in the above embodiment, the file data information table further includes a data atom set, and the "byte_file" field of the data atom set corresponds to the specific content of the note to be transmitted. Therefore, after the receiving end pulls up the memo application, by analyzing the corresponding content in the "byte_file" field, all the content aiming at the note to be transmitted, which is transmitted by the transmitting end, can be loaded and displayed in the current interface.

In addition, since the receiving end receives the note to be transmitted for the first time, the receiving end does not have a file data information table corresponding to the note to be transmitted locally, so that the receiving end can save the file data information table transmitted by the transmitting section, and the subsequent transmitting end can determine whether delta data need to be transmitted according to the file data feature code recorded in the file data information table and the newly generated temporary file data feature code when the subsequent transmitting end is used as an initiator of an application connection request, namely, the transmitting end for transmitting the note to be transmitted.

S402, pulling up a memo application through a file unique identifier of a transmitting end, and loading local note content and note content transmitted in a delta mode after the memo application is pulled up.

Because the application is continued, the sending end updates the content of the note to be transmitted, and the delta data in the note is transmitted to the receiving end in a delta transmission mode, after the memo application is pulled up, the receiving end loads the part of delta data and local note content, so that the note to be transmitted, which is managed by the sending end and has the delta data, is obtained through fusion.

S403, pulling up the memo application through the unique file identifier of the transmitting end, and loading local note content after the memo application is pulled up.

Because the application is continued, the sending end does not update the content of the note to be transmitted, namely, the note content is not transmitted to the receiving end, and therefore, the receiving end directly loads the local note content after pulling up the memo application.

S404, updating the file data table.

In this way, when the subsequent sending end is used as the initiator of the application connection request, that is, the sending end of the note to be transmitted, it can determine whether the delta data needs to be transmitted according to the file data feature code recorded in the file data information table and the newly generated temporary file data feature code.

In order to more intuitively see the difference between the multi-device application connection method provided by the embodiment of the present application and the existing application connection time, the application to be subjected to application connection is taken as a memo application as an example, and referring to table 1, the difference between the multi-device application connection method provided by the embodiment of the present application and the existing application connection time is described.

Table 1 comparison of application succession time consumption

As can be seen from table 1, in the current application connection scheme, the notes transmitted by each application connection are transmitted in full quantity, so that the time consumption is long, which results in long waiting time of the user and poor user experience. The application connection performed by using the multi-device application connection method provided by the embodiment of the application uses the full-quantity transmission mode to transmit the notes only when the application is connected for the first time, and uses the differential transmission mode in the subsequent connection scene, namely in the non-first connection scene, so that the connection time consumption is greatly reduced, the user only waits for a short time when the application is connected for the first time or the differential transmission content is larger, the user does not need to wait for loading each time, and the user experience is greatly improved.

Therefore, the sending end can select a proper transmission mode according to actual conditions to transmit the note to be transmitted, the receiving end can select to locally load part of data or all data or only acquire data to load from the sending end, so that the note to be transmitted which is connected for the first time can be received and displayed by the receiving end, the time consumption of data transmission can be reduced in the subsequent process which is not connected for the first time, and the success rate of multi-equipment application connection can be improved.

Furthermore, it is understood that the terminal device, in order to implement the above-mentioned functions, comprises corresponding hardware and/or software modules for performing the respective functions. The steps of an algorithm for each example described in connection with the embodiments disclosed herein may be embodied in hardware or a combination of hardware and computer software. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. Those skilled in the art may implement the described functionality using different approaches for each particular application in conjunction with the embodiments, but such implementation is not to be considered as outside the scope of this application.

In addition, it should be noted that, in an actual application scenario, the multi-device application connection method provided in the foregoing embodiments implemented by the terminal device may also be executed by a chip system included in the terminal device, where the chip system may include a processor. The chip system may be coupled to a memory such that the chip system, when running, invokes a computer program stored in the memory, implementing the steps performed by the terminal device. The processor in the chip system can be an application processor or a non-application processor.

In addition, the embodiment of the application further provides a computer readable storage medium, and the computer storage medium stores computer instructions, which when executed on the terminal device, cause the terminal device to execute the related method steps to implement the multi-device application connection method in the embodiment.

In addition, the embodiment of the application further provides a computer program product, when the computer program product runs on the terminal equipment, the terminal equipment is caused to execute the related steps, so as to realize the multi-equipment application connection method in the embodiment.

In addition, embodiments of the present application also provide a chip (which may also be a component or module) that may include one or more processing circuits and one or more transceiver pins; the receiving pin and the processing circuit communicate with each other through an internal connection path, and the processing circuit executes the related method steps to implement the multi-device application connection method in the above embodiment, so as to control the receiving pin to receive signals and control the sending pin to send signals.

In addition, as can be seen from the foregoing description, the terminal device, the computer-readable storage medium, the computer program product, or the chip provided in the embodiments of the present application are used to perform the corresponding methods provided above, so that the advantages achieved by the method can be referred to the advantages in the corresponding methods provided above, which are not repeated herein.

The above embodiments are merely for illustrating the technical solution of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A multi-device application connectivity method, wherein a first device is applied, the method comprising:

in the process of editing a first file by using a first application registered as a continuing application, sending an application continuing request aiming at the first application to second equipment;

detecting whether a file data information table corresponding to the first file exists locally or not, wherein information in the file data information table is used for indicating the second equipment to start a first application installed on the second equipment after the second equipment makes the application connection response, and loading the first file; wherein the file data information table comprises file data feature codes;

when a file data information table corresponding to the first file exists, determining that the first file is not subjected to continuous transmission for the first time;

when the first file is not transmitted continuously for the first time, after receiving an application continuous response of the second equipment for the application continuous request, randomly scanning the first file to generate a temporary data atom set;

generating a temporary file data feature code according to the data in the temporary data atom set;

when the temporary file data feature code is different from the file data feature code recorded in the file data information table, transmitting the difference data in the first file to the second device in a difference transmission mode; when the first file is not transmitted continuously for the first time, the time for transmitting the first file in a differential transmission mode is shorter than the time for transmitting the first file in a full transmission mode;

When the temporary file data feature code is the same as the file data feature code recorded in the file data information table, not transmitting the data of the first file to the second device;

when a file data information table corresponding to the first file does not exist, determining that the first file is continuously transmitted for the first time;

constructing a file data information table corresponding to the first file according to the first application and the first file, wherein the file data information table carries all data of the first file;

after receiving an application continuing response made by the second equipment for the application continuing request, transmitting the file data information table to the second equipment by adopting a full transmission mode;

the first device and the second device have complete editing, storing and transmitting functions for the first file.

2. The method of claim 1, wherein constructing the file data information table corresponding to the first file from the first application and the first file comprises:

generating a file unique identifier according to the first application and the first file, wherein the file unique identifier indicates the relation between the first file and the first application;

Generating file basic public information and a data atom set according to the first file, wherein the data atom set carries all data of the first file;

generating a file data feature code according to the data in the data atom set, wherein the file data feature code is used for identifying the data in the first file;

and generating the file data information table according to the unique file identifier, the file basic public information, the data atom set and the file data feature codes.

3. The method according to claim 1 or 2, characterized in that the method further comprises:

and after the differential data in the first file is transmitted to the second device by adopting a differential transmission mode or the file data information table is transmitted to the second device by adopting a full transmission mode, the first file is saved, and an interface capable of editing the first file is exited.

4. The method of claim 3, wherein after the exiting the interface where the first file can be edited, the method further comprises:

when receiving an application connection request for the first application sent by the second device when the first application is not in a foreground operation, adding an application connection identifier on a first application icon corresponding to the first application;

And responding to the operation of the first application icon added with the application connection identifier, switching the first application into a foreground operation, loading the local first file, and transmitting the differential data of the first file by the second equipment in a differential transmission mode.

5. The method according to claim 4, wherein the method further comprises:

and updating the file data information table according to the difference data.

6. The method of claim 4, wherein after adding an application connection identifier to the first application icon corresponding to the first application, the method further comprises:

when the operation of the first application icon added with the application continuing identification is not received within a set time, canceling the application continuing identification on the first application icon;

after the application connection identifier is canceled, the first device and the second device cannot conduct application connection on the first application.

7. The method according to claim 1 or 2, characterized in that the method further comprises:

after the differential transmission mode is adopted to transmit differential data in the first file to the second device, or the full transmission mode is adopted to transmit the file data information table to the second device, the file data information table is continuously remained on an interface capable of editing the first file;

And the content of the first file displayed in the interface of the first file is kept synchronous with the content of the first file in the second device.

8. The method according to claim 1 or 2, characterized in that before said sending an application connectivity request for said first application to a second device, the method further comprises:

ensuring that the first device and the second device have opened an application connection function, a bluetooth function, and a wireless local area network function.

9. A multi-device application connectivity method, wherein a second device is applied, the method comprising:

under the condition that the second device installs a first application, when receiving an application connection request for the first application sent by the first device, adding an application connection identifier on a first application icon corresponding to the first application;

responding to the operation of the first application icon added with the application continuing identification, sending an application continuing response made for the application continuing request to the first equipment, and switching the first application to be operated in the foreground;

after receiving a file data information table transmitted by the first equipment in a full transmission mode, analyzing all data of a first file from a data atom set in the file data information table, loading and displaying the data, and storing the file data information table to a local place; the file data information table transmitted by the first device in a full transmission mode is as follows: when the first device detects that a file data information table corresponding to the first file does not exist locally, the first device constructs the file data information table corresponding to the first file according to the first application and the first file, and the file data information table carries all data of the first file;

After receiving the differential data of the first file transmitted by the first equipment in a differential transmission mode, loading the differential data, displaying the first file stored locally, and updating the file data information table stored locally according to the differential data; the difference data of the first file transmitted by the first device in the difference transmission mode is: when the first device detects that a file data information table corresponding to the first file exists locally, after receiving an application continuing response of the second device for the application continuing request, when a file data feature code recorded in the file data information table is different from a temporary file data feature code generated according to the first file, the first device adopts differential data of the first file transmitted in a differential transmission mode;

the temporary file data feature code generated according to the first file specifically includes:

randomly scanning the first file to generate a temporary data atom set;

and generating the temporary file data feature codes according to the data in the temporary data atom set.

10. The method according to claim 9, wherein the method further comprises:

after receiving an application connection request for a first application sent by a first device, canceling the application connection identifier on the first application icon when an operation of the first application icon added with the application connection identifier is not received within a set time;

after the application connection identifier is canceled, the second device cannot connect with the first device for the first application.

11. The method according to claim 9, wherein the method further comprises:

and under the condition that the second equipment does not install the first application, prompting a user to install the first application when receiving an application connection request for the first application, which is sent by the first equipment.

12. A terminal device, characterized in that the terminal device comprises: a memory and a processor, the memory and the processor coupled; the memory stores program instructions that, when executed by the processor, cause the terminal device to perform the multi-device application continuation method of any one of claims 1 to 8 or the multi-device application continuation method of any one of claims 9 to 11.

13. A computer readable storage medium comprising a computer program which, when run on a terminal device, causes the terminal device to perform the multi-device application splicing method of any of claims 1 to 8 or the multi-device application splicing method of any of claims 9 to 11.