In-vehicle device, management device, resource determination program, and resource management program

Abstract

This will facilitate and reduce the cost of upgrading vehicle functions. [Solution] The in-vehicle device includes an acquisition unit that acquires resource information relating to resources outside the vehicle, a decision unit that performs a decision process to determine the resources to be used to perform services relating to the vehicle based on the resource information acquired by the acquisition unit, and a transmission unit that transmits the request for the resources determined by the decision unit to an external device outside the vehicle.

Description

Technical Field

[0001] The present disclosure relates to an in-vehicle device, a management device, a resource determination program, and a resource management program.

Background Art

[0002] In a server that operates multiple applications, technologies for improving the utilization efficiency of resources have been developed. For example, Patent Document 1 (Japanese Patent Application Laid-Open No. 2018-190355) discloses the following technology. That is, the resource management method is a resource management method executed in a resource management device that manages the amount of resource allocation for multiple applications operating on a server, and includes a receiving step of receiving the importance of each application, a grouping step of grouping the applications into two or more groups according to the received importance, a resource allocation step of preferentially allocating resources from the group of applications with high importance, a monitoring step of monitoring the resource usage amount of each application in the group, and a resource reallocation step of allocating at least a part of the resource allocation amount of the group having surplus resources to the group in which the resource utilization rate, which is the resource usage amount with respect to the allocated resource amount, has reached a predetermined value or more when the resource utilization rate has reached a predetermined value or more in any of the groups as a result of the monitoring.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Patent Document 2

Patent Document 3

Summary of the Invention

Problems to be Solved by the Invention

[0004] To upgrade vehicle functionality, it is sometimes necessary to update the hardware and other configurations within the vehicle. In recent years, with the increasing sophistication and diversification of vehicle functions, the frequency of such updates is expected to increase. Therefore, there is a need to simplify and reduce the cost of these functional upgrades.

[0005] This disclosure was made to solve the aforementioned problems, and its purpose is to provide an in-vehicle device, a management device, a resource determination program, and a resource management program that can facilitate and reduce the cost of upgrading the functions of a vehicle. [Means for solving the problem]

[0006] The in-vehicle device of this disclosure includes an acquisition unit that acquires resource information relating to resources outside the vehicle, a determination unit that performs a determination process to determine the resources to be used to perform services relating to the vehicle based on the resource information acquired by the acquisition unit, and a transmission unit that transmits a request for the resources determined by the determination unit to an external device outside the vehicle.

[0007] One aspect of this disclosure can be implemented not only as an in-vehicle device equipped with such characteristic processing, but also as a step-based method for such characteristic processing, or as a semiconductor integrated circuit that implements part or all of the in-vehicle device. Furthermore, one aspect of this disclosure can be implemented as a system including the in-vehicle device.

[0008] One aspect of this disclosure can be implemented not only as a management device equipped with such characteristic processing, but also as a step-based method for such characteristic processing, or as a semiconductor integrated circuit that implements part or all of the management device. Furthermore, one aspect of this disclosure can be implemented as a system including the management device. [Effects of the Invention]

[0009] According to this disclosure, it is possible to make vehicle function upgrades easier and less expensive. [Brief explanation of the drawing]

[0010] [Figure 1] Figure 1 is a diagram showing an example of the configuration of a communication system according to an embodiment of the present disclosure. [Figure 2] Figure 2 shows an example of the configuration of an in-vehicle system according to an embodiment of the present disclosure. [Figure 3] Figure 3 shows an example of the configuration of an in-vehicle relay device according to an embodiment of the present disclosure. [Figure 4] Figure 4 shows an example of the configuration of a resource management server according to an embodiment of the present disclosure. [Figure 5] Figure 5 shows an example of the configuration of an edge server according to an embodiment of the present disclosure. [Figure 6] Figure 6 is a diagram illustrating an example of a service performed by an edge server in a communication system according to an embodiment of the present disclosure. [Figure 7] Figure 7 shows an example of resource allocation by an in-vehicle relay device according to an embodiment of the present disclosure. [Figure 8] Figure 8 shows an example of resource reallocation by an in-vehicle relay device according to an embodiment of the present disclosure. [Figure 9] Figure 9 shows another example of resource reallocation by an in-vehicle relay device according to an embodiment of the present disclosure. [Figure 10] Figure 10 shows another example of resource reallocation by an in-vehicle relay device according to an embodiment of the present disclosure. [Figure 11] Figure 11 is a flowchart illustrating an example of the operation procedure when a resource management server according to the embodiment of this disclosure performs distribution processing. [Figure 12] Figure 12 is a flowchart illustrating an example of the operation procedure when a resource management server according to the embodiment of this disclosure allocates resources. [Figure 13]FIG. 13 is a flowchart defining an example of an operation procedure when a resource management server according to an embodiment of the present disclosure performs resource allocation. [Figure 14] FIG. 14 is a flowchart defining an example of an operation procedure when an edge server according to an embodiment of the present disclosure executes a service. [Figure 15] FIG. 15 is a flowchart defining an example of an operation procedure when an edge server according to an embodiment of the present disclosure performs a process of stopping the execution of a service. [Figure 16] FIG. 16 is a flowchart defining an example of an operation procedure when an in-vehicle relay device according to an embodiment of the present disclosure performs a determination process. [Figure 17] FIG. 17 is a flowchart defining an example of an operation procedure when an in-vehicle relay device according to an embodiment of the present disclosure performs a determination process. [Figure 18] FIG. 18 is a diagram showing a configuration of a modification example of a resource management server according to an embodiment of the present disclosure. [Figure 19] FIG. 19 is a diagram showing a configuration of a modification example of an in-vehicle relay device according to an embodiment of the present disclosure. [Figure 20] FIG. 20 is a flowchart defining an example of an operation procedure when a modification example of a resource management server according to an embodiment of the present disclosure performs resource allocation. [Figure 21] FIG. 21 is a flowchart defining an example of an operation procedure when a modification example of a resource management server according to an embodiment of the present disclosure performs resource allocation.

MODE FOR CARRYING OUT THE INVENTION

[0011] First, the content of the embodiment of the present disclosure will be listed and described. (1) An in-vehicle device according to an embodiment of the present disclosure includes: an acquisition unit that acquires resource information relating to resources outside the vehicle; a decision unit that performs a decision process to determine the resources to be used for performing services relating to the vehicle based on the resource information acquired by the acquisition unit; and a transmission unit that transmits a request for the resources determined by the decision unit to an external device outside the vehicle.

[0012] This configuration allows for the use of external resources to perform vehicle-related services, enabling the upgrade of service delivery capabilities without requiring any changes to the vehicle's configuration. Therefore, it facilitates and reduces the cost of upgrading vehicle functionality.

[0013] (2) In (1) above, the acquisition unit may further acquire route information indicating the planned route of the vehicle, and the determination unit may further perform the determination process based on the route information acquired by the acquisition unit.

[0014] This configuration allows for the determination of appropriate resources based on the vehicle's planned route.

[0015] (3) In (2) above, the decision unit may determine a plurality of resources to be used in order based on the resource information and the route information.

[0016] With this configuration, when a vehicle travels along its planned route, services can be continuously provided by, for example, multiple resources located in different locations.

[0017] (4) In (2) or (3) above, the decision unit may decide on a plurality of resources in the decision process, the decision unit may decide on the usage period of each resource to be used based on the route information, and the transmission unit may transmit to the external device information indicating the usage period of each resource determined by the decision unit.

[0018] This configuration allows for the determination of the appropriate usage period for each resource according to the planned route of the vehicles, thereby enabling efficient use of resources between vehicles.

[0019] (5) In any of (1) to (4) above, the resource information may include at least one of the following: information indicating the types of services that can be performed, information indicating the areas in which the services are provided, and information indicating the performance of the device that performs the services.

[0020] This configuration allows for the determination of appropriate resources based on the types of services that can be performed, the areas where the services are provided, or the performance of the equipment running the services.

[0021] (6) The management device according to the embodiment of the present disclosure is a management device installed outside a vehicle and includes a resource allocation unit that allocates resources located outside the vehicle for use in performing services related to the vehicle.

[0022] This configuration allows for the use of external resources to perform vehicle-related services, enabling the upgrade of service delivery capabilities without requiring any changes to the vehicle's configuration. Therefore, it facilitates and reduces the cost of upgrading vehicle functionality.

[0023] (7) In the above (6), the vehicle may determine the resources to be used to perform the service and send a resource request to the management device to request the determined resources, the management device may further include a receiving unit to receive the resource request from the vehicle, and the resource allocation unit may perform the allocation based on the resource request received by the receiving unit.

[0024] This configuration allows for a more accurate understanding of the resources that should be allocated to the vehicles, thereby enabling the more reliable execution of services corresponding to those resources.

[0025] (8) In (6) or (7) above, the resource allocation unit may determine the allocation according to the area in which the multiple services corresponding to the multiple resources are provided.

[0026] This configuration allows for the appropriate allocation of resources depending on the area where the service is provided.

[0027] (9) In the above (7), if the receiving unit receives a new resource request from another vehicle, the resource allocation unit may reallocate the resources based on the planned route of the other vehicle.

[0028] With this configuration, if a resource request is received from another vehicle after resources have been allocated to one vehicle, appropriate resources can be newly allocated to each vehicle according to the planned route of the other vehicle.

[0029] (10) In the above (7), if the resource allocation unit is short of resources and the receiving unit receives a new resource request from another vehicle, it may reallocate the resources according to priority.

[0030] With this configuration, if resource requests are received from other vehicles in a situation where resources are insufficient, the resource allocation to each vehicle can be reviewed according to priority.

[0031] (11) In (10) above, the priority may be determined according to the type of vehicle.

[0032] This configuration allows resources to be preferentially allocated to high-priority vehicle types, such as emergency vehicles.

[0033] (12) In (10) or (11) above, the priority may be determined according to the type of service provided to the vehicle.

[0034] This configuration allows resources to be preferentially allocated to vehicles that provide high-priority services.

[0035] (13) In any of the above (10) to (12), the priority may be determined according to the load conditions of the vehicle.

[0036] This configuration allows for more reliable service execution by prioritizing resource allocation to vehicles when they are under heavy load.

[0037] (14) In the above (6), the management device may further include a decision unit that performs a decision process to determine the resources to be used to execute the service, and the resource allocation unit may perform the allocation of the resources determined by the decision unit.

[0038] This configuration allows for a more accurate understanding of the resources that should be allocated to the vehicle, thereby enabling more reliable execution of services corresponding to those resources. Furthermore, since the vehicle does not need to perform the processing required to determine the resources, the processing load on the vehicle can be reduced.

[0039] (15) In the above (14), the decision unit may determine a plurality of resources in the decision process, and the decision unit may determine the usage period of each resource based on the planned route of the vehicle.

[0040] This configuration allows for the determination of appropriate usage periods for each resource according to the vehicle's planned route, enabling efficient resource utilization between vehicles. Furthermore, since the vehicle does not need to perform processing to determine resource usage periods, the processing load on the vehicle can be reduced.

