Detailed Description
So that the manner in which the features and elements of the disclosed embodiments can be understood in detail, a more particular description of the disclosed embodiments, briefly summarized above, may be had by reference to the embodiments, some of which are illustrated in the appended drawings. In the following description of the technology, for purposes of explanation, numerous details are set forth in order to provide a thorough understanding of the disclosed embodiments. However, one or more embodiments may be practiced without these details. In other instances, well-known structures and devices may be shown in simplified form in order to simplify the drawing.
In the present disclosure, a mobile device includes, but is not limited to, a personal digital assistant, a mobile computing device, a smart phone, a cellular phone, a cell phone, a one-way pager, a two-way pager, a messaging device, a computer, a personal computer, a desktop computer, a laptop computer, a notebook computer, a handheld computer, a workstation, a minicomputer, a mainframe computer, a supercomputer, a network appliance, a consumer electronics product, a programmable consumer electronics product.
For example, a mobile device may include: the charging device comprises a charging slot, a data communication line connected with the charging slot, a control chip connected with the data communication line, a communication module connected with the control chip, a GPS module connected with the control chip and a battery. For example, the mobile device may include a fingerprint recognition module and a voice prompt module for recognizing a user's fingerprint, and the like. For example, the mobile device may be shaped like a car key.
In the disclosed embodiments, the mobile device communicates with the vehicle, including communicating in a wired communication manner and communicating in a wireless communication manner. For example, the mobile device communicates with the vehicle through a USB interface.
Fig. 1 is a schematic flow chart diagram of a method for vehicle sharing provided by an embodiment of the present disclosure.
In this embodiment, the method for vehicle sharing is applied to a mobile device, and the method for vehicle sharing includes:
step S101, sending verification information to the vehicle, wherein the verification information comprises the mobile equipment ID and the user ID.
The mobile device ID can be divided into two parts, one part is an authorized general part, and the other part is a unique identifier of one mobile device.
And S102, receiving a verification result fed back by the vehicle, wherein the verification result comprises a verification result of the mobile equipment and a verification result of the user.
And step S103, entering a driving mode when the verification result of the mobile equipment and the verification result of the user are both verified.
The mobile equipment directly sends verification information to the vehicle, the vehicle verifies the verification information, and the vehicle can enter a driving mode after the verification is passed. In the process of entering the driving mode, the participation of the internet is not needed, the dependence of the process of using the shared vehicle on the internet is reduced, and the shared vehicle is convenient to use when networking is unavailable.
Fig. 2 is a schematic flow chart illustrating the process of sending the verification information and receiving the feedback result according to the embodiment of the disclosure.
In this embodiment, sending the verification information to the vehicle and receiving the verification result fed back by the vehicle includes:
step S201, sending the mobile device ID and receiving the authentication result of the mobile device.
Optionally, the authentication result of the mobile device is an authentication result obtained by authenticating the generic part, or the authentication result of the mobile device is an authentication result obtained by authenticating the unique identifier, or the authentication result of the mobile device is an authentication result obtained by authenticating the generic part and the unique identifier.
Step S202, when the verification result of the mobile device is that the verification is passed, the user ID is sent and the verification result of the user is received.
The mobile equipment ID can be verified to judge whether the mobile equipment is authorized mobile equipment or not, the user ID can be verified to judge whether the user is a legal user or not, the mobile equipment ID and the user ID are verified respectively, and the verification accuracy is improved.
Optionally, the authentication result of the user is an authentication result obtained by authenticating the user ID, or the authentication result of the user is an authentication result obtained by authenticating a binding relationship between the user ID and the mobile device ID.
Fig. 3 is a schematic flow chart illustrating sending of authentication information and receiving of a feedback result according to an embodiment of the present disclosure.
In this embodiment, sending the verification information to the vehicle and receiving the verification result fed back by the vehicle includes:
step S301, sending the mobile device ID and receiving the verification result of the mobile device.
Wherein the authentication result of the mobile device is an authentication result obtained by authenticating a generic part of the mobile device ID.
Step S302, when the verification result of the mobile device is that the verification is passed, the historical data is synchronized, the user ID is sent, and the verification result of the user is received.
And history data is synchronized, and the user ID is verified by using the synchronized data, so that the accuracy of a verification result can be improved.
Optionally, synchronizing the historical data comprises: synchronizing an authorized mobile device ID and an authorized user ID; alternatively, historical trip information is synchronized.
The ID of the authorized mobile equipment and the ID of the authorized user are synchronized, and then the ID of the user is verified based on the synchronized data, so that the accuracy of the verification result can be improved.
Optionally, synchronizing historical data, comprising: the method includes obtaining a first most recent synchronization time point of historical data on the mobile device, obtaining a second most recent synchronization time point of historical data on the vehicle, comparing the first most recent synchronization time point and the second most recent synchronization time point, selecting a latest historical data among the historical data on the mobile device and the historical data on the vehicle, and overwriting another historical data with the latest historical data.
In some application scenarios, the user registers a user ID on the mobile device, and the mobile device ID and the user ID are authorized. After the user is registered, before the mobile device and the vehicle communicate, if the vehicle is not connected with the internet and history data are synchronized, the database of the vehicle does not have the information of the user ID, at this time, the history data are synchronized, the history data on the mobile device are the latest history data, the history data on the mobile device are covered by the history data on the vehicle, then the history data on the vehicle have the authorization information of the mobile device ID and the user ID, and at this time, the user can successfully unlock the vehicle through the mobile device.
The historical data is synchronized, so that the historical database on the vehicle or the historical database on the mobile device is in a relatively new state, and a relatively accurate verification result can be obtained when networking is unavailable.
Optionally, entering a driving mode comprising:
recording the travel information, and uploading the travel information when the networking is successful; or,
and uploading historical travel information when networking is successful.
After uploading the trip information or historical trip information, management of the shared vehicles is facilitated, such as settlement of fees.
The travel information can be recorded and uploaded through the mobile equipment, and can also be recorded and uploaded through the vehicle.
Fig. 4 is a schematic flowchart of a method for vehicle sharing provided by an embodiment of the present disclosure.
In this embodiment, the method for vehicle sharing is applied to a vehicle, and the method for vehicle sharing includes:
step S401, receiving verification information sent by mobile equipment, wherein the verification information comprises a mobile equipment ID and a user ID;
step S402, obtaining the verification result of the verification information, wherein the verification result comprises the verification result of the mobile equipment and the verification result of the user;
step S403, feeding back a verification result to the mobile equipment;
and S404, entering a driving mode when the verification result of the mobile equipment and the verification result of the user are both verified.
The mobile equipment directly sends verification information to the vehicle, the vehicle verifies the verification information, and the vehicle can enter a driving mode after the verification is passed. In the process of entering the driving mode, the participation of the internet is not needed, the dependence of the process of using the shared vehicle on the internet is reduced, and the shared vehicle is convenient to use when networking is unavailable.
Fig. 5 is a schematic flow chart of receiving authentication information and feeding back an authentication result according to an embodiment of the present disclosure.
In this embodiment, receiving authentication information sent by a mobile device, obtaining an authentication result of the authentication information, and feeding back the authentication result to the mobile device includes:
step S501, receiving the ID of the mobile device, obtaining the verification result of the mobile device, and feeding back the verification result of the mobile device to the mobile device.
The mobile device ID can be divided into two parts, one part is an authorized general part, and the other part is a unique identifier of one mobile device. The verification result is a verification result of a general part of the mobile device ID, or the verification result is a verification result of a unique identifier of the mobile device ID, or the verification result is a verification result of the complete mobile device ID.
Step S502, when the verification result of the mobile equipment is passing verification, receiving the user ID, obtaining the verification result of the user, and feeding back the verification result of the user to the mobile equipment.
The mobile equipment ID can be verified to judge whether the mobile equipment is authorized mobile equipment or not, the user ID can be verified to judge whether the user is a legal user or not, the mobile equipment ID and the user ID are verified respectively, and the verification accuracy is improved.
The verification result of the user is the verification result of the user ID, or the verification result of the user is the verification result of the binding relationship between the user ID and the mobile device ID.
Fig. 6 is a schematic flowchart of receiving authentication information and feeding back an authentication result according to an embodiment of the present disclosure.
In this embodiment, receiving authentication information sent by a mobile device, obtaining an authentication result of the authentication information, and feeding back the authentication result to the mobile device includes:
step S601, receiving the ID of the mobile device, obtaining the verification result of the mobile device, and feeding back the verification result of the mobile device to the mobile device.
Wherein the verification result of the mobile device is the verification result of the universal part of the mobile device ID.
Step S602, when the verification result of the mobile device is that the verification is passed, the historical data is synchronized, the user ID is received, the verification result of the user is obtained based on the synchronized historical data, and the verification result of the user is fed back to the mobile device.
Historical data are synchronized, and the user ID is verified by using the synchronized data, so that the accuracy of the verification result can be improved. The verification result of the user is the verification result of the user ID, or the verification result of the user is the verification result of the binding relationship between the user ID and the mobile device ID.
Optionally, synchronizing historical data on the vehicle, comprising: synchronizing an authorized mobile device ID and an authorized user ID; alternatively, historical trip information is synchronized. The ID of the authorized mobile equipment and the ID of the authorized user are synchronized, and then the ID of the user is verified based on the synchronized data, so that the accuracy of the verification result can be improved.
Optionally, the vehicle enters a trip mode comprising: recording the travel information, and uploading the travel information when the networking is successful; alternatively, historical trip information is uploaded when networking is successful. After uploading the trip information or historical trip information, management of shared vehicles, such as settlement of fees, is facilitated.
The journey information can be recorded and uploaded through the vehicle, and the journey information can also be uploaded through the mobile device.
Fig. 7 is a schematic flow chart diagram of a method for vehicle sharing provided by an embodiment of the present disclosure.
In this embodiment, a method for vehicle sharing includes:
step S701, the mobile equipment sends a mobile equipment ID to the vehicle;
step S702, the vehicle verifies the universal part of the mobile equipment ID, and obtains and feeds back the verification result of the mobile equipment;
step S703, synchronizing the historical data of the mobile equipment and the vehicle when the verification result of the mobile equipment is that the verification is passed;
Step S704, the mobile device sends a user ID to the vehicle, the vehicle verifies the user ID, or the vehicle verifies the binding relationship between the user ID and the mobile device ID, and the verification result of the user is obtained and fed back;
step S705, when the authentication result of the user is the pass authentication, the mobile device and the vehicle enter the driving mode.
Fig. 8 is a schematic diagram of an apparatus for vehicle sharing provided by an embodiment of the present disclosure.
In this embodiment, the apparatus for vehicle sharing includes:
a processor (processor)81 and a memory (memory)82, and may further include a Communication Interface 83 and a bus 84. The processor 81, the communication interface 83 and the memory 82 may communicate with each other through the bus 84. The communication interface 83 may be used for information transfer. The processor 81 may invoke logic instructions in the memory 82 to perform the method for vehicle sharing of the above-described embodiment.
Furthermore, the logic instructions in the memory 82 may be implemented in software functional units and stored in a computer readable storage medium when sold or used as a stand-alone product.
The memory 82 is a computer-readable storage medium, and can be used for storing software programs, computer-executable programs, such as program instructions/modules corresponding to the methods in the embodiments of the present disclosure. The processor 81 executes the functional application and data processing by executing the software program, instructions and modules stored in the memory 82, that is, implements the method in the above-described method embodiment.
The memory 82 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to the use of the terminal device, and the like. Further, the memory 82 may include high speed random access memory and may also include non-volatile memory.
The embodiment of the disclosure provides a mobile device.
In some embodiments, the mobile device comprises a processor and a memory storing program instructions, the processor being configured, when executing the program instructions, to perform the method for vehicle sharing provided by the aforementioned embodiments.
The disclosed embodiment provides a vehicle.
In some embodiments, a vehicle comprises a processor and a memory storing program instructions, the processor being configured, upon execution of the program instructions, to perform the foregoing implementations provide a method for vehicle sharing.
The disclosed embodiments provide a computer-readable storage medium storing computer-executable instructions configured to perform the method for vehicle sharing provided by the above embodiments.
Embodiments of the present disclosure provide a computer program product comprising a computer program stored on a computer readable storage medium, the computer program comprising program instructions which, when executed by a computer, cause the computer to perform the method for vehicle sharing provided by the above embodiments.
The computer-readable storage medium described above may be a transitory computer-readable storage medium or a non-transitory computer-readable storage medium.
The technical solution of the embodiments of the present disclosure may be embodied in the form of a software product, where the computer software product is stored in a storage medium and includes one or more instructions to enable a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method in the embodiments of the present disclosure. And the aforementioned storage medium may be a non-transitory storage medium comprising: various media capable of storing program codes, such as a usb disk, a removable hard disk, a ROM, (Read-Only Memory), a RAM (Random Access Memory), a magnetic disk, or an optical disk, may also be transient storage media.
The above description and drawings sufficiently illustrate embodiments of the disclosure to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. The examples merely typify possible variations. Individual components and functions are optional unless explicitly required, and the sequence of operations may vary. Portions and features of some embodiments may be included in or substituted for those of others. The scope of the disclosed embodiments includes the full ambit of the claims, as well as all available equivalents of the claims. As used in this application, although the terms "first," "second," etc. may be used in this application to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element, unless the meaning of the description changes, so long as all occurrences of the "first element" are renamed consistently and all occurrences of the "second element" are renamed consistently. The first and second elements are both elements, but may not be the same element. Furthermore, the words used in the specification are words of description only and are not intended to limit the claims. As used in the description of the embodiments and the claims, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. Similarly, the term "and/or" as used in this application is meant to encompass any and all possible combinations of one or more of the associated listed. Furthermore, the terms "comprises" and/or "comprising," when used in this application, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method or device comprising the element. In this document, each embodiment may be described with emphasis on differences from other embodiments, and the same and similar parts between the respective embodiments may be referred to each other. For methods, products, etc. of the embodiment disclosures, reference may be made to the description of the method section for relevance if it corresponds to the method section of the embodiment disclosure.
Those of skill in the art would appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software may depend upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosed embodiments. It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the system, the apparatus and the unit described above may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the embodiments disclosed herein, the disclosed methods, products (including but not limited to devices, apparatuses, etc.) may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, a division of a unit may be merely a division of a logical function, and an actual implementation may have another division, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form. Units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to implement the present embodiment. In addition, functional units in the embodiments of the present disclosure may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, 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. 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 special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.