Patent Publication Number: US-9408177-B2

Title: System and method for resource management for operator services and internet

Description:
TECHNICAL FIELD 
     This disclosure relates in general to the field of communications and, more particularly, to providing resource management for operator services and Internet. 
     BACKGROUND 
     Wireless communication technologies are used in connection with many applications involving laptop computers, cellular telephones, user equipment, tablets, etc. Wireless communication technologies are tasked with handling increased amounts of data traffic, where the types of data being transported through mobile wireless networks have changed dramatically. This is because of device sophistication, which fosters data-intensive activities such as displaying movies, playing video games, readily attaching photographs to e-mails and text messages, etc. Moreover, video file-sharing and other types of usages (more traditionally associated with wired networks) have been gradually displacing voice as the dominant traffic in mobile wireless networks. There is a significant challenge for system architects and mobile operator providers to maintain a stable/reliable network environment and to provide optimal performance for their subscribers. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       To provide a more complete understanding of the present disclosure and features and advantages thereof, reference is made to the following description, taken in conjunction with the accompanying figures, wherein like reference numerals represent like parts, in which: 
         FIG. 1  is a simplified block diagram of a communication system for providing multi-radio management in accordance with one embodiment of the present disclosure; 
         FIG. 2  is a simplified flowchart illustrating possible example details associated with the communication system; 
         FIGS. 3A-3B  are simplified flowcharts illustrating potential operations associated with the communication system; 
         FIG. 4  is a simplified block diagram illustrating multi-radio control in a multiplexed environment in accordance with another embodiment of the present disclosure; 
         FIG. 5  is a simplified block diagram illustrating example details associated with a multi-radio management entity of the communication system; 
         FIG. 6  is a simplified block diagram illustrating example details associated with a cellular resource management architecture that employs WiFi analytics in the communication system; and 
         FIG. 7  is a simplified flowchart illustrating example activities associated with a WiFi analytics component associated with the communication system. 
     
    
    
     DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS 
     Overview 
     A method is provided in one example embodiment and includes maintaining geographical information (e.g., X,Y coordinates, longitude/latitude data, preconfigured location information, satellite information, global positioning system (GPS) data, any suitable location information exchanged via packets, etc.) for a plurality of WiFi access points. The method also includes managing radio resources (bandwidth, tunnels, links, connections, session continuity, handover/handoff, etc.) for a UE at a network element using the geographical information for the plurality of WiFi access points. 
     The managing may include verifying a cellular network type for the UE, and preferentially admitting the UE if the UE is in a particular zone (e.g., residential applications, low-to-medium density hot-zones, enterprise branch offices, macrocellular coverage zones more generally, etc.). The managing may also include verifying if the UE belongs to a group associated with high data consumption (heavy data users); and verifying if a device associated with the UE belongs to a group associated with high data consumption (e.g., laptops, iPads, server, etc.). In more specific embodiments, the method may include establishing a first connection to a long-term evolution-customer premise equipment (LTE-CPE), which is coupled to a particular WiFi access point. The method can also include establishing a second connection to provide an LTE service over a backhaul. 
     The method may also include recording a plurality of attach times for a plurality of UEs; recording a plurality of detach times for the plurality of UEs; and generating a representative time metric for the plurality of UEs for each of the WiFi access points. The broad term ‘time metric’ can be inclusive of any suitable time interval, such as an average, a median, a minimum, etc. across a group of users (or an individual user) that may be camping on a given WiFi access point, a WiFi access location, a WiFi access link, etc. 
     In certain embodiments, a database of WiFi access point identifiers is provisioned and includes one or more media access control (MAC) addresses, and one or more global positioning system (GPS) locations associated with the WiFi access points. Additionally, each of the geographic locations can be associated with a set of services that are defined based on previously collected statistics associated with the WiFi access points. 
     The method may also include detecting that a particular UE has provided a request for a connection to a network via WiFi; and accessing a database to verify a geographic origin associated with the request for the connection. In certain instances, a database is provisioned and identifies particular WiFi access points associated with poor connectivity characteristics. Additionally, a database can be provisioned and includes a plurality of Mobile Equipment Identities (MEIs), which are mapped to respective device types. 
     In other implementations, the method includes maintaining Evolved Packet Core (EPC) subscription information associated with the UE, wherein the subscription information includes particular bit rates. The method can also include identifying a particular geographic location associated with a particular one of the WiFi access points; determining whether a configured threshold has been reached for the particular geographic location; and generating a request to release userplane bearer resources for the UE. Evolved packet core (EPS) bearers can be released for a packet data network (PDN) involving one or more gateways. The configured threshold can be a function of a time of day (ToD) characteristic. 
     In certain implementations, a local area network (LAN) session involving the UE is multiplexed to a mobile network session to provide session continuity for the UE. Additionally, traffic is loadbalanced across a LAN and a cellular access using dynamic host configuration protocol (DHCP) options. The method can include establishing a connection with a packet gateway (PGW)/serving gateway (SGW), which is coupled to a small cell that is coupled to the LTE-CPE. 
     In more particular embodiments, the method can include performing connection admission control of WiFi subscribers based on a plurality of mobile network parameters. The plurality of mobile network parameters are provided in a wireless connectivity object (WCO), and the WCO includes an aggregate maximum bit rate (AMBR) parameter, an allocation and retention priority (ARP) parameter, and a quality of service (QoS) class identifier. 
     In certain example scenarios, the method can include preempting an existing connection for a certain UE at a WiFi access point in favor of a different UE possessing certain subscription credentials. The existing connection can be redirected to a different WiFi access point. Additionally, a privileged access control is provided at a WiFi access point, and a subscriber identity is verified before being allowed access at the WiFi access point. Mobile network QoS parameters for the UE can be signaled to the WiFi access network such that the WiFi access network is able to obtain WiFi QoS parameters that are equivalent to the mobile network QoS parameters. 
     The method can also include enforcing rate-limiting of subscriber traffic in the WiFi access network based on an equivalent to an aggregate maximum bit rate (AMBR) parameter. Service data flow rules can be used to mark Differentiated Services Code Point (DSCP) in certain Internet protocol (IP) headers to enable the WiFi access point to provide WiFi QoS consistent with mobile network subscription parameters. Additionally, signaling can be performed to establish tunnels from a WiFi access network gateway to a mobile network gateway. Connectivity parameters can be received as new DHCP or IPv6 Neighbor Discovery options. The WiFi access point is signaled to establish a tunnel with the WiFi access network gateway. 
     Example Embodiments 
     Turning to  FIG. 1 ,  FIG. 1  is a simplified block diagram of a communication system  10  for providing multi-radio management for Internet and operator services in accordance with one embodiment of the present disclosure. In a particular implementation, the architecture of  FIG. 1  may work in conjunction with local area network (LAN) access and a long-term evolution (LTE) service, which includes a backhaul. Communication system  10  may include multiple instances of user equipment (UEs)  12   a - x  and one or more WiFi wireless access points (WAPs)  14 , which collectively form a wireless LAN (WLAN). In addition,  FIG. 1  illustrates a small cell  28  and a multi-radio management entity (MRME)  20 , which includes a processor  42  and a memory element  44 . Also provided in communication system  10  is an LTE-CPE  24 , which may include wireless LAN controller (WLC), and which may provide an interface between the WLAN and MRME  20  and small cell  28 . 
     In certain embodiments, the architecture of  FIG. 1  may include infrastructure (generally indicated at arrow  16 ), which may include a packet data gateway/serving gateway (PGW/SGW)  38 . PGW/SGW  38  is coupled to a home subscriber server (HSS)  30 , a charging gateway function online charging system  32 , a policy and charging rules function (PCRF)  34 , and an access network delivery selection function (ANDSF)  36 . Communications between these elements may occur over the S6a interface, the Gy interface, the Gx interface, or over any other suitable link or interface. 
     In operation, MRME  20  can be configured to perform subscriber admission control based on evolved packet core (EPC) subscriptions. Additionally, MRME  20  is configured to provide nomadic (or mobile) session decisions, EPC-equivalent quality of service (QoS) signaling. In addition, MRME  20  is configured to offer privileged access control, along with traffic routing rule delivery. 
     For purposes of illustrating certain example techniques of communication system  10 , it is important to understand the typical communications that may be traversing the WiFi/cellular networks. The following foundational information may be viewed as a basis from which the present disclosure may be properly explained. Several deployments require access to the Internet and operator services via the LAN access (such as WiFi). For example, these can include residential broadband without wireline backhaul, hotspots, hot-zones, high-density venues such as stadiums, etc. LTE can provide backhaul technology for such deployments and offer a capacity savings for the operator, since a single EPS bearer is statistically multiplexed across multiple LAN users. LTE can also offer coverage relief for the operator because a LAN technology is used for access. Also, the LTE framework offers a predictable service delivery based on known technology (without relying on 3rd parties). 
     In such an architecture, the end users may use either the LAN or the cellular network to access the Internet and the operator services. However, in such LAN-multiplexed-on-LTE deployments, several problems should be resolved. For example, the operators should be able to authenticate LAN users before allowing access via LTE. This is a basic requirement that can be accomplished using protocol procedures specified in various standards (e.g., 3GPP). Operators should also account for admission control for LAN users to ensure predictable service. In essence, in order to ensure predictability across the LAN and cellular networks, there needs to be a way to limit a total number of users attached to the LAN. Separately, operators should limit the users accessing the LTE service based on the physical location. Additionally, operators should provide session continuity with common policies across LAN and cellular access. Essentially, subject to policy, a user&#39;s session via the LAN and cellular access should be able to continue regardless of access movements. 
     Operators should also balance traffic across LAN and cellular networks. For example, when a user has both LAN and cellular access, the operator should be able to distribute the traffic load based on the suitability of services and access. Also, operators should offer common policy management, where the operator applies policies consistently across access networks. Note that with the LTE backhaul, there is a need for hierarchical policy management because a LAN user&#39;s policy is subject to the policy affecting the LTE backhaul subscription. Furthermore, a LAN user may have independent policy profiles for the cellular network. 
     In accordance with the teachings of the present disclosure, the architecture of communication system  10  is configured to address these issues (and others) in offering an effective platform for managing resources across networks. More specifically, the solution includes leveraging MRME  20  and LTE-CPE  24 , which can include LTE user equipment, along with a wireless LAN router, the WLC, and an Internet offload interface (where the WLC and the Internet offload interface may be viewed as optional). MRME  20  can intelligently manage the LAN user&#39;s session on LTE-CPE  24 , as well as directly managing this device. In addition, PGW/SGW  38  is configured to manage the LAN user&#39;s EPC session in accordance with the policy governing both the LTE-CPE and the user. 
     In more specific terms, the architecture of  FIG. 1  can provide the following functionalities. For admission control for LAN users, the number of users accessing the Internet and operator services can be limited by MRME  20 , thereby providing some degree of service assurance to subscribers. In regards to QoS in the LAN, the LAN can be programmed with QoS parameters consistent with the user&#39;s policy and subscription in the EPC. This can ensure consistent and predictable subscriber experiences. For close subscriber group support, a subset of LAN users with access privileges would be allowed to access certain LTE-CPEs (e.g., based on physical location of the LAN and LTE-CPE). For session continuity, a LAN user&#39;s session multiplexed on the LTE-CPE can be adjoined with the LAN user&#39;s mobile network session, thus providing session continuity and common policy application. In addition, for flow mobility, based on policy, the PGW can loadbalance traffic across LAN and cellular access. This information can be provided to the LAN device through one or more new dynamic host configuration protocol (DHCP) options. In alternative embodiments, a 3rd party device (e.g., a 3GPP ANDSF function) can be triggered by the PGW to signal the LAN device. 
     For hierarchical policy management, embodiments of the present disclosure can offer a mechanism for managing a user&#39;s policy as a member of a larger group depending on the type of access. For example, a user accessing the EPC via the LAN would be subject to a policy governing the subscription itself, as well as the policy governing the user within the realm of LTE-CPE access. An independent policy may apply for such a user accessing the EPC directly through cellular access. The actual connectivity can be associated with any appropriate radio technology (e.g., 3G UMTS/CDMA, 4G LTE, WLAN, etc.). 
     In regards to the LTE radio access options, for an LTE UE with WiFi, the UE has an LTE radio to a macrocell as the backhaul. The UE reflects a UE from the mobility management entity (MME) and PGW perspective. The UE can be a WiFi router IPv6 prefix delegations and IPv4 network address translation (NAT). Example scenarios can include residential applications, low-to-medium density hot-zones, enterprise branch offices, etc. In the case of an LTE UE associated with WiFi and a small cell, the UE has an LTE radio that connects to a small cell for higher capacity, which could be dedicated for the UE. In addition, backhaul from the small cell may be wireless or wired and, further, may need to be secured. The UE reflects a UE from the MME and PGW perspective. The UE can be a WiFi router with IPv6 prefix delegations and IPv4 NAT. Scenarios can include high-density venues (e.g., concerts, stadiums, Times Square, etc.). 
     MRME  20  is also configured execute operations in order to engender a unified subscriber control. In a generic sense, MRME  20  is reflective of a centralized function: overseeing the management of different radio access technologies. For example, MRME  20  performs connection admission control of WiFi subscribers based on a combination of mobile network (3G, 4G) parameters (e.g., including the aggregate maximum bit rate (AMBR), allocation and retention priority (ARP), QoS class identifier (QCI), etc.). This can pertain to already admitted users at a WiFi access point, as well as the subscription information of a new attachment request. 
     In certain cases, MRME  20  is configured to preempt an existing connection of a subscriber at a WiFi access point in favor of a new subscriber, who possesses better (preferred) subscription credentials. Furthermore, MRME  20  can preempt an existing connection of a subscriber at a WiFi access point in favor of a new subscriber possessing better subscription credentials. MRME  20  can subsequently provide a redirect service to the preempted subscriber so that the preempted subscriber could attach to a new WiFi access point. 
     Additionally, MRME  20  can perform privileged access control at a WiFi access point (e.g., a VIP lounge at an entertainment venue) in which MRME  20  verifies if the provided subscriber identity is allowed access at that particular WiFi access point. This can be achieved by consulting a local or external database consisting of geographical location of the WiFi access point, WiFi access point identifier, the service set identifier (SSID), a list of allowed users, etc. MRME  20  can be configured to provide a redirect service to a subscriber who is denied privileged access at a WiFi access point so that the subscriber can attempt connection to a different WiFi access point. In certain instances, MRME  20  can be configured to provide a redirect service to a privileged subscriber to attach to another WiFi access point with privileged access. This action may be performed, for instance, due to capacity limitation at the first WiFi access point. 
     In certain scenarios, MRME  20 , after performing connection admission control and or privileged access control, performs the signaling of QoS parameters to the WiFi access network (represented by a gateway node) such that the WiFi access network is able to obtain those QoS parameters that are equivalent to the mobile network (3G, 4G) QoS parameters. This signaling is typically done at the time of connection establishment with the mobile network, but it may also be done at any other appropriate time. Specifically, MRME  20  is configured to signal the wireless connectivity object (WCO), which contains the equivalent parameters (including AMBR, ARP, QoS class identifier (QCI), and service data flow rules). A service data flow (SDF) represents traffic of particular kind such as the worldwide web, YouTube, Facebook, etc. The service data flow rules can identify the treatment of different subscriber traffic, as well as the charging characteristics for the identified service data flows. The charging characteristics provide the information for the WiFi access network gateway to generate billing records. 
     The WiFi access network gateway (WAG) can enforce rate-limiting of subscriber traffic in the WiFi access network based on the equivalent AMBR parameter. Additionally, the WiFi access network gateway marks or re-marks the Differentiated Services Code Point (DSCP) in the IP header in accordance with the service data flow rules. Such marking or re-marking (when an already marked DSCP is not compliant with the SDF Rules) enables the WiFi access points to provide WiFi radio QoS that is consistent with the mobile network subscription parameters. The WiFi access network gateway can generate the subscriber billing records for the traffic served based on the charging characteristics that are provided. Note that the WAG is further detailed below in conjunction with the discussion of  FIG. 5 . 
     MRME  20 , after performing the connection admission control and or privileged access control, can perform the signaling with the WiFi access network (represented by a gateway node) so that the WiFi access network gateway can establish the connectivity with the mobile network (represented by the mobile network gateway such as a PGW (in 4G LTE), GGSN (in 3G UMTS), HA (in 3G CDMA), etc.). Specifically, the signaling is performed to establish the tunnels from the WiFi access network gateway to the mobile network gateway, as well as from the WiFi access network gateway to the WiFi access point. 
     Additionally, MRME  20  can be configured to provide the mobile UE specific parameters (e.g., the WiFi access point, and the mobile network gateway IP address to the WiFi access network gateway) as new DHCP options or IPv6 Neighbor Discovery options in the router solicitation message. The UE specific parameters can include the IMSI, UE-QoS (as identified in the subscription), and UE link-layer identifier. The WiFi access point parameters include a tunnel endpoint IP address, a GRE (or other tunnel identifier) key, AP geographic location, etc. 
     As an alternative to DHCP or IPv6 Neighbor Discovery, MRME  20  may provide the required tunneling parameters in an authentication, authorization, and accounting (AAA) message. The net result is that the WiFi access network gateway is able to establish the tunnel with the mobile network gateway. Additionally, the WiFi access network gateway provides connectivity parameters back to the MRME as new DHCP or IPv6 Neighbor Discovery options. These parameters include the UE-specific parameters (such as the assigned IP address and other relevant parameters), as well as its own tunnel parameters (such as the tunnel endpoint IP address, GRE key, etc.). As an alternative to DHCP or IPv6 Neighbor Discovery, the WiFi access network gateway may provide the required tunneling parameters in an AAA message. 
     MRME  20  can subsequently signal the WiFi access point to establish a tunnel with the WiFi access network gateway. This signaling may include the tunnel endpoint parameters of the WiFi access network gateway, as well as the WiFi subscriber identification (such as the assigned IP address/prefix and/or the MAC layer address) as new parameters that can be realized in the ‘Control And Provisioning of Wireless access points’ (CAPWAP) protocol in a particular embodiment of the present disclosure. Such a tunnel could be on a per-subscriber basis, or provided as an aggregate tunnel for a group of subscribers attached to the WiFi access point. 
     In terms of the infrastructure of the present disclosure, UEs  12   a - x  can be associated with clients, customers, endpoints, handheld devices, or end users wishing to initiate a communication in communication system  10  via some network. The term ‘UE’ and the term ‘mobile subscriber’ are inclusive of devices used to initiate a communication, such as a receiver, a computer, a router, a gateway, a network appliance, a proprietary device, a set-top box, an Internet radio device (IRD), a cell phone, a smartphone of any kind, a tablet, a personal digital assistant (PDA), an iPhone, an iPad, a Google Droid, or any other device, component, element, or object capable of initiating voice, audio, video, media, or data exchanges within communication system  10 . UEs  12   a - x  may also be inclusive of a suitable interface to the human user, such as a display, a keyboard, a touchpad, a remote control, or other terminal equipment. UEs  12   a - x  may also be any device that seeks to initiate a communication on behalf of another entity or element, such as a program, a database, or any other component, device, element, or object capable of initiating an exchange within communication system  10 . Data, as used herein in this document, refers to any type of numeric, voice, video, media, or script data, or any type of source or object code, or any other suitable information in any appropriate format that may be communicated from one point to another. 
     WAPs  14  are configured to connect one or more UEs  12   a - x  to a network (e.g., a WiFi network). WAPs  14  may resemble a network hub, relaying data between connected wireless devices (e.g., UEs  12   a - x ) in addition to a connected wired device (e.g., an Ethernet hub or switch). This allows wireless devices to communicate with other wired and wireless devices. Networks of the present disclosure represent a series of points or nodes of interconnected communication paths for receiving and transmitting packets of information that propagate through the architecture. Each network can offer a communicative interface between sources and/or hosts, and each may be any LAN, WLAN metropolitan area network (MAN), Intranet, Extranet, wide area network (WAN), virtual private network (VPN), or any other appropriate architecture or system that facilitates communications in a network environment. The architecture of the present disclosure may include a configuration capable of transmission control protocol/internet protocol (TCP/IP) communications for the transmission and/or reception of packets in a network. The architecture of the present disclosure may also operate in conjunction with a user datagram protocol/IP (UDP/IP) or any other suitable protocol, where appropriate and based on particular needs. 
     PCRF  34  may be configured to determine policy rules in real-time in a multimedia network. PCRF  34  can operate at a network core and access subscriber databases and other specialized functions, such as charging systems, in a scalable and centralized manner. PCRF  34  is the part of the network architecture that aggregates information to and from the network, operational support systems, and other sources (such as portals) in real time, supporting the creation of rules and then making policy decisions for each UE  12   a - x  active on the network. AAA nodes in the network may provide authentication, authorization, and accounting for UEs  12   a - x  accessing and using communication system  10 . HSS  30  may provide management of a centralized subscriber database of UEs  12   a - x  accessing and using communication system  10 . 
     Turning to  FIG. 2 ,  FIG. 2  is a simplified flowchart  100  illustrating an operating procedure for an LTE-CPE with WiFi. In a general sense, the signaling messages provided are meant to be an embodiment of general-purpose procedures. This particular flow may begin at  102 , where the LTE-CPE maintains an always-on LTE connection. At  104 , the service provider (SP) policy can determine the backhaul bandwidth and other parameters associated with the LTE-CPE. At  106 , after suitable attachment, the LTE-CPE obtains an IPv6 prefix pool (e.g., either through configuration or via IPv6 prefix delegation from the PGW). At  108 , user equipment (UE) can perform the WiFi association. More specifically, the UE has a subscription with the service provider and, therefore, can present credentials for EPC authentication. In certain scenarios, the 802.1X authentication is followed by the Extensible Authentication Protocol (EAP)-Authentication and Key Agreement (AKA)/AKA being performed. The WLC in the LTE-CPE can operate as the authenticator, where it routes the messages to the operator&#39;s AAA server/authentication center (AuC). At  110 , after successful authentication, the WiFi-UE sends a DHCP request. At  112 , the LTE-CPE allocates the IPv6 prefix from the prefix pool and/or a private IPv4 address. 
     Turning to  FIGS. 3A-3B ,  FIGS. 3A-3B  are simplified flowcharts  200  illustrating the LTE-CPE performing a WiFi-UE connection procedure. This particular flow may begin at  202 , where a Non-Access Stratum (NAS) message (bearer resource allocation request) is sent. This message may include new parameters: WiFi-UE-IMSI, IPv6 prefix, IPv4 address, SSID, user location information (ULI), etc. At  204 , for admission control, MRME  20  can be configured to maintain a threshold for the number of WiFi connections allowed per LTE-CPE. A new connection request is rejected if the threshold has been reached. More sophisticated admission control methods can be equally used. At  206 , for the close subscriber group support, this can be thought of as a value-add feature for WiFi. MRME  20  is configured to verify if the WiFi-UE-IMSI is authorized to access the SSID at the given ULI. If the WiFi-UE is not authorized, MRME  20  rejects the bearer resource allocation request. 
     At  208 , MRME  20  sends a GPRS Tunneling Protocol (GTP)v2 bearer resource command message to the PGW. This message can include WiFi-UE-IMSI, IPv6 prefix and/or IPv4 address, radio access technology (RAT) Type=WiFi, SSID, ULI. It should be noted that the presence of WiFi-UE-IMSI is an indication to the PGW that a WiFi user is being “multiplexed” to the LTE-CPE. There can be other explicit indications provided at this juncture. At  210 , the PGW communicates with the PCRF (e.g., through IP-CAN session modification). The PCRF can maintain the policy and QoS information for the WiFi-UE-IMSI, SSID, and ULI. The policy can determine whether the user should be provided with a dedicated bearer. 
     In terms of session continuity, at  212  the policy rule may provide appropriate session continuity. If there is an existing (cellular) context for the WiFi-UE, then the same IPv6 prefix may be returned back for session continuity. Different policy rules can still apply based on RAT type. At  214 , for flow mobility, the policy rules may provide flow distribution across cellular and WiFi. In this case, the PGW may trigger the ANDSF server with the required flow rules to communicate with the UE. Alternatively, the flow rules may be provided in the GTP and NAS messages, where the LTE-CPE may provide the flow specs using DHCP options. At  216 , based on the PCRF interaction, the PGW either initiates an update bearer request (for default bearer modification) or create bearer request (for dedicated bearer creation) with MRME  20 . In either message, the PGW can include an IE containing the signature definition file (SDF) rules for the WiFi-UE. The rules may be specific to location (and/or time of day (ToD)). 
     At  218 , MRME  20  can generate a modify EPS bearer context request or activate dedicated EPS bearer context procedures. At  220 , MRME  20  is configured to provide a WiFi connectivity object (WCO) in the relevant NAS message to the LTE-CPE. The WCO contains the SDF rules provided by the PGW, and a mapping of the EPC QoS parameters to the WiFi QoS parameters. At  222 , the LTE-CPE establishes a context for the WiFi-UE with the received parameters and responds with the relevant NAS message to MRME  20 . MRME  20  responds to PGW with update bearer response or create bearer response message. The PGW updates the LTE-CPE context with WiFi-UE context (IMSI, IP address/prefix, policy rules). This completes the SDF/Bearer establishment on the LTE side for the WiFi-UE. As  230 , the LTE-CPE responds to the WiFi-UE with DHCP answer. 
     The IPv6 prefix and/or IPv4 address provided to the WiFi-UE depends on what is supplied in the NAS message. Specifically, if session continuity is provided, the addresses will be those supplied by the PGW (and not the ones allocated by the LTE-CPE in a previous step). This would complete the “WiFi-UE Connect” procedure. At  226 , the LTE-CPE programs the SDF and/or bearer rules for handling the traffic for the WiFi-UE. At  228 , the LTE-CPE provides the WCO object to the WLC, which may be co-located with the LTE-CPE. At  230 , the WLC programs the access points with the information provided in the WCO (e.g., IPv6 prefix, IPv4 address, MAC address of the WiFi-UE, 802.11n user priority levels etc.). 
     Turning to the specific functions associated with the architecture of  FIG. 1 , for the PGW (offering a hierarchical UE context), this element should multiplex a UE (LTE-CPE) context among multiple WiFi UEs using the LTE-CPE. The WiFi UEs may already have their own contexts on the PGW since a WiFi UE is generally a UE with a service provider subscription. Hence, a data structure that links the existing mobile context of a UE to its WiFi context under the LTE-CPE context is sufficient. The policy rules for direct LTE access and WiFi access for the same UE can be different. 
     For MRME  20 , admission control dictates limiting the number of WiFi users. This is based on the number of existing users and their aggregate bandwidth and QoS requirements. For closed subscriber groups, MRME  20  maintains a database of users with permitted LAN access at a particular physical location of the LTE-CPE. Only permitted users can be offered connectivity. For the of EPC QoS to the LAN, MRME  20  is configured to provide the WCO that maps parameters (e.g., EPC QoS, AMBR, GBR, QCI, ARP) to corresponding LAN parameters for rate-limiting, differentiated QoS, etc. 
     In addition, for LTE-CPE  24 , this device can perform EPC authentication for the LAN user. For example, LTE-CPE  24  can be configured for initiating EPS bearer modification upon LAN attach (e.g., WiFi association); initiating EPS bearer deactivation upon LAN detach (e.g., WiFi dissociation); and declining EPC access based on the admission control performed by the MRME. LTE-CPE  24  can also be responsible for declining EPC access based on a closed subscriber group verification provided by MRME  20 . In addition, LTE-CPE  24  can be responsible for maintaining LAN user context (including authentication, QoS, and policy); mapping of LAN user context to the corresponding LTE EPS bearer context; and rate-limiting traffic on the LAN interface based on the signaling from MRME  20  (co-located WLC). Also, LTE-CPE  24  can be configured for setting the user priority levels for WLAN access based on the WCO provided by MRME  20 . 
     Turning to  FIG. 4 ,  FIG. 4  is a simplified block diagram illustrating multi-radio control being performed in a LAN-multiplexed-WAN environment in accordance with one embodiment of communication system  10 . Note that much of the infrastructure of  FIG. 4  overlaps with that provided in  FIG. 1 . Additionally, it should be noted that a WiFi mobile multiplexer (WiMM)  50  is provided in this architecture. In this particular example, a subscriber context is being provided in WiMM  50 . In addition, a shared WAN bearer (e.g., LTE default EPS bearer) exists between PGW/SGW  38  and WiMM  50 , where individual subscriber traffic propagates between these elements. 
       FIG. 5  is a simplified block diagram illustrating an instance of MRME  20  in accordance with an example embodiment of communication system  10 . Note the per-user EPC subscription and QoS that exist between the WAG and MRME  20 . Note also that the WiFi network awareness between these elements, as is being illustrated. Within MRME  20 , there is WiFi access connection admission control, which can be based on the EPC subscription. Between each endpoint (i.e., UEs  12   a ,  12   b ) and the WAG is traffic routing rules distribution. In addition, in this particular example, PGW  38  facilitates a cohesive radio awareness with MRME  20 . 
     In operation of certain embodiments, components of the present disclosure effectively manage multi-radio connectivity service in which the subscribers attach to the mobile network via a LAN technology (such as WiFi) to a device that provides a shared common mobile network bearer (such as an EPS bearer in 4G LTE, PDP context in 3G UMTS, etc.). This can offer gains achievable from the statistical multiplexing of LAN subscriber traffic over the mobile network bearer, while simultaneously ensuring individual subscriber management of WiFi users at the mobile network gateway. As a point of clarification, such a statistical multiplexing of WiFi subscribers to a shared mobile network bearer (EPS Bearer or PDP context) is in contrast to WiFi subscribers attaching to the mobile network without sharing a common EPS bearer or a PDP context. As a matter of additional clarification, such a protocol is in contrast to WiFi subscribers sharing a common mobile network bearer, but without being individually managed by the mobile network gateway. 
     WiMM  50  can intelligently multiplex WiFi subscriber traffic onto a shared mobile network bearer based on the communication with MRME  20 . In one embodiment, WiMM  50  can be implemented on an LTE/3G UE device that simultaneously acts as a router towards the WiFi access and as a user equipment towards the LTE/3G network. WiMM  50  signals the WiFi subscriber parameters to MRME  20 . These new parameters can include WiFi-Subscriber-IMSI, IPv6 Prefix, IPv4 address, SSID, geographical location. In one embodiment, these parameters are signaled using the 3GPP standard NAS and the GTP messages. 
     Note that the mobile network gateway can decide which IP address to assign to the WiFi subscriber based on the policy configured either locally or obtained via an external server. Such a determination can be based on the explicit knowledge (signaled by the WiMM and subsequently by the MRME) that the subscriber attachment is for a WiFi subscriber that is connecting via a shared mobile network bearer. Such a determination can also be based on the operator policy as to whether the WiFi subscriber is offered only nomadic service without a persistence of service continuity across multiple radio networks, or if the WiFi subscriber is offered full mobility service with the persistence of service continuity across multiple radio networks. 
     MRME  20  can be configured to provide the WiFi access point usage and the prevailing network information to the mobile network gateway, which in turn can provide traffic routing rules to MRME  20 . Subsequently, MRME  20  can be configured to provide the traffic routing rules to the UE. The traffic routing rules determine the mapping of a particular traffic set to the corresponding radio technology. Such rules can be dynamic and dependent on such factors as the time of day, subscriber profile, etc. MRME  20  is configured to receive WiFi access point information upon each subscriber attaching or detaching (and/or at other configurable times). With the provided network health information, the mobile network gateway is configured to assign a particular traffic set to the appropriate radio technology. Such traffic routing information can be provided to the UE via MRME  20 . 
     In certain cases, MRME  20  can be configured to provide the network health information to the mobile network gateway as a set of new parameters in the GTP. Subsequently, the mobile network gateway provides the traffic routing rules for all the concerned radio technologies (3G, 4G, WiFi) as a set of new parameters in the GTP to the MRME. In certain instances, MRME  20  can be configured to provide the traffic routing rules to the UE for the relevant radio technologies (3G, 4G, WiFi) as a set of new parameters in the 3GPP NAS protocol. MRME  20  can be configured to provide the traffic routing rules as a set of new parameters in the NAS protocol to the WiMM, which in turn provides those rules to the UE as a set of new DHCP or IPv6 Neighbor Discovery options. 
       FIG. 6  is a simplified block diagram illustrating example details associated with cellular resource management with WiFi analytics. This particular example includes PGW  62  and SGW  60  as separate elements, although they may be co-located in other embodiments. In addition, a WiFi access point  70  is coupled to an evolved node B (eNB)  64 , which may be reflective of a macrocellular base station. WiFi access point  70  is associated with a stadium in this particular example. In addition, a different access point  68  may be provisioned at a mall location. The radio resources can be provided by eNB  64 , which can also provide radio resource management. Tunnel resource management can be provided by SGW  60 , where packet data network (PDN) connection management is provided by PGW  62 . 
     Multi-radio small cells offer a significant tool to enhance network coverage and capacity for mobile service providers. In certain environments, the mobile service provider can leverage the costs associated with deploying a small cell for cellular network to also include the WiFi as an access network. This enables the provider to use WiFi to support the burgeoning demand on capacity and to relieve congestion on cellular networks. However, the user experience can vary greatly on WiFi without adequate admission control and resource management. Embodiments of the present disclosure can use multi-radio information to make intelligent admission decisions such that a service provider can manage their overall network more intelligently and effectively. 
     When a mobile device has multi-radio capability, it can attach to more than one radio network simultaneously, for instance to LTE radio and WiFi. When a mobile service provider (MSP) controls cellular and WiFi access, as in a multi-radio metrocell in which the UE may be attached to the macrocell and WiFi or small cell and WiFi, it is important for the MSP to control the user experience while balancing the desire to offload traffic from cellular to WiFi. More specifically, the users at cell edges that generally receive poor macrocell experience should be given assured WiFi connectivity and experience compared to those having better cellular coverage (e.g., via a small cell). In addition, devices that are known to be high consumers of data (e.g., tablets) should be placed on WiFi if possible, based on the policy (such as the access point name (APN) configuration preference for the radio interface). In addition, the heavy data users also need to be placed on WiFi as much as possible. Also, certain WiFi locations may have restricted access. Only those users with privileged access should be given WiFi connectivity. 
     In summary, an MSP needs to make intelligent call admission control (CAC) and resource management decision in controlling the Quality of Experience (QoE) over WiFi, which is important, as WiFi becomes an integral part of mobile service delivery. Without such intelligence being provisioned in the network, subscriber experiences can vary widely and, further, be unpredictable during times of overcrowding and congestion. Once a CAC decision is made, it is important to enforce the subscription parameters so that no single user is able to monopolize the WiFi resources and adversely affect other users. This is the role of resource management. 
     MRME  20  maintains knowledge of multiple radios (macrocellular, small cell, and WiFi), as well as the user attachments to those radios. MRME  20  can be configured with a database of outdoor WiFi access point identifiers (such as unique MAC addresses, or any other such identifier), global positioning system (GPS) locations, and the service set identifiers of interest. MRME  20  can also be configured with a database consisting of a set of WiFi access points that fall within a poor macrocellular coverage zone, which reflects an area of known poor connectivity experience (such as poor signal-to-noise ratio and geometry factor). MRME  20  may also include a database consisting of a Mobile Equipment Identity (MEI) mapped to the device type. For instance, knowing the MEI (IMEI or IMEISV), the database could retrieve whether the device is a smartphone or a tablet. Furthermore, MRME  20  may also include a database of heavy traffic users, obtained from an external analytics engine, which outputs data using a call detail record (CDR) on a mobile gateway. In addition, MRME  20  has the user&#39;s EPC subscription information such as their Gold/Silver/Bronze tiers, along with the allocated bit rates, etc. 
     In operation, when an attach request arrives, MRME  20  knows the geographical location of the user within the granularity of the coverage radius of the WiFi access point to which the user is attaching. When a UE successfully attaches to a WiFi access point after authentication, its attach time is recorded by MRME  20 . When a UE detaches from an access point, the detach time is recorded by MRME  20 . With this information, each geographic location served by WiFi access points is attributed with a corresponding user “sojourn time”, which indicates a representative time (such as average, median, minimum etc.) across all users of camping on the WiFi access. For instance, a typical user at a game in a stadium is likely to be at the location for approximately two hours. The sojourn times are collected and corrected for hysteresis, and the statistics can be maintained over time. Other relevant access usage statistics can also be maintained. 
     Each geographic location also has a set of services defined based on its geo-context, which is associated with the preferred services for the location, as specified by the operator policy. For instance, a stadium may have interactive multimedia (based on content caching) as a preferred service, whereas a residential location is configured with voice over WiFi as a preferred service. Such services can be provisioned using a construct such as APN. In regards to signaling, when a UE connects to the EPC via WiFi, MRME  20  consults its database to verify the geo-origin of the request, and performs the following actions. 
     If the sojourn time for the location is at least as much as an operator-configured threshold for the location, MRME  20  sends a message “X-Request” to SGW  60  requesting it to release all user plane bearer resources for the UE. SGW  60  responds with an “X-Response” to MRME  20 , which then sends an “X′-Request” to the macrocellular base station (eNB), requesting it to release the radio resources associated with the UE. The eNB releases the Resource Reservation Control (RRC) connection and the associated UE context and responds with an “X′-Response” to MRME  20 . This causes the expeditious release of precious macro radio resources. This also causes the release of user plane tunnel resources at SGW  60 . 
     If the sojourn time for a location is at least as much as a configured threshold for the location and the geo-context so indicates, MRME  20 , in addition to releasing the macro radio resources alone, also releases the EPS bearer(s) for applicable PDNs in the EPC gateways. MRME sends a ‘Y-Request’ message (via SGW) to the PGW, which responds, with a ‘Y-Response’ message. Subsequently, MRME  20  sends a “Y′-Request” message to the eNB and the UE, and receives a “Y′-Response” message in return. 
     For example, when the geo-location is residential, an operator policy can be configured so that MRME  20  releases any dedicated EPS bearers as well as any PDN connection associated with an IMS APN (on cellular) if it can be served on the WiFi. With this configuration, some PDNs over cellular are deactivated entirely (i.e., both radio and core network resources are released), and the radio resources are released for those PDNs which are still resident on cellular network (while their EPC session state is maintained). Additionally, the above procedures are performed as a function of ToD triggers. Operators may establish different thresholds for sojourn times and geo-context based on the ToD policy of interest. 
     In a particular implementation, MRME  20  can be provisioned in a control node such as an MME in the LTE/SAE architecture. MRME  20  can have a well-defined interface to the WiFi controller, which manages the WiFi access points, as well as the user attachment. The WiFi controller may physically reside inside the same node as MRME or it may reside elsewhere in the network with a secure connection to MRME  20 . Similarly, MRME  20  communicates using a well-defined interface with the normal MME entity. 
     The message sequence X-Request/X-Response and XT-Request/XT-Response can be implemented using the S1 Release Procedure [e.g., TS 23.401]. The sequence X-Request/X-Response can map to the Release Access Bearer Request/Release Access Bearer Response sequence [e.g., TS 29.274]. The sequence XT-Request/XT-Response maps to S1-AP UE Context Release Command/S1-AP UE Context Release Complete sequence [e.g., TS 36.413]. 
     The message sequence Y-Request/Y-Response can be implemented either as an MME-initiated Bearer Deactivation procedure or M ME-initiated PDN Disconnection procedure [TS 23.401]. The messages can map to Delete Bearer Request/Delete Bearer Response and Delete Session Request/Delete Session Response respectively [TS 29.274]. The message sequence Y′-Request/Y′-Response can be implemented using E-RAB Release Command (S1-AP) with Deactivate EPS Bearer Context Request (i.e., NAS) and E-RAB Release Response (S1-AP) &amp; Deactivate EPS Bearer Context Accept sequences [TS 24.301, TS 36.413]. 
       FIG. 7  is a simplified flow diagram  700  illustrating example activities associated with intelligent provisioning of end users in a network environment. This particular flow may begin at  702 , when a user attempts to access WiFi at a given location. The corresponding UE can perform the appropriate authentication procedure. As a part of this procedure, the UE provides necessary credentials (e.g., its IMSI). Additionally, the UE can also supply the corresponding MEI. At  704 , the WiFi access network routes the authentication request to the MRME. Once the authentication succeeds at  706 , the MRME has the knowledge of which access point the request is arriving from, as well as the subscriber details. At  708 , the UE sends an association request, which is also routed to the MRME. At this point, the MRME performs the following series of actions. The exact sequence of actions is configurable based on policy. 
     At  710 , the MRME is configured to verify the cellular network type for the user. The MRME can preferentially admit the user if the user is in the Macro Red Zone. The MRME can also redirect an existing candidate user to a different AP if the resource situation so demands. At  712 , the MRME is configured to verify if the user belongs to a Heavy User Group. This group contains identities (e.g., IMSI/NAI) of known heavy users of the mobile Internet. The MRME can preferentially admit the user if the user is in the Heavy User Group. In addition, the MRME can redirect an existing candidate user to a different AP if the resource situation so demands. In  714 , the MRME is configured to verify if the device belongs to a Heavy Data Group. A listing for the group can list the devices (e.g., based on the MEI), where a listing reflects whether or not the device is a heavy consumer of mobile Internet data. The MRME is configured to preferentially admit the user if the device belongs to the Heavy Data Group. The MRME can also redirect an existing candidate user to a different AP if the resource situation so demands. 
     In terms of infrastructure configured to perform certain activities discussed herein, MRME  20 , LTE-CPE  24 , WiMM  50 , and PGW/SGW  38  are network elements that can facilitate many of the processing, resource management, and/or access activities discussed herein. As used herein in this Specification, the term ‘network element’ is meant to encompass any of the aforementioned elements, as well as routers, switches, cable boxes, gateways, bridges, loadbalancers, firewalls, inline service nodes, proxies, servers, processors, modules, or any other suitable device, component, element, proprietary appliance, user equipment, or object operable to exchange information in a network environment. These network elements may include any suitable hardware, software, components, modules, interfaces, or objects that facilitate the operations thereof. This may be inclusive of appropriate algorithms and communication protocols that allow for the effective exchange of data or information. 
     In one implementation, MRME  20 , LTE-CPE  24 , and/or WiMM  50  include software to achieve (or to foster) the resource management activities discussed herein. This could include the implementation of instances of various software modules to perform these activities. Additionally, each of these elements can have an internal structure (e.g., a processor, a memory element, etc.) to facilitate some of the operations described herein. In other embodiments, these access activities may be executed externally to these elements, or included in some other network element to achieve the intended functionality. Alternatively, MRME  20 , LTE-CPE  24 , and/or WiMM  50  may include software (or reciprocating software) that can coordinate with other network elements in order to achieve the resource management activities described herein. In still other embodiments, one or several devices may include any suitable algorithms, hardware, software, components, modules, interfaces, or objects that facilitate the operations thereof. 
     In certain example implementations, the resource management functions outlined herein may be implemented by logic encoded in one or more non-transitory tangible media (e.g., embedded logic provided in an application specific integrated circuit [ASIC], digital signal processor [DSP] instructions, software [potentially inclusive of object code and source code] to be executed by a processor [processor  42  shown in  FIG. 1 ], or other similar machine, etc.). In some of these instances, a memory element [memory element  44  shown in  FIG. 1 ] can store data used for the operations described herein. This includes the memory element being able to store instructions (e.g., software, logic, code, etc.) that are executed to carry out the activities described in this Specification. The processor (e.g., processor  42 ) can execute any type of instructions associated with the data to achieve the operations detailed herein in this Specification. In one example, the processor could transform an element or an article (e.g., data) from one state or thing to another state or thing. In another example, the activities outlined herein may be implemented with fixed logic or programmable logic (e.g., software/computer instructions executed by the processor) and the elements identified herein could be some type of a programmable processor, programmable digital logic (e.g., a field programmable gate array [FPGA], an erasable programmable read only memory (EPROM), an electrically erasable programmable ROM (EEPROM)) or an ASIC that includes digital logic, software, code, electronic instructions, or any suitable combination thereof. 
     Any of these elements (e.g., the network elements, etc.) can include memory elements for storing information to be used in achieving the access activities as outlined herein. Additionally, each of these devices may include a processor that can execute software or an algorithm to perform the access management activities as discussed in this Specification. These devices may further keep information in any suitable memory element [random access memory (RAM), ROM, EPROM, EEPROM, ASIC, etc.], software, hardware, or in any other suitable component, device, element, or object where appropriate and based on particular needs. Any of the memory items discussed herein should be construed as being encompassed within the broad term ‘memory element.’ Similarly, any of the potential processing elements, modules, and machines described in this Specification should be construed as being encompassed within the broad term ‘processor.’ Each of the network elements can also include suitable interfaces for receiving, transmitting, and/or otherwise communicating data or information in a network environment. 
     Note that with the examples provided above, interaction may be described in terms of two, three, or four network elements. However, this has been done for purposes of clarity and example only. In certain cases, it may be easier to describe one or more of the functionalities of a given set of flows by only referencing a limited number of network elements. It should be appreciated that communication system  10  (and its teachings) are readily scalable and, further, can accommodate a large number of components, as well as more complicated/sophisticated arrangements and configurations. Accordingly, the examples provided should not limit the scope or inhibit the broad teachings of communication system  10 , as potentially applied to a myriad of other architectures. 
     It is also important to note that the steps in the preceding FIGURES illustrate only some of the possible scenarios that may be executed by, or within, communication system  10 . Some of these steps may be deleted or removed where appropriate, or these steps may be modified or changed considerably without departing from the scope of the present disclosure. In addition, a number of these operations have been described as being executed concurrently with, or in parallel to, one or more additional operations. However, the timing of these operations may be altered considerably. The preceding operational flows have been offered for purposes of example and discussion. Substantial flexibility is provided by communication system  10  in that any suitable arrangements, chronologies, configurations, and timing mechanisms may be provided without departing from the teachings of the present disclosure. 
     Numerous other changes, substitutions, variations, alterations, and modifications may be ascertained to one skilled in the art and it is intended that the present disclosure encompass all such changes, substitutions, variations, alterations, and modifications as falling within the scope of the appended claims. In order to assist the United States Patent and Trademark Office (USPTO) and, additionally, any readers of any patent issued on this application in interpreting the claims appended hereto, Applicant wishes to note that the Applicant: (a) does not intend any of the appended claims to invoke paragraph six (6) of 35 U.S.C. section 112 as it exists on the date of the filing hereof unless the words “means for” or “step for” are specifically used in the particular claims; and (b) does not intend, by any statement in the specification, to limit this disclosure in any way that is not otherwise reflected in the appended claims.