U.S. patent application number 15/855408 was filed with the patent office on 2018-12-27 for management of mobile objects.
The applicant listed for this patent is INTERNATIONAL BUSINESS MACHINES CORPORATION. Invention is credited to SATOSHI HOSOKAWA, YASUTAKA NISHIMURA, MAKOTO TANIBAYASHI, SHOICHIRO WATANABE.
Application Number | 20180374357 15/855408 |
Document ID | / |
Family ID | 64693496 |
Filed Date | 2018-12-27 |
United States Patent
Application |
20180374357 |
Kind Code |
A1 |
HOSOKAWA; SATOSHI ; et
al. |
December 27, 2018 |
MANAGEMENT OF MOBILE OBJECTS
Abstract
An embodiment of the invention may include a method, computer
program product and computer system for managing mobile objects.
The embodiment may receive an event detected in a geographic space
by a mobile object of a plurality of mobile objects. The embodiment
may determine a reliability of the event based on a reliability
associated with the mobile object. The embodiment may store the
event in a mobile object database based on the reliability of the
even being above a reference reliability.
Inventors: |
HOSOKAWA; SATOSHI; (KODAIRA,
JP) ; NISHIMURA; YASUTAKA; (YAMATO, JP) ;
TANIBAYASHI; MAKOTO; (SUGAMACHI, JP) ; WATANABE;
SHOICHIRO; (NERIMA-KU, JP) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
INTERNATIONAL BUSINESS MACHINES CORPORATION |
Armonk |
NY |
US |
|
|
Family ID: |
64693496 |
Appl. No.: |
15/855408 |
Filed: |
December 27, 2017 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
15628815 |
Jun 21, 2017 |
|
|
|
15855408 |
|
|
|
|
Current U.S.
Class: |
1/1 |
Current CPC
Class: |
G05D 1/0238 20130101;
G08G 1/0129 20130101; G06F 16/489 20190101; H04W 4/44 20180201;
H04L 67/12 20130101; B60W 30/08 20130101; G01C 21/32 20130101; G08G
1/162 20130101; G01S 17/931 20200101; B60W 30/0956 20130101; G08G
1/0112 20130101; G08G 1/09623 20130101; G06F 16/29 20190101; B60W
30/0953 20130101; G08G 1/0141 20130101 |
International
Class: |
G08G 1/16 20060101
G08G001/16; G06F 17/30 20060101 G06F017/30; G05D 1/02 20060101
G05D001/02; B60W 30/08 20120101 B60W030/08; B60W 30/095 20120101
B60W030/095 |
Claims
1. A method for managing mobile object, the method comprising:
receiving an event detected in a geographic space by a mobile
object of a plurality of mobile objects, wherein receiving the
event detected in the geographic space by the mobile object of the
plurality of mobile objects includes changing a reception frequency
of the event detected by the mobile object, according to the
reliability of the mobile object detecting an event; determining a
reliability of the event based on a reliability associated with the
mobile object, wherein determining the reliability of the event
includes determining the reliability of the one event based on the
reliability associated with each of two or more mobile objects
among the plurality of mobile objects in the mobile object
database, in response to the two or more mobile objects detecting
the one event; storing the event in a mobile object database based
on the reliability of the event being above a reference
reliability, wherein storing the event in a mobile object database
includes storing the reliability of each mobile object among the
plurality of mobile objects detecting an event in the mobile object
database, in association with each of one or more sensors possessed
by each mobile object; updating, in the mobile object database, the
reliability associated with the mobile object that detected the
event in the mobile object database based on a detection result of
the one event by the mobile object; and performing a process
relating to the plurality of mobile objects based on the event
being stored in the mobile object database, wherein performing the
process includes providing notification of existence of the one
event to another mobile object among the plurality of mobile
objects.
Description
BACKGROUND
[0001] The present invention relates to management of the movement
of mobile objects.
[0002] Driving support and automobile systems receive information
by communicating with a plurality of automobiles, acquire event
information concerning accidents or obstructions on the road and
map this information onto a map along with the position of an
automobile. Such systems reference automobile position information,
automobile characteristic information, driver characteristic
information, and the like, and transmits suitable event information
to each automobile.
BRIEF SUMMARY
[0003] An embodiment of the invention may include a method,
computer program product and computer system for managing mobile
objects. The embodiment may receive an event detected in a
geographic space by a mobile object of a plurality of mobile
objects. The embodiment may determine a reliability of the event
based on a reliability associated with the mobile object. The
embodiment may store the event in a mobile object database based on
the reliability of the even being above a reference
reliability.
BRIEF DESCRIPTION OF THE DRAWINGS
[0004] FIG. 1 shows a system 100 according to an embodiment of the
present invention and a map area corresponding to a geographic
space managed by the system 100.
[0005] FIG. 2 shows a subsystem 200 according to the embodiment of
the present invention and a map area corresponding to a region A
managed by the subsystem 200.
[0006] FIG. 3 shows a first exemplary configuration of the system
100 according to the present embodiment.
[0007] FIG. 4 shows management of events by the event server 210
and the mobile object server 220 according to one embodiment.
[0008] FIG. 5 shows management of mobile object by the mobile
object server 220 and object server 230 according to one
embodiment.
[0009] FIG. 6 shows an operational flow of an exemplary
configuration of the system 100 according to the present
embodiment.
[0010] FIG. 7 shows an operational flow of S620 according to the
present embodiment.
[0011] FIG. 8 shows an operational flow of S650 according to the
present embodiment.
[0012] FIG. 9 shows an illustrative example of an event list.
[0013] FIG. 10 shows an illustrative example of a candidate event
list.
[0014] FIG. 11 shows an illustrative example of a notification
event list.
[0015] FIG. 12 shows a mobile object 10 and events according to one
embodiment.
[0016] FIG. 13 shows an operational flow of S660 according to the
present embodiment.
[0017] FIG. 14 shows a second exemplary configuration of the system
100 according to the present embodiment.
[0018] FIG. 15 shows an exemplary configuration of the system 100
according to another embodiment.
[0019] FIG. 16 shows a process flow of the system 100 according to
the present embodiment.
[0020] FIG. 17 shows an exemplary candidate event list in the
present embodiment.
[0021] FIG. 18 shows an exemplary detection rule.
[0022] FIG. 19 shows exemplary data of the detection result.
[0023] FIG. 20 shows a detection target object designated by the
detection rule of FIG. 18.
[0024] FIG. 21 shows exemplary statistical information stored in
the mobile object database 2300.
[0025] FIG. 22 shows another example of statistical information
stored in the mobile object database 2300.
[0026] FIG. 23 shows an exemplary hardware configuration of a
computer according to the embodiment of the invention.
DETAILED DESCRIPTION
[0027] Embodiments of the present invention will now be described
in detail with reference to the accompanying Figures.
[0028] 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.
[0029] FIG. 1 shows a system 100 and a map area corresponding to a
geographic space managed by the system 100, according to an
embodiment of the present invention. The system 100 manages a
geographic space that includes routes on which a mobile object 10
moves. The system 100 is operable to divide the geographic space
into a plurality of regions and manage these regions. A mobile
object 10 may 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 objects 10 may be manned/unmanned
automobiles, motorbikes, bicycles, humans having a digital device,
airplanes, vessels, drones, or the like.
[0030] FIG. 1 shows an automobile as an example of the mobile
object 10, which moves along roads as examples of land routes. The
system 100 includes a plurality of subsystems 200 that respectively
manage the plurality of regions. FIG. 1 shows an example in which
the map area is divided into six regions from region A to region F,
and six subsystems 200 respectively manage these six regions.
[0031] System 100 comprises a plurality of event servers 210, a
plurality of mobile object servers 220, a plurality of object
servers 230, and a plurality of passenger servers 240. According to
the embodiment of FIG. 1, each of the subsystems 200 may include at
least one of the plurality of event servers 210 and one of the
plurality of mobile object servers 220.
[0032] The event server 210 manages events occurring in each region
of the geographic space. In one embodiment, the event server 210 of
subsystem 200 assigned to region A may manage events in region A.
The plurality of mobile object servers 220 respectively assigned to
a plurality of regions in a geographic space manage the mobile
objects 10 in each of the plurality of regions. In one embodiment,
the mobile object server 220 assigned to region A may manages
mobile objects 10 located in region A. The object server 230
manages information of the mobile objects 10 regardless of the
location of the mobile objects 10. The passenger server 240 manages
information of at least one passenger riding on the mobile objects
10.
[0033] Each of the subsystems 200 may be implemented on one or more
servers. In one embodiment, each event server 210 and mobile object
server 220 may be implemented on one server. In one embodiment, a
set of an event server 210 and a mobile object server 220 in a
subsystem 200 may be implemented by one server. Portions of the
system 100 other than the subsystems 200 may also be implemented on
one or more servers. In one embodiment, each object server 230 and
passenger server 240 may be implemented on one server. In another
embodiment, a set of object servers 230 and a set of passenger
servers 240 may be each implemented by one server. In yet another
embodiment, all of the object servers 230 and the passenger servers
240 may 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.
[0034] The system 100 acquires the positions of a mobile object 10
from the mobile object 10, and the mobile object server 220
managing the region that includes the acquired position of the
mobile object 10 may manage the movement of this mobile object 10.
The system 100 acquires information of events that have occurred to
the mobile object 10 and/or on the road outside, and the event
server 210 managing the region including the position where such an
event has occurred may manage the state of the event.
[0035] 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 object 10, the subsystem 200 may provide
notification about the event information to the mobile object 10
that made the request. For example, if the mobile object 10 is
moving on a route in a geographical area corresponding to region A,
then the mobile object sever 220 managing region A provides this
mobile object 10 with the notification about the event relating to
the route.
[0036] Since the map area is divided into a plurality of regions,
despite the mobile object 10 simply moving on a route, the region
corresponding to the position of the mobile object 10 might change.
FIG. 1 shows an example in which the mobile object 10 is driving on
a road such that the position of the mobile object 10 moves from
region A to region B on the regions. In this case, according to the
movement of the mobile object 10, the system 100 may transfer the
information concerning the mobile object 10 from the mobile object
server 220 managing region A to the mobile object server 220
managing region B, and may also transfer the management of the
mobile object 10 to the mobile object server 220 managing region
B.
[0037] FIG. 2 shows a subsystem 200 and a map area corresponding to
a region A managed by the subsystem 200, according to an embodiment
of the present invention. The event server 210 manages at least one
event agent, and executes each event agent to manage events on
routes in a region assigned to the event server 210. 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 server
210 is the same as the region assigned to the mobile object server
220. However, in other embodiments, these regions may be
different.
[0038] In the embodiment of FIG. 2, the region A, which is the
region assigned to the event server 210, is divided into 16 areas
and 16 areas are assigned to each of the event agents EA1-EA16. The
event server 210 executes each of the event agents EA1-EA16 to
manage events occurring on routes of each area of region A. For
example, the event agent EA2 may manage a "closure" event on an
area corresponding to EA2 on the map, and the event agent EA4 may
manage a "speed limit" event on an area corresponding to EA4 as
shown in FIG. 2.
[0039] The plurality of mobile object servers 220 may include at
least one mobile object server 220 including one or more mobile
object agents, each of which is assigned to each of the mobile
objects 10. In the embodiment of FIG. 2, the mobile object server
220 includes three mobile object agents MOAs 1-3 assigned to three
mobile objects 10 in the assigned region A. The mobile object
server 220 executes each of the mobile object agents MOA1-MOA3 to
manage the mobile objects 10 traveling on the region A.
[0040] FIG. 3 shows an exemplary configuration of the system 100,
according to an embodiment of the present invention. The system 100
may be operable to communicate with each of a plurality of mobile
objects 10 to send and receive the information used to manage the
mobile objects 10. The system 100 may be operable to acquire map
data and/or information exchanged with the mobile objects 10,
through the Internet, a subscriber network, a cellular network, or
any desired combination of networks. The system 100 includes an
acquiring section 110, a dividing section 130, a region manager
140, a receiving section 150, a transmitting section 152, a gateway
apparatus 160, a plurality of subsystems 200, a plurality of object
servers 230, and a plurality of passenger servers 240.
[0041] The acquiring section 110 may be operable to acquire map
data corresponding to the geographical areas where a mobile object
10 is positioned, from an external database 30, for example. In
response to the map being updated, the acquiring section 110 may
acquire some or all of the updated map data. The acquiring section
110 may be operable to acquire the map data from the Internet, a
subscriber network, a cellular network, or any desired combination
of networks. The system 100 may be operable to store the map data
in advance.
[0042] The acquiring section 110 may further acquire an event that
has occurred within the geographic space to be managed by the
system 100. In this case, the acquiring section 110 may acquire,
accident information, traffic information, weather information,
time information, etc.
[0043] The dividing section 130 may be operable to communicate with
the acquiring section 110 and divide the map area into a plurality
of regions. In this embodiment, the dividing section 130 generates
two groups of regions by dividing an original map area into a
plurality of regions.
[0044] The region manager 140 may be operable to store information
concerning the plurality of regions including the regions resulting
from the division. The region manager 140 may be operable to
specify the subsystem 200 managing the region that includes the
position of the mobile object 10, in response to receiving the
position of the mobile object 10. The region manager 140 may be
implemented on one or more servers.
[0045] The storage section 142 may be operable to communicate with
the dividing section 130 and store information concerning the
plurality of first regions and the plurality of second regions
resulting from the division by the dividing section 130. The
storage section 142 may store setting values or the like of the
system 100.
[0046] The storage section 142 may store intermediate data,
calculation results, threshold values, parameters, and the like
that are generated by or used in the operations of the system 100.
In response to a request from any component within the system 100,
the storage section 142 may supply the data stored therein to the
component making the request. The storage section 142 may 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.
[0047] The determining section 146 may be operable to communicate
with the storage section 142, and determine one region from the
plurality of regions (e.g., regions A-F of FIG. 1) in which each of
the mobile objects 10 is located based on the position information
of the mobile object 10 and geographic information of the plurality
of regions. The determining section 146 may identify a route or
position in the map area managed by the system 100 that corresponds
to the position information of the mobile object 10.
[0048] The determining section 146 may store the position
information of this mobile object 10 and/or information of the
determined region in the storage section 142, in association with
this mobile object 10. The determining section 146 may store a
history of the position information of this mobile object 10 and/or
a history of the determined mobile object server 220 in the storage
section 142. The determining section 146 may be a circuit, a shared
or dedicated computer readable medium storing computer readable
program instructions executable by a shared or dedicated processor,
etc.
[0049] The receiving section 150 may be operable to receive
information transmitted from each of a plurality of mobile objects
10. Each mobile object 10 may transmit information at designated
time intervals, and the receiving section 150 may sequentially
receive this transmitted information. In this embodiment, the
receiving section 150 may receive car probe data from each mobile
object 10 as the information. The car probe data may include
information detected by the mobile object 10, such as position
information of the mobile object 10.
[0050] In one embodiment, the position information may include
longitude and latitude (and optionally altitude information) of the
mobile object 10 in an absolute coordinate system. In another
embodiment, the mobile object 10 may determine its location in the
absolute coordinate system by using GPS, and the determining
section 146 receiving the position information may determine a
route on which the mobile object 10 exists and a specific location
of the route at which the mobile object 10 exists based on the
position information. Alternatively, the mobile object 10 may
include such detailed position information in the car probe
data.
[0051] The receiving section 150 may communicate with the plurality
of mobile objects 10 and receive the car probe data of each mobile
object 10, via the Internet 40. The receiving section 150 may
receive the car probe data of the plurality of mobile objects 10
through wireless communication, a subscriber network, a cellular
network, or any desired combination of networks.
[0052] The transmitting section 152 may be operable to transmit
event information to each of the mobile objects 10 according to
settings, for example. The transmitting section 152 may transmit
information concerning the route on which the mobile object 10 is
expected to travel. The transmitting section 152 may communicate
with the mobile objects 10 and transmit each type of information to
the mobile objects 10 via the Internet 40. The transmitting section
152 may transmit each type of information to the mobile objects 10
through wireless communication, a subscriber network, a cellular
network, or any desired combination of networks.
[0053] The gateway apparatus 160 may be operable to transfer
communication between the plurality of subsystems 200 and the
plurality of mobile objects 10. The gateway apparatus 160 may
communicate with the receiving section 150 and receive the
information transmitted by each mobile object 10.
[0054] The gateway apparatus 160 may communicate with the region
manager 140 and demand the transfer destination for each piece of
information received from the mobile objects 10, of the region
manager 140. In response to this request, the gateway apparatus 160
may receive from the region manager 140 the information of the
subsystem 200 managing the region on which the mobile object 10
exists. The gateway apparatus 160 may transfer the information
received from the mobile object 10 to the subsystem 200 that is to
manage the mobile object 10. In other words, the gateway apparatus
160 may transfer the information received from each mobile object
10 to the subsystem 200 determined by the region manager 140.
[0055] The gateway apparatus 160 may communicate with each of the
subsystems 200, and receive the information transmitted by each
subsystem 200. The gateway apparatus 160 may communicate with the
transmitting section 152 and supply the transmitting section 152
with the information received from each subsystem 200, such that
this information is transferred to the mobile objects 10 designated
for each subsystem 200.
[0056] The gateway apparatus 160 may include a plurality of gateway
devices, and may quickly perform transfer between the plurality of
subsystems 200 and the plurality of mobile objects 10. In this
case, the receiving section 150 may function as a load balancer
that supplies the information from the mobile objects 10, such that
the load is spread among the plurality of gateways. The load
balancer may sequentially supply information from the mobile
objects 10 to the gateways having lighter loads. The gateway
apparatus 160 may be a network that provides a connection between a
plurality of networks using the same or different types of
protocols.
[0057] A plurality of subsystems 200 may be operable to communicate
with the region manager 140 and the gateway apparatus 160 and to
respectively manage a plurality of regions in a geographic space.
Each subsystem 200 is operable to manage mobile objects 10 that
travel routes in its managing region and to manage events on its
managing region.
[0058] As described, each subsystem 200 may include the event
server 210 and the mobile object server 220. The event server 210
manages events occurring on its managing region with the plurality
of the event agents. In one embodiment, the event server 210 may
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.
[0059] The mobile object server 220 manages the plurality of the
mobile objects 10 traveling on its managing region with the
plurality of the mobile object agents. In one embodiment, the
mobile object server 220 may 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
server 220 may execute the mobile object agent to collect
information of events from at least one event server 210, and
provide the mobile object 10 with information that assists the
mobile object 10 with traveling in the geographic space.
[0060] A plurality of object servers 230 including at least one
object server 230 may communicate with the gate way 160 and include
an object agent (OA) containing information of the mobile object
10. An object agent may correspond to each mobile object 10 and
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 object 10,
(ii) an identification (ID) of the mobile object 10, (iii) an ID of
a passenger of the mobile object 10, and (iv) a characteristic of
the mobile object 10 (e.g., model/version information, width,
length, and/or height of the mobile object 10).
[0061] The object server 230 may perform, through the object agent,
(i) provision and/or update of information of the mobile object 10,
(ii) registration, update, and/or deletion of the ID of passenger
riding on the mobile object 10, (iii) provision and/or update of
the information of the region of the mobile object 10, and (iv)
provision of information needed for generation of a new mobile
object agent by the mobile object server 220.
[0062] At least one passenger server 240 of a plurality of
passenger servers may communicate with the gateway apparatus 160,
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 objects 10, 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 server 240 may perform, through the
passenger agent, provision and/or update of information of the
passengers.
[0063] As described above, the system 100 of the present embodiment
may manage the mobile objects by utilizing the mobile object agents
in each mobile object server 220, and manage the events by
utilizing the event agent in each event server 210. According to
the system 100 of the embodiment, the system 100 can separately
manage information relating to the mobile objects 10 and events on
the geographic map with a plurality of kinds of servers.
Furthermore, the plurality of mobile object servers 220 can
smoothly transfer the management of the mobile objects 10 traveling
across the regions via the mobile object agents, thereby improving
the efficiency of the whole system 100. In addition, according to
the system 100 of the embodiment, each event server 210 divides
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 objects 10. In addition, the system 100
can provide the mobile object agent with information of mobile
object 10 by the object agent of the object server 230. The system
100 can also provide the mobile object agent with information of
passengers of the mobile objects 10 by the passenger agent of the
passenger server 240.
[0064] FIG. 4 shows management of events by the event server 210
and the mobile object server 220, according to an embodiment of the
present invention. In this embodiment, a mobile object 10 is
traveling on a target route on region A and transmitting a car
probe data including the position information to the event server
210 managing region A with the car probe data via a gateway
apparatus, such as the gateway apparatus 160. The event server 210
manages 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).
[0065] In the embodiment of FIG. 4, the event agent EA2 manages
events of an area (indicated as "DA2" on the region A of FIG. 4) by
the event list of the event agent EA2 and the candidate event list
of the event agent EA2 based on car probe data from the mobile
object 10 on the area DA2. For example, the event agent EA2
assigned to the area DA2 is executable to generate an event based
on the information from the mobile object 10.
[0066] In one embodiment, each mobile object server 220 is operable
to receive information from the mobile object 10 in the region A
assigned to the mobile object server 220. The mobile object server
220 determines the target route where the mobile object 10 is
located. The mobile object server 220 sends the information to one
event server 210 assigned to a region A where the mobile object 10
is located, and thereby requests the event agent EA2 assigned to
the area DA2 where 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.
[0067] The mobile object server 220 executes the mobile object
agent MOA1 for the mobile object 10 to provide the mobile object 10
with information that assists the mobile object 10 with traveling
in the area DA2 based on the information of the event on the other
route and the influence event of the target route. In the
embodiment of FIG. 4, the mobile object agent MOA1 receives, from
the event agent EA2, the event information of the route on which
the mobile object 10 exists, and provides the mobile object 10 with
the event information (e.g., information of closure).
[0068] FIG. 5 shows management of a mobile object 10 by the mobile
object servers 220 and object server 230, according to an
embodiment of the present invention. The mobile object server 220-1
may transfer the mobile object agent to the mobile object server
220-2 assigned to a neighboring region in response to the mobile
object 10 moving to the neighboring region. In this embodiment, in
response to a mobile object 10 traveling from region A to region B,
the mobile object server 220-1 managing region A deletes the mobile
object agent MOA for the mobile object 10, and a mobile object
server 220-2 managing region B generates a mobile object agent MOA
for the mobile object 10.
[0069] In this embodiment, the object agent 230 may store
information that includes a mobile object server identifier MOS-ID
that identifies one of the plurality of mobile object servers 220
executing the mobile object agent corresponding to the object agent
10. Just after the mobile object 10 arrives at region B, the mobile
object server 220-2 has not been executing the mobile object agent
for the mobile object 10. The mobile object server 220-2 is
operable to receive information from the mobile object 10 in the
region B assigned to the mobile object server 220-2.
[0070] Using the information from the mobile object 10, the mobile
object server 220-2 obtains the mobile object server identifier
MOS-ID from the object server 230 that manages the object agent for
the mobile object 10 because the mobile object server 220-2 is not
executing the mobile object agent for the mobile object 10. The
mobile object server 220-2 requests a mobile object server 220-1
identified by the mobile object server identifier MOS-ID to
transfer the mobile object agent for the mobile object 10. Then the
mobile object server 220-1 managing region A transfers the mobile
object agent to the mobile object server 220-2 assigned to a
neighboring region B in response to the request.
[0071] FIG. 6 shows an operational flow of a system, according to
an embodiment of the present invention. The present embodiment
describes an example in which the system 100 performs the
operations from S610 to S680 shown in FIG. 6 to manage mobile
objects, such as mobile object 10, and events on a map area. FIG. 6
shows one example of the operational flow of the system 100 shown
in FIGS. 1-5, but the system 100 shown in FIGS. 1-5 is not limited
to using this operational flows explained below. Also, the
operational flow in FIG. 6 may be performed by other systems.
[0072] First, an acquiring section, such as the acquiring section
110, 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 section
130, may divide the map area to generate a plurality of
regions.
[0073] Next, the system may perform an initialization process for
the mobile object (S620). The system may perform the process of
S620 if a user (passenger) initializes a setting of a mobile object
and any passengers of the mobile object, before starting to drive
the mobile object.
[0074] After S620, a gateway apparatus, such as the gateway
apparatus 160, 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.
[0075] 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 manager 140, about the region on
which the moving exists. A determining section, such as the
determining section 146, 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
server 210, that manages the determined region and a mobile object
server, such as the mobile object server 220, that manages the
determined region with the car probe data.
[0076] 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.
[0077] 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).
[0078] After S660, the system determines whether to end the process
for the target mobile object (S680). 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 S630 for 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.
[0079] 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.
[0080] The process of S610 may be performed once before starting
processes S620-S680. The process of S620-S680 may be performed for
every mobile object.
[0081] FIG. 7 shows 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 S620 of FIG. 6, through processes S621 to
S623 shown in FIG. 7.
[0082] 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.
[0083] 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.
[0084] 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.
[0085] Next, the mobile object server 220 managing the region in
which the mobile object 10 exists generates a new mobile object
agent for the mobile object 10 (S623). In one embodiment, the
mobile object server 220 may copy the information of the object
agent for the mobile object 10 to the newly generated mobile object
agent. For example, the mobile object server 220 may store the
information of the mobile object 10 and the information of the at
least one passenger of the mobile object 10 in the newly generated
mobile object agent for the mobile object 10.
[0086] FIG. 8 shows 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 S650 of FIG. 6, through
processes S651 to S659 shown in FIG. 8.
[0087] 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.
[0088] 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."
[0089] 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).
[0090] 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).
[0091] 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.
[0092] 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 S655 and if negative, the event
server proceeds with the process S656.
[0093] 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.
[0094] 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.
[0095] Next, the event server determines, by the target event
agent, whether the notification event ID list has at least one
entry (S657). 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.
[0096] 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."
[0097] 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.
[0098] FIG. 9 shows an illustrative example of an event list,
according to an embodiment of the present invention. As described
in FIG. 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 "Eve 0214") has occurred along the
full length of edge 0001 on the area, that the event has limited
the speed to 30 km/h, and that edge 0001 includes an influence
event identified as "Eve 0114." The event list also indicates that
an event (identified as "Eve 0114" on edge 0002) has occurred 32 m
from the 1st node on edge 0002 on the area, that the event is a
closure of a route, and that edge 0001 includes influence events
identified as "Eve 0214" on edge 0001, "Eve 0421" on edge 0003,
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.
[0099] According to the first entry in the event list of FIG. 9,
the edge 0001 has influence event Eve 0114. This may mean that a
mobile object traveling on the edge 0001 is influenced by the event
Eve 0114 that has occurred apart from edge 0001 within 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 edge 0001, the target event agent searches and
obtains routes (edge IDs) apart from the target route (edge 0001)
within the threshold distance, and then finds neighboring edge 0002
as a result. In response to receiving the car probe data including
the position information of the edge 0001, the target event agent
determines whether the edge of influence event (edge 0002)
corresponding to the target route is listed as edge IDs in the
event list.
[0100] 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.
[0101] Although the event list of FIG. 9 includes 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.
[0102] FIG. 10 shows an illustrative example of a candidate event
list, according to an embodiment of the present invention. As
described in FIG. 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 edge 0009 on the area, and that
evidence of an event (skid) has been observed once at a point 15 m
from the 2nd node on edge 0013 on the area.
[0103] 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.
[0104] FIG. 11 shows an illustrative example of a notification
event list, according to an embodiment of the present invention. As
described in FIG. 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 edge 0001 on the area, and that an event (closure)
has occurred at a point 32 m from the 1st node on edge 0002 on the
area.
[0105] FIG. 12 shows a mobile object and events, according to an
embodiment of the present invention. In the embodiment of FIG. 12,
the target mobile object 10 is traveling eastbound on the edge
0001, which is the target route. The target event agent EA1 manages
an area including the edge 0001, the edge 0002, the edge 0101, and
the edge 0102, and the neighboring event agent EA2 manages an area
including the edge 0003, the edge 0103, and the edge 0104.
[0106] Direction dependent edges are described in FIG. 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 EA1 manages an event (Eve 0214) on the edge
0001 as the target event in the event list. Since the edge 0002 is
apart from the edge 0001 within the threshold distance, the target
event agent EA1 also manages an event (Eve 0114) on the edge 0002
as an influence event in the event list. The target event agent EA1
manages a notification event list including the target event
(Eve0214) and the influence event (Eve 0114) for the target mobile
object 10.
[0107] In the embodiment of FIG. 12, the mobile object agent
managing target mobile object requests the event agent EA1 that
manages the target event (e.g., Eve 0214) and the influence event
(e.g., Eve 0114) 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 EA2 that
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 (Edge 0001).
[0108] FIG. 13 shows 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 S660 of FIG. 6,
through processes S661 to S669 shown in FIG. 13.
[0109] 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.
[0110] 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.
[0111] Next, at S663, the mobile object server may inquire the
object server 230 identified at S662 for 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.
[0112] 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.
[0113] 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 object 10 that has been not managed by the mobile object
server.
[0114] 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.
[0115] 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.
[0116] 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.
[0117] 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.
[0118] 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.
[0119] 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).
[0120] 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.
[0121] 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.
[0122] FIG. 14 shows an exemplary configuration of the system 100,
according to an embodiment of the present invention. In this
embodiment, each subsystem 200 includes an event server 210, mobile
object server 220, an object server 230, and a passenger server
240. However, other embodiments are also possible, in which each
subsystem 200 comprises any combination of singles or multiples of
each server. In other embodiments, the system 100 may manage
allocation of object agents of the object server 230 and passenger
agents of the passenger server 240 in the subsystem 200. For
example, the gateway apparatus 160 may change allocation of the
object/passenger agents to the subsystems 200 to rectify the
imbalance of data processing loads among the subsystems 200.
[0123] In the embodiment described above, the event server 210 may
manage allocated event agents. In other embodiments, the system 100
may manage allocation of event agents to the event servers 210. For
example, the gateway apparatus 160 may change allocation of event
agents to the event servers 210 to rectify the imbalance of loads
of processing events among the event servers 210. In the embodiment
described above, the event server 210 causes each event agent to
manage allocated divided area derived from a region. In other
embodiment, the event server 210 causes 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).
[0124] FIG. 15 shows an exemplary configuration of the system 100
according to another embodiment. In the system 100 according to the
present embodiment, components having substantially the same
operation as components in the system 100 shown in FIG. 3 and FIG.
14 are given the same reference numerals, and descriptions thereof
are omitted.
[0125] In the present exemplary configuration, the mobile object 10
may include one or more sensors 11 for detecting an event/candidate
event. For example, the mobile object 10 may include, as the sensor
11, an image sensor for identifying road signs, obstacles, and the
like and/or LIDAR (Light Detection and Ranging, Laser Imaging
Detection and Ranging) for identifying obstacles. In addition to or
instead of this, the mobile object 10 may include a sound sensor
for detecting damage to the mobile object 10 and/or abnormalities
in the engine noise as the sensor 11. The mobile object 10 may
include sensors 11 independently for each sensing region, and may
include sensors 11 respectively facing forward and to the right,
forward and to the left, straight forward, and straight
backward.
[0126] In the present exemplary configuration, the system 100 may
further include a mobile object database 2300 and a rule setting
section 170.
[0127] The mobile object database 2300 may store the reliability
with which each of a plurality of mobile objects 10 moving in a
geographic space detects an event (referred to as the detection
reliability). For example, the mobile object database 2300 may
store the detection reliability of each mobile object 10 in
association with each of the plurality of mobile objects 10.
Furthermore, the mobile object database 2300 may store the
detection reliability of each mobile object 10 in association with
each of the one or more sensors 11 of the mobile object 10. Here,
the event detection reliability is the certainty of the detection
result of an event by the mobile object 10. As an example, in the
present exemplary configuration, the detection reliability may be a
value in a range from 0.9 to 1.1, where a higher value indicates
greater reliability. The detection reliability may be updated
according to the process flow described further below. The initial
value of the detection reliability may be set arbitrarily from the
type, model, model year, and the like of the mobile object 10
and/or the sensor 11 of the mobile object 10, and may be set to be
1.0.
[0128] The mobile object database 2300 may store statistical
information of detection results of events/candidate events by the
plurality of mobile objects 10. For example, the statistical
information may be information obtained by acquiring statistics for
each of the type, model, model year, total distance traveled, and
driver of the mobile objects 10, or at least one combination of
these categories, for the correctness of a plurality of detection
results by the plurality of mobile objects 10. Here, the
correctness may be the ratio of correct detection results, and may
be a ratio with which events registered in an event list are
detected or a ratio with which an event that is moved from the
event list to the candidate event list is not detected. Acquiring
statistics for each type of mobile object 10 is performed because
it is possible for a difference to occur in the identification rate
of events, and therefore the correctness, due to the shape or the
like of the mobile object 10. Acquiring statistics for each model
year and/or the total distance traveled is performed because it is
possible for a difference to occur in the correctness due to the
degradation caused by aging. Acquiring statistics for each driver
is performed because it is possible for a difference to occur in
the correctness due to the differences in the angle of the sensor
11 relative to an event, the length of time during which the event
can be detected, and the like as a result of the drivers having
different driving styles, e.g. turning at high speed at
intersections, driving close to other automobiles, and the like.
Furthermore, these statistics are also acquired because it is
possible for a difference to occur in the correctness due to the
path normally traveled, the frequency of car washing (in other
words, the ratio of the outer surface of the sensor 11 being
clear), and/or the like being different. The statistical
information may be information obtained by acquiring statistics for
at least one of each sensor, each sensing region, and each
detection rule of the mobile objects 10, in addition to or instead
of the information described above.
[0129] The mobile object database 2300 may be connected to the
object server 230. The information in the mobile object database
2300 may be updated by the object server 230.
[0130] The rule setting section 170 may set a detection rule for
detecting one event/candidate event, for at least one mobile object
10. Here, the detection rule may at least designate the
event/candidate event to be detected by the mobile object 10. The
rule setting section 170 may supply at least one mobile object 10
with the set detection rule, via the gateway apparatus 160.
[0131] Here, in the present exemplary configuration, the acquiring
section 110 may acquire a dynamic map from the database 30. The
dynamic map may be a high-definition digital geographic map that
incorporates not only information concerning geographic objects,
but also event information that changes over time, such as
accidents, traffic jams, and construction regulations. The dynamic
map may be provided to each mobile object 10 from the transmitting
section 152.
[0132] The receiving section 150 may receive car probe data that
includes the information concerning the event/candidate event
detected in the geographic space by one mobile object 10 among the
plurality of mobile objects 10, from this one mobile object 10. The
received event/candidate event information may be supplied to the
event server 210 corresponding to the region in which this one
mobile object 10 is located, by the gateway apparatus 160. The
receiving section 150 may receive probe data relating to each
detected event from two or more mobile objects 10.
[0133] If the event/candidate event information detected by one
mobile object 10 is received, the event server 210 may judge the
reliability of this one event (referred to as event reliability)
based on the detection reliability associated with the one mobile
object 10 in the mobile object database 2300. The event server 210
may register/update the information concerning the one
event/candidate event and the group including the event reliability
thereof, for the event list/candidate event list, using the target
event agent. Here, the event reliability is the certainty of the
event occurring. As an example, in the present exemplary
configuration, the event reliability may be a value in a range from
0.9 to 1.1, where a higher value indicates greater reliability.
Furthermore, in the present exemplary configuration, the event and
the candidate event may be classified according to the event
reliability, and the candidate event may be an event whose event
reliability is less than a threshold value, e.g. 1.0.
[0134] The mobile object server 220 may be operable to assist with
the movement of the plurality of mobile objects 10 in the
geographic space. For example, if the travel route of the mobile
object 10 is confirmed, e.g. if the travel route is provided to the
mobile object 10 via car navigation or the like, the mobile object
server 220 may provide this mobile object 10 with the event
information occurring on this route. Furthermore, if the travel
route of the mobile object 10 is not confirmed, the mobile object
server 220 may calculate one or more routes (Most Probable Paths
(MPP)) that are most likely to be traveled in the future by mobile
objects 10 that are currently travelling and provide this mobile
object 10 with the event information occurring on these routes.
[0135] With the system 100 described above, the event reliability
of one event detected by one mobile object 10 is judged based on
the detection reliability associated with the one mobile object 10.
Accordingly, it is possible to provide the reliability of the
detected event. Furthermore, since the event reliability is judged
based on the detection reliability associated with the sensor 11
that detected the one event, it is possible to provide event
reliability with higher accuracy.
[0136] FIG. 16 shows a process flow of the system 100 according to
the present embodiment. The system 100 according to the present
embodiment judges the event reliability by performing this
operational flow.
[0137] First, in S641, the mobile object server 220 may calculate
the MPP of one mobile object 10. For example, the mobile object
server 220 may calculate the MPP using, in addition to the current
travel history of the one mobile object 10, at least one of pattern
matching that utilizes the travel history up to the most recent
travel history for the one mobile object 10, the travel state of
another mobile object 10 at the current time point, and the current
time range, day of the week, and the like. The mobile object server
220 may calculate the MPP by performing deep learning. If the
travel route of the mobile object 10 is confirmed, the mobile
object server 220 may set this travel route to be the MPP.
[0138] Next, in S642, the rule setting section 170 may issue
instructions for the deletion of information of one or more target
objects to be set as detection targets, from the map information of
the geographic space possessed by the one mobile object 10. For
example, the rule setting section 170 may issue instructions for
the deletion of the information of the target object from a map
portion along the MPP, in the map provided to the one mobile object
10 from the transmitting section 152. The target object may be a
road accessory or a known event/candidate event that is already
registered in the event/candidate event list. The event/candidate
event may be a traffic jam, a speed limit, road construction, an
obstacle, a fire near the road, or the like. The road accessory may
be installations or works necessary for maintaining the road
structure, ensuring safe and smooth commuting on the road, and road
management, and may be a fence, pole, street sign, mirror, street
lamp, geographic point mark, road sign or the like on the road. The
process of S642 does not need to be performed.
[0139] Next, in S643, the rule setting section 170 may set the
detection rule for detecting the one detection target, for the one
mobile object 10. The detection target may be a known
event/candidate event, or may be an unknown event that has yet to
be registered in the event list/candidate event list. The detection
target may be a target object deleted from the map by the process
of S642. In this case, since the map information differs from the
state of the road identified by the sensor 11 of the mobile object
10, it becomes more difficult to detect the detection target. If
the process of S642 is not performed, the detection target may be a
road accessory (e.g. a traffic signal or the like scheduled to be
newly installed) that is present on the map. The detection target
may be on the MPP. In this way, it is possible to remove the burden
of setting the detection target on roads that have a low
probability of being traveled.
[0140] The detection rule may further include a position on the map
at which detection is to be performed. As an example, in the
present embodiment, this position may be on the MPP. In addition to
this, the detection rule may further include a relative position of
the detection target (e.g. forward and to the right or the like)
for the mobile object 10 located at this position. The detection
rule may further include environment conditions of a case in which
the detection is to be performed by applying this rule, e.g. the
brightness of the surrounding area or the like. The rule setting
section 170 may set, as a usage target, any one detection rule from
among a plurality of detection rules stored in advance.
[0141] The rule setting section 170 may set the difficulty of the
detection in association with the detection rule. In this way, in
S646 described further below, it is possible to improve the
efficiency when updating the detection reliability according to the
detection result. For example, the rule setting section 170 may set
the difficulty of the detection associated with the detection rule
based on the statistical information of the detection results of
the detection target by one or more mobile objects 10. As an
example, the rule setting section 170 may set a low difficulty if
the correctness corresponding to one mobile object 10 in the
statistical information is greater than or equal to a first
reference correctness (e.g. 95%), and may set a high difficulty if
this correctness is less than a second reference correctness (e.g.
80%).
[0142] The processes from S641 to S643 described above may be
performed between S620 and S630 in FIG. 6. If the system 100 judges
that the process is not to be ended in S680 in FIG. 6, the system
100 may move to the process of S641.
[0143] Here, when the detection rule is set for the one mobile
object 10 according to S643, this one mobile object 10 may attempt
to detect the detection target according to this detection rule.
The one mobile object 10 may transmit the detection result to the
receiving section 150. The one mobile object 10 may include, in the
detection result, an ID of this one mobile object 10 and/or an ID
of the sensor 11 that performed the detection. If the detection
target is not detected when the one mobile object 10 passes through
the position on the map where the detection target is to be
detected, the one mobile object 10 may transmit notification of
this fact, or does not need to transmit the detection result. If a
road accessory that was deleted from the map by the process of S642
and designated as a detection target by the process of S643 is
detected, in the present embodiment, as an example, the mobile
object 10 may transmit a detection result indicating that the
detection target was detected, or may transmit the detection result
indicating that an event/candidate event for the occurrence of an
obstacle (the road accessory in this case) was detected. The mobile
object 10 for which the detection rule is set may perform detection
of events that are not already set as detection targets by this
detection rule in parallel.
[0144] Next, in S644, the receiving section 150 may receive
information concerning the detection target detected by the one
mobile object 10. The receiving section 150 may supply the event
server 210 with the received information via the gateway apparatus
160.
[0145] The receiving section 150 may change the reception frequency
of the detection result from the one mobile object 10, according to
the detection reliability of the one mobile object 10. For example,
the receiving section 150 may set the reception frequency to be
high in advance if the detection reliability is higher than a
reference reliability (e.g. 1.05). The process of S644 may be the
process of S630 in FIG. 6.
[0146] Next, in S645, if an event is designated in the detection
rule, the event server 210 may judge the event reliability of the
corresponding event/candidate event according to the detection
result. Instead of or in addition to this, if an event/candidate
event that is not designated in the detection rule is detected by
the mobile object 10, the event server 210 may judge the event
reliability of the corresponding event/candidate event. The
judgement concerning the event reliability may be performed by the
target event agent corresponding to the position of the one mobile
object 10.
[0147] The event server 210 may judge the event reliability based
on the detection reliability of the one mobile object 10. The event
server 210 may judge the event reliability of the detected
event/candidate event based on the detection reliability associated
with the one sensor 11 that detected the event/candidate event
among the one or more sensors 11 of the one mobile object 10.
[0148] For example, using the ID of the one mobile object 10 or the
ID of the one sensor 11 included in the detection result as a key,
the event server 210 may read the detection reliability of this one
mobile object 10 or one sensor 11 that detected the event/candidate
event from the mobile object database 2300.
[0149] If a detection result indicating detection of an unknown
event/candidate event is received, the event server 210 may judge
the detection reliability of the one mobile object 10 or the one
sensor 11 that detected the event/candidate event to be the event
reliability as-is. As an example, if the detection reliability is
1.1, the event server 210 may judge the event reliability to be
1.1. Instead of this, the event server 210 may judge the event
reliability to be a lowest value of 0.9 if the detection
reliability of the one mobile object 10 is less than a reference
value (e.g. 0.95), and judge the event reliability to be a highest
value of 1.1 if the detection reliability is greater than or equal
to the reference value.
[0150] If a detection result indicating that an unknown
event/candidate event was not detected is received, e.g. if an
unknown event designated by the detection rule is not detected, the
event server 210 may judge the event reliability to be the lowest
value of 0.9.
[0151] If a plurality of detection results for one event/candidate
event are received from two or more mobile objects 10, the event
server 210 may judge the event reliability of the one
event/candidate event based on the detection reliability associated
with each of these mobile objects 10 (or each sensor 11).
[0152] Here, a case in which a plurality of detection results are
received for one event/candidate event may be a case in which two
or more mobile objects 10 each detect a respective one
event/candidate event, a case in which only some of the two or more
mobile objects 10 detect the one event/candidate event, and/or a
case in which none of the two or more mobile objects 10 detect the
one event/candidate event. While the event server 210 is judging
the event reliability in response to receiving a plurality of
detection results, the one event/candidate event may be known or
may remain unknown, or may transition from being unknown to being
known. An example of a case in which the one event/candidate event
remains unknown includes a case in which detection results from a
plurality of mobile objects 10 are received continuously in a short
time for an unknown event/candidate event, for example.
[0153] In such a case, the event server 210 may once again judge
the event reliability based on the detection reliability of the
mobile object 10/sensor 11 corresponding to the ID included in the
most recent detection result for this event/candidate event and on
each detection reliability of the mobile object 10/sensor 11
corresponding to the IDs included in one or more previous detection
results (e.g. each detection reliability stored in the event
list/candidate event list).
[0154] For example, in a case where the plurality of detection
results are each a detection result indicating affirmative
detection, the event server 210 may judge the event reliability to
be the highest value of 1.1 if the event/candidate event is
detected by at least a first reference number (e.g. 2) of the
mobile objects 10 and the detection reliability of each mobile
object 10 is greater than or equal to a first reference threshold
value (e.g. 1.05). Furthermore, the event server 210 may judge the
event reliability to be the highest value of 1.1 if the
event/candidate event is detected by at least a second reference
number (e.g. 10), which is greater than the first reference number,
of the mobile objects 10 and the detection reliability of each
mobile object 10 is greater than or equal to a second reference
threshold value (e.g. 1.00), which is less than the first reference
threshold value. The event server 210 may judge the highest value,
the lowest value, or the average value among the detection
reliabilities to be the new event reliability.
[0155] If the plurality of detection results are each a detection
result indicating that there was no detection, the event server 210
may judge the event reliability to be the lowest value of 0.9.
[0156] If some of the plurality of detection results are detection
results indicating affirmative detection and others are detection
results indicating that there was no detection, the event server
210 may judge the highest value, the lowest value, or the average
value among the detection reliabilities to be the new event
reliability.
[0157] The event server 210 may judge the event reliability further
based on at least one of the behavior state of the one mobile
object 10 and the environment at the location of the one mobile
object 10. For example, if there is a possibility of the
performance of the sensor 11 dropping because of the behavior state
and/or environment of the mobile object 10, the event server 210
may judge the event reliability using a detection reliability that
has been reduced by a prescribed value. In this way, it is possible
to judge the event reliability with higher accuracy. Such a
behavior state may be a state in which the mobile object travels at
a speed greater than or equal to a reference speed, travels on a
bumpy road, travels on a curb, makes a turn, or the like.
Furthermore, such an environment may be an environment in which the
travel speed of a nearby mobile object 10 is greater than or equal
to a reference speed, an environment in which the illumination is
less than a reference illumination, a rainy environment, or the
like, for example.
[0158] The process of S645 described above may be performed between
the processes of S651 and S652 in FIG. 8.
[0159] Next, in S646, the event server 210 and the mobile object
server 220 perform the process corresponding to the detection
result of the event/event candidate by the one mobile object
10.
[0160] The event server 210 may update the event list/candidate
event list.
[0161] For example, the event server 210 may register the event and
the candidate event in a list based on the event reliability. As an
example, if an unregistered event is detected, the event server 210
may register an event whose event reliability has been judged to be
greater than or equal to a threshold value (e.g. 1.05) in the event
list, and may register an event whose event reliability has been
judged to be less than the threshold value as a candidate event in
the candidate event list. The event server 210 may register the
detection reliability of the mobile object 10/sensor 11 that made
the detection in the list in association with the event/candidate
event.
[0162] If the judgment is made for an event/candidate event that
has already been registered, the event server 210 may add the
detection reliability of the mobile object 10/sensor 11
corresponding to the ID included in the detection result to the
list. If an event is detected and the event reliability of this
event is judged to be less than the threshold value, the event
server 210 may downgrade this event to being a candidate event,
register this event in the candidate event list, and delete this
event from the event list. If a registered candidate event is
detected and the event reliability thereof is judged to be greater
than or equal to the threshold value, the event server 210 may
upgrade this candidate event to an event, register this event in
the event list, and delete this event from the candidate event
list. A hysteresis may be created in which the threshold value for
downgrading an event and the threshold value for upgrading a
candidate event are different values. The registration of an
event/candidate event in a list and the deletion of an
event/candidate event from a list may be performed by the event
agent corresponding to the position of this event/candidate
event.
[0163] The event server 210 may update the map acquired by the
acquiring section 110 and provided to the mobile object 10,
according to the detection result. For example, if a new event is
registered in the event list, the event server 210 may add this
event to the map. If an event is deleted from the event list, the
event server 210 may delete this event from the map. The addition
of an event to the map and the deletion of an event from the map
may be performed by the event agent corresponding to the position
of this event.
[0164] The mobile object server 220 may perform a process relating
to a plurality of mobile objects 10 with the assumption that an
event exists, on a condition that the event reliability is greater
than or equal to a reference reliability. For example, the mobile
object server 220 may notify one or more mobile objects 10
differing from the one mobile object 10 about the existence of one
event using the corresponding mobile object agent, on a condition
that the event reliability of the one event is greater than or
equal to the reference reliability (e.g. 1.05). The other mobile
objects 10 may be automobiles following after the one mobile object
10. In this way, the other mobile objects 10 can avoid the one
event. The mobile object server 220 may search for a movement route
of another mobile object 10 with the assumption that the one event
exists using the mobile object agent for the other mobile object
10, on a condition that the event reliability of the one event is
greater than or equal to the reference reliability. As an example,
if the event is detected on the MPP of the other mobile object 10,
the mobile object server 220 may search for a movement route that
avoids this event and provide this other mobile object 10 with this
movement route. In this case, the mobile object server 220 may
search for a movement route with the assumption that the one event
exists.
[0165] The process of S646 described above may be performed in S669
in FIG. 13.
[0166] Next, in S647, the object server 230 may update the
detection reliability of the one mobile object 10 in the mobile
object database 2300, based on the detection result of one
detection target by the one mobile object 10, using the object
agent. For example, the object server 230 may update the detection
reliability of the one mobile object 10 based on whether the one
mobile object 10 has detected the presence of a detection target
that is a target object deleted from the map information by the
process of S642. The object server 230 may increase the detection
reliability if the target object is detected, and may decrease the
detection reliability if the target object is not detected. The
object server 230 may cause the increase amount of the detection
reliability to be greater if the detection target is deleted from
the map information than if the detection target is not
deleted.
[0167] If the difficulty of the detection is associated with the
detection rule, the object server 230 may change the update amount
of the detection reliability of the one mobile object 10 based on
this difficulty. For example, the object server 230 may cause the
increase amount used when there is affirmative detection to be
greater when the difficulty is greater, and may cause the decrease
amount used when there is no detection to be greater when the
difficulty is lower. If the detection target designated by a
detection rule with a difficulty lower than a reference value is
not detected by the one mobile object 10, the object server 230 may
judge that the sensor 11 of the one mobile object 10 is damaged,
and set the detection reliability to the lowest value. In this
case, the object server 230 may provide the information concerning
the sensor 11 judged to be damaged to the one mobile object 10 from
the mobile object server 220 corresponding to this one mobile
object 10.
[0168] Next, in S648, the object server 230 may perform an update
by adding the detection result from the one mobile object 10 and
newly generating statistical information in the mobile object
database 2300, using the object agent.
[0169] The processes of steps S647 and S648 may be performed
between S660 and S680 in FIG. 6. The process of S648 may be
performed before the process of S647.
[0170] With the operational flow described above, the processes
relating to a plurality of mobile objects 10 (e.g. notification
about the presence of an event or searching for a movement route)
are performed with the assumption that the event exists, on a
condition that the event reliability of the (candidate) event
detected in S646 is greater than or equal to a reference
reliability. Accordingly, if the event reliability is high, the
process relating to the unknown (candidate) event can be performed
immediately for other mobile objects 10. Accordingly, unlike a case
in which the candidate event is upgraded to an event based on the
number of detections, it is possible to quickly provide other
mobile objects 10 with the information of the unknown event.
[0171] Furthermore, in S647, the detection reliability of the
mobile object 10 in the mobile object database 2300 is updated
based on the detection result of the event by the mobile object 10,
and therefore it is possible to maintain the value of the detection
reliability at a value corresponding to the actual detection
accuracy.
[0172] If a detection target that is a target object that has been
deleted from the map information is detected, the detection
reliability of the mobile object 10 is increased in S647, and
therefore the difficulty of the detection is increased and it is
possible to bring the value of the detection reliability closer to
the actual detection accuracy.
[0173] Furthermore, since the detection rule is set, it is possible
to dynamically test the detection reliability. Yet further, since
the update amount of the detection reliability is changed based on
the difficulty of the detection associated with the detection rule,
it is possible to bring the value of the detection reliability
closer to a value corresponding to the actual detection
accuracy.
[0174] Since the detection reliability is updated using the
detection result, it is possible to eliminate the effort of
calculating and setting a strict detection reliability from
detailed data such as the model and type of the sensor 11 mounted
in the mobile object 10. Furthermore, since it is possible to
perform a diagnostic examination of the detection reliability in
real time, it is possible to detect damage and degradation due to
aging of the sensor 11.
[0175] Since the reception frequency of the detection result by the
one mobile object 10 is changed according to the detection
reliability of the one mobile object 10, it is possible to
prioritize the reception of detection results by a mobile object 10
with high detection reliability over the reception of detection
results by a mobile object 10 with low detection reliability.
Accordingly, it is possible to quickly provide other mobile objects
10 with information concerning an event having high event
reliability.
[0176] FIG. 17 shows an exemplary candidate event list in the
present embodiment. The candidate event list in the present
embodiment may include reliability of an event in association with
edge IDs of candidate events, counts of detecting candidate events,
locations of candidate events, specific contents of candidate
events for each candidate event, and the like.
[0177] FIG. 18 shows an exemplary detection rule. This detection
rule designates a target object in a geographic space as the
detection target. For example, in this detection rule, there is one
target object (see Portion (I)) designated as existing within a
range of 50 m from a mobile object 10 at a position with a latitude
of 49 degrees 19 minutes and a longitude of 12 degrees 393 minutes
(see Portion (IV)). Furthermore, this detection rule designates
that the target object is positioned forward and to the right of
the mobile object 10 (see Portion (II)), and that a color (e.g.
orange) is shown in the range of #FF8800-FF88FF (see Portion
(III)). This detection rule further includes a numerical value
(e.g. 100 lux) for the environment illumination in a case where
detection is to be performed.
[0178] FIG. 19 shows exemplary data of the detection result. This
data may show that one pole with a length of 20 cm existing in a
range of 3 to 4 meters from the mobile object 10 has been detected.
The "Length Affected" in the drawing may be a distance at which
attention must be paid to the detection target, and may be a
required separation distance from the detection target, for
example.
[0179] FIG. 20 shows a detection target object designated by the
detection rule of FIG. 18. In the drawing, the circle symbols
indicate the poles as road accessories, and the hashed regions
indicate sensing regions of the one or more sensors 11 of the
mobile object 10. Here, in the present embodiment, the sensing
region includes regions forward and to the right, straight forward,
and straight backward from the mobile object 10. Furthermore, the X
mark in the drawing indicates the detection target designated by
the detection rule. In the present embodiment, as an example, the
detection target is an orange-colored pole. The pole that is the
detection target may be deleted in advance from the map information
of the mobile object 10 in the process of S642.
[0180] If the mobile object 10 detects the detection target, the
mobile object 10 may transmit a detection result indicating the
detection of the detection target, or may transmit a detection
result indicating the detection of an event/candidate event that
causes an obstacle. The mobile object 10 may also transmit this
detection result if an unknown event that is not designated by the
detection rule (e.g. an event of an obstacle being present forward
and to the right) is detected. If the mobile object 10 detects the
detection target of an event differing from the detection target,
the reliability of this event may be judged in the process of S645.
If the event reliability is greater than or equal to a reference
reliability (e.g. 1.05), in the process of S646, notification of
the existence of this event may be provided to other mobile objects
10 (e.g. a plurality of mobile objects 10 in the top portion of the
drawing).
[0181] If the mobile object 10 does not detect the detection
target, in the process of S647, the detection reliability of the
mobile object 10 or the sensor 11 facing forward and to the right
may be reduced.
[0182] FIG. 21 shows exemplary statistical information stored in
the mobile object database 2300. This statistical information
indicates the correctness for each combination of a type, a model,
a sensing region, and a detection rule of the mobile object 10.
With this statistical information, if a mobile object 10 whose type
is "A" and model is "model 001" performs detection using a
detection rule "B" (e.g. the detection rule shown in FIG. 18) in
the sensing region "forward and to the right," the correctness is
90%. In S643, based on this correctness, the difficulty may be set
for a case in which the mobile object 10 whose type is "A" and
model is "model 001" performs detection using a detection rule "B"
in the sensing region "forward and to the right."
[0183] FIG. 22 shows another example of statistical information
stored in the mobile object database 2300. This statistical
information indicates the correctness for each combination of a
driver, a sensing region, and a detection rule. With this
statistical information, if the mobile object 10 driven by the
driver "John Smith" performs detection using a detection rule "B"
(e.g. the detection rule shown in FIG. 18) in the sensing region
"forward and to the right," the correctness is 83%.
[0184] In the present embodiment above, an example is described in
which the system 100 includes the rule setting section 170, but the
rule setting section 170 may be included in the event server 210 or
the object server 230 instead. Furthermore, the rule setting
section 170 is described as deleting the information concerning the
target object from the map information in the process of S642, but
the process of S642 does not need to be performed. In addition to
this, the rule setting section 170 is described as setting the
detection rule in the process of S643, but the process of S643 does
not need to be performed. In this case, the mobile object 10 may
detect a known and/or unknown event/candidate event. Furthermore,
the system 100 does not need to include the rule setting section
170.
[0185] In the above description, the information concerning an
event with low event reliability among the events detected by the
mobile object 10 is registered in the candidate event list as a
candidate event, but such an event may be deleted without being
registered. For example, the event server 210 may register the
information concerning an event whose event reliability is greater
than or equal to a threshold value (e.g. 0.95), and delete the
information concerning an event whose event reliability is less
than the threshold value without registering this event.
[0186] FIG. 23 shows an exemplary hardware configuration of a
computer configured to perform the foregoing operations, according
to an embodiment of the present invention. A program that is
installed in the computer 700 can cause the computer 700 to
function as or perform operations associated with apparatuses of
the embodiments of the present invention or one or more sections
(including modules, components, elements, etc.) thereof, and/or
cause the computer 700 to perform processes of the embodiments of
the present invention or steps thereof. Such a program may be
executed by the CPU 2000 to cause the computer 700 to perform
certain operations associated with some or all of the blocks of
flowcharts and block diagrams described herein.
[0187] The computer 700 according to the present embodiment
includes a CPU 2000, a RAM 2020, a graphics controller 2075, and a
display device 2080, which are mutually connected by a host
controller 2082. The computer 700 also includes input/output units
such as a communication interface 2030, a hard disk drive 2040, a
DVD-ROM drive 2060 and an IC card drive, which are connected to the
host controller 2082 via an input/output controller 2084. The
computer also includes legacy input/output units such as a ROM 2010
and a keyboard 2050, which are connected to the input/output
controller 2084 through an input/output chip 2070.
[0188] The CPU 2000 operates according to programs stored in the
ROM 2010 and the RAM 2020, thereby controlling each unit. The
graphics controller 2075 obtains image data generated by the CPU
2000 on a frame buffer or the like provided in the RAM 2020 or in
itself, and causes the image data to be displayed on the display
device 2080.
[0189] The communication interface 2030 communicates with other
electronic devices via a network 2035. The hard disk drive 2040
stores programs and data used by the CPU 2000 within the computer
700. The DVD-ROM drive 2060 reads the programs or the data from the
DVD-ROM 2095, and provides the hard disk drive 2040 with the
programs or the data via the RAM 2020. The IC card drive reads
programs and data from an IC card, and/or writes programs and data
into the IC card.
[0190] The ROM 2010 stores therein a boot program or the like
executed by the computer 700 at the time of activation, and/or a
program depending on the hardware of the computer 700. The
input/output chip 2070 may also 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 controller 2084.
[0191] A program is provided by computer readable media such as the
DVD-ROM 2095 or the IC card. The program is read from the computer
readable media, installed into the hard disk drive 2040, RAM 2020,
or ROM 2010, which are also examples of computer readable media,
and executed by the CPU 2000. The information processing described
in these programs is read into the computer 700, resulting in
cooperation between a program and the above-mentioned various types
of hardware resources. An apparatus or method may be constituted by
realizing the operation or processing of information in accordance
with the usage of the computer 700. For example, when communication
is performed between the computer 700 and an external device, the
CPU 2000 may execute a communication program loaded onto the RAM
2020 to instruct communication processing to the communication
interface 2030, based on the processing described in the
communication program. The communication interface 2030, under
control of the CPU 2000, reads transmission data stored on a
transmission buffering region provided in a recording medium such
as the RAM 2020, the hard disk drive 2040, the DVD-ROM 2095, or the
IC card, and transmits the read transmission data to network 2035
or writes reception data received from network 2035 to a reception
buffering region or the like provided on the recording medium.
[0192] In addition, the CPU 2000 may cause all or a necessary
portion of a file or a database to be read into the RAM 2020, the
file or the database having been stored in an external recording
medium such as the hard disk drive 2040, the DVD-ROM drive 2060
(DVD-ROM 2095), the IC card, etc., and perform various types of
processing on the data on the RAM 2020. The CPU 2000 may then write
back the processed data to the external recording medium.
[0193] Various types of information, such as various types of
programs, data, tables, and databases, may be stored in the
recording medium to undergo information processing. The CPU 2000
may perform various types of processing on the data read from the
RAM 2020, which includes various types of operations, processing of
information, condition judging, conditional branch, unconditional
branch, search/replace of information, etc., as described
throughout this disclosure and designated by an instruction
sequence of programs, and writes the result back to the RAM 2020.
In addition, the CPU 2000 may 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 the recording medium, the CPU 2000 may
search for an entry matching the condition whose attribute value of
the first attribute is designated, from among the plurality of
entries, 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.
[0194] The above-explained program or software modules may be
stored in the computer readable media on or near the computer 700.
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 the computer readable media,
thereby providing the program to the computer 700 via the
network.
[0195] The present invention may be a system, a method, and/or a
computer program product. The computer program product may include
a computer readable storage medium (or media) having computer
readable program instructions thereon for causing a processor to
carry out aspects of the present invention.
[0196] The computer readable storage medium can be a tangible
device that can retain and store instructions for use by an
instruction execution device. The computer readable storage medium
may be, for example, but is not limited to, an electronic storage
device, a magnetic storage device, an optical storage device, an
electromagnetic storage device, a semiconductor storage device, or
any suitable combination of the foregoing. A non-exhaustive list of
more specific examples of the computer readable storage medium
includes the following: a portable computer diskette, a hard disk,
a random access memory (RAM), a read-only memory (ROM), an erasable
programmable read-only memory (EPROM or Flash memory), a static
random access memory (SRAM), a portable compact disc read-only
memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a
floppy disk, a mechanically encoded device such as punch-cards or
raised structures in a groove having instructions recorded thereon,
and any suitable combination of the foregoing. A computer readable
storage medium, as used herein, is not to be construed as being
transitory signals per se, such as radio waves or other freely
propagating electromagnetic waves, electromagnetic waves
propagating through a waveguide or other transmission media (e.g.,
light pulses passing through a fiber-optic cable), or electrical
signals transmitted through a wire.
[0197] Computer readable program instructions described herein can
be downloaded to respective computing/processing devices from a
computer readable storage medium or to an external computer or
external storage device via a network, for example, the Internet, a
local area network, a wide area network and/or a wireless network.
The network may comprise copper transmission cables, optical
transmission fibers, wireless transmission, routers, firewalls,
switches, gateway computers and/or edge servers. A network adapter
card or network interface in each computing/processing device
receives computer readable program instructions from the network
and forwards the computer readable program instructions for storage
in a computer readable storage medium within the respective
computing/processing device.
[0198] Computer readable program instructions for carrying out
operations of the present invention may be assembler instructions,
instruction-set-architecture (ISA) instructions, machine
instructions, machine dependent instructions, microcode, firmware
instructions, state-setting data, or either source code or object
code written in any combination of one or more programming
languages, including an object oriented programming language such
as Smalltalk, C++ or the like, and conventional procedural
programming languages, such as the "C" programming language or
similar programming languages. The computer readable program
instructions may execute entirely on the user's computer, partly on
the user's computer, as a stand-alone software package, partly on
the user's computer and partly on a remote computer or entirely on
the remote computer or server. In the latter scenario, the remote
computer may be connected to the user's computer through any type
of network, including a local area network (LAN) or a wide area
network (WAN), or the connection may be made to an external
computer (for example, through the Internet using an Internet
Service Provider). In some embodiments, electronic circuitry
including, for example, programmable logic circuitry,
field-programmable gate arrays (FPGA), or programmable logic arrays
(PLA) may execute the computer readable program instructions by
utilizing state information of the computer readable program
instructions to individualize the electronic circuitry, in order to
perform aspects of the present invention.
[0199] Aspects of the present invention are described herein with
reference to flowchart illustrations and/or block diagrams of
methods, apparatus (systems), and computer program products
according to embodiments of the invention. It will be understood
that each block of the flowchart illustrations and/or block
diagrams, and combinations of blocks in the flowchart illustrations
and/or block diagrams, can be implemented by computer readable
program instructions.
[0200] These computer readable program instructions may be provided
to a processor of a general purpose computer, special purpose
computer, or other programmable data processing apparatus to
produce a machine, such that the instructions, which execute via
the processor of the computer or other programmable data processing
apparatus, create means for implementing the functions/acts
specified in the flowchart and/or block diagram block or blocks.
These computer readable program instructions may also be stored in
a computer readable storage medium that can direct a computer, a
programmable data processing apparatus, and/or other devices to
function in a particular manner, such that the computer readable
storage medium having instructions stored therein comprises an
article of manufacture including instructions which implement
aspects of the function/act specified in the flowchart and/or block
diagram block or blocks.
[0201] The computer readable program instructions may also be
loaded onto a computer, other programmable data processing
apparatus, or other device to cause a series of operational steps
to be performed on the computer, other programmable apparatus or
other device to produce a computer implemented process, such that
the instructions which execute on the computer, other programmable
apparatus, or other device implement the functions/acts specified
in the flowchart and/or block diagram block or blocks.
[0202] The flowchart and block diagrams in the Figures illustrate
the architecture, functionality, and operation of possible
implementations of systems, methods, and computer program products
according to various embodiments of the present invention. In this
regard, each block in the flowchart or block diagrams may represent
a module, segment, or portion of instructions, which comprises one
or more executable instructions for implementing the specified
logical function(s). In some alternative implementations, the
functions noted in the block may occur out of the order noted in
the figures. For example, two blocks shown in succession may, in
fact, be executed substantially concurrently, or the blocks may
sometimes be executed in the reverse order, depending upon the
functionality involved. It will also be noted that each block of
the block diagrams and/or flowchart illustration, and combinations
of blocks in the block diagrams and/or flowchart illustration, can
be implemented by special purpose hardware-based systems that
perform the specified functions or acts or carry out combinations
of special purpose hardware and computer instructions.
[0203] While the embodiments of the present invention have been
described, the technical scope of the invention is not limited to
the above described embodiments. It is apparent to persons skilled
in the art that various alterations and improvements can be added
to the above-described embodiments. It is also apparent from the
scope of the claims that the embodiments added with such
alterations or improvements can be included in the technical scope
of the invention.
[0204] The operations, procedures, steps, and stages of each
process performed by an apparatus, system, program, and method
shown in the claims, embodiments, or diagrams can be performed in
any order as long as the order is not indicated by "prior to,"
"before," or the like and as long as the output from a previous
process is not used in a later process. Even if the process flow is
described using phrases such as "first" or "next" in the claims,
embodiments, or diagrams, it does not necessarily mean that the
process must be performed in this order.
[0205] As made clear from the above, with the embodiments of the
present invention, it is possible to provide the reliability of a
detected event.
[0206] The programs described herein are identified based upon the
application for which they are implemented in a specific embodiment
of the invention. However, it should be appreciated that any
particular program nomenclature herein is used merely for
convenience, and thus the invention should not be limited to use
solely in any specific application identified and/or implied by
such nomenclature.
[0207] The flowchart and block diagrams in the Figures illustrate
the architecture, functionality, and operation of possible
implementations of systems, methods and computer program products
according to various embodiments of the present invention. In this
regard, each block in the flowchart or block diagrams may represent
a module, segment, or portion of code, which comprises one or more
executable instructions for implementing the specified logical
function(s). It should also be noted that, in some alternative
implementations, the functions noted in the block may occur out of
the order noted in the figures. For example, two blocks shown in
succession may, in fact, be executed substantially concurrently, or
the blocks may sometimes be executed in the reverse order,
depending upon the functionality involved. It will also be noted
that each block of the block diagrams and/or flowchart
illustration, and combinations of blocks in the block diagrams
and/or flowchart illustration, can be implemented by special
purpose hardware-based systems that perform the specified functions
or acts, or combinations of special purpose hardware and computer
instructions.
[0208] The present invention may be a system, a method, and/or a
computer program product at any possible technical detail level of
integration. The computer program product may include a computer
readable storage medium (or media) having computer readable program
instructions thereon for causing a processor to carry out aspects
of the present invention.
[0209] The computer readable storage medium can be a tangible
device that can retain and store instructions for use by an
instruction execution device. The computer readable storage medium
may be, for example, but is not limited to, an electronic storage
device, a magnetic storage device, an optical storage device, an
electromagnetic storage device, a semiconductor storage device, or
any suitable combination of the foregoing. A non-exhaustive list of
more specific examples of the computer readable storage medium
includes the following: a portable computer diskette, a hard disk,
a random access memory (RAM), a read-only memory (ROM), an erasable
programmable read-only memory (EPROM or Flash memory), a static
random access memory (SRAM), a portable compact disc read-only
memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a
floppy disk, a mechanically encoded device such as punch-cards or
raised structures in a groove having instructions recorded thereon,
and any suitable combination of the foregoing. A computer readable
storage medium, as used herein, is not to be construed as being
transitory signals per se, such as radio waves or other freely
propagating electromagnetic waves, electromagnetic waves
propagating through a waveguide or other transmission media (e.g.,
light pulses passing through a fiber-optic cable), or electrical
signals transmitted through a wire.
[0210] Computer readable program instructions described herein can
be downloaded to respective computing/processing devices from a
computer readable storage medium or to an external computer or
external storage device via a network, for example, the Internet, a
local area network, a wide area network and/or a wireless network.
The network may comprise copper transmission cables, optical
transmission fibers, wireless transmission, routers, firewalls,
switches, gateway computers and/or edge servers. A network adapter
card or network interface in each computing/processing device
receives computer readable program instructions from the network
and forwards the computer readable program instructions for storage
in a computer readable storage medium within the respective
computing/processing device.
[0211] Computer readable program instructions for carrying out
operations of the present invention may be assembler instructions,
instruction-set-architecture (ISA) instructions, machine
instructions, machine dependent instructions, microcode, firmware
instructions, state-setting data, configuration data for integrated
circuitry, or either source code or object code written in any
combination of one or more programming languages, including an
object oriented programming language such as Smalltalk, C++, or the
like, and procedural programming languages, such as the "C"
programming language or similar programming languages. The computer
readable program instructions may execute entirely on the user's
computer, partly on the user's computer, as a stand-alone software
package, partly on the user's computer and partly on a remote
computer or entirely on the remote computer or server. In the
latter scenario, the remote computer may be connected to the user's
computer through any type of network, including a local area
network (LAN) or a wide area network (WAN), or the connection may
be made to an external computer (for example, through the Internet
using an Internet Service Provider). In some embodiments,
electronic circuitry including, for example, programmable logic
circuitry, field-programmable gate arrays (FPGA), or programmable
logic arrays (PLA) may execute the computer readable program
instructions by utilizing state information of the computer
readable program instructions to personalize the electronic
circuitry, in order to perform aspects of the present
invention.
[0212] Aspects of the present invention are described herein with
reference to flowchart illustrations and/or block diagrams of
methods, apparatus (systems), and computer program products
according to embodiments of the invention. It will be understood
that each block of the flowchart illustrations and/or block
diagrams, and combinations of blocks in the flowchart illustrations
and/or block diagrams, can be implemented by computer readable
program instructions.
[0213] These computer readable program instructions may be provided
to a processor of a general purpose computer, special purpose
computer, or other programmable data processing apparatus to
produce a machine, such that the instructions, which execute via
the processor of the computer or other programmable data processing
apparatus, create means for implementing the functions/acts
specified in the flowchart and/or block diagram block or blocks.
These computer readable program instructions may also be stored in
a computer readable storage medium that can direct a computer, a
programmable data processing apparatus, and/or other devices to
function in a particular manner, such that the computer readable
storage medium having instructions stored therein comprises an
article of manufacture including instructions which implement
aspects of the function/act specified in the flowchart and/or block
diagram block or blocks.
[0214] The computer readable program instructions may also be
loaded onto a computer, other programmable data processing
apparatus, or other device to cause a series of operational steps
to be performed on the computer, other programmable apparatus or
other device to produce a computer implemented process, such that
the instructions which execute on the computer, other programmable
apparatus, or other device implement the functions/acts specified
in the flowchart and/or block diagram block or blocks.
[0215] The flowchart and block diagrams in the Figures illustrate
the architecture, functionality, and operation of possible
implementations of systems, methods, and computer program products
according to various embodiments of the present invention. In this
regard, each block in the flowchart or block diagrams may represent
a module, segment, or portion of instructions, which comprises one
or more executable instructions for implementing the specified
logical function(s). In some alternative implementations, the
functions noted in the blocks may occur out of the order noted in
the Figures. For example, two blocks shown in succession may, in
fact, be executed substantially concurrently, or the blocks may
sometimes be executed in the reverse order, depending upon the
functionality involved. It will also be noted that each block of
the block diagrams and/or flowchart illustration, and combinations
of blocks in the block diagrams and/or flowchart illustration, can
be implemented by special purpose hardware-based systems that
perform the specified functions or acts or carry out combinations
of special purpose hardware and computer instructions.
[0216] While steps of the disclosed method and components of the
disclosed systems and environments have been sequentially or
serially identified using numbers and letters, such numbering or
lettering is not an indication that such steps must be performed in
the order recited, and is merely provided to facilitate clear
referencing of the method's steps. Furthermore, steps of the method
may be performed in parallel to perform their described
functionality.
[0217] While the embodiments of the present invention have been
described, the technical scope of the invention is not limited to
the above described embodiments. It is apparent to persons skilled
in the art that various alterations and improvements can be added
to the above-described embodiments. It is also apparent from the
scope of the claims that the embodiments added with such
alterations or improvements can be included in the technical scope
of the invention.
* * * * *