JP2008027388A - Sensor information conversion device, sensor information conversion method and sensor information notification method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a technique for notifying sensor information as information more useful to a user and flexibly selecting sensors for use. <P>SOLUTION: A sensor information conversion device for converting sensor data received from sensors into information to be provided for a user comprises a sensor data conversion means for converting sensor data received from a sensor into state information showing a state adapted to an object measured by the sensor, and a state information conversion means for converting the state information into information showing a predetermined event expected from the state information. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a technique for processing information from a sensor attached to a house, a building, or the like.

  There is a technology for installing various sensors in a house or the like and notifying a user who is the owner of the house that the sensor has reacted. As an example of such a technique, for example, a system disclosed in Patent Document 1 is known.

  In the system of Patent Document 1, a door opening / closing sensor that detects opening / closing of a door, a glass break sensor that detects breakage of a window glass, a locking confirmation sensor that detects whether the door is locked, and the like are provided on the door. in use. That is, a dedicated sensor having a function capable of predefining an abnormal state of a target facility to which the sensor is attached and detecting the defined abnormal state is used.

  And, for example, if the door open / close sensor reacts, it recognizes that the door is opened, and if the glass break sensor reacts, it recognizes that the window glass is broken, and can know the state change of the housing facility from the information of the reacted sensor. .

  However, in the technique of Patent Document 1, the user may aim to be notified of the presence / absence of each dedicated sensor installed, and the user may be notified of the presence / absence of an abnormality and the type of sensor that has reacted when there is an abnormality. Can only know.

Moreover, in the conventional sensor monitoring technology including the technology of Patent Document 1, the sensor is limited to a specific application, and the processing related to sensor information in various devices that provide a monitoring service corresponds to the sensor type. It is fixedly incorporated in the entire process. Therefore, it is difficult to use the same sensor for a plurality of uses or to change the sensor.
JP 2003-256950 A

  The present invention has been made in view of the above points, and enables not only the fact of whether or not the sensor has reacted, but also notification of the sensor information that has reacted as more meaningful information to the user, and is flexible. It is an object of the present invention to provide a technique capable of selecting and using a sensor.

  The above-described problem is a sensor information conversion device that converts sensor data received from a sensor into information for providing to a user, and the sensor data received from the sensor represents a state corresponding to a measurement target of the sensor. A sensor information conversion device comprising: sensor data conversion means for converting into state information; and state information conversion means for converting the state information into information representing a predetermined event determined from the state information. Is done.

  The sensor data conversion means may be selected from a plurality of sensor data conversion means as means corresponding to a set of the sensor type and the measurement target type of the sensor. The state information conversion unit may be selected from a plurality of state information conversion units as a unit corresponding to a set of the predetermined event and the type of measurement target of the sensor.

  In the case where there are a plurality of pairs of sensors and measurement targets, the sensor information conversion device includes a plurality of sensor data conversion units corresponding to the plurality of sets, and the state information conversion unit includes the plurality of sensor data conversion units. Information representing the predetermined event may be obtained by converting a plurality of state information obtained by the means. In this case, the state information conversion means includes a plurality of state information conversion means respectively corresponding to the sensor data conversion means and means for outputting final information from information output from the plurality of state information conversion means. It is good as well.

  The above-described problem is a sensor information notification method executed by a sensor information notification system for converting sensor data received from a sensor into information for notifying the user and notifying the user. A step of receiving registration information including a set of a type and a type of measurement target of the sensor; and a sensor data conversion unit corresponding to the set of the sensor type and the type of measurement target of the sensor based on the registration information. A step of selecting, a step of converting sensor data received from the sensor by the selected sensor data conversion means into state information representing a state corresponding to a measurement target of the sensor, and the state information Is converted into information representing a predetermined event to be determined and stored in the storage device, and triggered by the user in advance. And if it is determined also solved by a sensor information notification method characterized by a step of notifying the information corresponding to the user to the user.

  According to the present invention, it is possible to obtain state information peculiar to the measurement object regardless of the sensor type by the sensor data conversion means. Then, the status information conversion means can further convert the status information to obtain information representing a predetermined event that is meaningful to a user having a certain monitoring purpose.

  The state information conversion means can be configured to execute processing independent of the sensor type, and even if the sensor type is changed, only the sensor data conversion means needs to be changed, in order to achieve the same purpose. If so, there is no need to change the state information conversion means.

  Moreover, since the sensor data conversion means corresponding to the set of the sensor type and the measurement target type of the sensor is selected and used, the sensor can be selected flexibly. Furthermore, since the state information conversion means can be selected by registering a predetermined event according to the user's purpose, the user can easily perform monitoring according to various purposes.

  Embodiments of the present invention will be described below with reference to the drawings.

  FIG. 1 shows a schematic configuration of a system in the present embodiment. In this system, users attach various sensors to doors, windows, chairs, etc. in buildings such as homes, install sensor readers and sensor gateways (GWs), and these devices send sensor data to the network. To the server device 10 via the network. Then, the server device 10 analyzes the sensor data, converts the sensor data into information easy for humans to understand, and presents the information to the user terminal 30 via the monitoring device 20.

  The server device 10 includes a sensor raw data extraction unit 101, a sensor data meaning processing unit 102 that assigns meanings corresponding to objects to the sensor raw data, and meaning information that manages the meaning information associated with the objects. A management unit 103 and a semantic information secondary processing unit 104 for processing the meaning information into more significant information and managing the contents are provided.

  The sensor reader is a device that receives sensor information from the sensor and notifies the sensor GW. The sensor GW is a device that receives sensor information from the sensor reader, connects to the server device 10 using an NW line such as an IP network, and notifies the sensor information. Further, both the server device 10 and the monitoring device 20 are realized by installing a predetermined program in a computer having a CPU, a storage device, and the like.

  Next, functional configurations of the monitoring device 20 and the server device 10 will be described in more detail with reference to FIG. FIG. 2 is a diagram illustrating a configuration of functions that exist after the generation, registration, and the like of each functional unit are completed.

(Monitoring device 20)
As shown in FIG. 2, the monitoring device 20 includes a user interface unit 201, an incident check unit 202, a middleware communication unit 203, and a mail server 204. In the present embodiment, the monitoring device 20 includes a user interface unit 201, an incident check unit 202, and a middleware communication unit 203 as applications.

  The user interface unit 201 has a function of providing the user terminal 30 with a user interface for the user to select a service menu and register user environment information when the user terminal 30 accesses the monitoring apparatus 201 via the network. Yes. The user interface unit 201 is realized using, for example, a Web server.

  The incident check unit 202 has a function of acquiring information analyzed by the server device 10 and notifying the user terminal 30 by e-mail or the like when the information indicates that a predetermined event has occurred. . The middleware communication unit 203 is a functional unit for communicating with the middleware in the server device 10.

