Information sharing method, electronic equipment and computer readable storage medium

[0019] Preferred embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although preferred embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure can be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

[0020] As used herein, the term "comprise" and its variants mean open inclusion, ie "including but not limited to". The term "or" means "and/or" unless otherwise stated. The term "based on" means "based at least in part on". The terms "one example embodiment" and "one embodiment" mean "at least one example embodiment." The term "another embodiment" means "at least one further embodiment". The terms "first", "second", etc. may refer to different or the same object. Other definitions, both express and implied, may also be included below.

[0021] It is found through research that, in the above-mentioned traditional schemes for information sharing, virtual key sharing is usually carried out in the form of short-distance Bluetooth authorization. For example, the car owner's mobile device needs to initiate a sharing request in the case of Bluetooth connection with the vehicle's keyless entry system (PEPS) ECU system, and the vehicle generates a corresponding code based on the sharing request and sends it to the car owner's mobile device. The owner's mobile device sends the code to the recipient's mobile device, for example via Bluetooth communication. The recipient's mobile device establishes a Bluetooth communication connection with the vehicle within the predetermined range of the vehicle, so as to send the received code to the vehicle. After the vehicle confirmation code is verified, the authorization certificate is fed back to the recipient's mobile device to make it Can unlock the owner's vehicle. The above-mentioned traditional virtual key sharing scheme requires the car owner to manually initiate Bluetooth authorization at close range, which is not conducive to the safe and convenient sharing of virtual keys by the car owner, and the shared virtual key cannot intelligently match the sharing scene under the condition of meeting the security requirements.

[0022] In order to at least partially address one or more of the above-mentioned problems as well as other potential problems, example embodiments of the present disclosure propose a scheme for information sharing. In this solution, at the first mobile device, a task request is sent to the server, the task request indicating at least task information about the associated vehicle of the first mobile device, so that the server determines the second mobile device for receiving the authorization credential based on the task request. device, the authorization credential is used to unlock the vehicle; sending object identification information to the server, for the server to send the authorization credential configured with permission information to the second mobile device in response to confirming that the second mobile device has passed the verification, and the permission information is based on the task The request and at least one of the associated attributes of the second mobile device and the first mobile device are configured, and the permission information is associated with the control range of the second mobile device for the vehicle.

[0023] In the above solution, the server automatically determines the second mobile device to receive the authorization credential (such as a virtual key) based on the task request from the first mobile device, and configures the virtual key based on the task request and/or the associated attributes of the second mobile device Authorization information, and sending the authorization credential to the verified second mobile device, the present disclosure can enable the user to share the authorization credential safely and conveniently, especially the sharing of the virtual key.

[0024] figure 1 A schematic diagram showing a system 100 for a method for information sharing according to an embodiment of the present disclosure. like figure 1 As shown, the system 100 includes a vehicle 110, a plurality of mobile devices of a plurality of users (a first mobile device 120 of a vehicle owner 160, a second mobile device 122 of an associated user 162, a third mobile device 124 of an associated user 164), a server 130 ,. In some embodiments, the first mobile device 120 , the second mobile device 122 , the third mobile device 124 , the server 130 , and the vehicle 110 can perform data interaction via the base station 150 and the network 140 , for example.

[0025] Regarding the vehicle 110, it includes at least: a vehicle machine, a vehicle-mounted data sensing device, and a vehicle-mounted T-BOX. The on-board data sensing device is used to sense the vehicle's own data and the external environment data where the vehicle is located in real time.

[0026] Regarding the on-vehicle T-BOX, it is used for data interaction between the vehicle and the machine, the mobile device 120, the roadside unit, and the server 130. The vehicle T-BOX includes, for example, a SIM card, GPS antenna, 4G or 5G antenna, etc. When the user sends a control command (remotely start the vehicle, turn on the air conditioner, adjust the seat to a suitable position, etc.) After the control command is obtained, the control message is sent through the CAN bus to realize the control of the vehicle, and finally the operation result is fed back to the user's mobile phone APP. The on-vehicle T-BOX communicates with the vehicle through canbus to realize data interaction, such as transmitting vehicle status information, button status information, control instructions, etc. The vehicle-mounted T-BOX can collect bus data related to the vehicle 110 bus Dcan, Kcan, and PTcan.

[0027] The vehicle 110 and the mobile device can exchange and share data through wireless communication means such as Wi-Fi, Bluetooth, and cellular. For example, in some embodiments, the first mobile device 120 obtains the virtual key data associated with the user account from the cloud after logging in to the virtual key APP through the user account. For example, the first mobile device 120 first uses the private key pair to acquire the virtual key data Decrypt to obtain a virtual key that can be shared. The virtual key data includes, for example, T-BOX's Bluetooth information, connection key (CONNECTKEY), access key (ACCESSKEY), key authority and validity period, etc. For example, the first mobile device 120 can perform remote data interaction with the on-board T-BOX of the vehicle 110 via Bluetooth near field communication or the server 130 (eg TSP) via a predetermined application (eg virtual key APP). For example, the first mobile device 120 scans the BLE device through the server 130 through the virtual key APP to find the T-BOX of the vehicle 110 of the vehicle 110, connects to the T-BOX via the server 130 and sends a connection key (CONNECTKEY), and the T-BOX confirms the received After the connection key (CONNECTKEY) is verified, the T-BOX analyzes the instruction obtained from the virtual key APP of the first mobile device 120. If it is determined that the instruction is to unlock the door, the T-BOX will send a message to the CANBUS of the vehicle. Execute the lock command.

[0028]In some embodiments, T-BOX can return a random code to the virtual key APP of the first mobile device 120 via the server 130 after confirming that the received connection key (CONNECTKEY) is verified, and the virtual key APP and T-BOX are based on Access key (ACCESSKEY) and random code encrypt interactive data to prevent replay attacks.

[0029] Real-time data interaction is performed between the vehicle 110 and the server 130 through wireless communication technologies such as satellite wireless communication or mobile cellular, for example. For example, the signal interaction between the vehicle 110 and the server 130 via the T-BOX can be performed using the TLS1.2 standard. The T-BOX of the vehicle 110 is configured with a security identifier (ie Security ID) for uniquely identifying the T-BOX when it leaves the factory. The server 130 can perform authentication with the T-BOX based on the security identifier, so as to ensure the security of data interaction.

[0030] With respect to mobile devices, it is, for example but not limited to, a cell phone. In some embodiments, the mobile device may be a tablet computer. The terminal device can directly perform near-field data interaction with the vehicle T-BOX, or can perform remote data interaction with the vehicle T-BOX via the server 130 . In addition, the first terminal device may also perform data interaction with the second mobile device 122 , the third mobile device 124 , and the server 130 via the base station 150 and the network 140 . A predetermined application (such as a virtual vehicle key APP) is configured on the mobile device. For example, through a predetermined action (such as shaking), the mobile device can establish association with the vehicle 110 and start a predetermined application (such as a virtual vehicle key APP). The first terminal device 120 may send a task request about the associated vehicle 110 to the server 130 , so that the server 130 determines the second mobile device 122 for receiving the virtual key for unlocking the vehicle 110 based on the task request. The first terminal device 120 may also send to the server 130 the object identification information for the second mobile device 122 to verify, so that when the second mobile device 122 passes the verification, the server 130 sends the second mobile device 122 the information configured with Authorization credentials for permission information.

[0031] Regarding the server 130, it is used to provide car networking services, such as providing car remote services. In some embodiments, the server 130 may be a computing device such as a server, which has one or more processing units, including special-purpose processing units such as GPUs, FPGAs, and ASICs, and general-purpose processing units such as CPUs. Additionally, one or more virtual machines may also be running on each computing device. In some embodiments, the server 130 may determine the second mobile device 122 to receive the virtual key for unlocking the vehicle based on the task request from the first mobile device 120 regarding the associated vehicle, and based on the task request and the second mobile device 122 and the associated attributes of the first mobile device 120 to configure the authority information related to the control range of the virtual key;

[0032] The following will combine figure 2 A method for information sharing according to an embodiment of the present disclosure is described. figure 2 A flowchart of a method 200 for information sharing according to an embodiment of the present disclosure is shown. It should be understood that method 200 may, for example, be Figure 8 The described electronic device 800 executes. also available at figure 1 The described server 130 executes. It should be understood that method 200 may also include additional actions not shown and/or actions shown may be omitted, and that the scope of the present disclosure is not limited in this respect.

[0033] At block 202 , the server 130 obtains a mission request from the first mobile device 120 , the mission request including mission information about the vehicle 110 associated with the first mobile device 120 . In some embodiments, the task information included in the task request is used to identify the task content about the vehicle 110 , such as maintenance, vehicle rental, vehicle sharing, substitute driving, takeaway, express delivery, and the like. In some embodiments, the task request further includes object identification information for indicating the second mobile device 122 performing the task associated with the vehicle 110 . The object identification information includes, for example, at least one of: the mobile phone number of the second mobile device 122 , the account or instant messaging application number bound to the second mobile device 122 , and the identity of the associated user 162 of the second mobile device 122 .

