server

Abstract

To reduce user disadvantage while maintaining an automatic driving system removed from a vehicle platform.SOLUTION: A vehicle server 7 comprises a processor 71, and a memory 72 in which a program which can be executed by the processor 71 is stored. The processor 71 receives a maintenance request signal indicating that predetermined maintenance is required of a first ADK2A removed from a first VP3A in a first vehicle 1A. The processor 71 acquires a maintenance schedule in which a second vehicle maintenance period which removes a second ADK2B to maintain a second VP3B in a second vehicle 1B is set, based on reception of the maintenance request signal. The processor 71 sets a first vehicle maintenance period which removes the first ADK2A from the first VP3A to perform predetermined maintenance, so as to overlap with at least a part of the second vehicle maintenance period, based on the maintenance schedule.SELECTED DRAWING: Figure 9

Description

[Technical field]

[0001] The present disclosure relates to a server and an information processing method. [Background technology]

[0002] JP 2021-5292 A (Patent Document 1) discloses an information processing device that makes it easier to improve user convenience and promote the use of rental vehicles regarding vehicle maintenance and rental vehicle reservations. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2021-5292 Summary of the Invention [Problem to be solved by the invention]

[0004] In recent years, technological development for autonomous driving of vehicles has progressed. There are also known companies that specialize in developing autonomous driving systems that comprehensively control autonomous driving. An autonomous driving system developed separately from the vehicle platform (the vehicle itself) is mounted on the vehicle platform (so-called external). Then, autonomous driving is realized when the vehicle platform operates according to commands from the external autonomous driving system.

[0005] In such vehicles, if the autonomous driving system is removed from the vehicle platform for maintenance, the vehicle cannot be used in autonomous driving mode while the autonomous driving system is being maintained, even if the vehicle platform does not require maintenance.

[0006] The present disclosure has been made in consideration of the above-mentioned problems, and aims to reduce the inconvenience to users while an autonomous driving system that has been removed from a vehicle platform is being maintained. [Means for solving the problem]

[0007] (1) A server according to an aspect of the present disclosure sets a maintenance schedule for a vehicle including a vehicle platform and an automated driving system removably mounted on the vehicle platform. The server includes a processor and a memory storing a program executable by the processor. The processor receives a maintenance request signal indicating that a first automated driving system removed from a first vehicle platform in a first vehicle requires a predetermined maintenance. Based on the reception of the maintenance request signal, the processor obtains a maintenance schedule in which a second vehicle maintenance period is set for removing a second automated driving system in a second vehicle and maintaining the second vehicle platform. By executing the program stored in the memory, the processor sets the first vehicle maintenance period, in which the first automated driving system is removed from the first vehicle platform and predetermined maintenance is performed, to overlap at least a portion of the second vehicle maintenance period based on the maintenance schedule.

[0008] According to the above configuration (1), while the first automated driving system is removed from the first vehicle platform and undergoing maintenance, the second automated driving system removed for maintenance of the second vehicle platform can be attached to the first vehicle platform of the first vehicle. Therefore, automated driving on the first vehicle platform becomes possible while the first automated driving system removed from the first vehicle platform is being maintained, thereby reducing inconvenience to the user.

[0009] (2) The processor sets the first vehicle maintenance period so that the start of the first vehicle maintenance period is within the second vehicle maintenance period.

[0010] According to the above configuration (2), when a second automated driving system is installed on a first vehicle platform, the time that the first vehicle platform waits until the second automated driving system is removed from the second vehicle platform can be shortened.

[0011] (3) The processor sets the first vehicle maintenance period so that removal of the first automated driving system from the first vehicle platform is completed after completion of removal of the second automated driving system from the second vehicle platform during the second vehicle maintenance period.

[0012] According to the above configuration (3), when a second automated driving system is installed on a first vehicle platform, the time that the first vehicle platform must wait until the second automated driving system is removed from the second vehicle platform can be eliminated.

[0013] (4) The maintenance schedule includes vehicle maintenance periods for one or more other vehicles in which the autonomous driving system is removed and the vehicle platform is maintained. The one or more other vehicles include a second vehicle. The processor proposes one or more candidate maintenance periods corresponding to each of the vehicle maintenance periods for the one or more other vehicles to a first user terminal associated with the first vehicle. When one of the one or more candidate maintenance periods is selected by an operation on the first user terminal, the processor sets the first vehicle maintenance period to the vehicle corresponding to the selected candidate maintenance period as the second vehicle.

[0014] According to the above configuration (4), it becomes easy to set the first vehicle maintenance period to a period that overlaps with at least a part of the second vehicle maintenance period and is convenient for the user of the first vehicle.

[0015] (5) Before setting the first vehicle maintenance period, the processor queries a second user terminal associated with the second vehicle for consent to assembling the second automated driving system to the first vehicle platform. When consent to the query is selected by an operation on the second user terminal, the processor sets the first vehicle maintenance period to overlap with at least a portion of the second vehicle maintenance period.

[0016] According to the above configuration (5), it becomes easier for the user of the first vehicle to obtain consent from the user of the second vehicle to use the second autonomous driving system, and the user of the first vehicle can more reliably use the second autonomous driving system during the first vehicle maintenance period.

[0017] (6) An information processing method according to another aspect of the present disclosure is an information processing method by a computer, the information processing method including a step of setting, by the computer, a maintenance schedule for a vehicle including a vehicle platform and an autonomous driving system removably mounted on the vehicle platform, The setting step includes a step of receiving a maintenance request signal indicating that a first autonomous driving system removed from the first vehicle platform in a first vehicle requires predetermined maintenance, a step of acquiring a maintenance schedule in which a second vehicle maintenance period is set for removing the second autonomous driving system in a second vehicle and maintaining the second vehicle platform based on the reception of the maintenance request signal, and a step of setting, based on the maintenance schedule, the first vehicle maintenance period for removing the first autonomous driving system from the first vehicle platform and performing the predetermined maintenance so as to overlap at least a part of the second vehicle maintenance period.

[0018] According to the method (6) above, similar to the configuration (1) above, while the first autonomous driving system removed from the first vehicle platform is being maintained, the second autonomous driving system enables autonomous driving of the first vehicle, thereby reducing inconvenience to the user. Effect of the Invention

[0019] According to the present disclosure, it is possible to reduce inconvenience to users while an autonomous driving system that has been removed from a vehicle platform is being maintained. [Brief description of the drawings]

[0020] [Figure 1] 1 is a diagram illustrating an overall configuration of an information processing system according to an embodiment of the present disclosure. [Diagram 2]FIG. 2 is a diagram showing the configuration of an ADK and a VP in more detail. [Diagram 3] FIG. 2 is a block diagram showing a typical hardware configuration of a dealer server. [Figure 4] FIG. 1 is a block diagram showing a typical hardware configuration of an ADK server. [Diagram 5] FIG. 2 is a block diagram showing a typical hardware configuration of a vehicle server. [Figure 6] FIG. 1 is a conceptual diagram showing a schematic configuration of a database relating to ADK abnormality information. [Figure 7] FIG. 1 is a conceptual diagram showing a schematic configuration of a database having information regarding the required maintenance time for an ADK. [Figure 8] FIG. 1 is a conceptual diagram of a maintenance schedule. [Figure 9] FIG. 2 is a sequence diagram showing a process flow in the information processing system according to the embodiment. [Figure 10] 10 is a sequence diagram showing the flow of processing in the information processing system according to the present embodiment, following FIG. [Figure 11] FIG. 13 is a diagram showing an input screen of a first user terminal for selecting whether or not to use another idle ADK rental service when preparing an ADK. [Figure 12] FIG. 13 is a diagram showing an input screen of a first user terminal for selecting a matching candidate in matching with an idle ADK. [Figure 13] This is the screen which is displayed after the maintenance schedule setting is selected in FIG. 12, and which allows the user to set and confirm the details of the maintenance schedule. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0021] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. In the drawings, the same or corresponding parts are denoted by the same reference characters, and the description thereof will not be repeated.

[0022] In this disclosure and its embodiments, "maintenance" of an autonomous driving system refers to any action for maintaining the autonomous driving system in a normal state or for restoring the autonomous driving system to a normal state from an abnormal state. Maintenance may include inspection, repair, adjustment, and replacement. The same applies to "maintenance" of a vehicle platform.

[0023] [Embodiment] <Overall system configuration> 1 is a diagram illustrating a schematic overall configuration of an information processing system according to an embodiment of the present disclosure. An information processing system 100 manages a plurality of vehicles. In reality, a large number of vehicles can be managed, but for convenience of explanation, a first vehicle 1A and a second vehicle 1B different from the first vehicle 1A will be described as specific vehicles 1. These vehicles 1 are autonomous vehicles and include an autonomous driving kit (ADK) 2 and a vehicle platform (VP) 3.

[0024] The ADK2 creates a driving plan for the vehicle 1. The ADK2 outputs various control requests for driving the vehicle 1 according to the driving plan to the VP3 according to an API (Application Program Interface) defined for each control request. The ADK2 also receives various signals indicating the vehicle state (VP3 state) from the VP3 according to an API defined for each signal. The ADK2 then reflects the vehicle state in the driving plan. The ADK2 is attached to the rooftop of the VP3, for example. The ADK2 can also be removed from the VP3. The ADK2 corresponds to the "autonomous driving system" according to the present disclosure.

[0025] The VP3 executes driving control in the autonomous driving mode according to control requests from the ADK2. When the ADK2 is removed, the VP3 can also execute driving control in the manual mode (driving control according to the driver's operation).

[0026] The ADK2 and VP3 transmit various information (ADK abnormality information, VP abnormality information, etc., which will be described later) to a server in the information processing system 100. The detailed configurations of the ADK2 and VP3 will be described with reference to FIG.

[0027] The user of the vehicle 1 is typically an individual user, but is not limited to this. The user may also be a business that provides an autonomous driving service using the vehicle 1 (such as a taxi business, a rental car business, a car sharing business, or a ride sharing service business). The user has a user terminal 4. The user terminal 4 is a smartphone, a tablet, a personal computer, or the like. The user terminal 4 displays information received from a server in the information processing system 100. In addition, the user terminal 4 accepts user operations and transmits the results of the user's selection to the server.

[0028] The information processing system 100 includes a dealer server 5, an ADK server 6, and a vehicle server 7. The servers are connected to each other via a network so as to be able to communicate with each other bidirectionally.

[0029] The dealer server 5 is a server operated by the dealer (sales store) of the vehicle 1. In this example, the vehicle 1 (ADK2 and VP3) is maintained by the dealer. Therefore, the dealer server 5 manages a maintenance schedule (see FIG. 8) for the vehicle 1. The dealer server 5 transmits the maintenance schedule to the vehicle server 7, for example, in response to a request from the vehicle server 7. FIG. 1 shows the information processing system 100 when a maintenance schedule for a first vehicle 1A is set. A second vehicle 1B shows a vehicle 1 for which a maintenance schedule has already been set or which is being maintained at a dealer.

[0030] The vehicle 1 may also be maintained by another facility such as a maintenance shop. In that case, the information processing system 100 may include, instead of or in addition to the dealer server 5, another server operated by the facility.

[0031] The ADK server 6 is, for example, a server operated by the manufacturer of the ADK 2. The ADK server 6 may be operated by a maintenance management company for the ADK 2. The ADK server 6 collects information on abnormalities in the ADK 2 from the ADK 2. Hereinafter, this information is also referred to as "ADK abnormality information." The ADK server 6 includes a database (see FIG. 6) for storing ADK abnormality information collected from multiple vehicles 1. The ADK server 6 transmits the ADK abnormality information to the dealer server 5 prior to maintenance of the ADK 2. This enables the dealer to perform appropriate maintenance of the ADK 2. Note that the ADK abnormality information is not notified from the ADK 2 to the VP 3.

[0032] The vehicle server 7 is, for example, a server operated by the manufacturer of the vehicle 1. The vehicle server 7 collects information regarding abnormalities in the VP3 from the VP3. Hereinafter, this information is also referred to as "VP abnormality information." The vehicle server 7 has a database for storing VP abnormality information from multiple vehicles 1. Prior to maintenance of the VP3, the vehicle server 7 transmits the VP abnormality information to the dealer server 5. This enables the dealer to perform appropriate maintenance of the VP3.

[0033] When an abnormality that requires maintenance occurs in the ADK2, the ADK server 6 transmits a maintenance request for the ADK2 together with the ADK abnormality information to the vehicle server 7. Hereinafter, this request is also referred to as an "ADK maintenance request." When the vehicle server 7 receives the ADK maintenance request, it creates a candidate maintenance period by referring to the maintenance schedule acquired from the dealer server 5. At this time, the maintenance schedule includes a vehicle maintenance period for the second vehicle 1B described later. The vehicle server 7 transmits the created candidate maintenance period to the user terminal 4. The user operates the user terminal 4 to select a candidate maintenance period that the user desires, and further selects a more detailed desired maintenance schedule from among the selected candidate maintenance period. The user terminal 4 transmits the desired maintenance schedule selected by the user to the vehicle server 7. The vehicle server 7 outputs a notification to the dealer server 5 to confirm the maintenance reservation with the contents of the desired maintenance schedule selected by the user. As a result, the maintenance schedule is updated in the dealer server 5.

[0034] In addition, in FIG. 1, it has been described that the vehicle server 7 creates the candidate maintenance periods in the user terminal 4. In this case, the vehicle server 7 corresponds to the "server" according to the present disclosure. However, instead of the vehicle server 7, the dealer server 5 may create the candidate maintenance periods. In that case, an ADK maintenance request is transmitted from the ADK server 6 to the dealer server 5, and a maintenance request for VP3 is transmitted from the vehicle server 7 to the dealer server 5 as necessary. Also, the ADK server 6 may create the candidate maintenance periods.

[0035] Each of the dealer server 5, the ADK server 6, and the vehicle server 7 may be a server owned by the business operator. Each server may be a shared server shared by multiple business operators including the business operator. Each server may be a cloud server provided by a cloud server management company.

[0036] <Vehicle configuration> 2 is a diagram showing the configuration of the ADK and VP in more detail. The ADK 2 includes a computer 21, a recognition sensor 22, a posture sensor 23, a sensor cleaner 24, an HMI (Human Machine Interface) 25, and a communication module 26.

[0037] VP3 includes a vehicle control interface box (VCIB) 31 and a base vehicle 32. The base vehicle 32 includes an ECU 321, a brake system 322, a steering system 323, a powertrain system 324, an active safety system 325, a body system 326, and a digital communication module (DCM) 327. The brake system 322 includes brake systems 322A and 322B. The steering system 323 includes steering systems 323A and 323B. The powertrain system 324 includes an electric parking brake (EPB) system 324A, a parking lock (P lock) system 324B, and a propulsion system 324C.

[0038] The computer 21 is redundant and includes two processors 211, 212. The computer 21 (each of the processors 211, 212) acquires data on the environment of the vehicle 1 using the recognition sensor 22 when the vehicle 1 is autonomously driven. The computer 21 also acquires data on the attitude, behavior, and position of the vehicle 1 using the attitude sensor 23 when the vehicle 1 is autonomously driven. Furthermore, the computer 21 is communicably connected to the VCIB 31. The computer 21 acquires the vehicle state from the VP3 via the VCIB 31 and sets the next operation of the vehicle 1 (accelerate, decelerate, turn, etc.). The computer 21 outputs various commands for realizing the next operation to the VP3 via the VCIB 31.

[0039] The recognition sensor 22 is a sensor for recognizing the environment of the vehicle 1. The recognition sensor 22 includes at least one of, for example, a LIDAR (Laser Imaging Detection and Ranging), a millimeter wave radar, and a camera (none of which are shown). The LIDAR measures the distance and direction of an object by emitting, for example, an infrared pulse laser light and detecting the reflected light of the laser light from the object. The millimeter wave radar measures the distance and direction of an object by emitting millimeter waves and detecting the reflected wave of the millimeter waves from the object. The camera captures an image of the surroundings of the vehicle 1. The recognition sensor 22 corresponds to the "sensor" according to the present disclosure.

[0040] The attitude sensor 23 is a sensor for detecting the attitude, behavior, and position of the vehicle 1. The attitude sensor 23 includes, for example, an IMU (Inertial Measurement Unit) and a GPS (Global Positioning System) (neither shown). The IMU detects, for example, the acceleration in the forward / backward, left / right, and up / down directions of the vehicle 1, and the angular velocities in the roll, pitch, and yaw directions of the vehicle 1. The GPS identifies the position of the vehicle 1 using information received from multiple GPS satellites orbiting the Earth.

[0041] The sensor cleaner 24 is configured to remove dirt adhering to the above-mentioned various sensors (camera lenses, laser light irradiation parts, etc.) while the vehicle 1 is traveling by using a cleaning liquid, a wiper, etc. The HMI 25 is configured to be connected to an input / output device (not shown) such as a touch panel display provided on the base vehicle 32. The communication module 26 is configured to enable two-way data communication between the computer 21 and the ADK server 6.

[0042] The VCIB 31 is communicatively connected to the ADK 2 via a controller area network (CAN) or the like. The VCIB 31 executes a predetermined API defined for each signal to receive various control requests from the ADK 2 and output vehicle states to the ADK 2. When the VCIB 31 receives a control request from the ADK 2, it outputs a control command corresponding to the control request to a system corresponding to the control command via the ECU 321. The VCIB 31 also acquires various information related to the vehicle state (state of the base vehicle 32) via the ECU 321, and outputs the acquired information to the ADK 2.

[0043] The VCIB31 includes a VCIB311 and a VCIB312. The VCIB311 and the VCIB312 basically have the same functions. However, between the VCIB311 and the VCIB312, some of the buses connected to the systems of the base vehicle 32 are different. Specifically, the VCIB311 is communicatively connected to the brake system 322A, the steering system 323A, the EPB system 324A, the P-lock system 324B, the propulsion system 324C, and the body system 326. The VCIB312 is communicatively connected to the brake system 322B, the steering system 323B, and the P-lock system 324B.

[0044] The ECU 321 integrates and controls the systems in the base vehicle 32 in cooperation with the ADK 2. The ECU 321 also transmits various information indicating the vehicle state to the vehicle server 7 via the DCM 327, and transmits various requests to the vehicle server 7. The ECU 321 also receives commands or notifications from the vehicle server 7 via the DCM 327.

[0045] Each of the brake systems 322A and 322B is configured to control a brake device (not shown) provided on each wheel of the base vehicle 32. The brake device includes, for example, a disk brake system that operates according to a hydraulic pressure adjusted by an actuator. The brake system 322A generates a braking command for the brake device according to a control request transmitted from the ADK2 via the VCIB311.

[0046] Each of the steering systems 323A and 323B is configured to control the steering angle of the steering wheels of the vehicle 1 using a steering device (not shown). The steering device includes, for example, an electric power steering (EPS) capable of adjusting the steering angle by an actuator. The steering system 323A generates a steering command for the steering device according to a control request transmitted from the ADK2 via the VCIB 311. The steering system 323B generates a steering command for the steering device according to a control request transmitted from the ADK2 via the VCIB 312.

[0047] The EPB system 324A controls an EPB (not shown) provided on at least one of the wheels in accordance with a control request transmitted from the ADK2 via the VCIB 311. The EPB fixes the wheel by, for example, operating a drum brake for parking braking.

[0048] The P lock system 324B controls a P lock device (not shown) provided on the transmission in accordance with a control request transmitted from the ADK2 via the VCIB 311. The P lock device fixes the rotation of the output shaft of the transmission by engaging a parking lock pole with a lock gear provided and connected to a rotating element in the transmission. This fixes the wheels.

[0049] The propulsion system 324C switches the shift range of a shift device (not shown) in accordance with a control request transmitted from the ADK2 via the VCIB 311. The propulsion system 324C also controls the driving force from a driving source (such as a motor generator or an engine, not shown) in accordance with a control request from the ADK2.

[0050] The active safety system 325 detects an obstacle in front or behind the vehicle 1 using a group of sensors (camera, radar, sensor, etc.) not shown. The active safety system 325 determines whether or not there is a possibility that the vehicle 1 will collide with the obstacle based on the distance between the vehicle 1 and the obstacle and the moving direction of the vehicle 1. If the active safety system 325 determines that there is a possibility of a collision, it outputs a braking command to the brake system 322A to increase the braking force.

[0051] The body system 326 is configured to control components such as turn signals, a horn, and windshield wipers (none of which are shown) in accordance with, for example, the driving state or environment of the vehicle 1. The body system 326 controls each of the above components in accordance with a control request transmitted from the ADK2 via the VCIB31.

[0052] The DCM 327 is an in-vehicle communication module that is configured to enable two-way data communication between the ECU 321 and the vehicle server 7.

[0053] <Server hardware configuration> 3 is a block diagram showing a typical hardware configuration of a dealer server. The dealer server 5 includes a processor 51, a memory 52, a keyboard 53, a mouse 54, a display 55, and a communication interface (IF) 56. The memory 52 includes a read only memory (ROM) 521, a random access memory (RAM) 522, and a hard disk drive (HDD) 523. The processor 51, the memory 52, the keyboard 53, the mouse 54, the display 55, and the communication IF 56 are connected to each other via a bus.

[0054] The processor 51 controls the overall operation of the dealer server 5. The memory 52 stores an operating system and application programs executed by the processor 51. In particular, the HDD 523 of the dealer server 5 stores a required time maintenance database (see FIG. 7) that stores information that serves as an estimate of the time required for maintenance to recover from various abnormalities in the ADK 2, and a maintenance schedule (see FIG. 8). The keyboard 53 and mouse 54 accept input from an operator of the dealer server 5. The display 55 displays various information to the operator. The communication IF 56 is configured to be capable of communicating with other servers (the ADK server 6 and the vehicle server 7).

[0055] 4 is a block diagram showing a typical hardware configuration of an ADK server. The hardware configuration of the ADK server 6 is basically the same as that of the dealer server 5, and therefore will not be described repeatedly. A database (see FIG. 6) related to ADK abnormality information collected from the ADK 2 is stored in the HDD 623 of the ADK server 6.

[0056] 5 is a block diagram showing a typical hardware configuration of a vehicle server. The hardware configuration of the vehicle server 7 is basically the same as that of the dealer server 5, so the description will not be repeated. The HDD 723 of the vehicle server 7 stores a database of VP abnormality information collected from a large number of VPs 3 and the above-mentioned user registration information. <Database> 6 is a conceptual diagram showing the schematic configuration of a database relating to ADK anomaly information. The database has a data table 81. In the data table 81, for each identification number (ADK-ID) of a plurality of ADKs 2, the identification number (VP-ID) of the VP3 in which that ADK 2 is mounted and information relating to an anomaly that has occurred in that ADK 2 (ADK anomaly information) are associated. The ADK anomaly information is represented using a predefined anomaly code.

[0057] The abnormality code includes a section (such as a symbol or a numerical value) indicating the location of the abnormality. In this example, the abnormality code includes a section indicating which of the computer 21, the recognition sensor 22, the attitude sensor 23, the sensor cleaner 24, the HMI 25, and the communication module 26 (see FIG. 2) is the abnormal location. Although not shown in order to avoid cluttering the drawing, it is desirable for the abnormality code to include a section that specifies the abnormal location in more detail. For example, in a configuration in which the recognition sensor 22 includes a LIDAR and a camera (neither of which is shown), the abnormality code may include a section indicating which of the LIDAR and the camera is the abnormal location.

[0058] The abnormality code further includes a classification (symbol, numerical value, etc.) indicating whether the maintenance of the ADK2 to eliminate the abnormality corresponding to the abnormality code is maintenance that requires the ADK2 to be removed from the VP3, maintenance that does not require the ADK2 to be removed from the VP3 but can be performed by removing the ADK2 from the VP3, or maintenance that cannot be performed by removing the ADK2 from the VP3. Therefore, the vehicle server 7 that receives the ADK abnormality signal from the ADK server 6 can determine whether or not it is necessary and possible to remove the ADK2 when setting a maintenance schedule for the vehicle 1, based on the abnormality code of the ADK2. An abnormality that requires the ADK2 to be removed from the VP3 for maintenance is typically an error in the computer 21.

[0059] The abnormality code does not necessarily have to include a category indicating whether or not the ADK2 needs to be removed to resolve the abnormality corresponding to the abnormality code. If the abnormality code does not include such a category, the HDD 723 of the vehicle server 7 has a database that predetermines whether or not the ADK2 needs to be removed during maintenance corresponding to the ADK abnormality information. In this way, the vehicle server 7 that receives an ADK abnormality signal from the ADK server 6 can determine whether or not the ADK2 needs to be removed when setting a maintenance schedule for the vehicle 1 by referring to the database based on the abnormality code of the ADK2. In the database, an abnormality code indicating the ADK abnormality information is associated with whether or not the ADK2 needs to be removed during maintenance to resolve the abnormality based on the ADK abnormality information.

[0060] FIG. 7 is a conceptual diagram showing a schematic configuration of a database having information on the required maintenance time of an ADK. As shown in FIG. 7, the HDD 523 of the dealer server 5 stores a database in which information on the required maintenance time is saved, for reference when notifying the user terminal 4 of an estimated required maintenance time or when creating a candidate maintenance period, which will be described later. The database has a data table 82. In the data table 82, various information on maintenance for eliminating the abnormality of the ADK2 at the dealer who operates the dealer server 5 is associated with an abnormality code that defines the abnormality information of the ADK. In the example shown in FIG. 7, for each abnormality code, the required maintenance time when the maintenance corresponding to the abnormality code is performed, whether or not the ADK needs to be removed, whether or not it is possible, the required time to remove the ADK2 when the ADK2 is removed from the VP3 during the maintenance, and the required time to reattach the ADK2 to the VP3 after the maintenance of the ADK2 are set in advance. The ADK removal time and ADK installation time may be preset individually corresponding to each code of the ADK abnormality information, or may be set to the same time regardless of the ADK abnormality information. The database having information regarding the maintenance time required for the ADK2 described above also includes information regarding the time required to remove the ADK2 from the VP3 and the time required to install the ADK2 from the VP3 when no abnormality has occurred in the vehicle 1 (not shown).

[0061] <Maintenance Schedule> When some abnormality occurs in the ADK2 and / or VP3 and maintenance becomes necessary, the user brings the vehicle 1 to a dealer and requests maintenance. As described above, the dealer server 5 has a maintenance schedule for monitoring the ADK2 and VP3 scheduled for maintenance or currently being maintained at the dealer. This allows the vehicle server 7 to set a maintenance schedule for the vehicle 1 that requires maintenance, taking into account the maintenance status of other vehicles 1.

[0062] Fig. 8 is a conceptual diagram of a maintenance schedule. In this embodiment, an example will be described in which a dealer has three or more facilities capable of maintaining or storing ADK2 and three or more facilities capable of maintaining or storing VP3. In Fig. 8, two of the three or more facilities capable of maintaining or storing ADK2 are described as "ADK-1" and "ADK-2", and two of the three or more facilities capable of maintaining or storing VP3 are described as "VP-1" and "VP-2", and schedules for facilities other than these are not shown.

[0063] In the maintenance schedule 83 shown in Fig. 8, the identification information (ADK-ID) of the ADK2 or the identification information (VP-ID) of the VP3 to be maintained or stored at each facility is set for each one-hour time slot. In the maintenance schedule 83, an outline of the work to be performed at each facility is set for each one-hour time slot. The outline of the work includes "maintenance", which is the actual maintenance work to eliminate the abnormality of the ADK2 or VP3, "removal", which is the work to remove the ADK2 from the VP3, "installation", which is the work to install the ADK2 to the VP3, and "idle", which is simply storing the VP3 or ADK2 that is not to be maintained. In Fig. 8, the ADK2 to be removed from and installed at the VP3 in "removal" and "installation" are represented by the identification information (ADK-ID) of the ADK2.

[0064] That is, in the example of the maintenance schedule 83 shown in FIG. 8, it is understood that the following maintenance is scheduled to be performed at the facilities of "VP-1" and "ADK-1". First, in "VP-1", ADK2 is removed from VP3. The removed ADK2 is stored in "ADK-1" without being maintained and becomes idle, while in "VP-1", maintenance of VP3 from which ADK2 has been removed is performed. Then, after the maintenance of VP3 is completed in "VP-1", ADK2 stored in "ADK-1" is reattached to VP3 in "VP-1". That is, by acquiring the maintenance schedule 83, it is possible to obtain information that there is an ADK2 that has been removed from VP3 and is stored in a dealer without being maintained and becomes idle during a specific period.

[0065] An abnormality that requires the ADK2 to be removed before servicing the VP3 is typically a deformation of the roof of the VP3 or a base (not shown) attached to the roof. Since the ADK2 is fixed to the base, these deformations distort the origin of the coordinates of the recognition sensor 22. Therefore, it becomes necessary to remove the ADK2 before servicing the VP3.

[0066] In the information processing system 100 according to this embodiment, as in the above example, when the vehicle maintenance period of one or more vehicles 1 (corresponding to the second vehicle 1B described later) in which ADK2 (corresponding to the second ADK2B described later) is removed and VP3 (corresponding to the second VP3B described later) is maintained is set in the maintenance schedule 83, the maintenance schedule of the first vehicle 1A in which the first ADK2A is removed from the first VP3A and only the first ADK2A is maintained is set by referring to this. As a result, during the maintenance of the first ADK2A, the idle second ADK2B is mounted on the first VP3A, so that the first VP3A can continue to be used in automatic driving. Hereinafter, the flow of the process of setting the maintenance schedule of the first vehicle 1A in the information processing system 100 according to this embodiment will be described.

[0067] <System processing sequence> Fig. 9 is a sequence diagram showing the flow of processing in the information processing system according to this embodiment. In Fig. 9, from left to right, processing executed by the first user terminal 4A, the ADK server 6, the vehicle server 7, the dealer server 5, and the second user terminal 4B is shown. Hereinafter, a sequence is referred to as "SQ." Note that, below, the flow of processing is shown when an abnormality occurs only in the first ADK 2A in the first vehicle 1A, and no abnormality occurs in the first VP 3A.

[0068] 9, the ADK server 6 transmits to the vehicle server 7 ADK abnormality information (see FIG. 6) indicating that an abnormality has occurred in the first ADK 2A and that the first ADK 2A removed from the first VP 3A in the first vehicle 1A requires specified maintenance (SQ1). At the same time, the ADK server 6 transmits a maintenance request signal based on the ADK abnormality signal (SQ2), and the vehicle server 7 receives this maintenance request signal.

[0069] Based on the ADK abnormality signal and the ADK maintenance request signal, the vehicle server 7 requests the dealer server 5 operated by the dealer in charge of the first vehicle 1A for the required maintenance time for the dealer to perform the specified maintenance (SQ3). In response to the request from the vehicle server 7, the dealer server 5 refers to the maintenance time database (see FIG. 7) and transmits the required maintenance time and related information to the vehicle server 7 (SQ4).

[0070] The vehicle server 7 transmits to the first user terminal 4A information that the first ADK2A needs a specific maintenance, and transmits the required maintenance period if the specific maintenance is performed at the dealer in charge. Furthermore, the vehicle server 7 inquires of the first user terminal 4A whether to use an idle ADK rental service when the specific maintenance of the first ADK2A is performed at the dealer (SQ5). In this embodiment, the idle ADK rental service refers to a service in which, if there is an idle ADK at the dealer where the maintenance is scheduled, the idle ADK is installed in the first VP3A, and the first VP3A can be used in automatic driving even during the maintenance of the first ADK2A. The idle ADK refers to an ADK2 that is not used and is stored in an idle state at the dealer in charge when the ADK2 is removed from the VP3 in a certain vehicle 1 and only the VP3 is maintained.

[0071] The first user terminal 4A accepts an operation on the first user terminal 4A in response to the inquiry as to whether or not to use the above-mentioned service, and transmits to the vehicle server 7 a notification that the first user has selected to use the service (SQ6).

[0072] When the vehicle server 7 receives the selection of the use of the service, it requests the dealer server 5 for maintenance schedule information of vehicles 1 other than the first vehicle 1A in order to provide candidates for idle ADKs (SQ7). At this time, the maintenance schedule information requested by the vehicle server 7 is maintenance schedule information for a vehicle 1 for which the VP3 from which the ADK2 has been removed is to be maintained and the ADK2 does not require maintenance and is to be stored separately at the dealer in charge. In response to the request for maintenance schedule information, the dealer server 5 transmits the maintenance schedule information of vehicles 1 other than the first vehicle 1A based on the maintenance schedule (see FIG. 8) (SQ8). The maintenance schedule information includes the vehicle maintenance period of each vehicle, and the vehicle maintenance period further includes the period for removing the ADK2 mounted on the VP3, the period for maintaining the VP3 after removing the ADK2 (in other words, the period for which the ADK2 is idle), and the period for attaching the ADK2 to the VP3 after maintenance is completed.

[0073] The above-mentioned maintenance schedule information includes maintenance schedule information for the second vehicle 1B, which will be described later. Therefore, based on receiving the maintenance request signal at SQ2, the vehicle server 7 acquires, after SQ3 to SQ6, at SQ7 and SQ8, a maintenance schedule in which a second vehicle maintenance period is set for removing the second ADK2B from the second vehicle 1B and maintaining the second VP3B.

[0074] The vehicle server 7 creates one or more candidate maintenance periods for maintaining the first vehicle 1A based on the acquired maintenance schedule (SQ9). The one or more candidate maintenance periods correspond to respective vehicle maintenance periods of one or more other vehicles other than the first vehicle 1A.

[0075] Fig. 10 is a sequence diagram showing the flow of processing in the information processing system according to this embodiment, following Fig. 9. As shown in Fig. 10, the vehicle server 7 transmits one or more candidate maintenance periods to the first user terminal 4A associated with the first vehicle 1A and proposes them (SQ10). The first user terminal 4A accepts an operation of the first user terminal 4A in response to the proposal of one or more candidate maintenance periods, and transmits to the vehicle server 7 that one maintenance period has been selected from the one or more candidate maintenance periods (SQ11).

[0076] The vehicle server 7 inquires of the first user terminal 4A about a detailed desired maintenance date within the selected maintenance period (SQ12). Specifically, the vehicle server 7 inquires about the start date of maintenance of the first vehicle 1A. In response to the request for the desired maintenance date from the vehicle server 7, the first user terminal 4A accepts an operation of the first user terminal 4A, and transmits the desired maintenance date input or selected by the operation to the vehicle server 7 (SQ13). The desired maintenance date specifically includes the start date of maintenance.

[0077] When one of the one or more candidate maintenance periods is selected by an operation on the first user terminal 4A in SQ11, the vehicle server 7 makes an inquiry to the second user terminal 4B associated with the second vehicle 1B for consent to assembling the second ADK 2B to the first VP 3A (ADK loan consent inquiry) via SQ12 and SQ13 (SQ14). That is, the second vehicle 1B is a vehicle 1 for which a maintenance period has already been set corresponding to the maintenance period of the first vehicle 1A selected in SQ11, and for which it is set in the maintenance schedule that the second ADK 2B is to be removed from the second VP 3B and only the second VP 3B is to be maintained. In response to the ADK rental approval inquiry, the second user terminal 4B accepts an operation by the second user on the second user terminal 4B, and transmits to the vehicle server 7 that the operation has selected approval to attach the second ADK 2B to the first VP 3A (ADK rental approval) (SQ15).

[0078] When the vehicle server 7 receives the ADK rental acceptance transmitted from the second user terminal 4B, it sets the first vehicle maintenance period by designating the vehicle corresponding to the candidate maintenance period selected in SQ11 as the second vehicle 1B.

[0079] Then, the vehicle server 7 transmits to the dealer server 5 and the first user terminal 4A the fact that the first vehicle maintenance period has been set, i.e., the maintenance contents of the first vehicle 1A have been finalized (SQ16). The maintenance contents of the first vehicle 1A specifically include the work of removing the first ADK2A from the first VP3A in response to the ADK abnormality information and the maintenance request signal, the work of attaching the second ADK2B to the first VP3A, the work of servicing the first ADK2A in response to the ADK abnormality information and the maintenance request signal, the work of removing the second ADK2B from the first VP3A, and the work of attaching the first ADK2A that has been serviced to the first VP3A. Then, when the dealer server 5 receives the fact that the above maintenance contents have been finalized from the vehicle server 7, it updates the maintenance schedule (SQ17).

[0080] After setting the first vehicle maintenance period, the vehicle server 7 notifies that there is a plan to attach a second ADK 2B to the first VP 3A (ADK reassignment plan) during the first vehicle maintenance period (SQ18). Upon receiving the notification of the ADK reassignment plan, the ADK server 6 stores information related to the ADK reassignment plan in the memory of the vehicle server 7 based on the notification (SQ19).

[0081] In the above manner, the vehicle server 7 sets a maintenance schedule for the first vehicle 1A including the first VP 3A and the first ADK 2A mounted on the first VP 3A.

[0082] <User interface> When user registration is performed at the time of sale of the vehicle 1, the user's account and password are associated with the vehicle 1 (ADK2 and VP3) owned by the user. Here, it is assumed that user registration has been completed and login (user authentication) for displaying information related to the vehicle 1 has been successful. The following describes the GUI (Graphical User Interface) displayed on the first user terminal 4A in the above flow.

[0083] 11 is a diagram showing an input screen of a first user terminal for selecting whether or not to use another idle ADK rental service when maintaining an ADK. As shown in FIG. 11, an input screen 91 includes a service use button 911 for selecting the use of the idle ADK rental service, and a normal maintenance reservation button 912 for making a normal maintenance reservation without using the service.

[0084] In the following example, a case will be described in which an abnormality represented by an abnormality code "C0245" occurs in the computer 21 of the first ADK 2A having an identification number (ADK-ID) "A00005" associated with the first user (see FIG. 6). When an abnormality represented by an abnormality code "C0245" occurs in the first ADK 2A, the first user terminal 4A is notified by the vehicle server 7 that a specified maintenance is required, and receives an inquiry about using the service at SQ5. Information related to these notifications and inquiries is displayed on the input screen 91.

[0085] The input screen 91 also has a display field 913 that displays the required maintenance period if maintenance is performed. In this example, the required maintenance period acquired in SQ3 and SQ4, "3 business days" (see FIG. 7 for the required maintenance period for the abnormality "C0245"), is displayed. This allows the user of the first user terminal 4A to decide whether or not to use the ADK rental service after taking into consideration the period during which autonomous driving is unavailable in the first vehicle 1A. The user operates the service use button 911 when using the idle ADK rental service, and operates the normal maintenance reservation button 912 when making a normal maintenance reservation without using the service.

[0086] Fig. 12 is a diagram showing an input screen of a first user terminal for selecting a matching candidate in matching with an idle ADK. As shown in Fig. 12, an input screen 92 includes a matching list display field 921 that displays a matching partner of an idle ADK, a plurality of buttons 922 for selecting a matching partner, a maintenance schedule setting button 923 for transitioning to an input screen for setting a detailed maintenance schedule after deciding on a matching partner, and a button 924 for returning to the previous input screen 91 (see Fig. 11). In this example, "Candidate A" is selected by the button 922.

[0087] In this example, "Candidate A" displayed in the matching list display field 921 is an ADK2 with an ADK-ID of "A00023" that has been removed from a VP3 with a VP-ID of "V06597" and will be idle for a predetermined period (see FIG. 8). Based on the information on the required maintenance period acquired in SQ3 and SQ4 and the information on the required maintenance period acquired in SQ7 and SQ8, a matching list that includes candidate maintenance periods is created (SQ9), and the matching list that includes the candidate maintenance periods is transmitted to the first user terminal 4A (SQ10).

[0088] In this example, referring to Fig. 8, the start date of the maintenance of vehicle 1 related to candidate A is 10:00 on April 1, 2022, so as shown in Fig. 12, the list is created with the start date of the candidate maintenance period of the first vehicle 1A corresponding to candidate A being after 10:00 on April 1, 2022, which is the start date of the maintenance of vehicle 1 related to candidate A. As a result, if the ADK2 of candidate A is to be mounted on the first VP3A as the second ADK2B, the time that the first vehicle 1A waits for the second ADK2B to be removed from the second VP3B can be shortened.

[0089] Also, in this example, referring to FIG. 8, removal of the ADK2 for the candidate A is completed at 11:00 on April 1, 2022, while referring to FIG. 7, the time required to remove the first ADK2A from the first VP3A for the abnormality that occurred in the first vehicle 1A is 1 hour. For this reason, as shown in FIG. 12, the list is created with the start date of the candidate maintenance period for the first vehicle 1A corresponding to the candidate A being after 10:00 on April 1, 2022, so that removal of the first ADK2A from the first VP3A is completed after removal of the ADK2 of the candidate A from the VP3. As a result, if the ADK2 of the candidate A is to be installed, the time to wait for the ADK2 to be removed can be omitted.

[0090] Furthermore, the matching list display field 921 displays an approximate maximum period (maximum usage period) during which the idle ADK can be used if each candidate idle ADK is to be installed. This allows the user to select an idle ADK to be matched by referring to this together with the date and time of bringing in the first vehicle 1A (i.e., the start of the first vehicle maintenance period). The maximum usage period is calculated by subtracting the period required to remove the first ADK 2A and the period required to install the first ADK 2A in the first vehicle 1A in which the ADK abnormality has occurred from the idle period of the ADK in the maintenance schedule 83 (see FIG. 8) by referring to the data table 82.

[0091] Fig. 13 is a screen for setting and confirming the details of the maintenance schedule, which is transitioned to and displayed after the maintenance schedule setting is selected in Fig. 12. As shown in Fig. 13, the input screen 93 includes a first carry-in date and time selection button 931, a scheduled maintenance completion date display field 932, a second carry-in deadline display field 933, a matching start button 934 operated to confirm the maintenance schedule and start matching with a candidate ADK, and a button 935 for returning to the previous input screen 92 (see Fig. 12). In this example, the input screen displayed after "Candidate A" is selected in Fig. 12 and the maintenance schedule setting button 923 is operated is displayed.

[0092] In Figure 13, for the first bring-in date and time, the time period after the candidate maintenance period shown in Figure 12, during which the second ADK2B can be installed and removed before the maintenance of the VP3 (second VP3B) associated with the idle ADK of "candidate A" (hereinafter, this idle ADK will be described as the "second ADK2B") is completed, can be selected using the first bring-in date and time selection button 931.

[0093] As a result, the first vehicle maintenance period is set to overlap at least a part of the maintenance period (second vehicle maintenance period) of the second vehicle 1B to which the second ADK2B was attached. This allows the second ADK2B removed for maintenance of the second VP3B to be attached to the first VP3A of the first vehicle 1A while the first ADK2A removed from the first VP3A is being maintained. This allows the first vehicle 1A to be driven automatically while the first ADK2A removed from the first VP3A is being maintained, thereby reducing inconvenience to the user.

[0094] Furthermore, the first vehicle maintenance period is set so that the start of the first vehicle maintenance period is within the second maintenance period. This makes it possible to shorten the time that the first VP3A waits until the second ADK2B is removed from the second VP3B when the second ADK2B is attached to the first VP3A. Furthermore, the first vehicle maintenance period is set so that the removal of the first ADK2A from the first VP3A is completed after the second ADK2B is removed from the second VP3B. This makes it possible to omit the time that the first VP3A waits until the second ADK2B is removed from the second VP3B when the second ADK2B is attached to the first VP3A.

[0095] Furthermore, the scheduled maintenance completion date display field 932 is updated each time the first bring-in date and time is selected. The scheduled maintenance completion date display field 932 is displayed based on the required maintenance period acquired in SQ3 and SQ4 and the selected first bring-in date and time. Furthermore, the second bring-in deadline display field 933 is displayed based on the maintenance schedule 83 (see FIG. 8) acquired in SQ7 and SQ8 and the required maintenance time (see FIG. 7) acquired in SQ3 and SQ4. In this example, the deadline is brought forward from 15:00 on April 6, 2022 (see FIG. 8) when the attachment of the second ADK2B to the second VP3B is scheduled to start, and is displayed as 14:00 on April 6, 2022 by the time required to remove the second ADK2B from the first VP3A. This means that as long as the first VP3A with the second ADK2B installed is brought in by the second delivery deadline mentioned above, the maintenance schedule for removing the second ADK2B from the first VP3A and then reattaching the second ADK2B to the original second VP3B can be maintained.

[0096] Then, when the matching start button 934 is operated, the processes of SQ14, SQ15 and SQ16 are executed.

[0097] In the above embodiment, the first user and the second user are different from each other, but the first user and the second user may be the same. If the first user and the second user are the same, SQ14 and SQ15 in FIG. 10 may be omitted.

[0098] The embodiments disclosed herein should be considered to be illustrative and not restrictive in all respects. The scope of the present disclosure is defined by the claims, not by the description of the embodiments described above, and is intended to include all modifications within the meaning and scope of the claims. [Explanation of symbols]

[0099] 1 vehicle, 1A first vehicle, 1B second vehicle, 2 autonomous driving kit (ADK), 2A first autonomous driving kit (ADK), 2B second autonomous driving kit (ADK), 21 computer, 211, 212 processor, 22 recognition sensor, 23 attitude sensor, 24 sensor cleaner, 25 HMI, 26 communication module, 3 vehicle platform (VP), 3A first vehicle platform (VP), 3B second vehicle platform (VP), 31, 311, 312 vehicle control interface box (VCIB), 32 base vehicle, 321 ECU, 322, 322A, 322B brake system, 323, 323A, 323B steering system, 324 power train system, 324A electric parking brake (EPB) system, 324B parking lock system, 324C propulsion system, 325 Active safety system, 326 body system, 327 DCM, 4 user terminal, 4A first user terminal, 4B second user terminal, 5 dealer server, 51 processor, 52 memory, 521 ROM, 522 RAM, 533 HDD, 53 keyboard, 54 mouse, 55 display, 56 communication IF, 6 ADK server, 61 processor, 62 memory, 621 ROM, 622 RAM, 623 HDD, 63 keyboard, 64 mouse, 65 display, 66 communication IF, 7 vehicle server, 71 processor, 72 memory, 721 ROM, 722 RAM, 723 HDD, 73 keyboard, 74 mouse, 75 display, 76 communication IF.

Claims

1. A server that sets a maintenance schedule for a vehicle including a vehicle platform and an autonomous driving system removably mounted on the vehicle platform, A processor; A memory in which a program executable by the processor is stored, The processor, receiving a maintenance request signal indicating that a first automated driving system removed from a first vehicle platform in a first vehicle requires predetermined maintenance; obtaining a maintenance schedule including a second vehicle maintenance period for removing the second automated driving system from the second vehicle and maintaining the second vehicle platform based on receiving the maintenance request signal; A server that executes the program stored in the memory to set a first vehicle maintenance period, during which the first autonomous driving system is removed from the first vehicle platform and the specified maintenance is performed, so as to overlap with at least a portion of the second vehicle maintenance period based on the maintenance schedule.

2. The server of claim 1 , wherein the processor sets the first vehicle maintenance period such that a start date of the first vehicle maintenance period occurs within the second vehicle maintenance period.

3. 3. The server of claim 1 or claim 2, wherein the processor sets the first vehicle maintenance period such that removal of the first automated driving system from the first vehicle platform is completed after removal of the second automated driving system from the second vehicle platform is completed during the second vehicle maintenance period.

4. The maintenance schedule includes a vehicle maintenance period for one or more other vehicles in which the autonomous driving system is removed and the vehicle platform is maintained; the one or more other vehicles includes the second vehicle, The processor, propose one or more candidate maintenance periods corresponding to respective vehicle maintenance periods of the one or more other vehicles to a first user terminal associated with the first vehicle; A server as described in any one of claims 1 to 3, wherein when one of the one or more candidate maintenance periods is selected by an operation on the first user terminal, the first vehicle maintenance period is set with the vehicle corresponding to the selected candidate maintenance period as the second vehicle.

5. The processor, Before setting the first vehicle maintenance period, a second user terminal associated with the second vehicle is inquired of for consent to assembling the second automated driving system to the first vehicle platform; A server as described in any one of claims 1 to 4, which sets the first vehicle maintenance period to overlap with at least a portion of the second vehicle maintenance period when acceptance of the inquiry is selected by operation on the second user terminal.

Images