A cross-device authentication method

Abstract

The present application provides a method for cross-device authentication, which relates to the field of electronic technology. This method enables a user with multiple devices to call upon the device capabilities of each device to verify the user's data, providing a better user experience. The specific scheme is as follows: a first device receives an authentication request; the first device queries a stored device profile; the first device determines an authentication response device based on the device profile; the first device sends a first message to a second device, the first message including the authentication request; the first device receives a first return result sent by the second device, the first return result being obtained by the second device by identifying the biometric characteristics in the first message; and the first device performs a corresponding operation based on the authentication request.

Description

[0001] This application claims priority to Chinese application No. 202010419055.1, filed on May 18, 2020, entitled “A Method for Cross-Device Authentication,” the entire contents of which are incorporated herein by reference. Technical Field

[0002] The embodiments of the present application relate to the field of electronic technology, and in particular to a method for cross-device authentication. Background Art

[0003] With the continuous development of terminal technology, the number of electronic devices owned by users continues to rise. When users use some functions of smart terminals, such as payment, access to user data, etc., the electronic device needs to confirm the user's identity before executing. In the prior art, some electronic devices have software and hardware for implementing user authentication, and implement user authentication through these software and hardware, such as recognizing the user's face through a camera, or recognizing the user's fingerprint through a fingerprint module. For some electronic devices that do not have software and hardware for user authentication, user authentication cannot be implemented, which brings inconvenience to users. Summary of the Invention

[0004] The embodiment of the present application provides a method for cross-device authentication, which enables electronic devices that support authenticating user identities to provide authentication capabilities for other electronic devices that do not have this capability, making user authentication between devices more flexible and providing a better user experience.

[0005] To achieve the above objectives, the present invention adopts the following technical solutions:

[0006] In the first aspect, the first device receives an authentication request; the first device queries the stored device portrait; the first device determines the authentication response device based on the device portrait; the first device sends a first message to the second device, and the first message includes an authentication request; the first device receives a first return result sent by the second device, and the first return result is obtained by the second device by identifying the biometric characteristics in the first message; the first device performs corresponding operations according to the authentication request.

[0007] In one possible design, before the first device performs a corresponding operation according to the authentication request, the method further includes:

[0008] The first device sends a first message to the third device, where the first message includes an authentication request; the first device receives a second return result sent by the third device, where the second return result is obtained by the third device by identifying the biometric characteristics in the first message; the first device makes a decision based on the first return result and the second return result.

[0009] In one possible design, the device profile includes the device capabilities and device states of the first, second, and third devices. For example, device capabilities include display capabilities, computing capabilities, and storage capabilities. For example, device states include online / offline, connected to / disconnected from WLAN, and screen off / on. Electronic devices can optionally be in one or more device states.

[0010] In one possible design, when the device state of the first device changes, the first device sends the device portrait to the second device and the third device. In one possible design, the first device periodically sends the device portrait to the second device and the third device.

[0011] In one possible design, the first device, the second device, and the third device log in to the same account.

[0012] In one possible design, the first device, the second device, and the third device are connected to the same wireless local area network.

[0013] In one possible design, the biometric characteristic includes at least one of the following: face, fingerprint, iris, retina, DNA, skin, hand shape or vein, voice, signature or gait, gender, age, height or weight.

[0014] In one possible design, the present application provides a device including a processor and a memory, wherein the memory is used to store computer-executable instructions. When the device is running, the processor can execute the computer-executable instructions stored in the memory, so that the electronic device performs a cross-device authentication method.

[0015] In one possible design, the present application provides a computer-readable storage medium including computer instructions. When the computer instructions are executed on an electronic device, the electronic device performs a cross-device authentication method.

[0016] In one possible design, the present application provides a computer program product, which, when executed on a computer, enables the computer to perform a cross-device authentication method.

[0017] The cross-device authentication method provided in this application enables collaborative authentication between electronic devices, allowing users to access data on one device from another device and verify the user's identity based on the device capabilities. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 A schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present application;

[0019] Figure 2 A schematic diagram of the software structure of the electronic device provided in an embodiment of the present application;

[0020] Figure 3 An exemplary user interface diagram of a mobile phone provided in an embodiment of the present application;

[0021] Figures 4A-4C A schematic diagram of a scenario for viewing schedules across devices provided in an embodiment of the present application;

[0022] Figures 5A-5B A schematic diagram of a scenario for querying bills across devices provided in an embodiment of the present application;

[0023] Figures 5C-5F A user interface diagram of the authentication process provided in an embodiment of the present application;

[0024] Figures 6A-6B A schematic diagram of a scenario for viewing photos across devices provided in an embodiment of the present application;

[0025] Figure 7 A flowchart of cross-device authentication provided in an embodiment of the present application. DETAILED DESCRIPTION

[0026] The technical solutions in the embodiments of the present application will be described below in conjunction with the accompanying drawings in the embodiments of the present application. In the description of the embodiments of the present application, unless otherwise specified, " / " means or, for example, A / B can mean A or B; "and / or" in this article is merely a description of the association relationship of associated objects, indicating that three relationships can exist, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, "multiple" means two or more than two.

[0027] In the following, the terms "first" and "second" are used for descriptive purposes only and should not be understood to indicate or imply relative importance or implicitly specify the number of the technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of this embodiment, unless otherwise specified, "plurality" means two or more.

[0028] The embodiments of the present application provide a cross-device authentication method that can be applied to electronic devices such as mobile phones, tablet computers, wearable devices (e.g., watches, bracelets, helmets, headphones, etc.), in-vehicle devices, augmented reality (AR) / virtual reality (VR) devices, laptops, ultra-mobile personal computers (UMPCs), netbooks, personal digital assistants (PDAs), smart home devices (e.g., smart TVs, smart speakers, smart cameras, etc.). It is understandable that the embodiments of the present application do not impose any restrictions on the specific types of electronic devices.

[0029] For example, Figure 1 1 shows a schematic diagram of the hardware structure of the electronic device 100. Figure 1 As shown, the electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc.

[0030] The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU). The different processing units may be independent devices or integrated into one or more processors. The controller may serve as the nerve center and command center of the electronic device 100. The controller may generate operation control signals based on instruction opcodes and timing signals to control instruction fetching and execution. The processor 110 may also include memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a high-speed cache memory. This memory may store instructions or data that have just been used or are being recycled by the processor 110. If the processor 110 needs to use the instruction or data again, it can directly retrieve it from the memory. This avoids duplicate accesses, reduces the processor 110's waiting time, and thus improves system efficiency.

[0031] The USB interface 130 is an interface that complies with USB standards and specifications, and may be a Mini USB interface, a Micro USB interface, a USB Type-C interface, or the like. The USB interface 130 can be used to connect a charger to charge the electronic device 100, and can also be used to transfer data between the electronic device 100 and peripheral devices. The charging management module 140 is used to receive charging input from the charger. The power management module 141 is used to connect the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140, and provides power to the processor 110, the internal memory 121, the external memory, the display 194, the camera 193, and the wireless communication module 160.

[0032] The wireless communication functionality of electronic device 100 can be implemented using antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, a modem processor, and a baseband processor. Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In other embodiments, the antennas can be used in conjunction with a tuning switch.

