Vehicle, server, service provision system, and data transmission method

Abstract

A vehicle (10) that communicates with a server that provides connected services determines, when a change occurs in the traveling state of the vehicle on the basis of data indicating the traveling state of the vehicle, whether the number of transmissions or the data size of data transmitted from the vehicle (10) to a server (20) exceeds a threshold value. If the threshold value is exceeded, the vehicle (10) determines whether the transmitted data is classified into one of a first group relating to transmission periods, a second group relating to value changes, and a third group relating to travel distance intervals, on the basis of transmission conditions that must be satisfied to maintain the accuracy of the connected services. If it is determined that the data is classified into one of the first to third groups, the vehicle (10) transmits the data to the server (20) in accordance with the transmission conditions.

Description

Vehicle, server, service providing system, and data transmission method

[0001] The present invention relates to a vehicle, a server, a service providing system, and a data transmission method.

[0002] In recent years, connected services have become popular that support vehicle driving by installing sensors, cameras, etc. in vehicles, sending data about the condition of the vehicle and its surroundings to a server, and notifying the vehicle and user of the results of the analysis of that data.

[0003] However, transmitting all data generated while the vehicle is traveling to a server results in unnecessary communication and resource usage. Patent Document 1, for example, discloses a technology for reducing unnecessary communication and resource usage, which includes: "a storage determination unit that determines images to be stored from among a plurality of images captured by an imaging unit that captures the exterior of a moving body; and a condition determination unit that determines conditions for determining images to be stored. The storage determination unit determines images to be stored in accordance with the conditions determined by the condition determination unit. The condition determination unit determines, based on the speed of the moving body, at least one of the following conditions for determining images to be stored: (i) a condition related to the time interval from when an image is determined as an image to be stored until when the next image to be stored is determined; and (ii) a condition related to the distance traveled by the moving body from when an image is determined as an image to be stored until the next image to be stored is determined."

[0004] Japanese Patent Application Laid-Open No. 2020-80462

[0005] However, the conventional technology disclosed in the above-mentioned Patent Document 1 only targets image data and does not consider reducing unnecessary communication or resource usage for other types of data. Furthermore, the conventional technology disclosed in the above-mentioned Patent Document 1 has only two conditions for determining which images to save: a condition related to the interval between image saves and a condition related to the distance traveled by a moving object until the next image to save is determined. Therefore, the conventional technology disclosed in the above-mentioned Patent Document 1 may not be able to ensure sufficient accuracy of connected services.

[0006] The present invention has been made in consideration of the above circumstances, and aims to reduce unnecessary communication and resource usage in mobile communications in vehicles while ensuring sufficient accuracy of connected services.

[0007] One aspect of the present invention is a vehicle that communicates with a server that provides a connected service, the vehicle having a processor, a memory, and a storage unit, the storage unit storing transmission conditions for data indicating the vehicle's driving state when the data is transmitted from the vehicle to the server, the transmission conditions being the transmission conditions that must be met to maintain the accuracy of the connected service, the processor determining whether a change has occurred in the driving state based on the data, and if it is determined that a change has occurred in the driving state, determining whether the average value of the number of transmissions or the data size of the data transmitted from the vehicle to the server per predetermined time period has exceeded a threshold, and if it is determined that the number of transmissions or the average value has exceeded the threshold, determining based on the transmission conditions whether the data is classified into one of a first group related to the transmission period of the data, a second group related to changes in the value of the data, and a third group related to the distance traveled by the vehicle, and if it is determined that the data is classified into one of the first to third groups, transmitting the data to the server in accordance with the transmission conditions.

[0008] According to the present invention, in mobile communications in a vehicle, it is possible to reduce unnecessary communications and resource usage while ensuring sufficient accuracy of connected services.

[0009] 1 is a hardware configuration diagram of an overall system including a vehicle and a server according to embodiment 1. FIG. 2 is a functional block diagram of an overall system including a vehicle and a server according to embodiment 1. FIG. 3 is a flowchart showing overall processing of the overall system according to embodiment 1. FIG. 4 is a flowchart showing waste detection processing according to embodiment 1. FIG. 5 is a flowchart showing service requirement confirmation processing according to embodiment 1. FIG. 6 is a diagram showing an example of a service list table according to embodiment 1. FIG. 7 is a diagram showing an example of a required data item list table according to embodiment 1. FIG. 8 is a flowchart showing data item grouping processing according to embodiment 1. FIG. 9 is a diagram showing an example of a data item group table according to embodiment 1. FIG. 10 is a flowchart showing data transmission processing according to embodiment 1. FIG. 11 is a flowchart showing waste detection processing according to embodiment 2. FIG. 12 is a flowchart showing overall processing according to embodiment 3.

[0010] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. Note that the embodiments described below do not limit the invention according to the claims, and not all of the elements and combinations thereof described in the embodiments are necessarily essential to the solution of the invention.

[0011] In the following description, the programs that realize each processing function unit are executed by a processor to perform a predetermined process using a storage resource (e.g., a random access memory (RAM)) and / or a communication interface device (e.g., a port). The processor is, for example, a central processing unit (CPU). Therefore, the process executed by each processing function unit may be a process performed by a processor or a computer having that processor.