[0041] (16) The resource determination program according to the embodiment of the present disclosure is a resource determination program used in an in-vehicle device, which causes a computer to function as an acquisition unit that acquires resource information relating to resources outside the vehicle, a determination unit that performs a determination process to determine the resources to be used for performing services relating to the vehicle based on the resource information acquired by the acquisition unit, and a transmission unit that transmits the resource request determined by the determination unit to an external device outside the vehicle.

[0042] This configuration allows for the use of external resources to perform vehicle-related services, enabling the upgrade of service delivery capabilities without requiring any changes to the vehicle's configuration. Therefore, it facilitates and reduces the cost of upgrading vehicle functionality.

[0043] (17) The resource management program according to the embodiment of the present disclosure is a resource management program used in a management device provided outside a vehicle, and is a program that causes a computer to function as a resource allocation unit that allocates resources located outside the vehicle, which are used to perform services related to the vehicle.

[0044] This configuration allows for the use of external resources to perform vehicle-related services, enabling the upgrade of service delivery capabilities without requiring any changes to the vehicle's configuration. Therefore, it facilitates and reduces the cost of upgrading vehicle functionality.

[0045] Embodiments of this disclosure will be described below with reference to the drawings. In the drawings, the same or corresponding parts are denoted by the same reference numerals, and their descriptions will not be repeated. Furthermore, at least some of the embodiments described below may be combined in any way.

[0046] [Communication System] Figure 1 is a diagram showing an example of the configuration of a communication system according to an embodiment of the present disclosure. Referring to Figure 1, the communication system 501 comprises a resource management server 170, a plurality of edge servers 180, and one or more in-vehicle systems 301. The in-vehicle system 301 is mounted on a vehicle 1. The resource management server 170 and the edge servers 180 are located outside the vehicle 1. The resource management server 170 is an example of an external device and an example of a management device.

[0047] The resource management server 170 and edge server 180 are used, for example, by a business operator or individual who manages the operation of vehicle 1. The resource management server 170 and edge server 180 send and receive information via the external network 151.

[0048] Each edge server 180 executes services S related to vehicle 1. Specifically, the edge server 180 executes services S such as autonomous driving services, obstacle avoidance services, and door unlocking services related to the autonomous driving of vehicle 1.

[0049] In this embodiment, for example, the autonomous driving services performed by the edge server 180 are the LKAS (Lane Keeping Assist System) service and the ACC (Adaptive Cruise Control) service. The LKAS service is a service to prevent vehicle 1 from deviating from the driving lane in which it is traveling. The ACC service is a service to ensure that the distance between vehicle 1 and other vehicles located in front of it (hereinafter also referred to as "vehicles ahead") is above a certain value.

[0050] The obstacle avoidance service is a service that avoids obstacles while vehicle 1 is in motion. The door unlocking service is a service that unlocks the doors of vehicle 1 while it is parked or stopped.

[0051] Figure 2 shows an example of the configuration of an in-vehicle system according to an embodiment of the present disclosure. Referring to Figure 2, the in-vehicle system 301 comprises an in-vehicle relay device 101 and a plurality of in-vehicle devices 202. The in-vehicle relay device 101 is an example of an in-vehicle device.

[0052] In-vehicle equipment 202 includes in-vehicle ECUs (Electronic Control Units), sensors, actuators, navigation systems, human-machine interfaces, and cameras. In-vehicle ECUs include TCUs (Telematics Communication Units), engine ECUs, autonomous driving ECUs, steering ECUs, brake ECUs, and door lock ECUs.

[0053] The in-vehicle relay device 101 and the multiple in-vehicle devices 202 constitute an in-vehicle network 401. The multiple in-vehicle devices 202 are connected to the in-vehicle relay device 101, for example, via a CAN bus 51 that conforms to the CAN (Controller Area Network) standard.

[0054] In the example shown in Figure 2, the in-vehicle system 301 includes in-vehicle equipment 202, which consists of in-vehicle equipment 202A, 202B, 202C, and 202D. In addition, in the example shown in Figure 2, CAN buses 51A and 51B are provided as CAN bus 51.

[0055] In-vehicle devices 202A and 202B are connected to the in-vehicle relay device 101 via CAN bus 51A. In-vehicle devices 202C and 202D are connected to the in-vehicle relay device 101 via CAN bus 51B.

[0056] The in-vehicle relay device 101 is, for example, a gateway device. The in-vehicle relay device 101 performs relay processing to relay data transmitted and received between the in-vehicle devices 202.

[0057] For example, each in-vehicle device 202 transmits a CAN frame containing various information, such as information to assist the automated driving performed by the vehicle 1 and information used for entertainment (described later), and a CAN-ID (Identifier) ​​indicating the type of data, to another in-vehicle device 202 or an in-vehicle relay device 101. The in-vehicle relay device 101 relays a CAN frame received from one in-vehicle device 202 to another in-vehicle device 202. The in-vehicle relay device 101 also creates a CAN frame containing the above-mentioned various information and CAN-ID, and transmits the created CAN frame to the destination in-vehicle device 202.

[0058] Furthermore, the in-vehicle system 301 is not limited to a configuration in which two CAN buses 51 are provided; it may also be configured to have one or three or more CAN buses 51.

[0059] Furthermore, the in-vehicle relay device 101 and the in-vehicle equipment 202 may be configured to perform communication in accordance with communication protocols such as CAN FD (CAN with Flexible Data Rate), Ethernet (registered trademark), FlexRay (registered trademark), MOST (Media Oriented System Transport) (registered trademark), LIN (Local Interconnect Network), and CXPI (Clock Extension Peripheral Interface) (registered trademark), in addition to or instead of communication in accordance with the CAN standard.

[0060] In the example shown in Figure 2, in-vehicle equipment 202A, in-vehicle equipment 202B, and in-vehicle equipment 202C are TCU, vehicle speed sensor, and navigation device, respectively. Hereinafter, in-vehicle equipment 202A, in-vehicle equipment 202B, and in-vehicle equipment 202C will also be referred to as TCU202A, vehicle speed sensor 202B, and navigation device 202C, respectively.

[0061] Referring to Figures 1 and 2, the TCU202A communicates with the resource management server 170 and the edge server 180, for example, via the wireless base station device 161.

[0062] More specifically, the TCU202A communicates wirelessly with the wireless base station equipment 161 in accordance with communication standards such as LTE (Long Term Evolution) (registered trademark) or 5G.

[0063] Specifically, when the TCU202A receives a CAN frame containing various information from the in-vehicle relay device 101, it transmits a radio signal containing the said information to the radio base station device 161.

[0064] When the wireless base station device 161 receives a wireless signal from the TCU 202A, it transmits various information contained in the received wireless signal to the resource management server 170 via an external network 151 such as the Internet.

[0065] Furthermore, when the wireless base station device 161 receives an IP packet from the resource management server 170 or edge server 180 via the external network 151, it includes the received IP packet in the wireless signal and transmits it to the TCU 202A.

[0066] When the TCU202A receives a radio signal containing IP packets from the resource management server 170 or edge server 180 via the radio base station device 161, it retrieves the IP packets from the received radio signal, stores the retrieved IP packets in one or more CAN frames, and transmits them to the in-vehicle relay device 101.

[0067] The vehicle speed sensor 202B measures the vehicle speed of vehicle 1, for example, periodically or irregularly, and transmits the vehicle speed information indicating the measurement result to the on-board relay device 101.

[0068] The navigation device 202C transmits location information indicating the location of vehicle 1 to the in-vehicle relay device 101, for example, periodically or irregularly.

[0069] [Vehicle-mounted relay device] Figure 3 shows an example of the configuration of an in-vehicle relay device according to an embodiment of the present disclosure. Referring to Figure 3, the in-vehicle relay device 101 comprises a relay unit 11, a processing unit 12, and a storage unit 13. The processing unit 12 includes a service management unit 21, a determination unit 22, and a control unit 23. One or both of the relay unit 11 and the processing unit 12 are implemented by a processing circuit including, for example, one or more processors. The storage unit 13 is, for example, a non-volatile memory included in the processing circuit. The service management unit 21 is an example of an acquisition unit. The relay unit 11 is an example of a transmission unit.

[0070] (Relay section) The relay unit 11 receives a CAN frame transmitted from a certain in-vehicle device 202. The relay unit 11 then checks whether the received CAN frame is a CAN frame that its own in-vehicle relay device 101 should receive.

[0071] The storage unit 13 stores, for example, a reception list L indicating the CAN-IDs included in the CAN frames that its in-vehicle relay device 101 should receive. The reception list L is registered in the storage unit 13 by the manufacturer of the vehicle 1 when the vehicle 1 is shipped.

[0072] When the relay unit 11 receives a CAN frame, it checks whether the CAN-ID contained in the CAN frame is registered in the reception list L by referring to the reception list L in the storage unit 13.

[0073] The relay unit 11 discards a CAN frame if the CAN-ID contained in the received CAN frame is not registered in the reception list L.

[0074] On the other hand, the relay unit 11 performs relay processing if the CAN-ID included in the received CAN frame is registered in the reception list L and the destination of the CAN frame is the in-vehicle equipment 202. Also, if the relay unit 11 outputs the CAN frame to the processing unit 12 if the CAN-ID included in the received CAN frame is registered in the reception list L and the destination of the CAN frame is its own in-vehicle relay device 101.

[0075] More specifically, for example, the storage unit 13 stores a routing table that shows the correspondence between CAN-IDs, the devices to which CAN frames are transmitted, and the CAN bus 51 (hereinafter also referred to as the "destination bus") to which the destination devices are connected. The routing table is registered in the storage unit 13 by the manufacturer of vehicle 1 when vehicle 1 is shipped, for example.

[0076] For example, if the relay unit 11 has a CAN-ID included in a CAN frame received from the in-vehicle device 202 registered in the reception list L, it refers to the routing table in the storage unit 13 to confirm the destination device corresponding to that CAN-ID.

[0077] When the relay unit 11 confirms that the destination device of the received CAN frame is the in-vehicle device 202, it refers to the routing table to identify the destination bus corresponding to that destination device. The relay unit 11 then outputs the received CAN frame to the identified destination bus.

[0078] Meanwhile, when the relay unit 11 confirms that the destination device of the received CAN frame is its own in-vehicle relay device 101, it outputs various information contained in the CAN frame to the processing unit 12.

[0079] [Resource Management Server] Figure 4 shows an example of the configuration of a resource management server according to an embodiment of the present disclosure. Referring to Figure 4, the resource management server 170 comprises a communication unit 31, a distribution unit 32, a resource allocation unit 33, a resource release unit 34, and a storage unit 35. Some or all of the communication unit 31, distribution unit 32, resource allocation unit 33, and resource release unit 34 are implemented by a processing circuit including, for example, one or more processors. The storage unit 35 is, for example, a non-volatile memory included in the processing circuit. The communication unit 31 is an example of a transmission unit.

[0080] Referring to Figures 1 and 4, the communication unit 31 communicates with the TCU 202A by, for example, sending and receiving various information via the external network 151 and the wireless base station equipment 161.

[0081] (Distribution of resource information) The distribution unit 32 performs distribution processing to distribute resource information regarding resource R located outside of vehicle 1 to each vehicle 1 via the communication unit 31.

[0082] For example, resource information includes type information indicating the type of service S that each edge server 180 can perform, service area information indicating the area in which service S is provided by each edge server 180 (hereinafter also referred to as "service area A"), and performance information indicating the performance of each edge server 180.

[0083] Specifically, for example, performance information includes the processing speed and storage capacity of the edge server 180, which are shown as the performance of the edge server 180.

[0084] The processing speed of the edge server 180 is, for example, the processing speed of the CPU (Central Processing Unit) or MPU (Micro Processing Unit) in that edge server 180. Specifically, the processing speed of the edge server 180 is expressed as a numerical value with units such as MIPS (Million Instructions Per Second) or FLOPS (FLoating-point Operations Per Second).

[0085] The storage capacity of the edge server 180 is, for example, the amount of data that the edge server 180 can provide, and is the capacity of the edge server 180's storage, such as RAM (Random Access Memory), ROM (Read Only Memory), or HDD (Hard Disk Drive). Specifically, the storage capacity of the edge server 180 is indicated by a numerical value with units such as bytes.

[0086] For example, the storage unit 35 stores type information and service area information. The distribution unit 32 performs distribution processing, for example, periodically.

[0087] For example, the shape of the service area A for each edge server 180 indicated in the service area information is circular. In this case, the shape of the service area A is represented by the coordinates of the center point of the service area A and its diameter. Note that the shape of the service area A is not limited to a circle; it may also be polygonal. In this case, the shape of the service area A is represented by the coordinates of multiple vertices of the service area A.

[0088] For example, when the processing timing T for distribution processing arrives, the distribution unit 32 acquires type information and provision area information from the storage unit 35. Also, when the processing timing T arrives, the distribution unit 32 sends an information request notification N1 to each edge server 180 via the communication unit 31, indicating that it requests the transmission of performance information.

[0089] When each edge server 180 receives an information request notification N1 from the resource management server 170, it sends its latest performance information to the resource management server 170 as a response to the information request notification N1.

[0090] In the resource management server 170, when the distribution unit 32 receives performance information from each edge server 180 via the communication unit 31, it creates resource information that includes the received performance information and type information and provision area information obtained from the storage unit 35. The distribution unit 32 then outputs the created resource information to the communication unit 31.

[0091] When the communication unit 31 receives resource information from the distribution unit 32, it creates an IP packet P1 for each vehicle 1 that contains the resource information, and includes the IP address of the resource management server 170 and the IP address of the vehicle 1 as the source IP address and destination IP address, respectively. The communication unit 31 then transmits the created IP packet P1 to the TCU 202A in each vehicle 1.

[0092] Referring again to Figure 2, when the TCU202A in vehicle 1 receives an IP packet P1 from the resource management server 170, it transmits the resource information contained in the received IP packet P1 to the in-vehicle relay device 101.

[0093] [Vehicle-mounted relay device] (Service Management Department) Referring again to Figures 2 and 3, in the in-vehicle relay device 101, for example, the service management unit 21 acquires resource information and route information indicating the planned route E of vehicle 1.

[0094] More specifically, when the relay unit 11 receives resource information from the TCU 202A, it outputs the received resource information to the service management unit 21.

[0095] When the service management unit 21 receives resource information from the relay unit 11, it sends a reception notification to the navigation device 202C via the relay unit 11 indicating that the relay unit 11 has received the resource information.

[0096] For example, when the navigation device 202C receives a notification from the in-vehicle relay device 101, it displays a screen B1 on its own display unit prompting the user to input whether or not they wish to receive service S from the edge server 180.

[0097] When the navigation device 202C receives input indicating a desire to receive service S, it displays screen B2 on its display unit prompting the user to input the type of service S they wish to receive and the desired service period. The desired service period may or may not include the current time.

[0098] When the navigation device 202C receives input regarding the type of service S to be provided and the desired service period, it creates route information.

[0099] Specifically, for example, when the navigation device 202C receives input for the type of service S that the user wishes to receive, it displays screen B3 on its display unit prompting the user to input the departure and destination of vehicle 1, as well as the planned departure time.

[0100] When the navigation device 202C receives input of the departure point and destination of vehicle 1, as well as the scheduled departure time ta, it creates route information that indicates the planned route E from the departure point to the destination, one or more waypoints along the planned route E, the scheduled departure time, the time of passing through each waypoint, and the scheduled arrival time which is the time of arrival at the destination, as well as route information that indicates the type of service S and the desired period of provision that was received as input.

[0101] The navigation device 202C then transmits the created route information to the in-vehicle relay device 101.

[0102] On the other hand, when the navigation device 202C receives input indicating that it does not wish to receive service S, it sends a notification to the in-vehicle relay device 101 indicating that it does not wish to receive service S.

[0103] In the in-vehicle relay device 101, when the relay unit 11 receives route information or a notification that does not need to be provided from the navigation device 202C, it outputs the received route information or notification that does not need to be provided to the service management unit 21.

[0104] Furthermore, the in-vehicle relay device 101 is not limited to a configuration that transmits reception notifications to the navigation device 202C, but may also be configured to store the latest resource information in the storage unit 13 each time it receives resource information from the resource management server 170. In this case, for example, the in-vehicle relay device 101 confirms, via the navigation device 202C, whether or not the vehicle 1 wishes to receive service S when the vehicle 1 departs, or when a passenger in the vehicle 1 inputs a destination or the like into the navigation device 202C.

[0105] (Decision-making process) When the service management unit 21 receives routing information from the relay unit 11, it performs a decision process to determine whether or not to send a resource request to the resource management server 170 to request resource R.

[0106] More specifically, for example, the service management unit 21 checks whether the type of service S indicated by the route information received from the relay unit 11 is included in the type information received from the resource management server 170 via the relay unit 11.

[0107] Furthermore, for example, the determination unit 22 checks whether each piece of performance information included in the resource information received from the relay unit 11 satisfies a predetermined condition J. For example, the predetermined condition J is that the processing speed of the edge server 180 indicated by the performance information is greater than threshold Th1, and the storage capacity of the edge server 180 indicated by the performance information is greater than threshold Th2. For example, thresholds Th1 and Th2 are set to values ​​corresponding to the type of service S performed by the edge server 180.

[0108] The service management unit 21 determines that if the type of service S indicated by the routing information is included in the type information and each performance information satisfies the predetermined condition J, it will send a resource request to the resource management server 170.

[0109] The service management unit 21 then outputs the resource information and route information received from the relay unit 11 to the determination unit 22.

[0110] On the other hand, the service management unit 21 determines that it will not send a resource request to the resource management server 170 if the type of service S indicated by the route information is not included in the type information, or if at least one of the multiple performance information items does not satisfy the predetermined condition J.

[0111] Furthermore, if the service management unit 21 receives a notification from the relay unit 11 that service is not to be provided, it will not perform any decision-making processing.

[0112] (Decision process) For example, the decision unit 22 performs a decision process to determine the resources R to be used to execute the service S, based on the resource information and route information obtained by the service management unit 21.

[0113] More specifically, for example, the decision unit 22 determines a plurality of resources R to be used in sequence based on resource information and route information obtained by the service management unit 21.

[0114] Specifically, when the decision unit 22 receives resource information and route information from the service management unit 21, it uses the desired service period, planned route E, planned departure time, and planned arrival time indicated by the route information to calculate the travel section Q of vehicle 1 during the desired service period.

[0115] Then, the decision unit 22 performs a decision process using the service area information included in the resource information received from the service management unit 21 and the calculated travel section Q.

[0116] Specifically, the decision unit 22 selects an edge server 180 corresponding to a service provision area A that overlaps with the travel section Q as the resource R to be used to execute service S.

[0117] In this embodiment, it is assumed that there are multiple service provision areas A that overlap with the travel section Q. That is, the decision unit 22 selects multiple edge servers 180 corresponding to each of the multiple service provision areas A that overlap with the travel section Q as multiple resources R to be used to execute the service S.

[0118] The decision unit 22 then determines the order in which the selected multiple resources R will be used. Specifically, for example, the decision unit 22 determines the order in which the vehicle 1 will pass through the selected multiple service areas A during the desired service period as the order in which the multiple resources R will be used.

[0119] Furthermore, for example, the decision unit 22 determines the usage period U for each resource R to be used based on the route information obtained by the service management unit 21.

[0120] More specifically, for example, when the decision unit 22 determines a plurality of resources R to be used to perform service S, it calculates the usage period U of each resource R based on the service provision area A corresponding to that resource R, the desired service provision period indicated by the route information, and the calculated travel section Q.

[0121] The decision unit 22 then outputs to the relay unit 11 a resource request for requesting multiple resources R that it has decided to use to execute the service S, and usage period information indicating the usage period U for each resource R.

[0122] (Sending resource requests and usage period information) For example, the relay unit 11 sends a resource request to the resource management server 170 to request the resource R determined by the determination unit 22, and usage period information indicating the usage period U for each resource R determined by the determination unit 22.

[0123] For example, the memory unit 13 stores identification information (hereinafter also referred to as "vehicle ID") for identifying vehicle 1.

[0124] The relay unit 11 transmits the allocation request information, which includes the resource request and usage period information received from the decision unit 22, and the vehicle ID stored in the storage unit 13, to the resource management server 170 via the TCU 202A.

[0125] [Receiving resource requests] Referring again to Figure 4, in the resource management server 170, the communication unit 31 receives a resource request from the vehicle 1.

[0126] More specifically, the communication unit 31 receives allocation request information from the in-vehicle relay device 101 via the wireless base station device 161 and the external network 151. The communication unit 31 then outputs the received allocation request information to the resource allocation unit 33.

[0127] [Resource allocation] For example, the resource allocation unit 33 allocates resource R based on the resource request received by the communication unit 31.

[0128] For example, the storage unit 35 stores a resource management table that shows the correspondence between the type of resource R, the duration, and the utilization rate of resource R.

[0129] The resource allocation unit 33 compares the utilization rate C during the usage period U of each resource R indicated by the resource request included in the allocation request information received from the communication unit 31 with the threshold Th11.

[0130] Specifically, for example, when the resource allocation unit 33 receives allocation request information from the communication unit 31, it refers to the resource management table in the storage unit 35 to identify the resource R of the type indicated by the resource request included in the allocation request information and the usage rate C corresponding to the usage period U indicated by the usage period information included in the allocation request information. The resource allocation unit 33 then checks whether the identified resource R's usage rate C is less than the threshold Th11.

[0131] The resource allocation unit 33 determines that if the utilization rate C of the identified resource R is equal to or greater than the threshold Th11, it is not possible to allocate the resource R corresponding to that utilization rate C. The resource allocation unit 33 then outputs to the communication unit 31 unallocated information indicating that the allocation of resource R is not possible, including the vehicle ID included in the allocation request information received from the communication unit 31.

[0132] On the other hand, the resource allocation unit 33 determines that if the utilization rate C of the identified resource R is less than the threshold Th11, the resource R corresponding to that utilization rate C can be allocated. The resource allocation unit 33 then outputs to the communication unit 31 the allocation information indicating the type of resource R that it has determined can be allocated, including the vehicle ID included in the allocation request information received from the communication unit 31.

