Management of mobile objects and service platform for mobile objects

To provide different services and information in real time to each automobile or each driver with a high-quality driving assistance or automatic driving system that manages a plurality of mobile objects by communicating with the mobile objects, provided is a system including a mobile object server operable to receive information from each of a plurality of mobile objects within a geographic space and perform a process associated with each mobile object; and a registration server operable to register a first additional process that is to be performed in addition to a first basic process common to the plurality of mobile objects, in association with one mobile object among the plurality of mobile objects. Also provided are a method and program product.

BACKGROUND

The present invention relates to management of mobile objects and a service platform for mobile objects.

A high-speed driving support and automobile system is known that receives information from a plurality of automobiles, acquires information concerning accidents or obstructions on the road and maps this information onto a map along with the position of an automobile, and references automobile position information, automobile characteristic information, and driver characteristic information to transmit suitable event information to each automobile.

However, such a system has a problem that as the geographic space being handled expands, the number of automobiles and the number of roads increases, thereby increasing the amount of information being sent and received to a level that surpasses the processing capability of the server. In addition to event information in the geographic space, such a system is desired to be able to provide different information and services or the like in real time for each automobile or each driver. Furthermore, a function is desired that enables a service provider other than the designer, manager, and/or proprietor of this system to provide information, services, and the like.

SUMMARY

According to a first aspect of the present invention, provided is a system comprising a mobile object server operable to receive information from each of a plurality of mobile objects within a geographic space and perform a process associated with each mobile object; and a registration server operable to register a first additional process that is to be performed in addition to a first basic process common to the plurality of mobile objects, in association with one mobile object among the plurality of mobile objects. Also provided are a method and program product.

DETAILED DESCRIPTION

Hereinafter, example embodiments of the present invention will be described. The example embodiments shall not limit the invention according to the claims, and the combinations of the features described in the embodiments are not necessarily essential to the invention.

FIG. 1shows a system100and a map area corresponding to a geographic space managed by the system100, according to an embodiment of the present invention. The system100manages a geographic space that includes routes on which a mobile object10moves. The system100is operable to divide the geographic space into a plurality of regions and manage these regions. A mobile object10may move on routes including land routes, sea routes, and/or air routes, for example. The geographic space may be land, sea, or air space that includes the routes on which the mobile object travels. The mobile objects10may be manned/unmanned automobiles, motorbikes, bicycles, humans having a digital device, airplanes, vessels, drones, or the like.

FIG. 1shows an automobile as an example of the mobile object10, which moves along roads as examples of land routes. The system100includes a plurality of subsystems200that respectively manage the plurality of regions.FIG. 1shows an example in which the map area is divided into six regions from region A to region F, and six subsystems200respectively manage these six regions.

System100comprises a plurality of event servers210, a plurality of mobile object servers220, a plurality of object servers230, and a plurality of passenger servers240. According to the embodiment ofFIG. 1, each of the subsystems200may include at least one of the plurality of event servers210and one of the plurality of mobile object servers220.

The event server210manages events occurring in each region of the geographic space. In one embodiment, the event server210of subsystem200assigned to region A may manage events in region A. The plurality of mobile object servers220respectively assigned to a plurality of regions in a geographic space manage the mobile objects10in each of the plurality of regions. In one embodiment, the mobile object server220assigned to region A may manages mobile objects10located in region A. The object server230manages information of the mobile objects10regardless of the location of the mobile objects10. The passenger server240manages information of at least one passenger riding on the mobile objects10.

Each of the subsystems200may be implemented on one or more servers. In one embodiment, each event server210and mobile object server220may be implemented on one server. In one embodiment, a set of an event server210and a mobile object server220in a subsystem200may be implemented by one server. Portions of the system100other than the subsystems200may also be implemented on one or more servers. In one embodiment, each object server230and passenger server240may be implemented on one server. In another embodiment, a set of object servers230and a set of passenger servers240may be each implemented by one server. In yet another embodiment, all of the object servers230and the passenger servers240may be implemented on one server. These servers may exist at any point on a network including the Internet, a subscriber network, a cellular network, or a desired combination of networks. The servers may be computers or other types of data processors, and may be dedicated servers, or may be shared servers that perform other operations.

The system100acquires the positions of a mobile object10from the mobile object10, and the mobile object server220managing the region that includes the acquired position of the mobile object10may manage the movement of this mobile object10. The system100acquires information of events that have occurred to the mobile object10and/or on the road outside, and the event server210managing the region including the position where such an event has occurred may manage the state of the event.

This event may include information about accidents, obstructions, closure, limitation, status, or construction on the road, or information about the weather, temperature, buildings, shops, or parking lots near the road. In response to a setting or a request from the mobile object10, the subsystem200may provide notification about the event information to the mobile object10that made the request. For example, if the mobile object10is moving on a route in a geographical area corresponding to region A, then the mobile object sever220managing region A provides this mobile object10with the notification about the event relating to the route.

Since the map area is divided into a plurality of regions, despite the mobile object10simply moving on a route, the region corresponding to the position of the mobile object10might change.FIG. 1shows an example in which the mobile object10is driving on a road such that the position of the mobile object10moves from region A to region B on the regions. In this case, according to the movement of the mobile object10, the system100may transfer the information concerning the mobile object10from the mobile object server220managing region A to the mobile object server220managing region B, and may also transfer the management of the mobile object10to the mobile object server220managing region B.

FIG. 2shows a subsystem200and a map area corresponding to a region A managed by the subsystem200, according to an embodiment of the present invention. The event server210manages at least one event agent, and executes each event agent to manage events on routes in a region assigned to the event server210. An “agent” may be a software entity having specific data, and may operable to receive a message (e.g. command), and return a result of the message. Each region of the plurality of regions of geographic space includes at least a portion of one area of the plurality of areas. In this embodiment, the region assigned to the event server210is the same as the region assigned to the mobile object server220. However, in other embodiments, these regions may be different.

In the embodiment ofFIG. 2, the region A, which is the region assigned to the event server210, is divided into 16 areas and 16 areas are assigned to each of the event agents EA1-EA16. The event server210executes each of the event agents EA1-EA16to manage events occurring on routes of each area of region A. For example, the event agent EA2may manage a “closure” event on an area corresponding to EA2on the map, and the event agent EA4may manage a “speed limit” event on an area corresponding to EA4as shown inFIG. 2.

The plurality of mobile object servers220may include at least one mobile object server220including one or more mobile object agents, each of which is assigned to each of the mobile objects10. In the embodiment ofFIG. 2, the mobile object server220includes three mobile object agents MOAs1-3assigned to three mobile objects10in the assigned region A. The mobile object server220executes each of the mobile object agents MOA1-MOA3to manage the mobile objects10traveling on the region A.

FIG. 3shows an exemplary configuration of the system100, according to an embodiment of the present invention. The system100may be operable to communicate with each of a plurality of mobile objects10to send and receive the information used to manage the mobile objects10. The system100may be operable to acquire map data and/or information exchanged with the mobile objects10, through the Internet, a subscriber network, a cellular network, or any desired combination of networks. The system100includes an acquiring section (i.e., module)110, a dividing section130, a region manager140, a receiving section150, a transmitting section152, a gateway apparatus160, a plurality of subsystems200, a plurality of object servers230, and a plurality of passenger servers240.

The acquiring section110may be operable to acquire map data corresponding to the geographical areas where a mobile object10is positioned, from an external database30, for example. In response to the map being updated, the acquiring section110may acquire some or all of the updated map data. The acquiring section110may be operable to acquire the map data from the Internet, a subscriber network, a cellular network, or any desired combination of networks. The system100may be operable to store the map data in advance.

The acquiring section110may further acquire an event that has occurred within the geographic space to be managed by the system100. In this case, the acquiring section110may acquire, accident information, traffic information, weather information, time information, etc.

The dividing section130may be operable to communicate with the acquiring section110and divide the map area into a plurality of regions. In this embodiment, the dividing section130generates two groups of regions by dividing an original map area into a plurality of regions.

The region manager140may be operable to store information concerning the plurality of regions including the regions resulting from the division. The region manager140may be operable to specify the subsystem200managing the region that includes the position of the mobile object10, in response to receiving the position of the mobile object10. The region manager140may be implemented on one or more servers. The region manager140includes a storage section142and a determining section146.

The storage section142may be operable to communicate with the dividing section130and store information concerning the plurality of first regions and the plurality of second regions resulting from the division by the dividing section130. The storage section142may store setting values or the like of the system100.

The storage section142may store intermediate data, calculation results, threshold values, parameters, and the like that are generated by or used in the operations of the system100. In response to a request from any component within the system100, the storage section142may supply the data stored therein to the component making the request. The storage section142may be a computer readable storage medium such as an electric storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, or a semiconductor storage device.

The determining section146may be operable to communicate with the storage section142, and determine one region from the plurality of regions (e.g., regions A-F ofFIG. 1) in which each of the mobile objects10is located based on the position information of the mobile object10and geographic information of the plurality of regions. The determining section146may identify a route or position in the map area managed by the system100that corresponds to the position information of the mobile object10.

The determining section146may store the position information of this mobile object10and/or information of the determined region in the storage section142, in association with this mobile object10. The determining section146may store a history of the position information of this mobile object10and/or a history of the determined mobile object server220in the storage section142. The determining section146may be a circuit, a shared or dedicated computer readable medium storing computer readable program instructions executable by a shared or dedicated processor, etc.

The receiving section150may be operable to receive information transmitted from each of a plurality of mobile objects10. Each mobile object10may transmit information at designated time intervals, and the receiving section150may sequentially receive this transmitted information. In this embodiment, the receiving section150may receive car probe data from each mobile object10as the information. The car probe data may include information detected by the mobile object10, such as position information of the mobile object10.

In one embodiment, the position information may include longitude and latitude (and optionally altitude information) of the mobile object10in an absolute coordinate system. In another embodiment, the mobile object10may determine its location in the absolute coordinate system by using GPS, and the determining section146receiving the position information may determine a route on which the mobile object10exists and a specific location of the route at which the mobile object10exists based on the position information. Alternatively, the mobile object10may include such detailed position information in the car probe data.

The receiving section150may communicate with the plurality of mobile objects10and receive the car probe data of each mobile object10, via the Internet40. The receiving section150may receive the car probe data of the plurality of mobile objects10through wireless communication, a subscriber network, a cellular network, or any desired combination of networks.

The transmitting section152may be operable to transmit event information to each of the mobile objects10according to settings, for example. The transmitting section152may transmit information concerning the route on which the mobile object10is expected to travel. The transmitting section152may communicate with the mobile objects10and transmit each type of information to the mobile objects10via the Internet40. The transmitting section152may transmit each type of information to the mobile objects10through wireless communication, a subscriber network, a cellular network, or any desired combination of networks.

The gateway apparatus160may be operable to transfer communication between the plurality of subsystems200and the plurality of mobile objects10. The gateway apparatus160may communicate with the receiving section150and receive the information transmitted by each mobile object10.

The gateway apparatus160may communicate with the region manager140and demand the transfer destination for each piece of information received from the mobile objects10, of the region manager140. In response to this request, the gateway apparatus160may receive from the region manager140the information of the subsystem200managing the region on which the mobile object10exists. The gateway apparatus160may transfer the information received from the mobile object10to the subsystem200that is to manage the mobile object10. In other words, the gateway apparatus160may transfer the information received from each mobile object10to the subsystem200determined by the region manager140.

The gateway apparatus160may communicate with each of the subsystems200, and receive the information transmitted by each subsystem200. The gateway apparatus160may communicate with the transmitting section152and supply the transmitting section152with the information received from each subsystem200, such that this information is transferred to the mobile objects10designated for each subsystem200.

The gateway apparatus160may include a plurality of gateway devices, and may quickly perform transfer between the plurality of subsystems200and the plurality of mobile objects10. In this case, the receiving section150may function as a load balancer that supplies the information from the mobile objects10, such that the load is spread among the plurality of gateways. The load balancer may sequentially supply information from the mobile objects10to the gateways having lighter loads. The gateway apparatus160may be a network that provides a connection between a plurality of networks using the same or different types of protocols.

A plurality of subsystems200may be operable to communicate with the region manager140and the gateway apparatus160and to respectively manage a plurality of regions in a geographic space. Each subsystem200is operable to manage mobile objects10that travel routes in its managing region and to manage events on its managing region.

As described, each subsystem200may include the event server210and the mobile object server220. The event server210manages events occurring on its managing region with the plurality of the event agents. In one embodiment, the event server210may perform, through the event agent, (i) registration, update and/or deletion of events, (ii) registration, update and/or deletion of candidate events, and (iii) provision of event information.

The mobile object server220manages the plurality of the mobile objects10traveling on its managing region with the plurality of the mobile object agents. In one embodiment, the mobile object server220may perform, through the mobile object agent, (i) processing of the car probe data, (ii) update of information of the mobile object, and (iii) provision of information to the mobile object. For example, the mobile object server220may execute the mobile object agent to collect information of events from at least one event server210, and provide the mobile object10with information that assists the mobile object10with traveling in the geographic space.

A plurality of object servers230including at least one object server230may communicate with the gate way160and include an object agent (OA) containing information of the mobile object10. An object agent may correspond to each mobile object10and contain information thereof. In one embodiment, the object agent may contain (i) information, by region, of which subsystem currently manages a mobile object agent of the mobile object10, (ii) an identification (ID) of the mobile object10, (iii) an ID of a passenger of the mobile object10, and (iv) a characteristic of the mobile object10(e.g., model/version information, width, length, and/or height of the mobile object10).

The object server230may perform, through the object agent, (i) provision and/or update of information of the mobile object10, (ii) registration, update, and/or deletion of the ID of passenger riding on the mobile object10, (iii) provision and/or update of the information of the region of the mobile object10, and (iv) provision of information needed for generation of a new mobile object agent by the mobile object server220.

At least one passenger server240of a plurality of passenger servers may communicate with the gateway160, and include a passenger agent that contains information of at least one passenger. A passenger agent may correspond to each passenger or candidate passenger of mobile objects10, and contain information thereof. In one embodiment, the object agent may contain an ID of a passenger and a characteristic of the passenger (e.g., information of age, gender, type, and the like of license of the passenger). The passenger server240may perform, through the passenger agent, provision and/or update of information of the passengers.

As described above, the system100of the present embodiment may manage the mobile objects by utilizing the mobile object agents in each mobile object server220, and manage the events by utilizing the event agent in each event server210. According to the system100of the embodiment, the system100can separately manage information relating to the mobile objects10and events on the geographic map with a plurality of kinds of servers. Furthermore, the plurality of mobile object servers220can smoothly transfer the management of the mobile objects10traveling across the regions via the mobile object agents, thereby improving the efficiency of the whole system100. In addition, according to the system100of the embodiment, each event server210divides event management in one region among the plurality of event agents and provides the mobile object agent with event information, thereby improving the efficiency of event management in the region (e.g., improving response time of event search) and thus event notification to the mobile objects10. In addition, the system100can provide the mobile object agent with information of mobile object10by the object agent of the object server230. The system100can also provide the mobile object agent with information of passengers of the mobile objects10by the passenger agent of the passenger server240.

FIG. 4shows management of events by the event server210and the mobile object server220, according to an embodiment of the present invention. In this embodiment, a mobile object10is traveling on a target route on region A and transmitting a car probe data including the position information to the event server210managing region A with the car probe data via a gateway apparatus, such as the gateway apparatus160. The event server210manages event information through each event agent based on the car probe data from the mobile objects on region A. For example, each event agent may manage an event list (containing information of an event and an influence event for routes on the area managed by the event agent) and a candidate event list (containing information of candidates of an event for routes on the area managed by the event agent).

In the embodiment ofFIG. 4, the event agent EA2manages events of an area (indicated as “DA2” on the region A ofFIG. 4) by the event list of the event agent EA2and the candidate event list of the event agent EA2based on car probe data from the mobile object10on the area DA2. For example, the event agent EA2assigned to the area DA2is executable to generate an event based on the information from the mobile object10.

In one embodiment, each mobile object server220is operable to receive information from the mobile object10in the region A assigned to the mobile object server220. The mobile object server220determines the target route where the mobile object10is located. The mobile object server220sends the information to one event server210assigned to a region A where the mobile object10is located, and thereby requests the event agent EA2assigned to the area DA2where the target route is located to send an event list containing information of an event on the target route and the influence event of the target route.

The mobile object server220executes the mobile object agent MOA1for the mobile object10to provide the mobile object10with information that assists the mobile object10with traveling in the area DA2based on the information of the event on the other route and the influence event of the target route. In the embodiment ofFIG. 4, the mobile object agent MOA1receives, from the event agent EA2, the event information of the route on which the mobile object10exists, and provides the mobile object10with the event information (e.g., information of closure).

FIG. 5shows management of a mobile object10by the mobile object servers220and object server230, according to an embodiment of the present invention. The mobile object server220-1may transfer the mobile object agent to the mobile object server220-2assigned to a neighboring region in response to the mobile object10moving to the neighboring region. In this embodiment, in response to a mobile object10traveling from region A to region B, the mobile object server220-1managing region A deletes the mobile object agent MOA for the mobile object10, and a mobile object server220-2managing region B generates a mobile object agent MOA for the mobile object10.

In this embodiment, the object server230may store information that includes a mobile object server identifier MOS-ID that identifies one of the plurality of mobile object servers220executing the mobile object agent corresponding to the object agent10. Just after the mobile object10arrives at region B, the mobile object server220-2has not been executing the mobile object agent for the mobile object10. The mobile object server220-2is operable to receive information from the mobile object10in the region B assigned to the mobile object server220-2.

Using the information from the mobile object10, the mobile object server220-2obtains the mobile object server identifier MOS-ID from the object server230that manages the object agent for the mobile object10because the mobile object server220-2is not executing the mobile object agent for the mobile object10. The mobile object server220-2requests a mobile object server220-1identified by the mobile object server identifier MOS-ID to transfer the mobile object agent for the mobile object10. Then the mobile object server220-1managing region A transfers the mobile object agent to the mobile object server220-2assigned to a neighboring region B in response to the request.

FIG. 6shows an operational flow of a system, according to an embodiment of the present invention. The present embodiment describes an example in which the system100performs the operations from S610to S680shown inFIG. 6to manage mobile objects, such as mobile object10, and events on a map area.FIG. 6shows one example of the operational flow of the system100shown inFIGS. 1-5, but the system100shown inFIGS. 1-5is not limited to using this operational flows explained below. Also, the operational flow inFIG. 6may be performed by other systems.

First, an acquiring section, such as the acquiring section110, may acquire the map data of the geographic space to be managed by the system (S610). The acquiring section may acquire map data of a geographic space that includes one or more cities, one or more towns, and the like. The acquiring section may include map data of a geographic space including one or more states, countries, continents, etc. A dividing section, such as the dividing section130, may divide the map area to generate a plurality of regions.

Next, the system may perform an initialization process for the mobile object (S620). The system may perform the process of S620if a user (passenger) initializes a setting of a mobile object and any passengers of the mobile object, before starting to drive the mobile object.

After S620, a gateway apparatus, such as the gateway apparatus160, of the system may acquire a car probe data from the mobile object (S630). Although the system may acquire the car probe data from the plurality of the mobile objects, the system acquiring a car probe data from one mobile object (which, may be referred to as “a target mobile object”) is explained in the below description. The car probe data may include information detected by the target mobile object, such as current position information of the target mobile object, a speed and/or direction of the target mobile object, and event information observed by the target mobile object (e.g., occurrence of ABS, detection of obstacles, or the like). In one embodiment, the position information may include an edge ID of an edge on which the target mobile object exists and the distance between the current location of the target mobile object and the one end of the edge.

Next, the gateway apparatus may determine a region on which the target mobile object is traveling based on the position information of the car probe data of the target mobile object (S640). In one embodiment, the gateway apparatus may inquire a region manager, such as the region manager140, about the region on which the mobile object exists. A determining section, such as the determining section146, of the region manager may determine the region the target mobile object and provide the gateway apparatus with the information of the region of the target mobile object. The gateway apparatus may provide an event server, such as the event server210, that manages the determined region and a mobile object server, such as the mobile object server220, that manages the determined region with the car probe data.

Next, the event server that is provided with the car probe data of the target mobile object may process events for the mobile objects (S650). The event server may manage event information based on the car probe data for notification of events to the target mobile object.

After S650, the mobile object server that is provided with the car probe data of the target mobile object may manage a mobile object agent for the target mobile object (S660).

After S660, the system determines whether to end the process for the target mobile object. In one embodiment, the gateway apparatus may determine whether the car probe date indicates the engine stop of the target mobile object. If the system determines not to end the process, then the system proceeds with the process of S630for the target mobile object. If the system determines to end the process, then the system ends the process for the target mobile object, and may continue the process for other mobile objects.

As described above, the system manages mobile objects by utilizing mobile object agents realized by the plurality of the mobile object servers. Since the system can transfer the mobile object agent between the mobile object servers, it can efficiently manage the mobile objects traveling around the plurality of regions. Furthermore, the system collects car probe data from the mobile objects and manages events generated from the car probe data by utilizing the event agents. Since each event server divides a number of events occurring on its managing regions into a plurality of areas by utilizing the event agents, it can efficiently handle event information.

The process of S610may be performed once before starting processes S620-S680. The process of S620-S680may be performed for every mobile object.

FIG. 7shows an operational flow of an initialization process for a mobile object, according to an embodiment of the present invention. The present embodiment describes an example in which the system performs an initialization process, such as the initialization process of S620ofFIG. 6, through processes S621to S623shown inFIG. 7.

First, a gateway apparatus receives a setting data (including an ID of the mobile object, an ID(s) of passenger(s) and position information of the mobile object) from the mobile object (S621). The gateway apparatus determines one mobile object server that manages the mobile object based on the position information of the mobile object. The gateway apparatus provides the determined mobile object server with the setting data. Then, the determined mobile object server obtains information (e.g., ID(s) of the passenger(s)) of at least one passenger of the mobile object from the setting data of the mobile object.

Then, the mobile object server may request the object agent of the object server for the mobile object to store the information of the at least one passenger of the mobile object (S622). For example, each mobile object may be mapped to each object agent of the object servers based on values of the IDs of the mobile objects, and the mobile object server may identify one object agent corresponding to the ID of the mobile object based on the calculation using the ID. Then, the mobile object server may provide the object server managing the identified object agent with the setting data including the position information, the ID of the mobile object, and ID(s) of passenger(s) of the mobile object via the gateway apparatus.

Next, the object server stores the information of passenger(s) on an object agent. In one embodiment, each of passengers may be preliminarily mapped to each of the passenger servers based on values of the IDs of passengers, and the passenger servers may have information of passengers. The object server may identify one passenger server corresponding to the ID of a passenger based on the calculation using the ID. The object server may receive, via the gateway apparatus, the information of passengers from the passenger server corresponding to the ID. Then, the object server may store or update the information of the mobile object and the passengers of the mobile object, in the object agent for the mobile object. The object server may include the information of a region that the mobile object currently exists, in the object agent.

Next, the mobile object server220managing the region in which the mobile object10exists generates a new mobile object agent for the mobile object10(S623). In one embodiment, the mobile object server220may copy the information of the object agent for the mobile object10to the newly generated mobile object agent. For example, the mobile object server220may store the information of the mobile object10and the information of the at least one passenger of the mobile object10in the newly generated mobile object agent for the mobile object10.

FIG. 8shows an operational flow of event processing, according to an embodiment of the present invention. The present embodiment describes an example in which the system performs event processing, such as the event processing of S650ofFIG. 6, through processes S651to S659shown inFIG. 8.

First, the event server may identify an event agent (S651). In one embodiment, the event sever determines one event agent from the plurality of event agents based on the position information of the target mobile object. The determined event agent may be referred to as “target event agent.” For example, the event server determines a target route (or an edge of the map data) of the target mobile object based on the position information and the map data, and selects, as a target event agent, an event agent that manages an area including the target route of the target mobile object indicated by the car probe data. In another embodiment, the car probe data of a target mobile object may include the information of the target route of the target mobile object.

Next, the event server may edit event lists by the target event agent based on the car probe data (S652). In one embodiment, the target event agent may generate or update information of events (e.g., an edge that an event occurs, an event ID, a location of an event, and content of event) of the target route on the event list based on information of the car probe data. The event of the target route may be referred to as a “target event.”

Next, the event server may search, by the target event agent, an influence event on the target route on the area of the target event agent based on the car probe data (S653). The influence event of the target route relates to an event on another route within a threshold distance (e.g., a threshold travelling distance of the target route, a threshold number of edges away from the target route, and/or a threshold travelling time from the target route).

In one embodiment, the target event agent itself may search routes (or edge IDs) apart from the target route within the threshold distance based on the topology information of routes in the regions, or may request other entities (e.g., a server) to search for routes (or edge IDs).

Next, the event server may determine whether the event list of the target event agent includes event entries corresponding to all influence events of the target route searched at S653(S654). In one embodiment, the target event agent determines whether edges of the influence events are listed as edge IDs of events in the event list.

If an area managed by a target event agent includes the routes (edges) of all influence events relating to an event, then an event list of the target event agent includes corresponding event entries of all influence events. However, if the routes (edges) of any influence events are managed by other event agents, then the event list may not include corresponding event entries of all influence events. If the decision is positive, then the event server proceeds with the process S655and if negative, the event server proceeds with the process S656.

At S655, the event server may edit a notification event ID list by the target event agent. The notification event ID list includes IDs of influence events and edge IDs of the influence events that are determined to be not included in the event list of the target event agent at S654. In other words, the notification event ID list is a list of event IDs of influence events that are not managed by the target event agent. Then, the event server may proceed with the process of S656.

At S656, the event server may edit a notification event list for the target mobile object, by the target event agent. The notification event list is a list of events that may be helpful to the target mobile object traveling on the target route. The notification event list may include target events and influence events of the target events. The target event agent may add entries of the target events and the influence events in its managing event list for notification.

Next, the event server determines, by the target event agent, whether the notification event ID list has at least one entry. If the decision is positive, then the event server proceeds with the process of S658, and if negative, then the event server ends the process of S650.

At S658, the event server may identify, by the target event agent, an event agent that manages an event list including events in the notification event ID list. The determined event agent may be referred to as “remote event agent.”

Next, the event server may acquire information of events in the notification event ID list (S659), and end the process S650. In one embodiment, the target event agent may receive information of events in the notification event ID list from the remote event agent, and edit the notification event list based on the acquired information. In another embodiment, the target event agent may add entries of the influence events in the notification event ID list based on the acquired information.

FIG. 9shows an illustrative example of an event list, according to an embodiment of the present invention. As described inFIG. 9, the event list may include edge IDs of events, event IDs of events, locations of events, specific contents of events, and influence events relating to events. In this embodiment, each route is represented as “edge.” For example, this event list indicates that an event (identified as “Eve0214”) has occurred along the full length of edge0001on the area, that the event has limited the speed to 30 km/h, and that edge0001includes an influence event identified as “Eve0114.” The event list also indicates that an event (identified as “Eve0114” on edge0002) has occurred 32 m from the 1st node on edge0002on the area, that the event is a closure of a route, and that edge0001includes influence events identified as “Eve0214” on edge0001, “Eve0421” on edge0003, etc. In one embodiment, the target event agent may add a new entry corresponding to an event detected by the car probe data, in the event list.

According to the first entry in the event list ofFIG. 9, the edge0001has influence event0114. This may mean that a mobile object traveling on the edge0001is influenced by the event0114that has occurred apart from edge0001within a threshold distance. In response to receiving the car probe data including the position information indicating that the target mobile object is traveling on the edge0001, the target event agent searches and obtains routes (edge IDs) apart from the target route (edge0001) within the threshold distance, and then finds neighboring edge0002as a result. In response to receiving the car probe data including the position information of the edge0001, the target event agent determines whether the edge of influence event (edge0002) corresponding to the target route is listed as edge IDs in the event list.

The target event agent assigned to the area may generate or update a candidate event based on information from the target mobile object. In one embodiment, the target event agent may generate or update candidate events on the candidate event list including information of a plurality of edges on the area of the event agent based on information of the car probe data.

Although the event list ofFIG. 9includes information of influence events, the information of the influence events may be managed by another list. In one embodiment, the event agent may manage both a first event list containing information of an event on the target route and a second event list containing information of the influence event.

FIG. 10shows an illustrative example of a candidate event list, according to an embodiment of the present invention. As described inFIG. 10, the event list may include edge IDs of candidate events, counts of detecting candidate events, locations of candidate events, and specific contents of candidate events for each candidate event. For example, this candidate event list indicates that evidence of an event (congestion) has been observed twice along the full length of edge0009on the area, and that evidence of an event (skid) has been observed once at a point 15 m from the 2nd node on edge0013on the area.

The target event agent may determine whether to change a candidate event in the candidate event list to an event in the event list. In one embodiment, the target event agent may upgrade the candidate event to the event based on information from other mobile objects. In this case, the target event agent counts occurrences of a candidate event observed by a plurality of mobile objects (including the target mobile object and other mobile objects). If the count of a candidate event exceeds a threshold value, then the target event agent determines that the candidate event is upgraded to an event. In one embodiment, in response to the upgrade, the target event agent deletes the entry of the candidate event from the candidate event list, and generates a new entry of an event corresponding to the deleted candidate event. The event servers may set the same or different criteria for upgrading candidate events among the plurality of event agents.

FIG. 11shows an illustrative example of a notification event list, according to an embodiment of the present invention. As described inFIG. 11, the notification event list may include edge IDs of target/influence events, event IDs of target/influence events, locations of target/influence events, and specific contents of target/influence events. For example, this notification event list indicates that an event (speed limit) has occurred along the full length of edge0001on the area, and that an event (closure) has occurred at a point 32 m from the 1st node on edge0002on the area.

FIG. 12shows a mobile object and events, according to an embodiment of the present invention. In the embodiment ofFIG. 12, the target mobile object10is traveling eastbound on the edge0001, which is the target route. The target event agent EA1manages an area including the edge0001, the edge0002, the edge0101, and the edge0102, and the neighboring event agent EA2manages an area including the edge0003, the edge0103, and the edge0104.

Direction dependent edges are described inFIG. 12. However, edges may not be direction dependent according other embodiments, and in such embodiments, the event agent may manage events, candidate events, and influence events with direction information. The target event agent EA1manages an event (Eve0214) on the edge0001as the target event in the event list. Since the edge0002is apart from the edge0001within the threshold distance, the target event agent EA1also manages an event (Eve0114) on the edge0002as an influence event in the event list. The target event agent EA1manages a notification event list including the target event (Eve0214) and the influence event (Eve0114) for the target mobile object10.

In the embodiment ofFIG. 12, the mobile object agent managing target mobile object requests the event agent EA1that manages the target event (e.g., Eve0214) and the influence event (e.g., Eve0114) to send the notification event list including the target event and the influence event. In another embodiment, the mobile object agent may request the remote event agent EA2that manages the information of influence event(s) (e.g., Eve0421) to send a notification event list containing information of the influence event(s) if the influence event is located outside of the area including the target route (Edge0001).

FIG. 13shows an operational flow of mobile object processing, according to an embodiment of the present invention. The present embodiment describes an example in which the system manages the target mobile object, such as in S660ofFIG. 6, through processes S661to S669shown inFIG. 13.

At S661, the mobile object server may determine whether the mobile object agent for the target mobile object exists in the region determined to be the region of the mobile object, such as the region determined at S640. In other words, the mobile object server determines whether the mobile object server manages the mobile object agent of the target mobile object. If the decision is positive, then the mobile object server proceeds with the process S667, and if negative, the mobile object server proceeds with the process S662.

At S662, the mobile object server may identify an object server that includes the object agent containing the information of the target mobile object. In one embodiment, the mobile object server may identify the object server in the same manner described in S622.

Next, at S663, the mobile object server may inquire the object server230identified at S662for the location of the mobile object agent of the target mobile object. The object server may refer to the object agent of the target mobile object, obtain information of the mobile object server that currently manages the mobile object agent MOA of the target mobile object, if it exists, and provide the mobile object server with the information.

Next, the mobile object server may determine whether the mobile object agent for the target mobile object exists in any other regions. In other words, the mobile object server may determine which mobile object server manages the mobile object agent for the target mobile object from the plurality of mobile object servers managing other regions, at S663. If the decision is positive, then the mobile object server proceeds with the process S666, and if negative the mobile object server proceeds with the process S665.

At S665, the mobile object server generates a new mobile object agent MOA for the target mobile object. The mobile object server may generate the mobile object agent MOA for the target mobile object by obtaining information of the target mobile object from the object server that includes the object agent containing the information of the target mobile object. In one embodiment, the mobile object server may generate the new mobile object agent in the same manner described in S623. The mobile object server may also communicate with the object server via the gateway apparatus, and register the current region of the target mobile object in the object agent corresponding to the target mobile object. By generating the new mobile object agent, the system can handle a new mobile object10that has been not managed by the mobile object server.

At S666, the mobile object server may transfer the mobile object agent from the other mobile object server determined to manage the mobile object agent for the target mobile object at S664. In one embodiment, the mobile object server may receive information of the mobile object agent for the target mobile object from the other mobile object server, and generate a new mobile object agent including the received information. The mobile object server may also communicate with the object server via the gateway apparatus, and register the current region of the target mobile object in the object agent of the target mobile object.

Next, at S667, the mobile object server may receive a notification event list for the target mobile object. In one embodiment, the mobile object server first determines the target route where the target mobile object is located. Then, the mobile object server may request the event agent that manages the information of target event(s) and influence event(s) corresponding to the target route to send a notification event list containing information of the target event(s) and influence event(s) of the target route.

At S668, the mobile object server may update the current location of the target mobile object by the mobile object agent. In one embodiment, the mobile object agent for the target mobile object updates the current location of the target mobile object based on the position information of the car probe data.

At S669, the mobile object server may execute the mobile object agent for the target mobile object to provide the target mobile object with information that assists the target mobile object with traveling in the geographic space based on the information included in the event list. In one embodiment, the mobile object agent may provide the target mobile object with information of events on the notification event list.

In one embodiment, the at least one mobile object server may execute the mobile object agent for the target mobile object to provide the target mobile object with information that assists the target mobile object with traveling in the geographic space based on the information of the at least one passenger of the target mobile object. For example, the mobile object agent may provide the target mobile object with an alert, a notice, and/or an action list relating events on the notification event list depending on a number of passengers (e.g., for guiding a car pool lane), the age, gender, license, real time information (e.g., driving history or sleep history), and characteristics of the passengers.

The action list is a list of actions recommended to passengers in response to the events (e.g., braking, accelerating, and/or steering of the target mobile object).

The action list may include commands to the target mobile object for automatic driving and/or driving assist. In one embodiment, the mobile object agent may include information that the passenger is sensitive to rough driving, and then the mobile object agent may provide commands to gently drive the target mobile object. In one embodiment, the mobile object agent may include information of driving skill of a driver passenger, and then provide different commands depending on the skill of the driver. The mobile object server may provide the target mobile object with the information via the gateway apparatus.

As described above, the mobile object server receives information from the target mobile object in the region assigned to the mobile object server, and generates the mobile object agent for the target mobile object if there is no mobile object server among the plurality of mobile object servers that is executing the mobile object agent.

FIG. 14shows an exemplary configuration of the system100, according to an embodiment of the present invention. In this embodiment, each subsystem200includes an event server210, mobile object server220, an object server230, and a passenger server240. However, other embodiments are also possible, in which each subsystem200comprises any combination of singles or multiples of each server. In other embodiments, the system100may manage allocation of object agents of the object server230and passenger agents of the passenger server240in the subsystem200. For example, the gateway apparatus160may change allocation of the object/passenger agents to the subsystems200to rectify the imbalance of data processing loads among the subsystems200.

In the embodiment described above, the event server210may manage allocated event agents. In other embodiments, the system100may manage allocation of event agents to the event servers210. For example, the gateway apparatus160may change allocation of event agents to the event servers210to rectify the imbalance of loads of processing events among the event servers210. In the embodiment described above, the event server210causes each event agent to manage allocated divided area derived from a region. In other embodiment, the event server210causes at least one event agent to manage specific information regarding events (e.g., cross section of roads or other specific function(s) of a map, or, hurricane or other disaster/accident).

FIG. 15shows an exemplary configuration of a system100according to the present embodiment. In the system100according to the present embodiment, components having substantially the same operation as components of the system100of the embodiment shown inFIGS. 3 and 14are given the same reference numerals, and redundant descriptions are omitted. The system100according to the present embodiment is in communication with a plurality of mobile objects10to manage these mobile objects, and also provides each individual mobile object or individual passenger with different information, services, and the like in real time.

As described above, the system100includes an event server210that processes events occurring in a geographic space and a mobile object server220operable to transmit suitable event information to each mobile object10and assist with the movement of the plurality of mobile objects10in the geographic space. In the present embodiment, the process of transmitting event information to a mobile object10performed by the mobile object server220is referred to as a first basic process. The system100includes a registration server310for each subsystem200.

The registration server310may be operable to register a first additional process to be performed in addition to the first basic process common to a plurality of mobile objects10, in association with a single mobile object10among the plurality of mobile objects10. In this case, the registration server310may be operable to register the first additional process in association with one mobile object agent associated with one mobile object10. The registration server310may register the first additional process with a mobile object agent, or may instead register the first additional process with the object server230.

The registration server310may register a rule and/or logic that is a process more complex than a rule as each first additional process. Specifically, the registration server310may register an inherent rule and/or logic to one or more mobile objects10as first additional processes in the corresponding one or more mobile object agents. A first basic process may be a rule and/or logic performed in common for the plurality of mobile objects10, and registered in the event server210or the event agent server.

The registration server310may be operable to register a second addition process to be performed in addition to a second basic process common to a plurality of passengers, in association with a single passenger among the plurality of passengers. In this case, the registration server310may register the second additional process with one passenger agent associated with one passenger.

The registration server310may register a rule and/or logic that is a process more complex than a rule as each second additional process. The registration server310may register an inherent rule and/or logic to one or more passengers as second additional processes in the corresponding one or more passenger agents. The second basic process may be a rule and/or logic performed in common for the plurality of passengers. The second basic process is registered in the passenger agent or event agent and performed by the passenger server240or the event server210according to characteristics of the passengers, for example.

The mobile object server220according to the present embodiment may be operable to receive information from each of a plurality of mobile objects10in a geographic space and perform a process associated with each mobile object10. In this case, the mobile object server220may be operable to perform processes set for a mobile object agent associated with each of the mobile objects10. Specifically, rules and/or logic corresponding respectively to the plurality of mobile objects10may be registered in mobile object agents corresponding respectively to the mobile objects10, and the mobile object server220may perform the rules and/or logic registered in the event agents.

The mobile object server220may be operable to perform the processes set for the mobile object agents associated respectively with the mobile objects10, using the event processing results of the event server210. In this case, after the event processing by the event server210, the mobile object server220may perform the processes recorded in the mobile object agents.

The mobile object server220may be operable to perform processes associated respectively with the passengers. In this case, the mobile object server220may be operable to perform the processes set for the passenger agent associated with each passenger riding in one mobile object10. Specifically, if rules and/or logic corresponding respectively to a plurality of passengers are registered in corresponding passenger agents, the mobile object server220may perform the rules and/or logic registered in the passenger servers.

The system100includes a plurality of the mobile object servers220, and therefore each mobile object server220may be operable to perform processes set for a mobile object agent associated with each of the mobile objects10moving respectively in a plurality of regions obtained by dividing the geographic space. Each mobile object server220may be operable to perform the processes set for the passenger agent associated with each of the mobile objects10moving respectively in the plurality of regions obtained by dividing the geographic space.

The system100of the present embodiment described above identifies the mobile object agent and passenger agent corresponding to the car probe data acquired from a mobile object10, and performs the processes set in this mobile object agent and passenger agent. The operation of such a system100is described below.

FIG. 16shows an exemplary configuration of a portion of the operational flow of the system100according to the present embodiment. The system100according to the present embodiment performs the operational flow shown inFIG. 16to perform each process set for a plurality of mobile objects10in the geographic space. For example, the operational flow shown inFIG. 16is performed by the system100after S660of the operational flow described inFIG. 6.

Specifically, in the processing up to S660, the system100may receive the car probe data from a mobile object10and identify the mobile object agent corresponding to the mobile object10and the passenger agent corresponding to the passenger of the mobile object10. The system100may identify the event agent associated with the identified mobile object agent and passenger agent, and perform the first basic process and/or second basic process set for the identified event agent. For example, in response to an event that is an accident occurrence on a route on which the mobile object10moves, the system100performs a process of notifying the mobile object10with information about this accident as the first basic process.

At S672inFIG. 16, the registration server310may register the first additional processes and/or the second additional processes. The registration server310may register the corresponding first additional process in one or more mobile object agents identified in the processing up to S660. The registration server310may register, in each mobile object agent, a first additional process corresponding to a characteristic, state, travelled route, or the like of the mobile object10. For example, for one mobile object10that includes a navigation system and has turned ON a setting to display information concerning detours, the registration server310registers a first additional process of “if there is an accident, search for a detour where this accident has occurred and provide the search results as notification” in the mobile object agent corresponding to this one mobile object10.

The registration server310may register a corresponding second additional process in one or more passenger agents identified in the processing up to S660. The registration server310may register, in each mobile object agent, a second additional process corresponding to a characteristic or the like of a passenger of the mobile object10. For example, for a passenger of one mobile object10who has a medical license, the registration server310may register a second additional process of “if there is an accident, search for the scale of the accident, people injured in the accident, the dispatch state of ambulances, and the like, and provide the search results as notification” in the passenger agent corresponding to the passenger of the one mobile object10.

The registration server310may be operable to register a call-up condition for calling up a first additional process, in association with one mobile object agent. In a similar manner, the registration server310may be operable to register a call-up condition for calling up a second addition process, in association with one passenger agent. The registration server310may be operable to register the first additional process and the second additional process together with respective priorities. If there is no new process to be registered beyond the processes that have already been registered, the registration server310may proceed to the next stage.

At S674, the mobile object server220may select a first additional process and a second additional process to be performed. If a call-up condition is registered for the first additional process or the second additional process, the mobile object server220may select the additional process that fulfills this call-up condition.

If the number of registered first additional processes and second additional processes is less than or equal to a reference number or a threshold value, the mobile object server220may select all of the registered first additional processes and second additional processes. In this case, the mobile object server220may perform all of the registered first additional processes and second additional processes. If the number of registered first additional processes and second additional processes is greater than the reference number or the threshold value, the mobile object server220may select a number of first additional processes and second additional processes substantially equal to the reference number or the threshold value. In this case, the mobile object server220may select the first additional processes and second additional processes to be performed according to the priority or the like.

The mobile object server220may be operable to perform the additional processes associated with each mobile object10, at S676. The mobile object server220may be operable to, when performing processes set for one mobile object agent, call up and perform a first additional process in response to the call-up condition being satisfied. Similarly, the mobile object server220may be operable to, when performing processes set for one passenger agent, call up and perform a second additional process in response to the call-up condition being satisfied. The mobile object server220may perform all of the first additional processes and second additional processes for which no call-up condition is registered in the mobile object agent and the passenger agent. The mobile object server220may perform the first additional processes and the second additional processes according to the priority or the like.

The mobile object server220may be operable to perform a process of providing notification that one mobile object10has become distanced from a predetermined location or geographical region. For example, if a mobile object10having a theft notification function set to ON has moved at least a reference distance from a parking position, the mobile object server220provides notification of theft to a registered destination. Furthermore, if a passenger has a contract for insurance that stipulates conditions such as an age limit, a passenger limit (e.g. family members only), a driving region limit (e.g. a country or state), a vehicle type, a license, a limit to a certain automobile, or the like, the mobile object server220may notify the passenger in response to the contract conditions being violated (e.g. if the mobile object10moves outside of the limited driving region).

If a family member is driving who is unused to driving, for example, the mobile object server220may provide a warning as notification to the registered destination in response to the mobile object10moving outside of a set range. If the mobile object10is a specialized vehicle that is wider and taller than a normal passenger automobile, in response to this mobile object10moving off of a route on which a vehicle with this height and width can travel, the mobile object server220may provide the passengers with a warning, search for a route on which the mobile object10can travel, and provide notification of this route or guidance to this route.

The mobile object server220may be operable to perform a process of providing notification that someone other than a predetermined passenger is manipulating one mobile object10, as the first additional process or the second additional process. Since the mobile object server220can perform processing including complicated logic, it is possible to perform processes such as transmitting e-mail, making a telephone call, providing notification to a plurality of registered destinations, providing notification to a second candidate if notification to a first candidate is impossible, and the like.

The mobile object server220may perform processes set for a mobile object agent using processing results of an event from the event server210. For example, in response to an event of an accident occurring on a route on which a mobile object10is moving, the mobile object server220performs a process that includes searching for a detour route near the location where this accident occurred and providing the search results as notification, as the first additional process. Furthermore, in response to an event of an accident occurring on a route on which a mobile object10is moving, the mobile object server220may perform a process that includes searching for the scale of the accident, people injured in the accident, the dispatch state of ambulances, and the like, and providing the search results as notification as the second additional process.

If the additional processes of the mobile object server220have ended, the system100may perform S680of the operational flow shown inFIG. 6. By performing the operational flow described above, the system100according to the present embodiment can provide an additional process that includes handling different information and performing services in real time, for each mobile object10or each passenger.

FIG. 17shows feature information used to select the first additional process to be performed, by the mobile object server220according to the present embodiment. As an example,FIG. 17shows feature information used when the mobile object server220performs the operation of S674shown inFIG. 16. The mobile object server220may manage a plurality of mobile objects10using corresponding mobile object IDs, andFIG. 17shows these mobile object IDs in the first column. The second column and the third column inFIG. 17show the current location of each mobile object10. The fourth column inFIG. 17shows whether the owner of the mobile object10is an individual or a company. In this way, the second to fourth columns ofFIG. 17may include feature information held by the mobile object agents corresponding to the mobile objects10.

The fifth column inFIG. 17shows the age of the passengers, the sixth column shows whether the passengers are the owners, and the seventh column shows the number of people riding along with the passengers (drivers) of the mobile objects10. In this way, the fifth to seventh columns ofFIG. 17may include feature information held by the passenger agents corresponding to the passengers of the mobile objects10. The mobile object server220may be operable to perform a corresponding additional process if a change occurs in this feature information.

Specifically, the call-up conditions registered by the registration server310may have, as necessary conditions, changes of designated pieces of feature information among a plurality of pieces of feature information relating to one mobile object10held by one mobile object agent. For example, in response to a change occurring in the current position of a mobile object10in the second column and/or the third column, the mobile object server220performs a first additional process such as “searching for whether the current position is included in a region that is covered by the insurance to which the owner of the mobile object10is subscribed, and providing the search results as notification.”

The call-up conditions registered by the registration server310may have, as necessary conditions, changes of designated pieces of feature information among a plurality of pieces of feature information relating to one passenger held by one passenger agent. For example, in response to a change occurring in the feature information of a passenger in the sixth column, the mobile object server220performs a second additional process such as “searching for whether the current passenger is included as a person insured by the insurance to which the owner of the mobile object10is subscribed, and providing the search results as notification.” As another example, in response to a change occurring in the feature information of a passenger in the sixth column, the mobile object server220performs a second additional process such as “searching for whether the current passenger is an acquaintance or family member registered by the owner of the mobile object10, and providing the owner with the search results as notification.”

FIG. 17shows an example of a security company and insurance company to which a passenger is subscribed providing information, a service, or the like to a mobile object10and the passenger. In this case, the insurance company and security company may make a request for settings of the system100or the like based on the information, service, or the like to be provided, to the designer, manager, and/or proprietor of this system100. Instead, the system100may be operable to allow a service provider differing from the designer, manager, and/or proprietor of this system100to access the system and provide the service. Such a system100is described below.

FIG. 18shows an exemplary configuration of the system100according to the present embodiment. In the system100according to the present embodiment, components having substantially the same operation as those of the system100according to the embodiment shown inFIG. 15are given the same reference numerals and redundant descriptions are omitted. The system100according to the present embodiment is an example of a service platform for a plurality of mobile objects that is operable to cooperate with an external system or the like. The system100may further include a collaboration server400.

The collaboration server400may be operable to control access to the system100from an external server or the like. The collaboration server400may be operable to perform authentication of the external server, for example. The collaboration server400manages mobile objects, passengers, rules, logic, and/or external servers using respectively corresponding IDs, and controls the access, for example.

An external server or the like that has been authenticated by the collaboration server400may be operable to communicate with the event server210, the mobile object server220, the object server230, the passenger server240, and/or the registration server310. Furthermore, an external server or the like that has been authenticated by the collaboration server400may be operable to communicate with a mobile object agent, a passenger agent, and/or an event agent.

Specifically, the mobile object server220may be operable to call-up a service process provided by the external server or the like when performing a first additional process registered in one mobile object agent. In this way, a service provider or the like that is different from the designer, manager, and/or proprietor of the system100can provide services and information using real time data of a plurality of mobile objects10, for example.

The registration server310may be operable to register a first additional process in association with one mobile object agent in response to a request from an external server or the like that is run by a service provider providing a service. In this way, a service provider or the like that is different from the designer, manager, and/or proprietor of the system100can design or add a variety of services that are not offered by the system.

For example, a security company can provide the owner of a mobile object10who has entered into a contract with a theft prevention service. In response to a person who is not a registered passenger moving the mobile object10outside of a set region, the security company may provide the owner of the mobile object10with a warning and track the movement of the mobile object10. In response to instructions from the owner or a reference time having passed, the security company may notify the police or the like of theft.

An insurance company can provide the owner of a mobile object10who has entered into a contract with real time information indicating whether the insurance is applicable. If the owner of the mobile object10has done something that falls outside the range covered by the insurance, the insurance company may provide an insurance contract that covers a wider range.

A car rental company can provide a service using the position information of a user. The car rental company may provide services corresponding to detailed monetary amounts, according to the movement distance and/or the movement region. The rental car company may suitably designate a rental location and a return location, according to the position information of the user and the arrangement state of the mobile objects10. A taxi company and a taxi driver can know a dispatch state and occupied state in real time.

The above describes an example in which the system100according to the present embodiment has the registration server310register the first additional processes, second additional processes, and call-up conditions in the mobile object agents. Instead, the registration server310may register the first additional processes, second additional processes, and call-up conditions in object servers230associated with the mobile object agents. In this case, the mobile object server220may be operable to copy the information of the mobile object10and the information concerning the first additional processes, second additional processes, and call-up conditions from the object server230to the mobile object agent during the step of generating the mobile object agent corresponding to a mobile object10, e.g. S623ofFIG. 7.

In this way, the mobile object server220can perform the processes set for the mobile object agent based on information possessed by the mobile object agent, and can therefore improve the processing speed. The registration server310may be operable to perform the registration to the object server230before the step of generating the mobile object agent. Specifically, the registration server310may be operable to register the first additional processes, second additional processes, and call-up conditions in the object server230during S620(initialization) inFIG. 6.

Instead, for some of the mobile objects10among the plurality of mobile objects10, the mobile object server220may copy the information of the mobile objects10and the information of the first additional processes, second additional processes, and call-up conditions from the object server230to the mobile object agents. Instead of this, for a plurality of mobile objects10, the mobile object server220need not copy the information of the first additional processes, second additional processes, and call-up conditions from the object server230to the mobile object agents.

The mobile object server220may be operable to, if performing a mobile object agent that does not include information of a first process, a second process, or a call-up condition, question the object server230about this information. In this way, the subsystem200can decrease the amount of memory used.

If a process with high performance frequency, a condition with high change frequency, or a process desired to have a high processing speed is determined, the mobile object server220may copy the information of the first additional processes, second additional processes, and call-up conditions corresponding to this process from the object server230to a mobile object agent. In other words, if a process with low performance frequency, a condition with low change frequency, or a process whose processing speed is irrelevant is determined, the mobile object server220need not copy the information corresponding to this process or condition from the object server230to the mobile object agent. In this way, the subsystem200can improve the processing speed while reducing the amount of memory used.

FIG. 19shows an exemplary configuration of a computer1900according to an embodiment of the invention. The computer1900according to the present embodiment includes a CPU2000, a RAM2020, a graphics controller2075, and a display apparatus2080which are mutually connected by a host controller2082. The computer1900also includes input/output units such as a communication interface2030, a hard disk drive2040, and a DVD-ROM drive2060which are connected to the host controller2082via an input/output controller2084. The computer also includes legacy input/output units such as a ROM2010and a keyboard2050which are connected to the input/output controller2084through an input/output chip2070.

The host controller2082connects the RAM2020with the CPU2000and the graphics controller2075which access the RAM2020at a high transfer rate. The CPU2000operates according to programs stored in the ROM2010and the RAM2020, thereby controlling each unit. The graphics controller2075obtains image data generated by the CPU2000on a frame buffer or the like provided in the RAM2020, and causes the image data to be displayed on the display apparatus2080. Alternatively, the graphics controller2075may contain therein a frame buffer or the like for storing image data generated by the CPU2000.

The input/output controller2084connects the host controller2082with the communication interface2030, the hard disk drive2040, and the DVD-ROM drive2060, which are relatively high-speed input/output units. The communication interface2030communicates with other electronic devices via a network. The hard disk drive2040stores programs and data used by the CPU2000within the computer1900. The DVD-ROM drive2060reads the programs or the data from the DVD-ROM2095, and provides the hard disk drive2040with the programs or the data via the RAM2020.

The ROM2010and the keyboard2050and the input/output chip2070, which are relatively low-speed input/output units, are connected to the input/output controller2084. The ROM2010stores therein a boot program or the like executed by the computer1900at the time of activation, a program depending on the hardware of the computer1900. The keyboard2050inputs text data or commands from a user, and may provide the hard disk drive2040with the text data or the commands via the RAM2020. The input/output chip2070connects a keyboard2050to an input/output controller2084, and may connect various input/output units via a parallel port, a serial port, a keyboard port, a mouse port, and the like to the input/output controller2084.

A program to be stored on the hard disk drive2040via the RAM2020is provided by a recording medium as the DVD-ROM2095, and an IC card. The program is read from the recording medium, installed into the hard disk drive2040within the computer1900via the RAM2020, and executed in the CPU2000.

A program that is installed in the computer1900and causes the computer1900to function as an apparatus, such as the region manager, the subsystems200and other element(s) in the system100ofFIG. 3,FIG. 14,FIG. 15, andFIG. 18, includes a determining module. The program or module acts on the CPU2000, to cause the computer1900to function as a section, component, element such as determining section146.

The information processing described in these programs is read into the computer1900, to function as the determining section, which is the result of cooperation between the program or module and the above-mentioned various types of hardware resources. Moreover, the apparatus is constituted by realizing the operation or processing of information in accordance with the usage of the computer1900.

For example when communication is performed between the computer1900and an external device, the CPU2000may execute a communication program loaded onto the RAM2020, to instruct communication processing to a communication interface2030, based on the processing described in the communication program. The communication interface2030, under control of the CPU2000, reads the transmission data stored on the transmission buffering region provided in the recording medium, such as a RAM2020, a hard disk drive2040, or a DVD-ROM2095, and transmits the read transmission data to a network, or writes reception data received from a network to a reception buffering region or the like provided on the recording medium. In this way, the communication interface2030may exchange transmission/reception data with the recording medium by a DMA (direct memory access) method, or by a configuration that the CPU2000reads the data from the recording medium or the communication interface2030of a transfer destination, to write the data into the communication interface2030or the recording medium of the transfer destination, so as to transfer the transmission/reception data.

In addition, the CPU2000may cause all or a necessary portion of the file of the database to be read into the RAM2020such as by DMA transfer, the file or the database having been stored in an external recording medium such as the hard disk drive2040, the DVD-ROM drive2060(DVD-ROM2095) to perform various types of processing onto the data on the RAM2020. The CPU2000may then write back the processed data to the external recording medium by means of a DMA transfer method or the like. In such processing, the RAM2020can be considered to temporarily store the contents of the external recording medium, and so the RAM2020, the external recording apparatus, and the like are collectively referred to as a memory, a storage section, a recording medium, a computer readable medium, etc. Various types of information, such as various types of programs, data, tables, and databases, may be stored in the recording apparatus, to undergo information processing. Note that the CPU2000may also use a part of the RAM2020to perform reading/writing thereto on the cache memory. In such an embodiment, the cache is considered to be contained in the RAM2020, the memory, and/or the recording medium unless noted otherwise, since the cache memory performs part of the function of the RAM2020.

The CPU2000may perform various types of processing, onto the data read from the RAM2020, which includes various types of operations, processing of information, condition judging, search/replace of information, etc., as described in the present embodiment and designated by an instruction sequence of programs, and writes the result back to the RAM2020. For example, when performing condition judging, the CPU2000may judge whether each type of variable shown in the present embodiment is larger, smaller, no smaller than, no greater than, or equal to the other variable or constant, and when the condition judging results in the affirmative (or in the negative), the process branches to a different instruction sequence, or calls a sub routine.

In addition, the CPU2000may search for information in a file, a database, etc., in the recording medium. For example, when a plurality of entries, each having an attribute value of a first attribute is associated with an attribute value of a second attribute, are stored in a recording apparatus, the CPU2000may search for an entry matching the condition whose attribute value of the first attribute is designated, from among the plurality of entries stored in the recording medium, and reads the attribute value of the second attribute stored in the entry, thereby obtaining the attribute value of the second attribute associated with the first attribute satisfying the predetermined condition.

The above-explained program or module may be stored in an external recording medium. Exemplary recording mediums include a DVD-ROM2095, as well as an optical recording medium such as a Blu-ray Disk or a CD, a magneto-optic recording medium such as a MO, a tape medium, and a semiconductor memory such as an IC card. In addition, a recording medium such as a hard disk or a RAM provided in a server system connected to a dedicated communication network or the Internet can be used as a recording medium, thereby providing the program to the computer1900via the network.

As made clear from the above, the embodiments of the present invention can be used to realize a system for managing geographic space and mobile objects and a platform for mobile objects thereon.