Information processing device, information processing method, and information processing system

The information processing device and method facilitate safe and timely program updates for vehicles during maintenance, addressing the challenge of updating vehicle programs during operation.

JP7585996B2Active Publication Date: 2024-11-19TOYOTA JIDOSHA KK
View PDF 8 Cites 0 Cited by

Patent Information

Application Number
JP2021108005
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2021-06-29
Publication Date
2024-11-19
Estimated Expiration
2041-06-29

AI Technical Summary

Technical Problem

Existing systems fail to update vehicle programs at appropriate timings, particularly during operation, which can lead to safety and efficiency issues.

Method used

An information processing device and method that plans program updates for vehicles during maintenance periods when they are stopped, utilizing a control center to coordinate with vehicle centers and mobile units to ensure safe and timely updates.

Benefits of technology

Enables safe and timely updates of vehicle programs, avoiding operational disruptions and ensuring the vehicle's safety and efficiency by performing updates when the vehicle is stationary.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007585996000001
    Figure 0007585996000001
  • Figure 0007585996000002
    Figure 0007585996000002
  • Figure 0007585996000003
    Figure 0007585996000003
Patent Text Reader

Abstract

To allow for updating a program installed in a vehicle at appropriate times.SOLUTION: An information processing device 4 provided herein comprises a control unit 201 configured to perform steps of acquiring information on update of a program installed in a vehicle 2, and making a plan to update the program while the vehicle 2 is stationary in an operation plan on the basis of the information on the update.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates to an information processing device, an information processing method, and an information processing system. [Background technology]

[0002] Conventionally, there is an operation schedule determination device that acquires schedule information of a plurality of users and attribute information indicating the interrelationships between at least some of the plurality of users, and determines an operation schedule for an autonomous vehicle based on the acquired information. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] International Publication No. 2018 / 230646 [Patent Document 2] JP 2018-132979 A Summary of the Invention [Problem to be solved by the invention]

[0004] An object of the present disclosure is to provide an information processing device, an information processing method, and an information processing system that are capable of updating a program implemented in a vehicle at an appropriate timing. [Means for solving the problem]

[0005] One aspect of the present disclosure is an information processing device that includes a control unit that acquires information regarding updates to a program implemented in a vehicle, and, based on the information regarding the update, creates a plan to update the program while the vehicle is stopped in an operation plan.

[0006] The present disclosure can include, as other aspects, an information processing method, a computer program, a recording medium on which a computer program is recorded, and an information processing system having similar features to the above-described information processing device. Effect of the Invention

[0007] According to the present disclosure, it becomes possible to perform updates to programs installed in a vehicle at appropriate times. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating an information processing system according to the first embodiment. [Diagram 2] FIG. 2 is a diagram illustrating an example of the configuration of a terminal device. [Diagram 3] FIG. 3 is an example of a release NOTE sent from the vehicle center to the control center. [Figure 4] FIG. 4 shows an example of operation schedule data that the control center distributes to each mobile unit. [Diagram 5] FIG. 5 is a diagram illustrating an example of status information of each moving object held by the control center. [Figure 6] FIG. 6 is a flowchart showing an example of processing by the control center. [Figure 7] FIG. 7 is a flowchart showing an example of processing by the control center. [Figure 8] FIG. 8 is a flowchart showing an example of processing by the Central ECU of the vehicle. [Figure 9] FIG. 9 is a flowchart showing an example of a process performed by the vehicle center. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] The information processing device according to the embodiment includes a control unit. The control unit acquires information about updates to a program installed in a vehicle, and performs an operation plan based on the information about the updates. Develop and implement a plan to update programs while vehicles are parked.

[0010] Here, the program is preferably a program related to vehicle driving control, but may be other programs. Installed in a vehicle includes being used or executed by an on-board computer provided in the vehicle.

[0011] Hereinafter, an information processing device, an information processing method, and an information processing system according to embodiments will be described with reference to the drawings. The configurations of the embodiments are examples. The configurations of the embodiments can be combined as appropriate.

[0012] <System configuration> 1 is a diagram illustrating an information processing system 100 of the first embodiment. The information processing system 100 has a mobile object 2, a computer at a vehicle center 3, and a computer at a control center 4. Hereinafter, the computer at the vehicle center 3 and the computer at the control center 4 are also simply referred to as the vehicle center 3 and the control center 4. The mobile object 2, the vehicle center 3, and the control center 4 are connected by a network N.