[0033] The mobile communication module 150 can provide solutions for wireless communications including 2G / 3G / 4G / 5G applied to the electronic device 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves from the antenna 1, and filter, amplify, and process the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna 1. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the same device as at least some of the modules of the processor 110.

[0034] The wireless communication module 160 can provide wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc., which are applied to the electronic device 100. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110. The wireless communication module 160 can also receive the signal to be sent from the processor 110, frequency modulate it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

[0035] In some embodiments, the antenna 1 of the electronic device 100 is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, so that the electronic device 100 can communicate with the network and other devices through wireless communication technology. The wireless communication technology may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technology. The GNSS may include a global positioning system (GPS), a global navigation satellite system (GLONASS), a Beidou navigation satellite system (BDS), a quasi-zenith satellite system (QZSS) and / or a satellite based augmentation system (SBAS).

[0036] Display screen 194 is used to display the display interface of the application, such as the viewfinder interface of the camera application. Display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode or an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a MiniLED, a MicroLed, a Micro-oLed, a quantum dot light-emitting diode (QLED), etc. In some embodiments, electronic device 100 may include one or more display screens 194.

[0037] The ISP processes data fed back by camera 193. For example, when taking a photo, the shutter is opened, and light is transmitted through the lens to the camera's photosensitive element. The light signal is converted into an electrical signal, which is then passed to the ISP for processing and converted into a visible image. The ISP can also perform algorithmic optimization on image noise, brightness, and skin tone. It can also optimize parameters such as exposure and color temperature of the captured scene. In some embodiments, the ISP can be located within camera 193.

[0038] The camera 193 is used to capture still images or videos. The object generates an optical image through the lens and projects it onto the photosensitive element. The photosensitive element can be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, and then passes the electrical signal to the ISP for conversion into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV or other format. In some embodiments, the electronic device 100 may include one or more cameras 193.

[0039] The digital signal processor is used to process digital signals. In addition to processing digital image signals, it can also process other digital signals. For example, when the electronic device 100 selects a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy.

[0040] Video codecs are used to compress or decompress digital video. Electronic device 100 may support one or more video codecs. This allows electronic device 100 to play or record videos in various encoding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, and MPEG4.

[0041] The NPU is a neural network (NN) computing processor. Drawing on the structure of biological neural networks, such as the transmission patterns between neurons in the human brain, it rapidly processes input information and can continuously self-learn. The NPU can enable intelligent cognitive applications in electronic device 100, such as image recognition, face recognition, speech recognition, and text comprehension.

[0042] The internal memory 121 can be used to store computer executable program codes, which include instructions. The processor 110 executes various functional applications and data processing of the electronic device 100 by running the instructions stored in the internal memory 121. The internal memory 121 may include a program storage area and a data storage area. Among them, the program storage area can store an operating system, and software code of at least one application (such as Huawei video application, wallet, etc.). The data storage area can store data generated during the use of the electronic device 100 (such as captured images, recorded videos, etc.). In addition, the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc.

[0043] The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device. The external memory card communicates with the processor 110 via the external memory interface 120 to implement data storage functions. For example, files such as pictures and videos can be stored on the external memory card.

[0044] The electronic device 100 can implement audio functions such as music playback and recording through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone jack 170D, and the application processor.

[0045] Among them, the sensor module 180 can include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0046] Pressure sensor 180A is used to sense pressure signals and convert them into electrical signals. In some embodiments, pressure sensor 180A can be provided on display screen 194. Gyroscope sensor 180B can be used to determine the motion posture of electronic device 100. In some embodiments, gyroscope sensor 180B can be used to determine the angular velocity of electronic device 100 around three axes (i.e., x, y, and z axes).

[0047] The gyroscope sensor 180B can be used for anti-shake shooting. The air pressure sensor 180C is used to measure air pressure. In some embodiments, the electronic device 100 calculates the altitude through the air pressure value measured by the air pressure sensor 180C to assist in positioning and navigation. The magnetic sensor 180D includes a Hall sensor. The electronic device 100 can use the magnetic sensor 180D to detect the opening and closing of the flip leather case. In some embodiments, when the electronic device 100 is a flip phone, the electronic device 100 can detect the opening and closing of the flip according to the magnetic sensor 180D. Then, according to the detected opening and closing state of the leather case or the opening and closing state of the flip, features such as automatic unlocking of the flip can be set. The acceleration sensor 180E can detect the magnitude of the acceleration of the electronic device 100 in various directions (generally three axes). When the electronic device 100 is stationary, the magnitude and direction of gravity can be detected. It can also be used to identify the posture of the electronic device 100, and applied to applications such as horizontal and vertical screen switching and pedometers.

[0048] The distance sensor 180F is used to measure the distance. The electronic device 100 can measure the distance through infrared or laser. In some embodiments, when shooting a scene, the electronic device 100 can use the distance sensor 180F to measure the distance to achieve fast focusing. The proximity light sensor 180G may include, for example, a light emitting diode (LED) and a light detector, such as a photodiode. The light emitting diode can be an infrared light emitting diode. The electronic device 100 emits infrared light outward through the light emitting diode. The electronic device 100 uses the photodiode to detect infrared reflected light from nearby objects. When sufficient reflected light is detected, it can be determined that there is an object near the electronic device 100. When insufficient reflected light is detected, the electronic device 100 can determine that there is no object near the electronic device 100. The electronic device 100 can use the proximity light sensor 180G to detect that the user holds the electronic device 100 close to the ear to talk, so as to automatically turn off the screen to save power. The proximity light sensor 180G can also be used in leather case mode and pocket mode to automatically unlock and lock the screen.

[0049] The ambient light sensor 180L is used to sense ambient light brightness. The electronic device 100 can adaptively adjust the brightness of the display screen 194 based on the perceived ambient light brightness. The ambient light sensor 180L can also be used to automatically adjust the white balance when taking photos. The ambient light sensor 180L can also work with the proximity light sensor 180G to detect whether the electronic device 100 is in a pocket to prevent accidental touches. The fingerprint sensor 180H is used to collect fingerprints. The electronic device 100 can use the collected fingerprint characteristics to implement fingerprint unlocking, access application locks, fingerprint photography, fingerprint call answering, etc.

[0050] The temperature sensor 180J is used to detect temperature. In some embodiments, the electronic device 100 uses the temperature detected by the temperature sensor 180J to execute a temperature processing strategy. For example, when the temperature reported by the temperature sensor 180J exceeds a threshold, the electronic device 100 reduces the performance of the processor located near the temperature sensor 180J to reduce power consumption and implement thermal protection. In other embodiments, when the temperature is lower than another threshold, the electronic device 100 heats the battery 142 to prevent the electronic device 100 from shutting down abnormally due to low temperature. In other embodiments, when the temperature is lower than another threshold, the electronic device 100 boosts the output voltage of the battery 142 to prevent abnormal shutdown due to low temperature.

[0051] The touch sensor 180K is also called a "touch panel." The touch sensor 180K can be disposed on the display screen 194. The touch sensor 180K and the display screen 194 form a touch screen, also called a "touch screen." The touch sensor 180K is used to detect touch operations applied thereto or in the vicinity thereof. The touch sensor can transmit the detected touch operations to the application processor to determine the type of touch event. Visual output related to the touch operations can be provided via the display screen 194. In other embodiments, the touch sensor 180K can also be disposed on the surface of the electronic device 100, in a location different from that of the display screen 194.

