<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet type="text/xsl" href="method-tokens.xsl"?>
<?xml-model href="method-tokens.rng" schematypens="http://relaxng.org/ns/structure/1.0" ?>
<registry xmlns="http://www.iana.org/assignments" id="method-tokens">
  <title>Method Tokens</title>
  <category>Geopriv Location Object Registries</category>
  <created>2004-11-03</created>
  <updated>2022-09-15</updated>
  <registry id="method-tokens-1">
    <title>Method Tokens</title>
    <xref type="rfc" data="rfc4119"/>
    <registration_rule>First Come First Served</registration_rule>
    <note>These tokens are associated with the PIDF-LO object.</note>
    <record date="2018-12-07">
      <token>A-GNSS</token>
      <description>Assisted Global Navigation Satellite Systems</description>
      <xref type="person" data="Brian_Rosen"/>
    </record>
    <record>
      <token>A-GPS</token>
      <description>GPS with assistance</description>
      <xref type="rfc" data="rfc4119"/>
    </record>
    <record>
      <token>AOA</token>
      <description>Angle of Arrival</description>
      <xref type="person" data="James_Winterbottom"/>
    </record>
    <record date="2012-01-11">
      <token>best-guess</token>
      <description>The LIS cannot provide an accurate location. The value is its best guess, but may be very inaccurate.</description>
      <xref type="person" data="Brian_Rosen"/>
    </record>
    <record>
      <token>Cell</token>
      <description>Location of the cellular radio antenna</description>
      <xref type="rfc" data="rfc4119"/>
    </record>
    <record date="2019-03-21">
      <token>DBH</token>
      <description>Device-Based Hybrid</description>
      <xref type="person" data="Apple"/>
    </record>
    <record date="2022-09-15">
      <token>DBH2</token>
      <description>A Device-Based Hybrid system (typically on a
        mobile device) produces a compound location that
        includes a full or partial Civic Address in addition
        to the Geodetic Location normally expected from
        a DBH system. Distinct from RevGeo because,
        even if the DBH system uses reverse-geocoding to
        determine the Civic Location, the DBH system
        determines and delivers the Civic Location, not a
        downstream entity.</description>
      <xref type="uri" data="https://cdn.ymaws.com/www.nena.org/resource/resmgr/standards/nena-req-003.1-2022_3d_gis_2.pdf">NENA-REQ-003.1-2022</xref>
      <xref type="person" data="Tom_Hsu"/>
    </record>
    <record date="2019-03-21">
      <token>DBH_HELO</token>
      <description>Device-Based Hybrid using Apple Hybridized Emergency Location</description>
      <xref type="person" data="Apple"/>
    </record>
    <record date="2008-07-15">
      <token>Derived</token>
      <description>This value is intended to represent a location       
object determined by geocoding or reverse geocoding
a location determined by some other method.</description>
      <xref type="person" data="Brian_Rosen"/>
    </record>
    <record date="2022-09-15">
      <token>Derived-RevGeo</token>
      <description>A full or partial Civic Location, which is not
        validated against an LVF, is derived by reversegeocoding a Geodetic Location. The original
        Geodetic Location MUST also be delivered with
        the derived Civic Location. Used when a
        downstream entity other than the calling device
        reverse-geocodes a Geodetic Location it received
        from an upstream entity, such as location
        services/DBH.</description>
      <xref type="uri" data="https://cdn.ymaws.com/www.nena.org/resource/resmgr/standards/nena-req-003.1-2022_3d_gis_2.pdf">NENA-REQ-003.1-2022</xref>
      <xref type="person" data="Tom_Hsu"/>
    </record>
    <record date="2022-09-15">
      <token>DerivedRevGeo-LVF</token>
      <description>A full or partial Civic Location, which is validated
        against an LVF, is derived by reverse-geocoding a
        Geodetic Location.</description>
      <xref type="uri" data="https://cdn.ymaws.com/www.nena.org/resource/resmgr/standards/nena-req-003.1-2022_3d_gis_2.pdf">NENA-REQ-003.1-2022</xref>
      <xref type="person" data="Tom_Hsu"/>
    </record>
    <record>
      <token>Device-Assisted_A-GPS</token>
      <description>Device provides psuedo-ranges to a network element   
that computes the location</description>
      <xref type="person" data="James_Winterbottom"/>
    </record>
    <record>
      <token>Device-Assisted_EOTD</token>
      <description>Enhanced Observed Time Difference, device provides   
measurements, network element computes location</description>
      <xref type="person" data="James_Winterbottom"/>
    </record>
    <record>
      <token>Device-Based_A-GPS</token>
      <description>Network provides psuedo-ranges to the device and     
