JP5320978B2 - Context generation device, system, program, and method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To solve the problem that a system cannot acquire various kinds of contexts about an entity from contexts of other adequate entities which conform to the kinds of the contexts. <P>SOLUTION: A context-generating device 11 includes: a management part 25 which stores management tables which are provided to correspond to entities and each store contexts and relations which include the designation of other entities and related kinds (R category); and a generation part which inputs the identification information of the first entity and the kinds (C category) of the contexts, and traces the relation of a selected R category, beginning from the management table of the first entity, on the basis of the input C category to search the management table of the second entity, and then generates the contexts of the first entity on the basis of the contexts stored in the management table concerned. <P>COPYRIGHT: (C)2010,JPO&amp;INPIT

Description

  The present invention relates to a context generation device, system, program, and method.

  Patent Document 1 describes a context providing device. The context is information representing the status of a certain target (person, thing, etc.). The context is, for example, the position of a person, the state of the person (during a telephone call / meeting, etc.), the inventory status of an object, and the temperature to be managed in a room or furnace. The apparatus of Patent Literature 1 generates a context of a target to be acquired from a target context different from a target for which a context is to be acquired using a relationship between the targets.

  The apparatus stores the relationship between objects as a link. For example, the person 1 and the context of the mobile phone 1 carried by the person 1 are linked semi-fixedly. The context of the automobile 1 and the RFID tag 1 mounted on the automobile 1 is fixedly linked. Further, when the person 1 gets into the car 1, the RFID reader included in the mobile phone 1 carried by the person 1 reads the RFID tag 1 mounted on the car 1, and between the context of the mobile phone 1 and the RFID tag 1. A link is temporarily established.

  When the position context of the person 1 is requested, the apparatus uses the link of the person 1 for the context of the mobile phone 1, uses the link of the mobile phone 1 for the context of the RFID tag 1, and the RFID tag 1 The link is used to sequentially search the context of the automobile 1. Then, the apparatus acquires position information from the context of the automobile 1 and outputs the position information as the position information of the person 1. The vehicle 1 is equipped with a GPS (Global Positioning System) position detection device, and position information acquired by the device is stored as a context of the vehicle 1.

  In Patent Document 2, the monitoring / support unit in the vicinity of the stairs detects the RFID tag of the elderly person, performs a relationship such as “I am going down the stairs”, and makes a support decision based on information about the elderly person and the stairs. The automatic support system to perform is described.

  Patent Document 3 describes a communication node that writes / reads relationship information between objects in a storage area in response to a request from an application or another node. In the node, the application specifies relationship information to be read / written.

  Patent Document 4 describes an RFID management apparatus that groups RFID (Radio Frequency Identification) related information into groups based on tag reading locations and times and stores them in a storage unit. The apparatus uses the grouping information to extract RFID related information within the input location and time range.

JP 2005-293012 A JP 2007-025854 A JP 2007-116640 A JP 2008-112263 A

  The technology of the above patent document has a problem that various types of contexts for entities (such as people, things, or parts thereof) cannot be generated from the contexts of other appropriate entities according to the type of context. .

  The device of Patent Literature 1 does not consider the type of relationship between entities that can be used, depending on the type of context. Thus, the device may obtain context using inappropriate entity relationships.

  If the desired context is position information, it may be appropriate to output the position information of the car as the position information of the person using the relationship “a person is in the car”. However, for example, if the context is impact information, it is not necessarily appropriate to output the vehicle impact information as human impact information using the relevant relationship. This is because the person and the car may not be in direct contact (for example, the person is sitting on a cushioned chair that absorbs shock).

  Patent Documents 2 to 4: Since the context information of an entity is not acquired from another entity, the above-described problem is not solved.

  The objective of this invention is providing the context production | generation apparatus, system, program, and method which solve the above-mentioned subject.

  A context generation apparatus according to an embodiment of the present invention is provided for an entity, and stores a management table that stores a context and a management table that stores associations including other entity designations and association types (R types), respectively. The identification information of the first entity and the context type (C type) are input, and the relation of the R type selected based on the input C type is started from the management table of the first entity. The management table of the second entity is searched, and a generation unit that generates the context of the first entity based on the context stored in the management table is provided.

  A context generation program according to an embodiment of the present invention is provided for an entity, and includes a management unit that stores a management table that stores contexts and associations including other entity designations and association types (R types). The identification type of the first entity and the type of context (C type) are input, and the R type selected based on the input C type starting from the management table of the first entity The management table of the second entity is searched by tracing the association of the first entity, and a generation process for generating the context of the first entity is executed based on the context stored in the management table.

  A context generation method according to an embodiment of the present invention is a computer provided with a management unit that stores a management table that stores associations including contexts and other entity designations and association types (R types). Is selected based on the input C type based on the input process of inputting the identification information of the first entity and the type of context (C type), and the management table of the first entity. It has a generating step of searching the management table of the second entity by tracing the association of the R type and generating the context of the first entity based on the context stored in the management table.

  The context generation device according to the present invention can acquire various types of contexts for an entity from the contexts of other appropriate entities according to the type of the context.

  FIG. 1 shows the configuration of a context generation system 10 according to the first embodiment of the present invention. The context generation system 10 includes a context generation device 11, a sensor 13, a tag reader 15, a management terminal 16, and a user terminal 17 connected to a network 18.

  The sensor 13 is a device that outputs measurement values of the outside world such as an infrared sensor, a position sensor, a thermal sensor, a vibration sensor, and a sound sensor. The sensor 13 is attached to the entity 12 and generates a context 36 of the entity 12. Here, “attach” refers to mounting, sticking, hanging, arrangement in the vicinity, and the like. Which form is taken is appropriately selected according to the properties of the entity 12 and the sensor 13 and the usage environment. For example, when it is desired to measure the temperature of the box, a thermal sensor is attached to the outer surface of the box, but when it is desired to measure the environmental temperature, the thermal sensor is placed on the shelf of the box (arranged in the vicinity of the box).

  The entity 12 is a subject that can generate situation information, such as a person, a thing, or a part thereof. The context 36 is status information of the entity 12.

  The entity 12 is, for example, an operator, a driver, a product, a car, or the like. One person or one thing may be associated with a plurality of entities 12. A person's right hand and left hand may be associated with separate entities 12, and the inside and outside of the box may be associated with separate entities 12. Some of the people or things that can generate different contexts 36 may be managed as separate entities 12. The context 36 is, for example, a person's position, a person's state (during a telephone call / meeting, etc.), an inventory status of an object, and a room or furnace management target temperature.

  An ID tag 14 or a tag reader 15 may be attached to the entity 12 and used to set the relationship 3b between the entities 12. The ID tag 14 is an RFID tag (Radio Frequency IDentification) or the like. The tag reader 15 is an RFID reader or the like. The ID tag 14 may be a barcode label, and the tag reader 15 may be a barcode reader.

  FIG. 2 shows a configuration of the context generation device 11. The context generation device 11 includes a generation unit 20, a processing unit 23, and a registration unit 27. The context generation device 11 holds a data list 21 and a searched related list 22 on a memory (not shown). The context generation device 11 includes a search rule holding unit 24, a management unit 25, and an association rule holding unit 26 on a storage device such as a disk device. The management unit 25 stores a management table 30 corresponding to the entity 12.

  The generation unit 20 inputs a context request 28 from the user terminal 17 and outputs a context 36. The processing unit 23 inputs the information of the ID tag 14 attached to the entity 12 from the tag reader 15 or inputs the measurement value from the sensor 13 to attach the relation 3b between the entities 12. The registration unit 27 inputs setting information and correction information from the management terminal 16 and registers and corrects the management table 30 of the management unit 25. The processing unit 23 and the registration unit 27 may be distributed and arranged in devices outside the context generation device 11. The processing unit 23 and the registration unit 27 do not have to exist when the entity 12 or the relationship 3b thereof is fixed.

  The generation unit 20, the processing unit 23, and the registration unit 27 are realized by hardware. The generation unit 20, the processing unit 23, and the registration unit 27 may be realized by executing a context generation program 29 on a memory (not shown) by a processor (not shown) of the context generation device 11 that is also the computer 19.

  FIG. 3 shows the configuration of the management table 30. The management table 30 stores an entity A ID 31, type (E type 32), tag ID 33, reader ID 34, C information 3 a, and association 3 b corresponding to the entity 12 (for example, entity A).

  The E type 32 indicates the type of the entity A (person, product, car, etc.). The tag ID 33 stores the identification information when the ID tag 14 is attached to the entity A. The reader ID 34 stores the identification information when the tag reader 15 is attached to the entity A. A plurality of ID tags 14 and tag readers 15 may be attached to the entity A. In this case, a plurality of tag IDs 33 and reader IDs 34 may be stored. When the ID tag 14 and the tag reader 15 are not attached to the entity 12, the tag ID 33 and the reader ID 34 store Null.

  A plurality of entities 12 (for example, the outside of the box and the inside of the box) may share the same ID tag 14 or tag reader 15. In this case, the same tag ID 33 and reader ID 34 are stored in the plurality of management tables 30.

  The C information 3a describes the situation related information of the entity A. The C information 3a includes a sensor ID 35, a context 36, and a C type 37. The context 36 stores the status information of the entity A. The C type 37 indicates the type of the context 36 (temperature, impact, enrollment / seating status, etc.). The sensor ID 35 is identification information of the sensor 13 for acquiring the context 36. When the entity 12 has a plurality of types of contexts 36, a plurality of C information 3a exists corresponding to the entity A. When the context 36 is not acquired from the sensor 13, for example, when input from the management terminal 16, the sensor ID 35 stores Null. A plurality of entities 12 may share the same sensor 13. In this case, the same sensor ID 35 is stored in the plurality of management tables 30.

  Association 3b describes the relationship that entity A has to other entities 12. The association 3b includes an R type 38 and another entity designation 39. The other entity designation 39 is pointer information for the other entity 12 (for example, the address of the management table 30 corresponding to the other entity 12). The R type 38 indicates the type of relationship with respect to another entity 12. When entity A has a plurality of relationships, a plurality of associations 3b exist for entity A. When entity A has no relationship with other entities 12, association 3b stores Null.

  When the generation unit 20 is requested to generate the context 36 of an entity 12 (entity A), the generation unit 20 may generate the context 36 of another entity 12 (entity B) by following the relationship 3b starting from the entity A. is there. At this time, if the pointer information to the entity B is stored in the other entity designation 39 of the management table 30 of the entity A, the generation unit 20 directly searches the management table 30 of the entity B by following this pointer information. . Pointer information to the entity C is stored in the other entity designation 39 of the management table 30 of the entity A,. . In some cases, pointer information to the entity B is stored in the other entity designation 39 of the management table 30 of the entity D. In this case, the generation unit 20 traces the pointer information, and from entity A to entity C,. . . The management table 30 of entity B is searched via D.