[0133] For example, the storage unit 35 stores a server table that shows the correspondence between the type of resource R and identification information (hereinafter also referred to as "server ID") for identifying the edge server 180.

[0134] If the resource allocation unit 33 determines that the utilization rate C of the identified resource R is less than the threshold Th11, it refers to the server table in the storage unit 35 to identify the server ID corresponding to that resource R. The resource allocation unit 33 then outputs service request information to the communication unit 31 indicating a request to execute the service S corresponding to that resource R, along with the identified server ID.

[0135] When the communication unit 31 receives unallocable or available resource information from the resource allocation unit 33, it creates an IP packet P2 containing the unallocable or available resource information, which includes the IP address of the resource management server 170 and the IP address of vehicle 1 corresponding to the vehicle ID included in the unallocable or available resource information as the source IP address and destination IP address, respectively. The communication unit 31 then sends the created IP packet P2 to the TCU202A.

[0136] Furthermore, when the communication unit 31 receives service request information from the resource allocation unit 33, it creates an IP packet P3 containing the service request information, which includes the IP address of the resource management server 170 and the IP address of the edge server 180 corresponding to the server ID indicated by the service request information as the source IP address and destination IP address, respectively. The communication unit 31 then sends the created IP packet P3 to the destination edge server 180.

[0137] Referring again to Figures 2 and 3, when TCU202A receives an IP packet P2 from the resource management server 170, it transmits the unassigned or assignable information contained in the received IP packet P2 to the in-vehicle relay device 101.

[0138] In the in-vehicle relay device 101, when the relay unit 11 receives unassigned information or assignable information from the TCU 202A, it transmits the received unassigned information or assignable information to the navigation device 202C.

[0139] When the navigation device 202C receives information that a unit cannot be assigned from the in-vehicle relay device 101, it performs notification processing based on that information.

[0140] Specifically, for example, when the navigation device 202C receives information that resource R could not be allocated from the in-vehicle relay device 101, it displays a screen on its own display unit indicating that resource R could not be allocated.

[0141] [Edge Server] Figure 5 shows an example of the configuration of an edge server according to an embodiment of the present disclosure. Referring to Figure 5, the edge server 180 comprises a communication unit 41, a service execution unit 42, and a storage unit 43. One or both of the communication unit 41 and the service execution unit 42 are implemented by a processing circuit including, for example, one or more processors. The storage unit 43 is, for example, a non-volatile memory included in the processing circuit.

[0142] When the communication unit 41 receives service request information from the resource management server 170 via the external network 151, it outputs the received service request information to the service execution unit 42.

[0143] (Service Execution Unit) When the service execution unit 42 receives service request information from the communication unit 41, it executes a service S of the type indicated by the service request information.

[0144] Figure 6 is a diagram illustrating an example of a service performed by an edge server in a communication system according to an embodiment of the present disclosure.

[0145] In the example shown in Figure 6, the communication system 501 includes edge servers 180A, 180B, and 180C, which are edge servers 180.

[0146] Edge server 180A performs LKAS and ACC services. Edge servers 180B and 180C perform obstacle avoidance and door unlocking services, respectively.

[0147] <LKASサービスおよびACCサービス> Referring to Figures 5 and 6, in the edge server 180A, when the service execution unit 42 receives service request information S1 from the resource management server 170 via the communication unit 41 indicating that it requests the execution of LKAS service and ACC service, it requests the in-vehicle relay device 101 to transmit vehicle information indicating the status of vehicle 1, which is used to generate control information.

[0148] More specifically, for example, the service execution unit 42 transmits data request information indicating the type of vehicle information to be used for generating control information to the in-vehicle relay device 101 via the communication unit 41.

[0149] Specifically, the service execution unit 42 creates data request information (hereinafter also referred to as "data request information D1") indicating a request to transmit location information and vehicle speed information as vehicle information, and the vehicle ID indicated in the service request information S1 received from the communication unit 41. The service execution unit 42 then outputs the created data request information D1 to the communication unit 41.

[0150] When the communication unit 41 receives data request information D1 from the service execution unit 42, it creates an IP packet P11 containing the data request information D1, which includes the IP address of the edge server 180A and the IP address of vehicle 1 corresponding to the vehicle ID indicated in the data request information D1 as the source IP address and destination IP address, respectively. The communication unit 41 then sends the created IP packet P11 to the TCU 202A.

[0151] When TCU202A receives an IP packet P11 from the edge server 180A, it transmits the data request information D1 contained in the received IP packet P11 to the in-vehicle relay device 101.

[0152] Referring again to Figure 3, in the in-vehicle relay device 101, when the service management unit 21 receives data request information D1 from the TCU 202A via the relay unit 11, it transmits location information and vehicle speed information to the edge server 180A via the TCU 202A.

[0153] Specifically, after receiving data request information D1, the service management unit 21 transmits location information from the navigation device 202C to the edge server 180A via the TCU 202A each time it receives location information.

[0154] Furthermore, after receiving data request information D1, the service management unit 21 transmits the vehicle speed information from the vehicle speed sensor 202B to the edge server 180A via the TCU 202A each time it receives vehicle speed information.

[0155] Referring again to Figures 5 and 6, the edge server 180A communicates with, for example, one or more roadside sensors installed on a highway. These roadside sensors periodically detect objects on the road and transmit roadside sensor information K1 indicating the detection result to the edge server 180A.

[0156] In the edge server 180A, for example, the storage unit 43 stores map information for a region that includes the location indicated by the location information transmitted from the in-vehicle relay device 101.

[0157] When the service execution unit 42 receives location information from the in-vehicle relay device 101 via the communication unit 41, it uses the received location information and the map information stored in the storage unit 43 to determine whether or not the vehicle 1 is traveling on a highway.

[0158] When the service execution unit 42 determines that vehicle 1 is traveling on a highway, it executes LKAS service and ACC service based on the information received from the in-vehicle relay device 101 after determining that vehicle 1 is traveling on a highway, specifically location information and vehicle speed information, as well as roadside sensor information K1 received from the roadside sensor.

[0159] The edge server 180A transmits the execution results of the LKAS service and the ACC service to the in-vehicle relay device 101.

[0160] More specifically, for example, in the edge server 180A, the service execution unit 42 transmits control information (hereinafter also referred to as "control information G1"), which is the result of executing the LKAS service, to the in-vehicle relay device 101 via the communication unit 41 and TCU 202A. Control information G1 is information for controlling an in-vehicle device 202 that should be operated to prevent the vehicle 1 from deviating from the driving lane. Here, the in-vehicle device 202 is assumed to be a steering ECU.

[0161] Furthermore, for example, the service execution unit 42 transmits control information (hereinafter also referred to as "control information G2"), which is the result of executing the ACC service, to the in-vehicle relay device 101 via the communication unit 41 and TCU 202A. Control information G2 is information for controlling an in-vehicle device 202 that should be operated to maintain a certain distance from the vehicle ahead. Here, the in-vehicle device 202 is assumed to be a brake ECU.

[0162] Referring again to Figures 2 and 3, in the in-vehicle relay device 101, for example, the control unit 23 controls the in-vehicle equipment 202 of the vehicle 1 using control information received from the edge server 180A via the TCU 202A and relay unit 11.

[0163] More specifically, when the control unit 23 receives control information G1 from the edge server 180A via the TCU 202A and relay unit 11, it transmits the control information G1 to the steering ECU via the relay unit 11.

[0164] When the steering ECU receives control information G1 from the in-vehicle relay device 101, it operates according to the received control information G1.

[0165] Furthermore, when the control unit 23 receives control information G2 from the edge server 180A via the TCU 202A and relay unit 11, it transmits the control information G2 to the brake ECU via the relay unit 11.

[0166] When the brake ECU receives control information G2 from the in-vehicle relay device 101, it operates according to the received control information G2.

[0167] <Obstacle avoidance service> In the edge server 180B, when the service execution unit 42 receives service request information S2 from the resource management server 170 via the communication unit 41 indicating a request to execute the obstacle avoidance service, it creates data request information (hereinafter also referred to as "data request information D2") indicating a request to send the data necessary for executing the obstacle avoidance service and the vehicle ID indicated in the service request information S2. The service execution unit 42 then outputs the created data request information D2 to the communication unit 41.

[0168] In this embodiment, for example, the data required to perform the obstacle avoidance service includes the location information of vehicle 1, the vehicle speed information of vehicle 1, information indicating the detection result of a roadside sensor installed at the intersection CS, the location information of another vehicle 1 entering the intersection CS, and the vehicle speed information of the other vehicle 1.

[0169] When the communication unit 41 receives data request information D2 from the service execution unit 42, it creates an IP packet P12 containing the data request information D1, which includes the IP address of the edge server 180B and the IP address of vehicle 1 corresponding to the vehicle ID indicated in the data request information D2 as the source IP address and destination IP address, respectively. The communication unit 31 then sends the created IP packet P12 to the TCU 202A.

[0170] When TCU202A receives an IP packet P12 from the edge server 180B, it transmits the data request information D2 contained in the received IP packet P12 to the in-vehicle relay device 101.

[0171] Referring again to Figure 3, in the in-vehicle relay device 101, when the service management unit 21 receives data request information D2 from the TCU 202A via the relay unit 11, it transmits location information and vehicle speed information to the edge server 180B via the TCU 202A.

[0172] Specifically, after receiving data request information D2, the service management unit 21 transmits location information from the navigation device 202C to the edge server 180B via the TCU 202A each time it receives location information.

[0173] Furthermore, after receiving data request information D2, the service management unit 21 transmits the vehicle speed information from the vehicle speed sensor 202B to the edge server 180B via the TCU 202A each time it receives vehicle speed information.

[0174] Referring again to Figures 5 and 6, the edge server 180B communicates with, for example, one or more roadside sensors installed around the intersection CS. These roadside sensors periodically detect objects on the road and transmit roadside sensor information K2 indicating the detection result to the edge server 180B.

[0175] In the edge server 180B, for example, the storage unit 43 stores map information for a region that includes the location indicated by the location information transmitted from the in-vehicle relay device 101.

[0176] Furthermore, the edge server 180B communicates with other vehicles 1 traveling around the intersection CS to obtain location information and vehicle speed information from those other vehicles 1.

[0177] When the service execution unit 42 receives location information from the in-vehicle relay device 101 via the communication unit 41, it uses the received location information and the map information stored in the storage unit 43 to determine whether or not the vehicle 1 is passing through intersection CS.

[0178] When the service execution unit 42 determines that vehicle 1 is passing through an intersection CS, it executes an obstacle avoidance service based on the information received from the in-vehicle relay device 101 immediately after determining that vehicle 1 is passing through an intersection CS, specifically, location information and vehicle speed information, roadside sensor information K2 received from roadside sensors installed at the intersection CS, and location information and vehicle speed information of other vehicles 1 around the intersection CS.

[0179] The edge server 180B transmits the results of the obstacle avoidance service to the in-vehicle relay device 101.

