Device login method, electronic device, and vehicle

Abstract

The present application relates to the technical field of terminals. Provided are a device login method, an electronic device, and a vehicle. In the present application, when a second electronic device is located in a target three-dimensional space, a first electronic device can instruct the account of the second electronic device to be automatically logged in to by means of a target display screen corresponding to the target three-dimensional space, thereby realizing automatic login of a device account, and thus reducing the user operation difficulty. The method comprises: a first electronic device acquiring the position of a second electronic device, which the first electronic device establishes a communication connection with, wherein the second electronic device is a mobile terminal; when a first position of the second electronic device is in a first target three-dimensional space, the first electronic device acquiring a target display screen among at least one display screen connected to the first electronic device, wherein part or all of the target display screen is in the first target three-dimensional space; and then, the first electronic device logging in to a first account of the second electronic device by means of the target display screen.

Description

Device login method, electronic device, and vehicle

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on December 29, 2023, with application number 202311865376.4 and application name “Device Login Method, Electronic Device and Vehicle”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of terminal technology, and in particular to a device login method, electronic equipment, and vehicle. Background Art

[0003] With the development of intelligent vehicles, the number of applications that can be installed on vehicle computers and the number of vehicle settings and functions are increasing. When users use these applications or functions, the vehicle computer stores the user data generated in the user's logged-in account. A vehicle may have multiple users, so the vehicle computer stores user data corresponding to multiple accounts.

[0004] Currently, multiple screens per vehicle are becoming a trend. For example, the in-vehicle display screens may include the central control screen on the center console, the screen in front of the front passenger (also known as the front passenger), the screen in front of the left rear passenger, and the screen in front of the right rear passenger. After boarding the vehicle, the user logs in on the selected screen. The vehicle computer then loads the corresponding user data onto the selected screen based on the account login operation, facilitating subsequent operations.

[0005] However, for the security of user data, account login operations are generally more complicated, which increases the difficulty of user operations.

[0006] Summary of the Invention

[0007] To address the aforementioned technical issues, this application provides a device login method, electronic device, and vehicle. This application provides a technical solution whereby, when a second electronic device is located within a target three-dimensional space, a first electronic device can instruct a target display screen corresponding to the target three-dimensional space to automatically log in to the second electronic device's account. This automated device account login reduces user operational complexity and enhances the user experience.

[0008] In order to achieve the above technical objectives, this application provides the following technical solutions:

[0009] In a first aspect, a device login method is provided, applicable to a first electronic device. A communication connection is established between the first electronic device and at least one display screen, as well as a second electronic device. The method includes: obtaining a first location of the second electronic device, where the second electronic device is a mobile terminal; determining that the first location is within a first target three-dimensional space; obtaining a target display screen from the at least one display screen, where part or all of the target display screen is within the first target three-dimensional space; and logging into a first account of the second electronic device through the target display screen.

[0010] When a first electronic device determines that a second electronic device has entered the first target three-dimensional space corresponding to a target display screen, it can determine that the user currently carrying the second electronic device is close to the target display screen and is likely to operate the target display screen. Therefore, the first electronic device can automatically log in to the first account of the second electronic device through the target display screen. In this way, by determining whether the second electronic device is located in the pre-configured first target three-dimensional space, automatic account login is achieved for the target display screen. This account login process no longer relies on the user's active login, effectively reducing user operation difficulty.

[0011] In some examples, the first electronic device is a vehicle computer, and the at least one display screen and the first electronic device are located in the same vehicle.

[0012] In some examples, the second electronic device is a wearable device. In some examples, the second electronic device is a smart watch or a smart bracelet.

[0013] According to a first aspect, after logging into a first account of a second electronic device via a target display, the target display is in a locked state by default, and the method further includes: detecting a first operation performed by the user on the target display. In response to the first operation, when a second position of the second electronic device is within a second target three-dimensional space corresponding to the target display, unlocking the target display; wherein the first target three-dimensional space and the second target three-dimensional space have overlapping space, and part or all of the target display is within the overlapping space.

[0014] In some examples, the second target three-dimensional space is smaller than the first target three-dimensional space.

[0015] In some examples, the first target three-dimensional space includes the second target three-dimensional space.

[0016] For example, if a first electronic device detects a user unlocking a target display and determines that a second electronic device is currently located within a second target three-dimensional space, it can determine that the unlocking operation was performed by the user carrying the second electronic device. Therefore, the first electronic device can instruct the target display to automatically unlock, allowing the user carrying the second electronic device to continue operating the target display without having to perform unlock verification. This effectively reduces user operation difficulty while ensuring user data security.

[0017] According to the first aspect, or any implementation of the first aspect above, before logging into the first account of the second electronic device through the target display screen, the method further includes: obtaining a device identification of the second electronic device, and obtaining a locally stored first account that is bound to the device identification.

[0018] In some examples, a whitelist corresponding to the first account is maintained in the server, and the whitelist records the device identifications of electronic devices that are logged in with the first account, and these electronic devices are trusted devices. The first electronic device can obtain the whitelist issued by the server. Then, before the first electronic device logs in to the first account of the second electronic device through the target display, it can first confirm whether the identification of the second electronic device is in the whitelist. If the device identification of the second electronic device is in the whitelist, the first electronic device can determine that the second electronic device is a trusted device, and the first electronic device can automatically log in to the first account through the target display, thereby ensuring the security of the first account. If the device identification of the second electronic device is not in the whitelist, the first electronic device can determine that the second electronic device is not a trusted device, and the first electronic device does not have to log in to the first account through the target display, thereby avoiding affecting the security of the user data under the first account.

[0019] In this way, the security of account login is enhanced by determining the binding relationship between the device identifier and the first account.

[0020] In some examples, after determining that the first position of the second electronic device is located in the first target three-dimensional space, the first electronic device obtains the device identification of the second electronic device to determine the first account corresponding to the device identification and completes automatic login of the first account of the target display screen.

[0021] In other examples, after establishing a communication connection with the second electronic device, the first electronic device can obtain the device identification of the second electronic device, and then determine the first account corresponding to the device identification of the second electronic device. Afterwards, the first electronic device monitors the position of the second electronic device, and after determining that the first position of the second electronic device is located in the first target three-dimensional space, completes the automatic login of the first account of the target display screen. Optionally, the first electronic device obtains the first account corresponding to the device identification from a locally stored white list based on the device identification of the second electronic device, determines that the second electronic device is a trusted device, and can monitor the position of the second electronic device to ensure the security of the user data under the first account. Otherwise, if the second electronic device fails to obtain the first account corresponding to the device identification from the locally stored white list, the first electronic device determines that the second electronic device is not a trusted device, and does not need to monitor the position of the second electronic device, thereby saving power consumption.

[0022] According to the first aspect, or any implementation of the first aspect above, logging into the first account of the second electronic device through the target display screen includes: obtaining the account currently logged into the second electronic device. If the first account and the account currently logged into the second electronic device are the same, logging into the first account of the second electronic device through the target display screen.

[0023] In some examples, since electronic devices can log in to one or more accounts, to ensure the security of user data associated with each account, the first electronic device may first confirm whether the account currently logged in to the second electronic device is the first account before logging in to the first account on the target display. If the account currently logged in to the second electronic device is the first account, the target display will then log in to the first account, thereby ensuring the security of user data associated with the first account.

[0024] For example, user A owns a smartwatch. In response to user A's account 1 being logged in on the smartwatch, the server determines the smartwatch as a trusted device and establishes a binding relationship between the smartwatch's device identifier and account 1. The vehicle's primary account is account 2, which is associated with account 1. The server sends a whitelist to the vehicle that includes the binding relationship between the smartwatch's device identifier and account 1. Subsequently, user B uses user A's smartwatch and brings it near the vehicle. In one scenario, user B instructs the smartwatch to log in to user B's account 3. Based on the stored binding relationship, the vehicle's computer determines that the account 1 corresponding to the smartwatch's device identifier is different from the currently logged-in account 3. Therefore, it is not necessary to instruct the target display to log in to account 1, thereby preventing the target display from loading user A's user data and compromising the security of user A's user data. In another scenario, the smartwatch is logged out of account 1 and is not logged into any other account. In response to the smartwatch not being logged in, the vehicle's computer also does not instruct the target display to log in to account 1, thereby preventing the target display from loading user A's user data and compromising the security of user A's user data.

