Authorization method, authorization system, electronic device, and computer-readable medium

Abstract

The present application relates to the technical field of terminal electronic devices, and specifically to an authorization method, an authorization system, an electronic device, and a computer-readable medium. By identifying the relative position of a handheld device carried by a user, the handheld device suitable for the authorization operation of the user is matched for each screen in a cabin. Each screen can prompt the user to perform authorization verification by means of the matched handheld device, thereby supporting that the user can rapidly log in an account on the corresponding screen. Therefore, when the user enters the cabin and needs to log in the account on the screen in the cabin, the user can use the handheld device matched with the corresponding screen to perform authorization verification, thereby simplifying the operation process of the user logging in the account on the corresponding screen, and achieving the purpose of rapid login. Therefore, the present application is conducive to improving the user experience and also reducing the idleness of screen resources in the cabin.

Description

Authorization method, authorization system, electronic device and computer-readable medium

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on December 1, 2023, with application number 202311663178.X and application name “Authorization Method, Authorization System, Electronic Device and Computer-Readable Medium”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present invention relates to the technical field of terminal electronic equipment, and in particular to an authorization method, an authorization system, an electronic device and a computer-readable medium. Background Art

[0003] With the development of intelligent technology, physical spaces with multiple devices are gradually developing into intelligent physical spaces with human-computer interaction as the core and multi-screen linkage. This physical space can include spaces such as smart cockpits and smart homes. Taking the smart cockpit as an example, the smart cockpit that supports multiple screens and multiple users has become the mainstream development trend. The realization of multiple screens and multiple users requires that each screen of the vehicle equipment in the cockpit can support an independent login account. Therefore, users riding in the vehicle can log in to their personal account when getting on the vehicle, and can also log out of the logged-in account when getting off the vehicle in order to avoid leaking personal privacy data. The same user may need to log in to their personal account repeatedly when riding in the same seat at different times or riding in different seats to facilitate their use of the screen that is closer.

[0004] However, the current screens in the cockpit support users to log in to their accounts independently, but users are usually required to enter their account passwords to log in, or use handheld devices such as mobile phones to scan the QR code displayed on the cockpit screen to log in, which is a cumbersome operation. The method of using the near field communication (NFC) function of the car key to realize account login often only supports the main driver to quickly log in to the account and cannot support multiple users to log in. In addition, due to cost considerations, there are relatively few screens in the cockpit that are equipped with biometric recognition devices, and they cannot support multiple users to log in to their accounts through biometric recognition. The above factors, combined, lead to the multiple screens in the cockpit being easily idle because it is inconvenient for multiple users to quickly log in to their accounts, which affects the user experience and also causes a waste of screen resources.

[0005] Summary of the Invention

[0006] The present application provides an authorization method, an authorization system, an electronic device, and a computer-readable medium, which can enable a handheld device that matches the corresponding screen to perform authorization verification when a user enters a cabin and needs to log in to an account on a screen inside the cabin, thereby simplifying the operation process of the user logging in to an account on the corresponding screen and achieving the purpose of quick login.

[0007] In the first aspect, the present application provides an authorization method, which includes: detecting that the spatial position relationship between a first user device and a first screen of a first space device meets a first condition; sending a first authorization request message to the first user device, the first authorization request message being used to request login of a first account on the first screen, the first account being the account logged in on the first user device; receiving a first authorization result message, and corresponding to the first authorization result information indicating that the authorization is passed, logging in the first account on the first screen.

[0008] For example, the above-mentioned first user device can be an electronic device such as a mobile phone, tablet computer, watch, etc. carried by the user. The above-mentioned first space device can be an electronic device fixedly set in a certain space, such as a car-machine device in a smart cockpit (i.e., a vehicle cockpit). The first space device can control one or more screens, and the relative position relationship between one of the screens, such as the above-mentioned first screen and the first user device, is the above-mentioned spatial position relationship. In the present application, the above-mentioned spatial position relationship can determine the matching relationship between the user device and one or more screens controlled by the car-machine device after entering the vehicle cockpit. For example, if a user carries a mobile phone and rides in the main driving area, the present application can determine the corresponding matching between the mobile phone and the screen in the main driving area based on the spatial position relationship between the mobile phone and the screen in the main driving area. At this time, if the user clicks to log in to the account on the screen in the main driving area, the car-machine device can send an authorization request message to the mobile phone to guide the user to authorize through the mobile phone, so as to achieve the purpose of quickly logging in to the account.

[0009] It can be understood that the authorization scheme provided by the first aspect above is that when the relative position relationship between the first screen and the first user device meets certain conditions, such as when the first condition is met, an authorization request can be sent to the first user device, such as the first authorization request information mentioned above. The authorization request information allows the user to perform authorization operations through the first user device, thereby quickly logging into the account on the first space device in the space, such as quickly logging into the first account mentioned above. Among them, the first account mentioned above can be an account that the user has logged in on the first user device and intends to log in on the first screen of the first space device mentioned above. Correspondingly, the first condition mentioned above can be used to determine the area where the first user device, such as a mobile phone, is located in the vehicle cabin, and then the association between the first user device and the screen in the corresponding area (such as the first screen mentioned above) can be determined based on the first condition. That is, the first condition can be used to determine the matching relationship between the first screen and the first user device located in the associated area of ​​the screen.

[0010] It can be understood that after the user's first account is successfully logged in on the above-mentioned first screen, such as the screen of the vehicle device, the corresponding logged-in interface can be displayed.

[0011] In a possible implementation of the first aspect above, the method further includes: the first space device is set inside the physical space, and the first user device is a device that enters the physical space.

[0012] For example, the first space device may be a vehicle-mounted device disposed in a vehicle cabin, and the first user device may be an electronic device such as a mobile phone, tablet computer, or watch that a user brings into the vehicle cabin.

[0013] In a possible implementation of the first aspect above, the physical space includes a cabin of a vehicle, and detecting that the spatial position relationship between the first user device and the first screen of the first space device meets the first condition includes: detecting that the first user device is placed in a first area associated with the first screen in the cabin; and determining that the spatial position relationship between the first user device and the first screen meets the first condition.

[0014] For example, if the first user device is a mobile phone, when the user brings the mobile phone into the vehicle cabin, the vehicle-mounted device can use ultrasonic detection technology or array signal processing technology based on wireless signals to detect the location of the mobile phone, which can be in the main driver's seat area, the front passenger seat area, or the area where the rear seats are located. The vehicle-mounted device can use the speaker array in the vehicle cabin to form an ultrasonic device array to detect the area where the mobile phone is located. Furthermore, based on the detected area where the mobile phone is located, the vehicle-mounted device can determine that the spatial position relationship between the first screen associated with the area and the mobile phone meets the above-mentioned first condition. At this time, a matching relationship can be formed between the mobile phone and the above-mentioned first screen.

[0015] In a possible implementation of the first aspect above, it is detected that the spatial position relationship between the second user device and the first screen satisfies the first condition, and first authorization request information is sent to the first user device, including: when it is determined that the priority of the first user device is higher than the priority of the second user device, the first authorization request information is sent to the first user device.

[0016] For example, the first user device and the second user device may be electronic devices carried by the same user, and specifically, the first user device and the second user device may be logged into the same account. As an example, the first user device may be a mobile phone, and the second user device may be a tablet computer. The priority of the first user device and the second user device may be determined based on one or more of the security capabilities, processing capabilities, or other relevant capabilities of each device, or may be determined based on user settings, without limitation herein. For example, a mobile phone with stronger security capabilities may have a higher priority than a tablet computer with weaker security capabilities, and so on.

[0017] In a possible implementation of the first aspect above, the method is applied to a first space device or to a second space device, and when the method is applied to the second space device, logging in to the first account on the first screen includes: the second space device sends a login instruction to the first space device, wherein the login instruction is used to instruct the first space device to log in to the first account on the first screen.

[0018] That is, in some embodiments, the authorization scheme provided by the first aspect and various possible implementations can be implemented by the first spatial device. For example, the first spatial device can detect whether the spatial position relationship between the first user device and the first screen satisfies a first condition, send a first authorization request message to the first user device, and receive a first authorization result message.

[0019] In other embodiments, the authorization scheme provided by the above-mentioned first aspect and various possible implementations can be implemented by another electronic device, such as the above-mentioned second space device, which can be, for example, another vehicle-mounted device in the vehicle cabin. For example, the second space device can detect whether the spatial position relationship between the above-mentioned first user device and the first screen meets the first condition, send a first authorization request message to the first user device, and receive a first authorization result message, etc. At this time, a communication connection can be established between the second space device and the first space device, and various types of data can be transmitted to each other, including data related to the spatial position relationship and information data such as authorization requests and authorization results. In this scenario, the second space device can send a corresponding login instruction to the first space device based on the received first authorization result information to log in the user's first account on the first screen. It can be understood that after the login is completed, the corresponding interface after the successful login can be displayed on the first screen, and there is no limitation here.

[0020] It can be understood that in the above-mentioned scenario where the authorization scheme provided by this application is implemented by the second space device, the spatial position relationship between the first user device and the first screen can also be detected by the first space device and the detection result can be sent to the second space device. When the second space device receives the first authorization result information, it can also send the information to the first space device. There is no restriction here.

[0021] In a possible implementation of the first aspect above, when it is detected that the spatial position relationship between the first user device and the first screen of the first space device meets the first condition, the method includes: sending a first authorization request message to the first user device, and displaying a first interface on the first screen, wherein the first interface is used to prompt the user to perform an authorization confirmation operation on the first user device.

[0022] For example, the first space device or the second space device may display a prompt interface, such as the first interface, on the first screen operated by the user at the same time or before sending the first authorization request information to the first user device. The prompt interface may prompt the user to pick up the first user device such as a mobile phone to perform an authorization confirmation operation. In other embodiments, the authorization confirmation operation may also be described as an authorization operation. The prompt interface or the first interface may be, for example, the prompt interface shown in FIG2a or FIG2b below.

[0023] In some embodiments, the first interface may include a control indicating the selection of an authorized device, such as selection control 212 on prompt interface 210 shown in FIG. 2a below, or selection control 232 on prompt interface 230 shown in FIG. 2b below. When a user clicks the control indicating the selection of an authorized device on the first interface, the first screen may display a list of available devices in the current vehicle cabin. The list of available devices may include device information corresponding to multiple user devices, and the spatial relationship between each user device and the first screen satisfies the first condition.

[0024] For example, if a user brings multiple devices such as a mobile phone, tablet, and watch onto a vehicle, and the first user device is the mobile phone placed in the driver's seat, the device information displayed in the optional device list may include the mobile phone and other devices placed in the driver's seat. These user devices can be carried by the same user sitting in the corresponding seat, or they can be carried by multiple users in other seats in the front or rear seats, without limitation.

[0025] In other embodiments, the above-mentioned optional device list may also display device information of devices placed in other areas in the vehicle cabin, including device information of devices placed in the co-pilot area and device information of devices placed in the rear seat area, etc., without limitation here.

[0026] As an example, if the above-mentioned first screen is a display screen in the main driver's area, the area corresponding to the first screen may be the front main driver's area and the front passenger's area in the vehicle's cabin, that is, at this time, the first screen of the vehicle-mounted device can display user devices such as mobile phones placed in the main driver's area or the front passenger's area. If the above-mentioned first screen is a display screen in the rear seat area, the area corresponding to the first screen may be the rear seat area in the vehicle's cabin, that is, at this time, the first screen of the vehicle-mounted device can display user devices such as mobile phones placed in the rear seat area. In other embodiments, the above-mentioned first screen may also display user devices in various areas of the vehicle's cabin in order according to the degree of matching corresponding to the relative positions, which is not limited here.

[0027] In a possible implementation of the first aspect above, before sending the first authorization request information to the first user device, the method also includes: displaying an optional device list on the first screen, the optional device list including device information of multiple user devices, wherein the spatial position relationship between the multiple user devices and the first screen satisfies the first condition, and the multiple user devices include the first user device; and sending the first authorization request information to the first user device, including: sending the first authorization information to the first user device when it is detected that the user selects the first user device.

[0028] For example, before sending authorization request information to a user device such as a mobile phone, the vehicle-mounted device may display a list of optional devices for the user to select an authorized device. The device information displayed in the optional device list may include device information corresponding to the mobile phone or tablet computer carried by the user. Taking the first screen as the screen of the vehicle-mounted device as an example, the vehicle-mounted device may send the first authorization request information to the mobile phone based on the priority of different devices, such as a mobile phone. The vehicle-mounted device may also select a tablet computer as the user device for authorization operations according to user instructions. In this case, the vehicle-mounted device sends the first authorization request information to the tablet computer. This is not limited here.