[0180] More specifically, for example, in the edge server 180B, the service execution unit 42 transmits warning information indicating that an obstacle has been detected at the intersection CS to the in-vehicle relay device 101 via the external network 151 and the wireless base station device 161 as a result of executing the obstacle avoidance service.

[0181] Referring again to Figures 2 and 3, in the in-vehicle relay device 101, when the service management unit 21 receives warning information from the edge server 180B via the TCU 202A and relay unit 11, it transmits the received warning information to the navigation device 202C via the relay unit 11.

[0182] When the navigation device 202C receives warning information from the in-vehicle relay device 101, it performs notification processing based on the received warning information. Specifically, for example, the navigation device 202C displays a screen on its display unit indicating that an obstacle has been detected at the intersection CS being passed through.

[0183] Furthermore, the edge server 180B may use, in place of, or in addition to, the location and speed information of another vehicle 1, the location and speed information of a vehicle V that does not have an in-vehicle system 301 and is traveling around the intersection CS, as data necessary for performing the obstacle avoidance service.

[0184] Furthermore, the edge server 180B may transmit warning information not only to vehicle 1, but also to other vehicles 1 entering the intersection CS that have not requested the execution of the obstacle avoidance service. Alternatively, the edge server 180B may be configured to transmit warning information not only to vehicle 1, but also to vehicle V entering the intersection CS.

[0185] Furthermore, the edge server 180B may be configured to transmit control information to the in-vehicle relay device 101 in addition to, or instead of, warning information, as a result of executing the obstacle avoidance service, to control the vehicle 1's movement in order to avoid the obstacle. In this case, the in-vehicle relay device 101 transmits the control information received from the edge server 180B to in-vehicle equipment 202 such as the steering ECU.

[0186] <Door unlocking service> Referring again to Figures 5 and 6, for example, when the resource management server 170 receives service request information S3 from the communication unit 41 indicating a request to perform the door unlocking service, it creates data request information (hereinafter also referred to as "data request information D3") indicating a request to send the data necessary to perform the door unlocking service and the vehicle ID indicated in the service request information S3. The service execution unit 42 then outputs the created data request information D3 to the communication unit 41.

[0187] In this embodiment, for example, the data required to perform the door unlocking service includes location information of vehicle 1, power information indicating the power status of vehicle 1, door information indicating the open / closed state of the vehicle 1's doors, and image information showing the facial image of the vehicle 1's occupant. The power information is, for example, information indicating the state of the vehicle 1's ignition power supply.

[0188] When the communication unit 41 receives data request information D3 from the service execution unit 42, it creates an IP packet P13 containing the data request information D3, which includes the IP address of the edge server 180C and the IP address of vehicle 1 corresponding to the vehicle ID indicated in the data request information D3 as the source IP address and destination IP address, respectively. The communication unit 31 then sends the created IP packet P13 to the TCU 202A.

[0189] When TCU202A receives IP packet P13 from edge server 180C, it transmits data request information D3 contained in the received IP packet P13 to the in-vehicle relay device 101.

[0190] Referring again to Figure 3, in the in-vehicle relay device 101, when the service management unit 21 receives data request information D3 from the TCU 202A via the relay unit 11, it periodically transmits location information, power information, and door information to the edge server 180C via the relay unit 11 and the TCU 202A.

[0191] Referring again to Figures 5 and 6, in the edge server 180C, the service execution unit 42 determines whether or not vehicle 1 is parked.

[0192] More specifically, for example, when the service execution unit 42 receives power information from the in-vehicle relay device 101 via the communication unit 41, it checks whether the ignition power state indicated by the received power information is in the off state.

[0193] The service execution unit 42 determines that vehicle 1 is not parked if the ignition power supply is in the ON state.

[0194] On the other hand, the service execution unit 42 determines that vehicle 1 is parked if the ignition power supply is in the off state.

[0195] For example, the storage unit 43 stores map information for a region that includes the location indicated by the location information transmitted from the in-vehicle relay device 101.

[0196] If the service execution unit 42 determines that vehicle 1 is parked, it uses the location information received from the in-vehicle relay device 101 immediately after determining that vehicle 1 is parked, and the map information stored in the storage unit 43, to identify the location of the parking lot where vehicle 1 is parked.

[0197] The service execution unit 42 then checks whether or not a camera for capturing facial images of passengers in vehicle 1 is installed in vehicle 1.

[0198] Specifically, when the service execution unit 42 identifies the location of the parking lot where vehicle 1 is parked, it sends a confirmation notification to the in-vehicle relay device 101 via the communication unit 41 and TCU 202A to confirm whether or not a camera is installed on vehicle 1.

[0199] In the in-vehicle relay device 101, when the service management unit 21 receives an acknowledgment notification from the edge server 180C via the TCU 202A and the relay unit 11, it sends response information indicating a response to the acknowledgment notification to the edge server 180C via the relay unit 11 and the TCU 202A.

[0200] In the edge server 180C, if the service execution unit 42 receives response information from the in-vehicle relay device 101 via the TCU 202A and communication unit 41 indicating that no camera is installed in the vehicle 1, it acquires image information from a peripheral device located outside the vehicle 1, such as a camera installed in a parking lot.

[0201] For example, the edge server 180C communicates with a camera installed in the parking lot where vehicle 1 is parked. When the camera detects a person at a target location in the parking lot, it sends image information showing the face of the detected person to the edge server 180C.

[0202] The edge server 180C is not limited to a camera installed in the parking lot; it may also be a communication terminal device carried by the occupant of vehicle 1, and may be configured to communicate with a communication terminal device including a camera. In this case, for example, when the occupant of vehicle 1 unlocks the door of vehicle 1 while it is parked, they use the communication terminal device to take a picture of their own face. The communication terminal device transmits image information showing the face image to the edge server 180C.

[0203] When the service execution unit 42 receives image information from a camera installed in the parking lot via the communication unit 41, it checks whether the door open / closed state, as indicated by the door information received from the in-vehicle relay device 101 immediately after receiving the image information, is in the closed state.

[0204] On the other hand, when the service execution unit 42 receives response information from the in-vehicle relay device 101 via the TCU 202A and the communication unit 41 indicating that a camera is mounted on the vehicle 1, it checks whether the door open / closed state indicated by the door information received from the in-vehicle relay device 101 immediately after identifying the parking lot location is in the closed state.

[0205] Then, if the door is in the closed state, the service execution unit 42 performs a door unlocking service.

[0206] The edge server 180C transmits the results of the door unlocking service to the in-vehicle relay device 101.

[0207] More specifically, for example, in the edge server 180B, the service execution unit 42 transmits control information (hereinafter also referred to as "control information G3"), which is the result of executing the door unlocking service, to the in-vehicle relay device 101 via the communication unit 41. Control information G3 is information for controlling the in-vehicle device 202 that should be operated to unlock the doors of the vehicle 1. In this case, the in-vehicle device 202 is the door lock ECU.

[0208] For example, when the service execution unit 42 acquires image information from a camera installed in the parking lot, it transmits the image information and the vehicle ID of vehicle 1 to the in-vehicle relay device 101 in the control information G3.

[0209] Furthermore, for example, if a camera is mounted on vehicle 1, the service execution unit 42 transmits the vehicle ID of vehicle 1, along with the vehicle ID of vehicle 1, to the in-vehicle relay device 101 in the control information G3.

[0210] Referring again to Figure 3, in the in-vehicle relay device 101, when the control unit 23 receives control information G3 from the edge server 180C via the TCU 202A and relay unit 11, it performs facial recognition of the occupant of vehicle 1.

[0211] For example, the memory unit 13 stores passenger information that shows the facial images of the passengers of vehicle 1. If the control unit 23 receives control information G3 from the edge server 180C and includes image information, it calculates the similarity between the facial image shown in the image information and the facial image shown in the passenger information stored in the memory unit 13.

[0212] On the other hand, if the control information G3 received from the edge server 180C does not contain image information, the control unit 23 calculates the similarity between the face image shown in the image information received from the camera mounted on the vehicle 1 and the face image shown in the passenger information stored in the storage unit 13.

[0213] The control unit 23 determines that face recognition has failed if the calculated similarity is below the threshold. On the other hand, the control unit 23 determines that face recognition has succeeded if the calculated similarity is equal to or greater than the threshold.

[0214] When the control unit 23 determines that facial recognition has been successful, it transmits the control information G3 received from the edge server 180C to the door lock ECU via the relay unit 11.

[0215] When the door lock ECU receives control information G3 from the in-vehicle relay device 101, it operates according to the received control information G3. That is, the door lock ECU unlocks the doors of vehicle 1.

[0216] Figure 7 shows an example of resource allocation by an in-vehicle relay device according to an embodiment of the present disclosure.

[0217] In the example shown in Figure 7, the communication system 501 includes edge servers 180D, 180E, and 180F. Edge server 180D is assigned to vehicle 1A, which is vehicle 1. Edge server 180E is assigned to vehicles 1B, 1C, 1D, and 1E, which are vehicle 1. Edge server 180F is assigned to vehicles 1F and 1G, which are vehicle 1.

[0218] Furthermore, in the example shown in Figure 7, for instance, edge servers 180D, 180E, and 180F perform the same service S on each other.

[0219] In the following explanation, service area A of edge server 180D, service area A of edge server 180E, and service area A of edge server 180F will also be referred to as service area A1, service area A2, and service area A3, respectively.

[0220] [Reallocate resources] Referring again to Figure 4, in the resource management server 170, for example, when the communication unit 31 receives a new resource request from another vehicle 1, the resource allocation unit 33 reallocates resource R based on the planned route E of the other vehicle 1.

[0221] (a) Example 1 Figure 8 shows an example of resource reallocation by an in-vehicle relay device according to an embodiment of the present disclosure. Figure 8 shows the reallocation of resource R when the resource management server 170 receives a new resource request from vehicle 1H, which is vehicle 1.

[0222] In the example shown in Figure 8, vehicle 1H sends request information to resource management server 170, which includes a resource request indicating the use of edge server 180E and usage period information indicating the usage period U of edge server 180E (hereinafter also referred to as "usage period U1"). In the example shown in Figure 8, it is assumed that the utilization rate C of edge server 180E during usage period U1 is greater than or equal to the threshold Th11.

[0223] Referring to Figures 4 and 8, in the resource management server 170, the resource allocation unit 33 determines whether or not reassignment of the edge server 180E is possible because the utilization rate C of the edge server 180E during the usage period U1 is equal to or greater than the threshold Th11.

[0224] For example, the resource allocation unit 33 determines the allocation of multiple resources R according to multiple service provision areas A, each corresponding to a multiple resource R.

[0225] Specifically, for example, the resource allocation unit 33 checks whether there are other vehicles 1 traveling in other service provision areas A that overlap with service provision area A2 during the usage period U1.

[0226] The resource allocation unit 33 determines that if there is another vehicle 1 traveling in another service area A that overlaps with service area A2 during the usage period U1, then it is possible to reallocate the edge server 180E. The resource allocation unit 33 then changes the edge server 180 assigned to the other vehicle 1 during the usage period U1 to the edge server 180 corresponding to the other service area A.

[0227] In the example shown in Figure 8, vehicles 1B and 1C are assumed to travel in the overlapping areas of service provision area A1 and service provision area A2 during the usage period U1. In this case, the resource allocation unit 33 changes the resource R to be allocated to vehicles 1B and 1C during the usage period U1 from edge server 180E to edge server 180D. The resource allocation unit 33 then determines that edge server 180E will be allocated as resource R to vehicle 1H during the usage period U1 and transmits the allocation information to vehicle 1H via the communication unit 31.

[0228] On the other hand, if, during the usage period U1, there are no other vehicles 1 traveling in other service provision areas A that overlap with service provision area A2, the resource allocation unit 33 transmits information that allocation is not possible to vehicle 1H via the communication unit 31.

[0229] (b) Example 2 Figure 9 shows another example of resource reallocation by an in-vehicle relay device according to an embodiment of the present disclosure. Figure 9 shows the reallocation of resource R when the resource management server 170 receives a new resource request from vehicle 1J, which is vehicle 1.

[0230] In the example shown in Figure 9, vehicle 1J sends allocation request information to resource management server 170, which includes a resource request indicating the use of edge server 180D and usage period information indicating the usage period U of edge server 180D (hereinafter also referred to as "usage period U2"). In the example shown in Figure 9, it is assumed that the utilization rate C of edge server 180D during usage period U2 is greater than or equal to the threshold Th11.

[0231] Referring to Figures 4 and 9, in the resource management server 170, the resource allocation unit 33 determines whether or not the edge server 180D can be reassigned because the utilization rate C of the edge server 180D during the usage period U2 is equal to or greater than the threshold Th11.

[0232] Specifically, for example, the resource allocation unit 33 checks whether vehicle 1J will travel through other service provision areas A that overlap with service provision area A2 during the usage period U2, based on the route information included in the allocation request information received from vehicle 1J.

[0233] In the example shown in Figure 9, vehicle 1J is assumed to travel through the overlapping areas of service area A1 and service area A3 during the usage period U2. In this case, the resource allocation unit 33 determines that edge server 180F, rather than edge server 180D, is to be allocated as resource R to vehicle 1J.

[0234] The resource allocation unit 33 then transmits allocation information indicating that the edge server 180F has been allocated to the vehicle 1J via the communication unit 31.

[0235] On the other hand, if the vehicle 1J does not travel through any other service area A that overlaps with service area A2 during the usage period U2, the resource allocation unit 33 transmits information that the allocation is unavailable to the vehicle 1J via the communication unit 31.

[0236] (c) Example 3 For example, if resource R is insufficient and the communication unit 31 receives a new resource request from another vehicle 1, the resource allocation unit 33 reallocates resource R according to priority. For example, priority is determined according to the type of vehicle 1.

[0237] Figure 10 shows another example of resource reallocation by an in-vehicle relay device according to an embodiment of the present disclosure. Figure 10 shows the reallocation of resource R when the resource management server 170 receives a new resource request from vehicle 1K, which is vehicle 1.

[0238] In the example shown in Figure 10, vehicle 1K sends allocation request information to resource management server 170, which includes a resource request indicating that it requests the use of edge server 180F, and usage period information indicating the usage period of edge server 180F (hereinafter also referred to as "usage period U3"). In the example shown in Figure 10, it is assumed that the utilization rate C of edge server 180F during usage period U3 is greater than or equal to the threshold Th11.

[0239] Referring to Figures 4 and 10, the resource allocation unit 33 sends an information request notification N2 to each vehicle 1, i.e., vehicles 1F, 1G, and 1K, that travels through the service provision area A3 during the usage period U3, indicating that it requests the transmission of type information indicating the type of vehicle 1, if the utilization rate C of the edge server 180F during the usage period U3 is equal to or greater than the threshold Th11.

[0240] Vehicles 1F, 1G, and 1K send type information to the resource management server 170 as a response to the information request notification N2 received from the resource management server 170.

[0241] In the resource management server 170, the resource allocation unit 33 uses the type information received from the vehicle 1 via the communication unit 31 to confirm whether the vehicle 1 is a vehicle of a specific type. In this embodiment, for example, the resource allocation unit 33 uses the received type information to confirm whether the vehicle 1 that sent the type information is an emergency vehicle such as an ambulance.

[0242] The resource allocation unit 33 determines that if the vehicle 1 that is the source of the type information is an emergency vehicle, it will allocate the edge server 180F as resource R to be assigned to the vehicle 1 during the usage period U3. On the other hand, if the vehicle 1 that is the source of the type information is not an emergency vehicle but a general vehicle, the resource allocation unit 33 determines that it will not assign resource R to the vehicle 1 during the usage period U3.

[0243] In the example shown in Figure 10, vehicle 1K is an emergency vehicle, and vehicles 1F and 1G are general vehicles. In this case, the resource allocation unit 33 decides to allocate edge server 180F to vehicle 1K during usage period U3. The resource allocation unit 33 also decides not to allocate edge server 180F to vehicles 1F and 1G during usage period U3.

[0244] Furthermore, the priority used in reallocating resource R may be determined not only by the type of vehicle 1, but also by the type of service S provided to vehicle 1. In Figure 10, for example, if the service S provided to vehicle 1K is a specific service S, then edge server 180F is preferentially allocated to vehicle 1K during usage period U3.

[0245] Specifically, if the utilization rate C of the edge server 180F during the usage period U3 is greater than or equal to the threshold Th11, the resource allocation unit 33 checks whether the type of service S indicated by the route information included in the allocation request information received from each vehicle 1 traveling in the service provision area A3 during the usage period U3 is a specific service S. Specific services S include services that require vehicle 1 to move to a safe location, services that are mandated to be performed by traffic laws, etc., and services that place a heavy processing load on vehicle 1.

[0246] The resource allocation unit 33 determines that if the type of service S indicated by the route information included in the allocation request information received from vehicle 1 is a specific service S, it will allocate the edge server 180F as resource R to be allocated to vehicle 1 during the usage period U3. On the other hand, if the type of service S indicated by the route information is not a specific service S, the resource allocation unit 33 determines that it will not allocate resource R to vehicle 1 during the usage period U3.

[0247] Furthermore, the priority used in reallocating resource R may be determined according to the load status of vehicle 1. Specifically, for example, the load status of vehicle 1 is the usage rate W of the CPU and memory, etc., of each in-vehicle device 202 of vehicle 1. Here, the said load status is assumed to be the CPU usage rate W of each in-vehicle device 202.

[0248] In Figure 10, for example, if the utilization rate W of each in-vehicle device 202 in vehicle 1K is greater than or equal to the threshold Th21, then the edge server 180F is preferentially assigned to vehicle 1K during the usage period U3.

[0249] Referring again to Figures 2 and 3, for example, in the in-vehicle relay device 101, when the decision unit 22 has determined the resource R to be used to perform the service S, it sends an information request notification N3 to each in-vehicle device 202 via the relay unit 11, indicating that it requests the transmission of equipment status information showing the utilization rate W.

[0250] Each in-vehicle device 202 transmits device status information to the in-vehicle relay device 101 as a response to the information request notification N3 received from the in-vehicle relay device 101.

[0251] In the in-vehicle relay device 101, the determination unit 22 transmits the allocation request information to the resource management server 170, including multiple device status information received from each in-vehicle device 202 via the relay unit 11.

[0252] Referring again to Figures 4 and 10, the resource allocation unit 33, if the utilization rate C of the edge server 180F during the usage period U3 is equal to or greater than the threshold Th11, checks whether the utilization rate W of each in-vehicle device 202 of each vehicle 1 traveling in the service provision area A3 during the usage period U3 is equal to or greater than the threshold Th21.

[0253] The resource allocation unit 33 determines that if the utilization rate W of each in-vehicle device 202 of vehicle 1 is equal to or greater than the threshold Th21, it will allocate the edge server 180F as resource R to be allocated to vehicle 1 during the usage period U3. On the other hand, if the utilization rate of at least one of the multiple in-vehicle devices 202 of vehicle 1 is less than the threshold Th21, the resource allocation unit 33 determines that it will not allocate resource R to vehicle 1 during the usage period U3.

[0254] [Resource release request] Referring again to Figures 1 and 3, in the in-vehicle relay device 101, the service management unit 21 sends a request to release resource R to the resource management server 170.

[0255] More specifically, for example, the service management unit 21 determines whether the conditions for terminating the provision of service S (hereinafter also referred to as "termination conditions") are met. Termination conditions include when the user of vehicle 1 wishes to terminate the provision of service S, and when vehicle 1 moves from within service area A to outside service area A. In the following explanation, we will assume that the termination condition is when the user of vehicle 1 wishes to terminate the provision of service S.

[0256] For example, the navigation device 202C receives input indicating a desire to terminate the provision of service S. Upon receiving this input, the navigation device 202C transmits termination information indicating the desire to terminate the provision of service S to the in-vehicle relay device 101.

[0257] In the in-vehicle relay device 101, when the service management unit 21 receives termination information from the navigation device 202C via the relay unit 11, it determines that the termination conditions have been met. The service management unit 21 then sends release request information, including a release request indicating the type of resource R to be released and the vehicle ID stored in the storage unit 13, to the resource management server 170 via the relay unit 11 and TCU 202A.

[0258] [Release resources] Referring again to Figure 4, in the resource management server 170, when the communication unit 31 receives release request information from the in-vehicle relay device 101, it outputs the received release request information to the resource release unit 34.

[0259] When the resource release unit 34 receives a release request information from the communication unit 31, it releases resource R.

[0260] More specifically, for example, when the resource release unit 34 receives release request information from the communication unit 31, it updates the resource management table in the storage unit 36. Specifically, for example, the resource release unit 34 updates the utilization rate C in the resource management table corresponding to the type of resource R indicated by the release request information. The updated utilization rate C is smaller than the utilization rate C before the update.

[0261] Furthermore, the resource release unit 34 refers to the server table in the storage unit 35 to identify the server ID corresponding to the type of resource R indicated by the release request included in the release request information received from the communication unit 31.

[0262] The resource release unit 34 then sends stop request information indicating a request to stop the execution of service S to the edge server 180 of the identified service ID via the communication unit 31.

[0263] Referring again to FIG. 5, in the edge server 180, when the service execution unit 42 receives the stop request information from the resource management server 170 via the communication unit 41, it stops the execution of the service S according to the received stop request information.

[0264] [Operation flow] Next, the operation flow of each device in the communication system 501 according to the embodiment of the present disclosure will be described with reference to the drawings.

[0265] FIG. 11 is a flowchart defining an example of an operation procedure when the resource management server according to the embodiment of the present disclosure performs the distribution process.

[0266] Referring to FIG. 11, first, the resource management server 170 waits for the arrival of the processing timing T (NO in step ST101).

[0267] Then, when the processing timing T arrives (YES in step ST101), the resource management server 170 transmits an information request notification N1 indicating a request to transmit performance information to each edge server 180 (step ST102).

[0268] Next, the resource management server 170 waits for the reception of the performance information from each edge server 180 (NO in step ST103).