[0025] According to the first aspect, or any implementation of the first aspect above, before obtaining the first location of the second electronic device, the method further includes: in response to a second user operation, logging into a second account through the server, where the second account is the first account or an account associated with the first account; and receiving and saving a whitelist sent by the server, where the whitelist includes a binding relationship between a device identifier of the second electronic device and the first account.

[0026] In this way, the car computer ensures the security of subsequent automatic login of the target display screen by maintaining the white list.

[0027] In some examples, the server determines that the whitelist has been updated and automatically sends the updated whitelist to the first electronic device. For example, if a third electronic device logs into the first account, the server obtains the binding relationship between the device identifier of the third electronic device and the first account, adds the binding relationship to the whitelist, and sends the updated whitelist to the first electronic device. In this way, when the third electronic device subsequently approaches the first electronic device and enters the first target three-dimensional space, the first electronic device can automatically log into the first account through the target display.

[0028] In some examples, the first electronic device or another electronic device can add an account associated with the second account based on user operation, where the second account is the account of the first electronic device.

[0029] For example, after a first electronic device logs into a second account, a display screen detects a user requesting to log into the first account and sends a login request for the first account to a server. After the server confirms that the first electronic device has logged into the first account, it can establish an association between the first account and the second account.

[0030] For example, a third electronic device (such as a mobile phone) logs into the vehicle's second account while running a vehicle management application. The third electronic device detects the user adding a trusted account and obtains the first account. The third electronic device sends the first account to the server, which then sets the first account as a trusted account and establishes an association between the first and second accounts.

[0031] In some examples, if a first account and a second account are associated with each other, the first account and the second account may share a whitelist corresponding to the first account and a whitelist corresponding to the second account. The whitelist corresponding to the first account includes the device identifiers of electronic devices logged in with the first account, and the whitelist corresponding to the second account includes the device identifiers of electronic devices logged in with the second account.

[0032] In some examples, the whitelist includes a first account and a second account. In some examples, after the first electronic device determines that the second electronic device has moved into the first target three-dimensional space, it obtains the first account corresponding to the second electronic device, confirms that the first account is on the whitelist, and can directly log in to the first account through the target display. In other words, the first electronic device does not need to determine the device identifier of the second electronic device.

[0033] According to the first aspect, or any implementation of the first aspect above, each of the at least one display screen connected to the first electronic device is configured with a corresponding three-dimensional space, and the three-dimensional spaces corresponding to each display screen do not overlap.

[0034] In this way, the first electronic device can determine a unique target display screen according to the three-dimensional space where the second electronic device is located.

[0035] In a second aspect, a first electronic device is provided. The electronic device includes: a processor and a memory, the memory is coupled to the processor, the memory is used to store computer program code, the computer program code includes computer instructions, when the processor reads the computer instructions from the memory, the first electronic device executes: the first electronic device obtains the first position of a second electronic device that has established a communication connection with the first electronic device, the second electronic device is a mobile terminal. It is determined that the first position is located in a first target three-dimensional space, and a target display screen is obtained from at least one display screen that has established a communication connection with the first electronic device, and part or all of the target display screen is located in the first target three-dimensional space. Log in to the first account of the second electronic device through the target display screen.

[0036] According to a second aspect, after a first account of a second electronic device is logged into via a target display, the target display is in a locked state by default. When a processor reads computer instructions from a memory, the processor further causes the first electronic device to execute: detecting a first operation performed by the user on the target display. In response to the first operation, when a second position of the second electronic device is within a second target three-dimensional space corresponding to the target display, unlocking the target display; wherein the first target three-dimensional space and the second target three-dimensional space have overlapping space, and part or all of the target display is within the overlapping space.

[0037] According to the second aspect, or any implementation of the second aspect, the second target three-dimensional space is smaller than the first target three-dimensional space.

[0038] According to the second aspect, or any implementation of the second aspect, the first target three-dimensional space includes the second target three-dimensional space.

[0039] According to the second aspect, or any implementation of the second aspect above, when the processor reads the computer instructions from the memory, it further causes the first electronic device to execute: obtaining a device identification of the second electronic device, and obtaining a locally stored first account that is bound to the device identification.

[0040] According to the second aspect, or any implementation of the second aspect above, logging into the first account of the second electronic device through the target display screen includes: obtaining the account currently logged into the second electronic device. If the first account and the account currently logged into the second electronic device are the same, logging into the first account of the second electronic device through the target display screen.

[0041] According to the second aspect, or any implementation of the second aspect above, when the processor reads the computer instructions from the memory, the processor further causes the first electronic device to: in response to a second user operation, log in to a second account through the server, where the second account is the first account or an account associated with the first account; and receive and save a whitelist sent by the server, where the whitelist includes a binding relationship between the device identifier of the second electronic device and the first account.

[0042] According to the second aspect, or any implementation of the second aspect above, each of the at least one display screen connected to the first electronic device is configured with a corresponding three-dimensional space, and the three-dimensional spaces corresponding to each display screen do not overlap.

[0043] According to the second aspect, or any implementation of the second aspect above, the first electronic device is a vehicle computer, and the at least one display screen and the first electronic device are located in the same vehicle.

[0044] According to the second aspect, or any implementation of the second aspect, the second electronic device is a wearable device.

[0045] According to the second aspect, or any implementation of the above second aspect, the second electronic device is a smart watch or a smart bracelet.

[0046] In a third aspect, a vehicle is provided, comprising the first electronic device as described in the second aspect and any possible implementation thereof, and at least one display screen.

[0047] In a fourth aspect, an electronic device is provided, which has the function of implementing the device login method described in the first aspect and any possible implementation thereof. This function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-mentioned functions.

[0048] In a fifth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program (also referred to as instructions or codes), which, when executed by an electronic device, causes the electronic device to perform the method of the first aspect or any one of the embodiments of the first aspect.

[0049] In a sixth aspect, a computer program product is provided. When the computer program product is run on an electronic device, the electronic device executes the method of the first aspect or any one of the embodiments of the first aspect.

[0050] In a seventh aspect, a circuit system is provided, the circuit system including a processing circuit, the processing circuit being configured to execute the method of the first aspect or any one of the embodiments of the first aspect.

[0051] In an eighth aspect, a chip system is provided, comprising at least one processor and at least one interface circuit, wherein the at least one interface circuit is used to perform transceiver functions and send instructions to the at least one processor. When the at least one processor executes the instructions, the at least one processor executes the method of the first aspect or any one of the embodiments of the first aspect.

[0052] The technical effects of the aforementioned aspects can be referenced with each other and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] FIG1 is a schematic diagram of the distribution of display screens in a cockpit according to an embodiment of the present application;

[0054] FIG2 is a schematic diagram of a communication system for applying the device login method provided in an embodiment of the present application;

[0055] FIG3 is a schematic diagram of the hardware structure of a first electronic device provided in an embodiment of the present application;

[0056] FIG4 is a flow chart of a device login method according to an embodiment of the present application;

[0057] FIG5 is a second flow chart of a device login method according to an embodiment of the present application;

[0058] FIG6 is a schematic diagram of a three-dimensional space corresponding to a display screen provided in an embodiment of the present application;

[0059] FIG7 is a schematic diagram of a scene in which a smartwatch enters a first target three-dimensional space corresponding to a target display screen according to an embodiment of the present application;

[0060] FIG8 is a third flow chart of a device login method according to an embodiment of the present application;

[0061] FIG9 is a schematic diagram of a scene in which a smartwatch enters a second target three-dimensional space corresponding to a target display screen according to an embodiment of the present application;

[0062] FIG10 is a schematic structural diagram of a first electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0063] The technical solutions in the embodiments of the present application are described below in conjunction with the drawings in the embodiments of the present application. Among them, in the description of the embodiments of the present application, the terms used in the following embodiments are only for the purpose of describing specific embodiments, and are not intended to be used as limitations on the present application. As used in the specification and appended claims of the present application, the singular expressions "one", "a kind of", "said", "above", "the" and "this" are intended to include expressions such as "one or more", unless there is a clear indication to the contrary in the context. It should also be understood that in the following embodiments of the present application, "at least one", "one or more" refer to one or more (including two).

