Management server and vehicle network system
The management server in the vehicle network system addresses unnecessary data transmission by aggregating communication traffic for each application, reducing network traffic and enabling service providers to manage excess communication through fees.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2022-07-08
- Publication Date
- 2026-03-04
AI Technical Summary
Existing in-vehicle information utilization networks transmit unnecessary data, leading to increased communication traffic, necessitating a method to grasp the communication status on the vehicle network system.
A management server with a server communication unit and communication traffic management unit aggregates communication traffic for each application identification data, enabling the management server to grasp the communication status and take appropriate actions.
The management server effectively manages communication traffic by identifying and restricting unnecessary data transmission, reducing overall network traffic and allowing service providers to address excess communication volume through measures like charging additional fees.
Smart Images

Figure 0007823514000001 
Figure 0007823514000002 
Figure 0007823514000003
Abstract
Description
[Technical Field]
[0001] The present disclosure relates to communication in a vehicle network system. [Background technology]
[0002] The in-vehicle information utilization network system described in Patent Document 1 includes an in-vehicle network system, an inspection system, an in-vehicle information communication device, a mobile computer, a server device, and a client device. The in-vehicle information communication device receives in-vehicle data from the in-vehicle network system and the inspection system and transmits the received in-vehicle data to the mobile computer via short-range communication. The mobile computer transmits the in-vehicle data to the server device via long-range communication. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] International Publication 2014 / 017454 Summary of the Invention [Problem to be solved by the invention]
[0004] In the above-described in-vehicle information utilization network system, all in-vehicle data acquired on the network is transmitted to a server device. As a result, even unnecessary in-vehicle data is transmitted to the server device, increasing the amount of communication traffic. In order to prevent such an increase in communication traffic due to the transmission of unnecessary data, it is desirable to grasp the communication status on the network.
[0005] One aspect of the present disclosure provides a technique that makes it possible to grasp a communication status on a vehicle network system. [Means for solving the problem]
[0006] A management server according to one aspect of the present disclosure includes a server communication unit (54) and a communication traffic management unit (52). The server communication unit wirelessly communicates with a plurality of onboard devices (30) mounted in different vehicles. Each of the onboard devices executes a plurality of application programs. Each of the application programs has application identification data for identifying the application program. The communication traffic management unit acquires, via the server communication unit, communication traffic corresponding to the execution of each of the application programs from each of the onboard devices, and calculates the application communication traffic by tallying up the communication traffic for each application identification data.
[0007] The management server acquires the communication volume from each of the multiple onboard devices and aggregates the communication volume for each application identification data. Therefore, the management server can grasp the communication status between the management server and the multiple onboard devices. As a result, the management server can take action according to the communication status.
[0008] A vehicle network system according to another aspect of the present disclosure includes a plurality of on-board devices (30) mounted in different vehicles and a management server (50). Each of the plurality of on-board devices includes an on-board communication unit (32), an application execution unit (36), and a communication traffic measurement unit (33). The on-board communication unit wirelessly communicates with the management server. The application execution unit installs and executes a plurality of application programs. Each of the plurality of application programs has application identification data for identifying the respective application programs. The communication traffic measurement unit measures communication traffic corresponding to execution of each of the plurality of application programs by the application execution unit for each application identification data, and transmits communication information associating each of the measured communication traffic with the application identification data to the management server via the on-board communication unit. The management server includes a server communication unit (54) and a communication traffic management unit (52). The server communication unit wirelessly communicates with the plurality of on-board devices. The communication traffic management unit acquires communication information from each of the plurality of on-board devices via the server communication unit, aggregates communication traffic for each application identification data, and calculates application communication traffic.
[0009] The vehicle network system has the same effects as the management server. [Brief explanation of the drawings]
[0010] [Figure 1] 1 is a block diagram showing a configuration of a vehicle network system according to an embodiment of the present invention; [Figure 2] FIG. 2 is a block diagram showing a hardware configuration of the vehicle-mounted device according to the embodiment. [Figure 3] FIG. 2 is a block diagram showing a hardware configuration of a management server according to the present embodiment. [Figure 4] 5 is a flowchart showing a process of measuring communication traffic executed by the vehicle-mounted device according to the present embodiment; [Figure 5] 5 is a flowchart showing a communication restriction process executed by the vehicle-mounted device according to the present embodiment. [Figure 6] 5 is a flowchart showing a process for removing communication restrictions executed by the vehicle-mounted device according to the present embodiment. [Figure 7] 10 is a flowchart illustrating a communication volume measurement process executed by the management server according to the present embodiment. [Figure 8] 10 is a flowchart illustrating a communication restriction request process executed by the management server according to the present embodiment. [Figure 9] 10 is a flowchart showing a process of requesting removal of communication restriction executed by the management server according to the present embodiment; DETAILED DESCRIPTION OF THE INVENTION
[0011] <1. Configuration> The schematic configuration of a vehicle network system 100 according to this embodiment will be described with reference to FIG. 1. The vehicle network system 100 includes a management server 50, multiple onboard devices 30A, 30B, 30C, and 30D, and multiple service servers 60A, 60B, and 60C. The number of onboard devices included in the vehicle network system 100 is not limited to four, but may be two, three, or five or more. The number of service servers included in the vehicle network system 100 is not limited to three, but may be two, four, or more. Hereinafter, the onboard devices 30A, 30B, 30C, and 30D will be collectively referred to as onboard devices 30, and the service servers 60A, 60B, and 60C will be collectively referred to as service servers 60.
[0012] Each of the on-vehicle devices 30 is installed in a different vehicle and collects vehicle data. Each of the on-vehicle devices 30 executes one or more application programs provided by the service server 60, processes the vehicle data, and generates processed data. The management server 50 is installed outside the vehicle and manages the application programs provided by each of the service servers 60.
[0013] Each of the service servers 60 is used by a plurality of service businesses (specifically, service providers). Each service business may install and use its own service server 60, or may use a service server 60 installed by another party (for example, the operator of the management server 50). Each of the service servers 60 acquires vehicle data or processed data via the management server 50, and uses the vehicle data or processed data to provide a service to a service user. The service user may be a vehicle user, owner, or operation manager, and the service may be a fleet service, a congestion prediction service, or the like.
[0014] Service providers develop application programs according to the services they provide through the service server 60. The service providers register the developed application programs in the management server 50. Service users enter into a contract with one of the service providers and download the application programs developed by the contracted service provider from the management server 50. The management server 50 manages the communication volume of data related to the in-vehicle device applications for each application.
[0015] <1-1. Configuration of the in-vehicle device> As shown in FIG. 2, the vehicle-mounted device 30 includes a control unit 310, a vehicle interface (hereinafter referred to as vehicle I / F) 320, a communication device 330, and a storage device 340.
[0016] The control unit 310 includes a CPU 311, a ROM 312, and a RAM 313. Various functions of the control unit 310 are realized by the CPU 311 executing a program stored in a non-transitory physical recording medium. In this embodiment, the ROM 312 corresponds to the non-transitory physical recording medium storing the program. Furthermore, by executing this program, a method corresponding to the program is performed.
[0017] The vehicle I / F 320 is connected to one or more vehicle electronic control units (hereinafter referred to as vehicle ECUs) 10 via an in-vehicle network or the like, and acquires various vehicle data from each of the vehicle ECUs 10. Each of the vehicle ECUs 10 controls various devices such as brakes, steering, cameras, and radar. The in-vehicle network may include CAN and Ethernet. CAN is an abbreviation for Controller Area Network. CAN is a registered trademark. Ethernet is a registered trademark.
[0018] The communication device 330 performs data communication with the management server 50 via a wide area communication network by wireless communication. The storage device 340 includes a vehicle database (hereinafter referred to as vehicle data DB) 37, and stores vehicle data acquired via the vehicle I / F 320 and the like.
[0019] As shown in FIG. 1, the in-vehicle device 30 includes the functions of a vehicle data acquisition unit 31, an in-vehicle communication unit 32, a communication traffic measurement unit 33, an in-vehicle application management unit , an API 35, and an application execution unit . The vehicle data acquisition unit 31 repeatedly acquires vehicle data related to various devices from the vehicle ECU 10 at a predetermined acquisition period. The vehicle data includes the operation amount of the various devices and detection data detected by the various devices. For example, the vehicle data includes brake on / off, vehicle speed, and steering angle. The vehicle data may include not only raw data but also normalized or standardized data to eliminate variations between vehicle models. The vehicle data acquisition unit 31 associates the acquired vehicle data with the type of vehicle data and the acquisition time, and stores the data in the vehicle data DB 37.
[0020] The in-vehicle communication unit 32 controls the communication device 330 to perform wireless communication with the management server 50 . The API 35 is a standard interface for the application execution unit 36 to access the vehicle data DB 37 .
[0021] The application execution unit 36 accesses the vehicle data DB 37 via the API 35 and executes application programs using the vehicle data. The application programs include a first application, a second application, a third application, etc. The application execution unit 36 downloads and installs each of the first application, the second application, and the third application from the management server 50.
[0022] The first application is an application program developed by a provider of service server 60A and provided via management server 50. By executing the first application, application execution unit 36 generates, from vehicle data, processed data required for service server 60A to provide the first service. The second application is an application program developed by a provider of service server 60B and provided via management server 50. By executing the second application, application execution unit 36 generates, from vehicle data, processed data required for service server 60B to provide the second service. The third application is an application program developed by a provider of service server 60C and provided via management server 50. By executing the third application, application execution unit 36 generates, from vehicle data, processed data required for service server 60C to provide the third service.
[0023] The application execution unit 36 executes each of the first application, the second application, and the third application as a container. Note that the application execution unit 36 may install and execute only one or two application programs, or may install and execute four or more application programs.
[0024] The in-vehicle application management unit 34 manages the application IDs of the application programs installed in the in-vehicle devices 30 by associating them with container IDs. The application ID is an ID assigned to each application program and is a common ID within the vehicle network system 100. That is, if a first application installed in the in-vehicle device 30A is the same as a first application installed in the in-vehicle device 30B, the two application programs have the same application ID. The container ID is a temporary local ID assigned by each in-vehicle device 30. Note that, in this embodiment, the application ID corresponds to the application identification data of the present disclosure, but the application identification data is not limited to the application ID and may be any data that can identify an application program.
[0025] The communication volume measurement unit 33 measures the volume of communication between the in-vehicle communication unit 32 and the management server 50 for each container ID. When the application execution unit 36 executes an application program, data communication is performed between the in-vehicle device 30 and the management server 50. The volume of communication between the in-vehicle device 30 and the management server 50 varies depending on the type of application program. Therefore, the communication volume measurement unit 33 measures the volume of communication associated with the execution of the application program by the application execution unit 36 for each container ID. Furthermore, the communication volume measurement unit 33 acquires an application ID corresponding to the container ID from the in-vehicle application management unit 34 and associates the communication volume for each container ID with the application ID. Then, the communication volume measurement unit 33 transmits communication information to the management server 50 via the in-vehicle communication unit 32 at a predetermined transmission period or immediately before the in-vehicle device 30 is stopped. The communication information corresponds to information that associates the communication volume within the transmission period with the application ID.
[0026] <1-2. Management Server Configuration> As shown in FIG. 3, the management server 50 includes a control unit 510, a communication unit 520, and a storage unit 530.
[0027] The control unit 510 includes a CPU 511, a ROM 512, and a RAM 513. The various functions of the control unit 510 are realized by the CPU 511 executing a program stored in a non-transitory tangible recording medium. In this example, the ROM 512 corresponds to the non-transitory tangible recording medium storing the program. Furthermore, the execution of this program causes a method corresponding to the program to be performed.
[0028] The communication device 520 is wirelessly connected to each of the vehicle-mounted devices 30 and each of the service servers 60 via a wide area communication network, and performs data communication. The storage device 530 stores vehicle data and the like provided by the vehicle-mounted device 30.
[0029] As shown in FIG. 1, the management server 50 includes the functions of a service provider management unit 51, a communication traffic management unit 52, a server application management unit 53, and a server communication unit . The service provider management unit 51 manages information on the service providers that provide each of the service servers 60 (that is, service provider information).
[0030] The server application management unit 53 manages application programs registered by each of the service servers 60. Specifically, the server application management unit 53 manages the application ID of each application program in association with the service provider that provided the application program (e.g., identification data of the service provider). The server communication unit 54 controls the communication device 520 to perform wireless communication with each of the vehicle-mounted devices 30 and each of the service servers 60 .
[0031] The communication traffic management unit 52 collects and stores communication information at predetermined intervals from each of the in-vehicle devices 30 connected to the management server 50. The communication traffic management unit 52 aggregates the collected communication information for each application ID and calculates the application communication traffic for each application ID. Furthermore, the communication traffic management unit 52 acquires the service providers corresponding to the application IDs from the server application management unit 53 and the service provider management unit 51, and calculates the total traffic by adding up the application communication traffic for each service provider.
[0032] A single service provider may provide multiple application programs. Therefore, the communication traffic management unit 52 divides the multiple application programs registered in the server application management unit 53 into multiple groups. Each of the multiple groups is provided by a different service provider. The communication traffic management unit 52 then adds up the application communication traffic corresponding to the application IDs included in each group to calculate the total communication traffic for each service provider.
[0033] <2. Processing> <2-1. Processing performed by the in-vehicle device> <2-1-1. Measurement of communication volume> Next, a communication traffic measurement process executed by the vehicle-mounted device 30 will be described with reference to the flowchart of Fig. 4. The vehicle-mounted device 30 repeatedly executes the communication traffic measurement process at a predetermined processing cycle.
[0034] In S10, the communication traffic measurement unit 33 measures the communication traffic with the management server 50 for each application ID from the time when the communication traffic was last measured to the present time. The in-vehicle device 30 adds up the application communication traffic every time it communicates with the management server 50.
[0035] Next, in S20, the communication volume measurement unit 33 determines whether a predetermined time has elapsed since the previous transmission of the communication volume to the management server 50, or whether the on-board device 30 is about to stop. The on-board device 30 stops when the vehicle in which the on-board device 30 is installed stops. Therefore, the on-board device 30 determines whether a predetermined time has elapsed since the previous transmission, or whether the vehicle is about to stop. If it is determined that a predetermined time has elapsed since the previous transmission, or the on-board device 30 is about to stop, the process proceeds to S30. If it is determined that a predetermined time has not elapsed since the previous transmission, and the on-board device 30 is not about to stop, the process of S20 is repeatedly executed.
[0036] Next, in S30, the in-vehicle communication unit 32 associates the communication volume for each application ID with the application ID and transmits it to the management server 50.
[0037] <2-1-2. Communication restriction processing> Next, the communication restriction process executed by the vehicle-mounted device 30 will be described with reference to the flowchart in Figure 5. The management server 50 transmits a communication restriction request to the vehicle-mounted device 30 that has installed an application program provided by a communication volume excess service provider. The communication volume excess service provider is a service provider whose total communication volume exceeds a set upper limit. Here, the process when the vehicle-mounted device 30 receives a communication restriction request from the management server 50 will be described.
[0038] At S100, the in-vehicle communication unit 32 receives a communication restriction request from the management server 50. The communication restriction request is a request for communication restriction on the application ID of an application program provided by a communication volume excess service provider. The communication restriction includes limiting the communication volume to a predetermined value or less and stopping communication.
[0039] In S110, the in-vehicle communication unit 32 notifies the application execution unit 36 of the communication restriction. Upon receiving the notification, the application execution unit 36 stops execution of the application program corresponding to the application ID specified in the communication restriction (hereinafter, the communication restricted application) and enters a standby state.
[0040] In S120, the in-vehicle communication unit 32 starts restricting communication requests from the application execution unit 36. That is, when the in-vehicle communication unit 32 receives a communication restriction request from the management server 50, the in-vehicle communication unit 32 restricts communication even if the in-vehicle communication unit 32 receives a communication request from the application execution unit 36 in association with the execution of a communication restriction application.
[0041] In S130, the communication traffic measurement unit 33 measures the communication traffic associated with the execution of the communication restricted application from the time when the in-vehicle communication unit 32 receives the communication restriction request until the time when the communication restriction starts. Then, the in-vehicle communication unit 32 transmits the measured communication traffic to the management server 50.
[0042] <2-1-3. Cancellation of communication restrictions> Next, the process of removing communication restrictions executed by the vehicle-mounted device 30 will be described with reference to the flowchart of FIG.
[0043] In S200, the in-vehicle communication unit 32 receives a request to remove the communication restriction from the management server 50. Alternatively, the communication restriction period ends. For example, if the upper limit of communication volume is set for each month, the communication restriction period runs from the time the communication volume exceeds the upper limit to the end of the month, and the communication restriction period ends after the end of the month.
[0044] Next, in S210, the in-vehicle communication unit 32 notifies the application execution unit 36 of the release of the communication restriction. Upon receiving the notification, the application execution unit 36 starts executing the communication restricted application. Next, in S220, the in-vehicle communication unit 32 removes the restriction on the communication request from the application execution unit 36. That is, when the in-vehicle communication unit 32 receives a communication request from the application execution unit 36, the in-vehicle communication unit 32 communicates with the management server 50 without restricting the communication.
[0045] <2-2. Processing performed by the management server> <2-2-1. Communication volume measurement processing> Next, a description will be given of the traffic volume measurement process executed by the management server 50 with reference to the flowchart of Fig. 7. The management server 50 repeatedly executes the traffic volume measurement process at predetermined processing intervals.
[0046] In S300, the server communication unit 54 collects communication information indicating the communication volume for each application ID from each vehicle-mounted device 30 connected to the management server 50. Next, in S310, the communication traffic management unit 52 adds the communication traffic acquired this time to the communication traffic acquired in the previous processing cycle for each vehicle-mounted device 30 and each application ID.
[0047] Next, in S320, the communication traffic management unit 52 calculates the application communication traffic by summing up the communication traffic calculated in S310 for each application ID between the in-vehicle devices 30 connected to the management server 50.
[0048] Next, in S330, the total communication volume is calculated by adding up the application communication volumes corresponding to the application IDs provided by each service provider. Next, in S340, the total communication volume calculated in S330 is compared with a set upper limit for each service provider. The set upper limit is determined for each service provider according to the contract between the service provider and the operator of the management server 50.
[0049] In S350, it is determined for each service provider whether the total communication volume exceeds the set upper limit. If any of the total communication volumes exceeds the set upper limit, the process proceeds to S360. If all of the total communication volumes are equal to or less than the set upper limit, the process ends. S360 requests service providers that exceed data usage limits to limit data usage.
[0050] <2-2-2. Processing communication restriction requests> Next, the communication restriction request process executed by the management server 50 will be described with reference to the flowchart of FIG.
[0051] In S400, the service provider whose communication volume is in excess determined in S360 is notified of the upper limit being exceeded via the corresponding service server 60. Next, in S410, a communication restriction request is transmitted to the vehicle-mounted device 30 in which an application program related to a communication volume excess service provider is installed.
[0052] <2-2-3. Processing a request to remove communication restrictions> Next, a process for requesting removal of communication restrictions executed by the management server 50 will be described with reference to the flowchart of FIG.
[0053] In S500, a request to lift the communication restriction is received from the excess communication volume service provider via the corresponding service server 60. When the condition for lifting the communication restriction is met, the excess communication volume service provider requests the management server 50 to lift the communication restriction. The condition for lifting the communication restriction is, for example, payment of an additional fee. The set upper limit value increases in response to payment of the additional fee.
[0054] Next, in S510, a request to remove the communication restriction is sent to the in-vehicle device in which an application program related to the communication volume excess service provider is installed.
[0055] <3.Effects> According to the present embodiment described above in detail, the following effects are achieved. (1) The management server 50 acquires the communication volume from each of the multiple in-vehicle devices 30, aggregates the communication volume for each application ID, and calculates the application communication volume. Therefore, the management server 50 can grasp the communication status on the vehicle network system 100. Consequently, the management server 50 can take action according to the communication status.
[0056] (2) The management server 50 calculates the total communication volume by adding up the application communication volume for each service provider. Therefore, the management server 50 can grasp the total communication volume for each service provider.
[0057] (3) Data Overage: The service provider is notified of the data overage, allowing the service provider to take measures such as restricting data usage or charging additional fees. (4) A communication restriction is requested for the vehicle-mounted device 30 that has installed an application program related to the service provider for excessive communication traffic. This allows the vehicle-mounted device 30 to recognize and deal with the excess communication traffic.
[0058] (5) When the in-vehicle communication unit 32 receives a request for communication restriction and notifies the application execution unit 36, the application execution unit 36 can stop the execution of the application program and reduce the amount of communication.
[0059] (6) Even if the in-vehicle communication unit 32 receives a communication request from the application execution unit 36, the communication amount can be reduced by restricting the communication.
[0060] (Other embodiments) Although the embodiments of the present disclosure have been described above, the present disclosure is not limited to the above-described embodiments and can be implemented in various modified forms.
[0061] (a) In the above embodiment, the communication volume measurement unit 33 measures the communication volume and generates communication information indicating the communication volume associated with the application ID. The communication volume measurement unit 33 may measure the communication volume, acquire the communication destination, communication type, and vehicle status, and add the acquired communication destination, communication type, and vehicle status to the communication information. The communication destination may be a server provided by a service provider or a server provided by an operator of a management server. The communication type may be a cellular line or a Wi-Fi (registered trademark) line. The vehicle status may be a driving state or a parked state.
[0062] According to this configuration, the destination and the type of communication can be used to set the communication fee. Communication when the vehicle is parked is more likely to cause the battery to run out than communication when the vehicle is moving. Therefore, by using the vehicle state to set the communication fee and setting the communication fee for vehicle states that are more likely to cause the battery to run out higher than the communication fee for vehicle states that are less likely to cause the battery to run out, it is possible to suppress communication when the vehicle is in a state that is more likely to cause the battery to run out.
[0063] (b) The controller 310, 510 and the method described herein may be implemented by a special-purpose computer configured by configuring a processor and memory programmed to perform one or more functions embodied in a computer program. Alternatively, the controller 310, 510 and the method described herein may be implemented by a special-purpose computer configured by configuring a processor with one or more dedicated hardware logic circuits. Alternatively, the controller 310, 510 and the method described herein may be implemented by one or more special-purpose computers configured by combining a processor and memory programmed to perform one or more functions with a processor configured with one or more hardware logic circuits. Furthermore, the computer program may be stored as instructions executed by a computer on a computer-readable non-transitory tangible recording medium. The method for implementing the functions of each unit included in the controller 310, 510 does not necessarily need to include software; all of the functions may be implemented using one or more hardware devices.
[0064] (c) Multiple functions possessed by one component in the above embodiments may be realized by multiple components, or one function possessed by one component may be realized by multiple components. Also, multiple functions possessed by multiple components may be realized by one component, or one function realized by multiple components may be realized by one component. Also, part of the configuration of the above embodiments may be omitted. Also, at least part of the configuration of the above embodiments may be added to or substituted for the configuration of another of the above embodiments.
[0065] (d) In addition to the above-mentioned management server and vehicle network system, the present disclosure can also be realized in various forms, such as a program for causing a computer to function as the management server, a non-transient physical recording medium such as a semiconductor memory on which this program is recorded, and a method for collecting communication volume in a vehicle network. [Explanation of symbols]
[0066] 30, 30A, 30B, 30C, 30D... vehicle-mounted device, 32... vehicle-mounted communication unit, 33... communication volume measurement unit, 36... application execution unit, 50... management server, 52... communication volume management unit, 54... server communication unit, 100... vehicle network system.
Claims
1. a server communication unit (54) configured to communicate wirelessly with a plurality of on-board devices (30) mounted on different vehicles, each of the plurality of on-board devices configured to execute a plurality of application programs, each of the plurality of application programs having application identification data for identifying each of the plurality of application programs; a communication traffic management unit (52) configured to acquire, via the server communication unit, from each of the plurality of on-board devices, a communication traffic corresponding to the execution of each of the plurality of application programs, and to calculate an application communication traffic by tallying up the communication traffic for each of the application identification data; the server communication unit (54) is configured to wirelessly communicate with service servers associated with each of a plurality of service providers; each of the plurality of application programs is developed in accordance with a service provided by one of the plurality of service providers; the plurality of application programs are divided into a plurality of groups; each of the plurality of groups is provided by a different service provider from the plurality of service providers; The communication traffic management unit (52) is configured to calculate a total communication traffic by summing up the corresponding application communication traffic for each of the plurality of groups. Management server.
2. The communication traffic management unit (52) determining whether the calculated total communication volume exceeds a set upper limit value for each of the plurality of groups; When it is determined that the total communication volume of any of the plurality of groups exceeds the set upper limit value, the server communication unit (54) is configured to notify a service server associated with a corresponding service provider among the plurality of service providers of the excess communication volume. The management server according to claim 1 .
3. the communication volume management unit (52) is configured to request a communication restriction to an on-board device (30) selected from the plurality of on-board devices via the server communication unit; The selected vehicle-mounted device has installed thereon one of the plurality of groups for which it is determined that the total communication volume exceeds the set upper limit value. The management server according to claim 2 .
4. A vehicle network system including a plurality of on-board devices (30) mounted on different vehicles and a management server (50), Each of the plurality of on-vehicle devices an in-vehicle communication unit (32) configured to communicate wirelessly with the management server; an application execution unit (36) configured to install and execute a plurality of application programs, each of the plurality of application programs having application identification data that identifies each of the plurality of application programs; a communication volume measurement unit (33) configured to measure a communication volume corresponding to the execution of each of the plurality of application programs by the application execution unit for each of the application identification data, and to transmit communication information in which each of the measured communication volumes is associated with the application identification data to the management server via the in-vehicle communication unit, The management server a server communication unit (54) configured to communicate wirelessly with the plurality of vehicle-mounted devices; a communication traffic management unit (52) configured to acquire the communication information from each of the plurality of on-board devices via the server communication unit, and to calculate the application communication traffic by tallying up the communication traffic for each of the application identification data; the server communication unit (54) is configured to wirelessly communicate with service servers associated with each of a plurality of service providers; each of the plurality of application programs is developed in accordance with a service provided by one of the plurality of service providers; the plurality of application programs are divided into a plurality of groups; each of the plurality of groups is provided by a different service provider from the plurality of service providers; The communication traffic management unit (52) is configured to calculate a total communication traffic by summing up the corresponding application communication traffic for each of the plurality of groups. Vehicle network system.
5. The communication traffic management unit (52) determining whether the calculated total communication volume exceeds a set upper limit value for each of the plurality of groups; When it is determined that the total communication volume of any of the plurality of groups exceeds the set upper limit value, the server communication unit (54) is configured to notify a service server associated with a corresponding service provider among the plurality of service providers of the excess communication volume. The vehicle network system according to claim 4 .
6. the communication volume management unit (52) is configured to request a communication restriction to a selected one of the plurality of on-board devices (30) via the server communication unit (54); The selected vehicle-mounted device has installed thereon one of the plurality of groups for which it is determined that the total communication volume exceeds the set upper limit value. The vehicle network system according to claim 5 .
7. The in-vehicle communication unit (32) is configured to notify the application execution unit (36) when receiving the request for communication restriction. The vehicle network system according to claim 6 .
8. The in-vehicle communication unit (32) is configured to restrict communication when receiving the request for communication restriction, even if receiving a communication request from the application execution unit (36).
8. The vehicle network system according to claim 6 or 7.
9. The communication volume measurement unit (33) is configured to measure the communication volume, acquire the communication destination, the communication type, and the vehicle status, and add them to the communication information. The vehicle network system according to any one of claims 4 to 7.
Citation Information
Patent Citations
Originating call restriction system
JP2006340294A
Traffic management for third-party applications
JP2015534293A
Data management device, data management method, and data communication system
JP2019009789A
Techniques to identify application foreground / background state based on network traffic
US20160261472A1
On-board information communication apparatus, and on-board information utilizing network system
WO2014017454A1