[0269] Then, when the resource management server 170 receives the performance information from each edge server 180 (YES in step ST103), it acquires the type information and the provided area information from the storage unit 35 (step ST104).

[0270] Next, the resource management server 170 performs a distribution process of distributing the acquired type information, provided area information, and resource information including the performance information received from each edge server 180 to the in-vehicle relay device 101 (step ST105), and waits for the arrival of the next processing timing T (NO in step ST101).

[0271] FIG. 12 and FIG. 13 are flowcharts defining an example of an operation procedure when a resource management server according to an embodiment of the present disclosure allocates resources. Note that FIGS. 12 and 13 show the operation when the resource management server 170 allocates the resource R to one vehicle 1. The resource management server 170 performs the processes of FIGS. 12 and 13 in parallel for each vehicle 1, for example.

[0272] Referring to FIGS. 12 and 13, first, the resource management server 170 waits to receive allocation request information from the in-vehicle relay device 101 (NO in step ST201).

[0273] Then, when the resource management server 170 receives the allocation request information from the in-vehicle relay device 101 (YES in step ST201), it determines whether it is possible to allocate the resource R during the usage period U indicated by the usage period information included in the allocation request information. For example, as described above, the resource management server 170 refers to the resource management table in the storage unit 36 to identify the type of resource R indicated by the resource request included in the received request information and the usage rate C corresponding to the usage period U. Then, the resource management server 170 checks whether the identified usage rate C is less than the threshold Th11 (step ST202).

[0274] Next, when the resource management server 170 determines that it is possible to allocate the resource R during the usage period U (YES in step ST202), it allocates the resource R (step ST203).

[0275] Next, the resource management server 170 transmits allocatable information indicating the type of the resource R determined to be allocatable to the in-vehicle relay device 101 (step ST204).

[0276] Next, the resource management server 170 sends service request information to the edge server 180 indicating a request for the execution of service S corresponding to the allocated resource R, the server ID of the edge server 180 corresponding to resource R, and the vehicle ID included in the received request information (step ST205). Steps ST204 and ST205 may be executed in any order or in parallel.

[0277] Next, the resource management server 170 awaits the reception of a release request information from the in-vehicle relay device 101 (NO in step ST206).

[0278] Then, when the resource management server 170 receives a release request information from the in-vehicle relay device 101 (YES in step ST206), it releases resource R (step ST207) and waits to receive new allocation request information from the in-vehicle relay device 101 (NO in step ST201).

[0279] On the other hand, if the resource management server 170 determines that it is not possible to allocate resource R during the usage period U (NO in step ST202), it determines whether it is possible to reallocate resource R. For example, as described above, the resource management server 170 checks whether there are other vehicles 1 traveling in other service provision areas A that overlap with the service provision area A corresponding to resource R during the usage period U (step ST208).

[0280] Next, if the resource management server 170 determines that resource R can be reallocated (YES in step ST208), it reallocates resource R (step ST209) and transmits the reallocation information to the in-vehicle relay device 101 (step ST204).

[0281] On the other hand, if the resource management server 170 determines that reallocation of resource R is not possible (NO in step ST208), it sends allocation impossible information to the in-vehicle relay device 101 indicating that resource R cannot be allocated (step ST210), and waits for new allocation request information from the in-vehicle relay device 101 (NO in step ST201).

[0282] Figure 14 is a flowchart illustrating an example of the operation procedure when an edge server according to the embodiment of this disclosure performs a service. Figure 14 shows the operation of edge server 180A.

[0283] Referring to Figure 14, first, the edge server 180A waits for the reception of service request information S1 from the resource management server 170 (NO in step ST301).

[0284] Then, when the edge server 180A receives service request information S1 from the resource management server 170 (YES in step ST301), it sends data request information D1 to the in-vehicle relay device 101 indicating that it requests the transmission of vehicle information necessary for the execution of the type of service S indicated by the service request information S1, namely the LKAS service and the ACC service (step ST302).

[0285] Next, the edge server 180A waits to receive vehicle information from the in-vehicle relay device 101 (NO in step ST303).

[0286] Then, when the edge server 180A receives vehicle information from the in-vehicle relay device 101 (YES in step ST303), it uses the received vehicle information to execute LKAS service and ACC service. For example, as described above, the edge server 180A uses the vehicle information to create control information G1 and G2 for controlling the in-vehicle equipment 202 of vehicle 1 (step ST304).

[0287] Next, the edge server 180A transmits the execution results of the LKAS service and the ACC service, that is, the control information G1 and G2, to the in-vehicle relay device 101 (step ST305), and waits for the reception of new service request information S1 from the resource management server 170 (NO in step ST301).

[0288] FIG. 15 is a flowchart defining an example of an operation procedure when an edge server according to an embodiment of the present disclosure performs a process of stopping the execution of a service.

[0289] Referring to FIG. 15, first, the edge server 180 waits for the reception of stop request information from the resource management server 170 (NO in step ST401).

[0290] Then, when the edge server 180 receives the stop request information from the resource management server 170 (YES in step ST401), it stops the execution of the service S (step ST402).

[0291] FIGS. 16 and 17 are flowcharts defining an example of an operation procedure when an in-vehicle relay device according to an embodiment of the present disclosure performs a determination process.

[0292] Referring to FIGS. 16 and 17, first, the in-vehicle relay device 101 waits for the reception of resource information from the resource management server 170 (NO in step ST501).

[0293] Next, when the in-vehicle relay device 101 receives the resource information from the resource management server 170 (YES in step ST501), it performs a determination process of determining whether to transmit a resource request to the resource management server 170 (step ST502).

[0294] Next, when the in-vehicle relay device 101 determines to transmit a resource request (YES in step ST503), it performs a determination process of determining the resource R to be used for the execution of the service S (step ST504).

[0295] Next, the in-vehicle relay device 101 determines the resource R to be used to perform service S, and then calculates the usage period U of the resource R based on the planned route E of vehicle 1 and the desired period for which service S is to be provided (step ST505).

[0296] Next, the in-vehicle relay device 101 sends allocation request information, which includes a resource request, usage period information indicating the calculated usage period U, and the vehicle ID of vehicle 1, to the resource management server 170 (step ST506).

[0297] Next, the in-vehicle relay device 101 awaits the reception of allocationable or unallocable information from the resource management server 170 (NO in step ST507).

[0298] Then, when the in-vehicle relay device 101 receives allocationable or allocationless information from the resource management server 170 (YES in step ST507), it transmits the received allocationable or allocationless information to the navigation device 202C (step ST508).

[0299] Next, the in-vehicle relay device 101 awaits the reception of data request information or control information from the edge server 180 (NO in step ST509 or NO in step ST511).

[0300] Then, when the in-vehicle relay device 101 receives data request information from the edge server 180 (YES in step ST509), it transmits vehicle information of the type indicated by the received data request information to the edge server 180 (step ST510), and waits to receive new data request information or control information from the edge server 180 (NO in step ST509 or NO in step ST511).

[0301] Furthermore, when the in-vehicle relay device 101 receives control information from the edge server 180 (YES in step ST511), it uses the received control information to control the in-vehicle equipment 202. For example, as described above, the in-vehicle relay device 101 transmits the received control information to the in-vehicle equipment 202 (step ST512).

[0302] Next, the in-vehicle relay device 101 determines whether or not the termination conditions for terminating the provision of service S are met (step ST513).

[0303] Then, if the in-vehicle relay device 101 determines that the termination conditions are met (YES in step ST513), it sends a release request information to the resource management server 170, including a request to release resource R and the vehicle ID of vehicle 1 (step ST514), and waits to receive new resource information from the resource management server 170 (NO in step ST501).

[0304] On the other hand, if the in-vehicle relay device 101 determines that it will not send a resource request (NO in step ST503), it waits for new resource information to be received from the resource management server 170 (NO in step ST501).

[0305] Furthermore, if the in-vehicle relay device 101 determines that the termination conditions are not met (NO in step ST513), it waits for new data request information or new control information to be received from the edge server 180 (NO in step ST509 or NO in step ST511).

[0306] In the communication system 501 according to the embodiment of this disclosure, the in-vehicle relay device 101 is configured to perform decision processing using resource information and route information, but it is not limited to this configuration. The in-vehicle relay device 101 may be configured to perform decision processing using resource information without using route information. Alternatively, the in-vehicle relay device 101 may be configured to perform decision processing using resource information and other information besides resource information and route information.

[0307] Furthermore, while the communication system 501 according to the embodiment of this disclosure is configured such that the in-vehicle relay device 101 determines multiple resources R to be used sequentially using resource information and route information, it is not limited to this configuration. The in-vehicle relay device 101 may also be configured to determine a single resource R using resource information and route information.

[0308] Furthermore, in the communication system 501 according to the embodiment of this disclosure, the in-vehicle relay device 101 is configured to determine the usage period U of each resource R based on route information, but it is not limited to this. The in-vehicle relay device 101 may also be configured to determine the usage period U of each resource R based on information other than route information. The in-vehicle relay device 101 may also be configured not to determine the usage period U of each resource R. In this case, for example, the resource management server 170 allocates resource R on the premise that vehicle 1 will use resource R for the entire period of the desired provision period.

[0309] Furthermore, in the communication system 501 according to the embodiment of this disclosure, the in-vehicle relay device 101 is configured to acquire resource information including type information, service area information, and performance information from the resource management server 170, but it is not limited to this. The resource information may include a portion of the type information, service area information, and performance information. In addition, the resource information may include other information relating to resource R instead of, or in addition to, a portion or all of, the type information, service area information, and performance information.

[0310] Furthermore, while the communication system 501 according to the embodiment of this disclosure is configured such that the resource management server 170 allocates resources R according to multiple service provision areas A, it is not limited to this configuration. The resource management server 170 may also be configured to allocate a common resource R across the entire planned route E of vehicle 1.

[0311] Furthermore, in the communication system 501 according to the embodiment of this disclosure, the resource management server 170 is configured to reallocate resource R when it receives a new resource request from another vehicle 1, but it is not limited to this configuration. The resource management server 170 may also be configured not to reallocate resource R, but to allocate available resources, i.e., usable resources R, to other vehicle 1.

[0312] Furthermore, in the communication system 501 according to the embodiment of this disclosure, the priority when the resource management server 170 reallocates resource R is determined according to the type of vehicle 1, the type of service S provided to vehicle 1, or the load status of vehicle 1, but it is not limited to this. For example, the priority may be determined according to the length of the usage period U of resource R, etc.

[0313] Furthermore, while the communication system 501 according to the embodiment of this disclosure is configured such that the in-vehicle relay device 101 performs decision processing and resource request transmission processing, it is not limited to this configuration. A device other than the in-vehicle relay device 101 in the in-vehicle network 401 may perform decision processing and resource request transmission processing.

[0314] Furthermore, although the communication system 501 according to the embodiment of this disclosure is described as having separate devices for the resource management server 170 and the edge server 180, it is not limited to this. The edge server 180 may be included in the resource management server 170.

