WO2019166092A1 - Procédés fournissant des rapports de mesure comprenant une identification d'un événement temporel de base et capteurs et nœuds de réseau associés - Google Patents

Procédés fournissant des rapports de mesure comprenant une identification d'un événement temporel de base et capteurs et nœuds de réseau associés Download PDF

Info

Publication number
WO2019166092A1
WO2019166092A1 PCT/EP2018/055075 EP2018055075W WO2019166092A1 WO 2019166092 A1 WO2019166092 A1 WO 2019166092A1 EP 2018055075 W EP2018055075 W EP 2018055075W WO 2019166092 A1 WO2019166092 A1 WO 2019166092A1
Authority
WO
WIPO (PCT)
Prior art keywords
time event
base time
time
event
measurement value
Prior art date
Application number
PCT/EP2018/055075
Other languages
English (en)
Inventor
Gonzalo Camarillo Gonzalez
Ari KERÄNEN
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Priority to PCT/EP2018/055075 priority Critical patent/WO2019166092A1/fr
Publication of WO2019166092A1 publication Critical patent/WO2019166092A1/fr

Links

Classifications

    • GPHYSICS
    • G01MEASURING; TESTING
    • G01DMEASURING NOT SPECIALLY ADAPTED FOR A SPECIFIC VARIABLE; ARRANGEMENTS FOR MEASURING TWO OR MORE VARIABLES NOT COVERED IN A SINGLE OTHER SUBCLASS; TARIFF METERING APPARATUS; MEASURING OR TESTING NOT OTHERWISE PROVIDED FOR
    • G01D21/00Measuring or testing not otherwise provided for
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
    • G06F1/04Generating or distributing clock signals or signals derived directly therefrom
    • G06F1/14Time supervision arrangements, e.g. real time clock

