[go: up one dir, main page]

US12074945B2 - Data collection system and data collection method - Google Patents

Data collection system and data collection method Download PDF

Info

Publication number
US12074945B2
US12074945B2 US17/800,739 US202017800739A US12074945B2 US 12074945 B2 US12074945 B2 US 12074945B2 US 202017800739 A US202017800739 A US 202017800739A US 12074945 B2 US12074945 B2 US 12074945B2
Authority
US
United States
Prior art keywords
data
data collection
metadata
terminal
information
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.)
Active, expires
Application number
US17/800,739
Other versions
US20230105373A1 (en
Inventor
Tomohiro Taniguchi
Shinya Tamaki
Tetsuya Suzuki
Yasutaka Kimura
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.)
Nippon Telegraph and Telephone Corp
Original Assignee
Nippon Telegraph and Telephone Corp
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 Nippon Telegraph and Telephone Corp filed Critical Nippon Telegraph and Telephone Corp
Assigned to NIPPON TELEGRAPH AND TELEPHONE CORPORATION reassignment NIPPON TELEGRAPH AND TELEPHONE CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: TAMAKI, Shinya, TANIGUCHI, TOMOHIRO, Kimura, Yasutaka, SUZUKI, TETSUYA
Publication of US20230105373A1 publication Critical patent/US20230105373A1/en
Application granted granted Critical
Publication of US12074945B2 publication Critical patent/US12074945B2/en
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/12Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12Discovery or management of network topologies
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/34Signalling channels for network management communication
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/56Provisioning of proxy services
    • H04L67/567Integrating service provisioning from a plurality of service providers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30Services specially adapted for particular environments, situations or purposes
    • H04W4/38Services specially adapted for particular environments, situations or purposes for collecting sensor information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00Reducing energy consumption in communication networks

Definitions

  • the present disclosure relates to sensing data collection in the Internet of Things (IoT).
  • IoT Internet of Things
  • Network configuration information or instrument information of a terminal or an instrument is acquired using a lightweight communication protocol that is standardized and does not need high performance.
  • NPL 1 reports a method using link layer discovery protocol (LLDP).
  • LLDP link layer discovery protocol
  • NPL 2 data relating to the sensing data
  • users can utilize the sensing data safely and easily by acquiring and distributing the sensing data and the metadata together.
  • metadata instrument information
  • a maker's name or a model number related to the sensing data can be collected with an economical system configuration.
  • Metadata includes not only instrument information such as a product name/model number but also information relating to installation conditions such as the installation position/installer of a sensor instrument and information relating to a target to be observed by a sensor device (see, for example, NPL 2).
  • an object of the present disclosure is to provide a data collection system and a data collection method which are capable of collecting various pieces of metadata other than sensing data and instrument information by existing communication protocols and associating the sensing data, the instrument information, and the metadata with each other without errors.
  • a center terminal transmits various pieces of metadata by the extension or option function of existing communication protocols used to collect sensing data or instrument information.
  • a data collection system that performs communication from a terminal to a data collection unit by one or a plurality of communication protocols, in which the terminal includes a detection unit other than a sensor device that detects sensing data and instrument information, and stores metadata that is information detected by the detection unit in an extended field specified by the one or the plurality of communication protocols within a frame specified by the one or the plurality of communication protocols for transmitting the sensing data or the instrument information, and the data collection unit associates the sensing data, the instrument information, and the metadata with each other based on information for identifying the terminal described in the frame.
  • a data collection method for performing communication from a terminal to a data collection unit by one or a plurality of communication protocols, the method including acquiring, by the terminal, metadata that is information detected by a detection unit other than a sensor device that detects sensing data and instrument information, storing, by the terminal, the metadata in an extended field specified by the one or the plurality of communication protocols within a frame specified by the one or the plurality of communication protocols for transmitting the sensing data or the instrument information, and associating, by the data collection unit, the sensing data, the instrument information, and the metadata with each other based on information for identifying the terminal described in the frame.
  • the data collection unit can collectively collect the sensing data, the instrument information, and various pieces of metadata.
  • the data collection unit can collectively collect the sensing data, the instrument information, and various pieces of metadata.
  • the present disclosure can provide a data collection system and a data collection method which are capable of collecting various pieces of metadata other than sensing data and instrument information by existing communication protocols and associating the sensing data, the instrument information, and the metadata with each other without errors.
  • the terminal processes and stores the metadata to fit into the extended field, or divides the metadata to fit into the extended field and stores the divided metadata in a plurality of frames.
  • the terminal may make, as the metadata, a record in which the information detected by the detection unit is accumulated for a certain period of time or a result obtained by performing specific calculation.
  • the terminal may change, spontaneously or in accordance with an instruction from the data collection unit, at least one of a detail detected by the detection unit or a timing at which the detection unit detects information.
  • the one or the plurality of communication protocols of the frame in which the metadata is stored are link layer discovery protocol (LLDP) or home-network topology identifying protocol (HTIP).
  • LLDP and HTIP are lightweight communication protocols that are standardized in the data collection system of the IoT and do not need high performance. It is possible to avoid an increase in system cost and the complication of operations by adopting these communication protocols.
  • the terminal can change a transmission interval of the frame spontaneously or in accordance with an instruction from the data collection unit.
  • the present disclosure can provide a data collection system and a data collection method which are capable of collecting various pieces of metadata other than sensing data and instrument information by existing communication protocols and associating the sensing data, the instrument information, and the metadata with each other without errors.
  • FIG. 1 is a diagram illustrating a data collection system according to the present disclosure.
  • FIG. 2 is a diagram illustrating a terminal included in the data collection system according to the present disclosure.
  • FIG. 3 is a diagram illustrating a data collection unit included in the data collection system according to the present disclosure.
  • FIG. 4 is a diagram illustrating a data collection system according to the present disclosure.
  • FIG. 5 is a diagram illustrating a terminal included in the data collection system according to the present disclosure.
  • FIG. 6 is a diagram illustrating a data collection unit included in the data collection system according to the present disclosure.
  • FIG. 7 is a diagram illustrating an example in which the data collection system according to the present disclosure stores instrument information and metadata in a frame.
  • FIG. 8 is a diagram illustrating an example in which the data collection system according to the present disclosure stores instrument information and metadata in a frame.
  • FIG. 1 is a diagram illustrating a data collection system 301 according to the present embodiment.
  • the data collection system 301 is a data collection system that performs communication from a terminal 11 to a data collection unit 12 by one or a plurality of communication protocols, in which the terminal 11 includes a detection unit 11 e other than a sensor device 11 a that detects sensing data and instrument information and stores metadata that is information detected by the detection unit 11 e in an extended field specified by the communication protocols within a frame specified by the communication protocols for transmitting the sensing data or the instrument information, and the data collection unit 12 associates the sensing data, the instrument information, and the metadata with each other based on information for identifying the terminal 11 described in the frame.
  • a data collection network 15 is a network that connects the sensor terminal 11 present in a specific range and the data collection unit 12 .
  • the data collection network 15 is, for example, a local area network (LAN), a field area network (FAN), an IoT area network, and the like.
  • the sensor terminal 11 senses a target for observation and generates sensing data.
  • the sensor terminal 11 collectively transmits the sensing data, the instrument information, and the metadata to the data collection unit 13 by one or a plurality of communication protocols. The details of the sensor terminal 11 will be described below.
  • Wi-Fi wireless
  • LPWA wireless
  • Ethernet trademark
  • PLC conducting wires
  • PLC Single Pair Ethernet
  • optical fiber optical fiber
  • LLPD various protocols for instrument information collection
  • HTIP home network protocol
  • communication protocols used in the data collection network 15 may be of a single type or may be of multiple types.
  • the data collection unit 12 is, for example, an IoT gateway, an access point, or any of various other storage devices.
  • the data collection unit 12 passes the collected sensing data, instrument information, and metadata as information in a state associated with the sensor terminal 11 to a data analysis unit 13 .
  • the details of the data collection unit 12 will also be described below.
  • the data analysis unit 13 stores the information passed from the data collection unit 12 and uses the stored information for analysis.
  • the data analysis unit 13 may be in the same device as the data collection unit 12 or may be in a separate device. In a case where the data analysis unit is in a separate device, it may be located away from the data collection unit 12 through a network.
  • FIG. 2 is a diagram illustrating the sensor terminal 11 .
  • the sensor terminal 11 includes the sensor device 11 a , an instrument information storage processing unit 11 b , a sensing data storage processing unit 11 c , a protocol operation unit 11 d , the detection unit 11 e , and a metadata storage processing unit 11 f .
  • the sensor device 11 a senses a target for observation.
  • the instrument information storage processing unit 11 b collects instrument information of a target for observation (such as, for example, the maker's name, model name, and model number of an instrument), and stores the information at a predetermined position in a frame (a field that can be used for an original application such as an “extended field” or an “optional field” specified by protocols).
  • the sensing data storage processing unit 11 c stores the sensing data from the sensor device 11 a at a predetermined position in a frame (such as a payload portion specified by protocols).
  • the detection unit 11 e acquires information (metadata) other than the instrument information.
  • the information other than the instrument information is position information of a target for detection, installer information, and environmental information.
  • the detection unit 11 e includes a position information detection unit 11 e 1 , an installer detection unit 11 e 2 , and an environmental information detection unit 11 e 3 in order to acquire such pieces of information.
  • the position information detection unit 11 e 1 is, for example, a GPS, an acceleration sensor, a gyro sensor, or an RSSI receiver of a Wi-Fi signal, a BLE beacon signal, or the like.
  • the installer detection unit 11 e 2 is, for example, a fingerprint sensor, a vein sensor, a camera (face/iris recognition), or a microphone (voiceprint detection) in a case where an installer is identified, and is a receiver that receives output values of a sensor worn by the installer (such as blood pressure, heartbeat, movement speed, speech, or conversation) in a case where the status of the installer is confirmed.
  • the environmental information detection unit 11 e 3 is, for example, a camera (video information) or an environmental sensor of temperature, humidity, illuminance, air pressure, sound, infrared/ultraviolet light, or the like.
  • the detection unit 11 e may detect all of a plurality of targets for detection or may detect any one of them.
  • the metadata storage processing unit 11 f stores the data detected by the detection unit 11 e as metadata in an extended field or an optional field within a frame which is set by a communication protocol.
  • the protocol operation unit 11 d transmits a frame in which the sensing data or the instrument information is stored in a predetermined field and metadata is stored in an extended field or an optional field to the data collection unit 12 .
  • the communication protocol of a frame in which the sensing data is stored and the communication protocol of a frame in which the instrument information is stored may be the same as each other or may be different from each other.
  • the metadata storage processing unit 11 f may store the metadata in a frame of any one communication protocol (a frame in which the sensing data is stored or a frame in which the instrument information is stored), or may store the metadata in frames of both communication protocols (a frame in which the sensing data is stored and a frame in which the instrument information is stored).
  • the metadata storage processing unit 11 f may store the metadata in a frame after processing such as converting the metadata into a certain abbreviated code and then storing it, or dividing the metadata and then storing them into a plurality of frames (fragmentation).
  • the metadata storage processing unit 11 f can freely set a storage timing at which the metadata is stored in a frame.
  • the storage timing may be set each time the metadata is updated, or the metadata may be stored at a timing when the metadata is accumulated for a certain period of time instead of being stored sequentially.
  • the metadata storage processing unit 1 if may store, in a frame, the record (log) of the accumulation or the result of specific calculation/statistical processing.
  • the detail and storage timing of the metadata stored in a frame may be fixed or variable.
  • the detail and storage timing of the metadata may be dynamically changed according to the decision of the sensor terminal 11 itself or instructions from the data analysis unit 13 and the data collection unit 12 .
  • FIG. 3 is a diagram illustrating the data collection unit 12 .
  • the data collection unit 12 includes a protocol operation unit 12 a , a collected data processing unit 12 b , and a data batch transmission unit 12 c .
  • the protocol operation unit 12 a receives a frame in which the metadata is stored in a specific extended field from the sensor terminal 11 .
  • the collected data processing unit 12 b extracts the sensing data, the instrument information, and the metadata from the received frame, and arranges them in a database based on information (example: a MAC address) for identifying the individual of the sensor terminal 11 .
  • the data batch transmission unit 12 c stores the data arranged in the database at a predetermined timing in a payload portion of a frame and transmits the frame to the data analysis unit 13 .
  • the data batch transmission unit 12 c may transmit only a portion of the data in the database or may transmit all the data, in accordance with the requirements of the data analysis unit 13 .
  • FIG. 4 is a diagram illustrating a data collection system 302 of the present embodiment.
  • the data collection system 302 is different from the data collection system 301 of FIG. 1 in that it includes a sensor terminal 21 as a substitute for the sensor terminal 11 and a data collection unit 22 as a substitute for the data collection unit 12 and that the communication protocol of a frame in which the metadata is stored is LLDP or HTIP.
  • the communication protocol of a frame in which the metadata is stored is LLDP or HTIP.
  • FIG. 5 is a diagram illustrating the sensor terminal 21 .
  • the sensor terminal 21 includes a communication protocol operation unit for sensing data 11 d 1 and an LLDP protocol operation unit 11 d 2 as a substitute for the communication protocol operation unit 11 d of the sensor terminal 11 .
  • the communication protocol operation unit for sensing data 11 d 1 transmits a frame in which the sensing data is stored by the sensing data storage processing unit 11 c to the data collection unit 22 using any communication protocol (such as, for example, Ethernet (trade name), Wi-Fi, or LPWA).
  • any communication protocol such as, for example, Ethernet (trade name), Wi-Fi, or LPWA).
  • the LLDP protocol operation unit 11 d 2 transmits a frame in which instrument information such as the product name/model number of the sensor terminal 21 and network configuration information are stored by the instrument information storage processing unit 11 b and various pieces of metadata are stored by the metadata storage processing unit 1 if to the data collection unit 22 using LLDP or HTIP. How the instrument information storage processing unit 11 b and the metadata storage processing unit 11 f store this information in a frame will be described below. Meanwhile, the LLDP protocol operation unit 11 d 2 may fix the transmission interval of the frame, or may change it spontaneously or in accordance with an instruction from the data collection unit.
  • FIG. 6 is a diagram illustrating the data collection unit 22 .
  • the data collection unit 22 includes a communication protocol operation unit for sensing data 12 a 1 and an LLDP protocol operation unit 12 a 2 as a substitute for the protocol operation unit 12 a of the data collection unit 12 .
  • the communication protocol operation unit for sensing data 12 a 1 receives a frame in which the sensing data transmitted from each sensor terminal 21 is stored.
  • the LLDP protocol operation unit 12 a 2 receives a frame in which the instrument information and the metadata transmitted from each sensor terminal 21 are stored.
  • the collected data processing unit 12 b extracts the sensing data, the instrument information, and the metadata from each received frame, and arranges them in a database based on information for identifying the individual of the sensor terminal 11 .
  • the information for identifying the individual of the sensor terminal 11 is, for example, a MAC address which is commonly used in a communication protocol for sensing data and an LLDP protocol.
  • the collected data processing unit 12 b associates the sensing data, the instrument information, and the metadata with each other based on this MAC address.
  • FIG. 7 is a diagram illustrating an example in which instrument information and metadata are stored in a frame in a case where the LLDP protocol operation unit 11 d 2 adopts LLDP (see, for example NPL 3) as a communication protocol.
  • FIG. 7 (A) is a diagram illustrating a frame structure of LLDP.
  • the frame of LLDP is constituted by a header and a data unit.
  • FIG. 7 (B) is a diagram illustrating a format of the data unit.
  • the data unit is constituted by a mandatory TLV, an optional TLV, and a terminal TLV.
  • FIG. 7 (C) is a diagram illustrating a format of one optional TLV.
  • the optional TLV is constituted by a TLV type, a TLV length, and an information field.
  • FIG. 7 (A) is a diagram illustrating a frame structure of LLDP.
  • the frame of LLDP is constituted by a header and a data unit.
  • FIG. 7 (B)
  • TLV 7 (D) is a list of optional TLV types.
  • various pieces of information such as a device name, a maker's name, a MAC address, or an IP address can be stored as instrument information in the information field of the optional TLV.
  • the information field of the optional TLV becomes an extended field, which makes it possible to store metadata.
  • FIG. 8 is a diagram illustrating an example in which instrument information and metadata are stored in a frame in a case where the LLDP protocol operation unit 11 d 2 adopts HTIP (see, for example, NPL 4) as a communication protocol.
  • FIG. 8 (A) is a diagram illustrating a frame structure of HTIP.
  • the frame of HTIP is constituted by a field for describing a TLV type and length and a data field.
  • FIG. 8 (B) is a diagram illustrating a format of the data field.
  • the data field is constituted by an instrument information ID, an instrument information data length, and instrument information.
  • FIG. 8 (C) is a list of instrument information IDs.
  • instrument information ID In a case where “1” to “4”, “20” to “27”, and “50” to “54” are input to the instrument information ID, various pieces of information such as a device name, a maker's name, a MAC address, or an IP address can be stored as instrument information in the instrument information field of the data field. In addition, in a case where “255” is input to the instrument information ID, the instrument information field of the data field becomes a vendor-specific extended field, which makes it possible to store metadata.
  • the sensor terminal ( 11 , 21 ) and the data collection unit ( 12 , 22 ) described above can also be implemented by a computer and a program, and the program can also be recorded in a recording medium or provided through a network.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Arrangements For Transmission Of Measured Signals (AREA)
  • Selective Calling Equipment (AREA)

