Vehicle configuration data management method, vehicle, equipment, cloud server, system and storage medium

Abstract

The invention relates to a vehicle configuration data management method, a vehicle, equipment, a cloud server, a system and a storage medium. The vehicle configuration data management method comprises the steps of generating updated vehicle configuration data for adjusting at least one configuration in response to a setting operation of a user for the at least one configuration of a vehicle; and when the mobile device with the NFC module is detected, transmitting the vehicle configuration data to the mobile device, so that the mobile device updates the NFC data pre-stored by the mobile device according to the vehicle configuration data. The method has the advantages of low cost, rapidness, convenience, high safety and the like.

Description

Technical Field

[0001] The present application relates to the field of vehicle technology, and in particular to a vehicle configuration data management method, vehicle, equipment, cloud server, system and storage medium. Background Art

[0002] At present, the personalized configuration of vehicles is realized based on face recognition. In this configuration method, a camera needs to be installed in the vehicle. After the user completes the personalized configuration based on the vehicle's display screen, the vehicle calls the camera to collect the user's facial data and establishes a binding relationship between the facial data and the personalized configuration. After that, the vehicle can obtain the corresponding personalized configuration through face recognition to adjust the personalized configuration. It is precisely because this configuration method requires face recognition that on the one hand, the facial data needs to be saved in the vehicle. If the data is not saved properly, it will threaten the user's privacy. On the other hand, high-precision cameras need to be installed in the vehicle, which is costly. Summary of the invention

[0003] The embodiments of the present application provide a vehicle configuration data management method, vehicle, equipment, cloud server, system and storage medium, which have the advantages of low cost, fast and convenient, high security, etc., so as to at least partially solve the above technical problems.

[0004] To achieve the above object, according to a first aspect of the present application, a vehicle configuration data management method is provided, which is applied to a vehicle with an NFC module, comprising:

[0005] In response to a setting operation of a user on at least one configuration of the vehicle, generating updated vehicle configuration data for adjusting the at least one configuration;

[0006] When a mobile device with an NFC module is detected, the vehicle configuration data is transmitted to the mobile device, so that the mobile device updates NFC data pre-stored in the mobile device according to the vehicle configuration data.

[0007] Optionally, transmitting the vehicle configuration data to the mobile device comprises:

[0008] In response to a user's selection operation on a download control, when the mobile device is detected, the vehicle configuration data is sent to an NFC tag pre-stored in the mobile device.

[0009] Optionally, the method further includes:

[0010] If a mobile device with an NFC module is detected, the vehicle configuration data transmitted by the mobile device is obtained;

[0011] At least one configuration of the vehicle is adjusted based on the vehicle configuration data.

[0012] Optionally, before acquiring the vehicle configuration data transmitted by the mobile device, the method further includes:

[0013] authenticating the mobile device according to the target random number;

[0014] After the authentication is passed, the step of acquiring the vehicle configuration data transmitted by the mobile device is performed.

[0015] Optionally, authenticating the mobile device according to the target random number includes:

[0016] Generate a target random number according to a preset random number generation rule, and send the target random number to a mobile device;

[0017] The encrypted ciphertext returned by the mobile device is obtained, and the identity of the mobile device is authenticated according to the encrypted ciphertext and the target random number.

[0018] Optionally, the performing identity authentication on the mobile device according to the encrypted ciphertext and the target random number includes:

[0019] decrypting the encrypted ciphertext according to a target authentication key to obtain a decrypted ciphertext, wherein the mobile device and the vehicle have the same target authentication key;

[0020] If the decrypted ciphertext is consistent with the target random number, it is determined that the mobile device is authenticated.

[0021] Optionally, the setting operation includes at least one of a write operation, a modify operation, and a delete operation.

[0022] According to a second aspect of the present application, a vehicle configuration data management method is provided, which is applied to a mobile device having an NFC module, comprising:

[0023] Update pre-stored NFC data according to the vehicle configuration data transmitted by the vehicle acquired by the NFC module, and send the updated NFC data to the cloud server;

[0024] The NFC data includes vehicle configuration data, and the vehicle configuration data is used to adjust at least one configuration of the vehicle.

[0025] Optionally, the method further comprises:

[0026] In response to a user logging into the mobile device for the first time, sending a request to obtain the NFC tag to the cloud server;

[0027] When the NFC data sent by the cloud server is received, an NFC tag is created in the mobile device.

[0028] Optionally, the method further comprises:

[0029] When a vehicle equipped with an NFC module is detected, NFC data stored in the NFC tag of the mobile device is transmitted to the NFC tag of the vehicle, so that the vehicle adjusts at least one configuration of the vehicle according to the NFC data.

[0030] According to a third aspect of the present application, a vehicle configuration data management method is provided, which is applied to a cloud server, comprising:

[0031] When receiving NFC data sent by the first mobile device, updating the pre-stored NFC data of the first mobile device with the received NFC data;

[0032] The NFC data includes vehicle configuration data, and the vehicle configuration data is used to adjust at least one configuration of the vehicle.

[0033] Optionally, when receiving the acquisition request of the NFC tag sent by the second mobile device, issuing data of the NFC tag is sent to the second mobile device, so that the second mobile device creates the NFC tag.

[0034] Optionally, after sending the issuance data of the NFC tag to the second mobile device so that the second mobile device creates the NFC tag, the method further includes:

[0035] When the NFC tag creation success information sent by the second mobile device is received, the user information data in the acquisition request is associated with the NFC tag and stored.

[0036] Optionally, the method further comprises:

[0037] In response to a request for downloading vehicle configuration data sent by a second mobile device, obtaining user information data in the request;

[0038] Querying vehicle configuration data having a corresponding association relationship with the user information data according to the user information data, and feeding back the vehicle configuration data to the second mobile device;

[0039] The second mobile device is configured to have an NFC module.

[0040] Optionally, the method further includes:

[0041] Acquire user registration information sent by the second mobile device, and perform legal authentication on the second mobile device according to the user registration information;

[0042] When the legal authentication is passed, the user registration information is stored, and registration success information is generated and sent to the second mobile device.

[0043] Optionally, before querying the vehicle configuration data having a corresponding association relationship with the user information data according to the user information data and feeding back to the second mobile device, the method further includes:

[0044] Performing identity authentication on the second mobile device according to the user information data and the user registration information;

[0045] When the identity authentication is passed, the vehicle configuration data having a corresponding association relationship with the user information data is queried according to the user information data, and the vehicle configuration data is fed back to the second mobile device.

[0046] Optionally, the performing identity authentication on the second mobile device according to the user information data and the user registration information includes:

[0047] When the user information data is consistent with the user registration information, it is determined that the identity authentication of the second mobile device is passed.

[0048] According to a fourth aspect of the present application, a vehicle is provided, the vehicle having an NFC module, the vehicle comprising: a memory having a computer program stored thereon; and a processor for executing the computer program in the memory to implement the vehicle configuration data management method as described in the first aspect above.

[0049] According to a fifth aspect of the present application, a mobile device is provided, the mobile device having an NFC module, the mobile device comprising: a memory on which a computer program is stored; and a processor for executing the computer program in the memory to implement the vehicle configuration data management method as described in the second aspect above.

[0050] According to the sixth aspect of the present application, a cloud server is provided, comprising: a memory on which a computer program is stored; and a processor for executing the computer program in the memory to implement the vehicle configuration data management method as described in the third aspect above.

[0051] According to the seventh aspect of the present application, a vehicle configuration system is provided, which includes a mobile device with NFC communication function as described in the fourth aspect above, a vehicle with NFC communication function as described in the fifth aspect above, and a cloud server as described in the sixth aspect above.

[0052] According to the eighth aspect of the present application, a non-temporary computer-readable storage medium is provided, on which a computer program is stored. When the program is executed by a processor, it implements the vehicle configuration data management method as described in the first aspect above, or implements the vehicle configuration data management method as described in the second aspect above, or implements the vehicle configuration data management method as described in the third aspect above.

[0053] The benefit of the present application is that at least one configuration of a vehicle can be adjusted through an NFC tag, which is low-cost, fast, convenient and highly secure.

[0054] More specifically, some embodiments of the present application may produce the following specific beneficial effects:

[0055] The vehicle configuration data management method provided in the embodiment of the present application allows a user to set at least one configuration of a vehicle, and the vehicle can respond to the user's configuration operation and generate corresponding configuration data. In this way, when the vehicle detects that a mobile device with an NFC module is approaching, the configuration data can be sent to the mobile device for storage, so that when the user needs to adjust the personalized configuration of the vehicle, the user can directly bring the mobile device close to the vehicle, and the vehicle can read the NFC data stored in the mobile device after detecting the mobile device, and adjust the personalized configuration of the vehicle according to the vehicle configuration data included in the NFC data.

[0056] Based on this, the embodiments of the present application can realize the application scenario of "one person to multiple vehicles" in which different vehicles automatically adjust the personalized configuration by reading NFC data stored in the same mobile device, and can also realize the application scenario of "multiple people to one vehicle" in which the same vehicle automatically adjusts the personalized configuration by reading NFC data stored in different mobile devices. The embodiments of the present application help to achieve efficient switching of the same user to different vehicles and different users to the same vehicle.

[0057] Moreover, in the embodiment of the present application, the vehicle does not need to save user data such as user accounts and biometric features (such as face), which does not threaten the privacy of users and does not have an upper limit on the number of user accounts. It is precisely because the embodiment of the present application adjusts at least one configuration of the vehicle through the NFC module that, compared with installing a high-definition camera in the vehicle for face recognition, NFC technology has the advantages of low cost, fast and convenient, and high security.

[0058] In addition, the vehicle configuration data management method provided in the embodiment of the present application backs up the NFC data of the mobile device through the cloud server. When the NFC data pre-stored in the mobile device is updated, the mobile device sends the updated NFC data to the cloud server to update the backup, so that when the user changes the mobile device, the backed-up NFC data is downloaded from the cloud server to the new mobile device, and the switch between the old and new mobile devices can be completed. Therefore, when the user changes the mobile device, the embodiment of the present application does not require the user to re-register the user account and apply for the issuance of a new NFC tag, effectively achieving the effect of "one-time configuration and recycling" of the user account and NFC tag.

[0059] Other features and advantages of the present application will be described in detail in the subsequent detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0060] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present application, and those skilled in the art can obtain other drawings based on these drawings without creative work.

[0061] In order to more completely understand the present application and its beneficial effects, the following description will be given in conjunction with the accompanying drawings, wherein the same figure numbers represent the same parts in the following description.

[0062] Figure 1 It is a flowchart of a vehicle configuration data management method on a mobile device side provided in an embodiment of the present application.

[0063] Figure 2 It is a flowchart of a vehicle configuration data management method on the vehicle side provided in an embodiment of the present application.

[0064] Figure 3 It is a flowchart of a vehicle configuration data management method on the cloud server side provided in an embodiment of the present application.

[0065] Figure 4 It is a flow chart of a vehicle configuration data management method provided in an embodiment of the present application.

[0066] Figure 5 It is a flowchart of another vehicle configuration data management method provided in an embodiment of the present application.

[0067] Figure 6 This is a flowchart of another vehicle configuration data management method provided in an embodiment of the present application.

[0068] Figure 7 This is a flowchart of another vehicle configuration data management method provided in an embodiment of the present application.

[0069] Figure 8 This is a flowchart of another vehicle configuration data management method provided in an embodiment of the present application.

[0070] Fig. 9 It is a schematic diagram of an application scenario of "one person to multiple vehicles" provided in an embodiment of the present application.

[0071] Fig.10 It is a schematic diagram of an application scenario of "multiple people in one car" provided in an embodiment of the present application.

[0072] Fig.11 It is a schematic diagram of an application scenario of "switching between old and new mobile devices" provided in an embodiment of the present application.

[0073] Fig.12 It is a block diagram of a vehicle configuration system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0074] The technical solutions in the embodiments of the present application will be described clearly and completely below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present application.

[0075] According to the first aspect of the present application, an embodiment of the present application provides a vehicle configuration data management method.

[0076] See also Figure 1 , Figure 1 1 is a flow chart of a vehicle configuration data management method provided by an embodiment of the present application. The vehicle configuration data management method can be applied to vehicles with NFC communication function. Figure 1 As shown, the vehicle configuration data management method may include the following steps:

[0077] Step S110: generating updated vehicle configuration data for adjusting at least one configuration in response to a user's setting operation for at least one configuration of the vehicle;

[0078] Step S120: When a mobile device with an NFC module is detected, the vehicle configuration data is transmitted to the mobile device, so that the mobile device updates the NFC data pre-stored in the mobile device according to the vehicle configuration data.

[0079] In some embodiments, the above step S120 may include: in response to the user's selection operation for the download control, when the mobile device is detected, sending the vehicle configuration data to an NFC tag pre-stored in the mobile device.

[0080] The vehicle configuration data management method in this embodiment may further include:

[0081] Step S130: if a mobile device with an NFC module is detected, then obtaining vehicle configuration data transmitted by the mobile device;

[0082] Step S140: Adjust at least one configuration of the vehicle according to the vehicle configuration data.

[0083] It is worth noting that in this embodiment, the current user (such as the first user) can bring his mobile device close to the NFC module of the vehicle (such as "touch and pay"). If the vehicle detects the mobile device with an NFC module, it can obtain the vehicle configuration data transmitted by the mobile device and adjust at least one configuration of the vehicle according to the vehicle configuration data, such as seat position, rearview mirror position, air-conditioning temperature and air volume, speaker volume and mode, etc.

[0084] If the user of the vehicle changes (or the mobile device changes), the new user (such as the second user) only needs to bring his or her mobile device close to the vehicle's NFC module. Once the vehicle detects the new mobile device, it can obtain the vehicle configuration data transmitted by the new mobile device to configure the vehicle, so that the second user can also personalize the vehicle.

[0085] Before obtaining the vehicle configuration data transmitted by the mobile device, the vehicle can verify the legitimacy of the identity of the mobile device, and adjust the vehicle configuration according to the vehicle configuration data after the verification is passed. The subsequent embodiments will be described in detail and will not be repeated here.

[0086] In this way, this embodiment can be effectively applied to the application scenario of "multiple people to one car", that is, since the vehicle does not need to store user information, there is no user upper limit, and legal mobile devices can personalize the vehicle through the NFC function, and since the vehicle does not need to store any user data, user privacy is also guaranteed.

[0087] In some embodiments, before the above step S130, the following steps may also be included:

[0088] Step S150: authenticating the mobile device according to the target random number;

[0089] Step S160: After the authentication is passed, the step of acquiring the vehicle configuration data transmitted by the mobile device is executed.

[0090] In some embodiments, the above step S150 may include:

[0091] Step S1501, generating a target random number according to a preset random number generation rule, and sending the target random number to a mobile device;

[0092] Step S1502, obtaining the encrypted ciphertext returned by the mobile device, and performing identity authentication on the mobile device according to the encrypted ciphertext and the target random number.

[0093] In some embodiments, the above step S1502 may include:

[0094] decrypting the encrypted ciphertext according to a target authentication key to obtain a decrypted ciphertext, wherein the mobile device and the vehicle have the same target authentication key;

[0095] If the decrypted ciphertext is consistent with the target random number, it is determined that the mobile device is authenticated.

[0096] In one embodiment, the setting operation includes at least one of a write operation, a modify operation, and a delete operation.

[0097] For an introduction to the various steps in the vehicle configuration data management method on the vehicle side, see the following Figures 4 to 8 The relevant contents in the embodiments are not described in detail here.

[0098] According to the second aspect of the present application, an embodiment of the present application provides a vehicle configuration data management method.

[0099] See also Figure 2 , Figure 2 1 is a flow chart of a vehicle configuration data management method provided by an embodiment of the present application. The vehicle configuration data management method can be applied to a mobile device with NFC communication function. Figure 2 As shown, the vehicle configuration data management method may include the following steps:

[0100] Step S210: updating the pre-stored NFC data according to the vehicle configuration data transmitted by the vehicle acquired by the NFC module, and sending the updated NFC data to the cloud server;

[0101] The NFC data includes vehicle configuration data, and the vehicle configuration data is used to adjust at least one configuration of the vehicle.

[0102] In some embodiments, the vehicle configuration data management method further includes the following steps:

[0103] Step S220: In response to the user logging into the mobile device for the first time, sending a request to obtain the NFC tag to the cloud server;

[0104] Step S230: When receiving the NFC data sent by the cloud server, an NFC tag is created in the mobile device.

[0105] In some embodiments, the vehicle configuration data management method further includes the following steps:

[0106] Step S240: When a vehicle equipped with an NFC module is detected, the NFC data stored in the NFC tag of the mobile device is transmitted to the NFC tag of the vehicle, so that the vehicle adjusts at least one configuration of the vehicle according to the NFC data.

[0107] It is worth noting that in this embodiment, the user (such as the first user) can bring the mobile device close to the NFC module of the vehicle (such as "touch and bump"). At this time, if the mobile device detects a vehicle with an NFC module, the NFC data stored in the NFC tag of the mobile device (such as vehicle configuration data) can be transmitted to the NFC tag of the vehicle, so that the vehicle can adjust at least one configuration of the vehicle according to the received vehicle configuration data, such as seat position, rearview mirror position, air-conditioning temperature and air volume, speaker volume and mode, etc.

[0108] Moreover, when the user of the vehicle changes (or the mobile device changes), the new user (such as the second user) only needs to bring his or her mobile device close to the vehicle's NFC module. Once the new mobile device detects the vehicle with an NFC module, it can transmit the NFC data (such as vehicle configuration data) stored in the NFC tag of the mobile device to the NFC tag of the vehicle, so that the vehicle adjusts at least one configuration of the vehicle according to the vehicle configuration data sent by the new mobile device, such as seat position, rearview mirror position, air-conditioning temperature and air volume, speaker volume and mode, etc.

[0109] In this way, this embodiment can be applicable to the application scenario of "multiple people to one car", that is, since the vehicle does not need to store user information, there is no user upper limit, and legal mobile devices can personalize the vehicle through the NFC function, and since the vehicle does not need to store any user data, user privacy is also guaranteed.

[0110] For an introduction to the various steps in the vehicle configuration data management method on the mobile device side, see the following Figures 4 to 8 The relevant contents in the embodiments are not described in detail here.

[0111] According to a third aspect of the present application, an embodiment of the present application provides a vehicle configuration data management method.

[0112] See also Figure 3 , Figure 3 1 is a flow chart of a vehicle configuration data management method provided by an embodiment of the present application. The vehicle configuration data management method can be applied to a cloud server. Figure 3 As shown, the vehicle configuration data management method may include the following steps:

[0113] Step S310: when receiving NFC data sent by the first mobile device, updating the pre-stored NFC data of the first mobile device to the received NFC data; wherein the NFC data includes vehicle configuration data, and the vehicle configuration data is used to adjust at least one configuration of the vehicle.

[0114] In some embodiments, the vehicle configuration data management method further includes the following steps:

[0115] Step S320: When receiving the NFC tag acquisition request sent by the second mobile device, sending the NFC tag issuance data to the second mobile device, so that the second mobile device creates the NFC tag.

[0116] In some embodiments, after the above step S320, the following steps may also be included:

[0117] Step S330: When the NFC tag creation success information sent by the second mobile device is received, the user information data in the acquisition request is associated with the NFC tag and stored.

[0118] In some embodiments, the vehicle configuration data management method further includes the following steps:

[0119] Step S340: Responding to the request for downloading vehicle configuration data sent by the second mobile device, obtaining user information data in the request;

[0120] Step S350: querying the vehicle configuration data having a corresponding association relationship with the user information data according to the user information data, and feeding back the vehicle configuration data to the second mobile device;

[0121] The second mobile device is configured to have an NFC module.

[0122] In some embodiments, the vehicle configuration data management method further includes the following steps:

[0123] Step S360: obtaining user registration information sent by the second mobile device, and performing legal authentication on the second mobile device according to the user registration information;

[0124] Step S370: When the legal authentication is passed, the user registration information is stored, and registration success information is generated and sent to the second mobile device.

[0125] In some embodiments, before the above step S350, the following steps may also be included:

[0126] Step S380: authenticating the second mobile device according to the user information data and the user registration information;

[0127] Step S390: When the identity authentication is passed, query the vehicle configuration data corresponding to the user information data according to the user information data, and feed back to the second mobile device.

[0128] In some embodiments, the above step S380 may include:

[0129] Step S3801: When the user information data is consistent with the user registration information, it is determined that the identity authentication of the second mobile device is passed.

[0130] For an introduction to each step in the vehicle configuration data management method on the cloud server side, see the following Figures 4 to 8 The relevant contents in the embodiments are not described in detail here.

[0131] In summary, the vehicle configuration data management method provided in the embodiment of the present application adjusts the personalized configuration of the vehicle through an NFC tag. When the user needs to adjust the personalized configuration of the vehicle, the mobile device with an NFC module (i.e., with NFC communication function) is brought close to the vehicle that also has NFC communication function, so that the vehicle can read the NFC data stored in the mobile device after detecting the mobile device, so as to adjust the personalized configuration of the vehicle according to the vehicle configuration data included in the NFC data. Based on this, the embodiment of the present application can realize the application scenario of "one person to multiple vehicles" in which different vehicles automatically adjust the personalized configuration by reading the NFC data stored in the same mobile device, such as Fig. 9 As shown; it is also possible to realize the application scenario of "multiple people to one car" where the same vehicle automatically adjusts the personalized configuration by reading the NFC data stored in different mobile devices, such as Fig.10 As shown; the embodiments of the present application help to achieve efficient switching of the same user to different vehicles and different users to the same vehicle.

[0132] Moreover, in the embodiment of the present application, the vehicle does not need to save user data such as user accounts and biometric features (such as face), which does not threaten the privacy of users and does not have an upper limit on the number of user accounts. It is precisely because the embodiment of the present application adjusts at least one configuration of the vehicle through the NFC tag that, compared with installing a high-definition camera in the vehicle for face recognition, NFC technology has the advantages of low cost, fast and convenient, and high security.

[0133] In addition, the vehicle configuration data management method provided in the embodiment of the present application backs up the NFC data of the mobile device through the cloud server. When the NFC data pre-stored in the mobile device is updated, the mobile device sends the updated NFC data to the cloud server to update the backup, so that when the user changes the mobile device, the backed-up NFC data is downloaded from the cloud server to the new mobile device, and the switch between the new and old mobile devices can be completed. Fig.11 Therefore, in the embodiment of the present application, when a user changes a mobile device, the user does not need to re-register a user account and apply for a new NFC tag, thereby effectively achieving the effect of "one-time configuration and recycling" of the user account and NFC tag.

[0134] According to a fourth aspect of the present application, an embodiment of the present application provides a vehicle configuration data management method.

[0135] See also Figure 4 , Figure 4 1 is a flow chart of a vehicle configuration data management method provided by an embodiment of the present application. The vehicle configuration data management method can be applied to a vehicle configuration system, which may include a cloud server and a mobile device with NFC communication function.

[0136] like Figure 4 As shown, the vehicle configuration data management method may include the following steps:

[0137] Step ST410: the mobile device sends a registration request for the user account to the cloud server in response to the user's submission operation for the registration information;

[0138] Step S T420: The cloud server performs a first legitimacy authentication on the mobile device according to the registration request; if the mobile device passes the first legitimacy authentication, the following step ST430 is executed; if the mobile device fails the first legitimacy authentication, the following step ST460 is executed;

[0139] Step ST430: The cloud server stores the user account;

[0140] Step ST440: The cloud server sends a successful registration indication message to the mobile device;

[0141] Step ST450: The mobile device displays a user interface according to the indication information of successful registration;

[0142] Step ST460: The cloud server sends a registration failure indication message to the mobile device;

[0143] Step ST470: The mobile device displays a user interface according to the indication information of registration failure.

[0144] In an embodiment of the present application, a mobile application installed in a mobile device may provide a user-operable user interface to facilitate user registration of a user account, etc. In step ST410, the mobile device may display a registration user interface of the mobile application to facilitate the user to enter registration information. In response to the user's submission operation for the registration information, the mobile device sends a registration request for the user account to the cloud server. The registration request includes the registration information submitted by the user, and optionally, the registration information includes but is not limited to at least one of the following: the name, password, mobile phone number, email address, etc. of the user account.

[0145] In step ST420, the cloud server needs to perform a first legitimacy authentication on the mobile device according to the registration request, or in other words, the cloud server performs a first legitimacy authentication on the user account requested to be registered by the mobile device according to the registration request. Optionally, the first legitimacy authentication includes but is not limited to at least one of the following authentications: whether the name already exists, whether the password is too simple (such as whether it only has numbers or letters), whether the mobile phone number is legal (such as whether the format is correct, whether it exists, etc.), whether the email address is legal (such as whether the format is correct, whether it exists, etc.), etc.

[0146] When the mobile device passes the first legitimacy authentication, steps ST430 to ST450 are continued. Figure 4 Only taking step ST430 being performed before step ST440 as an example, in actual application, step ST430 may also be performed after step ST440 or ST450, or may be performed simultaneously with step ST440 or ST450, and the embodiment of the present application does not limit this. In step ST450, the mobile device displays a user interface according to the indication information of successful registration to prompt the user that the user account requested to be registered has been successfully registered.

[0147] When the mobile device fails to pass the first legitimacy authentication, continue to execute steps ST460 and ST470. In step ST470, the mobile device displays a user interface according to the indication information of registration failure to prompt the user that the registration of the user account requested by the user has failed. Optionally, the indication information of registration failure also includes the reason for the registration failure, such as the name already exists, the password is too simple, the mobile phone number does not exist, the email address does not exist, the email address format is incorrect, etc., so that the user interface displayed by the mobile device in step ST470 is also used to prompt the user the reason for the registration failure of the user account requested by the user.

[0148] To summarize, the vehicle configuration data management method provided in the embodiment of the present application saves the successfully registered user account through the cloud server during the user account registration stage, so that when the user subsequently changes the mobile device, the corresponding NFC tag can be obtained by logging into the user account on the new mobile device.

[0149] According to the fifth aspect of the present application, an embodiment of the present application provides a vehicle configuration data management method.

[0150] See also Figure 5 , Figure 5 1 is a flow chart of a vehicle configuration data management method provided by an embodiment of the present application. The vehicle configuration data management method can be applied to a vehicle configuration system, which may include a cloud server and a mobile device with NFC communication function.

[0151] like Figure 5 As shown, the vehicle configuration data management method may include the following steps:

[0152] Step ST510: the mobile device performs a second legitimacy authentication on the login information in response to the user's submission operation on the login information; if the login information passes the second legitimacy authentication, the following step ST520 is executed; if the login information fails the second legitimacy authentication, the following step ST590 is executed;

[0153] Step ST520: The mobile device synchronizes data related to the logged-in user account from the cloud server;

[0154] Step ST530: the mobile device sends a request to create an NFC tag to the cloud server in response to the user's submission operation on the tag information;

[0155] Step ST540: the cloud server generates issuance data of the NFC tag according to the creation request;

[0156] Step ST550: the cloud server sends the issuance data of the NFC tag to the mobile device;

[0157] Step ST560: The mobile device creates an NFC tag in the mobile device according to the issuance data;

[0158] Step ST570: The mobile device sends a successful creation indication message to the cloud server;

[0159] Step ST580: The cloud server establishes a mapping relationship between the user account and the NFC tag;

[0160] Step ST590: The mobile device displays a user interface based on the indication information of login failure.

[0161] In an embodiment of the present application, a mobile application installed in a mobile device may provide a user-operable user interface to facilitate the user to log in to a user account, apply to create an NFC tag, etc. In step ST510, the mobile device may display the login user interface of the mobile application to facilitate the user to enter login information. Optionally, the login information includes, but is not limited to, at least one of the following: the mobile phone number, name, password, email address, etc. of the user account. In an embodiment of the present application, when the mobile device successfully registers a user account, it may locally store relevant information of the user account, such as name, password, mobile phone number, email address, etc., so as to facilitate the subsequent authentication of the legitimacy of the login information when the user logs in to the user account. In step ST510, the mobile device needs to perform a second legitimacy authentication on the login information submitted by the user to verify whether the login information submitted by the user is correct, such as whether it is consistent with the relevant information of the user account stored in the mobile device.

[0162] When the login information passes the second legitimacy authentication, the user account requested by the user to log in is successfully logged in in the mobile device, and steps ST520 to ST580 are continued.

[0163] In step ST520, the mobile device synchronizes data related to the logged-in user account from the cloud server. The data related to the user account includes, but is not limited to, NFC tags that have been successfully created through the user account. For example, the user logs in to the user account through other mobile devices and creates a new NFC tag, and uploads the new NFC tag to the cloud server, so that when the user logs in to the user account on the current mobile device, the NFC tags corresponding to the user account created by other mobile devices can be synchronized from the cloud server.

[0164] In step ST530, the user account requested by the user to log in is successfully logged in in the mobile device, and the mobile device can display the creation user interface of the mobile application so that the user can enter the tag information of the NFC tag currently requested to be created. In response to the user's submission operation for the tag information, the mobile device sends a creation request for the NFC tag to the cloud server. The creation request includes the tag information submitted by the user, and optionally, the tag information includes but is not limited to at least one of the following: the name of the user account, the model of the vehicle, etc.

[0165] In step ST540, the cloud server generates an NFC tag and the issuance data of the NFC tag according to the creation request. The issuance data of the NFC tag refers to the data that needs to be written into the NFC tag when the mobile device first creates the NFC tag, or it can be said that the NFC tag is a carrier for storing the issuance data, and the NFC tag can be initialized to its required function through the issuance data of the NFC tag. For example, in an embodiment of the present application, the NFC tag is used to store vehicle configuration data, and the vehicle can adjust the personalized configuration of the vehicle by reading the NFC tag.

[0166] In step ST560, the mobile device transmits the issuance data of the NFC tag sent by the cloud server to the created NFC tag to implement functional initialization of the NFC tag.

[0167] In step ST570, the mobile device successfully creates the NFC tag and sends an indication of successful creation to the cloud server so that the cloud server can establish a mapping relationship between the user account and the NFC tag in step ST580.

[0168] When the login information fails to pass the second legitimacy authentication, the user account requested by the user to log in fails to log in in the mobile device, and step ST590 is continued. In step ST590, the mobile device can generate an indication of login failure, and display a user interface according to the indication of login failure to prompt the user that the login of the user account requested by the user failed. Optionally, the indication of login failure also includes the reason for the login failure, such as the name does not exist, the password is wrong, the mobile phone number is wrong, the email address does not exist, etc., so that the user interface displayed by the mobile device in step ST590 is also used to prompt the user the reason for the login failure of the user account requested by the user.

[0169] To summarize, the vehicle configuration data management method provided in the embodiment of the present application establishes a mapping relationship between the user account and the NFC tag through a cloud server during the NFC tag creation phase, so that when the user subsequently replaces the mobile device, the NFC tag corresponding to the user account can be synchronized from the cloud server by logging into the user account on the new mobile device.

[0170] According to the sixth aspect of the present application, an embodiment of the present application provides a vehicle configuration data management method.

[0171] See also Figure 6 , Figure 6 1 is a flow chart of a vehicle configuration data management method provided by an embodiment of the present application. The vehicle configuration data management method can be applied to a vehicle configuration system, which may include a cloud server, a mobile device with NFC communication function, and a vehicle with NFC communication function. Figure 6 As shown, the vehicle configuration data management method may include the following steps:

[0172] Step ST610: the vehicle generates updated vehicle configuration data for adjusting at least one configuration in response to a setting operation of the user on at least one configuration of the vehicle;

[0173] Step ST620: In response to the user's selection operation for downloading the control, the vehicle performs a third legitimacy authentication on the mobile device when detecting a mobile device with an NFC communication function; if the mobile device passes the third legitimacy authentication, the following step ST630 is executed; if the mobile device fails the third legitimacy authentication, the following step ST670 is executed;

[0174] Step ST630: The vehicle transmits the vehicle configuration data to the NFC tag pre-stored in the mobile device;

[0175] Step ST640: The mobile device sends the updated NFC data to the cloud server;

[0176] Step ST650: the cloud server updates the pre-stored NFC data of the mobile device with the received NFC data;

[0177] Step ST660: the vehicle performs a prompt operation according to the prompt information of successful writing;

[0178] Step ST670: The vehicle performs prompt operations according to the prompt information of authentication failure.

[0179] In an embodiment of the present application, a display screen installed in a vehicle may provide a user-operable user interface to facilitate the user to set at least one configuration of the vehicle. In step ST610, the vehicle may display a setting user interface of a vehicle application to facilitate the user to input setting parameters of at least one configuration. In response to the user's setting operation for at least one configuration of the vehicle, the vehicle generates vehicle configuration data for adjusting at least one configuration. Among them, at least one configuration of the vehicle refers to a personalized configuration of the vehicle, including but not limited to at least one of the following: seat position, rearview mirror position, air conditioning temperature and air volume, speaker volume and mode, etc.

[0180] It should be understood that the vehicle can display a download control in the vehicle application, and the user can manually adjust at least one configuration before selecting to operate the download control. In response to the user's selection operation on the download control, the vehicle obtains the setting parameters of the at least one configuration and generates vehicle configuration data for adjusting the at least one configuration. In other words, the user's setting of the at least one configuration is achieved by actually adjusting the at least one configuration, rather than setting it in the setting user interface of the vehicle application displayed by the vehicle. Figure 6 The setting user interface of a vehicle displaying a vehicle application is taken as an example, but this does not constitute a limitation of the present application.

[0181] In step ST620, the vehicle may display a download control in the vehicle application, and in response to the user's selection operation on the download control, the vehicle detects a mobile device with an NFC communication function. In the embodiment of the present application, the vehicle also has an NFC communication function. When a mobile device with an NFC communication function approaches the vehicle, if the distance between the mobile device and the vehicle's NFC antenna is less than a preset distance (such as 4 cm or 10 cm, etc.), the vehicle can detect the mobile device. Optionally, the vehicle NFC works in a card reader mode, and the mobile device NFC works in a card emulation mode.

[0182] When a mobile device with NFC communication function is detected, the vehicle performs a third legitimacy authentication on the mobile device to ensure the security of the vehicle's data or services. Optionally, the vehicle performs a third legitimacy authentication on the mobile device including: the vehicle sends the first authentication data to the mobile device; the mobile device encrypts the first authentication data to obtain the second authentication data; the mobile device sends the second authentication data to the vehicle; the vehicle decrypts the second authentication data; the vehicle compares the first authentication data with the decrypted second authentication data. Among them, the encryption key and encryption method used by the mobile device to encrypt the first authentication data are consistent with the decryption key and decryption method used by the vehicle to decrypt the second authentication data. Optionally, the first authentication data is a set of random numbers, which are not less than 8 bytes. Based on this, when the first authentication data is the same as the decrypted second authentication data, the mobile device passes the third legitimacy authentication; when the first authentication data and the decrypted second authentication data are not the same, the mobile device fails the third legitimacy authentication.