(Server device 10)
The server device 10 includes an overall unit 110, a network management unit 111, a function unit generation / management unit 112, a user request processing unit 113, a sensor raw data extraction unit 101, a sensor data semantic processing unit 102, a semantic information management unit 103, A semantic information secondary processing unit 104, a semantic information tertiary processing unit 105, a position information detection unit 114, a reader state management unit 115, and a GW state management unit 116 are included.

  Since these functional units operate as middleware for the application of the monitoring device 20, these functional units may be collectively referred to as middleware. In the present embodiment, each functional unit is realized by executing a predetermined program in the server device 10. For example, when these functional units are realized using an object-oriented software technique, each functional unit corresponds to an instance activated from a class (dynamically loaded into a memory).

  Note that the monitoring device 20 and the server device 10 may be realized as one device. Further, middleware may be realized in one device, or each functional unit may be distributed and arranged in a plurality of devices, and one middleware may be logically realized by a plurality of devices.

  Hereinafter, each functional unit of the server device 10 will be described. In addition, the user environment in the following description is composed of sensors, objects, places, incidents, and respective link relationships. A thing is a measurement target to which a sensor is attached, such as a window, a door, a person, or a pet. A place is a place where a thing exists and is associated with a sensor reader. The incident refers to information obtained by secondary analysis of the meaning information, and the composite incident is a bundle of a plurality of incident analysis results.

  The overall unit 110 of the server apparatus 10 provides an interface function that receives a request from the monitoring apparatus 20 and returns a response. Specifically, it accepts two types of requests, that is, user environment registration and incident confirmation from the monitoring device 20, and returns a response.

  The network management unit 111 receives the sensor information packet from the network, reads the ID portion included in the header of the sensor information packet, and transfers the sensor information to the appropriate sensor raw data extraction unit 101 based on the ID.

  When the user environment is registered, the functional unit generation / management unit 112 generates a functional unit corresponding to what constitutes the user environment and a functional unit for giving meaning to the sensor data according to the user environment. Specifically, the functional unit generation / management unit 112 activates a program corresponding to each functional unit, and generates the functional unit by appropriately setting information (ID information, link information, etc.) necessary for the operation. .

  Each functional unit described below is a functional unit generated by the functional unit generation / management unit 112 when a user and a user environment are registered. Note that a program serving as a basis for each functional unit is created in advance and stored in the storage device of the server device 10.

  The user request processing unit 113 is a functional unit that is generated in one-to-one correspondence with the user, and manages the user environment.

  The sensor raw data extraction unit 101 is a functional unit that is generated in one-to-one correspondence with the sensors registered by the user. In the present embodiment, the sensor type and the sensor raw data extraction unit corresponding table 151 that stores the sensor type and the type of the sensor raw data extraction unit corresponding to the sensor are stored in correspondence with each other. 1 is started, and the sensor raw data extraction unit 101 is generated.

  The sensor raw data extraction unit 101 has a function of managing the state of the sensor (for example, life / death information indicating whether the sensor data is periodically rising, which reader is connected, etc.). The sensor raw data extraction unit 101 also has a function of receiving primitive raw data of the corresponding sensor and immediately transferring the raw data to a functional unit that performs appropriate meaning processing.

  The sensor data meaning processing unit 102 is a functional unit that is generated according to the type of sensor and the type of object to which the sensor is attached. In the present embodiment, the sensor type-mono type-sensor data meaning processing unit correspondence table 152 that stores the type of the sensor data meaning processing unit in association with the combination of the sensor type and the product type refers to the sensor A sensor data semantic processing unit 102 is generated by starting a program that is a base of the sensor data semantic processing unit corresponding to the combination of the type of the object and the type of the item to which the sensor is attached.

  The sensor data meaning processing unit 102 is a processing unit that determines the state of an object attached with a sensor from sensor information. For example, the door opening / closing state is determined based on information from a vibration sensor attached to the door. Even when the same state is determined, the processing content for determining the state is different if the sensor type is different. Further, in the present embodiment, a state to be detected for each product type is determined in advance (open / closed status for a door, seated status for a chair, etc.), corresponding to each combination of sensor type and product type. A program that is the basis of the sensor data meaning processing unit is created in advance, and the type is stored in the table.

  The semantic information management unit 103 is a functional unit that is generated in a one-to-one correspondence with a thing (window, door, furniture, pet, person, etc.) registered by the user. In the present embodiment, by referring to the item type / semantic information management unit correspondence table 153 that stores the type of the item and the type of the meaning information management unit corresponding to the item in association with each other, 1 is assigned to the item. The semantic information management unit 103 is generated by starting a program that is the basis of the semantic information management unit corresponding to the pair.

  The meaning information management unit 103 manages the state and position information of the corresponding object, and further manages the relationship with the meaning information secondary processing unit 104 for secondary analysis of the state of the object. The state information is notified from the sensor data meaning processing unit 102, and the position information is notified from the position information detection unit 114. Upon receiving these notifications, the semantic information management unit 103 immediately notifies the related semantic information secondary processing unit 104 of the status information.

  The semantic information secondary processing unit 104 is a functional unit generated in a one-to-one correspondence with the incident type and the item type registered by the user.

  In the server apparatus 10 of this Embodiment, the state which the door is open can be notified as an abnormal condition using the vibration sensor attached to the door, for example. Further, it is possible to determine that there is no human activity using a vibration sensor attached to the door, and to notify it as an abnormal situation.

  As will be described in detail later, when notifying that the door is open as an abnormal state, the sensor data meaning processing unit 102 detects only the open / closed state of the door, and the state is passed through the meaning information management unit 103. To the semantic information secondary processing unit 104, and the semantic information secondary processing unit 104 determines that “it is abnormal when“ open ””. Also, when notifying that there is no human activity as an abnormal situation, the sensor data meaning processing unit 102 detects only the open / closed state of the door as described above, but the meaning information secondary processing unit 104 The state of “no human activity” is determined from the pattern of the open / close state of.

  Whether you want to make the above judgment “abnormal when“ open ”” or whether you want to judge “no human activity” as an abnormality corresponds to each incident type. The user selects the incident type according to the monitoring content intended.

  Further, for example, since the process of detecting “no activity” using the door open / close state is different from the process of detecting “no activity” using the vibration state of the chair, the server device 10 determines whether the incident type A program for performing each processing is stored in advance in association with the combination of types. This program is the basis of the semantic information secondary processing unit 104. The contents of each program are determined and created based on, for example, monitoring contents frequently requested by users.

  In this embodiment, the mono type-incident type-semantic information secondary processing unit correspondence table 154 that stores the type of the semantic information secondary processing unit in association with the combination of the incident type and the mono type is referred to. Thus, the program that is the basis of the semantic information secondary processing unit associated with the combination of the incident type and the product type is started, and the semantic information secondary processing unit 104 is generated.

  Each semantic information secondary processing unit is a separate server, and the status information obtained by meaning the sensor information is sent to the server according to the registered contents of the user, and the semantic information secondary processing is sent to that server. It is also possible to perform processing.

  The semantic information tertiary processing unit 105 is a functional unit generated in one-to-one correspondence with a composite method (also referred to as a composite incident) registered by the user. For example, if the user wants to be notified of an abnormality when the open / closed state of the door is open and a person is absent from the vibration state of the chair, the user opens the open / closed state of the door. An incident type that is determined to be abnormal if it is, an incident type that is determined to be abnormal when the person is absent from the vibration state of the chair, and an abnormality if both of these occur simultaneously The compound method “AND” that indicates that it is detected is registered.

  In other words, the semantic information tertiary processing unit 105 is a functional unit that collects the analysis results of the semantic information secondary processing unit 104 and creates information aggregated by AND or OR combination. In the present embodiment, by referring to the composite method-semantic information tertiary processing unit correspondence table 155 that stores the composite method and the type of the semantic information tertiary processing unit corresponding to the composite method in association with each other. Then, the semantic information tertiary processing unit 105 is generated by starting a program that is a base of the semantic information tertiary processing unit corresponding to the composite method on a one-to-one basis.

  The position information detection unit 114 is a function unit that is generated in a one-to-one correspondence with a location registered by the user (such as a living room, a child's room, and an entrance), and a thing (window, door, furniture, pet, person, etc.) Manage the installation location. In addition, the position information detection unit 114 analyzes where the sensor is located, then analyzes where the object associated with the sensor is located, and the semantic information management unit 103 corresponding to the object. Has a function of notifying location information.

  The reader state management unit 115 is a functional unit that is generated in one-to-one correspondence with the sensor reader registered by the user, and manages the life / death state of the reader. The sensor reader is associated with a place and manages the relationship.

  The GW state management unit 116 is a functional unit that is generated in one-to-one correspondence with the GW registered by the user, and manages the life / death state of the GW.

(System operation overview)
Hereinafter, an outline of the operation procedure of the system when the system of the present embodiment provides a service will be described.

[Middleware activation in server device 10]
Step 1) When the middleware is activated, the supervising unit 110 is generated first.

  Step 2) The overall unit 110 generates the function unit generation / management unit 112.

[Activation of application in monitoring device 20]
Step 3) When the application in the monitoring device 20 is activated, the Web server or the like constituting the user interface unit 201 starts to operate. Examples of service menu items presented to the user terminal 30 by the user interface unit 201 of the monitoring device 20 include “service selection” and “user registration” as the main menu, and “home” as the submenu of “service selection”. There are security, building management, elderly / child watching, and greenhouse management.

[user registration]
Step 4) The user terminal 30 accesses the user interface unit 201 provided by the application. Here, it is assumed that “user registration” is selected from the user terminal 30.

  Step 5) The user interface unit 201 of the monitoring device 20 displays a user registration screen on the user terminal 30, and the user registers a user ID, a mail address, and the like from this screen. The user terminal 30 notifies the incident check unit 202 of the monitoring device 20 of the pair of the user ID and the mail address, and the incident check unit 202 manages this information with the pair.

  Step 6) Also, when the monitoring device 20 notifies the server device 10 of the user ID, the functional unit generation / management unit 112 generates a user request processing unit 113 corresponding to the user.

  In this specification, “information management” includes storing information in the storage device of the monitoring device 20 or the server device 10 so that it can be read out as appropriate. “Registering information” includes storing information in the storage device of the monitoring device 20 or the server device 10.

[Service selection and user environment registration]
Step 7) The user registered user can access the “service selection” menu and select a desired service.

  Step 8) As an example, when the user selects “home security”, a screen for registering a user environment for home security is presented to the user terminal 30 by the user interface unit 201 of the monitoring device 20.

  Step 9) First, the user registers the sensor as the user environment from the user terminal 30. Select the sensor type and model number from the menu screen, and register the ID (serial number, etc.) unique to the sensor.

  Step 10) When the user performs a registration operation, the registered information is notified to the server device 10, and the functional unit generation / management unit 112 generates the sensor raw data extraction unit 101 corresponding to the registered sensor.

  Step 11) The user selects an item and an incident from the menu and registers them. For example, when the absence of a person is to be notified from the vibration state of the chair, the chair is registered as a thing, and the incident corresponding to the absence detection is registered as an incident.

  Step 12) Subsequently, the user registers the link relationship between the sensor, the thing, and the incident registered through the user terminal 30. For example, when a vibration sensor is attached to a chair, since there is a link relationship between the vibration sensor and the chair, registration to that effect is performed. Corresponding link relations between goods and incidents are also registered.

  With the above registration, function units (semantic information management unit 103, semantic information secondary processing unit 104) corresponding to the object and the incident are generated.

  Step 13) Subsequently, the user registers the unique ID of the reader and GW to be used via the user terminal 30. Based on this information, the reader state management unit 115 and the GW state management unit 116 corresponding to the middleware are generated.

