Data reading method and system for vehicle EEPROM and electronic equipment

Abstract

The invention relates to the technical field of vehicle data management, and discloses a data reading method and system for a vehicle EEPROM (Electrically Erasable Programmable Read-Only Memory) and electronic equipment. According to the method, variable storage spaces corresponding to a plurality of application layer modules are divided according to a plurality of data reading types, various kinds of similar data are obtained, data cache spaces corresponding to the similar data are generated, target data of a vehicle EEPROM are read according to an interface calling type and the data reading type, a data updating strategy is matched, and the target data of the vehicle EEPROM are updated. The data updating strategy is used for sequentially updating the data of the data cache space and the variable storage space according to the target data, so that the application layer module reads the data of the vehicle EEPROM by reading the corresponding variable storage space; the data updating of the variable storage space is adaptively configured based on different interface calling types and data reading types, so that a unified data access mechanism is realized, and the data reading efficiency of the vehicle EEPROM is improved.

Description

Technical Field

[0001] The present invention relates to the technical field of vehicle data management, and in particular to a data reading method, system and electronic equipment for vehicle EEPROM. Background Art

[0002] In the vehicle electronic system architecture, the application layer module accesses the electrically erasable programmable read-only memory (EEPROM) by calling the underlying interface of the non-volatile memory (NVM) in the underlying software (BSW, Basic Software Layer). The interface calling mechanism includes synchronous calling and asynchronous calling. The synchronous calling type adopts a blocking working mode. The caller must wait for the underlying interface to complete the data read and write operation and return the execution result before continuing the subsequent business process, which can ensure the strict controllability of the operation timing. The asynchronous calling mechanism supports non-blocking operations. The caller can release the execution resources immediately after initiating the read and write request. After the underlying interface completes the data operation, the result is returned through the callback function or event notification mechanism, effectively improving the utilization of system resources.

[0003] However, with the evolution of automotive intelligence, the number of application layer functional modules has increased exponentially. Multiple application layer modules directly call the underlying interfaces, forming a tightly coupled architecture. In addition, different application layer modules use a mixed synchronous / asynchronous calling method to concurrently access the EEPROM. Due to the lack of a unified data access scheduling and arbitration mechanism, there is resource competition in the interface calls between application layer modules, which causes EEPROM bus arbitration delays, resulting in low data reading efficiency of the vehicle EEPROM. Summary of the Invention

[0004] In order to provide a basic understanding of some aspects of the disclosed embodiments, a brief summary is given below. The summary is not an extensive review, nor is it intended to identify key / critical elements or delineate the scope of protection of these embodiments, but rather serves as a prelude to the detailed description that follows.

[0005] In view of the above-mentioned shortcomings of the prior art, the present application provides a method, system and electronic device for reading data from a vehicle EEPROM to improve the data reading efficiency of the vehicle EEPROM.

[0006] The present application provides a data reading method for a vehicle EEPROM, comprising: obtaining variable storage spaces corresponding to multiple application layer modules, wherein the variable storage spaces store data variables required by the application layer modules; dividing the data variables according to multiple data reading types to obtain similar data corresponding to each data reading type, and generating data cache spaces according to each similar data; calling the data reading interface of the vehicle EEPROM according to the current call type to obtain target data corresponding to the current reading type, and matching the data update strategy corresponding to the target data using the current call type and / or the current read type as a matching basis, wherein the current call type is any interface call type and the current read type is any data read type; executing the data update strategy to update the data cache space corresponding to the target data according to the target data, and updating the variable storage space according to the data cache space after the data update, so that the application layer module can read the data of the vehicle EEPROM by reading the variable storage space corresponding to the application layer module.

[0007] In one embodiment of the present application, data cache space is generated respectively according to each of the similar data, including at least one of the following: obtaining a reference space length corresponding to a data reading type, and dividing the similar data corresponding to the data reading type according to the reference space length, so as to divide the similar data stored in one or more variable storage spaces into a similar data set, and generating data cache space corresponding to each of the similar data sets according to the reference space length, wherein the amount of similar data in the similar data set is less than or equal to the reference space length; obtaining a target space length corresponding to a data reading type, and generating a data cache space corresponding to the data reading type according to the target space length, wherein the similar data corresponding to the data reading type corresponds to the data elements of the data cache space.

[0008] In one embodiment of the present application, the data cache space corresponding to the target data is updated according to the target data, and the variable storage space is updated according to the data cache space after the data update in the following manner: one or more data cache spaces corresponding to the current read type are respectively used as current cache spaces, and the target data includes the current data corresponding to each of the current cache spaces, wherein the current data includes data to be updated and data verification information; if each of the data verification information meets the preset data verification value, then the data of each current cache space is updated according to each of the data to be updated, and the variable storage space is updated according to the current cache space after the data update.

[0009] In one embodiment of the present application, data is updated on each of the current cache spaces according to each of the data to be updated, and data is updated on the variable storage space according to the current cache space after the data update, including at least one of the following: if the current call type is a synchronous call type, and the current read type is an immediate write read type, then the number of the current cache spaces is multiple; if each of the data verification information satisfies the data verification value, then data is updated on each of the current cache spaces according to each of the data to be updated, and data is updated on the variable storage space according to the current cache space after the data update; if the current The call type is a synchronous call type, and the current read type is a delayed write read type, then the number of the current cache space is one; if the data verification information satisfies the data verification value, the current cache space is updated according to the data to be updated, and the variable storage space is updated according to the current cache space after the data update; if the current call type is an asynchronous call type, and the current read type is an immediate write read type, then the number of the current cache space is multiple; the preset shared cache space is assigned in turn according to each current data; in response to the data in the shared cache space The verification information satisfies the data verification value, and the current cache space is updated according to the data to be updated in the shared cache space; if the data to be updated have completed the data update of the current cache space, the variable storage space is updated according to the current cache space; if the current call type is an asynchronous call type, and the current read type is an immediate write read type, the number of the current cache spaces is multiple, and the current data also includes a data function identifier; the preset cache space corresponding to each data function identifier is assigned a value according to each current data; in response to the data verification information in any preset cache space satisfying The data verification value is used to update the current cache space according to the data to be updated in the preset cache space; if all the data to be updated have completed the data update of the current cache space, the variable storage space is updated according to the current cache space; if the current call type is an asynchronous call type and the current read type is a delayed write read type, the number of the current cache space is one; if the data verification information all meets the data verification value, the current cache space is updated according to the data to be updated, and the variable storage space is updated according to the current cache space after the data update.

[0010] In one embodiment of the present application, the method also includes at least one of the following: if the current call type is a synchronous call type, then in response to the data update of the variable storage space, the status flag bits corresponding to each current cache space are set respectively according to the data verification information in the target data; if the current call type is an asynchronous call type, then in response to obtaining the target data, the status flag bits corresponding to each current cache space are set respectively according to the data verification information in the target data, and whether the data verification information meets the data verification value is determined based on the comparison result between the status flag bits and the data verification value.

[0011] In one embodiment of the present application, the method further includes: if the current call type is a synchronous call type, and any data verification information does not meet the data verification value, obtaining the call retry count corresponding to the synchronous call type; if the call retry count corresponding to the synchronous call type is less than or equal to a preset retry count threshold, increasing the call retry count corresponding to the current call type, and re-calling the data reading interface corresponding to the current read type according to the current call type to update the target data; if the call retry count corresponding to the synchronous call type is greater than the retry count threshold, updating the variable storage space according to the current cache space; if the current call type is an asynchronous call type, and any data verification information does not meet the data verification value, comparing the status flag corresponding to the data verification information according to a preset retry flag, and obtaining the call retry count corresponding to the asynchronous call type; if the status flag corresponding to the data verification information does not meet the retry flag, and the call retry count corresponding to the asynchronous call type is less than or equal to the retry count threshold, setting the data verification flag according to the retry flag. The state flag bit corresponding to the data verification information is determined, the call retry count corresponding to the current call type is increased, and the data reading interface corresponding to the current read type is re-called according to the current call type to update the target data; if the state flag bit corresponding to the data verification information does not satisfy the retry flag bit, and the call retry count corresponding to the asynchronous call type is greater than the retry count threshold, the variable storage space is updated according to the current cache space; if the state flag bit corresponding to the data verification information satisfies the retry flag bit, the time when the state flag bit satisfies the retry flag bit is counted to obtain the duration; if the duration is greater than the preset duration threshold, and the call retry count corresponding to the asynchronous call type is less than or equal to the retry count threshold, the call retry count corresponding to the current call type is increased, and the data reading interface corresponding to the current read type is re-called according to the current call type to update the target data; if the duration is greater than the duration threshold, and the call retry count corresponding to the asynchronous call type is greater than the retry count threshold, the variable storage space is updated according to the current cache space.

[0012] In one embodiment of the present application, the application layer module reads the variable storage space in the following manner: obtaining the status flag corresponding to each of the data cache spaces; if each of the space flags satisfies the data verification value, executing the first reading method, wherein the first reading method includes extracting data from the variable storage space corresponding to the application layer module to obtain the data variable corresponding to the application layer module; if any status flag satisfies the retry flag, waiting for the variable storage space to update the data and counting the waiting time; if the waiting time is greater than a preset waiting time threshold, executing the second reading method, wherein the second reading method includes setting the data variable corresponding to the application layer module according to a preset initial value; if any flag does not satisfy the data verification value and the retry flag, executing the first reading method or the second reading method.

[0013] In one embodiment of the present application, the method further includes: obtaining a task duration corresponding to a data reading task, and determining a task duration threshold based on multiple task durations, wherein the data reading task includes calling a data reading interface of the vehicle EEPROM according to a current call type, obtaining target data corresponding to the current read type, and using the current call type and / or the current read type as a matching basis to match a data update strategy corresponding to the target data, and executing the data update strategy; in response to the task duration of any data reading task being greater than or equal to the task duration threshold, interrupting execution of the data reading task.

[0014] The present application provides a data reading system for a vehicle EEPROM, comprising: an acquisition module, configured to acquire variable storage spaces corresponding to a plurality of application layer modules, wherein the variable storage spaces store data variables required by the application layer modules; a generation module, configured to divide the data variables according to a plurality of data reading types, obtain similar data corresponding to each data reading type, and generate data cache spaces based on each similar data; a matching module, configured to call a data reading interface of the vehicle EEPROM according to a current call type, obtain target data corresponding to the current read type, and match a data update strategy corresponding to the target data using the current call type and / or the current read type as a matching basis, wherein the current call type is any interface call type and the current read type is any data read type; and an execution module, configured to execute the data update strategy, update the data cache space corresponding to the target data according to the target data, and update the variable storage space according to the data cache space after the data update, so that the application layer module reads data from the vehicle EEPROM by reading the variable storage space corresponding to the application layer module.

[0015] The present application provides an electronic device, comprising: a processor and a memory; the memory is used to store a computer program, and the processor is used to execute the computer program stored in the memory, so that the electronic device performs the above method.

[0016] Beneficial effects of this application:

[0017] By dividing the variable storage spaces corresponding to multiple application layer modules according to various data read types, various similar data are obtained, and data cache spaces corresponding to each similar data are generated. Then, the target data of the vehicle EEPROM is read according to the interface call type and the data read type, and a data update strategy is matched. The data update strategy is used to sequentially update the data cache space and the variable storage space according to the target data, so that the application layer module can read the data from the vehicle EEPROM by reading the corresponding variable storage space. In this way, compared with the application layer module directly calling the underlying interface, the variable storage space and the data cache space are set to decouple the application layer module from the underlying software, so that the application layer interface can read the data from the vehicle EEPROM by reading the corresponding variable storage space. Moreover, through the matching mechanism of the data update strategy, the data update of the variable storage space is adaptively configured based on different interface call types and data read types, thereby realizing a unified data access mechanism and improving the data reading efficiency of the vehicle EEPROM. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 This is a flow chart of a method for reading data from a vehicle EEPROM in an embodiment of the present application;

[0019] Figure 2 This is a schematic structural diagram of a system architecture for implementing a method for reading data from a vehicle EEPROM in an embodiment of the present application;

[0020] Figure 3 This is a schematic diagram of the structure of a data cache space in an embodiment of the present application;

[0021] Figure 4 This is a flow chart of an EEPROM data update method based on a synchronous call type and an immediate write and read type in an embodiment of the present application;

[0022] Figure 5 This is a flow chart of an EEPROM data update method based on a synchronous call type and a delayed write-read type in an embodiment of the present application;

[0023] Figure 6 This is a flow chart of an EEPROM data update method based on an asynchronous call type and an immediate write and read type in an embodiment of the present application;

[0024] Figure 7 1 is a flow chart of another EEPROM data update method based on asynchronous call type and immediate write and read type in an embodiment of the present application;

[0025] Figure 8 This is a flow chart of an EEPROM data update method based on an asynchronous call type and a delayed write-read type in an embodiment of the present application;

[0026] Figure 9 This is a schematic structural diagram of a data reading system for a vehicle EEPROM in an embodiment of the present application;

[0027] Figure 10 It is a schematic structural diagram of an electronic device in an embodiment of the present invention. DETAILED DESCRIPTION

[0028] The following describes the embodiments of the present invention through specific examples. Those skilled in the art can easily understand other advantages and effects of the present invention from the content disclosed in this specification. The present invention can also be implemented or applied through different specific embodiments. The details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of the present invention. It should be noted that the following embodiments and sub-samples in the embodiments can be combined with each other unless there is a conflict.

