Information processing device, information processing method, and information system

Abstract

To select an appropriate charging method according to the state of a device that operates on a battery.SOLUTION: A control unit of an information processing device executes: acquisition of a first amount of charge required for a battery that operates a predetermined device; and selection of a charging method that allows charge for at least the first amount of charge within a first time range from among a plurality of charging methods.SELECTED DRAWING: Figure 1

Description

[Technical field]

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

[0002] Nowadays, various devices that run on batteries are in use, such as moving objects such as electric vehicles, portable information devices, etc. For example, the following Patent Document 1 proposes charging batteries based on the driving plans of each of a plurality of vehicles and external factors that affect the battery usage of the vehicles. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2011-120327 A Summary of the Invention [Problem to be solved by the invention]

[0004] An object of the embodiments of the present disclosure is to make it possible to select an appropriate charging method according to the status of a device operated by a battery. [Means for solving the problem]

[0005] The disclosed embodiment is exemplified by an information processing device including a controller that executes the following: obtaining a first charge amount required for a battery that operates a specific device; and selecting, from among a plurality of charging methods, a charging method that can charge at least the first charge amount within a first time range. Another aspect of the present embodiment is exemplified by an information processing method executed by the computer, which executes the steps of: acquiring a first charge amount required for a battery that operates a specific device; and selecting, from among a plurality of charging methods, a charging method that can charge at least the first charge amount within a first time range. Another aspect of the present embodiment is also exemplified by an information system, which includes an information processing device including a control unit that executes the following: acquiring a first charge amount required for a battery that operates a specific device, and selecting a charging method that can charge at least the first charge amount within a first time range from among a plurality of charging methods, and the specific device. Effect of the Invention

[0006] According to the present information processing device, it is possible to select an appropriate charging method according to the status of the device that is operated by the battery. [Brief description of the drawings]

[0007] [Figure 1] FIG. 1 is a diagram illustrating an information system according to the first embodiment. [Diagram 2] FIG. 2 is an example of a release NOTE sent from the vehicle center to the control center. [Diagram 3] FIG. 3 shows an example of operation schedule data that the control center distributes to each mobile object. [Figure 4] FIG. 4 is a diagram illustrating an example of status information of each moving object held by the control center. [Diagram 5] FIG. 5 is a diagram illustrating an example of charging equipment and battery charge / discharge characteristics provided in an information system. [Figure 6] FIG. 6 is a diagram illustrating a process of setting an operation schedule for a moving object by a computer in a control center. [Figure 7] FIG. 7 is a flowchart illustrating the details of the process of creating the next operation schedule after the computer program is updated. [Figure 8] FIG. 8 is a flowchart illustrating the details of the process of creating the next operation schedule without updating the computer program. [Figure 9] FIG. 9 is a flowchart illustrating details of a planning process for a next operation schedule with an update in the second embodiment. [Figure 10]FIG. 10 is a diagram illustrating the details of the adjustment process of the next scheduled operation time. [Figure 11] FIG. 11 is a diagram illustrating a detailed modification of the next scheduled operation time adjustment process. [Figure 12] FIG. 12 is a diagram illustrating an example of the configuration of an information system according to the third embodiment. [Figure 13] FIG. 13 is a diagram illustrating a process of planning an update of a computer program executed on a portable electronic device by a computer. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] Hereinafter, an information processing device, an information processing method, and an information system according to the present embodiment will be described with reference to the drawings. The information processing device includes a control unit that executes acquiring a first charge amount required for a battery that operates a specific device, and selecting a charging method that can charge at least the first charge amount within a first time range from among a plurality of charging methods.

[0009] Here, the specified device is not limited as long as it is a device or equipment that runs on a battery. The battery is a rechargeable secondary battery or a storage battery. The battery is also called a battery. The first charge amount required for the battery is the charge amount required for the specified device to provide a function to a user after a first time has elapsed. For example, it is desirable that the first charge amount within the first time period charges the battery to an amount of power required to provide a function without affecting the usage plan of the specified device or the user's action schedule.

[0010] <First embodiment> (System configuration) 1 is a diagram illustrating an information system 100 of the first embodiment. The information 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 will also be 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.

[0011] 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.

[0012] 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.

[0013] As shown in FIG. 1, the mobile object 2 includes a Data Communication Module (DCM) 21, a Central Electrical Control Unit (Central ECU) 22, a User Interface (UIF) device 23, a preventive safety device 24, an Advanced Drive System (ADS) 25, and an audio / video / NA. and a VI device 26.

[0014] The DCM 21 accesses the network N and communicates with other mobile units, the vehicle center 3, or the management The DCM 21 communicates with the control center 4, etc. The DCM 21 is capable of wireless communication via a mobile communication network.

[0015] 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 in the memory and executes processing as the Central ECU 22. The Central ECU 22 updates, for example, a computer program executed by an ECU mounted in each device in the mobile object 2 and manages the progress of the update. In addition, the Central ECU 22 updates the computer program. It detects errors when the engine is replaced and executes the necessary processing when an error occurs. The combination of DCM 21 is an example of an on-board computer in a vehicle.

[0016] The UIF device 23 provides a user interface when, for example, updating a computer 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 UIF device 23 also has an ECU similar to the Central ECU 22. The Central ECU 22 and the ECUs in the UIF device 23 can be called a common ECU group.

[0017] The preventive safety device 24 has an ECU built in and executes collision avoidance support processing by processing a computer program. 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.

[0018] ADS25 is connected to Spatial Information Service (SIS) 27 and Advanced Drive Extension (ADX) 28. ADS25, SIS27 and ADX2 The ADS25 is equipped with an ECU and performs advanced driving assistance processing by processing computer programs. Based on detection signals from the vehicle position sensor (AR), the vehicle or three-dimensional object around the moving body 2 is detected, the position of the moving body 2 itself is estimated, and motion control is performed.

[0019] 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 provides position information from a global navigation satellite system (GNSS) or a global positioning system (GPS), six-axis acceleration information from a gyro sensor, The SIS 27 acquires route information or map information from a traffic light or a navigation system. Based on the acquired information, the SIS 27 calculates the attitude of the moving object 2 itself and its position on the map. The ADX 28 applies an Artificial Intelligence (AI) system to calculate the information from the various sensors mentioned above. The information is recognized, processed, and the processing result is notified to the ADS25.

[0020] 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 the processing of a computer program.

[0021] 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.

[0022] The ECUs of the above-mentioned preventive safety device 24, ADS 25, and audio / video / NAVI device 26, and the ECUs of the devices connected thereto, can be called an individual ECU group. The Central ECU 22 monitors the progress of updates to the computer programs mounted in the individual ECU group and the timing of the updates. Manage errors.

[0023] 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 computer programs executed by each of these ECUs. The vehicle center 3 distributes update data for updating computer programs to the mobile bodies 2. The update data can also be simply called an update program.

[0024] The control center 4 manages the operation and maintenance of each mobile object 2. The control center 4 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 of 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, and the like 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.

[0025] As described above, the moving object 2 is equipped with various parts each having an ECU built in. The computer 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 this reason, the computer programs for the ECUs installed in the moving object 2 are updated during the maintenance period when the moving object 2 is stopped traveling.

[0026] The vehicle center 3 notifies the control center 4 of the latest update contents and update schedule for the computer 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 computer 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 update of the computer program 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 update of the computer program of each ECU.

[0027] 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 computer 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).

[0028] The DCM 21 accesses the vehicle center 3 according to the received operation schedule, acquires update data for updating the computer programs, and transfers the data to the Central ECU 22. The Central ECU 22 updates the computer 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.

[0029] 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 updating the computer program in 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 computer program of the UIF device 23.

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

[0031] The ADS 25 and the audio / video / navi device 26 are connected to the Central ECU 22 via a network within the vehicle, such as Ethernet (registered trademark). The ADS 25 and the audio / video / navi device 26 each receive data for updating a computer program from the Central ECU 22. The ADS 25 and the audio / video / navi device 26 then each executes updates of the computer programs of themselves and their subordinate ECUs. The ADS 25 and the audio / video / navi device 26 report statuses associated with the updates to the Central ECU 22.

[0032] (Example data) Fig. 2 is an example of a release NOTE sent from the vehicle center 3 to the control center 4. In the example of Fig. 2, the release NOTE specifies values ​​for keywords in the format of "keyword:value". Also, in the example of Fig. 2, the "keyword:value" pairs are enclosed in curly brackets "{}" and described hierarchically.

[0033] That is, from FIG. 2, it can be seen that the vehicle type of the moving object 2 is E-palette G0, the system version to be released is V07-01, and the release date is ddmmmyyyy, which is a release NOTE of a computer program. The system version is the version given to the entire group of computer programs installed in the mobile unit 2. This release note also describes the type of program, version, data size (volume) of update data, etc. for each ECU type. For example, it can be seen that the version of PC1, which is a program for the Central ECU, is V07-01-1, and the data size is V1 MB.

[0034] The release note is not limited to the format shown in FIG. 2. For example, the release note may be written in a prescribed format such as HyperText Markup Language (HTML) or Extensible Markup Language (XML). It may also be written in a tabular format in which records containing multiple elements are arranged.

[0035] FIG. 3 is an example of operation schedule data (distributed by "planned distribution" in FIG. 1) that the control center 4 distributes to each mobile unit. An operation schedule is created for each mobile unit 2. For this reason, the operation schedule in FIG. 3 includes a mobile unit ID for identifying the mobile unit 2. Also, in the example of FIG. 3, the operation schedule is created for each day, so includes the year, month, and date. Furthermore, in the example of FIG. 3, the operation schedule specifies the operation of the mobile unit 2 for each time period, as well as plans for maintenance, etc.

[0036] 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 computer program updates. Mobile ID: E-PALETTE EV1 is operated from 9:00 to 11:00. Vehicle ID: E-PALETTE EV1 operates from 11:00 to 13:00. During this period, the vehicle stops operation, goes into maintenance mode, and the battery is charged. Vehicle ID: E-PALETTE EV1 operates from 13:00 to 23:00, and stops operation after 23:00 and goes into maintenance mode. In the example in Figure 3, details of scheduled maintenance and operation between 13:00 and 22:00 are omitted.

[0037] Note that Fig. 3 is an example of an operation schedule, and the operation schedule created by the control center 4 is not limited to Fig. 3. For example, in Fig. 3, the time periods are defined in units of one hour. However, the time periods may be defined in units of one minute. Furthermore, the operation schedule does not have to be created for each day, and may be created for each week, for example. Furthermore, the operation schedule may be created for each month. Furthermore, the operation schedule may be created for weekdays (Monday to Friday), Saturdays, and holidays.

[0038] Fig. 4 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 update status of the computer programs of the mobile object 2, the battery status, etc. The status information is stored in a predetermined database of the control center 4. In the example of Fig. 4, the status information includes a mobile object ID, the last update date, the system version of the entire group of computer programs installed in the mobile object 2, the date and time of the completion of the previous operation, and the battery status.

[0039] Here, as in FIG. 3, the moving object ID is identification information that uniquely identifies the moving object 2. The last update date is the date when the moving object 2 (in FIG. 4, the moving object ID is E-PALETTE EV1) last updated the This is the update date when the computer programs of the ECUs of each part were updated. The system version of the computer programs is the version of the entire computer programs in the mobile object 2 after updating, as explained in FIG.

[0040] 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. 2) 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 date and time of the last update and the system version of the entire computer program group after the update in the state information.