[0012] In the following description, identical or similar components are given the same reference numerals, and in later embodiments and modifications, their description may be omitted or only the differences may be described. Furthermore, when there are multiple identical or similar components, they may be described with the same reference numerals but with different subscripts. Furthermore, when there is no need to distinguish between these multiple components, the subscripts may be omitted. The number of each component may be singular or plural unless otherwise specified.

[0013] First Embodiment (Hardware Configuration of Overall System S Including Vehicle 10 and Server 20 According to First Embodiment) FIG. 1 is a hardware configuration diagram of an overall system S including a vehicle and a server according to a first embodiment.

[0014] The overall system S is configured to include a plurality of vehicles 10 and a server 20 that communicates with the vehicles 10. The overall system S is a connected service providing system that collects information about the driving conditions of each vehicle 10, including the conditions of each vehicle 10 and its surroundings, and generates and distributes distribution data for connected services to each vehicle 10 based on the collected information.

[0015] Each vehicle 10 has the configuration described below in common. However, each vehicle 10 may have a configuration other than that described below. Note that each vehicle 10 and server 2 may be configured from multiple devices rather than being a single device.

[0016] The vehicle 10 includes a CPU 11, a ROM (Read Only Memory) 12, which is a read-only storage device, a RAM 13, which is a readable and writable storage device, an in-vehicle communication unit 14, a vehicle storage unit 15, and sensors 16. The CPU 11 loads a program stored in the ROM 12 into the RAM 13 and executes it, thereby realizing a plurality of functions, which will be described later.

[0017] However, the functions of vehicle 10 may be realized by a field programmable gate array (FPGA), which is a rewritable logic circuit, or an application specific integrated circuit (ASIC), which is an integrated circuit for a specific application, other than the combination of CPU 11, ROM 12, and RAM 13. Vehicle 10 may also be provided with a combination different from the combination of CPU 11, ROM 12, and RAM 13, for example, a combination of CPU 11, ROM 12, RAM 13, and FPGA.

[0018] The in-vehicle communication unit 14 communicates with the server 20. The in-vehicle communication unit 14 is a communication module capable of wireless communication. The communication standards supported by the in-vehicle communication unit 14 are not particularly limited, but include, for example, 3G, 4G, and 5G. The in-vehicle communication unit 14 may be directly connected to the server 20, or may be connected to the server 20 via a base station provided by a telecommunications carrier or the Internet.

[0019] The vehicle memory unit 15 is a non-volatile storage device, such as a flash memory. The sensor 16 is one or more sensors that collect information about the surroundings of the vehicle 10 (host vehicle) on which the device is installed and measure the operation of the host vehicle. The sensor 16 is, for example, a camera, a laser range finder, or the like.

[0020] The server 20 has a CPU 21 which is a central processing unit, a ROM 22 which is a read-only storage device, a RAM 23 which is a readable and writable storage device, a server communication unit 24, and a server storage unit 25. The CPU 21 deploys a program stored in the ROM 22 into the RAM 23 and executes it, thereby realizing a plurality of functions which will be described later.

[0021] However, the functions of the server 20 may be realized by an FPGA or an ASIC instead of the combination of the CPU 21, the ROM 22, and the RAM 23. The server 20 may also have a combination of configurations different from the combination of the CPU 21, the ROM 22, and the RAM 23, for example, a combination of the CPU 21, the ROM 22, the RAM 23, and an FPGA.

[0022] The server communication unit 24 communicates with the in-vehicle communication unit 14. The server communication unit 24 may communicate directly with the in-vehicle communication unit 14 or may communicate via another device, such as a base station of a telecommunications carrier or another communication device. The server storage unit 25 is a non-volatile storage device, such as a hard disk drive (HDD) or a solid state drive (SSD).

[0023] (Functional Configuration of Overall System S Including Vehicle 10 and Server 20 According to First Embodiment) FIG. 2 is a functional block diagram of an overall system S including the vehicle 10 and server 20 according to the first embodiment.

[0024] (Configuration of Vehicle 10) The vehicle 10 includes a data acquisition unit 111, a data recording unit 112, a service management unit 113, a service execution unit 114, a data management unit 115, and a data transmission / reception unit 116.

[0025] The data acquisition unit 111 acquires data generated by sensors, cameras, and the like attached to the vehicle 10 through in-vehicle communication such as a Controller Area Network (CAN). The data recording unit 112 records the data related to the vehicle 10 acquired by the data acquisition unit 111 in the vehicle storage unit 15.

[0026] The service management unit 113 manages connected services that can be used by a user of the vehicle 10. The "user" here refers to the driver or passenger of the vehicle 10.

[0027] The service execution unit 114 executes the connected service managed by the service management unit 113. For example, if the connected service is a service that recommends the shortest route based on road conditions, the service execution unit 114 notifies the navigation system of information about the shortest route based on the service information distributed from the server 20.

[0028] The data management unit 115 manages data indicating the driving state of the vehicle 10 used in connected services acquired by the data acquisition unit 111. The data recording unit 112 manages which services use each data item recorded in the vehicle storage unit 15, etc.

