[go: up one dir, main page]

EP3335481B1 - Synchronisation partielle de fonction de synchronisation de base de temps (tsf) dans un protocole de mesure de base de temps fine (ftm) - Google Patents

Synchronisation partielle de fonction de synchronisation de base de temps (tsf) dans un protocole de mesure de base de temps fine (ftm) Download PDF

Info

Publication number
EP3335481B1
EP3335481B1 EP16748381.7A EP16748381A EP3335481B1 EP 3335481 B1 EP3335481 B1 EP 3335481B1 EP 16748381 A EP16748381 A EP 16748381A EP 3335481 B1 EP3335481 B1 EP 3335481B1
Authority
EP
European Patent Office
Prior art keywords
wireless device
ftm
timestamp
frame
message
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
Application number
EP16748381.7A
Other languages
German (de)
English (en)
Other versions
EP3335481A1 (fr
Inventor
Subash MARRI SRIDHAR
Carlos Horacio Aldana
Santosh Kumar Vamaraju
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.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
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 Qualcomm Inc filed Critical Qualcomm Inc
Publication of EP3335481A1 publication Critical patent/EP3335481A1/fr
Application granted granted Critical
Publication of EP3335481B1 publication Critical patent/EP3335481B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H04W4/023—Services making use of location information using mutual or relative location information between multiple location based services [LBS] targets or of distance thresholds
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H04L5/0055—Physical resource allocation for ACK/NACK
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/001—Synchronization between nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/001—Synchronization between nodes
    • H04W56/0015—Synchronization between nodes one node acting as a reference for the others
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/0055—Synchronisation arrangements determining timing error of reception due to propagation delay
    • H04W56/0065—Synchronisation arrangements determining timing error of reception due to propagation delay using measurement of signal travel time

Definitions

  • a station may include at least one local clock or timer on which the station bases its communication and data processing.
  • it is usually difficult to precisely synchronize the local clocks among several stations in a system.
  • a first RTT in a first direction is determined between a first wireless device and a second wireless device based on a first set of one or more messages exchanged between the first wireless device and the second wireless device.
  • a second RTT in a second direction is determined between the second wireless device and the first wireless device based on a second set of one or more messages exchanged between the second wireless device and the first wireless device, and an average RTT of the first RTT and the second RTT is computed, wherein the average RTT has a low impact of the clock drifts.
  • a method for determining at least one of a time for exiting and a time for entering a low power sleep mode to utilize a discovery window includes determining an earliest possible start time of a discovery window according to a clock at the first device. The method further includes transitioning from the low power sleep mode to a higher power active mode approximately at the determined earliest possible start time, wherein the determined earliest possible start time is based at least in part on a clock drift value associated with the first device and a clock drift value associated with a second device of the wireless network.
  • An example method for broadcasting network neighbor reports includes generating a beacon transmission, determining a neighbor report count value, if the neighbor report count value is greater than zero, then broadcasting the beacon transmission including at least a beacon frame and the neighbor report count value, and decrementing the neighbor report count value; if the neighbor report count value is equal to zero, then broadcasting the beacon transmission including at least a beacon frame and a neighbor report, and resetting the neighbor count value.
  • a wireless station generates a time stamp at a higher resolution than can be broadcast within a standard time stamp field in a frame.
  • the generated time stamp is divided into two parts: the first part being included within the time stamp field and the second part being included within a vendor specific field in the same frame.
  • the frame is transmitted by the wireless station and received by other wireless stations in the wireless network. If the receiving wireless station has the capability, it decodes both the time stamp field and the vendor specific field and recreates the higher resolution time stamp.
  • This higher resolution time stamp is then used to synchronize the receiving wireless station and the transmitting wireless station by resetting a clock or by storing time stamps and corresponding clock values.
  • the techniques can improve the efficiency and power consumption of timing synchronization between wireless devices.
  • the techniques involve embedding partial timing synchronization function (TSF) timer values in fine timing measurement (FTM) frames such that a wireless device receiving the FTM frames may set its local TSF timer based on the received TSF timer values.
  • TSF partial timing synchronization function
  • FTM fine timing measurement
  • STAs Fixed, portable, or mobile stations (STAs) in a single infrastructure basic service set (BSS) or an independent BSS (IBSS) are usually synchronized to a common clock.
  • BSS infrastructure basic service set
  • IBSS independent BSS
  • STAs maintain local TSF timers for synchronization or other purposes.
  • the TSF timer counts in increments of microseconds with a maximum counter value of 2 64 .
  • the timing synchronization function keeps the TSF timers for all STAs in the same BSS synchronized.
  • An access point (AP) in a BSS may be the timing master for the TSF.
  • an initiating STA may have a sense of the TSF of a responding STA or AP for accurate timing measurement.
  • An AP or responding STA may periodically transmit Beacons or announce frames including the value of the AP's TSF timer in order to synchronize the TSF timers of other STAs.
  • An STA can synchronize its local TSF timer to the AP or responding STA by constantly receiving and parsing Beacons or announce frames.
  • an initiating STA may actively transmit probe request frames and wait for a probe response that includes time information.
  • the initiating STA's TSF timer is different from a timestamp in the received Beacon, announce frame or probe response, the initiating STA may set its local TSF timer based on the received timestamp value.
  • a timestamp refers to encoded information indicating the time when a certain event occurs.
  • Wireless communication systems may comprise wireless devices and APs, which allow the wireless devices to connect to a wired or wireless network using one or more wireless standards.
  • An AP is generally referred to as an entity that includes one STA and provides access to distribution services via wireless medium for associated STAs.
  • An STA is a logical entity that is a singly addressable instance of a medium access control (MAC) and a physical layer (PHY) interface to the wireless medium.
  • MAC medium access control
  • PHY physical layer
  • Some wireless communication systems may allow wireless devices to be configured as STAs that can communicate between one another or through the APs. Standards such as IEEE 802.1 1ac, 802.1 1ad, 802.1 1v, 802.11REVmc, etc. are commonly used for such communications. These standards can include error specifications to ensure quality of communication.
  • IEEE 802.11 is a set of media access control and physical layer specification for implementing wireless local area network (WLAN) communication, called Wi-Fi, in the unlicensed (2.4, 3.6, 5, and 60 GHz) frequency bands.
  • Wi-Fi plays an important role in the growing application of Indoor Location.
  • the key applicable Wi-Fi technology in Indoor Location is ranging using time-of-flight (TOF) ranging measurements defined in IEEE 802.11, because distances between devices can be used to determine device location.
  • TOF time-of-flight
  • fine timing measurement protocol is proposed for ranging.
  • an initiating station exchanges FTM frames with a responding station to measure the time-of-flight or the round trip time (RTT).
  • the initiating station then computes its range to the responding station after receiving fine timing measurements (i.e., timestamps corresponding to the departure time of the FTM frame and the arrival time of its corresponding acknowledge ACK frame) from the responding station.
  • fine timing measurements i.e., timestamps corresponding to the departure time of the FTM frame and the arrival time of its corresponding acknowledge ACK frame
  • the initiating station exchanges FTM frames with multiple responding APs for TOF measurements in order to determine its absolute location.
  • the initiating station exchanges FTM frames with at least three APs in order to determine its absolute location.
  • FIG. 1A is a simplified illustration of a wireless communication system 100, according to one embodiment.
  • the wireless communication system 100 can include one or more STA(s) 105, AP(s) 120, and a data communication network 130.
  • FIG. 1A provides only a generalized illustration of various components, any or all of which may be utilized as appropriate. Furthermore, components may be rearranged, combined, separated, substituted, and/or omitted, depending on desired functionality. For example, although only a few STAs 105 and APs are illustrated in wireless communication system 100 illustrated in FIG. 1A , embodiments may include a smaller or larger number of either or both STAs and/or APs.
  • embodiments may include dozens, hundreds, thousands, or more of either or both STAs and/or APs.
  • STA(s) 105 and/or AP(s) 120 may be connected with one or more additional networks, such as cellular carrier networks, satellite positioning networks, and the like which can have a variety of components (e.g., servers, satellites, base stations, etc.) that are not illustrated in FIG. 1A .
  • additional networks such as cellular carrier networks, satellite positioning networks, and the like which can have a variety of components (e.g., servers, satellites, base stations, etc.) that are not illustrated in FIG. 1A .
  • components e.g., servers, satellites, base stations, etc.
  • a wireless device or STA may comprise a system, a subscriber unit, a subscriber station, a fixed station, a portable station, a mobile station, a remote mobile station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, a user device, a user equipment (UE), or an access point.
  • an STA can be a cellular telephone, a cordless telephone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device having wireless connection capability, a computing device, or other processing device connected to a wireless modem.
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital assistant
  • STA(s) 105 can communicate with AP(s) 120, which can enable the STA(s) 105 to communicate through data communication network 130. Communication to and from STA(s) 105 may thus also be implemented, in some embodiments, using various wireless communication standards and/or protocols, which may be determined by data communication network 130. Some embodiments can include, for example, one or more of the IEEE 802.11 family of standards as discussed above.
  • Data communication network 130 may comprise one or more of a variety of networks, including local networks such as a local area network (LAN) or a personal area network (PAN), a wide area network (WAN) such as the Internet, and/or any of a variety of public and/or private communication networks.
  • networking technologies can include switching and/or packetized networks utilizing optical, radio frequency (RF), wired, satellite, and/or other technologies.
  • Wireless communication system 100 may provide positioning capabilities to calculate or estimate the location of one or more STAs 105.
  • Such capabilities can include a satellite positioning system (SPS), such as the Global Positioning System (GPS), and/or triangulation and/or trilateration provided by stationary components, such as the AP(s) 120.
  • SPS satellite positioning system
  • GPS Global Positioning System
  • STAs 105 may be configured to provide positioning capabilities based on their determined distance from one another.
  • the determination of round trip time for pre-specified messages or dialogs between two STAs for example, can be used to provide an indication of distance between the two STAs.
  • An STA 105 can include at least one local clock, on which the STA 105 bases its communication and data processing. However, it is usually not possible to precisely synchronize the local clocks among the several STAs, and therefore, each local clock may have its own timing error or clock drift relative to clocks of other STAs.
  • FIG. 1B illustrates an example setup in which synchronization between STAs may be achieved, according to one embodiment.
  • two STAs STA1 105-1 and STA2 105-2
  • STAs 105 may be part of a larger system, such as wireless communication system 100 illustrated in FIG. 1A .
  • STAs 105 may engage in an exchange of fine timing measurement frame and acknowledgement, as described below.
  • FIG. 1C is another example setup in which STAs may be synchronized.
  • an AP can communicate with three STAs - STA1 105-a, STA2 105-b, and STA3 105-c -using wireless communication signals 110.
  • the wireless communication signals 110 may include uplink (UL) and/or downlink (DL) frames.
  • STAs may additionally communicate directly with each other via similar means.
  • Additional STAs and/or APs (not shown) may be part of the same wireless system (e.g., WLAN).
  • Some wireless systems may have more or fewer STAs. It will be understood that the techniques described herein may be utilized in systems having different configurations and/or components than those shown. Moreover, wireless systems may include other types of wireless devices.
  • the STAs and/or APs can correspond with wireless devices and/or may incorporate components of a computer, such as computing systems, described below in the present disclosure.
  • embodiments described herein may pertain to wireless communications for devices utilizing a wireless communication system 100, such as a WLAN, according to various IEEE 802.11 communication standards. Some embodiments may utilize standards other than the IEEE 802.11 family of standards. In some embodiments, rather than relying on satellite signals or assistance data from terrestrial base stations transmitting satellite geo-positioning data, STAs may acquire their geographic locations using wireless APs. The APs may transmit and receive wireless signals following various IEEE 802.11 standards, such as 802.11g, 802.11n, 802.1 1ac, 802.11ad, 802.11v, etc.
  • STAs may comply with 802.1 1ac, 802.11v, and/or 802.11REVmc standards while transmitting or receiving signals from multiple antennas. Some embodiments may sample timing signals in 0.1 nanosecond (ns) or 1 picosecond (ps) increments, while some other embodiments may sample signals in time increments of less than 10 ns, such as, for example, 1.5 ns, 2 ns, 0.1 ns, etc., while still complying with the standards.
  • Embodiments may implement time of departure (TOD) and time of arrival (TOA) measurements from IEEE 802.11 standards based on definitions that account for transmitted signals from multiple antennas.
  • TOD time of departure
  • TOA time of arrival
  • both receiving and sending STAs may transmit information sufficient to compute TOD and TOA measurements.
  • some of the information may be codified in revised 802.11 standards.
  • the APs may transmit and receive timing measurements, such as TOA and TOD measurements, to and from the STAs.
  • the STA may be able to determine its location by performing techniques similar to GPS positioning, e.g. trilateration and the like, using the multiple timing measurements.
  • the STAs may transmit and receive timing measurements between one another in order to obtain the RTT and the distance between one another.
  • FIG. 2 illustrates an IEEE 802.11REVmc FTM session 200 with multiple bursts.
  • an STA 220 that supports fine timing measurement protocol as an initiator (referred to as an initiating STA) transmits an initial FTM Request frame 230.
  • An STA 210 that supports the fine timing measurement protocol as a responder (referred to as a responding STA) does not transmit FTM frames to a peer STA unless the peer STA supports the fine timing measurement protocol as an initiator and responding STA 210 has received an initial FTM request frame from the peer STA.
  • FTM request frame 230 may include a trigger field and a set of scheduling parameters in a FTM parameters field that describe the initiating STA's availability for measurement exchange.
  • Responding STA 210 may send an ACK frame 232 to initiating STA 220 acknowledging the successful reception of initial FTM request 230.
  • a first FTM frame in FTM session 200 is an initial FTM frame FTM_1 234.
  • Responding STA 210 may generally transmit initial FTM frame FTM_1 234 within 10 ms in response to initial FTM request frame 230.
  • Initial FTM frame FTM_1 234 includes a FTM parameters field.
  • a value of a status indication field in initial FTM frame FTM_1 234 indicates whether the initial FTM request was successful, incapable or failed.
  • Initiating STA 220 acknowledges the receiving of initial FTM frame FTM_1 234 by sending an ACK frame 236.
  • FTM frames are generally sent during time windows called burst instances.
  • the timing of the burst instances may be defined by the following parameters in the FTM parameter field of an initial FTM request frame or initial FTM frame: (1) partial TSF timer value for the beginning of the first burst instance; (2) burst duration - the duration of each burst instance starting at the boundary of a burst period; and (3) burst period - the interval from the beginning of one burst instance to the beginning of the following burst instance.
  • an "ASAP" field in FTM request frames is set to 0.
  • the ASAP field indicates whether an initiating STA's requests to start the first burst instance of the FTM session as soon as possible.
  • the ASAP field is set to 0 by an initiating STA
  • the initiating STA requests the start of the first burst instance specified by the partial TSF timer field in the FTM request frame.
  • the ASAP field in the FTM request frame is set to 1 by an initiating STA
  • the partial TSF timer field in the FTM request frame indicates the requested start of the first burst instance if the ASAP field is set to 0 in the initial FTM frame.
  • an FTM trigger frame may be used to trigger each burst instance.
  • An FTM trigger frame is an FTM request frame that has the trigger field set to 1 and does not include a measurement request field or a FTM parameters field.
  • the first burst instance starts at the value indicated by the Partial TSF Timer field in the initial FTM frame.
  • the Partial TSF Timer field value may be set to a value less than 10 ms from the reception of the most recent initial FTM request frame.
  • the ASAP field can also be used by the responding STA to signal whether the initiating STA's request to start the first burst instance of the FTM session as soon as possible has been honored or not.
  • the Partial TSF Timer field in the initial Fine Timing Measurement frame indicates the start time of the first burst instance and the earliest time the FTM trigger should be sent by the initiating STA.
  • the ASAP field is set to 1 by the responding STA, the Partial TSF Timer field in the initial Fine Timing Measurement frame indicates the start time of the first burst instance and the earliest time the initial Fine Timing Measurement frame will be sent.
  • the responding STA may set the ASAP field to 1 to indicate the STA's intent to send a Fine Timing Measurement frame as soon as possible.
  • initiating STA 220 transmits an FTM trigger frame 238 at the beginning of a burst as soon as it is available on channel. This indicates to responding STA 210 availability of initiating STA 220 for the remainder of the burst instance. Following FTM trigger frame 238, responding STA 210 transmits an ACK frame 240, and transmits non-initial FTM frames, such as FTM_2 242 and FTM_3 246, before the burst duration elapses. Initiating STA 220 sends an ACK frame, such as ACK frame 244 or 248, each time an FTM frame is successfully received. Within a burst instance, consecutive FTM frames are spaced at least a Min Delta FTM apart. After a burst period, a next burst instance may start, which includes similar operations as in the first burst instance as indicated by operations 250, 252, 254, 256, 258, and 260.
  • initiating STA 220 may perform fine timing measurement on each FTM frame addressed to it. For example, responding STA 210 transmits FTM frame FTM_2 242, and captures a first time tl_2 when FTM frame FTM_2 242 is transmitted. Initiating STA 220 captures a second time t2_2 when FTM frame FTM_2 242 arrives at initiating STA 220. Additionally, initiating STA 220 captures a third time t3_2 hen it transmits ACK frame 244. Responding STA 210 captures a fourth time t4_2 when ACK frame 244 arrives at responding STA 210.
  • FIG. 3A illustrates an example of an FTM request frame 310 that corresponds to, for example, initial FTM request 230, FTM request 238, or FTM request 250 of FIG. 2 .
  • FTM request frame 310 includes a 1-octet Category field, a 1-octet Public Action field, a 1-octet Trigger field, an optional location configuration information (LCI, which may include latitude, longitude and altitude information) measurement request field, an optional Location Civic Measurement Request field, and an optional FTM Parameters field.
  • the Category field is set to the value for Public.
  • the Public Action field is set to indicate that this is a FTM request frame.
  • the LCI Measurement Request field includes a Measurement Request element with Measurement Type equal to LCI Request, which indicates a request for a Measurement Report element with Measurement Type equal to LCI.
  • the Location® Measurement Request field includes a Measurement Request element with Measurement Type equal to Location® Request, which indicates a request for a Measurement Report with Measurement Type equal to Location Civic report.
  • the FTM Parameters field is present in the initial FTM Request frame, such as initial FTM request 230 of FIG. 2 , but is not present in subsequent FTM Request (trigger) frames, such as FTM Request frame 238 or 250 in FIG. 2 . If present, the FTM parameter field includes FTM parameters.
  • FIG. 3B is an example of an FTM frame 320 that corresponds to, for example, FTM_1 234, FTM_2 242, FTM_3 246, FTM 4 254,or FTM_5 258 of FIG. 2 .
  • FTM frame 320 includes a 1-octet Category field, a 1-octet Public Action field, a 1-octet Dialog Token field, a 1-octet Follow Up Dialog Token field, a 6-octet TOD field, a 6-octet TOA field, a 2-octet TOD Error field, a 2-octet TOA Error field, an optional LCI Report field, an optional Location Civic Report field, and an optional FTM Parameters field.
  • the Category field is set to the value for Public.
  • the Public Action field is set to indicate that this is a FTM frame.
  • the Dialog Token field is a nonzero value chosen by the responding STA to identify the FTM frame as the first of a pair, such as FTM_2 242 in FIG. 2 , with a second or a follow-up FTM frame, such as FTM_3 246, to be sent later.
  • the Dialog Token field can be set to "0" to indicate that the FTM frame will not be followed by a subsequent follow-up FTM frame.
  • the Follow Up Dialog Token field is the nonzero value of the Dialog Token field of the last transmitted FTM frame, indicating that it is the follow up FTM frame and that the TOD, TOA, TOD Error and TOA Error fields include the values of the timestamps captured for the first FTM frame of the pair.
  • FTM_3 246 may include timestamps captured for FTM frame FTM_2 242.
  • the Follow Up Dialog Token field is set to "0" to indicate that the FTM frame is not a follow-up to a last transmitted FTM.
  • the TOD, TOA, TOD Error, and TOA Error fields may be expressed in units of 0.1 ns.
  • the TOD field includes a timestamp that represents the time, with respect to a time base, at which the start of the preamble of the last transmitted FTM frame appeared at the transmit antenna connector.
  • the TOA field includes a timestamp that represents the time, with respect to a time base, at which the start of the preamble of the ACK frame to the last transmitted FTM frame arrived at the receive antenna connector.
  • the TOD Error field includes an upper bound for the error in the value specified in the TOD field.
  • the TOA Error field includes an upper bound for the error in the value specified in the TOA field.
  • the LCI Report field is optionally present. If present, it includes a Measurement Report element with Measurement Type equal to LCI report.
  • the Location Civic Report field is optionally present.
  • the FTM Parameters field is present in the initial FTM frame, such as FTM_1 234 in FIG. 2 , but is not present in subsequent FTM frames, such as FTM_2 242 or FTM_3 246 in FIG. 2 . If present, the FTM Parameters filed includes FTM Parameters.
  • the FTM protocol may be extended or modified to transmit TSF timer values within the FTM frames along with the time information for fine timing measurement.
  • FIG. 4 is a diagram 400 illustrating an FTM session with partial timing synchronization function timer values embedded in FTM frames according to some embodiments of the present disclosure.
  • FIG. 4 is similar to FIG. 2 , but with additional timestamps being captured and transmitted.
  • timestamps of the last successfully transmitted FTM request frame for which an ACK has been properly received by the initiating STA
  • initial FTM request 430 and FTM trigger requests 438 and 450 in FIG. 4 can be captured at both initiating STA 420 at the time of departure (TOD) of the FTM request and at responding STA 410 at the time of arrival (TOA) of the FTM request.
  • TOD time of departure
  • TOA time of arrival
  • Responding STA 410 can then send the captured timestamp at TOA of the last successfully transmitted FTM request in an FTM frame. For example, as shown in FIG. 4 , responding STA 410 may capture its timer value t0_1 at the TOA of initial FTM request 430, and send the timer value t0_1 in FTM_1 434 to initiating STA 420, which may then use time value t0_1 and the timestamp t0_0 it captured at the TOD of the initial FTM request 430 for synchronization with responding STA 410.
  • responding STA 410 may capture its timer value t0_3 or t0_5 at the TOA of a first non-initial FTM request (FTM trigger request), such as FTM request 438 or 450, and send timer value t0_3 in FTM_2 442 or t0_5 in FTM_4 454 to initiating STA 420, which may then use time value t0_3 or t0_5 and the timestamp it captured at the TOD of FTM request 438 (t0_2) or 450 (t0_4) for synchronization with responding STA 410.
  • FTM trigger request such as FTM request 438 or 450
  • Some embodiments may vary from the FTM session illustrated in FIG. 4 , depending on the request of the initiating STA.
  • the FTM session may be in multiple-burst or single-burst mode, and the initiating STA may request responding STA 710 to start the burst instances "as soon as possible.”
  • the order of determining timestamps and sending messages may be altered.
  • the timestamps captured at the responding STA such as t0_3 or t0_5
  • a timestamp captured at the responding STA may be sent in two or more parts.
  • a part of timestamp t0_3 may be sent in FTM_2 442 and the other part of timestamp t0_3 may be sent in FTM_3 446.
  • FTM_2 442 a part of timestamp t0_3 may be sent in FTM_2 442 and the other part of timestamp t0_3 may be sent in FTM_3 446.
  • FIG. 5A illustrates an example modified initial FTM frame 500, such as FTM_1 434 in FIG. 4 , in response to an initial FTM request, such as initial FTM request 430.
  • FTM frame 500 includes new fields 510 compared with FTM frame 320 shown in FIG. 3B .
  • New fields 510 may include a 1-octet Element ID, a 1-octet Length, and a 2, 3, 4, or 5-octet partial TSF of FTM Request Frame.
  • the Element ID identifies the type of an element by a pre-defined number.
  • the Length field specifies the number of octets following the Length field. For example, the length field may have a value of 2, 3, 4, or 5 for FTM frame 500.
  • the partial TSF of FTM request frame may include at least a part of a timestamp captured at the TOA of the FTM request frame by the responding STA, and may include, for example, 2 octets, 3 octets, 4 octets, or 5 octets.
  • new field 510 may be added at different locations in FTM frame 500, such as before the LCI Report field.
  • the partial TSF of FTM request frame field may represent bits [25:10] of a 64-bit full TSF timer value (&0x0000000003FFFC00), and therefore has a unit of 2 10 or 1024 ⁇ s and a wrap-around time of about 67 seconds.
  • This format is consistent with Partial TSF field used in, for example, FTM parameters field of an FTM frame.
  • the partial TSF may represent bits [23:0] of the 64-bit full TSF timer value (&0x0000000000FFFFFF), and therefore has a unit of 1 ⁇ s and a wrap-around time of about 17 seconds. This may be helpful when the burst duration is 250 ⁇ s, which requires a better timing accuracy.
  • the partial TSF may represent bits [31:8] of the full TSF timer value (&0x00000000FFFFFF00), and therefore has a unit of 2 8 or 256 ⁇ s and a wrap-around time of about 1.2 hours.
  • the partial TSF may represent bits [31:0] of the full TSF timer value (&0x00000000FFFFFF), and therefore has a unit of 1 ⁇ s and a wrap-around time of about 1.2 hours. This may be helpful when the burst duration is 250 ⁇ s, which requires a better timing accuracy.
  • the partial TSF may represent bits [39:0] of the full TSF timer value (&0x000000FFFFFFFF), and therefore has a unit of 1 ⁇ s and a wrap-around time of about 305 hours.
  • a full 64-bit TSF timer value may be included in initial FTM frame 500 in response to an initial FTM request, rather than only sending a partial TSF timer value.
  • FIG. 5B illustrates an example modified non-initial FTM frame 550, such as FTM_2 and FTM_4 of FIG. 4 , in response to a first non-initial FTM request, such as FTM request 438 or 450 in FIG. 4 , at the beginning of a burst instance.
  • Non-initial FTM frame 550 includes new fields 560 compared with a first non-initial FTM frame in a way similar to initial FTM frame 500.
  • new fields 560 in non-initial FTM frame 550 may include a 1-octet Element ID, a 1-octet Length, and a 2, 3, 4, or 5-octet partial TSF of FTM Request Frame.
  • the Element ID identifies the type of an element by a pre-defined number.
  • the Length field specifies the number of octets following the Length field.
  • the length field may have a value of 2, 3, 4, or 5 for non-initial FTM frame 550.
  • the partial TSF of FTM request frame may include at least a part of a timestamp captured at the non-initial FTM request frame by the responding STA, and may include 2 octets, 3 octets, 4 octets, or 5 octets, where the partial TSF value may include the same bits as described above with respect to initial FTM frame 500 in FIG. 5A .
  • a full 64-bit TSF timer value may be included in initial FTM frame 500 in response to the initial FTM request, while a 2, 3, 4, or 5-octet partial TSF value may be included in non-initial FTM frame 550.
  • the partial TSF value may be larger than 5 octets or less than 2 octets.
  • FIG. 5C illustrates an example modified FTM Parameters field 580.
  • reserved bit B40 may be designated as a Partial TSF Timer No Preference bit.
  • the Partial TSF Timer No Preference bit in FTM Parameters field 580 indicates that the initiating STA has no preference as to when the first burst instance starts, and the corresponding Partial TSF Timer field (B24-B39) is reserved and should be ignored by the responding STA.
  • the Partial TSF Timer No Preference bit is reserved, or set to "0," when FTM Parameters field 580 is included in a Fine Timing Measurement frame.
  • a reserved bit in TOA error field may be set to indicate that a partial TSF of FTM Request Frame field is present such that the element ID and length field in FTM frame 500 or 550 may be omitted to reduce the number of bits transmitted.
  • FIG. 6A illustrates an example modified initial FTM frame 600, such as FTM_1 of FIG. 4 , using a reserved bit, where a reserved bit in TOA error field is set to 1 to indicate that a partial TSF of FTM Request Frame field is present, and a partial TSF of FTM request frame field 620 is inserted after the TOA error field.
  • partial TSF of FTM request frame field 620 may be 2, 3, 4, or 5-octet long and may represent the same bits as described above with respect to initial FTM frame 500 in FIG. 5A .
  • a full 64-bit TSF value may be included in FTM frame 600 in response to the initial FTM request, rather than only sending a partial TSF.
  • FIG. 6B illustrates an example modified first non-initial FTM frame 650, such as FTM_2 and FTM_4 of FIG. 4 , in response to a first non-initial FTM request at the beginning of a burst instance, where a reserved bit is set to 1 to indicate that a partial TSF of FTM Request Frame field is present.
  • a partial TSF of FTM request frame field 660 is inserted after the TOA error field.
  • partial TSF of FTM request frame field 660 may be 2, 3, 4, or 5-octet long and may represent the same bits as described above with respect to non-initial FTM frame 550 in FIG. 5B .
  • the above examples illustrate certain embodiments of the present disclosure in multiple-burst situations and with ASAP set to 0.
  • the partial TSF of FTM request frame field as described above may be inserted into the first FTM of any burst instance in response to a non-initial FTM request and/or an initial FTM frame in response to an initial FTM request.
  • FIG. 7A illustrates an FTM session 700 according to one embodiment of the present disclosure, where initiating STA 720 requests responding STA 710 to start the burst instances "as soon as possible" by setting the ASAP field to 1.
  • initiating STA 720 sends an FTM request 722 to responding STA 710, which, in response to receiving FTM request 722, sends an ACK frame 724 to initiating STA 720.
  • Responding STA 710 then starts to send a first FTM frame FTM_1 726 to initiating STA 720.
  • Initiating STA 720 sends an ACK 728 to responding STA 710 upon receiving FTM_1 726.
  • Responding STA 710 then sends a second FTM frame FTM_2 730 to initiating STA 720.
  • FTM_2 730 Upon receiving FTM_2 730, initiating STA 720 sends an ACK frame 732 to responding STA 710. Similar processes can be carried out in the next burst instance as shown by FTM request frame 734, ACK frame 736, FTM_3 738, ACK frame 740, FTM_4 742 and ACK frame 744.
  • the first FTM frame of each burst instance may include partial TSFs of FTM request frames 722 or 734.
  • the format and fields of FTM frames FTM_1 726 and FTM_3 738 may be the same as FTM frame 500 or 550 shown in FIG. 5A or 5B , or FTM frame 600 or 650 shown in FIG. 6A or 6B , as described above.
  • the value in the partial TSF of FTM request frame field may be a timestamp captured at responding STA 710 at the time of arrival of the FTM request frames 722 or 734, as indicated by t0_1 and t0_3 in FIG. 7A .
  • FIG. 7B illustrates an FTM session 750 according to another embodiment of the present disclosure, where initiating STA 770 requests a single burst of fine timing measurement to be taken as soon as possible by setting a Number of Bursts Exponent field (B8-B11 of FIG. 5C ) to 0 and the ASAP field to 1.
  • initiating STA 770 sends an FTM request 780 to responding STA 760, which, in response to receiving FTM request 780, sends an ACK frame 782 to initiating STA 770.
  • Responding STA 760 then starts to send a first FTM frame FTM_1 784 to initiating STA 770.
  • Initiating STA 770 sends an ACK frame 786 to responding STA 760 upon receiving FTM_1 784. Responding STA 760 then sends a second FTM frame FTM_2 788 to initiating STA 770. Upon receiving FTM_2 788, initiating STA 770 sends an ACK frame 790 to responding STA 760.
  • the first FTM frame of the single burst may include partial TSF of FTM request frame 780.
  • the format of FTM frame FTM_1 784 may be the same as FTM frame 500 or 550 in FIG. 5A or 5B , or FTM frame 600 or 650 in FIG. 6A or 6B , as described above.
  • the value in the partial TSF of FTM request frame field may be a timestamp captured at responding STA 760 at a time of arrival of the FTM request 780.
  • FIGS. 7A and 7B also illustrate some other embodiments of possible values of the partial TSF embedded in a FTM frame.
  • FIG. 7A rather than capturing timestamp t0_1 at responding STA 710 at the time of arrival of FTM request 722 and converting the captured timestamp t0_1 to a partial TSF to be embedded into FTM frame FTM _1 726, the time of departure of the current FTM frame FTM_1 726 (t1_1) at responding STA 710 can be captured and converted to a partial TSF, and embedded into FTM frame FTM_1 726.
  • initiating STA 720 may use the partial TSF of t1_1 and a time of arrival of FTM frame FTM_1 726 at initiating STA 720 (t2_1) for synchronization.
  • the time of departure of ACK frame 782 (t0_1) at responding STA 760 can be captured and converted to a partial TSF, and embedded into FTM frame FTM_1 784.
  • Initiating STA 770 may capture the time of arrival t0_2 of ACK frame 782 at initiating STA 770.
  • initiating STA 770 may use the partial TSF of t0_1 and the captured time of arrival t0_2 of ACK frame 782 at initiating STA 770 for synchronization.
  • the value of the partial TSF or full TSF may be any one of the time of arrival of an FTM request at the responding STA, the time of departure of an ACK frame from the responding STA in response to the FTM request, or the time of departure of a first FTM frame from the responding STA, in either multiple-burst or single-burst mode, with ASAP being set to either 0 or 1.
  • FIGS. 8A-8D illustrate some embodiments of timing synchronization methods on an initiating STA disclosed in the present disclosure. It is noted that even though FIGS. 8A-8D describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be rearranged. An operation may have additional steps not included in the figure. Some operations may be optional, and thus may be omitted in various embodiments. Some operations described in one block may be performed together with operations at another block. Furthermore, embodiments of the methods may be implemented in hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof.
  • FIG. 8A is a flow chart 800 illustrating some embodiments of methods of timing synchronization on an initiating wireless device using partial timing synchronization function timestamp in an FTM frame.
  • a first wireless device such as initiating STA 420, 720, or 770, sends a first message to a second wireless device, such as responding STA 410, 710, or 760.
  • the first message may be an initial FTM request frame, such as initial FTM request frame 430 in FIG. 4 , or a non-initial FTM request frame, such as FTM request frame 438 or 450 in FIG. 4 , FTM request frame 722 or 734 in FIG. 7A , or FTM request frame 780 in FIG. 7B .
  • Means for performing the function at block 802 may include but are not limited to, for example, wireless communication subsystem 1030, processing unit 1010, memory 1060, and/or bus 1005 as illustrated in FIG.
  • means for performing the function at block 802 may include but are not limited to, for example, wireless communications subsystem 1133, processing unit 1110, working memory 1135, and/or bus 1105 as illustrated in FIG. 11 and described in detail below.
  • the first wireless device may optionally capture or otherwise obtain a first timestamp, which indicates a time of departure of the first message from the first wireless device.
  • the first wireless device may obtain the first timestamp based on a local clock running on the first wireless device.
  • the first timestamp may be, for example, t0_0, t0_2 or t0_4 in FIG. 4 , t0_0 or t0_2 in FIG. 7A , or t0_0 in FIG. 7B .
  • Means for performing the function at block 804 may include but are not limited to, for example, clock 1045, processing unit 1010, memory 1060, input device(s) 1070, and/or bus 1005 as illustrated in FIG. 10 and described in detail below.
  • means for performing the function at block 804 may include but are not limited to, for example, clock 1150, processing unit 1110, working memory 1135, and/or bus 1105 as illustrated in FIG. 11 and described in detail below.
  • the first wireless device may receive a second message from the second wireless device in response to the first message.
  • the second message may be an acknowledgement message from the second wireless device to the first wireless device indicating the successful reception of the first message.
  • the second message may be one of ACK frame 432, 440 or 452 in FIG. 4 , ACK frame 724 or 736 in FIG. 7A , or ACK frame 782 in FIG. 7B .
  • Means for performing the function at block 806 may include but are not limited to, for example, wireless communication subsystem 1030, processing unit 1010, memory 1060, and/or bus 1005 as illustrated in FIG. 10 .
  • means for performing the function at block 806 may include but are not limited to, for example, wireless communications subsystem 1133, processing unit 1110, working memory 1135, and/or bus 1105 as illustrated in FIG. 11 and described in detail below.
  • the first wireless device may capture or otherwise obtain an alternative first timestamp at a time of arrival of the second message at the first wireless device, such as t0_2 shown in FIG. 7B that indicates the time of arrival of ACK frame 782 at initiating STA 770.
  • Means for performing the function at block 808 may include but are not limited to, for example, clock 1045, processing unit 1010, memory 1060, input device(s) 1070, and/or bus 1005 as illustrated in FIG. 10 .
  • means for performing the function at block 808 may include but are not limited to, for example, clock 1150, processing unit 1110, working memory 1135, and/or bus 1105 as illustrated in FIG. 11 and described in detail below.
  • the first wireless device receives a third message from the second wireless device.
  • the third message may be an FTM frame, such as, for example, FTM_1 434, FTM_2 442, or FTM_4 454 in FIG. 4 , FTM_1 726 or FTM_3 738 in FIG. 7A , or FTM_1 784 in FIG. 7B .
  • the third message may include at least a part of a second timestamp obtained by the second wireless device.
  • the second timestamp may be captured by the second wireless device at a time of arrival of the first message at the second wireless device, such as t0_1, t0_3, or t0_5 in FIG.
  • the second wireless device may capture the second timestamp based on a local clock running on the second wireless device.
  • Means for performing the function at block 810 may include but are not limited to, for example, wireless communication subsystem 1030, processing unit 1010, memory 1060, clock 1045, and/or bus 1005 as illustrated in FIG. 10 .
  • means for performing the function at block 810 may include but are not limited to, for example, wireless communications subsystem 1133, processing unit 1110, working memory 1135, clock 1150, and/or bus 1105 as illustrated in FIG. 11 and described in detail below.
  • the first wireless device may optionally capture or otherwise obtain another alternative first timestamp at a time of arrival of the third message at the first wireless device, such as t2_2 and t2_4 of FIG. 4 , t2_1 and t2_3 of FIG. 7A , or t2_1 of FIG. 7B , which may also be used for round trip time calculation in fine timing measurement.
  • Means for performing the function at block 812 may include but are not limited to, for example, clock 1045, processing unit 1010, memory 1060, input device(s) 1070, and/or bus 1005 as illustrated in FIG. 10 .
  • means for performing the function at block 812 may include but are not limited to, for example, clock 1150, processing unit 1110, working memory 1135, and/or bus 1105 as illustrated in FIG. 11 and described in detail below.
  • the first wireless device determines that the first wireless device is not synchronized to the second wireless device, based at least in part on a difference between an initial timestamp (the first timestamp or the alternative first timestamps) and the second timestamp.
  • the determination that the first wireless device is not synchronized to the second wireless device may also be based on the round trip time between the first wireless device and the second wireless device. For example, if a difference between the first timestamp (or the alternative first timestamp) and the second timestamp is different from a half of the round trip time, the first wireless device and the second wireless device may not be synchronized.
  • Means for performing the function at block 814 may include but are not limited to, for example, processing unit 1010, memory 1060, and/or bus 1005 as illustrated in FIG. 10 .
  • means for performing the function at block 814 may include but are not limited to, for example, processing unit 1110, working memory 1135, and/or bus 1105 as illustrated in FIG. 11 and described in detail below.
  • the first wireless device in response to a determination that the first wireless device is not synchronized to the second wireless device, the first wireless device may adjust its timer or local clock. The adjustment may be based at least partially on the received second timestamp, the obtained first timestamp (or the alternative first timestamp), or the round trip time between the first wireless device and the second wireless device.
  • Means for performing the timer adjustment function may include but are not limited to, for example, clock 1045, processing unit 1010, memory 1060, input device(s) 1070, and/or bus 1005 as illustrated in FIG. 10 .
  • means for performing the timer adjustment function may include but are not limited to, for example, clock 1150, processing unit 1110, working memory 1135, and/or bus 1105 as illustrated in FIG. 11 and described in detail below.
  • FIG. 8B is a flow chart 820 illustrating an embodiment of a method of timing synchronization on a wireless device using partial timing synchronization function timestamp in an FTM frame.
  • FIG. 8B may be better understood with reference to, for example, diagram 400 of FIG. 4 , FTM session 700 of FIG. 7A , or FTM session 750 of FIG. 7B .
  • a first wireless device such as initiating STA 420 of FIG. 4 , sends a first message to a second wireless device, such as responding STA 410 of FIG. 4 .
  • the first message may be an initial FTM request frame as shown by initial FTM request 430 in FIG. 4 , or a non-initial FTM request, such as FTM request frame 438 or 450 in FIG. 4 .
  • Means for performing the function at block 822 may include but are not limited to, for example, wireless communication subsystem 1030, processing unit 1010, memory 1060, and/or bus 1005 as illustrated in FIG. 10 and described in detail below.
  • means for performing the function at block 822 may include but are not limited to, for example, wireless communications subsystem 1133, processing unit 1110, working memory 1135, and/or bus 1105 as illustrated in FIG. 11 and described in detail below.
  • the first wireless device captures or otherwise obtains a first timestamp.
  • the first wireless device may capture the first timestamp based on a local clock running on the first wireless device.
  • the first timestamp may be based on a time of departure of the first message, such as initial FTM request 430 in FIG. 4 , or a non-initial FTM request, such as FTM request frame 438 or 450 in FIG. 4 , from the first wireless device.
  • the first timestamp may be, for example, t0_0, t0_2 or t0_4 in FIG. 4 .
  • the first timestamp may also be based on a time of arrival at the first wireless device of a message (such as a fine timing measurement frame or an acknowledgment frame) from the second wireless device as described below.
  • Means for performing the function at block 824 may include but are not limited to, for example, clock 1045, processing unit 1010, memory 1060, input device(s) 1070, and/or bus 1005 as illustrated in FIG. 10 and described in detail below.
  • means for performing the function at block 824 may include but are not limited to, for example, clock 1150, processing unit 1110, working memory 1135, and/or bus 1105 as illustrated in FIG. 11 and described in detail below.
  • the first wireless device receives a fine timing measurement frame from the second wireless device in response to the first message.
  • the fine timing measurement frame may be, for example, FTM_1 434, FTM_2 442, or FTM_4 454 in FIG. 4 .
  • the fine timing measurement frame may include at least a part of a second timestamp from the second wireless device.
  • the second timestamp may be captured by the second wireless device at a time of arrival of the first message at the second wireless device, such as t0_1, t0_3, or t0_5 in FIG. 4 .
  • the second timestamp may be captured by the second wireless device at a time of departure of a fine timing measurement frame at the second wireless device, such as t1_1 or t1_3 in FIG. 7A .
  • the second timestamp may also be captured by the second wireless device at a time of departure of an acknowledgement frame at the second wireless device, such as t0_1 in FIG. 7B .
  • the second wireless device may capture the second timestamp based on a local clock running on the second wireless device.
  • Means for performing the function at block 826 may include but are not limited to, for example, wireless communication subsystem 1030, processing unit 1010, memory 1060, clock 1045, and/or bus 1005 as illustrated in FIG. 10 .
  • means for performing the function at block 826 may include but are not limited to, for example, wireless communications subsystem 1133, processing unit 1110, working memory 1135, clock 1150, and/or bus 1105 as illustrated in FIG. 11 and described in detail below.
  • the first wireless device determines that the first wireless device is not synchronized to the second wireless device based at least partially on the part of a second timestamp and the first timestamp.
  • the determination of whether the first wireless device is synchronized to the second wireless device may also be based on the round trip time between the first wireless device and the second wireless device. For example, if a difference between the first timestamp and the second timestamp is different from a half of the round trip time, the first wireless device and the second wireless device may not be synchronized.
  • Means for performing the function at block 828 may include but are not limited to, for example, processing unit 1010, memory 1060, and/or bus 1005 as illustrated in FIG. 10 . In some embodiments, means for performing the function at block 828 may include but are not limited to, for example, processing unit 1110, working memory 1135, and/or bus 1105 as illustrated in FIG. 11 and described in detail below.
  • the first wireless device in response to a determination that the first wireless device is not synchronized to the second wireless device, may adjust its timer or local clock based at least partially on the part of the second timestamp. The first wireless device may also adjust its timer or local clock based on the first timestamp or the round trip time between the first wireless device and the second wireless device.
  • Means for performing the timer adjustment function may include but are not limited to, for example, clock 1045, processing unit 1010, memory 1060, input device(s) 1070, and/or bus 1005 as illustrated in FIG. 10 .
  • means for performing the timer adjustment function may include but are not limited to, for example, clock 1150, processing unit 1110, working memory 1135, and/or bus 1105 as illustrated in FIG. 11 and described in detail below.
  • FIG. 8C is a flow chart 840 illustrating another embodiment of a method of timing synchronization on a wireless device using partial timing synchronization function timestamp in an FTM frame.
  • FIG. 8C may be better understood with reference to, for example, FTM session 750 of FIG. 7B .
  • a first wireless device such as initiating STA 770 in FIG. 7B , sends a first message to a second wireless device, such as responding STA 760.
  • the first message may be a non-initial FTM request, such as FTM request frame 780 in FIG. 7B .
  • Means for performing the function at block 842 may include but are not limited to, for example, wireless communication subsystem 1030, processing unit 1010, memory 1060, and/or bus 1005 as illustrated in FIG. 10 and described in detail below.
  • means for performing the function at block 842 may include but are not limited to, for example, wireless communications subsystem 1133, processing unit 1110, working memory 1135, and/or bus 1105 as illustrated in FIG. 11 and described in detail below.
  • the first wireless device may receive a second message from the second wireless device in response to the first message.
  • the second message may be an acknowledgement message sent by the second wireless device to the first wireless device indicating the successful reception of the first message.
  • the second message may be ACK frame 782 in FIG. 7B .
  • Means for performing the function at block 844 may include but are not limited to, for example, wireless communication subsystem 1030, processing unit 1010, memory 1060, and/or bus 1005 as illustrated in FIG. 10 and described in detail below.
  • means for performing the function at block 844 may include but are not limited to, for example, wireless communications subsystem 1133, processing unit 1110, working memory 1135, and/or bus 1105 as illustrated in FIG. 11 and described in detail below.
  • the first wireless device may obtain a first indication a time of arrival of the second message at the first wireless device, such as t0_2 shown in FIG. 7B that indicates the time of arrival of ACK frame 782 at initiating STA 770.
  • Means for performing the function at block 846 may include but are not limited to, for example, clock 1045, processing unit 1010, memory 1060, input device(s) 1070, and/or bus 1005 as illustrated in FIG. 10 and described in detail below.
  • means for performing the function at block 846 may include but are not limited to, for example, clock 1150, processing unit 1110, working memory 1135, and/or bus 1105 as illustrated in FIG. 11 and described in detail below.
  • the first wireless device receives a fine timing measurement frame, such as FTM_1 784 in FIG. 7B , from the second wireless device in response to the first message.
  • the fine timing measurement frame may include a second indication of a time of departure of the second message from the second wireless device, such as t0_1 in FIG. 7B .
  • the second wireless device may capture the second indication based on a local clock running on the second wireless device.
  • Means for performing the function at block 848 may include but are not limited to, for example, wireless communication subsystem 1030, processing unit 1010, memory 1060, clock 1045, and/or bus 1005 as illustrated in FIG. 10 .
  • means for performing the function at block 848 may include but are not limited to, for example, wireless communications subsystem 1133, processing unit 1110, working memory 1135, clock 1150, and/or bus 1105 as illustrated in FIG. 11 and described in detail below
  • the first wireless device determines that the first wireless device is not synchronized to the second wireless device, based at least partially on the first indication and the second indication.
  • the determination that the first wireless device is not synchronized to the second wireless device may also be based on the round trip time between the first wireless device and the second wireless device. For example, if a difference between the first indication and the second indication is different from a half of the round trip time, the first wireless device and the second wireless device may not be synchronized.
  • Means for performing the function at block 850 may include but are not limited to, for example, processing unit 1010, memory 1060, and/or bus 1005 as illustrated in FIG. 10 .
  • means for performing the function at block 850 may include but are not limited to, for example, processing unit 1110, working memory 1135, and/or bus 1105 as illustrated in FIG. 11 and described in detail below.
  • the first wireless device in response to a determination that the first wireless device is not synchronized to the second wireless device, may adjust its timer or local clock based at least partially on the second indication. The first wireless device may also adjust its timer or local clock based on the first indication or the round trip time between the first wireless device and the second wireless device.
  • Means for performing the timer adjustment function may include but are not limited to, for example, clock 1045, processing unit 1010, memory 1060, input device(s) 1070, and/or bus 1005 as illustrated in FIG. 10 .
  • means for performing the timer adjustment function may include but are not limited to, for example, clock 1150, processing unit 1110, working memory 1135, and/or bus 1105 as illustrated in FIG. 11 and described in detail below.
  • FIG. 8D is a flow chart 860 illustrating one embodiment of a method of timing synchronization on a wireless device using partial timing synchronization function timestamp in an FTM frame.
  • FIG. 8D may be better understood with reference to, for example, FTM session 700 of FIG. 7A .
  • a first wireless device such as initiating STA 720 of FIG. 7A , sends a first message to a second wireless device, such as responding STA 710.
  • the first message may be an initial FTM request frame, or a non-initial FTM request, such as FTM request frame 722 or 734 in FIG. 7A .
  • Means for performing the function at block 862 may include but are not limited to, for example, wireless communication subsystem 1030, processing unit 1010, memory 1060, and/or bus 1005 as illustrated in FIG. 10 and described in detail below.
  • means for performing the function at block 862 may include but are not limited to, for example, wireless communications subsystem 1133, processing unit 1110, working memory 1135, and/or bus 1105 as illustrated in FIG. 11 and described in detail below.
  • the first wireless device receives a fine timing measurement frame from the second wireless device.
  • the fine timing measurement frame may be, for example, FTM_1 726 or FTM_3 738 in FIG. 7A .
  • the fine timing measurement frame may include a first indication of a time of departure of the fine timing measurement frame from the second wireless device, such as t1_1 or t1_3 in FIG. 7A .
  • the second wireless device may capture the first indication based on a local clock running on the second wireless device.
  • Means for performing the function at block 864 may include but are not limited to, for example, wireless communication subsystem 1030, processing unit 1010, memory 1060, clock 1045, and/or bus 1005 as illustrated in FIG. 10 .
  • means for performing the function at block 864 may include but are not limited to, for example, wireless communications subsystem 1133, processing unit 1110, working memory 1135, clock 1150, and/or bus 1105 as illustrated in FIG. 11 and described in detail below
  • the first wireless device captures or otherwise obtains a second indication of a time of arrival of the fine timing measurement frame at the first wireless device, such as t2_1 or t2_3 in FIG. 7A , which may also be used for round trip time calculation in fine timing measurement.
  • Means for performing the function at block 866 may include but are not limited to, for example, clock 1045, processing unit 1010, memory 1060, input device(s) 1070, and/or bus 1005 as illustrated in FIG. 10 and described in detail below.
  • means for performing the function at block 866 may include but are not limited to, for example, clock 1150, processing unit 1110, working memory 1135, and/or bus 1105 as illustrated in FIG. 11 and described in detail below.
  • the first wireless device determines that the first wireless device is not synchronized to the second wireless device, based on the first indication and the second indication.
  • the determination that the first wireless device is not synchronized to the second wireless device may also be based on the round trip time between the first wireless device and the second wireless device. For example, if a difference between the first indication and the second indication is different from a half of the round trip time, the first wireless device and the second wireless device may not be synchronized.
  • Means for performing the function at block 868 may include but are not limited to, for example, processing unit 1010, memory 1060, and/or bus 1005 as illustrated in FIG. 10 .
  • means for performing the function at block 868 may include but are not limited to, for example, processing unit 1110, working memory 1135, and/or bus 1105 as illustrated in FIG. 11 and described in detail below.
  • the first wireless device in response to a determination that the first wireless device is not synchronized to the second wireless device, may adjust its timer or local clock based at least partially on the first indication.
  • the first wireless device may also adjust its timer or local clock based on the second indication or the round trip time between the first wireless device and the second wireless device.
  • Means for performing the timer adjustment function may include but are not limited to, for example, clock 1045, processing unit 1010, memory 1060, input device(s) 1070, and/or bus 1005 as illustrated in FIG. 10 .
  • means for performing the timer adjustment function may include but are not limited to, for example, clock 1150, processing unit 1110, working memory 1135, and/or bus 1105 as illustrated in FIG. 11 and described in detail below.
  • FIG. 9 is a flow chart 900 illustrating an embodiment of a method of timing synchronization on a responding STA using partial timing synchronization function timestamp in an FTM frame. It is noted that even though FIG. 9 describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be rearranged. An operation may have additional steps not included in the figure. Some operations may be optional, and thus may be omitted in various embodiments. Some operations described in one block may be performed together with operations at another block. Furthermore, embodiments of the methods may be implemented in hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof.
  • a second wireless device receives a first message from a first wireless device, such as a initiating STA.
  • the first message may be an initial FTM request frame, such as initial FTM request 430 in FIG. 4 , or a non-initial FTM request, such as FTM request frame 438 or 450 in FIG. 4 , FTM request frame 722 or 734 in FIG. 7A , or FTM request frame 780 in FIG. 7B .
  • means for performing the function at block 910 may include but are not limited to, for example, wireless communication subsystem 1030, processing unit 1010, memory 1060, and/or bus 1005 as illustrated in FIG. 10 and described in detail below.
  • means for performing the function at block 910 may include but are not limited to, for example, wireless communications subsystem 1133, processing unit 1110, working memory 1135, and/or bus 1105 as illustrated in FIG. 11 and described in detail below.
  • the second wireless device may send a second message to the first wireless device.
  • the second message may be an acknowledgement message sent by the second wireless device to the first wireless device indicating the successful reception of the first message.
  • the second message may be one of ACK frame 432, 440 or 452 in FIG. 4 , ACK frame 724 or 736 in FIG. 7A , or ACK frame 782 in FIG. 7B .
  • means for performing the function at block 920 may include but are not limited to, for example, wireless communication subsystem 1030, processing unit 1010, memory 1060, and/or bus 1005 as illustrated in FIG. 10 and described in detail below.
  • means for performing the function at block 920 may include but are not limited to, for example, wireless communications subsystem 1133, processing unit 1110, working memory 1135, and/or bus 1105 as illustrated in FIG. 11 and described in detail below.
  • the second wireless device obtains a timestamp.
  • the timestamp may be captured by the second wireless device at (1) a time of arrival of the first message at the second wireless device, such as t0_1, t0_3 or t0_5 in FIG. 4 ; (2) a time of departure of the second message from the second wireless device, such as t0_1 in FIG. 7B ; or ( 3 ) a time of departure of a third message to be sent by the second wireless device to the first wireless device, such as t1_1 in FIG. 7A .
  • means for performing the function at block 930 may include but are not limited to, for example, clock 1045, processing unit 1010, memory 1060, and/or bus 1005 as illustrated in FIG.
  • means for performing the function at block 930 may include but are not limited to, for example, clock 1150, processing unit 1110, working memory 1135, and/or bus 1105 as illustrated in FIG. 11 and described in detail below.
  • the second wireless device sends the third message to the first wireless device.
  • the third message includes at least a part of the timestamp obtained by the second wireless device.
  • the third message may be an FTM frame, such as, for example, FTM_1 434, FTM_2 442, or FTM_4 454 in FIG. 4 , FTM_1 726 or FTM_3 738 in FIG. 7A , or FTM_1 784 in FIG. 7B .
  • the first wireless device may determine whether the first wireless device is synchronized to the second wireless device, based at least in part on the received timestamp.
  • means for performing the function at block 940 may include but are not limited to, for example, wireless communication subsystem 1030, processing unit 1010, memory 1060, and/or bus 1005 as illustrated in FIG. 10 and described in detail below.
  • means for performing the function at block 940 may include but are not limited to, for example, wireless communications subsystem 1133, processing unit 1110, working memory 1135, and/or bus 1105 as illustrated in FIG. 11 and described in detail below.
  • FIG. 10 illustrates an embodiment of a wireless device 1000, which can be utilized as described herein above.
  • wireless device 1000 can be used as an AP and/or STA as described in relation to the embodiments previously provided herein.
  • FIG. 10 is meant only to provide a generalized illustration of various components, any or all of which may be utilized as appropriate. It can be noted that, in some instances, components illustrated by FIG. 10 can be localized to a single physical device and/or distributed among various networked devices, which may be disposed at different physical locations.
  • wireless device 1000 can be a cellular telephone or other mobile electronic device.
  • wireless device 1000 may be a stationary device, such as an AP. As such, as previously indicated, components may vary from embodiment to embodiment.
  • Wireless device 1000 is shown comprising hardware elements that can be electrically coupled via a bus 1005 (or may otherwise be in communication, as appropriate).
  • the hardware elements may include a processing unit(s) 1010 which can include without limitation one or more general-purpose processors, one or more special-purpose processors (such as digital signal processing (DSP) chips, graphics acceleration processors, application specific integrated circuits (ASICs), and/or the like), and/or other processing structure or means, which can be configured to perform one or more of the methods described herein.
  • DSP digital signal processing
  • ASICs application specific integrated circuits
  • FIG. 10 some embodiments may have a separate DSP 1020, depending on desired functionality.
  • Wireless device 1000 also can include one or more input devices 1070, which can include without limitation a touch screen, a touch pad, microphone, button(s), dial(s), switch(es), and/or the like; and one or more output devices 1015, which can include without limitation a display, light emitting diodes (LEDs), speakers, and/or the like.
  • input devices 1070 can include without limitation a touch screen, a touch pad, microphone, button(s), dial(s), switch(es), and/or the like
  • output devices 1015 which can include without limitation a display, light emitting diodes (LEDs), speakers, and/or the like.
  • LEDs light emitting diodes
  • Wireless device 1000 might also include a wireless communication subsystem 1030, which can include without limitation a modem, a network card, an infrared communication device, a wireless communication device, and/or a chipset (such as a Bluetooth device, an IEEE 802.11 device (e.g., a device utilizing one or more of the 802.11 standards described herein), an IEEE 802.15.4 device, a WiFi device, a WiMax device, cellular communication facilities, etc.), and/or the like.
  • Wireless communication subsystem 1030 may permit data to be exchanged with a network, wireless access points, other computer systems, and/or any other electronic devices described herein, such as the configuration of FIGS. 1A-1C .
  • the communication can be carried out via one or more wireless communication antenna(s) 1032 that send and/or receive wireless signals 1034.
  • wireless communication subsystem 1030 can include separate transceivers to communicate with base transceiver stations and other wireless devices and access points, which may include communicating with different data networks and/or network types, such as wireless wide-area networks (WWANs), wireless local area networks (WLANs), or wireless personal area networks (WPANs).
  • WWAN may be, for example, a Code Division Multiple Access (CDMA) network, a Time Division Multiple Access (TDMA) network, a Frequency Division Multiple Access (FDMA) network, an Orthogonal Frequency Division Multiple Access (OFDMA) network, a Single-Carrier Frequency Division Multiple Access (SC-FDMA) network, a WiMax (IEEE 1002.16), and so on.
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-Carrier Frequency Division Multiple Access
  • a CDMA network may implement one or more radio access technologies (RATs) such as cdma2000, Wideband-CDMA (W-CDMA), and so on.
  • Cdma2000 includes IS-95, IS-2000, and/or IS-856 standards.
  • a TDMA network may implement Global System for Mobile Communications (GSM), Digital Advanced Mobile Phone System (D-AMPS), or some other RAT.
  • An OFDMA network may employ LTE, LTE Advanced, and so on.
  • LTE, LTE Advanced, GSM, and W-CDMA are described in documents from 3GPP.
  • Cdma2000 is described in documents from a consortium named "3rd Generation Partnership Project 2" (3GPP2). 3GPP and 3GPP2 documents are publicly available.
  • a WLAN may be an IEEE 802.1 1x network.
  • a WPAN may be a Bluetooth network, an IEEE 802.15x, or some other type of network. The techniques described herein may also be used for any combination of WWAN, WLAN and/or WPAN.
  • Wireless device 1000 may include a clock 1045 on bus 1005, which can generate a signal to synchronize various components on bus 1005.
  • Clock 1045 may include an inductor-capacitor (LC) oscillator, a crystal oscillator, a ring oscillator, a digital clock generator such as a clock divider or clock multiplexer, a phase locked loop, or other clock generator. As indicated previously, the clock may be synchronized (or substantially synchronized) with corresponding clocks on other wireless devices.
  • Clock 1045 may be driven by wireless communication interface 1030, which may be used to synchronize clock 1045 of wireless device 1000 to one or more other devices.
  • Wireless device 1000 can further include sensor(s) 1040.
  • sensors can include, without limitation, one or more accelerometer(s), gyroscope(s), camera(s), magnetometer(s), altimeter(s), microphone(s), proximity sensor(s), light sensor(s), and the like.
  • sensor(s) 1040 can be utilized, among other things, for dead reckoning and/or other positioning methods. Such positioning methods may be used to determine a location of wireless device 1000, and may utilize and/or complement the RTT values obtained using FTM techniques described herein.
  • Embodiments of the mobile device may also include a Standard Positioning Service (SPS) receiver 1080 capable of receiving signals 1084 from one or more SPS satellites using an SPS antenna 1082. Such positioning can be utilized to complement and/or incorporate the techniques for calculating RTT described herein.
  • SPS receiver 1080 can extract a position of the mobile device, using conventional techniques, from SPS satellite vehicles (SVs) of an SPS system, such as global navigation satellite system (GNSS) (e.g., Global Positioning System (GPS)), Galileo, Glonass, Compass, Quasi-Zenith Satellite System (QZSS) over Japan, Indian Regional Navigational Satellite System (IRNSS) over India, Beidou over China, and/or the like.
  • GNSS global navigation satellite system
  • GPS Global Positioning System
  • Galileo Galileo
  • Glonass Galileo
  • Glonass Galileo
  • Glonass Compass
  • QZSS Quasi-Zenith
  • SPS receiver 1080 can use various augmentation systems (e.g., a Satellite Based Augmentation System (SBAS)) that may be associated with or otherwise enabled for use with one or more global and/or regional navigation satellite systems.
  • SBAS Satellite Based Augmentation System
  • an SBAS may include an augmentation system(s) that provides integrity information, differential corrections, etc., such as, e.g., Wide Area Augmentation System (WAAS), European Geostationary Navigation Overlay Service (EGNOS), Multi -functional Satellite Augmentation System (MSAS), GPS Aided Geo Augmented Navigation or GPS and Geo Augmented Navigation system (GAGAN), and/or the like.
  • WAAS Wide Area Augmentation System
  • EGNOS European Geostationary Navigation Overlay Service
  • MSAS Multi -functional Satellite Augmentation System
  • GPS Aided Geo Augmented Navigation or GPS and Geo Augmented Navigation system (GAGAN) GPS Aided Geo Augmented Navigation or GPS and Geo Augmented Navigation system (GAGAN), and/or the like.
  • Wireless device 1000 may further include and/or be in communication with a memory 1060.
  • Memory 1060 can include, without limitation, local and/or network accessible storage, a disk drive, a drive array, an optical storage device, a solid-state storage device, such as a random access memory (“RAM”), and/or a read-only memory (“ROM”), which can be programmable, flash-updateable, and/or the like.
  • RAM random access memory
  • ROM read-only memory
  • Such storage devices may be configured to implement any appropriate data stores, including without limitation, various file systems, database structures, and/or the like.
  • Memory 1060 of wireless device 1000 also can comprise software elements (not shown), including an operating system, device drivers, executable libraries, and/or other code, such as one or more application programs, which may comprise computer programs provided by various embodiments, and/or may be designed to implement methods, and/or configure systems, provided by other embodiments, as described herein.
  • one or more procedures described with respect to the functionality discussed above, such as the methods shown in FIGS. 8 and/or 9 might be implemented as code and/or instructions executable by wireless device 1000, a processing unit within wireless device 1000, and/or another device of a wireless system.
  • code and/or instructions can be used to configure and/or adapt a general purpose computer (or other device) to perform one or more operations in accordance with the described methods.
  • FIG. 11 illustrates components of a computing system 1100, according to one embodiment.
  • computing system 1100 can be used as an AP as described in relation to the embodiments previously provided herein, and may communicate in a wireless communication system with one or more STAs, as previously discussed.
  • wireless device 1000 of FIG. 10 which may be mobile
  • computing system 1100 of FIG. 11 may, for example, be a stationary device (or set of devices).
  • FIG. 11 is meant only to provide a generalized illustration of various components, any or all of which may be utilized as appropriate.
  • system elements may be implemented in a relatively separated or relatively more integrated manner.
  • Computing system 1100 is shown comprising hardware elements that can be electrically coupled via a bus 1105 (or may otherwise be in communication, as appropriate).
  • the hardware elements may include a processing unit 1110, including without limitation one or more general-purpose processors and/or one or more special-purpose processors (such as digital signal processing chips, graphics acceleration processors, and/or the like), one or more input devices 1115, and one or more output devices 1120.
  • Input device(s) 1115 can include without limitation camera(s), a touchscreen, a touch pad, microphone(s), a keyboard, a mouse, button(s), dial(s), switch(es), and/or the like.
  • Output devices 1120 may include without limitation a display device, a printer, light emitting diodes (LEDs), speakers, and/or the like.
  • LEDs light emitting diodes
  • Computing system 1100 can also include a wired communications subsystem 1130 and wireless communication technologies managed and controlled by a wireless communication subsystem 1133.
  • wired communications subsystem 1130 and wireless communications subsystem 1133 can include, without limitation, a modem, a network interface (wireless, wired, both, or other combination thereof), an infrared communication device, a wireless communication device, and/or a chipset (such as a BluetoothTM device, an IEEE 802.11 device (e.g., a device utilizing one or more of the IEEE 802.11 standards described herein), a WiFi device, a WiMax device, cellular communication facilities, etc.), and/or the like.
  • a modem can include, without limitation, a modem, a network interface (wireless, wired, both, or other combination thereof), an infrared communication device, a wireless communication device, and/or a chipset (such as a BluetoothTM device, an IEEE 802.11 device (e.g., a device utilizing one or more of the IEEE
  • Wired communications subsystem 1130 and wireless communications subsystem 1133 may include one or more input and/or output communication interfaces to permit data to be exchanged with a data network, other computer systems, and/or any other devices described herein.
  • wired communications subsystem 1130 and/or wireless communications subsystem 1133 may permit computing system 1100 to determine RTT via uplink (UL) multiple-input multiple-output (MIMO) processes.
  • UL uplink
  • MIMO multiple-input multiple-output
  • computer system 1100 of FIG. 11 may include a clock 1150 on bus 1105, which can generate a signal to synchronize the various components on bus 1105.
  • Clock 1150 may include an LC oscillator, a crystal oscillator, a ring oscillator, a digital clock generator such as a clock divider or clock multiplexer, a phase locked loop, or other clock generator.
  • the clock may be synchronized (or substantially synchronized) with corresponding clocks on other wireless devices while performing the techniques described herein.
  • Clock 1150 may be driven by wireless communication subsystem 1133, which may be used to synchronize clock 1150 of computer system 1100 to one or more other devices.
  • Computing system 1100 may further include (and/or be in communication with) one or more non-transitory storage devices 1125, which can comprise, without limitation, local and/or network accessible storage, and/or can include, without limitation, a disk drive, a drive array, an optical storage device, a solid-state storage device, such as a random access memory (“RAM”), and/or a read-only memory (“ROM”), which can be programmable, flash-updateable and/or the like.
  • RAM random access memory
  • ROM read-only memory
  • Such storage devices may be configured to implement any appropriate data stores, including without limitation, various file systems, database structures, and/or the like.
  • storage device(s) 1125 may include a database 1127 (or other data structure) configured to store timestamp values as described in embodiments herein, which may be provided to APs and/or other devices via wired communications subsystem 1130 or wireless communications subsystem 1133.
  • database 1127 or other data structure
  • timestamp values as described in embodiments herein, which may be provided to APs and/or other devices via wired communications subsystem 1130 or wireless communications subsystem 1133.
  • computing system 1100 may further comprise a working memory 1135, which can include a RAM or ROM device, as described above.
  • Software elements shown as being currently located within working memory 1135, can include an operating system 1140, device drivers, executable libraries, and/or other code, such as one or more application programs 1145, which may comprise software programs provided by various embodiments, and/or may be designed to implement methods, and/or configure systems, provided by other embodiments, as described herein, such as some or all of the methods described in relation to FIGS. 2-9 .
  • one or more procedures described with respect to the method(s) discussed above might be implemented as code and/or instructions executable by a computer (and/or a processor within a computer).
  • code and/or instructions can be used to configure and/or adapt a general purpose computer (or other device) to perform one or more operations in accordance with the described methods.
  • a set of these instructions and/or code might be stored on a non-transitory computer-readable storage medium, such as non-transitory storage device(s) 1125 described above.
  • the storage medium might be incorporated within a computer system, such as computing system 1100.
  • the storage medium might be separate from a computer system (e.g., a removable medium, such as a flash drive), and/or provided in an installation package, such that the storage medium can be used to program, configure, and/or adapt a general purpose computer with the instructions/code stored thereon.
  • These instructions might take the form of executable code, which is executable by computing system 1100 and/or might take the form of source and/or installable code, which, upon compilation and/or installation on computing system 1100 (e.g., using any of a variety of generally available compilers, installation programs, compression/decompression utilities, etc.), then takes the form of executable code.
  • components that can include memory can include non-transitory machine-readable media.
  • machine-readable medium and “computer-readable medium” as used herein, refer to any storage medium that participates in providing data that causes a machine to operate in a specific fashion.
  • various machine-readable media might be involved in providing instructions/code to processing units and/or other device(s) for execution. Additionally or alternatively, the machine-readable media might be used to store and/or carry such instructions/code.
  • a computer-readable medium is a physical and/or tangible storage medium. Such a medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media.
  • Computer-readable media include, for example, magnetic and/or optical media, punch cards, paper tape, any other physical medium with patterns of holes, a RAM, a PROM, EPROM, a FLASH-EPROM, any other memory chip or cartridge, a carrier wave as described hereinafter, or any other medium from which a computer can read instructions and/or code.
  • a special purpose computer or a similar special purpose electronic computing device is capable of manipulating or transforming signals, typically represented as physical electronic, electrical, or magnetic quantities within memories, registers, or other information storage devices, transmission devices, or display devices of the special purpose computer or similar special purpose electronic computing device.
  • the term "at least one of' if used to associate a list, such as A, B, or C, can be interpreted to mean any combination of A, B, and/or C, such as A, AB, AA, AAB, AABBCCC, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Synchronisation In Digital Transmission Systems (AREA)

Claims (15)

  1. Procédé (820) de synchronisation temporelle entre un premier dispositif sans fil (420) et un deuxième dispositif sans fil (410), le procédé comprenant les étapes suivantes :
    l'envoi, par le premier dispositif sans fil, d'un premier message (430) au deuxième dispositif sans fil ;
    l'obtention (824), par le premier dispositif sans fil, d'un premier horodatage au niveau du premier dispositif sans fil ;
    la réception (826), par le premier dispositif sans fil, d'une trame de mesure de temps fine (434) en provenance du deuxième dispositif sans fil en réponse au premier message, la trame de mesure de temps fine comportant au moins une partie d'un deuxième horodatage provenant du deuxième dispositif sans fil, dans lequel le deuxième horodatage correspond à une valeur de minuteur de fonction de synchronisation temporelle, TSF, destinée à une synchronisation avec le deuxième dispositif sans fil ; et
    la synchronisation du premier dispositif sans fil avec le deuxième dispositif sans fil, en réponse à la détermination (828) que le premier dispositif sans fil n'est pas synchronisé avec le deuxième dispositif sans fil sur la base, au moins en partie, de la partie du deuxième horodatage et du premier horodatage.
  2. Procédé (820) selon la revendication 1, dans lequel la synchronisation du premier dispositif sans fil (420) avec le deuxième dispositif sans fil (410) comporte en outre l'étape suivante :
    le réglage d'une horloge sur le premier dispositif sans fil sur la base, au moins en partie, de la partie du deuxième horodatage.
  3. Procédé (820) selon la revendication 1, dans lequel le premier message (430) est une trame de requête de mesure de temps fine.
  4. Procédé (820) selon la revendication 1, dans lequel :
    le premier horodatage est basé sur un instant de départ du premier message (430) à partir du premier dispositif sans fil (420) ; et
    le deuxième horodatage est basé sur un instant d'arrivée du premier message au niveau du deuxième dispositif sans fil (410) .
  5. Procédé (820) selon la revendication 1, comprenant en outre l'étape suivante :
    la réception, par le premier dispositif sans fil (420), d'un deuxième message en provenance du deuxième dispositif sans fil (410) en réponse au premier message,
    dans lequel le premier horodatage est basé sur un instant d'arrivée du deuxième message au niveau du premier dispositif sans fil ; et
    dans lequel le deuxième horodatage est basé sur un instant de départ du deuxième message à partir du deuxième dispositif sans fil.
  6. Procédé (820) selon la revendication 5, dans lequel le deuxième message est une trame d'accusé de réception.
  7. Procédé (820) selon la revendication 1, dans lequel :
    le premier horodatage est basé sur un instant d'arrivée de la trame de mesure de temps fine au niveau du premier dispositif sans fil ; et
    dans lequel le deuxième horodatage est basé sur un instant de départ de la trame de mesure de temps fine à partir du deuxième dispositif sans fil.
  8. Procédé (820) selon la revendication 1, dans lequel la trame de mesure de temps fine comporte un parmi 2, 3, 4, 5 ou 8 octets du deuxième horodatage.
  9. Procédé (820) selon la revendication 1, dans lequel la trame de mesure de temps fine comporte un bit réservé indiquant que des informations d'horodatage sont présentes dans la trame de mesure de temps fine.
  10. Procédé (820) selon la revendication 1, dans lequel la détermination que le premier dispositif sans fil (420) n'est pas synchronisé avec le deuxième dispositif sans fil (410) est en outre basée sur un temps d'aller-retour entre le premier dispositif sans fil et le deuxième dispositif sans fil.
  11. Support de stockage lisible par ordinateur non transitoire comportant des instructions lisibles par machine stockées sur celui-ci pour synchroniser un premier dispositif sans fil (420) avec un deuxième dispositif sans fil (410), les instructions, quand elles sont exécutées par un ou plusieurs processeurs, forçant le premier dispositif sans fil à mettre en oeuvre les étapes selon l'une quelconque des revendications 1 à 9.
  12. Appareil comprenant :
    des moyens pour envoyer un premier message (430) à partir d'un premier dispositif sans fil (430) à un deuxième dispositif sans fil (410) ;
    des moyens pour capturer un premier horodatage au niveau du premier dispositif sans fil ;
    des moyens pour recevoir une trame de mesure de temps fine (434) en provenance du deuxième dispositif sans fil en réponse au premier message, la trame de mesure de temps fine comportant au moins une partie d'un deuxième horodatage en provenance du deuxième dispositif sans fil, dans lequel le deuxième horodatage correspond à une valeur de minuteur de fonction de synchronisation temporelle, TSF, destinée à une synchronisation avec le deuxième dispositif sans fil ; et
    des moyens pour synchroniser le premier dispositif sans fil avec le deuxième dispositif sans fil, en réponse à la détermination que le premier dispositif sans fil n'est pas synchronisé avec le deuxième dispositif sans fil sur la base, au moins en partie, de la partie du deuxième horodatage et du premier horodatage.
  13. Appareil selon la revendication 12, dans lequel les moyens pour synchroniser le premier dispositif sans fil (420) avec le deuxième dispositif sans fil (410) comportent :
    des moyens pour régler une horloge sur le premier dispositif sans fil sur la base, au moins en partie, de la partie du deuxième horodatage.
  14. Appareil selon la revendication 12, dans lequel :
    le premier horodatage est basé sur un instant de départ du premier message à partir du premier dispositif sans fil ; et
    le deuxième horodatage est basé sur un instant d'arrivée du premier message au niveau du deuxième dispositif sans fil.
  15. Appareil selon la revendication 12, comprenant en outre :
    des moyens pour recevoir un deuxième message en provenance du deuxième dispositif sans fil (410) en réponse au premier message,
    dans lequel le premier horodatage est basé sur un instant d'arrivée du deuxième message au niveau du premier dispositif sans fil (420) ;
    dans lequel le deuxième horodatage est basé sur un instant de départ du deuxième message à partir du deuxième dispositif sans fil ; et
    dans lequel le deuxième message est une trame d'accusé de réception.
EP16748381.7A 2015-08-10 2016-07-08 Synchronisation partielle de fonction de synchronisation de base de temps (tsf) dans un protocole de mesure de base de temps fine (ftm) Active EP3335481B1 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US201562203306P 2015-08-10 2015-08-10
US15/065,696 US9668101B2 (en) 2015-08-10 2016-03-09 Partial timing synchronization function (TSF) synchronization in fine timing measurement (FTM) protocol
PCT/US2016/041593 WO2017027140A1 (fr) 2015-08-10 2016-07-08 Synchronisation partielle de fonction de synchronisation de base de temps (tsf) dans un protocole de mesure de base de temps fine (ftm)

Publications (2)

Publication Number Publication Date
EP3335481A1 EP3335481A1 (fr) 2018-06-20
EP3335481B1 true EP3335481B1 (fr) 2020-08-26

Family

ID=56616017

Family Applications (1)

Application Number Title Priority Date Filing Date
EP16748381.7A Active EP3335481B1 (fr) 2015-08-10 2016-07-08 Synchronisation partielle de fonction de synchronisation de base de temps (tsf) dans un protocole de mesure de base de temps fine (ftm)

Country Status (9)

Country Link
US (1) US9668101B2 (fr)
EP (1) EP3335481B1 (fr)
JP (1) JP6457148B2 (fr)
KR (1) KR101895378B1 (fr)
CN (1) CN107925974B (fr)
AU (1) AU2016307332B2 (fr)
ES (1) ES2828023T3 (fr)
TW (1) TWI736545B (fr)
WO (1) WO2017027140A1 (fr)

Families Citing this family (29)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6634694B2 (ja) * 2014-06-06 2020-01-22 ソニー株式会社 情報処理装置、情報処理方法およびプログラム
US10009430B2 (en) * 2015-08-27 2018-06-26 Intel IP Corporation Apparatus, system and method of fine timing measurement (FTM)
CN106936559B (zh) * 2015-12-29 2020-01-31 华为技术有限公司 一种精细时间测量ftm方法和通信设备
US10405139B2 (en) * 2016-05-31 2019-09-03 Mediatek Inc. Portable electronic devices with an emergency mode for locating survivors in disasters
US10345883B2 (en) * 2016-05-31 2019-07-09 Taiwan Semiconductor Manufacturing Co., Ltd. Power estimation
US10757675B2 (en) 2016-06-03 2020-08-25 Locix, Inc. Systems and methods for precise radio frequency localization in the presence of multiple communication paths
US10470156B2 (en) 2016-06-03 2019-11-05 Locix, Inc. Systems and methods for coarse and fine time of flight estimates for precise radio frequency localization in the presence of multiple communication paths
US10455350B2 (en) 2016-07-10 2019-10-22 ZaiNar, Inc. Method and system for radiolocation asset tracking via a mesh network
US20180049130A1 (en) * 2016-08-12 2018-02-15 Po-Kai Huang Synchronization for wake-up radio
US10666628B2 (en) * 2017-08-04 2020-05-26 Apple Inc. Secure authentication of device identification for low throughput device to-device wireless communication
US10568064B2 (en) 2017-08-23 2020-02-18 Locix, Inc. Systems and methods for precise radio frequency localization using time difference of arrival
US10605889B2 (en) 2017-08-23 2020-03-31 Locix, Inc. Systems and methods for precise radio frequency localization using time sweep time difference of arrival
US20190089472A1 (en) * 2017-09-18 2019-03-21 Qualcomm Incorporated Audio synchronization over wlan
AU2019235617B2 (en) * 2018-03-14 2022-10-20 Locata Corporation Pty Ltd Method and apparatus for synchronising a location network
CN110649983B (zh) * 2018-06-26 2021-08-03 华为技术有限公司 一种同步方法及装置
EP4221265A1 (fr) * 2018-09-28 2023-08-02 Apple Inc. Partage de contenu sur la base de la proximité
US11412466B2 (en) * 2018-10-26 2022-08-09 Qualcomm Incorporated Synchronization in access point (AP) coordination
WO2020089962A1 (fr) * 2018-10-29 2020-05-07 三菱電機株式会社 Système de synchronisation temporelle, maître de temps, maître de gestion et procédé de synchronisation temporelle
US11327147B2 (en) 2018-12-26 2022-05-10 Locix, Inc. Systems and methods for determining locations of wireless sensor nodes based on anchorless nodes and known environment information
US11044160B2 (en) 2019-03-22 2021-06-22 Cisco Technology, Inc. Location-aware policy exchange
US10735900B1 (en) 2019-05-06 2020-08-04 Apple Inc. Ranging measurements for spatially-aware user interface of a mobile device
US11304031B2 (en) * 2019-10-10 2022-04-12 Samsung Electronics Co., Ltd. Wireless local area network system, method of transmitting distance information and measuring distance of wireless local area network system
CN112986972A (zh) * 2019-12-13 2021-06-18 华为技术有限公司 探测物体位置的方法和装置
US11968638B2 (en) * 2021-05-07 2024-04-23 Cisco Technology, Inc. Providing a clock value to a client device
US20230087308A1 (en) * 2021-09-22 2023-03-23 Cisco Technology, Inc. Timing measurement (tm)/fine timing measurement (ftm) for ranging and timing
US12526757B2 (en) 2021-11-26 2026-01-13 Electronics And Telecommunications Research Institute Method and apparatus for synchronizing timeslot in wireless local area network system
US11700590B1 (en) 2021-12-20 2023-07-11 Cisco Technology, Inc. Mobile time-sync distribution
EP4520111A1 (fr) * 2022-05-06 2025-03-12 Cognitive Systems Corp. Systèmes et procédés de synchronisation temporelle de transmissions de détection effectuées par des stations non associées
US20250071707A1 (en) * 2023-08-22 2025-02-27 Qualcomm Incorporated Extended personal area network time synchronization between a wireless communication device and a peripheral device

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012026935A1 (fr) * 2010-08-26 2012-03-01 Thomson Licensing Utilisation d'espace blanc pour dispositifs de réseau local sans fil

Family Cites Families (28)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2006270248A (ja) * 2005-03-22 2006-10-05 Sharp Corp パケット通信装置、パケット往復時間測定プログラムおよび記録媒体
US8023976B2 (en) * 2007-05-03 2011-09-20 Samsung Electronics Co., Ltd. Method and system for accurate clock synchronization for communication networks
JP4810520B2 (ja) * 2007-09-21 2011-11-09 日本電信電話株式会社 クライアント装置および同期システム
CN102111380B (zh) * 2009-12-25 2014-05-07 华为技术有限公司 一种时间同步的方法、设备及系统
JP2011176768A (ja) * 2010-02-25 2011-09-08 Nippon Telegr & Teleph Corp <Ntt> プッシュ型時刻配信装置、時刻同期サーバおよび時刻同期クライアント
US8654758B2 (en) * 2010-04-16 2014-02-18 Simmonds Precision Products, Inc. Synchronization within wireless devices
CN102447553A (zh) * 2010-10-12 2012-05-09 研祥智能科技股份有限公司 一种精确时间同步协议的实现装置
US9182493B2 (en) 2011-03-11 2015-11-10 Texas Instruments Incorporaed Fine time assistance for global navigation satellite systems
CN102244572B (zh) * 2011-07-18 2017-06-06 中兴通讯股份有限公司 一种实现时钟同步的方法及装置
US20140073352A1 (en) 2012-09-11 2014-03-13 Qualcomm Incorporated Method for precise location determination
EP2952046B1 (fr) * 2013-01-31 2017-01-25 Marvell World Trade Ltd. Compensation de décalage de fréquence destinée à la télémétrie wifi
US9191908B2 (en) * 2013-03-05 2015-11-17 Qualcomm Incorporated Reducing impact of clock drift in wireless devices
US10292103B2 (en) 2013-03-27 2019-05-14 Qualcomm Incorporated Systems and methods for synchronization within a neighborhood aware network
KR101638461B1 (ko) 2013-04-05 2016-07-11 인텔 코포레이션 802.11ah에서 제어 프레임에 대한 효율 개선 방법
US9426261B2 (en) 2013-05-15 2016-08-23 Qualcomm Incorporated Apparatus and methods for improved frames
US9591493B2 (en) * 2013-08-19 2017-03-07 Broadcom Corporation Wireless communication fine timing measurement PHY parameter control and negotiation
WO2015030339A1 (fr) * 2013-08-29 2015-03-05 엘지전자 주식회사 Procédé et appareil permettant de communiquer des informations relatives à une trame d'échec de transmission
US9661603B2 (en) 2013-08-30 2017-05-23 Qualcomm Incorporated Passive positioning utilizing beacon neighbor reports
JP6165985B2 (ja) * 2013-09-13 2017-07-19 インテル コーポレイション 飛行時間ウィンドウの制限同期
US10018704B2 (en) * 2013-10-17 2018-07-10 Mediatek Singapore Pte. Ltd. Snooping sensor STA or neighbor AP ranging and positioning in wireless local area networks
US9854547B2 (en) * 2013-11-12 2017-12-26 Marvell World Trade Ltd. Method and apparatus for synchronizing timing among devices in a wireless local area network (WLAN)
US9320010B2 (en) * 2013-12-24 2016-04-19 Intel Corporation Apparatus, system and method of estimating a location of a mobile device
GB2518921B (en) * 2014-03-24 2016-02-17 Imagination Tech Ltd High definition timing synchronisation function
US9819750B2 (en) * 2014-06-03 2017-11-14 Qualcomm Incorporated Neighbor aware network cluster topology establishment based on proximity measurements
US9769626B2 (en) * 2014-06-16 2017-09-19 Mediatek Singapore Pte. Ltd. Fine timing measurement positioning and improvements in wireless local area networks
US9826418B2 (en) * 2014-09-22 2017-11-21 Intel Corporation Apparatus, system and method of performing a time of flight (ToF) measurement
US9585080B2 (en) * 2014-12-23 2017-02-28 Intel Corporation Techniques for conducting fine timing measurements
US9689961B2 (en) * 2015-03-26 2017-06-27 Intel IP Corporation Apparatus, system and method of communication between wireless networks having different coordinate domains

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012026935A1 (fr) * 2010-08-26 2012-03-01 Thomson Licensing Utilisation d'espace blanc pour dispositifs de réseau local sans fil

Also Published As

Publication number Publication date
KR101895378B1 (ko) 2018-09-07
WO2017027140A1 (fr) 2017-02-16
EP3335481A1 (fr) 2018-06-20
ES2828023T3 (es) 2021-05-25
JP6457148B2 (ja) 2019-01-23
CN107925974A (zh) 2018-04-17
TWI736545B (zh) 2021-08-21
US9668101B2 (en) 2017-05-30
AU2016307332A1 (en) 2018-02-01
US20170048671A1 (en) 2017-02-16
BR112018002561A2 (pt) 2018-09-18
CN107925974B (zh) 2019-05-17
JP2018523416A (ja) 2018-08-16
TW201709761A (zh) 2017-03-01
KR20180030585A (ko) 2018-03-23
AU2016307332B2 (en) 2019-03-14

Similar Documents

Publication Publication Date Title
EP3335481B1 (fr) Synchronisation partielle de fonction de synchronisation de base de temps (tsf) dans un protocole de mesure de base de temps fine (ftm)
EP3394632B1 (fr) Format de trame de temps de départ (tod) de diffusion
US20180310133A1 (en) Wireless network positioning
EP3417638B1 (fr) Techniques pour une session de télémétrie infinie
US20250039828A1 (en) Time alignment configuration for hybrid cellular and uwb positioning
WO2020046483A1 (fr) Procédés et systèmes de détermination d&#39;emplacement d&#39;un dispositif mobile à l&#39;aide de bandes rf partielles
EP4298806A1 (fr) Télémétrie de liaison latérale pour positionner des types de signaux de référence
KR102344808B1 (ko) 라운드 트립 시간 결정
EP3777296B1 (fr) Orthogonalité et encapsulation pour signaux de positionnement et de navigation
US20160014711A1 (en) Round trip time (rtt) determination
BR112018002561B1 (pt) Método de sincronização de temporização entre um primeirodispositivo sem fio e um segundo dispositivo sem fio, memória legível porcomputador e equipamento

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20180112

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20190614

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 56/00 20090101AFI20200214BHEP

Ipc: H04W 4/02 20180101ALI20200214BHEP

INTG Intention to grant announced

Effective date: 20200318

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1307638

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200915

Ref country code: CH

Ref legal event code: NV

Representative=s name: MAUCHER JENKINS PATENTANWAELTE AND RECHTSANWAE, DE

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602016042771

Country of ref document: DE

REG Reference to a national code

Ref country code: NL

Ref legal event code: FP

REG Reference to a national code

Ref country code: SE

Ref legal event code: TRGR

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201127

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200826

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201228

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201126

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200826

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200826

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201126

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1307638

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200826

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200826

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200826

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200826

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201226

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200826

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200826

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200826

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200826

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200826

REG Reference to a national code

Ref country code: ES

Ref legal event code: FG2A

Ref document number: 2828023

Country of ref document: ES

Kind code of ref document: T3

Effective date: 20210525

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602016042771

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200826

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200826

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200826

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20210527

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200826

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200826

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20210731

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210708

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210708

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210731

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20160708

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200826

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200826

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200826

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20250612

Year of fee payment: 10

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: NL

Payment date: 20250618

Year of fee payment: 10

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20250612

Year of fee payment: 10

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: ES

Payment date: 20250814

Year of fee payment: 10

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20250616

Year of fee payment: 10

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: IT

Payment date: 20250714

Year of fee payment: 10

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: SE

Payment date: 20250708

Year of fee payment: 10

Ref country code: CH

Payment date: 20250801

Year of fee payment: 10

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200826