[0052] Bone conduction sensor 180M can acquire vibration signals. In some embodiments, bone conduction sensor 180M can acquire vibration signals from vibrating bones in the human body. Bone conduction sensor 180M can also contact the human pulse to receive blood pressure signals.

[0053] The buttons 190 include a power button, a volume button, etc. The button 190 can be a mechanical button. It can also be a touch button. The electronic device 100 can receive button input and generate key signal input related to the user settings and function control of the electronic device 100. The motor 191 can generate a vibration prompt. The motor 191 can be used for incoming call vibration prompts, and can also be used for touch vibration feedback. For example, touch operations acting on different applications (such as taking pictures, audio playback, etc.) can correspond to different vibration feedback effects. The touch vibration feedback effect can also support customization. The indicator 192 can be an indicator light, which can be used to indicate the charging status, power changes, and can also be used to indicate messages, missed calls, notifications, etc. The SIM card interface 195 is used to connect the SIM card. The SIM card can be inserted into the SIM card interface 195 or pulled out from the SIM card interface 195 to achieve contact and separation with the electronic device 100.

[0054] It is understandable that Figure 1 The components shown do not constitute a specific limitation on the electronic device 100. The electronic device 100 may also include more or fewer components than shown, or combine some components, separate some components, or arrange the components differently. Figure 1 The combination / connection relationship between the components can also be adjusted and modified.

[0055] Figure 2 FIG. 1 shows a schematic diagram of the software structure of the electronic device 100 provided in an embodiment of the present application. Figure 2As shown, the software structure of the electronic device 100 can be a layered architecture. For example, the software can be divided into several layers, each with a clear role and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into five layers, from top to bottom: the application layer, the application framework layer (framework, FWK), the system library and Android runtime (Android runtime), the hardware abstraction layer (HAL), and the kernel layer.

[0056] The application layer can include a series of application packages. Figure 2 As shown, the application layer may include camera, settings, skin module, user interface (UI), third-party applications, etc. Among them, third-party applications may include gallery, calendar, call, map, navigation, WLAN, Bluetooth, Huawei music, Huawei video, SMS, etc.

[0057] The application framework layer provides application programming interface (API) and programming framework for the application layer. The application framework layer may include some predefined functions. Figure 2 As shown, the application framework layer may include a window manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, and the like.

[0058] The window manager manages windowed applications. It can determine the display size, determine whether a status bar is present, lock the screen, and take screenshots. Content providers store and retrieve data and make it accessible to applications. This data can include video, images, audio, incoming and outgoing calls, browsing history and bookmarks, and phone books.

[0059] The view system includes visual controls, such as those for displaying text and images. The view system is used to build applications. A display interface can consist of one or more views. For example, a display interface containing a text notification icon might include a view for displaying text and a view for displaying images.

[0060] The phone manager is used to provide communication functions of the electronic device 100, such as management of call status (including answering, hanging up, etc.).

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

[0062] The notification manager enables applications to display notification information in the status bar. This can be used to convey notification-type messages and can disappear automatically after a short period of time without user interaction. For example, the notification manager is used to notify the completion of downloads, message reminders, etc. The notification manager can also be used to display notifications in the form of icons or scrolling text in the top status bar of the system, such as notifications from applications running in the background, or notifications that appear on the screen in the form of dialog windows. For example, a text message can be displayed in the status bar, a notification sound can be emitted, the electronic device 100 can vibrate, an indicator light can flash, etc.

[0063] The Android runtime includes the core library and the virtual machine. The Android runtime is responsible for scheduling and management of the Android system.

[0064] The core library consists of two parts: one containing the Java language's callable functions and the other the Android core library. The application layer and the application framework layer run in a virtual machine. The virtual machine executes the Java files in the application layer and application framework layer as binary files. The virtual machine manages object lifecycles, stack management, thread management, security and exception management, and garbage collection.

[0065] The system library can include multiple functional modules, such as a surface manager, media libraries, a 3D graphics processing library (such as OpenGL ES), and a 2D graphics engine (such as SGL).

[0066] The surface manager is used to manage the display subsystem and provide fusion of 2D and 3D layers for multiple applications.

[0067] The media library supports playback and recording of a variety of common audio and video formats, as well as static image files. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

[0068] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing and layer processing.

[0069] A 2D graphics engine is a drawing engine for 2D drawings.

[0070] The hardware abstraction layer provides a standard interface for the hardware of the hardware layer. The hardware abstraction layer optionally includes display drivers, camera drivers, audio drivers, and sensor drivers.

[0071] The kernel layer is the layer between hardware and software. The kernel layer optionally includes display drivers, camera drivers, audio drivers, and sensor drivers.

[0072] The hardware layer may optionally include various hardware devices, such as sensors for various functions provided in the sensor module 180 .

[0073] The electronic device 100 calls the sensor of the hardware layer, optionally accesses the sensor interface provided by the hardware abstraction layer, and optionally uses the sensor driver provided by the kernel layer.

[0074] The following examples will be Figure 1 or Figure 2 The electronic device 100 shown is a mobile phone as an example, and the technical solution provided by the embodiment of the present application is described in conjunction with the accompanying drawings.

[0075] Figure 3 An exemplary user interface 301 of a mobile phone provided in an embodiment of the present application is shown. The user interface 301 can be displayed on the display screen 194 of the mobile phone.

[0076] In a possible embodiment, the user interface 301 optionally includes the following elements or a subset or a superset thereof:

[0077] Icons fixed to the top status bar and used to indicate the status of the device, including: one or more signal strength (e.g., mobile network, Wi-Fi) indicators 303, current time 305, and a power indicator 307 for indicating the power level of the battery 142;

[0078] The main interface and application icons on the main interface include: Clock 309, Calendar 311, Gallery 313, Memo 315, File Management 317, Email 319, Music 321, Wallet 323, Huawei Video 325, Sports & Health 327, Weather 329, Browser 331, Smart Life 333, Settings 335, Voice Recorder 337, and App Store 339;

[0079] Application icons fixed at the bottom: Camera 341, Contacts 343, Phone 345, Messages 347;

[0080] An indicator 349 indicating the current interface.

[0081] It is understandable that the main interface includes clock 309, calendar 311, gallery 313, memo 315, file management 317, email 319, music 321, wallet 323, Huawei video 325, sports health 327, weather 329, browser 331, smart life 333, settings 335, recorder 337, and app store 339. When the user interface 301 displays other interfaces for displaying application icons (non-main interface), the indicator 349 indicating the current interface may optionally point to the switched interface, the icons fixed to the top status bar may optionally remain unchanged, and the application icons fixed to the bottom may optionally remain unchanged.

[0082] It is understandable that the above icons are merely examples of applications, and may be other forms of these exemplary applications, or icons corresponding to other applications.

[0083] With the continuous development of Internet of Things technology and terminal technology, users have more and more electronic devices of different types and functions. These electronic devices usually have communication functions and can communicate with one or more other electronic devices through one or more communication protocols to achieve data interaction.