Definitions

  • the present disclosure generally relates to sensors, and more particularly, to wireless sensors and related methods and network nodes.
  • An Internet of Things (IoT) sensor may be used to take measurements and wirelessly transmit the measurements over a network to a network node (e.g., a server). Such a sensor may thus take a measurement, and the sensor may need to report the measurement together with a time at which the measurement was made. For example, a temperature sensor may report a temperature value together with the time at which the temperature value was taken or measured (e.g., 27 degrees Celsius at 13:45 on September 22, 2017).
  • sensors may be subject to different types of constrains. Some sensors may be subject to one or more constraints of limited power, processing capacity, memory, etc. In many cases, a sensor may be constrained in that it does not have access to an accurate global clock. Such sensors without access to an accurate global clock (referred to as constrained sensors) may thus be unable to report absolute times for reported measurements.
  • constrained sensors Such sensors without access to an accurate global clock (referred to as constrained sensors) may thus be unable to report absolute times for reported measurements.
  • a server receiving reports from such a sensor may assume that the measurement was performed at the time the report was received.
  • the server may also estimate or measure the RTT (Round-trip Time) to the sensor and adjust the time accordingly.
  • sensors may group several measurements made during a period in a single report, which is sent at the end of the period.
  • network conditions between sensors and servers may be unstable and/or difficult to predict. For example, if DTN (Delay-tolerant Network) protocols are used by a sensor to send reports to a server, the RTTs can be multiple hours, or even longer. In such situations, existing strategies may be insufficient to obtain a good estimate of the time when the measurement was made.
  • DTN Delay-tolerant Network
  • a method of operating a sensor device may include detecting a base time event and providing a measurement value.
  • a measurement report may then be transmitted over a network to a network node.
  • the measurement report may include an identification of the base time event and the measurement value.
  • a method of operating a network node may include receiving a measurement report from a sensor device over a network.
  • the measurement report may include an identification of a base time event and a measurement value.
  • a time for the measurement value may be determined using the identification of the base time event.
  • a sensor that does not have practical access to an accurate global clock may be able to provide information allowing a remote server to accurately determine a time of a measurement received from the sensor.
  • Figure 1 is a block diagram illustrating measurement reporting according to some embodiments of inventive concepts
  • Figure 2 is a block diagram illustrating a wireless sensor according to some embodiments of inventive concepts
  • Figure 3 is a block diagram illustrating a network node according to some embodiments of inventive concepts
  • Figure 4 is a flow chart illustrating sensor device operations according to some embodiments of inventive concepts.
  • FIGS. 5 and 6 are flow charts illustrating network node operations according to some embodiments of inventive concepts.
  • FIG. 2 is a block diagram illustrating a sensor device 101 (which may be a wired or wireless sensor device such as a wired/wireless IOT sensor device, a 3GPP user equipment sensor device, or a User Equipment UE sensor device, etc.) according to some embodiments disclosed herein.
  • sensor device 101 may include processor 203 coupled with communication interface 201 (also referred to as a network interface), memory 205, first sensor 207, and second sensor 209.
  • Communication interface 201 may include one or more of an Ethernet interface, a WiFi interface, a cellular radio access network (RAN) interface (also referred to as a RAN transceiver), and/or other wired/wireless network communication interfaces.
  • RAN radio access network
  • Sensor device 101 can thus provide wireless communication over one or more wired/wireless links with a remote network node 103 (e.g., a server or a cloud based storage system).
  • a remote network node 103 e.g., a server or a cloud based storage system.
  • Processor 203 may include one or more data processing circuits, such as a general purpose and/or special purpose processor (e.g., microprocessor and/or digital signal processor).
  • Processor 203 may be configured to execute computer program instructions from functional modules in memory 205 (also referred to as a memory circuit or memory circuitry), described below as a computer readable medium, to perform some or all of the operations and methods that are described herein for one or more of the embodiments.
  • processor 203 may be defined to include memory so that separate memory 205 may not be required.
  • Sensor device 101 including processor 203, communication interface 201 memory 205, first sensor 207, and/or second sensor 209) may thus perform operations, for example, discussed below with respect to the figures.
  • Sensor 207 may thus be used to generate measurement values (e.g., temperature, pressure, etc.) that are transmitted by processor 203 through communication interface 201 to a remote network node 103. While sensor 207 is shown within sensor device 101 , sensor 207 may be provided outside sensor device 101 with coupling to processor 203. Moreover, while measurements are discussed by way of example, any data values may be transmitted by processor 203 through communication interface 201 to network node 103 according to some embodiments of inventive concepts. According to some embodiments, a second sensor 209 may be used to detect a base time event, or if detection of a base time event is not required, sensor 209 may be omitted.
  • measurement values e.g., temperature, pressure, etc.
  • FIG. 3 is a block diagram illustrating a network node 103 (e.g., a server) according to some embodiments disclosed herein.
  • network node 103 may include processor 303 coupled with communication interface 301 (also referred to as a network interface), and memory 305.
  • Communication interface 301 may include one or more of a wired network interface (e.g., an Ethernet interface), a WiFi interface, a cellular radio access network (RAN) interface (also referred to as a RAN transceiver), and/or other wired/wireless network communication interfaces.
  • Network node 103 can thus provide wired/wireless communication over one or more wired/wireless links with sensor device 101 (and possibly a second wireless sensor 102).
  • RAN radio access network
  • Processor 303 may include one or more data processing circuits, such as a general purpose and/or special purpose processor (e.g., microprocessor and/or digital signal processor). Processor 303 may be configured to execute computer program instructions from functional modules in memory 305 (also referred to as a memory circuit or memory circuitry), described below as a computer readable medium, to perform some or all of the operations and methods that are described herein for one or more of the embodiments. Moreover, processor 303 may be defined to include memory so that separate memory 305 may not be required. Network node 103, processor 303, and communication interface 301 may thus perform operations, for example, discussed below with respect to the figures.
  • processor 303 may include one or more data processing circuits, such as a general purpose and/or special purpose processor (e.g., microprocessor and/or digital signal processor). Processor 303 may be configured to execute computer program instructions from functional modules in memory 305 (also referred to as a memory circuit or memory circuitry), described below as a computer readable medium, to perform some
  • a sensor device 101 that does not have access to an accurate global clock may, nevertheless, have access to a clock that can measure relative times over short periods.
  • a clock e.g., included in processor 203
  • Such a clock may thus provide a good-enough accuracy when measuring short time periods.
  • such a clock may be used to report that a second measurement was made 5 seconds after the first measurement.
  • a third measurement was made (for instance) 1 month afterwards, the accuracy of the sensor’s clock may not be precise enough.
  • a constrained sensor device may provide a time offset that is relative to a base time event that is mutually known by both the sensor device 101 and the network node 103 (e.g., server) receiving the report.
  • a base time event that is mutually known by both the sensor device 101 and the network node 103 (e.g., server) receiving the report.
  • Many types of events can be used for this purpose. Examples of such events may include network events such as broadcast traffic (e.g., routing updates), sounds, radiation levels, etc. Accordingly, any event that can be known by both sensor device 101 and network node 103 can be used for this purpose.
  • network node 103 may obtain information regarding the base time event (including a time) through another sensor device 102.
  • sensor device 102 may include a sound sensor and sensor device 102 may have access to a global clock so that sensor device 103 can report an accurate time at which a sound of a certain frequency was recorded.
  • Sensor device 101 may include temperature and sound sensors 207 and 209 but may not have access to a global clock. In this situation, sensor device 101 may report a temperature that was measured (using sensor 207) 4 seconds after a particular sound was recorded/detected as a base time event using sensor 209.
  • the synchronizing sound could be produced by and/or responsive to network node 103 through an actuator with access to a speaker.
  • inventive concepts may be applicable to a sensor device 101 without access to a clock for measurements at all.
  • a sensor device 101 may be unable to achieving time synchronization (not even for a short period of time). Instead, such a sensor device 101 may only provide the network node 103 with an external reference (e.g.,
  • Such a sensor device 101 could take a measurement at the (precise) time the external event (base time event) is detected and report the measurement value to the network node 103.
  • a sensor device 101 including temperature and sound sensors 207 and 209 could report a temperature value that was measured at the same time a particular sound (base time event) was recorded/detected.
  • sensor device 101 may not have access to a global clock and/or may be unable to obtain network wide synchronization, but sensor device 101 may be able to provide sufficient information (e.g., an identification of the base time event and/or a time offset relative to the base time event) to enable network node 103 to determine the time a measurement was made.
  • sufficient information e.g., an identification of the base time event and/or a time offset relative to the base time event
  • Sensor device 101 may not have access to a global clock but may be able to take a measurement with respect to a given main property using sensor 207.
  • Sensor device 101 may measure/detect an additional (different) property/event (a base time event) using sensor 209, and sensor device 101 may include the relative difference in time between the two measurements (also referred to as a time offset) in its report.
  • Network node 103 may know the global time at which the measurement/detection of the additional property (the base time event) must have been performed because network node 103 can independently measure/detect that second
  • the server can determine a time (e.g., a global absolute time) at which the main property was measured by sensor device 101.
  • Sensor device 101 may use the SenML format of Reference [1 ] (identified below) to generate reports, given that the format is extended to support embodiments of inventive concepts discussed herein. Such an extension may allow a SenML report to describe an event to be used as the base time for the measurements in the report.
  • SenML Pack An example of such SenML Pack is shown below. The example includes three measurement values (v) of current levels at different times (t).
  • the“base time event” (“bte”, a new extension to SenML proposed for some embodiments of inventive concepts) is a reception of a Routing Advertisement with a fingerprint “42fa”. All times, denoted by the“t” field, in the SenML records are relative times with respect to the time of this event (also referred to as time offsets).
  • The“bte” option value may have two parts: a prefix denoting the type of the event (e.g., “RA” for router advertisement) and a fingerprint value that can be used to tell two similar kinds of events apart when needed.
  • An alternative network event may be a routing protocol update (e.g., Routing Protocol for Low-Power and Lossy Networks RPL or Thread routing message), an application layer messages (e.g., a Constrained Application Protocl CoAP or Hypertext Transfer Protocol HTTP message), or even a Medium Access Control MAC layer messages (e.g., a Wi-Fi Service Set Identifier SSID broadcast message) in cases where receiving network node 103 is connected to the same LAN or can otherwise detect the traffic.
  • a routing protocol update e.g., Routing Protocol for Low-Power and Lossy Networks RPL or Thread routing message
  • an application layer messages e.g., a Constrained Application Protocl CoAP or Hypertext Transfer Protocol HTTP message
  • a Medium Access Control MAC layer messages e.g., a Wi-Fi Service Set Identifier SSID broadcast message
  • a fingerprint may be created by taking a hash (e.g., SHA-256) of the IP packet above and including the IP headers and trimming the hash to appropriate length that (with sufficient probability) can distinguish between two different events (e.g., 3-5 bytes).
  • the base time event can thus be a network communication, and a fingerprint of the network communication can be generated based on a hash of the network communication.
  • a fingerprint of the network communication may be generated based on a hash of all bytes of a full IP packet making up the network communication.
  • Acoustic Fingerprint methods of Reference [2] may be used to generate an identification of the base time event. If a fingerprint generated using these methods is excessively large (e.g., tens of bytes), a hash of the fingerprint can be used to generate a fingerprint of the fingerprint since the fingerprint is used only to detect/identify the base time event, and the fingerprint may not need to include the full information of the acoustic fingerprint.
  • sensor 207 of sensor device 101 may be a moisture sensor in a smart home, and processor 203 of sensor device 101 may wake up once a minute to measure moisture levels in a basement using moisture sensor 207. After waking up, processor 203 may wait for a Router Advertisement RA (e.g., an IPv6 configuration message) that is used to obtain an IP address for IP communication, with the Router
  • a Router Advertisement RA e.g., an IPv6 configuration message
  • Advertisement being received at processor 203 through communication interface 201.
  • moisture sensor 207 measures the current moisture level and provides a value of the moisture level to processor 203.
  • Processor 203 generates a fingerprint of the Router
  • Advertisement RA and processor 203 sends the fingerprint of the RA, the value of the moisture level, and a time offset (for a time of the moisture level measurement relative to a time of reception of the RA) to network node 103 (e.g., an Application Server AS in the same network).
  • Network node 103 e.g., an AS
  • Network node 103 may generate a global time stamp for the measurement value based on the RA fingerprint and the time offset.
  • second sensor 209 may be omitted.
  • sensor 207 may be an acoustic sensor that senses vibration of a machine for predictive maintenance purposes.
  • the machine When running normally, the machine may emit a first periodic sound every 12.3 seconds (called Sl) and a second periodic sound every 1.3 seconds (called S2).
  • Sd When the machine is misbehaving, it may also emit a third sound (called Sd).
  • processor 203 detects a different sound than expected based on information received from sensor 207, processor 203 records a time difference/offset with respect to the first of the other two known sounds (e.g., Sl , with time difference/offset Tl).
  • Processor 203 then records information about Sd (e.g., an indication that Sd was detected, and/or a fingerprint of Sd for better analysis), time difference/offset Tl, and a fingerprint- ID of Sl .
  • Processor 203 may then transmit this information through communication interface 201 to network node 103 (e.g., an application server) that is also able to know the times of Sl and S2 (e.g., because Sl and S2 are periodic and can be determined based on a state of the system) and hence network node 103 can correlate a time of Sd to a global wall clock time and perform analysis accordingly.
  • network node 103 e.g., an application server
  • a smart city could use a traffic light as a "known reference point".
  • sensor device 101 may include sensors 207 and 209 that respectively measure/detect properties/events A and B.
  • property A may have a value“a” at“x” seconds after property B had a value of“b”.
  • Processor 203 may thus provide a measurement value (e.g., value“a”) based on information received from sensor 207, processor 203 may detect a base time event (e.g., property B having the value“b”) based on information received from sensor 209, and processor 203 may determine a time offset for a time of the measurement value relative to a time of the base time event.
  • Processor 203 may transmit a measurement report including the measurement value, an identification of the base time event, and the time offset through communication interface 201.
  • processor 303 may receive the measurement report through communication interface 301. Accordingly, processor 303 of network node 103 may determine/know at what (absolute) time property B had a value of“b” because processor 303 received that information from second sensor 102 (through communication interface 301). With this information, processor 303 of network node 103 may derive a (absolute/global) time when property A had a value of“a”.
  • network node 103 could be virtualized and run in“the cloud”.
  • the signaling of out-of-band events may be used to provide a reference time for a measurement made by a sensor device incapable of network-wide synchronization.
  • network-wide time synchronization may be maintained in smart grid devices.
  • a network node 103 server may determine an accurate time of a measurement received from a remote sensor device that is incapable of achieving network-wide time synchronization.
  • such devices may provide a time reference/offset for a measurement in relation to a single one-time event.
  • both devices may be connected to the (same) grid.
  • network node 103 and the constrained sensor device 101 do not need to be connected to the same media. Instead, network node 103 can get information about a given event indirectly from another sensor 102 (e.g., a sound sensor), as discussed above.
  • Reference [3] uses a periodic signal as the reference (because it aims to achieve time synchronization across the network). According to some embodiments of inventive concepts, any one-time event may be used as a reference. As a result, some embodiments of inventive concepts may provide description of different types of one-time events.
  • modules may be stored in memory 205 of Figure 2, and these modules may provide instructions so that when the instructions of a module are executed by processor 203, processor 203 performs respective operations of the flow chart of Figure 4.
  • processor 203 may detect a base time event.
  • processor 203 may provide a measurement value based on information/signals received from sensor 207.
  • processor 203 may determine a time offset for the measurement value relative to the base time event.
  • the time offset for example, may represent a difference in time between the base time event and a time of the measurement value.
  • processor 203 may transmit a measurement report through communication interface 201 over a network to a network node 103.
  • the measurement report may include an identification of the base time event, the measurement value, and the time offset.
  • detecting the base time event may include detecting a sound, for example, using sensor 209. If the base time event is a sound, the identification of the base time event may be based on an acoustic fingerprint of the sound. Moreover, the
  • identification of the base time event may be further based on a hash of the acoustic fingerprint of the sound.
  • detecting the base time event may include detecting a network communication received at processor 203 through communication interface 201.
  • the network communication may be at least one of a router advertisement, a routing update, a configuration message, a routing protocol update, an application layer message, and/or a medium access control MAC message, such that the network communication is received by both sensor device 101 and network node 103.
  • the identification of the base time event may be based on a fingerprint of the network
  • the fingerprint of the network communication may be based on a hash of the network communication (e.g., based on a hash of all bytes that make up the network
  • the measurement value may include at least one of a measured value of distance, mass, time, electrical current, temperature, luminous intensity, concentration, frequency, angle, force, pressure, energy, power, electrical charge, electrical voltage, electrical capacitance, electrical resistance, electrical conductance, magnetic flux, magnetic flux density, electrical inductance, luminous flux, luminous emittance, radioactivity, ionizing radiation dose, catalytic activity, area, volume, velocity, acceleration, flow rate, irradiance, luminance, data rate, information content, latitude, longitude, acidity, signal power level, sound pressure level, counter value, humidity, battery energy level, event rate, and/or electrical conductivity.
  • Various operations of Figure 4 may be optional with respect to some embodiments.
  • operations of block 405 of Figure 4 may be optional, in which case, the time offset may be omitted from the measurement report.
  • modules may be stored in memory 305 of Figure 3, and these modules may provide instructions so that when the instructions of a module are executed by processor 303, processor 303 performs respective operations of the flow chart of Figure 5.
  • processor 303 may receive a measurement report from a sensor device 101 over a network through communication interface 301 , and the measurement report may include an identification of a base time event and a measurement value.
  • processor 303 may obtain information regarding the base time event, with the information regarding the base time event being obtained separate from the measurement report.
  • processor 303 may determine a time associated with the base time event. For example, the time associated with the base time event may be determined using the information regarding the base time event.
  • processor 303 may determine a time for the measurement value using the identification of the base time event. For example, the time for the measurement value may be determined using the time associated with the base time event. According to some embodiments, the time for the measurement value may be determined as the time associated with the base time event. According to some other embodiments, the measurement report may include a time offset value for the measurement value relative to the base time event, and the time for the
  • measurement value may be determined using the time associated with the base time event and the time offset value.
  • the information regarding the base time event of block 503 may be a time of the base time event.
  • the information regarding the base time event may be obtained by processor 303 receiving (through communication interface 301) a base time event report from a base time event sensor device 102 separate from the sensor device 101 , with the base time event report including the information regarding the base time event.
  • the base time event may be a sound (e.g., detected using base time event sensor 102). Moreover, identification of the base time event may be based on a fingerprint of the sound. In addition, identification of the base time event may be based on a hash of the acoustic fingerprint of the sound.
  • the base time event may be a network
  • the network communication may be at least one of a router advertisement, a routing update, a configuration message, a routing protocol update, an application layer message, and/or a medium access control MAC message.
  • the identification of the base time event may be based on a fingerprint of the network communication, and the fingerprint of the network communication may be based on a hash of the network communication (e.g., based on a hash of all bytes that make up the network communication).
  • the measurement value may be at least one of a measured value of distance, mass, time, electrical current, temperature, luminous intensity, concentration, frequency, angle, force, pressure, energy, power, electrical charge, electrical voltage, electrical capacitance, electrical resistance, electrical conductance, magnetic flux, magnetic flux density, electrical inductance, luminous flux, luminous emittance, radioactivity, ionizing radiation dose, catalytic activity, area, volume, velocity, acceleration, flow rate, irradiance, luminance, data rate, information content, latitude, longitude, acidity, signal power level, sound pressure level, counter value, humidity, battery energy level, event rate, and/or electrical conductivity.
  • modules may be stored in memory 305 of Figure 3, and these modules may provide instructions so that when the instructions of a module are executed by processor 303, processor 303 performs respective operations of the flow chart of Figure 6.
  • processor 303 may initiate generation of sound from a transducer proximate to sensor device 101, such that the sound can be used by sensor device 101 and network node 103 as a base time event. For example, processor 303 may initiate generation of the sound from a transducer included in and/or adjacent to network node 103 provided that network node 103 and sensor device 101 are proximate to one another, or processor 303 may initiate generation of the sound from a remote transducer by transmitting an instruction/signal through communication interface 301 to the remote transducer that is proximate to sensor device 101.
  • processor 303 may receive a measurement report from sensor device 101 over a network through communication interface 301 , and the measurement report may include an identification of a base time event and a measurement value.
  • the base time event may be the sound initiated at block 500.
  • processor may obtain information regarding the base time event (e.g., the sound initiated at block 500), and the information regarding the base time event may be obtained separate from the measurement report.
  • the information regarding the base time event may be obtained by receiving a base time event report from a base time event sensor device 102 separate from the sensor device 101 , with the base time event report including the information regarding the base time event.
  • a base time event report may be received over a network through communication interface 301 from base time event sensor device 102 that detects the sound initiated at block 600.
  • the information regarding the base time event may include a time of the base time event (e.g., a globaFsynchronized time that the sound was detected at based time event sensor device 102) and the identification of the base time event.
  • base time event sensor device 102 may be remote from network node 103 (e.g., if sensor device 101 is remote from network node 103), or base time event sensor device 102 may integrated with network node 103 if network node 103 is proximate to sensor device 101.
  • processor 303 may determine a time associated with the base time event using the information regarding the base time event.
  • processor 303 may determine a time for the measurement value using the identification of the base time event and using the time associated with the base time event. According to some embodiments, the time for the measurement value may be determined as the time associated with the base time event. According to some other embodiments, the measurement report may include a time offset value for the measurement value relative to the base time event, and processor 303 may determine the time for the measurement value at block 607 using the time associated with the base time event and the time offset value.
  • the identification of the base time event may be based on a fingerprint of the sound.
  • the identification of the base time event may be based on a hash of the acoustic fingerprint of the sound.
  • the measurement value may include at least one of a measured value of distance, mass, time, electrical current, temperature, luminous intensity, concentration, frequency, angle, force, pressure, energy, power, electrical charge, electrical voltage, electrical capacitance, electrical resistance, electrical conductance, magnetic flux, magnetic flux density, electrical inductance, luminous flux, luminous emittance, radioactivity, ionizing radiation dose, catalytic activity, area, volume, velocity, acceleration, flow rate, irradiance, luminance, data rate, information content, latitude, longitude, acidity, signal power level, sound pressure level, counter value, humidity, battery energy level, event rate, and/or electrical conductivity.
  • the terms “comprise”, “comprising”, “comprises”, “include”, “including”, “includes”,’3 ⁇ 4ave”,’3 ⁇ 4as", “having”, or variants thereof are open-ended, and include one or more stated features, integers, elements, steps, components or functions but does not preclude the presence or addition of one or more other features, integers, elements, steps, components, functions or groups thereof.
  • the common abbreviation “e.g.” which derives from the Latin phrase “exempli gratia,” may be used to introduce or specify a general example or examples of a previously mentioned item, and is not intended to be limiting of such item.
  • the common abbreviation “i.e.”, which derives from the Latin phrase “id est,” may be used to specify a particular item from a more general recitation.
  • Example embodiments are described herein with reference to block diagrams and/or flowchart illustrations of computer-implemented methods, apparatus (systems and/or devices) and/or computer program products. It is understood that a block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by computer program instructions that are performed by one or more computer circuits.
  • These computer program instructions may be provided to a processor circuit of a general purpose computer circuit, special purpose computer circuit, and/or other programmable data processing circuit to produce a machine, such that the instructions, which execute via the processor of the computer and/or other programmable data processing apparatus, transform and control transistors, values stored in memory locations, and other hardware components within such circuitry to implement the functions/acts specified in the block diagrams and/or flowchart block or blocks, and thereby create means (functionality) and/or structure for implementing the functions/acts specified in the block diagrams and/or flowchart block(s).

Landscapes

  • Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Telephonic Communication Services (AREA)

Abstract

L'invention concerne un dispositif de capteur (101) pouvant détecter un événement temporel de base (B = "b") et fournir une valeur de mesure. Le dispositif de capteur transmet ensuite un rapport de mesure sur un réseau à un nœud de réseau. Le rapport de mesure comprend une identification de l'événement temporel de base, la valeur de mesure et un décalage temporel (x) représentant une différence temporelle entre l'événement temporel de base et un temps de la valeur de mesure. Le nœud de réseau peut recevoir le rapport de mesure (comprenant l'identification de l'événement temporel de base, la valeur de mesure et le décalage temporel) en provenance du dispositif capteur sur le réseau. Le nœud de réseau peut ensuite déterminer un temps de la valeur de mesure à l'aide de l'identification de l'événement temporel de base. L'invention concerne également des dispositifs de capteur, des nœuds de réseau et des procédés associés.
PCT/EP2018/055075 2018-03-01 2018-03-01 Procédés fournissant des rapports de mesure comprenant une identification d'un événement temporel de base et capteurs et nœuds de réseau associés WO2019166092A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2018/055075 WO2019166092A1 (fr) 2018-03-01 2018-03-01 Procédés fournissant des rapports de mesure comprenant une identification d'un événement temporel de base et capteurs et nœuds de réseau associés

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2018/055075 WO2019166092A1 (fr) 2018-03-01 2018-03-01 Procédés fournissant des rapports de mesure comprenant une identification d'un événement temporel de base et capteurs et nœuds de réseau associés

Publications (1)

Publication Number Publication Date
WO2019166092A1 true WO2019166092A1 (fr) 2019-09-06

Family

ID=61616975

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2018/055075 WO2019166092A1 (fr) 2018-03-01 2018-03-01 Procédés fournissant des rapports de mesure comprenant une identification d'un événement temporel de base et capteurs et nœuds de réseau associés

Country Status (1)

Country Link
WO (1) WO2019166092A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021185432A1 (fr) * 2020-03-17 2021-09-23 Eaton Intelligent Power Limited Intégration de données de capteur et détection d'événement
CN116471211A (zh) * 2023-06-19 2023-07-21 威胜信息技术股份有限公司 一种电力物联网精准对时方法

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070230269A1 (en) * 2004-09-16 2007-10-04 Vanderbilt University Acoustic source localization system and applications of the same
US20120166141A1 (en) * 2010-12-27 2012-06-28 Watkins Matthew B Validation of electric power system monitoring systems
US9322072B2 (en) 2012-12-11 2016-04-26 Api Intellectual Property Holdings, Llc Processes and apparatus for lignin separation in biorefineries
WO2017070593A2 (fr) * 2015-10-23 2017-04-27 Qualcomm Incorporated Appareil et procédés de synchronisation d'un contrôleur et de capteurs
GB2544561A (en) * 2015-11-23 2017-05-24 Time Machine Capital Ltd Tracking system and method for determining relative movement of a player within a playing arena
WO2017108374A1 (fr) * 2015-12-22 2017-06-29 Philips Lighting Holding B.V. Système de capteur

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070230269A1 (en) * 2004-09-16 2007-10-04 Vanderbilt University Acoustic source localization system and applications of the same
US20120166141A1 (en) * 2010-12-27 2012-06-28 Watkins Matthew B Validation of electric power system monitoring systems
US9322072B2 (en) 2012-12-11 2016-04-26 Api Intellectual Property Holdings, Llc Processes and apparatus for lignin separation in biorefineries
WO2017070593A2 (fr) * 2015-10-23 2017-04-27 Qualcomm Incorporated Appareil et procédés de synchronisation d'un contrôleur et de capteurs
GB2544561A (en) * 2015-11-23 2017-05-24 Time Machine Capital Ltd Tracking system and method for determining relative movement of a player within a playing arena
WO2017108374A1 (fr) * 2015-12-22 2017-06-29 Philips Lighting Holding B.V. Système de capteur

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ACOUSTIC FINGERPRINT, FROM WIKIPEDIA, 8 January 2018 (2018-01-08), Retrieved from the Internet <URL:https: /en.wikipedia.org/wiki Acoustic_fingerprint>
JENNINGS ET AL., MEDIA TYPES FOR SENSOR MEASUREMENT LISTS (SENML) DRAFT-IETF-CORE-SENML-12, 14 December 2017 (2017-12-14), Retrieved from the Internet <URL:https://datatracker.ietf.org/doc/draft-ietf-core-senml>

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021185432A1 (fr) * 2020-03-17 2021-09-23 Eaton Intelligent Power Limited Intégration de données de capteur et détection d'événement
CN116471211A (zh) * 2023-06-19 2023-07-21 威胜信息技术股份有限公司 一种电力物联网精准对时方法
CN116471211B (zh) * 2023-06-19 2023-10-13 威胜信息技术股份有限公司 一种电力物联网精准对时方法

Similar Documents

Publication Publication Date Title
US11057136B1 (en) Time correction using extension fields
US9226231B2 (en) Systems and methods for monitoring the size of a wireless network
JP6073917B2 (ja) 発見メッセージおよびページングメッセージを送信および受信するためのシステムおよび方法
KR102604138B1 (ko) 서비스 계층 시간 동기화
US20130300541A1 (en) Improving positioning accuracy of location tracking system
US20220353948A1 (en) Method and device for sidelink communication
US20160109554A1 (en) ADAPTIVE OPTIMIZATION OF TIME OF FLIGHT (ToF) EXCHANGE
US20120195256A1 (en) Method and apparatus for timing and/or frequency offset monitoring and handling
JP6363225B2 (ja) ワイヤレスローカルエリアネットワークアクセスポイントの性能測定のシステム及び方法
WO2019166092A1 (fr) Procédés fournissant des rapports de mesure comprenant une identification d&#39;un événement temporel de base et capteurs et nœuds de réseau associés
WO2014101668A1 (fr) Procédé et appareil pour une gestion de synchronisation temporelle
JP5451775B2 (ja) ワイヤレスネットワークにおけるリンク品質推定方法
EP3414959A1 (fr) Configurations de communication pour un dispositif de machine
EP3528560B1 (fr) Procédé d&#39;indication sfn et système
Li et al. Efficient campaign-type structural health monitoring using wireless smart sensors
Schmitt et al. TinyIPFIX for smart meters in constrained networks
Nishi et al. Time synchronization of IEEE P1451. 0 and P1451. 1.6 standard-based sensor networks
Bae et al. Time synchronization in wireless sensor networks
Gnawali et al. Sensor networks architectures and protocols
Mahjri et al. Weighted localization in mobile wireless networks
CN102215499A (zh) 一种确定测量事件发生时间的方法
JP2007053653A (ja) 無線lan遅延量測定装置および無線lan遅延量測定方法
Zou et al. A time synchronization method for wireless sensor networks
Guclu et al. Dependability analysis of asynchronous radio duty cycling protocols
CN116266818A (zh) 信息测量方法及装置

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: 18709980

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18709980

Country of ref document: EP

Kind code of ref document: A1