[0064] References to "one embodiment" or "some embodiments" etc. described in this specification mean that the specific features, structures or characteristics described in conjunction with the embodiment are included in one or more embodiments of the present application. Therefore, the statements "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. appearing in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in another way. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in another way. The term "connected" includes direct and indirect connections, unless otherwise stated. "First" and "second" are used for descriptive purposes only and are not to be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated.

[0065] In the embodiments of this application, words such as "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplarily" or "for example" in the embodiments of this application should not be interpreted as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplarily" or "for example" is intended to present the relevant concepts in a concrete manner.

[0066] In some embodiments, the cockpits of some vehicles are gradually achieving fully digital displays, with one or more display screens installed within the cockpit for displaying content such as digital instrument panels and in-car entertainment systems. As shown in FIG1 , the cockpit is equipped with multiple display screens, such as a central control screen 11 on the center console, a display screen 12 in front of the front passenger seat (also known as the front passenger), a display screen 13 in front of the left rear passenger, and a display screen 14 in front of the right rear passenger. It is understood that the cockpit may also include other display screens, such as an instrument panel screen, a display screen on the roof, a display screen on the windows, and a display screen on the seat armrests.

[0067] In some embodiments, there may be multiple users in the vehicle. In this case, for a vehicle with multiple display screens, user account login operations are high-frequency operations.

[0068] In some examples, account login methods include face recognition login, account password login, mobile phone code scanning authorization login, near field communication technology (NFC) card login, key login, etc.

[0069] Among them, if you want to implement face recognition login, you need to configure cameras that support face recognition capabilities for each display screen of the vehicle, which is very costly. In addition, the success rate of face recognition is affected by factors such as algorithms and environment, and there are problems such as delay and failure rate. During the account and password login process, the user needs to enter the account and password, which increases the requirements for the user's memory and is complicated to operate. During the mobile phone scan code authorization process, the user needs to first ensure that the mobile phone has logged into the account, and operate on the mobile phone to trigger the mobile phone to display the scan code interface, and also need to operate on the vehicle display screen to trigger the vehicle display screen to display the QR code. It can be seen that the user operation is relatively complicated. NFC card or key login cannot achieve flexible account binding and verify the authenticity of the user's identity, affecting the security of user data.

[0070] Thus, embodiments of the present application provide a device login method in which a first electronic device automatically locates a second electronic device. When the second electronic device is within a target three-dimensional space, the method instructs a target display screen corresponding to the target three-dimensional space to automatically log in to the second electronic device's account. Automatic device account login reduces user operational difficulty and enhances the user experience.

[0071] Figure 2 is a schematic diagram of a communication system to which the device login method provided in an embodiment of the present application is applied. As shown in Figure 2, the communication system includes a first electronic device 100 and a second electronic device 200.

[0072] Optionally, the first electronic device 100 may be a vehicle-mounted terminal or the like. The operating system installed on the first electronic device 100 includes but is not limited to Or other operating systems. The first electronic device 100 may not have an operating system installed. This application does not limit the specific type of the first electronic device 100, whether an operating system is installed, and the installed operating system.

[0073] Optionally, the second electronic device 200 may be, for example, a wearable device such as a smart watch, a smart bracelet, a smart ring, or smart glasses, or may be a mobile terminal device such as a mobile phone, a tablet computer, a laptop computer, an ultra-mobile personal computer (UMPC), a netbook, a personal digital assistant (PDA), or an artificial intelligence (AI) device. The operating system installed on the second electronic device 200 includes but is not limited to: This application does not limit the specific type of the second electronic device 200 or the installed operating system.

[0074] In some embodiments, a user brings a second electronic device 200 close to the first electronic device 100. The first electronic device 100 monitors the position of the second electronic device 200. After determining that the second electronic device 200 has entered the target three-dimensional space, the display screen corresponding to the target three-dimensional space can be triggered to log in to the account corresponding to the second electronic device 200 and load the corresponding user data. This reduces the user's device login operations and reduces the difficulty of user operation while ensuring the security of user data. Optionally, the account corresponding to the second electronic device 200 can be a device-level account, such as a Huawei account. Alternatively, the account can also be an application-level account, such as a smart life application account.

[0075] In some embodiments, as shown in FIG2 , the communication system may further include a server 300. Optionally, the server 300 may be a device or server with computing capabilities, such as a cloud server or a network server. The server 300 may be a single server, a server cluster consisting of multiple servers, or a cloud computing service center.

[0076] In some embodiments, the user may choose to log in to the same account on both the first electronic device 100 and the second electronic device 200. During the account login process, the server 300 may obtain the device identifications of the first electronic device 100 and the second electronic device 200, respectively, and confirm that the first electronic device 100 and the second electronic device 200 are trusted devices. Afterwards, the server 300 may send the device identification of the second electronic device 200 to the first electronic device 100. Subsequently, in response to the approach of the second electronic device 200, the first electronic device 100 may obtain the device identification of the second electronic device 200, and may determine that the second electronic device 200 is a trusted device, allowing automatic login to the account corresponding to the second electronic device 200.

[0077] Optionally, the first electronic device 100, the second electronic device 200, and the server 300 in the embodiment of the present application may be implemented by different devices, and the different devices may have the same, similar, or somewhat different hardware structures, such as the hardware structure shown in FIG3 .

[0078] For example, taking the first electronic device 100 having the hardware structure shown in FIG. 3 as an example, the hardware structure shown in FIG. 3 is described.

[0079] As shown in Figure 3, the first 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 wireless communication module 160, an audio module 170, a sensor module 180, a button 190, a motor 191, a camera 193, and a display screen 194, etc.

[0080] It should be understood that the structures illustrated in the embodiments of the present application do not constitute a specific limitation on the first electronic device 100. In other embodiments of the present application, the first electronic device 100 may include more or fewer components than shown, or may combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

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

[0082] The controller can generate operation control signals according to the instruction operation code and timing signal to complete the control of instruction fetching and execution.

[0083] Processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in processor 110 is a cache memory. This memory can store instructions or data that have just been used or are being recycled by processor 110. If processor 110 needs to use the same instruction or data again, it can directly access the memory. This avoids duplicate accesses, reduces processor 110 latency, and thus improves system efficiency.

[0084] 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.

[0085] The MIPI interface can be used to connect the processor 110 to peripheral devices such as the display screen 194 and the camera 193. MIPI interfaces include the camera serial interface (CSI) and the display serial interface (DSI). In some embodiments, the processor 110 and the camera 193 communicate via the CSI interface to implement the camera function of the first electronic device 100. The processor 110 and the display screen 194 communicate via the DSI interface to implement the display function of the first electronic device 100.

[0086] The USB interface 130 is an interface that complies with USB standards and specifications, and may be a Mini USB interface, a Micro USB interface, a USB Type-C interface, or the like. The USB interface 130 can be used to connect a charger to charge the first electronic device 100, or to transfer data between the first 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 to other terminal devices, such as AR devices.

[0087] It is understood that the interface connection relationship between the modules illustrated in the embodiments of the present application is merely an illustrative description and does not constitute a structural limitation on the first electronic device 100. In other embodiments of the present application, the first electronic device 100 may also adopt a different interface connection method from the above embodiments, or a combination of multiple interface connection methods.

[0088] The wireless communication function of the first electronic device 100 can be implemented through an antenna, a wireless communication module 160, a modem processor, a baseband processor, and the like.

[0089] Antennas are used to transmit and receive electromagnetic wave signals. Each antenna in the first electronic device 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example, antennas can be reused as diversity antennas for wireless local area networks. In other embodiments, antennas can be used in conjunction with tuning switches.

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

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

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

[0093] The first electronic device 100 implements display functionality through a GPU, display screen 194, and an application processor. The GPU is a microprocessor for image processing that connects the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 may include one or more GPUs that execute program instructions to generate or modify display information.

