A method and device for persisting an automobile middleware configuration word

Abstract

The application provides a method and device for persistently storing a configuration word of automobile middleware, the method comprising: in response to a target module of the automobile middleware initiating a configuration word reading command to a target client during running of the automobile middleware, the target client being locked by a target storage module, the target client reading parameter data corresponding to a target configuration word from a memory through the target storage module, and the target client being unlocked again by the target storage module, in response to the target module initiating a configuration word writing command to the target client, the target client being locked again by the target storage module, the target client writing the target configuration word into the memory through the target storage module, and the target client being unlocked again, and the target server writing the target configuration word from the memory into a target disk for disk storage.

Description

Technical Field

[0001] This application relates to the field of automotive middleware technology, and more specifically, to a method and apparatus for persistent storage of automotive middleware configuration words. Background Technology

[0002] The background technology of automotive middleware configuration word storage is to solve the problems of scattered, inefficient, and unreliable software configuration parameter management in traditional automotive electronic architecture.

[0003] Currently, most existing vehicle configuration word storage solutions adopt a distributed storage model, where the configuration word is bound to a specific controller.

[0004] However, existing vehicle configuration word storage solutions are difficult to adapt to the cross-domain collaboration characteristics of middleware, and are prone to problems such as configuration information loss, multi-domain configuration asynchrony, and parameter incompatibility after upgrade. This leads to problems with the integrity and consistency of configuration information, as well as limited applicability and high maintenance and development costs. Summary of the Invention

[0005] In view of this, the purpose of this application is to provide a method and apparatus for persistent storage of automotive middleware configuration words. By using an overall framework of target client, target server and target storage management modules, the configuration words of automotive middleware are persistently stored, realizing configuration word read, write and storage functions, and supporting cross-domain communication of middleware. The cross-domain collaboration characteristics of middleware are specifically designed to avoid problems such as configuration information loss, multi-domain configuration asynchrony, and parameter incompatibility after upgrade. It ensures the integrity and consistency of configuration information in complex scenarios. In addition, it has a wider range of applications and can be developed universally across car manufacturers and models, reducing maintenance and development costs.

[0006] In a first aspect, embodiments of this application provide a method for persistent storage of automotive middleware configuration words, the method comprising: In response to the target module of the automotive middleware initiating a configuration word read command to the target client during the operation of the automotive middleware, the target client locks the target storage module. The target client reads the parameter data corresponding to the target configuration word from memory through the target storage module, and performs a lock release through the target storage module; In response to the target module sending a configuration word write command to the target client, the target client relocks the target storage module. The target client writes the target configuration word into memory through the target storage module and then re-locks it. The target server writes the target configuration word from the memory to the target disk for disk storage.

[0007] In one possible implementation, the method further includes: Determine if a cross-process data lock is engaged; If the cross-process data lock is not locked, the target client will re-lock it through the target storage module; When the cross-process data lock is engaged, the target client does not perform configuration word write operations.

[0008] In one possible implementation, locking via the target storage module includes: The target client sends a first lock request command to the target storage module, so that the target storage module requests a lock through the cross-process data lock; The target client sends a first locking command to the target storage module, so that the target storage module locks itself using the cross-process data lock.

[0009] In one possible implementation, reading the parameter data corresponding to the target configuration word from memory through the target storage module includes: The target client sends a configuration word read command to the target storage module, and the target storage module sends a configuration word read command to the cross-process data lock. After the target storage module receives the parameter data sent by the cross-process data lock, it returns the parameter data to the target client through the target storage module.

[0010] In one possible implementation, the re-locking via the target storage module includes: The target client sends a second lock request command to the target storage module, so that the target storage module can request the lock again through the cross-process data lock; The target client sends a second locking command to the target storage module, so that the target storage module can relock using the cross-process data lock.

[0011] In one possible implementation, writing the target configuration word into memory includes: The target storage module sends a configuration word write command to the cross-process data lock; When the cross-process data lock receives the configuration word write command, it updates the original parameter data value corresponding to the target configuration word in memory based on the parameter data.

[0012] In one possible implementation, writing the target configuration word from the memory to the target disk for disk persistence includes: The target server sends a configuration word write command to the physical read / write module. When the physical read / write module receives the configuration word write command, it writes the target configuration word to the target disk for disk storage.