[0034] At block 204, the server 130 determines, based on the task request, a second mobile device 122 for receiving an authorization credential (eg, a virtual key of the vehicle 110) for unlocking the vehicle. For example, the server 130 determines the second mobile device 122 to receive the virtual key based on the task information and/or the object identification information.

[0035] At block 206, the server 130 configures permission information about the authorization credential of the task information based on at least one of the task request and the associated attributes of the second mobile device 122 and the first mobile device 120, and the permission information is related to the second mobile device 122. Device 122 is associated with respect to the range of maneuvering of vehicle 110 . In some embodiments, the server 130 can configure multiple (for example, four) different control ranges corresponding to the vehicle 110 . In some embodiments, the control range of the vehicle 110 is associated with the security control level of the vehicle 110 , for example, the unlockable ranges of the CAN bus, OTA, T-BOX, and other vehicle components are different under different authority levels.

[0036] In some embodiments, the permission information of the virtual key includes, for example but not limited to, first to fourth permission levels, and these four permission levels correspond to four different control ranges for the vehicle 110 , for example. For example, the first to fourth authority levels are, for example but not limited to: friend and family authority level, maintenance authority level, driving authority level and fetching authority level.

[0037] With regard to friends and family permission levels, in some embodiments it is, for example, the highest level of vehicle control permissions. In some embodiments, it is, for example, a higher level next to the control range of the vehicle owner's virtual key. Under this permission level, the CAN bus, OTA, T-BOX and other vehicle components can be unlocked by the shared virtual key, for example. In some embodiments, the server 130 determines the second mobile device 122 based on, for example, the friend information of the instant messaging application bound to the first mobile device 120 and/or object identification information about the second mobile device 122 included in the task request. Whether the associated user 162 of the mobile device 122 is a friend or family member of the user 160 of the first mobile device 120 . In some embodiments, if the server 130 determines that the instant messaging application account bound to the mobile phone number of the second mobile device 122 is a friend of the instant messaging application account bound to the mobile phone number of the first mobile device 120, or If the address book of a mobile device 120 or the contact group identifier of an instant messaging application is identified as a friend or a family member, then the associated attribute of the second mobile device 122 is determined to be a friend or a family member. For another example, the server 130 may determine the associated attribute of the second mobile device 122 based on the object identification information included in the task request. For example, if the server 130 determines that the object identification information in the task request sent by the first mobile device 120 indicates that the associated user 162 of the second mobile device 122 is a friend or family member of the user 160 of the first mobile device 120 . Then the associated attribute of the second mobile device 122 is determined to be the family and friends authority level corresponding to the highest authority level.

[0038] In some embodiments, if the server 130 can determine that the image of the associated user 162 about the second mobile device 122 includes the user 160 of the first mobile device; If the number of images matching the associated user's image exceeds a predetermined value, it may be determined that the associated user 162 of the second mobile device 122 is a friend or family member of the user 160 of the first mobile device 120 . For example, images of the associated user 162 frequently appear in photos sent or stored by the first mobile device 120 , or images of the associated user 162 on the second mobile device 120 also include the user 160 . Then the server 130 can determine that the associated user 162 is a friend or family member of the user 160 . In some embodiments, the server 130 may further determine whether the associated user 162 and the user 160 are friends or family members based on their positional relationship in the same image. For example, if the image shows that the distance between the associated user 162 and the user 160 is less than a predetermined distance, or there is friendly physical contact such as holding arms, the server 130 may determine that the associated user 162 is a friend or family member of the user 160 . By adopting the above means, it is possible to conveniently confirm the matching authority of the recipient of the virtual key based on a photo or an image.

[0039] In some embodiments, the server 130 obtains, for example, the task information about the maintenance vehicle 110 sent by the first mobile device 120, and the server 130 determines that the object identification information in the task request does not refer to friends or family members of the user 160 of the first mobile device 120 , the authority level of the virtual key is determined as the maintenance authority level. Regarding the maintenance authority level, in some embodiments, it is suitable for tasks such as vehicle maintenance and other tasks. This authority level is relatively high. Under this authority level, OTA (remote software upgrade) is turned off, remote key management is reserved, and remote debugging is turned off. Interface and shut down the remote control vehicle, other parts of the vehicle can be unlocked, however, the user's 160 personal belongings box in the vehicle 110 cannot be opened. The server 130 may also configure the permission level of the virtual key as the driving permission level or the fetching permission level based on the task content indicated by the task information.

[0040] Regarding the level of driving authority, in some embodiments, it is applicable to tasks such as driving on behalf of the vehicle, sharing, leasing, etc. Under this authority, the front cover of the vehicle cannot be unlocked and opened, for example.

