WO2020016976A1 - Communication system, in-vehicle device, information acquisition method, and information acquisition program - Google Patents

Communication system, in-vehicle device, information acquisition method, and information acquisition program Download PDF

Info

Publication number
WO2020016976A1
WO2020016976A1 PCT/JP2018/027000 JP2018027000W WO2020016976A1 WO 2020016976 A1 WO2020016976 A1 WO 2020016976A1 JP 2018027000 W JP2018027000 W JP 2018027000W WO 2020016976 A1 WO2020016976 A1 WO 2020016976A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
vehicle
unit
request
calculation
Prior art date
Application number
PCT/JP2018/027000
Other languages
French (fr)
Japanese (ja)
Inventor
天龍 三沢
Original Assignee
三菱電機株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 三菱電機株式会社 filed Critical 三菱電機株式会社
Priority to PCT/JP2018/027000 priority Critical patent/WO2020016976A1/en
Publication of WO2020016976A1 publication Critical patent/WO2020016976A1/en

Links

Images

Classifications

    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60R—VEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
    • B60R16/00—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for
    • B60R16/02—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for electric constitutive elements
    • B60R16/023—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for electric constitutive elements for transmission of signals between vehicle parts or subsystems

Definitions

  • the present invention relates to a communication system, an in-vehicle device, an information acquisition method, and an information acquisition program.
  • Information about cars is used for various purposes.
  • the information can be obtained from a device mounted on the vehicle.
  • the information is also referred to as vehicle data.
  • a technique for converting vehicle data into a practical data format that can be used in an application has been proposed (see Patent Document 1).
  • the navigation device of Patent Literature 1 stores a conversion table for converting vehicle data into a practical data format.
  • the navigation device converts the vehicle data into a practical data format based on the conversion table.
  • An object of the present invention is to easily obtain vehicle calculation information.
  • the communication system includes a vehicle-mounted device having an information acquisition unit that acquires information about the vehicle and a vehicle communication device, an instruction to acquire the information about the vehicle, and vehicle calculation information that indicates information of a request target using the information about the vehicle. And support information for supporting calculation processing executed by the vehicle-mounted device when the vehicle-mounted device calculates the information.
  • the vehicle communication device receives the request information, acquires information about the vehicle from the information acquisition unit based on the acquisition instruction, and acquires the vehicle calculation information based on the information about the vehicle and the support information. And transmits the vehicle calculation information to the information processing device.
  • vehicle calculation information can be easily obtained.
  • FIG. 1 is a diagram illustrating a communication system according to a first embodiment.
  • FIG. 3 is a diagram illustrating a configuration of hardware included in the vehicle communication device according to the first embodiment.
  • FIG. 2 is a functional block diagram illustrating a configuration of the vehicle communication device according to the first embodiment.
  • FIG. 3 is a diagram illustrating a specific example of an application request according to the first embodiment;
  • FIG. 5 is a diagram illustrating an example of a unit conversion table according to the first embodiment.
  • FIG. 7 is a diagram illustrating an example of a calculation support table according to the first embodiment.
  • FIG. 5 is a diagram illustrating an example of a module management list according to the first embodiment.
  • FIG. 5 is a diagram illustrating an example of a call module management list according to the first embodiment.
  • FIG. 3 is a diagram illustrating an example of a format of a request packet according to the first embodiment.
  • FIG. 3 is a diagram illustrating an example of a format of an ECU packet according to the first embodiment.
  • 5 is a state chart (No. 1) of the vehicle communication device according to the first embodiment.
  • 6 is a state chart (part 2) of the vehicle communication device according to the first embodiment.
  • FIG. 4 is a diagram illustrating a specific example of a process executed between the cloud server and the in-vehicle device according to the first embodiment.
  • FIG. 7 is a functional block diagram illustrating a configuration of a vehicle communication device according to a second embodiment.
  • FIG. 14 is a diagram illustrating an example of a module management list according to the second embodiment.
  • FIG. 14 is a diagram illustrating an example of a call module management list according to the second embodiment.
  • 9 is a state chart (No. 1) of the vehicle communication device according to the second embodiment.
  • FIG. 13 is a functional block diagram illustrating a configuration of a vehicle communication device according to a third embodiment.
  • FIG. 14 is a diagram illustrating an example of a call module management list according to the third embodiment.
  • FIG. 14 is a functional block diagram illustrating a configuration of an in-vehicle device according to a fourth embodiment.
  • FIG. 1 is a diagram illustrating the communication system according to the first embodiment.
  • the communication system includes the cloud server 100 and the in-vehicle device 200.
  • the communication system may further include cloud servers 101 and 102.
  • the communication system can execute the information acquisition method.
  • the cloud servers 100 to 102 communicate with the in-vehicle device 200.
  • the cloud servers 100 to 102 may be considered as a plurality of gateways existing between the plurality of cloud servers and the vehicle-mounted device 200.
  • the cloud server or the gateway is also called an information processing device.
  • the cloud server 100 has a higher-level application 100a.
  • the cloud server 101 has a host application 101a.
  • the cloud server 102 has a host application 102a.
  • the cloud server 100 may include upper applications 101a and 102a. That is, one cloud server may have a plurality of higher-level applications.
  • the vehicle-mounted device 200 includes the vehicle communication device 300 and ECUs (Engine Control Units) 400, 401, 402, and 403.
  • the ECUs 400 to 403 may be a plurality of sensors.
  • the ECU or the sensor is also called an information acquisition unit.
  • the ECUs 400 to 403 obtain information on the vehicle.
  • the ECUs 400 to 403 obtain information on a car from a device (not shown) of the vehicle-mounted device 200.
  • the ECUs 400 to 403 may acquire information about the vehicle by calculating information about the vehicle based on various information.
  • the information on the car may be considered as information on the operation of the car.
  • Information about a vehicle is also referred to as ECU data or vehicle data.
  • the information on the vehicle is referred to as ECU data.
  • the cloud servers 100 to 102 transmit the application request to the in-vehicle device 200.
  • the application request is also called request information.
  • the application request includes an instruction to acquire ECU data.
  • the application request includes support information.
  • the support information is information for supporting the calculation process executed by the in-vehicle device 200 when the in-vehicle device 200 calculates the vehicle calculation information using the ECU data.
  • the vehicle calculation information indicates information of a request target. That is, the vehicle calculation information is information that is requested by the application request. Further, the vehicle calculation information may be expressed as information shaped into information that can be received by the upper-level applications 100a to 102a.
  • the vehicle communication device 300 receives the application request transmitted by the cloud servers 100 to 102.
  • the car communication device 300 receives the application request transmitted by the cloud server 100.
  • the vehicle communication device 300 acquires ECU data from the ECU based on the acquisition instruction.
  • the vehicle communication device 300 calculates vehicle calculation information based on the ECU data and the support information.
  • the vehicle communication device 300 transmits the vehicle calculation information to the cloud server 100.
  • the cloud servers 101 and 102 acquire vehicle calculation information. As described above, the cloud servers 100 to 102 can acquire the information requested by the application request.
  • the number of cloud servers in FIG. 1 is three. However, the number of cloud servers is not limited to three.
  • the number of ECUs in FIG. 1 is four. However, the number of ECUs is not limited to four.
  • FIG. 2 is a diagram illustrating a configuration of hardware included in the vehicle communication device according to the first embodiment.
  • the vehicle communication device 300 includes a processor 301, a volatile storage device 302, and a nonvolatile storage device 303.
  • the processor 301 controls the entire vehicle communication device 300.
  • the processor 301 is a CPU (Central Processing Unit) or an FPGA (Field Programmable Gate Array).
  • Processor 301 may be a multiprocessor.
  • the vehicle communication device 300 may be realized by a processing circuit, or may be realized by software, firmware, or a combination thereof. Note that the processing circuit may be a single circuit or a composite circuit.
  • the volatile storage device 302 is a main storage device of the vehicle communication device 300.
  • the volatile storage device 302 is a RAM (Random Access Memory).
  • the non-volatile storage device 303 is an auxiliary storage device of the vehicle communication device 300.
  • the nonvolatile storage device 303 is an SSD (Solid ⁇ State ⁇ Drive).
  • Each of the cloud servers 100 to 102 has a processor, a volatile storage device, and a nonvolatile storage device, similarly to the vehicle communication device 300.
  • the process executed between the cloud server 100 and the vehicle communication device 300 is the same as the process executed between the cloud server 101 and the vehicle communication device 300.
  • the processing executed between the cloud server 100 and the vehicle communication device 300 is the same as the processing executed between the cloud server 102 and the vehicle communication device 300. Therefore, hereinafter, processing executed between the cloud server 100 and the vehicle communication device 300 will be mainly described. The description of the processing executed between the cloud servers 101 and 102 and the vehicle communication device 300 is omitted.
  • FIG. 3 is a functional block diagram illustrating a configuration of the vehicle communication device according to the first embodiment.
  • the vehicle communication device 300 includes a communication unit 310, a request management unit 320, an ECU information management unit 330, a conversion unit 340, an unsteady change detection unit 350, a vehicle calculation information management unit 360, a storage unit 370, and a main processing unit 380. .
  • the request management unit 320 includes a request reception unit 321, a request analysis unit 322, a module management unit 323, and a request shaping transmission unit 324.
  • the ECU information management section 330 has an ECU information acquisition section 331 and an ECU information transmission section 332.
  • the conversion unit 340 has a data conversion unit 341.
  • the non-stationary change detection unit 350 includes a statistical analysis processing unit 351 and a registration unit 352.
  • the vehicle calculation information management unit 360 has a vehicle calculation information reception unit 361 and a vehicle calculation information transmission unit 362.
  • the storage unit 370 may be realized as a storage area secured in the volatile storage device 302 or the nonvolatile storage device 303.
  • One of the communication unit 310, the request management unit 320, the request reception unit 321, the request analysis unit 322, the module management unit 323, the request shaping transmission unit 324, the ECU information management unit 330, the ECU information acquisition unit 331, and the ECU information transmission unit 332 All or some of the units may be realized by the processor 301.
  • Conversion section 340, data conversion section 341, non-stationary change detection section 350, statistical analysis processing section 351, registration section 352, vehicle calculation information management section 360, vehicle calculation information reception section 361, vehicle calculation information transmission section 362, and main processing Part or all of the unit 380 may be realized by the processor 301.
  • Conversion section 340, data conversion section 341, non-stationary change detection section 350, statistical analysis processing section 351, registration section 352, vehicle calculation information management section 360, vehicle calculation information reception section 361, vehicle calculation information transmission section 362, and main processing Part or all of the unit 380 may be realized as a module of a program executed by the processor 301.
  • the request management unit 320, the request reception unit 321, the request analysis unit 322, the module management unit 323, the request shaping transmission unit 324, the ECU information management unit 330, the ECU information acquisition unit 331, and the ECU information transmission unit 332 include a processor 301. Will be described as a module of a program to be executed. Conversion section 340, data conversion section 341, non-stationary change detection section 350, statistical analysis processing section 351, registration section 352, vehicle calculation information management section 360, vehicle calculation information reception section 361, vehicle calculation information transmission section 362, and main processing The unit 380 will be described as a module of a program executed by the processor 301. These modules may be realized by middleware executed by the processor 301.
  • the cloud servers 100 to 102 or the higher-level applications 100a to 102a are higher-level devices or higher-level applications than the vehicle communication device 300. Therefore, the cloud servers 100 to 102 or the higher-level applications 100a to 102a may be expressed as higher-level function units.
  • the ECUs 400 to 403 are devices lower than the vehicle communication device 300. Therefore, the ECUs 400 to 403 may be expressed as lower functional units.
  • the upper application and the middleware may be expressed as an information acquisition program.
  • the communication unit 310 communicates with the cloud server 100.
  • the communication unit 310 receives the application request transmitted by the upper application 100a.
  • FIG. 4 is a diagram illustrating a specific example of the application request according to the first embodiment.
  • the application request 500 is information issued by the host application 100a.
  • the application request 500 includes an application request file 501, a unit conversion table 502, and a calculation support table 503.
  • the application request file 501 may be given a file name “upper application # 1.ini”.
  • the application request file 501 is divided into a plurality of sections.
  • the plurality of sections include a function section, a data content definition section, and a data conversion definition section.
  • the function section is a section whose name is defined in advance.
  • the data content definition section is a section in which an arbitrary name can be defined.
  • the data conversion definition section is a section for defining data format shaping rules.
  • the application request file 501 includes an interface information section “[_INTERFACE_]”.
  • the interface information section includes an application name, an application ID (identifier), an operation instruction, an interface type, a CAN (Controller Area Network) system number, a filtering CAN ID, a notification cycle, and a non-stationary change detection.
  • the name of the application that issued the application request 500 (for example, the name of the higher-level application 100a) is registered in the application name.
  • the application ID information for identifying the application that issued the application request 500 is registered.
  • the operation instruction an operation instruction to the ECU information management unit 330 is registered. For example, an acquisition instruction for ECU data is registered in the ECU information management unit 330 as the operation instruction.
  • an interface for acquiring data from the ECU is registered.
  • “0” (library), “1” (memory), “2” (CAN), or “3” (Ethernet) is registered as the interface type.
  • Information indicating a CAN system is registered in the CAN system number.
  • “0” or “1” is registered as the CAN system number.
  • the filtering CAN ID a message ID of the data filtering CAN is registered.
  • “h730” and “h731” are registered as the filtering CAN ID.
  • the time for notifying the cloud server (that is, the host application) of the vehicle calculation information is registered. For example, 10000 [msec] (that is, 10 seconds) is registered in the notification cycle.
  • the notification cycle may be considered as a cycle for acquiring information from the ECU. That is, the notification cycle may be considered as a cycle of acquiring ECU data from the ECU.
  • ⁇ In the unsteady change detection, information indicating whether or not the vehicle communication device 300 performs the statistical analysis process is registered. For example, in the detection of the unsteady change, "0" (invalid), “1” (direct value), “2” (time differential value), "3” (average value), “4" (average deviation value), Alternatively, “5” (standard deviation value) is registered. If a value other than “0” is registered in the unsteady change detection, the application request 500 indicates that the issuing upper application has instructed the statistical analysis command.
  • the statistical analysis command may be considered as a statistical analysis command for ECU data. Further, the statistical analysis command may be considered as a statistical analysis command of the vehicle calculation information.
  • the application request file 501 includes “[_STRUCTURE_]” which is a higher-level provided data structure definition section.
  • the higher-level data structure definition section defines the data structure of data to be passed to the higher-level application. That is, the higher-level provided data structure definition section may be considered to indicate the information to be requested. Therefore, it may be considered that the vehicle registration information to be calculated by the in-vehicle device 200 is registered in the information registered in the higher-level provided data structure definition section.
  • ecu1.ownVelocity ecu3.relativeVelocity
  • ecu3.1tripDistance ecu3.1tripTime
  • absltVelocity ecu3.1tripTime
  • absltVelocity ecu3.1tripTime
  • absltVelocity ecu3.1tripTime
  • absltVelocity ecu3.1tripTime
  • absltVelocity ecu3.1tripTime
  • the application request file 501 includes a data conversion definition section “[_DATA_SPEC_]”.
  • the data conversion definition section information indicating which ECU data is acquired is registered. That is, an instruction to acquire ECU data is registered in the data conversion definition section.
  • the ECU from which to obtain the information is registered in the higher-level data structure definition section.
  • ecu1.ownVelocity registered in the higher-level provided data structure definition section means that ownVelocity is acquired from the ECU 400.
  • the information registered in the higher-level provided data structure definition section may be considered as an ECU data acquisition instruction.
  • a unit specified by the cloud server 100 or the higher-level application 100a is registered.
  • the application request 500 includes information indicating that the vehicle-mounted device 200 calculates the vehicle calculation information in a predetermined unit.
  • the declaration and definition of variables are registered in the application request file 501.
  • the application request 500 includes the unit conversion table 502 and the calculation support table 503.
  • the generic name of the unit conversion table 502 and the calculation support table 503 is also called support information.
  • Information calculated using at least one of the unit conversion table 502 and the calculation support table 503 is the vehicle calculation information.
  • FIG. 5 is a diagram illustrating an example of a unit conversion table according to the first embodiment.
  • the unit conversion table 502 is also called unit conversion information.
  • the unit conversion table 502 is information for converting a unit.
  • the data conversion unit 341 can calculate the vehicle calculation information in which the unit of the ECU data is converted into a predetermined unit based on the ECU data and the unit conversion table 502.
  • the unit conversion table 502 has an item of speed.
  • the data conversion unit 341 can convert the unit of the ECU data from “km / h” to “m / s” using the unit conversion table 502.
  • FIG. 5 illustrates a case where the unit conversion table 502 has items of “velocity”, “latitude / longitude”, “altitude”, and “angle”.
  • the unit conversion table 502 may include items other than the items illustrated in FIG.
  • FIG. 6 is a diagram illustrating an example of the calculation support table according to the first embodiment.
  • FIG. 4 shows that the upper-level application 100a requests the absolute speed (that is, absltVelocity of [_STRUCTURE_]).
  • the ECU data that can be obtained from the ECUs 400 to 403 does not include the absolute speed.
  • the calculation support table 503 is used.
  • the calculation support table 503 is also referred to as calculation support information.
  • the calculation support table 503 is information for supporting the calculation process executed by the in-vehicle device 200 when the in-vehicle device 200 calculates the vehicle calculation information using the plurality of ECU data.
  • the calculation support table 503 has an item of “absolute speed”.
  • the data conversion unit 341 may acquire ECU data indicating the vehicle speed from the ECU 400.
  • the data conversion unit 341 may acquire ECU data indicating the relative speed from the ECU 402.
  • the data conversion unit 341 calculates the absolute speed based on the calculation support table 503, the own vehicle speed, and the relative speed.
  • the calculation support table 503 has an item of “1 trip average speed”.
  • the data conversion unit 341 may acquire ECU data indicating one trip traveling distance and ECU data indicating one trip traveling time.
  • the data conversion unit 341 calculates the one-trip average speed based on the calculation support table 503, the one-trip travel distance, and the one-trip travel time.
  • the data conversion unit 341 acquires a plurality of ECU data from at least one or more ECUs. Then, the data conversion unit 341 calculates the vehicle calculation information based on the plurality of ECU data and the calculation support table 503.
  • FIG. 6 illustrates a case where the calculation support table 503 has items of “absolute speed”, “1 trip average speed”, and “cumulative distance”.
  • the calculation support table 503 may include items other than the items illustrated in FIG.
  • FIG. 4 illustrates a case where the application request 500 includes a unit conversion table 502 and a calculation support table 503.
  • the application request 500 may include only one of the unit conversion table 502 and the calculation support table 503.
  • the request receiving unit 321 receives the application request 500 from the communication unit 310.
  • the request analysis unit 322 analyzes the application request 500. More specifically, the request analysis unit 322 detects a request from the upper-level application 100a from the application request file 501. For example, the request analysis unit 322 detects that the host application 100a has instructed a statistical analysis command.
  • the request analysis unit 322 transmits the analysis result to the module management unit 323.
  • the module management unit 323 specifies a module to be loaded based on the analysis result and the calling module management list. Modules to be loaded are managed in a module management list.
  • FIG. 7 is a diagram illustrating an example of a module management list according to the first embodiment.
  • the module management list 371 is stored in the storage unit 370.
  • the module management list 371 has items of a major item module name, a major item module ID, a detailed module name, and a module ID.
  • the major item module name indicates the generic name of the detailed module.
  • the large item module ID indicates an ID corresponding to the large item module.
  • the ID of a module that is always loaded is assigned an uppercase alphanumeric character. The number is 1.
  • the ID of the request management unit 320 is A1.
  • Uppercase letters and numbers are assigned to the IDs of the modules that are loaded as required.
  • the number is 2.
  • the ID of the unsteady change detection unit 350 is C2.
  • the item of the detailed module name indicates the name of a module included in the major item module.
  • the item of the module ID indicates an ID corresponding to the detailed module.
  • an uppercase alphabetic character is arranged between the uppercase alphabetic character and the numeral of the ID of the large item module.
  • the ID of the request receiving unit 321 is AA1.
  • a lowercase alphabetic character is arranged between the uppercase alphabetic character and the numeral of the ID of the large item module.
  • the ID of the statistical analysis processing unit 351 is Ca2.
  • the module management unit 323 specifies a module to be loaded based on the analysis result and the calling module management list.
  • FIG. 8 is a diagram illustrating an example of a call module management list according to the first embodiment.
  • the calling module management list 372 is stored in the storage unit 370.
  • the calling module management list 372 has an application request type, a calling module ID, and a calling module name.
  • the item of the application request type indicates a condition for calling a module.
  • the item of the calling module ID indicates a module ID.
  • the item of the calling module name indicates the name of the module. For example, when the analysis result indicates that a value other than “0” is registered in “detectType” of the application request file 501, the module management unit 323 determines the non-stationary state of the load target based on the calling module management list 372.
  • the change detection unit 350 is specified.
  • the module management unit 323 loads the specified load target module. For example, the module management unit 323 loads the unsteady change detection unit 350. However, the module management unit 323 may load the load target module at any timing.
  • the module management unit 323 generates a request packet.
  • FIG. 9 is a diagram illustrating an example of a format of a request packet according to the first embodiment.
  • Request packet 600 includes an STX, a header, a payload, and an ETX.
  • STX indicates the beginning of the request packet 600.
  • the header indicates the order in which the modules will be executed. For example, AC1 and AD1 are registered in the header. This indicates that the request shaping transmission unit 324 is executed after the module management unit 323.
  • the application request 500 is registered in the payload.
  • ETX indicates the end of request packet 600.
  • the module management unit 323 transmits the request packet 600 to the next module according to the header of the request packet 600. Returning to FIG.
  • the request shaping transmission unit 324 acquires only the payload from the request packet 600. That is, the request shaping transmission unit 324 acquires the application request 500 from the request packet 600.
  • the request shaping transmission unit 324 transmits the application request 500 to the ECU information acquisition unit 331.
  • the ECU information acquisition unit 331 refers to [_STRUCTURE_] of the application request 500 and specifies what data is acquired from which ECU. For example, the ECU information acquisition unit 331 specifies to acquire ownVelocity from the ECU 400 based on ecu1.ownVelocity.
  • the ECU information acquisition unit 331 acquires information from the ECU. Note that the ECU information acquisition unit 331 acquires information from the ECU based on the notification cycle of the application request file 501.
  • the ECU information obtaining unit 331 converts information obtained from the ECU into ECU data based on the data conversion definition section of the application request file 501. For example, the ECU information acquisition unit 331 acquires 1 byte from the rear of the 2 bytes from the beginning of the information acquired from the ECU 400. Thereby, the ECU information acquisition unit 331 can acquire ownVelocity.
  • the ECU information obtaining unit 331 obtains a unit from information obtained from the ECU. For example, the ECU information acquisition unit 331 acquires a unit (for example, [km / h]) from the ECU 400. Then, the ECU information acquisition unit 331 associates the information acquired by the above processing with the unit. For example, the ECU information acquisition unit 331 associates ownVelocity with [km / h]. Thus, the information associated by the ECU information acquisition unit 331 is ECU data. For example, information in which ownVelocity is associated with [km / h] is ECU data. Further, for example, information in which the relative velocity and [m / s] are associated with each other is also ECU data.
  • the ECU information acquisition unit 331 can acquire ECU data from the ECU.
  • the ECU information acquisition unit 331 transmits the ECU data to the ECU information transmission unit 332.
  • the ECU information transmission unit 332 transmits the ECU data to the module management unit 323.
  • the module management unit 323 determines whether to load the conversion unit 340 based on the application request 500, the ECU data, and the calling module management list 372. For example, the module management unit 323 specifies that the unit specified by the host application 100a is different from the unit of ECU data.
  • the module management unit 323 determines to load the conversion unit 340 based on the calling module management list 372. When determining that the conversion unit 340 is to be loaded, the module management unit 323 loads the conversion unit 340. However, the module management unit 323 may load the conversion unit 340 at any timing.
  • the module management unit 323 transmits information on whether to load the conversion unit 340 and the unsteady change detection unit 350 to the ECU information transmission unit 332.
  • the ECU information transmission unit 332 generates an ECU packet based on the information.
  • FIG. 10 is a diagram illustrating an example of a format of an ECU packet according to the first embodiment.
  • the ECU packet 601 includes an STX, a header, a payload, and ETX.
  • STX indicates the start of the ECU packet 601.
  • the ECU information transmission unit 332 generates a header based on information on whether to load the conversion unit 340 and the unsteady change detection unit 350.
  • the header indicates the order in which the modules will be executed. For example, BB1, Ba2, Ca2, Cb2, and CA1 are registered in the header. This indicates that the processing is executed in the order of the ECU information transmission unit 332, the data conversion unit 341, the statistical analysis processing unit 351, the registration unit 352, and the vehicle calculation information reception unit 361.
  • the ECU data and the application request 500 are registered.
  • ETX indicates the end of the ECU packet 601.
  • the ECU information transmission unit 332 transmits the ECU packet 601 to the next module according to the header of the ECU packet 601. Returning to FIG.
  • the data conversion unit 341 converts the unit using the unit conversion table 502. Further, the data conversion unit 341 may express that the unit is converted using the unit conversion table 502. Since the converted or converted information is information calculated based on the ECU data and the unit conversion table 502, it is vehicle calculation information.
  • the data conversion unit 341 calculates the information requested by the application request 500 based on the calculation support table 503 and the ECU data.
  • the calculated information is vehicle calculation information because it is information calculated based on the calculation support table 503 and the ECU data.
  • the statistical analysis processing unit 351 performs a statistical analysis.
  • the registration unit 352 registers the analysis result in the payload of the ECU packet 601.
  • the vehicle calculation information receiving unit 361 receives the ECU packet 601.
  • the vehicle calculation information receiving unit 361 acquires payload information from the ECU packet 601. For example, the vehicle calculation information receiving unit 361 acquires vehicle calculation information and ECU data from the ECU packet 601.
  • the vehicle calculation information transmitting unit 362 transmits the information of the payload to the upper application 100a via the communication unit 310. Thereby, the host application 100a can acquire the information requested by the application request 500.
  • the main processing unit 380 can call the request management unit 320, the ECU information management unit 330, and the vehicle calculation information management unit 360.
  • the main processing unit 380 can also instruct the request management unit 320, the ECU information management unit 330, and the vehicle calculation information management unit 360.
  • a process executed by the vehicle communication device 300 will be described using a state chart.
  • FIG. 11 is a state chart (No. 1) of the vehicle communication device according to the first embodiment.
  • the communication unit 310 receives the application request transmitted by the upper application 100a.
  • the request receiving unit 321 receives the application request 500 from the communication unit 310.
  • Step S12 The request analysis unit 322 analyzes the application request 500.
  • the request analysis unit 322 transmits the analysis result to the module management unit 323.
  • the module management unit 323 specifies a module to be loaded based on the analysis result and the calling module management list.
  • the module management unit 323 generates the request packet 600.
  • the module management unit 323 transmits the request packet 600 to the next module according to the header of the request packet 600.
  • the request shaping transmission unit 324 acquires the application request 500 from the request packet 600.
  • the request shaping transmission unit 324 transmits the application request 500 to the ECU information acquisition unit 331.
  • the ECU information acquisition unit 331 can acquire the ECU data based on the application request 500.
  • FIG. 11 illustrates a case where the ECU 400 transmits information.
  • Step S15 The ECU information acquisition unit 331 acquires ECU data.
  • the method for acquiring the ECU data is as described above.
  • the ECU information acquisition unit 331 transmits the ECU data to the ECU information transmission unit 332.
  • the ECU information transmission unit 332 transmits the ECU data to the module management unit 323.
  • Step S16 The module management unit 323 determines whether to load the conversion unit 340 based on the ECU data and the calling module management list 372.
  • the module management unit 323 transmits information on whether to load the conversion unit 340 and the unsteady change detection unit 350 to the ECU information transmission unit 332.
  • the ECU information transmission unit 332 generates an ECU packet 601.
  • FIG. 12 is a state chart (2) of the vehicle communication device according to the first embodiment. (Step S21) If the module management unit 323 determines that the conversion unit 340 is to be loaded based on the determination result of step S16, it executes step S22. When the module management unit 323 determines that the conversion unit 340 is not loaded based on the determination result of step S16, the module management unit 323 executes step S24.
  • the module management unit 323 loads the conversion unit 340.
  • the data conversion unit 341 included in the conversion unit 340 acquires the application request 500 and the ECU data included in the ECU packet 601.
  • the data conversion unit 341 converts the unit using the unit conversion table 502.
  • the data conversion unit 341 converts the unit of ownVelocity included in the ECU packet 601 from "km / h" to "m / s". More specifically, the data conversion unit 341 calculates ownVelocity in units of “m / s” using the value indicated by ownVelocity and “1000/3600”.
  • the data conversion unit 341 registers the calculated information (that is, vehicle calculation information) in the payload of the ECU packet 601.
  • the data conversion unit 341 calculates the information based on the calculation support table 503 and the ECU data. For example, it is assumed that the information requested by the application request 500 is a 1-trip average speed. Then, it is assumed that the 1-trip average speed is not registered in the payload. It is also assumed that the ECU data is one trip traveling distance and one trip traveling time. The data conversion unit 341 calculates the one-trip average speed based on the calculation support table 503, the one-trip travel distance, and the one-trip travel time. The data conversion unit 341 registers the calculated information (that is, vehicle calculation information) in the payload of the ECU packet 601. Further, the data conversion unit 341 may use both the unit conversion table 502 and the calculation support table 503 based on the information requested by the application request 500.
  • Step S24 When there is a statistical analysis command in the application request 500, the module management unit 323 executes step S25. If there is no statistical analysis command in the application request 500, step S28 is executed. (Step S25) The module management unit 323 loads the unsteady change detection unit 350.
  • the statistical analysis processing unit 351 of the unsteady change detection unit 350 performs a statistical analysis. This will be described in detail.
  • the statistical analysis processing unit 351 analyzes whether or not the ECU data acquired this time is an abnormal value based on the past history of the ECU data. For example, when “detectType” is set to 3, the statistical analysis processing unit 351 calculates an average value based on a past history of ECU data (for example, relative speed). When the ECU data acquired this time is larger than the average value, the statistical analysis processing unit 351 may analyze the ECU data acquired this time as an abnormal value.
  • the statistical analysis processing unit 351 analyzes whether or not the vehicle calculation information calculated in step S23 is an abnormal value based on the past history of the vehicle calculation information. For example, when “detectType” is set to 3, the statistical analysis processing unit 351 calculates an average value based on the past history of the own vehicle speed (unit: m / s). When the own vehicle speed calculated in step S23 is larger than the average value, the statistical analysis processing unit 351 may analyze the own vehicle speed calculated in step S23 as an abnormal value. Further, for example, when “detectType” is set to 3, the statistical analysis processing unit 351 calculates an average value based on the past history of one trip average speed. If the average one-trip speed calculated in step S23 is larger than the average value, the statistical analysis processing unit 351 may analyze the average one-trip speed calculated in step S23 as an abnormal value.
  • the statistical analysis processing unit 351 performs time differentiation. If the time differential value exceeds a predetermined threshold, the statistical analysis processing unit 351 may determine that the value is an abnormal value.
  • Step S27 The registration unit 352 of the unsteady change detection unit 350 registers the analysis result in the payload of the ECU packet 601.
  • Step S28 The vehicle calculation information receiving unit 361 receives the ECU packet 601.
  • the vehicle calculation information receiving unit 361 acquires payload information from the ECU packet 601. When the vehicle calculation information is registered in the payload, the vehicle calculation information receiving unit 361 can acquire the vehicle calculation information.
  • Step S29 The vehicle calculation information transmitting unit 362 transmits the information of the payload to the upper application 100a via the communication unit 310.
  • the vehicle calculation information transmitting unit 362 can transmit the vehicle calculation information.
  • the analysis result is registered in the payload, the vehicle calculation information transmitting unit 362 can transmit the analysis result.
  • the host application 100a can acquire the information requested by the application request 500.
  • the host application 100a can acquire the ECU data requested by the application request 500.
  • the host application 100a can acquire the vehicle calculation information requested by the application request 500.
  • the module management unit 323 may determine in step S16 whether to load the unsteady change detection unit 350.
  • FIG. 13 is a diagram illustrating a specific example of a process executed between the cloud server and the in-vehicle device according to the first embodiment.
  • the cloud server 100 or the host application 100a transmits the application request 500 to the in-vehicle device 200 (Step S101).
  • the application request 500 includes a unit conversion table 502 and a calculation support table 503.
  • the application request 500 includes ownVelocity.
  • the unit of ownVelocity is "m / s".
  • the application request 500 includes absltVelocity.
  • the application request 500 also includes information indicating that ownVelocity is to be obtained from the ECU 400 (ie, ecu1).
  • the application request 500 includes information indicating that relativeVelocity, 1tripDistance, and 1tripTime are to be obtained from the ECU 402 (ie, ecu3).
  • FIG. 13 omits ecu1 and ecu3.
  • the vehicle communication device 300 acquires ownVelocity from the ECU 400.
  • the unit of the own Velocity is “km / h”.
  • the vehicle communication device 300 acquires from the ECU 402 the relative Velocity, 1 trip Distance, and 1 trip Time.
  • the unit of ownVelocity specified by the application request 500 is “m / s”.
  • the unit of ownVelocity acquired from the ECU 400 is “km / h”. Therefore, the vehicle communication device 300 uses the unit conversion table 502 to convert the unit of ownVelocity acquired from the ECU 400 from “km / h” to “m / s”.
  • the ECU data acquired from the ECUs 400 and 402 does not include absltVelocity and avrgVelocity. Therefore, the vehicle communication device 300 uses the calculation support table 503 to calculate absltVelocity and avrgVelocity.
  • the unit of the calculated absltVelocity and avrgVelocity is “m / s”.
  • the unit of absltVelocity and avrgVelocity specified by the application request 500 is “km / h”. Therefore, the vehicle communication device 300 uses the unit conversion table 502 to convert the calculated unit of the absltVelocity from “m / s” to “km / h”.
  • the vehicle communication device 300 uses the unit conversion table 502 to convert the unit of the calculated avrgVelocity from “m / s” to “km / h”. As described above, the vehicle communication device 300 can calculate vehicle calculation information in a predetermined unit based on the plurality of ECU data, the unit conversion table 502, and the calculation support table 503.
  • the vehicle communication device 300 transmits the information 700 to the cloud server 100 or the upper application 100a (Step S102).
  • the information 700 includes ECU data (for example, relative velocity) acquired from the ECUs 400 and 402.
  • the information 700 includes vehicle calculation information.
  • the vehicle calculation information is ownVelocity (unit: m / s), absltVelocity (unit: km / h), and avrgVelocity (unit: km / h).
  • the vehicle communication device 300 receives the application request 500 including the unit conversion table 502 and the calculation support table 503.
  • the vehicle communication device 300 can convert the unit of the ECU data by including the unit conversion table 502 in the application request 500.
  • the vehicle communication device 300 can generate new data by including the calculation support table 503 in the application request 500.
  • the vehicle communication device 300 since the application request 500 includes at least one of the unit conversion table 502 and the calculation support table 503, the vehicle communication device 300 does not store a conversion table for converting various types of ECU data. You may. Since the vehicle communication device 300 does not need to store the conversion table, it is not necessary to create the conversion table by complicated processing.
  • the cloud server 100 or the higher-level application 100a may include at least one of the unit conversion table 502 and the calculation support table 503 in the application request 500 in accordance with the information to be acquired. Therefore, the communication system does not create the conversion table and only needs to include at least one of the unit conversion table 502 and the calculation support table 503 in the application request 500, so that the vehicle calculation information can be easily obtained.
  • the cloud server 100 or the higher-level application 100a can obtain a result of statistically analyzing ECU data by transmitting a statistical analysis command of ECU data to the vehicle communication device 300.
  • the cloud server 100 or the upper application 100a can obtain an analysis result obtained by statistically analyzing the vehicle calculation information by transmitting a statistical analysis command of the vehicle calculation information to the vehicle communication device 300.
  • the vehicle communication device 300 promptly does not follow the notification cycle included in the application request 500.
  • the analysis result may be transmitted to the cloud server 100 or the host application 100a.
  • Embodiment 2 FIG. Next, a second embodiment will be described. Items that are different from the first embodiment will be mainly described, and descriptions of items that are common to the first embodiment will be omitted. Embodiment 2 refers to FIGS. 1 to 6 and 9 to 12. Embodiment 1 has described the case where the vehicle communication device 300 receives one application request. Embodiment 2 describes a case where vehicle communication device 300 receives a plurality of application requests.
  • FIG. 14 is a functional block diagram showing the configuration of the vehicle communication device according to the second embodiment.
  • the vehicle communication device 300a includes a request aggregation unit 390.
  • the request aggregating unit 390 includes a common data analyzing unit 391 and a notification cycle analyzing unit 392.
  • Part or all of the request aggregation unit 390, the common data analysis unit 391, and the notification cycle analysis unit 392 may be realized by the processor 301. Part or all of the request aggregation unit 390, the common data analysis unit 391, and the notification cycle analysis unit 392 may be realized as a module of a program executed by the processor 301.
  • the request aggregation section 390, the common data analysis section 391, and the notification cycle analysis section 392 will be described as modules of a program executed by the processor 301. These modules may be realized by middleware executed by the processor 301. 14 which are the same as or correspond to those shown in FIG. 3 are denoted by the same reference numerals as those shown in FIG. FIG. 14 omits the main processing unit 380. The functions of the common data analysis unit 391 and the notification cycle analysis unit 392 will be described later in detail.
  • FIG. 15 is a diagram illustrating an example of a module management list according to the second embodiment.
  • the module management list 371a is stored in the storage unit 370.
  • the module management list 371a registers that the large item module ID of the request aggregating unit 390 is A2.
  • the module management list 371a registers that the module ID of the common data analysis unit 391 is Aa2.
  • the module ID of the notification cycle analysis unit 392 is registered as Ab2 in the module management list 371a.
  • FIG. 16 is a diagram illustrating an example of a call module management list according to the second embodiment.
  • the calling module management list 372a is stored in the storage unit 370.
  • a condition for calling the request aggregating unit 390 is registered in the calling module management list 372a.
  • FIG. 17 is a state chart (1) of the vehicle communication device according to the second embodiment.
  • FIG. 17 differs from FIG. 11 in that steps S11a, 12a to 12e, 13a, and 14a are executed. Therefore, in FIG. 17, steps S11a, 12a to 12e, 13a, and 14a will be described. The other steps in FIG. 17 are given the same numbers as the step numbers in FIG. 11, and the description of the processing is omitted. After FIG. 17, the processing in FIG. 12 is executed.
  • the communication unit 310 receives a plurality of application requests. For example, the communication unit 310 receives a plurality of application requests transmitted by a plurality of higher-level applications simultaneously. In addition, for example, the communication unit 310 waits for a predetermined time after receiving an application request transmitted by one higher-level application. The communication unit 310 receives another application request within a predetermined time. The case where the communication unit 310 receives a plurality of application requests is not limited to the above example.
  • the request receiving unit 321 receives a plurality of application requests from the communication unit 310.
  • FIG. 17 illustrates a case where the upper application 100a transmits an application request.
  • Step S12a The request analysis unit 322 analyzes a plurality of application requests. For example, the request analysis unit 322 detects that the application request transmitted by the higher-level application 100a requests ownVelocity. Further, the request analysis unit 322 detects that the application request transmitted by the upper-level application 102a requests ownVelocity. The request analysis unit 322 detects that a plurality of application requests request common data.
  • the request analysis unit 322 analyzes whether a plurality of application requests request common data.
  • the request analysis unit 322 transmits the analysis result to the module management unit 323.
  • Step S12b If the analysis result indicates that common data is requested, the module management unit 323 executes Step S12c. When the analysis result indicates that the common data is not requested, the module management unit 323 generates the request packet 600.
  • the payload of the request packet 600 includes a plurality of application requests.
  • Step S12c The module management unit 323 loads the request aggregation unit 390 based on the calling module management list 372a.
  • the module management unit 323 generates the request packet 600.
  • AC1, Aa2, Ab2, and AD1 are registered in the header of the request packet 600. This indicates that after the module management unit 323, the common data analysis unit 391, the notification cycle analysis unit 392, and the request shaping transmission unit 324 are executed.
  • the payload of the request packet 600 includes a plurality of application requests.
  • the module management unit 323 transmits the request packet 600 to the next module according to the header of the request packet 600.
  • the common data analysis unit 391 refers to the payload of the request packet 600 and detects common data requested by each of the plurality of application requests.
  • common data is ownVelocity.
  • the notification cycle analyzer 392 calculates the greatest common divisor of the notification cycle based on the notification cycle included in each of the plurality of application requests. For example, the notification cycle included in the application request transmitted by the higher-level application 100a is 5000 [msec] (that is, 5 seconds). The notification cycle included in the application request transmitted by the upper application 102a is 10,000 [msec] (that is, 10 seconds). The notification cycle analysis unit 392 calculates 5 seconds, which is the greatest common divisor, based on 5 seconds and 10 seconds. The notification cycle analyzer 392 stores the greatest common divisor in the payload of the request packet 600.
  • Step S13a The request shaping / transmission unit 324 acquires payload information from the request packet 600. For example, the request shaping transmission unit 324 acquires a plurality of application requests. When the payload includes the greatest common divisor, the request shaping transmission unit 324 acquires the greatest common divisor.
  • Step S14a The request shaping transmission unit 324 transmits the information of the payload to the ECU information acquisition unit 331. Thereby, the ECU information acquisition unit 331 can acquire ECU data based on a plurality of application requests.
  • FIG. 17 illustrates a case where the ECU 400 transmits information.
  • the ECU information acquisition unit 331 acquires common data required by a plurality of application requests from the ECU based on the greatest common divisor. For example, the greatest common divisor is set to 5 seconds. OwnVelocity of common data.
  • the ECU that stores ownVelocity is assumed to be ECU 400.
  • the ECU information obtaining unit 331 obtains ownVelocity from the ECU 400 in a 5-second cycle.
  • the ECU information transmission unit 332 generates an ECU packet in step S16.
  • the ECU information transmission unit 332 generates an ECU packet for each of the plurality of application requests. For example, the ECU information transmission unit 332 generates an ECU packet including the application request transmitted by the upper application 100a and an ECU packet including the application request transmitted by the higher application 102a. Further, the ECU information transmission unit 332 may generate an ECU packet based on the notification cycle included in the application request. For example, 5 seconds are registered in the application request transmitted by the upper application 100a. Therefore, the ECU information transmission unit 332 generates the ECU packet so that the information of the payload of the ECU packet can be transmitted to the upper application 100a at a cycle of 5 seconds.
  • the ECU information transmission unit 332 generates the ECU packet so that the information of the payload of the ECU packet can be transmitted to the upper application 102a at a cycle of 10 seconds.
  • the vehicle communication device 300a executes steps S21 to S29 for each of the plurality of ECU packets. For example, the vehicle communication device 300a executes steps S21 to S29 on the ECU packet including the application request transmitted by the upper application 100a. Further, for example, the vehicle communication device 300a executes steps S21 to S29 on the ECU packet including the application request transmitted by the upper application 102a.
  • the vehicle communication device 300a receives a plurality of application requests.
  • the vehicle communication device 300a determines the greatest common divisor based on the notification cycle included in each of the plurality of application requests. Is calculated.
  • the vehicle communication device 300a acquires common ECU data based on the greatest common divisor.
  • the ECU information acquisition unit 331 acquires ownVelocity in a 5-second cycle.
  • the ECU information acquisition unit 331 executes a process of acquiring ownVelocity in a 5-second cycle based on the application request transmitted by the upper application 100a.
  • the ECU information acquisition unit 331 executes a process of acquiring ownVelocity at a cycle of 10 seconds based on the application request transmitted by the upper application 102a.
  • acquiring ownVelocity for each application request increases the load on the vehicle communication device 300a. Therefore, the vehicle communication device 300a acquires common data based on the greatest common divisor of the notification cycle. Thereby, the vehicle communication device 300a can reduce the number of times of acquiring the ECU data (for example, ownVelocity). Therefore, the vehicle communication device 300a can reduce the load.
  • Embodiment 3 FIG. Next, a third embodiment will be described. Items that are different from the first and second embodiments will be mainly described, and descriptions of items that are common to the first and second embodiments will be omitted. Embodiment 3 refers to FIGS. 1 to 6, 9 to 12, and 14 to 17.
  • the module to be loaded by the vehicle communication device is specified, and the specified module is loaded.
  • the module to be loaded by the vehicle communication device is specified, and the module is loaded in advance.
  • FIG. 18 is a functional block diagram illustrating a configuration of the vehicle communication device according to the third embodiment.
  • the vehicle communication device 300b has a request management unit 320b.
  • the request management unit 320b has a request analysis unit 322b and a module management unit 323b.
  • the configurations in FIG. 18 that are the same as or correspond to the configurations illustrated in FIGS. 3 and 14 are denoted by the same reference numerals as those illustrated in FIGS. In FIG. 18, the main processing unit 380 is omitted.
  • the module management unit 323b investigates what kind of application request is transmitted before the cloud server 100 to 102 or the higher-level application 100a to 102a transmits the application request. Therefore, the module management unit 323b transmits a disclosure instruction to the cloud servers 100 to 102 or the higher-level applications 100a to 102a. Further, the module management unit 323b may transmit the disclosure instruction by broadcast or multicast.
  • Each of the cloud servers 100 to 102 or the higher-level applications 100a to 102a transmits an application request file to be included in the application request to the vehicle communication device 300b.
  • the request analysis unit 322b analyzes each application request file.
  • the request analysis unit 322b transmits the analysis result to the module management unit 323b. For example, acquisition of common data from the ECU is registered in the analysis result. Also, for example, it is registered in the analysis result that “1” is specified in “detectType”.
  • the module management unit 323b specifies the module to be loaded based on the analysis result and the calling module management list 372a. For example, the module management unit 323b specifies the request aggregating unit 390 because acquiring the common data from the ECU is registered in the analysis result. The module management unit 323b specifies the non-stationary change detection unit 350 because “1” is designated as “detectType” in the analysis result. The module management unit 323b loads the request aggregation unit 390 and the unsteady change detection unit 350.
  • FIG. 18 illustrates a state in which the request aggregation unit 390 and the unsteady change detection unit 350 are loaded.
  • the module management unit 323b may create a call module management list for specifying a module to be loaded based on the analysis result.
  • the calling module management list will be described.
  • FIG. 19 is a diagram illustrating an example of a call module management list according to the third embodiment.
  • the calling module management list 372b is stored in the storage unit 370. For example, conditions for calling the request aggregating unit 390 and the unsteady change detecting unit 350 are registered in the calling module management list 372b.
  • the module management unit 323b may load a module based on the calling module management list 372b.
  • the vehicle communication device 300b may notify the cloud servers 100 to 102 or the higher-level applications 100a to 102a that the application request can be transmitted.
  • the vehicle communication device 300b acquires, from the cloud server, information that can specify a module that processes the application request (that is, the application request file). Before receiving the application request, the vehicle communication device 300b loads the module based on the identifiable information.
  • the vehicle communication device 300b loads the module in advance before receiving the application request. This eliminates the need for the vehicle communication device 300b to execute the process of loading the module after receiving the application request. Therefore, the vehicle communication device 300b can shorten the processing time for the application request.
  • the communication unit 310 transmits an application request to the request management unit 320.
  • a plurality of modules may exist between the communication unit 310 and the request management unit 320. Then, the request management unit 320 receives the application request via the communication unit 310 and the plurality of modules.
  • the request aggregation unit 390 may be executed after the module management unit 323. However, a plurality of modules may exist between the module management unit 323 and the request aggregation unit 390.
  • the conversion unit 340 and the unsteady change detection unit 350 may be executed.
  • a plurality of modules may exist between the ECU information transmission unit 332 and the conversion unit 340 or the unsteady change detection unit 350.
  • Embodiment 4 FIG. Next, a fourth embodiment will be described. Matters that are different from the first to third embodiments will be mainly described, and descriptions of items common to the first to third embodiments will be omitted. Embodiment 4 may refer to FIGS. 3 to 12 and 14 to 19. In the first to third embodiments, the case where the cloud servers 100, 101, and 102 exist outside the vehicle-mounted device has been described. In the fourth embodiment, a case will be described in which the functions of the cloud servers 100, 101, and 102 are provided in the vehicle-mounted device.
  • FIG. 20 is a functional block diagram illustrating the configuration of the vehicle-mounted device according to the fourth embodiment.
  • the in-vehicle device 200c includes a request unit 800, a vehicle communication unit 300c, and ECUs 400 to 403. Part or all of the request unit 800 and the vehicle communication unit 300c may be realized by a processor included in the vehicle-mounted device 200c.
  • Part or all of the request unit 800 may be realized as a module of the higher-level applications 100a, 101a, and 102a executed by the processor of the in-vehicle device 200c.
  • Part or all of the vehicle communication unit 300c may be realized as a module of a program executed by a processor included in the vehicle-mounted device 200c.
  • the function of the request unit 800 is the same as that of the cloud servers 100, 101, 102 (upper applications 100a, 101a, 102a).
  • the request unit 800 transmits an application request.
  • the application request includes an ECU data acquisition instruction, and support information for supporting calculation processing executed by the vehicle communication unit 300c when the vehicle communication unit 300c calculates vehicle calculation information using the ECU data. .
  • the function of the vehicle communication unit 300c is the same as that of the vehicle communication device described in the first to third embodiments.
  • the vehicle communication unit 300c receives an application request.
  • the vehicle communication unit 300c acquires ECU data from the ECU based on the acquisition instruction.
  • the vehicle communication unit 300c calculates vehicle calculation information based on the ECU data and the support information.
  • the vehicle communication unit 300c transmits the vehicle calculation information to the request unit 800.
  • the function of the vehicle communication unit 300c is the same as the function of the vehicle communication device described in the first to third embodiments, and a description thereof will be omitted.
  • the request unit 800 and the vehicle communication unit 300c can execute the same processes as those performed between the cloud servers 100, 101, and 102 and the vehicle communication device described in the first to third embodiments. Therefore, the fourth embodiment has the same effects as the effects described in the first to third embodiments.

Landscapes

  • Engineering & Computer Science (AREA)
  • Mechanical Engineering (AREA)
  • Small-Scale Networks (AREA)

Abstract

A communication system comprises: an in-vehicle device (200) having a vehicle communication device (300) and an ECU that acquires ECU data; and a cloud server transmitting, to the in-vehicle device (200), an application request which includes an ECU data acquisition instruction and assistance information for assisting with calculation processing executed by the in-vehicle device (200) when the in-vehicle device (200) is caused to calculate vehicle calculation information that indicates request target information, using the ECU data. The vehicle communication device (300) receives the application request, acquires the ECU data from the ECU on the basis of the acquisition instruction, calculates the vehicle calculation information on the basis of the ECU data and the assistance information, and transmits the vehicle calculation information to the cloud server.

Description

通信システム、車載装置、情報取得方法、及び情報取得プログラムCommunication system, in-vehicle device, information acquisition method, and information acquisition program
　本発明は、通信システム、車載装置、情報取得方法、及び情報取得プログラムに関する。 The present invention relates to a communication system, an in-vehicle device, an information acquisition method, and an information acquisition program.
　車に関する情報が、様々な用途に用いられている。当該情報は、車に搭載された装置から取得することができる。当該情報は、車両データとも言う。
　ここで、車両データをアプリケーションで利用可能な実用データ形式に変換する技術が提案されている（特許文献１を参照）。例えば、特許文献１のナビゲーション装置は、車両データを実用データ形式に変換するための変換テーブルを記憶する。ナビゲーション装置は、変換テーブルに基づいて車両データを実用データ形式に変換する。 Information about cars is used for various purposes. The information can be obtained from a device mounted on the vehicle. The information is also referred to as vehicle data.
Here, a technique for converting vehicle data into a practical data format that can be used in an application has been proposed (see Patent Document 1). For example, the navigation device of Patent Literature 1 stores a conversion table for converting vehicle data into a practical data format. The navigation device converts the vehicle data into a practical data format based on the conversion table.
特開２００２－３３１８８２号公報JP-A-2002-331882
　上記技術では、変換テーブルが用いられる。車両データを実用データ形式に変換するためには、予め変換テーブルを作成しておく必要がある。車両データには、様々な種類のデータがある。そのため、様々な種類のデータを変換するための変換テーブルを作成することは、困難である。 変 換 In the above technology, a conversion table is used. In order to convert vehicle data into a practical data format, it is necessary to create a conversion table in advance. There are various types of data in vehicle data. Therefore, it is difficult to create a conversion table for converting various types of data.
　本発明の目的は、容易に車算出情報を取得することである。 目的 An object of the present invention is to easily obtain vehicle calculation information.
　本発明の一態様に係る通信システムが提供される。通信システムは、車に関する情報を取得する情報取得部と車通信装置とを有する車載装置と、前記車に関する情報の取得指示と、前記車に関する情報を用いて、要求対象の情報を示す車算出情報を前記車載装置に算出させる際に前記車載装置が実行する算出処理を支援するための支援情報と、を含む要求情報を前記車載装置に送信する情報処理装置と、を含む。前記車通信装置は、前記要求情報を受信し、前記取得指示に基づいて、前記情報取得部から前記車に関する情報を取得し、前記車に関する情報と前記支援情報に基づいて、前記車算出情報を算出し、前記車算出情報を前記情報処理装置に送信する。 通信 シ ス テ ム A communication system according to one embodiment of the present invention is provided. The communication system includes a vehicle-mounted device having an information acquisition unit that acquires information about the vehicle and a vehicle communication device, an instruction to acquire the information about the vehicle, and vehicle calculation information that indicates information of a request target using the information about the vehicle. And support information for supporting calculation processing executed by the vehicle-mounted device when the vehicle-mounted device calculates the information. The vehicle communication device receives the request information, acquires information about the vehicle from the information acquisition unit based on the acquisition instruction, and acquires the vehicle calculation information based on the information about the vehicle and the support information. And transmits the vehicle calculation information to the information processing device.
　本発明によれば、容易に車算出情報を取得することができる。 According to the present invention, vehicle calculation information can be easily obtained.
実施の形態１の通信システムを示す図である。1 is a diagram illustrating a communication system according to a first embodiment. 実施の形態１の車通信装置が有するハードウェアの構成を示す図である。FIG. 3 is a diagram illustrating a configuration of hardware included in the vehicle communication device according to the first embodiment. 実施の形態１の車通信装置の構成を示す機能ブロック図である。FIG. 2 is a functional block diagram illustrating a configuration of the vehicle communication device according to the first embodiment. 実施の形態１のアプリケーション要求の具体例を示す図である。FIG. 3 is a diagram illustrating a specific example of an application request according to the first embodiment; 実施の形態１の単位変換テーブルの例を示す図である。FIG. 5 is a diagram illustrating an example of a unit conversion table according to the first embodiment. 実施の形態１の算出支援テーブルの例を示す図である。FIG. 7 is a diagram illustrating an example of a calculation support table according to the first embodiment. 実施の形態１のモジュール管理リストの例を示す図である。FIG. 5 is a diagram illustrating an example of a module management list according to the first embodiment. 実施の形態１の呼出モジュール管理リストの例を示す図である。FIG. 5 is a diagram illustrating an example of a call module management list according to the first embodiment. 実施の形態１の要求パケットのフォーマットの例を示す図である。FIG. 3 is a diagram illustrating an example of a format of a request packet according to the first embodiment. 実施の形態１のＥＣＵパケットのフォーマットの例を示す図である。FIG. 3 is a diagram illustrating an example of a format of an ECU packet according to the first embodiment. 実施の形態１の車通信装置のステートチャート（その１）である。5 is a state chart (No. 1) of the vehicle communication device according to the first embodiment. 実施の形態１の車通信装置のステートチャート（その２）である。6 is a state chart (part 2) of the vehicle communication device according to the first embodiment. 実施の形態１のクラウドサーバと車載装置との間で実行される処理の具体例を示す図である。FIG. 4 is a diagram illustrating a specific example of a process executed between the cloud server and the in-vehicle device according to the first embodiment. 実施の形態２の車通信装置の構成を示す機能ブロック図である。FIG. 7 is a functional block diagram illustrating a configuration of a vehicle communication device according to a second embodiment. 実施の形態２のモジュール管理リストの例を示す図である。FIG. 14 is a diagram illustrating an example of a module management list according to the second embodiment. 実施の形態２の呼出モジュール管理リストの例を示す図である。FIG. 14 is a diagram illustrating an example of a call module management list according to the second embodiment. 実施の形態２の車通信装置のステートチャート（その１）である。9 is a state chart (No. 1) of the vehicle communication device according to the second embodiment. 実施の形態３の車通信装置の構成を示す機能ブロック図である。FIG. 13 is a functional block diagram illustrating a configuration of a vehicle communication device according to a third embodiment. 実施の形態３の呼出モジュール管理リストの例を示す図である。FIG. 14 is a diagram illustrating an example of a call module management list according to the third embodiment. 実施の形態４の車載装置の構成を示す機能ブロック図である。FIG. 14 is a functional block diagram illustrating a configuration of an in-vehicle device according to a fourth embodiment.
　以下、図面を参照しながら実施の形態を説明する。以下の実施の形態は、例にすぎず、本発明の範囲内で種々の変更が可能である。 Hereinafter, embodiments will be described with reference to the drawings. The following embodiments are merely examples, and various modifications can be made within the scope of the present invention.
実施の形態１．
　図１は、実施の形態１の通信システムを示す図である。通信システムは、クラウドサーバ１００及び車載装置２００を含む。通信システムは、クラウドサーバ１０１，１０２をさらに含んでもよい。通信システムは、情報取得方法を実行することができる。
　クラウドサーバ１００～１０２は、車載装置２００と通信する。クラウドサーバ１００～１０２は、複数のクラウドサーバと車載装置２００との間に存在する複数のゲートウェイと考えてもよい。クラウドサーバ又はゲートウェイは、情報処理装置とも言う。 Embodiment 1 FIG.
FIG. 1 is a diagram illustrating the communication system according to the first embodiment. The communication system includes the cloud server 100 and the in-vehicle device 200. The communication system may further include cloud servers 101 and 102. The communication system can execute the information acquisition method.
The cloud servers 100 to 102 communicate with the in-vehicle device 200. The cloud servers 100 to 102 may be considered as a plurality of gateways existing between the plurality of cloud servers and the vehicle-mounted device 200. The cloud server or the gateway is also called an information processing device.
　クラウドサーバ１００は、上位アプリケーション１００ａを有する。クラウドサーバ１０１は、上位アプリケーション１０１ａを有する。クラウドサーバ１０２は、上位アプリケーション１０２ａを有する。ここで、クラウドサーバ１００は、上位アプリケーション１０１ａ，１０２ａを有してもよい。すなわち、１つのクラウドサーバが、複数の上位アプリケーションを有してもよい。 The cloud server 100 has a higher-level application 100a. The cloud server 101 has a host application 101a. The cloud server 102 has a host application 102a. Here, the cloud server 100 may include upper applications 101a and 102a. That is, one cloud server may have a plurality of higher-level applications.
　車載装置２００は、車通信装置３００及びＥＣＵ（Ｅｎｇｉｎｅ　Ｃｏｎｔｒｏｌ　Ｕｎｉｔ）４００，４０１，４０２，４０３を有する。ＥＣＵ４００～４０３は、複数のセンサでもよい。ＥＣＵ又はセンサは、情報取得部とも言う。ＥＣＵ４００～４０３は、車に関する情報を取得する。例えば、ＥＣＵ４００～４０３は、車載装置２００が有する装置（図示を省略）から車に関する情報を取得する。また、例えば、ＥＣＵ４００～４０３は、様々な情報に基づいて車に関する情報を算出することで、車に関する情報を取得する場合もある。車に関する情報は、車の動作に関する情報と考えてもよい。車に関する情報は、ＥＣＵデータ又は車両データとも言う。以下、車に関する情報は、ＥＣＵデータと呼ぶ。 The vehicle-mounted device 200 includes the vehicle communication device 300 and ECUs (Engine Control Units) 400, 401, 402, and 403. The ECUs 400 to 403 may be a plurality of sensors. The ECU or the sensor is also called an information acquisition unit. The ECUs 400 to 403 obtain information on the vehicle. For example, the ECUs 400 to 403 obtain information on a car from a device (not shown) of the vehicle-mounted device 200. Further, for example, the ECUs 400 to 403 may acquire information about the vehicle by calculating information about the vehicle based on various information. The information on the car may be considered as information on the operation of the car. Information about a vehicle is also referred to as ECU data or vehicle data. Hereinafter, the information on the vehicle is referred to as ECU data.
　クラウドサーバ１００～１０２は、アプリケーション要求を車載装置２００に送信する。アプリケーション要求は、要求情報とも言う。アプリケーション要求には、ＥＣＵデータの取得指示が含まれている。また、アプリケーション要求には、支援情報が含まれている。支援情報は、ＥＣＵデータを用いて、車算出情報を車載装置２００に算出させる際に車載装置２００が実行する算出処理を支援するための情報である。また、車算出情報は、要求対象の情報を示す。すなわち、車算出情報は、アプリケーション要求が要求する対象の情報である。また、車算出情報は、上位アプリケーション１００ａ～１０２ａが受け取れる情報に整形された情報であると表現してもよい。 The cloud servers 100 to 102 transmit the application request to the in-vehicle device 200. The application request is also called request information. The application request includes an instruction to acquire ECU data. In addition, the application request includes support information. The support information is information for supporting the calculation process executed by the in-vehicle device 200 when the in-vehicle device 200 calculates the vehicle calculation information using the ECU data. The vehicle calculation information indicates information of a request target. That is, the vehicle calculation information is information that is requested by the application request. Further, the vehicle calculation information may be expressed as information shaped into information that can be received by the upper-level applications 100a to 102a.
　車通信装置３００は、クラウドサーバ１００～１０２が送信したアプリケーション要求を受信する。ここで、クラウドサーバ１００が送信したアプリケーション要求を車通信装置３００が受信した場合について、説明する。
　車通信装置３００は、クラウドサーバ１００が送信したアプリケーション要求を受信する。車通信装置３００は、取得指示に基づいて、ＥＣＵからＥＣＵデータを取得する。車通信装置３００は、ＥＣＵデータと支援情報とに基づいて、車算出情報を算出する。車通信装置３００は、車算出情報をクラウドサーバ１００に送信する。 The vehicle communication device 300 receives the application request transmitted by the cloud servers 100 to 102. Here, the case where the vehicle communication device 300 receives the application request transmitted by the cloud server 100 will be described.
The car communication device 300 receives the application request transmitted by the cloud server 100. The vehicle communication device 300 acquires ECU data from the ECU based on the acquisition instruction. The vehicle communication device 300 calculates vehicle calculation information based on the ECU data and the support information. The vehicle communication device 300 transmits the vehicle calculation information to the cloud server 100.
　同様に、クラウドサーバ１０１，１０２は、車算出情報を取得する。このように、クラウドサーバ１００～１０２は、アプリケーション要求で要求した情報を取得することができる。
　図１のクラウドサーバの数は、３つである。しかし、クラウドサーバの数は、３つに限らない。図１のＥＣＵの数は、４つである。しかし、ＥＣＵの数は、４つに限らない。 Similarly, the cloud servers 101 and 102 acquire vehicle calculation information. As described above, the cloud servers 100 to 102 can acquire the information requested by the application request.
The number of cloud servers in FIG. 1 is three. However, the number of cloud servers is not limited to three. The number of ECUs in FIG. 1 is four. However, the number of ECUs is not limited to four.
　次に、車通信装置３００が有するハードウェアについて説明する。
　図２は、実施の形態１の車通信装置が有するハードウェアの構成を示す図である。車通信装置３００は、プロセッサ３０１、揮発性記憶装置３０２、及び不揮発性記憶装置３０３を有する。 Next, the hardware of the vehicle communication device 300 will be described.
FIG. 2 is a diagram illustrating a configuration of hardware included in the vehicle communication device according to the first embodiment. The vehicle communication device 300 includes a processor 301, a volatile storage device 302, and a nonvolatile storage device 303.
　プロセッサ３０１は、車通信装置３００全体を制御する。例えば、プロセッサ３０１は、ＣＰＵ（Ｃｅｎｔｒａｌ　Ｐｒｏｃｅｓｓｉｎｇ　Ｕｎｉｔ）、又はＦＰＧＡ（Ｆｉｅｌｄ　Ｐｒｏｇｒａｍｍａｂｌｅ　Ｇａｔｅ　Ａｒｒａｙ）などである。プロセッサ３０１は、マルチプロセッサでもよい。車通信装置３００は、処理回路によって実現されてもよく、又は、ソフトウェア、ファームウェア若しくはそれらの組み合わせによって実現されてもよい。なお、処理回路は、単一回路又は複合回路でもよい。 The processor 301 controls the entire vehicle communication device 300. For example, the processor 301 is a CPU (Central Processing Unit) or an FPGA (Field Programmable Gate Array). Processor 301 may be a multiprocessor. The vehicle communication device 300 may be realized by a processing circuit, or may be realized by software, firmware, or a combination thereof. Note that the processing circuit may be a single circuit or a composite circuit.
　揮発性記憶装置３０２は、車通信装置３００の主記憶装置である。例えば、揮発性記憶装置３０２は、ＲＡＭ（Ｒａｎｄｏｍ　Ａｃｃｅｓｓ　Ｍｅｍｏｒｙ）である。不揮発性記憶装置３０３は、車通信装置３００の補助記憶装置である。例えば、不揮発性記憶装置３０３は、ＳＳＤ（Ｓｏｌｉｄ　Ｓｔａｔｅ　Ｄｒｉｖｅ）である。 The volatile storage device 302 is a main storage device of the vehicle communication device 300. For example, the volatile storage device 302 is a RAM (Random Access Memory). The non-volatile storage device 303 is an auxiliary storage device of the vehicle communication device 300. For example, the nonvolatile storage device 303 is an SSD (Solid \ State \ Drive).
　クラウドサーバ１００～１０２は、車通信装置３００と同様に、プロセッサ、揮発性記憶装置、及び不揮発性記憶装置を有する。
　ここで、クラウドサーバ１００と車通信装置３００との間で実行される処理は、クラウドサーバ１０１と車通信装置３００との間で実行される処理と同じである。また、クラウドサーバ１００と車通信装置３００との間で実行される処理は、クラウドサーバ１０２と車通信装置３００との間で実行される処理と同じである。そこで、以下、クラウドサーバ１００と車通信装置３００との間で実行される処理について、主に説明する。そして、クラウドサーバ１０１，１０２と車通信装置３００との間で実行される処理については、説明を省略する。 Each of the cloud servers 100 to 102 has a processor, a volatile storage device, and a nonvolatile storage device, similarly to the vehicle communication device 300.
Here, the process executed between the cloud server 100 and the vehicle communication device 300 is the same as the process executed between the cloud server 101 and the vehicle communication device 300. Further, the processing executed between the cloud server 100 and the vehicle communication device 300 is the same as the processing executed between the cloud server 102 and the vehicle communication device 300. Therefore, hereinafter, processing executed between the cloud server 100 and the vehicle communication device 300 will be mainly described. The description of the processing executed between the cloud servers 101 and 102 and the vehicle communication device 300 is omitted.
　次に、車通信装置３００が有する機能ブロックについて説明する。
　図３は、実施の形態１の車通信装置の構成を示す機能ブロック図である。車通信装置３００は、通信部３１０、要求管理部３２０、ＥＣＵ情報管理部３３０、変換部３４０、非定常変化検出部３５０、車算出情報管理部３６０、記憶部３７０、及びメイン処理部３８０を有する。 Next, functional blocks of the vehicle communication device 300 will be described.
FIG. 3 is a functional block diagram illustrating a configuration of the vehicle communication device according to the first embodiment. The vehicle communication device 300 includes a communication unit 310, a request management unit 320, an ECU information management unit 330, a conversion unit 340, an unsteady change detection unit 350, a vehicle calculation information management unit 360, a storage unit 370, and a main processing unit 380. .
　要求管理部３２０は、要求受付部３２１、要求解析部３２２、モジュール管理部３２３、及び要求整形伝達部３２４を有する。ＥＣＵ情報管理部３３０は、ＥＣＵ情報取得部３３１及びＥＣＵ情報伝達部３３２を有する。変換部３４０は、データ変換部３４１を有する。非定常変化検出部３５０は、統計解析処理部３５１及び登録部３５２を有する。車算出情報管理部３６０は、車算出情報受付部３６１及び車算出情報送信部３６２を有する。 The request management unit 320 includes a request reception unit 321, a request analysis unit 322, a module management unit 323, and a request shaping transmission unit 324. The ECU information management section 330 has an ECU information acquisition section 331 and an ECU information transmission section 332. The conversion unit 340 has a data conversion unit 341. The non-stationary change detection unit 350 includes a statistical analysis processing unit 351 and a registration unit 352. The vehicle calculation information management unit 360 has a vehicle calculation information reception unit 361 and a vehicle calculation information transmission unit 362.
　記憶部３７０は、揮発性記憶装置３０２又は不揮発性記憶装置３０３に確保した記憶領域として実現してもよい。
　通信部３１０、要求管理部３２０、要求受付部３２１、要求解析部３２２、モジュール管理部３２３、要求整形伝達部３２４、ＥＣＵ情報管理部３３０、ＥＣＵ情報取得部３３１、及びＥＣＵ情報伝達部３３２の一部又は全部は、プロセッサ３０１によって実現してもよい。変換部３４０、データ変換部３４１、非定常変化検出部３５０、統計解析処理部３５１、登録部３５２、車算出情報管理部３６０、車算出情報受付部３６１、車算出情報送信部３６２、及びメイン処理部３８０の一部又は全部は、プロセッサ３０１によって実現してもよい。 The storage unit 370 may be realized as a storage area secured in the volatile storage device 302 or the nonvolatile storage device 303.
One of the communication unit 310, the request management unit 320, the request reception unit 321, the request analysis unit 322, the module management unit 323, the request shaping transmission unit 324, the ECU information management unit 330, the ECU information acquisition unit 331, and the ECU information transmission unit 332 All or some of the units may be realized by the processor 301. Conversion section 340, data conversion section 341, non-stationary change detection section 350, statistical analysis processing section 351, registration section 352, vehicle calculation information management section 360, vehicle calculation information reception section 361, vehicle calculation information transmission section 362, and main processing Part or all of the unit 380 may be realized by the processor 301.
　通信部３１０、要求管理部３２０、要求受付部３２１、要求解析部３２２、モジュール管理部３２３、要求整形伝達部３２４、ＥＣＵ情報管理部３３０、ＥＣＵ情報取得部３３１、及びＥＣＵ情報伝達部３３２の一部又は全部は、プロセッサ３０１が実行するプログラムのモジュールとして実現してもよい。変換部３４０、データ変換部３４１、非定常変化検出部３５０、統計解析処理部３５１、登録部３５２、車算出情報管理部３６０、車算出情報受付部３６１、車算出情報送信部３６２、及びメイン処理部３８０の一部又は全部は、プロセッサ３０１が実行するプログラムのモジュールとして実現してもよい。 One of the communication unit 310, the request management unit 320, the request reception unit 321, the request analysis unit 322, the module management unit 323, the request shaping transmission unit 324, the ECU information management unit 330, the ECU information acquisition unit 331, and the ECU information transmission unit 332 All or a part may be realized as a module of a program executed by the processor 301. Conversion section 340, data conversion section 341, non-stationary change detection section 350, statistical analysis processing section 351, registration section 352, vehicle calculation information management section 360, vehicle calculation information reception section 361, vehicle calculation information transmission section 362, and main processing Part or all of the unit 380 may be realized as a module of a program executed by the processor 301.
　以下、要求管理部３２０、要求受付部３２１、要求解析部３２２、モジュール管理部３２３、要求整形伝達部３２４、ＥＣＵ情報管理部３３０、ＥＣＵ情報取得部３３１、及びＥＣＵ情報伝達部３３２は、プロセッサ３０１が実行するプログラムのモジュールとして説明する。変換部３４０、データ変換部３４１、非定常変化検出部３５０、統計解析処理部３５１、登録部３５２、車算出情報管理部３６０、車算出情報受付部３６１、車算出情報送信部３６２、及びメイン処理部３８０は、プロセッサ３０１が実行するプログラムのモジュールとして説明する。これらのモジュールは、プロセッサ３０１が実行するミドルウェアで実現してもよい。 Hereinafter, the request management unit 320, the request reception unit 321, the request analysis unit 322, the module management unit 323, the request shaping transmission unit 324, the ECU information management unit 330, the ECU information acquisition unit 331, and the ECU information transmission unit 332 include a processor 301. Will be described as a module of a program to be executed. Conversion section 340, data conversion section 341, non-stationary change detection section 350, statistical analysis processing section 351, registration section 352, vehicle calculation information management section 360, vehicle calculation information reception section 361, vehicle calculation information transmission section 362, and main processing The unit 380 will be described as a module of a program executed by the processor 301. These modules may be realized by middleware executed by the processor 301.
　ここで、クラウドサーバ１００～１０２又は上位アプリケーション１００ａ～１０２ａは、車通信装置３００よりも上位の装置又は上位のアプリケーションである。そのため、クラウドサーバ１００～１０２又は上位アプリケーション１００ａ～１０２ａは、上位機能ユニットと表現してもよい。また、ＥＣＵ４００～４０３は、車通信装置３００よりも下位の装置である。そのため、ＥＣＵ４００～４０３は、下位機能ユニットと表現してもよい。また、上位アプリケーション及びミドルウェアは、情報取得プログラムと表現してもよい。
　通信部３１０は、クラウドサーバ１００と通信する。通信部３１０は、上位アプリケーション１００ａが送信したアプリケーション要求を受信する。 Here, the cloud servers 100 to 102 or the higher-level applications 100a to 102a are higher-level devices or higher-level applications than the vehicle communication device 300. Therefore, the cloud servers 100 to 102 or the higher-level applications 100a to 102a may be expressed as higher-level function units. The ECUs 400 to 403 are devices lower than the vehicle communication device 300. Therefore, the ECUs 400 to 403 may be expressed as lower functional units. Further, the upper application and the middleware may be expressed as an information acquisition program.
The communication unit 310 communicates with the cloud server 100. The communication unit 310 receives the application request transmitted by the upper application 100a.
　ここで、アプリケーション要求を具体的に説明する。
　図４は、実施の形態１のアプリケーション要求の具体例を示す図である。例えば、アプリケーション要求５００は、上位アプリケーション１００ａが発行する情報である。アプリケーション要求５００は、アプリケーション要求ファイル５０１、単位変換テーブル５０２、及び算出支援テーブル５０３を含む。アプリケーション要求ファイル５０１は、“上位アプリケーション＃１．ｉｎｉ”というファイル名が付けられていてもよい。 Here, the application request will be specifically described.
FIG. 4 is a diagram illustrating a specific example of the application request according to the first embodiment. For example, the application request 500 is information issued by the host application 100a. The application request 500 includes an application request file 501, a unit conversion table 502, and a calculation support table 503. The application request file 501 may be given a file name “upper application # 1.ini”.
　また、アプリケーション要求ファイル５０１は、複数のセクションに区切られている。複数のセクションには、機能セクション、データ内容定義セクション、及びデータ変換定義セクションがある。機能セクションは、予め名称が規定されたセクションである。データ内容定義セクションは、任意の名前を規定できるセクションである。データ変換定義セクションは、データのフォーマット整形規則を定義するセクションである。 The application request file 501 is divided into a plurality of sections. The plurality of sections include a function section, a data content definition section, and a data conversion definition section. The function section is a section whose name is defined in advance. The data content definition section is a section in which an arbitrary name can be defined. The data conversion definition section is a section for defining data format shaping rules.
　アプリケーション要求ファイル５０１は、インタフェース情報セクションである“［＿ＩＮＴＥＲＦＡＣＥ＿］”を含む。インタフェース情報セクションには、アプリケーション名、アプリケーションＩＤ（ｉｄｅｎｔｉｆｉｅｒ）、動作指示、インタフェース種別、ＣＡＮ（Ｃｏｎｔｒｏｌｌｅｒ　Ａｒｅａ　Ｎｅｔｗｏｒｋ）系統番号、フィルタリングＣＡＮ　ＩＤ、通知周期、及び非定常変化検出を含む。 The application request file 501 includes an interface information section “[_INTERFACE_]”. The interface information section includes an application name, an application ID (identifier), an operation instruction, an interface type, a CAN (Controller Area Network) system number, a filtering CAN ID, a notification cycle, and a non-stationary change detection.
　アプリケーション名には、アプリケーション要求５００を発行したアプリケーション名（例えば、上位アプリケーション１００ａの名称）が登録される。アプリケーションＩＤには、アプリケーション要求５００を発行したアプリケーションを識別する情報が登録される。動作指示には、ＥＣＵ情報管理部３３０に対する動作指示が登録される。例えば、動作指示には、ＥＣＵ情報管理部３３０にＥＣＵデータの取得指示が登録される。 The name of the application that issued the application request 500 (for example, the name of the higher-level application 100a) is registered in the application name. In the application ID, information for identifying the application that issued the application request 500 is registered. In the operation instruction, an operation instruction to the ECU information management unit 330 is registered. For example, an acquisition instruction for ECU data is registered in the ECU information management unit 330 as the operation instruction.
　インタフェース種別には、ＥＣＵからデータを取得するインタフェースが登録される。例えば、インタフェース種別には、“０”（ライブラリ）、“１”（メモリ）、“２”（ＣＡＮ）、又は“３”（イーサーネット）が登録される。
　ＣＡＮ系統番号には、ＣＡＮの系統を示す情報が登録される。例えば、ＣＡＮの系統番号には、“０”又は“１”が登録される。フィルタリングＣＡＮ　ＩＤには、データフィルタリング用ＣＡＮのメッセージＩＤが登録される。例えば、フィルタリングＣＡＮ　ＩＤには、“ｈ７３０”と“ｈ７３１”が登録される。 In the interface type, an interface for acquiring data from the ECU is registered. For example, “0” (library), “1” (memory), “2” (CAN), or “3” (Ethernet) is registered as the interface type.
Information indicating a CAN system is registered in the CAN system number. For example, “0” or “1” is registered as the CAN system number. In the filtering CAN ID, a message ID of the data filtering CAN is registered. For example, “h730” and “h731” are registered as the filtering CAN ID.
　通知周期には、クラウドサーバ（すなわち、上位アプリケーション）に車算出情報を通知する時間が登録される。例えば、通知周期には、１００００［ｍｓｅｃ］（すなわち、１０秒）が登録される。また、通知周期は、ＥＣＵから情報を取得する周期と考えてもよい。すなわち、通知周期は、ＥＣＵからＥＣＵデータを取得する周期と考えてもよい。 In the notification cycle, the time for notifying the cloud server (that is, the host application) of the vehicle calculation information is registered. For example, 10000 [msec] (that is, 10 seconds) is registered in the notification cycle. The notification cycle may be considered as a cycle for acquiring information from the ECU. That is, the notification cycle may be considered as a cycle of acquiring ECU data from the ECU.
　非定常変化検出には、車通信装置３００に統計解析処理を実行させるか否かを示す情報が登録される。例えば、非定常変化検出には、“０”（無効）、“１”（直値）、“２”（時間微分値）、“３”（平均値）、“４”（平均偏差値）、又は“５”（標準偏差値）が登録される。非定常変化検出に“０”以外の値が登録されている場合、アプリケーション要求５００は、発行元の上位アプリケーションが統計解析命令を指示していることを示す。統計解析命令は、ＥＣＵデータの統計解析命令と考えてもよい。また、統計解析命令は、車算出情報の統計解析命令と考えてもよい。 情報 In the unsteady change detection, information indicating whether or not the vehicle communication device 300 performs the statistical analysis process is registered. For example, in the detection of the unsteady change, "0" (invalid), "1" (direct value), "2" (time differential value), "3" (average value), "4" (average deviation value), Alternatively, “5” (standard deviation value) is registered. If a value other than “0” is registered in the unsteady change detection, the application request 500 indicates that the issuing upper application has instructed the statistical analysis command. The statistical analysis command may be considered as a statistical analysis command for ECU data. Further, the statistical analysis command may be considered as a statistical analysis command of the vehicle calculation information.
　アプリケーション要求ファイル５０１は、上位提供データ構造定義セクションである“［＿ＳＴＲＵＣＴＵＲＥ＿］”を含む。上位提供データ構造定義セクションには、上位アプリケーションに渡すデータのデータ構造が定義される。すなわち、上位提供データ構造定義セクションは、要求対象の情報を示していると考えてもよい。そのため、上位提供データ構造定義セクションに登録されている情報には、車載装置２００に算出させる車算出情報が登録されていると考えてもよい。 The application request file 501 includes “[_STRUCTURE_]” which is a higher-level provided data structure definition section. The higher-level data structure definition section defines the data structure of data to be passed to the higher-level application. That is, the higher-level provided data structure definition section may be considered to indicate the information to be requested. Therefore, it may be considered that the vehicle registration information to be calculated by the in-vehicle device 200 is registered in the information registered in the higher-level provided data structure definition section.
　例えば、上位提供データ構造定義セクションには、ｅｃｕ１.ｏｗｎＶｅｌｏｃｉｔｙ、ｅｃｕ３.ｒｅｌａｔｉｖｅＶｅｌｏｃｉｔｙ、ｅｃｕ３．１ｔｒｉｐＤｉｓｔａｎｃｅ、ｅｃｕ３．１ｔｒｉｐＴｉｍｅ、ａｂｓｌｔＶｅｌｏｃｉｔｙ、及びａｖｒｇＶｅｌｏｃｉｔｙが登録される。なお、データ構造に含まれる各データのデータ長は、３２ビットである。
　ここで、“ｅｃｕ１”は、ＥＣＵ４００のＩＤである。“ｅｃｕ３”は、ＥＣＵ４０２のＩＤである。 For example, ecu1.ownVelocity, ecu3.relativeVelocity, ecu3.1tripDistance, ecu3.1tripTime, absltVelocity, and avrgVelocity are registered in the higher-level provided data structure definition section. The data length of each data included in the data structure is 32 bits.
Here, “ecu1” is the ID of the ECU 400. “Ecu3” is the ID of the ECU 402.
　アプリケーション要求ファイル５０１は、データ変換定義セクションである“［＿ＤＡＴＡ＿ＳＰＥＣ＿］”を含む。データ変換定義セクションには、どのＥＣＵデータを取得するのかを示す情報が登録される。すなわち、データ変換定義セクションには、ＥＣＵデータの取得指示が登録される。また、どのＥＣＵから取得するかは、上位提供データ構造定義セクションに登録される。例えば、上位提供データ構造定義セクションに登録されているｅｃｕ１.ｏｗｎＶｅｌｏｃｉｔｙは、ＥＣＵ４００からｏｗｎＶｅｌｏｃｉｔｙを取得することを意味する。このように、どのＥＣＵから取得するかが上位提供データ構造定義セクションに登録されているので、上位提供データ構造定義セクションに登録されている情報が、ＥＣＵデータの取得指示と考えてもよい。 The application request file 501 includes a data conversion definition section “[_DATA_SPEC_]”. In the data conversion definition section, information indicating which ECU data is acquired is registered. That is, an instruction to acquire ECU data is registered in the data conversion definition section. The ECU from which to obtain the information is registered in the higher-level data structure definition section. For example, ecu1.ownVelocity registered in the higher-level provided data structure definition section means that ownVelocity is acquired from the ECU 400. As described above, from which ECU the information is acquired is registered in the higher-level provided data structure definition section, so that the information registered in the higher-level provided data structure definition section may be considered as an ECU data acquisition instruction.
　また、データ変換定義セクションには、ＥＣＵから取得した情報をＥＣＵデータの形式にフォーマット変換する際の規則が定義される。例えば、データ変換定義セクションには、［ｏｗｎＶｅｌｏｃｉｔｙ］が登録される。［ｏｗｎＶｅｌｏｃｉｔｙ］には、“ＩｄＦ＝ＣＡＮ”が登録される。これは、“ＣＡＮからデータを取得する”の意味である。［ｏｗｎＶｅｌｏｃｉｔｙ］には、ＣＡＮ　ＩＤが“０ｘ７３０”であることが登録される。［ｏｗｎＶｅｌｏｃｉｔｙ］には、“Ｆ＝＃２”が登録される。これは、“ＥＣＵから取得した情報の先頭から２ｂｙｔｅのうち、後ろから１ｂｙｔｅを取得する”の意味である。すなわち、取得された１ｂｙｔｅの情報が、ｏｗｎＶｅｌｏｃｉｔｙである。 (4) The data conversion definition section defines rules for converting information obtained from the ECU into a format of ECU data. For example, [ownVelocity] is registered in the data conversion definition section. “IdF = CAN” is registered in [ownVelocity]. This means "acquire data from CAN". In [ownVelocity], it is registered that the CAN @ ID is "0x730". “F = # 2” is registered in [ownVelocity]. This means "acquiring 1 byte from the back of the 2 bytes from the beginning of the information acquired from the ECU". That is, the acquired 1-byte information is ownVelocity.
　また、データ変換定義セクションには、クラウドサーバ１００又は上位アプリケーション１００ａが指定する単位が登録される。例えば、［ｏｗｎＶｅｌｏｃｉｔｙ］には、“ＦＵｎｉｔ＝ｍ／ｓ”が登録される。これは、クラウドサーバ１００又は上位アプリケーション１００ａがｏｗｎＶｅｌｏｃｉｔｙを“ｍ／ｓ”の単位で取得したいことを示す。言い換えれば、アプリケーション要求ファイル５０１には、車載装置２００に、ｏｗｎＶｅｌｏｃｉｔｙを予め決められた単位である“ｍ／ｓ”で算出させることが登録されている。このように、アプリケーション要求５００には、車載装置２００に車算出情報を予め決められた単位で算出させることを示す情報が含まれている。
　このように、アプリケーション要求ファイル５０１には、変数の宣言及び定義が登録される。 In the data conversion definition section, a unit specified by the cloud server 100 or the higher-level application 100a is registered. For example, “FUnit = m / s” is registered in [ownVelocity]. This indicates that the cloud server 100 or the host application 100a wants to acquire ownVelocity in the unit of “m / s”. In other words, it is registered in the application request file 501 that the in-vehicle device 200 calculates ownVelocity in a predetermined unit of “m / s”. As described above, the application request 500 includes information indicating that the vehicle-mounted device 200 calculates the vehicle calculation information in a predetermined unit.
As described above, the declaration and definition of variables are registered in the application request file 501.
　上述したように、アプリケーション要求５００は、単位変換テーブル５０２及び算出支援テーブル５０３を含む。単位変換テーブル５０２及び算出支援テーブル５０３の総称は、支援情報とも言う。そして、単位変換テーブル５０２及び算出支援テーブル５０３の少なくとも何れかのテーブルを用いて算出された情報が、車算出情報である。 As described above, the application request 500 includes the unit conversion table 502 and the calculation support table 503. The generic name of the unit conversion table 502 and the calculation support table 503 is also called support information. Information calculated using at least one of the unit conversion table 502 and the calculation support table 503 is the vehicle calculation information.
　次に、単位変換テーブル５０２及び算出支援テーブル５０３について説明する。
　図５は、実施の形態１の単位変換テーブルの例を示す図である。単位変換テーブル５０２は、単位変換情報とも言う。単位変換テーブル５０２は、単位を変換するための情報である。データ変換部３４１は、ＥＣＵデータと単位変換テーブル５０２に基づいて、ＥＣＵデータの単位を予め決められた単位に変換された車算出情報を算出することができる。 Next, the unit conversion table 502 and the calculation support table 503 will be described.
FIG. 5 is a diagram illustrating an example of a unit conversion table according to the first embodiment. The unit conversion table 502 is also called unit conversion information. The unit conversion table 502 is information for converting a unit. The data conversion unit 341 can calculate the vehicle calculation information in which the unit of the ECU data is converted into a predetermined unit based on the ECU data and the unit conversion table 502.
　例えば、単位変換テーブル５０２は、速度の項目を有する。ＥＣＵデータの単位が“ｋｍ／ｈ”の場合、データ変換部３４１は、単位変換テーブル５０２を用いて、ＥＣＵデータの単位を“ｋｍ／ｈ”から“ｍ／ｓ”に変換することができる。
　図５は、単位変換テーブル５０２が、“速度”、“緯度／経度”、“高度”、及び“角度”の項目を有する場合を例示している。単位変換テーブル５０２は、図５に例示した項目以外の項目を含んでもよい。 For example, the unit conversion table 502 has an item of speed. When the unit of the ECU data is “km / h”, the data conversion unit 341 can convert the unit of the ECU data from “km / h” to “m / s” using the unit conversion table 502.
FIG. 5 illustrates a case where the unit conversion table 502 has items of “velocity”, “latitude / longitude”, “altitude”, and “angle”. The unit conversion table 502 may include items other than the items illustrated in FIG.
　図６は、実施の形態１の算出支援テーブルの例を示す図である。ここで、例えば、図４では、上位アプリケーション１００ａが絶対速度を要求していることを示している（すなわち、［＿ＳＴＲＵＣＴＵＲＥ＿］のａｂｓｌｔＶｅｌｏｃｉｔｙ）。しかし、ＥＣＵ４００～４０３から取得できるＥＣＵデータには、絶対速度が含まれていない。このような場合、算出支援テーブル５０３が用いられる。 FIG. 6 is a diagram illustrating an example of the calculation support table according to the first embodiment. Here, for example, FIG. 4 shows that the upper-level application 100a requests the absolute speed (that is, absltVelocity of [_STRUCTURE_]). However, the ECU data that can be obtained from the ECUs 400 to 403 does not include the absolute speed. In such a case, the calculation support table 503 is used.
　算出支援テーブル５０３は、算出支援情報とも言う。算出支援テーブル５０３は、複数のＥＣＵデータを用いて車載装置２００に車算出情報を算出させる際に車載装置２００が実行する算出処理を支援するための情報である。 The calculation support table 503 is also referred to as calculation support information. The calculation support table 503 is information for supporting the calculation process executed by the in-vehicle device 200 when the in-vehicle device 200 calculates the vehicle calculation information using the plurality of ECU data.
　例えば、算出支援テーブル５０３は、“絶対速度”の項目を有する。データ変換部３４１は、ＥＣＵ４００から自車速度を示すＥＣＵデータを取得する場合がある。また、データ変換部３４１は、ＥＣＵ４０２から相対速度を示すＥＣＵデータを取得する場合がある。上位アプリケーション１００ａが絶対速度を要求している場合、データ変換部３４１は、算出支援テーブル５０３、自車速度、及び相対速度に基づいて、絶対速度を算出する。 For example, the calculation support table 503 has an item of “absolute speed”. The data conversion unit 341 may acquire ECU data indicating the vehicle speed from the ECU 400. The data conversion unit 341 may acquire ECU data indicating the relative speed from the ECU 402. When the host application 100a requests the absolute speed, the data conversion unit 341 calculates the absolute speed based on the calculation support table 503, the own vehicle speed, and the relative speed.
　また、例えば、算出支援テーブル５０３は、“１ｔｒｉｐ平均速度”の項目を有する。データ変換部３４１は、１ｔｒｉｐ走行距離を示すＥＣＵデータと１ｔｒｉｐ走行時間を示すＥＣＵデータを取得する場合がある。上位アプリケーション１００ａが１ｔｒｉｐ平均速度を要求している場合、データ変換部３４１は、算出支援テーブル５０３、１ｔｒｉｐ走行距離、及び１ｔｒｉｐ走行時間に基づいて、１ｔｒｉｐ平均速度を算出する。 算出 Further, for example, the calculation support table 503 has an item of “1 trip average speed”. The data conversion unit 341 may acquire ECU data indicating one trip traveling distance and ECU data indicating one trip traveling time. When the host application 100a requests the one-trip average speed, the data conversion unit 341 calculates the one-trip average speed based on the calculation support table 503, the one-trip travel distance, and the one-trip travel time.
　このように、データ変換部３４１は、少なくとも１以上のＥＣＵから複数のＥＣＵデータを取得する。そして、データ変換部３４１は、複数のＥＣＵデータと算出支援テーブル５０３に基づいて、車算出情報を算出する。
　図６は、算出支援テーブル５０３が、“絶対速度”、“１ｔｒｉｐ平均速度”、及び“累積距離”の項目を有する場合を例示している。算出支援テーブル５０３は、図６に例示した項目以外の項目を含んでもよい。 As described above, the data conversion unit 341 acquires a plurality of ECU data from at least one or more ECUs. Then, the data conversion unit 341 calculates the vehicle calculation information based on the plurality of ECU data and the calculation support table 503.
FIG. 6 illustrates a case where the calculation support table 503 has items of “absolute speed”, “1 trip average speed”, and “cumulative distance”. The calculation support table 503 may include items other than the items illustrated in FIG.
　なお、図４は、アプリケーション要求５００が単位変換テーブル５０２と算出支援テーブル５０３とを含む場合を例示している。しかし、アプリケーション要求５００は、単位変換テーブル５０２と算出支援テーブル５０３の何れか一方のみを含んでもよい。
　図３に戻って、説明する。 FIG. 4 illustrates a case where the application request 500 includes a unit conversion table 502 and a calculation support table 503. However, the application request 500 may include only one of the unit conversion table 502 and the calculation support table 503.
Returning to FIG.
　要求受付部３２１は、通信部３１０からアプリケーション要求５００を受け付ける。要求解析部３２２は、アプリケーション要求５００を解析する。詳細には、要求解析部３２２は、アプリケーション要求ファイル５０１から上位アプリケーション１００ａの要求を検出する。例えば、要求解析部３２２は、上位アプリケーション１００ａが統計解析命令を指示していることを検出する。 The request receiving unit 321 receives the application request 500 from the communication unit 310. The request analysis unit 322 analyzes the application request 500. More specifically, the request analysis unit 322 detects a request from the upper-level application 100a from the application request file 501. For example, the request analysis unit 322 detects that the host application 100a has instructed a statistical analysis command.
　要求解析部３２２は、解析結果をモジュール管理部３２３に伝達する。モジュール管理部３２３は、解析結果と呼出モジュール管理リストに基づいて、ロードするモジュールを特定する。ロードされるモジュールなどは、モジュール管理リストで管理されている。 (4) The request analysis unit 322 transmits the analysis result to the module management unit 323. The module management unit 323 specifies a module to be loaded based on the analysis result and the calling module management list. Modules to be loaded are managed in a module management list.
　ここで、モジュール管理リストについて説明する。
　図７は、実施の形態１のモジュール管理リストの例を示す図である。モジュール管理リスト３７１は、記憶部３７０に格納される。モジュール管理リスト３７１は、大項目モジュール名、大項目モジュールＩＤ、詳細モジュール名、及びモジュールＩＤの項目を有する。 Here, the module management list will be described.
FIG. 7 is a diagram illustrating an example of a module management list according to the first embodiment. The module management list 371 is stored in the storage unit 370. The module management list 371 has items of a major item module name, a major item module ID, a detailed module name, and a module ID.
　大項目モジュール名の項目は、詳細モジュールの総称を示す。大項目モジュールＩＤは、大項目モジュールに対応するＩＤを示す。常にロードされるモジュールのＩＤには、大文字英字数字が割り当てられる。なお、数字は、１である。例えば、要求管理部３２０のＩＤは、Ａ１である。必要に応じてロードされるモジュールのＩＤには、大文字英字数字が割り当てられる。なお、数字は、２である。例えば、非定常変化検出部３５０のＩＤは、Ｃ２である。 (4) The major item module name indicates the generic name of the detailed module. The large item module ID indicates an ID corresponding to the large item module. The ID of a module that is always loaded is assigned an uppercase alphanumeric character. The number is 1. For example, the ID of the request management unit 320 is A1. Uppercase letters and numbers are assigned to the IDs of the modules that are loaded as required. The number is 2. For example, the ID of the unsteady change detection unit 350 is C2.
　詳細モジュール名の項目は、大項目モジュールに含まれるモジュールの名称を示す。モジュールＩＤの項目は、詳細モジュールに対応するＩＤを示す。数字が１の大項目モジュールに含まれるモジュールのＩＤには、当該大項目モジュールのＩＤの大文字英字と数字との間に大文字英字が配置される。例えば、要求受付部３２１のＩＤは、ＡＡ１である。数字が２の大項目モジュールに含まれるモジュールのＩＤには、当該大項目モジュールのＩＤの大文字英字と数字との間に小文字英字が配置される。例えば、統計解析処理部３５１のＩＤは、Ｃａ２である。
　上述したように、モジュール管理部３２３は、解析結果と呼出モジュール管理リストに基づいて、ロードするモジュールを特定する。 The item of the detailed module name indicates the name of a module included in the major item module. The item of the module ID indicates an ID corresponding to the detailed module. In the ID of the module included in the large item module having the numeral 1, an uppercase alphabetic character is arranged between the uppercase alphabetic character and the numeral of the ID of the large item module. For example, the ID of the request receiving unit 321 is AA1. In the ID of the module included in the large item module having the numeral 2, a lowercase alphabetic character is arranged between the uppercase alphabetic character and the numeral of the ID of the large item module. For example, the ID of the statistical analysis processing unit 351 is Ca2.
As described above, the module management unit 323 specifies a module to be loaded based on the analysis result and the calling module management list.
　ここで、呼出モジュール管理リストについて説明する。
　図８は、実施の形態１の呼出モジュール管理リストの例を示す図である。呼出モジュール管理リスト３７２は、記憶部３７０に格納される。呼出モジュール管理リスト３７２は、アプリケーション要求種別、呼出モジュールＩＤ、及び呼出モジュール名を有する。 Here, the calling module management list will be described.
FIG. 8 is a diagram illustrating an example of a call module management list according to the first embodiment. The calling module management list 372 is stored in the storage unit 370. The calling module management list 372 has an application request type, a calling module ID, and a calling module name.
　アプリケーション要求種別の項目は、モジュールを呼び出す条件を示す。呼出モジュールＩＤの項目は、モジュールＩＤを示す。呼出モジュール名の項目は、モジュールの名称を示す。
　例えば、アプリケーション要求ファイル５０１の“ｄｅｔｅｃｔＴｙｐｅ”に“０”以外が登録されていることを解析結果が示している場合、モジュール管理部３２３は、呼出モジュール管理リスト３７２に基づいて、ロード対象の非定常変化検出部３５０を特定する。 The item of the application request type indicates a condition for calling a module. The item of the calling module ID indicates a module ID. The item of the calling module name indicates the name of the module.
For example, when the analysis result indicates that a value other than “0” is registered in “detectType” of the application request file 501, the module management unit 323 determines the non-stationary state of the load target based on the calling module management list 372. The change detection unit 350 is specified.
　図３に戻って、説明する。
　モジュール管理部３２３は、特定したロード対象のモジュールをロードする。例えば、モジュール管理部３２３は、非定常変化検出部３５０をロードする。しかし、モジュール管理部３２３は、ロード対象のモジュールをどのタイミングでロードしてもよい。モジュール管理部３２３は、要求パケットを生成する。 Returning to FIG.
The module management unit 323 loads the specified load target module. For example, the module management unit 323 loads the unsteady change detection unit 350. However, the module management unit 323 may load the load target module at any timing. The module management unit 323 generates a request packet.
　ここで、要求パケットについて、説明する。
　図９は、実施の形態１の要求パケットのフォーマットの例を示す図である。要求パケット６００は、ＳＴＸ、ヘッダ、ペイロード、及びＥＴＸを含む。ＳＴＸは、要求パケット６００の始まりを示す。ヘッダは、モジュールが実行される順番を示す。例えば、ヘッダには、ＡＣ１、ＡＤ１が登録される。これは、モジュール管理部３２３の後、要求整形伝達部３２４が実行されることを示す。ペイロードには、アプリケーション要求５００が登録される。ＥＴＸは、要求パケット６００の終わりを示す。 Here, the request packet will be described.
FIG. 9 is a diagram illustrating an example of a format of a request packet according to the first embodiment. Request packet 600 includes an STX, a header, a payload, and an ETX. STX indicates the beginning of the request packet 600. The header indicates the order in which the modules will be executed. For example, AC1 and AD1 are registered in the header. This indicates that the request shaping transmission unit 324 is executed after the module management unit 323. The application request 500 is registered in the payload. ETX indicates the end of request packet 600.
　モジュール管理部３２３は、要求パケット６００のヘッダに従って、要求パケット６００を次のモジュールに送信する。
　図３に戻って、説明する。 The module management unit 323 transmits the request packet 600 to the next module according to the header of the request packet 600.
Returning to FIG.
　要求整形伝達部３２４は、要求パケット６００からペイロードのみを取得する。すなわち、要求整形伝達部３２４は、要求パケット６００からアプリケーション要求５００を取得する。要求整形伝達部３２４は、アプリケーション要求５００をＥＣＵ情報取得部３３１に伝達する。
　ＥＣＵ情報取得部３３１は、アプリケーション要求５００の［＿ＳＴＲＵＣＴＵＲＥ＿］を参照し、どのＥＣＵから何のデータを取得するのかを特定する。例えば、ＥＣＵ情報取得部３３１は、ｅｃｕ１.ｏｗｎＶｅｌｏｃｉｔｙに基づいて、ＥＣＵ４００からｏｗｎＶｅｌｏｃｉｔｙを取得することを特定する。 The request shaping transmission unit 324 acquires only the payload from the request packet 600. That is, the request shaping transmission unit 324 acquires the application request 500 from the request packet 600. The request shaping transmission unit 324 transmits the application request 500 to the ECU information acquisition unit 331.
The ECU information acquisition unit 331 refers to [_STRUCTURE_] of the application request 500 and specifies what data is acquired from which ECU. For example, the ECU information acquisition unit 331 specifies to acquire ownVelocity from the ECU 400 based on ecu1.ownVelocity.
　ＥＣＵ情報取得部３３１は、ＥＣＵから情報を取得する。なお、ＥＣＵ情報取得部３３１は、アプリケーション要求ファイル５０１の通知周期に基づいてＥＣＵから情報を取得する。
　ＥＣＵ情報取得部３３１は、アプリケーション要求ファイル５０１のデータ変換定義セクションに基づいて、ＥＣＵから取得した情報からＥＣＵデータの形式に変換する。例えば、ＥＣＵ情報取得部３３１は、ＥＣＵ４００から取得した情報の先頭から２ｂｙｔｅのうち、後ろから１ｂｙｔｅを取得する。これにより、ＥＣＵ情報取得部３３１は、ｏｗｎＶｅｌｏｃｉｔｙを取得できる。 The ECU information acquisition unit 331 acquires information from the ECU. Note that the ECU information acquisition unit 331 acquires information from the ECU based on the notification cycle of the application request file 501.
The ECU information obtaining unit 331 converts information obtained from the ECU into ECU data based on the data conversion definition section of the application request file 501. For example, the ECU information acquisition unit 331 acquires 1 byte from the rear of the 2 bytes from the beginning of the information acquired from the ECU 400. Thereby, the ECU information acquisition unit 331 can acquire ownVelocity.
　また、ＥＣＵ情報取得部３３１は、ＥＣＵから取得した情報から単位を取得する。例えば、ＥＣＵ情報取得部３３１は、ＥＣＵ４００から単位（例えば、［ｋｍ／ｈ］）を取得する。そして、ＥＣＵ情報取得部３３１は、上記処理により取得した情報と単位とを対応付ける。例えば、ＥＣＵ情報取得部３３１は、ｏｗｎＶｅｌｏｃｉｔｙと［ｋｍ／ｈ］とを対応付ける。このように、ＥＣＵ情報取得部３３１により対応付けられた情報は、ＥＣＵデータである。例えば、ｏｗｎＶｅｌｏｃｉｔｙと［ｋｍ／ｈ］とが対応付けられた情報が、ＥＣＵデータである。また、例えば、ｒｅｌａｔｉｖｅＶｅｌｏｃｉｔｙと［ｍ／ｓ］とが対応付けられた情報も、ＥＣＵデータである。 (4) The ECU information obtaining unit 331 obtains a unit from information obtained from the ECU. For example, the ECU information acquisition unit 331 acquires a unit (for example, [km / h]) from the ECU 400. Then, the ECU information acquisition unit 331 associates the information acquired by the above processing with the unit. For example, the ECU information acquisition unit 331 associates ownVelocity with [km / h]. Thus, the information associated by the ECU information acquisition unit 331 is ECU data. For example, information in which ownVelocity is associated with [km / h] is ECU data. Further, for example, information in which the relative velocity and [m / s] are associated with each other is also ECU data.
　このように、ＥＣＵ情報取得部３３１は、ＥＣＵからＥＣＵデータを取得できる。ＥＣＵ情報取得部３３１は、ＥＣＵデータをＥＣＵ情報伝達部３３２に伝達する。 Thus, the ECU information acquisition unit 331 can acquire ECU data from the ECU. The ECU information acquisition unit 331 transmits the ECU data to the ECU information transmission unit 332.
　ＥＣＵ情報伝達部３３２は、ＥＣＵデータをモジュール管理部３２３に伝達する。モジュール管理部３２３は、アプリケーション要求５００、ＥＣＵデータ、及び呼出モジュール管理リスト３７２に基づいて、変換部３４０をロードするか否かを判定する。例えば、モジュール管理部３２３は、上位アプリケーション１００ａが指定する単位とＥＣＵデータの単位とが異なることを特定する。モジュール管理部３２３は、呼出モジュール管理リスト３７２に基づいて、変換部３４０をロードすると判定する。モジュール管理部３２３は、変換部３４０をロードすると判定した場合、変換部３４０をロードする。しかし、モジュール管理部３２３は、どのタイミングで変換部３４０をロードしてもよい。 (4) The ECU information transmission unit 332 transmits the ECU data to the module management unit 323. The module management unit 323 determines whether to load the conversion unit 340 based on the application request 500, the ECU data, and the calling module management list 372. For example, the module management unit 323 specifies that the unit specified by the host application 100a is different from the unit of ECU data. The module management unit 323 determines to load the conversion unit 340 based on the calling module management list 372. When determining that the conversion unit 340 is to be loaded, the module management unit 323 loads the conversion unit 340. However, the module management unit 323 may load the conversion unit 340 at any timing.
　モジュール管理部３２３は、変換部３４０及び非定常変化検出部３５０をロードするか否かの情報をＥＣＵ情報伝達部３３２に送信する。ＥＣＵ情報伝達部３３２は、当該情報に基づいて、ＥＣＵパケットを生成する。 (4) The module management unit 323 transmits information on whether to load the conversion unit 340 and the unsteady change detection unit 350 to the ECU information transmission unit 332. The ECU information transmission unit 332 generates an ECU packet based on the information.
　ここで、ＥＣＵパケットについて、説明する。
　図１０は、実施の形態１のＥＣＵパケットのフォーマットの例を示す図である。ＥＣＵパケット６０１は、ＳＴＸ、ヘッダ、ペイロード、及びＥＴＸを含む。ＳＴＸは、ＥＣＵパケット６０１の始まりを示す。ＥＣＵ情報伝達部３３２は、変換部３４０及び非定常変化検出部３５０をロードするか否かの情報に基づいて、ヘッダを生成する。ヘッダは、モジュールが実行される順番を示す。例えば、ヘッダには、ＢＢ１、Ｂａ２、Ｃａ２、Ｃｂ２、及びＣＡ１が登録される。これは、ＥＣＵ情報伝達部３３２、データ変換部３４１、統計解析処理部３５１、登録部３５２、車算出情報受付部３６１の順番で処理が実行されることを示す。ペイロードには、ＥＣＵデータとアプリケーション要求５００が登録される。ＥＴＸは、ＥＣＵパケット６０１の終わりを示す。 Here, the ECU packet will be described.
FIG. 10 is a diagram illustrating an example of a format of an ECU packet according to the first embodiment. The ECU packet 601 includes an STX, a header, a payload, and ETX. STX indicates the start of the ECU packet 601. The ECU information transmission unit 332 generates a header based on information on whether to load the conversion unit 340 and the unsteady change detection unit 350. The header indicates the order in which the modules will be executed. For example, BB1, Ba2, Ca2, Cb2, and CA1 are registered in the header. This indicates that the processing is executed in the order of the ECU information transmission unit 332, the data conversion unit 341, the statistical analysis processing unit 351, the registration unit 352, and the vehicle calculation information reception unit 361. In the payload, the ECU data and the application request 500 are registered. ETX indicates the end of the ECU packet 601.
　ＥＣＵ情報伝達部３３２は、ＥＣＵパケット６０１のヘッダに従って、ＥＣＵパケット６０１を次のモジュールに送信する。
　図３に戻って、説明する。 The ECU information transmission unit 332 transmits the ECU packet 601 to the next module according to the header of the ECU packet 601.
Returning to FIG.
　データ変換部３４１は、上位アプリケーション１００ａが指定する単位とＥＣＵデータの単位とが異なる場合、単位変換テーブル５０２を用いて、単位を変換する。また、データ変換部３４１は、単位変換テーブル５０２を用いて、単位を換算すると表現してもよい。なお、変換又は換算された情報は、ＥＣＵデータと単位変換テーブル５０２に基づいて算出された情報であるため、車算出情報である。 When the unit specified by the host application 100a and the unit of the ECU data are different, the data conversion unit 341 converts the unit using the unit conversion table 502. Further, the data conversion unit 341 may express that the unit is converted using the unit conversion table 502. Since the converted or converted information is information calculated based on the ECU data and the unit conversion table 502, it is vehicle calculation information.
　また、データ変換部３４１は、アプリケーション要求５００が要求している情報がＥＣＵから取得できなかった場合、算出支援テーブル５０３とＥＣＵデータとに基づいて、アプリケーション要求５００が要求している情報を算出する。なお、算出された情報は、算出支援テーブル５０３とＥＣＵデータに基づいて算出された情報であるため、車算出情報である。 When the information requested by the application request 500 cannot be obtained from the ECU, the data conversion unit 341 calculates the information requested by the application request 500 based on the calculation support table 503 and the ECU data. . Note that the calculated information is vehicle calculation information because it is information calculated based on the calculation support table 503 and the ECU data.
　統計解析処理部３５１は、アプリケーション要求５００に統計解析命令がある場合、統計解析を実行する。登録部３５２は、解析結果をＥＣＵパケット６０１のペイロードに登録する。
　車算出情報受付部３６１は、ＥＣＵパケット６０１を受け付ける。車算出情報受付部３６１は、ＥＣＵパケット６０１からペイロードの情報を取得する。例えば、車算出情報受付部３６１は、ＥＣＵパケット６０１から車算出情報とＥＣＵデータを取得する。 When the application request 500 includes a statistical analysis command, the statistical analysis processing unit 351 performs a statistical analysis. The registration unit 352 registers the analysis result in the payload of the ECU packet 601.
The vehicle calculation information receiving unit 361 receives the ECU packet 601. The vehicle calculation information receiving unit 361 acquires payload information from the ECU packet 601. For example, the vehicle calculation information receiving unit 361 acquires vehicle calculation information and ECU data from the ECU packet 601.
　車算出情報送信部３６２は、通信部３１０を介して、ペイロードの情報を上位アプリケーション１００ａに送信する。
　これにより、上位アプリケーション１００ａは、アプリケーション要求５００で要求した情報を取得することができる。 The vehicle calculation information transmitting unit 362 transmits the information of the payload to the upper application 100a via the communication unit 310.
Thereby, the host application 100a can acquire the information requested by the application request 500.
　メイン処理部３８０は、要求管理部３２０、ＥＣＵ情報管理部３３０、及び車算出情報管理部３６０を呼び出すことができる。また、メイン処理部３８０は、要求管理部３２０、ＥＣＵ情報管理部３３０、及び車算出情報管理部３６０に指示することもできる。
　次に、車通信装置３００が実行する処理について、ステートチャートを用いて説明する。 The main processing unit 380 can call the request management unit 320, the ECU information management unit 330, and the vehicle calculation information management unit 360. The main processing unit 380 can also instruct the request management unit 320, the ECU information management unit 330, and the vehicle calculation information management unit 360.
Next, a process executed by the vehicle communication device 300 will be described using a state chart.
　図１１は、実施の形態１の車通信装置のステートチャート（その１）である。
　（ステップＳ１１）通信部３１０は、上位アプリケーション１００ａが送信したアプリケーション要求を受信する。要求受付部３２１は、通信部３１０からアプリケーション要求５００を受け付ける。 FIG. 11 is a state chart (No. 1) of the vehicle communication device according to the first embodiment.
(Step S11) The communication unit 310 receives the application request transmitted by the upper application 100a. The request receiving unit 321 receives the application request 500 from the communication unit 310.
　（ステップＳ１２）要求解析部３２２は、アプリケーション要求５００を解析する。要求解析部３２２は、解析結果をモジュール管理部３２３に伝達する。
　モジュール管理部３２３は、解析結果と呼出モジュール管理リストに基づいて、ロードするモジュールを特定する。
　モジュール管理部３２３は、要求パケット６００を生成する。モジュール管理部３２３は、要求パケット６００のヘッダに従って、要求パケット６００を次のモジュールに送信する。 (Step S12) The request analysis unit 322 analyzes the application request 500. The request analysis unit 322 transmits the analysis result to the module management unit 323.
The module management unit 323 specifies a module to be loaded based on the analysis result and the calling module management list.
The module management unit 323 generates the request packet 600. The module management unit 323 transmits the request packet 600 to the next module according to the header of the request packet 600.
　（ステップＳ１３）要求整形伝達部３２４は、要求パケット６００からアプリケーション要求５００を取得する。
　（ステップＳ１４）要求整形伝達部３２４は、アプリケーション要求５００をＥＣＵ情報取得部３３１に伝達する。
　これにより、ＥＣＵ情報取得部３３１は、アプリケーション要求５００に基づいてＥＣＵデータを取得できる。図１１は、ＥＣＵ４００が情報を送信する場合を例示している。 (Step S13) The request shaping transmission unit 324 acquires the application request 500 from the request packet 600.
(Step S14) The request shaping transmission unit 324 transmits the application request 500 to the ECU information acquisition unit 331.
Thus, the ECU information acquisition unit 331 can acquire the ECU data based on the application request 500. FIG. 11 illustrates a case where the ECU 400 transmits information.
　（ステップＳ１５）ＥＣＵ情報取得部３３１は、ＥＣＵデータを取得する。ＥＣＵデータを取得する方法は、上述した通りである。ＥＣＵ情報取得部３３１は、ＥＣＵデータをＥＣＵ情報伝達部３３２に伝達する。
　ＥＣＵ情報伝達部３３２は、ＥＣＵデータをモジュール管理部３２３に伝達する。 (Step S15) The ECU information acquisition unit 331 acquires ECU data. The method for acquiring the ECU data is as described above. The ECU information acquisition unit 331 transmits the ECU data to the ECU information transmission unit 332.
The ECU information transmission unit 332 transmits the ECU data to the module management unit 323.
　（ステップＳ１６）モジュール管理部３２３は、ＥＣＵデータと呼出モジュール管理リスト３７２とに基づいて、変換部３４０をロードするか否かを判定する。モジュール管理部３２３は、変換部３４０及び非定常変化検出部３５０をロードするか否かの情報をＥＣＵ情報伝達部３３２に送信する。
　ＥＣＵ情報伝達部３３２は、ＥＣＵパケット６０１を生成する。 (Step S16) The module management unit 323 determines whether to load the conversion unit 340 based on the ECU data and the calling module management list 372. The module management unit 323 transmits information on whether to load the conversion unit 340 and the unsteady change detection unit 350 to the ECU information transmission unit 332.
The ECU information transmission unit 332 generates an ECU packet 601.
　図１２は、実施の形態１の車通信装置のステートチャート（その２）である。
　（ステップＳ２１）モジュール管理部３２３は、ステップＳ１６の判定結果で変換部３４０をロードすると判定した場合、ステップＳ２２を実行する。モジュール管理部３２３は、ステップＳ１６の判定結果で変換部３４０をロードしないと判定した場合、ステップＳ２４を実行する。 FIG. 12 is a state chart (2) of the vehicle communication device according to the first embodiment.
(Step S21) If the module management unit 323 determines that the conversion unit 340 is to be loaded based on the determination result of step S16, it executes step S22. When the module management unit 323 determines that the conversion unit 340 is not loaded based on the determination result of step S16, the module management unit 323 executes step S24.
　（ステップＳ２２）モジュール管理部３２３は、変換部３４０をロードする。
　（ステップＳ２３）変換部３４０に含まれるデータ変換部３４１は、ＥＣＵパケット６０１に含まれるアプリケーション要求５００とＥＣＵデータとを取得する。データ変換部３４１は、上位アプリケーション１００ａが指定する単位とＥＣＵデータの単位とが異なる場合、単位変換テーブル５０２を用いて、単位を変換する。例えば、データ変換部３４１は、単位変換テーブル５０２を用いて、ＥＣＵパケット６０１に含まれるｏｗｎＶｅｌｏｃｉｔｙの単位を“ｋｍ／ｈ”から“ｍ／ｓ”に変換する。詳細には、データ変換部３４１は、ｏｗｎＶｅｌｏｃｉｔｙが示す値と“１０００／３６００”とを用いて、単位が“ｍ／ｓ”のｏｗｎＶｅｌｏｃｉｔｙを算出する。データ変換部３４１は、算出した情報（すなわち、車算出情報）をＥＣＵパケット６０１のペイロードに登録する。 (Step S22) The module management unit 323 loads the conversion unit 340.
(Step S23) The data conversion unit 341 included in the conversion unit 340 acquires the application request 500 and the ECU data included in the ECU packet 601. When the unit specified by the host application 100a and the unit of ECU data are different, the data conversion unit 341 converts the unit using the unit conversion table 502. For example, using the unit conversion table 502, the data conversion unit 341 converts the unit of ownVelocity included in the ECU packet 601 from "km / h" to "m / s". More specifically, the data conversion unit 341 calculates ownVelocity in units of “m / s” using the value indicated by ownVelocity and “1000/3600”. The data conversion unit 341 registers the calculated information (that is, vehicle calculation information) in the payload of the ECU packet 601.
　また、データ変換部３４１は、アプリケーション要求５００で要求している情報がペイロードに登録されていない場合、算出支援テーブル５０３とＥＣＵデータとに基づいて、当該情報を算出する。例えば、アプリケーション要求５００で要求している情報が、１ｔｒｉｐ平均速度とする。そして、１ｔｒｉｐ平均速度が、ペイロードに登録されていないものとする。また、ＥＣＵデータが、１ｔｒｉｐ走行距離と１ｔｒｉｐ走行時間であるものとする。データ変換部３４１は、算出支援テーブル５０３、１ｔｒｉｐ走行距離、及び１ｔｒｉｐ走行時間に基づいて、１ｔｒｉｐ平均速度を算出する。データ変換部３４１は、算出した情報（すなわち、車算出情報）をＥＣＵパケット６０１のペイロードに登録する。
　また、データ変換部３４１は、アプリケーション要求５００が要求する情報に基づいて、単位変換テーブル５０２と算出支援テーブル５０３との両方を用いてもよい。 When the information requested by the application request 500 is not registered in the payload, the data conversion unit 341 calculates the information based on the calculation support table 503 and the ECU data. For example, it is assumed that the information requested by the application request 500 is a 1-trip average speed. Then, it is assumed that the 1-trip average speed is not registered in the payload. It is also assumed that the ECU data is one trip traveling distance and one trip traveling time. The data conversion unit 341 calculates the one-trip average speed based on the calculation support table 503, the one-trip travel distance, and the one-trip travel time. The data conversion unit 341 registers the calculated information (that is, vehicle calculation information) in the payload of the ECU packet 601.
Further, the data conversion unit 341 may use both the unit conversion table 502 and the calculation support table 503 based on the information requested by the application request 500.
　（ステップＳ２４）モジュール管理部３２３は、アプリケーション要求５００に統計解析命令がある場合、ステップＳ２５を実行する。アプリケーション要求５００に統計解析命令がない場合、ステップＳ２８が実行される。
　（ステップＳ２５）モジュール管理部３２３は、非定常変化検出部３５０をロードする。 (Step S24) When there is a statistical analysis command in the application request 500, the module management unit 323 executes step S25. If there is no statistical analysis command in the application request 500, step S28 is executed.
(Step S25) The module management unit 323 loads the unsteady change detection unit 350.
　（ステップＳ２６）非定常変化検出部３５０の統計解析処理部３５１は、統計解析を実行する。
　詳細に説明する。統計解析処理部３５１は、ＥＣＵデータの過去の履歴に基づいて、今回取得したＥＣＵデータが異常値であるか否かを解析する。例えば、統計解析処理部３５１は、“ｄｅｔｅｃｔＴｙｐｅ”に３が設定されている場合、ＥＣＵデータ（例えば、相対速度）の過去の履歴に基づいて平均値を算出する。統計解析処理部３５１は、今回取得したＥＣＵデータが平均値よりも大きい場合、今回取得したＥＣＵデータを異常値と解析してもよい。 (Step S26) The statistical analysis processing unit 351 of the unsteady change detection unit 350 performs a statistical analysis.
This will be described in detail. The statistical analysis processing unit 351 analyzes whether or not the ECU data acquired this time is an abnormal value based on the past history of the ECU data. For example, when “detectType” is set to 3, the statistical analysis processing unit 351 calculates an average value based on a past history of ECU data (for example, relative speed). When the ECU data acquired this time is larger than the average value, the statistical analysis processing unit 351 may analyze the ECU data acquired this time as an abnormal value.
　また、統計解析処理部３５１は、車算出情報の過去の履歴に基づいて、ステップＳ２３で算出された車算出情報が異常値であるか否かを解析する。例えば、統計解析処理部３５１は、“ｄｅｔｅｃｔＴｙｐｅ”に３が設定されている場合、自車速度（単位は、ｍ／ｓ）の過去の履歴に基づいて平均値を算出する。統計解析処理部３５１は、ステップＳ２３で算出された自車速度が平均値よりも大きい場合、ステップＳ２３で算出された自車速度を異常値と解析してもよい。また、例えば、統計解析処理部３５１は、“ｄｅｔｅｃｔＴｙｐｅ”に３が設定されている場合、１トリップ平均速度の過去の履歴に基づいて平均値を算出する。統計解析処理部３５１は、ステップＳ２３で算出された１トリップ平均速度が平均値よりも大きい場合、ステップＳ２３で算出された１トリップ平均速度を異常値と解析してもよい。 (4) The statistical analysis processing unit 351 analyzes whether or not the vehicle calculation information calculated in step S23 is an abnormal value based on the past history of the vehicle calculation information. For example, when “detectType” is set to 3, the statistical analysis processing unit 351 calculates an average value based on the past history of the own vehicle speed (unit: m / s). When the own vehicle speed calculated in step S23 is larger than the average value, the statistical analysis processing unit 351 may analyze the own vehicle speed calculated in step S23 as an abnormal value. Further, for example, when “detectType” is set to 3, the statistical analysis processing unit 351 calculates an average value based on the past history of one trip average speed. If the average one-trip speed calculated in step S23 is larger than the average value, the statistical analysis processing unit 351 may analyze the average one-trip speed calculated in step S23 as an abnormal value.
　また、例えば、統計解析処理部３５１は、アプリケーション要求ファイル５０１の“ｄｅｔｅｃｔＴｙｐｅ”に２が設定されている場合、時間微分を実行する。統計解析処理部３５１は、時間微分値が所定の閾値を超えている場合、異常値と判定してもよい。 Further, for example, when “detectType” of the application request file 501 is set to 2, the statistical analysis processing unit 351 performs time differentiation. If the time differential value exceeds a predetermined threshold, the statistical analysis processing unit 351 may determine that the value is an abnormal value.
　（ステップＳ２７）非定常変化検出部３５０の登録部３５２は、解析結果をＥＣＵパケット６０１のペイロードに登録する。
　（ステップＳ２８）車算出情報受付部３６１は、ＥＣＵパケット６０１を受け付ける。車算出情報受付部３６１は、ＥＣＵパケット６０１からペイロードの情報を取得する。車算出情報受付部３６１は、ペイロードに車算出情報が登録されている場合、車算出情報を取得できる。 (Step S27) The registration unit 352 of the unsteady change detection unit 350 registers the analysis result in the payload of the ECU packet 601.
(Step S28) The vehicle calculation information receiving unit 361 receives the ECU packet 601. The vehicle calculation information receiving unit 361 acquires payload information from the ECU packet 601. When the vehicle calculation information is registered in the payload, the vehicle calculation information receiving unit 361 can acquire the vehicle calculation information.
　（ステップＳ２９）車算出情報送信部３６２は、通信部３１０を介して、ペイロードの情報を上位アプリケーション１００ａに送信する。車算出情報送信部３６２は、ペイロードに車算出情報が登録されている場合、車算出情報を送信できる。また、車算出情報送信部３６２は、ペイロードに解析結果が登録されている場合、解析結果を送信できる。 (Step S29) The vehicle calculation information transmitting unit 362 transmits the information of the payload to the upper application 100a via the communication unit 310. When the vehicle calculation information is registered in the payload, the vehicle calculation information transmitting unit 362 can transmit the vehicle calculation information. When the analysis result is registered in the payload, the vehicle calculation information transmitting unit 362 can transmit the analysis result.
　これにより、上位アプリケーション１００ａは、アプリケーション要求５００で要求した情報を取得することができる。例えば、上位アプリケーション１００ａは、アプリケーション要求５００で要求したＥＣＵデータを取得することができる。また、例えば、上位アプリケーション１００ａは、アプリケーション要求５００で要求した車算出情報を取得することができる。
　ここで、モジュール管理部３２３は、非定常変化検出部３５０をロードするか否かの判定をステップＳ１６で実行してもよい。 Thereby, the host application 100a can acquire the information requested by the application request 500. For example, the host application 100a can acquire the ECU data requested by the application request 500. Further, for example, the host application 100a can acquire the vehicle calculation information requested by the application request 500.
Here, the module management unit 323 may determine in step S16 whether to load the unsteady change detection unit 350.
　図１３は、実施の形態１のクラウドサーバと車載装置との間で実行される処理の具体例を示す図である。クラウドサーバ１００又は上位アプリケーション１００ａは、アプリケーション要求５００を車載装置２００に送信する（ステップＳ１０１）。
　アプリケーション要求５００は、単位変換テーブル５０２と算出支援テーブル５０３を含む。例えば、アプリケーション要求５００は、ｏｗｎＶｅｌｏｃｉｔｙを含む。ｏｗｎＶｅｌｏｃｉｔｙの単位は、“ｍ／ｓ”である。また、例えば、アプリケーション要求５００は、ａｂｓｌｔＶｅｌｏｃｉｔｙを含む。 FIG. 13 is a diagram illustrating a specific example of a process executed between the cloud server and the in-vehicle device according to the first embodiment. The cloud server 100 or the host application 100a transmits the application request 500 to the in-vehicle device 200 (Step S101).
The application request 500 includes a unit conversion table 502 and a calculation support table 503. For example, the application request 500 includes ownVelocity. The unit of ownVelocity is "m / s". Also, for example, the application request 500 includes absltVelocity.
　また、アプリケーション要求５００は、ｏｗｎＶｅｌｏｃｉｔｙをＥＣＵ４００から取得することを示す情報（すなわち、ｅｃｕ１）を含む。アプリケーション要求５００は、ｒｅｌａｔｉｖｅＶｅｌｏｃｉｔｙ、１ｔｒｉｐＤｉｓｔａｎｃｅ、及び１ｔｒｉｐＴｉｍｅをＥＣＵ４０２から取得することを示す情報（すなわち、ｅｃｕ３）を含む。なお、図１３は、ｅｃｕ１とｅｃｕ３を省略している。 The application request 500 also includes information indicating that ownVelocity is to be obtained from the ECU 400 (ie, ecu1). The application request 500 includes information indicating that relativeVelocity, 1tripDistance, and 1tripTime are to be obtained from the ECU 402 (ie, ecu3). FIG. 13 omits ecu1 and ecu3.
　車通信装置３００は、ｏｗｎＶｅｌｏｃｉｔｙをＥＣＵ４００から取得する。当該ｏｗｎＶｅｌｏｃｉｔｙの単位は、“ｋｍ／ｈ”である。車通信装置３００は、ｒｅｌａｔｉｖｅＶｅｌｏｃｉｔｙ、１ｔｒｉｐＤｉｓｔａｎｃｅ、及び１ｔｒｉｐＴｉｍｅをＥＣＵ４０２から取得する。 The vehicle communication device 300 acquires ownVelocity from the ECU 400. The unit of the own Velocity is “km / h”. The vehicle communication device 300 acquires from the ECU 402 the relative Velocity, 1 trip Distance, and 1 trip Time.
　アプリケーション要求５００が指定するｏｗｎＶｅｌｏｃｉｔｙの単位は、“ｍ／ｓ”である。ＥＣＵ４００から取得したｏｗｎＶｅｌｏｃｉｔｙの単位は、“ｋｍ／ｈ”である。そこで、車通信装置３００は、単位変換テーブル５０２を用いて、ＥＣＵ４００から取得したｏｗｎＶｅｌｏｃｉｔｙの単位を“ｋｍ／ｈ”から“ｍ／ｓ”に変換する。 The unit of ownVelocity specified by the application request 500 is “m / s”. The unit of ownVelocity acquired from the ECU 400 is “km / h”. Therefore, the vehicle communication device 300 uses the unit conversion table 502 to convert the unit of ownVelocity acquired from the ECU 400 from “km / h” to “m / s”.
　ＥＣＵ４００，４０２から取得したＥＣＵデータには、ａｂｓｌｔＶｅｌｏｃｉｔｙ及びａｖｒｇＶｅｌｏｃｉｔｙが含まれていない。そこで、車通信装置３００は、算出支援テーブル５０３を用いて、ａｂｓｌｔＶｅｌｏｃｉｔｙ及びａｖｒｇＶｅｌｏｃｉｔｙを算出する。算出されたａｂｓｌｔＶｅｌｏｃｉｔｙ及びａｖｒｇＶｅｌｏｃｉｔｙの単位は、“ｍ／ｓ”である。アプリケーション要求５００が指定するａｂｓｌｔＶｅｌｏｃｉｔｙ及びａｖｒｇＶｅｌｏｃｉｔｙの単位は、“ｋｍ／ｈ”である。そこで、車通信装置３００は、単位変換テーブル５０２を用いて、算出したａｂｓｌｔＶｅｌｏｃｉｔｙの単位を“ｍ／ｓ”から“ｋｍ／ｈ”に変換する。車通信装置３００は、単位変換テーブル５０２を用いて、算出したａｖｒｇＶｅｌｏｃｉｔｙの単位を“ｍ／ｓ”から“ｋｍ／ｈ”に変換する。このように、車通信装置３００は、複数のＥＣＵデータ、単位変換テーブル５０２、及び算出支援テーブル５０３に基づいて、予め決められた単位の車算出情報を算出することができる。 ＥＣＵ The ECU data acquired from the ECUs 400 and 402 does not include absltVelocity and avrgVelocity. Therefore, the vehicle communication device 300 uses the calculation support table 503 to calculate absltVelocity and avrgVelocity. The unit of the calculated absltVelocity and avrgVelocity is “m / s”. The unit of absltVelocity and avrgVelocity specified by the application request 500 is “km / h”. Therefore, the vehicle communication device 300 uses the unit conversion table 502 to convert the calculated unit of the absltVelocity from “m / s” to “km / h”. The vehicle communication device 300 uses the unit conversion table 502 to convert the unit of the calculated avrgVelocity from “m / s” to “km / h”. As described above, the vehicle communication device 300 can calculate vehicle calculation information in a predetermined unit based on the plurality of ECU data, the unit conversion table 502, and the calculation support table 503.
　車通信装置３００は、クラウドサーバ１００又は上位アプリケーション１００ａに情報７００を送信する（ステップＳ１０２）。情報７００には、ＥＣＵ４００，４０２から取得したＥＣＵデータ（例えば、ｒｅｌａｔｉｖｅＶｅｌｏｃｉｔｙ）が含まれる。また、情報７００には、車算出情報が含まれる。例えば、車算出情報は、ｏｗｎＶｅｌｏｃｉｔｙ（単位は、ｍ／ｓ）、ａｂｓｌｔＶｅｌｏｃｉｔｙ（単位は、ｋｍ／ｈ）、及びａｖｒｇＶｅｌｏｃｉｔｙ（単位は、ｋｍ／ｈ）である。 The vehicle communication device 300 transmits the information 700 to the cloud server 100 or the upper application 100a (Step S102). The information 700 includes ECU data (for example, relative velocity) acquired from the ECUs 400 and 402. The information 700 includes vehicle calculation information. For example, the vehicle calculation information is ownVelocity (unit: m / s), absltVelocity (unit: km / h), and avrgVelocity (unit: km / h).
　実施の形態１によれば、車通信装置３００は、単位変換テーブル５０２と算出支援テーブル５０３を含むアプリケーション要求５００を受信する。車通信装置３００は、アプリケーション要求５００に単位変換テーブル５０２が含まれていることで、ＥＣＵデータの単位を変換できる。また、車通信装置３００は、アプリケーション要求５００に算出支援テーブル５０３が含まれていることで、新たなデータを生成することができる。 According to the first embodiment, the vehicle communication device 300 receives the application request 500 including the unit conversion table 502 and the calculation support table 503. The vehicle communication device 300 can convert the unit of the ECU data by including the unit conversion table 502 in the application request 500. In addition, the vehicle communication device 300 can generate new data by including the calculation support table 503 in the application request 500.
　このように、アプリケーション要求５００に単位変換テーブル５０２と算出支援テーブル５０３の少なくとも一方が含まれているため、車通信装置３００は、様々な種類のＥＣＵデータを変換するための変換テーブルを格納しなくてもよい。車通信装置３００は、変換テーブルを格納しなくてよいので、複雑な処理により変換テーブルを作成しなくてよい。 As described above, since the application request 500 includes at least one of the unit conversion table 502 and the calculation support table 503, the vehicle communication device 300 does not store a conversion table for converting various types of ECU data. You may. Since the vehicle communication device 300 does not need to store the conversion table, it is not necessary to create the conversion table by complicated processing.
　また、クラウドサーバ１００又は上位アプリケーション１００ａは、取得したい情報に合わせて、単位変換テーブル５０２と算出支援テーブル５０３の少なくとも一方をアプリケーション要求５００に含めればよい。よって、通信システムは、変換テーブルを作成せず、単位変換テーブル５０２と算出支援テーブル５０３の少なくとも一方をアプリケーション要求５００に含めればよいので、容易に車算出情報を取得することができる。 The cloud server 100 or the higher-level application 100a may include at least one of the unit conversion table 502 and the calculation support table 503 in the application request 500 in accordance with the information to be acquired. Therefore, the communication system does not create the conversion table and only needs to include at least one of the unit conversion table 502 and the calculation support table 503 in the application request 500, so that the vehicle calculation information can be easily obtained.
　また、クラウドサーバ１００又は上位アプリケーション１００ａは、ＥＣＵデータの統計解析命令を車通信装置３００に送信することで、ＥＣＵデータを統計解析した解析結果を取得できる。また、クラウドサーバ１００又は上位アプリケーション１００ａは、車算出情報の統計解析命令を車通信装置３００に送信することで、車算出情報を統計解析した解析結果を取得できる。 The cloud server 100 or the higher-level application 100a can obtain a result of statistically analyzing ECU data by transmitting a statistical analysis command of ECU data to the vehicle communication device 300. In addition, the cloud server 100 or the upper application 100a can obtain an analysis result obtained by statistically analyzing the vehicle calculation information by transmitting a statistical analysis command of the vehicle calculation information to the vehicle communication device 300.
　車通信装置３００は、今回取得したＥＣＵデータ又は今回算出した車算出情報が異常値であることを解析結果が示している場合、アプリケーション要求５００に含まれている通知周期に従わずに、速やかに解析結果をクラウドサーバ１００又は上位アプリケーション１００ａに送信してもよい。 If the analysis result indicates that the ECU data obtained this time or the vehicle calculation information calculated this time is an abnormal value, the vehicle communication device 300 promptly does not follow the notification cycle included in the application request 500. The analysis result may be transmitted to the cloud server 100 or the host application 100a.
実施の形態２．
　次に、実施の形態２を説明する。実施の形態１と相違する事項を主に説明し、実施の形態１と共通する事項の説明を省略する。実施の形態２は、図１～６，９～１２を参照する。
　実施の形態１は、車通信装置３００が１つのアプリケーション要求を受信する場合を説明した。実施の形態２は、車通信装置３００が複数のアプリケーション要求を受信する場合を説明する。 Embodiment 2 FIG.
Next, a second embodiment will be described. Items that are different from the first embodiment will be mainly described, and descriptions of items that are common to the first embodiment will be omitted. Embodiment 2 refers to FIGS. 1 to 6 and 9 to 12.
Embodiment 1 has described the case where the vehicle communication device 300 receives one application request. Embodiment 2 describes a case where vehicle communication device 300 receives a plurality of application requests.
　図１４は、実施の形態２の車通信装置の構成を示す機能ブロック図である。車通信装置３００ａは、要求集約部３９０を有する。要求集約部３９０は、共通データ解析部３９１と通知周期解析部３９２とを有する。 FIG. 14 is a functional block diagram showing the configuration of the vehicle communication device according to the second embodiment. The vehicle communication device 300a includes a request aggregation unit 390. The request aggregating unit 390 includes a common data analyzing unit 391 and a notification cycle analyzing unit 392.
　要求集約部３９０、共通データ解析部３９１、及び通知周期解析部３９２の一部又は全部は、プロセッサ３０１によって実現してもよい。要求集約部３９０、共通データ解析部３９１、及び通知周期解析部３９２の一部又は全部は、プロセッサ３０１が実行するプログラムのモジュールとして実現してもよい。 Part or all of the request aggregation unit 390, the common data analysis unit 391, and the notification cycle analysis unit 392 may be realized by the processor 301. Part or all of the request aggregation unit 390, the common data analysis unit 391, and the notification cycle analysis unit 392 may be realized as a module of a program executed by the processor 301.
　以下、要求集約部３９０、共通データ解析部３９１、及び通知周期解析部３９２は、プロセッサ３０１が実行するプログラムのモジュールとして説明する。これらのモジュールは、プロセッサ３０１が実行するミドルウェアで実現してもよい。
　図３に示される構成と同じ又は対応する図１４の構成は、図３に示される符号と同じ符号を付している。また、図１４は、メイン処理部３８０を省略している。
　共通データ解析部３９１及び通知周期解析部３９２の機能については、後で詳細に説明する。 Hereinafter, the request aggregation section 390, the common data analysis section 391, and the notification cycle analysis section 392 will be described as modules of a program executed by the processor 301. These modules may be realized by middleware executed by the processor 301.
14 which are the same as or correspond to those shown in FIG. 3 are denoted by the same reference numerals as those shown in FIG. FIG. 14 omits the main processing unit 380.
The functions of the common data analysis unit 391 and the notification cycle analysis unit 392 will be described later in detail.
　図１５は、実施の形態２のモジュール管理リストの例を示す図である。モジュール管理リスト３７１ａは、記憶部３７０に格納される。
　例えば、モジュール管理リスト３７１ａには、要求集約部３９０の大項目モジュールＩＤがＡ２であることが登録される。例えば、モジュール管理リスト３７１ａには、共通データ解析部３９１のモジュールＩＤがＡａ２であることが登録される。例えば、モジュール管理リスト３７１ａには、通知周期解析部３９２のモジュールＩＤがＡｂ２であることが登録される。 FIG. 15 is a diagram illustrating an example of a module management list according to the second embodiment. The module management list 371a is stored in the storage unit 370.
For example, the module management list 371a registers that the large item module ID of the request aggregating unit 390 is A2. For example, the module management list 371a registers that the module ID of the common data analysis unit 391 is Aa2. For example, the module ID of the notification cycle analysis unit 392 is registered as Ab2 in the module management list 371a.
　図１６は、実施の形態２の呼出モジュール管理リストの例を示す図である。呼出モジュール管理リスト３７２ａは、記憶部３７０に格納される。
　例えば、呼出モジュール管理リスト３７２ａには、要求集約部３９０を呼び出す条件が登録される。 FIG. 16 is a diagram illustrating an example of a call module management list according to the second embodiment. The calling module management list 372a is stored in the storage unit 370.
For example, a condition for calling the request aggregating unit 390 is registered in the calling module management list 372a.
　図１７は、実施の形態２の車通信装置のステートチャート（その１）である。図１７は、ステップＳ１１ａ，１２ａ～１２ｅ，１３ａ，１４ａが実行される点が、図１１と異なる。そのため、図１７では、ステップＳ１１ａ，１２ａ～１２ｅ，１３ａ，１４ａを説明する。図１７における他のステップについては、図１１のステップ番号と同じ番号を付することによって、処理の説明を省略する。また、図１７の後は、図１２の処理が実行される。 FIG. 17 is a state chart (1) of the vehicle communication device according to the second embodiment. FIG. 17 differs from FIG. 11 in that steps S11a, 12a to 12e, 13a, and 14a are executed. Therefore, in FIG. 17, steps S11a, 12a to 12e, 13a, and 14a will be described. The other steps in FIG. 17 are given the same numbers as the step numbers in FIG. 11, and the description of the processing is omitted. After FIG. 17, the processing in FIG. 12 is executed.
　（ステップＳ１１ａ）通信部３１０は、複数のアプリケーション要求を受信する。例えば、通信部３１０は、複数の上位アプリケーションが同時に送信した複数のアプリケーション要求を受信する。また、例えば、通信部３１０は、１つの上位アプリケーションが送信したアプリケーション要求を受信した後、所定時間待機する。通信部３１０は、所定時間内に他のアプリケーション要求を受信する。通信部３１０が複数のアプリケーション要求を受信する場合については、上記の例に限らない。
　要求受付部３２１は、通信部３１０から複数のアプリケーション要求を受け付ける。なお、図１７は、上位アプリケーション１００ａがアプリケーション要求を送信する場合を例示している。 (Step S11a) The communication unit 310 receives a plurality of application requests. For example, the communication unit 310 receives a plurality of application requests transmitted by a plurality of higher-level applications simultaneously. In addition, for example, the communication unit 310 waits for a predetermined time after receiving an application request transmitted by one higher-level application. The communication unit 310 receives another application request within a predetermined time. The case where the communication unit 310 receives a plurality of application requests is not limited to the above example.
The request receiving unit 321 receives a plurality of application requests from the communication unit 310. FIG. 17 illustrates a case where the upper application 100a transmits an application request.
　（ステップＳ１２ａ）要求解析部３２２は、複数のアプリケーション要求を解析する。例えば、要求解析部３２２は、上位アプリケーション１００ａが送信したアプリケーション要求がｏｗｎＶｅｌｏｃｉｔｙを要求していることを検出する。また、要求解析部３２２は、上位アプリケーション１０２ａが送信したアプリケーション要求がｏｗｎＶｅｌｏｃｉｔｙを要求していることを検出する。要求解析部３２２は、複数のアプリケーション要求が共通のデータを要求していることを検出する。 (Step S12a) The request analysis unit 322 analyzes a plurality of application requests. For example, the request analysis unit 322 detects that the application request transmitted by the higher-level application 100a requests ownVelocity. Further, the request analysis unit 322 detects that the application request transmitted by the upper-level application 102a requests ownVelocity. The request analysis unit 322 detects that a plurality of application requests request common data.
　このように、要求解析部３２２は、複数のアプリケーション要求が共通のデータを要求しているか否かを解析する。要求解析部３２２は、解析結果をモジュール管理部３２３に伝達する。 As described above, the request analysis unit 322 analyzes whether a plurality of application requests request common data. The request analysis unit 322 transmits the analysis result to the module management unit 323.
　（ステップＳ１２ｂ）モジュール管理部３２３は、共通のデータを要求していることを解析結果が示している場合、ステップＳ１２ｃを実行する。モジュール管理部３２３は、共通のデータを要求していないことを解析結果が示している場合、要求パケット６００を生成する。要求パケット６００のペイロードには、複数のアプリケーション要求が含まれる。 (Step S12b) If the analysis result indicates that common data is requested, the module management unit 323 executes Step S12c. When the analysis result indicates that the common data is not requested, the module management unit 323 generates the request packet 600. The payload of the request packet 600 includes a plurality of application requests.
　（ステップＳ１２ｃ）モジュール管理部３２３は、呼出モジュール管理リスト３７２ａに基づいて、要求集約部３９０をロードする。モジュール管理部３２３は、要求パケット６００を生成する。要求パケット６００のヘッダには、ＡＣ１、Ａａ２、Ａｂ２、ＡＤ１が登録される。これは、モジュール管理部３２３の後、共通データ解析部３９１、通知周期解析部３９２、要求整形伝達部３２４が実行されることを示す。また、要求パケット６００のペイロードには、複数のアプリケーション要求が含まれる。
　モジュール管理部３２３は、要求パケット６００のヘッダに従って、要求パケット６００を次のモジュールに送信する。 (Step S12c) The module management unit 323 loads the request aggregation unit 390 based on the calling module management list 372a. The module management unit 323 generates the request packet 600. AC1, Aa2, Ab2, and AD1 are registered in the header of the request packet 600. This indicates that after the module management unit 323, the common data analysis unit 391, the notification cycle analysis unit 392, and the request shaping transmission unit 324 are executed. The payload of the request packet 600 includes a plurality of application requests.
The module management unit 323 transmits the request packet 600 to the next module according to the header of the request packet 600.
　（ステップＳ１２ｄ）共通データ解析部３９１は、要求パケット６００のペイロードを参照し、複数のアプリケーション要求のそれぞれが要求している共通のデータを検出する。例えば、共通のデータは、ｏｗｎＶｅｌｏｃｉｔｙである。 (Step S12d) The common data analysis unit 391 refers to the payload of the request packet 600 and detects common data requested by each of the plurality of application requests. For example, common data is ownVelocity.
　（ステップＳ１２ｅ）通知周期解析部３９２は、複数のアプリケーション要求のそれぞれに含まれている通知周期に基づいて、通知周期の最大公約数を算出する。例えば、上位アプリケーション１００ａが送信したアプリケーション要求に含まれている通知周期は、５０００［ｍｓｅｃ］（すなわち、５秒）である。上位アプリケーション１０２ａが送信したアプリケーション要求に含まれている通知周期は、１００００［ｍｓｅｃ］（すなわち、１０秒）である。通知周期解析部３９２は、５秒と１０秒とに基づいて、最大公約数である５秒を算出する。
　通知周期解析部３９２は、要求パケット６００のペイロードに最大公約数を格納する。 (Step S12e) The notification cycle analyzer 392 calculates the greatest common divisor of the notification cycle based on the notification cycle included in each of the plurality of application requests. For example, the notification cycle included in the application request transmitted by the higher-level application 100a is 5000 [msec] (that is, 5 seconds). The notification cycle included in the application request transmitted by the upper application 102a is 10,000 [msec] (that is, 10 seconds). The notification cycle analysis unit 392 calculates 5 seconds, which is the greatest common divisor, based on 5 seconds and 10 seconds.
The notification cycle analyzer 392 stores the greatest common divisor in the payload of the request packet 600.
　（ステップＳ１３ａ）要求整形伝達部３２４は、要求パケット６００からペイロードの情報を取得する。例えば、要求整形伝達部３２４は、複数のアプリケーション要求を取得する。また、要求整形伝達部３２４は、ペイロードに最大公約数が含まれている場合、最大公約数を取得する。 (Step S13a) The request shaping / transmission unit 324 acquires payload information from the request packet 600. For example, the request shaping transmission unit 324 acquires a plurality of application requests. When the payload includes the greatest common divisor, the request shaping transmission unit 324 acquires the greatest common divisor.
　（ステップＳ１４ａ）要求整形伝達部３２４は、ペイロードの情報をＥＣＵ情報取得部３３１に伝達する。
　これにより、ＥＣＵ情報取得部３３１は、複数のアプリケーション要求に基づいてＥＣＵデータを取得できる。なお、図１７は、ＥＣＵ４００が情報を送信する場合を例示している。 (Step S14a) The request shaping transmission unit 324 transmits the information of the payload to the ECU information acquisition unit 331.
Thereby, the ECU information acquisition unit 331 can acquire ECU data based on a plurality of application requests. FIG. 17 illustrates a case where the ECU 400 transmits information.
　ここで、ＥＣＵ情報取得部３３１は、ペイロードに最大公約数が含まれている場合、最大公約数に基づいて、複数のアプリケーション要求が要求する共通のデータをＥＣＵから取得する。例えば、最大公約数を５秒とする。共通のデータをｏｗｎＶｅｌｏｃｉｔｙする。ｏｗｎＶｅｌｏｃｉｔｙを記憶するＥＣＵをＥＣＵ４００とする。ＥＣＵ情報取得部３３１は、５秒周期で、ｏｗｎＶｅｌｏｃｉｔｙをＥＣＵ４００から取得する。 Here, if the greatest common divisor is included in the payload, the ECU information acquisition unit 331 acquires common data required by a plurality of application requests from the ECU based on the greatest common divisor. For example, the greatest common divisor is set to 5 seconds. OwnVelocity of common data. The ECU that stores ownVelocity is assumed to be ECU 400. The ECU information obtaining unit 331 obtains ownVelocity from the ECU 400 in a 5-second cycle.
　ＥＣＵ情報伝達部３３２は、ステップＳ１６でＥＣＵパケットを生成する。ＥＣＵ情報伝達部３３２は、複数のアプリケーション要求のそれぞれについてＥＣＵパケットを生成する。例えば、ＥＣＵ情報伝達部３３２は、上位アプリケーション１００ａが送信したアプリケーション要求を含むＥＣＵパケットと上位アプリケーション１０２ａが送信したアプリケーション要求を含むＥＣＵパケットとを生成する。また、ＥＣＵ情報伝達部３３２は、アプリケーション要求に含まれている通知周期に基づいて、ＥＣＵパケットを生成してもよい。例えば、上位アプリケーション１００ａが送信したアプリケーション要求には、５秒が登録されている。そのため、ＥＣＵ情報伝達部３３２は、５秒周期で、ＥＣＵパケットのペイロードの情報を上位アプリケーション１００ａに送信できるようにＥＣＵパケットを生成する。また、例えば、上位アプリケーション１０２ａが送信したアプリケーション要求には、１０秒が登録されている。そのため、ＥＣＵ情報伝達部３３２は、１０秒周期で、ＥＣＵパケットのペイロードの情報を上位アプリケーション１０２ａに送信できるようにＥＣＵパケットを生成する。 The ECU information transmission unit 332 generates an ECU packet in step S16. The ECU information transmission unit 332 generates an ECU packet for each of the plurality of application requests. For example, the ECU information transmission unit 332 generates an ECU packet including the application request transmitted by the upper application 100a and an ECU packet including the application request transmitted by the higher application 102a. Further, the ECU information transmission unit 332 may generate an ECU packet based on the notification cycle included in the application request. For example, 5 seconds are registered in the application request transmitted by the upper application 100a. Therefore, the ECU information transmission unit 332 generates the ECU packet so that the information of the payload of the ECU packet can be transmitted to the upper application 100a at a cycle of 5 seconds. In addition, for example, 10 seconds is registered in the application request transmitted by the higher-level application 102a. Therefore, the ECU information transmission unit 332 generates the ECU packet so that the information of the payload of the ECU packet can be transmitted to the upper application 102a at a cycle of 10 seconds.
　車通信装置３００ａは、複数のＥＣＵパケットのそれぞれに対して、ステップＳ２１～２９を実行する。例えば、車通信装置３００ａは、上位アプリケーション１００ａが送信したアプリケーション要求を含むＥＣＵパケットに対して、ステップＳ２１～２９を実行する。また、例えば、車通信装置３００ａは、上位アプリケーション１０２ａが送信したアプリケーション要求を含むＥＣＵパケットに対して、ステップＳ２１～２９を実行する。 The vehicle communication device 300a executes steps S21 to S29 for each of the plurality of ECU packets. For example, the vehicle communication device 300a executes steps S21 to S29 on the ECU packet including the application request transmitted by the upper application 100a. Further, for example, the vehicle communication device 300a executes steps S21 to S29 on the ECU packet including the application request transmitted by the upper application 102a.
　このように、車通信装置３００ａは、複数のアプリケーション要求を受信する。車通信装置３００ａは、複数のアプリケーション要求のそれぞれに含まれている取得指示の対象であるＥＣＵデータが共通の場合、複数のアプリケーション要求のそれぞれに含まれている通知周期に基づいて、最大公約数を算出する。車通信装置３００ａは、最大公約数に基づいて、共通のＥＣＵデータを取得する。 車 Thus, the vehicle communication device 300a receives a plurality of application requests. When the ECU data that is the target of the acquisition instruction included in each of the plurality of application requests is common, the vehicle communication device 300a determines the greatest common divisor based on the notification cycle included in each of the plurality of application requests. Is calculated. The vehicle communication device 300a acquires common ECU data based on the greatest common divisor.
　上記では、ＥＣＵ情報取得部３３１が、５秒周期で、ｏｗｎＶｅｌｏｃｉｔｙを取得する場合を例示した。ここで、ＥＣＵ情報取得部３３１は、上位アプリケーション１００ａが送信したアプリケーション要求に基づいて、５秒周期で、ｏｗｎＶｅｌｏｃｉｔｙを取得する処理を実行するものとする。また、ＥＣＵ情報取得部３３１は、上位アプリケーション１０２ａが送信したアプリケーション要求に基づいて、１０秒周期で、ｏｗｎＶｅｌｏｃｉｔｙを取得する処理を実行するものとする。このように、アプリケーション要求毎にｏｗｎＶｅｌｏｃｉｔｙを取得することは、車通信装置３００ａの負荷を大きくする。そこで、車通信装置３００ａは、通知周期の最大公約数に基づいて、共通のデータを取得する。これにより、車通信装置３００ａは、ＥＣＵデータ（例えば、ｏｗｎＶｅｌｏｃｉｔｙ）を取得する回数を少なくできる。よって、車通信装置３００ａは、負荷を軽減できる。 In the above, the case where the ECU information acquisition unit 331 acquires ownVelocity in a 5-second cycle has been illustrated. Here, the ECU information acquisition unit 331 executes a process of acquiring ownVelocity in a 5-second cycle based on the application request transmitted by the upper application 100a. Further, the ECU information acquisition unit 331 executes a process of acquiring ownVelocity at a cycle of 10 seconds based on the application request transmitted by the upper application 102a. Thus, acquiring ownVelocity for each application request increases the load on the vehicle communication device 300a. Therefore, the vehicle communication device 300a acquires common data based on the greatest common divisor of the notification cycle. Thereby, the vehicle communication device 300a can reduce the number of times of acquiring the ECU data (for example, ownVelocity). Therefore, the vehicle communication device 300a can reduce the load.
実施の形態３．
　次に、実施の形態３を説明する。実施の形態１，２と相違する事項を主に説明し、実施の形態１，２と共通する事項の説明を省略する。実施の形態３は、図１～６，９～１２，１４～１７を参照する。 Embodiment 3 FIG.
Next, a third embodiment will be described. Items that are different from the first and second embodiments will be mainly described, and descriptions of items that are common to the first and second embodiments will be omitted. Embodiment 3 refers to FIGS. 1 to 6, 9 to 12, and 14 to 17.
　実施の形態１，２では、車通信装置がアプリケーション要求を受信した後、車通信装置がロードするモジュールを特定し、特定したモジュールがロードされた。実施の形態３では、車通信装置がアプリケーション要求を受信する前に、車通信装置がロードするモジュールを特定し、予めモジュールがロードされる。 In the first and second embodiments, after the vehicle communication device receives the application request, the module to be loaded by the vehicle communication device is specified, and the specified module is loaded. In the third embodiment, before the vehicle communication device receives the application request, the module to be loaded by the vehicle communication device is specified, and the module is loaded in advance.
　図１８は、実施の形態３の車通信装置の構成を示す機能ブロック図である。車通信装置３００ｂは、要求管理部３２０ｂを有する。要求管理部３２０ｂは、要求解析部３２２ｂとモジュール管理部３２３ｂを有する。
　図３，１４に示される構成と同じ又は対応する図１８の構成は、図３，１４に示される符号と同じ符号を付している。また、図１８は、メイン処理部３８０を省略している。 FIG. 18 is a functional block diagram illustrating a configuration of the vehicle communication device according to the third embodiment. The vehicle communication device 300b has a request management unit 320b. The request management unit 320b has a request analysis unit 322b and a module management unit 323b.
The configurations in FIG. 18 that are the same as or correspond to the configurations illustrated in FIGS. 3 and 14 are denoted by the same reference numerals as those illustrated in FIGS. In FIG. 18, the main processing unit 380 is omitted.
　モジュール管理部３２３ｂは、クラウドサーバ１００～１０２又は上位アプリケーション１００ａ～１０２ａがアプリケーション要求を送信する前に、どのようなアプリケーション要求を送信するのかを調査する。そのため、モジュール管理部３２３ｂは、クラウドサーバ１００～１０２又は上位アプリケーション１００ａ～１０２ａに開示指示を送信する。また、モジュール管理部３２３ｂは、ブロードキャスト又はマルチキャストで開示指示を送信してもよい。 The module management unit 323b investigates what kind of application request is transmitted before the cloud server 100 to 102 or the higher-level application 100a to 102a transmits the application request. Therefore, the module management unit 323b transmits a disclosure instruction to the cloud servers 100 to 102 or the higher-level applications 100a to 102a. Further, the module management unit 323b may transmit the disclosure instruction by broadcast or multicast.
　クラウドサーバ１００～１０２又は上位アプリケーション１００ａ～１０２ａのそれぞれは、アプリケーション要求に含める予定のアプリケーション要求ファイルを車通信装置３００ｂに送信する。 Each of the cloud servers 100 to 102 or the higher-level applications 100a to 102a transmits an application request file to be included in the application request to the vehicle communication device 300b.
　要求解析部３２２ｂは、各アプリケーション要求ファイルを解析する。要求解析部３２２ｂは、解析結果をモジュール管理部３２３ｂに送信する。例えば、解析結果には、ＥＣＵから共通のデータを取得することが登録されている。また、例えば、解析結果には、“ｄｅｔｅｃｔＴｙｐｅ”に“１”が指定されていることが登録されている。 The request analysis unit 322b analyzes each application request file. The request analysis unit 322b transmits the analysis result to the module management unit 323b. For example, acquisition of common data from the ECU is registered in the analysis result. Also, for example, it is registered in the analysis result that “1” is specified in “detectType”.
　モジュール管理部３２３ｂは、解析結果と呼出モジュール管理リスト３７２ａとに基づいて、ロード対象のモジュールを特定する。例えば、モジュール管理部３２３ｂは、ＥＣＵから共通のデータを取得することが解析結果に登録されているので、要求集約部３９０を特定する。モジュール管理部３２３ｂは、“ｄｅｔｅｃｔＴｙｐｅ”に“１”が指定されていることが解析結果に登録されているので、非定常変化検出部３５０を特定する。モジュール管理部３２３ｂは、要求集約部３９０と非定常変化検出部３５０とをロードする。図１８は、要求集約部３９０と非定常変化検出部３５０とがロードされている状態を例示している。 The module management unit 323b specifies the module to be loaded based on the analysis result and the calling module management list 372a. For example, the module management unit 323b specifies the request aggregating unit 390 because acquiring the common data from the ECU is registered in the analysis result. The module management unit 323b specifies the non-stationary change detection unit 350 because “1” is designated as “detectType” in the analysis result. The module management unit 323b loads the request aggregation unit 390 and the unsteady change detection unit 350. FIG. 18 illustrates a state in which the request aggregation unit 390 and the unsteady change detection unit 350 are loaded.
　モジュール管理部３２３ｂは、解析結果に基づいて、ロード対象のモジュールを特定するための呼出モジュール管理リストを作成してもよい。ここで、呼出モジュール管理リストについて、説明する。 The module management unit 323b may create a call module management list for specifying a module to be loaded based on the analysis result. Here, the calling module management list will be described.
　図１９は、実施の形態３の呼出モジュール管理リストの例を示す図である。呼出モジュール管理リスト３７２ｂは、記憶部３７０に格納される。例えば、呼出モジュール管理リスト３７２ｂには、要求集約部３９０及び非定常変化検出部３５０を呼び出す条件が登録される。
　モジュール管理部３２３ｂは、呼出モジュール管理リスト３７２ｂに基づいて、モジュールをロードしてもよい。 FIG. 19 is a diagram illustrating an example of a call module management list according to the third embodiment. The calling module management list 372b is stored in the storage unit 370. For example, conditions for calling the request aggregating unit 390 and the unsteady change detecting unit 350 are registered in the calling module management list 372b.
The module management unit 323b may load a module based on the calling module management list 372b.
　車通信装置３００ｂは、ロード対象のモジュールをロードした後、クラウドサーバ１００～１０２又は上位アプリケーション１００ａ～１０２ａに、アプリケーション要求の送信が可能であることを通知してもよい。 After loading the module to be loaded, the vehicle communication device 300b may notify the cloud servers 100 to 102 or the higher-level applications 100a to 102a that the application request can be transmitted.
　このように、車通信装置３００ｂは、アプリケーション要求を受信する前に、アプリケーション要求に対して処理を行うモジュールを特定可能な情報（すなわち、アプリケーション要求ファイル）をクラウドサーバから取得する。車通信装置３００ｂは、アプリケーション要求を受信する前に、特定可能な情報に基づいてモジュールをロードする。 As described above, before receiving the application request, the vehicle communication device 300b acquires, from the cloud server, information that can specify a module that processes the application request (that is, the application request file). Before receiving the application request, the vehicle communication device 300b loads the module based on the identifiable information.
　実施の形態３によれば、車通信装置３００ｂは、アプリケーション要求を受信する前に、予めモジュールをロードする。これにより、車通信装置３００ｂは、アプリケーション要求を受信した後、モジュールをロードする処理を実行しなくて済む。よって、車通信装置３００ｂは、アプリケーション要求に対する処理時間を短くできる。 According to the third embodiment, the vehicle communication device 300b loads the module in advance before receiving the application request. This eliminates the need for the vehicle communication device 300b to execute the process of loading the module after receiving the application request. Therefore, the vehicle communication device 300b can shorten the processing time for the application request.
　実施の形態１～３では、通信部３１０がアプリケーション要求を要求管理部３２０に伝達する。しかし、通信部３１０と要求管理部３２０との間には、複数のモジュールが存在してもよい。そして、要求管理部３２０は、通信部３１０と複数のモジュールとを介してアプリケーション要求を受信する。 In the first to third embodiments, the communication unit 310 transmits an application request to the request management unit 320. However, a plurality of modules may exist between the communication unit 310 and the request management unit 320. Then, the request management unit 320 receives the application request via the communication unit 310 and the plurality of modules.
　実施の形態２，３では、モジュール管理部３２３の後、要求集約部３９０が実行される場合がある。しかし、モジュール管理部３２３と要求集約部３９０との間に、複数のモジュールが存在してもよい。 In the second and third embodiments, the request aggregation unit 390 may be executed after the module management unit 323. However, a plurality of modules may exist between the module management unit 323 and the request aggregation unit 390.
　実施の形態１～３では、ＥＣＵ情報伝達部３３２の後、変換部３４０及び非定常変化検出部３５０が実行される場合がある。しかし、ＥＣＵ情報伝達部３３２と、変換部３４０又は非定常変化検出部３５０との間に、複数のモジュールが存在してもよい。 In the first to third embodiments, after the ECU information transmission unit 332, the conversion unit 340 and the unsteady change detection unit 350 may be executed. However, a plurality of modules may exist between the ECU information transmission unit 332 and the conversion unit 340 or the unsteady change detection unit 350.
実施の形態４．
　次に、実施の形態４を説明する。実施の形態１～３と相違する事項を主に説明し、実施の形態１～３と共通する事項の説明を省略する。実施の形態４は、図３～１２，１４～１９を参照してもよい。
　実施の形態１～３では、クラウドサーバ１００，１０１，１０２が車載装置の外に存在する場合を説明した。実施の形態４では、クラウドサーバ１００，１０１，１０２の機能を車載装置が有している場合を説明する。 Embodiment 4 FIG.
Next, a fourth embodiment will be described. Matters that are different from the first to third embodiments will be mainly described, and descriptions of items common to the first to third embodiments will be omitted. Embodiment 4 may refer to FIGS. 3 to 12 and 14 to 19.
In the first to third embodiments, the case where the cloud servers 100, 101, and 102 exist outside the vehicle-mounted device has been described. In the fourth embodiment, a case will be described in which the functions of the cloud servers 100, 101, and 102 are provided in the vehicle-mounted device.
　図２０は、実施の形態４の車載装置の構成を示す機能ブロック図である。車載装置２００ｃは、要求部８００、車通信部３００ｃ、及びＥＣＵ４００～４０３を有する。
　要求部８００及び車通信部３００ｃの一部又は全部は、車載装置２００ｃが有するプロセッサによって実現してもよい。 FIG. 20 is a functional block diagram illustrating the configuration of the vehicle-mounted device according to the fourth embodiment. The in-vehicle device 200c includes a request unit 800, a vehicle communication unit 300c, and ECUs 400 to 403.
Part or all of the request unit 800 and the vehicle communication unit 300c may be realized by a processor included in the vehicle-mounted device 200c.
　要求部８００の一部又は全部は、車載装置２００ｃが有するプロセッサが実行する上位アプリケーション１００ａ，１０１ａ，１０２ａのモジュールとして実現してもよい。車通信部３００ｃの一部又は全部は、車載装置２００ｃが有するプロセッサが実行するプログラムのモジュールとして実現してもよい。 Part or all of the request unit 800 may be realized as a module of the higher- level applications 100a, 101a, and 102a executed by the processor of the in-vehicle device 200c. Part or all of the vehicle communication unit 300c may be realized as a module of a program executed by a processor included in the vehicle-mounted device 200c.
　要求部８００の機能は、クラウドサーバ１００，１０１，１０２（上位アプリケーション１００ａ，１０１ａ，１０２ａ）と同じである。例えば、要求部８００は、アプリケーション要求を送信する。アプリケーション要求は、ＥＣＵデータの取得指示と、ＥＣＵデータを用いて、車算出情報を車通信部３００ｃに算出させる際に車通信部３００ｃが実行する算出処理を支援するための支援情報と、を含む。 The function of the request unit 800 is the same as that of the cloud servers 100, 101, 102 ( upper applications 100a, 101a, 102a). For example, the request unit 800 transmits an application request. The application request includes an ECU data acquisition instruction, and support information for supporting calculation processing executed by the vehicle communication unit 300c when the vehicle communication unit 300c calculates vehicle calculation information using the ECU data. .
　車通信部３００ｃの機能は、実施の形態１～３に記載した車通信装置と同じである。例えば、車通信部３００ｃは、アプリケーション要求を受信する。車通信部３００ｃは、取得指示に基づいて、ＥＣＵからＥＣＵデータを取得する。車通信部３００ｃは、ＥＣＵデータと支援情報に基づいて、車算出情報を算出する。車通信部３００ｃは、車算出情報を要求部８００に送信する。このように、車通信部３００ｃの機能は、実施の形態１～３に記載した車通信装置の機能と同じなので、説明を省略する。 The function of the vehicle communication unit 300c is the same as that of the vehicle communication device described in the first to third embodiments. For example, the vehicle communication unit 300c receives an application request. The vehicle communication unit 300c acquires ECU data from the ECU based on the acquisition instruction. The vehicle communication unit 300c calculates vehicle calculation information based on the ECU data and the support information. The vehicle communication unit 300c transmits the vehicle calculation information to the request unit 800. As described above, the function of the vehicle communication unit 300c is the same as the function of the vehicle communication device described in the first to third embodiments, and a description thereof will be omitted.
　要求部８００と車通信部３００ｃとは、実施の形態１～３に記載したクラウドサーバ１００，１０１，１０２と車通信装置との間で実行される処理と同じ処理を実行することができる。そのため、実施の形態４は、実施の形態１～３に記載の効果と同じ効果を奏する。 The request unit 800 and the vehicle communication unit 300c can execute the same processes as those performed between the cloud servers 100, 101, and 102 and the vehicle communication device described in the first to third embodiments. Therefore, the fourth embodiment has the same effects as the effects described in the first to third embodiments.
　以上に説明した各実施の形態における特徴は、互いに適宜組み合わせることができる。 特 徴 The features of the embodiments described above can be combined with each other as appropriate.
　１００，１０１，１０２　クラウドサーバ、　１００ａ，１０１ａ，１０２ａ　上位アプリケーション、　２００，２００ｃ　車載装置、　３００，３００ａ，３００ｂ　車通信装置、　３００ｃ　車通信部、　３０１　プロセッサ、　３０２　揮発性記憶装置、　３０３　不揮発性記憶装置、　３１０　通信部、　３２０，３２０ｂ　要求管理部、　３２１　要求受付部、　３２２，３２２ｂ　要求解析部、　３２３，３２３ｂ　モジュール管理部、　３２４　要求整形伝達部、　３３０　ＥＣＵ情報管理部、　３３１　ＥＣＵ情報取得部、　３３２　ＥＣＵ情報伝達部、　３４０　変換部、　３４１　データ変換部、　３５０　非定常変化検出部、　３５１　統計解析処理部、　３５２　登録部、　３６０　車算出情報管理部、　３６１　車算出情報受付部、　３６２　車算出情報送信部、　３７０　記憶部、　３７１，３７１ａ　モジュール管理リスト、　３７２，３７２ａ，３７２ｂ　呼出モジュール管理リスト、　３８０　メイン処理部、　３９０　要求集約部、　３９１　共通データ解析部、　３９２　通知周期解析部、　４００，４０１，４０２，４０３　ＥＣＵ、　５００　アプリケーション要求、　５０１　アプリケーション要求ファイル、　５０２　単位変換テーブル、　５０３　算出支援テーブル、　６００　要求パケット、　６０１　ＥＣＵパケット、　７００　情報、　８００　要求部。 100, 101, 102 cloud server, {100a, 101a, 102a} host application, {200, 200c} in-vehicle device, {300, 300a, 300b} car communication device, {300c} car communication unit, {301} processor, {302} volatile storage device, {303} nonvolatile storage device {310} communication unit, {320, 320b} request management unit, {321} request reception unit, {322, 322b} request analysis unit, {323, 323b} module management unit, {324} request shaping transmission unit, {330} ECU information management unit, {331} ECU information acquisition unit, # 332 ECU information transmission unit, {340} conversion unit, {341} data conversion unit, {350} unsteady change detection unit, {351} statistical analysis processing unit, {352} registration unit, {360} vehicle calculation information management unit, # 36 Vehicle calculation information receiving unit, {362} vehicle calculation information transmission unit, {370} storage unit, {371, 371a} module management list, {372, 372a, 372b} calling module management list, {380} main processing unit, {390} request aggregation unit, {391} common data analysis unit, 392 notification cycle analyzer, {400, 401, 402, 403} ECU, {500} application request, {501} application request file, {502} unit conversion table, {503} calculation support table, {600} request packet, {601} ECU packet, {700} information, {800} request unit.

Claims (11)

  1. 　車に関する情報を取得する情報取得部と車通信装置とを有する車載装置と、
    　前記車に関する情報の取得指示と、前記車に関する情報を用いて、要求対象の情報を示す車算出情報を前記車載装置に算出させる際に前記車載装置が実行する算出処理を支援するための支援情報と、を含む要求情報を前記車載装置に送信する情報処理装置と、
    　を含み、
    　前記車通信装置は、
    　前記要求情報を受信し、
    　前記取得指示に基づいて、前記情報取得部から前記車に関する情報を取得し、
    　前記車に関する情報と前記支援情報に基づいて、前記車算出情報を算出し、
    　前記車算出情報を前記情報処理装置に送信する、
    　通信システム。     An in-vehicle device having an information acquisition unit for acquiring information about a vehicle and a vehicle communication device,
    Support information for supporting calculation processing executed by the in-vehicle device when the in-vehicle device calculates vehicle calculation information indicating requested information using the instruction to acquire information on the vehicle and the information on the vehicle. And an information processing device that transmits request information to the in-vehicle device, including:
    Including
    The car communication device,
    Receiving the request information,
    Based on the acquisition instruction, acquire information on the vehicle from the information acquisition unit,
    Calculating the vehicle calculation information based on the information on the vehicle and the support information,
    Transmitting the vehicle calculation information to the information processing device;
    Communications system.
  2. 　前記支援情報は、単位を変換するための情報である単位変換情報を含み、
    　前記要求情報には、前記車載装置に前記車算出情報を予め決められた単位で算出させることを示す情報が含まれており、
    　前記車通信装置は、
    　前記車に関する情報と前記単位変換情報に基づいて、前記車に関する情報の単位を前記予め決められた単位に変換された前記車算出情報を算出する、
    　請求項１に記載の通信システム。     The support information includes unit conversion information that is information for converting a unit,
    The request information includes information indicating that the in-vehicle device calculates the vehicle calculation information in a predetermined unit,
    The car communication device,
    Based on the information on the car and the unit conversion information, calculate the car calculation information in which a unit of the information on the car is converted into the predetermined unit.
    The communication system according to claim 1.
  3. 　前記車載装置は、少なくとも１以上の前記情報取得部を有し、
    　前記支援情報は、複数の前記車に関する情報を用いて、前記車載装置に前記車算出情報を算出させる際に前記車載装置が実行する算出処理を支援するための情報である算出支援情報を含み、
    　前記車通信装置は、
    　少なくとも１以上の前記情報取得部から複数の前記車に関する情報を取得し、
    　複数の前記車に関する情報と前記算出支援情報に基づいて、前記車算出情報を算出する、
    　請求項１に記載の通信システム。     The in-vehicle device has at least one or more of the information acquisition units,
    The support information, using information on the plurality of vehicles, includes calculation support information that is information for supporting a calculation process performed by the vehicle-mounted device when the vehicle-mounted device calculates the vehicle calculation information,
    The car communication device,
    Acquiring information on a plurality of the vehicles from at least one or more of the information acquiring units;
    Calculating the vehicle calculation information based on the information on the plurality of vehicles and the calculation support information;
    The communication system according to claim 1.
  4. 　前記要求情報には、前記車載装置に前記車算出情報を予め決められた単位で算出させることを示す情報が含まれており、
    　前記車載装置は、少なくとも１以上の前記情報取得部を有し、
    　前記支援情報は、単位を変換するための情報である単位変換情報と、複数の前記車に関する情報を用いて、前記車載装置に前記車算出情報を算出させる際に前記車載装置が実行する算出処理を支援するための情報である算出支援情報とを含み、
    　前記車通信装置は、
    　少なくとも１以上の前記情報取得部から複数の前記車に関する情報を取得し、
    　複数の前記車に関する情報、前記単位変換情報、及び前記算出支援情報に基づいて、前記予め決められた単位の前記車算出情報を算出する、
    　請求項１に記載の通信システム。     The request information includes information indicating that the in-vehicle device calculates the vehicle calculation information in a predetermined unit,
    The in-vehicle device has at least one or more of the information acquisition units,
    The support information is a unit conversion information that is information for converting a unit, and a calculation process executed by the on-vehicle device when the on-vehicle device calculates the vehicle calculation information by using information on a plurality of vehicles. And calculation support information that is information for supporting the
    The car communication device,
    Acquiring information on a plurality of the vehicles from at least one or more of the information acquiring units;
    Based on the information on the plurality of vehicles, the unit conversion information, and the calculation support information, calculate the vehicle calculation information in the predetermined unit,
    The communication system according to claim 1.
  5. 　前記要求情報は、前記車に関する情報の統計解析命令を含み、
    　前記車通信装置は、
    　前記要求情報に前記統計解析命令が含まれている場合、前記車に関する情報の過去の履歴に基づいて、前記情報取得部から取得した前記車に関する情報が異常値であるか否かを解析し、
    　解析結果を前記情報処理装置に送信する、
    　請求項１から４のいずれか１項に記載の通信システム。     The request information includes a statistical analysis command of information on the vehicle,
    The car communication device,
    If the request information includes the statistical analysis instruction, based on the past history of information about the car, analyze whether the information about the car acquired from the information acquisition unit is an abnormal value,
    Transmitting an analysis result to the information processing apparatus;
    The communication system according to claim 1.
  6. 　前記要求情報は、前記車算出情報の統計解析命令を含み、
    　前記車通信装置は、
    　前記要求情報に前記統計解析命令が含まれている場合、前記車算出情報の過去の履歴に基づいて、算出された前記車算出情報が異常値であるか否かを解析し、
    　解析結果を前記情報処理装置に送信する、
    　請求項１から４のいずれか１項に記載の通信システム。     The request information includes a statistical analysis command of the vehicle calculation information,
    The car communication device,
    If the request information includes the statistical analysis command, based on the past history of the vehicle calculation information, analyze whether the calculated vehicle calculation information is an abnormal value,
    Transmitting an analysis result to the information processing apparatus;
    The communication system according to claim 1.
  7. 　前記要求情報は、前記車に関する情報を取得する周期を示す情報を含み、
    　前記車通信装置は、
    　複数の前記要求情報を受信し、
    　複数の前記要求情報のそれぞれに含まれている前記取得指示の対象である前記車に関する情報が共通の場合、複数の前記要求情報のそれぞれに含まれている前記周期に基づいて、最大公約数を算出し、
    　前記最大公約数に基づいて、共通の前記車に関する情報を取得する、
    　請求項１から６のいずれか１項に記載の通信システム。     The request information includes information indicating a cycle of acquiring information on the car,
    The car communication device,
    Receiving a plurality of the request information;
    When the information about the vehicle that is the target of the acquisition instruction included in each of the plurality of request information is common, the greatest common divisor is determined based on the cycle included in each of the plurality of request information. Calculate,
    Obtaining information about the common vehicle based on the greatest common divisor;
    The communication system according to claim 1.
  8. 　前記車通信装置は、
    　前記要求情報を受信する前に、前記要求情報に対して処理を行うモジュールを特定可能な情報を前記情報処理装置から取得し、
    　前記要求情報を受信する前に、前記特定可能な情報に基づいて、前記モジュールをロードする、
    　請求項１から７のいずれか１項に記載の通信システム。     The car communication device,
    Before receiving the request information, obtain from the information processing apparatus information that can specify a module that performs processing on the request information,
    Loading the module based on the identifiable information before receiving the request information;
    The communication system according to claim 1.
  9. 　車に関する情報を取得する情報取得部と、
    　車通信部と、
    　前記車に関する情報の取得指示と、前記車に関する情報を用いて、要求対象の情報を示す車算出情報を前記車通信部に算出させる際に前記車通信部が実行する算出処理を支援するための支援情報と、を含む要求情報を送信する要求部と、
    　を有し、
    　前記車通信部は、
    　前記要求情報を受信し、
    　前記取得指示に基づいて、前記情報取得部から前記車に関する情報を取得し、
    　前記車に関する情報と前記支援情報に基づいて、前記車算出情報を算出し、
    　前記車算出情報を前記要求部に送信する、
    　車載装置。     An information acquisition unit that acquires information about a car,
    Car communication department,
    An instruction to acquire information about the vehicle, and information about the vehicle, for supporting the calculation process performed by the vehicle communication unit when the vehicle communication unit calculates vehicle calculation information indicating requested information. A request unit for transmitting request information including support information;
    Has,
    The car communication unit,
    Receiving the request information,
    Based on the acquisition instruction, acquire information on the vehicle from the information acquisition unit,
    Calculating the vehicle calculation information based on the information on the vehicle and the support information,
    Transmitting the vehicle calculation information to the request unit;
    In-vehicle devices.
  10. 　車に関する情報を取得する情報取得部と車通信装置とを有する車載装置と、情報処理装置とを含む通信システムの中の前記情報処理装置が、
    　前記車に関する情報の取得指示と、前記車に関する情報を用いて、要求対象の情報を示す車算出情報を前記車載装置に算出させる際に前記車載装置が実行する算出処理を支援するための支援情報と、を含む要求情報を前記車載装置に送信し、
    　前記車通信装置が、
    　前記要求情報を受信し、
    　前記取得指示に基づいて、前記情報取得部から前記車に関する情報を取得し、
    　前記車に関する情報と前記支援情報に基づいて、前記車算出情報を算出し、
    　前記車算出情報を前記情報処理装置に送信する、
    　情報取得方法。     An in-vehicle device having an information acquisition unit and a vehicle communication device for acquiring information about a vehicle, and the information processing device in a communication system including the information processing device,
    Support information for supporting calculation processing executed by the in-vehicle device when the in-vehicle device calculates vehicle calculation information indicating requested information using the instruction to acquire information on the vehicle and the information on the vehicle. And transmitting request information to the in-vehicle device,
    The vehicle communication device,
    Receiving the request information,
    Based on the acquisition instruction, acquire information on the vehicle from the information acquisition unit,
    Calculating the vehicle calculation information based on the information on the vehicle and the support information,
    Transmitting the vehicle calculation information to the information processing device;
    Information acquisition method.
  11. 　車に関する情報を取得する情報取得部と車通信装置とを有する車載装置と、情報処理装置とを含む通信システムの中の前記情報処理装置に、
    　前記車に関する情報の取得指示と、前記車に関する情報を用いて、要求対象の情報を示す車算出情報を前記車載装置に算出させる際に前記車載装置が実行する算出処理を支援するための支援情報と、を含む要求情報を前記車載装置に送信する、
    　処理を実行させ、
    　前記車通信装置に、
    　前記要求情報を受信し、
    　前記取得指示に基づいて、前記情報取得部から前記車に関する情報を取得し、
    　前記車に関する情報と前記支援情報に基づいて、前記車算出情報を算出し、
    　前記車算出情報を前記情報処理装置に送信する、
    　処理を実行させる、
    　情報取得プログラム。     An in-vehicle device having an information acquisition unit for acquiring information about a car and a vehicle communication device, and the information processing device in the communication system including the information processing device,
    Support information for supporting calculation processing executed by the in-vehicle device when the in-vehicle device calculates vehicle calculation information indicating requested information using the instruction to acquire information on the vehicle and the information on the vehicle. And transmitting request information to the in-vehicle device, including:
    Execute the process,
    In the vehicle communication device,
    Receiving the request information,
    Based on the acquisition instruction, acquire information on the vehicle from the information acquisition unit,
    Calculating the vehicle calculation information based on the information on the vehicle and the support information,
    Transmitting the vehicle calculation information to the information processing device;
    Execute the process,
    Information acquisition program.