[0094] The display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel. The display panel can be manufactured using a liquid crystal display (LCD), for example, an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode or an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), Mini-LED, Micro-LED, Micro-OLED, quantum dot light-emitting diodes (QLED), etc. In some embodiments, the first electronic device 100 may include one or N display screens 194, where N is a positive integer greater than 1.

[0095] For example, as shown in FIG1 , a first electronic device 100 is provided with multiple display screens, such as a central control screen 11 on the center console, a display screen 12 in front of the passenger in the front passenger seat (also referred to as the front passenger), a display screen 13 in front of the left rear passenger, and a display screen 14 in front of the right rear passenger. It is understood that the electronic device may also include other display screens, such as an instrument screen on the dashboard, a display screen on the roof, a display screen on the window, etc.

[0096] In some embodiments, the display screen 194 may also be integrated with an audio output module for playing audio. For example, the display screen in front of the rear passenger on the left side of the display screen 194 may be integrated with an audio output module. During video or audio playback, the display screen may output audio through the audio output module. Alternatively, the first electronic device 100 may be configured with multiple audio modules 170, and different audio modules 170 may be used with different display screens 194 to play audio from different display screens 194.

[0097] 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 first electronic device 100. The external memory card communicates with the processor 110 via the external memory interface 120 to implement data storage functions. For example, files such as music and videos can be stored in the external memory card.

[0098] The internal memory 121 can be used to store computer executable program codes, which include instructions. The internal memory 121 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area may store data created during the use of the first electronic device 100 (such as audio data, a phone book, etc.), etc. In addition, the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc. The processor 110 executes various functional applications and data processing of the first electronic device 100 by running instructions stored in the internal memory 121 and / or instructions stored in a memory provided in the processor.

[0099] The audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signals. The audio module 170 can also be used to encode and decode audio signals. In some embodiments, the audio module 170 can be set in the processor 110, or some functional modules of the audio module 170 can be set in the processor 110. The first electronic device 100 can use the audio module 170, such as music playback and recording. The audio module 170 may include a speaker, a receiver, a microphone, a headphone jack, and an application processor to implement audio functions.

[0100] In some embodiments, the first electronic device 100 may receive a user voice command via the audio module 170, and then analyze the voice command to obtain audio information. Furthermore, in response to the voice command, the first electronic device 100 may also obtain display information corresponding to each display screen. The first electronic device 100 may then match the audio information with the display information to determine the target display screen corresponding to the display information that matches the audio information. The first electronic device 100 may then execute the voice command on the target display screen.

[0101] The sensor module 180 may include a pressure sensor, a gyro sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a distance sensor, a proximity light sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, and the like.

[0102] The buttons 190 include a control button, a power button, a volume button, etc. The buttons 190 may be mechanical buttons or touch buttons. The first electronic device 100 may receive key inputs and generate key signal inputs related to user settings and function control of the first electronic device 100.

[0103] The following takes the first electronic device 100 as a car computer, the second electronic device 200 as a smart watch, and the server 300 as a server as an example to introduce in detail the device login method provided in the embodiment of the present application.

[0104] Figure 4 is a flow chart of a device login method provided in an embodiment of the present application. It should be noted that the method is not limited to the specific sequence shown in Figure 4 and below. It should be understood that in other embodiments, the order of some steps in the method can be interchanged according to actual needs, or some steps can be omitted or deleted. The method includes the following steps:

[0105] S401. The server obtains a first account corresponding to the smart watch.

[0106] The first account can be a device-level account or an application-level account. For example, the first account is a Huawei account. When the smartwatch is powered on for the first time, in response to the user's login operation, the user logs in to the Huawei account through interaction with the server. Subsequently, when the smartwatch is powered on again after being shut down, the user can automatically log in to the Huawei account. For another example, the first account can be a smart life application account.

[0107] In some embodiments, during the process of logging into the first account on the smartwatch, the server can obtain the device identification of the smartwatch based on the account login request sent by the smartwatch. After the device login to the first account is verified, the server can identify the smartwatch as a trusted device.

[0108] In some examples, the server maintains a whitelist corresponding to the first account, and the whitelist is used to save the device identifiers of electronic devices in which the first account is logged in. It should be understood that different electronic devices can log in to the same account. In some examples, after the server determines that the smartwatch is a trusted device, such as after the smartwatch completes the account login, it establishes a binding relationship between the device identifier of the smartwatch and the first account, and saves the binding relationship to the whitelist corresponding to the first account. In some examples, when the smartwatch is the device for logging in to the first account for the first time (such as when the user creates the first account through the smartwatch), the server creates a whitelist corresponding to the first account in response to the account login request sent by the smartwatch.

[0109] Exemplarily, in response to an account login request sent by a smartwatch, the server determines that the first account on the smartwatch is logged in, and then records the binding relationship between the smartwatch's device identifier and the first account in a whitelist. Optionally, if the smartwatch subsequently logs out of the first account, such as when the user instructs the smartwatch to log out or the smartwatch automatically logs out after a long period of inactivity, the server obtains the change in the smartwatch's first account login status and confirms that the first account corresponding to the smartwatch is not logged in. The server then obtains the whitelist corresponding to the first account and deletes the binding relationship between the smartwatch's device identifier and the first account recorded in the whitelist. Optionally, if the smartwatch subsequently logs in to the first account again, the server may add the binding relationship between the smartwatch's device identifier and the first account to the first account's whitelist in response to the smartwatch being logged in.

[0110] In some embodiments, the smartwatch does not have to be in a logged-in state for the first account, and the server can also obtain the binding relationship between the device identifier of the smartwatch and the first account. Optionally, the smartwatch has never been logged in to the first account, or the smartwatch is in a logged-in state for the first account. For example, the mobile phone (or other electronic device) is logged in to the first account, and detects the user's operation of adding the smartwatch as a trusted device corresponding to the first account, that is, detects the account authorization operation, and sends a trusted device addition request to the server. Accordingly, the server can establish a binding relationship between the first account and the device identifier of the smartwatch based on the trusted device addition request, and add the binding relationship to the whitelist corresponding to the first account. Optionally, in the current scenario, the whitelist includes at least the binding relationship between the device identifier of the mobile phone and the first account, and the binding relationship between the device identifier of the smartwatch and the first account.

[0111] S402: The vehicle computer sends an account login request to the server, where the account login request carries the second account.

[0112] S403: The server obtains a whitelist corresponding to the second account, where the whitelist includes the first account associated with the second account.

[0113] Among them, the second account is the owner's account, or the owner's authorized account.

[0114] For example, the vehicle's owner is user A. In response to user A's operation, the vehicle's onboard computer (or other electronic device) creates a second account for managing vehicle data. This second account is then referred to as the vehicle owner account. Alternatively, during the account creation process, the server creates the second account in response to the vehicle's request and sets it as the vehicle owner account.

[0115] For example, a rental company may own a vehicle and create an owner account. Subsequently, user A rents the vehicle. With authorization from the owner account, user A's second account is granted permission to manage the vehicle's data. This second account is then designated as the owner's authorized account. Optionally, during the account authorization process, the server completes the account authorization based on a request from the electronic device logged into the owner account, setting the second account as the owner's authorized account.

[0116] In some embodiments, the vehicle computer can log in to one or more accounts based on user operations. A second account logged in on the vehicle computer for managing vehicle data is described as a primary account, and other device accounts (such as the first account) logged in on the vehicle computer are described as secondary accounts.

[0117] For example, if the vehicle computer is already logged into a primary account (e.g., a second account), and the vehicle computer detects a user requesting to log into the first account on the passenger screen, it sends an account login request containing the first account to the server. The server responds to the account login request and determines that the first account is a secondary account.

[0118] In some examples, after the vehicle computer determines that the display screen is logged in for the first time with a secondary account (e.g., a first account), it may allocate a user space for the first account to store the received user data of the first account, such as settings for functions such as air conditioning and seats, application data, etc. Subsequently, through the contents described below in steps S501-S504, after the vehicle computer automatically logs in the first account on the target display screen, it may load the user space corresponding to the first account on the target display screen.

[0119] In some examples, the server receives an account login request from the vehicle computer and obtains the second account carried therein. The server confirms that the second account is the primary account, that is, the owner account or the owner's authorized account, and can obtain a whitelist corresponding to the second account so that the vehicle computer can automatically authorize the automatic login of other accounts in the whitelist. Among them, the entire vehicle data managed by the master account includes user data corresponding to different user spaces corresponding to different slave accounts. Therefore, the master account has the authority to authorize other slave accounts to automatically log in to ensure data security. Based on this, the server will confirm the whitelist corresponding to the master account only after receiving the account login request from the master account.

[0120] In some embodiments, when the vehicle computer (or other electronic device) is already logged into the second account, in response to a user operation, it can set the first account as a trusted account. The vehicle computer can establish an association between the first account and the second account and send the association to the server. Alternatively, the vehicle computer (or other electronic device) sends a trusted account add request to the server and includes the first account in the trusted account add request. Then, in response to the trusted device add request, the server can establish and save the association between the second account currently logged into the vehicle computer and the first account, and then the server can send the association to the vehicle computer.

[0121] For example, in response to a user action, a mobile phone launches a vehicle management app, which is used to manage vehicle data and operate the vehicle. The second account is already logged into the vehicle management app. Subsequently, in response to the user adding a trusted account in the vehicle management app, the mobile phone retrieves the first account and sends a trusted account addition request containing the first account to the server. The server then establishes and stores an association between the second account and the first account, completing the trusted account addition.

[0122] In some embodiments, when a vehicle computer (or other electronic device) is already logged into a second account and detects a user logging into another account (such as a first account), it sends an account login request to a server, including the first account in the request. After authorizing the vehicle computer to log into the first account, the server can establish an association between the second account (the primary account) currently logged into the vehicle computer and the first account (the secondary account).

[0123] In some embodiments, the associated master and slave accounts share a whitelist. For example, after establishing an association between a first account and a second account, the server may obtain Whitelist 1 corresponding to the first account and establish a corresponding association between the second account and Whitelist 1. This way, the second account not only corresponds to Whitelist 2 originally associated with it, but also to Whitelist 1. Whitelist 1 includes the binding relationship between the device identifier of an electronic device logged in with the first account and the first account, while Whitelist 2 includes the binding relationship between the device identifier of an electronic device logged in with the second account and the second account. The whitelist corresponding to the second account then includes both Whitelist 1 and Whitelist 2. Alternatively, the server may establish a corresponding association between the second account and a shared whitelist formed by combining Whitelist 1 and Whitelist 2. That is, if the first and second accounts are associated, the first and second accounts may share both the whitelist corresponding to the first account and the whitelist corresponding to the second account. In response to the account login request sent by the vehicle computer, the server obtains a whitelist corresponding to the second account, including the second account and the first account associated with the second account.

[0124] It should be understood that step S401 occurs before step S402, but step S401 is not always included before step S402. For example, after obtaining the first account corresponding to the smartwatch, the server may detect one or more account login requests sent by the vehicle computer. S404: The server sends a whitelist to the vehicle computer.

[0125] In some embodiments, after obtaining the whitelist corresponding to the second account, the server feeds the whitelist back to the vehicle computer. Correspondingly, the vehicle computer receives the whitelist fed back by the server.

[0126] In some examples, in steps S402-S404, the server, in response to the account login request sent by the vehicle computer, may provide the vehicle computer with a whitelist corresponding to the second account currently logged in. Alternatively, the vehicle computer may separately send a request to the server to obtain a trusted device (or trusted account), where the trusted device is an electronic device that is logged in with a first account associated with the second account. In response to the request, the server obtains the first account associated with the second account and sends the whitelist corresponding to the first account to the vehicle computer.

[0127] In some examples, if the server determines that no account associated with the second account exists, the server will not send the whitelist to the vehicle computer. Alternatively, the server may send a whitelist specifically corresponding to the second account to the vehicle computer.

[0128] S405. The vehicle computer saves the whitelist.

[0129] In some embodiments, the vehicle computer receives a whitelist sent by the server and saves the whitelist.

[0130] Optionally, the whitelist sent by the server includes the first account and the second account. Alternatively, the whitelist sent by the server also includes an association between the first account and the device identifier of the smartwatch.

[0131] It should be understood that the whitelist can also be described as a trusted device list, etc.

[0132] In some examples, the vehicle computer maintains a whitelist that includes at least one piece of trusted device information (such as the device identifier of a smartwatch). The trusted device information indicates that the electronic device is a trusted device that the user has authorized to log in to the first account and the first account is currently logged in. Therefore, based on this electronic device, the vehicle computer can subsequently determine that the user carrying the electronic device is trustworthy, ensuring the security of automatic login on the vehicle display.

[0133] In this way, the car computer ensures the security of subsequent automatic login of the target display screen by maintaining the white list.

[0134] In some embodiments, the server determines that the whitelist is updated and automatically sends the updated whitelist to the first electronic device.

[0135] For example, after a third electronic device logs in to the first account, the server establishes a binding relationship between the third electronic device's device identifier and the first account, adds the binding relationship to a whitelist, and sends the updated whitelist to the first electronic device. This way, if the third electronic device subsequently approaches the first electronic device and enters the target three-dimensional space, the first electronic device can also automatically log in to the first account through the target display corresponding to the target three-dimensional space.

[0136] The following is a detailed description of the automatic login process for the target display.

[0137] Figure 5 is a flow chart of another device login method provided in an embodiment of the present application. It should be noted that the method is not limited to the specific sequence shown in Figure 5 and below. It should be understood that in other embodiments, the order of some steps in the method can be interchanged according to actual needs, or some steps can be omitted or deleted. The method includes the following steps:

[0138] S501: The vehicle computer and the smart watch establish a communication connection.

[0139] In some embodiments, a wireless communication connection can be established between the vehicle computer and the smartwatch. The wireless communication technology used to establish the wireless communication connection includes, but is not limited to, at least one of the following: ultra-wide band (UWB), Bluetooth (BT) (e.g., traditional Bluetooth or Bluetooth low energy (BLE)), wireless local area networks (WLAN) (e.g., wireless fidelity (Wi-Fi) networks), near field communication (NFC), Zigbee, frequency modulation (FM), infrared (IR), star flash, etc.

[0140] In some examples, the car computer and the smartwatch support proximity discovery. For example, when the smartwatch is close to the car computer, the car computer and the smartwatch can discover each other and then establish a wireless communication connection such as a UWB connection, a Bluetooth connection, or a Wi-Fi peer-to-peer (P2P) connection.

[0141] S502: The vehicle computer monitors the location of the smart watch.

[0142] In some embodiments, after establishing a communication connection with the smart watch, the vehicle computer can monitor the location of the smart watch to subsequently determine whether to trigger automatic login to the target display screen.

[0143] In some examples, the car computer monitors the location of the smart watch through functions such as UWB ranging, Bluetooth ranging, and star flash ranging.

[0144] S503: The vehicle computer determines whether the smartwatch has entered the first target three-dimensional space of the target display screen. If so, step S504 is executed; if not, the process returns to step S502 to continue position monitoring of the smartwatch.

[0145] In some embodiments, the vehicle is equipped with at least one display screen, and the vehicle computer establishes a communication connection with the at least one display screen, which can be a wired or wireless communication connection. The vehicle computer divides the vehicle interior space based on the configuration of the display screens in the vehicle. For example, after determining a calibration point based on the positional relationship between the display screen and the seat position, the vehicle computer divides a certain three-dimensional space centered on the calibration point, such that the corresponding display screen is located within the three-dimensional space. In this way, when the vehicle computer subsequently determines that a trusted device (such as a smartwatch) has entered a first target three-dimensional space, it can determine that the user carrying the smartwatch is likely to operate the target display screen corresponding to the first target three-dimensional space and can therefore instruct the target display screen to log in to the first account (i.e., execute step S504). If no smartwatch has entered the first target three-dimensional space, the vehicle computer can determine that no user needs to operate the target display screen and simply continue to monitor the location of the smartwatch (i.e., execute step S502). For example, if the user is currently boarding the vehicle and has not yet sat down, it is temporarily unable to confirm the target display screen that the user may operate.

