WO2023276816A1 - データ処理方法、および通信システム - Google Patents
データ処理方法、および通信システム Download PDFInfo
- Publication number
- WO2023276816A1 WO2023276816A1 PCT/JP2022/024888 JP2022024888W WO2023276816A1 WO 2023276816 A1 WO2023276816 A1 WO 2023276816A1 JP 2022024888 W JP2022024888 W JP 2022024888W WO 2023276816 A1 WO2023276816 A1 WO 2023276816A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- data
- vehicle
- unit
- processing method
- input
- Prior art date
Links
- 238000004891 communication Methods 0.000 title claims abstract description 122
- 238000003672 processing method Methods 0.000 title claims abstract description 44
- 238000000034 method Methods 0.000 claims abstract description 179
- 238000012545 processing Methods 0.000 claims description 110
- 238000012937 correction Methods 0.000 claims description 3
- 238000013075 data extraction Methods 0.000 claims 1
- 238000001914 filtration Methods 0.000 description 65
- 230000006870 function Effects 0.000 description 57
- 238000013480 data collection Methods 0.000 description 37
- 238000010606 normalization Methods 0.000 description 27
- 238000006243 chemical reaction Methods 0.000 description 23
- 238000010586 diagram Methods 0.000 description 12
- 239000000284 extract Substances 0.000 description 7
- 238000013500 data storage Methods 0.000 description 6
- 239000008186 active pharmaceutical agent Substances 0.000 description 5
- 230000005540 biological transmission Effects 0.000 description 5
- 230000001133 acceleration Effects 0.000 description 4
- 238000013523 data management Methods 0.000 description 4
- 230000000694 effects Effects 0.000 description 3
- 102100034112 Alkyldihydroxyacetonephosphate synthase, peroxisomal Human genes 0.000 description 2
- 101000799143 Homo sapiens Alkyldihydroxyacetonephosphate synthase, peroxisomal Proteins 0.000 description 2
- 238000000848 angular dependent Auger electron spectroscopy Methods 0.000 description 2
- 230000001413 cellular effect Effects 0.000 description 2
- 238000004590 computer program Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000012549 training Methods 0.000 description 2
- 101000654386 Homo sapiens Sodium channel protein type 9 subunit alpha Proteins 0.000 description 1
- 102100031367 Sodium channel protein type 9 subunit alpha Human genes 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000002708 enhancing effect Effects 0.000 description 1
- 238000000605 extraction Methods 0.000 description 1
- 239000000446 fuel Substances 0.000 description 1
- 238000003384 imaging method Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 239000000203 mixture Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 239000010705 motor oil Substances 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/565—Conversion or adaptation of application format or content
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06T—IMAGE DATA PROCESSING OR GENERATION, IN GENERAL
- G06T7/00—Image analysis
- G06T7/70—Determining position or orientation of objects or cameras
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06V—IMAGE OR VIDEO RECOGNITION OR UNDERSTANDING
- G06V20/00—Scenes; Scene-specific elements
- G06V20/50—Context or environment of the image
- G06V20/56—Context or environment of the image exterior to a vehicle by using sensors mounted on the vehicle
- G06V20/58—Recognition of moving objects or obstacles, e.g. vehicles or pedestrians; Recognition of traffic objects, e.g. traffic signs, traffic lights or roads
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C5/00—Registering or indicating the working of vehicles
- G07C5/008—Registering or indicating the working of vehicles communicating information to a remotely located station
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16Y—INFORMATION AND COMMUNICATION TECHNOLOGY SPECIALLY ADAPTED FOR THE INTERNET OF THINGS [IoT]
- G16Y40/00—IoT characterised by the purpose of the information processing
- G16Y40/10—Detection; Monitoring
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/24—Negotiation of communication capabilities
Definitions
- the present disclosure relates to a data processing method and a communication system executed by an in-vehicle device unit.
- Patent Literature 1 discloses a technology that is an in-vehicle device mounted on a vehicle and collects data related to the vehicle from within the vehicle and uploads it to a predetermined server.
- the data uploaded from the onboard device to the server is raw data whose meaning cannot be understood from the data itself. For this reason, it is necessary to process the raw data so that the meaning of the raw data can be understood on the server side.
- One aspect of the present disclosure is to reduce the processing load on the server side in technology for collecting vehicle data. Also, the function or performance of the vehicle-mounted device may be expanded with a low development load.
- a third process is performed to convert the data after the second process into data whose meaning can be understood without comparing it with other data. Furthermore, the data after the third processing is provided to the server.
- the input I/F 155A in the embodiment corresponds to the acquisition section in the present disclosure
- the filtering sections 20B and 156B in the embodiment correspond to the first processing section in the present disclosure
- the standardization units 20C and 156C in the embodiment correspond to the second processing unit in the present disclosure
- the normalization unit 20D in the embodiment corresponds to the third processing unit in the present disclosure
- the communication unit 13 in the embodiment corresponds to the providing unit in the present disclosure.
- the functions of the filtering units 20B and 156B correspond to the first processing in the present disclosure
- the functions of the standardization units 20C and 156C correspond to the second processing in the present disclosure. Equivalent to.
- the function of the normalization unit 20D corresponds to the third process in the present disclosure
- the function of the structuring unit 20E corresponds to the fourth process in the present disclosure.
- the functions of the determination units 20A and 156A correspond to the functions of determining the capability of the vehicle-mounted device in the present disclosure.
- the communication unit 213 corresponds to the relay unit in the present disclosure.
- the mobility IoT system 1 of this embodiment includes a plurality of data collection devices 2, a management center 3, and a service providing server 4, as shown in FIG. IoT is an abbreviation for Internet of Things.
- the data collection device 2 is mounted on the vehicle and has a function of performing data communication with the management center 3 via the wide area wireless communication network NW.
- the management center 3 is a device that manages the mobility IoT system 1.
- the management center 3 has a function of performing data communication with the plurality of data collecting devices 2 and the service providing server 4 via the wide area wireless communication network NW.
- the service providing server 4 is, for example, a server installed to provide a service for managing vehicle operation.
- the mobility IoT system 1 may include a plurality of service providing servers with different service contents.
- the data collection device 2 includes a main body portion 2A, which is the main body portion of the vehicle-mounted device, and an expansion unit 2B detachably attached to the main body portion 2A.
- a plurality of expansion units 2B may be provided as shown in FIG.
- the extension unit 2B is configured to be electrically connectable to and detachable from the main body 2A mounted on the vehicle using connectors 150A to 190A.
- the main unit 2A includes a microcomputer 11, a vehicle interface (hereinafter referred to as vehicle I/F) 12, a communication unit 13, and a storage unit 14, as shown in FIG.
- vehicle I/F vehicle interface
- storage unit 14 as shown in FIG.
- the microcomputer 11 includes a first core 21, a second core 22, a ROM 23, a RAM 24, a flash memory 25, an input/output section 26, and a bus 27.
- the microcomputer 11 Various functions of the microcomputer 11 are realized by the first core 21 and the second core 22 executing a program stored in a non-transitional material recording medium.
- the ROM 23 corresponds to a non-transitional substantive recording medium storing programs. Also, by executing this program, a method corresponding to the program is executed. Part or all of the functions executed by the first core 21 and the second core 22 may be configured in hardware by one or a plurality of ICs or the like.
- the flash memory 25 is a data rewritable nonvolatile memory.
- the flash memory 25 includes a standardized vehicle data storage section 25A for storing standardized vehicle data, which will be described later.
- the input/output unit 26 is a circuit for inputting/outputting data between the outside of the microcomputer 11 and the first core 21 and the second core 22 .
- the bus 27 connects the first core 21, the second core 22, the ROM 23, the RAM 24, the flash memory 25, and the input/output unit 26 so that data can be input/output to each other.
- the communication unit 13 performs data communication with the management center 3 via the wide area wireless communication network NW.
- the storage unit 14 is a storage device for storing various data.
- the vehicle I/F 12 is an input/output circuit for inputting/outputting signals between the electronic control unit and sensors mounted on the vehicle.
- Vehicle I/F 12 includes a power supply voltage input port, a general-purpose input/output port, a CAN communication port, an Ethernet communication port, and the like.
- a CAN communication port is a port for transmitting and receiving data according to the CAN communication protocol.
- the Ethernet communication port is a port for transmitting and receiving data based on the Ethernet communication protocol.
- CAN is an abbreviation for Controller Area Network. CAN is a registered trademark. Ethernet is a registered trademark.
- An expansion unit 2B is connected to the CAN communication port and the Ethernet communication port as described later, and another electronic control device mounted on the vehicle is connected via the expansion unit 2B.
- the main unit 2A of the data collection device 2 can transmit and receive communication frames to and from other electronic control devices.
- Each port of the vehicle I/F 12 has a plurality of connectors 125A to 125G connectable to the expansion unit 2B, as shown in FIG. Different expansion units 2B can be connected to the connectors 125A to 125G. Further, the vehicle I/F 12 is configured to be able to communicate with a communication protocol preset for each of the connectors 125A-125G.
- the expansion unit 2B has a function for expanding or enhancing the functions and performance of the main body 2A.
- the expansion unit 2B has a function that the main unit 2A does not have, or a function that takes part of the processing performed in the main unit 2A to increase the speed of the main unit 2A by providing resources for the main unit 2A. .
- the expansion unit 2B is electrically arranged between the vehicle I/F 12 and the vehicle-side device 2C.
- the vehicle I/F 12 can acquire data from the vehicle-side device 2C via the extension unit 2B, and in particular, can collect data to be transmitted to the management center 3 via the extension unit 2B. Moreover, the vehicle I/F 12 can transmit data to the vehicle-side device 2C via the expansion unit 2B.
- the data collection device 2 includes a vehicle expansion unit 150, a sensor expansion unit 160, a display expansion unit 170, a USB expansion unit 180, and a network expansion unit 190 as expansion units 2B.
- a vehicle expansion unit 150 a sensor expansion unit 160
- a display expansion unit 170 a USB expansion unit 180
- a network expansion unit 190 as expansion units 2B.
- many expansion units 150 to 190 are provided, but the number and type of expansion units 150 to 190 to be provided can be arbitrarily set according to the type and grade of the vehicle. Therefore, the main body part 2A can function as the data collection device 2 without the expansion unit 2B.
- the vehicle expansion unit 150 includes on-vehicle device side connectors 150A and 150B and device side connectors 150C to 150H.
- the on-vehicle-side connectors 150A and 150B are connectors on the side connected to the main body 2A
- the device-side connectors 150C to 150H are connectors on the side connected to the vehicle-side device 2C.
- the vehicle extension unit 150 communicates with other electronic control units arranged in the vehicle via the equipment-side connectors 150C to 150H, and receives data obtained from the vehicle-side equipment 2C located inside the vehicle as input data. and That is, the vehicle extension unit 150 uses vehicle data for controlling the vehicle as input data.
- the vehicle expansion unit 150 has a function of transmitting and receiving data to and from the main unit 2A via the vehicle-mounted device side connectors 150A and 150B.
- the in-vehicle device side connector 150A is a connector compatible with the Ethernet communication protocol, and configured to be connectable with the connector 125A on the vehicle I/F 12 side.
- the in-vehicle device side connector 150B is a connector corresponding to CAN, GPIO, and UART communication protocols, and is configured to be connectable with the connector 125B on the vehicle I/F 12 side.
- GPIO means a general-purpose IO port and is an abbreviation for General Purpose Input/Output.
- UART is an abbreviation for Universal Asynchronous Receiver/Transmitter.
- the device-side connector 150C is a connector compatible with the UART communication protocol.
- the device-side connector 150D is a connector compatible with the Ethernet communication protocol.
- the device-side connector 150E is a connector compatible with the GPIO communication protocol.
- the device-side connector 150F is a connector compatible with the CAN communication protocol.
- the device-side connector 150G is a connector compatible with the CAN FD communication protocol.
- the device-side connector 150H is a connector compatible with the LIN communication protocol. Note that these device-side connectors 150C to 150H may be configured to be accommodated in one connector case.
- CAN FD is an abbreviation for CAN with Flexible Data Rate.
- LIN is an abbreviation for Local Interconnect Network.
- the in-vehicle device side connector 160A of the sensor expansion unit 160 is a connector compatible with UART and Ethernet communication protocols, and is configured to be connectable with the connector 125C on the vehicle I/F 12 side.
- the display expansion unit 170 includes an in-vehicle device side connector 170A and a device side connector 170B.
- the display expansion unit 170 is connected to the vehicle I/F 12 via the vehicle-mounted device side connector 170A.
- the display expansion unit 170 is connected to the display 175 via the equipment side connector 170B.
- the display expansion unit 170 receives display data such as video as input data.
- the in-vehicle device side connector 170A is compatible with, for example, LVDS format video data
- the device side connector 170B is compatible with, for example, HDMI format video data.
- HDMI is a registered trademark.
- Display expansion unit 170 converts the format of video data sent from vehicle I/F 12 and outputs the data to display 175 .
- the expansion unit 2B may have a data conversion function or a communication protocol conversion function like the display expansion unit 170 does.
- the network expansion unit 190 includes an in-vehicle device side connector 190A, a Bluetooth antenna 195A, a WiFi antenna 195B, and a cellular antenna 195C.
- Bluetooth and WiFi are registered trademarks.
- the in-vehicle device side connector 190A is a connector compatible with communication protocols of PCI express (Peripheral Component Interconnect Express), USB, and UART.
- a plurality of output lines included in the vehicle-mounted device connector 190A may be provided so as to correspond to the data received from each of the antennas 195A, 195B, and 195C. Also, one output line may be provided for outputting the data received from each antenna 195A, 195B, 195C.
- the management center 3 includes a control unit 31, a communication unit 32, and a storage unit 33, as shown in FIG.
- the storage unit 33 is a storage device for storing various data.
- the main body 2A of the data collection device 2 includes a first unit 101 as a functional block realized by the first core 21 executing the program stored in the ROM 23, as shown in FIG.
- the main unit 2A includes a second unit 102 as a functional block implemented by the second core 22 executing the program stored in the ROM 23 .
- the second application 106 executes processing related to services provided by the service providing server 4 .
- the second application 106 is configured to be able to access the standardized vehicle data storage section 25A of the flash memory 25 and refer to the standardized vehicle data in order to execute service-related processing.
- the method of realizing these elements that make up the management center 3 is not limited to software, and some or all of the elements may be realized using one or more pieces of hardware.
- the electronic circuit may be realized by a digital circuit including many logic circuits, an analog circuit, or a combination thereof.
- Mobility GW 111 includes shadow storage unit 112 and vehicle control unit 113 .
- the shadow storage unit 112 stores a shadow 114 containing data for each vehicle on which the data collection device 2 is mounted.
- a shadow 114 indicates a group of vehicle data for a certain vehicle.
- the vehicle control unit 113 has a function of controlling the vehicle on which the data collection device 2 is mounted based on instructions from the service providing server 4 .
- the vehicle expansion unit 150 is an electronic control device mainly composed of a microcomputer having a CPU 153 and a memory 154 such as ROM and RAM.
- Various functions of the microcomputer are realized by CPU 153 executing a program stored in a non-transitional substantive recording medium.
- the memory 154 corresponds to a non-transitional substantive recording medium storing programs. Also, by executing this program, a method corresponding to the program is executed.
- a part or all of the functions executed by the CPU 153 may be configured as hardware using one or a plurality of ICs or the like.
- the number of microcomputers provided in the vehicle expansion unit 150 may be one or more.
- Functions executed by the CPU 153 include an input I/F 155A, an output I/F 155B, a determination section 156A, a filtering section 156B, and a standardization section 156C.
- the vehicle expansion unit 150 includes a plurality of input lines 152C-152H, a plurality of output lines 151A-151F, and at least one connector 150A-190A.
- Input lines 152C to 152H are provided for each communication protocol of data to be handled, and data is input. Note that, in the present embodiment, even when a plurality of wirings are required for one communication protocol, the plurality of wirings are referred to as one input line. The same applies to output lines.
- the input lines 152C-152H are wires connected to the device-side connectors 150C-150H.
- the input line 152C is wiring corresponding to UART.
- the input line 152D is a wiring compatible with Ethernet.
- the input line 152E is a wiring corresponding to GPIO.
- the input line 152F is wiring corresponding to CAN.
- the input line 152G is a wiring corresponding to CAN FD.
- the input line 152H is a wiring corresponding to LIN.
- the output lines 151B to 151F are wires that are collectively connected to the in-vehicle device side connector 150B.
- the output line 151B is wiring for a battery power supply.
- the output line 151C is wiring for an ignition power supply.
- the output line 151D is a communication line for CAN communication.
- the output line 151E is a communication line for GPIO communication.
- the output line 151F is a communication line for UART communication.
- the vehicle-mounted device side connector 150B may be provided for each of the output lines 151A to 151F. Also, one of the output lines 151B to 151F may be unconnected.
- the vehicle expansion unit 150 is connected to the vehicle I/F 12 through both connectors 150A and 150B.
- the number of input lines 152C to 152H to which data is transmitted is set smaller than the number of output lines 151A and 151D to 151F to which data are transmitted.
- Vehicle extension unit 150 may be connected to vehicle I/F 12 through only one of connectors 150A and 150B. Vehicle extension unit 150 may also include only one of connectors 150A and 150B.
- the input line is for each protocol or data type, for example, one for JPEG, Two lines, one for GIF and the other for GIF, may be arranged.
- the input lines may be divided for each type of data.
- two USB connection lines, one for JPEG and one for GIF may be arranged.
- the expansion unit 2B performs image recognition on JPEG and GIF image data and forms them in the standard format for target information, the output data is only target information, so the output line is 1. can be a book. That is, the number of output lines is smaller than the number of input lines for the same type of input data. Any communication protocol may be used for this single output line.
- data input from one or more input lines using different communication protocols may be configured to be output from one output line.
- the data received by the CAN FD input line may be converted into CAN format and output from the CAN output line.
- CAN input data and CAN FD input data can be output from the same CAN output line, and the number of output lines is smaller than the number of input lines.
- MPEG image data when MPEG image data is input to the expansion unit 2B, only one input line for MPEG can be arranged. In the expansion unit 2B, this input line can be branched into two. One of the output lines can be used to output the MPEG image data itself from the output line. The other one of the output lines can be used for image recognition by the expansion unit 2B and for outputting target information in a standard format. That is, there are more output lines than input lines for the same kind of input data.
- data input from one communication protocol may be configured to be branched and output from two output lines.
- one of the output lines can be used to output the CAN input data itself.
- the other output line can be used to normalize the input data in the expansion unit 2B and output the normalized data.
- the main unit 2A of the data collection device 2 includes a determination unit 20A, a filtering unit 20B, a standardization unit 20C, and a normalization unit as functions executed by the first unit 101 or the second unit 102. 20D, with a structured portion 20E. Either the first unit 101 or the second unit 102 may perform these functions.
- the determination unit 156A, the filtering unit 156B, and the standardization unit 156C of the vehicle expansion unit 150 are configured to perform predetermined processing on the input data and output output data based on the input data from the output lines 151A to 151F. be done.
- the output data may be data after processing by the filtering unit 156B or the like, or may be the input data itself.
- the determination unit 20A, the filtering unit 20B, and the standardization unit 20C included in the main unit 2A have the same functions as the determination unit 156A, the filtering unit 156B, and the standardization unit 156C included in the vehicle expansion unit 150. explain.
- determination units 20A and 156A Upon receiving data from vehicle I/F 12 or input I/F 155A, determination units 20A and 156A recognize the communication protocol of the data based on the communication ports that received the data, that is, connectors 150C to 150H. Specifically, for example, when data is received at a CAN communication port (eg, input line 152F), the determination units 20A and 156A recognize that the communication protocol of the received data is CAN. For example, when data is received at an Ethernet communication port (for example, input line 152D), the determination units 20A and 156A recognize that the communication protocol of the received data is Ethernet.
- a CAN communication port eg, input line 152F
- Ethernet communication port for example, input line 152D
- the judging section 156A of the vehicle expansion unit 150 judges the capabilities of the main body section 2A, that is, the processing that the main body section 2A can execute, based on the communication protocol, the types of the connectors 150A to 190A, and the like. This is because whether the processing should be performed by the vehicle expansion unit 150 or the processing by the main body 2A is set depending on whether the main body 2A has sufficient capability.
- the determination unit 156A of the vehicle expansion unit 150 determines that the main unit 2A has the preset capability
- the determination unit 156A of the vehicle expansion unit 150 directly converts the received data to the main unit 2A without performing thinning, protocol conversion, or the like on the data. transfer to the output I/F 155B so as to transmit to .
- the determination unit 156A of the vehicle expansion unit 150 determines what kind of processing is to be performed on the input data based on the filtering table 8 shown in FIG.
- vehicle expansion unit 150 upon receiving data from connectors 150C-E and 150G-H having communication ports other than CAN, in other words, data is received from connectors 150C-E and 150G-H having communication ports other than CAN. implement.
- vehicle expansion unit 150 when data is received from connector 150F having a CAN communication protocol, in other words, a CAN communication port, processing in later-described filtering section 156B and standardization section 156C is not performed.
- the CAN frame consists of a start of frame, an arbitration field, a control field, a data field, a CRC field, an ACK field and an end of frame.
- the arbitration field consists of an 11-bit or 29-bit identifier (that is, ID) and a 1-bit RTR bit.
- CANID the 11-bit identifier used in CAN communication.
- the CANID is set in advance based on the content of data included in the CAN frame, the source of the CAN frame, the destination of the CAN frame, and the like.
- processing is performed as follows.
- the sensor extension unit 160 receives data from a connector having a UART communication protocol, in other words, a UART communication port
- the data is processed by a filtering unit 156B and a standardization unit 156C, which will be described later.
- sensor extension unit 160 receives data from a connector having an Ethernet communication protocol, in other words, an Ethernet communication port
- it does not perform processing in filtering section 156B and standardization section 156C, which will be described later.
- the data input from the Ethernet input line is directly output from the output line.
- the display expansion unit 170 and the USB expansion unit 180 do not perform processing in the later-described filtering section 156B and standardization section 156C, regardless of the type of data to be handled. That is, the data input from the input line is directly output from the output line.
- the network expansion unit 190 performs processing in the later-described filtering section 156B and standardization section 156C regardless of the type of data to be handled.
- the vehicle expansion unit 150 does not perform filtering when data is received using the CAN communication protocol. In this case, since CAN data has already been received, conversion into CAN data by standardization unit 156C is not performed either. However, the filtering unit 156B may perform a process of extracting only CAN data of a preset type from the input data.
- the filtering section of the sensor expansion unit 160 receives data using the UART communication protocol, it performs processing set according to the data type.
- the sensor extension unit 160 performs image recognition based on the input data and extracts target object information as a recognition result. Specifically, for example, from binary data consisting only of 0 and 1, edges that serve as boundaries of brightness on the image are extracted, and the shapes, sizes, etc. of the edges are used to determine whether objects in the image are people, things, vehicles, or signs. etc. It should be noted that the sensor extension unit 160 may only perform conversions that reduce the resolution of the image, such as conversions that reduce the number of pixels per frame.
- the sensor extension unit 160 When receiving voice data, the sensor extension unit 160 performs voice recognition based on the input data and extracts text data as a recognition result. It should be noted that the sensor extension unit 160 may only perform conversions that reduce the resolution, eg, bitrate, of the audio.
- the standardized data includes, for example, an ID indicating the data type, data length information, actual data (i.e., payload), and error correction code, and each data has a common data format, that is, a common data format.
- the target information that is the recognition result is stored in the payload.
- the normalization information includes setting items such as "CANID”, "ECU", “position”, “DLC”, "unique label”, “resolution”, “offset” and “unit”. Prepare. "Unique label” and "ECU” are as described above.
- Data type "data size” and “data unit” indicate the type, size and unit of the numerical value indicated by the "data value”.
- Energy which is an item in the first hierarchy, is a category name indicating energy information, and includes "battery state”, “battery configuration”, and "fuel” as items in the second hierarchy.
- Vehicle identification information which is an item of the second hierarchy, has “vehicle identification number”, “vehicle number”, and “license plate” as items of the third hierarchy.
- the first process can be omitted according to the types of the connectors 150A-190A.
- the extension unit 2B can determine the capability of the main body 2A according to the types of the connectors 150A-190A.
- the data after data structuring can be provided to the management center 3.
- the obstacle data can be converted into the obstacle recognition result and then output to the main unit 2A. Therefore, processing by the main body 2A can be reduced as compared with the case where the processing is performed by the main body 2A.
Landscapes
- Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Multimedia (AREA)
- Signal Processing (AREA)
- Computing Systems (AREA)
- Computer Networks & Wireless Communication (AREA)
- Computer Vision & Pattern Recognition (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Small-Scale Networks (AREA)
Abstract
Description
実施形態におけるモビリティIoTシステム1は、本開示での通信システムに相当する。また、データ収集装置2は、本開示での車載機ユニットに相当し、実施形態における本体部2Aは、本開示での車載機に相当する。また、実施形態における他のECU、レーダ165、カメラ166,185、マイク167,187、加速度センサ168、ディスプレイ175、GPS186、タッチパネル188、スピーカ189、アンテナ195A~195Cは、本開示での提供元機器に相当する。
以下に本開示の実施形態を図面とともに説明する。
次に、本体部2Aと拡張ユニット2Bとが実行する処理について説明する。なお、拡張ユニット2Bについては、拡張ユニット2Bを代表して、車両拡張ユニット150を説明する。他の拡張ユニット160~190については、概ね同様の構成および機能を備えるため、相違点のみ説明する。
判定部20A,156Aは、車両I/F12または入力I/F155Aからデータを受信すると、データを受信した通信ポート、つまりコネクタ150C~150Hに基づいて、データの通信プロトコルを認識する。具体的には、判定部20A,156Aは、例えば、CAN通信ポート(例えば入力線152F)でデータを受信した場合には、受信したデータの通信プロトコルはCANであると認識する。また判定部20A,156Aは、例えば、イーサネット通信ポート(例えば入力線152D)でデータを受信した場合には、受信したデータの通信プロトコルはイーサネットであると認識する。
フィルタリング部20B,156Bは、入力されたデータに対して、フィルタリングを実施する。ここで、本実施形態でのフィルタリングとは、入力されたデータに対して、よりデータ量が少なくなるように処理することを示す。
標準化部20C,156Cは、フィルタリング部20B,156Bによる処理後のデータを、予め設定された形式のデータに変換する処理である標準化を実施する。標準化はフォーマット化とも呼ばれる。
以下で示す、正規化部20Dおよび構造化部20Eは、本体部2Aに備えられる機能である。正規化部20Dは、標準化後のデータを、正規化情報を用いて正規化することで、正規化データを生成する。そして、正規化部20Dは、正規化データを用いて、他データと比較することなく意味が理解できるデータに変換する処理である意味化を実施する。
構造化部20Eは、意味化されたデータを、予め階層化された各分類に対応付ける処理であるデータ構造化を実施する。この際、構造化部20Eは、意味化されたデータを階層化してフラッシュメモリ25に記憶する。具体的には、構造化部20Eは、変換されたデータを、フラッシュメモリ25に設けられた標準化車両データ格納部25Aの対応領域に格納する。この結果、標準化車両データ格納部25Aは、データを階層化して構成される標準化車両データを格納する。
次に、図13に示すシーケンス図を用いて、データ収集装置2が標準化車両データを作成する手順を説明する。なお、この手順は、例えば所定の周期毎に実施され、この結果、データ収集装置2は、定期的に管理センター3に対してデータを送信することができる。
以上詳述した第1実施形態によれば、以下の効果を奏する。
以上、本開示の実施形態について説明したが、本開示は上述の実施形態に限定されることなく、種々変形して実施することができる。
Claims (20)
- 通信機を介してクラウドサーバと通信可能な車載機(2A)と、前記車載機に対して着脱自在に構成された拡張ユニット(2B)とを備える車載機ユニット(2)が実行するデータ処理方法であって、
入力データの提供元となる提供元機器から前記入力データを取得し(L11,L15)、
前記入力データに対して、よりデータ量が少なくなるような処理である第1処理を実施し(L13,L22)、
前記第1処理後のデータを、予め設定された形式のデータに変換する第2処理を実施し(L14,L23)、
前記第2処理後のデータを、正規化データに変換する第3処理を実施し(L16,L24)、
前記第3処理後のデータに基づいて、車両データをクラウドサーバに提供する(L31)
データ処理方法。 - 請求項1に記載のデータ処理方法であって、
前記拡張ユニットは、
前記提供元機器から前記入力データを取得し、前記第1処理および前記第2処理を実施し、
前記車載機は、
前記第2処理後のデータを取得し、前記第3処理を実施し、前記第3処理後のデータをサーバに提供する
データ処理方法。 - 請求項1または請求項2に記載のデータ処理方法であって、
前記拡張ユニットは、
前記車載機の能力を判定し、
前記車載機に予め設定された能力があると判定すると、前記入力データに対して前記第1処理および第2処理を実施しない未処理データを前記車載機に送信し、
前記車載機に予め設定された能力がないと判定すると、前記入力データを前記第1処理および前記第2処理を実施し、前記第2処理後のデータを前記車載機に送信し、
前記車載機は、
前記未処理データを受けると、前記第1処理、前記第2処理、前記第3処理を実施し、前記第3処理後のデータをサーバに提供し、
前記第2処理後のデータを受けると、前記第3処理を実施し、前記第3処理後のデータをサーバに提供する
データ処理方法。 - 請求項1または請求項2に記載のデータ処理方法であって、
前記拡張ユニットは、
予め設定されたテーブルを参照することで前記入力データの処理を実施するか否かを設定し、前記実施しないと設定された場合、前記入力データに対して前記第1処理および第2処理を実施しない未処理データを前記車載機に送信し、
前記実施すると設定された場合、前記入力データを前記第1処理および前記第2処理を実施し、前記第2処理後のデータを前記車載機に送信し、
前記車載機は、
前記未処理データを受けると、前記第1処理、前記第2処理、前記第3処理を実施し、前記第3処理後のデータをサーバに提供し、
前記第2処理後のデータを受けると、前記第3処理を実施し、前記第3処理後のデータをサーバに提供する
データ処理方法。 - 請求項2から請求項4の何れか1項に記載のデータ処理方法であって、
前記拡張ユニットは、
前記入力データの種別に応じて、前記第1処理を省略する場合がある
データ処理方法。 - 請求項5に記載のデータ処理方法であって、
前記拡張ユニットは、
前記車載機との間の通信に用いられる通信プロトコルが予め設定されたプロトコルである場合に、前記第1処理を省略する
データ処理方法。 - 請求項5に記載のデータ処理方法であって、
前記拡張ユニットは、
前記車載機との接続に用いられるコネクタの種別が予め設定された種別である場合に、前記第1処理を省略する
データ処理方法。 - 請求項5に記載のデータ処理方法であって、
前記拡張ユニットは、
前記入力データに含まれる画像の種別が予め設定された種別である場合に、前記第1処理を省略する
データ処理方法。 - 請求項1から請求項8までのいずれか1項に記載のデータ処理方法であって、
前記第3処理後のデータを、構造化する第4処理を実施し、
前記第4処理後のデータをサーバに提供する
データ処理方法。 - 請求項9に記載のデータ処理方法であって、
前記第4処理後のデータをサーバに定期的に提供する
データ処理方法。 - 請求項1から請求項10の何れか1項に記載のデータ処理方法であって、
前記入力データとして、カメラによる撮像データを取得し、前記第1処理として、前記撮像データから物体を認識する処理を実施する
データ処理方法。 - 請求項1から請求項11の何れか1項に記載のデータ処理方法であって、
前記入力データとして音声データを取得し、前記第1処理として、前記音声データから音声の内容を認識する処理を実施する
データ処理方法。 - 請求項1から請求項12の何れか1項に記載のデータ処理方法であって、
前記入力データとして、車両の周囲の障害物を検知する障害物センサによる障害物データを取得し、前記第1処理として、前記障害物データから少なくとも障害物の位置を認識する処理を実施する
データ処理方法。 - 請求項1から請求項13の何れか1項に記載のデータ処理方法であって、
前記入力データとして、近距離デバイスから得られるデバイスデータを取得し、前記第1処理として、前記入力データから予め設定された近距離デバイスから得られたデバイスデータを抽出する処理を実施する
データ処理方法。 - 請求項1から請求項14の何れか1項に記載のデータ処理方法であって、
前記入力データとして、クラウドサーバから得られるクラウドデータを取得し、前記第1処理として、前記入力データから予め設定されたクラウドサーバから得られたクラウドデータを抽出する処理を実施する
データ処理方法。 - 請求項1から請求項15の何れか1項に記載のデータ処理方法であって、
前記入力データとして、通信プロトコルCAN(登録商標)によるCANデータを取得し、前記第1処理として、前記入力データから予め設定された種別のCANデータを抽出するCANデータ抽出処理を実施する
データ処理方法。 - 請求項1から請求項16の何れか1項に記載のデータ処理方法であって、
前記第2処理として、前記第1処理後のデータを、CANデータに準じたデータ形式に変換する処理を実施する
データ処理方法。 - 請求項1から請求項17の何れか1項に記載のデータ処理方法であって、
前記第2処理として、前記第1処理後のデータを、データ種別を示すID、データ量の情報、実データ、誤り訂正符号を含むデータに変換する処理を実施する
データ処理方法。 - 通信機を介してクラウドサーバと通信可能な車載機(2A)と、前記車載機に対して着脱自在に構成された拡張ユニット(2B)とを備える通信システム(1)であって、
入力データの提供元となる提供元機器から前記入力データを取得するように構成された取得部(155A)と、
前記入力データに対して、よりデータ量が少なくなるような処理である第1処理を実施するように構成された第1処理部(20B,156B)と、
前記第1処理後のデータを、予め設定された形式のデータに変換する第2処理を実施するように構成された第2処理部(20C,156C)と、
前記第2処理後のデータを、正規化データに変換する第3処理を実施するように構成された第3処理部(20D)と、
前記第3処理後のデータに基づいて、車両データをクラウドサーバに提供するように構成された提供部(13)と、
を備える通信システム。 - 通信機を介してクラウドサーバと通信可能な車載機(2A)と、前記車載機に対して着脱自在に構成された拡張ユニット(2B)と、前記拡張ユニットへデータを出力する電子制御装置(210)と、を備える通信システム(1)であって、
他の電子制御装置から送信されたデータを前記拡張ユニットへ中継するように構成された中継部(213)と、
前記中継部から送信された入力データを取得するように構成された取得部(155A)と、
前記入力データに対して、よりデータ量が少なくなるような処理である第1処理を実施するように構成された第1処理部(20B,156B)と、
前記第1処理後のデータを、予め設定された形式のデータに変換する第2処理を実施するように構成された第2処理部(20C,156C)と、
前記第2処理後のデータを、正規化データに変換する第3処理を実施するように構成された第3処理部(20D)と、
前記第3処理後のデータに基づいて、車両データをクラウドサーバに提供するように構成された提供部(13)と、
を備える通信システム。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202280046981.6A CN117597904A (zh) | 2021-07-02 | 2022-06-22 | 数据处理方法以及通信系统 |
JP2023531861A JPWO2023276816A1 (ja) | 2021-07-02 | 2022-06-22 | |
US18/397,364 US20240127637A1 (en) | 2021-07-02 | 2023-12-27 | Data processing method and communication system |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2021110910 | 2021-07-02 | ||
JP2021-110910 | 2021-07-02 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US18/397,364 Continuation US20240127637A1 (en) | 2021-07-02 | 2023-12-27 | Data processing method and communication system |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2023276816A1 true WO2023276816A1 (ja) | 2023-01-05 |
Family
ID=84691792
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2022/024888 WO2023276816A1 (ja) | 2021-07-02 | 2022-06-22 | データ処理方法、および通信システム |
Country Status (4)
Country | Link |
---|---|
US (1) | US20240127637A1 (ja) |
JP (1) | JPWO2023276816A1 (ja) |
CN (1) | CN117597904A (ja) |
WO (1) | WO2023276816A1 (ja) |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2007062481A (ja) * | 2005-08-30 | 2007-03-15 | Denso Corp | 車載用電子機器の接続システム |
JP2017182418A (ja) * | 2016-03-30 | 2017-10-05 | マツダ株式会社 | 運転支援装置及び運転支援システム |
JP2018005848A (ja) * | 2016-07-08 | 2018-01-11 | トヨタ自動車株式会社 | 車載通信装置 |
KR20180098062A (ko) * | 2017-02-24 | 2018-09-03 | 주식회사 포키비언 | 차량데이터 계층화 및 적응형 데이터 전송 장치 및 방법 |
JP2020024685A (ja) * | 2018-08-06 | 2020-02-13 | デンソー インターナショナル アメリカ インコーポレーテッド | モバイルネットワークデバイスおよびモバイルネットワークデバイスの操作方法 |
JP2020101980A (ja) * | 2018-12-21 | 2020-07-02 | トヨタ自動車株式会社 | 情報取得装置、情報取得方法、プログラム |
-
2022
- 2022-06-22 WO PCT/JP2022/024888 patent/WO2023276816A1/ja active Application Filing
- 2022-06-22 JP JP2023531861A patent/JPWO2023276816A1/ja active Pending
- 2022-06-22 CN CN202280046981.6A patent/CN117597904A/zh active Pending
-
2023
- 2023-12-27 US US18/397,364 patent/US20240127637A1/en active Pending
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2007062481A (ja) * | 2005-08-30 | 2007-03-15 | Denso Corp | 車載用電子機器の接続システム |
JP2017182418A (ja) * | 2016-03-30 | 2017-10-05 | マツダ株式会社 | 運転支援装置及び運転支援システム |
JP2018005848A (ja) * | 2016-07-08 | 2018-01-11 | トヨタ自動車株式会社 | 車載通信装置 |
KR20180098062A (ko) * | 2017-02-24 | 2018-09-03 | 주식회사 포키비언 | 차량데이터 계층화 및 적응형 데이터 전송 장치 및 방법 |
JP2020024685A (ja) * | 2018-08-06 | 2020-02-13 | デンソー インターナショナル アメリカ インコーポレーテッド | モバイルネットワークデバイスおよびモバイルネットワークデバイスの操作方法 |
JP2020101980A (ja) * | 2018-12-21 | 2020-07-02 | トヨタ自動車株式会社 | 情報取得装置、情報取得方法、プログラム |
Also Published As
Publication number | Publication date |
---|---|
US20240127637A1 (en) | 2024-04-18 |
CN117597904A (zh) | 2024-02-23 |
JPWO2023276816A1 (ja) | 2023-01-05 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN106453465B (zh) | 用于车辆控制器与外部资源之间交互工作的系统和方法 | |
WO2023023975A1 (zh) | 一种芯片、芯片制造方法、以及相关装置 | |
CN109246126B (zh) | 车载自动驾驶系统的数据通信方法及装置 | |
US20170339056A1 (en) | Remote vehicle data collection system | |
US10306689B2 (en) | Systems and methods for shared mixed reality experiences using digital, physical, temporal or spatial discovery services | |
CN113156916A (zh) | 控制器系统及控制方法 | |
CN111124443A (zh) | 车辆、车机设备及车载仪表升级方法 | |
US20150025733A1 (en) | Vehicle control device and method | |
CN115334110A (zh) | 用于车辆控制的系统架构、通信方法、车辆、介质及芯片 | |
CN114461070A (zh) | 用于实现车载虚拟现实的系统、方法和车辆 | |
JP5370341B2 (ja) | 通信装置及びデータ通信システム | |
WO2023276816A1 (ja) | データ処理方法、および通信システム | |
WO2023276815A1 (ja) | 拡張ユニット、車載機ユニット、および車両システム | |
WO2021243602A1 (zh) | 一种车辆控制系统和子控制单元 | |
CN115297461B (zh) | 数据交互方法、装置、车辆、可读存储介质及芯片 | |
KR20150005209A (ko) | 차량과 휴대용 단말 간의 연동 기능을 갖는 장치 및 그 동작 방법 | |
CN111026475A (zh) | 车辆、车机设备及其基于地图软件的车辆服务处理方法 | |
CN207594873U (zh) | 一种基于BroadR-Reach以太网的汽车车机原型系统 | |
US10661732B2 (en) | In-vehicle relay device | |
WO2018192585A1 (zh) | 传输方法和传输装置 | |
WO2024026593A1 (zh) | 一种协同控车方法及相关装置 | |
WO2021073501A1 (zh) | 车内业务切片的资源配置方法及装置、系统 | |
US20240134675A1 (en) | Display apparatus for vehicle | |
JP2024511005A (ja) | データ伝送方法、装置及びシステム | |
TW202240475A (zh) | 資訊處理裝置、資訊處理系統、資訊處理方法及記錄媒體 |
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: 22832964 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2023531861 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 202280046981.6 Country of ref document: CN |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 22832964 Country of ref document: EP Kind code of ref document: A1 |