[0029] It is understood that in some embodiments, the vehicle-mounted device may also display the first interface prompting the user to perform the authorization operation on the first screen when sending the first authorization request information to a higher-priority device, such as a mobile phone. The first interface includes the control for selecting the authorized device. When it is detected that the user clicks the control and selects another user device, such as a tablet, from the list of selectable devices, the vehicle-mounted device may further send the authorization request information to the tablet. This is not limited to this.

[0030] In a possible implementation of the first aspect above, it is detected that the spatial position relationship between the third user device and the second screen of the first space device meets the second condition; a second authorization request message is sent to the third user device, and the second authorization request message is used to request to log in the second account on the second screen, and the second account is the account logged in on the third user device; the second authorization result information is received, and the authorization is passed corresponding to the second authorization result information, and the second account is logged in on the second screen.

[0031] It can be understood that the above-mentioned second condition may be the same as the above-mentioned first condition or may be different from the above-mentioned first condition, and there is no limitation on this. The above-mentioned second condition may be used to determine the matching relationship between the above-mentioned second screen and the user device carried by another user. If the user of the user device corresponding to the above-mentioned first screen is sitting in the main driving area, the other user may, for example, be sitting in the back seat of the vehicle cabin, and the corresponding above-mentioned second screen may be the screen in the back area. In other embodiments, the other user may also be sitting in the seat in the co-pilot area, and the corresponding above-mentioned second screen may be the screen in the co-pilot area, and there is no limitation on this.

[0032] In a possible implementation of the first aspect above, the relevant information of the first account is stored in the server; and the first authorization result information includes the relevant information of the first account.

[0033] For example, the above-mentioned server can be an electronic device running a platform such as an account cloud. The server can store account-related information that users register and log in through user devices such as mobile phones, including account numbers, passwords, etc. In order to facilitate the management of each user's account login status and security, the server can record the login information of each account on different electronic devices. At this time, after the user logs in to the account on the mobile phone, he can use the mobile phone for identity authentication based on the present application solution, and authorize the login of the same account on the first screen of the above-mentioned first space device, such as authorizing the login of the account on the screen in the main driving area of ​​the car device. At this time, the mobile phone can verify the biometric information entered by the user, confirm the user's identity, and send the confirmation result to the server or the account cloud after confirming that the identity is legal. The server can then send the above-mentioned first authorization result information to the screen of the account to be logged in to notify the screen or the corresponding car device that the authorization is passed. The authorization result information can also carry relevant information such as the account number and password of the corresponding account, so that the screen can complete the quick login of the relevant account.

[0034] In a possible implementation of the first aspect above, the manner in which the first user device establishes a communication connection with the first space device includes any one of the following: a connection established based on Bluetooth technology; a connection established based on wireless fidelity technology; a connection established based on ultra-wideband wireless carrier communication technology; a connection established based on Star Flash technology.

[0035] It is understood that if two or more spatial devices are installed in the same physical space, such as the same vehicle cabin, communication connections can be established between the spatial devices using the above methods. Similarly, if multiple user devices are installed in the same vehicle cabin, communication connections can also be established between user devices logged into the same account using the above methods, without limitation.

[0036] In other embodiments, the above-mentioned physical space may also include other spaces with multiple devices, such as smart home spaces, which is not limited here.

[0037] In a possible implementation of the first aspect above, the first space device includes a vehicle-mounted device.

[0038] In other embodiments, the above-mentioned first space equipment may also include electronic devices set in other spaces, such as large-screen devices in smart home spaces, etc., which is not limited here.

[0039] In the second aspect, the present application provides an authorization system, which includes a third space device and a server, wherein the third space device is used to send a first authorization request message to the first user device when it detects that the spatial position relationship between the first user device and the first screen of the first space device meets the first condition, wherein the first authorization request message is used to request to log in a first account on the first screen, and the first account is the account logged in on the first user device; the third space device and the first space device are the same device or different devices: the server is used to send a first authorization result message to the third space device when it receives information indicating authorization from the first user device; and the third space device logs in the first account on the first screen when it determines that the first authorization result information indicates that the authorization is passed.

[0040] In a possible implementation of the second aspect above, the above system also includes a first user device, wherein the first user device is used to respond to the first authorization request information and display a fourth interface, wherein the fourth interface is used to prompt the user to perform an authorization operation; and the first user device is also used to respond to the user's authorization operation and send information indicating authorization to the server.

[0041] In a possible implementation of the second aspect above, the third space device is arranged inside the physical space, the physical space includes the cabin of the vehicle, and the way in which the third space device detects that the spatial position relationship between the first user device and the first screen of the first space device meets the first condition includes: the third space device detects that the first user device is located in the first area associated with the first screen in the cabin.

[0042] In a possible implementation of the second aspect above, the third space device sends the first authorization request information to the first user device, including: the third space device sends the first authorization request information to the first user device when detecting that the spatial position relationship between the second user device and the first screen meets the first condition and determining that the priority of the first user device is higher than the priority of the second user device.

[0043] In a third aspect, the present application provides an electronic device comprising: one or more processors; one or more memories; one or more memories storing one or more programs, which, when one or more programs are executed by one or more processors, enables the electronic device to execute the authorization method provided in the first aspect and various possible implementations.

[0044] In a fourth aspect, the present application provides a computer-readable medium having instructions stored thereon, which, when executed on a computer, causes the computer to execute the authorization method provided in the first aspect and various possible implementations.

[0045] In a fifth aspect, the present application provides a computer program product, including a computer program / instruction, which, when executed by a processor, implements the authorization method provided in the above-mentioned first aspect and various possible implementations.

[0046] The beneficial effects of the second to fifth aspects mentioned above can be found in the relevant descriptions of the first aspect and various possible implementations of the first aspect, and will not be elaborated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] FIG1a shows a schematic diagram of an application scenario of multiple screens and multiple user login accounts in a cockpit.

[0048] FIG1 b shows a schematic diagram of another application scenario of multiple screens and multiple user login accounts in a cockpit.

[0049] FIG2 a shows a schematic diagram of a prompt interface and an authorization verification interface displayed by the vehicle-mounted device in response to a user's account login operation provided by an embodiment of the present application.

[0050] FIG2 b shows a schematic diagram of another prompt interface and authorization verification interface displayed by the vehicle-mounted device in response to the user's account login operation provided by an embodiment of the present application.

[0051] FIG3 is a schematic diagram showing a system software structure of an electronic device provided in an embodiment of the present application.

[0052] FIG4 is a schematic diagram showing a login scenario corresponding to a user carrying a handheld device into a cockpit provided in Example 1 of the present application.

[0053] Figure 5a is a schematic diagram of the implementation process of an authorization method provided in Example 1 of the present application.

[0054] FIG5b is a schematic diagram showing a measurement scenario in which an in-cabin vehicle equipment controls an ultrasonic detection signal provided in Example 1 of the present application.

[0055] FIG6 is a schematic diagram showing a login scenario corresponding to a user carrying a handheld device into a cockpit provided in Example 2 of the present application.

[0056] FIG7 shows a schematic diagram of the implementation process of an authorization method provided in Example 2 of the present application.

[0057] Figure 8a shows a schematic diagram of a prompt interface and a device list interface displayed by the vehicle-mounted device provided in Example 2 of the present application in response to the user's login account operation.

[0058] Figure 8b shows a schematic diagram of another prompt interface displayed by the vehicle-mounted device provided in Example 2 of the present application in response to the user's operation of logging into the account.

[0059] FIG9 a is a schematic diagram showing a login scenario corresponding to two users carrying two handheld devices into a cockpit, as provided in Example 3 of the present application.

[0060] Figure 9b is a schematic diagram of another login scenario corresponding to two users carrying two handheld devices into the cabin provided in Example 3 of the present application.

[0061] Figure 9c is a schematic diagram of a login scenario corresponding to three users carrying three handheld devices into the cabin provided in Example 3 of the present application.

[0062] Figure 9d is a schematic diagram of another login scenario corresponding to three users carrying three handheld devices into the cabin provided in Example 3 of the present application.

[0063] Figure 9e is a schematic diagram of a login scenario corresponding to four users carrying four handheld devices into the cabin provided in Example 3 of the present application.

[0064] Figure 9f is a schematic diagram of another login scenario corresponding to three users carrying three handheld devices into the cabin provided in Example 3 of the present application.

[0065] FIG10 is a schematic diagram showing an implementation flow of an authorization method provided in Example 3 of the present application.

[0066] FIG11 a is a schematic diagram showing the matching relationship between each screen in the vehicle-mounted device and the mobile phone carried by each user in the login scenario shown in FIG9 e .

[0067] FIG. 11 b is a schematic diagram showing a device list interface displayed on the screen 200A in the login scenario shown in FIG. 9 e .

[0068] FIG12 a is a schematic diagram showing a login scenario corresponding to n handheld terminals (where m<n) carried by m users entering a cabin provided by an embodiment of the present application.

[0069] FIG12 b is a schematic diagram showing the matching relationship between each screen in the vehicle-mounted device and the mobile phone carried by each user in the login scenario shown in FIG12 a .

[0070] FIG12c is a schematic diagram showing a device list interface displayed on the screen 200A in the login scenario shown in FIG12a above.

[0071] Figure 13a is a schematic diagram of a login scenario corresponding to an embodiment of the present application in which the number of users entering the cockpit is greater than the number of screens in the vehicle equipment.

[0072] Figure 13b is a schematic diagram of another login scenario corresponding to an embodiment of the present application in which the number of users entering the cockpit is greater than the number of screens in the vehicle equipment.

[0073] FIG14 is a schematic diagram showing the hardware structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0074] In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be described in detail below with reference to the accompanying drawings and specific implementation methods.

[0075] It should also be stated that the steps in the methods and processes in the embodiments of the present application are numbered for ease of reference, rather than to limit the order of precedence. If there is a sequence between the steps, the written description shall prevail.

[0076] 1a and 1b respectively show schematic diagrams of an application scenario of multiple screens and multiple user login accounts in a cockpit.

[0077] Referring to Figure 1a, the screen of the smart cockpit can be configured as screen A (also known as the central control screen) for the main driver and screen B (also known as the co-pilot screen) for the co-pilot.

[0078] As shown in Figure 1b, the smart cockpit screens may include not only Screen A and Screen B, but also Screen C for users in the rear seats. It is understood that in other scenarios, the number of screens configured in some vehicle cockpits may reach 4 to 10 or even more.

[0079] It is understood that in the login scenario shown in Figure 1a above, screen A and screen B can be different screens of the same vehicle-mounted device, that is, screen A and screen B can be connected to the same host computer with communication and data processing capabilities. Screen A and screen B can also be screens of different vehicle-mounted devices, that is, screen A and screen B can be connected to different hosts with communication and data processing capabilities, without limitation here.

[0080] Similarly, in the login scenario shown in FIG. 1 b above, screen A, screen B, and screen C may be different screens of the same vehicle-mounted device, or screens of different vehicle-mounted devices, and there is no limitation here.

[0081] In the multi-screen, multi-user scenarios illustrated in Figures 1a and 1b above, as previously described, if multiple users wish to log in to their personal accounts on screens A and B, they are often required to enter their account and password for login verification on screens A and B, or scan a device QR code displayed on screens A and B before performing an authorization operation to log in to their personal accounts. This cumbersome operation of logging in to personal accounts on screens A and B is difficult to achieve quickly, resulting in a poor user experience and a reluctance to log in, which in turn leads to idle and wasted screen resources within the cockpit.

[0082] In order to solve the above problems, the present application provides an authorization method. Specifically, the method matches each screen in the cabin with a handheld device suitable for the user to perform authorized operations by identifying the position of the user's seat in the cabin and the relative position of the handheld device carried by the user. At this time, each screen can prompt the user to perform authorization verification through the matched handheld device, such as verifying biometric information such as fingerprints, facial information, iris information or voiceprints, thereby supporting the user to quickly log in to the account on the corresponding screen. In this way, when the user enters the cabin and needs to log in to the account on the screen in the cabin, the handheld device matched with the corresponding screen can be used for authorization verification, simplifying the user's operation process of logging in to the account on the corresponding screen and achieving the purpose of quick login. This is conducive to improving the user experience while also helping to reduce the idleness of screen resources in the cabin.

