Data processing system and data processing method

Abstract

A plurality of devices (110 (110A, 110B), 120) constituting an on-vehicle system (100) comprise respective databases (111, 121). A database (111) of a host device (110A) shares data with a database (121) of another device (120). The host device (110A) transmits, to other devices (110B, 120), data which has been updated at predetermined regular intervals or every time data of a field is updated, and the data is shared with the host device (110A). This makes it possible to improve the efficiency of a data transfer process, and to perform immediate transmission of urgent data or the like.

Description

[Technical Field]

[0001] The present invention relates to a data processing system and a data processing method. [Background technology]

[0002] In some data processing systems, each device has a database, and data is shared between the databases of a plurality of devices.

[0003] For example, an in-vehicle system has been disclosed in which data from sensors mounted on a vehicle is stored in a database for each unit, and the data in the database is shared between units (see, for example, Patent Document 1 below). [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2010-231407 Summary of the Invention [Problem to be solved by the invention]

[0005] However, conventional data processing systems have not been able to efficiently share data stored in databases between devices. For example, when data is transferred between devices every time the database is updated, communication occurs every time the database is updated, reducing the efficiency of the data transfer process. Furthermore, if the data stored in the database is outdated, invalid data may be transferred. Furthermore, setting up a shared database on a network allows data to be shared with anyone, making it impossible to maintain data security.

[0006] In view of the above-mentioned problems, an object of the present invention is to enable efficient use of data between devices that share a database. [Means for solving the problem]

[0007] The data processing system of the present invention is a data processing system in which multiple devices each have a database and share data, and each device has a control unit that periodically transmits updated data for fields registered in its own database to other devices that have databases with which the data is shared.

[0008] Furthermore, the data processing system of the present invention is a data processing system in which multiple devices each have a database and share data, and each device has a control unit that, when data in a field registered in its own database is updated, transmits the updated data to another device that has a database with which the field data is shared.

[0009] The control unit transmits data of a field having a high priority on the basis of the priority set for each field.

[0010] The control unit is also characterized in that, if the priority of the field of the updated data is higher than the priority of the field of the data being transmitted, it interrupts the data being transmitted and transmits the updated data.

[0011] Furthermore, the control unit is characterized in that, if the priority of the field of the updated data is higher than the priority of the field of the data being transmitted, it divides the data being transmitted into multiple pieces and transmits the updated data by interrupting the data being transmitted and transmitting the divided pieces of data that have not yet been transmitted.

[0012] In addition, the data processing system of the present invention is a data processing system in which multiple devices each have a database and share data, and the devices have a history of data registered for each field in the database, and a control unit that invalidates the data in the history that is older than a certain period of time.

[0013] The control unit may have a time window of a predetermined period, and invalidate the data that falls outside the time window.

[0014] The control unit is also characterized in that, when writing the data to the database, the control unit does not register the data outside the time window in the database.

[0015] The control unit may also be characterized in that, when reading the data from the database, the control unit does not read the data that falls outside the time window from the database, or notifies the user that the data is invalid.

[0016] Furthermore, the data processing system of the present invention is a data processing system in which multiple devices each have a database and share data, and the devices have a control unit that sets group information for each database, sets an encryption key for each database, and shares data with other devices only between databases that have the same group information and the same encryption key.

[0017] Furthermore, the data processing method of the present invention is a data processing method in which multiple devices each have a database and share data, and each device periodically executes a process of transmitting updated data for fields registered in its own database to another device that has a database with which the data is shared.

[0018] Furthermore, the data processing method of the present invention is a data processing method in which multiple devices each have a database and share data, and when data in a field registered in one device's own database is updated, the device executes a process to send the updated data to another device having a database with which the field data is shared.

[0019] In addition, the data processing method of the present invention is a data processing method in which a plurality of devices each have a database and share data, centre Registered for each field De The method is characterized by having a history of data and executing a process to invalidate the data in the history that is older than a certain period of time.

[0020] Furthermore, the data processing method of the present invention is a data processing method in which multiple devices each have a database and share data, wherein the devices set group information for each database, set an encryption key for each database, and execute a process of sharing data with other devices only between databases that have the same group information and the same encryption key.

[0021] According to the above configuration, when a device's database is updated, the updated data is sent to other devices at regular intervals or immediately upon data update, thereby improving the efficiency of data transfer processing and enabling the immediate transmission of urgent data, etc. Furthermore, each device stores a history of database data, and by invalidating data older than a certain period of time using a time window or the like, it becomes possible to avoid handling unnecessary old data. Furthermore, by setting an encryption key for each device's database on a group basis, data can be shared only between devices that have the encryption key, preventing unauthorized data sharing by third parties. [Effects of the Invention]

[0022] According to the present invention, it is possible to effectively use data between devices that share a database. [Brief explanation of the drawings]

[0023] [Figure 1] FIG. 1 illustrates an example of an overall configuration of a data processing system according to an embodiment. [Figure 2] FIG. 2 is a diagram illustrating an example of a hardware configuration of each device in the data processing system according to the embodiment. [Figure 3]FIG. 3 is an explanatory diagram of transmission timing control after data update (part 1). [Figure 4] FIG. 4 is an explanatory diagram of transmission timing control after data update (part 2). [Figure 5] FIG. 5 is an explanatory diagram of transmission timing control after data update (part 3). [Figure 6] FIG. 6 is an explanatory diagram of transmission timing control after data update (part 4). [Figure 7] FIG. 7 is an explanatory diagram of transmission timing control after data update (part 5). [Figure 8] FIG. 8 is a sequence diagram of an example of transmission timing control after data update (part 1). [Figure 9] FIG. 9 is a sequence diagram of an example of transmission timing control after data update (part 2). [Figure 10] FIG. 10 is an explanatory diagram of control for invalidating old data in the DB. [Figure 11] FIG. 11 is a diagram illustrating an example of control in which the DB invalidates old data. [Figure 12] Figure 12 is a sequence diagram of an example of control for invalidating old data in the DB. (Part 1) [Figure 13] FIG. 13 is a sequence diagram of a control example in which the DB invalidates old data. (Part 2) [Figure 14] FIG. 14 is an explanatory diagram of the control for linking an encryption key to a DB group. [Figure 15] FIG. 15 is a sequence diagram of an example of control for linking an encryption key to a DB group. DETAILED DESCRIPTION OF THE INVENTION

[0024] (Embodiment) DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Preferred embodiments of a data processing system and a data processing method according to the present invention will be described in detail below with reference to the accompanying drawings.

[0025] 1 is a diagram illustrating an example of the overall configuration of a data processing system according to an embodiment. In the embodiment, an in-vehicle system mounted on a vehicle will be described as an example of the data processing system. The in-vehicle system 100 includes devices 110 (110A, 110B) such as a system on a chip, and a microcontroller 120.

[0026] The device 110 (110A, 110B) includes a database (DB) 111, a camera 112, an image processing unit 113, a communication control unit 114, a secure unit 115, and a communication unit .

[0027] The camera 112 captures an image, and the image processing unit 113 processes the image data captured by the camera 112 and stores the image data in the database 111. The communication control unit 114 controls the sharing, communication, and encryption of data held in the database 111 with external devices. In the configuration example of FIG. 1, the external devices are the device 110B as seen from the device 110A and the microcontroller 120.

[0028] The secure unit 115 performs encryption / decryption processing on data to be communicated with external devices and data to be read from and written to the database 111. The communication unit 116 communicates with external devices via the network NW using a predetermined communication method based on the communication control of the communication control unit 114.

[0029] The communication method may be, for example, a local area network (LAN), a peripheral component interconnect (PCI), Express, a serial peripheral interface (SPI), or a controller area network (CAN).

[0030] The microcontroller 120 includes a database 121, a sensor 122, a data processing unit 123, a communication control unit 124, a secure unit 125, and a communication unit 126. The sensor 122 includes, for example, a radar sensor that detects objects in front of and behind the vehicle, and an acceleration sensor that detects the acceleration of the vehicle.

[0031] The data processing unit 123 stores in the database 121 radar data detected by the radar sensor 122a and acceleration data detected by the acceleration sensor 122b.

[0032] The communication control unit 124 controls the sharing, communication, and encryption of data held in the database 121 with external devices. The secure unit 125 performs encryption / decryption processing on data communicated with external devices and data read from and written to the database 121. The communication unit 126 communicates with external devices using a predetermined communication method based on the communication control of the communication control unit 124.

[0033] 1, the external devices are the device 110B as seen from the device 110A, and the microcontroller 120. As a result, the devices 110A, 110B, and the microcontroller 120 share the data in their respective databases 111, 121 via the network NW.

[0034] The device 110 acquires images of the inside and outside of the vehicle using a camera mounted on the vehicle, and shares the image data with the microcontroller 120 through data sharing. For example, when controlling the vehicle such as speed and steering, the microcontroller 120 controls the drive of the engine and motor for driving the vehicle by referring to the shared image data and sensor data (radar, acceleration, etc.).

[0035] 2 is a diagram showing an example of the hardware configuration of each device in the data processing system according to the embodiment. The functions of the device 110 and the microcontroller 120 shown in FIG.

[0036] 2, the system includes a control unit (CPU) 201, a read-only memory (ROM) 202, a random access memory (RAM) 203, an auxiliary storage unit 204 such as a semiconductor memory or a disk drive, a communication interface (I / F) 205, a secure engine 206, and an input / output I / F 210. The CPU 201 to the input / output I / F 210 are connected to each other via a bus 200.

[0037] The functions of the device 110 and microcontroller 120 shown in FIG. 1 can be configured, for example, as a single embedded device, or as part of a device with multiple functions. Depending on the device configuration, the device may have a display, keyboard, mouse, scanner, and printer, which can be connected via the input / output I / F 210.

[0038] The ROM 202 is a non-volatile memory that stores control programs, etc. The RAM 203 is a volatile memory that is used as a work area when the CPU 201 executes the arithmetic processing of the programs.

[0039] The communication I / F 205 controls the network NW and the internal interface, and inputs and outputs data between the network NW and external devices. In addition to the above, the network NW also includes Wi-Fi (registered trademark), Bluetooth (registered trademark), infrared communication (IrDA), etc., and can communicate with external devices wirelessly or via a wire.

[0040] The functions of the image processing unit 113, communication control unit 114, and secure unit 115 in the device 110 shown in Fig. 1 can be obtained by executing a program by the CPU 201 shown in Fig. 2. Furthermore, the functions of the data processing unit 123, communication control unit 124, and secure unit 125 in the microcontroller 120 shown in Fig. 1 can be obtained by executing a program by the CPU 201 shown in Fig. 2.

[0041] 1 can be configured using the auxiliary storage unit 204 in Fig. 2. The functions of the communication units 116 and 126 of the device 110 and microcontroller 120 in Fig. 1 can be configured using the communication I / F 205 in Fig. 2.

[0042] 1 are realized by the secure engine 206 shown in Fig. 2. The secure engine 206 is configured by an encryption circuit chip or software, and performs encryption / decryption processing on data communicated with external devices and data read / written to / from the databases 111 and 121 under the control of the communication control units 114 and 124.

[0043] (Data sharing control according to the embodiment) In the data processing system, a database has fields, sharing destinations can be set for each field, and data is transmitted to the sharing destinations. In the embodiment, the devices 110 (110A, 110B) and the communication control units 114, 124 of the microcontroller 120 have the following functions 1 to 3 for sharing data with external devices. An overview of each of functions 1 to 3 will be explained.

[0044] 1. Controlling the timing of transmission after data update The devices (device 110, microcontroller 120) transmit data to the sharing destination when updating field data registered in the database. At this time, the devices (communication control units 114, 124) perform the following data transmission control (1) and (2).

[0045] (1) Send database data at regular intervals. (2) Send immediately when data is updated.

[0046] It allows data to be selected on a field-by-field basis, and data that can be delayed is (1) sent periodically, while urgent data is (2) sent immediately. For example, fields can be prioritized, and higher-priority data can be sent first. Also, even when lower-priority data is being sent, higher-priority data can be sent by interrupting it. Furthermore, the device receiving the data can reject data that is older than a set time, and can reject data that is so old that it is meaningless because it would take too long to send via the Internet, etc.

[0047] 2. Control to keep a record of data registration and invalidate old data The database includes a history data list of data registration and a field list. For each field, it includes an area to be registered in the history data list and information on data sharing destinations.

[0048] Then, a time window is used for the history, and data that is older than a certain time and falls outside the time window is invalidated from the history. When old data is treated as invalid data, invalidating data that is older than a certain time means that unnecessary data does not need to be handled. Data can be invalidated, for example, by invalidating an identifier that indicates the state of the data (invalid, as described below). Alternatively, the actual data can be invalidated by discarding or deleting it.

[0049] 3. Associate an encryption key with the group. Each database has group information and sends its own data to other databases with the same group information. By linking (associating) an encryption key with the group, devices cannot send or receive data even if they belong to the same group unless they have the encryption key. This prevents third parties from sharing data without permission, improving security against unauthorized access.

[0050] (Function 1. Controlling the transmission time after data update) 3 to 7 are explanatory diagrams of transmission timing control after data update. First, Fig. 3 shows the data sharing state when data is updated. In Fig. 3, for example, device A corresponds to device 110A, and device B corresponds to microcontroller 120 (and device 110B).

[0051] As shown in Fig. 3, DB 111 of device A (110A) has fields 1 to 3, and DB 121 of sharing destination device B (120) also has similar fields 1 to 3. Assume that application 301 of device A (110A) updates data in field 2 of DB 111. In this case, device A (110A) transmits the updated data to device B (120), the data sharing destination. Device B (120) stores the received data in field 2 of database 121.

[0052] Fig. 4 is an explanatory diagram of Function 1(1) - Periodic Data Transmission. In the configuration example of Fig. 4(a), device A (110A) has a sensor group 401, and stores data from sensor 1 in field 1 of DB 111 in an updatable manner, data from sensor 2 in field 2 of DB 111 in an updatable manner, and data from sensor 3 in field 3 of DB 111 in an updatable manner. The arrows in the diagram indicate the flow of data, and data within device A (110A) is handled by addresses.

[0053] 4(a), it is assumed that there is a change in the detected value (data) of sensor 1, and the data of sensor 1 is updated and stored in field 1 of DB 111. After that, if there is a change in the detected value of sensor 3, the data of sensor 3 is updated and stored in field 3 of DB 111.

[0054] Device A (110A) has a data queue 412 and a transmission queue 413. Data of field 1 and data of field 3 are stored in the data queue 412 in the order of update of DB 111. Data queue 412 queues the data of fields 1 and 3 at specified fixed time intervals.

[0055] Figure 4(b) shows the transmission priority of the transmission queue. The transmission queue 413 transmits the stored data in order from the queue with the highest transmission priority to the queue with the lowest priority. In the case of Figure 4(a), the transmission queue 413 transmits the data stored in the queue with the highest priority (Any data 1 to 3) at regular intervals, and then transmits the data of fields 1 and 3 at regular intervals.

[0056] 5 is an explanatory diagram of function 1(2) immediate transmission at the time of data update. Assume that there is a change in the detected value (data) of sensor 1 of device A (110A), and the data of sensor 1 is updated and stored in field 1 of DB 111.

[0057] Immediately after the DB 111 is updated, device A (110A) sends the data of the corresponding field 1 to the transmission queue 413. Then, in response to the update of the DB 111, the transmission queue 413 immediately transmits the data of the high priority queue (Any data1).

[0058] Fig. 6 is an explanatory diagram of Function 1(2) immediate transmission with priority when data is updated. In the example of Fig. 6, priority is set in the field of DB 111, and data with higher priority is transmitted first.

[0059] Assume that data from sensor 2 is updated and stored in field 2 of DB 111. Here, assume that the priority of field 2 is set higher than the other fields 1 and 3. In this case, device A (110A) causes the updated data for field 2 to be queued with the highest priority in the transmission queue 413. As a result, data with a higher priority (data in field 2) is transmitted before data with a lower priority (Any data 1, 2).

[0060] 7 is an explanatory diagram of Function 1(2) - immediate interrupt transmission with priority when data is updated. As shown in Fig. 7(a), when data from sensor 2 is updated and stored in field 2, which has a high priority, in DB 111, it is assumed that low-priority data (Any data1) is being transmitted from transmission queue 413.

[0061] In this case, device A (110A) divides the data being transmitted (Any data1) into a plurality of (four in the illustrated example) pieces of data (Any data1-1 to 1-4), and continues transmitting Any data1-1.

[0062] 7(b), device A (110A) causes the data of field 2, which has a high priority, to be inserted into the highest priority queue of transmission queues 413. This allows transmission queue 413 to transmit the inserted data of field 2 immediately after transmitting Any data1-1. After this, the divided Any data1-2 will be transmitted.

[0063] As described above, according to the embodiment, data can be transmitted periodically or immediately upon updating the DB 111. Furthermore, the data to be transmitted immediately can be selected on a field-by-field basis in the DB 111.

[0064] As a result, device A (110A) can transmit data that can be slightly delayed at regular intervals as shown in Fig. 4, and can transmit urgent data with the highest priority as shown in Fig. 6. Furthermore, when urgent data occurs, even if low-priority data is being transmitted, the urgent data can be transmitted by interrupting the low-priority data as shown in Fig. 7.

[0065] 8 and 9 are sequence diagrams of an example of transmission timing control after data update. Fig. 8 shows an example of data transmission control corresponding to Function 1(1) data transmission at a fixed cycle (for example, 10 msec).

[0066] On the device A (110A) side, a task application A (301A), a DB 111, and a transmission queue (queuing task) 413 are arranged, and on the device B (120) side, a task application B (301B) and a DB 121 are arranged.

[0067] 8, it is assumed that there are two data updates to DB111 within a fixed period. First, task application A (301A) writes data to DB111 (step S802) in response to a data write request due to a change in sensor detection data (step S801). For example, the data written to DB111 includes DataStore1 (DB111), Range (sensor detection), 12345... (value).

[0068] The DB 111 queues the updated data in the transmission queue 413 (step S803). The data sent to the transmission queue 413 includes information for sharing data with device B (120) (data write to device B (120), task B (task application B (301B) / Datastore2, Range, 12345...)). The transmission queue 413 sorts the data in order of priority (step S804).

[0069] After that, task application A (301A) writes data to DB111 (step S806) in response to a data write request due to a change in the subsequent detection data of the same sensor (step S805). The data written to DB111 at this time includes DataStore1 (DB111), Range (sensor detection), 67890... (value after the change).

[0070] The DB 111 queues the updated data in the transmission queue 413 (step S807). The data sent to the transmission queue 413 includes information for sharing data with the device B (120) (data write to the device B (120), task B (task application B (301B) / Datastore2, Range, 67890...)).

[0071] Then, the transmission queue 413 rearranges the data in order of priority (step S808). The transmission queue 413 then transmits the data rearranged in order of priority to the device B (120) to update the data (step S809). As a result, the device A (110A) can transmit two pieces of data updated during a certain period together to the device B (120), allowing the DB 111 of the device A (110A) and the DB 121 of the device B (120) to share data.

[0072] Next, Fig. 9 shows an example of data transmission control corresponding to Function 1(2) Immediate Transmission. First, task application A (301A) writes data to DB111 (step S902) in response to a data write request due to a change in sensor detection data (step S901). For example, the data to be written to DB111 (SepDataStoreWriteDataField) includes DataStore1 (DB111), Range (sensor detection), 12345... (value).

[0073] The DB 111 transmits the updated data to the DB 121 of the device B (120) and updates the DB 121 (step S903). As shown in the example of Fig. 9, the updated data is urgent and has high priority in the device A (101A), so it can be transmitted to the device B (120) immediately without going through the transmission queue 413.

[0074] In this way, every time data is updated in device A (110A), the DB 111 and DB 121 of device B (120) can immediately be made to share data.

[0075] (Function 2. Maintaining a data registration history and controlling the invalidation of old data) 10A and 10B are explanatory diagrams of control for invalidating old data in a DB. As shown in Fig. 10A, the device 110 has a history (e.g., registration date and time) for each data field in the DB 111. The device 120 also has a history for each data field in the DB 121, similar to the device 110.

[0076] Taking the device 110 as an example, the application 301 of the device 110 determines which data is valid among the data held in the DB 111. In other words, after the application 301 acquires data from the DB 111, it must determine the validity of the data.

[0077] 10(b) shows data control of DB 111 in the embodiment. In the embodiment, the device 110 (communication control unit 114) sets a time window T for the history of DB 111, and deletes data older than a certain time that falls outside the time window T from the history (DB 111).

[0078] 10(b), the device 110 determines that the data of history 1 and history 2 is located within the time window T (i.e., new data) and that the data of history 3 is located outside the time window T (old data).The device 110 (communication control unit 114) then deletes the old data of history 3, which is located outside the time window T, from the DB 111.

[0079] As a result, when old data is treated as invalid data, old data that has been there for a certain period of time or more is invalidated from the DB (for example, notified as invalid. The actual data may also be discarded or deleted), thereby eliminating the need for the device 110 to handle unnecessary data. In this case, the application 301 retrieves only valid data from the DB 111, eliminating the need for the application 301 to determine the validity of the data, thereby reducing the processing load. The time window T can be set arbitrarily; for example, by setting it to unlimited, all data from the DB 111 can be retrieved by the application 301.

[0080] Furthermore, when receiving data, the device 110 can prevent data older than the time set in the time window T from being accepted. For example, when writing acquired sensor data to the DB 111, data with a time outside the set time window T can be invalidated.

[0081] 11 is a diagram illustrating an example of control in which the DB invalidates old data. Fields 1 to 3 of the DB 111 store data D1 to D3, each corresponding to a different time (time stamp).

[0082] Now, suppose that a predetermined time window T is set in DB 111. After setting this time window T, if the timestamp of data D1-2 acquired from update data D1 (D1-1 to D1-4) of field 1 acquired by device 110 is outside the time window T, device 110 invalidates the acquired data D1-2 of field 1.

[0083] Furthermore, for example, the timestamp of data D3-5 of update data D3 (D3-1 to D3-6) of field 3 acquired by device 110 is within time window T, so device 110 registers acquired data D3-5 of field 3 in DB 111. In this way, it is possible to deal with cases where the timestamps of data acquired in order change due to fluctuations in the communication state between a sensor or the like and device 110, and it becomes possible to invalidate old data (D1-2) outside the time window T.

[0084] 12 and 13 are sequence diagrams of a control example in which the DB invalidates old data. A control example corresponding to the invalidation of data D1-2 shown in Fig. 11 will be described. Fig. 12 illustrates an example in which the DB 111 responds by declaring data outside the time window T as invalid when reading.

[0085] Based on the data read request (step S1201), the task application 301 of the device 110 reads the corresponding data from the DB 111 (step S1202). The read command at this time includes, for example, SepDataStoreReadFieldOnIndex(DataStore1 (DB111), SensorA (sensor), 2 (second data)).

[0086] Here, the DB 111 determines whether any of the stored data has a timestamp outside the time window T (step S1203). In the example of Fig. 11, the DB 111 determines that the data D1-2 from Sensor A is outside the time window T, and treats this data D1-2 as invalid. As a result, the DB 111 responds to the task application 301 that the data D1-2 does not exist (step S1204).

[0087] FIG. 13 illustrates an example in which the DB 111 invalidates data outside the time window T when data is synchronously written in the devices A and B.

[0088] In response to a data write request from task application A (301A) of device A (110A) due to a change in the sensor detection data (step S1301), device A (110A) writes data to DB 111 (step S1302). For example, the write command to DB 111 includes DataStoreWriteDataField(DataStore1(DB111), Range(sensor detection), 12345...(value)).

[0089] Here, DB111 determines whether there is any data among the data requested to be written and stored data whose timestamp falls outside the time window T (step S1303). For example, if there is any data among the data stored in DB111 whose timestamp falls outside the time window T (for example, data D1-2 of Sensor A shown in the example of FIG. 11), DB111 invalidates this data D1-2.

[0090] Furthermore, the DB 111 of the device A (110A) notifies the DB 121 of the device B (120) of a data update indicating that the data D1-2 has been deleted (step S1304). As a result of this data update, the DB 121 of the device B (120) deletes the shared data D1-2.

[0091] (Function 3. Control of linking encryption keys to groups) 14A and 14B are explanatory diagrams of the control for linking an encryption key to a group of DBs. As shown in Fig. 14A, DB 111 has group information and transmits its own data to DB 121 having the same group information.

[0092] 14(a), group A is set in DB 111A of device A (110) (step S1401). DB 111A notifies external DB 121 of the setting of group A (step S1402). Group A is also set in DB 121, and DB 121 notifies DB 111A of the existence of a group with the same name (group A) (step S1403).

[0093] As a result, the DB 111A transmits its own data (field data 1 to 3) to the DB 121 (step S1404).

[0094] According to the configuration in Figure 14(a), DBs in the same group on the same network can share data with anyone. However, there is a possibility that data (values) may be stolen or written by undesirable parties or due to a setting error.

[0095] Fig. 14(b) shows how an encryption key is linked to a group of DBs according to an embodiment. In the example of Fig. 14(b), DB 111A of device 110A and DB 121 of device 120 hold the same group (group A) and the same encryption key (group key A), and DBs 111A and 121 can share data.

[0096] On the other hand, suppose that group A is set in DB 111B of device 110B, but the encryption key is group key C. In this case, DB 111A (and DB 120) cannot be shared with DB 111B.

[0097] In this way, by linking the encryption key in addition to the group settings, even if people belong to the same group, they cannot send or receive data unless they have the same encryption key. This means that even if a third party manages to set up group sharing without permission, they will not be able to share the database unless they have the group's encryption key, thereby improving security.

[0098] 15 is a sequence diagram of an example of control for linking an encryption key to a DB group. This example shows an application of this control to periodic data transmission control between device A (111A) and device B (120) shown in FIG.

[0099] 8, it is assumed that data is updated twice in the DB 111 within a fixed period. First, task application A (301A) writes data to the DB 111 (step S1502) in response to a data write request due to a change in the sensor detection data (step S1501).

[0100] The DB 111 queues the updated data in the transmission queue 413 (step S1503). The data sent to the transmission queue 413 includes information for sharing data with the device B (120).

[0101] Thereafter, task application A (301A) writes data to DB 111 (step S1505) in response to a data write request due to a change in the subsequent detection data of the same sensor (step S1504).

[0102] The DB 111 queues the updated data in the transmission queue 413 (step S1506).

[0103] Then, the transmission queue 413 encrypts the two queued data items with the group key, adds an authentication code to the data, and transmits it to device B (120) to update the data (step S1507). As a result, device A (110A) encrypts the two data items updated during a certain period together with the encryption key and transmits them to device B (120), and DB 121 of device B (120) can share data with DB 111 of device A (110A) which has the same encryption key.

[0104] As described above, according to the embodiment, in a data processing system in which multiple devices each have a database and share data, each device periodically transmits updated data for fields registered in its own database to other devices that share the data database. This allows data updated within a certain period to be transmitted collectively to the other shared devices, thereby improving the efficiency of data transfer processing.

[0105] Furthermore, when field data registered in a device's own database is updated, the device can transmit the updated data to other devices that have databases with which the field data is shared, allowing data to be immediately transmitted to other devices whenever it is updated.

[0106] Furthermore, devices can prioritize the transmission of data in high-priority fields based on the priority set for each field, allowing data in high-priority fields, such as urgent data, to be shared among multiple devices without any time lag.

[0107] Furthermore, if the priority of the field of the updated data is higher than the priority of the field of the data being sent, the device can interrupt the data being sent and send the updated data. For example, if the priority of the field of the updated data is higher than the priority of the field of the data being sent, the device divides the data being sent into multiple pieces and sends the updated data into the divided pieces of data that have not yet been sent, interrupting the data being sent. This makes it possible to send data in high-priority fields to other devices with which data is shared with as little time lag as possible.

[0108] Furthermore, the device has a history of data registered for each field in the database, and can invalidate historical data older than a certain period of time. For example, the device has a time window of a predetermined period, invalidates data that falls outside the time window, and when writing data to the database, does not register data that falls outside the time window in the database. Furthermore, when reading data from the database, data that falls outside the time window is not read from the database, or notifies the database that the data is invalid. This reduces the processing load on the database of each device by invalidating old, unnecessary data among the data stored, and also enables efficient use of database capacity.

[0109] Furthermore, a device can set group information for each database and an encryption key for each database, and can only share data with other devices between databases that have the same group information and encryption key. This allows data to be shared only between devices that have the encryption key, preventing unauthorized data sharing by third parties. [Explanation of symbols]

[0110] 100 In-Vehicle Systems 110,120 equipment 111,121 databases (DB) 112 Camera 113 Image processing section 114,124 Communication control unit 115,125 Secure Department 116,126 Communications Department 122 sensors 123 Data Processing Unit 201 CPU 202 ROM 203 RAM 204 Auxiliary storage 205 Communication Interface 206 Secure Engine 301 Application (Task Application) 412 Data Queue 413 Send Queue NW Network T Time Window

Claims

1. In a data processing system in which multiple devices each have a database and share data, The device comprises: a control unit that periodically transmits updated data for fields registered in its own database to the other device that has a database with which the data is shared; the control unit transmits data of a field having a higher priority on the basis of the priority set for each field. A data processing system comprising:

2. In a data processing system in which multiple devices each have a database and share data, The device comprises: a control unit configured to, when field data registered in its own database is updated, transmit the updated data to another device having a destination database with which the field data is shared; the control unit transmits data of a field having a higher priority on the basis of the priority set for each field. A data processing system comprising:

3. (delete)

4. The control unit If the priority of the field of the updated data is higher than the priority of the field of the data currently being transmitted, the updated data is transmitted by interrupting the data currently being transmitted.

3. The data processing system of claim 2.

5. The control unit If the priority of the field of the updated data is higher than the priority of the field of the data being transmitted, divide the data being transmitted into a plurality of parts; transmitting the updated data in addition to the divided data that has not yet been transmitted, by interrupting the data currently being transmitted; 5. The data processing system of claim 4.

6. In a data processing system in which multiple devices each have a database and share data, The device comprises: a control unit that has a history of data registered for each field of the database and invalidates the data in the history that is older than a certain period of time; A data processing system comprising:

7. The control unit A time window is set for a predetermined period, and the data that falls outside the time window is invalidated.

7. The data processing system of claim 6.

8. The control unit When writing the data to the database, the data that falls outside the time window is not registered in the database.

8. The data processing system of claim 7.

9. The control unit When reading the data from the database, the data outside the time window is not read from the database, or the data is notified as invalid.

8. The data processing system of claim 7.

10. In a data processing system in which multiple devices each have a database and share data, The device comprises: Set group information for each of the databases, An encryption key is set for each of the databases, a control unit that shares data only between databases having the same group information and the same encryption key with other devices; A data processing system comprising:

11. A data processing method in which multiple devices each have a database and share data, The device comprises: Executes a process of periodically transmitting updated data for fields registered in its own database to the other device having a database with which the data is shared; the transmitting process transmits data of a field having a higher priority on the basis of the priority set for each field; A data processing method comprising:

12. A data processing method in which multiple devices each have a database and share data, The device comprises: When data in a field registered in its own database is updated, the updated data is transmitted to another device having a database with which the data in the field is shared; the transmitting process transmits data of a field having a higher priority on the basis of the priority set for each field; A data processing method comprising:

13. A data processing method in which multiple devices each have a database and share data, The device comprises: The database has a history of data registered for each field, and executes a process to invalidate the data in the history that is older than a certain period of time. A data processing method comprising:

14. A data processing method in which multiple devices each have a database and share data, The device comprises: Set group information for each of the databases, An encryption key is set for each of the databases, executes a process of sharing data between only databases having the same group information and the same encryption key with other devices; A data processing method comprising:

Images