WO2024201562A1 - データ収集システム - Google Patents

データ収集システム Download PDF

Info

Publication number
WO2024201562A1
WO2024201562A1 PCT/JP2023/011782 JP2023011782W WO2024201562A1 WO 2024201562 A1 WO2024201562 A1 WO 2024201562A1 JP 2023011782 W JP2023011782 W JP 2023011782W WO 2024201562 A1 WO2024201562 A1 WO 2024201562A1
Authority
WO
WIPO (PCT)
Prior art keywords
metadata
terminal
layer
management server
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.)
Ceased
Application number
PCT/JP2023/011782
Other languages
English (en)
French (fr)
Japanese (ja)
Inventor
真也 玉置
章裕 今江
聖 成川
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.)
NTT Inc
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
Priority to JP2025509062A priority Critical patent/JPWO2024201562A1/ja
Priority to PCT/JP2023/011782 priority patent/WO2024201562A1/ja
Publication of WO2024201562A1 publication Critical patent/WO2024201562A1/ja
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0686—Additional information in the notification, e.g. enhancement of specific meta-data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/02—Capturing of monitoring data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/324—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the data link layer [OSI layer 2], e.g. HDLC

Definitions

  • This disclosure relates to a technology for collecting metadata such as the location, installer, time, and status of a sensor.
  • Non-Patent Document 1 reports a method that uses LLDP (Link Layer Discovery Protocol, see Non-Patent Document 3 for example).
  • Non-Patent Document 2 data related to the sensing data
  • metadata data related to the sensing data
  • a technology has been proposed that stores and transmits metadata such as the sensor location in an extension area of a frame defined by the communication protocol used to transmit the main sensing data.
  • metadata such as the sensor location
  • the extension area of a frame defined by a communication protocol it is necessary to use a common communication protocol in the system.
  • the purpose of this disclosure is to make it possible to collect sensing data and metadata even when there are terminals that connect to a communication network using different communication protocols.
  • the data information system is a system in which a network device is connected between a terminal and a management server, a terminal that stores predetermined metadata in an extension area of a layer 2 communication frame and transmits the metadata; A network device according to the present disclosure; and a management server that collects the metadata transmitted from the terminal.
  • the network device disclosed herein When the network device disclosed herein receives a first Layer 2 communication frame from a terminal to a management server, it stores the information stored in the extension area of the received first Layer 2 communication frame in an extension area of a second Layer 2 communication frame that can be transmitted from the device to the management server.
  • the method disclosed herein is a method executed by a network device connected between a terminal and a management server, comprising: When a first Layer 2 communication frame is received from a terminal to a management server, the information stored in the extension area of the received first Layer 2 communication frame is stored in an extension area of a second Layer 2 communication frame that can be transmitted from the terminal to the management server.
  • the information stored in an extension area of the first Layer 2 communication frame may include metadata of the terminal.
  • the metadata of the terminal can be collected in the management server using a communication protocol that does not require high performance.
  • the network device of the present disclosure may store an identifier of the device itself in the metadata storage area.
  • the network device of the present disclosure may also store an identifier of the device itself by adding an extension area in the second Layer 2 communication frame.
  • the network device of the present disclosure When the network device of the present disclosure receives the first Layer 2 communication frame from the terminal, it may store the information stored in the extension area of the first Layer 2 communication frame and the identifier of the terminal in an extension area of the second Layer 2 communication frame and transfer it to the management server.
  • the program of the present disclosure is a program for causing a computer to realize each function of the network device of the present disclosure, and is a program for causing a computer to execute each procedure of the method executed by the network device of the present disclosure.
  • FIG. 1 is a diagram illustrating a data collection system according to the present disclosure.
  • FIG. 2 is a diagram illustrating a terminal of a data collection system according to the present disclosure.
  • FIG. 2 is a diagram illustrating a management server of the data collection system according to the present disclosure.
  • 11 is a diagram illustrating a frame transmitted from a terminal to a management server.
  • FIG. FIG. 1 is a diagram illustrating a data collection system according to the present disclosure. 2 illustrates an example of the configuration of a network device according to the present disclosure. 2 shows an example of a layer 2 communication frame. 2 shows an example of a layer 2 communication frame.
  • FIG. 1 is a diagram illustrating a data collection system according to the present disclosure. 2 shows an example of a layer 2 communication frame.
  • FIG. 1 illustrates an example of the operation of a network device.
  • FIG. 1 is a diagram illustrating a data collection system according to the present disclosure.
  • FIG. 1 is a diagram illustrating a data collection system according to the present disclosure.
  • FIG. 1 is a diagram illustrating a data collection system according to the present disclosure.
  • 2 shows an example of a layer 2 communication frame.
  • the data collection system 301 is a data collection system that performs communication from a terminal 11 to a network device 12 by utilizing an extension area of a standardized communication protocol (such as LLDP, HTIP, IEEE802.11, etc.),
  • the terminal 11 stores the sensing data detected by the sensor device in an area of the frame defined by the communication protocol, which is different from the area for storing the metadata, and transmits the data to the network device 12.
  • the network device 12 transfers the frame to the management server 13,
  • the management server 13 is characterized in that it associates the sensing data with the metadata and stores them based on information for identifying the terminal 11 that is written in the frame.
  • the data collection network 15 is a network that connects the terminals 11 that exist within a specific range to the management server 13.
  • the data collection network 15 is, for example, a local area network (LAN), a field area network (FAN), an IoT area network, etc.
  • LAN local area network
  • FAN field area network
  • IoT area network IoT area network
  • FIG. 2 is a diagram for explaining the terminal 11.
  • the terminal 11 is, for example, an IoT sensor terminal that senses an observation target and generates sensing data.
  • the terminal 11 includes a sensor device 11a, a sensing data storage processing unit 11b, a device information storage processing unit 11c, a communication protocol operation unit 11d1 , metadata detection units ( 11e1 , 11e2 , 11e3 , ...), and a metadata storage processing unit 11f.
  • the sensor device 11a senses an object to be observed and acquires sensing data (main data).
  • the sensing data may be, for example, temperature, images, acceleration, sound, light, CO2, etc.
  • the device information storage processing unit 11c collects device information of the observed target (e.g., the device manufacturer name, model name, model number, etc.) and stores the information in a specified position of the frame (an area that can be used for unique purposes, such as an "extension area” or "optional area” specified by the protocol).
  • the sensing data storage processing unit 11b stores the sensing data from the sensor device 11a in a specified position of the frame (such as the payload portion defined by the protocol).
  • the sensing data storage processing unit 11b may process the sensing data before storing it in the frame, for example by converting it into a shortened code and storing it, or by splitting it into multiple frames and storing them (fragmentation), so that it conforms to the format/restrictions of the frame's unique extension area.
  • the sensing data storage processing unit 11b can arbitrarily set the timing for storing the sensing data in the frame.
  • the storage timing can be each time the sensing data is updated, or the sensing data can be stored not sequentially but after it has been accumulated for a certain period of time.
  • the sensing data storage processing unit 11b can store a record (log) of the sensing data or the results of specific calculations/statistical processing in the frame.
  • the type of sensing data stored in the frame and the storage timing may be fixed or variable.
  • the type of sensing data and the storage timing may be dynamically changed by the terminal 11 itself or by an instruction from the management server 13.
  • the frame transmission period may also be fixed or variable.
  • the frame transmission period may be dynamically changed at the discretion of the terminal 11 itself or in response to an instruction from the management server 13.
  • the metadata detection unit 11e acquires information (metadata) other than device information.
  • Information other than device information is, for example, location information of the detection target, time information, person, object, or event information, and other information.
  • the present invention does not limit the information other than device information to these.
  • the metadata detection unit 11e has a location information detection unit 11e 1 , a time detection unit 11e 2 , a person, object, or event detection unit 11e 3 , and other detection units.
  • the location information detection unit 11e 1 is, for example, a GPS, an acceleration sensor, a gyro sensor, or an RSSI receiver for Wi-Fi signals, BLE (Bluetooth Low Energy) beacon signals, etc.
  • the location metadata detected by the location information detection unit 11e 1 is information about a location acquired from a GPS signal, a BLE beacon signal, radio wave information of wireless communication, radio wave information of non-communication (television, radio, radio clock, other noise, etc.), power information, visible light information, sound wave information, vibration information, acceleration information, or other location metadata source.
  • the time detection unit 11e2 is, for example, an information receiver from GPS or NTP (Network Time Protocol).
  • the time metadata detected by the time detection unit 11e2 is information about time acquired from a GPS signal, information from the NTP, or other time metadata sources.
  • the person, object, and event detection unit 11e 3 is a receiver that receives, for example, information from a BLE beacon (carried by a person), a smartphone carried by a person, or information from image analysis results.
  • the person, object, or event metadata detected by the person, object, and event detection unit 11e 3 is information about a person, object, or event obtained from a BLE beacon carried by a person, information from a smartphone carried by a person, information from image analysis results, or other current event metadata sources.
  • Other metadata detected by the detection unit includes information regarding the network configuration of the data collection network 15.
  • the metadata detection unit 11e may detect all of the multiple detection targets, or may detect any one of them.
  • the metadata storage processing unit 11f stores the data detected by the metadata detection unit 11e as metadata in an extension area or option area in the frame set by the communication protocol.
  • the metadata storage processing unit 11f can store metadata in the control system frame of an IEEE 804.11 wireless LAN.
  • various metadata are stored in the "Vendor Specific” area, which is an extension area of a Probe Request frame.
  • various metadata are stored in the "Vendor Specific” area, which is an extension area of a Probe Response frame.
  • the metadata storage processing unit 11f may process the metadata before storing it in the frame, for example by converting it into an abbreviated code and storing it, or by splitting it and storing it in multiple frames (fragmentation), so that it conforms to the format/restrictions of the frame's unique extension area.
  • the metadata storage processing unit 11f can arbitrarily set the timing for storing metadata in a frame.
  • the storage timing can be each time the metadata is updated, or the metadata can be stored not sequentially but after it has been accumulated for a certain period of time.
  • the metadata storage processing unit 11f can store a record (log) of the metadata or the results of specific calculations/statistical processing in the frame.
  • the type of metadata stored in the frame and the storage timing may be fixed or variable.
  • the type of metadata and the storage timing may be dynamically changed at the discretion of the terminal 11 itself or in response to an instruction from the management server 13.
  • the communication protocol operation unit 11d 1 transmits a frame in which sensing data and device information are stored in a predetermined area and metadata is stored in an extension area or an option area to the network device 12 using a lightweight and standardized communication protocol such as LLDP or HTIP (Home network Topology Identifying Protocol).
  • the communication protocol of the frame in which the sensing data is stored and the communication protocol of the frame in which the device information is stored may be the same or different.
  • the metadata storage processing unit 11f may store the metadata in a frame of one of the communication protocols (a frame in which the sensing data is stored or a frame in which the device information is stored) or in a frame of both communication protocols (a frame in which the sensing data is stored and a frame in which the device information is stored).
  • the terminal 11 also has a function of operating according to instructions from the management server 13, etc. Specifically, the terminal 11 has an instruction interpretation unit 11g, and when the terminal itself changes the BLE beacon signal or metadata information (information to be transmitted, radio wave intensity, transmission frequency, etc.) according to instructions from the management server 13, the terminal transmits the information to the outside.
  • the terminal 11 operates a communication protocol operation unit 11d1 .
  • the terminal 11 has a communication protocol operation unit 11d2 in addition to the communication protocol operation unit 11d1 , and operates the communication protocol operation unit 11d2 .
  • the terminal 11 itself is a beacon signal source for other terminals to grasp metadata.
  • the terminal 11 may be a beacon signal source for identifying location metadata, or a beacon terminal carried by a worker to identify nearby people.
  • the network device 12 is, for example, a network switch, a wireless access point, a wireless repeater, etc.
  • the network device 12 sends the frames uploaded from the lower data collection network 15 to the management server 13 as is.
  • the network device 12 may have a metadata processing unit (metadata detection unit 11e and metadata storage processing unit 11f) that the terminal 11 has. Even if the network device 12 does not have the sensor device 11a, it can add metadata such as its own unique information such as its own MAC address and a connection port to a frame sent from the terminal 11 and transfer the frame to the management server 13. If the network device 12 has a metadata processing section, it becomes possible to grasp the logical connection from the management server 13 to the terminal 11, and a more accurate logical/physical network management map can be created. In other words, even if the network device 12 is a network switch (switching hub) or a wireless repeater that does not have functions at layer 3 or above, this technology operates at layer 2, making it possible to manage and understand the connections between network devices, including the network device 12.
  • FIG. 3 is a diagram explaining the management server 13.
  • the management server 13 has a communication protocol operation unit 13a, an information processing unit 13b, and an information storage unit 13c.
  • the management server 13 extracts information from frames passed from the network device 12, stores it, and provides it for analysis.
  • the management server 13 is characterized by having a function to store combinations of two or more pieces of collected information in the information storage unit 13c.
  • the communication protocol operation unit 13a receives frames in which sensing data and metadata are stored from the terminal 11 and the network device 12.
  • the information processing unit 12b extracts the following sensing data, device information, and metadata from the received frames, and organizes them in the information storage unit 13c based on information that identifies the individual terminal 11 (e.g., MAC address).
  • the management server 13 refers to metadata related to a location and stores the main data acquired at the same location or within a certain area in the format of [location metadata, main data].
  • location metadata Like GPS information, there are cases where the information has become direct location metadata at the time of sensing by the terminal 11. On the other hand, there are also cases where, like signals, visible light, or sound information from BLE beacons, it is not determined whether the information is location information at the time of sensing by the terminal 11 and transmitting it as metadata, and the management server 13 recognizes/understands the metadata as location metadata.
  • FIG. 4 is a diagram explaining a frame 41 transmitted from the terminal 11 to the management server 13.
  • the network device 12 is not shown in FIG. 4.
  • the frame 41 is a layer 2 communication frame such as an Ethernet (registered trademark) frame or a Wi-Fi communication frame.
  • the frame 41 is composed of a logical identifier 41a of the communication device such as a MAC address, a source and destination identifier 41b such as an IP address, an area 41c in which sensing data such as temperature and images are stored, and an extension area 41d in which metadata is stored.
  • the identifier 41b and area 41c form a layer 3 communication packet.
  • the management server 13 for example, combines the MAC address of the logical identifier 41a with the location metadata of the extension area 41d to form [MAC address, location metadata], and combines the MAC address of the logical identifier 41a with the installer metadata of the extension area 41d to form [MAC address, installer metadata], and organizes them in the information storage unit 13c.
  • the data collection system 301 can acquire network configuration information, device information, sensing data, and metadata of terminals and devices using a communication protocol that does not require high performance.
  • (Embodiment 2) 5 shows an example of a system configuration of this embodiment.
  • the system of this embodiment includes an access point (hereinafter sometimes abbreviated as AP) 12A and a gateway (hereinafter sometimes abbreviated as GW) 12G that function as a network device 12. Therefore, in this embodiment, the layer 2 communication frame transmitted from the terminal 11E can be of two types of communication protocols, 802.11 wireless (Wi-Fi) communication and wired Ethernet communication.
  • Wi-Fi 802.11 wireless
  • the terminal 11W is connected to the access point 12A via Wi-Fi. For this reason, the terminal 11W transmits metadata using the extension field of the Probe Request.
  • the terminal 11E is connected to the gateway 12G via wired Ethernet (registered trademark) communication. Therefore, the terminal 11E transmits metadata using the extension field of the LLDP. As a result, the terminals 11W and 11E transmit metadata using extension areas of Layer 2 communication frames defined by different communication protocols.
  • the access point 12A or the gateway 12G further stores and transmits information (logical identifier (MAC address) of the terminal, metadata, etc.) collected from the terminal 11 via a low-layer protocol as metadata in an extended area of the layer 2 communication protocol between the access point 12A or the gateway 12G and the management server 13, thereby enabling the integration of two types of low-layer metadata collection technologies (Wi-Fi version/LLDP version).
  • MAC address logical identifier
  • the management server 13 to collect metadata together with the history of the network devices 12 that the metadata issued from the terminal 11 passed through before reaching the management server 13, even if the access points 12A or the gateways 12G are in a multi-stage configuration.
  • FIG. 6 shows an example of the configuration of the network device 12 of this embodiment.
  • the network device 12 includes a data processing unit 21, a LAN side communication protocol operation unit 22L, and a WAN side communication protocol operation unit 22W.
  • the LAN side communication protocol operation unit 22L is connected to the terminal 11, and the WAN side communication protocol operation unit 22W is connected to the management server 13.
  • the LAN side communication protocol operation unit 22L is connected to the terminal 11W.
  • the network device 12 is a gateway 12G, the LAN side communication protocol operation unit 22L is connected to the terminal 11E.
  • the network device 12 of the present disclosure When the network device 12 of the present disclosure receives a first Layer 2 communication frame from the terminal 11 to the management server 13, it stores the information stored in the extension area of the received first Layer 2 communication frame in an extension area of a second Layer 2 communication frame that can be transmitted from the device to the management server 13.
  • the access point 12A or the gateway 12G further stores the information (terminal logical identifier (MAC address), metadata, etc.) collected from the terminal 11 using the layer 2 communication frame in an extension area of the layer 2 communication protocol between the access point 12A or the gateway 12G and the management server 13 as metadata and sends it out.
  • information terminal logical identifier (MAC address), metadata, etc.
  • FIGS. 7 and 8 show examples of layer 2 communication frames.
  • the access point 12A receives frame 41W shown in FIG. 7(a) from the terminal 11W, it sends out frame 41A shown in FIG. 7(b).
  • the gateway 12G receives frame 41E shown in FIG. 8(a) from the terminal 11E, it sends out frame 41G shown in FIG. 8(b).
  • a gateway 12G is connected between the access point 12A and the management server 13, as shown in FIG. 9.
  • the gateway 12G receives frame 41A shown in FIG. 10(a) from the access point 12A, it sends out frame 41GA shown in FIG. 10(b).
  • the information on the logical identifier 41a of the access point 12A stored in the header information of frame 41A is processed by the gateway 12G, and is newly added as one piece of metadata in frame 41GA sent from the gateway 12G to the upper network.
  • the same is true when a gateway 12G is connected between the access point 12A and the management server 13.
  • the information collected by each network device 12 on the way to the management server 13 using the layer 2 communication frame is further stored as metadata in an extended area of the layer 2 communication protocol and sent out.
  • FIG. 11 shows an example of the operation of a network device.
  • S11 The LAN side communication protocol operation section 21L receives metadata from the LAN side terminal 11W via the layer 2 communication protocol extension area. This confirmation is performed at regular time intervals (S12).
  • S13 The metadata received in step S11 is temporarily stored in memory, and an instruction from the data processing unit 21 is awaited. When the metadata temporarily stored in memory is detected in step S13, the metadata (along with the terminal logical identifier) is passed to the WAN side communication protocol operation unit 22W.
  • S14 The WAN-side communication protocol operation unit 22W stores the metadata temporarily stored in the memory in an extension area of the WAN-side communication protocol, and sends it out.
  • the sending in step S14 may be performed whenever new metadata is received in step S11, or may be performed after a certain amount of metadata has accumulated in memory in step S12, or may be sent according to instructions from the management server 13, etc.
  • Each access point 12A stores its own logical identifier (such as a MAC address) in the logical identifier 41a of the frame 41A shown in FIG. 7(b).
  • logical identifier such as a MAC address
  • collection may be performed using the extended area of one of the layer 2 communication protocols, or both may be used. When both are used, there may be cases where redundancy is provided so that metadata can be delivered even if a problem occurs with one of the communications.
  • (Embodiment 3) 13 shows an example of a system configuration of this embodiment.
  • the Probe Request frame may be broadcast and therefore may reach the management server 13 via multiple access points 12A.
  • These properties can also be utilized in use cases where low latency is important, such as when some kind of feedback control is desired.
  • each of the multiple access points 12A stores its own logical identifier as metadata in an extension area of the layer 2 communication protocol and transmits it. At this time, each access point 12A stores the time information when the logical identifier was stored in the metadata storage area.
  • the management server 13 will receive the same metadata 41A multiple times via multiple routes, but will adopt the metadata 41A that arrived earlier and discard the metadata 41A that arrived later, so that the metadata that arrived via the route with the least delay can always be used.
  • the time information stored in the metadata 41 by each access point 12A can be compared, and only the metadata 41A with the shortest delay time in the wireless section can be used.
  • the system of this embodiment collects metadata from multiple routes and uses the data (metadata) that arrives at the management server 13 the fastest or the data (metadata) that has the smallest delay time in the wireless section for calculation processing, thereby improving low latency.
  • the history information indicating that metadata has reached the management server 13 via multiple access points 12A can be used to estimate the location of the terminal 11W, as it provides a clue as to which access point 12A the terminal 11W is located in proximity to.
  • FIG. 14 shows an example of the system configuration of this embodiment.
  • an example of the embodiment in which connections are made via more multiple access points 12A and gateways 12G is shown.
  • the upper limit of the extension area in LLDP is 1500 bytes
  • the upper limit of the extension area in Probe Request is 2304 bytes.
  • the network device 12 of this embodiment divides the metadata to be stored in the extension area 41d and sends it out.
  • Figure 15 shows an example of a frame configuration for LLDP.
  • Each network device 12 that the frame passes through on the way to the management server 13 adds an extension field including type, length, and value.
  • network device 12#1 that receives a Layer 2 communication frame from terminal 11 generates extension fields TVL1 and TVL2, stores the logical identifier and metadata of terminal 11 in extension field TVL1, and stores its own logical identifier in extension field TVL2.
  • the next network device 12#2 generates extension field TVL3 and stores its own logical identifier there.
  • each network device 12 adds an extension area for storing the identifier of its own device to the received layer 2 communication frame. This makes it possible to store the identifier of each network device 12 in the extension area of the layer 2 communication frame even if the access points 12A and gateways 12G are connected in multiple stages.
  • the system of the present disclosure includes: (1) A configuration in which an access point 12A and a gateway 12G are mixed (FIG. 5); (2) In a pattern in which only Wi-Fi is used, a Probe Request frame can reach multiple access points 12A from one terminal 11W ( FIG. 12 ). (3) A multi-stage configuration in which access points 12A and gateways 12G are connected in a daisy chain (FIG. 9), Even if the file is marked as such, metadata can still be collected.
  • Access point 12A and gateway 12G may transfer collected metadata by HTTP at any time, or may temporarily store the metadata in a memory area as text data and then send the data to management server 13 in a lump. Any method may be used to send the metadata to management server 13.
  • Metadata can be delivered to the management server 13 with low latency and before an IP connection is established.
  • the probability of information loss due to packet loss, frame collisions, etc. can be reduced by utilizing the Layer 2 communication protocol extension areas of both communication paths to send metadata to the upstream network. Also, from the perspective of low latency, the probability of quality degradation in low latency can be reduced by adopting the data that reaches the management server 13 the fastest via multiple paths.
  • the network device of the present disclosure can also be realized by a computer and a program, and the program can be recorded on a recording medium or provided via a network.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)
