Registration method and electronic equipment

Abstract

The invention provides a registration method and electronic equipment, and the method comprises the steps that first electronic equipment can carry out proxy registration through second electronic equipment which can communicate with a cloud end, so that the first electronic equipment carries out registration authentication with the cloud end; therefore, the electronic equipment which does not have the capability of communicating with the cloud can be registered to the cloud in a proxy registration mode and added into the trust ring.

Description

Technical Field

[0001] This application relates to the field of terminal devices, and in particular, to a registration method and an electronic device. Background Art

[0002] With the development of terminal technology and the widespread use of terminals, terminal devices can provide various services for users to meet their daily needs. The trust ring service enables multiple devices within the same ring to perform service transfers (such as notifications, incoming calls, etc.). For example, when a terminal device provides a call service for a user, if the user is inconvenient to make a call on this terminal, the user can transfer the above call to another terminal device to maintain the continuity of the call and meet the user's call needs. However, devices that cannot access the network, such as in-vehicle devices, cannot log in to an account due to their inability to connect to the network, and thus cannot connect to the cloud, and further cannot join the trust ring. Summary of the Invention

[0003] This application provides a registration method and an electronic device. In this method, the electronic device to be registered can be registered in the cloud through an electronic device that has already joined the trust ring to join the trust ring.

[0004] In a first aspect, this application provides a registration method, which includes: the first electronic device establishes a first communication connection with the second electronic device in response to a received first operation; the second electronic device performs data interaction with the cloud through a second communication connection, and the second electronic device belongs to the first trust ring; the first electronic device performs registration authentication with the cloud through the second electronic device; wherein, during the process of the first electronic device performing registration authentication with the cloud, the information sent by the first electronic device to the cloud is sent to the second electronic device through the first communication connection, and the second electronic device acts as an agent to send it to the cloud; the information sent by the cloud to the first electronic device is sent to the second electronic device through the second communication connection, and the second electronic device acts as an agent to send it to the first electronic device; after the first electronic device and the cloud successfully complete the registration authentication, the first electronic device obtains the first user information of the first trust ring. In this way, the electronic device to be registered can be proxy-registered through an electronic device that has already joined the trust ring and can communicate with the cloud, enabling devices without networking capabilities to also be registered to the cloud and thus join the trust ring.

[0005] Exemplarily, the user information includes but is not limited to: the username and user ID within the trust ring.

[0006] Exemplarily, the trust ring is optionally a device with the same username and user ID. And devices within the same trust ring can perform service transfers through self-networking between devices (i.e., communication connections, which can be Bluetooth, Wi-Fi, etc.).

[0007] In a possible implementation, the first electronic device registers and authenticates with the cloud, including: during the process of the first electronic device registering and authenticating with the cloud, the first electronic device sends the public key information and identification information of the first electronic device to the cloud through the second electronic device. In this way, after the cloud obtains the public key information of the first electronic device, other electronic devices within the trust ring can pull the public key information and identification information of the first electronic device from the cloud, so as to receive the broadcast of the first electronic device based on the identification information and authenticate with the first electronic device based on the public key information. In addition, the cloud adds the identification information of the first electronic device to the device information corresponding to the trust ring to indicate that the first electronic device has joined the trust ring.

[0008] In a possible implementation, the method further includes: the first electronic device establishes a communication connection with at least one electronic device within the first trust ring based on the first user information. In this way, after the first electronic device registers with the cloud, joins the trust ring, and obtains the user information, it can establish a communication connection with the same trust ring, which can also be understood as electronic devices with the same user information (i.e., the ad hoc network described in this application).

[0009] In a possible implementation, the method further includes: the first electronic device conducts service transfer with at least one electronic device. In this way, within the same trust ring and devices that have established communication connections with each other, multi-device service interactions can be carried out, such as service transfer.

[0010] In a possible implementation, the first electronic device establishing a communication connection with at least one electronic device within the first trust ring based on the first user information includes: the first electronic device sends a Bluetooth broadcast message, which includes the identification information and the first user information of the first electronic device; the first electronic device authenticates with at least one electronic device that receives the Bluetooth broadcast message. During the authentication process, at least one electronic device obtains the public key information of the first electronic device from the cloud and authenticates with the first electronic device based on the public key information; after the first electronic device successfully authenticates with at least one electronic device, it establishes a communication connection with at least one electronic device. In this way, after an electronic device without an Internet connection is successfully registered through the proxy of an electronic device within the trust ring, it can establish a communication connection with other electronic devices within the trust ring based on the obtained user information, that is, send a Bluetooth broadcast carrying the user information, so that other online devices within the trust ring can discover the electronic device and establish a connection.

[0011] In a possible implementation, after the first electronic device successfully registers and authenticates with the cloud, the first electronic device obtains the first user information of the first trust ring, including: the first electronic device receives the registration success information sent by the second electronic device, and the registration success information is used to indicate that the vehicle-mounted device has successfully registered with the cloud and joined the first trust ring, and the registration success information includes the first user information. In this way, after the first electronic device determines that the second electronic device has successfully registered, it can send the user information (including the user name and user ID) stored at its end to the second electronic device, so that the second electronic device has the same user name and user ID as the first electronic device.

[0012] In a possible implementation, the method further includes: the first electronic device establishes a third communication connection with the third electronic device in response to the received second operation; the third electronic device performs data interaction with the cloud through a fourth communication connection, and the third electronic device belongs to the second trust ring; the first electronic device performs registration authentication with the cloud through the third electronic device;; wherein, during the process of the first electronic device performing registration authentication with the cloud, the information sent by the first electronic device to the cloud is sent to the third electronic device through the third communication connection, and the third electronic device acts as an agent to send it to the cloud on behalf of the first electronic device; the information sent by the cloud to the first electronic device is sent to the third electronic device through the fourth communication connection, and the third electronic device acts as an agent to send it to the first electronic device on behalf of the cloud; after the first electronic device successfully registers and authenticates with the cloud, the first electronic device obtains the second user information of the second trust ring. In this way, the first electronic device can also perform proxy registration through the electronic devices in other trust rings to join more trust rings.

[0013] In a possible implementation, the method further includes: the first electronic device switches from the first trust ring to the second trust ring in response to the received third operation, and establishes a communication connection with at least one electronic device within the second trust ring.

[0014] In a possible implementation, the first communication connection is a Bluetooth connection.

[0015] Second aspect, the present application provides an electronic device, including: one or more processors, a memory; and one or more computer programs, wherein the one or more computer programs are stored on the memory, and when the computer programs are executed by the one or more processors, the electronic device is caused to perform the following steps: the first electronic device establishes a first communication connection with the second electronic device in response to a received first operation; the second electronic device performs data interaction with the cloud through a second communication connection, and the second electronic device belongs to the first trust ring; the first electronic device performs registration authentication with the cloud through the second electronic device; wherein, during the process of the first electronic device performing registration authentication with the cloud, the information sent by the first electronic device to the cloud is sent to the second electronic device through the first communication connection, and the second electronic device acts as an agent to send it to the cloud; the information sent by the cloud to the first electronic device is sent to the second electronic device through the second communication connection, and the second electronic device acts as an agent to send it to the first electronic device; after the first electronic device and the cloud succeed in registration authentication, the first electronic device obtains the first user information of the first trust ring.

[0016] In a possible implementation manner, when the computer programs are executed by the one or more processors, the electronic device is caused to perform the following steps: during the process of the first electronic device performing registration authentication with the cloud, the first electronic device sends the public key information of the first electronic device and the identification information of the first electronic device to the cloud through the second electronic device.

[0017] In a possible implementation manner, when the computer programs are executed by the one or more processors, the electronic device is caused to perform the following steps: the first electronic device establishes a communication connection with at least one electronic device within the first trust ring based on the first user information.

[0018] In a possible implementation manner, when the computer programs are executed by the one or more processors, the electronic device is caused to perform the following steps: the first electronic device performs service transfer with at least one electronic device.

[0019] In a possible implementation manner, when the computer programs are executed by the one or more processors, the electronic device is caused to perform the following steps: the first electronic device sends a Bluetooth broadcast message, and the Bluetooth broadcast message includes the identification information of the first electronic device and the first user information; the first electronic device authenticates with at least one electronic device that receives the Bluetooth broadcast message, wherein, during the authentication process, at least one electronic device obtains the public key information of the first electronic device from the cloud and authenticates with the first electronic device based on the public key information; after the first electronic device and at least one electronic device succeed in authentication, a communication connection is established with at least one electronic device.

[0020] In a possible implementation, when the computer program is executed by one or more processors, the electronic device is caused to perform the following steps: The first electronic device receives the registration success information sent by the second electronic device. The registration success information is used to indicate that the in-vehicle device has successfully registered to the cloud and joined the first trust ring. The registration success information includes the first user information.

[0021] In a possible implementation, when the computer program is executed by one or more processors, the electronic device is caused to perform the following steps: The first electronic device establishes a third communication connection with the third electronic device in response to the received second operation; Data interaction is performed between the third electronic device and the cloud through a fourth communication connection. The third electronic device belongs to the second trust ring; The first electronic device performs registration authentication with the cloud through the third electronic device;; Wherein, during the process of the first electronic device performing registration authentication with the cloud, the information sent by the first electronic device to the cloud is sent to the third electronic device through the third communication connection, and the third electronic device forwards it to the cloud on behalf of the first electronic device; The information sent by the cloud to the first electronic device is sent to the third electronic device through the fourth communication connection, and the third electronic device forwards it to the first electronic device on behalf of the cloud; After the first electronic device and the cloud successfully complete the registration authentication, the first electronic device obtains the second user information of the second trust ring.

[0022] In a possible implementation, when the computer program is executed by one or more processors, the electronic device is caused to perform the following steps: The first electronic device switches from the first trust ring to the second trust ring in response to the received third operation, and establishes a communication connection with at least one electronic device within the second trust ring.

[0023] In a third aspect, the present application provides a computer-readable medium for storing a computer program, the computer program including instructions for performing the method in the first aspect or any possible implementation of the first aspect.

[0024] In a fourth aspect, the present application provides a computer program, the computer program including instructions for performing the method in the first aspect or any possible implementation of the first aspect.

[0025] In a fifth aspect, the present application provides a chip, the chip including a processing circuit and transceiver pins. Wherein, the transceiver pins and the processing circuit communicate with each other through an internal connection path. The processing circuit performs the method in the first aspect or any possible implementation of the first aspect to control the receive pin to receive a signal and control the transmit pin to send a signal.

[0026] In a sixth aspect, the present application provides a registration system, the system including the first electronic device, the second electronic device, and the cloud involved in the first aspect and the second aspect above. Description of the Drawings

[0027] Figure 1 Schematic diagram of an exemplary application scenario;

[0028] Figure 2 Schematic diagram of the hardware structure of an exemplary electronic device;

[0029] Figure 3 Schematic diagram of the software structure of an exemplary electronic device;

[0030] Figure 4 Schematic diagram of the hardware structure of an exemplary electronic device;

[0031] Figure 5 Schematic diagram of the software structure of an exemplary electronic device;

[0032] Figure 6 Schematic diagram of the overall process;

[0033] Figure 7 Schematic diagram of the near - field registration process;

[0034] Figures 8A - 8B Schematic diagram of the user interface;

[0035] Figure 9 Schematic diagram of the Bluetooth connection;

[0036] Figures 10A - 10B Schematic diagram of the user interface;

[0037] Figure 11 Schematic diagram of the proxy registration process;

[0038] Figure 12 Schematic diagram of the interactive registration information process;

[0039] Figure 13 Schematic diagram of the user interface;

[0040] Figure 14 Schematic diagram of the online device authentication process;

[0041] Figure 15 Schematic diagram of the offline device authentication process;

[0042] Figure 16 Schematic diagram of the user interface;

[0043] Figure 17 Schematic diagram of the structure of the device. Detailed implementation manners

[0044] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in the present application without making creative efforts shall fall within the protection scope of the present application.

[0045] The term "and / or" in this document is merely a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B may represent three situations: A exists alone, A and B exist simultaneously, and B exists alone.

[0046] The terms "first", "second", etc. in the description and claims of the embodiments of the present application are used to distinguish different objects, rather than to describe a specific order of the objects. For example, the first target object and the second target object are used to distinguish different target objects, rather than to describe a specific order of the target objects.

[0047] In the embodiments of the present application, words such as "exemplary" or "for example" are used to represent examples, illustrations or explanations. Any embodiment or design solution described as "exemplary" or "for example" in the embodiments of the present application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Rather, the use of words such as "exemplary" or "for example" is intended to present relevant concepts in a specific manner.

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

[0049] In the embodiments of the present application, the terminal device may be a device with an Internet access function such as a mobile phone, a tablet computer, a wearable device, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a personal digital assistant (PDA), etc. with a shooting function, and may also be understood as a device that can be connected to the cloud. The device to be registered may be a device with near-field communication capabilities (such as Bluetooth, Wi-Fi, ZigBee, etc.) but without an Internet access function (i.e., unable to connect to the cloud), such as a vehicle-mounted device, an augmented reality (AR) / virtual reality (VR) device, a smart home device, etc.

[0050] In the following embodiments of this application, the term "user interface (UI)" refers to a media interface for interaction and information exchange between an application or an operating system and a user. It realizes the conversion between the internal form of information and the form acceptable to the user. The user interface is source code written in specific computer languages such as Java and Extensible Markup Language (XML). The interface source code is parsed and rendered on a mobile device or an electronic device, and finally presented as content recognizable by the user. The common manifestation form of the user interface is the graphical user interface (GUI), which refers to the user interface related to computer operations displayed in a graphical manner. It can be visual interface elements such as text, icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, and Widgets displayed on the display screen of a mobile device or an electronic device.

[0051] In the embodiments of this application, multiple electronic devices within the same trust ring can perform service transfer through wireless connections (including but not limited to Bluetooth, Wi-Fi, etc.), such as video sharing, audio sharing, incoming call sharing, etc., which can also be referred to as video service transfer, audio service transfer, incoming call service transfer (or call service transfer), etc. Among them, a mobile device (such as a mobile phone) can also be referred to as an output end or a source end, and an electronic device (such as a vehicle-mounted device) can also be referred to as an input end or a receiving end (sink end).

[0052] Figure 1 For an exemplary schematic diagram of an application scenario. Please refer to Figure 1 , in this scenario, mobile phone A and the vehicle-mounted device perform collaborative services. For example, mobile phone A transfers the video played on mobile phone A to the vehicle-mounted device for continuous playback. During the process of performing collaborative services between mobile phone A and the vehicle-mounted device, mobile phone B responds to the received user operation and performs incoming call sharing with the vehicle-mounted device, that is, transfers the call on mobile phone B to the vehicle-mounted device for answering.