[0315] Furthermore, some or all of the functions of the resource management server 170 according to the embodiment of this disclosure may be provided by cloud computing. That is, the resource management server 170 according to the embodiment of this disclosure may be a cloud server composed of multiple servers.

[0316] Furthermore, some or all of the functions of the edge server 180 according to the embodiment of this disclosure may be provided by cloud computing. That is, the edge server 180 according to the embodiment of this disclosure may be a cloud server composed of multiple servers.

[0317] [Differentiation] In the communication system 501 according to the embodiment of this disclosure, the in-vehicle relay device 101 is configured to perform the decision processing, but the system is not limited to this. The resource management server 170 may also be configured to perform the decision processing.

[0318] Figure 18 shows the configuration of a modified example of the resource management server according to the embodiment of the present disclosure. Referring to Figure 18, the resource management server 170A further includes a determination unit 22 compared to the resource management server 170 shown in Figure 4. Some or all of the communication unit 31, distribution unit 32, resource allocation unit 33, resource release unit 34, and determination unit 22 are implemented by a processing circuit including, for example, one or more processors. The storage unit 35 is, for example, a non-volatile memory included in the processing circuit.

[0319] When the processing timing T for distribution processing arrives, the distribution unit 32 distributes resource information to each vehicle 1, including type information and service area information, but excluding performance information of each edge server 180.

[0320] Figure 19 shows a modified configuration of the in-vehicle relay device according to an embodiment of the present disclosure. Referring to Figure 19, the processing unit 12A in the in-vehicle relay device 101A does not include the determination unit 22, unlike the processing unit 12 shown in Figure 3.

[0321] When the service management unit 21 receives resource information from the resource management server 170 via the TCU 202A and relay unit 11, it obtains route information from the navigation device 202C as described above.

[0322] Then, if the service management unit 21 finds that the type of service S indicated by the acquired route information is included in the type information received from the resource management server 170, it sends decision request information, which includes the route information and a request notification indicating that it is requesting a decision on the resource R to be used to execute the service S, to the resource management server 170 via the relay unit 11 and TCU202A.

[0323] Referring again to Figure 18, in the resource management server 170, the communication unit 31 outputs the decision request information received from the in-vehicle relay device 101 to the decision unit 22.

[0324] For example, the decision unit 22 performs a decision process to determine multiple resources R to be used to execute the service S, based on the route information included in the decision request information received from the communication unit 31 and the service area information stored in the storage unit 35.

[0325] Specifically, for example, when the decision unit 22 receives decision request information from the communication unit 31, it uses the route information included in the decision request information and the service area information stored in the storage unit 35 to determine, as described above, a number of resources R to be used during the desired service period indicated by the route information.

[0326] Furthermore, for example, the decision unit 22 determines the usage period U of each resource R based on the planned route E of the vehicle 1.

[0327] More specifically, for example, when the decision unit 22 receives decision request information from the communication unit 31, it calculates the usage period U of each resource R to be used, as described above, based on the route information included in the decision request information.

[0328] The determination unit 22 then outputs determination information to the resource allocation unit 33, which shows the multiple resources R determined in the determination process and the calculated usage period U for each resource R.

[0329] For example, the resource allocation unit 33 allocates the resource R determined by the determination unit 22.

[0330] Specifically, for example, when the resource allocation unit 33 receives decision information from the decision unit 22, it refers to the resource management table in the storage unit 35 to identify the resource R and the usage rate C corresponding to the usage period U of the resource R, as indicated by the decision information. The resource allocation unit 33 then checks whether the identified usage rate C is less than the threshold Th11.

[0331] Figures 20 and 21 are flowcharts illustrating an example of the operation procedure when a modified version of the resource management server according to the embodiment of this disclosure allocates resources. Figures 20 and 21 show the operation when the resource management server 170A allocates resource R to one vehicle 1. For example, the resource management server 170A performs the processes shown in Figures 20 and 21 in parallel for each vehicle 1.

[0332] Referring to Figures 20 and 21, first, the resource management server 170A waits for the receipt of decision request information from the in-vehicle relay device 101 (NO in step ST601).

[0333] Then, when the resource management server 170A receives decision request information from the in-vehicle relay device 101 (YES in step ST601), it performs a decision process to determine multiple resources R to be used to execute service S based on the route information included in the decision request information and the provision area information stored in the storage unit 35 (step ST602).

[0334] Next, the resource management server 170A determines which resources R to use and calculates the usage period U for each resource R based on the planned route E of vehicle 1 and the desired provision period indicated by the route information included in the received decision request information (step ST603).

[0335] The process from step ST604 to step ST612 is the same as the process from step ST202 to step ST210 shown in Figures 12 and 13.

[0336] The embodiments described above should be considered in all respects to be illustrative and not restrictive. The scope of the present invention is indicated by the claims rather than the foregoing description, and all modifications within the meaning and scope equivalent to the claims are intended to be included.

[0337] Each process (each function) of the above-described embodiment is implemented by a processing circuit including one or more processors. The processing circuit may consist of one or more memories, various analog circuits, various digital circuits, and other integrated circuits in addition to the one or more processors. The one or more memories store programs (instructions) that cause the one or more processors to execute each of the above processes. The one or more processors may execute each of the above processes according to the programs read from the one or more memories, or they may execute each of the above processes according to logic circuits that have been pre-designed to execute each of the above processes. The processors may be various processors suitable for computer control, such as CPUs, GPUs (Graphics Processing Units), DSPs (Digital Signal Processors), FPGAs (Field Programmable Gate Arrays), and ASICs (Application Specific Integrated Circuits). Furthermore, the physically separated multiple processors may cooperate with each other to execute each of the above processes. For example, the processors installed in each of several physically separate computers may cooperate with each other via a network such as a LAN (Local Area Network), WAN (Wide Area Network), and the Internet to perform the above processes. The program may be installed in the memory via the network from an external server device, or it may be distributed on a recording medium such as a CD-ROM (Compact Disc Read Only Memory), DVD-ROM (Digital Versatile Disk Read Only Memory), and semiconductor memory, and then installed in the memory from the recording medium.

[0338] The above description includes the following features. [Note 1] A method for determining resources in an in-vehicle device, Steps include obtaining resource information about resources outside the vehicle, The steps include: performing a decision process to determine the resources to be used to perform services related to the vehicle based on the acquired resource information; A resource determination method comprising the step of transmitting the determined resource request to an external device located outside the vehicle.

[0339] [Note 2] Equipped with a processing circuit, The aforementioned processing circuit is Obtain resource information regarding resources outside the vehicle, Based on the acquired resource information, a decision process is performed to determine the resources to be used to perform services related to the vehicle. An in-vehicle device that transmits the determined resource request to an external device located outside the vehicle.

[0340] [Note 3] A resource management method for a management device installed on the outside of a vehicle, A resource management method comprising the step of allocating resources located outside the vehicle to be used for performing services relating to the vehicle.

[0341] [Note 4] A control device installed on the outside of a vehicle, Equipped with a processing circuit, The aforementioned processing circuit is A management device that allocates resources located outside the vehicle, which are used to perform services related to the vehicle.

[0342] [Note 5] In-vehicle equipment and Equipped with a management device, The in-vehicle device performs a decision process to determine the resources to be used to perform services related to the vehicle, based on resource information relating to resources outside the vehicle. The in-vehicle device transmits a resource request to the management device to request the determined resource. The management device is a communication system that allocates resources based on the resource requests received from the in-vehicle device. [Explanation of Symbols]

[0343] 1 vehicle 11 Relay section 12,12A Processing Unit 13,35,43 Storage section 21 Service Management Department 22,36 Decision Section 23 Control Unit 31,41 Communications Department 32 Distribution Department 33 Resource Allocation Section 34 Resource Release Section 42 Service Execution Unit 51 CAN bus 101,101A Vehicle-mounted relay device 170,170A Resource Management Server 180 Edge Servers 202 Automotive equipment 301 In-vehicle systems 401 In-vehicle network 501 Communication System

Claims

1. A resource acquisition unit that acquires resource information regarding resources outside the vehicle, A decision unit performs a decision process to determine the resources to be used to perform services related to the vehicle, based on the resource information acquired by the acquisition unit. An in-vehicle device comprising: a transmission unit that transmits the resource request determined by the determination unit to an external device located outside the vehicle.

2. The acquisition unit further acquires route information indicating the planned route of the vehicle, The in-vehicle device according to claim 1, wherein the determination unit performs the determination process based on the route information acquired by the acquisition unit.

3. The in-vehicle device according to claim 2, wherein the determination unit determines a plurality of resources to be used in order based on the resource information and the route information.

4. The determination unit determines a plurality of resources in the determination process, The determination unit determines the usage period for each resource to be used based on the route information. The in-vehicle device according to claim 2 or 3, wherein the transmitting unit transmits information indicating the usage period of each resource determined by the determination unit to the external device.

5. The in-vehicle device according to claim 1 or 2, wherein the resource information includes at least one of the following: information indicating the types of services that can be performed, information indicating the areas in which the services are provided, and information indicating the performance of the device that performs the services.

6. A control device installed on the outside of a vehicle, A management device comprising a resource allocation unit that allocates resources located outside the vehicle, which are used to perform services related to the vehicle.

7. The vehicle determines the resources to be used to perform the service, and sends a resource request to the management device to request the determined resources. The aforementioned control device further, The vehicle is equipped with a receiving unit that receives the resource request from the vehicle, The management device according to claim 6, wherein the resource allocation unit performs the allocation based on the resource request received by the receiving unit.

8. The management device according to claim 6 or 7, wherein the resource allocation unit determines the allocation according to the area in which the multiple services corresponding to the multiple resources are provided.

9. The management device according to claim 7, wherein the resource allocation unit reallocates the resources based on the planned travel route of the other vehicle when the receiving unit receives a new resource request from the other vehicle.

10. The management device according to claim 7, wherein the resource allocation unit reallocates the resources according to priority when the resources are insufficient and the receiving unit receives a new resource request from another vehicle.

11. The management device according to claim 10, wherein the priority is determined according to the type of vehicle.

12. The management device according to claim 10, wherein the priority is determined according to the type of service provided to the vehicle.

13. The management device according to claim 10, wherein the priority is determined according to the load status of the vehicle.

14. The aforementioned control device further, The system includes a determination unit that performs a determination process to determine the resources to be used to execute the service, The management device according to claim 6, wherein the resource allocation unit performs the allocation of the resources determined by the determination unit.

15. The determination unit determines a plurality of resources in the determination process, The management device according to claim 14, wherein the determination unit determines the usage period of each resource based on the planned route of the vehicle.

16. A resource determination program used in an in-vehicle device, Computers, A resource acquisition unit that acquires resource information regarding resources outside the vehicle, A decision unit performs a decision process to determine the resources to be used to perform services related to the vehicle, based on the resource information acquired by the acquisition unit. A transmission unit transmits the resource request determined by the determination unit to an external device located outside the vehicle. A resource determination program to function as such.

17. A resource management program used in a management device installed on the outside of a vehicle, Computers, Resources located outside the vehicle, which are allocated by a resource allocation unit that allocates the resources used to perform services related to the vehicle. A resource management program designed to function as such.

Images