User management method and device, vehicle and storage medium

Abstract

The application relates to the technical field of vehicles, in particular to a user management method and device, a vehicle and a storage medium, wherein the method comprises the following steps: obtaining an account login request of a vehicle and a vehicle identifier; identifying a target account in the account login request, and detecting an actual state of the target account; if the actual state is an online state, generating a management identifier allowing the target account to be logged in by other vehicles at the same time according to the vehicle identifier, and logging in the target account by using the management identifier. Therefore, the problems that a user is kicked off when logging in a same account on different vehicles in the related art, and the user experience is poor are solved.

Description

Technical Field

[0001] This application relates to the field of vehicle technology, and in particular to a user management method, device, vehicle, and storage medium. Background Technology

[0002] The Internet of Vehicles (IoV) leverages next-generation information and communication technologies to achieve comprehensive network connectivity between vehicles, roads, people, and service platforms, thereby effectively utilizing all dynamic vehicle information on the information network platform and providing various functional services during vehicle operation.

[0003] In related technologies, a user account for a vehicle model corresponds to a vehicle networking platform. However, if multiple users of different vehicle models can share a single vehicle networking platform, it may lead to inconsistencies in information, low applicability, and difficulty in management. Taking a computer system as an example, if a user logs in to an application account on computer A, the application account logged in on computer B will be logged out. Summary of the Invention

[0004] This application provides a user management method, device, vehicle, and storage medium to solve the problems in related technologies, such as mutual kick-out when users log in to the same account on different vehicles, resulting in a poor user experience.

[0005] The first aspect of this application provides a user management method, including the following steps: obtaining a vehicle's account login request and vehicle identifier; identifying the target account in the account login request and detecting the actual status of the target account; if the actual status is online, generating a management identifier that allows simultaneous login of the target account with other vehicles based on the vehicle identifier, and using the management identifier to log in to the target account.

[0006] Optionally, generating a management identifier that allows simultaneous login to the target account with other vehicles based on the vehicle identifier includes: determining the model of the current vehicle based on the vehicle identifier; and matching the corresponding management identifier based on the model.

[0007] Optionally, before obtaining the vehicle's account login request and vehicle identifier, the process includes: identifying the model of one or more vehicles; assigning different management identifiers according to different model numbers; and storing the management identifiers, bound to the user's authentication information, in a preset database, wherein the user's authentication information includes the target account and its password, and the vehicle identifier.

[0008] Optionally, it also includes: if the actual status is offline, then logging into the target account.

[0009] Optionally, after logging into the target account, the process includes: identifying whether the user's information has been modified; if the user information has been modified, automatically synchronizing the data information to the other online target accounts.

[0010] Optionally, logging into the target account using the management identifier includes: identifying whether the authentication information corresponding to the management identifier is consistent with the authentication information in the vehicle's account login request; if they are consistent, the login is successful; otherwise, a login error message is generated.

[0011] Optionally, after obtaining the vehicle's account login request and vehicle identifier, the process includes: determining whether the target account in the account login request exists; if the target account does not exist, automatically registering with the vehicle networking platform based on the account login request.

[0012] A second aspect of this application provides a user management device, comprising: an acquisition module for acquiring a vehicle's account login request and a vehicle identifier; an identification module for identifying a target account in the account login request and detecting the actual status of the target account; and a generation module for generating a management identifier that allows simultaneous login of the target account with other vehicles based on the vehicle identifier if the actual status is online, and using the management identifier to log in to the target account.

[0013] A third aspect of this application provides a vehicle, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the user management method as described in the above embodiments.

[0014] A fourth aspect of this application provides a computer-readable storage medium having a computer program stored thereon, which is executed by a processor to implement the user management method as described in the above embodiments.

[0015] Therefore, this application has at least the following beneficial effects:

[0016] This application embodiment can determine whether other vehicles are simultaneously logging into the target account by detecting the actual status of the target account in the vehicle's account login request. If the target account is currently online, the management identifier of the corresponding target account is matched according to the vehicle identifier, and the target account is logged in using the management identifier. This ensures that the same vehicle network platform can be logged into simultaneously on different vehicles, greatly improving service availability, with high applicability and convenient management.

[0017] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0018] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, wherein:

[0019] Figure 1 This is a flowchart of a user management method provided according to an embodiment of this application;

[0020] Figure 2 This is a flowchart illustrating a user management method according to an embodiment of this application;

[0021] Figure 3 This is a schematic diagram illustrating user synchronization information according to an embodiment of this application;

[0022] Figure 4 This is a block diagram of a user management device according to an embodiment of this application;

[0023] Figure 5 This is a structural schematic diagram of a vehicle according to an embodiment of this application. Detailed Implementation

[0024] The embodiments of this application are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application.

[0025] The user management method, apparatus, vehicle, and storage medium of this application are described below with reference to the accompanying drawings. Addressing the problem of mutual kick-out when users log in to the same account on different vehicles, resulting in a poor user experience, as mentioned in the background art, this application provides a user management method. In this method, the actual status of the target account in the vehicle's account login request can be detected to determine if other vehicles are simultaneously logging into the same target account. If the target account is currently online, the management identifier of the corresponding target account is matched according to the vehicle identifier, and the target account is logged in using the management identifier. This ensures that users can simultaneously log in to the same vehicle networking platform on different vehicles, greatly improving service availability, and offering high applicability and convenient management. Thus, the problem of mutual kick-out when users log in to the same account on different vehicles, resulting in a poor user experience, is solved in the related art.

[0026] Specifically, Figure 1 This is a flowchart illustrating a user management method provided in an embodiment of this application.

[0027] like Figure 1 As shown, this user management method includes the following steps:

[0028] In step S101, the vehicle's account login request and vehicle identifier are obtained.

[0029] The vehicle's account login request includes the target account's username or mobile phone number, login password, etc., without specific restrictions.

[0030] It is understood that the embodiments of this application can obtain the vehicle's account login request and vehicle identifier in order to identify the target account in the account login request.

[0031] In this embodiment of the application, before obtaining the vehicle's account login request and vehicle identifier, the process includes: identifying the model of one or more vehicles; assigning different management identifiers according to different model numbers; and storing the user's authentication information bound to the management identifier in a preset database, wherein the user's authentication information includes the target account and its password and the vehicle identifier.

[0032] The default database can be Redis, without any specific restrictions.

[0033] It is understood that in this embodiment of the application, different management identifiers are assigned to vehicles according to different vehicle types, and the authentication information of users bound to the management identifiers is stored in the database so as to facilitate the matching of the corresponding management identifiers based on the vehicle identifiers in the future.

[0034] It should be noted that this application uses a MAP(KV) data structure to store data in the database, where K represents the management identifier, i.e., businessID, and V represents the user's authentication information, without any specific limitations.

[0035] Specifically, different businessIds are assigned to the user apps of different car models A, B, and C, such as businessIdA, businessIdB, and businessIdC. When a user logs into the vehicle networking platform using the user app of car model A, the vehicle networking login is successful and authentication information is returned. The current user's car model brand information and authentication information are stored in Redis (database) in a Map (KV) data structure, where the key is businessIdA and the value is the current user's authentication information.

[0036] In this embodiment of the application, after obtaining the vehicle's account login request and vehicle identifier, the process includes: determining whether the target account in the account login request exists; if the target account does not exist, automatically registering with the vehicle networking platform based on the account login request.

[0037] The target account can be a vehicle networking platform account, without specific restrictions.

[0038] It is understood that in this embodiment of the application, the system determines whether the target account in the account login request exists. If it does not exist, the system directly registers the vehicle networking platform based on the account and password in the account login request, saving registration time. If it exists, the system can log in directly.

[0039] In step S102, the target account in the account login request is identified, and the actual status of the target account is detected.

[0040] It is understood that in this embodiment of the application, the target account in the account login request is identified and its actual status is detected so that specific operations can be performed according to the actual status of the target account.

[0041] In step S103, if the actual status is online, a management identifier is generated based on the vehicle identifier, allowing simultaneous login to the target account with other vehicles, and the target account is logged in using the management identifier.

[0042] It is understood that if the actual status of the target account in this application embodiment is online, it indicates that other vehicles are also logging into the target account at the same time. Therefore, it is necessary to generate a management identifier for the target account based on the vehicle identifier and use the management identifier to log into the target account, so as to ensure that different vehicles can log into the same vehicle network platform at the same time, which greatly improves the availability of the service, has high applicability and is convenient for management.

[0043] Specifically, when a user's APP (Application) for vehicle model A needs to access the vehicle networking platform, the user registers for the vehicle networking platform with businessIdA. If the user has already registered for the vehicle networking platform, the system returns the user's information on the vehicle networking platform. If the user has not registered for the vehicle networking platform, the system registers for the vehicle networking platform and returns the user's information on the vehicle networking platform.

[0044] In this embodiment of the application, generating a management identifier that allows simultaneous login to the target account with other vehicles based on the vehicle identifier includes: determining the model of the current vehicle based on the vehicle identifier; and matching the corresponding management identifier based on the model.

[0045] It is understood that the embodiments of this application can solve the problem of vehicle brand isolation by assigning businessId to different vehicle brands. Therefore, the management identifier in the corresponding database is matched according to the actual vehicle to facilitate subsequent login to the target account.

[0046] In this embodiment of the application, the method further includes: if the actual state is offline, then logging into the target account.

[0047] It is understood that if the actual state of this application embodiment is offline, it means that there are no other vehicles logged in on the Internet platform at this time, and there is no mutual kicking problem caused by logging in to the same account at the same time. Therefore, the target account can be logged in directly according to the account login request.

[0048] In this embodiment of the application, logging into the target account using the management identifier includes: identifying whether the authentication information corresponding to the management identifier is consistent with the authentication information in the vehicle's account login request; if they are consistent, the login is successful; otherwise, a login error message is generated.

[0049] It is understood that in this embodiment of the application, when logging into the target account for the first time, the system determines whether the login can be successful based on the authentication information corresponding to the management identifier and the authentication information in the vehicle's account login request. If the information is consistent, the login is successful. If they are different, it means that the current user's authentication has been tampered with and the login is illegal, and an alarm prompt is issued, such as "Illegal login!"

[0050] Specifically, when a user uses the vehicle-to-everything (V2X) function with businessIdA and authentication information, the V2X platform queries the current user authentication information map in Redis. It obtains the authentication information stored in Redis through businessIdA and compares it with the authentication information carried by the user. If they are different, it means that the current user authentication has been tampered with and the login is illegal. If they are the same, it means that the authentication is successful and the user can use the V2X platform function.

[0051] In this embodiment of the application, after logging into the target account, the process includes: identifying whether the user's information has been modified; if the user information has been modified, automatically synchronizing the data information to other online target accounts.

[0052] It is understood that when the user information is detected to have been modified, the embodiment of this application triggers the user information synchronization service of the vehicle network platform, automatically synchronizing the data information to other online target accounts, ensuring that the user information of the current vehicle network platform is up-to-date, and improving the user experience.

[0053] Specifically, when a user modifies their user information on the connected vehicle platform through the A-model user app, this modification triggers the connected vehicle platform's user information synchronization service. This service then notifies all other user apps across different vehicle models to update their user information. When a user uses other vehicle model apps, their current user information on the connected vehicle platform remains up-to-date. This resolves the inconsistency in user information across different vehicle model apps, significantly improving user satisfaction.

[0054] According to the user management method proposed in the embodiments of this application, it is possible to determine whether other vehicles are simultaneously logging into the target account by detecting the actual status of the target account in the vehicle's account login request. If the actual status of the target account is online, the management identifier of the corresponding target account is matched according to the vehicle identifier, and the target account is logged in using the management identifier. This ensures that the same vehicle network platform can be logged in simultaneously on different vehicles, which greatly improves the availability of the service, has high applicability, and is convenient for management.

[0055] The following will combine Figure 2 and Figure 3 The user management method is explained in detail, and the specific steps are as follows:

[0056] Step 1: Assign different businessIds to users' apps based on different car models and brands.

[0057] Different businessIds are assigned to user apps of different vehicle models A, B, and C, such as businessIdA, businessIdB, and businessIdC. When a user app of vehicle model A needs to access the vehicle networking platform, the user registers for the platform with businessIdA. If the user has already registered for the vehicle networking platform, the system returns the user's information on the platform; otherwise, the system registers the user and returns their vehicle networking platform information.

[0058] Step 2: Store the APP user authentication information in Redis using a Map (KV) data structure. When the APP user uses the vehicle networking platform, compare the user authentication information with Redis to ensure security and uniqueness.

[0059] When a user logs into the connected vehicle platform using the User App (vehicle model A), successful login returns authentication information. The system also stores the user's vehicle model and authentication information in a Redis database using a Map (KV) data structure, where the key is `businessIdA` and the value is the user's authentication information. When the user uses connected vehicle functions with `businessIdA` and authentication information, the platform queries the Redis map for the user's authentication information. It retrieves the authentication information stored in Redis using `businessIdA` and compares it with the user's authentication information. If they are different, it indicates that the user's authentication has been tampered with and the login is unauthorized. If they are the same, authentication is successful and the user can use the connected vehicle platform functions.

[0060] Step 3: When a user modifies their user information, the vehicle networking platform notifies the user apps of each vehicle model through the user synchronization service.

[0061] When a user modifies their user information on the connected vehicle platform through the A-model user app, the modification triggers the connected vehicle platform's user information synchronization service. This service notifies all other user apps across different vehicle models to update their user information. When a user uses other vehicle model user apps, their current user information on the connected vehicle platform remains up-to-date. This resolves inconsistencies in user information across different vehicle model user apps, significantly improving user satisfaction.

[0062] In summary, the embodiments of this application can store user authentication information by mapping the vehicle brand ID, and manage the user authentication information through Redis, which solves the problem of existing users of multiple vehicle model user apps, ensuring that one vehicle networking platform can provide services to multiple vehicle model user apps and improve system availability; user information modifications can be promptly synchronized to each vehicle model user app.

[0063] Next, the user management device proposed according to the embodiments of this application is described with reference to the accompanying drawings.

[0064] Figure 4 This is a block diagram of a user management device according to an embodiment of this application.

[0065] like Figure 4 As shown, the user management device 10 includes: an acquisition module 100, an identification module 200, and a generation module 300.

[0066] The acquisition module 100 is used to acquire the vehicle's account login request and vehicle identifier; the identification module 200 is used to identify the target account in the account login request and detect the actual status of the target account; the generation module 300 is used to generate a management identifier that allows other vehicles to log in to the target account at the same time if the actual status is online, and then use the management identifier to log in to the target account.

[0067] In this embodiment of the application, the acquisition module 100 is further configured to: identify the model of one or more vehicles; assign different management identifiers according to different model numbers; and store the user's authentication information bound to the management identifier in a preset database, wherein the user's authentication information includes the target account and its password and the vehicle identifier.

[0068] In this embodiment of the application, the acquisition module 100 is further used to: determine whether the target account in the account login request exists; if the target account does not exist, automatically register the vehicle networking platform according to the account login request.

[0069] In this embodiment of the application, the device 10 further includes a login module.

[0070] The login module is used to log in to the target account if the actual status is offline.

[0071] In this embodiment of the application, the generation module 300 is further configured to: determine the model of the current vehicle based on the vehicle identifier; and match the corresponding management identifier based on the model.

[0072] In this embodiment of the application, the generation module 300 is further used to: identify whether the user's user information has been modified; if the user information has been modified, automatically synchronize the data information to other online target accounts.

[0073] In this embodiment of the application, the generation module 300 is further used to: identify whether the authentication information corresponding to the management identifier is consistent with the authentication information in the vehicle's account login request; if they are consistent, the login is successful; otherwise, a login error message is generated.

[0074] It should be noted that the foregoing explanation of the user management method embodiment also applies to the user management device of this embodiment, and will not be repeated here.

[0075] According to the user management device proposed in the embodiments of this application, it can determine whether other vehicles are logging into the same target account at the same time by detecting the actual status of the target account in the vehicle's account login request. If the actual status of the target account is online at this time, the management identifier of the corresponding target account is matched according to the vehicle identifier, and the target account is logged in using the management identifier. This ensures that the same vehicle network platform can be logged in simultaneously on different vehicles, which greatly improves the availability of the service, has high applicability, and is convenient for management.

[0076] Figure 5 A schematic diagram of the structure of a vehicle provided in an embodiment of this application. The vehicle may include:

[0077] The memory 501, the processor 502, and the computer program stored on the memory 501 and capable of running on the processor 502.

[0078] When processor 502 executes the program, it implements the user management method provided in the above embodiments.

[0079] Furthermore, the vehicle also includes:

[0080] Communication interface 503 is used for communication between memory 501 and processor 502.

[0081] The memory 501 is used to store computer programs that can run on the processor 502.

[0082] The memory 501 may include high-speed RAM (Random Access Memory) memory, and may also include non-volatile memory, such as at least one disk storage.

[0083] If the memory 501, processor 502, and communication interface 503 are implemented independently, then the communication interface 503, memory 501, and processor 502 can be interconnected via a bus to complete communication between them. The bus can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus, etc. The bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 5 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0084] Optionally, in a specific implementation, if the memory 501, processor 502, and communication interface 503 are integrated on a single chip, then the memory 501, processor 502, and communication interface 503 can communicate with each other through an internal interface.

[0085] Processor 502 may be a CPU (Central Processing Unit), an ASIC (Application Specific Integrated Circuit), or one or more integrated circuits configured to implement embodiments of this application.

[0086] This application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the user management method described above.

[0087] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0088] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "N" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0089] Any process or method described in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or N executable instructions for implementing custom logic functions or processes, and the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as should be understood by those skilled in the art to which embodiments of this application pertain.

[0090] It should be understood that the various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, the N steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented using any one or more of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (FPGAs), field-programmable gate arrays (FPGAs), etc.

[0091] Those skilled in the art will understand that all or part of the steps of the methods in the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, the program includes one or a combination of the steps of the method embodiments.

[0092] Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of this application.

Claims

1. A user management method characterized by comprising: Includes the following steps: Obtaining the vehicle's account login request and vehicle identifier, wherein, before obtaining the vehicle's account login request and vehicle identifier, the process includes: identifying the model of one or more vehicles; assigning different management identifiers according to different model numbers; and binding the management identifiers to the user's authentication information and storing it in a preset database, wherein the user's authentication information includes the target account and its password and the vehicle identifier; Identify the target account in the account login request and detect the actual status of the target account; If the actual status is online, a management identifier that allows simultaneous login to the target account with other vehicles is generated based on the vehicle identifier. The target account is then logged in using the management identifier. Generating the management identifier that allows simultaneous login to the target account with other vehicles based on the vehicle identifier includes: determining the vehicle model based on the vehicle identifier; and matching the corresponding management identifier based on the vehicle model.

2. The user management method according to claim 1, characterized by, Also includes: If the actual status is offline, then log in to the target account.

3. The user management method according to claim 1 or 2, characterized by, After logging into the target account, the following is included: Identify whether a user's information has been modified; If the user information is modified, the data information will be automatically synchronized to the other online target accounts.

4. The user management method according to claim 1, characterized by, The step of logging into the target account using the management identifier includes: Identify whether the authentication information corresponding to the management identifier is consistent with the authentication information in the vehicle's account login request; If the results match, the login is successful; otherwise, a login error message will be generated.

5. The user management method according to claim 1, characterized by, After obtaining the vehicle's account login request and vehicle identifier, the process includes: Determine whether the target account in the login request exists; If the target account does not exist, the vehicle networking platform will be automatically registered based on the account login request.

6. A user management apparatus characterized by comprising: include: The acquisition module is used to acquire the vehicle's account login request and vehicle identifier. Before acquiring the vehicle's account login request and vehicle identifier, the module includes: identifying the model of one or more vehicles; assigning different management identifiers according to different model numbers; and binding the management identifiers to the user's authentication information and storing it in a preset database. The user's authentication information includes the target account and its password and the vehicle identifier. The identification module is used to identify the target account in the account login request and detect the actual status of the target account; The generation module is used to generate a management identifier that allows simultaneous login to the target account with other vehicles based on the vehicle identifier if the actual status is online, and to log in to the target account using the management identifier. The generation of the management identifier that allows simultaneous login to the target account with other vehicles based on the vehicle identifier includes: determining the vehicle model based on the vehicle identifier; and matching the corresponding management identifier based on the vehicle model.

7. A vehicle characterized by comprising: include: A memory, a processor, and a computer program stored in the memory and executable on the processor, the processor executing the program to implement the user management method as described in any one of claims 1-5.

8. A computer-readable storage medium having stored thereon a computer program, characterized in that, The program is executed by the processor to implement the user management method as described in any one of claims 1-5.

Images