[0183] In the embodiment of the present application, in order to ensure the security of data or services of the mobile device, the mobile device may optionally perform a fourth legitimacy authentication on the vehicle ( Figure 6 (not shown), including: the mobile device sends the third authentication data to the vehicle; the vehicle encrypts the third authentication data to obtain the fourth authentication data; the vehicle sends the fourth authentication data to the mobile device; the mobile device decrypts the fourth authentication data; the mobile device compares the third authentication data and the decrypted fourth authentication data. Among them, the encryption key and encryption method of the vehicle to encrypt the third authentication data are consistent with the decryption key and decryption method of the mobile device to decrypt the fourth authentication data. Optionally, the third authentication data is a set of random numbers, which is not less than 8 bytes. Based on this, when the third authentication data is the same as the decrypted fourth authentication data, the vehicle passes the fourth legitimacy authentication; when the third authentication data is different from the decrypted fourth authentication data, the vehicle fails the fourth legitimacy authentication.

[0184] It should be understood that the fourth legitimacy authentication of the vehicle by the mobile device may be performed before the third legitimacy authentication of the vehicle by the vehicle, or after the third legitimacy authentication of the mobile device by the vehicle, or may be performed simultaneously with the third legitimacy authentication of the mobile device by the vehicle, and the embodiments of the present application are not limited to this.

[0185] When the mobile device passes the third legitimacy authentication, steps ST630 to ST660 are continued. In step ST630, the vehicle transmits the vehicle configuration data to the NFC tag pre-stored in the mobile device, such as the mobile device based on Figure 5 The mobile device updates the pre-stored NFC data in response to the vehicle's write operation, modification operation and / or deletion operation on the pre-stored NFC data to obtain updated NFC data. In step ST640, since the NFC data pre-stored in the mobile device is updated, the mobile device sends the updated NFC data to the cloud server, so that in step ST650, the cloud server updates the pre-stored NFC data of the mobile device to the latest received NFC data, thereby implementing a backup of the updated NFC data.

[0186] For example, the user modifies the vehicle configuration data to modify the pre-stored NFC data based on the modification user interface displayed on the mobile device. Based on this, the mobile device responds to the user's modification operation on the pre-stored NFC data and updates the pre-stored NFC data to obtain the updated NFC data. Figure 6 The ST640 and ST650 shown in .

[0187] In step ST660, after the vehicle configuration data is transmitted to the NFC tag pre-stored in the mobile device, the vehicle performs a prompt operation according to the prompt information of successful writing to prompt the user that the vehicle configuration data has been transmitted to the NFC tag. The prompt operation can be a display operation based on the user interface of the vehicle application or a playback operation based on the audio data of the vehicle voice assistant.

[0188] When the mobile device fails the third legitimacy authentication, step ST670 is continued. In step ST670, the vehicle performs a prompt operation according to the prompt information of the authentication failure to prompt the user that the authentication of the mobile device has failed. The prompt operation can be a display operation based on the user interface of the vehicle application or a playback operation based on the audio data of the vehicle voice assistant.

[0189] To summarize, the vehicle configuration data management method provided in the embodiment of the present application transmits the vehicle configuration data generated by the vehicle to an NFC tag pre-stored in the mobile device through the NFC communication function, so that when the user subsequently uses the mobile device to approach the vehicle, the vehicle can read the vehicle configuration data stored in the NFC tag of the mobile device and adjust the personalized configuration of the vehicle according to the vehicle configuration data.

[0190] Furthermore, in the vehicle configuration data management method provided in the embodiment of the present application, when the pre-stored NFC data is updated, the mobile device sends the updated NFC data to the cloud server to update the NFC data backup stored in the cloud server, so that when the user replaces the mobile device, the backed-up NFC data can be downloaded from the cloud server to the new mobile device to complete the switching between the old and new mobile devices.

[0191] According to the seventh aspect of the present application, an embodiment of the present application provides a vehicle configuration data management method.

[0192] See also Figure 7 , Figure 7 1 is a flow chart of a vehicle configuration data management method provided by an embodiment of the present application. The vehicle configuration data management method can be applied to a vehicle configuration system, and the vehicle configuration system can include a mobile device with NFC communication function and a vehicle with NFC communication function. Figure 7 As shown, the vehicle configuration data management method may include the following steps:

[0193] Step ST710: When the vehicle detects a mobile device with NFC communication function, the vehicle performs a fifth legitimacy authentication on the mobile device; if the mobile device passes the fifth legitimacy authentication, the following step ST720 is executed; if the mobile device fails the fifth legitimacy authentication, the following step ST750 is executed;

[0194] Step ST720: The vehicle reads the vehicle configuration data in the NFC tag stored in the mobile device;

[0195] Step ST730: the vehicle adjusts at least one configuration of the vehicle according to the vehicle configuration data;

[0196] Step ST740: the vehicle performs a prompt operation according to the prompt information configured;

[0197] Step ST750: The vehicle performs a prompt operation based on the prompt information of authentication failure.

[0198] In an embodiment of the present application, both the vehicle and the mobile device have NFC communication functions. The mobile device with NFC communication functions is brought close to the vehicle with NFC communication functions. For example, the NFC of the mobile device "touches" the NFC of the vehicle, and the vehicle can detect the mobile device. When the vehicle detects the mobile device with NFC communication functions, it is necessary to perform a fifth legitimacy authentication on the mobile device to ensure the security of the vehicle's data or services. For the implementation method of the fifth legitimacy authentication, please refer to the implementation method of the third legitimacy authentication mentioned above. They can be implemented as the same legitimacy authentication method, which will not be described in detail here. To ensure the security of the data or services of the mobile device, optionally, the mobile device can perform a sixth legitimacy authentication on the vehicle. For the implementation method of the sixth legitimacy authentication, please refer to the implementation method of the fifth legitimacy authentication mentioned above. They can be implemented as the same legitimacy authentication method, which will not be described in detail here.

[0199] When the mobile device passes the fifth legitimacy authentication, continue to execute the following steps ST720 to ST740. In step ST720, the vehicle reads the NFC tag stored in the mobile device to obtain the vehicle configuration data stored in the NFC tag, such as configuration data of seat position, rearview mirror position, air conditioning temperature and air volume, speaker volume and mode, etc. In step ST730, the vehicle adjusts at least one configuration of the vehicle according to the read vehicle configuration data to achieve personalized configuration adjustment. In step ST740, after completing the personalized configuration, the vehicle performs a prompt operation according to the prompt information of the configuration completion to prompt the user that the personalized configuration of the vehicle has been completed. Among them, the prompt operation can be a display operation implemented based on the user interface of the vehicle application, or it can be a playback operation implemented based on the audio data of the vehicle voice assistant.

[0200] When the mobile device fails the fifth legitimacy authentication, the following step ST750 is continued to be executed. In step ST750, the vehicle performs a prompt operation according to the prompt information of the authentication failure to prompt the user that the authentication of the mobile device has failed. The prompt operation can be a display operation based on the user interface of the vehicle application or a playback operation based on the audio data of the vehicle voice assistant.

[0201] In summary, the vehicle configuration data management method provided in the embodiment of the present application adjusts the personalized configuration of the vehicle through an NFC tag. When the user needs to adjust the personalized configuration of the vehicle, the mobile device with NFC communication function is brought close to the vehicle with NFC communication function, so that the vehicle reads the NFC tag stored in the mobile device after detecting the mobile device, and adjusts the personalized configuration of the vehicle according to the vehicle configuration data included in the NFC tag. Based on this, the embodiment of the present application can realize the application scenario of "one person to multiple vehicles" in which different vehicles automatically adjust the personalized configuration by reading the NFC tag stored in the same mobile device, such as Fig. 9 As shown; it is also possible to realize the application scenario of "multiple people to one car" where the same vehicle automatically adjusts the personalized configuration by reading NFC tags stored in different mobile devices, such as Fig.10 As shown; the embodiments of the present application help to achieve efficient switching of the same user to different vehicles and different users to the same vehicle.

[0202] According to the eighth aspect of the present application, an embodiment of the present application provides a vehicle configuration data management method.

[0203] See also Figure 8 , Figure 8 1 is a flow chart of a vehicle configuration data management method provided by an embodiment of the present application. The vehicle configuration data management method can be applied to a vehicle configuration system, which may include a cloud server and a mobile device with NFC communication function.

[0204] like Figure 8 As shown, the vehicle configuration data management method may include the following steps:

[0205] Step ST810: the mobile device performs the seventh legitimacy authentication on the login information in response to the user's submission operation on the login information; if the login information passes the seventh legitimacy authentication, the following step ST820 is executed; if the login information fails the seventh legitimacy authentication, the following step ST850 is executed;

[0206] Step ST820: the mobile device sends a request to obtain the NFC tag to the cloud server in response to the user logging into the mobile device for the first time;

[0207] Step ST830: The cloud server sends the currently stored NFC tag to the mobile device;

[0208] Step ST840: The mobile device creates an NFC tag in the mobile device;

[0209] Step ST850: The mobile device displays a user interface according to the indication information of login failure.

[0210] In an embodiment of the present application, a mobile application installed in a mobile device may provide a user-operable user interface to facilitate user login to a user account, etc. In step ST810, the mobile device may display a login user interface of the mobile application to facilitate the user to enter login information. Optionally, the login information includes, but is not limited to, at least one of the following: a mobile phone number, name, password, email address, etc. of the user account. In an embodiment of the present application, when a user account logs in to a mobile device for the first time, the mobile device may obtain relevant information of the user account from a cloud server, such as name, password, mobile phone number, email address, etc., to facilitate authentication of the legitimacy of the login information submitted by the user. In step ST810, the mobile device needs to perform a seventh legitimacy authentication on the login information submitted by the user to verify whether the login information submitted by the user is correct, such as whether it is consistent with the relevant information of the user account obtained by the mobile device from the cloud server.

[0211] When the login information passes the seventh legitimacy authentication, the user account requested by the user to log in successfully logs in the mobile device, and steps ST820 to ST840 are continued. In step ST820, the mobile device responds to the user logging in to the mobile device for the first time, that is, the mobile device responds to the user logging in to the user account in the mobile device for the first time, and sends a request to obtain the NFC tag to the cloud server. Among them, the request to obtain the NFC tag may include relevant information of the user account to indicate to the cloud server that the user account of the NFC tag needs to be obtained. In step ST830, the cloud server sends the currently stored NFC tag to the mobile device according to the acquisition request, and the NFC tag corresponds to the user account indicated by the acquisition request. In step ST840, the mobile device creates an NFC tag in the mobile device according to the received NFC tag to realize localized storage of the NFC tag in the mobile device. Optionally, in step ST830, the cloud server may also only send the vehicle configuration data in the currently stored NFC tag to the mobile device, so that in step ST840, the mobile device creates an NFC tag in the mobile device according to the received vehicle configuration data.

[0212] When the login information fails to pass the seventh legitimacy authentication, the user account requested by the user to log in fails to log in in the mobile device, and step ST850 is continued. In step ST850, the mobile device can generate an indication of login failure, and display a user interface according to the indication of login failure to prompt the user that the login of the user account requested by the user to log in failed. Optionally, the indication of login failure also includes the reason for the login failure, such as the name does not exist, the password is wrong, the mobile phone number is wrong, the email address does not exist, etc., so that the user interface displayed by the mobile device in step ST850 is also used to prompt the user the reason for the login failure of the user account requested by the user to log in.

[0213] In summary, the vehicle configuration data management method provided in the embodiment of the present application backs up the NFC tag of the mobile device through the cloud server. When the user changes the mobile device, the backed-up NFC tag is downloaded from the cloud server to the new mobile device, and the switch between the new and old mobile devices can be completed. Fig.11 Therefore, in the embodiment of the present application, when a user changes a mobile device, the user does not need to re-register a user account and apply for a new NFC tag, thereby effectively achieving the effect of "one-time configuration and recycling" of the user account and NFC tag.

[0214] It should be understood that the above Figures 4 to 8 The embodiment describes the vehicle configuration data management method provided by the embodiment of the present application from the perspective of the interaction between the cloud server, the mobile device and the vehicle. In practical applications, the above Figures 4 to 8 Each step performed by the cloud server in the embodiment can be independently implemented as a vehicle configuration data management method on the cloud server side; Figures 4 to 8 Each step performed by the mobile device in the embodiment can be independently implemented as a vehicle configuration data management method on the mobile device side; Figures 4 to 8 Each step executed by the vehicle in the embodiment may be independently implemented as a vehicle configuration data management method on the vehicle side.

[0215] According to the ninth aspect of the present application, an embodiment of the present application provides a vehicle configuration system.

[0216] See also Fig.12 , Fig.12 is a block diagram of a vehicle configuration system provided by an embodiment of the present application, the vehicle configuration system can adjust at least one configuration of the vehicle based on an NFC (Near Field Communication) tag. Fig.12 As shown, the vehicle configuration system 1200 includes: a cloud server 1210, a mobile device 1220 with NFC communication function, and a vehicle 1230 with NFC communication function.

[0217] The cloud server 1210 is used to manage user accounts, manage and issue NFC tags, back up vehicle configuration data, etc. Fig.12 As shown, the cloud server 1210 may include a user management module 1211 , an NFC tag management and issuance module 1212 , a user and tag data management module 1213 , a cloud security service module 1214 and a cloud service 1215 .

[0218] The user management module 1211 is used for registering user accounts and maintaining user information.

[0219] The NFC tag management and issuance module 1212 is used for generating issuance data of NFC tags, issuing NFC tags, and managing and maintaining NFC tags.

[0220] The user and tag data management module 1213 is used for the management and maintenance of user data and NFC tag data, such as the management and maintenance of the mapping relationship between user accounts and NFC tags.

[0221] The cloud security service module 1214 is used to provide security services for the cloud server 1210, such as authenticating the legitimacy of the mobile device 1220 and ensuring the security of cloud data or services.

[0222] The cloud service 1215 is used to provide the required cloud services for the mobile device 1220, such as registration and management of user accounts, issuance and management of NFC tags, synchronization of cloud data to the mobile device 1220, synchronization of data of the mobile device 1220 to the cloud, etc.

[0223] The mobile device 1220 is mainly used for users to manage NFC tags, such as applying for the issuance of NFC tags, viewing or modifying vehicle configuration data, interacting with the cloud server 1210 and the vehicle 1230, etc. Optionally, the mobile device 1220 can be implemented as a smart wearable device such as a mobile phone, a tablet computer, a smart watch, an NFC-specific device, or any other device with NFC function, etc., which is not specifically limited in the embodiments of the present application. Fig.12 As shown, the mobile device 1220 may include a mobile application 1221 , a mobile security service module 1222 , and a mobile device NFC 1223 .

[0224] The mobile application 1221 is used to provide a user-operable user interface to facilitate users to register user accounts, apply for issuance of NFC tags, modify vehicle configuration data, etc.

[0225] The mobile terminal security service module 1222 is used to provide a security server for mobile devices, such as authenticating the legitimacy of the cloud server 1210 and the vehicle 1230, ensuring the security of data or services of the mobile device, etc.

[0226] The mobile device NFC 1223 is used to provide an NFC communication function and complete the communication with the vehicle NFC. Optionally, the mobile device NFC 1223 works in a card emulation mode.

[0227] The vehicle 1230 is used to generate vehicle configuration data, adjust at least one configuration of the vehicle according to the vehicle configuration data, etc. Optionally, the vehicle may be a fuel vehicle, a plug-in hybrid vehicle, or a new energy vehicle, etc., which is not specifically limited in this application. Fig.12As shown, the vehicle 1230 may include a vehicle-side application 1231 , a vehicle-side security service module 1232 , and a vehicle NFC 1233 .

[0228] The vehicle-side application 1231 is used to provide a user-operable user interface to facilitate the generation and download of vehicle configuration data, etc.

[0229] The vehicle-side security service module 1232 is used to provide security services for the vehicle, such as authenticating the legitimacy of the mobile device 1220 and ensuring the security of vehicle-side data or services.

[0230] The vehicle NFC 1233 is used to provide NFC communication function and complete the communication with the mobile device NFC. Optionally, the vehicle NFC 1233 works in the card reader mode.

[0231] It should be understood that, in specific implementation, the above modules can be implemented as independent entities, or can be arbitrarily combined and implemented as the same or several entities. In addition, the specific implementation methods and corresponding beneficial effects of the above devices and modules can be referred to the above method embodiments, which will not be described in detail here.

[0232] According to the tenth aspect of the present application, an embodiment of the present application also provides a mobile device having an NFC communication function, the mobile device comprising: a memory on which a computer program is stored; and a processor for executing the computer program in the memory to implement the vehicle configuration data management method on the mobile device side as described above.

[0233] According to the eleventh aspect of the present application, an embodiment of the present application also provides a vehicle having an NFC communication function, the vehicle comprising: a memory on which a computer program is stored; and a processor for executing the computer program in the memory to implement the vehicle configuration data management method on the vehicle side as described above.

[0234] According to the twelfth aspect of the present application, an embodiment of the present application also provides a cloud server, which includes: a memory on which a computer program is stored; a processor for executing the computer program in the memory to implement the vehicle configuration data management method on the cloud server side as described above.

[0235] According to the thirteenth aspect of the present application, the embodiment of the present application further provides a non-transitory computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, the steps of the vehicle configuration data management method on the mobile device side are implemented, or the steps of the vehicle configuration data management method on the vehicle side are implemented, or the steps of the vehicle configuration data management method on the cloud server side are implemented. The non-transitory computer-readable storage medium has all the beneficial effects of the vehicle configuration data management method, and the present application will not repeat them here.

[0236] In the description of this application, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more features. In the description of this application, the meaning of "plurality" is two or more, unless otherwise clearly and specifically defined.

[0237] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0238] The embodiments, implementation methods and related technical features of the present application can be combined and replaced with each other without conflict.

[0239] The above are only preferred embodiments of the present application and do not constitute any form of limitation to the present application. Although the present application has been described in examples with different focuses on the descriptions of various embodiments, for parts not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments. However, any simple modifications, equivalent changes and modifications made to the above embodiments based on the technical essence of the present application without departing from the content of the technical solution of the present application are within the scope of the technical solution of the present application.

Claims

1. A vehicle configuration data management method, characterized in that: Applicable to vehicles with NFC modules, including: In response to a setting operation of a user on at least one configuration of the vehicle, generating updated vehicle configuration data for adjusting the at least one configuration; When a mobile device with an NFC module is detected, the vehicle configuration data is transmitted to the mobile device, so that the mobile device updates NFC data pre-stored in the mobile device according to the vehicle configuration data.

2. The method according to claim 1, characterized in that The transmitting the vehicle configuration data to the mobile device comprises: In response to a user's selection operation on a download control, when the mobile device is detected, the vehicle configuration data is sent to an NFC tag pre-stored in the mobile device.

3. The method according to claim 1, characterized in that The method further comprises: If a mobile device with an NFC module is detected, the vehicle configuration data transmitted by the mobile device is obtained; At least one configuration of the vehicle is adjusted based on the vehicle configuration data.

4. The method according to claim 3, characterized in that Before acquiring the vehicle configuration data transmitted by the mobile device, the method further includes: authenticating the mobile device according to the target random number; After the authentication is passed, the step of acquiring the vehicle configuration data transmitted by the mobile device is performed.

5. The method according to claim 4, characterized in that The step of authenticating the mobile device according to the target random number includes: Generate a target random number according to a preset random number generation rule, and send the target random number to a mobile device; The encrypted ciphertext returned by the mobile device is obtained, and the identity of the mobile device is authenticated according to the encrypted ciphertext and the target random number.

6. The method according to claim 5, characterized in that The performing identity authentication on the mobile device according to the encrypted ciphertext and the target random number includes: decrypting the encrypted ciphertext according to a target authentication key to obtain a decrypted ciphertext, wherein the mobile device and the vehicle have the same target authentication key; If the decrypted ciphertext is consistent with the target random number, it is determined that the mobile device is authenticated.

7. The method according to any one of claims 1 to 6, characterized in that: The setting operation includes at least one of a write operation, a modify operation, and a delete operation.

8. A vehicle configuration data management method, characterized in that: Applicable to mobile devices with NFC modules, including: Update pre-stored NFC data according to the vehicle configuration data transmitted by the vehicle acquired by the NFC module, and send the updated NFC data to the cloud server; The NFC data includes vehicle configuration data, and the vehicle configuration data is used to adjust at least one configuration of the vehicle.

9. The method according to claim 8, characterized in that The method further comprises: In response to a user logging into the mobile device for the first time, sending a request to obtain the NFC tag to the cloud server; When the NFC data sent by the cloud server is received, an NFC tag is created in the mobile device.

10. The method according to claim 8, characterized in that The method further comprises: When a vehicle equipped with an NFC module is detected, NFC data stored in the NFC tag of the mobile device is transmitted to the NFC tag of the vehicle, so that the vehicle adjusts at least one configuration of the vehicle according to the NFC data.

11. A vehicle configuration data management method, characterized in that: Applied to cloud servers, including: When receiving NFC data sent by the first mobile device, updating the pre-stored NFC data of the first mobile device with the received NFC data; The NFC data includes vehicle configuration data, and the vehicle configuration data is used to adjust at least one configuration of the vehicle.

12. The method according to claim 11, characterized in that The method further comprises: When receiving the acquisition request of the NFC tag sent by the second mobile device, the issuing data of the NFC tag is sent to the second mobile device, so that the second mobile device creates the NFC tag.

13. The method according to claim 12, characterized in that After sending the issuance data of the NFC tag to the second mobile device so that the second mobile device creates the NFC tag, the method further includes: When the NFC tag creation success information sent by the second mobile device is received, the user information data in the acquisition request is associated with the NFC tag and stored.

14. The method according to claim 12, characterized in that The method further comprises: In response to a request for downloading vehicle configuration data sent by a second mobile device, obtaining user information data in the request; Querying vehicle configuration data having a corresponding association relationship with the user information data according to the user information data, and feeding back the vehicle configuration data to the second mobile device; The second mobile device is configured to have an NFC module.

15. The method according to claim 14, characterized in that The method further comprises: Acquire user registration information sent by the second mobile device, and perform legal authentication on the second mobile device according to the user registration information; When the legal authentication is passed, the user registration information is stored, and registration success information is generated and sent to the second mobile device.

16. The method according to claim 15, characterized in that Before searching for vehicle configuration data corresponding to the user information data according to the user information data and feeding back the vehicle configuration data to the second mobile device, the method further includes: Performing identity authentication on the second mobile device according to the user information data and the user registration information; When the identity authentication is passed, the vehicle configuration data having a corresponding association relationship with the user information data is queried according to the user information data, and the vehicle configuration data is fed back to the second mobile device.

17. The method according to claim 16, characterized in that The performing identity authentication on the second mobile device according to the user information data and the user registration information includes: When the user information data is consistent with the user registration information, it is determined that the identity authentication of the second mobile device is passed.

18. A vehicle, characterized in that: The vehicle has an NFC module, and the vehicle includes: a memory having a computer program stored thereon; A processor, configured to execute the computer program in the memory to implement the method according to any one of claims 1 to 7.

19. A mobile device, characterized in that: The mobile device has an NFC module, and the mobile device includes: a memory having a computer program stored thereon; A processor, configured to execute the computer program in the memory to implement the method according to any one of claims 8 to 10.

20. A cloud server, characterized in that: The cloud server comprises: a memory having a computer program stored thereon; A processor, configured to execute the computer program in the memory to implement the method according to any one of claims 11 to 17.

21. A vehicle configuration system, characterized in that: The vehicle configuration system includes the vehicle with the NFC module as claimed in claim 18 and / or the mobile device with the NFC module as claimed in claim 19, and / or the cloud server as claimed in claim 20.

22. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, it implements the vehicle configuration data management method as described in any one of claims 1 to 7, or implements the vehicle configuration data management method as described in any one of claims 8 to 10, or implements the vehicle configuration data management method as described in any one of claims 11 to 17.

Images