Integrated server
The integrated server optimizes revenue distribution by coordinating multiple systems to avoid redundant recognition, transmission, and storage processes, ensuring comprehensive service coverage and cost efficiency.
Patent Information
- Application Number
- JP2023085304
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-24
- Publication Date
- 2024-12-05
AI Technical Summary
Existing systems fail to account for multiple service providers, leading to redundant recognition, transmission, and storage processes, resulting in lost revenue opportunities.
An integrated server that coordinates with multiple systems operated by different businesses to manage mobile objects with sensors, allocating recognition, transmission, and storage responsibilities among them to avoid duplication and optimize revenue distribution.
Prevents unnecessary costs due to duplicate processing and ensures all service target sections are covered, thereby maximizing profit opportunities for the integrated server.
Smart Images

Figure 2024168543000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to an integrated server that manages a plurality of systems. [Background technology]
[0002] A service for monitoring or investigating various conditions of vehicles or roads / roadsides is realized by a system consisting of a drive recorder installed in a vehicle that recognizes the conditions of the vehicle or road / roadsides, a communication network that transmits the conditions recognized by the drive recorder to a data center, and a data center that stores and displays the conditions. Such a system provides the conditions to service users and earns revenue from them. Patent Document 1 describes monitoring of roads, etc. based on images captured by live recorders installed in passenger cars, trucks, etc. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] 2021-163060 Publication Special Summary of the Invention [Problem to be solved by the invention]
[0004] However, Patent Document 1 does not take into consideration that services are provided by different businesses. Therefore, there may be cases where multiple businesses perform duplicate recognition, transmission, storage, etc., which may result in lost revenue opportunities.
[0005] Therefore, an object of the present invention is to provide an integrated server that can cover lost profit opportunities without duplicate management by a plurality of businesses. [Means for solving the problem]
[0006] The integrated server of the present invention is an integrated server that provides services in cooperation with systems operated by multiple different operators that manage mobile objects equipped with sensors, and is equipped with a confirmation unit that confirms, for each section along which the mobile object managed in each of the multiple systems travels, one or more systems that manage the mobile object that is about to travel through that section, and a calculation unit that calculates monetary allocations to a selected system and other systems other than the selected system based on the confirmation results by the confirmation unit. Effect of the Invention
[0007] According to the present invention, it is possible to cover lost revenue opportunities without performing duplicate management by a plurality of businesses. [Brief description of the drawings]
[0008] [Figure 1] 1 is a diagram showing a system configuration including an integrated server 100 according to the present disclosure. [Diagram 2] FIG. 2 is a schematic diagram showing an integration process of road information by vehicles managed by each system 200 in the present disclosure. [Diagram 3] FIG. 13 is a diagram showing how costs for recognition, transmission, and storage are divided (shared) in each system 200. [Figure 4] 2 is a block diagram showing the functional configuration of an integrated server 100 according to the present disclosure. FIG. [Diagram 5] FIG. 2 is a diagram showing a specific example of a management table 104. [Figure 6] 11 is a flowchart showing the system adjustment process of the integrated server 100 of the present disclosure. [Figure 7] 1 shows a management table 104 obtained by the system determination process. [Figure 8] 13 is a flowchart showing a billing process for each system 200 in integrated server 100. [Figure 9] FIG. 11 is a diagram showing a management table 104 obtained in the billing process. [Figure 10]FIG. 2 is a diagram showing a processing concept illustrating an integration function in integrated server 100. [Figure 11] 13 is a flowchart showing a process performed by integrated server 100 to provide a service to a customer. [Figure 12] FIG. 1 is a schematic diagram showing revenue sharing obtained for services provided to customers. [Figure 13] 13 is a flowchart showing a process for distributing profits in integrated server 100 of the present disclosure. [Figure 14] 13 is a specific example of the management table 104 when the profits and the distribution of the profits are registered. [Figure 15] FIG. 2 is a block diagram showing the functional configuration of a system 200. [Figure 16] FIG. 13 is a diagram showing a prediction DB based on predictions made by the system 1. [Figure 17] 4 is a flowchart showing the process of the system 200 for predicting vehicle travel. [Figure 18] 1 is a diagram illustrating an example of a hardware configuration of an integrated server 100 and a system 200 according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0009] The embodiments of the present disclosure will be described with reference to the accompanying drawings. Whenever possible, the same parts are designated by the same reference numerals and redundant description will be omitted.
[0010] FIG. 1 is a diagram showing a system configuration including an integrated server 100 in the present disclosure. As shown in the diagram, integrated server 100 is communicatively connected to systems 1 to 3 (hereinafter, unless otherwise specified, these will be collectively referred to as system 200). In the present disclosure, systems 1 to 3 are systems operated by different operators. Here, three systems are shown, but the present invention is not limited to this, and N systems (N>3) may be used.
[0011] These systems 200 manage roads, for example, based on image information and location information sent from vehicles managed by each system 200. The image information includes video information captured by the vehicle's drive recorder. Hereinafter, unless otherwise specified, the image information and location information will be referred to as road information. The integrated server 100 integrates and manages the road information sent from these systems 200, and provides customers with monitoring or investigation services using this road information.
[0012] FIG. 2 is a schematic diagram showing an integration process of road information by vehicles managed by each system 200 in the present disclosure. In FIG. 2(a), the integrated server 100 inquires of each system 200 about a schedule or prediction of driving in a target section to be covered by the service by the integrated server 100. In FIG. 2(a), there are roads A to C, and each system 200 manages vehicles traveling on each of the roads A to C. As shown in the figure, the road A is composed of small sections, roads A1 to A3. The same is true for roads B and C. In the present disclosure, the road A, i.e., the roads A1 to A3, are set as the target section to be covered by the service (service target section). For example, this service is for the purpose of road maintenance management, and manages the road conditions as images using a drive recorder or the like of a vehicle traveling on the road.
[0013] In this disclosure, the target is not only a vehicle that runs on a road equipped with a drive recorder as a specific example, but also various moving objects such as a person who moves on a road, site, or building while carrying a smartphone equipped with various sensors, and a drone that moves in a three-dimensional space equipped with various sensors, etc. In this disclosure, as an example, the service is intended for the maintenance and management of a road, and the road conditions are managed as images by using a drive recorder of a vehicle that runs on the road.
[0014] For example, this service is a road survey that uses the drive recorders of vehicles traveling on the road for various purposes such as transporting cargo and personnel to investigate the condition of road signs, etc., and also a sidewalk maintenance service that uses the sensors of smartphones carried by people walking on the sidewalk for various purposes to grasp damaged areas of the sidewalk, etc., and also a regional monitoring service that uses the sensors of drones moving in three-dimensional space for various purposes such as equipment inspection and cargo transportation to monitor the region.
[0015] Naturally, integrated server 100 of the present disclosure can be applied to other mobile objects and services, etc.
[0016] FIG. 2(b) is a diagram showing route r of each vehicle traveling on roads A to C. In the diagram, vehicles managed by system 1 are predicted to travel on roads C1, A2, and A3 indicated by route r1. Vehicles managed by system 2 are predicted to travel on roads A1, A2, and B2 indicated by route r2. Vehicles managed by system 3 are predicted to travel on roads A1 and C2 indicated by route r3. In each of the routes r1 to r3, the parts indicated by solid lines indicate roads that fall within the service area. The parts indicated by dashed lines indicate roads that fall outside the service area.
[0017] Figure 2(c) shows the sharing request for recognition, transmission, and storage of vehicle and road / roadside conditions in the service area. As shown in the figure, system 1 is in charge of road A3, system 2 is in charge of road A2, and system 3 is in charge of road A1. As shown in the figure, system 2 is in charge of road A2, which is predicted to be traveled by vehicles of system 1 and system 2.
[0018] In this way, the roads that each system is responsible for can be shared, and duplicate recognition, transmission, and storage of the same roads can be avoided.
[0019] FIG. 3 is a diagram showing division (allocation) of costs for recognition, transmission, and storage in each system 200. FIG. 3(a) shows that the recognition cost of system 2 is divided between systems 1 and 2, and the recognition cost of system 3 is divided between systems 2 and 3 and charged. In this disclosure, charging means bearing the costs of recognition, transmission, and storage. In this disclosure, when there is no need to particularly distinguish between recognition, transmission, and storage, it is referred to as management.
[0020] In Fig. 3(a), system 1, which is not responsible for road A2, secures the right to share revenue by contributing to the partial burden of the recognition cost of system 2, which is responsible for road A2. Similarly, for road A1, system 2 secures the right to share revenue by sharing the recognition cost with system 3.
[0021] FIG. 3(b) shows that the transmission cost of the responsible system is divided and charged to multiple systems. A vehicle under the management of system 1 would normally transmit data on roads A2 and A3 to system 1, but only needs data on road A3. Therefore, a vehicle under the management of system 2 would need to transmit data on roads A2 and A1, but only needs data on road A2. Similarly, systems 1 and 2 only need to transmit data on roads A3 and A2, respectively, to integrated server 100.
[0022] Therefore, system 1, which is not responsible for road A2, secures the right to share in the revenue by contributing to the partial burden of the transmission costs of system 2, which is responsible for road A2. System 2 also obtains the right to share in the revenue by partially bearing the transmission costs of system 3.
[0023] Fig. 3(c) shows that the cost of system storage is divided and charged to multiple systems. System 1 would normally store (store) data for roads A2 and A3, but only needs data for road A3. Similarly, system 2 would need to store (store) data for roads A2 and A1, but only needs data for road A2.
[0024] System 1, which is not responsible for road A2, secures its right to share in the revenue by contributing to the partial burden of the conservation costs of system 2, which is responsible for road A2. System 2 does the same.
[0025] As described above, the integrated server 100 can receive various information from each system 200 and determine the costs and allocated revenues to each system 200. In Fig. 3, the data of roads A1 and A2 are prevented from being duplicated in recognition, transmission, and storage by the adjustment function.
[0026] In this disclosure, systems 1 to 3 each independently provide monitoring or investigation services to customers, and have a mechanism for each customer to specify the sections to be serviced. This mechanism allows recognition, transmission, and storage only when a vehicle travels on a small section of a road that is requested to be shared by the integrated server, and prevents the occurrence of unnecessary costs due to duplicate processing in systems 1 to 3 as a whole.
[0027] 4 is a block diagram showing the functional configuration of integrated server 100 of the present disclosure. As shown in the figure, integrated server 100 includes a travel road inquiring unit 101, a selecting unit 102, a calculating unit 103, and a management table 104.
[0028] The travel road inquiry unit 101 is a part that inquires of each system 200 about the travel schedule or prediction of the service target section, and receives the response. The response includes the presence or absence of the travel schedule or prediction of one or more road subsections that constitute the service target section.
[0029] When there are multiple systems 200 that manage vehicles scheduled or predicted to travel on each of the short sections of roads that make up the service target section, the selection unit 102 is a part that selects one system to be requested to share from the multiple systems 200. The selection method may be random selection from the multiple systems 200, or a method of selecting from the multiple systems 200 so that each system shares an equal number of short sections of roads in order to make the sharing between the systems fair.
[0030] The calculation unit 103 is a part that calculates the charge (cost burden) and revenue share for each system 200 based on the combination of the system and road selected by the selection unit 102.
[0031] The management table 104 is a table that stores, for each road section, the service target section indicating the road covered by the service, the combination of the system and road selected by the selection unit 102, and the cost borne by each system. FIG. 5 is a diagram showing a specific example. As shown in the figure, the management table 104 associates, for each road section, the service target section, the system covering the road, the number of systems covering the road, the system in charge of recognition, transmission, and storage, the cost of recognition, transmission, and storage, the division (charge amount) of the cost of recognition, transmission, and storage, the revenue, and the distribution of the revenue. This management table 104 is generated in the form shown in FIG. 5 by performing an adjustment process, a charging process, and an integration process, which will be described later.
[0032] In Fig. 5, a correspondence table is created for each small section of a road such as road A1, road A2, etc. In Fig. 5, the service target section indicates road A. Roads A1, A2, and A3 are included in road A as shown in Fig. 2(a), and therefore are all checked as target sections. The "service target section" is set by an operator of integrated server 100 using a setting unit (not shown).
[0033] 2(b), here, systems 2 and 3 cover roads A1 and A2. Systems 2, 3, and 2 are registered as the "covering system" and the "number of covering systems" for roads A1 and A2 in management table 104. The "covering system" and the "number of covering systems" are registered by road travel inquiry unit 101.
[0034] In FIG. 5, the system 3 selected by the selection unit 102 is registered as the "system in charge of recognition, transmission, and storage."
[0035] The "recognition, transmission, and storage costs" here is, for example, 300 yen. This indicates the combined value of the recognition costs, transmission costs, and storage costs when system 3 performs recognition, transmission, and storage. This total value is obtained from the systems and registered by revenue processing unit 106. The "recognition, transmission, and storage cost division" indicates the respective costs when shared between system 2 and system 3. Revenue indicates the revenue when recognition, transmission, and storage for road A is performed, and revenue distribution indicates the distribution amount for each system. These "recognition, transmission, and storage cost division", "revenue", and "revenue distribution" are calculated by revenue processing unit 106.
[0036] The service providing unit 105 is a part that requests road data from each of the systems 1 to 3, performs integration processing, and transmits the data to the client's server to provide a service. This data is, for example, photographed data showing road conditions.
[0037] The revenue processing unit 106 processes the cost and revenue for the provided services. Specifically, the revenue processing unit 106 distributes the revenue according to the charges (charges) of each system.
[0038] A description will now be given of the operation of integrated server 100 configured in this manner. Fig. 6 is a flowchart showing the system adjustment process of integrated server 100 of the present disclosure.
[0039] The travel road inquiry unit 101 inquires of the systems 1 to 3 about the travel schedule or prediction of roads included in the target section to be covered by the service (S101). The travel road inquiry unit 101 receives prediction information of the travel schedule or prediction of the target section from the systems 1 to 3, and registers the prediction information in the management table 104 (S102). Based on the prediction information, the travel road inquiry unit 101 registers the systems and the number of systems to be covered for each road (small section) in the management table 104 shown in Fig. 5 (see Fig. 7). It is assumed that the service target section is registered in advance.
[0040] The selection unit 102 refers to the management table 104 and checks the number of systems covering the roads constituting the service target section for each road (S103). For roads with two or more systems, the selection unit 102 selects one system 200 (S104). The selection unit 102 requests the selected one system 200 (e.g., system 3) to share the recognition, transmission, and storage of a road (e.g., road A1), and notifies the selected one system 200 of the "number of systems covering" associated with the road (e.g., road A1) (S105). Meanwhile, the selection unit 102 notifies the other systems (e.g., system 2) that were not selected of the "number of systems covering" associated with the road (e.g., road A1) (S106).
[0041] In addition, in process S103, for a road (e.g., road A3) whose "number of systems covering" is one, the selection unit 102 requests the system 200 (e.g., system 1) covering that road to recognize, transmit, and store the road (S107).
[0042] Furthermore, in step S103, for a road where the "number of systems covered" is 0, the selection unit 102 determines that the road is not to be monitored or investigated (S108).
[0043] 2 as an example, the selection unit 102 determines that the road A2 included in the service target section is to be shared by the system 2, requests the system 2 to share the road, and notifies the system 2 of the number of systems to be covered (the number of systems 1 and 2). On the other hand, the selection unit 102 notifies the system 1 of the number of systems to be covered (2).
[0044] The selection unit 102 requests the system 1 to select road A3, which is a section to be serviced.
[0045] The selection unit 102 requests the system 3 to allocate the road A1, which is the section to be serviced, and notifies the system 2 of the "number of systems to be covered" (the system 2 and the system 3).
[0046] Through the above process, each system 200 is assigned by the integrated server 100 the roads it is responsible for recognizing, transmitting, and storing. Then, when a vehicle travels along a road (short section) requested by the integrated server 100, each system 200 controls the vehicle so that the vehicle photographs the road and roadside and transmits the photographed data to the system 200. Each system 200 also stores the data sent from the vehicle. This allows each system 200 to efficiently process the recognition process, transmission process, and data storage process of the vehicles it manages without duplication.
[0047] Each system 200 manages only the roads that it is responsible for recognizing, transmitting, and storing upon request from the integrated server 100, but this is not limited to the above. Each system 200 may recognize, transmit, and store all the roads that it is responsible for, regardless of the request. In this case, there may be cases where duplicate processing is performed, but the integrated server 100 may select the recognized data and distribute the costs and profits.
[0048] In addition, each system 200 may recognize, transmit, and store not only the roads it is responsible for, but also the roads that the vehicle is not responsible for when the vehicle travels on the road. In this case, the system 200 may not transmit data to the integrated server 100.
[0049] 7 shows the management table 104 obtained by the above process. As shown in the figure, in the adjustment process for the system 200, the management table 104 stores, for each road, the "service target section," "covered systems," "number of covered systems," and "system in charge." The "recognition, transmission, and storage costs," "recognition, transmission, and storage cost division," "revenue," and "revenue distribution" are registered in the billing process and revenue distribution process described later.
[0050] 8 is a flowchart showing the billing process for each system 200 in the integrated server 100. In the integrated server 100, the calculation unit 103 confirms the completion of recognition, transmission, and storage of the service target section (S201). This confirmation process is performed by the calculation unit 103 receiving a completion signal from each system 200.
[0051] The calculation unit 103 grasps the recognition, transmission, and storage costs of each road constituting the service target section, and registers them in the management table 104 (S202). For example, the cost grasping process is performed by the integrated server 100 collectively contracting or providing the recognition, transmission, and storage services of the systems 1 to 3, or by the integrated server 100 aggregating the costs incurred in the recognition, transmission, and storage services that the systems 1 to 3 individually contracted. That is, the integrated server 100 (calculation unit 103) obtains the "recognition, transmission, and storage costs" of each road from each system. This grasping process may be performed from each system 200, or may be registered separately by an operator of the integrated server 100.
[0052] The calculation unit 103 refers to the management table 104 and checks the "number of systems that cover" the service section for each road that constitutes the service section (S203).
[0053] Then, for roads with two or more systems, the calculation unit 103 divides the "recognition, transmission, and storage costs" of those roads by the "number of covering systems" associated with that road (S204). The calculation unit 103 charges the divided costs to all systems 200 covering the service target section (S205). That is, in addition to the systems 200 that perform recognition, transmission, and storage, the other systems 200 that do not perform these management processes also bear the costs. From the viewpoint of fairness, it is preferable to divide the costs equally by the number of systems, but other division methods are not excluded.
[0054] On the other hand, for a road where the "number of systems covering" is 1, the calculation unit 103 charges the full amount of the "recognition, transmission, and storage costs" of that road to the system 200 responsible for the recognition, transmission, and storage of that road.
[0055] These billing processes are carried out by the integrated server 100 notifying each of the systems 1 to 3 of the amount. Upon receiving this notification, each of the systems 200 carries out payment processing for the billed amount.
[0056] The payee is the party that contracted for the services used for recognition, transmission and storage in the system that actually performed the recognition, transmission and storage.
[0057] When integrated server 100 has a contract for the services of recognition, transmission, and storage of systems 1 to 3, integrated server 100 is the payee. When systems 1 to 3 have a contract for the services of recognition, transmission, and storage individually, the system in charge of recognition, transmission, and storage is the payee.
[0058] For example, in the example in Figure 2, for road A2 where system 1 and system 2 are able to recognize, transmit, and store data in an overlapping manner, system 2 is actually responsible for recognition, transmission, and storage and bears the divided costs, and system 1 also bears a similarly divided cost.
[0059] 9 is a diagram showing the management table 104 obtained by the billing process. As shown in the diagram, in this process, the "recognition, transmission, and storage costs" and the "division of the recognition, transmission, and storage costs" (corresponding to the contributions) are registered.
[0060] Fig. 10 is a diagram showing a processing concept showing the integration function in the integration server 100. Fig. 10(a) is a conceptual diagram of a process for integrating the road conditions shared by systems 1 to 3. Here, system 1 recognizes, transmits, and stores data on road A3, system 2 recognizes, transmits, and stores data on road A2, and system 3 recognizes, transmits, and stores data on road A1.
[0061] In the integrated server 100, the service providing unit 105 collects and integrates the road data stored in each of these systems 200. Here, the service providing unit 105 can obtain data showing the condition of Road A by collecting each piece of data on Roads A1 to A3 from Systems 1 to 3 which are in charge of the respective pieces of data.
[0062] 10(b), the integrated server 100 can provide a monitoring service and an investigation service based on the integrated data to the customer. In the present disclosure, the integrated server 100 performs the provision of the service by transmitting data captured by the vehicles under the management of each system to the customer's server or the like.
[0063] FIG. 11 is a flow chart showing the process performed by integrated server 100 to provide a service to a customer.
[0064] The service providing unit 105 requests each system 200 in charge of recognizing, transmitting, and storing each road constituting the service target section to provide data (S301). The service providing unit 105 receives data from each system 200 and integrates it as data for the entire service target section (S302). Then, the service providing unit 105 transmits the data for the service target section to the customer's server, thereby providing the customer with a monitoring service or an investigation service for the service target section (S303).
[0065] FIG. 12 is a schematic diagram showing revenue distribution obtained for services provided to customers. FIG. 12(a) is a diagram showing how revenue for services is obtained from customers. As shown in the figure, in the integrated server 100, revenue for monitoring services and investigation services is obtained from each customer. In terms of processing, money is paid to the operating company of the integrated server 100.
[0066] 12(b) is a diagram showing the calculation of the contribution of each system in integrated server 100. As shown in the figure, the contribution of system 1 is the ratio of the divided cost of roads A2 and A3 to the total cost. Similarly, the contribution of system 2 is the ratio of the divided cost of roads A1 and A2 to the total cost. The contribution of system 3 is the ratio of the cost of road A1 to the total cost. This is because the target section covered by system 3 is only road A1.
[0067] Fig. 12(c) is a diagram showing distribution of the obtained profit according to the degree of contribution of systems 1 to 3. Fig. 12(c) shows that the dividend calculated by integrated server 100 is distributed to each of systems 1 to 3.
[0068] 13 is a flowchart showing the process of distributing revenue in integrated server 100 of the present disclosure. In integrated server 100, revenue processing unit 106 obtains revenue from monitoring service or investigation service in the service target section (S401). In specific processing here, when an operator who operates integrated server 100 receives payment from a customer for monitoring service or the like, the operator registers the payment information (i.e., the amount paid) in integrated server 100. Revenue processing unit 106 of integrated server 100 obtains the payment information as revenue and registers it in the "Revenue" column of management table 104.
[0069] The revenue processing unit 106 refers to the management table 104 and calculates the total "recognition, transmission, and storage costs" of all roads that make up the service target section (S402). An explanation will be given taking roads A1 to A3 in FIG. 14 as an example. In FIG. 14, the revenue processing unit 106 calculates the total cost of roads A1 to A3. That is, the revenue processing unit 106 refers to the management table 104 and calculates a total of 600 yen, consisting of 300 yen for the "recognition, transmission, and storage cost" of road A1, 100 yen for the cost of road A2, and 200 yen for road A3. This is registered in the "total cost" column of the management table 104.
[0070] The revenue processing unit 106 refers to the management table 104 and calculates the ratio of the divided cost borne by each system 200 on each road constituting the service target section to the total cost as the contribution of each system 200 (S403). For example, the revenue processing unit 106 obtains the divided cost of system 2 of 150 yen and the divided cost of system 3 of 150 yen for road A1. The revenue processing unit 106 also calculates a total cost of 600 yen, which is the total divided cost including other roads. This is the total amount of "recognition, transmission, and storage costs" on roads A1 to A3. The revenue processing unit 106 then calculates the ratio of the divided cost to the total cost. The ratio of system 2 to road A1 is 150 / 600=0.25. Similarly, the ratio of system 3 to road A1 is 150 / 600=0.25.
[0071] In the process S403, the cost incurred (split cost) is used as an example of the degree of contribution, but the travel distance of the vehicle managed by each system, i.e., the distance of the small section (road), may also be used. For example, if the distance of road A is x and the distances of roads A1 to A3 in the small section are x1, x2, and x3, respectively, the degree of contribution of system 3 in charge of road A1 is x1 / x.
[0072] The revenue processing unit 106 distributes the revenue to each system 200 according to the contribution of each system 200 (S404). That is, the revenue processing unit 106 calculates the revenue of each system by multiplying the revenue by the above-mentioned ratio. In the present disclosure, the revenue processing unit 106 registers each revenue in the "revenue distribution" column of the management table 104.
[0073] 14 is a specific example of the management table 104 when the profits and the distribution of the profits are registered. As shown in the figure, the distribution amount of each system to the profits for each of the roads A1 to A3 is registered.
[0074] Next, a process for predicting vehicles traveling on roads will be described. In the present disclosure, each system that manages vehicles predicts the roads on which the vehicles will travel, and if the roads are sections covered by the service, the above-mentioned cost division and revenue distribution are performed.
[0075] 15 is a block diagram showing the functional configuration of the system 200. The system 200 includes a vehicle information acquisition unit 201, a driving frequency recording unit 202, a prediction unit 203, an inquiry processing unit 204, a notification unit 205, a vehicle information DB 206, and a prediction DB 207.
[0076] The vehicle information acquisition unit 201 is a part that acquires vehicle information including position information and time information from a vehicle managed by the system 200. The vehicle information acquired by the vehicle information acquisition unit 201 is registered in the vehicle information DB 206. In the vehicle information DB 206, the vehicle ID, the position information, and the time information are stored in association with each other.
[0077] The travel count recording unit 202 is a part that refers to the vehicle information DB 206 and, for example, registers the number of times each vehicle has traveled on each road during a predetermined period of time in the prediction DB 207. As shown in Fig. 16(a), the prediction DB 207 registers the number of times each vehicle has traveled on each road. Here, it is assumed that there are a vehicle 1 and a vehicle 2. Naturally, there may be more vehicles than this.
[0078] The prediction unit 203 is a part that predicts future travel based on the number of times each vehicle has traveled on each road. As an example of a prediction method, the prediction unit 203 predicts that the vehicle will travel in the future if the number of times traveled>threshold value, and predicts that the vehicle will not travel in the future if the number of times traveled<threshold value. As shown in FIG. 16(b), the prediction DB 207 checks the travel prediction of each vehicle for each road. Here, ◯ indicates that the vehicle will travel, and × indicates that the vehicle will not travel.
[0079] The inquiry processor 204 is a part that receives an inquiry from the integrated server 100 about the travel schedule or prediction for each road, and performs processing for that purpose. This inquiry includes identification information indicating each road. The inquiry processor 204 refers to the prediction DB 207, checks whether or not there is a travel prediction for each vehicle for each road that constitutes the service target section, and checks (marks with a circle) the service target section (road) that should be covered by the service (see FIG. 16(c)). Then, the inquiry processor 204 registers in the prediction DB 207 whether or not there is a travel prediction for the target section, and the vehicle, based on the travel prediction for each vehicle and the service target section that should be covered by the service.
[0080] The notification unit 205 is a part that notifies the integrated server 100 of the roads and the systems responsible for the roads, which are the results of the travel prediction.
[0081] 17 is a flowchart showing the processing of the system 200 for predicting vehicle travel. These processing are performed in each system 200. As a prerequisite, the vehicle information acquisition unit 201 acquires vehicle information from each vehicle managed by the system, and registers the vehicle information in the vehicle information DB 206.
[0082] Thereafter, the travel count recording unit 202 records the number of travels of the vehicle for each road with reference to the vehicle information DB 206 (S501). FIG. 16(a) shows that the travel count has been registered in the prediction DB 207. The prediction unit 203 predicts future travel based on the travel count of each vehicle on each road (S502). The prediction is performed, for example, based on the relationship between the travel count and a threshold value. FIG. 16(b) shows that the travel prediction has been registered in the prediction DB 207.
[0083] The inquiry processor 204 receives an inquiry from the integrated server about the planned or predicted travel of the target section (S503), and checks whether the vehicle is predicted to travel on each road (S504). Fig. 16(c) shows that the check is made for each road to see if it is a target section for service, and whether the vehicle is predicted to travel on that road is registered.
[0084] The notification unit 205 refers to the prediction DB 207, and when there is a driving prediction for each road, notifies the integrated server 100 of the road of the driving prediction (S505). When there is no driving prediction, the notification unit does not perform a notification. According to the prediction DB 207 in FIG. 16(c), the notification unit performs a notification that the system 1 has made a prediction for roads A2 and A3.
[0085] In this way, the vehicle's drivability in the target section can be predicted (determined) based on the number of trips, and the integrated server 100 can use this to determine the system's share in the target section.
[0086] In the above process S503, an inquiry may be received regarding the schedule for traveling in the target section. In the present disclosure, the schedule refers to a schedule based on, for example, a service table. For example, buses, transport vehicles, etc. have a set time and travel route, and therefore it is possible to determine whether or not to travel in the target section based on this. In the system 200, when buses, etc. are managed in this manner, the service table can be used to notify the integrated server 100 of the possibility of traveling in the target section. Based on these schedules, they are registered as predictions in the prediction DB.
[0087] Next, the effects of the integrated server 100 of the present disclosure will be described. The integrated server 100 of the present disclosure is an integrated server that provides services in cooperation with systems 1 to 3 operated by multiple different businesses that manage vehicles (automobiles, mobile bodies) having sensors such as cameras. For each road (section) on which the vehicle (mobile body) managed in each of the multiple systems 1 to 3 moves, the traveling road inquiry unit 101 checks one or more systems that manage the vehicle (mobile body) that is about to move through the section. In the above embodiment, the traveling road inquiry unit 101 functions as a confirmation unit, and acquires the roads covered from each system and registers them in the management table 104, thereby performing confirmation processing.
[0088] Based on the registration result (confirmation result) by the travel road inquiry unit 101, the monetary allocation to the selected one system and the systems other than the selected one system is calculated.
[0089] This enables financial allocation between systems operated by different operators, making it possible to reduce costs and prevent lost revenue opportunities. In other words, it prevents the occurrence of wasteful costs associated with duplicate recognition, transmission, and storage of the same vehicle, road, and roadside conditions by multiple systems, and also prevents lost revenue opportunities due to a single system being unable to provide services that cover all of the target sections.
[0090] Furthermore, by receiving a designation of the roads for which it is responsible, each system 200 only needs to recognize, transmit, and store data for those roads, and the freed-up resources for recognition, transmission, and storage can be diverted to other uses.
[0091] In other words, there may be cases where multiple operators incur unnecessary costs due to duplicate recognition, transmission, storage, etc. of the same vehicle or road / roadside conditions. In addition, there may be cases where each operator cannot independently provide services that cover all of the vehicles or roads / roadside conditions specified by the customer, resulting in lost revenue opportunities.
[0092] According to this disclosure, costs can be reduced by preventing duplicate recognition, transmission, and storage of the same road and roadside conditions by multiple operators (if the cost of duplicate recognition, transmission, and storage for multiple systems is N, it can be reduced from N to 1), and the freed resources for duplicate transmission and storage can be repurposed for other purposes, thereby increasing revenue opportunities by enabling multiple operators to provide services that cover all target sections.
[0093] Also, in the present disclosure, in the integrated server 100, the travel road inquiry unit 101 acquires roads (sections) that satisfy a service target section as a predetermined condition among the travel route of the vehicle (for example, a predicted travel route) from each of the multiple systems 1 to 3. Then, the travel road inquiry unit 101 performs a confirmation process by registering one or more systems in the management table 104 based on the acquired roads.
[0094] This makes it possible to obtain the roads covered by the service and the number of systems that cover them, enabling financial allocation.
[0095] The selection unit 102 also functions as a confirmation unit, and when a plurality of systems are confirmed in the management table 104 for each small section such as the road A2, the selection unit 102 selects one system based on a predetermined condition.
[0096] This allows one system to be selected to cover each road segment, and other systems that are not selected do not need to cover that system, so duplicate processing can be avoided.
[0097] In the present disclosure, the calculation unit 103 calculates the monetary allocation based on the confirmed number of systems as a confirmation result.
[0098] Here, monetary allocation refers to the contribution of the costs required for management (recognition, transmission, storage) in one selected system and in other non-selected systems.
[0099] In this way, by having the other system bear the costs, the other system can have the right to receive revenue share for the costs, thereby avoiding revenue loss.
[0100] Also, in this disclosure, monetary allocation refers to a share of revenue for provision of managed-based services in one system and another system.
[0101] The distribution is calculated based on the share of the costs involved in providing management in one system and in the other system.
[0102] The distribution amount may also be calculated based on the ratio of the distance (distance traveled by the vehicle) of the road (section) covered by one system to that covered by the other system.
[0103] This allows revenue sharing in one system or another according to the contributions made.
[0104] The integrated server 100 of the present disclosure includes a service providing unit 105 that provides services based on image data, which is a sensor result obtained from a plurality of systems, and a revenue processing unit 106 that obtains revenue according to the service provided. The calculation unit 103 can calculate monetary allocation based on the revenue.
[0105] In addition, in the present disclosure, the section to be calculated is determined based on the vehicle travel route predicted (or planned) by the system, within the service target section for the service provision.
[0106] The integrated server of the present disclosure has the following configuration.
[0107] [1] An integrated server that provides services in cooperation with systems operated by a plurality of different operators that manage mobile objects having sensors, a confirmation unit that confirms, for each section in which the moving object managed by each of the plurality of systems is to move, one or more systems that manage the moving object that is to move through the section; A calculation unit that calculates monetary allocations for the selected one system and other systems other than the selected one system based on a result of the confirmation by the confirmation unit; An integrated server comprising:
[0108] [2] An acquisition unit that acquires, from each of the plurality of systems, a section of a travel route of the moving object that satisfies a predetermined condition, The verification unit verifies the one or more systems based on the section. [1] The integrated server described in.
[0109] [3] The confirmation unit is selecting one system based on a predetermined condition if multiple systems are identified in each of the sections; [1] or [2].
[0110] [4] the calculation unit calculates a monetary allocation based on the confirmed number of systems as a confirmation result; An integrated server according to any one of [1] to [3].
[0111] [5] The monetary allocation indicates a share of the costs required to perform the management in the one system and the other system. An integrated server according to any one of [1] to [4].
[0112] [6] The monetary allocation refers to a share of revenue for the provision of the management-based services in the one system and the other system. An integrated server according to any one of [1] to [5].
[0113] [7] The distribution amount is calculated based on a share of the costs required for performing the management in the one system and the other system. [6] An integrated server as described in the above.
[0114] [8] The distribution amount is calculated based on a ratio of the distance of the section in charge in the one system and the other system. [6] An integrated server as described in the above.
[0115] [9] a service providing unit that provides services based on sensor results acquired from the plurality of systems; a revenue processing unit that acquires revenue according to the provision of the service; Equipped with The calculation unit calculates the monetary allocation based on the profit. An integrated server according to any one of [1] to [8].
[0116]
[10] The section is determined based on a movement route of the moving object predicted in the system, among target sections for the provision of the service. An integrated server according to any one of [1] to [9].
[0117] The block diagrams used in the description of the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. The method of realizing each functional block is not particularly limited. That is, each functional block may be realized by using one device that is physically or logically combined, or may be realized by using two or more devices that are physically or logically separated and directly or indirectly connected (for example, by wire, wireless, etc.). The functional block may be realized by combining the one device or the multiple devices with software.
[0118] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocation, mapping, assignment, etc. For example, a functional block (component) that performs the function of transmission is called a transmitting unit or a transmitter. In either case, as described above, there is no particular limitation on the method of realization.
[0119] For example, the integrated server 100 and the system 200 according to an embodiment of the present disclosure may function as a computer that performs processing of the integrated processing method of the present disclosure. Fig. 18 is a diagram showing an example of a hardware configuration of the integrated server 100 and the system 200 according to an embodiment of the present disclosure. The integrated server 100 and the system 200 described above may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like.
[0120] In the following description, the term "apparatus" may be interpreted as a circuit, a device, a unit, etc. The hardware configuration of integrated server 100 and system 200 may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.
[0121] Each function in the integrated server 100 and the system 200 is realized by loading a specific software (program) onto hardware such as the processor 1001 and the memory 1002, causing the processor 1001 to perform calculations, control communications via the communication device 1004, and control at least one of the reading and writing of data in the memory 1002 and the storage 1003.
[0122] The processor 1001, for example, operates an operating system to control the entire computer. The processor 1001 may be configured with a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned selection unit 102, calculation unit 103, service provision unit 105, and revenue processing unit 106 may be realized by the processor 1001.
[0123] Moreover, the processor 1001 reads out a program (program code), a software module, data, etc. from at least one of the storage 1003 and the communication device 1004 to the memory 1002, and executes various processes according to the read out programs. As the program, a program that causes a computer to execute at least a part of the operations described in the above-mentioned embodiment is used. For example, the calculation unit 103, the service provision unit 105, and the revenue processing unit 106 may be realized by a control program stored in the memory 1002 and operated in the processor 1001, and other functional blocks may be realized in a similar manner. Although the above-mentioned various processes have been described as being executed by one processor 1001, they may be executed by two or more processors 1001 simultaneously or sequentially. The processor 1001 may be implemented by one or more chips. The program may be transmitted from a network via a telecommunication line.
[0124] The memory 1002 is a computer-readable recording medium, and may be composed of at least one of, for example, a Read Only Memory (ROM), an Erasable Programmable ROM (EPROM), an Electrically Erasable Programmable ROM (EEPROM), a Random Access Memory (RAM), etc. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 can store a program (program code), a software module, etc. that can be executed to implement an integrated processing method according to an embodiment of the present disclosure.
[0125] Storage 1003 is a computer-readable recording medium, and may be composed of at least one of, for example, an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, and the like. Storage 1003 may be referred to as an auxiliary storage device. The above-mentioned storage medium may be, for example, a database, a server, or other suitable medium including at least one of memory 1002 and storage 1003.
[0126] The communication device 1004 is hardware (transmission / reception device) for performing communication between computers via at least one of a wired network and a wireless network, and is also called, for example, a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., in order to realize at least one of, for example, Frequency Division Duplex (FDD) and Time Division Duplex (TDD). For example, the above-mentioned road inquiry unit 101, etc. may be realized by the communication device 1004. The communication device 1004 may be implemented with a transmission unit and a reception unit that are physically or logically separated.
[0127] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that performs output to the outside. The input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).
[0128] In addition, each device such as the processor 1001 and the memory 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.
[0129] Furthermore, integrated server 100 and system 200 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), a field programmable gate array (FPGA), etc., and some or all of the functional blocks may be realized by the hardware. For example, processor 1001 may be implemented using at least one of these pieces of hardware.
[0130] The notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB))), other signals, or a combination thereof. In addition, the RRC signaling may be called an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.
[0131] The order of the steps, sequences, flow charts, etc. of each aspect / embodiment described in this disclosure may be changed unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.
[0132] The input and output information may be stored in a specific location (e.g., memory) or may be managed using a management table. The input and output information may be overwritten, updated, or added to. The output information may be deleted. The input information may be transmitted to another device.
[0133] The determination may be based on a value represented by a single bit (0 or 1), a Boolean (true or false) value, or a numerical comparison (e.g., comparison with a predetermined value).
[0134] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched according to execution. In addition, notification of specific information (e.g., notification that "X is the case") is not limited to being done explicitly, but may be done implicitly (e.g., not notifying the specific information).
[0135] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described in the present disclosure. The present disclosure can be implemented as modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.
[0136] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
[0137] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if the software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave, etc.), then these wired and / or wireless technologies are included within the definition of transmission media.
[0138] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.
[0139] In addition, the terms described in this disclosure and the terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of the channel and the symbol may be a signal (signaling). Also, the signal may be a message. Also, the component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.
[0140] In addition, the information, parameters, etc. described in the present disclosure may be represented using absolute values, may be represented using relative values from a predetermined value, or may be represented using other corresponding information. For example, a radio resource may be indicated by an index.
[0141] The names used for the above-mentioned parameters are not limiting in any way. Moreover, the formulas etc. using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not limiting in any way.
[0142] In this disclosure, the terms "Mobile Station (MS)", "user terminal", "User Equipment (UE)", "terminal", etc. may be used interchangeably.
[0143] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.
[0144] As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in a memory), and the like. In addition, "judgment" and "decision" can include considering resolving, selecting, choosing, establishing, comparing, etc., to be a "judgment" or "decision." In other words, "judgment" and "decision" can include considering some action to be a "judgment" or "decision." In addition, "judgment" can be interpreted as "assuming," "expecting," "considering," etc.
[0145] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using at least one of one or more wires, cables, and printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.
[0146] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."
[0147] Any reference to an element using a designation such as "first", "second" etc. used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must precede the second element in some way.
[0148] When "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Further, when used in this disclosure, the term "or" is not intended to be an exclusive or.
[0149] In this disclosure, where articles have been added due to translation, such as, for example, a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.
[0150] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different." [Explanation of symbols]
[0151] 101...traveling road inquiry unit, 102...selection unit, 103...calculation unit, 104...management table, 106...revenue processing unit, 105...service provision unit, 201...vehicle information acquisition unit, 202...travel count recording unit, 203...prediction unit, 204...inquiry processing unit, 205...notification unit, 206...vehicle information DB, 207...prediction DB.
Claims
1. An integrated server that provides services in cooperation with systems operated by a plurality of different operators that manage mobile objects having sensors, a confirmation unit that confirms, for each section in which the moving object managed in each of the plurality of systems is to move, one or more systems that manage the moving object that is to move in that section; A calculation unit that calculates monetary allocations for the selected one system and other systems other than the selected one system based on a result of the confirmation by the confirmation unit; An integrated server comprising:
2. An acquisition unit that acquires, from each of the plurality of systems, a section of a travel route of the moving object that satisfies a predetermined condition, The verification unit verifies the one or more systems based on the section. The integrated server of claim 1 .
3. The confirmation unit is and if multiple systems are identified in each of the sections, selecting one system based on a predetermined condition. The integrated server of claim 1 .
4. the calculation unit calculates a monetary allocation based on the confirmed number of systems as a confirmation result. The integrated server of claim 1 .
5. The monetary allocation indicates a share of the costs required to perform the management in the one system and the other system. The integrated server of claim 1 .
6. The monetary allocation refers to a share of revenue for the provision of the management-based services in the one system and the other system. The integrated server of claim 1 .
7. The distribution amount is calculated based on a share of the costs required for performing the management in the one system and the other system. The integrated server according to claim 6.
8. The distribution amount is calculated based on a ratio of the distance of the section in charge in the one system and the other system. The integrated server according to claim 6.
9. a service providing unit that provides services based on sensor results acquired from the plurality of systems; a revenue processing unit that acquires revenue according to the provision of the service; Equipped with The calculation unit calculates the monetary allocation based on the profit. The integrated server of claim 1 .
10. The section is determined based on a movement route of the moving object predicted in the system, among target sections for the provision of the service. The integrated server of claim 1 .
Citation Information
Patent Citations
Probe car information system, collecting / providing method and collecting / providing program
JP2005004359A
Information processing apparatus
JP2021163060A
