New energy vehicle data acquisition method, system, equipment and medium

Abstract

The invention discloses a new energy vehicle data acquisition method, system and device and a medium, and the method comprises the steps: detecting an activation state of a vehicle in response to a data acquisition request of the vehicle, and obtaining to-be-acquired data of the vehicle; when the activation state of the vehicle is first activation, sending a first data authorization request to the vehicle; a first-time authorization instruction sent by the vehicle is received, and a first-time authorization collection instruction is generated according to the first-time authorization instruction, so that the first-time authorization collection instruction is executed through the vehicle; obtaining the data type of the to-be-collected data, and determining the authorization state of the to-be-collected data based on the first authorization collection instruction; when the authorization state of the to-be-collected data is refused or unknown, sending a data authorization request associated with the to-be-collected data to the vehicle; the authorization agreement instruction of the vehicle is received, the collection instruction is sent to the vehicle, the collection instruction is executed through the vehicle, the to-be-collected data is collected, the informed property of a user on data collection can be guaranteed through multi-layer authorization, the safety risk is reduced through scene management and control, and a visual window supports the user to adjust collection authorization in real time.

Description

Technical Field

[0001] This application relates to the field of new energy vehicle data management technology, and in particular to a new energy vehicle data acquisition method, system, equipment and medium. Background Technology

[0002] New energy vehicles are a new type of automobile that uses unconventional vehicle fuels as a power source and integrates advanced power control and drive technologies. With the development of intelligence and connectivity, their data collection covers various types, including vehicle safety operation, basic services, and value-added services, and involves different application scenarios such as navigation, remote vehicle control, and in-vehicle entertainment. The authorization management of data collection is directly related to user information security and legitimate rights and interests, and is a key supporting link for the intelligent advancement of new energy vehicles.

[0003] Existing data collection technologies for new energy vehicles adopt a one-time, general authorization model. Users complete authorization without a clear understanding of the purpose and scope of use of some non-essential data, resulting in over-authorization or abuse of authorization. This not only fails to guarantee the authenticity and validity of users' informed consent, but also makes it difficult to match the data usage needs in different scenarios, thereby causing data security risks. Summary of the Invention

[0004] The following is an overview of the subject matter described in detail herein. This overview is not intended to limit the scope of the claims.

[0005] The main objective of this disclosure is to propose a method, system, device, and medium for data collection from new energy vehicles. This method can ensure users' awareness of data collection through multi-level authorization, reduce security risks through scenario-based management, and allow users to adjust collection authorization in real time through a visual window.

[0006] A first aspect of this application provides a method for collecting data from new energy vehicles, the method comprising: In response to a data collection request from a vehicle, the activation status of the vehicle is detected, and the data to be collected from the vehicle is acquired; the activation status includes at least one of initial activation and completed activation; When the vehicle is in the initial activation state, an initial data authorization request is sent to the vehicle; the initial data authorization request includes at least a first data authorization request, a second data authorization request, and a third data authorization request; the first data authorization request is a data collection request for the data required for the safe operation of the vehicle; the second data authorization request is a basic service data collection request for the vehicle; and the third data authorization request is a value-added service data collection request for the vehicle. Receive the initial authorization instruction sent by the vehicle, and generate an initial authorization collection instruction based on the initial authorization instruction, so as to execute the initial authorization collection instruction through the vehicle; The data type of the data to be collected is obtained to determine the authorization status of the data to be collected based on the initial authorization collection instruction; the data type of the data to be collected includes one of the following: data required for the safe operation of the vehicle, basic service data of the vehicle, value-added service data of the vehicle, and non-initial authorization collection data; If the authorization status of the data to be collected is rejected or unknown, a data authorization request associated with the data to be collected is sent to the vehicle. The system receives the authorization instruction from the vehicle, sends a collection instruction to the vehicle, and executes the collection instruction through the vehicle to collect the data to be collected.

[0007] The first aspect of this application provides a data collection method for new energy vehicles. In response to a data collection request from a vehicle, the method detects the vehicle's activation status and acquires the data to be collected. If the vehicle is in its initial activation state, an initial data authorization request is sent to the vehicle. An initial authorization instruction is received from the vehicle, and an initial authorization collection instruction is generated based on the initial authorization instruction to execute the initial authorization collection instruction through the vehicle. The data type of the data to be collected is obtained to determine the authorization status of the data based on the initial authorization collection instruction. If the authorization status of the data to be collected is denied or unknown, a data authorization request associated with the data to be collected is sent to the vehicle. The method receives an authorization consent instruction from the vehicle and sends a collection instruction to the vehicle to execute the collection instruction and collect the data to be collected. This method can ensure user awareness of data collection through multi-layered authorization, reduce security risks through scenario-based management, and support users in real-time adjustment of collection authorization through a visual window.

[0008] In some embodiments of this application, after responding to a vehicle's data collection request, detecting the vehicle's activation status, and acquiring the vehicle's data to be collected, the method further includes: If the vehicle's activation status is "activated," determine the authorization status of the data to be collected. If the authorization status of the data to be collected is "agree", a collection command is sent to the vehicle to execute the collection command and collect the data to be collected. If the authorization status of the data to be collected is rejected or unknown, a data authorization request associated with the data to be collected is sent to the vehicle; the vehicle's consent authorization instruction is received, and a collection instruction is sent to the vehicle to collect the data to be collected by executing the collection instruction through the vehicle.

[0009] In some embodiments of this application, the initial authorization instruction includes a first data authorization instruction, a second authorization instruction, and a third authorization instruction. Receiving the initial authorization instruction sent by the vehicle and generating an initial authorization collection instruction based on the initial authorization instruction, so as to execute the initial authorization collection instruction by the vehicle, includes: If the first data authorization instruction is "agree", the authorization status of the basic service data in the second data authorization request is updated according to the second authorization instruction, and a first authorization collection instruction is generated according to the authorization status of the basic service data in the second data authorization request; the authorization status of the basic service data in the second data authorization request includes one of "always agree" and "agree only when using"; the "always agree" indicates that the vehicle collects the basic service data in the second data authorization request in real time; the "agree only when using" indicates that the vehicle collects the basic service data in the second data authorization request when using the function corresponding to the basic service data in the second data authorization request. According to the third authorization instruction, the authorization status of the value-added service data in the third data authorization request is updated, and a second authorization collection instruction is generated based on the authorization status of the value-added service data in the third data authorization request. The authorization status of the value-added service data in the third data authorization request includes one of the following: always agree to value-added services, agree to value-added services only when used, and refuse value-added services. The always agree to value-added services indicates that the vehicle collects the value-added service data in the third data authorization request in real time. The agree to value-added services only when used indicates that the vehicle collects the value-added service data in the third data authorization request when using the function corresponding to the value-added service data in the third data authorization request. The refuse to value-added services indicates that the vehicle refuses to collect the value-added service data in the third data authorization request when using the function corresponding to the value-added service data in the third data authorization request. The first authorized collection instruction and the second authorized collection instruction are used as the initial authorized collection instruction, and the initial authorized collection instruction is executed by the vehicle.

[0010] In some embodiments of this application, the step of receiving the initial authorization instruction sent by the vehicle and generating an initial authorization collection instruction based on the initial authorization instruction, so as to execute the initial authorization collection instruction by the vehicle, further includes: If the first data authorization instruction is not responded to, an authorization reminder is sent to the vehicle, and the first authorization collection instruction is generated according to the first data authorization instruction, so that the vehicle executes the first authorization collection instruction, wherein the first authorization collection instruction indicates that the vehicle refuses to collect any data.