[0041] The last trip completion date and time was for mobile unit 2 (in Figure 4, 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.

[0042] FIG. 5 is a diagram illustrating an example of the charging and discharging characteristics of a battery held by the control center 4. However, the charging characteristics of a battery also depend on the charging equipment provided in the information system 100. In this embodiment, the battery mounted on the moving object 2 has the charging and discharging characteristics shown in FIG. 5. The charging and discharging characteristics can be accumulated experimentally or empirically. In FIG. 5, the charging and discharging characteristics of the battery include the charging speeds of normal charging and quick charging, the download power consumption rate, the update power consumption rate, and the operating power consumption rate.

[0043] The charging equipment installed in the information system 100 includes equipment capable of normal charging and equipment capable of rapid charging. Rapid charging refers to a charging method in which the charging speed is faster than normal charging. In FIG. 5, the charging speed is the amount of charging per hour, and the amount of charging is indicated by SOC. First, in the case of normal charging, the battery mounted on the moving object 2 can be charged at a rate of 5% / hour. Here, 5% / hour is, for example, 3 to 6 kWh per hour. This means that if the battery is charged at a charging rate of 5% / hour from an empty state, it will take 20 hours to fully charge.

[0044] Furthermore, when rapid charging is performed, the battery illustrated in FIG. 5 can be charged at a rate of 50% / hour. Here, the power charged at a rate of 50% / hour is, for example, 50 kWh or more per hour. That is, in the battery illustrated in FIG. 5, rapid charging can bring the battery from an empty state to a fully charged state in two hours.

[0045] The download power consumption rate is the power consumption per a predetermined unit of data amount when the DCM 21 of the mobile unit 2 downloads update data for a computer program, expressed as SOC. The download power consumption rate of the battery illustrated in Fig. 5 is 10% / 10MB. That is, the SOC of the battery decreases by 10% every time 10MB of data is downloaded.

[0046] The update power consumption rate is the power consumption per predetermined unit of data amount of update data, expressed in terms of SOC, when the DCM 21 and the ECUs below the Central ECU 22 of the moving object 2 update a computer program. The update power consumption rate of the battery illustrated in Fig. 5 is 10% / 10MB. That is, the SOC of the battery decreases by 10% every time an update is performed with 10MB of update data.

[0047] The operation power consumption rate is the amount of power consumed per hour when the mobile object 2 is in operation, expressed as SOC. The operation power consumption rate of the battery illustrated in FIG. 5 is 50% / hour. That is, the SOC of the battery decreases by 50% in one hour of driving. That is, in the example of FIG. 5, the mobile object 2 consumes the amount of power of a fully charged battery in two hours of driving. Note that the data in FIG. 5 is an example, and the battery of the mobile object 2 and the charging equipment that charges the battery are not limited to the example in FIG. 5. In the following process, the required charge amount and charging time of the battery are calculated using these charge and discharge characteristics.

[0048] 5 according to the type of vehicle or the type of battery. The information on the charge and discharge characteristics of the battery is not limited to being stored in the control center 4, and may be stored by the Central ECU 22 of each moving object 2 for the battery mounted on the moving object 2, for example. In this case, the control center 4 may obtain information on the charge and discharge characteristics of the battery mounted on the moving object 2 by inquiring of each moving object 2.

[0049] (Processing flow) FIG. 6 illustrates a process of setting an operation schedule of the mobile object 2 by the computer of the control center 4. As described above, the process of FIG. 6 will be described below by simply referring to the computer of the control center 4 as the control center 4. The same applies to the following FIG. 7 to FIG. 13, etc. The process of FIG. 6 is executed, for example, when the current operation of the mobile object 2 is completed. Note that FIG. 6 assumes that when a computer program update is implemented, downloading of update data for the update and updating of the computer program of each ECU of the mobile object 2 are executed while the battery of the mobile object 2 is being charged.

[0050] In the process of FIG. 6, the control center 4 receives a trip completion report from the mobile object 2. The trip completion report includes the charging state of the battery of the mobile object 2. Therefore, the control center 4 records the charging state of the battery of the mobile object 2 in the status information (see FIG. 4) of a predetermined database (S1). Note that the trip completion report from the mobile object 2 may be, for example, a report of the final trip of a daily operation plan. The operation completion report may be received when the operation is completed. Also, the operation completion report may be received from the moving object 2 every time the operation by the moving object 2 is completed. When the control center 4 receives the operation completion report every time the operation by the moving object 2 is completed, the control center 4 may modify the operation schedule exemplified in FIG. 3 every time the operation completion report is received.

[0051] Next, the control center 4 judges whether or not there is a plan to update the computer program in the mobile object 2. The control center 4 compares the latest release NOTE received from the vehicle center 3 with the status information of the mobile object 2 (FIG. 4). If the system version of the computer program of the mobile object 2 is older than the system version specified in the latest release NOTE, the control center 4 judges that there is a plan to update the computer program. If there is a plan to update the computer program, the control center 4 executes a process to create the next operation schedule including the update (S3). Details of S3 are illustrated in FIG. 7.

[0052] If there is no plan to update the computer program, the control center 4 executes a process of creating the next operation schedule without updating (S4). Details of S4 are illustrated in FIG.

[0053] Next, the control center 4 distributes the operation schedule to the mobile object 2 (S5). The mobile object 2 operates according to the distributed operation schedule. The control center 4 receives an update completion report from the mobile object 2 after the update is completed. The control center 4 then records the updated version and the update date and time in the status information for each mobile object 2. After that, the process shown in FIG. 6 ends.

[0054] 7 is a flowchart illustrating the details of the process (S3 in FIG. 6) of creating a next operation schedule with update of the computer program in the moving object 2 by the computer in the control center 4. In this process, the control center 4 creates an update plan that enables the computer program executed in each ECU of the moving object 2 to be updated by the time of the next operation.

[0055] First, in this process, the control center 4 acquires the data size of the update data (the value of volume in FIG. 2) from the release note (S31). The release note is an example of information related to the update of the first program, including the data amount of the update data used when the first program is updated. Here, the first program is exemplified as a group of programs to be rewritten in the current update. Therefore, it can be said that the control center 4 executes the process of S31 as an example of acquiring information related to the update of the first program.

[0056] In addition, the control center 4 acquires information on the next operation schedule (S32). The information on the next operation schedule includes the scheduled start time of the next operation, the destination of the next operation, the travel route, the scheduled travel time, etc. Here, the time from the current time to the scheduled start time of the next operation is an example of the first time.

[0057] If the mobile body 2 is operated periodically, information on the next scheduled operation of the mobile body 2 is obtained from a predetermined database that manages the periodic operation. On the other hand, if the mobile body 2 is operated non-periodically, the mobile body 2 is used for a sharing service or rental, etc. Therefore, information on the next scheduled operation of the mobile body 2 is obtained from reservation information for the sharing service or rental, etc. The information on the next scheduled operation is an example of schedule information of the mobile body 2 as a predetermined device. Therefore, it can be said that the control center 4 obtains the first time based on the schedule information of the mobile body 2 as a predetermined device.

[0058] Next, the control center 4 acquires the current state of charge (SOC) of the battery. The current state of charge (SOC) of the battery can also be said to be the remaining capacity of the battery. In addition, the control center 4 The control center 4 calculates the amount of power consumed in each process executed in the process. Then, the control center 4 calculates the required amount of power from the remaining battery level and the amount of power consumed in each process (S33). The amount of power consumed in each process includes the amount of power consumed for downloading, the amount of power consumed for updating, and the amount of power consumed for running in the process shown in FIG.

[0059] The download power consumption is the power consumption when the mobile object 2 downloads update data for a computer program from the vehicle center 3. The download power consumption is calculated from the download power consumption rate shown in FIG. 5 based on the data size of the update data. For example, if the data size of the update data is 20MB and the download power consumption rate is 10% / 10MB, then 20% of the power consumed when the battery is fully charged will be consumed. The download power consumption will be referred to as the third power consumption.

[0060] The update power consumption is the power consumption when each ECU of the mobile object 2 updates a computer program to be updated. The update power consumption is calculated from the update power consumption rate exemplified in FIG. 5 based on the data size of the update data. For example, if the data size of the update data is 20 MB and the update power consumption rate is 10% / 10 MB, 20% of the power consumed when the battery is fully charged is consumed. Here, the update power consumption is referred to as the second power consumption.

[0061] The traveling power consumption is the power consumption when the moving object 2 travels according to a schedule. For example, if the traveling time is 1 hour and the traveling power consumption rate is 50% / hour, 50% of the power consumed when the battery is fully charged is consumed. The traveling power consumption is referred to as the first power consumption.

[0062] Then, the control center 4 calculates the required charge amount from the current charge state (remaining charge) of the mobile object 2 and the amount of power consumed in each process. For example, if the download power consumption is 20%, the update power consumption is 20%, and the operation power consumption estimated from the operation schedule is 50%, the battery is required to be charged until it reaches at least 90% of the full charge. Therefore, for example, if the current battery charge state is 5% of the full charge, the required charge amount is calculated as 90%-5%=85%. In this embodiment, the required charge amount is called the first charge amount.

[0063] From the above, it can be said that the control center 4 executes the process of S33 as an example of acquiring the first charge amount required for the battery that operates the specified device. Therefore, it can be said that the control center 4 acquires the first charge amount based on the third power consumption amount at the time of downloading in addition to the first power consumption amount at the time of operation and the second power consumption amount at the time of update in the process of S33. Note that, if the mobile object 2 executes download of update data in advance, the download power consumption amount does not need to be included in S33. In this case, the control center 4 acquires the first charge amount from the current remaining battery amount, the first power consumption amount of the battery that is expected to be consumed during operation for a predetermined time, and at least the second power consumption amount of the battery that is expected to be consumed during the update of the first program. Note that the process of S33 can be said to be an example of acquiring the first charge amount from the current remaining battery amount and the first power consumption amount of the battery that is expected to be consumed during operation of the mobile object 2 for a predetermined time. This is because, in the calculation in S33, the first charge amount required for the battery can be obtained based on at least the first power consumption amount during operation.

[0064] Next, the control center 4 calculates the required time for normal charging and rapid charging from the required charge amount (S34). The required time for normal charging and rapid charging can be calculated by dividing the required charge amount by the normal charging speed and rapid charging speed, respectively, shown as examples in FIG. 5. Then, the control center 4 judges whether normal charging will be completed in time for the next operation time (S35). If it is judged in S35 that charging will be completed by normal charging by the time the next operation time, the control center 4 judges whether normal charging and rapid charging will be completed. A new implementation plan is prepared and incorporated into the operation schedule (S36). On the other hand, if it is determined in S35 that normal charging will not be able to complete charging by the time of the next operation, the control center 4 determines whether rapid charging will be able to complete charging in time for the next operation (S37). If it is determined in S37 that rapid charging will complete charging by the time of the next operation, the control center 4 prepares a plan for rapid charging and updating, and incorporates it into the operation schedule (S38).

[0065] On the other hand, if it is determined in S37 that charging will not be completed by the next operation time even with quick charging, the control center 4 executes a process of creating a next operation schedule without updating (S39). The process of creating a next operation schedule without updating is illustrated in FIG. 8. The time until the next operation time is an example of a first time range. Therefore, it can be said that the control center 4 executes the determinations of S35 and S37 as an example of selecting a charging method that can charge the first charge amount calculated in the process of S33 within the first time range from among a plurality of charging methods. In addition, it can be said that the control center 4 executes the processes of S36 and S38 as an example of creating a first plan that includes charging at least the first charge amount of the battery by the selected charging method and updating at least the first program (a group of programs to be rewritten in the current update).

[0066] FIG. 8 is a flowchart illustrating the details of the planning process of the next operation schedule without updating the computer program in the mobile object 2. That is, FIG. 8 shows the details of the planning process of the next operation schedule without updating (S4 in FIG. 6 and S39 in FIG. 6). The processes of S42 to S48 in FIG. 8 are the same as the processes of S32 to S38 in FIG. 7, except that the download power consumption amount and the update power consumption amount are not calculated. Therefore, the details of the processes of S42 to S48 are omitted. In the process of S43, the control center 4 calculates the operation power consumption amount for the operation of the mobile object 2. As described in FIG. 7, the operation power consumption amount for the operation of the mobile object 2 is an example of the first power consumption amount of the battery that is expected to be consumed by the operation of a predetermined device for a predetermined time. Therefore, it can be said that the computer of the control center 4 obtains the first charge amount from the remaining battery amount, which is the current charge state of the battery, and the first power consumption amount of the battery that is expected to be consumed by the operation of the mobile object 2 for a predetermined time.

[0067] Then, in the planning process of the next operation schedule without updating, if it is determined that charging will not be completed by the next operation time by either normal charging or rapid charging (NO in S47), the control center 4 requests the operator to adjust the next operation schedule (S49). For example, the control center 4 estimates the time when charging of the required amount of charge will be completed by rapid charging, and presents the estimated time to the operator. If the operator inputs approval, the control center 4 may change the time when charging of the required amount of charge will be completed to a new start time of the next operation.

[0068] (Effects of the embodiment) As described above, the information system 100 including the control center 4 of this embodiment acquires the minimum charge state required for operation of the mobile object 2. Then, the information system 100 can select from a plurality of charging methods a charging method that can charge the mobile object 2 from the current charge state to the minimum charge state required for operation by the start time of the next operation. Therefore, the information system 100 of this embodiment can appropriately set an operation schedule for the mobile object 2 that repeatedly operates and charges.

[0069] Furthermore, if the mobile object 2 is operated periodically, the information system 100 acquires the next operation start time from a predetermined database that manages periodic operations. Furthermore, if the mobile object 2 is operated non-periodically, the computer acquires information on the next operation schedule of the mobile object 2 from reservation information for a sharing service or rental, etc. Therefore, the information system 100 can acquire the next operation start time appropriately according to the service in which the mobile object 2 is used.

[0070] Furthermore, the information system 100 calculates the required charge amount from the current charge state of the mobile object 2 and the amount of power consumed by each process during operation of the mobile object. Therefore, the information system 100 can accurately calculate the amount of power required by the mobile object 2. In this case, the information system 100 can accurately calculate the amount of power required for operation of the mobile object 2, downloading update data for the computer programs of each ECU in the mobile object 2, and updating the computer programs.

[0071] The information system 100 can then calculate the charging time required to charge the required amount of electricity and set a plan to charge the battery of the mobile body 2 and update the computer programs of each ECU in the mobile body 2 by the time the mobile body 2 starts its next operation.

[0072] Furthermore, if charging to the required amount of power is not completed by the next scheduled operation time, the information system 100 estimates the time when charging to the required amount of power will be completed, and after obtaining approval from the operator, changes the start time of the next operation to the time when charging will be completed. Therefore, the information system 100 can create a plan so that the time until the start of operation is at least equal to or longer than the charging time.

[0073] Furthermore, the information system includes the amount of power required for downloading in the amount of power required, and can therefore calculate the amount of power required taking into account the downloading of data required for updating a computer program.

[0074] <Second embodiment> In the above-described first embodiment, when charging up to the required charge amount cannot be completed by quick charging, the control center 4 creates the next operation schedule without updating the computer program of the mobile object 2. In the present embodiment, an example is shown of a process in which the control center 4 creates a next operation schedule that allows updating of the computer program when charging cannot be completed by quick charging.

[0075] In the first embodiment, it is assumed that the download of update data for updating and the update of the computer programs of each ECU of the mobile object 2 are completed while the battery of the mobile object 2 is being charged. In this embodiment, when the download of update data for updating and the update of the computer programs of each ECU of the mobile object 2 cannot be completed while the battery of the mobile object 2 is being charged, a process for creating a next operation schedule that allows these to be completed is illustrated. Other than the above, the configuration and operation of the information system 100 of the second embodiment are the same as those of the first embodiment. Therefore, Figs. 1 to 6 of the first embodiment are also applied to the second embodiment as they are.

[0076] 9 is a flowchart illustrating the details of the planning process of the next operation schedule with update (S3 in FIG. 6) in the second embodiment. In FIG. 9, the processes of S31 to S38 are the same as those in FIG. 7, so the description thereof will be omitted.

[0077] In FIG. 9, if it is determined in S37 that charging will not be completed by the next scheduled operation time even with rapid charging, the control center 4 executes an adjustment process for the next scheduled operation time (S39A). After the process of drawing up a plan for normal charging and updating in S36 and incorporating the plan into the operation schedule, and the process of drawing up a plan for rapid charging and updating in S38 and incorporating the plan into the operation schedule, the control center 4 proceeds to the determination in S3A. The control center 4 then determines whether or not it is possible to update the computer program of each ECU of the mobile object 2 during charging (S3A). The determination of whether or not updating is possible may include a determination of whether downloading update data and updating the computer program after downloading is possible. Note that in this embodiment, the computer program is determined by a process that does not include downloading data for updating. Here, we call updating a data program “rewriting a computer program.”

[0078] In the process of S34 executed before the judgment of S3A, the control center 4 acquires the time required to rewrite the program based on the data size of the update data used when updating the program. In this embodiment, the time required for the update not including downloading is called the second time. In the process of S34, the control center 4 acquires the time required to download the update data for the program. In this embodiment, the time required for this downloading is called the third time.

[0079] If it is determined in S3A that the update cannot be completed during charging, the control center 4 executes an adjustment process (S39A) for the next scheduled operation time. The operation schedule created in the adjustment process in S39A will also be referred to as the first plan. Therefore, it can be said that the control center 4 creates the first plan so that the time until the start of use of the mobile object 2, which is an example of a predetermined device, is at least equal to or greater than the sum of the second time and the third time. On the other hand, if it is determined in S3A that the update can be completed during charging, the control center 4 ends the process.

[0080] FIG. 10 is a diagram illustrating the details of the next scheduled operation time adjustment process (S39A in FIG. 9). In this process, the control center 4 estimates the charging completion time from the time required for quick charging (S39A1). The control center 4 also estimates the download and update completion time from the time required for updating (second time) and the time required for downloading the update data (third time) (S39A2). As described above, the time required for updating (second time) and the time required for downloading the update data (third time) have already been calculated in the process of S34 in FIG. 9.

[0081] Then, the control center 4 presents to the operator on the display device that the next operation start time will be the later of the charging completion time and the download and update completion time (S39A3). Then, the control center 4 waits for the operator to input OK (S39A4). If OK is input in S39A4, the control center 4 sets the presented time as the next operation start time and creates an operation schedule for the moving object 2 (S39A4). As described above, the control center 4 executes the processes from S39A1 to S39A4 as an example of a process for creating a first plan so that the time until the start of use is at least equal to or greater than the sum of the second time and the third time. Thereafter, the control center 4 ends the process.

[0082] On the other hand, if no OK input is obtained in S39A4, the control center 4 proceeds to an operation schedule setting process by the operator (S39A6). That is, the control center 4 requests the operator to set an appropriate operation schedule for the moving object 2. After the operator sets the operation schedule, the control center 4 ends the process. Here, the time from the current time to the start time of the next operation is an example of the first time.

[0083] In Fig. 10, the control center 4 presents to the operator that the next operation start time will be the later of the charging completion time and the download and update completion time. That is, in Fig. 10, the next operation start time is determined taking into consideration the time when the update of the computer program is completed, including the download time of the update data. However, it is also possible to download the update data in advance before the computer program is rewritten. Therefore, the control center 4 may determine the next operation start time so that the update, including only the rewriting of the computer program, is completed, without considering the download time of the update data.

[0084] FIG. 11 is a diagram illustrating a detailed modification of the next scheduled operation time adjustment process (S39A in FIG. 9). As a prerequisite for executing the process in FIG. 11, the control center 4 determines the download time without taking into account the download time of the data for updating in the judgment in S3A in FIG. It is only necessary to determine whether or not the computer program can be rewritten after being downloaded. In this case, the control center 4 does not take into consideration the time required for downloading data for updating. Therefore, it can be said that the control center 4 acquires the time required for rewriting the first program as the second time in the determination of S3A in FIG. 9.

[0085] In Fig. 11, the process of S39A1 is the same as that in Fig. 10, and therefore the description thereof will be omitted. Next, the control center 4 estimates the completion time of the update (i.e., rewriting of the computer program) from the time required for rewriting the computer program of each ECU of the moving object 2 (second time) (S39B2). Then, the control center 4 presents to the operator that the later of the charging completion time and the update (rewriting) completion time will be set as the next operation start time (S39B3). The process of S39A4 and thereafter in Fig. 11 is the same as that in Fig. 10, and therefore the description thereof will be omitted. The processes from S39A1 to S39A6 are an example of creating a first plan so that the time until the start of use of the moving object 2, which is an example of a predetermined device, is at least equal to or longer than the second time.

[0086] (Effects of the second embodiment) According to this embodiment, the information system 100 can set an operation schedule so that charging of the battery of the mobile object 2 is completed by the start time of the next operation. Also, according to the process of Fig. 10, the information system 100 can set an operation schedule so that downloading of update data for updating and updating of the computer program of each ECU of the mobile object 2 are completed by the start time of the next operation. Also, according to the process of Fig. 11, the information system can set an operation schedule so that updating (rewriting) of the computer program of each ECU of the mobile object 2 is completed by the start time of the next operation.

[0087] <Third embodiment> The above first and second embodiments have exemplified the process of updating a computer program executed in each ECU of the mobile object 2 and creating an operation schedule including charging a battery of the mobile object 2. However, the processes of the above first and second embodiments are also applicable to devices other than the mobile object 2, for example, portable electronic devices exemplified by mobile phones and smartphones. Therefore, in this embodiment, a configuration and process for creating an operation plan including updating a computer program executed in the portable electronic device and charging a battery mounted on the portable electronic device are exemplified.

[0088] (Configuration example) FIG. 12 is a diagram illustrating an example of the configuration of an information system 101 of this embodiment. The information system 101 has a computer 10 and a portable electronic device 2A. The computer 10 is also called a server. It also includes a terminal capable of wirelessly communicating with the portable electronic device 2A. The computer 10 has a CPU 11, a main memory unit 12, and an external device connected through an interface (I / F), and executes information processing by a computer program. The CPU 11 is also called a processor. The CPU 11 is not limited to a single processor, and may have a multi-processor configuration. The CPU 11 may also include a graphics processing unit (GPU), a digital signal processor (DSP), etc. The CPU 11 may also cooperate with a hardware circuit such as a field programmable gate array (FPGA). Examples of the external device include an external storage unit 13, a display unit 14, an operation unit 15, and a communication unit 16.

[0089] The CPU 11 executes a computer program that has been loaded in an executable manner into the main memory unit 12, and provides the functions of the computer 10. The main memory unit 12 stores the computer program executed by the CPU 11, data processed by the CPU 11, and the like. The main memory unit 12 includes a dynamic random access memory (DRAM), a static random access memory (SRAM), a read Further, the external storage unit 13 may be, for example, a read only memory (ROM), etc. The external storage unit 13 is used as an auxiliary storage area and stores computer programs executed by the CPU 11, data processed by the CPU 11, etc. The external storage unit 13 is a hard disk drive, a solid state disk (SSD), etc. Furthermore, the computer 10 may be provided with a drive device for a removable storage medium. The removable storage medium is, for example, a Blu-ray disc, a Digital Versatile Disk (DVD), a Compact Disc (CD), a flash memory card, etc.

[0090] The computer 10 also has a display unit 14, an operation unit 15, and a communication unit 16. The display unit 14 is, for example, a liquid crystal display, an electroluminescence panel, etc. The operation unit 15 is, for example, a keyboard, a pointing device, etc. In this embodiment, a mouse is exemplified as the pointing device. The communication unit 16 transmits and receives data to and from other devices on the network. For example, the communication unit 16 communicates with the portable electronic device 2A via the network N2. The network N2 is, for example, a mobile phone network such as LTE, 5G, or 6G, a wireless local area network (LAN), etc. The communication unit 16 may have a communication interface that can also access the network N of the first embodiment (FIG. 1).

[0091] The configuration of the portable electronic device 2A is similar to that of the computer 10. However, the portable electronic device 2A has a touch panel with a touch sensor superimposed on a display as an operation unit. The hardware configurations of the computer of the vehicle center 3 and the computer of the control center 4 described in the first and second embodiments are also similar to that of the computer 10. Also, the ECU described in the first and second embodiments is similar to a combination of the CPU 11 and the main storage unit 12 in FIG. 12. Therefore, the CPU 11 and the main storage unit 12 are exemplified as an example of a control unit throughout the first to third embodiments.

[0092] The computer 10 executes the same processes as the vehicle center 3 and the control center 4 in the first and second embodiments. That is, the computer 10 supports charging the battery of the portable electronic device 2A, updating the computer program executed by the CPU 11, and the use of the portable electronic device 2A by the user. For example, the computer 10 accesses a schedule management database provided to the user through the portable electronic device 2A and acquires the user's planned activities.

[0093] The schedule management database may be stored in the main memory unit 12 and the external memory unit 13 of the computer 10. The portable electronic device 2A may access the computer 10 via the network N2 and provide the schedule management database function to the user. However, the schedule management database may be stored in the portable electronic device 2A. In the case where the schedule management database is stored in the portable electronic device 2A, the computer 10 may collect information on the schedule management database from the portable electronic device 2A with the user's approval.

[0094] In addition, the schedule management database may be set in advance as time periods (candidate time periods for updating) during which the user will not operate the portable electronic device 2A. The user may set the candidate time periods for updating. The portable electronic device 2A or the computer 10 may perform statistical processing of the user's past operation history and select days of the week, time periods, etc. during which the portable electronic device 2A is likely not to be operated. The portable electronic device 2A or the computer 10 may present the selected days of the week, time periods, etc. to the user on the display of the portable electronic device 2A and request confirmation in advance.

[0095] The computer 10 then creates an operation schedule including battery charging, downloading update data for updating, and updating the computer program executed by the CPU 11 during the time period when the user does not use the portable electronic device 2A. The operation schedule of the child device 2A is distributed to the portable electronic device 2A. The portable electronic device 2A charges the battery, downloads update data for updating, and updates the computer program executed by the CPU 11 in accordance with the distributed operation schedule.

[0096] (Processing example) Fig. 13 is a diagram illustrating a planning process of a computer program update executed by the portable electronic device 2A by the computer 10. The process of Fig. 13 is executed, for example, when the portable electronic device 2A becomes capable of performing a computer program update. The computer 10 may determine that a computer program update is capable of being performed in the portable electronic device 2A from a user's schedule management database. However, the computer 10 may also determine that a computer program update is capable of being performed by an operation input to the portable electronic device 2A by the user.

[0097] First, in this process, the computer 10 obtains the data size of the update data from the release NOTE of the program executed by the portable electronic device 2A (S131). If the computer 10 is operated by an organization that sells the portable electronic device 2A or an organization that provides services such as communication by the portable electronic device 2A, the computer 10 holds the release NOTE. The computer 10 may also obtain the release NOTE from an organization that sells the portable electronic device 2A, etc., via the network N of the first embodiment, the network N2 of the third embodiment, etc.

[0098] Next, the computer 10 calculates the power consumption of each process executed in the portable electronic device 2A (S132). The power consumption of each process includes the download power consumption, the update power consumption, and the operating power consumption. The download power consumption and the update power consumption are the same as those in the first and second embodiments.

[0099] The operating power consumption is the power consumption when the portable electronic device 2A operates in an on state and executes information processing. The operating power consumption may be calculated statistically from the past operation history of the portable electronic device 2A. Then, the computer 10 calculates the required charging amount from the current charging state of the portable electronic device 2A and the amount of power consumed in each process.

[0100] Next, the computer 10 calculates the time required for normal charging and quick charging from the required charging amount (S133). The computer 10 also acquires information on the next use schedule of the portable electronic device 2A from the user's schedule management database (S134). The information on the use schedule includes the scheduled start time of use, the duration of use, and the type of processing to be executed. The time until the scheduled start time of use is the time until the next use starts, and is an example of a first time. Therefore, the computer 10 executes the processing of S133 as an example of processing acquired based on the schedule information of the user of the portable electronic device 2A, which is an example of a predetermined device. However, the computer 10 may acquire the information on the use schedule by the user's operation input to the portable electronic device 2A.

[0101] Then, the computer 10 determines whether normal charging or rapid charging is preferable based on the scheduled start time of use and the required time for normal charging and rapid charging (S135). For example, if the required amount of charging can be achieved by normal charging by the scheduled start time of use, the computer 10 selects normal charging. On the other hand, if the required amount of charging cannot be achieved by normal charging by the scheduled start time of use, the computer 10 selects rapid charging.

[0102] When the user selects the quick charging, the computer 10 creates a charging plan for quick charging and updating, and displays the plan and guidance information on the display of the portable electronic device 2A (S136). When normal charging is selected, the computer 10 creates a charging plan for normal charging and updating, and displays the plan and guidance information on the display of the portable electronic device 2A (S137). When either S136 or S137 is displayed on the display of the portable electronic device 2A, the user can charge the portable electronic device 2A and update the computer program according to the display.

[0103] As described above, according to the information system 101 of this embodiment, the computer 10 supports updating of a computer program in the portable electronic device 2A and charging the required amount of charge of the portable electronic device 2A. That is, the computer 10 can perform normal charging so that the required amount of charge is completed by the scheduled start time of use. Also, when the required amount of charge of the portable electronic device 2A cannot be completed by the scheduled start time of use, the computer 10 can prompt the user to perform rapid charging, and promote charging of the required amount of charge during the update of the computer program.

[0104] <Other Modifications> In the above first and second embodiments, the computer of the control center 4 executes the process of setting the operation schedule of the moving object 2 (FIGS. 6 to 11). However, the central ECU 22, which is an on-board device of the moving object 2, may execute these processes. In that case, the vehicle center 3 may transmit a release NOTE to the central ECU 22 via the DCM 21 of the moving object 2.

[0105] In the third embodiment, the computer 10 executes the planning process exemplified in Fig. 13. However, the portable electronic device 2A may execute the planning process exemplified in Fig. 13 and present it to the user. In this case, the portable electronic device 2A may receive the release note and the update data for the computer program from a computer of the organization that manages the release note, such as the computer 10.

[0106] <Other embodiments> The above embodiment is merely an example, and the present disclosure may be modified as appropriate without departing from the spirit and scope of the present disclosure. Furthermore, the processes and means described in the present disclosure may be freely combined and implemented as long as no technical contradiction occurs.

[0107] Furthermore, 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.

[0108] 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 includes any type of medium suitable for storing electronic instructions, such as, for example, 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.), a read-only memory (ROM), a random access memory (RAM), an EPROM, an EEPROM, a magnetic card, a flash memory, or an optical card. [Explanation of symbols]

[0109] 2. Mobile 2A portable electronic equipment 3 Vehicle Center 4. Control Center 10. Computers 11 CPU 12 Main memory 13 External memory unit 14 Display section 15 Control section 16 Communications Department 21 DCM 22 Central ECU 23 UIF device 24 Preventive safety devices 25 ADS 26 Sound / video / NAVI equipment 100, 101 Information Systems

Claims

1. Acquiring information regarding an update of a first program installed in a specified device, the information including a data amount of update data used when the first program is updated; obtaining a first charge amount required for a battery that operates the predetermined device based on information regarding an update of the first program; selecting a charging method capable of charging at least the first charge amount within a first time range from among a plurality of charging methods; creating a first plan including a charging plan for at least the first charge amount of the battery by the selected charging method and an update plan for at least the first program; A control unit that executes An information processing device comprising:

2. The control unit acquires the first time based on schedule information of the specified device or schedule information of a user of the specified device. The information processing device according to claim 1 .

3. the control unit obtains the first charge amount from a current remaining amount of the battery and a first power consumption amount of the battery that is expected to be consumed during operation of the predetermined device for a predetermined period of time; 3. The information processing device according to claim 1 or 2.

4. When an update to the first program exists, the control unit selects whether to perform normal charging or rapid charging based on a prediction of the amount of power consumed by the specified device in the future, and generates the first plan for updating the first program during charging using the selected charging method. The information processing device according to claim 1 .

5. the control unit obtains the first charge amount from a current remaining charge of the battery, a first power consumption amount of the battery that is expected to be consumed by the operation of the specified device for a specified time, and a second power consumption amount of the battery that is expected to be consumed by at least updating the first program. The information processing device according to claim 1 .

6. the first plan further includes downloading update data for the first program; The control unit is acquiring the first charge amount based on a third power consumption amount of the battery that is expected to be consumed in downloading update data for the first program, in addition to the first power consumption amount and the second power consumption amount; The information processing device according to claim 5 .

7. the first time is a time until the next start of use of the predetermined device, The control unit is and acquiring a second time required for updating the first program based on a data amount of update data used when the first program is updated; creating the first schedule so that the time until the next start of use of the predetermined device is at least the second time; The information processing device according to claim 1 .

8. The control unit is and acquiring a third time required for downloading the update data of the first program based on a data amount of the update data used when the first program is updated; creating the first schedule so that the time until the start of use of the predetermined device is at least equal to or greater than the sum of the second time and the third time; The information processing device according to claim 7.

9. the predetermined device is an autonomous vehicle, the information processing device is a server that communicates with the vehicle, The control unit transmits the first plan to the vehicle. The information processing device according to claim 1 .

10. the predetermined device is an autonomous vehicle, The information processing device is a computer installed in the vehicle. The information processing device according to claim 1 .