[0029] The data transmitter / receiver 116 transmits the data stored in the vehicle storage unit 15 to the server 20 via the in-vehicle communication unit 14 in accordance with predetermined rules. The data transmitter / receiver 116 also receives service information related to the connected service executed by the service execution unit 114 from the server 20.

[0030] (Configuration of Server 20) The server 20 has a vehicle management unit 211, a service management unit 212, a data analysis unit 213, a service generation unit 214, a user management unit 215, and a service distribution unit 216. The vehicle management unit 211 manages all vehicles 10 that receive connected services provided by the server 20. For example, when subscribing to "Service A" provided by the server 20, information such as the vehicle IDs of all users registered to receive the service is managed.

[0031] The service management unit 212 manages the content of the connected services provided by the server 20. For example, it manages an ID for identifying the connected service, data items that need to be collected from the vehicle 10 in order to provide the service, requirements necessary to sufficiently satisfy the accuracy of the service, and the like.

[0032] The data analysis unit 213 analyzes data collected from the vehicles 10 in order to deliver connected services provided by the server 20 to the vehicles 10. For example, if the connected service is a service that recommends the shortest route based on road conditions, the data analysis unit 213 analyzes vehicle position data, vehicle speed data, and road traffic information collected from multiple vehicles 10 for each area to estimate congested roads.

[0033] The service generation unit 214 generates a connected service to be provided to the vehicle 10 based on information extracted from the data analyzed by the data analysis unit 213. For example, if the connected service is a service that recommends the shortest route based on road conditions, the service generation unit 214 generates a new route for the vehicle 10 to travel that avoids the congested roads estimated by the data analysis unit 213.

[0034] The user management unit 215 manages all users who have subscribed to the connected services provided by the server 20. The service distribution unit 216 distributes the distribution data of the connected services generated by the service generation unit 214 to the vehicle 10 via the server communication unit 24.

[0035] (Overall Processing of Overall System S According to First Embodiment) Fig. 3 is a flowchart showing overall processing of overall system S according to the first embodiment. The overall processing is processing for transmitting data necessary for maintaining connected services by vehicle 10. For example, when powered on, vehicle 10 transmits data to server 20 at predetermined intervals, and then executes the overall processing shown in Fig. 3 .

[0036] First, in step S101, the data management unit 115 determines whether there has been a change in the driving state of the vehicle based on the vehicle data accumulated in the vehicle storage unit 15. If there has been a change in the driving state of the vehicle (step S101 YES), the data management unit 115 proceeds to step S102, and if there has been no change (step S101 NO), the entire process ends.

[0037] The change in the driving condition referred to here is, for example, a state in which the vehicle 10 moves from a road with less than a certain amount of traffic to a road with more than a certain amount of traffic, encounters congestion, and the vehicle speed drops suddenly, and this state continues for a certain period of time. Also, a state in which the vehicle 10 travels from an ordinary road onto an expressway, the vehicle speed increases, and the increased vehicle speed continues for a certain period of time is also treated as a change in the driving condition. Data items to be monitored to detect such changes in the driving condition are registered in advance in the data management unit 115. Furthermore, step S101 is a process that is executed periodically.

[0038] Next, in step S102, the data transmitter / receiver 116 detects whether or not there is waste in the data transmission from the vehicle 10 to the server 20 (waste detection process). Details of the waste detection process will be described later with reference to FIG.

[0039] Next, in step S103, the data transmitter / receiver 116 determines whether a wasteful state in data transmission was detected in step S102. If a wasteful state was detected (step S103 YES), the data transmitter / receiver 116 proceeds to step S104, and if a wasteful state was not detected (step S103 NO), the data transmitter / receiver 116 returns to step S101.

[0040] In step S104, the service management unit 113 checks the service requirements for the connected services provided to the vehicle 10 to satisfy sufficient accuracy (service requirement check process). Details of the service requirement check process will be described later with reference to FIG. 5.

[0041] Next, in step S105, the data management unit 115 performs grouping of data items based on the data collection conditions, based on the confirmation result of step S104 (data item grouping process). Details of the data item grouping process will be described below with reference to FIG. 7.

[0042] Next, in step S106, the data transmitter / receiver 116 refers to the data item group table T3 (FIG. 8) created in step S105 and transmits the data items for each group to the server 20 (data transmission process). Details of the data transmission process will be described later with reference to FIG. 9.

[0043] (Details of Waste Detection Processing According to First Embodiment) FIG. 4 is a flowchart showing waste detection processing (step S102 (FIG. 3)) according to the first embodiment.

[0044] First, in step S102a, the data transmitter / receiver 116 receives an instruction regarding the data transmission frequency at which the server 20 transmits data. Next, in step S102b, the data transmitter / receiver 116 checks the content of the instruction regarding the data transmission frequency received in step S102a and checks whether there is an instruction to reduce the current data transmission frequency or to stop transmission. If there is an instruction to reduce the transmission frequency or to stop transmission (YES in step S102b), the data transmitter / receiver 116 proceeds to step S102f. On the other hand, if there is no instruction to reduce the transmission frequency or to stop transmission (NO in step S102b), the data transmitter / receiver 116 proceeds to step S102c.

[0045] In step S102c, the data transmitter / receiver 116 samples the number of data transmissions per predetermined time period from the vehicle 10 to the server 20 and the data size of the transmission data at regular intervals from the time point when the vehicle driving state detected in step S101 changes. Then, the data transmitter / receiver 116 calculates the average number of transmissions per travel distance.

[0046] For example, assume that the initial setting for the transmission frequency of vehicle 10 is one transmission per second. When traveling on a public road (40 km / h) without traffic jams, it takes approximately one second to travel 11 meters, and if one data transmission is performed during that time, the average number of transmissions per traveled distance is 1 / 11 = 0.09 (times / m). Furthermore, if vehicle 10 enters a congested road and takes five minutes to travel 11 meters, during which time it performs 300 data transmissions, the average number of transmissions per traveled distance is 300 / 11 = 27.3 (times / m). Furthermore, if the size of the data transmitted per transmission varies, the average transmission size per traveled distance can be further calculated.

[0047] Next, in step S102d, the data transmitter / receiver 116 compares the average value of the average number of transmissions or the average transmission size for the travel distance calculated in step S102c with a predetermined threshold. If the average value of the average number of transmissions or the average transmission size for the travel distance exceeds the threshold (step S102d YES), the data transmitter / receiver 116 proceeds to step S102f, and if the average value is equal to or less than the threshold (step S102d NO), the data transmitter / receiver 116 proceeds to step S102e.

[0048] In step S102e, the data transmitter / receiver 116 extracts the number of samplings performed in step S102c and compares it with a predetermined threshold value for the number of samplings. If the number of samplings exceeds the threshold value (YES in step S102e), the data transmitter / receiver 116 concludes that no wasteful state in data transmission has been detected and terminates the waste detection process. On the other hand, if the number of samplings is equal to or less than the threshold value (NO in step S102e), the data transmitter / receiver 116 returns the process to step S102b.

[0049] In step S102f, the data transmitter / receiver 116 determines that a wasteful state has occurred in data transmission based on an instruction from the server 20 or the sampling result of step S102c. After step S102f is completed, the data transmitter / receiver 116 ends the waste detection process.

[0050] (Details of Service Requirement Confirmation Processing According to the First Embodiment) FIG. 5 is a flowchart showing the service requirement confirmation processing (step S104 (FIG. 3)) according to the first embodiment.

[0051] First, in step S104a, the service management unit 113 checks whether or not there is a service being executed by the service execution unit 114. If there is a service being executed by the service execution unit 114 (YES in step S104a), the service management unit 113 proceeds to step S104b, and if there is no service being executed by the service execution unit 114 (NO in step S104a), the service requirement confirmation process ends.

[0052] 6A is a diagram illustrating an example of a service list table T1 according to embodiment 1. The service list table T1 registers connected services managed by the service management unit 113. The service list table T1 includes the following fields: ID, service name, destination, expiration date, and status.

[0053] The ID is identification information of an entry in the service list table T1. The service name is identification information of the service. The recipient is the name of the organization to which the connected service is provided. The expiration date is the period during which the vehicle 10 can use the connected service. The status indicates whether the connected service is running or not. The items included in the service list table T1 are not limited to those shown in FIG. 6A.

[0054] Next, in step S104b, the data management unit 115 extracts data items that need to be transmitted to the server 20 in order to execute the connected service managed by the service management unit 113 from the required data item list table T2.

[0055] 6B is a diagram showing an example of a required data item list table T2 according to embodiment 1. The required data item list table T2 shows data items of connected services managed by the data management unit 115. The required data item list table T2 includes items such as an ID, a service ID, a data item, and a collection condition.

[0056] The ID is identification information for an entry in the required data item list table T2. The service ID is identification information for a connected service. The data item represents the name of a data item that needs to be sent to the server 20 to execute each connected service. The collection conditions are data collection conditions for the server 20 to maintain sufficient service accuracy for the connected service. Note that the items included in the required data item list table T2 are not limited to those shown in FIG. 6B.

[0057] Next, in step S104c, the data management unit 115 extracts, from the required data item list table T2, collection conditions for data items that need to be transmitted to the server 20 in order to execute the connected service managed by the service management unit 113. When step S104c ends, the data management unit 115 ends the service requirement confirmation process.

[0058] (Details of Data Item Grouping Process According to First Embodiment) FIG. 7 is a flowchart showing the data item grouping process (step S105 (FIG. 3)) according to the first embodiment.

[0059] First, in step S105a, the data management unit 115 references the required data item list table T2 (FIG. 6B) to acquire data items. Next, in step S105b, the data management unit 115 references the required data item list table T2 to extract collection conditions for each data item acquired in step S105a.

[0060] Next, in step S105c, the data management unit 115 determines whether the collection condition for each data item included in the processing results of steps S105a and S105b is a "time period." A "time period" is a collection condition related to the data transmission period for periodically collecting (transmitting) data in units of a predetermined time, and is stored in the "collection condition" field of the required data item list table T2 (FIG. 6B) in time notation, such as "1 s." If the collection condition is a "time period," the data management unit 115 proceeds to step S105d, and if the collection condition is not a "time period," the data management unit 115 proceeds to step S105e.

