Location Measurements for IEEE 802.16e Devices

By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work in progress.”

Abstract

IEEE 802.16e defines means for true mobility within an 802.16 wireless network. Determining an accurate location for 802.16e devices requires information on radio parameters. A format is defined for location-related measurement data that can be provided by an 802.16e device. This measurement data can be used by a Location Information Server (LIS) to more accurately determine the location of the device.

1. Introduction
2. Conventions used in this document
3. 802.16e Measurement Data
4. 802.16e Measurement Schema
5. Security Considerations
6. IANA Considerations
6.1. URN Sub-Namespace Registration for urn:ietf:params:xml:ns:held:lm:802.16e
6.2. XML Schema Registration for 802.16e Measurement Schema
7. Normative References
§ Authors' Addresses
§ Intellectual Property and Copyright Statements

1. Introduction

This document describes a standard format for 802.16e measurement data that is based on radio measurements made of base stations near the device.

2. Conventions used in this document

3. 802.16e Measurement Data

A subscriber station (SS) in an 802.16e network is able to observe radio signals from each base station (BS) in its proximity. By observing the timing and strength of these signals, a SS is able to provide a LIS with information that can be used to determine its location.

  <locationRequest xmlns="urn:ietf:params:xml:ns:geopriv:held">
    <locationType exact="true">civic</locationType>
    <measurements xmlns="urn:ietf:params:xml:ns:geopriv:lm">
      <w16e xmlns="urn:ietf:params:xml:ns:geopriv:lm:802.16e">
        <servingBS id="00-21-43-65-87-a9"/>
      </w16e>
    </measurements>
  </locationRequest>

More measurement information can be provided, including timing measurement information for additional serving base stations (if fast base station switching or macro-diversity hand-over are in progress). Information on neighbouring base stations can be provided in addition to that for the serving BS, or instead of if the SS is not currently attached to the 802.16e interface.

The set measurement data that is included is chosen by the SS and will depend on the time it has available to acquire the measurements. The following measurement information may be provided:

The XML format described in this document provides a greater range of values than the Scanning Results Report (MOB_SCN-REP) or the Channel measurement Report Response (REP-RSP) message. This allows for the reporting of measurements in a manner less constrained by encoding. A greater range of values does not necessarily imply anything about the uncertainty in those measurements; the RMS error is used to indicate the magnitude of any error.

4. 802.16e Measurement Schema

<?xml version="1.0"?>
<xs:schema
    targetNamespace="urn:ietf:params:xml:ns:geopriv:lm:802.16e"
    xmlns:w16e="urn:ietf:params:xml:ns:geopriv:lm:802.16e"
    xmlns:bt="urn:ietf:params:xml:ns:geopriv:lm:basetypes"
    xmlns:xs="http://www.w3.org/2001/XMLSchema"
    elementFormDefault="qualified"
    attributeFormDefault="unqualified">

  <xs:annotation>
    <xs:documentation source="https://www.ietf.org/rfc/rfcXXXX.txt">
      <!-- [[NOTE TO RFC-EDITOR: Please replace above URL with URL of
           published RFC and remove this note.]] -->
      This document defines a location-related measurement format
      for 802.16e mobile wireless devices.
    </xs:documentation>
  </xs:annotation>

  <xs:import namespace="urn:ietf:params:xml:ns:geopriv:lm:basetypes"/>

  <xs:element name="w16e" type="w16e:w16eType"/>
  <xs:complexType name="w16eType">
    <xs:complexContent>
      <xs:restriction base="xs:anyType">
        <xs:sequence>
          <xs:choice>
            <xs:element ref="w16e:servingBS" maxOccurs="unbounded"/>
            <xs:element ref="w16e:neighbourBS"/>
          </xs:choice>
          <xs:element ref="w16e:neighbourBS"
                      minOccurs="0" maxOccurs="unbounded"/>
        </xs:sequence>
      </xs:restriction>
    </xs:complexContent>
  </xs:complexType>

  <xs:element name="neighbourBS" type="w16e:bsType"/>

  <xs:complexType name="bsType">
    <xs:complexContent>
      <xs:restriction base="xs:anyType">
        <xs:sequence>
          <xs:element name="rssi" type="bt:doubleWithRMSError"
                      minOccurs="0"/>
          <xs:element name="cinr" type="bt:doubleWithRMSError"
                      minOccurs="0"/>
          <xs:element name="rd" type="bt:doubleWithRMSError"
                      minOccurs="0"/>
        </xs:sequence>
        <xs:attribute name="id" type="bt:macAddressType"/>
      </xs:restriction>
    </xs:complexContent>
  </xs:complexType>

  <xs:element name="servingBS" type="w16e:servingBsType"/>

  <xs:complexType name="servingBsType">
    <xs:complexContent>
      <xs:extension base="w16e:bsType">
        <xs:sequence>
          <xs:element name="rtd" type="bt:nnDoubleWithRMSError"
                      minOccurs="0"/>
        </xs:sequence>
      </xs:extension>
    </xs:complexContent>
  </xs:complexType>