[0146] Exemplarily, as shown in FIG6 , the front row of the vehicle includes a driver's seat and a co-pilot seat. Generally, a display screen 61 is provided in front of the passenger in the co-pilot seat (also referred to as the front passenger), and the display screen 61 is generally operated by the passenger in the co-pilot seat. Therefore, the three-dimensional space corresponding to the display screen 61 is generally used to locate whether there is a passenger in the co-pilot seat. Only when there is a passenger can the display screen 61 be operated. For example, the screen center of the display screen 61 is set as a calibration point in advance, and a spherical three-dimensional space 62 corresponding to the display screen 61 is divided with the calibration point as the center of the circle. Afterwards, after detecting a trusted device (such as a smart watch), the vehicle computer can monitor whether the trusted device will enter the three-dimensional space 62 to determine whether the display screen 61 is likely to be operated, thereby determining whether the display screen 61 needs to automatically log in to the trusted device account.

[0147] As another example, as shown in FIG6 , a central control screen 63 is provided on the center console. The central control screen 63 is generally located in the middle position in front of the driver's seat and in front of the co-driver's seat, and is generally operated by the driver. Therefore, the three-dimensional space corresponding to the central control screen 63 is generally used to locate whether there is a driver in the driver's seat. Only when there is a driver can the central control screen 63 be operated. For example, the left center position of the screen of the central control screen 63 is set as a calibration point in advance, and the spherical three-dimensional space 64 corresponding to the central control screen 63 is divided with the calibration point as the center of the circle. Afterwards, after the vehicle computer detects a trusted device (such as a smart watch), it can monitor whether the trusted device will enter the three-dimensional space 64 to determine whether the central control screen 63 is likely to be operated, so as to determine whether the central control screen 63 needs to automatically log in to the trusted device account.

[0148] In some embodiments, the three-dimensional spaces corresponding to different display screens in the vehicle do not overlap. In this way, the vehicle computer can determine a unique target display screen based on the three-dimensional space where the smartwatch is located.

[0149] Optionally, at least a portion of the display screen is located in the three-dimensional space corresponding to the display screen. For example, the entire display screen 61 is located in the corresponding three-dimensional space 62, and a portion of the central control screen 63 is located in the corresponding three-dimensional space 64.

[0150] For example, after the car computer automatically logs in to the first account, it may display a prompt message prompting the user to confirm the login to the first account. Therefore, at least the display area of ​​the display screen where the prompt message is displayed must be located within the three-dimensional space corresponding to the display screen. This way, when the user confirms the prompt message, they can confirm that the first account corresponding to the prompt message is the login account of the smartwatch they are wearing, without any misunderstanding.

[0151] Optionally, the embodiment of the present application does not display the shape of the three-dimensional space. For example, the three-dimensional space is a sphere, a cube, an irregular solid shape, etc.

[0152] S504: The vehicle computer instructs the target display screen to log in to the first account of the smart watch.

[0153] In some embodiments, the vehicle computer determines that a smartwatch has entered a first target three-dimensional space of a target display screen and that the user currently wearing the smartwatch is close to the target display screen, potentially enabling operation of the target display screen. Therefore, the vehicle computer may request the smartwatch's device identifier. Based on the obtained smartwatch device identifier, the vehicle computer retrieves the first account corresponding to the device identifier from a locally stored whitelist. The vehicle computer then instructs the target display screen to automatically log in to the first account. Alternatively, the vehicle computer instructs the target display screen to automatically log in to the first account in the background.

[0154] For example, as shown in Figure 7, the smartwatch approaches the target display screen and enters the first target three-dimensional space. Optionally, the first target three-dimensional space is, for example, a sphere with a radius of 30 centimeters. After entering the first target three-dimensional space, the distance between the smartwatch and the target display screen is less than 30 centimeters. This relatively close distance makes it possible for the user wearing the smartwatch to operate the target display screen. Therefore, the vehicle computer instructs the target display screen to log in to the first account of the smartwatch.

[0155] In some examples, the vehicle computer instructs the target display screen to log in to the first account, and instructs the target display screen to load the user space corresponding to the first account, so that the target display screen obtains the corresponding user data, that is, the user can subsequently operate these user data on the target display screen.

[0156] In some examples, the target display screen logs in to the first account in the background to indicate that the user does not need to be aware of the first account login process and does not need to participate in the user operation, thereby reducing the difficulty of user operation. Subsequently, if the user needs to operate the target display screen, they can directly operate the user data corresponding to the first account.

[0157] In this way, the display screen account login no longer relies on the user's active login, effectively reducing the difficulty of user operation. In addition, through the maintenance of the whitelist, the security of user data is also guaranteed during the automatic login process.

[0158] In some embodiments, the vehicle computer can obtain the device identifier of the smartwatch during the process of establishing a communication connection with the smartwatch. In some examples, the vehicle computer and the smartwatch establish a communication connection based on the device identifier. Alternatively, after establishing a communication connection with the smartwatch, the vehicle computer can request the device identifier of the smartwatch based on the communication connection. The vehicle computer then monitors the location of the smartwatch.

[0159] That is, the vehicle computer may first monitor the location of the smartwatch, determine that the smartwatch is within the first target three-dimensional space, and then obtain the device identification of the smartwatch. Alternatively, the vehicle computer may first obtain the device identification of the smartwatch, then monitor the location of the smartwatch to determine whether the smartwatch is within the first target three-dimensional space.

[0160] In some embodiments, the vehicle computer matches the acquired device identifier of the smartwatch with the trusted device information in a maintained whitelist. If the match is successful, that is, the device identifier is stored in the whitelist, the smartwatch can be determined to be a trusted device. If the match fails, that is, the device identifier is not stored in the whitelist, the smartwatch can be determined to be an untrusted device. Optionally, after determining that the smartwatch is a trusted device, the vehicle computer instructs the target display screen to log in to the first account of the smartwatch in the background. In some examples, if the vehicle computer determines that the smartwatch is not a trusted device after establishing a communication connection with the smartwatch, the vehicle computer may not monitor the location of the smartwatch, thereby saving power consumption.

[0161] In some embodiments, while the vehicle computer is monitoring the smartwatch's location, the first account on the smartwatch is logged in, further ensuring the security of subsequent loading of user data onto the target display. While establishing a communication connection with the smartwatch, the vehicle computer can also obtain the smartwatch's account login information, such as whether the account is logged in and the logged-in account information. The vehicle computer then obtains the stored binding relationship between the device identifier and the account. Based on the smartwatch's account login information, the vehicle computer determines whether the account stored on the vehicle computer that is bound to the smartwatch's device identifier is the currently logged-in account on the smartwatch. If the account stored on the vehicle computer that is bound to the smartwatch's device identifier is the same as the currently logged-in account on the smartwatch, the vehicle computer monitors the smartwatch's location again to determine whether it is necessary to subsequently instruct the target display to log in to the first account. Otherwise, the vehicle computer does not need to monitor the smartwatch's location again. This ensures the security of the user data associated with the first account and avoids power consumption caused by unnecessary location monitoring.

[0162] For example, user A owns a smartwatch. In response to user A's account 1 being logged in on the smartwatch, the server determines the smartwatch as a trusted device and establishes a binding relationship between the smartwatch's device identifier and account 1. The vehicle's primary account is account 2, which is associated with account 1. The server sends a whitelist to the vehicle that includes the binding relationship between the smartwatch's device identifier and account 1. Subsequently, user B uses user A's smartwatch and brings it near the vehicle. In one scenario, user B instructs the smartwatch to log in to user B's account 3. Based on the stored binding relationship, the vehicle's computer determines that the account 1 corresponding to the smartwatch's device identifier is different from the currently logged-in account 3. Therefore, it is not necessary to instruct the target display to log in to account 1, thereby preventing the target display from loading user A's user data and compromising the security of user A's user data. In another scenario, the smartwatch is logged out of account 1 and is not logged into any other account. In response to the smartwatch not being logged in, the vehicle's computer also does not instruct the target display to log in to account 1, thereby preventing the target display from loading user A's user data and compromising the security of user A's user data.

