5.7 ISRP
24.3123GPPAccess Network Discovery and Selection Function (ANDSF) Management Object (MO)Release 17TS
5.7.1 ANDSF/ISRP/
The ISRP node acts as a placeholder for policies for ISRP.
– Occurrence: ZeroOrOne
– Format: node
– Access Types: Get, Replace
– Values: N/A
5.7.2 ANDSF/ISRP/<X>
This interior node acts as a placeholder for one or more ISRP rules.
– Occurrence: OneOrMore
– Format: node
– Access Types: Get, Replace
– Values: N/A
An ISRP rule can contain one or more of the following nodes: ForFlowBased, ForServiceBased or ForNonSeamlessOffload.
5.7.3 ANDSF/ISRP/<X>/ForFlowBased
The ForFlowBased node represents flow distribution container indicating data distribution among accesses based on flow description.
– Occurrence: ZeroOrOne
– Format: node
– Access Types: Get, Replace
– Values: N/A
If this node is present, it implies that the Home Agents of the PLMN identified in the leaf ANDSF/ISRP/<X>/PLMN of the same rule support IFOM.
5.7.4 ANDSF/ISRP/<X>/ForFlowBased/<X>/
This interior node acts as a placeholder for one or more flow distribution rule.
– Occurrence: OneOrMore
– Format: node
– Access Types: Get, Replace
– Values: N/A
5.7.5 ANDSF/ISRP/<X>/ForFlowBased/<X>/IPFlow
The IPFlow node indicates the flow description for a particular flow distribution rule.
– Occurrence: One
– Format: node
– Access Types: Get, Replace
– Values: N/A
An empty IPFlow node indicates the match-all flow description.
If the flow distribution rule contains more than one instance of the ANDSF/ISRP/<X>/ForFlowBased/<X>/IPFlow/<X> node (i.e. flow description), the UE shall consider the flow distribution rule if at least one of the flow descriptions as described in subclause 5.7.6 matches the traffic.
5.7.6 ANDSF/ISRP/<X>/ForFlowBased/<X>/IPFlow/<X>/
This interior node acts as a placeholder for one or more flow description.
– Occurrence: OneOrMore
– Format: node
– Access Types: Get, Replace
– Values: N/A
If the flow description is defined with more than one interior node or leaf (i.e. App-ID, AddressType, etc.) within a single instance of the ANDSF/ISRP/<X>/ForFlowBased/<X>/IPFlow/<X> node, then UE shall consider the flow description matching the traffic only if all the present interior nodes and leaf values match the traffic.
5.7.6A ANDSF/ISRP/<X>/ForFlowBased/<X>/IPFlow/<X>/App-ID
This interior node acts as a placeholder for an IPFlow identification based on an applicationID.
An IP flow is evaluated as matching if the IP flow matches at least one child node.
– Occurrence: ZeroOrOne
– Format: node
– Access Types: Get, Replace
– Values: N/A
The absence of this node indicates that the application identifier is not examined when matching packets against the IP flow description of the rule.
5.7.6B ANDSF/ISRP/<X>/ForFlowBased/<X>/IPFlow/<X>/App-ID/<X>/
This interior node acts as a placeholder for one or more combinations of OSId and OSAppId values.
– Occurrence: OneOrMore
– Format: node
– Access Types: Get, Replace
– Values: N/A
An IP flow is evaluated as matching if the IP flow is sent by an application:
– which uses services provided by an OS identified by the OS system identifier in the OSId leaf contained in this interior node; and
– associated with an OS specific application identifier in one of the OSAppId leaves contained in the OSApps interior node.
5.7.6C Void
5.7.6D ANDSF/ISRP/<X>/ForFlowBased/<X>/IPFlow/<X>/App-ID/
<X>/OSId
The OSId leaf indicates an operating system identifier.
– Occurrence: One
– Format: chr
– Access Types: Get, Replace
– Values: <operating system identifier>
The format of the operating system identifier is a Universally Unique IDentifier (UUID) as specified in IETF RFC 4122 [22].
5.7.6E ANDSF/ISRP/<X>/ForFlowBased/<X>/IPFlow/<X>/App-ID/
<X>/OSApps/
This interior node acts as a placeholder for the list of OS specific application identifiers.
– Occurrence: One
– Format: node
– Access Types: Get, Replace
– Values: <N/A>
5.7.6F ANDSF/ISRP/<X>/ForFlowBased/<X>/IPFlow/<X>/App-ID/
<X>/OSApps/<X>
This interior node acts as a placeholder for an OS specific application identifiers.
– Occurrence: OneOrMore
– Format: node
– Access Types: Get, Replace
– Values: <N/A>
5.7.6G ANDSF/ISRP/<X>/ForFlowBased/<X>/IPFlow/<X>/App-ID/
<X>/OSApps/<X>/OSAppId
The OSAppId leaf indicates an OS specific application identifier.
– Occurrence: One
– Format: chr
– Access Types: Get, Replace
– Values: <OS specific application identifier>
Further definition of the format of the OS specific application identifier is beyond the scope of this specification.
5.7.7 ANDSF/ISRP/<X>/ForFlowBased/<X>/IPFlow/<X>/
AddressType
The AddressType leaf indicates the IP version of the addresses describing the IP flow.
– Occurrence: ZeroOrOne
– Format: chr
– Access Types: Get, Replace
– Values: ‘IPv4’, ‘IPv6’
The absence of this leaf indicates that the IP flow described by the rule can have both IPv4 and IPv6 addresses. This field is mandatory if StartSourceIPaddress leaf is present.
5.7.8 ANDSF/ISRP/<X>/ForFlowBased/<X>/IPFlow/<X>/
StartSourceIPaddress
The StartSourceIPaddress leaf indicates the first IP source address of the IP address range of the IP flow description. The source address refers to the IP address of the data packets destined for the UE according to the terminology in the IETF RFC 6088 [24].
– Occurrence: ZeroOrOne
– Format: chr
– Access Types: Get, Replace
– Values: <an IPv4 address>, <an IPv6 address>.
The value of this leaf is an IPv4 address if the AddressType leaf value of the same rule is equal to IPv4. The value of this leaf is an IPv6 address if the AddressType leaf value of the same rule is equal to IPv6. If this leaf represents the first value of an IP source address range, the values of this leaf and the corresponding ANDSF/ISRP/<X>/ForFlowBased/<X>/IPFlow/<X>/EndSourceIPaddress leaf are set so that the IP address range can be represented in prefix notation.
EXAMPLE: IPv4 address range 192.0.2.0 – 192.0.2.255 is equal to 192.0.2.0/24 in prefix notation, and IPv6 address range 2001:db8::/128 – 2001:db8:ffff:ffff:ffff:ffff:ffff:ffff/128 equals 2001:db8::/32 in prefix notation.
The absence of this leaf indicates that source address field of the IP header is not examined when matching packets against the IP flow description of the rule.
The UE ignores an IPFlow instance with a StartSourceIPaddress leaf without a correspondent AddressType leaf. If the IPFlow instance is the only one contained in the flow distribution rule, the UE ignores the flow distribution rule.
When applying the rule to uplink traffic, the UE matches the addresses contained in the range between StartSourceIPaddress and EndSourceIPaddress against destination IP address field of the uplink traffic packets.
5.7.9 ANDSF/ISRP/<X>/ForFlowBased/<X>/IPFlow/<X>/
EndSourceIPaddress
The EndSourceIPaddress leaf indicates the last IP source address of the IP source address range of the IP flow description. The source address refers to the IP address of the data packets destined for the UE according to the terminology in the IETF RFC 6088 [24].
– Occurrence: ZeroOrOne
– Format: chr
– Access Types: Get, Replace
– Values: <an IPv4 address>, <an IPv6 address>.
This leaf can be present only if the leaf ANDSF/ISRP/<X>/ForFlowBased/<X>/IPFlow/<X>/StartSourceIPaddress is present. The absence of this leaf indicates that the IP source address range of the IP flow described by the rule is equal to the address contained in ANDSF/ISRP/<X>/ForFlowBased/<X>/IPFlow/<X>/StartSourceIPaddress. When representing the IP source address range with more than one IP address, the values of this leaf and the corresponding ANDSF/ISRP/<X>/ForFlowBased/<X>/IPFlow/<X>/StartSourceIPaddress leaf are set as defined in subclause 5.7.8.
The value of this leaf is an IPv4 address if the AddressType leaf value of the same rule is equal to IPv4. The value of this leaf is an IPv6 address if the AddressType leaf value of the same rule is equal to IPv6.
The UE ignores an IPFlow instance with a EndSourceIPaddress leaf without a correspondent StartSourceIPaddress leaf. If the IPFlow instance is the only one contained in the flow distribution rule, the UE ignores the flow distribution rule.
5.7.10 Void
5.7.11 Void
5.7.12 ANDSF/ISRP/<X>/ForFlowBased/<X>/IPFlow/<X>/
ProtocolType
The ProtocolType leaf indicates the protocol type in a flow description.
– Occurrence: ZeroOrOne
– Format: int
– Access Types: Get, Replace
– Values: <Protocol type>
The value of ProtocolType leaf is a value among the internet protocol numbers as defined in IANA Assigned Internet Protocol Numbers [18]. In case of IPv4 flow description, the value contained in this leaf is compared with the value of the last protocol type field. In case of IPv6 flow description, the value contained in this leaf is compared with the value of the last next header field. The UE ignores an IPFlow instance with a ProtocolType leaf indicating a protocol type not supported by the UE. If the IPFlow instance is the only one contained in the flow distribution rule, the UE ignores the flow distribution rule.
5.7.13 ANDSF/ISRP/<X>/ForFlowBased/<X>/IPFlow/<X>/ StartSourcePortNumber
The StartSourcePortNumber leaf indicates the first source port number of the source port numbers range of the IP flow description. The source port refers to the source port of the data packets destined for the UE according to the terminology in the IETF RFC 6088 [24].
– Occurrence: ZeroOrOne
– Format: int
– Access Types: Get, Replace
– Values: any value in the range 1-65535.
The absence of this leaf indicates that source port field of the transport protocol header is not examined when matching packets against the IP flow description of the rule.
When applying the rule to uplink traffic, the UE matches the port numbers contained in the range between StartSourcePortNumber and EndSourcePortNumber against destination port field of the uplink traffic packets.
5.7.14 ANDSF/ISRP/<X>/ForFlowBased/<X>/IPFlow/<X>/
EndSourcePortNumber
The EndSourcePortNumber leaf indicates the last source port number of the source port numbers range of the IP flow description. The source port refers to the source port of the data packets destined for the UE according to the terminology in the IETF RFC 6088 [24].
– Occurrence: ZeroOrOne
– Format: int
– Access Types: Get, Replace
– Values: any value in the range 1-65535.
This leaf can be present only if the leaf ANDSF/ISRP/<X>/ForFlowBased/<X>/IPFlow/<X>/StartSourcePortNumber is present. The absence of this leaf indicates that the source port number range of the IP flow described by the rule is equal to the source port number contained in ANDSF/ISRP/<X>/ForFlowBased/<X>/IPFlow/<X>/StartSourcePortNumber.
The UE ignores an IPFlow instance with a EndSourcePortNumber leaf without a correspondent StartSourcePortNumber leaf. If the IPFlow instance is the only one contained in the flow distribution rule, the UE ignores the flow distribution rule.
5.7.15 ANDSF/ISRP/<X>/ForFlowBased/<X>/IPFlow/<X>/
StartDestPortNumber
The StartDestPortNumber leaf indicates the first destination port number of the destination port numbers range of the IP flow description. The destination port refers to the destination port of the data packets sent by the corresponding node according to the terminology in the IETF RFC 6088 [24].
– Occurrence: ZeroOrOne
– Format: int
– Access Types: Get, Replace
– Values: any value in the range 1-65535.
The absence of this leaf indicates that destination port field of the transport protocol header is not examined when matching packets against the IP flow description of the rule.
When applying the rule to uplink traffic, the UE matches the port numbers contained in the range between StartDestPortNumber and EndDestPortNumber against source port field of the uplink traffic packets.
5.7.16 ANDSF/ISRP/<X>/ForFlowBased/<X>/IPFlow/<X>/
EndDestPortNumber
The EndDestPortNumber leaf indicates the last destination port number of the destination port numbers range of the IP flow description. The destination port refers to the destination port of the data packets sent by the corresponding node according to the terminology in the IETF RFC 6088 [24].
– Occurrence: ZeroOrOne
– Format: int
– Access Types: Get, Replace
– Values: any value in the range 1-65535.
This leaf can be present only if the leaf ANDSF/ISRP/<X>/ForFlowBased/<X>/IPFlow/<X>/StartDestPortNumber is present. The absence of this leaf indicates that the destination port number range of the IP flow described by the rule is equal to the port number contained in ANDSF/ISRP/<X>/ForFlowBased/<X>/IPFlow/<X>/StartDestPortNumber.
The UE ignores an IPFlow instance with a EndDestPortNumber leaf without a correspondent StartDestPortNumber leaf. If the IPFlow instance is the only one contained in the flow distribution rule, the UE ignores the flow distribution rule.
5.7.17 ANDSF/ISRP/<X>/ForFlowBased/<X>/IPFlow/<X>/QoS
The QoS leaf indicates the DS or ToS values parameters in a flow description.
– Occurrence: ZeroOrOne
– Format: bin
– Access Types: Get, Replace
– Values: any value in the range 0-63 expressed in a binary form
The DS and ToS values are defined in IETF RFC 3260 [10A].
5.7.17A ANDSF/ISRP/<X>/ForFlowBased/<X>/IPFlow/<X>/DomainName
The DomainName leaf indicates the destination domain name of the IP Flow description.
– Occurrence: ZeroOrOne
– Format: chr
– Access Types: Get, Replace
– Values: <FQDN>
The value of FQDN is Fully Qualified Domain Name (e.g. www.example.com) that was resolved into the destination IP address. The FQDN format is defined in 3GPP TS 23.003 [3].
The absence of this leaf indicates that the domain name is not examined when matching packets against the IP flow description of the rule.
5.7.17B ANDSF/ISRP/<X>/ForFlowBased/<X>/IPFlow/<X>/APN
The APN leaf indicates the APN of the IP flow description.
– Occurrence: ZeroOrOne
– Format: chr
– Access Types: Get, Replace
– Values: <APN>
The APN format is defined in 3GPP TS 23.003 [3].
If the traffic is for an APN matching the value of this leaf, then this leaf is evaluated as matching.
5.7.18 ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria
The RoutingCriteria node acts as a placeholder for validity conditions for a particular flow distribution rule.
– Occurrence: ZeroOrOne
– Format: node
– Access Types: Get, Replace
– Values: N/A
If at least one instance of ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X> node indicates matching validity condition, the UE shall consider the corresponding flow distribution rule as valid.
If the ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X> node is present and empty (i.e. none of the nodes ValidityArea, ValidityAreaRef, TimeOfDay, TimeOfDayRef, RANValidityCondition or RANValidityConditionRef exist), the ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X> node is not considered when evaluating the validity of the corresponding flow distribution rule.
5.7.19 ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/
This internal node acts as a placeholder for one or more validity conditions for a particular flow distribution rule.
– Occurrence: OneOrMore
– Format: node
– Access Types: Get, Replace
– Values: N/A
The UE shall consider the corresponding flow distribution rule as valid only if all the present interior nodes (ValidityArea, ValidityAreaRef, TimeOfDay, TimeOfDayRef, RANValidityCondition or RANValidityConditionRef) within a single instance of ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X> node indicate matching validity condition.
5.7.20 ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/
ValidityArea
The ValidityArea node acts as a placeholder for location conditions for a particular flow distribution rule.
– Occurrence: ZeroOrOne
– Format: node
– Access Types: Get, Replace
– Values: N/A
This node and its descendants are the same as defined in ANDSF/Policy/<X>/ValidityArea.
5.7.20A ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/
ValidityAreaRef
The ValidityAreaRef leaf contains a reference to a ValidityArea interior node.
– Occurrence: ZeroOrOne
– Format: chr
– Access Types: Get, Replace
– Values: < a reference to a ValidityArea interior node >
This node is the same as defined in ANDSF/Policy/<X>/ValidityAreaRef.
5.7.21 ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/
TimeOfDay
The TimeOfDay node acts as a placeholder for day condition for a particular flow distribution rule.
– Occurrence: ZeroOrOne
– Format: node
– Access Types: Get, Replace
– Values: N/A
This node and its descendants are the same as defined in <X>/Policy/<X>/TimeOfDay.
5.7.21A ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/
TimeOfDayRef
The TimeOfDayRef leaf contains a reference to a TimeOfDay interior node.
– Occurrence: ZeroOrOne
– Format: chr
– Access Types: Get, Replace
– Values: < a reference to a TimeOfDay interior node >
This node is the same as defined in <X>/Policy/<X>/TimeOfDayRef.
5.7.21B1 ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/
RANValidityCondition
The RANValidityCondition node acts as a placeholder for RAN validity condition for a particular flow distribution rule.
– Occurrence: ZeroOrOne
– Format: node
– Access Types: Get, Replace
– Values: N/A
When evaluating the RANValidityCondition node, the following applies:
– if both the OPI node and ThresholdCondition node are evaluated to be matching, the UE shall consider this RANValidCondition node as matching;
– if the rule is provided by the H-ANDSF, and the UE is roaming in the VPLMN, the UE shall consider this RANValidCondition node as matching;
– otherwise the UE shall consider this RANValidCondition node as not matching.
5.7.21B2 ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/
RANValidityCondition/ThresholdConditions
The ThresholdCondition interior node acts as a placeholder for information related to 3GPP and WLAN thresholds condition evaluation.
– Occurrence: One
– Format: node
– Access Types: Get, Replace
– Values: N/A
The ThresholdCondition shall be evaluated as follows:
– if ThresholdConditionEvalutionPolicy child leaf of this node is 0:
– if any one of the nodes included in Thresholds node is evaluated to be matching, the UE shall consider this node as matching;
– otherwise, the UE shall consider this node as not matching; and
– if ThresholdConditionEvalutionPolicy child leaf of this node is 1:
– if all the nodes included in Thresholds node are evaluated to be matching, the UE shall consider this node as matching;
– otherwise, the UE shall consider this node as not matching.
5.7.21B3 ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/
RANValidityCondition/ThresholdConditions/Thresholds
The Thresholds interior node acts as a placeholder for all 3GPP access thresholds and WLAN access thresholds.
– Occurrence: One
– Format: node
– Access Types: Get, Replace
– Values: N/A
The following 3GPP or WLAN access thresholds can be included in the Thresholds node:
1) 3GPP access thresholds:ThreshServingOffloadWLANLowP, ThreshServingOffloadWLANHighP, ThreshServingOffloadWLANLowQ, ThreshServingOffloadWLANHighQ;
2) WLAN access thresholds:ThreshChUtilWLANLow, ThreshChUtilWLANHigh, ThreshBackhRateDLWLANLow, ThreshBackhRateDLWLANHigh, ThreshBackhRateULWLANLow, ThreshBackhRateULWLANHigh, ThreshBeaconRSSIWLANLow, ThreshBeaconRSSIWLANHigh.
NOTE: If the operator wishes to ensure that ANDSF rules provide consistent traffic steering behaviour as the RAN rules, it is advised to have the threshold conditions in ANDSF policy evaluated in the same way as the threshold conditions in the RAN rules.
5.7.21B4 ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/
RANValidityCondition/ThresholdConditions/Thresholds/ThreshServingOffloadWLANLowP
The ThreshServingOffloadWLANLowP leaf node acts as a placeholder indicating that low threshold value of RSRP threshold (for E-UTRAN) / CPICH RSCP threshold (for UTRAN FDD) / P-CCPCH threshold (for UTRAN TDD) provided by E-UTRAN/UTRAN is to be taken into account when evaluating validity of the rule and is used by the UE for traffic steering to WLAN.
– Occurrence: ZeroOrOne
– Format: Null
– Access Types: Get, Replace
– Values: N/A
The ThreshServingOffloadWLANLowP threshold condition shall be evaluated as follows:
– if ThreshServingOffloadWLANLowP leaf is present and ThreshServingOffloadWLANLowP threshold value has not been received from E-UTRAN/UTRAN, the UE shall consider this node as not matching;
– otherwise if ThreshServingOffloadWLANLowP leaf is present and ThreshServingOffloadWLANLowP threshold value has been received from E-UTRAN/UTRAN;
– if the measurement value Qrxlevmeas is smaller than ThreshServingOffloadWLANLowP threshold value, the UE shall consider this node as matching; otherwise the UE shall consider this node as not matching.
5.7.21B5 ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/
RANValidityCondition/ThresholdConditions/Thresholds/ThreshServingOffloadWLANHighP
The ThreshServingOffloadWLANHighP leaf node acts as a placeholder indicating that high threshold value of RSRP threshold (for E-UTRAN) / CPICH RSCP threshold (for UTRAN FDD) / P-CCPCH threshold (for UTRAN TDD) provided by E-UTRAN/UTRAN is to be taken into account when evaluating validity of the rule and is used by the UE for traffic steering to E-UTRAN/UTRAN.
– Occurrence: ZeroOrOne
– Format: Null
– Access Types: Get, Replace
– Values: N/A
The ThreshServingOffloadWLANHighP threshold condition shall be evaluated as follows:
– if ThreshServingOffloadWLANHighP leaf is present and ThreshServingOffloadWLANHighP threshold value has not been received from E-UTRAN/UTRAN, the UE shall consider this node as not matching;
– otherwise if ThreshServingOffloadWLANHighP leaf is present and ThreshServingOffloadWLANHighP threshold value has been received from E-UTRAN/UTRAN;
– if the measurement value Qrxlevmeas is greater than ThreshServingOffloadWLANHighP threshold value, the UE shall consider this node as matching; otherwise the UE shall consider this node as not matching.
5.7.21B6 ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/
RANValidityCondition/ThresholdConditions/Thresholds/ThreshServingOffloadWLANLowQ
The ThreshServingOffloadWLANLowQ leaf node acts as a placeholder indicating that low threshold value of RSRQ threshold (for E-UTRAN) / CPICH EC/N0 threshold (for UTRAN FDD) provided by E-UTRAN/UTRAN is to be taken into account when evaluating validity of the rule and is used by the UE for traffic steering to WLAN.
– Occurrence: ZeroOrOne
– Format: Null
– Access Types: Get, Replace
– Values: N/A
The ThreshServingOffloadWLANLowQ threshold condition shall be evaluated as follows:
– if ThreshServingOffloadWLANLowQ leaf is present and ThreshServingOffloadWLANLowQ threshold value has not been received from E-UTRAN/UTRAN, the UE shall consider this node as not matching;
– otherwise if ThreshServingOffloadWLANLowQ leaf is present and ThreshServingOffloadWLANLowQ threshold value has been received from E-UTRAN/UTRAN;
– if the measurement value Qqualmeas is smaller than ThreshServingOffloadWLANLowQ threshold value, the UE shall consider this node as matching; otherwise the UE shall consider this node as not matching.
5.7.21B7 ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/
RANValidityCondition/ThresholdConditions/Thresholds/ThreshServingOffloadWLANHighQ
The ThreshServingOffloadWLANHighQ leaf node acts as a placeholder indicating that high threshold value of RSRQ threshold (for E-UTRAN) / CPICH EC/N0 threshold (for UTRAN FDD) provided by E-UTRAN/UTRAN is to be taken into account when evaluating validity of the rule and is used by the UE for traffic steering to E-UTRAN/UTRAN.
– Occurrence: ZeroOrOne
– Format: Null
– Access Types: Get, Replace
– Values: N/A
The ThreshServingOffloadWLANHighQ threshold condition shall be evaluated as follows:
– if ThreshServingOffloadWLANHighQ leaf is present and ThreshServingOffloadWLANHighQ threshold value has not been received from E-UTRAN/UTRAN, the UE shall consider this node as not matching;
– otherwise if ThreshServingOffloadWLANHighQ leaf is present and ThreshServingOffloadWLANHighQ threshold value has been received from E-UTRAN/UTRAN;
– if the measurement value Qqualmeas is greater than ThreshServingOffloadWLANHighQ threshold value, the UE shall consider this node as matching; otherwise the UE shall consider this node as not matching.
5.7.21B8 ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/
RANValidityCondition/ThresholdConditions/Thresholds/ThreshChUtilWLANLow
The ThreshChUtilWLANLow node leaf acts as a placeholder for low threshold value of WLAN channel utilization (BSS load) threshold provisioned by ANDSF and/or by RAN.
– Occurrence: ZeroOrOne
– Format: node
– Access Types: Get, Replace
– Values: N/A
The ThreshChUtilWLANLow threshold condition shall be evaluated as follows:
– if the ThreshChUtilWLANLowRAN node is present and ThreshChUtilWLANLowANDSF node is not present and the ThreshChUtilWLANLowRAN node is evaluated to be matching, the UE shall consider this node as matching;
– if the ThreshChUtilWLANLowANDSF node is present and ThreshChUtilWLANLowRAN node is not present and the ThreshChUtilWLANLowANDSF node is evaluated to be matching, the UE shall consider this node as matching;
– if both the ThreshChUtilWLANLowANDSF node and ThreshChUtilWLANLowRAN node are present ThreshChUtilWLANLowRAN node will take precedence over ThreshChUtilWLANLowANDSF node, i.e. the ThreshChUtilWLANLowRAN node is evaluated to be matching, the UE shall consider this node as matching. Otherwise, if the RAN threshold value has not been received from E-UTRAN/UTRAN and the ThreshChUtilWLANLowANDSF node is evaluated to be matching, the UE shall consider this node as matching;
– if this node is empty, the UE shall consider this node as matching; and
– otherwise the UE shall consider this node as not matching.
5.7.21B9 ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/
RANValidityCondition/ThresholdConditions/Thresholds/ThreshChUtilWLANLow/ThreshChUtilWLANLowANDSF
The ThreshChUtilWLANLowANDSF leaf node acts as a placeholder for low threshold value of WLAN channel utilization (BSS load) threshold obtained from 802.11 (Beacon or Probe Response) signalling. It is provisioned by ANDSF and used by the UE for traffic steering to WLAN.
– Occurrence: ZeroOrOne
– Format: int
– Access Types: Get, Replace
– Values: <ThreshChUtilWLANLowANDSF>
The ThreshChUtilWLANLowANDSF threshold condition shall be evaluated as follows:
– if the measurement value ChannelUtilizationWLAN obtained in the 802.11 (Beacon or Probe Response) signalling is smaller than value contained in this leaf, the UE shall consider this node as matching; otherwise the UE shall consider this node as not matching.
5.7.21B10 ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/
RANValidityCondition/ThresholdConditions/Thresholds/ThreshChUtilWLANLow/ThreshChUtilWLANLowRAN
The ThreshChUtilWLANLowRAN leaf node acts as a placeholder indicating that low threshold value of WLAN channel utilization (BSS load) threshold provided by E-UTRAN/UTRAN is to be taken into account when evaluating validity of the rule and is used by the UE for traffic steering to WLAN.
– Occurrence: ZeroOrOne
– Format: Null
– Access Types: Get, Replace
– Values: N/A
The ThreshChUtilWLANLowRAN threshold condition shall be evaluated as follows:
– if ThreshChUtilWLANLowRAN leaf is present and ThreshChUtilWLANLow threshold value has not been received from E-UTRAN/UTRAN, the UE shall consider this node as not matching;
– otherwise if ThreshChUtilWLANLowRAN leaf is present and ThreshChUtilWLANLow threshold value has been received from E-UTRAN/UTRAN;
– if the measurement value ChannelUtilizationWLAN is smaller than ThreshChUtilWLANLow threshold value, the UE shall consider this node as matching; otherwise the UE shall consider this node as not matching.
5.7.21B11 ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/
RANValidityCondition/ThresholdConditions/Thresholds/ThreshChUtilWLANHigh
The ThreshChUtilWLANHigh node leaf acts as a placeholder for high threshold value of WLAN channel utilization (BSS load) threshold provisioned by ANDSF and/or by RAN.
– Occurrence: ZeroOrOne
– Format: node
– Access Types: Get, Replace
– Values: N/A
The ThreshChUtilWLANHigh threshold condition shall be evaluated as follows:
– if the ThreshChUtilWLANHighRAN node is present and ThreshChUtilWLANHighANDSF node is not present and the ThreshChUtilWLANHighRAN node is evaluated to be matching, the UE shall consider this node as matching;
– if the ThreshChUtilWLANHighANDSF node is present and ThreshChUtilWLANHighRAN node is not present and the ThreshChUtilWLANHighANDSF node is evaluated to be matching, the UE shall consider this node as matching;
– if both the ThreshChUtilWLANHighANDSF node and ThreshChUtilWLANHighRAN node are present, ThreshChUtilWLANHighRAN node will take precedence over ThreshChUtilWLANHighANDSF node, i.e. the ThreshChUtilWLANHighRAN node is evaluated to be matching, the UE shall consider this node as matching. Otherwise, if the RAN threshold value has not been received from E-UTRAN/UTRAN and the ThreshChUtilWLANHighANDSF node is evaluated to be matching, the UE shall consider this node as matching;
– if this node is empty, the UE shall consider this node as matching; and
– otherwise the UE shall consider this node as not matching.
5.7.21B12 ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/
RANValidityCondition/ThresholdConditions/Thresholds/ThreshChUtilWLANHigh/ThreshChUtilWLANHighANDSF
The ThreshChUtilWLANHighANDSF leaf node acts as a placeholder for high threshold value of WLAN channel utilization (BSS load) threshold obtained from 802.11 (Beacon or Probe Response) signalling. It is provisioned by ANDSF and used by the UE for traffic steering to E-UTRAN/UTRAN.
– Occurrence: ZeroOrOne
– Format: int
– Access Types: Get, Replace
– Values: <ThreshChUtilWLANHighANDSF>
The ThreshChUtilWLANHighANDSF threshold condition shall be evaluated as follows:
– if the measurement value ChannelUtilizationWLAN obtained in the 802.11 (Beacon or Probe Response) signalling is greater than value contained in this leaf, the UE shall consider this node as matching; otherwise the UE shall consider this node as not matching.
5.7.21B13 ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/
RANValidityCondition/ThresholdConditions/Thresholds/ThreshChUtilWLANHigh/ThreshChUtilWLANHighRAN
The ThreshChUtilWLANHighRAN leaf node acts as a placeholder indicating that high threshold value of WLAN channel utilization (BSS load) threshold provided by E-UTRAN/UTRAN is to be taken into account when evaluating validity of the rule and is used by the UE for traffic steering to E-UTRAN/UTRAN.
– Occurrence: ZeroOrOne
– Format: Null
– Access Types: Get, Replace
– Values: N/A
The ThreshChUtilWLANHighRAN threshold condition shall be evaluated as follows:
– if ThreshChUtilWLANHighRAN leaf is present and ThreshChUtilWLANHigh threshold value has not been received from E-UTRAN/UTRAN, the UE shall consider this node as not matching;
– otherwise if ThreshChUtilWLANHighRAN leaf is present and ThreshChUtilWLANHigh threshold value has been received from E-UTRAN/UTRAN;
– if the measurement value ChannelUtilizationWLAN is greater than ThreshChUtilWLANHigh threshold value, the UE shall consider this node as matching; otherwise the UE shall consider this node as not matching.
5.7.21B14 ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/
RANValidityCondition/ThresholdConditions/Thresholds/ThreshBackhRateDLWLANLow
The ThreshBackhRateDLWLANLow node leaf acts as a placeholder for low threshold value of backhaul available downlink bandwidth thresholds provisioned by ANDSF and/or by RAN.
– Occurrence: ZeroOrOne
– Format: node
– Access Types: Get, Replace
– Values: N/A
The ThreshBackhRateDLWLANLow threshold condition shall be evaluated as follows:
– if the ThreshBackhRateDLWLANLowRAN node is present and ThreshBackhRateDLWLANLowANDSF node is not present and the ThreshBackhRateDLWLANLowRAN node is evaluated to be matching, the UE shall consider this node as matching;
– if the ThreshBackhRateDLWLANLowANDSF node is present and ThreshBackhRateDLWLANLowRAN node is not present and the ThreshBackhRateDLWLANLowANDSF node is evaluated to be matching, the UE shall consider this node as matching;
– if both the ThreshBackhRateDLWLANLowANDSF node and ThreshBackhRateDLWLANLowRAN node are present, ThreshBackhRateDLWLANLowRAN node will take precedence over ThreshBackhRateDLWLANLowANDSF node, i.e. the ThreshBackhRateDLWLANLowRAN node is evaluated to be matching, the UE shall consider this node as matching. Otherwise, if the RAN threshold value has not been received from E-UTRAN/UTRAN and the ThreshBackhRateDLWLANLowANDSF node is evaluated to be matching, the UE shall consider this node as matching;
– if this node is empty, the UE shall consider this node as matching; and
– otherwise the UE shall consider this node as not matching.
5.7.21B15 ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/
RANValidityCondition/ThresholdConditions/Thresholds/ThreshBackhRateDLWLANLow/ThreshBackhRateDLWLANLowANDSF
The ThreshBackhRateDLWLANLowANDSF leaf node acts as a placeholder for low threshold value of backhaul available downlink bandwidth threshold provided by E-UTRAN/UTRAN and is used by the UE for traffic steering to E-UTRAN/UTRAN.
– Occurrence: ZeroOrOne
– Format: int
– Access Types: Get, Replace
– Values: <ThreshBackhRateDLWLANLowANDSF>
The ThreshBackhRateDLWLANLow threshold condition shall be evaluated as follows:
– if the measurement value BackhaulRateDlWLAN derived from Downlink Speed and Downlink Load measurement results is smaller than value contained in this leaf, the UE shall consider this node as matching; otherwise the UE shall consider this node as not matching.
NOTE: BackhaulRateDlWLAN is calculated as the Downlink Speed * (1 – Downlink Load/255), where the downlink speed and load parameters are drawn from the WAN Metrics element obtained via ANQP signalling from WFA HS 2.0.
5.7.21B16 ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/
RANValidityCondition/ThresholdConditions/Thresholds/ThreshBackhRateDLWLANLow/ThreshBackhRateDLWLANLowRAN
The ThreshBackhRateDLWLANLowRAN leaf node acts as a placeholder indicating that low threshold value of backhaul available downlink bandwidth threshold provided by E-UTRAN/UTRAN is to be taken into account when evaluating validity of the rule and is used by the UE for traffic steering to E-UTRAN/UTRAN.
– Occurrence: ZeroOrOne
– Format: Null
– Access Types: Get, Replace
– Values: N/A
The ThreshBackhRateDLWLANLowRAN threshold condition shall be evaluated as follows:
– if ThreshBackhRateDLWLANLowRAN leaf is present and ThreshBackhRateDLWLANLow threshold value has not been received from E-UTRAN/UTRAN, the UE shall consider this node as not matching;
– otherwise if ThreshBackhRateDLWLANLowRAN leaf is present and ThreshBackhRateDLWLANLow threshold value has been received from E-UTRAN/UTRAN;
– if the value BackhaulRateDlWLAN derived from Downlink Speed and Downlink Load measurement results is smaller than ThreshBackhRateDLWLANLow threshold value, the UE shall consider this node as matching; otherwise the UE shall consider this node as not matching.
NOTE: BackhaulRateDlWLAN is calculated as the Downlink Speed * (1 – Downlink Load/255), where the downlink speed and load parameters are drawn from the WAN Metrics element obtained via ANQP signalling from WFA HS 2.0.
5.7.21B17 ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/
RANValidityCondition/ThresholdConditions/Thresholds/ThreshBackhRateDLWLANHigh
The ThreshBackhRateDLWLANHigh node leaf acts as a placeholder for high threshold value of backhaul available downlink bandwidth thresholds provisioned by ANDSF and/or by RAN.
– Occurrence: ZeroOrOne
– Format: node
– Access Types: Get, Replace
– Values: N/A
The ThreshBackhRateDLWLANHigh threshold condition shall be evaluated as follows:
– if the ThreshBackhRateDLWLANHighRAN node is present and ThreshBackhRateDLWLANHighANDSF node is not present and the ThreshBackhRateDLWLANHighRAN node is evaluated to be matching, the UE shall consider this node as matching;
– if the ThreshBackhRateDLWLANHighANDSF node is present and ThreshBackhRateDLWLANHighRAN node is not present and the ThreshBackhRateDLWLANHighANDSF node is evaluated to be matching, the UE shall consider this node as matching;
– if both the ThreshBackhRateDLWLANHighANDSF node and ThreshBackhRateDLWLANHighRAN node are present ThreshBackhRateDLWLANHighRAN node will take precedence over ThreshBackhRateDLWLANHighANDSF node, i.e. the ThreshBackhRateDLWLANHighRAN node is evaluated to be matching, the UE shall consider this node as matching. Otherwise, if the RAN threshold value has not been received from E-UTRAN/UTRAN and the ThreshBackhRateDLWLANHighANDSF node is evaluated to be matching, the UE shall consider this node as matching;
– if this node is empty, the UE shall consider this node as matching; and
– otherwise the UE shall consider this node as not matching.
5.7.21B18 ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/
RANValidityCondition/ThresholdConditions/Thresholds/ThreshBackhRateDLWLANHigh/ThreshBackhRateDLWLANHighANDSF
The ThreshBackhRateDLWLANHighANDSF leaf node acts as a placeholder for high threshold value of backhaul available downlink bandwidth threshold provided by E-UTRAN/UTRAN and is used by the UE for traffic steering to WLAN.
– Occurrence: ZeroOrOne
– Format: int
– Access Types: Get, Replace
– Values: <ThreshBackhRateDLWLANHigh>
The ThreshBackhRateDLWLANHighANDSF threshold condition shall be evaluated as follows:
– if the measurement value BackhaulRateDlWLAN derived from Downlink Speed and Downlink Load measurement results is greater than value contained in this leaf, the UE shall consider this node as matching; otherwise the UE shall consider this node as not matching.
NOTE: BackhaulRateDlWLAN is calculated as the Downlink Speed * (1 – Downlink Load/255), where the downlink speed and load parameters are drawn from the WAN Metrics element obtained via ANQP signalling from WFA HS 2.0.
5.7.21B19 ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/
RANValidityCondition/ThresholdConditions/Thresholds/ThreshBackhRateDLWLANHigh/ThreshBackhRateDLWLANHighRAN
The ThreshBackhRateDLWLANHighRAN leaf node acts as a placeholder indicating that high threshold value of backhaul available downlink bandwidth threshold provided by E-UTRAN/UTRAN is to be taken into account when evaluating validity of the rule and is used by the UE for traffic steering to WLAN.
– Occurrence: ZeroOrOne
– Format: Null
– Access Types: Get, Replace
– Values: N/A
The ThreshBackhRateDLWLANHighRAN threshold condition shall be evaluated as follows:
– if ThreshBackhRateDLWLANHighRAN leaf is present and ThreshBackhRateDLWLANHigh threshold value has not been received from E-UTRAN/UTRAN, the UE shall consider this node as not matching;
– otherwise if ThreshBackhRateDLWLANHighRAN leaf is present and ThreshBackhRateDLWLANHigh threshold value has been received from E-UTRAN/UTRAN;
– if the value BackhaulRateDlWLAN derived from Downlink Speed and Downlink Load measurement results is greater than ThreshBackhRateDLWLANHigh threshold value, the UE shall consider this node as matching; otherwise the UE shall consider this node as not matching.
NOTE: BackhaulRateDlWLAN is calculated as the Downlink Speed * (1 – Downlink Load/255), where the downlink speed and load parameters are drawn from the WAN Metrics element obtained via ANQP signalling from WFA HS 2.0.
5.7.21B20 ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/
RANValidityCondition/ThresholdConditions/Thresholds/ThreshBackhRateULWLANLow
The ThreshBackhRateULWLANLow node leaf acts as a placeholder for low threshold value of backhaul available uplink bandwidth thresholds provisioned by ANDSF and/or by RAN.
– Occurrence: ZeroOrOne
– Format: node
– Access Types: Get, Replace
– Values: N/A
The ThreshBackhRateULWLANLow threshold condition shall be evaluated as follows:
– if the ThreshBackhRateULWLANLowRAN node is present and ThreshBackhRateULWLANLowANDSF node is not present and the ThreshBackhRateULWLANLowRAN node is evaluated to be matching, the UE shall consider this node as matching;
– if the ThreshBackhRateULWLANLowANDSF node is present and ThreshBackhRateULWLANLowRAN node is not present and the ThreshBackhRateULWLANLowANDSF node is evaluated to be matching, the UE shall consider this node as matching;
– if both the ThreshBackhRateULWLANLowANDSF node and ThreshBackhRateULWLANLowRAN node are present, ThreshBackhRateULWLANLowRAN node will take precedence over ThreshBackhRateULWLANLowANDSF node, i.e. the ThreshBackhRateULWLANLowRAN node is evaluated to be matching, the UE shall consider this node as matching. Otherwise, if the RAN threshold value has not been received from E-UTRAN/UTRAN and the ThreshBackhRateULWLANLowANDSF node is evaluated to be matching, the UE shall consider this node as matching;
– if this node is empty, the UE shall consider this node as matching; and
– otherwise the UE shall consider this node as not matching.
5.7.21B21 ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/
RANValidityCondition/ThresholdConditions/Thresholds/ThreshBackhRateULWLANLow/ThreshBackhRateULWLANLowANDSF
The ThreshBackhRateULWLANLowANDSF leaf node acts as a placeholder for low threshold value of backhaul available uplink bandwidth threshold provided by E-UTRAN/UTRAN and is used by the UE for traffic steering to E-UTRAN/UTRAN.
– Occurrence: ZeroOrOne
– Format: int
– Access Types: Get, Replace
– Values: <ThreshBackhRateULWLANLowANDSF>
The ThreshBackhRateULWLANLowANDSF threshold condition shall be evaluated as follows:
– if the measurement value BackhaulRateUlWLAN derived from Uplink Speed and Uplink Load measurement results is smaller than value contained in this leaf, the UE shall consider this node as matching; otherwise the UE shall consider this node as not matching.
NOTE: BackhaulRateUlWLAN is calculated as the Uplink Speed * (1 – Uplink Load / 255), where the uplink speed and load parameters are drawn from the WAN Metrics element obtained via ANQP signalling from WFA HS 2.0.
5.7.21B22 ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/
RANValidityCondition/ThresholdConditions/Thresholds/ThreshBackhRateULWLANLow/ThreshBackhRateULWLANLowRAN
The ThreshBackhRateULWLANLowRAN leaf node acts as a placeholder indicating that low threshold value of backhaul available uplink bandwidth threshold provided by E-UTRAN/UTRAN is to be taken into account when evaluating validity of the rule and is used by the UE for traffic steering to E-UTRAN/UTRAN.
– Occurrence: ZeroOrOne
– Format: Null
– Access Types: Get, Replace
– Values: N/A
The ThreshBackhRateULWLANLowRAN threshold condition shall be evaluated as follows:
– if ThreshBackhRateULWLANLowRAN leaf is present and ThreshBackhRateULWLANLow threshold value has not been received from E-UTRAN/UTRAN, the UE shall consider this node as not matching;
– otherwise if ThreshBackhRateULWLANLowRAN leaf is present and ThreshBackhRateULWLANLow threshold value has been received from E-UTRAN/UTRAN;
– if the value BackhaulRateUlWLAN derived from Uplink Speed and Uplink Load measurement results is smaller than ThreshBackhRateULWLANLow threshold value, the UE shall consider this node as matching; otherwise the UE shall consider this node as not matching.
NOTE: BackhaulRateUlWLAN is calculated as the Uplink Speed * (1 – Uplink Load / 255), where the uplink speed and load parameters are drawn from the WAN Metrics element obtained via ANQP signalling from WFA HS 2.0.
5.7.21B23 ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/
RANValidityCondition/ThresholdConditions/Thresholds/ThreshBackhRateULWLANHigh
The ThreshBackhRateULWLANHigh node leaf acts as a placeholder for high threshold value of backhaul available uplink bandwidth thresholds provisioned by ANDSF and/or by RAN.
– Occurrence: ZeroOrOne
– Format: node
– Access Types: Get, Replace
– Values: N/A
The ThreshBackhRateULWLANHigh threshold condition shall be evaluated as follows:
– if the ThreshBackhRateULWLANHighRAN node is present and ThreshBackhRateULWLANHighANDSF node is not present and the ThreshBackhRateULWLANHighRAN node is evaluated to be matching, the UE shall consider this node as matching;
– if the ThreshBackhRateULWLANHighANDSF node is present and ThreshBackhRateULWLANHighRAN node is not present and the ThreshBackhRateULWLANHighANDSF node is evaluated to be matching, the UE shall consider this node as matching;
– if both the ThreshBackhRateULWLANHighANDSF node and ThreshBackhRateULWLANHighRAN node are present, ThreshBackhRateULWLANHighRAN node will take precedence over ThreshBackhRateULWLANHighANDSF node, i.e. the ThreshBackhRateULWLANHighRAN node is evaluated to be matching, the UE shall consider this node as matching. Otherwise, if the RAN threshold value has not been received from E-UTRAN/UTRAN and the ThreshBackhRateULWLANHighANDSF node is evaluated to be matching, the UE shall consider this node as matching;
– if this node is empty, the UE shall consider this node as matching; and
– otherwise the UE shall consider this node as not matching.
5.7.21B24 ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/
RANValidityCondition/ThresholdConditions/Thresholds/ThreshBackhRateULWLANHigh/ThreshBackhRateULWLANHighANDSF
The ThreshBackhRateULWLANHighANDSF leaf node acts as a placeholder for high threshold value of backhaul available uplink bandwidth threshold provisioned by ANDSF and is used by the UE for traffic steering to WLAN.
– Occurrence: ZeroOrOne
– Format: int
– Access Types: Get, Replace
– Values: <ThreshBackhRateULWLANHighANDSF>
The ThreshBackhRateULWLANHigh thresholdANDSF condition shall be evaluated as follows:
– if the measurement value BackhaulRateUlWLAN derived from Uplink Speed and Uplink Load measurement results is greater than value contained in this leaf, the UE shall consider this node as matching; otherwise the UE shall consider this node as not matching.
NOTE: BackhaulRateUlWLAN is calculated as the Uplink Speed * (1 – Uplink Load / 255), where the uplink speed and load parameters are drawn from the WAN Metrics element obtained via ANQP signalling from WFA HS 2.0.
5.7.21B25 ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/
RANValidityCondition/ThresholdConditions/Thresholds/ThreshBackhRateULWLANHigh/ThreshBackhRateULWLANHighRAN
The ThreshBackhRateULWLANHighRAN leaf node acts as a placeholder indicating that high threshold value of backhaul available uplink bandwidth threshold provided by E-UTRAN/UTRAN is to be taken into account when evaluating validity of the rule and is used by the UE for traffic steering to WLAN.
– Occurrence: ZeroOrOne
– Format: Null
– Access Types: Get, Replace
– Values: N/A
The ThreshBackhRateULWLANHighRAN threshold condition shall be evaluated as follows:
– if ThreshBackhRateULWLANHighRAN leaf is present and ThreshBackhRateULWLANHigh threshold value has not been received from E-UTRAN/UTRAN, the UE shall consider this node as not matching;
– otherwise if ThreshBackhRateULWLANHighRAN leaf is present and ThreshBackhRateULWLANHigh threshold value has been received from E-UTRAN/UTRAN;
– if the value BackhaulRateUlWLAN derived from Uplink Speed and Uplink Load measurement results is greater than ThreshBackhRateULWLANHigh threshold value, the UE shall consider this node as matching; otherwise the UE shall consider this node as not matching.
NOTE: BackhaulRateUlWLAN is calculated as the Uplink Speed * (1 – Uplink Load / 255), where the uplink speed and load parameters are drawn from the WAN Metrics element obtained via ANQP signalling from WFA HS 2.0.
5.7.21B26 ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/
RANValidityCondition/ThresholdConditions/Thresholds/ThreshBeaconRSSIWLANLow
The ThreshBeaconRSSIWLANLow node leaf acts as a placeholder for low threshold value of beacon RSSI thresholds provisioned by ANDSF and/or by RAN.
– Occurrence: ZeroOrOne
– Format: node
– Access Types: Get, Replace
– Values: N/A
The ThreshBeaconRSSIWLANLow threshold condition shall be evaluated as follows:
– if the ThreshBeaconRSSIWLANLowRAN node is present and ThreshBeaconRSSIWLANLowANDSF node is not present and the ThreshBeaconRSSIWLANLowRAN node is evaluated to be matching, the UE shall consider this node as matching;
– if the ThreshBeaconRSSIWLANLowANDSF node is present and ThreshBeaconRSSIWLANLowRAN node is not present and the ThreshBeaconRSSIWLANLowANDSF node is evaluated to be matching, the UE shall consider this node as matching;
– if both the ThreshBeaconRSSIWLANLowANDSF node and ThreshBeaconRSSIWLANLowRAN node are present ThreshBeaconRSSIWLANLowRAN node will take precedence over ThreshBeaconRSSIWLANLowANDSF node, i.e. the ThreshBeaconRSSIWLANLowRAN node is evaluated to be matching, the UE shall consider this node as matching. Otherwise, if the RAN threshold value has not been received from E-UTRAN/UTRAN and the ThreshBeaconRSSIWLANLowANDSF node is evaluated to be matching, the UE shall consider this node as matching;
– if this node is empty, the UE shall consider this node as matching; and
– otherwise the UE shall consider this node as not matching.
5.7.21B27 ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/
RANValidityCondition/ThresholdConditions/Thresholds/ThreshBeaconRSSIWLANLow/ThreshBeaconRSSIWLANLowANDSF
The ThreshBeaconRSSIWLANLowANDSF leaf node acts as a placeholder for low threshold value of beacon RSSI threshold provided by E-UTRAN/UTRAN and is used by the UE for traffic steering to E-UTRAN/UTRAN.
– Occurrence: ZeroOrOne
– Format: int
– Access Types: Get, Replace
– Values: <ThreshBeaconRSSIWLANLowANDSF>
The ThreshBeaconRSSIWLANLowANDSF threshold condition shall be evaluated as follows:
– if the measurement Beacon RSSI value is smaller than threshold value contained in this leaf, the UE shall consider this node as matching; otherwise the UE shall consider this node as not matching.
NOTE: Beacon RSSI is a metric for signal strength measured from Beacon frames as defined in IEEE 802.11™-2012 [26].
5.7.21B28 ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/
RANValidityCondition/ThresholdConditions/Thresholds/ThreshBeaconRSSIWLANLow/ThreshBeaconRSSIWLANLowRAN
The ThreshBeaconRSSIWLANLowRAN leaf node acts as a placeholder indicating that low threshold value of beacon RSSI threshold provided by E-UTRAN/UTRAN is to be taken into account when evaluating validity of the rule and is used by the UE for traffic steering to E-UTRAN/UTRAN.
– Occurrence: ZeroOrOne
– Format: Null
– Access Types: Get, Replace
– Values: N/A
The ThreshBeaconRSSIWLANLowRAN threshold condition shall be evaluated as follows:
– if ThreshBeaconRSSIWLANLowRAN leaf is present and ThreshBeaconRSSIWLANLow threshold value has not been received from E-UTRAN/UTRAN, the UE shall consider this node as not matching;
– otherwise if ThreshBeaconRSSIWLANLowRAN leaf is present and ThreshBeaconRSSIWLANLow threshold value has been received from E-UTRAN/UTRAN;
– if the measurement Beacon RSSI value is smaller than threshold value contained in this leaf, the UE shall consider this node as matching; otherwise the UE shall consider this node as not matching.
NOTE: Beacon RSSI is a metric for signal strength measured from Beacon frames as defined in IEEE 802.11™-2012 [26].
5.7.21B29 ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/
RANValidityCondition/ThresholdConditions/Thresholds/ThreshBeaconRSSIWLANHigh
The ThreshBeaconRSSIWLANHigh node leaf acts as a placeholder for high threshold value of beacon RSSI thresholds provisioned by ANDSF and/or by RAN.
– Occurrence: ZeroOrOne
– Format: node
– Access Types: Get, Replace
– Values: N/A
The ThreshBeaconRSSIWLANHigh threshold condition shall be evaluated as follows:
– if the ThreshBeaconRSSIWLANHighRAN node is present and ThreshBeaconRSSIWLANHighANDSF node is not present and the ThreshBeaconRSSIWLANHighRAN node is evaluated to be matching, the UE shall consider this node as matching;
– if the ThreshBeaconRSSIWLANHighANDSF node is present and ThreshBeaconRSSIWLANHighRAN node is not present and the ThreshBeaconRSSIWLANHighANDSF node is evaluated to be matching, the UE shall consider this node as matching;
– if both the ThreshBeaconRSSIWLANHighANDSF node and ThreshBeaconRSSIWLANHighRAN node are present ThreshBeaconRSSIWLANHighRAN node will take precedence over ThreshBeaconRSSIWLANHighANDSF node, i.e. the ThreshBeaconRSSIWLANHighRAN node is evaluated to be matching, the UE shall consider this node as matching. Otherwise, if the RAN threshold value has not been received from E-UTRAN/UTRAN and the ThreshBeaconRSSIWLANHighANDSF node is evaluated to be matching, the UE shall consider this node as matching;
– if this node is empty, the UE shall consider this node as matching; and
– otherwise the UE shall consider this node as not matching.
5.7.21B30 ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/
RANValidityCondition/ThresholdConditions/Thresholds/ThreshBeaconRSSIWLANHigh/ThreshBeaconRSSIWLANHighANDSF
The ThreshBeaconRSSIWLANHighANDSF leaf node acts as a placeholder for high threshold value of beacon RSSI threshold provisioned by ANDSF and is used by the UE for traffic steering to WLAN.
– Occurrence: ZeroOrOne
– Format: int
– Access Types: Get, Replace
– Values: <ThreshBeaconRSSIWLANHighANDSF>
The ThreshBeaconRSSIWLANHigh thresholdANDSF condition shall be evaluated as follows:
– if the measurement Beacon RSSI value is greater than threshold value contained in this leaf, the UE shall consider this node as matching; otherwise the UE shall consider this node as not matching.
NOTE: Beacon RSSI is a metric for signal strength measured from Beacon frames as defined in IEEE 802.11™-2012 [26].
5.7.21B31 ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/
RANValidityCondition/ThresholdConditions/Thresholds/ThreshBeaconRSSIWLANHigh/ThreshBeaconRSSIWLANHighRAN
The ThreshBeaconRSSIWLANHighRAN leaf node acts as a placeholder indicating that high threshold value of beacon RSSI threshold provided by E-UTRAN/UTRAN is to be taken into account when evaluating validity of the rule and is used by the UE for traffic steering to WLAN.
– Occurrence: ZeroOrOne
– Format: Null
– Access Types: Get, Replace
– Values: N/A
The ThreshBeaconRSSIWLANHighRAN threshold condition shall be evaluated as follows:
– if ThreshBeaconRSSIWLANHighRAN leaf is present and ThreshBeaconRSSIWLANHigh threshold value has not been received from E-UTRAN/UTRAN, the UE shall consider this node as not matching;
– otherwise if ThreshBeaconRSSIWLANHighRAN leaf is present and ThreshBeaconRSSIWLANHigh threshold value has been received from E-UTRAN/UTRAN;
– if the measurement Beacon RSSI value is greater than threshold value contained in this leaf, the UE shall consider this node as matching; otherwise the UE shall consider this node as not matching.
NOTE: Beacon RSSI is a metric for signal strength measured from Beacon frames as defined in IEEE 802.11™-2012 [26].
5.7.21B32 ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/
ThresholdConditions/ThresholdConditionEvalutionPolicy
The ThresholdConditionEvaluationPolicy leaf indicates evaluation policy for threshold conditions.
– Occurrence: One
– Format: bool
– Access Types: Get, Replace
– Values: 0, 1
0 Indicates that at least one threshold condition under Thresholds node is required to be matching for ThresholdCondition to be considered fulfilled.
1 Indicates that all threshold conditions under Thresholds node are required to be matching ThresholdCondition to be considered fulfilled.
The default value 0 applies if this leaf is not provisioned.
5.7.21B33 Void
5.7.21B34 ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/
RANValidityCondition/OPI
The OPI leaf contains the provisioned OPI value which is a bitmap assigned by ANDSF. Each bit in this bitmap is operator specific and is not defined in 3GPP specifications.
– Occurrence: One
– Format: int
– Access Types: Get, Replace
– Values: <OPI_bitmap>
The value of this leaf is a 16-bit integer formated as a bitmap. The meaning of each bit in this bitmap is operator specific and is not defined in 3GPP specifications.
The OPI node shall be evaluated as follows:
– if the RAN OPI value is received from E-UTRAN/UTRAN and a bitwise ‘AND’ operation between the OPI value received from RAN and the OPI value contained in this node is non-zero, the UE shall consider this node as matching; otherwise the UE shall consider this node as not matching.
5.7.21B35 ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/
RANValidityConditionRef
The RANValidityConditionRef leaf contains a reference to a RANValidityCondition interior node.
– Occurrence: ZeroOrOne
– Format: chr
– Access Types: Get, Replace
– Values: < a reference to a RANValidityCondition interior node >
The reference to a RANValidityCondition interior node is a full device URI as specified in OMA-TS-DM_Protocol-V1_2 [5A], identifying the RANValidityCondition interior node in the UE management tree.
RANValidityConditionRef leaf is considered a match when the referenced RANValidityCondition interior node is considered a match according to the rules described in subclause 5.7.21B1.
5.7.22 Void
5.7.23 ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingRule
The RoutingRule node indicates the preferred access for a flow distribution rule.
– Occurrence: One
– Format: node
– Access Types: Get, Replace
– Values: N/A
This node and its descendants are the same as defined in ANDSF/Policy/<X>/PrioritizedAccess unless explicitly specified.
5.7.23AA ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingRule/<X>
This interior node acts as a placeholder for one or more prioritized accesses.
– Occurrence: OneOrMore
– Format: node
– Access Types: Get, Replace
– Values: N/A
This node and its descendants are the same as defined in ANDSF/Policy/<X>/PrioritizedAccess/<X> unless explicitly specified.
The UE selects between 3GPP access technologies (i.e. E-UTRA, UTRA, GERAN) using the mechanisms implemented by lower layers (e.g. cell selection, cell reselection, handover, etc). If a 3GPP access technology corresponding to the value configured in the AccessTechnology leaf under this node is not selected by the UE then the UE shall ignore this node until the 3GPP access technology corresponding to the value configured in the AccessTechnology leaf becomes selected.
5.7.23A ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingRule/<X>/
AccessTechnology
The AccessTechnology leaf indicates a prioritized access technology.
– Occurrence: One
– Format: int
– Access Types: Get, Replace
– Values: <Access technology>
Possible values for the Access technology are specified in table 5.7.23A.1.
Table 5.7.23A.1: Possible values for the AccessTechnology leaf
Value |
Description |
0 |
Reserved |
1 |
Any 3GPP access technology, e.g. E-UTRA, UTRA, GERAN |
2 |
Reserved |
3 |
WLAN |
4 |
E-UTRA |
5 |
UTRA |
6 |
GERAN |
7-255 |
Reserved |
5.7.24 ANDSF/ISRP/<X>/ForFlowBased/<X>/RulePriority
The RulePriority leaf represents the priority given to one particular flow distribution rule and is represented as a numerical value.
– Occurrence: One
– Format: int
– Access Types: Get, Replace
– Values: <Rule priority>
RulePriority leaf is used to establish to which flow description rule a data traffic matching multiple flow distribution rules apply. The data traffic matching multiple flow distribution rules applies to the flow description rule with the highest priority. The UE shall treat the rule with the lowest RulePriority value as the rule having the highest priority. If the UE finds multiple rules with the same priority, the choice of the rule is UE implementation specific. If there are no matching access networks according to the rule, other rules with the same priority may be considered. If there are no matching access networks according to any rule with a certain priority, rules with lower priority may be considered.
5.7.25 ANDSF/ISRP/<X>/ForServiceBased
The ForServiceBased node represents flow distribution container indicating data distribution among accesses based on APN.
– Occurrence: ZeroOrOne
– Format: node
– Access Types: Get, Replace
– Values: N/A
5.7.26 ANDSF/ISRP/<X>/ForServiceBased/<X>/
This interior node acts as a placeholder for one or more flow distribution rules indicating data distribution among accesses based on APN.
– Occurrence: OneOrMore
– Format: node
– Access Types: Get, Replace
– Values: N/A
5.7.27 ANDSF/ISRP/<X>/ForServiceBased/<X>/APN
The APN leaf indicates the APN for which a particular flow distribution rule is valid.
– Occurrence: ZeroOrOne
– Format: chr
– Access Types: Get, Replace
– Values: <APN>
The APN format is defined in 3GPP TS 23.003 [3]. If this node is omitted, the flow description applies to any APN.
NOTE: If the APN leaf is omitted, this flow description will override flow descriptions of specific APNs whose Rule priority is not higher than the Rule priority of this flow description.
5.7.28 ANDSF/ISRP/<X>/ForServiceBased/<X>/RoutingCriteria
The RoutingCriteria node acts as a placeholder for validity conditions for a particular flow distribution rule.
– Occurrence: ZeroOrOne
– Format: node
– Access Types: Get, Replace
– Values: N/A
If at least one instance of ANDSF/ISRP/<X>/ForServiceBased/<X>/RoutingCriteria/<X> node indicates matching validity condition, the UE shall consider the corresponding flow distribution rule as valid.
If the ANDSF/ISRP/<X>/ForServiceBased/<X>/RoutingCriteria/<X> node is present and empty (i.e. none of the nodes ValidityArea, ValidityAreaRef, TimeOfDay, TimeOfDayRef, RANValidityCondition or RANValidityConditionRef exist), the ANDSF/ISRP/<X>/ForServiceBased/<X>/RoutingCriteria/<X> node is not considered when evaluating the validity of the corresponding flow distribution rule.
5.7.29 ANDSF/ISRP/<X>/ForServiceBased/<X>/RoutingCriteria/<X>/
This internal node acts as a placeholder for one or more validity conditions for a particular flow distribution rule.
– Occurrence: OneOrMore
– Format: node
– Access Types: Get, Replace
– Values: N/A
The UE shall consider the corresponding flow distribution rule as valid only if all the present interior nodes (ValidityArea, ValidityAreaRef, TimeOfDay, TimeOfDayRef, RANValidityCondition or RANValidityConditionRef) within a single instance of ANDSF/ISRP/<X>/ForServiceBased/<X>/RoutingCriteria/<X> node indicate matching validity condition.
5.7.30 ANDSF/ISRP/<X>/ForServiceBased/<X>/RoutingCriteria/<X>/
ValidityArea
The ValidityArea node acts as a placeholder for location conditions for a particular flow distribution rule.
– Occurrence: ZeroOrOne
– Format: node
– Access Types: Get, Replace
– Values: N/A
This node and its descendants are the same as defined in ANDSF/Policy/<X>/ValidityArea.
5.7.30A ANDSF/ISRP/<X>/ForServiceBased/<X>/RoutingCriteria/<X>/
ValidityAreaRef
The ValidityAreaRef leaf contains a reference to a ValidityArea interior node.
– Occurrence: ZeroOrOne
– Format: chr
– Access Types: Get, Replace
– Values: < a reference to a ValidityArea interior node >
This node is the same as defined in ANDSF/Policy/<X>/ValidityAreaRef.
5.7.31 ANDSF/ISRP/<X>/ForServiceBased/<X>/RoutingCriteria/<X>/
TimeOfDay
The TimeOfDay node acts as a placeholder for day condition for a particular flow distribution rule.
– Occurrence: ZeroOrOne
– Format: node
– Access Types: Get, Replace
– Values: N/A
This node and its descendants are the same as defined in ANDSF/Policy/<X>/TimeOfDay.
5.7.31A ANDSF/ISRP/<X>/ForServiceBased/<X>/RoutingCriteria/<X>/
TimeOfDayRef
The TimeOfDayRef leaf contains a reference to a TimeOfDay interior node.
– Occurrence: ZeroOrOne
– Format: chr
– Access Types: Get, Replace
– Values: < a reference to a TimeOfDay interior node >
This node is the same as defined in ANDSF/Policy/<X>/TimeOfDayRef.
5.7.31B1 ANDSF/ISRP/<X>/ForServiceBased/<X>/RoutingCriteria/<X>/
RANValidityCondition
The RANValidityCondition node acts as a placeholder for RAN validity condition for a particular flow distribution rule.
– Occurrence: ZeroOrOne
– Format: node
– Access Types: Get, Replace
– Values: N/A
This node and its descendants are the same as defined in ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/RANValidityCondition.
5.7.31B2 ANDSF/ISRP/<X>/ForServiceBased/<X>/RoutingCriteria/<X>/
RANValidityConditionRef
The RANValidityConditionRef leaf contains a reference to a RANValidityCondition interior node.
– Occurrence: ZeroOrOne
– Format: chr
– Access Types: Get, Replace
– Values: < a reference to a RANValidityCondition interior node >
This node is the same as defined in ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/RANValidityConditionRef.
5.7.32 ANDSF/ISRP/<X>/ForServiceBased/<X>/RoutingRule
The RoutingRule node indicates the preferred access for a flow distribution rule.
– Occurrence: One
– Format: node
– Access Types: Get, Replace
– Values: N/A
This node and its descendants are the same as defined in ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingRule.
5.7.33 ANDSF/ISRP/<X>/ForServiceBased/<X>/RulePriority
The RulePriority leaf represents the priority given to a particular flow distribution rule and is represented as a numerical value.
– Occurrence: One
– Format: int
– Access Types: Get, Replace
– Values: <Rule priority>
RulePriority leaf is used to establish to which flow description rule a data traffic matching multiple flow distribution rules apply. The data traffic matching multiple flow distribution rules applies to the flow description rule with the highest priority. The UE shall treat the rule with the lowest RulePriority value as the rule having the highest priority. If the UE finds multiple rules with the same priority, the choice of the rule is UE implementation specific. If there are no matching access networks according to the rule, other rules with the same priority may be considered. If there are no matching access networks according to any rule with a certain priority, rules with lower priority may be considered.
5.7.34 ANDSF/ISRP/<X>/ForNonSeamlessOffload/
The ForNonSeamlessOffload node represents a flow distribution container indicating data permissible for non-seamless WLAN offload routing based on flow description.
– Occurrence: ZeroOrOne
– Format: node
– Access Types: Get, Replace
– Values: N/A
5.7.35 ANDSF/ISRP/<X>/ForNonSeamlessOffload/<X>/
This interior node acts as a placeholder for one or more flow distribution rules indicating data distribution among accesses based on flow description.
– Occurrence: OneOrMore
– Format: node
– Access Types: Get, Replace
– Values: N/A
5.7.36 ANDSF/ISRP/<X>/ForNonSeamlessOffload/<X>/IPFlow
The IPFlow node indicates the flow description for a particular flow distribution rule.
– Occurrence: One
– Format: node
– Access Types: Get, Replace
– Values: N/A
An empty IPFlow node indicates the match-all flow description.
If the flow distribution rule contains more than one instance of the ANDSF/ISRP/<X>/ForNonSeamlessOffload/<X>/IPFlow/<X> node (i.e. flow description), the UE shall consider the flow distribution rule if at least one of the flow descriptions as described in subclause 5.7.37 matches the traffic.
5.7.37 ANDSF/ISRP/<X>/ForNonSeamlessOffload/<X>/
IPFlow/<X>
This interior node acts as a placeholder for one or more flow description.
– Occurrence: OneOrMore
– Format: node
– Access Types: Get, Replace
– Values: N/A
If the flow description is defined with more than one interior node or leaf (i.e. App-ID, AddressType, etc.) within a single instance of the ANDSF/ISRP/<X>/ForNonSeamlessOffload/<X>/IPFlow/<X> node, then UE shall consider the flow description matching the traffic only if all the present interior nodes and leaf values match the traffic.
5.7.37A ANDSF/ISRP/<X>/ForNonSeamlessOffload/<X>/
IPFlow/<X>/App-ID
This interior node acts as a placeholder for an IPFlow identification based on an applicationID.
An IP flow is evaluated as matching if the IP flow matches at least one child node.
– Occurrence: ZeroOrOne
– Format: node
– Access Types: Get, Replace
– Values: N/A
The absence of this leaf indicates that the application identifier is not examined when matching packets against the IP flow description of the rule.
5.7.37B ANDSF/ISRP/<X>/ForNonSeamlessOffload/<X>/
IPFlow/<X>/App-ID/<X>/
This interior node acts as a placeholder for one or more combinations of OSId and OSAppId values.
– Occurrence: OneOrMore
– Format: node
– Access Types: Get,Replace
– Values: N/A
An IP flow is evaluated as matching if the IP flow is sent by an application:
– which uses services provided by an OS identified by the OS system identifier in the OSId leaf contained in this interior node; and
– associated with an OS specific application identifier in one of the OSAppId leaves contained in the OSApps interior node.
5.7.37C Void
5.7.37D ANDSF/ISRP/<X>/ForNonSeamlessOffload/<X>/
IPFlow/<X>/App-ID/<X>/OSId
The OSId leaf indicates an operating system identifier.
– Occurrence: One
– Format: chr
– Access Types: Get, Replace
– Values: <operating system identifier>
The format of the operating system identifier is a Universally Unique IDentifier (UUID) as specified in IETF RFC 4122 [22].
5.7.37E ANDSF/ISRP/<X>/ForNonSeamlessOffload/<X>/IPFlow/<X>/App-ID/
<X>/OSApps/
This interior node acts as a placeholder for the list of OS specific application identifiers.
– Occurrence: One
– Format: node
– Access Types: Get, Replace
– Values: <N/A>
5.7.37F ANDSF/ISRP/<X>/ForNonSeamlessOffload/<X>/IPFlow/<X>/App-ID/
<X>/OSApps/<X>
This interior node acts as a placeholder for an OS specific application identifiers.
– Occurrence: OneOrMore
– Format: node
– Access Types: Get, Replace
– Values: <N/A>
5.7.37G ANDSF/ISRP/<X>/ForNonSeamlessOffload/<X>/IPFlow/<X>/ App-ID/
<X>/OSApps/<X>/OSAppId
The OSAppId leaf indicates an OS specific application identifier.
– Occurrence: One
– Format: chr
– Access Types: Get, Replace
– Values: <OS specific application identifier>
Further definition of the format of the OS specific application identifier is beyond the scope of this specification.
5.7.38 ANDSF/ISRP/<X>/ForNonSeamlessOffload/<X>/IPFlow/<X>/
AddressType
The AddressType leaf indicates the IP version of the addresses describing the IP flow.
– Occurrence: ZeroOrOne
– Format: chr
– Access Types: Get, Replace
– Values: ‘IPv4’, ‘IPv6’
The absence of this leaf indicates that the IP flow described by the rule can have both IPv4 and IPv6 addresses. This field is mandatory if StartSourceIPaddress leaf is present.
5.7.39 ANDSF/ISRP/<X>/ForNonSeamlessOffload/<X>/IPFlow/<X>/
StartSourceIPaddress
The StartSourceIPaddress leaf indicates the first IP source address of the IP address range of the IP flow description. The source address refers to the IP address of the data packets destined for the UE according to the terminology in the IETF RFC 6088 [24].
– Occurrence: ZeroOrOne
– Format: chr
– Access Types: Get, Replace
– Values: <an IPv4 address>, <an IPv6 address>.
The value of this leaf is an IPv4 address if the AddressType leaf value of the same rule is equal to IPv4. The value of this leaf is an IPv6 address if the AddressType leaf value of the same rule is equal to IPv6. If this leaf represents the first value of an IP source address range, the values of this leaf and the corresponding ANDSF/ISRP/<X>/ForNonSeamlessOffload /<X>/IPFlow/<X>/EndSourceIPaddress leaf are set so that the IP address range can be represented in prefix notation.
EXAMPLE: IPv4 address range 192.0.2.0 – 192.0.2.255 is equal to 192.0.2.0/24 in prefix notation, and IPv6 address range 2001:db8::/128 – 2001:db8:ffff:ffff:ffff:ffff:ffff:ffff/128 equals 2001:db8::/32 in prefix notation.
The absence of this leaf indicates that source address field of the IP header is not examined when matching packets against the IP flow description of the rule.
The UE ignores an IPFlow instance with a StartSourceIPaddress leaf without a correspondent AddressType leaf. If the IPFlow instance is the only one contained in the flow distribution rule, the UE ignores the flow distribution rule.
When applying the rule to uplink traffic, the UE matches the addresses contained in the range between StartSourceIPaddress and EndSourceIPaddress against destination IP address field of the uplink traffic packets.
5.7.40 ANDSF/ISRP/<X>/ForNonSeamlessOffload/<X>/IPFlow/<X>/
EndSourceIPaddress
The EndSourceIPaddress leaf indicates the last IP source address of the IP source address range of the IP flow description. The source address refers to the IP address of the data packets destined for the UE according to the terminology in the IETF RFC 6088 [24].
– Occurrence: ZeroOrOne
– Format: chr
– Access Types: Get, Replace
– Values: <an IPv4 address>, <an IPv6 address>.
This leaf can be present only if the leaf ANDSF/ISRP/<X>/ ForNonSeamlessOffload /<X>/IPFlow/<X>/StartSourceIPaddress is present. The absence of this leaf indicates that the IP source address range of the IP flow described by the rule is equal to the address contained in ANDSF/ISRP/<X>/ ForNonSeamlessOffload /<X>/IPFlow/<X>/StartSourceIPaddress. When representing the IP source address range with more than one IP address, the values of this leaf and the corresponding ANDSF/ISRP/<X>/ ForNonSeamlessOffload /<X>/IPFlow/<X>/StartSourceIPaddress leaf are set as defined in subclause 5.7.39.
The value of this leaf is an IPv4 address if the AddressType leaf value of the same rule is equal to IPv4. The value of this leaf is an IPv6 address if the AddressType leaf value of the same rule is equal to IPv6.
The UE ignores an IPFlow instance with a EndSourceIPaddress leaf without a correspondent StartSourceIPaddress leaf. If the IPFlow instance is the only one contained in the flow distribution rule, the UE ignores the flow distribution rule.
5.7.41 Void
5.7.42 Void
5.7.43 ANDSF/ISRP/<X>/ForNonSeamlessOffload/<X>/IPFlow/<X>/
ProtocolType
The ProtocolType leaf indicates the protocol type in a flow description.
– Occurrence: ZeroOrOne
– Format: int
– Access Types: Get, Replace
– Values: <Protocol type>
The value of ProtocolType leaf is a value among the internet protocol numbers as defined in IANA Assigned Internet Protocol Numbers [18]. In case of IPv4 flow description, the value contained in this leaf is compared with the value of the last protocol type field. In case of IPv6 flow description, the value contained in this leaf is compared with the value of the last next header field. The UE ignores an IPFlow instance with a ProtocolType leaf indicating a protocol type not supported by the UE. If the IPFlow instance is the only one contained in the flow distribution rule, the UE ignores the flow distribution rule.
5.7.44 ANDSF/ISRP/<X>/ForNonSeamlessOffload/<X>/IPFlow/<X>/
StartSourcePortNumber
The StartSourcePortNumber leaf indicates the first source port number of the source port numbers range of the IP flow description. The source port refers to the source port of the data packets destined for the UE according to the terminology in the IETF RFC 6088 [24].
– Occurrence: ZeroOrOne
– Format: int
– Access Types: Get, Replace
– Values: any value in the range 1-65535.
The absence of this leaf indicates that source port field of the transport protocol header is not examined when matching packets against the IP flow description of the rule.
When applying the rule to uplink traffic, the UE matches the port numbers contained in the range between StartSourcePortNumber and EndSourcePortNumber against destination port field of the uplink traffic packets.
5.7.45 ANDSF/ISRP/<X>/ForNonSeamlessOffload/<X>/IPFlow/<X>/
EndSourcePortNumber
The EndSourcePortNumber leaf indicates the last source port number of the source port numbers range of the IP flow description. The source port refers to the source port of the data packets destined for the UE according to the terminology in the IETF RFC 6088 [24].
– Occurrence: ZeroOrOne
– Format: int
– Access Types: Get, Replace
– Values: any value in the range 1-65535.
This leaf can be present only if the leaf ANDSF/ISRP/<X>/ForFlowBased/<X>/IPFlow/<X>/StartSourcePortNumber is present. The absence of this leaf indicates that the source port number range of the IP flow described by the rule is equal to the source port number contained in ANDSF/ISRP/<X>/ForFlowBased/<X>/IPFlow/<X>/StartSourcePortNumber.
The UE ignores an IPFlow instance with a EndSourcePortNumber leaf without a correspondent StartSourcePortNumber leaf. If the IPFlow instance is the only one contained in the flow distribution rule, the UE ignores the flow distribution rule.
5.7.46 ANDSF/ISRP/<X>/ForNonSeamlessOffload/<X>/IPFlow/<X>/
StartDestPortNumber
The StartDestPortNumber leaf indicates the first destination port number of the destination port numbers range of the IP flow description. The destination port refers to the destination port of the data packets sent by the corresponding node according to the terminology in the IETF RFC 6088 [24].
– Occurrence: ZeroOrOne
– Format: int
– Access Types: Get, Replace
– Values: any value in the range 1-65535.
The absence of this leaf indicates that destination port field of the transport protocol header is not examined when matching packets against the IP flow description of the rule.
When applying the rule to uplink traffic, the UE matches the port numbers contained in the range between StartDestPortNumber and EndDestPortNumber against source port field of the uplink traffic packets.
5.7.47 ANDSF/ISRP/<X>/ForNonSeamlessOffload/<X>/IPFlow/<X>/
EndDestPortNumber
The EndDestPortNumber leaf indicates the last destination port number of the destination port numbers range of the IP flow description. The destination port refers to the destination port of the data packets sent by the corresponding node according to the terminology in the IETF RFC 6088 [24].
– Occurrence: ZeroOrOne
– Format: int
– Access Types: Get, Replace
– Values: any value in the range 1-65535.
This leaf can be present only if the leaf ANDSF/ISRP/<X>/ForFlowBased/<X>/IPFlow/<X>/StartDestPortNumber is present. The absence of this leaf indicates that the destination port number range of the IP flow described by the rule is equal to the port number contained in ANDSF/ISRP/<X>/ForFlowBased/<X>/IPFlow/<X>/StartDestPortNumber.
The UE ignores an IPFlow instance with a EndDestPortNumber leaf without a correspondent StartDestPortNumber leaf. If the IPFlow instance is the only one contained in the flow distribution rule, the UE ignores the flow distribution rule.
5.7.48 ANDSF/ISRP/<X>/ForNonSeamlessOffload/<X>/IPFlow/<X>/
QoS
The QoS leaf indicates the DS or ToS values parameters in a flow description.
– Occurrence: ZeroOrOne
– Format: bin
– Access Types: Get, Replace
– Values: any value in the range from 0 up to and including 63 in a binary form.
The DS and ToS values are defined in IETF RFC 3260 [10A].
5.7.48A ANDSF/ISRP/<X>/ForNonSeamlessOffload/<X>/IPFlow/<X>/
DomainName
The DomainName leaf indicates the destination domain name of the IP Flow description.
– Occurrence: ZeroOrOne
– Format: chr
– Access Types: Get, Replace
– Values: <FQDN>
The value of FQDN is Fully Qualified Domain Name (e.g. www.example.com) that was resolved into the destination IP address. The FQDN format is defined in 3GPP TS 23.003 [3].
The absence of this leaf indicates that the domain name is not examined when matching packets against the IP flow description of the rule.
5.7.48B ANDSF/ISRP/<X>/ForNonSeamlessOffload/<X>/IPFlow/<X>/APN
The APN leaf indicates the APN of the IP flow description.
– Occurrence: ZeroOrOne
– Format: chr
– Access Types: Get, Replace
– Values: <APN>
The APN format is defined in 3GPP TS 23.003 [3].
If the traffic is for an APN matching the value of this leaf, then this leaf is evaluated as matching.
NOTE: Incorrect configuration of this parameter can cause traffic that needs to go to a particular Packet Data Network (PDN) to be transported over a WLAN that does not have access to the PDN, which in turn will cause the traffic to no longer be correctly routable.
5.7.49 ANDSF/ISRP/<X>/ForNonSeamlessOffload/<X>/
RoutingCriteria
The RoutingCriteria node acts as a placeholder for validity conditions for a particular flow distribution rule.
– Occurrence: ZeroOrOne
– Format: node
– Access Types: Get, Replace
– Values: N/A
If at least one instance of ANDSF/ISRP/<X>/ ForNonSeamlessOffload/<X>/RoutingCriteria/<X> node indicates matching validity condition, the UE shall consider the corresponding flow distribution rule as valid.
If the ANDSF/ISRP/<X>/ ForNonSeamlessOffload/<X>/RoutingCriteria/<X> node is present and empty (i.e. none of the nodes ValidityArea, ValidityAreaRef, TimeOfDay, TimeOfDayRef, RANValidityCondition or RANValidityConditionRef exist), the ANDSF/ISRP/<X>/ ForNonSeamlessOffload /<X>/RoutingCriteria/<X> node is not considered when evaluating the validity of the corresponding flow distribution rule.
5.7.50 ANDSF/ISRP/<X>/ForNonSeamlessOffload/<X>/
RoutingCriteria/<X>/
This internal node acts as a placeholder for one or more validity conditions for a particular flow distribution rule.
– Occurrence: OneOrMore
– Format: node
– Access Types: Get, Replace
– Values: N/A
The UE shall consider the corresponding flow distribution rule as valid only if all the present interior nodes (ValidityArea, ValidityAreaRef, TimeOfDay, TimeOfDayRef, RANValidityCondition or RANValidityConditionRef) within a single instance of ANDSF/ISRP/<X>/ ForNonSeamlessOffload /<X>/RoutingCriteria/<X> node indicate matching validity condition.
5.7.51 ANDSF/ISRP/<X>/ForNonSeamlessOffload/<X>/
RoutingCriteria/<X>/ValidityArea
The ValidityArea node acts as a placeholder for location conditions for a particular flow distribution rule.
– Occurrence: ZeroOrOne
– Format: node
– Access Types: Get, Replace
– Values: N/A
This node and its descendants are the same as defined in ANDSF/Policy/<X>/ValidityArea.
5.7.51A ANDSF/ISRP/<X>/ForNonSeamlessOffload/<X>/RoutingCriteria/<X>/
ValidityAreaRef
The ValidityAreaRef leaf contains a reference to a ValidityArea interior node.
– Occurrence: ZeroOrOne
– Format: chr
– Access Types: Get, Replace
– Values: < a reference to a ValidityArea interior node >
This node is the same as defined in ANDSF/Policy/<X>/ValidityAreaRef.
5.7.52 ANDSF/ISRP/<X>/ForNonSeamlessOffload/<X>/
RoutingCriteria/<X>/TimeOfDay
The TimeOfDay node acts as a placeholder for day condition for a particular flow distribution rule.
– Occurrence: ZeroOrOne
– Format: node
– Access Types: Get, Replace
– Values: N/A
This node and its descendants are the same as defined in ANDSF/Policy/<X>/TimeOfDay.
5.7.52A ANDSF/ISRP/<X>/ForNonSeamlessOffload/<X>/
RoutingCriteria/<X>/TimeOfDayRef
The TimeOfDayRef leaf contains a reference to a TimeOfDay interior node.
– Occurrence: ZeroOrOne
– Format: chr
– Access Types: Get, Replace
– Values: < a reference to a TimeOfDay interior node >
This node is the same as defined in ANDSF/Policy/<X>/TimeOfDayRef.
5.7.52B1 ANDSF/ISRP/<X>/ForNonSeamlessOffload/<X>/RoutingCriteria/
<X>/RANValidityCondition
The RANValidityCondition node acts as a placeholder for RAN validity condition for a particular flow distribution rule.
– Occurrence: ZeroOrOne
– Format: node
– Access Types: Get, Replace
– Values: N/A
This node and its descendants are the same as defined in ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/RANValidityCondition.
5.7.52B2 ANDSF/ISRP/<X>/ForNonSeamlessOffload/<X>/RoutingCriteria/<X>/
RANValidityConditionRef
The RANValidityConditionRef leaf contains a reference to a RANValidityCondition interior node.
– Occurrence: ZeroOrOne
– Format: chr
– Access Types: Get, Replace
– Values: < a reference to a RANValidityCondition interior node >
This node is the same as defined in ANDSF/ISRP/<X>/ForFlowBased/<X>/RoutingCriteria/<X>/RANValidityConditionRef.
5.7.53 Void
5.7.54 ANDSF/ISRP/<X>/ForNonSeamlessOffload/<X>/
RoutingRule
The RoutingRule node indicates the preferred access for a flow distribution rule.
– Occurrence: One
– Format: node
– Access Types: Get, Replace
– Values: N/A
5.7.55 ANDSF/ISRP/<X>/ForNonSeamlessOffload/<X>/
RoutingRule/<X>/
This interior node acts as a placeholder for one or more prioritized accesses.
– Occurrence: OneOrMore
– Format: node
– Access Types: Get, Replace
– Values: N/A
5.7.56 ANDSF/ISRP/<X>/ForNonSeamlessOffload/<X>/
RoutingRule/AccessId
The AccessId leaf represents an access network identifier.
– Occurrence: ZeroOrOne
– Format: chr
– Access Types: Get, Replace
– Values: <SSID>
The format of the SSID is defined by IEEE Std 802.11™-2012 [26].
The absence of this leaf indicates that the UE can consider any available WLAN access network for the network selection.
5.7.57 ANDSF/ISRP/<X>/ForNonSeamlessOffload/<X>/
RoutingRule/SecondaryAccessId
The SecondaryAccessId leaf represents a secondary access network identifier.
– Occurrence: ZeroOrOne
– Format: chr
– Access Types: Get, Replace
– Values: <HESSID>
This node is the same as defined in ANDSF/Policy/<X>/PrioritizedAccess/<X>/SecondaryAccessId.
5.7.58 ANDSF/ISRP/<X>/ForNonSeamlessOffload/<X>/
RoutingRule/AccessNetworkPriority
The AccessNetworkPriority leaf represents an access technology priority.
– Occurrence: One
– Format: int
– Access Types: Get, Replace
– Values: <Access network priority>
This node is the same as defined in ANDSF/Policy/<X>/PrioritizedAccess/<X>/AccessNetworkPriority.
5.7.59 ANDSF/ISRP/<X>/ForNonSeamlessOffload/<X>/
RulePriority
The RulePriority leaf represents the priority given to one particular flow distribution rule and is represented as a numerical value.
– Occurrence: One
– Format: int
– Access Types: Get, Replace
– Values: <Rule priority>
RulePriority leaf is used to establish to which flow description rule a data traffic matching multiple flow distribution rules apply. The data traffic matching multiple flow distribution rules applies to the flow description rule with the highest priority. The UE shall treat the rule with the lowest RulePriority value as the rule having the highest priority. If the UE finds multiple rules with the same priority, the choice of the rule is UE implementation specific. If there are no matching access networks according to the rule, other rules with the same priority may be considered. If there are no matching access networks according to any rule with a certain priority, rules with lower priority may be considered.
5.7.60 ANDSF/ISRP/<X>/Roaming
The Roaming leaf indicates the roaming condition for the ISRP rule.
– Occurrence: ZeroOrOne
– Format: bool
– Access Types: Get, Replace
– Values: 0, 1
0 Indicates that the rule is only valid when the UE is not roaming.
1 Indicates that the rule is only valid when the UE is roaming.
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.
The default value 0 applies if this leaf is not provisioned.The node is not used by the UE when the ISRP rule is provided by the V-ANDSF.
5.7.61 ANDSF/ISRP/<X>/PLMN
The PLMN leaf indicates a PLMN code of the operator, which created this ISRP rule.
– Occurrence: One
– Format: chr
– Access Types: Get, Replace
– Values: <PLMN>
The format of the PLMN is defined in 3GPP TS 23.003 [3].
When evaluating the PLMN leaf the following applies:
– if the value contained in this leaf is equal to the HPLMN (or an equivalent HPLMN) of the UE, the Roaming leaf is not provisioned or the value contained in the Roaming leaf of the ISRP rule is set to 0 and the UE is not roaming, the ISRP rule is valid;
– if the value contained in this leaf is equal to the HPLMN (or an equivalent HPLMN) of the UE, the value contained in the Roaming leaf of the ISRP rule is set to 1 and the UE is roaming, the ISRP rule is valid;
– if the value contained in this leaf is equal to a VPLMN (or an equivalent VPLMN) of the UE, and the UE is roaming in that VPLMN, the ISRP rule is valid independently of the Roaming leaf; and
– if there are multiple valid ISRP rules with the same value in the PLMN leaf, then the choice of which one to follow is UE implementation dependant.
5.7.62 ANDSF/ISRP/<X>/UpdatePolicy
The UpdatePolicy leaf indicates the update policy for the ISRP.
– Occurrence: ZeroOrOne
– Format: bool
– Access Types: Get, Replace
– Values: 0, 1
0 Indicates that the UE is not required to request an update of the rules.
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 ISRP when the rule is no longer considered to be valid by the UE.
The default value 0 applies if this leaf is not provisioned.