WO2022206676A1 - 一种功能迁移方法和装置 - Google Patents

一种功能迁移方法和装置 Download PDF

Info

Publication number
WO2022206676A1
WO2022206676A1 PCT/CN2022/083386 CN2022083386W WO2022206676A1 WO 2022206676 A1 WO2022206676 A1 WO 2022206676A1 CN 2022083386 W CN2022083386 W CN 2022083386W WO 2022206676 A1 WO2022206676 A1 WO 2022206676A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
mobile phone
group
information
request
Prior art date
Application number
PCT/CN2022/083386
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 WO2022206676A1 publication Critical patent/WO2022206676A1/zh

Links

Images

Classifications

    • 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/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0646—Horizontal data movement in storage systems, i.e. moving data in between storage devices or systems
    • G06F3/0647—Migration mechanisms
    • 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/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/44—Program or device authentication
    • 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/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
    • 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/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
    • G06K19/00—Record carriers for use with machines and with at least a part designed to carry digital markings
    • G06K19/06—Record carriers for use with machines and with at least a part designed to carry digital markings characterised by the kind of the digital marking, e.g. shape, nature, code
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
    • G06K19/00—Record carriers for use with machines and with at least a part designed to carry digital markings
    • G06K19/06—Record carriers for use with machines and with at least a part designed to carry digital markings characterised by the kind of the digital marking, e.g. shape, nature, code
    • G06K19/06009—Record carriers for use with machines and with at least a part designed to carry digital markings characterised by the kind of the digital marking, e.g. shape, nature, code with optically detectable marking
    • G06K19/06037—Record carriers for use with machines and with at least a part designed to carry digital markings characterised by the kind of the digital marking, e.g. shape, nature, code with optically detectable marking multi-dimensional coding