PCT/JP2023/011782 2023-03-24 2023-03-24 データ収集システム Ceased WO2024201562A1 (ja)

Priority Applications (2)

Application Number Priority Date Filing Date Title
JP2025509062A JPWO2024201562A1 (https=) 2023-03-24 2023-03-24
PCT/JP2023/011782 WO2024201562A1 (ja) 2023-03-24 2023-03-24 データ収集システム

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2023/011782 WO2024201562A1 (ja) 2023-03-24 2023-03-24 データ収集システム

Publications (1)

Publication Number Publication Date
WO2024201562A1 true WO2024201562A1 (ja) 2024-10-03

Family

ID=92904003

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2023/011782 Ceased WO2024201562A1 (ja) 2023-03-24 2023-03-24 データ収集システム

Country Status (2)

Country Link
JP (1) JPWO2024201562A1 (https=)
WO (1) WO2024201562A1 (https=)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022070295A1 (ja) * 2020-09-30 2022-04-07 日本電信電話株式会社 メタデータを収集するシステム及び方法並びにセンサー端末
WO2022149250A1 (ja) * 2021-01-08 2022-07-14 日本電信電話株式会社 データ収集装置、センサ端末、メタデータ収集システム、メタデータ収集方法、及びプログラム

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022070295A1 (ja) * 2020-09-30 2022-04-07 日本電信電話株式会社 メタデータを収集するシステム及び方法並びにセンサー端末
WO2022149250A1 (ja) * 2021-01-08 2022-07-14 日本電信電話株式会社 データ収集装置、センサ端末、メタデータ収集システム、メタデータ収集方法、及びプログラム

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
KOMORI, TATSUYA ET AL.: "Experimental Implementation and its Functional Evaluation of Next Generation Body Area Network", SMARTBAN, vol. 116, no. 81, 2 June 2016 (2016-06-02), pages 23 - 28, XP009555182 *