[0084] In some possible implementations, a mobile phone and a tablet are two exemplary devices of the electronic device 100. The mobile phone optionally communicates with the tablet via the wireless communication module 160, optionally enabling the transmission of multimedia files, such as text, pictures, videos, and files; optionally enabling the transmission of application data, such as the mobile phone sending application data from Huawei Video 325 to the tablet, or the mobile phone sending schedule data in the calendar 311 to the tablet; and optionally enabling the transmission of user data. For example, if a user needs to perform activities involving user identity verification, such as payment and unlocking, on the tablet, the mobile phone can be used for auxiliary authentication to achieve cross-device payment and authentication.

[0085] The following describes the device portrait of electronic device 100. This portrait is a set of data used to describe electronic device 100, optionally including two dimensions: device capabilities and device status. The device portrait is optionally stored as data in the internal memory 121 of electronic device 100 and / or other storage devices connected to external memory interface 120. The device capabilities and device status are described separately below.

[0086] The electronic device 100 may optionally include different types and numbers of hardware components, different types and numbers of software and hardware interfaces, and different software architectures, thereby having different device capabilities. Device capabilities include, but are not limited to, system integrity, computing power, storage capacity, and display capabilities.

[0087] In some possible implementations, a mobile phone and a tablet are exemplary devices of the electronic device 100, which may optionally include a processor 110 with high computing performance; may optionally include internal memory 121 and / or other storage devices connected to an external memory interface 120; may optionally include an LCD / OLED / AMOLED display screen 194 with good display quality and a large size; may optionally include one or more wireless communication modules 160, such as a WLAN module, a Bluetooth module, an NFC module, etc.; may optionally include a battery 142; and may optionally include a variety of software and hardware interfaces. The mobile phone and tablet have a complete operating system and can install some applications on the internal memory 121 and / or other storage devices connected to the external memory interface 120, such as a calendar 311 that can provide a function for recording schedules, a music 321 that can provide a function for playing audio files, and a wallet 323 that can provide a function for payment.

[0088] In some possible implementations, a smart speaker is an electronic device 100 that optionally includes a processor 110 with low computing performance, optionally includes internal memory 121 and / or other storage devices connected to an external memory interface 120; optionally does not include a display screen 194 or includes an LCD display screen 194 with weaker display capabilities; optionally includes one or more wireless communication modules 160, such as a WLAN module, a Bluetooth module, an NFC module, etc.; optionally includes or does not include a battery 142; and optionally includes some hardware and software interfaces. The Bluetooth speaker optionally includes an incomplete operating system or does not include an operating system, and can store some SDKs (Software Development Kits) on the internal memory 121 or other storage devices connected to the external memory interface 120. These SDKs provide mobile phones with services such as recording schedules, playing audio, and recognizing voice.

[0089] It is understandable that the strength of a device's capabilities is a relative concept. For example, in the two implementation schemes shown above, when the tablet has an LCD display and the smart speaker does not have a display, the tablet has better display capabilities than the smart speaker; and when the mobile phone has an OLED display and the tablet has an LCD display, the mobile phone has better display capabilities than the tablet.

[0090] The electronic device 100 may optionally include different device states, including but not limited to: powered on / off, unlocked / locked, screen on / off, working (occupied) / idle, recently used / unused, connected to WLAN / disconnected from WLAN, etc. It is understood that the electronic device 100 may optionally be in one or more of the aforementioned device states.

[0091] In one possible embodiment, the mobile phone is optionally powered on; the mobile phone is optionally in the screen-off state; the mobile phone is optionally playing an audio file in the music application 321 through the speaker 170A, and the mobile phone is in the working (occupied) state; the mobile phone is optionally used by the user in the recent period; the mobile phone is optionally connected to the WLAN and can exchange data with other electronic devices 100. In another possible embodiment, the smart speaker is optionally powered on; the smart speaker is optionally in the idle state; the smart speaker is optionally not used by the user in the recent period; the smart speaker is optionally connected to the WLAN and can exchange data with other electronic devices 100.

[0092] In some possible embodiments, the electronic device 100 optionally stores data through the internal memory 121 and / or other storage devices connected to the external memory interface 120, and the data optionally includes a device portrait, such as device capability data and device status data.

[0093] In some possible implementations, the electronic device 100 may also optionally store data, such as file data, schedule data, location data, health data, biometrics, etc., through the internal memory 121 and / or other storage devices connected to the external memory interface 120. Some of this data may have a high impact on the user, such as health data and biometrics. This type of data may involve the user's privacy and cannot be used by other users at will. In some possible implementations, data that has a high impact on the user may be optionally pre-set by the electronic device 100, or may be manually set and updated by the user of the electronic device 100.

[0094] In some possible implementations, when a user accesses this data, the electronic device 100 needs to authenticate the user's identity. The user can only use this data if the user's identity matches the user identity stored in the electronic device 100; if the user's identity does not match the user identity stored in the electronic device 100, the user cannot use this data. Therefore, when a user accesses or uses this data, the electronic device 100 needs to authenticate the user's identity. Common authentication methods include authentication via passwords, biometrics such as fingerprints, voiceprints, irises, and facial features, as well as SMS authentication and multi-factor authentication.

[0095] When authenticating the user's identity, the device capabilities will have a significant impact on the authentication of the electronic device 100. In some possible implementations, a mobile phone including one camera 193 may optionally support 2D face recognition; a mobile phone including two or more cameras 193 may optionally support 3D face recognition, wherein 3D face recognition has higher credibility and is more secure than 2D face recognition; a mobile phone that does not include a camera 193 does not support face recognition. In another possible embodiment, a mobile phone including a fingerprint sensor 180H supports determining the user's identity by identifying a detected fingerprint input, while a mobile phone that does not include a fingerprint sensor 180H does not support determining the user's identity by identifying a detected fingerprint input. In another possible embodiment, a mobile phone including a voiceprint recognition module supports determining the user's identity by identifying a detected voiceprint input, while a mobile phone that does not include a voiceprint recognition module does not support determining the user's identity by identifying a detected voiceprint input.

[0096] In some possible implementations, a user owns multiple electronic devices 100. Once the first device successfully authenticates the user, the user can only access the data stored on the first device and use the functions of the device, but cannot access the data stored on other electronic devices 100 or use the functions of other electronic devices 100. For example, a user owns both a mobile phone and a tablet. After the processor 110 of the mobile phone determines that the input of the fingerprint sensor 180H is that of the local user, the user can access the data stored on the mobile phone and use the functions of the mobile phone (for example, using the camera 193 to take photos). However, the user cannot access the data stored on the tablet or use the functions of the tablet.

[0097] This will lead to a fragmented device usage experience. When users access data, they need to verify each device separately, resulting in repeated operations and a poor user experience.

[0098] This application proposes an implementation plan for distributed device profiling.

[0099] On the basis of establishing a near-field connection based on the distributed device portrait, the technologies for establishing a near-field connection include but are not limited to: Wireless Local Area Network (WLAN) (such as Wireless Fidelity (Wi-Fi)), Bluetooth (BT), Near Field Communication (NFC), Ultra Wide Band (UWB), Infrared (IR), ZigBee, general 2.4G / 5G frequency band wireless communication technology, etc. Devices that establish a near-field connection do not need to go through the cloud / server when interacting with data. Data is only transmitted between devices that establish a near-field connection through the wireless communication module 160. This implementation method is more secure than transmission through the cloud / server and meets the need to protect user data privacy.

