Doc.: IEEE 802.11-07/2229r0 Submission July 2007 R. Roy, SRASlide 1 Timing Reference Information Element Proposal Notice: This document has been prepared.

Slides:



Advertisements
Similar presentations
Doc.: IEEE /1672 STA Provided Location November 2006 Donghee Shim, et alSlide 1 STA Provided Location Notice: This document has been prepared.
Advertisements

Doc.: IEEE /0049r0 Submission January 2007 Matthew Fischer, BroadcomSlide 1 Signaling of intolerance for 40 MHz transmissions Notice: This document.
Doc.: IEEE /0256r0 Submission February 2007 A. Centonza, D. StephensonSlide 1 Limitations on the Use of EBR Notice: This document has been prepared.
Doc.: IEEE /0866r1 Submission September 2005 Michael Montemurro, Chantry NetworksSlide 1 Mobility Domain Definition and Description Notice: This.
November 2005 Floyd Simpson, MotorolaSlide 1 doc.: IEEE /1193r0 Submission LB78 D3.0 Active Scanning Comments (clause ) Notice: This.
Doc.: IEEE /90r0 Submission Nov., 2012 NICTSlide b NICT Proposal IEEE P Wireless RANs Date: Authors: Notice: This document.
Doc.: IEEE /0930r0 Submission July 2006 Nancy Cam-Winget, Cisco Slide 1 Editor Updates since Jacksonville Notice: This document has been prepared.
Doc.: IEEE /0763r1 Submission July, 2008 Hu JunlingSlide 1 Location Coordinates Inquiry Notice: This document has been prepared to assist IEEE.
Doc.: IEEE /0644r2 Submission May 2006 Päivi Ruuska, NokiaSlide 1 Measurement Pilot Transmission Information as optional information in Probe.
Doc.: IEEE /2215r1 Submission July 2007 Ganesh Venkatesan, Intel CorporationSlide 1 Proposal – Supported Radio Resource Measurement Bitmask IE.
Doc.: IEEE /0217r0 Submission March 2005 Jason Liu and Justin McNew, TechnoComSlide 1 WRSS Discussions Notice: This document has been prepared.
Doc.: IEEE /2219r2 Submission July 2007 Stephenson & CanpolatSlide 1 Venue Type and Name Assisted Network Selection Date: Notice: This.
Doc.: IEEE /1219r2 Submission January, 2006 S. Ponnuswamy (Aruba Networks)Slide 1 Virtual AP Presentation Notice: This document has been prepared.
Doc.: IEEE /0408r0 Submission May 2005 John Klein, SymbolSlide 1 TPC Comments Notice: This document has been prepared to assist IEEE It.
November 2005doc.: IEEE /1079r0 Stuart GoldenNovember Notice: This document has been prepared to assist IEEE It is offered as a.
Doc.: IEEE /0041r1 AP Location Capability January 2007 Donghee Shim et alSlide 1 AP Location Capability Notice: This document has been prepared.
Doc.: IEEE /86r2 Submission March, 2010 Gabor BajkoSlide 1 Location Proxy Notice: This document has been prepared to assist IEEE It is.
Doc.: IEEE /1219r4 Submission March, 2006 S. Ponnuswamy (Aruba Networks)Slide 1 Virtual AP Presentation Notice: This document has been prepared.
Doc.: IEEE /0xxxr0 Submission July, 2008 Hu JunlingSlide 1 Location Coordinates Inquiry Notice: This document has been prepared to assist IEEE.
Doc.: IEEE /0039r1 Submission January 2007 Larry Green, Ixia Slide 1 TCP Parameters and Settings Notice: This document has been prepared to assist.
Doc.: IEEE /0460r1 Submission March 2006 Fujio Watanabe, DoCoMo USA LabsSlide 1 Japanese Emergency Call Regulation Notice: This document has been.
Doc.: IEEE /0136r0 Submission January 2007 Dave Stephenson, Cisco Systems, Inc.Slide 1 Input to Information Model Date: Notice:
Doc.: IEEE /0477r0 Submission March 2007 C. Wright, AzimuthSlide 1 Proposal for fixing additional issues in some subclauses Notice: This document.
Doc.: IEEE /0652r1 Submission May 2007 Emily Qi, Intel CorporationSlide 1 TGv Redline D0.12 Insert and Deletion Notice: This document has been.
Doc.: IEEE /0583r0 Submission May 2005 Simon Black et al, NokiaSlide 1 STA receiver performance indication Notice: This document has been prepared.
Beacon Measurement on Pilot Frames
Channel Switch Announcement with Extension
[ Interim Meetings 2006] Date: Authors: July 2005
Resource Request/Response Discussion
LB73 Noise and Location Categories
LB73 Noise and Location Categories
Waveform Generator Source Code
TGp Closing Report Date: Authors: July 2007 Month Year
Attendance and Documentation for the March 2007 Plenary
Motion to accept Draft p 2.0
Protected SSIDs Date: Authors: March 2005 March 2005
[place presentation subject title text here]
WAVE without beacons Date: Authors: May 2007 Month Year
On Coexistence Mechanisms
TGp Closing Report Date: Authors: May 2007 Month Year
AP Location Capability
On Coexistence Mechanisms
Reflector Tutorial Date: Authors: July 2006 Month Year
CID#102 - Channel Allocation for P2P
TGv Redline D0.07 Insert and Deletion
TGv Redline D0.06 Insert and Deletion
Congestion control timer
Proposal for Resolving Comments on Intra-Mesh Congestion Control
IEEE P Wireless RANs Date:
Protection Assurance Method
TGu-changes-from-d0-01-to-d0-02
LB73 Noise and Location Categories
Extended Channel Switch Announcements
Air Efficiency and Reliability Enhancements for Multicast
TGy draft 2.0 with changebars from draft 1.0
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
Updates to assigned numbers
WAVE without beacons Date: Authors: May 2007 Month Year
Signalling Multicast Group in PSMP frame
Off-channel selection
Extended Channel Switch Announcement for TGn
Signalling Multicast Group in PSMP frame
Questions to the Contention-based Protocol (CBP) Study Group
Air Efficiency and Reliability Enhancements for Multicast
EC Motions – July 2005 Plenary
Location Capability Negotiation
STC with CSI feedback IEEE P Wireless LANs Date:
Use of More Data Field Date: Authors: Nov 2005 Month Year
Non-AP STA Location Capability
WAPI Position Paper Sept 2005 Sept 2005 IEEE WG
Presentation transcript:

doc.: IEEE /2229r0 Submission July 2007 R. Roy, SRASlide 1 Timing Reference Information Element Proposal Notice: This document has been prepared to assist IEEE It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Release: The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures, including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE Working Group. If you have questions, contact the IEEE Patent Committee Administrator at. ieee802.org/guides/bylaws/sb-bylaws.pdf Date: Authors:

doc.: IEEE /2229r0 Submission July 2007 R. Roy, SRASlide 2 Abstract This document presents a proposal to create a Timing Reference Information Element for use with the TSF Timer commands proposed in p for the purpose of allowing higher layer synchronization to external clocks to be performed in an accurate and efficient manner whether the external clock is local to the STA or not.

doc.: IEEE /2229r0 Submission July 2007 R. Roy, SRASlide 3 Background We are designing a communication system for rapidly varying environments allows communication in the absence of any kind of BSS (because in these environments, there is insufficient time for any of the standard BSS establishment processes to complete). For a variety of reasons, synchronization of communicating STAs to external time sources (such as UTC time from a GPS unit) may be very advantageous in this BSSless mode of operation. Facilities for accurate higher layer synchronization should be included to provide maximum flexibility in PHY channelization configurations for (eg., for supporting multiple regulatory domains). The TSF Timer commands already in the p draft provide the lower layer mechanisms (primitives) allowing for such synchronization. The proposed Timing Reference Information Element provides a key element in the synchronization process.

doc.: IEEE /2229r0 Submission July 2007 R. Roy, SRASlide 4 BSSless Beacon Frame Contents (items in red mandatory in BSSless mode) OrderField / Information Element 1Timestamp 2Beacon Interval 3Capability 4SSID 5Supported Rates … NEDCA Parameter Set N+1QoS Capability N+2Time Reference Information (new) N+3WAVE Information (new) LastVendor Specific

doc.: IEEE /2229r0 Submission July 2007 R. Roy, SRASlide 5 Time Reference Information Format Contents: –Time Source indicates the external source of the time reference Local or external sources (e.g. common time reference based on UTC) –TSF Timer Error is the estimate of the offset of the Timestamp from the external time source Set to 0 if the time source is local –Standard Deviation is the estimate of the standard deviation (uncertainty) of the TSF Timer Error in the STA’s estimate of the external time source Set to 0 if the time source is local