[0163] In some embodiments, the vehicle computer stores a whitelist containing a first account and a second account. After determining that the smartwatch has entered the first target three-dimensional space of the target display screen, the vehicle computer obtains the first account logged in by the smartwatch. The vehicle computer determines that the first account is in the whitelist and is a trusted account. Therefore, the vehicle computer can instruct the target display screen to log in with the first account. This means that the vehicle computer can automatically log in accounts without verifying the device ID of the smartwatch.

[0164] In some embodiments, the display screens of some vehicles are also equipped with a lock screen function, and the lock screen verification information matches the first account. For example, after the device logs in to the first account, it is in a lock screen state by default, and the user sets the lock screen verification information such as a numeric or alphabetic password, a gesture password, or face recognition according to needs. Subsequently, after other devices log in to the first account, these lock screen verification information will still be effective to ensure the security of the user data corresponding to the first account. Therefore, in order to reduce the difficulty of the user's operation during the unlocking verification process after the target display screen logs in to the first account, the vehicle computer can continue to monitor the location of the smart watch to determine whether the user currently unlocking the target display screen is the user carrying the smart watch, and determine whether it can be automatically unlocked, thereby further ensuring the security of user data.

[0165] The following describes in detail the automatic unlocking process of the target display.

[0166] FIG8 is a flow chart of another device login method provided by an embodiment of the present application. It should be noted that the method is not limited to FIG8 and the specific sequence described below. It should be understood that in other embodiments, the order of some steps in the method can be interchanged according to actual needs, or some steps can be omitted or deleted. As shown in FIG8, after step S504, the method further includes the following steps:

[0167] S801. The vehicle computer continues to monitor the location of the smart watch.

[0168] In some embodiments, after the vehicle computer determines that the smart watch has entered the first target three-dimensional space, it can continue to monitor the position of the smart watch to determine whether the user carrying the smart watch will get closer to the target display screen.

[0169] In some examples, a smartwatch is generally worn on a user's wrist, so the position of the smartwatch is monitored. If the smartwatch moves closer to the target display, it can be determined that the user needs to operate the target display, such as unlocking the target display.

[0170] S802: The vehicle computer determines whether the smartwatch has entered the second target three-dimensional space of the target display screen. If so, execute step S803; if not, return to step S801 and continue to monitor the position of the smartwatch.

[0171] In some embodiments, the first target 3D space and the second target 3D space partially overlap, and the target display screen is located within this overlapping space. For example, the second target 3D space is a 3D space centered around the same calibration point as the first target 3D space. Optionally, the second target 3D space is smaller than the first target 3D space. Optionally, the first target 3D space includes the second target 3D space.

[0172] For example, the first target three-dimensional space corresponding to the display screen in front of the passenger on the co-pilot seat is a sphere with a radius of 30 cm and the screen center of the display screen as the center of the circle; the second target three-dimensional space corresponding to the display screen is a sphere with a radius of 3 cm and the screen center of the display screen as the center of the circle.

[0173] For example, as shown in FIG9 , after determining that the smartwatch has entered the first target three-dimensional space, the vehicle computer continues to monitor the smartwatch's position and determines that the smartwatch has moved closer to the target display. Subsequently, the vehicle computer determines that the smartwatch has entered the second target three-dimensional space and determines that the user wearing the smartwatch needs to operate the target display.

[0174] S803: The vehicle computer detects the user's unlocking operation on the target display screen and automatically unlocks the target display screen.

[0175] The unlocking operation includes, for example, gesture operations such as sliding, clicking, and double-clicking on the target display screen, or operations on buttons corresponding to the target display screen.

[0176] In some embodiments, if the target display screen of the vehicle computer detects a user's unlocking operation and the vehicle computer determines that the smartwatch is currently located within the second target three-dimensional space, it can determine that the unlocking operation was performed by the user wearing the smartwatch. Therefore, the vehicle computer can instruct the target display screen to automatically unlock, allowing the user wearing the smartwatch to continue operating the target display screen without having to perform unlock verification. This effectively reduces user operation difficulty while ensuring user data security.

[0177] For example, the in-vehicle display screen is somewhat public, and other users may also touch the target display screen. Therefore, if another user unlocks the target display screen, unlocking verification is required for that user to ensure the security of the user data corresponding to the logged-in first account. If a user wearing a smartwatch unlocks the target display screen (e.g., the user swipes the hand wearing the smartwatch on the target display screen to unlock), the vehicle computer can determine that the smartwatch currently unlocking the target display screen is located within the second target three-dimensional space, indicating that unlocking is more secure, and can therefore instruct the target display screen to automatically unlock.

[0178] Optionally, the present embodiment does not limit the order in which steps S802 and S803 are executed. For example, after detecting the user's unlocking operation on the target display screen, the vehicle computer may determine whether the current smartwatch is within the second target three-dimensional space corresponding to the target display screen. If so, the vehicle computer may automatically unlock the target display screen. In other words, the vehicle computer may first execute step S803 and then execute step S802.

[0179] In some embodiments, after the target display screen is automatically unlocked, the user can continue to operate the target display screen, such as editing application data, adjusting seat setting parameters, etc. The vehicle computer obtains the corresponding user data and saves it to the user space corresponding to the first account. In this way, after the user enters the vehicle again, the vehicle computer can load the latest user data for the user on the corresponding display screen. It should be understood that after entering the vehicle, the user can select the required seat according to their own needs, and the seat position is random. Therefore, each time the user enters the vehicle, the target display screen determined by the vehicle computer may not be the same. In this process, the vehicle computer determines the target display screen that needs to be automatically logged in and automatically unlocked this time based on the position monitoring of the trusted device carried by the user and the determined three-dimensional space.

[0180] In some embodiments, if the vehicle computer does not detect an unlock operation within a preset period of time after determining that the smartwatch has entered the second target three-dimensional space of the target display screen, it can determine that the user does not currently need to operate the target display screen. Therefore, the vehicle computer can instruct the target display screen to automatically log out of the first account, thereby ensuring the security of the user data corresponding to the first account.

[0181] In some embodiments, after the vehicle computer determines that the user in the seat corresponding to the target display screen has gotten off the vehicle, it can instruct the target display screen to automatically log out of the first account, thereby ensuring the security of the user data corresponding to the first account. For example, the vehicle computer determines that the target display screen is the display screen configured in front of the passenger in the front passenger seat. The vehicle obtains the front passenger seat data and determines that the user has left the seat. In addition, the vehicle computer obtains the door data and determines that the door was opened and then closed. Then, the vehicle computer can determine that the front passenger passenger has left the vehicle. Therefore, the vehicle computer can instruct the display screen to log out of the first account to prevent other passengers from subsequently sitting in the front passenger seat and affecting the security of the user data corresponding to the first account. It should be understood that the vehicle computer can also use other data to determine whether the user in the seat corresponding to the target display screen has gotten off the vehicle.

[0182] In some embodiments, the device login method provided in the embodiments of the present application can be applied to other physical space scenarios in addition to the above-mentioned vehicle (smart cockpit) scenario. For example, in the smart home scenario, different first target three-dimensional spaces and second target three-dimensional spaces corresponding to different smart home devices are pre-configured. In this way, when the mobile terminal enters the first target three-dimensional space, the central control device (such as a smart home control panel) can instruct the smart home device corresponding to the first target three-dimensional space to log in to the account of the mobile terminal. Subsequently, when the mobile terminal moves closer to the smart home device and enters the second target three-dimensional space corresponding to the smart home device, the central control device can instruct the smart home device to automatically unlock (or automatically run, etc.). In this regard, the embodiments of the present application will no longer provide examples one by one.

[0183] In some examples, the smart home device may not be located within the first target three-dimensional space (or second target three-dimensional space) corresponding to the smart home device. For example, if the smart home device is a computer on a desk, the corresponding first target three-dimensional space is near the door of the room and the computer is not located within the first target three-dimensional space, and the corresponding second target three-dimensional space is near the desk and the computer is located within the second target three-dimensional space. In this way, when the user opens the door with a smart watch and the smart watch is located within the first target three-dimensional space, the central control device can instruct the computer to automatically log in to the smart watch account, and when the user moves closer to the computer and the smart watch reaches the second target three-dimensional space, it can instruct the computer to automatically unlock.

