Information processing device, method, and system

Abstract

To improve a technique of an operation management system for managing an operation of an automatic driving vehicle.SOLUTION: An information processing device 30 for managing an operation plan of one or more automatic driving vehicles includes a database for allowing one or more users, the one or more automatic driving vehicles, one or more operation diagrams, and one or more points on each one of routes of the operation diagrams to be stored in association with information of at least one area. The information processing device 30 allows the one or more operation diagrams associated with the information of at least one area related to the user to be displayed on an incorporated display or a screen of an external device for each one of the users.SELECTED DRAWING: Figure 6

Description

[Technical Field]

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

[0002] Conventionally, traffic management systems that manage operation plans for autonomous vehicles have been known. For example, Patent Literature 1 discloses that in a traffic management system, when an autonomous vehicle is affected by an obstacle on the road, instructions to resolve the obstacle on the road are automatically output to a road management system based on an image of the obstacle on the road. [Prior art documents] [Patent documents]

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

[0004] There was room for improvement in the technology of the operation management system that manages the operation plans of autonomous vehicles.

[0005] The purpose of the present disclosure, made in consideration of the above circumstances, is to improve the technology of operation management systems that manage operation plans for autonomous vehicles. [Means for solving the problem]

[0006] An information processing device according to an embodiment of the present disclosure includes: a storage unit including a database configured to store one or more users, the one or more automated driving vehicles, one or more bus schedules, and one or more points on routes in each of the one or more bus schedules in association with at least one area; a control unit that displays, for each of the one or more users, the one or more bus schedules associated with the at least one area associated with the user on a built-in display or a screen of an external device; Equipped with.

[0007] According to one embodiment of the present disclosure, a method comprises: A method executed by an information processing device that manages operation plans for one or more autonomously driven vehicles, storing in a database one or more users, the one or more automated vehicles, one or more bus schedules, and one or more points on routes in each of the one or more bus schedules in association with at least one area; Displaying, for each of the one or more users, the one or more bus schedules associated with information on the at least one area associated with the user on a built-in display or a screen of an external device; Includes.

[0008] In accordance with one embodiment of the present disclosure, a system includes: A system for managing a schedule of one or more autonomous vehicles, an information processing device and a terminal device; Equipped with the information processing device includes a database configured to store one or more users, the one or more autonomous vehicles, one or more bus schedules, and one or more points on routes in each of the one or more bus schedules in association with at least one area; The information processing device or the terminal device displays, for each of the one or more users, on a screen, the one or more bus schedules associated with information on the at least one area associated with the user. [Effects of the Invention]

[0009] According to one embodiment of the present disclosure, the technology of a fleet management system for managing the operation of autonomous vehicles is improved. [Brief explanation of the drawings]

[0010] [Figure 1] 1 is a block diagram illustrating a schematic configuration of a system according to an embodiment of the present disclosure. [Figure 2] FIG. 2 is a block diagram showing a schematic configuration of a terminal device. [Figure 3] 1 is a block diagram showing a schematic configuration of a vehicle. [Figure 4] FIG. 1 is a block diagram showing a schematic configuration of an information processing device. [Figure 5] 10 is a diagram showing an example 1 / 3 of an image of a DB configuration of the information processing device according to the present embodiment. [Figure 6] 10 is a diagram showing an example 2 / 3 of an image of a DB configuration of the information processing device according to the present embodiment. [Figure 7] 3 is an example 3 / 3 of an image of a DB configuration of the information processing device according to the present embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, embodiments of the present disclosure will be described.

[0012] (Outline of the embodiment) An overview of a system 1 according to an embodiment of the present disclosure will be described with reference to Fig. 1. The system 1 includes a plurality of terminal devices 10, a plurality of vehicles 20, and an information processing device 30. Each of the terminal devices 10, each of the vehicles 20, and the information processing device 30 are communicably connected to a network 40 including, for example, the Internet and a mobile communication network.

[0013] The terminal device 10 is a computer such as a PC (Personal Computer), a smartphone, or a tablet terminal. In this embodiment, the terminal device 10 is used by a user who manages the operation of an autonomously driven vehicle, is connected to an information processing device 30 via a network 40, and inputs and outputs information required to manage the operation of the autonomously driven vehicle.

[0014] The vehicle 20 may be an autonomous vehicle capable of autonomous driving, such as levels 1 to 5, as defined by the Society of Automotive Engineers (SAE). In this embodiment, the vehicle 20 is capable of autonomous driving at levels 3 or 4, and a driving assistant can override the driving operation by riding in the vehicle 20 or remotely. The system 1 may include any number of vehicles 20, one or more.

[0015] The information processing device 30 is, for example, one or more computers such as a server device, etc. The information processing device 30 is capable of communicating with each of the terminal devices 10 and each of the vehicles 20 via a network 40.

[0016] First, an overview of this embodiment will be described, and details will be provided later. An information processing device 30 that manages operation plans for one or more autonomous vehicles includes a database configured to store one or more users, one or more autonomous vehicles, one or more bus schedules, and one or more points on the routes in each of the one or more bus schedules in association with information on at least one area. Then, for each of the one or more users, the information processing device 30 displays the one or more bus schedules associated with the information on the at least one area associated with the user on a built-in display or a screen of an external device.

[0017] Conventional traffic management systems for autonomous vehicles have managed operations within a range that satisfies the operational design domain (ODD) registered in the traffic management system. However, unlike conventional vehicles, autonomous vehicles require a wide range of elements for operational management, which can be extremely time-consuming and prone to errors. Under these circumstances, according to this embodiment, autonomous vehicles, users, service schedules, and locations are managed in units called areas, rather than within a range that satisfies the operational design domain (ODD). This increases the likelihood of errors, such as when a traffic manager in charge of a certain area erroneously assigns an autonomous vehicle that does not satisfy the ODD when assigning an autonomous vehicle to a scheduled flight that will travel in that area. Furthermore, efficient operations can be performed, such as by making changes to the operation plan on an area-by-area basis. Therefore, this embodiment improves the technology of traffic management systems that manage autonomous vehicle operations by enabling accurate and efficient management of autonomous vehicle operations.

[0018] Next, each component of the system 1 will be described in detail.

[0019] (Terminal Device Configuration) As shown in FIG. 2, the terminal device 10 includes a communication unit 11, an output unit 12, an input unit 13, a storage unit 14, and a control unit 15.

[0020] The communication unit 11 includes one or more communication interfaces connected to the network 40. The communication interfaces are compatible with mobile communication standards such as, but not limited to, 4G (4th Generation) or 5G (5th Generation). In this embodiment, the terminal device 10 communicates with the vehicle 20 and the information processing device 30 via the communication unit 11 and the network 40.

[0021] The output unit 12 includes one or more output devices that output information. Examples of the output devices include, but are not limited to, a display that outputs information as a video or a speaker that outputs information as a sound. Alternatively, the output unit 12 may include an interface for connecting an external output device.

[0022] The input unit 13 includes one or more input devices that detect an input operation by a user. Examples of the input devices include, but are not limited to, physical keys, capacitive keys, a mouse, a touch panel, a touch screen integrated with the display of the output unit 12, or a microphone. Alternatively, the input unit 13 may include an interface for connecting an external input device.

[0023] The storage unit 14 includes one or more memories. The memories may be, for example, semiconductor memories, magnetic memories, optical memories, etc., but are not limited to these. Each memory included in the storage unit 14 may function, for example, as a main storage device, an auxiliary storage device, or a cache memory. The storage unit 14 stores any information used in the operation of the terminal device 10. The storage unit 14 may store driving performance information acquired from the vehicle 20. Furthermore, for example, the storage unit 14 may store system programs, application programs, embedded software, etc. For example, the information stored in the storage unit 14 may be updateable with information acquired from the network 40 via the communication unit 11, for example.

[0024] The control unit 15 includes one or more processors, one or more programmable circuits, one or more dedicated circuits, or a combination thereof. The processor may be, for example, a general-purpose processor such as a CPU (Central Processing Unit) or a GPU (Graphics Processing Unit), or a dedicated processor specialized for a specific process, but is not limited to these. The programmable circuit may be, for example, but is not limited to, an FPGA (Field-Programmable Gate Array). The dedicated circuit may be, for example, but is not limited to, an ASIC (Application Specific Integrated Circuit). The control unit 15 controls the operation of the terminal device 10.

[0025] (Vehicle configuration) As shown in FIG. 3, the vehicle 20 includes a communication unit 21, a sensor unit 22, a storage unit 23, and a control unit 24.

[0026] The communication unit 21 includes one or more communication interfaces connected to the network 40. The communication interfaces are compatible with mobile communication standards such as 4G (4th Generation) and 5G (5th Generation), but are not limited to these and may be compatible with any communication standard. In this embodiment, the vehicle 20 communicates with the information processing device 30 via the communication unit 21 and the network 40.

[0027] The sensor unit 22 includes one or more sensors used to control the vehicle 20. The sensors are, for example, a position sensor corresponding to a GPS (Global Positioning System) or the like, a geomagnetic sensor, a speed sensor, an acceleration sensor, a gyro sensor, or the like, but are not limited to these and may be any sensor.

[0028] The storage unit 23 includes one or more memories. In this embodiment, the "memory" may be, for example, a semiconductor memory, a magnetic memory, an optical memory, or the like, but is not limited to these. Each memory included in the storage unit 23 may function as, for example, a main memory device, an auxiliary memory device, or a cache memory. The storage unit 23 stores any information used in the operation of the vehicle 20. For example, the storage unit 23 may store a system program, an application program, embedded software, etc. The information stored in the storage unit 23 may be updatable with information obtained from the network 40 via the communication unit 21, for example.

[0029] The control unit 24 includes one or more processors, one or more programmable circuits, one or more dedicated circuits, or a combination thereof. The processor may be, for example, a general-purpose processor such as a CPU (Central Processing Unit) or a GPU (Graphics Processing Unit), or a dedicated processor specialized for a specific process, but is not limited to these. The programmable circuit may be, for example, but is not limited to, an FPGA (Field-Programmable Gate Array). The dedicated circuit may be, for example, but is not limited to, an ASIC (Application Specific Integrated Circuit). The control unit 24 controls the overall operation of the vehicle 20. (Configuration of information processing device) As shown in FIG. 4, the information processing device 30 includes a communication unit 31, an output unit 32, an input unit 33, a storage unit , and a control unit .

[0030] The communication unit 31 includes one or more communication interfaces connected to the network 40. The communication interfaces may be compatible with, for example, a wired LAN standard or a wireless LAN standard, but are not limited to these and may be compatible with any communication standard. In this embodiment, the information processing device 30 communicates with the terminal device 10 and the vehicle 20 via the communication unit 31 and the network 40, respectively.

[0031] The output unit 32 includes one or more output devices that output information. Examples of the output devices include, but are not limited to, a display that outputs information as a video or a speaker that outputs information as a sound. Alternatively, the output unit 32 may include an interface for connecting an external output device.

[0032] The input unit 33 includes one or more input devices that detect an input operation by a user. Examples of the input devices include, but are not limited to, physical keys, capacitive keys, a mouse, a touch panel, a touch screen integrated with the display of the output unit 32, or a microphone. Alternatively, the input unit 33 may include an interface for connecting an external input device.

[0033] The storage unit 34 includes one or more memories. Each memory included in the storage unit 34 may function as, for example, a main storage device, an auxiliary storage device, or a cache memory. The storage unit 34 stores any information used in the operation of the information processing device 30. For example, the storage unit 34 may store system programs, application programs, embedded software, map information, etc. In this embodiment, the storage unit 34 includes a database (DB) 300 that stores information used to manage the operation of the autonomously driven vehicle.

[0034] The control unit 35 includes one or more processors, one or more programmable circuits, one or more dedicated circuits, or a combination thereof. The control unit 35 controls the overall operation of the information processing device 30. The operation of the information processing device 30 will be described in detail later.

[0035] (Database structure of information processing device) 5, 6, and 7, the DB 300 of the information processing device 30 includes business operator data 310, user data 320, area data 330, vehicle data 340, bus schedule data 350, and location data 360. The DB 300 may also include flight data 370, operation date data 380, and passing time data 390.

[0036] The business operator data 310 is information about a business operator to which a user who uses an operation management system that manages the operation of autonomously driven vehicles provided by the information processing device 30 belongs. For example, the business operator data 310 may include a business operator ID for uniquely identifying the business operator. Also, as shown in FIG. 5 , in this embodiment, the business operator data 310 is configured to be associated with one or more pieces of user data 320, one or more pieces of area data 330, and one or more pieces of vehicle data 340.

[0037] Specifically, for example, the business data 310 may include a user ID included in one or more pieces of user data 320, an area ID included in one or more pieces of area data 330, and a vehicle ID included in one or more pieces of vehicle data 340.

[0038] The user data 320 is information about a user who uses the operation control system by using the information processing device 30 and the terminal device 10. For example, the user data 320 may include a user ID for uniquely identifying the user. In addition, as shown in FIGS. 5 and 6, in this embodiment, the user data 320 is configured to be associated with one business operator data 310 and one or more area data 330.

[0039] Specifically, for example, the user data 320 may include a business operator ID included in one business operator data 310 and an area ID included in one or more area data 330.

[0040] Area data 330 is a unit for managing the operation of an autonomous vehicle. For example, area data 330 may include an area ID for uniquely identifying an area. Furthermore, as shown in FIGS. 5 and 6 , in this embodiment, area data 330 is configured to be associated with one business operator data 310, one or more user data 320, one or more vehicle data 340, one or more bus schedule data 350, and one or more location data 360.

[0041] Specifically, for example, area data 330 may include an operator ID included in one operator data 310, a user ID included in one or more user data 320, a bus schedule ID included in one or more bus schedule data 350, and a location ID included in one or more location data 360. Furthermore, because area data 330 is a unit for managing the operation of an autonomous vehicle, the actual area of ​​one area data 330 may overlap with that of another area data 330. For example, if one area data 330 includes a location called Address A, another area data 330 may also include a location called Address A. Furthermore, area data 330 may include information on the range for managing the operation of an autonomous vehicle. Alternatively, area data 330 may include information on a corresponding autonomous driving development kit (ADK). There may be multiple pieces of information on the corresponding ADK.

[0042] The vehicle data 340 is information about the vehicle 20. For example, the vehicle data 340 may include a vehicle ID for uniquely identifying the vehicle 20. Furthermore, for example, the vehicle data 340 may include information about the model of the vehicle 20 and the ADK installed in the vehicle 20. Furthermore, as shown in FIGS. 5 and 6 , in this embodiment, the vehicle data 340 is configured to be associated with one business operator data 310 and one area data 330.

[0043] Specifically, for example, the vehicle data 340 may include an operator ID included in one piece of operator data 310 and an area ID included in one piece of area data 330. Alternatively, the vehicle data 340 may include only an area ID included in one piece of area data 330. In this case, the vehicle data 340 is configured to be associated with one piece of operator data 310 via the area data 330.

[0044] The information processing device 30 may receive information about the vehicle model of the vehicle 20 and the ADK installed in the vehicle 20 from the control unit 24 of the vehicle 20 and store the information in the vehicle data 340 corresponding to the vehicle 20 .

[0045] The bus schedule data 350 includes route information and the operation start time and operation end time of a certain flight data 370. For example, the bus schedule data 350 may include a bus schedule ID for uniquely identifying a bus schedule, the operation start time and operation end time of the flight data 370, and route information. Note that a method for calculating the operation start time and operation end time of the flight data 370 and a method for identifying the route information will be described later. Also, as shown in FIG. 7 , in this embodiment, the bus schedule data 350 is configured to be associated one-to-one with one flight data 370, to be associated with one vehicle data 340, and to be associated with one or more location data 360 and one or more operation date data 380 via one flight data 370.

[0046] Specifically, for example, the bus schedule data 350 may include a flight ID included in one flight data 370, a vehicle ID included in one vehicle data 340, a location ID included in one or more locations, and an operation day ID included in one or more operation day data 380.

[0047] Alternatively, the bus schedule data 350 may include all of the information of one flight data 370.

[0048] The point data 360 is information that uniquely identifies a stop point of the flight data 370. For example, the point data 360 may include a point ID for identifying the point and information indicating the location of the point, such as the address of the point. Note that the point data 360 differs between inbound and outbound trips of the route. Also, as shown in FIGS. 6 and 7, in this embodiment, the point data 360 is configured to be associated with one area data 330 and one or more flight data 370.

[0049] Specifically, for example, the spot data 360 may include an area ID included in one piece of area data 330. Furthermore, in this embodiment, the spot data 360 is always associated with one piece of area data 330, and therefore, even if the stop point is the same, if the area data 330 is different, it is treated as different spot data 360. Furthermore, the spot data 360 may include information on the corresponding ADK. There may be information on multiple corresponding ADKs.

[0050] The flight data 370 is information that uniquely identifies a route and a flight within the route. For example, the flight data 370 may include a flight ID that combines a route ID with an ID that identifies the flight to uniquely identify the flight, and operation date data 380. Also, as shown in FIG. 7 , in this embodiment, the flight data 370 is configured to be associated with one or more location data 360.

[0051] Specifically, for example, the flight data 370 may include a location ID included in one or more location data 360. The flight data 370 may also include information on the order in which the flight data 370 passes through each of the location data 360 and passage time data 390. The flight data 370 may also be associated with one vehicle data 340 instead of the bus schedule data 350, and may include the operation start time and operation end time of the flight data 370, as well as route information.

[0052] The operation day data 380 is information that specifies the days on which the flight data 370 operates. The operation days included in the operation day data 380 may be represented by a specific month and day, a date, or a day of the week. Alternatively, the operation day data 380 may be information that specifies days on which no operation occurs. Furthermore, when the operation days are represented by a day of the week or a date, the operation day data 380 may include data such as a flag that can determine whether the operation is repeated or a one-time operation.

[0053] The passage time data 390 is the time when the flight data 370 passes the location data 360. The passage time data 390 may be expressed in hours and minutes.

[0054] The operation start time and operation end time of the flight data 370, as well as the route information, are calculated or identified by the control unit 35 of the information processing device 30, and are stored in the memory unit 34 as information on the bus schedule data 350 or the flight data 370.

[0055] Specifically, the control unit 35 calculates the passage time data 390 of the spot data 360 that is passed first among the spot data 360 included in the flight data 370 as the operation start time, and calculates the passage time data 390 of the spot data 360 that is passed last among the spot data 360 included in the flight data 370 as the operation end time, and stores these in the memory unit 34. The control unit 35 also identifies route information of the flight data 370 by arranging the spot data 360 included in the flight data 370 in the order in which they are passed, and stores these in the memory unit 34.

[0056] (Details of the embodiment) Next, details of this embodiment will be described using an example of the DB 300 of the information processing device 30 shown in FIG.

[0057] As shown in FIG. 6 and described above, the one or more pieces of user data 320, one or more pieces of vehicle data 340, one or more pieces of bus schedule data 350, and one or more pieces of point data 360 on the route in each of the one or more pieces of bus schedule data 350 stored in the memory unit 34 of the information processing device 30 are configured to be stored in association with at least one area.

[0058] Therefore, when a user of the system 1 logs in to access the information processing device 30, the control unit 35 can identify one or more area data 330 managed by the user because the area data 330 is associated with the user data 320 corresponding to the user. The control unit 35 can then identify one or more bus schedule data 350 associated with each of the identified one or more area data 330. Therefore, the control unit 35 can display only the identified one or more bus schedule data 350 on the display of the output unit 32 or on the screen of an external device such as the display of the output unit 12 of the terminal device 10.

[0059] As described above, the information processing device 30 that manages operation plans for one or more autonomous vehicles includes a database configured to store one or more users, one or more autonomous vehicles, one or more bus schedules, and one or more points on the routes in each of the one or more bus schedules in association with information on at least one area.The information processing device 30 then displays, for each of the one or more users, the one or more bus schedules associated with information on the at least one area associated with the user on a built-in display or the screen of an external device.

[0060] According to this configuration, autonomous vehicles, users, schedules, and locations are managed in units called areas, rather than managing operations within a range that satisfies an operational design domain (ODD). This increases the likelihood of reducing mistakes, such as when a dispatcher in charge of a certain area erroneously assigns an autonomous vehicle that does not satisfy the ODD when assigning an autonomous vehicle to a scheduled trip that runs through that area. Furthermore, this configuration enables efficient operations, such as making changes to operation plans collectively by area. Therefore, this embodiment improves the technology of operational management systems that manage autonomous vehicle operations, in that it can accurately and efficiently manage the operation of autonomous vehicles.

[0061] Although the present disclosure has been described based on the drawings and examples, it should be noted that those skilled in the art may make various modifications and alterations based on the present disclosure. Therefore, it should be noted that these modifications and alterations are included in the scope of the present disclosure. For example, the functions included in each component or step can be rearranged so as not to be logically inconsistent, and multiple components or steps can be combined or divided into one.

