RECORDING CONTROL DEVICE

Abstract

A recording control device (10) configured to control recording of a data item in one or more recording sections (14, 24, 34, 44, 54), the recording control device comprising: a data acquiring section (17) configured to acquire the data item having a plurality of types; a data read-only storage section (S110, S140, S190, S670) configured to store, in the one or more recording sections, the one or more data items that match a recording condition prepared in advance of the acquired data item having the plurality of types; a condition changing section (S135, S185, S260) configured to to define the recording condition as an old recording condition, and to specify that the data storage section uses a new recording condition instead of the old recording condition when the new recording condition different from the old condition is received from the outside; a time transmission section (S630) configured to transmit reference time information to a partner device (20), the partner device corresponding to a communication counterpart of the recording control device, and returning a response data item obtained by applying information to be transmitted by the partner device to the reference time information when the reference time information indicating a time managed by the recording control device is received; and a time setting section (S650) configured to to obtain the response data element, and to set a generation time of the response data element based on the reference time information of the response data element, where: the data storage section causes the data item to be recorded in association with the generation time of the response data item.

Description

[Technical field]

[0001] The present disclosure relates to a technique for controlling recording of data in a recording section. STATE OF THE ART

[0002] JP 2016 - 45 860 A discloses a technology for recording data collected from a vehicle in a recording section.

[0003] Reference is further made to JP 2013 - 41 443 A, US 2013 / 0 047 028 A1, and WO 99 / 50 849 A1, which have been identified as prior art. JP 2013 - 41 443 A and US 2013 / 0 047 028 A1 describe a management of storage devices. WO 99 / 50 849 A1 describes a data output device and a data input / output device.

[0004]

[0004] In the case of data recording, the required data changes depending on the situation. Therefore, the data that needs to be recorded also differs. The inventor's thorough investigation revealed a difficulty. Regarding the difficulty, the technology of JP 2016-45860 A can provide all the required data if all the data is recorded. However, since the capacity of a recording section has an upper limit, not all the data may be recorded.

[0005] An object of the invention is to provide a technology capable of efficiently recording required data according to a capacity of a recording section in a recording control device configured to control recording of the data in one or more recording sections.

[0006] The problem is solved by the features of the independent claims. Advantageous further developments are found in the dependent claims.

[0007] According to one aspect of the present disclosure, a recording control device is configured to control recording of a piece of data in a recording section, and includes: a data acquisition section; a data storage section; and a condition changing section. The data acquisition section is configured to acquire the piece of data having multiple types. The data storage section is configured to store, in the recording section, a piece of data from the acquired piece of data that conforms to a pre-prepared recording condition.

[0008] The condition change section is configured to define the recording condition as an old recording condition and to execute settings to use a new recording condition instead of the old recording condition when the new recording condition different from the old recording condition is received from the outside.

[0009] In such a recording control device, it may be possible to store the data item in the recording section according to a new recording condition when the new recording condition is received. It may be possible to efficiently store the required data item according to the capacity of the storage section by setting an appropriate recording condition.

[0010] The reference numerals in parentheses described in the claims simply indicate the correspondence to the specific means described in the embodiments that are an example of the present disclosure. Thus, the technical scope of the present invention is not necessarily limited thereto. Brief description of the drawings Fig. 1 is a block diagram showing a configuration of a data providing system 1; Fig. 2 is a flowchart showing vehicle processing; Fig. 3 is an explanatory view showing an overview of a service bus; Fig. 4 is a flowchart showing fault diagnosis processing; Fig. 5 is a flowchart showing recording processing; Fig. 6 is a block diagram showing a memory management function; Fig. 7 is a block diagram showing a function for managing time information; and Fig. 8 is a flowchart showing data transmission processing. DESCRIPTION OF EMBODIMENTS

[0011] Embodiments according to an aspect of the present disclosure will be described below with reference to the drawings. [1. Embodiment][1-1. Configuration]

[0012] A data provision system 1 that is Fig. 1, has a function of collecting appropriate information in a vehicle and providing the information to the outside. The data provision system 1 includes an information control GW 10, a base GW 20, and a communication line 5. GW is an abbreviation for gateway.

[0013] The communication line 5 communicatively connects the information control GW 10 and the base GW 20. The data provision system 1 may include a communication line 6, each of the ECUs 30, 40, and 50, and a server 60. The communication line 6 communicatively connects the base GW 20 and each of the ECUs 30, 40, and 50.

[0014] The information control GW 10, the base GW 20, the communication lines 5 and 6, and each of the ECUs 30, 40, and 50 are mounted on the vehicle. The server 60 is located outside the vehicle. The server 60 can communicate with the information control GW 10 via a communication line 53, an Internet network 52, and a base station 51. The base station 51 corresponds to a well-known base station such as a mobile phone and communicates with the vehicle via a wireless section 15 described later.

[0015] The information control GW 10, the base GW 20, and the server 60 mainly include a known microcomputer having CPUs 11, 21, and 61 respectively, and a semiconductor memory (hereinafter referred to as memory 12, 22, and 62) such as a RAM, a ROM, or a flash memory.

[0016] The information control GW 10, the base GW 20, and the server 60 include correspondingly associated communication sections 13, 23, and 63. The information control GW 10 and the base GW 20 further include read-only memories 14 and 24. The information control GW 10 further includes the wireless section 15 and a display section 16.

[0017] The communication sections 13, 23 and 63 function as known communication interfaces used at a time of performing communication via the communication lines 5, 6 and 53 connected to the own device and the own device, respectively.