[0029] It should be noted that the illustrations provided in the following embodiments are merely schematic illustrations of the basic concept of the present invention. Therefore, the illustrations only show components related to the present invention and are not drawn according to the number, shape, and size of components in actual implementation. In actual implementation, the type, quantity, and proportion of each component may be changed arbitrarily, and the component layout may also be more complex.

[0030] In the following description, numerous details are discussed to provide a more thorough explanation of the embodiments of the present invention. However, it will be apparent to those skilled in the art that the embodiments of the present invention may be practiced without these specific details. In other embodiments, well-known structures and devices are shown in block diagram form rather than in detail to avoid obscuring the embodiments of the present invention.

[0031] The terms "first," "second," and the like in the specification and claims of this application and the accompanying drawings are used to distinguish similar items and are not necessarily used to describe a particular order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate for the embodiments of the present application described herein. In addition, the terms "including," "having," and any variations thereof are intended to cover non-exclusive inclusions.

[0032] Unless otherwise stated, the term "plurality" means two or more.

[0033] In this application, the character " / " indicates that the preceding and following objects are in an "or" relationship. For example, A / B means: A or B.

[0034] The term "and / or" describes an association between objects, indicating that three relationships can exist. For example, A and / or B means: A or B, or A and B.

[0035] Combine Figure 1 As shown, the present application provides a method for reading data from a vehicle EEPROM, comprising:

[0036] Step S101, obtaining variable storage spaces corresponding to multiple application layer modules;

[0037] Among them, the variable storage space stores data variables required by the application layer module;

[0038] Step S102 , dividing each data variable according to multiple data reading types, obtaining data of the same type corresponding to each data reading type, and generating data cache space according to each data of the same type;

[0039] Step S103: calling the data reading interface of the vehicle EEPROM according to the current call type, obtaining the target data corresponding to the current read type, and matching the data update strategy corresponding to the target data using the current call type and / or the current read type as a matching basis;

[0040] Among them, the current call type is any interface call type, and the current read type is any data read type;

[0041] Step S104, execute the data update strategy to update the corresponding data cache space according to the target data, and update the variable storage space according to the data cache space after the data update, so that the application layer module can read the data of the vehicle EEPROM by reading the corresponding variable storage space.

[0042] The vehicle EEPROM data reading method provided in this application divides the variable storage spaces corresponding to multiple application layer modules according to multiple data read types, obtains various types of data, and generates data cache spaces corresponding to each type of data. The target data of the vehicle EEPROM is then read according to the interface call type and the data read type. A data update strategy is then matched to sequentially update the data cache space and the variable storage space based on the target data using the data update strategy, so that the application layer module reads data from the vehicle EEPROM by reading the corresponding variable storage space. Thus, compared to the application layer module directly calling the underlying interface, the variable storage space and the data cache space are decoupled from the underlying software by setting the variable storage space and the data cache space, allowing the application layer interface to read data from the vehicle EEPROM by reading the corresponding variable storage space. Furthermore, through the matching mechanism of the data update strategy, the data update of the variable storage space is adaptively configured based on different interface call types and data read types, thereby achieving a unified data access mechanism and improving the efficiency of vehicle EEPROM data reading.

[0043] Combine Figure 2 As shown, the present application provides a system architecture, including an application layer, a storage agent and underlying software.

[0044] The application layer includes multiple application layer modules, which are used to read data from the vehicle EEPROM by reading the corresponding variable storage space.

[0045] In some embodiments, the number of application layer modules is N, and the number of data variables required by the i-th application layer module is N. i , where i∈[1,N].

[0046] The storage agent is used to implement a data reading method for a vehicle EEPROM, including: obtaining variable storage spaces corresponding to multiple application layer modules; dividing each data variable according to multiple data reading types to obtain similar data corresponding to each data reading type, and generating data cache space according to each similar data; calling the data reading interface of the vehicle EEPROM according to the current call type to obtain target data corresponding to the current read type, and matching the data update strategy corresponding to the target data with the current call type and / or the current read type as the matching basis; executing the data update strategy to update the corresponding data cache space according to the target data, and updating the variable storage space according to the data cache space after the data update.

[0047] In some embodiments, the data read type includes an immediate write read type, a delayed write read type, and the like.

[0048] In some embodiments, the interface call type includes a synchronous call type, an asynchronous call type, and the like.

[0049] In some embodiments, the variable storage space and the data storage space are both array types, wherein the variable storage space corresponding to the i-th application layer module is represented as M(i)=(m i,j ), m i,j is the jth data variable corresponding to the i-th application layer module, j∈[1,N i ].

[0050] In some embodiments, the data variable m i,j The corresponding default value is expressed as This default value is agreed upon by the application layer module to the storage agent. This default value has no practical significance and does not affect the normal operation of vehicle functions and applications. i,j If the corresponding target data fails to be read, the default value is used. Set the data variable m i,j .

[0051] The underlying software is provided with a non-volatile memory, wherein the non-volatile memory includes a data read interface (NVMRead interface) and a data write interface (NVMWrite interface).

[0052] Optionally, data cache space is generated respectively according to each type of data, including: obtaining a reference space length corresponding to any data reading type, and dividing the similar data corresponding to the data reading type according to the reference space length, so as to divide the similar data stored in one or more variable storage spaces into a similar data set, and generating data cache space corresponding to each similar data set according to the reference space length, wherein the amount of similar data in the similar data set is less than or equal to the reference space length.

[0053] In some embodiments, the reference space length corresponding to the immediate write read type is 32 bytes, and one or more data cache spaces corresponding to the immediate write read type are generated according to the reference space length, wherein the kth data cache space corresponding to the immediate write read type is represented by A(k)=(a k,1 ,a k,2 ,…,a k,32 ).

[0054] In some embodiments, if a corresponding data variable exists for a data element in the data cache space corresponding to the immediate write read type, the data variable is used as the default value corresponding to the data element; and if a corresponding data variable does not exist for a data element in the data cache space corresponding to the immediate write read type, a preset element default value is used as the default value corresponding to the data element, for example, the element default value is 255.

[0055] Combine Figure 3 As shown, the variable storage space includes space 1, space 2 and space 3. The number of similar data corresponding to the immediate write and read type distributed in space 1, space 2 and space 3 are 24, 6 and 18 respectively. The similar data in space 1 and space 2 are set as one similar data set, and the similar data in space 3 are set as another similar data set. Data cache spaces A(1) and A(2) are set according to the two similar data sets.

[0056] In this way, compared with setting a corresponding data cache space for each variable storage space, the similar data stored in one or more variable storage spaces are divided into a similar data set, and the data cache space corresponding to each similar data set is generated according to the benchmark space length. This can reduce the number of data cache spaces corresponding to the immediate write read type and reduce the frequency of interaction between the data cache space and the data reading interface.

[0057] Optionally, data cache space is generated respectively according to each type of data, including: obtaining the target space length corresponding to any data reading type, and generating the data cache space corresponding to the data reading type according to the target space length, wherein the type of data corresponding to the data reading type corresponds to the data elements of the data cache space.

[0058] Combine Figure 3 As shown, the target space length corresponding to the delayed write read type is 512 bytes, and the data cache space corresponding to the delayed write read type is generated according to the target space length, wherein the data cache space corresponding to the delayed write read type is expressed as B=(b1, b2, ..., b 512 ).

[0059] In some embodiments, if a corresponding data variable exists for a data element in the data cache space corresponding to the delayed write read type, the data variable is used as the default value corresponding to the data element; and if a corresponding data variable does not exist for a data element in the data cache space corresponding to the delayed write read type, a preset element default value is used as the default value corresponding to the data element, for example, the element default value is 255.

[0060] Optionally, the corresponding data cache space is updated according to the target data, and the variable storage space is updated according to the data cache space after the data update in the following manner: one or more data cache spaces corresponding to the current read type are respectively used as current cache spaces, and the target data includes the current data corresponding to each current cache space, wherein the current data includes the data to be updated and data verification information; if each data verification information meets the preset data verification value, then the data of each current cache space is updated according to each data to be updated, and the variable storage space is updated according to the current cache space after the data update.

[0061] In some embodiments, the data verification value is 0.

[0062] Optionally, each current cache space is updated according to each data to be updated, and the variable storage space is updated according to the current cache space after the data update, including: if the current call type is a synchronous call type, and the current read type is an immediate write read type, then the number of current cache spaces is multiple; if each data verification information satisfies the data verification value, then each current cache space is updated according to each data to be updated, and the variable storage space is updated according to the current cache space after the data update.

[0063] Optionally, the method further includes: if the current call type is a synchronous call type, in response to data update of the variable storage space, setting status flags corresponding to each current cache space according to each data verification information in the target data.

[0064] In some embodiments, the status flag is a 16-byte binary format data, and the status flag corresponding to the data cache space x is represented by S x , x is A(k) or B, where the status flag S x The default value is "11111111 11111111".

[0065] Optionally, the method also includes: if the current call type is a synchronous call type, and any data verification information does not meet the data verification value, then obtaining the call retry count corresponding to the synchronous call type; if the call retry count corresponding to the synchronous call type is less than or equal to a preset retry count threshold, then increasing the call retry count corresponding to the current call type, and re-calling the data reading interface corresponding to the current read type according to the current call type to update the target data; if the call retry count corresponding to the synchronous call type is greater than the retry count threshold, then updating the variable storage space according to the current cache space.

[0066] In some embodiments, the number of call retries corresponding to the synchronous call type is expressed as TIME(1), and the number of call retries corresponding to the asynchronous call type is expressed as TIME(2), wherein the default values ​​corresponding to the number of call retries TIME(1) and the number of call retries TIME(2) are both 0.

[0067] Combine Figure 4 As shown, the present application provides an EEPROM data update method based on a synchronous call type and an immediate write-read type, comprising:

[0068] Step S401, setting the data cache space, variable storage space, status flag and call retry times according to their respective default values;

[0069] Step S402: calling the data reading interface corresponding to the immediate write and read type according to the synchronous call type to obtain the target data;

[0070] The data reading interface is called according to the read block ID and data length to obtain target data, which includes the current data corresponding to each current cache space;

[0071] Among them, the current data includes DATA data D[A(k)] = (d0, d1, d2, ...) and ERR error information e[A(k)], d0 is the data error flag (ErrorFlag), d0 and e[A(k)] are used as data verification information, and the remaining data is used as data to be updated;

[0072] Step S403, determine whether all data verification information meets the data verification value, if so, jump to step S404, if not, jump to step S406;

[0073] Wherein, if d0=0 and e[A(k)]=0, it means that the data verification information satisfies the data verification value;

[0074] Step S404 , updating data in each current cache space corresponding to the immediate write / read type according to each data to be updated, and updating data in the variable storage space according to the current cache space after the data update;

[0075] Step S405: updating the status flags corresponding to the respective current cache spaces according to the data verification information.

[0076] Among them, the status flag S A(k) ={e[A(k)]<<8}∨d0, for example, ERR error information e[A(k)]=00001000, data error flag d0=00000010, then {e[A(k)]<<8}=00001000 00000000, and then perform bitwise OR operation∨ on {e[A(k)]<<8} according to data error flag d0 to obtain status flag S A(k) =0000100000000010;

[0077] Step S406, obtaining the call retry count corresponding to the synchronous call type;

[0078] If ≠0 or e[A(k)]≠0, it means that the data verification information does not meet the data verification value;

[0079] Step S407, determine whether the call retry count is greater than the retry count threshold, if so, jump to step S408, if not, jump to step S409;

[0080] Step S408, updating the variable storage space according to the current cache space;

[0081] Among them, if the call retry count is greater than the retry count threshold, the interface call retry mechanism is stopped.

[0082] Step S409: increase the call retry count corresponding to the synchronous call type, and re-call the data reading interface corresponding to the immediate write read type according to the synchronous call type to update the target data, and jump to step S403.

[0083] Optionally, data is updated in each current cache space according to each data to be updated, and data is updated in the variable storage space according to the current cache space after the data update, including: if the current call type is a synchronous call type, and the current read type is a delayed write read type, then the number of current cache spaces is one; if the data verification information satisfies the data verification value, then the current cache space is updated according to the data to be updated, and data is updated in the variable storage space according to the current cache space after the data update.

[0084] Combine Figure 5 As shown, the present application provides an EEPROM data update method based on a synchronous call type and a delayed write-read type, comprising:

[0085] Step S501, setting the data cache space, variable storage space, status flag and call retry times according to their respective default values;

[0086] Step S502: calling the data reading interface corresponding to the delayed write read type according to the synchronous call type to obtain the target data;

[0087] The data reading interface is called according to the read block ID and data length to obtain target data, which includes the current data corresponding to each current cache space;

[0088] Among them, the current data includes DATA data D[B] = (d0, d1, d2, ...) and ERR error information e[B], d0 is the data error flag, d0 and e[B] are used as data verification information, and the remaining data is used as data to be updated;

[0089] Step S503, determine whether the data verification information meets the data verification value, if so, jump to step S504, if not, jump to step S505;

[0090] Wherein, if = 0 and e[B] = 0, it means that the data verification information satisfies the data verification value;

[0091] Step S504 , updating the current cache space corresponding to the delayed write read type according to the data to be updated, and updating the variable storage space according to the current cache space after the data update;

[0092] Step S505: update the status flag corresponding to the current cache space according to the data verification information.

[0093] Among them, the status flag s B ={e[B]<<8}∨d0;

