Centralized device and application distribution method

Abstract

In one embodiment of the present disclosure, in the center device (3), in the application ledger (33), a plurality of authentication applications and respective allocation conditions to vehicles of the respective authentication applications are registered. In the vehicle individual ledger (32), identification information of each vehicle and allocation completion information related to the authentication applications that have been allocated to the vehicles are registered. The application allocation function section (312) selects a plurality of vehicles that satisfy the allocation conditions as a candidate group of target vehicles, and determines a group of target vehicles that becomes a target of allocation of a new authentication application from the candidate group of target vehicles based on the allocation completion information. The application allocation function section (312) allocates the new authentication application to the determined group of target vehicles.

Description

[0001] Cross-reference of related applications

[0002] This application is based on Japanese Application No. 2024-51546, filed on March 27, 2024, the contents of which are incorporated herein by reference. Technical Field

[0003] This disclosure relates to a central apparatus and method for distributing applications to multiple vehicles. Background Technology

[0004] For example, Patent Document 1 discloses a technology for providing mobility services in which a vehicle is accessed via a network, various applications utilizing the functions and resources of the vehicle are executed, and the service operator obtains the execution results.

[0005] Existing technical documents

[0006] Patent documents

[0007] Patent document 1: Japanese Patent Application Publication No. 2023-117140.

[0008] As a similar service to the one described above, a service is envisioned that, for example, assigns an application under development to a vehicle, executes the application without the awareness of the vehicle's occupants, obtains the execution result, and utilizes it for program development. Such an application is referred to as a "verification application."

[0009] In this scenario, there are various constraints on the number of verification applications that can be assigned to a vehicle. Therefore, when assigning verification applications to a vehicle, the aforementioned constraints of each verification application must be considered during the selection process. Summary of the Invention

[0010] This disclosure was made in view of the above circumstances, and its purpose is to provide a central device and application allocation method capable of effectively allocating verification applications to multiple vehicles according to various conditions.

[0011] According to the central device of this disclosure, the verification application registration unit registers multiple verification applications and their respective allocation conditions to the vehicles. The allocated application registration unit registers identification information for each vehicle and allocation completion information related to verification applications already allocated to those vehicles. The candidate group selection unit selects multiple vehicles meeting the allocation conditions as target vehicle candidate groups. The vehicle group determination unit, based on the allocation completion information, determines the target vehicle group from the target vehicle candidate groups to be allocated a new verification application. The allocation unit allocates the new verification application to the determined target vehicle group. With this configuration, when a new verification application needs to be allocated to a vehicle, the central device can effectively determine the vehicle group to be allocated based on the allocation conditions of the verification application and the allocation completion information related to the allocated verification applications.

[0012] Furthermore, according to the central device of this disclosure, the vehicle group determination unit determines vehicles that do not have assigned verification applications operating under the same driving conditions as the assigned verification applications as the target vehicle group. Therefore, verification applications operating under different driving conditions can be assigned to a single vehicle. Thus, verification of each application can be performed efficiently. Attached Figure Description

[0013] The foregoing objects, as well as other objects, features, or advantages of this disclosure, will become more apparent from the following detailed description with reference to the accompanying drawings. These drawings are as follows:

[0014] Figure 1 This is a diagram illustrating the structure of the verification system applied in the first embodiment.

[0015] Figure 2 It is a functional block diagram representing the structure of an onboard device mounted on a vehicle.

[0016] Figure 3 This is a functional block diagram representing the structure of the central device.

[0017] Figure 4 It is a diagram that represents an overview of the application verification system through images.

[0018] Figure 5 This is a flowchart illustrating the processing content of the central device.

[0019] Figure 6 This is a schematic diagram of a terminal device that shows the distribution of vehicles in various allocation areas.

[0020] Figure 7 This is a schematic diagram of a terminal device displaying the search status of vehicles that meet the allocation criteria.

[0021] Figure 8This is a schematic diagram of a terminal device displaying the verification status of each verification application and the allocation and reservation status of new verification applications.

[0022] Figure 9 This is a diagram illustrating an example of the runtime scenarios for application categories A through D.

[0023] Figure 10 This diagram illustrates an example of an application that has been assigned within a specified period for vehicle individual numbers No. 1 to 4.

[0024] Figure 11 This diagram illustrates an example of the operational scenarios for application categories A through E allocated in the second embodiment.

[0025] Figure 12 This diagram illustrates an example of an application that has been assigned within a specified period for vehicle individual numbers No. 1 to 5.

[0026] Figure 13 This diagram illustrates an example of power consumption under the respective operating scenarios of application categories F to I in the third embodiment.

[0027] Figure 14 This is a diagram showing an example of the total power consumption of the applications that have been allocated for a specified period for vehicle individual numbers No. 5 to 7.

[0028] Figure 15 This is a diagram illustrating an example of GPU occupancy in the runtime scenarios of application categories J to M in the fourth embodiment.

[0029] Figure 16 This is a graph representing an example of the total GPU usage of applications that have been allocated during a specified period for vehicle individual numbers No. 5 to 7. Detailed Implementation

[0030] (First Implementation)

[0031] The first embodiment will be described below. Figure 1 The application verification system 1 shown includes multiple vehicle-mounted devices 2, a central device 3, and a system administrator terminal device 4. The vehicle-mounted devices 2 are mounted on the vehicle 10 and act as intermediaries between the vehicle 10 and the central device 3, performing vehicle information collection and vehicle control. The central device 3 communicates with the vehicle-mounted devices 2 via a wide area communication network (NW) to manage a database storing vehicle information provided by the vehicle-mounted devices 2, and provides users with interfaces to access the database and the vehicle-mounted devices 2. Users are also referred to as third parties, including application developers, application users, and users of the computing system.

[0032] The system administrator terminal device 4 is a terminal device used by the system administrator of the application verification system 1. Hereinafter, it is simply referred to as terminal device 4. Terminal device 4 accesses the central device 3 using the graphical user interface (hereinafter, GUI) provided by the central device 3.

[0033] In this embodiment, within the application verification system 1, the structure for enabling the vehicle 10 to execute various programs by leasing the resources of the vehicle 10 equipped with the vehicle-mounted device 2 to a user will be described. Resources refer to CPU computing resources, cameras mounted on the vehicle, various sensors, and other equipment.

[0034] like Figure 2 As shown, the vehicle-mounted device 2 includes a communication unit 21, a vehicle information unit 22, a control unit 23, and a power supply unit 24. The communication unit 21 communicates wirelessly between the control unit 23 and the central device 3 via a wide area communication network (NW). The vehicle information unit 22 connects to various vehicle-mounted devices via the vehicle's in-vehicle network and obtains various information from these devices. The control unit 23 includes a GPU (Graphics Processing Unit) 221, a CPU 222, a ROM 223, and a RAM 224. The GPU 221 is an IC that performs rendering processing when display units such as a display screen (not shown) in the vehicle 10 display information related to driving conditions and driving operations, such as images and symbols. The GPU 221 further executes machine learning models included in the application. Therefore, the GPU 221 is a control device that enables the application to operate.

[0035] Unless otherwise specified, "application," "assignment application," or "software" all refer to "verification application." Figure 3 As shown, the central device 3 includes a communication unit 31, an application ledger 32, and a vehicle individual ledger 33. The communication unit 31 communicates with the vehicle-mounted device 2 via wireless communication through a wide area communication network (NW). The data collection function unit 311 of the communication unit 31 collects the vehicle's historical data of movement and the execution result data of the verification application. The application allocation function unit 312, corresponding to the allocation unit, allocates the verification application to the vehicle.

[0036] The application ledger 32 contains items such as the category of the verification application and the allocation conditions to each vehicle 10, the operating scenario corresponding to the driving conditions of each verification application in the vehicle 10, the power consumption of each verification application in the vehicle 10, GPU utilization, and other evaluation metrics. The application ledger 32 corresponds to the verification application registration department. The vehicle individual ledger 33 contains items such as the individual identification number of each vehicle, vehicle model, historical action data collected from each vehicle 10 by the data collection function unit 311, the category of the application allocated to the vehicle 10, and the operating period. The vehicle individual ledger 33 corresponds to the application allocation registration department.

