CN114928639B - Information management system - Google Patents

Information management system Download PDF

Info

Publication number
CN114928639B
CN114928639B CN202210429715.3A CN202210429715A CN114928639B CN 114928639 B CN114928639 B CN 114928639B CN 202210429715 A CN202210429715 A CN 202210429715A CN 114928639 B CN114928639 B CN 114928639B
Authority
CN
China
Prior art keywords
vehicle
information
user
request
account
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202210429715.3A
Other languages
Chinese (zh)
Other versions
CN114928639A (en
Inventor
张银友
林杰
秦诚
魏星
王健
赵德银
张东波
刘晔
周时莹
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
FAW Group Corp
Original Assignee
FAW Group Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by FAW Group Corp filed Critical FAW Group Corp
Priority to CN202210429715.3A priority Critical patent/CN114928639B/en
Publication of CN114928639A publication Critical patent/CN114928639A/en
Application granted granted Critical
Publication of CN114928639B publication Critical patent/CN114928639B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G06Q30/0645—Rental transactions; Leasing transactions
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00—Registering or indicating the working of vehicles
    • G07C5/008—Registering or indicating the working of vehicles communicating information to a remotely located station
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00—Registering or indicating the working of vehicles
    • G07C5/08—Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
    • G07C5/0841—Registering performance data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks

Abstract

The embodiment of the disclosure discloses an information management system, comprising: the management terminal is in communication connection with the cloud server; the management terminal is used for sending an information management request to the cloud server; the cloud server is used for receiving the information management request sent by the management terminal so as to manage account information corresponding to a plurality of vehicle users according to the information management request.

Description

Information management system
Technical Field
The embodiment of the disclosure relates to the technical field of Internet of vehicles, in particular to an information management system.
Background
Automobiles are the most important travel tools for people nowadays, and with the development of technology, the authority of users, usage records and other data can be managed through locomotive accounts.
At present, the locomotive account management scheme mainly aims at personal users, and cannot manage the multi-user accounts in a multi-user vehicle scene.
Disclosure of Invention
The embodiment of the disclosure provides an information management system for managing account information corresponding to a plurality of vehicle users.
The embodiment of the disclosure provides an information management system, comprising: the management terminal is in communication connection with the cloud server;
the management terminal is used for sending an information management request to the cloud server;
the cloud server is used for receiving the information management request sent by the management terminal and managing account information corresponding to a plurality of vehicle users according to the information management request.
Further, the information management request includes a registration request;
the cloud server is further configured to:
and receiving a registration request sent by the management terminal, wherein the registration request comprises a vehicle identifier, judging whether a vehicle corresponding to the vehicle identifier is registered or not based on the vehicle identifier, receiving user uploading information sent by the management terminal when the vehicle is in an unregistered state, and registering a vehicle management account based on the user uploading information, wherein the vehicle management account is used for logging in the management terminal so as to manage account information corresponding to a plurality of vehicle users.
Further, the information management request includes an information replacement request;
the cloud server is further configured to:
receiving an information replacement request sent by the management terminal and sending a replacement confirmation request to the original vehicle management terminal under the condition that the vehicle is in a registration state;
and under the condition that the information fed back by the original vehicle management terminal is the replacement approval, receiving the user replacement information sent by the management terminal so as to complete the replacement of the vehicle management account information.
Further, the cloud server is further configured to:
acquiring a vehicle identifier from a vehicle registration database and verification information corresponding to the vehicle identifier;
and comparing the verification information corresponding to the vehicle identification obtained from the vehicle registration database with the vehicle identification and the verification information in the user replacement information to verify the validity of the vehicle replacement information.
Further, the management terminal is further configured to:
acquiring user information, and generating a user newly-added request based on the user information; or receiving a registration authorization request sent by the vehicle-mounted terminal, displaying, receiving response information to the registration authorization request, and generating a user newly-added request based on user information in the registration authorization request when the response information is authorization registration;
and sending the user newly-added request to a cloud server.
Further, the cloud server is further configured to:
receiving a user newly-added request sent by a management terminal, wherein the user newly-added request comprises user information;
judging whether the vehicle user registers an account or not based on the user information, and sending first verification information to the user terminal and receiving second verification information fed back by the management terminal under the condition that the vehicle user does not register the account;
if the first verification information is the same as the second verification information, completing the registration of the vehicle user account;
vehicle use information sent by the vehicle-mounted terminal registered with different vehicle user accounts is received, and the vehicle use information corresponding to a plurality of vehicle users is stored.
Further, the cloud server is further configured to:
receiving an account login request sent by a vehicle-mounted terminal, wherein the account login request comprises a user identifier;
under the condition that the account login request meets login conditions, calling vehicle use information based on the user identification;
and sending the vehicle use information to the vehicle-mounted terminal, wherein the vehicle-mounted terminal is used for adjusting the state of the vehicle equipment according to the vehicle use information so as to meet the vehicle use habit of a user.
Further, the cloud server is further configured to:
sending a registration authorization request to the management terminal under the condition that the account login request does not meet the login condition;
and under the condition that the management terminal agrees to the registration of the user, information verification is carried out to finish the registration of the user account.
Further, the cloud server is further configured to:
sending third verification information to a user terminal, and receiving fourth verification information fed back by the management terminal;
and if the third verification information is the same as the fourth verification information, the vehicle user account registration is successful.
Further, the management terminal is further configured to:
the method comprises the steps of sending a request for checking vehicle use data to a cloud server, and receiving the vehicle use data fed back by the cloud server, wherein the vehicle use data comprise vehicle oil consumption, driving mileage and running time.
According to the technical scheme, the management terminal can send an information management request to the cloud server; the cloud server is used for receiving the information management request sent by the management terminal, and managing account information corresponding to a plurality of vehicle users according to the information management request so as to manage the account information corresponding to the plurality of vehicle users.
Drawings
The above and other features, advantages, and aspects of embodiments of the present disclosure will become more apparent by reference to the following detailed description when taken in conjunction with the accompanying drawings. The same or similar reference numbers will be used throughout the drawings to refer to the same or like elements. It should be understood that the figures are schematic and that elements and components are not necessarily drawn to scale.
Fig. 1 is a schematic structural diagram of an information management system according to a first embodiment of the present disclosure;
FIG. 2 is a schematic diagram of a vehicle management account registration process according to an embodiment of the present disclosure;
fig. 3 is a schematic structural diagram of an information management system according to a second embodiment of the present disclosure;
fig. 4 is a schematic diagram of a flow of a newly added user account of a vehicle according to a second embodiment of the disclosure;
fig. 5 is a schematic diagram of a flow of a new user account of a vehicle according to a second embodiment of the disclosure.
Detailed Description
Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure have been shown in the accompanying drawings, it is to be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are for illustration purposes only and are not intended to limit the scope of the present disclosure.
It should be understood that the various steps recited in the method embodiments of the present disclosure may be performed in a different order and/or performed in parallel. Furthermore, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the present disclosure is not limited in this respect.
The term "including" and variations thereof as used herein are intended to be open-ended, i.e., including, but not limited to. The term "based on" is based at least in part on. The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments. Related definitions of other terms will be given in the description below.
It should be noted that the terms "first," "second," and the like in this disclosure are merely used to distinguish between different devices, modules, or units and are not used to define an order or interdependence of functions performed by the devices, modules, or units.
It should be noted that references to "one", "a plurality" and "a plurality" in this disclosure are intended to be illustrative rather than limiting, and those of ordinary skill in the art will appreciate that "one or more" is intended to be understood as "one or more" unless the context clearly indicates otherwise.
Example 1
Fig. 1 is a schematic structural diagram of an information management system according to an embodiment of the present disclosure, which is suitable for a situation of managing account information of multiple vehicle users. As shown in fig. 1, the system of the present embodiment includes: the management terminal 110 and the cloud server 120, the management terminal 110 is in communication connection with the cloud server 120.
In the embodiment of the present disclosure, the management terminal 110 refers to a device installed with software for managing a vehicle account, which may include, but is not limited to, an electronic device such as a mobile phone, a tablet computer, or a personal computer. For example, the information management request may be generated by touching or clicking a corresponding button on the display interface of the management terminal 110, and the information management request may be transmitted to the cloud server 120. The information management request refers to one or more requests for managing vehicle account information, wherein the vehicle account may include a vehicle user account, which refers to a driver of the vehicle, such as a vehicle rental customer, etc., and a vehicle manager account, which refers to a manager of the vehicle, such as a manager of a car rental company, etc. The communication connection manner between the management terminal 110 and the cloud server 120 includes wireless connection and wired connection, which is not limited herein. The cloud server 120 may be configured to receive an information management request sent by the management terminal 110, where the cloud server 120 may manage account information corresponding to a plurality of vehicle users according to the information management request, so as to satisfy a travel requirement of the user.
By way of example, the vehicle management account can be registered, the vehicle management account can be changed, the vehicle user account can be added, the vehicle use information associated with the account can be called, and the like, so that account information corresponding to a plurality of vehicle users can be managed, and travel demands of users can be met.
On the basis of the above embodiments, the information management request includes a registration request; cloud server 120 is also configured to: receiving a registration request sent by the management terminal 110, wherein the registration request includes a vehicle identifier, judging whether a vehicle corresponding to the vehicle identifier is registered based on the vehicle identifier, and receiving user uploading information sent by the management terminal 110 when the vehicle is in an unregistered state, and registering a vehicle management account based on the user uploading information, wherein the vehicle management account is used for logging in to the management terminal 110 to manage account information corresponding to a plurality of vehicle users.
Wherein the registration request refers to a registration request of the vehicle manager account. The registration request may include a vehicle identification. The vehicle identification refers to information that can be used to identify a vehicle, with uniqueness. For example, the vehicle identification may be a vehicle VIN number. The user upload information may include, but is not limited to, vehicle authentication information and manager user information. The vehicle verification information may include, but is not limited to, a vehicle owner, which may be a company name, and a travel license photograph. The administrator user information may include, but is not limited to, administrator name, identification card number, cell phone number, and the like.
For example, as shown in fig. 2, the vehicle manager may initiate a vehicle manager account registration procedure at the management terminal 110, and after the management terminal 110 inputs the vehicle VIN code, initiate a registration request to the cloud server 120; the cloud server 120 determines whether the VIN code in the registration request exists in the database, that is, determines whether the vehicle is registered for activation, and if the VIN code exists in the database, indicates that the vehicle is registered; if the VIN code does not exist in the database, it indicates that the vehicle is not registered, and further, the management terminal 110 may upload the vehicle verification information and the manager user information to complete registration of the vehicle management account. It is understood that the vehicle management account has authority to manage the user account, and can manage account information corresponding to a plurality of vehicle users.
In some embodiments, after receiving the user upload information sent by the management terminal 110, the cloud server 120 may further receive a verification code sent by the management terminal 110, and if the verification code is correct, the registration is successful, so as to generate the vehicle management account.
On the basis of the above embodiments, the information management request includes an information exchange request; cloud server 120 is also configured to: when the vehicle is in a registered state, receiving an information replacement request sent by the management terminal 110, and sending a replacement confirmation request to the original vehicle management terminal; and receiving user replacement information sent by the management terminal 110 to complete replacement of the vehicle management account information under the condition that the information fed back by the original vehicle management terminal is replacement approval.
For example, in the case that the vehicle is in the registration state, the display interface of the management terminal 110 may display operation buttons for replacing the vehicle owner, replacing the vehicle management user, and the like, after the user clicks, the corresponding information replacement request is sent to the cloud server 120, and a replacement confirmation request is sent to the original vehicle management terminal, and in the case that the information fed back by the original vehicle management terminal is the replacement approval, the user replacement information sent by the management terminal 110 is received, where the user replacement information may include, but is not limited to, vehicle verification information and manager user information, so as to complete the replacement of the vehicle management account information.
Based on the above embodiments, the cloud server 120 is further configured to: acquiring a vehicle identifier from a vehicle registration database and verification information corresponding to the vehicle identifier; and comparing the verification information corresponding to the vehicle identification obtained from the vehicle registration database with the vehicle identification and the verification information in the user replacement information to verify the validity of the vehicle replacement information.
The vehicle registration database refers to a database storing vehicle identification and verification information, and may be, for example, a national vehicle registration database or a local vehicle database, which is not limited herein. The verification information is used for verifying the validity of the information.
For example, when the information fed back by the original vehicle management terminal is that the vehicle is approved to be replaced, the vehicle VIN code and the verification information corresponding to the vehicle VIN code are acquired from the national vehicle registration database and are compared with the vehicle VIN code and the verification information in the user replacement information, if the vehicle VIN code and the verification information are identical, the vehicle information can be replaced through verification, if the vehicle VIN code and the verification information are not identical, the verification is not passed, the vehicle information replacement fails, and the correctness of the vehicle replacement information is ensured.
According to the technical scheme, the management terminal can send an information management request to the cloud server; the cloud server is used for receiving the information management request sent by the management terminal, and managing account information corresponding to a plurality of vehicle users according to the information management request so as to manage the account information corresponding to the plurality of vehicle users.
Example two
Referring to fig. 3, fig. 3 is a schematic structural diagram of an information management system according to an embodiment of the present disclosure, where the system according to the present embodiment may be combined with each of the alternatives in the information management system provided in the foregoing embodiment. The information management system provided in this embodiment is further optimized. Optionally, the management terminal 110 is further configured to: acquiring user information, and generating a user newly-added request based on the user information; or, receiving a registration authorization request sent by the vehicle-mounted terminal 130, displaying, receiving response information to the registration authorization request, and generating a user newly-added request based on user information in the registration authorization request when the response information is authorization registration; and sending the user newly-added request to the cloud server 120.
The user information may be input through the management terminal 110 on the display interface, and the user information may include, but is not limited to, a name, an identification card number, a mobile phone number, etc. of the vehicle user.
Illustratively, the management terminal 110 may fill in user information through the interface of the newly added user and package the newly added user information into a newly added user request; or, the management terminal 110 receives the registration authorization request sent by the vehicle-mounted terminal 130 and displays the registration authorization request on the display interface, and the manager can choose to grant the authorization registration or disallow the authorization registration. In the case where the management terminal 110 agrees to authorize registration, a user new request may be generated according to user information in the registration authorization request, where the user information may include a name, an identification card number, a mobile phone number, and the like, and the user new request is sent to the cloud server 120 to complete registration of the user account.
Based on the above embodiments, the cloud server 120 is further configured to: receiving a user adding request sent by the management terminal 110, wherein the user adding request comprises user information; judging whether the vehicle user has registered an account based on the user information, and sending first verification information to the user terminal and receiving second verification information fed back by the management terminal 110 under the condition that the vehicle user has not registered the account; if the first verification information is the same as the second verification information, completing the registration of the vehicle user account; vehicle usage information transmitted from the in-vehicle terminal 130 having different vehicle user accounts registered therein is received, and vehicle usage information corresponding to a plurality of vehicle users is stored.
Wherein the first authentication information and the second authentication information refer to information for authenticating the identity of the user. For example, the first authentication information and the second authentication information may be authentication codes.
As shown in fig. 4, fig. 4 is a schematic flow chart of a new user account of a vehicle, and after the vehicle manager account logs in the management terminal 110, a request is initiated on the interface of the new user to fill in user information: name, ID card number, mobile phone number; after receiving the new user adding request, the cloud server 120 determines whether user information exists in the database, if so, the cloud server indicates that the user is registered, and prompts the user to exist; if not, sending a verification code to the user terminal; the management terminal 110 fills in the verification code and feeds back the verification code to the cloud server 120, and the cloud server 120 completes the registration of the vehicle user account after receiving the correct verification code.
It should be noted that the vehicle user account is bound under the vehicle manager account and is managed by the vehicle manager account. The vehicle user account can be logged in to the vehicle-mounted terminal 130, the vehicle-mounted terminal 130 can send the vehicle use information in the login time period of the vehicle user account to the cloud server 120, and the cloud server 120 can receive the vehicle use information sent by the vehicle-mounted terminal 130 logged in with different vehicle user accounts and independently store the vehicle use information corresponding to a plurality of vehicle users so as to quickly call according to the user accounts.
Based on the above embodiments, the cloud server 120 is further configured to: receiving an account login request sent by the vehicle-mounted terminal 130, wherein the account login request comprises a user identifier; under the condition that the account login request meets login conditions, calling vehicle use information based on the user identification; the vehicle usage information is sent to the vehicle-mounted terminal 130, and the vehicle-mounted terminal 130 is used for adjusting the state of the vehicle equipment according to the vehicle usage information so as to meet the vehicle usage habit of the user.
The account login request refers to a request for logging in an account of a vehicle user, and the account login request can comprise a user identifier, wherein the user identifier refers to sign information of the vehicle user and has uniqueness. For example, the user identification may be identity information of the vehicle user, a cell phone number, etc. The login mode of the account can include, but is not limited to, verification codes, passwords, two-dimensional codes, voiceprint recognition, face recognition and the like. The vehicle usage information may include, but is not limited to, user data, usage habit data, usage records for the networked application, and the like. The user data may include face information, voiceprint information, etc., the usage habit data may include seat position, mirror angle, steering wheel height, etc., and the web application may include music, radio stations, etc.
For example, in the case that the account login request meets the login condition, that is, in the case that verification by means of a verification code, a password, a two-dimensional code, voiceprint recognition, face recognition, and the like is successful, the user identifier may be called the vehicle use information in the database, and the vehicle use information is sent to the vehicle-mounted terminal 130, and the vehicle-mounted terminal 130 adjusts the state of the vehicle device according to the vehicle use information, so as to meet the vehicle use habit of the user.
In some embodiments, the vehicle use information stored by the vehicle-mounted terminal 130 is emptied after the vehicle-mounted terminal 130 exits the vehicle user account.
Based on the above embodiments, the cloud server 120 is further configured to: in the case that the account login request does not satisfy the login condition, transmitting a registration authorization request to the management terminal 110; in the case where the management terminal 110 agrees to the user registration, information verification is performed to complete the registration of the user account.
As shown in fig. 5, fig. 5 is a schematic flow chart of a new user account of a vehicle, and the cloud server 120 may send a registration authorization request to the management terminal 110; if the manager refuses the registration authorization request at the management terminal 110, the vehicle-mounted terminal 130 prompts the newly-added user to fail, and if the registration authorization request is granted, information verification is performed to complete the registration of the user account. Methods of information verification include, but are not limited to, verification code verification, face verification, and the like, which are not limited herein.
Based on the above embodiments, the cloud server 120 is further configured to: sending the third authentication information to the user terminal and receiving the fourth authentication information fed back by the management terminal 110; and if the third verification information is the same as the fourth verification information, the vehicle user account registration is successful.
Wherein the third authentication information and the fourth authentication information refer to information for authenticating the identity of the user. For example, the third authentication information and the fourth authentication information may be authentication codes.
The management terminal 110 fills in the verification code, and sends the filled verification code to the cloud server 120, and the cloud server 120 generates a vehicle user account under the vehicle manager account after receiving the correct verification code.
In some embodiments, the management terminal 110 is further configured to send a request for checking vehicle usage data to the cloud server, and receive the vehicle usage data fed back by the cloud server, where the vehicle usage data includes vehicle fuel consumption, driving range, and running time. It should be noted that the vehicle usage data is data associated with a vehicle user account, that is, the management terminal 110 may view vehicle usage data associated with any vehicle user account.
According to the technical scheme, the user newly-added request can be generated through the management terminal so as to increase vehicle users and complete the registration of the vehicle user accounts, and the cloud server can receive the account login request sent by the vehicle-mounted terminal, wherein the account login request comprises a user identifier; under the condition that the account login request meets login conditions, vehicle use information is called based on the user identification; and sending the vehicle use information to a vehicle-mounted terminal, wherein the vehicle-mounted terminal is used for adjusting the state of the vehicle equipment according to the vehicle use information so as to meet the vehicle use habit of a user.
The foregoing description is only of the preferred embodiments of the present disclosure and description of the principles of the technology being employed. It will be appreciated by persons skilled in the art that the scope of the disclosure referred to in this disclosure is not limited to the specific combinations of features described above, but also covers other embodiments which may be formed by any combination of features described above or equivalents thereof without departing from the spirit of the disclosure. Such as those described above, are mutually substituted with the technical features having similar functions disclosed in the present disclosure (but not limited thereto).
Moreover, although operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of the present disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are example forms of implementing the claims.

Claims (7)

1. An information management system, comprising: the management terminal is in communication connection with the cloud server;
the management terminal is used for sending an information management request to the cloud server;
the cloud server is used for receiving the information management request sent by the management terminal and managing account information corresponding to a plurality of vehicle users according to the information management request;
wherein the information management request includes an information replacement request;
the cloud server is further configured to:
receiving an information replacement request sent by the management terminal and sending a replacement confirmation request to the original vehicle management terminal under the condition that the vehicle is in a registration state;
receiving user replacement information sent by the management terminal under the condition that the information fed back by the original vehicle management terminal is to be replaced, so as to complete replacement of vehicle management account information;
the information management request is used for registering a vehicle management account, changing the vehicle management account, adding a vehicle user account and calling vehicle use information associated with the account;
wherein, the management terminal is further used for:
acquiring user information, and generating a user newly-added request based on the user information; or receiving a registration authorization request sent by the vehicle-mounted terminal, displaying, receiving response information to the registration authorization request, and generating a user newly-added request based on user information in the registration authorization request when the response information is authorization registration;
the user newly-added request is sent to a cloud server;
wherein, the cloud server is further configured to:
receiving a user newly-added request sent by a management terminal, wherein the user newly-added request comprises user information;
judging whether the vehicle user registers an account or not based on the user information, and sending first verification information to the user terminal and receiving second verification information fed back by the management terminal under the condition that the vehicle user does not register the account;
if the first verification information is the same as the second verification information, completing the registration of the vehicle user account;
vehicle use information sent by the vehicle-mounted terminal registered with different vehicle user accounts is received, and the vehicle use information corresponding to a plurality of vehicle users is stored.
2. The information management system according to claim 1, wherein the information management request includes a registration request;
the cloud server is further configured to:
and receiving a registration request sent by the management terminal, wherein the registration request comprises a vehicle identifier, judging whether a vehicle corresponding to the vehicle identifier is registered or not based on the vehicle identifier, receiving user uploading information sent by the management terminal when the vehicle is in an unregistered state, and registering a vehicle management account based on the user uploading information, wherein the vehicle management account is used for logging in the management terminal so as to manage account information corresponding to a plurality of vehicle users.
3. The information management system of claim 1, wherein the cloud server is further configured to:
acquiring a vehicle identifier from a vehicle registration database and verification information corresponding to the vehicle identifier;
and comparing the verification information corresponding to the vehicle identification obtained from the vehicle registration database with the vehicle identification and the verification information in the user replacement information to verify the validity of the vehicle replacement information.
4. The information management system of claim 1, wherein the cloud server is further configured to:
receiving an account login request sent by a vehicle-mounted terminal, wherein the account login request comprises a user identifier;
under the condition that the account login request meets login conditions, calling vehicle use information based on the user identification;
and sending the vehicle use information to the vehicle-mounted terminal, wherein the vehicle-mounted terminal is used for adjusting the state of the vehicle equipment according to the vehicle use information so as to meet the vehicle use habit of a user.
5. The information management system of claim 4, wherein the cloud server is further configured to:
sending a registration authorization request to the management terminal under the condition that the account login request does not meet the login condition;
and under the condition that the management terminal agrees to the registration of the user, information verification is carried out to finish the registration of the user account.
6. The information management system of claim 5, wherein the cloud server is further configured to:
sending third verification information to a user terminal, and receiving fourth verification information fed back by the management terminal;
and if the third verification information is the same as the fourth verification information, the vehicle user account registration is successful.
7. The information management system according to claim 1, wherein the management terminal is further configured to:
the method comprises the steps of sending a request for checking vehicle use data to a cloud server, and receiving the vehicle use data fed back by the cloud server, wherein the vehicle use data comprise vehicle oil consumption, driving mileage and running time.
CN202210429715.3A 2022-04-22 2022-04-22 Information management system Active CN114928639B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210429715.3A CN114928639B (en) 2022-04-22 2022-04-22 Information management system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210429715.3A CN114928639B (en) 2022-04-22 2022-04-22 Information management system

Publications (2)

Publication Number Publication Date
CN114928639A CN114928639A (en) 2022-08-19
CN114928639B true CN114928639B (en) 2023-12-05

Family

ID=82806545

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210429715.3A Active CN114928639B (en) 2022-04-22 2022-04-22 Information management system

Country Status (1)

Country Link
CN (1) CN114928639B (en)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103152331A (en) * 2013-02-07 2013-06-12 百度在线网络技术（北京）有限公司 Method and system for logging in/registering through mobile terminal and cloud server
CN105635297A (en) * 2016-01-11 2016-06-01 深圳诺康医疗设备有限公司 Terminal device control method and system
CN106210047A (en) * 2016-07-11 2016-12-07 北京长安汽车工程技术研究有限责任公司 A kind of vehicle information management method, system and car networked system
CN107666498A (en) * 2016-07-27 2018-02-06 比亚迪股份有限公司 Update method, device, cloud server, system and the vehicle of vehicle module
CN109873749A (en) * 2018-12-21 2019-06-11 深圳市元征科技股份有限公司 A kind of sharing method and relevant device of information of vehicles
CN110855598A (en) * 2018-08-20 2020-02-28 北京场景互娱传媒科技有限公司 Terminal application management method, terminal device, cloud server and storage medium
CN111901798A (en) * 2019-05-06 2020-11-06 上海擎感智能科技有限公司 Login management method and device and computer storage medium

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103152331A (en) * 2013-02-07 2013-06-12 百度在线网络技术（北京）有限公司 Method and system for logging in/registering through mobile terminal and cloud server
CN105635297A (en) * 2016-01-11 2016-06-01 深圳诺康医疗设备有限公司 Terminal device control method and system
CN106210047A (en) * 2016-07-11 2016-12-07 北京长安汽车工程技术研究有限责任公司 A kind of vehicle information management method, system and car networked system
CN107666498A (en) * 2016-07-27 2018-02-06 比亚迪股份有限公司 Update method, device, cloud server, system and the vehicle of vehicle module
CN110855598A (en) * 2018-08-20 2020-02-28 北京场景互娱传媒科技有限公司 Terminal application management method, terminal device, cloud server and storage medium
CN109873749A (en) * 2018-12-21 2019-06-11 深圳市元征科技股份有限公司 A kind of sharing method and relevant device of information of vehicles
CN111901798A (en) * 2019-05-06 2020-11-06 上海擎感智能科技有限公司 Login management method and device and computer storage medium

Also Published As

Publication number Publication date
CN114928639A (en) 2022-08-19

Similar Documents

Publication Publication Date Title
US11743248B2 (en) Onboard vehicle digital identification transmission
US20240078856A1 (en) Method and system for activating telematics services
US9242619B2 (en) Method for controlling a vehicle using driver authentication, vehicle terminal, biometric identity card, biometric identification system, and method for providing a vehicle occupant protection and tracking function using the biometric identification card and the terminal
US20140129053A1 (en) Credential check and authorization solution for personal vehicle rental
CN102118368B (en) Binding method of users and vehicle equipment information, service platform and vehicle system
US10629012B1 (en) Multi-factor authentication for vehicles
CN110197328B (en) Vehicle management method, vehicle management server, terminal and storage medium
CN106600083A (en) Management method and management device for managing order receiving behavior of driver
EP3907673A1 (en) Authorization of vehicle repairs
CN111435503B (en) Method and device for acquiring electronic credentials
CN114928639B (en) Information management system
KR20190109804A (en) Apparatus and method of car calling service in autonomous vehicle
CN110555756A (en) Unattended car renting method and device
GB2581533A (en) Method for authenticating a user to a digital tachograph of a vehicle by means of a mobile device, digital tachograph, mobile device and data base device
CN110197535A (en) A kind of method, terminal and car-mounted device of riding
US20240046717A1 (en) Methods and Systems for Securely Accessing Operational Data
KR20130094673A (en) Method and system for subscribing one-day car insurance
US20220044207A1 (en) Vehicle service authorization
CN116455922A (en) Identity verification method and related product
KR20220080824A (en) Mobility service device and method for a carpool driver
CN116842492A (en) Vehicle-mounted control method and control system for leased vehicle

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant