JP7080000B2 - Service management device and service management method - Google Patents

Description

The present invention relates to a technique for calculating a usage fee for a mobility service (for example, a toll road, an hourly parking lot) using mobility data of an automobile vehicle (for example, location information, vehicle registration number).

In recent years, connected cars equipped with in-vehicle terminals capable of wide-area wireless communication are becoming widespread. With the realization of connected cars, sensor information can be collected from vehicles at any time, and a technological field called car telematics is developing, such as presenting automobile insurance charges according to the driving tendency of the driver and real-time monitoring of vehicle operating conditions.

Conventionally, a technique of mounting a wireless communication device such as an ETC (Electronic Toll Collection System) communication device on a vehicle and paying a toll road usage fee in a non-contact manner at a toll gate has become widespread. By analyzing the accurate location information collected from the toll collection in real time, it is possible to provide a toll transportation service that does not require dedicated equipment.

Patent Document 1 discloses one of the techniques related to toll transportation services in the connected car era, which does not require dedicated equipment. In the technique disclosed in Patent Document 1, based on the location information recorded by the connected car, the order of use of individual services and each of them in a specific area where a plurality of service resources (toll roads, parking lots, etc.) exist. The service usage time is measured and the service charge is calculated using static metering logic.

Japanese Unexamined Patent Publication No. 2015-130079

In the technique disclosed in Patent Document 1, since the charge of the service used in the automobile vehicle is calculated by the static metering logic, the metering logic is fixed and cannot be dynamically changed. For example, even if the user cannot enjoy the value of the toll road service due to traffic congestion during rush hours in urban areas or speed limit due to bad weather, the service charge is the same as when there is no traffic jam or the speed limit has not been changed. Will be. That is, the metering logic cannot be flexibly set according to environmental conditions such as traffic jams and weather.

It is an object of the present invention to provide a technique that allows flexible modification of the metering logic for calculating the price of a mobility service.

In order to achieve the above object, the present invention has a service resource management unit that manages geographic configuration information including resource location information indicating the location of service resources available by the vehicle, and a service usage amount related to the use of the service resource by the vehicle. The service metering management unit that manages metering logic management information including logic information indicating the usage amount calculation method for calculating the usage amount and application time information indicating the time to apply the usage amount calculation method, and the use of service resources. Based on the mobility data receiving unit that receives mobility data including position information from the declaring vehicle, and the mobility data and the geographical configuration information, the use of the service resource by the declaring vehicle is determined, and the declaring vehicle determines the use of the service resource. A service resource usage determination unit that generates service usage status management information including usage resource information related to the service resource used and usage time information indicating the time when the declared vehicle used the service resource, and the service usage status management. With reference to the information and the metering logic management information, regarding the use of the service resource by the declared vehicle based on the time when the declared vehicle used the service resource and the usage amount calculation method applied to the time. It has a service usage amount calculation unit that calculates the service usage amount.

INDUSTRIAL APPLICABILITY According to the present invention, it is possible to calculate an appropriate amount of service usage even when a plurality of dynamically changed metering logics exist for one use of a transportation service using a vehicle, which is flexible. Can provide toll transportation services.

It is a block diagram of the mobility service metering system using the management server according to 1st Embodiment. It is a figure which shows an example of the hardware configuration of the management server shown in FIG. It is a figure which shows the structural example of the table provided in the declaration vehicle information management part shown in FIG. It is a figure which shows the configuration example of the metering logic management table provided in the service metering management unit shown in FIG. It is a figure which shows the configuration example of the charge plan management table provided in the service metering management unit shown in FIG. It is a figure which shows the configuration example of the service resource management table provided in the service resource management part shown in FIG. It is a figure which shows the configuration example of the map / road composition information management table provided in the service resource management part shown in FIG. It is a figure which shows the configuration example of the vehicle registration information management table provided in the service resource management unit shown in FIG. It is a figure which shows the configuration example of the service usage state management table provided in the metering processing unit shown in FIG. 1. It is a figure which shows the configuration example of the metering result management table provided in the metering processing part shown in FIG. It is a flowchart which shows an example of the processing flow of the metering processing part shown in FIG. It is a flowchart which shows an example of the processing flow of the mobility service management part shown in FIG. It is a figure which shows the GUI image of the in-vehicle terminal installed on the service use vehicle shown in FIG. It is a figure which shows an example of the service definition information provided by the service provider shown in FIG. It is a block diagram of the mobility service metering system using the management server by 2nd Embodiment. It is a figure which shows the structural example of the table provided in the non-declaration vehicle management part shown in FIG. It is a figure which shows the configuration example of the charge plan management table provided in the service metering management unit shown in FIG. FIG. 15 is a diagram showing a configuration example of a service usage status management table for undeclared vehicles provided in the metering processing unit shown in FIG. 15. FIG. 15 is a diagram showing a configuration example of a metering result management table for non-declared vehicles provided in the metering processing unit shown in FIG. 15. It is a flowchart which shows an example of the processing flow of the non-declaration vehicle information management part shown in FIG. It is a block diagram of the mobility service metering system using the management server according to 3rd Embodiment. FIG. 21 is a diagram showing a configuration example of a table provided in the declaration vehicle information management unit shown in FIG. 21. FIG. 21 is a diagram showing a configuration example of a charge plan management table provided in the service metering management unit shown in FIG. 21.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.

The mobility data in the present embodiment refers to data including position information measured by a sensor mounted on each automobile or an in-vehicle terminal, and identification information uniquely identifying an automobile vehicle, an in-vehicle terminal, or the like. The mobility data may include information for identifying an individual driver or the like, and may include a vehicle registration number, an ETC on-board unit ID, communication equipment contractor information, or the like as the identification information.

The service in this embodiment mainly refers to a service related to road traffic. Examples of services related to road traffic include toll road services and hourly parking lot services.

(First Embodiment)
FIG. 1 is a block diagram of a mobility service metering system using a management server according to the first embodiment.

As shown in FIG. 1, the mobility service metering system 100 in this embodiment includes a management console 101, a management server (service management device) 102, a service provider 103, a field 104, a service-using vehicle 105, and an in-vehicle terminal. It has 106, a gateway 107, and a management organization 108 such as map data / vehicle registration information.

The management console 101 has a function of displaying a management screen of the mobility metering system. The management server 102 is a form of realizing a mobility service metering system, and is a server device having a metering system function. The service provider 103 is a provider such as a road management company that provides mobility services. The field 104 is a road traffic resource for which the service usage fee is metered, such as a toll road or an hourly parking lot. The service use vehicle 105 is a vehicle that uses the service in the field 104. The in-vehicle terminal 106 is an in-vehicle terminal mounted on the service-using vehicle 105, and the service-using vehicle 105 becomes a reporting vehicle by mounting the in-vehicle terminal 106. The gateway 107 is a communication facility that communicates between the vehicle-mounted terminal 106 and the management server 102. The map data / vehicle registration information management organization 108 is an organization such as a map management company or a public institution that holds map data and vehicle registration information used in service metering.

The management server 102 includes a mobility data transmission / reception unit 111, a declaration vehicle information management unit 112, a mobility service management unit 113, a metering processing unit 114, and a communication IF (interface) 115.

The mobility data transmission / reception unit 111 receives mobility data including the position information of the service use vehicle 105 from the in-vehicle terminal 106 of the service use vehicle 105 traveling in the field 104 via the gateway 107, or is calculated by the management server 102. It has a function of transmitting service usage amount and usage fee information to the in-vehicle terminal 106.

The declaration vehicle information management unit 112 has a declaration information extraction unit 120, a billing target ID management table 121, a position information shaping unit 122, and a position information management table 123. The declaration vehicle information management unit 112 provides vehicle position information, vehicle identification information, and service use necessary for metering the service usage amount of each service use vehicle 105 from the mobility data input via the mobility data transmission / reception unit 111. Extract and manage personal information.

From the mobility data received by the mobility data transmission / reception unit 111, the declaration information extraction unit 120 obtains the position information of each vehicle, the vehicle registration number that can be a vehicle identifier, the identifier of the in-vehicle terminal 106, and the person to be charged for the service usage fee. Extract the user identifier to be identified.

The billing target ID management table 121 is a table that manages ID information for uniquely identifying a billing target person for a service usage fee by a vehicle. The billing target ID management table 121 registers the vehicle identifier and the user identifier extracted by the declaration information extraction unit 120 in association with the unique billing target ID. In addition, the vehicle identifier manages the size of the vehicle involved in determining the price plan.

When the position information extracted from the mobility data is encrypted or encoded, or when the format of the position information is not unified (for example, the specification is decimal, but the received data is received by the position information shaping unit 122). Data is decrypted and formatted (in the case of sexagesimal).

The position information management table 123 includes the position information shaped by the position information shaping unit 122 and the vehicle identifier to which the position information is transmitted for each service use vehicle in order to specify where the service use vehicle 104 was at a certain time. , The measurement date and time of the location information is managed in association with the location information identifier.

The mobility service management unit 113 has a service metering management unit 130 and a service resource management unit 131. The mobility service management unit 113 has a function of managing service definition information such as metering definition information (described later) managed by the service metering management unit 130 and field definition information (described later) managed by the service resource management unit 131. .. The mobility service management unit 113 receives the service definition information 160 from the service provider 103 via the communication IF 115.

The service definition information 160 is composed of metering definition information 161 that defines a service usage amount metering using mobility data and a usage charge calculation method, and field definition information 162 that defines a range of fields 104 to which a service is provided. To. The mobility service management unit 113 provides the metering definition information 161 to the service metering management unit 130, and the field definition information 162 to the service resource management unit 131. Both the metering definition information 161 and the field definition information 162 are dynamically changed by the service provider 103 in consideration of changes in the external environment such as road congestion.

The metering definition information 161 includes a usage amount calculation logic, a logic provision start / end time, a charge plan, and a definition of a vehicle type to which the charge plan is applied. The usage amount calculation logic is information including a data processing method or a processing program for measuring the service usage amount from the mobility data. The logic provision start / end time is information for selecting the usage amount calculation logic to be applied from the measurement date and time of the mobility data. The charge plan is information including a data processing method or program for converting the measured service usage amount into a service usage charge. The vehicle type is information indicating the attributes of an automobile such as a vehicle size, an application, an internal combustion engine, and the like.

The field definition information 162 includes information for designating a road, a lane on the road, a roadside parking lot, etc. included in the field 104 to which the service is provided, and a vehicle type for designating a vehicle to be provided with the service.

The mobility service management unit 113 receives the map / vehicle registration information 170 required for metering processing from the map data / vehicle registration information management organization 108 via the communication IF 115. The map information 171 is information indicating the position information and shape of each road traffic resource and the connection relationship between the resources. The vehicle registration information 172 is information that is a set of an identifier that uniquely identifies a vehicle, such as a vehicle registration number, an identifier of a registered holder, and a vehicle type. The map / vehicle registration information 170 is managed by the service resource management unit 131.

In the present embodiment, the business operator that provides the mobility service metering system 100 and the service business operator 103 are assumed to be different business operators, but the service business operator 103 provides the metering system 100 to the company or another company. May be good.

The service metering management unit 130 has a metering logic management table 132 and a rate plan management table 133. The service metering management unit 130 indicates the time for applying the usage amount calculation logic of the metering definition information 161 indicating the metering logic which is the usage amount calculation method input from the mobility service management unit 113. The metering logic management table 132 is registered and managed together with the application time information, and the rate plan information input from the mobility service management unit 113 is registered and managed in the rate plan management table 133. At that time, the service metering management unit 130 converts the service definition information input by the service provider 103 to generate metering logic management information, and registers and manages the metering logic management table 132. As a result, the service provider can input the service definition information in a format that is easy to input.
The service metering management unit 130 also has a function of searching for and providing data in response to a reference request for data registered in the metering logic management table 132 and the rate plan management table 133 from the metering processing unit 114. Have.