[0100] The implementation of distributed device portraits also requires the establishment of a trust relationship between the electronic devices 100. The technology for establishing a trust relationship can optionally be that the electronic devices 100 log in to the same account, such as the user's tablet, the tablet and the smart TV log in to the Huawei account, Apple account, etc. at the same time; optionally, different electronic devices 100 are associated with the same account, for example, the smart speaker does not have the ability to log in to the account, but can be associated with the application installed on the mobile phone / tablet, at which time the smart speaker can be controlled through the application; optionally, a trust list is created on the first device, and the second device is added to the trust list. At this time, a trust relationship is established between the first device and the second device. For example, the mobile phone creates a trust list. When the smart speaker is connected to the mobile phone through the wireless communication module 160, the mobile phone collects the name / identity of the smart speaker. The user adds the name / identity of the smart speaker to the trust list. At this time, a trust relationship is established between the mobile phone and the smart speaker.

[0101] Distributed device portrait refers to the synchronized device portrait between trusted devices that establish a near-field connection, wherein the device that establishes the distributed device portrait can autonomously implement task scheduling in combination with the device capabilities and device status of other devices, thereby giving the user the experience of using a super terminal. In some possible implementation schemes, the first device, the second device, and the third device log in to the same account, and the first device, the second device, and the third device are under the same WLAN. The first device collects and sends the device portrait to the second device and the third device; the second device collects and sends the device portrait to the first device and the third device; the third device collects and sends the device portrait to the first device and the second device. At this time, each electronic device 100 stores the device portrait of the electronic device 100 with which it establishes a near-field connection and trust relationship.

[0102] When the device portrait of one or more devices among the trusted devices establishing a near-field connection changes, the device portrait needs to be synchronized with the other devices in the trusted devices establishing the near-field connection.

[0103] In some possible implementations, if the device profile of the first device changes, the first device collects and sends the device profile to the second and third devices. In some possible implementations, if the device profile of the first device changes, the first device collects and sends the changed device profile to the second and third devices, while other unchanged device profiles do not need to be transmitted to the second and third devices.

[0104] When a new device establishes a near-field connection and trust relationship with an existing device, the device portrait needs to be synchronized.

[0105] In some possible implementations, the fourth device is a newly added device that establishes a near-field connection with the first, second, and third devices and a trusted relationship with the first, second, and third devices. The fourth device collects and sends a device profile to the first, second, and third devices, and the first, second, and third devices send their respective device profiles to the fourth device.

[0106] When an existing device disconnects from the near-field connection and / or cancels the trust relationship with other devices, the device portrait needs to be synchronized.

[0107] In some possible implementations, the first device, the second device, and the third device establish a near-field connection via WLAN technology. When the first device disconnects the near-field connection, the second device detects that the first device has disconnected the near-field connection (for example, the second device sends a first message to the second device, but does not receive a return code from the second device within a time period). The second device refreshes the stored device profile and changes the connected WLAN state parameter in the device status of the first device to the disconnected WLAN state. The second device sends the changed device profile to the third device.

[0108] Trusted devices that establish a near field connection may optionally synchronize device portraits periodically.

[0109] In some possible implementation schemes, the first device, the second device, and the third device use the same timing cycle. After the timing cycle is reached, the first device collects and sends the device portrait to the second device and the third device; the second device collects and sends the device portrait to the first device and the third device; and the third device collects and sends the device portrait to the first device and the second device.

[0110] In some possible implementation schemes, the first device cycle can optionally use an independent timing cycle for each device. After the first device reaches the timing cycle of the first device, it collects and sends the device portrait to the second device and the third device; after the second device reaches the timing cycle of the second device, it collects and sends the device portrait to the first device and the third device; after the third device reaches the timing cycle of the third device, it collects and sends the device portrait to the first device and the second device.

[0111] In some possible implementations, when a trigger event occurs, the electronic device 100 actively synchronizes the device portrait. For example, when the first device detects a trigger event for unlocking the screen, the first device collects and sends the device portrait to the second device and the third device. After the second device receives the device portrait sent by the first device (optionally including the event that the first device unlocked the screen), it collects and sends the device portrait to the first device and the third device. After the third device receives the device portrait sent by the first device (optionally including the event that the first device unlocked the screen), it collects and sends the device portrait to the first device and the second device.

[0112] When the electronic device 100 receives the device portrait, in some possible implementation schemes, the electronic device 100 sends a return code to the electronic device that sent the device portrait. In other possible implementation schemes, the electronic device 100 does not send a return code to the electronic device that sent the device portrait.

[0113] In some possible implementations, some device portrait data may affect the real-time performance of the distributed device portrait system (for example, after a power outage on the first device, but there is no corresponding record on the second device). In this case, data synchronization can be performed at a first frequency. Some device portrait data may not affect the real-time performance of the distributed device portrait system. In this case, data synchronization can be performed at a second frequency. The first frequency is higher than the second frequency.

[0114] The establishment and synchronization of distributed device portraits can enable the trusted device that establishes a near-field connection to store the device portraits of other electronic devices 100. At this time, the electronic device 100 can query the device capabilities and device status of each device, thereby realizing the sharing of device capabilities between devices. For example, the mobile phone can determine that the smart speaker is in an idle state by querying the locally stored device portrait, and send an audio file to the smart speaker through the wireless communication module 160. The smart speaker plays the audio file through the speaker 170A. For another example, the tablet can determine that the mobile phone includes a camera 193 by querying the locally stored device portrait, and send a request to call the camera 193 to the mobile phone through the wireless communication module 160. The mobile phone starts the camera 193 and takes a photo. The mobile phone sends the taken photo to the tablet through the wireless communication module 160.

[0115] In some possible implementations, a central device, optionally a more powerful device such as a mobile phone or television, is included among the devices building the distributed device profile. When a device other than the central device requires cross-device authentication, it first sends a cross-device authentication request to the master device, which then makes the authentication decision (e.g., schedules the authentication task).

[0116] In some possible implementations, the central device is not a fixed device. For example, a data stack can be established to determine the central device in the distributed device profile, with the device at the top of the data stack being the central device. If the first device at the top of the stack goes offline, the second device becomes the top device, receiving authentication requests from other devices and making authentication decisions.

[0117] The following describes a specific implementation process of a cross-device authentication method in combination with scenarios.

[0118] 1. Users use smart speakers to broadcast their schedule data

[0119] Figure 4A A cross-device authentication scenario is shown, which includes a smart speaker 401, a mobile phone 403, and a tablet 405. The smart speaker 401, the mobile phone 403, and the tablet 405 construct a distributed device portrait.

[0120] Figure 4B This diagram shows a user waking up the device and performing an action using voice. An optional user voice command is "Xiaoyi Xiaoyi, check tomorrow's schedule." "Xiaoyi Xiaoyi" is the device wake-up word, and the user's intention here is to check tomorrow's schedule.

[0121] The user's intention is to view the schedule, and the smart speaker 401 can optionally only view the locally stored schedule. However, in order to provide a better user experience and provide the user with a more complete schedule, the smart speaker 401 also needs to collect the schedules on the electronic device 100 with which the distributed device portrait is established, that is, the smart speaker 401 needs to collect the schedules on the mobile phone 403 and the tablet 405.

[0122] In some possible implementations, the smart speaker 401 has a voice recognition function. After detecting the device wake-up word "Xiaoyi Xiaoyi", the smart speaker 401 collects voice data and outputs the user's intention to check the schedule through voice recognition technology and natural language processing technology.

[0123] In some possible implementations, the smart speaker does not have voiceprint recognition capabilities, meaning that the smart speaker 401 cannot determine whether the identity of the voice data matches one or more user identities stored locally, or whether the voiceprint of the voice data matches the voiceprint of one or more users stored locally. The smart speaker 401 queries the stored distributed device profiles and discovers that the electronic device 100 with voiceprint recognition capabilities includes a mobile phone 403 and a tablet 405. The smart speaker 401 initiates an authentication request to the mobile phone 403 and the tablet 405. The smart speaker 401 optionally sends the voice data to the mobile phone 403 and the tablet 405; the smart speaker 401 also optionally sends the voice data and the user's intent to the mobile phone 403 and the tablet 405.

[0124] In some possible implementations, after receiving voice data, mobile phone 403 and tablet 405 use voiceprint recognition technology to determine whether the voice data matches the voiceprints of one or more users stored locally. In some possible implementations, mobile phone 403 determines that the voice data matches the locally stored user voiceprints and, based on the received user intent, performs an operation responsive to the user intent. Specifically, mobile phone 403 collects schedule data from calendar 311 and returns it to smart speaker 401. Tablet 405 determines that the voice data matches the locally stored user voiceprints and receives the user intent. Tablet 405 performs an operation responsive to the user intent. Specifically, tablet 405 collects schedule data from calendar 311 and returns it to smart speaker 401. After receiving the returned matching result and schedule data, the smart speaker 401 matches. The smart speaker 401 optionally collects locally stored schedule data and optionally merges the local schedule data with the received schedule data. Using speech synthesis technology, the processor 110 of the smart speaker 401 calls the audio module 170 and speaker 170A to broadcast the schedule data, thus completing the data collection and broadcast between devices to establish a distributed device profile. The broadcast method can optionally broadcast each schedule in the synthesized schedule data, and can also optionally broadcast each schedule in the synthesized schedule data and the device source corresponding to the schedule. Figure 4C A schematic diagram of a scenario in which the smart speaker 401 broadcasts schedule data is shown.

[0125] In some possible implementations, after receiving the voice data, mobile phone 403 and tablet 405 use voiceprint recognition technology to determine whether the voice data matches the voiceprints of one or more users stored on the mobile phone. In some possible implementations, mobile phone 403 determines whether the voice data matches the voiceprints of the users stored on the mobile phone and returns a matching result. After receiving the results from mobile phone 403 and tablet 405, smart speaker 401 determines whether the voice data matches the stored users. For example, if the smart speaker 401 receives a yes return result from the mobile phone 403 and a yes return result from the tablet 405, the smart speaker 401 determines that the identity of the voice data matches the stored user, and the smart speaker 401 sends a request to the mobile phone 403 and the tablet 405 to obtain schedule information; for another example, if the smart speaker 401 receives a yes return result from the mobile phone 403 and a no return result from the tablet 405, the smart speaker 401 determines that the identity of the voice data matches the user stored in the mobile phone 403, but does not match the user stored in the tablet 405, and the smart speaker 401 sends a request to the mobile phone 403 to obtain schedule information; for another example, if the smart speaker 401 receives a match degree of 80% return result from the mobile phone 403 and a match degree of 90% return result from the tablet 405, the smart speaker 401 determines that the identity of the voice data matches the stored user based on a threshold value (for example, 60%), and the smart speaker 401 sends a request to the mobile phone 403 and the tablet 405 to obtain schedule information.

[0126] In some possible implementation schemes, the smart speaker 401 sends the synthesized schedule data to the mobile phone 403 and / or the tablet 405 , so that the user can view the synthesized schedule data on the mobile phone 403 and / or the tablet 405 .

[0127] In some possible implementations, the smart speaker 401 has a voiceprint recognition function, that is, the smart speaker 401 can determine whether the collected voice data matches the voiceprints of one or more users stored locally. When the voiceprints match, the smart speaker 401 determines that the current user of the smart speaker is the stored user, and the smart speaker 401 sends the user's intention to the mobile phone 403 and tablet 405. After receiving the user's intention, the mobile phone 403 and tablet 405 perform operations responsive to the user's intention, collect and return the schedule data to the smart speaker 401. After collecting the locally stored schedule data, the smart speaker 401 merges the received schedule data with the collected schedule data, and optionally uses voice recognition technology to broadcast the schedule through the audio module 170 and speaker 170A.

[0128] In some possible implementations, the devices used to create a distributed device profile include a smart speaker 401, a mobile phone 403, and a tablet 405. Smart speaker 401 and tablet 405 do not have voiceprint recognition capabilities, while mobile phone 403 does. After querying the stored distributed device profile, smart speaker 401 sends the voice data and user intent to mobile phone 403. Mobile phone 403 determines whether the voiceprint of the voice data matches the stored user's voiceprint and returns the matching result and schedule data to smart speaker 401. After receiving the matching result and schedule data, smart speaker 401 sends the user intent to tablet 405. After receiving the user data, tablet 405 optionally collects schedule data and returns the schedule data to smart speaker 401. Smart speaker 401 merges the received schedule data with the collected schedule data to generate synthesized schedule data.

[0129] In some possible implementations, the smart speaker 401 may optionally only send an authentication request to the other device, which then collects the voice data and performs the authentication. In some possible implementations, the smart speaker 401 may optionally send the voice data to the other device, which then performs the authentication. In some possible implementations, the smart speaker 401 may optionally perform the authentication and voice data processing itself, and then send the processed results to the other device.

[0130] 2. Users use smart speakers to check their bills

[0131] Figure 4A A cross-device authentication scenario is shown, which includes a smart speaker 401, a mobile phone 403 and a tablet 405, wherein the smart speaker 401, the mobile phone 403 and the tablet 405 build a distributed device portrait and are connected to the same WLAN.

[0132] Figure 5A This diagram shows a user waking up the device and performing an action using voice. An optional user voice command is "Xiaoyi Xiaoyi, check this month's bill for the credit card ending in 1501." "Xiaoyi Xiaoyi" is the device wake-up phrase, and the user's intention here is to check the credit card bill.

[0133] In some possible implementations, smart speaker 401 has a voice recognition function. After detecting the device wake-up word "Xiao Yi Xiao Yi", smart speaker 401 collects voice data and outputs the user's intention in the voice data through voice recognition technology and natural language processing technology to inquire about the credit card bill. Smart speaker 401 needs to determine whether the identity of the voice data matches the identity of one or more stored users, that is, whether the voice print of the voice data matches the voice print of one or more users.

[0134] In some possible implementations, the smart speaker 401 has a voiceprint recognition function. When the smart speaker 401 determines that the voiceprint of the speech data matches the user's voiceprint stored locally, the smart speaker proceeds to perform the following operations.

