Establishing application-based routing policies in multi-mode user equipment using operating system-specific identifiers
Techniques for establishing and implementing application-based routing policies for multi-mode wireless communication devices are described. In some examples, information particular to the profile and platform configuration of the UE, including an identifier of an operating system, is communicated to an Access Network Discovery Function (ANDSF) server. The ANDSF server may provide an inter-system routing policy (ISRP) to handle appropriate network offloading actions for the particular application and device configuration. In some examples, the ISRP may be specific to flow-based or non-seamless based traffic offloading from certain software applications and include nodes to define routing rules based on an operating system identifier and operating system-specific application identifier. The policy may be propagated from the ANDSF server and implemented in multi-mode UE mobile computing devices in connection with offloading policies established in a 3GPP LTE/LTE-A Evolved Packet Core network architecture.
1. A user equipment (UE), comprising:
one or more hardware processors configured to:
cause the UE to transmit UE profile information to a carrier-based access network, the UE profile information including a value for an operating system identifier (OSId) that identifies an operating system of the UE;
cause the UE to receive an ANDSF management object including a routing policy, the ANDSF management object being provided in response to transmission of the value for the OSId in the UE profile information; and
cause the UE to perform offloading of data from a software application arranged for operation within the operating system of the UE to a secondary access network, in accordance with the routing policy, wherein the routing policy indicates a routing rule for offloading data of the software application;
wherein the routing rule is defined for an operating system-specific application identifier (OSAppId) for the software application, and wherein the OSAppId is an identifier associated with the software application that uniquely identifies the software application within the UE for the OSId;
wherein a value for the OSAppId is defined in a first node of the routing policy, wherein a value for the OSId is defined in a second node of the routing policy, and wherein the first node and the second node are included in a third node of the routing policy; and
wherein the third node of the routing policy includes a plurality of nodes providing respective combinations of OSId and OSAppId values, and wherein the plurality of nodes includes the first node and the second node.
2. The UE of claim 1 , wherein the UE profile information includes information for one or more aspects of the UE including a software version, a hardware version, or a hardware architecture.
3. The UE of claim 1 , wherein the routing policy is an Inter-System Routing Policy providing a plurality of rules, wherein the plurality of rules includes a non-seamless offload-based routing rule defined in a fourth node of the routing policy, and wherein the fourth node of the routing policy includes the third node.
4. The UE of claim 1 , wherein the routing policy is an Inter-System Routing Policy providing a plurality of rules, wherein the plurality of rules includes a flow-based routing rule defined in a fifth node of the routing policy, and wherein the fifth node of the routing policy includes the third node.
5. The UE of claim 1 , wherein the carrier-based access network operates in accordance with a standard from a 3GPP Long Term Evolution or Long Term Evolution-Advanced (LTE/LTE-A) standards family, and wherein the secondary access network operates in accordance with a standard from an IEEE 802.11 standards family.
6. The UE of claim 1 , comprising an accelerometer.
7. The UE of claim 1 , comprising:
a transceiver arranged to communicate with the carrier-based access network.
8. The UE of claim 1 , comprising:
a transceiver arranged to communicate with the secondary access network.
9. A method, performed by hardware circuitry of a User Equipment (UE), for implementing an application-based routing policy, the method comprising:
transmitting, to a carrier-based access network, UE profile information, the UE profile information including a value for an operating system identifier (OSId) that identifies an operating system of the UE;
receiving, from the access network, a Access Network Discovery and Selection Function (ANDSF) management object, the ANDSF management object including a routing policy that is provided in response to transmission of the OSId in the UE profile information; and
offloading data from a software application arranged for operation within the operating system of the UE to a secondary access network, in accordance with the routing policy, wherein the routing policy indicates a routing rule for offloading data of the software application;
wherein the routing rule is defined for an operating system-specific application identifier (OSAppId) for the software application, wherein the OSAppId is an identifier associated with the software application that uniquely identifies the software application within the UE for the OSId;
wherein a value for the OSAppId is defined in a first node of the routing policy, wherein a value for the OSId is defined in a second node of the routing policy, and wherein the first node and the second node are included in a third node of the routing policy; and
wherein the third node of the routing policy includes a plurality of nodes providing respective combinations of OSId and OSAppId values, and wherein the plurality of nodes includes the first node and the second node.
10. The method of claim 9 , wherein the routing policy is an Inter-System Routing Policy providing a plurality of rules, wherein the plurality of rules includes a non-seamless offload-based routing rule defined in a fourth node of the routing policy, and wherein the fourth node of the routing policy includes the third node.
11. The method of claim 9 , wherein the routing policy is an Inter-System Routing Policy providing a plurality of rules, wherein the plurality of rules includes a flow-based routing rule defined in a fifth node of the routing policy, and wherein the fifth node of the routing policy includes the third node.
12. The method of claim 9 , wherein transmitting the OSId includes providing the UE profile information in an initial ANDSF management object transmitted from the UE to the access network during an Open Mobile Alliance Device Management (OMA-DM) exchange.
13. The method of claim 12 , wherein the ANDSF management object and the initial ANDSF management object are structured in an eXtensible Markup Language (XML) format.
14. The method of claim 9 , wherein a distinct node is included within the routing policy for each application of the UE identified for inclusion in the application routing policy for offloading data to the secondary access network.
15. The method of claim 9 , wherein the ANDSF management object is provided from an ANDSF server within an Evolved Packet Core operating in accordance with a standard from a 3GPP Long Term Evolution or Long Term Evolution-Advanced (LTE/LTE-A) standards family, and wherein the secondary access network is a wireless local area network operating in accordance with a standard from an IEEE 802.11 standards family.
16. A non-transitory machine readable medium including instructions, which when performed by a machine, cause the machine to perform operations to:
transmit, to a carrier-based access network, UE profile information, the UE profile information including a value for an operating system identifier (OSId) that identifies an operating system of the UE;
receive, from the access network, a Access Network Discovery and Selection Function (ANDSF) management object, the ANDSF management object including a routing policy that is provided in response to transmission of the value for the OSId in the UE profile information; and
offload data from a software application arranged for operation within the operating system of the UE to a secondary access network, in accordance with the routing policy, wherein the routing policy indicates a routing rule for offloading data of the software application;
wherein the routing rule is defined for an operating system-specific application identifier (OSAppId) for the software application, and wherein the OSAppId is an identifier associated with the software application that uniquely identifies the software application within the UE for the OSId;
wherein a value for the OSAppId is defined in a first node of the routing policy, wherein a value for the OSId is defined in a second node of the routing policy, and wherein the first node and the second node are included in a third node of the routing policy; and
wherein the third node of the routing policy includes a plurality of nodes providing respective combinations of OSId and OSAppId values, and wherein the plurality of nodes includes the first node and the second node.
17. The non-transitory machine readable medium of claim 16 , wherein the UE profile information includes information for one or more of:
a software version, a hardware version, or a hardware architecture.
18. The non-transitory machine readable medium of claim 16 , wherein the routing policy is an Inter-System Routing Policy providing a plurality of rules, wherein the plurality of rules includes a non-seamless offload-based routing rule defined in a fourth node of the routing policy, and wherein the fourth node of the routing policy includes the third node.
19. The non-transitory machine readable medium of claim 16 , wherein the routing policy is an Inter-System Routing Policy providing a plurality of rules, wherein the plurality of rules includes a flow-based routing rule defined in a fifth node of the routing policy, and wherein the fifth node of the routing policy includes the third node.
20. The non-transitory machine readable medium of claim 16 , wherein transmitting the OSId includes providing the UE profile information in an initial ANDSF management object transmitted from the UE to the access network during an Open Mobile Alliance Device Management (OMA-DM) exchange.
21. The non-transitory machine readable medium of claim 20 , wherein the ANDSF management object and the initial ANDSF management object are structured in an eXtensible Markup Language (XML) format.