ETSI TS 124 312 V9.0.

0 (2010-01)
Technical Specification

Universal Mobile Telecommunications System (UMTS); LTE; Access Network Discovery and Selection Function (ANDSF) Management Object (MO) (3GPP TS 24.312 version 9.0.0 Release 9)

3GPP TS 24.312 version 9.0.0 Release 9

1

ETSI TS 124 312 V9.0.0 (2010-01)

Reference
RTS/TSGC-0124312v900

Keywords
LTE, UMTS

ETSI
650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from: http://www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http://portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http://portal.etsi.org/chaircor/ETSI_support.asp

Copyright Notification
No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. © European Telecommunications Standards Institute 2010. All rights reserved. DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. TM 3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. LTE™ is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
TM TM TM TM

ETSI

3GPP TS 24.312 version 9.0.0 Release 9

2

ETSI TS 124 312 V9.0.0 (2010-01)

Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http://webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document.

Foreword
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http://webapp.etsi.org/key/queryform.asp.

ETSI

3GPP TS 24.312 version 9.0.0 Release 9

3

ETSI TS 124 312 V9.0.0 (2010-01)

Contents
Intellectual Property Rights ................................................................................................................................2 Foreword.............................................................................................................................................................2 Foreword.............................................................................................................................................................6 1 2 3
3.1 3.3

Scope ........................................................................................................................................................7 References ................................................................................................................................................7 Definitions and abbreviations ...................................................................................................................8
Definitions .......................................................................................................................................................... 8 Abbreviations ..................................................................................................................................................... 8

4 5
5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8 5.9 5.10 5.10A 5.11 5.12 5.13 5.14 5.15 5.16 5.17 5.18 5.18A 5.18B 5.19 5.20 5.21 5.22 5.23 5.24 5.25 5.26 5.27 5.27A 5.28 5.29 5.30 5.31 5.32 5.33 5.33A 5.34 5.35 5.36 5.36A 5.36B

ANDSF MO .............................................................................................................................................8 ANDSF MO parameters .........................................................................................................................11
General ............................................................................................................................................................. 11 Node: <X> ....................................................................................................................................................... 11 <X>/Name ....................................................................................................................................................... 11 <X>/Policy ....................................................................................................................................................... 11 <X>/Policy/<X> .............................................................................................................................................. 11 <X>/Policy/<X>/RulePriority ......................................................................................................................... 12 <X>/Policy/<X>/PrioritizedAccess ................................................................................................................. 12 <X>/Policy/<X>/PrioritizedAccess/<X> ........................................................................................................ 12 <X>/Policy/<X>/PrioritizedAccess/<X>/ AccessTechnology........................................................................ 12 <X>/Policy/<X>/PrioritizedAccess/<X>/ AccessId ....................................................................................... 13 <X>/Policy/<X>/PrioritizedAccess/<X>/ SecondaryAccessId ........................................................................ 13 <X>/Policy/<X>/PrioritizedAccess/<X>/ AccessNetworkPriority ................................................................ 13 <X>/Policy/<X>/ValidityArea ........................................................................................................................ 14 <X>/Policy/<X>/ValidityArea/3GPP_Location.............................................................................................. 14 <X>/Policy/<X>/ValidityArea/3GPP_Location/<X> ..................................................................................... 14 <X>/Policy/<X>/ValidityArea/3GPP_Location/<X>/PLMN......................................................................... 15 <X>/Policy/<X>/ValidityArea/3GPP_Location/<X>/TAC............................................................................ 15 <X>/Policy/<X>/ValidityArea/3GPP_Location/<X>/LAC............................................................................ 15 <X>/Policy/<X>/ValidityArea/3GPP_Location/<X>/GERAN_CI ................................................................ 15 <X>/Policy/<X>/ValidityArea/3GPP_Location/ <X>/UTRAN_CI ................................................................ 16 <X>/Policy/<X>/ValidityArea/3GPP_Location/ <X>/EUTRA_CI ................................................................. 16 <X>/Policy/<X>/ValidityArea/3GPP2_Location............................................................................................ 16 <X>/Policy/<X>/ValidityArea/3GPP2_Location/1x ...................................................................................... 17 <X>/Policy/<X>/ValidityArea/3GPP2_Location/1x/<X> .............................................................................. 17 <X>/Policy/<X>/ValidityArea/3GPP2_Location/1x/<X>/ SID ..................................................................... 17 <X>/Policy/<X>/ValidityArea/3GPP2_Location/1x/<X>/ NID .................................................................... 17 <X>/Policy/<X>/ValidityArea/3GPP2_Location/1x/<X>/ Base_ID.............................................................. 18 <X>/Policy/<X>/ValidityArea/3GPP2_Location/HRPD ................................................................................ 18 <X>/Policy/<X>/ValidityArea/3GPP2_Location/HRPD/<X> ....................................................................... 18 <X>/Policy/<X>/ValidityArea/3GPP2_Location/HRPD/<X>/ Sector_ID..................................................... 18 <X>/Policy/<X>/ValidityArea/3GPP2_Location/HRPD/<X>/ Netmask ....................................................... 19 <X>/Policy/<X>/ValidityArea/WiMAX_Location ......................................................................................... 19 <X>/Policy/<X>/ValidityArea/WiMAX_Location/<X> ................................................................................ 19 <X>/Policy/<X>/ValidityArea/WiMAX_Location/<X>/NAP-ID ................................................................. 19 <X>/Policy/<X>/ValidityArea/WiMAX_Location/<X>/BS-ID .................................................................... 20 <X>/Policy/<X>/ValidityArea/WLAN_Location ........................................................................................... 20 <X>/Policy/<X>/ValidityArea/WLAN_Location/<X> .................................................................................. 20 <X>/Policy/<X>/ValidityArea/WLAN_Location/<X>/HESSID ................................................................... 20 <X>/Policy/<X>/ValidityArea/WLAN_Location/<X>/SSID ........................................................................ 20 <X>/Policy/<X>/ValidityArea/WLAN_Location/<X>/BSSID ...................................................................... 21 <X>/Policy/<X>/ValidityArea/Geo_Location ................................................................................................ 21 <X>/Policy/<X>/ValidityArea/Geo_Location/Circular .................................................................................. 21 <X>/Policy/<X>/ValidityArea/Geo_Location/Circular/<X> ......................................................................... 21

ETSI

...... 34 <X>/DiscoveryInformation/<X>/ AccessNetworkArea/Geo_Location/Circular/<X>/Radius ............ 22 <X>/Policy/<X>/ValidityArea/Geo_Location/Circular/<X>/ AnchorLongitude ....73A 5................................. 23 <X>/Policy/<X>/TimeOfDay/<X>/TimeStart ................................... 30 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ 3GPP2_Location/HRPD/<X> .........84A <X>/Policy/<X>/ValidityArea/Geo_Location/Circular/<X>/ AnchorLatitude ....................83 5.......................................................................0 Release 9 4 ETSI TS 124 312 V9...................................................................80 5.....76C 5...... 30 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ 3GPP2_Location/HRPD/<X>/Sector_ID .......................................... 27 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ 3GPP_Location/<X>/TAC ..... 29 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ 3GPP2_Location/1x/<X>/Base_ID ..........................................................56 5............ 30 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ WiMAX_Location ......................58B 5.....71 5....................... 35 <X>/UE_Location/3GPP_Location ................................................ 23 <X>/Policy/<X>/TimeOfDay/<X>/TimeStop .....58 5..........................72 5..............0 (2010-01) 5........................79 5........... 27 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ 3GPP_Location/<X>/GERAN_CI .................................................................................................................................... 34 <X>/UE_Location .48 5...............................................................................................................36E 5........................ 27 <X>/DiscoveryInformation/<X>/ AccessNetworkArea/3GPP_Location/<X>/UTRAN_CI ..................76D 5.............. 33 <X>/DiscoveryInformation/<X>/ AccessNetworkArea /Geo_Location/Circular/<X> .......................................................................................................................................... 25 <X>/DiscoveryInformation/<X>/AccessNetworkArea ....................................................81 5......... 33 <X>/DiscoveryInformation/<X>/ AccessNetworkArea /Geo_Location/Circular ........................51 5. 25 <X>/DiscoveryInformation/<X>/AccessNetworkType .......................................................... 33 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ Geo_Location .......................0.............................. 34 <X>/DiscoveryInformation/<X>/ AccessNetworkInformationRef ..................0.................... 25 Void .............82 5.................................................................................. 31 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ WiMAX_Location/<X>/BS-ID .....49 5.........78 5.................................... 23 <X>/Policy/<X>/TimeOfDay/<X> ........................... 29 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ 3GPP2_Location/HRPD............................................................................................................................36C 5.................... 26 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ 3GPP_Location/<X>/PLMN ......................................................................................................63 5................................ 25 Void .... 36 <X>/UE_Location/3GPP_Location/<X>/ UTRAN_CI ....................................................... 25 <X>/DiscoveryInformation/<X> ...................76E 5.................................. 22 <X>/Policy/<X>/ValidityArea/Geo_Location/Circular/<X>/ Radius ........62 5.....38 5................................................73 5..............76A 5.. 27 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ 3GPP_Location/<X>/LAC .................................................46 5........................70 5..... 29 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ 3GPP2_Location/1x/<X>/SID ......................................................... 22 <X>/Policy/<X>/PLMN ..........................................59 5........ 25 <X>/Policy/<X>/UpdatePolicy ...............312 version 9..............................................................................................61 5...................41 5.......................................................................................... 32 <X>/DiscoveryInformation/<X>/AccessNetworkArea /WLAN_Location/<X>/SSID ...................................................... 32 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ WLAN_Location/<X>/BSSID .......................................................84 5.............54 5.... 34 <X>/DiscoveryInformation/<X>/ AccessNetworkArea/Geo_Location/Circular/<X>/AnchorLongitude................... 24 <X>/Policy/<X>/TimeOfDay/<X>/DateStart.......................................................... 32 <X>/DiscoveryInformation/<X>/AccessNetworkArea /WLAN_Location/<X>/HESSID .............................37 5...... 35 <X>/UE_Location/3GPP_Location/<X>/TAC ......53 5...............................76B 5......................... 35 <X>/UE_Location/3GPP_Location/<X> ..............45 5.........................................65 5............................................. 26 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ 3GPP_Location/<X> ............................................................. 28 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ 3GPP2_Location/1x ...........................................................50 5..69 5....... 28 <X>/DiscoveryInformation/<X>/ AccessNetworkArea/3GPP_Location/<X>/EUTRA_CI ...60 5.................................................................... 25 Void ...................... 28 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ 3GPP2_Location/1x/<X> .......... 32 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ WLAN_Location/<X> ..........................57 5................ 30 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ 3GPP2_Location/HRPD/<X>/Netmask............67 5................................................................................................................................................... 33 <X>/DiscoveryInformation/<X>/ AccessNetworkArea/Geo_Location/Circular/<X>/AnchorLatitude ................................................ 24 <X>/Policy/<X>/TimeOfDay/<X>/DateStop ......................... 31 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ WiMAX_Location/<X>.....................75 5.................... 22 <X>/Policy/<X>/Roaming ................77 5.....55 5....................66 5................ 36 ETSI .................47 5.............................39 5........................... 23 <X>/Policy/<X>/TimeOfDay.....................................43 5.................................74 5....44 5....................67A 5..................................................... 25 <X>/DiscoveryInformation................................. 28 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ 3GPP2_Location .....52 5............................... 31 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ WLAN_Location ...... 35 <X>/UE_Location/3GPP_Location/<X>/PLMN .................37A 5................................................................................ 24 Void .....68 5...................................... 26 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ 3GPP_Location ................................................ 31 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ WiMAX_Location/<X>/NAP-ID ......................... 36 <X>/UE_Location/3GPP_Location/<X>/GERAN_CI ....................................................................... 35 <X>/UE_Location/3GPP_Location/<X>/LAC ........40 5......................................... 29 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ 3GPP2_Location/1x/<X>/NID ...............................................................................64 5.............................................................................58A 5.36D 5.................................................................................................................42 5...........................3GPP TS 24..............................................76 5......................

...3..........................................0................... 42 Introduction ..................................................................................... 38 <X>/UE_Location/3GPP2_Location/HRPD/<X>/Sector_ID ................ 45 <X>/NetworkList/<X>/ FrequencyInfo/<X>ChannelBandwidth ....................... 44 <X>/NetworkList/<X>/FrequencyInfo/<X> .................................... 39 <X>/UE_Location/WiMAX_Location/<X>/NAP-ID ..3GPP TS 24............................................................................................................................................................ 44 <X>/NetworkList/<X>/FrequencyInfo/<X>FirstFreq .............3....................................3.................................................................................93A 5....................... 43 Node: <X> ...2 6........................................... 43 General........ 46 <X>/Ext ......................96 5...............................97 5.....3.......................................3.............3 6....................... 40 <X>/UE_Location/WLAN_Location/<X>/BSSID ....................15 6.................................................................................................................... 43 <X>/NetworkList/<X> ................................................... 46 <X>/NetworkList/<X>/CellType .................. 37 <X>/UE_Location/3GPP2_Location/1x ...................................... 47 6 6...............................................................................87 5......................................................................... 40 <X>/UE_Location/WLAN_Location ..8 6.....................................102 5..............................3................................................. 41 <X>/UE_Location/Geo_Location/...................................................................................... 39 <X>/UE_Location/WiMAX_Location/<X> ................................................................................................................................... 43 <X>/Name ..............................................................2 6..............................85 5.......... 45 <X>/NetworkList/<X>/ FrequencyInfo/<X>FFT_Size ..........................................3...............11 6.............3......................................86 ETSI .............................................99 5....42 Annex A (informative): Annex B (informative): Annex C (informative): ANDSF MO DDF ................102B 5.80 Change history ......................................................... 42 WNDS MO parameters ...102D 5..........................16 6................100 5...............................0..................... 37 <X>/UE_Location/3GPP2_Location/1x/<X>/Base_ID .... 43 <X>/NetworkList .................................................................................................... 40 <X>/UE_Location/WLAN_Location/<X> ...........................................................................................................................................88 5................................0 Release 9 5 ETSI TS 124 312 V9......................................................12 6.. 39 <X>/UE_Location/WiMAX_Location ...3....................... 38 <X>/UE_Location/3GPP2_Location/HRPD/<X>/Netmask ..... 40 <X>/UE_Location/WLAN_Location/<X>/HESSID ....... 37 <X>/UE_Location/3GPP2_Location/1x/<X>/NID ..................... 45 <X>/NetworkList/<X>/ FrequencyInfo/<X>DuplexMode ............................................................................................1 6....................................................................................................................................9 6..............................................................................................................102A 5.....................312 version 9................................................................................................... 41 <X>/ UE_Location /RPLMN ............................................................................................... 42 <X>/Ext ............................................................................................................................................................................. 42 WNDS MO ..............3.................................................................................................................................. 41 <X>/ UE_Location /Geo_Location/Longitude .............................................1 6.............6 6............................3....................................3 6..................................................................................... 41 <X>/ UE_Location /Geo_Location/Latitude ..... 36 <X>/UE_Location/3GPP2_Location .................................................................................................................................7 6.......................................10 6......... 44 <X>/NetworkList/<X>/FrequencyInfo .................................................... 44 <X>/NetworkList/<X>/FrequencyInfo/<X>NextFreqStep ...............................................................................................................................................................................................................................................................................................................................................................91 5..........102C 5.......................85 History .........................................93 5................. 39 <X>/UE_Location/WiMAX_Location/<X>/BS-ID .............3.3.......99A 5.................................................................................................94 5................................................................3......................................3.......48 WNDS MO DDF ..........................................101 5.................................3.......... 46 <X>/ NetworkList /<X>/NAP-ID ..............18 MO for WiMAX........................................90 5.....103 <X>/UE_Location/3GPP_Location/<X>/ EUTRA_CI ...........................................................................................................................................................86 5.................................................................... 40 <X>/UE_Location/WLAN_Location/<X>/SSID ....................14 6.................................... 37 <X>/UE_Location/3GPP2_Location/1x/<X> ........................................................................... 38 <X>/UE_Location/3GPP2_Location/HRPD/<X> ................13 6.......................................92 5........................................ 41 Void ...............................................3..................................................................................................... 46 <X>/NetworkList/<X>/OperatorDifferentiatedTextField ....................................3.......................................... 38 <X>/UE_Location/3GPP2_Location/HRPD ..........................0 (2010-01) 5.................89 5...............95 5................................................................................................................... 46 <X>/NetworkList/<X>/ FrequencyInfo/<X>Preambles ............................................................................. 44 <X>/NetworkList/<X>/FrequencyInfo/<X>LastFreq ..............................4 6............. 37 <X>/UE_Location/3GPP2_Location/1x/<X>/SID.........17 6.........84B 5...........................................................................................5 6..................................................98 5................

y the second digit is incremented for all changes of substance.0.y. it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.0 Release 9 6 ETSI TS 124 312 V9. ETSI . technical enhancements. Should the TSG modify the contents of the present document. 2 presented to TSG for approval. i.3GPP TS 24.312 version 9.z where: x the first digit: 1 presented to TSG for information.0. 3 or greater indicates TSG approved document under change control. The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. corrections. updates.0 (2010-01) Foreword This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).e. z the third digit is incremented when editorial only changes have been incorporated in the document. etc.

2.402 [4] respectively.and access network discovery information that can be managed by the ANDSF. The service requirements and the functional requirements for the access network discovery and selection are described in 3GPP TS 22.0.331: "Radio Resource Control (RRC).302: "Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks". WiMAX Forum Network Architecture Release 1. In the case of a reference to a 3GPP document (including a GSM document).331: "Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Resource Control (RRC).0.032: "Universal Geographical Area Description (GAD)". ETSI .2 and upwards. 2 References • References are either specific (identified by date of publication. Approved Version 1.0 version 1. 3GPP TS 23. OMA-DDS-DM_ConnMO-V1_0. and is defined using the OMA DM Device Description Framework (DDF) as described in the Enabler Release Definition OMA-ERELD-DM-V1_2 [5].3GPP TS 24. 3GPP TS 25. addressing and identification". OMA-DDS-DM_ConnMO_WLAN-V1_0-20081024-A: 'Standardized Connectivity Management Objects WLAN Parameters'. The Management Object (MO) is compatible with the OMA Device Management (DM) protocol specifications. through reference in this text. 3GPP TS 24. 3GPP TS 36.0 – 07 Nov 2008. The MO consists of relevant parameters for intersystem mobility policy. subsequent revisions do not apply.003: "Numbering.0 – 24 Oct 2008. OMA-ERELD-DM-V1_2: "Enabler Release Definition for OMA Device Management". version number. Protocol specification". constitute provisions of the present document.20081107-A: "Standardized Connectivity Management Objects". The following documents contain provisions which. 3GPP TS 22. • For a specific reference. etc.312 version 9.278 [2] and in 3GPP TS 23. a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.) or non-specific. • For a non-specific reference.0 Release 9 7 ETSI TS 124 312 V9.2 – Stage 3: "Detailed Protocols and Procedures". 3GPP TS 23.2 – Stage 2: "Architecture Tenets. Approved Version 1.2.0 (2010-01) 1 Scope The present document defines management objects that can be used by the Access Network Discovery and Selection Function (ANDSF) and the UE.402: "Architecture enhancements for non-3GPP accesses".905: "Vocabulary for 3GPP Specifications". 3GPP TS 23. [1] [2] [3] [3A] [3AA] [3B] [3C] [4] [4A] [4B] [5] [6] [7] 3GPP TR 21. Reference Model and Reference Points". edition number.278: "Service requirements for the Evolved Packet System (EPS)". the latest version applies. May 2008. WiMAX Forum Network Architecture Release 1. May 2008.0 version 1. Protocol Specification". version 1.

302 [3AA]. 3.1.S0024-0: "cdma2000 High Rate Packet Data Air Interface Specification".0 Release 9 8 ETSI TS 124 312 V9. April 2007.0.312 version 9.S0016: "Over-the-Air Service Provisioning of Mobile Stations in Spread Spectrum Standards". "Unicode 5. a transformation format of ISO 10646".16-2004/Cor1-2005: "IEEE Standard for Local and Metropolitan Area Networks.0. March 2008.0 Approved Specification Revision 1.unicode.Telecommunications and information exchange between systems-Local and metropolitan area networks-Specific requirements-Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications". February 2006.16e-2005 and IEEE Std 802. IEEE Std 802. IETF RFC 3629 (November 2003): "UTF-8. Part 16: Air Interface for Fixed and Mobile Broadband Wireless Access Systems Amendments 2 and Corrigendum 1". Unicode Standard Annex #15.4.Information interchange -Representation of dates and times" IEEE 802.3 ANDSF DDF DM MO OMA RSSI UE WNDS Abbreviations Access Network Discovery and Selection Function Device Description Framework Device Management Management Object Open Mobile Alliance Receive Signal Strength Indicator User Equipment WiMAX Network Discovery and Selection For the purposes of the present document.as well as access network discovery information stored in a UE supporting provisioning of such information from an ANDSF. 3GPP2 C.11™-2007: "Information Technology. IEEE Std 802. ISO 8601:2004: "Data elements and interchange formats -. 3GPP2 C.0.11u: "Draft Amendment to Standard for Information Technology . the following abbreviations apply: 4 ANDSF MO The ANDSF MO is used to manage intersystem mobility policy. The ANDSF may initiate the provision of information from the ANDSF to the UE as specified in 3GPP TS 24. Unicode Normalization Forms".3GPP TS 24.0. http://www.Telecommunications and information exchange between systems-Local and metropolitan area networks-Specific requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications: Amendment 7: Interworking with External Networks" [10] [11] [12] [13] [14] [15] [16] [17] 3 3.org 3GPP2 C. ETSI .1 Definitions and abbreviations Definitions For the purposes of the present document.0 (2010-01) [8] [9] WiMAX Forum Mobile System Profile Release 1.S0005: "Upper Layer (Layer 3) Signaling Standard for cdma2000 Spread Spectrum Systems".905 [1] apply. the terms and definitions given in 3GPP TR 21.

0. using a client initiated session alert message of code "Generic Alert". The trigger for (re-)evaluating rules is that the 'active' rule becomes invalid (conditions no longer fulfilled).0:provision". In addition to conditions and results there is a rule-priority that shall be set for each rule in order for the UE to determine which rule.1: ETSI . The rules also have a number of results (e. The way such coordinates are retrieved is implementation dependant (e.e. The MO defines validity areas. current access technology and location) where one or more may be present and set to a value.g. the highest priority rule becomes 'active' rule and network re-selection is performed.0.3GPP TS 24. If there are no results for the 'active' rule.0 Release 9 9 ETSI TS 124 312 V9. while DiscoveryInformation provide further information for the UE to access the access network defined in the policy. The OMA DM Access Control List (ACL) property mechanism as standardized (see Enabler Release Definition OMAERELD-DM-V1_2 [5]) may be used to grant or deny access rights to OMA DM servers in order to modify nodes and leaf objects of the ANDSF MO. The UE is not required to switch on all UE's supported radios for deducing its location for ANDSF purposes or for evaluating the validity area condition of a policy or a discovery information. The MO has a node indicating the position of the UE. The Management Object Identifier is: urn:oma:mo:ext-3gpp-andsf:1. While the rule remains 'active'.g. which must all match in order to make the Policy valid. The rules have a number of conditions (e. The intersystem mobility policy information consists of a set of one or more intersystem mobility policy rules. than currently selected.0 (2010-01) The UE may initiate the provision of information from the ANDSF. The "Type" element of the OMA DM generic alert message shall be set to "urn:oma:at:ext-3gppandsf:1. The update of the information contained in this node doesn"t necessarily imply any interaction with the ANDSF server.312 version 9. The relation between Policy and DiscoveryInformation is that Policies prioritize the access network. it is implementation dependent how UE performs network selection. The following nodes and leaf objects are possible under the ANDSF node as described in figure 4. UE shall keep considering higher priority networks. preferred access technology and restricted access technology) to be used whenever a rule is 'active'. it should consider as 'active'. that rule is referred to as the 'active' rule. The validity of the policy takes into account ValidityArea. the UE has changed its position) or some other manufacturer specific trigger. position of the UE and availability of access networks in terms of geographical coordinates. Irrespective of whether any rule is 'active' or not. or some other manufacturer specific trigger.g. When ANDSF policy selection rules identify an available network. out of potentially several valid rules. At any point in time there shall be at most one rule applied. the UE shall periodically re-evaluate ANDSF policies. in the prioritized network list of the rule. There may hence be zero or one 'active' rule. GPS receiver). PLMN and TimeOfDay.0. The trigger for updating the value of this node is that the location information it contains is no longer valid (i. Roaming.

0.312 version 9.0.1: The ANDSF MO ETSI .0 Release 9 10 ETSI TS 124 312 V9.0 (2010-01) <X> Name ? Policy ? <X> + RulePriority PrioritizedAccess ValidityArea ? Roaming ? PLMN <X> + AccessTechnology AccessId ? SecondaryAccessId ? AccessNetworkPriority 3GPP_Location ? 3GPP2_Location ? WiMAX_Location ? WLAN_Location ? Geo_Location ? Circular ? <X> + <X> + AnchorLatitude AnchorLongitude Radius TimeStart ? TimeStop ? DateStart ? DateStop ? AccessNetworkType AccessNetworkArea TimeOfDay ? UpdatePolicy ? <X> + PLMN TAC ? LAC ? GERAN_CI ? UTRAN_CI ? <X> + EUTRA_CI ? SID 1x ? <X> + NID ? Base_ID ? HRPD ? <X> + Sector_ID Netmask <X> + NAP-ID PLMN BS-ID TAC ? <X> + HESSID ? <X> + LAC ? SSID ? GERAN_CI ? BSSID UTRAN_CI ? 3GPP_Location ? EUTRA_CI ? SID 3GPP2_Location ? NID ? Base_ID ? 1x ? <X> + Sector_ID HRPD ? <X> + Netmask WiMAX_Location ? WLAN_Location ? Geo_Location ? <X> + NAP-ID BS-ID <X> + HESSID ? SSID ? BSSID AnchorLatitude AnchorLongitude Radius SID NID ? Base_ID ? Sector_ID Netmask DiscoveryInformation ? UE_Location ? AccessNetworkInformationRef ? 3GPP_Location ? <X> + 3GPP2_Location ? 1x ? HRPD ? WiMAX_Location ? WLAN_Location ? Ext ? Geo_Location ? RPLMN ? <X> + <X> + Circular ? <X> + PLMN TAC ? LAC ? GERAN_CI ? UTRAN_CI ? EUTRA_CI ? <X> + <X> + NAP-ID BS-ID HESSID ? SSID ? BSSID AnchorLongitude AnchorLatitude Figure 4.3GPP TS 24.

312 version 9. Replace Values: N/A This interior node acts as a placeholder for one or more intersystem mobility policy rules. 5.2 - Node: <X> Occurrence: ZeroOrOne Format: node Access Types: Get Values: N/A This interior node acts as a placeholder for zero or one accounts for a fixed node.0.3 - <X>/Name Occurrence: ZeroOrOne Format: chr Access Types: Get Values: <User displayable name> The Name leaf is a name for the ANDSF MO settings. ETSI .5 - <X>/Policy/<X> Occurrence: OneOrMore Format: node Access Types: Get. 5. Unicode Normalization Forms [12].0 Release 9 11 ETSI TS 124 312 V9.3GPP TS 24.1 ANDSF MO parameters General This clause describes the parameters for the ANDSF MO.4 - <X>/Policy Occurrence: ZeroOrOne Format: node Access Types: Get.0 (2010-01) 5 5. The User displayable name shall be represented by Unicode characters encoded as UTF-8 as specified in IETF RFC 3629 [11] and formatted using Normalization Form KC (NFKC) as specified in Unicode Standard Annex #15. Replace Values: N/A The Policy node acts as a placeholder for policies for intersystem mobility. 5. 5.0.

Replace Values: <Access technology> The AccessTechnology leaf indicates a prioritized access technology. Replace Values: <Rule priority> The RulePriority leaf represents the priority given to one particular rule and is represented as a numerical value. If there are overlapping rules (e. - Possible values for the Access technology are specified in table 5.0 Release 9 12 ETSI TS 124 312 V9. If the UE finds multiple rules with the same priority.3GPP TS 24.9 <X>/Policy/<X>/PrioritizedAccess/<X>/ AccessTechnology Occurrence: One Format: int Access Types: Get.0 (2010-01) 5. they should not have the same priority. Replace Values: N/A This interior node acts as a placeholder for one or more prioritized accesses. 5. In case more than one valid intersystem mobility policy rule exists. If there are no matching access networks according to the rule.0.g. Replace Values: N/A The PrioritizedAccess node indicates the preferred access for one particular rule. rule by PLMN). ETSI . the choice of the rule is UE implementation specific. the UE shall treat the rule with the lowest RulePriority value as the rule having the highest priority among the valid rules. 5.7 - <X>/Policy/<X>/PrioritizedAccess Occurrence: One Format: node Access Types: Get.0.312 version 9.9.8 - <X>/Policy/<X>/PrioritizedAccess/<X> Occurrence: OneOrMore Format: node Access Types: Get.6 - <X>/Policy/<X>/RulePriority Occurrence: One Format: int Access Types: Get. by location. other rules with the same priority shall be considered. for example: rule by CGI.1. 5.

1: Possible values for the AccessTechnology leaf Value 0 1 3 4 5-255 Reserved 3GPP WLAN WiMAX Reserved Description 5.0 Release 9 13 ETSI TS 124 312 V9.0. Replace Values: <HESSID> The SecondaryAccessId contains an identifier for a specific radio access network.312 version 9. Only HESSID for WLAN radio access network is contained in this leaf.0. The AccessId be represented by Unicode characters encoded as UTF-8 as specified in IETF RFC 3629 [11] and formatted using Normalization Form KC (NFKC) as specified in Unicode Standard Annex #15. 5. Occurrence: One Format: int Access Types: Get. The format of the HESSID is defined by IEEE 802.3GPP TS 24. Occurrence: ZeroOrOne Format: chr Access Types: Get. Replace Values: <Access id> The AccessId contains an identifier for a specific radio access network.10A <X>/Policy/<X>/PrioritizedAccess/<X>/ SecondaryAccessId The SecondaryAccessId leaf represents a secondary access network identifier. 5. AccessIds in numerical format shall be encoded as character string.11 <X>/Policy/<X>/PrioritizedAccess/<X>/ AccessNetworkPriority The AccessNetworkPriority leaf represents an access technology priority. Replace Values: <Access network priority> ETSI . Occurrence: ZeroOrOne Format: chr Access Types: Get. The SecondaryAccessId leaf may only be present when the corresponding AccessId leaf for a WLAN radio access network is present.10 <X>/Policy/<X>/PrioritizedAccess/<X>/ AccessId The AccessId leaf represents an access network identifier.0 (2010-01) Table 5. Unicode Normalization Forms [12]. Only SSID for WLAN and NAP-ID for WiMAX radio access network are contained in this leaf.9.11u [17].

If the UE is not able to find an access network according to ANDSF policies. RulePriority leaf is used as discriminator. The same AccessNetworkPriority value may be used for more than one AccessId and more than one Access Technology. If more than one AccessId or more than one Access Technology with the same value of the AccessNetworkPriority are avilable.1: Values of AccessNetworkPriority leaf Value 0 1-250 251-253 254 255 Description Reserved Priority value Reserved Restricted access. 5. Replace Values: N/A This is considered to be fulfilled if at least one of 3GPP_Location.0 Release 9 14 ETSI TS 124 312 V9.13 - <X>/Policy/<X>/ValidityArea/3GPP_Location The 3GPP_Location node acts as a placeholder for 3GPP location descriptions.0.0. NOTE: It is implementation dependent if or when a restricted access is selected if there are no other accesses available. The AccessNetworkPriority value 'Forbidden' (255) indicates an access that shall not be used by the UE. the UE selects one of them in an implementation dependant way. or WLAN_Loaction. Table 5. The AccessNetworkPriority value 'Restricted access' (254) indicates an access that should not be used by the UE. Occurrence: ZeroOrOne Format: node Access Types: Get. or 3GPP2_Location or WiMAX_Location. UE is not allowed to use this access if the current rule is active. Occurrence: OneOrMore ETSI .312 version 9.11. only rules without Validity Area can be considered for active rule. Replace Values: N/A If the UE is currently aware that it is located in the coverage area described by this node.12 - <X>/Policy/<X>/ValidityArea The ValidityArea node acts as a placeholder for location conditions for a particular rule. or Geo_Location is a match. as defined in table 5. the UE shall consider the corresponding rule as valid.0 (2010-01) In case more than one valid PrioritizedAccess are available and if the value of the priority belongs to the range 1-250. Occurrence: ZeroOrOne Format: node Access Types: Get.14 - <X>/Policy/<X>/ValidityArea/3GPP_Location/<X> This interior node acts as a placeholder for one or more 3GPP location descriptions. it is implementation dependent how to proceed with network selection. In case of overlapping validity domains of multiple policy rules.11. 5. If UE is not able to deduce its location by any means.1. 5. Forbidden. This access should be avoided if the current rule is active. the UE shall consider the access network (with the corresponding access identifier if present) with the lowest AccessNetworkPriority value as the access network (with the corresponding access identifier if present) having the highest priority.3GPP TS 24.

0 Release 9 15 ETSI TS 124 312 V9. 5.16 <X>/Policy/<X>/ValidityArea/3GPP_Location/<X>/TAC The TAC leaf indicates a Tracking Area Code for one particular 3GPP location condition for the intersystem mobility policy rule.17 <X>/Policy/<X>/ValidityArea/3GPP_Location/<X>/LAC The LAC leaf indicates a Location Area Code for one particular 3GPP location condition for the intersystem mobility policy rule. Occurrence: ZeroOrOne Format: chr Access Types: Get. Replace Values: N/A 5.003 [3].312 version 9. Occurrence: One Format: chr Access Types: Get.15 <X>/Policy/<X>/ValidityArea/3GPP_Location/<X>/PLMN The PLMN leaf indicates a PLMN code for one particular 3GPP location condition for the intersystem mobility policy rule.003 [3]. 5. Replace ETSI .003 [3].0.3GPP TS 24. 5. Occurrence: ZeroOrOne Format: chr Access Types: Get.0 (2010-01) - Format: node Access Types: Get. Replace Values: <Tracking area code> The format of the TAC is defined by 3GPP TS 23.18 <X>/Policy/<X>/ValidityArea/3GPP_Location/<X>/GERAN_ CI The GERAN_CI leaf indicates a cell identity for one particular GERAN network related location description. Occurrence: ZeroOrOne Format: bin Access Types: Get. Replace Values: <PLMN> The format of the PLMN is defined by 3GPP TS 23. Replace Values: <Location area code> The format of the LAC is defined by 3GPP TS 23.0.

as described in 3GPP TS 36. 5. shall be provided. Replace Values: N/A If the UE is currently aware that it is located in the coverage area described by this node.331 [3C] and obtained from lower layers of the UE. or both. Occurrence: ZeroOrOne Format: node Access Types: Get. the UE shall consider the corresponding rule as valid.0. is defined in 3GPP TS 23. 5. Occurrence: ZeroOrOne Format: bin Access Types: Get.0 (2010-01) - Values: <GERAN Cell Identity> The format of the Cell Global Identity. 5.312 version 9.18A <X>/Policy/<X>/ValidityArea/3GPP_Location/ <X>/UTRAN_CI The UTRAN_CI leaf indicates a cell identity for one particular UTRAN network related location description. The value of GERAN_CI is coded as a bit string with fixed length of 16 bits.003 [3]. The GERAN_CI value is set to the Cell Identity.0 Release 9 16 ETSI TS 124 312 V9.3GPP TS 24. The value of EUTRA_CI is coded as a bit string with fixed length of 28 bits.0.003 [3]. CI. If ANDSF provides 3GPP2_Location as a validity area.18B <X>/Policy/<X>/ValidityArea/3GPP_Location/ <X>/EUTRA_CI The EUTRA_CI leaf indicates a cell identity for one particular E-UTRA network related location description. obtained from lower layers of the UE. Replace Values: <E-UTRA Cell Identity > The EUTRA_CI value is set to the cellidentity part of the Evolved Cell Global Identifier. ETSI . of which the Cell Identity is part. The value of UTRAN CI is coded as a bit string with fixed length of 28 bits.331 [3B] and obtained from lower layers of the UE. either the 1x or HRPD interior node. Replace Values: <UTRAN Cell Identity > The UTRAN_CI value is set to the UTRAN Cell Identity as defined in 3GPP TS 25. RulePriority leaf is used as discriminator.19 - <X>/Policy/<X>/ValidityArea/3GPP2_Location This 3GPP2_Location node acts as a placeholder for 3GPP2 location descriptions. Occurrence: ZeroOrOne Format: bin Access Types: Get. In case of overlapping validity domains of multiple policy rules. The CI is part of the Cell Global Identity as defined in 3GPP TS 23.

0.22 <X>/Policy/<X>/ValidityArea/3GPP2_Location/1x/<X>/ SID This SID leaf indicates a System Identification code for one particular 3GPP2 1x RAT location condition for the intersystem mobility policy rule. Occurrence: OneOrMore Format: node Access Types: Get. Replace Values: <System Identification> The format of the SID is defined by 3GPP2 C S0016 [14]. ETSI . 5.0 Release 9 17 ETSI TS 124 312 V9. Occurrence: ZeroOrOne Format: chr Access Types: Get Values: <Network Identification> The format of the NID is defined by 3GPP2 C. Replace Values: N/A 5. Replace Values: N/A 5.20 - <X>/Policy/<X>/ValidityArea/3GPP2_Location/1x This 1x node acts as a placeholder for 3GPP2 1x RAT location descriptions.312 version 9.21 - <X>/Policy/<X>/ValidityArea/3GPP2_Location/1x/<X> This interior node acts as a placeholder for one or more 3GPP2 1x RAT location descriptions.0. Occurrence: One Format: chr Access Types: Get.3GPP TS 24. Occurrence: ZeroOrOne Format: node Access Types: Get.23 <X>/Policy/<X>/ValidityArea/3GPP2_Location/1x/<X>/ NID This NID leaf indicates a Network Identification code for one particular 3GPP2 1x RAT location condition for the intersystem mobility policy rule.S0016 [14].0 (2010-01) 5.

ETSI .25 - <X>/Policy/<X>/ValidityArea/3GPP2_Location/HRPD This HRPD node acts as a placeholder for 3GPP2 HRPD RAT location descriptions. Replace Values: N/A 5. Occurrence: OneOrMore Format: node Access Types: Get. Occurrence: ZeroOrOne Format: chr Access Types: Get. Occurrence: ZeroOrOne Format: node Access Types: Get. Replace Values: <Base Station Identification> The format of the Base_ID is defined by 3GPP2 C.27 <X>/Policy/<X>/ValidityArea/3GPP2_Location/HRPD/<X>/ Sector_ID This Sector_ID leaf indicates a Sector Identification code for one particular 3GPP2 HRPD RAT location condition for the intersystem mobility policy rule. Replace Values: < Sector_ID > The format of the Sector_ID is defined by 3GPP2 C.0.24 <X>/Policy/<X>/ValidityArea/3GPP2_Location/1x/<X>/ Base_ID This Base_ID leaf indicates a Base Station Identification code for one particular 3GPP2 1x RAT location condition for the intersystem mobility policy rule.0 Release 9 18 ETSI TS 124 312 V9.0 (2010-01) 5. Occurrence: One Format: bin Access Types: Get.26 - <X>/Policy/<X>/ValidityArea/3GPP2_Location/HRPD/<X> This interior node acts as a placeholder for one or more 3GPP2 HRPD RAT location descriptions. 5. The length of Sector ID contained in this node is 128 bits.312 version 9. Replace Values: N/A 5.3GPP TS 24.0.S0024-0 [15].S0005 [13].

Occurrence: OneOrMore Format: node Access Types: Get.312 version 9. Occurrence: One Format: chr Access Types: Get.0 (2010-01) 5.0 version 1. Replace Values: N/A If the UE is currently aware that it is located in the coverage area described by this node.30 <X>/Policy/<X>/ValidityArea/WiMAX_Location/<X>/NAP-ID The NAP-ID leaf indicates the Network Access Provider for a particular WiMAX location condition for the intersystem mobility policy rule.28 - <X>/Policy/<X>/ValidityArea/WiMAX_Location The WiMAX_Location node acts as a placeholder for WiMAX location descriptions.S0024-0 [15]. ETSI .0.3GPP TS 24.2 – Stage 3 [7]. Replace Values: N/A 5. RulePriority leaf is used as discriminator.27A <X>/Policy/<X>/ValidityArea/3GPP2_Location/HRPD/<X>/ Netmask This Netmask leaf indicates a Netmask code for one particular 3GPP2 HRPD RAT location condition for the intersystem mobility policy rule.2 – Stage 2 [6] and WiMAX Forum Network Architecture Release 1. the UE shall consider the corresponding rule as valid. Occurrence: ZeroOrOne Format: node Access Types: Get. The length of Netmask contained in this node is 8 bits.29 - <X>/Policy/<X>/ValidityArea/WiMAX_Location/<X> This interior node acts as a placeholder for one or more WiMAX location descriptions.0.2.0 version 1. The mask contained in this leaf shall be applied to the Sector_ID bit string contained in the correspondent leaf of interior node <X>/Policy/<X>/ValidityArea/3GPP2_Location/HRPD/<X>/Sector_ID. 5. Replace Values: <NAP-ID> The format of the NAP-ID is defined by the WiMAX Forum Network Architecture Release 1.0 Release 9 19 ETSI TS 124 312 V9. Occurrence: One Format: bin Access Types: Get. 5. In case of overlapping validity domains of multiple policy rules.2. Replace Values: < Netmask> The format of Netmask is defined by 3GPP2 C.

312 version 9. 5.0. Replace Values: N/A If the UE is currently aware that it is located in the coverage area described by this node. the UE shall consider the corresponding rule as valid. In case of overlapping validity domains of multiple policy rules. RulePriority leaf is used as discriminator. Occurrence: ZeroOrOne Format: node Access Types: Get. Occurrence: ZeroOrOne Format: chr Access Types: Get. Occurrence: OneOrMore Format: node Access Types: Get.33A <X>/Policy/<X>/ValidityArea/WLAN_Location/<X>/HESSID The HESSID leaf indicates the HESSID for a particular WLAN location condition for the intersystem mobility policy rule.33 - <X>/Policy/<X>/ValidityArea/WLAN_Location/<X> This interior node acts as a placeholder for one or more WLAN location descriptions.34 <X>/Policy/<X>/ValidityArea/WLAN_Location/<X>/SSID The SSID leaf indicates the SSID for a particular WLAN location condition for the intersystem mobility policy rule.0 Release 9 20 ETSI TS 124 312 V9. Replace Values: <HESSID> The format of the HESSID is defined by IEEE 802.32 - <X>/Policy/<X>/ValidityArea/WLAN_Location The WLAN_Location node acts as a placeholder for WLAN location descriptions.0. Replace Values: N/A 5.16e-2005 and IEEE Std 802.31 <X>/Policy/<X>/ValidityArea/WiMAX_Location/<X>/BS-ID The BS-ID leaf indicates the BS identifier for a particular WiMAX location condition for the intersystem mobility policy rule. 5. Occurrence: One Format: chr Access Types: Get.3GPP TS 24. ETSI . Replace Values: <BS-ID> The format of the BS-ID is defined by the IEEE Std 802.16-2004/Cor1-2005 [10].0 (2010-01) 5. 5.11u [17].

312 version 9.36A <X>/Policy/<X>/ValidityArea/Geo_Location/Circular The Circular node acts as a placeholder for circular areas location descriptions for one intersystem mobility policy rule.0 Release 9 21 ETSI TS 124 312 V9.36 <X>/Policy/<X>/ValidityArea/Geo_Location The Geo_Location node acts as a placeholder for Geographical location descriptions for one intersystem mobility policy rule.0 (2010-01) - Occurrence: ZeroOrOne Format: chr Access Types: Get.3GPP TS 24.11™-2007 [9].0.35 <X>/Policy/<X>/ValidityArea/WLAN_Location/<X>/BSSID The BSSID leaf indicates the AP identifier for one particular WLAN location condition for the intersystem mobility policy rule.0. RulePriority leaf is used as discriminator. In case of overlapping validity domains of multiple policy rules. Replace Values: <SSID> The format of the SSID is defined by IEEE Std 802.36B <X>/Policy/<X>/ValidityArea/Geo_Location/Circular/<X> The interior node acts as a placeholder for one or more circular area location descriptions for one intersystem mobility policy rule. 5. Replace Values: N/A 5. Occurrence: ZeroOrOne Format: node Access Types: Get. 5. Replace Values: <BSSID> The format of the BSSID is defined by IEEE Std 802. Occurrence: One Format: chr Access Types: Get. Occurrence: ZeroOrOne Format: node Access Types: Get. the UE shall consider the corresponding rule as valid. Occurrence: OneOrMore Format: node ETSI .11™-2007 [9]. Replace Values: N/A If the UE is currently aware that it is located in the area described by this node. 5.

5. Replace Values: < Radius> The Radius is given in meters and is defined in subclause 6.0.312 version 9. Occurrence: ZeroOrOne Format: bool Access Types: Get. Replace Values: 0.37 - <X>/Policy/<X>/Roaming The Roaming leaf indicates the roaming condition for the intersystem mobility policy rule. 1 ETSI .1 of 3GPP TS 23. 5.36D <X>/Policy/<X>/ValidityArea/Geo_Location/Circular/<X>/ AnchorLongitude The AnchorLongitude node acts as a placeholder for the longitude value of the centre of the circular area. Occurrence: One Format: int Access Types: Get. Occurrence: One Format: bin Access Types: Get.3GPP TS 24. 5. Replace Values: <N/A > 5.36E <X>/Policy/<X>/ValidityArea/Geo_Location/Circular/<X>/ Radius The Radius node acts as a placeholder for the radius value of the circular area.0.032 [3A]. Occurrence: One Format: bin Access Types: Get.032 [3A].1 of 3GPP TS 23.032 [3A]. Replace Values: < Longitude > The Longitude is defined in subclause 6.0 (2010-01) - Access Types: Get. Replace Values: < Latitude> The Latitude is defined in subclause 6.6 of 3GPP TS 23.0 Release 9 22 ETSI TS 124 312 V9.36C <X>/Policy/<X>/ValidityArea/Geo_Location/Circular/<X>/ AnchorLatitude The AnchorLatitude node acts as a placeholder for the latitude value of the center of the circular area.

5.0 Release 9 23 ETSI TS 124 312 V9. which created this policy.312 version 9. 5. matches at least one time interval indicated in the TimeOfDay node. 5. 5.39 - <X>/Policy/<X>/TimeOfDay/<X> This interior node acts as a placeholder for one or more time of day condition for the intersystem mobility policy rule. NOTE: When the UE is roaming. Occurrence: ZeroOrOne Format: node Access Types: Get.40 <X>/Policy/<X>/TimeOfDay/<X>/TimeStart The TimeStart leaf acts as a place holder containing the time of the day that indicates when the UE shall start to apply the intersystem policy rule. 1 Indicates that the rule is only valid when the UE is roaming.003 [3].3GPP TS 24.g. with TimeStart-TimeStop pair and DateStartDateStop pair).37A <X>/Policy/<X>/PLMN The PLMN leaf indicates a PLMN code of the operator.38 - <X>/Policy/<X>/TimeOfDay The TimeOfDay node indicates the time of day condition for the intersystem mobility policy rule. The UE shall consider a rule with the Roaming leaf present as valid only if the current roaming state (roaming/not roaming) of the UE matches the one indicated in the Roaming value. UE that does not support calendar or clock application does not need to interpret the TimeOfDay leaf. ETSI . how it discovers and interacts with the ANDSF is not specified in the specification of this release.0.0 (2010-01) 0 Indicates that the rule is only valid when the UE is not roaming. Replace Values: N/A The UE shall consider a rule with the TimeOfDay present as valid only if the time of day in the current time zone. Occurrence: One Format: chr Access Types: Get. Occurrence: OneOrMore Format: node Access Types: Get. Replace Values: N/A If the time interval is indicated with more than one leaf value pair (e. Replace Values: <PLMN> The format of the PLMN is defined by 3GPP TS 23. as indicated by the UE.0. the UE shall consider a rule with the TimeOfDay present as valid only if all the leaf value pairs in the node match with the time indicated by the UE.

as defined in ISO 8601:2004 [16]. as defined in ISO 8601:2004 [16]. the UE shall consider as validity period of the policy the time starting at TimeStart and ending at TimeStop of the following day. Replace Values: <date> The value this leaf can assume is a date represented in string format.43 <X>/Policy/<X>/TimeOfDay/<X>/DateStop The DateStop leaf acts as a place holder containing the date that indicates when the UE shall stop to apply the intersystem policy rule. as defined in ISO 8601:2004 [16].e.0 (2010-01) - Occurrence: ZeroOrOne Format: chr Access Types: Get. The UE handling of semantical error where DateStart node indicates a date that does not exist is UE implementation specific. Replace Values: <time of day> The value this leaf can assume is time of the day represented in string format.0.41 <X>/Policy/<X>/TimeOfDay/<X>/TimeStop The TimeStop leaf node acts as a place holder containing the time of the day that indicates when the UE shall stop to apply the intersystem policy rule. Replace Values: <time of day> The value this leaf can assume is time of the day represented in string format.0. Occurrence: ZeroOrOne Format: chr Access Types: Get. ETSI . 5. 5. Replace Values: <date> The value this leaf can assume is a date represented in string format. Occurrence: ZeroOrOne Format: chr Access Types: Get. a later date) than the value of corresponding DateStart leaf.42 <X>/Policy/<X>/TimeOfDay/<X>/DateStart The DateStart leaf acts as a place holder containing the date that indicates when the UE shall start to apply the intersystem policy rule. If within the same occurrence of TimeOfDay the value of TimeStop is smaller than TimeStart.312 version 9. as defined in ISO 8601:2004 [16].0 Release 9 24 ETSI TS 124 312 V9.3GPP TS 24. 5. The value of this leaf shall be greater (i. Occurrence: ZeroOrOne Format: chr Access Types: Get. The UE handling of semantical error where DateStop node indicates a date that does not exist is UE implementation specific.

1 0 Indicates that the UE is not required to request an update of the rules.46 5. 5.312 version 9.51 <X>/DiscoveryInformation/<X>/AccessNetworkType The AccessNetworkType leaf represents the type of an access network. Occurrence: ZeroOrOne Format: bool Access Types: Get.3GPP TS 24. Replace Values: N/A The operator may provide information on available access networks through the ANDSF.0 (2010-01) 5.48 - Void Void Void Void <X>/Policy/<X>/UpdatePolicy The UpdatePolicy leaf indicates the update policy for the intersystem mobility policy rule.0.45 5.47 5.49 - <X>/DiscoveryInformation The DiscoveryInformation node acts as a placeholder for access network discovery information. Occurrence: OneOrMore Format: node Access Types: Get. Replace Values: N/A 5. The UE may use the information as an aid in discovering other access networks. 1 Indicates that the UE is required to request an update of the rules. The UpdatePolicy value may be used by the UE to determine whether or not to request an update of its intersystem mobility policy when the rule is no longer considered to be valid by the UE.0 Release 9 25 ETSI TS 124 312 V9. Occurrence: ZeroOrOne Format: node Access Types: Get.44 5. 5. ETSI .50 - <X>/DiscoveryInformation/<X> This interior node acts as a placeholder for one or more access network information elements. Replace Values: 0.0.

Replace Values: N/A ETSI . Occurrence: ZeroOrOne Format: node Access Types: Get.312 version 9. the networks described in the correspondent AccessNetworkInformationRef are expected to be available.1.3GPP TS 24.0. Replace Values: N/A If the UE is currently aware that it is located in the coverage area described by this node. Replace Values: <Access network type> The value of AccessNetworkType indicates the type of the network for which discovery assistance information is provided.0. Table 5.52 <X>/DiscoveryInformation/<X>/AccessNetworkArea The AccessNetworkArea node acts as a placeholder for a description of the location where one particular access network is expected to be available. Possible values are specified in table 5.53 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ 3GPP_Location The 3GPP_Location node acts as a placeholder for 3GPP location descriptions. Replace Values: N/A 5.1: Possible values for the AccessNetworkType leaf Value 0 1 3 4 5-255 Reserved 3GPP WLAN WiMAX Reserved Description 5. 5.54 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ 3GPP_Location/<X> This interior node acts as a placeholder for one or more 3GPP location descriptions.51.0 (2010-01) - Occurrence: One Format: int Access Types: Get. Occurrence: One Format: node Access Types: Get.51. Occurrence: OneOrMore Format: node Access Types: Get.0 Release 9 26 ETSI TS 124 312 V9.

58 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ 3GPP_Location/<X>/GERAN_CI The GERAN_CI leaf indicates a GERAN Cell Identity for one particular 3GPP network related location description.57 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ 3GPP_Location/<X>/LAC This LAC leaf indicates a Location Area Code for one particular 3GPP location description.0.18.312 version 9. Replace Values: <Tracking area code> The format of the TAC is defined by 3GPP TS 23. 5. Replace Values: <GERAN Cell Identity> The leaf usage is defined in subclause 5. Occurrence: One Format: chr Access Types: Get.56 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ 3GPP_Location/<X>/TAC This TAC leaf indicates a Tracking Area Code for one particular 3GPP location description.0 Release 9 27 ETSI TS 124 312 V9. Occurrence: ZeroOrOne Format: chr Access Types: Get.003 [3]. Occurrence: ZeroOrOne Format: bin Access Types: Get. Replace Values: <PLMN> The format of the PLMN is defined by 3GPP TS 23. 5.003 [3]. Replace Values: <Location area code> The format of the LAC is defined by 3GPP TS 23.003 [3].55 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ 3GPP_Location/<X>/PLMN The PLMN leaf indicates a PLMN code for one particular 3GPP location description.3GPP TS 24.0 (2010-01) 5.0. 5. Occurrence: ZeroOrOne Format: chr Access Types: Get. ETSI .

312 version 9. If ANDSF provides 3GPP2_Location in AccessNetworkArea interior node. Replace Values: N/A If the UE is currently aware that it is located in the coverage area described by this 3GPP2_Location node. Occurrence: ZeroOrOne Format: bin Access Types: Get. Occurrence: ZeroOrOne Format: node Access Types: Get. 5. Replace ETSI .58A <X>/DiscoveryInformation/<X>/ AccessNetworkArea/3GPP_Location/<X>/UTRAN_CI The UTRAN_CI leaf indicates a UTRAN Cell Identity for one particular 3GPP network related location description.3GPP TS 24. Occurrence: ZeroOrOne Format: bin Access Types: Get. or both.0. Replace Values: <UTRAN Cell Identity> The leaf usage is defined in subclause 5. the networks described in the correspondent AccessNetworkInformationRef are expected to be available.18B.0 Release 9 28 ETSI TS 124 312 V9.0 (2010-01) 5. shall be provided.58B <X>/DiscoveryInformation/<X>/ AccessNetworkArea/3GPP_Location/<X>/EUTRA_CI The EUTRA_CI leaf indicates an E-UTRA Cell Identity for one particular 3GPP network related location description. 5.0. Occurrence: ZeroOrOne Format: node Access Types: Get.60 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ 3GPP2_Location/1x This 1x node acts as a placeholder for one or more 3GPP2 1x RAT location descriptions. either the 1x or HRPD interior node. Replace Values: <E-UTRA Cell Identity> The leaf usage is defined in subclause 5.18A. 5.59 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ 3GPP2_Location This 3GPP2_Location node acts as a placeholder for 3GPP2 location description.

Occurrence: One Format: chr Access Types: Get. Replace Values: N/A 5.S0005 [13]. Occurrence: ZeroOrOne Format: chr Access Types: Get. 5.62 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ 3GPP2_Location/1x/<X>/SID This SID leaf indicates a System Identification code for one particular 3GPP2 1x RAT location description. Occurrence: ZeroOrOne Format: chr Access Types: Get.64 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ 3GPP2_Location/1x/<X>/Base_ID This Base_ID leaf indicates a Base Station Identification Code for one particular 3GPP2 1x RAT location description.0.0. Replace Values: <System Identification> The format of the SID is defined by 3GPP2 C.63 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ 3GPP2_Location/1x/<X>/NID This NID leaf indicates a Network Identification code for one particular 3GPP2 1x RAT location description. Replace Values: <Base Station Identification> The format of the Base_ID is defined by 3GPP2 C. Replace Values: <Network Identification> The format of the NID is defined by 3GPP2 C.3GPP TS 24. ETSI .0 Release 9 29 ETSI TS 124 312 V9.0 (2010-01) - Values: N/A 5.312 version 9.61 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ 3GPP2_Location/1x/<X> This interior node acts as a placeholder for one or more 3GPP2 1x RAT location descriptions.S0016 [14]. 5.S0016 [14]. Occurrence: OneOrMore Format: node Access Types: Get.

Replace Values: N/A 5. Replace Values: <Netmask> The format of Netmask is defined by 3GPP2 C.0.0 (2010-01) 5. Occurrence: OneOrMore Format: node Access Types: Get. Occurrence: One Format: bin Access Types: Get. The length of Sector ID contained in this node is 128 bits. Occurrence: One Format: bin Access Types: Get.S0024-0 [15].0. Occurrence: ZeroOrOne Format: node Access Types: Get. The mask contained in this leaf shall be applied to the Sector_ID bit string contained in the correspondent leaf of interior node <X>/DiscoveryInformation/<X>/AccessNetworkArea/3GPP2_Location/HRPD/<X>.S0024-0 [15].67 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ 3GPP2_Location/HRPD/<X>/Sector_ID This Sector_ID leaf indicates a Sector Identification code for one particular 3GPP2 HRPD RAT location description.0 Release 9 30 ETSI TS 124 312 V9.312 version 9. ETSI .66 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ 3GPP2_Location/HRPD/<X> This interior node acts as a placeholder for one or more 3GPP2 HRPD RAT location descriptions. The length of Netmask contained in this node is 8 bits. Replace Values: <Sector ID> The format of the Sector ID is defined by 3GPP2 C. 5.3GPP TS 24.65 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ 3GPP2_Location/HRPD This HRPD node acts as a placeholder for one or more 3GPP2 HRPD RAT location descriptions. Replace Values: N/A 5.67A <X>/DiscoveryInformation/<X>/AccessNetworkArea/ 3GPP2_Location/HRPD/<X>/Netmask This Netmask leaf indicates a Netmask code for one particular 3GPP2 HRPD RAT location description.

71 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ WiMAX_Location/<X>/BS-ID The BS-ID leaf indicates the BS identifier for a particular WiMAX location description.0 (2010-01) 5. 5. 5.16-2004/Cor1-2005 [10].2 – Stage 2 [6] and WiMAX Forum Network Architecture Release 1.70 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ WiMAX_Location/<X>/NAP-ID The NASP-ID leaf indicates the Network Access Provider for a particular WiMAX location description. Occurrence: One Format: chr Access Types: Get.0 Release 9 31 ETSI TS 124 312 V9.68 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ WiMAX_Location The WiMAX_Location node acts as a placeholder for WiMAX location descriptions.16e-2005 and IEEE Std 802. Occurrence: ZeroOrOne Format: node Access Types: Get.0 version 1.2. Occurrence: OneOrMore Format: node Access Types: Get.0.2.2 – Stage 3 [7]. Replace Values: <BS-ID> The format of the BS-ID is defined by the IEEE Std 802. Replace Values: N/A 5. Occurrence: One Format: chr Access Types: Get. Replace Values: N/A If the UE is currently aware that it is located in the coverage area described by this node.0. the networks described in the correspondent AccessNetworkInformationRef are expected to be available.3GPP TS 24. Replace Values: <NAP-ID> The format of the NAP-ID is defined by the WiMAX Forum Network Architecture version 1. ETSI .312 version 9.69 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ WiMAX_Location/<X> This interior node acts as a placeholder for one or more WiMAX location descriptions.

Replace Values: <SSID> The format of the SSID is defined by IEEE Std 802.74 <X>/DiscoveryInformation/<X>/AccessNetworkArea /WLAN_Location/<X>/SSID The SSID leaf indicates the SSID for a particular WLAN location description.11™-2007 [9]. 5.3GPP TS 24.0 (2010-01) 5.0 Release 9 32 ETSI TS 124 312 V9. Replace Values: <HESSID> The format of the HESSID is defined by IEEE 802.73A <X>/DiscoveryInformation/<X>/AccessNetworkArea /WLAN_Location/<X>/HESSID The HESSID leaf indicates the HESSID for a particular Home WLAN Specific Identifier location description. ETSI . 5.11u [17]. Occurrence: OneOrMore Format: node Access Types: Get. Occurrence: ZeroOrOne Format: node Access Types: Get. Replace Values: N/A 5. the networks described in the correspondent AccessNetworkInformationRef are expected to be available.0.73 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ WLAN_Location/<X> This interior node acts as a placeholder for one or more WLAN location descriptions. Occurrence: ZeroOrOne Format: chr Access Types: Get.312 version 9.0.72 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ WLAN_Location The WLAN_Location node acts as a placeholder for WLAN location descriptions. Replace Values: N/A If the UE is currently aware that it is located in the coverage area described by this node. Occurrence: ZeroOrOne Format: chr Access Types: Get.

Occurrence: OneOrMore Format: node Access Types: Get.312 version 9.76 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ Geo_Location This Geo_Location node acts as a placeholder for geographical location descriptions for location of one or more access networks. 5. Replace Values: N/A 5.75 <X>/DiscoveryInformation/<X>/AccessNetworkArea/ WLAN_Location/<X>/BSSID The BSSID leaf indicates the AP identifier for one particular WLAN location description.0. the networks described in the correspondent AccessNetworkInformationRef are expected to be available.11™-2007 [9].76A <X>/DiscoveryInformation/<X>/ AccessNetworkArea /Geo_Location/Circular The Circular node acts as a placeholder for circular areas location descriptions. Occurrence: ZeroOrOne Format: node Access Types: Get. Replace Values: <N/A > ETSI .3GPP TS 24. 5.76B <X>/DiscoveryInformation/<X>/ AccessNetworkArea /Geo_Location/Circular/<X> The interior node acts as a placeholder for one or more circular area location descriptions. Occurrence: ZeroOrOne Format: node Access Types: Get.0.0 (2010-01) 5. Occurrence: One Format: chr Access Types: Get. Replace Values: N/A If the UE is currently aware that it is located in the area described by this Geo_Location node. Replace Values: <BSSID> The format of the BSSID is defined by IEEE Std 802.0 Release 9 33 ETSI TS 124 312 V9.

0. 5.3GPP TS 24.032 [3A]. Occurrence: One Format: bin Access Types: Get.76C <X>/DiscoveryInformation/<X>/ AccessNetworkArea/Geo_Location/Circular/<X>/AnchorLati tude The AnchorLatitude node acts as a placeholder for the latitude value of the center of the circular area.0 Release 9 34 ETSI TS 124 312 V9. 5.0. Occurrence: One Format: int Access Types: Get. Replace Values: <Latitude> The Latitude is defined in subclause 6. 5.312 version 9.1 of 3GPP TS 23.76D <X>/DiscoveryInformation/<X>/ AccessNetworkArea/Geo_Location/Circular/<X>/AnchorLon gitude The AnchorLongitude node acts as a placeholder for the longitude value of the center of the circular area.6 of 3GPP TS 23.76E <X>/DiscoveryInformation/<X>/ AccessNetworkArea/Geo_Location/Circular/<X>/Radius The Radius node acts as a placeholder for the radius value of the circular area. Replace Values: < Radius> The Radius is given in meters and is defined in subclause 6. Replace Values: < Longitude> The Longitude is defined in subclause 6.1 of 3GPP TS 23. Occurrence: ZeroOrOne Format: chr Access Types: Get. Replace Values: <An access network information object> ETSI .032 [3A].0 (2010-01) 5. Occurrence: One Format: bin Access Types: Get.032 [3A].77 <X>/DiscoveryInformation/<X>/ AccessNetworkInformationRef The AccessNetworkInformationRef leaf represents a reference to an access network information object.

5. Occurrence: One Format: chr Access Types: Get Values: <PLMN> The format of the PLMN is defined by 3GPP TS 23. Occurrence: OneOrMore Format: node Access Types: Get Values: N/A 5.g. Occurrence: ZeroOrOne Format: node Access Types: Get Values: N/A The UE should insert the parameters of all the 3GPP networks it can discover when updating this node.0.For example WLAN related values for the AccessNetworkInformationRef are defined in the OMA Connectivity Management Objects defined e.78 - <X>/UE_Location The UE_Location node acts as a placeholder for describing the current location of the UE. ETSI . and WiMAX related values for the AccessNetworkInformationRef are defined in the WiMAX MO in clause 6.0.0 Release 9 35 ETSI TS 124 312 V9. 5.79 - <X>/UE_Location/3GPP_Location The 3GPP_Location node acts as a placeholder for 3GPP location descriptions.312 version 9.20081107-A [4A] and OMADDS-DM_ConnMO_WLAN-V1_0-20081024-A [4B]. in OMA-DDS-DM_ConnMO-V1_0.3GPP TS 24.003 [3].82 <X>/UE_Location/3GPP_Location/<X>/TAC This TAC leaf indicates a Tracking Area Code for one particular 3GPP network related location of the UE.81 - <X>/UE_Location/3GPP_Location/<X>/PLMN The PLMN leaf indicates a PLMN code for one particular 3GPP network related location of the UE. etc.80 - <X>/UE_Location/3GPP_Location/<X> This interior node acts as a placeholder for one or more 3GPP location descriptions.0 (2010-01) The value of AccessNetworkInformationRef is a reference to an object with access network type specific information. 5. Occurrence: ZeroOrOne Format: node Access Types: Get Values: N/A 5.

003 [3].312 version 9. 5.3GPP TS 24. Occurrence: ZeroOrOne Format: bin Access Types: Get Values: <E-UTRA Cell Identity> ETSI . Occurrence: ZeroOrOne Format: bin Access Types: Get Values: < GERAN Cell Identity > The leaf usage is defined in subclause 5.84 - <X>/UE_Location/3GPP_Location/<X>/GERAN_CI The GERAN_CI leaf indicates a GERAN Cell Identity for one particular 3GPP network related location description. 5.18.84A <X>/UE_Location/3GPP_Location/<X>/ UTRAN_CI The UTRAN_CI leaf indicates a UTRAN Cell Identity for one particular 3GPP network related location description.0.0.003 [3].84B <X>/UE_Location/3GPP_Location/<X>/ EUTRA_CI The EUTRA_CI leaf indicates an E-UTRA Cell Identity for one particular 3GPP network related location description. Occurrence: ZeroOrOne Format: bin Access Types: Get Values: <UTRAN Cell Identity> The leaf usage is defined in subclause 5. 5. 5.0 (2010-01) - Occurrence: ZeroOrOne Format: chr Access Types: Get Values: <Tracking area code> The format of the TAC is defined by 3GPP TS 23.83 - <X>/UE_Location/3GPP_Location/<X>/LAC This LAC leaf indicates a Location Area Code for one particular 3GPP network related location of the UE.0 Release 9 36 ETSI TS 124 312 V9.18A. Occurrence: ZeroOrOne Format: chr Access Types: Get Values: <Location area code> The format of the LAC is defined by 3GPP TS 23.

18B.0 Release 9 37 ETSI TS 124 312 V9. Occurrence: ZeroOrOne Format: node Access Types: Get Values: N/A The UE should insert the parameters of all the 3GPP2 networks it can discover when updating this node.89 <X>/UE_Location/3GPP2_Location/1x/<X>/NID This NID leaf indicates a Network Identification code for one particular 3GPP2 1x RAT location used to indicate UE position.87 - <X>/UE_Location/3GPP2_Location/1x/<X> This interior node acts as a placeholder for one or more 3GPP2 1x RAT location descriptions of UE position.312 version 9.86 <X>/UE_Location/3GPP2_Location/1x This 1x node acts as a placeholder for one or more 3GPP2 1x RAT network related location descriptions of UE's position. Occurrence: ZeroOrOne Format: node Access Types: Get Values: N/A 5. 5.3GPP TS 24. ETSI . Occurrence: One Format: chr Access Types: Get Values: <SID> The format of the SID is defined by 3GPP2 C.S0016 [14].0 (2010-01) The leaf usage is defined in subclause 5.0. 5.88 <X>/UE_Location/3GPP2_Location/1x/<X>/SID This SID leaf indicates a System Identification code for one particular 3GPP2 1x RAT location used to indicate UE position.85 - <X>/UE_Location/3GPP2_Location This 3GPP2_Location node acts as a placeholder for 3GPP2 network related location description of UE's position. 5. Occurrence: OneOrMore Format: node Access Types: Get Values: N/A 5.0.

0. Occurrence: ZeroOrOne Format: chr Access Types: Get Values: <Base_ID> The format of the Base_ID is defined by 3GPP2 C. Occurrence: ZeroOrOne Format: node Access Types: Get Values: N/A 5. 5. Occurrence: One Format: bin Access Types: Get Values: <Sector_ID> ETSI .S0005 [13]. Occurrence: OneOrMore Format: node Access Types: Get Values: N/A 5. 5.90 <X>/UE_Location/3GPP2_Location/1x/<X>/Base_ID This Base_ID leaf indicates a Base Station Identification code for one particular 3GPP2 1x RAT location used to indicate UE position.92 - <X>/UE_Location/3GPP2_Location/HRPD/<X> This interior node acts as a placeholder for one or more 3GPP2 HRPD RAT location descriptions of UE position.0.0 (2010-01) - Occurrence: ZeroOrOne Format: chr Access Types: Get Values: <NID> The format of the NID is defined by 3GPP2 C.0 Release 9 38 ETSI TS 124 312 V9.91 - <X>/UE_Location/3GPP2_Location/HRPD This HRPD node acts as a placeholder for one or more 3GPP2 HRPD RAT location descriptions of UE position.93 <X>/UE_Location/3GPP2_Location/HRPD/<X>/Sector_ID This Sector_ID leaf indicates a Sector Identification code for one particular 3GPP2 HRPD RAT location used to indicate UE position.312 version 9.3GPP TS 24.S0016 [14].

Occurrence: ZeroOrOne Format: node Access Types: Get Values: N/A The UE should insert the parameters of all the WiMAX networks it can discover when updating this node.S0024-0 [15].0.2 – Stage 3 [7].S0024-0 [15].3GPP TS 24.2 – Stage 2 [6] and WiMAX Forum Network Architecture Release 1. Occurrence: OneOrMore Format: node Access Types: Get Values: N/A 5.0 (2010-01) The format of the Sector_ID is defined by 3GPP2 C.95 - <X>/UE_Location/WiMAX_Location/<X> This interior node acts as a placeholder for one or more WiMAX location descriptions. ETSI . 5. Occurrence: One Format: chr Access Types: Get Values: <NAP-ID> The format of the NAP-ID is defined by the WiMAX Forum Network Architecture version 1.0 version 1. The mask contained in this leaf shall be applied to the Sector_ID bit string contained in the correspondent leaf of interior node.312 version 9.96 - <X>/UE_Location/WiMAX_Location/<X>/NAP-ID The NAP-ID leaf indicates the Network Access Provider for a particular WiMAX network related location of the UE. Occurrence: One Format: bin Access Types: Get Values: <Netmask> The format of Netmask is defined by 3GPP2 C. The length of Netmask contained in this node is 8 bits.93A <X>/UE_Location/3GPP2_Location/HRPD/<X>/Netmask The Netmask leaf indicates a Netmask code for one particular 3GPP2 HRPD RAT location used to indicate UE position. 5.0 Release 9 39 ETSI TS 124 312 V9. 5.2.2.0. The length of Sector ID contained in this node is 128 bits.94 - <X>/UE_Location/WiMAX_Location The WiMAX_Location node acts as a placeholder for WiMAX location descriptions.

5.99 - <X>/UE_Location/WLAN_Location/<X> This interior node acts as a placeholder for one or more WLAN location descriptions. Occurrence: ZeroOrOne Format: chr Access Types: Get.11u [17].99A <X>/UE_Location/WLAN_Location/<X>/HESSID The HESSID leaf indicates the HESSID for a particular WiFi network related location of the UE.0 Release 9 40 ETSI TS 124 312 V9. Replace Values: <HESSID> The format of the HESSID is defined by IEEE 802.0. Occurrence: OneOrMore Format: node Access Types: Get Values: N/A 5. Occurrence: One Format: chr Access Types: Get Values: <BS-ID> The format of the BS-ID is defined by the IEEE Std 802.16-2004/Cor1-2005 [10].98 - <X>/UE_Location/WLAN_Location The WLAN_Location node acts as a placeholder for WLAN location descriptions. 5.3GPP TS 24. 5. Occurrence: ZeroOrOne Format: chr ETSI .312 version 9.16e-2005 and IEEE Std 802. Occurrence: ZeroOrOne Format: node Access Types: Get Values: N/A The UE should insert the parameters of all the WLAN networks it can discover when updating this node.0.97 - <X>/UE_Location/WiMAX_Location/<X>/BS-ID The BS-ID leaf indicates the BS identifier for a particular WiMAX network related location of the UE.0 (2010-01) 5.100 - <X>/UE_Location/WLAN_Location/<X>/SSID The SSID leaf indicates the SSID for a particular WLAN network related location of the UE.

102 - <X>/UE_Location/Geo_Location/ This node acts as a placeholder for one or more UE Geo_Location location descriptions.1 of 3GPP TS 23.312 version 9.11™-2007 [9].0 Release 9 41 ETSI TS 124 312 V9.102C <X>/ UE_Location /Geo_Location/Longitude The Longitude node acts as a placeholder for the longitude value of the position of the UE.101 - <X>/UE_Location/WLAN_Location/<X>/BSSID The BSSID leaf indicates the AP identifier for one particular WLAN network related location of the UE. 5.102A Void 5.032 [3A]. 5. it shall insert the coordinates of its position in this Geo_Location node. Occurrence: ZeroOrOne Format: node Access Types: Get Values: <N/A > If the UE is aware of its geographical position.0 (2010-01) - Access Types: Get Values: <SSID> The format of the SSID is defined by IEEE Std 802. Occurrence: One Format: bin Access Types: Get Values: <Latitude > The Latitude is defined in subclause 6.3GPP TS 24. Occurrence: One Format: bin Access Types: Get Values: < Longitude> ETSI .11™-2007 [9]. Occurrence: One Format: chr Access Types: Get Values: <BSSID> The format of the BSSID is defined by IEEE Std 802. 5.102B <X>/ UE_Location /Geo_Location/Latitude The Latitude node acts as a placeholder for the latitude value of the position of the UE.0.0. 5.

The ANDSF may initiate the provisioning of WiMAX specific information using a server initiated session alert message. Usually the vendor extension is identified by vendor specific name under the ext node. 5.0.1 MO for WiMAX Introduction This section defines the WiMAX Network Discovery and Selection (WNDS) MO and the corresponding behaviour of the UE with regard to discovering and selecting WiMAX access networks in the home operator network.0.402 [4].003 [3].3GPP TS 24. ETSI .). The service requirements for the WiMAX network discovery and selection function are described in 3GPP TS 23.0 Release 9 42 ETSI TS 124 312 V9. Occurrence: ZeroOrOne Format: chr Access Types: Get Values: <PLMN> The format of the PLMN is defined by 3GPP TS 23. Occurrence: ZeroOrOne Format: node Access Types: Get Values: N/A 6 6. device vendor etc.2 and upwards.1 of 3GPP TS 23.2 WNDS MO The WNDS MO is used to manage WiMAX network discovery and selection information stored in the UE and supports provisioning of such information from the ANDSF. 6. version 1. The WNDS MO is compatible with the OMA Device Management (DM) protocol specifications. The Management Object Identifier is: urn:oma:mo:ext-3gpp-wnds:1. and is defined using the OMA DM Device Description Framework (DDF) as described in the Enabler Release Definition OMA-ERELD-DM-V1_2 [5]. The tree structure under the vendor identifier is not defined and can therefore include one or more un-standardized sub-trees. The UE may initiate the provision of information from the ANDSF using a client initiated session alert message.102D <X>/ UE_Location /RPLMN The RPLMN leaf indicates a PLMN code of the registered PLMN the UE is connected to. The OMA DM Access Control List (ACL) property mechanism as standardized (see Enabler Release Definition OMAERELD-DM-V1_2 [5]) may be used to grant or deny access rights to OMA DM servers in order to modify nodes and leaf objects of the WNDS MO.103 <X>/Ext The Ext is an interior node for where the vendor specific information about the ANDSF MO is being placed (vendor meaning application vendor.0.032 [3A]. 5.0 (2010-01) The Longitude is defined in subclause 6.312 version 9.

2.1: WNDS MO 6.3GPP TS 24.3.2 - Node: <X> This interior node acts as a placeholder for zero or one accounts for a fixed node.3 6.3.312 version 9.0. 6. ETSI .4 <X>/NetworkList This interior node acts as a placeholder for available WiMAX Network.3.0.1: Figure 6.2.3 - <X>/Name The Name leaf is a name for the WNDS MO settings.1 WNDS MO parameters General This clause describes the parameters for the WNDS MO.3.0 (2010-01) The following nodes and leaf objects are possible under the WiMAX Network Discovery and Selection node as described in figure 6. Occurrence: ZeroOrOne Format: node Access Types: Get Values: N/A 6. Occurrence: ZeroOrOne Format: chr Access Types: Get Values: <User displayable name> 6.0 Release 9 43 ETSI TS 124 312 V9.

9 <X>/NetworkList/<X>/FrequencyInfo/<X>LastFreq The LastFreq leaf specifies the last center frequency in KHz for this channel. If this value equals to the FirstFreq or the leaf node is omitted.3.6 - <X>/NetworkList/<X>/FrequencyInfo The FrequencyInfo node contains WiMAX operating frequency related information.0. Replace Values: <N/A> 6.8 - <X>/NetworkList/<X>/FrequencyInfo/<X>FirstFreq The FirstFreq leaf specifies the first center frequency in KHz for this channel.0 (2010-01) - Occurrence: ZeroOrOne Format: node Access Types: Get. Replace Values: <FirstFreq> 6. Replace Values: <N/A> 6.312 version 9. Replace Values: <N/A> 6.5 - <X>/NetworkList/<X> This interior node acts as a placeholder for properties of one or more WiMAX Network.7 - <X>/NetworkList/<X>/FrequencyInfo/<X> This interior node acts as a placeholder for one or more FrequencyInfo node properties.0. Occurrence: OneOrMore Format: node Access Types: Get. If this field is present then NextFreqStep shall be present as well. Occurrence: One Format: int Access Types: Get. Replace Values: < N/A> 6..3. then this entry refers to a single channel rather than a channel range. Occurrence: OneOrMore Format: node Access Types: Get.3GPP TS 24. Occurrence: One ETSI . Occurrence: One Format: node Access Types: Get.3.3.0 Release 9 44 ETSI TS 124 312 V9.3.

3.15. Table 6.15. The formula to calculate the next central frequency is: CurrentFreq = FirstFreq While (CurrentFreq <= LastFreq) CurrentFreq = CurrentFreq + NextFreqStep 6.0. If this field is present LastFreq shall be present as well. Replace Values: <ChannelBandwidth> 6. Occurrence: One Format: int Access Types: Get.3.3GPP TS 24.0 (2010-01) - Format: int Access Types: Get. Replace Values: <LastFreq> 6. Replace Values: <Duplex mode> The value of the DuplexMode shall be used as specified in Table 6.3.11 - <X>/NetworkList/<X>/ FrequencyInfo/<X>ChannelBandwidth The ChannelBandwidth leaf is the system bandwith in KHz that is supported by the WiMAX network. The DuplexMode can be TDD.3.312 version 9.3. Replace Values: <NextFreqStep> When this leaf node is omitted there is only one central frequency (i.1.0 Release 9 45 ETSI TS 124 312 V9. Occurrence: One Format: int Access Types: Get.e FirstFreq).1: Values of DuplexMode Value 0 1 2 3 4-255 Reserved TDD FDD HFDD Reserved Description ETSI .10 <X>/NetworkList/<X>/FrequencyInfo/<X>NextFreqStep The NextFreqStep leaf defines the frequency step in KHz to reach the next central frequency when defining the frequency range using FirstFreq and LastFreq.12 <X>/NetworkList/<X>/ FrequencyInfo/<X>DuplexMode The DuplexMode leaf is the duplex mode supported by the network. FDD or hybrid FDD (HFDD) Occurrence: One Format: int Access Types: Get.0.

Replace Values: <Cell type> 6. micro or macro.3. Occurrence: One Format: chr Access Types: Get. Replace Values: <NAP-ID> 6.0.0 version 1. 6. Occurrence: One Format: int Access Types: Get.13 - <X>/NetworkList/<X>/ FrequencyInfo/<X>FFT_Size The FFT_Size leaf specifies the channel"s FFT. Occurrence: ZeroOrOne Format: chr Access Types: Get.15 <X>/ NetworkList /<X>/NAP-ID The NAP-ID leaf is the identifier of the WiMAX radio access infrastructure provider.3. The two MSB are zeroed and the LSB indicates channel 0. Replace Values: <Text field> ETSI .0. pico.312 version 9.16 - <X>/NetworkList/<X>/CellType The CellType leaf represents the type of cell.2.3GPP TS 24.2 – Stage 3 [7].14 - <X>/NetworkList/<X>/ FrequencyInfo/<X>Preambles The Preambles leaf specifies the valid preambles for each channel in the channel range.2. Replace Values: <Preambles> The value is a hexadecimal string which is 29 digits long. The cell type can be femto.3.0 (2010-01) 6. Occurrence: One Format: int Access Types: Get. For further details on Network Access Provider please refer to the WiMAX Forum Network Architecture version 1.17 <X>/NetworkList/<X>/OperatorDifferentiatedTextField The OperatorDifferentiatedTextField leaf represents textual information that the operator wants to associate with the access technology. Replace Values: <FFT size> 6.2 – Stage 2 [6] and WiMAX Forum Network Architecture Release 1.3. Occurrence: One Format: chr Access Types: Get.3.0 Release 9 46 ETSI TS 124 312 V9.

0.0 Release 9 47 ETSI TS 124 312 V9. Usually the vendor extension is identified by vendor specific name under the ext node. 6.312 version 9.0 (2010-01) The text field contains alphanumeric characters. Occurrence: ZeroOrOne Format: node Access Types: Get Values: N/A ETSI . The tree structure under the vendor identifier is not defined and can therefore include one or more unstandardized sub-trees.3.0. device vendor etc.).3GPP TS 24.18 <X>/Ext The Ext is an interior node for where the vendor specific information about the WNDS MO is placed (vendor can be application vendor.

org/tech/DTD/dm_ddf-v1_2.</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>Policy</NodeName> <!-.0.0 (2010-01) Annex A (informative): ANDSF MO DDF This DDF is the standardized minimal set.</DFTitle> <DFType> <DDFName/> </DFType> </DFProperties> ETSI .0 Release 9 48 ETSI TS 124 312 V9. <?xml version="1.The Policy node starts here.2</VerDTD> <Man>--The device manufacturer--</Man> <Mod>--The device model--</Mod> <Node> <NodeName>ANDSF</NodeName> <DFProperties> <AccessType> <Get/> </AccessType> <Description>ANDSF settings</Description> <DFFormat> <node/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>The ANDSF Management Object.2//EN" "http://www. A vendor can define its own DDF for the complete device.3GPP TS 24.</DFTitle> <DFType> <DDFName/> </DFType> </DFProperties> <Node> <NodeName>Name</NodeName> <DFProperties> <AccessType> <Get/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>User displayable name for the node.dtd"> <MgmtTree> <VerDTD>1. This DDF can include more features than this minimal standardized version. --> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>Policies for access network selection.0.0" encoding="UTF-8"?> <!DOCTYPE MgmtTree PUBLIC "-//OMA//DTD-DM-DDF 1.312 version 9.openmobilealliance.

</DFTitle> <DFType> <DDFName/> </DFType> </DFProperties> <Node> <NodeName></NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <OneOrMore/> </Occurrence> <DFType> <DDFName></DDFName> </DFType> </DFProperties> <Node> <NodeName>AccessTechnology</NodeName> <DFProperties> ETSI .0.0 (2010-01) <Node> <NodeName>RulePriority</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <int/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>Rule priority.3GPP TS 24.312 version 9.</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>PrioritizedAccess</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>Prioritized access.0.0 Release 9 <Node> <NodeName></NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <OneOrMore/> </Occurrence> <DFType> <DDFName></DDFName> </DFType> </DFProperties> 49 ETSI TS 124 312 V9.

3GPP TS 24.0 (2010-01) <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <int/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>Access technology.0.</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>AccessId</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>Access identity.</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> </Node> </Node> ETSI .0.</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>AccessNetworkPriority</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <int/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>Access network priority.0 Release 9 50 ETSI TS 124 312 V9.</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>SecondaryAccessId</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>Access identity.312 version 9.

0 (2010-01) <Node> <NodeName>ValidityArea</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>Validity area.0.</DFTitle> <DFType> <DDFName/> </DFType> </DFProperties> <Node> <NodeName>3GPP_Location</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>Validity area for 3GPP access.0 Release 9 51 ETSI TS 124 312 V9.0.</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> ETSI .3GPP TS 24.312 version 9.</DFTitle> <DFType> <DDFName/> </DFType> </DFProperties> <Node> <NodeName></NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <OneOrMore/> </Occurrence> <DFType> <DDFName></DDFName> </DFType> </DFProperties> <Node> <NodeName>PLMN</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>PLMN.

</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>UTRAN_CI</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <bin/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>UTRAN_CI.312 version 9.</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> ETSI .0.0 Release 9 52 ETSI TS 124 312 V9.3GPP TS 24.0 (2010-01) <NodeName>TAC</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>TAC.</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>LAC</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>LAC.</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>GERAN_CI</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <bin/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>GERAN_CI.0.

0.</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> </Node> </Node> <Node> <NodeName>3GPP2_Location</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle> Validity area for 3GPP2 access.</DFTitle> <DFType> <DDFName/> </DFType> </DFProperties> <Node> <NodeName></NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <OneOrMore/> </Occurrence> <DFType> <DDFName></DDFName> </DFType> </DFProperties> ETSI .0 Release 9 53 ETSI TS 124 312 V9.312 version 9.0 (2010-01) <Node> <NodeName>EUTRA_CI</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <bin/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>EUTRA_CI.3GPP TS 24.</DFTitle> <DFType> <DDFName/> </DFType> </DFProperties> <Node> <NodeName>1x</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle> Validity area for 3GPP2-1x access.0.

3GPP TS 24.0 (2010-01) <Node> <NodeName>SID</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>1x-SID.312 version 9.0 Release 9 54 ETSI TS 124 312 V9.</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>Base_ID</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>1x-Base ID.0.0.</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> </Node> </Node> <Node> <NodeName>HRPD</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle> Validity area for 3GPP2-HRPD access</DFTitle> <DFType> ETSI .</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>NID</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>1x-NID.

0 (2010-01) <Node> <NodeName></NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <OneOrMore/> </Occurrence> <DFType> <DDFName></DDFName> </DFType> </DFProperties> <Node> <NodeName>Sector_ID</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <bin/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>HRPD Sector ID</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>Netmask</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <bin/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>HRPD netmask</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> </Node> </Node> </Node> <Node> <NodeName>WiMAX_Location</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> ETSI .0 Release 9 <DDFName/> </DFType> </DFProperties> 55 ETSI TS 124 312 V9.312 version 9.3GPP TS 24.0.0.

312 version 9.0 (2010-01) <DFTitle> Validity area for WiMAX access.0.3GPP TS 24.</DFTitle> <DFType> <DDFName/> </DFType> </DFProperties> <Node> <NodeName></NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <OneOrMore/> </Occurrence> <DFType> <DDFName></DDFName> </DFType> </DFProperties> <Node> <NodeName>NAP-ID</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>NAP-ID</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>BS-ID</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>BS-ID</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> </Node> </Node> <Node> <NodeName>WLAN_Location</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <ZeroOrOne/> ETSI .0.0 Release 9 56 ETSI TS 124 312 V9.

312 version 9.</DFTitle> <DFType> <DDFName/> </DFType> </DFProperties> <Node> <NodeName></NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <OneOrMore/> </Occurrence> <DFType> <DDFName></DDFName> </DFType> </DFProperties> <Node> <NodeName>HESSID</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>HESSID</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>SSID</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>SSID</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>BSSID</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>BSSID</DFTitle> <DFType> ETSI .0.0 (2010-01) </Occurrence> <DFTitle> Validity area for WLAN access.0 Release 9 57 ETSI TS 124 312 V9.3GPP TS 24.0.

</DFTitle> <DFType> <DDFName/> </DFType> </DFProperties> <Node> <NodeName></NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <OneOrMore/> </Occurrence> <DFType> <DDFName></DDFName> </DFType> </DFProperties> <Node> <NodeName>AnchorLatitude</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>Anchor latitude</DFTitle> <DFType> ETSI .0 Release 9 58 ETSI TS 124 312 V9.312 version 9.0 (2010-01) <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> </Node> </Node> <Node> <NodeName>Geo_Location</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>Geographical location.0.3GPP TS 24.0.</DFTitle> <DFType> <DDFName/> </DFType> </DFProperties> <Node> <NodeName>Circular</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>Circular location descripton.

0.0 (2010-01) <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>AnchorLongitude</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>Anchor longitude</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>Radius</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>Radius</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> </Node> </Node> </Node> </Node> <Node> <NodeName>Roaming</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <bool/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>Rule priority.</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>PLMN</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <chr/> ETSI .0.3GPP TS 24.312 version 9.0 Release 9 59 ETSI TS 124 312 V9.

0.</DFTitle> <DFType> <DDFName/> </DFType> </DFProperties> <Node> <NodeName></NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <OneOrMore/> </Occurrence> <DFType> <DDFName></DDFName> </DFType> </DFProperties> <Node> <NodeName>TimeStart</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <int/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>Start condition for time of rule.3GPP TS 24.0 (2010-01) </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>PLMN which created the policy.</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>TimeStop</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <int/> ETSI .</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>TimeOfDay</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>Time of day.312 version 9.0 Release 9 60 ETSI TS 124 312 V9.0.

--> ETSI .</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>DateStart</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <int/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>Starting date for time condition of rule.0 (2010-01) </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>Stop condition for time of rule.</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> </Node> </Node> <Node> <NodeName>DiscoveryInformation</NodeName> <!-.The DiscoveryInformation node starts here.312 version 9.</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>DateStop</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <int/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>Stop date for time condition of rule.0.0.3GPP TS 24.</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> </Node> </Node> <Node> <NodeName>UpdatePolicy</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <bool/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>Update policy.0 Release 9 61 ETSI TS 124 312 V9.

0 (2010-01) <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>Access network discovery information.3GPP TS 24.</DFTitle> <DFType> <DDFName/> </DFType> </DFProperties> <Node> <NodeName></NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <OneOrMore/> </Occurrence> <DFType> <DDFName></DDFName> </DFType> </DFProperties> <Node> <NodeName>AccessNetworkType</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <int/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>Access network type.</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>AccessNetworkArea</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>Access network area.0 Release 9 62 ETSI TS 124 312 V9.312 version 9.0.</DFTitle> <DFType> <DDFName/> </DFType> </DFProperties> <Node> <NodeName>3GPP_Location</NodeName> <DFProperties> <AccessType> ETSI .0.

312 version 9.0.</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>LAC</NodeName> <DFProperties> <AccessType> <Get/> ETSI .0 Release 9 63 ETSI TS 124 312 V9.0 (2010-01) <Get/> <Replace/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>Discovery information for 3GPP access.3GPP TS 24.</DFTitle> <DFType> <DDFName/> </DFType> </DFProperties> <Node> <NodeName></NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <OneOrMore/> </Occurrence> <DFType> <DDFName></DDFName> </DFType> </DFProperties> <Node> <NodeName>PLMN</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>PLMN.</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>TAC</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>TAC.0.

</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>GERAN_CI</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <bin/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>GERAN_CI.</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>EUTRA_CI</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <bin/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>EUTRA_CI.</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> </Node> </Node> <Node> ETSI .3GPP TS 24.0 Release 9 64 ETSI TS 124 312 V9.0.</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>UTRAN_CI</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <bin/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>UTRAN_CI.0.312 version 9.0 (2010-01) <Replace/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>LAC.

312 version 9.0 (2010-01) <NodeName>3GPP2_Location</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>Discovery information for 3GPP2 access.0.3GPP TS 24.</DFTitle> <DFType> <DDFName/> </DFType> </DFProperties> <Node> <NodeName>1x</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>Discovery information for 3GPP2-1x access.</DFTitle> <DFType> <DDFName/> </DFType> </DFProperties> <Node> <NodeName></NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <OneOrMore/> </Occurrence> <DFType> <DDFName></DDFName> </DFType> </DFProperties> <Node> <NodeName>SID</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>1x-SID.0.</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>NID</NodeName> <DFProperties> ETSI .0 Release 9 65 ETSI TS 124 312 V9.

0 (2010-01) <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>1x-NID.3GPP TS 24.0.0 Release 9 66 ETSI TS 124 312 V9.0.312 version 9.</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>Base_ID</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>1x-Base ID.</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> </Node> </Node> <Node> <NodeName>HRPD</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>Discovery information for 3GPP2-HRPD access</DFTitle> <DFType> <DDFName/> </DFType> </DFProperties> <Node> <NodeName></NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <OneOrMore/> </Occurrence> <DFType> <DDFName></DDFName> </DFType> </DFProperties> <Node> <NodeName>Sector_ID</NodeName> ETSI .

0 (2010-01) <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <bin/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>HRPD Sector ID</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>Netmask</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <bin/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>HRPD netmask</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> </Node> </Node> </Node> <Node> <NodeName>WiMAX_Location</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>Discovery information for WiMAX access.0.0 Release 9 67 ETSI TS 124 312 V9.0.3GPP TS 24.312 version 9.</DFTitle> <DFType> <DDFName/> </DFType> </DFProperties> <Node> <NodeName></NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <OneOrMore/> </Occurrence> <DFType> <DDFName></DDFName> </DFType> </DFProperties> ETSI .

0 (2010-01) <Node> <NodeName>NAP-ID</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>NAP-ID</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>BS-ID</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>BS-ID</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> </Node> </Node> <Node> <NodeName>WLAN_Location</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>Discovery information for WLAN access.3GPP TS 24.312 version 9.0.0 Release 9 68 ETSI TS 124 312 V9.0.</DFTitle> <DFType> <DDFName/> </DFType> </DFProperties> <Node> <NodeName></NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <OneOrMore/> </Occurrence> <DFType> <DDFName></DDFName> </DFType> </DFProperties> ETSI .

0.0 (2010-01) <Node> <NodeName>HESSID</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat <chr/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>HESSID</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>SSID</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>SSID</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>BSSID</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>BSSID</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> </Node> </Node> <Node> <NodeName>Geo_Location</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>Geographical location.0 Release 9 69 ETSI TS 124 312 V9.0.3GPP TS 24.312 version 9.</DFTitle> <DFType> ETSI .

0.3GPP TS 24.0 Release 9 <DDFName/> </DFType> </DFProperties> 70 ETSI TS 124 312 V9.0 (2010-01) <Node> <NodeName>Circular</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>Circular location descripton.312 version 9.0.</DFTitle> <DFType> <DDFName/> </DFType> </DFProperties> <Node> <NodeName></NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <OneOrMore/> </Occurrence> <DFType> <DDFName></DDFName> </DFType> </DFProperties> <Node> <NodeName>AnchorLatitude</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>Anchor latitude</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>AnchorLongitude</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>Anchor longitude</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> ETSI .

3GPP TS 24.0 (2010-01) </DFProperties> </Node> <Node> <NodeName>Radius</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>Radius</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> </Node> </Node> </Node> </Node> <Node> <NodeName>AccessNetworkInformationRef</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>Access network information reference.0.0.312 version 9.The UE_Location node starts here.</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> </Node> </Node> <Node> <NodeName>UE_Location</NodeName> <!-.0 Release 9 71 ETSI TS 124 312 V9. --> <DFProperties> <AccessType> <Get/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>Current location of the UE</DFTitle> <DFType> <DDFName/> </DFType> </DFProperties> <Node> <NodeName>3GPP_Location</NodeName> <DFProperties> <AccessType> <Get/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> ETSI .

312 version 9.3GPP TS 24.0 Release 9 72 ETSI TS 124 312 V9.0.0.0 (2010-01) <ZeroOrOne/> </Occurrence> <DFTitle>Current 3GPP location of the UE</DFTitle> <DFType> <DDFName/> </DFType> </DFProperties> <Node> <NodeName></NodeName> <DFProperties> <AccessType> <Get/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <OneOrMore/> </Occurrence> <DFType> <DDFName></DDFName> </DFType> </DFProperties> <Node> <NodeName>PLMN</NodeName> <DFProperties> <AccessType> <Get/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>Current PLMN</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>TAC</NodeName> <DFProperties> <AccessType> <Get/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>Current TAC</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>LAC</NodeName> <DFProperties> <AccessType> <Get/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>Current LAC</DFTitle> <DFType> <MIME>text/plain</MIME> ETSI .

0.3GPP TS 24.0 (2010-01) <Node> <NodeName>GERAN_CI</NodeName> <DFProperties> <AccessType> <Get/> </AccessType> <DFFormat> <bin/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>Current GERAN_CI</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>UTRAN_CI</NodeName> <DFProperties> <AccessType> <Get/> </AccessType> <DFFormat> <bin/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>Current UTRAN_CI</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>EUTRA_CI</NodeName> <DFProperties> <AccessType> <Get/> </AccessType> <DFFormat> <bin/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>Current EUTRA_CI</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> </Node> </Node> <Node> <NodeName>3GPP2_Location</NodeName> <DFProperties> <AccessType> <Get/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>Current 3GPP2 location of the UE</DFTitle> <DFType> <DDFName/> ETSI .0 Release 9 </DFType> </DFProperties> </Node> 73 ETSI TS 124 312 V9.312 version 9.0.

0.312 version 9.0 (2010-01) <Node> <NodeName>1x</NodeName> <DFProperties> <AccessType> <Get/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>Current 3GPP2-1x location of the UE</DFTitle> <DFType> <DDFName/> </DFType> </DFProperties> <Node> <NodeName></NodeName> <DFProperties> <AccessType> <Get/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <OneOrMore/> </Occurrence> <DFType> <DDFName></DDFName> </DFType> </DFProperties> <Node> <NodeName>SID</NodeName> <DFProperties> <AccessType> <Get/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>Current SID</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>NID</NodeName> <DFProperties> <AccessType> <Get/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>Current NID</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>Base_ID</NodeName> ETSI .0.3GPP TS 24.0 Release 9 </DFType> </DFProperties> 74 ETSI TS 124 312 V9.

312 version 9.0.0 Release 9 75 ETSI TS 124 312 V9.0 (2010-01) <DFProperties> <AccessType> <Get/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>Current Base ID</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> </Node> </Node> <Node> <NodeName>HRPD</NodeName> <DFProperties> <AccessType> <Get/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>Current 3GPP2-HRPD location of the UE</DFTitle> <DFType> <DDFName/> </DFType> </DFProperties> <Node> <NodeName></NodeName> <DFProperties> <AccessType> <Get/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <OneOrMore/> </Occurrence> <DFType> <DDFName></DDFName> </DFType> </DFProperties> <Node> <NodeName>Sector_ID</NodeName> <DFProperties> <AccessType> <Get/> </AccessType> <DFFormat> <bin/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>Current Sector ID</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>Netmask</NodeName> <DFProperties> <AccessType> <Get/> ETSI .0.3GPP TS 24.

0.0 (2010-01) </AccessType> <DFFormat> <bin/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>HRPD netmask</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> </Node> </Node> </Node> <Node> <NodeName>WiMAX_Location</NodeName> <DFProperties> <AccessType> <Get/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>Current WiMAX location of the UE</DFTitle> <DFType> <DDFName/> </DFType> </DFProperties> <Node> <NodeName></NodeName> <DFProperties> <AccessType> <Get/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <OneOrMore/> </Occurrence> <DFType> <DDFName></DDFName> </DFType> </DFProperties> <Node> <NodeName>NAP-ID</NodeName> <DFProperties> <AccessType> <Get/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>Current NAP-ID</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>BS-ID</NodeName> <DFProperties> <AccessType> <Get/> </AccessType> <DFFormat> ETSI .0.0 Release 9 76 ETSI TS 124 312 V9.312 version 9.3GPP TS 24.

0 (2010-01) <chr/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>Current BS-ID</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> </Node> </Node> <Node> <NodeName>WLAN_Location</NodeName> <DFProperties> <AccessType> <Get/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>Current WLAN location of the UE</DFTitle> <DFType> <DDFName/> </DFType> </DFProperties> <Node> <NodeName></NodeName> <DFProperties> <AccessType> <Get/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <OneOrMore/> </Occurrence> <DFType> <DDFName></DDFName> </DFType> </DFProperties> <Node> <NodeName>HESSID</NodeName> <DFProperties> <AccessType> <Get/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>Current HESSID</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>SSID</NodeName> <DFProperties> <AccessType> <Get/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> ETSI .0.0.312 version 9.0 Release 9 77 ETSI TS 124 312 V9.3GPP TS 24.

0.3GPP TS 24.0.0 (2010-01) <ZeroOrOne/> </Occurrence> <DFTitle>Current SSID</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>BSSID</NodeName> <DFProperties> <AccessType> <Get/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>Current BSSID</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> </Node> </Node> <Node> <NodeName>Geo_Location</NodeName> <DFProperties> <AccessType> <Get/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>Current Geographical location of the UE</DFTitle> <DFType> <DDFName/> </DFType> </DFProperties> <Node> <NodeName>AnchorLatitude</NodeName> <DFProperties> <AccessType> <Get/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>Anchor latitude</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>AnchorLongitude</NodeName> <DFProperties> <AccessType> <Get/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <One/> ETSI .0 Release 9 78 ETSI TS 124 312 V9.312 version 9.

312 version 9.3GPP TS 24.0 Release 9 79 ETSI TS 124 312 V9.</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> </Node> <Node> <NodeName>Ext</NodeName> <!-.0.The Extension node starts here.0 (2010-01) </Occurrence> <DFTitle>Anchor longitude</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> </Node> <Node> <NodeName>RPLMN</NodeName> <DFProperties> <AccessType> <Get/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>RPLMN. --> <DFProperties> <AccessType> <Get/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>A collection of all Extension objects</DFTitle> <DFType> <DDFName/> </DFType> </DFProperties> </Node> </Node> </MgmtTree> ETSI .0.

dtd"> <MgmtTree> <VerDTD>1. This DDF can include more features than this minimal standardized version.2</VerDTD> <Man>--The device manufacturer--</Man> <Mod>--The device model--</Mod> <Node> <NodeName>WiMAX_NDS</NodeName> <DFProperties> <AccessType> <Get/> </AccessType> <Description>WiMAX NDS settings</Description> <DFFormat> <node/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>The WiMAX NDS Management Object.The NetworkList node starts here.0 Release 9 80 ETSI TS 124 312 V9. --> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>Properties for each of the network in NetworkList.312 version 9.0.0 (2010-01) Annex B (informative): WNDS MO DDF This DDF is the standardized minimal set.0.</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>NetworkList</NodeName> <!-.0" encoding="UTF-8"?> <!DOCTYPE MgmtTree PUBLIC "-//OMA//DTD-DM-DDF 1.org/tech/DTD/dm_ddf-v1_2.3GPP TS 24. <?xml version="1.</DFTitle> <DFType> <DDFName/> </DFType> </DFProperties> ETSI . A vendor can define its own DDF for the complete device.</DFTitle> <DFType> <DDFName/> </DFType> </DFProperties> <Node> <NodeName>Name</NodeName> <DFProperties> <AccessType> <Get/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>User displayable name for the node.openmobilealliance.2//EN" "http://www.

3GPP TS 24.312 version 9.0.0 Release 9

81

ETSI TS 124 312 V9.0.0 (2010-01)

<Node> <NodeName/> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <OneOrMore/> </Occurrence> <DFTitle>The "name" node for properties of NetworkList.</DFTitle> <DFType> <DDFName/> </DFType> </DFProperties>

<Node> <NodeName>FrequencyInfo</NodeName> <!-- The FrequencyInfo node starts here. --> <DFProperties> <AccessType> <Get/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>Frequency Information for the network.</DFTitle> <DFType> <DDFName/> </DFType> </DFProperties> <Node> <NodeName/> <DFProperties> <AccessType> <Get/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <OneOrMore/> </Occurrence> <DFTitle>The "name" node for frequency Information of network.</DFTitle> <DFType> <DDFName/> </DFType> </DFProperties> <Node> <NodeName>FirstFreq</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <int/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>The First Center Frequency.</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node>

ETSI

3GPP TS 24.312 version 9.0.0 Release 9

82

ETSI TS 124 312 V9.0.0 (2010-01)

<NodeName>LastFreq</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <int/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>The Last Center Frequency.</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>NextFreqStep</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <int/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>The frequency step for next central frequency.</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>ChannelBandwidth</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <int/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>The channel bandwidth in KHz.</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>DuplexMode</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <int/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>The duplex mode for this channel.</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node>

ETSI

3GPP TS 24.312 version 9.0.0 Release 9

83

ETSI TS 124 312 V9.0.0 (2010-01)

<Node> <NodeName>FFTSize</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <int/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>The FFT size for this channel.</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>Preambles</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>The Preambles for this channel.</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> </Node> </Node>

<Node> <NodeName>CellType</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <int/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>The Cell Type.</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>NAP-ID</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <int/> </DFFormat> <Occurrence> <One/> </Occurrence> <DFTitle>The Network Access Provider Identifier.</DFTitle>

ETSI

3GPP TS 24.312 version 9.0.0 Release 9

84

ETSI TS 124 312 V9.0.0 (2010-01)

<DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> </Node> </Node> <Node> <NodeName>OperatorDifferentiatedTextField</NodeName> <DFProperties> <AccessType> <Get/> <Replace/> </AccessType> <DFFormat> <chr/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>The differentiated operator text field for this cell.</DFTitle> <DFType> <MIME>text/plain</MIME> </DFType> </DFProperties> </Node> <Node> <NodeName>Ext</NodeName> <!-- The Extension node starts here. --> <DFProperties> <AccessType> <Get/> </AccessType> <DFFormat> <node/> </DFFormat> <Occurrence> <ZeroOrOne/> </Occurrence> <DFTitle>A collection of all Extension objects.</DFTitle> <DFType> <DDFName/> </DFType> </DFProperties> </Node> </Node> </MgmtTree>

ETSI

0 8. C1-084560 Includes the following contributions agreed by CT1: C1-084830.2.3.3. C1-084452. C1-084559.0. C1-084451.11 and to refer to IEEE 802.1.2.1.0 8.2.0 8.0 8.0.0 8.0 8.0 8.2.1.0 8.0 8.0.11u Naming of ANDSF MO tree 3 PLMN information to ANDSF for roaming UE Old New 0.0.1.0 8.4.0 8.0 8.0 8.0 8.0. C1-085346.0 (2010-01) Annex C (informative): Change history Change history Date 2008-10 TSG # CT1#55 bis CT1#56 TSG Doc.0 CP-090125 CP-090131 CP-090130 CP-090128 CP-090127 CP-090127 CP-090129 CP-090413 CP-090413 CP-090413 CP-090413 CP-090655 CP-090655 CP-090655 CP-090901 0001 0005 0007 0012 0016 0017 0019 0008 0020 0021 0024 0028 0029 0030 0034 CP-090901 0036 CP-090937 0033 ETSI . C1-084557.0 8.0. C1-084558.0 8.0 8.0 8.0.4. C1-085339 Alignments and cleanups by the rapporteur Version 1.0 8.0 1.0 2008-11 0.0 8.11 2 Aligning ANDSF MO to request from IEEE 802.0 8.1.0 8.0.0 created for presentation to CT#42 for information and approval Version 8.3.1.0 8.0 8.0 8.0.0.3.2.3.1.0 Release 9 85 ETSI TS 124 312 V9.0 8.0.0 2008-11 2008-12 2009-03 2009-03 2009-03 2009-03 2009-03 2009-03 2009-03 2009-06 2009-06 2009-06 2009-06 2009-09 2009-09 2009-09 2009-12 2009-12 2009-12 CT#42 CT#43 CT#43 CT#43 CT#43 CT#43 CT#43 CT#43 CT#44 CT#44 CT#44 CT#44 CT#45 CT#45 CT#45 CT#46 CT#46 CT#46 0.0 9.1.0 8.0 8.0 0.1.2.0.2.1.0 8.0 8. C1-085347.312 version 9. C1-085155.2.0 8.0.0 1.0. C1-085536.2.4.1. C1-085554.0 8.1. C1-085343.1. CR Rev Subject/Comment Includes the following contributions agreed by CT1: C1-084148.3GPP TS 24. C1-085535.0 8.0 created after approval in CT#42 4 Adding ConnMO reference and Correct the Alert Type urn for the ANDSF MO registered by OMNA 1 TimeOfDay Modification 2 Geo_location identifiers 2 Corrections and cleanups of the ANDSF MO 2 Creating the DDF for the ANDSF MO 1 Removal of editor"s notes 3 Additional 3GPP cell identities in ANDSF MO 1 urn for the WNDS MO registered by OMNA and minor corrections 2 Clarifications and clean-ups 2 Updates and corrections to the the WNDS MO 4 Correction of ANDSF initiated provisioning 1 Format type correction 1 Corrections to ANDSF MO to align with HESSID of 802. C1-084151.0.0 8.

0.0.3GPP TS 24.0 (2010-01) History Document history V9.0 Release 9 86 ETSI TS 124 312 V9.0.312 version 9.0 January 2010 Publication ETSI .