[0037] Next, the function of this embodiment will be explained. Figure 4 This diagram illustrates the outline of an application verification system. Features such as human characteristics, vehicle status, and environmental conditions corresponding to the operating scenarios are extracted from market data, and modeled data is collected. Next, based on the models of each feature, vehicles with the functionalities required for verification are selected; that is, vehicles meeting the allocation conditions for the verification application are selected. Then, the verification application is assigned to the selected vehicles. The allocation conditions are set by the operator or user to suit the verification vehicles for the application. For example, the allocation conditions for driver support software include: driving in high-traffic areas, driving at night, having driver monitoring functions, and a history of detecting driver drowsiness, etc.

[0038] In vehicles where verification applications are assigned, the applications are executed in a so-called shadow mode without the awareness of the vehicle occupants. The results of this execution may include, for example, the application of machine learning (ML). This machine learning can be performed on either the vehicle side or the central device side. In the example shown in the diagram, when the verification application using a rain sensor is running, the scenario where the rain sensor can be replaced by another sensor is verified as a "reduction scenario." During this process, the learning model and the triggering conditions for data collection are updated; if this update is detected, the verification application is reassigned to the target vehicle. The following cycle of repeatedly executing machine learning, updating the learning model and triggering conditions, and reassigning the verification application is performed during the specified verification period.

[0039] like Figure 5 As shown, in the central device 3, the system administrator operates the terminal device 4 to register the verification applications assigned to the vehicle 10 in the application ledger 32 (S1), and register the conditions for assigning each verification application to the vehicle 10 (S2). Then, in the vehicle individual ledger 33, vehicles 10 that meet the assignment conditions of each verification application are searched as target vehicles (S3). As a result of this search, vehicles that become assignment candidates are determined (S4). Steps S3 and S4 correspond to the candidate group selection unit.

[0040] Next, for each vehicle 10 that is a candidate for allocation, the status of resources is checked (S5). Here, when a new verification application is allocated, it is checked whether the verification application can be allocated to vehicle 10 and made to operate. The status that the verification application can be allocated to vehicle 10 and made to operate is defined as "resources are available". Specific examples of this are described below.

[0041] Then, it is determined whether the number of available vehicles 10 in the resources is greater than or equal to the number of verification applications that need to be assigned (S6). If the former is greater than or equal to the latter (Yes), a verification application is assigned (S7). On the other hand, if the former is less than the latter (No), the verification application is set to an assignment reservation state (S8). This state is maintained until, for example, other verification applications are deleted from the vehicle 10 side, thereby creating a resource vacancy. Steps S5 and S6 correspond to the vehicle group decision unit.

[0042] When a verification application is assigned to vehicle 10, it executes in shadow mode as described above during the set verification period. By executing the verification application, execution results utilizing sensors mounted on vehicle 10 are acquired and accumulated during the verification period. When the verification period ends, the accumulated execution results are uploaded to central device 3. In this way, the execution result data of the verification application collected by central device 3 is used for the development of the verification application, etc. Furthermore, the verification period is also referred to as the running period.

[0043] Figure 6 This is a schematic diagram of the screen in the GUI of the terminal device 4, showing the distribution status of vehicles 10 in various locations in the allocation area centered on the Chubu region of Japan, based on the selected allocation software, model category / conditions, vehicle search start / end date, vehicle type, etc. Figure 7 It is the same schematic diagram, showing the retrieval status of vehicle 10 that meets the allocation criteria. Figure 8 This indicates the verification status of each verification application and the allocation reservation status of a new verification application. In the diagram, "Assignment Application" refers to the verification application.

[0044] Figure 9 This is an example of the operational scenarios for application categories A through D. For example, A is an application associated with an anti-theft function that operates while vehicle 10 is parked. B is an application associated with functions such as interior lights that operate when an accessory switch of vehicle 10 is turned on. C is an application associated with an autonomous driving function that operates while vehicle 10 is in motion. D is an application associated with the opening and closing of vehicle doors that operate while vehicle 10 is parked.

[0045] As for the operating scenarios related to these, there are "parking" and "driving," and below them are "main power off" and "main power on," and below that, "accessory power off" and "accessory power on." The on / off state of the main power corresponds to the on / off state of the ignition switch. Application A's operating scenario is "accessory power off," application B's is "accessory power on," application C's is "main power on," and application D's is "parking."