[0013] The network N includes a wired network and a wireless network. The wired network is, for example, also called a core network or a backbone, and is a broadband network exemplified by an optical fiber network. The wireless network is, for example, a Long Term Evolution (LTE), a fifth generation mobile communication system (5G), a sixth generation mobile communication system ( This includes mobile phone networks such as 6G.

[0014] The moving object 2 is, for example, a vehicle. The vehicle may be four-wheeled, three-wheeled, or two-wheeled. The vehicle may be driven by an engine or a motor. The vehicle may be equipped with an automatic driving system capable of autonomous driving or automatic driving. The moving object 2 is an example of a vehicle capable of communicating with a control center 4, which is an information processing device.

[0015] In FIG. 1, the moving object 2 has a Data Communication Module (DCM) 21 and a Central Electrical Control Unit (Central ECU) 22. The moving object 2 further has a User Interface (UIF) device 23, a preventive safety device 24, and an Advanced Drive System (A The system includes a data set (DS) 25 and an audio / video / NAVI device 26.

[0016] The DCM 21 is a communication device that accesses the network N and communicates with other moving bodies, the vehicle center 3, the control center 4, etc. The DCM 21 is capable of wireless communication via a mobile communication network.

[0017] The Central ECU 22 manages each device in the mobile object 2. The Central ECU 22 includes, for example, a processor and a memory. The processor executes a computer program (hereinafter, simply referred to as a "program") in the memory to perform processing as the Central ECU 22. The Central ECU 22 is implemented, for example, by an ECU installed in each device in the moving object 2. The Central ECU 22 updates the programs being executed and manages the progress of the updates. Detects errors when updating programs and executes processing when errors occur. Central The combination of the ECU 22 and the DCM 21 is an example of a computer installed in a vehicle (an on-board computer).

[0018] The UIF device 23 provides a user interface when updating a program executed by an ECU mounted on each device in the mobile object 2. The user interface is also called a reprogramming Human Machine Interface (repro HMI). The central ECU 22 and the UIF 23 also have an ECU similar to the central ECU 22. The ECUs etc. in the device 23 can be called a common ECU group.

[0019] The preventive safety device 24 has an ECU built in and executes collision avoidance support processing by program processing. The preventive safety device 24 executes, for example, collision avoidance support, lane departure warning, automatic high beam, radar cruise control, etc., based on signals from sensors such as radar and cameras.

[0020] ADS25 is connected to Spatial Information Service (SIS) 27 and Advanced Drive Extension (ADX) 28. ADS25, SIS27 and ADX2 The ADS25, for example, detects the presence of a LiDAR sensor and detects the presence of a LiDAR sensor. The detection signal is used to detect vehicles or three-dimensional objects around the moving body 2, estimate the position of the moving body 2 itself, and perform motion control.

[0021] The SIS 27 provides the attitude of the moving object 2 itself, its position on a map, and the like to the ADS 25. That is, the SIS 27 obtains position information from a global navigation satellite system (GNSS) or a global positioning system (GPS). The SIS 27 acquires a six-axis acceleration signal from the gyro sensor, route information or map information from the navigation system, etc. Based on the acquired information, the SIS 27 calculates the attitude of the moving object 2 itself and its position on the map, etc. The ADX 28 applies an Artificial Intelligence (AI) system. It uses this to recognize and process information from the various sensors mentioned above, and notify the ADS25 of the processing results.

[0022] The audio / video / NAVI device 26 is connected to the Rear Seat Entertainment (RSE) 2B. The audio / video / NAVI device 26 and the RSE 2B each have an ECU built in, and provide the user of the mobile object 2 with various functions such as audio, video, and map information through program processing.

[0023] 1, the audio / video / NAVI device 26 can further be connected to, for example, an AMP 29 for signal amplification and an operation unit 2A. The operation unit 2A is, for example, a touch display that displays information to the user and accepts operations from the user. If the mobile object 2 is a vehicle with a back seat, the RSE 2B independently provides television broadcasts and Digital Versatile Disc (DVD) images to the user seated in the back seat of the vehicle interior.

[0024] The ECUs of the above-mentioned preventive safety device 24, ADS 25, and audio / video / navigation device 26, and the ECUs of each device connected to them, can be called an individual ECU group. The Central ECU 22 manages the progress of updates to the programs mounted in the individual ECU group and errors during updates. The programs used (executed by the ECUs) in each ECU of the preventive safety device 24, ADS 25, SIS 27, and audio / video / navigation device 26 are examples of programs related to the movement control of a moving object (vehicle driving control).

[0025] The vehicle center 3 is operated by an organization such as a company that sells or maintains the mobile body 2, or by a company commissioned by that company. The vehicle center 3 manages parts such as ECUs installed in all mobile bodies sold or maintained by these companies. The vehicle center 3 also manages the types and versions of programs executed in each of these ECUs. The vehicle center 3 distributes update data for updating programs to the mobile bodies 2, etc. The update data can also be simply called an update program. Each ECU included in the common ECU group and individual ECU group is an example of an "on-board computer."

[0026] The control center 4 manages the operation and maintenance of each of the moving objects 2. is, for example, a computer of an FMS company that provides a fleet management service (FMS). The control center 4 creates an operation schedule, for example, of the mobile object 2 that is operated periodically, including the operation start time, operation, operation end time, and maintenance time slot. The control center 4 updates the operation schedule in a timely manner, distributes it to the mobile object 2, and manages the operation of the mobile object 2. The control center 4 also manages a usage schedule for a service that is used irregularly, for example, a sharing schedule including the operation start date and time, operation end date and time, and maintenance date and time for the mobile object 2 in a ride sharing service. The control center 4 also manages a rental schedule for the mobile object 2 that is used for rental. Hereinafter, schedules related to the operation, use, rental, etc. of the mobile object 2 are collectively referred to simply as an operation schedule. Furthermore, in the case where the mobile object 2 is an electric vehicle, the control center 4 incorporates a schedule for charging the mobile object 2 into the operation schedule and manages it.

[0027] As described above, the moving object 2 is equipped with various parts each having an ECU built in. The programs executed by the ECU in each part are updated in accordance with improvements or malfunction countermeasures. Meanwhile, safety is required for the moving object 2. For that reason, updates to the programs for the ECUs installed in the moving object 2 are performed during the maintenance period when the moving object 2 is stopped moving (when the moving object 2 is stopped).

[0028] The vehicle center 3 notifies the control center 4 of the latest update contents and update schedule for the program of each ECU in the form of a release note. When the control center 4 receives the release note, it incorporates the update schedule for the program of each ECU into the operation schedule of each mobile object 2. In other words, the control center 4 plans the operation schedule of each mobile object 2 so that the program update of each ECU is completed during a maintenance period when each mobile object 2 is not running. The control center 4 notifies the mobile object 2 of the confirmed operation schedule (planned distribution in FIG. 1) and executes the program update of each ECU.

[0029] The DCM 21 of the moving object 2 communicates with the vehicle center 3 and the control center 4 via the network N. The DCM 21 receives an operation schedule including a program update plan from the control center 4 (planned distribution in FIG. 1). The Central ECU 22 is connected to the DCM 21 via a network within the moving object exemplified by, for example, Ethernet (registered trademark).

[0030] The DCM 21 accesses the vehicle center 3 according to the received operation schedule, acquires update data for updating the programs, and transfers it to the Central ECU 22. The Central ECU 22 updates the programs of each ECU including the common ECU group and the individual ECU group during a maintenance period when the mobile object 2 is stopped. When the Central ECU 22 completes updating each ECU, the DCM 21 notifies the control center 4 of a completion report.

[0031] The UIF device 23 is connected to the Central ECU 22 by a network within the vehicle, such as a Controller Area Network (CAN (registered trademark)). The UIF device 23 may receive a confirmation input by a user's operation via the repro HMI. That is, the Central ECU 22 may request the user to confirm the start of the program update using the UIF device 23, and start the update after the confirmation is obtained. The UIF device 23 itself also obtains update data from the Central ECU 22 and updates the program of the UIF device 23.

[0032] The preventive safety device 24 is, for example, a Controller Area Network with Flexible Data rate ( The preventive safety device 24 is connected to the Central ECU 22 via a network in the moving object 2, such as CAN-FD (CAN is a registered trademark). The preventive safety device 24 receives the update data of the system and executes the update. Then, the preventive safety device 24 reports the status of the update to the Central ECU 22.

[0033] The ADS 25 and the audio / video / NAVI device 26 are exemplified by, for example, Ethernet (registered trademark). The ADS 25 and the audio / video / navi device 26 are connected to the Central ECU 22 via a network within the vehicle. The ADS 25 and the audio / video / navi device 26 each receive program update data from the Central ECU 22. Then, the ADS 25 and the audio / video / navi device 26 each execute program updates for themselves and the ECUs under their control. The ADS 25 and the audio / video / navi device 26 report statuses associated with the updates to the Central ECU 22.

[0034] <Example of vehicle center and control center configuration> 2 is a diagram showing a configuration example of a terminal device 200 capable of operating as the vehicle center 3 or the control center 4. As the terminal device 200, for example, a general-purpose information processing device (computer) such as a personal computer (PC) or a workstation, or a dedicated information processing device such as a server machine can be applied. The terminal device 200 has a communication function and can be connected to the network N by wire or wirelessly.

[0035] 2, the terminal device 200 includes a processor 201 as a processing unit or control unit (controller), a storage device 202, a communication device 203, an input device 204, and an output device 205, which are interconnected via a bus 206. Each of the vehicle center 3 and the control center 4 may be one terminal device 200 or a collection (cloud) of two or more terminal devices 200.

[0036] The storage device 202 includes a main storage device and an auxiliary storage device. The main storage device is used as a storage area for programs and data, a program development area, a program work area, and a buffer area for communication data. The main storage device is configured with a RAM (Random Access Memory) or a combination of a RAM and a ROM (Read Only Memory). The auxiliary storage device is used as a storage area for data and programs. A non-volatile storage medium can be applied as the auxiliary storage device. Examples of non-volatile storage media include a hard disk, a Solid State Drive (SSD), a flash memory, and an EEPROM (Electrically Erasable Programmable Read-Only Memory).

[0037] The communication device 203 is a circuit that performs communication processing and operates as a transmitting unit and a receiving unit (communication unit). For example, the communication device 203 is a network interface card (NIC). The communication device 203 also supports wireless communication (LTE, 5G, wireless LAN (Wi-Fi), B The communication device 203 may be a wireless communication circuit that performs wireless communication (such as LE). Also, the communication device 203 may include both a circuit that performs wired communication processing and a wireless communication circuit.

[0038] The input device 204 includes keys, buttons, a pointing device, a touch panel, etc., and is used to input information. The input device 204 may include a microphone (audio input device). The output device 205 is, for example, a liquid crystal display or an organic EL display, etc., and displays information and data. The output device 205 may include a speaker (audio output device).

[0039] The processor 201 is, for example, a CPU (Central Processing Unit). The processor 201 executes various programs stored in the storage device 202 to perform various processes.

[0040] For example, the processor 201 of the terminal device 200 operating as the vehicle center 3 executes a program to cause the terminal device 200 to operate as the above-mentioned vehicle center 3. In addition, the processor 201 of the terminal device 200 operating as the control center executes a program to cause the terminal device 200 to operate as the control center 4.

[0041] In addition, even if a plurality of CPUs are used as the above-mentioned processor 201, it is still considered to be a multi-core type. At least a part of the processing performed by the CPU may be performed by a CPU such as a DSP (Digital Signal Processor) or a GPU (Graphical Processing Unit). The processing performed by the CPU may be performed by a processor other than the CPU. Furthermore, at least a part of the processing performed by the CPU may be performed by a dedicated or general-purpose integrated circuit (hardware). The integrated circuit may be an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Array). The CPU may include a microcontroller, a programmable gate array, etc. Alternatively, at least a part of the processing performed by the CPU may be executed by a combination of a processor and an integrated circuit. The combination is called, for example, a microcontroller (MCU), a system-on-a-chip (SoC), a system LSI, or a chipset.

[0042] <Data example> Fig. 3 is an example of a release NOTE transmitted from the vehicle center 3 to the control center 4. In the example shown in Fig. 3, the release NOTE specifies values ​​for keywords in the format of "keyword:value". Also, in the example of Fig. 3, the "keyword:value" pairs are enclosed in curly brackets "{}" and described hierarchically.

[0043] That is, from FIG. 3, it can be seen that the vehicle type of the moving object 2 is E-palette G0. It can also be seen that the system version to be released is V07-01. It can also be seen that the release date is ddmmmyyyy, which is the release NOTE of the program. It can be seen that the system version is the version given to the entire group of programs installed in the mobile unit 2. In addition, this release NOTE describes the type of program, version, and data size (volume) of program update data (update data) for each ECU type. For example, the version of PC1, which is a program for the Central ECU, is V07-01-1, and the data size is V1M. It turns out to be B.

[0044] The release note is not limited to the format shown in FIG. 3. For example, the release note may be written in a prescribed format such as HyperText Markup Language (HTML) or Extensible Markup Language (XML). The release note may be described in a table format in which records each including a plurality of elements are arranged. The release note may also include information indicating the importance of the program update. The importance may be indicated, for example, by "normal" or "high", and the Central ECU 22 may be configured to perform an operation different from that for a "normal" update, that is, an update with high importance.

[0045] FIG. 4 is an example of data of an operation plan (operation schedule; distributed by "Plan distribution" in FIG. 1) that the control center 4 distributes to the mobile objects 2 under its management. An operation plan is created for each mobile object 2. For this reason, the operation plan includes a mobile object ID for identifying the mobile object 2. Also, in the data example of FIG. 4, the operation plan is created for each day and includes the year, month, and date. Furthermore, in the data example of FIG. 4, the operation plan specifies the operation of the mobile object 2 for each time period, as well as schedules for maintenance, etc.

[0046] For example, on the date DDMMMYYYY, maintenance of the mobile unit 2 is carried out from 0:00 to 9:00. The maintenance includes charging the battery of the mobile unit ID: E-PALETTE EV1 and Includes program updates. Mobile ID: E-PALETTE EV1 operates from 9:00 to 11:00. Vehicle ID: E-PALETTE EV1 will stop operating between 11:00 and 13:00. The vehicle stops, goes into maintenance mode, and the battery is charged. The vehicle ID: E-PALETTE EV1 is 13: It operates from 00 to 23:00, and stops operating after 23:00 and goes into maintenance mode. Note that in the example of Figure 4, the details of the maintenance schedule and operation schedule from 13:00 to 22:00 are omitted.

[0047] As shown in FIG. 4, program update and download of program update data are performed during the time period when the mobile object 2 is in a maintenance state, that is, when the vehicle is stopped. In the example shown in FIG. 4, download of program update data and program update are planned for the maintenance state time period from 0:00 to 7:59. However, acquisition of update data by download is not essential, and update data may be read from a storage medium connected to the Central ECU 22. In this case, it is not necessary to define a download schedule. Also, the download time and the program update time may be defined (set) in different time periods sandwiched between the operation state (driving) time. For example, download may be set to the time period from 0:00 to 7:59, and program update may be set to the time period from 11:00 to 12:59.

[0048] The data structure of the operation plan created by the control center 4 is not limited to the data example shown in FIG. 4. For example, in FIG. 4, the time period is defined in hourly increments. However, the time period may be defined in minute increments. Also, the operation plan does not have to be created for each day, and may be created, for example, for each week. Also, the operation plan may be created for each month. Also, the operation plan may be created for weekdays (Monday to Friday), Saturdays, and holidays.

[0049] Fig. 5 is a diagram illustrating an example of status information of each mobile object 2 held by the control center 4. The status information records the current program update status of the mobile object 2, the battery status, etc. The status information is saved in a predetermined database (stored in the storage device 202) of the control center 4. In the example shown in Fig. 5, the status information includes a mobile object ID, the last update date, the system version of the entire group of programs installed in the mobile object 2, the date and time of the completion of the previous operation, and the battery status.

[0050] Here, the moving object ID is identification information that uniquely identifies the moving object 2, as in FIG. 4. The last update date is the date when the moving object 2 (the moving object ID of E-PALETTE EV1 in FIG. 5) last updated the moving object 2. The system version of the programs is the version of the entire program group after updating in the mobile object 2, as explained in FIG.

[0051] However, the state information is not limited to this configuration. For example, the state information may hold the current version of each program (e.g., version V07-01-1 of each program in FIG. 3) for each ECU of each part. When the control center 4 receives a report of the completion of the update from the moving object 2, the control center 4 records the last update date and time and the system version of the entire group of programs after the update in the state information.

[0052] The last trip completion date and time was for mobile unit 2 (in Figure 5, the mobile unit ID is E-PALETTE EV1). The battery status is the current state of charge (State Of Charge (SOC)) of the battery. The battery charge state is obtained together with the trip completion report and recorded in the status information "battery state." The battery charge state (SOC) is shown, for example, as a percentage of the remaining power compared to the amount of power when fully charged.

[0053] <Processing at the control center> 6 and 7 are flowcharts showing an example of processing by the processor 201 (the processor 201 of the control center 4) of the terminal device 200 operating as the control center 4. The processing shown in Fig. 6 and Fig. 7 may be performed for each moving object 2 to be managed, or for each group to which two or more moving objects 2 grouped by an appropriate method belong.

[0054] In FIG. 6, in step S001, the processor 201 acquires the release NOTE that the control center 4 receives from the vehicle center 3 via the network N, and identifies a program to be updated from the system version in the release NOTE.

[0055] In step S002, the processor 201 determines whether the release NOTE contains information indicating an update of a program with high importance. If it is determined that the release NOTE contains information indicating an update of a program with high importance, the process proceeds to step S009, and if not, the process proceeds to step S003.

[0056] In step S003, the processor 201 identifies the distribution start date and time of the program update data from the release date in the release NOTE. In step S004, the processor 201 acquires, from the storage device 202, operation plan data of the moving object 2 for a predetermined date after the distribution start date and time (for example, the distribution start date or the day after).

[0057] In step S005, the processor 201 identifies the size of the update data, that is, the size of the data to be downloaded, from the release NOTE.

[0058] In step S006, the processor 201 calculates the time required to download the update data from information indicating the size of the update data and the communication performance (throughput) of the DCM 21. The processor 201 also calculates the time required to update the program using the update data from information indicating the size of the update data and the performance of the Central ECU 22 (amount of data that can be processed per unit time).

[0059] For example, if the size of the update data (download size) is 1 GB and the throughput of the DCM 21 is 40 Mbps, the communication time is 1 GB / 40 Mbps = 200 seconds. This communication time is the time required to download the update data. Also, if the Central ECU 22 can process 1 MB of data per second, the time required to update (rewrite) the program (update time) is 1 GB / (1 MB / s) = 1000 seconds. The communication time is an example of the "second time length", and the update time is an example of the "first time length".

[0060] In step S007, the processor 201 sets the download plan of the update data and the program update plan in the operation plan. That is, the processor 201 identifies a maintenance state time zone for the day from the operation plan data for the specified day acquired in step S003, and identifies a maintenance state time zone having a time length equal to or longer than the total value of the communication time and the update time described above. Then, the processor 201 sets a specified time in the identified time zone (for example, the same time as the start time of the time zone, or a time after a specified time has elapsed from the start time) as the download start time. Also, a time after the download end time is set as the update start time. At this time, the update start time is set so that the update end time falls within the specified time zone. Here, if the time required for download and update does not fall within a certain maintenance state time zone, the processor 201 sets the download during a certain maintenance state time zone and the update during another maintenance state time zone. In this way, the processor 201 sets (draws up) a plan for downloading and updating in the operation plan of the moving body 2.

[0061] In step S008, the processor 201 generates an instruction for the mobile object 2. The instruction for the mobile object 2 includes an instruction to start downloading the update data at the download start time, and an instruction to start updating the program using the update data at the update start time. The instruction for the mobile object 2 is sent from the communication device 203 to the network N, and is received by the DCM 21 of the mobile object 2.

[0062] In steps S009 and S010, the processor 201, similarly to steps S003 and S004, identifies the distribution start date and time of the update data from the release note, and acquires operation plan data for a predetermined day after the distribution start date and time.

[0063] In step S011, the processor 201 determines to stop the operation of the moving object 2 according to the operation plan for a predetermined day (stop of the operation plan). As the predetermined day, a day including the distribution start date and time of the update data may be preferentially selected.

[0064] In step S012, the processor 201 creates a plan for downloading update data and updating a program for the mobile object 2 on a predetermined day. For example, assume that the distribution start date and time of the update data is 9:30, and the operation plan for the predetermined day including the distribution start date and time is a plan to run the mobile object 2 between 9:00 and 10:59, as in the example shown in FIG. 4. In this case, the processor 201 stops the operation plan for the predetermined day, and sets a time period after 9:30 on the predetermined day during which the mobile object 2 continues to maintain a stopped state. Then, the processor 201 creates a plan for downloading and updating (setting the download start time and update start time) during that time period.

[0065] In step S013, the processor 201 selects an alternative moving body (alternative vehicle). The alternative moving body is a moving body (vehicle) that operates according to an operation plan in place of the moving body 2 whose operation has been stopped. The storage device 202 has a program updated and stores information on alternative moving bodies that are not scheduled to operate on a specified day in advance, and the processor 201 determines a moving body specified by the information as the alternative moving body.

[0066] In step S014, the processor 201 assigns an operation plan for a predetermined day to the alternative moving body. For example, if the moving body 2 whose operation has been stopped is scheduled to operate as shown in Fig. 4 after 9:00, the processor 201 assigns an operation plan for after 9:00 to the alternative moving body. At this time, the processor 201 may assign the entire operation plan for the predetermined day.

[0067] In step S015, the processor 201 generates an instruction for the moving object 2. The instruction for the moving object 2 includes an instruction to change the operation plan indicating the suspension of operation on a predetermined day, an instruction to start downloading update data at the download start time on the predetermined day, and an instruction to start updating the program using the update data at the update start time. The instruction for the moving object 2 is sent from the communication device 203 to the network N and received by the DCM 21 of the moving object 2.

[0068] In step S016, the processor 201 generates an instruction for the alternative moving body. The instruction for the alternative moving body includes an instruction to change the operation plan indicating the operation content for the specified day. The instruction for the alternative moving body is sent from the communication device 203 to the network N and received by the alternative moving body. The alternative moving body changes the operation plan for the specified day and operates in place of the moving body 2 on the specified day.

[0069] <Processing in mobile units and vehicle centers> Fig. 8 is a flowchart showing an example of processing by the Central ECU 22 (hereinafter, referred to as "ECU 22") of the moving object 2. Fig. 9 is a flowchart showing an example of processing by the vehicle center 3.

[0070] In step S101, the ECU 22 acquires an instruction relating to download and update, which the DCM 21 has received from the control center 4 via the network N.

[0071] In step S102, the ECU 22 determines whether or not the instruction from the control center 4 includes an instruction to change the operation plan. If so, the process proceeds to step S103; otherwise, the process proceeds to step S104.

[0072] In step S103, the ECU 22 changes the operation plan. That is, the ECU 22 changes the operation plan for the predetermined day specified in the change instruction for the operation plan in accordance with the change instruction. As a result, the original operation plan for the predetermined day is stopped.

[0073] In step S104, the ECU 22 performs a reservation setting for starting download of the update data at the download start time on the predetermined date included in the instruction from the control center 4. The ECU 22 also performs a reservation setting for starting update of the program using the update data at the update start time on the predetermined date.

[0074] In step S105, the ECU 22 waits for the download start time to arrive, and when it is determined that the download start time has arrived, downloads the update data (step S106). That is, the ECU 22 generates a message requesting download of the update data, and the download request is sent from the DCM 21 to the network N and received by the vehicle center 3.

[0075] In the vehicle center 3, the processor 201 of the terminal device 200 operating as the vehicle center 3 (the processor 201 of the vehicle center 3) receives the download request via the communication device 203 (step S201 in FIG. 9).

[0076] The processor 201 of the vehicle center 3 performs control to read out the update data corresponding to the download request from the storage device 202 of the vehicle center 3 based on the information indicating the program update data included in the download request. The processor 201 of the vehicle center 3 also performs control to transmit the update data to the mobile object 2 (step S202 in FIG. 9). As a result, the update data is sent from the communication device 203 to the network N.

[0077] In the mobile object 2, the DCM 21 receives the update data from the network N. The ECU 22 of the mobile object 2 receives the update data from the DCM 21. In this manner, the update data is downloaded.

[0078] In step S107, when the ECU 22 determines that the download is complete (YES in step S107), the ECU 22 waits for the program update start time to arrive (step S108). When it is determined that the update start time has arrived (YES in step S108), the ECU 22 updates the program using the update data (step S109). Then, when it is determined that the program update is completed (YES in step S110), the ECU 22 ends the processing in FIG. 6 and FIG. 7.

[0079] <Effects of the embodiment> In the embodiment, the control center 4 (information processing device) includes a processor 201 (control unit). The processor 201 acquires a release NOTE as information related to an update of a program (used by an ECU mounted on the moving object 2) implemented in a moving object 2 (vehicle) operated according to an operation plan. The processor 201 makes a plan to update the program while the moving object 2 is stopped according to the operation plan based on the release NOTE (step S007 in FIG. 6).

[0080] With the above configuration, the moving object 2 updates the program according to the program update schedule, so that the program is updated while the moving object 2 is stopped (while the vehicle is stopped). Since the program includes a program related to the movement of the moving object 2 (the running of the vehicle), However, by driving while the vehicle is stopped, the processor can be updated in a safe environment. In other words, the program can be updated at the appropriate time.

[0081] In the embodiment, the processor 201 calculates (obtains) a first time length (update time) required to update the program based on information indicating the size of program update data included in the update-related information (release NOTE) (step S006 in FIG. 6). Then, the processor 201 creates a plan to update the program during the time when the moving object 2 is stopped (time during maintenance, for example, 0:00 to 7:59) that continues for more than the first time length in the operation plan (step S007). This makes it possible to update the program during the stopped time.

[0082] In the embodiment, the processor 201 further acquires a second time length (communication time) required to download the update data based on the information indicating the size of the update data (step S006). The processor 201 then creates a plan to update the program during a period during which the mobile object 2 is stopped (a maintenance period) that continues for a period equal to or longer than the sum of the first time length and the second time length in the operation plan (step S007). This allows the update data to be downloaded in a safe environment during which the mobile object 2 is stopped.

[0083] Furthermore, in the embodiment, in step S007 of Fig. 6, the processor 201 can create a plan to download update data during a first stopping time of the moving object 2 in the operation plan (for example, a time period from 0:00 to 7:59 in Fig. 4). The processor 201 also creates a plan to update the program using the downloaded update data during a second stopping time different from the first stopping time (for example, a time period from 11:00 to 12:59 in Fig. 4). In this way, downloading and updating can be performed in different time periods.

[0084] In addition, in an embodiment, the processor 201 can plan to update the program when the mobile body 2 is in a maintenance state (while the vehicle is parked) after the start date and time of distribution of the program update data included in the release NOTE (steps S006 and S007).

[0085] In the embodiment, when the release NOTE includes information indicating an update of a program with high importance, the processor 201 can suspend the operation of the moving object 2 in the operation plan (FIG. 7, step S011). Then, the processor 201 can create a program update plan for the moving object 2 that is stopped due to the suspension of the operation (step S012).

[0086] The processor 201 can also stop the operation of the mobile object 2 after the start date and time of distribution of the program update data (step S011).The processor 201 can then create an update plan for downloading the update data to the mobile object 2 that has been stopped due to the stop of operation and updating the program using the update data (step S012).

[0087] In addition, in the embodiment, the processor 201 can create a plan to operate an alternative vehicle (alternative moving body) whose program has been updated in place of the vehicle (moving body 2) (steps S013 and S014).

[0088] In the embodiment, the processor 201 downloads the program update data while the mobile body is stopped (while the vehicle is stopped) according to the program update schedule. Then, the processor 201 can transmit, to the mobile object 2, an instruction to update the program using the update data (steps S008 and S016).

[0089] In the embodiment, the control center 4 is an information processing device. However, the DCM 21 of the moving object 2 may receive the release NOTE and operate as an information processing device that performs the processes of steps S001 to S007, S009 to S014, and S016 shown in Figs. 6 and 7.

[0090] <Other> The above embodiment is merely an example, and the present disclosure may be modified as appropriate without departing from the spirit of the present disclosure. In addition, a process described as being performed by one device may be shared and executed by multiple devices. Alternatively, a process described as being performed by different devices may be executed by one device. In a computer system, the hardware configuration (server configuration) by which each function is realized can be flexibly changed.

[0091] The present disclosure can also be realized by supplying a computer program implementing the functions described in the above embodiments to a computer, and having one or more processors of the computer read and execute the program. Such a computer program may be provided to the computer by a non-transitory computer-readable storage medium connectable to the system bus of the computer, or may be provided to the computer via a network. The non-transitory computer-readable storage medium is, for example, any type of disk, such as a magnetic disk (e.g., a floppy disk, a hard disk drive (HDD), etc.), an optical disk (e.g., a CD-ROM, a DVD disk, a Blu-ray disk, etc.). The non-transitory computer-readable medium also includes a read-only memory (ROM), a random access memory (RAM), an EPROM, an EEPROM, a magnetic card, a flash memory, an optical card, and any type of medium suitable for storing electronic instructions. [Explanation of symbols]

[0092] 2. Mobile 3 Vehicle Center 4. Control Center 21 DCM 22 Central ECU 23 UIF device 24 Preventive safety devices 25 ADS 26 Sound / video / NAVI equipment 100 Information Processing Systems 200 Terminal Equipment 201 Processor 202 Storage device 203 Communication Equipment 204 Input Device 205 Output Device

Claims

1. Obtaining information regarding updates to programs implemented in the vehicle; obtaining a first time length required for updating the program based on information indicating a size of data for updating the program, which is included in the information regarding the update; and creating a plan to update the program during a period during which the vehicle is stopped that continues for at least the first time length in an operation plan based on information regarding the update; A control unit that executes Information processing device.

2. The control unit is and acquiring a second time length required for downloading the update data based on information indicating a size of the update data; In the operation plan, a plan is made to update the program during a period during which the vehicle is stopped that is continuous for a period equal to or longer than the sum of the first time length and the second time length. The information processing device according to claim 1 .

3. Obtaining information regarding updates to programs implemented in the vehicle; and creating a plan to download data for updating the program during a first stop time of the vehicle in an operation plan based on information regarding the update, and creating a plan to update the program using the data for updating the program during a second stop time of the vehicle that is different from the first stop time of the vehicle; A control unit that executes Information processing device.

4. Obtaining information regarding updates to a program implemented in a vehicle; Developing a plan to update the program while the vehicle is stopped in the operation plan based on the information about the update; A control unit that executes The control unit is When the information regarding the update includes information indicating an update of the program having a high importance, the operation of the vehicle in the operation plan is stopped; Developing an update plan for the program for the vehicle that has been stopped due to the suspension of operation; Information processing device.

5. The control unit stops operation of the vehicle after a distribution start date and time of the data for updating the program, Developing the update plan for downloading data for updating the program to the vehicle that has been stopped due to the suspension of operation and updating the program using the update data; The information processing device according to claim 4.

6. The control unit develops a plan to operate a substitute vehicle having the updated program in place of the vehicle.

6. The information processing device according to claim 4 or 5.

7. 5 . The information processing device according to claim 1 , wherein the control unit creates a plan to update the program during a period during which the vehicle is stopped after a distribution start date and time of data for updating the program included in the information regarding the update.

8. The program is a program related to driving control of the vehicle. The information processing device according to claim 1 .

9. The control unit downloads data for updating the program while the vehicle is stopped in accordance with a plan for updating the program, and transmits an instruction to the vehicle to update the program using the data for updating. The information processing device according to claim 1 .

10. An information processing device, Obtaining information regarding updates to programs implemented in the vehicle; obtaining a first time length required for updating the program based on information indicating a size of data for updating the program, the information relating to the update being included in the information relating to the update; and creating a plan to update the program during a period during which the vehicle is stopped that continues for at least the first time length in an operation plan based on information regarding the update; Execute Information processing methods.

11. The information processing device includes: and acquiring a second time length required for downloading the update data based on information indicating a size of the update data; In the operation plan, a plan is made to update the program during a period during which the vehicle is stopped that continues for a period equal to or longer than the sum of the first time length and the second time length. The information processing method according to claim 10.

12. An information processing device, Obtaining information regarding updates to programs implemented in the vehicle; and creating a plan to download data for updating the program during a first stop time of the vehicle in an operation plan based on information regarding the update, and creating a plan to update the program using the data for updating the program during a second stop time of the vehicle that is different from the first stop time of the vehicle; Execute Information processing methods.

13. An information processing device, Obtaining information regarding updates to a program implemented in a vehicle; Developing a plan to update the program while the vehicle is stopped in the operation plan based on the information about the update; An information processing method for performing The information processing device includes: When the information regarding the update includes information indicating an update of the program having a high importance, the operation of the vehicle in the operation plan is stopped; Developing an update plan for the program for the vehicle that has been stopped due to the suspension of operation; Information processing methods.

14. The information processing device includes: Stopping the operation of the vehicle after the start date and time of distribution of the data for updating the program; A plan is made to download data for updating the program to the vehicle that has been stopped due to the suspension of operation and to update the program using the data for updating. The information processing method according to claim 13.

15. The information processing device creates a plan to operate a substitute vehicle having the updated program in place of the vehicle.

15. The information processing method according to claim 13 or 14.

16. the information processing device creates a plan to update the program during a period during which the vehicle is stopped after a distribution start date and time of data for updating the program included in the information regarding the update; The information processing method according to any one of claims 10 to 13.

17. The program is a program related to driving control of the vehicle.

17. The information processing method according to any one of claims 11 to 16.

18. An information processing device; A vehicle capable of communicating with the information processing device, The information processing device includes: Obtaining information regarding updates to a program installed in the vehicle; obtaining a first time length required for updating the program based on information indicating a size of data for updating the program, which is included in the information regarding the update; Developing a plan to update the program during a period during which the vehicle is stopped that continues for at least the first time length in an operation plan based on information regarding the update; and transmitting instructions to the vehicle to update the program according to a schedule for updating the program; A control unit that executes The vehicle updates the program in accordance with the instructions. Information processing system.

19. An information processing device; A vehicle capable of communicating with the information processing device, The information processing device includes: Obtaining information regarding updates to a program installed in the vehicle; Developing a plan to download data for updating the program during a first stop time of the vehicle in an operation plan based on information regarding the update, and developing a plan to update the program using the data for updating the program during a second stop time of the vehicle different from the first stop time of the vehicle; and transmitting instructions to the vehicle to update the program according to a schedule for updating the program; A control unit that executes The vehicle updates the program in accordance with the instructions. Information processing system.

20. An information processing device; A vehicle capable of communicating with the information processing device, The information processing device includes: Obtaining information regarding updates to a program installed in the vehicle; Developing a plan to update the program during a stop of the vehicle in a travel plan based on the information about the update; and transmitting instructions to the vehicle to update the program according to a schedule for updating the program; A control unit that executes The control unit is When the information regarding the update includes information indicating an update of the program having a high importance, the operation of the vehicle in the operation plan is stopped; Develop an update plan for the program for the vehicle that has been stopped due to the suspension of operation; The vehicle updates the program in accordance with the instructions. Information processing system.

Citation Information

Patent Citations

  • controller

    JP2012014253A

  • Program distribution system, server, program distribution method, and computer program

    JP2018005894A

  • Software update system, and server

    JP2018132979A

  • On-vehicle device, program update method, and program update system

    JP2019191943A

  • Self-driving vehicle and program for self-driving vehicle

    JP2020038585A