Authorization method, authorization system, electronic equipment and computer readable medium

Abstract

The invention relates to the technical field of terminal electronic equipment, in particular to an authorization method, an authorization system, electronic equipment and a computer readable medium, and aims to match each screen in a cabin with a handheld device suitable for the user to perform authorization operation by identifying the relative position of the handheld device carried by the user. Each screen can prompt the user to perform authorization verification through the matched handheld device, thereby supporting the user to quickly log in an account on the corresponding screen. Thus, when the user enters the cabin and needs to log in the account on the screen in the cabin, the handheld device matched with the corresponding screen can be used for authorization verification, the operation process that the user logs in the account on the corresponding screen is simplified, and the purpose of rapid login is achieved. Therefore, the user experience is improved, and the idle screen resources in the cabin are reduced.

Description

Technical Field

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

[0002] With the development of intelligent technologies, the physical space including multiple devices is gradually evolving towards an intelligent physical space centered on human-computer interaction and featuring multi-screen linkage. This physical space can include spaces such as intelligent cockpits and smart homes. Taking the intelligent cockpit as an example, currently, intelligent cockpits that support multiple screens and multiple users have become the mainstream development trend. To achieve multiple screens and multiple users, each screen of the in-vehicle device in the cockpit needs to support independent account logins. Therefore, a user riding in a vehicle can log in to their personal account when getting in the car, and when getting out of the car, the user can also log out of the logged-in account to prevent the leakage of personal privacy data. The same user may need to repeatedly log in to their personal account at different times when sitting in the same seat or different seats to conveniently use the screen that is closer.

[0003] However, currently, each screen in the cockpit supports independent user account logins, but usually, users need to enter account passwords for login or use handheld devices such as mobile phones to scan the QR codes displayed on the cockpit screen for login, and the operations are relatively cumbersome. Moreover, the method of using the near field communication (NFC) function of the car key to achieve account login often only supports the main driver to quickly log in to the account and does not support multi-user logins. Also, due to cost considerations, few of the multiple screens in the cockpit are equipped with biometric recognition devices, and multi-users cannot log in to the account through biometric recognition either. These factors combined result in the multiple screens in the cockpit being easily idle because it is inconvenient for multi-users to quickly log in to the account, which not only affects the user experience but also causes a waste of screen resources. Summary of the Invention

[0004] The present application provides an authorization method, an authorization system, an electronic device, and a computer-readable medium. When a user enters the cockpit and needs to log in to an account on the screen in the cockpit, authorization verification can be performed using a handheld device that matches the corresponding screen, simplifying the operation process of the user logging in to the account on the corresponding screen and achieving the purpose of quick login.

[0005] In a 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 spatial device satisfies a first condition; sending a first authorization request message to the first user device, where the first authorization request message is used to request to log in to a first account on the first screen, and the first account is the account logged in on the first user device; receiving a first authorization result message, and corresponding to the first authorization result message indicating that the authorization is passed, logging in to the first account on the first screen.

[0006] For example, the above-mentioned first user device may be an electronic device such as a mobile phone, a tablet computer, or a watch carried by a user. The above-mentioned first spatial device may be an electronic device fixedly installed in a certain space, such as a vehicle-mounted device in a smart cockpit (i.e., a vehicle cockpit). The first spatial device may 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 may determine the matching relationship between the user device and one or more screens controlled by the vehicle-mounted device after the user device enters the vehicle cockpit. For example, if a user carries a mobile phone and rides in the driver's area, the present application may determine the corresponding matching between the mobile phone and the screen in the driver's area according to the spatial position relationship between the mobile phone and the screen in the driver's area. At this time, if the user clicks to log in to an account on the screen in the driver's area, the vehicle-mounted device may 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.

[0007] It can be understood that in the authorization scheme provided in the above-mentioned first aspect, when the relative position relationship between the above-mentioned first screen and the first user device satisfies certain conditions, such as satisfying the above-mentioned first condition, an authorization request, such as the above-mentioned first authorization request message, may be sent to the first user device. The authorization request message may allow the user to perform an authorization operation through the first user device, so as to quickly log in to an account on the first spatial device in the space, such as quickly logging in to the above-mentioned first account. Among them, the above-mentioned first account may be the account that the user has logged in on the first user device and intends to log in on the first screen of the above-mentioned first spatial device. Correspondingly, the above-mentioned first condition may be used to determine the area where each seat is located in the vehicle cockpit for the first user device, such as a mobile phone, and then based on the first condition, the matching relationship between the first user device and the screen (such as the above-mentioned first screen) in the corresponding area may be determined. That is, the first condition may be used to determine the matching relationship between the first screen and the first user device located in the area associated with the screen.

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

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

[0010] For example, the above first space device may be a vehicle-mounted device disposed inside the vehicle cockpit, and the above first user device may be an electronic device such as a mobile phone, a tablet computer, or a watch that the user carries into the vehicle cockpit.

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

[0012] For example, when the first user device is a mobile phone and the user carries the mobile phone into the vehicle cockpit, the vehicle-mounted device can use ultrasonic detection technology or array signal processing technology based on wireless signals to detect that the position of the mobile phone can be in the driver's area or the passenger's area, or can also be in the area where the rear seats are located, etc. The vehicle-mounted device can use the speaker array inside the vehicle cockpit to form an ultrasonic device array to realize the detection of the area where the mobile phone is located. Furthermore, the vehicle-mounted device can determine that the spatial position relationship between the first screen associated with the detected area of the mobile phone and the mobile phone satisfies the above first condition. At this time, a matching relationship can be formed between the mobile phone and the above first screen.

[0013] In a possible implementation of the above first aspect, detecting that the spatial position relationship between the second user device and the first screen satisfies the first condition, and sending a first authorization request message to the first user device includes: sending a first authorization request message to the first user device when it is determined that the priority of the first user device is higher than the priority of the second user device.

[0014] For example, the above first user device and the second user device may be electronic devices carried by the same user, specifically, it can be reflected that the first user device and the second user device log in to the same account. As an example, the first user device is a mobile phone, and the second user device is a tablet computer. The priorities of the first user device and the second user device can be determined according to one or more of the security capabilities, processing capabilities, or other relevant capabilities of each device, or can also be determined based on user settings, which are not limited here. For example, the mobile phone with stronger security capabilities may have a higher priority than the tablet computer with lower security capabilities, etc.

[0015] In a possible implementation of the above first aspect, the method is applied to the first spatial device or the second spatial device, and in the case where the method is applied to the second spatial device, logging in to the first account on the first screen includes: the second spatial device sending a login instruction to the first spatial device, where the login instruction is used to instruct the first spatial device to log in to the first account on the first screen.

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

[0017] In other embodiments, the authorization scheme provided by the above first aspect and various possible implementations can be implemented by another electronic device, such as the above second spatial device, which can be another in-vehicle device in the vehicle cockpit, for example. For example, the second spatial device can detect whether the spatial position relationship between the above first user device and the first screen meets the first condition, send the first authorization request information to the first user device, and receive the first authorization result information, etc. At this time, a communication connection can be established between the second spatial device and the first spatial 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, according to the received first authorization result information, the second spatial device can send a corresponding login instruction to the first spatial device to log in to the user's first account on the first screen. It can be understood that after the login is completed, the corresponding interface after successful login can be displayed on the first screen, which is not limited here.

[0018] It can be understood that in the scenario where the above second spatial device implements the authorization scheme provided by this application, the spatial position relationship between the first user device and the first screen can also be detected by the first spatial device and the detection result can be sent to the second spatial device. When the second spatial device receives the first authorization result information, it can also send the information to the first spatial device, which is not limited here.

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

[0020] For example, when the above-mentioned first space device or second space device sends the above-mentioned first authorization request information to the first user device, or before that, it can display a prompt interface on the first screen operated by the user, such as the above-mentioned first interface. The prompt interface can prompt the user to pick up the first user device such as a mobile phone for authorization confirmation operation. In some other embodiments, the authorization confirmation operation can also be described as an authorization operation. The prompt interface, that is, the above-mentioned first interface, can be, for example, the one Figure 2a or Figure 2b shown in the prompt interface.

[0021] In some embodiments, the above-mentioned first interface may include a control for indicating the selection of an authorized device, such as the selection control 212 on the prompt interface 210 shown below Figure 2a or the selection control 232 on the prompt interface 230 shown below Figure 2b When the user clicks the control for indicating the selection of an authorized device on the above-mentioned first interface, the above-mentioned first screen can correspondingly display a list of selectable devices in the current vehicle cockpit. The list of selectable devices may include device information corresponding to multiple user devices, and the spatial position relationship between each user device and the first screen all satisfies the above-mentioned first condition.

[0022] For example, the user gets in the car with multiple devices such as a mobile phone, a tablet computer, and a watch. The above-mentioned first user device is the mobile phone placed in the driver's area. The device information displayed in the above-mentioned list of selectable devices may include the device information of the mobile phone placed in the driver's area and other devices. These user devices can be devices carried by the same user sitting on the corresponding seat, or devices carried by multiple users sitting on other seats in the front row or the rear row area. There is no limitation here.

[0023] In some other embodiments, the above-mentioned list of selectable devices may also display the device information of devices placed in other areas in the vehicle cockpit, including the device information of devices placed in the passenger area and the device information of devices placed in the rear seat area, etc. There is no limitation here.

[0024] As an example, if the above-mentioned first screen is the display screen in the driver's area, the corresponding area range of the first screen can be the front row driver's area and the passenger area in the vehicle cockpit, that is, at this time, the first screen of the in-vehicle device can display user devices such as mobile phones placed in the driver's area or the passenger area. If the above-mentioned first screen is the display screen in the rear row area, the corresponding area range of the first screen can be the rear row area in the vehicle cockpit, that is, at this time, the first screen of the in-vehicle device can display user devices such as mobile phones placed in the rear row area. In some other embodiments, the above-mentioned first screen can also display the user devices in each area of the vehicle cockpit in order according to the matching degree corresponding to the relative position. There is no limitation here.

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

[0026] For example, before a vehicle-mounted device sends authorization request information to a user device such as a mobile phone, it can display an optional device list for the user to select an authorized device. The device information displayed in the optional device list may include the corresponding device information of a mobile phone or a 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 can send the foregoing first authorization request information to a device with a higher priority, such as a mobile phone, according to the priorities of different devices. The vehicle-mounted device can also select a tablet computer as the user device for the authorization operation according to the user's instruction. At this time, the vehicle-mounted device sends the foregoing first authorization request information to the tablet computer, which is not limited herein.

[0027] It can be understood that in some embodiments, when the vehicle-mounted device also sends the foregoing first authorization request information to a device with a higher priority, such as a mobile phone, it can display the foregoing first interface for prompting the user to perform an authorization operation on the first screen, and the first interface includes the foregoing control for indicating the selection of an authorized device. When it is detected that the user clicks the control and selects another user device, such as a tablet computer, in the foregoing optional device list, the authorization request information can be sent to the tablet computer again, which is not limited herein.

[0028] In a possible implementation of the foregoing first aspect, it is detected that the spatial position relationship between the third user device and the second screen of the first spatial device satisfies a second condition; sending second authorization request information to the third user device, where the second authorization request information is used to request to log in to a second account on the second screen, and the second account is an account logged in on the third user device; receiving second authorization result information, and corresponding to the second authorization result information indicating that the authorization is passed, logging in to the second account on the second screen.

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

[0030] In a possible implementation of the above first aspect, 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.

[0031] For example, the above server can be an electronic device running platforms such as account cloud. The relevant information of the accounts registered and logged in by users through user devices such as mobile phones can be stored on this server, including accounts, passwords, etc. For the convenience of managing the login status and security of each user's account, etc., 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, based on the solution of the present application, the user can use the mobile phone to perform identity verification and authorize to log in to the same account on the first screen of the above first space device, for example, authorize to log in to the account on the screen in the main driver area of the vehicle-mounted device, etc. At this time, the mobile phone can verify biometric information input by the user, etc., confirm the user's identity, and after determining that the identity is legal, can send the confirmation result to the server or the account cloud, and then the server can send the above first authorization result information to the screen of the account to be logged in to notify the screen or the corresponding vehicle-mounted device that the authorization is passed. The relevant information such as the account and password of the corresponding account can also be carried in the authorization result information to facilitate the quick login of the relevant account by the screen.

[0032] In a possible implementation of the above first aspect, 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 Wi-Fi technology; a connection established based on ultra-wideband wireless carrier communication technology; a connection established based on XingShan technology.

[0033] It can be understood that if there are two or more space devices in the same physical space, such as in the same vehicle cockpit, the space devices can also establish communication connections based on the above various methods. Similarly, if there are multiple user devices in the same vehicle cockpit, the user devices logged in to the same account can also establish communication connections based on the above various methods, and there is no limitation here.

[0034] In some other embodiments, the above physical space may also be a space including other multi-device spaces, such as a smart home space, etc., which is not limited herein.

[0035] In a possible implementation of the first aspect above, the first space device includes a vehicle head unit device.

[0036] In some other embodiments, the above first space device may also include an electronic device disposed in other spaces, such as a large-screen device in a smart home space, etc., which is not limited herein.

[0037] In a second aspect, the present application provides an authorization system, which includes a third space device and a server. Among them, the third space device is configured 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 a first condition. The first authorization request message is used to request to log in to 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 configured to send a first authorization result message to the third space device when it receives information indicating authorization from the first user device. And, when the third space device determines that the first authorization result message indicates authorization passed, it logs in to the first account on the first screen.

[0038] In a possible implementation of the second aspect above, the system further includes a first user device. The first user device is configured to respond to the first authorization request message and display a fourth interface, where the fourth interface is used to prompt the user to perform an authorization operation. And, the first user device is further configured to respond to the user's authorization operation and send information indicating authorization to the server.

[0039] In a possible implementation of the second aspect above, the third space device is disposed inside the physical space, and the physical space includes the cockpit of a vehicle. And, the manner 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 a first area associated with the first screen inside the cockpit.

[0040] In a possible implementation of the second aspect above, the third space device sending the first authorization request message to the first user device includes: the third space device sending the first authorization request message to the first user device when it detects that the spatial position relationship between the second user device and the first screen meets the first condition and determines that the priority of the first user device is higher than the priority of the second user device.

[0041] In a third aspect, the present application provides an electronic device, including: one or more processors; one or more memories; and one or more programs stored in the one or more memories, which, when executed by the one or more processors, cause the electronic device to execute the authorization method provided in the first aspect and various possible implementations thereof.

[0042] In a fourth aspect, the present application provides a computer-readable medium, on which instructions are stored, and when the instructions are executed on a computer, the computer is caused to execute the authorization method provided in the first aspect and various possible implementations thereof.

[0043] In a fifth aspect, the present application provides a computer program product, including a computer program / instructions, which, when executed by a processor, implement the authorization method provided in the first aspect and various possible implementations thereof.

[0044] For the beneficial effects of the second to fifth aspects above, reference may be made to the relevant descriptions in the first aspect and various possible implementations of the first aspect, which will not be elaborated herein. Description of the Drawings

[0045] Figure 1a Fig. shows a schematic diagram of an application scenario of multi-screen and multi-user login accounts in a cockpit.

[0046] Figure 1b Fig. shows another schematic diagram of an application scenario of multi-screen and multi-user login accounts in a cockpit.

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

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

[0049] Figure 3 Fig. shows a schematic diagram of the system software structure of an electronic device provided in an embodiment of the present application.

[0050] Figure 4 Fig. shows a schematic diagram of a login scenario where a user enters a cockpit with a handheld device in Embodiment 1 of the present application.

[0051] Figure 5a Fig. shows a schematic diagram of the implementation process of an authorization method provided in Embodiment 1 of the present application.

[0052] Figure 5bThe figure shows a schematic diagram of a measurement scenario in which a vehicle-mounted device in the cockpit of the present application's Embodiment 1 controls the emission of an ultrasonic detection signal.

[0053] Figure 6 The figure shows a schematic diagram of a login scenario in which a user in Embodiment 2 of the present application enters the cockpit while carrying a handheld device.

[0054] Figure 7 The figure shows a schematic diagram of the implementation process of an authorization method provided in Embodiment 2 of the present application.

[0055] Figure 8a The figure shows a schematic diagram of a prompt interface and a device list interface displayed by the vehicle-mounted device in response to a user's operation of logging in to an account in Embodiment 2 of the present application.

[0056] Figure 8b The figure shows another schematic diagram of a prompt interface displayed by the vehicle-mounted device in response to a user's operation of logging in to an account in Embodiment 2 of the present application.

[0057] Figure 9a The figure shows a schematic diagram of a login scenario in which two users in Embodiment 3 of the present application enter the cockpit while carrying two handheld devices respectively.

[0058] Figure 9b The figure shows another schematic diagram of a login scenario in which two users in Embodiment 3 of the present application enter the cockpit while carrying two handheld devices respectively.

[0059] Figure 9c The figure shows a schematic diagram of a login scenario in which three users in Embodiment 3 of the present application enter the cockpit while carrying three handheld devices respectively.

[0060] Figure 9d The figure shows another schematic diagram of a login scenario in which three users in Embodiment 3 of the present application enter the cockpit while carrying three handheld devices respectively.

[0061] Figure 9e The figure shows a schematic diagram of a login scenario in which four users in Embodiment 3 of the present application enter the cockpit while carrying four handheld devices respectively.

[0062] Figure 9f The figure shows another schematic diagram of a login scenario in which three users in Embodiment 3 of the present application enter the cockpit while carrying three handheld devices respectively.

[0063] Figure 10 The figure shows a schematic diagram of the implementation process of an authorization method provided in Embodiment 3 of the present application.

[0064] Figure 11a As shown above Figure 9eSchematic diagram of the matching relationship between each screen in the in-vehicle device and each mobile phone carried by each user in the shown login scenario.

[0065] Figure 11b As shown above Figure 9e Schematic diagram of a device list interface displayed on screen 200A in the shown login scenario.

[0066] Figure 12a Schematic diagram of a login scenario corresponding to m users carrying n handheld terminals (where m < n) entering the cockpit provided by an embodiment of the present application.

[0067] Figure 12b As shown above Figure 12a Schematic diagram of the matching relationship between each screen in the in-vehicle device and each mobile phone carried by each user in the shown login scenario.

[0068] Figure 12c As shown above Figure 12a Schematic diagram of a device list interface displayed on screen 200A in the shown login scenario.

[0069] Figure 13a Schematic diagram of a login scenario corresponding to the number of users entering the cockpit being greater than the number of screens in the in-vehicle device provided by an embodiment of the present application.

[0070] Figure 13b Schematic diagram of another login scenario corresponding to the number of users entering the cockpit being greater than the number of screens in the in-vehicle device provided by an embodiment of the present application.

[0071] Figure 14 Schematic diagram of the hardware structure of an electronic device provided by an embodiment of the present application. Detailed implementation manners

[0072] In order to make the objectives, 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 in conjunction with the accompanying drawings of the specification and specific implementation manners.

[0073] It should also be noted that the numbering of the steps in the methods and processes in the embodiments of the present application is for the convenience of reference and does not limit the order of precedence. If there is an order of precedence between the steps, it shall be subject to the written description.

[0074] Figures 1a to 1b Schematic diagrams of application scenarios for multi-screen and multi-user login accounts in a cockpit are respectively shown.

[0075] Refer to Figure 1a , the screen of the intelligent cockpit can be configured with screen A (also known as the central control screen) for the driver and screen B (also known as the co-pilot screen) for the co-pilot.

[0076] Reference Figure 1b As shown, the screens in the intelligent cockpit can not only include Screen A and Screen B, but also include Screen C for users on the seats in the rear row area, etc. It can be understood that in some other scenarios, the number of screens configured in some vehicle cockpits may reach 4 to 10 or even more.

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

[0078] Similarly, in the above Figure 1b shown login scenario, Screen A, Screen B, and Screen C can be different screens of the same in-vehicle device, or can be screens of different in-vehicle devices, which is not limited here.

[0079] In the above Figure 1a or Figure 1b In multi-screen and multi-user scenarios such as the above examples, as mentioned before, when multiple users want to log in to their personal accounts on screens such as Screen A and Screen B respectively, they often need to enter their account numbers and passwords on screens such as Screen A and Screen B for verification and login, or the user needs to scan the device QR codes displayed on screens such as Screen A and Screen B and then perform an authorization operation to log in to their personal accounts. The operation of the user logging in to their personal account on screens such as Screen A and Screen B is rather cumbersome, and quick login cannot be achieved, resulting in a poor user experience, which causes the user to be reluctant to perform the login operation, thus leading to the idle and waste of the screen resources in the cockpit.

[0080] To solve the above problems, the present application provides an authorization method. Specifically, the method matches a handheld device suitable for the user to perform an authorization operation for each screen in the cockpit by identifying the seat position where the user is sitting in the cockpit and the relative position of the handheld device carried by the user. At this time, each screen can then prompt the user to perform authorization verification through the matched handheld device, such as verifying biometric information such as fingerprints, face information, iris information, or voiceprint, so as to support the user to quickly log in to the account on the corresponding screen. In this way, when the user enters the cockpit and needs to log in to the account on the screen in the cockpit, the user can use the handheld device matched with the corresponding screen to perform authorization verification, simplifying the operation process of the user logging in to the account on the corresponding screen and achieving the purpose of quick login. This is beneficial to improving the user experience and also beneficial to reducing the idle of the screen resources in the cockpit.