[Service operation]
Step 14) A user who has completed user registration and user environment registration turns on the power of actual devices such as sensors, sensor readers, and GWs. The GW device has a user interface provided by the GW device, which is used to register the IP address of the server device 10 in the GW device.

  Step 15) The sensor information is transmitted to the sensor reader when the sensor detects vibration or at a timing when temperature or the like is measured at regular intervals. This transmitted information includes the unique ID of the sensor and measurement information.

  Step 16) The sensor reader adds the unique ID information of the reader itself to the received information and notifies the sensor GW of the information.

  Step 17) The sensor GW adds the unique ID information of the GW itself to the received information and transmits it to the server device 10 via the network.

  Step 18) The server device 10 receives a sensor information packet including measurement information and ID information.

  Step 19) The server apparatus 10 refers to the network topology information based on the received ID information of the sensor information packet, and transfers the sensor information to the sensor raw data extraction unit 101.

  Step 20) Subsequently, the sensor data meaning processing unit 102 receives the sensor information from the sensor raw data extraction unit 101, and performs the sensor information meaning processing. Then, the semantic information secondary processing unit 104 or the semantic information tertiary processing unit 105 performs a final analysis process and holds the analysis result.

  Step 21) On the other hand, the incident check unit 202 of the monitoring device 20 periodically transmits a confirmation request for incident information corresponding to the registered user to the server device 10. Then, the server device 10 transmits the incident confirmation request to the user request processing unit 113 corresponding to the user. Note that the user request processing unit 113 corresponding to the user can be identified by using the user ID.

  Step 22) The user request processing unit 113 includes a semantic information secondary processing unit 104 and a semantic information tertiary processing unit 105 corresponding to the incident and the complex incident registered by the user corresponding to the user request processing unit 113. Information is owned by each processing unit from all managed processing units.

  Step 23) The user request processing unit 113 returns the acquired information from the information secondary processing unit 104 and the like to the monitoring device 20 that is the request source.

  Step 24) The incident check unit 202 of the monitoring device 20 receives the acquired information and transmits it to the mail address of the user terminal 30. The incident check unit 202 notifies the user terminal 30 when the acquired information indicates “abnormal”. In addition, the acquired information can be notified to the user terminal 30 regardless of the presence or absence of “abnormal”.

  Step 25) Thus, the user can obtain information (secondary or tertiary processing information) that represents a meaningful event occurrence that is more easily understood by humans, rather than the state of an object simply given meaning from primitive sensor information. it can.

(Details of operation)
Next, the operation and configuration of the system in the present embodiment will be described in more detail.

  In the detailed operation example described below, an example in which the presence or absence of an indoor person's activity is monitored by attaching a vibration sensor manufactured by Company A to the door will be described.

[Register user environment and device information]
First, user environment registration / device information registration will be described with reference to FIGS. The dotted lines in FIG. 3 and the subsequent block diagrams mean that the ID and the pointer are registered as shown in FIG. These pieces of information are referred to as reference information.

  Step 1-1) At the start of service use, the user inputs a user ID from the screen displayed on the user terminal 30 by the user interface unit 201 of the monitoring device 20. At this time, as shown in FIG. 3, the middleware communication unit 203 in the monitoring device 20 notifies the user ID to the overall unit 110 of the server device 10. The supervising unit 110 requests the functional unit generation / management unit 112 to generate the user request processing unit 113, and the functional unit generation / management unit 112 generates a user request processing unit 113 corresponding to the user. Here, for example, a user ID corresponding to the user is set as identification information in the program corresponding to the user request processing unit 113 and the program is started.

  Step 1-2) Next, the user registers the user environment. FIG. 5A shows a user environment registered in the server device 10 in this operation example.

  In this step, the user registers the sensor to be used, the object to which the sensor is attached, and the monitoring content (incident). As described above, the type of incident is set in advance in the server device 10, and the set type is displayed on the user terminal 30, and the desired incident is selected from those displayed by the user.

  For example, “open” that detects an abnormality as an incident according to the open / closed state of windows / doors, “absent” that detects an absence according to the open / closed state of windows / doors, etc., according to the open / closed state of doors, etc. There is “no activity” for detecting the presence or absence of human activity, and the user selects an incident according to the purpose.

  In this operation example, the user desires to monitor the presence or absence of an indoor person's activity by attaching a vibration sensor made by company A to the door, so the vibration sensor made by company A (ID = 0001), Register the door as an object and “no activity” as an incident.

  When the monitoring device 20 notifies the server device 10 of the input information, the functional unit generation / management unit 112 of the server device 10 displays the item type / semantic information management unit correspondence table 153 shown in FIG. With reference to the sensor type-sensor raw data extraction unit correspondence table 151 shown in FIG. 6B, the semantic information management unit 103 corresponding to the product type and the sensor raw data extraction unit 101 corresponding to the sensor type are generated.

  Then, as indicated by the dotted line in FIG. 3, the functional unit generation / management unit 112 registers the generated reference information of the functional unit in the user environment management unit of the user request processing unit 113. It is assumed that the location information detection unit 114 manages the location name and there is no correspondence table because there is no type in the processing contents.

  In the user ring shown in FIG. 5A, the functional unit shown in FIG. 5B is generated. The server device 10 automatically assigns serial numbers to registered sensors, objects, and incidents. The user can specify the serial number and perform an operation (detail display, deletion, etc.).

  Step 1-3) Next, the user registers the link relationship of the user environment. The link relationship registered in this operation example is shown in FIG. Assuming the registration contents of this operation example shown in FIG. 5A, the link relationship “1-2” between the vibration sensor 1 manufactured by company A and the door, and the link relationship “2” between the door and the incident “no activity” -3 "is registered.

  Thereafter, the functional unit generation / management unit 112 refers to the sensor type-thing type-sensor data meaning processing unit correspondence table 152 shown in FIG. The processing unit 102 is generated. Similarly, the functional unit generation / management unit 112 refers to the mono type-incident type-semantic information secondary processing unit correspondence table 154 shown in FIG. The attached information secondary processing unit 104 is generated. Then, the function unit generation / management unit 112 registers the generated reference information of the function unit in the user environment management unit of the user request processing unit 113.

  Step 1-4) Subsequently, as shown in FIG. 9, the functional unit generation / management unit 112 uses the link relationship to assign the corresponding sensor data meaning to the notification destination management unit of the sensor raw data extraction unit 101. The reference information of the processing unit 102 is registered. Similarly, the reference information of the corresponding semantic information management unit 103 is registered in the notification destination management unit of the sensor data semantic processing unit 102. Similarly, the reference information of the corresponding semantic information secondary processing unit 104 is registered in the notification destination management unit of the semantic information management unit 103.

  As a result of the above processing, each function unit shown in FIG. 7B is generated, and notification destination management information between the function units is registered in each function unit.

  Step 1-5) On the other hand, the user registers device (node, reader, gateway, etc.) information to be used in the server device 10 via the user terminal 30 and the monitoring device 20. ID information for identifying each device is embedded in a device such as a node, and the ID information is registered. FIG. 10A shows an example of user equipment to be registered.

  As illustrated in FIG. 11, when registering a user device, the function unit generation / management unit 112 generates a network management unit 111 that manages the device information.

  Step 1-6) Next, the functional unit generation / management unit 112 generates a reader state management unit 115 and a GW state management unit 116 as shown in FIG. Then, as shown in FIG. 11, the reference information is registered in the network management unit 111.

  In addition, each functional unit manages each ID information as static information. The sensor raw data extraction unit 101-1 and the sensor raw data extraction unit 101-2 are generated in the above step 1-2, but this is also registered in the network management unit 111, and each ID information is assigned to each. Register in the functional part.

  Step 1-7) In order to register the reader installation position information, the user shows the relationship between the location registered in Step 1-2 and the reader registered in Step 1-5 as shown in FIG. Link with a serial number. At this time, the server device 10 registers the position information detection unit 114 in the location management unit of the reader status management unit 115 as shown in FIG.

  In the above example, individual meaning processing units are generated at the time of registration by the user. Instead, after receiving a sensor information packet, a corresponding item is generated based on the sensor ID included in the packet. (Measuring object) may be discriminated, and a semantic processing unit corresponding to the sensor ID and the object may be generated to perform the semantic processing. Even in this case, the association between the sensor and the object is registered.

