WO2024067225A1 - 应用接续方法和终端设备 - Google Patents

应用接续方法和终端设备 Download PDF

Info

Publication number
WO2024067225A1
WO2024067225A1 PCT/CN2023/119544 CN2023119544W WO2024067225A1 WO 2024067225 A1 WO2024067225 A1 WO 2024067225A1 CN 2023119544 W CN2023119544 W CN 2023119544W WO 2024067225 A1 WO2024067225 A1 WO 2024067225A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
connection
terminal device
matching relationship
continuation
Prior art date
Application number
PCT/CN2023/119544
Other languages
English (en)
French (fr)
Inventor
许嘉
张伟
王鑫鹏
Original Assignee
荣耀终端有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 荣耀终端有限公司 filed Critical 荣耀终端有限公司
Publication of WO2024067225A1 publication Critical patent/WO2024067225A1/zh

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
    • G06F3/04817—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance using icons
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication

Definitions

  • the present application relates to the field of terminal technology, and in particular to an application connection method and a terminal device.
  • terminal devices are divided into source devices and peer devices.
  • the source device is the sending device
  • the peer device is the receiving device.
  • the applications on the source device and the peer device can be connected by the user triggering the connection conditions.
  • the source device is a computer
  • the peer device is a mobile phone.
  • the user logs in to the same account on the computer and the mobile phone, and the computer and the mobile phone are in the same local area network. If the user plays a video on the video player software on the computer, the video player software on the user's mobile phone can play the video synchronously. If the user is editing text on the computer, the text being edited can be displayed synchronously on the user's mobile phone.
  • the content of the application on the source device may be connected to an application with an unreliable trust source on the peer device, resulting in user information leakage.
  • a mobile phone connects the content of a memo to a memo on a tablet. If the memo on the tablet is a fake application, the information edited by the user will be stolen by the fake application. Therefore, it is currently necessary to provide an application connection method that can avoid connecting the content of an application to an application with an unreliable trust source and improve the security of application connection.
  • the embodiments of the present application provide an application connection method and a terminal device, which can avoid connecting the content of an application to an application with an unreliable trust source, improve the security of the application connection, and thus improve the user experience.
  • an application continuation method is provided, which is applied to a system including a first terminal device, a second terminal device, and a cloud server, wherein a user logs in to the same account on the first terminal device and the second terminal device, and the first terminal device and the second terminal device are in the same local area network, the method comprising: the second terminal device receives a broadcast continuation notification from the first terminal device, the broadcast continuation notification being used to request that a first continuation application of the first terminal device be continuation to the second terminal device; the second terminal device determines a second continuation application based on the broadcast continuation notification, and performs legitimacy authentication and matching relationship verification on the second continuation application to obtain a legitimacy authentication result and a matching relationship verification result; when the legitimacy authentication result is that the legitimacy authentication passes, and the matching relationship verification result is that the matching relationship verification passes, the second terminal device displays a connection contact of the second continuation application.
  • the application continuation method of the embodiment of the present application performs legitimacy authentication and matching relationship verification on the second continuation application on the second terminal device, and when the legitimacy authentication and matching relationship verification are passed, displays the continuation contact of the second continuation application on the second terminal device, thereby avoiding connecting the content of the application to an application with an unreliable trust source, improving the security of the application continuation, and thus improving the user experience.
  • the above-mentioned broadcast continuation notification includes: an application identifier APPID of the first continuation application and a continuation policy; wherein the continuation policy includes at least one of the following: a continuation status identifier, a package name or process name of at least one target continuation application, a device type of at least one target continuation application, an application market listing policy of at least one target continuation application, and a minimum version supporting the continuation; at least one target continuation application includes a second continuation application.
  • connection status identifier can be a flag bit used to identify the connection policy status. For example, a flag bit of 0 can indicate that the connection is not supported, a flag bit of 1 can indicate application connection, and a flag bit of 3 can indicate browser connection. It is understood that the specific value of the flag bit can be set arbitrarily as long as it can distinguish different states, and the embodiment of the present application does not make specific limitations.
  • the continuation policy includes the package name of the first continuation application on the Android platform; if the first continuation application is an application on the Windows platform, the continuation policy includes the continuable process name of the first continuation application on the Windows platform.
  • the application market listing strategy can be any of the following: not listed, overseas application market 1, domestic application market 1, domestic application market 2, overseas application market 2.
  • the minimum version of the application that supports the continuation can be represented by the minimum version number of the application that supports the continuation, which is used to represent the minimum version when the second continuation application can be continued.
  • the above-mentioned second terminal device determines the second connection application based on the broadcast connection notification, including: the second terminal device determines, based on the device type of at least one target connection application, an application with the same device type as the second terminal device in at least one target connection application as the second connection application.
  • the above-mentioned legitimacy authentication of the second succession application includes: the second terminal device sends a legitimacy authentication request to the cloud server, and the legitimacy authentication request carries the APPID of the second succession application; the second terminal device receives cloud identification information of the second succession application from the cloud server, and the cloud identification information includes the package name and/or signature of the second succession application stored in the cloud server; the second terminal device compares the cloud identification information with the local identification information of the second succession application to obtain a legitimacy authentication result, and the local identification information is the package name and/or signature of the second succession application stored locally on the second terminal device.
  • the above-mentioned matching relationship verification of the second connection application includes: the second terminal device sends a matching relationship query request to the cloud server, and the matching relationship query request carries the APPID of the second connection application; the second terminal device receives a first matching relationship from the cloud server, and the first matching relationship is used to represent at least one application that can be connected with the second connection application; the second terminal device determines whether at least one application includes the first connection application based on the first matching relationship, and obtains a matching relationship verification result.
  • the above-mentioned matching relationship verification of the second connection application includes: the second terminal device sends a matching relationship query request to the cloud server, and the matching relationship query request carries the APPID of the first connection application; the second terminal device receives a first matching relationship from the cloud server, and the first matching relationship is used to represent at least one application that can be connected with the first connection application; the second terminal device determines whether at least one application includes the second connection application based on the first matching relationship, and obtains a matching relationship verification result.
  • the above-mentioned matching relationship verification of the second succession application includes: the second terminal device obtains a second matching relationship, the second matching relationship is used to represent at least one application that can be connected with the second succession application, and the second matching relationship is pre-stored locally by the second terminal device when installing the second succession application; the second terminal device determines whether at least one application includes the first succession application based on the second matching relationship, and obtains a matching relationship verification result.
  • the application developer has pre-defined the matching relationship between the second continuation application and other applications (i.e., the second matching relationship) in the installation package of the second continuation application.
  • the second terminal device installs the second continuation application, it parses the installation package of the second continuation application, obtains the second matching relationship, and stores the second matching relationship in the system registration manager.
  • At least one application that has a matching relationship with the second continuation application includes the first continuation application, it is considered that there is a matching relationship between the first continuation application and the second continuation application, and the matching relationship verification passes; otherwise, it is considered that there is no matching relationship between the first continuation application and the second continuation application, and the matching relationship verification fails.
  • the above method also includes: the second terminal device sends a connection data request message to the first terminal device in response to a user's click operation on the connection contact; the second terminal device receives the connection data from the first terminal device and displays the connection data.
  • a terminal device which is used to execute the method in any possible implementation of the first aspect.
  • the terminal device includes a module for executing the method in any possible implementation of the first aspect.
  • the terminal device may include a module that executes the methods/operations/steps/actions described in each of the above aspects.
  • the module may be a hardware circuit, software, or a combination of hardware circuit and software.
  • the terminal device is a communication chip, which may include an input circuit or interface for sending information or data, and an output circuit or interface for receiving information or data.
  • the terminal device is a communication device, which may include a transmitter for sending information or data, and a receiver for receiving information or data.
  • a terminal device comprising a processor and a memory.
  • the processor is used to read instructions stored in the memory, and can receive signals through a receiver and transmit signals through a transmitter to execute the method in any possible implementation of the first aspect.
  • processors there are one or more processors and one or more memories.
  • the memory may be integrated with the processor, or the memory may be provided separately from the processor.
  • the memory can be a non-transitory memory, such as a read-only memory (ROM), which can be integrated with the processor on the same chip or can be separately set on different chips.
  • ROM read-only memory
  • the embodiments of the present application do not limit the type of memory and the setting method of the memory and the processor.
  • the relevant data interaction process such as sending the connection data request information
  • receiving the capability information can be a process of receiving the input capability information from the processor.
  • the processed output data can be output to the transmitter, and the input data received by the processor can come from the receiver.
  • the transmitter and the receiver can be collectively referred to as a transceiver.
  • the terminal device in the third aspect may be a chip, and the processor may be implemented by hardware or by When implemented through software, the processor may be a logic circuit, an integrated circuit, etc. When implemented through hardware, the processor may be a general-purpose processor implemented by reading software codes stored in a memory, and the memory may be integrated in the processor or located outside the processor and exist independently.
  • a computer program product comprising: a computer program (also referred to as code, or instruction), which, when executed, enables a computer to execute a method in any possible implementation of the first aspect.
  • a computer program also referred to as code, or instruction
  • a computer-readable storage medium which stores a computer program (also referred to as code or instruction), which, when executed on a computer, enables the computer to execute a method in any possible implementation of the first aspect.
  • a computer program also referred to as code or instruction
  • FIG1 is a schematic diagram of an application scenario of an embodiment of the present application.
  • FIG2 is a schematic diagram of the structure of a terminal device provided in an embodiment of the present application.
  • FIG3 is a schematic diagram of the software structure of a terminal device provided in an embodiment of the present application.
  • FIG4 is a schematic diagram of another software structure of a terminal device provided in an embodiment of the present application.
  • FIG5 is a schematic flow chart of an application connection method provided in an embodiment of the present application.
  • FIG6 is a schematic diagram of a developer interface of an open platform provided in an embodiment of the present application.
  • FIG. 7 is a schematic flow chart of a method for continuing application registration and applying for continuing authority provided in an embodiment of the present application
  • FIG8 is a schematic flow chart of establishing a matching relationship by applying for a subsequent application provided in an embodiment of the present application
  • FIG. 9 is a schematic flow chart of a method for registering and binding a connection application provided in an embodiment of the present application.
  • FIG10 is a schematic flow chart of a method for displaying a connection notification according to an embodiment of the present application.
  • FIG11 is a schematic flow chart of another method for displaying a connection notification provided in an embodiment of the present application.
  • FIG12 is a schematic flow chart of a method for acquiring and loading connection data provided in an embodiment of the present application.
  • FIG13 is a schematic diagram of a source device interface in the application connection method provided by the present application.
  • FIG. 14 is a schematic diagram of the interface of the peer device in the application connection method provided by the present application.
  • FIG15 is a schematic block diagram of a terminal device provided in an embodiment of the present application.
  • FIG16 is a schematic block diagram of another terminal device provided in an embodiment of the present application.
  • words such as “first” and “second” are used to distinguish the same or similar items with substantially the same functions and effects. Those skilled in the art can understand that words such as “first” and “second” do not limit the quantity and execution order, and words such as “first” and “second” do not necessarily limit the difference.
  • "at least one” means one or more, and “more” means two or more.
  • “And/or” describes the association relationship of the associated objects, indicating that there may be three relationships, for example, A and/or B, which can represent Indicates: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural.
  • the character “/” generally indicates that the objects before and after are in an “or” relationship.
  • “At least one of the following” or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can be represented by: a, b, c, ab, a--c, bc, or abc, where a, b, c can be single or plural.
  • terminal devices are divided into source devices and peer devices.
  • the source device is the sending device
  • the peer device is the receiving device.
  • the applications on the source device and the peer device can be connected by the user triggering the connection conditions.
  • the source device is a computer
  • the peer device is a mobile phone.
  • the user logs in to the same account on the computer and the mobile phone, and the computer and the mobile phone are in the same local area network. If the user plays a video on the video player software on the computer, the video player software on the user's mobile phone can play the video synchronously. If the user is editing text on the computer, the text being edited can be displayed synchronously on the user's mobile phone.
  • Fig. 1 shows a schematic diagram of an application scenario 100 of an embodiment of the present application.
  • the application scenario includes a first terminal device 101 and a second terminal device 102, wherein the first terminal device 101 can be used as a source device, the second terminal device 102 can be used as a peer device, a user logs in to the same account on the first terminal device 101 and the second terminal device 102, and the first terminal device 101 and the second terminal device 102 are in the same local area network, and the first terminal device 101 can connect the content of the application to the second terminal device 102.
  • the application scenario 100 further includes a third terminal device 103.
  • the third terminal device 103 can also serve as a peer device, the user also logs in to the same account on the third terminal device 103, and the first terminal device 101 and the third terminal device 103 are in the same local area network, and the first terminal device 101 can connect the content of the application to the third terminal device 103.
  • the number of peer devices may be one or more, and this is not limited in the embodiments of the present application.
  • the present application does not require that the above-mentioned multiple opposite-end devices are all in the same local area network as the source-end device.
  • the above-mentioned first terminal device 101 and the second terminal device 102 may be in one local area network (such as WiFi), and the first terminal device 101 and the third terminal device 103 may be in another local area network (such as Bluetooth).
  • the first terminal device 101 may connect the content on the application to the second terminal device 102 and the third terminal device 103 respectively.
  • FIG. 2 shows a schematic structural diagram of a terminal device 200 .
  • the terminal device may include a processor 210, an external memory interface 220, an internal memory 221, a universal serial bus (USB) interface 230, a charging management module 240, a power management module 241, a battery 242, an antenna 1, an antenna 2, a mobile communication module 250, a wireless communication module 260, an audio module 270, a speaker 270A, a receiver 270B, a microphone 270C, an earphone interface 270D, a sensor module 280, a button 290, a motor 291, an indicator 292, a camera 293, a display screen 294, and a subscriber identification module (SIM) card interface 295, etc.
  • SIM subscriber identification module
  • the sensor module 280 may include a pressure sensor 280A, a gyroscope sensor 280B, an air pressure sensor 280C, a magnetic sensor 280D, an acceleration sensor 280E, a distance sensor 280F, a proximity light sensor 280G, a fingerprint sensor 280H, a temperature sensor 280J, a touch sensor 280K, an ambient light sensor 280L, a bone marrow sensor 280A, a pressure sensor 280B, a ... pressure sensor 280D, Conductivity sensor 280M, etc.
  • the structure illustrated in the embodiments of the present application does not constitute a specific limitation on the terminal device.
  • the terminal device may include more or fewer components than shown in the figure, or combine certain components, or split certain components, or arrange the components differently.
  • the components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.
  • the processor 210 may include one or more processing units, for example, the processor 210 may include an application processor (AP), a modem processor, a graphics processor (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and/or a neural-network processing unit (NPU), etc.
  • AP application processor
  • GPU graphics processor
  • ISP image signal processor
  • DSP digital signal processor
  • NPU neural-network processing unit
  • Different processing units may be independent devices or integrated into one or more processors.
  • the controller can generate operation control signals according to the instruction operation code and timing signal to complete the control of instruction fetching and execution.
  • the processor 210 may also be provided with a memory for storing instructions and data.
  • the memory in the processor 210 is a cache memory.
  • the memory may store instructions or data that the processor 210 has just used or cyclically used. If the processor 210 needs to use the instruction or data again, it may be directly called from the memory. This avoids repeated access, reduces the waiting time of the processor 210, and thus improves the efficiency of the system.
  • the processor 210 may include one or more interfaces.
  • the interface may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver/transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input/output (GPIO) interface, a subscriber identity module (SIM) interface, and/or a universal serial bus (USB) interface, etc.
  • I2C inter-integrated circuit
  • I2S inter-integrated circuit sound
  • PCM pulse code modulation
  • UART universal asynchronous receiver/transmitter
  • MIPI mobile industry processor interface
  • GPIO general-purpose input/output
  • SIM subscriber identity module
  • USB universal serial bus
  • the interface connection relationship between the modules illustrated in the embodiment of the present application is only a schematic illustration and does not constitute a structural limitation on the terminal device.
  • the terminal device may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.
  • the terminal device implements the display function through a GPU, a display screen 294, and an application processor.
  • the GPU is a microprocessor for image processing, which connects the display screen 294 and the application processor.
  • the GPU is used to perform mathematical and geometric calculations for graphics rendering.
  • the processor 210 may include one or more GPUs, which execute program instructions to generate or change display information.
  • the terminal device can realize the shooting function through the ISP, the camera 293, the video codec, the GPU, the display screen 294 and the application processor.
  • the external memory interface 220 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the terminal device.
  • the external memory card communicates with the processor 210 through the external memory interface 220 to implement a data storage function. For example, files such as music and videos can be stored in the external memory card.
  • the internal memory 221 can be used to store computer executable program codes, and the executable program codes include instructions.
  • the internal memory 221 may include a program storage area and a data storage area.
  • the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc.
  • the data storage area may store data created during the use of the terminal device (such as audio data, a phone book, etc.), etc.
  • the internal memory 221 may include a program storage area and a data storage area.
  • 221 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc.
  • the processor 210 executes various functional applications and data processing of the terminal device by running instructions stored in the internal memory 221 and/or instructions stored in a memory provided in the processor. For example, the application continuation method of the embodiment of the present application may be executed
  • the terminal device of the present application can be used as a source device or as a peer device.
  • the source device can also be called a sender, and the peer device can also be called a receiver.
  • the software system of the terminal device can adopt a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture.
  • FIG. 3 of the embodiment of the present application takes the Android system of the layered architecture as an example to illustrate the software structure of the sender and the receiver.
  • the layered architecture divides the software into several layers, each with clear roles and division of labor. Data transmission and communication are carried out between layers through software interfaces.
  • the Android system is divided into five layers, from top to bottom, namely, the application layer, the application framework layer, the Android runtime (Android runtime) and system library, the hardware abstract layer (hardware abstract layer, HAL), and the kernel layer.
  • the application layer may include a series of application packages.
  • the application package may include third-party applications, software development kits (SDKs), Bluetooth, WIFI, memos, videos, games and other applications.
  • SDKs software development kits
  • the continuation application may access the continuation service SDK
  • the continuation application may be a system application in the terminal device, or a third-party application, and applications such as memos, videos, games and the like may also be system applications or third-party applications.
  • the application framework layer provides application programming interface (API) and programming framework for the applications in the application layer.
  • API application programming interface
  • the application framework layer includes some predefined functions.
  • the application framework layer may include a connection service manager, a communication service manager, an authentication service manager, a notification manager, a window manager, a resource manager, a content provider, and a view system, etc.
  • the manager may also be referred to as a module in some application scenarios.
  • connection service manager can be responsible for the management of connection tasks and can be the core of the overall connection service framework.
  • the connection service manager can be responsible for the access of connection applications, the authentication of connection applications, the icon management of connection applications, and the transmission of connection data across devices.
  • the communication service manager can be used to realize data transmission across devices.
  • the communication service manager can realize security authentication and account authentication of devices with the same account, self-discovery and self-organizing networking of devices, data transmission between devices, and access to communication services.
  • the authentication service manager may be responsible for verifying the legitimacy of the application.
  • the application may be allowed to access the subsequent service after the authentication service manager passes the verification.
  • the notification manager enables applications to display notification information in the status bar. It can be used to convey notification-type messages and can automatically disappear after a short stay without user interaction. For example, the notification manager is used to notify download completion, message reminders, etc.
  • the notification manager can also be a notification that appears in the system top status bar in the form of a chart or scroll bar text, such as a notification of an application running in the background, or a notification that appears on the screen in the form of a dialog window. For example, a text message is prompted in the status bar, a prompt tone is issued, the terminal device vibrates, the indicator light flashes, etc.
  • the notification manager can display the broadcast continuation notification in the taskbar.
  • the window manager is used to manage window programs.
  • the window manager can obtain the size of the display screen, determine whether there is a status bar, lock the screen, touch the screen, drag the screen, capture the screen, etc.
  • the resource manager provides various resources for applications, such as localized strings, icons, images, layout files, Video files, etc.
  • Content providers are used to implement data sharing between different applications, allowing one program to access data in another program while ensuring the security of the accessed data.
  • the view system can be responsible for the interface drawing and event processing of the application program.
  • the view system can be used to process the event processing after the user clicks the notification icon of the subsequent application.
  • Android runtime includes core libraries and virtual machines. Android runtime is responsible for scheduling and management of the Android system.
  • the core library consists of two parts: one part is the function that needs to be called by the Java language, and the other part is the Android core library.
  • the application layer and the application framework layer run in a virtual machine.
  • the virtual machine executes the Java files of the application layer and the application framework layer as binary files.
  • the virtual machine is used to perform functions such as object life cycle management, stack management, thread management, security and exception management, and garbage collection.
  • the system library can include multiple functional modules, such as media libraries, function libraries, graphics processing libraries (such as OpenGL ES), etc.
  • the media library supports playback and recording of a variety of commonly used audio and video formats, as well as static image files, etc.
  • the media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.
  • the function library provides developers with API interfaces for multiple services, making it easy for developers to quickly integrate and implement various functions.
  • the graphics processing library is used to implement graphics drawing, image rendering, synthesis and layer processing.
  • the hardware abstraction layer is an abstract structure between the kernel layer and the Android runtime.
  • the hardware abstraction layer can be a package of the hardware driver, providing a unified interface for the call of the upper-layer application.
  • the hardware abstraction layer may include a Bluetooth module, a WIFI module, a hardware configuration module, etc.
  • the Bluetooth module and the WIFI module in the hardware abstraction layer can shield the specific hardware implementation details of the Bluetooth driver and the WIFI driver in the kernel layer, and the upper-layer application can implement the Bluetooth function and the WIFI function by calling the interface without having to know the specific implementation method of the kernel-layer hardware driver.
  • the kernel layer is a layer between hardware and software.
  • the kernel layer may include display drivers, camera drivers, audio drivers, Bluetooth drivers, WiFi drivers, CPU drivers, etc.
  • the communication service manager can connect across devices through relevant modules such as Bluetooth drivers and WiFi drivers to achieve self-discovery and self-organizing networking of devices.
  • connection data in the Android system layered framework, combining the scenario of broadcast connection notification display between terminal devices during the application connection process.
  • the application in the application layer of the sending end, the application can realize data transmission with the continuation service by accessing the continuation service SDK.
  • the continuation service SDK can send a continuation service binding and application registration continuation service request to the continuation service manager, thereby realizing the continuation application registration and binding data transmission between the application layer and the application framework layer.
  • connection service manager can complete the binding of communication services by performing signaling transmission and data transmission with the communication service manager.
  • the connection service manager can also bind authentication services and application authentication with the authentication service manager.
  • the communication service manager can call the Bluetooth module interface and the WIFI module interface provided by the hardware abstraction layer to realize the self-discovery and self-organizing network of the device, and realize the session connection, message transmission, and transmission of follow-up content between terminal devices through the Bluetooth driver and WIFI driver in the kernel layer.
  • the receiving end When the receiving end receives the connection-related data from the sending end based on the kernel layer, it can transmit the data to Related modules in the hardware abstraction layer.
  • the communication service manager can obtain the transmitted connection data through the interface provided in the hardware abstraction layer, and perform signaling and data transmission with the connection service manager.
  • the connection service manager After receiving the connection-related data, the connection service manager can bind the authentication service and apply the authentication with the authentication service manager. Furthermore, the connection service manager can instruct the desktop launcher to display the broadcast connection notification in the form of an icon.
  • the sending end or the receiving end of the embodiment of the present application can also adopt the Windows system.
  • the difference from the Android system is that the layered architecture of the Windows system is mainly divided into user state and kernel state.
  • the user state can include user application processes, system processes, service processes, etc.;
  • the kernel state can include the kernel and device driver layer, as well as the hardware abstraction layer, etc.
  • the user application process can execute a series of applications.
  • the specific executable application types can be the same as the application types in the application layer of the Android system, which will not be repeated here.
  • the system process and service process may include a connection service manager, a communication service manager, an authentication service manager, a system process, a notification manager, a window manager, etc., which can provide corresponding services for the execution of user application processes.
  • the functions of the connection service manager, the communication service manager, the authentication service manager and other processes related to the embodiment of the present application can be found in the description of the relevant managers in Android, which will not be repeated here.
  • the kernel layer and device driver layer may include Bluetooth driver, WiFi driver, display driver, etc.
  • the hardware abstraction layer may include Bluetooth module, WiFi module, hardware configuration module, etc. The functions of specific functional modules can be found in the relevant description in Android, which will not be repeated here.
  • FIG5 is a schematic flow chart of an application connection method 500 provided in an embodiment of the present application.
  • the method 500 can be applied to the above scenario 100.
  • the hardware structure of the terminal device involved in the method 500 can be as shown in FIG2, and the software structure can be as shown in FIG3 or FIG4.
  • the first terminal device can correspond to the sending end of FIG3 or FIG4, and the second terminal device can correspond to the receiving end of FIG3 or FIG4.
  • a first terminal device sends a broadcast connection notification to a second terminal device, and correspondingly, the second terminal device receives the broadcast connection notification from the first terminal device.
  • the broadcast connection notification is used to request that the first connection application of the first terminal device be connected to the second terminal device.
  • the second terminal device determines a second connection application according to the broadcast connection notification.
  • the broadcast connection notification carries at least one device type of a target connection application
  • the second terminal device determines a target connection application having the same device type as the second terminal device as the second connection application.
  • the second terminal device performs legitimacy authentication and matching relationship verification on the second subsequent application, and obtains a legitimacy authentication result and a matching relationship verification result.
  • the application continuation method of the embodiment of the present application performs legitimacy authentication and matching relationship verification on the second continuation application on the second terminal device, and when the legitimacy authentication and matching relationship verification are passed, displays the continuation contact of the second continuation application on the second terminal device, thereby avoiding connecting the content of the application to an application with an unreliable trust source, improving the security of the application continuation, and thus improving the user experience.
  • the open platform can be understood as a web page or client of the open platform that can communicate with the cloud server.
  • application developers can log in to their developer accounts through their own devices (such as tablets, computers, laptops, etc.), enter the developer interface of the open platform, register the application by filling in the relevant information of the application, and apply for continued permissions for the application.
  • the administrator of the open platform can log in to his administrator account through his own device (such as tablets, computers, laptops, etc.), enter the administrator interface of the open platform, review the information submitted by the application developer, and assign an application identifier (application identification, APPID) and continued permissions to the application.
  • application identification application identification
  • Figure 6 is a schematic diagram of a developer interface of an open platform provided in an embodiment of the present application.
  • Figure 7 is a schematic flow chart of a method 700 for continuing application registration and applying for continued permissions provided in an embodiment of the present application. The following, in conjunction with Figures 6 and 7, details the process of application developers registering on the open platform and applying for continued permissions.
  • the application developer selects the platform type of the application to be registered as “Andriod”, the device type of the application to be registered as “tablet”, the application type of the application to be registered as tool class, enters the application package name of the application to be registered as “Com.Beiwanglu”, the user identification (UID) of the application to be registered as “5256XX1”, the application signature of the application to be registered as “0e 56 46 74 4a”, and uploads the application icon of the application to be registered (i.e., the six-pointed star-shaped icon shown in FIG. 6 ). Then, the application developer clicks the “Create” button. As shown in FIG.
  • the open platform in response to the application developer’s click operation, sends a registration instruction to the cloud server, and the registration instruction carries the relevant information selected and input by the above application developer.
  • the cloud server receives the registration instruction, and according to the relevant information selected and input by the above application developer, sends an audit task generation instruction to the open platform, and the audit task generation instruction is used to generate an audit task for the administrator account of the open platform.
  • the open platform receives the audit task generation instruction, and based on the audit task generation instruction, displays a button of the audit task prompt message on the administrator interface of the open platform. The administrator of the open platform clicks the button to view the audit task, and conducts a qualification review on the relevant information selected and input by the application developer.
  • the administrator of the open platform clicks the pass button, and the open platform sends the audit pass instruction to the cloud server.
  • the cloud server receives the audit pass instruction, allocates an APPID to the application to be registered, and sends it to the open platform. After receiving the APPID of the application to be registered, the open platform jumps from the interface a shown in Figure 6 to the interface b shown in Figure 6.
  • the application developer clicks to select "Basic Continuation Permission” and "Domestic Application Market Continuation", and clicks the "Submit” button.
  • the open platform in response to the application developer's click operation, the open platform sends a permission application instruction to the cloud server, and applies to the cloud server for basic continuation permission and domestic application market continuation permission.
  • the cloud server receives the permission application instruction, which carries the above-mentioned platform type, application name, APPID, application package name, application signature, application icon, and related information selected by the application developer. Based on the permission application instruction, the cloud server sends a permission approval task generation instruction to the open platform.
  • the permission approval task generation instruction is used to generate a permission approval task for the administrator account of the open platform.
  • the open platform receives the permission approval task generation instruction and displays a button with a permission approval task prompt message on the administrator interface of the open platform.
  • the administrator of the open platform clicks the button to view the permission approval task and approves the succession rights selected by the application developer.
  • the open platform will approve the permission, and if the permission is approved, the administrator of the open platform clicks the approval button, and the open platform sends a permission approval instruction to the cloud server.
  • the cloud server receives the permission approval instruction, establishes the association between the above platform type, application name, APPID, application package name, application signature, application icon, and subsequent permissions, and stores them.
  • the open platform jumps to the interface c shown in Figure 6 to the interface d shown in Figure 6. In the interface d shown in Figure 6, the open platform displays a pop-up window of "Permission approval successful" on the application developer's interface.
  • the above description only takes the case of passing the qualification review as an example. If the qualification review of the application to be registered fails, the cloud server will not allocate an APPID for the application to be registered, and the interface a shown in Figure 6 will not jump to the interface b shown in Figure 6, but will directly display a prompt message to prompt that the application developer's qualification review has not passed.
  • the above description only takes the case of passing the approval as an example. If the continued permission approval of the application to be registered fails, the cloud server will not establish and store the above association relationship, and the open platform will display a prompt message of the approval result (i.e., approval failed) to the application developer on the developer interface.
  • APPID is the identification information assigned to the application by the cloud server during the registration process of the application in the cloud server
  • UID is the identification information assigned during the application development process.
  • APPID is the identification information assigned to the application by the cloud server during the registration process of the application in the cloud server
  • UID is the identification information assigned during the application development process.
  • their installation packages will carry APPID, and the terminal device can parse and save the APPID of the application by installing the application.
  • Table 1 shows descriptions and examples of various information on the Android platform and the Windows platform.
  • a matching relationship can be established between the applications, for example, a matching relationship between Memo A on an Android phone and Memo B on an Android tablet, so that subsequent applications on different platforms or different categories of devices can be connected based on the matching relationship.
  • the above matching relationship can be established in a variety of different ways.
  • the developer of an application may apply to the cloud server to establish a matching relationship between applications on different platforms or different types of devices.
  • the developer of memo A may apply to the cloud server to establish a matching relationship between memo A and memo B.
  • FIG8 shows a schematic flow chart of a method 800 for establishing a matching relationship by applying for a subsequent application provided in an embodiment of the present application.
  • the developer of memo A logs in to his developer account on the open platform, and after memo A enters the platform type, APPID, package name, signature, and developer information of the target successor memo B on the developer interface of the open platform, he clicks the "Apply" button.
  • the open platform sends an application instruction to the cloud server, which carries the APPID of memo A, the APPID of memo B, the package name, and the signature.
  • the cloud server receives the application instruction and authenticates the legitimacy of memo B, that is, queries the package name and signature of memo B stored in the cloud server according to the APPID of memo B in the application instruction, and compares the package name and signature of memo B stored in the cloud server with the package name and signature of memo B carried in the application instruction. If the package name and signature of memo B stored in the cloud server are the same as the package name and signature of memo B carried in the application instruction, the cloud server considers that the legitimacy of memo B is authenticated, and sends a matching relationship establishment request to the open platform, which carries the platform type, APPID, package name, signature, and developer information of memo A.
  • the platform type, package name, signature, and developer information of memo A can be obtained by querying the cloud server based on the previous process of continuing application registration and applying for continued permissions.
  • the open platform receives the matching relationship establishment request, displays the matching relationship establishment request message on the developer interface of memo B, and the developer of memo B logs in to his developer account on the open platform and agrees or rejects the matching relationship establishment request by clicking.
  • the open platform sends a notification of agreeing or rejecting the matching relationship establishment to the cloud server.
  • the cloud server receives the notification of agreeing or rejecting the matching relationship establishment.
  • the cloud server establishes and stores the matching relationship between memo A and memo B, and sends a notification of successful matching relationship establishment to the open platform.
  • the open platform receives the notification of successful matching relationship establishment, and displays a notification reminder of successful matching relationship establishment on the developer interface of memo A. Otherwise, the cloud server does not establish a matching relationship between memo A and memo B, and displays a notification reminder of failed matching relationship establishment on the developer interface of memo A.
  • the application developer may pre-define the matching relationship of the application in the application installation package, and when the user installs the application on the terminal device, the terminal device may directly store the matching relationship of the application.
  • the application developer may pre-describe the APPID of other applications (hereinafter referred to as target follow-up applications) trusted by the application in the relevant files of the application, and establish a matching relationship between the application and the target follow-up application.
  • the application developer can describe the target follow-up application through the Metadata in the AndroidManifest.xml manifest file
  • the application developer can describe the target follow-up application through the registry value item of the application.
  • memo A and memo B are Android applications
  • the APPID of memo A is 123456
  • the APPID of memo B is 654321.
  • the developer of memo A specifies the AndroidManifest.xml manifest of memo A.
  • the metadata in the file is described as follows:
  • the mobile phone can parse the installation package of application A, obtain the matching relationship between memo A and memo B, and store the matching relationship in the system registration module on the mobile phone.
  • the application continuation method of the present application can be divided into three stages: the first stage is the registration and binding of the continuation application, the second stage is the display of the continuation notification, and the third stage is the acquisition and loading of the continuation data.
  • the system for implementing the method for connecting an application across devices may include a first terminal device, a second terminal device, and a cloud server.
  • the first terminal device may correspond to the transmitting end of FIG. 3 or FIG. 4, and the second terminal device may correspond to the receiving end of FIG. 3 or FIG. 4.
  • the first terminal device and the second terminal device may each include various functional modules for implementing the connection service, for example, a connection service SDK, a connection service manager, a communication service manager, and an authentication service manager.
  • the cloud server may include functional modules for implementing the connection service, for example, a communication service manager, an authentication service module, and a matching verification module.
  • connection application of the first terminal device will be referred to as the first connection application
  • connection service SDK of the first terminal device will be referred to as the first connection service SDK
  • connection service manager of the first terminal device will be referred to as the first connection service manager
  • communication service manager of the first terminal device will be referred to as the first communication service manager
  • authentication service manager of the first terminal device will be referred to as the first authentication service manager.
  • the continuation application of the second terminal device is called the second continuation application
  • the continuation service SDK of the second terminal device is called the second continuation service SDK
  • the continuation service manager of the second terminal device is called the second continuation service manager
  • the communication service manager of the second terminal device is called the second communication service manager
  • the authentication service manager of the second terminal device is called the second authentication service manager
  • the desktop launcher of the second terminal device is called the desktop launcher.
  • the communication service manager of the cloud server is called the third communication service manager
  • the authentication service module of the cloud server is called the third authentication service module
  • the matching verification module of the cloud server is called the matching verification module.
  • Figure 9 is a schematic flow chart of a method 900 for registration and binding of the subsequent application provided in an embodiment of the present application.
  • the method 900 may include the following steps.
  • a first connection application determines whether a current connection scenario is a first valid connection scenario.
  • the first continuation application when the current continuation scenario is the first valid continuation scenario, the first continuation application sends a registration continuation service request to the first continuation service SDK, and the registration continuation service request carries the UID and APPID of the first continuation application; correspondingly, the first continuation service SDK receives the registration continuation service request.
  • the first effective continuation scenario is determined based on the user behavior on the first continuation application.
  • the first continuation application is integrated with the first continuation service SDK.
  • the first continuation application can access the continuation service by calling the registration interface of the first continuation service SDK.
  • the user behavior can be the user clicking the first continuation application icon to start the application, or the user performing editing and other operations in the first continuation application, or the user clicking the play button in the first continuation application to perform operations such as video playback, music playback, or other media playback.
  • the specific monitored user behavior can be customized by the continuation application, and the embodiments of the present application are not limited thereto. system.
  • the first valid continuation scenario of the memo may be: in response to a user's click operation on the application icon of the memo, the memo application is in the startup state; in another possible implementation, the first valid continuation scenario of the memo may also be: in response to a user's input operation on the memo, the memo is currently in the editing state.
  • the first connection service SDK sends a registration connection service request to the first connection service manager.
  • the first connection service manager receives the registration connection service request.
  • the first connection service manager sends a first legitimacy authentication request to the first authentication service manager.
  • the first authentication service manager receives the first legitimacy authentication request.
  • the first legitimacy authentication request is used to request authentication of the first subsequent application, and the first legitimacy authentication request carries the UID (or process information) and APPID of the first subsequent application.
  • the first authentication service manager determines the local identification information of the first subsequent application based on the first legitimacy authentication request.
  • the first authentication service manager may determine the local identification information of the first subsequent application according to the UID (or process information) of the first subsequent application in the first legitimacy authentication request, where the local identification information includes the package name (or process name) and signature of the first subsequent application.
  • the first authentication service manager can determine the local identification information of the first continuation application according to the UID of the first continuation application, and the local identification information includes the package name and signature of the first continuation application.
  • the first authentication service manager can determine the local identification information of the first continuation application according to the process information of the first continuation application, and the local identification information includes the process name and signature of the first continuation application.
  • the first authentication service manager sends a first legitimacy authentication request to the first communication service manager.
  • the first communication manager receives the first legitimacy authentication request.
  • the first communication service manager sends a first legitimacy authentication request to the third communication service manager, and correspondingly, the third communication service manager receives the first legitimacy authentication request.
  • the third communication service manager sends a first legitimacy authentication request to the third authentication service module, and correspondingly, the third authentication service module receives the first legitimacy authentication request.
  • the third authentication service module obtains the cloud identification information of the first subsequent application based on the first legitimacy authentication request.
  • the third authentication service module can obtain the cloud identification information of the first subsequent application according to the APPID of the first subsequent application in the first legitimacy authentication request, and the cloud identification information includes the package name (or process name) and signature of the first subsequent application.
  • the cloud identification information is stored by the cloud server during the application process of the above-mentioned succession authority by the first succession application.
  • the third authentication service module sends the cloud identification information of the first connection application to the third communication service manager, and correspondingly, the third communication service manager receives the cloud identification information of the first connection application.
  • the third communication service manager sends the cloud identification information of the first connection application to the first communication service manager, and correspondingly, the first communication service manager receives the cloud identification information of the first connection application.
  • the first communication service manager sends the cloud identification information of the first connection application to the first authentication service manager, Correspondingly, the first authentication service manager receives the cloud identification information of the first follow-up application.
  • the first authentication service manager compares the cloud identification information and the local identification information of the first subsequent application, and determines the legitimacy authentication result of the first subsequent application according to whether the cloud identification information and the local identification information match.
  • the legitimacy authentication results may include authentication passed and authentication failed, and the match here can be the same.
  • the first authentication service manager determines that the legitimacy authentication of the first subsequent application has passed, otherwise, the first authentication service manager determines that the legitimacy authentication of the first subsequent application has failed.
  • the first authentication service manager sends the legitimacy authentication result of the first connection application to the first connection service manager, and correspondingly, the first connection service manager receives the legitimacy authentication result of the first connection application.
  • the first connection service management sends the legitimacy authentication result of the first connection application to the first connection application, and correspondingly, the first connection application receives the legitimacy authentication result of the first connection application.
  • the first communication service manager and the second communication service manager can perform self-discovery and self-networking through Bluetooth or WIFI, as well as account authentication. Furthermore, the first communication service manager can send information indicating that the second terminal device is online to the first connection service manager. For example, the information indicating that the second terminal device is online may include information such as the device identification (DevID) of the second terminal device.
  • DevID device identification
  • the first connection service manager After the first connection service manager receives the information sent by the first communication service manager indicating that the second terminal device is online, the information of the second terminal device can be stored and managed to execute the subsequent application connection process.
  • FIG. 10 is a schematic flow chart of a method 1000 for displaying a connection notification provided in an embodiment of the present application.
  • the method 1000 may include the following steps:
  • a first connection application determines whether a current connection scenario is a second valid connection scenario.
  • the second effective connection scenario is similar to the first effective connection scenario, which will not be described in detail here.
  • the second effective connection scenario may be the same as or different from the first effective connection scenario, and this application does not limit this.
  • the second effective continuation scenario and the first effective continuation scenario may both be that the first continuation application is in the startup state.
  • the first effective continuation scenario may be that the first continuation application is in the startup state
  • the second effective continuation scenario may be that the first continuation application is in the editing state.
  • the first connection application sends a broadcast connection notification to the first connection service SDK.
  • the first connection service SDK receives the broadcast connection notification.
  • the broadcast connection notification may carry the APPID and connection policy of the first connection application.
  • connection strategy is used to determine the devices that can be connected, and each application can correspond to its own connection strategy.
  • connection strategy of an application can be related to one or more of the following fields:
  • Connection status identification device types supported by the application, APPID of the target connection application, package name or process name of the target connection application, application market listing strategy of the second connection application, browser startup parameters, minimum version supporting connection, etc.
  • the connection status identifier may be a flag bit used to identify the connection policy status. For example, a flag bit of 0 may indicate that the connection is not supported, a flag bit of 1 may indicate an application connection, and a flag bit of 3 may indicate a browser connection. It is understood that the specific value of the flag bit may be set arbitrarily as long as it can distinguish different states, and the present application embodiment does not make specific limitations.
  • connection policy includes the device types supported by the application
  • the connection policy includes that the second connection application can support the implementation of connection services on mobile phones, tablet computers, televisions, computers, etc.
  • the first connection service manager confirms that the second terminal device is a mobile phone, tablet computer, television or computer, etc.
  • the first connection service manager can instruct the first communication service manager and the second communication service manager to establish a session path.
  • the continuation policy includes the package name of the target continuation application on the Android platform; if the target continuation application is an application on the Windows platform, the continuation policy includes the continuable process name of the target continuation application on the Windows platform.
  • the application market listing strategy can be any of the following: not listed, overseas application market 1, domestic application market 1, domestic application market 2, overseas application market 2.
  • the minimum version of the application that supports the continuation can be represented by the minimum version number of the application that supports the continuation, which is used to represent the minimum version of the second continuation application that can be continuation.
  • the continuation policy includes that the first continuation application can support a minimum version number of V1.5, or a minimum version of 15.
  • the first continuation service manager confirms that the version number of the second continuation application is greater than or equal to V1.5, or the version of the second continuation application is greater than or equal to 15, the first continuation service manager can instruct the first communication service manager and the second communication service manager to establish a session path.
  • the number of target connection applications can be at least one.
  • the first terminal device and multiple terminal devices including the second terminal device are in the same local area network and logged in to the same account, there can be multiple target connection applications in the broadcast connection notification.
  • a user logs in to the same account on a mobile phone, tablet computer and computer. If the mobile phone, tablet computer and computer are in the same local area network, the mobile phone, as the sending end (i.e., the first terminal device mentioned above), can identify that the tablet computer and the computer are online.
  • the memo A on the mobile phone sends the above-mentioned broadcast connection notification to the tablet computer and the computer
  • the target connection application included in the broadcast connection notification is the memo B of the tablet computer and the memo C of the computer.
  • the connection policy in the broadcast connection notification carries the following content:
  • the first connection service SDK sends a broadcast connection notification to the first connection service manager.
  • the first connection service manager receives the broadcast connection notification.
  • the first connection service manager sends a broadcast connection notification to the first communication service manager.
  • the first communication service manager receives the broadcast connection notification.
  • the first communication service manager sends the broadcast connection notification to the second communication service manager, and correspondingly, the second communication service manager receives the broadcast connection notification.
  • the second communication service manager sends the broadcast connection notification to the second connection service manager.
  • the second connection service manager receives the broadcast connection notification.
  • the second connection service manager determines a second connection application based on the broadcast connection notification.
  • the broadcast connection notification carries device type information of the target connection application
  • the second connection service manager can determine the second connection application from the target connection application according to the device type information of the target connection application and the second terminal device.
  • the second connection service manager may determine that the memo B of the tablet computer is the second connection application.
  • the second connection service manager determines whether the second terminal device has installed the second connection application.
  • the second connection service manager may query whether the second terminal device includes the package name/process name of the second connection application. When the second terminal device includes the package name/process name of the second connection application, it may be determined that the second terminal device has installed the second connection application.
  • the second connection service manager when the second connection application has been installed on the second terminal device, the second connection service manager sends a second legitimacy authentication request and a matching relationship verification request to the second authentication service manager, and correspondingly, the second authentication service manager receives the second legitimacy authentication request and the matching relationship verification request.
  • the second connection service manager may instruct the second terminal device to install the second connection application.
  • the second authentication service manager sends a second legitimacy authentication request to the second communication service manager, corresponding to Preferably, the second communication service manager receives a second legitimacy authentication request.
  • the second communication service manager sends a second legitimacy authentication request to the third communication service manager, and correspondingly, the third communication service manager receives the second legitimacy authentication request.
  • the third communication service manager sends a second legitimacy authentication request to the third authentication service module, and correspondingly, the third authentication service module receives the second legitimacy authentication request.
  • the third authentication service module obtains the cloud identification information of the second subsequent application according to the second legitimacy authentication request.
  • the cloud identification information includes the package name (or process name) and signature of the second subsequent application stored in the cloud server.
  • the third authentication service module returns the cloud identification information to the third communication service manager, and correspondingly, the third communication service manager receives the cloud identification information.
  • the third communication service manager returns the cloud identification information to the second communication service manager, and correspondingly, the second communication service manager receives the cloud identification information.
  • the second communication service manager returns the cloud identification information to the second authentication service manager, and correspondingly, the second authentication service manager receives the cloud identification information.
  • the second authentication service manager compares the cloud identification information and the local identification information, and determines the legitimacy authentication result of the second subsequent application according to whether the cloud identification information and the local identification information match.
  • the local identification information is the package name (or process name) and signature of the second continuation application stored on the second terminal device.
  • the broadcast continuation notification carries the package name/process name of the second continuation application.
  • the second authentication service manager can obtain the signature of the second continuation application through the package name/process name of the second continuation application.
  • the second authentication service manager can obtain the signature of the second continuation application through the package name of the second continuation application.
  • the second authentication service manager can obtain the installation path of the second continuation application from the registry information RegRoot and RegKey through the process name of the second continuation application, find the main process of the second continuation application after splicing the relative path described by "ImagePath", and then read the signature of the second continuation application.
  • the second authentication service manager sends a matching relationship verification request to the second communication service manager.
  • the second communication service manager receives the matching relationship verification request.
  • the second communication service manager sends a matching relationship query request to the third communication service manager based on the matching relationship verification request.
  • the third communication service manager receives the matching relationship query request.
  • the matching relationship query request carries the APPID of the first subsequent application.
  • S1020 The third communication service manager sends a matching relationship query request to the matching verification module.
  • the matching verification module receives the matching relationship query request.
  • the matching verification module queries and obtains a first matching relationship based on the matching relationship query request.
  • the matching verification module stores the matching relationship between applications.
  • the first subsequent application may or may not have a matching relationship with at least one subsequent application, and this application does not limit this.
  • the matching verification module can query the first connection application according to the APPID of the first connection application.
  • the applications with matching relationships obtain at least one application with which the first subsequent application has a matching relationship.
  • the matching verification module returns the first matching relationship to the third communication service manager.
  • the third communication service manager receives the first matching relationship.
  • the third communication service manager returns the first matching relationship to the second communication service manager, and correspondingly, the second communication service manager receives the first matching relationship.
  • the second communication service manager returns the first matching relationship to the second authentication service manager.
  • the second authentication service manager receives the first matching relationship.
  • the second authentication service manager performs a matching relationship verification based on the first matching relationship, that is, determines whether there is a matching relationship between the first follow-up application and the second follow-up application.
  • the first matching relationship includes two situations, and matching relationship verification based on the first matching relationship also includes two situations:
  • the first matching relationship is used to represent at least one application that can be connected to the second connection application.
  • judging whether there is a matching relationship between the first connection application and the second connection application can be: judging whether at least one application that has a matching relationship with the second connection application includes the first connection application.
  • at least one application that has a matching relationship with the second connection application includes the first connection application, it is considered that there is a matching relationship between the first connection application and the second connection application, and the matching relationship verification passes; otherwise, it is considered that there is no matching relationship between the first connection application and the second connection application, and the matching relationship verification fails.
  • the first matching relationship is used to represent at least one application that can be connected to the first connection application.
  • judging whether there is a matching relationship between the first connection application and the second connection application can be: judging whether the at least one application that has a matching relationship with the first connection application includes the second connection application.
  • the at least one application that has a matching relationship with the first connection application includes the second connection application, it is considered that there is a matching relationship between the first connection application and the second connection application, and the matching relationship verification passes; otherwise, it is considered that there is no matching relationship between the first connection application and the second connection application, and the matching relationship verification fails.
  • the second authentication service manager returns the legality authentication result and the matching relationship verification result to the second connection service manager, and correspondingly, the second connection service manager receives the legality authentication result and the matching relationship verification result.
  • the legality authentication result includes authentication passed or authentication failed
  • the matching relationship verification result includes verification passed or verification passed.
  • the desktop launcher controls the display of a connection point of the second connection application.
  • the connection point may be displayed in the form of an icon of the second connection application.
  • steps S1011 to S1017 and steps S1018 to S1025 are not in a particular order and can be executed simultaneously, or S1018 to S1025 can be executed first and then S1011 to S1017.
  • the embodiments of the present application are not limited to this.
  • FIG10 shows the display process of the continuation notification in which the matching relationship between applications is established and stored in the cloud server. If the application developer pre-defines the matching relationship between the second continuation application and other applications in the installation package of the second continuation application, the second terminal device can obtain the above-mentioned first matching relationship after installing the second continuation application without querying the cloud server.
  • the display process of the continuation notification in this case is introduced below in conjunction with FIG10.
  • FIG. 11 is a schematic flow chart of another method 1100 for displaying a connection notification provided by an embodiment of the present application.
  • the application framework layer of the software structure of the terminal device also includes a system registration manager for storing the matching relationship of applications when connecting.
  • the method 1100 is similar to the above-mentioned method 1000, wherein steps S1101 to S1117 are the same as the above-mentioned steps S1001 to S1017, and are not repeated here.
  • the second authentication service manager sends a matching relationship verification request to the system registration manager, and correspondingly, the system registration manager receives the matching relationship verification request.
  • S1119 The system registration manager queries and obtains a second matching relationship based on the matching relationship verification request.
  • the application developer has pre-defined the matching relationship between the second continuation application and other applications (i.e., the second matching relationship) in the installation package of the second continuation application.
  • the second terminal device installs the second continuation application, it parses the installation package of the second continuation application, obtains the second matching relationship, and stores the second matching relationship in the system registration manager.
  • S1120 The system registration manager sends the first matching relationship to the second authentication service manager, and correspondingly, the second authentication service manager receives the second matching relationship.
  • the second authentication service manager performs a matching relationship verification based on the second matching relationship, that is, determines whether there is a matching relationship between the first follow-up application and the second follow-up application.
  • FIG12 is a schematic flow chart of a method 1200 for acquiring and loading connection data provided in an embodiment of the present application.
  • the method 1200 includes the following steps:
  • the second connection service manager may launch a second connection application and instruct the second connection application to load a transition animation effect.
  • the second follow-up application may be started and load the transition effect.
  • the transition effect may include prompt information such as "Loading"
  • the second connection application calls the second connection service SDK to register the connection service and callback.
  • the second continuation application may carry information such as the application package name of the second continuation application when registering the continuation service.
  • the second connection service SDK sends a request for binding the connection service to the second connection service manager.
  • the second connection service manager receives the request for binding the connection service.
  • the second connection service manager sends a request for binding the communication service to the second communication service manager.
  • the second communication service manager receives the request for binding the communication service.
  • the second connection service manager sends a binding success message to the second connection service SDK.
  • the service SDK receives a successful binding message.
  • the second connection service SDK sends a request for registering the connection service and a callback to the second connection service manager.
  • the second connection service manager receives the request for registering the connection service and a callback.
  • the second connection service SDK sends a registration success message to the second connection application, and correspondingly, the second connection application receives the registration success message.
  • connection service manager After S1201, the second connection service manager sends a connection data request to the second communication service manager, and correspondingly, the second communication service manager receives the connection data request.
  • the second communication service manager sends a connection data request to the first communication management server, and correspondingly, the first communication management server receives the connection data request.
  • the first communication management server sends a connection data request to the first connection service manager.
  • the first connection service manager receives the connection data request.
  • the first connection service manager sends a connection data request to the first connection service SDK.
  • the first connection service SDK receives the connection data request.
  • the first connection service SDK sends a connection data request to the first connection application, and correspondingly, the first connection application receives the connection data request.
  • the first connection application packages and encrypts the connection data.
  • the first connection application sends connection data to the first connection service SDK, and correspondingly, the first connection service SDK receives the connection data.
  • the first connection service SDK sends connection data to the first connection service manager, and correspondingly, the first connection service manager receives the connection data.
  • the first connection service manager sends connection data to the first communication management server, and correspondingly, the first communication management server receives the connection data.
  • the first communication management server sends connection data to the second communication service manager, and correspondingly, the second communication service manager receives the connection data.
  • the second communication service manager sends connection data to the second connection service manager, and correspondingly, the second connection service manager receives the connection data.
  • the second connection service manager sends connection data to the second connection application, and correspondingly, the second connection application receives the connection data.
  • the second connection application sends a connection success message to the second connection service SDK.
  • the second connection service SDK receives the connection success message.
  • the second connection service SDK sends a connection success message to the second connection service manager.
  • the second connection service manager receives the connection success message.
  • the second connection service manager sends a connection success message to the second communication service manager, and correspondingly, the second communication service manager receives the connection success message.
  • the first communication management server sends a connection success message to the first connection service manager, and correspondingly, the first connection service manager receives the connection success message.
  • the first connection service manager sends a connection success message to the first connection service SDK.
  • the first connection service SDK receives the connection success message.
  • the first connection service SDK sends a connection success message to the first connection application, and correspondingly, the first connection application receives the connection success message.
  • the first continuation application if the first continuation application has already registered and bound to the continuation service, then when the first continuation application of the first terminal device monitors some user behaviors, the first continuation application does not need to re-register for the continuation service, or it is understood that there is no need to execute the above-mentioned method 900.
  • the first continuation application can directly execute method 1000 or 1100, as well as method 1200, etc., which will not be repeated here.
  • the first terminal device i.e., source device
  • the second terminal device i.e., peer device
  • the connecting application is a memo.
  • the mobile phone and the tablet computer are in the same local area network, and the memos of the mobile phone and the tablet computer are logged in to the same account.
  • FIG13 is a schematic diagram of the source device interface in the application connection method provided by the present application, which is used to introduce the interface of the mobile phone as the source device responding to the user operation.
  • the user is editing text on the mobile phone's memo
  • the mobile phone displays the text edited by the user accordingly, and the cursor position changes with the user's editing position.
  • the mobile phone's memo is in the editing state, and the mobile phone sends a broadcast connection notification of the mobile phone memo to the tablet computer.
  • FIG 14 is a schematic diagram of an interface change of a peer device provided in an embodiment of the present application, which is used to introduce the interface change of a tablet computer as a peer device in response to user operations.
  • a recent taskbar is displayed below the desktop of the tablet computer, and the recent taskbar includes a memo icon and multiple other application icons.
  • the tablet computer receives a broadcast continuation notification from the mobile phone, and displays a contact (such as a black dot in Figure 14) in the upper right corner of the memo icon in the recent taskbar to prompt the user that the memo from the mobile phone wants to be continued with the memo of the tablet computer.
  • interface b of Figure 14 a memo page is displayed, and "Loading continuation content" is displayed on the memo page. After the content is loaded, interface c of Figure 14 is displayed. In interface c of Figure 14, the same memo content and the same cursor position as the mobile phone are displayed.
  • Fig. 15 is a terminal device 1500 provided in an embodiment of the present application, and the terminal device 1500 includes: a processing module 1501 and a transceiver module 1502.
  • the terminal device 1500 is used to implement the steps corresponding to the second terminal device in the above method.
  • the transceiver module 1502 is used to: receive a broadcast connection notification from the first terminal device, the broadcast connection notification is used to request that the first connection application of the first terminal device be connected to the terminal device; the processing module 1501 is used to: determine the second connection application based on the broadcast connection notification, and perform legitimacy authentication and matching relationship verification on the second connection application to obtain a legitimacy authentication result and a matching relationship verification result; when the legitimacy authentication result is that the legitimacy authentication passed, and the matching relationship verification result is that the matching relationship verification passed, display the connection contact of the second connection application.
  • the above-mentioned broadcast continuation notification includes: an application identifier APPID and a continuation policy of the first continuation application; wherein the continuation policy includes at least one of the following: a continuation status identifier, a package name or process name of at least one target continuation application, a device type of at least one target continuation application, an application market listing policy of at least one target continuation application, and a minimum version supporting the continuation; at least one target continuation application includes a second continuation application.
  • the processing module 1501 is further configured to: based on the device type of the at least one target connection application, determine an application of the same device type as the terminal device in the at least one target connection application as the second connection application.
  • the transceiver module 1502 is also used to: send a legitimacy authentication request to the cloud server, the legitimacy authentication request carries the APPID of the second subsequent application; receive cloud identification information of the second subsequent application from the cloud server, the cloud identification information includes the package name and/or signature of the second subsequent application stored in the cloud server; the processing module 1501 is also used to: compare the cloud identification information with the local identification information of the second subsequent application to obtain a legitimacy authentication result, the local identification information is the package name and/or signature of the second subsequent application stored locally on the terminal device.
  • the transceiver module 1502 is also used to: send a matching relationship query request to the cloud server, the matching relationship query request carries the APPID of the second connection application; receive a first matching relationship from the cloud server, the first matching relationship is used to represent at least one application that can be connected with the second connection application; the processing module 1501 is also used to: based on the first matching relationship, determine whether at least one application includes the first connection application, and obtain a matching relationship verification result.
  • the transceiver module 1502 is also used to: send a matching relationship query request to the cloud server, the matching relationship query request carries the APPID of the first succession application; receive a first matching relationship from the cloud server, the first matching relationship is used to represent at least one application that can be connected with the first succession application; the processing module 1501 is also used to: based on the first matching relationship, determine whether at least one application includes the second succession application, and obtain a matching relationship verification result.
  • the processing module 1501 is also used to: obtain a second matching relationship, the second matching relationship is used to represent at least one application that can be connected with the second connection application, and the second matching relationship is pre-stored locally when the terminal device installs the second connection application; based on the second matching relationship, determine whether at least one application includes the first connection application, and obtain a matching relationship verification result.
  • the transceiver module 1502 is further used to: in response to a user clicking operation on the connection contact, send a connection data request message to the first terminal device; receive connection data from the first terminal device, and display the connection data.
  • the terminal device 1500 here is embodied in the form of a functional module.
  • the term "module” here may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a dedicated processor or a group processor, etc.) and a memory for executing one or more software or firmware programs, a combined logic circuit and/or other suitable components that support the described functions.
  • ASIC application specific integrated circuit
  • the terminal device 1500 can be specifically the second terminal device in the above embodiment, and the terminal device 1500 can be used to execute the various processes and/or steps corresponding to the second terminal device in the above method embodiment. To avoid repetition, it will not be repeated here.
  • the terminal device 1500 has the function of implementing the corresponding steps performed by the second terminal device in the above method; the above function can be implemented by hardware, or by hardware executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the above function.
  • the transceiver module 1502 may include a sending module and a receiving module, the sending module can be used to implement the various steps and/or processes for performing the sending action corresponding to the above transceiver module, and the receiving module can be used to implement the various steps and/or processes for performing the receiving action corresponding to the above transceiver module.
  • the sending module can be replaced by a transmitter, and the receiving module can be replaced by a receiver, respectively performing the sending and receiving operations and related processing operations in each method embodiment.
  • the terminal device 1500 in FIG. 15 may also be a chip or a chip system, such as a system on chip (SOC).
  • the transceiver module 1502 may be a transceiver circuit of the chip, which is not limited here.
  • FIG16 is another terminal device 1600 provided in an embodiment of the present application.
  • the terminal device 1600 includes a processor 1601, a transceiver 1602, and a memory 1603.
  • the processor 1601, the transceiver 1602, and the memory 1603 communicate with each other through an internal connection path, the memory 1603 is used to store instructions, and the processor 1601 is used to execute the instructions stored in the memory 1603 to control the transceiver 1602 to send signals and/or receive signals.
  • the terminal device 1600 can be specifically the second terminal device in the above embodiment, and can be used to execute the various steps and/or processes corresponding to the second terminal device in the above method embodiment.
  • the memory 1603 may include a read-only memory and a random access memory, and provide instructions and data to the processor. A part of the memory may also include a non-volatile random access memory.
  • the memory may also store information about the device type.
  • the processor 1601 may be used to execute instructions stored in the memory, and when the processor 1601 executes the instructions stored in the memory, the processor 1601 is used to execute the various steps and/or processes of the above method embodiment corresponding to the second terminal device.
  • the transceiver 1602 may include a transmitter and a receiver, the transmitter may be used to implement the various steps and/or processes corresponding to the above transceiver for performing the sending action, and the receiver may be used to implement the various steps and/or processes corresponding to the above transceiver for performing the receiving action.
  • the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • CPU central processing unit
  • DSP digital signal processors
  • ASIC application-specific integrated circuits
  • FPGA field programmable gate arrays
  • a general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.
  • each step of the above method can be completed by an integrated logic circuit of hardware in a processor or an instruction in the form of software.
  • the steps of the method disclosed in conjunction with the embodiment of the present application can be directly embodied as a hardware processor for execution, or a combination of hardware and software modules in a processor for execution.
  • the software module can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc.
  • the storage medium is located in a memory, and the processor executes the instructions in the memory, and completes the steps of the above method in conjunction with its hardware. To avoid repetition, it is not described in detail here.
  • the present application also provides a computer-readable storage medium, which is used to store a computer program, and the computer program is used to implement the method corresponding to the second terminal device in the above embodiment.
  • the present application also provides a computer program product, which includes a computer program (also referred to as code or instruction).
  • a computer program also referred to as code or instruction.
  • the computer program runs on a computer, the computer can execute the method corresponding to the second terminal device shown in the above embodiment.
  • modules and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.
  • the disclosed systems, devices and methods can be
  • the device embodiments described above are only schematic, for example, the division of the modules is only a logical function division, and there may be other divisions in actual implementation, such as multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed.
  • Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or modules, which can be electrical, mechanical or other forms.
  • modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical modules, that is, they may be located in one place or distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional module in each embodiment of the present application may be integrated into one processing module, or each module may exist physically separately, or two or more modules may be integrated into one module.
  • the functions are implemented in the form of software function modules and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art.
  • the computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk, and other media that can store program codes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Human Computer Interaction (AREA)
  • Multimedia (AREA)
  • Technology Law (AREA)
  • Computer Hardware Design (AREA)
  • Telephone Function (AREA)
  • Stored Programmes (AREA)

Abstract

本申请实施例提供了一种应用接续方法和终端设备，能够避免将应用的内容接续到信任源不可靠的应用，提高应用接续的安全性，从而提高用户体验。该方法包括：第二终端设备接收来自第一终端设备的广播接续通知，广播接续通知用于请求将第一终端设备的第一接续应用接续至第二终端设备；第二终端设备根据广播接续通知，确定第二接续应用，并对第二接续应用进行合法性鉴权和匹配关系校验，获得合法性鉴权结果和匹配关系校验结果；在合法性鉴权结果为合法性鉴权通过、且匹配关系校验结果为匹配关系校验通过的情况下，第二终端设备显示第二接续应用的接续触点。

Description

应用接续方法和终端设备
本申请要求于2022年09月28日提交中国国家知识产权局、申请号为202211193576.5、申请名称为“应用接续方法和终端设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及终端技术领域，尤其涉及一种应用接续方法和终端设备。
背景技术
在多设备场景中，终端设备被划分为源端设备和对端设备，源端设备是发送端设备，对端设备是接收端设备。当源端设备和对端设备登陆了相同的账号，并且源端设备和对端设备处于同一局域网的情况下，通过用户触发接续条件，源端设备和对端设备上的应用可实现接续。例如，源端设备为电脑，对端设备为手机，用户在电脑和手机登陆了相同的账号，且电脑和手机处于同一局域网，若用户在电脑上的视频播放软件播放视频，用户的手机上的视频播放软件能同步播放该视频，若用户在电脑上正在编辑文本，用户的手机上可以同步显示正在编辑的文本。
但是，在应用接续的过程中，对于某一应用而言，源端设备上应用的内容可能会接续到对端设备上信任源不可靠的应用上，导致用户信息泄露，例如，手机将备忘录的内容接续到平板上的备忘录，若平板上的备忘录是一个伪造的应用，用户所编辑的信息就会被这个伪造的应用窃取。因此，目前需要提供一种应用接续方法，能够避免将应用的内容接续到信任源不可靠的应用，提高应用接续的安全性。
发明内容
本申请实施例提供一种应用接续方法和终端设备，能够避免将应用的内容接续到信任源不可靠的应用，提高应用接续的安全性，从而提高用户体验。
第一方面，提供了一种应用接续方法，应用于包括第一终端设备、第二终端设备、以及云服务器的系统，用户在第一终端设备和第二终端设备上登录了相同的账号，并且第一终端设备与第二终端设备处于同一局域网，该方法包括：第二终端设备接收来自第一终端设备的广播接续通知，广播接续通知用于请求将第一终端设备的第一接续应用接续至第二终端设备；第二终端设备根据广播接续通知，确定第二接续应用，并对第二接续应用进行合法性鉴权和匹配关系校验，获得合法性鉴权结果和匹配关系校验结果；在合法性鉴权结果为合法性鉴权通过、且匹配关系校验结果为匹配关系校验通过的情况下，第二终端设备显示第二接续应用的接续触点。
本申请实施例的应用接续方法，通过第二终端设备上对第二接续应用进行合法性鉴权和匹配关系校验，在合法性鉴权和匹配关系检验均通过的情况下，在第二终端设备上显示第二接续应用的接续触点，能够避免将应用的内容接续到信任源不可靠的应用，提高应用接续的安全性，从而提高用户体验。
结合第一方面，在第一方面的某些实现方式中，上述广播接续通知包括：第一接续应用的应用标识符APPID和接续策略；其中，接续策略包括下列至少一种：接续状态标识、至少一个目标接续应用的包名或进程名、至少一个目标接续应用的设备类型、至少一个目标接续应用的应用市场上架策略以及支持接续的最小版本；至少一个目标接续应用包括第二接续应用。
应理解，接续状态标识可以为用于标识接续策略状态的标志位。例如，标志位为0可以表示不支持接续，标志位为1可以表示应用接续，标志位为3可以表示浏览器接续。可以理解的是，标志位的具体值可以任意设置，能够区分不同的状态即可，本申请实施例不作具体限定。
还应理解，若第一接续应用为Android平台的应用，则接续策略包括第一接续应用在Android平台的包名；若第一接续应用为Windows平台的应用，则接续策略包括第一接续应用在Windows平台的可接续进程名。
应用市场上架策略可以为下列任一种：未上架、海外应用市场1、国内应用市场1、国内应用市场2、海外应用市场2。
支持接续应用的最小版本可以用支持接续应用的最小版本号表示，用于表示第二接续应用可接续时的最小版本。
结合第一方面，在第一方面的某些实现方式中，上述第二终端设备根据广播接续通知，确定第二接续应用，包括：第二终端设备基于至少一个目标接续应用的设备类型，将至少一个目标接续应用中与第二终端设备的设备类型相同的应用确定为第二接续应用。
结合第一方面，在第一方面的某些实现方式中，上述对第二接续应用进行合法性鉴权，包括：第二终端设备向云服务器发送合法性鉴权请求，合法性鉴权请求携带第二接续应用的APPID；第二终端设备接收来自云服务器的第二接续应用的云端标识信息，云端标识信息包括云服务器存储的第二接续应用的包名和/或签名；第二终端设备将云端标识信息和第二接续应用的本地标识信息进行比较，获得合法性鉴权结果，本地标识信息为第二终端设备本地存储的第二接续应用的包名和/或签名。
结合第一方面，在第一方面的某些实现方式中，上述对第二接续应用进行匹配关系校验，包括：第二终端设备向云服务器发送匹配关系查询请求，匹配关系查询请求携带第二接续应用的APPID；第二终端设备接收来自云服务器的第一匹配关系，第一匹配关系用于表示能够与第二接续应用进行接续的至少一个应用；第二终端设备基于第一匹配关系，判断至少一个应用是否包括第一接续应用，获得匹配关系校验结果。
应理解，当与第二接续应用存在匹配关系的至少一个应用中包括第一接续应用，则认为第一接续应用和第二接续应用之间存在匹配关系，匹配关系校验通过，否则，认为第一接续应用和第二接续应用之间不存在匹配关系，匹配关系校验未通过。
结合第一方面，在第一方面的某些实现方式中，上述对第二接续应用进行匹配关系校验，包括：第二终端设备向云服务器发送匹配关系查询请求，匹配关系查询请求携带第一接续应用的APPID；第二终端设备接收来自云服务器的第一匹配关系，第一匹配关系用于表示能够与第一接续应用进行接续的至少一个应用；第二终端设备基于第一匹配关系，判断至少一个应用是否包括第二接续应用，获得匹配关系校验结果。
应理解，当与第一接续应用存在匹配关系的至少一个应用中包括第二接续应用，则认 为第一接续应用和第二接续应用之间存在匹配关系，匹配关系校验通过，否则，认为第一接续应用和第二接续应用之间不存在匹配关系，匹配关系校验未通过。
结合第一方面，在第一方面的某些实现方式中，上述对第二接续应用进行匹配关系校验，包括：第二终端设备获取第二匹配关系，第二匹配关系用于表示能够与第二接续应用进行接续的至少一个应用，第二匹配关系是第二终端设备在安装第二接续应用时预先存储在本地的；第二终端设备基于第二匹配关系，判断至少一个应用是否包括第一接续应用，获得匹配关系校验结果。
应理解，应用开发者预先在第二接续应用的安装包中定义了第二接续应用与其他应用之间的匹配关系(即第二匹配关系)，第二终端设备在安装第二接续应用时，解析第二接续应用的安装包，得到第二匹配关系，并将第二匹配关系存储在系统注册管理器。
具体地，当与第二接续应用存在匹配关系的至少一个应用中包括第一接续应用，则认为第一接续应用和第二接续应用之间存在匹配关系，匹配关系校验通过，否则，认为第一接续应用和第二接续应用之间不存在匹配关系，匹配关系校验未通过。
结合第一方面，在第一方面的某些实现方式中，上述方法还包括：第二终端设备响应于用户对接续触点的点击操作，向第一终端设备发送接续数据请求消息；第二终端设备接收来自第一终端设备的接续数据，并显示接续数据。
第二方面，提供了一种终端设备，用于执行上述第一方面中任一种可能的实现方式中的方法。具体地，该终端设备包括用于执行上述第一方面中任一种可能的实现方式中的方法的模块。
在一种设计中，该终端设备可以包括执行上述各个方面中所描述的方法/操作/步骤/动作所一一对应的模块，该模块可以是硬件电路，也可是软件，也可以是硬件电路结合软件实现。
在另一种设计中，该终端设备为通信芯片，通信芯片可以包括用于发送信息或数据的输入电路或者接口，以及用于接收信息或数据的输出电路或者接口。
在另一种设计中，该终端设备为通信设备，通信设备可以包括用于发送信息或数据的发射机，以及用于接收信息或数据的接收机。
第三方面，提供了一种终端设备，包括处理器和存储器。该处理器用于读取存储器中存储的指令，并可通过接收器接收信号，通过发射器发射信号，以执行上述第一方面中的任一种可能实现方式中的方法。
可选地，处理器为一个或多个，存储器为一个或多个。
可选地，存储器可以与处理器集成在一起，或者存储器与处理器分离设置。
在具体实现过程中，存储器可以为非瞬时性(non-transitory)存储器，例如只读存储器(read only memory，ROM)，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限定。
应理解，相关的数据交互过程例如发送接续数据请求信息可以为从处理器输出指示信息的过程，接收能力信息可以为处理器接收输入能力信息的过程。具体地，处理输出的数据可以输出给发射器，处理器接收的输入数据可以来自接收器。其中，发射器和接收器可以统称为收发器。
上述第三方面中的终端设备可以是一个芯片，该处理器可以通过硬件来实现也可以通 过软件来实现，当通过硬件实现时，该处理器可以是逻辑电路、集成电路等；当通过软件来实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现，该存储器可以集成在处理器中，可以位于该处理器之外，独立存在。
第四方面，提供了一种计算机程序产品，计算机程序产品包括：计算机程序(也可以称为代码，或指令)，当计算机程序被运行时，使得计算机执行上述第一方面中的任一种可能实现方式中的方法。
第五方面，提供了一种计算机可读存储介质，该计算机可读存储介质存储有计算机程序(也可以称为代码，或指令)，当其在计算机上运行时，使得计算机执行上述第一方面中的任一种可能实现方式中的方法。
附图说明
图1是本申请实施例的应用场景示意图；
图2是本申请实施例提供的终端设备的结构示意图；
图3是本申请实施例提供的终端设备的软件结构示意图；
图4是本申请实施例提供的终端设备的另一种软件结构示意图；
图5是本申请实施例提供的一种应用接续方法的示意性流程图；
图6是本申请实施例提供的一种开放平台的开发者界面的示意图；
图7是本申请实施例提供的一种接续应用注册和申请接续权限的示意性流程图；
图8是本申请实施例提供的一种接续应用申请建立匹配关系的示意性流程图；
图9是本申请实施例提供的接续应用的注册与绑定的方法的示意性流程图；
图10是本申请实施例提供的接续通知的显示方法的示意性流程图；
图11是本申请实施例提供的另一接续通知的显示方法的示意性流程图；
图12是本申请实施例提供的接续数据的获取与加载方法的示意性流程图；
图13是本申请提供的应用接续方法中源端设备界面示意图；
图14是本申请提供的应用接续方法中对端设备界面示意图；
图15是本申请实施例提供的一种终端设备的示意性框图；
图16是本申请实施例提供的另一种终端设备的示意性框图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。
需要说明的是，本申请实施例中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其他实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
本申请实施例中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表 示：单独存在A，同时存在A和B，单独存在B的情况，其中A，B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b，或c中的至少一项(个)，可以表示：a，b，c，a-b，a--c，b-c，或a-b-c，其中a，b，c可以是单个，也可以是多个。
在多设备场景中，终端设备被划分为源端设备和对端设备，源端设备是发送端设备，对端设备是接收端设备。当源端设备和对端设备登陆了相同的账号，并且源端设备和对端设备处于同一局域网的情况下，通过用户触发接续条件，源端设备和对端设备上的应用可实现接续。例如，源端设备为电脑，对端设备为手机，用户在电脑和手机登陆了相同的账号，且电脑和手机处于同一局域网，若用户在电脑上的视频播放软件播放视频，用户的手机上的视频播放软件能同步播放该视频，若用户在电脑上正在编辑文本，用户的手机上可以同步显示正在编辑的文本。
为了便于理解本申请，下面结合图1对本申请实施例所涉及的应用场景进行介绍。
图1示出了本申请实施例的应用场景100的示意图。该应用场景包括第一终端设备101和第二终端设备102，其中，第一终端设备101可以作为源端设备，第二终端设备102可以作为对端设备，用户在第一终端设备101和第二终端设备102上登录了相同的账号，且第一终端设备101和第二终端设备102处于同一局域网，第一终端设备101可以将应用程序的内容接续到第二终端设备102上。
可选地，上述应用场景100还包括第三终端设备103。第三终端设备103也可以作为对端设备，用户在第三终端设备103上也登录了相同的账号，且第一终端设备101和第三终端设备103处于同一局域网，第一终端设备101可以将应用程序的内容接续到第三终端设备103上。
应理解，在多设备应用接续的场景中，对端设备(即接收端)的数量可以为一个或者多个，本申请实施例对此不作限定。
还应理解，本申请并不要求上述多个对端设备均与源端设备处于同一局域网下，例如，上述第一终端设备101和第二终端设备102可以处于一个局域网(例如WiFi)，第一终端设备101和第三终端设备103可以处于另一局域网(例如蓝牙)，第一终端设备101可以将应用程序上的内容分别接续到第二终端设备102和第三终端设备103。
为了更好的理解本申请实施例中的终端设备，下面对本申请实施例的终端设备的硬件结构进行介绍。
图2示出了终端设备200的结构示意图。
终端设备可以包括处理器210，外部存储器接口220，内部存储器221，通用串行总线(universal serial bus，USB)接口230，充电管理模块240，电源管理模块241，电池242，天线1，天线2，移动通信模块250，无线通信模块260，音频模块270，扬声器270A，受话器270B，麦克风270C，耳机接口270D，传感器模块280，按键290，马达291，指示器292，摄像头293，显示屏294，以及用户标识模块(subscriber identification module，SIM)卡接口295等。其中传感器模块280可以包括压力传感器280A，陀螺仪传感器280B，气压传感器280C，磁传感器280D，加速度传感器280E，距离传感器280F，接近光传感器280G，指纹传感器280H，温度传感器280J，触摸传感器280K，环境光传感器280L，骨 传导传感器280M等。
可以理解的是，本申请实施例示意的结构并不构成对终端设备的具体限定。在本申请另一些实施例中，终端设备可以包括比图示更多或更少的部件，或者组合某些部件，或者拆分某些部件，或者不同的部件布置。图示的部件可以以硬件，软件或软件和硬件的组合实现。
处理器210可以包括一个或多个处理单元，例如：处理器210可以包括应用处理器(application processor，AP)，调制解调处理器，图形处理器(graphics processing unit，GPU)，图像信号处理器(image signal processor，ISP)，控制器，视频编解码器，数字信号处理器(digital signal processor，DSP)，基带处理器，和/或神经网络处理器(neural-network processing unit，NPU)等。其中，不同的处理单元可以是独立的器件，也可以集成在一个或多个处理器中。
控制器可以根据指令操作码和时序信号，产生操作控制信号，完成取指令和执行指令的控制。
处理器210中还可以设置存储器，用于存储指令和数据。在一些实施例中，处理器210中的存储器为高速缓冲存储器。该存储器可以保存处理器210刚用过或循环使用的指令或数据。如果处理器210需要再次使用该指令或数据，可从上述存储器中直接调用。避免了重复存取，减少了处理器210的等待时间，因而提高了系统的效率。
在一些实施例中，处理器210可以包括一个或多个接口。接口可以包括集成电路(inter-integrated circuit，I2C)接口，集成电路内置音频(inter-integrated circuit sound，I2S)接口，脉冲编码调制(pulse code modulation，PCM)接口，通用异步收发传输器(universal asynchronous receiver/transmitter，UART)接口，移动产业处理器接口(mobile industry processor interface，MIPI)，通用输入输出(general-purpose input/output，GPIO)接口，用户标识模块(subscriber identity module，SIM)接口，和/或通用串行总线(universal serial bus，USB)接口等。
可以理解的是，本申请实施例示意的各模块间的接口连接关系，只是示意性说明，并不构成对终端设备的结构限定。在本申请另一些实施例中，终端设备也可以采用上述实施例中不同的接口连接方式，或多种接口连接方式的组合。
终端设备通过GPU，显示屏294，以及应用处理器等实现显示功能。GPU为图像处理的微处理器，连接显示屏294和应用处理器。GPU用于执行数学和几何计算，用于图形渲染。处理器210可包括一个或多个GPU，其执行程序指令以生成或改变显示信息。
终端设备可以通过ISP，摄像头293，视频编解码器，GPU，显示屏294以及应用处理器等实现拍摄功能。
外部存储器接口220可以用于连接外部存储卡，例如Micro SD卡，实现扩展终端设备的存储能力。外部存储卡通过外部存储器接口220与处理器210通信，实现数据存储功能。例如将音乐，视频等文件保存在外部存储卡中。
内部存储器221可以用于存储计算机可执行程序代码，可执行程序代码包括指令。内部存储器221可以包括存储程序区和存储数据区。其中，存储程序区可存储操作系统，至少一个功能所需的应用程序(比如声音播放功能，图像播放功能等)等。存储数据区可存储终端设备使用过程中所创建的数据(比如音频数据，电话本等)等。此外，内部存储器 221可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件，闪存器件，通用闪存存储器(universal flash storage，UFS)等。处理器210通过运行存储在内部存储器221的指令，和/或存储在设置于处理器中的存储器的指令，执行终端设备的各种功能应用以及数据处理。例如，可以执行本申请实施例的应用接续方法。
本申请的终端设备可以作为源端设备，也可以作为对端设备。源端设备也可以称为发送端，对端设备也可以称为接收端。终端设备的软件系统可以采用分层架构，事件驱动架构，微核架构，微服务架构，或云架构。本申请实施例的图3以分层架构的Android系统为例，示例性说明发送端和接收端的软件结构。
如图3所示，以发送端为例，分层架构将软件分成若干个层，每一层都有清晰的角色和分工。层与层之间通过软件接口进行数据的传输与通信。在一些实施例中，将Android系统分为五层，从上至下分别为应用程序层，应用程序框架层，安卓运行时(Android runtime)和系统库、硬件抽象层(hardware abstract layer，HAL)，以及内核层。
应用程序层可以包括一系列应用程序包。如图3所示，应用程序包可以包括三方应用、软件开发工具包(software development kit，SDK)、蓝牙、WIFI、备忘录、视频、游戏等应用程序。例如本申请实施例中，在应用程序层中，接续应用可以接入接续服务SDK，接续应用可以为终端设备中的系统应用，也可以为三方应用，备忘录、视频、游戏等应用也可以为系统应用或三方应用。
应用程序框架层为应用程序层的应用程序提供应用编程接口(application programming interface，API)和编程框架。应用程序框架层包括一些预先定义的函数。
如图3所示，应用程序框架层可以包括接续服务管理器、通信服务管理器、鉴权服务管理器、通知管理器、窗口管理器、资源管理器、内容提供器和视图系统等。其中，管理器在一些应用场景中也可以称为模块。
接续服务管理器可以负责接续任务的管理，可以为整体接续服务框架的核心。例如本申请实施例中，接续服务管理器可以负责接续应用的接入、接续应用的鉴权、接续应用的图标管理以及接续数据跨设备间的传输。
通信服务管理器可以用于实现跨设备间的数据传输，例如本申请实施例中，通信服务管理器可以实现同账号设备的安全认证与账号鉴权、设备的自发现与自组网、设备间的数据传输以及通信服务的接入等。
鉴权服务管理器可以负责应用的合法性校验，例如本申请实施例中，在鉴权服务管理器校验通过后可以允许应用接入接续服务。
通知管理器使应用程序可以在状态栏中显示通知信息，可以用于传达告知类型的消息，可以短暂停留后自动消失，无需用户交互。比如通知管理器被用于告知下载完成，消息提醒等。通知管理器还可以是以图表或者滚动条文本形式出现在系统顶部状态栏的通知，例如后台运行的应用程序的通知，还可以是以对话窗口形式出现在屏幕上的通知。例如在状态栏提示文本信息、发出提示音、终端设备振动、指示灯闪烁等。例如本申请实施例中，当终端设备接收到广播接续通知时，通知管理器可以在任务栏中显示广播接续通知。
窗口管理器用于管理窗口程序。窗口管理器可以获取显示屏大小，判断是否有状态栏、锁定屏幕、触摸屏幕、拖拽屏幕、截取屏幕等。
资源管理器为应用程序提供各种资源，例如本地化字符串、图标、图片、布局文件、 视频文件等等。
内容提供器用于在不同的应用程序之间实现数据共享的功能，允许一个程序访问另一个程序中的数据，同时还能保证被访问的数据的安全性。
视图系统可以负责应用程序的界面绘制和事件处理。例如本申请实施例中，视图系统可以用于处理用户点击接续应用的通知图标后的事件处理。
Android runtime包括核心库和虚拟机。Android runtime负责安卓系统的调度和管理。
核心库包含两部分：一部分是java语言需要调用的功能函数，另一部分是安卓的核心库。
应用程序层和应用程序框架层运行在虚拟机中。虚拟机将应用程序层和应用程序框架层的java文件执行为二进制文件。虚拟机用于执行对象生命周期的管理，堆栈管理，线程管理，安全和异常的管理，以及垃圾回收等功能。
系统库可以包括多个功能模块。例如：媒体库(Media Libraries)、函数库(Function Libraries)图形处理库(例如：OpenGL ES)等。
媒体库支持多种常用的音频，视频格式回放和录制，以及静态图像文件等。媒体库可以支持多种音视频编码格式，例如:MPEG4，H.264，MP3，AAC，AMR，JPG，PNG等。
函数库为开发者提供多种服务的API接口，方便开发者快速集成并实现各种功能。
图形处理库用于实现图形绘图、图像渲染、合成和图层处理等。
硬件抽象层是介于内核层和Android runtime之间的抽象出来的一层结构。硬件抽象层可以是对硬件驱动的一个封装，为上层应用的调用提供统一接口。硬件抽象层可以包括蓝牙模块、WIFI模块、硬件配置模块等。例如本申请实施例中，硬件抽象层中的蓝牙模块和WIFI模块可以屏蔽内核层中蓝牙驱动和WIFI驱动的具体硬件实现细节，上层应用在不必知道内核层硬件驱动的具体实现方式的情况下就可以通过调用接口实现蓝牙功能和WIFI功能。
内核层是硬件和软件之间的层。内核层可以包括显示驱动、摄像头驱动、音频驱动、蓝牙驱动、WiFi驱动、中央处理器驱动等。例如本申请实施例中，通信服务管理器可以通过蓝牙驱动以及WiFi驱动等相关模块进行跨设备间的连接，实现设备的自发现与自组网。
下面结合终端设备之间在应用接续过程中进行广播接续通知显示的场景，示例性说明Android系统分层框架中的接续数据的传输流程。
如图3所示，在发送端的应用程序层中，应用程序可以通过接入接续服务SDK实现与接续服务的数据传输。接续服务SDK可以向接续服务管理器发送绑定接续服务以及应用注册接续服务请求，进而实现应用程序层与应用程序框架层之间的接续应用注册与绑定的数据传输。
在应用程序框架层中，接续服务管理器可以通过与通信服务管理器进行信令传输与数据传输完成通信服务的绑定。接续服务管理器还可以与鉴权服务管理器进行绑定鉴权服务以及应用鉴权。
在接续应用注册成功后，通信服务管理器可以调用硬件抽象层提供的蓝牙模块接口以及WIFI模块接口实现设备的自发现与自组网，并通过内核层中的蓝牙驱动和WIFI驱动实现终端设备间的会话连接、消息传递，以及接续内容的传输等。
当接收端基于内核层接收到发送端传递过来的接续相关的数据后，可以将数据传输给 硬件抽象层中的相关模块。在接收端的应用程序框架层中，通信服务管理器可以通过硬件抽象层中提供的接口获取传输过来的接续数据，并与接续服务管理器进行信令传输与数据传输。接续服务管理器在接收到接续相关的数据后，可以与鉴权服务管理器进行绑定鉴权服务以及应用鉴权。进一步的，接续服务管理器可以指示桌面启动器以图标形式显示广播接续通知。
可以理解的是，本申请实施例的发送端或接收端也可以采用Windows系统，如图4所示，与Android系统不同的是Windows系统的分层架构主要分为用户态和内核态，用户态可以包括用户应用程序进程，以及系统进程与服务进程等；内核态可以包括内核和设备驱动层，以及硬件抽象层等。
用户应用程序进程可以执行一系列应用程序。具体可执行的应用程序类型可以与Android系统中应用程序层中的应用程序类型相同，在此不再赘述。
系统进程与服务进程中可以包括接续服务管理器、通信服务管理器、鉴权服务管理器、系统进程、通知管理器、窗口管理器等，可以为用户应用程序进程的执行提供相应服务。具体与本申请实施例相关的接续服务管理器、通信服务管理器、鉴权服务管理器等进程的作用可参见Android中的相关管理器描述，在此不再赘述。
内核层和设备驱动层可以包括蓝牙驱动、WiFi驱动、显示驱动等，硬件抽象层可以包括蓝牙模块、WIFI模块、硬件配置模块等。具体的功能模块的作用可参见Android中的相关描述，在此不再赘述。
下面将详细介绍本申请实施例的应用接续方法。下面的实施例可以相互结合或独立实施，对于相同或相似的概念或过程可能在某些实施例中不再赘述。本申请实施例将应用程序简称为“应用”。
图5是本申请实施例提供的一种应用接续方法500的示意性流程图。该方法500可以应用于上述场景100，该方法500所涉及的终端设备的硬件结构可以如图2所述，软件结构可以如图3或图4所示。第一终端设备可以对应于图3或图4的发送端，第二终端设备可以对应于图3或图4的接收端。
S501，第一终端设备向第二终端设备发送广播接续通知，对应地，第二终端设备接收来自第一终端设备的广播接续通知。
具体地，广播接续通知用于请求将第一终端设备的第一接续应用接续至第二终端设备。
S502，第二终端设备根据广播接续通知，确定第二接续应用。
具体地，广播接续通知中携带至少一个目标接续应用的设备类型，第二终端设备确定与第二终端设备的设备类型相同的目标接续应用为第二接续应用。
S503，第二终端设备对第二接续应用进行合法性鉴权和匹配关系校验，获得合法性鉴权结果和匹配关系校验结果。
S504，在合法性鉴权结果为合法性鉴权通过、且匹配关系校验结果为匹配关系校验通过的情况下，第二终端设备显示所述第二接续应用的接续触点。
本申请实施例的应用接续方法，通过第二终端设备上对第二接续应用进行合法性鉴权和匹配关系校验，在合法性鉴权和匹配关系检验均通过的情况下，在第二终端设备上显示第二接续应用的接续触点，能够避免将应用的内容接续到信任源不可靠的应用，提高应用接续的安全性，从而提高用户体验。
下面，详细描述本申请实施例的应用接续方法。
应用在开发完成之后需要在云服务器注册，向云服务器申请接续权限。
应理解，应用开发者可以通过开放平台进行注册和接续权限的申请。开放平台可以理解为开放平台的网页或者客户端，能够与云服务器进行通信。具体地，应用开发者可以通过自己的设备(例如平板、计算机、笔记本电脑等)登录自己的开发者账户，进入开放平台的开发者界面，通过填写应用的相关信息注册应用，并为该应用申请接续权限。开放平台的管理员可以通过自己的设备(例如平板、计算机、笔记本电脑等)登录自己的管理员账户，进入开放平台的管理员界面，对应用开发者提交的信息进行审核，并为该应用分配应用标识符(application identification，APPID)和接续权限。
图6是本申请实施例提供的一种开放平台的开发者界面的示意图。图7是本申请实施例提供的一种接续应用注册和申请接续权限的方法700的示意性流程图，下面结合图6和图7，详细介绍应用开发者在开放平台注册和申请接续权限的过程。
如图6所示，在图6的界面a中，应用开发者选择待注册应用的平台类型为“Andriod”、待注册应用的设备类型为“平板”、待注册应用的应用类型为工具类，输入待注册应用的应用包名为“Com.Beiwanglu”、待注册应用的用户标识(user identification，UID)为“5256XX1”、待注册应用的应用签名为“0e 56 46 74 4a”，并上传待注册应用的应用图标(即为图6中所示的六角星样式的图标)。然后，应用开发者点击“创建”按钮。如图7所示，响应于应用开发者的点击操作，开放平台向云服务器发送注册指令，该注册指令携带上述应用开发者选择和输入的相关信息。云服务器接收注册指令，根据上述应用开发者选择和输入的相关信息，向开放平台发送审核任务生成指令，该审核任务生成指令用于为开放平台的管理员账户生成审核任务。开放平台接收该审核任务生成指令，并基于该审核任务生成指令，在开放平台的管理员界面显示审核任务提示消息的按钮，开放平台的管理员点击该按钮查看审核任务，并对应用开发者选择和输入的相关信息进行资质审核，若资质审核通过，开放平台的管理员点击通过按钮，开放平台向云服务器发送审核通过指令。云服务器接收审核通过指令，为待注册应用分配APPID，并发送给开放平台。开放平台在收到待注册应用的APPID之后，将图6所示的界面a跳转为图6所示的界面b。
在图6所示的界面b中，应用开发者点击“申请接续权限”按钮，界面跳转至图6所示的界面c。图6所示的界面c显示有备忘录应用的平台类型“Andriod”、应用名称“备忘录”、APPID“123456”、应用包名“Com.Beiwanglu”、应用签名“0e 56 46 74 4a”、应用图标“六角星样式的图标”等注册信息，以及权限设置的选项。其中，权限设置包括三个选项：1，基础接续权限；2，国内应用市场接续；3，国外应用市场接续。应用的开发者点击选择“基础接续权限”和“国内应用市场接续”，点击“提交”按钮。如图7所示，响应于应用开发者的点击操作，开放平台向云服务器发送权限申请指令，向云服务器申请基础接续权限和国内应用市场接续权限。云服务器接收权限申请指令，该权限申请指令携带有上述平台类型、应用名称、APPID、应用包名、应用签名、应用图标、以及应用开发者选择的相关信息，基于该权限申请指令，云服务器向开放平台发送权限审批任务生成指令，该权限审批任务生成指令用于为开放平台的管理员账户生成权限审批任务。开放平台接收该权限审批任务生成指令，在开放平台的管理员界面显示权限审批任务提示消息的按钮，开放平台的管理员点击该按钮查看权限审批任务，并对应用开发者选择的接续权 限进行审批，若权限审批通过，开放平台的管理员点击通过按钮，开放平台向云服务器发送权限审批通过指令。云服务器接收权限审批通过指令，建立上述平台类型、应用名称、APPID、应用包名、应用签名、应用图标以及接续权限之间的关联关系，并进行存储。开放平台将图6所示的界面c跳转为图6所示的界面d。在图6所示的界面d中，开放平台在应用开发者的界面显示“权限审批成功”的弹窗。
应理解，对于资质审核，上述仅仅以资质审核通过的情况为例进行说明，若待注册应用的资质审核未通过，则云服务器不会为待注册应用分配APPID，图6所示的界面a不会跳转到图6所示的界面b，而是直接显示提示消息，提示应用开发者资质审核未通过。对于接续权限审批，上述仅仅以审批通过的情况为例进行说明，若待注册应用的接续权限审批未通过，则云服务器不会建立和存储上述关联关系，开放平台在开发者界面为应用开发者显示审批结果(即审批未通过)的提示消息。
需要说明的是，APPID为应用在云服务器进行注册的过程中，云服务器给应用分配的标识信息，UID为应用开发过程中被分配的标识信息。对于已注册的应用，其安装包中会携带APPID，终端设备可以通过安装该应用，从而解析并保存该应用的APPID。
在本申请实施例中，不同平台或不同类别设备的应用都需要进行上述图6所示的注册过程，这样，不同平台或不同类别设备的应用之间才能实现接续。例如，Andriod平台手机的备忘录A的开发者需要在云服务器注册备忘录A，为Andriod平台手机的备忘录A申请接续权限，获取Andriod平台手机的备忘录A的APPID 1；Andriod平台平板电脑的备忘录B的开发者需要在云服务器注册备忘录B，为Andriod平台平板电脑的备忘录B申请接续权限，获取Andriod平台平板电脑的备忘录B的APPID 2；Windows平台计算机的备忘录C的开发者还需要在云服务器注册备忘录C，为Windows平台计算机的备忘录C申请接续权限，获取Windows平台计算机的备忘录C的APPID 3。
针对Android平台的应用，在注册时应用开发者需要输入该应用在Android平台的包名、签名、图标、以及开发者等信息；针对Windows平台的应用，在注册时应用开发者需要输入该应用在Windows平台的进程名、注册表信息和安装目录、签名、图标、以及开发者等信息。
示例性地，表一示出了Android平台和Windows平台的各项信息的说明以及举例。
表一

在不同平台或不同类别设备的应用在云服务器进行了注册并申请了接续权限之后，可以建立应用之间的匹配关系，例如，Android平台手机的备忘录A和Android平台平板电脑的备忘录B之间的匹配关系，这样后续不同平台或不同类别设备的应用才能基于该匹配关系进行接续。
在本申请实施例中，可以通过多种不同的方式建立上述匹配关系。
在一种可能的实现方式中，应用的开发者可以向云服务器申请建立不同平台或不同类别设备的应用之间的匹配关系，例如，备忘录A的开发者可以向云服务器申请建立备忘录A与备忘录B之间的匹配关系。图8示出了本申请实施例提供的一种接续应用申请建立匹配关系的方法800的示意性流程图。
如图8所示，备忘录A的开发者在开放平台登录自己的开发者账户，在备忘录A在开放平台的开发者界面上输入目标接续备忘录B的平台类型、APPID、包名、签名、以及开发者等信息后，点击“申请”按钮。响应该点击操作，开放平台向云服务器发送申请指令，该申请指令携带备忘录A的APPID、备忘录B的APPID、包名以及签名等信息。云服务器接收该申请指令，对备忘录B的合法性进行鉴权，即根据申请指令中备忘录B的APPID查询云服务器存储的备忘录B的包名和签名，比较云服务器存储的备忘录B的包名和签名与申请指令中携带的备忘录B的包名和签名。在云服务器存储的备忘录B的包名和签名与申请指令中携带的备忘录B的包名和签名相同的情况下，云服务器认为备忘录B的合法性进行鉴权通过，向开放平台发送匹配关系建立请求，该匹配关系建立请求携带有备忘录A的平台类型、APPID、包名、签名、以及开发者等信息。备忘录A的平台类型、包名、签名、以及开发者等信息可以是云服务器基于之前的接续应用注册和申请接续权限过程查询得到的。开放平台接收该匹配关系建立请求，在备忘录B的开发者界面显示匹配关系建立请求消息，备忘录B的开发者在开放平台登录自己的开发者账户，通过点击操作同意或拒绝该匹配关系建立请求。响应于用户的点击操作，开放平台向云服务器发送同意或拒绝匹配关系建立的通知。云服务器接收该同意或拒绝匹配关系建立的通知。在该通知为同意匹配关系建立的情况下，云服务器建立并存储备忘录A和备忘录B之间的匹配关系，并向开放平台发送匹配关系建立成功的通知。开放平台接收该匹配关系建立成功的通知，在备忘录A的开发者界面显示匹配关系建立成功的通知提醒。否则，云服务器不建立备忘录A和备忘录B匹配关系，并在备忘录A的开发者界面显示匹配关系建立失败的通知提醒。
在另一种可能的实现方式中，应用开发者可以预先在应用的安装包中定义该应用的匹配关系，用户在终端设备上安装该应用时，该终端设备可以直接存储该应用的匹配关系。例如，应用开发者可以预先在应用的相关文件中描述本应用所信任的其他应用(后续称为目标接续应用)的APPID，并建立本应用与目标接续应用之间的匹配关系。
示例性地，针对Android应用，应用的开发者可以通过AndroidManifest.xml清单文件中的Metadata对目标接续应用进行描述，针对Windows应用，应用的开发者可以通过本应用的注册表值项对目标接续应用进行描述。
示例性地，备忘录A和备忘录B均为Android应用，备忘录A的APPID为123456，备忘录B的APPID为654321。备忘录A的开发者在备忘录A的AndroidManifest.xml清单 文件中的元数据(metadata)描述如下：
<meta-data android:name＝“com.xxx.xxx.client.appid”android:value＝“123456”/>
<meta-data android:name＝“com.xxx.xxx.allowstart.appids”android:value＝“654321”/>。
该描述表示，备忘录A信任的目标接续应用包括备忘录B，即备忘录A和备忘录B之间具备匹配关系。
当用户在手机上安装备忘录A时，手机可以解析A应用的安装包，得到备忘录A与备忘录B的匹配关系，并将该匹配关系存储在手机上的系统注册模块。
上面介绍了应用的权限申请和匹配关系建立的过程。下面将结合各模块之间的交互过程，详细说明本申请的应用接续方法。
本申请的应用接续方法可以分为三个阶段，第一阶段为接续应用的注册与绑定，第二阶段为接续通知的显示、第三阶段为接续数据的获取与加载。
实现跨设备间的应用接续方法的系统中可以包括第一终端设备、第二终端设备以及云服务器，第一终端设备可以对应于图3或图4的发送端，第二终端设备可以对应于图3或图4的接收端。第一终端设备与第二终端设备中均可以包括实现接续服务的各个功能模块，例如，可以包括接续服务SDK、接续服务管理器、通信服务管理器，以及鉴权服务管理器等。云服务器中可以包括实现接续服务的功能模块，例如，通信服务管理器、鉴权服务模块、以及匹配校验模块。
为了便于描述，后续将第一终端设备的接续应用称为第一接续应用，第一终端设备的接续服务SDK称为第一接续服务SDK，第一终端设备的接续服务管理器称为第一接续服务管理器，第一终端设备的通信服务管理器称为第一通信服务管理器，第一终端设备的鉴权服务管理器称为第一鉴权服务管理器。
将第二终端设备的接续应用称为第二接续应用，第二终端设备的接续服务SDK称为第二接续服务SDK，第二终端设备的接续服务管理器称为第二接续服务管理器，第二终端设备的通信服务管理器称为第二通信服务管理器，第二终端设备的鉴权服务管理器称为第二鉴权服务管理器，第二终端设备的桌面启动器称为桌面启动器。
将云服务器的通信服务管理器称为第三通信服务管理器，云服务器的鉴权服务模块称为第三鉴权服务模块，云服务器的匹配校验模块称为匹配校验模块。
首先，结合图9介绍第一阶段：接续应用的注册与绑定。图9为本申请实施例提供的接续应用的注册与绑定的方法900的示意性流程图。该方法900可以包括下列步骤。
S901，第一接续应用判断当前接续场景是否为第一有效接续场景。
S902，在当前接续场景为第一有效接续场景的情况下，第一接续应用向第一接续服务SDK发送注册接续服务请求，该注册接续服务请求中携带第一接续应用的UID和APPID；对应地，第一接续服务SDK收到该注册接续服务请求。
具体地，第一有效接续场景是根据第一接续应用上的用户行为判断的。第一接续应用上集成了第一接续服务SDK，当第一终端设备的第一接续应用监控到一些用户行为时，第一接续应用可以通过调用第一接续服务SDK的注册接口接入接续服务。用户行为可以为用户点击第一接续应用图标启动应用，也可以为用户在第一接续应用中进行编辑等操作，还可以为用户在第一接续应用中点击播放按钮进行视频播放、音乐播放或其他媒体播放等操作，具体所监控的用户行为可以由接续应用进行自定义设置，本申请实施例在此不做限 制。
示例性地，当第一接续应用是备忘录时，在一种可能的实现方式中，该备忘录的第一有效接续场景可以为：响应于用户在备忘录的应用图标上的点击操作，备忘录应用处于启动状态；在另一种可能的实现方式中，该备忘录的第一有效接续场景还可以为：响应于用户在备忘录的输入操作，备忘录当前处于编辑状态。
S903，第一接续服务SDK向第一接续服务管理器发送注册接续服务请求，对应地，第一接续服务管理器接收该注册接续服务请求。
S904，第一接续服务管理器向第一鉴权服务管理器发送第一合法性鉴权请求，对应地，第一鉴权服务管理器接收该第一合法性鉴权请求。
具体地，第一合法性鉴权请求用于请求对第一接续应用进行鉴权，第一合法性鉴权请求中携带第一接续应用的UID(或进程信息)和APPID。
S905，第一鉴权服务管理器基于该第一合法性鉴权请求，确定第一接续应用的本地标识信息。
具体地，第一鉴权服务管理器可以根据第一合法性鉴权请求中第一接续应用的UID(或进程信息)确定第一接续应用的本地标识信息，该本地标识信息包括第一接续应用的包名(或进程名)和签名。
示例性地，当第一接续应用为Andriod平台的应用时，第一鉴权服务管理器可以根据第一接续应用的UID确定第一接续应用的本地标识信息，该本地标识信息包括第一接续应用的包名和签名。当第一接续应用为Windows平台的应用时，第一鉴权服务管理器可以根据第一接续应用的进程信息确定第一接续应用的本地标识信息，该本地标识信息包括第一接续应用的进程名和签名。
S906，第一鉴权服务管理器向第一通信服务管理器发送第一合法性鉴权请求，对应地，第一通信管理器接收该第一合法性鉴权请求。
S907，第一通信服务管理器向第三通信服务管理器发送第一合法性鉴权请求，对应地，第三通信服务管理器接收该第一合法性鉴权请求。
S908，第三通信服务管理器向第三鉴权服务模块发送第一合法性鉴权请求，对应地，第三鉴权服务模块接收该第一合法性鉴权请求。
S909，第三鉴权服务模块基于该第一合法性鉴权请求，获取第一接续应用的云端标识信息。
具体地，第三鉴权服务模块可以根据第一合法性鉴权请求中第一接续应用的APPID获取第一接续应用的云端标识信息，该云端标识信息包括第一接续应用的包名(或进程名)和签名。
应理解，该云端标识信息是第一接续应用在上述接续权限的申请过程中云服务器保存的。
S910，第三鉴权服务模块向第三通信服务管理器发送第一接续应用的云端标识信息，对应地，第三通信服务管理器接收第一接续应用的云端标识信息。
S911，第三通信服务管理器向第一通信服务管理器发送第一接续应用的云端标识信息，对应地，第一通信服务管理器接收到第一接续应用的云端标识信息。
S912，第一通信服务管理器向第一鉴权服务管理器发送第一接续应用的云端标识信息， 对应地，第一鉴权服务管理器接收到第一接续应用的云端标识信息。
S913，第一鉴权服务管理器比较第一接续应用的云端标识信息和本地标识信息，根据云端标识信息和本地标识信息是否匹配，确定第一接续应用的合法性鉴权结果。
应理解，合法性鉴权结果可以包括鉴权通过和鉴权未通过，这里的匹配可以为相同，当云端标识信息和本地标识信息相同时，第一鉴权服务管理器确定第一接续应用的合法性鉴权通过，否则，第一鉴权服务管理器确定第一接续应用的合法性鉴权未通过。
S914，第一鉴权服务管理器向第一接续服务管理发送第一接续应用的合法性鉴权结果，对应地，第一接续服务管理接收到第一接续应用的合法性鉴权结果。
S915，第一接续服务管理向第一接续应用发送第一接续应用的合法性鉴权结果，对应地，第一接续应用接收到第一接续应用的合法性鉴权结果。
应理解，在第一接续应用的合法性鉴权结果为鉴权通过的情况下，第一接续应用的接续服务注册成功，第一接续应用具备发送广播接续通知的能力；否则，第一接续应用的接续服务注册失败，第一接续应用不具备发送广播接续通知的能力。
还应理解，上述的S905可以S904之后、S913之前的时间段内执行，本申请对此不作限定。
在第一接续应用接续服务注册成功之后，第一通信服务管理器与第二通信服务管理器可以通过蓝牙或者WIFI进行自发现与自组网，以及进行账号鉴权。进一步地，第一通信服务管理器可以向第一接续服务管理器发送用于表示第二终端设备上线的信息。例如，用于表示第二终端设备上线的信息可以包括第二终端设备的设备标识(device identification，DevID)等信息。
在第一接续服务管理器接收到第一通信服务管理器发送的用于表示第二终端设备上线的信息后，可以将第二终端设备的信息进行存储与管理，以便执行进行后续的应用接续的流程。
接着，结合图10或图11介绍第二阶段：接续通知的显示。图10为本申请实施例提供的一种接续通知的显示方法1000的示意性流程图。该方法1000可以包括下列步骤：
S1001，第一接续应用判断当前接续场景是否为第二有效接续场景。
具体地，该第二有效接续场景与上述第一有效接续场景类似，此处不再赘述。第二有效接续场景与上述第一有效接续场景可以相同，也可以不同，本申请对此不作限定。
在一种可能的实现方式中，第二有效接续场景和第一有效接续场景可以均为第一接续应用处于启动状态。在另一种可能的实现方式中，上述第一有效接续场景可以为第一接续应用处于启动状态，第二有效接续场景可以为第一接续应用处于编辑状态。
S1002，在当前接续场景为第二有效接续场景的情况下，第一接续应用向第一接续服务SDK发送广播接续通知，对应地，第一接续服务SDK接收该广播接续通知。
具体地，该广播接续通知可以携带第一接续应用的APPID和接续策略。
应理解，接续策略用于确定可接续的设备，各应用程序可以对应各自的接续策略。示例性地，应用程序的接续策略可以与下述的一项或多项字段有关：
接续状态标识、应用程序支持的设备类型、目标接续应用的APPID、目标接续应用的包名或进程名、第二接续应用的应用市场上架策略、浏览器启动参数、支持接续的最小版本等。
接续状态标识可以为用于标识接续策略状态的标志位。例如，标志位为0可以表示不支持接续，标志位为1可以表示应用接续，标志位为3可以表示浏览器接续。可以理解的是，标志位的具体值可以任意设置，能够区分不同的状态即可，本申请实施例不作具体限定。
示例性地，当接续策略为包括应用程序所支持的设备类型时，例如，接续策略中包括第二接续应用可以支持在手机、平板电脑、电视、电脑等上实现接续服务，则第一接续服务管理器在确认第二终端设备为手机、平板电脑、电视或电脑等时，第一接续服务管理器可以指示第一通信服务管理器和第二通信服务管理器建立会话通路。
若目标接续应用为Android平台的应用，则接续策略包括目标接续应用在Android平台的包名；若目标接续应用为Windows平台的应用，则接续策略包括目标接续应用在Windows平台的可接续进程名。
应用市场上架策略可以为下列任一种：未上架、海外应用市场1、国内应用市场1、国内应用市场2、海外应用市场2。
支持接续应用的最小版本可以用支持接续应用的最小版本号表示，用于表示第二接续应用可接续时的最小版本。示例性地，接续策略中包括第一接续应用可以支持最小版本号为V1.5，或最小版本为15，则第一接续服务管理器在确认第二接续应用的版本号大于或等于V1.5时，或者第二接续应用的版本大于或等于15时，第一接续服务管理器可以指示第一通信服务管理器和第二通信服务管理器建立会话通路。
应理解，目标接续应用的数量可以为至少一个，例如，当第一终端设备设备与包括第二终端设备的多个终端设备设备同处于同一局域网，且登录了相同的账号时，广播接续通知中可以有多个目标接续应用。
示例性地，用户在手机、平板电脑和计算机上登录了同一账号，若手机、平板电脑和计算机处于同一局域网，手机端作为发送端(即上述第一终端设备)，可以识别出平板电脑、计算机在线，手机端的备忘录A向平板电脑和计算机发送上述广播接续通知时，该广播接续通知包括的目标接续应用为平板电脑的备忘录B和计算机的备忘录C。
当目标接续应用包括平板电脑的备忘录B和计算机的备忘录C时，广播接续通知中接续策略携带的内容如下：

S1003，第一接续服务SDK向第一接续服务管理器发送广播接续通知，对应地，第一接续服务管理器接收该广播接续通知。
S1004，第一接续服务管理器向第一通信服务管理器发送广播接续通知，对应地，第一通信服务管理器接收该广播接续通知。
S1005，第一通信服务管理器向第二通信服务管理器发送该广播接续通知，对应地，第二通信服务管理器接收该广播接续通知。
S1006，第二通信服务管理器向第二接续服务管理器发送该广播接续通知，对应地，第二接续服务管理器接收该广播接续通知。
S1007，第二接续服务管理器基于广播接续通知，确定第二接续应用。
具体地，广播接续通知中携带有目标接续应用的设备类型信息，第二接续服务管理器可以根据目标接续应用和第二终端设备的设备类型信息，从目标接续应用中确定第二接续应用。
示例性地，当目标接续应用包括平板电脑的备忘录B和计算机的备忘录C，第二终端设备为平板电脑时，第二接续服务管理器可以确定平板电脑的备忘录B为第二接续应用。
S1008，第二接续服务管理器判断第二终端设备是否安装第二接续应用。
具体地，第二接续服务管理器可以查询第二终端设备中是否包括第二接续应用的包名/进程名，当第二终端设备中包括有第二接续应用的包名/进程名时，可以确定第二终端设备已安装第二接续应用。
S1009，在第二终端设备已安装第二接续应用的情况下，第二接续服务管理器向第二鉴权服务管理器发送第二合法性鉴权请求和匹配关系校验请求，对应地，第二鉴权服务管理器接收第二合法性鉴权请求和匹配关系校验请求。
具体地，第二合法性鉴权请求用于请求对第二接续应用进行鉴权，第二合法性鉴权请求中携带有第二接续应用的APPID。匹配关系校验请求用于请求校验第一接续应用的匹配关系，该匹配关系校验请求携带有第一接续应用的APPID。
应理解，在第二终端设备未安装第二接续应用的情况下，第二接续服务管理器可以指示第二终端设备安装第二接续应用。
S1010，第二鉴权服务管理器向第二通信服务管理器发送第二合法性鉴权请求，对应 地，第二通信服务管理器接收第二合法性鉴权请求。
S1011，第二通信服务管理器向第三通信服务管理器发送第二合法性鉴权请求，对应地，第三通信服务管理器接收第二合法性鉴权请求。
S1012，第三通信服务管理器向第三鉴权服务模块发送第二合法性鉴权请求，对应地，第三鉴权服务模块接收第二合法性鉴权请求。
S1013，第三鉴权服务模块根据第二合法性鉴权请求获取第二接续应用的云端标识信息。
应理解，云端标识信息包括第二接续应用的在云服务器存储的包名(或进程名)和签名。
S1014，第三鉴权服务模块向第三通信服务管理器返回云端标识信息，对应地，第三通信服务管理器接收云端标识信息。
S1015，第三通信服务管理器向第二通信服务管理器返回云端标识信息，对应地，第二通信服务管理器接收云端标识信息。
S1016，第二通信服务管理器向第二鉴权服务管理器返回云端标识信息，对应地，第二鉴权服务管理器接收云端标识信息。
S1017，第二鉴权服务管理器比较云端标识信息和本地标识信息，根据云端标识信息和本地标识信息是否匹配，确定第二接续应用的合法性鉴权结果。
具体地，本地标识信息为第二接续应用在第二终端设备上存储的包名(或进程名)和签名，广播接续通知中携带第二接续应用的包名/进程名，第二鉴权服务管理器可以通过第二接续应用的包名/进程名获取第二接续应用的签名。
示例性地，当第二接续应用为Andriod平台应用时，第二鉴权服务管理器可以通过第二接续应用的包名获取第二接续应用的签名。当第二接续应用为Windows平台应用时，第二鉴权服务管理器可以通过第二接续应用的进程名，从注册表信息RegRoot和RegKey中获取第二接续应用的安装路径，拼接“ImagePath”所描述的相对路径后，找到第二接续应用的主进程，然后读取第二接续应用的的签名。
应理解，第二接续应用的合法性鉴权结果与上述第一接续应用的合法性鉴权结果类似，此处不再赘述。
S1018，第二鉴权服务管理器向第二通信服务管理器发送匹配关系校验请求，对应地，第二通信服务管理器接收匹配关系校验请求。
S1019，第二通信服务管理器基于匹配关系校验请求，向第三通信服务管理器发送的匹配关系查询请求，对应地，第三通信服务管理器接收匹配关系查询请求。
具体地，该匹配关系查询请求携带有第一接续应用的APPID。
S1020，第三通信服务管理器向匹配校验模块发送的匹配关系查询请求，对应地，匹配校验模块接收匹配关系查询请求。
S1021，匹配校验模块基于匹配关系查询请求，查询得到第一匹配关系。
应理解，通过上述在云服务器建立应用之间匹配关系的方法，匹配校验模块存储有应用之间的匹配关系。第一接续应用可以与至少一个接续应用之间存在匹配关系，也可以不存在匹配关系，本申请对此不做限制。
具体地，匹配校验模块可以根据第一接续应用的APPID，查询与第一接续应用具有的 匹配关系的应用，得到与第一接续应用存在匹配关系的至少一个应用。
S1022，匹配校验模块向第三通信服务管理器返回第一匹配关系，对应地，第三通信服务管理器接收第一匹配关系。
S1023，第三通信服务管理器向第二通信服务管理器返回第一匹配关系，对应地，第二通信服务管理器接收第一匹配关系。
S1024，第二通信服务管理器向第二鉴权服务管理器返回第一匹配关系，对应地，第二鉴权服务管理器接收第一匹配关系。
S1025，第二鉴权服务管理器基于第一匹配关系，进行匹配关系校验，即判断第一接续应用和第二接续应用之间是否存在匹配关系。
具体地，第一匹配关系包括两种情况，基于第一匹配关系进行匹配关系校验也包括两种情况：
在一种情况下，第一匹配关系用于表示能够与第二接续应用进行接续的至少一个应用。在这种情况下，判断第一接续应用和第二接续应用之间是否存在匹配关系可以为：判断与第二接续应用存在匹配关系的至少一个应用是否包括第一接续应用。当与第二接续应用存在匹配关系的至少一个应用中包括第一接续应用，则认为第一接续应用和第二接续应用之间存在匹配关系，匹配关系校验通过，否则，认为第一接续应用和第二接续应用之间不存在匹配关系，匹配关系校验未通过。
在另一种情况下，第一匹配关系用于表示能够与第一接续应用进行接续的至少一个应用。在这种情况下，判断第一接续应用和第二接续应用之间是否存在匹配关系可以为：判断与第一接续应用存在匹配关系的至少一个应用是否包括第二接续应用。当与第一接续应用存在匹配关系的至少一个应用中包括第二接续应用，则认为第一接续应用和第二接续应用之间存在匹配关系，匹配关系校验通过，否则，认为第一接续应用和第二接续应用之间不存在匹配关系，匹配关系校验未通过。
S1026，第二鉴权服务管理器向第二接续服务管理器返回合法性鉴权结果和匹配关系校验结果，对应地，第二接续服务管理器接收合法性鉴权结果和匹配关系校验结果。
具体地，合法性鉴权结果包括鉴权通过或鉴权未通过，匹配关系校验结果包括校验通过或校验为通过。
S1027，在合法性鉴权结果和匹配关系校验结果均通过的情况下，第二接续服务管理器向桌面启动器发送显示接续触点的指令。
S1028，桌面启动器控制显示第二接续应用的接续触点。该接续触点可以以第二接续应用的图标的形式显示。
应理解，上述S1011至S1017的步骤与S1018至S1025的步骤顺序不分先后，可以同时执行，也可以先执行S1018至S1025，再执行S1011至S1017，本申请实施例对此不作限定。
图10示出了应用之间的匹配关系建立并存储在云服务器的接续通知的显示流程。若应用开发者预先在第二接续应用的安装包中定义了第二接续应用与其他应用之间的匹配关系，则第二终端设备在安装了第二接续应用之后就可以获得上述第一匹配关系，无需向云服务器查询。下面结合图10对这种情况的接续通知的显示流程进行介绍。
图11是本申请实施例提供的另一接续通知的显示方法1100的示意性流程图。在第二 终端设备的软件结构的应用程序框架层还包括系统注册管理器，用于存储应用在接续时的匹配关系。
该方法1100和上述方法1000类似，其中，S1101至S1117与上述S1001至S1017步骤相同，此处不再赘述。
S1118，第二鉴权服务管理器向系统注册管理器发送匹配关系校验请求，对应地，系统注册管理器接收匹配关系校验请求。
S1119，系统注册管理器基于匹配关系校验请求，查询得到第二匹配关系。
应理解，应用开发者预先在第二接续应用的安装包中定义了第二接续应用与其他应用之间的匹配关系(即第二匹配关系)，第二终端设备在安装第二接续应用时，解析第二接续应用的安装包，得到第二匹配关系，并将第二匹配关系存储在系统注册管理器。
S1120，系统注册管理器向第二鉴权服务管理器发送第一匹配关系，对应地，第二鉴权服务管理器接收第二匹配关系。
S1121，第二鉴权服务管理器基于第二匹配关系，进行匹配关系校验，即判断第一接续应用和第二接续应用之间是否存在匹配关系。
具体地，第二匹配关系用于表示能够与第二接续应用进行接续的至少一个应用。判断第一接续应用和第二接续应用之间是否存在匹配关系可以为：判断与第二接续应用存在匹配关系的至少一个应用是否包括第一接续应用。当与第二接续应用存在匹配关系的至少一个应用中包括第一接续应用，则认为第一接续应用和第二接续应用之间存在匹配关系，匹配关系校验通过，否则，认为第一接续应用和第二接续应用之间不存在匹配关系，匹配关系校验未通过。
S1122～S1124与上述S1026～S1028步骤相同，此处不再赘述。
最后，结合图12介绍第三阶段：接续数据的获取与加载。
图12是本申请实施例提供的接续数据的获取与加载方法1200的示意性流程图。方法1200包括以下步骤：
S1201，桌面启动器响应于用户的点击接续触点的操作，向第二接续服务管理器发送事件触发指令。
S1202，第二接续服务管理器可以拉起第二接续应用，指示第二接续应用加载过渡动画效果。
S1203，第二接续应用可以启动并加载过渡动效。
具体地，过渡动效例如可以包括“加载中…”等提示信息。
S1204，第二接续应用调用第二接续服务SDK注册接续服务和回调。
应理解，第二接续应用在注册接续服务时可以携带第二接续应用的应用包名等信息。
S1205，第二接续服务SDK向第二接续服务管理器发送绑定接续服务的请求，对应地，第二接续服务管理器接收绑定接续服务的请求。
S1206，第二接续服务管理器向第二通信服务管理器发送绑定通信服务的请求，对应地，第二通信服务管理器接收绑定通信服务的请求。
S1207，第二通信服务管理器绑定成功后，第二通信服务管理器向第二接续服务管理器发送绑定成功的消息，对应地，第二接续服务管理器接收绑定成功的消息。
S1208，第二接续服务管理器向第二接续服务SDK发送绑定成功的消息，对应地，第 二接续服务SDK接收绑定成功的消息。
S1209，第二接续服务SDK向第二接续服务管理器发送注册接续服务和回调的请求，对应地，第二接续服务管理器接收注册接续服务和回调的请求。
S1210，第二接续服务管理器注册成功后，向第二接续服务SDK发送注册成功的消息，对应地，第二接续服务SDK接收注册成功的消息。
S1211，第二接续服务SDK向第二接续应用发送注册成功的消息，对应地，第二接续应用接收注册成功的消息。
S1212，在S1201之后，第二接续服务管理器向第二通信服务管理器发送接续数据请求，对应地，第二通信服务管理器接收该接续数据请求。
S1213，第二通信服务管理器向第一通信管理服务器发送接续数据请求，对应地，第一通信管理服务器接收接续数据请求。
S1214，第一通信管理服务器向第一接续服务管理器发送接续数据请求，对应地，第一接续服务管理器接收接续数据请求。
S1215，第一接续服务管理器向第一接续服务SDK发送接续数据请求，对应地，第一接续服务SDK接收接续数据请求。
S1216，第一接续服务SDK向第一接续应用发送接续数据请求，对应地，第一接续应用接收接续数据请求。
S1217，第一接续应用将接续数据打包加密。
S1218，第一接续应用向第一接续服务SDK发送接续数据，对应地，第一接续服务SDK接收接续数据。
S1219，第一接续服务SDK向第一接续服务管理器发送接续数据，对应地，第一接续服务管理器接收接续数据。
S1220，第一接续服务管理器向第一通信管理服务器发送接续数据，对应地，第一通信管理服务器接收接续数据。
S1221，第一通信管理服务器向第二通信服务管理器发送接续数据，对应地，第二通信服务管理器接收接续数据。
S1222，第二通信服务管理器向第二接续服务管理器发送接续数据，对应地，第二接续服务管理器接收该接续数据。
S1223，第二接续服务管理器向第二接续应用发送接续数据，对应地，第二接续应用接收接续数据。
S1224，第二接续应用加载并显示接续数据。
S1225，第二接续应用向第二接续服务SDK发送接续成功消息，对应地，第二接续服务SDK接收接续成功消息。
S1226，第二接续服务SDK向第二接续服务管理器发送接续成功消息，对应地，第二接续服务管理器接收接续成功消息。
S1227，第二接续服务管理器向第二通信服务管理器发送接续成功消息，对应地，第二通信服务管理器接收接续成功消息。
S1228，第二通信服务管理器向第一通信管理服务器发送接续成功消息，对应地，第一通信管理服务器接收接续成功消息。
S1229，第一通信管理服务器向第一接续服务管理器发送接续成功消息，对应地，第一接续服务管理器接收接续成功消息。
S1230，第一接续服务管理器向第一接续服务SDK发送接续成功消息，对应地，第一接续服务SDK接收接续成功消息。
S1231，第一接续服务SDK向第一接续应用发送接续成功消息，对应地，第一接续应用接收接续成功消息。
S1232，第一接续应用退出接续页面。
需要说明的是，在本申请实施例的应用接续方法中，如果第一接续应用已经注册和绑定过接续服务，则当第一终端设备的第一接续应用监控到一些用户行为时，第一接续应用则不需要重新注册接续服务，或理解为不需要执行上述的方法900，第一接续应用可以直接执行方法1000或1100，以及方法1200等，此处不再赘述。
上述图9至图12所示的方法可以应用于图1所示的应用场景100，所涉及的终端设备的硬件结构可以如图2所示，软件结构可以如图3或图4所示，但本申请实施例不限于此。
上面结合图9至图12介绍了本申请提供的应用接续方法的整体流程，下面结合图13和图14对应用接续的方法中第一终端设备和第二终端设备的应用接续界面进行介绍。
下面，以第一终端设备(即源端设备)为手机、第二终端设备(即对端设备)为平板电脑，且接续应用为备忘录为例，进行示例性说明。手机和平板电脑处于同一局域网下，且手机的备忘录和平板电脑的备忘录登录了同一账号。
图13为本申请提供的应用接续方法中源端设备界面示意图，用于介绍手机作为源端设备响应用户操作的界面，在图13所示的界面中，用户正在手机的备忘录上编辑文本，手机相应地显示用户所编辑的文本，光标的位置随用户编辑的位置而改变。手机的备忘录处于编辑状态，手机向平板电脑发送手机备忘录的广播接续通知。
图14是本申请实施例提供的对端设备的一种界面变化示意图，用于介绍平板电脑作为对端设备响应用户操作的界面变化。在图14的界面a中，平板电脑的桌面下方显示最近任务栏，最近任务栏中包括备忘录图标和其他多个应用图标。平板电脑接收来自手机的广播接续通知，在最近任务栏中的备忘录图标右上角显示触点(如图14中的黑色圆点)，以提示用户来自手机的备忘录想要与平板电脑的备忘录接续。用户点击上述触点，平板电脑响应于用户的点击操作，显示图14的界面b。在图14的界面b中，显示备忘录的页面，并在该备忘录页面上显示“正在加载接续内容”，内容加载之后，显示图14的界面c。在图14的界面c中，显示与手机相同的备忘录内容及相同的光标位置。
上文结合图6至图14，详细描述了本申请实施例的应用接续方法，下面将结合图15和图16，详细描述本申请实施例的终端设备。
图15是本申请实施例提供的终端设备1500，该终端设备1500包括：处理模块1501和收发模块1502。该终端设备1500用于实现上述方法中第二终端设备对应的步骤。
收发模块1502用于：接收来自第一终端设备的广播接续通知，广播接续通知用于请求将第一终端设备的第一接续应用接续至终端设备；处理模块1501用于：根据广播接续通知，确定第二接续应用，并对第二接续应用进行合法性鉴权和匹配关系校验，获得合法性鉴权结果和匹配关系校验结果；在合法性鉴权结果为合法性鉴权通过、且匹配关系校验结果为匹配关系校验通过的情况下，显示第二接续应用的接续触点。
可选地，上述广播接续通知包括：第一接续应用的应用标识符APPID和接续策略；其中，接续策略包括下列至少一种：接续状态标识、至少一个目标接续应用的包名或进程名、至少一个目标接续应用的设备类型、至少一个目标接续应用的应用市场上架策略以及支持接续的最小版本；至少一个目标接续应用包括第二接续应用。
可选地，处理模块1501还用于：基于至少一个目标接续应用的设备类型，将至少一个目标接续应用中与终端设备的设备类型相同的应用确定为第二接续应用。
可选地，收发模块1502还用于：向云服务器发送合法性鉴权请求，合法性鉴权请求携带第二接续应用的APPID；接收来自云服务器的第二接续应用的云端标识信息，云端标识信息包括云服务器存储的第二接续应用的包名和/或签名；处理模块1501还用于：将云端标识信息和第二接续应用的本地标识信息进行比较，获得合法性鉴权结果，本地标识信息为终端设备本地存储的第二接续应用的包名和/或签名。
可选地，收发模块1502还用于：向云服务器发送匹配关系查询请求，匹配关系查询请求携带第二接续应用的APPID；接收来自云服务器的第一匹配关系，第一匹配关系用于表示能够与第二接续应用进行接续的至少一个应用；处理模块1501还用于：基于第一匹配关系，判断至少一个应用是否包括第一接续应用，获得匹配关系校验结果。
可选地，收发模块1502还用于：向云服务器发送匹配关系查询请求，匹配关系查询请求携带第一接续应用的APPID；接收来自云服务器的第一匹配关系，第一匹配关系用于表示能够与第一接续应用进行接续的至少一个应用；处理模块1501还用于：基于第一匹配关系，判断至少一个应用是否包括第二接续应用，获得匹配关系校验结果。
可选地，处理模块1501还用于：获取第二匹配关系，第二匹配关系用于表示能够与第二接续应用进行接续的至少一个应用，第二匹配关系是终端设备在安装第二接续应用时预先存储在本地的；基于第二匹配关系，判断至少一个应用是否包括第一接续应用，获得匹配关系校验结果。
可选地，收发模块1502还用于：响应于用户对接续触点的点击操作，向第一终端设备发送接续数据请求消息；接收来自第一终端设备的接续数据，并显示接续数据。
应理解，这里的终端设备1500以功能模块的形式体现。这里的术语“模块”可以指应用特有集成电路(application specific integrated circuit，ASIC)、电子电路、用于执行一个或多个软件或固件程序的处理器(例如共享处理器、专有处理器或组处理器等)和存储器、合并逻辑电路和/或其它支持所描述的功能的合适组件。在一个可选例子中，本领域技术人员可以理解，终端设备1500可以具体为上述实施例中的第二终端设备，终端设备1500可以用于执行上述方法实施例中与第二终端设备对应的各个流程和/或步骤，为避免重复，在此不再赘述。
上述终端设备1500具有实现上述方法中第二终端设备执行的相应步骤的功能；上述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。例如，上述收发模块1502可以包括发送模块和接收模块，该发送模块可以用于实现上述收发模块对应的用于执行发送动作的各个步骤和/或流程，该接收模块可以用于实现上述收发模块对应的用于执行接收动作的各个步骤和/或流程。该发送模块可以由发射器替代，该接收模块可以由接收器替代，分别执行各个方法实施例中的收发操作以及相关的处理操作。
在本申请的实施例，图15中的终端设备1500也可以是芯片或者芯片系统，例如：片上系统(system on chip，SOC)。对应的，收发模块1502可以是该芯片的收发电路，在此不做限定。
图16是本申请实施例提供的另一种终端设备1600。该终端设备1600包括处理器1601、收发器1602和存储器1603。其中，处理器1601、收发器1602和存储器1603通过内部连接通路互相通信，该存储器1603用于存储指令，该处理器1601用于执行该存储器1603存储的指令，以控制该收发器1602发送信号和/或接收信号。
应理解，终端设备1600可以具体为上述实施例中的第二终端设备，并且可以用于执行上述方法实施例中与第二终端设备对应的各个步骤和/或流程。可选地，该存储器1603可以包括只读存储器和随机存取存储器，并向处理器提供指令和数据。存储器的一部分还可以包括非易失性随机存取存储器。例如，存储器还可以存储设备类型的信息。该处理器1601可以用于执行存储器中存储的指令，并且当该处理器1601执行存储器中存储的指令时，该处理器1601用于执行上述与该第二终端设备对应的方法实施例的各个步骤和/或流程。该收发器1602可以包括发射器和接收器，该发射器可以用于实现上述收发器对应的用于执行发送动作的各个步骤和/或流程，该接收器可以用于实现上述收发器对应的用于执行接收动作的各个步骤和/或流程。
应理解，在本申请实施例中，该处理器可以是中央处理单元(central processing unit，CPU)，该处理器还可以是其他通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
在实现过程中，上述方法的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器执行存储器中的指令，结合其硬件完成上述方法的步骤。为避免重复，这里不再详细描述。
本申请还提供了一种计算机可读存储介质，该计算机可读存储介质用于存储计算机程序，该计算机程序用于实现上述实施例中与第二终端设备对应的方法。
本申请还提供了一种计算机程序产品，该计算机程序产品包括计算机程序(也可以称为代码，或指令)，当该计算机程序在计算机上运行时，该计算机可以执行上述实施例所示的第二终端设备对应的方法。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的模块及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和模块的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通 过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述模块的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个模块或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或模块的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的模块可以是或者也可以不是物理上分开的，作为模块显示的部件可以是或者也可以不是物理模块，即可以位于一个地方，或者也可以分布到多个网络模块上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能模块可以集成在一个处理模块中，也可以是各个模块单独物理存在，也可以两个或两个以上模块集成在一个模块中。
所述功能如果以软件功能模块的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请实施例的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请实施例揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请实施例的保护范围之内。因此，本申请实施例的保护范围应所述以权利要求的保护范围为准。

Claims (19)

  1. 一种应用接续的方法，其特征在于，应用于包括第一终端设备、第二终端设备、以及云服务器的系统，用户在所述第一终端设备和所述第二终端设备上登录了相同的账号，并且所述第一终端设备与所述第二终端设备处于同一局域网，所述方法包括：
    所述第二终端设备接收来自所述第一终端设备的广播接续通知，所述广播接续通知用于请求将所述第一终端设备的第一接续应用接续至所述第二终端设备；
    所述第二终端设备根据所述广播接续通知，确定第二接续应用，并对所述第二接续应用进行合法性鉴权和匹配关系校验，获得合法性鉴权结果和匹配关系校验结果；
    在所述合法性鉴权结果为合法性鉴权通过、且所述匹配关系校验结果为匹配关系校验通过的情况下，所述第二终端设备显示所述第二接续应用的接续触点。
  2. 根据权利要求1所述的方法，其特征在于，所述广播接续通知包括：所述第一接续应用的应用标识符APPID和接续策略；
    其中，所述接续策略包括下列至少一种：
    接续状态标识、至少一个目标接续应用的包名或进程名、所述至少一个目标接续应用的设备类型、所述至少一个目标接续应用的应用市场上架策略以及支持接续的最小版本；
    所述至少一个目标接续应用包括所述第二接续应用。
  3. 根据权利要求2所述的方法，其特征在于，所述第二终端设备根据所述广播接续通知，确定第二接续应用，包括：
    所述第二终端设备基于所述至少一个目标接续应用的设备类型，将所述至少一个目标接续应用中与所述第二终端设备的设备类型相同的应用确定为所述第二接续应用。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，所述对所述第二接续应用进行合法性鉴权，包括：
    所述第二终端设备向所述云服务器发送合法性鉴权请求，所述合法性鉴权请求携带所述第二接续应用的APPID；
    所述第二终端设备接收来自所述云服务器的所述第二接续应用的云端标识信息，所述云端标识信息包括所述云服务器存储的所述第二接续应用的包名和/或签名；
    所述第二终端设备将所述云端标识信息和所述第二接续应用的本地标识信息进行比较，获得所述合法性鉴权结果，所述本地标识信息为所述第二终端设备本地存储的所述第二接续应用的包名和/或签名。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，所述对所述第二接续应用进行匹配关系校验，包括：
    所述第二终端设备向所述云服务器发送匹配关系查询请求，所述匹配关系查询请求携带所述第二接续应用的APPID；
    所述第二终端设备接收来自所述云服务器的第一匹配关系，所述第一匹配关系用于表示能够与所述第二接续应用进行接续的至少一个应用；
    所述第二终端设备基于所述第一匹配关系，判断所述至少一个应用是否包括所述第一接续应用，获得所述匹配关系校验结果。
  6. 根据权利要求1至4中任一项所述的方法，其特征在于，所述对所述第二接续应用进行匹配关系校验，包括：
    所述第二终端设备向所述云服务器发送匹配关系查询请求，所述匹配关系查询请求携带所述第一接续应用的APPID；
    所述第二终端设备接收来自所述云服务器的第一匹配关系，所述第一匹配关系用于表示能够与所述第一接续应用进行接续的至少一个应用；
    所述第二终端设备基于所述第一匹配关系，判断所述至少一个应用是否包括所述第二接续应用，获得所述匹配关系校验结果。
  7. 根据权利要求1至4中任一项所述的方法，其特征在于，所述对所述第二接续应用进行匹配关系校验，包括：
    所述第二终端设备获取第二匹配关系，所述第二匹配关系用于表示能够与所述第二接续应用进行接续的至少一个应用，所述第二匹配关系是所述第二终端设备在安装所述第二接续应用时预先存储在本地的；
    所述第二终端设备基于所述第二匹配关系，判断所述至少一个应用是否包括所述第一接续应用，获得所述匹配关系校验结果。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，所述方法还包括：
    所述第二终端设备响应于用户对所述接续触点的点击操作，向所述第一终端设备发送接续数据请求消息；
    所述第二终端设备接收来自所述第一终端设备的接续数据，并显示所述接续数据。
  9. 一种终端设备，其特征在于，包括：
    收发模块，用于接收来自第一终端设备的广播接续通知，所述广播接续通知用于请求将所述第一终端设备的第一接续应用接续至所述终端设备；
    处理模块，用于根据所述广播接续通知，确定第二接续应用，并对所述第二接续应用进行合法性鉴权和匹配关系校验，获得合法性鉴权结果和匹配关系校验结果；在所述合法性鉴权结果为合法性鉴权通过、且所述匹配关系校验结果为匹配关系校验通过的情况下，显示所述第二接续应用的接续触点。
  10. 根据权利要求9所述的终端设备，其特征在于，所述广播接续通知包括：所述第一接续应用的应用标识符APPID和接续策略；
    其中，所述接续策略包括下列至少一种：
    接续状态标识、至少一个目标接续应用的包名或进程名、所述至少一个目标接续应用的设备类型、所述至少一个目标接续应用的应用市场上架策略以及支持接续的最小版本；
    所述至少一个目标接续应用包括所述第二接续应用。
  11. 根据权利要求10所述的终端设备，其特征在于，所述处理模块还用于：
    基于所述至少一个目标接续应用的设备类型，将所述至少一个目标接续应用中与所述终端设备的设备类型相同的应用确定为所述第二接续应用。
  12. 根据权利要求9至11中任一项所述的终端设备，其特征在于，所述收发模块还用于：
    向云服务器发送合法性鉴权请求，所述合法性鉴权请求携带所述第二接续应用的APPID；接收来自所述云服务器的所述第二接续应用的云端标识信息，所述云端标识信息包括所述云服务器存储的所述第二接续应用的包名和/或签名；
    所述处理模块还用于：
    将所述云端标识信息和所述第二接续应用的本地标识信息进行比较，获得所述合法性鉴权结果，所述本地标识信息为所述终端设备本地存储的所述第二接续应用的包名和/或签名。
  13. 根据权利要求9至12中任一项所述的终端设备，其特征在于，所述收发模块还用于：
    向云服务器发送匹配关系查询请求，所述匹配关系查询请求携带所述第二接续应用的APPID；接收来自所述云服务器的第一匹配关系，所述第一匹配关系用于表示能够与所述第二接续应用进行接续的至少一个应用；
    所述处理模块还用于：
    基于所述第一匹配关系，判断所述至少一个应用是否包括所述第一接续应用，获得所述匹配关系校验结果。
  14. 根据权利要求9至12中任一项所述的终端设备，其特征在于，所述收发模块还用于：
    向云服务器发送匹配关系查询请求，所述匹配关系查询请求携带所述第一接续应用的APPID；接收来自所述云服务器的第一匹配关系，所述第一匹配关系用于表示能够与所述第一接续应用进行接续的至少一个应用；
    所述处理模块还用于：
    基于所述第一匹配关系，判断所述至少一个应用是否包括所述第二接续应用，获得所述匹配关系校验结果。
  15. 根据权利要求9至12中任一项所述的终端设备，其特征在于，所述处理模块还用于：
    获取第二匹配关系，所述第二匹配关系用于表示能够与所述第二接续应用进行接续的至少一个应用，所述第二匹配关系是所述终端设备在安装所述第二接续应用时预先存储在本地的；基于所述第二匹配关系，判断所述至少一个应用是否包括所述第一接续应用，获得所述匹配关系校验结果。
  16. 根据权利要求9至15中任一项所述的终端设备，其特征在于，所述收发模块还用于：
    响应于用户对所述接续触点的点击操作，向所述第一终端设备发送接续数据请求消息；接收来自所述第一终端设备的接续数据，并显示所述接续数据。
  17. 一种终端设备，其特征在于，包括：存储器和处理器，所述存储器用于存储计算机程序，所述处理器用于执行所述计算机程序，以执行如权利要求1-8中任一项所述的方法。
  18. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储有指令，当所述指令被执行时，使得计算机执行如权利要求1-8中任一项所述的应用接续方法。
  19. 一种计算机程序产品，其特征在于，包括计算机程序，当所述计算机程序被运行时，使得电子设备执行如权利要求1-8中任一项所述的方法。
PCT/CN2023/119544 2022-09-28 2023-09-18 应用接续方法和终端设备 WO2024067225A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211193576.5 2022-09-28
CN202211193576.5A CN117784989A (zh) 2022-09-28 2022-09-28 应用接续方法和终端设备

Publications (1)

Publication Number Publication Date
WO2024067225A1 true WO2024067225A1 (zh) 2024-04-04

Family

ID=90389769

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/119544 WO2024067225A1 (zh) 2022-09-28 2023-09-18 应用接续方法和终端设备

Country Status (2)

Country Link
CN (1) CN117784989A (zh)
WO (1) WO2024067225A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111447323A (zh) * 2020-03-20 2020-07-24 华为技术有限公司 一种应用显示接续方法及装置
CN113311975A (zh) * 2020-02-27 2021-08-27 华为技术有限公司 多设备之间的应用互动方法及相关设备
CN113645622A (zh) * 2021-07-08 2021-11-12 荣耀终端有限公司 设备鉴权方法、电子设备以及存储介质
CN114924671A (zh) * 2022-07-18 2022-08-19 荣耀终端有限公司 应用接续方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113311975A (zh) * 2020-02-27 2021-08-27 华为技术有限公司 多设备之间的应用互动方法及相关设备
CN111447323A (zh) * 2020-03-20 2020-07-24 华为技术有限公司 一种应用显示接续方法及装置
CN113645622A (zh) * 2021-07-08 2021-11-12 荣耀终端有限公司 设备鉴权方法、电子设备以及存储介质
CN114924671A (zh) * 2022-07-18 2022-08-19 荣耀终端有限公司 应用接续方法和装置

Also Published As

Publication number Publication date
CN117784989A (zh) 2024-03-29

Similar Documents

Publication Publication Date Title
US9026918B2 (en) Enabling a user device to access enterprise data
US8694981B2 (en) Shared resource dependencies
US20190089810A1 (en) Resource access method, apparatus, and system
US20130219307A1 (en) System and method for runtime user interface management
US20190303219A1 (en) Embedding an interface of one application into an interface of another application
US20090064202A1 (en) Support layer for enabling same accessory support across multiple platforms
US11882154B2 (en) Template representation of security resources
WO2023051355A1 (zh) 权限检查的方法和电子设备
WO2016070690A1 (zh) 实现终端设备上的网页和应用间通信的方法、装置和系统
CN115048642A (zh) 多可信执行环境下可信应用间的通信方法及电子设备
CN116700552B (zh) 应用接续方法和终端设备
CN110278273A (zh) 多媒体文件上传方法、装置、终端、服务器和存储介质
CN107957887A (zh) 一种设备的组件加载方法、装置以及物联网系统
WO2024067225A1 (zh) 应用接续方法和终端设备
US20240031630A1 (en) Platform-agnostic media framework
CN114706633B (zh) 预加载方法、电子设备及存储介质
US11431727B2 (en) Security of code between code generator and compiler
WO2024067205A1 (zh) 应用接续方法和终端设备
WO2022078119A1 (zh) 跨设备数据分享方法及相关设备
CN108171063A (zh) 访问安全元件的方法、终端及计算机可读存储介质
CN114692093B (zh) 一种应用程序安装方法及电子设备
CN115981576B (zh) 共享数据的方法、电子设备及存储介质
US11991040B2 (en) Network configuration method and device
CN115250259B (zh) 信息交互方法、装置和电子设备
WO2024113957A1 (zh) 游戏服务的管理方法和电子设备

Legal Events

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

Ref document number: 23870457

Country of ref document: EP

Kind code of ref document: A1