[0135] By querying the stored distributed device portraits, the smart speaker 401 finds that the mobile phone 403 has a credit card-related application, that is, the mobile phone 403 can support credit card bill inquiries. The smart speaker 401 sends the user intention to the mobile phone 403. In some possible implementation schemes, after receiving the user's intention, the mobile phone 403 queries the credit card bill and returns it to the smart speaker 401. In some possible implementation schemes, the mobile phone 403 determines that the action of querying the credit card requires reconfirmation of the user's identity. The confirmation method can optionally be fingerprint confirmation, that is, the user needs to enter the fingerprint again to verify the identity. In some possible implementation schemes, the mobile phone 403 prompts the user that fingerprint authentication is required. In some possible implementation schemes, the mobile phone 403 returns the result to the smart speaker 401, and then the smart speaker 401 prompts the user that fingerprint authentication is required, such as Figure 5B shown. Figure 5C-5F The relevant UI interface of fingerprint authentication is shown, such as Figure 5C As shown, the lock screen interface 501 of the mobile phone 403 includes a prompt box 503, which is used to prompt the user that an authentication request has been received and ask whether to authenticate the device. Figure 5D As shown, a face recognition prompt box 503 is displayed on the lock screen interface 501, which is used to prompt the user to verify the identity information through the face. Figure 5E As shown, a fingerprint authentication prompt box 505 is displayed on the lock screen interface 501, which is used to prompt the user to authenticate the identity information through fingerprint recognition. Figure 5F As shown, an authentication success prompt box 507 is displayed on the lock screen interface 501, indicating that the voiceprint data, fingerprint data and stored user data match. After the mobile phone 403 receives the user's fingerprint input and determines that the voiceprint and voice data match the user stored locally, the mobile phone 403 opens the credit card application in the background to query the credit card bill. In some possible implementation schemes, the mobile phone 403 determines that the data privacy is relatively high and does not send it to the smart speaker 401, and chooses to broadcast the voice data through the audio module and speaker of the mobile phone 403. In some possible implementation schemes, the mobile phone 403 sends the credit card bill to the smart speaker 401, and the smart speaker broadcasts the voice data through the audio module and speaker. It can be understood that the broadcast voice data needs to be implemented through speech synthesis technology. This process optionally occurs on the mobile phone 403 and optionally occurs on the smart speaker 401. This embodiment of the present application does not limit this.

[0136] In some possible implementations, if mobile phone 403 has a credit card app installed but lacks fingerprint recognition capabilities, and tablet 405 supports fingerprint recognition but doesn't have the credit card app installed, smart speaker 401 may optionally first send a request to tablet 405 to perform fingerprint recognition on the user. Upon receiving this request, tablet 405 may optionally prompt the user to verify their fingerprint. When tablet 405 determines that the fingerprint entered by the user, the audio data sent by smart speaker 401, and the locally stored user data match, tablet 405 sends a response to smart speaker 401. Upon receiving this response, smart speaker 401 transmits the user's intent to mobile phone 403, which then opens the credit card app in the background to query the credit card bill. In some possible implementations, mobile phone 403 sends the credit card bill to smart speaker 401, which then broadcasts the voice data via its audio module and speaker. It is understood that the voice data broadcast may require speech synthesis technology, and this process may occur on mobile phone 403 or smart speaker 401, though this embodiment of the application is not limiting in this regard.

[0137] In some possible implementations, smart speaker 401 needs to determine whether mobile phone 403 is online before sending the user intent. If mobile phone 403 is online, smart speaker 401 chooses to send the user intent to mobile phone 403; if mobile phone 403 is offline, it chooses not to send the user intent, and other devices other than mobile phone 403 used to build the distributed device profile do not have the function of querying credit card information. Smart speaker 401 determines that the execution has failed and optionally announces the failure through voice, such as "execution failed". In some possible implementations, after sending the user intent to mobile phone 403, smart speaker 401 receives a return result from mobile phone 403 after a certain period of time, determines that mobile phone 403 is offline, changes the collected WLAN connection status parameters to the WLAN disconnected status, and optionally updates the updated distributed device profile data to other online devices.

[0138] 3. Users use TV to find electronic devices

[0139] In some possible implementations, some electronic devices in home and office scenarios are shared by users, such as a television in a home scenario and a projector in an office scenario. Users cannot establish distributed device profiles with these electronic devices. For example, user A's multiple electronic devices establish distributed device profiles with the television, and the television stores the device profiles of user A's multiple electronic devices. At the same time, user B's multiple electronic devices also establish distributed device profiles with the television, and the television also stores the device profiles of user B's multiple electronic devices. In this case, user A's multiple electronic devices, user B's multiple electronic devices, and the television all establish distributed device profiles, meaning user A can view the device capabilities and device status of one or more electronic devices of user B, which brings about user privacy issues.

[0140] In some possible implementation schemes, the embodiments of the present application also include public devices. The public device can optionally send its own device portrait to other electronic devices with which it establishes a distributed device portrait. It will store a list of devices with which it establishes a distributed device portrait (such as the device name and MAC address of the device), but will not store the device portrait (device capabilities and / or device portrait), nor will it store user data, such as the user's voiceprint data, fingerprint data, etc. That is, the public device can communicate with the devices in the stored device list, but will not store the data of these devices (for example, device status, processing capabilities, etc.). On the side of other electronic devices that establish distributed device portraits, the device portrait of the public device will be stored, and a label for distinguishing the public device will be set. In other words, the public device can know which devices have established a distributed device portrait with it through existing technology, and can communicate with these devices, but does not know the device capabilities and device status of these devices. Other electronic devices that establish distributed device portraits with the public device can distinguish the public devices in the stored device list, will not send their own device portrait data to the public device, but can view the device portrait of the public device locally.

[0141] In some possible implementations, if a public device is not logged into an account, when a user needs to establish a distributed device profile with the public device, the user can scan a code provided by the public device, such as a one-dimensional code, a two-dimensional code, a QR code, etc., through an electronic device in the established distributed profile. Alternatively, the user can bring the electronic device in the established distributed device profile close to the NFC tag of the public device. In this way, the public device can be added to the established distributed device profile.

[0142] In some possible implementations, a television is an example of a public device. A user wakes up the television with a voice command, for example, "Xiaoyi, Xiaoyi, help me find my phone." Upon receiving the voice data, the television optionally recognizes the voice as a request to find a phone and sends the voice data and semantics to each electronic device in a device list. Upon receiving the voice data, the electronic device first determines whether the voiceprint of the voice data matches the user's stored voiceprint. If so, it performs the action corresponding to the received semantics, such as determining whether the electronic device is a mobile phone. If so, it may optionally vibrate or emit a sound. In some possible implementations, some mobile phones do not have voiceprint recognition capabilities. In this case, an electronic device capable of voiceprint recognition determines whether the voiceprint of the voice data matches the user's voiceprint. It then queries its stored device profiles and prompts other electronic devices with mobile phone types to vibrate or emit a sound. In some possible implementations, the mobile phone also returns a prompt to the television, prompting the phone to vibrate or emit a sound, for example, through a pop-up window. In some possible implementations, if the TV does not receive a response from the device after a period of time, it may display a device not found message on the TV.

[0143] 4. Users view photos on TV

[0144] In some possible implementations, users have a need to display multimedia content on public devices, such as viewing photos stored on a mobile phone or tablet on a TV. Figure 6A As shown, the scene includes TV 601, mobile phone 603 and mobile phone 605, wherein TV 601, mobile phone 603 and mobile phone 605 establish distributed device portraits and are currently in the same WLAN.

[0145] In some possible implementations, a diagram shows a user waking up a device and performing an action using voice. The user voice can be, for example, "Xiaoyi, Xiaoyi, I want to see photos from the last 90 days." The television 603 can optionally utilize voice recognition and natural language processing technologies to determine that the user's intention is to view photos.

[0146] The TV 603 sends voice data (optionally including the semantics corresponding to the voice data) to the electronic devices in the device list. After receiving the voice data, the electronic devices first determine whether the voiceprint of the voice data matches the voiceprint of the user stored locally. If they match, the actions corresponding to the received semantics are executed. In some possible implementation schemes, the mobile phone 603 determines that it matches and sends the photos on the mobile phone 603 to the smart TV 601. The mobile phone 603 determines that it matches and sends the photos on the mobile phone 605 to the smart TV 601. The user can Figure 6BAs shown, photos on mobile phone 601 and mobile phone 603 are viewed on TV 601. In some possible implementations, in order to better protect the user's privacy and not store the user's data on public devices, mobile phone 601 and mobile phone 603 can optionally display photos of mobile phone 603 and mobile phone 605 on smart TV 601 by screen projection.

[0147] In some possible implementations, two accounts are logged into mobile phone 603, and each image in the gallery of mobile phone 603 is labeled to indicate whether the image is associated with the first account or the second account. When the voice data corresponds to the first account, television 601 only displays images labeled as corresponding to the first account; when the voice data corresponds to the second account, television 601 only displays images labeled as corresponding to the second account.

[0148] The following describes how cross-device authentication works.

[0149] The authentication requesting device detects (step 701) an authentication request. It is understood that the authentication request may be manifested as the authentication requesting device detecting input data, where the action required in the input data requires authentication of the user's identity. In some embodiments, the authentication request may be voice data input, text input, or other types of input.

[0150] The authentication requesting device queries (step 703) the stored device portrait data. The authentication requesting device may optionally view the stored device portrait data, including device capability data and device status data.

[0151] The authentication requesting device (step 705) decides on the authentication device. The authentication requesting device decides based on one or more characteristics of the authentication request and one or more characteristics of the authentication device.

[0152] The authentication requesting device sends (step 707) an authentication request to the authentication responding device. In some possible implementations, the authentication requesting device sends the detected input data to the authentication responding device. In some possible implementations, the authentication requesting device sends the semantics corresponding to the detected data and the input data to the responding device.

[0153] The authentication response device performs (step 709) biometric authentication. The authentication response device authenticates the biometric characteristics of the input data received from the authentication request device through one or more components and returns (step 711) the authentication result.

[0154] In some possible implementations, the authentication requesting device sends authentication requests to multiple authentication responding devices, thereby receiving authentication results returned by the multiple devices. The authentication requesting device then determines (step 713) a final authentication result based on the multiple returned results.

[0155] The authentication response device outputs (step 715) an authentication result. The output authentication result may be the final authentication result of step 713, or an operation corresponding to the semantics of the input data executed according to the final authentication result.

[0156] The present application also provides an electronic device including one or more processors and one or more memories. The one or more memories are coupled to the one or more processors, and the one or more memories are used to store computer program code. The computer program code includes computer instructions. When the one or more processors execute the computer instructions, the electronic device executes the steps of the electronic device in the above method embodiment, thereby implementing the above cross-device authentication method.

[0157] An embodiment of the present application also provides a computer-readable storage medium, which stores computer instructions. When the computer instructions are executed on an electronic device, the electronic device executes the above-mentioned related method steps to implement the cross-device authentication method in the above-mentioned embodiment.

[0158] An embodiment of the present application further provides a computer program product, which, when executed on a computer, enables the computer to execute the aforementioned related steps to implement the cross-device authentication method performed by the electronic device in the aforementioned embodiment.

[0159] In addition, an embodiment of the present application also provides a device, which can specifically be a chip, component or module, and the device may include a connected processor and memory; wherein the memory is used to store computer-executable instructions, and when the device is running, the processor can execute the computer-executable instructions stored in the memory to enable the chip to execute the cross-device authentication method in the above-mentioned method embodiments.

[0160] Among them, the electronic device, computer-readable storage medium, computer program product or chip provided in this embodiment are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding methods provided above, and will not be repeated here.

[0161] Through the description of the above implementation methods, technical personnel in the relevant field can understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be distributed and completed by different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0162] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the modules or units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0163] The units described as separate components may or may not be physically separate, 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 distributed in multiple places. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0164] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0165] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0166] The above content is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A cross-device authentication method, applied to electronic devices, characterized in that: The method comprises: The first device receives an authentication request; The first device queries the stored device portrait; The first device determines a second device according to the device portrait, where the second device is an authentication response device; The first device sends first information to the second device, where the first information includes the authentication request and the user intention; The first device receives a first return result sent by the second device, where the first return result includes a result of the second device responding to the user's intention, and the first return result is obtained by the second device by identifying a biometric characteristic in the first information; The first device performs a corresponding operation according to the authentication request.

2. The method according to claim 1, characterized in that Before the first device performs a corresponding operation according to the authentication request, the method further includes: The first device sends the first information to a third device, where the first information includes the authentication request; The first device receives a second returned result sent by the third device, where the second returned result is obtained by the third device by identifying the biometric characteristic in the first information; The first device makes a decision according to the first returned result and the second returned result.

3. The method according to claim 1 or 2, characterized in that The device portrait includes device capabilities and device statuses of the first device, the second device, and the third device.

4. The method according to claim 1 or 2, characterized in that When the device state of the first device changes, the first device sends the device portrait to the second device and the third device.

5. The method according to claim 1 or 2, characterized in that The first device periodically sends the device portrait to the second device and the third device.

6. The method according to claim 1 or 2, characterized in that The first device, the second device, and the third device are logged in to the same account.

7. The method according to claim 1 or 2, characterized in that The first device, the second device and the third device are connected to the same wireless local area network.

8. The method according to claim 1 or 2, characterized in that The biometric characteristic includes at least one of the following: face, fingerprint, iris, retina, deoxyribonucleic acid DNA, skin, hand shape or vein, voice, signature or gait, gender, age, height or weight.

9. A cross-device authentication device, characterized in that: The device comprises a processor and a memory, wherein the memory is used to store computer-executable instructions. When the device is running, the processor can execute the computer-executable instructions stored in the memory, so that the electronic device performs the cross-device authentication method as described in any one of claims 1 to 8.

10. A computer-readable storage medium, characterized in that The method comprises computer instructions, which, when executed on an electronic device, enable the electronic device to execute the cross-device authentication method according to any one of claims 1 to 8.

11. A computer program product, characterized in that When the computer program product is run on a computer, the computer is caused to execute the cross-device authentication method according to any one of claims 1 to 8.

Images