Definitions

  • the present application relates to the field of terminals, and in particular, to a function migration method and apparatus.
  • the embodiments of the present application provide a function migration method and device, which can ensure the safety and reliability of data sharing.
  • an embodiment of the present application provides a function migration method, which is applied to a first device.
  • the method includes: sending a first request to a second device, where the first request carries the identifier of the first device, the identifier of the first application, and the first request. Second, the identification of the application; receiving a first response from the second device, where the first response is used to indicate a first group created by the second device, the members of the first group include the second application of the second device; sending the second device to the second device
  • the second request is used to apply for adding the first application of the first device to the first group; to migrate the first function in the first application to the second application of the second device, where the first function includes one or more A graphical user interface (user interface, UI).
  • UI graphical user interface
  • the first application of the first device and the second application of the second device can join the first group, that is, members of the first group can join the first group.
  • a first application of the first device and a second application of the second device are included. Since the first group is established after negotiation between the first device and the second device, migrating function data between members of the first group, such as migrating one or more UIs of the first function, can ensure data sharing. Safe and reliable.
  • the first response includes a personal identification number (PIN) corresponding to the first group and/or the communication connection information of the second device;
  • the second request is sent to the second device, including : Send a second request to the second device according to the PIN and/or the communication connection information of the second device.
  • PIN personal identification number
  • the first device needs to join the group created by the second device, it can carry the PIN corresponding to the group in the request, so that the second device can verify the security of the first device according to the PIN, so as to ensure the data Safe and secure sharing.
  • the method further includes: receiving a second response, where the second response is used to indicate that the first application of the first device has joined the first group.
  • the first device can learn that the first application has joined the first group, so that function migration can be directly performed subsequently.
  • the method further includes: creating a second group, wherein members of the second group include the first application of the first device and the second application of the second device. That is, the first device can locally create a group (ie, the second group), which is the same as the group created by the second device. In this way, when the second application of the second device performs function migration to the first application of the first device, if the first device determines that the second group is stored locally, it can be considered that the second application of the second device is safe and reliable , you can directly perform function migration.
  • the method further includes: in response to the user's first operation of the first application on the first device, displaying a first pop-up frame, where the first pop-up frame includes a network that is in the same network as the first device.
  • the identification of the device; sending the first request to the second device includes: in response to the second operation of the user selecting the second device in the first pop-up box, sending the first request to the second device. In this way, the user can select the device whose function needs to be migrated through the first pop-up box.
  • the devices in the same network as the first device include trusted devices and untrusted devices; wherein, the trusted devices include devices that log into the same account as the first device, and devices that are logged into the same account as the first device.
  • the trusted device and the untrusted device can be prompted to the user, so as to facilitate the user to manage the corresponding devices.
  • the method further includes: scanning a two-dimensional code picture displayed by the second device, where the two-dimensional code picture includes the personal identification code PIN corresponding to the first group and/or the communication connection information of the second device, Sending the second request to the second device includes: sending the second request to the second device according to the PIN and/or the communication connection information of the second device.
  • the two-dimensional code picture is used as an identifier for schematic illustration, and the two-dimensional code picture may be replaced with other types of identifiers, such as barcodes, character strings, etc., which are not limited in this application.
  • migrating the first function in the first application to the second device includes: sending service information of the first function to the second device; when the first application is a live broadcast application, the first function
  • the service information includes at least one of a video stream, an audio stream, and bullet screen information in the live room of the first device; or when the first application is a camera application, the service information of the first function includes a shooting preview screen or a menu of a shooting interface column information; or when the first application is a K song application, the service information of the first function includes at least one of song title, lyrics, audio information of the song, video information of the song, and control interface of the song; or when the first application When the first application is a shopping application, the service information of the first function includes information of commodities in the shopping cart; or when the first application is an email application, the service information of the first function includes at least one of the subject, body and attachments of the email.
  • some functions of different applications for example, a live broadcast application, a camera application, a karaoke application, an email application or a shopping application
  • a live broadcast application for example, a camera application, a karaoke application, an email application or a shopping application
  • the second device which can meet the requirements of cross-border operation.
  • the need for device migration capabilities for example, a live broadcast application, a camera application, a karaoke application, an email application or a shopping application
  • the communication connection information of the second device includes a Wi-Fi address or a Bluetooth address of the second device.
  • the method further includes: sending a third request to a third device, where the third request carries the identifier of the first device, the package name of the first application, and the package name of the third application ; the third request is used to request to migrate the first function of the first application to the third application of the third device; receive a second response, the second response includes the information agreeing to the migration and all the group name of the second group created by the third device, the members of the second group include the first application of the first device and the third application of the third device; The third device sends a fourth request, the fourth request is used to apply for joining the second group, and the fourth request includes the group name of the second group; The first function is migrated to the third device.
  • the method further includes updating members of the first group saved locally, and the updated members of the first group include the first application of the first device , the second application of the second device and the third application of the third device.
  • the package name of the second application is the same as the package name of the first application.
  • the trusted device includes a third device, and in response to a user's operation of deleting the third device from the trusted device, the group related to the third device is deleted.
  • the first group is set to be valid permanently or within a preset time.
  • the method further includes: rearranging the song-ordering control UI; in response to the user performing the operations of ordering and cutting songs on the song-ordering control UI , and send song-ordering and song-cutting information to the second device.
  • the business information of the first function includes commodity information in the shopping cart, and the commodity information includes commodity name, commodity link and commodity price information at least one of them.
  • the service information of the first function includes at least one of the subject, body or attachment of the email.
  • an embodiment of the present application provides a function migration method, which is applied to a second device.
  • the method includes: receiving a first request from the first device, where the first request carries an identifier of the first device, an identifier of the first application, and identification of the second application; creating a first group, members of the first group including the second application of the second device; sending a first response to the first device, where the first response is used to indicate the first group; A second request from a device, where the second request is used to apply for adding the first application of the first device to the first group.
  • a first function in the first application migrated by the first device is received, wherein the first function includes one or more graphical user interface UIs.
  • the first application of the first device and the second application of the second device can join the first group, that is, members of the first group can join the first group.
  • a first application of the first device and a second application of the second device are included. Since the first group is established after negotiation between the first device and the second device, migrating function data between members of the first group, such as migrating one or more UIs of the first function, can ensure data sharing. Safe and reliable.
  • the first response includes the personal identification code PIN corresponding to the first group and/or the communication connection information of the second device.
  • the second device can verify the security of the first device according to the PIN, thereby ensuring the safety and reliability of data sharing.
  • the method further includes: sending a second response to the first device, where the second response is used to indicate that the first application of the first device has joined the second group.
  • the first device can learn that the first application has joined the first group, so that function migration can be directly performed subsequently.
  • the method further includes: displaying a first pop-up box, where the first pop-up box is used to prompt the user whether to agree to add the first application of the first device to the first Groups; receive consent instructions from users. In this way, the user may be prompted to add the first application of the first device to the first group through the first pop-up box.
  • the method before creating the first group, further includes: determining, according to the identifier of the first device, that the second device currently does not have a second group, wherein the members of the second group include the first device and the second device. That is, when it is determined that a group is not established between the first device and the second device, that is, when the first device and the second device have not established a process trusted connection first, the first group can be created.
  • the method before creating the first group, further includes: determining, according to the identifier of the first device, the identifier of the first application and the identifier of the second application, that the second device currently does not have the third group , wherein the members of the third group include the first application of the first device and the second application of the second device. That is, if it is determined that no group is established between the first application of the first device and the second application of the second device, that is, the first application of the first device and the second application of the second device have not established a process beforehand. In the case of a letter connection, the first group can be created.
  • the method further includes: displaying a two-dimensional code picture, where the two-dimensional code picture includes the personal identification code PIN corresponding to the first group and/or the communication connection information of the second device.
  • the two-dimensional code picture is used as an identifier for schematic illustration, and the two-dimensional code picture may be replaced with other types of identifiers, such as barcodes, character strings, etc., which are not limited in this application.
  • receiving the first function in the first application migrated by the first device includes: receiving service information of the first function from the first device; when the first application is a live broadcast application, the first function
  • the business information of the first device includes at least one of the video stream, audio stream and bullet screen information in the live room of the first device; or when the first application is a camera application, the business information of the first function includes the shooting preview screen or the shooting interface.
  • the service information of the first function includes at least one of song title, lyrics, audio information of the song, video information of the song, and control interface of the song;
  • the application is a shopping application
  • the business information of the first function includes commodity information in the shopping cart; or when the first application is an email application, the business information of the first function includes at least one of the subject, body and attachments of the email.
  • some functions of different applications for example, a live broadcast application, a camera application, a karaoke application, an email application or a shopping application
  • a live broadcast application for example, a camera application, a karaoke application, an email application or a shopping application
  • the second device which can meet the requirements of cross-border operation.
  • the need for device migration capabilities for example, a live broadcast application, a camera application, a karaoke application, an email application or a shopping application
  • the communication connection information of the second device includes a Wi-Fi address or a Bluetooth address of the second device.
  • the package name of the second application is the same as the package name of the first application.
  • the first group is set to be valid permanently or within a preset time.
  • the method further includes: displaying a second pop-up box, where the second pop-up box is used to prompt the user whether to agree to the first device to migrate the first function to the second equipment.
  • the second device if the second device installs the live broadcast application, the second device detects whether the live broadcast application is logged in; if the live broadcast application is in the logged-in state, the live broadcast application displays the first function on the live broadcast screen of the second device.
  • the second device displays the first function in the form of an audio player.
  • the service information of the first function includes the photographing preview screen and the menu bar information of the photographing interface.
  • the second device displays the shooting preview screen of the first device and the menu bar of the shooting interface; in response to the user triggering the first device to shoot on the second device, a shooting instruction is sent to the first device. , the first device captures a photo or video.
  • the first application is the K song application
  • the second device installs the K song application, it is detected whether the K song application is logged in; if the K song application is in the login state, the K song application displays the first function .
  • the first application is a karaoke application
  • the karaoke application is not installed on the second device, the first function is displayed in the form of an audio player.
  • the shopping application when the first application is a shopping application, if the shopping application is installed on the second device, it is detected whether the shopping application is logged in; if the shopping application is in a logged-in state, the shopping application displays and shares the business information of the first function.
  • the shopping cart, the shared shopping cart includes all the products in the shopping cart of the second device and all the products in the shopping cart of the first device.
  • the second device in response to the user's operation of settling all commodities in the shared shopping cart, the second device sends a payment request to the first device, where the payment request includes the total amount of all commodities in the shopping cart of the first device.
  • the first application is a mail application
  • a mailbox application is installed on the second device, it is detected whether the mailbox application is logged in; if the mailbox application is in a logged-in state, the mailbox application displays the first function.
  • the first application is an email application
  • the email application if the email application is not installed on the second device, the first function is coded, rearranged and displayed in the form of a graphic editor.
  • an embodiment of the present application provides a function migration method, which is applied to a communication system including a first device and a second device.
  • the method includes: the first device sends a first request to the second device, and the first request carries the first request.
  • the identification of the device the second device receives the first request from the first device; the second device sends the first response from the first device, the first response is used to indicate the first group created by the second device, the members of the first group Including a second device; the first device receives a first response from the second device; the first device sends a second request to the second device, and the second request is used to apply for adding the first device to the first group; A first function in an application is migrated to the second device, the first application is any application in the first device, and the first function includes one or more graphical user interface UIs.
  • the first response includes the personal identification code PIN corresponding to the first group and/or the communication connection information of the second device
  • sending the second request to the second device includes: according to the PIN and/or The communication connection information of the second device sends a second request to the second device; the method further includes: receiving a second response from the second device, where the second response is used to indicate that the first device has joined the first group.
  • the first device in response to the user's first operation, displays a first pop-up box, and the first pop-up box includes the identifiers of one or more devices that have not been authenticated with the first device; the first The device sending the first request to the second device includes: in response to a second operation of the user selecting the second device in the first pop-up box, sending the first request to the second device.
  • the method further includes: the first device creates a second group, and members of the second group include the first device and the second device.
  • the method further includes: in response to the user's first operation of the first application on the first device, the first device displays a first pop-up frame, where the first pop-up frame includes the same location as the first device.
  • the identifier of the device in the network; the first device sending the first request to the second device includes: the first device sends the first request to the second device in response to the second operation of the user selecting the second device in the first pop-up box .
  • the devices in the same network as the first device include trusted devices and untrusted devices; wherein, the trusted devices include devices that log into the same account as the first device, and devices that are logged into the same account as the first device.
  • the trusted devices include devices that log into the same account as the first device, and devices that are logged into the same account as the first device.
  • a device that has undergone device-level authentication or a device that has undergone application-level authentication with the first application of the first device; untrusted devices include devices that have not logged into the same account as the first device, and have not undergone device-level authentication with the first device. or a device that has not undergone application-level authentication with the first application of the first device.
  • the method further includes: the second device displays a two-dimensional code picture, and the two-dimensional code picture includes the personal identification code PIN corresponding to the first group and/or the communication connection information of the second device; the first The device scans the QR code picture displayed by the second device; the first device sends the second request to the second device, including: the first device sends the second request to the second device according to the PIN and/or the communication connection information of the second device.
  • the first device migrating the first function in the first application to the second device includes: sending service information of the first function to the second device; when the first application is a live broadcast application, the first The service information of a function includes at least one of the video stream, audio stream and bullet screen information of the live room of the first device; or when the first application is a camera application, the service information of the first function includes shooting a preview screen or shooting The menu bar information of the interface; or when the first application is a K song application, the service information of the first function includes at least one of the song title, lyrics, audio information of the song, video information of the song, and control interface of the song; or when When the first application is a shopping application, the business information of the first function includes the commodity information in the shopping cart; or when the first application is an email application, the business information of the first function includes at least one of the subject, body and attachments of the email. kind.
  • an embodiment of the present application provides a function migration method, which is applied to a first device, including: creating a first group, members of the first group including a first application of the first device; receiving a first application from the second device A request, the first request is used to apply for adding the second application of the second device to the first group; adding the second application of the second device to the first group; migrating the first function in the first application to the second
  • the second application of the device, the second function includes one or more graphical user interfaces UI.
  • the method before receiving the first request from the second device, the method further includes: displaying a first identifier for indicating the first group, wherein the first request corresponds to the first identifier .
  • the first identifier includes a two-dimensional code picture, and the first identifier includes a personal identification code PIN; after receiving the first request from the second device, the method further includes: determining that the first request carries the PIN ; Determine to add the second application of the second device to the first group.
  • migrating the first function in the first application to the second application of the second device includes: sending service information of the first function to the second device; when the first application is a live broadcast application, The service information of the first function includes at least one of the video stream, audio stream, and bullet screen information in the live room of the first device; or when the first application is a camera application, the service information of the first function includes shooting a preview screen or The menu bar information of the shooting interface; or when the first application is a K song application, the service information of the first function includes at least one of the song title, lyrics, audio information of the song, video information of the song, and control interface of the song; or When the first application is a shopping application, the business information of the first function includes the commodity information in the shopping cart; or when the first application is an email application, the business information of the first function includes at least one of the subject, body and attachments of the email. A sort of.
  • an embodiment of the present application provides a function migration method, which is applied to a second device, including: sending a first request to the first device, where the first request is used to apply for adding a second application of the second device to the first device A first group is created, the members of the first group include a first application of the first device and a second application of the second device; the first function in the first application is received from the first device, wherein the first function includes One or more graphical user interface UIs.
  • the method before sending the first request to the first device, the method further includes: scanning a first identifier for indicating the first group, wherein the first request corresponds to the first identifier .
  • the first identifier includes a two-dimensional code picture, and the first identifier includes a personal identification code PIN; sending the first request to the first device includes: sending a first request to the first device, the first The PIN is included in the request.
  • receiving the first function of the first application from the first device includes: receiving service information of the first function from the first device; when the first application is a live application, the service of the first function The information includes at least one of the video stream, audio stream, and bullet screen information in the live room of the first device; or when the first application is a camera application, the business information of the first function includes the shooting preview screen or the menu bar of the shooting interface information; or when the first application is a K song application, the service information of the first function includes at least one of song title, lyrics, audio information of the song, video information of the song, and control interface of the song; or when the first application is When the shopping application is used, the service information of the first function includes the commodity information in the shopping cart; or when the first application is an email application, the service information of the first function includes at least one of the subject, body and attachment of the email.
  • the present application provides a first device including one or more processors and one or more memories.
  • the one or more memories are coupled to the one or more processors for storing computer program code comprising computer instructions which, when executed by the one or more processors, cause the first device.
  • the present application provides a second device including one or more processors and one or more memories.
  • the one or more memories are coupled to the one or more processors for storing computer program code comprising computer instructions which, when executed by the one or more processors, cause the second device.
  • an embodiment of the present application provides a computer program product, which, when the computer program product runs on a computer, causes the computer to execute the method in any of the possible implementations of any one of the foregoing aspects.
  • the present application provides a chip system, which can be set in the first device.
  • the chip system includes one or more interface circuits and one or more processors.
  • the interface circuit and the processor are interconnected by wires.
  • the chip system can be applied to electronic equipment including a communication module and a memory.
  • the interface circuit is used for the memory to receive signals and to send the received signals to the processor, the signals including computer instructions stored in the memory.
  • the processor executes the computer instructions
  • the first device can execute the method described in any of the above aspects and any of its possible implementations.
  • an embodiment of the present application provides a computer storage medium, including computer instructions, when the computer instructions are executed on the first device, the first device is made to execute the method in any of the possible implementation manners of any of the above aspects .
  • an embodiment of the present application provides a function migration system, including at least two devices (for example, a first device and a second device), each of which can perform any of the foregoing aspects and any possible implementation manners thereof the method described.
  • FIG. 1 is a schematic diagram of a system architecture provided by an embodiment of the present application.
  • FIG. 2 is a schematic diagram of another system architecture provided by an embodiment of the present application.
  • FIG. 3 is a schematic diagram of a hardware structure of an electronic device provided by an embodiment of the present application.
  • FIG. 4 is a schematic diagram of a software architecture of an electronic device provided by an embodiment of the present application.
  • FIG. 5A is a schematic display diagram provided by an embodiment of the present application.
  • FIG. 5B is another schematic display diagram provided by an embodiment of the present application.
  • FIG. 5C is another schematic display diagram provided by an embodiment of the present application.
  • FIG. 5D is another schematic display diagram provided by an embodiment of the present application.
  • FIG. 5E is another schematic display diagram provided by an embodiment of the present application.
  • FIG. 5F is another schematic display diagram provided by an embodiment of the present application.
  • FIG. 6A is another schematic display diagram provided by an embodiment of the present application.
  • FIG. 6B is another schematic display diagram provided by an embodiment of the present application.
  • FIG. 6C is another schematic display diagram provided by an embodiment of the present application.
  • FIG. 7A is a schematic diagram of a signal interaction provided by an embodiment of the present application.
  • FIG. 7B is another schematic diagram of signal interaction provided by an embodiment of the present application.
  • FIG. 7C is another schematic diagram of signal interaction provided by an embodiment of the present application.
  • FIG. 8A is another schematic display diagram provided by an embodiment of the present application.
  • FIG. 8B is another schematic display diagram provided by an embodiment of the present application.
  • FIG. 8C is another schematic display diagram provided by an embodiment of the present application.
  • FIG. 8D is another schematic display diagram provided by an embodiment of the present application.
  • FIG. 8E is another schematic display diagram provided by an embodiment of the present application.
  • FIG. 9A is another schematic diagram of signal interaction provided by an embodiment of the present application.
  • FIG. 9B is another schematic diagram of signal interaction provided by an embodiment of the present application.
  • FIG. 9C is another schematic diagram of signal interaction provided by an embodiment of the present application.
  • FIG. 10A is another schematic display diagram provided by an embodiment of the present application.
  • FIG. 10B is another schematic display diagram provided by the embodiment of the present application.
  • FIG. 11 is another schematic diagram of signal interaction provided by an embodiment of the present application.
  • FIG. 12A is another schematic display diagram provided by an embodiment of the present application.
  • FIG. 12B is another schematic display diagram provided by an embodiment of the present application.
  • FIG. 12C is another schematic display diagram provided by an embodiment of the present application.
  • FIG. 12D is another schematic display diagram provided by an embodiment of the present application.
  • FIG. 12E is another schematic display diagram provided by an embodiment of the present application.
  • FIG. 12F is another schematic display diagram provided by the embodiment of the present application.
  • FIG. 13 is another schematic diagram of signal interaction provided by an embodiment of the present application.
  • FIG. 14A is another schematic display diagram provided by an embodiment of the present application.
  • FIG. 14B is another schematic display diagram provided by an embodiment of the present application.
  • FIG. 14C is another schematic display diagram provided by an embodiment of the present application.
  • FIG. 14D is another schematic display diagram provided by an embodiment of the present application.
  • FIG. 14E is another schematic display diagram provided by an embodiment of the present application.
  • FIG. 14F is another schematic display diagram provided by an embodiment of the present application.
  • FIG. 15 is another schematic diagram of signal interaction provided by an embodiment of the present application.
  • FIG. 16A is another schematic display diagram provided by an embodiment of the present application.
  • FIG. 16B is another schematic display diagram provided by an embodiment of the present application.
  • FIG. 16C is another schematic display diagram provided by an embodiment of the present application.
  • FIG. 16D is another schematic display diagram provided by an embodiment of the present application.
  • FIG. 16E is another schematic display diagram provided by an embodiment of the present application.
  • FIG. 17A is another schematic diagram of signal interaction provided by an embodiment of the present application.
  • FIG. 17B is another schematic display diagram provided by an embodiment of the present application.
  • FIG. 17C is another schematic display diagram provided by an embodiment of the present application.
  • FIG. 17D is another schematic display diagram provided by an embodiment of the present application.
  • FIG. 18A is another schematic display diagram provided by an embodiment of the present application.
  • FIG. 18B is another schematic display diagram provided by the embodiment of the present application.
  • FIG. 18C is another schematic display diagram provided by an embodiment of the present application.
  • FIG. 18D is another schematic display diagram provided by an embodiment of the present application.
  • FIG. 19 is another schematic diagram of signal interaction provided by an embodiment of the present application.
  • FIG. 20 is another schematic diagram of signal interaction provided by an embodiment of the present application.
  • FIG. 21 is another schematic diagram of signal interaction provided by an embodiment of the present application.
  • FIG. 22 is another schematic diagram of signal interaction provided by an embodiment of the present application.
  • FIG. 23 is a schematic structural diagram of a chip system provided by an embodiment of the present application.
  • the system architecture involved in the embodiments of the present application may include multiple electronic devices, the multiple electronic devices may be networked, and information exchange may be performed between the multiple electronic devices after the networking.
  • the networking methods include but are not limited to the following methods:
  • Wireless fidelity (wireless fidelity, Wi-Fi) networking mode multiple electronic devices can access the same routing device (for example, a router).
  • a mobile phone 101 , a mobile phone 102 , a tablet computer 103 , a notebook computer 104 , and a smart TV 105 can be connected to the router 106 to form a home network.
  • multiple electronic devices can join the same hotspot device (for example, access the hotspot of the same mobile phone), and at this time, the information interaction between the electronic device and the electronic device can be forwarded through the hotspot device.
  • mobile phone 102, tablet computer 103, notebook computer 104, and smart TV 105 can be connected to mobile phone 101 to form a hotspot network, and mobile phone 101 can be used as a hotspot device to forward information for each electronic device.
  • Bluetooth networking mode multiple electronic devices can be connected to the same Bluetooth device (eg, mobile phone 104 ), and the information exchange between the electronic device and the electronic device can be forwarded through the Bluetooth device.
  • the mobile phone 101 , the tablet computer 103 , the notebook computer 104 , and the smart TV 105 can be connected to the mobile phone 102 to form a Bluetooth network, and the mobile phone 102 can be used as a Bluetooth device to forward information for each electronic device.
  • Multiple electronic devices may use multiple networking methods, for example, using both a wireless fidelity networking method and a Bluetooth networking method, which is not limited in this application.
  • an electronic device 200 (such as a mobile phone) is used as an example to illustrate the structure of the electronic device provided by the embodiment of the present application.
  • the electronic device 200 may include: a processor 210, an external memory interface 220, an internal memory 221, a universal serial bus (USB) interface 230, a charging management module 240, a power management module 241, a battery 242, Antenna 1, Antenna 2, Mobile Communication Module 250, Wireless Communication Module 260, Audio Module 270, Speaker 270A, Receiver 270B, Microphone 270C, Headphone Interface 270D, Sensor Module 280, Key 290, Motor 291, Indicator 292, Camera 293, Display screen 294, and subscriber identification module (subscriber identification module, SIM) card interface 295 and so on.
  • SIM subscriber identification module
  • the above sensor module 280 may include sensors such as pressure sensor, gyroscope sensor, air pressure sensor, magnetic sensor, acceleration sensor, distance sensor, proximity light sensor, fingerprint sensor, temperature sensor, touch sensor, ambient light sensor and bone conduction sensor.
  • sensors such as pressure sensor, gyroscope sensor, air pressure sensor, magnetic sensor, acceleration sensor, distance sensor, proximity light sensor, fingerprint sensor, temperature sensor, touch sensor, ambient light sensor and bone conduction sensor.
  • the structure illustrated in this embodiment does not constitute a specific limitation on the electronic device 200 .
  • the electronic device 200 may include more or fewer components than shown, or combine some components, or separate some components, or different component arrangements.
  • the illustrated components 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 (application processor, AP), a modem processor, a graphics processor (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), controller, memory, video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural-network processing unit (NPU) Wait. Wherein, different processing units may be independent devices, or may be integrated in one or more processors.
  • application processor application processor, AP
  • modem processor graphics processor
  • ISP image signal processor
  • controller memory
  • video codec digital signal processor
  • DSP digital signal processor
  • NPU neural-network processing unit
  • the controller may be the nerve center and command center of the electronic device 200 .
  • the controller can generate an operation control signal according to the instruction operation code and timing signal, and complete the control of fetching and executing instructions.
  • a memory may also be provided in the processor 210 for storing instructions and data.
  • the memory in processor 210 is cache memory.
  • the memory may hold instructions or data that have just been used or recycled by the processor 210 . If the processor 210 needs to use the instruction or data again, it can be called directly from the memory. Repeated accesses are avoided, and the waiting time of the processor 210 is reduced, thereby improving the efficiency of the system.
  • the processor 210 may include one or more interfaces.
  • the interface may include an integrated circuit (inter-integrated circuit, I2C) interface, an integrated circuit built-in audio (inter-integrated circuit sound, I2S) interface, a pulse code modulation (pulse code modulation, PCM) interface, a universal asynchronous transceiver (universal asynchronous transmitter) receiver/transmitter, UART) interface, mobile industry processor interface (MIPI), general-purpose input/output (GPIO) interface, subscriber identity module (SIM) interface, and / or universal serial bus (universal serial bus, USB) interface, etc.
  • I2C integrated circuit
  • I2S integrated circuit built-in audio
  • PCM pulse code modulation
  • PCM pulse code modulation
  • UART universal asynchronous transceiver
  • 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 this embodiment is only a schematic illustration, and does not constitute a structural limitation of the electronic device 200 .
  • the electronic device 200 may also adopt different interface connection manners in the foregoing embodiments, or a combination of multiple interface connection manners.
  • the charging management module 240 is used to receive charging input from the charger.
  • the charger may be a wireless charger or a wired charger. While the charging management module 240 charges the battery 242 , the power management module 241 can also supply power to the electronic device.
  • the power management module 241 is used to connect the battery 242 , the charging management module 240 and the processor 210 .
  • the power management module 241 receives input from the battery 242 and/or the charging management module 240, and supplies power to the processor 210, the internal memory 221, the external memory, the display screen 294, the camera 293, and the wireless communication module 260.
  • the power management module 241 and the charging management module 240 may also be provided in the same device.
  • the wireless communication function of the electronic device 200 may be implemented by the antenna 1, the antenna 2, the mobile communication module 250, the wireless communication module 260, the modulation and demodulation processor, the baseband processor, and the like.
  • the antenna 1 of the electronic device 200 is coupled with the mobile communication module 250
  • the antenna 2 is coupled with the wireless communication module 260, so that the electronic device 200 can communicate with the network and other devices through wireless communication technology.
  • Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals.
  • Each antenna in electronic device 200 may be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization.
  • the antenna 1 can be multiplexed as a diversity antenna of the wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.
  • the mobile communication module 250 may provide a wireless communication solution including 2G/3G/4G/5G, etc. applied on the electronic device 200 .
  • the mobile communication module 250 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), and the like.
  • the mobile communication module 250 can receive electromagnetic waves from the antenna 1, filter and amplify the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation.
  • the mobile communication module 250 can also amplify the signal modulated by the modulation and demodulation processor, and then convert it into electromagnetic waves for radiation through the antenna 1 .
  • at least part of the functional modules of the mobile communication module 250 may be provided in the processor 210 .
  • at least part of the functional modules of the mobile communication module 250 may be provided in the same device as at least part of the modules of the processor 210 .
  • the wireless communication module 260 can provide applications on the electronic device 200 including WLAN (such as (wireless fidelity, Wi-Fi) network), Bluetooth (bluetooth, BT), global navigation satellite system (global navigation satellite system, GNSS), frequency modulation ( frequency modulation, FM), near field communication technology (near field communication, NFC), infrared technology (infrared, IR) and other wireless communication solutions.
  • WLAN such as (wireless fidelity, Wi-Fi) network
  • Bluetooth bluetooth, BT
  • global navigation satellite system global navigation satellite system, GNSS
  • frequency modulation frequency modulation, FM
  • near field communication technology near field communication, NFC
  • infrared technology infrared, IR
  • the wireless communication module 260 may be one or more devices integrating at least one communication processing module.
  • the wireless communication module 260 receives electromagnetic waves via the antenna 2 , modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 210 .
  • the wireless communication module 260 can also receive the signal to be sent from the processor 210 , perform frequency modulation on the signal, amplify the signal, and then convert it into an electromagnetic wave for radiation through the antenna 2 .
  • the electronic device 200 implements a display function through a GPU, a display screen 294, an application processor, and the like.
  • the GPU is a microprocessor for image processing, and is connected to the display screen 294 and the application processor.
  • the GPU is used to perform mathematical and geometric calculations for graphics rendering.
  • Processor 210 may include one or more GPUs that execute program instructions to generate or alter display information.
  • Display screen 294 is used to display images, videos, and the like.
  • the display screen 294 includes a display panel.
  • the electronic device 200 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 ISP is used to process the data fed back by the camera 293 .
  • Camera 293 is used to capture still images or video.
  • the electronic device 200 may include 1 or N cameras 293 , where N is a positive integer greater than 1.
  • 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 electronic device 200.
  • the external memory card communicates with the processor 210 through the external memory interface 220 to realize the data storage function. For example to save files like music, video etc in external memory card.
  • Internal memory 221 may be used to store computer executable program code, which includes instructions.
  • the processor 210 executes various functional applications and data processing of the electronic device 200 by executing the instructions stored in the internal memory 221 .
  • the processor 210 may execute instructions stored in the internal memory 221, and the internal memory 221 may include a program storage area and a data storage area.
  • the storage program area can store an operating system, an application program required for at least one function (such as a sound playback function, an image playback function, etc.), and the like.
  • the storage data area can store data (such as audio data, phone book, etc.) created during the use of the electronic device 200 and the like.
  • the internal memory 221 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, universal flash storage (UFS), and the like.
  • the electronic device 200 may implement audio functions through an audio module 270, a speaker 270A, a receiver 270B, a microphone 270C, an earphone interface 270D, and an application processor. Such as music playback, recording, etc.
  • the keys 290 include a power-on key, a volume key, and the like. Keys 290 may be mechanical keys. It can also be a touch key. Motor 291 can generate vibrating cues. The motor 291 can be used for vibrating alerts for incoming calls, and can also be used for touch vibration feedback. The indicator 292 can be an indicator light, which can be used to indicate the charging status, the change of power, and can also be used to indicate messages, missed calls, notifications, and the like.
  • the SIM card interface 295 is used to connect a SIM card. The SIM card can be contacted and separated from the electronic device 200 by inserting into the SIM card interface 295 or pulling out from the SIM card interface 295 .
  • the electronic device 200 may support 1 or N SIM card interfaces, where N is a positive integer greater than 1.
  • the SIM card interface 295 can support Nano SIM card, Micro SIM card, SIM card and so on.
  • the software architecture of the electronic device may include an application layer, an application framework layer, a hardware abstraction layer (HAL) and a driver layer.
  • the embodiments of the present application are described by taking as an example that the operating system of the electronic device is a dual-frame operating system (ie, the Android system and the Hongmeng system).
  • the electronic device may also be an Android system, a Hongmeng system, an IOS system, or other operating systems, which are not limited in the embodiments of the present application.
  • the application layer may include Android applications and Hongmeng applications.
  • the Android application may include a device manager (device manager) kit and a distributed execution framework (distributed execute framework, DEF) kit.
  • the kit (service) may be a software development kit (software development kit, SDK) used to provide basic services to the application layer (application programs).
  • SDK software development kit
  • DM kit can include device discovery module, trusted device maintenance module, device authentication module, device screening, sorting module, etc.
  • Harmony apps can include DM kit and Harmony SDK.
  • the SDK may refer to a collection of related documents, examples and tools that assist in the development of a certain type of software.
  • the DM kit can include a device discovery module, a trusted device maintenance module, a device authentication module, a device screening, and a sorting module.
  • the application layer may also include applications such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, short message, etc., which are not limited in this application.
  • the application framework layer can include DM, DEF, distributed scheduler manager Service (DMS), two-dimensional code identification module (hivision), Hongmeng label management module, security management module, communication module, device profile (device profile) ).
  • the application framework layer may also include an activity manager, a window manager, a content provider, a resource manager, a notification manager, and the like, which are not limited in this embodiment of the present application.
  • the device management module (DM module): mainly provides device discovery, trusted device maintenance and device authentication capabilities. By maintaining local device information, writing information into QR code, scanning code for identification, establishing physical connection and maintaining device group information to establish a secure and reliable connection between devices with the same account or different accounts, between Android and Hongmeng devices .
  • the DM may include a device discovery module, a trusted device maintenance module, a device authentication module, and a device sorting and screening module.
  • the device discovery module is used for processing such as sending broadcasts, discovering devices, encapsulating device information, and device list pop-up UI.
  • the trusted device maintenance module is used to query the trusted device list, write trusted device information, maintain the trusted device list, monitor the online and offline of trusted devices, and so on.
  • the device authentication module is used for bottom channel management, access control, PIN code mechanism and group management.
  • the device sorting and screening module is used for processing such as device screening and device sorting.
  • Hongmeng label management module responsible for providing Hongmeng label application, analysis, formatting, Hongmeng label service query and service distribution capabilities.
  • Distributed Execution Framework responsible for providing atomic service discovery, registration, query, and migration; responsible for underlying data communication and device discovery between devices.
  • QR code identification module Provides Hongmeng label generation and code scanning capabilities, generates a Hongmeng QR code label through the label information provided by the label service, and triggers the label service to parse the label information by scanning the Hongmeng QR code label.
  • Security management module manages groups in distributed scenarios and device group authentication; groups include public groups and application-level private groups. Provides secure and trusted communication and connection between devices and between applications and applications in distributed scenarios.
  • Soft bus manages self-discovery and self-organization of devices with the same account in distributed scenarios; scans and discovers devices with different accounts; provides channels for communication between different devices to ensure safe and stable data transmission.
  • DMS It mainly completes cross-device service binding and cross-device Android interface definition language (AIDL) interface calling capability.
  • AIDL is a description language for defining server and client communication interfaces.
  • Device information database responsible for reading, writing, storing and managing device information.
  • HAL can include microphones, speakers, Wi-Fi modules, Bluetooth modules, cameras, sensors, etc.
  • the driver layer is the layer between hardware and software, also known as the kernel layer.
  • the kernel layer contains at least display drivers, camera drivers, audio drivers, and sensor drivers.
  • the above software architecture can be deployed on multiple electronic devices in the current networking environment (for example, mobile phone 101, mobile phone 102, tablet computer 103, laptop computer 104, smart TV 105, router 106, etc. in FIG. 1 or FIG. 2 , etc. ).
  • Ability is an abstraction of the capabilities of an application.
  • An application can contain one or more abilities. HarmonyOS supports application deployment in units of Ability. There are two types of Ability: FA (Feature Ability) and AA (Meta Ability).
  • AA Developed by the third party based on the Hongmeng system service, a program entity that implements a single function, is used to provide the ability to run tasks in the background, and has no UI interface. AA has the characteristics of multi-terminal deployment and distributed execution. AA has dependencies on system services, and there is no dependency between AA.
  • FA Used to provide the ability (functionality) to interact with the user.
  • An FA can contain a set of related pages (which can also be thought of as a set of UIs), and each page can be represented by an instance of AbilitySlice.
  • FA can realize program entities with complex functions by calling AA, and it can be developed based on the structure of new interface/data/logic separation, and can be packaged and put on the shelves independently.
  • FA has the following capabilities: no installation, independent operation from applications, cross-device UI migration, and cross-device binary migration.
  • FA is partly similar to the UI interface of applet or quick app, but it is different in essence.
  • the difference can include two points, one is that FA can be migrated across devices (for example, the FA of mobile phone A can be migrated to mobile phone B, so that mobile phone B can control the FA of mobile phone A); the other is that FA can be cross-platform, for example, FA It can run on both the Android system and the Hongmeng system.
  • the current mini programs or quick apps usually run on the Android system.
  • FA sharing technology can be used to share FA between different devices, that is, FA of one device can be migrated to another device for display and operation.
  • authentication is required to ensure the safety and reliability of FA sharing.
  • the embodiment of the present application provides a function migration method, which includes device-level authentication and application-level authentication.
  • application-level authentication between different devices, specific applications between different devices can communicate with each other (that is, applications can exchange service data, such as FA migration).
  • the first application of device A and the first application of device B are mutually authenticated, the first application of device A and the first application of device B can communicate with each other, but other applications (such as the second application) of device A and the device can communicate with each other.
  • Other applications of B eg, the second application
  • device-level authentication all applications between different devices can communicate with each other.
  • the following takes mobile phone A and mobile phone B as examples to introduce the user interface (user interface, UI) interface of the device-level authentication provided in the embodiment of the present application.
  • UI user interface
  • the user may enter the smart collaboration interface 501 from the settings application, and the smart collaboration interface 501 may include a list named "My Devices".
  • My Devices includes this machine (ie mobile phone A), kiki's Mate pad and kiki's Mate book pro.
  • This machine, kiki's Mate pad and kiki's Mate book pro can be devices with the same account (for example, sharing a Huawei account).
  • the machine, kiki's Mate pad and kiki's Mate book pro can be devices with different accounts but authenticated (for the authentication process, please refer to the relevant description below).
  • the smart collaboration interface 501 may include a button 502 for binding other devices.
  • binding refers to establishing a trusted relationship between two devices, so that any applications of the two devices can communicate with each other, for example, FAs can be migrated to each other without authentication.
  • the user's operation eg, click operation
  • the bind other device button 502 as shown in (b) of FIG.
  • the positions, names and shapes of elements for example, buttons, icons, text, etc.
  • the button 502 in (a) in FIG. 5A may be replaced with the button 503 and the button 504 in (b) in FIG. 5A .
  • the mobile phone A can display the touch add interface 505, and the touch add interface 505 can display a pop-up frame 506 , the pop-up frame 506 includes a prompt picture and prompt information, for example, the prompt information can be: "touch to add, after the mobile phone turns on NFC, touch the ontag tag on the device with the back.” Users can follow the prompts to add new devices with just one touch.
  • the prompt information can be: "touch to add, after the mobile phone turns on NFC, touch the ontag tag on the device with the back.” Users can follow the prompts to add new devices with just one touch.
  • the mobile phone A may display the scan to add interface 507, and the scan to add interface 507 may include a prompt picture and prompt information, for example, the prompt information may be: "scan the QR code on the device or the package". Users can operate according to the prompt information to add new devices by swiping.
  • the mobile phone A can display a pop-up frame 508, and the pop-up frame 508 includes the prompt message "Please ensure that the device is turned on and located near the mobile phone", and the pop-up frame 508 may also include that the mobile phone A is based on a short-range communication network (for example, Wi-Fi network or Bluetooth network) detected devices, such as room TV, HUAWEI P20 and Mate book X pro and other devices.
  • a short-range communication network for example, Wi-Fi network or Bluetooth network
  • a prompt message 510 "Waiting for confirmation from the peer end" may be displayed below the logo of the HUAWEI P20.
  • a cancel button 511 may also be displayed in the pop-up box 508. In response to the user's operation of clicking the cancel button 511, the mobile phone A may return to the interface shown in (a) of FIG. 5C.
  • mobile phone A may display a new device binding interface 512, and the new device binding interface 512 may include a prompt The information "Scan the QR code displayed on the opposite end", and the user can operate according to the prompt information in order to add a new device.
  • the embodiments of the present application do not limit the jump relationship between different UI interfaces. For example, as shown in (b) of FIG. 5C , in response to the user's operation of clicking the binding button 509 , as shown in (b) of FIG. 5D , the mobile phone may directly display the scan interface 512 .
  • the mobile phone A may display a pop-up box 521, prompting the user "device authentication failed", and in response to the user's operation of clicking the know button 522, the pop-up box 521 may be hidden.
  • the pop-up frame 521 may disappear after a preset time (eg, 3s).
  • a preset time eg, 3s
  • mobile phone A may display a pop-up box 523, prompting the user "the peer is busy, please initiate binding later", in response to the user clicking the know button 524 operation, the pop-up box 523 can be hidden. Alternatively, the pop-up frame 523 may disappear after a preset time (eg, 3s).
  • mobile phone A may display a pop-up box 525, prompting the user that “the peer end refuses to trust this device, and the binding fails”, in response to the user clicking the know button 526 operation, the pop-up box 525 can be hidden. Alternatively, the pop-up frame 525 may disappear after a preset time (eg, 3s).
  • the mobile phone A may display a pop-up box 527 in the interface 512, prompting the user that "the QR code of the opposite end is closed, the device authentication cannot be completed, and the binding fails".
  • the pop-up box 527 may be hidden.
  • the peer device is mobile phone B (for example, it can be HUAWEI P20)
  • mobile phone B can display a pop-up frame 531
  • the pop-up box 531 may include prompt information 532 "HUAWEI MATE30 requests to bind this machine, whether to trust this device"
  • the pop-up box 531 may also include a distrust button 533 and a trust button 534.
  • a countdown (for example, 14s) may also be displayed in the untrusted button. When the countdown ends, if the user does not click any button, the pop-up box 531 may be automatically hidden.
  • the mobile phone A can perform an authentication process with the mobile phone B (refer to the related description of steps 718A-732 below), so that the mobile phone A can bind the mobile phone B.
  • the mobile phone B receives the binding request of the mobile phone A in the screen-off state or the screen-locked state, as shown in (b) in FIG.
  • the smart collaboration application receives a device binding request at 7:30 am.
  • it can be "HUAWEI MATE30 (ie mobile phone A) requests to bind this device, do you trust this device?"
  • the pop-up box 536 can be changed to the form of a pop-up box 531, and the user can choose to trust or not trust the HUAWEI MATE 30 (i.e., mobile phone A).
  • mobile phone B can display a pop-up frame 541 in the video interface or game interface 540, and the pop-up frame 541 can Prompt the user that the smart collaboration application receives a device binding request, which can be "HUAWEI MATE30 requests to bind this machine, do you trust this device?".
  • the pop-up box 541 may display more information, for example, a distrust button 543 and a trust button 544 may be displayed.
  • a countdown (for example, 14s) may also be displayed in the distrust button 543.
  • the pop-up box 541 may be automatically hidden.
  • the mobile phone A may perform an authentication process with the mobile phone B (refer to the related descriptions of steps 718A-732 below).
  • the mobile phone B in response to the user's operation of clicking the trust button, as shown in FIG. 6C , the mobile phone B may return to the desktop 530 and display a pop-up frame 550 , which may include the two-dimensional code 551 generated by the mobile phone B. , can also include the prompt message 552 "Scan to bind, allow HUAWEI MATE30 to scan and bind to this machine".
  • the user of mobile phone A can scan the QR code displayed by mobile phone B with mobile phone A, so that mobile phone A and mobile phone B can be bound.
  • the pop-up box 550 may further include a cancel button 553, and in response to the user's operation of clicking the cancel button 553, the pop-up box 550 may be hidden.
  • mobile phone A and mobile phone B are logged into the same account (for example, a Huawei account)
  • mobile phone A can be directly bound with mobile phone B (for example, as shown in (b) in FIG. 5C , click on mobile phone A
  • the binding button corresponding to mobile phone B (HUAWEI P20)
  • there is no need to wait for confirmation from mobile phone B for example, there is no need to wait for confirmation from the peer end as in (a) in Figure 5D, and there is no need to scan the peer end as in (b) in Figure 5D displayed QR code).
  • mobile phone A and mobile phone B are different account devices. As shown in Figure 7A, including:
  • the user triggers an operation of binding the mobile phone B on the mobile phone A.
  • the user may click the binding button corresponding to the mobile phone B on the mobile phone A.
  • the binding button 509 corresponding to the mobile phone B (HUAWEI P20) on the mobile phone A
  • the mobile phone A performs step 702.
  • the setting application of the mobile phone A initiates a binding request to the DM of the mobile phone A.
  • the setting application refers to an application named "settings", which is used to configure the basic functions of mobile phone A, such as network configuration, display and brightness configuration, sound and vibration configuration, application management configuration, etc. .
  • the information carried in the binding request may include the name of mobile phone A (for example, HUAWEI MATE30).
  • the DM of the mobile phone A requests the information of the authenticated device from the device information database of the mobile phone A.
  • the DM of mobile phone A can read the information of the authenticated device from the device information database.
  • the device information database stores information of devices that have been authenticated with the mobile phone A.
  • the information of the authenticated device may include a device name and a device ID.
  • the device ID may be, for example, an International Mobile Equipment Identity (IMEI).
  • IMEI International Mobile Equipment Identity
  • the information of the device authenticated with the mobile phone A may be as shown in Table 1.
  • the device information database of the mobile phone A returns the information of the authenticated device to the DM of the mobile phone A.
  • the information of the authenticated device may include the information of the mobile phone B.
  • steps 703 and 704 are optional. If steps 703 and 704 are executed, that is, if the information of the authenticated device is obtained, the mobile phone A can display the authenticated device to the user.
  • the authenticated device can be in the bound state by default, or the authenticated device can be re-bound.
  • Steps 703 and 704 are a schematic implementation of the DM of the mobile phone A to obtain the information of the authenticated device, and the DM of the mobile phone A can also obtain the information of the authenticated device in other ways (for example, read the information of the authenticated device from the preset storage space. information of the authentication device), which is not limited in this application.
  • the DM of the mobile phone A requests the communication module of the mobile phone A for information of nearby devices.
  • Device management can call the communication module of device A through a resident service to continuously send broadcasts to the surrounding area, so that device management can discover all near-field devices (that is, all devices under near-field communication) by registering for the broadcast monitoring service. may include Wi-Fi communication, Bluetooth communication, etc.).
  • the DM can classify and display the certified devices in the near-field full-scale devices in the form of icons (kiki's Mate pad shown in (a) in Figure 5C ). , kiki's Mate book pro, etc.) and uncertified devices (room TV, HUAWEI P20 and Mate book X pro, etc. as shown in (b) in Figure 5C).
  • step 703 there is no necessary execution sequence between step 703 and step 705, which is not specifically limited in this embodiment.
  • the communication module of the mobile phone A returns the information of the nearby devices to the DM of the mobile phone A.
  • the DM of mobile phone A pops up a list of nearby devices.
  • the DM of mobile phone A can invoke the pop-up box capability, so that a pop-up box 508 (that is, a list of nearby devices) pops up on the display screen of mobile phone A.
  • the pop-up box 508 includes the room TV, HUAWEI P20 and Nearby devices such as Mate book X pro.
  • the user selects a device to be bound.
  • the user can select the device to be bound from the list of nearby devices, for example, the user can select HUAWEI P20 (ie, mobile phone B).
  • HUAWEI P20 ie, mobile phone B.
  • the DM of the mobile phone A requests the communication module of the mobile phone A to create an underlying channel.
  • the underlying channel may be a Bluetooth channel or a Wi-Fi channel, etc., which is not limited in this application.
  • the communication module of the mobile phone A exchanges information with the communication module of the mobile phone B to create an underlying channel.
  • the communication module of mobile phone A sends a notification of successful creation to the DM of mobile phone A.
  • the communication module of mobile phone A sends a notification of successful creation of the underlying channel to the DM of mobile phone A, indicating that the underlying channel is successfully created between the communication module of mobile phone A and the communication module of mobile phone B.
  • step 711 is optional. If step 711 is performed, the DM of the subsequent mobile phone A can learn that the underlying channel is successfully created in time, so that data can be transmitted through the underlying channel subsequently. Alternatively, the success of the creation of the underlying channel may also be obtained based on other methods. For example, if a notification of failure of the creation of the underlying channel is not received after a preset time, it may be considered that the underlying channel has been created successfully.
  • the DM of the mobile phone A sends an authentication request message to the mobile phone B through the communication module of the mobile phone A.
  • the authentication request message may include an identification (eg, name or ID) of mobile phone A and identity authentication information generated by mobile phone A, and the identity authentication information generated by mobile phone A may include a token generated by mobile phone A.
  • the name of the mobile phone A can be, for example, HUAWEI MATE30.
  • the token can be, for example, a random string of several digits.
  • token can be used for identity authentication.
  • the mobile phone A may send a token to the mobile phone B, and the token may be the device number/device mac address of the mobile phone A, or other identifiers used to determine the mobile phone A.
  • the information of the token can be added to the QR code picture generated by mobile phone B subsequently, so that the QR code picture can only be used by mobile phone A.
  • the above method further includes:
  • the communication module of the mobile phone B sends a notification of successful creation to the DM of the mobile phone B.
  • the communication module of mobile phone B sends a notification that the bottom channel is successfully created to the DM of mobile phone B, indicating that the bottom channel is successfully created between the communication module of mobile phone B and the communication module of mobile phone A.
  • step 713 is optional. If step 713 is executed, the DM of the subsequent mobile phone B can timely learn that the underlying channel is successfully created, so that data can be transmitted through the underlying channel subsequently. Alternatively, the success of the creation of the underlying channel may also be obtained based on other methods. For example, if a notification of failure of the creation of the underlying channel is not received after a preset time, it may be considered that the underlying channel has been created successfully.
  • step 711 there is no necessary execution sequence between step 711 and step 713, which is not specifically limited in this embodiment.
  • the communication module of mobile phone A sends an authentication request message to the communication module of mobile phone B.
  • the communication module of mobile phone A can send an authentication request message to the communication module of mobile phone B through the underlying channel.
  • the communication module of the mobile phone B forwards the authentication request message to the DM of the mobile phone B.
  • step 712 , step 714 and step 715 are used to describe the process of mobile phone A sending an authentication request message to mobile phone B.
  • the DM of mobile phone A and the DM of mobile phone B need to communicate through the communication module of mobile phone A and the communication module of mobile phone B respectively.
  • the DM of mobile phone A and the DM of mobile phone B can also communicate through other modules, or the DM of mobile phone A
  • the DM with the mobile phone B may have the communication capability and can directly communicate, which is not limited in this application.
  • the DM of mobile phone B notifies the user whether to agree to the binding through a pop-up window.
  • the mobile phone A may pop up a pop-up box 531, and the pop-up box 531 may include prompt information 532 “HUAWEI MATE30 requests to bind this machine, whether to trust this device”, the pop-up box 531 A distrust button 533 and a trust button 534 may also be included.
  • the mobile phone B receives the operation that the user agrees to bind.
  • the user clicking the trust button 534 may indicate that the user agrees to the binding.
  • the DM of mobile phone B can return the information agreed by the user to the DM of mobile phone A through the communication module, and mobile phone A can prompt the user Actively scan the QR code (QR code picture) displayed by the peer (mobile phone B).
  • QR code QR code picture
  • the DM of the mobile phone B can return the information that the user does not agree to to the DM of the mobile phone A through the communication module, and the mobile phone A can display as shown in Figure 5E (c ), the binding failed.
  • steps 716 and 717 may be optional.
  • mobile phone A and mobile phone B may directly execute step 718A and subsequent necessary steps without requesting the user whether to agree to the binding.
  • Steps 716 and 717 are an implementation manner in which the mobile phone B prompts the user whether to agree to the binding.
  • the mobile phone B can also prompt the user in other ways, such as notification through a background system notification message, which is not limited in this application.
  • the DM of the mobile phone B determines whether the mobile phone B has established a group related to the mobile phone A.
  • the DM of mobile phone B can query whether mobile phone B has established a public group related to mobile phone A from the HiChain of mobile phone B.
  • the HiChain of mobile phone B can store all the group information established by mobile phone B, including public groups and private groups.
  • the public group may refer to a group established with the granularity of a device. For example, if two devices belong to a public group, it means that the two devices are authenticated at the device level, and all applications between the two devices can communicate with each other securely.
  • a private group refers to a group established with device and application granularity. For example, a first application of a first device can perform application-level authentication with a second application of a second device.
  • the first application and the second application belong to a private group, and at this time, the first application and the second application can securely communicate with each other (for example, data can be shared securely).
  • the identifiers of the first application and the second application may be the same or different, which is not limited in this application. If an application corresponding to the two devices belongs to a private group, it means that the two devices have been authenticated at the application level, and the specific applications corresponding to the two devices can communicate with each other securely. Exemplarily, all group information established by mobile phone B may be shown in Table 2:
  • Group 1 (Mobile B, Mobile C) Group 3 (App 1 on Phone B, App 2 on Phone D) Group 2 (Mobile B, Mobile D) Group 4 (application 1 of mobile phone B, application 3 of mobile phone E)
  • group 1 and group 2 in Table 2 may be combined into a group including 3 members, for example, group 5 (mobile phone B, mobile phone C, and mobile phone D).
  • group 5 mobile phone B, mobile phone C, and mobile phone D.
  • the mobile phone A can search for a device that has undergone device-level authentication with the mobile phone A from the group 5, without traversing the public group established between the two devices.
  • group 3 and group 4 in Table 2 can be combined into a group including 3 members, such as group 6 (application 1 of mobile phone B, application 2 of mobile phone D, application 3 of mobile phone E) .
  • group 6 application 1 of mobile phone B, application 2 of mobile phone D, application 3 of mobile phone E
  • the mobile phone A can search for the application of the device that has undergone application-level authentication with the mobile phone A from the group 6, without traversing the private group established between the two applications.
  • the DM of the mobile phone B requests the security management module of the mobile phone B to create a group.
  • the security module of mobile phone B creates a group about mobile phone A, and the group names are the device IDs of mobile phone A and mobile phone B. Further, the group attribute between mobile phone A and mobile phone B can be set to be public, that is, all applications between mobile phone A and mobile phone B can communicate with each other.
  • the security management module of the mobile phone B sends a group creation success notification to the DM of the mobile phone B.
  • step 718B and step 718C are a schematic way of creating a group, and the present application does not limit other ways of creating a group.
  • the DM of mobile phone B can directly create a group.
  • the DM of mobile phone B requests a label from the Hongmeng label management module of mobile phone B.
  • the Hongmeng label management module of mobile phone B can generate a label, and the label includes the authentication verification information and the session ID of mobile phone B.
  • the authentication verification information can include the token received from mobile phone A. Alternatively, it can be considered that the authentication verification information includes the token received from mobile phone A and the session identifier of mobile phone B.
  • the session identifier of the mobile phone B includes the device connection information of the mobile phone B. For example, the session identifier of the mobile phone B includes the Wi-Fi address of the mobile phone B (for example, an IP address and a port (Port) number) or a Bluetooth address.
  • the authentication verification information may also include the personal identification password PIN corresponding to the group.
  • the PIN can be, for example, several random numbers, such as 6-digit or 8-digit random numbers.
  • the mobile phone B may send the PIN corresponding to the group to the mobile phone A.
  • the PIN corresponding to the group can be carried in the request.
  • Mobile phone B determines that the PIN carried by mobile phone A is correct (that is, sent by mobile phone B to mobile phone A), considers mobile phone A to be safe and reliable, and allows mobile phone A to join the group created by mobile phone B.
  • the Hongmeng label management module of the mobile phone B requests the two-dimensional code picture (BitMap) of the authentication verification information from the two-dimensional code identification module of the mobile phone B.
  • the two-dimensional code identification module of mobile phone B can assemble the two-dimensional code picture according to the authentication verification information. It should be noted that the above-mentioned embodiments take a two-dimensional code image as an identifier for schematic illustration, and the two-dimensional code image may be replaced with other types of identifiers, such as barcodes, character strings, etc., which are not limited in this application.
  • the two-dimensional code identification module of the mobile phone B returns the two-dimensional code picture to the Hongmeng label management module of the mobile phone B.
  • the Hongmeng label management module of mobile phone B returns the QR code picture to the DM of mobile phone B.
  • the DM of the mobile phone B sends the two-dimensional code picture to the communication module of the mobile phone B.
  • the DM of mobile phone B can send the QR code picture of mobile phone B to mobile phone A through the communication module of mobile phone B, so that mobile phone A can scan the QR code picture internally, that is, after step 723a , steps 723b-725 may be performed.
  • mobile phone B can display the QR code picture of mobile phone B on the display interface of mobile phone B (the display interface shown in FIG. 6C ), so that mobile phone A can directly scan it, so that the QR code in mobile phone A can be directly scanned.
  • the two-dimensional code identification module can directly obtain the two-dimensional code picture generated by the mobile phone B, thereby skipping steps 723b to 725.
  • the communication module of the mobile phone B sends the two-dimensional code picture to the communication module of the mobile phone A.
  • the DM of mobile phone A can pull up the QR code recognition module, and scan the QR code image generated by mobile phone B through the QR code recognition module.
  • the above method further includes:
  • the communication module of the mobile phone A sends the QR code picture to the DM of the mobile phone A.
  • the DM of mobile phone A sends a two-dimensional code picture to the two-dimensional code identification module of mobile phone A.
  • the two-dimensional code identification module of mobile phone A scans the two-dimensional code picture, and sends the identified information to the Hongmeng label management module of mobile phone A.
  • the Hongmeng label management module of mobile phone A parses the information sent by the two-dimensional code identification module, and obtains the parsing result.
  • the parsing result may include information such as token, PIN, and session identifier of mobile phone B.
  • the Hongmeng label management module of mobile phone A sends the analysis result to the DM of mobile phone A.
  • steps 724 to 728 are a schematic implementation manner for mobile phone A to process two-dimensional code pictures, and mobile phone A can also process two-dimensional code pictures in other ways, which are not limited in this application.
  • the DM of mobile phone A can integrate the QR code image processing function, so that the DM of mobile phone A can directly scan and parse the QR code image to obtain information such as token, PIN, and session ID of mobile phone B.
  • step 730 is executed.
  • steps 729 and 730 are optional. If steps 729 and 730 are executed, that is, if the DM of mobile phone A checks the token, the security of the communication between mobile phone A and mobile phone B can be better guaranteed.
  • the mobile phone A joins the public group created by the mobile phone B.
  • the DM of mobile phone A determines the Wi-Fi address or Bluetooth address of mobile phone B according to the session identifier, and applies to the security module of mobile phone A to join the group created by mobile phone B.
  • the security module of the mobile phone A uses the Wi-Fi address or the Bluetooth address to create the underlying communication channel, and sends a group join request to the mobile phone B, and the group join request may include a group ID.
  • the request to join a group may further include a PIN.
  • the mobile phone B After the mobile phone B receives the request to join the group, it can verify the PIN. After the authentication is passed (that is, the PIN is the same as the PIN in the QR code picture), the two devices join the same group (the group members of the group can include Mobile phone A and mobile phone B, the attribute of the group is public) to complete the authentication.
  • mobile phone B After mobile phone B receives the request to join the group and passes the authentication, it will send a response message to mobile phone A, the response message indicating that mobile phone A has joined the public group created by mobile phone B.
  • the security management module of the mobile phone A notifies the application (setting application) that the authentication is successful.
  • the information of the group may include group members (the group members of the group may include mobile phone A and mobile phone B), and the information of the group may also include the group name and attribute information of the group (for example, the attribute is public).
  • device-level authentication is completed between mobile phone A and mobile phone B, and all applications between mobile phone A and mobile phone B can communicate with each other.
  • the live broadcast application, K song application, shopping application and mail application of mobile phone A can communicate with the live broadcast application, K song application, shopping application and mail application of mobile phone B.
  • mobile phone A and mobile phone B can perform all or part of the above steps 701-732. In order to verify (ie, perform device-level authentication) when mobile phone A and mobile phone B are bound, to ensure the security of data between devices.
  • an account for example, a Huawei account
  • device-level authentication In order to verify (ie, perform device-level authentication) when mobile phone A and mobile phone B are bound, to ensure the security of data between devices.
  • the mobile phone A and the mobile phone B may perform the above steps 701-732. In order to verify when mobile phone A and mobile phone B are bound to ensure the security of data between devices.
  • the mobile phone A and the mobile phone B can perform the above steps 701-732. In order to verify when mobile phone A and mobile phone B are bound, to further ensure the security of data between devices.
  • steps 701 to 732 may be optional, that is, they are not necessary technical features of the device-level authentication scheme.
  • steps 703 and 704 may be optional steps, that is, you may directly check the surrounding devices without querying the authenticated devices.
  • steps 711 and 713 may be optional steps, that is, a creation success notification may not be sent.
  • steps 716 and 717 may be optional steps, that is, they may be bound directly without the user's consent.
  • steps 723b to 725 may be optional steps, in which case mobile phone A can directly obtain the QR code picture generated by mobile phone B (for example, by scanning the QR code picture displayed by mobile phone B).
  • This application provides a distributed display solution based on cross-device FA sharing for live broadcast services.
  • the live broadcast screen of mobile phone A (the live broadcast screen of device A can be considered as an FA, such as FA1) can be shared to mobile phone B, and the mobile phone B can display the FA of mobile phone A and the live screen of mobile phone B at the same time (the live screen of device B can be considered as one FA, such as FA2), so as to achieve the experience of displaying one or more FAs across devices, saving users the tediousness of switching terminals back and forth , which greatly reduces user operations.
  • This application does not require devices to meet the requirements of the same system, nor does it require devices to log in to the same device account (for example, the same Huawei account), and has a wide range of applications.
  • mobile phone A may display a live broadcast interface 801 , and the live broadcast interface 801 may include a migration button 802 , which is located in the upper left corner of the interface 801 .
  • the migration button 802 may also be located at the lower left corner, the lower right corner, the upper right corner, etc. of the interface 801, which is not limited in this application.
  • the text displayed on the button 802 may also be other content, such as sharing, transfer, etc., which is not limited in this application.
  • the migration button 802 In response to the user clicking the migration button 802 on the live broadcast interface 801 (the migration button 802 is used to migrate (send) the live broadcast interface of mobile phone A to other devices (eg, mobile phone B)), as shown in (a) of FIG. 8B , the mobile phone A can pop up a pop-up box 803 .
  • the embodiments of the present application do not limit the way of jumping between UI interfaces.
  • the mobile phone may display a pop-up frame 803 in response to the operation of a user-specific gesture (eg, three-finger swipe, knuckle tap, etc.), as shown in (a) of FIG. 8B .
  • the pop-up box 803 may include nearby devices, and the nearby devices include certified devices (bedroom TV, monica's Mate pad, etc.) and uncertified devices (room TV, HUAWEI P20, Mate book X pro, etc.).
  • mobile phone A can send an authentication request message to mobile phone B.
  • a prompt message 805 “Waiting for confirmation from the peer end” can be displayed below the HUAWEI P20.
  • mobile phone B (HUAWEI P20) receives the authentication request message sent by mobile phone A when the live broadcast interface 811 is displayed
  • mobile phone B can display a pop-up frame 812
  • the pop-up frame 812 includes prompt information "HUAWEI MATE30 (mobile phone A) requests to migrate the live broadcast interface to this machine, do you agree?”
  • the pop-up box 812 can display more content, For example, a disagree button 814 and an agree button 815a are displayed.
  • the agree button 815a are displayed in response to the user's operation of clicking the agree button 815a, as shown in (c) in FIG.
  • the mobile phone may display a pop-up box 815b, and the pop-up box 815b may include the agree button 815c only this time and agree all the time (not in the future).
  • Reprompt) button 815d In response to the operation of the user clicking the agree button 815a or the agreement button 815c only this time or the agree button 815d all the time, as shown in FIG. 8D, the mobile phone B may display a pop-up box 816, and the pop-up box 816 may include the QR code image generated by the mobile phone B. , can also include the prompt message 817 "Scan for authentication, allow HUAWEI MATE30 to scan for authentication".
  • the user of mobile phone A can scan the QR code image displayed by mobile phone B, and then mobile phone B can receive the live broadcast screen (FA1) from mobile phone A.
  • mobile phone B can display the mobile phone on the live broadcast interface 811 The live broadcast interface 819 sent by A.
  • the mobile phone B can receive the live broadcast screen (FA1) from the mobile phone A.
  • the mobile phone B can display the live broadcast interface 819 sent by the mobile phone A on the live broadcast interface 811.
  • FIG. 9A including:
  • the mobile phone A receives an operation that the user triggers the function migration.
  • the user may click the transfer button 802 when the mobile phone A is broadcasting the host.
  • the migration button may also be called a share button, a send button, etc., which is not limited in this application.
  • the user can trigger the function migration in other ways, for example, the function migration can be triggered by the method of "touching” or “scanning", which is not limited in this application.
  • the application (for example, a live broadcast application) initiates a migration request to the DM of the mobile phone A.
  • the information carried in the migration request may include the identifier of the application at the originating end (the name of the live broadcast application at the local end), the identifier of the application at the connecting end (the name of the live broadcast application at the opposite end), and the name of the mobile phone A.
  • the package name of the connection terminal may be given by an application (for example, a live broadcast application), which depends on the design of the application by the application manufacturer, and will not be repeated here.
  • the information carried in the migration request may be arranged according to a preset order.
  • the preset sequence may be the name of the mobile phone A, the identifier of the application at the originating end, and the identifier of the application at the connecting end in sequence.
  • the preset sequence may be the identifier of the application at the originating end, the identifier of the application at the connecting end, and the name of the mobile phone A in sequence.
  • the DM of the mobile phone A requests an authenticated device from the device information database of the mobile phone A.
  • step 703 For the specific process, reference may be made to the relevant description in step 703, which is not repeated here.
  • the device information database of the mobile phone A returns the information of the authenticated device to the DM of the mobile phone A.
  • steps 903 and 904 are optional. If steps 903 and 904 are executed, that is, if the information of the authenticated device is obtained, the mobile phone A can display the authenticated device to the user.
  • Steps 903 and 904 are a schematic implementation of the DM of the mobile phone A to obtain the information of the authenticated device, and the DM of the mobile phone A can also obtain the information of the authenticated device in other ways (for example, read the information of the authenticated device from the preset storage space. information of the authentication device), which is not limited in this application.
  • the DM of the mobile phone A requests the communication module of the mobile phone A for information of nearby devices.
  • step 705 For the specific process, reference may be made to the relevant description in step 705, which is not repeated here.
  • the communication module of the mobile phone A returns the information of the nearby devices to the DM of the mobile phone A.
  • the DM of mobile phone A pops up a list of nearby devices.
  • the list of nearby devices may be, for example, a pop-up box 803 as shown in (a) of FIG. 8B .
  • the user can select a device from the list of nearby devices. If it is an untrusted device (that is, a device with a different account that has not been authenticated (for example, the same Huawei account has not been logged in)), after step 907, steps 908 to 936 can be performed to perform application-level Certification. If it is a trusted device (for example, it has logged into the same Huawei account, or has been authenticated before (including device-level authentication or application-level authentication)), the FA can be migrated directly, that is, after step 907, steps 933-936 can be executed directly .
  • an untrusted device that is, a device with a different account that has not been authenticated (for example, the same Huawei account has not been logged in)
  • steps 908 to 936 can be performed to perform application-level Certification.
  • the FA can be migrated directly, that is, after step 907, steps 933-936 can be executed directly .
  • the user selects an unauthenticated device.
  • HUAWEI P20 which is an untrusted device.
  • the DM of the mobile phone A requests the communication module of the mobile phone A to create an underlying channel.
  • the underlying channel may be a Bluetooth channel or a Wi-Fi channel, etc., which is not limited in this application.
  • the communication module of the mobile phone A exchanges information with the communication module of the mobile phone B to create an underlying channel.
  • the communication module of the mobile phone A sends a notification that the bottom channel is successfully created to the DM of the mobile phone A.
  • step 911 is optional. If step 911 is performed, the DM of the subsequent mobile phone A can timely learn that the underlying channel is successfully created, so that data can be transmitted through the underlying channel subsequently. Alternatively, the success of the creation of the underlying channel may also be obtained based on other methods. For example, if a notification of failure of the creation of the underlying channel is not received after a preset time, it may be considered that the underlying channel has been created successfully.
  • the DM of the mobile phone A sends an authentication request message to the mobile phone B through the communication module of the mobile phone A.
  • the authentication request message includes the device name of the initiator (for example, HUAWEI MATE30), the package name of the initiator (for example, com.zhibo.video), and the package name of the connection terminal (for example, com.zhibo.video).
  • the authentication request message also includes the token generated by mobile phone A.
  • the above method further includes:
  • the communication module of the mobile phone B sends a notification that the bottom channel is successfully created to the DM of the mobile phone B.
  • step 911 there is no necessary execution sequence between step 911 and step 913, which is not specifically limited in this embodiment.
  • step 913 is optional. If step 913 is executed, the DM of the subsequent mobile phone B can learn that the underlying channel is successfully created in time, so that data can be transmitted through the underlying channel subsequently. Alternatively, the success of the creation of the underlying channel may also be obtained based on other methods. For example, if a notification of failure of the creation of the underlying channel is not received after a preset time, it may be considered that the underlying channel has been created successfully.
  • the communication module of mobile phone A sends an authentication request message to the communication module of mobile phone B.
  • the information carried in the authentication request message may include the identifier of the application at the originating end, the identifier of the application at the connecting end and the name of the mobile phone A.
  • the information carried in the authentication request message may be arranged according to a preset order.
  • the preset sequence may be the name of the mobile phone A, the identifier of the application at the originating end, and the identifier of the application at the connecting end in sequence.
  • the preset sequence may be the identifier of the application at the originating end, the identifier of the application at the connecting end, and the name of the mobile phone A in sequence.
  • the communication module of the mobile phone B forwards the authentication request message to the DM of the mobile phone B.
  • step 912 , step 914 and step 915 are used to describe the process of mobile phone A sending an authentication request message to mobile phone B.
  • the DM of mobile phone A and the DM of mobile phone B need to communicate through the communication module of mobile phone A and the communication module of mobile phone B respectively.
  • the DM of mobile phone A and the DM of mobile phone B can also communicate through other modules, or the DM of mobile phone A
  • the DM with the mobile phone B may have the communication capability and can directly communicate, which is not limited in this application.
  • the DM of mobile phone B notifies the user whether to agree to the migration through a pop-up window.
  • the mobile phone B can display a pop-up box 812, and the pop-up box 812 includes prompt information. "HUAWEI MATE30 requests to migrate the live broadcast interface to this machine, do you agree?"
  • the pop-up box 812 can display more content, such as showing disagreement button 814 and agree button 815a.
  • the mobile phone may display a pop-up box 815b, and the pop-up box 815b may include the agree button 815c only this time and agree all the time (not in the future).
  • Reprompt) button 815d it should be understood that, in response to the user's operation of clicking the consent button 815c only this time, after performing the following steps 917-932, the mobile phone A can migrate the live broadcast interface (ie FA1) to the mobile phone B once.
  • steps 901 to 932 may be re-executed.
  • the live broadcast application of mobile phone A can always migrate FA to the live broadcast application of mobile phone B without re-authentication (for example, no need to re-execute steps 901-932). ).
  • the mobile phone B receives the operation that the user agrees to the migration.
  • the mobile phone B may receive the operation of the user clicking the agree button 815a.
  • the DM of the mobile phone B can return the information agreed by the user to the DM of the mobile phone A through the communication module, and the mobile phone A can prompt the user to actively scan the two displayed on the opposite end (mobile phone B).
  • QR code two-dimensional code picture
  • the DM of the mobile phone B can return the information that the user does not agree to to the DM of the mobile phone A through the communication module, and the mobile phone A can display as shown in Figure 5E (c ), the migration failed.
  • steps 916 and 917 may be optional.
  • mobile phone A and mobile phone B may directly perform step 918A and subsequent necessary steps without requesting the user whether to agree to the migration.
  • Steps 916 and 917 are an implementation manner of mobile phone B prompting the user whether to agree to the migration.
  • Mobile phone B may also prompt the user in other ways, such as notification through a background system notification message, which is not limited in this application.
  • the DM of mobile phone B determines whether mobile phone B has established a group related to the live broadcast application of mobile phone A.
  • the DM of mobile phone B can query whether mobile phone B has established a private group related to mobile phone A from the HiChain of mobile phone B. For related descriptions, reference may be made to step 718A, which will not be repeated here.
  • the DM of the mobile phone B requests the security management module of the mobile phone B to create a group.
  • the security module of mobile phone B may create a group about the live broadcast application of mobile phone A (group members of the group may include the live broadcast application of mobile phone A and the live broadcast application of mobile phone B). Further, the group attribute can be set to private, that is, only a specific application (live broadcast application) is applicable.
  • the mobile phone B may send the group ID of the group created by the mobile phone B about the live broadcast application of the mobile phone A to the mobile phone A.
  • Mobile phone A can join the group created by mobile phone B according to the group ID.
  • the mobile phone B may also send the device ID of the mobile phone B to the mobile phone A.
  • the device ID of the mobile phone B can be used when the mobile phone A communicates with the mobile phone B, and the device ID of the mobile phone B can include a network ID (netId) and a device IP (deviceIP).
  • the security management module of the mobile phone B sends a group creation success notification to the DM of the mobile phone B.
  • step 918B and step 918C are a schematic way of creating a group, and this application does not limit other ways of creating a group.
  • the DM of mobile phone B can directly create a group.
  • the DM of mobile phone B requests a label from the Hongmeng label management module of mobile phone B.
  • the Hongmeng label management module of mobile phone B can generate a label, and the label includes authentication verification information, and the authentication verification information can include the token received from mobile phone A and the session ID of mobile phone B and other information.
  • the session identifier of the mobile phone B includes the device connection information of the mobile phone B.
  • the session identifier of the mobile phone B includes the Wi-Fi address of the mobile phone B (for example, an IP address and a port (Port) number) or a Bluetooth address.
  • the authentication verification information may also include a PIN corresponding to the group.
  • the Hongmeng label management module of the mobile phone B requests the two-dimensional code picture of the authentication verification information from the two-dimensional code identification module of the mobile phone B.
  • the two-dimensional code identification module of mobile phone B can assemble the two-dimensional code picture according to the authentication verification information.
  • the two-dimensional code identification module of the mobile phone B returns the two-dimensional code picture to the Hongmeng label management module of the mobile phone B.
  • the Hongmeng label management module of mobile phone B returns the QR code picture to the DM of mobile phone B.
  • the DM of the mobile phone B sends the two-dimensional code picture to the communication module of the mobile phone B.
  • the DM of mobile phone B can send the QR code picture of mobile phone B to mobile phone A, so that mobile phone A scans the QR code picture internally, that is, after step 923a, steps 923b- Step 925.
  • the mobile phone B can display the QR code picture of the mobile phone B on the display interface of the mobile phone B (the display interface shown in FIG. 8D ), so that the mobile phone A can scan it directly, so that the The two-dimensional code identification module can directly obtain the two-dimensional code picture generated by the mobile phone B, thereby skipping steps 923b-925.
  • the communication module of the mobile phone B sends the two-dimensional code picture to the communication module of the mobile phone A.
  • the DM of mobile phone A can pull up the QR code recognition module, and scan the QR code image generated by mobile phone B through the QR code recognition module.
  • the above method further includes:
  • the communication module of the mobile phone A sends the two-dimensional code picture to the DM of the mobile phone A.
  • the DM of mobile phone A sends a two-dimensional code picture to the two-dimensional code identification module of mobile phone A.
  • the two-dimensional code identification module of mobile phone A scans the two-dimensional code, and sends the identified information to the Hongmeng label management module of mobile phone A.
  • the Hongmeng label management module of mobile phone A parses the information sent by the two-dimensional code identification module, and obtains the parsing result.
  • the analysis result may include information such as the token, PIN of the mobile phone B, and the session identifier of the mobile phone B.
  • the Hongmeng tag management module of mobile phone A sends the analysis result to the DM of mobile phone A.
  • steps 924 to 928 are a schematic implementation manner for mobile phone A to process two-dimensional code pictures, and mobile phone A can also process two-dimensional code pictures in other ways, which are not limited in this application.
  • the DM of mobile phone A can integrate the QR code image processing function, so that the DM of mobile phone A can directly scan and parse the QR code image to obtain information such as token, PIN, and session ID of mobile phone B.
  • step 930 is executed.
  • steps 929 and 930 are optional. If steps 929 and 930 are executed, that is, if the DM of mobile phone A checks the token, the security of the communication between mobile phone A and mobile phone B can be better guaranteed.
  • the DM of mobile phone A applies to the security module of mobile phone A to join the private group created by mobile phone B according to the session ID index of the Wi-Fi address or Bluetooth address of the peer device (that is, mobile phone B) stored at the local end.
  • the security module of mobile phone A uses the Wi-Fi address or Bluetooth address to create an underlying communication channel, and sends a group join request to mobile phone B, where the group join request includes the parsed PIN and group ID.
  • Mobile phone B receives the request to join the group, verifies the PIN, and passes the authentication (that is, the PIN is the same as the PIN in the QR code picture), the live broadcast application in the two devices joins the same group (the group of the group).
  • Members can include the live broadcast application of mobile phone A and the live broadcast application of mobile phone B, and the attribute of the group is private) to complete the authentication.
  • mobile phone B when mobile phone B receives the request to join the group and passes the authentication, it will send a response message to mobile phone A, the response message indicates that the live broadcast application of mobile phone A has joined the private group created by mobile phone B .
  • the security management module of mobile phone A notifies that the authentication of the live broadcast application is successful.
  • the live broadcast application of mobile phone A requests the DEF of mobile phone A to migrate to FA1.
  • FA1 can realize all or part of the functions in the live broadcast application, and it consists of one or more user interfaces.
  • the DEF of the mobile phone A sends the service information of the FA1 to the DMS of the mobile phone B.
  • the service information of FA1 may include live video stream, audio stream, bullet screen information and so on.
  • the DMS of the mobile phone B requests the DEF of the mobile phone B to connect to FA1.
  • the DEF connection FA1 of the mobile phone B means that the mobile phone B processes and displays the FA1 according to the received service information.
  • the display content of FA1 on mobile phone B may be synchronized with the display content of FA1 on mobile phone A, or there may be differences in format or partial content with the display content of FA1 on mobile phone A, which is not limited in this application.
  • DEF of mobile phone B can detect FA2 of mobile phone B. If FA2 has the ability to display FA1 (that is, FA2 supports displaying multiple FAs), DEF can be pulled up on FA2 Show live FA1, that is, show the FA1 interface on the FA2 interface. For example, as shown in FIG. 8E , the mobile phone B may display the live broadcast interface 819 sent by the mobile phone A on the live broadcast interface 811 .
  • the user can watch the live screen of mobile phone B and the live screen of mobile phone A on mobile phone B at the same time, so as to achieve the experience of displaying one or more FAs across devices, which saves the user the tediousness of switching terminals back and forth, and simplifies user operations. Improve user experience.
  • FA for example, FA4
  • mobile phone B migrates the FA (for example, FA4) on mobile phone C to mobile phone B, and mobile phone B is currently in the FA2 display interface
  • FA2 has the ability to display multiple FAs
  • mobile phone B can display 3 FAs at the same time.
  • FA FA1, FA2, and FA3
  • the embodiments of the present application are mainly applied to the scenario of sharing FAs between live broadcast applications across devices, that is, through the FA sharing of multiple devices, a certain device can display multiple FA scenarios at the same time, so that dual-view dual-screen live broadcasting can be freely performed , which can be used to evaluate live broadcast (out-of-the-box close-up + anchor), sports director (athlete's perspective + commentary), education live broadcast (book close-up + teacher), e-commerce live broadcast (product details + show guide) and other scenarios, which can improve user experience and Product competitiveness.
  • the mobile phone A and the mobile phone B can perform the above steps 901-936.
  • verification ie, perform device-level authentication
  • FA migration between mobile phone A and mobile phone B, to ensure the security of data (for example, FA1) between devices.
  • the mobile phone A and the mobile phone B may perform the above steps 901-936. In order to verify the FA migration between mobile phone A and mobile phone B to ensure the security of data between devices.
  • mobile phone A and mobile phone B may perform steps 901 to 936 above. In order to verify the FA migration between mobile phone A and mobile phone B, to further ensure the security of data between devices.
  • steps 901 to 936 may be optional, that is, they are not necessary technical features of the application-level authentication scheme.
  • steps 903 and 904 may be optional steps, that is, you may directly check the surrounding devices without querying the authenticated devices.
  • steps 911 and 913 may be optional steps, that is, a creation success notification may not be sent.
  • steps 916 and 917 may be optional steps, that is, direct migration may be performed without the user's consent.
  • steps 923b to 925 may be optional steps, in which case mobile phone A can directly obtain the QR code picture generated by mobile phone B (for example, by scanning the QR code picture displayed by mobile phone B).
  • the following describes the UI interface of the application-level authentication provided by the embodiment of the present application by taking a photographing application as an example in conjunction with a specific scenario.
  • the present application provides a method, based on cross-device FA sharing technology, establishes a connection between two devices, uses one device (for example, mobile phone A) as a camera phone, and migrates the camera FA of a remote device to another device (for example, mobile phone A) , mobile phone B), in this way, the user can observe the photographing screen of mobile phone A by holding the mobile phone B and control the photographing, which helps the user to take more satisfactory photos and can improve the user experience.
  • mobile phone A when the user uses mobile phone A to take a picture, mobile phone A displays a photographing interface 1001, and the photographing interface includes a preview frame and a menu area.
  • mobile phone A can send the camera interface of mobile phone A (the camera interface of mobile phone A can be regarded as an FA, for example, FA5) to mobile phone B, as shown in FIG. 10B , Mobile phone B can display the camera interface of mobile phone A, and mobile phone B can control the camera interface of mobile phone A.
  • the camera interface of mobile phone A can be regarded as an FA, for example, FA5
  • mobile phone B can display the camera interface of mobile phone A
  • mobile phone B can control the camera interface of mobile phone A.
  • user A may click the migration button 1002 in the photographing interface 1001 .
  • the camera application of the mobile phone A initiates a migration request to the DM of the mobile phone A.
  • the information carried in the migration request includes the package name of the initiator (package name of the camera application at the local end), the package name of the connection end (the package name of the camera application at the opposite end), and the name of the mobile phone A.
  • steps 1103 to 1132 reference may be made to the related descriptions of steps 903 to 932, which will not be repeated here. Some of the steps in steps 903-932 may be optional.
  • the camera application of the mobile phone A requests the DEF of the mobile phone A to migrate to FA5.
  • the DEF of the mobile phone A sends the relevant information of the FA5 to the DMS of the mobile phone B.
  • the relevant information of the FA5 may include the shooting preview screen and the menu bar information of the shooting interface.
  • the DMS of the mobile phone B requests the DEF of the mobile phone B to connect to the FA5.
  • the DEF of the mobile phone B is connected to FA5 means that the mobile phone B processes and displays FA5 according to the received service information.
  • the mobile phone B can display and control the camera interface (FA5) of the mobile phone A.
  • the cross-device FA sharing technology enables two devices to establish a connection, and shares the FA5 of mobile phone A to mobile phone B, so that the shooting interface can be previewed on mobile phone B, and the camera function of mobile phone A can also be controlled, which is helpful for Users can take more satisfactory photos, which can improve the user experience.
  • the following describes the UI interface of the application-level authentication provided by the embodiment of the present application by taking the K song application as an example in conjunction with a specific scenario.
  • the present application provides a multi-device collaborative control scheme based on FA sharing for the K song scenario, which supports cross-device application-level mutual assistance sharing under the same network (eg, the same Wi-Fi network).
  • the karaoke service of the local machine for example, mobile phone A
  • the karaoke service of the local machine can be seamlessly transferred to other terminal devices (for example, TV, speakers); at the same time, it does not require user account authorization to log in, and does not require multiple terminal devices to use the same system .
  • the advantages of the audio and video playback experience of devices such as TVs and speakers can be brought into play, and the advantages of devices such as mobile phones are convenient for interaction and easy to pick up sound, and the operation steps are simple and quick, which greatly improves the user experience.
  • mobile phone A can display the karaoke interface 1201, in response to the operation of the user clicking the karaoke button 1202 corresponding to the song “red beans”, as shown in FIG. 12A
  • the mobile phone A can display the karaoke interface 1203 of the red bean, in response to the user clicking the migration button 1204 (the migration button 1204 is used to migrate (send) the karaoke interface of the mobile phone A to other devices (for example, a mobile phone).
  • B)) operation as shown in (a) of FIG.
  • the mobile phone can pop up a pop-up box 1205, which can include nearby devices, and the nearby devices include authenticated devices (bedroom TV, monica's Mate pad, etc.) and uncertified devices (room TV, Brian's Mate pad and Mate book X pro, etc.).
  • the mobile phone A may send an authentication request message to the mobile phone B.
  • a prompt message 1207 “waiting for confirmation from the peer end" may be displayed below the room TV. As shown in FIG.
  • the TV can display a pop-up box 1210, which includes a prompt message “HUAWEI MATE30 (mobile phone A) requests to migrate the K-song service to this machine, do you agree?”
  • the pop-up box 1210 may also include disagreement button 1212 and agree button 1213.
  • the TV can display a pop-up box 1214, and the pop-up box 1214 may include a QR code image generated by the TV, and may also include a prompt message 1215 “Scan for authentication, allow HUAWEI MATE30 swipe for certification”.
  • the user of mobile phone A can scan the QR code picture displayed on the TV, and then the TV can receive the karaoke interface from mobile phone A (the karaoke interface can be regarded as an FA, such as FA6), as shown in Figure 12E, the TV The karaoke interface 1217 can be displayed.
  • the television may receive the karaoke interface (FA6) from the mobile phone A, as shown in FIG. 12E, the television may display the karaoke interface 1217.
  • mobile phone A can rearrange the UI, as a song ordering console, the user performs operations such as ordering songs, cutting songs, etc. on mobile phone A, and the song list information will be synchronously sent to the TV through the communication data channel. Controls the playback of music on the TV side.
  • FIG. 13 A specific implementation manner of the method provided by the embodiment of the present application will be described below by taking a karaoke application as an example.
  • the method provided in this embodiment of the present application can be applied to two near-field devices on the same network, such as mobile phone A and a TV, where mobile phone A can be an Android system or a dual-frame system, the TV can be a Hongmeng system, and mobile phone A and TV are different account device.
  • mobile phone A can be an Android system or a dual-frame system
  • the TV can be a Hongmeng system
  • mobile phone A and TV are different account device.
  • Figure 13 including:
  • the K song application of the mobile phone A initiates a migration request to the DM of the mobile phone A.
  • the information carried in the migration request includes the package name of the initiating end (the name of the karaoke application package of the local end), the package name of the connecting end (the name of the karaoke application package of the opposite end), and the name of the mobile phone A.
  • steps 1303 to 1332 reference may be made to the related descriptions of steps 903 to 932, which will not be repeated here. Some of the steps in steps 903-932 may be optional.
  • the K song application of mobile phone A requests the DEF of mobile phone A to migrate to FA6.
  • the DEF of the mobile phone A sends the relevant information of the FA6 to the DMS of the TV.
  • the related information of FA6 may include song information of K-song, and the song information includes at least one of song title (eg, red beans), lyrics, audio information and video information.
  • the DMS of the TV requests the DEF of the TV to connect to FA6.
  • the TV's DEF can detect whether the TV's K-song app and account are logged in, and prompt the user to log in to the K-song app, so that the K-song app can display the FA6 sent by mobile phone A.
  • the TV's DEF can pull up the FA6, which provides the ability to display the FA6, without the need to pre-install the karaoke app, which can achieve the effect of using the karaoke service instantly.
  • the embodiments of the present application provide a near-field application layer data sharing service for the karaoke entertainment scenario, which can realize one-key migration of FA across devices and operating systems without relying on any third-party platform, and does not require pre-installed karaoke applications.
  • the karaoke service can be used immediately, and a mobile karaoke room can be quickly built, which can improve the user experience, the operation is simple, and the entertainment experience is improved.
  • the following describes the UI interface of the application-level authentication provided by the embodiment of the present application by taking a shopping application as an example in conjunction with a specific scenario.
  • the present application provides an application-layer data sharing service based on near-field FA sharing, which supports one-key synchronization of shopping cart information between multiple terminal devices under the same network (for example, the same Wi-Fi network).
  • the shopping cart of one terminal device (the shopping cart can be regarded as an FA, for example, FA7) can be migrated to another terminal device, and the goods in the shopping carts of the two devices can be settled in a unified manner to enjoy the full discount, and then pay separately to save the
  • the troubles of mutual transfer, the operation steps are simple and fast, which can greatly improve the user experience of shopping.
  • the near-field FA sharing capability is the basic capability provided by system services, it does not require the same operating system, nor does it need to log in to the same device account (for example, a Huawei account), or even do not need to install a shopping application on the device. It is used by various e-commerce platforms, and the adaptation cost is small, allowing more users to enjoy a more convenient online shopping experience.
  • the mobile phone can pop up a pop-up box 1403, and the pop-up box 1403 can include nearby devices, and the nearby devices include Certified devices (bedroom TV, monica's Mate pad, etc.) and uncertified devices (room TV, HUAWEI P20 and Mate book X pro, etc.).
  • the nearby devices include Certified devices (bedroom TV, monica's Mate pad, etc.) and uncertified devices (room TV, HUAWEI P20 and Mate book X pro, etc.).
  • mobile phone A can send an authentication request message to mobile phone B. And, as shown in (b) of FIG. 14B , a prompt message 1405 “Waiting for confirmation from the peer end” can be displayed below the HUAWEI P20. As shown in FIG.
  • mobile phone B (HUAWEI P20) receives the authentication request message sent by mobile phone A when displaying the desktop, mobile phone B can display a pop-up frame 1410, and the pop-up frame 1410 includes the prompt message “HUAWEI MATE30 (mobile phone A) requests Migrate the shopping cart to the local machine, agree or not", the pop-up box 1410 may include a disagree button 1412 and an agree button 1413.
  • the mobile phone B may display a pop-up frame 1415, and the pop-up frame 1415 may include the QR code image generated by the mobile phone B, and may also include a prompt message 1416 "Scan a scan to bind.
  • the user of mobile phone A can scan the QR code picture displayed by mobile phone B, and then mobile phone B can receive the shopping cart (FA6) from mobile phone A, or, in response to the user's operation of clicking the agree button 1413, mobile phone B can receive the shopping cart from mobile phone A (FA6).
  • Mobile phone A receives the shopping cart (FA6).
  • the mobile phone B can display the shared shopping cart on the shopping cart interface 1417 , and the shared shopping cart includes both the products added by “me” and the products added by user A (the user of mobile phone A).
  • mobile phone B can also migrate its own shopping cart (for example, FA7) to mobile phone A, so that, as shown in FIG.
  • mobile phone A can display the shared shopping cart on the shopping cart interface 1407, and the shared shopping cart includes both “I "Added products also include products added by user B (user of mobile phone B).
  • the shared shopping cart includes both “I "Added products also include products added by user B (user of mobile phone B).
  • users can realize combined order shopping with one click, and do not need to rely on any third-party platform to share, which saves the tedious steps of sharing goods with each other and transferring money to each other, which greatly improves the shopping experience.
  • the user opens the shopping application on mobile phone A, selects a product to add to the shopping cart, and then enters the shopping cart interface 1401.
  • the user can click the migration button 1402 on the shopping cart interface 1401.
  • the shopping cart is migrated (sent) to another device (eg, phone B).
  • the shopping application initiates a migration request (sharing request) to the DM of mobile phone A.
  • the information carried in the migration request includes the package name of the initiator (the shopping application package name of the local terminal), the package name of the connecting terminal (the shopping application package name of the opposite terminal), and the name of the mobile phone A.
  • the package name of the initiator is such as com.huawei.vmall
  • the package name of the connecting end is such as com.huawei.vmall.
  • steps 1503 to 1532 reference may be made to the related descriptions of steps 903 to 932, which will not be repeated here. Some of the steps in steps 903-932 may be optional.
  • the shopping application of the mobile phone A requests the DEF of the mobile phone A to migrate to FA7.
  • the DEF of the mobile phone A sends the relevant information of the FA7 to the DMS of the mobile phone B.
  • the relevant information of the FA7 includes the commodity information in the shopping cart, and the commodity information includes at least one of commodity name, commodity link, commodity price and other information.
  • the DMS of the mobile phone B requests the DEF of the mobile phone B to connect to FA7.
  • mobile phone B pulls up FA7.
  • mobile phone B can display the shared shopping cart on the shopping cart interface 1417, which contains not only one item in its own shopping cart, but also three items selected by user A. .
  • user B can intuitively see all the products purchased by the order. After selecting some or all of the products in the shopping cart, the user can check whether the amount meets the full-reduction activity, realizing the fast order-combining function.
  • the product information in the shared shopping cart can be updated in real time. For example, there are new products in the shopping cart of the device that initiates the migration (for example, mobile phone A), and the shared shopping cart of the destination device (for example, mobile phone B) can be refreshed even.
  • mobile phone B can initiate a payment request to user A and carry payment-related information, which may include payment platform and payment amount.
  • the payment amount can be: the total amount of the purchased goods - (the total amount of each individual / the total amount of the shared shopping cart) * discount value.
  • the shopping cart of one terminal device (the shopping cart may be regarded as an FA, for example, FA7) can be migrated to another terminal device, and the commodities in the shopping carts of the two devices can be settled and enjoyed in a unified manner
  • the full discount, and then separate payment saves the trouble of mutual transfer, and the operation steps are simple and quick, which can greatly improve the user experience of combined order shopping.
  • a user in a home environment, a user holds a mobile phone and a TV and is participating in a shopping festival full of 400 minus 100 activities.
  • the user will frequently switch the product details page and the shopping cart page to view or modify the contents of the shopping cart during the process of selecting products on the mobile phone.
  • the user can migrate the shopping cart to the TV, browse and select products on the mobile phone, and watch the contents of the shopping cart on the TV at any time, which saves the complicated operation of repeatedly switching pages on the mobile phone. Improve user experience.
  • the user selects some products on the two mobile phones (mobile phone A and mobile phone C) and adds them to the shopping cart, and the user can transfer the shopping carts of mobile phone A and mobile phone C to TV B at the same time.
  • the group members on mobile phone A can include (A's shopping application, B's shopping application); the group members on mobile phone C can include (C's shopping application, B's shopping application); B's shopping application); the group members on TV B include (A's shopping application, B's shopping application, and C's shopping application), and the TV group includes three members. That is, the shopping application of the TV has respectively performed application-level authentication with the shopping application of the mobile phone A and the shopping application of the mobile phone C, and can subsequently communicate with the shopping applications of the mobile phone A and the mobile phone C respectively.
  • the shopping cart FA migration scenario implemented based on the near-field FA sharing capability is mainly applicable to a networking environment, such as a home environment and a work environment.
  • a networking environment such as a home environment and a work environment.
  • near-field networking short-distance networking
  • this solution is also valuable for reference.
  • the Internet can be used to realize the sharing and real-time synchronization of shopping cart contents.
  • the e-commerce platform can integrate the shopping cart in the Internet environment into its own shopping application, and realize sharing through its own cloud service and account.
  • the handoff technology proposed by Apple allows users to switch from one Apple device (for example, Mac, iPhone, iPad or Apple Watch, etc.) to another nearby Apple device to continue working without losing the task process.
  • this requires that the email relay device must log in to the same AppleId, install the same email client in advance, and log in to the email account; and this technology cannot select the push device, for example, a certain email needs to be pushed to the TV in the conference room Show, because the two devices are not logged into the same AppleId, the relay cannot be achieved.
  • the present application provides an application connection service based on near-field cross-device FA migration for the switching scenarios between mobile office and non-mobile office of business personnel, and supports one-key migration of emails between multiple terminal devices.
  • the watch can pull up the email viewing interface on the mobile phone side with one key, and go directly to the text of the email on the mobile phone side.
  • the present application also supports one-click seamless transfer to other devices (eg, other mobile phones, PAD or TV) to continue, providing the ultimate multi-device email collaboration experience.
  • This application does not require the same system, nor does it require devices to log in to the same account, and even does not require the installation of email applications on both devices, and has a wide range of applications.
  • mobile phone A can display an email interface 1601 (the email interface 1601 can be regarded as an FA, for example, FA8),
  • the interface 1601 clicks the migration button 1602 (the migration button is used to migrate (send) the mail interface of mobile phone A to other devices (eg, TV)), as shown in (a) in FIG. 16B, mobile phone A can pop up a pop-up box 1603, the pop-up box 1603 can include nearby devices, and the nearby devices include certified devices (monica's Mate pad, etc.) and uncertified devices (TV, HUAWEI P20, Mate book X pro, etc.).
  • certified devices monica's Mate pad, etc.
  • uncertified devices TV, HUAWEI P20, Mate book X pro, etc.
  • the mobile phone A may send an authentication request message to the TV.
  • a prompt message 1605 "waiting for confirmation from the peer end" may be displayed below the TV.
  • the TV can display a pop-up box 1610, which includes a prompt message “HUAWEI MATE30 (mobile phone A) requests to migrate emails to this machine, do you agree?”
  • the pop-up box 1610 may also include a disagree button 1614 and Agree button 1615.
  • the agree button 1613 as shown in FIG.
  • the TV can display a pop-up box 1614, and the pop-up box 1614 may include a QR code image generated by the TV, and may also include a prompt message 1615 “Scan for authentication, allow HUAWEI MATE30 swipe for certification”.
  • the user of the mobile phone A can scan the QR code picture displayed by the TV, and then the TV can receive the email interface (FA8) from the mobile phone A, as shown in FIG. 16E, the TV can display the email interface 1616.
  • the TV may receive a mail interface (FA8) from the mobile phone A, as shown in FIG. 16E, the TV may display the mail interface 1616.
  • FIG. 17A including:
  • the user opens an email editor on the mobile phone and clicks the "Migrate” button on the editing interface.
  • the email application of the mobile phone A initiates a migration request to the DM of the mobile phone A.
  • the information carried in the migration request includes the package name of the originating end (the name of the mail application package of the local end), the package name of the connecting end (the name of the mail application package of the opposite end), and the name of the mobile phone A.
  • steps 1703 to 1732 reference may be made to the related descriptions of steps 903 to 932, which will not be repeated here. Some of the steps in steps 903-932 may be optional.
  • the mail application of mobile phone A requests the DEF of mobile phone A to migrate to FA8.
  • the mail application may request the DEF of the mobile phone A to connect to the FA8 with the parameters of the device and the target device (for example, the identifiers of the device and the target device).
  • the DEF of the mobile phone A sends the relevant information of the FA8 to the DMS of the TV.
  • the relevant information of the FA8 may include email content information, and the email content information may include information such as subject, text, and attachments.
  • the DMS of the TV requests the DEF connection service of the TV.
  • the TV's DEF can detect whether the email client and account are logged in, and prompt the user to log in to the email account, so that the email application can display FA8, that is, the email interface migrated from mobile phone A is displayed.
  • the TV's DEF can be pulled up to display the FA8, that is, the FA8 will be rearranged and displayed, so that the device that is not logged in/without the email client installed can also display the email content, and can avoid the leakage of private information such as email accounts. .
  • the DEF of the TV does not support displaying FA8, you can download and install an FA capable of displaying FA8 from the application market (the FA may be developed by a third-party application manufacturer).
  • the user can edit and reply to the email on the TV, and the content of the edited and replied email can be sent back to the mobile phone A through the data communication channel, and the email is sent out according to the account information of the mobile phone A.
  • the migration device can only be used for display and editing. In the end, the sending and receiving of emails are performed by the migration initiator. The migrated device can only view the emails pushed by the initiator. seam switch.
  • This application can make mail flow between multiple devices, does not require logging in to the same device account, and does not require all devices to be installed with an email client and log in to an email account, which greatly expands the range of available devices.
  • the mobile phone and the PC after the user's watch receives the email notification, an email notification interface 1701 can be displayed, prompting the user that there is an email, and responding to the user's click to view
  • the button 1702 as shown in FIG. 17C, the watch can directly pull up the email viewing interface 1704 on the mobile phone (the watch can send an email viewing request to the mobile phone, and the mobile phone can directly display the email viewing interface 1704), one step directly to the email text.
  • the user can click the migration button 1705 on the mobile phone to migrate the email to the PC, as shown in Figure 17D, the PC can display the email In the editing interface 1706, after inserting the attachment in the mail editing interface 1706, the user can click the migration button 1707 to re-migrate the email carrying the attachment to the mobile phone.
  • the watch, mobile phone and PC can work together conveniently and quickly, and the user experience is high.
  • this application realizes one-key migration of emails between mobile office and non-mobile office, and transfers seamlessly, greatly improving the multi-device collaborative office experience.
  • Multi-device email migration is free from the restrictions of user accounts/email clients/mail accounts, and can cover multiple devices under the same network, greatly broadening the usage scenarios of email migration.
  • the receiver (passive migration device, such as mobile phone B, TV, etc.) generates two-dimensional code information
  • the initiator active migration device, such as mobile phone A
  • the initiator active migration device, such as mobile phone A
  • the receiver passive migration device, such as mobile phone B, TV, etc.
  • user A can select the migration option 1801 on the karaoke interface 1800 of the TV (the migration option 1801 is used to migrate (send) the karaoke interface of the TV to other devices (eg, mobile phone B)) .
  • the migration option 1801 is used to migrate (send) the karaoke interface of the TV to other devices (eg, mobile phone B)) .
  • user A may use a control device (eg, a remote control, a mobile phone, etc.) to select the "migration" option.
  • the TV is a touch device
  • user A may directly click the "Migrate” option to select the "Migrate” option.
  • the TV can pop up a pop-up box 1802, which may include a QR code image generated by the TV, and may also include a prompt message 1803 "Scan for authentication, allow other devices to scan and join my song room. ".
  • User B can use mobile phone B to scan the QR code picture displayed on the TV (mobile phone B can use the scanning portal provided by a third-party application (for example, K song application, etc.), or can use the scanning portal provided by the system), and then, as shown in the figure.
  • a third-party application for example, K song application, etc.
  • the mobile phone B can display the karaoke interface 1804, and the avatar 1805 of the user A (the avatar of the account of the K song application logged in on the TV, or the avatar of the device account (such as a Huawei account) logged in by the TV) can be displayed. Displayed at the bottom of the lyrics, indicating that the current user A is singing a song.
  • the mobile phone B can display a pop-up box 1807, and in response to the user's operation of clicking the chorus button 1808, as shown in FIG. 18D, the avatar of user A is displayed.
  • the avatar of the account of the K song app logged in on the TV or the avatar of the device account (such as a Huawei account) logged in on the TV
  • the avatar of user B 1810 the avatar of the account of the K song app logged in by mobile phone B, or the avatar of the account of the K song app logged in by mobile phone B, or logged in by mobile phone B
  • the avatar of the device account for example, a Huawei account
  • the method provided in this embodiment of the present application can be applied to two near-field devices, such as a TV and a mobile phone B, the TV and the mobile phone B are devices with different accounts (for example, not the same Huawei account), and both the TV and the mobile phone B have K song turned on application.
  • a TV and a mobile phone B are devices with different accounts (for example, not the same Huawei account), and both the TV and the mobile phone B have K song turned on application.
  • Figure 19 including:
  • the user can select the migration option 1801 on the karaoke interface of the TV.
  • the migration option 1801 is used to migrate (send) a series of karaoke interfaces of mobile phone A (for example, the series of karaoke interfaces can be regarded as FA9) to other devices (for example, mobile phone B)).
  • the migration option may also be referred to as a sharing option, a sending option, etc., which is not limited in this application.
  • the user may use a control device (eg, a remote control, a mobile phone, etc.) to select the "migration" option.
  • a control device eg, a remote control, a mobile phone, etc.
  • the user can directly click the "Migrate” option to select the "Migrate” option.
  • the user may further select the device to be migrated after selecting the migration option 1801, for example, mobile phone B may be selected.
  • the two-dimensional code identification module of the TV initiates a request to generate a two-dimensional code to the Hongmeng label management module of the TV.
  • the input parameters of the QR code generation request include a Bundle object and an asynchronous callback.
  • the Bundle object contains the source package name (the local karaoke application package name) and the destination package name (the opposite end karaoke application package name or the package name of the FA to be migrated) required by the karaoke service.
  • the asynchronous callback contains the result of creating the QR code.
  • the QR code field can be obtained if the creation is successful, and the error code can be obtained if the creation fails.
  • the Hongmeng label management module of the TV requests the device information of the TV from the DM of the TV.
  • the device information of the TV may include the name of the TV, a network ID (netId), a device IP (deviceIP), and the like.
  • the Bundle object saves the device information obtained by the Hongmeng tag management module to the device management, which is used to create groups and subsequently transmit the client application package name and other information to the peer device through the channel.
  • the DM of the TV generates a PIN.
  • the TV's DM can generate random PINs.
  • the PIN can be several random numbers.
  • the DM of the TV can also generate a token, and the token can be a random string of several digits.
  • the DM of the TV calls the security management module to obtain the connection parameters of the local device.
  • the local device connection parameters may include the local network ID (netId), the device IP (deviceIP), the Bluetooth address (BtMac), and the Wi-Fi address (Wi-FiPort). Among them, netId is saved locally.
  • the DM of the TV invokes the security management module to create a group.
  • the created group can be (the name of the machine (that is, the TV, such as HUAWEI TV), the package name of the karaoke application of this machine, (the name of the peer device can be vacant), the package name/waiting of the karaoke application of the peer package name of the migrated FA), the group currently lacks at least one member, allowing other devices to join as members.
  • the security management module After the security management module successfully creates the group, it sends a callback notification to the DM of the TV.
  • the DM of the TV After receiving the callback notification, the DM of the TV sends the PIN, token and device information of the TV to the Hongmeng label management module.
  • the DM of the TV saves the group name (groupName) locally, and packages the PIN, token, and device information of the TV into a bundle type, and passes it to the Hongmeng label management module through the device management callback.
  • the Hongmeng label management module generates a QR code picture based on the PIN, token and device information of the TV.
  • the Hongmeng label management module sends the two-dimensional code information to the two-dimensional code identification module.
  • the two-dimensional code identification module generates a two-dimensional code picture according to the two-dimensional code information and displays the two-dimensional code picture.
  • the two-dimensional code identification module can call the display function of the TV, so as to display the two-dimensional code picture on the display screen of the TV.
  • Mobile phone B opens the two-dimensional code identification module to scan the two-dimensional code picture displayed on the TV.
  • the two-dimensional code identification module of mobile phone B identifies the two-dimensional code information (also called a two-dimensional code label) in the two-dimensional code picture, pulls up the Hongmeng label management module, and transmits the two-dimensional code information.
  • the two-dimensional code information also called a two-dimensional code label
  • the Hongmeng label management module parses the two-dimensional code information, and extracts the fields (strings) stored in the two-dimensional code information.
  • the Hongmeng label management module of mobile phone B sends an authentication request message to the DM of mobile phone B, and registers a callback.
  • the authentication request message includes fields parsed from the two-dimensional code information.
  • the DM of the mobile phone B processes the authentication request message.
  • the DM of the mobile phone B can split the fields included in the authentication request message to obtain the deviceIp and Wi-FiPort fields, and call the communication module interface according to the deviceIp and Wi-FiPort to create a communication channel between the mobile phone B and the TV.
  • the DM of the mobile phone B sends an authentication request message to the DM of the TV through the communication module.
  • the DM of mobile phone B can set the token as the parameter requestId. It can be understood that the DM of the mobile phone B can also send information such as the device ID of the mobile phone B to the DM of the TV through the communication module.
  • the DM of the TV extracts the token based on the parameter requestId, compares the extracted token with the token saved at the local end, and if they are consistent, agrees to create a secure communication channel between the two devices (that is, the TV and the mobile phone B) (the secure communication channel can be encrypted, for example. protected communication channel), and send group information to mobile phone B through the secure communication channel, the group information includes the network ID of the TV, the group ID (groupId), group type (groupType) and Group name (groupName), etc.
  • the DM of the mobile phone B receives and saves the group information sent by the TV.
  • the DM of mobile phone B invokes the security management module to obtain all group information that has a trusted relationship with the peer device, and then traverses through the security management module to query whether the K song application of the TV has access rights to the group.
  • Step 1915 is executed if the authority is available.
  • the DMS of the mobile phone B receives the relevant information of the FA9 from the DEF of the TV.
  • the relevant information of the FA9 may include song information of the K song, and the song information includes at least one of the song title (eg, red beans), lyrics, audio information and video information.
  • the song information includes at least one of the song title (eg, red beans), lyrics, audio information and video information.
  • operations such as ordering songs and cutting songs on mobile phone B and the song list information will be synchronously sent to the TV through a secure communication channel, which can control the playback of music on the TV side.
  • the TV and the mobile phone B can perform the above steps 1901-1915.
  • verification that is, perform device-level authentication
  • the TV and the mobile phone B can perform the above steps 1901-1915. In order to verify the FA migration between the TV and the mobile phone B to ensure the security of the data between the devices.
  • the TV and the mobile phone B can perform the above steps 1901-1915.
  • the TV and the mobile phone B can perform the above steps 1901-1915.
  • the TV and the mobile phone B can perform the above steps 1901-1915.
  • the security of the data between the devices for example, the relevant information of the FA9.
  • step 1905 may be an optional step, for example, the DM of the TV may obtain local device connection parameters from other modules.
  • step 1906b may be an optional step, that is, after the security management module successfully creates a group, it may not send a callback notification to the DM of the TV.
  • steps 1911b and 1912 may be optional steps, that is, the DM of the mobile phone B may not send the token to the DM of the TV, and the DM of the TV does not need to verify the token.
  • mobile phone C (the device account of mobile phone C is different from the device account of mobile phone B, for example, is not logged into the same Huawei account) can also join the group created by the TV by scanning the QR code (for the specific process, please refer to step 1809-step 1818).
  • multiple devices can quickly launch the FA9 based on the QR code scanning method, without pre-installation, and the service can be used immediately; and after multiple devices scan the code, a circle of trust can be established for information exchange, such as playlists between multiple devices, etc.
  • the information can be refreshed and synchronized in real time, and multiple devices (for example, mobile phone B or mobile phone C) can coordinately control the chairman terminal (for example, TV) to realize multi-device cooperative control and realize a real mobile KTV experience.
  • the initiator may generate a QR code picture (eg, perform steps 1901-1908c), and one or more recipients (passive migration devices, such as mobile phone B and mobile phone C) ) can be authenticated according to the QR code picture of the TV (for example, step 1909a-step 1914 is executed), after passing the authentication, the receiver can migrate the shopping cart, live room, mail, etc.
  • multiple devices for example, , the effect of sharing shopping cart, live broadcast room, mail and other information between TV, mobile phone B and mobile phone C
  • shopping cart product information, live video stream, mail content and other information between multiple devices can be refreshed and synchronized in real time
  • multiple devices can coordinately control the chairman terminal (for example, TV), realize the cooperative control of multiple devices, and realize the real cooperative shopping, live broadcast or mail editing experience.
  • each UI interface provided by the embodiments of the present application, for example, the above-mentioned FIGS. 5A-5F, 6A-6C, 8A-8D, 10A-10B, 12A-12E, Fig. 14A-Fig. 14F, Fig. 16A-Fig. 16E, Fig. 18A-Fig. 18C, etc.
  • the interface design of each UI interface is only an illustration, and does not limit the design of each element (eg, button, icon, text, etc.) in the UI interface location, name and shape, etc.
  • buttons of different UI interfaces can be rearranged and combined into the same UI interface.
  • the button 502 in (a) in FIG. 5A may be replaced with the button 503 and the button 504 in (b) in FIG. 5A .
  • the embodiments of the present application do not limit the jump relationship between UI interfaces.
  • the mobile phone may directly display the scan interface 512 .
  • This embodiment of the present application also does not limit the way of jumping between UI interfaces (for example, if there is a description of clicking the first button of the first UI interface to jump to the second UI in this embodiment of the present application, only the first interface and the second UI are described in this embodiment.
  • a jumping method of the interface is indicated, and other jumping methods are not limited).
  • the mobile phone in response to the operation of a user-specific gesture (eg, three-finger swipe, knuckle tap, etc.), as shown in (a) of FIG. 8B , the mobile phone may display a pop-up frame 803 .
  • a user-specific gesture eg, three-finger swipe, knuckle tap, etc.
  • the embodiment of the present application provides a function migration method, as shown in FIG. 20 , including:
  • a first device sends a first request to a second device.
  • the first request carries the identifier of the first device, the identifier of the first application, and the identifier of the second application.
  • the first request may be the authentication request message in the foregoing embodiment, and the related description is not repeated here.
  • a first pop-up frame in response to the user's first operation on the first application of the first device, a first pop-up frame is displayed, and the first pop-up frame includes an identifier of a device in the same network as the first device;
  • the first request is sent to the second device.
  • the first pop-up frame here may be the pop-up frame 508 as shown in (b) in FIG. 5C or the pop-up frame 803 as shown in (a) in FIG. 8B , or the like.
  • the devices in the same network as the first device include trusted devices and untrusted devices; where the trusted devices include devices that log into the same account as the first device, and devices that have undergone device-level authentication with the first device Or a device that has undergone application-level authentication with the first application of the first device; untrusted devices include devices that do not log in to the same account as the first device, devices that have not undergone device-level authentication with the first device, or devices that have not been authenticated with the first device.
  • the first application of the device has been authenticated at the application level.
  • the first device may be the mobile phone A in the foregoing embodiment.
  • the second device receives the first request from the first device.
  • the first device may display a first pop-up box, where the first pop-up box is used to prompt the user whether to agree to add the first application of the first device to the first group; and receive an consent instruction from the user.
  • the first pop-up frame here may be the pop-up frame 531 shown in (a) in FIG. 6A , or the pop-up frame 812 as shown in (a) in FIG. 8C , or the like.
  • the second device may be the mobile phone B in the foregoing embodiment.
  • the second device creates a first group, and members of the first group include the second application of the second device.
  • the second device Before the second device creates the first group, it may be determined according to the identifier of the first device that the second device does not currently have a second group, where members of the second group include the first device and the second device.
  • the second device Before the second device creates the first group, it may be determined, according to the identifier of the first device, the identifier of the first application, and the identifier of the second application, that the second device does not currently have a third group, where members of the third group include A first application for the first device and a second application for the second device.
  • the second device sends a first response to the first device.
  • the first response may include the personal identification code PIN corresponding to the first group and/or the communication connection information of the second device.
  • the first device receives a first response from the second device.
  • the first response is used to indicate a first group created by the second device, and members of the first group include the second application of the second device.
  • the first device sends a second request to the second device.
  • the second request is used to apply for adding the first application of the first device to the first group.
  • the second device may display a two-dimensional code picture, where the two-dimensional code picture includes the personal identification code PIN corresponding to the first group and/or the communication connection information of the second device.
  • the first device can scan the QR code picture displayed by the second device to obtain the personal identification code PIN corresponding to the first group and/or the communication connection information of the second device.
  • the communication connection information sends a second request to the second device.
  • the first device sends the second request to the second device according to the PIN and/or the communication connection information of the second device.
  • the second device receives the second request from the first device.
  • the second device may add the first application of the first device to the first group according to the second request.
  • the second device may send a second response to the first device, and the first device may receive the second response, where the second response is used to indicate that the first application of the first device has joined the first group.
  • the first device migrates the first function in the first application to the second application of the second device, where the first function includes one or more UIs.
  • migrating the first function in the first application to the second application of the second device includes: sending service information of the first function to the second device; when the first application is a live broadcast application, The service information of the first function includes at least one of the video stream, audio stream, and bullet screen information in the live room of the first device; or when the first application is a camera application, the service information of the first function includes shooting a preview screen or The menu bar information of the shooting interface; or when the first application is a K song application, the service information of the first function includes at least one of the song title, lyrics, audio information of the song, video information of the song, and control interface of the song; or When the first application is a shopping application, the business information of the first function includes the commodity information in the shopping cart; or when the first application is an email application, the business information of the first function includes at least one of the subject, body and attachments of the email. A sort of.
  • the first device may create a second group, wherein members of the second group include the first application of the first device and the second application of the second device.
  • the second device receives a first function in the first application migrated by the first device, where the first function includes one or more UIs.
  • the first device or the second device in the embodiment of FIG. 20 may be the mobile phone A and the mobile phone B, etc. in the foregoing embodiments, respectively.
  • the foregoing embodiments which are not described here Do repeat.
  • This embodiment of the present application provides a function migration method, as shown in FIG. 21 , including:
  • the first device sends a first request to the second device.
  • the first request carries the identifier of the first device.
  • the second device receives the first request from the first device.
  • the second device sends a first response to the first device.
  • the first response is used to indicate a first group created by the second device, and members of the first group include the second device.
  • the first device receives the first response from the second device.
  • the first device sends a second request to the second device, where the second request is used to apply for adding the first device to the first group.
  • the first device migrates the first function in the first application to the second device, where the first application is any application in the first device, and the first function includes one or more graphical user interfaces UI.
  • the first device or the second device in the embodiment of FIG. 21 may be the mobile phone A and the mobile phone B, etc. in the foregoing embodiments, respectively, and the first request may be the authentication request message and the like in the foregoing embodiments.
  • the first request may be the authentication request message and the like in the foregoing embodiments.
  • the embodiment of the present application provides a function migration method, as shown in FIG. 22 , including:
  • the first device creates a first group, and members of the first group include a first application of the first device.
  • the second device sends a first request to the first device, where the first request is used to apply for adding the second application of the second device to the first group created by the first device, and the members of the first group include The first application and the second application of the second device.
  • the first device receives a first request from the second device, where the first request is used to apply for adding the second application of the second device to the first group.
  • the first device adds the second application of the second device to the first group.
  • the first device migrates the first function in the first application to the second application of the second device, where the second function includes one or more UIs.
  • the second device receives a first function in the first application from the first device, where the first function includes one or more UIs.
  • the first device or the second device in the embodiment of FIG. 22 may be the mobile phone A and the mobile phone B, etc. in the foregoing embodiment, respectively, and the first request may be the authentication request message and the like in the foregoing embodiment.
  • the first request may be the authentication request message and the like in the foregoing embodiment.
  • first device or a second device may be the electronic device 200 shown in FIG. 3 .
  • the first device or the second device may include a communication module, a memory, and one or more processors.
  • the communication module and the memory are coupled to the processor.
  • the memory is used to store computer program code comprising computer instructions.
  • the chip system includes at least one processor 2301 and at least one interface circuit 2302 .
  • the processor 2301 and the interface circuit 2302 may be interconnected by wires.
  • the interface circuit 2302 may be used to receive signals from other devices (eg, a memory of an electronic device).
  • the interface circuit 2302 may be used to send signals to other devices (eg, the processor 2301).
  • the interface circuit 2302 may read instructions stored in a memory in the electronic device and send the instructions to the processor 2301 .
  • the first device/second device (the electronic device 230 shown in FIG. 6) can be made to execute the steps in the above embodiments.
  • the interface circuit 2302 may read instructions stored in memory in the server and send the instructions to the processor 2301.
  • the server can be caused to perform the various steps in the above-mentioned embodiments.
  • the chip system may also include other discrete devices, which are not specifically limited in this embodiment of the present application.
  • the disclosed apparatus and method may be implemented in other manners.
  • the device embodiments described above are only illustrative.
  • the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be Incorporation may either be integrated into another device, or some features may be omitted, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place, or may be distributed to multiple different places . Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a readable storage medium.
  • the technical solutions of the embodiments of the present application can be embodied in the form of software products in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, which are stored in a storage medium , including several instructions to make a device (may be a single chip microcomputer, a chip, etc.) or a processor (processor) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk and other mediums that can store program codes.