[0041] With regard to the permission level for picking up objects, in some embodiments, it is applicable to tasks such as takeaway and express delivery of the vehicle, and the permission level is the lowest. Under this permission, only the trunk of the vehicle 110 can be opened based on the virtual key. Under this permission, close the remote control vehicle and multimedia system, close the remote software upgrade, keep the remote key management; close the remote debugging interface and external interface (USB).

[0042] In some embodiments, the permission information of the virtual key also includes default permissions and/or user-defined permissions. The following will also combine Figure 5 Further determine and describe the specific way to configure permission information. Here, no more details.

[0043] At block 208, the server 130 confirms whether the second mobile device 122 is authenticated. In some embodiments, the server 130 confirms whether the second mobile device 122 passes the verification based on the acquired object identification information from the first mobile device 120 indicating that the second mobile device 122 performs a task related to the vehicle 110 . The object identification information includes, for example, at least one of: the mobile phone number of the second mobile device 122 , the account or instant messaging application number bound to the second mobile device 122 , and the identity of the associated user 162 of the second mobile device 122 . In some embodiments, the object identification information may also include an image of the associated user 162 for the second mobile device 122 . The following will also combine image 3 Further identify the method used to verify who the authorized credential is shared with. Here, no more details.

[0044] At block 210 , if the server 130 confirms that the second mobile device 122 is authenticated, an authorization credential configured with permission information is sent to the second mobile device 122 .

[0045] exist figure 2 In the above solution shown, the server automatically determines the second mobile device to receive the authorization credential (such as a virtual key) based on the task request from the first mobile device, and configures based on the task request and/or the associated attributes of the second mobile device The permission information of the virtual key, and sending the authorization certificate to the verified second mobile device, this disclosure can automatically configure the permission information of the virtual key according to the sharing scene of the virtual key, without the need for the user to make additional settings, so that the user can safely and conveniently Share authorization credentials, especially the sharing of virtual keys.

[0046] In some embodiments, the method 200 further includes: the server 130 sends the configured permission information to the first mobile device 120, so as to present an interface element for identifying the permission information at the first mobile device 120 (such as Figure 7 The interface element 700 is shown), and the interface element 700 supports the user to perform operations associated with the permission information. will be combined later Figure 7 The interface element 700 is described in detail, and will not be repeated here.

[0047] image 3 A flowchart of a method 300 for verifying authorized credential sharing objects according to an embodiment of the present disclosure is shown. It should be understood that the method 300 can be, for example, in Figure 8 The described electronic device 800 executes. also available at figure 1 The described server 130 executes. It should be understood that method 300 may also include additional actions not shown and/or actions shown may be omitted, and that the scope of the present disclosure is not limited in this respect.

[0048] At block 302 , the server 130 obtains object identification information from the first mobile device 120 , the object identification information including an image of the associated user 162 on the second mobile device 122 . In some embodiments, the image of the associated user 162 may be locally sourced from the first mobile device 120 (for example, pre-stored by the first mobile device 120 ), or obtained from a network or an instant messaging application. For example, the avatar photo of the driver who received the order or the driver (such as the avatar photo of the Didi driver) is obtained through the taxi-hailing software, and another example is the WeChat friend image received through instant messaging applications such as WeChat.

[0049] In some embodiments, the server 130 obtains the face area of ​​the associated user 162 in the image based on the image of the associated user, and then performs feature extraction on the face area to obtain the face features of the image of the associated user.

[0050] At block 304 , the server 130 obtains the facial image captured via the second mobile device 122 . In some embodiments, the server 130 prompts the associated user 162 to perform a predetermined action (such as blinking) during the collection of facial images via the second mobile device 122, and acquires multiple images during the predetermined action by the associated user through the camera of the second mobile device 122. Frame the face image.

[0051] At block 306, the server 130 confirms whether the face image matches the image of the associated user 162 based on the image features extracted from the face image. In some embodiments, before the server 130 correlates the facial features of the image of the user 162 with the facial features in the collected multiple frames of facial images, the server 130 first bases on the facial features in the collected multiple frames of facial images. At least one of the position change of the key point, the association relationship between the foreground area and the face area is used to determine whether the multi-frame face image is collected from the living body of the associated user 162 .

[0052] At block 308 , if the server 130 confirms that the facial image matches that of the associated user 162 , an authorization credential is sent to the second mobile device 122 .

[0053] pass image 3 As shown in the above solution, the present disclosure can conveniently verify the virtual key sharing object through images. Further, the above method 300 can also prevent others from defrauding the virtual key of the vehicle 110 by using the image or video of the associated user 162 for verification.