The metering logic management table 132 uses the usage amount calculation logic required for the metering processing unit 114 to calculate the service usage amount from the mobility data, using the measurement date and time of the mobility data and the service resource in use as a query. For reference, it is a table that manages the identifier of the service resource to which the usage amount calculation logic is applied, the logic application start / end date / time information, and the logic information in association with each other.

The charge plan management table 133 is a vehicle type to which the charge plan is applied and a charge plan in order to refer to a different charge plan for each vehicle type when converting the service usage amount calculated from the mobility data into the charge information. It is a table that manages by associating with.

The service resource management unit 131 includes a service resource management table 135, a map / road information management table 136, a vehicle registration information management table 137, and a map matching processing unit 138. The service resource management unit 131 converts the field definition information to which the service is provided into the service resource information, registers it in the service resource management table 135, and manages it. The service resource information is information expressing the road lanes and the like constituting the field 104 in position information (latitude and longitude) in order to determine the use of the field 104 by the service-using vehicle 105 by the position information of the mobility data. Further, since the field 104 may be different for each vehicle type even at the same date and time, the service resource information includes the road traffic resource defining the field 104 and the specific road traffic resource provided as a paid service. Hold the vehicle type together. As a case of providing a service in which the field 104 differs depending on the vehicle type, for example, the overtaking lane may be a paid service only for a gasoline vehicle having a high environmental load. The service resource management unit 131 converts the field definition information 162 provided by the mobility service management unit 113 into service resource information and registers it in the service resource management table. For example, the service resource management unit 131 may consider that the field definition information 162 provided by the service provider 103 is such as "a roadside parking lot in the area A surrounded by four points of location information". The location information of the four points and the information "roadside parking lot" are converted into service resource information including the location information of each roadside parking lot included in the range. The conversion process is performed using the map matching process unit 138. The converted information is registered and managed in the service resource management table 135. The service resource management unit 131 receives the vehicle registration information 172 such as the map information 171 and the vehicle registration number input from the mobility service management unit 113, and receives the map / road information management table 136 and the vehicle registration information management table 137, respectively. It also has a function to update sequentially.

Further, the service resource management unit 131 searches for information registered in the service resource management table 135, the map / road information management table 136, and the vehicle registration information management table 137 in response to a request from the mobility service management unit 113. It also provides a function to do.

The service resource management table 135 is a table for grouping and managing the service resources constituting the individual fields 104 in order to identify the field 104 including the service resource from the identifier of the service resource used by the service use vehicle 105. Is. The service resource management table 135 associates a resource group consisting of one or more service resources to be serviced with a vehicle type to which paid services are provided so that different fields 104 can be defined for each vehicle type. to manage.

The map / road information management table 136 is a table for managing road traffic resources provided by the map data / vehicle registration information management organization 108. The map / road information management table 136 uses the map matching processing unit 138 (described later) for individual road traffic resources in order to identify the nearest road traffic resource with respect to any input position information. , Manages the correspondence between resource types, resource shapes based on location information (positioning points), and connection information between resources. That is, the service resource management unit 131 receives the geographical configuration information including the resource position information indicating the position of the service resource available by the vehicle from the map data / vehicle registration information management organization 108, and uses the map / road information management table 136. to manage.

The vehicle registration information management table 137 manages the vehicle registration information provided by the management organization 108 such as map data / vehicle registration information, and in order to estimate the vehicle type of the service-using vehicle 105 from the vehicle registration number, the vehicle registration number and the vehicle registration number It is a table managed in association with the vehicle type of the registered vehicle.

The map matching processing unit 138 is closest to the input latitude / longitude from the latitude / longitude information input by the service resource management unit 131 when the service resource management unit 131 converts the field definition information 162 into the service resource information. Provides the ability to calculate and identify service resources. Further, the map matching processing unit 138 also provides a function of specifying service resource information included in the area designated by the latitude / longitude information. When specifying a service resource by specifying an area, it also provides a function of specifying and specifying the type of service resource, for example, specifying only a roadside parking lot in the area. The service resource to be searched in the specific process is the service resource managed by the map / road information management table 136.

The metering processing unit 114 includes a service resource usage determination unit 140, a service usage status management table 141, a service usage amount calculation unit 142, a usage charge calculation unit 143, and a metering result management table 144. The service usage amount calculation unit 142 has a metering logic application unit 145. The usage charge calculation unit 143 has a charge plan application unit 146. The metering processing unit 114 shapes the received mobility data by the reporting vehicle information management unit 112, registers it in the billing target ID management table 121 and the location information management table 123, and then provides the processed mobility via the communication IF 115. Accept data. The processed mobility data includes an identifier of the vehicle that is the source of the mobility data and an identifier of the formatted location information. By using these identifiers, the position information and the vehicle type managed by the declared vehicle information management unit 112 are appropriately referred to and used.

The service resource usage determination unit 140 is based on the position information and vehicle type included in the processed mobility data managed by the declaration vehicle information management unit 112 and the information registered in the map / road information management table 136. The use of the service resource by the service use vehicle 105 is determined. Then, as a result of the service usage determination, with respect to the processed mobility data expected to be used by the service, the usage resource information regarding the service resource used by the service using vehicle 105 and the usage time information indicating the time when the service using vehicle 105 uses the service resource. The service usage status management information including and is generated and registered in the service usage status management table 141 together with the identifier of the resource group expected to be used.

The service usage status management table 141 is a table for accumulating the determination results of the service resource usage determination unit 140. The usage charge calculation unit 142 accumulates the judgment result of whether or not the service is used in order to measure the service usage amount of each service use vehicle 105. The service usage status management table 141 is expected to be used with the identifier of the location information, the measurement date and time, and the identifier of the service usage vehicle 105 included in the service usage status management information for the processed mobility data in which the service is expected to be used. Manage by associating resource group identifiers.

The service usage amount calculation unit 142 refers to the service usage status management information registered as the service usage determination result in the service usage status management table 141 and the information registered in the metering logic management table 132, and the service usage vehicle 105 refers to the service usage vehicle 105. It has a function of calculating the service usage amount related to the use of the service resource by the service use vehicle 105 based on the time when the service resource is used and the usage amount calculation method by the metering logic applied to the time. The service usage amount calculation unit 142 acquires data having an identifier of an arbitrary service use vehicle 105 from the service usage status management table 141, sorts the data in chronological order, and applies the calculation process. Each sorted data includes an identifier of position information, and the time change of the position information of the target vehicle can be acquired. By using the time change of the location information, for example, the usage amount of the toll road service is calculated based on the distance traveled in the field 104, and the usage amount of the roadside parking lot service is the time spent in a specific parking lot. You can calculate the usage amount with. In a service in which the metering information required for usage calculation is dynamically changed, the setting of the service usage fee may change while driving on a toll road. In such cases, there is more than one metering information to apply to the sorted data. The service usage amount calculation unit 142 appropriately selects and applies appropriate metering information from the resource group (field 104) in use and the position measurement time contained in the sorted individual data, and applies the usage amount. calculate.

The usage charge calculation unit 143 calculates the service usage charge finally imposed on the service user by using the service usage amount calculated by the service usage amount calculation unit 142 and the charge plan information held in the charge plan management table 134. do. The usage charge calculation unit 143 registers the calculation result in the metering result management table 144.

The metering result management table 144 is a table that manages the results calculated by the usage charge calculation unit 143. The metering result management table 144 manages the identifier, the charge, and the collection state of the service user 105 in association with each other. The metering result management table 144 may include the usage amount calculation logic applied at the time of metering and the position information ID 221.

The communication IF 115 has an API (Application Programming Interface) 150 and a GUI (Graphical User Interface) 151. The management server 102 exchanges data by communication with the management console 101, the service provider 103, and the map data / vehicle registration information management organization 108 via the communication IF 115. For example, the data exchanged with the service provider 103 is metering definition information 161 and field definition information 162. The data exchanged with the map data / vehicle registration information management organization 108 is map information 171 and vehicle registration information 172. The API 150 exchanges these definition information and data in, for example, JSON (JavaScript Object Notation) format (Javascript is a registered trademark). Further, inside the management server 102, the declaration vehicle information management unit 112, the mobility service management unit 113, and the metering processing unit 114 can exchange data with each other via the communication IF 115.

FIG. 2 is a diagram showing an example of the hardware configuration of the management server 102 shown in FIG.

The management server 102 shown in FIG. 1 is, for example, a general computer, and as shown in FIG. 2, a CPU (Central Processing Unit) 1301, a memory 1302, an auxiliary storage device 1303, a communication interface 1304, a media interface 1305, and so on. The input / output device 1306 is provided. Further, the external storage medium 1307 is connected via the media interface 1305. Further, it connects to the management console 101 via the network 1308 via the communication interface 1304.

The CPU 1301 executes a program stored in the memory 1302 or the auxiliary storage device 1303, and executes various processes using the data stored in the memory 1302 or the auxiliary storage device 1303.

The memory 1302 is, for example, a RAM (Random Access Memory), and stores a program executed by the CPU 1301, data, and the like.

The auxiliary storage device 1303 is, for example, a bird disk, a flash memory, a RAM, or the like, and stores a program executed by the CPU 1301 and data used by the CPU 1301.

The communication interface 1304 is an interface for communicating with another device (a communication device owned by an in-vehicle terminal 105 or a service provider 103, etc.) via the network 1308.

The media interface 1305 is removable from the external storage medium 1307 and mediates the input / output of data to / from the external storage medium 1307.

The input / output device 1306 is connected to the console 101 operated by the administrator of the management server 102, and inputs / outputs information to / from the console 101.

Each functional unit mounted on the management server 102 shown in FIG. 1 is realized by the CPU 1301 reading and executing a program stored in the auxiliary storage device 1303 or the memory 1302. Further, the information managed by each functional unit included in the management server 102 is stored in the memory 1302 and the auxiliary storage device 1303.

The program executed by the CPU 1301 may be acquired via the communication interface 1304 or may be acquired from an available external storage medium via the media interface 1305, if necessary. Further, the management server 102 is not only mounted on the hardware shown in FIG. 2, but also deployed on the cloud that provides the computing power of the physical hardware as a logically divided virtual environment service. You may.

FIG. 3 is a diagram showing a configuration example of a table provided in the declaration vehicle information management unit 112 shown in FIG. The tables included in the declaration vehicle information management unit 112 include (a) a billing target ID management table 121 and (b) a location information management table 123.

As shown in FIG. 3A, the billing target ID management table 121 is composed of a billing target ID 201, a user ID 202, a vehicle ID 203, and a vehicle type 204. The billing target ID management table 121 is a table for the purpose of managing information for identifying a service-using vehicle. The billing target ID 201 is an ID assigned to each vehicle in order to manage the combination of the user ID 202 and the vehicle ID 203. The user ID 202 is an identifier that identifies an individual or a corporation for which service charges are to be collected, such as an individual number, an ETC card number, a driver's license number, and an in-vehicle terminal ID. The vehicle ID 203 is ID information that can uniquely identify a vehicle, such as a vehicle number. The vehicle type 204 is information indicating the attributes of the vehicle specified by the vehicle ID 203, and is, for example, a vehicle size classification, a vehicle body application, a fuel type, etc., and is a query for the vehicle ID 203 when it is not included in the mobility data. This is information acquired by referring to the vehicle registration information management table 137.

When the declaration information extraction unit 120 extracts individual data from the received mobility data, the user ID 202, the vehicle ID 203, and the vehicle type 204 constituting the billing target ID management table 121 are managed by the billing target ID management table 121. It is determined whether or not the combination is not performed, and if the combination is not managed, a new charge target ID 201 is assigned and registered in the table.