[0013] Secondly, embodiments of this application also provide a persistent storage device for automotive middleware configuration words, the device comprising: The first reading module is used to respond to the target module of the automotive middleware sending a configuration word reading command to the target client during the operation of the automotive middleware, wherein the target client locks the target storage module. The second reading module is used by the target client to read parameter data corresponding to the target configuration word from memory through the target storage module, and to perform a lock release through the target storage module; The first writing module is used to respond to the target module sending a configuration word writing command to the target client, and the target client locks the target storage module again through the target storage module. The second write module is used by the target client to write the target configuration word into memory through the target storage module and then re-lock it. The disk write module is used by the target server to write the target configuration word from the memory to the target disk for disk storage.

[0014] In one possible implementation, the device further includes: The judgment module is used to determine whether the cross-process data lock is engaged; The first execution module is used to allow the target client to re-lock the cross-process data lock through the target storage module when the cross-process data lock is not locked. The second execution module is configured to prevent the target client from performing a configuration word write operation when the cross-process data lock is locked.

[0015] In one possible implementation, the first reading module is specifically used for: The target client sends a first lock request command to the target storage module, so that the target storage module requests a lock through the cross-process data lock; The target client sends a first locking command to the target storage module, so that the target storage module locks itself using the cross-process data lock.

[0016] In one possible implementation, the second reading module is specifically used for: The target client sends a configuration word read command to the target storage module, and the target storage module sends a configuration word read command to the cross-process data lock. After the target storage module receives the parameter data sent by the cross-process data lock, it returns the parameter data to the target client through the target storage module.

[0017] In one possible implementation, the first writing module is specifically used for: The target client sends a second lock request command to the target storage module, so that the target storage module can request the lock again through the cross-process data lock; The target client sends a second locking command to the target storage module, so that the target storage module can relock using the cross-process data lock.

[0018] In one possible implementation, the second writing module is specifically used for: The target storage module sends a configuration word write command to the cross-process data lock; When the cross-process data lock receives the configuration word write command, it updates the original parameter data value corresponding to the target configuration word in memory based on the parameter data.

[0019] In one possible implementation, the disk dropping module is specifically used for: The target server sends a configuration word write command to the physical read / write module. When the physical read / write module receives the configuration word write command, it writes the target configuration word to the target disk for disk storage.

[0020] Thirdly, embodiments of this application provide an electronic device, including: a processor, a storage medium, and a bus. The storage medium stores machine-readable instructions executable by the processor. When the electronic device is running, the processor communicates with the storage medium via the bus, and the processor executes the machine-readable instructions to perform the steps of the persistent storage method for automotive middleware configuration words as described in any of the first aspects.

[0021] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor, performs the steps of the persistent storage method for automotive middleware configuration words as described in any of the first aspects.

[0022] This application provides a method and apparatus for persistent storage of configuration words in automotive middleware. In response to a target module of the automotive middleware initiating a configuration word read command to a target client during the middleware's operation, the target client locks the target storage module, reads the parameter data corresponding to the target configuration word from memory through the target storage module, and then unlocks the target configuration word through the target storage module. In response to a target module initiating a configuration word write command to the target client, the target client locks the target storage module again, writes the target configuration word into memory through the target storage module, and then unlocks the target configuration word again. The target server then writes the target configuration word from memory to the target disk for disk storage. This application, through the use of an overall framework including target client, target server, and target storage management modules, persistently stores automotive middleware configuration words, enabling configuration word read / write and storage functions, and supports cross-domain communication of the middleware. It has been specifically designed for the cross-domain collaboration characteristics of the middleware, avoiding problems such as configuration information loss, multi-domain configuration asynchrony, and parameter incompatibility after upgrades, ensuring the integrity and consistency of configuration information in complex scenarios. In addition, it has a wider range of applications, allowing for universal development across car manufacturers and models, reducing maintenance and development costs.

[0023] To make the above-mentioned objectives, features and advantages of this application more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0024] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0025] Figure 1 This is a flowchart of a method for persistent storage of automotive middleware configuration words according to an embodiment of this application; Figure 2 This is a schematic diagram of the persistent storage framework design for automotive middleware configuration words; Figure 3 This is a timing diagram of reading configuration words from automotive middleware; Figure 4 This is a timing diagram of writing and disk partitioning configuration words in automotive middleware; Figure 5 This is a schematic diagram of the structure of a persistent storage device for automotive middleware configuration words provided according to an embodiment of this application; Figure 6 This is a schematic diagram of the structure of an electronic device provided according to an embodiment of this application. Detailed Implementation