[0081] It can be understood that the above method for identifying the seat position where the user is sitting in the cockpit can be determined based on the detection results of seat sensors configured on each seat in the cockpit. The relative positions between the handheld device carried by the user, the in-vehicle device, and each screen can be determined by the results obtained through ranging and angle measurement by emitting sound waves in the form of ultrasound, etc., from the sound-emitting device of the in-vehicle device and receiving the above sound waves through the sound-pickup device of the user's handheld device. In some other embodiments, the in-vehicle device can also establish communication connections with each handheld device entering the cockpit through technologies such as ultra-wideband (UWB) wireless carrier communication technology and nearLink technology, and determine the relative positions of each handheld device relative to the in-vehicle device and each screen, which are not limited here. In this way, the in-vehicle device can determine the matching relationship between each screen in the cockpit and the user's handheld device based on the seat position where the user is sitting detected by the seat sensor and the relative position of the handheld device carried by the user.

[0082] After determining the above matching relationship, the in-vehicle device can set the identification information of the corresponding handheld device, or the identification information of communication components such as the Bluetooth chip of the handheld device, the internet protocol address (IP) address, etc. of the corresponding screen. 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 an authorization operation through the matching handheld terminal to quickly log in to the account. It can be understood that in some embodiments, after the user enters the cockpit with the handheld device, the in-vehicle device can also automatically prompt the user to authorize and log in to the account on the screen corresponding to the seat based on the seat position where the user is sitting, which is not limited here.

[0083] Reference Figure 2a , after entering the cockpit, the user can click on the control for indicating logging in to the account on the screen corresponding to the current seat. After the in-vehicle device 200 detects the above operation 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. Among them, 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 and the in-vehicle device 200 establish a Bluetooth connection after the user enters the cockpit with the mobile phone 100. The above authorization verification request can also be sent based on the transmission channel established corresponding to the Bluetooth connection. Among them, the above detection process can include detecting the relative position relationship in space of the mobile phone 100 relative to the screen operated by the user based on ultrasound, which will be introduced in detail below and will not be elaborated here.

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

[0085] In addition, when there are many users in the cockpit, the in-vehicle device 200 may also display a list of devices for selection to the users through the corresponding screen. The list of devices may list the device identification information of multiple handheld devices available for the users to quickly perform authorization operations in the current cockpit, such as device names or device models, etc. For example, refer to Figure 2a , for the convenience of user login, a selection control 212 may also be displayed on the prompt interface 210. The selection control 212 may display prompt content such as "Select a specified device for authorized login". When the user clicks the selection control 212, the screen may display the above list of devices, and the user may select a handheld device for verifying biometric information, etc. by themselves to perform the authorization operation.

[0086] For another example, refer to Figure 2b , a prompt interface 230 may also be displayed on the corresponding screen of the in-vehicle device 200. A prompt message 231 may be displayed on the prompt interface 230. The prompt message 231 may display, for example, content such as "Multiple authorizable devices are found. Please select an authorized device". In some embodiments, Figure 2b a selection control 232 may also be displayed on the prompt interface 230 as shown. At this time, the user may click the above prompt message 231 or click the selection control 232 to make the corresponding screen of the in-vehicle device 200 display the above list of devices. Furthermore, the user may select a convenient handheld device for operation in the list of devices by themselves to perform the authorization operation and achieve a quick login to the personal account.

[0087] It can be understood that the authorization method provided in this application can be applicable to an electronic device located in the cockpit of a vehicle, such as a vehicle-mounted device, etc. It can have one or more screens, and each screen can support independent account logins. Among them, the above-mentioned vehicle can include, but is not limited to, land vehicles (such as vehicles), water vehicles (such as ships), and air vehicles (such as airplanes). The above-mentioned vehicle can be a vehicle in a broad sense. For example, it can be a means of transportation (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 lawn mowers, harvesters, etc.), amusement equipment, toy vehicles, etc., which are not limited here.

[0088] The handheld devices applicable to the authorization method provided in this application can include, but are not limited to, mobile phones, tablets, desktop computers, laptops, handheld computers, netbooks, and wearable devices such as augmented reality (AR) / virtual reality (VR) devices, smart TVs, smart watches, vehicle-mounted devices, portable game consoles, portable music players, reader devices, and other electronic devices with one or more processors and communication functions.

[0089] It can be understood that in the embodiments of this 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, providing the ability for the user of the handheld terminal to conveniently log in to the account and unlock the device. In the solution of this application, an electronic device such as a vehicle-mounted device without a biometric recognition function can call the above-mentioned handheld device with a biometric recognition function, such as a mobile phone, a tablet, etc., for the user to quickly verify identity information and complete the authorization operation. In addition, based on the authorization method provided in this application, after biometric recognition and authorization are passed using the handheld device, the vehicle-mounted device will not retain the user's biometric information, account password information, etc., which is also beneficial to avoiding the problem of privacy information leakage after the user takes the vehicle.

[0090] Figure 3 According to the embodiments of this application, a schematic diagram of the system software structure of an electronic device is shown.

[0091] It can be understood that the electronic device installed with Figure 3 the system 300 shown can include the above-mentioned vehicle-mounted device 200 or other electronic devices configured in the cockpit of a vehicle, and can also include the above-mentioned handheld devices such as the mobile phone 100, which are not limited here.

[0092] As Figure 3 shown, the system 300 can adopt a distributed system or AndroidTM Systems, etc., are not limited here. The above distributed system can adopt a layered architecture, which can include an application layer, an application framework layer, a system service layer, and a kernel layer.

[0093] Among them, the application layer can include a series of application program packages. The application program packages can, for example, include application programs such as an account system client, a launcher, music, and settings, etc., which are not limited here. The above account system client can call the distributed framework provided by the system 300 to provide a multi-account management function that supports independent account login on multiple screens. In some other embodiments, this management function can also be described as a multi-user management function, which is not limited here.

[0094] The application framework layer can provide a distributed framework for the application layer. Among them, the distributed framework can include an account management framework that supports independent login of multiple accounts or multiple users. This framework can provide a function framework for realizing the interconnection (including startup, call, migration) between the various layer structures within the system 300 and between the system 300, and includes application programming interfaces (APIs) corresponding to each framework.

[0095] The system service layer is the core of the distributed operating system. The system service layer provides system services to the application programs and software development kits (SDKs), etc., in the application layer through the application framework layer. In the embodiments of the present application, the system service layer can include a mobile sensing development platform (MSDP) subsystem and a distributed soft bus, etc. Among them, the MSDP subsystem can provide core capabilities such as distributed fusion sensing capabilities and distributed device virtualization capabilities for the above account system client or through the above distributed framework.

[0096] Among them, the distributed fusion sensing capability can aggregate and fuse the sensor data collected by the seat sensors installed on each seat in the cockpit, the Bluetooth ranging data, and the position of the handheld device in the corresponding area in the cockpit determined based on acoustic wave detection such as ultrasonic waves, etc., to more accurately determine the spatial position relationship of the handheld device used by the user relative to the in-vehicle device, which can also be referred to as the relative position relationship in the present application.

[0097] Among them, the spatial position relationship between the handheld device used by the user and the in-vehicle device may include the spatial position relationship between the handheld device and multiple screens controlled by the in-vehicle device. This spatial position relationship can be determined based on the association relationships between the screens and the driver's area, the co-driver's area, and the area where the rear seats are located in the vehicle cockpit, etc. When the in-vehicle device detects that the user's handheld device is placed at a certain position within the above-mentioned area, the spatial position relationship between the handheld device and the screen associated with the area can be determined.