[0062] For example, in the above-described embodiments, an embodiment is also possible in which the configuration and operation of the terminal device 10 and / or the information processing device 30 are distributed among multiple computers that can communicate with each other. Also, for example, an embodiment is also possible in which some or all of the components of the information processing device 30 are provided in the terminal device 10, and conversely, an embodiment is also possible in which some or all of the components of the terminal device 10 are provided in the information processing device 30. For example, the terminal device 10 may include some or all of the components of the information processing device 30, and the information processing device 30 may include some or all of the components of the terminal device 10.

[0063] Also, for example, in the above-described embodiment, the control unit 35 may control the first autonomous vehicle associated with the first bus schedule so that it cannot be associated with a second bus schedule that partially overlaps with the first bus schedule in terms of time period.

[0064] Specifically, consider the case where a user assigns vehicle data 340 (first operated vehicle) to certain bus schedule data 350 (second bus schedule) on a management screen provided by the information processing device 30. At this time, the control unit 35 checks whether the period from the operation start time to the operation end time included in the bus schedule data 350 acquired from the storage unit 34 overlaps with the period from the operation start time to the operation end time included in other bus schedule data 350 (first bus schedule) with which the vehicle data 340 is already associated. If there is no overlap, the control unit 35 associates the bus schedule data 350 with the vehicle data 340. If there is an overlap, the control unit 35 may output a message such as "This vehicle cannot be assigned because it has already been assigned to the 'first bus schedule'" on the management screen, thereby preventing the vehicle data 340 from being associated with the bus schedule data 350. Alternatively, the control unit 35 may output a message such as "This vehicle has already been assigned to the 'First bus schedule', so please change the vehicle on the 'First bus schedule'" on the management screen, and prompt the user to disassociate the vehicle data 340 that was associated with another bus schedule data 350, or may disassociate it.

[0065] Also, for example, in the above-described embodiment, the control unit 35 may limit the area data 330 with which the vehicle data 340 can be associated, or the bus schedule data 350 with which the autonomous vehicle can be associated, based on the ADK information of the vehicle data 340.

[0066] Specifically, consider the case where a user assigns vehicle data 340 to certain area data 330 or certain bus schedule data 350 on a management screen provided by the information processing device 30. At this time, the control unit 35 checks whether the corresponding ADK information included in the area data 330 includes the ADK information included in the vehicle data 340. Alternatively, the control unit 35 checks whether the corresponding ADK information included in each point data 360 on the route of the bus schedule data 350 includes all of the ADK information included in the vehicle data 340. If the ADK information is included, the control unit 35 associates the vehicle data 340 with the area data 330 or the bus schedule data 350. Furthermore, if the vehicle data 340 has already been assigned to another area data 330 or another bus schedule data 350, the control unit 35 may transmit information necessary for setting an ADK in response to a change in the area or bus schedule to the vehicle 20 corresponding to the vehicle data 340. If the ADK is not included, the control unit 35 may output a message such as "This vehicle cannot be assigned because its ADK does not correspond to this area" or "This vehicle cannot be assigned because its ADK does not correspond to this bus schedule" on the management screen, thereby preventing the vehicle data 340 from being associated with the area data 330 or the bus schedule data 350. Alternatively, the control unit 35 may output a message such as "This vehicle's ADK does not correspond to this area, so please change the settings related to the ADK of the vehicle" or "This vehicle's ADK does not correspond to this area, so please change the settings related to the ADK of the vehicle" on the management screen, thereby urging the user to change the settings of the ADK installed in the vehicle 20.

[0067] Also, for example, in the above-described embodiment, the vehicle data 340 may include information regarding the status of the vehicle 20 corresponding to the vehicle data 340, and the control unit 35 may limit the area data 330 with which each of the vehicle data 340 can be associated, or the bus schedule data 350 with which the vehicle data 340 can be associated, based on the information regarding the status.

[0068] Specifically, for example, consider a case where the vehicle data 340 includes information about the status of the vehicle 20, and a user assigns the vehicle data 340 to certain area data 330 or certain bus schedule data 350 on a management screen provided by the information processing device 30. At this time, the control unit 35 checks the information about the status of the vehicle 20 included in the vehicle data 340. Then, for example, if the status of the vehicle 20 is "out of order," the control unit 35 may output a message such as "This vehicle cannot be assigned because it is out of order" to the management screen, thereby preventing the vehicle data 340 from being associated with the area data 330 or the bus schedule data 350.

[0069] "Status information" includes the aforementioned vehicle 20 being "out of order," but may also include information about any vehicle 20, such as "in operation," "under maintenance," etc.

[0070] Also, for example, in the above-described embodiment, the bus schedule data 350 may include status information on the bus schedule route, and the control unit 35 may limit the bus schedule data 350 to which the vehicle data 340 can be associated based on the status information on the route.

[0071] Specifically, for example, consider a case where the bus schedule data 350 includes status information on the bus schedule route, and the user assigns vehicle data 340 to certain area data 330 or certain bus schedule data 350 on a management screen provided by the information processing device 30. At this time, the control unit 35 checks the status information on the bus schedule route included in the bus schedule data 350. Then, for example, if the status on the bus schedule route is "accident in progress," the control unit 35 may output a message such as "This route cannot be assigned because an accident has occurred" to the management screen, thereby preventing the vehicle data 340 from being associated with the bus schedule data 350.

[0072] The "status information on the route of the bus schedule" includes the aforementioned status of "accident occurring" on the route of the bus schedule, but may also include information on any status on the route of the bus schedule, such as "under construction," "bad weather," etc. The control unit 35 may acquire status information on the route of the bus schedule by periodically receiving status information on roads on the route of the bus schedule from a system that monitors road conditions, etc.