Abstract

本申请实施例提供一种功能迁移方法和装置，涉及终端领域，能够保证数据分享的安全可靠。其方法为：第一设备向第二设备发送第一请求，第一请求携带第一设备的标识、第一应用的标识和第二应用的标识；从第二设备接收第一响应，第一响应用于指示第二设备创建的第一群组，第一群组的成员包括第二设备的第二应用；向第二设备发送第二请求，第二请求用于申请将第一设备的第一应用加入第一群组；将第一应用中的第一功能迁移到第二设备的第二应用，第一功能包括一个或者多个图形用户界面。

Description

一种功能迁移方法和装置
本申请要求于2021年03月31日提交国家知识产权局、申请号为202110352451.1、申请名称为“一种功能迁移方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及终端领域，尤其涉及一种功能迁移方法和装置。
背景技术
随着智能手机、平板、个人计算机(personal computer，PC)等数字化设备的普及和发展，个人终端数量激增，不同设备之间具有分享业务数据的需求。因此，如何分享业务数据以保证数据的安全可靠成为一个亟待解决的问题。
发明内容
本申请实施例提供一种功能迁移方法和装置，能够保证数据分享的安全可靠。
第一方面，本申请实施例提供一种功能迁移方法，应用于第一设备，方法包括：向第二设备发送第一请求，第一请求携带第一设备的标识、第一应用的标识和第二应用的标识；从第二设备接收第一响应，第一响应用于指示第二设备创建的第一群组，第一群组的成员包括第二设备的第二应用；向第二设备发送第二请求，第二请求用于申请将第一设备的第一应用加入第一群组；将第一应用中的第一功能迁移到第二设备的第二应用，第一功能包括一个或者多个图形用户界面(user interface，UI)。
基于本申请实施例提供的方法，经过第一设备和第二设备的协商，第一设备的第一应用和第二设备的第二应用可以加入第一群组，即第一群组的成员可以包括第一设备的第一应用和第二设备的第二应用。由于第一群组是经过第一设备和第二设备协商后建立的，因此在第一群组的成员之间迁移功能数据，例如迁移第一功能的一个或者多个UI，能够保证数据分享的安全可靠。
在一种可能的实现方式中，第一响应包括第一群组对应的个人识别密码(personal identification number，PIN)和/或第二设备的通信连接信息；向第二设备发送第二请求，包括：根据PIN和/或第二设备的通信连接信息向第二设备发送第二请求。这样，当第一设备需要加入第二设备创建的群组时，可以在请求中携带群组对应的PIN，以便第二设备可以根据PIN对第一设备的安全性进行校验，从而可以保证数据分享的安全可靠。
在一种可能的实现方式中，方法还包括：接收第二响应，其中，第二响应用于指示第一设备的第一应用已加入第一群组。这样，第一设备可以获知第一应用已加入第一群组，以便后续可以直接进行功能迁移。
在一种可能的实现方式中，方法还包括：创建第二群组，其中，第二群组的成员包括第一设备的第一应用以及第二设备的第二应用。也就是说，第一设备可以在本地 创建一个群组(即第二群组)，该群组与第二设备创建的群组相同。这样，当第二设备的第二应用向第一设备的第一应用进行功能迁移时，若第一设备确定本地保存有第二群组，可以认为第二设备的第二应用是安全可信的，可以直接进行功能迁移。
在一种可能的实现方式中，方法还包括：响应于用户在第一设备的第一应用的第一操作，显示第一弹框，第一弹框包括与第一设备处于同一个网络中的设备的标识；向第二设备发送第一请求，包括：响应于用户在第一弹框中选中第二设备的第二操作，向第二设备发送第一请求。这样，可以通过第一弹框供用户选择需要进行功能迁移的设备。
在一种可能的实现方式中，与第一设备处于同一个网络中的设备包括可信设备和不可信设备；其中，可信设备包括与第一设备登录同一个账号的设备、与第一设备进行过设备级认证的设备或者与第一设备的第一应用进行过应用级认证的设备；不可信设备包括未与第一设备登录同一个账号的设备、未与第一设备进行过设备级认证的设备或者未与第一设备的第一应用进行过应用级认证的设备。这样，可以向用户提示可信设备和不可信设备，方便用户管理相应的设备。
在一种可能的实现方式中，方法还包括：扫描第二设备显示的二维码图片，二维码图片包括第一群组对应的个人识别码PIN和/或第二设备的通信连接信息，向第二设备发送第二请求，包括：根据PIN和/或第二设备的通信连接信息向第二设备发送第二请求。这里以二维码图片为标识符进行示意说明，可以将二维码图片替换为其他类型的标识符，例如条形码、字符串等，本申请不做限定。
在一种可能的实现方式中，将第一应用中的第一功能迁移到第二设备包括：向第二设备发送第一功能的业务信息；当第一应用为直播应用时，第一功能的业务信息包括第一设备的直播间的视频流、音频流以及弹幕信息中的至少一种；或者当第一应用为拍照应用时，第一功能的业务信息包括拍摄预览画面或拍摄界面的菜单栏信息；或者当第一应用为K歌应用时，第一功能的业务信息包括歌名、歌词、歌曲的音频信息歌曲的视频信息、歌曲的控制界面中的至少一种；或者当第一应用为购物应用时，第一功能的业务信息包括购物车中的商品信息；或者当第一应用为邮件应用时，第一功能的业务信息包括邮件的主题、正文和附件中的至少一种。
这样，在不同的场景下，可以将第一设备上不同的应用程序(例如，直播应用、拍照应用、K歌应用、邮件应用或购物应用)的部分功能迁移到第二设备上，可以满足跨设备迁移功能的需求。
在一种可能的实现方式中，所述第二设备的通信连接信息包括所述第二设备的无线保真Wi-Fi地址或蓝牙地址。
在一种可能的实现方式中，所述方法还包括：向第三设备发送第三请求，所述第三请求携带所述第一设备的标识、第一应用的包名和第三应用的包名；所述第三请求用于请求将所述第一应用的第一功能迁移到所述第三设备的所述第三应用；接收第二响应，所述第二响应包括同意迁移的信息和所述第三设备创建的第二群组的群组名，所述第二群组的成员包括所述第一设备的所述第一应用以及所述第三设备的所述第三应用；向所述第三设备发送第四请求，所述第四请求用于申请加入所述第二群组，所述第四请求包括所述第二群组的群组名；将所述第一应用中的所述第一功能迁移至所 述第三设备。
在一种可能的实现方式中，所述方法还包括更新本地保存的所述第一群组的成员，更新后的所述第一群组的成员包括所述第一设备的所述第一应用、所述第二设备的所述第二应用和所述第三设备的所述第三应用。
在一种可能的实现方式中，所述第二应用的包名和所述第一应用的包名相同。
在一种可能的实现方式中，所述可信设备包括第三设备，响应于用户从所述可信设备中删除所述第三设备的操作，删除与所述第三设备相关的群组。
在一种可能的实现方式中，所述第一群组被设置为永久有效或在预设时间内有效。
在一种可能的实现方式中，当第一应用为K歌应用时，所述方法还包括：重新编排点歌控制UI；响应于用户在所述点歌控制UI进行点歌、切歌的操作，将点歌、切歌信息发送给所述第二设备。
在一种可能的实现方式中，当所述第一应用为购物应用时，所述第一功能的业务信息包括购物车中的商品信息，所述商品信息包括商品名、商品链接和商品价格信息中的至少一种。
在一种可能的实现方式中，当所述第一应用为邮件应用时，所述第一功能的业务信息包括邮件的主题、正文或附件中的至少一种。
第二方面，本申请实施例提供一种功能迁移方法，应用于第二设备，方法包括：接收来自第一设备的第一请求，第一请求携带第一设备的标识、第一应用的标识和第二应用的标识；创建第一群组，第一群组的成员包括第二设备的第二应用；向第一设备发送第一响应，第一响应用于指示第一群组；接收来自第一设备的第二请求，第二请求用于申请将第一设备的第一应用加入第一群组。接收第一设备迁移的第一应用中的第一功能，其中，第一功能包括一个或者多个图形用户界面UI。
基于本申请实施例提供的方法，经过第一设备和第二设备的协商，第一设备的第一应用和第二设备的第二应用可以加入第一群组，即第一群组的成员可以包括第一设备的第一应用和第二设备的第二应用。由于第一群组是经过第一设备和第二设备协商后建立的，因此在第一群组的成员之间迁移功能数据，例如迁移第一功能的一个或者多个UI，能够保证数据分享的安全可靠。
在一种可能的实现方式中，第一响应包括第一群组对应的个人识别码PIN和/或第二设备的通信连接信息。这样，第二设备可以根据PIN对第一设备的安全性进行校验，从而可以保证数据分享的安全可靠。
在一种可能的实现方式中，方法还包括：向第一设备发送第二响应，其中，第二响应用于指示第一设备的第一应用已加入第二群组。这样，第一设备可以获知第一应用已加入第一群组，以便后续可以直接进行功能迁移。
在一种可能的实现方式中，从第一设备接收第一请求之后，方法还包括：显示第一弹框，第一弹框用于提示用户是否同意将第一设备的第一应用加入第一群组；接收来自用户的同意指令。这样，可以通过第一弹框提示用户将第一设备的第一应用加入第一群组。
在一种可能的实现方式中，在创建第一群组之前，方法还包括：根据第一设备的标识确定第二设备当前没有第二群组，其中，第二群组的成员包括第一设备和第二设 备。即确定第一设备和第二设备之间没有建立群组的情况下，也就是第一设备和第二设备在先没有建立过程可信连接的情况下，可以创建第一群组。
在一种可能的实现方式中，在创建第一群组之前，方法还包括：根据第一设备的标识、第一应用的标识和第二应用的标识，确定第二设备当前没有第三群组，其中，第三群组的成员包括第一设备的第一应用以及第二设备的第二应用。即确定第一设备的第一应用以及第二设备的第二应用之间没有建立群组的情况下，也就是第一设备的第一应用以及第二设备的第二应用在先没有建立过程可信连接的情况下，可以创建第一群组。
在一种可能的实现方式中，方法还包括：显示二维码图片，二维码图片包括第一群组对应的个人识别码PIN和/或第二设备的通信连接信息。这里以二维码图片为标识符进行示意说明，可以将二维码图片替换为其他类型的标识符，例如条形码、字符串等，本申请不做限定。
在一种可能的实现方式中，接收第一设备迁移的第一应用中的第一功能包括：接收来自第一设备的第一功能的业务信息；当第一应用为直播应用时，第一功能的业务信息包括第一设备的直播间的视频流、音频流以及弹幕信息中的至少一种；或者当第一应用为拍照应用时，第一功能的业务信息包括拍摄预览画面或拍摄界面的菜单栏信息；或者当第一应用为K歌应用时，第一功能的业务信息包括歌名、歌词、歌曲的音频信息歌曲的视频信息、歌曲的控制界面中的至少一种；或者当第一应用为购物应用时，第一功能的业务信息包括购物车中的商品信息；或者当第一应用为邮件应用时，第一功能的业务信息包括邮件的主题、正文和附件中的至少一种。
这样，在不同的场景下，可以将第一设备上不同的应用程序(例如，直播应用、拍照应用、K歌应用、邮件应用或购物应用)的部分功能迁移到第二设备上，可以满足跨设备迁移功能的需求。
在一种可能的实现方式中，第二设备的通信连接信息包括第二设备的无线保真Wi-Fi地址或蓝牙地址。
在一种可能的实现方式中，第二应用的包名和第一应用的包名相同。
在一种可能的实现方式中，第一群组被设置为永久有效或在预设时间内有效。
在一种可能的实现方式中，从第一设备接收第一请求之后，方法还包括：显示第二弹框，第二弹框用于提示用户是否同意第一设备将第一功能迁移至第二设备。
在一种可能的实现方式中，若第二设备安装直播应用，第二设备检测直播应用是否登录；若直播应用为登录状态，直播应用在第二设备的直播画面上展示第一功能。
在一种可能的实现方式中，若第二设备未安装直播应用，第二设备以音频播放器的形式展示第一功能。
在一种可能的实现方式中，当第一应用为拍照应用时，第一功能的业务信息包括拍摄预览画面和拍摄界面的菜单栏信息。
在一种可能的实现方式中，第二设备显示第一设备的拍摄预览画面和拍摄界面的菜单栏；响应于用户在第二设备触发第一设备进行拍摄的操作，向第一设备发送拍摄指令，第一设备拍摄照片或视频。
在一种可能的实现方式中，当第一应用为K歌应用时，若第二设备安装K歌应用， 检测K歌应用是否登录；若K歌应用为登录状态，K歌应用展示第一功能。
在一种可能的实现方式中，当第一应用为K歌应用时，若第二设备未安装K歌应用，以音频播放器的形式展示第一功能。
在一种可能的实现方式中，当第一应用为购物应用时，若第二设备安装购物应用，检测购物应用是否登录；若购物应用为登录状态，购物应用根据第一功能的业务信息显示共享购物车，共享购物车包括第二设备的购物车中的全部商品和第一设备的购物车中的全部商品。
在一种可能的实现方式中，响应于用户结算共享购物车中全部商品的操作，第二设备向第一设备发送付款请求，付款请求包括第一设备的购物车中的全部商品的总金额。
在一种可能的实现方式中，当第一应用为邮件应用时，若第二设备安装邮箱应用，检测邮箱应用是否登录；若邮箱应用为登录状态，邮箱应用展示第一功能。
在一种可能的实现方式中，当第一应用为邮件应用时，若第二设备未安装邮箱应用，以图文编辑器的形式对第一功能进行编码重排显示。
第三方面，本申请实施例提供一种功能迁移方法，应用于包括第一设备和第二设备的通信系统，方法包括：第一设备向第二设备发送第一请求，第一请求携带第一设备的标识；第二设备从第一设备接收第一请求；第二设备从第一设备发送第一响应，第一响应用于指示第二设备创建的第一群组，第一群组的成员包括第二设备；第一设备从第二设备接收第一响应；第一设备向第二设备发送第二请求，第二请求用于申请将第一设备加入第一群组；第一设备将第一应用中的第一功能迁移至第二设备，第一应用为第一设备中的任一个应用，第一功能包括一个或多个图形用户界面UI。
在一种可能的实现方式中，第一响应包括第一群组对应的个人识别码PIN和/或第二设备的通信连接信息，向第二设备发送第二请求，包括：根据PIN和/或第二设备的通信连接信息向第二设备发送第二请求；方法还包括：从第二设备接收第二响应，第二响应用于指示第一设备已加入第一群组。
在一种可能的实现方式中，响应于用户的第一操作，第一设备显示第一弹框，第一弹框包括一个或多个未与第一设备进行过认证的设备的标识；第一设备向第二设备发送第一请求，包括：响应于用户在第一弹框中选择第二设备的第二操作，向第二设备发送第一请求。
在一种可能的实现方式中，方法还包括：第一设备创建第二群组，第二群组的成员包括第一设备以及第二设备。
在一种可能的实现方式中，方法还包括：响应于用户在第一设备的第一应用的第一操作，第一设备显示第一弹框，第一弹框包括与第一设备处于同一个网络中的设备的标识；第一设备向第二设备发送第一请求，包括：第一设备响应于用户在第一弹框中选中第二设备的第二操作，向第二设备发送第一请求。
在一种可能的实现方式中，与第一设备处于同一个网络中的设备包括可信设备和不可信设备；其中，可信设备包括与第一设备登录同一个账号的设备、与第一设备进行过设备级认证的设备或者与第一设备的第一应用进行过应用级认证的设备；不可信设备包括未与第一设备登录同一个账号的设备、未与第一设备进行过设备级认证的设 备或者未与第一设备的第一应用进行过应用级认证的设备。
在一种可能的实现方式中，方法还包括：第二设备显示二维码图片，二维码图片包括第一群组对应的个人识别码PIN和/或第二设备的通信连接信息；第一设备扫描第二设备显示的二维码图片；第一设备向第二设备发送第二请求，包括：第一设备根据PIN和/或第二设备的通信连接信息向第二设备发送第二请求。
在一种可能的实现方式中，第一设备将第一应用中的第一功能迁移至第二设备包括：向第二设备发送第一功能的业务信息；当第一应用为直播应用时，第一功能的业务信息包括第一设备的直播间的视频流、音频流以及弹幕信息中的至少一种；或者当第一应用为拍照应用时，第一功能的业务信息包括拍摄预览画面或拍摄界面的菜单栏信息；或者当第一应用为K歌应用时，第一功能的业务信息包括歌名、歌词、歌曲的音频信息歌曲的视频信息、歌曲的控制界面中的至少一种；或者当第一应用为购物应用时，第一功能的业务信息包括购物车中的商品信息；或者当第一应用为邮件应用时，第一功能的业务信息包括邮件的主题、正文和附件中的至少一种。
第四方面，本申请实施例提供一种功能迁移方法，应用于第一设备，包括：创建第一群组，第一群组的成员包括第一设备的第一应用；从第二设备接收第一请求，第一请求用于申请将第二设备的第二应用加入第一群组；将第二设备的第二应用加入第一群组；将第一应用中的第一功能迁移到第二设备的第二应用，第二功能包括一个或者多个图形用户界面UI。
在一种可能的实现方式中，在从第二设备接收第一请求之前，方法还包括：显示用于指示第一群组的第一标识符，其中，第一请求与第一标识符相对应。
在一种可能的实现方式中，第一标识符包括二维码图片，第一标识符包括个人识别码PIN；从第二设备接收第一请求之后，方法还包括：确定第一请求中携带PIN；确定将第二设备的第二应用加入第一群组。
在一种可能的实现方式中，将第一应用中的第一功能迁移到第二设备的第二应用包括：向第二设备发送第一功能的业务信息；当第一应用为直播应用时，第一功能的业务信息包括第一设备的直播间的视频流、音频流以及弹幕信息中的至少一种；或者当第一应用为拍照应用时，第一功能的业务信息包括拍摄预览画面或拍摄界面的菜单栏信息；或者当第一应用为K歌应用时，第一功能的业务信息包括歌名、歌词、歌曲的音频信息歌曲的视频信息、歌曲的控制界面中的至少一种；或者当第一应用为购物应用时，第一功能的业务信息包括购物车中的商品信息；或者当第一应用为邮件应用时，第一功能的业务信息包括邮件的主题、正文和附件中的至少一种。
第五方面，本申请实施例提供一种功能迁移方法，应用于第二设备，包括：向第一设备发送第一请求，第一请求用于申请将第二设备的第二应用加入第一设备创建的第一群组，第一群组的成员包括第一设备的第一应用和第二设备的第二应用；从第一设备接收第一应用中的第一功能，其中，第一功能包括一个或者多个图形用户界面UI。
在一种可能的实现方式中，在向第一设备发送第一请求之前，方法还包括：扫描用于指示第一群组的第一标识符，其中，第一请求与第一标识符相对应。
在一种可能的实现方式中，第一标识符包括二维码图片，第一标识符包括个人识别码PIN；向第一设备发送第一请求包括：向第一设备发送第一请求，第一请求中携 带PIN。
在一种可能的实现方式中，从第一设备接收第一应用中的第一功能包括：从第一设备接收第一功能的业务信息；当第一应用为直播应用时，第一功能的业务信息包括第一设备的直播间的视频流、音频流以及弹幕信息中的至少一种；或者当第一应用为拍照应用时，第一功能的业务信息包括拍摄预览画面或拍摄界面的菜单栏信息；或者当第一应用为K歌应用时，第一功能的业务信息包括歌名、歌词、歌曲的音频信息歌曲的视频信息、歌曲的控制界面中的至少一种；或者当第一应用为购物应用时，第一功能的业务信息包括购物车中的商品信息；或者当第一应用为邮件应用时，第一功能的业务信息包括邮件的主题、正文和附件中的至少一种。
第六方面，本申请提供了一种第一设备，包括一个或多个处理器和一个或多个存储器。该一个或多个存储器与一个或多个处理器耦合，一个或多个存储器用于存储计算机程序代码，计算机程序代码包括计算机指令，当一个或多个处理器执行计算机指令时，使得第一设备执行上述第一方面或第三方面或第四方面中任一方面任一项可能的实现方式中的方法。
第七方面，本申请提供了一种第二设备，包括一个或多个处理器和一个或多个存储器。该一个或多个存储器与一个或多个处理器耦合，一个或多个存储器用于存储计算机程序代码，计算机程序代码包括计算机指令，当一个或多个处理器执行计算机指令时，使得第二设备执行上述第二方面或第三方面或第五方面中任一方面任一项可能的实现方式中的方法。
第八方面，本申请实施例提供了一种计算机程序产品，当计算机程序产品在计算机上运行时，使得计算机执行上述任一方面任一项可能的实现方式中的方法。
第九方面，本申请提供一种芯片系统，该芯片系统可以设置于第一设备中。该芯片系统包括一个或多个接口电路和一个或多个处理器。该接口电路和处理器通过线路互联。该芯片系统可以应用于包括通信模块和存储器的电子设备。该接口电路用于存储器接收信号，并向处理器发送接收到的信号，该信号包括存储器中存储的计算机指令。当处理器执行该计算机指令时，第一设备可以执行上述任一方面及其任一种可能的实现方式所述的方法。
第十方面，本申请实施例提供了一种计算机存储介质，包括计算机指令，当计算机指令在第一设备上运行时，使得第一设备执行上述任一方面任一项可能的实现方式中的方法。
第十一方面，本申请实施例提供一种功能迁移系统，包括至少两个设备(例如第一设备和第二设备)，每个设备可以执行上述任一方面及其任一种可能的实现方式所述的方法。
附图说明
图1为本申请实施例提供的一种系统架构示意图；
图2为本申请实施例提供的又一种系统架构示意图；
图3为本申请实施例提供的一种电子设备的硬件结构示意图；
图4为本申请实施例提供的一种电子设备的软件架构示意图；
图5A为本申请实施例提供的一种显示示意图；
图5B为本申请实施例提供的又一种显示示意图；
图5C为本申请实施例提供的又一种显示示意图；
图5D为本申请实施例提供的又一种显示示意图；
图5E为本申请实施例提供的又一种显示示意图；
图5F为本申请实施例提供的又一种显示示意图；
图6A为本申请实施例提供的又一种显示示意图；
图6B为本申请实施例提供的又一种显示示意图；
图6C为本申请实施例提供的又一种显示示意图；
图7A为本申请实施例提供的一种信号交互示意图；
图7B为本申请实施例提供的又一种信号交互示意图；
图7C为本申请实施例提供的又一种信号交互示意图；
图8A为本申请实施例提供的又一种显示示意图；
图8B为本申请实施例提供的又一种显示示意图；
图8C为本申请实施例提供的又一种显示示意图；
图8D为本申请实施例提供的又一种显示示意图；
图8E为本申请实施例提供的又一种显示示意图；
图9A为本申请实施例提供的又一种信号交互示意图；
图9B为本申请实施例提供的又一种信号交互示意图；
图9C为本申请实施例提供的又一种信号交互示意图；
图10A为本申请实施例提供的又一种显示示意图；
图10B为本申请实施例提供的又一种显示示意图；
图11为本申请实施例提供的又一种信号交互示意图；
图12A为本申请实施例提供的又一种显示示意图；
图12B为本申请实施例提供的又一种显示示意图；
图12C为本申请实施例提供的又一种显示示意图；
图12D为本申请实施例提供的又一种显示示意图；
图12E为本申请实施例提供的又一种显示示意图；
图12F为本申请实施例提供的又一种显示示意图；
图13为本申请实施例提供的又一种信号交互示意图；
图14A为本申请实施例提供的又一种显示示意图；
图14B为本申请实施例提供的又一种显示示意图；
图14C为本申请实施例提供的又一种显示示意图；
图14D为本申请实施例提供的又一种显示示意图；
图14E为本申请实施例提供的又一种显示示意图；
图14F为本申请实施例提供的又一种显示示意图；
图15为本申请实施例提供的又一种信号交互示意图；
图16A为本申请实施例提供的又一种显示示意图；
图16B为本申请实施例提供的又一种显示示意图；
图16C为本申请实施例提供的又一种显示示意图；
图16D为本申请实施例提供的又一种显示示意图；
图16E为本申请实施例提供的又一种显示示意图；
图17A为本申请实施例提供的又一种信号交互示意图；
图17B为本申请实施例提供的又一种显示示意图；
图17C为本申请实施例提供的又一种显示示意图；
图17D为本申请实施例提供的又一种显示示意图；
图18A为本申请实施例提供的又一种显示示意图；
图18B为本申请实施例提供的又一种显示示意图；
图18C为本申请实施例提供的又一种显示示意图；
图18D为本申请实施例提供的又一种显示示意图；
图19为本申请实施例提供的又一种信号交互示意图；
图20为本申请实施例提供的又一种信号交互示意图；
图21为本申请实施例提供的又一种信号交互示意图；
图22为本申请实施例提供的又一种信号交互示意图；
图23为本申请实施例提供的一种芯片系统的结构示意图。
具体实施方式
本申请实施例涉及的系统架构可以包括多个电子设备，多个电子设备之间可以进行组网，组网后多个电子设备之间可以进行信息交互。组网方式包含不限于以下方式：
(1)、无线保真(wireless fidelity，Wi-Fi)组网方式：多个电子设备可以接入同一个路由设备(例如，路由器)。如图1所示，手机101、手机102、平板电脑103、笔记本电脑104、智慧电视105可以接入路由器106，组成一个家庭网络。或者，多个电子设备可以加入同一个热点设备(例如，接入同一个手机的热点)，此时电子设备和电子设备之间的信息交互，可以通过热点设备转发。例如，手机102、平板电脑103、笔记本电脑104、智慧电视105可以接入手机101，组成一个热点网络，手机101可以作为热点设备为各个电子设备转发信息。
(2)、蓝牙组网方式：多个电子设备可以连接到同一个蓝牙设备(例如，手机104)，此时电子设备和电子设备之间的信息交互，可以通过蓝牙设备转发。如图2所示，手机101、平板电脑103、笔记本电脑104、智慧电视105可以接入手机102，组成一个蓝牙网络，手机102可以作为蓝牙设备为各个电子设备转发信息。
多个电子设备可以采用多种组网方式，例如，同时采用无线保真组网方式和蓝牙组网方式，本申请不做限定。
如图3所示，本申请实施例以电子设备200(如手机)为例，对本申请实施例提供的电子设备的结构进行举例说明。电子设备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可以包括压力传感器，陀螺仪传感器，气压传感器， 磁传感器，加速度传感器，距离传感器，接近光传感器，指纹传感器，温度传感器，触摸传感器，环境光传感器和骨传导传感器等传感器。
可以理解的是，本实施例示意的结构并不构成对电子设备200的具体限定。在另一些实施例中，电子设备200可以包括比图示更多或更少的部件，或者组合某些部件，或者拆分某些部件，或者不同的部件布置。图示的部件可以以硬件，软件或软件和硬件的组合实现。
处理器210可以包括一个或多个处理单元，例如：处理器210可以包括应用处理器(application processor，AP)，调制解调处理器，图形处理器(graphics processing unit，GPU)，图像信号处理器(image signal processor，ISP)，控制器，存储器，视频编解码器，数字信号处理器(digital signal processor，DSP)，基带处理器，和/或神经网络处理器(neural-network processing unit，NPU)等。其中，不同的处理单元可以是独立的器件，也可以集成在一个或多个处理器中。
控制器可以是电子设备200的神经中枢和指挥中心。控制器可以根据指令操作码和时序信号，产生操作控制信号，完成取指令和执行指令的控制。
处理器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)接口等。
可以理解的是，本实施例示意的各模块间的接口连接关系，只是示意性说明，并不构成对电子设备200的结构限定。在另一些实施例中，电子设备200也可以采用上述实施例中不同的接口连接方式，或多种接口连接方式的组合。
充电管理模块240用于从充电器接收充电输入。其中，充电器可以是无线充电器，也可以是有线充电器。充电管理模块240为电池242充电的同时，还可以通过电源管理模块241为电子设备供电。
电源管理模块241用于连接电池242，充电管理模块240与处理器210。电源管理模块241接收电池242和/或充电管理模块240的输入，为处理器210，内部存储器221，外部存储器，显示屏294，摄像头293，和无线通信模块260等供电。在一些实施例中，电源管理模块241和充电管理模块240也可以设置于同一个器件中。
电子设备200的无线通信功能可以通过天线1，天线2，移动通信模块250，无线通信模块260，调制解调处理器以及基带处理器等实现。在一些实施例中，电子设备200的天线1和移动通信模块250耦合，天线2和无线通信模块260耦合，使得电子设备200可以通过无线通信技术与网络以及其他设备通信。
天线1和天线2用于发射和接收电磁波信号。电子设备200中的每个天线可用于覆盖单个或多个通信频带。不同的天线还可以复用，以提高天线的利用率。例如：可以将天线1复用为无线局域网的分集天线。在另外一些实施例中，天线可以和调谐开关结合使用。
移动通信模块250可以提供应用在电子设备200上的包括2G/3G/4G/5G等无线通信的解决方案。移动通信模块250可以包括至少一个滤波器，开关，功率放大器，低噪声放大器(low noise amplifier，LNA)等。移动通信模块250可以由天线1接收电磁波，并对接收的电磁波进行滤波，放大等处理，传送至调制解调处理器进行解调。
移动通信模块250还可以对经调制解调处理器调制后的信号放大，经天线1转为电磁波辐射出去。在一些实施例中，移动通信模块250的至少部分功能模块可以被设置于处理器210中。在一些实施例中，移动通信模块250的至少部分功能模块可以与处理器210的至少部分模块被设置在同一个器件中。
无线通信模块260可以提供应用在电子设备200上的包括WLAN(如(wireless fidelity，Wi-Fi)网络)，蓝牙(bluetooth，BT)，全球导航卫星系统(global navigation satellite system，GNSS)，调频(frequency modulation，FM)，近距离无线通信技术(near field communication，NFC)，红外技术(infrared，IR)等无线通信的解决方案。
无线通信模块260可以是集成至少一个通信处理模块的一个或多个器件。无线通信模块260经由天线2接收电磁波，将电磁波信号调频以及滤波处理，将处理后的信号发送到处理器210。无线通信模块260还可以从处理器210接收待发送的信号，对其进行调频，放大，经天线2转为电磁波辐射出去。
电子设备200通过GPU，显示屏294，以及应用处理器等实现显示功能。GPU为图像处理的微处理器，连接显示屏294和应用处理器。GPU用于执行数学和几何计算，用于图形渲染。处理器210可包括一个或多个GPU，其执行程序指令以生成或改变显示信息。
显示屏294用于显示图像，视频等。该显示屏294包括显示面板。
电子设备200可以通过ISP，摄像头293，视频编解码器，GPU，显示屏294以及应用处理器等实现拍摄功能。ISP用于处理摄像头293反馈的数据。摄像头293用于捕获静态图像或视频。在一些实施例中，电子设备200可以包括1个或N个摄像头293，N为大于1的正整数。
外部存储器接口220可以用于连接外部存储卡，例如Micro SD卡，实现扩展电子设备200的存储能力。外部存储卡通过外部存储器接口220与处理器210通信，实现数据存储功能。例如将音乐，视频等文件保存在外部存储卡中。
内部存储器221可以用于存储计算机可执行程序代码，所述可执行程序代码包括指令。处理器210通过运行存储在内部存储器221的指令，从而执行电子设备200的各种功能应用以及数据处理。例如，在本申请实施例中，处理器210可以通过执行存储在内部存储器221中的指令，内部存储器221可以包括存储程序区和存储数据区。
其中，存储程序区可存储操作系统，至少一个功能所需的应用程序(比如声音播放功能，图像播放功能等)等。存储数据区可存储电子设备200使用过程中所创建的数据(比如音频数据，电话本等)等。此外，内部存储器221可以包括高速随机存取 存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件，闪存器件，通用闪存存储器(universal flash storage，UFS)等。
电子设备200可以通过音频模块270，扬声器270A，受话器270B，麦克风270C，耳机接口270D，以及应用处理器等实现音频功能。例如音乐播放，录音等。
按键290包括开机键，音量键等。按键290可以是机械按键。也可以是触摸式按键。马达291可以产生振动提示。马达291可以用于来电振动提示，也可以用于触摸振动反馈。指示器292可以是指示灯，可以用于指示充电状态，电量变化，也可以用于指示消息，未接来电，通知等。SIM卡接口295用于连接SIM卡。SIM卡可以通过插入SIM卡接口295，或从SIM卡接口295拔出，实现和电子设备200的接触和分离。电子设备200可以支持1个或N个SIM卡接口，N为大于1的正整数。SIM卡接口295可以支持Nano SIM卡，Micro SIM卡，SIM卡等。
如图4所示，对本申请实施例提供的电子设备的软件结构进行举例说明。电子设备的软件架构可以包括应用层、应用框架层、硬件抽象层(hardware abstraction layer，HAL)和驱动层。本申请实施例以电子设备的操作系统是双框架操作系统(即安卓系统和鸿蒙系统)为例进行说明。电子设备也可以是安卓系统、鸿蒙系统、IOS系统或者其他操作系统，本申请实施例不做限定。
其中，应用层可以包括安卓应用和鸿蒙应用。其中，安卓应用可以包括设备管理(device manager)kit和分布式执行框架(distributed execute framework，DEF)kit。其中，kit(服务)可以是一种用于向应用层(的应用程序)提供基础服务的软件开发工具包(software development kit，SDK)。DM kit可以包括设备发现模块、可信设备维护模块、设备认证模块、设备筛选、排序模块等。鸿蒙应用可以包括DM kit和鸿蒙SDK。其中，SDK可以是指辅助开发某一类软件的相关文档、范例和工具的集合。
其中，DM kit可以包括设备发现模块、可信设备维护模块、设备认证模块、设备筛选、排序模块等。可选的，应用层还可以包括相机，图库，日历，通话，地图，导航，WLAN，蓝牙，音乐，视频，短信息等应用程序，本申请不做限定。
应用框架层可以包括DM、DEF、分布式调度管理服务(distributed scheduler manager Service，DMS)、二维码识别模块(hivision)、鸿蒙标签管理模块、安全管理模块、通信模块、设备信息数据库(device profile)。当然，应用框架层还可以包括活动管理器、窗口管理器，内容提供器，资源管理器，通知管理器等，本申请实施例对此不做任何限制。
其中，设备管理模块(DM模块)：主要提供设备发现，可信设备维护以及设备认证能力。通过维护本地设备信息，将信息写入二维码，扫码识别，建立物理连接以及维护设备群组信息来对同账号或异账号设备之间，安卓与鸿蒙设备之间建立安全可信的连接。可选的，DM中可以包括设备发现模块、可信设备维护模块、设备认证模块和设备排序、筛选模块。设备发现模块用于进行发送广播、发现设备、设备信息封装和设备列表弹框UI等处理。可信设备维护模块用于进行查询可信设备列表、写入可信设备信息、可信设备列表维护、监听可信设备上下线等处理。设备认证模块用于进行底层通道管理、访问控制、PIN码机制和群组管理等处理。设备排序、筛选模块用于进行设备筛选、设备排序等处理。
鸿蒙标签管理模块：负责提供鸿蒙标签申请、解析、格式化，鸿蒙标签服务查询以及服务分发能力。
分布式执行框架(DEF)：负责提供原子化服务的发现，注册，查询，迁移；负责设备之间底层数据通信和设备发现。
二维码识别模块：提供鸿蒙标签生成以及扫码能力，通过标签服务提供的标签信息生成鸿蒙二维码标签，通过扫描鸿蒙二维码标签触发标签服务解析标签信息。
安全管理模块(HiChain)：管理分布式场景下的群组，以及设备群组认证；群组包括公共群组和应用级私有群组。提供分布式场景下设备与设备间，应用与应用间的安全可信通信和连接。
通信模块(communication)：软总线管理分布式场景下同账号设备的自发现，自组网；扫描发现不同账号的设备；为不同设备间的通信提供通道，保障数据的安全稳定传输。
DMS：主要完成跨设备的服务绑定，以及跨设备的Android接口定义语言(android interface definition language，AIDL)接口调用能力。AIDL是用于定义服务器和客户端通信接口的一种描述语言。
设备信息数据库：负责设备信息的读写，存储与管理。
HAL可以包括麦克风、扬声器、Wi-Fi模组、蓝牙模组、摄像头、传感器等。
驱动层是硬件和软件之间的层，也可以称为内核层。内核层至少包含显示驱动，摄像头驱动，音频驱动，传感器驱动。
上述软件架构可以部署在当前组网环境内的多个电子设备上(例如，如图1或图2中的手机101、手机102、平板电脑103、笔记本电脑104、智慧电视105、路由器106等等)。
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。其中，在本申请的描述中，除非另有说明，“至少一个”是指一个或多个，“多个”是指两个或多于两个。另外，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。
为了下述各实施例的描述清楚简洁，首先给出相关概念或技术的简要介绍：
Ability：Ability是应用所具有的能力的抽象，一个应用可以包含一个或者多个Ability。HarmonyOS支持应用以Ability为单位进行部署。Ability分为两种类型：FA(特性能力)和AA(元能力)。
AA：由三方基于鸿蒙系统服务开发，实现单一功能的程序实体，用于提供后台运行任务的能力，无UI界面。AA具有多端部署、分布执行的特性。AA对系统服务有依赖关系，AA之间不存在依赖关系。
FA：用于提供与用户交互的能力(功能)。一个FA可以包含一组相关页面(也可以认为是一组UI)，每个页面可以用一个AbilitySlice实例表示。FA可以通过调用AA实现复杂功能的程序实体，基于新的界面/数据/逻辑分离的结构开发，可以独立打包和上架。FA具有以下能力：免安装，脱离应用独立运行、跨设备UI迁移、跨设备 二进制迁移等能力。FA与小程序或快应用的UI界面有部分类似，但实质上是不同的。其区别可以包括两点，一是FA可以跨设备迁移(例如，可以将手机A的FA迁移到手机B，这样手机B可以控制手机A的该FA)；二是FA可以跨平台，例如，FA既可以运行在安卓系统，也可以运行在鸿蒙系统，目前的小程序或快应用通常运行在安卓系统。
目前，可以采用FA分享技术在不同设备之间分享FA，即可以将一个设备的FA迁移至另一个设备进行展示和操作。在分享FA之前，需要进行认证，保证FA分享的安全可靠。
本申请实施例提供一种功能迁移方法，包括设备级认证和应用级认证。不同设备之间经过应用级认证后，不同设备间的特定应用可以实现互通(即应用之间可以交换业务数据，例如迁移FA)。例如，设备A的第一应用和设备B的第一应用相互认证后，设备A的第一应用和设备B的第一应用可以实现互通，但设备A的其他应用(例如第二应用)和设备B的其他应用(例如第二应用)之间不互通。经过设备级认证后，不同设备间的所有应用可以实现互通。
为了便于理解，以下以手机A和手机B为例，对本申请实施例提供的设备级认证的用户界面(user interface，UI)界面进行介绍。
如图5A中的(a)所示，用户可以从设置应用进入智慧协同界面501，智慧协同界面501可以包括名称为“我的设备”的列表。其中，“我的设备”包括本机(即手机A)、kiki’s Mate pad和kiki’s Mate book pro。本机、kiki’s Mate pad和kiki’s Mate book pro可以是同账号(例如，共用一个华为账号)的设备。或者，本机、kiki’s Mate pad和kiki’s Mate book pro可以是异账号但经过认证(认证过程可以参考下文的相关描述)的设备。
可选的，智慧协同界面501可以包括绑定其他设备按钮502。本申请实施例中，绑定是指两个设备间建立可信关系，从而两个设备的任意应用之间可以实现互通，例如可以相互迁移FA，无需认证。响应于用户对绑定其他设备按钮502的操作(例如，点击操作)，如图5A中的(b)所示，手机A可以显示碰一碰添加按钮503和扫一扫添加按钮504。应该理解的是，图5A中的(a)和(b)分别对应的UI界面中的各个元素(例如，按钮、图标、文字等)的位置、名称和形状等不是固定不变的，可以根据需求进行自由组合或设计。例如，可以将图5A中的(a)中的按钮502可以替换为图5A中的(b)中的按钮503和按钮504。
例如，响应于用户对碰一碰添加按钮503的点击操作，如图5B中的(a)所示，手机A可以显示碰一碰添加界面505，碰一碰添加界面505中可以显示弹框506，弹框506中包括提示图画和提示信息，提示信息例如可以是：“碰一碰添加，手机开启NFC后，用背面碰一碰设备上的ontag标签”。用户可以根据提示信息进行操作，以便通过碰一碰的方式添加新的设备。又例如，响应于用户对扫一扫添加按钮504的点击操作，如图5B中的(b)所示，手机A可以显示扫一扫添加界面507，扫一扫添加界面507中可以包括提示图画和提示信息，提示信息例如可以是：“扫描设备或包装上的二维码”。用户可以根据提示信息进行操作，以便通过扫一扫的方式添加新的设备。
若手机A不支持通过碰一碰和扫一扫的方式添加新的设备，如图5C中的(a)所 示，响应于用户点击绑定其他设备按钮502的操作，如图5C中的(b)所示，手机A可以显示弹框508，弹框508中包括提示信息“请确保设备已开启，且位于手机附近”，弹框508中还可以包括手机A基于短距通信网络(例如，Wi-Fi网络或蓝牙网络)检测到的设备，例如房间电视、HUAWEI P20和Mate book X pro等设备。每个设备对应一个绑定按钮。响应于用户对HUAWEI P20对应的绑定按钮509的操作，如图5D中的(a)所示，HUAWEI P20的标识下方可以显示提示信息510“等待对端确认...”。弹框508中还可以取消按钮511，响应于用户点击取消按钮511的操作，手机A可以返回如图5C中的(a)所示的界面。
若对端设备确认(例如，对端设备的用户同意绑定)，如图5D中的(b)所示，手机A可以显示绑定新设备界面512，绑定新设备界面512中可以包括提示信息“扫一扫对端显示的二维码”，用户可以根据提示信息进行操作，以便添加新的设备。应该理解的是，本申请实施例不限定不同UI界面的跳转关系。例如，如图5C中的(b)所示，响应于用户点击绑定按钮509的操作，如图5D中的(b)所示，手机可以直接显示扫描界面512。
若对端设备未确认(例如，对端设备不具备绑定功能，绑定超时，或者对端设备正忙，或者对端设备的用户不同意绑定)，如图5E中的(a)所示，手机A可以显示弹框521，提示用户“设备认证失败”，响应于用户点击知道按钮522的操作，弹框521可以隐去。或者，弹框521可以在预设时间(例如，3s)后隐去。在另一种可能的设计中，如图5E中的(b)所示，手机A可以显示弹框523，提示用户“对端正忙，请稍后发起绑定”，响应于用户点击知道按钮524的操作，弹框523可以隐去。或者，弹框523可以在预设时间(例如，3s)后隐去。在又一种可能的设计中，如图5E中的(c)所示，手机A可以显示弹框525，提示用户“对端拒绝信任此设备，绑定失败”，响应于用户点击知道按钮526的操作，弹框525可以隐去。或者，弹框525可以在预设时间(例如，3s)后隐去。或者，如图5F所示，手机A可以在界面512中显示弹框527，提示用户“对端二维码已关闭，无法完成设备认证，绑定失败”。响应于用户点击知道按钮528的操作，弹框527可以隐去。
假设对端设备是手机B(例如可以是HUAWEI P20)，若手机B在显示桌面530时接收到手机A的绑定请求，如图6A中的(a)所示，手机B可以显示弹框531，弹框531中可以包括提示信息532“HUAWEI MATE30请求绑定本机，是否信任此设备”，弹框531中还可以包括不信任按钮533和信任按钮534。不信任按钮中还可以显示倒计时(例如，14s)，倒计时结束时若用户未点击任何按钮可以自动隐去弹框531。响应于用户点击信任按钮534的操作，手机A可以与手机B进行认证过程(参考下文关于步骤718A-步骤732的相关描述)，从而手机A可以绑定手机B。
若手机B在息屏状态或锁屏状态下接收到手机A的绑定请求，如图6A中的(b)所示，手机B可以在锁屏界面535中显示弹框536，弹框536可以提示用户智慧协同应用在上午7:30接收到设备绑定请求，具体可以是“HUAWEI MATE30(即手机A)请求绑定本机，是否信任此设备？”响应于用户从锁屏状态进入桌面的操作(例如，输入密码或输入指纹)，如图6A中的(a)所示，弹框536可以变更为弹框531的形式，用户可以选择信任或不信任HUAWEI MATE30(即手机A)。
若手机B在视频播放或游戏状态下接收到手机A的绑定请求，如图6B中的(a)所示，手机B可以在视频界面或游戏界面540中显示弹框541，弹框541可以提示用户智慧协同应用接收到设备绑定请求，具体可以是“HUAWEI MATE30请求绑定本机，是否信任此设备？”。响应于用户点击下拉控件542的操作，如图6B中的(b)所示，弹框541可以展示更多信息，例如可以显示不信任按钮543和信任按钮544。不信任按钮543中还可以显示倒计时(例如，14s)，倒计时结束时若用户未点击任何按钮可以自动隐去弹框541。响应于用户点击信任按钮544的操作，手机A可以与手机B进行认证过程(参考下文关于步骤718A-步骤732的相关描述)。
在一种可能的设计中，响应于用户点击信任按钮的操作，如图6C所示，手机B可以返回桌面530，且显示弹框550，弹框550中可以包括手机B生成的二维码551，还可以包括提示信息552“扫一扫绑定，允许HUAWEI MATE30扫一扫绑定本机”。此时，手机A的用户可以用手机A扫描手机B显示的二维码，以便手机A与手机B进行绑定。弹框550中还可以包括取消按钮553，响应于用户点击取消按钮553的操作，弹框550可以隐去。
在一些实施例中，若手机A和手机B登录了同一个账号(例如，华为账号)，手机A可以直接与手机B绑定(例如，如图5C中的(b)，在手机A上点击手机B(HUAWEI P20)对应的绑定按钮)，无需等待手机B确认(例如，无需如图5D中的(a)一样等待对端确认，也无需如图5D中的(b)一样扫描对端显示的二维码)。
下面以手机A和手机B为例，对本申请实施例提供的设备级认证方法的具体实现方式进行说明。其中，手机A和手机B为异账号设备。如图7A所示，包括：
701、用户在手机A上触发绑定手机B的操作。
例如，用户可以在手机A上点击手机B对应的绑定按钮。例如，如图5C中的(b)所示，响应于用户在手机A上点击手机B(HUAWEI P20)对应的绑定按钮509的操作，手机A执行步骤702。
702、手机A的设置应用向手机A的DM发起绑定请求。
其中，设置应用是指名称为“设置”的应用程序，该设置应用用于对手机A的基础功能进行配置，例如可以用于网络配置、显示和亮度配置、声音和振动配置、应用管理配置等。
其中，绑定请求中携带的信息可以包括手机A的名称(例如，HUAWEI MATE30)。
703、可选的，手机A的DM收到设置应用发送的绑定请求后，向手机A的设备信息数据库请求已认证设备的信息。
手机A的DM可以从设备信息数据库中读取已认证过的设备的信息。设备信息数据库中存储有已与手机A认证过的设备的信息。其中，认证过的设备的信息可以包括设备名称和设备ID。设备ID例如可以是国际移动设备识别码(international mobile equipment identity，IMEI)。示例性的，与手机A认证过的设备的信息可以如表1所示。
表1
设备名称 设备ID(IMEI)
kiki’s Mate pad 123456XXXXXXX
kiki’s Mate book pro 654321XXXXXXX
704、可选的，手机A的设备信息数据库向手机A的DM返回已认证设备的信息。
在一种可能的设计中，当手机A与手机B相互认证后，已认证设备的信息可以包括手机B的信息。
应该理解的是，在手机A与手机B进行设备级认证时，步骤703和步骤704是可选的。若执行步骤703和步骤704，即若获取到已认证设备的信息，手机A可以向用户展示已认证设备。已认证设备可以默认是绑定状态，或者，可以对已认证设备重新进行绑定。
步骤703和步骤704是手机A的DM获取已认证设备的信息的一种示意的实现方式，手机A的DM还可以通过其他方式获取已认证设备的信息(例如，从预设存储空间读取已认证设备的信息)，本申请不做限定。
705、手机A的DM向手机A的通信模块请求附近设备的信息。
设备管理可以通过一个常驻服务调用设备A的通信模块持续向周边发送广播，这样设备管理可以通过注册广播监听服务来发现近场全量设备(即近场通信下的全部设备，其中，近场通信可以包括无线保真通信、蓝牙通信等)。再结合从设备信息数据库中读取的已认证过的设备的信息，DM可以以图标的形式分类展示近场全量设备中的已认证设备(如图5C中的(a)所示的kiki’s Mate pad，kiki’s Mate book pro等)和未认证设备(如图5C中的(b)所示的房间电视，HUAWEI P20和Mate book X pro等)。
需要说明的是，步骤703和步骤705之间没有必然的执行先后顺序，本实施例对此不作具体限定。
706、手机A的通信模块向手机A的DM返回附近设备的信息。
707、手机A的DM弹出附近设备列表。
如图5C中的(b)所示，手机A的DM可以调用弹框能力，从而在手机A的显示屏弹出弹框508(即附近设备列表)，弹框508中包括房间电视，HUAWEI P20和Mate book X pro等附近设备。
708、用户选择需要绑定的设备。
例如，如图5C中的(b)所示，用户可以从附近设备列表中选择需要绑定的设备，例如用户可以选中HUAWEI P20(即手机B)。
709、手机A的DM向手机A的通信模块请求创建底层通道。
底层通道可以是蓝牙通道或Wi-Fi通道等，本申请不做限定。
710、手机A的通信模块与手机B的通信模块进行信息交互，创建底层通道。
711、可选的，手机A的通信模块向手机A的DM发送创建成功通知。
即手机A的通信模块向手机A的DM发送底层通道创建成功通知，表示手机A的通信模块与手机B的通信模块之间成功创建底层通道。
应该理解的是，在手机A与手机B进行设备级认证时，步骤711是可选的。若执行步骤711，后续手机A的DM可以及时获知底层通道创建成功，以便后续可以通过底层通道传输数据。或者，也可以基于其他方式获知底层通道创建成功，例如，经过预设时间未收到底层通道创建失败的通知，可以认为底层通道创建成功。
712、手机A的DM通过手机A的通信模块向手机B发送认证请求消息。
其中，认证请求消息可以包括手机A的标识(例如，名称或ID)和手机A生成的身份认证信息，手机A生成的身份认证信息可以包括手机A生成的令牌(token)。手机A的名称例如可以是HUAWEI MATE30。token例如可以是若干位的随机字符串。
其中，token可以用于身份认证。本申请实施例中，手机A可以向手机B发送token，token可以是手机A的设备号/设备mac地址，也可以是用来确定手机A的其它标识。当手机B接收到手机A的token后，可以将该token的信息加入到手机B后续生成二维码图片中，使得该二维码图片只能被手机A所使用。
如图7B所示，上述方法还包括：
713、可选的，手机B的通信模块向手机B的DM发送创建成功通知。
即手机B的通信模块向手机B的DM发送底层通道创建成功通知，表示手机B的通信模块与手机A的通信模块之间成功创建底层通道。
应该理解的是，在手机A与手机B进行设备级认证时，步骤713是可选的。若执行步骤713，后续手机B的DM可以及时获知底层通道创建成功，以便后续可以通过底层通道传输数据。或者，也可以基于其他方式获知底层通道创建成功，例如，经过预设时间未收到底层通道创建失败的通知，可以认为底层通道创建成功。
需要说明的是，步骤711和步骤713之间没有必然的执行先后顺序，本实施例对此不作具体限定。
714、手机A的通信模块向手机B的通信模块发送认证请求消息。
手机A的通信模块可以通过底层通道向手机B的通信模块发送认证请求消息。
715、手机B的通信模块将认证请求消息转发给手机B的DM。
可以理解的是，步骤712、步骤714和步骤715用于描述手机A向手机B发送认证请求消息的过程。手机A的DM与手机B的DM需要分别通过手机A的通信模块和手机B的通信模块进行通信，当然，手机A的DM与手机B的DM也可以通过其他模块通信，或者，手机A的DM与手机B的DM可以具有通信能力直接可以进行通信，本申请不做限定。
716、可选的，手机B的DM通过弹窗通知用户是否同意绑定。
示例性的，如图6A中的(a)所示，手机A可以弹出弹框531，弹框531中可以包括提示信息532“HUAWEI MATE30请求绑定本机，是否信任此设备”，弹框531中还可以包括不信任按钮533和信任按钮534。
717、可选的，手机B接收用户同意绑定的操作。
例如，如图6A中的(a)所示，用户点击信任按钮534可以表示用户同意绑定。
若用户同意(例如，如图6A中的(a)所示，若用户点击信任按钮534)，手机B的DM可以通过通信模块将用户同意的信息返回给手机A的DM，手机A可以提示用户主动扫描对端(手机B)显示的二维码(二维码图片)。
另外，若用户不同意(例如，若用户点击不信任按钮533)，手机B的DM可以通过通信模块将用户不同意的信息返回给手机A的DM，手机A可以显示如图5E中的(c)所示的提示信息，绑定失败。
应该理解的是，在手机A与手机B进行设备级认证时，步骤716和步骤717可以 是可选的。例如，若手机A与手机B登录了同一个账号，或者设置了亲情号码等服务，手机B可以不向用户请求是否同意绑定，直接执行步骤718A及其后续的必要步骤。
步骤716和步骤717是手机B提示用户是否同意绑定的一种实现方式，手机B还可以通过其他方式提示用户，例如通过后台系统通知消息通知，本申请不做限定。
718A、手机B的DM判断手机B是否建立过与手机A相关的群组。
手机B的DM可以从手机B的HiChain中查询手机B是否建立过与手机A相关的公共群组。其中，手机B的HiChain可以存储手机B建立过的全部群组信息，包括公共群组和私有群组。其中，公共群组可以是指以设备为粒度建立的群组，例如两个设备属于一个公共群组表示两个设备经过设备级的认证，两个设备之间的所有应用可以安全互通。私有群组是指以设备和应用为粒度建立的群组，例如，第一设备的第一应用可以与第二设备的第二应用进行应用级认证。经过应用级认证后，第一应用与第二应用属于一个私有群组，此时第一应用与第二应用可以安全互通(例如，可以安全分享数据)。第一应用与第二应用的标识可以相同或不相同，本申请不对此进行限定。两个设备分别对应的一个应用属于一个私有群组表示该两个设备经过应用级的认证，两个设备分别对应的特定应用之间可以安全互通。示例性的，手机B建立过的全部群组信息可以如表2所示：
表2
公共群组 私有群组
群组1(手机B，手机C) 群组3(手机B的应用1，手机D的应用2)
群组2(手机B，手机D) 群组4(手机B的应用1，手机E的应用3)
可选的，表2中的群组1和群组2可以组合成一个包括3个成员的群组，例如群组5(手机B，手机C，手机D)。这样，手机A可以从群组5中查找与手机A进行过设备级认证的设备，无需遍历两两设备之间建立的公共群组。
可选的，表2中的群组3和群组4可以组合成一个包括3个成员的群组，例如群组6(手机B的应用1，手机D的应用2，手机E的应用3)。这样，手机A可以从群组6中查找与手机A进行过应用级认证的设备的应用，无需遍历两两应用之间建立的私有群组。
718B、如果手机B未建立过与手机A相关的群组，手机B的DM向手机B的安全管理模块请求创建群组。
手机B的安全模块创建一个关于手机A的群组，群组名为手机A和手机B的设备ID。进一步可以设置手机A和手机B之间的群组属性为公共，即手机A和手机B之间的所有应用可以互通。
718C、手机B的安全管理模块向手机B的DM发送群组创建成功通知。
应该理解的是，步骤718B和步骤718C是一种示意的创建群组的方式，本申请不限定其他创建群组的方式，例如，手机B的DM可以直接创建群组。
719、手机B的DM向手机B的鸿蒙标签管理模块请求标签。
手机B的鸿蒙标签管理模块可以生成标签，标签中包括认证校验信息以及手机B的会话标识，认证校验信息可以包括从手机A接收的token。或者，可以认为认证校验信息包括从手机A接收的token和手机B的会话标识。手机B的会话标识中包括手 机B的设备连接信息。例如，手机B的会话标识包括手机B的Wi-Fi地址(例如，IP地址和端口(Port)号)或者蓝牙地址。
认证校验信息中还可以包括群组对应的个人识别密码PIN。PIN例如可以是若干位随机数字，例如可以为6位或8位随机数字等。本申请实施例中，手机B可以向手机A发送群组对应的PIN。当手机A需要加入手机B创建的群组时，可以在请求中携带群组对应的PIN。手机B确定手机A携带的PIN是正确的(即是手机B发送给手机A的)，认为手机A是安全可信的，允许手机A加入手机B创建的群组。
720、手机B的鸿蒙标签管理模块向手机B的二维码识别模块请求认证校验信息的二维码图片(BitMap)。
手机B的二维码识别模块可以根据认证校验信息组装二维码图片。需要说明的是，上述实施例以二维码图片为标识符进行示意说明，可以将二维码图片替换为其他类型的标识符，例如条形码、字符串等，本申请不做限定。
721、手机B的二维码识别模块向手机B的鸿蒙标签管理模块返回二维码图片。
722、手机B的鸿蒙标签管理模块向手机B的DM返回二维码图片。
723a、可选的，手机B的DM向手机B的通信模块发送二维码图片。
在一种可能的设计中，手机B的DM可以通过手机B的通信模块将手机B的二维码图片发送给手机A，以便手机A对该二维码图片进行内部扫描，即在步骤723a之后，可以执行步骤723b-步骤725。在另一种可能的设计中，手机B可以将手机B的二维码图片显示在手机B的显示界面(如图6C所示的显示界面)，以便手机A直接扫描，从而使得手机A中的二维码识别模块可以直接获取手机B生成的二维码图片，从而跳过步骤723b-步骤725。上述两种设计均可以实现本方案的技术效果，本申请不对此进行限定。
723b、可选的，手机B的通信模块向手机A的通信模块发送二维码图片。
手机A的DM可以拉起二维码识别模块，通过二维码识别模块扫描手机B生成的二维码图片。
如图7C所示，上述方法还包括：
724、可选的，手机A的通信模块向手机A的DM发送二维码图片。
725、可选的，手机A的DM向手机A的二维码识别模块发送二维码图片。
726、手机A的二维码识别模块扫描二维码图片，将识别到的信息发送给手机A的鸿蒙标签管理模块。
727、手机A的鸿蒙标签管理模块解析二维码识别模块发送的信息，得到解析结果。
其中，解析结果可以包括token、PIN和手机B的会话标识等信息。
728、手机A的鸿蒙标签管理模块向手机A的DM发送解析结果。
可以理解的是，步骤724-步骤728是手机A处理二维码图片的一种示意的实现方式，手机A还可以通过其他方式处理二维码图片，本申请不做限定。例如，手机A的DM可以集成二维码图片处理功能，这样手机A的DM可以直接扫描和解析二维码图，以得到token、PIN和手机B的会话标识等信息。
729、手机A的DM校验token。
若从手机B接收到的token与认证请求消息中携带的token相同，执行步骤730。
730、手机A的DM回调认证成功。
应该理解的是，在手机A与手机B进行设备级认证时，步骤729和步骤730是可选的。若执行步骤729和步骤730，即若手机A的DM校验token，可以更好地保证手机A和手机B通信的安全性。
731、手机A加入手机B创建的公共群组。
手机A的DM根据会话标识确定手机B的Wi-Fi地址或者蓝牙地址，向手机A的安全模块申请加入手机B创建的群组。
手机A的安全模块利用Wi-Fi地址或蓝牙地址创建底层通信通道，并向手机B发送加入群组请求，加入群组请求中可以包括群组ID。可选的，加入群组请求中还可以包括PIN。手机B接收到加入群组请求，可以校验PIN，认证通过(即该PIN与二维码图片中的PIN相同)后，两个设备加入同一个群组(该群组的群组成员可以包括手机A和手机B，该群组的属性为公共)，完成认证。
在一种可能的实现方式中，当手机B接收到加入群组请求并认证通过后，会向手机A发送一个响应消息，该响应消息指示手机A已加入手机B创建的公共群组。
732、手机A的安全管理模块通知应用程序(设置应用)认证成功。
手机A可以在本地保存群组的信息。群组的信息可以群组成员(该群组的群组成员可以包括手机A和手机B)，群组的信息还可以包括群组的群组名和属性信息(例如，属性为公共)。
这样，手机A和手机B之间完成了设备级认证，手机A和手机B间的所有应用可以实现互通。例如，手机A的直播应用、K歌应用、购物应用和邮件应用可以和手机B的直播应用、K歌应用、购物应用和邮件应用之间互通。
在一些实施例中，若手机A和手机B中的一个登录了账号(例如，华为账号)，另一个没有登录账号，手机A和手机B可以执行上述步骤701-步骤732的全部或者部分步骤。以便在手机A和手机B绑定时进行验证(即进行设备级认证)，以保证设备间的数据的安全。
在一些实施例中，若手机A和手机B都没有登录账号(例如，华为账号)，手机A和手机B可以执行上述步骤701-步骤732。以便在手机A和手机B绑定时进行验证，以保证设备间的数据的安全。
在一些实施例中，若手机A和手机B登录了同一个账号(例如，华为账号)，手机A和手机B可以执行上述步骤701-步骤732。以便在手机A和手机B绑定时进行验证，进一步保证设备间的数据的安全。
需要说明的是，上述步骤701-步骤732中的部分步骤可以是可选的，即不是设备级认证方案的必要技术特征。例如，步骤703和步骤704可以是可选的步骤，即可以不查询已认证设备，直接查看周边的设备。又例如，步骤711和步骤713可以是可选的步骤，即可以不发送创建成功通知。又例如，步骤716和步骤717可以是可选的步骤，即可以不经过用户同意，直接绑定。又例如，步骤723b-步骤725可以是可选的步骤，此时手机A可以直接获取手机B生成的二维码图片(例如，通过扫描手机B显示的二维码图片)。
若设备之间未进行设备级认证，设备间的应用可以进行应用级认证，从而使得特定应用之间可以互通。下面结合具体的场景，以直播应用为例，对本申请实施例提供的应用级认证的UI界面进行介绍。
随着电商的发展，越来越多的人关注到直播卖货这种销售新渠道。直播卖货不仅要求带货设备拍摄清晰，拾音准确，还要有更佳的交互体验。直播卖货当前的一个痛点是在同一个镜头下无法同时展示主播和清晰的商品细节，导致电商秀导展示的真实感、认同感降低。
本申请针对直播业务，提供了一种基于跨设备FA分享的分布式展示方案，例如可以将手机A的直播画面(设备A的直播画面可以认为是一个FA，例如FA1)分享至手机B，手机B可以同时显示手机A的FA和手机B的直播画面(设备B的直播画面可以认为是一个FA，例如FA2)，达到跨设备展示一个或多个FA的体验，省去用户来回切换终端的繁琐，大大减少了用户操作。本申请不要求设备之间满足同系统的要求，也不要求设备登录同一个设备账号(例如，同一个华为账号)，适用范围广。
示例性的，如图8A所示，用户在手机A打开直播应用后，手机A可以显示直播界面801，直播界面801可以包括迁移按钮802，迁移按钮802位于界面801的左上角。应该理解的是，迁移按钮802也可以位于界面801的左下角、右下角、右上角等位置，本申请不做限定。当然，按钮802上显示的文字也可以是其他内容，例如可以是共享、转移等，本申请不做限定。响应于用户在直播界面801点击迁移按钮802(迁移按钮802用于将手机A的直播界面迁移(发送)至其他设备(例如，手机B))的操作，如图8B中的(a)所示，手机A可以弹出弹框803。应该理解的是，本申请实施例不限定UI界面之间的跳转方式。例如，如图8A所示，响应于用户特定手势(例如，三指下滑、指关节敲击等)的操作，如图8B中的(a)所示，手机可以显示弹框803。其中，弹框803中可以包括附近的设备，附近的设备包括已认证设备(卧室电视，monica’s Mate pad等)和未认证设备(房间电视，HUAWEI P20和Mate book X pro等)。响应于用户点击HUAWEI P20(未认证过的设备)对应的控件804的操作，手机A可以向手机B发送认证请求消息。并且，如图8B中的(b)所示，在HUAWEI P20的下方可以显示提示信息805“等待对端确认”。如图8C中的(a)所示，若手机B(HUAWEI P20)在显示直播界面811时，接收到手机A发送的认证请求消息，手机B可以显示弹框812，弹框812中包括提示信息“HUAWEI MATE30(手机A)请求将直播界面迁移到本机，是否同意”，响应于用户点击下拉按钮813的操作，如图8C中的(b)所示，弹框812可以显示更多内容，例如显示不同意按钮814和同意按钮815a。可选的，响应于用户点击同意按钮815a的操作，如图8C中的(c)所示，手机可以显示弹框815b，弹框815b中可以包括仅本次同意按钮815c和一直同意(以后不再提示)按钮815d。响应于用户点击同意按钮815a或仅本次同意按钮815c或一直同意按钮815d的操作，如图8D所示，手机B可以显示弹框816，弹框816中可以包括手机B生成的二维码图片，还可以包括提示信息817“扫一扫认证，允许HUAWEI MATE30扫一扫认证”。此时手机A的用户可以扫一扫手机B展示的二维码图片，而后，手机B可以从手机A接收直播画面(FA1)，如图8E所示，手机B可以在直播界面811上显示手机A发送的直播界面819。或者，响应于用户点击同意按钮815的操作，手机 B可以从手机A接收直播画面(FA1)，如图8E所示，手机B可以在直播界面811上显示手机A发送的直播界面819。
下面以直播应用为例，对本申请实施例提供的应用级认证方法的具体实现方式进行说明。本申请实施例提供的方法可以应用于两个近场设备，例如手机A和手机B，手机A和手机B为异账号设备(例如，未登录同一个华为账号)，且手机A和手机B都打开了直播应用。如图9A所示，包括：
901、手机A接收用户触发功能迁移的操作。
例如，如图8A所示，用户可以在手机A直播主播的情况下点击迁移按钮802。迁移按钮也可以称为分享按钮、发送按钮等，本申请不做限定。
用户可以通过其他方式触发功能迁移，例如，可以通过“碰一碰”或“扫一扫”的方式触发功能迁移，本申请不做限定。
902、应用程序(例如，直播应用)向手机A的DM发起迁移请求。
其中，迁移请求中携带的信息可以包括发起端的应用程序的标识(本端直播应用包名)，接续端的应用程序的标识(对端直播应用包名)和手机A的名称。其中，接续端包名可以是应用程序(例如，直播应用)给出的，取决于应用厂商对应用程序的设计，在此不做赘述。
在一种可能的设计中，迁移请求中携带的信息可以是根据预设顺序排列的。例如，预设顺序可以依次是手机A的名称、发起端的应用程序的标识和接续端的应用程序的标识。或者，预设顺序可以依次是发起端的应用程序的标识、接续端的应用程序的标识和手机A的名称。
903、可选的，手机A的DM收到迁移请求后，向手机A的设备信息数据库请求已认证的设备。
具体过程可以参考步骤703中的相关描述，在此不做赘述。
904、可选的，手机A的设备信息数据库向手机A的DM返回已认证设备的信息。
应该理解的是，在手机A与手机B进行设备级认证时，步骤903和步骤904是可选的。若执行步骤903和步骤904，即若获取到已认证设备的信息，手机A可以向用户展示已认证设备。
步骤903和步骤904是手机A的DM获取已认证设备的信息的一种示意的实现方式，手机A的DM还可以通过其他方式获取已认证设备的信息(例如，从预设存储空间读取已认证设备的信息)，本申请不做限定。
905、手机A的DM向手机A的通信模块请求附近设备的信息。
具体过程可以参考步骤705中的相关描述，在此不做赘述。
906、手机A的通信模块向手机A的DM返回附近设备的信息。
907、手机A的DM弹出附近设备列表。
附近设备列表例如可以是如图8B中的(a)所示的弹框803。
用户可以从附近设备列表中选择设备，若是不可信设备(即未进行过认证的异账号设备(例如未登录同一个华为账号))，步骤907之后，可以执行步骤908-步骤936，进行应用级认证。若是可信设备((例如，登录了同一个华为账号，或者之前认证(包括设备级认证或应用级认证)过)，则可以直接迁移FA，即步骤907之后，可以直接 执行步骤933-步骤936。
908、用户选中未认证设备。
例如，如图8B中的(a)所示，用户选中HUAWEI P20，HUAWEI P20为不可信设备。
909、手机A的DM向手机A的通信模块请求创建底层通道。
底层通道可以是蓝牙通道或Wi-Fi通道等，本申请不做限定。
910、手机A的通信模块与手机B的通信模块进行信息交互，创建底层通道。
911、可选的，手机A的通信模块向手机A的DM发送底层通道创建成功通知。
应该理解的是，在手机A与手机B进行设备级认证时，步骤911是可选的。若执行步骤911，后续手机A的DM可以及时获知底层通道创建成功，以便后续可以通过底层通道传输数据。或者，也可以基于其他方式获知底层通道创建成功，例如，经过预设时间未收到底层通道创建失败的通知，可以认为底层通道创建成功。
912、手机A的DM通过手机A的通信模块向手机B发送认证请求消息。
其中，认证请求消息包括发起端设备名称(例如，HUAWEI MATE30)，发起端包名(例如com.zhibo.video)，接续端包名(例如com.zhibo.video)。认证请求消息还包括手机A生成的token。
如图9B所示，上述方法还包括：
913、可选的，手机B的通信模块向手机B的DM发送底层通道创建成功通知。
需要说明的是，步骤911和步骤913之间没有必然的执行先后顺序，本实施例对此不作具体限定。
应该理解的是，在手机A与手机B进行设备级认证时，步骤913是可选的。若执行步骤913，后续手机B的DM可以及时获知底层通道创建成功，以便后续可以通过底层通道传输数据。或者，也可以基于其他方式获知底层通道创建成功，例如，经过预设时间未收到底层通道创建失败的通知，可以认为底层通道创建成功。
914、手机A的通信模块向手机B的通信模块发送认证请求消息。
认证请求消息中携带的信息可以包括发起端的应用程序的标识，接续端的应用程序的标识和手机A的名称。
在一种可能的设计中，认证请求消息中携带的信息可以是根据预设顺序排列的。例如，预设顺序可以依次是手机A的名称、发起端的应用程序的标识和接续端的应用程序的标识。或者，预设顺序可以依次是发起端的应用程序的标识、接续端的应用程序的标识和手机A的名称。
915、手机B的通信模块将认证请求消息转发给手机B的DM。
可以理解的是，步骤912、步骤914和步骤915用于描述手机A向手机B发送认证请求消息的过程。手机A的DM与手机B的DM需要分别通过手机A的通信模块和手机B的通信模块进行通信，当然，手机A的DM与手机B的DM也可以通过其他模块通信，或者，手机A的DM与手机B的DM可以具有通信能力直接可以进行通信，本申请不做限定。
916、可选的，手机B的DM通过弹窗通知用户是否同意迁移。
示例性的，如图8C中的(a)所示，若手机B在显示直播界面811时，接收到手 机A发送的认证请求消息，手机B可以显示弹框812，弹框812中包括提示信息“HUAWEI MATE30请求将直播界面迁移到本机，是否同意”，响应于用户点击下拉按钮813的操作，如图8C中的(b)所示，弹框812可以显示更多内容，例如显示不同意按钮814和同意按钮815a。
可选的，响应于用户点击同意按钮815a的操作，如图8C中的(c)所示，手机可以显示弹框815b，弹框815b中可以包括仅本次同意按钮815c和一直同意(以后不再提示)按钮815d。应该理解的是，响应于用户点击仅本次同意按钮815c的操作，执行下述步骤917-步骤932后，手机A可以向手机B迁移一次直播界面(即FA1)。下次从手机A的直播应用向手机B的直播应用迁移FA时，需要重新认证，例如可以重新执行步骤901-步骤932。响应于用户点击一直同意按钮815d的操作，执行下述步骤917-步骤932后，手机A的直播应用可以一直向手机B的直播应用迁移FA，无需再次认证(例如无需重新执行步骤901-步骤932)。
917、可选的，手机B接收用户同意迁移的操作。
示例性的，如图8C中的(b)所示，手机B可以接收用户点击同意按钮815a的操作。
若用户同意(例如，若用户点击同意按钮815a)，手机B的DM可以通过通信模块将用户同意的信息返回给手机A的DM，手机A可以提示用户主动扫描对端(手机B)显示的二维码(二维码图片)。
另外，若用户不同意(例如，若用户点击不同意按钮814)，手机B的DM可以通过通信模块将用户不同意的信息返回给手机A的DM，手机A可以显示如图5E中的(c)所示的提示信息，迁移失败。
应该理解的是，在手机A与手机B进行设备级认证时，步骤916和步骤917可以是可选的。例如，若手机A与手机B登录了同一个账号，或者设置了亲情号码等服务，手机B可以不向用户请求是否同意迁移，直接执行步骤918A及其后续的必要步骤。
步骤916和步骤917是手机B提示用户是否同意迁移的一种实现方式，手机B还可以通过其他方式提示用户，例如通过后台系统通知消息通知，本申请不做限定。
918A、手机B的DM判断手机B是否建立过与手机A的直播应用相关的群组。
手机B的DM可以从手机B的HiChain中查询手机B是否建立过与手机A相关的私有群组。相关描述可以参考步骤718A，在此不做赘述。
918B、如果手机B未建立过与手机A的直播应用相关的群组，手机B的DM向手机B的安全管理模块请求创建群组。
手机B的安全模块可以创建一个关于手机A的直播应用的群组(该群组的群组成员可以包括手机A的直播应用和手机B的直播应用)。进一步可以设置群组属性为私有，即特定应用(直播应用)才适用。
可选的，手机B可以将其创建的关于手机A的直播应用的群组的群组ID发送给手机A。手机A可以根据群组ID加入手机B创建的群组。可选的，手机B还可以将手机B的设备ID发送给手机A。手机B的设备ID可以用于手机A与手机B进行通信时使用，手机B的设备ID可以包括网络ID(netId)和设备IP(deviceIP)。
918C、手机B的安全管理模块向手机B的DM发送群组创建成功通知。
应该理解的是，步骤918B和步骤918C是一种示意的创建群组的方式，本申请不限定其他创建群组的方式，例如，手机B的DM可以直接创建群组。
919、手机B的DM向手机B的鸿蒙标签管理模块请求标签。
手机B的鸿蒙标签管理模块可以生成标签，标签中包括认证校验信息，认证校验信息可以包括从手机A接收的token以及手机B的会话标识等信息。手机B的会话标识中包括手机B的设备连接信息。例如，手机B的会话标识包括手机B的Wi-Fi地址(例如，IP地址和端口(Port)号)或者蓝牙地址。认证校验信息还可以包括群组对应的PIN。
920、手机B的鸿蒙标签管理模块向手机B的二维码识别模块请求认证校验信息的二维码图片。
手机B的二维码识别模块可以根据认证校验信息组装二维码图片。
921、手机B的二维码识别模块向手机B的鸿蒙标签管理模块返回二维码图片。
922、手机B的鸿蒙标签管理模块向手机B的DM返回二维码图片。
923a、可选的，手机B的DM向手机B的通信模块发送二维码图片。
在一种可能的设计中，手机B的DM可以将手机B的二维码图片发送给手机A，以便手机A对该二维码图片进行内部扫描，即在步骤923a之后，可以执行步骤923b-步骤925。在另一种可能的设计中，手机B可以将手机B的二维码图片显示在手机B的显示界面(如图8D所示的显示界面)，以便手机A直接扫描，从而使得手机A中的二维码识别模块可以直接获取手机B生成的二维码图片，从而跳过步骤923b-步骤925。上述两种设计均可以实现本方案的技术效果，本申请不对此进行限定。
923b、可选的，手机B的通信模块向手机A的通信模块发送二维码图片。
手机A的DM可以拉起二维码识别模块，通过二维码识别模块扫描手机B生成的二维码图片。
如图9C所示，上述方法还包括：
924、可选的，手机A的通信模块向手机A的DM发送二维码图片。
925、可选的，手机A的DM向手机A的二维码识别模块发送二维码图片。
926、手机A的二维码识别模块扫描二维码，将识别到的信息发送给手机A的鸿蒙标签管理模块。
927、手机A的鸿蒙标签管理模块解析二维码识别模块发送的信息，得到解析结果。
其中，解析结果可以包括手机B的token、PIN和手机B的会话标识等信息。
928、手机A的鸿蒙标签管理模块向手机A的DM发送解析结果。
可以理解的是，步骤924-步骤928是手机A处理二维码图片的一种示意的实现方式，手机A还可以通过其他方式处理二维码图片，本申请不做限定。例如，手机A的DM可以集成二维码图片处理功能，这样手机A的DM可以直接扫描和解析二维码图，以得到token、PIN和手机B的会话标识等信息。
929、手机A的DM校验token。
若从手机B接收到的token与认证请求消息中携带的token相同，执行步骤930。
930、手机A的DM回调认证成功。
应该理解的是，在手机A与手机B进行设备级认证时，步骤929和步骤930是可选的。若执行步骤929和步骤930，即若手机A的DM校验token，可以更好地保证手机A和手机B通信的安全性。
931、手机A的直播应用加入手机B创建的私有群组。
手机A的DM根据会话标识索引本端保存的对端设备(即手机B)的Wi-Fi地址或者蓝牙地址，向手机A的安全模块申请加入手机B创建的私有群组。
手机A的安全模块利用Wi-Fi地址或蓝牙地址创建底层通信通道，并向手机B发送加入群组请求，该加入群组请求中包括解析得到的PIN和群组ID。手机B接收到加入群组请求，校验PIN，认证通过(即该PIN与二维码图片中的PIN相同)后，两个设备中的直播应用加入同一个群组(该群组的群组成员可以包括手机A的直播应用和手机B的直播应用，该群组的属性为私有)，完成认证。
在一种可能的实现方式中，当手机B接收到加入群组请求并认证通过后，会向手机A发送一个响应消息，该响应消息指示手机A的直播应用已加入手机B创建的私有群组。
932、手机A的安全管理模块通知直播应用认证成功。
这样，手机A的直播应用和手机B的直播应用之间完成了应用级认证，手机A和手机B间的直播应用可以实现互通。
933、手机A的直播应用请求手机A的DEF迁移FA1。
其中，FA1可以实现直播应用中的全部或者部分功能，它由一个多个用户界面组成。
934、手机A的DEF向手机B的DMS发送FA1的业务信息。
FA1的业务信息可以包括直播的视频流、音频流、弹幕信息等。
935、手机B的DMS请求手机B的DEF接续FA1。
其中，手机B的DEF接续FA1是指手机B根据接收到的业务信息处理FA1并显示。其中，手机B上的FA1的显示内容可以与手机A上的FA1的显示内容保持同步，也可以与手机A上FA1的显示内容存在着格式或者部分内容上的差异，本申请不对此进行限定。
936、手机B的DEF拉起展示FA1。
其中，手机B的DEF拉起FA1是指手机B运行和显示FA1。
若手机B当前处于直播画面(即运行FA2)，手机B的DEF可以对手机B的FA2进行检测，若FA2具有展示FA1的能力(即FA2支持展示多个FA)，DEF可以在FA2上拉起展示直播FA1，即将FA1界面展示在FA2界面上。例如，如图8E所示，手机B可以在直播界面811上显示手机A发送的直播界面819。这样，用户可以在手机B上同时观看到手机B的直播画面和手机A的直播画面，达到跨设备展示一个或多个FA的体验，省去用户来回切换终端的繁琐，简化了用户操作，可以提高用户体验。
若手机B当前处于直播画面(即运行FA2)，但FA2不具有展示FA1的能力，则FA1迁移失败，但是手机A还可以继续分享直播应用的其他FA(例如，直播购物车FA3)，无需再次建立连接。
若手机B当前处于桌面界面，则可以在桌面上预览、控制手机A的FA1。
应该理解的是，如果存在手机C迁移手机C上的FA(例如，FA4)给手机B，且手机B当前处于FA2显示界面，若FA2具有展示多个FA的能力，手机B可以同时展示3个FA(FA1、FA2和FA3)，依次类推。
本申请实施例主要应用于跨设备在直播应用之间分享FA的场景，即通过多设备的FA分享，使得某一个设备可以同时展示多个FA的场景，这样，可以自由进行双视角双画面直播，可用于测评直播(开箱特写+主播)、运动导播(运动员视角+解说)，教育直播(书本特写+老师)，电商直播(商品细节+秀导)等场景，能够提升用户使用体验和产品竞争力。
在一些实施例中，若手机A和手机B中的一个登录了账号(例如，华为账号)，另一个没有登录账号，手机A和手机B可以执行上述步骤901-步骤936。以便在手机A和手机B之间进行FA迁移时进行验证(即进行设备级认证)，以保证设备间的数据(例如，FA1)的安全。
在一些实施例中，若手机A和手机B都没有登录账号(例如，华为账号)，手机A和手机B可以执行上述步骤901-步骤936。以便在手机A和手机B之间进行FA迁移时进行验证，以保证设备间的数据的安全。
在一些实施例中，若手机A和手机B登录了同一个账号(例如，华为账号)，手机A和手机B可以执行上述步骤901-步骤936。以便在手机A和手机B之间进行FA迁移时进行验证，进一步保证设备间的数据的安全。
需要说明的是，上述步骤901-步骤936中的部分步骤可以是可选的，即不是应用级认证方案的必要技术特征。例如，步骤903和步骤904可以是可选的步骤，即可以不查询已认证设备，直接查看周边的设备。又例如，步骤911和步骤913可以是可选的步骤，即可以不发送创建成功通知。又例如，步骤916和步骤917可以是可选的步骤，即可以不经过用户同意，直接迁移。又例如，步骤923b-步骤925可以是可选的步骤，此时手机A可以直接获取手机B生成的二维码图片(例如，通过扫描手机B显示的二维码图片)。
下面结合具体的场景，以拍照应用为例，对本申请实施例提供的应用级认证的UI界面进行介绍。
外出旅游时，一行人需要拍团队照，往往需要找一个路人或通过手表等外设控制拍照按钮来拍照。但是通过找路人或通过手表等外设来拍照的方式因为不清楚拍照时的状况往往很难拍出合适的照片。本申请提供一种方法，基于跨设备FA分享技术技术，在两个设备建立连接，将一个设备(例如，手机A)作为拍照手机，并将远端设备的拍照FA迁移至另一个设备(例如，手机B)，这样，用户可以通过手持手机B观察手机A的拍照画面并控制拍照，有助于用户拍出更满意的照片，可以提高用户体验。
如图10A所示，用户采用手机A拍照时，手机A显示拍照界面1001，拍照界面包括预览框和菜单区域。响应于用户A点击菜单区域的迁移按钮1002的操作，手机A可以将手机A的拍照界面(手机A的拍照界面可以看做一个FA，例如，FA5)发送给手机B，如图10B所示，手机B可以显示手机A的拍照界面，并且手机B可以控制手机A的拍照界面。
下面以拍照应用为例，对本申请实施例提供的方法的具体实现方式进行说明。本申请实施例提供的方法可以应用于两个近场设备，例如手机A和手机B，手机A和手机B为异账号设备。如图11所示，包括：
1101、用户在手机A的拍照应用中点击“迁移”按钮。
示例性的，如图10A所示，用户A可以在拍照界面1001中点击迁移按钮1002。
1102、手机A的拍照应用向手机A的DM发起迁移请求。
迁移请求中携带的信息包括发起端包名(本端拍照应用包名)，接续端包名(对端拍照应用包名)，手机A的名称。
步骤1103-步骤1132可以参考步骤903-步骤932的相关描述，在此不做赘述。其中，步骤903-932中的部分步骤可以是可选的。
1133、手机A的拍照应用请求手机A的DEF迁移FA5。
1134、手机A的DEF向手机B的DMS发送FA5的相关信息。
FA5的相关信息可以包括拍摄预览画面和拍摄界面的菜单栏信息。
1135、手机B的DMS请求手机B的DEF接续FA5。
手机B的DEF接续FA5是指手机B根据接收到的业务信息处理FA5并显示。
1136、手机B的DEF拉起展示FA5。
如图10B所示，手机B可以显示并控制手机A的拍照界面(FA5)。本申请实施例通过跨设备FA分享技术使得两个设备建立连接，将手机A的FA5分享至手机B上，使得在手机B上可以预览拍摄界面，还可以控制手机A的拍照功能，有助于用户拍出更满意的照片，可以提高用户体验。
下面结合具体的场景，以K歌应用为例，对本申请实施例提供的应用级认证的UI界面进行介绍。
随着互联网的迅速发展，移动式的K歌越来越受到用户的欢迎。例如，用户打开K歌应用授权登录后，可以创建对应的歌房，并可通过分享歌房链接或者邀请码的方式邀请其他用户进入歌房，其他用户可以通过直接点击链接或者输入邀请码进入同一歌房，进行点歌、演唱等操作。但是，上述分享过程存在较多问题：1)面对面地向朋友分享本端创建的歌房，需要通过
Figure PCTCN2022083386-appb-000001
等转发链接，分享步骤较多；2)对端用户收到歌房链接并点击进入歌房时，若对端设备未安装K歌应用，需要跳转应用市场进行K歌应用的安装，之后重新点击链接进入歌房，用户体验不佳；3)歌房的分享以及进入强依赖设备上
Figure PCTCN2022083386-appb-000002
K歌等应用，无法实现即时使用近场体验更佳的设备(如电视)。
本申请针对K歌场景，提供了一种基于FA共享的多设备协同控制方案，支持同网络(例如，同一个Wi-Fi网络)下跨设备应用级互助分享。例如，可以将本机(例如，手机A)的K歌服务无缝流转至或其他终端设备(例如，电视、音箱)；同时无需用户账号授权登录，也不要求多个终端设备使用同一个系统。这样，可以发挥电视、音箱等设备的影音播放体验优势，发挥手机等设备交互便捷、拾音方便的优势，操作步骤简单快捷，极大地提升用户体验。
如图12A中的(a)所示，用户在手机A打开K歌应用后，手机A可以显示K歌界面1201，响应于用户点击歌曲“红豆”对应的K歌按钮1202的操作，如图12A中的 (b)所示，手机A可以显示红豆的K歌界面1203，响应于用户点击迁移按钮1204(迁移按钮1204用于将手机A的K歌界面迁移(发送)至其他设备(例如，手机B))的操作，如图12B中的(a)所示，手机可以弹出弹框1205，弹框1205中可以包括附近的设备，附近的设备包括已认证设备(卧室电视，monica’s Mate pad等)和未认证设备(房间电视，Brian’s Mate pad和Mate book X pro等)。响应于用户点击房间电视(未认证过的设备)对应的控件1206的操作，手机A可以向手机B发送认证请求消息。并且，如图12B中的(b)所示，在房间电视的下方可以显示提示信息1207“等待对端确认”。如图12C所示，电视可以显示弹框1210，弹框1210中包括提示信息“HUAWEI MATE30(手机A)请求将K歌服务迁移到本机，是否同意”，弹框1210中还可以包括不同意按钮1212和同意按钮1213。响应于用户点击同意按钮1213的操作，如图12D所示，电视可以显示弹框1214，弹框1214中可以包括电视生成的二维码图片，还可以包括提示信息1215“扫一扫认证，允许HUAWEI MATE30扫一扫认证”。此时手机A的用户可以扫一扫电视展示的二维码图片，而后，电视可以从手机A接收K歌界面(K歌界面可以视为一个FA，例如FA6)，如图12E所示，电视可以展示K歌界面1217。或者，响应于用户点击同意按钮815的操作，电视可以从手机A接收K歌界面(FA6)，如图12E所示，电视可以展示K歌界面1217。进一步的，如图12F所示，手机A可以重新编排UI，作为点歌控制台，用户在手机A上进行点歌、切歌等操作以及歌单信息会通过通信数据通道同步发送给电视，可以控制电视侧音乐的播放。
下面以K歌应用为例，对本申请实施例提供的方法的具体实现方式进行说明。本申请实施例提供的方法可以应用于处于同一网络下的两个近场设备，例如手机A和电视，手机A可以为安卓系统或双框架系统，电视可以为鸿蒙系统，手机A和电视为异账号设备。如图13所示，包括：
1301、用户在手机A的K歌应用中点击“迁移”按钮。
1302、手机A的K歌应用向手机A的DM发起迁移请求。
迁移请求中携带的信息包括发起端包名(本端K歌应用包名)，接续端包名(对端K歌应用包名)，手机A的名称。
步骤1303-步骤1332可以参考步骤903-步骤932的相关描述，在此不做赘述。其中，步骤903-932中的部分步骤可以是可选的。
1333、手机A的K歌应用请求手机A的DEF迁移FA6。
1334、手机A的DEF向电视的DMS发送FA6的相关信息。
FA6的相关信息可以包括K歌的歌曲信息，歌曲信息包括歌名(例如，红豆)、歌词、音频信息和视频信息中的至少一种。
1335、电视的DMS请求电视的DEF接续FA6。
1336、电视的DEF拉起展示FA6。
若电视安装K歌应用，电视的DEF可以电视的K歌应用和账号是否登录进行检测，提示用户登录K歌应用，以便K歌应用展示手机A发送的FA6。
若电视未安装K歌应用，电视的DEF可以拉起FA6，即提供展示FA6的能力，无需预装K歌应用，可以达到即时使用K歌服务的效果。
本申请实施例针对K歌娱乐场景提供了一种近场应用层数据共享业务，可实现跨设备跨操作系统间FA的一键迁移，不需要依赖任何三方平台，不要求预装K歌应用，可以即时使用K歌服务，快速打造移动式K歌房，能够提升用户体验，操作简单，提升娱乐体验。
下面结合具体的场景，以购物应用为例，对本申请实施例提供的应用级认证的UI界面进行介绍。
随着互联网的迅速发展，尤其是移动互联网的普及，网络购物已经成为大部分人日常生活必不可少的元素。手机、平板作为网络购物中最常用的终端设备，如果能在用户的购物体验方面有较好的提升，无疑会大大增强终端设备的市场竞争力。以使用手机购物为例，在各种购物节中，商家会推出很多满减的优惠活动，用户为了追求更实惠的价格，往往会找身边的朋友、家人一起拼单来购买某些商品，从而达到商家的满减额度。在这个过程中，存在以下几个痛点：1)面对面地向朋友分享某件商品，也需要通过微信来转发，分享步骤较多；2)为了参加优惠，用户会在商品选购界面和购物车之间频繁切换，操作琐碎繁杂；3)当多人一起拼单购买某个商家的商品时，分享商品，添加购物车和切换界面等操作将会更加频繁，完成付款后还需要附带转账操作，极为不便。针对这类问题，部分厂商提出面对面拼单的解决方案，可以通过
Figure PCTCN2022083386-appb-000003
扫码将想要拼单的商品分享给身边的其他用户，实现面对面快捷拼单操作。但是该解决方案存在一些弊端：一方面商家平台和使用场景有着较大的限制，另一方面从用户A付款到分享二维码给用户B，用户B再打开微信扫码，浏览，购买该商品，分享过程依旧依赖微信平台，步骤较多。
本申请针对网络购物场景，提供了一种基于近场FA共享的应用层数据共享业务，支持同网络(例如，同一个Wi-Fi网络)下多个终端设备之间一键同步购物车信息，可以将一个终端设备的购物车(购物车可以视为一个FA，例如，FA7)迁移到另一个终端设备中，两个设备的购物车的商品可以统一结算享受满减优惠，再分开付款省去相互转账的烦恼，操作步骤简单快捷，可以极大地提升拼单购物的用户体验。同时由于近场FA共享能力是系统服务提供的基础能力，不需要同操作系统，也不需要登录同一个设备账号(例如，华为账号)，甚至不需要设备上安装购物应用，通用性高，能被各个电商平台所使用，且适配成本小，能让更多的用户享受到更加便捷的网络购物体验。
示例性的，如图14A所示，用户在手机A打开购物应用后，可以进入购物车界面1401，响应于用户在购物车界面1401点击迁移按钮1402(迁移按钮1402用于将手机A的购物车迁移(发送)至其他设备(例如，手机B))的操作，如图14B中的(a)所示，手机可以弹出弹框1403，弹框1403中可以包括附近的设备，附近的设备包括已认证设备(卧室电视，monica’s Mate pad等)和未认证设备(房间电视，HUAWEI P20和Mate book X pro等)。响应于用户点击HUAWEI P20(未认证过的设备)对应的控件1404的操作，手机A可以向手机B发送认证请求消息。并且，如图14B中的(b)所示，在HUAWEI P20的下方可以显示提示信息1405“等待对端确认”。如图14C所示，若手机B(HUAWEI P20)在显示桌面时接收到手机A发送的认证请求消息，手机B可以显示弹框1410，弹框1410中包括提示信息“HUAWEI MATE30(手机A) 请求将购物车迁移至本机，是否同意”，弹框1410可以包括不同意按钮1412和同意按钮1413。响应于用户点击同意按钮1413的操作，如图14D所示，手机B可以显示弹框1415，弹框1415中可以包括手机B生成的二维码图片，还可以包括提示信息1416“扫一扫绑定，允许HUAWEI MATE30扫一扫认证”。此时手机A的用户可以扫一扫手机B展示的二维码图片，而后，手机B可以从手机A接收购物车(FA6)，或者，响应于用户点击同意按钮1413的操作，手机B可以从手机A接收购物车(FA6)。如图14E所示，手机B可以在购物车界面1417显示共享购物车，共享购物车中既包括“我”添加的商品，也包括用户A(手机A的用户)添加的商品。另外，手机B也可以将自身的购物车(例如，FA7)迁移至手机A，这样，如图14F所示，手机A可以在购物车界面1407显示共享购物车，共享购物车中既包括“我”添加的商品，也包括用户B(手机B的用户)添加的商品。这样，用户可以一键实现拼单购物，不需要依赖任何三方平台分享，省去了相互分享商品，相互转账的繁冗步骤，大大提升购物体验。
下面以购物应用为例，对本申请实施例提供的方法的具体实现方式进行说明。本申请实施例提供的方法可以应用于两个近场设备，例如手机A和手机B，手机A和手机B为异账号设备。如图15所示，包括：
1501、用户在手机A的购物应用中点击“迁移”按钮。
如图14A所示，用户在手机A打开购物应用后，选择商品添加至购物车，然后进入购物车界面1401，用户可以在购物车界面1401点击迁移按钮1402，迁移按钮1402用于将手机A的购物车迁移(发送)至其他设备(例如，手机B)。
1502、购物应用向手机A的DM发起迁移请求(分享请求)。
迁移请求中携带的信息包括发起端包名(本端购物应用包名)，接续端包名(对端购物应用包名)，手机A的名称。发起端包名例如com.huawei.vmall，接续端包名例如com.huawei.vmall。
步骤1503-步骤1532可以参考步骤903-步骤932的相关描述，在此不做赘述。其中，步骤903-932中的部分步骤可以是可选的。
1533、手机A的购物应用请求手机A的DEF迁移FA7。
1534、手机A的DEF向手机B的DMS发送FA7的相关信息。
FA7的相关信息包括购物车中的商品信息，商品信息包括商品名、商品链接和商品价格等信息中的至少一种。
1535、手机B的DMS请求手机B的DEF接续FA7。
1536、手机B的DEF拉起展示FA7。
手机B的DEF拉起FA7，如图14E所示，手机B可以在购物车界面1417显示共享购物车，其中既包含了自己购物车中的一件商品，也包含了用户A选择的三件商品。此时用户B可以直观地看到拼单购买的所有商品，选中购物车的部分或全部商品后，用户可以查看金额是否满足满减活动，实现了快捷的拼单功能。
另外，共享购物车中的商品信息可以实时更新，例如发起迁移的设备(例如，手机A)购物车中有新增商品，目的设备(例如，手机B)的共享购物车也可以即使刷新。
进一步的，用户B点击“结算”按钮时，手机B可以向用户A发起付款请求并携带 付款相关信息，付款相关信息可以包括收款平台和付款金额等。其中，付款金额可以为：各自购买的商品总额－(各自总额/共享购物车总金额)*优惠值。待付款完成后，共享购物车清空，一次拼单购物流程结束。
基于本申请实施例提供的方法，可以将一个终端设备的购物车(购物车可以视为一个FA，例如，FA7)迁移到另一个终端设备中，两个设备的购物车的商品可以统一结算享受满减优惠，再分开付款省去相互转账的烦恼，操作步骤简单快捷，可以极大地提升拼单购物的用户体验。
在又一些实施例中，在家庭环境下，一名用户持有一部手机以及一部电视，正在参与购物节满400减100的活动。传统的购物场景下，该用户在用手机挑选商品的过程中会频繁地切换商品详情页面与购物车页面，以查看或修改购物车内容。基于本申请实施例提供的方法，用户可以将购物车迁移到电视上，在手机上浏览和选择商品，在电视上可以随时观看购物车的内容，省去了手机反复切换页面的繁杂操作，可以提高用户体验。
在又一些实施例中，用户在两个手机(手机A和手机C)上分别选中了一些商品加入了购物车，用户可以同时把手机A和手机C的购物车都迁移到电视B上。当手机A和手机C分别与电视B认证完成后，手机A上的群组成员可以包括(A的购物应用，B的购物应用)；手机C上的群组成员可以包括(C的购物应用，B的购物应用)；电视B上的群组成员包括(A的购物应用，B的购物应用和C的购物应用)，电视的群组包括三个成员。即电视的购物应用分别与手机A的购物应用和手机C的购物应用进行了应用级认证，后续可以分别与手机A和手机C的购物应用进行互通。
应该理解的是，基于近场FA共享能力来实现的购物车FA迁移场景，其主要适用于组网环境下，如家庭环境和工作环境。对于不能近场组网(短距组网)的场景，该方案也有借鉴价值，例如可以利用互联网实现购物车内容的共享和实时同步。或者，电商平台可以将互联网环境下的购物车集成到自己的购物应用中，通过自身的云服务和账号来实现共享。
下面结合具体的场景，以邮件应用为例，对本申请实施例提供的应用级认证的UI界面进行介绍。
当前，办公软件如邮箱的使用场景正在发生一些变化，除了传统的办公室和家庭场景外，外地出差/交通工具/等候/户外走动都成为了办公人员的使用场景。已有厂商在各个移动平台上提供邮箱客户端，使得用户在多种设备上都能访问邮箱，但是当用户在移动办公与非移动办公状态切换时，无法无缝切换，操作不能连续进行，用户体验不好。例如，在智能手表上收到邮件通知时，想要在手机或者Pad上回复时，还需要打开手机/Pad，登录邮箱，查找到邮件，然后回复，操作繁琐，用户体验较差。目前，苹果公司提出的接力(handoff)技术可以让用户从一台苹果设备(例如，Mac、iPhone、iPad或Apple Watch等)切换到附近另一台苹果设备上继续工作，任务进程不丢失。但这要求邮箱接力的设备必须登录同一个AppleId，提前安装相同的邮箱客户端，且登录邮箱账号；并且该技术无法针对推送设备进行选择，比如在会议室需要将某一封邮件推送到电视上展示，由于两个设备未登录同一个AppleId，接力无法实现。
本申请针对商务人员移动办公和非移动办公切换场景，提供了一种基于近场跨设 备FA迁移的应用接续业务，支持多个终端设备之间一键迁移邮件。例如，手表可以一键拉起手机侧邮件查看界面，在手机侧一步直达邮件正文。又例如，对于手机侧正在编辑的邮件草稿，本申请同样支持一键将其无缝转移到其他设备(例如，其他手机、PAD或电视)中继续进行，提供极致的多设备邮件协同体验。本申请不需要同系统，也不要求设备登录同一个账号，甚至不需要两端设备都安装邮箱应用，适用范围广。
示例性的，用户在手机A收到一封邮件并打开后，如图16A所示，手机A可以显示邮件界面1601(邮件界面1601可以视为一个FA，例如，FA8)，响应于用户在邮件界面1601点击迁移按钮1602(迁移按钮用于将手机A的邮件界面迁移(发送)至其他设备(例如，电视))的操作，如图16B中的(a)所示，手机A可以弹出弹框1603，弹框1603中可以包括附近的设备，附近的设备包括已认证设备(monica’s Mate pad等)和未认证设备(电视，HUAWEI P20和Mate book X pro等)。响应于用户点击电视(未认证过的设备)对应的控件1604的操作，手机A可以向电视发送认证请求消息。并且，如图16B中的(b)所示，在电视的下方可以显示提示信息1605“等待对端确认”。如图16C所示，电视可以显示弹框1610，弹框1610中包括提示信息“HUAWEI MATE30(手机A)请求将邮件迁移到本机，是否同意”，弹框1610中还可以包括不同意按钮1614和同意按钮1615。响应于用户点击同意按钮1613的操作，如图16D所示，电视可以显示弹框1614，弹框1614中可以包括电视生成的二维码图片，还可以包括提示信息1615“扫一扫认证，允许HUAWEI MATE30扫一扫认证”。此时手机A的用户可以扫一扫电视展示的二维码图片，而后，电视可以从手机A接收邮件界面(FA8)，如图16E所示，电视可以显示邮件界面1616。或者，响应于用户点击同意按钮1613的操作，电视可以从手机A接收邮件界面(FA8)，如图16E所示，电视可以显示邮件界面1616。
下面以邮件应用为例，对本申请实施例提供的方法的具体实现方式进行说明。本申请实施例提供的方法可以应用于两个近场设备，例如手机A和PC，手机A可以是安卓系统，PC可以是鸿蒙系统，手机A和PC为异账号设备。如图17A所示，包括：
1701、用户在手机A的邮件应用中点击“迁移”按钮。
用户在手机上打开一封邮件编辑，点击编辑界面的“迁移”按钮。
1702、手机A的邮件应用向手机A的DM发起迁移请求。
迁移请求中携带的信息包括发起端包名(本端邮件应用包名)，接续端包名(对端邮件应用包名)，手机A的名称。
步骤1703-步骤1732可以参考步骤903-步骤932的相关描述，在此不做赘述。其中，步骤903-932中的部分步骤可以是可选的。
1733、手机A的邮件应用请求手机A的DEF迁移FA8。
邮件应用可以携带本设备和目标设备参数(例如，本设备和目标设备的标识)向手机A的DEF请求接续FA8。
1734、手机A的DEF向电视的DMS发送FA8的相关信息。
FA8的相关信息可以包括邮件内容信息，邮件内容信息可以包括主题，正文，附件等信息。
1735、电视的DMS请求电视的DEF接续业务。
1736、电视的DEF拉起展示FA8。
若电视安装有邮箱客户端，电视的DEF可以对邮箱客户端和账号是否登录进行检测，提示用户登录邮箱账号，从而邮箱应用可以拉起展示FA8，即显示手机A迁移过来的邮件界面。
若电视未安装邮箱客户端，电视的DEF可以拉起展示FA8，即将FA8进行编码重排显示，这样未登录/未安装邮箱客户端的设备也可以展示邮件内容，且可以避免邮箱账号等隐私信息泄露。另外，若电视的DEF不支持展示FA8，可以从应用市场下载安装能够展示FA8的FA(该FA可以是第三方应用厂商开发的)。
进一步的，用户可以在电视上对邮件进行编辑、回复等操作，编辑、回复的邮件内容可以通过数据通信通道回传到手机A，并依据手机A的账号信息将邮件发送出去。这样，即使电视未安装邮箱客户端，或者未登录邮箱账号，也可实现一键迁移，提升用户体验，提高办公效率。迁移设备可以只作为展示和编辑使用，最终邮件收发均由迁移发起端执行，迁移的设备只能查看发起端主动推送的邮件，流程结束后内容主动销毁，做到真正的邮件随人走，无缝切换。
本申请可以使邮件在多设备间流转，不要求登录同一设备账号，也不要求所有设备都安装邮箱客户端和登录邮箱账号，大大拓宽可用设备范围。
另外，若两个设备间已完成组网和认证，直接点击迁移按钮即可完成迁移，更加方便快捷。例如，假设手表、手机和PC之间已完成组网和认证，如图17B所示，用户的手表接收邮件通知后，可以显示邮件通知界面1701，提示用户有一封信邮件，响应于用户点击查看按钮1702的操作，如图17C所示，手表可以直接拉起手机侧邮件查看界面1704(手表可以向手机发送邮件查看请求，手机可以直接显示邮件查看界面1704)，一步直达邮件正文。用户在手机上编辑回复邮件的过程中，如果需要插入一份文档，但是文档保存在PC中，用户可以在手机上点击迁移按钮1705将邮件迁移到PC，如图17D所示，PC可以显示邮件编辑界面1706，用户在邮件编辑界面1706插入附件后可以点击迁移按钮1707将携带附件的邮件重新迁移到手机。这样，手表、手机和PC之间可以方便快捷地协同工作，用户体验较高。
本申请基于近场跨设备FA迁移技术，实现邮件在移动办公和非移动办公间一键迁移，无缝流转，大大提升多设备协同办公体验。多设备迁移邮件脱离用户账号/邮箱客户端/邮箱账号的限制，可覆盖同一组网下的多种设备，大大拓宽了邮件迁移的使用场景。
上述实施例是以接收方(被动迁移设备，例如手机B，电视等)生成二维码信息，发起方(主动迁移设备，例如手机A)解析手机B的二维码信息加入手机B创建的群组进行认证的。
在另一些实施例中，也可以由发起方(主动迁移设备，例如手机A)生成二维码信息，接收方(被动迁移设备，例如手机B，电视等)根据手机A的二维码信息进行认证。
示例性的，如图18A所示，用户A可以在电视的K歌界面1800选中迁移选项1801(迁移选项1801用于将电视的K歌界面迁移(发送)至其他设备(例如，手机B))。可选的，用户A可以采用控制设备(例如，遥控器，手机等)选中“迁移”选项。或者， 若电视是触控设备，用户A可以直接点击“迁移”选项以选中“迁移”选项。如图18B所示，电视可以弹出弹框1802，弹框1802中可以包括电视生成的二维码图片，还可以包括提示信息1803“扫一扫认证，允许其他设备扫一扫加入我的歌房”。用户B可以采用手机B扫描电视显示的二维码图片(手机B可以采用第三方应用(例如，K歌应用等)提供的扫描入口，或者可以采用系统自带的扫描入口)，之后，如图18C中的(a)所示，手机B可以显示K歌界面1804，用户A的头像1805(电视登录的K歌应用的账号的头像，或者电视登录的设备账号(例如华为账号)的头像)可以显示在歌词底层，表示当前用户A正在演唱歌曲。响应于用户点击点歌按钮1806的操作，如图18C中的(b)所示，手机B可以显示弹框1807，响应于用户点击合唱按钮1808的操作，如图18D所示，用户A的头像1811(电视登录的K歌应用的账号的头像，或者电视登录的设备账号(例如华为账号)的头像)和用户B的头像1810(手机B登录的K歌应用的账号的头像，或者手机B登录的设备账号(例如，华为账号)的头像)，表示用户B与用户A合唱同一首歌曲。
下面以K歌应用为例，对本申请实施例提供的应用级认证方法的具体实现方式进行说明。本申请实施例提供的方法可以应用于两个近场设备，例如电视和手机B，电视和手机B为异账号设备(例如，不是同一个华为账号)，且电视和手机B都打开了K歌应用。如图19所示，包括：
1901、用户在电视上的K歌界面选中“迁移”选项。
例如，如图18A所示，用户可以在电视的K歌界面选中迁移选项1801。(迁移选项1801用于将手机A的一系列K歌界面(例如，该一系列K歌界面可以看做FA9)迁移(发送)至其他设备(例如，手机B))。其中，迁移选项也可以称为分享选项、发送选项等，本申请不做限定。
可选的，用户可以采用控制设备(例如，遥控器，手机等)选中“迁移”选项。或者，若电视是触控设备，用户可以直接点击“迁移”选项以选中“迁移”选项。
可选的，用户可以在选中迁移选项1801后进一步选择待迁移的设备，例如可以选中手机B。
1902、电视的二维码识别模块向电视的鸿蒙标签管理模块发起生成二维码请求。
示例性的，生成二维码请求的入参包含一个Bundle对象以及一个异步回调。其中，Bundle对象中包含K歌业务所需的源包名(本端K歌应用包名)和目的包名(对端K歌应用包名或者待迁移的FA的包名)。异步回调包含创建二维码的结果，创建成功可以获取二维码字段，创建失败获取错误码。
1903、电视的鸿蒙标签管理模块向电视的DM请求电视的设备信息。
电视的设备信息可以包括电视的名称、网络ID(netId)和设备IP(deviceIP)等。
Bundle对象将鸿蒙标签管理模块获取的设备信息保存到设备管理，用于创建群组及后续通过通道将客户端应用包名等信息传到对端设备。
1904、电视的DM生成PIN。
电视的DM可以生成随机的PIN。PIN可以是若干位随机数字。可选的，电视的DM还可以生成token，token可以是若干位随机字符串。
1905、可选的，电视的DM调用安全管理模块获取本机设备连接参数。
其中，本机设备连接参数可以包括本机的网络ID(netId)，设备IP(deviceIP)，蓝牙地址(BtMac)，Wi-Fi地址(Wi-FiPort)。其中，netId在本地保存。
1906a、电视的DM调用安全管理模块创建群组。
其中，创建的群组可以是(本机名称(即电视，例如HUAWEI TV)，本机的K歌应用的包名，(对端设备名称可以空缺)，对端K歌应用的包名/待迁移的FA的包名)，该群组当前缺少至少一个成员，允许其他设备作为成员加入。
1906b、可选的，安全管理模块创建群组成功后，向电视的DM发送回调通知。
1907、电视的DM接收到回调通知后，向鸿蒙标签管理模块发送PIN、token和电视的设备信息。
电视的DM在本地保存群组名(groupName)，并将PIN、token和电视的设备信息打包为Bundle类型，通过设备管理回调将其传递给鸿蒙标签管理模块。
1908a、鸿蒙标签管理模块根据PIN、token和电视的设备信息生成二维码图片。
1908b、鸿蒙标签管理模块将二维码信息发送给二维码识别模块。
1908c、二维码识别模块根据二维码信息生成二维码图片并显示该二维码图片。
其中，二维码识别模块可以调用电视的显示功能，从而在电视的显示屏上显示二维码图片。
1909a、手机B打开二维码识别模块扫描电视显示的二维码图片。
1909b、手机B的二维码识别模块识别二维码图片中的二维码信息(也可以称为二维码标签)，拉起鸿蒙标签管理模块并传入二维码信息。
1909c、鸿蒙标签管理模块解析二维码信息，提取二维码信息中存储的字段(字符串)。
1910、手机B的鸿蒙标签管理模块向手机B的DM发送认证请求消息，并注册回调。
认证请求消息包括从二维码信息中解析出的字段。
1911a、手机B的DM对认证请求消息进行处理。
手机B的DM可以对认证请求消息中包括的字段进行拆分，得到deviceIp和Wi-FiPort字段，根据deviceIp和Wi-FiPort调用通信模块接口创建手机B和电视之间的通信通道。
1911b、可选的，手机B的DM通过通信模块向电视的DM发送认证请求消息。
手机B的DM可以将token设置为参数requestId。可以理解的是，手机B的DM还可以通过通信模块向电视的DM发送手机B的设备ID等信息。
1912、可选的，电视的DM校验token。
电视的DM基于参数requestId提取token，将提取的token和本端保存的token进行比较，如果一致则同意两台设备(即电视和手机B)之间创建安全通信通道(安全通信通道例如可以是加密保护的通信通道)，并通过该安全通信通道向手机B发送群组信息，该群组信息包括电视的网络ID，电视创建的群组的群组ID(groupId)、群组类型(groupType)和群组名(groupName)等。
1913、手机B的DM接收并保存电视发送的群组信息。
1914、手机B的DM调用安全管理模块获取与对端设备存在可信关系的所有群组 信息，然后通过安全管理模块遍历查询电视的K歌应用应用是否有群组的访问权限。
如果没有权限，设备管理通过HiChain加入指定群组，群组加入成功会触发两端设备的onFinish回调，在该方法中调用HiChain写入对端的包名信息，用于后续查询应用级可信关系。如果已有权限则执行步骤1915。
1915、手机B的DMS接收来自电视的DEF的FA9的相关信息。
FA9的相关信息可以包括K歌的歌曲信息，歌曲信息包括歌名(例如，红豆)、歌词、音频信息和视频信息中的至少一种。
可选的，手机B上进行点歌、切歌等操作以及歌单信息会通过安全通信通道同步发送给电视，可以控制电视侧音乐的播放。
在一些实施例中，若电视和手机B中的一个登录了账号(例如，华为账号)，另一个没有登录账号，电视和手机B可以执行上述步骤1901-步骤1915。以便在电视和手机B之间进行FA迁移时进行验证(即进行设备级认证)，以保证设备间的数据的安全。
在一些实施例中，若电视和手机B都没有登录账号(例如，华为账号)，电视和手机B可以执行上述步骤1901-步骤1915。以便在电视和手机B之间进行FA迁移时进行验证，以保证设备间的数据的安全。
在一些实施例中，若电视和手机B登录了同一个账号(例如，华为账号)，电视和手机B可以执行上述步骤1901-步骤1915。以便在电视和手机B之间进行FA迁移时进行验证，进一步保证设备间的数据(例如，FA9的相关信息)的安全。
需要说明的是，上述步骤1901-步骤1915中的部分步骤可以是可选的，即不是设备级认证方案的必要技术特征。例如，步骤1905可以是可选的步骤，例如电视的DM可以从其他模块获取本机设备连接参数。又例如，步骤1906b可以是可选的步骤，即安全管理模块创建群组成功后，可以不向电视的DM发送回调通知。又例如，步骤1911b和步骤1912可以是可选的步骤，即手机B的DM可以不向电视的DM发送token，电视的DM也无需校验token。
当然，手机C(手机C的设备账号和手机B的设备账号不同，例如未登录同一个华为账号)也可以通过扫描二维码的方式加入电视创建的群组(具体过程可以参考步骤1809-步骤1818)。这样，多个设备可以基于二维码扫码的方式快速拉起FA9，无需预装，即时使用服务；且多个设备扫码后可以建立信任圈进行信息交互，例如多个设备间歌单等信息能够实时刷新同步，多个设备(例如，手机B或手机C)可以协同控制主席端(例如，电视)，实现多设备协同控制，实现真正的移动式KTV体验。
在又一些实施例中，发起方(主动迁移设备，例如电视)可以生成二维码图片(例如，执行步骤1901-1908c)，一个或多个接收方(被动迁移设备，例如手机B和手机C)可以根据电视的二维码图片进行认证(例如，执行步骤1909a-步骤1914)，通过认证后，接收方可以将购物车、直播间、邮件等迁移至电视，从而达到在多个设备(例如，电视、手机B和手机C)之间共享购物车、直播间、邮件等信息的效果，多个设备间的购物车商品信息、直播视频流、邮件内容等信息能够实时刷新同步，多个设备(例如，电视、手机B和手机C)可以协同控制主席端(例如，电视)，实现多设备协同控制，实现真正的协同购物、直播或邮件编辑体验。
需要说明的是，对于本申请实施例提供的各个UI界面，例如上文中的图5A-图5F、图6A-图6C、图8A-图8D、图10A-图10B、图12A-图12E、图14A-图14F、图16A-图16E、图18A-图18C等，各个UI界面的界面设计仅是一种示意，不限定UI界面中的各个元素(例如，按钮、图标、文字等)的位置、名称和形状等。例如，图8A中的按钮802(原本位于界面801的左上角)也可以位于界面801的右下角，按钮802上显示的文字也可以是共享、转移等。在一些实施例中，不同UI界面的元素可以重新排列组合到同一个UI界面。例如，图5A中的(a)中的按钮502可以替换为图5A中的(b)中的按钮503和按钮504。本申请实施例不限定UI界面之间的跳转关系。例如，若本申请实施例出现从第一UI界面跳转至第二UI界面的描述，仅是第一界面和第二界面的一种跳转关系示意，不限定有其他的跳转关系。例如，如图5C中的(b)所示，响应于用户点击绑定按钮509的操作，如图5D中的(b)所示，手机可以直接显示扫描界面512。本申请实施例也不限定UI界面之间的跳转方式(例如，若本申请实施例出现点击第一UI界面的第一按钮跳转至第二UI的描述，仅是第一界面和第二界面的一种跳转方式示意，不限定有其他的跳转方式)。例如，如图8A所示，响应于用户特定手势(例如，三指下滑、指关节敲击等)的操作，如图8B中的(a)所示，手机可以显示弹框803。
本申请实施例提供一种功能迁移方法，如图20所示，包括：
2001、第一设备向第二设备发送第一请求。
其中，第一请求携带第一设备的标识、第一应用的标识和第二应用的标识。第一请求可以是上述实施例中的认证请求消息，相关描述在此不做赘述。
在一种可能的实施方式中，响应于用户在第一设备的第一应用的第一操作，显示第一弹框，第一弹框包括与第一设备处于同一个网络中的设备的标识；响应于用户在第一弹框中选中第二设备的第二操作，向第二设备发送第一请求。示例性的，这里的第一弹框可以是如图5C中的(b)所示的弹框508或者如图8B中的(a)所示的弹框803等。
其中，与第一设备处于同一个网络中的设备包括可信设备和不可信设备；其中，可信设备包括与第一设备登录同一个账号的设备、与第一设备进行过设备级认证的设备或者与第一设备的第一应用进行过应用级认证的设备；不可信设备包括未与第一设备登录同一个账号的设备、未与第一设备进行过设备级认证的设备或者未与第一设备的第一应用进行过应用级认证的设备。其中，第一设备可以是上述实施例中的手机A。
2002、第二设备接收来自第一设备的第一请求。
第一设备接收第一请求之后，可以显示第一弹框，第一弹框用于提示用户是否同意将第一设备的第一应用加入第一群组；接收来自用户的同意指令。示例性的，这里的第一弹框可以是如图6A中的(a)所示的弹框531，或者可以是如图8C中的(a)所示的弹框812等。
其中，第二设备可以是上述实施例中的手机B。
2003、第二设备创建第一群组，第一群组的成员包括第二设备的第二应用。
第二设备创建第一群组之前，可以根据第一设备的标识确定第二设备当前没有第二群组，其中，第二群组的成员包括第一设备和第二设备。
第二设备创建第一群组之前，可以根据第一设备的标识、第一应用的标识和第二应用的标识，确定第二设备当前没有第三群组，其中，第三群组的成员包括第一设备的第一应用以及第二设备的第二应用。
2004、第二设备向第一设备发送第一响应。
第一响应可以包括第一群组对应的个人识别码PIN和/或第二设备的通信连接信息。
2005、第一设备从第二设备接收第一响应。
第一响应用于指示第二设备创建的第一群组，第一群组的成员包括第二设备的第二应用。
2006、第一设备向第二设备发送第二请求。
第二请求用于申请将第一设备的第一应用加入第一群组。
在一种可能的实现方式中，第二设备可以显示二维码图片，二维码图片包括第一群组对应的个人识别码PIN和/或第二设备的通信连接信息。第一设备可以扫描第二设备显示的二维码图片，获取第一群组对应的个人识别码PIN和/或第二设备的通信连接信息，第一设备可以根据PIN和/或第二设备的通信连接信息向第二设备发送第二请求。
可选的，第一设备根据PIN和/或第二设备的通信连接信息向第二设备发送第二请求。
2007、第二设备接收来自第一设备的第二请求。
第二设备可以根据第二请求将第一设备的第一应用加入第一群组。
可选的，第二设备可以向第一设备发送第二响应，第一设备可以接收第二响应，其中，第二响应用于指示第一设备的第一应用已加入第一群组。
2008、第一设备将第一应用中的第一功能迁移到第二设备的第二应用，第一功能包括一个或者多个UI。
在一种可能的实现方式中，将第一应用中的第一功能迁移到第二设备的第二应用包括：向第二设备发送第一功能的业务信息；当第一应用为直播应用时，第一功能的业务信息包括第一设备的直播间的视频流、音频流以及弹幕信息中的至少一种；或者当第一应用为拍照应用时，第一功能的业务信息包括拍摄预览画面或拍摄界面的菜单栏信息；或者当第一应用为K歌应用时，第一功能的业务信息包括歌名、歌词、歌曲的音频信息歌曲的视频信息、歌曲的控制界面中的至少一种；或者当第一应用为购物应用时，第一功能的业务信息包括购物车中的商品信息；或者当第一应用为邮件应用时，第一功能的业务信息包括邮件的主题、正文和附件中的至少一种。
可选的，第一设备可以创建第二群组，其中，第二群组的成员包括第一设备的第一应用以及第二设备的第二应用。
2009、第二设备接收第一设备迁移的第一应用中的第一功能，其中，第一功能包括一个或者多个UI。
图20的实施例中的第一设备或第二设备可以分别为前述实施例中的手机A和手机B等，图20的实施例中未详述的部分，可以参考前述实施例，在此不做赘述。
本申请实施例提供一种功能迁移方法，如图21所示，包括：
2101、第一设备向第二设备发送第一请求。
第一请求携带第一设备的标识。
2102、第二设备从第一设备接收第一请求。
2103、第二设备向第一设备发送第一响应。
第一响应用于指示第二设备创建的第一群组，第一群组的成员包括第二设备。
2104、第一设备从第二设备接收第一响应。
2105、第一设备向第二设备发送第二请求，第二请求用于申请将第一设备加入第一群组。
2106、第一设备将第一应用中的第一功能迁移至第二设备，第一应用为第一设备中的任一个应用，第一功能包括一个或多个图形用户界面UI。
图21的实施例中的第一设备或第二设备可以分别为前述实施例中的手机A和手机B等，第一请求可以是上述实施例中的认证请求消息等。图21的实施例中未详述的部分，可以参考前述实施例，在此不做赘述。
本申请实施例提供一种功能迁移方法，如图22所示，包括：
2201、第一设备创建第一群组，第一群组的成员包括第一设备的第一应用。
2202、第二设备向第一设备发送第一请求，第一请求用于申请将第二设备的第二应用加入第一设备创建的第一群组，第一群组的成员包括第一设备的第一应用和第二设备的第二应用。
2203、第一设备从第二设备接收第一请求，第一请求用于申请将第二设备的第二应用加入第一群组。
2204、第一设备将第二设备的第二应用加入第一群组。
2205、第一设备将第一应用中的第一功能迁移到第二设备的第二应用，第二功能包括一个或者多个UI。
2206、第二设备从第一设备接收第一应用中的第一功能，其中，第一功能包括一个或者多个UI。
图22的实施例中的第一设备或第二设备可以分别为前述实施例中的手机A和手机B等，第一请求可以是上述实施例中的认证请求消息等。图22的实施例中未详述的部分，可以参考前述实施例，在此不做赘述。
本申请另一些实施例提供了一种第一设备或第二设备，第一设备或第二设备可以是如图3所示的电子设备200。第一设备或第二设备可以包括：通信模块、存储器和一个或多个处理器。该通信模块、存储器与处理器耦合。该存储器用于存储计算机程序代码，该计算机程序代码包括计算机指令。
本申请另一实施例提供一种芯片系统，如图23所示，该芯片系统包括至少一个处理器2301和至少一个接口电路2302。处理器2301和接口电路2302可通过线路互联。例如，接口电路2302可用于从其它装置(例如，电子设备的存储器)接收信号。又例如，接口电路2302可用于向其它装置(例如处理器2301)发送信号。
例如，接口电路2302可读取电子设备中存储器中存储的指令，并将该指令发送给处理器2301。当所述指令被处理器2301执行时，可使得第一设备/第二设备(如图6所示的电子设备230)执行上述各实施例中的各个步骤。
又例如，接口电路2302可读取服务器中存储器中存储的指令，并将该指令发送给 处理器2301。当所述指令被处理器2301执行时，可使得服务器执行上述实施例中的各个步骤。
当然，该芯片系统还可以包含其他分立器件，本申请实施例对此不作具体限定。
通过以上实施方式的描述，所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将装置的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述模块或单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个装置，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是一个物理单元或多个物理单元，即可以位于一个地方，或者也可以分布到多个不同地方。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个可读取存储介质中。基于这样的理解，本申请实施例的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该软件产品存储在一个存储介质中，包括若干指令用以使得一个设备(可以是单片机，芯片等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
以上内容，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何在本申请揭露的技术范围内的变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (19)

  1. 一种功能迁移方法，其特征在于，应用于第一设备，所述方法包括：
    向第二设备发送第一请求，所述第一请求携带所述第一设备的标识、第一应用的标识和第二应用的标识；
    从所述第二设备接收第一响应，所述第一响应用于指示所述第二设备创建的第一群组，所述第一群组的成员包括所述第二设备的所述第二应用；
    向所述第二设备发送第二请求，所述第二请求用于申请将所述第一设备的所述第一应用加入所述第一群组；
    将所述第一应用中的第一功能迁移到所述第二设备的所述第二应用，所述第一功能包括一个或者多个图形用户界面UI。
  2. 根据权利要求1所述的方法，其特征在于，所述第一响应包括所述第一群组对应的个人识别码PIN和/或所述第二设备的通信连接信息；
    所述向所述第二设备发送第二请求，包括：
    根据所述PIN和/或所述第二设备的通信连接信息向所述第二设备发送所述第二请求。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    接收第二响应，其中，所述第二响应用于指示所述第一设备的所述第一应用已加入所述第一群组。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，所述方法还包括：
    创建第二群组，其中，所述第二群组的成员包括所述第一设备的所述第一应用以及所述第二设备的所述第二应用。
  5. 根据权利要求1-4任一项所述的方法，其特征在于，所述方法还包括：
    响应于用户在所述第一设备的第一应用的第一操作，显示第一弹框，所述第一弹框包括与所述第一设备处于同一个网络中的设备的标识；
    所述向第二设备发送第一请求，包括：
    响应于所述用户在所述第一弹框中选中所述第二设备的第二操作，向所述第二设备发送所述第一请求。
  6. 根据权利要求5所述的方法，其特征在于，
    所述与所述第一设备处于同一个网络中的设备包括可信设备和不可信设备；其中，所述可信设备包括与所述第一设备登录同一个账号的设备、与所述第一设备进行过设备级认证的设备或者与所述第一设备的所述第一应用进行过应用级认证的设备；所述不可信设备包括未与所述第一设备登录同一个账号的设备、未与所述第一设备进行过设备级认证的设备或者未与所述第一设备的所述第一应用进行过应用级认证的设备。
  7. 根据权利要求1-6任一项所述的方法，其特征在于，所述方法还包括：
    扫描所述第二设备显示的二维码图片，所述二维码图片包括所述第一群组对应的个人识别码PIN和/或所述第二设备的通信连接信息，
    所述向所述第二设备发送第二请求，包括：
    根据所述PIN和/或所述第二设备的通信连接信息向所述第二设备发送所述第二请求。
  8. 根据权利要求1-7任一项所述的方法，其特征在于，将所述第一应用中的第一功能迁移到所述第二设备的所述第二应用包括：
    向所述第二设备发送所述第一功能的业务信息；
    当所述第一应用为直播应用时，所述第一功能的业务信息包括所述第一设备的直播间的视频流、音频流以及弹幕信息中的至少一种；或者
    当所述第一应用为拍照应用时，所述第一功能的业务信息包括拍摄预览画面或拍摄界面的菜单栏信息；或者
    当所述第一应用为K歌应用时，所述第一功能的业务信息包括歌名、歌词、歌曲的音频信息歌曲的视频信息、歌曲的控制界面中的至少一种；或者
    当所述第一应用为购物应用时，所述第一功能的业务信息包括购物车中的商品信息；或者
    当所述第一应用为邮件应用时，所述第一功能的业务信息包括邮件的主题、正文和附件中的至少一种。
  9. 一种功能迁移方法，其特征在于，应用于第二设备，所述方法包括：
    接收来自第一设备的第一请求，所述第一请求携带所述第一设备的标识、第一应用的标识和第二应用的标识；
    创建第一群组，所述第一群组的成员包括所述第二设备的所述第二应用；
    向所述第一设备发送第一响应，所述第一响应用于指示所述第一群组；
    接收来自所述第一设备的第二请求，所述第二请求用于申请将所述第一设备的所述第一应用加入所述第一群组；
    接收所述第一设备迁移的所述第一应用中的第一功能，其中，所述第一功能包括一个或者多个图形用户界面UI。
  10. 根据权利要求9所述的方法，其特征在于，
    所述第一响应包括所述第一群组对应的个人识别码PIN和/或所述第二设备的通信连接信息。
  11. 根据权利要求9或10所述的方法，其特征在于，所述方法还包括：
    向所述第一设备发送第二响应，其中，所述第二响应用于指示所述第一设备的所述第一应用已加入所述第一群组。
  12. 根据权利要求9-11任一项所述的方法，其特征在于，所述从第一设备接收第一请求之后，所述方法还包括：
    显示第一弹框，所述第一弹框用于提示用户是否同意将所述第一设备的所述第一应用加入所述第一群组；
    接收来自用户的同意指令。
  13. 根据权利要求9-12任一项所述的方法，其特征在于，在所述创建第一群组之前，所述方法还包括：
    根据所述第一设备的标识确定所述第二设备当前没有第二群组，其中，所述第二群组的成员包括所述第一设备和所述第二设备。
  14. 根据权利要求9-13任一项所述的方法，其特征在于，在所述创建第一群组之前，所述方法还包括：
    根据所述第一设备的标识、所述第一应用的标识和所述第二应用的标识，确定所述第二设备当前没有第三群组，其中，所述第三群组的成员包括所述第一设备的所述第一应用以及所述第二设备的所述第二应用。
  15. 根据权利要求9-14任一项所述的方法，其特征在于，所述方法还包括：
    显示二维码图片，所述二维码图片包括所述第一群组对应的个人识别码PIN和/或所述第二设备的通信连接信息。
  16. 根据权利要求9-15任一项所述的方法，其特征在于，所述接收所述第一设备迁移的所述第一应用中的第一功能包括：
    接收来自所述第一设备的所述第一功能的业务信息；
    当所述第一应用为直播应用时，所述第一功能的业务信息包括所述第一设备的直播间的视频流、音频流以及弹幕信息中的至少一种；或者
    当所述第一应用为拍照应用时，所述第一功能的业务信息包括拍摄预览画面或拍摄界面的菜单栏信息；或者
    当所述第一应用为K歌应用时，所述第一功能的业务信息包括歌名、歌词、歌曲的音频信息歌曲的视频信息、歌曲的控制界面中的至少一种；或者
    当所述第一应用为购物应用时，所述第一功能的业务信息包括购物车中的商品信息；或者
    当所述第一应用为邮件应用时，所述第一功能的业务信息包括邮件的主题、正文和附件中的至少一种。
  17. 一种终端，所述终端为第一设备，其特征在于，包括：处理器、近距离无线通信模块、存储器、以及一个或多个程序；其中，所述处理器和所述存储器耦合，所述处理器与所述近距离无线通信模块连接；所述一个或多个程序被存储在所述存储器中，所述一个或多个程序包括指令，所述指令用于执行如权利要求1-8任一项所述的方法。
  18. 一种终端，所述终端为第二设备，其特征在于，包括：处理器、近距离无线通信模块、存储器、以及一个或多个程序；其中，所述处理器和所述存储器耦合，所述处理器与所述近距离无线通信模块连接；所述一个或多个程序被存储在所述存储器中，所述一个或多个程序包括指令，所述指令用于执行如权利要求9-16任一项所述的方法。
  19. 一种计算机可读介质，用于存储一个或多个程序，其中所述一个或多个程序被配置为被所述一个或多个处理器执行，所述一个或多个程序包括指令，所述指令用于执行如权利要求1-8任一项或9-16任一项所述的方法。
PCT/CN2022/083386 2021-03-31 2022-03-28 一种功能迁移方法和装置 WO2022206676A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110352451.1A CN115145474A (zh) 2021-03-31 2021-03-31 一种功能迁移方法和装置
CN202110352451.1 2021-03-31

Publications (1)

Publication Number Publication Date
WO2022206676A1 true WO2022206676A1 (zh) 2022-10-06

Family

ID=83405065

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/083386 WO2022206676A1 (zh) 2021-03-31 2022-03-28 一种功能迁移方法和装置

Country Status (2)

Country Link
CN (1) CN115145474A (zh)
WO (1) WO2022206676A1 (zh)

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120032945A1 (en) * 2008-12-19 2012-02-09 Openpeak Inc. Portable computing device and method of operation of same
CN103092721A (zh) * 2011-10-31 2013-05-08 联想(北京)有限公司 一种应用备份方法、电子设备及系统
CN106572163A (zh) * 2016-11-02 2017-04-19 广东欧珀移动通信有限公司 一种数据迁移的方法及终端
CN107018189A (zh) * 2017-03-31 2017-08-04 青岛海信移动通信技术股份有限公司 迁移应用数据以及接收应用数据的方法及装置
CN109729125A (zh) * 2017-10-30 2019-05-07 华为技术有限公司 会话建立方法、设备及系统
CN109862525A (zh) * 2017-11-30 2019-06-07 华为技术有限公司 一种用户群组的建立方法及装置
CN110336683A (zh) * 2019-07-18 2019-10-15 中国联合网络通信集团有限公司 一种会话迁移的方法及装置
CN112153098A (zh) * 2019-06-28 2020-12-29 华为技术有限公司 一种应用迁移方法及装置

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120032945A1 (en) * 2008-12-19 2012-02-09 Openpeak Inc. Portable computing device and method of operation of same
CN103092721A (zh) * 2011-10-31 2013-05-08 联想(北京)有限公司 一种应用备份方法、电子设备及系统
CN106572163A (zh) * 2016-11-02 2017-04-19 广东欧珀移动通信有限公司 一种数据迁移的方法及终端
CN107018189A (zh) * 2017-03-31 2017-08-04 青岛海信移动通信技术股份有限公司 迁移应用数据以及接收应用数据的方法及装置
CN109729125A (zh) * 2017-10-30 2019-05-07 华为技术有限公司 会话建立方法、设备及系统
CN109862525A (zh) * 2017-11-30 2019-06-07 华为技术有限公司 一种用户群组的建立方法及装置
CN112153098A (zh) * 2019-06-28 2020-12-29 华为技术有限公司 一种应用迁移方法及装置
CN110336683A (zh) * 2019-07-18 2019-10-15 中国联合网络通信集团有限公司 一种会话迁移的方法及装置

Also Published As

Publication number Publication date
CN115145474A (zh) 2022-10-04

Similar Documents

Publication Publication Date Title
EP2624601B1 (en) Short-range radio communication system and method for operating the same
US9900477B2 (en) Terminal device and method for controlling thereof
US9338235B2 (en) Method for providing in-vehicle notification service, machine-readable storage medium, head unit device, and mobile device
CN110917614A (zh) 基于区块链系统的云游戏系统及云游戏的控制方法
CN111045568B (zh) 基于区块链的虚拟物品处理方法、装置、设备及存储介质
US20220321572A1 (en) Meeting Join for Meeting Device
US11909806B2 (en) Systems and methods for establishing highly secure and resilient persistent communication connections
CN111164983A (zh) 互联终端出借本地处理能力
WO2022206770A1 (zh) 一种设备间应用协同工作的方法及设备
US11671556B2 (en) Method of performing video call and display device
WO2022206676A1 (zh) 一种功能迁移方法和装置
WO2022206627A1 (zh) 一种功能迁移方法和装置
WO2022206630A1 (zh) 一种功能迁移方法和装置
CN111694892A (zh) 资源转移方法、装置、终端、服务器及存储介质
CN114979049B (zh) 即时通讯消息的显示方法、装置、设备及存储介质
CN108141697B (zh) 电子设备、配套设备和操作电子设备的方法
WO2021031940A1 (zh) 放映厅业务管理方法、互动方法、显示设备及移动终端
US20170013458A1 (en) Electronic devices and method for near field communication between two electronic devices
WO2022135156A1 (zh) 分布式跨设备协同方法、电子设备及通信系统
CN114741008B (zh) 分布式跨设备协同方法、电子设备及通信系统
CN106411869A (zh) 通信方法及装置
WO2023046028A1 (zh) 用于分布式显示的屏幕识别方法、介质及电子设备
CN116739574A (zh) 一种显示设备及第三方应用的支付方法
CN115883897A (zh) 显示设备、开机导航配置方法及存储介质
CN115793936A (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: 22778858

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22778858

Country of ref document: EP

Kind code of ref document: A1