[0094] Step S506, obtaining the call retry count corresponding to the synchronous call type;

[0095] If d0≠0 or e[B]≠0, it means that the data verification information does not meet the data verification value;

[0096] Step S507, determine whether the call retry count is greater than the retry count threshold, if so, jump to step S508, if not, jump to step S509;

[0097] Step S508, updating the variable storage space according to the current cache space;

[0098] Among them, if the call retry count is greater than the retry count threshold, the interface call retry mechanism is stopped.

[0099] Step S509 , increase the call retry count corresponding to the synchronous call type, and re-call the data reading interface corresponding to the delayed write read type according to the synchronous call type to update the target data, and jump to step S503 .

[0100] Optionally, data of each current cache space is updated according to each data to be updated, and data of the variable storage space is updated according to the current cache space after the data update, including: if the current call type is an asynchronous call type, and the current read type is an immediate write read type, then the number of current cache spaces is multiple; according to each current data, the preset shared cache space is assigned in turn; in response to the data verification information in the shared cache space satisfying the data verification value, the current cache space is updated according to the data to be updated in the shared cache space; if the data to be updated has completed the data update of the current cache space, the variable storage space is updated according to the current cache space.

[0101] Optionally, the method also includes: if the current call type is an asynchronous call type, in response to obtaining the target data, setting the status flag corresponding to each current cache space according to the data verification information in the target data, and judging whether the data verification information meets the data verification value based on the comparison result between the status flag and the data verification value.

[0102] Optionally, the method further includes: if the current call type is an asynchronous call type, and any data verification information does not meet the data verification value, then comparing the status flag corresponding to the data verification information according to the preset retry flag, and obtaining the number of call retries corresponding to the asynchronous call type; if the status flag corresponding to the data verification information does not meet the retry flag, and the number of call retries corresponding to the asynchronous call type is less than or equal to the retry number threshold, then setting the status flag corresponding to the data verification information according to the retry flag, increasing the number of call retries corresponding to the current call type, and re-calling the data reading interface corresponding to the current read type according to the current call type to update the target data; if the status flag corresponding to the data verification information does not meet the retry flag, and the asynchronous call type If the number of call retries corresponding to the asynchronous call type is greater than the retry threshold, the variable storage space is updated according to the current cache space; if the status flag corresponding to the data verification information satisfies the retry flag, the time during which the status flag satisfies the retry flag is counted to obtain the duration; if the duration is greater than the preset duration threshold, and the number of call retries corresponding to the asynchronous call type is less than or equal to the retry threshold, the number of call retries corresponding to the current call type is increased, and the data reading interface corresponding to the current read type is re-called according to the current call type to update the target data; if the duration is greater than the duration threshold, and the number of call retries corresponding to the asynchronous call type is greater than the retry threshold, the variable storage space is updated according to the current cache space.

[0103] In some embodiments, the retry flag is "00000000 11111111".

[0104] Combine Figure 6 As shown, the present application provides an EEPROM data update method based on asynchronous call type and immediate write and read type, including:

[0105] Step S601, setting the data cache space, variable storage space, status flag and call retry times according to their respective default values;

[0106] Step S602: calling the data reading interface corresponding to the immediate write and read type according to the asynchronous call type to obtain the target data;

[0107] Step S603: assigning values ​​to the preset shared cache space in sequence according to each current data, and setting a status flag according to the data verification information in the shared cache space;

[0108] Among them, for multiple current cache spaces of the immediate write and read type, multiple asynchronous calls are made to the same data read interface, and the current data returned by the underlying software is the same. Therefore, multiple current data are stored in the same shared cache space. After one current data completes the data update, the next current data is assigned to the shared cache space;

[0109] The shared cache space includes the cache space F = (f0, f1, f2, ...) for DATA data and the cache space G for ERR error information, and f0 and G are used as data verification information;

[0110] Step S604, determine whether the status flag corresponding to the shared cache space meets the data verification value, if so, jump to step S605, if not, jump to step S607;

[0111] Step S605, updating the current cache space according to the data to be updated in the shared cache space;

[0112] Step S606: If all data to be updated have completed data update in the current cache space, the variable storage space is updated according to the current cache space.

[0113] Step S607: Compare the status flag corresponding to the data verification information with the retry flag, and obtain the number of call retries corresponding to the asynchronous call type;

[0114] Step S608, determine whether the status flag corresponding to the shared cache space satisfies the retry flag, if so, jump to step S609, if not, jump to step S614;

[0115] Step S609, counting the time during which the status flag meets the retry flag to obtain the duration;

[0116] Step S610, determine whether the duration is greater than the duration threshold, if so, jump to step S611, if not, jump to step S609;

[0117] Step S611, determine whether the call retry count corresponding to the asynchronous call type is greater than the retry count threshold, if so, jump to step S612, if not, jump to step S613;

[0118] Step S612: update the variable storage space according to the current cache space.

[0119] Step S613: Increase the call retry count corresponding to the current call type, and re-call the data reading interface corresponding to the current read type according to the current call type to update the target data.

[0120] Step S614, determine whether the call retry count corresponding to the asynchronous call type is greater than the retry count threshold, if so, jump to step S612, if not, jump to step S615.

[0121] Step S615: Set the status flag corresponding to the data verification information according to the retry flag, reset the shared cache space, and jump to step S613;

[0122] Among them, the data elements in F are all reset to 11111111, and G is reset to 111111111.

[0123] Optionally, data of each current cache space is updated according to each data to be updated, and data of the variable storage space is updated according to the current cache space after the data update, including: if the current call type is an asynchronous call type, and the current read type is an immediate write read type, then the number of current cache spaces is multiple, and the current data also includes a data function identifier; according to each current data, the preset cache space corresponding to each data function identifier is assigned a value; in response to the data verification information in any preset cache space satisfying the data verification value, the current cache space is updated according to the data to be updated in the preset cache space; if the data to be updated has completed the data update of the current cache space, the variable storage space is updated according to the current cache space.

[0124] Combine Figure 7 As shown, the present application provides an EEPROM data update method based on asynchronous call type and immediate write and read type, including:

[0125] Step S701, setting the data cache space, variable storage space, status flag and call retry times according to their respective default values;

[0126] Step S702: calling the data reading interface corresponding to the immediate write and read type according to the asynchronous call type to obtain the target data;

[0127] Among them, the current data returned by the data reading interface contains a data function identifier (FunctionID). According to the data function identifier, each current data is stored in the corresponding preset cache space, and after the data verification information passes the data verification value, the data to be updated in the preset cache space is updated to the current cache space.

[0128] Step S703: assigning values ​​to preset cache spaces corresponding to respective data function identifiers according to respective current data, and setting status flags of respective current cache spaces according to respective data verification information;

[0129] Step S704, determine whether each status flag satisfies the data verification value, if so, jump to step S705, if not, jump to step S707;