[0061] For example, as shown in Figure 6B, if the collection condition is "1 s", it can be seen that "speed" data needs to be transmitted at a "time period" of "1 second" in order for the connected service to maintain a certain level of accuracy.

[0062] In step S105d, the data management unit 115 registers the data items determined to be "time periods" in step S105c as "time period groups" (first groups) in the data item group table T3 (FIG. 8).

[0063] In step S105e, the data management unit 115 determines whether the collection condition for the data item that was not determined to be a "time period" in step S105c is a "change in value."

[0064] Here, "change in value" refers to a collection condition that performs data collection (data transmission) when a certain index value changes beyond a threshold. The "change in value" may be stored as a percentage change, such as "10% decrease," in the "collection condition" of the required data item list table T2 (FIG. 6B), or the amount of change itself may be stored. If the collection condition is "change in value," the data management unit 115 proceeds to step S105f, and if the collection condition is not "change in value," the data management unit 115 proceeds to step S105g.

[0065] For example, as shown in Figure 6B, when the collection conditions are "50% or more: 10% decrease, less than 50%: 5% decrease," it can be seen that the "battery capacity" data needs to be transmitted under the following transmission conditions in order for the connected service to maintain a certain level of accuracy. That is, when the "battery capacity" is 50% or more and the "battery capacity" is decreased by 10%, and when the "battery capacity" is less than 50%, the "battery capacity" needs to be transmitted when the "battery capacity" is decreased by 5%.

[0066] In step S105f, the data management unit 115 registers the data items determined to be "value changes" in step S105e as "value change groups" (second groups) in the data item group table T3 (FIG. 8).

[0067] In step S105g, the data management unit 115 determines whether the collection condition for the data item that was not determined to be a "change in value" in step S105e is a "travel distance interval." A "travel distance interval" is a collection condition for collecting data (transmitting data) every time the vehicle 10 travels a predetermined distance, and is stored in the "collection condition" field of the required data item list table T2 (FIG. 6B) in a distance notation such as "20 m." If the collection condition is a "distance interval," the data management unit 115 proceeds to step S105h, and if the collection condition is not a "distance interval," the data management unit 115 proceeds to step S105i.

[0068] For example, as shown in Figure 6B, if the collection condition is "20 m," data on the "position" of one's own vehicle 10 needs to be transmitted every time the vehicle moves a "travel distance interval" of "20 m" in order to maintain a certain level of accuracy for the relevant connected service.

[0069] In step S105h, the data management unit 115 registers the data item determined to be "distance interval" in step S105g as a "distance interval group" (third group) in the data item group table T3 (FIG. 8).

[0070] On the other hand, in step S105i, the data management unit 115 does not need to transmit data items that did not fall under the "distance interval" category in step S105g, regardless of the conditions of "time period," "change in value," or "distance interval." Therefore, the data management unit 115 registers the corresponding data items as an "other group" in the data item group table T3 (FIG. 8).

[0071] (Data item group table T3 according to embodiment 1) Fig. 8 is a diagram showing an example of the data item group table T3 according to embodiment 1. As a result of steps S105a to S105i, the data item group table T3 (Fig. 8) is created. The data item group table T3 includes items such as ID, data item, collection condition, and group.

[0072] The ID is identification information for an entry in the data item group table T3. The data item represents the name of a data item that needs to be transmitted to the server 20 to execute each connected service. The collection condition is a condition for transmitting data from the vehicle 10 to the server 20, and is a data transmission condition that must be met in order for distribution data generated based on the transmitted data to maintain sufficient service accuracy of the connected service. The group is a group into which each piece of data is classified. Note that the items included in the data item group table T3 are not limited to those shown in FIG. 8.

[0073] (Details of Data Transmission Process According to First Embodiment) Fig. 9 is a flowchart showing the data transmission process (step S106 (Fig. 3)) for each data item according to the first embodiment. The data transmission process is executed in parallel for each data item.

[0074] First, in step S106a, the data transmitter / receiver 116 refers to the data item group table T3 (FIG. 8) to acquire the data items to be transmitted to the server 20. Next, in step S106b, the data transmitter / receiver 116 refers to the data item group table T3 to extract the collection conditions for the data items acquired in step S106a.

[0075] Next, in step S106c, the data transmitter / receiver 116 refers to the data item group table T3 and determines whether the data item extracted in step S106b is a "time cycle group." If the data item extracted in step S106b is a "time cycle group" (YES in step S106c), the data transmitter / receiver 116 proceeds to step S106d. On the other hand, if the data item is not a "time cycle group" (NO in step S106c), the data transmitter / receiver 116 proceeds to step S106e.

[0076] In step S106d, the data transmitter / receiver 116 determines whether the time period condition, which is the transmission condition for the "time period group," is satisfied. If the time period condition is satisfied, the data transmitter / receiver 116 proceeds to step S106i, and if the time period condition is not satisfied, the data transmitter / receiver 116 repeats step S106d. For example, the collection condition for the data item "speed" is "1 s," and it is determined whether the 1-second period is satisfied.