FIG. 4 shows the configuration of the context request 28. The context request 28 includes ID 31 and C type 37. This ID 31 indicates the target entity 12 of the context request 28. The C type 37 indicates the type of the context 36 to be acquired for the target entity 12. FIG. 5 shows the configuration of data stored in the association rule holding unit 26. The association rule holding unit 26 stores one or a plurality of association rules 40. The association rule 40 includes a type pair 41 and a setting type 42. The type pair 41 stores an E type 32 pair. The setting type 42 stores the type (R type 38) of the association 3b set between the two entities 12 having the E type 32 of each type pair 41. The R type 38 includes, for example, “attach” indicating the close arrangement of the two entities 12, “nearby” indicating the contact arrangement, and “in” indicating the peripheral arrangement.

  According to FIG. 5, the first association rule 40 stipulates that, for example, an association 3b having an R type 38 of “near” is set between two entities 12 having an E type 32 of a track and a product. This corresponds to the product being placed on the truck and brought into contact. The second association rule 40 stipulates that, for example, an association 3b in which the R type 38 is in is set between the two entities 12 in which the E type 32 is a truck and a person. This corresponds to a person getting on the truck and in a peripheral arrangement state. A person is standing on a flexible foot on a track or sitting on a chair with good cushioning properties, so that the person is not in direct contact. Similarly, the third association rule 40 stipulates that, for example, an association 3b whose R type 38 is near is set between two entities 12 whose E type 32 is a product. The product corresponds to the case where the product is brought into contact by being stacked or placed side by side.

  Note that the context generation device 11 may not include the association rule holding unit 26 and may hold data corresponding to the association rule 40 in the processing unit 23 in a fixed manner.

  FIG. 6 shows a configuration of data stored in the search rule holding unit 24. The search rule holding unit 24 stores one or a plurality of search rules 43. The search rule 43 includes a request specification 44 and a search related specification 45. The request specification 44 stores one or a plurality of C types 37. The search relation specification 45 stores one or a plurality of R types 38.

  The generation unit 20 acquires the search rule 43 based on the C type 37 specified in the context request 28, traces the relationship 3b of the R type 38 described in the search related specification 45 of the search rule 43, and obtains the context 36. Is generated.

  In the first search rule 43 of FIG. 6, when any of position, temperature, gas concentration, and humidity is designated as the C type 37 of the context request 28, the generation unit 20 sets the R type 38 to attach, nearby, in It is stipulated that any of the relations 3b may be traced. In the second search rule 43, when either impact or acceleration is specified by the context request 28, the generation unit 20 may follow any relation 3b in which the R type 38 is attached or near, but the R type 38 stipulates that there is no trace of the association 3b of in. In the third search rule 43, when any of heart rate, pressure, and illuminance is designated by the context request 28, the generation unit 20 may follow the association 3b where the R type 38 is attached. Stipulates that there is no trace of the relationship 3b between near and in.

  In addition, for a certain type of association 3b (for example, near), the number of times of tracing can be specified by the search rule 43 or the like. This is because depending on the type of the context 36, the number of entities 12 to which the context 36 is propagated through the association 3b may be limited. Note that the number of times of tracing (the number of hops) refers to the number of management tables 30 through which the management table 30 for obtaining the context 36 is accessed from the management table 30 serving as the starting point.

    The context generation device 11 may not include the search rule holding unit 24. In this case, the context generation device 11 may input the search rule 43 from the user terminal 17 or may hold data equivalent to the search rule 43 inside.

  FIG. 7 is an operation flowchart of the registration unit 27. The registration unit 27 inputs a request to create or modify the management table 30 from the management terminal 16 (S1). If the input is a creation request (Y in S2), the same unit reserves a new management table 30 area in the management unit 25 and performs initial setting (setting of a null value) (S3). Subsequently, the registration unit 27 stores the ID 31 and the E type 32 in the management table 30 created by inputting from the management terminal 16 (S4). If any of the tag ID 33, reader ID 34, C information 3a, and related 3b information is input from the management terminal 16, the same unit stores the information in the created management table 30 (S5) and ends the process. To do. Here, the tag ID 33, the reader ID 34, the C information 3a, and the related 3b information input from the management terminal 16 are fixed information about the entity 12, for example.

  When the input is a correction request (N in S2), the registration unit 27 inputs the ID 31 from the management terminal 16 and acquires the management table 30 storing the ID 31 (S6). Thereafter, the same unit inputs correction information from the management terminal 16, corrects the contents of the searched management table 30 (S7), and ends the process.

  For example, when the ID tag 14, the tag reader 15, and the sensor 13 are attached to or removed from the entity 12, the tag ID 33, the reader ID 34, and the sensor ID 35 are corrected. For example, when a semi-fixed relationship with another entity 12 is set, the relationship 3b is corrected. Furthermore, for example, when the situation information that does not depend on the sensor 13 occurs, the context 36 is corrected. The situation information that does not depend on the sensor 13 occurs when the delivery person inputs from the portable terminal as the management terminal 16 that the delivery of the parcel delivery package as the entity 12 has been completed.

  FIG. 8 is an operation flowchart of the processing unit 23. The processing unit 23 starts operation when data is input from the sensor 13 or the tag reader 15. For example, the sensor 13 periodically transmits the sensor ID 35 and the measurement value to the processing unit 23. For example, when the transmission information of the ID tag 14 is detected (when it appears) or when the transmission information of the ID tag 14 is no longer detected (when it disappears), the tag reader 15 notifies the processing unit 23 of the appearance or disappearance. The tag reader 15 notifies the processing unit 23 of the tag ID 33 and the reader ID 34 as appearance data or disappearance data.

  When data is input from the sensor 13 (N in S10), the processing unit 23 acquires all the management tables 30 having the sensor ID 35 that matches the input sensor ID 35 (S11). The same unit stores the input measurement values in the contexts 36 of all the acquired management tables 30 (S12). More precisely, the same unit stores the measurement value in the context 36 of the C information 3 a having the sensor ID 35 that matches the input sensor ID 35 in the management table 30.

  When the appearance data is input from the tag reader 15 (Y in S10 and Y in S13), the processing unit 23 acquires all the management table 30 (management table A) having the tag ID 33 that matches the input tag ID 33 ( S17). Further, the same unit acquires all the management tables 30 (management table B) having the reader ID 34 that matches the input reader ID 34 (S18).

  The same unit sets a relation 3b for all combinations of the acquired management table A and management table B (S19 to S1C). Specifically, the same unit compares the two E types 32 acquired from the sequentially selected management tables A and B with the type pair 41 of the association rule holding unit 26 and acquires an association rule 40 that matches (S19). . The processing unit 23 acquires the R type 38 to be set from the setting type 42 of the acquired association rule 40 (S1A). The same part sets the acquired R type 38 in the R type 38 of the management table A and the address of the management table B in the other entity designation 39 (S1B). The same part sets the acquired R type 38 in the R type 38 of the management table B, and sets the address of the management table A in the other entity designation 39 (S1C).

  When erasure data is input from the tag reader 15 (Y in S10 and N in S13), the processing unit 23 acquires all of the management table 30 (management table C) having the tag ID 33 that matches the input tag ID 33 ( S14). Furthermore, the same unit acquires all the management tables 30 (management table D) having the reader ID 34 that matches the input reader ID 34 (S15). The same part deletes the mutual relation 3b (sets a Null value) for all combinations of the acquired management table C and management table D (S16).

  For example, when the tag reader 15 detects the transmission information of the ID tag 14 (when it appears), the tag reader 15 notifies the processing unit 23 of the appearance, but when it does not detect the transmission information of the ID tag 14 (when it disappears). May be configured not to notify the disappearance. In this configuration, the processing unit 23 may process the received data as having been received when the appearance data is received in a state of being related between the entities 12. For example, a tag reader 15 is installed at the entrance of a truck or a warehouse, and when the ID tag 14 attached to the product is read at the time of carrying in, it is interpreted as appearance data, and when it is read again at the time of carrying out, it is interpreted as lost data. It means to cancel the association.

  In this case, for example, after acquiring the R type 38 to be set (S1A), the processing unit 23 checks whether the association 3b of the R type 38 is set between the management tables A and B. If already set (Y in S1Z), the related 3b may be deleted (after S14).

  FIG. 9 is an operation flowchart of the generation unit 20. The generation unit 20 first inputs a context request 28 from the user terminal 17 (S20), and initializes (sets a null value) the data list 21 and the inspected related list 22 as work areas (S21).

  FIG. 10 shows the configuration of the data list 21. The data list 21 is an area including one or a plurality of contexts 36 found in the scanning process when the management table 30 is scanned following the association 3b.

  FIG. 11 shows the structure of the inspected related list 22. The inspected association list 22 is an area that can include one or more associations 3b that have already been scanned when the management table 30 is scanned by following the associations 3b. The inspected association list 22 is provided to prevent double scanning of the association 3b. The inspected relation list 22 stores the relation 3b (R type 38 and other entity designation 39) stored in the management table 30 in association with the ID 31 of the management table 30.

  Next, the generation unit 20 acquires all the management table 30 (management table A) having the ID 31 input by the context request 28 (S22). The same part searches the search rule holding unit 24 and acquires the search rule 43 (search rule A) having the C type 37 input by the context request 28 in the request specification 44 (S23).

  The generation unit 20 searches the context 36 starting from the management table A (S24). That is, the same section starts from the management table A, and enters the context of the input C type 37 from the management table 30 searched by following the relationship 3b of the R type 38 in the range defined by the search related specification 45 of the search rule A. 36 is added to the data list 21 (details will be described later).

  When the scanning is completed and the context 36 is stored in the data list 21 (Y in S25), the same section outputs the context 36 (S26) and ends the process.

  When the scanning is completed and the context 36 is not stored in the data list 21 (N in S25), the same unit outputs a notification that “there is no requested context” (S27) and performs the processing. finish.

  When a plurality of contexts 36 are stored in the data list 21, the same unit may output an average value of the plurality of contexts 36 as the context 36. The same unit may calculate an average value by excluding a particularly large or small value from the plurality of contexts 36. The same unit may output the maximum value or the minimum value as the context 36 from the plurality of contexts 36. Further, the same unit may output a notification that “there is no requested context” when the number of the plurality of contexts 36 is equal to or less than a predetermined value or when the variance of the values is larger than a predetermined value.

  FIG. 12 is a flowchart of the search process of the context 36 starting from the management table A by the generation unit 20. If the input context 36 of type C 37 exists in the management table A, the generation unit 20 adds it to the data list 21 (S30). The generation unit 20 scans the management table 30 by tracing all the relations 3b of the management table A (S31 to S35).

  Specifically, the generation unit 20 takes out the R type 38 of the association 3b that is sequentially selected, and checks whether the R type 38 is included in the search relation designation 45 of the search rule A (S31). If it is included (Y in S31), the same part checks whether the relevant 3b has already been scanned (S32). This is performed by checking whether the ID 31 of the management table A and the related 3b are already registered in the checked related list 22.

  If it has not been scanned (N in S32), the same part registers the ID 31 of the management table A and the related 3b in the checked related list 22 (S33). Thereafter, the same part acquires the management table 30 (new management table A) of the other entity 12 related by following the other entity designation 39 of the related 3b (S34).

  Then, the same part searches the context 36 starting from the new management table A (S35), and ends the process. The search processing for the context 36 starting from the new management table A is realized by recursively calling the processing in this figure.

  FIG. 13 shows a first application example (situation 1) of the context generation system 10. In this example, the entity 12 is a product 1 and a product 2 (E type 32 is a product), person 1 (E type 32 is a person), heart rate monitor 1 (E type 32 is a heart rate monitor), track 1 (E Type 32 is a track). The product 1 includes an RFID tag 1 (ID tag 14) and a temperature sensor 1 (sensor 13). The product 2 includes an RFID tag 2. The person 1 includes an RFID tag 3. The heart rate monitor 1 includes a heart rate sensor (sensor 13). The truck 1 has a gate provided with RFID readers 1 and 2 (tag reader 15) at the load / unload port. A heart rate monitor 1 is in close contact with the person 1. The person 1 holds the products 1 and 2 and stands in front of the loading / unloading exit of the truck 1.

  FIG. 14 shows a management table 30 corresponding to the first adaptation case (situation 1). In the management unit 25, a management table 30 corresponding to each entity 12 is created. In addition, between the person 1 and the heart rate monitor 1, an association 3b (F-a, b) in which the R type 38 is attach is set. For example, the administrator of the context generation system 10 registers these pieces of information in the management unit 25 from the management terminal 16 via the registration unit 27.

  FIG. 15 shows a first adaptation case (situation 2) of the context generation system 10. In this situation, the person 1 gets into the truck through the gate while holding the goods 1 and 2, and places the goods 1 and 2 on the truck 1 (approaching arrangement). The person 1 stands with his / her feet capable of absorbing vibration in the track 1, and is arranged around from the viewpoint of the context 36 such as vibration.

  FIG. 16 shows the management table 30 corresponding to the first adaptation case (situation 2). When a person 1 wears a heart rate monitor 1 and passes through the gate while holding the products 1 and 2, the RFID reader 1 or 2 of the gate reads the identification information of the RFID tags 1, 2, and 3, and reads the read data. Output to the processing unit 23. In response to this, the processing unit 23 sets a new association 3b. It is assumed that the RFID readers 1 and 2 at the gate are arranged at a distance where the information of the same ID tag 14 is not read repeatedly.

  When the identification information of the RFID tag 1 is input from the tag reader 1 or 2, the processing unit 23 sets an association 3 b with an R type 38 of “near” between the track 1 and the product 1 according to the association rule 40 (r 1 -a, b). When the identification information of the RFID tag 2 is input from the tag reader 1 or 2, the processing unit 23 sets an association 3b of R type 38 near between the track 1 and the product 2 according to the association rule 40 (r2-a, b). When the identification information of the RFID tag 3 is input from the tag reader 1 or 2, the processing unit 23 sets an association 3b in which the R type 38 is in between the track 1 and the person 1 according to the association rule 40 (r3-a, b).