11. the predetermined device is a portable terminal, the information processing device is a server that communicates with the terminal, The control unit transmits the first plan to the terminal. The information processing device according to claim 1 .

12. The computer acquiring information regarding an update of a first program, the information including a data amount of update data used when a first program installed in a predetermined device is updated; obtaining a first charge amount required for a battery that operates the predetermined device based on information regarding an update of the first program; selecting a charging method capable of charging at least the first charge amount within a first time range from among a plurality of charging methods; creating a first plan including a charging plan for at least the first charge amount of the battery by the selected charging method and an update plan for at least the first program; Execute Information processing methods.

13. The computer acquires the first time based on schedule information of the specified device or schedule information of a user of the specified device. The information processing method according to claim 12.

14. the computer obtains the first charge amount from a current remaining charge of the battery and a first power consumption amount of the battery that is expected to be consumed during operation of the specified device for a specified period of time; 14. The information processing method according to claim 12 or 13.

15. The computer includes: when an update for the first program exists, selecting whether to perform normal charging or quick charging based on a prediction of an amount of power consumed by the predetermined device in the future, and generating the first plan for updating the first program during charging by the selected charging method; The information processing method according to any one of claims 12 to 14.

16. the computer obtains the first charge amount from a current remaining charge of the battery, a first power consumption amount of the battery that is expected to be consumed by the operation of the specified device for a specified time, and a second power consumption amount of the battery that is expected to be consumed by at least updating the first program; 16. The information processing method according to claim 12.

17. the first plan further includes downloading update data for the first program; The computer includes: acquiring the first charge amount based on a third power consumption amount of the battery that is expected to be consumed in downloading update data for the first program, in addition to the first power consumption amount and the second power consumption amount; The information processing method according to claim 16.

18. the first time is a time until the next start of use of the predetermined device, The computer includes: and acquiring a second time required for updating the first program based on a data amount of update data used when the first program is updated; creating the first schedule so that the time until the next start of use of the predetermined device is at least the second time; 18. The information processing method according to any one of claims 12 to 17.

19. The computer includes: and acquiring a third time required for downloading the first program based on a data amount of update data used when the first program is updated; creating the first schedule so that the time until the start of use of the predetermined device is at least equal to or greater than the sum of the second time and the third time; 20. The information processing method according to claim 18.

20. Acquiring information regarding an update of a first program installed in a specified device, the information including a data amount of update data used when the first program is updated; obtaining a first charge amount required for a battery that operates the predetermined device based on information regarding an update of the first program; selecting a charging method capable of charging at least the first charge amount within a first time range from among a plurality of charging methods; creating a first plan including a charging plan for at least the first charge amount of the battery by the selected charging method and an update plan for at least the first program; An information processing device including a control unit that executes The predetermined device; An information system having:

Images