[0073] Also, for example, in the above-described embodiment, the control unit 35 may determine whether or not a flight is a special flight based on the operation date data 380 included in the flight data 370, and if the flight is a special flight, may display the fact that it is a special flight on the built-in display or the screen of an external device in a manner that makes it clear that it is a special flight.

[0074] Specifically, the control unit 35 checks a flag that can determine whether the service included in the operation date data 380 is a repeat service or a one-time service. If the service is a one-time service, the control unit 35 determines that the service corresponding to the service data 370 that is associated one-to-one with the bus schedule data 350 is a special service. Then, the control unit 35 displays this information on the display of the output unit 32 or on the screen of an external device such as the display of the output unit 12 of the terminal device 10 in a manner that makes it clear that the service is a special service.

[0075] The "manner in which it is clear that the flight is a special flight" can be any manner such as displaying special flights in a different color, or displaying the special flight as "special flight."

[0076] Furthermore, for example, in the above-described embodiment, the control unit 35 may restrict the association of the bus schedule data 350 with the area data 330 based on the information of the corresponding ADK included in the point data 360.

[0077] Specifically, consider the case where a user changes a certain area data 330 associated with certain bus schedule data 350 to another area data 330 on a management screen provided by the information processing device 30. At this time, the control unit 35 checks whether, for all point data 360 associated with the bus schedule data 350, any of the corresponding ADK information included in the point data 360 matches any of the corresponding ADK information included in the changed area data 330. If there is a match, the control unit 35 associates the bus schedule data 350 with the changed area data 330. If there is a mismatch, the control unit 35 may output a message such as "This bus schedule cannot be assigned because the ADK does not correspond to the changed area" to the management screen, thereby preventing the bus schedule data 350 from being associated with the changed area data 330.

[0078] Furthermore, for example, in the above-described embodiment, the control unit 35 may restrict the association of the point data 360 with the bus schedule data 350 based on the information of the corresponding ADK included in the point data 360.

[0079] Specifically, consider the case where a user changes a certain spot data 360 associated with certain bus schedule data 350 to another spot data 360 on the management screen provided by the information processing device 30. At this time, the control unit 35 checks whether any of the corresponding ADK information included in the other spot data 360 associated with the current bus schedule data 350 matches any of the corresponding ADK information included in the other spot data 360 associated with the changed spot data 360. The control unit 35 checks information about the status of the vehicle 20 included in the vehicle data 340. If there is a match, the control unit 35 associates the current bus schedule data 350 with the changed spot data 360. If there is a match, the control unit 35 may output a message such as "This spot cannot be assigned because the ADK does not correspond to the bus schedule" to the management screen, thereby preventing the bus schedule data 350 from being associated with the changed spot data 360.

[0080] Also, for example, an embodiment is possible in which a general-purpose computer functions as the information processing device 30 according to the above-described embodiment. Specifically, a program describing the processing content for realizing each function of the information processing device 30 according to the above-described embodiment is stored in the memory of the general-purpose computer, and the program is read and executed by a processor. Therefore, the present disclosure can also be realized as a program executable by a processor, or a non-transitory computer-readable medium storing the program.

[0081] Some embodiments of the present disclosure will be described below as examples, however, it should be noted that the embodiments of the present disclosure are not limited to these examples. [Appendix 1] An information processing device that manages operation plans for one or more autonomously driven vehicles, a storage unit including a database configured to store one or more users, the one or more automated driving vehicles, one or more bus schedules, and one or more points on routes in each of the one or more bus schedules in association with at least one area; a control unit that displays, for each of the one or more users, the one or more bus schedules associated with the at least one area associated with the user on a built-in display or a screen of an external device; An information processing device comprising: [Appendix 2] 10. The information processing device according to claim 1, Each of the one or more bus schedules is configured to be stored in one-to-one association with one flight. Information processing device. [Appendix 3] 10. The information processing device according to claim 2, The information about each of the one or more bus schedules includes a service start time and a service end time, The control unit performs control so that a first autonomous vehicle associated with a first bus schedule cannot be associated with a second bus schedule that partially overlaps with the first bus schedule in terms of time period. Information processing device. [Appendix 4] An information processing device according to any one of Supplementary Notes 1 to 3, The information about each of the one or more autonomous vehicles includes information about an autonomous driving development kit (ADK) installed in each of the one or more autonomous vehicles; the control unit limits areas to which each of the one or more autonomously driven vehicles can be associated or bus schedules to which each of the one or more autonomously driven vehicles can be associated, based on the information of the ADK; Information processing device. [Appendix 5] 5. The information processing device according to claim 4, when an area associated with the autonomously driven vehicle is changed, the control unit outputs a message on the built-in display or the screen of the external device prompting a change in settings related to the ADK of the autonomously driven vehicle. Information processing device. [Appendix 6] An information processing device according to any one of Supplementary Notes 1 to 5, the information about each of the one or more autonomous vehicles includes information about a state of each of the one or more autonomous vehicles; the control unit limits areas to which each of the one or more autonomous vehicles can be associated or bus schedules to which each of the one or more autonomous vehicles can be associated, based on the information about the state; Information processing device. [Appendix 7] An information processing device according to any one of Supplementary Notes 1 to 6, The information about each of the one or more bus schedules includes status information on the route of each of the one or more bus schedules, the control unit limits bus schedules that can be associated with each of the one or more autonomous vehicles based on the state information on the route. Information processing device. [Appendix 8] An information processing device according to any one of Supplementary Notes 2 to 7, The control unit determines whether the one flight is a special flight based on information about an operation date included in the information about the one flight, If the one flight is the special flight, display it on the built-in display or the screen of the external device in a manner that makes it clear that it is the special flight. Information processing device. [Appendix 9] An information processing device according to any one of Supplementary Notes 4 to 8, The information about each of the one or more locations includes information about an autonomous driving development kit (ADK) corresponding to each of the one or more locations; the control unit limits areas to which each of the one or more bus schedules can be associated based on the information of the ADK. Information processing device. [Appendix 10] An information processing device according to any one of Supplementary Notes 4 to 8, The information about each of the one or more locations includes information about an autonomous driving development kit (ADK) corresponding to each of the one or more locations; the control unit restricts the placement of each of the one or more points on a bus schedule route based on the information of the ADK; Information processing device. [Appendix 11] A method executed by an information processing device that manages operation plans for one or more autonomously driven vehicles, storing in a database one or more users, the one or more automated vehicles, one or more bus schedules, and one or more points on routes in each of the one or more bus schedules in association with at least one area; Displaying, for each of the one or more users, the one or more bus schedules associated with the at least one area associated with the user on a built-in display or a screen of an external device; A method comprising: [Appendix 12] 12. The method of claim 11, storing each of the one or more bus schedules in one-to-one association with one flight, wherein information on each of the one or more bus schedules includes a service start time and a service end time; Controlling a first autonomous vehicle associated with a first bus schedule so that the first autonomous vehicle cannot be associated with a second bus schedule that partially overlaps with the first bus schedule in terms of time period; The method further comprises: [Appendix 13] 13. The method according to claim 11 or 12, The information about each of the one or more autonomous vehicles includes information about an autonomous driving development kit (ADK) installed in each of the one or more autonomous vehicles; restricting areas to which each of the one or more autonomously driven vehicles can be associated or bus schedules to which each of the one or more autonomously driven vehicles can be associated based on the information of the ADK; The method further comprises: [Appendix 14] 14. The method of claim 13, When the area to which an autonomously driven vehicle is associated is changed, a message is output on the built-in display or the screen of the external device to prompt the user to change settings related to the ADK of the autonomously driven vehicle; The method further comprises: [Appendix 15] 15. The method of any one of appendices 11 to 14, comprising: the information about each of the one or more autonomous vehicles includes information about a state of each of the one or more autonomous vehicles; restricting an area with which each of the one or more automated vehicles may be associated or a bus schedule with which each of the one or more automated vehicles may be associated based on the information about the state; A method comprising: [Appendix 16] 16. The method of any one of appendices 11 to 15, comprising: The information about each of the one or more bus schedules includes status information on the route of each of the one or more bus schedules, restricting a schedule with which each of the one or more automated vehicles can be associated based on the on-route condition information; The method further comprises: [Appendix 17] 17. The method according to any one of claims 11 to 16, storing each of the one or more bus schedules in one-to-one association with one flight; Determining whether the one flight is a special flight based on information on the operation date included in the information on the one flight; If the one flight is the special flight, displaying it on the built-in display or the screen of the external device in a manner that makes it clear that it is the special flight; The method further comprises: [Appendix 18] 18. The method of any one of appendices 13 to 17, comprising: The information about each of the one or more locations includes information about an autonomous driving development kit (ADK) corresponding to each of the one or more locations; restricting areas to which each of the one or more bus schedules can be associated based on the information of the ADK; The method further comprises: [Appendix 19] 19. The method of any one of appendices 13 to 18, comprising: The information about each of the one or more locations includes information about an autonomous driving development kit (ADK) corresponding to each of the one or more locations; restricting the placement of each of the one or more points on a route of a bus schedule based on information of the ADK; The method further comprises: [Appendix 20] A system for managing a schedule of one or more autonomous vehicles, an information processing device and a terminal device; Equipped with the information processing device includes a database configured to store one or more users, the one or more autonomously driven vehicles, one or more bus schedules, and one or more points on routes in each of the one or more bus schedules in association with at least one area; the information processing device or the terminal device displays, for each of the one or more users, the one or more bus schedules associated with the at least one area associated with the user on a screen; system. [Explanation of symbols]

[0082] 1 System 10 Terminal Equipment 11 Communications Department 12 Output section 13 Input section 14 Storage section 15 Control Unit 16 Positioning unit 20 vehicles 21 Communications Department 22 Sensor section 23 Memory section 24 Control Unit 30 Information processing equipment 31 Communications Department 32 Output section 33 Input section 34 Storage section 35 Control Unit 40 Network 300 DB 310 Business Data 320 User Data 330 Area Data 340 Vehicle Data 350 Train schedule data 360 point data Flight 370 data 380 Operation Day Data 390 Passing Time Data

Claims

1. An information processing device that manages operation plans of one or more autonomously driven vehicles, a storage unit including a database configured to store one or more users, the one or more automated driving vehicles, one or more bus schedules, and one or more points on routes in each of the one or more bus schedules in association with at least one area; a control unit that displays, for each of the one or more users, the one or more bus schedules associated with the at least one area associated with the user on a built-in display or a screen of an external device; An information processing device comprising:

2. 2. The information processing device according to claim 1, Each of the one or more bus schedules is configured to be stored in one-to-one association with one flight. Information processing device.

3. 3. The information processing device according to claim 2, The information about each of the one or more bus schedules includes a service start time and a service end time, the control unit controls the first autonomous vehicle associated with the first bus schedule so that the first autonomous vehicle cannot be associated with a second bus schedule that partially overlaps with the first bus schedule in terms of time period. Information processing device.

4. 2. The information processing device according to claim 1, The information about each of the one or more autonomous vehicles includes information about an autonomous driving development kit (ADK) installed in each of the one or more autonomous vehicles; the control unit limits areas to which each of the one or more autonomously driven vehicles can be associated or bus schedules to which each of the one or more autonomously driven vehicles can be associated, based on the information of the ADK. Information processing device.

5. 5. The information processing device according to claim 4, When an area associated with an autonomously driven vehicle is changed, the control unit outputs a message on the built-in display or the screen of the external device to prompt a change in settings related to the ADK of the autonomously driven vehicle. Information processing device.

6. 2. The information processing device according to claim 1, the information about each of the one or more autonomous vehicles includes information about a state of each of the one or more autonomous vehicles; the control unit limits areas to which each of the one or more autonomous vehicles can be associated or bus schedules to which each of the one or more autonomous vehicles can be associated, based on the information about the state. Information processing device.

7. 2. The information processing device according to claim 1, The information about each of the one or more bus schedules includes status information on the route of each of the one or more bus schedules, the control unit limits a bus schedule that can be associated with each of the one or more autonomously driven vehicles based on the state information on the route. Information processing device.

8. 3. The information processing device according to claim 2, The control unit determines whether the one flight is a special flight based on information about an operation date included in the information about the one flight, If the one flight is the special flight, displaying the special flight on the built-in display or the screen of the external device in a manner that makes it clear that the flight is the special flight. Information processing device.

9. 5. The information processing device according to claim 4, The information about each of the one or more locations includes information about an autonomous driving development kit (ADK) corresponding to each of the one or more locations; the control unit limits areas to which each of the one or more bus schedules can be associated based on the information of the ADK. Information processing device.

10. 5. The information processing device according to claim 4, The information about each of the one or more locations includes information about an autonomous driving development kit (ADK) corresponding to each of the one or more locations; the control unit restricts placement of each of the one or more points on a route of a bus schedule based on information of the ADK. Information processing device.

11. A method executed by an information processing device that manages operation plans for one or more autonomously driven vehicles, storing in a database one or more users, the one or more automated vehicles, one or more bus schedules, and one or more points on routes in each of the one or more bus schedules in association with at least one area; Displaying, for each of the one or more users, the one or more bus schedules associated with the at least one area associated with the user on a built-in display or a screen of an external device; A method comprising:

12. 12. The method of claim 11, storing each of the one or more bus schedules in one-to-one association with one flight, wherein information on each of the one or more bus schedules includes a service start time and a service end time; Controlling a first autonomous vehicle associated with a first bus schedule so that the first autonomous vehicle cannot be associated with a second bus schedule that partially overlaps with the first bus schedule in terms of time period; The method further comprises:

13. 12. The method of claim 11, The information about each of the one or more autonomous vehicles includes information about an autonomous driving development kit (ADK) installed in each of the one or more autonomous vehicles; restricting areas to which each of the one or more autonomously driven vehicles can be associated or bus schedules to which each of the one or more autonomously driven vehicles can be associated based on information about the ADK; The method further comprises:

14. 14. The method of claim 13, When the area to which the autonomously driven vehicle is associated is changed, a message prompting a user to change settings related to the ADK of the autonomously driven vehicle is output on the built-in display or the screen of the external device; The method further comprises:

15. 12. The method of claim 11, the information about each of the one or more autonomous vehicles includes information about a state of each of the one or more autonomous vehicles; restricting areas with which each of the one or more automated vehicles may be associated or bus schedules with which each of the one or more automated vehicles may be associated based on the information about the state; A method comprising:

16. 12. The method of claim 11, The information about each of the one or more bus schedules includes status information on the route of each of the one or more bus schedules, restricting a schedule with which each of the one or more automated vehicles can be associated based on the on-route condition information; The method further comprises:

17. 12. The method of claim 11, storing each of the one or more bus schedules in one-to-one association with one flight; Determining whether the one flight is a special flight based on information on the operation date included in the information on the one flight; If the one flight is the special flight, displaying it on the built-in display or the screen of the external device in a manner that makes it clear that it is the special flight; The method further comprises:

18. 14. The method of claim 13, The information about each of the one or more locations includes information about an autonomous driving development kit (ADK) corresponding to each of the one or more locations; limiting areas to which each of the one or more bus schedules can be associated based on the information of the ADK; The method further comprises:

19. 14. The method of claim 13, The information about each of the one or more locations includes information about an autonomous driving development kit (ADK) corresponding to each of the one or more locations; restricting placement of each of the one or more points on a route of a bus schedule based on information of the ADK; The method further comprises:

20. A system for managing a schedule of one or more autonomous vehicles, an information processing device and a terminal device; Equipped with the information processing device includes a database configured to store one or more users, the one or more autonomous vehicles, one or more bus schedules, and one or more points on routes in each of the one or more bus schedules in association with at least one area; the information processing device or the terminal device displays, for each of the one or more users, the one or more bus schedules associated with the at least one area associated with the user on a screen; system.

Images