Further, the temperature sensor 1 and the heart rate sensor 1 regularly output measurement values to the processing unit 23. When these measurement values are input, the processing unit 23 stores a context 36 corresponding to each sensor ID 35 (r4, r5).
In this state, the heart rate of the person 1 is obtained as follows. The generation unit 20 inputs a context request 28 for designating the person 1 (ID 31) and the heart rate (C type 37). The generation unit 20 accesses the management table 30 of the person 1 using the ID 31 as a key. The person 1 has two R types 38 of “in” and “attach” as associations 3b (Fa and r3-b). In accordance with the search rule 43, the generation unit 20 manages the heart rate monitor 1 by following the association 3b (F-a) in which the R type 38 is not attached but following the association 3b (F3-a) in which the R type 38 is attach From Table 30, the context 36 (r5) of the C type 37 heart rate is obtained.

  On the other hand, the temperature of the person 1 is obtained as follows. The generation unit 20 inputs a context request 28 for designating person 1 (ID 31) and temperature (C type 37). The generation unit 20 accesses the management table 30 of the person 1 using the ID 31 as a key. The person 1 has two R types 38 of “in” and “attach” as associations 3b (F-a and r3-b). The generation unit 20 accesses the management table 30 of the track 1 following the related 3b (r3-b) in which the R type 38 is in according to the search rule 43. Thereafter, the same section further follows the near 3 relationship (r1-a) of the track 1 and obtains the context 36 (r4) in which the C type 37 is the temperature from the management table 30 of the product 1.

  The generation unit 20 accesses the management table 30 of the heart rate monitor 1 by following the association 3b (F-a) of attach according to the search rule 43. However, the heart rate monitor 1 does not have the temperature context 36, and the relationship to be followed elsewhere. Since there is no 3b, the scanning in this direction is finished without obtaining the temperature. The generation unit 20 also accesses the management table 30 of the product 2 by following the near 3b (r2-a) of the track 1, but the product 2 does not have the temperature context 36 and the other relationship to be traced. Since there is no 3b, the scanning in this direction is finished without obtaining the temperature.

  The context generation system 10 of the present embodiment can acquire various C-type 37 contexts 36 for the entity 12 from the contexts 36 of other appropriate entities 12 corresponding to the C-type 37 of the context 36 (first effect). ). In the above application case, the context generation system 10 obtains the heart rate context of the person 1 entity from the heart rate entity while the temperature context is obtained from the commodity 1 entity even for the same person 1 entity. Yes.

  The reason why this effect is obtained is that the relationship 3b having the R type 38 is set between the entities 12, and the context 36 of the other entity 12 is accessed by following the relationship 3b of the R type 38 selected according to the C type 37. Because it does.

  The second effect is that a highly reliable context 36 can be acquired. The reason is that the context generation device 11 acquires the context 36 of the type C 37 to be obtained from the plurality of entities 12 and calculates the average value after excluding a particularly large or small value. Is output. By using a plurality of information sources, the reliability of the acquired context 36 can be improved.

  A third effect is that the entity 12 can be flexibly defined (corresponding to an object in the real world). The reason is that the entity 12 can have and share the ID tag 14 and the sensor 13 separately. For example, the box can have the ID tag 14 on the outer surface and the sensor 13 (for example, a thermometer) separately on the outer surface and the inner surface. In this way, the context generation device 11 can manage the inside and outside of the box as separate entities 12. The apparatus can separately manage the internal temperature and the external temperature of the box while grasping the movement of both entities 12 at the same time.

  A fourth effect is that an association 3b of an appropriate type (R type 38) can be set between the entities 12. The reason is that an appropriate R type 38 relation 3b is set according to the type of entity 12 (E type 32).

  FIG. 17 shows a configuration of the context generation system 10 according to the second exemplary embodiment of the present invention. In the context generation system 10 of the first embodiment, the tag reader 15 of the entity A detects the approach between the entity A and the entity B by inputting information on the ID tag 14 of the entity B. In the context generation system 10 of this embodiment, the tag reader 15 inputs information on the ID tag 14 of the entity A and the ID tag 14 of the entity B at the same time (within the first time), so that the entity A and the entity B Detect approach.

  Except as described below, the context generation system 10 of the present embodiment is the same as the context generation system 10 of the first embodiment. The context generation device 11 of this embodiment holds an R history table 50 in a memory (not shown).

  FIG. 18 shows the configuration of the R history table 50. The R history table 50 stores a time series of input data (reader history 51) from the tag reader 15. The reader history 51 includes an input time 52, a reader ID 34, and a tag ID 33.

  FIG. 19 is an operation flowchart (part) of the processing unit 23 according to the second embodiment. The processing in this figure is inserted between a and b in FIG. At this time, the process between b and c in FIG. 8 (the process according to the first embodiment) may or may not be present. That is, this embodiment may be mounted in parallel with the first embodiment, or may be mounted independently.

  In the present embodiment, when the processing unit 23 inputs the tag ID 33 and the reader ID 34 as appearance data or disappearance data from the tag reader 15, the management table 30 (management table P) having a tag ID 33 that matches the input tag ID 33. Are all acquired (S40). The same unit acquires from the R history table 50 all the reader histories 51 where the difference between the current time and the input time 52 is within the first time and the reader ID 34 matches the input reader ID 34 (S41). ). The processing unit 23 inputs the current time from a timer or the like (not shown).

  The processing unit 23 performs the following processes (S42 to S49) for all acquired reader histories 51. First, the processing unit 23 acquires the tag ID 33 from the sequentially selected reader history 51 (S42), and then acquires all the management tables 30 (management table Q) having the tag ID 33 that matches the acquired tag ID 33 (S42). S43). The same part sets or deletes the association 3b with respect to all combinations of the acquired management table P and management table Q (S44 to S49). Specifically, the same unit compares the two E types 32 acquired from the sequentially selected management tables P and Q with the type pair 41 of the association rule holding unit 26 and acquires an association rule 40 that matches (S44). . The processing unit 23 acquires the R type 38 to be set from the setting type 42 of the acquired association rule 40 (S45). The same part checks whether or not the relation 3b of the R type 38 is set between the management tables P and Q (S46).

  If not already set (N in S46), the same part sets the R type 38 acquired in the R type 38 of the management table P and the address of the management table Q in the other entity designation 39 (S47). The same part sets the acquired R type 38 in the R type 38 of the management table Q, and sets the address of the management table P in the other entity designation 39 (S48).

  If already set (Y in S46), the same part deletes the association 3b between the management tables P and Q (S49).

  FIG. 20 shows a second adaptation case (situation 1) of the context generation system 10. The person 1 holds the product 3 in addition to the products 1 and 2 and stands in front of the loading / unloading exit of the truck 1. Person 1 does not have a heart rate monitor 1. Others are the same as the first adaptation case (situation 1).

  FIG. 21 shows a management table 30 corresponding to the second adaptation case (situation 1). In the management unit 25, a management table 30 corresponding to each entity 12 is created.

  FIG. 22 shows a second adaptation case (situation 2) of the context generation system 10. In this situation, the person 1 gets into the truck through the gate while holding the goods 1, 2 and 3, and places the goods 1, 2 and 3 on the truck 1 (approaching arrangement). The person 1 stands with his / her feet capable of absorbing vibration in the track 1, and is arranged around from the viewpoint of the context 36 such as vibration.

  FIG. 23 shows the management table 30 corresponding to the second adaptation case (situation 2). When a person 1 passes through the gate with goods 1, 2 and 3, the RFID reader 1 or 2 of the gate reads the identification information of the RFID tags 1, 2, 3, and 4, and processes the read data To the unit 23. In response to this, the processing unit 23 sets a new association 3b.

  For example, when the identification information of the RFID tag 2 is received within the first time following the identification information of the RFID tag 1 from the tag reader 1 or 2, the same unit detects the approach of the products 1 and 2, and the association rule 40 In the meantime, the relation 3b in which the R type 38 is near is set (r10). Subsequently, when the identification information of the RFID tag 4 is received within the first time, the processing unit 23 detects the approach of the products 1, 2, and 3, and the products 3, 2, and 3 are detected according to the association rule 40. The relationship 3b in which the R type 38 is near is set between the product 1 and the product 1 (r11, r12). Subsequently, when the identification information of the RFID tag 3 is received within the first time, the processing unit 23 detects the approach of the person 1 and the products 1, 2 and 3, but the association rule 40 (setting type 42 is Null). ), The relationship 3b is not set for the person 1 and any product.

  If the process between b and c in FIG. 8 (the process according to the first embodiment) is also executed, the processing unit 23 also sets the relationship 3b (r1 to r4) with the track 1.

  FIG. 24 shows the management table 30 when the person 1 goes out of the truck 1 through the gate while holding the products 1, 2 and 3. The processing unit 23 deletes the relation 3b between r10 to r12 according to the operation flowchart of FIG. For example, when the processing unit 23 receives the identification information of the RFID tag 2 within the first time following the identification information of the RFID tag 1 from the tag reader 1 or 2, the processing unit 23 performs the following. First, the processing unit 23 tries to set the relationship 3b in which the R type 38 is “near” between the two in accordance with the association rule 40, but detects that the relationship 3b has already been set, and the products 1 and 2 are far away. Therefore, the relationship 3b (r10) between the two is deleted.

  Further, when the process between b and c in FIG. 8 (the process according to the first embodiment) is also executed, the processing unit 23 also deletes the association 3b (r1 to r4) with the track 1.

  When the disappearance of the entity 12 is detected (after S14 in FIG. 8), the processing unit 23 deletes all the related 3b (excluding the related 3b set by the registration unit 27) of the entity 12. May be implemented. That is, the processing unit 23 may delete all the relations 3b set at the time of carry-in at the time of carry-out. In this case, a plurality of entities 12 may be detected simultaneously at the time of carry-out, and in that case, a relationship may be established between these entities 12. In this way, when products 1, 2 and 3 are carried in at the same time and only products 1 and 2 are carried out at the same time, for products 1 and 2, the relationship 3b between products 1 and 2 is deleted. Association 3b can be retained.

  The context generation system 10 according to the present embodiment can set various associations 3b between the entities 12. The reason is that when the tag reader 15 inputs the information of the ID tag 14 of the entity A and the ID tag 14 of the entity B at the same time, the system detects that the entity A and the entity B are approaching and far away, This is because the association 3b is set and deleted.

  FIG. 25 shows a configuration of the context generation system 10 according to the third exemplary embodiment of the present invention. When the sensors 13 of the entities A and B detect the measurement values within the first measurement value at the same time (within the second time), the context generation system 10 of the present embodiment detects the approach between the entities A and B. To do. In addition, the system detects that the entities A and B are far if both sensors 13 simultaneously detect a measurement value greater than or equal to the second measurement value difference.

  Except as described below, the context generation system 10 of this embodiment is the same as that of the first embodiment. The context generation device 11 of this embodiment holds an S history table 70, a measured value difference table 60, and a conversion table 80 in a memory (not shown).

  FIG. 26 shows the configuration of the measurement value difference table 60. The measured value difference table 60 stores a first measured value difference 62 and a second measured value difference 63 for each sensor type 61.

  FIG. 27 shows the structure of the S history table 70. The S history table 70 stores a time series of input data (sensor history 71) from the sensor 13. The sensor history 71 includes an input time 52, a sensor ID 35, a sensor type 61, and a history measurement value 72.

  FIG. 28 shows the configuration of the conversion table 80. The conversion table 80 stores the sensor type 61 corresponding to the sensor ID 35.

  FIG. 29 is an operational flowchart (partial) 1/3 of the processing unit 23 of the third embodiment. The processing in this figure is inserted between d and e in FIG. At this time, there may or may not be a process (a process according to the first or second embodiment) between a and c in FIG. That is, this embodiment may be mounted in parallel with the first or second embodiment, or may be mounted independently.

  In this embodiment, when the sensor ID 35 and the measurement value are input from the sensor 13, the processing unit 23 acquires all of the management table 30 (management table E) having the sensor ID 35 that matches the input sensor ID 35 (S50). . The same unit acquires the sensor type 61 corresponding to the input sensor ID 35 from the conversion table 80. Further, the same unit acquires a first measurement value difference 62 and a second measurement value difference 63 corresponding to the acquired sensor type 61 from the measurement value difference table 60 (S51). From the S history table 70, the same section shows that the difference between the current time and the input time 52 is within the second time, the sensor type 61 matches the acquired sensor type 61, and the input measurement value and history measurement value 72 All the sensor histories 71 within the first measured value difference 62 acquired by the difference are acquired (S52). If it can be obtained (Y in S53), the processing unit 23 sets the relation 3b (FIG. 30).

  If it cannot be obtained (N in S53) or after the processing of FIG. 30, the processing unit 23 performs the following processing. That is, the same part shows that, from the S history table 70, the difference between the current time and the input time 52 is within the second time, the sensor type 61 matches the acquired sensor type 61, and the input measured value and history measured value 72 are the same. All the sensor histories 71 having the second measured value difference 63 or more acquired by the difference are acquired (S54).

  If it can be obtained (Y in S55), the processing unit 23 deletes the association 3b (FIG. 31). If it cannot be obtained (N in S55), the processing unit 23 ends the process.

  FIG. 30 is an operation flowchart (part) 2/3 of the processing unit 23 according to the third embodiment. The processing unit 23 performs the following processing (S60 to S65) for all the sensor histories 71 acquired in S52. First, the processing unit 23 acquires the sensor ID 35 from the sequentially selected sensor history 71 (S60). The same unit acquires all the management tables 30 (management table F) having the sensor ID 35 that matches the acquired sensor ID 35 (S61). The same unit sets a relation 3b for all combinations of the acquired management table E and management table F (S61 to S65). Specifically, the same unit compares the two E types 32 acquired from the sequentially selected management tables E and F with the type pair 41 of the association rule holding unit 26 and acquires an association rule 40 that matches (S62). . The processing unit 23 acquires the R type 38 to be set from the setting type 42 of the acquired association rule 40 (S63). The same part sets the R type 38 acquired in the R type 38 of the management table E and the address of the management table F in the other entity designation 39 (S64). The same part sets the acquired R type 38 in the R type 38 of the management table F, and sets the address of the management table E in the other entity designation 39 (S65).

  FIG. 31 is an operation flowchart (part) 3/3 of the processing unit 23 according to the third embodiment. The processing unit 23 performs the following processing (S70 to S72) for all the sensor histories 71 acquired in S52. First, the processing unit 23 acquires the sensor ID 35 from the sequentially selected sensor history 71 (S70). The same unit acquires all the management tables 30 (management table G) having the sensor ID 35 that matches the acquired sensor ID 35 (S71). The same part deletes the relation 3b with respect to all combinations of the acquired management table E and management table G (S72).

  FIG. 32 shows a third adaptation case (situation 1) of the context generation system 10. In this example, the entity 12 is the product 1 and the product 2 (both E type 32 is a product). The products 1 and 2 are provided with impact sensors 1 and 2, respectively. Assume that products 1 and 2 are both loaded onto a truck.

  FIG. 33 shows the management table 30 corresponding to the third adaptation case (situation 1). In the management unit 25, a management table 30 corresponding to each entity 12 is created. For example, the administrator of the context generation system 10 registers these pieces of information in the management unit 25 from the management terminal 16 via the registration unit 27. Here, when the truck travels and vibrates (situation 2), both the impact sensors 1 and 2 output measurement values corresponding to the vibration to the processing unit 23. The processing unit 23 inputs the same measurement value from the impact sensors 1 and 2 at the same time (within the second time), and sets the relationship 3b in which the R type 38 is “near” between them according to the association rule 40 (r13). . FIG. 34 shows the management table 30 corresponding to the third adaptation case (situation 2).

  FIG. 35 shows a third adaptation case (situation 3) of the context generation system 10. For example, it is assumed that the product 2 has fallen from the truck. In this case, the processing unit 23 continues to input the measurement value corresponding to the running vibration of the truck from the impact sensor 1 of the product 1, while inputting the large impact measurement value accompanying the fall from the impact sensor 2 of the product 2. become. As a result, the context generation device 11 detects that the products 1 and 2 are far and deletes the association 3b between the two entities 12. FIG. 36 shows the management table 30 corresponding to the third adaptation case (situation 3).

  The context generation system 10 according to the present embodiment can set various associations 3b between the entities 12. This is because the context generation system 10 of the present embodiment detects the approach of both entities 12 when the sensors 13 of the entities A and B simultaneously detect the measurement values within the first measurement value difference 62. . In addition, the same system detects that both entities 12 are distant when both sensors 13 simultaneously detect a measurement value greater than or equal to the second measurement value difference 63.

  FIG. 37 shows a basic configuration of the context generation device 11 according to the present invention. The context generation device 11 includes a management unit 25 and a generation unit 23. The management unit 25 stores the management table 30 that is provided for the entity 12 and stores the context 3 and the association 3b including the other entity designation 39 and the relationship type (R type 38). The generation unit 20 inputs the identification information of the first entity 12 and the type of context 36 (C type 37). The same part searches the management table 30 of the second entity 12 by tracing the relation 3b of the R type 38 selected based on the C type 37 input from the management table 30 of the first entity 12. The same part generates the context 36 of the first entity 12 based on the context 36 stored in the management table 30.

FIG. 1 shows the configuration of a context generation system 10 according to the first embodiment of the present invention. FIG. 2 shows a configuration of the context generation device 11. FIG. 3 shows the configuration of the management table 30. FIG. 4 shows the configuration of the context request 28. FIG. 5 shows a configuration of data stored in the association rule holding unit 26. FIG. 6 shows a configuration of data stored in the search rule holding unit 24. FIG. 7 is an operation flowchart of the registration unit 27. FIG. 8 is an operation flowchart of the processing unit 23. FIG. 9 is an operation flowchart of the generation unit 20. FIG. 10 shows the configuration of the data list 21. FIG. 11 shows the structure of the inspected related list 22. FIG. 12 is a flowchart of the search process of the context 36 starting from the management table A by the generation unit 20. FIG. 13 shows a first application example (situation 1) of the context generation system 10. FIG. 14 shows a management table 30 corresponding to the first adaptation case (situation 1). FIG. 15 shows a first adaptation case (situation 2) of the context generation system 10. FIG. 16 shows the management table 30 corresponding to the first adaptation case (situation 2). FIG. 17 shows a configuration of the context generation system 10 according to the second exemplary embodiment of the present invention. FIG. 18 shows the configuration of the R history table 50. FIG. 19 is an operation flowchart (part) of the processing unit 23 according to the second embodiment. FIG. 20 shows a second adaptation case (situation 1) of the context generation system 10. FIG. 21 shows a management table 30 corresponding to the second adaptation case (situation 1). FIG. 22 shows a second adaptation case (situation 2) of the context generation system 10. FIG. 23 shows the management table 30 corresponding to the second adaptation case (situation 2). FIG. 24 shows the management table 30 when the person 1 goes out of the truck 1 through the gate while holding the products 1, 2 and 3. FIG. 25 shows a configuration of the context generation system 10 according to the third exemplary embodiment of the present invention. FIG. 26 shows the configuration of the measurement value difference table 60. FIG. 27 shows the structure of the S history table 70. FIG. 28 shows the configuration of the conversion table 80. FIG. 29 is an operational flowchart (partial) 1/3 of the processing unit 23 of the third embodiment. FIG. 30 is an operation flowchart (part) 2/3 of the processing unit 23 according to the third embodiment. FIG. 31 is an operation flowchart (part) 3/3 of the processing unit 23 according to the third embodiment. FIG. 32 shows a third adaptation case (situation 1) of the context generation system 10. FIG. 33 shows the management table 30 corresponding to the third adaptation case (situation 1). FIG. 34 shows the management table 30 corresponding to the third adaptation case (situation 2). FIG. 35 shows a third adaptation case (situation 3) of the context generation system 10. FIG. 36 shows the management table 30 corresponding to the third adaptation case (situation 3). FIG. 37 shows a basic configuration of the context generation device 11 according to the present invention.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 Context production | generation system 11 Context production | generation apparatus 12 Entity 13 Sensor 14 ID tag 15 Tag reader 16 Management terminal 17 User terminal 18 Network 20 Generation part 21 Data list 22 Searched related list 23 Processing part 24 Search rule holding part 25 Management part 26 Association rule Holding unit 27 Registration unit 28 Context request 29 Context generation program 30 Management table 31 ID
32 E type 33 Tag ID
34 Reader ID
35 Sensor ID
36 Context 37 C type 38 R type 39 Other entity specification 3a C information 3b Related 40 Association rule 41 Type pair 42 Setting type 43 Search rule 44 Request specification 45 Search related specification 50 R history table 51 Reader history 52 Input time 60 Measurement value difference Table 61 Sensor type 62 First measurement value difference 63 Second measurement value difference 70 S history table 71 Sensor history 72 History measurement value 80 Conversion table