[Processing and meaning of sensor information]
Next, processing of each functional unit in the process of giving meaning after receiving the sensor information in this operation example will be described in more detail with reference to FIGS. It is assumed that the user environment and the user device are registered in the above-described process and a corresponding functional unit is generated.

  Further, it is assumed that the packet structure notified from the real machine GW to the network management unit 111 of the server device 10 via the network has a format shown in FIG. That is, the packet includes the ID of the sensor that is the information source, the ID of the node, the ID of the relayed reader, and the ID of the gateway. FIG. 12B shows an example of the contents of a packet transmitted from the vibration sensor manufactured by company A with sensor ID 0001 and received by the server device 10. In the case of a vibration sensor manufactured by Company A, the vibration information is represented by a binary value, which is “1” at the time when the vibration occurs, and the vibration information values at other times are “0”. Hereinafter, a case where this packet is received will be described.

  Step 2-1) FIG. 13 is a functional block diagram for explaining the operation of the network management unit 111. As illustrated in FIG. 13, the network management unit 111 includes a packet reception unit 1111, an ID extraction unit 1112, an NW device search unit 1113, an NW device management unit 1114, a link registration unit 1115, and a sensor information notification unit 1116. Yes.

  When the packet reception unit 1111 receives the packet, the ID extraction unit 1112 of the network management unit 111 extracts ID information from the packet. In this operation example, 1009 is extracted as the GWID, 0108 is extracted as the reader ID, and 0001 is extracted as the sensor ID.

  Step 2-2) The NW device search unit 1113 of the network management unit 111 selects the sensor raw data extraction unit 101, the reader state management unit 115, and the GW state management unit 116 having the extracted ID information from the NW device management unit 1114. Search and extract.

  Step 2-3) The link registration unit 1115 registers link information in the link management unit of each functional unit extracted in step 2-2. Specifically, the reference information of the corresponding sensor raw data extraction unit 101-1 is registered in the link management unit of the reader state management unit 115, and the reference information of the reader state management unit 115 is registered as the link management unit of the GW state management unit 116. Register with.

  Step 2-4) Next, as shown in FIG. 14, the NW device search unit 1113 notifies the sensor information notification unit 1116 of the sensor information and the reference information of the sensor raw data extraction unit 101-1, and the sensor information notification unit 1116 notifies sensor information to the sensor raw data extraction unit 101-1.

  In this operation example, since sensor ID = 0001, sensor information is notified to the sensor raw data extraction unit 101-1 shown in FIG.

  Step 3-1) FIG. 15 shows a functional configuration of the sensor raw data extraction unit 101-1. As illustrated in FIG. 15, the sensor raw data extraction unit 101-1 includes a sensor information reception unit 1011, a sensor information extraction unit 1012, a sensor information notification unit 1013, and a notification destination management unit 1014.

  As illustrated in FIG. 15, the sensor information reception unit 1011 of the sensor raw data extraction unit 101-1 receives sensor information from the network management unit 111.

  Step 3-2) The sensor information extraction unit 1012 of the sensor raw data extraction unit 101-1 extracts sensor information and notifies the sensor information notification unit 1013 of the sensor information. In this operation example, sensor information = 1 is notified as shown in the packet of FIG.

  Step 3-3) As shown in FIG. 7B, the information managed by the notification destination management unit 1014 corresponds to the sensor data meaning processing unit 102-1 (A company vibration sensor attached to the door). Sensor information notifying unit 1013 notifies the sensor data meaning processing unit 102-1 of “1”.

[Example of Semantic Processing in Sensor Data Semantic Processing Unit 102-1]
Next, semantic processing in the sensor data semantic processing unit 102-1 will be described. In addition, since the meaning process regarding the sensor attached to the door in this operation example and the meaning information secondary processing process are shown in FIG. 16, FIG. 16 will be referred to as appropriate.

  The sensor data meaning processing unit 102-1 in this operation example determines whether the door is in an “open” state or a “closed” state based on sensor information (simple numerical information). It has a function of notifying the result to the meaning information management unit 103-1. That is, as shown in FIG. 16B, when the door state is “closed” at time t = 0, and “1” is notified as vibration information at t = 1, meaning instance 1 Changes the meaning information after t = 1 to “open” and notifies the meaning information management unit 103-1 of the value of “open”.

  FIG. 17A is a functional configuration diagram of the sensor data meaning assigning processing unit 102-1. As shown in FIG. 17A, the sensor data semantic processing unit 102-1 includes a sensor information receiving unit 1021, a semantic processing unit 1022, a semantic information management unit 1023, a semantic table 1024, and a semantic information notification unit. 1025 and a notification destination management unit 1026. FIG. 17B shows the contents of the meaning table 1024.

  Step 4-1) The sensor information receiving unit 1021 of the sensor data meaning assigning unit 102-1 receives sensor information (this value is A) from the sensor raw data extracting unit 101-1. In this operation example, A = 1.

  Step 4-2) The meaning information management unit 1023 of the sensor data meaning assignment processing unit 102-1 manages state information for meaning assignment (this value is B), and the initial state as described above. Then we have the information “closed”.

  Step 4-3) The semantic processing unit 1022 extracts new semantic information from the semantic table 1024 shown in FIG. 17B based on the values A and B. Here, since A = 1 and B = “closed”, the semantic information = “open”.

  Step 4-4) The semantic information management unit 1025 updates the management information to “open”.

  Step 4-5) Then, the semantic information notification unit 1025 acquires the reference information of the semantic information management unit 103-1 managed by the notification destination management unit 1026, and “open” the semantic information management unit 103-1. To be notified.

[Processing of Meaning Information Management Unit 103-1 and Semantic Information Secondary Processing Processing Unit 104-1]
Next, a process after information is notified from the sensor data meaning processing unit 102-1 to the meaning information management unit 103-1. As illustrated in FIG. 16C, the semantic information management unit 103-1 holds the state information received from the sensor data semantic processing unit 102-1, and the semantic information secondary processing unit 104-1. Has a function of notifying state information.

  FIG. 18 shows a functional configuration of the meaning information management unit 103-1. As illustrated in FIG. 18, the semantic information management unit 103-1 includes a semantic information receiving unit 1031, a status management unit 1032, a status notification unit 1033, and a notification destination management unit 1034.

  FIG. 19 shows a functional configuration of the semantic information secondary processing unit 104-1 associated with the semantic information management unit 103-1. As shown in FIG. 19, the semantic information secondary processing unit 104-1 includes a mono state receiving unit 1041, an analysis processing unit 1042, a state change recording unit 1043, an analysis result management unit 1044, an analysis result notification unit 1045, and A notification destination management unit 1046 is provided. Hereinafter, the operation in such a configuration will be described.

  Step 5-1) The semantic information receiving unit 1031 of the semantic information managing unit 103-1 receives information “open” or “closed” from the sensor data semantic processing unit 102-1.

  Step 5-2) The state management unit 1032 manages “open” or “closed” notified in step 5-1.

  Step 5-3) The status notification unit 1033 acquires the reference information of the semantic information secondary processing unit 104-1 managed by the notification destination management unit 1034, and “open” to the information secondary processing unit 104-1. Alternatively, “closed” is notified.

  Next, the process of the semantic information secondary processing unit 104-1 will be described.

  Step 6-1) The mono state receiving unit 1041 of the information secondary processing unit 104-1 receives the information “open” or “closed” from the semantic information management unit 103-1, and notifies the analysis processing unit 1042 of the information. To do.

  Step 6-2) The analysis processing unit 1042 of the semantic information secondary processing processing unit 104-1 does not immediately analyze the information notified from the semantic information management unit 103-1 on a daily basis. The result is stored and analyzed, and the analysis result management unit 1044 manages the result. Hereinafter, specific contents of the analysis in this operation example will be described.

  The semantic information secondary processing unit 104-1 receives the update of information from the semantic information management unit 103-1 within the predetermined period (one day in this operation example) and displays the analysis result as “active”. The analysis result is “no activity” when there is no notification from the meaning information management unit 103-1 within a predetermined period. That is, as shown in FIG. 16D, in 4/12 and 4/13, there is a state update from the semantic information management unit 103-1, but 4/14 is not updated. As shown in e), 4/12 and 4/13 obtain an analysis result “active” and 4/14 “no activity”. In such a process, if there is a status update, the timer is reset, and if there is a status update while the timer measures 24 hours, it will be “active”, otherwise it will be “no activity” Can be realized.

  According to such processing, when realizing an answering machine or a monitoring service for elderly / children living alone, it is necessary to check all sensor information such as door vibration that occurs many times a day. Efficient monitoring is possible using activity detection results on a daily basis.