[0130] Step S705, updating the current cache space according to each data to be updated;

[0131] Step S706: Update the variable storage space according to the current cache space.

[0132] Step S707: Compare the status flag corresponding to the data verification information with the retry flag, and obtain the number of call retries corresponding to the asynchronous call type;

[0133] Step S708, determine whether any status flag satisfies the retry flag, if so, jump to step S709, if not, jump to step S714;

[0134] Step S709, counting the time during which the status flag meets the retry flag to obtain the duration;

[0135] Step S710, determine whether the duration is greater than the duration threshold, if so, jump to step S711, if not, jump to step S709;

[0136] Step S711, determine whether the call retry count corresponding to the asynchronous call type is greater than the retry count threshold, if so, jump to step S712, if not, jump to step S713;

[0137] Step S712: update the variable storage space according to the current cache space.

[0138] Step S713: increase the call retry count corresponding to the current call type, and re-call the data reading interface corresponding to the current read type according to the current call type to update the target data.

[0139] Step S714, determine whether the call retry count corresponding to the asynchronous call type is greater than the retry count threshold, if so, jump to step S712, if not, jump to step S715.

[0140] Step S715: Set the status flag corresponding to the data verification information according to the retry flag, and jump to step S713.

[0141] Optionally, each current cache space is updated according to each data to be updated, and the variable storage space is updated according to the current cache space after the data update, including: if the current call type is an asynchronous call type, and the current read type is a delayed write read type, then the number of current cache spaces is one; if the data verification information satisfies the data verification value, then the current cache space is updated according to the data to be updated, and the variable storage space is updated according to the current cache space after the data update.

[0142] Combine Figure 8 As shown, the present application provides an EEPROM data update method based on asynchronous call type and delayed write read type, including:

[0143] Step S801, setting the data cache space, variable storage space, status flag and call retry times according to their respective default values;

[0144] Step S802: calling the data reading interface corresponding to the delayed write read type according to the asynchronous call type to obtain the target data;

[0145] Step S803, setting the status flag of the current cache space according to the data verification information;

[0146] Step S804, determine whether the status flag meets the data verification value, if so, jump to step S805, if not, jump to step S807;

[0147] Step S805, updating the current cache space according to the data to be updated;

[0148] Step S806: Update the variable storage space according to the current cache space.

[0149] Step S807: Compare the status flag of the current cache space with the retry flag, and obtain the number of call retries corresponding to the asynchronous call type;

[0150] Step S808, determine whether the status flag corresponding to the current cache space satisfies the retry flag, if so, jump to step S809, if not, jump to step S814;

[0151] Step S809, counting the time during which the status flag meets the retry flag to obtain the duration;

[0152] Step S810, determine whether the duration is greater than the duration threshold, if so, jump to step S811, if not, jump to step S809;

[0153] Step S811, determine whether the call retry count corresponding to the asynchronous call type is greater than the retry count threshold, if so, jump to step S812, if not, jump to step S813;

[0154] Step S812: update the variable storage space according to the current cache space.

[0155] Step S813: Increase the call retry count corresponding to the current call type, and re-call the data reading interface corresponding to the current read type according to the current call type to update the target data.

[0156] Step S814, determine whether the call retry count corresponding to the asynchronous call type is greater than the retry count threshold, if so, jump to step S812, if not, jump to step S815.

[0157] Step S815: Set the status flag corresponding to the data verification information according to the retry flag, and jump to step S813.

[0158] Optionally, the application layer module reads the variable storage space in the following manner: obtaining the status flag bits corresponding to each data cache space; if each space flag bit satisfies the data verification value, executing the first reading method, wherein the first reading method includes extracting data from the variable storage space corresponding to the application layer module to obtain the data variable corresponding to the application layer module; if any status flag bit satisfies the retry flag bit, waiting for the variable storage space to update the data, and counting the waiting time; if the waiting time is greater than a preset waiting time threshold, executing the second reading method, wherein the second reading method includes setting the data variable corresponding to the application layer module according to a preset initial value; if any flag bit does not satisfy the data verification value and the retry flag bit, executing the first reading method or the second reading method.

[0159] In some embodiments, if the status flag S x If both are "00000000 00000000", it means that the data update of the storage agent is normal and each application layer module can read the data variables in the variable storage space; if any status flag S x If the status flag S is "11111111 11111111", and the waiting time reaches the waiting time threshold, it means that the storage agent is re-reading the data, and each application layer module uses the preset value as the read data variable; if the status flag S x If it is not "00000000000000000" or "11111111 11111111", it indicates that the data reading of the storage agent is abnormal. According to the requirements of the application layer module, the historical variables in the variable storage space can be directly read as data variables, or the preset values ​​can be used as the read data variables.

[0160] Optionally, the method also includes: obtaining the task duration corresponding to the data reading task, and determining a task duration threshold based on multiple task durations, wherein the data reading task includes calling the data reading interface of the vehicle EEPROM according to the current call type, obtaining the target data corresponding to the current reading type, and using the current call type and / or the current reading type as a matching basis, matching the data update strategy corresponding to the target data, and executing the data update strategy; in response to the task duration of any data reading task being greater than or equal to the task duration threshold, interrupting the execution of the data reading task.

[0161] In some embodiments, the storage agent executes a data reading task through a Task function, wherein the Task function is periodically scheduled in the operating system with an interval of 0.01s (seconds) so that the Task function can be timed; when the task result of the data reading task is a task interruption or the execution ends, the task duration corresponding to the data reading task is determined; by multiple measurements of the data reading task, the task durations corresponding to multiple data reading tasks are obtained; the task durations are arranged from large to small, and one of the largest task durations is used as the task duration threshold, or the average of the largest task durations is used as the task duration threshold; if the task duration of the storage agent executing the data reading task is greater than the task duration threshold, the data reading task is interrupted.

[0162] Combine Figure 9 As shown, the present application provides a data reading system for vehicle EEPROM, including an acquisition module 901 , a generation module 902 , a matching module 903 and an execution module 904 .

[0163] The acquisition module 901 is used to acquire variable storage spaces corresponding to a plurality of application layer modules, wherein the variable storage spaces store data variables required by the application layer modules.

[0164] The generating module 902 is used to divide each data variable according to multiple data reading types, obtain similar data corresponding to each data reading type, and generate data cache space according to each similar data.

[0165] The matching module 903 is used to call the data reading interface of the vehicle EEPROM according to the current call type, obtain the target data corresponding to the current read type, and use the current call type and / or the current read type as the matching basis to match the data update strategy corresponding to the target data, wherein the current call type is any interface call type and the current read type is any data read type.

[0166] The execution module 904 is used to execute the data update strategy to update the corresponding data cache space according to the target data, and update the variable storage space according to the data cache space after the data update, so that the application layer module can read the data of the vehicle EEPROM by reading the corresponding variable storage space.

