One document matched: draft-thomson-geopriv-wimax-measurements-04.xml
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY RFC2119 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC3688 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3688.xml">
<!ENTITY RFC4282 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4282.xml">
<!ENTITY I-D.ietf-geopriv-held-measurements PUBLIC "" "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-geopriv-held-measurements.xml">
<!ENTITY I-D.ietf-geopriv-held-identity-extensions PUBLIC "" "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-geopriv-held-identity-extensions.xml">
<!ENTITY I-D.thomson-geopriv-location-quality PUBLIC "" "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.thomson-geopriv-location-quality.xml">
]>
<?rfc symrefs="yes"?>
<?rfc sortrefs="no"?>
<?rfc iprnotified="yes"?>
<?rfc strict="yes"?>
<?rfc toc="yes"?>
<?rfc tocindent="yes"?>
<rfc category="std" ipr="trust200902">
<front>
<title abbrev="Location Measurements for 802.16e">
Location Measurements for IEEE 802.16e Devices
</title>
<author initials="M." surname="Thomson" fullname="Martin Thomson">
<organization>Andrew Corporation</organization>
<address>
<postal>
<street>Andrew Building (39)</street>
<street>Wollongong University Campus</street>
<street>Northfields Avenue</street>
<city>Wollongong</city>
<region>NSW</region>
<code>2522</code>
<country>AU</country>
</postal>
<email>martin.thomson@andrew.com</email>
</address>
</author>
<author initials="J." surname="Winterbottom" fullname="James Winterbottom">
<organization>Andrew Corporation</organization>
<address>
<postal>
<street>Andrew Building (39)</street>
<street>Wollongong University Campus</street>
<street>Northfields Avenue</street>
<city>Wollongong</city>
<region>NSW</region>
<code>2522</code>
<country>AU</country>
</postal>
<email>james.winterbottom@andrew.com</email>
</address>
</author>
<date month="July" year="2010"/>
<area>Application</area>
<workgroup>GEOPRIV</workgroup>
<keyword>Internet-Draft</keyword>
<keyword>HELD</keyword>
<keyword>Location</keyword>
<keyword>Measurements</keyword>
<keyword>802.16</keyword>
<keyword>802.16e</keyword>
<keyword>WiMAX</keyword>
<abstract>
<t>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. A separate measurement used for identifying WiMAX session-related parameters is also provided.
</t>
</abstract>
</front>
<middle>
<section title="Introduction">
<t>Determining the location of a device in an IEEE 802.16e <xref target="IEEE.80216E"/> mobile wireless network requires information from the device to improve the accuracy of the final result. Radio timing information provided by the device can enable the calculation of a more accurate location estimate by a Location Information Server (LIS).</t>
<t>This document describes a standard format for 802.16e measurement data that is based on radio measurements made of base stations near the device.
</t>
</section>
<section anchor="conventions" title="Conventions used in this document">
<t>This document builds on <xref target="I-D.ietf-geopriv-held-measurements"/> and consequently uses the same set of terminology. Terminology from <xref target="IEEE.80216E"/> is used where appropriate.
</t>
<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in <xref target="RFC2119"/>.
</t>
</section>
<section title="802.16e Radio Measurement Data">
<t>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.
</t>
<t>The most basic 802.16e measurement indicates the serving BS, as shown in <xref target="ex-basic"/>.
</t>
<figure anchor="ex-basic" title="HELD Location Request with 802.16e Measurement Data">
<artwork><![CDATA[
<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>
]]></artwork>
</figure>
<t>More measurement information can be provided, including timing measurement information for additional serving base stations (if fast base station switching (FBSS) or macro-diversity hand-over (MDHO) are in progress). Information on neighbouring base stations can be provided in addition to that for the serving BS.
</t>
<t>The set of measurement data is chosen by the SS and the presence of specific elements will depend on the time the SS has available to acquire the measurements. The following measurement information may be provided:
<list style="hanging">
<t hangText="id:">(Attribute) The base station identifier for the measured BS. Note that while this isn't a MAC address, it shares the encoding defined for the MAC address.
</t>
<t hangText="rssi:">Receive signal strength indicator, calculated as defined in <xref target="IEEE.80216E"/>. This value is measured in units of dBm. This datum optionally includes an RMS error in dB and sample count.
</t>
<t hangText="cinr:">Carrier inteference to noise ratio (signal to noise), calculated as defined in <xref target="IEEE.80216E"/>. This value is measured in units of dB. This datum optionally includes an RMS error and sample count.
</t>
<t hangText="rd:">Relative delay of the signal from the BS, measured relative to other base stations. Since this value is relative, it MUST be included on at least two BS measurements to be of any use. It is RECOMMENDED that this value be set to <spanx style="verb">0</spanx> for the first BS in the measured set. This datum optionally includes an RMS error and sample count.
<figure anchor="rd" title="Relative Delay Example">
<artwork><![CDATA[
(V) _
| `- _ t[1]
| `- _ t[2]
| BS1 ` . - - - - - - - - - - (V)
_|`. |
|U| `. t[3] |
|_| `. BS2 |
Target SS `.
(V)
|
|
| BS3
]]></artwork>
</figure>
Based on the example in <xref target="rd"/>, relative delay can be calculated based on the relative time that signals transmitted simultaneously (or with known relative times) by base stations can be calculated. If the time of receipt of the signal from each base station is t[x] and the relative delay for BS1 is set to zero, the relative time for each subsequent measured base station is t[x] - t[1].
</t>
<t hangText="rtd:">Round trip delay of the signal from the SS to the BS and back. This measurement datum is only applicable for each serving BS. This value is measured in seconds. This datum optionally includes an RMS error and sample count.
</t>
</list>
</t>
<t>The <spanx style="verb">rmsError</spanx> attribute for signal to noise and received signal strength MAY be calculated using the continuous weighted average method described in <xref target="IEEE.80216E"/>. Values of <spanx style="verb">alpha_AVG</spanx> and <spanx style="verb">k</spanx> are selected by the SS.
</t>
<t>The XML format described in this document provides a greater range of values than the Scanning Results Report (<spanx style="verb">MOB_SCN-REP</spanx>) or the Channel measurement Report Response (<spanx style="verb">REP-RSP</spanx>) 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.
</t>
<section title="Measurement Request Parameters">
<t>A request that does not contain sufficient measurement data can result in an error response. <xref target="I-D.ietf-geopriv-held-measurements"/> defines a measurement request that indicates what parameters might be necessary to complete the request. These parameters might also be present in a response that includes an indication that the requested <xref target="I-D.thomson-geopriv-location-quality">location quality</xref> was not provided.
</t>
<t>The elements present in a radio measurement are all optional. In order for a Device to know which of these is requested, the <spanx style="verb">parameter</spanx> element is defined for radio measurement data. This identifies each requested element using a qualified name.
</t>
<figure anchor="ex-mr">
<preamble>The following example shows a HELD error response that indicates that RSSI and CINR measurement would aid in fulfilling the request.
</preamble>
<artwork><![CDATA[
<error xmlns="urn:ietf:params:xml:ns:geopriv:held"
code="locationUnknown">
<message xml:lang="en">Insufficient measurement data</message>
<measurementRequest
xmlns="urn:ietf:params:xml:ns:geopriv:lm"
xmlns:w16e="urn:ietf:params:xml:ns:geopriv:lm:802.16e">
<measurement type="w16e:w16e">
<w16e:parameter>w16e:rssi</wifi:parameter>
<w16e:parameter>w16e:cinr</wifi:parameter>
</measurement>
</measurementRequest>
</error>
]]></artwork>
</figure>
</section>
</section>
<section title="WiMAX Session-Related Measurements">
<t>In Worldwide Interoperability for Microwave Access (WiMAX) networks <xref target="WiMAX.LBS"/>, an SS might have a particular access network designated as a "home network". In some configurations the network is designed in such a way that the SS only has access to a location server in the home network, known as a home location server, or hLS. However, a server in the current (visited) access network - the vLS - could be the only server that is capable of communicating with the access network to determine the location of the SS. In this case the hLS provides WiMAX session information to the vLS, giving the vLS the information necessary to identify a session and generate location information.
</t>
<t><xref target="ex-session"/> shows an example measurement that contains information regarding a session. This contains the session identifier that is assigned by the anchor authenticator. The <xref target="RFC4282">Network Access Identifier (NAI)</xref> of the device and the address of the anchor authenticator is included.
</t>
<figure anchor="ex-session">
<artwork><![CDATA[
<measurements xmlns="urn:ietf:params:xml:ns:geopriv:lm">
<wimaxSession xmlns="urn:ietf:params:xml:ns:geopriv:lm:802.16e">
<sessionID>19abd9e9f923978f80310d</sessionID>
<nai>user.206417@example.realm</nai>
<anchor ip="2001:DB8::f:301">f-301.aa.example.com</anchor>
</wimaxSession>
</measurements>
]]></artwork>
</figure>
<t>Session parameters are used to identify a particular network attachment session:
<list style="hanging">
<t hangText="sessionID:">A temporary identifier given to a particular session. This value is a binary value that is expressed in hexadecimal.
</t>
<t hangText="nai:">The <xref target="RFC4282">NAI</xref> used by the device to gain network authorization.
</t>
<t hangText="anchor:">The domain name of the anchor authenticator in the visited network. Optionally, this includes an attribute that indicates an IP address in addition to the domain name.
</t>
</list>
</t>
<t>The formal grammar for <xref target="RFC4282">NAI</xref> permits invalid UTF-8, which cannot be expressed using XML. Therefore, this lexical representation of NAI permits escaping. Non-unicode characters (and any other character) are expressed using a backslash ('\') followed by two hexadecimal digits representing the value of a single octet.
</t>
<t>The value-space representation of an NAI is the sequence of octets that is produced from the concatenation of UTF-8 encoded sequences of unescaped characters and octets derived from escaped components. This sequence MUST conform to the constraints in <xref target="RFC4282"/>.
</t>
</section>
<section anchor="schema" title="802.16e Measurement Schema">
<t><list style="hanging"><t hangText="Note:">The pattern for NAI has extra whitespace added to conform to formatting restrictions. The actual value does not contain whitespace. </t></list></t>
<figure>
<artwork><![CDATA[
<?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:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</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:element name="wimaxSession" type="w16e:wimaxSessionType"/>
<xs:complexType name="wimaxSessionType">
<xs:complexContent>
<xs:restriction base="xs:anyType">
<xs:sequence>
<xs:element name="sessionID" type="xs:hexBinary"/>
<xs:element name="nai" type="w16e:naiType"/>
<xs:element name="anchor" type="w16e:anchorType"/>
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="anchorType">
<xs:simpleContent>
<xs:extension base="w16e:domainType">
<xs:attribute name="ip" type="bt:ipAddressType"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:simpleType name="domainType">
<xs:restriction base="xs:token">
<xs:pattern
value="([a-zA-Z0-9]([a-zA-Z0-9-]*[a-zA-Z0-9])?\.?)+"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="naiType">
<xs:restriction base="xs:token">
<xs:pattern
value="([^\\]|\\[\dA-Fa-f]{2})*
(@([A-Za-z\d]([A-Za-z\d\-]*[A-Za-z\d])*\.)+
[A-Za-z\d]([A-Za-z\d\-]*[A-Za-z\d])*)?"/>
</xs:restriction>
</xs:simpleType>
</xs:schema>
]]></artwork>
</figure>
</section>
<section anchor="security" title="Security Considerations">
<t>The considerations of <xref target="I-D.ietf-geopriv-held-measurements"/> apply. The receiver of 802.16e measurement information requires knowledge of the location of base stations to make effective use of the information.
</t>
<t>NAI is used as identification information for a device. The connection of this information with other session parameters provides a potential link between identity and location. In addition, unless care is taken to verify this information, this datum could be exploited by an attacker to gain access to another user's location information. See the privacy and security considerations of <xref target="I-D.ietf-geopriv-held-identity-extensions"/> for details on using identity parameters.
</t>
</section>
<section anchor="iana" title="IANA Considerations">
<section title="URN Sub-Namespace Registration for urn:ietf:params:xml:ns:held:lm:802.16e">
<t>This section registers a new XML namespace, <spanx style="verb">urn:ietf:params:xml:ns:held:lm:802.16e</spanx>, following the guidelines in <xref target="RFC3688"/>.
<list style="empty">
<t>URI: urn:ietf:params:xml:ns:held:lm</t>
<t>Registrant Contact: IETF, GEOPRIV working group, (geopriv@ietf.org), Martin Thomson (martin.thomson@andrew.com).</t>
<t>XML:
<figure>
<artwork><![CDATA[
BEGIN
<?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
<title>802.16e Measurements</title>
</head>
<body>
<h1>Namespace for 802.16e Measurements</h1>
<h2>urn:ietf:params:xml:ns:held:lm:802.16e</h2>
[[NOTE TO IANA/RFC-EDITOR: Please update RFC URL and replace XXXX
with the RFC number for this specification.]]
<p>See <a href="[[RFC URL]]">RFCXXXX</a>.</p>
</body>
</html>
END
]]></artwork>
</figure>
</t>
</list>
</t>
</section>
<section title="XML Schema Registration for 802.16e Measurement Schema">
<t>This section registers an XML schema following the guidelines in <xref target="RFC3688"/>.
<list style="hanging">
<t hangText="URI:">urn:ietf:params:xml:schema:held:lm:802.16e</t>
<t hangText="Registrant Contact:">IETF, GEOPRIV working group, (geopriv@ietf.org), Martin Thomson (martin.thomson@andrew.com).</t>
<t hangText="Schema:">The XML for this schema can be found in <xref target="schema"/> of this document.
</t>
</list>
</t>
</section>
</section>
<!-- <section title="Acknowledgements">
<t>
</t>
</section> -->
<!--
<appendix title="Change Log">
<t>[[The RFC Editor is requested to remove this section at publication.]]</t>
<t>Changes since -0-1:
<list style="symbols">
<t>Document created.</t>
</list>
</t>
</appendix>
-->
</middle>
<back>
<references title="Normative References">
&RFC2119;
&RFC3688;
&RFC4282;
&I-D.ietf-geopriv-held-measurements;
&I-D.ietf-geopriv-held-identity-extensions;
&I-D.thomson-geopriv-location-quality;
<reference anchor="IEEE.80216E">
<front>
<title>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</title>
<author>
<organization>IEEE</organization>
</author>
<date month="February" day="28" year="2006" />
</front>
<seriesInfo name="Std" value="802.16E"/>
</reference>
<reference anchor="WiMAX.LBS">
<front>
<title>WiMAX Network Protocols and Architecture for Location Based Services</title>
<author>
<organization>WiMAX Forum</organization>
</author>
<date month="November" day="12" year="2008" />
</front>
<seriesInfo name="Network Release 1.5" value="1.0.0 Draft"/>
</reference>
</references>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-24 04:44:08 |