[0077] In step S106e, the data transmitter / receiver 116 refers to the data item group table T3 and determines whether the data item extracted in step S106b is a "value change group." If the data item extracted in step S106b is a "value change group" (YES in step S106e), the data transmitter / receiver 116 proceeds to step S106f. On the other hand, if the data item is not a "value change group" (NO in step S106e), the data transmitter / receiver 116 proceeds to step S106g.

[0078] In step S106f, the data transmitter / receiver 116 determines whether the value change condition, which is the transmission condition for the "value change group," is satisfied. If the value change condition is satisfied, the data transmitter / receiver 116 proceeds to step S106i, and if the value change condition is not satisfied, the data transmitter / receiver 116 repeats step S106f. For example, the collection condition for the data item "battery capacity" is "50% or more: 10% decrease, less than 50%: 5% decrease," and it is determined whether the condition of 10% decrease or 5% decrease is satisfied.

[0079] In step S106g, the data transmitter / receiver 116 refers to the data item group table T3 and determines whether the data item extracted in step S106b is a "travel distance interval group." If the data item extracted in step S106b is a "travel distance interval group" (YES in step S106g), the data transmitter / receiver 116 proceeds to step S106h. On the other hand, if the data item is not a "travel distance interval group" (NO in step S106g), the data transmitter / receiver 116 ends the data transmission process.

[0080] In step S106h, the data transmitter / receiver 116 determines whether the travel distance interval condition, which is the transmission condition for the "travel distance interval group," is satisfied. If the travel distance interval condition is satisfied, the data transmitter / receiver 116 proceeds to step S106i, and if the travel distance interval condition is not satisfied, the data transmitter / receiver 116 repeats step S106h. For example, the collection condition for the data item "location" is "20 m," and it is determined whether the travel distance has reached 20 m.

[0081] In step S106i, the data transmitter / receiver 116 transmits the data of the corresponding data item to the server 20 via the in-vehicle communication unit 14.

[0082] Effect of First Embodiment In this embodiment, when a wasteful state is detected due to a change in the driving state of the vehicle 10, the frequency of data transmission to the server 20 is reduced while satisfying the collection conditions for data items necessary for maintaining the connected service. This makes it possible to reduce wasteful communication and resource usage while maintaining the accuracy of the connected service.

[0083] [Second embodiment] In a second embodiment, in the waste detection process of step S102 (FIG. 3), a state in which wasteful data transmission occurs only on the vehicle 10 side without receiving an instruction from the server 20. In the second embodiment, only the differences from the first embodiment will be described.

[0084] (Waste Detection Processing According to Embodiment 2) Fig. 10 is a flowchart showing waste detection processing according to embodiment 2. Embodiment 2 differs from embodiment 1 in that the waste detection processing shown in Fig. 10 is executed in step S102 (Fig. 3), but is otherwise similar to embodiment 1.

[0085] First, in step S102Ba, the data management unit 115 checks the current position and driving route of the vehicle 10 and acquires area information for the planned driving area through which the vehicle 10 will drive. Next, in step S102Bb, the data management unit 115 compares the planned driving area acquired in step S102Bb with a pre-registered map of communication-disabled areas and determines whether the planned driving area is an area in which communication will be disabled. If the planned driving area is an area in which communication is disabled (step S102Bb YES), the data management unit 115 proceeds to step S102Bc, and if it is an area in which communication is enabled (step S102Bb NO), the data management unit 115 proceeds to step S102c.

[0086] In step S102Bc, the data management unit 115 instructs the data transmission / reception unit 116 to stop data transmission when it detects that the vehicle 10 has entered a communication unavailable area. Next, in step S102Bd, the data management unit 115 instructs the data recording unit 112 to back up data related to the vehicle 10 in the vehicle storage unit 15 while the vehicle 10 is traveling in the communication unavailable area. Then, the data management unit 115 instructs the data transmission / reception unit 116 to transmit data to the server 20 when the vehicle 10 begins traveling in a communication available area.

[0087] Steps S102c, S102d, S102e, and S102f are the same as those in FIG.

[0088] (Effects of embodiment 2) According to this embodiment, by detecting wasteful states only on the vehicle 10 side, even when communication with the server 20 is not possible, the wasteful state of the vehicle can be detected, and wasteful communication and resource usage can be reduced.

[0089] [Third Embodiment] In a third embodiment, instead of the overall processing according to the first embodiment shown in Fig. 3, the server 20 detects unnecessary data transmission and transmits instructions regarding the frequency of data transmission to the vehicle 10. The vehicle 10 then transmits data in accordance with the instructions regarding the frequency of data transmission from the server 20. In the third embodiment, only the differences from the first embodiment will be described.

[0090] (Overall Processing According to Embodiment 3) Fig. 11 is a flowchart showing overall processing according to embodiment 3. Embodiment 3 differs from embodiment 1 in that the overall processing shown in Fig. 11 is executed instead of the overall processing according to embodiment 1 in Fig. 3, but is otherwise similar to embodiment 1.