PCT/JP2018/027000 2018-07-19 2018-07-19 Communication system, in-vehicle device, information acquisition method, and information acquisition program WO2020016976A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2018/027000 WO2020016976A1 (en) 2018-07-19 2018-07-19 Communication system, in-vehicle device, information acquisition method, and information acquisition program

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2018/027000 WO2020016976A1 (en) 2018-07-19 2018-07-19 Communication system, in-vehicle device, information acquisition method, and information acquisition program

Publications (1)

Publication Number Publication Date
WO2020016976A1 true WO2020016976A1 (en) 2020-01-23

Family

ID=69163683

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2018/027000 WO2020016976A1 (en) 2018-07-19 2018-07-19 Communication system, in-vehicle device, information acquisition method, and information acquisition program

Country Status (1)

Country Link
WO (1) WO2020016976A1 (en)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2002331882A (en) * 2001-05-09 2002-11-19 Hitachi Ltd Vehicle data access method and on-vehicle terminal
JP2003006067A (en) * 2001-06-22 2003-01-10 Fujitsu Ltd Program and device for supporting collection of management information
JP2006039625A (en) * 2004-07-22 2006-02-09 Nec Software Tohoku Ltd Performance statistical information output system and performance statistical information output method, and program
JP2008204281A (en) * 2007-02-21 2008-09-04 Nippon Soken Inc Object detection device and inter-vehicle communication system
JP2009294004A (en) * 2008-06-03 2009-12-17 Fujitsu Ten Ltd Abnormality analysis apparatus and abnormality analysis method
JP2011060323A (en) * 2010-12-06 2011-03-24 Hitachi Ltd Information monitoring method, system, and program
JP2012010021A (en) * 2010-06-23 2012-01-12 Toyota Motor Corp Vehicle communication device

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2002331882A (en) * 2001-05-09 2002-11-19 Hitachi Ltd Vehicle data access method and on-vehicle terminal
JP2003006067A (en) * 2001-06-22 2003-01-10 Fujitsu Ltd Program and device for supporting collection of management information
JP2006039625A (en) * 2004-07-22 2006-02-09 Nec Software Tohoku Ltd Performance statistical information output system and performance statistical information output method, and program
JP2008204281A (en) * 2007-02-21 2008-09-04 Nippon Soken Inc Object detection device and inter-vehicle communication system
JP2009294004A (en) * 2008-06-03 2009-12-17 Fujitsu Ten Ltd Abnormality analysis apparatus and abnormality analysis method
JP2012010021A (en) * 2010-06-23 2012-01-12 Toyota Motor Corp Vehicle communication device
JP2011060323A (en) * 2010-12-06 2011-03-24 Hitachi Ltd Information monitoring method, system, and program