[0098] 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, etc. Among them, for the understanding of the distributed soft bus function, the computer hardware bus can be referred to. The distributed soft bus can have characteristics such as automatic discovery, plug-and-play, self-organizing network (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 instant interconnection can be achieved with any device in the same local area network or connected to it via Bluetooth. In addition, the distributed soft bus can also share relevant data of the logged-in account, the authorization result information confirmed after the user completes biometric information verification, etc. between networks such as Bluetooth and wireless-fidelity (Wi-Fi). In addition, in the embodiments of the present application, a communication connection can also be established between the in-vehicle device, etc. and the handheld device based on the distributed soft bus technology or the Bluetooth technology, etc., and the relative positions of the handheld devices with respect to the screens of the in-vehicle device can be determined through ultrasonic detection technology, and finally the matching relationship between each screen and the corresponding handheld device can be accurately determined. This matching relationship can be comprehensively determined, for example, according to the association relationship between each screen and the area where each seat is located, and the result of the area where the handheld device is located determined based on ultrasonic detection technology. In other embodiments, the method for detecting the relative positions of the handheld devices with respect to the screens of the in-vehicle device can also adopt methods such as array signal processing technology based on wireless signals, which is not limited here.

[0099] The kernel layer is the layer between hardware and software. The kernel layer of the distributed operating system includes: a kernel subsystem and a driver subsystem. Among them, the kernel subsystem is between. The distributed operating system can adopt a multi-kernel design, so the kernel subsystem supports selecting a suitable OS kernel for different resource-constrained devices.

[0100] The kernel abstract layer (KAL) on the kernel subsystem provides basic kernel capabilities for the upper layer by shielding the multi-kernel differences, including process / thread management, memory management, file system, network management, and peripheral management, etc.

[0101] The driver framework provided by the driver subsystem is the basis for the opening 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, audio drivers, etc., for driving the corresponding devices to work and providing corresponding hardware capabilities. In the embodiments of the present application, the driver subsystem may also include a driver for interacting with a seat sensor or other sensors, which is not limited herein.

[0102] The following will be based on the above Figure 3 shown system architecture, and the specific implementation process of the authorization method provided by the present application will be introduced in detail in combination with the application scenarios provided by different embodiments.

[0103] First, the specific implementation process of the authorization method provided by the present application will be introduced in combination with the application scenario where a user enters the cockpit with a handheld device provided in Embodiment 1.

[0104] Embodiment 1

[0105] Figure 4 According to the embodiments of the present application, a schematic diagram of the login scenario corresponding to a user entering the cockpit with a handheld device is shown.

[0106] Taking a vehicle cockpit as an example, as Figure 4 shown, in this scenario, the in-vehicle device 200 in the cockpit may have multiple screens, including Screen A, Screen B, Screen C, Screen D, etc., which can be respectively described as Screen 200A, Screen 200B, Screen 200C, Screen 200D for clarity below.

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

[0108] At this time, the in-vehicle device 200 can discover the mobile phone 100 through Bluetooth and establish a Bluetooth connection or a distributed connection with the mobile phone 100. In this way, the mobile phone 100 and the in-vehicle device 200 can synchronize device information and send request data, etc. based on the data transmission channel provided by the above Bluetooth connection. Among them, the in-vehicle device 200 can establish a Bluetooth connection with the mobile phone 100 based on the relevant record information of the Bluetooth pairing and connection with the mobile phone 100 during the historical usage period.

[0109] In the embodiment of the present application, the in-vehicle device 200 can determine that each screen in the cockpit can be authorized to log in to the user account through the mobile phone 100 according to the seat position where the user is sitting and the relative position of the mobile phone 100 in the cockpit relative to each screen of the in-vehicle device 200, etc. It can be understood that the account authorized by the user to log in can be managed through the account cloud, and the account cloud can run on the server. The mobile phone 100, the in-vehicle device 200, and other electronic devices used by the user can log in to the same account, and a distributed connection can be established between the electronic devices logging in to the same user account based on the above-mentioned distributed soft bus or other communication methods, which will not be limited or elaborated here.

[0110] Based on the above Figure 4 scenario shown, Figure 5a According to the embodiment of the present application, a schematic diagram of the implementation process of an authorization method is shown.

[0111] Referring to Figure 5a , the implementation process may involve the interaction between the mobile phone 100, the in-vehicle device 200, and the account cloud 300 that manages the user account.

[0112] Specifically, as Figure 5a shown, the process may include the following steps:

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

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

[0115] When the user enters the vehicle cockpit with the mobile phone 100, the in-vehicle device 200 can discover the mobile phone 100 via Bluetooth. If a Bluetooth connection has been established between the mobile phone 100 and the in-vehicle device 200, they can directly establish a Bluetooth connection without the need for re-Bluetooth pairing. If a Bluetooth connection has not been established between the mobile phone 100 and the in-vehicle device 200, the user can complete the pairing and establish a Bluetooth connection according to the relevant operation prompts provided by the mobile phone 100 or the in-vehicle device 200. It can be understood that the above-mentioned manner of the mobile phone 100 or the in-vehicle device 200 providing relevant operation prompts can be through screen display or through voice and other means for prompting, which is not limited herein.

[0116] 502: The in-vehicle device 200 sends a detection signal for measuring orientation to the mobile phone 100.

[0117] Exemplarily, the above-mentioned detection signal for measuring orientation can be a high-frequency signal such as ultrasonic wave, or other carrier signals that cannot be perceived by the user, which is not limited herein.

[0118] As an example, refer to Figure 5b As shown, after the in-vehicle device 200 establishes a connection with the mobile phone 100, it can emit ultrasonic waves through a speaker array deployed inside the cockpit. The speaker array can include, but is not limited to, Figure 5b the speakers in the layout areas indicated by speaker A, speaker B, speaker C, and speaker D as shown. The above ultrasonic waves can be received by a sound pickup device configured on the mobile phone 100, such as a microphone, and the mobile phone 100 can continue to execute the following step 503.

[0119] 503: The mobile phone 100 synchronizes the detection signal reception result to the in-vehicle device 200.

[0120] Exemplarily, the above-mentioned detection signal reception result can include the time information recorded when the microphone of the mobile phone 100 receives ultrasonic waves, or it can be the area of the seat in the vehicle cockpit where the mobile phone 100 is located determined by the mobile phone 100 based on the ultrasonic wave signal reception result. Furthermore, the in-vehicle device 200 can determine the relative position relationship between each screen and the mobile phone 100.

[0121] 504: The in-vehicle device 200 acquires sensor data.

[0122] Exemplarily, the above-mentioned sensor data can be the data collected by seat sensors configured on each seat in the cockpit. In some embodiments, the data collected by the seat sensors is used to indicate whether a user is sitting on the seat, or to determine whether there is a user in the area sensed by the seat sensor. The seat sensor can be a seat sensor in the driver's area, the passenger's area, or the rear row area, which is not limited herein.

[0123] It can be understood that the above-mentioned seat sensor can be a pressure sensor arranged under the corresponding seat, or a sensor capable of detecting the wearing state of the seat belt, which is not limited here. For example, within a certain period of time, the processor or computing unit of the in-vehicle device 200 can determine whether the user is sitting on the seat in the driver's area based on the change in the pressure value detected by the pressure sensor under the driver's seat area.

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

[0125] Exemplarily, 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, the in-vehicle device 200 can determine the relative position relationships between the screens 200A, 200B, 200C, and 200D and the mobile phone 100 respectively.

[0126] For example, according to the relative position detection result obtained by the ultrasonic detection technology, it can be determined that the mobile phone 100 is located in the driver's seat area associated with the screen 200A, and then the relative position relationships between the mobile phone 100 and the screens 200A, 200B, 200C, and 200D can be determined. Among them, the relative position relationship between the mobile phone 100 and the screen 200A can meet a preset condition, and this preset condition is, for example, the matching relationship between the screen 200A and one or more handheld devices placed in the driver's area. It can be understood that the relative distances between the mobile phone 100 and the screens 200A and 200C can also be the same, but since the screen associated with the driver's area is the screen 200A, it can be determined that the mobile phone 100 matches the screen 200A. This is not limited here.

[0127] In some other embodiments, in order to improve the recommendation accuracy, when the relative distances between the mobile phone 100 and multiple screens of the in-vehicle device 200 are the same or similar, the in-vehicle device 200 can also determine the handheld device with the smallest relative distance from each screen and corresponding to the seat position where the user is sitting based on the seat position determined by comprehensively collecting the data of the above-mentioned seat sensor. Additionally, the above method for detecting the relative position between the handheld device and each screen of the in-vehicle device can also adopt methods such as array signal processing technology based on wireless signals, which is not limited here.

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

[0129] Exemplarily, when the user needs to log in to an account on the in-vehicle device 200, the user can perform a login operation on a nearby screen. For example, refer to Figure 4In the login scenario shown, the user sitting in the driver's area can click on the relevant control for logging in to the account on screen 200A. Correspondingly, the in-vehicle device 200 can detect the user's login operation through this screen 200A.

[0130] In some other embodiments, the screen for the user to perform the login operation in the cockpit can also be screen 200B, screen 200C, screen 200D, etc. Correspondingly, the in-vehicle device 200 can detect the user's login operation on screen 200B, screen 200C, or screen 200D, which is not limited herein.

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

[0132] Exemplarily, when the in-vehicle device 200 detects the user's login operation through screen 200A, it can use the mobile phone 100 corresponding to this screen 200A as the target device recommended for the user to use. This target device can provide biometric recognition capabilities, etc., for the user to quickly perform the authorization operation.

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

[0134] In some other embodiments, if the handheld devices carried by the user can include multiple ones, such as including a mobile phone, a watch, and a tablet computer, etc., or multiple users each bring at least one handheld device into the cockpit, etc., then the in-vehicle device 200 can comprehensively determine the target device corresponding to the screen where the user is currently operating based on the relative position relationship between each of the determined screens and each handheld device. This will be specifically described in the relevant embodiments below and will not be elaborated herein.

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

[0136] Exemplarily, after the in-vehicle device 200 determines the target device (such as the mobile phone 100) for the user to perform the authorization operation, it can send an authorization login request to this target device. This authorization login request can instruct the target device to display an authorization interface and can instruct the target device to prompt the user with other information for the authorization operation (such as voice information, etc.), which is not limited herein.

[0137] 509: The in-vehicle device 200 displays a first prompt interface.

[0138] Exemplarily, before, simultaneously with, or after the vehicle-mounted device 200 executes the above step 508, it may display a relevant interface for reminding the user to perform an authorization operation on the target device. For the convenience of description, the reminder interface will be referred to as the first reminder interface hereinafter. In some embodiments, the content of the first reminder interface may refer to the content displayed by the reminder interface 210 shown above Figure 2a and the specific content may refer to the above Figure 2a shown and related descriptions, which will not be elaborated here.

[0139] In other embodiments, the vehicle-mounted device 200 may also remind the user of relevant information for performing an authorization operation on the target device by means of voice prompts, etc., or the vehicle-mounted device 200 may not execute this step 509 to display the above first reminder interface, which is not limited here.

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

[0141] Exemplarily, the mobile phone 100 may prompt the user to perform an authorization operation by displaying an authorization interface. The authorization interface may have areas for prompting the user to input biometric information such as fingerprint information or face information. As an example, the mobile phone 100 may display the Figure 2a shown authorization verification interface 220, and areas for prompting the input of fingerprint information and areas for prompting the input of face information may be displayed on this interface 220.

[0142] In other embodiments, the mobile phone 100 may also prompt the user to perform an authorization operation by playing voice prompts, etc., which is not limited here.

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

[0144] Exemplarily, the above verification information input by the user may include fingerprint information, face information, iris information, voiceprint information, etc. provided by the user, and may also include account, password, and / or verification code information input by the user through an input method soft keyboard, etc., which is not limited here.

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

[0146] Exemplarily, the mobile phone 100 may verify whether the verification information such as fingerprint information, face information, iris information, and voiceprint information input by the user during the authorization operation on relevant interfaces such as the authorization verification interface matches the corresponding pre-collected biometric information, and send the verification result corresponding to whether it matches to the account cloud 300. This verification result can be used for the authorization verification request to request the account cloud 300 to verify whether the verification information input by the user through the mobile phone 100 matches the biometric information recorded corresponding to the relevant account.

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

[0148] It can be understood that the account cloud 300 can store and manage account-related information such as the accounts and passwords registered by each user. Therefore, the account cloud 300 can generate corresponding authorization result information according to the verification result sent by the mobile phone 100. Corresponding to the matching verification result, the account cloud 300 can generate authorization result information indicating successful authorization and send it to the in-vehicle device 200; corresponding to the non-matching verification result, the account cloud 300 can return authorization result information indicating failed authorization to the in-vehicle device 200.

[0149] 514: The in-vehicle device 200 completes logging in to the account.

[0150] Exemplarily, based on the authorization result information indicating successful authorization sent by the account cloud 300, the in-vehicle device 200 can complete the process of logging in to the account. It can be understood that based on the authorization result information indicating failed authorization sent by the account cloud 300, the in-vehicle device 200 can also inform the user of the failure result through means such as the interface or voice.

[0151] It can be understood that based on the interaction process corresponding to the above steps 501 to 514, for the login scenario where a user enters the cockpit with a handheld device, the in-vehicle device 200 can implement cross-device invocation of the biometric information recognition ability of the handheld device, instruct the user to perform authorization verification, and then quickly complete the process of logging in to the account on the in-vehicle device 200. Obviously, this process can simplify the operation process of the user entering information such as the account and password on the relevant screen of the in-vehicle device 200, or scanning the QR code displayed on the relevant screen of the in-vehicle device 200 and then verifying the biometric information, which is beneficial to improving the user experience and further beneficial to reducing the idle of the screen resources in the cockpit.

[0152] The following introduces the specific implementation process of the authorization method provided by this application in combination with the application scenario where a user enters the cockpit with multiple handheld devices provided in Embodiment 2.

[0153] Embodiment 2

[0154] Figure 6 According to the embodiment of the present application, a schematic diagram of the login scenario corresponding to a user entering the cockpit with multiple handheld devices is shown.

[0155] Taking the vehicle cockpit as an example, as Figure 6 shown, in this scenario, the in-vehicle device 200 in the cockpit can have multiple screens, including Screen A, Screen B, Screen C, Screen D, etc., which can be respectively described as Screen 200A, Screen 200B, Screen 200C, Screen 200D for clarity below.

[0156] In the embodiment of the present application, the number of users entering the cockpit can be 1, but the number of handheld devices carried by this user can be multiple. For example, Figure 6 as shown, for example, this user can carry a mobile phone 100, a watch 400, a tablet computer 500, etc. into the cockpit. In other embodiments, the multiple handheld devices carried by the above user can also be other devices, and the number of handheld devices carried by the user can also be 2, 4, or other numbers, which are not limited herein.

[0157] Based on the above Figure 6 shown scenario, Figure 7 According to the embodiment of the present application, a schematic diagram of the implementation process of an authorization method is shown.

[0158] Referring to Figure 7 , this implementation process may involve the interaction between the vehicle-mounted device 200 and the mobile phone 100, the watch 400, and the tablet computer 500. Among them, the process of interaction between the vehicle-mounted device 200, the mobile phone 100, the watch 400, and the tablet computer 500 and the account cloud 300 is not shown, and the specific interaction can refer to the description in the relevant steps, which will not be elaborated herein.

[0159] As Figure 7 shown, this process may include the following steps:

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

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

[0162] 703: The mobile phone 100, the watch 400, and the tablet computer 500 synchronize the detection signal reception results to the vehicle-mounted device 200.

[0163] 704: The vehicle-mounted device 200 acquires sensor data.

[0164] It can be understood that the execution process of the above 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 difference between the above steps 701 to 704 in the embodiment of the present application is that the interaction subjects involve the vehicle-mounted device 200 and multiple handheld devices carried by the same user.

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

[0166] Exemplarily, when a user carries multiple handheld devices, the placement positions of the handheld devices may vary, correspondingly resulting in different time data, etc., of the ultrasonic and other detection signals received by the handheld devices from the vehicle-mounted device 200. For the vehicle-mounted device 200 operated by the user or the relevant screen of the vehicle-mounted device 200, the handheld device suitable for being recommended to the user for authorization operation (i.e., matching) can be determined according to the relative positions between the handheld devices and the vehicle-mounted device 200 or the corresponding screen of the vehicle-mounted device 200.

[0167] As an example, referring to the Figure 6 login scenario shown above, for example, the mobile phone 100 carried by the user is the closest to the screen 200A, and the tablet computer 500 may be the closest to the screen 200B due to being placed on the seat in the co-pilot area. At this time, the vehicle-mounted device 200 can set the matching relationship between the screen 200A and the mobile phone 100, and set the matching relationship between the screen 200B and the tablet computer 500. In some other embodiments, the matching relationship between the above-mentioned handheld devices and each screen may also include other relationships. For example, a matching relationship is formed between the screen 200A and the watch 400 worn by the user, and a matching relationship is formed between the screen 200B and the mobile phone 100 and the tablet computer 500 placed on the seat in the co-pilot area, etc. There is no limitation here. The above distance can be determined according to the position of the mobile phone 100 placed in the vehicle cockpit determined by the ultrasonic detection result. The position where the mobile phone 100 is placed in the driver's area or the co-pilot area, as well as the accurate position of the mobile phone 100 in the corresponding area, can be measured based on the ultrasonic detection technology or the array signal processing technology based on wireless signals. The specific detection process can refer to the relevant implementation solutions of the ultrasonic detection technology, which will not be elaborated here.

[0168] It can be understood that the matching relationship between each screen of the vehicle-mounted device 200 and each handheld device can be a many-to-one, one-to-one, or one-to-many corresponding matching relationship, and there is no limitation here.

[0169] 706: The vehicle-mounted device 200 detects a login operation of the user on the screen 200A.

[0170] Exemplarily, referring to the Figure 6 scenario shown above, if the user is sitting on the seat in the driver's area, the user can click on the control for triggering the login account on the screen 200A, that is, perform a login operation.

[0171] In some other embodiments, the user can also perform a login operation on other screens in the cockpit, such as performing a login operation on the screen 200B, or the screen 200C, the screen 200D, etc. There is no limitation here.

[0172] 707: The vehicle-mounted device 200 determines the mobile phone 100 matching the screen 200A as the target device.

[0173] Exemplarily, when the vehicle-mounted device 200 executes the above steps 702 to 705, it can comprehensively detect that the handheld device corresponding to the screen 200A is the mobile phone 100 based on an ultrasonic device array (such as a speaker array), a seat sensor, etc. Correspondingly, when the vehicle-mounted device 200 detects the user's login operation in the above step 706, it can determine the mobile phone 100 as the target device matching the screen 200A.

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

[0175] Exemplarily, among the multiple handheld devices connected to the vehicle-mounted device 200, the matching priority of the mobile phone 100 with the vehicle-mounted device 200 can be higher than that of the smartwatch 400 with the vehicle-mounted device 200, and the matching priority of the smartwatch 400 with the vehicle-mounted device 200 can be higher than that of the tablet computer 500 with the vehicle-mounted device 200. In some embodiments, the vehicle-mounted device 200 can send an authorization login request to the preferentially matched mobile phone 100 and execute the following step 709, etc., to prompt the user to perform an authorization operation on the mobile phone 100. In other embodiments, the vehicle-mounted device 200 can also send authorization login requests to each handheld device in turn according to the priority order corresponding to each of the above handheld devices; or, the vehicle-mounted device 200 can send an authorization login request to the smartwatch 400 after the preferentially requested mobile phone 100 has been unresponsive for a long time, etc., which is not limited here.

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

[0177] Exemplarily, the vehicle-mounted device 200 can send an authorization login request to the mobile phone 100 that matches the screen 200A and can remind the user to perform an authorization login through the mobile phone 100. This reminder interface can be denoted as the second prompt interface for differential description from the first prompt interface displayed in step 509 in the above embodiment 1.

[0178] It can be understood that in some embodiments, the content of this second prompt interface can refer to Figure 8a the prompt interface 810 shown. The display content of this prompt interface 810 can be the same as that of the Figure 2a prompt interface 210 shown above. That is, the content displayed on the above second prompt interface can be the same as the content displayed on the first prompt interface in the above embodiment 1.

[0179] Referring to Figure 8a shown, the prompt interface 810 can display a prompt message 811, and this prompt message 811 can include content such as "Please complete the login authorization on the mobile phone side", etc. Continuing to refer to Figure 8a, To facilitate user login, a selection control 812 may also be displayed on the prompt interface 810. For example, prompt content such as "Select a specified device for authorized login" may be displayed on the selection control 812. When the user clicks on the selection control 812 on the prompt interface 810, the corresponding screen of the in-vehicle device 200 may display a list of devices including each currently connected handheld device. Specifically, reference may be continued to the relevant descriptions in steps 711 to 712 below, which will not be elaborated here.

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

[0181] Exemplarily, in response to the authorization login request sent by the in-vehicle device 200, the mobile phone 100 may display a corresponding authorization login interface or prompt the user to perform an authorization operation by voice or other means. The specific prompting process may refer to the relevant description in step 510 of the above-mentioned embodiment 1, which will not be elaborated here.

[0182] 711: The in-vehicle device 200 detects the user's operation of selecting an authorized device on the second prompt interface.

[0183] Exemplarily, if the user is not convenient to perform an authorization operation through the mobile phone 100 matched with the in-vehicle device 200 at this time, the user may choose to perform an authorization operation through other handheld terminals. For example, the user may choose a smartwatch 400, etc.

[0184] As an example, referring to Figure 8a As shown, when the user clicks on the selection control 812 on the prompt interface 810, the in-vehicle device 200 may detect the user's operation of selecting an authorized device on the second prompt interface. At this time, the in-vehicle device 200 may continue to execute the following step 712 to display a list of devices including multiple handheld devices.

[0185] In some other embodiments, before executing the above step 708 to send an authorization login request, the in-vehicle device 200 may also not execute the above steps 708 to 710, but display Figure 8b the prompt interface 830 as shown. Referring to Figure 8b As shown, the prompt interface 830 may display prompt information 831 such as "Multiple authorizable devices are found. Please select an authorized device". In some embodiments, a selection control 832 may also be displayed in the prompt interface 830. The user may click on the prompt information 831 or click on the selection control 832 on the Figure 8b prompt interface 830 as shown, causing the in-vehicle device 200 to execute the following step 712 to display a device list.

[0186] 712: The in-vehicle device 200 displays a device list.

[0187] As an example, the interface of the in-vehicle device 200 for displaying the device list may refer toFigure 8a The device list interface 820 shown. On this interface 820, identification information such as the names or models of multiple handheld devices such as the currently connected mobile phone 100, smartwatch 400, and tablet computer 500 can be displayed.

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

[0189] 713: The in-vehicle device 200 determines that the selected smartwatch 400 by the user is the target device.

[0190] Exemplarily, continuing to refer to the above Figure 8a shown, the user can click on the login control 821 corresponding to "Smartwatch 400" on the device list interface 820 displayed on the screen 200A to set the smartwatch 400 as the authorized device for authorization operations. In some embodiments, Figure 8a in the device list interface 820 shown, prompt information such as "Click Me to Log In" can be displayed on the login controls corresponding to each device. Referring to Figure 8a the content displayed on the shown login control 821, which is not limited herein. Correspondingly, the in-vehicle device 200 can use the selected smartwatch 400 by the user as the target device and continue to execute the following step 714 to send an authorization login request.

[0191] It can be understood that in the device list displayed by the in-vehicle device 200, the display priorities corresponding to different handheld devices carried by the user can be different, and this priority can be preset or accept user settings, etc. For example, for the above mobile phone, smartwatch, and tablet computer, the priority order displayed by the in-vehicle device 200 can be mobile phone > smartwatch > tablet computer.

[0192] It can be understood that the user can also click on the login controls corresponding to other devices on the device list interface 820 such as Figure 8a shown, for example, click on the login control 822 corresponding to the tablet computer 500, etc., which is not limited herein.

[0193] 714: The in-vehicle device 200 sends an authorization login request to the smartwatch 400.

[0194] 715: The smartwatch 400 prompts the user to perform an authorization operation.

[0195] Exemplarily, when the smartwatch 400 receives the authorization login request sent by the in-vehicle device 200, it can respond to this request and prompt the user to perform an authorization operation by displaying an authorization interface or through voice, etc. The specific prompting process can refer to the relevant description in step 510 in the above embodiments, which will not be elaborated herein.

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

[0197] 717: The watch 400 sends the verification result to the account cloud.

[0198] Specifically, for the process of the watch 400 executing the above steps 716 to 717, reference can be made to the relevant descriptions of the mobile phone 100 executing steps 511 to 512 in the above-mentioned Embodiment 1, which will not be elaborated here.

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

[0200] 719: The in-vehicle device 200 completes logging in to the account.

[0201] Specifically, for the process of the in-vehicle device 200 executing the above steps 718 to 719, reference can be made to the relevant descriptions of the account cloud 300 executing step 513 and the in-vehicle device 200 executing step 514 in the above-mentioned Embodiment 1, which will not be elaborated here.

[0202] It can be understood that based on the interaction process corresponding to the above steps 701 to 719, for the login scenario where a user brings multiple handheld devices into the cockpit, the in-vehicle device 200 can recommend a matching target device for the screen that needs to log in to the user account based on the detection results of ultrasonic detection technology and seat sensors, etc., providing a convenient way for the user to log in to the account. Also, the in-vehicle device 200 can receive the operation of the user selecting a specified device as the authorized device, meeting the actual need of the user to select a handheld device that is convenient for authorized login for the authorization operation, which is beneficial to further improving the user experience. In addition, the authorization method provided in the embodiments of the present application can obviously remedy the situation of mis-recommending handheld devices by the in-vehicle device 200 based on the detection results of ultrasonic detection technology, seat sensors, etc., providing more optional configurations for the user and facilitating the user to quickly log in to the account in the cockpit.

[0203] The following introduces the specific implementation process of the authorization method provided in the present application in combination with the application scenario where multiple users each bring a handheld device into the cockpit in Embodiment 3.

[0204] Embodiment 3

[0205] Figures 9a to 9f According to the embodiments of the present application, a schematic diagram of the login scenario corresponding to multiple users each bringing one or more handheld devices into the cockpit is shown.

[0206] Taking the vehicle cockpit as an example, as Figure 9aAs shown, the in-vehicle device 200 in the cockpit of this scenario may have multiple screens, including Screen A, Screen B, Screen C, Screen D, etc. For the sake of clarity, they can be separately described as Screen 200A, Screen 200B, Screen 200C, and Screen 200D below.

[0207] In the embodiments of the present application, the number of users entering the cockpit 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 Figure 9a shown, for example, the user can carry a mobile phone 100, a watch 400, a tablet computer 500, etc. into the cockpit. In other embodiments, the multiple handheld devices carried by the above users can also be other devices, and the number of handheld devices carried by the user can also be 2, 4, or other numbers, which are not limited herein.

[0208] As an example, referring to Figure 9a , User A can carry a mobile phone 100A into the cockpit and sit on the seat in the driver's area. User B can carry a mobile phone 100B into the cockpit and sit on the seat in the co-driver's area. After the in-vehicle device 200 establishes a device connection with the mobile phone 100A and the mobile phone 100B, based on the detection results of the ultrasonic detection technology and the detection results of the seat sensor, the matching relationship between Screen 200A and the mobile phone 100A, and between Screen 200B and the mobile phone 100B can be determined.

[0209] Referring to Figure 9b , User A can carry a mobile phone 100A into the cockpit and sit on the seat in the driver's area. User C can carry a mobile phone 100C into the cockpit and sit on the seat on the left side of the rear row area. After the in-vehicle device 200 establishes a device connection with the mobile phone 100A and the mobile phone 100C, based on the detection results of the ultrasonic detection technology and the detection results of the seat sensor, the matching relationship between Screen 200A and the mobile phone 100A, and between Screen 200C and the mobile phone 100C can be determined.

[0210] Referring to Figure 9c , User A can carry a mobile phone 100A into the cockpit and sit on the seat in the driver's area. User C can carry a mobile phone 100C into the cockpit and sit on the seat on the left side of the rear row area. User D can carry a mobile phone 100D into the cockpit and sit on the seat on the right side of the rear row area. After the in-vehicle device 200 establishes a device connection with the mobile phone 100A, the mobile phone 100C, and the mobile phone 100D, based on the detection results of the ultrasonic detection technology and the detection results of the seat sensor, the matching relationship between Screen 200A and the mobile phone 100A, between Screen 200C and the mobile phone 100C, and between Screen 200D and the mobile phone 100D can be determined.

[0211] Referring to Figure 9dAs shown, user A can carry mobile phone 100A into the cockpit and sit on the seat in the driver's area. User B can carry mobile phone 100B into the cockpit and sit on the seat in the co-driver's area. User C can carry mobile phone 100C into the cockpit and sit on the seat on the right side of the rear row area. After the in-vehicle device 200 establishes a device connection with mobile phone 100A, mobile phone 100B, and mobile phone 100C, based on the detection results of the ultrasonic detection technology and the detection results of the seat sensors, the matching relationships between screen 200A and mobile phone 100A, screen 200B and mobile phone 100B, and screen 200C and mobile phone 100C can be determined.

[0212] Reference Figure 9e As shown, user A can carry mobile phone 100A into the cockpit and sit on the seat in the driver's area. User B can carry mobile phone 100B into the cockpit and sit on the seat in the co-driver's area. User C can carry mobile phone 100C into the cockpit and sit on the seat on the left side of the rear row area. User D can carry mobile phone 100D into the cockpit and sit on the seat on the right side of the rear row area. After the in-vehicle device 200 establishes a device connection with mobile phone 100A, mobile phone 100B, mobile phone 100C, and mobile phone 100D, based on the detection results of the ultrasonic detection technology and the detection results of the seat sensors, 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 can be determined.

[0213] Reference Figure 9f As shown, user A can carry mobile phone 100A into the cockpit and sit on the seat in the driver's area. User C can carry mobile phone 100C into the cockpit and sit on the seat on the left side of the rear row area. User D can carry mobile phone 100D into the cockpit and sit on the seat in the middle of the rear row area. After the in-vehicle device 200 establishes a device connection with mobile phone 100A, mobile phone 100C, and mobile phone 100D, based on the detection results of the ultrasonic detection technology and the detection results of the seat sensors, the matching relationships between screen 200A and mobile phone 100A, screen 200C and mobile phone 100C, and screen 200D and mobile phone 100D can be determined, and the matching relationships between screen 200A and mobile phone 100A, screen 200C and mobile phone 100C, and mobile phone 100D can also be determined.

[0214] It can be understood that in the application scenario of the embodiments of the present application, when there are many users entering the cockpit, the vehicle-mounted device 200 may not be able to distinguish the target device matching the corresponding screen from the handheld devices of each user. At this time, the vehicle-mounted device 200 can obtain each handheld device carried by each user through Bluetooth connection and form a list. When the vehicle-mounted device 200 recommends the target device to the user, it can recommend based on the detection results of the seat sensor and the detection results based on the ultrasonic detection technology, or can also recommend in combination with the operation of the user selecting the target device on the corresponding screen. In other embodiments, when the vehicle-mounted device 200 recommends the target device to the user, it can also comprehensively consider the detection results of the seat sensor and the detection results of the array signal processing technology based on the wireless signal, which is not limited here.

[0215] As an example, based on the above Figure 9a shown scenario, Figure 10 According to the embodiments of the present application, a schematic diagram of the implementation process of an authorization method is shown.

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

[0217] Specifically, as Figure 10 shown, the process may include the following steps:

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

[0219] Exemplarily, when user A enters the cockpit with the mobile phone 100A, the vehicle-mounted device 200 can discover the mobile phone 100A based on Bluetooth and establish a device connection with the mobile phone 100A. Similarly, when user B enters the cockpit with the mobile phone 100B, the vehicle-mounted device 200 can discover the mobile phone 100B based on Bluetooth and establish a device connection with the mobile phone 100B. After establishing the device connection, the vehicle-mounted device 200 can synchronize device information with the mobile phone 100A or the mobile phone 100B. The specific implementation process can refer to the relevant description of step 501 in the above embodiment 1, which will not be elaborated here.

[0220] It can be understood that in the context of the embodiments of the present application, " / " can be used to represent the "and / or" relationship. Since user A entering the cockpit with mobile phone 100A and user B entering the cockpit with mobile phone 100B can occur successively or simultaneously, and the vehicle-mounted device 200 is within the Bluetooth signal coverage supported by the Bluetooth chip, if it can receive the Bluetooth signal of mobile phone 100A and / or mobile phone 100B, a device connection can be established between the vehicle-mounted device 200 and mobile phone 100A and / or mobile phone 100B, which is not limited herein.

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

[0222] Exemplarily, the vehicle-mounted device 200 can send detection signals such as ultrasonic waves to the connected mobile phone 100A / mobile phone 100B. Then, when receiving the detection signal reception result feedback from the mobile phone 100A / mobile phone 100B in the following steps 1003a / 1003b, the relative position of the mobile phone 100A / mobile phone 100B can be determined, that is, the relative position of the mobile phone 100A / mobile phone 100B with respect to the vehicle-mounted device 200.

[0223] For the specific implementation process of the vehicle-mounted device 200 sending detection signals such as ultrasonic waves, reference can be made to the relevant description of step 502 in the above-mentioned embodiment 1, which will not be elaborated herein.

[0224] 1003a / 1003b: The mobile phone 100A / mobile phone 100B synchronizes the detection signal reception result to the vehicle-mounted device 200.

[0225] In the embodiments of the present application, based on the relative position determined by the measurement results of the above steps 1002a to step 1003a and / or steps 1002a to step 1003b, it can also be the relative position of the mobile phone 100A / mobile phone 100B with respect to the screen 200A / screen 200B of the vehicle-mounted device 200. The vehicle-mounted device 200 can measure and calculate and determine it according to the requirements of subsequent relevant steps through detection signals such as ultrasonic waves, which is not limited herein.

[0226] For the specific synchronization process, reference can be made to the relevant description of step 503 in the above-mentioned embodiment 1, which will not be elaborated herein.

[0227] 1004: The vehicle-mounted device 200 obtains sensor data.

[0228] Exemplarily, if user A enters the cockpit and sits on the seat in the driver's area, the vehicle-mounted device 200 can obtain the sensor data collected by the seat sensor in the driver's area. If user B enters the cockpit and sits on the seat in the passenger's area, the vehicle-mounted device 200 can obtain the sensor data collected by the seat sensor in the driver's area.

[0229] In some other embodiments, when the user enters the cockpit, they can also sit on the seats in other areas, such as the seats in the rear row area, etc. Correspondingly, the vehicle-mounted device 200 can obtain the sensor data collected by the corresponding seat sensors in the corresponding area, which is not limited herein.

[0230] 1005: The vehicle-mounted device 200 determines the matching relationship based on the relative positions of the screens and the handheld devices and the positions where the users are sitting.

[0231] For the specific process of the vehicle-mounted device 200 executing the above steps 1004 to 1005, reference can be made to the relevant descriptions in steps 704 to 705 in Embodiment 2 above, which will not be elaborated herein.

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

[0233] Exemplarily, when user A is sitting on the seat in the driver's area, they can click on the relevant control indicating the login account on the screen 200A, that is, perform the login operation. Correspondingly, the screen 200A of the vehicle-mounted device 200 can detect the user's login operation, and then continue to execute the following step 1007a to send an authorization login request to the mobile phone 100A.

[0234] In some other embodiments, the vehicle-mounted device 200 can also automatically trigger the login of the account and execute the following step 1007a to send an authorization login request to the mobile phone 100A when it does not detect the user's login operation on the screen 200A, which is not limited herein.

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

[0236] Exemplarily, when user B is sitting on the seat in the driver's area, they can click on the relevant control indicating the login account on the screen 200B, that is, perform the login operation. Correspondingly, the screen 200B of the vehicle-mounted device 200 can detect the user's login operation, and then continue to execute the following step 1007b to send an authorization login request to the mobile phone 100B.

[0237] In some other embodiments, the vehicle-mounted device 200 can also automatically trigger the login of the account and execute the following step 1007b to send an authorization login request to the mobile phone 100B when it does not detect the user's login operation on the screen 200B, which is not limited herein.

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

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

[0240] For the specific implementation process of sending the authorization login request, reference can be made to the relevant description in step 508 of Embodiment 1 above, and details will not be elaborated here.

[0241] In some other embodiments, if user A or user B carries multiple handheld devices, such as a mobile phone, a watch, a tablet computer, etc., the in-vehicle device 200 can send authorization login requests to different types of handheld devices respectively according to the priority order corresponding to each handheld device. For the specific implementation, reference can be made to the relevant description in step 708 of Embodiment 2 above, and details will not be elaborated here.

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

[0243] Exemplarily, the in-vehicle device 200 can display a prompt interface for prompting the user to perform an authorization operation on the mobile phone 100A through the screen 200, which is denoted as the third prompt interface.

[0244] It can be understood that the in-vehicle device 200 can execute this step 1008a to display the above-mentioned third prompt interface before, at the same time as, or after executing the above step 1007a, and there is no limitation here.

[0245] In some embodiments, the third prompt interface can refer to the Figure 8a prompt interface 810 shown in Embodiment 2 above. In some other embodiments, the above-mentioned third prompt interface can refer to the Figure 8b prompt interface 830 shown in Embodiment 2 above, and there is no limitation here.

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

[0247] Exemplarily, the in-vehicle device 200 can display a prompt interface for prompting the user to perform an authorization operation on the mobile phone 100B through the screen 200, which is denoted as the fourth prompt interface.

[0248] It can be understood that the in-vehicle device 200 can execute this step 1008b to display the above-mentioned fourth prompt interface before, at the same time as, or after executing the above step 1007b, and there is no limitation here.

[0249] In some embodiments, the fourth prompt interface may refer to the prompt interface 810 provided in the above-mentioned Embodiment 2. Figure 8a In some other embodiments, the above-mentioned fourth prompt interface may refer to the prompt interface 830 provided in the above-mentioned Embodiment 2, which is not limited herein. Figure 8b

[0250] 1009a: The screen 200A of the vehicle-mounted device 200 detects that the user selects an authorized device on the third prompt interface.

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

[0252] In some other embodiments, user A may also use the mobile phone 100 recommended by the vehicle-mounted device 200 for the authorization operation. At this time, the screen 200A of the vehicle-mounted device 200 may also not execute the relevant processes of the following steps 1009a to 1011a, but continue to execute the relevant processes of the following steps 1012a to 1014a.

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

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

[0255] In some other embodiments, user B may also use the mobile phone 100 recommended by the vehicle-mounted device 200 for the authorization operation. At this time, the screen 200B of the vehicle-mounted device 200 may also not execute the relevant processes of the following steps 1009b to 1011b, but continue to execute the relevant processes of the following steps 1012b to 1014b.

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

[0257] It can be understood that the screen 200A / screen 200B of the vehicle-mounted device 200 can display a device list including other handheld terminals already connected to the current vehicle-mounted device 200 in response to the user's operation of selecting an authorized device. The device list may refer to the corresponding one in the following text for the above Figure 9e ​An example of the device list interface of the described scenario and related descriptions will not be elaborated here.

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

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

[0260] Exemplarily, the target device selected by the above-mentioned user A / user B can be other handheld terminals selected by the user, such as a watch or a tablet computer, etc., or the mobile phone 100A / mobile phone 100B selected by the user, etc., which is not limited here.

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

[0262] For the specific prompting process, reference can be made to the relevant descriptions in step 510 of the above-mentioned embodiment, which will not be elaborated here.

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

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

[0265] For the specific processes of receiving verification information, sending authorization verification requests, etc., reference can be made to the relevant descriptions of the mobile phone 100 executing steps 511 to 512 in the above-mentioned embodiment 1, which will not be elaborated here.

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

[0267] 1016: The in-vehicle device 200 completes logging in to the account on the corresponding screen.

[0268] For the specific process of the in-vehicle device 200 executing the above steps 1015 to 1016, reference can be made to the relevant descriptions of the account cloud 300 executing step 513 and the in-vehicle device 200 executing step 512 in the above-mentioned embodiment 1, which will not be elaborated here.

[0269] It can be understood that based on the above Figure 10 shown interaction process, when multiple users enter the cockpit with their handheld terminals respectively, the in-vehicle device 200 can interact with the handheld terminals of each user through the corresponding matching screen to implement the authorization method provided by this application. In this way, each user entering the cockpit can experience quickly logging in to the account on the screen adapted to the corresponding seat, which is beneficial to improving the user experience, and the screens in the cockpit can also be used more frequently.

[0270] Similarly, for the Figures 9b to 9f login scenario shown above, the interaction process between each handheld device and each screen of the vehicle-mounted device 200 can refer to Figure 10 the relevant descriptions of each step in the process shown, which will not be elaborated here.

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

[0272] In the Figure 9e login scenario shown above, if the user operates on the used screen to select an authorized device, the corresponding screen of the vehicle-mounted device 200 can display Figure 11b the device list interface 1110 shown in the figure. The device list displayed on this interface 1110 can include information related to the mobile phones carried by the user himself and other users as alternative handheld devices. For example, the device list interface 1110 displayed on the above screen 200A can sequentially display information related to mobile phones 100A, 100B, 100C, and 100D. When the user clicks the login control "Click Me to Log In" corresponding to mobile phone 100A, 100B, 100C, or 100D on this device list interface 1110, the corresponding mobile phone can be set as the authorized device. It can be understood that if user A wants to log in to the account using user C's mobile phone 100C, usually user C needs to verify user C's biometric information on the authorization verification interface displayed on mobile phone 100C, and this operation can log in to user C's personal account on screen 200A with the authorization of user C.

[0273] And so on. In some other embodiments, multiple users entering the cockpit each carry multiple handheld devices, that is, n handheld terminals carried by m users (where m < n). At this time, while the vehicle-mounted device quickly matches the handheld devices for authorizing and logging in to the account for each user's used screen, it 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 respond to the user's operation of selecting other handheld terminals as authorized devices and display a list of information related to the handheld devices related to each user on the corresponding screen.

[0274] As an example, refer to Figure 12aIn the login scenario shown, user A can enter the cockpit with mobile phone 100A, smartwatch 400A, and tablet computer 500A and sit on the seat in the driver's area. User C can enter the cockpit with mobile phone 100C and smartwatch 400C and sit on the seat on the left side of the rear row. After the in-vehicle device 200 establishes device connections with mobile phone 100A, smartwatch 400A, tablet computer 500A, mobile phone 100C, and smartwatch 400C, it can determine the matching relationship between the corresponding screen and the corresponding handheld terminal based on the detection results of the ultrasonic detection technology and the seat sensor.

[0275] Reference Figure 12b , the above Figure 12a The matching relationship between the screen and the handheld device in the login scenario shown above may include the corresponding matching of screen 200A with mobile phone 100A, smartwatch 400A, and tablet computer 500A carried by user A and the corresponding matching of screen 200C with mobile phone 100C and smartwatch 400C carried by user C.

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

[0277] In some other embodiments, if the number of users entering the cockpit is greater than the number of screens in the in-vehicle device, each user can carry one or more handheld devices respectively. In this case, multiple users may need to use the same screen of the in-vehicle device to log in to the account. At this time, when the in-vehicle device quickly matches the handheld device for authorizing the login account for the screen used by each user, it can display the device list for the user to select the handheld terminal instead of displaying the recommended authorized device.

[0278] As an example, reference Figure 13aIn the login scenario shown, the in-vehicle device 200 only has screens 200A, 200B, and 200C. In this scenario, user A can enter the cockpit with mobile phone 100A and sit on the seat in the driver's area. User B can enter the cockpit with mobile phone 100B and sit on the seat in the co-driver's area. User C can enter the cockpit with mobile phone 100C and sit on the seat on the left side of the rear area. User D can enter the cockpit with mobile phone 100D and sit on the seat on the right side of the rear area. After the in-vehicle device 200 establishes device connections with mobile phones 100A, 100B, 100C, and 100D, based on the detection results of the ultrasonic detection technology and the detection results of the seat sensors, it may not be possible to determine the matching relationship between screen 200C and mobile phones 100C and 100D. If user C or user D operates to log in to an account on screen 200C, screen 200C can display a device list interface containing information related to mobile phones 100C and 100D for user C or user D sitting in the rear area to select.

[0279] Similarly, referring to Figure 13b In the login scenario shown, user A can enter the cockpit with mobile phone 100A and sit on the seat in the driver's area. User B can enter the cockpit with mobile phone 100B and sit on the seat in the co-driver's area. Users C, D, and E enter the cockpit with mobile phones 100C, 100D, and 100E respectively and sit on the seats in the left, middle, and right positions of the rear area in sequence. At this time, based on the detection results of the ultrasonic detection technology and the detection results of the seat sensors, the in-vehicle device 200 may not be able to determine the matching relationship between screen 200C and mobile phones 100C, 100D, and 100E, or may only be able to determine the matching relationship between screen 200C and the relatively closer mobile phone 100D. If user C, user D, or user E operates to log in to an account on screen 200C, screen 200C can display a device list interface containing information related to mobile phones 100C, 100D, and 100E for user C, user D, or user E sitting in the rear area to select.

[0280] In some other embodiments, among multiple users entering the cockpit, it is also possible that some users carry handheld terminals while some users do not carry handheld devices, that is, n handheld terminals carried by m users (where m > n). In this scenario, the in-vehicle device may detect that users are sitting on the seats in multiple areas based on the seat sensors. At this time, the in-vehicle device quickly finds the relatively closer handheld device for each user and displays relevant information such as the name or model of the handheld device for the users in the cockpit to refer to and judge the ownership user of the recommended authorized device, and then can instruct the corresponding user to perform authorized login on the corresponding handheld device. Details are not described here.

[0281] Figure 14 The following is a schematic diagram of the hardware structure of an electronic device according to an embodiment of the present application.

[0282] As Figure 14 shown, 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, etc. 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, etc.

[0283] It can be understood that the structure schematically shown in the embodiments 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 combine certain components, or split certain components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0284] In the embodiments of the present application, Figure 14 the illustrated electronic device 1400 may be the above-mentioned vehicle-mounted device 200, or may be an electronic device such as a handheld terminal carried by a user, which is not limited herein.