[Incident analysis combining multiple states]
Next, an example of performing an incident analysis combining a plurality of states will be described. In this operation example, an A company magnet sensor (ID = 0001) is attached to the door to detect the open / close state, and an A company vibration sensor (ID = 0002) is attached to the chair to detect the presence / absence of the seat. , And anomaly detection is performed by ANDing the door open / closed state and the presence / absence state. Specifically, when the door is “open” and “seated”, an analysis result indicating an abnormality is obtained.

  The incident information tertiary processing unit 105 that bundles a plurality of analysis results (incidents) output from the plurality of meaning information secondary processing units 104 is used for incident analysis combining a plurality of states. Hereinafter, the flow of processing will be described.

  Step 7-1) In this example, the user registers the elements as shown in FIG.

  Step 7-2) The functional unit generating / managing unit 112 generates the functional units shown in FIG. 21 with reference to the various functional unit correspondence tables. Further, these are registered in the user request processing unit 113.

  Here, the sensor data meaning processing unit 102-2 that performs the meaning processing of the sensor data sent from the vibration sensor (sensor ID = 0002) manufactured by Company A attached to the chair will be described.

  The sensor data meaning processing unit 102-2 in this operation example determines whether the chair user is “present” or “away” based on the sensor information, and gives the meaning to the determination result. It has a function of notifying the information management unit 103-2.

  The sensor data meaning processing unit 102-2 in this operation example, when the vibration continuously occurs as shown in FIG. 22B, that is, the next vibration occurs within the unit time T1 after the vibration is generated. In this case, it means “being present”, and if it does not vibrate once in unit time T2, it means “being away”. For example, it is assumed that the presence status is “being away” at time t = 0, and no vibration occurs until t = 1. From t = 1, the vibration is generated once or more per unit time T1, and “1” is notified each time, so that the sensor data meaning processing unit 102-2 assigns meaning from t = 1. The information is changed to “at present”, and the value of “at present” is notified to the meaning information management unit 103-2. As a result, the status information of the meaning information management unit 103-2 changes from “being away” to “being present”.

  After that, the vibration continues until t = 2, but if the occurrence of vibration disappears after t = 2, the sensor data meaning processing unit 102-2 changes the meaning information from “t = 2” to “being away”. Then, the value of “being away” is notified to the meaning information management unit 103-2.

  FIG. 23 shows the configuration of the sensor data meaning processing unit 102-2 that performs such an operation. As shown in FIG. 23, the sensor data meaning processing unit 102-2 includes a sensor information receiving unit 2021, a meaning processing unit 2022, a timeout detection unit 2023, a meaning information notification unit 2024, and a notification destination management unit 2025. is doing. The processing operation in this configuration is as follows.

  First, when a sensor information packet with a sensor ID of 0002 (other IDs are the same as in FIG. 12B) is received, the packet is notified to the sensor raw data extraction unit 101-2, and sensor data semantic processing is performed. “1” is notified to the unit 102-2, and the sensor information receiving unit 2021 in FIG. 23 receives “1”.

  When the sensor information receiving unit 2021 of the sensor data meaning processing unit 102-2 receives the information “1”, it notifies the meaning processing unit 2022. Upon receiving the notification “1”, the meaning processing unit 2022 resets the timer to the timeout detection unit 2023 and starts the timer. The timeout detection unit 2023 monitors the timer value until a certain period of time elapses after the timer is started. When a certain time (T1) has elapsed, the semantic processing unit 2022 is notified of a timeout.

  The semantic processing unit 2022 monitors the notification of “1” from the sensor information reception unit 2021 and the timeout notification from the timeout detection unit 2023. If the next notification of “1” is before the timeout, Semantic information is set to “present”. On the other hand, if the time-out notification comes before the next “1” notification, it is determined to be “seated”. Then, the meaning information notification unit 2024 acquires the reference information of the meaning information management unit 103-2 managed by the notification destination management unit 2025, and “seated” or “seated” is stored in the meaning information management unit 103-2. ".

  Step 7-3) When the link relationship as shown in FIG. 20B is registered in Step 7-2, the notification destination management information is registered in each functional unit as shown in FIG. Here, the reference information of the semantic information secondary processing unit 104-1 is included in the notification destination management information of the semantic information management unit 103-1, and the semantic information is included in the notification destination management information of the semantic information management unit 103-2. Register the reference information of the secondary processing unit 104-2, and further add the reference information of the semantic information tertiary processing unit 105-1 to the notification destination management information of the semantic information secondary processing unit 104-1. The reference information of the semantic information tertiary processing unit 105-1 is registered in the notification destination management information of the semantic information secondary processing unit 104-2.

  FIG. 24 shows a functional configuration of the semantic information tertiary processing unit 105. As shown in FIG. 24, the semantic information tertiary processing unit 105 includes an element incident state reception unit 1051, a binary operation processing unit 1052, an element incident state management unit 1053, and a binary operation result management unit 1054. . The semantic information secondary processing unit 104 as shown in FIG. 19 can register the semantic information tertiary processing unit 105 in the notification destination management unit 1046. Using this reference information, the analysis result notification unit 1045 of the semantic information secondary processing unit 104 notifies the semantic information tertiary processing unit 105 of the analysis result.

  Step 7-4) Information from the sensor attached to the door is given the meaning of "open" or "closed" by the sensor data meaning processing unit 102-1 as shown in FIG. Further, the information from the sensor attached to the chair is given a meaning of “seated” or “present” as shown in FIG. 22 by the sensor data significance processing unit 102-2.

  In this operation example, if the door is in the “open” state, the semantic information secondary processing unit 103-1 has an analysis result of “abnormal”, and the semantic information secondary processing unit 103-2 In the “seated” state, an analysis result “abnormal” is obtained.

  Information analyzed by each semantic information secondary processing unit is notified to the semantic information tertiary processing unit 105-1. The semantic information tertiary processing unit 105-1 uses an AND combination of the analysis results of each semantic information secondary processing unit as an analysis result, and "abnormal" is notified from all of the semantic information secondary processing units. It is set as “abnormal”. This makes it possible to detect an abnormality when the door is “open” and “seated”.

[Procedure for changing sensor type]
The system according to the present embodiment has a feature that it is not necessary to change the meaning information management unit 103, the meaning information secondary processing unit 104, and the application that uses the incident detection result even if the sensor type is changed. Have.

  The procedure for changing the sensor type will be described next. Here, the case where the vibration sensor attached to the door in order to monitor the opening and closing of the door is changed to a temperature sensor will be described. There is no change in the purpose of monitoring the opening and closing of the door.

  Step 8-1) The user deletes the link relationship between the vibration sensor and the door from the menu screen of the application displayed on the user terminal 30. That is, the link relationship “1-2” in FIG. 7B is deleted, and the link relationship between the vibration sensor and the door is deleted. Thereby, in the server apparatus 10, the sensor data meaning processing unit 102-1 associated with the vibration sensor is deleted.

  Step 8-2) The user registers the temperature sensor and the ID of the sensor from the menu screen. Accordingly, a new serial number is assigned to the temperature sensor within the application of the monitoring device 20 and the middleware of the server device 10 (for example, serial number = 10). In the server device 10, for example, a sensor raw data extraction unit 101-3 is added.

  Step 8-3) The user registers the link relationship between the temperature sensor and the door from the menu screen. If the serial number corresponding to the temperature sensor is 10 in step 8-2, the link relationship “10-3” is registered. This completes the user process.

  Step 8-4) Thereafter, the server device 10 creates a sensor data meaning processing unit 102 corresponding to the temperature sensor and the door, and registers the link relationship between the functional units. The processing procedure from here is the same as the processing from step 1-3 of the user environment registration / device information registration processing.

  In the present embodiment, the sensor data meaning processing unit 102 absorbs the difference in the output value due to the difference in the sensor, and the meaning information (opening / closing state or the like) that does not depend on the difference in the sensor. Since it can be passed to the semantic information secondary processing unit 104, it is not necessary to change the semantic information management unit 103 and the semantic information secondary processing unit 104 even if the sensor is changed.

[Operation example of location information detection]
By adopting the configuration of this embodiment, position information can be detected. An example of operation for detecting position information will be described with reference to an operation sequence shown in FIG.

  Step 9-1) When the network management unit 111 receives the sensor information packet, the sensor raw data extraction unit 101 corresponding to the ID information included in the packet is referred to the sensor data and the reader state management unit 115 via the reference. Notify information.

  Step 9-2) The sensor raw data extraction unit 101 requests location information from the reader state management unit 115.

  Step 9-3) As shown in FIG. 10B and FIG. 11, the reader state management unit 115 is linked to a place in the process of user registration, and responds to this associated place.

  Step 9-4) The sensor raw data extraction unit 101 notifies this meaning information to the meaning information management unit 103 having a correspondence relationship. Examples of things here are movable “people”, “dogs”, “cats”, “bags”, and the like. The location information includes “living room”, “entrance”, “attic” and the like.

  Step 9-5) The semantic information management unit 103 manages presence information such as “in the living room”, “in the attic”, and “does not exist” as the state of the object.

  Step 9-6) The semantic information management unit 103 notifies the semantic information secondary processing unit 104 of these “living room”, “in the attic”, and “does not exist” information. When sensor information corresponding to a certain sensor is not received for a certain period of time, it is assumed that an object linked to the sensor is “not present” within a range where radio waves reach the reader.

  Step 9-7) The analysis processing from the semantic information secondary processing unit 104 is the same as before.

  For example, if “cat” stays in the attic throughout the day, a new meaning of “abnormal” is given, and if “person” is “absent” even at midnight, Can be given a meaning.

[Operation example of incident notification]
Next, an operation example in which the application of the monitoring device 20 acquires the incident result from the server device 10 and notifies the user of the incident result will be described with reference to FIG.

  Step 10-1) In addition to the registered user ID and user email address, the incident check unit 202 of the monitoring device 20 notifies the incident notification method (for example, notification by immediate email, notification at noon, 1 It has a user information DB for managing notifications at intervals of time, etc.).

  Step 10-2) The incident check unit 202 periodically requests the incident analysis result corresponding to the user ID to the middleware of the server device 10 via the middleware communication unit 203 using the user ID. Of course, the user may request the incident analysis result from the user terminal 30.

  Step 10-3) The central unit 110 of the server apparatus 10 receives this request, searches the user request processing unit list for the user request processing unit 113 corresponding to the user ID, and requests the user request corresponding to the user ID. The processing unit 113 is requested for the incident analysis result.

  Step 10-4) The user request processing unit 113 acquires the analysis results of the all semantic information secondary processing unit and the semantic information tertiary processing unit stored in the incident list, and returns this result.

  Step 10-5) Upon acquiring this incident analysis result, the incident check unit 202 refers to the user information DB and acquires the incident notification method for the user.

  Step 10-6) Normally, “immediate notification when the incident analysis result is“ abnormal ”” is set as the incident notification method, and if the “incident analysis result is“ abnormal ””, the incident is notified to the mail server 204. Notify the analysis result (abnormal) and deliver the mail. Other notification methods include notifying the incident analysis results collectively after noon regardless of whether there is an abnormality, or notifying when an opportunity designated in advance by the user is given.

  If the notification method is specified in detail for each incident, the notification method for each incident is registered in the user information DB and referred to. The above operation is executed for the number of registered users.

(Concrete example)
A specific example in the case of performing monitoring using the system having the functions described above will be described below. In the following example, it is assumed that the middleware of the server device 10 is realized using object-oriented software technology, and each functional unit is realized by an instance generated from a class.

  The object factory instance in the following description corresponds to the functional unit generation / management unit 112 described so far, the user agent instance corresponds to the user request processing unit 113, the sensor instance corresponds to the sensor raw data extraction unit 101, The sensor meaning instance corresponds to the sensor data meaning processing unit 102, the mono instance corresponds to the meaning information management unit 103, the incident instance corresponds to the meaning information secondary processing unit 104, and the composite incident instance means Assume that the attached information tertiary processing unit 105 corresponds, the location instance corresponds to the position information detection unit 114, the reader instance corresponds to the reader state management unit 115, and the GW instance corresponds to the GW state management unit 116.

  Further, the correspondence table of each functional unit described so far is a class correspondence table that holds class names instead of the types of functional units. Note that the instance reference numbers described in each specific example are uniquely assigned to each specific example.

[Specific Example 1]
In specific example 1, an example will be described in which a vibration sensor manufactured by company A is attached to a door, and further activity analysis is performed from the door state change pattern to derive the activity status of an indoor person. This example corresponds to an example in which the activity status is monitored by attaching a vibration sensor with ID = 0001 to the door in the detailed operation example described above.

  In specific example 1, the following items are registered as the user environment.

Incident: Activity detection Object: Door Sensor: Company A vibration sensor Link relation: Door-Company A vibration sensor, activity detection-door The object factory instance of the server device 10 is a mono instance corresponding to a door based on the class correspondence table. 1 is generated, and a sensor instance 1 corresponding to the vibration sensor 1 manufactured by company A (hereinafter referred to as vibration sensor 1) is generated. In addition, an incident instance 1 corresponding to the activity detection is generated. The incident instance 1 has logic for monitoring and analyzing a change in the state of an object over a long period of time. Furthermore, the object factory instance generates a meaning instance 1 from the link relationship between the vibration sensor 1 and the door. Then, association between instances is performed. With the above processing, the generation of the user environment object shown in FIG. 28 is completed. The incident instance, location instance, thing instance, sensor instance, and meaning instance are collectively referred to as a user environment object.

  In the monitoring stage, the vibration sensor 1 vibrates by moving the door, and vibration information is notified from the vibration sensor 1 to the sensor reader. The sensor reader notifies the sensor GW, and the sensor GW notifies the server device 10 via the network.

  When the server device 10 receives the raw data of the vibration information, the server device 10 determines that the vibration information is from the vibration sensor 1 from the individual ID of the sensor stored in the raw data, and notifies the internal sensor instance 1 of the information. Subsequent processing is as described with reference to FIG.

  According to Specific Example 1, when realizing an answering machine or a monitoring service for elderly / children living alone, one day without having to check all sensor information such as door vibration that occurs many times a day. It is possible to monitor efficiently using the activity detection result in units.

  Now, even if a sensor different from the vibration sensor is applied instead of the vibration sensor, the server device only needs to change the meaning instance, and it is necessary to change to the application that uses the incident detection result as a mono instance or incident instance. There is no. Hereinafter, an example of operation when the vibration sensor is changed to a temperature sensor will be described.

[Specific example 1: When using a temperature sensor]
In this case, the link relationship between the door and the vibration sensor 1 manufactured by company A is deleted, the temperature sensor 1 manufactured by company B is registered as the sensor, and the link relationship between the door and the temperature sensor 1 manufactured by company A is registered. And the object factory instance in the server apparatus 10 deletes the sensor instance 1 corresponding to the vibration sensor 1, and deletes the meaning instance 1. Next, a sensor instance 2 corresponding to the temperature sensor 1 (hereinafter, temperature sensor 1) manufactured by company B is generated, and a meaning instance 2 is generated from the link relationship between the temperature sensor 1 and the door. In addition, by associating the instances, the user environment object of FIG. 29 is completed.

  In the monitoring stage, the temperature sensor 1 applied to the door senses temperature information periodically (for example, every few seconds) and notifies the sensor reader of the temperature value. The sensor reader notifies the sensor GW, and the sensor GW notifies the server device 10 via an NW line or the like.

  When the server apparatus 10 receives the raw data of the vibration information, the server apparatus 10 determines that the vibration information is from the temperature sensor 1 from the individual ID of the sensor stored in the raw data, and notifies the internal sensor instance 2 of the vibration information.

  As shown in FIG. 30A, the temperature information is an analog value (immovable decimal) and the unit is Celsius. The sensor instance 2 notifies the meaning instance 2 of the temperature information. As shown in FIG. 29, the meaning instance 2 accumulates temperature values for a certain time (for example, 1 hour) to obtain an average value and variance, calculates a confidence interval, and has temperature values within the upper and lower limits. In this case, the semantic information is “closed”, and “temperature” is “open” if the temperature is outside this section. Specifically, as shown in FIG. 30B, since the temperature value is within the confidence interval from time t = 0 to t = 1, it is assumed that the door state is “closed”, and t = 1. When the temperature value falls outside the confidence interval, the meaning instance 2 changes the meaning information after t = 1 to “open” and notifies the mono instance 1 of the value of “open”. As a result, the state information of the mono instance 1 changes from “closed” to “open”.

  After this, if the low temperature value continues until t = 2, and the temperature value rises into the confidence interval at t = 2, the semantic instance 2 changes the semantic information to “closed”, The value of “closed” is notified to the mono instance 1.

  Information notification and meaning detection processing between the thing instance 1 and the incident instance 1 are the same as when the vibration sensor 1 is used.

[Specific Example 2]
Next, specific example 2 will be described. In specific example 2, a case will be described in which data of the same type of vibration sensor is given to one window to mean the open / closed state of the window, and the other is given to a chair to mean the seated state.

  In specific example 2, the following items are registered as the user environment.

Object: Window, swivel chair Sensor: A company vibration sensor 1, A company vibration sensor 2
Link relationship: Window-Vibration sensor 1 manufactured by company A, Swivel chair-Vibration sensor 2 manufactured by company A
Based on the class correspondence table, the object factory instance of the server device 10 generates a mono instance 1 corresponding to the window and a mono instance 2 corresponding to the swivel chair, and corresponds to the vibration sensor 1 (hereinafter, vibration sensor 1) manufactured by A company. The sensor instance 2 corresponding to the sensor instance 1 and the vibration sensor 2 manufactured by company A (hereinafter referred to as vibration sensor 2) is generated. Furthermore, a meaning instance 1 is generated from the link relationship between the vibration sensor 1 and the window. Similarly, the meaning instance 2 is generated from the link relationship between the vibration sensor 2 and the swivel chair. Further, by creating an association between instances, the generation of the user environment object shown in FIG. 31 is completed.

  In the monitoring stage, the vibration sensor 1 vibrates by moving the window, and vibration information is notified from the vibration sensor 1 to the sensor reader. The sensor reader notifies the sensor GW, and the sensor GW notifies the server device 10 via an NW line or the like.

  When the server apparatus 10 receives the raw data of the vibration information, the server apparatus 10 determines that the vibration information is from the sensor 1 from the individual ID of the sensor stored in the raw data, and notifies the internal sensor instance 1 of the information.

  As shown in FIG. 32A, the vibration information is expressed by binary values, and is assumed to have a value of “1” at the time when the vibration occurs. The value of vibration information at other times is “0”. The sensor instance 1 notifies the meaning instance 1 of vibration information. In the meaning instance 1, as shown in FIG. 32B, the meaning information is switched at the time when the vibration is generated. As a specific example, at time t = 0, it is assumed that the window state is “closed”, and “1” is notified as vibration information at t = 1, so that the meaning instance 1 has a meaning after t = 1. The information is changed to “open”, and the value of this “open” is notified to the mono instance 1. As a result, the state information of the mono instance 1 changes from “closed” to “open”.

  Similarly, at t = 2, when a second vibration occurs and the value “1” is notified from the sensor instance 1 to the meaning instance 1, the meaning instance 1 changes the meaning information to “closed”, The value of “closed” is notified to the mono instance 1. These operations are the same as the operations shown in FIGS. The incident instance determines that the open state is abnormal.

  On the other hand, when a person uses (sits down) a chair, the vibration sensor 2 vibrates, and vibration information is notified from the vibration sensor 2 to the sensor reader. The sensor reader notifies the sensor GW, and the sensor GW notifies the server device 10 via an NW line or the like.

  When the server apparatus 10 receives the raw data of the vibration information, the server apparatus 10 determines that the vibration information is from the sensor 2 from the individual ID of the sensor stored in the raw data, and notifies the internal sensor instance 2 of the information. Subsequent “seating” and “seating” meaning processing is the same as the processing described with reference to FIG.

[Specific Example 3]
Next, specific example 3 will be described. In specific example 3, as two or more states, one assigns a sensor to a window to indicate the open / closed state of the window, and the other assigns the sensor to a person and is located inside or outside the house. An example in which abnormality determination is performed by combining these two or more states will be described.

  In specific example 3, the following items are registered as the user environment.

Item: Window, Human Sensor: A company vibration sensor 1, A company position detection sensor 2
Link relation: Window-vibration sensor 1 manufactured by company A, position detection sensor 2 manufactured by person-company A
Based on the class correspondence table, the object factory instance of the server apparatus 10 generates a mono instance 1 corresponding to a window and a mono instance 4 corresponding to a person, and corresponds to a vibration sensor 1 (hereinafter, vibration sensor 1) manufactured by A company. A sensor instance 4 corresponding to the sensor instance 1 and the position detection sensor 2 (hereinafter referred to as position detection sensor 2) manufactured by company A is generated.

  Furthermore, a meaning instance 1 is generated from the link relationship between the vibration sensor 1 and the window. Similarly, a meaning instance 4 is generated from the link relationship between the position detection sensor 2 and a person. Then, by associating the instances, the generation of the user environment object shown in FIG. 33 is completed. Note that the specific example 3 includes the action instance 1 that notifies the user in a predetermined case.

  In the monitoring stage, the vibration sensor 1 vibrates by moving the window, and vibration information is notified from the vibration sensor 1 to the sensor reader. The sensor reader notifies the sensor GW, and the sensor GW notifies the server device 10 via an NW line or the like.

  When the server apparatus 10 receives the raw data of the vibration information, the server apparatus 10 determines that the vibration information is from the sensor 1 from the individual ID of the sensor stored in the raw data, and notifies the internal sensor instance 1 of the information.

  Information held by the sensor instance 1, the meaning instance 1, the mono instance 1, and the incident instance 1 is as shown in FIGS. 32 (a) to 32 (d). In the specific example 3, when the incident instance 1 detects “abnormal”, it notifies the composite incident instance 1.

  On the other hand, the position detection sensor 2 transmits a radio signal periodically, for example, and the person who is attached to the position detection sensor 2 is in an area where the radio wave reaches the sensor reader (in the house). The reader detects the position detection sensor 2 by detecting a radio wave signal. In that case, the sensor reader notifies the update information of the position detection sensor 2 to the sensor GW, and the sensor GW notifies the server device 10.

  If the position detection sensor 2 cannot be detected by a person moving out of the area where the radio wave reaches (goes out) and the radio signal is not notified to the sensor reader from the position detection sensor 2, the sensor reader is positioned at the sensor GW. The update information of the detection sensor 2 cannot be notified, and the sensor GW cannot also notify the server device 10.

  When the server apparatus 10 receives the raw data of the update information of the position detection sensor, the server apparatus 10 determines that the update information is from the sensor 2 from the individual ID of the sensor stored in the raw data, and sends it to the internal sensor instance 4. Notice.

  The information of the position detection sensor 2 is represented by binary values as shown in FIG. 34 (a), and assumes a value of “1” at the time when the radio signal arrives. The other time values are “0”. The sensor instance 4 notifies the semantic instance 4 of the update information.

  As shown in FIG. 34 (a), the meaning instance 4 periodically changes the meaning information when the update information is received. When the radio wave signal can reach from a state where there is no update information from the position detection sensor 2 and reception of the update information occurs, it means “at home”, and when the update information cannot be received during the unit time T, “ It means “on the road”. As a specific example, it is assumed that at time t = 0, the person's whereabouts state is “going out” and no information update occurs until t = 1. Information update occurs periodically from t = 1, and “1” is notified each time, so that the semantic instance 4 changes the semantic information from “t = 1” to “at home”. The value of “at home” is notified to the mono instance 4. As a result, the state information of the mono instance 4 changes from “out of office” to “at home” (FIG. 34C).

  Thereafter, the information update continues until t = 2, but if the radio signal can no longer reach after t = 2, the semantic instance 4 changes the semantic information from “t = 2” to “going out”. The value of “medium” is notified to the mono instance 4.

  Further, as shown in FIG. 34 (d), the mono instance 4 notifies the incident instance 2 of “out of office” and “at home” information. When incident instance 2 is “out of office” as an elemental incident, an abnormal value is assumed to be “abnormal” when t = 0 to t = 1, and t = 2, and this is notified to composite incident instance 1.

  The composite incident instance 1 notifies the action instance 1 when “abnormal” is an AND condition as values of a plurality of incident instances. If the process of action instance 1 is a notification of incidents to a user to a mobile mail, the incident is notified to the user's mobile phone only when “abnormal” information notification is received from incident instance 1 and incident instance 2.

  In specific example 3, when the values of incident instance 1 and incident instance 2 are both abnormal, that is, when the person is “going out” but the window is “open”, the mobile mail is notified. .

[Specific Example 4]
Next, specific example 4 will be described. In specific example 4, as two or more states, one assigns a sensor to the availability sensor of the water station to imply the availability of the water station, and the other assigns it to the river and An example will be described in which whether or not the amount of water is sufficient (usable situation) is used, and abnormality determination is performed by combining these two or more states.

  In specific example 4, the following items are registered as the user environment.

Object: Waterworks Bureau, River Sensor: Operation Rate Measurement Sensor, Water Level Sensor Sensor Link Relationship: Waterworks Bureau-Occupancy Rate Measurement Sensor, River-Water Level Sensor Sensor The object factory instance of the server device 10 is based on the class correspondence table. A corresponding mono-instance 5 and a mono-instance 6 corresponding to a river are generated, a sensor instance 2 corresponding to an operation rate measurement sensor (hereinafter referred to as an operation rate sensor), and a sensor instance 1 corresponding to a water level sensor (hereinafter referred to as a water level sensor). Is generated.

  Furthermore, the meaning instance 2 is generated from the link relationship between the operation rate sensor and the water station. Similarly, the meaning instance 3 is generated from the link relationship between the water level sensor 1 and the river. Then, by associating the instances, the generation of the user environment object in FIG. 35 is completed.

  In the monitoring stage, the operation status of the water department is periodically notified from the operation rate sensor to the sensor reader. The sensor reader notifies the sensor GW, and the sensor GW notifies the server device 10 via an NW line or the like.

  When the server device 10 receives the raw data of the operation rate information, the server device 10 determines that the vibration information is from the operation rate sensor based on the individual ID of the sensor stored in the raw data, and notifies the internal sensor instance 2 of the vibration information. .

  As shown in FIG. 36A, the operation rate information is expressed as an analog value, and the operation rate (utilization rate) is periodically transmitted. The sensor instance 2 notifies the associated meaning instance 2 of the operation rate information. As illustrated in FIG. 36B, the meaning instance 2 determines that “the operation rate is high” when the operation rate exceeds a certain value (for example, 80%). As a specific example, at time t = 0, “operating rate is high”, and when t = 1, a value smaller than the threshold value is notified as operating rate information, so that the semantic instance 2 has semantic information after t = 1. Is changed to “low operation rate”, and the value of “low operation rate” is notified to the mono instance 5. As a result, the state information of the mono-instance 5 changes from “high operation rate” to “low operation rate”.

  Similarly, at t = 2, if the value of the operating rate exceeds the threshold value and the value “high operating rate” is notified from the sensor instance 2 to the semantic instance 2, the semantic instance 2 displays the semantic information as “operating rate”. Change to “high”, and notify the mono instance 5 of the value of “high availability”.

  Further, as shown in FIG. 36 (d), the mono instance 5 notifies the incident instance 3 of “high operation rate” and “low operation rate” information. Incident instance 3 is an abnormal value when it is “high availability” as an element incident, and when t = 0 to t = 1 and t = 2 to t = 3, it is assumed to be “abnormal”, and this is designated as composite incident instance 1. Notice.

  On the other hand, the water level status of the river is periodically notified from the water level sensor to the sensor reader. The reader notifies the sensor GW, and the sensor GW notifies the server device 10 via an NW line or the like.

  When the server device 10 receives the raw data of the water level information, the server device 10 determines that the information is from the water level sensor from the individual ID of the sensor stored in the raw data, and notifies the internal sensor instance 1 of the information.

  As shown in FIG. 37A, the sensor information is represented by an analog value, and the water level information is periodically transmitted. The sensor instance 1 notifies the meaning level instance 3 of the water level information. If the meaning instance 3 exceeds a certain value (for example, 30 cm) as shown in FIG. 37B, it is determined that the water level is high. As a specific example, at time t = 0, “water level is high”, and when t = 1, a value smaller than the battle value is notified as the water level information, so that the meaning instance 3 has the meaning information after t = 1. Change to “low water level” and notify the mono instance 6 of this “low water level” value. Thereby, the state information of the mono-instance 6 changes from “high water level” to “low water level”.

  Similarly, at t = 2, when the value of the water level exceeds the threshold value and the value “high water level” is notified from the sensor instance 1 to the semantic instance 3, the semantic instance 3 sets the semantic information to “high water level”. And the value of “high water level” is notified to the mono instance 6.

  Also, as shown in FIG. 37 (d), the mono instance 6 notifies the incident instance 4 of “high water level” and “low water level” information. If the incident instance 4 has an abnormal value when the water level is low as an elemental incident, t = 1 to t = 2 and t = 3.

  The composite incident instance 1 notifies the action instance 2 when “abnormal” is an AND condition as values of a plurality of incident instances. If action instance 2 is an alarm buzzer, an incident will be notified to the user's mobile phone only when an “abnormal” information notification is received from incident instance 3 that detects an abnormality in operating rate and incident instance 4 that detects an abnormality in water level. Is done. In other words, the alarm buzzer sounds when the operation rate of the Waterworks Bureau is high and the river level is low.

[Specific Example 5]
As an example of using a complex incident, the following monitoring is also possible.

  By installing temperature sensors at a plurality of locations (for example, 20 locations) in the greenhouse and registering 20 temperature sensors, 20 sensors and mono-instances are made. Assume that incident instances are linked to each of them, and “abnormal” occurs when the temperature falls below 10 degrees. Note that the class that is the basis of the incident instance in this case is instantiated as an instance corresponding to each sensor and thing, and has a logic to set a certain temperature as a parameter and detect “abnormal” when the temperature falls below that temperature. is doing.

  Then, a composite incident that collects these 20 incidents is registered. The class corresponding to this composite incident has a logic of a composite method for determining “abnormal” when 10 or more out of 20 incidents become “abnormal”. As a result, the temperature of the entire greenhouse can be collected and managed abnormally, and even if several temperature sensors break down, it is possible to avoid erroneous detection by collecting them all together. As a similar example, combining door opening / closing and chair presence / absence information is also effective in improving the accuracy of detecting the presence / absence of a person.

[Effects of the system described in the embodiment]
As described above, according to the present system, the sensor is not limited to a specific application, and the same type of sensor can be used for various purposes such as presence detection, window opening / closing detection, and operation detection of electrical equipment. It becomes possible.

  Also, when the sensor type or model number is changed while using the service, the user only has to re-register the sensor type, model number, and serial number from the menu screen.

  In addition, information from a large number of sensors can be efficiently confirmed by collecting or aggregating the information, and can be provided as information that can be easily understood by human senses. Furthermore, it becomes possible to correct erroneous detection of individual sensors using a large number of sensors.

  The present invention is not limited to the above-described embodiment, and various modifications and applications can be made within the scope of the claims.

It is a figure which shows schematic structure of the system in embodiment of this invention. It is a functional block diagram of a server apparatus and a monitoring apparatus. It is a figure which shows cooperation between the function parts when registering a user environment. It is a figure explaining the meaning of the broken-line arrow of FIG. It is an example of a user environment. It is a figure which shows various function part corresponding | compatible tables. It is an example of a link relation, a sensor data meaning processing unit generated at the time of link relation registration, and registered notification destination management information. It is a figure which shows various function part corresponding | compatible tables. It is a figure which shows the cooperation between function parts when registering the link relation of a user environment. It is a figure which shows the example of the user apparatus information etc. which are registered into a system. It is a figure which shows cooperation between function parts when registering a user's NW apparatus. It is a figure which shows the sensor information packet notified to a server apparatus from NW apparatus. It is a figure for demonstrating operation | movement of the network management part at the time of sensor information packet reception. It is a block diagram of a network management part. It is a block diagram of the sensor raw data extraction part 101-1. It is a figure for demonstrating a detailed operation example. It is a block diagram of the sensor data meaning process part 102-1. It is a block diagram of the meaning information management part 103-1. It is a block diagram of the sensor data meaning process part 102-2. It is an example of the user environment containing a composite incident. It is an example of the management information of a notification destination management part including the meaning information tertiary processing part 105-1. It is a figure for demonstrating a detailed operation example. It is a block diagram of the meaning information secondary process part 104-1. It is a block diagram of the meaning information tertiary processing part 105-1. It is a figure for demonstrating a detailed operation example. It is a processing sequence in the case of performing position detection from sensor information. It is a processing sequence for acquiring an incident analysis result. It is a figure which shows the user environment object of the specific example 1. It is a figure which shows a user environment object in the case of using a temperature sensor in the specific example 1. It is a figure for demonstrating the processing content in the case of using a temperature sensor in the specific example 1. FIG. It is a figure which shows the user environment object of the specific example 2. It is a figure for demonstrating the processing content in the specific example 2. FIG. It is a figure which shows the user environment object of the specific example 3. It is a figure for demonstrating the processing content in the specific example 3. FIG. It is a figure which shows the user environment object of the specific example 4. It is a figure for demonstrating the processing content in the specific example 4. FIG. It is a figure for demonstrating the processing content in the specific example 4. FIG.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 Server apparatus 101 Sensor raw data extraction part 102 Sensor data meaning processing part 103 Semantic information management part 104 Semantic information secondary processing part 105 Semantic information tertiary processing part 110 Supervision part 111 Network management part 112 Object generation / Management unit 113 User request processing unit 114 Location information detection unit 115 Reader state management unit 116 GW state management unit 20 Monitoring device 201 User interface unit 202 Incident check unit 203 Middleware communication unit 204 Mail server 30 User terminal

Claims (12)

A sensor information conversion device that converts sensor data received from a sensor into information for providing to a user,
Sensor data conversion means for converting sensor data received from the sensor into state information representing a state corresponding to the measurement target of the sensor;
A sensor information conversion device comprising: state information conversion means for converting the state information into information representing a predetermined event determined from the state information.   The sensor data conversion unit is selected from a plurality of sensor data conversion units as a unit corresponding to a set of a type of the sensor and a type of measurement target of the sensor. The sensor information conversion apparatus according to 1.   3. The apparatus according to claim 2, further comprising: a unit that determines a type of the sensor and a type of a measurement target of the sensor based on sensor data received from the sensor and selects a sensor data conversion unit corresponding to the set. The sensor information conversion device described in 1.   In response to receiving registration of the sensor type and the measurement target type of the sensor, the sensor data conversion means corresponding to the set of the sensor type and the measurement target type of the sensor is selected. The sensor information conversion apparatus according to claim 2.   Accept registration to change sensor type or measurement target type, use sensor data conversion means corresponding to the combination of sensor type and measurement target type after change instead of sensor data conversion means before change The sensor information conversion apparatus according to claim 2, wherein:   The state information conversion unit is selected from a plurality of state information conversion units as a unit corresponding to a set of the predetermined event and the type of measurement target of the sensor. The sensor information conversion apparatus according to 1.   In response to accepting registration of the predetermined event and the type of measurement target of the sensor, there is provided means for selecting a state information conversion unit corresponding to a set of the predetermined event and the type of measurement target of the sensor. The sensor information conversion apparatus according to claim 6.   The sensor information conversion device holds the identification information of the sensor reader and the location information of the sensor reader in association with each other, and when the sensor data including the identification information of the sensor reader is received, the location information corresponding to the identification information The sensor information conversion apparatus according to claim 1, further comprising means for notifying the state information conversion means as the state information. When there are a plurality of sets of sensors and measurement targets, the sensor information conversion device includes a plurality of sensor data conversion means corresponding to the plurality of sets,
2. The sensor information according to claim 1, wherein the state information conversion unit obtains information representing the predetermined event by converting a plurality of state information obtained by the plurality of sensor data conversion units. Conversion device.   The apparatus according to any one of claims 1 to 9, further comprising means for notifying the user of information representing the predetermined event corresponding to the user when it is determined that the trigger has been designated in advance by the user. The sensor information conversion apparatus according to Item 1. A sensor information conversion method executed by a sensor information conversion device that converts sensor data received from a sensor into information for providing to a user,
A sensor data conversion step for converting sensor data received from the sensor into state information representing a state corresponding to the measurement target of the sensor;
A state information conversion step of converting the state information obtained by the sensor data conversion step into information representing a predetermined event determined from the state information. A sensor information notification method executed by a sensor information notification system for converting sensor data received from a sensor into information for notifying the user and notifying the user,
Receiving registration information including a set of a sensor type and a measurement target type of the sensor;
Selecting from a plurality of sensor data conversion means sensor data conversion means corresponding to a set of the sensor type and the measurement target type of the sensor based on the registration information;
Converting the sensor data received from the sensor by the selected sensor data conversion means into state information representing a state corresponding to the measurement target of the sensor;
Converting the state information into information representing a predetermined event determined from the state information, and holding the information in a storage device;
And a step of notifying the user of information representing the predetermined event corresponding to the user when it is determined that the trigger has been designated in advance by the user.

Images