[0184] The collection, storage, use, processing, transmission, provision, and disclosure of user personal information in the technical solutions of this application are in compliance with relevant laws and regulations and do not violate public order and good morals. For example, in the technical solutions of this application, the processing of user personal information is performed with the user's authorization, which is explained here and will not be repeated below.

[0185] The above describes in detail the device login method provided by the embodiment of the present application in conjunction with Figures 4 to 9. The following describes in detail the first electronic device provided by the embodiment of the present application in conjunction with Figure 10.

[0186] In one possible design, Figure 10 is a schematic diagram of the structure of a first electronic device provided in an embodiment of the present application. As shown in Figure 10, the first electronic device 1000 may include a transceiver unit 1001 and a processing unit 1002. The first electronic device 1000 may be used to implement the functions of the vehicle computer involved in the above method embodiment.

[0187] Optionally, the transceiver unit 1001 is used to support the first electronic device 1000 to execute S402 and S404 in Figure 4; and / or, support the first electronic device 1000 to execute S501 and S502 in Figure 5; and / or, support the first electronic device 1000 to execute S801 in Figure 8.

[0188] Optionally, the processing unit 1002 is used to support the first electronic device 1000 to execute S405 in Figure 4; and / or, support the first electronic device 1000 to execute S503 and S504 in Figure 5; and / or, support the first electronic device 1000 to execute S802 and S803 in Figure 8.

[0189] Among them, the transceiver unit may include a receiving unit and a sending unit, and may be implemented by a transceiver or a transceiver-related circuit component, and may be a transceiver or a transceiver module. The operations and / or functions of each unit in the first electronic device 1000 are respectively to implement the corresponding process of the device login method described in the above method embodiment. All relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional unit. For the sake of brevity, they are not repeated here.

[0190] Optionally, the first electronic device 1000 shown in Figure 10 may further include a storage unit (not shown in Figure 10) in which a program or instruction is stored. When the transceiver unit 1001 and the processing unit 1002 execute the program or instruction, the first electronic device 1000 shown in Figure 10 can perform the device login method described in the above method embodiment.

[0191] The technical effects of the first electronic device 1000 shown in FIG10 may refer to the technical effects of the device login method described in the above method embodiment, and will not be repeated here.

[0192] In addition to being in the form of the first electronic device 1000, the technical solution provided in this application may also be a functional unit or chip in the first electronic device, or a device used in conjunction with the first electronic device.

[0193] An embodiment of the present application also provides a chip system, including: a processor, the processor is coupled to a memory, the memory is used to store programs or instructions, when the program or instructions are executed by the processor, the chip system implements the method in any of the above method embodiments.

[0194] Optionally, there may be one or more processors in the chip system. The processor may be implemented in hardware or software. When implemented in hardware, the processor may be a logic circuit, an integrated circuit, etc. When implemented in software, the processor may be a general-purpose processor implemented by reading software code stored in a memory.

[0195] Optionally, the memory in the chip system may be one or more. The memory may be integrated with the processor or may be provided separately from the processor, which is not limited in the embodiments of the present application. For example, the memory may be a non-transient processor, such as a read-only memory (ROM), which may be integrated with the processor on the same chip or provided on different chips. The embodiments of the present application do not specifically limit the type of memory or the configuration of the memory and the processor.

[0196] Exemplarily, the chip system may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD) or other integrated chips.

[0197] It should be understood that each step in the above method embodiment can be completed by hardware integrated logic circuits in a processor or by software instructions. The method steps disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware processor, or by a combination of hardware and software modules in a processor.

[0198] An embodiment of the present application also provides a computer-readable storage medium, which stores a computer program. When the computer program runs on a computer, the computer executes the above-mentioned related steps to implement the device login method in the above-mentioned embodiment.

[0199] An embodiment of the present application also provides a computer program product. When the computer program product is run on a computer, it enables the computer to execute the above-mentioned related steps to implement the device login method in the above-mentioned embodiment.

[0200] In addition, embodiments of the present application further provide a device. Specifically, the device may be a component or module, and may include one or more processors and a memory connected to each other. The memory is configured to store a computer program. When the computer program is executed by one or more processors, the device performs the device login method described in each of the above method embodiments.

[0201] The apparatus, computer-readable storage medium, computer program product, or chip provided in the embodiments of the present application are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods provided above and will not be repeated here.

[0202] The steps of the method or algorithm described in conjunction with the disclosure of the embodiments of the present application can be implemented in a hardware manner or can be implemented by a processor executing software instructions. The software instructions can be composed of corresponding software modules, and the software modules can be stored in a random access memory (RAM), a flash memory, a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a register, a hard disk, a mobile hard disk, a read-only compact disc (CD-ROM) or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor so that the processor can read information from the storage medium and can write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can be located in an application specific integrated circuit (ASIC).

[0203] Through the description of the above embodiments, those skilled in the art will clearly understand that for the sake of convenience and brevity, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed; that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. The specific working processes of the above-mentioned systems, devices, and units can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

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

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

[0206] Computer-readable storage media include, but are not limited to, any of the following: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and other media that can store program code.

[0207] The above is only a specific embodiment of the present application, but the scope of protection of this application is not limited to this. Any changes or substitutions within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A device login method, characterized in that, Applied to a first electronic device, communication connections are established between the first electronic device, at least one display screen, and a second electronic device. The method includes: Obtain a first position of the second electronic device, where the second electronic device is a mobile terminal; Determine that the first position is within a first target three-dimensional space, and obtain a target display screen among the at least one display screen, where part or all of the target display screen is within the first target three-dimensional space; Log in to a first account of the second electronic device through the target display screen.

2. The method according to claim 1, wherein After logging in to the first account of the second electronic device through the target display screen, the target display screen is default in a locked screen state. The method further includes: Detect a first operation of a user on the target display screen; In response to the first operation, unlock the target display screen when a second position of the second electronic device is within a second target three-dimensional space corresponding to the target display screen; wherein, there is an overlapping space between the first target three-dimensional space and the second target three-dimensional space, and part or all of the target display screen is within the overlapping space.

3. The method according to claim 2, characterized in that, The second target three-dimensional space is smaller than the first target three-dimensional space.

4. The method according to claim 3, characterized in that, The first target three-dimensional space includes the second target three-dimensional space.

5. The method according to any one of claims 1 to 4, characterized in that, Before logging in to the first account of the second electronic device through the target display screen, the method further includes: Obtain a device identifier of the second electronic device; Obtain the first account locally saved and having a binding relationship with the device identifier.

6. The method according to claim 5, characterized in that, The logging in to the first account of the second electronic device through the target display screen includes: Obtain the account currently logged in to the second electronic device; When the first account is the same as the account currently logged in to the second electronic device, log in to the first account of the second electronic device through the target display screen.

7. The method according to any one of claims 1-6, characterized in that, Before obtaining the first position of the second electronic device, the method further includes: In response to a second operation of a user, log in to a second account through a server, where the second account is the first account or an account associated with the first account; Receive and save a whitelist sent by the server, where the whitelist includes the binding relationship between the device identifier of the second electronic device and the first account.

8. The method according to any one of claims 1-7, characterized in that, Each of the at least one display screen connected to the first electronic device is configured with a corresponding three-dimensional space, and the corresponding three-dimensional spaces of each display screen do not overlap.

9. The method according to any one of claims 1 to 8, characterized in that, The first electronic device is a vehicle-mounted device, and the at least one display screen and the first electronic device are located in the same vehicle.

10. The method according to any one of claims 1-9, characterized in that, The second electronic device is a wearable device.

11. The method according to claim 10, characterized in that, The second electronic device is a smart watch or a smart bracelet.

12. An electronic device, characterized in that, Includes: A processor and a memory, the memory is coupled to the processor, the memory is used to store computer program code, the computer program code includes computer instructions, and when the processor reads the computer instructions from the memory, the electronic device executes the method according to any one of claims 1-11.

13. A vehicle, characterized in that, Includes: The electronic device according to claim 12, and at least one display screen.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a computer program, which, when running on an electronic device, causes the electronic device to execute the method according to any one of claims 1-11.

15. A computer program product, characterized in that, When the computer program product runs on a computer, it causes the computer to execute the method according to any one of claims 1-11.

Images