3GPP-24.312 ANDSF MO: LTE-UMTS Mobility Management Object for Inter-system Discovery

需积分: 10 156 浏览量更新于2024-07-19 收藏 1.51MB PDF 举报

3GPP-24.312- ANDSF MO 是一项重要的技术规范，它定义了在移动通信系统中，Access Network Discovery and Selection Function (ANDSF) 和 User Equipment (UE) 之间使用的管理对象（Management Objects, MO）。这个MO设计遵循OMA Device Management (DM) 协议版本1.2及更高版本的要求，具体采用OMA DM Device Description Framework (DDF) 进行描述，如OMA-ERELD-DM-V1_2标准所述。 ANDSF MO的核心目标是实现跨系统的移动性策略管理和网络发现信息的管理。这些管理对象涵盖了与接入网络发现和选择相关的参数，对于支持无缝的网络切换和用户服务需求的满足至关重要。在3GPP TS 22.278 [2] 中，详细阐述了服务需求的定义，而3GPP TS 23.402 [4] 则提供了功能需求的说明，确保了ANDSF能够高效地执行其职责。 3GPP TS 24.312 版本12.11.0 Release 12 的这份技术规范，针对的是 Long Term Evolution (LTE) 和 Universal Mobile Telecommunications System (UMTS) 的互操作性，特别是针对LTE向UMTS的网络切换场景。MO的设计旨在通过标准化的接口，使得ANDSF能与UE进行交互，管理UE对不同网络类型（如3G或4G）的选择和切换过程，从而确保用户的连接质量和体验。整个文档由欧洲电信标准化协会(ETSI)发布，可供下载，强调了电子版和打印版的版权保护，并指出任何修改必须获得ETSI的书面授权。同时，官方发布的 Portable Document Format (PDF) 版本被认为是唯一的权威文档来源。 3GPP-24.312- ANDSF MO 是移动通信网络中的一项关键技术文档，它规范了UE与ANDSF之间的交互，促进了不同网络技术间的兼容性和用户体验优化。理解和掌握这个MO对于网络运营商、设备制造商以及开发人员来说，都是实现高效网络运营和服务质量提升的重要参考。

ETSI

ETSI TS 124 312 V12.11.0 (2016

01)

3GPP TS 24.312

version 12.11.0 Release 12

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>.

Reserved: 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 3GPP TS 23.402 [4] apply:

S2a

For the purpose of the present document, the terms and definitions given in 3GPP TS 24.302 [3AA] apply:

Home ANDSF

Visited ANDSF

WLANSP

PSPL

RAN Assistance Information

OPI

For the purposes of the present document, the terms and definitions given in 3GPP TS 24.303 [3AB] apply:

Home Agent

3.2 Abbreviations

For the purposes of the present document, the following abbreviations apply:

ANDSF Access Network Discovery and Selection Function

CPICH Common Pilot Channel

DDF Device Description Framework

DIDA Data IDentification in ANDSF

DM Device Management

DS Differenciated Services

E-UTRA Enhanced Universal Terrestrial Radio Access

FDD Frequency Division Duplex

FQDN Fully Qualified Domain Name

GERAN GSM Edge Radio Access Network

IARP Inter-APN Routing Policy

IFOM IP Flow Mobility

ETSI

ETSI TS 124 312 V12.11.0 (2016

01)

3GPP TS 24.312 version 12.11.0 Release 12

ISMP Inter-System Mobility Policy

ISRP Inter-System Routing Policy

MAPCON Multi Access PDN Connectivity

MO Management Object

OMA Open Mobile Alliance

OPI Offload Preference Indicator

OS Operating System

OSAppId Operating System specific Application Identifier

OSId Operating System Identifier

P-CCPCH Primary Common Control Physical Channel

PSPL Preferred Service Providers List

RSCP Receive Signal Code Power

RSRP Reference Signal Received Power

RSRQ Reference Signal Received Quality

RSSI Receive Signal Strength Indicator

ToS Type of Service

TDD Time Division Duplex

UE User Equipment

UTRA Universal Terrestrial Radio Access

UUID Universally Unique IDentifier

WLANSP WLAN Selection Policy

WNDS WiMAX Network Discovery and Selection

4 ANDSF MO

4.1 Descriptions

4.1.1 General

The ANDSF MO is used to manage Inter-System Mobility Policy (ISMP), Inter-System Routing Policy (ISRP), Inter-

APN Routing Policy (IARP), RuleSelectionInformation and WLAN Selection Policy (WLANSP) as well as access

network discovery information stored in a UE supporting provisioning of such information from an ANDSF. In

addition, the ANDSF MO is also used to manage the HomeNetworkPreference policy stored in a UE supporting

provisioning of Preferred Service Provider List (PSPL) and S2a Connectivity Preference information from an ANDSF.

The ANDSF may initiate the provision of information from the ANDSF to the UE as specified in

3GPP TS 24.302 [3AA].

If the UE wishes to provide the user location information to the ANDSF when sending the Package 1 (see OMA-TS-

DM_Protocol-V1_2 [5A]), the UE shall include in the Package 1 a Generic Alert message (along with other commands)

where the "Type" element is set to "urn:oma:at:ext-3gpp-andsf:1.0:ue_location", the "Data" element is set to the

information contained in the UE_Location node subtree (see subclause 5.6) encoded as XML formatted as specified by

OMA-TS-DM_TNDS-V1_2 [5B] and the "LocURI" element (inside the "Source" element) is set to the address of the

ANDSF Management Object as specified by OMA-TS-DM_Protocol-V1_2 [5A].

If the UE wishes to provide the UE profile information to the ANDSF while sending Package 1 (see OMA-TS-

DM_Protocol-V1_2 [5A]), the UE shall include in Package 1 a Generic Alert message (along with other commands)

where the "Type" element is set to "urn:oma:at:ext-3gpp-andsf:1.0:ue_profile", the "Data" element is set to the

information contained in the UE_Profile node subtree (see subclause 5.7A) encoded as XML formatted as specified by

OMA-TS-DM_TNDS-V1_2 [5B] and the "LocURI" element (inside the "Source" element) is set to the address of the

ANDSF Management Object as specified by OMA-TS-DM_Protocol-V1_2 [5A].

The UE may initiate the provision of all available information from the ANDSF, using a client-initiated session Alert

message of code "Generic Alert" (see OMA-TS-DM_Protocol-V1_2 [5A]). When requesting all available information

from ANDSF, the "Type" element of the OMA DM generic alert message shall be set to "urn:oma:at:ext-3gpp-

andsf:1.0:provision", the "LocURI" element (inside the "Source" element) shall be set to the address of the ANDSF

Management Object as specified by OMA-TS-DM_Protocol-V1_2 [5A] and the "Data" element is not included.

When the UE is requesting partial ANDSF information, i.e. ISMP, Discovery information or ISRP as defined in

subclauses 4.1.2, 4.1.3 and 4.1.5 respectively, the ANDSF server should provide the requested ANDSF information to

ETSI

ETSI TS 124 312 V12.11.0 (2016

01)

3GPP TS 24.312 version 12.11.0 Release 12

the UE. Additionally, the ANDSF server may provide other than the requested ANDSF information during the same

ANDSF session.

ISMP prioritizes access networks when the UE is not capable to connect to the EPC through multiple accesses. ISRP

indicates how to distribute traffic among available accesses when the UE is capable to connect to the EPC through

multiple accesses (i.e. the UE is configured for IFOM, MAPCON, non-seamless WLAN offload or any combination of

these capabilities). IARP indicates which traffic should be routed across different PDN connections and which traffic

should be non-seamlessly offloaded to WLAN. DiscoveryInformation provides further information for the UE to access

the access network defined in the ISMP or in the ISRP. WLANSP provides information for the UE to select and reselect

a WLAN. RuleSelectionInformation indicates whether to prioritise ISMP, ISRP and WLANSP provided by HPLMN or

by VPLMN when the UE is roaming and ANDSF rules are available from both HPLMN and VPLMN. The PSPL in

HomeNetworkPreference is used by the UE to determine the selected service provider in order to construct NAI (see

IETF RFC 4282 [25]) to perform 3GPP-based access authentication over the selected WLAN as specified in

3GPP TS 23.402 [4]. HomeNetworkPreference policy also contains S2a Connectivity Preference which is used to

indicate whether or not the home operator prefers the UE to establish PDN connections over WLAN by using the

applicable S2a procedures specified in 3GPP TS 23.402 [4].

The MO defines validity areas, position of the UE and availability of access networks in terms of geographical

coordinates. The way such coordinates are retrieved is implementation dependant (e.g. GPS receiver).

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 discovery information.

The Management Object Identifier is: urn:oma:mo:ext-3gpp-andsf:1.0.

The OMA DM Access Control List (ACL) property mechanism as standardized (see Enabler Release Definition OMA-

ERELD-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 shall ignore any node which is a child of the ANDSF MO root node and is not supported by the UE. The

ANDSF server shall ignore any node which is a child of the ANDSF MO root node and is not supported by the ANDSF

server.

The UE shall support receiving OMA DM commands with bodies encoded as XML formatted as described in OMA-

TS-DM_TNDS-V1_2 [5B].

Validity criteria container of the ANDSF MO enables reducing redundancies in ANDSF MO.

4.1.2 Policy (ISMP)

The Policy node represents ISMP and the information consists of a set of one or more ISMP rules. At any point in time

there shall be at most one rule applied, that rule is referred to as the 'active' rule. There may hence be zero or one 'active'

rule.

The rules have a number of validity conditions (e.g. current access technology and location) where one or more may be

present and set to a value. The rules also have a number of results (e.g. preferred access technology and restricted access

technology) to be used whenever a rule is 'active'. If there are no results for the 'active' rule, it is implementation

dependent how UE performs network selection. When ANDSF policy selection rules identify an available network, the

highest priority rule becomes 'active' rule and network re-selection is performed. If the UE is roaming and ANDSF rules

from both Home ANDSF and Visited ANDSF are available, the active rule is selected according to the

<ANDSF>/RuleSelectionInformation as specified in subclauses 4.1.9 and 5.10.

While the rule remains 'active', UE shall keep considering higher priority networks, than currently selected, in the

prioritized network list of the rule. 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, out of potentially several valid rules, it should consider as 'active'.

The validity of the rule can be restricted by validity conditions. The validity of the rule takes into account ValidityArea,

ValidityAreaRef, Roaming, TimeOfDay, and TimeOfDayRef, where each existing non-empty node must match in order

to make the rule valid. The UE does not make any evaluation on nodes which are present and empty. In addition, this

rule is considered valid if none of the validity conditions exist.

The UE capable of any combinations of IFOM or MAPCON or non-seamless WLAN offload with all those

combination of capabilities disabled, or a UE which is not IFOM capable and is not MAPCON capable and is not

non-seamless WLAN offload capable, may initiate the provision of ISMP information from the ANDSF, using a client

ETSI

ETSI TS 124 312 V12.11.0 (2016

01)

3GPP TS 24.312 version 12.11.0 Release 12

initiated session containing a generic alert. When requesting ISMP, the "Type" element of the OMA DM generic alert

message shall be set to "urn:oma:at:ext-3gpp-andsf:1.0:provision-single-if", the "LocURI" element (inside the "Source"

element) shall be set to the address of the ANDSF Management Object as specified by OMA-TS-DM_Protocol-

V1_2 [5A] and the "Data" element is not included.

The UE shall ignore any rule containing a node not supported by the UE.

4.1.3 Discovery information

The UE may initiate the provision of discovery information from the ANDSF using a client initiated session containing

a generic alert. When requesting discovery information, the "Type" element of the OMA DM generic alert message

shall be set to "urn:oma:at:ext-3gpp-andsf:1.0:provision-disc-info", the "LocURI" element (inside the "Source" element)

shall be set to the address of the ANDSF Management Object as specified by OMA-TS-DM_Protocol-V1_2 [5A] and

the "Data" element is not included.

The UE shall ignore any node which is a descendant of the DiscoveryInformation node and is not supported by the UE.

4.1.4 UE location

The MO has a node indicating the position of the UE. The trigger for updating the value of this node is that the location

information it contains is no longer valid (i.e. the UE has changed its position) or some other manufacturer specific

trigger. The update of the information contained in this node doesn"t necessarily imply any interaction with the ANDSF

server.

The ANDSF server shall ignore any node which is a descendant of the UE_Location node and is not supported by the

ANDSF server.

4.1.5 ISRP

The ISRP information consists of a set of one or more ISRP rules. Each ISRP rule contains indication on traffic

distribution for UEs that are configured for IFOM, MAPCON or non-seamless WLAN offload.

Each ISRP rule has a PLMN leaf and an optional Roaming leaf. Roaming and PLMN leaves are used by the UE to

determine if an ISRP rule is valid, see subclause 5.7.60 and 5.7.61. At any point in time there shall be at most one ISRP

rule used for routing, and, that ISRP rule is referred to as the 'active' ISRP rule. There can be multiple valid ISRP rules

at the same time. If UE is roaming and ANDSF rules from both Home ANDSF and Visited ANDSF are available, the

active rule is selected according to the <ANDSF>/RuleSelectionInformation as specified in subclauses 4.1.9 and 5.10.

An ISRP rule can contain one or more flow distribution containers. These are ForFlowBased for IFOM service,

ForServiceBased for MAPCON and ForNonSeamlessOffload for Non-seamless WLAN offload. A UE evaluates only

the supported flow distribution containers of the 'active' ISRP rule. A flow distribution container can have one or more

flow distribution rules.

A flow distribution rule can have a validity condition defined by the RoutingCriteria node. The validity of the flow

distribution rule takes into account ValidityArea, ValidityAreaRef, TimeOfDay, TimeOfDayRef,

RANValidityCondition and RANValidityConditionRef where each existing non-empty node must match in order to

make the rule valid. In addition, this flow distribution rule without any validity conditions is considered valid, i.e.

validity condition is fulfilled. A flow distribution rule is applied only if the validity condition is fulfilled and if the flow

distribution rule is contained by the 'active' ISRP rule. A flow distribution rule has a number of results (e.g. preferred

access technology and restricted access technology) defined in the RoutingRule node to be used whenever the flow

distribution rule is applied. Each flow distribution rule has also a mandatory node identifying the data traffic (e.g. based

on APN or IP flow description) to which the results contained in RoutingRule node apply.

If there are no results for an 'active' ISRP rule, it is implementation dependent how UE performs network selection for

the class of traffic to which the results apply.

In addition to conditions, results and traffic class, there is a rule priority that shall be set for each flow distribution rule.

The rule priority is encoded in RulePriority leaf, and it enables the UE to determine which flow distribution rule, out of

potentially several flow distribution rules, contained in every supported flow distribution container of the 'active' ISRP

rule, it should apply to an IP flow matching the data traffic description of the multiple flow distribution rules. The ISRP

rule consists of one or more flow distribution container. Each flow distribution container is applicable for either IFOM,

MAPCON, or non-seamless WLAN offload. The scope of the RulePriority extends across all supported flow

ETSI

ETSI TS 124 312 V12.11.0 (2016

01)

3GPP TS 24.312 version 12.11.0 Release 12

distribution containers belonging to the 'active' ISRP rule. If the same flow matches multiple flow distribution rules,

then the flow distribution rule with the highest RulePriority is applied for the IP flow.

If a flow matches multiple flow distribution rules with the same highest priority, the selection of the flow distribution

rule for routing of that flow is implementation dependent. If there are multiple applied flow distribution rules within the

'active' ISRP rule and they refer to the same access technology but different access networks and the UE is not able to

have connection to all of them at the same time, the selection of the access network is implementation dependant.

The UE configured for IFOM or MAPCON or non-seamless WLAN offload or any combination of these capabilities,

may initiate the provision of ISRP information from the ANDSF, using a client initiated session containing a generic

alert. When requesting ISRP, the "Type" element of the OMA DM generic alert message shall be set to "urn:oma:at:ext-

3gpp-andsf:1.0:provision-multiple-if", the "LocURI" element (inside the "Source" element) shall be set to the address of

the ANDSF Management Object as specified by OMA-TS-DM_Protocol-V1_2 [5A] and the "Data" element is not

included.

If the UE indicated support for ISRP rules based on Application Identifers (DIDA) in DevCapability, then when the

ANDSF server provides an ISRP rule containing an App-ID interior node, the ANDSF server sets the OSId leaf

contained in the App-ID interior node to the value of one of the OSId leaves contained in the UE_Profile interior node.

The UE shall ignore any node which is a child of the ISRP rule (i.e. flow distribution container) and is not supported by

the UE.

The UE shall ignore any flow distribution rule containing a node not supported by the UE.

4.1.6 UE_Profile

The UE_Profile node contains information pertaining to the UE that can be used by the ANDSF server for information

provisioning. This node is set by the UE prior to establishing a connection with the ANDSF server.. The ANDSF server

retrieves information in this node after UE establishes connection with the ANDSF server. The update of the

information contained in this node doesn"t necessarily imply any interaction with the ANDSF server.

The ANDSF server shall ignore any node which is a descendant of the UE_Profile node and is not supported by the

ANDSF server.

4.1.7 WLANSP

The WLANSP information consists of a set of one or more WLANSP rules. At any point in time, there shall be at most

one rule applied, that rule is referred to as the 'active' rule. There can be multiple valid WLANSP rules at the same time.

The validity of the rule can be restricted by validity conditions. The validity of the rule takes into account ValidityArea,

ValidityAreaRef, Roaming, TimeOfDay and TimeOfDayRef, where each existing non-empty node must match in order

to make the rule valid. The UE does not make any evaluation on nodes that are present and empty. In addition, this rule

is considered valid if none of the validity conditions exist.

A WLANSP rule can have one or more WLAN selection criteria defined under the

ANDSF/WLANSP/<X>/SelectionCriteria node. Each selection criterion contains:

- ANDSF/WLANSP/<X>/SelectionCriteria/<X>/CriteriaPriority leaf;

- ANDSF/WLANSP/<X>/SelectionCriteria/<X>/HomeNetworkIndication leaf;

- ANDSF/WLANSP/<X>/SelectionCriteria/<X>/PreferredRoamingPartnerList leaf;

- ANDSF/WLANSP/<X>/SelectionCriteria/<X>/MinBackhaulThreshold leaf;

- ANDSF/WLANSP/<X>/SelectionCriteria/<X>/MaximumBSSLoadValue leaf;

- ANDSF/WLANSP/<X>/SelectionCriteria/<X>/RequiredProtoPortTuple leaf;

- ANDSF/WLANSP/<X>/SelectionCriteria/<X>/SPExclusionList leaf; and

- ANDSF/WLANSP/<X>/SelectionCriteria/<X>/PreferredSSIDList node.

剩余380页未读，继续阅读

BingoAmI

粉丝: 5
资源: 12

3GPP-24.312 ANDSF MO: LTE-UMTS Mobility Management Object for In...

最新资源

3GPP-24.312 ANDSF MO: LTE-UMTS Mobility Management Object for In...

3GPP-TS-24.301：EPS NAS协议规范（Release 9）

3GPP TS23.273: 5G 定位服务中文翻译

L830-GLM.2模块硬件用户手册-电磁兼容标准引用

最新3GPP - 2018.09.26

polar-3gpp-matlab.zip

3Gpp-WCDMA.rar

3GPP-36.104

robmaunder-turbo-3gpp-matlab.zip

robmaunder-polar-3gpp-matlab.zip

3GPP-TS-24.301

最新资源