[0167] The vehicle EEPROM data reading system provided by the present application divides the variable storage spaces corresponding to multiple application layer modules according to various data reading types, obtains various types of data, and generates data cache spaces corresponding to each type of data. The system then reads target data from the vehicle EEPROM according to the interface call type and the data reading type, and matches a data update strategy. The data cache space and the variable storage space are updated sequentially according to the target data using the data update strategy, so that the application layer module reads data from the vehicle EEPROM by reading the corresponding variable storage space. Thus, compared to the application layer module directly calling the underlying interface, the variable storage space and the data cache space are decoupled from the underlying software by setting the variable storage space and the data cache space. The application layer interface reads data from the vehicle EEPROM by reading the corresponding variable storage space. Furthermore, the data update strategy matching mechanism enables adaptive configuration of the variable storage space data update based on different interface call types and data reading types, thereby achieving a unified data access mechanism and improving the efficiency of vehicle EEPROM data reading.

[0168] The present application also provides an electronic device, comprising: a processor and a memory; the memory is used to store a computer program, and the processor is used to execute the computer program stored in the memory, so that the electronic device performs the above method.

[0169] Figure 10 The following is a schematic diagram showing the structure of a computer system suitable for implementing an electronic device according to an embodiment of the present application. Figure 10 The computer system 1000 of the electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0170] like Figure 10As shown, the computer system 1000 includes a central processing unit (CPU) 1001, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 1002 or the program loaded from the storage part 1008 into the random access memory (RAM) 1003, such as executing the method in the above embodiment. Various programs and data required for system operation are also stored in the RAM 1003. The CPU 1001, ROM 1002 and RAM 1003 are connected to each other via a bus 1004. An input / output (I / O) interface 1005 is also connected to the bus 1004.

[0171] The following components are connected to the I / O interface 1005: an input section 1006 including a keyboard, a mouse, and the like; an output section 1007 including devices such as a cathode ray tube (CRT), a liquid crystal display (LCD), and a speaker; a storage section 1008 including a hard disk and the like; and a communication section 1009 including a network interface card such as a LAN (Local Area Network) card or a modem. The communication section 1009 performs communication processing via a network such as the Internet. A drive 1010 is also connected to the I / O interface 1005 as needed. Removable media 1011, such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory, is installed in the drive 1010 as needed, so that computer programs read therefrom can be installed into the storage section 1008 as needed.

[0172] The electronic device disclosed in this embodiment includes a processor, a memory, a transceiver, and a communication interface. The memory and the communication interface are connected to the processor and the transceiver and complete communication with each other. The memory is used to store computer programs, the communication interface is used to communicate, and the processor and the transceiver are used to run the computer program, so that the electronic device executes each step of the above method.

[0173] The above description and the accompanying drawings fully illustrate the embodiments of the present disclosure to enable those skilled in the art to practice them. Other embodiments may include structural, logical, electrical, process and other changes. The embodiments represent only possible variations. Unless expressly required, individual components and functions are optional, and the order of operations may vary. Parts and subsamples of some embodiments may be included in or replace parts and subsamples of other embodiments. Moreover, the terms used in this application are only used to describe the embodiments and are not used to limit the claims. As used in the description of the embodiments and claims, unless the context clearly indicates otherwise, the singular forms "a", "an" and "the" are intended to also include plural forms. Similarly, the term "and / or" as used in this application refers to any and all possible combinations of one or more associated listings. In addition, when used in this application, the term "comprise" and its variations "comprises" and / or comprising refer to the presence of a stated subsample, whole, step, operation, element, and / or component, but do not exclude the presence or addition of one or more other subsamples, wholes, steps, operations, elements, components and / or groups of these. In the absence of further restrictions, an element defined by the statement "comprises a..." does not exclude the presence of other identical elements in the process, method or device that includes the element. In this article, each embodiment may focus on the differences from other embodiments, and the same and similar parts between the various embodiments can be referenced to each other. For the methods, products, etc. disclosed in the embodiments, if they correspond to the method part disclosed in the embodiments, then the relevant parts can be found in the description of the method part.

[0174] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software may depend on the specific application and design constraints of the technical solution. Technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application. Technicians can clearly understand that for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0175] In the embodiments disclosed herein, the disclosed methods and products (including but not limited to devices, equipment, etc.) can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of units can be merely a logical functional division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some sub-samples can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between each other shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, and can be electrical, mechanical or other forms. The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to implement this embodiment. In addition, the functional units in this application may be integrated into a processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0176] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of the systems, methods, and computer program products of the present application. In this regard, each block in a flowchart or block diagram may represent a module, program segment, or portion of code, which contains one or more executable instructions for implementing a specified logical function. In some alternative implementations, the functions marked in the blocks may occur in an order different from that marked in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, or they may sometimes be executed in the opposite order, depending on the functions involved. In the descriptions corresponding to the flowcharts and block diagrams in the accompanying drawings, the operations or steps corresponding to different blocks may also occur in an order different from that disclosed in the description, and sometimes there is no specific order between different operations or steps. For example, two consecutive operations or steps may actually be executed substantially in parallel, or they may sometimes be executed in the opposite order, depending on the functions involved. Each block in the block diagram and / or flowchart, as well as combinations of blocks in the block diagram and / or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or action, or may be implemented using a combination of dedicated hardware and computer instructions.

Claims

1. A method for reading data from a vehicle EEPROM, characterized in that: include: Acquire variable storage spaces corresponding to a plurality of application layer modules respectively, wherein the variable storage spaces store data variables required by the application layer modules; Dividing each of the data variables according to multiple data reading types to obtain similar data corresponding to each of the data reading types, and generating data cache space according to each of the similar data; Calling the data reading interface of the vehicle EEPROM according to the current call type to obtain target data corresponding to the current reading type, and matching the data update strategy corresponding to the target data using the current call type and / or the current reading type as a matching basis, wherein the current call type is any interface call type and the current reading type is any data reading type; The data update strategy is executed to update the data cache space corresponding to the target data according to the target data, and to update the variable storage space according to the data cache space after the data update, so that the application layer module can read the data of the vehicle EEPROM by reading the variable storage space corresponding to the application layer module.

2. The method according to claim 1, characterized in that Generating data cache space respectively according to each of the similar data, including at least one of the following: Obtaining a reference space length corresponding to any data read type, and dividing similar data corresponding to the data read type according to the reference space length, so as to divide the similar data stored in one or more variable storage spaces into a similar data set, and generating data cache spaces corresponding to each similar data set according to the reference space length, wherein the amount of similar data in the similar data set is less than or equal to the reference space length; A target space length corresponding to any data read type is obtained, and a data cache space corresponding to the data read type is generated according to the target space length, wherein similar data corresponding to the data read type corresponds to data elements of the data cache space.

