The SimcardOpenEPC components for Client Mobility Support have the role of interacting with the Core Network Mobility Management Components and providing an enhanced experience for the applications running on the client devices. While not mandatory for simple scenarios, the OpenEPC Client Mobility Manager improves majorly the user experience through the following features:
  • OMA DM SyncML based S14 interfaces enabled communication with the OpenEPC ANDSF based on 3GPP Rel.12;
  • automated network selection and vertical handover capabilities, enabling¬†operator-based networks balancing between different technologies;
  • providing the latest Inter-System Mobility Policies (ISMP), Inter-System Routing Policies (ISRP) and Inter-APN Routing Policies (IARP), with IP Flow Mobility (IFOM), Multi Access Point Connectivity (MAPCON) and Non-Seamless WiFi Offload (NSWO) capabilities
  • enabling HotSpot 2.0/WLANSP functionality
  • one-stop interface for exchanging connectivity information and commands with the client based applications;

The OpenEPC Client Mobility Manager is provided currently on Linux and Android platforms. Additional platforms can be supported on demand.

network

In the absence of the Client Mobility Manager, simpler and standard Network Managers can be instead employed. Attachments are standard and common, only their orchestrations as well the use of operator indicated policies, would lack in performance:

  • for 3GPP access, standard modem-based connectivity;
  • for non-3GPP standard WPA-EAP authentication, followed by DHCP/DHCPv6 procedures.

For providing value-added functionality, the Access Network Discovery and Selection Function (ANDSF) situated in the Core Network assists the Mobility Manager with information and operator pushed policies, through the S14 interfaces.

The ANDSF communicates over the S14 interface based on standard OMA DM SyncML protocols and recommendations, or alternatively on a simplified XML exchange over TCP, with the Client Mobility Manager in the UEs. Through this component, the operator can optimize both its network re-selection mechanisms, as well as enable advanced features:
  • steer devices towards less loaded access technologies or access points
  • request users to vacate a base station such that it could be turned-off to save power in access overlapping situations
  • auto discover access technology coverage
  • provide time/location/application based policies on selection and use of access networks
  • provide discovery information for non-3GPP wireless technologies
  • push IP Flow Mobility policy information towards the UE
web-epc_and_sfFor communicating with the PGW, the OpenEPC Client Mobility Manager side-steps the current lack of standardization for network-based mobility scenarios in 3GPP Rel.12 multi-access use-cases, by using a hybrid DSMIPv6 approach. Similar to the S2c interface concepts, the implementation provides the best of both worlds:
  • network-based mobility to provide seamless mobility to client device even without any Mobile-IP signaling support
  • auto-detection of pre-Rel.12/post-Rel.11 situation on a user-by-use basis, allowing for both seamless vertical handovers and IP flow mobility in parallel
  • flexible distribution of IP flows in a multi-access environment, through use of DSMIPv6 signaling with the PGW

Similar to the PCRF, also the ANDSF is connected to the HSS/SPR and hence Inter-system Mobility policies can be customized on a subscriber-by-subscriber basis.