[0091] First, in step S201, the service management unit 212 of the server 20 acquires a service from a list of connected services provided by the server 20. The "list of connected services provided by the server 20" has a format similar to that of the service list table T1 (FIG. 6A), and the connected services provided by the server 20 are registered.

[0092] Next, in step S202, the service management unit 212 inquires of the user management unit 215 about target users for the service acquired in step S201. The service management unit 212 then narrows down the target users for the corresponding service and returns a list of the narrowed down users to the service management unit 212.

[0093] Next, in step S203, the service management unit 212 inquires of the vehicle management unit 211 about the vehicles 10 of the relevant user for the relevant service based on the user list acquired in step S202. The vehicle management unit 211 narrows down the vehicles 10 that are eligible for the relevant service, and responds to the service management unit 212 with a list of the narrowed down eligible vehicles.

[0094] Next, in step S204, the vehicle management unit 211 acquires the location information of each vehicle 10 listed in the list of target vehicles acquired in step S203. The vehicle management unit 211 then compares the location information with a pre-registered mobile communication unavailable area map (area information) to confirm whether each vehicle is within the relevant area. A mobile communication unavailable area here refers to an area where mobile communication signals cannot reach due to, for example, the shape of the road or the surrounding environment. If there is a vehicle 10 traveling in the relevant area (step S204 YES), the vehicle management unit 211 proceeds to step S205. If there is no vehicle 10 traveling in the relevant area (step S204 NO), the vehicle management unit 211 proceeds to step S206.

[0095] In step S205, the service distribution unit 216 sends an instruction to stop data transmission to the target vehicle 10 that is traveling in the area determined in step S204, along with information that the vehicle is traveling in an area where mobile communication is not available.

[0096] Meanwhile, in step S206, the service generation unit 214 determines whether the amount of data collected from the target vehicle 10 for generating a service is sufficient for generating the service. For example, if a certain number of vehicles 10 or more are traveling in a certain area, it can be determined that a sufficient amount of data necessary for generating the service has been collected. If the required data is sufficient (step S206 YES), the service generation unit 214 proceeds to step S207, and if the required data is not sufficient (step S206 NO), the service generation unit 214 proceeds to step S208.

[0097] In step S207, since the determination result in step S206 indicates that there is a sufficient amount of data, the service distribution unit 216 transmits an instruction to the target vehicle 10 to reduce the frequency of data transmission.

[0098] On the other hand, in step S208, since the amount of data is insufficient as a result of step S206, the service distribution unit 216 transmits an instruction to the target vehicle 10 to maintain the current data transmission frequency. In step S208, the service distribution unit 216 may transmit an instruction to the vehicle 10 to increase the current data transmission frequency.

[0099] Then, in step S209, the data transmitter / receiver 116 of the target vehicle 10 transmits the data of the relevant service to the server 20 via the in-vehicle communication unit 14 in accordance with the instruction regarding the frequency of data transmission received from the server 20.

[0100] (Effects of Embodiment 3) According to this embodiment, the server 20 detects a wasteful state by utilizing information that the vehicle 10 does not have access to (for example, information about the status of other vehicles 10 or the status of the server 20) and transmits instructions regarding the data transmission frequency. As a result, the vehicle 10 can appropriately maintain, reduce, or increase the data transmission frequency, thereby reducing wasteful communication and resource usage while maintaining the service quality of the connected service. Furthermore, by detecting a wasteful state in the server 20, it is possible to deal with cases where the vehicle 10 does not have sufficient computing power.

[0101] [Embodiment 4] An overall system (data transmission system) according to this embodiment includes the vehicle 10 disclosed in embodiment 1 and the server 20 disclosed in embodiment 3. The server 20 executes the process of the server 20 shown in Fig. 11 and transmits instructions regarding the data transmission frequency to the vehicle 10 in steps S205, S207, and S208. The vehicle 10 receives the instructions regarding the data transmission frequency from the server 20 in step S102a.

[0102] Effect of Fourth Embodiment In this embodiment, both the server 20 and the vehicle 10 determine a "state in which useless data transmission is occurring" from the vehicle 10 to the server 20. Then, when the server 20 outputs an instruction from the vehicle 10 to the server 20 to reduce the frequency of data transmission or stop data transmission, the instruction from the server 20 takes priority. On the other hand, when the server 20 does not output an instruction to reduce the frequency of data transmission or stop data transmission, the vehicle 10 determines a "state in which useless data transmission is occurring." In this way, by using the determinations of both the vehicle 10 and the server 20 in combination, it is possible to efficiently improve the accuracy of determining a "state in which useless data transmission is occurring," and it may be possible to further reduce useless communication and resource usage while maintaining the accuracy of connected services.

[0103] Although the embodiments of the present disclosure have been described in detail above, the present disclosure is not limited to the above-described embodiments and can be modified in various ways without departing from the spirit of the present disclosure. For example, the above-described embodiments have been described in detail to clearly explain the present invention, and the present disclosure is not necessarily limited to those including all of the described configurations. Furthermore, some of the configurations of the above-described embodiments can be added to, deleted from, or replaced with other configurations.