3. The method according to claim 1, characterized in that The data cache space corresponding to the target data is updated according to the target data, and the variable storage space is updated according to the data cache space after the data update in the following manner: One or more data cache spaces corresponding to the current read type are respectively used as current cache spaces, wherein the target data includes current data corresponding to each of the current cache spaces, wherein the current data includes data to be updated and data verification information; If each piece of data verification information satisfies a preset data verification value, data in each current cache space is updated according to each piece of data to be updated, and data in the variable storage space is updated according to the current cache space after the data update.

4. The method according to claim 3, characterized in that Updating the data in each current cache space according to each data to be updated, and updating the data in the variable storage space according to the current cache space after the data update, including at least one of the following: If the current call type is a synchronous call type and the current read type is an immediate write read type, then the number of the current cache spaces is multiple; if each piece of data verification information satisfies the data verification value, then data is updated in each of the current cache spaces according to each piece of data to be updated, and data is updated in the variable storage space according to the current cache space after the data update; If the current call type is a synchronous call type and the current read type is a delayed write read type, the number of the current cache space is one; if the data verification information satisfies the data verification value, the current cache space is updated according to the data to be updated, and the variable storage space is updated according to the current cache space after the data update; If the current call type is an asynchronous call type and the current read type is an immediate write read type, the number of the current cache spaces is multiple; assigning values ​​to the preset shared cache spaces in sequence according to the current data; in response to the data verification information in the shared cache space satisfying the data verification value, updating the current cache space according to the data to be updated in the shared cache space; if the data to be updated has completed the data update of the current cache space, updating the variable storage space according to the current cache space; If the current call type is an asynchronous call type, and the current read type is an immediate write read type, then the number of the current cache spaces is multiple, and the current data further includes a data function identifier; assigning a value to each preset cache space corresponding to each data function identifier according to each current data; in response to data verification information in any preset cache space satisfying the data verification value, updating the current cache space according to the data to be updated in the preset cache space; if each of the data to be updated has completed the data update of the current cache space, updating the variable storage space according to the current cache space; If the current call type is an asynchronous call type and the current read type is a delayed write read type, the number of the current cache space is one; if the data verification information satisfies the data verification value, the current cache space is updated according to the data to be updated, and the variable storage space is updated according to the current cache space after the data update.

5. The method according to claim 3, characterized in that The method further comprises at least one of the following: If the current call type is a synchronous call type, in response to data update of the variable storage space, respectively setting the status flag bits corresponding to the current cache spaces according to each data verification information in the target data; If the current call type is an asynchronous call type, in response to obtaining the target data, the status flag bits corresponding to each current cache space are set respectively according to the data verification information in the target data, and whether the data verification information meets the data verification value is determined based on the comparison result between the status flag bits and the data verification value.

6. The method according to claim 5, characterized in that The method further comprises: If the current call type is a synchronous call type, and any data verification information does not meet the data verification value, then obtain the call retry count corresponding to the synchronous call type; If the number of call retries corresponding to the synchronous call type is less than or equal to a preset retry threshold, the number of call retries corresponding to the current call type is increased, and the data reading interface corresponding to the current read type is re-called according to the current call type to update the target data; If the number of call retries corresponding to the synchronous call type is greater than the retry threshold, updating the variable storage space according to the current cache space; If the current call type is an asynchronous call type, and any data verification information does not meet the data verification value, then compare the status flag corresponding to the data verification information with the preset retry flag, and obtain the call retry count corresponding to the asynchronous call type; If the status flag corresponding to the data verification information does not satisfy the retry flag, and the number of call retries corresponding to the asynchronous call type is less than or equal to the retry threshold, then setting the status flag corresponding to the data verification information according to the retry flag, increasing the number of call retries corresponding to the current call type, and re-calling the data reading interface corresponding to the current read type according to the current call type to update the target data; If the status flag corresponding to the data verification information does not satisfy the retry flag, and the number of call retries corresponding to the asynchronous call type is greater than the retry threshold, then the variable storage space is updated according to the current cache space; If the status flag corresponding to the data verification information satisfies the retry flag, the time during which the status flag satisfies the retry flag is counted to obtain the duration; If the duration is greater than a preset duration threshold, and the number of call retries corresponding to the asynchronous call type is less than or equal to the retry threshold, then the number of call retries corresponding to the current call type is increased, and the data reading interface corresponding to the current read type is re-called according to the current call type to update the target data; If the duration is greater than the duration threshold, and the number of call retries corresponding to the asynchronous call type is greater than the retry threshold, data in the variable storage space is updated according to the current cache space.

7. The method according to claim 5, characterized in that The application layer module reads the variable storage space in the following way: Obtaining status flags corresponding to the data cache spaces; If each of the space flag bits satisfies the data verification value, a first reading method is executed, wherein the first reading method includes extracting data from the variable storage space corresponding to the application layer module to obtain the data variable corresponding to the application layer module; If any status flag satisfies the retry flag, wait for the variable storage space to update data and count the waiting time; If the waiting time is longer than a preset waiting time threshold, executing a second reading method, wherein the second reading method includes setting a data variable corresponding to the application layer module according to a preset initial value; If any flag does not satisfy the data verification value and the retry flag, the first reading method or the second reading method is executed.

8. The method according to any one of claims 1 to 7, characterized in that The method further comprises: Obtaining a task duration corresponding to a data reading task, and determining a task duration threshold based on a plurality of task durations, wherein the data reading task includes calling a data reading interface of the vehicle EEPROM according to a current call type, obtaining target data corresponding to the current read type, matching a data update strategy corresponding to the target data using the current call type and / or the current read type as a matching basis, and executing the data update strategy; In response to a task duration of any data reading task being greater than or equal to the task duration threshold, execution of the data reading task is interrupted.

9. A data reading system for vehicle EEPROM, characterized in that: include: An acquisition module, configured to acquire variable storage spaces corresponding to a plurality of application layer modules, wherein the variable storage spaces store data variables required by the application layer modules; A generating module, configured to divide each of the data variables according to a plurality of data reading types, obtain similar data corresponding to each of the data reading types, and generate data cache space according to each of the similar data; a matching module, configured to call a data reading interface of the vehicle EEPROM according to a current call type, obtain target data corresponding to the current reading type, and match a data update strategy corresponding to the target data using the current call type and / or the current reading type as a matching basis, wherein the current call type is any interface call type and the current reading type is any data reading type; An execution module is used to execute the data update strategy to update the data cache space corresponding to the target data according to the target data, and to update the variable storage space according to the data cache space after the data update, so that the application layer module can read the data of the vehicle EEPROM by reading the variable storage space corresponding to the application layer module.

10. An electronic device, characterized in that: include: processor and memory; The memory is used to store a computer program, and the processor is used to execute the computer program stored in the memory, so that the electronic device performs the method according to any one of claims 1 to 8.

Images