Abstract

An object of the present disclosure is to provide a data collection system capable of collecting various pieces of metadata other than sensing data and instrument information by existing communication protocols and associating the sensing data, the instrument information, and the metadata with each other without errors. A data collection system 301 is a data collection system that performs communication from a terminal 11 to a data collection unit 12 by one or a plurality of communication protocols, in which the terminal 11 includes a detection unit 11 e other than a sensor device 11 a that detects the sensing data and the instrument information, and stores metadata that is information detected by the detection unit 11 e in an extended field specified by the communication protocols within a frame specified by the communication protocols for transmitting the sensing data or the instrument information, and the data collection unit 12 associates the sensing data, the instrument information, and the metadata with each other based on information for identifying the terminal 11 described in the frame.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS
This application is a 371 U.S. National Phase of International Application No. PCT/JP2020/007248, filed on Feb. 21, 2020. The entire disclosure of the above application is incorporated herein by reference.
TECHNICAL FIELD
The present disclosure relates to sensing data collection in the Internet of Things (IoT).
BACKGROUND ART
Network configuration information or instrument information of a terminal or an instrument is acquired using a lightweight communication protocol that is standardized and does not need high performance. For example, NPL 1 reports a method using link layer discovery protocol (LLDP).
In the IoT, a large number of sensor terminals are connected to a network to collect data (sensing data) generated by these sensor terminals. In addition, in data utilization in the IoT, the importance of not only sensing data generated by the sensor terminals but also data relating to the sensing data called metadata has been reported (NPL 2 or the like), and it is expected that users can utilize the sensing data safely and easily by acquiring and distributing the sensing data and the metadata together. For example, in a case where LLDP disclosed in NPL 1 is used, metadata (instrument information) such as a maker's name or a model number related to the sensing data can be collected with an economical system configuration.
CITATION LIST Non Patent Literature
    • NPL 1: Yoshiyuki Mihara, Takefumi Yamazaki, Manabu Okamoto, Atsushi Sato, “Designing HTIP which Identifies Home Network Topology and Applying HTIP to a Troubleshooting Application”, Transactions of Information Processing Society of Japan Consumer Devices & Systems, Vol. 2, No. 3, pp. 34-45, December 2012.
    • NPL 2: Toshihiko Oda, Hiroshi Imai, Takeshi Naito, Hajime Takebayashi, “An Approach of Defining, Generating and Utilizing Metadata for Sensing Data Trading Market”, Proceedings of the Annual Conference of the Japanese Society for Artificial Intelligence, 2018 (32nd), June 2012.
    • NPL 3: IEEE Std 802.1AB-2016, “IEEE Standard for Local and metropolitan area networks-Station and Media Access Control Connectivity Discovery” NPL 4: TTC Standard JJ-300.00, “HTIP: Homenetwork Topology Identifying Protocol, Third Edition”, May 25, 2017