[0054] In some embodiments, method 200 may also include method 400 for invalidating authorization credentials. Figure 4 A flowchart of a method 400 for invalidating authorization credentials according to an embodiment of the present disclosure is shown. It should be understood that method 400 may, for example, be Figure 8 The described electronic device 800 executes. also available at figure 1 Execution at the management device 130 is described. It should be understood that method 400 may also include additional actions not shown and/or actions shown may be omitted, and that the scope of the present disclosure is not limited in this respect.

[0055] At block 402 , the server 130 may confirm whether at least one of the following conditions is satisfied: a predetermined authorization time for the authorization token has arrived, or an instruction about revoking the authorization token is detected from the first mobile device 120 .

[0056] At block 404, if the server 130 confirms that at least one of the conditions mentioned at block 402 is satisfied, the authorization credential for obtaining the state information of the vehicle is the virtual key of the vehicle.

[0057] At block 406 , the server 130 determines whether the vehicle is in an engine-off state based on the state information.

[0058] At block 408, if the server 130 confirms that the vehicle 110 is turned off, the authorization credential is invalidated. By adopting the above means, the present disclosure can conveniently take back the shared virtual key after confirming that the vehicle 110 is in a non-driving safe state.

[0059] In some embodiments, the method 200 may also include a method 500 for configuring permission information of the authorization credential. Figure 5 A flowchart of a method 500 for configuring permission information of an authorization credential according to an embodiment of the present disclosure is shown. It should be understood that method 500 may, for example, be Figure 8 The described electronic device 800 executes. also available at figure 1 The described management device 130 executes. It should be understood that method 500 may also include additional actions not shown and/or actions shown may be omitted, and that the scope of the present disclosure is not limited in this respect.

[0060] At block 502 , the server 130 determines whether the associated attribute of the second mobile device 122 indicates that the associated user 162 of the second mobile device 122 is a friend or family member of the user 160 of the first mobile device 120 . Whether the associated user of the second mobile device 122 is a friend or family member of the user of the first mobile device 120 can be determined in a number of ways.

[0061] In some embodiments, the server 130 may determine whether the associated user of the second mobile device 122 is the user of the first mobile device based on the friend information or the contact group identifier of the instant messaging application account bound to the first mobile device 120. friends or family. For example, if the server 130 determines that the instant messaging application account bound to the mobile phone number of the second mobile device 122 belongs to a friend of the first mobile device 120, then determine that the associated attribute of the second mobile device 122 is friend or family member. For another example, the server 130 may determine the association attribute of the second mobile device 122 based on the object identification information about the second mobile device included in the task request. For example, if the server 130 determines that the object identifier about the second mobile device 122 in the task request sent by the first mobile device 120 indicates that the associated user 162 of the second mobile device 122 is a friend or family member of the user 160 of the first mobile device 120 . Then the association attribute of the second mobile device 122 is determined as the family members and friends of the first mobile device 120 . In some embodiments, if the server 130 determines that the task information in the task request indicates surrogate driving or takeaway, the server 130 determines that the associated attribute of the second mobile device 122 is a third party.

[0062] At block 504, if the server 130 determines that the associated user 162 of the second mobile device 122 is a friend or family member of the user 160 of the first mobile device 120, the authorization information is configured such that the authorization credential can unlock the vehicle within the first range of the vehicle. part. In some embodiments, the first control range corresponds to, for example, the highest authority level, and the first control range of the vehicle 110 corresponds to, for example, the control range under the above-mentioned friend or family authority level. Under this permission level, CAN bus, OTA, T-BOX and other parts of the vehicle can be unlocked.

[0063] At block 506, the server 130 determines whether the task information is associated with maintenance of the vehicle. For example, the server 130 may determine whether the sharing of the virtual key is related to the maintenance and repair of the vehicle 110 based on the task information. For example, based on the vehicle state information of the vehicle 110 and the schedule information of the user 160 of the first mobile device 120, the server 130 can determine whether the time the vehicle 110 stays at the current vehicle location is greater than or equal to the time required for maintaining the vehicle; and obtains the first The mobile device sends the task information about the maintenance vehicle 110 and the mobile phone numbers of the mobile devices of the multiple 4S shop personnel. The server 130 determines that the sharing of the virtual key is related to the maintenance and repair of the vehicle 110 .

[0064] At block 508 , if the server 130 determines that the task information is associated with maintenance of the vehicle 110 , the authorization information is configured such that the authorization credential may unlock vehicle components within the second operating range of the vehicle. Because the maintenance and repair of the vehicle requires a comprehensive inspection and repair of each component of the vehicle 110 , a wide authority level for the vehicle control range is required. In some embodiments, the second maneuvering range of the vehicle 110 corresponds to, for example, the aforementioned maneuvering range under the maintenance authorization level. Under this permission level, close the remote control vehicle, close the remote software upgrade, keep the remote key management, close the remote debugging interface, and other parts of the vehicle can be unlocked. However, the personal belongings box of the user 160 in the vehicle 110 cannot be opened.

[0065] At block 510, the server 130 determines whether the task information indicates at least one item in a first set of predetermined tasks. In some embodiments, the first set of predetermined tasks includes, for example, car driving, car sharing, car rental and car exchange.

[0066] At block 512, if the server 130 can determine that the task information indicates at least one of the first predetermined set of tasks, configure the authorization information such that the authorization credential can unlock vehicle components within a third operating range of the vehicle, the first operating range being greater than the first operating range Second control range and third control range. The third maneuvering range of the vehicle 110 corresponds to, for example, the aforementioned maneuvering range under the driving authorization level. Under this permission level, turn off the remote control vehicle and multimedia system; turn off the remote software upgrade, keep the remote key management; turn off the remote debugging interface and external interface (USB); other parts of the vehicle can be unlocked, but the front cover of the vehicle cannot be unlocked. Open.

[0067] In some embodiments, if the server 130 can determine that the task information indicates at least one item in the second set of predetermined tasks, configure the authority information so that the authorization credential can unlock the vehicle components within the fourth operating range of the vehicle, the fourth operating range is less than A second maneuvering range and a third maneuvering range. In some embodiments, the second scheduled task set includes, for example, food delivery, express delivery, and the like. The fourth control range of the vehicle 110 corresponds to, for example, the control range under the above-mentioned access level. Under this authority level, for example, the second mobile device 122 can only open the trunk of the vehicle 110 based on the obtained virtual key, and close the remote control vehicle and multimedia system; close the remote software upgrade; remote upgrade, keep the remote key management; close the remote Debug interface, external interface (USB).

[0068] exist Figure 5 In the above solution shown, the server of the present disclosure can automatically determine the permission level of the virtual key with a security level that matches the associated attribute and task content of the associated user of the second mobile device 122, which can meet the requirements for permissions in different scenarios of shared keys. Intelligent management.

[0069] Image 6 A flowchart of a method 600 for information sharing according to an embodiment of the present disclosure is shown. It should be understood that the method 600 can be, for example, in Figure 8 The described electronic device 800 executes. also available at figure 1 Execution at mobile device 120 is described. It should be understood that method 600 may also include additional actions not shown and/or actions shown may be omitted, and that the scope of the present disclosure is not limited in this respect.

[0070]At block 602, the first mobile device 120 sends a task request to the server 130, the task request indicating at least task information about the associated vehicle 110 of the first mobile device 120, so that the server 130 determines the first task for receiving the authorization credential based on the task request. Two mobile devices 122 , and authorization credentials are used to unlock the vehicle 110 .

[0071] At block 604, the first mobile device 120 sends the object identification information to the server 130, so that the server 130 sends an authorization credential configured with permission information to the second mobile device 122 in response to confirming that the second mobile device 122 passes the verification, The authority information is configured based on at least one of the task request and the associated attributes of the second mobile device 122 and the first mobile device 120 , and the authority information is associated with the control range of the vehicle 110 by the second mobile device 122 .

[0072] Regarding the object identification information, in some embodiments, the object identification information sent by the first mobile device 120 to the server 130 may be the mobile phone number of the second mobile device 122, the identification of the associated user 162 of the second mobile device 122 (such as the associated ID number of the user 162), the account number of the associated user, and at least one item of the image about the associated user. For example, the object identification information sent by the first mobile device 120 to the server 130 includes an image of the associated user of the second mobile device, so that the server 130 can confirm that the face image collected by the second mobile device 120 is associated with the image of the user. Whether it matches, if the server 130 confirms that the face image collected by the second mobile device 120 matches the image of the associated user, the server 130 sends an authorization credential configured with determined authority information to the second mobile device, so that the second mobile device The associated user of device 120 unlocks vehicle 110 based on the received virtual key.

[0073] In some embodiments, the method 600 further includes: the first mobile device 120 acquires the permission information of the configured virtual key from the server 130; and based on the permission information, displaying an interface element for identifying the permission information (for example, as Figure 7 As shown in the interface element 700), the interface element supports the user to perform operations associated with the permission information.

