US20060161645A1 - Sensor network system and data retrieval method for sensing data - Google Patents

Sensor network system and data retrieval method for sensing data Download PDF

Info

Publication number
US20060161645A1
US20060161645A1 US11/211,467 US21146705A US2006161645A1 US 20060161645 A1 US20060161645 A1 US 20060161645A1 US 21146705 A US21146705 A US 21146705A US 2006161645 A1 US2006161645 A1 US 2006161645A1
Authority
US
United States
Prior art keywords
data
sensor
information
user terminal
data processing
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US11/211,467
Other languages
English (en)
Inventor
Norihiko Moriwaki
Toshiyuki Odaka
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hitachi Ltd
Original Assignee
Hitachi Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hitachi Ltd filed Critical Hitachi Ltd
Assigned to HITACHI, LTD. reassignment HITACHI, LTD. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: MORIWAKI, NORIHIKO, ODAKA, TOSHIYUKI
Publication of US20060161645A1 publication Critical patent/US20060161645A1/en
Priority to US11/727,039 priority Critical patent/US8671136B2/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling

Definitions

  • This invention relates to a technology of using information supplied by a large number of sensors connected with the network.
  • the Internet and other networks have been used in recent years mainly for accessing documents, images, movies, sounds or other stored contents through search engines or previously set links. In other words, the technology of accessing the stored contents has been nearly completed.
  • a technology of transmitting the current information is streaming technology made up of continuously transmitting images captured by a camera installed at a fixed position (web camera).
  • sensor network technology of acquiring through a network sensing data acquired from a large number of small wireless sensor nodes is developing (JP 2002-006937 A, JP 2003-319550 A, JP 2004-280411 A, U.S. Patent Application Publication 2004/0093239 Specification, and U.S. Patent Application Publication 2004/0103139 Specification).
  • JP 2002-006937 A, JP 2003-319550 A, JP 2004-280411 A, U.S. Patent Application Publication 2004/0093239 Specification, and U.S. Patent Application Publication 2004/0103139 Specification In recent years, the expectation is growing high for a sensor network system enabling to capture real-world information through sensors and using this information at a remote place through a network.
  • the present service on the Internet is closed to services on a virtual space
  • the essential difference of the sensor network from the present Internet is that it is fused with the real world.
  • the possibility of realizing fusion with the real world enables to provide a variety of services dependent on time, location and other situation.
  • the connection of a large variety of objects present in the real world with a network enables to realize traceability and to address to the social needs for securing “safety” in a wide sense and to the needs of “improving efficiency” in inventory control and office work.
  • the search engine shown in the related art indicated above enables to find out the position (address) in the network concerned of the data stored in the past, there is a problem in that it is not suited to efficient retrieval of real-time information from a huge amount of sensor information connected with the network concerned and for the retrieval of changes in information.
  • the object of this invention is to realize a sensor network system capable of easily retrieving real-time information from a large number of sensors connected with the network concerned.
  • This invention includes distributed servers for storing the data transmitted from plural sensor nodes and a management server connected thereto through the first network and the user terminals, and the management server has a model table containing previously set model names and the information link pointers indicating the link pointer of the data corresponding to the model names.
  • the data acquired from the sensors is collected only by the distributed servers, while the management server manages only the positions of collecting data from the sensors, and the data meeting the requests of the user terminals is retrieved by the distributed servers and are provided.
  • the data acquired from the sensors is collected by the distributed servers, the locations of the sensor data are managed by the management server, the user terminals request data from the management server, and the management server acquires the data requested by the distributed servers.
  • This will prevent the load on the management server from getting excessively large because no data will be stored in the management server even if the number of sensors turns out to be huge.
  • it will be possible to provide easily and quickly necessary information for the users by restricting any excessive growth of the traffic on the network with which the management server, the distributed servers and the user terminals are connected while using a large number of sensors.
  • FIG. 1 is a block diagram showing the system of the sensor network representing the first embodiment of this invention
  • FIG. 2 is a functional block diagram of the sensor network
  • FIG. 3 is a block diagram showing an example of wireless sensor node WSN
  • FIG. 4 is a graph showing the operating condition of the wireless sensor node and shows the relationship between time and power consumption
  • FIG. 5 is an illustration showing an example of the disposition of wireless sensor nodes
  • FIG. 6 is a block diagram showing the relationship between the objects and the measured data of sensor nodes, and shows the starting time of measurement;
  • FIG. 7 is a block diagram showing the relationship between the objects and the measured data of sensor nodes, and shows the state when a predetermined time has passed from the start of the measurement;
  • FIG. 8 is a graph showing the relationship between the data amount of the objects, the amount of measured data of the sensor nodes and time;
  • FIG. 9 is a block diagram showing the event-action controller of the distributed data processing server DDS.
  • FIG. 10 is a detailed description of the event table
  • FIG. 11 is a block diagram showing the essential parts of the directory server DRS.
  • FIG. 12 is a detailed description of the sensor information table
  • FIG. 13 is a detailed description of the attribute interpretation list
  • FIG. 14 is a block diagram showing the relationship between the real-world model list and the distributed data processing server DDS;
  • FIG. 15 is a detailed description of the model binding list
  • FIG. 16 is a time chart showing the steps of registering the sensor information
  • FIG. 17 is a data format for registering sensor nodes
  • FIG. 18 is a time chart showing the steps of registering the real-world model list
  • FIG. 19 is a time chart showing the steps of registering the model binding list
  • FIG. 20 is a time chart showing an example of responses to the access to the model binding list
  • FIG. 21 is a detailed description of the steps required when the position of Mr. Suzuki is designated from the model binding list;
  • FIG. 22 is a detailed description of the steps required when the seated state of Mr. Suzuki is designated from the model binding list;
  • FIG. 23 is a detailed description of the steps required when the temperature of Mr. Suzuki is designated from model binding list;
  • FIG. 24 is a detailed description of the steps required when the members of the meeting room A are designated from the model binding list;
  • FIG. 25 is a detailed description of the steps required when the number of persons in the meeting room A is designated from the model binding list;
  • FIG. 26 is a block diagram of the action controller ACC of the directory server DRS;
  • FIG. 27 is a timing chart showing the steps of registering an action table
  • FIG. 28 is an illustration of the screen setting the actions displayed in the user terminal UST at the time of registering the action table
  • FIG. 29 is also an illustration of the screen setting actions
  • FIG. 30 is a detailed description showing entries in the event table of the distributed data processing server DDS.
  • FIG. 31 is a detailed description showing entries in the action table of the directory server DRS.
  • FIG. 32 is a time chart showing the sequence of setting a single action
  • FIG. 33 is a time chart showing the sequence of responding a single action
  • FIG. 34 is an illustration of the screen for setting actions displayed on the user terminal UST when a single action with plural events is to be registered;
  • FIG. 35 is also an illustration of the screen for setting actions displayed on the user terminal UST when a single action with plural events is to be registered;
  • FIG. 36 is a detailed description showing entries in the event table of the distributed data processing server DDS- 1 ;
  • FIG. 37 is a detailed description showing entries in the event table of the distributed data processing server DDS- 2 ;
  • FIG. 38 is a detailed description showing entries in the action table of the directory server DRS.
  • FIG. 39 is a time chart showing the sequence of setting an action with plural events.
  • FIG. 40 is a time chart showing the sequence of responding plural events
  • FIG. 41 is a block diagram showing the event-action controller of the distributed data processing server DDS representing the second embodiment
  • FIG. 42 is an illustration of the screen for setting actions displayed on the user terminal UST when actions are to be registered
  • FIG. 43 is a description showing entries in the event-action table of the distributed data processing server DDS.
  • FIG. 44 is a time chart showing the sequence of setting actions
  • FIG. 45 is a time chart showing the sequence of responding to plural events and actions
  • FIG. 46 is a block diagram showing the system of a sensor network representing a first variant
  • FIG. 47 is also a block diagram showing the system of a sensor network representing the first variant
  • FIG. 48 is a block diagram showing the system of a sensor network representing a second variant.
  • FIG. 1 is an illustration of the basic configuration of the sensor network system showing the first embodiment of this invention.
  • the wireless sensor nodes (WSN) and the wireless mobile sensor nodes (MSN) are nodes installed at predetermined positions, or fixed on a predetermined objects or persons, to gather information on the environment or information on the objects to which they are fixed, and to transmit the information to the base stations BST- 1 to BST-n.
  • the sensor nodes are made up of wireless sensor nodes WSN and MSN connected by wireless communication with the base stations BST- 1 to BST-n and wired sensor nodes FSN connected by wired communication with the network NWK-n.
  • the wireless sensor nodes WSN installed at fixed locations, for example with their sensor sensing the surrounding situation at regular intervals, transmit the sensing information to the base station BST previously set.
  • the wireless mobile sensor nodes MSN are designed to be mobile being carried by a person or on a car and transmit information to the nearest base stations BST.
  • WSN or MSN when the term represents the whole (generic term) wireless sensor nodes, it will be represented by the acronym WSN or MSN, and when it represents specific wireless sensor nodes, it will be represented by the acronym plus extensions such as WSN- 1 to WSN-n or MSN- 1 to MSN-n.
  • Other elements will also be represented likewise without any extension when the whole generic name is indicated, and when specific elements are indicated, they will be represented by the acronym plus extensions “ ⁇ 1 to n”.
  • Each base station BST- 1 to BST-n is connected with one or plural wireless sensor node or nodes WSN or MSN, and each base station BST- 1 to BST-n is connected with a distributed data processing server DDS- 1 to BST-n for collecting data transmitted by each sensor node through the network NWK- 2 to BST-n.
  • the network NWK- 2 to BST-n is designed to connect the base stations BST and the distributed data processing servers (distributed servers) DDS.
  • the distributed data processing server DDS may vary the number of connections depending on the required scale of the system.
  • Each distributed data processing server DDS- 1 to DDS-n having a disk drive DSK for storing the data received from the wireless and wired sensor nodes (simply referred to hereinafter as “sensor node”), a CPU (not shown) and a memory executes a specified program, collects measured data transmitted by the sensor nodes as described below, and makes various steps such as data storage, data processing, and transmission of notices and data to a directory server (management server) DRS or other servers through the network NWK- 1 according to the conditions previously prescribed.
  • the network NWK- 1 is formed of a LAN, the Internet and the like.
  • the data collected from the sensor nodes contains the proper ID for identifying the sensor nodes and numerical data.
  • the numerical data may come with a time stamp to indicate when the data is sensed.
  • the directory server DRS converts the output data of the sensor node into a real-world model that users can understand (person, object, state and the like) based on a definition previously set and present the result to the user.
  • the wired sensor nodes FSN may be connected with the distributed data processing servers DDS- 1 to DDS-n.
  • the wired sensor nodes FSN may be connected with the base stations BST, and the base stations BST may manage the wired sensor nodes FSN in the same way as the wireless sensor nodes.
  • the network NWK- 1 is connected with a directory server DRS for managing the real-world models related with the sensing information transmitted from the distributed data processing servers DDS, user terminals UST using the information of this directory server DRS, and an operation terminal ADT for setting and operating the directory server DRS, the distributed data processing server DDS and the base stations BST, and the sensor nodes.
  • a directory server DRS for managing the real-world models related with the sensing information transmitted from the distributed data processing servers DDS
  • user terminals UST using the information of this directory server DRS
  • an operation terminal ADT for setting and operating the directory server DRS, the distributed data processing server DDS and the base stations BST, and the sensor nodes.
  • separate operation terminals may be provided respectively for the sensor managers who manage the sensor nodes and the service managers who manage the service of the sensor network.
  • the directory server DRS provided with a CPU (not shown), a memory and a storage system executes the specified program and manages the objects related with meaningful information as described below.
  • the directory server DRS accesses the distributed data processing servers DDS- 1 to DDS-n having measured data corresponding to the real-world model, acquires the corresponding measured data, converts the sensing data if necessary into a form understandable for the users and display the result on the user terminals UST.
  • FIG. 2 is a functional block diagram of the sensor network shown in FIG. 1 .
  • the structure of the distributed data processing server DDS- 1 only from among the distributed data processing servers DDS- 1 to DDS-n shown in FIG. 1 and only the structure of the base station BST- 1 from among the base stations BST- 1 to BST-n connected with the distributed data processing servers DDS- 1 .
  • Other distributed data processing servers DDS and other base stations BST are similarly structured.
  • the base station BST- 1 for collecting data from the wireless sensor nodes WSN, MSN and wired sensor nodes FSN includes a command controller CMC-B, a sensor node manager SNM, and an event monitor EVM.
  • the sensor nodes transmit measured data by attaching the previously set ID thereto.
  • the command controller CMC-B exchanges commands with the command controller CMC-D of the distributed data processing server DDS- 1 as described below. For example, in response to a command issued by the distributed data processing server DDS- 1 , the command controller CMC-B sets the parameters of the base station BST- 1 and transmits the state of the base station BST- 1 to the distributed data processing server DDS- 1 . Or it sets the parameters of the sensor nodes managed by the base station BST- 1 and transmits the state of the sensor nodes to the distributed data processing server DDS- 1 .
  • the sensor node manager SNM maintains the management information (operating condition, residual power and the like) of the sensor nodes under its management. And when an inquiry has been received from the distributed data processing server DDS- 1 on sensor nodes, the sensor node manager SNM provides the management information instead of and for each sensor node.
  • the sensor nodes can reduce their own processing load by assigning the processing load related to management to the base station BST and can limit any unnecessary power consumption.
  • the sensor node manager SNM updates the management information of sensor nodes and informs the distributed data processing server DDS- 1 of any anomaly that occurred in any of the sensor nodes.
  • An anomaly in sensor node includes the case of no response from the sensor nodes, the case where the power supply to the sensor nodes has fallen below the previously set value and other situations in which the sensor node function is interrupted or comes to a halt.
  • the sensor node manager SNM Upon receipt of a command (setting of output timing) from the command controller CMC-D to the sensor nodes, the sensor node manager SNM transmits this command to the sensor nodes to set the output timing, and upon receipt of a notice showing the completion of setting from the sensor nodes, the sensor node manager SNM updates the management information of sensor nodes.
  • the output timing of sensor nodes indicates, for example, the interval between cyclical transmissions of data from the wireless sensor nodes WSN to the base station BST- 1 .
  • the base station BST manages the previously set wireless sensor nodes WSN, MSN and wired sensor nodes FSN under its control, and transmits the data measured by each sensor node to the distributed data processing server DDS.
  • the distributed data processing server DDS- 1 includes a disk drive DSK used for a database DB, a command controller CMC-D described below, an event action controller EAC, and a database controller DBC.
  • the command controller CMC-D communicates with the base station BST and the directory server DRS described below to transmit and receive commands and the like.
  • the event action controller EAC Upon receipt of measured data from the sensor nodes through the base station BST, the event action controller EAC acquires ID corresponding to the measured data or data ID, reads the rule of event corresponding to the data ID from the table described below (event table ETB in FIG. 10 ) and judges whether an event corresponding to the value of the measured data has occurred or not. And the event action controller EAC takes an action corresponding to the occurrence of an event corresponding to the data ID.
  • the sensor node ID for identifying the sensor node can be used for the data ID.
  • the actions taken include the transformation of measured data (raw data) into secondary data (processed data) based on the rule set in advance by the user and the like for each data ID, the storage of the measured data and secondary data into the database DB through the database controller DBC, or the notification of the same to the directory server DRS and the like.
  • FIG. 1 shows, the disposition of plural distributed data processing servers DDS concentrating regionally (or locally) some of them against plural base stations BST enables to process separately at different locations information supplied by a large number of sensor nodes.
  • a distributed data processing server DDS may be installed on each floor, and in factories a distributed data processing server DDS may be installed in each building.
  • the disk drive DSK of the distributed data processing server DDS- 1 stores as databases DB the measured data of the sensor nodes WSN, MSN, and FSN that has been received from the base stations BST, secondary data that has been acquired by processing this measured data, and device data relating to the base stations BST.
  • the database controller DBC of the data processing server DDS- 1 stores the measured data outputted by the sensor nodes transmitted by the event action controller EAC in its database DB. And if necessary it stores the secondary data produced by value processing the measured data or fusing with other data in its database DB. Incidentally, it updates device data as required from time to time in response to the request of operation terminal ADT and the like.
  • the directory server DRS for managing plural distributed data processing servers DDS includes a session controller SES for controlling communications from the user terminals UST or operation terminals ADT connected through the network NWK- 1 as stated later on, a model manager MMG, a real-world model table MTB, a system manager NMG, an action controller ACC and a search engine SER.
  • the model manager MMG manages by using a real-world model list MDL having set the correlation between the real-world models (objects) understandable for the user and the measured data or secondary data collected by the distributed data processing servers DDS from the sensor nodes set in the real-world model table MTB.
  • the directory server DRS also manages the position information of location (URL and other links) of measured data or secondary data corresponding to the real world model.
  • the user can access directly the constantly changing measurement information of the sensor nodes by designating the real world model. While the measured data of the sensor nodes and secondary data increase as the time passes, the real-world model information remains unchanged in its dimension even after the passage of the time, and only its contents change. We will describe the details of this real-world model later on.
  • the real-world model table MTB is stored in the predetermined storage system (not shown in any figure) of the directory server DRS.
  • the action controller ACC of the directory server DRS communicates with the event action controller EAC and the command controller CMC-D of the distributed data processing servers DDS, and receives the event action setting requests outputted by the user terminals UST and the operation terminals ADT. Then it analyzes the details of the event or action it had received, and sets the distribution of functions between the directory server DRS and the distributed data processing servers DDS- 1 to DDS-n corresponding to the analysis results.
  • an action or an event may sometimes relate not only to a distributed data processing server DDS but also plural distributed data processing servers DDS- 1 to DDS-n.
  • the search engine SER refers the real-world model table MTB based on the search requests for the objects received by the session controller SES, and searches the database DB of the distributed data processing servers DDS.
  • the search engine SER relates the database DB to the contents of the query, converts the query to the SQL (structured query language) and carries out the search.
  • the database DB to be searched may sometimes cover plural distributed data processing servers DDS.
  • this query relates to “the acquisition of the latest data (snapshot/stream).”
  • “the acquisition of the latest data (stream)” relates to the action setting of the action controller ACC.
  • the system manager NMG globally manages the distributed data processing servers DDS connected with the network NWK- 1 and constituting the sensor network, the base stations BST connected with the distributed data processing servers DDS and the sensor nodes connected with the base stations BST.
  • the system manager NMG provides an interface related with the registration and retrieval of the distributed data processing servers DDS, the base stations BST and the sensor nodes to the operation terminals ADT and the like, and manages the condition of each device and the condition of the sensor nodes.
  • commands issued by the system manager NMG through the command controller CMC-D include reset, set parameters, delete data, transmit data, set standard-type event-action, and the like.
  • FIGS. 3 to 5 An example of sensor node will be shown in FIGS. 3 to 5 .
  • the RF processor WPR transmits the commands and the like received from the base stations BST to the controller CNT, and the controller CNT analyzes the commands received and proceeds to the predetermined processing (e.g., change of setting and the like).
  • the controller CNT transmits the information on the remaining power (or amount of electric charges made) of the power supply unit POW to the base stations BST through the RF processor WPR.
  • the controller CNT itself monitors the remaining power (or the amount of electric charges) of the power supply unit POW, and when the remaining power has fallen below the previously set value, the controller CNT may warn the base stations BST that power supply is about to run out.
  • the RF processor WPR is operated intermittently to reduce power consumption.
  • the controller CNT stops driving the sensors SSR and switches from a sleep state to an operating state at a predetermined timing to drive the sensors SSR and transmits the measured data.
  • a battery may be used for the power supply unit POW, or solar cell, vibrational energy generation or other similar energy generation units may be used.
  • the wireless mobile sensor node MSN may be designed in the same way as shown in FIGS. 3 and 4 .
  • FIG. 5 is a detailed illustration showing an example of sensor nodes connected with the distributed data processing server DDS- 1 shown in FIGS. 1 and 2 above.
  • a base station BST- 0 In the office, a base station BST- 0 is installed, and a wireless sensor node WSN- 0 having a pressure switch as a sensor SSR is installed on the chair in the office.
  • the wireless sensor node WSN- 0 is set to communicate with the base station BST- 0 .
  • a base station BST- 1 is installed in the meeting room A, and the wireless sensor nodes WSN- 3 to WSN- 10 respectively having a pressure switch as a sensor SSR are installed on the chairs of the meeting room A. Furthermore, the meeting room A is provided with a wired sensor node FSN- 1 having a temperature sensor, and the wired sensor node FSN- 1 is connected with the base station BST- 1 . Each of the wireless sensor nodes WSN- 3 to WSN- 10 and the wired sensor node FSN- 1 are set in such a way that they can communicate with the base station BST- 1 .
  • a base station BST- 2 is installed in the meeting room B, and the wireless sensor nodes WSN- 11 to WSN- 17 respectively having a pressure switch as a sensor SSR and the wired sensor node FSN- 2 having a temperature sensor are installed on the chairs of the meeting room B. These sensor nodes are connected with the base station BST- 2 .
  • the employees using the office, the meeting rooms A and B are required to wear a wireless mobile sensor node MSN- 1 serving as their identification card.
  • the wireless mobile sensor node MSN- 1 is constituted as an identification card with a temperature sensor SSR- 1 for measuring the temperature of the employee (or the ambient temperature) and a tag TG- 1 storing the proper identifier of the employee (employee ID).
  • the wireless mobile sensor node MSN- 1 can transmit the employee ID and the measured temperature data to the base stations BST- 0 , 1 or 2 .
  • the directory server DRS has formed in advance the following objects as the real-world model, and defines the same in the real-world model list MDL of the real-world model table MTB.
  • Mr. Suzuki is an employee using the office or the meeting rooms A and B shown in FIG. 5 , and that he is wearing a wireless mobile sensor node MSN- 1 shown in FIG. 5 and FIG. 6 .
  • the sensor information table STB of FIG. 12 shows, the sensor information table is defined in such a way that the measured data (e.g. temperature) and position information of each sensor node MSN may be stored in the distributed data processing server DDS designated as the data link pointer.
  • the position information of the sensor node MSN may be acquired as the ID information of the base station BST that detects the sensor node MSN.
  • the real-world model list MDL of the real-world model table MTB contains a definition that the object representing the position of Mr. Suzuki (OBJ- 1 ) is an object actually located in the link pointer named measured data 1 (LINK- 1 ), and thus manages the relationship of correspondence between the real-world model and the actual data position.
  • the object representing the position of Mr. Suzuki (OBJ- 1 ) in the real-world model list MDL is related with the storage position of the distributed data processing server DDS corresponding to the measured data 1 (LINK- 1 ).
  • the position information given by the wired mobile sensor node MSN- 1 indicating the position of Mr. Suzuki is stored in the disk drive DSK 1 of the distributed data processing server DDS.
  • Mr. Suzuki's position (OBJ- 1 ) seems to be stored in the real-world model table MTB of the directory server DRS.
  • the actual data is stored not in the directory server DRS, but in the disk drive DSK 1 previously set of the distributed data processing server DDS.
  • the object representing the members of the meeting room A (OBJ- 4 ) will be defined in the real-world model table MTB in such a way that the name of employee acquired from the information of the wireless mobile sensor node MSN connected with the base station BST- 1 of the meeting room A may be stored in the measured data 4 (LINK- 4 ). If no pressure switch (WSN- 3 to WSN- 10 ) is used, the number of persons in the meeting room A may be calculated from the number of the wireless mobile sensor nodes MSN detected by the base station BST- 1 in the meeting room A. Further, the distributed data processing servers DDS corresponding to the measured data 4 and the storage position will be defined. In FIGS. 6 and 7 , the individual information acquired from the wired mobile sensor node MSN of each employee will be stored in the disk drive DSK 4 of the distributed data processing server DDS.
  • the object representing the members of the meeting room A (OBJ- 5 ) will be defined in the real-world model table MTB in such a way that the number of persons acquired from the pressure switches (WSN- 3 to WSN- 10 ) in the meeting room A may be stored in the measured data 5 (LINK- 5 ).
  • the distributed data processing server DDS corresponding to the measured data 5 and the storage position will be defined.
  • the seating information from the wired sensor nodes WSN- 3 to WSN- 10 will be stored in the disk drive DSK 5 of the distributed data processing server DDS.
  • the object representing the temperature of the meeting room A (OBJ- 6 ) will be defined in the real-world model table MTB in such a way that the temperature measured by the wired sensor node FSN- 1 in the meeting room A may be stored in the measured data 6 (LINK- 6 ).
  • the distributed data processing server DDS corresponding to the measured data 6 and the storage position will be defined.
  • the temperature data from the FSN- 1 will be stored in the disk drive DSK 6 of the distributed data processing server DDS.
  • each object OBJ defined in the real-world model table MTB stores the link pointer (LINK) corresponding to the measured data, and although the object data as seen from the user terminal UST may seem to exist in the directory server DRS, the actual data is stored in the distributed data processing server DDS.
  • LINK link pointer
  • the storage position of the measured data measured by the sensor nodes, the secondary data obtained by converting the measured data into an understandable form for the user and the other data usable for the user are set.
  • the measured data from the sensor nodes is collected by each distributed data processing server DDS, and if an event/action is set as described later on, the measured data will be processed and will be stored in the predetermined distributed data processing server DDS as secondary data.
  • the data from the sensor nodes will be actually collected and processed by the distributed data processing servers DDS, and the directory server DRS will manage the real-world model, the link pointer of information and the definition of the sensor nodes.
  • the users of the user terminals UST will not be required to learn the location of the sensor nodes, they will be able to obtain the desired data corresponding the measurement (or the secondary data) of the sensor node by retrieving the objects OBJ.
  • the directory server DRS will manage the link pointer of each object OBJ, and the actual data will be stored and processed in the distributed data processing servers DDS, even if the number of sensor nodes turns out to be huge, it will be possible to prevent the distributed data processing servers DDS from being overloaded. In other words, even when a large number of sensor nodes are employed, it will be possible to suppress the traffic load on the network NWK- 1 connecting the directory server DRS, distributed data processing servers DDS and the user terminals UST.
  • FIG. 7 showing the state after the lapse of a predetermined period of time after the state of FIG. 6 , the actual measured data transmitted from the sensor nodes will be written into the disk drives DSK- 1 to DSK- 6 of the distributed data processing servers DDS, and the amount of data will increase as the time passes.
  • the amount of information stored in the link pointers LINK- 1 to LINK- 6 corresponding to the objects OBJ- 1 to OBJ- 6 set in the model list MDL of the real-world model table MTB of the directory server DRS remains unchanged even with the passage of time, and the contents of information indicated by the link pointers LINK- 1 to LINK- 6 change.
  • the relationship between the amount of information of the objects OBJ- 1 to OBJ- 6 managed by the directory server DRS, the amount of data of the measured data 1 to 6 managed by the distributed data processing servers DDS and time is that, while the amount of data of the objects is constant as shown in FIG. 8 , the amount of measured data increases as the time passes.
  • a distributed data processing server DDS is connected with several base stations BST, and a directory server DRS is connected with tens of distributed data processing servers DDS
  • the total number of sensor nodes will be several thousands or several tens of thousands. Supposing that each sensor node transmits data every minute, hundreds or thousands of measured data pieces will be sent every second to the distributed data processing server DDS, the presence of an event will be judged, and if an event has occurred, a predetermined action, such as a notice, data processing or other action will be taken. If these actions are to be carried out by a centralized server, the load of the server itself or that of the network for connecting with the server will be very large. In addition, the collected data or the secondary data must be provided to the user terminals in response to users. Therefore, the load of the server or that of the network will further increase.
  • the server function is divided on DRS and DDS.
  • the directory server DRS receives access from the user terminals UST and manages the information link pointers of the sensor nodes.
  • the distributed data processing servers DDS manage plural base stations BST, collect and process the data from the sensor nodes.
  • the information from the sensor nodes is distributed among and collected by plural distributed data processing servers DDS, and each distributed data processing server DDS respectively stores or processes the data. In this way, the collection and processing of data from a large number of sensor nodes is distributed and thus the concentration of load into specific servers can be avoided.
  • the directory server DRS manages collectively (in a centralized way) the link pointers LINK of information acquired from the measured data of the sensor nodes and provides the user terminals UST with the correspondence relationship between the objects and the link pointers LINK. Users acquire useful information from the data link pointers by inquiring the directory server DRS on the target objects even if they have no information regarding the physical position of sensor nodes.
  • the centralized management of information link pointers by the directory server DRS enables the user terminals UST to acquire the measured data or secondary data concerning the target sensor node by accessing the directory server DRS without sensor node information.
  • the directory server DRS converts the data acquired from the distributed data processing servers DDS into information understandable for the users based on the attribute interpretation list ATL and provides the result to the user terminals UST.
  • the objects stored in the directory server DRS are set and modified depending on the system structure, and do not change chronologically as the measured data retrieved by the sensor nodes does. Therefore, the part that controls collectively the objects is not affected by chronological changes in the load of the measured data. As a result, the direct exchange of the sensor node data with the distributed data processing servers DDS is restricted, and thus the possibility that the overload of the network NWK- 1 connected with the directory server DRS is suppressed.
  • FIGS. 6 and 7 show the case where separate distributed data processing servers DDS are respectively connected with a disk drive DSK.
  • a distributed data processing server DDS may be provided and plural disk drives DSK may be connected therewith. It is also possible to connect the disk drives with grouped plural distributed data processing servers DDS.
  • the event-action controller EAC of the distributed data processing server DDS has an event table ETB for correlating the measured data collected by the base stations BST with events.
  • a record of the event table ETB is made up of a data ID allocated to each sensor node and given to the measured data (corresponding to the data ID shown in FIGS. 12 and 14 ), EVT constituting the criteria of judging the occurrence of an event relating to the measured data, and a data holder DHL for determining whether the measured data should be stored in the database DB or not.
  • the measured data whose data ID is “XXX” notifies the directory server DRS on the occurrence of an event when its value is greater than A 1 .
  • the measured data whose data ID is “XXX” are set in such a way that they will be written on the disk drive DSK whenever the data arrive s.
  • the distributed data processing server DDS receives the measured data acquired from the base station BST at first by the sensing data ID extractor IDE and extracts the data ID or ID given to the measured data. And the sensing data ID extractor IDE sends the measured data to the latest data memory LDM.
  • the extracted data ID will be sent to the event search engine EVS to search the event table ETB, and when a record whose data ID matches is found, the event contents EVT of the record and the measured data will be sent to the event condition parser EVM.
  • the event condition parser EVM compares the value of the measured data and the event contents EVT, and when the conditions are satisfied, the event condition parser EVM notifies the directory server DRS that an event has occurred through the directory server interface DSI. And the event condition parser EVM transmits the request of the data holder DHL to the latest data memory.
  • the database controller DBC will receive the data from the latest data memory LDM and write the data on the disk drive DSK.
  • the distributed data processing server DDS When the directory server interface DSI has received a reference request for the measured data from the directory server DRS, the distributed data processing server DDS will transmit the access request to the data access receiver DAR.
  • the data access receiver DAR If the request for data access is for the latest data, the data access receiver DAR reads the measured data corresponding to the data ID contained in the access request from the latest data memory LDM, and returns the same to the directory server interface DSI. Or, if the access request is for the past data, the data access receiver DAR reads the measured data corresponding to the data ID contained in the access request from the disk drive DSK, and returns the same to the directory server interface DSI.
  • the distributed data processing server DDS retains the latest data in the latest data memory LDM from among the sensor node data collected from the base stations BST, and records other data in the disk drive DSK for reference in the future. And it is also possible to hold the data in the disk drive DSK only when an event has occurred to save the disc capacity.
  • it will be possible to manage plural base stations BST (in other words a large number of sensor nodes) with a single distributed data processing server DDS.
  • FIG. 11 shows the details of the system manager NMG and the model manager MMG of the directory server DRS and the real-world model table MTB shown in FIG. 2 .
  • the system manager NMG of the directory server DRS includes a sensor information table STB for managing the sensor nodes, a registration interface for registering sensor nodes in the sensor information table STB, and a retrieval interface for retrieving the contents of the sensor information table STB.
  • the sensor information table STB will be managed by the sensor operation terminal ADT-A.
  • the sensor information table STB is made up of a record of the data ID allocated in advance for each sensor node, the sensor type indicating the type of sensor node, the meaning indicating the object of measurement by the sensor node, the contents of measurement measured by the sensor node, the location indicating the position (or object) of the sensor node, the observation interval indicating the frequency by which the sensor node detects the measurement from the object of measurement, and the data link pointer showing the link pointer of the data measured (the position of storage in the distributed data processing server DDS- 1 to DDS-n) which are managed by an ID for identifying the sensor node as an index.
  • the table shows that the tag TG- 1 of the wireless mobile sensor node MSN- 1 constituted as an identification card shown in FIG. 5 is allocated a data ID of 01, and the object of measurement is the location (position) of the wireless mobile sensor node MSN- 1 , the frequency of measurement is every 30 seconds, and the measurement data is stored in the distributed data processing server DDS- 1 .
  • the table shows that the sensor SSR- 1 disposed in the wireless mobile sensor node MSN- 1 constituted as an identification card is allocated a data ID of 02, that the object of measurement is the ambient temperature, that the frequency of measurement is every 60 seconds, and that the measured data is stored in the distributed data processing server DDS- 2 .
  • This sensor information table STB contains data set by the sensor operation terminal ADT-A, and the sensor manager and the service manager can learn the functions and position of the sensor nodes and the link pointers of the measured data by referring the sensor information table STB.
  • the real-world model table MTB managed by the model manager MMG includes an attribute interpretation list ATL for interpreting what the measured data means, a real-world model list MDL showing the relationship of correspondence between the model name of the object OBJ- 1 to OBJ-n shown in FIG. 6 and the actual information storage position and a model binding list MBL showing the relationship of correlation among the objects OBJ- 1 to OBJ-n.
  • model manager MMG includes an attribute interpretation list manager ATM for managing the attribute interpretation list ATL, a real-world model list manager MDM for managing the real-world model list MDL, and a model binding list manager MBM for managing the model binding list MBL in order to manage each list of this real-world model table MTB, and each manager includes respectively a registration interface for registering/changing the list and a retrieval interface for retrieving each list.
  • the real-world model table MTB should be managed by the service manager who uses the service operation terminal ADT-B. Furthermore, the sensor operation terminal and the service operation terminal shown in FIG. 11 may be integrated into a single operation terminal as shown in FIG. 1 .
  • the user terminal UST for using the sensor network will be used to retrieve objects OBJ from the desired list through the retrieval interface of each list.
  • the attribute interpretation list ATL managed by the attribute interpretation list manager ATM includes a table for converting the output value of sensor nodes into meaningful information as shown in FIG. 13 because the return values (measurements) of the sensor nodes WSN, MSN and FSN and the secondary data converted by the distributed data processing servers DDS cannot be understood easily as they are by the users of the user terminals UST (hereinafter referred to simply as “user”).
  • FIG. 13 is previously set according to the objects OBJ- 1 to OBJ-n.
  • the name table ATL-m is related with the position of Mr. Suzuki OBJ- 1 shown in FIG. 6 , and as shown in FIG. 12 , the personal name corresponding to the return value (measurement) from the identifier set in the tag TG set in the sensor node MSN- 1 whose sensor type is identification card is indicated in the meaning column.
  • the seat table ATL-s of FIG. 13 shows the state of persons sitting on the chairs in the office or in the meeting room A shown in FIG. 5 , and stores the state of persons sitting (present or absent) corresponding to the return value (measurement) of wireless sensor nodes WSN- 3 to WSN- 10 installed on each chair (each wireless sensor node WSN- 3 to WSN- 10 ). For example, a return value of 00 shows that the person is present (seated), and a return value of 01 shows that the person is absent.
  • the temperature table ATL-t of FIG. 13 is a table of values given by the temperature sensors (SSR- 1 , FSN- 1 and 2 of MSN- 1 ) shown in FIG. 5 , and the function f (x) for converting the return value (the measured data of the temperature sensors) into temperature y will be stored in the meaning column.
  • the number of persons table ATL-n is a table showing the number of persons in the meeting room A, and the number of persons corresponding to the return value (the number of persons seated shown by the chair sensors in the meeting room A, or the number of mobile sensor nodes MSN in the meeting room A) will be indicated in the meaning column.
  • the attribute interpretation list ATL is a list defining the meaning corresponding to the measured data, and respective table will be created corresponding to the objects formed.
  • the real-world model list MDL is a list created in advance by the service managers and the like, and as shown in FIG. 14 the position of information corresponding to the model name set for each object will be stored in the information link pointer.
  • the combination of model name, information link pointer and data ID constitutes a real-world model list MDL.
  • the directory server DRS manages only meaningful information that the users can understand from the model list MDL, and this meaningful information will be located in any of the distributed data processing servers DDS- 1 to DDS-n.
  • the objects OBJ defined in the model list MDL indicate where the substance of the meaningful information is located in the information link pointer.
  • this information link pointer is created in advance by the service manager and the like.
  • the data ID is a value corresponding to the sensor data (data acquired directly from the sensor node or secondary data acquired by processing) serving as the basis of the object value.
  • an information link pointer named LINK- 1 for Mr. Suzuki's position OBJ- 1 is stored, and this information link pointer stores URL, path and the like.
  • this object is retrieved from the user terminals UST, meaningful information (substance of the object) can be obtained from the information link pointers.
  • the directory server DRS acquires the data corresponding to the information link pointer from the distributed data processing server DDS created in the information link pointer LINK.
  • the directory server DRS converts the acquired data into information that the user can understand based on the attribute interpretation list ATL and transmits the same to the user terminals UST.
  • the distributed data processing server DDS Since it is no longer necessary to convert the data collected from the sensor nodes into a form understandable for the users every time they are collected, in the distributed data processing server DDS, it is possible to drastically reduce the load of the distributed data processing servers DDS that collect and/or manage the data of a large number of sensor nodes.
  • This conversion processing of data conducted by the directory server DRS if necessary at the request of users can eliminate any unnecessary conversion operation, and thus it will be possible to make the sensor network resources to function efficiently.
  • the model binding list MBL showing the relationship of correlation among the objects OBJ- 1 to OBJ-n summarizes the related information on the elements common with the objects OBJ of the real-world model list MDL.
  • model binding list MBL As an example of the model binding list MBL, as FIG. 15 shows, “personal name” (“Mr. Suzuki” in the figure) and elements related with “the meeting room A” are extracted as common elements among the objects OBJ of the real-world model list MDL. For example, as objects OBJ related with the personal name of “Mr. Suzuki” registered in the meaning column of the name table ATL-m of the attribute interpretation list ATL shown in FIG. 13 , there are position OBJ- 1 , seated state at the employee's own seat in the office OBJ- 2 , and temperature OBJ- 3 , and the link pointers of the objects related with the personal name of Mr. Suzuki are set in a tree structure as “position” LINK- 1 , “seated state” LINK- 2 , and “temperature” LINK- 3 as shown in the figure, and this will constitute a model binding list MBL-P related to personal name.
  • model binding list MBL will constitute a source of information relating different pieces of information having common elements out of the elements of the objects of the real-world model list MDL. It should be noted that different elements of this model binding list MBL were related in advance by the service manager and the like.
  • the sensor manager installs a sensor node at a predetermined place or on an employee and then registers the sensor node on the directory server DRS according to the time chart shown in FIG. 16 .
  • the sensor manager accesses the directory server DRS through the sensor operation terminal ADT-A, and accesses the registration interface of the system manager NMG. Then, the sensor manager sets the data ID, the sensor type, attribute, measurement values, place of installation, interval of observation, and the data link pointer from the sensor operation terminal ADT-A using the data format shown in FIG. 17 , and transmits the same to the system manager NMG of the directory server DRS as a request for registration (RG- 1 ).
  • the data link pointers should be secured and the attribute should be designated to the distributed data processing server DDS that is supposed to receive the sensor node data.
  • the system manager NMG of the directory server DRS Upon receipt of this request for registration, the system manager NMG of the directory server DRS adds the sensor node information for which the request for registration was presented to the sensor information table STB shown in FIG. 12 . And the system manager NMG allocates an identifier ID to the newly added sensor node. This sensor node ID may be allocated from the sensor operation terminal ADT-A.
  • the system manager NMG allocates the link pointer of the measured data of the sensor node for which a request for registration was presented to the distributed data processing server DDS designated as a data link pointer and then completes a record of the sensor information table STB.
  • the system manager NMG returns a notice of completion (ACK) to the sensor operation terminal ADT-A, indicating that a new record was successfully added.
  • the distributed data processing server DDS upon receipt of a notice of registration of a sensor node from the directory server DRS, issues a command to the base station BST corresponding to “the place of installation” in FIG. 17 to enable the sensor node having the relevant ID with predetermined observation frequency.
  • the sensor manager SNM of the base station BST will receive the registration of the data ID and the observation interval.
  • the new sensor node will be able to transmit the measured data to the distributed data processing server DDS to which this sensor node belongs through the base station BST.
  • the service manager accesses the directory server DRS from the service operation terminal ADT-B to access the retrieval interface of the system manager NMG. Then, the service manager retrieves the desired sensor nodes based on the ID and the like and returns the sensor nodes meeting the retrieval conditions to the service operation terminal ADT-B.
  • the service operation terminal ADT-B shows the retrieval result of the sensor nodes that have been received from the system manager NMG on the display devices and the like.
  • the service manager selects a desired sensor node from the sensor nodes displayed on the service operation terminal ADT-B, designates the objects to be correlated with the measured data of this sensor node, and registers the same on the model manager MMG of the directory server DRS.
  • This registration results in the creation of a real-world model list (MDL) showing the relations between the object and its information link ( FIG. 14 ).
  • MDL real-world model list
  • the model manager MMG issues a predetermined command to the distributed data processing server DDS- 1 to, for example, store the position of the base station BST having received the mobile sensor node MSN with a tag ID TG- 1 (Mr. Suzuki's identifier) with regards to the object OBJ- 1 of “Mr. Suzuki's position” in the distributed data processing server DDS- 1 .
  • the distributed data processing server DDS- 1 is set to register an action in the event-action controller EAC.
  • the content of the action is set to store the position of the base station BST in the database DB on receipt of TG- 1 data whose tag ID indicates Mr. Suzuki,
  • An information link pointer corresponding to the object OBJ- 1 of the real-world model list MDL will be set regarding the substance of the data “Mr. Suzuki's position” stored in the database DB of the distributed data processing server DDS- 1 .
  • the model manager MMG issues a command to the distributed data processing server DDS- 1 to write a value of “00” in the database DB of the distributed data processing server DDS- 1 if the measurement of the wireless sensor node WSN- 0 with a pressure switch as a sensor SSR is ON, and to write a value of “01” in the database DB of the distributed data processing server DDS- 1 if the measurement of the wireless sensor node WSN- 0 is OFF.
  • the event action controller EAC of the distributed data processing server DDS- 1 Upon receipt of this command, the event action controller EAC of the distributed data processing server DDS- 1 proceeds to an operation of writing “00” or “01” for the measured data of the sensor node WSN- 0 (corresponding respectively ON or OFF) in the database DB of the distributed data processing server DDS- 1 .
  • an information link pointer corresponding to the object OBJ- 2 of the real-world model list MDL will be set regarding the substance of the data “Mr. Suzuki's seating” stored in the database DB of the distributed data processing server DDS- 1 .
  • the object (information link pointer) set by the model manager MMG and the position of the distributed data processing server DDS for actually storing the information are set.
  • the model manager MMG creates the object OBJ- 1 of “Mr. Suzuki's position” and stores the model name, the data ID and the information link pointer in the real-world model list MDL.
  • the model manager MMG sends a notice of completion to the service operation terminal ADT-B.
  • the service operation terminal ADT-B For displaying the notice of completing the creation of the objects received and for creating the object, the service operation terminal ADT-B repeats the operation described above to create the desired objects.
  • the service manager accesses the model manager MMG of the directory server DRS from the service operation terminal ADT-B to access the retrieval interface of the model manager MMG. Then, the service manager retrieves the desired objects and returns the object matching the retrieval conditions to the service operation terminal ADT-B.
  • the service operation terminal ADT-B outputs the retrieval result of the objects received from the model manager MMG on a display device not shown and the like.
  • the service manager selects a desired object from among the objects displayed in the service operation terminal ADT-B and requests the model manager MMG of the directory server DRS to indicate the elements common to all the objects in a model binding list.
  • the personal name “Mr. Suzuki” will be created in the model binding list MBL-P, and this model binding list MBL-P will be related with the position of Mr. Suzuki OBJ- 1 , the seating state of Mr. Suzuki OBJ- 2 , and the temperature of Mr. Suzuki OBJ- 3 .
  • the model manager MMG relates the model binding list MBL-P with the information link pointer of all the objects OBJ- 1 to OBJ- 3 and stores the same in the model binding list MBL.
  • the model manager MMG sends a notice of completion to the service operation terminal ADT-B.
  • the service operation terminal ADT-B For displaying the notice of completing the creation of the model binding list received and for creating the model binding list, the service operation terminal ADT-B repeats the operation described above to create the desired model binding list.
  • the user terminal UST accesses the search engine SER of the directory server DRS, and requests the model binding manager MBM to retrieve the model binding list MBL. This request for retrieval is made, for example, by the retrieval of key words and GUI as shown in FIG. 15 .
  • the model binding list manager MBM returns the result of retrieval requested to the user terminal UST and displays the result of the model binding list matching with the retrieval request on a display device of the user terminal UST.
  • the user selects any model binding list from among the retrieval result on the user terminal UST and requests information (Step 110 ).
  • the model binding list is constituted by link points in a tree structure grouped together by common elements among the objects OBJ, and the users present their request for information to the distributed data processing server DDS constituting the link pointer by choosing any link pointer displayed in the model binding list of the user terminal UST.
  • the user accesses the measured data or secondary data requested from the user terminals UST and returns the access result to the attribute interpretation list manager ATM of the directory server DRS.
  • the attribute interpretation list manager ATM obtains the meaning for the return value of the attribute interpretation list ATL shown in FIG. 13 from the ID of the measured data sent from the distributed data processing server DDS (Step 112 ).
  • the search engine SER of the directory server DRS returns the meaning corresponding to the measured data analyzed by the attribute interpretation list manager ATM to the user terminal UST, and the user terminal UST displays the response of the directory server DRS in the place of the response from the distributed data processing server DDS.
  • the measured data of the distributed data processing server DDS- 1 set previously for the position of Mr. Suzuki OBJ- 1 from the user terminal UST is accessed. If the link pointer LINK- 1 is related for example with the data link pointer of the sensor information table STB shown in FIG. 12 , the distributed data processing server DDS reads the measured data of the mobile sensor node MSN- 1 being the measured data from the database DB corresponding to this data link pointer, and returns to the directory server DRS.
  • the place table ATL-p of the attribute interpretation list ATL is chosen from data attribute stored together with data, and the meaning corresponding to the return value (measurement) is acquired.
  • the return value is 02 for example
  • the information of the link pointer LINK- 1 of the model binding list MBL-P will be “meeting room A.” Therefore, the response for the object OBJ- 1 of “Mr. Suzuki's position” of the model binding list MBL-P is converted from a measurement value of the sensor node MSN- 1 “02” into the meaningful information “meeting room A” and will be displayed (or notified) on the user terminal UST.
  • the present embodiment shows the method wherein the data attribute will be acquired together with the data.
  • the data link pointer and their attribute of sensor node are set, at the time of registration, to the distributed data processing server DDS that is to receive data from the sensor node.
  • attributes may be designated to models at the time of registering the real-world model list MDL.
  • FIG. 22 shows the case of carrying out the operation of FIG. 20 above for “the seating state of Mr. Suzuki” LINK- 2 of the model binding list MBL-P shown in FIG. 15 .
  • FIG. 23 shows the case of carrying out the operation of FIG. 20 above for “the temperature of Mr. Suzuki” LINK- 3 of the model binding list MBL-P shown in FIG. 15 .
  • FIG. 24 shows the case of carrying out the operation of FIG. 20 above for “the members in the meeting room A” of the model binding list MBL-R shown in FIG. 15 .
  • the tag ID of the identification card node detected by the base station BST- 1 corresponding to the meeting room A is read in the base station BST- 1 as measured data. And this value will be stored in the information link pointer shown in FIG. 14 (here, the distributed data processing server DDS- 1 ) set in advance as a data link pointer.
  • the distributed data processing server DDS- 1 collects at a prescribed frequency the tag ID of the wireless sensor nodes MSN- 1 to MSN-n from the base station BST- 1 and updates the value showing the members of the meeting room A (set of tag ID of the identification card nodes).
  • FIG. 24 shows that the employees whose tag ID are “01” and “02” have been detected in the meeting room A from the wireless mobile sensor nodes MSN- 1 to MSN-n collected by the distributed data processing server DDS- 1 .
  • the distributed data processing server DDS- 1 transmits this secondary data “01. 02” to the attribute interpretation list manager ATM of the directory server DRS.
  • FIG. 25 shows the case of carrying out the operation shown in FIG. 20 above for “the number of persons in the meeting room A” of the model binding list MBL-R shown in FIG. 15 .
  • the number of persons in the meeting room A specifically the number of IDs of the identification card detected by the base station BST- 1 corresponding to the meeting room A or the number of the seating detection nodes which is ON is calculated. And this value will be stored in the information link pointer shown in FIG. 14 set in advance as a data link pointer of the object OBJ- 5 .
  • the distributed data processing server DDS- 1 collects the number x of the IDs of the wireless mobile sensor nodes MSN- 1 to MSN-n from the base station BST- 1 at a prescribed frequency, and calculates and updates the value showing the number of persons at the meeting room A (secondary data).
  • the distributed data processing server DDS- 1 sends this secondary data x to the attribute interpretation list manager ATM of the directory server DRS.
  • FIG. 26 is a block diagram showing the details of the action controller ACC of the directory server DRS.
  • the action controller ACC Based on a notice on the occurrence of an event received from the event action controller EAC of plural distributed data processing servers DDS, the action controller ACC automatically performs an “action” previously set.
  • the action controller ACC includes an action receiver ARC for receiving the setting of action from the user terminal UST through the session controller SES, an action analyzer AAN for analyzing the action received and for setting the distribution of functions (or loads) between the directory server DRS and the distributed data processing server DDS according to the analysis result, an action manager AMG for managing the definition and execution of actions, an action table ATB for storing the relationship between the events and actions according to the request for setting from the user terminal UST, an event monitor instructor EMN for issuing instructions to the distributed data processing server DDS- 1 to DDS-n to monitor the events defined in the action table ATB, an event receiver ERC for receiving the notice of events that occurred at each distributed data processing server DDS- 1 to DDS-n, and an action executer (executing unit) ACE for executing the prescribed actions based on the definition of the event-action table ATB received.
  • an action receiver ARC for receiving the setting of action from the user terminal UST through the session controller SES
  • an action analyzer AAN for analyzing the action received and
  • the registration of actions is explained with reference to the timing chart in FIG. 27 .
  • the user accesses the action controller ACC of the directory server DRS through the user terminal UST or the like to request the setting of action.
  • the action controller ACC of the directory server DRS accesses the action controller ACC of the directory server DRS through the user terminal UST or the like to request the setting of action.
  • FIG. 28 we will examine the case where Mr. X taking his seat triggers sending a pop-up notice to the IP address of the user terminal UST of A.
  • the action receiver ARC of the action controller ACC requests to the action analyzer AAN to set the action.
  • the action analyzer AAN selects the data ID of the object of monitoring, for example, from Mr. X taking his seat, and decides which condition of the measured data of the sensor nodes to be met to trigger an action.
  • the model of “Mr. X taking his seat” will be retrieved by referring the real-world model list MDL of the real-world model table MTB and the attribute interpretation list ATL.
  • the action manager AMG sends an instruction to the distributed data processing server DDS which manages the sensor node in order to monitor the occurrence of an event of “Mr. X taking seat” .
  • the action manager AMG sets an action of “IP address: send a pop-up notice to the user terminal UST of A” in the action table ATB, and sets the sensor node ID mentioned above as an ID of the event of executing the action.
  • the notice to be given to the directory server DRS is an action executed in the distributed data processing server DDS- 1 .
  • the reception of the occurrence of an event from the distributed data processing server DDS- 1 will be set in the event condition column
  • a pop-up notice to the user terminal UST will be set in the action column to be executed by the directory server DRS
  • the IP address indicating Mr. A from among the user terminal UST will be set in the action parameters column.
  • the screen for requesting the action setting in FIGS. 28 and 29 is provided by the action receiver ARC of the directory server DRS to the user terminal UST, and the real-world model list MDL is related to the “personal name” pull-down menu, the pull-down menu “seated,” “in conference” and “at home” is related with the attribute interpretation list ATL, and the pull-down menu of “pop-up” and “mail” shows the action to be executed by the directory server DRS.
  • a single action to be executed following a single event as described above will be called “a single action,” as is shown in FIG. 32 .
  • a request for an action setting is presented by the user terminal UST to the action controller ACC of the directory server DRS, an action analysis and an instruction for monitoring an event are created in the action controller ACC, and an event table ETB will be defined in the event-action controller EAC of the distributed data processing server DDS.
  • the action controller ACC informs the user terminals UST that a series of action settings have been completed.
  • FIG. 33 is a time chart showing the execution of actions set in FIGS. 28 and 29 above.
  • This event occurrence will be notified by the distributed data processing server DDS to the directory server DRS and will be received by the even receiver ERC shown in FIG. 26 .
  • the action executer ACE sends a pop-up notice to the user terminal UST having an IP address A that is designated by the action manager AMG.
  • the pop-up notice is sent to the user UST with IP address A enabling to confirm that Mr. X has taken his seat.
  • FIGS. 28, 29 and 33 describe the case of taking an action for an event that has occurred. However, as shown in FIGS. 34 to 39 , it is possible to set the case of taking an action when two events have occurred.
  • FIGS. 34 and 35 are screens for requesting the setting for an action triggered by plural events occurrence.
  • a pull-down menu wherein the state of “being seated” and the like for two personal name columns can be chosen is defined.
  • the conditions for the event corresponding these two personal names are, like FIGS. 28 and 29 above, related with the real-world model list MDL and the attribute interpretation list ATL of the real-world model table MTB.
  • the action to be executed by the directory server DRS pop-up notice, mail transmission
  • the parameters column (address and the like) required for the execution of the actions
  • the event of “Mr. Suzuki taking seat” will be set in the same way as FIGS. 28 and 29 above, and the event shown in FIG. 36 will be set in the event table ETB of the distributed data processing server DDS- 2 which monitors the taking seat of Mr. Suzuki.
  • the time chart of setting the action table at this time will be shown in FIG. 39 .
  • “00” showing the taking seat from the attribute interpretation list ATL will be the condition of the event
  • the action of informing the action controller ACC of the directory server DRS when this event condition has been met will be set in the event table ETB of the distributed data processing server DDS- 2 as shown in FIG. 37 .
  • FIG. 40 is a time chart showing how the actions are executed.
  • FIGS. 41 to 45 indicate the case where single actions are executed in the distributed data processing servers DDS.
  • An action executer ACE is added to the event action controller EAC of the distributed data processing server DDS in FIG. 9 , the event table ETB shown in FIG. 9 is replaced by the event action table EATB.
  • the rest of the structure is the same as the first embodiment.
  • the event action controller EAC of the distributed data processing server DDS includes an event action table EATB for relating the measured data collected from the base stations BST with the events and actions through the directory server interface DSI.
  • each record of the event-action table EATB includes data ID given to the measured data allocated to each sensor node, an event contents column indicating the conditions on the measured data for generating events, an action column indicating the details of the action executed by the distributed data processing server DDS when an event occurs, a parameter column for storing the values necessary for executing an action, a data holder DHL for determining whether the measured data will be stored in the database DB or not when an event occurs.
  • the measured data will not be written in the disk drive DSK even if the condition is met when an event occurs.
  • the measured data received from the base station BST is first of all received by the sensing data ID extractor IDE, the ID allocated to each sensor node is extracted from the measured data, and this ID will be the data ID.
  • the sensing data ID extractor IDE will send the measured data to the latest data memory LDM.
  • the extracted data ID will be sent to the event search engine EVS to search the event action table EATB. If a record whose data ID matches is found, the event entry of the record and the measured data will be sent to the event condition parser EVM.
  • the event condition parser EVM compares the value of measured data and the event entry EVT, and if they meet the conditions they will be sent to the action executer ACE. And the action executer ACE will notice the event occurrence to the latest data memory LDM and the database controller DBC.
  • the database controller DBC will write the data whose data holder DHL is YES in the event action table EATB in the disk drive DSK.
  • the data access receiver DAR is similar to the embodiment 1 described above, and if the access request is for the latest data, it will read the measured data matching the data ID contained in the access request from the latest data memory LDM and return the same to the directory server interface DSI.
  • FIG. 44 shows a time chart for setting actions in the distributed data processing server DDS and FIG. 42 shows an example of interface sent by the action controller ACC of the directory server DRS to the user terminal UST for setting actions.
  • the directory server DRS communicates with the distributed data processing servers DDS and sets the request for setting actions received from the user terminals UST to the distributed data processing server DDS corresponding to the sensor node ID designated.
  • the user accesses the action controller ACC of the directory server DRS from the user terminal UST and the like and requests to set actions.
  • actions we will examine the case of, as FIG. 28 shows, setting actions of monitoring the position of Mr. X and upon his entry into the meeting room A, sending a pop-up notice to the user terminal UST with an IP address: A.
  • the action receiver ARC of the action controller ACC requests the action analyzer AAN to set the action.
  • the action analyzer AAN chooses the data ID of the object of monitoring from, for example, Mr. X's position, and decides in which condition of the measured data of the sensor node the event will occur.
  • it in order to convert the real-world event of “Mr. X taking his seat” into a data ID, it will search the model of “Mr. X taking his seat” by referring to the real-world model list MDL and the attribute interpretation list ATL of the real-world model table MTB.
  • the action manager AMG judges whether the request presented by the user terminal UST is for a single action or not, and if it is for a single action, it will set in such a way that the requested action may be executed in the distributed data processing server DDS which holds the information mentioned above.
  • an instruction will be sent out to the distributed data processing server DDS that manages the sensor nodes selected as mentioned above to monitor whether the event “Mr. X′ position” matches with the condition “meeting room A”.
  • the action controller ACC of the directory server DRS sets the action of “sending Email to the user with a mail address: mailto_b@xyz.com” in the event-action table EATB in the distributed data processing server DDS, and sets the sensor node ID mentioned above as the event ID for executing the action.
  • the action controller ACC of the directory server DRS sets values on the corresponding distributed data processing server DDS instead of setting values in its own action table ATB so that both events and actions may be set in the event-action table EATB of the distributed data processing server DDS.
  • the events and actions will be executed in the distributed data processing server DDS as shown in FIG. 45 .
  • Mr. X enters the meeting room
  • the entry of Mr. X into the meeting room A will be notified to the prescribed Email address.
  • the directory server DRS only sets actions to the distributed data processing server DDS, and it is not necessary to monitor the actual occurrence of events. Accordingly, the collection of data and the execution of single action may be entrusted to the distributed data processing servers DDS, and the directory server DRS only does tasks such as monitoring the request for retrieval and actions with plural events from the user terminals UST. Therefore, when the number of requests for monitoring actions is very large, it is possible to prevent the loads of the directory server DRS from becoming excessively large and to operate the sensor network smoothly.
  • FIGS. 46 and 47 are block diagrams showing the first variant of the first or second embodiments described above.
  • the measurements coming from certain sensor nodes are stored in the predetermined distributed data processing servers DDS as raw data A, while the measurements from other sensor nodes are stored in predetermined distributed data processing servers DDS as raw data B.
  • each distributed data processing server DDS the raw data A and B are respectively processed (e.g. mean value for the unit time and the like) and the results of processing are stored as data A and B respectively of the secondary directory server DR.
  • the processing timing of the raw data A and B may be set as an action based on the predetermined conditions (passage of time) in the directory server DRS or each distributed data processing server DDS.
  • Each distributed data processing server DDS will calculate the third data C from the processed secondary data A and B as the specified action and store them as new secondary data in the specified distributed data processing server DDS.
  • this third data C When this third data C are processed further, it will be stored as the tertiary data C′.
  • the secondary data A and B will represent respectively the average temperature and the average humidity for a unit length of time.
  • the index of discomfort calculated from the average temperature and the average humidity can be expressed as third data C
  • the average value per unit length of time of the third data C can be expressed as tertiary data C′.
  • various events taking place are represented by measured data.
  • measured data (raw data) and secondary data are stored in a single distributed data processing server DDS.
  • the secondary data A and B may be transmitted to a different distributed management server from the distributed management server which manages the secondary data. This enables to handle the secondary data A and B as raw data, and the tertiary data C′ as secondary data.
  • FIG. 48 shows the second variant, wherein the network to which the distributed data processing server DDS is connected in the first or second embodiment is divided into a plurality, the other aspects of the configuration remaining the same as the first or second embodiment.
  • the network to which the distributed data processing server DDS is connected may be set to be different according to the frequency of referring the measured data and the like.
  • the measured data or secondary data whose frequency of reference from the directory server DRS (not shown) is high is connected with the same network 1 as the directory server DRS.
  • the distributed data processing server DDS storing secondary data D whose reference frequency is relatively low is connected with the network 2
  • the distributed data processing server DDS storing the secondary data E that is hardly referred is connected with the network 3 .
  • All the networks 1 to 3 are respectively connected with a gateway not shown.
  • Such a disposition of the distributed data processing servers DDS will enable to improve the access speed to the distributed data processing server DDS having data with a high frequency of reference.
  • the data link pointer corresponding to the model name was set as the information link pointer in the real-world model list MDL of the directory server DRS.
  • the latest value of data may be stored with the information link pointer.
  • the data traffic between the directory server DRS and the distributed data processing server DDS increases as the number of objects increases.
  • the load for the network NWK- 1 increases as compared with the embodiments described above, and yet it will be possible to respond quickly to the request for data from the user terminal UST, and further improvement in response can be expected.
  • the directory server manages collectively the location of data, plural distributed data processing servers are provided and are distributed on the network for collecting the data from the sensor nodes in real time. Therefore, it is possible to access data received from a huge number of sensor nodes quickly and easily.
  • this invention can be applied to a sensor network having a large number of sensor nodes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Economics (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Operations Research (AREA)
  • Physics & Mathematics (AREA)
  • Educational Administration (AREA)
  • Marketing (AREA)
  • Development Economics (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Game Theory and Decision Science (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
US11/211,467 2005-01-14 2005-08-26 Sensor network system and data retrieval method for sensing data Abandoned US20060161645A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US11/727,039 US8671136B2 (en) 2005-01-14 2007-03-23 Sensor network system and data retrieval method for sensing data

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2005-007525 2005-01-14
JP2005007525A JP4808409B2 (ja) 2005-01-14 2005-01-14 センサネットワークシステム、センサデータの検索方法及びプログラム

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US11/727,039 Continuation US8671136B2 (en) 2005-01-14 2007-03-23 Sensor network system and data retrieval method for sensing data

Publications (1)

Publication Number Publication Date
US20060161645A1 true US20060161645A1 (en) 2006-07-20

Family

ID=36685256

Family Applications (2)

Application Number Title Priority Date Filing Date
US11/211,467 Abandoned US20060161645A1 (en) 2005-01-14 2005-08-26 Sensor network system and data retrieval method for sensing data
US11/727,039 Expired - Fee Related US8671136B2 (en) 2005-01-14 2007-03-23 Sensor network system and data retrieval method for sensing data

Family Applications After (1)

Application Number Title Priority Date Filing Date
US11/727,039 Expired - Fee Related US8671136B2 (en) 2005-01-14 2007-03-23 Sensor network system and data retrieval method for sensing data

Country Status (3)

Country Link
US (2) US20060161645A1 (zh)
JP (1) JP4808409B2 (zh)
CN (2) CN101241510B (zh)

Cited By (39)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060259255A1 (en) * 2005-04-05 2006-11-16 Anderson James C Method of visualizing power system quantities using a configurable software visualization tool
US20060282498A1 (en) * 2005-06-09 2006-12-14 Hitach, Ltd. Sensor network system, method for data processing of a sensor network system
US20070282944A1 (en) * 2005-12-05 2007-12-06 Toshiyuki Odaka Sensor network system, gateway node, and method for relaying data of sensor network system
US20080004994A1 (en) * 2006-06-16 2008-01-03 Federal Express Corporation Methods and systems for providing sensor data using a sensor web
US20080104530A1 (en) * 2006-10-31 2008-05-01 Microsoft Corporation Senseweb
US20080247313A1 (en) * 2007-04-03 2008-10-09 Microsoft Corporation Slot-Cache for Caching Aggregates of Data with Different Expiry Times
US20080259919A1 (en) * 2005-09-27 2008-10-23 Nortel Networks Limited Method for Dynamic Sensor Network Processing
US20080267181A1 (en) * 2005-11-08 2008-10-30 Nortel Networks Limited Selective Multicasting of Sensor Data for Reliable Delivery
EP2060062A1 (en) * 2006-09-01 2009-05-20 Electronics and Telecommunications Research Institute Usn middleware apparatus and method for generating information based on data from heterogeneous sensor networks and information service providing system using the same
US20090144011A1 (en) * 2007-11-30 2009-06-04 Microsoft Corporation One-pass sampling of hierarchically organized sensors
US7555412B2 (en) 2007-02-09 2009-06-30 Microsoft Corporation Communication efficient spatial search in a sensor data web portal
US20090198648A1 (en) * 2008-01-31 2009-08-06 Invensys Systems, Inc. System and method for adaptively retrieving parameter trend data from a supervisory control manufacturing/production database
US20090198806A1 (en) * 2006-06-29 2009-08-06 Electronics And Telecommunications Research Instit Data structure for managing sensor network using id of sensor node and method using the same
JP2010514009A (ja) * 2006-12-14 2010-04-30 ラム リサーチ コーポレーション 一次サーバーアーキテクチャネットワーク構成およびその方法
US20100306189A1 (en) * 2007-11-29 2010-12-02 Min Soo Kim Sensor network managing apparatus and method thereof
US20110099054A1 (en) * 2008-05-26 2011-04-28 Hitachi, Ltd. Human behavior analysis system
US20110131320A1 (en) * 2007-12-17 2011-06-02 Electronics And Telecommunications Research Institute Apparatus and method of dynamically managing sensor module on sensor node in wireless sensor network
US20110153655A1 (en) * 2009-12-21 2011-06-23 Electronics And Telecommunications Research Institute Server-sensor network cooperative spatial query processing method and server using the same
CN102289452A (zh) * 2011-06-20 2011-12-21 中兴通讯股份有限公司 一种电信网管性能数据输出的方法及装置
US8085792B1 (en) 2007-06-29 2011-12-27 Google Inc. Traffic-oblivious load balancing protocol for sensor networks
US20120185458A1 (en) * 2011-01-18 2012-07-19 Microsoft Corporation Clustering crowd-sourced data to identify event beacons
US20120191413A1 (en) * 2011-01-26 2012-07-26 Hitachi, Ltd. Sensor information analysis system and analysis server
US20120257624A1 (en) * 2007-11-13 2012-10-11 Cisco Technology, Inc. Routing operations using sensor data
US8392401B1 (en) * 2007-06-29 2013-03-05 Google Inc. Query partitioning to decompose hotspots in sensor networks
US20140025825A1 (en) * 2012-07-17 2014-01-23 Sensinode Oy Method and apparatus in a web service system
JP2014038568A (ja) * 2012-08-20 2014-02-27 Tsukasa Hashimoto 検出システム、センサ、設定情報管理方法及びプログラム
US8671136B2 (en) * 2005-01-14 2014-03-11 Hitachi, Ltd. Sensor network system and data retrieval method for sensing data
US20140087695A1 (en) * 2011-05-12 2014-03-27 Telefonaktiebolaget L M Ericsson (Publ) Sensor Data Distribution System
US20140201356A1 (en) * 2013-01-16 2014-07-17 Delta Electronics, Inc. Monitoring system of managing cloud-based hosts and monitoring method using for the same
US20150031381A1 (en) * 2013-07-25 2015-01-29 Verizon Patent And Licensing Inc. Processing communications via a sensor network
US8954364B2 (en) 2011-09-19 2015-02-10 International Business Machines Corporation Hierarchical contexts to drive live sensor applications
CN104392296A (zh) * 2014-10-24 2015-03-04 东北大学 一种轧机多智能体模型系统的信息交换方法
US9985860B2 (en) 2013-09-23 2018-05-29 Schweitzer Engineering Laboratories, Inc. Selection and display of polled and streamed electric power system measurements
US10664553B2 (en) 2017-10-06 2020-05-26 Schweitzer Engineering Laboratories, Inc. Generating a representation of high-frequency signal data from an electric power delivery system
US10838937B2 (en) 2016-11-30 2020-11-17 Fujitsu Limited Distributed data management apparatus, non-transitory computer-readable storage medium, and distributed data management method
US10855526B2 (en) 2017-02-06 2020-12-01 Yokogawa Electric Corporation Sensor registration method, sensor registration system, and relay device
US11334829B2 (en) * 2019-12-19 2022-05-17 Honeywell International Inc. Methods and systems for electronic checklist data references
US20220351522A1 (en) * 2014-06-30 2022-11-03 Nec Corporation Guidance processing apparatus and guidance method
US11899517B2 (en) 2021-08-26 2024-02-13 Schweitzer Engineering Laboratories, Inc. Event analysis and display

Families Citing this family (40)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4839152B2 (ja) * 2006-08-04 2011-12-21 株式会社日立製作所 センサネットワークシステム及びセンサネットワークのデータ処理方法
JP4806605B2 (ja) * 2006-08-30 2011-11-02 株式会社日立製作所 センサネットワークシステム及びセンサネットワークのデータ管理方法
JP2008217160A (ja) * 2007-02-28 2008-09-18 Nippon Telegr & Teleph Corp <Ntt> センシングデータ変換システム、データ変換装置、およびデータ変換方法
JP2008257588A (ja) * 2007-04-06 2008-10-23 Toshiba Corp 業務指標演算装置
US20090107265A1 (en) * 2007-10-25 2009-04-30 Cisco Technology, Inc. Utilizing Presence Data Associated with a Sensor
US8352296B2 (en) * 2008-04-18 2013-01-08 Microsoft Corporation Managing real time meeting room status
CN102365901B (zh) * 2009-04-07 2014-10-29 瑞典爱立信有限公司 将传感器附接到wsan
CN101882354B (zh) * 2009-05-08 2013-09-18 北京时代凌宇科技有限公司 一种动态计算传感器物理量的装置和方法
JP5300655B2 (ja) * 2009-08-24 2013-09-25 日本電信電話株式会社 情報蓄積検索方法、情報蓄積検索装置、およびプログラム
JP5512215B2 (ja) * 2009-09-30 2014-06-04 株式会社日立システムズ ジョブ処理システム及びその方法、そのプログラム
TWI401979B (zh) * 2009-10-14 2013-07-11 Ind Tech Res Inst 無線感測網路之存取授權裝置與方法
JP5018914B2 (ja) * 2010-03-03 2012-09-05 沖電気工業株式会社 センサデータ提供システム、方法及び装置
JP5554731B2 (ja) * 2011-02-01 2014-07-23 日本電信電話株式会社 情報更新装置及び情報更新方法
CN102185745A (zh) * 2011-04-22 2011-09-14 郭永平 物联网服务系统
KR20130037368A (ko) * 2011-10-06 2013-04-16 한국전자통신연구원 센서 네트워크를 구성하는 중간 노드 장치 및 중간 노드 장치가 수행하는 센서 데이터 처리 방법
JP5348221B2 (ja) * 2011-11-04 2013-11-20 オムロン株式会社 ネットワークシステム、ノード装置群、コンピュータ装置およびセンサデータ送受信方法
CN102523148A (zh) * 2011-12-29 2012-06-27 苏州佰思迈信息咨询有限公司 智能优化物联网的方法
US9024780B2 (en) * 2012-05-04 2015-05-05 Itron, Inc. Limited data messaging with standards compliance
US9092244B2 (en) * 2012-06-07 2015-07-28 Dell Products, Lp System for developing custom data transformations for system integration application programs
EP2879411B1 (en) 2012-07-25 2017-05-17 Fujitsu Limited Sensor node, data processing system, and data processing method
CN103888715A (zh) * 2012-12-21 2014-06-25 北京计算机技术及应用研究所 一种基于多类型传感器的视频监控统一控制方法及系统
AU2013388154B2 (en) 2013-04-30 2017-06-15 Essity Hygiene And Health Aktiebolag Process and arrangement for collecting and storing data related to a condition of an absorbent product
WO2015001657A1 (ja) 2013-07-04 2015-01-08 富士通株式会社 データネットワーク管理システム、データネットワーク管理装置、データ処理装置、およびデータネットワーク管理方法
JP6200377B2 (ja) * 2014-05-29 2017-09-20 日本電信電話株式会社 仮想ｄｂシステム、および、仮想ｄｂシステムの情報処理方法
US10091279B2 (en) * 2015-05-27 2018-10-02 FlowJo, LLC Wireless connected laboratory
CN107218966B (zh) * 2016-03-21 2023-07-28 深圳市兴源智能仪表股份有限公司 供水管网数据智能采集方法
CN105929301B (zh) * 2016-04-12 2019-01-04 扬州盈信电气工程有限公司 一种变电站接地网腐蚀故障点智能监测装置
EP3540614B1 (en) * 2016-11-10 2024-05-15 Nippon Telegraph and Telephone Corporation Information storage device, information storage method, and program
US11144595B2 (en) * 2017-06-06 2021-10-12 Omron Corporation Score calculation unit, search device, score calculation method, and score calculation program
EP3663929B1 (en) * 2017-08-03 2022-11-23 Aptpod, Inc. Client device, data collection system, data transmission method, and program
US11055647B2 (en) * 2018-03-22 2021-07-06 Microsoft Technology Licensing, Llc Resource conflict detection and communication
US11210323B2 (en) 2018-04-27 2021-12-28 Microsoft Technology Licensing, Llc Methods and systems for generating property keys corresponding to physical spaces, devices, and/or users
US10747578B2 (en) 2018-04-27 2020-08-18 Microsoft Technology Licensing, Llc Nested tenants
US10484829B1 (en) 2018-04-27 2019-11-19 Microsoft Technology Licensing, Llc Methods and systems for generating maps corresponding to physical spaces, devices, and/or users
US10951482B2 (en) 2018-05-16 2021-03-16 Microsoft Technology Licensing, Llc Device identification on a building automation control network
US11456915B2 (en) 2018-05-21 2022-09-27 Microsoft Technology Licensing, Llc Device model templates
JP7420734B2 (ja) * 2018-11-13 2024-01-23 ソニーセミコンダクタソリューションズ株式会社 データ配信システム、センサデバイス及びサーバ
JP7016790B2 (ja) * 2018-12-06 2022-02-07 株式会社日立製作所 連携システムおよび連携方法
JP7150584B2 (ja) * 2018-12-06 2022-10-11 エヌ・ティ・ティ・コミュニケーションズ株式会社 エッジサーバとそのプログラム
CN111835681B (zh) * 2019-04-19 2023-08-04 北京京东尚科信息技术有限公司 一种大规模流量异常主机检测方法和装置

Citations (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6131119A (en) * 1997-04-01 2000-10-10 Sony Corporation Automatic configuration system for mapping node addresses within a bus structure to their physical location
US20020082879A1 (en) * 2000-08-31 2002-06-27 Brent Miller Method and system for seat selection and ticket purchasing in a networked computer system
US20040093239A1 (en) * 2002-11-13 2004-05-13 Biomedical Systems Corporation System and method for handling the acquisition and analysis of medical data over a network
US20040103139A1 (en) * 2000-03-30 2004-05-27 United Devices, Inc. Distributed processing system having sensor based data collection and associated method
US20040177319A1 (en) * 2002-07-16 2004-09-09 Horn Bruce L. Computer system for automatic organization, indexing and viewing of information from multiple sources
US20040254652A1 (en) * 2001-10-04 2004-12-16 Shunji Ota Method for managing sensor network system, program for managing sensor network system,record medium with recorde program for managing sensor network system, apparatus for managing sensor network system, method for managing relay network, program for managing relay network, record medium
US20060173995A1 (en) * 2005-01-28 2006-08-03 Hitachi, Ltd. Processing method for sensing data
US20060202834A1 (en) * 2005-03-03 2006-09-14 Norihiko Moriwaki Sensor network system and data retrieval method for sensing data
US20060242285A1 (en) * 2005-03-24 2006-10-26 Norihiko Moriwaki Sensor network system and data transfer method for sensing data
US20070019452A1 (en) * 2005-07-11 2007-01-25 Hitachi, Ltd. Electronic apparatus and sensor network system
US20070083283A1 (en) * 2005-10-11 2007-04-12 Koji Ara Work management support method and work management support system which use sensor nodes
US20070198708A1 (en) * 2005-01-14 2007-08-23 Norihiko Moriwaki Sensor network system and data retrieval method for sensing data
US20070262863A1 (en) * 2006-05-08 2007-11-15 Toshiyuki Aritsuka Sensor network system and sensor network position specifying method
US20070282944A1 (en) * 2005-12-05 2007-12-06 Toshiyuki Odaka Sensor network system, gateway node, and method for relaying data of sensor network system
US20080055113A1 (en) * 2006-08-30 2008-03-06 Hitachi, Ltd. Sensor network system and data management method for sensor network
US20080071899A1 (en) * 2006-09-14 2008-03-20 Hitachi, Ltd. Sensor network system for managing the latest data and history data
US20080143512A1 (en) * 2006-12-14 2008-06-19 Yoshihiro Wakisaka Wireless communication system and wireless terminal apparatus for sensor network
US20090189977A1 (en) * 2008-01-25 2009-07-30 International Business Machines Corporation System and method for spotlight identification of audience members during question and answer sessions

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5914671A (en) * 1997-02-27 1999-06-22 Micron Communications, Inc. System and method for locating individuals and equipment, airline reservation system, communication system
JPH11296478A (ja) * 1998-04-08 1999-10-29 Nec Corp 離席監視システム
WO1999060804A1 (en) * 1998-05-18 1999-11-25 Leviton Manufacturing Co., Inc. Network based electrical control system with distributed sensing and control
US8489669B2 (en) * 2000-06-07 2013-07-16 Apple Inc. Mobile data processing system moving interest radius
JP2002006937A (ja) 2000-06-27 2002-01-11 Tokyo Electric Power Co Inc:The 設備管理方法、設備管理システム、および、設備管理中継サーバ
JP2003319550A (ja) 2002-04-22 2003-11-07 Toshiba Corp 誘導電気機器運転支援システム及び方法
US6982639B2 (en) * 2002-11-26 2006-01-03 Ge Medical Systems Information Technologies, Inc. Wireless subject locator
JP2004280411A (ja) 2003-03-14 2004-10-07 Morinaga Milk Ind Co Ltd 遠隔監視システムおよびアフターサービス提供方法
CN1255748C (zh) * 2003-11-24 2006-05-10 华中科技大学 一种存储虚拟化系统的元数据层次管理方法及其系统
TWI227606B (en) * 2003-11-28 2005-02-01 Inst Information Industry System of non-intrusive access control and method thereof
CN100498766C (zh) * 2003-12-02 2009-06-10 天津曙光计算机产业有限公司 基于数据库的海量文件管理系统与方法
JP4285420B2 (ja) * 2005-02-22 2009-06-24 株式会社日立製作所 センサネット管理システム
US7589637B2 (en) * 2005-12-30 2009-09-15 Healthsense, Inc. Monitoring activity of an individual

Patent Citations (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6131119A (en) * 1997-04-01 2000-10-10 Sony Corporation Automatic configuration system for mapping node addresses within a bus structure to their physical location
US20040103139A1 (en) * 2000-03-30 2004-05-27 United Devices, Inc. Distributed processing system having sensor based data collection and associated method
US20020082879A1 (en) * 2000-08-31 2002-06-27 Brent Miller Method and system for seat selection and ticket purchasing in a networked computer system
US20040254652A1 (en) * 2001-10-04 2004-12-16 Shunji Ota Method for managing sensor network system, program for managing sensor network system,record medium with recorde program for managing sensor network system, apparatus for managing sensor network system, method for managing relay network, program for managing relay network, record medium
US7109875B2 (en) * 2001-10-04 2006-09-19 Omron Corporation Sensor network system managing method, sensor network system managing program, storage medium containing sensor network system managing program, sensor network system managing device, relay network managing method, relay network managing program, storage medium containing relay network managing program, and relay network managing device
US20040177319A1 (en) * 2002-07-16 2004-09-09 Horn Bruce L. Computer system for automatic organization, indexing and viewing of information from multiple sources
US20040093239A1 (en) * 2002-11-13 2004-05-13 Biomedical Systems Corporation System and method for handling the acquisition and analysis of medical data over a network
US20070198708A1 (en) * 2005-01-14 2007-08-23 Norihiko Moriwaki Sensor network system and data retrieval method for sensing data
US20060173995A1 (en) * 2005-01-28 2006-08-03 Hitachi, Ltd. Processing method for sensing data
US20070171052A1 (en) * 2005-03-03 2007-07-26 Norihiko Moriwaki Sensor network system and data retrieval method for sensing data
US20060202834A1 (en) * 2005-03-03 2006-09-14 Norihiko Moriwaki Sensor network system and data retrieval method for sensing data
US7298259B2 (en) * 2005-03-03 2007-11-20 Hitachi, Ltd. Sensor network system and data retrieval method for sensing data
US7403114B2 (en) * 2005-03-03 2008-07-22 Hitachi, Ltd. Sensor network system and data retrieval method for sensing data
US20060242285A1 (en) * 2005-03-24 2006-10-26 Norihiko Moriwaki Sensor network system and data transfer method for sensing data
US20070019452A1 (en) * 2005-07-11 2007-01-25 Hitachi, Ltd. Electronic apparatus and sensor network system
US7366579B2 (en) * 2005-10-11 2008-04-29 Hitachi, Ltd. Work management support method and work management support system which use sensor nodes
US20070083283A1 (en) * 2005-10-11 2007-04-12 Koji Ara Work management support method and work management support system which use sensor nodes
US20080189157A1 (en) * 2005-10-11 2008-08-07 Koji Ara Work management support method and work management support system which use sensor nodes
US20070282944A1 (en) * 2005-12-05 2007-12-06 Toshiyuki Odaka Sensor network system, gateway node, and method for relaying data of sensor network system
US20070299956A1 (en) * 2005-12-05 2007-12-27 Toshiyuki Odaka Sensor network system, gateway node, and method for relaying data of sensor network system
US20070262863A1 (en) * 2006-05-08 2007-11-15 Toshiyuki Aritsuka Sensor network system and sensor network position specifying method
US20080055113A1 (en) * 2006-08-30 2008-03-06 Hitachi, Ltd. Sensor network system and data management method for sensor network
US20080071899A1 (en) * 2006-09-14 2008-03-20 Hitachi, Ltd. Sensor network system for managing the latest data and history data
US20080143512A1 (en) * 2006-12-14 2008-06-19 Yoshihiro Wakisaka Wireless communication system and wireless terminal apparatus for sensor network
US20090189977A1 (en) * 2008-01-25 2009-07-30 International Business Machines Corporation System and method for spotlight identification of audience members during question and answer sessions

Cited By (54)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8671136B2 (en) * 2005-01-14 2014-03-11 Hitachi, Ltd. Sensor network system and data retrieval method for sensing data
US20060259255A1 (en) * 2005-04-05 2006-11-16 Anderson James C Method of visualizing power system quantities using a configurable software visualization tool
US20060282498A1 (en) * 2005-06-09 2006-12-14 Hitach, Ltd. Sensor network system, method for data processing of a sensor network system
US20080259919A1 (en) * 2005-09-27 2008-10-23 Nortel Networks Limited Method for Dynamic Sensor Network Processing
US8619768B2 (en) 2005-09-27 2013-12-31 Avaya, Inc. Method for dynamic sensor network processing
US20080267181A1 (en) * 2005-11-08 2008-10-30 Nortel Networks Limited Selective Multicasting of Sensor Data for Reliable Delivery
US20070299956A1 (en) * 2005-12-05 2007-12-27 Toshiyuki Odaka Sensor network system, gateway node, and method for relaying data of sensor network system
US20070282944A1 (en) * 2005-12-05 2007-12-06 Toshiyuki Odaka Sensor network system, gateway node, and method for relaying data of sensor network system
US20080004994A1 (en) * 2006-06-16 2008-01-03 Federal Express Corporation Methods and systems for providing sensor data using a sensor web
US9163962B2 (en) * 2006-06-16 2015-10-20 Fedex Corporate Services, Inc. Methods and systems for providing sensor data using a sensor web
US10382885B2 (en) 2006-06-16 2019-08-13 Fedex Corporate Services, Inc. Methods and systems for providing sensor data using a sensor web
US20130238779A1 (en) * 2006-06-29 2013-09-12 Electronics And Telecommunications Research Institute Data structure for managing sensor network using id of sensor node and method using the same
US20090198806A1 (en) * 2006-06-29 2009-08-06 Electronics And Telecommunications Research Instit Data structure for managing sensor network using id of sensor node and method using the same
EP2060062A4 (en) * 2006-09-01 2014-05-21 Korea Electronics Telecomm USN MIDDLEWARE DEVICE AND METHOD FOR GENERATING INFORMATION BASED ON DATA FROM HETEROGENIC SENSOR NETWORKS AND INFORMATION SERVICE PROCESSING SYSTEM THEREWITH
EP2060062A1 (en) * 2006-09-01 2009-05-20 Electronics and Telecommunications Research Institute Usn middleware apparatus and method for generating information based on data from heterogeneous sensor networks and information service providing system using the same
US20080104530A1 (en) * 2006-10-31 2008-05-01 Microsoft Corporation Senseweb
US7971143B2 (en) * 2006-10-31 2011-06-28 Microsoft Corporation Senseweb
JP2010514009A (ja) * 2006-12-14 2010-04-30 ラム リサーチ コーポレーション 一次サーバーアーキテクチャネットワーク構成およびその方法
US7555412B2 (en) 2007-02-09 2009-06-30 Microsoft Corporation Communication efficient spatial search in a sensor data web portal
US20080247313A1 (en) * 2007-04-03 2008-10-09 Microsoft Corporation Slot-Cache for Caching Aggregates of Data with Different Expiry Times
US8185355B2 (en) 2007-04-03 2012-05-22 Microsoft Corporation Slot-cache for caching aggregates of data with different expiry times
US8625575B1 (en) 2007-06-29 2014-01-07 Google Inc. Traffic-oblivious load balancing protocol for sensor networks
US8392401B1 (en) * 2007-06-29 2013-03-05 Google Inc. Query partitioning to decompose hotspots in sensor networks
US8085792B1 (en) 2007-06-29 2011-12-27 Google Inc. Traffic-oblivious load balancing protocol for sensor networks
US20120257624A1 (en) * 2007-11-13 2012-10-11 Cisco Technology, Inc. Routing operations using sensor data
US8515944B2 (en) * 2007-11-29 2013-08-20 Electronics And Telecommunications Research Institute Sensor network managing apparatus and method thereof
US20100306189A1 (en) * 2007-11-29 2010-12-02 Min Soo Kim Sensor network managing apparatus and method thereof
US20090144011A1 (en) * 2007-11-30 2009-06-04 Microsoft Corporation One-pass sampling of hierarchically organized sensors
US7933919B2 (en) * 2007-11-30 2011-04-26 Microsoft Corporation One-pass sampling of hierarchically organized sensors
US20110131320A1 (en) * 2007-12-17 2011-06-02 Electronics And Telecommunications Research Institute Apparatus and method of dynamically managing sensor module on sensor node in wireless sensor network
US20090198648A1 (en) * 2008-01-31 2009-08-06 Invensys Systems, Inc. System and method for adaptively retrieving parameter trend data from a supervisory control manufacturing/production database
US20110099054A1 (en) * 2008-05-26 2011-04-28 Hitachi, Ltd. Human behavior analysis system
KR101236990B1 (ko) 2009-12-21 2013-02-25 한국전자통신연구원 서버-센서네트워크의 협력 공간질의 처리방법 및 그 서버
US20110153655A1 (en) * 2009-12-21 2011-06-23 Electronics And Telecommunications Research Institute Server-sensor network cooperative spatial query processing method and server using the same
US20120185458A1 (en) * 2011-01-18 2012-07-19 Microsoft Corporation Clustering crowd-sourced data to identify event beacons
US20120191413A1 (en) * 2011-01-26 2012-07-26 Hitachi, Ltd. Sensor information analysis system and analysis server
US20140087695A1 (en) * 2011-05-12 2014-03-27 Telefonaktiebolaget L M Ericsson (Publ) Sensor Data Distribution System
CN102289452A (zh) * 2011-06-20 2011-12-21 中兴通讯股份有限公司 一种电信网管性能数据输出的方法及装置
US8954364B2 (en) 2011-09-19 2015-02-10 International Business Machines Corporation Hierarchical contexts to drive live sensor applications
US11283668B2 (en) 2012-07-17 2022-03-22 Pelion (Finland) Oy Method and apparatus in a web service system
US10630528B2 (en) * 2012-07-17 2020-04-21 Arm Finland Oy Method and apparatus in a web service system
US20140025825A1 (en) * 2012-07-17 2014-01-23 Sensinode Oy Method and apparatus in a web service system
JP2014038568A (ja) * 2012-08-20 2014-02-27 Tsukasa Hashimoto 検出システム、センサ、設定情報管理方法及びプログラム
US20140201356A1 (en) * 2013-01-16 2014-07-17 Delta Electronics, Inc. Monitoring system of managing cloud-based hosts and monitoring method using for the same
US9467274B2 (en) * 2013-07-25 2016-10-11 Verizon Patent And Licensing Inc. Processing communications via a sensor network
US20150031381A1 (en) * 2013-07-25 2015-01-29 Verizon Patent And Licensing Inc. Processing communications via a sensor network
US9985860B2 (en) 2013-09-23 2018-05-29 Schweitzer Engineering Laboratories, Inc. Selection and display of polled and streamed electric power system measurements
US20220351522A1 (en) * 2014-06-30 2022-11-03 Nec Corporation Guidance processing apparatus and guidance method
CN104392296A (zh) * 2014-10-24 2015-03-04 东北大学 一种轧机多智能体模型系统的信息交换方法
US10838937B2 (en) 2016-11-30 2020-11-17 Fujitsu Limited Distributed data management apparatus, non-transitory computer-readable storage medium, and distributed data management method
US10855526B2 (en) 2017-02-06 2020-12-01 Yokogawa Electric Corporation Sensor registration method, sensor registration system, and relay device
US10664553B2 (en) 2017-10-06 2020-05-26 Schweitzer Engineering Laboratories, Inc. Generating a representation of high-frequency signal data from an electric power delivery system
US11334829B2 (en) * 2019-12-19 2022-05-17 Honeywell International Inc. Methods and systems for electronic checklist data references
US11899517B2 (en) 2021-08-26 2024-02-13 Schweitzer Engineering Laboratories, Inc. Event analysis and display

Also Published As

Publication number Publication date
CN1805349B (zh) 2011-07-27
CN1805349A (zh) 2006-07-19
US8671136B2 (en) 2014-03-11
JP2006195788A (ja) 2006-07-27
JP4808409B2 (ja) 2011-11-02
CN101241510A (zh) 2008-08-13
US20070198708A1 (en) 2007-08-23
CN101241510B (zh) 2012-05-02

Similar Documents

Publication Publication Date Title
US8671136B2 (en) Sensor network system and data retrieval method for sensing data
US7298259B2 (en) Sensor network system and data retrieval method for sensing data
US7860917B2 (en) Sensor network system and data transfer method for sensing data
JP5328829B2 (ja) センサネットワークシステム、センサデータの検索方法
US7982603B2 (en) Sensor net system, sensor net system data managing method, and sensor net system data managing program
US8040232B2 (en) USN middleware apparatus and method for generating information based on data from heterogeneous sensor networks and information service providing system using the same
JP5010985B2 (ja) センサノード
JP5672934B2 (ja) センシングデータ表示装置および表示システム
US20080164997A1 (en) Sensor-net systems and its application systems for locationing
JP2006344017A (ja) センサネットワークシステム及びセンサネットワークのデータ処理方法
US20060173995A1 (en) Processing method for sensing data
US20120165988A1 (en) Method and apparatus for collecting building management data
CN113168419A (zh) 数据检索装置及其数据检索方法和程序、边缘服务器及其程序
CN108965436B (zh) 基于传感器网络的气体检测系统用高效稳定通讯系统
CN104483880B (zh) 一种数据采集方法及数据采集服务器
JP5147771B2 (ja) 消費情報地図表示装置、消費情報地図表示システム、および消費情報地図表示方法
CN108462741A (zh) 一种施工用管控系统的服务器集群及数据分析方法
JPH09120379A (ja) 開発支援システムおよび開発支援方法
CN115840726A (zh) 一种基于节点串行采集数据处理的方法与装置
Toninelli et al. An Open Source Platform for Business Process Mining

Legal Events

Date Code Title Description
AS Assignment

Owner name: HITACHI, LTD., JAPAN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:MORIWAKI, NORIHIKO;ODAKA, TOSHIYUKI;REEL/FRAME:016921/0941

Effective date: 20050729

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION