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 TS 24.302. 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 subclause 4.1.2, subclause 4.1.3 and subclause 4.1.5 respectively, the ANDSF server should provide the requested ANDSF information to 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 RFC 4282) to perform 3GPP-based access authentication over the selected WLAN as specified in TS 23.402. 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 TS 23.402. 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.

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 subclause 4.1.9 and subclause 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 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.

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.

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.

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 subclause 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 subclause 4.1.9 and subclause 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 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.

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.

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.

The UE does not make any evaluation on nodes and leaves that are present and empty. A WLAN that matches all the present non-empty nodes and leaves of a selection criterion of the active WLANSP rule is considered as matching the selection criterion. The priority of a selection criterion is encoded in the ANDSF/WLANSP/<X>/SelectionCriteria/<X>/CriteriaPriority leaf. The WLAN priority defined in the PreferredSSIDList node represents the priority of the WLAN matching the selection criterion. In addition to validity conditions and selection criteria, there is a rule priority that shall be set for each rule. The rule priority is encoded in ANDSF/WLANSP/<X>/RulePriority leaf, and it enables the UE to determine which rule, out of potentially several valid rules, it should consider as 'active'. 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 subclause 4.1.9 and subclause 5.10. The UE may initiate the provision of WLANSP information from the ANDSF, using a client-initiated session containing a generic alert. When requesting WLANSP, the "Type" element of the OMA DM generic alert message shall be set to "urn:oma:at:ext-3gpp-andsf:1.0:provision-wlansp-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 rule containing a node not supported by the UE.

The IARP information consists of a set of one or more IARP rules. Each IARP rule contains indication on traffic distribution for UEs that selects an APN associated with an existing PDN connection or non-seamless WLAN offload for routing the traffic matching specific IP flows. Each IARP rule has a PLMN leaf and an optional Roaming leaf. Roaming and PLMN leaves are used by the UE to determine if an IARP rule is valid, see subclause 5.9.60 and subclause 5.9.61. At any point in time there shall be at most one IARP rule applied, that IARP rule is referred to as the 'active' IARP rule. There can be multiple valid IARP rules at the same time, in which case the selection of the active IARP rule implementation-dependent. When the UE is roaming, the V-ANDSF shall not provide any IARP to a roaming UE. If the UE receives IARP from a V-ANDSF then the UE shall ignore it. An IARP rule can have two flow distribution containers. These are ForInterAPNRouting for Inter-APN routing and ForNonSeamlessOffload for non-seamless WLAN offload. 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' IARP rule. A flow distribution rule has a number of results (e.g. preferred APN and restricted APN) 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 associated with the sent traffic or IP flow description of the sent traffic) to which the results contained in RoutingRule node apply. An IARP rule shall be first applied followed by an ISRP rule for the IP flow. If there are no results for an 'active' IARP rule, an ISRP rule shall be applied for the IP flow. If there are no results for 'active' IARP rule and 'active' ISRP rule, then it is implementation dependent how UE performs APN selection or non-seamless WLAN offload for the class of traffic to which the results apply. In addition to conditions, results and IP flow description, 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 matching flow distribution rules, of the 'active' IARP rule, it should apply to an IP flow matching the data traffic description of the multiple flow distribution rules. If the same flow matches multiple flow distribution rules, then the flow distribution rule with the highest RulePriority is applied for the IP flow. The scope of the RulePriority extends across all supported flow distribution containers belonging to the 'active' IARP rule. 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. The UE may initiate the provision of IARP information from the ANDSF, using a client initiated session containing a generic alert. When requesting IARP, the "Type" element of the OMA DM generic alert message shall be set to "urn:oma:at:ext-3gpp-andsf:1.0:provision-apnnswo-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 IARP rules based on Application Identifers (DIDA) in DevCapability, then when the ANDSF server provides an IARP 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 IARP 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.

The rule selection information represents VPLMNs with preferred WLAN selection rules defined in the RuleSelectionInformation node, which includes a VPLMNswithPreferredRules node and a PLMN leaf, see subclause 5.10. The VPLMNswithPreferredRules node contains one or more VPLMNs. Rule selection information indicates whether to prioritise ISMP, ISRP and WLANSP provided by VPLMN or by HPLMN when the UE is roaming and ANDSF rules are available from both HPLMN and VPLMN.

Home Network Preference information assists the UE in selecting a WLAN, a service provider for 3GPP-based authentication over WLAN, and an ePDG for tunnel management procedure as specified in TS 23.402. The UE shall only use the Home Network Preference information provided by the H-ANDSF or, if H-ANDSF is not available, statically provisioned in the UE. The UE shall ignore any Home Network Preference information provided by V-ANDSF . The UE may initiate the provisioning of HomeNetworkPreference information from the ANDSF, using a client-initiated session containing a generic alert. When requesting HomeNetworkPreference, the "Type" element of the OMA DM generic alert message shall be set to "urn:oma:at:ext-3gpp-andsf:1.0:provision-homenetworkpreference-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.

Visited Network Preference information assists the UE in selecting a WLAN and a service provider for 3GPP-based authentication over WLAN when the UE is roaming in a V-PLMN, as specified in TS 23.402. The Visited Network Preference information may be provided by a V-ANDSF only. The UE shall ignore any VisitedNetworkPreference rules provided by an ANDSF other than the V-ANDSF. The UE may initiate the provisioning of VisitedNetworkPreference information from the ANDSF, using a client-initiated session containing a generic alert. When requesting VisitedNetworkPreference, the "Type" element of the OMA DM generic alert message shall be set to "urn:oma:at:ext-3gpp-andsf:1.0:provision-visitednetworkpreference-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.

Validity criteria container contains ValidityArea interior nodes, TimeOfDay interior nodes, and RANValidityCondition interior nodes referenced from other parts of ANDSF MO.

The Untrusted_WLAN node contains parameter for an untrusted WLAN connection. This node can be configured in the UE by the HPLMN only and is used to establish a connection with an untrusted WLAN. The UE shall ignore any node which is a descendant of the Untrusted_WLAN node and if not supported by the UE.