</xs:schema>

5. Security Considerations

6. IANA Considerations

6.1. URN Sub-Namespace Registration for urn:ietf:params:xml:ns:held:lm:802.16e

6.2. XML Schema Registration for 802.16e Measurement Schema

7. Normative References

Authors' Addresses

Full Copyright Statement

This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.

This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Intellectual Property

The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.

Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.

The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.

[RFC2119]	Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” BCP 14, RFC 2119, March 1997 (TXT, HTML, XML).
[RFC3688]	Mealling, M., “The IETF XML Registry,” BCP 81, RFC 3688, January 2004 (TXT).
[I-D.thomson-geopriv-held-measurements]	Thomson, M. and J. Winterbottom, “Using Device-provided Location-Related Measurements in Location Configuration Protocols,” draft-thomson-geopriv-held-measurements-05 (work in progress), October 2009 (TXT).
[IEEE.80216E]	IEEE, “Air Interface for Fixed and Mobile Broadband Wireless Access Systems; Physical and Medium Access Control Layers for Combined Fixed and Mobile Operation in Licensed Bands,” Std 802.16E, February 2006.

	Martin Thomson
	Andrew
	PO Box U40
	Wollongong University Campus, NSW 2500
	AU
Phone:	+61 2 4221 2915
Email:	martin.thomson@andrew.com
URI:	http://www.andrew.com/

	James Winterbottom
	Andrew
	PO Box U40
	Wollongong University Campus, NSW 2500
	AU
Phone:	+61 2 4221 2938
Email:	james.winterbottom@andrew.com
URI:	http://www.andrew.com/

Location Measurements for IEEE 802.16e Devices
draft-thomson-geopriv-wimax-measurements-00

Status of this Memo

Abstract

Table of Contents

1. Introduction

2. Conventions used in this document

3. 802.16e Measurement Data

4. 802.16e Measurement Schema

5. Security Considerations

6. IANA Considerations

6.1. URN Sub-Namespace Registration for urn:ietf:params:xml:ns:held:lm:802.16e

6.2. XML Schema Registration for 802.16e Measurement Schema

7. Normative References

Authors' Addresses

Full Copyright Statement

Intellectual Property

Location Measurements for IEEE 802.16e Devicesdraft-thomson-geopriv-wimax-measurements-00

Status of this Memo

Abstract

Table of Contents

1. Introduction

2. Conventions used in this document

3. 802.16e Measurement Data

4. 802.16e Measurement Schema

5. Security Considerations

6. IANA Considerations

6.1. URN Sub-Namespace Registration for urn:ietf:params:xml:ns:held:lm:802.16e

6.2. XML Schema Registration for 802.16e Measurement Schema

7. Normative References

Authors' Addresses

Full Copyright Statement

Intellectual Property

Location Measurements for IEEE 802.16e Devices
draft-thomson-geopriv-wimax-measurements-00