[0026] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. It should be understood that the accompanying drawings in this application are for illustrative and descriptive purposes only and are not intended to limit the scope of protection of this application. Furthermore, it should be understood that the schematic drawings are not drawn to scale. The flowcharts used in this application illustrate operations implemented according to some embodiments of this application. It should be understood that the operations in the flowcharts may not be implemented in sequence, and steps without logical contextual relationships may be reversed or implemented simultaneously. In addition, those skilled in the art, guided by the content of this application, may add one or more other operations to the flowcharts, or remove one or more operations from the flowcharts.

[0027] Furthermore, the described embodiments are merely some, not all, of the embodiments of this application. The components of the embodiments of this application described and illustrated herein can typically be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely to illustrate selected embodiments of the application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.

[0028] It should be noted that the term "comprising" will be used in the embodiments of this application to indicate the presence of the features declared thereafter, but does not exclude the addition of other features.

[0029] Considering the background technology of automotive middleware configuration word storage, the core purpose is to solve the problems of scattered, inefficient, and unreliable software configuration parameter management in traditional automotive electronic architecture.

[0030] Currently, most existing automotive configuration word storage solutions adopt a distributed storage model, where configuration words are bound to specific controllers. However, existing automotive configuration word storage solutions are difficult to adapt to the cross-domain collaboration characteristics of middleware, and are prone to problems such as configuration information loss, multi-domain configuration asynchrony, and parameter incompatibility after upgrades. This leads to issues with the integrity and consistency of configuration information, limited applicability, and high maintenance and development costs.

[0031] To address this issue, this application provides a method and apparatus for persistent storage of automotive middleware configuration words. By using an overall framework of target client, target server, and target storage management modules, the method persistently stores automotive middleware configuration words, enabling configuration word read / write and storage functions. It also supports cross-domain communication of the middleware and has been specifically designed to address the cross-domain collaboration characteristics of the middleware. This avoids problems such as configuration information loss, multi-domain configuration asynchrony, and parameter incompatibility after upgrades, ensuring the integrity and consistency of configuration information in complex scenarios. Furthermore, it has a wider range of applications, allowing for universal development across vehicle manufacturers and vehicle models, thus reducing maintenance and development costs.

[0032] Figure 1 This is a flowchart of a method for persistent storage of automotive middleware configuration words according to an embodiment of this application. Figure 1 As shown in the embodiment of this application, the persistent storage method for automotive middleware configuration words may specifically include: S101. In response to the target module of the automotive middleware sending a configuration word read command to the target client during the operation of the automotive middleware, the target client locks the target storage module.

[0033] S102. The target client reads the parameter data corresponding to the target configuration word from memory through the target storage module, and performs lock release through the target storage module.

[0034] S103. In response to the target module sending a configuration word write command to the target client, the target client relocks the storage module.

[0035] S104. The target client writes the target configuration word into memory through the target storage module and then relocks the lock.

[0036] S105. The target server writes the target configuration word from memory to the target disk for disk storage.

[0037] The above-mentioned method for persistent storage of automotive middleware configuration words uses an overall framework of target client, target server, and target storage management modules to persistently store automotive middleware configuration words, enabling configuration word read / write and storage functions. It also supports cross-domain communication of the middleware and has been specifically designed for the cross-domain collaboration characteristics of the middleware, avoiding problems such as configuration information loss, multi-domain configuration asynchrony, and parameter incompatibility after upgrades. This ensures the integrity and consistency of configuration information in complex scenarios. In addition, it has a wider range of applications, allowing for universal development across car manufacturers and models, thus reducing maintenance and development costs.

[0038] The exemplary steps described above in the embodiments of this application are illustrated below with specific examples: S101, in response to the target module of the automotive middleware sending a configuration word read command to the target client during the operation of the automotive middleware, the target client locks the target storage module.

[0039] It should be noted that this application applies to an automotive middleware configuration word persistent storage framework. This framework includes QNX on a processor (SOC), where QNX includes a cockpit HMI and cockpit services. The cockpit HMI includes an instrument cluster HMI, and the cockpit services include automotive middleware components. These components read and write configuration words through pissaclient (target client), storage (target storage module), and pissaserver (target server). For example... Figure 2 As shown.

[0040] As those skilled in the art will understand, psisclient, or Proxy, is used to receive external messages, essentially acting as a client; under storage, storage::dirty is used to manage dirty data, providing dirty setting and erasure, and supports multi-process concurrency, meaning that any number of keys can have dirty data at any given time; storage::mutex (corresponding to cross-process data lock) provides cross-process data lock; storage::datax is used for memory data read and write, based on sectors and indexes; memory (corresponding to memory) is encapsulated in memory form; util is the utility component, providing various attributes and default value lookup; psis_server is the user's key-value data read and write control (disk write timing control); IO (physical read and write module) represents the physical read and write logic abstraction of data; COM represents external communication control (psisClient, power status).

[0041] In this embodiment of the application, when the target module of the automotive middleware needs to read data with a specified key value during operation, it sends a data read command (configuration word read command) to the target client. Upon receiving the configuration word read command, the target client locks the target storage module for subsequent processing. For example, as... Figure 3 As shown.

[0042] Optionally, when locking through the target storage module, the target client sends a first lock request command to the target storage module, enabling the target storage module to request the lock using a cross-process data lock; similarly, the target client sends a first lock command to the target storage module, enabling the target storage module to lock using a cross-process data lock. For example, as... Figure 3 As shown.

[0043] S102, the target client reads the parameter data corresponding to the target configuration word from memory through the target storage module, and performs a lock release through the target storage module.

[0044] In this embodiment, the target client reads the parameter data of the target configuration word from memory through the target storage module and performs a lock reset for subsequent processing. For example, as Figure 3 As shown.

[0045] Optionally, when reading parameter data corresponding to the target configuration word from memory through the target storage module, the target client sends a configuration word read command to the target storage module, so as to send the configuration word read command to the cross-process data lock through the target storage module; after the target storage module receives the parameter data sent by the cross-process data lock, it returns the parameter data to the target client through the target storage module.

[0046] S103, in response to the target module sending a configuration word write command to the target client, the target client relocks the storage module.

[0047] In this embodiment of the application, when the target module of the automotive middleware sends a command to the target client to write the configuration word, the target client locks the target storage module again for subsequent processing.

[0048] Optionally, when re-locking through the target storage module, the target client sends a second lock request command to the target storage module, enabling the target storage module to re-request the lock using a cross-process data lock; similarly, the target client sends a second lock command to the target storage module, enabling the target storage module to re-lock using a cross-process data lock. For example, as... Figure 4 As shown.

[0049] S104, the target client writes the target configuration word into memory through the target storage module and then re-locks the device.

[0050] In this embodiment, the target client writes the target configuration word into memory through the target storage module and then re-locks the memory for subsequent processing. For example, as... Figure 4 As shown.

[0051] Optionally, when writing the target configuration word into memory, a configuration word write command is sent to the cross-process data lock through the target storage module; when the cross-process data lock receives the configuration word write command, it updates the original parameter data value corresponding to the target configuration word in memory based on the parameter data.

[0052] S105, the target server writes the target configuration word from memory to the target disk for disk storage.

[0053] In this embodiment, the target server continues to write the target configuration word from memory to the target disk for persistent storage, thereby achieving persistent storage of the configuration word. For example, as Figure 4 As shown.

[0054] In some implementations, the target server sends a configuration word write command to the physical read / write module (IO); when the physical read / write module (IO) receives the configuration word write command, it writes the target configuration word to the target disk for disk storage.

[0055] The persistent storage method for automotive middleware configuration words provided in this application embodiment responds to the target client initiating a configuration word read command from the target module during the operation of the automotive middleware. The target client locks the target storage module, reads the parameter data corresponding to the target configuration word from memory through the target storage module, and unlocks the target through the target storage module. In response to the target module initiating a configuration word write command from the target client, the target client locks the target storage module again, writes the target configuration word into memory through the target storage module, and unlocks the target again. The target server writes the target configuration word from memory to the target disk for disk storage. The persistent storage method for automotive middleware configuration words in this application persistently stores automotive middleware configuration words through an overall framework of target client, target server, and target storage management modules, enabling configuration word read / write and storage functions. It also supports cross-domain communication of the middleware and has been specifically designed for the cross-domain collaboration characteristics of the middleware, avoiding problems such as configuration information loss, multi-domain configuration asynchrony, and parameter incompatibility after upgrades. This ensures the integrity and consistency of configuration information in complex scenarios. In addition, it has a wider range of applications, allowing for universal development across car manufacturers and models, thus reducing maintenance and development costs.

[0056] Furthermore, it determines whether the cross-process data lock is locked; if the cross-process data lock is not locked, the target client re-locks it through the target storage module; if the cross-process data lock is locked, the target client does not perform the configuration word write operation.

[0057] It should be noted that when a cross-process data lock is locked, it indicates that there are other processes that are currently writing to memory and have not yet completed. At this time, the target module cannot perform a write operation.

[0058] In summary, this application persistently stores the configuration words of automotive middleware, enabling read, write, and storage functions of the configuration words. It can solidify and store key configuration parameters, ensuring the integrity, consistency, and traceability of configuration information in complex scenarios such as power failure restarts, operating condition switching, and software and hardware upgrades. At the same time, the platform-based design greatly improves the development efficiency of automotive instruments and reduces maintenance costs.

[0059] Figure 5 This is a schematic diagram of the persistent storage device for automotive middleware configuration words provided according to an embodiment of this application; as shown below. Figure 5 As shown, the persistent storage device 500 for automotive middleware configuration words in this embodiment of the application may specifically include: The first reading module 501 is used to respond to the target module of the automotive middleware sending a configuration word reading command to the target client during the operation of the automotive middleware, wherein the target client locks the target storage module. The second reading module 502 is used by the target client to read parameter data corresponding to the target configuration word from memory through the target storage module, and to perform a lock release through the target storage module; The first writing module 503 is used to respond to the target module sending a configuration word writing command to the target client, and the target client locks the target storage module again through the target storage module. The second writing module 504 is used for the target client to write the target configuration word into memory through the target storage module and then re-lock; The disk write module 505 is used by the target server to write the target configuration word from the memory to the target disk for disk storage.

[0060] In one possible implementation, the device further includes: The judgment module is used to determine whether the cross-process data lock is engaged; The first execution module is used to allow the target client to re-lock the cross-process data lock through the target storage module when the cross-process data lock is not locked. The second execution module is configured to prevent the target client from performing a configuration word write operation when the cross-process data lock is locked.

[0061] In one possible implementation, the first reading module is specifically used for: The target client sends a first lock request command to the target storage module, so that the target storage module requests a lock through the cross-process data lock; The target client sends a first locking command to the target storage module, so that the target storage module locks itself using the cross-process data lock.

[0062] In one possible implementation, the second reading module is specifically used for: The target client sends a configuration word read command to the target storage module, and the target storage module sends a configuration word read command to the cross-process data lock. After the target storage module receives the parameter data sent by the cross-process data lock, it returns the parameter data to the target client through the target storage module.

[0063] In one possible implementation, the first writing module is specifically used for: The target client sends a second lock request command to the target storage module, so that the target storage module can request the lock again through the cross-process data lock; The target client sends a second locking command to the target storage module, so that the target storage module can relock using the cross-process data lock.

[0064] In one possible implementation, the second writing module is specifically used for: The target storage module sends a configuration word write command to the cross-process data lock; When the cross-process data lock receives the configuration word write command, it updates the original parameter data value corresponding to the target configuration word in memory based on the parameter data.

[0065] In one possible implementation, the disk dropping module is specifically used for: The target server sends a configuration word write command to the physical read / write module. When the physical read / write module receives the configuration word write command, it writes the target configuration word to the target disk for disk storage.

[0066] The persistent storage device for automotive middleware configuration words provided in this application embodiment responds to the target client initiating a configuration word read command from the target module during the operation of the automotive middleware. The target client locks the target storage module, reads the parameter data corresponding to the target configuration word from memory through the target storage module, and unlocks the target through the target storage module. In response to the target module initiating a configuration word write command from the target client, the target client locks the target storage module again, writes the target configuration word into memory through the target storage module, and unlocks the target again. The target server writes the target configuration word from memory to the target disk for disk storage. This application, through the use of an overall framework including target client, target server, and target storage management modules, persistently stores automotive middleware configuration words, enabling configuration word read / write and storage functions, and supports cross-domain communication of the middleware. It has been specifically designed for the cross-domain collaboration characteristics of the middleware, avoiding problems such as configuration information loss, multi-domain configuration asynchrony, and parameter incompatibility after upgrades, ensuring the integrity and consistency of configuration information in complex scenarios. In addition, it has a wider range of applications, allowing for universal development across car manufacturers and models, reducing maintenance and development costs.

[0067] like Figure 6 As shown in the embodiment of this application, an electronic device 600 includes a processor 601, a memory 602, and a bus. The memory 602 stores machine-readable instructions executable by the processor 601. When the electronic device is running, the processor 601 communicates with the memory 602 via the bus. The processor 601 executes the machine-readable instructions to perform the steps of the above-described persistent storage method for automotive middleware configuration words.

[0068] Specifically, the memory 602 and processor 601 mentioned above can be general-purpose memory and processor, without any specific limitations. When the processor 601 runs the computer program stored in the memory 602, it can execute the above-mentioned persistent storage method for automotive middleware configuration words.

[0069] Corresponding to the above-described persistent storage method for automotive middleware configuration words, this application embodiment also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the steps of the above-described persistent storage method for automotive middleware configuration words.

[0070] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems and devices described above can be referred to the corresponding processes in the method embodiments, and will not be repeated here. In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. Furthermore, multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed mutual coupling or direct coupling or communication connection can be through some communication interfaces; the indirect coupling or communication connection of devices or modules can be electrical, mechanical, or other forms.

[0071] The modules described as separate components may or may not be physically separate. The components shown as modules 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.

[0072] In addition, 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.

[0073] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a processor-executable, non-volatile, 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 a portion 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 several commands to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the deployment methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, external hard drives, ROM, RAM, magnetic disks, or optical disks.

[0074] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for persistent storage of automotive middleware configuration words, characterized in that, The method includes: In response to the target module of the automotive middleware initiating a configuration word read command to the target client during the operation of the automotive middleware, the target client locks the target storage module. The target client reads the parameter data corresponding to the target configuration word from memory through the target storage module, and performs a lock release through the target storage module; In response to the target module sending a configuration word write command to the target client, the target client relocks the target storage module. The target client writes the target configuration word into memory through the target storage module and then re-locks it. The target server writes the target configuration word from the memory to the target disk for disk storage.

2. The method according to claim 1, characterized in that, The method further includes: Determine if a cross-process data lock is engaged; If the cross-process data lock is not locked, the target client will re-lock it through the target storage module; When the cross-process data lock is engaged, the target client does not perform configuration word write operations.

3. The method according to claim 2, characterized in that, The locking process via the target storage module includes: The target client sends a first lock request command to the target storage module, so that the target storage module requests a lock through the cross-process data lock; The target client sends a first locking command to the target storage module, so that the target storage module locks itself using the cross-process data lock.

4. The method according to claim 2, characterized in that, The step of reading the parameter data corresponding to the target configuration word from memory through the target storage module includes: The target client sends a configuration word read command to the target storage module, and the target storage module sends a configuration word read command to the cross-process data lock. After the target storage module receives the parameter data sent by the cross-process data lock, it returns the parameter data to the target client through the target storage module.

5. The method according to claim 2, characterized in that, The step of re-locking via the target storage module includes: The target client sends a second lock request command to the target storage module, so that the target storage module can request the lock again through the cross-process data lock; The target client sends a second locking command to the target storage module, so that the target storage module can relock using the cross-process data lock.

6. The method according to claim 2, characterized in that, The step of writing the target configuration word into memory includes: The target storage module sends a configuration word write command to the cross-process data lock; When the cross-process data lock receives the configuration word write command, it updates the original parameter data value corresponding to the target configuration word in memory based on the parameter data.

7. The method according to claim 2, characterized in that, The step of writing the target configuration word from the memory to the target disk for disk storage includes: The target server sends a configuration word write command to the physical read / write module. When the physical read / write module receives the configuration word write command, it writes the target configuration word to the target disk for disk storage.

8. A persistent storage device for automotive middleware configuration words, characterized in that, The device includes: The first reading module is used to respond to the target module of the automotive middleware sending a configuration word reading command to the target client during the operation of the automotive middleware, wherein the target client locks the target storage module. The second reading module is used by the target client to read parameter data corresponding to the target configuration word from memory through the target storage module, and to perform a lock release through the target storage module; The first writing module is used to respond to the target module sending a configuration word writing command to the target client, and the target client locks the target storage module again through the target storage module. The second write module is used by the target client to write the target configuration word into memory through the target storage module and then re-lock it. The disk write module is used by the target server to write the target configuration word from the memory to the target disk for disk storage.

9. An electronic device, characterized in that, include: The device includes a processor, a memory, and a bus. The memory stores machine-readable instructions executable by the processor. When the electronic device is running, the processor communicates with the memory via the bus. When the machine-readable instructions are executed by the processor, the steps of the persistent storage method for automotive middleware configuration words as described in any one of claims 1 to 7 are performed.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, performs the steps of the persistent storage method for automotive middleware configuration words as described in any one of claims 1 to 7.

Images