[0046] Figure 10 This refers to an example of an application that has been assigned within the specified period for the identification information of vehicle 10, namely, No. 1 to 4 as individual numbers. For example, in No. 1, since application A, whose operating scenario is "accessory power off," has already been assigned, application B or C, whose operating scenario does not conflict, can be newly assigned. Each application's operating period, verified within vehicle 10, is determined during assignment, and this operating period is monitored by the central device 3. When the operating period on vehicle 10 is changed, communication occurs between the on-board device 2 and the central device 3 to achieve synchronization, thus enabling the central device 3 to monitor the change in period.

[0047] As described above, according to this embodiment, in the central device 3, multiple verification applications and their respective allocation conditions to vehicles 10 are registered in the application ledger 32. The vehicle individual ledger 33 registers the identification information of each vehicle 10 and allocation completion information related to verification applications that have already been allocated to vehicles 10. The application allocation function unit 312 selects multiple vehicles 10 that meet the allocation conditions as a target vehicle candidate group, and from this target vehicle candidate group, determines the target vehicle group to which a new verification application will be allocated based on the allocation completion information. The application allocation function unit 312 allocates the new verification application to the determined target vehicle group. With this configuration, when a new verification application needs to be allocated to a vehicle 10, the vehicle group to which the application will be allocated can be effectively determined based on the allocation conditions of the verification application and the allocation completion information related to the allocated verification applications.

[0048] Furthermore, the application allocation function unit 312 identifies vehicles 10 that do not have allocated verification applications that run in the same scenario as the assigned verification application as the target vehicle group. Therefore, verification applications that run under different driving conditions can be allocated to a single vehicle 10. Thus, verification of each application can be performed effectively.

[0049] (Second Implementation)

[0050] Hereinafter, the same symbols will be used to mark the parts that are the same as in the first embodiment, and the descriptions will be omitted. The different parts will be described. In the second embodiment, the vehicle 10 is indicated to be an electric vehicle or a hybrid electric vehicle. Figure 11 Applications A through D shown are the same as in the first embodiment. Application E is a specialized application for charging the driving battery of an electric vehicle, such as a comfort function while waiting for charging. In this case, in the application's operating scenario, there is a distinction between "charging" and "charging disconnected" in the "parking" state.

[0051] Figure 12 This example illustrates an application where allocation is completed within a specified period for individual vehicle numbers No. 1 to No. 5 of vehicle 10. In vehicle No. 1, application A indicates allocation is complete; in vehicle No. 2, applications A and C indicate allocation is complete; in vehicle No. 3, application B indicates allocation is complete; in vehicle No. 4, application D indicates allocation is complete; and in vehicle No. 5, application E indicates allocation is complete. In this case, for vehicle No. 5, application C can be added to indicate allocation completion.

[0052] (Third Implementation)

[0053] The third embodiment describes a situation where the power consumption of each application is considered as an object of limiting the resources on the vehicle 10 side. Figure 13 Applications F to I shown are, for example, applications associated with the anti-theft function in the same way as application A. When these applications F to I are executed in the "Accessory Power Off" scenario, the power consumption is 10mW to 40mW.

[0054] like Figure 14 As shown, in vehicle 10 No. 5, F and G are used to complete the allocation; in vehicle 10 No. 6, H is used to complete the allocation; and in vehicle 10 No. 7, F and H are used to complete the allocation. In these vehicles 10 No. 5 to No. 7, the maximum allowable power consumption when "accessory power is disconnected" is set to, for example, 60mW. For example, in vehicle 10 No. 6, a power consumption of 30mW is used to complete the allocation using H; therefore, both F and I can be used for additional allocation.

[0055] (Fourth Implementation)

[0056] The fourth embodiment describes the case where the utilization rate of GPU221 is considered as an object that limits the resources on the vehicle 10 side. Figure 15 Applications J to M shown are, for example, objects associated with the autonomous driving function in the same way as application C. When these applications J to M are executed in the "parking" or "driving" scenarios under the "main power on" condition, the utilization rate of GPU221 is 10% to 40%.