[0083] It is understood that the above-mentioned method of identifying the seat position of the user in the cabin can be determined by the detection results of the seat sensors configured on each seat in the cabin. The relative position between the handheld device carried by the above-mentioned user and the vehicle-mounted device and each screen can be determined by the sound wave such as ultrasound emitted by the speaker device of the vehicle-mounted device and the sound pickup device of the user's handheld device to receive the above sound wave for distance and angle measurement. In other embodiments, the vehicle-mounted device can also establish a communication connection with each handheld device entering the cabin through ultra-wideband (UWB) wireless carrier communication technology, nearLink technology, etc., and determine the relative position of each handheld device relative to the vehicle-mounted device and each screen, which is not limited here. In this way, the vehicle-mounted device can determine the matching relationship between each screen in the cabin and each user's handheld device based on the seat position of the user detected by the seat sensor and the relative position of the handheld device carried by the user.

[0084] After determining the above-mentioned matching relationship, the vehicle-mounted device can set the corresponding screen with the identification information of the corresponding matching handheld device, or the identification information of the communication components such as the Bluetooth chip of the handheld device, the Internet Protocol address (IP address), etc. Furthermore, when the corresponding screen detects the user's login operation, it can send an authorization verification request to the matching handheld terminal, and prompt the user to perform the authorization operation through the matching handheld terminal to quickly log in to the account. It is understandable that in some embodiments, after the user brings the handheld device into the cabin, the vehicle-mounted device can also automatically prompt the user to authorize the login account on the handheld device on the screen corresponding to the seat according to the user's seat position, and there is no limitation here.

[0085] Referring to Figure 2a, after entering the cockpit, the user can click on the control indicating the login account on the screen corresponding to the current seat. After the vehicle-mounted device 200 detects the above operation of the user through the corresponding screen, it can send an authorization verification request to the mobile phone 100 based on the matching relationship between the screen and the handheld device carried by the user, such as the mobile phone 100. The matching relationship between the screen operated by the user and the mobile phone 100 carried by the user can be detected and determined when the mobile phone 100 establishes a Bluetooth connection with the vehicle-mounted device 200 after the user carries the mobile phone 100 into the cockpit. The above authorization verification request can also be sent based on the transmission channel established corresponding to the Bluetooth connection. The above detection process may include the above-mentioned ultrasonic detection of the relative position relationship of the mobile phone 100 in space relative to the screen operated by the user. The details will be described in detail below and will not be repeated here.

[0086] Correspondingly, before, at the same time or after the vehicle-mounted device 200 sends an authorization verification request to the mobile phone 100, the prompt interface 210 shown in Figure 2a can be displayed on the corresponding screen. A prompt message 211 can be displayed on the prompt interface 210, and the prompt message 211 may include, for example, content such as "Please complete the login authorization on the mobile phone side", and at the same time, the corresponding mobile phone 100 can display the authorization verification interface 220 shown in Figure 2a. The user can verify fingerprint information, face information, iris information or voiceprint information on the authorization verification interface 220 to complete the authorization operation. Referring to Figure 2a, a prompt message 221 can also be displayed on the authorization verification interface 220 displayed by the mobile phone 100, and the prompt message 221 may include, for example, content such as "The vehicle-mounted device is logging into the account, please scan the fingerprint or verify the face authorization", which is not limited here.

[0087] Furthermore, when there are multiple users in the cabin, the vehicle-mounted device 200 may also display a list of available devices to the user via the corresponding screen. This list may include device identification information, such as device name or model, for multiple handheld devices currently in the cabin that the user can quickly authorize. For example, referring to Figure 2a , to facilitate user login, a selection control 212 may also be displayed on the prompt interface 210. This selection control 212 may display a prompt such as "Select a specific device to authorize login." Clicking this selection control 212 will cause the screen to display the aforementioned device list, allowing the user to select a handheld device for biometric verification and authorization.

[0088] For another example, referring to Figure 2b , a prompt interface 230 may also be displayed on the corresponding screen of the vehicle-mounted device 200. This prompt interface 230 may display a prompt message 231, such as "Multiple authorized devices found, please select an authorized device." In some embodiments, the prompt interface 230 shown in Figure 2b may also display a selection control 232. At this point, the user can click on the prompt message 231 or the selection control 232 to display the device list on the corresponding screen of the vehicle-mounted device 200. The user can then select a convenient handheld device from the device list for authorization, enabling quick login to their personal account.

[0089] It can be understood that the electronic device applicable to the authorization method provided in this application can be located in the cabin of a vehicle, such as a vehicle-mounted device, etc., and can have one or more screens, and each screen can support an independent login account. Among them, the above-mentioned means of transportation can include but are not limited to road vehicles (such as vehicles), water vehicles (such as ships), and air vehicles (such as airplanes). The above-mentioned vehicles can be vehicles in a broad sense, for example, vehicles (such as commercial vehicles, passenger cars, motorcycles, flying cars, trains, etc.), industrial vehicles (such as forklifts, trailers, tractors, etc.), engineering vehicles (such as excavators, bulldozers, cranes, etc.), agricultural equipment (such as mowers, harvesters, etc.), amusement equipment, toy vehicles, etc., without limitation here.

[0090] The authorization method provided in this application is applicable to handheld devices that may include, but are not limited to, mobile phones, tablet computers, desktop computers, laptops, handheld computers, netbooks, as well as augmented reality (AR) / virtual reality (VR) devices, smart TVs, smart watches and other wearable devices, car equipment, portable game consoles, portable music players, reader devices, and other electronic devices with one or more processors and communication functions.

[0091] It can be understood that in the embodiment of the present application, the above-mentioned handheld terminal can be configured with components, devices or equipment with biometric recognition functions such as fingerprint recognition, face recognition, iris recognition and voiceprint recognition, so as to provide users of the handheld terminal with the ability to conveniently log in to accounts and unlock devices. In the present application scheme, electronic devices such as vehicle-mounted devices that do not have biometric recognition functions can call the above-mentioned handheld devices with biometric recognition functions, such as mobile phones and tablets, for users to quickly verify identity information and complete authorization operations. In addition, based on the authorization method provided by the present application, after biometric recognition and authorization are passed using a handheld device, the user's biometric information and account password information will not be retained on the vehicle-mounted device, which is also conducive to avoiding the problem of users leaking privacy information after riding in a vehicle.

[0092] FIG3 shows a schematic diagram of a system software structure of an electronic device according to an embodiment of the present application.

[0093] It is understandable that the electronic devices installed with the system 300 shown in Figure 3 may include the above-mentioned vehicle equipment 200 or electronic devices configured in the cabin of other vehicles, and may also include handheld devices such as the above-mentioned mobile phone 100, without limitation here.

[0094] As shown in Figure 3, the system 300 may be a distributed system or an Android™ system, etc., which is not limited here. The above-mentioned distributed system may adopt a layered architecture, which may include an application layer, an application framework layer, a system service layer, and a kernel layer.

[0095] The application layer may include a series of application packages. Application packages may include, for example, an account system client, a desktop (launcher), music, and settings applications, without limitation. The account system client may utilize the distributed framework provided by system 300 to provide multi-account management functionality that supports independent login of accounts on multiple screens. In other embodiments, this management functionality may also be described as multi-user management functionality, without limitation.

[0096] The application framework layer can provide a distributed framework for the application layer. This distributed framework can include an account management framework that supports multiple accounts or multiple independent user logins. This framework can provide a functional framework for enabling interoperability (including startup, invocation, and migration) between various layers within system 300 and between systems 300, as well as the corresponding application programming interface (API) for each framework.

[0097] The system service layer is the core of the distributed operating system. It provides system services to applications and software development kits (SDKs) in the application layer through the application framework layer. In the embodiment of the present application, the system service layer may include a mobile sensing development platform (MSDP) subsystem and a distributed soft bus. The MSDP subsystem can provide core capabilities such as distributed fusion perception and distributed device virtualization capabilities to the above-mentioned account system client or through the above-mentioned distributed framework.

[0098] Among them, the distributed fusion perception capability can summarize and fuse the sensor data collected by the seat sensors installed on each seat in the above-mentioned cabin, Bluetooth ranging data, and the position of the handheld device in the corresponding area in the cabin determined based on ultrasonic and other sound wave detection, so as to more accurately determine the spatial position relationship of the handheld device used by the user relative to the vehicle equipment, which can also be called the relative position relationship in this application.

[0099] The spatial position relationship between the handheld device used by the user and the vehicle-mounted device may include the spatial position relationship between the handheld device and multiple screens controlled by the vehicle-mounted device. This spatial position relationship may be determined based on the association between each screen and the driver's seat area, the passenger seat area, and the area where the rear seats are located within the vehicle cabin. When the vehicle-mounted device detects that the user's handheld device is placed at a certain location within the aforementioned area, the spatial position relationship between the handheld device and the screens associated with that area may be determined.

[0100] The distributed soft bus, as an example structure of the underlying network, is used to transmit display data between devices and control instructions across devices. Among them, for the understanding of the distributed soft bus function, reference can be made to the computer hardware bus. The distributed soft bus can have the characteristics of automatic discovery, ready-to-use, self-organizing networking (heterogeneous network networking), high bandwidth, low latency, and high reliability. Through the distributed soft bus technology, not only can all data be shared between devices, but also they can be instantly interconnected with any device in the same local area network or connected to it via Bluetooth. In addition, the distributed soft bus can also share login account related data, authorization result information corresponding to the user's biometric information verification, etc. between networks such as Bluetooth and wireless fidelity (Wi-Fi). In addition, in an embodiment of the present application, a communication connection can be established between the vehicle-mounted device and the handheld device based on distributed soft bus technology or Bluetooth technology, and the relative position of each handheld device relative to each screen of the vehicle-mounted device can be determined through ultrasonic detection technology, ultimately accurately determining the matching relationship between each screen and the corresponding handheld device. This matching relationship can be determined based on, for example, the association between each screen and the area where each seat is located, as well as the result of the area where the handheld device is located determined based on ultrasonic detection technology. In other embodiments, the method of detecting the relative position of the handheld device relative to each screen of the vehicle-mounted device can also adopt methods such as array signal processing technology based on wireless signals, which are not limited here.

[0101] The kernel layer is the layer between hardware and software. The kernel layer of a distributed operating system consists of the kernel subsystem and the driver subsystem. Because distributed operating systems can employ multi-core designs, the kernel subsystem supports the selection of appropriate OS kernels for different resource-constrained devices.

[0102] The kernel abstraction layer (KAL) on the kernel subsystem shields the differences between multiple kernels and provides basic kernel capabilities to the upper layer, including process / thread management, memory management, file system, network management, and peripheral management.

[0103] The driver framework provided by the driver subsystem is the foundation for the openness of the distributed system hardware ecosystem, providing unified peripheral access capabilities and a driver development and management framework. In some embodiments, the driver subsystem may include device drivers such as display drivers, camera drivers, and audio drivers to drive the corresponding devices and provide corresponding hardware capabilities. In the embodiments of the present application, the driver subsystem may also include drivers that interact with seat sensors or other sensors, etc., which are not limited here.

[0104] The following will describe in detail the specific implementation process of the authorization method provided in this application based on the system architecture shown in FIG3 above and in combination with the application scenarios provided in different embodiments.

[0105] The following first introduces the specific implementation process of the authorization method provided by this application in conjunction with the application scenario provided in Example 1 where a user brings a handheld device into the cabin.

[0106] Example 1

[0107] FIG4 shows a schematic diagram of a login scenario corresponding to a user carrying a handheld device into a cockpit according to an embodiment of the present application.

[0108] Taking the vehicle cockpit as an example, as shown in Figure 4, the vehicle equipment 200 in the cockpit in this scene can have multiple screens, including screen A, screen B, screen C, screen D, etc. For clarity, they can be described as screen 200A, screen 200B, screen 200C, and screen 200D respectively.

[0109] In the embodiment of the present application, the number of users entering the cabin may be 1, and the user may enter the cabin with a handheld device such as a mobile phone 100. In other embodiments, the handheld device carried by the user may also be an electronic device such as a watch or a tablet computer, which is not limited here.

[0110] At this point, the vehicle-mounted device 200 can discover the mobile phone 100 via Bluetooth and establish a Bluetooth connection or distributed connection with the mobile phone 100. In this way, the mobile phone 100 and the vehicle-mounted device 200 can synchronize device information and send request data based on the data transmission channel provided by the Bluetooth connection. The vehicle-mounted device 200 can establish a Bluetooth connection with the mobile phone 100 based on the relevant records of Bluetooth pairing and connection establishment with the mobile phone 100 during historical use.

