Content for  TS 24.312  Word version:  17.0.0

Top   Top   None   None   Next
1…   4…   4.2…   5…   5.5   5.6   5.7…   5.8   5.9   5.10…   6…   A…


1  Scopep. 14

The present document defines management objects that can be used by the Access Network Discovery and Selection Function (ANDSF) and the UE.
The Management Objects (MO) are compatible with the OMA Device Management (DM) protocol specifications, version 1.2 and upwards, and are defined using the OMA DM Device Description Framework (DDF) as described in the enabler release definition OMA-ERELD-DM-V1_2 [5].
The MOs consist of relevant parameters:
  • for access network discovery;
  • for access network selection;
  • for traffic steering; and
  • for ePDG selection;
that can be managed by the ANDSF.
The service requirements and the functional requirements for the access network discovery and access network selection are described in TS 22.278 and in TS 23.402 respectively.

2  Referencesp. 14

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
TR 21.905: "Vocabulary for 3GPP Specifications".
TS 22.278: "Service requirements for the Evolved Packet System (EPS)".
TS 23.003: "Numbering, addressing and identification".
TS 23.032: "Universal Geographical Area Description (GAD)".
TS 24.302: "Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks".
TS 24.303: "Mobility management based on Dual-Stack Mobile IPv6".
TS 25.331: "Radio Resource Control (RRC); Protocol Specification".
TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Resource Control (RRC); Protocol specification".
TS 23.402: "Architecture enhancements for non-3GPP accesses".
OMA-DDS-DM_ConnMO-V1_0- 20081107-A: "Standardized Connectivity Management Objects", Approved Version 1.0 - 07 Nov 2008.
OMA-DDS-DM_ConnMO_WLAN-V1_0-20081024-A: "Standardized Connectivity Management Objects WLAN Parameters", Approved Version 1.0 - 24 Oct 2008.
OMA-ERELD-DM-V1_2: "Enabler Release Definition for OMA Device Management".
OMA-TS-DM_Protocol-V1_2: "OMA Device Management Protocol".
OMA-TS-DM_TNDS-V1_2: "OMA Device Management Tree and Description Serialization".
WiMAX Forum Network Architecture Release 1.0 version 1.2.2 - Stage 2: "Architecture Tenets, Reference Model and Reference Points", May 2008.
WiMAX Forum Network Architecture Release 1.0 version 1.2.2 - Stage 3: "Detailed Protocols and Procedures", May 2008.
WiMAX Forum Mobile System Profile Release 1.0 Approved Specification Revision 1.4.0: April 2007.
[9]  Void.
IEEE Std 802.16e-2005 and IEEE Std 802.16-2004/Cor1-2005: "IEEE Standard for Local and Metropolitan Area Networks, Part 16: Air Interface for Fixed and Mobile Broadband Wireless Access Systems Amendments 2 and Corrigendum 1", February 2006.
RFC 3260  (April 2002): "New Terminology and Clarifications for Diffserv".
RFC 3629  (November 2003): "UTF-8, a transformation format of ISO 10646".
"Unicode 5.1.0: Unicode Standard Annex #15; Unicode Normalization Forms", March 2008.
3GPP2 C.S0005: "Upper Layer (Layer 3) Signaling Standard for cdma2000 Spread Spectrum Systems".
3GPP2 C.S0016: "Over-the-Air Service Provisioning of Mobile Stations in Spread Spectrum Standards".
3GPP2 C.S0024: "cdma2000 High Rate Packet Data Air Interface Specification".
ISO 8601:2004: "Data elements and interchange formats -- Information interchange -- Representation of dates and times".
[17]  Void.
IANA Assigned Internet Protocol Numbers: (
[19]  Void.
[20]  Void.
[21]  Void.
RFC 4122  (July 2005): "A Universally Unique IDentifier (UUID) URN Namespace".
Wi-Fi Alliance: "Hotspot 2.0 (Release 2) Technical Specification, version 1.0.0", 2014-08-08.
RFC 6088  (January 2011): "Traffic Selectors for Flow Bindings".
RFC 4282 (December 2005): "The Network Access Identifier".
IEEE Std 802.11™-2012: "Information Technology- 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".

3  Definitions and abbreviationsp. 16

3.1  Definitionsp. 16

For the purposes of the present document, the terms and definitions given in TR 21.905 apply.
Active rule:
A rule that has been selected by the UE as the active rule as specified in clause 4.
Empty node:
A node which is present in the ANDSF MO with no internal node or leaf object(s) to it is present.
Inter-System Routing Policy rule:
In the present document, Inter-System Routing Policy (ISRP) consists of one or more ISRP rules. ISRP rule is a single instance of <X>/ISRP/<X>. The ISRP rule consists of one or more flow distribution container.
Inter-APN Routing Policy rule:
In the present document, Inter-APN Routing Policy (IARP) consists of one or more IARP rules. IARP rule is a single instance of <X>/IARP/<X>. The IARP rule consists of one or more flow distribution container.
Flow distribution container:
In the present document, Flow distribution container denotes the node <X>/ISRP/<X>/ForFlowBased, <X>/ISRP/<X>/ForServiceBased, <X>/ISRP/<X>/ForNonSeamlessOffload/, <X>/IARP/<X>/ForInterAPNRouting or <X>/IARP/<X>/ForNonSeamlessOffload/.
Flow distribution rule:
In the present document, Flow distribution rule denotes a single instance of <X>/ISRP/<X>/ForFlowBased/<X>, <X>/ISRP/<X>/ForServiceBased/<X>, <X>/ISRP/<X>/ForNonSeamlessOffload/<X>, <X>/IARP/<X>/ForInterAPNRouting/<X> or <X>/IARP/<X>/ForNonSeamlessOffload/<X>.
The value "reserved" is assigned to a code point to indicate that it is reserved for future use. The present document specifies no processing rules for handling of "reserved" value by the receiving entity.
Operating System (OS):
collection of UE software that provides common services for applications.
Operating System Identifier (OSId):
an identifier identifying the operating system.
OS specific Application Identifier (OSAppId):
an identifier associated with a given application and uniquely identifying the application within the UE for a given operating system.
Valid rule:
A rule that fulfils the validity criteria that is specified in clause 4.
For the purposes of the present document, the following terms and definitions given in TS 23.402 apply:
For the purpose of the present document, the terms and definitions given in TS 24.302 apply:
Visited ANDSF
RAN Assistance Information
For the purposes of the present document, the terms and definitions given in TS 24.303 apply:
Home Agent

3.2  Abbreviations |R12|p. 16

For the purposes of the present document, the following abbreviations apply:
Access Network Discovery and Selection Function
Common Pilot Channel
Device Description Framework
Data IDentification in ANDSF
Device Management
Differenciated Services
evolved Packet Data Gateway
Enhanced Universal Terrestrial Radio Access
Frequency Division Duplex
Fully Qualified Domain Name
GSM Edge Radio Access Network
Inter-APN Routing Policy
IP Flow Mobility
Inter-System Mobility Policy
Inter-System Routing Policy
Multi Access PDN Connectivity
Management Object
Open Mobile Alliance
Offload Preference Indicator
Operating System
Operating System specific Application Identifier
Operating System Identifier
Primary Common Control Physical Channel
Preferred Service Providers List
Receive Signal Code Power
Reference Signal Received Power
Reference Signal Received Quality
Receive Signal Strength Indicator
Type of Service
Time Division Duplex
User Equipment
Universal Terrestrial Radio Access
Universally Unique IDentifier
WLAN Selection Policy
WiMAX Network Discovery and Selection

Up   Top   ToC