JP4727268B2 - Information management apparatus, position information management apparatus, information management method, information management program, computer-readable recording medium, and position information management system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To report appropriate information in response to a request made by either a device connected via a network, an application, or a process. <P>SOLUTION: A reporting process device includes a storage part for storing an application event management table in which event creation requirements are associated with trigger events; a basic event creating part for creating basic events if the event creation requirements held by a basic event management table are determined to be met according to the information inputted; an application event creating part for creating application events if the basic events match the trigger events and if the information acquired according to the basic information matches the event creation requirements associated with the trigger events; and a reporting process part that implements a process for providing reports according to the application events. <P>COPYRIGHT: (C)2007,JPO&amp;INPIT

Description

The present invention relates to an information management device, a location information management device, an information management method, an information management program, a computer-readable recording medium, and a location information management system, and in particular, when a predetermined condition is met, via a network. It is related with the technique which notifies to the apparatus, application, or process connected in this way.

  In recent years, the development of information network technology has been remarkable. Various devices are connected in a network constructed under various environments such as a company, and various applications can be executed on these devices. For this reason, many applications that perform processing based on information input via a network have been developed.

  Thus, a technique has been proposed that provides information to devices connected to a network, assuming that an event has occurred when a defined condition is subordinate (for example, Patent Document 1).

  In the technique described in this Patent Document 1, when a trigger for notifying an event is received and the criteria described in the profile that matches or correlates with this event is satisfied, the method defined in this profile is used. You will be notified.

JP 2003-32721 A

  However, in the technique described in Patent Document 1, there is no specific description about the conditions described in the profile, and complicated conditions cannot be set as conditions for notification. For this reason, there is a problem that an optimum condition cannot be set in order to notify information requested by a device, application or process.

The present invention has been made in view of the above, and an information management apparatus, a position information management apparatus, and the like that enable notification of appropriate information in response to a request from a device, application, or process connected via a network, An object is to provide an information management method, an information management program, a computer-readable recording medium, and a position information management system.

In order to solve the above-described problems and achieve the object, the invention according to claim 1 manages information on a target event and detects a portable information storage medium provided in the target. An information management device connected to the information management device, indicating the type of information to be notified based on predetermined information including identification information for identifying the detection device and signal strength of a signal from the portable information storage medium A first storage unit for storing notification rule information for specifying a notification type; and detection time information for receiving predetermined information from the detection device and indicating the predetermined information and a time at which the predetermined information is received; In accordance with the notification rule information based on a change in the predetermined information with the passage of the detection time information held in the second storage means Identified notification type Of the first notification information, it generates and holds including the detection time information is specified based on the predetermined notification rule for the first notification information held in the first notification information that the notification type, the second notification information, generating means and a transmission destination information for transmitting the application or process as the destination, the information to be notified to the application or process that produces, including the detection time third storage means, the second notification information generated by the generating means, the said to the notification type of the second notification information third storage means for storing the notification type is the type, the And a notification means for notifying the transmission destination indicated by the transmission destination information associated with.

According to a second aspect of the present invention, in the position information management device for managing the position information of the object that can be specified by the detection device detecting the portable information storage medium provided in the object, the identification for specifying the detection device Storing notification rule information for specifying a notification type indicating a type of information to be notified regarding the position of the object based on predetermined information including information and signal strength of a signal from the portable information storage medium; Detection information indicating a position at which the portable information storage medium is received based on the predetermined information and a time at which the predetermined information is received. In association with the second storage means ,
The first notification information of the notification type specified in accordance with the notification rule information based on the change of the position information with the passage of the detection time information held in the second storage means is the detection time. The second notification information of the notification type specified based on the first notification information held and the notification rule predetermined for the first notification information is generated and held including information. Storing generation means for generating including the detection time, transmission destination information for transmitting an application or process as a transmission destination, and a notification type that is a type of information to be notified to the application or process. 3 of the storage unit, the second notification information generated by the generating means, said destination associated with said third memory means to the notification type of the second notification information Characterized by comprising a notification unit that notifies the destination indicated by broadcast, the.

According to a third aspect of the present invention, information executed by an information management device connected to a detection device for managing information on a target event and detecting a portable information storage medium attached to the target is provided. A management method, wherein the information management device determines a type of information to be notified based on predetermined information including identification information for identifying the detection device and signal strength of a signal from a portable information storage medium. A first storage unit for storing notification rule information for specifying a notification type to be displayed; and a second storage unit for storing the predetermined information and detection time information indicating a time when the predetermined information is received in association with each other. If, Bei and destination information for transmitting the application or process as the destination, a third storage means for storing notification type is the type of information should be notified to the application or process, and the Reception step of receiving means, from the detection device, receives a predetermined information, is held in the second storage means in association with the detection time information indicating a time receiving the predetermined information and the predetermined information And the generation means includes a first notification type specified in accordance with the notification rule information based on a change in the predetermined information with the passage of the detection time information held in the second storage means . Notification information is generated and stored including the detection time information, and the notification type specified based on the first notification information stored and the notification rule predetermined for the first notification information , A generation step of generating the second notification information including the detection time; and a notification unit that converts the second notification information generated in the generation step into the notification type of the second notification information. the third And having a notification step of notifying the destination indicated by the transmission destination information associated with 憶 means.

The invention according to claim 4 is characterized in that the information management method according to claim 3 is executed by a computer.

The invention according to claim 5 is a computer-readable recording medium storing the information management program according to claim 4 .

According to a sixth aspect of the present invention, there is provided a portable information storage medium provided in an object existing in an area from which position information is acquired, and the portable information storage without contact with the portable information storage medium. A position information management system comprising: a detection apparatus that detects a medium; and a position information management apparatus that manages position information that manages position information of an object that includes the detected portable information storage medium. The device has a notification type indicating a type of information to be notified regarding the position of the object based on predetermined information including identification information for identifying the detection device and signal strength of a signal from the portable information storage medium. specifying a first storage means for storing notification rule information, from the detection device, receives a predetermined information, and detection time information indicating a time receiving the said predetermined information prescribed information Receiving means for holding the second storage means put response, held in the second storage means, based on a change of the predetermined information with the passage of the detection time information, identified according to the notification rule information The first notification information of the notification type to be generated is generated and stored including the detection time information, and the first notification information stored and the notification rule predetermined for the first notification information are used. notification type specified based, it notifies the second notification information, generating means for generating including the detection time, the transmission destination information for transmitting the application or process as the destination, to the application or process third storage means, the second notification information generated by the generating means, the notification type of the second notification information to be stored and a notification type is the type of information to be the Characterized by comprising a notification unit configured to notify the destination indicated by said destination information associated with the third storage means.

According to the invention according to claim 1, an effect that allows notification of appropriate information for the request by the application or process.

Further, according to the invention according to claim 2, an effect that allows notification of appropriate information for the request by the application or process.

Further, according to the invention according to claim 3, an effect that allows notification of appropriate information for the request by the application or process.

Further, according to the invention according to claim 4, by executing is read by the computer, it is possible to realize the information management method according to claim 3 in use of the computer, similar to the respective information management method The effect of.

Further, the invention according to claim 5, a recording medium storing an information management program according to claim 4, by loading the recording medium into a computer, can execute an information management program There is an effect.

Further, according to the invention according to claim 6, an effect that allows notification of appropriate information for the request by the application or process.

Exemplary embodiments of an information management device, a location information management device, an information management method, an information management program, a computer-readable recording medium, and a location information management system according to the present invention are described in detail below with reference to the accompanying drawings. Explained.

  FIG. 1 is a block diagram showing a configuration of a location information management system according to an embodiment of the present invention. In the position information management system according to the present embodiment, active tags 161a to 161n provided to an object, readers 151a to 151n that receive identification signals transmitted from the active tags 161a to 161n, and readers 151a to 151n. The location information management server 100 is connected to. As shown in this figure, the readers 151a to 151n detect signals output from the active tags 161a to 161n. The readers 151a to 151n transmit the information included in the detected identification signal and the measured signal strength to the positional information management server 100 connected through the network. Then, the location information management server 100 generates an event when the transmitted information and the location information that can be acquired from the measured signal strength match the event generation conditions set in advance, and the event is generated based on this event. The notified notification information is transmitted for each application.

  This event is generated in response to a change in a signal detected from the active tags 161a to 161n or the like, or a change in an event such as the passage of time, in other words, it corresponds to event information. In this embodiment, basic events and applied events are used as events. However, the use of these events is not limited, and a plurality of types of events may be prepared. The basic event and the application event will be described later.

  In this embodiment, the object includes not only an object but also a person. As a result, the tag is detected in various situations, for example, the user holds the active tag 161l, the active tag 161m is provided on an object such as a PHS held by the user, and the active tag 161n is provided on a package to be loaded. Thus, the processing described later can be performed.

  In other words, the active tags 161a to 161n correspond to portable information storage media, and are provided for at least one object or each user. In the present embodiment, the active tags 161a to 161n transmit identification signals every second by radio waves. In this embodiment, the portable information storage medium is not limited to a tag that actively transmits radio waves, and may be a passive one, for example. As a more specific example, communication may be performed using a passive RFID tag or the Bluetooth standard or ZigBee standard that actively emits radio waves.

  In other words, the readers 151a to 151n correspond to detection devices. When receiving the identification signals from the active tags 161a to 161n, the tags included in the received identification signals at the address and port indicating the location information management server 100 The ID and the measured signal strength are transmitted and associated with the reader IDs of the readers 151a to 151n in the position information management server 100. The reader ID can be specified from the correspondence between the reader ID and the reader address. The address of the source reader can be specified from the source address included in the header of the packet used when sending the information.

  As another form different from the present embodiment, the readers 151a to 151n may transmit the reader IDs indicating the readers 151a to 151n in association with the above information.

  FIG. 2 is an explanatory diagram conceptually showing the overall configuration of the location information management server 100. Each reader 151a-c transmits the detected identification signal together with the signal strength to the positional information management server 100 through the network, and the positional information management server 100 further detects the position information of the user or the object based on the received information. And notifies the applications A201 to D204 through the network. The notifications for the applications A201 to D204 are transmitted every predetermined time, or when there is a request from each application.

  Returning to FIG. 1, the location information management server 100 includes a storage unit 101, a reception processing unit 102, a tag information management unit 109, a location information acquisition unit 103, a basic event generation unit 104, and an application event generation unit. 105, a notification information generation unit 106, a notification processing unit 107, and an event editing reception unit 108, and after storing the identification information transmitted from the readers 151a to 151n and the position information acquired from the measured signal strength , Generate a basic event when a condition for generating a basic event is satisfied based on this position information, etc., generate an applied event when a condition for generating an applied event is satisfied based on the generated basic event, Notification information is generated based on the generated application event and notified to another application or process.

  The basic event is information generated when a change in a basic event such as the passage of time or the detection of an active tag is detected. The basic event corresponds to first event information in other words.

  Also, the applied event is information generated when it is determined that the condition about the complex event that can be determined based on the basic event and the generated applied event is satisfied, such as staying in a predetermined place. It is.

  The storage unit 101 stores a position information database 111, a basic event database 112, an applied event database 113, and a filtering database 114. In addition, the storage unit 101 can be configured by any commonly used storage unit such as an HDD, an optical disk, a memory card, and the like.

  The position information database 111 stores a reader position management table, a tag signal management table, and an ID position information management table. FIG. 3 shows the structure of the reader position management table. As shown in the figure, the reader position management table holds a reader ID, reader position information, and reader address in association with each other. By associating the reader ID with the address of the reader, the reader ID can be specified from the address of the reader from which information indicating that an active tag has been detected is transmitted. Thereby, the position information of the reader can be specified based on the reader ID. The reader address can be obtained by referring to the header of the packet transmitted from the reader.

  FIG. 4 shows the structure of the tag signal management table. As shown in the figure, the tag signal management table holds IDs, reader IDs, signal strengths, and detection times in association with each other. That is, the tag signal management table manages information in which detection time is associated with information transmitted from the readers 151a to 151n as a record. The ID is an ID used for specifying an object provided with the active tags 161a to 161n.

  FIG. 5 is a diagram showing the structure of the ID position information management table. As shown in the figure, the ID position information management table holds IDs, position information, and detection times in association with each other. Each record held by the ID position management table is generated based on the records held by the reader position management table and the tag signal management table. The detection time is the time when the readers 151a to 151n detect the active tags 161a to 161n. By storing the position information in this way, it is possible to detect a change in the position information of the object, calculate the distance between a plurality of objects, and the like.

  The basic event database 112 stores a basic event management table. FIG. 6 is a diagram showing the structure of the basic event management table. As shown in the figure, a basic event to be generated and an event generation condition are stored in association with each other. In FIG. 6, the event generation conditions are written in Japanese for easy understanding, but are actually held in a format that can be recognized by the location information management server 100. The same applies to FIGS. 7 and 8 described later. In other words, the event generation condition held in the basic event management table corresponds to basic generation condition information.

  The basic event shown in this figure will be described. 'DETECTED' is generated when the position information of the detected active tag is acquired. 'UNDETECTED' is generated when an active tag cannot be detected and when an active tag is detected but position information cannot be acquired. 'POS_UPDATE' is generated when the position information management table is updated with the acquired position information of the active tag. 'POS_CHANGE' is generated when the ID specifying the acquired position information is already held as a record of the position information management table, and the position information held by this record is different from the acquired position information. . ‘TIME_CYCLE’ is an event periodically generated every predetermined cycle time. The predetermined cycle time is set to a time interval for periodically notifying the application of information, for example, 1 second.

  In addition, when events of ‘DETECTED’, ‘UNDETECTED’, ‘POS_UPDATE’ and ‘POS_CHANGE’ are generated, ID, position information, and detection time are included in these events. In addition, in this embodiment, “TIME_CYCLE” is generated including the current time and the ID and position information held by the record updated since the previous transmission in the position information management table. It is possible to generate only including the current time. Note that this embodiment does not limit the event generated in the present invention to the above event, but sets an appropriate event according to information requested by the notification destination application.

  The applied event database 113 stores an applied event management table, an event state management table, and an area table.

  FIG. 7 is a diagram showing the structure of the applied event management table. As shown in the figure, an event name, a trigger event, an event generation condition, an argument, transmission data, an expiration date, and a validity flag are associated and held. An application event is generated by an application event generation unit 105 to be described later using the table shown in FIG.

  This applied event management table is information that holds the generated applied event and the conditions to be generated in association with each other, in other words, corresponds to event correspondence information. In addition, the event generation conditions in the applied event management table correspond to event generation condition information in other words. The trigger event is an event used as a comparison target when generating, and in other words, corresponds to target event information.

  The event name indicates the event name of the application event generated when the generation condition is satisfied. The trigger event indicates an event serving as a trigger for determining whether or not to generate the application event, and not only a basic event but also an application event is used as a trigger. The event generation condition indicates a condition for generating an application event. The argument holds a value used in the event generation condition. For example, when the event generation condition is “when detected at a specified position” and the argument is “ID001, (10, 30)”, an active tag with ID001 is detected at coordinates (10, 30) indicating the specified position. It is determined that the event generation conditions are met. If no argument is set, it matches with any value. For example, when the argument is “, (10, 30)” in the event generation condition described above, it is determined that the event generation condition is matched when an arbitrary active tag is detected at the coordinates (10, 30) indicating the designated position. To do.

  The transmission data is information included in the generated event. The valid period indicates a time limit for generating the application event indicated by this record. When this time limit has passed, no event is generated using this record. The expiration date can be specified when an event is added by the event editing accepting unit 108 described later. The event whose expiration date has expired is deleted or invalidated by setting the validity flag to '0'.

  The valid flag indicates whether or not this record is valid. The valid flag is valid when it is “1”, and an event is generated when the generation condition indicated by this record is satisfied. In case of ', it is invalid and no event is generated in this record. A method for generating an application event using this table will be described later.

  FIG. 8 is a diagram showing a list of applied events registered as records in the applied event management table shown in FIG. From the list shown in the figure, an argument, an expiration date, a validity flag, and the like are set and registered in the application event management table according to the necessity of the application and process to which the notification information is to be transmitted. These applied events are not only registered in the applied event management table as events to be generated, but also set as event generation conditions. For example, in the applied event management table shown in FIG. 7, in the “AWAY_AREA” event of the ninth record, the “LASTING” event is set as the event generation condition. As a result, when the event generation condition of the “LASTING” event is satisfied, the “AWAY_AREA” event is generated.

  FIG. 9 shows the structure of the event state management table. As shown in the figure, time and occurrence events are associated and held. This makes it possible to recognize events that occur at each time. Although not shown in the drawing for improving the visibility, the held event holds not only the event name but also information held by the event, for example, ID, position information, detection time, and the like. This makes it possible to identify which ID or at which position these events have occurred. The events held in this table may be any events, and basic events and application events are registered in this embodiment. Depending on the mode used, only one of them may be registered.

  FIG. 10 shows the structure of the area table. As shown in the figure, the area name and the corresponding area are held in association with each other. The area holds the shape of the area and the coordinates for specifying the area. For example, when it is described as a rectangular area, it indicates that the area is a rectangle, and when it is a rectangular area, the position coordinates of two points for specifying the rectangle are held. Further, the shape of the region may be other than a rectangle, and for example, a circular area may be considered. In the case of this circular area, it is conceivable to maintain the position coordinate and radius as the center.

  The filtering database 114 stores an ID information management table and a filter table. FIG. 11 shows the structure of the ID information management table. As shown in the figure, the ID information management table holds an ID, a name, and a type in association with each other. The name indicates the name of the object, and the name unified in each application can be used by holding it in the ID information management table. Further, by holding the name in the ID information management table, it becomes possible for a human to identify the object itself having a tag. The type holds the attribute of the object indicated by the ID, such as whether the object specified by the ID is a person or a thing, if it is a person, its affiliation, and if it is an object, the property. Thus, filtering based on the attribute of the object can be performed by holding the type in association with the ID.

  FIG. 12 shows the structure of the filter table. As shown in the figure, an event, a filter type, an ID, a position, a service type, a cipher, a transmission destination, and transmission information are held in association with each other. The “event” field indicates that transmission is performed when it matches the generated application event. In other words, the “event” field corresponds to notification event information. The “filter type”, “ID”, and “position” fields are fields indicating filtering conditions, and are transmitted only when the conditions described in these fields are satisfied. In other words, these fields correspond to notification condition information in other words. In addition, when there is no description in these fields, it is assumed that no filtering condition is set. The “service type” field holds a transmission protocol for transmission. The “encryption” field holds an encryption method for transmission to the application. The “transmission destination” field indicates the transmission destination of information, and an application for processing information exists at the transmission destination. The “transmission information” field holds the type of information to be transmitted. Thereby, only information necessary for each application can be transmitted. In other words, when the filtering condition held by the record is satisfied, the information held in “transmission information” is acquired, and the acquired information is associated with the record in “transmission destination” and stored in “service” It is transmitted using the transmission protocol set in “Type”. The information to be transmitted can be grasped by referring to the associated “transmission information” field. As a result, a condition to be transmitted for each application is set, and information can be transmitted only when this condition is satisfied.

  Returning to FIG. 1, the reception processing unit 102 performs a process of receiving information transmitted from the readers 151 a to 151 n. In the present embodiment, the reception processing unit 102 receives the tag ID and the measured signal strength received from the readers 151a to 151n via the network. When receiving, the IP address of the reader can be specified by referring to the header of the received packet. The tag ID, signal strength, and reader IP address are information determined to be transmitted from the readers 151a to 151n, and in other words, correspond to predetermined information. The reception processing unit 102 requests the tag information management unit 109 to update the tag signal management table with information in which detection times are associated with the received information. The detection time is the time when the readers 151a to 151n are considered to detect the active tags 161a to 161n, in other words, the current time when the tag ID or the like is received from the readers 151a to 151n.

  The tag information management unit 109 performs processing on each table held in the device DB. In the present embodiment, the tag information management unit 109 identifies a reader ID from the reader IP address input from the reception processing unit 102 with reference to the reader position management table, and the specified reader ID is input. With the information in which the ID, the signal strength, and the detection time are associated with each other, update is performed on the matching record using the reader ID and ID of the tag signal management table as a key. Thereby, in the tag signal management table, the associated reader ID and ID can hold the signal intensity and detection time based on the latest detection information.

  In addition, the tag information management unit 109 holds only for a certain period of time when it is not updated with the record held in the tag signal management table. In the present embodiment, this fixed time is 3 seconds or more. Thus, for example, when a predetermined active tag is detected by reader a, reader b, and reader c one second ago, but is detected only by reader a and reader b this time, a reader indicating reader a and reader b is displayed. Only the record associated with the ID is updated, and the record associated with the reader ID indicating the reader c holds the information one second before. In this way, if it is detected even once within 3 seconds, information associated with the tag ID is held. That is, the position information can be calculated even when a signal from the active tag cannot be detected temporarily due to some trouble.

  The position information acquisition unit 103 checks whether or not the tag signal management table is updated every predetermined period, and if updated, acquires an ID that can be specified by the updated record. The position information of the active tags 161a to 161n is acquired based on the information of the record that holds the information. The position information can be acquired from the reader ID held in the tag signal management table, the reader ID held in the reader position management table, and the position information of the reader. In the present embodiment, the predetermined period is 1 second, and the position information acquisition unit 103 checks whether or not it is updated every second. In other words, the acquired position information corresponds to the acquired position information.

  In addition, when there is only one reader that has detected the active tag, the position information acquisition unit 103 uses the detected coordinate system and position information of the reader as a coordinate system and position information indicating the position of the active tag 161b.

  In addition, the position information acquisition unit 103 may use any of various currently proposed position calculation methods when there are a plurality of readers that have detected an active tag. For example, an average value of the detected position information of the reader, or a method of taking an average value after weighting the detected position information of the reader with a signal intensity is conceivable.

  Then, the position information acquisition unit 103 updates the position information management table in association with the acquired ID, position information, and detection time. At this time, it is confirmed whether or not the position has changed from the previously updated position information. Then, a basic event generation unit, which will be described later, determines whether or not the position information management table has been successfully updated in the acquired ID, position information, and detection time, and whether or not the position has changed from the previously updated position information. To 104.

  The basic event generation unit 104 generates a basic event and outputs the basic event to the applied event generation unit 105 when the event generation conditions held in the basic event management table shown in FIG. There are no particular limitations on the conditions set as the event generation conditions, and for example, conditions based on object position information, time, an active tag detection region, or the active tag itself may be considered. In other words, the event generation condition held in the basic event management table corresponds to the first event condition.

  In the present embodiment, the basic event generation unit 104 generates an event at every predetermined event generation interval. The generation interval is set to a suitable time based on the needs of the application to be notified or the processing capability of the location information management server 100. In this embodiment, the event generation interval is set to 1 second.

  Further, the basic event generation unit 104 generates an event based on the position information or the like when receiving the position information or the like within the event generation interval. In the present embodiment, the basic event generation unit 104 generates a “DETECTED” event when it receives position information or the like, and includes ID, position information, and detection time in this event. If the position information management table has been successfully updated, the basic event generation unit 104 generates a “POS_UPDATE” event and includes the detected ID, position information, and detection time. If the position has changed from the previously updated position information, the basic event generation unit 104 generates a “POS_CHANGE” event and includes the detected ID, position information, and detection time.

  Further, the basic event generation unit 104 generates a basic event when the event generation condition is satisfied even when position information or the like is not received within the event generation interval. In the present embodiment, the basic event generation unit 104 is within a holding period determined to hold information detected since the previous detection of the active tag, and position information or the like has not been input within the current generation interval. In this case, an 'UNDETECTED' event is generated. In addition, the basic event generation unit 104 includes the ID detected in the holding period but not detected this time, the position information and the detection time at the previous detection, in the ‘UNDETECTED’ event. In addition, the basic event generation unit 104 generates a “TIME_CYCLE” event for each cycle time. In this embodiment, the holding period is 3 seconds and the cycle time is 1 second.

  FIG. 13 is an explanatory diagram showing an example of the correlation between the position information input from the position information acquisition unit 103 and the event generated by the basic event generation unit 104. As shown in the figure, the basic event generation unit 104 generates an event at every event generation interval. In this figure, in order to make explanation easy, it is assumed that there is one active tag detected, and the description of the ID and the like of this active tag is omitted in this figure. Further, in the environment shown in this figure, since the radio wave condition is bad, the identification signal transmitted from the active tag can be detected only once every few seconds. Based on predetermined information such as an identification signal detected in such an environment, the position information acquisition unit 103 acquires the position information and outputs it to the basic event generation unit 104. Note that the position information acquisition unit 103 does not output the position information because the tag signal management table is not updated at the time when the identification signal from the active tag cannot be detected.

  The basic event generation unit 104 generates an event at every event generation interval (1 second) regardless of whether position information or the like is input. That is, an event is generated on the condition that 1 second has elapsed, and the time elapsed since the previous generation corresponds to elapsed time information. The basic event generation unit 104 generates a “TIME_CYCLE” event every time regardless of whether position information or the like is input. Since no position information or the like is input at the event generation time 1301, the basic event generation unit 104 generates an “UN_DETECTED” event.

  In addition, since the position information and the like are input at the event generation time 1302, the basic event generation unit 104 generates a 'DETECTED' event, and further indicates' POS_UPDATE indicating that the position information management table has been updated with the acquired position information. 'Generate an event.

  Further, since the position information input at the event generation time 1303 is different from the position information input at the previous event generation time 1302, the basic event generation unit 104 performs the event other than the “DETECTED” event and the “POS_UPDATE” event. , Generate a 'POS_CHANGE' event. These generated events are input to an applied event generation unit 105 described later.

  By providing the basic event generation unit 104, it is possible to generate a basic event corresponding to a change in the phenomenon. The applied event generation unit 105 can generate an applied event based on more complicated conditions by using this basic event as a trigger.

  The applied event generation unit 105 uses the generated event as a trigger to generate an applied event when the event generation conditions held in the applied event management table shown in FIG. 7 are met. An event used as a trigger is not particularly limited. In the present embodiment, either a basic event or an application event may be used as a trigger.

  Further, the application event generation unit 105 may use information held in another table in order to determine whether or not the event generation conditions held in the application event management table are met. In the present embodiment, the applied event generation unit 105 satisfies the event generation condition by using the information stored in the area table and the event state management table held in the applied event database 113 as necessary. Determine whether or not. This makes it possible to set event generation conditions in more detail.

  Further, in the present embodiment, the applied event generation unit 105 generates an event at predetermined event generation intervals in the same manner as the basic event generation unit 104. In this embodiment, the event generation interval of the applied event generation unit 105 is set to be every second.

  Further, the applied event generation unit 105 outputs both the input basic event and the generated applied event to the notification information generation unit 106. Further, the applied event generation unit 105 determines whether or not an event generation condition held in the applied event management table is met by using the generated applied event as a trigger, and generates an applied event when the event is met.

  The applied event generation unit 105 registers the input basic event and the generated applied event in association with the current time in the event state management table record at each event generation interval. When an event is registered in the event state management table, not only the event name but also information included in the event, such as ID, position information, and detection time, are registered.

  An example in which an application event is generated using the application event management table shown in FIG. 7 will be described. When the “DETECTED” event is input from the basic event generation unit 104, the application event generation unit 105 matches the trigger events of the first, second, and fourth records of this application event management table. When the condition is satisfied, an application event for each record is generated. The ID included in the input 'DETECTED' event is ID001, and the position information is (10, 10). In this case, since the event generation conditions and the conditions specified by the arguments of the first record and the second record are not satisfied, the 'PRESENT' event is not generated.

  On the other hand, the location information (10, 10) is identified as the first conference room from the area table shown in FIG. In other words, the event generation condition of the fourth record “when ID001 is detected in the first conference room” according to the argument and the event generation condition is satisfied. As a result, the applied event generation unit 105 generates a “PREENT_AREA” event. Further, the generated event includes ID0001, which is information specified by “transmission data”, the first meeting room, and the time when the tag is detected. Note that the applied event generation unit 105 needs to acquire a coordinate area indicating the “first conference room” from the area table when making the determination.

  Then, the applied event generation unit 105 determines whether there is a record triggered by the generated “PRESENT_AREA” event. If it is determined that there is an event, the same processing as described above is performed whether or not the event generation condition of this record is satisfied. In the applied event management table shown in FIG. 7, “STAY_AREA” exists as an applied event of “PREENT_AREA” in the trigger event. Therefore, referring to the event generation condition, the argument is ID001 and 10 minutes in LASTING (PREENT_AREA). When these event generation conditions are satisfied, a 'STAY_AREA' event is generated.

  The 'LASTING' event is an event that is generated when a specified event continues for a specified time or more, and when the same event is generated continuously at intervals of 1 second during the specified time. In other words, the “LASTING” event is an event that is defined as having been detected 300 times when the specified time is 5 minutes, that is, on the condition that it has been detected a predetermined number of times within the specified time. This is a generated event.

  By enabling the setting of such event generation conditions, it becomes possible to register the 'STAY_AREA' event, so that a specific person or an arbitrary person can confer as a service that the location information management server 100 can provide. It is possible to notify in real time that information is present. Note that whether this specific person or an arbitrary person can be changed by setting an argument.

  Next, the applied event generation unit 105 outputs the generated event and the input event to the notification information generation unit 106, and further generates the generated 'PRESENT_AREA' event and the input 'DETECTED' event in the event state management table. sign up.

  Further, the applied event generation unit 105 may generate one applied event based on a plurality of events. For example, in the 'CLOSE' event shown in FIG. 7, the event generation condition is “when multiple tags are in the vicinity” and the arguments are 4 and 3, so that 4 active tags are within 3 meters. Event generation conditions are met. Since the trigger event is “POS_UPDATE”, the applied event generation unit 105 receives four or more “POS_UPDATE” within the event generation interval, and the position information held by these events is within 3 meters. Then, a “CLOSE” event is generated assuming that the event generation condition of this record is satisfied. As described above, an event having a more complicated condition can be generated by setting a plurality of events as conditions and generating one event.

  An example in which the applied event generation unit 105 refers to the event state table to determine whether or not the event generation condition is satisfied will be described. For example, in the above-described ‘STAY_AREA’ event, the event generation condition is ‘LASTING (PREENT_AREA)’, and the argument is ID001 and 10 minutes. In order to confirm whether or not this event generation condition is satisfied, the applied event generation unit 105 refers to the event state table and confirms whether or not the “PRESENT_AREA” event including the ID001 is continuously registered for 10 minutes. To do. If the event has been continuously registered for 10 minutes, the applied event generation unit 105 determines that the event generation condition is satisfied, and generates a “STAY_AREA” event. Note that since there is no application event triggered by 'STAY_AREA' in the application events held in the application event management table shown in FIG. 7, the application event generation unit 105 satisfies the event generation condition using the 'STAY_AREA' event. It is not determined whether or not. The generated ‘STAY_AREA’ event includes the UID 001, the area, the time when the tag is detected, and the duration after entering the area.

  FIG. 14 is a diagram illustrating an example of a record registered in the event state management table when the above-described ‘STAY_AREA’ event is generated. As shown in this figure, the 'STAY_AREA' event, the 'PRESENT_AREA' event that triggered this event, and the 'DETECTED' event that triggered this event are simultaneously registered with 'POS_UPDATE' indicating that it has been updated. .

  Another example in which the applied event generation unit 105 refers to the event state table to determine whether or not the event generation condition is satisfied will be described. There is an 'EV_CHANGE' event as an event that needs to be determined whether or not the event generation condition is satisfied by referring to the event state reference table. As shown in the list of FIG. 8, this event is determined to satisfy the event generation condition when a change occurs between the event generated last time and the event generated this time. As described above, it is possible to generate an event by comparing the event generated last time with the event generated this time, so that an event with a more complicated condition can be generated.

  As an event for which this 'EV_CHANGE' event is set as an event generation condition, there is a 'LEAVE' event in the eighth record of the applied event management table shown in FIG. The ‘LEAVE’ event is set as a trigger event ‘ABSENT_AREA’ event, ‘EV_CHANGE (PREENT_AREA, ABSENT_AREA)’ is set as an event generation condition, and ‘reception room’ is set as an argument.

  In other words, when the ‘ABSENT_AREA’ event is generated, the applied event generation unit 105 determines whether or not the event generation condition of the ‘LEAVE’ event is satisfied by using this event as a trigger. If the 'ABSENT_AREA' event generated this time contains information about a drawing room, the condition is met. In this case, the applied event generation unit 105 refers to the event state management table in order to check whether or not the “PREENT_AREA” event including the information about the reception room is generated last time. If the event state management table holds a 'PRESENT_AREA' event including information on the reception room generated last time, the application event generation unit 105 determines that the event generation condition has been satisfied, and the applied event generation unit 105 determines 'LEAVE'. Generate an event. Needless to say, the IDs held by the 'ABSENT_AREA' event generated this time and the 'PRESENT_AREA' generated last time must match.

  FIG. 15 is a diagram showing an example of an event state management table in which the generated “LEAVE” event is held. As shown in the figure, when a 'PRESENT_AREA' event is generated last time and a 'ABSENT_AREA' event is generated this time, a 'LEAVE' event is generated. After that, even if the 'ABSENT_AREA' event is generated, the 'LEAVE' event is not generated.

  Returning to FIG. 1, the notification information generation unit 106 generates notification information based on the basic event and the application event input from the application event generation unit 105. In the present embodiment, the notification information generation unit 106 generates notification information that satisfies the conditions held in the filter table from the input event. Note that the generated notification information includes an event name, and this allows the destination application to specify when the notification information was generated. The notification information generation unit 106 performs filtering using the filter table shown in FIG. 12, and transmits the transmission information to the transmission destination.

  In addition, the notification information generation unit 106 satisfies not only the information held by the input event such as the basic event or the application event but also the condition that the information acquired based on the information held by the event is held in the filter table. In some cases, notification information may be generated. For example, the ID included in the event is compared with the ID stored in the ID information management table, the record information corresponding to the input event is acquired, and the information stored in the acquired record is used for filtering. It is determined whether or not the conditions held by the table are satisfied. When these holding conditions are satisfied, the notification information generation unit 106 generates notification information.

  For example, the notification information generation unit 106 uses the ID included in the “POS_UPDATE” event as a key, and acquires record information from the ID information management table. As a result, the name and type corresponding to the event can be acquired. Filtering can be performed using these conditions as conditions set in the filter table.

  Further, the notification information generation unit 106 can set not only information held by an event but also information acquired from the associated table as transmission information as transmission information. In the example described above, the name and type acquired from the ID information management table can also be set as information to be transmitted.

  The filter table conditions will be described. For example, when the “ID” of each record in the filter table matches the ID included in the basic event or application event, the condition defined by “ID” is satisfied. As described above, the notification information generation unit 106 generates notification information when the condition held by each record is satisfied.

  As another example, a case will be described in which the notification information generation unit 106 acquires information from another table than information included in the input event and determines whether the condition is satisfied. First, the notification information generation unit 106 compares “ID” included in the input event with the field “ID” of the ID information management table, and acquires the matched record information. When the “type” included in the acquired record information matches the “filter type” of each record in the filter table, the condition defined by the “filter type” is satisfied. As described above, the notification information generation unit 106 generates notification information when the condition held by each record is satisfied.

  Further, when the condition of the filter table record is satisfied, the notification information generation unit 106 refers to the “transmission information” field of the record indicating the filter, acquires the information described in “transmission information”, and acquires the information Include information in the notification information. As a result, notification information including information suitable for each application can be generated.

  Further, in the present embodiment, the information described in the “transmission information” field may be information included in the input event or information that can be acquired from a correspondence relationship with the input event. . Information that can be acquired from the correspondence relationship with the input event includes information that can be acquired from a table group held in the filtering database 114. For example, “name”, “type”, and the like held in the ID information management table may be set as a transmission condition.

  Thereby, the notification information generation unit 106 can acquire information described in “transmission information” as information necessary for generating notification information.

  Further, the notification information generation unit 106 outputs the generated notification information to the notification processing unit 107. Further, when outputting the notification information, the notification information generation unit 106 outputs “transmission destination” and “service type” held in the record of the filter table. Further, when the filter holds the encryption, the notification information generation unit 106 outputs the encryption along with the notification information.

  When the notification information, “transmission destination”, and “service type” are input from the notification information generation unit 106, the notification processing unit 107 calls a program that performs transmission processing with the transmission protocol held by the service type, and sends the notification information. Process to send to the destination. In addition, when encryption is input together with notification information or the like, the notification processing unit 107 transmits the notification information after encryption using the input encryption method.

  With this input encryption method, the location information management server 100 and the application are encrypted. Any means may be used as the encryption means, for example, Ipsec, https, SSL, DES, or the like. As described above, the notification processing unit 107 can prevent information leakage by performing the encryption process. Furthermore, privacy can be maintained and security can be improved.

  The event editing reception unit 108 receives a request from an application or process connected to the location information management server 100, and adds, changes, or deletes records in each table in order to transmit notification information suitable for the request. In the present embodiment, the event edit accepting unit 108 adds a record in the applied event management table of the applied event database 113 or deletes or changes the corresponding record in order to set a condition for generating notification information.

  Further, the event edit accepting unit 108 receives, as a record to be added from another application, an event name selected from the applied event list shown in FIG. 8 and information on an argument for setting an event generation condition. Application events can be registered. Thereby, an application event suitable for the request of another application can be generated.

  In addition, when the event editing reception unit 108 receives a request to delete or change a condition for generating an event registered by a request from another application, the event editing reception unit 108 can identify from the information received together with the request Delete or change the record. The information received together with this request may be any information as long as it can specify a record, and for example, an event name and an argument can be considered. In the case of a change, a condition to be changed is received together with the above information, and the record is changed according to the condition to be changed.

  Further, when deleting a record in the application event management table, the event editing accepting unit 108 checks the dependency relationship, and if there is a record using the record to be deleted as an event generation condition such as a trigger event, the record The use flag can be turned off to stop use. Further, the event edit accepting unit 108 checks the dependency when performing a process of newly adding the record, and sets a valid flag when a record used as an event generation condition exists in a record to be generated in the future. Processing such as turning on may be performed. With these processes, it is possible to reduce the load of the event generation process, and it is possible to reduce labor at the time of event generation.

  Further, when a filtering condition, a transmission destination, and the like are input from another application, the event editing reception unit 108 registers a record based on the information input in the filter table of the filtering database 114.

  In addition to the request for filter registration, the event edit accepting unit 108 also accepts a request for changing a filter or deleting a filter. The received request deletes or changes the corresponding record in the filter table using information specifying the filter received together with the request, and in the case of a change, information indicating the condition to be changed. The conditions for specifying the filter may be any conditions as long as the record can be specified, such as the “transmission destination” field and the “event” field in the service filter table.

  As described above, the event editing accepting unit 108 can register, change, and delete events and filters to be generated, so that other applications want information to be transmitted periodically, as well as when necessary. Even if only information is transmitted, it is possible to cope.

  Next, processing from receiving information such as an ID from the reader in the positional information management server 100 according to the present embodiment configured as described above until notification information is notified to the application will be described. FIG. 16 is a flowchart showing a procedure of the above-described processing in the location information management server 100 according to the present embodiment.

  First, the reception processing unit 102 receives information such as tag IDs of the active tags 161a to 161n detected by the readers 151a to 151n from the readers 151a to 151n (step S1601).

  Then, the tag information management unit 109 updates the tag signal management table in association with the tag ID received by the reception processing unit 102, the reader ID of the received reader, the signal strength, and the detection time (step S1602).

  Next, the position information acquisition unit 103 checks whether the tag signal management table is updated by the tag information management unit 109 every second. When the position information acquisition unit 103 has been updated, the position information acquisition unit 103 acquires an ID indicating an active tag detected from the updated record, acquires a record holding information on the acquired ID, By calculating the position information based on the information, the position information of the active tags 161a to 161n is acquired (step S1603).

  Then, the basic event generation unit 104 generates a basic event associated with the satisfied condition when the input position information or the like or a condition set in advance by a lapse of a predetermined time is satisfied (step S1604).

  Next, the applied event generation unit 105 uses the input basic event or the generated applied event as a trigger, and generates an applied event when the event generation conditions held in the applied event management table are met (step S1605). . Then, the applied event generation unit 105 outputs all the input basic events and the generated applied events to the notification information generation unit 106.

  Next, when the information included in the input event and the information associated with this information satisfy the filter condition, the notification information generation unit 106 stores “transmission information” held by the filter. Information specified by the field is acquired, and notification information is generated by associating the acquired information (step S1606). That is, notification information is not generated when the information related to the input event does not satisfy the filter condition.

  Next, the notification processing unit 107 performs processing for notifying the generated notification information to the transmission destination specified in the “transmission destination” field held by the filter (step S1607). At the time of notification, transmission is performed using the transmission protocol held by the service type of the filter, and when the encryption of the filter is defined, encryption is performed using the defined encryption.

  According to the processing procedure described above, it is possible to transmit information suitable for each application after detecting the active tags 161a to 161n. The processing procedure described above shows an example of the processing procedure from reception of information such as an ID according to the present embodiment to generation of notification information and notification processing. It is not limited to procedures.

  Next, a process from the input of position information and the like in the basic event generation unit 104 of the position information management server 100 according to the present embodiment configured as described above to the output of the generated basic event will be described. FIG. 17 is a flowchart illustrating the above-described processing procedure in the basic event generation unit 104 according to the present embodiment.

  First, the basic event generation unit 104 receives input of ID position information and the like updated by the position information acquisition unit 103 (step S1701).

  Next, the basic event generation unit 104 sets the input information such as the ID position information received in step S1701 in the record of the basic event management table when one second has elapsed since the generation of the previous event. It is determined whether the event generation condition is satisfied (step S1702).

  If it is determined that the event generation condition is satisfied (step S1702: YES), the basic event generation unit 104 generates an event from the event name associated with the event generation condition (step S1703). In addition, when generating an event, the basic event generation unit 104 includes information such as position information and ID in the event.

  Then, it is determined whether or not the confirmation has been completed for all event generation conditions held in the basic event management table (step S1704).

  If it is determined that the confirmation has been completed for all event generation conditions (step S1704: YES), the basic event generation unit 104 performs a process of outputting the generated basic event (step S1705).

  Further, when it is determined that the event generation conditions are not satisfied (step S1702: No) and when it is determined that the confirmation has not been completed for all event generation conditions (step S1704: No), the determination is made in step S1702. The record next to the record holding the event generation condition is set as a determination target (step S1706). As a result, the next event generation condition is set, and processing is performed from step S1702 to determine whether or not this event generation condition is satisfied.

  With the processing procedure described above, a basic event can be generated from the input position information and the like. The processing procedure described above shows an example of the processing procedure from the input of position information or the like according to the present embodiment to the output of the generated basic event, and the present invention is limited to this processing procedure. It is not a thing.

  Next, processing from the reception of the input of the basic event to the output of the input basic event and the generated application event in the application event generation unit 105 according to the present embodiment configured as described above will be described. FIG. 18 is a flowchart showing the above-described processing procedure in the applied event generation unit 105 according to the present embodiment.

  First, the applied event generation unit 105 receives an input of a basic event from the basic event generation unit 104 (step S1801).

  Next, the applied event generation unit 105 sets the input first basic event as a target event to be compared (step S1802).

  Then, the applied event generation unit 105 determines whether the event name of the basic event set as the target event matches the event name of the trigger event held in the applied event management table (step S1803). When making a determination for the first time, the first record held in the applied event management table is set as a determination target, and the determination is made using the trigger event of the first record.

  If it is determined that the event names match (step S1803: Yes), the applied event generation unit 105 triggers based on the information held by the basic event set as the target event and the information acquired from the correspondence with the basic event. It is determined whether a condition for generating an application event associated with the event is satisfied (step S1804).

  If it is determined that the application event generation condition is satisfied (step S1804: YES), the application event generation unit 105 generates an application event (step S1805).

  In addition, when it is determined that the application event generation condition is not satisfied (step S1804: No) and when it is determined that the event names do not match (step S1803: No), the application event generation unit 105 does not perform any particular processing. .

  Then, the applied event generation unit 105 sets the generated applied event as a target event, and performs recursion processing for the processing from step S1803 to step S1808 (step S1806). Thereby, an application event based on the application event is generated.

  Next, the applied event generation unit 105 determines whether or not the application event generation conditions of all records held in the applied event management table have been compared (step S1807).

  If it is determined that the application event generation conditions have been compared (step S1807: NO), the application event generation unit 105 sets the next record held in the application event management table as a determination target (step S1808). The determination is performed using the trigger event of the record set as the determination target in step S1803.

  Then, the applied event generation unit 105 determines whether determination processing has been performed for all input basic events (step S1809).

  When it is determined that the determination process has not been completed for all the input basic events (step S1809: No), the applied event generation unit 105 is the basic that is not the target of the determination process for the input basic event. An event is selected, and the selected basic event is set as a target event for the next determination process (step S1810). The determination is made based on whether or not the event name of the trigger event matches with the set basic event (step S1810).

  When it is determined that the determination process has been completed for all input basic events (step S1809: Yes), the applied event generation unit 105 generates notification information about the input basic events and the generated applied events. The output processing is performed on the unit 106 (step S1811).

  Since the basic event and the applied event are input to the notification information generating unit 106 by the processing procedure described above, it is possible to generate the notification information based on the conditions set in the applied event management table. The processing procedure described above shows an example of the processing procedure from the reception of the input of the basic event according to the present embodiment to the output of the input basic event and the generated application event. The processing procedure is not limited to this.

  In this embodiment, the cycle time indicating the interval for generating 'TIME_CYCLE' is set to 1 second, and the generation interval for generating the basic event by the basic event generation unit 104 is set to 1 second. Instead, a suitable time is set according to the needs from the application and the processing capability of the location information management server 100. Further, the holding period is not limited to 3 seconds.

  In the present embodiment, the event is generated in two stages. However, the event is not limited to two stages, and may be three or more stages.

  In the present invention, by providing an event generation definition mechanism that is different from the one-stage event generation definition depending on the mechanism of the position information acquisition unit, complex events with conditions actually required by various applications are provided. Can be defined at low cost.

  In this embodiment, the notification destination is not limited to an application, and any information can be set as a notification destination as long as it can send and receive information about devices and processes connected via processes and networks. May be.

  In this embodiment, the two-stage event generation, that is, the basic event and the application event is performed as described above, thereby enabling output of notification information based on complicated conditions. As a result, the application that receives the notification information is not required to perform processing of managing, analyzing, and processing the input notification information to extract optimum information, thereby reducing the processing load.

  Furthermore, since only the optimal information when the two-stage conditions are met is notified, information that is not required by the application is not notified, and the processing load on the application is reduced. Network traffic is also reduced. Furthermore, when an application developer develops an application based on notification information, it is not necessary to create a program for executing complicated processing, and the burden is reduced.

  Further, when setting complicated conditions in one stage, it is necessary to perform complicated processing such as preparing a macro or the like, but in this embodiment, complicated conditions are set in two stages. This makes it possible to easily set complicated conditions.

  In addition, since the present invention is an event generation method that is not limited to the position information server described above, it is possible to construct an advanced event processing system that uses existing information notification processing. In the position information management system as well as the position information management server using the active tag of the present embodiment, it can be applied to, for example, a position acquisition service using a mobile terminal or a position information management system such as GPS. is there.

  Furthermore, not only the position information management device but also any device that performs notification according to the occurrence or change of an event can be applied. For example, a device that sets two or more event generation conditions based on information detected from a sensor installed to measure the occurrence of an event and outputs notification information when these conditions are satisfied It is also possible to apply.

  FIG. 19 is a diagram illustrating a hardware configuration of a PC that executes a program for realizing the functions of the location information management server 100. The location information management server 100 of this embodiment includes a control device such as a CPU (Central Processing Unit) 1901, a storage device such as a ROM (Read Only Memory) 1902 and a RAM (Random Access Memory) 1903, and an HDD (Hard Disk). Drive), an external storage device 1904 such as a CD (Compact Disk) drive device, a display device 1907 such as a display device, a communication interface 1906 connected to a network, and an input device 1905 such as a keyboard and a mouse are connected. A bus 1908 is provided and has a hardware configuration using a normal computer.

  The notification processing program executed by the location information management server 100 of the present embodiment is a file in an installable or executable format, and is a CD-ROM, flexible disk (FD), CD-R, DVD (Digital Versatile Disk). Or the like recorded on a computer-readable recording medium.

  Further, the notification processing program executed by the location information management server 100 of the present embodiment may be stored on a computer connected to a network such as the Internet and provided by being downloaded via the network. . In addition, the notification processing program executed by the location information management server 100 of the present embodiment may be provided or distributed via a network such as the Internet.

  Further, the notification processing program according to the present embodiment may be provided by being incorporated in advance in a ROM or the like.

  The notification processing program executed by the location information management server 100 according to this embodiment includes the above-described units (reception processing unit, tag information management unit, location information acquisition unit, basic event generation unit, applied event generation unit, notification information generation). Module, a notification processing unit, and an event editing reception unit). As actual hardware, the CPU reads the notification processing program from the recording medium and executes the notification processing program. The reception processing unit, the tag information management unit, the position information acquisition unit, the basic event generation unit, the applied event generation unit, the notification information generation unit, the notification processing unit, and the event edit reception unit are generated on the main storage device. It has become.