As shown in FIG. 3B, the position information management table 123 is composed of a position information ID 221, a charge target ID 222, a position measurement date and time 223, and a position information 224. The position information management table 123 is a table that manages all the position data received from the service-using vehicle 104. The location information ID 221 is a value that identifies individual mobility data received by the management server 102, and is uniquely assigned to the mobility data by the declaration information extraction unit 120. The billing position information ID 221 is a value that identifies individual mobility data received by the management server 102, and is issued for each mobility data by the declaration information extraction unit 120. The billing target ID 222 is a value that identifies the source of the mobility data. The position measurement date and time 223 is a time stamp indicating the date and time when the position was measured by the source vehicle. The position information 224 is vehicle position information and is absolute position information such as latitude / longitude and altitude.

The position information ID 221 constituting the position information management table 123 is identifier information newly issued when the declaration information extraction unit 120 receives the mobility data. The declaration information extraction unit 120 uses the billing target ID 201, which is an identifier of the mobility data sender, the time stamp included in the mobility data, and the position information formatted by the position information shaping unit 122, respectively, for the billing target ID 222 and the position measurement date and time. As 223 and position information 224, they are registered in the position information management table 123 in association with the position information ID 221.

FIG. 4 is a diagram showing a configuration example of the metering logic management table 132 included in the service metering management unit 130 shown in FIG.

As shown in FIG. 4, the metering logic management table 132 includes a logic ID 301, a logic application start date / time 302, a logic application end date / time 303, a resource group ID 304, and a usage amount calculation logic 305. The logic ID 301 is an identifier given to each record by the service metering management unit 130 in order to identify each usage amount calculation logic. The logic application start date and time 302 is the application start time of the metering logic specified in each record. The logic application end date and time 303 is the application end time of the metering logic specified in each record. The logic application start date and time 302 and the logic application end date and time 303 may be collectively referred to as application time information. The resource group ID 304 is information that specifies a service resource for which the service usage amount is to be measured. In the resource group, for example, when the resource is set as an area between intersections, the resource constituting the section to be measured of the service usage amount is set as one group. The usage amount calculation logic 305 is arithmetic processing information for calculating the service usage amount. Specific examples of arithmetic processing are shown in records 311 to 313. Record 311 shows the usage amount calculation process of the toll road service as an example, and is a calculation that estimates the movement route from the mobility data of an arbitrary vehicle and calculates the usage amount from the mileage of the movement route and the continuous usage status of the toll road. The process definition is described. The usage amount included in the usage amount calculation logic 305 is a concept close to the usage fee, but the usage fee is not determined only by this usage amount, but for example, the usage fee is determined from the usage amount and the attribute of the vehicle. Is determined. Further, it may be used to set points to be given to the user instead of the usage fee.

In the logic application start date and time 302, the logic application end date and time 303, and the usage amount calculation logic 305 constituting the metering logic management table 132, the service metering management unit 130 receives metering definition information 161 from the mobility service management unit 113. At the time of acceptance, the corresponding information is extracted from the input information and registered in the metering logic management table 132. At that time, the service metering management unit 130 newly issues the logic ID 301 in order to identify the combination of the logic application start date / time 302, the logic application end date / time 303, and the usage amount calculation logic 305. When the service resource management unit 131 converts the field definition information 162 received from the service provider 102 into service resource information, the resource group ID 305 is newly issued to the converted service resource group by the service resource management unit 131. Obtain and register the identifier.

FIG. 5 is a diagram showing a configuration example of the charge plan management table 133 included in the service metering management unit 130 shown in FIG.

As shown in FIG. 5, the charge plan configuration table 133 shown in FIG. 1 is composed of a plan ID 401, a vehicle type 402, and a charge plan 403, and is a logic for calculating a usage charge from the usage amount. By using this charge plan configuration table 133 for calculating the service usage charge, it is possible to calculate the service usage charge to which a different charge plan is applied for each vehicle type. The plan ID 401 is an identifier of each record 411 to 413. The vehicle type 402 is information indicating the attributes of the vehicle to which the rate plan is applied. For example, the records 411 and 413 are all information about an EV vehicle whose vehicle type is a sedan type, but they are different records because the vehicle body usage is different, and the charge plan 403 is also different. The charge plan 403 defines a processing method or program for changing the service usage amount calculated by using the usage amount calculation logic 305 into the usage charge information.

The vehicle type 402 constituting the charge plan configuration table 133 and the charge plan 403 are described as the vehicle type 402 from the acquired information when the service metering management unit 130 acquires the metering definition information 161 from the mobility service management unit 113. Extract and register the rate plan 403. If there is no record that matches the extracted vehicle type in the charge plan configuration table 133, the service metering management unit 130 issues a new plan ID 401, and the plan ID 401, the vehicle type 402, and the charge plan 403 are added to the charge plan management table. To register with. If there is a record with a vehicle type that matches the extracted vehicle type, replace only the rate plan 403 with the new rate plan.

FIG. 6 is a diagram showing a configuration example of the service resource management table 135 included in the service resource management unit 130 shown in FIG.

As shown in FIG. 6, the service resource management table 135 includes a resource group ID 501, a vehicle type 502, and a measurement target resource 503. The resource group ID 501 is information that identifies each record 511 to 513. Each resource group having the resource group ID 501 is composed of a vehicle type 502 to be serviced and a measurement target resource 503 indicating a road traffic resource constituting the field 104. The information constituting the measurement target resource 503 is the identifier information (resource ID 601) of each road traffic facility managed in the map / road configuration information management table 136, such as intersections between roads constituting the section to be used. It is composed of information indicating the branch point and lane of. By identifying the lane, for example, it is possible to set a higher usage fee for the overtaking lane.

The resource group ID 501 and the vehicle type 502 constituting the service resource management table 135 are registered when the field definition information 162 is provided by the mobility service management unit 113. When the service resource management unit 131 acquires the field definition information 162, it first issues the resource group ID 501 and acquires the vehicle type 502 from the mobility service management unit 113, and registers the vehicle type 502 in the service resource management table 135. Next, the acquired field definition information 162 is converted into service resource information and registered as the measurement target resource 503.

FIG. 7 is a diagram showing a configuration example of the map / road configuration information management table 136 included in the service resource management unit 130 shown in FIG.

As shown in FIG. 7, the map / road configuration information management table 130 shown in FIG. 1 is composed of a resource ID 601, a resource type 602, a configuration positioning point 603, and an inter-resource connection information 604. The resource ID 601 is an identifier of each record 611 to 612. Each record is information indicating the minimum structural unit of a road transportation facility. On a general road, a specific lane between intersections is the minimum unit, and in a roadside parking lot, a parking space for one car is the minimum unit. The resource type 602 is information indicating the type of road transportation facility, for example, a general road of record 611, a roadside parking lot of record 612, and the like. The configuration positioning point 603 is a positioning point composed of latitude and longitude indicating the shape of the road traffic facility of each record. For example, in a record of a general road where the resource type 602 is a straight road, it is composed of two endpoints, and when there is a curve, it is composed of three or more endpoints. Further, the resource type 602 is a point indicating the position in the record of the roadside parking lot. When a vacant lot is set as the resource type 602, it is conceivable to set four points of the parking space as positioning points. The inter-resource connection information 604 is information indicating the resource to be connected. For example, a one-lane road has two different resource IDs that connect to the endpoints of the road.

The resource type 602, the configuration positioning point 603, and the inter-resource connection information 604 that configure the map / road configuration information management table 130 are registered by the service resource management unit 131. The map data / vehicle registration information management organization 108 inputs the change information to the service resource management unit 131 every time there is a change in the shape or configuration of the map or the road. The service resource management unit 131 extracts and registers the resource type 602, the configuration positioning point 603, and the information corresponding to the inter-resource connection information 604 from the input information. The resource ID 601 may be issued by the service resource management unit 131 when there is new registration information, or when the map data / vehicle registration information management organization 108 has a unique identifier for each resource, the resource ID 601 may be issued by the service resource management unit 131. The identifier may be registered as the resource ID 601.

FIG. 8 is a diagram showing a configuration example of the vehicle registration information management table 137 included in the service resource management unit 130 shown in FIG.

As shown in FIG. 8, the vehicle registration information management table 137 shown in FIG. 1 is composed of a vehicle registration number 701, a vehicle type 702, and a registration holder ID 703. The vehicle registration number 701 is identifier information that uniquely identifies a vehicle, and as an example, there is a vehicle registration number plate registered in a transportation agency. The vehicle type 702 is vehicle attribute information indicating the size and use of the vehicle, the fuel mechanism, and the like. The registered name 703 is vehicle owner information that is an individual or a corporation.

The vehicle registration number 701, the vehicle type 702, and the registration holder ID 703 that constitute the vehicle registration information management table 137 are registered by the service resource management unit 131. The map data / vehicle registration information management organization 108 inputs the change information to the management server 102 every time there is a change in the vehicle registration number information to be managed. The service resource management unit 131 extracts and registers the vehicle registration number 701, the vehicle type 702, and the registration holder ID 703 from the input information.

FIG. 9 is a diagram showing a configuration example of the service usage status management table 141 included in the metering processing unit 114 shown in FIG.

As shown in FIG. 9, the service usage status management table 141 shown in FIG. 1 is composed of a billing target ID 801, a measurement date and time 802 as usage time information, a resource group ID 803 as usage resource information, and a location information ID 804. It is composed. The service usage status management table 141 is a set of processed mobility data input from the declaration information management unit 112 whose location information is included in the measurement target resource 503 of the service resource management table 135. The billing target ID 801 is information that uniquely identifies the service user. The measurement date and time 802 is a time stamp at the time of measuring mobility data. The resource group ID 803 is a resource group ID 501 in which the location information and the measurement target resource 503 of the resource group match among the resource groups managed in the service resource management table 135. The position information position information ID 804 is information for identifying the position information that matches the measurement target resource 503 among the position information managed by the position information management table 123, and is different from the information indicating the latitude and longitude.

The billing target ID 801 constituting the service usage status management table 141, the measurement date and time 802, the resource group ID 803, and the location information ID 804 are information registered by the service resource usage determination unit 140. After the declaration vehicle information management unit 112 acquires new mobility data, the service resource usage determination unit 140 receives the billing target ID 201, the vehicle type 204, the position information ID 221 and the position measurement date and time 222 from the declaration vehicle information management unit 112. Receives input of processed mobility data including. The service resource usage determination unit 140 acquires the resource ID closest to the input position information from the map matching processing unit 138, and searches the service resource management table 135 using the resource ID and the vehicle type 204 as a query. If there is a resource group ID 501 that hits as a result of the search, it is determined that the service is expected to be used, and the billing target ID 201, the location measurement date / time ID 223, the resource group ID 501, and the location information ID 221 are measured as the billing target ID 801 respectively. Register as the date and time 802, the resource group ID 803, and the location information ID 804.

FIG. 10 is a diagram showing a configuration example of the metering result management table 146 included in the metering processing unit 114 shown in FIG. 1.

As shown in FIG. 10, the metering result management table 171 shown in FIG. 1 is composed of a charge target ID 901, a collection state 902, an application logic ID array 903, evidence 904, and a charge 905. Each record 911, 912 is a metering result of one service use of the service use vehicle 104, respectively. The billing target ID 901 is identifier information that identifies the service-using vehicle 104. The collection state 902 is flag information indicating whether or not the metering result has already been collected. The applied logic ID array 903 is an array of logic ID 301 applied at the time of metering. The logic ID 301 may be applied one or more at one time of using the service, and holds all the applied logic ID 301s. For example, when moving by connecting different highways, the application logic of each highway is arranged. Evidence 904 is an array of location information ID 804 used during metering. The charge 905 is the final service usage charge calculated as a result of metering.