Also Published As

Publication number Publication date
JPWO2024201562A1 (https=) 2024-10-03

Similar Documents

Publication Publication Date Title
CN102668657B (zh) 无线网络中使用标识被跟踪设备的响应消息的位置跟踪
US10419342B2 (en) Gateways for sensor data packets in cellular networks
KR101572215B1 (ko) 네트워크 시스템
US20090141692A1 (en) Optimized ad hoc networking
US20130258898A1 (en) Computer system, controller, controller manager and communication route analysis method
WO2006051638A1 (ja) 通信システム、無線ｌａｎ基地局制御装置および無線ｌａｎ基地局装置
JP7435810B2 (ja) メタデータを収集するシステム及び方法並びにセンサー端末
WO2011119019A1 (en) Method of communicating signals in 6lowpan network to ipv6 network
Gundogan et al. ICNLoWPAN–named-data networking for low power IoT networks
JP6631232B2 (ja) ルーティング情報を判定するためのシステムおよび方法
KR20090065260A (ko) Ｉｐ 기반 시스템과 ｗｓｎ 노드와의 연동을 위한 고유식별자를 이용한 주소 변환 시스템 및 방법
WO2024201562A1 (ja) データ収集システム
JP6904846B2 (ja) 通信装置、通信装置の制御方法、および、プログラム
Le et al. An approach to design a multi-protocol gateway device for Internet of Things system
JP2003258859A (ja) 通信システム、通信方法、転送装置及びネットワーク管理装置
JP6428702B2 (ja) 管理装置および管理システム
WO2024084641A1 (ja) 位置検出サーバ及び位置変動把握方法
JP7388534B2 (ja) データ収集システム及びデータ収集方法
WO2024122024A1 (ja) 管理ノード、通信端末、及びデータ収集方法
KR20130111537A (ko) 네트워크 시스템
WO2024122017A1 (ja) データ収集システム
WO2024122013A1 (ja) データ収集システム
JP2002111668A (ja) ネットワーク構成表示装置
WO2024232070A1 (ja) データ収集システム
WO2024122011A1 (ja) データ収集システム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23930204

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2025509062

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2025509062

Country of ref document: JP

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 23930204

Country of ref document: EP

Kind code of ref document: A1