[0018] Read-only memories 14 and 24 are configured as any storage area, such as a hard disk drive or flash memory. Any known configuration can be used for read-only memories 14 and 24.

[0019] The wireless section 15 is configured as a known wireless communication module that communicates with the base station 51. The display section 16 is configured as a known display that displays an image according to a video signal.

[0020] ECUs 30, 40, and 50 each contain the CPU and memory (not shown). ECUs 30, 40, and 50 contain correspondingly associated read-only memories 34, 44, and 54.

[0021] The CPUs of the ECUs 30, 40, and 50 have a function of communicating with the devices via the communication line 6 and a function of reading / writing data from / to specific addresses of the ROMs 34, 44, and 54 in the self-device according to an external instruction. The CPUs of the ECUs 30, 40, and 50 have the function of detecting a free area of ​​the ROMs 34, 44, and 54 in the self-device and transmitting this information to a device connected to the communication line 6, such as the base GW 20. The data may be referred to as a data item.

[0022] Each of the functions of the information control GW 10, the base GW 20, and the server 60 is implemented by CPUs 11, 21, and 61, which execute a program stored in a non-volatile, tangible storage medium. In this example, the working memories 12, 22, and 62 correspond to the non-volatile, tangible storage medium in which the program is stored.

[0023] By executing this program, a process corresponding to the program is executed. The non-volatile tangible storage medium refers to a recording medium that excludes electromagnetic waves. The number of microcomputers constituting the information control GW 10, the base GW 20, and the server 60 may be one or more.

[0024] As a configuration of functions implemented by the program execution of the CPU 11 as shown in Fig. 1, the information control GW 10 includes a recording control section 17, a time management section 18, and a condition changing section 19.

[0025] A function of the recording control section 17 monitors data flowing in the communication line 5 and acquires several types of this data. Data among the acquired data that match a pre-prepared recording condition is stored in the ROMs 14, 24, 34, 44, and 54. That is, the function of the recording control section 17 controls the recording of data in the ROMs 14, 24, 34, 44, and 54.

[0026] The recording condition specifies conditions such as a data type, recording cycle, resolution, sampling time, and the presence / absence of a signal that constitutes a trigger. Details will be described in vehicle processing or the like described later.

[0027] The function of the time management section 18 applies a data acquisition time to the data stored in the ROMs 14, 24, 34, 44, and 54 according to an absolute time. The absolute time corresponds to the time managed by the information control GW 10. Details of the function of the time management section 18 will be described in a recording processing described later.

[0028] A function of the condition changing section 19 executes processing for changing the recording condition when a function of an application or data is recorded according to the external instruction.

[0029] The base GW 20 functions as a gateway device that relays data, and includes a vehicle information collection section 26A, a vehicle information conversion section 26B, and a vehicle software rewriting section 26C, or a section 26C for rewriting in-vehicle software as a configuration of a function implemented by the CPU 21 that executes the program. A function of the gateway device relays the data to be relayed between the plurality of communication lines 5 and 6 according to a pre-prepared table.

[0030] A function of the vehicle information collection section 26A collects the vehicle information necessary for fault diagnosis processing or the like. The function of the vehicle information collection section 26A may include a function as a vehicle information provision proxy, diagnosis master, or the like, which will be described later.

[0031] A function of the vehicle information conversion section 26B converts the vehicle information into a data type suitable for a used application and provides the vehicle information. The function of the vehicle information conversion section 26B may include a function as the vehicle information provision proxy or the like, which will be described later. That is, the function of the vehicle information conversion section 26B is configured to convert the data stored in the recording section into the corresponding preset type according to the type of service or application in a data provision destination. The function of the vehicle information conversion section 26B is configured to output the converted data to the data provision destination.

[0032] Specifically, when providing information about a vehicle speed, raw data such as "1500 pulses / s" may be provided, data obtained by converting raw data into a speed such as "100 km / h" may be provided, or data obtained by converting it into a magnitude related to a specific speed such as "limit speeding" may be provided. That is, after being converted into a type that a service user can easily use, the data can be provided.

[0033] A function of the vehicle software rewriting section 26C rewrites the application mounted in the vehicle. The function of the vehicle software rewriting section 26C may include a function as a reprogramming master or the like.

[0034] How Fig. As shown in Figure 1, the server 60 includes a diagnosis section 66 as a configuration of a function implemented by the CPU 61 that executes the program. The function of the diagnosis section 66 diagnoses the fault in the vehicle while modifying the data collected in the vehicle by executing the fault diagnosis processing described later.

[0035] A method for implementing these elements constituting the information control GW 10, the base GW 20, and the server 60 is not limited to software, and some or all of the elements may be implemented using one or more hardware elements. For example, if the above functions are implemented by an electronic circuit that is hardware, the electronic circuit may be implemented by a digital circuit including a large number of logic circuits, an analog circuit, or a combination of the digital circuit and the analog circuit. [1-2. Processing][1-2-1. Vehicle processing]

[0036] The vehicle processing executed by the CPU 11 of the information control GW 10 will be described with reference to a flowchart of Fig. 2 described.

[0037] In S110, the information control GW 10 periodically records information in a periodic diagnosis service. The periodic diagnosis service specifies the entire service for the server 60 to periodically diagnose the vehicle. The information control GW 10 performs processing to collect the data required by the server 60 to periodically diagnose the vehicle as part of the periodic diagnosis service.

[0038] For example, the periodic diagnostic service is linked to a recording condition for collecting information such as battery voltage, engine coolant temperature, and brake hydraulic pressure. The ROMs 14, 24, 34, 44, and 54 store data that meets this recording condition as periodic information.

[0039] When the data is collected, the ROMs 14, 24, 34, 44, and 54 store the data according to the recording condition. However, the recording condition is set for each service. Each parameter type is set as a recording condition. Each parameter type includes the type of collected data, the recording cycle at the time of data recording, the resolution of each data, the collection time determined by a start time and an end time of data collection, and the presence / absence of a signal as a trigger at the time of starting the data condition, or the like. Details of the processing for storing the data in the ROMs 14, 24, 34, 44, and 54 will be described in the recording processing described later.

[0040] In S120, the information control GW 10 uploads the periodic information to the server 60. When a time for a preset cycle, such as once a day, has elapsed, or when a power supply of the vehicle is turned on for the first time, or the like after the time for this cycle has elapsed, the periodic information is transmitted to the server 60 via the wireless section 15.

[0041] In S130, the information control GW 10 determines whether plug-and-play of a detailed diagnostic service has been received. Plug-and-play (PnP) here represents a function of coordinating hardware such as the information control GW 10 or the base GW 20, firmware, drivers, operating systems, and applications, as well as autonomously installing a connection tool and setting the connection tool when the connection tool, such as a peripheral device or an expansion card, is connected to the information control GW 10.

[0042] However, in the plug-and-play described here, the connection instrument does not need to be physically connected to the information control GW 10. It is also referred to as plug-and-play that the connection instrument is not physically connected, a program related to a specific service is received from the server 60, and the hardware and software are coordinated. Plug-and-play can be implemented by connecting any peripheral device, expansion card, or the like to the information control GW 10.

[0043] In the embodiment, the collection condition is configured to be changed dynamically, that is, without restarting the system, through plug-and-play. Here, the embodiment has a service bus function as an example of a configuration for implementing plug-and-play, as shown in Fig. 3 is shown.

[0044] In the well-known multi-tier architecture, that is, in a configuration in which applications are divided into several layers and the layers are developable and maintainable as separate modules, the service bus is configured as an application that bridges the data between the application layer and the presentation layer and a lower layer that represents a layer below the presentation layer.

[0045] The service bus transmits data so that the multiple devices that communicate via communication lines 5 and 6—here, the information control GW 10, the base GW 20, and the ECUs 30, 40, and 50—can communicate data as if they were one device. Therefore, the service bus includes a database for linking data used in the lower layer or a lower layer with data used in the application layer. The service bus performs data conversion between the application layer and the lower layer by referring to this database.

[0046] For example, when a device 100 uses a message as data that another device 200 includes, a device 100 transmits a request at the application layer as described in “[1] REQUEST TRANSMISSION” of Fig. 3. The service bus converts the data type appropriate for the lower layer or the layer below the lower layer. Data transmission is performed via communication lines 5 and 6.

[0047] Another device 200 receives this data and the service bus converts it into the data type usable in the application layer and the request is recognized in the application layer as described in “[2] REQUEST RECEIPT” of Fig. 3. As shown in “[3] REPLY TRANSFER” of Fig. 3, another device 200 returns the message in reverse order. As described in “[4] RESPONSE RECEIPT” of Fig. 3, a device 100 receives the message via the service bus.

[0048] That is, by placing the service bus, there is no need to deal with any lower layer or further lower layer structure when developing the application.

[0049] The service bus has the following features.

[0050] [1] The service bus is middleware installed in an instrument such as the vehicle-mounted ECU, a cloud server outside the vehicle, and a smartphone. Individual service buses are connected through cross-application communication, internal communication, and external communication, and a single service bus is virtually constructed. The service bus hides the lower layer, such as in-vehicle communication. This configuration allows a service developer to focus on service development.

[0051] [2] The service bus receives a start-up request from a vehicle system or service for activation. The service bus receives a stop request from the vehicle system for termination. This means that it may be possible to manage the service bus's activation state externally.

[0052] [3] The presence of the service bus enables, for example, the installation, uninstallation, and updating of applications such as services. For example, it may be possible to start the service upon activation of the service bus or upon receipt of a request from a start management service. It may be possible to stop the service upon stop of the service bus or upon receipt of a request from a stop management service. In other words, the presence of the service bus enables the management of the service state.

[0053] [4] Due to the presence of the service bus, it may be possible to receive an execution request from a consumer service representing a service that uses the particular service and execute a provider service representing a service that provides the particular service. For example, it may be possible to resolve an installation position of the provider service, perform different access for each provider service according to a consumer service, perform priority control such as arbitration on a service unit or a message unit, or the like.

[0054] In the embodiment, at a time of plug and play, plug and play is implemented by simple processing by only rewriting the application corresponding to the application layer or the application corresponding to the application layer and the service bus.

[0055] After determining that the plug-and-play of the detailed diagnosis service has been received in S130, the information control GW 10 proceeds to S135 and changes the recording condition to a recording condition corresponding to the detailed diagnosis service. The detailed diagnosis service corresponds to a service that performs fault diagnosis in more detail than the periodic diagnosis service. For example, the recording condition corresponding to the detailed diagnosis service is set to a condition where the type of stored data is multiple and the frequency of data acquisition is higher than the recording condition corresponding to the periodic diagnosis service.

[0056] That is, in the processing described above, an input is received through plug-and-play, and the data type provided to the server 60 is changed. When the data type is changed, it is determined to receive a new recording condition associated with the detailed diagnosis service from the outside, and to use the new recording condition instead of the recording condition in the periodic diagnosis service.

[0057] In S140, the information control GW 10 records the detailed information in the detailed diagnosis service. The data that meets the recording condition according to the detailed diagnosis service is stored as detailed information in the ROMs 14, 24, 34, 44, and 54.

[0058] In S150, the information control GW 10 uploads the detailed information. The detailed information is immediately transmitted to the server 60 via the wireless section 15.

[0059] On the other hand, if the information control GW 10 determines in S130 that the plug-and-play of the detailed diagnosis service has not been received, the information control GW 10 proceeds to S180 and determines whether the plug-and-play of a progress observation service has been received. The progress observation service is a service that observes progress after a time at which the vehicle is diagnosed as having a fault.

[0060] After determining in S180 that the plug-and-play of the progress monitoring service has been received, the information control GW 10 proceeds to S185 and changes the recording condition to a recording condition corresponding to the progress monitoring service. For example, the recording condition corresponding to the progress monitoring service is set to a condition that the type of stored data is more or that more types of data are stored than the recording condition corresponding to the periodic diagnosis service, and a state of a failure point can be monitored according to the failure point.

[0061] In S190, the information control GW 10 records progress information in the progress monitoring service. Data that meets the recording condition according to the progress monitoring service is stored as progress information in the ROMs 14, 24, 34, 44, and 54.

[0062] In S200, the information control GW 10 uploads the progress information. When a time has elapsed for a preset cycle, such as once a day, similar to the periodic information, the progress information is transmitted to the server 60 via the wireless section 15.

[0063] On the other hand, if the information control GW 10 determines in S180 that the plug-and-play of the progress monitoring service has not been received, the information control GW 10 proceeds to S230 and determines whether entry guidance has been received. The entry guidance represents guidance for recommending access to or entry into a repair shop because it is diagnosed that the failure is occurring.

[0064] After determining in S230 that the entry guidance has been received, the information control GW 10 proceeds to S240 and performs an entry display in the display section 16. For example, the information control GW 10 causes the display section 16 to display, for example, a message such as "Please have inspection performed at a repair shop" as an entry display.

[0065] On the other hand, if the information control GW 10 determines in S230 that the entry guidance has not been received, the information control GW 10 proceeds to S250 and determines whether software rewriting has been received. Software rewriting is an instruction to rewrite the software of the information control GW 10, the base GW 20, the ECUs 30, 40, and 50, or the like. Rewriting data corresponding to a program for updating is also received with the instruction.

[0066] After determining in S250 that the software rewriting has been received, the information control GW 10 proceeds to S260. After determining the software rewriting, the information control GW 10 terminates the vehicle processing of Fig. 2. It is set to update the software based on the rewrite data. The software is updated when the vehicle is not moving, such as when parked.

[0067] On the other hand, after determining in S250 that the software rewriting has not been received, the information control GW 10 terminates the vehicle processing of Fig. 2. [1-2-2. Fault diagnosis processing]

[0068] The fault diagnosis processing executed by the server 60 will be described with reference to the flowchart of Fig. 4. In the fault diagnosis processing, the server 60 determines in S310 whether the periodic information has been acquired.

[0069] After determining in S310 that the periodic information has been acquired, the server 60 proceeds to S320 and performs a periodic diagnosis. The periodic diagnosis represents processing executed in the server 60 in the periodic diagnosis service. For example, in the periodic diagnosis, it is determined whether the periodic information deviates from the pre-prepared standard information. If the periodic information deviates from the standard information, it is determined that an abnormality exists.

[0070] In S330, the server 60 determines whether there is an abnormality in any part of the vehicle. If it is determined in S330 that there is an abnormality, the server 60 proceeds to S340 and performs the plug-and-play of the detailed diagnosis service.

[0071] On the other hand, if it is determined in S330 that there is no abnormality, or it is determined in S310 that the periodic information has not been acquired, the server 60 proceeds to S370 and determines whether the detailed information has been acquired.

[0072] After determining in S370 that the detailed information has been required or acquired, the server 60 proceeds to S380 and performs detailed diagnosis. The detailed diagnosis represents processing executed in the server 60 in the detailed diagnosis service. In the detailed diagnosis, it is determined that the periodic information differs from the pre-prepared standard information in more data. However, the acquisition time of the data is set to be shorter than the periodic diagnosis service because a capacity of the (read-only) memory is limited.

[0073] The server 60 detects whether the detailed information data deviates from the standard information and estimates the abnormal point according to the data type in which the abnormality is detected. Then, at least whether the abnormality is a hardware failure or a software abnormality is identified.

[0074] In S390, the server 60 determines whether the vehicle had the error. After determining in S390 that the vehicle had the error, the server 60 proceeds to S400 and determines whether the error is a hardware error.

[0075] After determining in S400 that the error is a hardware failure, the server 60 proceeds to S410. After transmitting the entry guidance, the server 60 proceeds to S430. On the other hand, if determining in S400 that the error is not a hardware failure, the server 60 proceeds to S420 and transmits the software rewriting.

[0076] After determining in S390 that the vehicle had no fault, the server 60 proceeds to S430 and performs the plug and play of the progress monitoring service.

[0077] After determining in S370 that the detailed information has not been acquired, the server 60 proceeds to S460 and determines whether the progress information has been acquired. After determining in S460 that the progress information has been acquired, the server 60 proceeds to S470 and performs progress monitoring. In progress monitoring, it is detected which data of the progress information deviates from the standard information. The abnormal point is estimated according to the data type in which the abnormality is detected.

[0078] In S480, the server 60 determines whether there is a difficulty in progress observation. After determining in S480 that there is a difficulty in progress observation, the server 60 proceeds to S490. After transmitting the entry guidance, the server 60 terminates the fault diagnosis processing of Fig. 4.

[0079] On the other hand, after determining in S460 that the progress information has not been acquired and after determining in S480 that there is no difficulty in progress observation, the server 60 ends the fault diagnosis processing of Fig. 4. The free capacity can be called the free area. [1-2-3. Recording processing and data transmission processing]

[0080] A recording processing executed by the information control GW 10 will be described with reference to the flowchart of Fig. 5. The recording processing described below represents details of S110, S140, and S190. In S610, the information control GW 10 detects the free capacity of each (read-only) memory.

[0081] In this processing, as in Fig. 6, the information control GW 10 and the base GW 20 cooperate and detect the free area of ​​the read-only memories 14, 24, 34, 44 and 54 of each of the devices connected to each of the communication lines 5 and 6.

[0082] The information control GW 10 has, as part of functions of the recording control section 17, a function as a read-only memory master 171 and a function as a dynamic probing client 172, as shown in Fig. 6 and Fig. 7. The base GW 20 has a function as a dynamic probing server 27, as shown in Fig. 6 and Fig. 7 is shown.

[0083] The ROM master 171 has a function of detecting the free areas of the ROMs 14, 24, 34, 44 and 54 and determining a position for recording the data.

[0084] The dynamic probing client 172 has a function for transmitting reference time information and applying absolute time to the received data.

[0085] The dynamic probing server 27 has a function of adding internal information for applying time information to the transmitted data in the information control GW 10.

[0086] In each of the ROMs 14, 24, 34, 44, and 54, an area is predefined in which data can be recorded by the recording processing. The information control GW 10 detects the free area of ​​the ROM 14 of the self-device in this area using the ROM master 171 function. The base GW 20 detects the free areas of a plurality of ROMs 14, 24, 34, 44, and 54 connected to a subordinate of the base GW 20, that is, the communication line 6 on one side of the base GW 20, using the dynamic probing server 27 function.

[0087] Then, the base GW 20 detects the free area through the communication between the base GW 20 and the ECUs 30, 40, and 50 and transmits this information to the information control GW 10.

[0088] In S620, the information control GW 10 sets the recording address. The recording address represents a position of the free area in each of the ROMs 14, 24, 34, 44, and 54, that is, an address.

[0089] In S630, the information control GW 10 transmits the reference time information. The reference time information represents a uniquely identifiable number of a reference time. The reference time represents a time corresponding to a reference managed by the information control GW 10 and the absolute time.

[0090] In the information control GW 10, a table is prepared in advance in which the reference time number and the absolute time are linked. This processing corresponds to a processing in which the information control GW 10 sends "[1] Reference time number" to the base GW 20 in Fig. 7 transmits.

[0091] After these processings, the basic GW 20 carries out a Fig. 8. The data transfer processing executed by the base GW 20 will be described with reference to a flowchart of Fig. 8 described.

[0092] In S710, the base GW 20 determines whether it is a data transmission time. The data transmission time represents a predefined time as the time at which the base GW 20 should transmit the data.

[0093] After determining in S710 that it is not the data transmission time, the base GW 20 terminates the data transmission processing of Fig. 8. On the other hand, if it is determined in S710 that it is the data transmission time, the base GW 20 proceeds to S720 and extracts the reference time information from the received data.

[0094] In S730, the base GW 20 acquires the vehicle information to be transmitted. This processing corresponds to a processing in which the base GW 20 acquires "[2] vehicle information" by executing the function as a vehicle information providing proxy 28 in Fig. 7 is used. The vehicle information corresponds to general data processed in the vehicle, such as information obtained from a sensor or the like, or information obtained by calculation by the ECU.

[0095] In S740, the base GW 20 applies the internal information. The internal information includes a timestamp. The timestamp contains the reference time number and an internal timer value.

[0096] The reference time number represents a number linked to the reference time of the information control GW 10. The internal timer value represents counter time values ​​of the base GW 20 and the other ECUs 30, 40, and 50.

[0097] This processing corresponds to a processing that the base GW 20 sends “[3] internal information” to the dynamic probing server 27 by performing the function as the vehicle information providing proxy 28 in Fig. 7 is used. In S750, after transferring package data, the base GW 20 terminates the data transfer processing of Fig. 8. The package data includes vehicle information and internal information.

[0098] The information control GW 10 receives such data transmission processing and executes processing in S640 and subsequent processings described in Fig. 5. In S640, the information control GW 10 determines whether the package data has been received.

[0099] After determining that the package data has not been received in S640, the information control GW 10 returns to S640. On the other hand, if it is determined in S640 that the package data has been received, the information control GW 10 proceeds to S650 and extracts the absolute time. In this processing, a delay time due to communication and a delay time due to internal processing of the base GW 20 are calculated using the reference time information transmitted by the information control GW 10, the absolute time when the package data is received, and the internal timer value. The time at which the vehicle information is obtained is estimated.

[0100] A mean value between the reference time information transmitted from the information control GW 10 and the absolute time at which the package data is received can be estimated as the time at which the vehicle information is obtained. A value obtained by subtracting the preset time according to a performance of the base GW 20 from the mean value, that is, a time before the mean time, can be estimated as the time at which the vehicle information is obtained.

[0101] In S660, the information control GW 10 determines whether the recording condition is satisfied. Based on the determination in S660 that the recording condition is satisfied, the information control GW 10 proceeds to S670. After applying the absolute time using the function of the dynamic probing client 172, the information control GW 10 records the data in the ROM corresponding to the recorded address and terminates the recording processing of Fig. 5. The recording condition here is a recording condition set according to the type of service.

[0102] On the other hand, if it is determined in S660 that the recording condition is not satisfied, the information control GW 10 ends the recording processing of Fig. 5. [1-3. Effects]

[0103] According to the embodiment described in detail above, the following effects are obtained.

[0104] (1a) The information control GW 10 of the present disclosure controls the recording of the data in the ROMs 14, 24, 34, 44, and 54. The CPU 11 functions as the recording control section 17. The CPU 11 acquires the plurality of data types and stores in the ROMs 14, 24, 34, 44, and 54 the data that conforms to the pre-prepared recording conditions of the acquired data.

[0105] The CPU 11 functions as the condition changing section 19. The CPU 11 is configured to determine to use the new recording condition instead of the old recording condition based on receiving the new recording condition from the outside which is different from the old recording condition.

[0106] In such an information control GW 10, it may be possible to store the data in the ROMs 14, 24, 34, 44, and 54 according to the new recording condition upon receipt of the new recording condition. Therefore, it may be possible to efficiently store the required data according to the capacities of the ROMs 14, 24, 34, 44, and 54 by setting the appropriate recording condition.

[0107] (1b) In the information control GW 10 described above, the CPU 11 functions as the recording control section 17. The CPU 11 confirms the free area, which is the area where data can be recorded, in the plurality of ROMs 14, 24, 34, 44, and 54 arranged at mutually different positions. The CPU 11 sets the address indicating the position of the free area. The CPU 11 records the data in the free area according to the address.

[0108] In such an information control GW 10, it may be possible to search the positions of the free areas of the multiple ROMs 14, 24, 34, 44, and 54 to record the data in these free areas. Therefore, it may be possible to use the multiple ROMs 14, 24, 34, 44, and 54 as if they were individual ROMs 14, 24, 34, 44, and 54.

[0109] (1c) In the information control GW 10, the CPU 11 functions as the time management section 18 and transmits the reference time information to the base GW 20. The base GW 20 is a device as a communication counterpart of the information control GW 10. Upon receiving the reference time information representing the time managed by the information control GW 10, the base GW 20 returns response data obtained by applying the information to be sent from the base GW 20 to the reference time information (for example, the package data).

[0110] The CPU 11 functions as the time management section 18. The CPU 11 acquires the response data and sets a generation time based on the reference time information of the response data. The CPU 11 functions as the recording control section 17 and links the generation time of the response data with the data to record the data.

[0111] In such an information control GW 10, the base GW 20 returns the reference time information transmitted from the information control GW 10 with the information to be transmitted. Therefore, it may be possible to link the obtained data with the time of the information control GW 10 to record the time, even if the base GW 20 has no time information or if the time information of the base GW 20 is different from the time of the information control GW 10.

[0112] (1d) In the information control GW 10 described above, the CPU 11 functions as the recording control section 17. The CPU 17 supplies the data stored in the ROMs 14, 24, 34, 44, and 54 to the server 60 positioned outside the information control GW 10.

[0113] The CPU 11 functions as the condition changing section 19. When the plug and play is entered, the CPU 11 changes at least the data type provided from the information control GW 10.

[0114] In such an information control GW 10, it may be possible to change the data type provided by the information control GW 10 only by the user's simple operation because the data type provided in plug and play is changed.

[0115] (1e) In the information control GW 10 described above, the CPU 11 functions as the condition changing section 19. The CPU 11 determines to use the new recording condition when the data type provided from the information control GW 10 is changed.

[0116] In such an information control GW 10, it may be possible to change the recording condition in plug-and-play. [2. Other embodiments]

[0117] Although the embodiments of the present disclosure have been described above, the present disclosure is not limited to the above-described embodiments, and various modifications may be made to implement the present disclosure.

[0118] (2a) In the above-described embodiment, the own vehicle information representing the vehicle on which the information control GW 10 is mounted is collected and provided to the server 60. However, it may be set that, using the request from the own vehicle as a trigger, the other vehicle information representing the vehicle other than the own vehicle can be collected via the server 60. In this case, the information control GW 10 can provide the preset data when the trigger is received via the server 60. In this case, it may be set that information is defined in terms of privacy, and the corresponding other vehicle information cannot be obtained from the own vehicle.

[0119] Information from other vehicles can be used for the following tasks.

[0120] [1] The information is used to collect vehicle information of the same vehicle type as the owner's vehicle for fault diagnosis of the owner's vehicle.

[0121] [2] The information is used to collect wiper operation information around a target to confirm whether it is raining around the target.

[0122] [3] The information is used for setting so that the vehicle information, such as images, movies or audios, can be collected to predict a position of an obstacle on a road or the like.

[0123] [4] The information is used to change a vehicle information collection condition from a user terminal such as a smartphone from a remote location to collect camera images or film information of the own vehicle.

[0124] [5] The information is used to change the vehicle information collection condition to collect in-vehicle audio information to analyze a factor at the time of a failure or an accident.

[0125] [6] The information is used to provide a bus load check function to the server 60, the information control GW 10, or the ECUs 30, 40, and 50 to establish communication related to control by controlling so that the load does not become too large.

[0126] [7] The information is used to absorb differences between manufacturers, vehicle types, and sensors, to provide information by generalizing the vehicle information to provide the vehicle information. The information is used to enable more in-vehicle devices or the like to share the data.

[0127] [8] The information is used to use a camera, millimeter wave radar, laser radar or the like when the obstacle is detected.

[0128] (2b) The information control GW 10 and the basic GW 20 may have the following functions. [1] Exploratory master

[0129] A probing master is a function for collecting any vehicle information in any way through any trigger to provide the information based on a variable collection condition according to use cases. For example, all vehicle information is virtually collected and all vehicle information is provided.

[0130] Specific requirements: The vehicle information is collected based on the variable collection condition to be provided based on a trigger from the collection condition service or a trigger of the vehicle detecting a fault or a sign of a fault, to perform periodic diagnosis, detailed diagnosis and progress monitoring in cooperation with a cloud. [2] Automotive Information Proxy (AIPX)

[0131] A vehicle information provision proxy is a function for generalizing vehicle information, such as the control or diagnostic framework, to provide the vehicle information in a form required by the service. For example, it may be possible to allow or deny different access controls for each piece of vehicle information according to the service user. Control logic is hidden from the outside by processing the vehicle information in accordance with the service user. Specific requirements: The AIPX is used to convert speed information into a form that can be easily used by the service user, such as "1500 pulses / s," "100 km / h," or "speeding," and to provide the speed information. Read-only memory master

[0132] A read-only memory with the capacity required by the service is provided by centrally managing excess read-only memory from control ECUs distributed throughout the vehicle. Specific requirements: A read-only memory service is used when a read-only memory that records collected vehicle information is in short supply due to a change in the collection condition. In the event of a hardware replacement, the read-only memory service is used when backing up data. The read-only memory service is used when the read-only memory that records individual settings for each user is in short supply.

[0133] That is, the read-only memory master 171 determines whether the data can be recorded in a specific recording section corresponding to one of the plurality of read-only memories. The specific recording section represents, for example, the read-only memory 14 of the information control GW 10, which corresponds to the device on which the read-only memory master 171 is mounted.

[0134] A case where the data cannot be recorded in the specific recording section corresponds to a case where the area of ​​the ROM 14 is scarce due to the change of the collection condition, a case where the ROM 14 is unusable at the time of hardware replacement or the like, a case where the ROM 14 recording individual settings for each user is scarce, or the like. The configuration for detecting that the collection condition is changed, the ROM 14 is unusable, and the ROM 14 is scarce may include a configuration for performing a separate determination and a configuration that a signal indicating the determination is input.

[0135] If the data cannot be recorded in the specific recording section, the ROM master 171 confirms the free capacity of the other ROM 24 or the like and records the data according to the address of the free capacity. The ROM master 171 causes the ROM 14 to record the data if the data can be stored in the ROM 14. Time management service

[0136] A time management service provides the time or elapsed time from a specified time. The time management service involves the ECU, which may not obtain the absolute time. Specific requirements: For fault diagnosis, in a case where an event is recorded, the time management service is used to record a time at which the vehicle information is collected or a time at which information occurs in the ECU in the base GW, which may not obtain the absolute time. Vehicle exterior communication service

[0137] The vehicle-external communication service absorbs the difference between a vehicle-external protocol and a service bus message to transmit the message to / receive the message from a vehicle-external service. Specific requirements: The vehicle-external communication service is used for fault diagnosis when the collected vehicle information is uploaded to the cloud. [6] Vehicle status notification service

[0138] A vehicle state notification service provides the vehicle state used for collection condition determination. The vehicle state includes a power state. Special requirements: The vehicle state notification service is used when vehicle information needs to be collected when the ignition is turned on or when +B is activated. The vehicle state notification service is used when vehicle information needs to be collected when changing lanes. [7] Diagnostic Master

[0139] The diagnostic master provides a diagnostic framework required by the service. To perform cloud-based fault diagnosis, the diagnostic master is used to read a DTC or an operating factor. [8] Reprogramming master

[0140] A reprogramming master changes the vehicle information that can be collected or provided by software rewriting the condition service, AIPX (access control or processing), or ECU. Special requirements: The reprogramming master is used when changing the collection condition or rewriting the software other than the PnP application is required.

[0141] (2c) A plurality of functions of one element in the above embodiment may be implemented by a plurality of elements, or a function of one element may be implemented by a plurality of elements. Further, a plurality of functions of a plurality of elements may be implemented by a plurality of elements, or a function implemented by a plurality of elements may be implemented by a plurality of elements. In addition, a part of the configuration of the above embodiment may be omitted. At least a part of the configuration of the above embodiment may be added to or replaced by another configuration of the above embodiment. All modes included in the technical idea identified by the wording described in the claims correspond to embodiments of the present disclosure.

[0142] (2d) The function of the information control GW 10 and the function of the base GW 20 may be provided to each other, or one may have all of the other function. Specifically, the functions of the recording control section 17, the time management section 18, and the condition changing section 19 of the information control GW 10 can be implemented by the base GW 20. The functions of the vehicle information collection section 26A, the vehicle information conversion section 26B, and the vehicle software rewriting section 26C of the base GW 20 can be implemented by the information control GW 10.

[0143] (2e) In addition to the data providing system 1 described above, the present disclosure can be implemented in various modes such as a device that configures a component of the data providing system 1, a program for making a computer function as the data providing system 1, a non-volatile tangible recording medium such as a semiconductor memory in which the program is recorded, and a data management method.

[0144] [3. Correspondence relationship between the configuration of the embodiment and the configuration of the present disclosure]

[0145] In the above-described embodiment, the information control GW 10 may correspond to a recording control device in the present disclosure. In the above-described embodiment, the base GW 20 may correspond to a partner device in the present disclosure. In the above-described embodiment, the server 60 may correspond to a provision target device in the present disclosure. In the above-described embodiment, the ROMs 14, 24, 34, 44, and 54 may correspond to a recording section in the present disclosure.

[0146] In the above-described embodiment, a function as the recording control section 17 of the information control GW 10 may correspond to a data acquisition section in the present disclosure. In the above-described embodiment, the vehicle information conversion section 26B of the base GW 20 or the information control GW 10 may correspond to a data output section in the present disclosure. In the above-described embodiment, the processings in S110, S140, S190, and S670 among the processings executed by the information control GW 10 may correspond to a data read-only storage section in the present disclosure. In the above-described embodiment, the processings in S120, S150, and S200 may correspond to a data provision section in the present disclosure.In the embodiment described above, the processings in S135, S185, and S260 may correspond to a condition changing section and a type changing section in the present disclosure.

[0147] In the above-described embodiment, the processing in S610 may correspond to an area confirmation section in the present disclosure. In the above-described embodiment, the processing in S620 may correspond to an address setting section in the present disclosure. In the above-described embodiment, the processing in S630 may correspond to a time transmission section in the present disclosure. In the above-described embodiment, the processing in S640 may correspond to a time setting section in the present disclosure.

Claims

[1] A recording control device (10) configured to control recording of a data item in one or more recording sections (14, 24, 34, 44, 54), the recording control device comprising: a data acquiring section (17) configured to acquire the data item having a plurality of types; a data read-only storage section (S110, S140, S190, S670) configured to store, in the one or more recording sections, the one or more data items that match a recording condition prepared in advance of the acquired data item having the plurality of types; a condition changing section (S135, S185, S260) configured to to define the recording condition as an old recording condition, and to specify that the data storage section uses a new recording condition instead of the old recording condition when the new recording condition different from the old condition is received from the outside; a time transmission section (S630) configured to transmit reference time information to a partner device (20), the partner device corresponding to a communication counterpart of the recording control device, and returning a response data item obtained by applying information to be transmitted by the partner device to the reference time information when the reference time information indicating a time managed by the recording control device is received; and a time setting section (S650) configured to to obtain the response data element, and to set a generation time of the response data element based on the reference time information of the response data element, where: the data storage section causes the data item to be recorded in association with the generation time of the response data item. [2] A recording control device according to claim 1, further comprising: a data providing section (S120, S150, S200) configured to provide the data item stored in the one or more recording sections to a provision target device (60) arranged outside the recording control device; and a type changing section (S135, S185, S260) configured to change at least one type of the data item provided by the data providing section when a plug and play is input. [3] A recording control device (10) configured to control recording of a data item in one or more recording sections (14, 24, 34, 44, 54), the recording control device comprising: a data acquiring section (17) configured to acquire the data item having a plurality of types; a data read-only storage section (S110, S140, S190, S670) configured to store, in the one or more recording sections, the one or more data items that match a recording condition prepared in advance of the acquired data item having the plurality of types; a condition changing section (S135, S185, S260) configured to define the recording condition as an old recording condition and to set the data storage section to use a new recording condition instead of the old recording condition when the new recording condition different from the old condition is received from the outside; a data providing section (S120, S150, S200) configured to provide the data item stored in the one or more recording sections to a provision target device (60) arranged outside the recording control device; and a type changing section (S135, S185, S260) configured to change at least one type of the data item provided by the data providing section when a plug and play is input. [4] A recording control device according to claim 2 or claim 3, wherein: the condition change section is configured to specify that the data storage section uses the new recording condition when the type change section changes the type of the data item provided by the data provision section. [5] A recording control device according to any one of claims 1 to 4, further comprising: a data output section (26B) configured to convert the data item stored in the one or more recording sections into a predetermined form according to a delivery destination of the data item, and output the converted data item to the data item's delivery destination. [6] A recording control device (10) configured to control recording of a data item in one or more recording sections (14, 24, 34, 44, 54), the recording control device comprising: a data acquiring section (17) configured to acquire the data item having a plurality of types; a data read-only storage section (S110, S140, S190, S670) configured to store, in the one or more recording sections, the one or more data items that match a recording condition prepared in advance of the acquired data item having the plurality of types; a condition changing section (S135, S185, S260) configured to define the recording condition as an old recording condition, and specify that the data storage section uses a new recording condition instead of the old recording condition when the new recording condition, which is different from the old condition, is received from the outside; and a data output section (26B) configured to convert the data item stored in the one or more recording sections into a predetermined form according to a delivery destination of the data item, and output the converted data item to the data item's delivery destination. [7] A recording control device according to any one of claims 1 to 6, further comprising: the one or more recording sections including a plurality of recording sections arranged at mutually different positions; an area confirmation section (S610) configured to confirm a free area in the plurality of recording sections, the free area indicating an area in which the data item can be recorded; and an address setting section (S620) configured to set an address indicating a position of the free area, where: the data storage section causes the data item to be recorded in the free area according to the address. [8] A recording control device according to claim 7, wherein: the area confirmation section is configured to to determine whether the data item can be recorded in a specific recording section corresponding to one of the plurality of recording sections, and to confirm the free capacity if the data item cannot be recorded in the specific recording section; and the data storage section is configured to to cause the specific recording section to record the data item if the data item can be recorded in the specific recording section, and to cause the data item to be recorded in the free area according to the address when the data item cannot be recorded in the specific recording section.

Images