The billing target ID 901, the application logic ID array, and the evidence 904 constituting the metering result management table 144 are registered by the service usage amount calculation unit 142. The service usage amount calculation unit 142 receives input from the service resource usage determination unit 140 of the billing target ID 201 that is expected to end the service use. The service usage amount calculation unit 142 acquires the data of the service usage status management table 141 by using the input billing target ID 201 as a query, and performs the usage amount calculation process. The service usage amount calculation unit 142 uses the billing target ID 801 for which the calculation process has been performed, the resource group ID 803 included in the acquired data as a query, and the aggregate data of the logic ID 301 obtained from the metering logic management table 133, and the acquired data. The set data of the included position information ID 804 is registered in the billing target ID 901, the application logic ID array 903, and the evidence 904, respectively. The charge 905 constituting the metering result management table 144 is registered by the usage charge calculation unit 143 after converting the usage amount calculated by the service usage amount calculation unit 142 into a usage charge. The collection state 902 constituting the metering result management table 144 inputs the "uncollected" flag at the time of registering the service usage fee, and after the service provider 102 or the management console 101 finishes collecting the fee, " Enter the Collected flag.

The service management method in the management server 102 configured as described above will be described below.

First, the processing in the metering processing unit 114 will be described.

FIG. 11 is a flowchart showing an example of the processing flow of the metering processing unit 114 shown in FIG.

The processing flow of the metering processing unit 114 is described in steps 1010 to 1016 carried out by the service resource usage determination unit 140, steps 1020 to 1025 carried out by the service usage amount calculation unit 142, and the usage charge calculation unit 144. It is composed of steps 1030 to 1032 to be carried out.

The service resource usage determination unit 140 executes a series of processes from step 1010 to step 1016 in a loop for each processed mobility data input from the declaration vehicle information management unit 112.

First, in step 1011 the service resource utilization determination unit 140 acquires the resource group ID 501 from the service resource management unit 131 by using the vehicle type 204 specified from the processed mobility data and the location information 224 as a query. The vehicle type 204 of the query is specified from the vehicle identification information (vehicle ID) included in the processed mobility data by referring to the billing target ID management table 121. The location information of the query is converted into the resource ID 601 by the map matching processing unit 138 at the time of searching, and then the search processing is executed.

Next, in step 1012, the service resource usage determination unit 140 performs conditional branching based on the search result of the resource group ID 501. If there is a resource group ID that hits the search, it means that the service is used in the field 104 for the location information of the query.

When there is a resource group ID (step 1012 is TRUE), the service resource usage determination unit 140 registers the resource group ID 501, the billing target ID, and the like in the service usage status management table 141 in step 1014.

On the other hand, when there is no resource group ID (step 1012 is FALSE), the service resource usage determination unit 140 searches the service usage status management table 141 for a record having a chargeable ID of the mobility data source vehicle in step 1013. , Determine if there is a record.

If there is no record (step 1013 is FALSE), it means that the source vehicle of the mobility data being processed is not currently using any service, so that the service resource usage determination unit 140 loops in step 1016. The process ends and the process returns to S1010.

On the other hand, there is a record (when step 1013 is TRUE, it indicates that the vehicle that sent the mobility data used the service but is not using the service now, so the service resource is used. The determination unit 140 determines that the service usage has been completed, and shifts to the processing of the service usage amount calculation unit 143.

First, in step 1020, the service usage amount calculation unit 143 acquires a record having a charge target ID included in the processed mobility data from the service usage status management table 141. In steps 1021 to 1023, as loop 2 processing for each acquired record, the service usage amount calculation unit 143 uses the resource group ID 803 and the location information measurement date and time 802 included in the acquired records as queries in the meter in step 1022. Acquire the metering logic ID 301 from the ring logic management table 132.

Next, in step 1024, the service usage amount calculation unit 143 groups the records acquired in step 1020 by the metering logic ID 301 acquired in step 1022.

In steps 1025 to 1027, the service usage amount calculation unit 143 executes loop 3 processing on the grouped records (data series).

In the loop 3 process, in step 1025, the service usage amount calculation unit 143 first uses the grouped data series in order from the oldest position measurement date and time.

Next, in step 1026, the service usage amount calculation unit 143 applies the usage amount calculation logic 305 having the corresponding logic ID 301 to the grouped data series, and calculates the service usage amount.

In step 1027, the service usage amount calculation unit 143 sequentially totals the service usage amount for each data series and processes the next data series.

First, in step 1030, the usage charge calculation unit 144 acquires a plan 403 from the charge plan management table 134a using the vehicle type of the target vehicle as a query in order to calculate the usage charge from the total of the calculated service usage amounts. ..

Next, in step 1031, the usage charge calculation unit 144 calculates the service usage amount by multiplying the calculated service usage amount and the acquired plan information. That is, the usage charge calculation unit 144 is registered in the service usage amount calculated by the service usage charge calculation unit 142, the metering logic registered in the metering logic management table 132, and the vehicle registration information management table 137. The service usage fee of the service usage vehicle 105 will be calculated based on the information.

After that, the usage charge calculation unit 143 stores the service usage charge information calculated in step 1032 in the metering result management table 144.

Next, the process in the mobility service management unit 113 will be described.

FIG. 12 is a flowchart showing an example of the processing flow of the mobility service management unit 113 shown in FIG.

The processing flow of the mobility service management unit 113 includes steps 1110 to 1111 executed by the service provider 103, steps 1120 to 1121 executed by the mobility service management unit 113, and steps 1130 to implemented by the service resource management unit 131. It is composed of step 1131, step 1140 carried out by the mobility service management unit 113, and steps 1150 to 1152 carried out by the service metering management unit 130.

The service provider 101 creates the service definition information 161 in step 1110. The service provider 101 sets the billing target vehicle type, the metering logic, the logic application period, the section, the charge plan, etc. that constitute the metering definition information 161 included in the service definition information 161 with reference to the road congestion information and the like. Create an item.

In step 1111, the service provider 101 inputs the setting information related to the metering created by the service provider 101 to the communication ID 115.

First, in step 1120, the mobility service management unit 131 acquires setting information related to metering by the mobility service management unit 131 via the communication ID 115.

Next, in step 1121, the mobility service management unit 113 inputs the field definition information 162 to the service resource management unit 131.

Next, in step 1130, the service resource management unit 131 converts the field definition information 162 into the service resource information represented by the resource ID 601 managed in the map / road information management table 136 by using the map matching processing unit 138. do. The converted section information is data as shown in the measurement target resource 503 of the service resource management table 135.

Next, in step 1131, the service resource management unit 131 registers the target vehicle type and the formatted section information in the service resource management table 135, and issues a new resource group ID 501.

Next, in step 1140, the mobility service management unit 113 inputs the metering definition information 161 and the resource group ID 501 issued in S1131 to the service metering management unit 130.

Next, in step 1150, the service metering management unit 130 registers the resource group ID 501, the usage amount calculation logic 305, and the logic application period (302, 303) in the metering logic management table 132.

In step 1151, the service metering management unit 130 determines whether or not there is a change in the rate plan in the setting items related to metering.

When the change of the charge plan is confirmed in step 1151, the service metering management unit 130 registers the changed charge plan and the target vehicle type in the charge plan management unit 133 in step 1152.

FIG. 13 is a diagram showing a GUI image of an in-vehicle terminal 106 installed on the service utilization vehicle 105 shown in FIG.

As shown in FIG. 13, it is conceivable to display the service metering result notification message 1203 and the currently available service information 1204a and 1204b on the display panel 1202 mounted on the car navigation system (car navigation system) 1201. In the one shown in FIG. 13, various information notified through the service provider 102 is displayed on the display panel 1202 mounted on the car navigation system 1201, but the in-vehicle terminal used for the display is a smartphone or a head. It may be an up display, and display information may be notified as voice information from an in-vehicle terminal having a voice information transmission function such as an ETC terminal. The service metering result notification message 1203 is an example of a message displayed when the service charge information calculated by the management server 101 is notified from the service provider 102 to the in-vehicle terminal 104a. The service information 1204a and 1204b are information regarding the services currently available, which are notified from the service provider 102 to the service use vehicle 105.

FIG. 14 is a diagram showing an example of the service definition information 160 provided by the service provider 103 shown in FIG.

In the service provider 103 shown in FIG. 1, for example, as shown in FIG. 14, the service definition information 2300 including metering definition information 2310 and field definition information 2320 is provided to the management server 102 to perform the above-mentioned processing. Will be executed.

As described above, in the present embodiment, the calculation method of the service usage amount is managed together with the time when the calculation method is applied and used for the calculation of the service usage amount of the vehicle. Therefore, a flexible service that changes the calculation method depending on the time is available. It will be possible.

(Second embodiment)
In the second embodiment, in addition to the service-using vehicle 105 that can transmit its own mobility data, which was a chargeable vehicle in the first embodiment, the service-using vehicle that cannot transmit mobility data is also subject to service metering. And.

FIG. 15 is a block diagram of a mobility service metering system using the management server according to the second embodiment.

In the description of the present embodiment, the description of the functional unit and the table necessary for performing the service metering for the service-using vehicle that does not transmit the mobility data, which is the difference from the first embodiment, will be mainly described.

As functional units and tables unique to this embodiment, a mobility data reporting vehicle 1401, an in-vehicle camera 1402, a mobility data non-declaring vehicle 1403, a non-declaring vehicle information output unit 1410, a non-declaring vehicle information management unit 1420, and the like. The rate plan management table 1430, the non-declared vehicle compatible service usage status management table 1440, and the non-declared vehicle compatible metering result management table 1441. The non-declared vehicle information management unit 1420 includes a non-declared vehicle mobility data estimation unit 1411, a camera / sensor data processing unit 1422, a non-declared vehicle ID management table 1423, and a non-declared vehicle position information management table 1424.

The mobility data reporting vehicle 1401 is a vehicle that sequentially transmits mobility data including the position information of the own vehicle, vehicle identification information, and the like to the management server 102. The in-vehicle camera 1402 is a camera device mounted on the mobility data reporting vehicle 1401. The camera device may be a camera device having a function of acquiring distance information to a subject in addition to an imaging function, in addition to a general monocular camera. Such camera devices include, for example, a stereo camera that measures the distance from image data obtained by a plurality of camera devices to the subject, or image data acquired by a monocular camera and electromagnetic waves, sound waves, or the like to reach the subject. An example is a combination of a sensing function for measuring a distance. Further, all the vehicles classified in the mobility data reporting vehicle 1401 may not be equipped with the camera device 1402. Mobility data The mobility data of the declaration vehicle 1401 is metered by the declaration vehicle information management unit 112 by the method disclosed in the first embodiment.

The mobility data non-declared vehicle 1403 is a vehicle that does not transmit mobility data including the position information of the own vehicle, vehicle identification information, and the like to the management server 102. The mobility data non-declared vehicle 1403 includes a case where the mobility data of the own vehicle is not acquired and transmitted, or even if there is a data acquisition function, the vehicle is intentionally or intentionally not transmitted to the management server 102.

The non-declared vehicle information output unit 1410 is the processed mobility shaped by the declaring vehicle information management unit 112 when the mobility data transmitted by the mobility data declaring vehicle 1401 includes image data taken by the in-vehicle camera 1402. It has a function to output data to the undeclared vehicle information management unit 1420. The processed mobility data to be output includes the billing target ID 201 which is the identification information of the source vehicle, the position information ID 221 of the source vehicle, the position measurement date and time 223, the shaped position information 224, and the image data. included. The processed mobility data is transferred through the communication IF 115.

The non-declared vehicle information management unit 1420 estimates the mobility data non-declared vehicle 1403 that does not transmit mobility data among the service-using vehicles reflected in the image data input from the non-declared vehicle information output unit 1410, and obtains the estimated mobility data. Provides the ability to accumulate. The estimated mobility data is relative to the vehicle registration number of the mobility data non-declared vehicle 1403, the identification information of the registered holder, the chargeable ID of the image data shooting vehicle, the position information ID of the shooting vehicle, and the position measurement date and time. Includes position information and position information expressed in latitude and longitude.

Further, the non-declared vehicle information management unit 1420 provides a function of registering or searching the estimated mobility data in the non-declared vehicle ID management table 1423 and the non-declared vehicle position information management table 1424.

The non-declared vehicle mobility data estimation unit 1421 is based on the position information of the source vehicle included in the input processed mobility data and the analysis result of the camera / sensor data processing unit 1422 for the input image data, and the mobility data non-declaration unit is not declared. Estimate mobility data for vehicle 1403.

The non-declared vehicle mobility data estimation unit 1421 obtains the position measurement date and time, the position information, and the registered holder identification information, which are particularly necessary for service metering, among the information constituting the estimated mobility data of the non-declared vehicle mobility data 1403. Identify. The registered holder identification information is information necessary for collecting the service usage fee when the fee cannot be collected using wireless communication.

The non-declared vehicle mobility data estimation unit 1421 uses the position measurement date and time 223 included in the processed mobility data input from the non-declared vehicle information output unit 1410 as the position measurement date and time of the estimated mobility data. The position information of the estimated mobility data uses the position information 224 included in the processed mobility data as a reference position, and synthesizes the relative positions of the photographed vehicle and the photographed vehicle obtained by the analysis processing of the camera / sensor data processing unit 1422 for the image data. Get by doing. The position information and the position measurement date and time of the mobility data non-declared vehicle 1403 are registered in the non-declared vehicle position information management table 1424.

The non-declared vehicle mobility data estimation unit 1421 determines that the registered holder identification information of the mobility data non-declared vehicle 1403 is based on the vehicle registration number information of the photographed vehicle obtained by the analysis processing of the camera / sensor data processing unit 1422 for the image data. Estimate to. The non-declared vehicle mobility data estimation unit 1421 searches the vehicle registration information management table 137 using the acquired vehicle registration number as a query, and uses the registered vehicle individual number 704 included in the search result as vehicle owner identification information. The vehicle owner identification information is registered in the non-declared vehicle ID management table 1423.

The camera / sensor data processing unit 1422 provides a function of acquiring the vehicle registration number of the vehicle to be photographed and the relative position information between the vehicle to be photographed and the vehicle to be photographed from the input image data. The vehicle registration number recognition function may use a general image recognition processing program or artificial intelligence trained with image data of a large number of vehicle registration numbers. Further, the vehicle registration number recognition function may be implemented on the management server 102 or may use an image recognition service outside the management server 102. The relative position information may be something like Euler angles (X, Y, Z) and distance (meters) observed from the shooting vehicle. The relative position information may be used by extracting the direction and distance of the vehicle to be photographed from, for example, depth information obtained from multiple image data captured by a stereo camera or distance sensing information by electromagnetic waves. Alternatively, a rough direction and distance may be estimated from the size of the subject reflected in the image data taken by the monocular camera device and used as relative position information.

The non-declared vehicle ID management table 1423 manages the service usage status by the mobility data non-declared vehicle 1403 and collects the service charge for a specific individual or corporation. It is a table that manages by associating. The vehicle registration number estimated by the undeclared vehicle mobility data estimation unit 1421, the registered owner ID 704 obtained from the vehicle registration information management table 137 using the vehicle registration number as a query, and the vehicle type 702 are managed in association with each other.

The non-declared vehicle position information management table 1424 is a billing target so that the estimated mobility data generated by the non-declared vehicle mobility data estimation unit 1421 can be searched for each charge target ID given to the mobility data non-declared vehicle 1403. It is a table that manages ID, estimated position information, and position measurement date and time in association with each other.

The rate plan management table 1430 defines the vehicle type to which the plan is applied, the mobility data declaration method, and the charge calculation method in order to refer to an appropriate charge plan that differs depending on the vehicle type and the mobility data declaration method. It is a table that manages by associating. The mobility data declaration method includes a self-declaration method in which the service charge is measured by the mobility data transmitted by the user and another vehicle declaration method in which the service charge is measured from the image data included in the mobility data of the other vehicle. It is information that distinguishes.

The service usage status management table 1440 for undeclared vehicles is an individual processed mobility that has received a service usage determination in order to manage the determination result of the service resource usage determination unit 140 and search the usage status of any service usage vehicle. The data is the identifier of the billable person of the mobility data declaring vehicle 1401 or the mobility data non-declaring vehicle 1403, the declaring method of the mobility data, the identifier of the position information, the measurement date and time, and the identifier of the resource group including the resource in use. Are associated and managed.

The metering result management table 1441 for non-declared vehicles is a table for managing and accumulating the calculation results of the usage charge calculation unit 143. The non-declared vehicle-compatible metering result management table 1441 manages data in association with the identifier of the service-using vehicle, the declaration method of mobility data, the charge, and the collection status. The managed data may include logic information applied at the time of metering and position information used for metering as evidence of metering.

FIG. 16 is a diagram showing a configuration example of a table provided in the non-declared vehicle management unit 1420 shown in FIG. The tables provided by the non-declared vehicle management unit 1420 include (a) a non-declared vehicle ID management table 1423 and (b) a non-declared vehicle position information management table 1424.

As shown in FIG. 16, the non-declared vehicle ID management table 1423 shown in FIG. 15 is composed of a billing target ID 1501, a registered owner ID 1502, a vehicle ID 1503, and a vehicle type 1504. The non-declared vehicle ID management table 1423 is a table for the purpose of managing information that identifies individual vehicles that use the service, similar to the billing target ID management table 121 in the first embodiment. However, while the billing target ID management table 121 manages the vehicle identifier of the mobility data reporting vehicle 1501 (service-using vehicle 105 in the first embodiment), the non-declaring vehicle ID management table 1423 manages the mobility data non-declaring vehicle. It manages the vehicle identifier of the vehicle 1503. The billing target ID 1501 is an identifier on the system given to the vehicle ID 1503. The registered holder ID 1502 is information such as the personal number of the vehicle owner set when the vehicle registration number is notified, and is an identifier that identifies an individual or a corporation for which the service fee is to be collected. The vehicle ID 1503 is ID information that can uniquely identify a vehicle, such as a vehicle number. The vehicle type 1504 is information indicating the attributes of the vehicle specified by the vehicle ID 1503.

The billing target ID 1501, the registered owner ID 1502, the vehicle ID 1503, and the vehicle type 1504 constituting the non-declared vehicle ID management table 1423 are the mobility data received and processed by the declared vehicle information management unit 112, and the non-declared vehicle information. It is received by the non-declared vehicle mobility data estimation unit 1421 via the output unit 1410, and is registered after generating the estimated mobility data of the mobility data non-declared vehicle 1403 based on the image data. At this time, the non-declared vehicle mobility data estimation unit 1421 has the vehicle registration number (vehicle ID 1503) acquired from the image data, the registration holder ID 1502 acquired from the vehicle registration information management unit table 137 using this as a query, and the vehicle type. 1504 is input to the non-declared vehicle ID management table 1423, and if there is no record in which the vehicle ID 1503 matches, the billing target ID 1501 is issued and registered.

As shown in FIG. 16B, the non-declared vehicle position information management table 1424 includes a position information ID 1521, a photographer charge target ID 1522, a photographer position information ID 1523, a relative position 1524, a position measurement date and time 1525, and the like. It is composed of position information 1526.

The non-declared vehicle position information management table 1424 is a table that manages the mobility data estimated by the non-declared vehicle mobility data estimation unit 1421, and is a table having the same purpose as the position information management table 123. The location information ID 1521 is an identifier for identifying each estimated mobility data. The photographer charge target ID 1522 is an identifier for identifying the vehicle from which the processed mobility data is transmitted. The photographer position information ID 1523 is an identifier for specifying the position information of the vehicle that is the source of the processed mobility data. The relative position 1524 is the relative position information of the vehicle to be photographed from the imaged vehicle estimated by the camera / sensor data processing unit 1422. This includes, for example, a direction expressed by a distance from the front of the photographing vehicle or a relative angle. The position measurement date and time 1525 is the measurement date and time of the estimated position information. The position information 1526 is the position information of the vehicle to be photographed estimated by the undeclared vehicle mobility data estimation unit 1421, and is the absolute position information such as latitude / longitude and altitude.

Like the non-declared vehicle ID management table 1423, the non-declared vehicle position information management table 1424 estimates the processed mobility data received from the mobility data declaring vehicle 1401 via the non-declared vehicle information output unit 1410. It is created when the mobility data of the mobility data reporting vehicle 1403 received by the unit 1421 and reflected in the image data is estimated.

The photographer charge target ID 1522, the photographer position information ID 1523, the relative position 1524, the position measurement date and time 1525, and the position information 1526 constituting the non-declared vehicle position information management table 1424 are obtained from the non-declared vehicle mobility data estimation unit 1421. When input, the position information ID 1521 is issued and registered for all the input data, unlike the case of the non-declared vehicle ID management table 1423.

FIG. 17 is a diagram showing a configuration example of the rate plan management table 1430 included in the service metering management unit 130 shown in FIG.

As shown in FIG. 15, the rate plan management table 1430 shown in FIG. 15 has one column added to the rate plan management table 133 in the first embodiment, and the purpose of use of the information managed by the table is And the processing related to record registration are the same as those in the rate plan management table 133. The following describes mainly the newly added columns.

The charge plan configuration table 1430 is composed of a plan ID 401, a vehicle type 402, a declaration method 1601, and a plan 403. The filing method 1601 is one of the selection items of the rate plan, and the rate plan (self-reported) applied to the mobility data reporting vehicle 1401 and the rate plan (reported by others) applied to the mobility data non-declared vehicle 1403 are selected. Information for distinguishing. For example, it is conceivable that the rate plan applied to the mobility data non-declared vehicle 1403 is higher than the rate plan applied to the mobility data declared vehicle 1401.

The vehicle type 402 constituting the charge plan configuration table 1430, the declaration method 1601, and the charge plan 403 are used when the service metering management unit 130 acquires metering information from the service provider 103 via the communication IF 115. The vehicle type 402, the declaration method 1601 and the rate plan 403 are extracted and registered from the acquired information. If there is no record that matches the extracted vehicle type and declaration method 1601 in the rate plan configuration table 1430, the service metering management unit 130 issues a new plan ID 401, and the plan ID 401, vehicle type 402, and declaration method 1601 are used. Register plan 403 in the rate plan management table. If there is a record with the extracted vehicle type and declaration method 1601 matching vehicle type and declaration method 1601, only the rate plan 403 is exchanged for the new rate plan.

FIG. 18 is a diagram showing a configuration example of the service usage status management table 1440 for undeclared vehicles included in the metering processing unit 114 shown in FIG.

As shown in FIG. 18, the non-declared vehicle correspondence service usage status management table 1440 included in the metering processing unit 114 shown in FIG. 15 has one column added to the service usage status management table 141 according to the first embodiment. The purpose of use of the information managed in the table, the processing related to the record registration, and the like are the same as those in the service usage status management table 141. The columns newly added will be mainly described below.

The non-declaration vehicle correspondence service usage status management table 1440 has a charge target ID 801, a measurement date and time 802, a declaration method 1701, a resource group ID 803, and a location information ID 804. In the declaration method 1701, the mobility data expected to be used by the service resource usage determination unit 140 is either self-reported data regarding the mobility data reporting vehicle 1401 or data reported by another person regarding the mobility data non-declaring vehicle 1403. It is information for distinguishing between.

The billing target ID 801 constituting the non-declared vehicle support service usage status management table 1440, the measurement date and time 802, the declaration method 1701, the resource group ID 803, and the location information ID 804 are information registered by the service resource usage determination unit 140. be. Every time the declared vehicle information management unit 112 acquires new mobility data, the service resource usage determination unit 140 receives a billing target ID (201 or 1501) from the declared vehicle information management unit 112 or the non-declared vehicle information management unit 1420. The vehicle type (204 or 1504), the position information ID (221 or 1521), and the position measurement date and time (223 or 1525) are input. The service resource usage determination unit 140 acquires the resource ID closest to the input location information from the map matching processing unit 138, and searches the service resource management table 135 using the resource ID and the vehicle type (204 or 1504) as a query. .. If there is a resource group ID 501 that hits as a result of the search, it is determined that the service is expected to be used, and the billing target ID (201 or 1501), the position measurement date / time ID (223 or 1523), the resource group ID 501, and the position are determined. The information ID (221 or 1521) is registered as the charge target ID 801, the measurement date and time 802, the resource group ID 803, and the location information ID 804, respectively. At the same time, in the declaration method 1701, if the registration information is the data input from the declaration vehicle information management unit 112, the "self-declaration" flag is registered, and the registration information is the data input from the non-declaration vehicle information management unit 1420. In that case, register the "Declaration of other vehicle" flag.

FIG. 19 is a diagram showing a configuration example of a metering result management table 1441 for non-declared vehicles included in the metering processing unit 114 shown in FIG.

As shown in FIG. 19 and the metering result management table 1441 for non-declared vehicles provided in the metering processing unit 114 shown in FIG. 15, one column is added to the metering result management table 144 in the first embodiment. The purpose of use of the information managed in the table, the processing related to the record registration, and the like are the same as those of the metering result management table 144. The columns newly added will be mainly described below.

The metering result management table 1441 for non-declared vehicles includes a charge target ID 901, a collection state 902, a declaration method 1801, an applicable logic ID array 903, evidence 904, and a charge 905. The declaration method 1801 is information for distinguishing whether the vehicle whose service usage fee is metered is the mobility data declaration vehicle 1401 or the mobility data non-declaration vehicle 1403.

The billing target ID 901, the declaration method 1801, the applicable logic ID array, and the evidence 904 constituting the metering result management table 1441 for non-declared vehicles are registered by the service usage amount calculation unit 142. The service usage amount calculation unit 142 receives input from the service resource usage determination unit 140 of the billing target ID 201 or 1501 that is expected to end the service use. The service usage amount calculation unit 142 acquires the data of the service usage status management table 1440 for undeclared vehicles by using the input billing target ID as a query, and performs the usage amount calculation process. The service usage amount calculation unit 142 uses the billing target ID 801 that has been calculated, the resource group ID 803 included in the acquired data as a query, and the aggregate data of the logic ID 301 obtained from the metering logic management table 132, and the acquired data. The set data of the included position information ID 804 is registered in the billing target ID 901, the application logic ID array 903, and the evidence 904, respectively. The charge 905 constituting the metering result management table 144 is registered by the usage charge calculation unit 143 after converting the usage amount calculated by the service usage amount calculation unit 142 into a usage charge. At the same time, the collection state 902 inputs the "uncollected" flag at the time of registering the service usage fee, and the declaration method 1801 inputs the declaration method 1701 included in the data acquired from the non-declaration vehicle correspondence service usage status management table 1440. In the collection state 902, the "collected" flag is input via the communication IF 115 after the service provider 102 or the management console 101 has finished collecting the charges.

The processing of the undeclared vehicle information management unit 115 will be described below.

FIG. 20 is a flowchart showing an example of the processing flow of the non-declared vehicle information management unit 115 shown in FIG.

The processing flow of the declared vehicle information management unit 115 shown in FIG. 15 includes steps 1910 to 1911 performed by functional units other than the non-declared vehicle information management unit 115, and steps 1120 performed by the non-declared vehicle information management unit 1420. It is composed of steps 1930 to 1933 carried out by the camera / sensor data processing unit 1422 and steps 1940 to 1947 carried out by the non-declared vehicle mobility data estimation unit 1421. Steps 1940 to 1943 are loop processing (loop 1) for the data of each vehicle to be photographed detected by the camera / sensor data processing unit 1422.

In step 1910, when the mobility data reporting vehicle 1401 transmits the image data of the surrounding road taken by the vehicle-mounted camera 1402 of the own vehicle to the management server 102 together with the mobility data including the position information and the vehicle identifier measured by the own vehicle, the image data is obtained. The mobility data transmission / reception unit 111 receives these mobility data including the above.

Then, in step 1911, the declaring vehicle management unit 112 outputs the billing target ID 201 of the mobility data transmitting vehicle, the position information ID 221 and the image data to the non-declaring vehicle management unit 1420 among the received mobility data.

The non-declared vehicle information management 1420 inputs the input image data of the surrounding road to the camera / sensor data processing unit 1422 in step 1920.

First, in step 1930, the camera / sensor data processing unit 1422 reads the vehicle registration number of the vehicle (vehicle to be photographed) reflected in the input image data.

Next, in step 1931, the camera / sensor data processing unit 1422 estimates the relative positions of the photographing vehicle and the photographed vehicle. For the estimation of the relative position, the depth information generated by the stereo camera or the distance information with the surrounding object acquired by using the electromagnetic wave may be used.

Next, in step 1932, the camera / sensor data processing unit 1422 determines the absolute position (latitude, longitude, etc.) of the photographed vehicle from the position information of the photographing vehicle that can be referred to from the position information ID 221 and the relative position estimated in step 1931. ) Is estimated.

Next, in step 1933, the camera / sensor data processing unit 1422 outputs the vehicle registration number read in step 1931 and the absolute position information of the vehicle to be photographed estimated in step 1932 to the undeclared vehicle mobility data estimation unit 1421. do.

Then, in step 1940, the non-declared vehicle mobility data estimation unit 1421 loops 1 with respect to the data of one or more photographed vehicles input from the camera / sensor data processing unit 1422 with respect to the data of each photographed vehicle. To execute.

Next, in step 1941, the non-declared vehicle mobility data estimation unit 1421 searches for a record in the billing target ID management table 121 by using the vehicle registration number as a query from the data of the vehicle to be photographed input in the loop 1. This is executed to detect whether the vehicle to be photographed is a mobility data declaring vehicle 1401 that transmits its own mobility data or a service use mobility data non-declaring 1403 that does not emit mobility data.

Then, in step 1942, the non-declared vehicle mobility data estimation unit 1421 determines whether or not there is a record that hits the search process.

If there is a record, the non-declared vehicle mobility data estimation unit 1421 determines that the vehicle to be photographed is the mobility data declaring vehicle 1401, proceeds to step 1943, and returns to the loop 1 process for the data of the next photographed vehicle.

On the other hand, if there is no record, the non-declared vehicle mobility data estimation unit 1421 determines that the photographed vehicle is the mobility data non-declared vehicle 1403, and proceeds to step 1944 to continue processing the data of the photographed vehicle. ..

In step 1944, the undeclared vehicle mobility data estimation unit 1421 inquires of the vehicle registration information management unit 137 for the vehicle registration number included in the data of the vehicle to be photographed, and acquires the vehicle type 702 and the registered owner ID 703.

Next, in step 1945, the undeclared vehicle mobility data estimation unit 1421 sets the registered owner ID 702, the vehicle registration number, and the vehicle type 702 as the registered owner ID 1502, the vehicle ID 1503, and the vehicle type 1504, respectively, as the undeclared vehicle. Register in the ID management table 1423 and issue the undeclared vehicle management ID 1501.

Next, in step 1946, the non-declared vehicle mobility data estimation unit 1421 takes a picture of the non-declared vehicle management ID 1504, the charge target ID 201 and the location information ID 221 of the mobility data declaring vehicle 1401 that captured the image data, and the location information ID 221, estimated in step 1932. The absolute position information, relative position information, and position measurement time of the vehicle are set to the photographer charge target ID 1522, the photographer position information ID 1523, the relative position 1524, and the position measurement date and time 1525, which constitute the non-declared vehicle position information management table, respectively. , Register in location information 1526. At this time, a new location information ID 1521 is also issued.

Then, in step 1947, the non-declared vehicle mobility data estimation unit 1421 inputs the mobility data of the non-declared vehicle to the metering processing unit 114 in the same manner as the mobility data of the declared vehicle.

After that, as in the first embodiment, the service resource usage determination unit 140 determines the use of the service resource by the non-declared vehicle based on the estimated position information of the non-declared vehicle, and the service resource used by the non-declared vehicle. Service usage status management information including usage resource information and usage time information indicating the time when the undeclared vehicle used the service resource is generated and registered in the service usage status management table 1440, and the service usage amount calculation unit 142 The time when the undeclared vehicle used the service resource by referring to the service usage status management information registered in the service usage status management table 1440 and the metering logic management information registered in the metering logic management table 132, and the time thereof. The service usage amount related to the use of service resources by undeclared vehicles will be calculated based on the usage amount calculation method applied to the time.

In this embodiment, not only vehicles that notify mobility data and declare the use of services, but also mobility that includes location information about vehicles that cannot make a declaration even when there are vehicles that cannot make a declaration. It is possible to provide a flexible service that collects data and changes the calculation method depending on the time. In this embodiment, for example, an item called a declaration method is provided in the metering definition information 2310 of the service definition information 2300 in the first embodiment illustrated in FIG. 14, and self-declaration and other vehicle declaration are set, and the rate plan is set. By setting the respective rate plans for self-assessment and other vehicle declaration for the item, the above-mentioned processing will be executed. For example, the self-reported rate plan is "total usage [unit] x 1.0 yen x 0.6", and the rate plan for other vehicles is "total usage [unit] x 1.0 yen x 1.0". Different rate plans can be applied.

In this embodiment, the position information of the mobility data non-declared vehicle 1403 that does not declare the use of service resources is estimated based on the image data taken by the in-vehicle camera 1402 of the mobility data declaring vehicle 1401. The mobility data receiving unit 111 receives the road camera image data taken by the road camera device installed in the service resource, and the non-declared vehicle information management unit 1420 receives the mobility data non-mobility data based on the road camera image data. It may be configured to estimate the position information of the declared vehicle 1403. With such a configuration, it is possible to calculate the service usage amount of the non-declared vehicle that uses the service resource when the declared vehicle does not exist.

(Third embodiment)
In the third embodiment, a method for detecting falsification of mobility data in the first embodiment and the second embodiment will be described.

In the first embodiment and the second embodiment, it is assumed that all the mobility data transmitted to the management server 102 has not been tampered with. However, since the mobility data is created by the in-vehicle terminal 106 of the mobility data reporting vehicle 1401 and the in-vehicle camera 1402, there is a risk of falsification of the data transmitted to the management server 102. The risk of tampering is, for example, a case where the position information measured by the in-vehicle terminal 106 is illegally tampered with before transmission to the management server 102 so that the metering system does not detect the use of the service, or the image is taken by the in-vehicle camera 1402. There may be cases where image data is falsely reflected and an unrelated vehicle that is not using the service is reflected, and an unreasonable service usage fee is imposed on other vehicles, but the problem is that these cannot be detected. ..

The third embodiment evaluates the consistency between the mobility data provided by the plurality of mobility data reporting vehicles 1401. The consistency evaluation method in the present embodiment is based on the premise that the majority of the mobility data reporting vehicles 1401 transmit untamed mobility data, and based on this premise, fraud detection is performed by the consistency evaluation described above. To solve the problem of.

In addition, as a result of the consistency evaluation, the mobility data reporting vehicle 1401 that provides mobility data without fraud is regarded as a highly reliable service user vehicle, and a mechanism such as discounting the charge for the highly reliable service user vehicle is provided. Explain how to provide and encourage the use of services without fraud.

FIG. 21 is a block diagram of a mobility service metering system using the management server according to the third embodiment. FIG. 21 is an overall view of the third embodiment.

In the description of this embodiment, since many functional units and tables are common to the second embodiment shown in FIG. 15, the difference from the second embodiment will be mainly described. Consistency evaluation unit 2010, consistency evaluation result management table 2011, reliability evaluation unit 2012, reliability management table 2013, detection report vehicle information output unit 2020, rate plan management table, as functional units and tables unique to this embodiment. There is 2030.

The consistency evaluation unit 2010 has a function of evaluating the consistency between mobility data obtained from a plurality of vehicles in order to detect a vehicle that transmits mobility data including tampered position information and image data. The consistency evaluation unit 2010 performs a consistency evaluation on the mobility data obtained from the mobility data reporting vehicle 1401. When the image data is included in the mobility data and a plurality of other mobility data reporting vehicles 1401 are shown in the image data, the vehicle that has transmitted the image data is the target vehicle for the consistency evaluation. Consistency evaluation is performed by evaluating the match between the position information of the surrounding vehicles obtained from the image data and the position information self-reported by the mobility data reporting vehicle 1401 reflected in the image data. The fraud that can be detected by the consistency evaluation is the data falsification performed by the evaluation target vehicle on the position information or the image data included in the mobility data.

The consistency evaluation by the consistency evaluation unit 2010 is performed based on the analysis result of the image data executed by the undeclared vehicle information management unit 1420 via the detection vehicle information output unit 2020 (described later). When the declaring vehicle information management unit 112 acquires the mobility data including the image data, the declaring vehicle information management unit 112 manages the processed mobility data including the image data via the non-declaring vehicle information output unit 1410. Input to unit 1420. The non-declared vehicle management unit 1420 acquires the relative position information from the shooting vehicle and the vehicle registration number for the vehicle reflected in the image data by the camera / sensor data processing unit 1422. The detected vehicle information output unit 2020 (described later) has relative position information and a vehicle registration number regarding two or more vehicles (vehicles to be photographed) acquired from image data, and a position information ID of the evaluation target vehicle included in the processed mobility data. , The position information, the position measurement date and time, and the vehicle data to be photographed including the charge target ID are input to the consistency evaluation unit 2010.

The consistency evaluation unit 2010 uses the vehicle registration number of each photographed vehicle included in the photographed vehicle data as a query to acquire the billing target ID 201 in which the query and the vehicle ID 203 of the billing target ID management table 121 match. Further, the charge target ID 201 of each photographed vehicle acquired from the position information management table 123 and the position measurement date and time of the evaluation target vehicle included in the photographed vehicle data are used as a query, and are closest to the position measurement date and time of the evaluation target vehicle. Acquires the position information of the vehicle to be photographed measured at daytime. The consistency evaluation unit 2010 performs the following consistency evaluation using the position information of each vehicle to be photographed as reference information. Based on the position information of the vehicle to be evaluated and the relative position information of the vehicle to be evaluated included in the data of the vehicle to be evaluated, the position information of the vehicle to be evaluated is estimated and the vehicle to be photographed obtained from the position information management table 123. Compare with the location information of. The two position information are the information estimated from the mobility data of the vehicle to be evaluated and the self-reported information of the vehicle to be photographed at a close date and time. If both the vehicle to be evaluated and the vehicle to be photographed are not fraudulent, the two position information generally match. In the present embodiment, as described above, there are few mobility data reporting vehicles 1401 that falsify the position data, and it is assumed that almost all the position information declared by the photographed vehicle is correct. Perform the same operation for all the vehicles to be photographed included in the vehicle data to be photographed. For example, if the position information of more than half of the vehicles to be photographed match, the mobility data including the image data is invalid. It is presumed that the source vehicle of the mobility data including the image data without fraud is a fair vehicle. As the evaluation result, the consistency evaluation unit 2010 registers the charge target ID 201 of the mobility data transmission source vehicle, the position information ID, the position measurement date and time, and the determination result in the consistency evaluation result management table 2011. The determination result may be a discrete evaluation such as "no fraud" (evaluation "〇") or "suspected fraud" (evaluation "-").

The consistency evaluation result table 2011 accumulates the evaluation results of the presence or absence of unauthorized data alteration by the consistency evaluation unit 2010, and quantifies the reliability of excellent vehicles that provide fair mobility data from the past consistency evaluation results. This is a table for managing the consistency evaluation result, the identifier of the mobility data to be evaluated, and the identifier of the vehicle that transmitted the data in association with each other.

The reliability evaluation unit 2012 will give preferential treatment to service usage fees for vehicles using excellent services that provide mobility data without falsification or other fraud, based on the results of the consistency evaluation, for individual mobility. It has a function to quantitatively evaluate the reliability of the data reporting vehicle 1401.

The reliability evaluation unit 2012 uses the evaluation results of individual vehicles registered in the consistency evaluation result table 2011. The consistency evaluation unit 2010 is executed when a new evaluation result is registered in the consistency evaluation result table 2011. When a new evaluation result is registered, a record related to the target vehicle is acquired from the consistency evaluation result management table 2011 using the charge target ID included in the registered record as a query. The reliability is calculated using the evaluation results included in each acquired record. As the reliability calculation method, an evaluation method defined in advance may be provided to the reliability evaluation unit 2012. For example, there are methods such as using the percentage of "no fraud" (evaluation "○ (circle)") in the number of records, or fixing the reliability to 60% if there is even one fraud. Be done. Further, instead of using all the records, a method may be applied in which the evaluation is narrowed down to only the records for the past one year from the present by referring to the position measurement date and time included in each record.

The reliability management table 2013 evaluates the reliability evaluation result by the reliability evaluation unit 2013 for the vehicle to be evaluated in order to give preferential treatment of the service usage fee to the excellent service use vehicle that provides fair mobility data. It is a table for managing by associating with an identifier.

The detection vehicle information output unit 2020 was extracted by the camera / sensor data processing unit 1422 based on the processed mobility data including the image data input from the non-declared vehicle information output unit 1410 to the non-declared vehicle mobility data estimation unit 1421. It has a function to output the imaged vehicle data to the consistency evaluation unit 2010. In the detection vehicle information output unit 2020, the photographed vehicle data extracted by the camera / sensor data processing unit 1422 is the relative position information, the vehicle registration number, and the processed vehicle for two or more vehicles (photographed vehicle) as described above. It includes the position information ID of the evaluation target vehicle included in the mobility data, the position information, the position measurement date and time, and the charge target ID.

The rate plan management table 2030 refers to the vehicle type to which the plan is applied and the declaration of mobility data in order to refer to an appropriate rate plan that differs depending on the vehicle type, the mobility data declaration method, and the reliability evaluation of the target vehicle. It is a table that manages the method, the range of reliability evaluation, and the definition of the charge calculation method in association with each other. The range of reliability evaluation is a guideline for referring to the charge plan according to the reliability evaluation when there is a reliability evaluation having the charge target ID of the target vehicle when calculating the charge of the mobility data reporting vehicle 1401. Information.

FIG. 22 is a diagram showing a configuration example of a table provided in the declaration vehicle information management unit 112 shown in FIG. 21. The tables included in the declaration vehicle information management unit 112 include (a) consistency evaluation result management table 2011 and (b) reliability management table 2013.

As shown in FIG. 22A, the consistency evaluation result management table 2011 includes a charge target ID 1501, a position information 1502, a position measurement date and time 1503, and an evaluation result 1504. The billing target ID 1501 is an identifier for specifying the evaluation target vehicle for the consistency evaluation. The location information ID 1502 is an identifier for identifying the mobility data subject to consistency evaluation. The position measurement date and time 1503 is the measurement date and time of the position information included in the mobility data specified by the position information ID 1502. The evaluation result 1504 is a consistency evaluation result by the consistency evaluation unit 2010 for the mobility data to be evaluated.

The billing target ID 2101, the position information 2102, the position measurement date and time 2103, and the evaluation result 2104 constituting the consistency evaluation result management table 2011 are registered by the consistency evaluation unit 2010. In the consistency evaluation unit 2010, the declaration vehicle information management unit 112 receives the mobility data including the image data, and the analysis processing result of the camera / sensor data processing unit 1422 for the mobility data is input via the detection vehicle information output unit 2020. Consistency evaluation will be carried out when it is done. As a result of the consistency evaluation, the charge target ID 201, the position information 224, the position information ID 221 of the evaluation target vehicle (the vehicle from which the mobility data is transmitted), and the evaluation results are the charge target ID 2101, the position information 2102, and the position measurement, respectively. It is registered as the date and time 2103 and the evaluation result 2104.

As shown in FIG. 22B, the reliability management table 2013 includes a charge target ID 2121, a reliability 2122, and a consistency evaluation result target period 2123.

The billing target ID 2121, the reliability 2122, and the consistency evaluation result target period 2123 constituting the reliability management table 2013 are registered by the reliability evaluation unit 2012 after the reliability evaluation is executed. The reliability evaluation unit is executed when new data is registered in the consistency evaluation result management table 2011. As a result of the reliability evaluation, the reliability evaluation unit stores the chargeable ID of the vehicle to be evaluated, the calculated reliability, and the oldest position measurement date / time information among the consistency evaluation result records used for the reliability evaluation in the reliability management table. Register in 2013.

FIG. 23 is a diagram showing a configuration example of the charge plan management table 2030 included in the service metering management unit 130 shown in FIG. 21.

As shown in FIG. 23, the charge plan management table 2030 included in the service metering management unit 130 shown in FIG. 21 is a table in which one column is added to the charge plan management table 1430 in the second embodiment. The purpose of use of the information managed in and the processing related to record registration are the same as those in the rate plan management table 133. The following describes mainly the newly added columns.

The charge plan configuration table 1430 is composed of a plan ID 401, a vehicle type 402, a declaration method 1501, a reliability 2201, and a charge plan 2202. The reliability 2201 is one of the selection items of the rate plan, and the rate plan applied to each vehicle based on the high reliability of the mobility data transmitted by each vehicle so far for the mobility data reporting vehicle 1401. Information for distinguishing. For example, the higher the reliability, the lower the usage fee may be set.

In the vehicle type 402 constituting the charge plan configuration table 2030, the declaration method 1501, the reliability 2201, and the charge plan 2202, the service metering management unit 130 acquires metering information from the service provider 103 via the communication IF 115. At that time, the vehicle type 402, the declaration method 1501, the reliability 2201 and the charge plan 2202 are extracted and registered from the acquired information. If there is no record that matches the combination of the vehicle type 402, the declaration method 1501 and the reliability 2201 extracted in the rate plan configuration table 2030, the service metering management unit 130 issues a new plan ID 401, and the plan ID 401 and the vehicle Register the type 402, the declaration method 1501, the reliability 2201 and the plan 2202 in the rate plan management table. If there is a record with the extracted vehicle type and the declaration method 1501 that matches the vehicle type and the declaration method 1501, only the rate plan 2202 is exchanged for the new rate plan.

As described above, in this embodiment, the image data included in the mobility data received from the mobility data reporting vehicle 1401 is used to evaluate the consistency of the position information of other declared vehicles reflected in the image data. Since it has a section 2010, it is possible to verify the content declared by the mobility data from the reporting vehicle with the image data taken by another vehicle, and when the reporting vehicle makes an illegal declaration such as falsifying the position information. Fraud can be detected.

In addition, it has a reliability evaluation unit 2012 that evaluates the reliability of the declaration of the declared vehicle based on the consistency evaluation result in the consistency evaluation unit 2010, and has confidence in the declared content of the declared vehicle based on the past consistency evaluation result. Since the degree is calculated, it is possible to know how reliable the declared vehicle is.

In the present embodiment, the position information of another reporting vehicle is estimated based on the image data taken by the in-vehicle camera 1402 of the mobility data reporting vehicle 1401, and the estimated position information is used to match the position information. Although the property is evaluated, the mobility data receiving unit 111 receives the road camera image data taken by the road camera device installed in the service resource, and based on this road camera image data, another declared vehicle. The position information of the camera may be estimated, and the consistency of the position information may be evaluated using the estimated position information. With such a configuration, the consistency of the position information of the declared vehicle can be evaluated even by using the road camera device installed in the service resource.

