Detailed Description
Preferred embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While the preferred embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may 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.
The term "include" and variations thereof as used herein is meant to be inclusive in an open-ended manner, i.e., "including but not limited to". Unless specifically stated otherwise, the term "or" means "and/or". 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 additional embodiment". The terms "first," "second," and the like may refer to different or the same object. Other explicit and implicit definitions are also possible below.
It is found that, in the above conventional scheme for information sharing, virtual key sharing is usually performed by means of bluetooth short-range authorization. For example, the mobile device of the vehicle owner needs to initiate a sharing request under the condition of bluetooth connection with a vehicle keyless entry system (PEPS) ECU system, and the vehicle generates a corresponding code based on the sharing request and sends the code to the mobile device of the vehicle owner. The owner's mobile device sends the code to the recipient's mobile device, for example by means of bluetooth communication. The mobile device of the receiver establishes Bluetooth communication connection with the vehicle within a preset range from the vehicle so as to send the received code to the vehicle, and after the vehicle confirmation code is verified, the authorization certificate is fed back to the mobile device of the receiver, so that the mobile device of the vehicle owner can be unlocked. The above conventional virtual key sharing scheme requires that the owner and the receiver manually initiate bluetooth authorization in a close range, which is not beneficial for the owner to safely and conveniently share the virtual key remotely.
To address, at least in part, one or more of the above issues and other potential issues, example embodiments of the present disclosure propose a scheme for information sharing. In the scheme, at a server, in response to detecting a query request from a first mobile device, querying authorization credentials of an associated vehicle with the first mobile device, the authorization credentials for unlocking the associated vehicle; obtaining a sharing request from a first mobile device for sharing an authorization credential with a second mobile device, the sharing request including at least an identification of the second mobile device, the sharing request being generated based on a first voice obtained at the first mobile device; in response to the confirmation detecting the pickup request from the second mobile device, confirming whether the pickup request is validated; and generating an associated account number for the second mobile device to acquire the authorization credential based on the pickup request in response to confirming that the pickup request is verified.
In the scheme, when the first mobile device confirms that the first voice is associated with the authorization certificate of the associated vehicle, sharing information is generated based on the first voice, and a second mobile device for receiving the authorization certificate is determined based on the sharing information; and then sending a sharing request to the server for sharing the authorization credential to the second mobile device, the present disclosure enables the user to share the authorization credential securely, conveniently, and remotely.
Fig. 1 shows a schematic diagram of a system 100 for a method for information sharing according to an embodiment of the present disclosure. As shown in fig. 1, system 100 includes a vehicle 110, a plurality of mobile devices of a plurality of users (e.g., a first mobile device 120 specifically including user 160, a second mobile device 122 specifically including user 162), and a server 130. In some embodiments, the first mobile device 120, the second mobile device 122, the server 130, and the vehicle 110 may interact with data via the base station 150 and the network 140, for example.
As for the vehicle 110, it includes at least: the system comprises a vehicle machine, a vehicle-mounted data sensing device and a vehicle-mounted T-BOX. The vehicle-mounted data sensing equipment is used for sensing data of the vehicle and data of the external environment where the vehicle is located in real time.
And the vehicle-mounted T-BOX is used for data interaction of a vehicle machine, a mobile device, a road side unit and the server 130. The vehicle-mounted T-BOX comprises a SIM card, a GPS antenna, a 4G or 5G antenna and the like. When a user sends a control command (remotely starts a vehicle, opens an air conditioner, adjusts a seat to a proper position and the like) through an application program (APP) of a mobile device (such as a mobile phone), a TSP background CAN send a monitoring request command to a vehicle-mounted T-BOX, the T-BOX CAN perform data interaction with a vehicle machine, after the vehicle obtains the control command, the vehicle sends a control message through a CAN bus and realizes the control of the vehicle, and finally an operation result is fed back to the mobile phone APP of the user. Data interaction is realized between the vehicle-mounted T-BOX and the vehicle machine through canbus communication, such as vehicle state information, key state information, control instructions and the like. The vehicle-mounted T-BOX can collect bus data related to buses Dcan, Kcan and PTcan of the vehicle 110.
The vehicle 110 and the mobile device can interact and share data through wireless communication means such as Wi-Fi, Bluetooth, cellular and the like. For example, in some embodiments, after logging in the virtual key APP through the user account, the first mobile device 120 acquires the virtual key data associated with the user account from the cloud, and the first mobile device 120 first decrypts the acquired virtual key data, for example, by using a private key, to obtain a virtual key that can be shared. The virtual key data includes, for example, bluetooth information of the T-BOX, a connection key (connection key), an access key (ACCESSKEY), a key authority, a validity period, and the like. First mobile device 120 may, for example, interact with the onboard T-BOX of vehicle 110 via a predetermined application (e.g., virtual key APP) via bluetooth near field communication or via remote data interaction with server 130 (e.g., TSP). For example, the first mobile device 120 scans the BLE device through the server 130 via the virtual key APP to find the T-BOX of the vehicle 110, connects the T-BOX through the server 130 and sends a connection key (connection key), after the T-BOX confirms that the received connection key (connection key) is verified, the T-BOX parses the obtained instruction from the virtual key APP of the first mobile device 120, and if the instruction is determined to be the unlocking of the doors, the T-BOX sends an instruction for executing the unlocking to the CANBUS of the vehicle.
In some embodiments, the T-BOX may 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 (connect) is authenticated, the virtual key APP and the T-BOX encrypting the interaction data based on the access key (ACCESSKEY) and the random code in order to prevent replay attacks.
The vehicle 110 and the server 130 interact with each other in real time via wireless communication techniques, such as satellite wireless communication or mobile cellular. For example, the signal interaction between vehicle 110 to server 130 via T-BOX can be performed using the TLS1.2 standard. The T-BOX of vehicle 110 is configured at the factory with a secure identifier (i.e., Security ID) that uniquely identifies the T-BOX. Server 130 may perform authentication with the T-BOX based on the secure identifier to ensure security of data interaction.
With respect to the mobile device, it is, for example and without limitation, a cell phone. In some embodiments, the mobile device may be a tablet computer. The mobile device may interact with the onboard T-BOX directly in the near field or remotely via server 130. In addition, the first mobile device can also interact with the second mobile device 122 server 130 via the base station 150, the network 140. A predetermined application (e.g., virtual vehicle key APP) is configured at the mobile device, for example, through a predetermined action (e.g., shaking a rock) the mobile device may establish an association with the vehicle 110 and launch the predetermined application (e.g., virtual vehicle key APP). The first mobile device 120 may obtain the first voice. If the first mobile device 120 determines that the first voice is associated with authorization credentials for an associated vehicle 110 sharing the first mobile device 120, shared information may be generated based on the first voice, the shared information indicating at least an object for receiving the authorization credentials for unlocking the associated vehicle 110. The first mobile device 120 may also determine a second mobile device 122 associated with the object; and sending a sharing request to the server 130 for sharing the authorization credential with the second mobile device 122, the sharing request including at least identification information of the second mobile device 122. The second mobile device 122 may obtain a sharing link from the first mobile device 120 for sharing authorization credentials to the second mobile device 122 for unlocking the associated vehicle 110 with the first mobile device 120, the second mobile device 122 determined based on, for example, the obtained first voice at the first mobile device 120. The second mobile device 122 may present vehicle information for the associated vehicle based on the sharing link; in response to the confirmation detecting the operation on the authorization voucher, sending a pickup request to the server, wherein the server sends confirmation information on the second mobile equipment for picking up the authorization voucher to the first mobile equipment in response to the confirmation that the pickup request is verified; and if the second mobile device 122 confirms detection of information from the server 130 indicating that the authorization credential has been associated to the associated account of the second mobile device 122, presenting information indicating that the authorization credential has been shared.
With respect to server 130, it is used to provide internet of vehicles services, such as providing automotive remote services. In some embodiments, the server 130 may be a computing device, such as a server, having one or more processing units, including special purpose processing units, such as GPUs, FPGAs, and ASICs, and general purpose processing units, such as CPUs. In addition, one or more virtual machines may also be running on each computing device. In some embodiments, if the server 130 detects a query request from the first mobile device 120, the server queries authorization credentials of the associated vehicle 110 with the first mobile device 120, the authorization credentials for unlocking the associated vehicle 110; a sharing request from the first mobile device 120 to share the authorization credential with the second mobile device 122 is obtained, the sharing request including at least an identification of the second mobile device 122, and the sharing request generated based on the obtained first voice at the first mobile device 122. If the server 130 confirms that the pickup request from the second mobile device 122 is detected, it confirms whether the pickup request is authenticated; and if the server 130 confirms that the pickup request is verified, generating an associated account number for the second mobile device 122 to obtain authorization credentials based on the pickup request.
A method for information sharing according to an embodiment of the present disclosure will be described below in conjunction with fig. 2. Fig. 2 shows a flow diagram of a method 200 for information sharing according to an embodiment of the present disclosure. It should be understood that the method 200 may be performed, for example, at the electronic device 600 depicted in fig. 6. May also be performed at the first mobile device 120 depicted in fig. 1. It should be understood that method 200 may also include additional acts not shown and/or may omit acts shown, as the scope of the disclosure is not limited in this respect.
At block 202, a first mobile device 120 acquires a first voice. In some embodiments, the first mobile device 120 is for example equipped with a virtual key APP, and the virtual key APP is started when a predetermined operation (for example shaking) at the first mobile device 120 is detected. For example, the user 160 also opens the instant messaging application at the first mobile device 120 and enters the first voice in the instant messaging application. The first voice is, for example: the vehicle key is shared with Xiaoming, the use validity period of the key is 3 days, and the pickup validity period is 15 minutes.
In some embodiments, the first mobile device 120, after acquiring the first voice, may first extract voiceprint features of the first voice to confirm whether the first voice is authenticated based on the voiceprint features; if the first mobile device 120 determines that the first voice is authenticated, the first voice is converted to text to determine whether the first voice is associated with the authorization credential shared with the associated vehicle 110 of the first mobile device based on the text. In some embodiments, the voiceprint feature comprises at least one of a resonance mode feature, a voice purity feature, an average pitch feature, a range feature, for example.
The reason for adopting the above means is that the sizes and the forms of the sounding organs used by different people during speaking are greatly different, and the differences enable the voiceprint atlases of different people to be different, so that whether the first voice comes from the user 160 of the first mobile device 120 can be determined by extracting the voiceprint features, so as to accurately confirm the authenticity of the first voice, and further prevent other people from sharing the virtual key by using the first mobile device 120, thereby improving the security of authorized credential sharing.
Regarding the manner of verifying the first voice, in some embodiments, the verification manner includes, for example: the first mobile device 120 enhances the acquired first speech; it is then determined whether the quality of the first speech meets a predetermined condition. If the first mobile device 120 determines that the quality of the first voice meets a predetermined condition; then the valid speech in the first speech is extracted for voiceprint feature extraction. The first mobile device 120 then matches the extracted voiceprint features with pre-stored voiceprint features of the user 160 of the first mobile device 120. The first voice may be confirmed to be authenticated if the first mobile device 120 confirms that the extracted voiceprint features match the pre-stored voiceprint features.
In some embodiments, the manner of determining whether the first voice is associated with sharing authorization credentials for the associated vehicle 110 with the first mobile device 120 includes, for example: the first mobile device 120 identifies semantics of the first voice and confirms whether the first voice is associated with the authorization credential based on the identified semantics of the first voice. For example, if the first mobile device 120 confirms that keywords such as car and key are included in the recognized semantics at the same time, it may be determined that the first voice is associated with an authorization credential associated with the vehicle 110.
At block 204, the first mobile device 120 determines whether the first voice is associated with authorization credentials for the associated vehicle 110 sharing the first mobile device 120.
At block 206, if the first mobile device 120 determines that the first voice is associated with authorization credentials for sharing the associated vehicle 110 of the first mobile device 120, sharing information is generated based on the first voice, the sharing information indicating at least an object for receiving the authorization credentials, the authorization credentials for unlocking the vehicle.
Regarding the sharing information, in some real-time modes, the sharing information further comprises at least one of a use authorization period of the authorization certificate, a pickup period of the authorization certificate and authorization authority. For example, if the first mobile device 120 confirms that the first voice is associated with the virtual key based on the semantic meaning of the first voice, the first mobile device 120 determines information such as a sharing object of the virtual key, an authorization period of use of the virtual key, and a virtual key pickup period based on the recognized semantic meaning of the first voice.
At block 208, the first mobile device 120 determines the second mobile device 122 associated with the object.
The first mobile device 120 may determine the second mobile device 122 associated with the object in a variety of ways. In some embodiments, the first mobile device 120 queries the address book or a friend of the instant messaging application for a candidate object with high similarity to the shared object. For example, if the first mobile device 120 determines that an instant messaging application (e.g., without limitation, a WeChat) has been opened, the candidate object associated with the object is determined in an instant messaging application buddy of the instant messaging application. For example, the determined sharing object (xiaoming) is used as a key word, and the instant messaging application friend of the first mobile device 120 searches for one or more candidate objects with high similarity to the receiving object of the determined authorization credential (for example, the determined three candidate objects are respectively a micro signal, a crowing, a small name and a xiaoming). The first mobile device 120 then retrieves the second speech to identify the selected object associated with the object based on the identified semantics of the second speech. For example, if the first mobile device 120 recognizes the semantics of the acquired second speech, for example, indicate: the third candidate object is ranked, and the first mobile device 120 determines the third candidate object (e.g., the micro signal corresponding to the twilight) as the selected object.
By adopting the means, the voice of the user can be identified so as to confirm the receiving object of the virtual key, the complicated operations such as manual login or inputting the identifier of the second mobile equipment are not needed, and the sharing convenience of the authorization certificate is improved. Moreover, under some special scenes, for example, when the owner drives the vehicle, the authorization voucher is shared based on voice, and the receiving object of the authorization voucher can be conveniently identified under the condition of not interfering normal driving.
The way in which the first mobile device 120 shares the virtual key of the vehicle via the instant messaging application will be further described with reference to fig. 3, and will not be described herein again.
At block 210, the first mobile device 120 sends a sharing request to the server 130 for sharing the authorization credential with the second mobile device 120, the sharing request including at least identification information of the second mobile device.
In some embodiments, the sharing request further includes at least one of an identification of an associated user of the second mobile device 122 and an identification of an instant messaging application of the associated user, so that the server 130 verifies the pickup request from the second mobile device based on the obtained sharing request. For example, the server 130 may also verify whether the virtual key information to be retrieved matches the sharing key or the selected object of the instant messaging application based on the information in the obtained sharing request.
In the above scenario shown in fig. 2, upon confirming that the first voice is associated with the authorization credential of the associated vehicle 110, the first mobile device 120 generates shared information based on the first voice and determines the second mobile device 122 for receiving the authorization credential based on the shared information; a sharing request is then sent to the server 130 for sharing the authorization credential to the second mobile device 122, which enables the user to share the authorization credential securely, conveniently, and remotely.
In some embodiments, the method 200 may further comprise: the first mobile device 120 sends a third voice to the server 130 for the server 130 to confirm whether the pick-up request from the second mobile device 122 is authenticated based on at least one of the voiceprint features and semantics of the third voice, the third voice being obtained in advance by the first mobile device 120. In some implementations, the third voice further indicates a password for authenticating the pick-up request, and the third voice is obtained via at least one of a microphone of the first mobile device and an instant messaging application. For example, the third voice may be obtained via an instant messaging application (e.g., WeChat or telephone) at the first mobile device 120, or may be obtained through a microphone at the first mobile device 120. For example, the third voice is a voice of a user of the second mobile device 122 (e.g., a wechat buddy minuscule) receiving the virtual key obtained by wechat at the first mobile device 120. In some embodiments, the third voice is also indicative of a password for picking up the key, for example, the password is a password or a passphrase. Such as numbers, letters, keywords, or combinations thereof, of no more than four words.
After the server 130 receives the third voice from the first mobile device 120, the voiceprint feature of the third voice can be extracted; and obtaining a fourth voice from the user 162 of the second mobile device 122; it is then confirmed whether the fourth voice matches the third voice based on the voiceprint feature of the third voice. If the confirmation matches, the pickup request of the second mobile device 122 is verified, and then the server 130 generates an associated account number for the second mobile device 122 to obtain authorization credentials based on the pickup request. In some embodiments, the server 130, in addition to extracting the voiceprint features of the third voice, also identifies the semantics of the third voice to obtain a password indicated by the third voice for use in verifying the pick-up request; then, based on the voiceprint feature and the password, it is confirmed whether the fourth voice matches the third voice. By adopting the above means, the method and the device can prevent others from pretending the authorization certificate based on the voiceprint characteristics or the secret language of the receiving object of the authorization certificate, thereby improving the security of remote sharing of the authorization certificate.
In some embodiments, the third voice may also be the sound of the owner of the vehicle. For example, the car owner shares the sound with the recipient of the authorization ticket through the instant messaging application, which uses the car owner's sound to retrieve the authorization ticket.
Fig. 3 shows a flowchart of a method 300 for sharing a vehicle virtual key via an instant messaging application, in accordance with an embodiment of the present disclosure. It should be understood that the method 300 may be performed, for example, at the electronic device 600 depicted in fig. 6. May also be performed at the first mobile device 120 depicted in fig. 1. It should be understood that method 300 may also include additional acts not shown and/or may omit acts shown, as the scope of the disclosure is not limited in this respect.
At block 302, the first mobile device 120 invokes an instant messaging application Software Development Kit (SDK) interface (e.g., the wechat JS-SDK interface). For example, the first mobile device 120 may obtain the "share to friends circle" button click state and set the shared content interface in the instant messaging application and obtain the "share to friends" button click state and set the shared content interface by using the instant messaging application JS-SDK interface. For example, the first mobile device 120 may further define a callback function executed after the user confirms sharing by setting a success parameter, and define a callback function executed after the user cancels sharing by a cancel parameter.
At block 304, the first mobile device 120 simulates a screen click to send a share link to the determined selected object via the opened instant messaging application for picking up the authorization credential, the share link including at least one of a predetermined application, a two-dimensional code, and URL link information. For example, the first mobile device 120 sends an applet for sharing the virtual key of the vehicle 110 to a selected object (for example, a micro signal corresponding to the applet) determined by the aforementioned second voice through a virtual click through the instant messaging application, and indicates the virtual key information, the vehicle information of the associated vehicle 110, the shared key, the location of the vehicle 110, and the like in the shared applet.
In the above scheme shown in fig. 3, the vehicle owner can conveniently and safely share the virtual key to the instant messaging application friend through the instant messaging application opened at the first mobile device even in the driving state by using the instant messaging application SDK interface and simulating screen clicking.
Fig. 4 shows a flow diagram of a method 400 for information sharing according to an embodiment of the present disclosure. It should be understood that the method 400 may be performed, for example, at the electronic device 600 depicted in fig. 6. May also be performed at the server 130 depicted in fig. 1. It should be understood that method 400 may also include additional acts not shown and/or may omit acts shown, as the scope of the disclosure is not limited in this respect.
At block 402, if the server 130 detects a query request from the first mobile device 120, authorization credentials of the associated vehicle 110 with the first mobile device 120 are queried. The authorization credential is used to unlock the associated vehicle 110.
In some embodiments, if the server 130 detects a login request from the first mobile device 120, the server 130 first confirms whether the associated account number of the first mobile device 120 is authenticated. If the server 130 confirms that the associated account number of the first mobile device 120 is verified and receives a query request about the virtual key from the first mobile device 120, the server 130 may query the virtual key of the associated vehicle 110 bound to the associated account number of the first mobile device 120, so that the server 130 sends, to the first mobile device 120, association information of the authorization credential bound to the associated account number of the first mobile device 120, the association information including at least vehicle information of the associated vehicle 110; and the first mobile device 120 sends the sharing link to the second mobile device 122 based on the association information.
At block 404, the server 130 obtains a sharing request from the first mobile device 120 for sharing the authorization credentials with the second mobile device 122, the sharing request including at least an identification of the second mobile device 122, the sharing request generated based on the first voice obtained at the first mobile device 120.
In some embodiments, the sharing request further includes at least one of an identification of an associated user of the second mobile device 122, an identification of an instant messaging application of the associated user. For example, if the first mobile device 120 detects a pan operation, the virtual key information is displayed at the first mobile device 120. The first mobile device 120 may initiate sharing for the virtual key at the first mobile device 120 by a first voice of the user 160 in relation to the virtual key of the associated vehicle 110 or a click on the virtual key APP interface. For example, the first mobile device 120 determines the second mobile device 122 associated with the object based on the recognized semantics of the first speech; a share request is then sent to the server 130 for sharing the authorization credential to the second mobile device 122.
At block 406, the server 130 confirms whether a pickup request from the second mobile device 122 is detected.
At block 408, if the server 130 confirms that a pickup request from the second mobile device 122 is detected, it confirms whether the pickup request is authenticated. The pick-up request includes at least an identification of the second mobile device 122. In some embodiments, the pickup request further includes information such as a mobile phone number of the second mobile device, instant messaging application account information, an instant messaging application avatar, a sharing key, and the like.
Whether the pick-up request is authenticated may be confirmed in a number of ways.
In some embodiments, the server 130 may extract voiceprint features of the third voice from the first mobile device 120; then, a fourth voice from the second mobile device 122 is obtained; and then, whether the fourth voice is matched with the third voice is determined based on the voiceprint characteristics of the third voice. In some embodiments, the server 130, in addition to extracting the voiceprint features of the third voice, also identifies the semantics of the third voice to obtain the password for verifying the pick-up request indicated by the third voice; then, it is confirmed whether the fourth voice matches the third voice based on the voiceprint feature and the password. By adopting the above means, the method and the device can prevent others from pretending the authorization certificate by matching the voiceprint characteristics or the secret words of the receiving object of the authorization certificate, thereby improving the security of remote sharing of the authorization certificate.
In some embodiments, the third voice may also be the sound of the owner of the vehicle. For example, the owner may share his voice to the recipient of the authorization ticket through the instant messaging application, and the recipient may retrieve the authorization ticket by using the acquired owner's voice.
In some embodiments, the server 130 may also confirm whether the pickup request is validated, e.g., based on information indicated in the sharing request from the first mobile device 120, to match corresponding information indicated in the pickup request from the second mobile device 122. If the two respectively indicated association information match, the server 130 may confirm that the pick-up request is authenticated.
At block 410, if the server 130 confirms that the pickup request is validated, an associated account number for the second mobile device 122 to obtain authorization credentials is generated based on the pickup request.
In the above scheme shown in fig. 4, the server 130 obtains the sharing request for the authorization credentials generated based on the first voice from the first mobile device 120, obtains and verifies the pickup request from the second mobile device 122, and generates the associated account number for the second mobile device 122 to obtain the authorization credentials based on the pickup request after the pickup request passes the verification.
In some embodiments, the method 400 further comprises: if the server 130 confirms that the pickup request is authenticated, confirmation information regarding the second mobile device 122 picking up the authorization ticket is sent to the first mobile device 120 to present a confirmation prompt at the first mobile device 120. By adopting the above means for confirming the prompt information, it is convenient to prompt the user whether the sharing intention before adjustment is needed at the first mobile device 120 by the opportunity of confirming the prompt information, thereby avoiding the sharing instruction being wrong. Associating the authorization credential to the associated account of the second device 122 if the server 130 acknowledges receipt of the acknowledgement from the first mobile device 120 for the acknowledgement prompt; and send a prompt to the second mobile device 122 that the authorization credential has been shared. By adopting the means of sending the prompt message to the second mobile device, the user of the second mobile device is reminded of knowing that the virtual key is associated with the relevant account in time.
In some embodiments, the method 400 further comprises: if the server 130 confirms receipt of adjustment information from the first mobile device 120 regarding the authorization credential bound to the account associated with the second mobile device 122, an instruction matching the adjustment information is sent to the T-BOX of the associated vehicle 110, the adjustment information including at least one of permission modification information, lifetime modification information, and withdrawal information. By adopting the means, the T-BOX can be informed to adaptively manage the shared authorization voucher according to the instruction of the owner in time.
Fig. 5 shows a flow diagram of a method 500 of information sharing according to an embodiment of the present disclosure. It should be understood that the method 500 may be performed, for example, at the electronic device 600 depicted in fig. 6. May also be performed at the second mobile device 122 depicted in fig. 1. It should be understood that method 500 may also include additional acts not shown and/or may omit acts shown, as the scope of the disclosure is not limited in this respect.
At block 502, the second mobile device 122 obtains a sharing link from the first mobile device 120 for sharing authorization credentials to the second mobile device 122, the authorization credentials for unlocking the associated vehicle 110 of the first mobile device 120, the second mobile device 122 determined based on the obtained first voice at the first mobile device 120.
In some embodiments, the sharing link includes at least one of a predetermined application, a two-dimensional code, and URL link information. In some embodiments, the second mobile device 122 may receive, through the instant messaging application, a sharing link sent by the user 160 of the first mobile device 120 as a buddy of the instant messaging application to share the authorization credential with the user 162 of the second mobile device 122.
At block 504, the second mobile device 122 may present vehicle information of the vehicle based on the sharing link.
In some embodiments, the vehicle information presented includes, for example, vehicle location, license plate number, and the like. For example, the sharing link is an applet that is shared through an instant messaging application, for example. Based on the applet, information such as the vehicle location, license plate number, etc. of vehicle 110 may be displayed at second mobile device 122. In some embodiments, the interface of the applet is operable, for example.
At block 506, the second mobile device 122 confirms whether an operation with respect to the authorization credential was detected.
At block 508, if the second mobile device 122 confirms detection of the operation with respect to the authorization credential, a pickup request is sent to the server 130 for the server 130 to send confirmation information to the first mobile device 120 that the second mobile device 122 picks up the authorization credential upon confirming that the pickup request is authenticated.
In some embodiments, second mobile device 122 obtains the fourth voice via at least one of a microphone and an instant messaging application of second mobile device 122; the fourth voice is then sent to the server 130 for the server 130 to authenticate the pick-up request.
At block 510, if the second mobile device 122 confirms whether information from the server 130 indicating that authorization credentials have been associated to the associated account of the second mobile device 122 is detected.
At block 512, if the second mobile device 122 confirms detection of information from the server 130 indicating that the authorization credential has been associated to the associated account of the second mobile device 122, information indicating that the authorization credential has been shared is presented. The authorization ticket includes identification information of the T-BOX of the vehicle.
In some embodiments, the virtual key associated with the associated account of second mobile device 122 is generated by the T-BOX of vehicle 110 and is different from the virtual key to which the associated account of first mobile device 120 is bound.
In some embodiments, after second mobile device 122 logs into virtual key APP, the virtual key bound to the associated account of second mobile device 122 may be obtained.
After the second mobile device 122 CAN perform encrypted communication with the T-BOX of the vehicle 110 based on the virtual key, the T-BOX of the vehicle 110 performs data interaction with the CAN bus, so as to support the second mobile device 122 to perform a vehicle control function within a control range matched with the preset authority of the virtual key.
In the above scenario shown in fig. 5, by sending a pick-up request based on the second mobile device 120 determined based on the first voice obtained at the first mobile device 120 and based on the sharing link received by the second mobile device 120, and indicating information that the authorization ticket has been shared when the authorization ticket has been associated to the associated account of the second mobile device 122, the present disclosure enables secure, convenient and remote acquisition of the shared authorization ticket.
FIG. 6 schematically illustrates a block diagram of an electronic device 600 suitable for use in implementing embodiments of the present disclosure. The device 600 may be a device for implementing the methods 200, 300, 400 and 500 shown in fig. 2 to 5. As shown in fig. 6, device 600 includes a Central Processing Unit (CPU)601 that may perform various appropriate actions and processes in accordance with computer program instructions stored in a Read Only Memory (ROM)602 or loaded from a storage unit 608 into a Random Access Memory (RAM) 603. In the RAM603, various programs and data required for the operation of the device 600 can also be stored. The CPU 601, ROM 602, and RAM603 are connected to each other via a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.
A number of components in the device 600 are connected to the I/O interface 605, including: an input unit 606, an output unit 607, a storage unit 608, a processing unit 601 performs the various methods and processes described above, for example performing the methods 200, 300, 400 and 500. For example, in some embodiments, the methods 200, 300, 400, and 500 may be implemented as a computer software program stored on a machine-readable medium, such as the storage unit 608. In some embodiments, part or all of the computer program may be loaded and/or installed onto the device 600 via the ROM 602 and/or the communication unit 609. When the computer program is loaded into RAM603 and executed by CPU 601, one or more of the operations of methods 200, 300, 400, and 500 described above may be performed. Alternatively, in other embodiments, CPU 601 may be configured by any other suitable means (e.g., by way of firmware) to perform one or more acts of methods 200, 300, 400, and 500.
It should be further appreciated that the present disclosure may be embodied as methods, apparatus, systems, and/or computer program products. The computer program product may include a computer-readable storage medium having computer-readable program instructions embodied thereon for carrying out various aspects of the present disclosure.
The computer readable storage medium may be a tangible device that can hold and store the instructions for use by the instruction execution device. The computer readable storage medium may be, for example, but not limited to, an electronic memory device, a magnetic memory device, an optical memory device, an electromagnetic memory device, a semiconductor memory device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a Static Random Access Memory (SRAM), a portable compact disc read-only memory (CD-ROM), a Digital Versatile Disc (DVD), a memory stick, a floppy disk, a mechanical coding device, such as punch cards or in-groove projection structures having instructions stored thereon, and any suitable combination of the foregoing. Computer-readable storage media as used herein is not to be construed as transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission medium (e.g., optical pulses through a fiber optic cable), or electrical signals transmitted through electrical wires.
The computer-readable program instructions described herein may be downloaded from a computer-readable storage medium to a respective computing/processing device, or to an external computer or external storage device via 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. The network adapter card or 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 the respective computing/processing device.
The computer program instructions for carrying out operations of the present disclosure may be assembler instructions, Instruction Set Architecture (ISA) instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The 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. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider). In some embodiments, the electronic circuitry that can execute the computer-readable program instructions implements aspects of the present disclosure by utilizing the state information of the computer-readable program instructions to personalize the electronic circuitry, such as a programmable logic circuit, a Field Programmable Gate Array (FPGA), or a Programmable Logic Array (PLA).
Various 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 will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-readable program instructions.
These computer-readable program instructions may be provided to a processor in a voice interaction device, a processing unit of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processing unit of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer-readable program instructions may also be stored in a computer-readable storage medium that can direct a computer, programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer-readable medium storing the instructions comprises an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer, other programmable apparatus or other devices implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
Having described embodiments of the present disclosure, the foregoing description is intended to be exemplary, not exhaustive, and not limited to the disclosed embodiments. Many modifications and variations 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 in order to best explain the principles of the embodiments, the practical application, or improvements made to the technology in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.
The above are only alternative embodiments of the present disclosure and are not intended to limit the present disclosure, which may be modified and varied by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present disclosure should be included in the protection scope of the present disclosure.