Claims (25)

A management unit that is provided for each entity and stores a management table that stores contexts and associations including other entity designations and association types (R types);
The identification information of the first entity and the type (C type) of the context are acquired, and the R type selected based on the acquired C type is started from the management table of the first entity. A context generation apparatus comprising: a generation unit that searches the management table of the second entity following the association and generates the context of the first entity based on the context stored in the management table. The said management table of several said 2nd entity is searched, The said production | generation part which produces | generates the context of the said 1st entity based on the said context stored in the said several management table is provided. Context generator. The management unit for storing the management table for storing the corresponding entity type (E type);
Detecting the approach or distant of the two entities,
Storing an association with one entity having an R type selected based on two E types stored in each of the management tables of the two entities in the management table of the other entity; Or the context production | generation apparatus of Claim 1 or 2 provided with the process part which deletes the said stored relationship. The context according to claim 3, further comprising: the processing unit that detects the approach of the two entities when the identification information of the ID tag attached to each of the two entities is acquired from one tag reader within a first time. Generator. When the measurement data within the first measurement value difference is acquired within the second time from the sensor attached to each of the two entities, the approach of the two entities is detected, or the second measurement value difference is detected. 5. The context generation device according to claim 3, further comprising the processing unit that detects that the two entities are far if the measurement data is acquired within the second time. 6. The processing unit for detecting whether the two entities are approaching or far from each other when an identifier of an ID tag attached to one of the two entities is acquired from a tag reader attached to the other entity. Any one of the context generation devices. The R type includes “contact arrangement” and “peripheral arrangement” of two entities,
If the inputted C type is temperature, the management table of the second entity is searched by following the relation of “contact arrangement” or “peripheral arrangement”. If the inputted C type is vibration, 7. The context generation device according to claim 1, further comprising: the generation unit that searches the management table of the second entity by following the association of “contact arrangement” but does not follow the association of “peripheral arrangement”. The context according to claim 1, further comprising: the generation unit that acquires a measurement value from a sensor attached to the entity and generates the context to be stored in the management table as the context of the entity. Generator. The context generation device according to claim 8, comprising: a registration unit that acquires data from a management terminal to create or modify the management table; and a generation unit that acquires the identification information of the first entity and the C type from a user terminal. ,
The management terminal;
The user terminal;
A context generation system including the sensor. A computer provided with a management unit for storing a management table that stores associations including contexts and other entity designations and association types (R types), which are provided for entities.
The identification information of the first entity and the type (C type) of the context are acquired, and the R type selected based on the acquired C type is started from the management table of the first entity. A context generation program that searches the management table of the second entity following the association and executes a generation process for generating the context of the first entity based on the context stored in the management table. In the computer,
The management table of the plurality of second entities is searched, and the generation processing for generating the context of the first entity is executed based on the context stored in the plurality of management tables. Context generator. In the computer comprising the management unit for storing the management table storing the corresponding entity type (E type),
Detecting the approach or distant of the two entities,
Storing an association with one entity having an R type selected based on two E types stored in each of the management tables of the two entities in the management table of the other entity; Or the context generation program of Claim 10 or 11 which performs the related process which deletes the said stored relationship. In the computer,
The identification processing of the ID tag attached to each of the two entities is acquired from a single tag reader within a first time, and the related processing for detecting the approach of the two entities is executed. Context generator. In the computer,
When the measurement data within the first measurement value difference is acquired within the second time from the sensor attached to each of the two entities, the approach of the two entities is detected, or the second measurement value difference is detected. 14. The context generation program according to claim 12 or 13, wherein when the above measurement data is acquired within the second time, the related processing for detecting that the two entities are far away is executed. In the computer,
13. An identifier of an ID tag attached to one of the two entities is acquired from a tag reader attached to the other entity, and the related processing for detecting that the two entities are approaching or far away is executed. Any one of 14 context generation programs. The R type includes “contact arrangement” and “peripheral arrangement” of two entities,
In the computer,
If the inputted C type is temperature, the management table of the second entity is searched by following the relation of “contact arrangement” or “peripheral arrangement”. If the inputted C type is vibration, 16. The context generation program according to claim 10, wherein the management table of the second entity is searched by following the association of “contact arrangement”, but the generation processing is not performed following the association of “peripheral arrangement”. . In the computer,
17. The measurement process according to claim 10, wherein a measurement value is acquired from a sensor attached to the entity, and the generation process for generating the context to be stored in the management table as the context of the entity is executed. Context generator. A computer provided with a management unit that stores a management table that is provided for an entity and stores a context and a relationship including another entity designation and a relationship type (R type).
An acquisition step of acquiring identification information of the first entity and a type (C type) of the context;
Starting from the management table of the first entity, the management table of the second entity is searched by following the association of the R type selected based on the acquired C type and stored in the management table A context generation method comprising: a generation step of generating a context of the first entity based on the performed context. The computer is
It searches the management table of the plurality of the second entity, based on the context stored in the plurality of management tables, with the generating step of generating a context of the first entity, according to claim 1 8 Context generation method. The computer including the management unit that stores the management table that stores a type (E type) of the corresponding entity,
Detecting the approach or distant of the two entities,
Storing an association with one entity having an R type selected based on two E types stored in each of the management tables of the two entities in the management table of the other entity; or has an associated step of deleting the associated stored, claim 1 8 or 1 9 the method of context generation. The computer is
21. The context of claim 20 , comprising the related step of detecting the proximity of the two entities when the identification information of the ID tag attached to each of the two entities is obtained from a tag reader within a first time. Generation method. The computer is
When the measurement data within the first measurement value difference is acquired within the second time from the sensor attached to each of the two entities, the approach of the two entities is detected, or the second measurement value difference is detected. The context generation method according to claim 20 or 21 , further comprising the related step of detecting that the two entities are far if the measurement data is acquired within the second time. The computer is
With the related step of detecting that the identifier of the ID tag attached to one of the two entities, acquired from the tag reader that is attached to the other result, approaching or Tonoi of the two entities, claims 20 to 22 Any one of the context generation methods. The R type includes “contact arrangement” and “peripheral arrangement” of two entities,
The computer is
If the inputted C type is temperature, the management table of the second entity is searched by following the relation of “contact arrangement” or “peripheral arrangement”. If the inputted C type is vibration, if it searches the management table of the follow additional second of said entities of the "contact arrangement" the associated context generation method of claim 18 or 23 having a generating step does not follow the "peripheral arrangement". The computer is
The context according to any one of claims 18 to 24 , further comprising: the generation step of acquiring a measured value from a sensor attached to the entity and generating the context to be stored in the management table as the context of the entity. Generation method.

Images