100 ... Mobility service metering system, 101 ... Management console, 102 ... Management server, 103 ... Service provider, 104 ... Field, 105 ... Service-using vehicle, 106 ... In-vehicle terminal, 107 ... Gateway, 108 ... Map data / vehicle registration Information management organization, 111 ... Mobility data transmission / reception unit, 112 ... Declaration vehicle information management department, 113 ... Mobility service management department, 114 ... Metering processing unit, 115 ... Communication IF (interface), 120 ... Declaration information extraction unit, 121 ... Billing target ID management table, 122 ... Location information shaping department, 123 ... Declared vehicle position information management table, 130 ... Service metering management department, 131 ... Service resource management department, 132 ... Metering logic management table, 133 ... Price plan Management table, 135 ... Service resource management table, 136 ... Map / road configuration information management table, 137 ... Vehicle registration information management table, 138 ... Map matching processing unit, 140 ... Service resource usage determination unit, 141 ... Service usage status management table , 142 ... Service usage amount calculation unit, 143 ... Usage charge calculation unit, 144 ... Metering result management table, 145 ... Metering logic application unit, 146 ... Charge plan application unit, 150 ... API, 152 ... GUI, 1201 ... Car navigation system 1202 ... Display panel 1203 ... Service metering result notification message 1204 ... Currently available service information, 1301 ... CPU, 1302 ... Memory, 1303 ... Auxiliary storage device, 1304 ... Communication interface, 1305 ... Media interface, 1306 ... Input / output device, 1307 ... External storage medium, 1308 ... Network, 1401 ... Mobility data reporting vehicle, 1402 ... In-vehicle camera, 1403 ... Mobility data non-declared vehicle, 1410 ... Non-declared vehicle information output unit, 1420 ... Non-declared vehicle information management Department, 1421 ... Non-declared vehicle mobility data estimation unit, 1422 ... Camera / sensor data processing unit, 1423 ... Non-declared vehicle ID management table, 1424 ... Non-declared vehicle position information management table, 1430, 1440 ... Price plan management table, 1441 ... Metering result management table for non-declared vehicles, 2010 ... Consistency evaluation unit, 2011 ... Consistency evaluation result management table, 2012 ... Reliability evaluation unit, 2013 ... Reliability management table, 2020 ... Detection report vehicle information output unit

Claims (8)

A service resource management unit that manages geographic configuration information including resource location information that indicates the location of service resources available to the vehicle.
It manages metering logic management information including logic information indicating a usage amount calculation method for calculating the service usage amount related to the use of the service resource by the vehicle and application time information indicating the time for applying the usage amount calculation method. Service metering management department and
A mobility data receiver that receives mobility data including location information and image data taken by the declared vehicle from the declared vehicle that declares the use of service resources.
The use of the service resource by the declared vehicle is determined based on the mobility data and the geographical configuration information, the usage resource information regarding the service resource used by the declared vehicle, and the time when the declared vehicle uses the service resource. Service resource usage determination unit that generates service usage status management information including usage time information indicating
With reference to the service usage status management information and the metering logic management information, the declaration vehicle uses the declaration vehicle based on the time when the declaration vehicle uses the service resource and the usage amount calculation method applied to the time. The service usage amount calculation unit that calculates the service usage amount related to the use of service resources,
It has a non-declared vehicle information management unit that estimates the position information of non-declared vehicles that do not declare the use of service resources based on the image data.
The service resource usage determination unit determines the use of the service resource by the non-declared vehicle based on the estimated position information of the undeclared vehicle, and the usage resource information regarding the service resource used by the non-declared vehicle and the non-declared vehicle. Generates service usage status management information including usage time information indicating the time when the declared vehicle used the service resource.
The service usage amount calculation unit refers to the service usage status management information and the metering logic management information, and the time when the undeclared vehicle uses the service resource and the usage amount calculation method applied to the time. Based on, the amount of service usage related to the use of the service resource by the undeclared vehicle is calculated.
Service management device. The mobility data receiving unit further receives the road camera image data taken by the road camera device installed in the service resource, and further receives the road camera image data.
The non-declared vehicle information management unit estimates the position information of the non-declared vehicle that does not declare the use of service resources based on the road camera image data.
The service management device according to claim 1. A service resource management unit that manages geographic configuration information including resource location information that indicates the location of service resources available to the vehicle.
It manages metering logic management information including logic information indicating a usage amount calculation method for calculating the service usage amount related to the use of the service resource by the vehicle and application time information indicating the time for applying the usage amount calculation method. Service metering management department and
A mobility data receiver that receives mobility data including location information and image data taken by the declared vehicle from the declared vehicle that declares the use of service resources.
The use of the service resource by the declared vehicle is determined based on the mobility data and the geographical configuration information, the usage resource information regarding the service resource used by the declared vehicle, and the time when the declared vehicle uses the service resource. Service resource usage determination unit that generates service usage status management information including usage time information indicating
With reference to the service usage status management information and the metering logic management information, the declaration vehicle uses the declaration vehicle based on the time when the declaration vehicle uses the service resource and the usage amount calculation method applied to the time. The service usage amount calculation unit that calculates the service usage amount related to the use of service resources,
When another declared vehicle is shown as a vehicle to be photographed in the image data, the photographed vehicle is based on the position information of the declared vehicle to which the image data is transmitted and the relative position information between the declared vehicle and the photographed vehicle. The position information of the photographed vehicle is estimated, and the estimated position information is compared with the position information of the photographed vehicle included in the mobility data received from the photographed vehicle by the mobility data receiving unit, and the photographed vehicle is compared. It has a consistency evaluation unit that evaluates the consistency of location information.
Service management device. The service management device according to claim 3, further comprising a reliability evaluation unit that evaluates the reliability of the declaration of the declaration vehicle based on the consistency evaluation result in the consistency evaluation unit. A service resource management unit that manages geographic configuration information including resource location information that indicates the location of service resources available to the vehicle.
It manages metering logic management information including logic information indicating a usage amount calculation method for calculating the service usage amount related to the use of the service resource by the vehicle and application time information indicating the time for applying the usage amount calculation method. Service metering management department and
A mobility data receiving unit that receives mobility data including location information from a vehicle that declares the use of service resources, and receives road camera image data taken by a road camera device installed in the service resource.
The use of the service resource by the declared vehicle is determined based on the mobility data and the geographical configuration information, the usage resource information regarding the service resource used by the declared vehicle, and the time when the declared vehicle uses the service resource. Service resource usage determination unit that generates service usage status management information including usage time information indicating
With reference to the service usage status management information and the metering logic management information, the declaration vehicle uses the declaration vehicle based on the time when the declaration vehicle uses the service resource and the usage amount calculation method applied to the time. The service usage amount calculation unit that calculates the service usage amount related to the use of service resources,
When another declared vehicle is shown as a vehicle to be photographed in the image data, it is based on the position information of the road camera device that transmitted the image data and the relative position information between the road camera device and the vehicle to be photographed. The position information of the photographed vehicle is estimated, and the estimated position information is compared with the position information of the photographed vehicle included in the mobility data received from the photographed vehicle by the mobility data receiving unit, and the photographed vehicle is compared. It has a consistency evaluation unit that evaluates the consistency of vehicle position information.
Service management device. A service resource management process that manages geographic configuration information, including resource location information that indicates the location of service resources available to the vehicle.
It manages metering logic management information including logic information indicating a usage amount calculation method for calculating the service usage amount related to the use of the service resource by the vehicle and application time information indicating the time for applying the usage amount calculation method. Service metering management process and
Mobility data reception processing that receives mobility data including location information and image data taken by the declared vehicle from the declared vehicle that declares the use of service resources.
The use of the service resource by the declared vehicle is determined based on the mobility data and the geographical configuration information, the usage resource information regarding the service resource used by the declared vehicle, and the time when the declared vehicle uses the service resource. Service resource usage determination processing that generates service usage status management information including usage time information indicating
With reference to the service usage status management information and the metering logic management information, the declaration vehicle uses the declaration vehicle based on the time when the declaration vehicle uses the service resource and the usage amount calculation method applied to the time. Service usage calculation processing that calculates service usage related to service resource usage, and
Non-declared vehicle information management processing that estimates the position information of non-declared vehicles that do not declare the use of service resources based on the image data, and
Based on the estimated position information of the non-declared vehicle, the use of the service resource by the non-declared vehicle is determined, and the usage resource information regarding the service resource used by the non-declared vehicle and the non-declared vehicle use the service resource. A second service resource usage determination process that generates service usage status management information including usage time information indicating the time spent
The non-declared vehicle is based on the time when the non-declared vehicle uses the service resource and the usage amount calculation method applied to the time with reference to the service usage status management information and the metering logic management information. The second service usage amount calculation process for calculating the service usage amount related to the use of the service resource by
A service management method executed by a management server configured with a computer . A service resource management process that manages geographic configuration information, including resource location information that indicates the location of service resources available to the vehicle.
It manages metering logic management information including logic information indicating a usage amount calculation method for calculating the service usage amount related to the use of the service resource by the vehicle and application time information indicating the time for applying the usage amount calculation method. Service metering management process and
Mobility data reception processing that receives mobility data including location information and image data taken by the declared vehicle from the declared vehicle that declares the use of service resources.
The use of the service resource by the declared vehicle is determined based on the mobility data and the geographical configuration information, the usage resource information regarding the service resource used by the declared vehicle, and the time when the declared vehicle uses the service resource. Service resource usage determination processing that generates service usage status management information including usage time information indicating
With reference to the service usage status management information and the metering logic management information, the declaration vehicle uses the declaration vehicle based on the time when the declaration vehicle uses the service resource and the usage amount calculation method applied to the time. Service usage calculation processing that calculates service usage related to service resource usage, and
When another declared vehicle is shown as a vehicle to be photographed in the image data, the photographed vehicle is based on the position information of the declared vehicle to which the image data is transmitted and the relative position information between the declared vehicle and the photographed vehicle. The position information of the photographed vehicle is estimated, and the estimated position information is compared with the position information of the photographed vehicle included in the mobility data received from the photographed vehicle in the mobility data reception process, and the photographed vehicle is compared. Consistency evaluation processing that evaluates the consistency of the location information of
A service management method executed by a management server configured with a computer . A service resource management process that manages geographic configuration information, including resource location information that indicates the location of service resources available to the vehicle.
It manages metering logic management information including logic information indicating a usage amount calculation method for calculating the service usage amount related to the use of the service resource by the vehicle and application time information indicating the time for applying the usage amount calculation method. Service metering management process and
Mobility data reception processing that receives mobility data including location information from the declaring vehicle that declares the use of the service resource, and receives the road camera image data taken by the road camera device installed in the service resource.
The use of the service resource by the declared vehicle is determined based on the mobility data and the geographical configuration information, the usage resource information regarding the service resource used by the declared vehicle, and the time when the declared vehicle uses the service resource. Service resource usage determination processing that generates service usage status management information including usage time information indicating
With reference to the service usage status management information and the metering logic management information, the declaration vehicle uses the declaration vehicle based on the time when the declaration vehicle uses the service resource and the usage amount calculation method applied to the time. Service usage calculation processing that calculates service usage related to service resource usage, and
When another declared vehicle is shown as a vehicle to be photographed in the image data, it is based on the position information of the road camera device that transmitted the image data and the relative position information between the road camera device and the vehicle to be photographed. The position information of the photographed vehicle is estimated, and the estimated position information is compared with the position information of the photographed vehicle included in the mobility data received from the photographed vehicle in the mobility data reception process, and the photographed vehicle is compared. The management server configured by the computer executes the consistency evaluation process that evaluates the consistency of the position information of the shooting vehicle.
Service management method.

Images