[0104] Furthermore, the above-described configurations, functional units, processing units, etc. may be partially or entirely implemented in hardware, for example, by designing them as integrated circuits. The above-described configurations, functions, etc. may also be implemented in software by a processor interpreting and executing a program that implements each function. Information such as the programs, tables, and files that implement each function can be stored in a memory, a storage device such as an HDD or SSD, or a recording medium such as an IC card, an SD card, or a DVD.

[0105] In addition, in the above-mentioned drawings, the control lines and information lines shown are those that are considered necessary for explanation, and do not necessarily show all the control lines and information lines that are actually implemented. For example, it may be considered that almost all components are actually connected to each other.

[0106] The above-described arrangement of the functions and data of the vehicle 10 and the server 20 is merely an example. The arrangement, integration, and distribution of the functions and data can be changed to an optimal form in terms of the performance, processing efficiency, communication efficiency, etc. of the hardware and software.

[0107] 10: Vehicle, 11, 21: CPU, 14: In-vehicle communication unit, 15: In-vehicle memory unit, 16: Sensor, 24: Server communication unit, 25: Server memory unit, 111: Data acquisition unit, 112: Data recording unit, 113: Service management unit, 114: Service execution unit, 115: Data management unit, 116: Data transmission / reception unit, 211: Vehicle management unit, 212: Service management unit, 213: Data analysis unit, 214: Service generation unit, 215: User management unit, 216: Service distribution unit.

Claims

1. A vehicle that communicates with a server that provides a connected service, the vehicle having a processor, a memory, and a storage unit, the storage unit storing transmission conditions for data when the data is transmitted from the vehicle to the server, the transmission conditions being to be satisfied in order to maintain accuracy of the connected service, the processor acquiring the data indicating a driving state of the vehicle, determining based on the data whether a change has occurred in the driving state, determining whether an average value of the number of transmissions or the data size of the data transmitted from the vehicle to the server per predetermined time period exceeds a threshold value if it is determined that the number of transmissions or the average value exceeds a threshold value, determining based on the transmission conditions whether the data is classified into any of a first group related to a transmission period of the data, a second group related to a change in the value of the data, and a third group related to an interval of travel distance of the vehicle, and transmitting the data to the server in accordance with the transmission conditions if it is determined that the data is classified into any of the first to third groups.

2. A vehicle as described in claim 1, characterized in that when the processor receives an instruction from the server to reduce or stop the transmission of the data transmitted from the vehicle to the server, the processor reduces or stops the transmission of the data to the server without determining whether the number of transmissions or the average value has exceeded a threshold value.

3. A vehicle as described in claim 1, wherein the processor acquires area information through which the vehicle is scheduled to travel based on the current position and travel route of the vehicle, determines whether the area information corresponds to a communication-prohibited area in which the communication is not possible, and stops transmitting the data to the server if it is determined that the area information corresponds to the communication-prohibited area.

4. A server that communicates with a vehicle and provides a connected service to the vehicle, the server having a processor and memory, the processor queries a user management unit that manages users of the vehicle to narrow down target users of the connected service, queries a vehicle management unit that manages the vehicle to narrow down target vehicles in which the target users reside, determines whether the amount of data obtained by the vehicle indicating the driving condition of the vehicle for generating distribution data for the connected service to be delivered to the vehicle satisfies the required data amount that should be satisfied in order to maintain the accuracy of the connected service, and if it is determined that the amount of data satisfies the required data amount, sends an instruction to the target vehicle to reduce the frequency of transmission of the data to the server.

5. A server as described in claim 4, characterized in that, when it is determined that the amount of data of the data does not satisfy the required amount of data, the processor sends an instruction to the target vehicle to maintain or increase the frequency of transmission of the data to the server.

6. A server as described in claim 4, wherein the processor acquires area information in which the target vehicle is scheduled to travel based on the current position and travel route of the target vehicle, determines whether the area information corresponds to a communication-prohibited area in which the communication is impossible, and, if it is determined that the area information corresponds to the communication-prohibited area, transmits an instruction to the target vehicle to stop transmitting the data to the server.

7. A service providing system comprising: a vehicle according to claim 2; and a server according to claim 6.

8. A data transmission method executed by a vehicle that communicates with a server that provides a connected service, wherein the vehicle has a processor, a memory, and a storage unit, and the storage unit stores transmission conditions for data when transmitting data from the vehicle to the server, the transmission conditions being to be satisfied in order to maintain accuracy of the connected service, and the processor acquires the data indicating a driving state of the vehicle, determines whether or not a change has occurred in the driving state based on the data, and if it is determined that a change has occurred in the driving state, determines whether or not an average value of the number of transmissions or data size of the data per predetermined time transmitted from the vehicle to the server has exceeded a threshold, and if it is determined that the number of transmissions or the average value has exceeded a threshold, determines based on the transmission conditions whether the data is classified into any of a first group related to a transmission period of the data, a second group related to a change in the value of the data, and a third group related to a moving distance interval of the vehicle, and if it is determined that the data is classified into any of the first to third groups, transmits the data to the server in accordance with the transmission conditions.

Images