[0074] In some embodiments, the interface elements at least include: a first interface element and a plurality of icons. The first interface element is used to indicate the vehicle 110 , and a plurality of icons are used to respectively identify the statuses of multiple vehicle components that are prohibited from being unlocked in the control range corresponding to the authority information. In some embodiments, multiple icons are operable. The first mobile device 120 may confirm whether an operation on the icon is detected. If the first mobile device 120 confirms that the operation on the icon is detected, then based on the icon targeted by the operation, determine the vehicle components that are prohibited from unlocking included in the control range corresponding to the authority information. will be combined later Figure 7 The composition and control method of the interface element 700 will be described in detail, and will not be repeated here.

[0075] exist Image 6 In the shown method 600 for information sharing, the first mobile device 120 sends a task request to the server 130, so that the server 130 can determine the second mobile device 122 to receive the authorization certificate for unlocking the vehicle based on the task request, and send the request to the server. 130 sends the object identification information so that when the second mobile device 122 passes the verification, the server 130 determines the authority information of the virtual key based on the task request and the associated attribute of the second mobile device, and sends the authorization certificate. This disclosure can make the user safe and convenient Sharing of authorization credentials, especially the sharing of virtual keys.

[0076] The following will combine Figure 7 Interface elements according to embodiments of the present disclosure are described. Figure 7 A schematic diagram of an interface element 700 according to an embodiment of the present disclosure is shown, and it should be understood that the interface element 700 may be, for example, in Figure 8 The depicted electronic device 800 is presented. also available at figure 1 The mobile device 120 is depicted. It should be understood that interface element 700 may also include additional elements not shown and/or elements shown may be omitted, and the scope of the present disclosure is not limited in this respect.

[0077] like Figure 7 As shown, the interface element 700 at least includes: a first interface element 710 used to indicate the vehicle 110 ; and a plurality of icons used to respectively identify the states of multiple unlockable vehicle components in the control range corresponding to the authority information.

[0078] In some embodiments, the plurality of icons include, for example but not limited to: icon 720 for engine start unlock, icon 722 for window control unlock, icon 724 for door unlock, icon for remote vehicle status query unlock Icon 726, icon 728 for unlocking the trunk, and icons not shown below for remote control car unlocking, icons for remote key management unlocking, icons for remote upgrade unlocking, and unlocking for debugging interfaces icon, an icon for unlocking the external interface (USB), an icon for unlocking the multimedia system, etc. The above-mentioned multiple icons may indicate the control range corresponding to the authority of the currently configured virtual key, that is, indicate the state where unlocking of vehicle components is prohibited under the currently configured authority level. By adopting the above means, the user of the mobile device can intuitively understand the control range of the shared virtual key.

[0079] The above-mentioned multiple icons may also support user operations. For example, if the first mobile device 120 determines that the user's operation on one or more icons of the multiple icons is detected, the unlocking prohibition setting of the vehicle component corresponding to the operated icon may be changed. , such as changing the setting of the operated icon from prohibiting unlocking to allowing unlocking, and then editing the control range corresponding to the permission information of the virtual key. In some embodiments, the first mobile device 120 can also customize the control range corresponding to the permission information of the virtual key to be shared by selecting one or more icons among the above-mentioned icons. By adopting the above means, the user of the mobile device can conveniently edit and customize the control range of the virtual key, so as to adapt to the needs of different key sharing scenarios.

[0080] Figure 8 A block diagram of an electronic device 800 suitable for implementing embodiments of the present disclosure is schematically shown. Device 800 may be used to implement the Figures 2 to 6 Apparatus for methods 200, 300, 400, 500, 600 and 700 are shown. like Figure 8 As shown, the device 800 includes a central processing unit (CPU) 801 that can operate according to computer program instructions stored in a read only memory (ROM) 802 or loaded from a storage unit 808 into a random access memory (RAM) 803 , to perform various appropriate actions and processing. In the RAM 803, various programs and data necessary for the operation of the device 800 can also be stored. The CPU 801 , ROM 802 , and RAM 803 are connected to each other via a bus 804 . An input/output (I/O) interface 805 is also connected to the bus 804 .

[0081] Multiple components in the device 800 are connected to the I/O interface 805, including: an input unit 806, an output unit 807, and a storage unit 808. The processing unit 801 executes various methods and processes described above, for example, executes methods 200, 300, 400, 500, 600 and 700. For example, in some embodiments, methods 200 , 300 , 400 , 500 , 600 , and 700 may be implemented as a computer software program stored on a machine-readable medium, such as storage unit 808 . In some embodiments, part or all of the computer program may be loaded and/or installed onto the device 800 via the ROM 802 and/or the communication unit 809 . When the computer program is loaded into RAM 803 and executed by CPU 801, one or more operations of methods 200, 300, 400, 500, 600 and 700 described above may be performed. Alternatively, in other embodiments, the CPU 801 may be configured to perform one or more actions of the methods 200, 300, 400, 500, 600, and 700 in any other suitable manner (eg, by means of firmware).

[0082] It should be further explained that the present disclosure may be a method, device, system and/or computer program product. A computer program product may include a computer-readable storage medium having computer-readable program instructions thereon for carrying out various aspects of the present disclosure.

[0083] A computer readable storage medium may be a tangible device that can retain and store instructions for use by an instruction execution device. A computer readable storage medium may be, for example, but is not limited to, an electrical storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of computer-readable storage media include: portable computer diskettes, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or flash memory), static random access memory (SRAM), compact disc read only memory (CD-ROM), digital versatile disc (DVD), memory stick, floppy disk, mechanically encoded device, such as a printer with instructions stored thereon A hole card or a raised structure in a groove, and any suitable combination of the above. As used herein, computer-readable storage media are not to be construed as transient signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides or other transmission media (e.g., pulses of light through fiber optic cables), or transmitted electrical signals.

[0084] Computer-readable program instructions described herein may be downloaded from a computer-readable storage medium to a respective computing/processing device, or downloaded to an external computer or external storage device over a network, such as the Internet, a local area network, a wide area network, and/or a wireless network. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers, and/or edge servers. A network adapter card or a network interface in each computing/processing device receives computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in a computer-readable storage medium in each computing/processing device .

[0085] Computer program instructions for performing the operations of the present disclosure may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or Source or object code written in any combination, including object-oriented programming languages—such as Smalltalk, C++, etc., and conventional procedural programming languages—such as “C” or similar programming languages. Computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer, or entirely on the remote computer or server implement. In cases involving a remote computer, the remote computer can be connected to the user computer through any kind of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computer (such as via the Internet using an Internet service provider). connect). In some embodiments, an electronic circuit, such as a programmable logic circuit, field programmable gate array (FPGA), or programmable logic array (PLA), can be customized by utilizing state information of computer-readable program instructions, which can Various aspects of the present disclosure are implemented by executing computer readable program instructions.

[0086] Aspects of the present disclosure are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the disclosure. It should be understood that each block of the flowcharts and/or block diagrams, and combinations of blocks in the flowcharts and/or block diagrams, can be implemented by computer-readable program instructions.

[0087]These computer-readable program instructions can be provided to a processor in a voice interaction device, a general-purpose computer, a special-purpose computer, or a processing unit of another programmable data processing device, thereby producing a machine that allows these instructions to be processed by a computer or other programmable When the processing unit of the data processing device is executed, a device for realizing the functions/actions specified in one or more blocks in the flowchart and/or block diagram is generated. These computer-readable program instructions can also be stored in a computer-readable storage medium, and these instructions cause computers, programmable data processing devices and/or other devices to work in a specific way, so that the computer-readable medium storing instructions includes An article of manufacture comprising instructions for implementing various aspects of the functions/acts specified in one or more blocks in flowcharts and/or block diagrams.

[0088] It is also possible to load computer-readable program instructions into a computer, other programmable data processing device, or other equipment, so that a series of operational steps are performed on the computer, other programmable data processing device, or other equipment to produce a computer-implemented process , so that instructions executed on computers, other programmable data processing devices, or other devices implement the functions/actions specified in one or more blocks in the flowcharts and/or block diagrams.

[0089] The flowchart and block diagrams in the figures illustrate the architecture, functions, and operations of possible implementations of apparatuses, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in a flowchart or block diagram may represent a module, a program segment, or a portion of an instruction that contains one or more programmable components for implementing the specified logical functions. Execute instructions. In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks in succession may, in fact, be executed substantially concurrently, or they may sometimes be executed in the reverse order, depending upon the functionality involved. It should also be noted that each block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by a dedicated hardware-based system that performs the specified function or action , or may be implemented by a combination of dedicated hardware and computer instructions.

[0090] Having described various embodiments of the present disclosure above, the foregoing description is exemplary, not exhaustive, and is not limited to the disclosed embodiments. Many modifications and alterations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is chosen to best explain the principle of each embodiment, practical application or technical improvement in the market, or to enable other ordinary skilled in the art to understand each embodiment disclosed herein.

[0091] The above are only optional embodiments of the present disclosure, and are not intended to limit the present disclosure. For those skilled in the art, the present disclosure may have various modifications and changes. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present disclosure shall be included within the protection scope of the present disclosure.