Similar Documents

Publication Publication Date Title
US9231998B2 (en) Vehicle-specific computation management system for cloud computing
US10999156B2 (en) Mobility services platform for self-healing mobility clients
EP3369635A1 (en) Vehicle control device and vehicle control system
WO2020145279A1 (en) On-vehicle information processing device, user terminal, information processing method, and program
US11528325B2 (en) Prioritizing data using rules for transmission over network
US10893063B2 (en) Information processing device and information processing method
WO2013011735A1 (en) Communication system, relay device, and communication method
US9299198B2 (en) Fleet vehicle aftermarket equipment monitoring
EP3547608B1 (en) Control device, computer readable recording medium recording program for control device, and control method
KR20170013277A (en) Method and device for processing real-time vehicle traveling data
US10861253B2 (en) Information processing device and information processing method
WO2020012471A2 (en) Optimizing size of protocol communication in a vehicle internal networks
US20230040713A1 (en) Simulation method for autonomous vehicle and method for controlling autonomous vehicle
JP2019103006A (en) On-vehicle relay device, information processing device, relay device, information processing method, program, information processing system, vehicle, and external device
JP7180686B2 (en) Information processing device, anomaly analysis method and program
WO2019239798A1 (en) Electronic control device and electronic control system
US11924726B2 (en) In-vehicle control device, information processing device, vehicle network system, method of providing application program, and recording medium with program recorded thereon
JP2019194845A (en) Disaster mitigation system for connected vehicles with hidden vehicle functionality
JP6157644B2 (en) Method for reducing the total computational capacity to be retained, use of a car-to-X communication device and a car-to-X communication device
WO2020016976A1 (en) Communication system, in-vehicle device, information acquisition method, and information acquisition program
JP2014031077A (en) Vehicle operation verification system
US20230145286A1 (en) Vehicle management system, server, vehicle, and vehicle management method
US11084495B2 (en) Monitoring apparatus, monitoring method, and program
WO2024004594A1 (en) Relay device, information processing method, and in-vehicle system
US20240007859A1 (en) Detecting spoofed ethernet frames within an autosar communication stack

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18926817

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18926817

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP