JP4973844B2 - Object-oriented vehicle control device - Google Patents

Description

  The present invention relates to an object-oriented vehicle control device.

JP 2001-270399 A

  2. Description of the Related Art In recent years, electronic devices mounted on automobiles are mainly controlled using a hardware unit including a microcomputer (MPU) called an ECU. As exemplified in Patent Document 1, a method of realizing this control by a computer system designed by object orientation (hereinafter, also referred to as “object-oriented system”) has become widespread (Patent Document 1). By adopting the object-oriented system, the difference in the hardware configuration of the devices involved in the control can be concealed inside the object constituting the software, and the independence of each control program can be enhanced for each control target. As an object-oriented programming language, for example, Java (registered trademark) or C ++ is known, and both describe a program in units of objects. An object is a unit of an organic program with autonomy, and is described in an integrated form of data and procedures. Work as a whole program is advanced by exchanging messages between objects. A procedure that is started by receiving a message is called a method. Requests for work on objects can only be made via methods, and direct access to the data in the objects is prohibited.

In an object-oriented system, each object receives a message for calling a method incorporated in the object from another object, and processing is executed in such a manner that an execution result of the method is returned to the message source. Here, objects can be broadly classified into classes (class objects) and instances (instance objects) created using the classes. The class describes the definition of attributes for storing data and methods that describe functional processing. A class corresponds to a template of an object, and has only a general-purpose method set and variable definition, and a specific process cannot be directly executed as it is. Therefore, an instance, which is an object that defines the actual processing content, assigns a specific value to the attribute, and a pointer to link to the method actually used among the methods described in the class It is created through procedures such as describing. Note that an instance is newly created using a class as a template , and the original class is not rewritten. Further, the actual processing proceeds in such a manner that each instance created from the corresponding class receives a message and passes control to a method of the corresponding class.

  In an object-oriented system, all information is modeled as an object and described as a class. A program is an aggregate of the classes, and a large number of instances generated from each class have information entities. In this case, the problem is that the instance is normally generated on the work memory (RAM) and is erased from the memory when the program ends. Therefore, by converting the contents of the instance into a storage format such as a file and saving it to a (non-volatile) storage medium so that the created instance can be reused later, even if the program ends, it can be A feature has been devised that allows an instance to be restored at any time. This function is called instance persistence.

  As described above, the class from which the instance is created is constructed from the definition of the attribute in which data is stored (referred to as “field”) and the method describing the functional processing realized using the attribute. Then, an instance is created by specifying the state of this class as an object in the form of storing an actual value in a variable on the field. “Instance persistence” is nothing but saving an object state, that is, attribute data.

  The attribute is, for example, a parameter used for control, and the parameter value is grasped as the substance of the attribute data. However, for passive data groups that are the target of output processing to output devices such as display devices, printing devices or audio output units, such as image data and audio data files, text strings that construct databases, or log data, The process of writing to and storing in a storage medium or reading out for output is basically executed in an object-oriented manner using a class that controls access to the medium such as storage and writing. Therefore, an instance in which the data is incorporated is created for the saving or reading process, and the instance is made permanent by executing the saving.

  In recent years, many non-volatile memories are used as storage media in automobile control systems, and different types of non-volatile memories such as EEPROM and flash memory are often used depending on the type of data. It is coming. For example, an EEPROM has a relatively small capacity but can be erased / written in units of bytes, whereas a flash memory has a large capacity, but can only be written in units of bytes. There is a difference that it can only be executed in units of larger blocks (sectors). Therefore, for example, the former is used for storing control parameters that are frequently rewritten, and the latter is used for storing image data and large-capacity text data. Since the speed is higher than that of the EEPROM and the price is being reduced, a design change may be implemented in the field where the EEPROM has been used so far. On the other hand, considering the power backup of the RAM, there may be a design change example in which data storage in the nonvolatile memory is changed to data saving on the RAM or vice versa. Furthermore, it is conceivable to change the design to a system in which one data is stored redundantly in a plurality of storage media in order to improve reliability.

  When persisting data (instance), it is necessary to specify the storage medium that is the storage destination, but this storage destination is conventionally specified by the application that makes the storage request (hereinafter also abbreviated as “app”). I was supposed to. Then, on the application side, as shown in FIG. 8, the data to be stored is acquired autonomously, the medium to be stored is determined by itself, and the data to be stored is transferred to each medium in the form of a storage request. Will be. However, since this method is closely related to the application and the storage medium, if the type of the storage medium is changed as described above, it will be very susceptible to significant changes in the application. You may be forced to do so. In particular, in the case of a design change involving a nonvolatile memory, there is a problem that the influence is particularly great because the data size that can be stored and the erasable unit are different.

  An object of the present invention is to provide an object-oriented vehicle control system capable of minimizing the influence on applications and data even when the design of a storage medium is changed.

Means for Solving the Problems and Effects of the Invention

An object-oriented vehicle control system according to the present invention includes a CPU, and is a vehicle control device that controls the operation of an in-vehicle electronic device when the CPU executes an object-oriented program. The program to solve
Implement the persistence interface for accepting from the application class a save request for persisting and saving the instance of the data that is the target of the save request from the application class involved in operation control. Persistence-compatible data class for converting the above-mentioned instance into storage data in a form to which medium-specific reference information, which is information to be referred to in order to specify the storage medium that is the storage destination, is added. When,
An individual medium management class that is provided in a form that individually corresponds to a storage medium or storage medium group that is a storage destination candidate of storage data, and that stores storage data that has received a storage request in the corresponding storage medium;
Select the individual medium management class corresponding to the storage medium that is the data storage destination by referring to the medium specific reference information given to the storage data passed from the persistence-compatible data class. It was a persistent management class for passing data for storage in a separate media management class, and having a.

  According to the above configuration, the method related to the storage processing in the storage medium is incorporated into the individual medium management class individually corresponding to the storage medium, and on the other hand, the method for converting the data into the storage data that is the storage form is permanent. The data storage request from the application is received in the persistence-compatible data class. The converted storage data is transferred to the individual medium management class of the corresponding storage medium by referring to the medium specific reference information given to the storage data by the persistence management class. The storage medium that is the data storage destination when viewed from the application can be hidden by the persistence-compatible data class. This means that, as shown in FIG. 7, the relationship between the storage medium and data to be processed is switched as compared with the conventional method of FIG. As a result, it is possible to carry out design changes related to the specification change and exchange of the storage medium with almost no influence from the application or the data structure.

The above program, as well as implement the data storage interface for accepting a write request to the storage medium store data from the persistent management class, providing data management class equipped with data storage method to individual storage medium be able to. In this case, each individual medium management class can be constructed as a subclass that inherits the data management class. When there is a design change of the storage medium, it is possible to easily cope with a system change only by changing the method of this data management class.

Next, the medium specific reference information may be a data type specifying information specifying a type of data. Then, media / data type correspondence information indicating the correspondence between the data type specified by the data type identification information and the individual medium management class is prepared in advance, and the persistence management class is referred to the medium / data type correspondence information. by can select individual media management class corresponding to the type of data for storage, constructed as for passing stored data thereto.

  The above configuration means that the type of the storage medium is indirectly specified according to the type of data. If the medium specific reference information is described as directly specifying the storage medium type, the contents of the medium specific reference information must be changed when there is a design change of the storage medium type. A design change work is required to rewrite the medium specific reference information. However, as described above, if the design change of the storage medium type occurs by using the medium specific reference information as the data type specific information, the medium / data type correspondence relationship referred to in the persistence management class should be corrected. As long as there is no change in the type of data handled by the app, the media change will not affect the app at all.

On the other hand, the persistence management class refers to the data size information as the medium specific reference information, selects the individual medium management class corresponding to the storage medium as the data storage destination according to the data size information, and sets the storage data to this. It can also be for delivery. Even in this method, since the type of the storage medium is indirectly specified according to the data size, the influence of the medium change does not affect the application as well. Of course, this method can also be used in combination with a method for indirectly specifying the type of the storage medium according to the type of data.

As described above, when non-volatile memories having different specifications are designated as the storage medium, the contribution of the effects of the present invention is significant. For example, when the data is state data including a setting value of a variable indicating the state of the application class, the persistent management class is an individual medium management class associated with an EEPROM which is one of the nonvolatile memories. selected, when data is image data, can be used to select individual media management class associated with the flash memory which is one of the non-volatile memory. In many cases, the attribute is a parameter value, the capacity is relatively small, and it is preferable that the attribute is stored in an EEPROM that can flexibly cope with frequent rewriting.

In this case, persistence management class data, if it is important predetermined data, when the EEPROM for status data previously assumed to select another EEPROM, a separate EEPROM important data Since it can be saved, it can flexibly support different security level settings. Also, if the data is log data consisting of communication logs or device operation logs, a large amount of data storage requests are made in time series, so select a flash memory that is different from the image data flash memory. it is convenient if you and meant to be.

The persistence-compatible data class generates an identification ID for uniquely specifying storage data from an address storing its own instance, and stores the storage data in a form to which the identification ID is assigned. Can be for delivery to . Further, the individual medium management class can be used for writing the storage data transferred from the permanent management class to the corresponding storage medium with an identification ID.

  As described above, the storage data identification ID is uniquely created from the address indicating the storage destination of the instance including the data to be saved in the persistence-compatible data class, and the identification ID is added to correspond. By saving the data in the storage medium, the identification ID of the data to be restored to be restored can be easily specified from the address (this does not disappear even when the program is terminated) at the time of restoration. Convenience at the time of restoration can be achieved.

Next, persistent corresponding data class implements the serialization interface for serializing an instance of itself, it can be configured as for passing the persistence management class the serialized data as save data. As a result, even data with a relatively complicated structure can be converted into data having a simple byte string structure by serialization, and the storage process on the storage medium can be greatly simplified. Data that is particularly suitable for serialization is state data that includes a setting value of a variable indicating the state of the application class.

  Data that exceeds the predetermined size or has already been serialized is converted to data for storage in the persistence-compatible data class without executing serialization processing by the serialization interface. Is efficient. In particular, the image data is originally described as byte string data, corresponds to data that has been serialized, and has a large size, so by avoiding uniform serialization processing as it is as storage data, Processing efficiency can be increased.

Next, as a configuration considering data reading (restoring), the following is possible. In other words, persistence interface, already a restoring request for restoring the instance reads the storage data stored can be made to accept the application class instance of the own identifiable form. The persistence management class has a save list for storing a list of identification IDs for specifying saved save data in a form that can be specified by a storage medium as a save destination, and the above-described restoration request specifies The identification ID is specified based on the address, and further, the storage ID of the storage destination is specified by searching the identification list on the storage list, and the identification ID is received by the individual medium management class corresponding to the specified storage medium. Can be for passing. Each individual media management class, the saved data corresponding to the identification ID received is read from the corresponding storage medium, and intended for passing the saved data to the persistent corresponding data classes through persistence management class be able to. Persistence corresponding data classes can be used to recover the data for the storage in its own instance.

The storage list provided in the persistence management class may be created by directly specifying the storage medium that is the storage destination, or as described above, data uniquely associated with the storage medium (or storage medium group). Depending on the type, it may be created indirectly. For example, in the latter case, at the time of data restoration, an address for storing an instance of the storage request target data and specific information of the data type are acquired from the application side, and an identification ID created from the address in the corresponding storage list is obtained. Search for. As a result, the storage medium stored with the identification ID can be quickly identified, and the storage data can be read and restored smoothly. In order to recover the serialized storage data, serialized interface, it is necessary to structure as to deserialize data for storage that is serialized during a restore.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.
FIG. 1 is a diagram conceptually showing the configuration of a control subject 40 in the object-oriented vehicle control system of the present invention from the viewpoint of an object-oriented platform. In this embodiment, the control subject 40 is configured as an arithmetic processing device that executes information processing based on a program described in Java. The program execution device 1 is a CPU in which a circuit for executing bytecode by Java is incorporated, and includes a program execution unit 3, a method search unit 4, a memory controller 5, and the like. The memory 2 is a ROM or RAM, or a storage area including both, and storage areas such as a program data area 6 and a search table area 7 are set (in FIG. 1, the program execution device 1 is shown). Although it is handled as a single CPU for convenience, the configuration is not limited to this, and for example, a CPU group connected by an in-vehicle network such as a CAN (Controller Area Network) may be used.

  The program data area 6 stores a byte code program compiled from a Java source program (hereinafter, a program for one address is referred to as “program data”). The search table area 7 stores a class table, a method table, etc. (not shown) in order to search a place where the called method is stored when the method is called.

  Memory access in the program execution device 1 is controlled by the memory controller 5. The program execution unit 3 obtains the program data from the program data area 6 and executes it by giving the memory controller 5 a program address indicating the storage location of the program data to be read. In particular, when the program data is a message indicating a method call, the program execution unit 3 sends the message to the method search unit 4 to request a method storage location search.

  The message includes data indicating the name of the class to which the object that is the object of the message belongs, the method name of the method to be executed, the arguments, the presence / absence of a return value, and its type. Based on this message, the method search unit 4 recognizes the class to which the object that is the message belongs and the specified method, and then searches the storage location of the method using the search table. This search processing is performed by causing the memory controller 5 to read out information by designating an address (indicated as “table address” in the figure) of a storage location of search information required in the search table area 7. Realize. The table address is given by a pointer indicating the entry position of each search table or a value indicating the address of the area corresponding to the entry position in the memory 2.

  The method search unit 4 acquires the start address (hereinafter referred to as “program start address”) of the storage location of the designated method as a search result, and transmits this program start address to the program execution unit 3 as a program counter. The program execution unit 3 sets a work area for the method in a memory area for a stack (not shown), and sequentially transmits each program data constituting the method from the program data area 6 starting from an address indicated by the program counter. Read and execute processing corresponding to each program data.

The execution program of the control subject 40 is constructed on the object-oriented platform. FIG. 2 is a class diagram according to the UML (Unified Modeling Language) notation showing the configuration of the program. The program is composed of the following objects.
Persistence-compatible data class 101C: Persistence for accepting a storage request for persisting and saving the instance from the application class 106C as data to be saved from the application class 106C involved in operation control. When the storage interface 101K is implemented and the above storage request is received, the data is converted into the storage data in a form to which the medium specifying reference information that is the information to be referred to in order to specify the storage medium as the storage destination is added. .
Individual medium management classes 103C and 104C: provided in a form that individually corresponds to a storage medium or storage medium group that is a storage destination candidate for storage data, and stores storage data that has received a storage request in the corresponding storage medium .
Persistence management class 102C: individual data corresponding to a storage medium serving as a data storage destination by referring to the medium-specific reference information attached to the storage data delivered from the continuation correspondence data conversion processing class 101C The medium management classes 103C and 104C are selected, and the storage data is transferred to the selected individual medium management classes 103C and 104C.

Data management class 105C: A data storage interface 105I that accepts a write request to the storage medium for storage data from the persistence management class 102C is mounted, and a data storage method for each storage medium is mounted. Each of the individual medium management classes 103C and 104C is constructed as a subclass that inherits the data management class 105C.

  In the above configuration, the method related to the storage processing in the storage medium is incorporated in the individual medium management classes 103C and 104C individually corresponding to the storage medium. In addition, a method for converting data into storage data that is a storage form is incorporated in the persistence-compatible data class 101C. Then, the persistence-compatible data class 101C accepts a data storage request from the application. The converted storage data is transferred to the individual medium management classes 103C and 104C of the corresponding storage medium by referring to the medium specifying reference information given to the storage data by the persistence management class 102C. As a result, the storage medium that is the data storage destination when viewed from the application is hidden by the persistence-compatible data class 101C.

  As a result, it is possible to carry out design changes related to specification changes and exchanges of storage media with little influence from applications or data structures (for example, EEPROM, flash memory, RAM and other communication-connected other devices). Mutual conversion between control bodies (ECUs)). In addition, as a secondary effect, design related to redundancy for improving data reliability, such as duplication of storage media (for example, duplication of storage area of flash memory, addition of backup area on RAM, etc.) Changes can be easily accommodated.

  Specifically, the medium specifying reference information is data type specifying information for specifying the type of data as shown in FIG. Then, medium / data type correspondence information indicating the correspondence between the data type specified by the data type specifying information and the individual medium management classes 103C and 104C is prepared. The persistent management class 102C in FIG. 2 selects the individual medium management classes 103C and 104C corresponding to the type of the storage data by referring to the medium / data type correspondence relationship information, and stores the storage data in this. It is built to be handed over. Note that the data type can be specified from, for example, an attribute of a class used for saving / restoring data on the application side, but is not limited thereto. For example, an array for storing an instance of the storage request target data corresponding to the corresponding data type of the persistence management class (a storage list storage list 200A to 200D described later: for example, an image data list or normal data) It is also possible to configure so as to specify the type of data by registering in the list.

  As the storage medium, nonvolatile memories having different specifications, specifically, EEPROM (storage medium α, storage medium γ) and flash memory (storage medium δ, storage medium ε: indicated as “flash” in the figure) In addition, an auxiliary RAM (storage medium β) is used. The persistent management class 102C is an individual medium management class 104C (corresponding to the EEPROM 2) when the data is state data including a setting value of a variable indicating the state of the application class 106C (hereinafter referred to as normal data). Specifically, in FIG. 2, the instance 104J (data management 2 in FIG. 3)) is selected. If the data is image data, the individual medium management class 103C (specifically, the instance 103J (data management 4 in FIG. 3) in FIG. 2) associated with the flash memory 2 is selected.

  When the data is important data defined as a security protection target (in this embodiment, contract data including personal information, etc.), individual medium management associated with an EEPROM 2 different from the status data EEPROM 1 The class 103C (specifically, the instance 104J (data management 1 in FIG. 3) in FIG. 2) is selected. If the data is log data including a communication log or an operation log of the device, an image is displayed. The individual medium management class 103C (specifically, the instance 103J (data management 3 in FIG. 3) in FIG. 2) associated with the flash memory 1 different from the data flash memory 2 is selected.

  As shown in FIG. 4, the persistence-compatible data class 101C displays an identification ID for uniquely specifying storage data as an address for storing its own instance (in the figure, “persistent data storage address”). Is generated). The identification ID can be made to coincide with, for example, the above address, or can be created in such a manner that data processing (such as calculation or addition of an identification bit) that can be uniquely restored to the original address is performed. In any case, the identification ID can be specified by referring to the address, and the address can be specified by referring to the identification ID.

  Then, the storage data is transferred to the persistence management class 102C with the identification ID. Further, the individual medium management classes 103C and 104C write the storage data transferred from the permanent management class 102C to the open address of the corresponding storage medium in a form to which the identification ID is given.

  Returning to FIG. 2, the persistence-supporting data class 101C implements the serialization interface 101I for serializing its own instance, and the serialized data is stored in the persistence management class 102C as storage data as shown in FIG. Deliver. The serialization interface 101I also has a method for acquiring the data size at the time of serialization and a method for deserializing the serialized storage data.

  Data particularly suitable for serialization is state data (normal data) including a setting value of a variable indicating the state of the application class 106C. However, data that exceeds a predetermined size or data that has been serialized in advance, specifically, the image data in the present embodiment is originally described as byte string data, Since serialization has been completed, serialization processing by the serialization interface 101I is not executed in the persistence-compatible data class 101C.

  As shown in FIG. 2, the image data saving process itself is also executed according to the instance created from the persistence-compatible data class and incorporating the image data, and the image data is also created from the storage address of the instance. Is given and converted to data for storage. As described above, by passing a reference to the image data in the permanent interface, it is possible to save the image data in a corresponding storage medium without using the serialized interface 101I.

  The persistence interface 101K receives from the application class 106C a restore request for reading the saved data that has already been saved and restoring it to the instance from the application class 106C in such a manner that the storage address of the corresponding instance can be specified (in addition, the save data Delete requests can also be accepted). As illustrated in FIG. 6, the persistence management class 102 </ b> C stores save lists 200 </ b> A to 200 </ b> D that store a list of identification IDs that specify stored data for storage in a form that can be specified by a storage medium that is a storage destination. Have. Here, the storage medium type can be indirectly specified by the data type (in FIG. 2, only the image data list (200D) and the normal data list (200B) are shown as the save list, and others are omitted. Drawing).

  Then, an identification ID is specified based on the address specified by the received restoration request, and further, the identification ID is searched on the storage lists 200A to 200D in FIG. The identification ID is transferred to the individual medium management classes 103C and 104C corresponding to the data type. At this time, it is only necessary to perform a search on the corresponding data type storage list in FIG. 6 by passing the identification information together with the identification ID.

  Each of the individual medium management classes 103C and 104C reads storage data corresponding to the received identification ID from the storage medium corresponding to the individual medium management class 103C and 104C, and stores the storage data in the persistence support data class 101C via the persistence management class 102C. Hand over. The persistence-compatible data class 101C restores the storage data (for example, serialized data) to the original instance (note that deserialization at the time of restoration is naturally omitted for data that has not been serialized) )

  FIG. 5 shows each sequence at the time of data storage and restoration. First, the application class 106C issues a data storage or restoration request to the persistence-compatible data class 101C (here, an instance of image data is created as its own instance) via the persistence interface 101K. . The persistence corresponding data class 101C requests the persistence management class 102C to save or restore the instance. The persistence management class 102C determines whether data serialization is necessary. If necessary, the persistence management class 102C requests serialization or deserialization from the persistence-compatible data class 101C, causes corresponding data conversion to be performed, and corresponding memory Request to write to or read from the medium.

The figure which shows notionally the structure of the control main body in the object-oriented vehicle control system of this invention from a viewpoint of an object-oriented platform. The class diagram according to the UML notation which shows the structure of the program which the control main body of FIG. 1 performs. The conceptual block diagram which shows the relationship between the software of a system, and hardware. The conceptual diagram which shows the flow of data serialization and storage medium preservation | save / reading. FIG. 3 is a sequence diagram corresponding to FIG. 2. The conceptual diagram of a preservation | save list. The conceptual block diagram which shows the flow of the information between the objects in this invention. The conceptual block diagram which shows the flow of the information between the objects in a prior art example.

Explanation of symbols

1 Program execution device (CPU)
40 Control subject
101C Persistence compatible data class 101K Persistence interface 101I Serialization interface 102C Persistence management class 103C, 104C Individual media management class 105I Data storage interface 106C Application class

Claims (14)

Is configured to include a CPU, the CPU executes the object-oriented program, a vehicle control device that controls the operation of in-vehicle electronics, said program,
Implementing a persistence interface for accepting from the application class a storage request for persistently storing the instance of the data as a target of the storage request from the application class involved in the operation control, Persistence for converting the own instance into storage data in a form to which medium specifying reference information, which is information to be referred to in order to specify a storage medium as a storage destination, is given by receiving the storage request Corresponding data class,
An individual medium management class provided to individually correspond to a storage medium or a storage medium group that is a storage destination candidate of the storage data, and for storing the storage data that has received a storage request in the corresponding storage medium; ,
Select the individual medium management class corresponding to the storage medium that is the data storage destination by referring to the medium specific reference information given to the storage data delivered from the persistence-compatible data class. A persistent management class for passing the storage data to the selected individual medium management class;
An object-oriented vehicle control device comprising: The program implements a data storage interface for accepting a write request to the storage medium from the persistence management class and stores a data storage method for each storage medium. Have
Each said individual media management class, object-oriented vehicle control device according to claim 1, wherein is built as a subclass to inherit the data management class. The medium specific reference information is a data type specifying information for specifying a type of the data,
Medium / data type correspondence information indicating the correspondence between the data type specified by the data type specifying information and the individual medium management class is prepared in advance.
The persistence management class, by reference to the medium / data category correspondence information, said select individual media management class corresponding to the type of data for storage, the storage data received passes for thereto object-oriented vehicle control device according to claim 1 or claim 2 is intended. The persistence management class refers to data size information as the medium specifying reference information, selects the individual medium management class corresponding to a storage medium serving as a data storage destination according to the data size information , and stores the storage data object-oriented vehicle control apparatus according to any one of claims 1 to 3 is intended for passing on this.   The object-oriented vehicle control device according to any one of claims 1 to 4, wherein non-volatile memories having different specifications are designated as the storage medium. When the data is state data including a setting value of a variable indicating the state of the application class, the persistent management class is the individual medium associated with an EEPROM which is one of the nonvolatile memories. select a management class, the data in the case of image data, according to claim 5, wherein is used for selecting the individual media management class associated with the flash memory which is one of the non-volatile memory An object-oriented vehicle control device. The persistence management class, the data previously in the case of important data defined, the state object oriented vehicle according to claim 6, wherein the EEPROM of the data is for selecting a different EEPROM Control device. The persistence management class, the data is, if a log data consisting of operation logs of the communication log or equipment, according to claim flash memory for the image data is for selecting a different flash memory The object-oriented vehicle control device according to claim 6 or 7. The persistence-compatible data class generates an identification ID for uniquely identifying the storage data from an address storing the instance, and stores the storage data in a form to which the identification ID is assigned. For passing to the persistence management class,
Any the individual media management classes, the saved data passed received from the persistence management class, of the identification ID is for writing to a corresponding storage medium applied to form the claims 1 to 8 The object-oriented vehicle control device according to claim 1. The persistent corresponding data class implements the serialization interface for serializing an instance of the own claim 9 is intended for passing the persistence management class the serialized data as the stored data The control apparatus for object-oriented vehicles as described. The persistence-compatible data class does not execute serialization processing by the serialization interface when the instance exceeds the predetermined size or is serialized in advance. , object-oriented vehicle control device according to claim 10 is provided for with the saved data the data.   The object-oriented vehicle control device according to claim 11, wherein the serialized data is image data. The persistence interface reads out the saved data that has already been saved and restores it to the instance from the application class in a form that can specify the address that stores the instance corresponding to the saved data. It is intended for accepting,
The persistence management class has a save list for storing a list of identification IDs that specify the saved data for saving in a form that can be specified by a storage medium as a save destination, and the received restore request is The identification ID is specified based on the specified address, and further, the storage medium is specified by searching the identification list for the identification ID, and the individual medium management class corresponding to the specified storage medium in is intended for passing the identification ID,
Each said individual media management classes, said received reads saved data corresponding to the identification ID from the corresponding storage medium, for transferring the stored data to the persistent corresponding data classes through the persistence management class And
The persistent corresponding data class object-oriented vehicle control device according to any one of claims 9 to 12 is used to recover the data for the storage in the instance of the own. The serialization interface, object-oriented vehicle control device according to claim 13 quoting claim 10 is intended to deserialize serialized the saved data was at the time of the restoration.

Images