[0057] like Figure 16As shown, in vehicle 10 No. 5, J and K are allocated; in vehicle 10 No. 6, L is allocated; and in vehicle 10 No. 7, J and L are allocated. In these vehicles 10 No. 5 through 7, the upper limit of GPU 221 utilization is set to, for example, 50%. For example, in vehicle 10 No. 6, L is allocated with a utilization rate of 30%, therefore both J and M can be allocated through additional allocation.

[0058] In addition to the inventions described in the scope of the patent claims, this application also includes the following inventions. [1]

[0060] A central device (3) that distributes applications to multiple vehicles (10) includes:

[0061] The verification application registration unit (32) registers multiple verification applications and their respective allocation conditions to the vehicle when multiple applications that are objects of verification actions via physical machines in the vehicle are used as verification applications.

[0062] The application registration department (33) has completed the allocation process. This application registration department has registered the identification information of each vehicle and the allocation completion information related to the verification applications that have been allocated to the vehicles.

[0063] The candidate group selection unit (S4, S5) selects multiple vehicles that meet the allocation conditions as the target vehicle candidate group.

[0064] The vehicle group decision unit (S6, S7) determines, based on the allocation completion information, the target vehicle group from the target vehicle candidate group to be assigned to the new verification application; and

[0065] The distribution unit (312) distributes the new verification application to the target vehicle group. [2]

[0067] [1] The central device recorded, wherein the allocation completion information includes the driving status of the verification application used for allocation operating in the vehicle.

[0068] The vehicle group determination unit will determine the vehicles that have been assigned to the verification application but do not have the same driving conditions as the assigned verification application as the target vehicle group. [3]

[0070] [2] The central device described includes information on the power consumed when the application is running in the vehicle, including the allocation conditions and the allocation completion information.

[0071] The allocation completion information includes the upper limit of the allowable power consumption for each vehicle under various driving conditions.

[0072] The vehicle group determination unit will determine the target vehicle group as follows: the power consumed when all assigned verification applications and the assigned verification applications are running is below the upper limit value. [4]

[0074] The central device described in [2] or [3], wherein the vehicle is equipped with a GPU that enables the verification application to operate, the GPU being a graphics processing unit.

[0075] The allocation conditions and the allocation completion information include the GPU utilization rate when the application is running in the vehicle.

[0076] The allocation completion information includes the upper limit of the allowed usage rate for each vehicle under each driving condition.

[0077] The vehicle group determination unit will determine the target vehicle group as follows: the utilization rate is below the upper limit value when all assigned verification applications and all assigned verification applications are running. [5]

[0079] The central device described in any of [2] to [4], wherein the driving conditions include the vehicle being parked and in motion. [6]

[0081] The central device described in any of [2] to [5] includes the driving conditions when the ignition switch of the vehicle is turned on and off. [7]

[0083] The central device described in any of [2] to [6] includes the driving conditions when the accessory power of the vehicle is turned on and off. [8]

[0085] The central device described in any of [2] to [7], in the case that the vehicle is an electric vehicle.

[0086] The driving conditions include when the driving battery of the vehicle is charging and when charging is disconnected. [9]

[0088] An application allocation method for allocating applications to multiple vehicles (10), wherein the central device comprises:

[0089] The verification application registration unit (32) registers multiple verification applications and their respective allocation conditions to the vehicle when multiple applications that are objects of verification actions via a physical machine in the vehicle are used as verification applications; and

[0090] The application registration department (33) has completed the allocation process. This department registers the identification information of each vehicle and the allocation completion information related to the verification applications that have been allocated to the vehicles.

[0091] In the central device,

[0092] Select multiple vehicles that meet the allocation conditions as candidate groups of target vehicles (S4, S5).

[0093] Based on the allocation completion information, the object vehicle group that will be assigned to the new verification application is determined from the object vehicle candidate group (S6).

[0094] The new verification application is assigned to the target vehicle group (S7).

[0095] (Other implementation methods)

[0096] The verification of the application and its allocation conditions is not limited to the example.

[0097] Regarding the specific power consumption of each application and the maximum allowable values ​​on the vehicle side, these can be adjusted appropriately based on individual designs. The same applies to GPU utilization.

[0098] The third and fourth embodiments can also be applied to electric vehicles, etc.