doc.: IEEE /2229r0 Submission Month Year R. Roy/SRASlide 6 Proposed Text Describing the Timing Reference Information Element and it’s use TSF Syncronization in BSSless mode STAs choosing to synchronize to a common external time base may do so using the TSF Timer primitives provided along with the Timing Reference Information Element. For example, STAs may synchronize to Universal Coordinates Time (UTC) time relative to UTC instant T00:00: UTC is defined in ITU-R TF (1986) [B2] and can be obtained externally from many sources including GPS. GPS receivers typically provide a precise 1 pulse per second (PPS) UTC signal (with an error less than 100 ns), and these precise 1 PPS signals can be used for timing and synchronization. STAs that choose to synchronize to UTC time may estimate UTC time as the value of the STAs TSF timer plus any offsets estimated as described in This estimate of UTC time can be used for many purposes including synchronization of channel changes and implementation of TDMA channelization (i.e., time slots). STAs that have a source of UTC time (e.g., from a GPS unit) can easily implement an estimator in a variety of ways, all of which are beyond the scope of this standard. STAs that do not have an internal source of time (UTC or any other) may nonetheless estimate time from BSSless beacons containing a Timestamp and a Timing Reference Information Element received from STAs that do have an estimate of time (UTC or any other). While the details of how this can be accomplished are beyond the scope of this standard, it is easy to see that sufficient information is present in the received BSSless beacon frames. The Timestamps give an estimate of the value of the TSF timer of the transmitting STA at the moment the first bits of the Timestamps were transmitted out the transducer (antenna). The Timing Reference Information Elements give estimates of the offsets necessary to correct each Timestamp so that each matches the output of its external time source (which must be the same for all BSSless beacons obviously, and may be, e.g., UTC time) at the transmission time, and the local timestamp attached to the received BSSless beacon frame gives an estimate of the local TSF timer value at the instant of reception of each BSSless beacon. This information is clearly sufficient for the receiving STA to produce a (biased if the propagation delays from the transmitters to the receiver is not accounted for properly) estimate of the external clock on the transmitting STAs (again it must be the same external source). The details of how this is implemented are beyond the scope of this standard, but statistically unbiased (this is a bit difficult to achieve in these applications) and efficient estimators are preferred. Such estimators also produce estimates of the uncertainties of the parameters they estimate, and these uncertainties are included in the Timing Reference Information Element as well.

doc.: IEEE /2229r0 Submission Month Year R. Roy/SRASlide 7 Proposed Text Describing the Timing Reference Information Element and it’s use Timing Reference information The Timing Reference Information element shown in Figure XX [ed: not shown] contains information describing the source of external time as well as the estimate thereof and its uncertainty. This information can be used by recipients of BSSless beacons to estimate time from the external clock on the STA transmitting the BSSless beacon. This information element has at a minimum an element ID field (1 octet), a length field (1 octet), a timing capabilities field (1 octet), a TSF timer offset field (4 octets), and TSF timer standard deviation field (3 octets). If the minimum information is included, the length field is set to 8. The timing capabilities field is a single-byte (octet) field used to inform recipients of the Timing Reference Information Element of the sender’s source of external time information as well as the current condition of the timing estimator. Bits 0- 2 of this field shall be set to 0 if there is no source of external time associated with the Timing Reference information. Bits 0-2 are set to 0b001 if UTC is the external source, e.g., if the STA has a GPS unit onboard capable of generating UTC time. Other values for bits -2 are currently reserved for future use. Bit 3 of this field shall be set to 1 if this time source is currently available and being used to estimate time, and 0 if not. Bits 4–7 are reserved for future enhancements. The TSF timer offset field is a 4-byte field and shall contain a TSF timer offset estimate (i.e., a zeroth order correction) as a 2’s complement integer in microseconds, which when added to the STA’s TSF timer value yields a zeroth order estimate of the STA’s best estimate of external time (e.g., UTC time) at the instant the first bit of the Timestamp in the BSSless beacon was transmitted from STA’s antenna.

doc.: IEEE /2229r0 Submission Month Year R. Roy/SRASlide 8 Proposed Text Describing the Timing Reference Information Element and it’s use The TSF timer standard deviation field is a 3-byte field containing an estimate of the standard deviation of the error in the STA’s estimate of external time (including biases that have not been calibrated out) in unsigned integer format in units of microseconds. The TSF timer standard deviation field shall be set to its maximum value (2^(24)-1) to indicate that the value of the TSF timer offset field is not meaningful and should not be used to estimate UTC time. Upon startup, the TSF timer offset shall be set to zero and the TSF timer standard deviation shall be set to its maximum value (2^(24)-1), indicating that the TSF timer offset estimate is not currently valid. Note that once any lower variance source of UTC time becomes available, that source and its error variance can be adopted as initial conditions for the UTC estimator. The value of the TSF timer standard deviation, i.e., the error in the estimate of external time (or equivalently, the TSF timer offset for zeroth order estimators) is generally a function of various environmental and implementation factors and will vary with time. For improved estimates of external time, the Timing Reference Information Element can be extended to include higher order information as follows. The Timing Reference Information Element can be extended to include a first order correction (i.e., a correction for the difference between the clock frequencies of the external source and the local TSF Timer). The value in the length field is increased by a multiple of 7 octets. For first order corrections, a 4-byte TSF Timer frequency offset field is appended and contains an estimate of the difference in the external clock’s rate and the rate of the local TSF Timer. It is a signed integer in units of microseconds/second. Following that, a 3-byte unsigned integer, in units of microseconds/second, containing an estimate of the uncertainty in the estimated clock difference is appended. These estimates can be used to yield improved estimates of the external clock. The implementation details are beyond the scope of this standard.