5.7A UE_Profile
24.3123GPPAccess Network Discovery and Selection Function (ANDSF) Management Object (MO)Release 17TS
5.7A.1 ANDSF/UE_Profile/
The UE_Profile node acts as a placeholder for describing the information characterizing the UE.
NOTE: In order to avoid conflicts in names of <X>/UE_Profile/<X> dynamic nodes and names of permanent nodes included in the <X>/UE_Profile interior node, the four leftmost characters of name of any permanent node included in the <X>/UE_Profile interior node are different from the "OsId" and the four leftmost characters of the name of <X>/UE_Profile/<X> dynamic nodes are the "OsId".
– Occurrence: ZeroOrOne
– Format: node
– Access Types: Get
– Values: N/A
5.7A.2 ANDSF/UE_Profile/<X>
This interior node acts as a placeholder for one or more profile aspects of the UE. The four leftmost characters of the name of this interior node are the "OsId".
– Occurrence: ZeroOrMore
– Format: node
– Access Types: Get
– Values: N/A
NOTE: A UE can have multiple concurrently active operating systems.
If the UE supports ISRP flow distribution rules or IARP flow distribution rules or both (see subclause 5.7A.4) containing an OS specific application identifier, one <X> interior node with OSId leaf is included for each supported OS in the ANDSF/UE_Profile node.
5.7A.3 ANDSF/UE_Profile/<X>/OSId
TheOSId leaf indicates the operating system identifier of the UE.
– Occurrence: One
– Format: chr
– Access Types: Get
– 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.7A.4 ANDSF/UE_Profile/DevCapability
The DevCapability leaf indicates the device capability of the UE and ANDSF can use this information to adapt the ANDSF MO information to the capabilities of the UE. The value of this leaf is a sequence of ‘1’ and ‘0’ characters, where the character value ‘1’ denotes support and ‘0’ denotes no support for a feature.
– Occurrence: ZeroOrOne
– Format: chr
– Access Types: Get
– Values: <Device Capability>
The first character of the leaf value indicates support for ISRP rules based on Application Identifiers (DIDA). If the UE supports ISRP rules based on Application Identifiers, the UE sets the first character of the leaf value to ‘1’.
The second character of the leaf value indicates support for IARP rules based on Application Identifiers (DIDA). If the UE supports IARP rules based on Application Identifiers, the UE sets the second character of the leaf value to ‘1’.
The third character of the leaf value indicates support for ValidityAreaRef leaf included in ISMP, DI, ISRP, WLANSP, and IARP. If the UE supports ValidityAreaRef leaf included in ISMP, DI, ISRP, WLANSP, and IARP, the UE sets the third character of the leaf value to ‘1’.
The fourth character of the leaf value indicates support for TimeOfDayRef leaf included in ISMP, ISRP, WLANSP, and IARP. If the UE supports TimeOfDayRef leaf included in ISMP, ISRP, WLANSP, and IARP, the UE sets the fourth character of the leaf value to ‘1’.
If this node is not present or the value is null string, the UE does not support any feature indicated with the node.
If there are additional characters in the leaf value and the ANDSF server does not understand them, these additional characters are ignored by the ANDSF server.
If a character is not ‘1’, the ANDSF server treats the value as ‘0’.