[0099] This disclosure describes embodiments, but it should be understood that this disclosure is not limited to those embodiments or constructions. This disclosure includes various modifications and equivalent variations. Furthermore, various combinations and methods, including only one of these elements, or other combinations and methods including more than one element or the following, are all within the scope and spirit of this disclosure.

[0100] The means and / or functions provided by various devices can be provided through software stored in a physical memory device and a computer executing it, software only, hardware only, or a combination thereof. For example, when a control device is provided through electronic circuitry as hardware, it can be provided through digital circuitry or analog circuitry that includes a plurality of logic circuits.

[0101] The control unit and method described in this disclosure can also be implemented by a dedicated computer, which is provided by comprising a processor and memory programmed to perform one or more functions embodied in a computer program. Alternatively, the control unit and method described in this disclosure can also be implemented by a dedicated computer provided by comprising a processor composed of one or more dedicated hardware logic circuits. Alternatively, the control unit and method described in this disclosure can also be implemented by one or more dedicated computers, which are composed of a combination of a processor and memory programmed to perform one or more functions and a processor composed of one or more hardware logic circuits. Furthermore, the computer program can also be stored as instructions to be executed by the computer in a computer-readable non-volatile storage medium.

Claims

1. A central device (3) for distributing applications to multiple vehicles (10), characterized in that, have: The verification application registration unit (32) registers multiple verification applications and their respective allocation conditions to the vehicle when multiple applications that are objects of verification actions via physical machines in the vehicle are used as verification applications. The application registration department (33) has completed the allocation process. This application registration department has registered the identification information of each vehicle and the allocation completion information related to the verification applications that have been allocated to the vehicles. The candidate group selection unit (S4, S5) selects multiple vehicles that meet the allocation conditions as the target vehicle candidate group. The vehicle group decision unit (S6, S7) determines, based on the allocation completion information, the target vehicle group from the target vehicle candidate group to be assigned to the new verification application; and The distribution unit (312) distributes the new verification application to the target vehicle group.

2. The central device according to claim 1, characterized in that, The allocation completion information includes the driving status of the verification application used for allocation, which is operating in the vehicle. The vehicle group determination unit will determine the vehicles that have been assigned to the verification application but do not have the same driving conditions as the assigned verification application as the target vehicle group.

3. The central device according to claim 2, characterized in that, The allocation conditions and the allocation completion information include information verifying the power consumed when the application was running in the vehicle. The vehicle group determination unit determines the target vehicle group as follows: the power consumed when all assigned verification applications and the assigned verification applications are running is below the upper limit allowed under each driving condition of each vehicle.

4. The central device according to claim 2, characterized in that, The vehicle is equipped with a GPU, which is a graphics processing unit, to enable the verification application to function. The allocation conditions and the allocation completion information include the GPU utilization rate when the application is running in the vehicle. The vehicle group determination unit determines the target vehicle group as follows: the utilization rate is below the upper limit of the allowable utilization rate under each driving condition of each vehicle when all assigned verification applications and the assigned verification applications are running.

5. The central device according to any one of claims 2 to 4, characterized in that, The driving status includes the vehicle being parked and in motion.

6. The central device according to any one of claims 2 to 4, characterized in that, The driving conditions include when the vehicle's ignition switch is turned on and off.

7. The central device according to any one of claims 2 to 4, characterized in that, The driving conditions include when the vehicle's accessory power is turned on and off.

8. The central device according to any one of claims 2 to 4, characterized in that, In the case that the vehicle is an electric vehicle The driving conditions include when the driving battery of the vehicle is charging and when charging is disconnected.

9. An application allocation method for allocating applications to multiple vehicles (10), characterized in that, The central device includes: The verification application registration unit (32) registers multiple verification applications and their respective allocation conditions to the vehicle when multiple applications that are objects of verification actions via physical machines in the vehicle are used as verification applications. as well as The application registration department (33) has completed the allocation process. This department registers the identification information of each vehicle and the allocation completion information related to the verification applications that have been allocated to the vehicles. In the central device, Select multiple vehicles that meet the allocation conditions as candidate groups of target vehicles (S4, S5). Based on the allocation completion information, the object vehicle group that will be assigned to the new verification application is determined from the object vehicle candidate group (S6). The new verification application is assigned to the target vehicle group (S7).

Images