[0111] In the embodiment of the present application, the vehicle machine 200 can determine that each screen in the cabin can be authorized to log in to the user account through the mobile phone 100 based on the user's seat position and the relative position of the mobile phone 100 in the cabin relative to the various screens of the vehicle machine device 200. It can be understood that the account authorized to log in by the user can be managed by the account cloud, which can run on the server. The mobile phone 100, vehicle machine 200 and other electronic devices used by the user can log in to the same account, and the electronic devices logged in to the same user account can establish a distributed connection based on the above-mentioned distributed soft bus or other communication methods, which is not limited here and will not be elaborated.

[0112] Based on the scenario shown in FIG4 above, FIG5a shows a schematic diagram of an implementation process of an authorization method according to an embodiment of the present application.

[0113] 5 a , the implementation process may involve interactions between a mobile phone 100 , a vehicle device 200 , and an account cloud 300 for managing user accounts.

[0114] Specifically, as shown in FIG5a , the process may include the following steps:

[0115] 501: The mobile phone 100 establishes a device connection with the vehicle device 200 and synchronizes device information.

[0116] Exemplarily, the above-mentioned device connection may include a Bluetooth connection and a distributed connection established based on the above-mentioned distributed soft bus, etc. The above-mentioned device information may include the identification information and address of the Bluetooth chip / component synchronized to the vehicle-mounted device 200, as well as the identification information and location information of components such as the microphone; it may also include the identification information and address of the Bluetooth chip / component sent to the vehicle-mounted device 200 by the vehicle-mounted device 200, as well as the identification information and location information of each speaker in the speaker array. The above-mentioned speaker array can be used as an ultrasonic device array. This application determines the area of ​​the mobile phone 100 in the vehicle cabin based on ultrasonic detection technology, and then determines the relative position between the mobile phone 100 and the corresponding screen of the vehicle-mounted device 200.

[0117] When the user brings the mobile phone 100 into the vehicle cabin, the vehicle device 200 can discover the mobile phone 100 via Bluetooth. If the mobile phone 100 and the vehicle device 200 have already established a Bluetooth connection, the two can directly establish a Bluetooth connection without having to pair them again. If the mobile phone 100 and the vehicle device 200 have not established a Bluetooth connection, the user can follow the relevant operation prompts provided by the mobile phone 100 or the vehicle device 200 to complete the pairing and establish a Bluetooth connection. It can be understood that the above-mentioned mobile phone 100 or the vehicle device 200 can provide relevant operation prompts through screen display or voice prompts, which are not limited here.

[0118] 502: The vehicle-mounted device 200 sends a detection signal for measuring the direction to the mobile phone 100.

[0119] For example, the detection signal for measuring the orientation may be a high-frequency signal such as ultrasonic wave, or may be other carrier signals that cannot be perceived by the user, and no limitation is made here.

[0120] As an example, referring to FIG5b , after establishing a connection with the mobile phone 100, the vehicle-mounted device 200 can emit ultrasonic waves through a speaker array distributed within the cabin. The speaker array may include, but is not limited to, speakers in the arrangement areas indicated by speaker A, speaker B, speaker C, and speaker D shown in FIG5b . The ultrasonic waves can be received by a sound pickup device, such as a microphone, configured in the mobile phone 100, and the mobile phone 100 can proceed to perform step 503 described below.

[0121] 503: The mobile phone 100 transmits a synchronous detection signal reception result to the vehicle device 200.

[0122] For example, the detection signal reception result may include the time information recorded when the microphone of the mobile phone 100 receives the ultrasonic wave, or the mobile phone 100 may determine the seat area in the vehicle cabin where the mobile phone 100 is located based on the ultrasonic signal reception result. Furthermore, the vehicle-mounted device 200 may determine the relative positional relationship between each screen and the mobile phone 100.

[0123] 504: The vehicle device 200 obtains sensor data.

[0124] For example, the sensor data may be collected by seat sensors installed on each seat in the cabin. In some embodiments, the data collected by the seat sensors is used to indicate whether a user has sat in a seat, or to determine whether a user exists within the area sensed by the seat sensors. The seat sensors may be located in the driver's seat, the passenger seat, or the rear seat, without limitation.

[0125] It is understood that the seat sensor can be a pressure sensor disposed under the corresponding seat, or a sensor capable of detecting the wearing status of a seat belt, without limitation. For example, within a certain time period, the processor or computing unit of the vehicle-mounted device 200 can detect changes in pressure values ​​based on the pressure sensor under the driver's seat to determine whether a user is seated in the driver's seat.

[0126] 505: The vehicle device 200 determines the relative position relationship between each screen and the handheld device.

[0127] For example, the vehicle device 200 can determine the relative position relationship of screen 200A, screen 200B, screen 200C and screen 200D respectively with the mobile phone 100 based on the detection signal reception result sent by the mobile phone 100 in the above step 503 and the sensor data obtained in the above step 504.

[0128] For example, based on the relative position detection results obtained by ultrasonic detection technology, it can be determined that the mobile phone 100 is located in the main driving seat area associated with screen 200A, and then the relative position relationship between the mobile phone 100 and screen 200A, screen 200B, screen 200C and screen 200D can be determined. Among them, the relative position relationship between the mobile phone 100 and screen 200A can meet the preset conditions, and the preset conditions are, for example, the matching relationship between screen 200A and one or more handheld devices placed in the main driving area. It can be understood that the mobile phone 100 can also be at the same relative distance from screen 200A and screen 200C, but because the screen associated with the main driving area is screen 200A, it can be determined that the mobile phone 100 matches screen 200A. This is not limited here.

[0129] In other embodiments, to improve recommendation accuracy, when the relative distances between the mobile phone 100 and multiple screens of the vehicle-mounted device 200 are the same or similar, the vehicle-mounted device 200 may also determine the handheld device with the shortest relative distance to each screen and corresponding to the user's seat position based on the data collected by the seat sensor to recommend it to the user as the operable device for authorized login. Furthermore, the aforementioned method of detecting the relative position of the handheld device relative to the various screens of the vehicle-mounted device may also employ methods such as array signal processing technology based on wireless signals, which are not limited herein.

[0130] 506 : The vehicle device 200 detects the user's login operation on the screen 200A.

[0131] For example, when a user needs to log in to an account on the vehicle-mounted device 200, they can perform the login operation on a nearby screen. For example, referring to the login scenario shown in Figure 4, a user sitting in the main driving area can click the relevant control on screen 200A to trigger the login account. Correspondingly, the vehicle-mounted device 200 can detect the user's login operation through screen 200A.

[0132] In other embodiments, the screen on which the user performs the login operation in the cockpit may also be screen 200B, screen 200C, or screen 200D, etc. Correspondingly, the vehicle device 200 may detect the user's login operation on screen 200B, screen 200C, or screen 200D, without limitation.

[0133] 507 : The vehicle-mounted device 200 determines that the mobile phone 100 that meets the conditions is the target device.

[0134] For example, when the vehicle device 200 detects the user's login operation through the screen 200A, it can recommend the mobile phone 100 corresponding to the screen 200A as a target device for the user to use. The target device can provide biometric recognition capabilities, etc., for the user to quickly perform authorization operations.

[0135] It can be understood that in the embodiment of the present application, for the application scenario where a single user carries a single handheld device into the cabin, since the vehicle device 200 can only use the current only handheld device (such as mobile phone 100) for authorized login, the above-mentioned steps 502, 503, 505 and 507 may not be executed.

[0136] In other embodiments, if a user carries multiple handheld devices, such as a mobile phone, a watch, and a tablet, or if multiple users each carry at least one handheld device into the cabin, the vehicle-mounted device 200 may combine the relative positional relationships between the various screens and the handheld devices determined above to determine the target device corresponding to the screen currently being operated by the user. This will be described in detail in the relevant embodiments below and is not elaborated on here.

[0137] 508 : The vehicle device 200 sends an authorization login request to the mobile phone 100 .

[0138] For example, after determining the target device (e.g., mobile phone 100) for the user to authorize the operation, the vehicle device 200 may send an authorization login request to the target device. The authorization login request may instruct the target device to display an authorization interface or to prompt the user with other information (e.g., voice message) for the authorization operation, without limitation.

[0139] 509: The vehicle-mounted device 200 displays a first prompt interface.

[0140] For example, before, during, or after the vehicle-mounted device 200 executes step 508, a related interface may be displayed to remind the user to perform authorization operations on the target device. For ease of description, this reminder interface is hereinafter referred to as the first reminder interface. In some embodiments, the content of this first reminder interface may refer to the content displayed in the reminder interface 210 shown in FIG. 2a above. For specific content, please refer to FIG. 2a and the related description above, and will not be repeated here.

[0141] In other embodiments, the vehicle device 200 may also remind the user of relevant information for authorization operations on the target device through voice prompts or the like, or the vehicle device 200 may not execute step 509 to display the above-mentioned first prompt interface, which is not limited here.

[0142] 510: The mobile phone 100 prompts the user to perform authorization operation.

[0143] For example, the mobile phone 100 can prompt the user to authorize the operation by displaying an authorization interface. The authorization interface can include an area prompting the user to enter biometric information such as fingerprint information or facial information. As an example, the mobile phone 100 can display the authorization verification interface 220 shown in Figure 2a above, which can display an area prompting the user to enter fingerprint information and an area prompting the user to enter facial information.

[0144] In other embodiments, the mobile phone 100 may also prompt the user to perform the authorization operation by playing a voice prompt or other methods, which is not limited here.

[0145] 511: The mobile phone 100 receives the verification information input by the user.

[0146] Exemplarily, the verification information input by the above-mentioned user may include fingerprint information, face information, iris information and voiceprint information provided by the user, and may also include account number, password and / or verification code information input by the user through an input method soft keyboard, etc., without limitation here.

[0147] 512: The mobile phone 100 sends the verification result to the account cloud 300.

[0148] For example, the mobile phone 100 can verify whether the fingerprint information, face information, iris information, and voiceprint information input by the user for authorization operations on the authorization verification interface or other related interfaces match the corresponding pre-collected biometric information, and send a verification result corresponding to whether the match is true to the account cloud 300. This verification result can be used to request the account cloud 300 to check whether the verification information entered by the user through the mobile phone 100 matches the biometric information recorded corresponding to the relevant account.

[0149] 513: The account cloud 300 returns authorization result information to the vehicle device 200.

[0150] It will be appreciated that the account cloud 300 can store and manage account-related information, such as each user's registered account number and password. Therefore, the account cloud 300 can generate corresponding authorization result information based on the verification result sent by the mobile phone 100. For matching verification results, the account cloud 300 can generate authorization result information indicating that the authorization was approved and send it to the vehicle-mounted device 200. For mismatching verification results, the account cloud 300 can return authorization result information indicating that the authorization was rejected to the vehicle-mounted device 200.

[0151] 514: The vehicle device 200 completes the account login.

[0152] For example, the vehicle-mounted device 200 can complete the account login process based on the authorization result information sent by the account cloud 300 indicating that the authorization was passed. It is understood that the vehicle-mounted device 200 can also notify the user of the failure result through an interface or voice, based on the authorization result information sent by the account cloud 300 indicating that the authorization was not passed or failed.

[0153] It can be understood that based on the interactive process corresponding to steps 501 to 514 above, in the login scenario where a user brings a handheld device into the cockpit, the vehicle-mounted device 200 can implement cross-device invocation of the handheld device's biometric information recognition capabilities, instruct the user to perform authorization verification, and thus quickly complete the account login process on the vehicle-mounted device 200. Obviously, this process can simplify the user's operation of entering information such as account number and password on the relevant screen of the vehicle-mounted device 200, or scanning the QR code displayed on the relevant screen of the vehicle-mounted device 200 to verify biometric information, thereby improving the user experience and reducing idle screen resources in the cockpit.

[0154] The following describes the specific implementation process of the authorization method provided in this application in conjunction with the application scenario provided in Example 2 where a user brings multiple handheld devices into the cabin.

[0155] Example 2

[0156] FIG6 shows a schematic diagram of a login scenario corresponding to a user carrying multiple handheld devices into a cockpit according to an embodiment of the present application.

[0157] Taking the vehicle cockpit as an example, as shown in Figure 6, the vehicle equipment 200 in the cockpit in this scene can have multiple screens, including screen A, screen B, screen C, screen D, etc. For clarity, they can be described as screen 200A, screen 200B, screen 200C, and screen 200D respectively.

[0158] In this embodiment of the present application, the number of users entering the cabin may be one, but the number of handheld devices carried by the user may be multiple. As shown in Figure 6, for example, the user may carry a mobile phone 100, a watch 400, and a tablet computer 500 into the cabin. In other embodiments, the multiple handheld devices carried by the user may be other devices, and the number of handheld devices carried by the user may be two, four, or any other number, without limitation.

[0159] Based on the scenario shown in FIG6 above, FIG7 shows a schematic diagram of an implementation process of an authorization method according to an embodiment of the present application.

[0160] Referring to Figure 7 , this implementation process may involve interactions between the vehicle-mounted device 200 and the mobile phone 100, watch 400, and tablet computer 500. The process of interaction between the vehicle-mounted device 200, mobile phone 100, watch 400, and tablet computer 500 and the account cloud 300 is not shown. For detailed interactions, please refer to the descriptions in the relevant steps and will not be repeated here.

[0161] As shown in Figure 7, the process may include the following steps:

[0162] 701: The vehicle device 200 establishes device connections with the mobile phone 100, the watch 400 and the tablet computer 500 respectively, and synchronizes device information.

[0163] 702 : The vehicle-mounted device 200 sends a detection signal for measuring the orientation to the mobile phone 100 , the watch 400 , and the tablet computer 500 .

[0164] 703 : The mobile phone 100 , the watch 400 and the tablet computer 500 synchronously detect the signal reception result to the vehicle device 200 .

[0165] 704: The vehicle device 200 obtains sensor data.

[0166] It is understood that the execution process of steps 701 to 704 can refer to the execution process of steps 501 to 504 in the above embodiment 1. Compared with steps 501 to 504 in the above embodiment 1, the above steps 701 to 704 in the embodiment of the present application are different in that the interaction subjects involve the vehicle-mounted device 200 and multiple handheld devices carried by the same user.

[0167] 705 : The vehicle device 200 determines a matching relationship based on the relative positions of each screen and each handheld device.

[0168] For example, when a user carries multiple handheld devices, the placement of each handheld device may be different, resulting in different time data, etc., for each handheld device to receive detection signals such as ultrasonic waves emitted by the vehicle-mounted device 200. For the vehicle-mounted device 200 or the relevant screen of the vehicle-mounted device 200 operated by the user, the handheld device suitable for recommendation to the user for authorized operation (i.e., matching) can be determined based on the relative position of each handheld device and the vehicle-mounted device 200 or the relevant screen of the vehicle-mounted device 200.

[0169] As an example, referring to the login scenario shown in FIG6 , for example, the user's mobile phone 100 is closest to screen 200A, while the tablet computer 500 may be closest to screen 200B due to being placed on the passenger seat. In this case, the vehicle-mounted device 200 can set a matching relationship between screen 200A and mobile phone 100, and a matching relationship between screen 200B and tablet computer 500. In other embodiments, the matching relationships between the handheld device and each screen may also include other relationships, such as a matching relationship between screen 200A and the user's watch 400, and a matching relationship between screen 200B and mobile phone 100 and tablet computer 500 placed on the passenger seat. This is not a limitation. The above distances can be determined based on the position of mobile phone 100 in the vehicle cabin as determined by ultrasonic detection results. The position of mobile phone 100 in the passenger seat or the passenger seat, as well as the exact position of mobile phone 100 within the corresponding area, can be measured using ultrasonic detection technology or array signal processing technology based on wireless signals. The specific detection process can be referenced to the relevant implementation solutions of ultrasonic detection technology and is not described in detail here.

[0170] It is understandable that the matching relationship between each screen of the vehicle device 200 and each handheld device can be a many-to-one, one-to-one or one-to-many corresponding matching relationship, which is not limited here.

[0171] 706 : The vehicle device 200 detects the user's login operation on the screen 200A.

[0172] For example, referring to the scenario shown in FIG6 , if the user is sitting in a seat in the main driving area, the user can click on the control on the screen 200A to trigger the login account, and perform the login operation.

[0173] In other embodiments, the user may also perform the login operation on other screens in the cockpit, such as screen 200B, screen 200C, screen 200D, etc., which is not limited here.

[0174] 707 : The vehicle device 200 determines that the mobile phone 100 that matches the screen 200A is the target device.

[0175] For example, when executing steps 702 to 705 above, the vehicle-mounted device 200 may comprehensively detect, based on an ultrasonic device array (e.g., a speaker array) and seat sensors, that the handheld device matching the screen 200A is the mobile phone 100. Accordingly, when the vehicle-mounted device 200 detects a user login operation during step 706 above, it may determine the mobile phone 100 as the target device matching the screen 200A.

[0176] 708 : The vehicle device 200 sends an authorization login request to the mobile phone 100 .

[0177] For example, among multiple handheld devices connected to the vehicle-mounted device 200, the matching priority of the mobile phone 100 with the vehicle-mounted device 200 may be higher than the matching priority of the watch 400 with the vehicle-mounted device 200, and the matching priority of the watch 400 with the vehicle-mounted device 200 may be higher than the matching priority of the tablet computer 500 with the vehicle-mounted device 200. In some embodiments, the vehicle-mounted device 200 may send an authorization login request to the prioritized mobile phone 100 and execute step 709 below to prompt the user to perform authorization operations on the mobile phone 100. In other embodiments, the vehicle-mounted device 200 may also send authorization login requests to each handheld device in the order of priority corresponding to the above-mentioned handheld devices; or, if the mobile phone 100 with the priority request does not respond for a long time, the vehicle-mounted device 200 may send an authorization login request to the watch 400, and so on, without limitation here.

[0178] 709: The vehicle-mounted device 200 displays a second prompt interface.

[0179] For example, the vehicle device 200 may send an authorization login request to the mobile phone 100 that matches the screen 200A, and may remind the user to authorize the login through the mobile phone 100. This reminder interface may be referred to as a second prompt interface to distinguish it from the first prompt interface displayed in step 509 in the above embodiment 1.

[0180] It is understood that in some embodiments, the content of the second prompt interface can refer to the prompt interface 810 shown in Figure 8a. The display content of the prompt interface 810 can be the same as the display content of the prompt interface 210 shown in Figure 2a above. In other words, the content displayed in the second prompt interface can be the same as the content displayed in the first prompt interface in Example 1 above.

[0181] As shown in FIG8a , the prompt interface 810 may display a prompt message 811 , which may include, for example, content such as "Please complete login authorization on your mobile phone." Continuing with FIG8a , to facilitate user login, the prompt interface 810 may also display a selection control 812 , which may display, for example, a prompt such as "Select a specified device to authorize login." When the user clicks the selection control 812 on the prompt interface 810 , the corresponding screen of the vehicle-mounted device 200 may display a device list including all currently connected handheld devices. For details, please refer to the description of steps 711 to 712 below, which will not be repeated here.

[0182] 710: The mobile phone 100 prompts the user to perform authorization operation.

[0183] For example, in response to the authorization login request sent by the vehicle device 200, the mobile phone 100 may display a corresponding authorization login interface or prompt the user to perform the authorization operation through voice, etc. The specific prompt process can be referred to the relevant description of step 510 in the above embodiment 1 and will not be repeated here.

[0184] 711: The vehicle device 200 detects that the user selects the authorized device operation on the second prompt interface.

[0185] For example, if it is inconvenient for the user to perform authorization operations through the mobile phone 100 matched with the vehicle device 200, the user can choose to perform authorization operations through other handheld terminals, for example, the user can choose a watch 400.

[0186] As an example, referring to FIG8a , when the user clicks the selection control 812 on the prompt interface 810 , the vehicle-mounted device 200 can detect the user's selection of an authorized device on the second prompt interface. At this point, the vehicle-mounted device 200 can proceed to step 712 below to display a device list containing multiple handheld devices.

[0187] In other embodiments, before executing step 708 and sending the authorization login request, the vehicle-mounted device 200 may skip steps 708 to 710 and instead display a prompt interface 830 shown in FIG8b . Referring to FIG8b , the prompt interface 830 may display a prompt message 831 such as "Multiple authorized devices found, please select an authorized device." In some embodiments, the prompt interface 830 may also display a selection control 832 . The user can click on the prompt message 831 or the selection control 832 on the prompt interface 830 shown in FIG8b to cause the vehicle-mounted device 200 to execute step 712 below to display a device list.

[0188] 712: The vehicle device 200 displays a device list.

[0189] As an example, the interface for displaying the device list of the vehicle device 200 may refer to the device list interface 820 shown in FIG8a . The interface 820 may display the names or models of multiple handheld devices such as the currently connected mobile phone 100 , watch 400 , and tablet computer 500 .

[0190] In other embodiments, the device list interface displayed by the vehicle device 200 may also include more or fewer devices than those shown in the above-mentioned device list interface 820, and the layout style of the device list interface may also be different from that of the above-mentioned device list interface 820, which is not limited here.

[0191] 713: The vehicle device 200 determines that the watch 400 selected by the user is the target device.

[0192] For example, referring to FIG8a above, a user can click the login control 821 corresponding to "Watch 400" on the device list interface 820 displayed on screen 200A to set Watch 400 as the authorized device for authorization operations. In some embodiments, in the device list interface 820 shown in FIG8a , the login control corresponding to each device can display a prompt such as "Click me to log in." The content displayed on the login control 821 shown in FIG8a is not limited here. Correspondingly, the vehicle-mounted device 200 can use the user-selected watch 400 as the target device and proceed to step 714 below to send an authorization login request.

[0193] It is understood that in the device list displayed by the vehicle-mounted device 200, the display priority for different handheld devices carried by the user may be different, and the priority may be preset or user-configured. For example, for the mobile phone, watch, and tablet computer mentioned above, the priority order displayed by the vehicle-mounted device 200 may be mobile phone > watch > tablet computer.

[0194] It is understandable that the user can also click on the login control corresponding to other devices on the device list interface 820 shown in FIG. 8 a , for example, click on the login control 822 corresponding to the tablet computer 500 , etc., and there is no limitation here.

[0195] 714 : The vehicle device 200 sends an authorization login request to the watch 400 .

[0196] 715: The watch 400 prompts the user to perform authorization operation.

[0197] For example, when the watch 400 receives the authorization login request sent by the vehicle device 200, it can respond to the request by displaying an authorization interface or prompting the user to perform the authorization operation through voice, etc. The specific prompt process can be referred to the relevant description of step 510 in the above embodiment and will not be repeated here.

[0198] 716: The watch 400 receives the verification information input by the user.

[0199] 717: Watch 400 sends the verification result to the account cloud.

[0200] Specifically, the process of the watch 400 executing the above steps 716 to 717 can correspond to the relevant description of the mobile phone 100 executing steps 511 to 512 in the above embodiment 1, and will not be repeated here.

[0201] 718: The vehicle device 200 receives the authorization result information returned by the account cloud.

[0202] 719: The vehicle device 200 completes the account login.

[0203] Specifically, the process of the vehicle-mounted device 200 executing the above steps 718 to 719 can correspond to the description of the account cloud 300 executing step 513 and the vehicle-mounted device 200 executing step 514 in the above embodiment 1, which will not be repeated here.

[0204] It can be understood that based on the interactive process corresponding to the execution of steps 701 to 719 above, for a login scenario in which a user brings multiple handheld devices into the cockpit, the vehicle-mounted device 200 can recommend a matching target device to the screen that needs to log in to the user account based on the detection results of the ultrasonic detection technology and the detection results of the seat sensor, etc., and provide the user with a convenient way to log in to the account. In addition, the vehicle-mounted device 200 can also receive the user's operation of selecting a designated device as the authorized device, meeting the user's actual needs of selecting a handheld device that is convenient for authorized login to perform authorized operations, which is conducive to further improving the user experience. In addition, the authorization method provided in the embodiment of the present application can obviously remedy the situation in which the vehicle-mounted device 200 mistakenly recommends a handheld device based on the detection results of the ultrasonic detection technology and the seat sensor, and provide the user with more optional configurations, so as to facilitate the user to quickly log in to the account in the cockpit.

[0205] The following describes the specific implementation process of the authorization method provided in this application in conjunction with the application scenario provided in Example 3 where multiple users each carry a handheld device into the cabin.

[0206] Example 3

[0207] Figures 9a to 9f are schematic diagrams of login scenarios corresponding to multiple users carrying one or more handheld devices into the cabin according to an embodiment of the present application.

[0208] Taking the vehicle cockpit as an example, as shown in Figure 9a, the vehicle equipment 200 in the cockpit in this scene can have multiple screens, including screen A, screen B, screen C, screen D, etc. For clarity, they can be described as screen 200A, screen 200B, screen 200C, and screen 200D respectively.

[0209] In an embodiment of the present application, the number of users entering the cabin can be m (m≥1 and m is an integer). The number of handheld devices carried by each user can be 1 or n (n>1 and n is an integer). As shown in Figure 9a, for example, the user can carry a mobile phone 100, a watch 400, and a tablet computer 500 into the cabin. In other embodiments, the multiple handheld devices carried by the above-mentioned users can also be other devices, and the number of handheld devices carried by the users can also be 2, 4, or other numbers, which are not limited here.

[0210] As an example, referring to Figure 9a, user A can enter the cabin with mobile phone 100A and sit in the driver's seat, while user B can enter the cabin with mobile phone 100B and sit in the passenger seat. After establishing a device connection with mobile phones 100A and 100B, vehicle-mounted device 200 can determine the matching relationship between screen 200A and mobile phone 100A, and screen 200B and mobile phone 100B, based on the detection results of ultrasonic detection technology and the detection results of the seat sensor.

[0211] As shown in Figure 9b, user A can enter the cabin with mobile phone 100A and sit in the driver's seat, while user C can enter the cabin with mobile phone 100C and sit in the left rear seat. After establishing a device connection with mobile phones 100A and 100C, vehicle-mounted device 200 can determine the matching relationship between screen 200A and mobile phone 100A, and screen 200C and mobile phone 100C, based on the detection results of ultrasonic detection technology and the seat sensor.

[0212] As shown in Figure 9c, user A can enter the cabin with mobile phone 100A and sit in the driver's seat. User C can enter the cabin with mobile phone 100C and sit in the left rear seat. User D can enter the cabin with mobile phone 100D and sit in the right rear seat. After establishing device connections with mobile phones 100A, 100C, and 100D, vehicle-mounted device 200 can determine the matching relationships between screen 200A and mobile phone 100A, screen 200C and mobile phone 100C, and screen 200D and mobile phone 100D based on the detection results of ultrasonic detection technology and seat sensors.

[0213] As shown in Figure 9d, user A can enter the cabin with mobile phone 100A and sit in the driver's seat, user B can enter the cabin with mobile phone 100B and sit in the passenger seat, and user C can enter the cabin with mobile phone 100C and sit in the right rear seat. After establishing device connections with mobile phones 100A, 100B, and 100C, vehicle-mounted device 200 can determine the matching relationships between screen 200A and mobile phone 100A, screen 200B and mobile phone 100B, and screen 200C and mobile phone 100C based on the detection results of ultrasonic detection technology and seat sensors.

[0214] As shown in Figure 9e, user A can enter the cabin with mobile phone 100A and sit in the driver's seat, user B can enter the cabin with mobile phone 100B and sit in the passenger seat, user C can enter the cabin with mobile phone 100C and sit in the left rear seat, and user D can enter the cabin with mobile phone 100D and sit in the right rear seat. After establishing device connections with mobile phones 100A, 100B, 100C, and 100D, vehicle-mounted device 200 can determine the matching relationships between screen 200A and mobile phone 100A, screen 200B and mobile phone 100B, screen 200C and mobile phone 100C, and screen 200D and mobile phone 100D based on the detection results of ultrasonic detection technology and the detection results of the seat sensors.

[0215] As shown in Figure 9f, user A can enter the cabin with mobile phone 100A and sit in the driver's seat, user C can enter the cabin with mobile phone 100C and sit in the left rear seat, and user D can enter the cabin with mobile phone 100D and sit in the center rear seat. After establishing device connections with mobile phones 100A, 100C, and 100D, vehicle-mounted device 200 can determine the matching relationships between screen 200A and mobile phone 100A, screen 200C and mobile phone 100C, and screen 200D and mobile phone 100D based on the detection results of ultrasonic detection technology and seat sensors. Alternatively, the matching relationships between screen 200A and mobile phone 100A, screen 200C and mobile phone 100C, and mobile phone 100D can be determined.

[0216] It can be understood that in the application scenario of the embodiment of the present application, there may be a situation where when there are many users entering the cabin, the vehicle-machine device 200 may not be able to distinguish the target device that matches the corresponding screen from the handheld devices of each user. At this time, the vehicle-machine device 200 can obtain the handheld devices carried by each user through a Bluetooth connection and form a list. When recommending a target device to the user, the vehicle-machine device 200 can make a recommendation based on the detection results of the seat sensor and the detection results based on ultrasonic detection technology, or it can make a recommendation based on the user's operation of selecting the target device on the corresponding screen. In other embodiments, when recommending a target device to the user, the vehicle-machine device 200 can also make a recommendation based on the detection results of the seat sensor and the detection results of the array signal processing technology based on wireless signals, which is not limited here.

[0217] As an example, based on the scenario shown in FIG9a above, FIG10 shows a schematic diagram of an implementation process of an authorization method according to an embodiment of the present application.

[0218] It can be understood that the process shown in Figure 10 may involve the interaction between the handheld device 100A of user A, the handheld device 100B of user B and the screen 200A and screen 200B of the vehicle device 200.

[0219] Specifically, as shown in FIG10 , the process may include the following steps:

[0220] 1001a / 1001b: The vehicle device 200 establishes a device connection with the mobile phone 100A / mobile phone 100B and synchronizes device information.

[0221] For example, when user A enters the cabin with mobile phone 100A, vehicle-mounted device 200 can discover mobile phone 100A via Bluetooth and establish a device connection with mobile phone 100A. Similarly, when user B enters the cabin with mobile phone 100B, vehicle-mounted device 200 can discover mobile phone 100B via Bluetooth and establish a device connection with mobile phone 100B. After establishing the device connection, vehicle-mounted device 200 can synchronize device information with mobile phone 100A or mobile phone 100B. The specific implementation process can be referred to the relevant description of step 501 in the above embodiment 1 and is not repeated here.

[0222] It is understood that in the context of the embodiments of the present application, " / " can be used to represent an "and / or" relationship. Since user A entering the cabin with mobile phone 100A and user B entering the cabin with mobile phone 100B can occur one after another or simultaneously, if the vehicle-mounted device 200 is within the Bluetooth signal coverage range supported by the Bluetooth chip and can receive the Bluetooth signal from mobile phone 100A and / or mobile phone 100B, it can establish a device connection with mobile phone 100A and / or mobile phone 100B, without limitation here.

[0223] 1002a / 1002b: The vehicle-mounted device 200 sends a detection signal for measuring the direction to the mobile phone 100A / mobile phone 100B.

[0224] For example, the vehicle-machine device 200 can send ultrasonic or other detection signals to the connected mobile phone 100A / mobile phone 100B, and then when executing the following steps 1003a / 1003b and receiving the detection signal reception result fed back by the mobile phone 100A / mobile phone 100B, it can determine the relative position of the mobile phone 100A / mobile phone 100B, that is, the relative position of the mobile phone 100A / mobile phone 100B relative to the vehicle-machine device 200.

[0225] The specific implementation process of the vehicle-mounted device 200 sending ultrasonic and other detection signals can refer to the relevant description of step 502 in the above embodiment 1, and will not be repeated here.

[0226] 1003a / 1003b: The mobile phone 100A / mobile phone 100B synchronously detects the signal reception result from the vehicle-mounted device 200.

[0227] In the embodiment of the present application, the relative position determined based on the measurement results of steps 1002a to 1003a and / or 1002a to 1003b may also be the relative position of the mobile phone 100A / mobile phone 100B relative to the screen 200A / screen 200B of the vehicle-mounted device 200. The vehicle-mounted device 200 may measure and calculate the relative position using ultrasonic or other detection signals as required for executing subsequent related steps, and this is not limited here.

[0228] The specific synchronization process can refer to the relevant description of step 503 in the above embodiment 1, and will not be repeated here.

[0229] 1004: The vehicle device 200 obtains sensor data.

[0230] For example, if user A enters the cabin and sits in a seat in the driver's seat, the vehicle-mounted device 200 can obtain sensor data collected by the seat sensor in the driver's seat. If user B enters the cabin and sits in a seat in the passenger seat, the vehicle-mounted device 200 can obtain sensor data collected by the seat sensor in the driver's seat.

[0231] In other embodiments, users may enter the cabin and sit in seats in other areas, such as seats in the back row, and accordingly, the vehicle equipment 200 may obtain sensor data collected by corresponding seat sensors in the corresponding areas, without limitation here.

[0232] 1005: The vehicle-mounted device 200 determines a matching relationship based on the relative positions of each screen and each handheld device and the seating position of each user.

[0233] The specific process of the vehicle-mounted device 200 executing the above steps 1004 to 1005 can refer to the relevant descriptions of steps 704 to 705 in the above embodiment 2, and will not be repeated here.

[0234] 1006a: The vehicle device 200 detects the user's login operation on the screen 200A.

[0235] For example, user A, seated in the driver's seat, can click on the control indicating the login account on screen 200A to log in. Accordingly, screen 200A of vehicle-mounted device 200 can detect the user's login operation and proceed to step 1007a below to send an authorization login request to mobile phone 100A.

[0236] In other embodiments, the vehicle device 200 may also automatically trigger the login account and execute the following step 1007a when no login operation by the user is detected on the screen 200A, and send an authorized login request to the mobile phone 100A. There is no limitation here.

[0237] 1006b: The vehicle device 200 detects the user's login operation on the screen 200B.

[0238] For example, user B, sitting in the driver's seat, can click on the relevant control indicating the login account on screen 200B to log in. Accordingly, screen 200B of vehicle-mounted device 200 can detect the user's login operation and then proceed to step 1007b below to send an authorization login request to mobile phone 100B.

[0239] In other embodiments, the vehicle device 200 may also automatically trigger the login account and execute the following step 1007b when no login operation by the user is detected on the screen 200B, and send an authorized login request to the mobile phone 100B. There is no limitation here.

[0240] 1007a / 1007b: The vehicle device 200 sends an authorization login request to the matching target device mobile phone 100A / mobile phone 100B.

[0241] For example, based on the matching relationship determined in step 1005 above, the vehicle-mounted device 200 can, in response to a login operation detected on screen 200A, send an authorized login request to the mobile phone 100A that matches screen 200A. Similarly, based on the matching relationship determined in step 1005 above, the vehicle-mounted device 200 can, in response to a login operation detected on screen 200B, send an authorized login request to the mobile phone 100B that matches screen 200B.

[0242] The specific implementation process of sending the authorization login request can refer to the relevant description in step 508 in the above embodiment 1, and will not be repeated here.

[0243] In other embodiments, if user A or user B carries multiple handheld devices, such as a mobile phone, a watch, or a tablet computer, the vehicle-mounted device 200 may send authorization login requests to each handheld device of a different type according to the priority order of each handheld device. For details, please refer to the relevant description of step 708 in the above embodiment 2 and will not be repeated here.

[0244] 1008a: The vehicle device 200 displays a third prompt interface through the screen 200A.

[0245] For example, the vehicle-mounted device 200 may display a prompt interface on the screen 200 for prompting the user to perform authorization operations on the mobile phone 100A, which is recorded as a third prompt interface.

[0246] It is understandable that the vehicle device 200 can execute step 1008a to display the third prompt interface before, at the same time as, or after executing step 1007a, and there is no limitation here.

[0247] In some embodiments, the third prompt interface may refer to the prompt interface 810 shown in FIG8a provided in the above embodiment 2. In other embodiments, the third prompt interface may refer to the prompt interface 830 shown in FIG8b provided in the above embodiment 2, which is not limited here.

[0248] 1008b: The vehicle device 200 displays a fourth prompt interface through the screen 200B.

[0249] For example, the vehicle-mounted device 200 may display a prompt interface on the screen 200 for prompting the user to perform authorization operations on the mobile phone 100B, which is recorded as the fourth prompt interface.

[0250] It is understandable that the vehicle device 200 can execute step 1008b to display the fourth prompt interface before, at the same time as, or after executing step 1007b, and there is no limitation here.

[0251] In some embodiments, the fourth prompt interface may refer to the prompt interface 810 shown in FIG8a provided in the above embodiment 2. In other embodiments, the fourth prompt interface may refer to the prompt interface 830 shown in FIG8b provided in the above embodiment 2, which is not limited here.

[0252] 1009a: The screen 200A of the vehicle device 200 detects that the user selects the operation of authorizing the device on the third prompt interface.

[0253] In some embodiments, user A may not use the mobile phone 100B recommended by the vehicle-mounted device 200 to perform the authorization operation, but may select other more convenient handheld terminals (such as a watch, etc.) to perform the authorization operation. Correspondingly, the screen A of the vehicle-mounted device 200 may detect the operation of user A selecting other authorization devices on the third prompt interface.

[0254] In other embodiments, user A may also use the mobile phone 100 recommended by the vehicle device 200 to perform the authorization operation. In this case, the screen 200A of the vehicle device 200 may not execute the following steps 1009a to 1011a, but continue to execute the following steps 1012a to 1014a.

[0255] 1009b: The screen 200B of the vehicle-mounted device 200 detects that the user selects the operation of authorizing the device on the fourth prompt interface.

[0256] In some embodiments, user B may not use the mobile phone 100B recommended by the vehicle-mounted device 200 to perform the authorization operation, but may select other more convenient handheld terminals (such as a watch, etc.) to perform the authorization operation. Correspondingly, the screen B of the vehicle-mounted device 200 may detect the operation of user B selecting other authorization devices on the third prompt interface.

[0257] In other embodiments, user B may also use the mobile phone 100 recommended by the vehicle device 200 to perform the authorization operation. In this case, the screen 200B of the vehicle device 200 may not execute the following steps 1009b to 1011b, but continue to execute the following steps 1012b to 1014b.

[0258] 1010a / 1010b: The vehicle device 200 displays the device list through the screen 200A / screen 200B.

[0259] It is understood that, in response to the user selecting an authorized device, the screen 200A / screen 200B of the vehicle-mounted device 200 may display a device list including other handheld terminals currently connected to the vehicle-mounted device 200. For this device list, reference may be made to the device list interface example and related description corresponding to the scenario shown in FIG. 9e above, and detailed description thereof will not be repeated here.

[0260] 1011a: The vehicle device 200 sends an authorization login request to the target device selected by user A.

[0261] 1011b: The vehicle device 200 sends an authorization login request to the target device selected by user B.

[0262] Exemplarily, the target device selected by the user A / user B may be other handheld terminals selected by the user, such as a watch or tablet computer, or may be a mobile phone 100A / mobile phone 100B selected by the user, and is not limited here.

[0263] 1012a / 1012b: Mobile phone 100A / mobile phone 100B prompts the user to perform authorization operation.

[0264] The specific prompt process can refer to the relevant description in step 510 in the above embodiment, which will not be repeated here.

[0265] 1013a / 1013b: Mobile phone 100A / mobile phone 100B receives the verification information input by the user.

[0266] 1014a / 1014b: Mobile phone 100A / mobile phone 100B sends the verification result to the account cloud.

[0267] The specific processes of receiving verification information, sending authorization verification request, etc. can refer to the relevant description of the mobile phone 100 executing steps 511 to 512 in the above embodiment 1, and will not be repeated here.

[0268] 1015: The vehicle device 200 receives the authorization result information returned by the account cloud.

[0269] 1016: The vehicle device 200 completes the account login on the corresponding screen.

[0270] The specific process of the vehicle-mounted device 200 executing the above steps 1015 to 1016 can correspond to the description of the account cloud 300 executing step 513 and the vehicle-mounted device 200 executing step 512 in the above embodiment 1, which will not be repeated here.

[0271] It can be understood that based on the interaction process shown in Figure 10 above, when multiple users each bring a handheld terminal into the cabin, the vehicle-mounted device 200 can interact with each user's handheld terminal through the corresponding matching screen to implement the authorization method provided by this application. In this way, each user entering the cabin can experience quick login to their account on the screen adapted for the corresponding seat, which is conducive to improving the user experience and allowing the screen in the cabin to be used more frequently.

[0272] Similarly, for the login scenarios shown in FIG. 9 b to FIG. 9 f above, the interaction process between each handheld device and each screen of the vehicle device 200 can refer to the relevant description of each step in the process shown in FIG. 10 , which will not be repeated here.

[0273] Among them, for the login scenario shown in Figure 9e above, the matching relationship between each screen in the vehicle device 200 and the mobile phone 100 carried by each user can refer to Figure 11a, where screen 200A corresponds to the mobile phone 100A carried by user A, screen 200B corresponds to the mobile phone 100B carried by user B, screen 200C corresponds to the mobile phone 100C carried by user C, and screen 200D corresponds to the mobile phone 100D carried by user D.

[0274] In the login scenario shown in FIG9e , if the user selects an authorized device on the screen, the corresponding screen of the vehicle-mounted device 200 may display the device list interface 1110 shown in FIG11b . The device list displayed on interface 1110 may include information related to the user's own and other users' mobile phones as candidate handheld devices. For example, the device list interface 1110 displayed on screen 200A may sequentially display information related to mobile phone 100A, mobile phone 100B, mobile phone 100C, and mobile phone 100D. By clicking the "Click to Login" login control corresponding to mobile phone 100A, mobile phone 100B, mobile phone 100C, or mobile phone 100D on device list interface 1110, the user can set the corresponding mobile phone as an authorized device. It is understood that if user A wants to log in to user C's account using mobile phone 100C, user C is typically required to verify user C's biometric information on the authorization verification interface displayed on mobile phone 100C. This operation, with user C's authorization, will log in user C's personal account on screen 200A.

[0275] Similarly, in other embodiments, multiple users entering the cabin each carry multiple handheld devices, i.e., m users carry n handheld terminals (where m < n). In this case, the vehicle-mounted device quickly matches the screen used by each user with the handheld device used to authorize the login account, and can also select a more recommended authorized device from the multiple handheld devices carried by each user. At the same time, the vehicle-mounted device can also display a list of handheld device-related information related to each user on the corresponding screen in response to the user selecting another handheld terminal as the authorized device.

[0276] As an example, referring to the login scenario shown in Figure 12a, user A can enter the cabin with mobile phone 100A, watch 400A, and tablet computer 500A and sit in the driver's seat. User C can enter the cabin with mobile phone 100C and watch 400C and sit in the left rear seat. After establishing device connections with mobile phone 100A, watch 400A, tablet computer 500A, mobile phone 100C, and watch 400C, vehicle-mounted device 200 can determine the matching relationship between the corresponding screen and the corresponding handheld terminal based on the detection results of ultrasonic detection technology and the detection results of the seat sensor.

[0277] Referring to Figure 12b, the matching relationship between the screen and the handheld device in the login scenario shown in Figure 12a above may include the corresponding matching relationship between the screen 200A and the mobile phone 100A, watch 400A, and tablet computer 500A carried by user A, and the corresponding matching relationship between the screen 200C and the mobile phone 100C and watch 400C carried by user C.

[0278] In the login scenario shown in FIG12a above, if the user operates on the screen used to select an authorized device, the corresponding screen of the vehicle device 200 can display the device list interface 1210 shown in FIG12c. The device list displayed on the interface 1210 may include information related to the mobile phones carried by the user and other users as alternative handheld devices. For example, the device list interface 1210 displayed on the above screen 200A may preferentially display relevant information of the mobile phone 100A, watch 400A, and tablet computer 500A, and may also display relevant information of the mobile phone 100C and watch 400C for the user to select. The user clicks on the login control corresponding to the corresponding handheld device in the device list interface 1210 to set the corresponding handheld device as an authorized device. The specific selection process can refer to the relevant description above and will not be repeated here.

[0279] In other embodiments, if the number of users entering the cabin exceeds the number of screens in the vehicle-mounted device, each user may bring one or more handheld devices. In this scenario, multiple users may need to log in to their accounts using the same screen on the vehicle-mounted device. In this case, when the vehicle-mounted device quickly matches the handheld device used for authorized login to each user's screen, it may not display a recommended authorized device, but instead display a list of handheld devices for the user to select.

[0280] As an example, referring to the login scenario shown in Figure 13a, vehicle-mounted device 200 only has screens 200A, 200B, and 200C. In this scenario, user A can enter the cabin with mobile phone 100A and sit in the driver's seat; user B can enter the cabin with mobile phone 100B and sit in the passenger seat; user C can enter the cabin with mobile phone 100C and sit in the left rear seat; and user D can enter the cabin with mobile phone 100D and sit in the right rear seat. After vehicle-mounted device 200 establishes device connections with mobile phones 100A, 100B, 100C, and 100D, it may be impossible to determine the matching relationship between screen 200C and mobile phones 100C and 100D based on the detection results of ultrasonic detection technology and the detection results of the seat sensors. If user C or user D logs in to their account on screen 200C, screen 200C may display a device list interface containing information related to mobile phone 100C and mobile phone 100D for selection by user C or user D sitting in the back seat.

[0281] Similarly, referring to the login scenario shown in FIG13b , user A can enter the cabin with mobile phone 100A and sit in the driver's seat. User B can enter the cabin with mobile phone 100B and sit in the passenger seat. User C, user D, and user E can enter the cabin with mobile phone 100C, mobile phone 100D, and mobile phone 100E, respectively, and sit in the left, center, and right seats in the rear seat. In this case, based on the detection results of ultrasonic detection technology and the detection results of the seat sensors, the vehicle-mounted device 200 may not be able to determine the matching relationship between screen 200C and mobile phone 100C, mobile phone 100D, and mobile phone 100E, or may only determine the matching relationship between screen 200C and the closer mobile phone 100D. If user C, user D, or user E logs in to their account on screen 200C, screen 200C may display a device list interface containing information related to mobile phone 100C, mobile phone 100D, and mobile phone 100E, allowing user C, user D, or user E in the rear seat to select a device.

[0282] In other embodiments, among the multiple users entering the cabin, some may carry handheld terminals, while others may not, that is, m users carry n handheld terminals (where m>n). In this scenario, the vehicle-mounted device may detect, based on the seat sensors, that there are users sitting on seats in multiple areas. At this time, the vehicle-mounted device quickly displays the name or model of the handheld device on the screen used by each user, so that the users in the cabin can refer to it to determine the user to whom the recommended authorized device belongs, and then instruct the corresponding user to authorize login on the corresponding handheld device. I will not elaborate on this here.

[0283] FIG14 shows a schematic diagram of the hardware structure of an electronic device according to an embodiment of the present application.

[0284] As shown in FIG14 , the electronic device 1400 may include a processor 110, a wireless communication module 120, a mobile communication module 130, a power module 140, an audio module 150, an interface module 160, a main camera 170 and a wide-angle camera 171, a memory 180, a sensor module 190, a button 102, a motor 103, and an indicator 104. The sensor module 190 may include a seat sensor, an acceleration sensor, a distance sensor, a proximity light sensor, a touch sensor, an ambient light sensor, and the like.

[0285] It should be understood that the structure illustrated in the embodiment of the present invention does not constitute a specific limitation on the electronic device 1400. In other embodiments of the present application, the electronic device 1400 may include more or fewer components than shown, or may combine or separate certain components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0286] In the embodiment of the present application, the electronic device 1400 shown in FIG14 may be the above-mentioned vehicle device 200, or may be an electronic device such as a handheld terminal carried by a user, and no limitation is made here.

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

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

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

[0290] In an embodiment of the present application, the processor 110 of the vehicle-mounted device 200 can complete instruction fetching, instruction execution, etc. through the controller to implement the relevant steps executed by the vehicle-mounted device 200 and each screen in the above-mentioned embodiments 1 to 3. For details, please refer to the relevant descriptions in the above-mentioned embodiments, which will not be repeated here.

[0291] The interface module 160 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 SIM card interface, and / or a universal serial bus (USB) interface, etc.

[0292] Among them, the I2S interface can be used for audio communication. In some embodiments, the processor 110 can include multiple I2S buses. The processor 110 can be coupled to the audio module 150 via the I2S bus to enable communication between the processor 110 and the audio module 150. In some embodiments, the audio module 150 can transmit audio signals to the wireless communication module 120 via the I2S interface, enabling the function of answering calls through a Bluetooth headset.

[0293] The PCM interface can also be used for audio communication, sampling, quantizing, and encoding analog signals. In some embodiments, the audio module 150 and the wireless communication module 120 can be coupled via a PCM bus interface. In some embodiments, the audio module 150 can also transmit audio signals to the wireless communication module 120 via the PCM interface, enabling the function of answering calls via a Bluetooth headset. Both the above-mentioned I2S interface and the above-mentioned PCM interface can be used for audio communication.

[0294] The UART interface is a universal serial data bus used for asynchronous communication. This bus can be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, the UART interface is typically used to connect the processor 110 and the wireless communication module 120. For example, the processor 110 communicates with the Bluetooth module in the wireless communication module 120 via the UART interface to implement Bluetooth functionality. In some embodiments, the audio module 150 can transmit audio signals to the wireless communication module 120 via the UART interface, enabling the function of playing music through Bluetooth headphones.

[0295] 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. USB interface 130 can be used to connect a charger to charge electronic device 1400, or to transfer data between electronic device 1400 and peripheral devices. It can also be used to connect headphones to play audio. This interface can also be used to connect other electronic devices, such as AR devices.

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

[0297] The power module 140 is used to connect the battery, the charging management module, and the processor 110. The power module 140 receives input from the battery and / or the charging management module and provides power to the processor 110, the memory 180, the main camera 170, the wide-angle camera 171, and the wireless communication module 120.

[0298] The wireless communication module 120 can provide wireless communication solutions for application in the electronic device 1400, 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 technology (NFC), infrared technology (IR), etc.

[0299] The mobile communication module 130 can provide wireless communication solutions including 2G / 3G / 4G / 5G, etc. applied to the electronic device 1400. The mobile communication module 130 can include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc.

[0300] The main camera 170 and the wide-angle camera 171 are 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 to be converted into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in standard RGB, YUV and other formats.

[0301] The memory 180 can be used to store computer executable program code, which includes instructions. The internal memory 180 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 electronic device 1400 (such as audio data, a phone book, etc.), etc. In addition, the memory 180 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 electronic device 1400 by running instructions stored in the memory 180, and / or instructions stored in a memory provided in the processor.

[0302] The electronic device 1400 can implement audio functions such as music playback and recording through the audio module 150, speakers, receivers, microphones, and application processors.

[0303] The audio module 150 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 150 can also be used to encode and decode audio signals. In some embodiments, the audio module 150 can be provided in the processor 110, or some functional modules of the audio module 150 can be provided in the processor 110.

[0304] The speaker, also called a "horn," is used to convert audio electrical signals into sound signals. The electronic device 1400 can listen to music or make hands-free calls through the speaker 170A.

[0305] The receiver, also called a handset, is used to convert audio electrical signals into sound signals. When the electronic device 1400 receives a call or a voice message, the voice can be received through the receiver.

[0306] A microphone, also known as a "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or sending a voice message, the user can put their mouth close to the microphone and speak to input the sound signal into the microphone. The electronic device 1400 can be provided with at least one microphone 170C. In other embodiments, the electronic device 1400 can be provided with two microphones 170C, which can not only collect sound signals but also realize noise reduction function. In other embodiments, the electronic device 1400 can also be provided with three, four or more microphones 170C to realize sound signal collection, noise reduction, and identification of sound sources, and realize directional recording function, etc.

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

[0308] The seat sensor can be used to convert pressure data detected by the pressure sensor into sensor data indicating whether a user is seated in the corresponding seat. For example, the seat sensor can convert pressure data within a certain range detected by the pressure sensor, including pressure data corresponding to the possible weights of adults, children, and elderly people, into sensor data indicating whether a user is seated in the corresponding seat.

[0309] The accelerometer can detect the magnitude of acceleration of the electronic device 1400 in all directions (generally three axes). When the electronic device 1400 is stationary, it can detect the magnitude and direction of gravity. It can also be used to identify the electronic device's posture, enabling applications such as switching between landscape and portrait modes and pedometers.

[0310] A distance sensor is used to measure distance. The electronic device 1400 can measure distance using infrared or laser. In some embodiments, when photographing a scene, the electronic device 1400 can use the distance sensor to measure distance to achieve fast focusing.

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

[0312] The ambient light sensor senses ambient light brightness. Electronic device 1400 can adaptively adjust display brightness based on the perceived ambient light. The ambient light sensor can also be used to automatically adjust white balance when taking photos. The ambient light sensor can also work in conjunction with the proximity sensor to detect whether electronic device 1400 is in a pocket to prevent accidental touches.

[0313] A touch sensor, also known as a "touch device," can be provided on a display screen. The touch sensor and the display screen form a touch screen, also known as a "touch screen." The touch sensor is used to detect touch operations applied to or near the touch sensor. The touch sensor can transmit the detected touch operations to an application processor to determine the type of touch event. Visual output related to the touch operation can be provided through the display screen. In other embodiments, the touch sensor can also be provided on the surface of the electronic device 1400, in a location different from that of the display screen.

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

[0315] Motor 103 can generate vibration prompts. Motor 103 can be used for incoming call vibration prompts, and can also be used for touch vibration feedback. For example, touch operations acting on different applications (such as taking pictures, audio playback, etc.) can correspond to different vibration feedback effects. Motor 103 can also correspond to different vibration feedback effects for touch operations acting on different areas of the display screen. Different application scenarios (for example: time reminders, receiving messages, alarm clocks, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also support customization.

[0316] The indicator 104 may be an indicator light, which may be used to indicate charging status, power level changes, messages, missed calls, notifications, etc.

[0317] The embodiments of the present application also provide a computer program product for implementing the authorization methods provided in the above embodiments.

[0318] The various embodiments of the mechanisms disclosed in this application can be implemented in hardware, software, firmware, or a combination of these implementation methods. The embodiments of the present application can be implemented as computer program modules or module codes executed on a programmable system, which includes at least one processor, a storage system (including volatile and non-volatile memory and / or storage elements), at least one input device, and at least one output device.

[0319] A computer program module or module code can be applied to input instructions to perform the functions described herein and generate output information. The output information can be applied to one or more output devices in a known manner. For the purposes of this application, a processing system includes any system having a processor such as, for example, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), or a microprocessor.

[0320] Module code can be implemented with high-level modular language or object-oriented programming language to communicate with the processing system. When necessary, module code can also be implemented with assembly language or machine language. In fact, the mechanism described in this application is not limited to the scope of any specific programming language. In either case, the language can be a compiled language or an interpreted language.

[0321] In some cases, the disclosed embodiments may be implemented in hardware, firmware, software, or any combination thereof. The disclosed embodiments may also be implemented as instructions carried or stored on one or more temporary or non-temporary machine-readable (e.g., computer-readable) storage media, which may be read and executed by one or more processors. For example, instructions may be distributed over a network or through other computer-readable media. Therefore, a machine-readable medium may include any mechanism for storing or transmitting information in a machine (e.g., computer) readable form, including but not limited to a floppy disk, an optical disk, an optical disk, a magneto-optical disk, a read-only memory (ROM), a random access memory (RAM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic card or an optical card, a flash memory, or a tangible machine-readable memory for transmitting information (e.g., a carrier wave, an infrared signal, a digital signal, etc.) using the Internet in an electrical, optical, acoustic, or other form of propagation signal. Accordingly, machine-readable media includes any type of machine-readable media suitable for storing or transmitting electronic instructions or information in a form readable by a machine (eg, a computer).

[0322] References in the specification to "one embodiment" or "an embodiment" mean that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one exemplary implementation or technique disclosed according to the embodiment of the present application. The appearances of the phrase "in one embodiment" in various places in the specification do not necessarily all refer to the same embodiment.

[0323] The disclosure of the embodiments of the present application also relates to an operating device for executing the text. The device can be constructed specifically for the required purpose or it can include a general-purpose computer that is selectively activated or reconfigured by a computer program stored in the computer. Such a computer program can be stored in a computer-readable medium, such as, but not limited to, any type of disk, including a floppy disk, an optical disk, a CD-ROM, a magneto-optical disk, a read-only memory (ROM), a random access memory (RAM), an EPROM, an EEPROM, a magnetic or optical card, an application-specific integrated circuit (ASIC) or any type of medium suitable for storing electronic instructions, and each can be coupled to a computer system bus. In addition, the computer mentioned in the specification can include a single processor or can be an architecture involving multiple processors for increased computing power.

[0324] In addition, the language used in this specification has been primarily selected for readability and instructional purposes and may not be selected to describe or limit the disclosed subject matter. Therefore, the present disclosure of embodiments is intended to illustrate, not to limit, the scope of the concepts discussed herein.

Claims

1. An authorization method, characterized in that: The method comprises: Detecting that a spatial position relationship between the first user device and the first screen of the first spatial device satisfies a first condition; Sending first authorization request information to the first user device, where the first authorization request information is used to request logging in to a first account on the first screen, where the first account is an account logged in to the first user device; The first authorization result information is received, and corresponding to the first authorization result information indicating that the authorization is passed, the first account is logged in on the first screen.

2. The method according to claim 1, characterized in that The first space device is arranged inside the physical space, and the first user device is a device that enters the physical space.

3. The method according to claim 2, characterized in that The physical space includes a cabin of a vehicle, and, The detecting that the spatial position relationship between the first user equipment and the first screen of the first space equipment satisfies the first condition includes: It is detected that the first user equipment is located in a first area associated with the first screen in the cockpit.

4. The method according to claim 3, characterized in that: The method further comprises: It is detected that the spatial position relationship between the second user equipment and the first screen satisfies the first condition, and, The sending first authorization request information to the first user equipment includes: In a case where it is determined that the priority of the first user equipment is higher than the priority of the second user equipment, the first authorization request information is sent to the first user equipment.

5. The method according to claim 4, characterized in that The method is applied to the first spatial device or to the second spatial device, and, When the method is applied to the second space device, logging into the first account on the first screen includes: The second space device sends a login instruction to the first space device, wherein the login instruction is used to instruct the first space device to log in to the first account on the first screen.

6. The method according to any one of claims 1 to 5, characterized in that Before sending the first authorization request information to the first user equipment, the method further includes: Displaying a selectable device list on the first screen, the selectable device list including device information of a plurality of user devices, wherein the spatial position relationship between the plurality of user devices and the first screen satisfies the first condition, the plurality of user devices including the first user device; and The sending first authorization request information to the first user equipment includes: In a case where it is detected that the user selects the first user equipment, first authorization information is sent to the first user equipment.

7. The method according to any one of claims 1 to 6, characterized in that The method further comprises: Detecting that a spatial position relationship between a third user device and a second screen of the first spatial device satisfies a second condition; Sending a second authorization request message to the third user device, where the second authorization request message is used to request to log in a second account on the second screen, where the second account is an account logged in on the third user device; The second authorization result information is received, and corresponding to the second authorization result information indicating that the authorization is passed, the second account is logged in on the second screen.

8. The method according to any one of claims 1 to 7, characterized in that The relevant information of the first account is stored in the server; and the first authorization result information includes the relevant information of the first account.

9. The method according to any one of claims 1 to 8, characterized in that The first space equipment includes vehicle equipment.

10. An authorization system, characterized in that: The system includes a third space device and a server, wherein: The third space device is used to send a first authorization request message to the first user device when it is detected that the spatial position relationship between the first user device and the first screen of the first space device meets the first condition, wherein the first authorization request message is used to request to log in a first account on the first screen, and the first account is an account logged in on the first user device; the third space device and the first space device are the same device or different devices: The server is configured to send first authorization result information to the third space device when receiving information indicating authorization from the first user equipment; and When the third space device determines that the first authorization result information indicates that the authorization is passed, the third space device logs in the First account.

11. The system according to claim 10, characterized in that The system further includes the first user equipment, wherein: The first user device is used to respond to the first authorization request information and display a fourth interface, wherein the fourth interface is used to prompt the user to perform an authorization operation; and The first user equipment is further configured to respond to the user's authorization operation and send information indicating authorization to the server.

12. The system according to claim 10 or 11, characterized in that The third space equipment is arranged inside a physical space, the physical space includes a cabin of a vehicle, and, The manner in which the third space device detects that the spatial position relationship between the first user equipment and the first screen of the first space device satisfies the first condition includes: The third space device detects that the first user device is located in a first area associated with the first screen in the cockpit.

13. The system according to claim 12, characterized in that The third space device sends first authorization request information to the first user equipment, including: The third space device sends first authorization request information to the first user device when detecting that the spatial position relationship between the second user device and the first screen satisfies the first condition and determining that the priority of the first user device is higher than that of the second user device.

14. An electronic device, characterized in that: include: one or more processors; One or more memories; the one or more memories store one or more programs, and when the one or more programs are executed by the one or more processors, the electronic device executes the authorization method described in any one of claims 1 to 9.

15. A computer readable medium, characterized in that The readable medium stores instructions, which, when executed on a computer, enable the computer to execute the authorization method according to any one of claims 1 to 9.

Images