[0011] In some embodiments of this application, before updating the authorization status of the basic service data in the second data authorization request according to the second authorization instruction, and before generating the first authorization collection instruction according to the authorization status of the basic service data in the second data authorization request, the method further includes: If the authorization status of the basic service data in the second data authorization request is "agree to use only", the operating status of the vehicle function associated with the basic service data in the second data authorization request is monitored in real time, so as to perform the corresponding basic data collection operation according to the operating status of the vehicle function associated with the basic service data in the second data authorization request; the basic data collection operation includes collecting the basic service data in the second data authorization request when the operating status of the vehicle function associated with the basic service data in the second data authorization request is running, and terminating the collection of the basic service data in the second data authorization request when the operating status of the vehicle function associated with the basic service data in the second data authorization request is stopped. When the authorization status of the value-added service data in the third data authorization request is "Agreed upon when value-added service is used only", the operating status of the vehicle function associated with the value-added service data in the third data authorization request is monitored in real time, so as to perform the corresponding value-added data collection operation according to the operating status of the vehicle function associated with the value-added service data in the third data authorization request; the value-added data collection operation includes collecting the value-added service data in the third data authorization request when the operating status of the vehicle function associated with the value-added service data in the third data authorization request is running, and terminating the collection of the value-added service data in the third data authorization request when the operating status of the vehicle function associated with the value-added service data in the third data authorization request is stopped.

[0012] In some embodiments of this application, after obtaining the data type of the data to be collected and determining the authorization status of the data to be collected based on the initial authorization collection instruction, the method further includes: if the authorization status of the data to be collected is agreed, sending a collection instruction to the vehicle to collect the data to be collected through the vehicle.

[0013] In some embodiments of this application, after receiving the vehicle's consent authorization instruction, sending a collection instruction to the vehicle to collect and execute the collection instruction through the vehicle, and collecting the data to be collected, the method further includes: A permission status management window is configured in the vehicle's infotainment settings interface to display the permission information of the data to be collected. The permission information includes the purpose of collection, authorization status, and the most recent collection time. In response to the authorization operation request in the permission status management window, obtain the data to be operated and the operation to be performed; According to the operation to be performed, update the authorization status of the data to be operated to the corresponding authorization status; Based on the authorization status after the data to be operated is updated, a corresponding update collection instruction is generated and sent to the vehicle so that the update collection instruction can be executed by the vehicle; the update collection instruction includes continuing to collect the data to be operated and terminating the collection of the data to be operated.

[0014] To achieve the above objectives, a second aspect of the present invention provides a data acquisition system for new energy vehicles, the system comprising: A response module is used to respond to a data collection request from a vehicle, detect the activation status of the vehicle, and acquire the data to be collected from the vehicle; the activation status includes at least one of initial activation and completed activation; The authorization module is used to send an initial data authorization request to the vehicle when the vehicle's activation status is initial activation. The initial data authorization request includes at least a first data authorization request, a second data authorization request, and a third data authorization request. The first data authorization request is a data collection request for data required for the safe operation of the vehicle. The second data authorization request is a basic service data collection request for the vehicle. The third data authorization request is a value-added service data collection request for the vehicle. A generation module is used to receive the initial authorization instruction sent by the vehicle, and generate an initial authorization collection instruction based on the initial authorization instruction, so as to execute the initial authorization collection instruction through the vehicle; The acquisition module is used to acquire the data type of the data to be collected, so as to determine the authorization status of the data to be collected based on the first authorization acquisition instruction; the data type of the data to be collected includes one of the following: data required for the safe operation of the vehicle, basic service data of the vehicle, value-added service data of the vehicle, and non-first authorization acquisition data; The sending module is used to send a data authorization request associated with the data to be collected to the vehicle when the authorization status of the data to be collected is rejected or unknown; The receiving module is used to receive the authorization instruction from the vehicle, send a collection instruction to the vehicle, and execute the collection instruction through the vehicle to collect the data to be collected.

[0015] To achieve the above objectives, a third aspect of the present invention provides an electronic device, comprising: at least one control processor and a memory for communicatively connecting to the at least one control processor; the memory stores instructions executable by the at least one control processor, the instructions being executed by the at least one control processor to enable the at least one control processor to execute the above-described new energy vehicle data acquisition method.

[0016] To achieve the above objectives, a fourth aspect of the present invention provides a computer-readable storage medium storing computer-executable instructions for causing a computer to execute the above-described method for collecting data from new energy vehicles.

[0017] It is understood that the beneficial effects of the second to fourth aspects compared with the related technologies are the same as the beneficial effects of the first aspect compared with the related technologies. Please refer to the relevant description in the first aspect above, which will not be repeated here. Attached Figure Description

[0018] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the description of the embodiments taken in conjunction with the following drawings, in which: Figure 1 This is a flowchart illustrating a data collection method for new energy vehicles provided in this application; Figure 2 This is a schematic diagram of the structure of a new energy vehicle data acquisition system provided in this application; Figure 3 This is a schematic diagram of the structure of an embodiment of the electronic device provided in this application. Detailed Implementation

[0019] The embodiments of this application are described in detail below. Examples of the 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 are only used to explain this application, and should not be construed as limiting this application.

[0020] In the description of this application, the use of terms such as "first," "second," etc., is for the purpose of distinguishing technical features only and should not be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated or the order of the technical features indicated.

[0021] In the description of this application, it should be understood that the orientation descriptions, such as up, down, etc., are based on the orientation or positional relationship shown in the accompanying drawings, and are only for the convenience of describing this application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of this application.

[0022] In the description of this application, it should be noted that, unless otherwise explicitly defined, terms such as "setup," "installation," and "connection" should be interpreted broadly, and those skilled in the art can reasonably determine the specific meaning of the above terms in this application in conjunction with the specific content of the technical solution.

[0023] New energy vehicles refer to automobiles that use unconventional vehicle fuels as their power source and integrate advanced technologies in vehicle power control and drive, resulting in vehicles with advanced technical principles, new technologies, and new structures.

[0024] Currently, because data collection for new energy vehicles involves various data types and application scenarios, user data collection authorization is usually done in a one-time, general manner. This makes it impossible to implement differentiated authorization management based on data sensitivity and usage scenarios. If authorization is granted to users without a clear understanding of their intent to collect some non-essential data, it can lead to over-authorization and abuse of authorization, and the authenticity and effectiveness of users' informed consent cannot be guaranteed.

[0025] Based on this, the embodiments of this application provide a method, system, device and medium for data collection of new energy vehicles, which aims to ensure users' awareness of data collection through multi-level authorization, reduce security risks through scenario-based management and control, and support users to adjust the collection authorization in real time through a visual window.

[0026] This application provides a method, system, device, and medium for acquiring data from new energy vehicles, which will be specifically described through the following embodiments. First, a method for acquiring data from new energy vehicles in this application is described.

[0027] Therefore, referring to Figure 1 This application provides a method for collecting data from new energy vehicles. This method is applied to a central controller, which can be a server, an electronic device, or a mobile terminal, etc. There are no specific limitations here. The method includes the following steps S110 to S160.

[0028] Step S110: In response to the vehicle's data collection request, detect the vehicle's activation status and acquire the vehicle's data to be collected; the activation status includes at least one of initial activation and completed activation. Step S120: When the vehicle is in the initial activation state, send an initial data authorization request to the vehicle; the initial data authorization request includes at least a first data authorization request, a second data authorization request, and a third data authorization request; the first data authorization request is a data collection request for the data required for the safe operation of the vehicle; the second data authorization request is a basic service data collection request for the vehicle; the third data authorization request is a value-added service data collection request for the vehicle. Step S130: Receive the first authorization instruction sent by the vehicle, and generate the first authorization collection instruction according to the first authorization instruction, so as to execute the first authorization collection instruction through the vehicle; Step S140: Obtain the data type of the data to be collected, so as to determine the authorization status of the data to be collected based on the first authorization collection instruction; the data type of the data to be collected includes one of the following: data required for safe operation of the vehicle, basic service data of the vehicle, value-added service data of the vehicle, and non-first authorization collection data; Step S150: If the authorization status of the data to be collected is denied or unknown, send a data authorization request associated with the data to be collected to the vehicle. Step S160: Receive the vehicle's consent authorization instruction, send a collection instruction to the vehicle, and execute the collection instruction through the vehicle to collect the data to be collected.

[0029] In this step, in response to data collection requests triggered by the vehicle (such as collection requests generated when the user starts navigation, remote vehicle control, or other functions), the current activation status of the vehicle is first detected, and the specific data content that the vehicle needs to collect is acquired simultaneously. This data is directly related to the functions triggered by the user and is necessary data to ensure the normal operation of the functions. Among them, the activation status includes initial activation (the first time the user powers on the vehicle after it leaves the factory and has not completed the initial authorization) and completed activation (the subsequent use status after completing the initial authorization process).

[0030] Furthermore, if the vehicle is determined to be in its first activation state, an initial data authorization request is pushed to the vehicle's in-vehicle infotainment system. This initial data authorization request includes a first data authorization request, a second data authorization request, and a third data authorization request, categorized by data sensitivity and purpose, to clearly inform the user of the significance of collecting different data through a hierarchical request structure.

[0031] Specifically, the first data authorization request is for data necessary for the safe operation of the vehicle (such as battery temperature, braking system status, and other data that directly affect driving safety), the second data authorization request is for basic service data (such as vehicle location, driving speed, and other data that support basic functions such as navigation and remote vehicle control), and the third data authorization request is for value-added service data (such as driving habits, in-vehicle entertainment APP usage records, and other data that optimizes the value-added experience).

[0032] Furthermore, the system receives the initial authorization command from the user via the vehicle's infotainment system and generates a targeted initial authorization collection command based on this command. This command clarifies which data is allowed to be collected, the triggering conditions for collection, and the scope of collection. The initial authorization collection command is then sent to the vehicle, which controls the operation of each data collection module according to the command. The initial authorization command includes a first data authorization command, a second authorization command, and a third authorization command, corresponding to the consent, rejection, or specific selection of three types of data authorization requests, respectively.

[0033] Furthermore, the specific types of data to be collected are clearly defined. These types can include data required for vehicle safety operation and / or basic service data and / or value-added service data and / or data related to non-initial authorization (such as microphone voice data from an in-vehicle karaoke system, image data from a remotely viewed in-vehicle camera, etc.). Then, by comparing the data with the previously generated initial authorization collection instruction, the authorization result (agreement, rejection, or no clear authorization record) corresponding to each piece of data to be collected is determined.

[0034] Specifically, if the authorization status of the data to be collected is determined to be refused (the user explicitly does not agree to the collection) or unknown (no corresponding authorization record), a secondary authorization request strongly associated with the data to be collected is sent to the vehicle terminal. The secondary authorization request clearly explains the specific purpose of the data collection, the validity period of use, and the impact of not authorizing the current function, thus ensuring the user's right to know.

[0035] Furthermore, upon receiving the user's consent authorization instruction via the vehicle's infotainment system, a collection instruction is immediately sent to the vehicle. Upon receiving the instruction, the vehicle activates the corresponding data collection module to accurately collect the required data. If the authorization status of the data to be collected is "agree," the collection instruction is sent directly to the vehicle without the need for additional secondary authorization, quickly initiating the collection process. Moreover, the collection behavior is bound to the corresponding function, and collection terminates when the function stops.

[0036] In one embodiment, a new energy vehicle data acquisition method of this application is implemented, which realizes a new energy vehicle data acquisition system. Specifically, it includes a hierarchical authorization initialization module, a scenario-based trigger acquisition module, a permission status management module, a data compliance verification module, and an authorization strategy execution engine. This solves the problems of not being able to perform hierarchical and differentiated authorization management based on data sensitivity and usage scenarios, and the inability to guarantee the authenticity and validity of user informed consent.

[0037] The tiered authorization initialization module initiates differentiated authorization requests to users through a multi-round pop-up configuration unit, associates data usage with functional permissions using an authorization option binding unit, and outputs the initial authorization configuration data by an initial policy generation unit. Specifically, this includes: executing the first pop-up, focusing on data essential for vehicle safety operation, clearly indicating the impact of not authorizing and only providing an "Agree" option; executing the second pop-up, for basic service data, providing two options: "Always Agree" and "Agree Only When Using"; and executing the third pop-up, for value-added service data, allowing users to directly refuse without affecting the use of basic functions.

[0038] Specifically, in the authorization initialization module, to quantitatively evaluate the effectiveness of authorization interactions in each round of pop-ups, the system calculates an authorization effectiveness index. The normalization calculation formula and execution steps are as follows: ; The specific execution steps include: the system records the number of times the user interacts with each round of pop-ups. and the number of times the terms were confirmed after being correctly understood. Simultaneously monitor the average user response time and the system's preset maximum allowable response threshold Compare; in the formula To determine the number of times users clicked "confirm" after correctly understanding the authorization terms, statistics were compiled using terms comprehension quizzes and interaction characteristics such as gaze duration exceeding 2 seconds. This represents the total number of times the system sends this round of authorization requests to the user. The average response time from when the pop-up window appears to when a user makes a selection. The system's maximum allowed response time threshold is 30 seconds by default; exceeding this timeout is considered an abandoned operation. To optimize the design and interaction logic of pop-ups, if The system automatically triggers optimization and iteration of pop-up text and interaction methods.

[0039] In addition, the basic service data targeted in the second round of pop-ups includes vehicle location and speed, and its authorization options are linked to navigation and remote vehicle control functions; the value-added service data targeted in the third round of pop-ups includes driving habit data and entertainment APP usage records, and its authorization status does not affect the availability of core navigation and remote vehicle control functions. Specifically, to ensure the accuracy of the association between data and functions, the system calculates the degree of matching between data and functions. The normalization formula and execution steps are as follows: ; The specific execution steps include: the system predefines the weight coefficients for each function. and Boolean values ​​relating data and functions Iterate through all functional data items and calculate the weighted matching degree; in the formula It is a Boolean value, taking the values ​​0 and 1, representing the first... Whether the data type has a logical relationship with the current function is indicated by 1 (related) and 0 (no). This is preset by the system based on the principle of minimum necessary functionality. For the first The class function weight coefficient is calculated based on the frequency of function use and security requirements, and its value ranges from [0, 1]. The total number of function categories monitored by the system, and the matching degree. It must be greater than or equal to the threshold. Otherwise, the system will determine that the function binding logic is abnormal and automatically trigger an authorization policy review.

[0040] Furthermore, the scenario-triggered acquisition module includes receiving user function request instructions, initiating scenario-based secondary authorization through a real-time authorization verification unit, determining the data type to be acquired using a function scenario matching unit, and outputting controlled acquisition instructions through the acquisition behavior control unit.

[0041] Specifically, the scenario-triggered data collection module uses a functional scenario matching unit to determine the data types to be collected, including: monitoring user requests for non-initial authorized functions, triggering a real-time pop-up window that matches the function, clearly stating the purpose and validity period of data collection, and requiring user confirmation before starting the data collection module, and the data collection behavior automatically terminates when the function is exited.

[0042] Among them, the non-initial authorization functions include in-vehicle KTV and remote viewing of the in-vehicle camera; for the in-vehicle KTV function, the pop-up window clearly prompts that the microphone voice data is collected for sound effect optimization and indicates that this use is valid; for the remote viewing function, authorization is required through both the APP and the vehicle's terminal, and the people in the vehicle can complete the authorization through facial recognition and password verification.

[0043] Furthermore, the permission status management module displays permission details through a status visualization unit, including: setting up a dedicated management entry in the vehicle settings interface; displaying the purpose of data collection, authorization status, and the most recent collection time by data category; and providing a one-click authorization revocation switch.

[0044] Specifically, the permission status management module includes receiving authorization configuration data and controlled collection instructions, displaying permission details through a status visualization unit, and generating permission change data in response to user operations using an authorization revocation processing unit. For example, it sends an operation result prompt pop-up to the user and synchronously updates the authorization policy library in the background while freezing relevant data flow channels.

[0045] To quantify the execution efficiency of authorization revocation operations, the system calculates the authorization revocation efficiency. The normalization formula and execution steps are as follows: ; The specific execution steps include: the system records the number of times the user initiates a withdrawal request. and number of successful executions At the same time, the average processing time from request to effect of permission change is statistically analyzed. and with system reference time Comparison; in the formula This refers to the number of successfully executed withdrawal requests, i.e., the number of times the system correctly terminates data collection and updates the policy database. This represents the total number of withdrawal requests initiated by the user. The average processing time from when the user initiates the withdrawal until data collection completely stops. The baseline processing time and efficiency value set for the system. It must be greater than the threshold. If the value is below the threshold, the system will automatically initiate a diagnostic process to check for network latency and abnormal module communication.

[0046] Specifically, the data compliance verification module includes receiving permission change data and function request instructions, determining the compliance of data collection through a legal rule parsing unit, and outputting the compliance verification result using an exception handling unit. For example, legal exceptions are applied to data necessary for secure operation to exempt users from denying permissions, while the "authorization-use" binding principle is strictly enforced for non-essential data. Furthermore, a multi-layered verification mechanism is implemented for remote control functions to ensure the legitimacy of the operating entity.

[0047] To achieve quantitative management of compliance, the system calculates a comprehensive compliance score. The normalization formula and execution steps are as follows: ; The specific implementation steps include: loading the "Several Provisions on the Management of Automotive Data Security" clause library into the system and assigning weights to each clause. And assess satisfaction level in real time. ; in the formula For the first The degree of compliance with the compliance clauses is rated as follows: 1 for full compliance, 0.5 for partial compliance, and 0 for non-compliance. The regulatory importance weight of this clause is predefined by legal experts, ranging from [0, 1]. The compliance score is the total number of compliance clauses monitored by the system. It must be greater than or equal to the threshold. Otherwise, the system will automatically freeze data collection and generate a compliance risk report.

[0048] Specifically, the authorization policy execution engine integrates initial authorization configuration data, controlled data collection instructions, permission change data, and compliance verification results. It drives the start / stop status of each data collection module through a policy mapping unit, ensuring that data collection activities are under dynamic authorization control. For example, a mapping table between authorization policies and data collection modules is first established, and then changes in authorization status are monitored in real time to trigger start / stop instructions for the collection modules. The decision parameters for the start / stop instructions are weighted comprehensively. Dynamically calculated using the following normalization formula: ; in, Quantify the current user's authorization status. The compliance score output by the data compliance verification module. This is the mandatory coverage factor for the system security policy, with a value range of [0, 1]. It is 1 when an emergency security event is detected that requires mandatory termination of data collection, and 0 otherwise. , , These are preset weighting coefficients, all positive real numbers, used to adjust the importance of each factor. Set execution threshold ,when At that time, a command to allow data collection is generated. At that time, a command to terminate data collection is generated; Furthermore, a dual protection mechanism of physical isolation and logical shielding is implemented for unauthorized data modules. Specifically, to evaluate the accuracy of policy mapping, the system calculates the policy mapping precision. The normalization formula and execution steps are as follows: ; The specific execution steps include: the system periodically comparing the actual mapped data item set. The set that should be mapped to the theory Calculate the percentage of their intersection; in the formula The set of data collection items actually mapped by the system. This is the set of data collection items that should be mapped according to the authorization strategy theory. The set intersection operator represents the data items that are commonly contained in both sets. The total number of data acquisition modules supported by the system, and the mapping accuracy. Needs to be stable If any deviation occurs, the system will automatically trigger the mapping table calibration process.

[0049] Furthermore, establishing a mapping table between authorization policies and data acquisition modules specifically includes: dividing control policies into three levels based on data sensitivity. Among these, the data sensitivity level... Calculated using the following normalized evaluation model: ; in, , , This is a Boolean data identifier, taking only 0 and 1 values, representing whether the data item contains personal identification information, precise location information, or biometric information, respectively. 1 indicates yes, 0 indicates no. , , These are the normalized weighting coefficients for the corresponding information types. , This is a rounding function that outputs the integers 1, 2, and 3, corresponding to low sensitivity, medium sensitivity, and high sensitivity levels, respectively. A level threshold is set: Calculation result. This is low-sensitivity data. This is medium-sensitive data. This is highly sensitive data.

[0050] Furthermore, a default rejection policy is implemented for highly sensitive data such as driving habits and biometrics, while dynamic authorization adjustments are allowed for less sensitive data such as vehicle operating status.

[0051] In one embodiment of this example, the vehicle's initial activation process is first initiated through the hierarchical authorization initialization module. The multi-round pop-up configuration unit sequentially triggers three rounds of differentiated authorization requests: the first round focuses on data necessary for the safe operation of the vehicle, clearly indicating that not authorizing will affect driving safety and only providing an "I hate" option; the second round targets basic service data, providing two options: "Always agree" and "Agree only when using"; and the third round targets value-added service data, allowing users to directly refuse without affecting basic functions. The initial policy generation unit outputs the initial authorization configuration data accordingly, completing the accurate collection and binding of user intent.

[0052] This enables differentiated authorization management. By using a multi-round pop-up configuration unit to set differentiated authorization options for data with different sensitivities, the system solves the problem of unclear intent caused by traditional one-time general authorization. Moreover, the system outputs clear initial authorization configuration data through the initial strategy generation unit, ensuring that users have full knowledge of the intent to collect data necessary for vehicle safe operation, basic service data, and value-added service data, thereby improving the transparency of the authorization process and the precision of user control.

[0053] Furthermore, when a user uses a non-initial authorized function, the scenario-based triggering collection module is immediately activated. After the real-time authorization verification unit detects the function request instruction, it determines the data type to be collected through the function scenario matching unit and triggers a real-time pop-up window that is strongly bound to the current scenario. After the user confirms, the collection behavior control unit outputs a controlled collection instruction, and the collection behavior automatically terminates when the function is exited, ensuring that the data collection is completely synchronized with the function usage scenario.

[0054] Therefore, dynamic permission control is achieved by triggering the collection module in a scenario-based manner. The real-time authorization verification unit initiates scenario-based secondary authorization to ensure that the data collection behavior is bound to the usage scenario of non-initial authorized functions in real time. When a user uses the in-vehicle KTV and initiates a request to remotely view the in-vehicle camera, the system determines the data type to be collected through the functional scenario matching unit and outputs controlled collection instructions through the collection behavior control unit. This prevents the problem of data collection from being out of touch with actual service needs and realizes scenario-based adaptation of permission management.

[0055] Furthermore, the permission status management module provides a dedicated management entry point on the vehicle system settings interface through the status visualization unit. It dynamically displays three pieces of information: collection purpose, authorization status, and most recent collection time, based on data category. When the user operates the authorization revocation switch, the authorization revocation processing unit immediately generates permission change data: sends a termination command to the corresponding data collection module, synchronously updates the authorization policy library to freeze the data flow channel, and sends an operation result prompt pop-up to the user, realizing real-time visibility and controllability of the authorization status.

[0056] Thus, through the synergy of the permission status management module and the authorization policy execution engine, a complete permission control closed loop is constructed. The status visualization unit provides a dedicated management entry point to display the purpose of data collection, authorization status, and the most recent collection time information. Combined with the permission change data generated by the authorization revocation processing unit, it ensures that users can adjust the authorization scope in real time. At the same time, the policy mapping unit drives the start and stop status of each data collection module, realizing a default rejection policy for highly sensitive data and dynamic authorization adjustment for low-sensitivity data, thereby improving the compliance and security of the data collection process.

[0057] Furthermore, the data compliance verification module loads the provisions of the "Several Provisions on the Management of Automotive Data Security" through the statutory rule parsing unit, and implements differentiated verification for three types of data: applying statutory exceptions to exempt users from the right to refuse data necessary for safe operation, strictly enforcing the "authorization-use" binding principle for non-essential data; and initiating a multi-verification mechanism for remote control functions. The exception handling unit outputs the compliance verification results in real time to ensure that every data collection behavior complies with regulatory requirements.

[0058] Furthermore, the authorization policy execution engine integrates initial authorization configuration data, controlled collection instructions, permission change data, and compliance verification results. It drives the start and stop status of the data collection module through the policy mapping unit, establishes a mapping relationship table between authorization policies and collection modules, monitors changes in authorization status in real time, and triggers start and stop instructions: it implements a default rejection policy for highly sensitive data, allows dynamic authorization adjustments for low-sensitivity data, and ensures zero collection of unauthorized data through a dual mechanism of physical isolation and logical shielding.

[0059] Furthermore, the system continuously collects operational data from each module, evaluates the quality of pop-up interactions through an authorization effectiveness index, assesses the accuracy of algorithm execution through a strategy mapping precision evaluation, and automatically triggers an optimization iteration process when the evaluation indicators fall below a set threshold: adjusting pop-up text design, calibrating the strategy mapping table, and optimizing compliance verification weight coefficients, forming a continuously self-improving closed-loop management system to continuously enhance the accuracy and compliance level of data collection and control.

[0060] Thus, through the synergy of the permission status management module and the authorization policy execution engine, a complete permission control closed loop is constructed. The status visualization unit provides a dedicated management entry point to display the purpose of data collection, authorization status, and the most recent collection time information. Combined with the permission change data generated by the authorization revocation processing unit, it ensures that users can adjust the authorization scope in real time. At the same time, the policy mapping unit drives the start and stop status of each data collection module, realizing a default rejection policy for highly sensitive data and dynamic authorization adjustment for low-sensitivity data, thereby improving the compliance and security of the data collection process.

[0061] In some embodiments, after detecting the vehicle's activation status and acquiring the vehicle's data to be collected in response to the vehicle's data acquisition request in step S110, the method further includes the following steps S210 to S230: Step S210: If the vehicle's activation status is "activated," determine the authorization status of the data to be collected. Step S220: If the authorization status of the data to be collected is "agree", send a collection command to the vehicle to collect the data to be collected by executing the collection command through the vehicle. Step S230: If the authorization status of the data to be collected is denied or unknown, send a data authorization request associated with the data to be collected to the vehicle; receive the vehicle's consent authorization instruction, send a collection instruction to the vehicle, and collect the data to be collected by executing the collection instruction through the vehicle.

[0062] In this embodiment, when the vehicle's activation status is detected as "activated" (i.e., the vehicle has completed the initial hierarchical authorization process and the initial authorization configuration data has been stored in the authorization policy library), the historical authorization records in the authorization policy library are determined. Combined with the specific purpose of the data to be collected, the authorization status of the data to be collected is accurately determined. The determination of the authorization status is based on the selection result corresponding to the initial authorization instruction, or the updated status after subsequent adjustments by the user through the permission management window. Specifically, it is divided into three categories: "agree," "reject," and "unknown." "Unknown" specifically refers to the case where there is no corresponding authorization record for this data in the authorization policy library.

[0063] Furthermore, if the authorization status of the data to be collected is "agree," a collection instruction is sent to the vehicle, specifying the scope, format, and flow path of the data to be collected. The collection process strictly adheres to the "function-data" binding principle. If the data is basic service data (such as location data), collection will only be performed during the operation of the corresponding function (such as navigation), and will automatically terminate when the function stops. Simultaneously, the collection behavior will undergo real-time data compliance verification to ensure compliance with legal rules. The collection time will be synchronously recorded after the data collection is completed, allowing users to query it later through the permission management window.

[0064] Furthermore, if the authorization status of the data to be collected is rejected or unknown, a secondary authorization request strongly associated with the data is sent to the vehicle's in-vehicle infotainment system. The secondary authorization request can be sent via a pop-up window, which clearly explains the specific purpose of the data collection (e.g., microphone voice data is used for in-vehicle KTV sound effect optimization), the validity period of use (e.g., during the current function usage period), and the impact of not authorizing the current function (e.g., rejection will not affect the use of basic functions).

[0065] Specifically, for special functions such as remotely viewing in-vehicle cameras, an authorization request must be sent simultaneously to the vehicle-linked mobile application. The user must complete dual confirmation on both the vehicle's infotainment system and the mobile app (in-vehicle occupants can use facial recognition or password verification for assistance). Only after receiving the user's authorization is a data collection command sent to the vehicle to control the vehicle to execute the command and collect data. The data collection automatically terminates when the corresponding function is exited, and the authorization policy library is updated to record the authorization status of the data as "agreed," facilitating rapid determination of subsequent similar requests.

[0066] In some embodiments, receiving the initial authorization instruction sent by the vehicle in step S130 and generating an initial authorization collection instruction based on the initial authorization instruction to execute the initial authorization collection instruction through the vehicle includes the following steps S310 to S330: Step S310: If the first data authorization instruction is "agree", update the authorization status of the basic service data in the second data authorization request according to the second authorization instruction, and generate a first authorization collection instruction according to the authorization status of the basic service data in the second data authorization request; the authorization status of the basic service data in the second data authorization request includes one of "always agree" and "agree only when using"; "always agree" indicates that the vehicle collects the basic service data in the second data authorization request in real time; "agree only when using" indicates that the vehicle collects the basic service data in the second data authorization request when using the function corresponding to the basic service data in the second data authorization request. Step S320: According to the third authorization instruction, update the authorization status of the value-added service data in the third data authorization request, and generate a second authorization collection instruction based on the authorization status of the value-added service data in the third data authorization request; the authorization status of the value-added service data in the third data authorization request includes one of the following: always agree to value-added services, agree to value-added services only when used, and refuse value-added services; always agree to value-added services indicates that the vehicle collects the value-added service data in the third data authorization request in real time; agree to value-added services only when used indicates that the vehicle collects the value-added service data in the third data authorization request when using the function corresponding to the value-added service data in the third data authorization request; refuse to collect the value-added service data in the third data authorization request when using the function corresponding to the value-added service data in the third data authorization request. Step S330: Take the first authorized collection command and the second authorized collection command as the initial authorized collection command, and execute the initial authorized collection command through the vehicle.

[0067] In this embodiment, the authorization of the first data is contingent upon consent. Since the first data authorization request corresponds to data required for safe vehicle operation (such as battery temperature, braking system status, and other data directly related to driving safety, only a consent option is provided), the authorization configuration stage for basic service data only begins after the user confirms consent. Specifically, the basic service data includes data supporting core basic functions such as navigation and remote vehicle control, such as vehicle location and speed.

[0068] Furthermore, based on the second authorization instruction provided by the user, the authorization status is updated. This authorization status is divided into only two categories: Basic Always Agreed and Basic Only Agreed. Basic Always Agreed means the vehicle will collect this type of data in real time to meet the needs of functions requiring continuous data acquisition, such as remote vehicle control. Basic Only Agreed establishes a strong binding between data collection and function usage; for example, location data is collected only when the navigation function is enabled, and collection automatically terminates when the function is stopped. Based on this clear authorization status, a first authorization collection instruction is generated, clearly defining the triggering conditions and scope for collecting basic service data, ensuring that the collection behavior complies with the "minimum necessary" principle.

[0069] Furthermore, regarding the authorization configuration of value-added service data, the authorization status of the value-added service data is updated based on the third authorization instruction provided by the user. The authorization status of value-added service data includes three categories: always agree to value-added services, agree to value-added services only when used, and refuse value-added services. Among them, always agree to value-added services means that the vehicle collects relevant data in real time for continuous optimization of value-added services; agree to value-added services only when used means that the collection behavior is triggered only when the corresponding value-added function is running, such as collecting microphone voice data for sound effect optimization during the use of the in-vehicle KTV function; refuse value-added services means that even if the user uses the value-added function, no relevant data will be collected, and it will not affect the normal operation of the core functions.

[0070] Specifically, the value-added service data includes driving habit data, in-vehicle entertainment app usage records, and other data used to optimize the value-added experience. Its authorization status does not affect the use of core basic functions such as navigation and remote vehicle control. Then, a second authorization collection command is generated to accurately match the value-added service data collection rules with the user's authorization intent.

[0071] Furthermore, the first authorized collection instruction for basic service data and the second authorized collection instruction for value-added service data are integrated to form a complete initial authorized collection instruction. This initial authorized collection instruction covers the collection triggering conditions, scope, and limitations for different types of data, fully reflecting the core logic of hierarchical authorization.

[0072] Furthermore, the integrated initial authorization collection command is issued to the vehicle. After receiving the command, the vehicle strictly executes the data collection operation according to the command through the control mechanism of the internal data collection module, realizing differentiated and scenario-based control of data collection for basic services and value-added services, and laying a compliant and accurate initial rule foundation for subsequent data collection behavior.

[0073] In some embodiments, receiving the initial authorization instruction sent by the vehicle in step S130 and generating an initial authorization collection instruction based on the initial authorization instruction to execute the initial authorization collection instruction through the vehicle further includes the following step S410: Step S410: If the first data authorization instruction is not responded to, send an authorization reminder to the vehicle and generate an initial authorization collection instruction according to the first data authorization instruction, so that the vehicle executes the initial authorization collection instruction, wherein the initial authorization collection instruction indicates that the vehicle refuses to collect any data.

[0074] In this embodiment, control rules are formulated for the special case where the first data authorization command is not responded to in the first activation scenario. Since the first data authorization command corresponds to the data required for the safe operation of the vehicle (such as battery temperature, braking system status, and other data that directly affect driving safety), the authorization of the data required for the safe operation of the vehicle is a basic prerequisite for the compliant operation of the vehicle.

[0075] Specifically, if no confirmation is received from the user within a preset response threshold (e.g., 30 seconds, meeting the system's time control standards for authorized interactions), it is determined that the "first data authorization command has not responded." A targeted authorization reminder is then sent to the vehicle's infotainment system. This reminder can be sent via a pop-up window, clearly informing the user that "unauthorized data required for safe operation will affect driving safety; authorization is required to use the vehicle's core functions normally," reinforcing the user's understanding of the necessity of this type of authorization. Simultaneously, to ensure the compliance of data collection and the clarity of user authorization, an initial authorization collection command will be generated based on the "no response" status. This clearly indicates that the vehicle refuses to collect any type of data (including safe operation data, basic service data, value-added service data, and all other data to be collected) until the user actively responds to the first data authorization request and submits a consent command. This avoids unauthorized data collection and complies with the mandatory "informed consent" requirements for data collection under relevant regulations.

[0076] In some embodiments, before updating the authorization status of the basic service data in the second data authorization request according to the second authorization instruction in step S130, and generating the first authorization collection instruction according to the authorization status of the basic service data in the second data authorization request, the following steps S510 to S520 are further included: Step S510: If the authorization status of the basic service data in the second data authorization request is "agreement only when using", monitor the operating status of the vehicle function associated with the basic service data in the second data authorization request in real time, and perform the corresponding basic data collection operation according to the operating status of the vehicle function associated with the basic service data in the second data authorization request; the basic data collection operation includes collecting the basic service data in the second data authorization request when the operating status of the vehicle function associated with the basic service data in the second data authorization request is "running", and terminating the collection of the basic service data in the second data authorization request when the operating status of the vehicle function associated with the basic service data in the second data authorization request is "stopped running"; Step S520: If the authorization status of the value-added service data in the third data authorization request is "Agreed when using the value-added service only", monitor the operating status of the vehicle function associated with the value-added service data in the third data authorization request in real time, and perform the corresponding value-added data collection operation according to the operating status of the vehicle function associated with the value-added service data in the third data authorization request; the value-added data collection operation includes collecting the value-added service data in the third data authorization request when the operating status of the vehicle function associated with the value-added service data in the third data authorization request is "running", and terminating the collection of the value-added service data in the third data authorization request when the operating status of the vehicle function associated with the value-added service data in the third data authorization request is "stopped running".

[0077] In this embodiment, when the authorization status of basic service data is "agree when using basic data only", a real-time monitoring mechanism is activated to continuously track the vehicle function operation status corresponding to the basic service data, ensuring that data collection is strictly bound to the function usage scenario.

[0078] Specifically, if navigation, remote vehicle control, or other related functions are detected to be running, the collection of basic service data is triggered to ensure the normal operation of the functions; if the related functions are detected to be stopped (such as when the user turns off navigation), the collection of the corresponding basic service data is immediately terminated to avoid the problem of excessive collection that continues even after the function is stopped. This not only conforms to the "minimum necessary" principle of data collection, but also improves the security of data use.

[0079] Furthermore, when the authorization status of value-added service data is "Agreement only when using value-added services", the operational status of the corresponding value-added function is monitored in real time. Specifically, when a user activates value-added functions such as in-vehicle KTV, only the necessary microphone voice data and other value-added service data are collected during the operation of this function, and the purpose of the data is clearly defined as the current function adaptation needs such as sound effect optimization; when the value-added function stops running, data collection is terminated, while ensuring that even if collection is terminated, the normal use of core basic functions such as navigation and remote vehicle control will not be affected. This satisfies the user's needs for value-added services, and achieves precise control over value-added service data through dynamic binding of "function-data", avoiding data collection and transfer in irrelevant scenarios.

[0080] In some embodiments, after receiving the vehicle's consent authorization instruction in step S160 and sending a collection instruction to the vehicle to execute the collection instruction and collect the data to be collected, the method further includes the following steps S610 to S640: Step S610: Configure the permission status management window in the vehicle's in-vehicle settings interface to display the permission information of the data to be collected. The permission information includes the purpose of collection, authorization status, and the most recent collection time. Step S620: In response to the authorization operation request in the permission status management window, obtain the data to be operated and the operation to be performed; Step S630: Update the authorization status of the data to be operated on to the corresponding authorization status according to the operation to be performed; Step S640: Based on the authorization status after the data to be operated is updated, generate the corresponding update collection instruction and send the update collection instruction to the vehicle so that the vehicle can execute the update collection instruction; the update collection instruction includes continuing to collect the data to be operated and terminating the collection of the data to be operated.

[0081] In this embodiment, a dedicated permission status management window is configured in the vehicle's infotainment system settings interface, serving as the core entry point for user-managed data authorization. This window clearly displays the three key permission information for each type of data to be collected, organized by data category. Specifically, this includes the purpose of collection (e.g., location data for navigation and positioning, microphone voice data for in-vehicle karaoke sound effect optimization), the current authorization status (e.g., agreeing to basic use only, rejecting value-added services), and the most recent collection time. This allows users to intuitively understand the collection dynamics of various data types, fully guaranteeing their right to know about data authorization.

[0082] Furthermore, real-time monitoring of user authorization requests initiated through the permission status management window (such as withdrawing authorization for a certain type of data, restoring authorization for the collection of rejected data, etc.) accurately identifies the data to be operated on (i.e. the data that the user is targeting to manage, such as driving habit data, vehicle location data, etc.) and the corresponding operations to be executed (such as terminating collection, continuing collection), ensuring the relevance and accuracy of operation instructions, and laying the foundation for subsequent permission adjustments.

[0083] Furthermore, based on the user's confirmed pending operation, the authorization status of the pending data is synchronously updated to the corresponding result (e.g., if the user initiates a withdrawal operation, it is updated to "reject"; if the user initiates a recovery operation, it is updated to "agree"). At the same time, the background automatically updates the vehicle's authorization policy library to ensure that changes in authorization status take effect in real time at the system level, avoiding inconsistencies between authorization status and actual control logic, and ensuring the rigor of access control.

[0084] Furthermore, based on the updated authorization status, a corresponding update collection instruction is generated. Specifically, if the authorization status is "agree," an instruction to "continue collecting pending data" is generated; if the authorization status is "reject," an instruction to "terminate collecting pending data" is generated.

[0085] Furthermore, once the command is generated, it is immediately sent to the vehicle, which then executes the corresponding operation. Specifically, when a command to terminate data collection is executed, the data flow channel for that data is simultaneously frozen to prevent unauthorized data from flowing illegally; when a command to continue data collection is executed, data collection is started or resumed according to preset collection rules. This creates a closed loop of "visual viewing - proactive operation - status update - command execution," allowing users to adjust the authorization scope in real time and autonomously, truly achieving controllability of the authorization status.

[0086] like Figure 2 As shown in some embodiments of this application, a new energy vehicle data acquisition system is provided. The system includes a response module 210, an authorization module 220, a generation module 230, an acquisition module 240, a sending module 250, and a receiving module 260. Specifically: The response module 210 is used to respond to the vehicle's data acquisition request, detect the vehicle's activation status, and acquire the vehicle's data to be collected; the activation status includes at least one of initial activation and completed activation. The authorization module 220 is used to send an initial data authorization request to the vehicle when the vehicle is in the initial activation state. The initial data authorization request includes at least a first data authorization request, a second data authorization request, and a third data authorization request. The first data authorization request is a data collection request for the data required for the safe operation of the vehicle. The second data authorization request is a basic service data collection request for the vehicle. The third data authorization request is a value-added service data collection request for the vehicle. The generation module 230 is used to receive the initial authorization instruction sent by the vehicle and generate an initial authorization collection instruction based on the initial authorization instruction, so as to execute the initial authorization collection instruction through the vehicle; The acquisition module 240 is used to acquire the data type of the data to be collected, so as to determine the authorization status of the data to be collected based on the first authorization acquisition instruction; the data type of the data to be collected includes one of the following: data required for safe operation of the vehicle, basic service data of the vehicle, value-added service data of the vehicle, and non-first authorization acquisition data; The sending module 250 is used to send a data authorization request associated with the data to be collected to the vehicle when the authorization status of the data to be collected is rejected or unknown. The receiving module 260 is used to receive the vehicle's consent authorization instruction, send a collection instruction to the vehicle, and execute the collection instruction through the vehicle to collect the data to be collected.

[0087] It should be noted that the new energy vehicle data acquisition system provided in this embodiment is based on the same inventive concept as the above-mentioned new energy vehicle data acquisition method. Therefore, the relevant content of the above-mentioned new energy vehicle data acquisition method is also applicable to the content of the new energy vehicle data acquisition system, and therefore will not be repeated here.

[0088] To this end, the system responds to vehicle data collection requests by detecting the vehicle's activation status and acquiring the data to be collected. If the vehicle is in its initial activation state, it sends an initial data authorization request to the vehicle. It receives the initial authorization instruction from the vehicle and generates an initial authorization collection instruction based on it, which is then executed by the vehicle. The system also obtains the data type of the data to be collected to determine its authorization status based on the initial authorization collection instruction. If the authorization status of the data to be collected is denied or unknown, the system sends a data authorization request associated with the data to the vehicle. Finally, it receives the vehicle's authorization consent instruction and sends a collection instruction to the vehicle, which is then executed by the vehicle to collect the data. This multi-layered authorization ensures user awareness of data collection, scenario-based control reduces security risks, and a visual window allows users to adjust collection authorization in real time.

[0089] like Figure 3 This application also provides an electronic device, which includes: At least one memory; At least one processor; At least one program; The program is stored in memory, and the processor executes at least one program to implement the above-described method for acquiring data from new energy vehicles.

[0090] This electronic device can be any smart terminal, including mobile phones, tablets, personal digital assistants (PDAs), and in-vehicle computers.

[0091] The electronic devices according to embodiments of this application will now be described in detail.

[0092] The processor 1600 can be implemented using a general-purpose central processing unit (CPU), microprocessor, application specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of the present invention. The memory 1700 can be implemented as a read-only memory (ROM), static storage device, dynamic storage device, or random access memory (RAM). The memory 1700 can store the operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the program code is stored in the memory 1700 and is called and executed by the processor 1600 to implement a new energy vehicle data acquisition method according to an embodiment of the present invention.

[0093] The input / output interface 1800 is used to implement information input and output. The communication interface 1900 is used to enable communication and interaction between this device and other devices. Communication can be achieved through wired means (such as USB, Ethernet cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.). Bus 2000 transmits information between various components of the device (e.g., processor 1600, memory 1700, input / output interface 1800, and communication interface 1900); The processor 1600, memory 1700, input / output interface 1800 and communication interface 1900 are connected to each other within the device via bus 2000.

[0094] This invention also provides a storage medium, which is a computer-readable storage medium storing computer-executable instructions for causing a computer to execute the above-described new energy vehicle data acquisition method.

[0095] Memory, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs and non-transitory computer-executable programs. Furthermore, memory may include high-speed random access memory, and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, memory may optionally include memory remotely located relative to the processor, and these remote memories can be connected to the processor via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0096] The embodiments described in this invention are intended to more clearly illustrate the technical solutions of the embodiments of this invention, and do not constitute a limitation on the technical solutions provided by the embodiments of this invention. As those skilled in the art will know, with the evolution of technology and the emergence of new application scenarios, the technical solutions provided by the embodiments of this invention are also applicable to similar technical problems.

[0097] Those skilled in the art will understand that the technical solutions shown in the figures do not constitute a limitation on the embodiments of the present invention, and may include more or fewer steps than shown, or combine certain steps, or different steps.

[0098] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0099] Those skilled in the art will understand that all or some of the steps in the methods disclosed above, as well as the functional modules / units in the systems and devices, can be implemented as software, firmware, hardware, or suitable combinations thereof.

[0100] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0101] It should be understood that in this application, "at least one (item)" means one or more, and "more than" means two or more. "And / or" is used to describe the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0102] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0103] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0104] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0105] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes multiple instructions to cause an electronic device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing programs, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0106] The above is a detailed description of the preferred embodiments of this application. However, the embodiments of this application are not limited to the above-described implementation methods. Those skilled in the art can make various equivalent modifications or substitutions without departing from the spirit of the embodiments of this application. All such equivalent modifications or substitutions are included within the scope defined by the claims of the embodiments of this application.

Claims

1. A method for collecting data from new energy vehicles, characterized in that, The method includes: In response to a data collection request from a vehicle, the activation status of the vehicle is detected, and the data to be collected from the vehicle is acquired; the activation status includes at least one of initial activation and completed activation; When the vehicle is in the initial activation state, an initial data authorization request is sent to the vehicle; the initial data authorization request includes at least a first data authorization request, a second data authorization request, and a third data authorization request; the first data authorization request is a data collection request for the data required for the safe operation of the vehicle; the second data authorization request is a basic service data collection request for the vehicle; and the third data authorization request is a value-added service data collection request for the vehicle. Receive the initial authorization instruction sent by the vehicle, and generate an initial authorization collection instruction based on the initial authorization instruction, so as to execute the initial authorization collection instruction through the vehicle; The data type of the data to be collected is obtained to determine the authorization status of the data to be collected based on the initial authorization collection instruction; the data type of the data to be collected includes one of the following: data required for the safe operation of the vehicle, basic service data of the vehicle, value-added service data of the vehicle, and non-initial authorization collection data; If the authorization status of the data to be collected is rejected or unknown, a data authorization request associated with the data to be collected is sent to the vehicle. The system receives the authorization instruction from the vehicle, sends a collection instruction to the vehicle, and executes the collection instruction through the vehicle to collect the data to be collected.

2. The data acquisition method for new energy vehicles according to claim 1, characterized in that, After responding to a data collection request from a vehicle, detecting the vehicle's activation status, and acquiring the vehicle's data to be collected, the method further includes: If the vehicle's activation status is "activated," determine the authorization status of the data to be collected. If the authorization status of the data to be collected is "agree", a collection command is sent to the vehicle to execute the collection command and collect the data to be collected. If the authorization status of the data to be collected is rejected or unknown, a data authorization request associated with the data to be collected is sent to the vehicle; the vehicle's consent authorization instruction is received, and a collection instruction is sent to the vehicle to collect the data to be collected by executing the collection instruction through the vehicle.

3. The data acquisition method for new energy vehicles according to claim 1, characterized in that, The initial authorization instruction includes a first data authorization instruction, a second authorization instruction, and a third authorization instruction. Receiving the initial authorization instruction sent by the vehicle and generating an initial authorization collection instruction based on the initial authorization instruction, so as to execute the initial authorization collection instruction through the vehicle, includes: If the first data authorization instruction is "agree", the authorization status of the basic service data in the second data authorization request is updated according to the second authorization instruction, and a first authorization collection instruction is generated according to the authorization status of the basic service data in the second data authorization request; the authorization status of the basic service data in the second data authorization request includes one of "always agree" and "agree only when using"; the "always agree" indicates that the vehicle collects the basic service data in the second data authorization request in real time; the "agree only when using" indicates that the vehicle collects the basic service data in the second data authorization request when using the function corresponding to the basic service data in the second data authorization request. According to the third authorization instruction, the authorization status of the value-added service data in the third data authorization request is updated, and a second authorization collection instruction is generated based on the authorization status of the value-added service data in the third data authorization request. The authorization status of the value-added service data in the third data authorization request includes one of the following: always agree to value-added services, agree to value-added services only when used, and refuse value-added services. The always agree to value-added services indicates that the vehicle collects the value-added service data in the third data authorization request in real time. The agree to value-added services only when used indicates that the vehicle collects the value-added service data in the third data authorization request when using the function corresponding to the value-added service data in the third data authorization request. The refuse to value-added services indicates that the vehicle refuses to collect the value-added service data in the third data authorization request when using the function corresponding to the value-added service data in the third data authorization request. The first authorized collection instruction and the second authorized collection instruction are used as the initial authorized collection instruction, and the initial authorized collection instruction is executed by the vehicle.

4. The data acquisition method for new energy vehicles according to claim 1, characterized in that, The step of receiving the initial authorization instruction sent by the vehicle and generating an initial authorization collection instruction based on the initial authorization instruction, so as to execute the initial authorization collection instruction through the vehicle, further includes: If the first data authorization instruction is not responded to, an authorization reminder is sent to the vehicle, and the first authorization collection instruction is generated according to the first data authorization instruction, so that the vehicle executes the first authorization collection instruction, wherein the first authorization collection instruction indicates that the vehicle refuses to collect any data.

5. The data acquisition method for new energy vehicles according to claim 3, characterized in that, Before updating the authorization status of the basic service data in the second data authorization request according to the second authorization instruction, and generating the first authorization collection instruction according to the authorization status of the basic service data in the second data authorization request, the method further includes: If the authorization status of the basic service data in the second data authorization request is "agree to use only", the operating status of the vehicle function associated with the basic service data in the second data authorization request is monitored in real time, so as to perform the corresponding basic data collection operation according to the operating status of the vehicle function associated with the basic service data in the second data authorization request; the basic data collection operation includes collecting the basic service data in the second data authorization request when the operating status of the vehicle function associated with the basic service data in the second data authorization request is running, and terminating the collection of the basic service data in the second data authorization request when the operating status of the vehicle function associated with the basic service data in the second data authorization request is stopped. When the authorization status of the value-added service data in the third data authorization request is "Agreed upon when value-added service is used only", the operating status of the vehicle function associated with the value-added service data in the third data authorization request is monitored in real time, so as to perform the corresponding value-added data collection operation according to the operating status of the vehicle function associated with the value-added service data in the third data authorization request; the value-added data collection operation includes collecting the value-added service data in the third data authorization request when the operating status of the vehicle function associated with the value-added service data in the third data authorization request is running, and terminating the collection of the value-added service data in the third data authorization request when the operating status of the vehicle function associated with the value-added service data in the third data authorization request is stopped.

6. The data acquisition method for new energy vehicles according to claim 1, characterized in that, After obtaining the data type of the data to be collected and determining the authorization status of the data to be collected based on the initial authorization collection instruction, the method further includes: if the authorization status of the data to be collected is agreed, sending a collection instruction to the vehicle to collect the data to be collected through the vehicle.

7. The data acquisition method for new energy vehicles according to claim 1, characterized in that, After receiving the vehicle's consent authorization instruction, sending a collection instruction to the vehicle, and collecting the data to be collected via the vehicle, the method further includes: A permission status management window is configured in the vehicle's infotainment settings interface to display the permission information of the data to be collected. The permission information includes the purpose of collection, authorization status, and the most recent collection time. In response to the authorization operation request in the permission status management window, obtain the data to be operated and the operation to be performed; According to the operation to be performed, update the authorization status of the data to be operated to the corresponding authorization status; Based on the authorization status after the data to be operated is updated, a corresponding update collection instruction is generated and sent to the vehicle so that the update collection instruction can be executed by the vehicle; the update collection instruction includes continuing to collect the data to be operated and terminating the collection of the data to be operated.

8. A data acquisition system for new energy vehicles, characterized in that, The system includes: A response module is used to respond to a data collection request from a vehicle, detect the activation status of the vehicle, and acquire the data to be collected from the vehicle; the activation status includes at least one of initial activation and completed activation; The authorization module is used to send an initial data authorization request to the vehicle when the vehicle's activation status is initial activation. The initial data authorization request includes at least a first data authorization request, a second data authorization request, and a third data authorization request. The first data authorization request is a data collection request for data required for the safe operation of the vehicle. The second data authorization request is a basic service data collection request for the vehicle. The third data authorization request is a value-added service data collection request for the vehicle. A generation module is used to receive the initial authorization instruction sent by the vehicle, and generate an initial authorization collection instruction based on the initial authorization instruction, so as to execute the initial authorization collection instruction through the vehicle; The acquisition module is used to acquire the data type of the data to be collected, so as to determine the authorization status of the data to be collected based on the first authorization acquisition instruction; the data type of the data to be collected includes one of the following: data required for the safe operation of the vehicle, basic service data of the vehicle, value-added service data of the vehicle, and non-first authorization acquisition data; The sending module is used to send a data authorization request associated with the data to be collected to the vehicle when the authorization status of the data to be collected is rejected or unknown; The receiving module is used to receive the authorization instruction from the vehicle, send a collection instruction to the vehicle, and execute the collection instruction through the vehicle to collect the data to be collected.

9. An electronic device, characterized in that, It includes at least one control processor and a memory for communicatively connecting to the at least one control processor; the memory stores instructions executable by the at least one control processor, which, when executed by the at least one control processor, enable the at least one control processor to perform a new energy vehicle data acquisition method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which are used to cause a computer to perform a data acquisition method for new energy vehicles as described in any one of claims 1 to 7.

Images