[0285] 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), etc. Among them, different processing units may be independent devices or integrated in one or more processors.

[0286] The controller may generate an operation control signal according to the instruction operation code and the timing signal to complete the control of fetching and executing instructions.

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

[0288] In the embodiments of the present application, the processor 110 of the vehicle-mounted device 200 can complete fetching instructions, executing instructions, etc. through the controller to implement the relevant steps executed by the vehicle-mounted device 200 and each screen in Embodiments 1 to 3 above. For specific details, reference can be made to the relevant descriptions in the above embodiments, which will not be elaborated here.

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

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

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

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

[0293] The USB interface 130 is an interface that complies with the USB standard specification, and can specifically be a Mini USB interface, a Micro USB interface, a USB Type C interface, etc. The USB interface 130 can be used to connect a charger to charge the electronic device 1400, and can also be used to transfer data between the 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, etc.

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

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

[0296] The wireless communication module 120 may provide solutions for wireless communications applied to the electronic device 1400, including wireless local area networks (WLANs) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), and the like.

[0297] The mobile communication module 130 may provide solutions for wireless communications applied to the electronic device 1400, including 2G / 3G / 4G / 5G and the like. The mobile communication module 130 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), and the like.

[0298] The main camera 170 and the wide-angle camera 171 are used to capture still images or videos. An object generates an optical image through the lens and projects it onto the photosensitive element. The photosensitive element may be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, and then transmits 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 a standard format such as RGB, YUV, etc.

[0299] The memory 180 may 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, application programs required for at least one function (such as a sound playback function, an image playback function, etc.). The data storage area may store data created during the use of the electronic device 1400 (such as audio data, phone book, 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 magnetic 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 the instructions stored in the memory 180 and / or the instructions stored in the memory provided in the processor.

[0300] The electronic device 1400 may implement audio functions through the audio module 150, the speaker, the receiver, the microphone, and the application processor, etc. For example, music playback, recording, etc.

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

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

[0303] The receiver, also known as the "earpiece", is used to convert an audio electrical signal into a sound signal. When the electronic device 1400 answers a call or a voice message, it can receive the voice through the receiver.

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

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

[0306] The seat sensor can be used to convert the pressure data detected by the pressure sensor into the perception data on whether there is a user sitting on the corresponding seat. For example, the seat sensor can convert the pressure data within a certain range detected by the pressure sensor, including the pressure data corresponding to the possible weights of adults, children, and the elderly, etc., into the perception data that a user is sitting on the corresponding seat is detected.

[0307] The acceleration sensor can detect the magnitude of the acceleration of the electronic device 1400 in various directions (generally three axes). When the electronic device 1400 is stationary, the magnitude and direction of gravity can be detected. It can also be used to identify the posture of the electronic device and applied to applications such as horizontal and vertical screen switching, pedometer, etc.

[0308] The distance sensor is used to measure the distance. The electronic device 1400 can measure the distance through infrared or laser. In some embodiments, in the shooting scene, the electronic device 1400 can use the distance sensor to measure the distance to achieve fast focusing.

[0309] The proximity light sensor can include, for example, a light-emitting diode (LED) and a light detector, such as a photodiode. The light-emitting diode can be an infrared light-emitting diode. The electronic device 1400 emits infrared light outward through the light-emitting diode. The electronic device 1400 uses the photodiode to detect the 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 that the user holds the electronic device 1400 close to the ear for a call, so as to automatically turn off the screen to achieve the purpose of power saving. The proximity light sensor can also be used for automatic unlocking and locking of the leather case mode and pocket mode.

[0310] The ambient light sensor is used to sense the ambient light brightness. The electronic device 1400 can adaptively adjust the display screen brightness according to the sensed ambient light brightness. The ambient light sensor can also be used to automatically adjust the white balance during photographing. The ambient light sensor can also cooperate with the proximity light sensor to detect whether the electronic device 1400 is in the pocket to prevent accidental touch.

[0311] A touch sensor, also known as a "touch control device". The touch sensor can be disposed on a display screen, and together with the display screen, they form a touch screen, also known as a "touch control screen". The touch sensor is used to detect touch operations acting thereon or in its vicinity. 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 some other embodiments, the touch sensor can also be disposed on the surface of the electronic device 1400, at a different position from where the display screen is located.

[0312] The button 102 includes a power-on button, volume buttons, etc. The button 102 can be a mechanical button or a touch button. The electronic device 1400 can receive button inputs and generate key signal inputs related to the user settings and function controls of the electronic device 1400.

[0313] The motor 103 can generate vibration prompts. The motor 103 can be used for incoming call vibration prompts and also for touch vibration feedback. For example, touch operations acting on different applications (such as taking pictures, playing audio, etc.) can correspond to different vibration feedback effects. Touch operations acting on different regions of the display screen can also make the motor 103 correspond to different vibration feedback effects. Different application scenarios (such as time reminder, receiving messages, alarm clock, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effects can also support customization.

[0314] The indicator 104 can be an indicator light and can be used to indicate the charging state, power change, and can also be used to indicate messages, missed calls, notifications, etc.

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

[0316] The embodiments of the mechanism disclosed in the present 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 memories and / or storage elements), at least one input device, and at least one output device.

[0317] A computer program module or module code can be applied to input instructions to perform the various functions described in this application 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.

[0318] The module code can be implemented in a high-level modular language or an object-oriented programming language to communicate with the processing system. When needed, the module code can also be implemented in assembly language or machine language. In fact, the mechanisms described in this application are not limited to the scope of any particular programming language. In either case, the language can be a compiled language or an interpreted language.

[0319] In some cases, the disclosed embodiments can be implemented in hardware, firmware, software, or any combination thereof. The disclosed embodiments can also be implemented as instructions carried or stored on one or more transient or non-transient machine-readable (e.g., computer-readable) storage media, which can be read and executed by one or more processors. For example, the instructions can be distributed via a network or via other computer-readable media. Thus, a machine-readable medium can include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer), including but not limited to, a floppy disk, a compact disc, a CD-ROM, a magneto-optical disc, 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 or optical card, a flash memory, or a tangible machine-readable memory for transmitting information (e.g., carrier waves, infrared signals, digital signals, etc.) in electrical, optical, acoustic, or other forms via the Internet. Thus, a machine-readable medium includes any type of machine-readable medium suitable for storing or transmitting electronic instructions or information in a form readable by a machine (e.g., a computer).

[0320] 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 in embodiments of the present application. The appearances of the phrase "in one embodiment" in various places in the specification are not necessarily all referring to the same embodiment.

[0321] The disclosure of embodiments of the present application also relates to an apparatus for performing the operations in the text. The apparatus may be specially constructed for the required purposes or it may comprise a general purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a computer readable medium, such as, but not limited to, any type of disk, including floppy disks, optical disks, CD-ROMs, magneto-optical disks, read-only memory (ROM), random access memory (RAM), EPROM, EEPROM, magnetic or optical cards, application specific integrated circuits (ASICs), or any type of medium suitable for storing electronic instructions, and each may be coupled to a computer system bus. In addition, the computers referred to in the specification may include a single processor or may be architectures involving multiple processors for increased computing power.

[0322] Additionally, the language used in this specification has been principally selected for readability and instructional purposes and may not have been selected to delineate or circumscribe the disclosed subject matter. Accordingly, the disclosure of embodiments of the present application is intended to illustrate rather than limit the scope of the concepts discussed herein.

Claims

1. An authorization method, characterized in that, the method includes: detecting that the spatial position relationship between a first user device and a first screen of a first space 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 to log in to a first account on the first screen, and the first account is the account logged in on the first user device; receiving first authorization result information, and corresponding to the first authorization result information indicating that authorization is passed, logging in to the first account on the first screen.

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

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

4. The method according to claim 3, characterized in that, the method further includes: detecting that the spatial position relationship between a second user device and the first screen satisfies the first condition, and, the sending the first authorization request information to the first user device includes: when it is determined that the priority of the first user device is higher than the priority of the second user device, sending the first authorization request information to the first user device.

5. The method according to claim 4, characterized in that, the method is applied to the first space device or applied to a second space device, and, when the method is applied to the second space device, the logging in to the first account on the first screen includes: the second space device sending a login instruction to the first space device, where 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 device, the method further includes: displaying an optional device list on the first screen, where the optional device list includes device information of multiple user devices, and 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, the sending the first authorization request information to the first user device includes: when it is detected that the user selects the first user device, sending first authorization information to the first user device.

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

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

9. The method according to any one of claims 1 to 8, wherein, The first space device includes a vehicle-mounted device.

10. An authorization system, wherein, The system includes a third space device and a server, wherein, The third space device is configured 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 a first condition, where the first authorization request message is used to request to log in to 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 configured 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 to the first account on the first screen when it determines that the first authorization result message indicates that the authorization is passed.

11. The system according to claim 10, wherein, The system further includes the first user device, wherein, The first user device is configured to respond to the first authorization request message and display a fourth interface, where the fourth interface is used to prompt the user to perform an authorization operation; and, The first user device 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, wherein, The third space device is disposed inside a physical space, the physical space includes a cockpit of a vehicle, and, The manner 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 a first area associated with the first screen inside the cockpit.

13. The system according to claim 12, wherein, The third space device sending the first authorization request message to the first user device includes: The third space device sends the first authorization request message to the first user device when it detects that the spatial position relationship between the second user device and the first screen meets the first condition and determines that the priority of the first user device is higher than the priority of the second user device.

14. An electronic device, wherein, Comprising: 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 is caused to execute the authorization method according to any one of claims 1 to 9.

15. A computer-readable medium, characterized in that instructions are stored on the readable medium, and when the instructions are executed on a computer, the computer is caused to execute the authorization method according to any one of claims 1 to 9.

Images