As described above, the information management apparatus, the position information management apparatus, the information management method, the information management program, the computer-readable recording medium, and the position information management system according to the present invention provide information to other applications, processes, or apparatuses. It is useful as a technique for notifying, and is particularly suitable for a technique for managing position information of an object using a tag or the like and notifying based on the managed information.

It is a block diagram which shows the structure of the positional infomation management system concerning embodiment. It is explanatory drawing shown notionally of the whole structure of the positional information management server. It is the figure which showed the structure of the reader position management table concerning embodiment. It is the figure which showed the structure of the tag signal management table concerning embodiment. It is the figure which showed the structure of ID position information management table concerning embodiment. It is the figure which showed the structure of the basic event management table concerning embodiment. It is the figure which showed the structure of the applied event management table concerning embodiment. It is the figure which showed the list of the applied events registered as a record in the applied event management table concerning embodiment. It is the figure which showed the structure of the event state management table concerning embodiment. It is the figure which showed the structure of the area table concerning embodiment. It is the figure which showed the structure of the ID information management table concerning embodiment. It is the figure which showed the structure of the filter table concerning embodiment. It is explanatory drawing which showed an example of the correlation of the positional information etc. which are input from the positional information acquisition part concerning embodiment, and the event produced | generated by a basic event production | generation part. It is the figure which showed an example of the record registered into an event state management table, when the 'STAY_AREA' event is produced | generated by the application event production | generation part of the location information management server concerning embodiment. It is the figure which showed an example of the event state management table by which the 'LEAVE' event produced | generated by the application event production | generation part of the location information management server concerning embodiment was hold | maintained. It is a flowchart which shows the procedure of a process from receiving information, such as ID, from the reader in the positional information management server concerning this Embodiment until notifying notification information to an application. It is a flowchart which shows the procedure of the process after outputting the basic event produced | generated after the positional information etc. in the basic event production | generation part 104 concerning this Embodiment were input. It is a flowchart which shows the procedure of the process from the reception of the input of the basic event in the applied event generation part 105 concerning this Embodiment to outputting the input basic event and the generated applied event. It is the figure which showed the hardware constitutions of PC which performed the program for implement | achieving the function of a positional information management server.

Explanation of symbols

DESCRIPTION OF SYMBOLS 100 Position information management server 101 Storage part 102 Reception processing part 103 Position information acquisition part 104 Basic event generation part 105 Applied event generation part 106 Notification information generation part 107 Notification processing part 108 Event edit reception part 109 Tag information management part 111 Position information database 112 Basic Event Database 113 Applied Event Database 114 Filtering Database 151a-n Reader 161a-n Active Tag 201 Application A
202 Application B
203 Application C
204 Application D
1301, 1302, 1303 Event generation time 1901 CPU
1902 ROM
1903 RAM
1904 External storage device 1905 Input device 1906 Communication interface 1907 Display device 1908 Bus

Claims (6)

An information management device connected to a detection device for managing information on a target event and detecting a portable information storage medium installed in the target,
Stores notification rule information for specifying a notification type indicating the type of information to be notified based on predetermined information including identification information for specifying the detection device and signal strength of a signal from a portable information storage medium First storage means to
Receiving means for receiving predetermined information from the detection device and associating the predetermined information with detection time information indicating a time at which the predetermined information was received ;
Wherein stored in the second storage means, based on a change of the predetermined information with the passage of the detection time information, notification type is specified according to the notification rule information, a first notification information, the detection The second notification information of a notification type that is generated and stored including time information, and that is specified based on the stored first notification information and a notification rule predetermined for the first notification information. Generating means including the detection time ;
Third storage means for storing destination information for transmitting an application or process as a destination and a notification type that is a type of information to be notified to the application or process;
The second notification information generated by the generation unit is notified to the transmission destination indicated by the transmission destination information associated with the notification type of the second notification information by the third storage unit. Notification means;
An information management device comprising: In a position information management device that manages position information of an object that can be identified by a detection device detecting a portable information storage medium provided in the object,
Identifying a notification type indicating a type of information to be notified regarding the position of the object based on predetermined information including identification information for identifying the detection device and signal strength of a signal from a portable information storage medium; First storage means for storing notification rule information;
A predetermined information is received from the detection device, and position information indicating the position of the portable information storage medium based on the predetermined information is associated with detection time information indicating a time when the predetermined information is received. Two storage means, holding reception means,
The first notification information of the notification type specified in accordance with the notification rule information based on the change of the position information with the passage of the detection time information held in the second storage means is the detection time. The second notification information of the notification type specified based on the first notification information held and the notification rule predetermined for the first notification information is generated and held including information. Generating means including the detection time ;
Third storage means for storing destination information for transmitting an application or process as a destination and a notification type that is a type of information to be notified to the application or process;
The second notification information generated by the generation unit is notified to the transmission destination indicated by the transmission destination information associated with the notification type of the second notification information by the third storage unit. Notification means;
A position information management device comprising: An information management method executed by an information management device connected to a detection device for managing information on a target event and detecting a portable information storage medium installed in the target,
The information management device specifies a notification type indicating a type of information to be notified based on predetermined information including identification information for specifying the detection device and signal strength of a signal from a portable information storage medium First storage means for storing notification rule information;
Second storage means for storing the predetermined information in association with detection time information indicating a time when the predetermined information is received;
Third storage means for storing destination information for transmitting an application or process as a destination and a notification type that is a type of information to be notified to the application or process;
A receiving step in which receiving means receives predetermined information from the detection device and associates the predetermined information with detection time information indicating a time at which the predetermined information is received, and holds it in a second storage means ; ,
Generating means, the held in the second storage means, on the basis of the change of the predetermined information over the course of a detection time information, notification type is specified according to the notification rule information, a first notification information the, generates and holds including the detection time information, notification type specified based on the predetermined notification rules for said stored first notification information and the first notification information, the first A generation step of generating the notification information of 2 including the detection time ;
The notification means transmits the second notification information generated in the generation step by the transmission destination information associated with the notification type of the second notification information in the third storage means. A notification step to notify first,
An information management method characterized by comprising:   An information management program for causing a computer to execute the information management method according to claim 3.   A computer-readable recording medium storing the information management program according to claim 4. A portable information storage medium provided in an object existing in an area from which position information is to be acquired; a detection device that detects the portable information storage medium in a non-contact manner with the portable information storage medium; In addition, a position information management system that manages position information for managing position information of an object including the portable information storage medium,
The location information management device
Identifying a notification type indicating a type of information to be notified regarding the position of the object based on predetermined information including identification information for identifying the detection device and signal strength of a signal from a portable information storage medium; First storage means for storing notification rule information;
Receiving means for receiving predetermined information from the detection device and associating the predetermined information with detection time information indicating a time at which the predetermined information was received ;
Wherein stored in the second storage means, based on a change of the predetermined information with the passage of the detection time information, notification type is specified according to the notification rule information, a first notification information, the detection The second notification information of a notification type that is generated and stored including time information, and that is specified based on the stored first notification information and a notification rule predetermined for the first notification information. Generating means including the detection time ;
Third storage means for storing destination information for transmitting an application or process as a destination and a notification type that is a type of information to be notified to the application or process;
The second notification information generated by the generation unit is notified to the transmission destination indicated by the transmission destination information associated with the notification type of the second notification information by the third storage unit. Notification means;
A location information management system characterized by comprising:

Images