SUMMARY OF THE INVENTION Technical Problem
Metadata includes not only instrument information such as a product name/model number but also information relating to installation conditions such as the installation position/installer of a sensor instrument and information relating to a target to be observed by a sensor device (see, for example, NPL 2).
As a method of collecting this metadata which is information other than instrument information, it is conceivable to develop/construct a dedicated system and collect the metadata, or to manually collect the metadata and then associate the collected metadata with separately collected sensing data. However, these approaches have the following difficulties.
    • (1) The development/construction of a plurality of systems or the manual collection and operation will increase costs and complicate operations.
    • (2) Errors (for example, human errors) occur when separately acquired sensing data and metadata are associated with each other.
While a collection method for solving these difficulties is expected, specific measures have not been revealed. Consequently, in order to solve the above problems, an object of the present disclosure is to provide a data collection system and a data collection method which are capable of collecting various pieces of metadata other than sensing data and instrument information by existing communication protocols and associating the sensing data, the instrument information, and the metadata with each other without errors.
Means for Solving the Problem
In order to solve the above problems, in the data collection system according to the present disclosure, a center terminal transmits various pieces of metadata by the extension or option function of existing communication protocols used to collect sensing data or instrument information.
Specifically, according to the present disclosure, there is provided a data collection system that performs communication from a terminal to a data collection unit by one or a plurality of communication protocols, in which the terminal includes a detection unit other than a sensor device that detects sensing data and instrument information, and stores metadata that is information detected by the detection unit in an extended field specified by the one or the plurality of communication protocols within a frame specified by the one or the plurality of communication protocols for transmitting the sensing data or the instrument information, and the data collection unit associates the sensing data, the instrument information, and the metadata with each other based on information for identifying the terminal described in the frame.
In addition, according to the present disclosure, there is provided a data collection method for performing communication from a terminal to a data collection unit by one or a plurality of communication protocols, the method including acquiring, by the terminal, metadata that is information detected by a detection unit other than a sensor device that detects sensing data and instrument information, storing, by the terminal, the metadata in an extended field specified by the one or the plurality of communication protocols within a frame specified by the one or the plurality of communication protocols for transmitting the sensing data or the instrument information, and associating, by the data collection unit, the sensing data, the instrument information, and the metadata with each other based on information for identifying the terminal described in the frame.
Because the center terminal transmits various pieces of metadata by the extension or option function of existing communication protocols, the data collection unit can collectively collect the sensing data, the instrument information, and various pieces of metadata. Thus, it is possible to achieve an economical and reliable system by avoiding an increase in costs, complication of operation, and occurrence of errors when the sensing data, the instrument information, and the metadata are associated with each other, which have been problems in methods of the related art.
Thus, the present disclosure can provide a data collection system and a data collection method which are capable of collecting various pieces of metadata other than sensing data and instrument information by existing communication protocols and associating the sensing data, the instrument information, and the metadata with each other without errors.
There is a limitation to the size of an extended field in a frame of a standardized communication protocol. Thus, it is preferable that the terminal processes and stores the metadata to fit into the extended field, or divides the metadata to fit into the extended field and stores the divided metadata in a plurality of frames.
In addition, the terminal may make, as the metadata, a record in which the information detected by the detection unit is accumulated for a certain period of time or a result obtained by performing specific calculation.
The terminal may change, spontaneously or in accordance with an instruction from the data collection unit, at least one of a detail detected by the detection unit or a timing at which the detection unit detects information.
It is preferable that the one or the plurality of communication protocols of the frame in which the metadata is stored are link layer discovery protocol (LLDP) or home-network topology identifying protocol (HTIP). LLDP and HTIP are lightweight communication protocols that are standardized in the data collection system of the IoT and do not need high performance. It is possible to avoid an increase in system cost and the complication of operations by adopting these communication protocols.
In this case, the terminal can change a transmission interval of the frame spontaneously or in accordance with an instruction from the data collection unit.
Effects of the Invention
The present disclosure can provide a data collection system and a data collection method which are capable of collecting various pieces of metadata other than sensing data and instrument information by existing communication protocols and associating the sensing data, the instrument information, and the metadata with each other without errors.
BRIEF DESCRIPTION OF DRAWINGS
FIG. 1 is a diagram illustrating a data collection system according to the present disclosure.
FIG. 2 is a diagram illustrating a terminal included in the data collection system according to the present disclosure.
FIG. 3 is a diagram illustrating a data collection unit included in the data collection system according to the present disclosure.
FIG. 4 is a diagram illustrating a data collection system according to the present disclosure.
FIG. 5 is a diagram illustrating a terminal included in the data collection system according to the present disclosure.
FIG. 6 is a diagram illustrating a data collection unit included in the data collection system according to the present disclosure.
FIG. 7 is a diagram illustrating an example in which the data collection system according to the present disclosure stores instrument information and metadata in a frame.
FIG. 8 is a diagram illustrating an example in which the data collection system according to the present disclosure stores instrument information and metadata in a frame.
DESCRIPTION OF EMBODIMENTS
Embodiments of the present disclosure will be described below with reference to the accompanying drawings. The embodiments to be described below are examples of the present disclosure, and the present disclosure is not limited to the following embodiments. In this description and the drawings, constituent elements having the identical reference signs are assumed to be the same as each other.
Embodiment 1
FIG. 1 is a diagram illustrating a data collection system 301 according to the present embodiment. The data collection system 301 is a data collection system that performs communication from a terminal 11 to a data collection unit 12 by one or a plurality of communication protocols, in which the terminal 11 includes a detection unit 11 e other than a sensor device 11 a that detects sensing data and instrument information and stores metadata that is information detected by the detection unit 11 e in an extended field specified by the communication protocols within a frame specified by the communication protocols for transmitting the sensing data or the instrument information, and the data collection unit 12 associates the sensing data, the instrument information, and the metadata with each other based on information for identifying the terminal 11 described in the frame.
A data collection network 15 is a network that connects the sensor terminal 11 present in a specific range and the data collection unit 12. The data collection network 15 is, for example, a local area network (LAN), a field area network (FAN), an IoT area network, and the like.
The sensor terminal 11 senses a target for observation and generates sensing data. In the same data collection network 15, there may be a plurality of sensor terminals 11 of a single type and there may be multiple types of sensor terminals. The sensor terminal 11 collectively transmits the sensing data, the instrument information, and the metadata to the data collection unit 13 by one or a plurality of communication protocols. The details of the sensor terminal 11 will be described below.
Various protocols for data communication such as wireless (Wi-Fi, LPWA), conducting wires (Ethernet (trade name), PLC, Single Pair Ethernet), or optical fiber (Ethernet, PON), as well as various protocols for instrument information collection such as LLPD, a home network protocol such as HTIP, and the like can be given as examples of the communication protocol. In addition, communication protocols used in the data collection network 15 may be of a single type or may be of multiple types.
The data collection unit 12 is, for example, an IoT gateway, an access point, or any of various other storage devices. The data collection unit 12 passes the collected sensing data, instrument information, and metadata as information in a state associated with the sensor terminal 11 to a data analysis unit 13. The details of the data collection unit 12 will also be described below.
The data analysis unit 13 stores the information passed from the data collection unit 12 and uses the stored information for analysis. The data analysis unit 13 may be in the same device as the data collection unit 12 or may be in a separate device. In a case where the data analysis unit is in a separate device, it may be located away from the data collection unit 12 through a network.
FIG. 2 is a diagram illustrating the sensor terminal 11. The sensor terminal 11 includes the sensor device 11 a, an instrument information storage processing unit 11 b, a sensing data storage processing unit 11 c, a protocol operation unit 11 d, the detection unit 11 e, and a metadata storage processing unit 11 f. The sensor device 11 a senses a target for observation. The instrument information storage processing unit 11 b collects instrument information of a target for observation (such as, for example, the maker's name, model name, and model number of an instrument), and stores the information at a predetermined position in a frame (a field that can be used for an original application such as an “extended field” or an “optional field” specified by protocols). The sensing data storage processing unit 11 c stores the sensing data from the sensor device 11 a at a predetermined position in a frame (such as a payload portion specified by protocols).
The detection unit 11 e acquires information (metadata) other than the instrument information. In the present embodiment, the information other than the instrument information is position information of a target for detection, installer information, and environmental information. However, the present disclosure does not limit the information other than the instrument information to such pieces of information. The detection unit 11 e includes a position information detection unit 11 e 1, an installer detection unit 11 e 2, and an environmental information detection unit 11 e 3 in order to acquire such pieces of information. The position information detection unit 11 e 1 is, for example, a GPS, an acceleration sensor, a gyro sensor, or an RSSI receiver of a Wi-Fi signal, a BLE beacon signal, or the like. The installer detection unit 11 e 2 is, for example, a fingerprint sensor, a vein sensor, a camera (face/iris recognition), or a microphone (voiceprint detection) in a case where an installer is identified, and is a receiver that receives output values of a sensor worn by the installer (such as blood pressure, heartbeat, movement speed, speech, or conversation) in a case where the status of the installer is confirmed. The environmental information detection unit 11 e 3 is, for example, a camera (video information) or an environmental sensor of temperature, humidity, illuminance, air pressure, sound, infrared/ultraviolet light, or the like.
Meanwhile, the detection unit 11 e may detect all of a plurality of targets for detection or may detect any one of them.
The metadata storage processing unit 11 f stores the data detected by the detection unit 11 e as metadata in an extended field or an optional field within a frame which is set by a communication protocol.
The protocol operation unit 11 d transmits a frame in which the sensing data or the instrument information is stored in a predetermined field and metadata is stored in an extended field or an optional field to the data collection unit 12. Meanwhile, the communication protocol of a frame in which the sensing data is stored and the communication protocol of a frame in which the instrument information is stored may be the same as each other or may be different from each other. In the latter case, the metadata storage processing unit 11 f may store the metadata in a frame of any one communication protocol (a frame in which the sensing data is stored or a frame in which the instrument information is stored), or may store the metadata in frames of both communication protocols (a frame in which the sensing data is stored and a frame in which the instrument information is stored).
In order to comply with the format/limitation of a specific extended field of a frame, the metadata storage processing unit 11 f may store the metadata in a frame after processing such as converting the metadata into a certain abbreviated code and then storing it, or dividing the metadata and then storing them into a plurality of frames (fragmentation).
The metadata storage processing unit 11 f can freely set a storage timing at which the metadata is stored in a frame. For example, the storage timing may be set each time the metadata is updated, or the metadata may be stored at a timing when the metadata is accumulated for a certain period of time instead of being stored sequentially. In addition, in a case where the metadata is accumulated for a certain period of time, the metadata storage processing unit 1 if may store, in a frame, the record (log) of the accumulation or the result of specific calculation/statistical processing.
The detail and storage timing of the metadata stored in a frame may be fixed or variable. The detail and storage timing of the metadata may be dynamically changed according to the decision of the sensor terminal 11 itself or instructions from the data analysis unit 13 and the data collection unit 12.
FIG. 3 is a diagram illustrating the data collection unit 12. The data collection unit 12 includes a protocol operation unit 12 a, a collected data processing unit 12 b, and a data batch transmission unit 12 c. The protocol operation unit 12 a receives a frame in which the metadata is stored in a specific extended field from the sensor terminal 11. The collected data processing unit 12 b extracts the sensing data, the instrument information, and the metadata from the received frame, and arranges them in a database based on information (example: a MAC address) for identifying the individual of the sensor terminal 11. The data batch transmission unit 12 c stores the data arranged in the database at a predetermined timing in a payload portion of a frame and transmits the frame to the data analysis unit 13. The data batch transmission unit 12 c may transmit only a portion of the data in the database or may transmit all the data, in accordance with the requirements of the data analysis unit 13.
Embodiment 2
FIG. 4 is a diagram illustrating a data collection system 302 of the present embodiment. The data collection system 302 is different from the data collection system 301 of FIG. 1 in that it includes a sensor terminal 21 as a substitute for the sensor terminal 11 and a data collection unit 22 as a substitute for the data collection unit 12 and that the communication protocol of a frame in which the metadata is stored is LLDP or HTIP. In the present embodiment, differences from the data collection system 301 of Embodiment 1 will be described.
FIG. 5 is a diagram illustrating the sensor terminal 21. The sensor terminal 21 includes a communication protocol operation unit for sensing data 11 d 1 and an LLDP protocol operation unit 11 d 2 as a substitute for the communication protocol operation unit 11 d of the sensor terminal 11.
The communication protocol operation unit for sensing data 11 d 1 transmits a frame in which the sensing data is stored by the sensing data storage processing unit 11 c to the data collection unit 22 using any communication protocol (such as, for example, Ethernet (trade name), Wi-Fi, or LPWA).
The LLDP protocol operation unit 11 d 2 transmits a frame in which instrument information such as the product name/model number of the sensor terminal 21 and network configuration information are stored by the instrument information storage processing unit 11 b and various pieces of metadata are stored by the metadata storage processing unit 1 if to the data collection unit 22 using LLDP or HTIP. How the instrument information storage processing unit 11 b and the metadata storage processing unit 11 f store this information in a frame will be described below. Meanwhile, the LLDP protocol operation unit 11 d 2 may fix the transmission interval of the frame, or may change it spontaneously or in accordance with an instruction from the data collection unit.
FIG. 6 is a diagram illustrating the data collection unit 22. The data collection unit 22 includes a communication protocol operation unit for sensing data 12 a 1 and an LLDP protocol operation unit 12 a 2 as a substitute for the protocol operation unit 12 a of the data collection unit 12. The communication protocol operation unit for sensing data 12 a 1 receives a frame in which the sensing data transmitted from each sensor terminal 21 is stored. The LLDP protocol operation unit 12 a 2 receives a frame in which the instrument information and the metadata transmitted from each sensor terminal 21 are stored.
The collected data processing unit 12 b extracts the sensing data, the instrument information, and the metadata from each received frame, and arranges them in a database based on information for identifying the individual of the sensor terminal 11. The information for identifying the individual of the sensor terminal 11 is, for example, a MAC address which is commonly used in a communication protocol for sensing data and an LLDP protocol. The collected data processing unit 12 b associates the sensing data, the instrument information, and the metadata with each other based on this MAC address.
FIG. 7 is a diagram illustrating an example in which instrument information and metadata are stored in a frame in a case where the LLDP protocol operation unit 11 d 2 adopts LLDP (see, for example NPL 3) as a communication protocol. FIG. 7(A) is a diagram illustrating a frame structure of LLDP. The frame of LLDP is constituted by a header and a data unit. FIG. 7(B) is a diagram illustrating a format of the data unit. The data unit is constituted by a mandatory TLV, an optional TLV, and a terminal TLV. FIG. 7(C) is a diagram illustrating a format of one optional TLV. The optional TLV is constituted by a TLV type, a TLV length, and an information field. FIG. 7(D) is a list of optional TLV types. In a case where “1” to “8” are input to the TLV type, various pieces of information such as a device name, a maker's name, a MAC address, or an IP address can be stored as instrument information in the information field of the optional TLV. In addition, in a case where “127” is input to the TLV type, the information field of the optional TLV becomes an extended field, which makes it possible to store metadata.
FIG. 8 is a diagram illustrating an example in which instrument information and metadata are stored in a frame in a case where the LLDP protocol operation unit 11 d 2 adopts HTIP (see, for example, NPL 4) as a communication protocol. FIG. 8(A) is a diagram illustrating a frame structure of HTIP. The frame of HTIP is constituted by a field for describing a TLV type and length and a data field. FIG. 8(B) is a diagram illustrating a format of the data field. The data field is constituted by an instrument information ID, an instrument information data length, and instrument information. FIG. 8(C) is a list of instrument information IDs. In a case where “1” to “4”, “20” to “27”, and “50” to “54” are input to the instrument information ID, various pieces of information such as a device name, a maker's name, a MAC address, or an IP address can be stored as instrument information in the instrument information field of the data field. In addition, in a case where “255” is input to the instrument information ID, the instrument information field of the data field becomes a vendor-specific extended field, which makes it possible to store metadata.
OTHER EMBODIMENTS
The sensor terminal (11, 21) and the data collection unit (12, 22) described above can also be implemented by a computer and a program, and the program can also be recorded in a recording medium or provided through a network.
REFERENCE SIGNS LIST
    • 11, 21 Sensor terminal
    • 11 a Sensor device
    • 11 b Instrument information storage processing unit
    • 11 c Sensing data storage processing unit
    • 11 d Protocol operation unit
    • 11 d 1 Communication protocol operation unit for sensing data
    • 11 d 2 LLDP protocol operation unit
    • 11 e Detection unit
    • 11 e 1 Position information detection unit
    • 11 e 2 Installer detection unit
    • 11 e 3 Environmental information detection unit
    • 11 f Metadata storage processing unit
    • 12, 22 Data collection unit
    • 12 a Protocol operation unit
    • 12 a 1 Communication protocol operation unit for sensing data
    • 12 a 2 LLDP protocol operation unit
    • 12 b Collected data processing unit
    • 12 c Data batch transmission unit
    • 13 Data analysis unit
    • 15 Data collection network
    • 301, 302 Data collection system

Claims (9)

The invention claimed is:
1. A data collection system configured to perform communication from a terminal to a data collection unit by one or a plurality of communication protocols, the data collection system including:
the terminal;
the data collection unit,
wherein the terminal includes a detection unit other than a sensor device that detects sensing data and instrument information, and stores metadata that is information detected by the detection unit in an extended field specified by the one or the plurality of communication protocols within a frame specified by the one or the plurality of communication protocols for transmitting the sensing data or the instrument information, and
the data collection unit associates in a database the sensing data, the instrument information, and the metadata with each other based on information for identifying the terminal described in the frame; and
a data batch transmission unit that stores the associated data at a predetermined timing in a payload portion of a frame and transmits at least a portion of the associated data in accordance with requirements of a data analysis unit.
2. The data collection system according to claim 1, wherein the terminal processes and stores the metadata to fit into the extended field.
3. The data collection system according to claim 1, wherein the terminal divides the metadata to fit into the extended field and stores pieces of metadata that are divided in a plurality of frames.
4. The data collection system according to claim 1, wherein the terminal makes, as the metadata, a record where the information detected by the detection unit is accumulated for a certain period of time or a result obtained by performing specific calculation.
5. The data collection system according to claim 1, wherein the terminal changes, spontaneously or in accordance with an instruction from the data collection unit, at least one of a detail detected by the detection unit or a timing when the detection unit detects information.
6. The data collection system according to claim 1, wherein the one or the plurality of communication protocols of the frame where the metadata is stored are link layer discovery protocol (LLDP) or home-network topology identifying protocol (HTIP).
7. The data collection system according to claim 6, wherein the terminal changes a transmission interval of the frame spontaneously or in accordance with an instruction from the data collection unit.
8. A data collection method for performing communication from a terminal to a data collection unit by one or a plurality of communication protocols, the method comprising:
acquiring, by the terminal, metadata that is information detected by a detection unit other than a sensor device that detects sensing data and instrument information;
storing, by the terminal, the metadata in an extended field specified by the one or the plurality of communication protocols within a frame specified by the one or the plurality of communication protocols for transmitting the sensing data or the instrument information; and
associating in a database, by the data collection unit, the sensing data, the instrument information, and the metadata with each other based on information for identifying the terminal described in the frame; and
by a data batch transmission unit, storing the associated data at a predetermined timing in a payload portion of a frame and transmitting at least a portion of the associated data in accordance with requirements of a data analysis unit.
9. A data collection system configured to perform communication from a terminal to a data collection unit by one or a plurality of communication protocols, the data collection system including:
the terminal;
the data collection unit,
wherein the terminal includes a detection unit other than a sensor device that detects sensing data and instrument information, and stores metadata that is information detected by the detection unit in an extended field specified by the one or the plurality of communication protocols within a frame specified by the one or the plurality of communication protocols for transmitting the sensing data or the instrument information, the extended field being an optional TLV field of the frame, and
the data collection unit associates in a database the sensing data, the instrument information, and the metadata with each other based on information for identifying the terminal described in the frame; and
a data batch transmission unit that stores the associated data at a predetermined timing in a payload portion of a frame and transmits at least a portion of the associated data in accordance with requirements of a data analysis unit.
US17/800,739 2020-02-21 2020-02-21 Data collection system and data collection method Active 2040-03-28 US12074945B2 (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2020/007248 WO2021166261A1 (en) 2020-02-21 2020-02-21 Data collection system and data collection method

Publications (2)

Publication Number Publication Date
US20230105373A1 US20230105373A1 (en) 2023-04-06
US12074945B2 true US12074945B2 (en) 2024-08-27

Family

ID=77391766

Family Applications (1)

Application Number Title Priority Date Filing Date
US17/800,739 Active 2040-03-28 US12074945B2 (en) 2020-02-21 2020-02-21 Data collection system and data collection method

Country Status (3)

Country Link
US (1) US12074945B2 (en)
JP (1) JP7388534B2 (en)
WO (1) WO2021166261A1 (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024122012A1 (en) * 2022-12-08 2024-06-13 日本電信電話株式会社 Data collection system

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2009260778A (en) 2008-04-18 2009-11-05 Hitachi High-Tech Control Systems Corp Sensor network gateway, and sensor network system
US20140155031A1 (en) 2012-12-03 2014-06-05 Samsung Electronics Co., Ltd. Method and mobile terminal for controlling screen lock
US20140361906A1 (en) * 2013-06-06 2014-12-11 Zih Corp. Method, apparatus, and computer program product improving backhaul of sensor and other data to real time location system network
US20150019710A1 (en) * 2013-07-11 2015-01-15 Neura, Inc. Interoperability mechanisms for internet of things integration platform
US20200026339A1 (en) * 2018-07-19 2020-01-23 Hewlett Packard Enterprise Development Lp Method for managing non-chatty iot devices to remain in an authenticated state
US20200137021A1 (en) * 2018-10-31 2020-04-30 Hewlett Packard Enterprise Development Lp Using intent to access in discovery protocols in a network for analytics
US20210184886A1 (en) * 2016-05-27 2021-06-17 Panasonic Intellectual Property Corporation Of America In-vehicle information processing for unauthorized data
US20220386090A1 (en) * 2020-02-19 2022-12-01 Pleiotek Wearable data storage and transmission device for processing sensor data
US20230336448A1 (en) * 2020-09-30 2023-10-19 Nippon Telegraph And Telephone Corporation Systems and methods for collecting metadata and sensor terminals

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2013152557A (en) * 2012-01-24 2013-08-08 Nippon Telegr & Teleph Corp <Ntt> Metadata attachment apparatus, metadata attachment method and metadata attachment program
JP6451820B1 (en) 2017-08-09 2019-01-16 オムロン株式会社 Sensor management unit, sensor device, sensor management method, and sensor management program

Patent Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2009260778A (en) 2008-04-18 2009-11-05 Hitachi High-Tech Control Systems Corp Sensor network gateway, and sensor network system
US20140155031A1 (en) 2012-12-03 2014-06-05 Samsung Electronics Co., Ltd. Method and mobile terminal for controlling screen lock
JP2014110638A (en) 2012-12-03 2014-06-12 Samsung Electronics Co Ltd Method for controlling screen lock and mobile terminal
US20210360404A1 (en) * 2012-12-03 2021-11-18 Samsung Electronics Co., Ltd. Method and mobile terminal for controlling screen lock
US20140361906A1 (en) * 2013-06-06 2014-12-11 Zih Corp. Method, apparatus, and computer program product improving backhaul of sensor and other data to real time location system network
US20150019710A1 (en) * 2013-07-11 2015-01-15 Neura, Inc. Interoperability mechanisms for internet of things integration platform
US20210184886A1 (en) * 2016-05-27 2021-06-17 Panasonic Intellectual Property Corporation Of America In-vehicle information processing for unauthorized data
US20200026339A1 (en) * 2018-07-19 2020-01-23 Hewlett Packard Enterprise Development Lp Method for managing non-chatty iot devices to remain in an authenticated state
US20200137021A1 (en) * 2018-10-31 2020-04-30 Hewlett Packard Enterprise Development Lp Using intent to access in discovery protocols in a network for analytics
US20220386090A1 (en) * 2020-02-19 2022-12-01 Pleiotek Wearable data storage and transmission device for processing sensor data
US20230336448A1 (en) * 2020-09-30 2023-10-19 Nippon Telegraph And Telephone Corporation Systems and methods for collecting metadata and sensor terminals

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
LAN/MAN Standards Committee of the IEEE Computer Society, IEEE Standard for Local and metropolitan area networks-Station and Media Access Control Connectivity Discovery, IEEE Std 802.1AB™-2016, Mar. 11, 2016.
The Telecommunication Technology Committee, HTIP: Home-network Topology Identifying Protocol, TTC Standard JJ-300.00, Version 3.0, May 25, 2017.
Toshihiko Oda et al., An Approach of Defining, Generating and Utilizing Metadata for Sensing Data Trading Market, The 32nd Annual Conference of the Japanese Society for Artificial Intelligence, 2018, Jun. 5, 2018.
Yoshiyuki Mihara et al., Designing HTIP which Identifies Home Network Topology and Applying HTIP to a Troubleshooting Application, Information Processing Society Journal Consumer Device & System, vol. 2, No. 3, 2012, pp. 34-45.

Also Published As

Publication number Publication date
JPWO2021166261A1 (en) 2021-08-26
JP7388534B2 (en) 2023-11-29
US20230105373A1 (en) 2023-04-06
WO2021166261A1 (en) 2021-08-26

Similar Documents

Publication Publication Date Title
WO2022149250A1 (en) Data collection device, sensor terminal, metadata collection system, metadata collection method, and program
JP7435810B2 (en) System and method for collecting metadata and sensor terminal
US8504610B2 (en) System and method for obtaining and executing instructions from a private network
US20160142493A1 (en) Sensor data collection system
CN108305628B (en) Speech recognition method, speech recognition device, computer equipment and storage medium
US20180165431A1 (en) Method, apparatus and system for device replacement detection and device recommendation
US12074945B2 (en) Data collection system and data collection method
JPWO2017179608A1 (en) Time synchronization method, sensor accommodating terminal, and sensor network system
US8918502B2 (en) FlowSense: light-weight networking sensing with openflow
JP7494909B2 (en) Data collection system, terminal, data collection method, and program
US11979462B2 (en) Data collection system and data collection method
CN113114704B (en) Video structured data one-way transmission method and device based on equipment attribute selection
CN113016161A (en) Analysis of event-based behavior of endpoints in industrial systems
JP6471085B2 (en) Network connection device, data compression collection method and program
KR101033922B1 (en) Voice recognition intelligent closed surveillance system
US11991063B2 (en) Anomaly detection device, anomaly detection method, and program
WO2023012870A1 (en) Sensor terminal, data collection unit, data collection system, data collection method, and program
US20130185419A1 (en) OFSense: Light-Weight Networking Sensing With OpenFlow
CN109088943B (en) Blood pressure detection method and device
Almhairat et al. Network Effects on Dual Machine Learning Models Predicting Smart Home Sensor Measurements
WO2024195018A1 (en) Moving body monitoring system and method
WO2024122017A1 (en) Data collection system
US20240184857A1 (en) Device type classification based on usage patterns
CN103310787A (en) Abnormal sound rapid-detection method for building security
KR100489244B1 (en) Apparatus for monitoring an unattended relay station and method thereof

Legal Events

Date Code Title Description
AS Assignment

Owner name: NIPPON TELEGRAPH AND TELEPHONE CORPORATION, JAPAN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:TANIGUCHI, TOMOHIRO;TAMAKI, SHINYA;SUZUKI, TETSUYA;AND OTHERS;SIGNING DATES FROM 20210119 TO 20220602;REEL/FRAME:060845/0286

FEPP Fee payment procedure

Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER

STPP Information on status: patent application and granting procedure in general

Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS

STPP Information on status: patent application and granting procedure in general

Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED

STCF Information on status: patent grant

Free format text: PATENTED CASE