the device computes its location</description>
      <xref type="person" data="James_Winterbottom"/>
    </record>
    <record>
      <token>Device-Based_EOTD</token>
      <description>Enhanced Observed Time Difference, network element   
provides measurements and device computes location</description>
      <xref type="person" data="James_Winterbottom"/>
    </record>
    <record>
      <token>DHCP</token>
      <description>Provided by DHCP (used for wireline access           
networks, see 802.11 below)</description>
      <xref type="rfc" data="rfc4119"/>
    </record>
    <record date="2018-12-07">
      <token>E-CID</token>
      <description>Enhanced Cell Identifier</description>
      <xref type="person" data="Brian_Rosen"/>
    </record>
    <record date="2019-04-22">
      <token>ELS-BLE</token>
      <description>Civic Address representing the associated location of the 
        UE based upon the Bluetooth beacon from ELS</description>
      <xref type="uri" data="http://www.atis.org">ATIS-0700028.v002</xref>
      <xref type="person" data="Roger_Marshall"/>
    </record>
    <record date="2019-04-22">
      <token>ELS-WiFi</token>
      <description>Civic Address representing the associated location of the 
        UE based upon the referenced Wi-Fi Access Point from ELS</description>
      <xref type="uri" data="http://www.atis.org">ATIS-0700028.v002</xref>
      <xref type="person" data="Roger_Marshall"/>
    </record>
    <record date="2018-12-07">
      <token>GNSS</token>
      <description>Global Navigation Satellite Systems</description>
      <xref type="person" data="Brian_Rosen"/>
    </record>
    <record>
      <token>GPS</token>
      <description>Global Positioning System</description>
      <xref type="rfc" data="rfc4119"/>
    </record>
    <record>
      <token>Handset_AFLT</token>
      <description>Advanced Forward Link Trilateration</description>
      <xref type="person" data="James_Winterbottom"/>
    </record>
    <record date="2022-05-12">
      <token>Handset_BLE</token>
      <description>Bluetooth based X,Y position, using beacon proximity 
        with varying power and coverage levels</description>
      <xref type="uri" data="https://www.nena.org/page/i3_Stage3">NENA-STA-010.3-2021</xref>
      <xref type="person" data="Brian_Rosen"/>
    </record>
    <record>
      <token>Handset_EFLT</token>
      <description>Enhanced Forward Link Trilateration</description>
      <xref type="person" data="James_Winterbottom"/>
    </record>
    <record date="2022-05-12">
      <token>Handset_WiFi</token>
      <description>WLAN based X,Y position, using beacon proximity or 
        ranging methods</description>
      <xref type="uri" data="https://www.nena.org/page/i3_Stage3">NENA-STA-010.3-2021</xref>
      <xref type="person" data="Brian_Rosen"/>
    </record>
    <record>
      <token>Hybrid_A-GPS</token>
      <description>Device provides psuedo-rangesto a network element    
that computes the location in combination with
network measurements</description>
      <xref type="person" data="James_Winterbottom"/>
    </record>
    <record date="2018-12-07">
      <token>hybridAGPS_AFLT</token>
      <description>Hybrid of Assisted GPS and Advanced Forward Link Trilateration</description>
      <xref type="person" data="Brian_Rosen"/>
    </record>
    <record date="2022-05-12">
      <token>hybridCellSector_AFLT</token>
      <description>Positioning based on combining information from multiple cells or sectors</description>
      <xref type="uri" data="https://www.nena.org/page/i3_Stage3">NENA-STA-010.3-2021</xref>
      <xref type="person" data="Brian_Rosen"/>
    </record>
    <record date="2018-12-07">
      <token>hybridCellSector_AGPS</token>
      <description>Hybrid of Cell/Sector based and Assisted GPS</description>
      <xref type="person" data="Brian_Rosen"/>
    </record>
    <record date="2022-05-12">
      <token>hybridOTDOA_A-GNSS</token>
      <description>Positioning based on the combination of OTDOA and multiple constellations (GPS, GLONASS, Galileo, etc.)</description>
      <xref type="uri" data="https://www.nena.org/page/LSRG">NENA-STA-034.1-2021</xref>
      <xref type="person" data="Brian_Rosen"/>
    </record>
    <record date="2022-05-12">
      <token>hybridOTDOA_AGPS</token>
      <description>Positioning based on the combination of OTDOA and AGPS measurements</description>
      <xref type="uri" data="https://www.nena.org/page/LSRG">NENA-STA-034.1-2021</xref>
      <xref type="person" data="Brian_Rosen"/>
    </record>
    <record date="2022-05-12">
      <token>hybridRFPatternMatch_AGPS</token>
      <description>Network-centric positioning method based on a combination of  radio link 
        measurements collected from the network and/or the device and AGPS</description>
      <xref type="uri" data="https://www.nena.org/page/i3_Stage3">NENA-STA-010.3-2021</xref>
      <xref type="person" data="Brian_Rosen"/>
    </record>
    <record date="2022-05-12">
      <token>hybridTDOA_A-GNSS</token>
      <description>Positioning based on the combination of TDOA and multiple constellations 
        (GPS, GLONASS, Galileo, etc.)</description>
      <xref type="uri" data="https://www.nena.org/page/i3_Stage3">NENA-STA-010.3-2021</xref>
      <xref type="person" data="Brian_Rosen"/>
    </record>
    <record date="2018-12-07">
      <token>hybridTDOA_AOA</token>
      <description>Hybrid of Time Difference of Arrival and Angle of Arrival</description>
      <xref type="person" data="Brian_Rosen"/>
    </record>
    <record date="2018-12-07">
      <token>hybridTDOA_AGPS</token>
      <description>Hybrid of Time Difference of Arrival and AGPS</description>
      <xref type="person" data="Brian_Rosen"/>
    </record>
    <record date="2018-12-07">
      <token>hybridTDOA_AGPS_AOA</token>
      <description>Hybrid of Time Difference of Arrival, Assisted GPS and Angle of Arrival</description>
      <xref type="person" data="Brian_Rosen"/>
    </record>
    <record date="2022-05-12">
      <token>hybridWiFi_AGPS</token>
      <description>Positioning in the network based on the combination of Wi-Fi and 
        AGPS measurements</description>
      <xref type="uri" data="https://www.nena.org/page/i3_Stage3">NENA-STA-010.3-2021</xref>
      <xref type="person" data="Brian_Rosen"/>
    </record>
    <record>
      <token>IPDL</token>
      <description>Idle Period Down Link</description>
      <xref type="person" data="James_Winterbottom"/>
    </record>
    <record>
      <token>LLDP-MED</token>
      <description>Provided by Link Layer Discovery Protocol - Media    
Endpoint Discovery (LLDP-MED)</description>
      <xref type="text">Telecommunications Industry Association, "Link Layer Discovery
Protocol for Media Endpoint Devices", ANSI/TIA-1057, April 2006.</xref>
      <xref type="person" data="Peter_Blatherwick"/>
    </record>
    <record>
      <token>Manual</token>
      <description>Entered manually by an operator or user, e.g.,       
based on subscriber billing or service location
information</description>
      <xref type="rfc" data="rfc4119"/>
    </record>
    <record date="2022-09-15">
      <token>Manual-FIXED</token>
      <description>A Civic Location is derived by knowledge that the
        calling device is connecting via a semi-static
        small-cell device that is at a known, validated,
        address, such as a pico/femtocell or that the
        calling device is a fixed cellular device.</description>
      <xref type="uri" data="https://cdn.ymaws.com/www.nena.org/resource/resmgr/standards/nena-req-003.1-2022_3d_gis_2.pdf">NENA-REQ-003.1-2022</xref>
      <xref type="person" data="Tom_Hsu"/>
    </record>
    <record date="2022-09-15">
      <token>Manual-RESD</token>
      <description>A Civic Location is provided using knowledge that
        the calling device is a static device at a known,
        validated, residential address.</description>
      <xref type="uri" data="https://cdn.ymaws.com/www.nena.org/resource/resmgr/standards/nena-req-003.1-2022_3d_gis_2.pdf">NENA-REQ-003.1-2022</xref>
      <xref type="person" data="Tom_Hsu"/>
    </record>
    <record date="2017-05-25">
      <token>MBS</token>
      <description>Metropolitan Beacon System</description>
      <xref type="person" data="NextNav"/>
    </record>
    <record date="2007-10-18">
      <token>MPL</token>
      <description>Measured Path Loss</description>
      <xref type="person" data="James_Winterbottom"/>
    </record>
    <record date="2016-05-12">
      <token>NEAD-BLE</token>
      <description>Civic Address representing the provisioned location of a 
        Bluetooth beacon to support the dispatching of emergency services.</description>
      <xref type="uri" data="http://www.atis.org">ATIS-0700028</xref>
      <xref type="person" data="Roger_Marshall"/>
    </record>
    <record date="2016-05-12">
      <token>NEAD-WiFi</token>
      <description>Civic Address representing the provisioned location of a 
        Wi-Fi Access Point to support the dispatching of emergency services.</description>
      <xref type="uri" data="http://www.atis.org">ATIS-0700028</xref>
      <xref type="person" data="Roger_Marshall"/>
    </record>
    <record date="2018-12-07">
      <token>networkRFFingerprinting</token>
      <description>Network Based RF Fingerprinting</description>
      <xref type="person" data="Brian_Rosen"/>
    </record>
    <record date="2018-12-07">
      <token>networkTDOA</token>
      <description>Network Based Time Difference of Arrival</description>
      <xref type="person" data="Brian_Rosen"/>
    </record>
    <record date="2018-12-07">
      <token>networkTOA</token>
      <description>Network Based Time of Arrival</description>
      <xref type="person" data="Brian_Rosen"/>
    </record>
    <record>
      <token>NMR</token>
      <description>Network Measurement Reports</description>
      <xref type="person" data="James_Winterbottom"/>
    </record>
    <record>
      <token>OTDOA</token>
      <description>Observed Time Difference of Arrival</description>
      <xref type="person" data="James_Winterbottom"/>
    </record>
    <record date="2022-09-15">
      <token>Proximity</token>
      <description>A Civic Location is provided using knowledge that
        the caller is at or near a specific registered
        address for that person’s identity and/or their
        device, such as determining by analyzing the
        caller’s Geodetic Location that they are at their
        registered home address or that they are placing
        a call from their home Wi-Fi.</description>
      <xref type="uri" data="https://cdn.ymaws.com/www.nena.org/resource/resmgr/standards/nena-req-003.1-2022_3d_gis_2.pdf">NENA-REQ-003.1-2022</xref>
      <xref type="person" data="Tom_Hsu"/>
    </record>
    <record>
      <token>RFID</token>
      <description>Proximity to a Radio Frequency Identification        
beacon</description>
      <xref type="person" data="James_Winterbottom"/>
    </record>
    <record date="2007-10-18">
      <token>RSSI</token>
      <description>Received Signal Strength Indicator</description>
      <xref type="person" data="James_Winterbottom"/>
    </record>
    <record date="2007-10-18">
      <token>RSSI-RTT</token>
      <description>Combination of Received Signal Strength Indicator    
and Round Trip Time used to determine the location
of the Target</description>
      <xref type="person" data="James_Winterbottom"/>
    </record>
    <record>
      <token>RTT</token>
      <description>Round Trip Time</description>
      <xref type="person" data="James_Winterbottom"/>
    </record>
    <record>
      <token>TA</token>
      <description>Timing Advance</description>
      <xref type="person" data="James_Winterbottom"/>
    </record>
    <record>
      <token>TA-NMR</token>
      <description>Timing Advance and Network Measurement Reports</description>
      <xref type="person" data="James_Winterbottom"/>
    </record>
    <record>
      <token>Triangulation</token>
      <description>Triangulated from time-of-arrival, signal strength   
or similar measurements</description>
      <xref type="rfc" data="rfc4119"/>
    </record>
    <record>
      <token>UTDOA</token>
      <description>Uplink Time Difference of Arrival</description>
      <xref type="person" data="James_Winterbottom"/>
    </record>
    <record>
      <token>Wiremap</token>
      <description>Location determined using wiremap correlations to    
ciruit identifiers</description>
      <xref type="person" data="James_Winterbottom"/>
    </record>
    <record>
      <token>802.11</token>
      <description>802.11 access point (used for DHCP-based             
provisioning over wireless access networks)</description>
      <xref type="rfc" data="rfc4119"/>
    </record>
  </registry>
  <people>
    <person id="Apple">
      <name>Apple, Inc.</name>
      <uri>mailto:helo&amp;group.apple.com</uri>
      <updated>2019-03-21</updated>
    </person>
    <person id="Brian_Rosen">
      <name>Brian Rosen</name>
      <uri>mailto:br&amp;brianrosen.net</uri>
      <updated>2022-05-12</updated>
    </person>
    <person id="James_Winterbottom">
      <name>James Winterbottom</name>
      <uri>mailto:james.winterbottom&amp;andrew.com</uri>
      <updated>2007-10-18</updated>
    </person>
    <person id="NextNav">
      <name>NextNav</name>
      <uri>mailto:info&amp;NextNav.com</uri>
      <updated>2017-05-25</updated>
    </person>
    <person id="Peter_Blatherwick">
      <name>Peter Blatherwick</name>
      <uri>mailto:peter_blatherwick&amp;mitel.com</uri>
      <updated>2006-07-19</updated>
    </person>
    <person id="Roger_Marshall">
      <name>Roger Marshall</name>
      <uri>mailto:roger.marshall&amp;comtechtel.com</uri>
      <updated>2019-04-22</updated>
    </person>
    <person id="Tom_Hsu">
      <name>Tom Hsu</name>
      <uri>mailto:tom.hsu&amp;nokia.com</uri>
      <updated>2022-09-15</updated>
    </person>
  </people>
</registry>