[0053] This application provides a registration method. An electronic device (such as Figure 1 mobile phone A in Figure 1 ) can be used as an agent device to provide an agent registration function for an unaccounted device to be registered (which can also be understood as a device that cannot log in to the cloud to register an account, such as

[0054] Figure 2 The structure diagram of electronic device 100 is shown. It should be understood that Figure 2The illustrated electronic device 100 is merely an example of an electronic device, and the electronic device 100 may have more or fewer components than those shown in the figure, may combine two or more components, or may have a different component configuration. Figure 2 The various components shown in Figure 2 may be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application specific integrated circuits.

[0055] 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 170, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone interface 170D, a sensor module 180, a key 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc.

[0056] The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (AP), a modem processor (Modem), a graphics processing unit (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Among them, different processing units may be independent devices or may be integrated in one or more processors.

[0057] Among them, the controller may be the nerve center and command center of the electronic device 100. The controller may generate operation control signals according to the instruction operation code and timing signal to complete the control of fetching and executing instructions.

[0058] A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory can hold the instructions or data that the processor 110 has just used or recycled. If the processor 110 needs to use the instruction or data again, it can directly call it from the said memory. This avoids repeated accesses and reduces the waiting time of the processor 110, thus improving the efficiency of the system.

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

[0060] The I2C interface is a bidirectional synchronous serial bus, including a serial data line (SDA) and a serial clock line (SCL). In some embodiments, the processor 110 may include multiple groups of I2C buses. The processor 110 can be respectively coupled to the touch sensor 180K, the charger, the flash, the camera 193, etc. through different I2C bus interfaces. For example: the processor 110 can be coupled to the touch sensor 180K through the I2C interface, enabling the processor 110 to communicate with the touch sensor 180K through the I2C bus interface to implement the touch function of the electronic device 100.

[0061] The I2S interface can be used for audio communication. In some embodiments, the processor 110 may include multiple groups of I2S buses. The processor 110 can be coupled to the audio module 170 through the I2S bus to implement communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 can transmit an audio signal to the wireless communication module 170 through the I2S interface to implement the function of answering a phone call through a Bluetooth headset.

[0062] The PCM interface can also be used for audio communication to sample, quantize, and encode analog signals. In some embodiments, the audio module 170 and the wireless communication module 170 can be coupled through the PCM bus interface. In some embodiments, the audio module 170 can also transmit audio signals to the wireless communication module 170 through the PCM interface to implement the function of answering calls through a Bluetooth headset. Both the I2S interface and the PCM interface can be used for audio communication.

[0063] The UART interface is a general-purpose serial data bus for asynchronous communication. This bus can be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, the UART interface is typically used to connect the processor 110 and the wireless communication module 170. For example, the processor 110 communicates with the Bluetooth module in the wireless communication module 170 through the UART interface to implement the Bluetooth function. In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 170 through the UART interface to implement the function of playing music through a Bluetooth headset.

[0064] The MIPI interface can be used to connect the processor 110 to peripheral devices such as the display screen 194 and the camera 193. The MIPI interface includes a camera serial interface (CSI), a display serial interface (DSI), etc. In some embodiments, the processor 110 and the camera 193 communicate through the CSI interface to implement the shooting function of the electronic device 100. The processor 110 and the display screen 194 communicate through the DSI interface to implement the display function of the electronic device 100.

[0065] The GPIO interface can be configured by software. The GPIO interface can be configured as a control signal or as a data signal. In some embodiments, the GPIO interface can be used to connect the processor 110 to the camera 193, the display screen 194, the wireless communication module 170, the audio module 170, the sensor module 180, etc. The GPIO interface can also be configured as an I2C interface, an I2S interface, a UART interface, a MIPI interface, etc.

[0066] The USB interface 130 is an interface that complies with the USB standard specification and can specifically be a Mini USB interface, a Micro USB interface, a USB Type C interface, etc. The USB interface 130 can be used to connect a charger to charge the electronic device 100, and can also be used for data transmission between the electronic device 100 and peripheral devices. It can also be used to connect headphones to play audio. This interface can also be used to connect other electronic devices, such as AR devices, etc.

[0067] It can be understood that the interface connection relationships between the modules illustrated in the embodiments of the present application are only illustrative descriptions and do not constitute a structural limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may also adopt different interface connection manners in the above embodiments, or a combination of multiple interface connection manners.

[0068] The charging management module 140 is used to receive a charging input from a charger. Among them, the charger may be a wireless charger or a wired charger. In some embodiments of wired charging, the charging management module 140 may receive the charging input of the wired charger through the USB interface 130. In some embodiments of wireless charging, the charging management module 140 may receive the wireless charging input through the wireless charging coil of the electronic device 100. While charging the battery 142, the charging management module 140 may also supply power to the electronic device through the power management module 141.

[0069] 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 the inputs from the battery 142 and / or the charging management module 140 and supplies power to the processor 110, the internal memory 121, the external memory, the display screen 194, the camera 193, the wireless communication module 170, etc. The power management module 141 may also be used to monitor parameters such as the battery capacity, the number of battery cycles, and the battery health status (leakage, impedance). In some other embodiments, the power management module 141 may also be disposed in the processor 110. In other embodiments, the power management module 141 and the charging management module 140 may also be disposed in the same device.

[0070] The wireless communication function of the electronic device 100 may be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 170, the modulation and demodulation processor, and the baseband processor, etc.

[0071] The antenna 1 and the antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in the electronic device 100 may be used to cover a single or multiple communication frequency bands. Different antennas may also be multiplexed to improve the utilization rate of the antennas. For example, the antenna 1 may be multiplexed as the diversity antenna of the wireless local area network. In some other embodiments, the antenna may be used in combination with a tuning switch.

[0072] The mobile communication module 150 may provide a solution for wireless communication including 2G / 3G / 4G / 5G, etc., which is applied to the electronic device 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 may receive an electromagnetic wave through the antenna 1, perform processing such as filtering and amplification on the received electromagnetic wave, and transmit it to the modulation and demodulation processor for demodulation. The mobile communication module 150 may also amplify the signal modulated by the modulation and demodulation processor and convert it into an electromagnetic wave through the antenna 1 for radiation. In some embodiments, at least some functional modules of the mobile communication module 150 may be provided in the processor 110. In some embodiments, at least some functional modules of the mobile communication module 150 and at least some modules of the processor 110 may be provided in the same device.

[0073] The modulation and demodulation processor may include a modulator and a demodulator. Among them, the modulator is used to modulate the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. Subsequently, the demodulator transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After being processed by the baseband processor, the low-frequency baseband signal is transmitted to the application processor. The application processor outputs a sound signal through an audio device (not limited to the speaker 170A, receiver 170B, etc.), or displays an image or video through the display screen 194. In some embodiments, the modulation and demodulation processor may be an independent device. In other embodiments, the modulation and demodulation processor may be independent of the processor 110 and be provided in the same device as the mobile communication module 150 or other functional modules.

[0074] The wireless communication module 170 may provide solutions for wireless communications applied to the electronic device 100, including wireless local area networks (WLANs) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite systems (GNSSs), frequency modulation (FM), near field communication (NFC), infrared (IR), etc. The wireless communication module 170 may be one or more devices integrating at least one communication processing module. The wireless communication module 170 receives electromagnetic waves via the antenna 2, performs frequency modulation and filtering processing on the electromagnetic wave signals, and sends the processed signals to the processor 110. The wireless communication module 170 may also receive signals to be sent from the processor 110, perform frequency modulation and amplification on them, and convert them into electromagnetic waves through the antenna 2 for radiation.

[0075] In some embodiments, antenna 1 of electronic device 100 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 170, so that electronic device 100 can communicate with a network and other devices through wireless communication technologies. The wireless communication technologies 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 technologies, etc. The GNSS may include global positioning system (GPS), global navigation satellite system (GLONASS), beidou navigation satellite system (BDS), quasi-zenith satellite system (QZSS), and / or satellite based augmentation systems (SBAS).

[0076] Electronic device 100 implements a display function through a GPU, display screen 194, and an application processor, etc. The GPU is a microprocessor for image processing, and is connected to display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs, which execute program instructions to generate or change display information.

[0077] The display screen 194 is used to display images, videos, etc. The 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 (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, the electronic device 100 may include one or N display screens 194, where N is a positive integer greater than 1.

[0078] The electronic device 100 can implement the shooting function through the ISP, the camera 193, the video codec, the GPU, the display screen 194, and the application processor, etc.

[0079] The ISP is used to process the data fed back by the camera 193. For example, when taking a photo, the shutter is opened, and light passes through the lens and is transmitted to the camera sensor. The light signal is converted into an electrical signal, and the camera sensor transmits the electrical signal to the ISP for processing and converts it into an image visible to the naked eye. The ISP can also perform algorithm optimization on the noise, brightness, and skin color of the image. The ISP can also optimize parameters such as the exposure and color temperature of the shooting scene. In some embodiments, the ISP can be set in the camera 193.

[0080] The camera 193 is used to capture static images or videos. An object generates an optical image through the lens and projects it onto the sensor. The sensor can be a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The sensor converts the light signal into an electrical signal, and then transmits the electrical signal to the ISP to convert it 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 standard RGB, YUV, etc. formats. In some embodiments, the electronic device 100 may include one or N cameras 193, where N is a positive integer greater than 1.

[0081] 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, etc.

[0082] The video codec is used to compress or decompress digital videos. The electronic device 100 can support one or more video codecs. In this way, the electronic device 100 can play or record videos in multiple coding formats, such as: Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

[0083] The NPU is a neural-network (NN) computing processor. By learning from the biological neural network structure, such as learning from the transmission mode between human brain neurons, it can quickly process the input information and can also continuously self-learn. Through the NPU, applications such as intelligent cognition of the electronic device 100 can be realized, such as: image recognition, face recognition, speech recognition, text understanding, etc.

[0084] 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 100. The external memory card communicates with the processor 110 through the external memory interface 120 to achieve the data storage function. For example, files such as music and videos are saved in the external memory card.

[0085] The internal memory 121 can be used to store computer-executable program code, and the executable program code includes 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 can include a program storage area and a data storage area. Among them, the program storage area can store the operating system, application programs required for at least one function (such as the sound playback function, the image playback function, etc.). The data storage area can store the data created during the use of the electronic device 100 (such as audio data, phone book, etc.). In addition, the internal memory 121 can include high-speed random access memory and can also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc.

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

[0087] The audio module 170 is used to convert digital audio information into an analog audio signal for output, and is also used to convert an analog audio input into a digital audio signal. The audio module 170 can also be used for encoding and decoding audio signals. In some embodiments, the audio module 170 can be disposed in the processor 110, or some functional modules of the audio module 170 can be disposed in the processor 110.

[0088] The speaker 170A, also known as the "loudspeaker", is used to convert an audio electrical signal into a sound signal. The electronic device 100 can listen to music or hands-free calls through the speaker 170A.

[0089] The receiver 170B, also known as the "earpiece", is used to convert an audio electrical signal into a sound signal. When the electronic device 100 answers a call or a voice message, the user can listen to the voice by bringing the receiver 170B close to the ear.

[0090] The microphone 170C, also known as the "microphone" or "transmitter", is used to convert a sound signal into an electrical signal. When making a call or sending a voice message, the user can speak by bringing the mouth close to the microphone 170C to input the sound signal into the microphone 170C. The electronic device 100 can be provided with at least one microphone 170C. In some other embodiments, the electronic device 100 can be provided with two microphones 170C, which can not only collect sound signals but also implement a noise reduction function. In some other embodiments, the electronic device 100 can also be provided with three, four or more microphones 170C, which can collect sound signals, reduce noise, identify the sound source, and implement functions such as directional recording.

[0091] The headphone jack 170D is used to connect a wired headphone. The headphone jack 170D can be a USB interface 130, or a 3.5 mm open mobile terminal platform (OMTP) standard interface, or a cellular telecommunications industry association of the USA (CTIA) standard interface.

[0092] The SIM card interface 195 is used to connect to a SIM card. The SIM card can be inserted into or removed from the SIM card interface 195 to achieve contact and separation from the electronic device 100. The electronic device 100 can support one or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 195 can support Nano SIM cards, Micro SIM cards, SIM cards, etc. Multiple cards can be inserted into the same SIM card interface 195 simultaneously. The types of the multiple cards can be the same or different. The SIM card interface 195 can also be compatible with different types of SIM cards. The SIM card interface 195 can also be compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to implement functions such as calls and data communication. In some embodiments, the electronic device 100 uses an eSIM, that is, an embedded SIM card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100.

[0093] The software system of the electronic device 100 can adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservices architecture, or a cloud architecture. In the embodiments of this application, the Android system with a layered architecture is taken as an example to exemplarily illustrate the software structure of the electronic device 100.

[0094] Figure 3 It is the software structure block diagram of the electronic device 100 in the embodiments of this application. The layered architecture of the electronic device 100 divides the software into several layers, and each layer has a clear role and division of labor. The layers communicate with each other through software interfaces. In some embodiments, from top to bottom, it includes but is not limited to: the application layer, the framework layer, the HAL layer, and the kernel layer.

[0095] The application layer can include a series of application program packages. As Figure 3 shown, the application program packages can include but are not limited to: application programs such as device management, device registration, discovery and connection, and in-vehicle applications.

[0096] The framework layer provides application programming interfaces (APIs) and programming frameworks for the application programs in the application layer. The application framework layer includes some predefined functions.

[0097] As Figure 3 shown, the framework layer can include but is not limited to: window manager, content provider, view system, distributed mobile sensing development platform (DMSDP) service, etc.

[0098] The window manager is used to manage window programs. The window manager can obtain the display screen size, determine whether there is a status bar, lock the screen, capture the screen, etc.

[0099] The content provider is used to store and obtain data, and make this data accessible to application programs. The data may include videos, images, audio, incoming and outgoing calls, browsing history and bookmarks, phone books, etc.

[0100] The view system includes visual controls, such as controls for displaying text, controls for displaying pictures, etc. The view system can be used to build application programs. The display interface can be composed of one or more views. For example, a display interface including a short message notification icon may include a view for displaying text and a view for displaying pictures.

[0101] The DMSDP service is used to provide virtualization services.

[0102] The kernel layer is the layer between hardware and software. The kernel layer at least includes a display driver, a camera driver, an audio driver, and a sensor driver.

[0103] It can be understood that Figure 3 The layers in the shown software structure and the components included in each layer do not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may include more or fewer layers than shown, and each layer may include more or fewer components, which are not limited in the present application.

[0104] Figure 4 It is the hardware structure of the exemplary electronic device 200. As Figure 4 shown, the electronic device 200 may include: a video codec 221, a processor 222, a memory 223, a wireless communication processing module 224, a power switch 225, a high definition multimedia interface (HDMI) communication processing module 227, a USB communication processing module 228, a display screen 229, and an audio module 230. Each module can be connected through a bus. Among them: The processor 222 can be used to read and execute computer-readable instructions. In a specific implementation, the processor 222 mainly includes a controller, an arithmetic unit, and registers. Among them, the controller is mainly responsible for instruction decoding and sending control signals for the operations corresponding to the instructions. The arithmetic unit is mainly responsible for performing fixed-point or floating-point arithmetic operations, shift operations, and logical operations, etc., and can also perform address operations and conversions. The registers are mainly responsible for storing register operands and intermediate operation results temporarily stored during the execution of instructions, etc. In a specific implementation, the hardware architecture of the processor 222 can be an application-specific integrated circuit (ASIC) architecture, a MIPS architecture, an ARM architecture, or an NP architecture, etc.

[0105] The wireless communication processing module 224 may include a Wi-Fi communication processing module 224A, and may also include communication modules such as a Bluetooth (BT) communication processing module 224B and an NFC processing module 224C.

[0106] In some embodiments, the wireless communication processing module 224 may be used to establish a communication connection with the mobile device 100, and receive the encoded data sent by the mobile device 100 based on this communication connection. For example, the Wi-Fi communication processing module 224A may be used to establish a Wi-Fi direct connection communication connection with the mobile device 100, the Bluetooth (BT) communication processing module 224B may be used to establish a Bluetooth communication connection with the mobile device 200, and the NFC processing module 224C may be used to establish an NFC connection with the mobile device 100, etc. That is, the wireless communication processing module 224 may support sharing of multimedia content between the mobile device 100 and the mobile device 200 through mirroring projection (such as Miracast).

[0107] In one implementation, the wireless communication processing module 224 may detect signals such as probe requests and scan signals emitted by the mobile device 100, discover the mobile device 100, and establish a communication connection with the mobile device 100. In another implementation, the wireless communication processing module 224 may also emit signals such as probe requests and scan signals, so that the electronic device 200 can discover the mobile device 100 and establish a communication connection with the mobile device 100 (such as a Wi-Fi P2P connection).

[0108] In some embodiments, when sharing multimedia content between the mobile device 100 and the electronic device 200 through mirroring projection (such as Miracast), the wireless communication processing module 224 (such as the Wi-Fi communication processing module 224A) may also receive the scene notified by the mobile device 100. The processor 222 may parse and learn this scene, adaptively select a playback strategy corresponding to this scene, and use this playback strategy to call modules such as the display screen 229 and the audio module 230 to play the multimedia content sent by the mobile device 100.

[0109] The video codec 221 is used to compress or decompress digital video. In the embodiments of the present application, the video codec 221 can decompress multimedia content from the mobile device 100 or the server 400. The electronic device 200 can support one or more video codecs and can play videos in one or more coding formats. For example: MPEG1, MPEG2, MPEG3, MPEG4, etc. The processor 222 can be used to parse signals received by the wireless communication processing module 224, such as the probe request broadcast by the electronic device 200, etc. The processor 222 can be used to perform corresponding processing operations according to the parsing results, such as generating a probe response, etc. The processor 222 can be used to drive the display screen 229 to perform display according to the decompression result of the video codec 221.

[0110] The memory 223 is coupled to the processor 222 and is used to store various software programs and / or multiple sets of instructions. In a specific implementation, the memory 223 can include high-speed random access memory and can also include non-volatile memory, such as one or more disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory 223 can store operating systems, such as embedded operating systems like uCOS, VxWorks, RTLinux, Harmony, Android, etc. The memory 223 can also store a communication program, which can be used to communicate with the electronic device 200, one or more servers, or additional devices.

[0111] The power switch 225 can be used to control the power supply to the electronic device 200.

[0112] The HDMI communication processing module 227 can be used to communicate with other devices through an HDMI interface (not shown).

[0113] The USB communication processing module 228 can be used to communicate with other devices through a USB interface (not shown).

[0114] The display screen 229 can be used to display images, videos, etc. The display screen 229 can adopt display screens such as LCD, OLED, AMOLED, FLED, QLED, etc. The content displayed on the display screen 229 can refer to the relevant descriptions of the subsequent method embodiments. The audio module 230 can be used to output an audio signal through an audio output interface, so that the electronic device 200 supports audio playback. The audio module 230 can also be used to receive audio data through an audio input interface. The audio module 230 can include but is not limited to: microphones, speakers, receivers, etc.

[0115] In some embodiments, the electronic device 200 may further include a serial interface such as an RS-232 interface. This serial interface can be connected to other devices, such as an audio external device like a speaker, enabling the display and the audio external device to cooperate in playing audio and video. It can be understood that Figure 4 The schematic structure does not constitute a specific limitation on the electronic device 200. In other embodiments of the present application, the electronic device 200 may include more or fewer components than shown, or combine certain components, or split certain components, or have different component arrangements. The illustrated components can be implemented in hardware, software, or a combination of software and hardware.

[0116] Figure 5 It is a schematic diagram of the software structure of the exemplary electronic device 200 shown. The software system of the electronic device 200 can adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservices architecture, or a cloud architecture, etc. Exemplarily, the software system of the electronic device 200 includes but is not limited to Linux or other operating systems.

[0117] Please refer to Figure 5 , the application layer of the software system of the electronic device 200 may include services such as DMSDP, a music application, a call application, a collaboration application, etc. The DMSDP service includes but is not limited to: a concurrent caching module, a virtualization capability module, a concurrent management module, and a concurrent information interaction module. For specific descriptions, please refer to Figure 3 the relevant content, which will not be elaborated here.

[0118] The kernel layer of the electronic device 200 may include but is not limited to: a display driver, an audio driver, a Wi-Fi driver, a Bluetooth driver, and a sensor driver, etc.

[0119] Figure 6 It is a schematic diagram of the overall process shown for example. Please refer to Figure 6 , the technical solution in the embodiment of the present application is mainly divided into three parts. The first part is near-field registration, the second part is proxy registration, and the third part is trust ring authentication. In the first part, the in-vehicle device (i.e., the electronic device to be registered) and the mobile phone (i.e., the proxy registration electronic device) perform a first authentication to verify the device legality. Among them, after the in-vehicle device and the mobile phone perform the first authentication, the mobile phone can obtain the fingerprint information of the in-vehicle device, and subsequently, there is no need to execute the near-field registration process anymore. In the second part, the mobile phone, as a proxy registration device, provides a proxy registration service for the in-vehicle device to register the in-vehicle device to the cloud. In the third part, other electronic devices within the same trust ring as the mobile phone (which can also be understood as having the same user account as the mobile phone) can obtain the device information of the in-vehicle device from the cloud and establish a trust relationship with the in-vehicle device through near-field communication.

[0120] The following will separately elaborate on the above three parts in detail.

[0121] Part 1: Near-Field Registration

[0122] Figure 7 For the schematic diagram of the exemplary near-field registration process, please refer to Figure 7 , which specifically includes but is not limited to the following steps:

[0123] S701, the in-vehicle application sends a registration instruction to the device management.

[0124] Exemplarily, in response to the received user operation, the in-vehicle application determines to start the proxy registration process and sends a registration instruction to the device management (which can also be referred to as the device management module or device management application, and this application does not make a limitation), for instructing to start the proxy registration process, and can also be understood as for instructing to start the proxy registration function.

[0125] Figure 8A For the schematic diagram of the exemplary user interface, please refer to Figure 8A , the in-vehicle display interface 801 includes but is not limited to: the mobile phone interconnection control 802, the interconnection setting control, etc. The user clicks the mobile phone interconnection control 802, and the in-vehicle device, in response to the received user operation, displays the mobile phone interconnection interface 803 in the display interface 801, which can also be called the proxy registration interface. The mobile phone interconnection interface 803 includes but is not limited to the connection option 804. The user can click the connection option 804 to trigger the proxy registration process.

[0126] Exemplarily, the in-vehicle application triggers the proxy registration process, that is, sends a registration instruction to the device management. And, as Figure 8B shown, the in-vehicle application generates a PIN code (which can also be called a connection code), and this connection code is a randomly generated number. The in-vehicle application displays the connection code display box 805 and displays the generated PIN code in this display box.

[0127] S702, the device management sends an instruction to start the proxy registration service to the device registration.

[0128] Exemplarily, the device management sends an instruction to start the proxy registration service to the device registration, for instructing to start the proxy registration service, and can also be understood as for instructing to start the Session Server (session service) described below. Specifically, the device registration provides a proxy registration service interface, and the device management sending an instruction to start the proxy registration service to the device registration is to call this proxy registration service interface to send an instruction to start the proxy registration service to the device registration.

[0129] S703, the device registration instructs to discover the connection and start the Session Server.

[0130] Exemplarily, in response to the received indication to start the proxy registration service, the device registration invokes the proxy registration service function to start the proxy registration service. Moreover, the device registration indicates the discovery of the connection to start the Session Sever. The SessionServer is used to monitor the Bluetooth service. After the Session Server is started, it monitors the information obtained by the electronic device through the Bluetooth connection. It can also be understood that the vehicle-mounted device can monitor the Bluetooth service through the Session Sever corresponding to the proxy registration service.

[0131] S704, discover the connection to start the Session Sever and establish a Bluetooth connection with the mobile phone.

[0132] Specifically, in response to the indication of the device registration, the discovery of the connection starts the Session Sever. For example, it invokes the Session Server function. The discovery of the connection can monitor the Bluetooth service through the Session Sever to obtain the required data. Moreover, the Session Server is a kind of session service. During the period when the vehicle-mounted device maintains the Session Server, it can maintain sessions with other devices, such as Bluetooth session connections, etc., which are not limited in this application.

[0133] Exemplarily, Figure 9 For the schematically shown Bluetooth connection diagram for exemplary illustration, please refer to Figure 9 , including but not limited to the following steps:

[0134] S901, the vehicle-mounted device receives a user operation.

[0135] Exemplarily, as described above, after the vehicle-mounted device receives a user operation, it can start the Session Server. The Session Server can register with the Nearby service. Among them, the application registering with the Nearby service can be understood as that the application expects the Nearby service to provide corresponding services during the application's use. For example, as described above, the use of the registration proxy service requires the Bluetooth function to be turned on. It can also be understood that the service capabilities supported by the proxy registration service include the Bluetooth function. The Session Server can register with the Nearby service and request to call the Bluetooth function during its use.

[0136] Exemplarily, the Nearby service can detect the start of the Session Server through the interface, which can also be understood as the start of the proxy registration service.

[0137] S902, the vehicle-mounted device sends a Discovery Request (discovery request) message.

[0138] Exemplarily, after the Nearby service determines that the proxy registration service has started, the scanning phase can be executed. Optionally, the Nearby service can call the underlying module or chip. For example, the Nearby service can call the D2D service to enable the D2D service to initiate the Bluetooth connection establishment process. Optionally, the D2D service can further call the D2D driver to enable the D2D driver to control the Bluetooth chip to broadcast Discovery Request messages in real time or periodically.

[0139] It should be noted that in the embodiments of the present application, the Bluetooth communication between devices, such as the Bluetooth communication between a vehicle-mounted device and mobile phone A, can be maintained through Bluetooth Low Energy (BLE) or through classic Bluetooth. The present application does not make a limitation.

[0140] Exemplarily, the Discovery Request message carries the device information of the vehicle-mounted device. Optionally, the device information includes, but is not limited to, the identification information of the vehicle-mounted device (such as device name, device model, Bluetooth address information, etc.). The present application does not make a limitation.

[0141] S903, mobile phone A displays a prompt box and receives user operations.

[0142] Exemplarily, the proxy registration service in mobile phone A is also pre-registered with the Nearby service. For specific descriptions, reference can be made to the relevant descriptions on the vehicle-mounted device side, which will not be repeated here.

[0143] Exemplarily, after mobile phone A receives the Discovery Request message sent by the vehicle-mounted device, mobile phone A can obtain the device information of the vehicle-mounted device. It should be noted that in the embodiments of the present application, the sending and receiving of Bluetooth signaling (or messages) are both completed through the cooperation of the Bluetooth chip and the Nearby service. For example, after the Bluetooth chip receives a Bluetooth message, it can output the information carried in the message to the Nearby service, and the Nearby service can send corresponding instructions and data to the application. The multi-screen collaboration application can perform response processing based on the received instructions and data. The interactions between the Bluetooth chip, the Nearby service, and the multi-screen collaboration application are all realized through the interfaces between layers and will not be repeated below.

[0144] Exemplarily, Figure 10A For the schematic diagram of the user interface shown exemplarily, please refer to Figure 10A, the display interface of mobile phone A can display a prompt box 1001, which includes but is not limited to: the identification information 1002 of the in-vehicle device. Optionally, the identification information 1002 of the in-vehicle device can be the icon of the in-vehicle device, or the device name of the in-vehicle device, or the model of the in-vehicle device, etc., which is not limited in this application. Optionally, mobile phone A can pre-store the corresponding relationship between the icon of the device and the device information. For example, mobile phone A stores the corresponding relationship between the icon of the in-vehicle device and the device type of the in-vehicle device (that is, indicating that the device is an in-vehicle device). After receiving the BLE Discovery Request message, mobile phone A obtains that the device type of the sending end is an in-vehicle device, and mobile phone A can obtain the device icon corresponding to the device type of the in-vehicle device stored locally and display it in the prompt box 1001.

[0145] Exemplarily, the prompt box 1001 further includes a cancel control 1003 and a confirmation control 1004. Exemplarily, the cancel control 1003 is used to cancel the display of the prompt box 1001, and it can also be understood as refusing to perform proxy registration with the in-vehicle device.

[0146] Exemplarily, in the embodiment of this application, when the user clicks the confirmation control 1004, correspondingly, mobile phone A receives the operation of the user clicking the connection control 1004, and mobile phone A determines to perform proxy registration with the in-vehicle device.

[0147] S904, mobile phone A sends a Discovery Response (discovery response) message to the in-vehicle device.

[0148] Exemplarily, in response to the operation of the user clicking the confirmation control 904 received, mobile phone A can send a Discovery Response message to the in-vehicle device based on the Bluetooth protocol and the Bluetooth address information of the in-vehicle device obtained from the Discovery Request message to indicate multi-screen collaboration with the in-vehicle device.

[0149] Optionally, the Discovery Response message sent by mobile phone A carries the device information of mobile phone A, and the device information includes but is not limited to: the Bluetooth address information of mobile phone A, the identification information of mobile phone A (such as device name, device model, etc.), etc., which is not limited in this application.

[0150] S905, the in-vehicle device sends a Bluetooth connection request message to mobile phone A.

[0151] Exemplarily, when the in-vehicle device receives the Discovery Response message sent by mobile phone A, the in-vehicle device may send a Bluetooth connection request message to mobile phone A based on the Bluetooth address information of mobile phone A carried in the Discovery Response message, for indicating to establish a Bluetooth connection with mobile phone A. Optionally, the connection request message carries information such as the Bluetooth address information of mobile phone A and the Bluetooth address information of the in-vehicle device, which is not limited in this application.

[0152] S906. Mobile phone A and the in-vehicle device establish a Bluetooth connection.

[0153] Exemplarily, after mobile phone A receives the Bluetooth connection request message sent by the in-vehicle device, it establishes a Bluetooth connection with the in-vehicle device.

[0154] It should be noted that in S906, mobile phone A and the in-vehicle device may perform multiple Bluetooth signaling interactions to transmit the information required for establishing the Bluetooth connection. The specific interaction process may refer to the content in the Bluetooth protocol, and this application will not repeat the description.

[0155] Furthermore, it should be noted that this application embodiment only takes S906 as an example for the Bluetooth connection. In other embodiments, it can also be understood that S902 is the start of the Bluetooth connection establishment, or it can be understood that any interaction process among S902 - S906 is the starting moment of the Bluetooth connection establishment, which is not limited in this application.

[0156] Exemplarily, after the discovery connection of the in-vehicle device determines to establish a Bluetooth connection with the mobile phone through the Session Server, it may send a confirmation response message to the device registration feedback, for indicating that the Session Server has been started, or it can also be understood that the proxy registration service has been started. The device registration sends a confirmation response message to the device management feedback, for indicating that the proxy registration service has been started.

[0157] S705. The mobile phone and the in-vehicle device perform a legality authentication.

[0158] Exemplarily, after the mobile phone and the in-vehicle device establish a Bluetooth connection, a PIN code input box is displayed in the mobile phone display interface. Figure 10B For the schematic diagram of the user interface shown exemplarily, please refer to Figure 10B, the user can enter the PIN code in the input box 1005 of the in-vehicle device based on the PIN code displayed on the in-vehicle device side, and click the confirmation option. In response to the received PIN code, the mobile phone sends a legality authentication message to the in-vehicle device, and the message includes, but is not limited to, the PIN code entered by the user. In response to the received legality authentication message, the in-vehicle device obtains the PIN code and compares it with the PIN code generated locally. If they are the same, it is determined that the legality authentication is successful. If they are different, it is determined that the legality authentication fails, and the display screen of the in-vehicle device can display that the PIN code input is incorrect and prompt the user to re-enter.

[0159] Part Two: Proxy Registration

[0160] Figure 11 For the schematic diagram of the exemplary proxy registration process, please refer to Figure 11 , specifically including but not limited to the following steps:

[0161] S1101, the mobile phone interacts with the cloud to register information.

[0162] Exemplarily, after the mobile phone establishes a Bluetooth connection with the in-vehicle device, it can initiate the proxy registration process. Optionally, the mobile phone and the cloud can perform data interaction through any wireless communication protocol, which is not limited in this application.

[0163] The cloud is one or more server clusters, and each server cluster includes one or more servers, which is not limited in this application.

[0164] Specifically, Figure 12 For the schematic diagram of the exemplary information interaction registration process, please refer to Figure 12 , specifically including but not limited to the following steps:

[0165] S1201, the mobile phone sends a registration request message to the cloud.

[0166] Exemplarily, the mobile phone sends a registration request message to the cloud. The registration request message is used to request registration information, and the registration request message includes, but is not limited to: a registration request indication, device information of the mobile phone (such as device ID, etc.), user account (such as a Honor account), etc.

[0167] S1202, the cloud sends a registration response message to the mobile phone.

[0168] Exemplarily, in response to the received registration request message, the cloud determines that there is a device that needs to be registered, and the cloud generates a first verification code, which can also be called registration information. The cloud sends a registration response message to the mobile phone, and the registration response message includes, but is not limited to, the first verification code, and the first verification code is optionally a random number.

[0169] S1102, The mobile phone sends a first verification code to the in-vehicle device.

[0170] Exemplarily, the mobile phone sends a first message to the in-vehicle device through the Bluetooth connection between the mobile phone and the in-vehicle device, and the first message includes the first verification code.

[0171] S1103a, The in-vehicle device sends a second verification code to the mobile phone.

[0172] Exemplarily, the in-vehicle device (specifically, the discovery connection) generates a second verification code (which can also be called the challenge word of the in-vehicle device) in response to the received first message, and the second verification code is optionally a random number.

[0173] The in-vehicle device sends a second message to the mobile phone through the Bluetooth connection between the in-vehicle device and the mobile phone, and the second message includes but is not limited to the second verification code.

[0174] S1103b, The mobile phone sends the second verification code to the cloud.

[0175] Exemplarily, the mobile phone sends a third message to the cloud in response to the received second message, and the third message includes the second verification code. It can be understood that the second message is a Bluetooth message. After receiving the Bluetooth message, the mobile phone unpacks and processes the message to obtain the second verification code. The mobile phone repackages the second verification code to generate a third message, and the third message is the packaging format that conforms to the communication protocol between the mobile phone and the cloud.

[0176] S1104a, The cloud sends a third verification code to the mobile phone.

[0177] Exemplarily, the cloud generates a third verification code (which can also be called the challenge word of the cloud) in response to the received third message, and the cloud sends a fourth message to the mobile phone, and the fourth message includes but is not limited to the third verification code. Optionally, the third verification code is a random number.

[0178] S1104b, The mobile phone sends the third verification code to the in-vehicle device.

[0179] Exemplarily, the mobile phone sends a fifth message to the in-vehicle device in response to the received fourth message. The fifth message includes but is not limited to the third verification code.

[0180] S1105, The in-vehicle device generates a fourth verification code based on the first verification code, the second verification code, and the third verification code.

[0181] Exemplarily, based on the above steps, both the in-vehicle device side and the cloud can obtain: registration information (i.e., the first verification code), the challenge word of the in-vehicle device (i.e., the second verification code), the challenge word of the cloud device (i.e., the third verification code), and the in-vehicle device key information. Among them, the in-vehicle device key information is issued by the cloud to the in-vehicle device and is pre-stored in the device. Moreover, the cloud also stores the key information of this in-vehicle device. Optionally, in-vehicle devices of the same type or the same brand can correspond to the same key information, or different in-vehicle devices can correspond to different in-vehicle information, which is not limited in this application.

[0182] The in-vehicle device can calculate the first verification code, the second verification code, the third verification code, and the in-vehicle device key information based on a preset algorithm (which can also be called a signature verification algorithm) to obtain a fourth verification code, which can also be called signature information.

[0183] S1106a, the in-vehicle device sends the fourth verification code to the mobile phone.

[0184] Exemplarily, the in-vehicle device sends a sixth message to the mobile phone. The sixth message includes, but is not limited to: the fourth verification code (which can also be called signature verification information), the identification information of the in-vehicle device (such as the in-vehicle device ID), and the public key information of the in-vehicle device. Optionally, the public key information and the key information of the in-vehicle device are a key pair, which can also be called symmetric encryption information.

[0185] S1106b, the mobile phone sends the fourth verification code to the cloud.

[0186] Exemplarily, in response to the received sixth message, the mobile phone sends a seventh message to the cloud. The seventh message includes, but is not limited to, the fourth verification code.

[0187] S1107, the cloud verifies the fourth verification code.

[0188] Exemplarily, in response to the received seventh message, the cloud obtains the fourth verification code. The cloud can obtain the pre-stored key information of the in-vehicle device (i.e., the first encryption information) based on the identification information of the in-vehicle device. The cloud can calculate a verification code to be verified based on a preset algorithm (the same as the algorithm on the in-vehicle device side) for the first verification code, the second verification code, the third verification code, and the in-vehicle device key information. The cloud compares the verification code to be verified with the fourth verification code.

[0189] In one example, if the verification code to be verified is the same as the fourth verification code, it is determined that the proxy registration is successful, and the cloud adds the in-vehicle device to the trust ring to which the mobile phone belongs. Specifically, the cloud stores a device list corresponding to each trust ring, and the list records the device identification information and device public key information of the devices within the trust ring. After the cloud obtains the identification information and public key information of the in-vehicle device, it adds the identification information and public key information of the in-vehicle device to the device list corresponding to the trust ring to which the mobile phone belongs. Optionally, adding the relevant information of the in-vehicle device to the device list of the trust ring can be understood as that the in-vehicle device has completed registration in the cloud and joined the trust ring, and the cloud executes S1108.

[0190] In another example, if the verification code to be verified is different from the fourth verification code, it is determined that the proxy registration fails, and the cloud sends a registration failure indication to the mobile phone, and the mobile phone sends a registration failure indication to the in-vehicle device. The in-vehicle device can display a proxy registration failure prompt message on the screen.

[0191] S1108, the cloud sends a proxy registration success indication to the mobile phone.

[0192] Exemplarily, the cloud determines that the proxy registration is successful and sends a proxy registration success indication to the mobile phone to indicate that the in-vehicle device has been successfully registered to the cloud.

[0193] S1109, the mobile phone sends registration result information to the in-vehicle device.

[0194] Exemplarily, in response to the received proxy registration success indication, the mobile phone determines that the in-vehicle device has been successfully registered to the cloud. The mobile phone obtains the device information of the mobile phone stored at its end (such as the device ID of the mobile phone), user name, user ID, and registration result. Among them, the user name and user ID are the user name and user ID corresponding to the trust ring where the mobile phone is located. It can be understood that the devices within this trust ring all use this user name and user ID.

[0195] The mobile phone sends registration result information to the in-vehicle device, and the registration result information includes but is not limited to: the device information of the mobile phone (such as the device ID of the mobile phone), user name, user ID, and registration result. Among them, the registration result is used to indicate that the in-vehicle device has been successfully registered to the cloud.

[0196] S1110a, the discovery connection sends a registration success message 1 to the device registration.

[0197] Exemplarily, in response to the received registration result information, the discovery connection determines that the proxy registration is successful and obtains the device information, user name, and user ID of the mobile phone.

[0198] The discovery connection sends a registration success message 1 to the device registration, and the message includes but is not limited to: the device information, user name, user ID, etc. of the mobile phone.

[0199] S1110b, the device registration sends a registration success message 2 to the device management.

[0200] Exemplarily, in response to the received registration success message 1, the device registration parses the information in the registration success message to obtain the user name, user ID, and device information of the mobile phone.

[0201] Send a registration success message 2 to the device management, and the message includes but is not limited to: user name, user ID.

[0202] S1110c, the device management sends a registration success message 3 to the in-vehicle application.

[0203] Exemplarily, in response to the received registration success message 2, the device management sends a registration success message 3, and the message includes but is not limited to: user name, user ID.

[0204] The in-vehicle application receives the registration success message 3, determines that the proxy registration is successful, and obtains the user name and user ID.

[0205] S1110d, the device registration sends a registration success message 4 to the discovery connection.

[0206] Exemplarily, after the device registration parses out the user name, user ID, and device information of mobile phone A, it can send a registration success message 4 to the discovery connection. The message includes but is not limited to: user ID and device information of mobile phone A. It can be understood that after the discovery connection receives the registration result information sent by the mobile phone and sends a registration success message 1 to the device registration, it is a message pass-through method, that is, only the message is unpacked and repackaged, and the data in the message is not parsed. The device registration can parse the data in the message to obtain information such as the user name and user ID, and send all or part of the parsed information to the discovery connection and the device management respectively.

[0207] Optionally, S1110d can be executed at any time after S1110a, and the present application does not limit its execution order.

[0208] Exemplarily, after the discovery connection obtains the user ID and device information of mobile phone A, it sends a Bluetooth broadcast packet, and the Bluetooth broadcast packet includes but is not limited to the device information of the in-vehicle device and the user ID, so that after the nearby devices in the same trust ring (that is, devices with the same user ID) receive the Bluetooth broadcast packet, they establish an ad hoc network (which can also be understood as a connection relationship within the trust ring) with it.

[0209] Exemplarily, mobile phone A receives a Bluetooth broadcast message and obtains the user ID therein. Based on the user ID, it is recognized that the in-vehicle device has the same user ID as mobile phone A, which is a device within the trust ring. Moreover, since an authentication process (i.e., the authentication process shown in Figure 7 ) has been executed between mobile phone A and the in-vehicle device, mobile phone A stores the fingerprint information of the in-vehicle device, etc., and the discovery connection of the in-vehicle device also stores the device information of mobile phone A. Correspondingly, mobile phone A and the in-vehicle device can quickly establish an ad hoc network based on the device information of mobile phone A.

[0210] Exemplarily, after the in-vehicle device joins the trust ring (i.e., successfully registers in the cloud and has a user ID and user name), and an ad hoc network is established between mobile phone A and the in-vehicle device, business transfer can be performed between mobile phone A and the in-vehicle device. The in-vehicle device can transfer the business of the in-vehicle device to mobile phone A, and mobile phone A can also transfer the business of mobile phone A to the in-vehicle device. The specific usage scenarios can refer to the embodiments of the prior art, which are not limited in this application. For example, Figure 13 For the schematic diagram of the user interface shown exemplarily, please refer to Figure 13 . After the in-vehicle device and mobile phone A establish an ad hoc network, a control 806 corresponding to mobile phone A can be displayed in the display interface 801 of the in-vehicle device. The user can click on the control 806 corresponding to mobile phone A to perform services within the trust ring such as business transfer with mobile phone A. In response to the received user operation, the in-vehicle device displays a trust ring service interface 807, which may include options or controls corresponding to different trust ring services. The user can trigger the trust ring service between the in-vehicle device and mobile phone A by selecting the corresponding control.

[0211] Optionally, when the in-vehicle device and mobile phone A perform business transfer, different Session Servers can be established according to different services. Optionally, if the ad hoc network connection between the in-vehicle device and mobile phone A is to be maintained (this application only takes Bluetooth connection as an example, and it can also be other connection methods such as Wi-Fi, which are not limited in this application), then at least one service needs to maintain data transmission. That is to say, if there is no service within a certain period of time, the connection will be automatically disconnected. Correspondingly, each service corresponds to a Session Server. When the ad hoc network connection between mobile phone A and the in-vehicle device corresponds to the Session Server of at least one service, the in-vehicle device can delete the Session Server corresponding to the proxy registration service. For example, after the in-vehicle device and mobile phone A establish an ad hoc network, at this time, the Session Server of the proxy registration service exists. The in-vehicle device and mobile phone A can perform data interaction for the map application, and the in-vehicle device starts the Session Server corresponding to the map application. Correspondingly, the in-vehicle device can delete the Session Server corresponding to the proxy registration service.

[0212] Part Three: Trust Ring Authentication.

[0213] Exemplarily, after the in-vehicle device successfully joins the trust ring (i.e., registers to the cloud), other devices within the trust ring can obtain relevant information of the in-vehicle device from the cloud, and establish an ad-hoc network with the in-vehicle device based on the user ID corresponding to the trust ring. Among them, the trust ring authentication is divided into two parts. The first part is the device data synchronization process, and the second part is the ad-hoc network establishment process. Among them, the device data synchronization process refers to the electronic devices within the trust ring synchronizing the relevant information of the newly added electronic device. The ad-hoc network establishment process refers to the electronic devices within the trust ring and the newly added electronic device can establish an ad-hoc network to conduct business transactions between devices. Optionally, the second part is an optional part. That is to say, after the first part is completed, the devices within the trust ring can establish an ad-hoc network with the newly added electronic device (such as an in-vehicle device) after receiving a user operation. Optionally, it can also be to automatically establish an ad-hoc network after some specific conditions (such as being close to the normal line). The specific triggering conditions can be set according to actual needs, and this application does not make any limitations.

[0214] Figure 14 For the schematic diagram of the online device authentication process shown exemplarily, please refer to Figure 14 , specifically including but not limited to the following steps:

[0215] S1401, the cloud sends a registration notice to Mobile Phone B.

[0216] Exemplarily, after the in-vehicle device is successfully registered, that is, after executing S1108, the cloud sends a registration notice to all online devices within the trust ring to which the in-vehicle device belongs. The registration notice is used to indicate that a new device has joined the trust ring. The registration notice includes but is not limited to the identification information of the in-vehicle device (such as the in-vehicle device ID).

[0217] Optionally, the cloud sends a registration notice to the online device through PUSH and MQTT (Message Queuing Telemetry Transport) connections. In this embodiment, only Mobile Phone B is taken as an example for illustration. The processing methods of other online electronic devices are the same, and this application will not give examples one by one.

[0218] S1402, Mobile Phone B sends a device information acquisition request to the cloud.

[0219] Exemplarily, Mobile Phone B (specifically the device management) determines that a new device has joined the trust ring in response to the received registration notice. Mobile Phone B acquires the identification information of the in-vehicle device. And Mobile Phone B sends a device information acquisition request to the cloud, and the request includes the identification information of the in-vehicle device.

[0220] S1403, the cloud sends device information to mobile phone B.

[0221] Exemplarily, the cloud sends device information to mobile phone B, and the device information includes but is not limited to: public key information of in-vehicle devices, etc.

[0222] Mobile phone B (specifically, device management) receives the device information and obtains the public key information of the in-vehicle device therein, etc.

[0223] S1404, device management sends a knowledge base update instruction to discovery connection.

[0224] Exemplarily, device management sends a knowledge base update instruction to discovery link, and the instruction includes but is not limited to: public key information of in-vehicle devices, identification information of in-vehicle devices (such as in-vehicle device ID).

[0225] S1405, discovery connection updates the knowledge base.

[0226] Exemplarily, discovery connection updates the knowledge base based on the knowledge base update instruction. Specifically, discovery connection writes the public key information of the in-vehicle device and the identification information of the in-vehicle device into the knowledge base correspondingly.

[0227] S1406, device management sends a query device online instruction to discovery link.

[0228] Device management sends a query device online instruction to discovery connection in real time or periodically, which is used to instruct discovery connection to query whether the in-vehicle device is online. Discovery connection can obtain the user ID (already in the knowledge base in advance) and the in-vehicle device ID from the knowledge base, and query whether it receives the corresponding Bluetooth broadcast. For example, as described above, after the in-vehicle device joins the trust ring, when the Bluetooth function is turned on, it sends a Bluetooth broadcast containing the in-vehicle device ID and the user ID in real time or periodically. After mobile phone B receives the Bluetooth broadcast (which may be sent by the in-vehicle device or other devices), mobile phone B detects whether the Bluetooth broadcast includes the user ID and the in-vehicle device ID. If the above information is included, it is determined that the sender of the Bluetooth broadcast is the device newly added to the trust ring.

[0229] Optionally, the Bluetooth broadcast has a certain range, and the Bluetooth broadcast cannot be received beyond this range. If mobile phone B is online but not within the Bluetooth broadcast range of the in-vehicle device, then mobile phone B cannot receive the Bluetooth broadcast of the in-vehicle device. When mobile phone B enters the Bluetooth broadcast range of the in-vehicle device at any time, mobile phone B (when online and the Bluetooth function is turned on) can scan the Bluetooth broadcast of the in-vehicle device and execute S1405.

[0230] S1407, mobile phone B authenticates with the in-vehicle device.

[0231] Exemplarily, it is found that after the discovery connection determines that the Bluetooth broadcast of the in-vehicle device is received, mobile phone B authenticates with the in-vehicle device. The specific authentication process includes but is not limited to:

[0232] Mobile phone B (specifically, the discovery connection on the mobile phone side) generates a first random number. Mobile phone B sends authentication message 1 to the in-vehicle device (specifically, the discovery connection of the in-vehicle device), and the first random number is included in authentication message 1.

[0233] The in-vehicle device receives authentication message 1 and obtains the first random number. The in-vehicle device generates a second random number. The in-vehicle device sends authentication message 2 to mobile phone B, and the second random number is included in the message.

[0234] Mobile phone B obtains the public key information of the in-vehicle device from the knowledge base. Based on the signature verification algorithm, mobile phone B performs operations on the public key of the in-vehicle device, the first random number, and the second random number to obtain the signature verification information. Mobile phone B sends authentication message 3 to the in-vehicle device, and the signature verification information is included in the message.

[0235] The in-vehicle device receives authentication message 3, obtains the signature verification information, and verifies the signature verification information. Specifically, the in-vehicle device also performs operations on the public key of the in-vehicle device, the first random number, and the second random number based on the signature verification algorithm to obtain the signature verification information. The in-vehicle device compares the signature verification information generated at its own end with the signature verification information sent by mobile phone B. If they are consistent, it is confirmed that the authentication is successful. The in-vehicle device sends an authentication success message to mobile phone B to indicate that the authentication is successful, and mobile phone B and the in-vehicle device can establish an ad-hoc network (which can be Bluetooth or Wi-Fi. The specific establishment process can refer to the existing technology and is not limited in this application). If they are inconsistent, the authentication fails.

[0236] Optionally, after the in-vehicle device and mobile phone B successfully establish an ad-hoc network, the in-vehicle device and / or mobile phone B can, in response to the received user operation, perform service transfer operations with any device (which can be one or more devices) that has already established an ad-hoc network within the trust ring. For example, if the in-vehicle device has currently established ad-hoc networks with mobile phone A and mobile phone B, mobile phone A can transfer the map data of mobile phone A to the in-vehicle device, and mobile phone B can transfer the chat data to the in-vehicle device. The map data of mobile phone A and the chat data of mobile phone B can be displayed on the display screen of the in-vehicle device.

[0237] Figure 15 For the schematic diagram of the offline device authentication process shown exemplarily, please refer to Figure 15 , which specifically includes but is not limited to the following steps:

[0238] S1501, Mobile phone C sends a login.

[0239] Exemplarily, in this scenario, take the scenario where mobile phone C goes offline and then goes online again as an example for explanation. After mobile phone C goes online again, mobile phone C sends a login notification to the cloud. In response to the login notification, the cloud determines that mobile phone C has logged in and sends a login response to mobile phone C.

[0240] S1502, the device management sends a device list update indication to the device registration.

[0241] Exemplarily, in response to the received login notification, the device management sends a device list update indication to the device registration to trigger the device registration to update the device list.

[0242] S1503, mobile phone C sends a full-device information acquisition request to the cloud.

[0243] Exemplarily, mobile phone C (specifically the device registration) sends a full-device information acquisition request to the cloud to request the device information of all devices within the trust ring to which mobile phone C belongs. The full-device information acquisition request includes, but is not limited to: the device identification information of mobile phone C, user ID, etc.

[0244] S1504, the cloud sends full-device information to mobile phone C.

[0245] Exemplarily, the cloud looks up the corresponding list within the trust ring based on the user ID of mobile phone C, and obtains the device information of all devices (i.e., full devices) within the trust ring from the list and sends it to mobile phone C. The device information includes, but is not limited to: the identification information of the device (i.e., device ID) and the corresponding device public key information.

[0246] S1505, the device management sends a knowledge base update indication to the discovery connection.

[0247] Exemplarily, after the device management obtains the full-device information, it sends a knowledge base update indication to the discovery connection to indicate the update of the knowledge base. The indication includes, but is not limited to, the full-device information.

[0248] S1506, the discovery connection updates the knowledge base.

[0249] Exemplarily, the discovery connection writes the obtained full-device information into the knowledge base. Optionally, the device clears the knowledge base every time it goes offline. Correspondingly, the device needs to update the knowledge base again every time it goes online again.

[0250] S1507, the device management sends a query device online indication to the discovery connection.

[0251] S1508, mobile phone C authenticates with the in-vehicle device.

[0252] Exemplarily, it is found that the connection will authenticate with electronic devices within the same trust ring nearby based on the device information of all devices. The specific authentication process is the same as the authentication process between mobile phone B and the in-vehicle device described above, and will not be elaborated here.

[0253] In a possible implementation, the in-vehicle device can join multiple trust rings. For example, mobile phone A, mobile phone B, mobile phone C, and the in-vehicle device in the above text are within the same trust ring (such as the first trust ring), and the user ID is the first user ID. The user can operate on the in-vehicle device and click the proxy registration function again to instruct the in-vehicle device to execute the proxy registration process. Correspondingly, the in-vehicle device responds to the received user operation and re-executes the proxy registration process. Assume that the in-vehicle device and mobile phone D execute the near-field authentication and proxy registration processes described above, and successfully register to the second trust ring where mobile phone D is located and have the corresponding user ID (such as the second user ID). The specific registration process can refer to the above text and will not be elaborated here. Exemplarily, the information corresponding to multiple trust rings can be displayed in the trust ring interface of the in-vehicle device, such as Figure 16 shown. In the paired device display box 808, controls corresponding to multiple trust rings joined by the in-vehicle device can be displayed, such as the first trust ring control 8081 and the second trust ring control 8082. The user can click the corresponding control to switch the trust ring joined by the in-vehicle device. The in-vehicle device responds to the received user operation, determines the target trust ring, and obtains the user ID of the target trust ring. As described above, after the in-vehicle device joins the first trust ring, the in-vehicle device sends Bluetooth broadcast information including the first user ID of the first trust ring in real time or periodically to establish or maintain an ad-hoc network with electronic devices within the first trust ring. After the in-vehicle device determines to switch the trust ring, the in-vehicle device will send Bluetooth broadcast information including the second user ID of the second trust ring to establish an ad-hoc network with electronic devices within the second trust ring. Still referring to Figure 16 it, exemplarily, the paired device display box 808 also includes a connect new mobile phone control 8083. When the user clicks this control, the in-vehicle device can be triggered to connect to an electronic device within an unjoined trust ring nearby to register to a new trust ring.

[0254] It can be understood that for an electronic device to implement the above functions, it includes the corresponding hardware and / or software modules for executing each function. Combining the algorithm steps of each example described in the embodiments disclosed in this article, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed in the way of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application in combination with the embodiments, but such implementation should not be considered to exceed the scope of the present application.

[0255] In one example, Figure 17 A schematic block diagram of a device 1700 according to an embodiment of the application is shown. The device 1700 may include: a processor 1701 and a transceiver / transceiver pin 1702. Optionally, it may further include a memory 1703.

[0256] Each component of the device 1700 is coupled together through a bus 1704. The bus 1704 includes, in addition to a data bus, a power bus, a control bus, and a status signal bus. However, for the sake of clarity, all kinds of buses are referred to as the bus 1704 in the figure.

[0257] Optionally, the memory 1703 may be used for the instructions in the foregoing method embodiments. The processor 1701 may be configured to execute the instructions in the memory 1703, control the receiving pin to receive signals, and control the transmitting pin to transmit signals.

[0258] The device 1700 may be the electronic device or the chip of the electronic device in the foregoing method embodiments.

[0259] Among them, all relevant contents of each step involved in the foregoing method embodiments can be cited in the function descriptions of the corresponding functional modules, and will not be elaborated here.

[0260] This embodiment also provides a computer storage medium. Computer instructions are stored in the computer storage medium. When the computer instructions run on an electronic device, the electronic device is enabled to execute the foregoing related method steps to implement the method in the foregoing embodiments.

[0261] This embodiment also provides a computer program product. When the computer program product runs on a computer, the computer is enabled to execute the foregoing related steps to implement the method in the foregoing embodiments.

[0262] In addition, an embodiment of the present application also provides a device. Specifically, this device may be a chip, a component, or a module. The device may include a processor and a memory connected to each other. The memory is used to store computer execution instructions. When the device runs, the processor may execute the computer execution instructions stored in the memory to enable the chip to execute the methods in the foregoing method embodiments.

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

[0264] As described above, the above embodiments are only used to illustrate the technical solutions of the present application and are not intended to limit it; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions recorded in the foregoing embodiments, or perform equivalent replacements on some of the technical features; and these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the various embodiments of the present application.

Claims

1. A registration method, characterized in that, Including: In response to a received first operation, a first electronic device establishes a first communication connection with a second electronic device; Data interaction is performed between the second electronic device and the cloud through a second communication connection, and the second electronic device belongs to a first trust ring; The first electronic device performs registration authentication with the cloud through the second electronic device; wherein, during the process of the first electronic device performing registration authentication with the cloud, the information sent by the first electronic device to the cloud is sent to the second electronic device through the first communication connection, and the second electronic device proxies the first electronic device to send it to the cloud; the information sent by the cloud to the first electronic device is sent to the second electronic device through the second communication connection, and the second electronic device proxies the cloud to send it to the first electronic device; After the first electronic device successfully performs registration authentication with the cloud, the first electronic device obtains first user information of the first trust ring.

2. The method according to claim 1, wherein The first electronic device performing registration authentication with the cloud includes: During the process of the first electronic device performing registration authentication with the cloud, the first electronic device sends public key information of the first electronic device and identification information of the first electronic device to the cloud through the second electronic device.

3. The method according to claim 2, wherein The method further includes: Based on the first user information, the first electronic device establishes a communication connection with at least one electronic device within the first trust ring.

4. The method according to claim 3, characterized in that The method further includes: The first electronic device performs service transfer with the at least one electronic device.

5. The method according to claim 3, characterized in that Based on the first user information, the first electronic device establishing a communication connection with at least one electronic device within the first trust ring includes: The first electronic device sends a Bluetooth broadcast message, and the Bluetooth broadcast message includes identification information of the first electronic device and the first user information; The first electronic device authenticates with the at least one electronic device that receives the Bluetooth broadcast message. During the authentication process, the at least one electronic device obtains the public key information of the first electronic device from the cloud and performs authentication with the first electronic device based on the public key information; After the first electronic device successfully authenticates with the at least one electronic device, it establishes a communication connection with the at least one electronic device.

6. The method according to any one of claims 1 to 5, characterized in that After the first electronic device successfully performs registration authentication with the cloud, the first electronic device obtaining the first user information of the first trust ring includes: The first electronic device receives a registration success message sent by the second electronic device. The registration success message is used to indicate that the in-vehicle device has been successfully registered to the cloud and joined the first trust ring, and the registration success message includes the first user information.

7. The method according to any one of claims 1 to 6, characterized in that, The method further includes: In response to a received second operation, the first electronic device establishes a third communication connection with a third electronic device; data interaction is performed between the third electronic device and the cloud through a fourth communication connection, and the third electronic device belongs to a second trust ring; The first electronic device is registered and authenticated with the cloud through the third electronic device. During the process of the first electronic device registering and authenticating with the cloud, the information sent by the first electronic device to the cloud is sent to the third electronic device through the third communication connection, and the third electronic device acts as an agent to send it to the cloud. The information sent by the cloud to the first electronic device is sent to the third electronic device through the fourth communication connection, and the third electronic device acts as an agent to send it to the first electronic device. After the first electronic device successfully registers and authenticates with the cloud, the first electronic device obtains the second user information of the second trust ring.

8. The method according to claim 7, wherein The method further includes: In response to a received third operation, the first electronic device switches from the first trust ring to the second trust ring and establishes a communication connection with at least one electronic device within the second trust ring.

9. The method according to any one of claims 1 to 8, characterized in that, The first communication connection is a Bluetooth connection.

10. An electronic device, characterized in that, Comprising: One or more processors and a memory; And one or more computer programs, wherein the one or more computer programs are stored on the memory, and when the computer programs are executed by the one or more processors, the electronic device is caused to execute the method according to any one of claims 1 to 9.

11. A computer storage medium, characterized in that, Comprising computer instructions, when the computer instructions run on an electronic device, the electronic device is caused to execute the method according to any one of claims 1 - 9.

12. A computer program product, characterized in that, When the computer program product runs on a computer, the computer is caused to execute the method according to any one of claims 1 - 9.

13. A chip, characterized in that, Comprising one or more interface circuits and one or more processors; the interface circuit is configured to receive a signal from the memory of the electronic device and send the signal to the processor, the signal including computer instructions stored in the memory; when the processor executes the computer instructions, the electronic device is caused to execute the method according to any one of claims 1 - 9.

Images