Patent Description:
Mobile network operators (MNOs) may provide subscribers with managed network access using both cellular and WiFi technologies. Currently, MNOs typically consider WiFi only as a way to offload Internet-based traffic for their dual-mode subscribers. In current approaches, an MNO may configure certain handset applications to always use WiFi for Internet access when WiFi is available. For example, an MNO may configure applications to use WiFi when the applications are in low mobility scenarios and while they are within a WiFi hotspot. Current approaches to using WiFi may reduce congestion on the MNO's cellular and core networks, but the reduced congestion may come with a cost.

A more detailed understanding may be had from the following description, given by way of example in conjunction with accompanying drawings wherein:.

The ensuing detailed description is provided to illustrate exemplary embodiments and is not intended to limit the scope, applicability, or configuration of the invention. Various changes may be made in the function and arrangement of elements and steps without departing from the spirit and scope of the invention.

Integrated small cell and WiFi (ISW) networks are deployments of small cells in the licensed spectrum along with WiFi access points in the unlicensed spectrum. Mobile Network Operators (MNOs) are beginning to incorporate "carrier-grade" WiFi in ways that complement their cellular and core networks through cost-effective integration and interworking. This may drive development of a variety of network architectures, subscriber service options, and policy management mechanisms.

ISW network requirements may address lower cost alternatives for Internet traffic offload via WiFi, service continuity between cellular and WiFi, simplified network deployment and management (e.g., via consolidation of cellular and WiFi provisioning mechanisms and self-organizing network (SON) extensions), and enhanced policy-based multi-access traffic management (e.g., via dynamic traffic steering and local enforcement of quality of service (QoS) across cellular and WiFi access technologies).

Disclosed herein are solutions for MNO control of WLAN QoS via Extensible Authentication Protocol (EAP) and Diameter messages. If MNOs deploy carrier WiFi, there may be a desire for access points (APs) and subscriber handsets to support at least some <NUM>. 11e or WiFi Alliance (WFA) Wireless Multimedia (WMM) QoS features so that the MNOs can offer value-added services via different levels of QoS over WiFi. For uplink data (WiFi transmission from the UE) a mechanism can be defined for providing operator-specified QoS policies to the user equipment (UE) directly from a 3GPP AAA server. The UE may also use these MNO policies to request a specified QoS level for specific downlink traffic streams from a wireless local area network (WLAN) AP.

To give further context, discussed below are relevant WiFi standards for WLANs QoS and WLANs as associated with 3GPP. 3GPP has specified control mechanisms for various levels of QoS over the cellular access and core network. As detailed herein, these capabilities are extended to include differentiation of WLAN QoS based on MNO requirements as may be similarly applied to cellular access networks.

WiFi may be used for inexpensive delivery of MNO value-added packet data services, including mobile session continuity, via unlicensed spectrum. Adjustments may be made for delivering better QoS for offloaded WiFi traffic depending on how and where the offload is done. For instance, WLANs may support QoS differentiation using the WMM standards based on IEEE <NUM>. IEEE <NUM>. 11e refers to Amendment <NUM>: Medium Access Control (MAC) Quality of Service Enhancements. Applications using the WMM APIs can prioritize <NUM>. 11e MAC frames according to user priorities (UPs) mapped to access categories (ACs) for voice, video, best effort, or background. The four AC queues allow higher priority frames to be transmitted with a statistically lower wait time than lower priority frames.

<FIG> illustrates a simplified architecture for a Trusted WLAN access network (TWAN) connected with an EPC. Further details regarding the TWAN are discussed with regard to <FIG>. According to section <NUM>. <NUM> of TS <NUM>, when the WLAN is considered trusted by the operator, TWAN <NUM> interfaces with EPC <NUM> in multiple ways. TWAN <NUM> may interface with EPC <NUM> via STa interface <NUM> for authentication procedures with 3GPP AAA server <NUM>. STa interface <NUM> securely transports access authentication, authorization, mobility parameters and charging-related information. In addition, TWAN <NUM> may interface with EPC <NUM> via S2a interface <NUM> for bearer management procedures with packet data network (PDN) gateway (PGW) <NUM>. ANDSF server <NUM> may be located in EPC <NUM> and communicate with UE <NUM> via communicatively connected PGW <NUM>. ANDSF server <NUM> may communicate to UE <NUM> using an s14 interface <NUM>. ANDSF server <NUM> may initiate a push to distribute its information to UE <NUM> or UE <NUM> may query ANDSF server <NUM> to pull desired information.

TS <NUM> considers the detailed functional split within TWAN <NUM> as out of scope for 3GPP. The external behavior exposed by the SWw interface <NUM>, S2a interface <NUM>, and STa interface <NUM> are considered in scope for 3GPP. Nevertheless, functions such as WLAN AN <NUM>, Trusted WLAN Access Gateway (TWAG) <NUM>, and Trusted WLAN AAA Proxy (TWAP) <NUM> are assumed in scope of TWAN <NUM>. WLAN AN <NUM> consists of one or more WLAN Access Points (APs). An AP terminates the UE's WLAN IEEE <NUM> link via SWw interface <NUM>. These could be standalone APs or APs connected to a Wireless LAN Controller (WLC), e.g., using IETF CAPWAP/DTLS protocols.

TWAG <NUM> acts as the default IP router for UE <NUM> on its access link and terminates the GTP-based S2a interface <NUM> with the PGW <NUM>. It also acts as a DHCP server for UE <NUM>. TWAG <NUM> maintains a UE MAC address association for forwarding packets between UE <NUM> and TWAG <NUM> via a point-to-point link through the AP (not shown) in WLAN <NUM> and the S2a GTP-u tunnel for UE <NUM> toward PGW <NUM>. The implementation of the point-to-point link, including how and when it is setup, is out-of-scope of 3GPP (e.g., WiFi procedures are defined by the WiFi Alliance and IEEE <NUM>, while WiFi network discovery and selection decisions are based on UE implementation).

TWAP <NUM> terminates the Diameter-based STa interface <NUM> with 3GPP AAA Server <NUM>. Diameter refers to the IETF authentication, authorization, and accounting protocol. TWAP <NUM> relays the AAA information between WLAN AN <NUM> and 3GPP AAA Server <NUM> (or Proxy in case of roaming). TWAP <NUM> establishes the binding of UE <NUM> subscription data including international mobile subscriber identity (IMSI) with UE <NUM> MAC address and can inform TWAG <NUM> of layer <NUM> attach and detach events. There may be an analogy drawn to 3GPP "attach" which can be viewed as an "authentication" procedure with the core network. TWAP <NUM> may also provide TWAG <NUM> with subscription information for UE <NUM>, such as IMSI or MAC bindings.

The 3GPP Release <NUM> SA2 work item for "S2a Mobility Over GTP" (SaMOG) has focused on enabling a GPRS tunneling protocol (GTP)-based S2a interface between PGW <NUM> and TWAN <NUM>. The 3GPP Release <NUM> architectures, functional descriptions, and procedures for GTP-based S2a over Trusted WLAN access were standardized in section <NUM> of TS <NUM>. The applicable GTP control plane protocol for tunnel management (GTPv2-C) is specified in TS <NUM> and the GTP user plane is specified in TS <NUM>. A focus of SaMOG is "trusted access to the EPC," hence, the procedures begin with an "initial attachment" to EPC <NUM>. Just as in LTE, successful completion of the initial attach procedure results in establishment of a "default" EPC <NUM> bearer enabling an "always-on" connection with the core network via a GTP tunnel on S2a interface <NUM>. For SaMOG, direct offload to the Internet <NUM> is not relevant, because in the situation of direct offload to the Internet <NUM> the user plane connection to EPC <NUM> is bypassed and no GTP tunnels are established. Home subscriber server (HSS) <NUM> or 3GPP AAA server <NUM> may indicate via STa interface <NUM> whether access to EPC <NUM> via S2a interface <NUM> or the use of non-seamless WLAN offload (NSWO) or both are allowed for a subscriber.

UE <NUM> initiates an "initial attach" with TWAN <NUM> using "TWAN-specific L2 procedures" that are outside the scope of 3GPP. For WLAN, this would be via IEEE <NUM> procedures followed by the IETF EAPoL-Start message that initiates EAP procedures with the 3GPP AAA server <NUM> through TWAP <NUM>. By comparison, initiation of an "initial attach" for 3GPP access is done via establishment of an RRC connection with an evolved node B (eNB) followed by 3GPP-specified nonaccess stratum (NAS) signaling with a mobility management entity (MME).

After standard EAP-based authentication, TWAP <NUM> provides TWAG <NUM> with the default access point name (APN) retrieved from HSS subscription data via 3GPP AAA server <NUM>. TWAG <NUM> then selects PGW <NUM> associated with the APN and sends a GTP-C "Create Session Request" to PGW <NUM>. This request identifies the RAT type as "Non-3GPP" and includes the Default EPS Bearer QoS (as passed down from HSS <NUM>) and a GTP Tunnel Endpoint Identifier (TEID) for TWAN <NUM>. Note that this QoS is applicable to the GTP tunnel between the TWAG <NUM> and PGW <NUM> (S2a interface <NUM>) - not to the actual end-to-end EPS bearer which includes the WiFi link, where the WLAN radio interface is considered out of scope for 3GPP. The default bearer QoS includes a QoS Class Identifier (QCI) for a non-guaranteed bit rate (non-GBR). The QCI value represents a resource type (GBR or non-GBR), priority level, packet delay budget, and packet error loss rate, as shown in Table <NUM> which reflects information from Table <NUM>, pg. <NUM> of "Next Generation Mobile Communications Ecosystem: Technology Management for Mobile Communications by Saad Z.

PGW <NUM> returns a "Create Session Response" to TWAG <NUM> including the default EPS Bearer QoS, the allocated UE <NUM> IP address, and a TEID for PGW <NUM>. A GTP-U tunnel now exists between TWAG <NUM> and PGW <NUM>. Packets for this EPS bearer are subsequently encapsulated with a GTPv1-U header containing the destination TEID, a UDP header identifying GTPv1-U port number <NUM>, and an "outer IP" header marked with DSCP values corresponding to the QCI. The DSCP mappings are established based on operator policies.

PGW <NUM> may also initiate creation of dedicated bearers on the GTP-based S2a interface. TWAN <NUM> specific resource allocation/modification procedure may be executed in this step in order to support the dedicated bearer QoS. The details of this step are out of the scope of 3GPP.

PGW <NUM> may also initiate a bearer modification procedure for a GTP-based S2a bearer. This procedure is used to update the TFT for an active default or dedicated S2a bearer, or in cases when one or several of the S2a bearer QoS parameters QCI, GBR, MBR or ARP are modified (including the QCI or the ARP of the default S2a bearer), e.g. due to the HSS Initiated Subscribed QoS Modification procedure.

The IPv4 address and/or IPv6 prefix is allocated to UE <NUM> when a new PDN connection is established. For instance, TWAG <NUM> may request an IPv4 address in the GTP Create Session Request and the IPv4 address is delivered to TWAG <NUM> during the GTP tunnel establishment via the GTP Create Session Response from PGW <NUM>. When UE <NUM> requests the IPv4 address via DHCPv4, TWAG <NUM> delivers the received IPv4 address, subnet mask, default route, DNS server name, etc., to UE <NUM> within DHCPv4 signaling. UE <NUM> can use the subnet mask and the default gateway address for its packet routing decisions. Corresponding procedures are also defined for IPv6. For the case of NSWO, it is assumed TWAN <NUM> can support a network address translation (NAT) function and can provide the UE with a local IP address.

For Trusted WLAN access to EPC <NUM>, the PDN connectivity service is provided by the point-to-point connectivity between UE <NUM> and TWAN <NUM> concatenated with S2a bearer(s) between TWAN <NUM> and PGW <NUM>.

The S2a bearers include a default bearer as a minimum. When the default bearer is modified and/or when dedicated bearers are established, TFTs containing packet filters are also provided. TWAN <NUM> handles uplink packets based on the uplink packet filters in the TFTs received from PGW <NUM> for the S2a bearers of the PDN connection. Downlink packets are handled by PGW <NUM> based on downlink packet filters in the TFTs stored in PGW <NUM> for the S2a bearers of the PDN connection.

IEEE <NUM>. 11e has standardized two mechanisms for providing QoS enhancements in WLANs, namely, EDCA and HCCA. Subsequently, the WiFi Alliance has adopted some features of the <NUM>. 11e EDCA standard into their Wireless MultiMedia (WMM) certification program. The use of these standards have been limited, mostly focused on vendor-specific enterprise deployments (e.g., for voice over WLAN). It has not typically been used for interworking with 3GPP MNO QoS policies.

IEEE <NUM>. 11e includes MAC capabilities for QoS prioritization in WLANs where transmission opportunities (TXOPs) are determined based on traffic priority. Mechanisms have been standardized using a hybrid coordination function (HCF) in the AP. The HCF may be described as a "hybrid" function because it supports both <NUM>) contention-based channel access (enhanced distributed channel access - EDCA), and <NUM>) controlled channel access (HCF controlled channel access - HCCA). EDCA is a prioritized CSMA/CA contention-based access mechanism. EDCA maps user priorities (UP) to four "access categories" (ACs) allowing higher priority frames to be transmitted with a statistically lower wait time than lower priority frames. The backoff value for each AC is broadcast by the QoS-enabled AP in the beacon frames for use by stations in uplink transmissions. HCF Controlled Channel Access (HCCA) is a contention-free access mechanism based on AP polling mechanisms. Although this can theoretically reduce contention on the medium, in reality there can still be uncontrollable interference from overlapping service areas.

The EDCA mechanism provides differentiated, distributed access by mapping eight different user priorities (UPs) to four access categories (ACs). The AC is derived from the UPs as shown below in Table <NUM>, which reflects information from Table <NUM>-<NUM> of IEEE Std <NUM>™-<NUM>.

The UP values are in the range of <NUM>-<NUM>, the same as the values defined for <NUM>. 1D user priorities (thereby simplifying the mapping). These user priorities were established for layer <NUM> data link frame prioritization in alignment with earlier class of service (CoS) standards including <NUM>. 1D (based on work done in <NUM>. 1D designations are listed as follows: BK = Background, BE = Best Effort, EE = Excellent Effort, CL = Controlled Load, VI = Video (<<NUM> delay), VO = Voice (<<NUM> delay), and NC = Network Control. User priority <NUM> is placed into the Best Effort AC instead of the Background AC to preserve backward compatibility with non-QoS stations since the IEEE considers QoS functionality optional.

The WiFi Alliance (WFA) defined its WiFi MultiMedia (WMM) certification program called WMM-Admission Control (WMM-AC) to ensure that devices requiring QoS (e.g., for VoIP) are only admitted into the network if sufficient resources are available. For example, a WMM client can include a "Traffic Specification" (TSPEC) in a signaling request to the AP before sending traffic flows of a specific AC type, such as voice.

IEEE <NUM>. 11u has defined standards for "Interworking with External Networks" such as those managed by 3GPP MNOs. 11u amendment describes methods for WLAN network discovery and selection, QoS mapping from external networks, and prioritized WLAN access for emergency services (e.g., for first responders). The WiFi Alliance has adopted some features of <NUM>. 11u network discovery and selection into their Hotspot <NUM> "Passpoint" certification program and the <NUM>. 11u QoS enhancements may be addressed in future Passpoint releases.

With respect to QoS mapping, <NUM>. 11u provides QoS mapping for subscription service provider networks (SSPNs) and other external networks that may have their own layer-<NUM> end-to-end packet marking practice (e.g., differentiated services code point (DSCP) usage conventions). Therefore, a way to remap the layer-<NUM> service levels to a common over-the-air service level is necessary. The QoS map provides stations and access points with a mapping of network-layer QoS packet marking (e.g., DSCP) to <NUM>.

For the downlink, at the AP, DSCP values are mapped to EDCA UPs. The non-AP station <NUM> (STA) may also use TSPEC and TCLAS elements in an add traffic stream (ADDTS) request frame to setup a traffic stream in the WLAN. In this method, the UP is specified in the traffic classification (TCLAS) element. The policy used by the AP to choose a specific method to map frames to user priorities is outside the scope of <NUM>.

For the uplink, at the non-AP STA, external QoS parameters are mapped to IEEE <NUM> QoS parameters, e.g., DSCP to IEEE <NUM> UP and in turn to EDCA ACs. This mapping helps the non-AP STA to construct correct QoS requests to the AP, e.g., ADDTS Request, and to transmit frames at the correct priority. Standards do not specify how a UE sets the DSCP value for uplink packets, if at all. UE <NUM> may, for instance, use the value received in the corresponding downlink packet for the corresponding flow.

Table <NUM>, which reflects information from IEEE Std <NUM>™-<NUM> Table V-<NUM>, shows examples of differentiated services (DiffServ) per hop behavior (PHB) and DSCP mappings for 3GPP UMTS/GPRS traffic classes and <NUM>. 11e AC and UP. The mapping of the DSCP to 3GPP UMTS/GPRS traffic class is available in Global System for Mobile Association (GSMA) IR. <NUM>, while IR. <NUM> adds the Evolved Packet System (EPS) QoS Class Identifier (QCI) mappings.

Table <NUM> may be constructed for EPC-based networks and reflects information from GSMA IR.

IETF draft-kaippallimalil-netext-pmip-qos-wifi-<NUM>, "Mapping PMIP Quality of Service in WiFi Network," outlines a recommended mapping between 3GPP QCI, DSCP, and <NUM>. 11e Access Category (AC) as shown below in Table <NUM>.

Although the WFA has adopted portions of <NUM>. 11u for network discovery and selection as part of the Hotspot <NUM> initiative and its corresponding Passpoint certification program, the QoS mapping standards have not been included to date. Hotspot <NUM> refers to an approach to public access Wi-Fi by the WFA allowing devices to automatically join a Wi-Fi subscriber service.

Given the current gaps of the conventional QoS techniques as eluded to above, there may be a need for adjustments that enable greater adoption of WLAN QoS controls, especially in light of the increased deployment of integrated small cell and WiFi networks. Defined below are extensions to EAP and Diameter for conveying uplink "WLAN QoS" parameters (e.g., QoS parameters for WiFi) to be applied by the UE. As further described below, EAP and Diameter messages may further be extended such that the messages may be interpreted by the TWAN enroute between the UE and 3GPP AAA server, thereby allowing the TWAN to set corresponding QoS for downlink traffic to the UE. Referring generally to <FIG> and <FIG>, for offloaded or EPC-routed traffic, the 3GPP AAA server <NUM> may provide the UE <NUM> with uplink <NUM>. 11e user priority (UP) preferences via extended EAP signaling based on HSS <NUM> subscription information. The TWAN <NUM> may also set the downlink <NUM>. 11e UP based on information from the extended EAP and Diameter messages.

In an example embodiment, QoS levels are globally configured in the TWAN <NUM>(e.g., see <FIG>). In another example embodiment, QoS levels are defined per subscriber based on information stored in the HSS <NUM> (e.g., see <FIG>).

For example, a "WLAN QoS" attribute may be implemented in an EAP-AKA' protocol. As stated in Solution <NUM> of 3GPP TR <NUM>, which is incorporated by reference as if the disclosure of which is set forth in its entirety herein: "Between the UE and the TWAN/Authenticator, the new information is sent via EAPoL (IEEE <NUM>. Between the TWAN/Authenticator and the 3GPP AAA Server, the EAP-AKA' payload is transported within Diameter messages. The principle is that the TWAN can read the parameters sent by the UE from the EAP messages, but cannot modify them, i.e., EAP messages are integrity protected, but not encrypted. When the TWAN needs to send a parameter to the UE, it does so indirectly by inserting the parameter in the Diameter message to the 3GPP AAA Server. Then the 3GPP AAA Server relays the parameter in the subsequent EAP message to the UE.

Referring in particular to <FIG>, an example system <NUM> includes the UE <NUM>, the TWAN <NUM>, the 3GPP AAA server <NUM>, and the HSS <NUM>. It will be appreciated that the example system <NUM> is simplified to facilitate description of the disclosed subject matter and is not intended to limit the scope of this disclosure. Other devices, systems, and configurations may be used to implement the embodiments disclosed herein in addition to, or instead of, a system instead of the system <NUM>, and all such embodiments are contemplated as within the scope of the present disclosure.

Referring to <FIG>, in accordance with the illustrated embodiment, at <NUM>, the UE <NUM> may store uplink (UL) WiFi QoS policies. At <NUM>, the TWAN <NUM> may store uplink and downlink (DL) WiFi QoS policies. The QoS policies, which may include parameters or attributes, may be statically configured in the TWAN <NUM> and be subsequently updated via an OAM server (not shown). At <NUM>, the UE <NUM> may attach to the TWAN <NUM> via an <NUM> communication. At <NUM>, the UE <NUM>, TWAN <NUM>, 3GPP AAA server <NUM>, and HSS <NUM> may go through a process of authentication onto a network. Thus, the UE <NUM> may be authenticated at <NUM>. At <NUM>, the TWAN <NUM> may send an EAP over LAN (EAPoL) message to the UE <NUM>. The message may include an EAP request. At <NUM>, the UE <NUM> may send an EAP response to the TWAN <NUM>. In accordance with the illustrated embodiment, at <NUM>, the TWAN <NUM>, inserts one or more TWAN UL QoS parameters in a Diameter message. The one or more QoS parameters may be subsequently sent to the UE <NUM> in an extended EAP message. At <NUM>, the diameter message that includes the one or more QoS parameters is sent to the 3GPP AAA server <NUM>. The diameter message may include an AVP ("Attribute Value Pair") parameter that conveys the TWAN QoS parameters as described herein.

Still referring to <FIG>, in accordance with the illustrated example, at <NUM>, the 3GPP AAA server <NUM> relays the TWAN UL QoS parameters to the UE <NUM> in an extended EAP message. For example, at <NUM>, the 3GPP AAA server <NUM> may send an extended diameter message to the TWAN <NUM> that includes the TWAN QoS parameters. Thus, the TWAN <NUM>, which also be referred to as a first or TWAN server <NUM>, may receive a message that indicates a WLAN QoS parameter. The message may be formatted in accordance with a diameter message. At <NUM>, the TWAN <NUM> can send an EAPoL message, in particular an EAP request message, to the UE <NUM> that includes the TWAN QoS parameters. Thus, the TWAN <NUM> may insert the WLAN QoS parameter into an extended extensible authentication protocol (EAP) message, thereby providing a QoS policy specified by the MNO to the UE <NUM>. In accordance with the illustrated example, the QoS policy is a global policy that applies to a plurality of user equipment's in the TWAN <NUM>. In response to the request, the UE <NUM> may send an EAP response message to the TWAN <NUM>, at <NUM>. At <NUM>, the UE <NUM>, TWAN <NUM>, and 3GPP AAA server may perform an EAP notification. At <NUM>, in accordance with the illustrated example, a diameter message, in particular an EAP success message, is sent to the TWAN <NUM> from the 3GPP AAA server <NUM>. At <NUM>, an EAPoL message, in particular the EAP success message, is sent to the UE <NUM> from the TWAN <NUM>. At <NUM>, the UE <NUM> may set an UL <NUM>. 11e MAC marking per the QoS mapping. Thus, the UE <NUM> may set a user priority for WLAN uplink traffic flows according to the WLAN Qos policy. Thereafter, the UE <NUM> may provide data to the TWAN <NUM> based on the WLAN QoS policy. Similarly, at <NUM>, the TWAN <NUM> may set a DL <NUM>. 11e MAC marking per the QoS mapping. Thus, the TWAN <NUM> may set a user priority for WLAN downlink traffic flows in accordance with the WLAN QoS policy. Thereafter, the TWAN <NUM> may provide data to the UE <NUM> in accordance with the WLAN QoS policy. The HSS <NUM> may store QoS policies specified by the MNO.

As discussed herein, it should be understood that the entities performing the steps illustrated in <FIG> are logical entities that may be implemented in the form of software (e.g., computer-executable instructions) stored in a memory of, and executing on a processor of, a device, server, or computer system such as those illustrated in <FIG> or <FIG>. That is, the method(s) illustrated in <FIG> may be implemented in the form of software (e.g., computer-executable instructions) stored in a memory of a computing device, such as the device or computer system illustrated in <FIG> or <FIG>, which computer executable instructions, when executed by a processor of the computing device, perform the steps illustrated in <FIG>.

Referring now to <FIG>, an example system <NUM> includes the UE <NUM>, the TWAN <NUM>, the 3GPP AAA server <NUM>, the HSS <NUM>, the PGW <NUM>, and an policy and charging rules function (PCRF) <NUM>. It will be appreciated that the example system <NUM> is simplified to facilitate description of the disclosed subject matter and is not intended to limit the scope of this disclosure. Other devices, systems, and configurations may be used to implement the embodiments disclosed herein in addition to, or instead of, a system instead of the system <NUM>, and all such embodiments are contemplated as within the scope of the present disclosure. In accordance with the illustrated embodiment, the 3GPP AAA Server <NUM> may signal the QoS preference to the TWAN <NUM> based on the subscriber-specific WiFi QoS information provided by the HSS <NUM>. As further described below with reference to <FIG>, subscriber-specific QoS parameters may be stored in the HSS <NUM>, conveyed to the 3GPP AAA Server <NUM>, and sent to the UE <NUM> via the 3GPP AAA Server <NUM> using extensions to the EAP protocol as described herein. Further, the parameters, and thus the messages, may be monitored by the TWAN <NUM> enroute to the UE <NUM>.

Referring in particular to <FIG>, at <NUM>, in accordance with an example embodiment, the UE <NUM> may attach to the TWAN <NUM> via an <NUM> communication. At <NUM>, the UE <NUM> may send an EAPoL start message to the TWAN <NUM>. In response, at <NUM>, an authentication may be initiated. At <NUM>, the 3GPP AAA server <NUM> may indicate a preference for a non-seamless WLAN offload (NSWO). The NSWO preference may be based on a WLAN QoS policy for a subscriber and/or a flow WLAN QoS policy. At <NUM>, the 3GPP AAA Server <NUM> sends an AKA' notification to the UE <NUM>. The notification may include, and thus may indicate, the preference for NSWO, which may be per a subscriber WLAN QoS and/or a flow WLAN QoS. At <NUM>, in accordance with the illustrated embodiment, the TWAN <NUM>, and in particular a signaling sniffer of the TWAN <NUM>, sniffs (interprets) EAP signaling and stores relevant subscription information at the TWAN <NUM>. For example, TWAN <NUM> may monitor EAP messages between the UE <NUM> and the 3GPP AAA server <NUM>, which may also be referred to as a second server. Example subscription information includes, without limitation, an NSWO preference and a WLAN QoS policy. The Signaling Sniffer may be implemented as a separate logical function while being implemented as part of the TWAN <NUM>. At <NUM>, the authentication, for instance the authentication of the UE <NUM>, concludes.

Referring now to <FIG>, in accordance with an alternative embodiment, at <NUM>, the UE <NUM> may send an EAPoL start message to the TWAN <NUM>. In response, the TWAN <NUM> may send an EAPoL request message to the UE <NUM> (at <NUM>). At <NUM>, the UE <NUM> may send an EAPoL response message to the TWAN <NUM>. At <NUM>, the TWAN <NUM> may send a diameter message to the 3GPP AAA Server. The diameter message may include the identity of the UE <NUM> associated with the EAP response and an identity of the access network. Thus, the TWAN <NUM> may send a diameter message to the 3GPP AAA server <NUM>, and the diameter message may be indicative of an identity of the UE <NUM>. At <NUM>, the 3GPP AAA server <NUM> requests information from the HSS <NUM>. For example, the information may include a WLAN QoS policy that is specific to the UE <NUM> based on subscriber information associated with the UE <NUM>. Alternatively, the 3GPP AAA server <NUM> may provide previously stored preferences, for instance during an example fast re-authentication, for NSWO. The information may include the QoS policy, which may be based on the subscriber (e.g., a user of the UE <NUM> and/or the UE <NUM> itself) or the flow, for example. At <NUM>, the 3GPP AAA server <NUM> sends a diameter message to the TWAN <NUM>. The message may include the retrieved and/or stored information from <NUM>. At <NUM>, in accordance with the illustrated example, the TWAN <NUM> sniffs the EAP signaling and stores relevant subscription information in the TWAN <NUM>. Thus, the TWAN <NUM> may monitor EAP messages between the UE <NUM> and the 3GPP AAA server <NUM>. Based on the monitored EAP messages and the identity of the UE <NUM>, the TWAN <NUM> may identify a WLAN QoS policy associated with the UE <NUM>. Example subscription information may include, without limitation, the NSWO preference and the WLAN QoS policy, which may be specific to the UE <NUM> based on subscriber information associated with the UE. At <NUM>, the TWAN <NUM> may send an EAPoL request message to the UE <NUM>. The message may include the identified WLAN QoS policy. Thus, the TWAN <NUM> may send the identified WLAN QoS policy to the UE <NUM>, for instance via an EAP message. The QoS policy may be retrieved via the HSS <NUM>. The UE <NUM> may send an EAPoL response message to the TWAN <NUM>, at <NUM>. At <NUM>, the TWAN <NUM> may send a diameter message that includes the EAP response to the 3GPP AAA server <NUM>. At <NUM>, the 3GPP AAA server <NUM> may send a diameter message that includes an EAP success message to the TWAN <NUM>. At <NUM>, the TWAN <NUM> may relay the EAP success message in an EAPoL message that is sent to the UE <NUM>.

Referring now to <FIG>, in accordance with another alternative embodiment, at <NUM>, the UE <NUM> may send an EAPoL start message to the TWAN <NUM>. In response, the TWAN <NUM> may send an EAPoL request message to the UE <NUM> (at <NUM>). At <NUM>, the UE <NUM> may send an EAPoL response message to the TWAN <NUM>. At <NUM>, the TWAN <NUM> may send a diameter message to the 3GPP AAA Server <NUM>. The diameter message may include an EAP request message that may include subscription data. At <NUM>, the TWAN <NUM> may send an EAPoL request message to the UE <NUM>. The UE <NUM> may send an EAPoL response message to the TWAN <NUM>, at <NUM>. At <NUM>, the TWAN <NUM> may send a diameter message that includes the EAP response to the 3GPP AAA server <NUM>. At <NUM>, in accordance with the illustrated example, the 3GPP AAA server <NUM> requests (retrieves) information from the HSS <NUM> if the information was not previously stored. At <NUM>, the 3GPP AAA server <NUM> sends a diameter message to the TWAN <NUM>. The message may include the retrieved information from <NUM>. The retrieved information may include, presented by way of example, subscription information, the APN identity, and the WLAN QoS, which may be subscriber based and/or flow based. At <NUM>, the TWAN <NUM> retrieves subscription data from the received diameter message, and in particular the new diameter AVP. The TWAN <NUM> may store relevant WLAN QoS subscription information in the TWAN <NUM>. At <NUM>, the TWAN <NUM> may send an EAPoL request message to the UE <NUM>. The EAPoL request message may include the WLAN QoS policy, which may be subscriber based and/or flow based. For example, in some cases, the WLAN QoS policy is specific to the UE <NUM>. Thus, the TWAN <NUM> may also set a user priority for WLAN downlink traffic flows destined for the UE <NUM> in accordance with the WLAN QoS policy. The UE <NUM> may send an EAPoL response message to the TWAN <NUM>, at <NUM>. At <NUM>, the TWAN <NUM> may send a diameter message that includes the EAP response to the 3GPP AAA server <NUM>. At <NUM>, the 3GPP AAA server <NUM> may send a diameter message that includes an EAP success message to the TWAN <NUM>. At <NUM>, the TWAN <NUM> may relay the EAP success message in an EAPoL message that is sent to the UE <NUM>. Thus, the UE <NUM> may be authenticated with a server that is controlled by an MNO. Based on the authentication, the UE <NUM> may receive a message that indicates a WLAN QoS policy. In various example embodiments, the message is formatted in accordance with an extended EAP message.

Referring now to <FIG>, after any of the authentications described above, a default bearer may be established between the TWAN <NUM> and the HSS <NUM>, at <NUM>. Alternatively, at <NUM>, a dedicated bearer may be established between the TWAN <NUM> and the HSS <NUM>. At <NUM>, the UE <NUM> may set the UL <NUM>. 11e MAC marking per the QoS mapping. Thus, the UE <NUM> may set a user priority for WLAN uplink traffic flows according to the WLAN QoS policy specified by the MNO. The UE <NUM> may thus provide data to the TWAN <NUM> based on the WLAN QoS policy. At <NUM>, the TWAN <NUM> may set the DL <NUM>. 11e MAC marking per the QoS mapping. Thus, the TWAN <NUM> may set a user priority for WLAN downlink traffic flows destined for the UE <NUM> in accordance with the WLAN QoS policy. The TWAN <NUM> may further provide data to the UE <NUM> in accordance with the WLAN QoS policy that may be specified by the MNO.

Thus, as described above, the TWAN <NUM> may include a signaling sniffer that reads the subscriber-specific "WLAN QoS" Diameter extensions provided to the TWAN <NUM> by the 3GPP AAA Server <NUM>, sniffs the subscriber-specific "WLAN QoS" EAP extensions provided to the UE <NUM> by the 3GPP AAA Server <NUM>, and/or provides the "WLAN QoS" and associated subscription information to the WiFi QoS Policy Manager.

Further, for downlink data over the SWw air interface, the TWAN <NUM> may set the <NUM>. 11e UP for traffic flows based on pre-configured values or based on an inspection of HSS subscriber info conveyed via the 3GPP AAA server <NUM> using extended EAP/Diameter signaling. Pre-configured policies may be used for handling the differentiation of downlink flows. For example, referring to <FIG>, global flow-based policies match configured packet filters. In accordance with the description relative to <FIG>, using EAP/Diameter with the described "WLAN QoS" extensions, the downlink traffic that is handled is tailored using the WLAN QoS information stored for the user in the HSS <NUM>.

In an example embodiment for uplink data over the SWw air interface, the UE <NUM> sets the <NUM>. 11e UP for traffic flows according to a pre-configured operator policy or as signaled by the new mechanisms described above. Pre-configured policies may be used for handling the differentiation of uplink flows, e.g., via flow-based policies matching specified packet filters. Using EAP with the described "WLAN QoS" extension, the uplink traffic handling may be tailored using the WLAN QoS information stored for the user in the HSS <NUM>.

Referring again to <FIG>, in some cases, dedicated bearers may be associated with a default PDN connection and may exhibit specific QoS requirements that cannot be adequately handled by the default connection. Packets belonging to the dedicated bearer may be distinguished via packet filters comprising a Traffic Flow Template (TFT). In the TWAN <NUM>, the TFTs may be provided via GTP signaling from the PGW <NUM> and may be used to route uplink packets from the TWAN <NUM> to the PGW <NUM> via the associated dedicated bearer. The PGW <NUM> may use its TFTs to route downlink packets to the TWAN <NUM> via the associated dedicated bearer.

As discussed herein, it should be understood that the entities performing the steps illustrated in <FIG> are logical entities that may be implemented in the form of software (e.g., computer-executable instructions) stored in a memory of, and executing on a processor of, a device, server, or computer system such as those illustrated in <FIG> and <FIG>. That is, the method(s) illustrated in <FIG> may be implemented in the form of software (e.g., computer-executable instructions) stored in a memory of a computing device, such as the device or computer system illustrated in <FIG> or <FIG>, which computer executable instructions, when executed by a processor of the computing device, perform the steps illustrated in <FIG>.

Disclosed below are more details with regard to 3GPP architecture that provides cellular LTE and Trusted WLAN access to an EPC. Under current practices, mobile network operators (MNOs) typically employ WiFi for offloading "best effort" Internet traffic from their cellular and core networks. However, increased interest in operator deployment of "small cells" and "carrier WiFi" is expected to encourage MNOs to seek better inter-operability across local cellular and WiFi networks. Generally, "small cells" refer to localized geographic areas providing wireless network access via operator-licensed spectrum using 3GPP-defined cellular Radio Access Technologies (RATs). Although offloaded traffic is discussed herein, it is contemplated that devices that may primarily use WiFi communication may practice the WLAN QoS via EAP/Diameter as disclosed herein.

As operators adopt "carrier WiFi" to optimize their networks and reduce expenses, it is expected that there will be a greater deployment of "Trusted" WLAN Access Networks (TWAN) that can interface directly with an operator's Mobile Core Network (MCN). Similarly, it is expected that there will be greater integration of MNO deployed small cell and WiFi access networks within common geographical areas such as high-traffic urban metropolitan hotspot locations. Such integration is motivated by the growing number of smartphones that support both cellular and WiFi access.

In this context, the term "trusted WLAN (TWAN) access" refers to the circumstances wherein appropriate measures have been taken to safeguard the EPC from access via the WLAN. Such measures are left to the discretion of the MNO and may, for example, include establishment of a tamperproof fiber connection between the WLAN and EPC, or establishment of an IPSec security association between the WLAN and a Security Gateway at the EPC edge. In contrast, if the WLAN access is deemed "untrusted," the WLAN may interface with an evolved Packet Data Gateway (ePDG) at the EPC edge, and the ePDG must establish an IPSec security association directly with each UE accessing the EPC through the WLAN.

<FIG> is a diagram of an example communication system <NUM> in which one or more disclosed embodiments may be implemented. <FIG> depicts a 3GPP architecture that provides cellular LTE and Trusted WLAN access to EPC <NUM>. As described in section <NUM>. <NUM> of 3GPP Technical Specification (TS) <NUM>, the contents of which are hereby incorporated herein by reference, when WLAN AN <NUM> is considered trusted by the operator, the Trusted WLAN Access Network (TWAN) <NUM> can be connected to Evolved Packet Core (EPC) <NUM> via the STa interface <NUM> toward the 3GPP AAA Server <NUM> for authentication, authorization, and accounting via the S2a interface <NUM> toward PDN Gateway (PGW) <NUM> for user plane traffic flows. An alternate path from TWAN <NUM> to a local IP network <NUM> (i.e., intranet) and/or directly to the Internet <NUM> is also shown.

3GPP LTE access network <NUM> (i.e., evolved Node B) is connected to EPC <NUM> via S1-MME interface <NUM> which provides a communication path with Mobility Management Entity (MME) <NUM>. S1-U interface <NUM> provides a communication path with Serving Gateway (SGW) <NUM>, which interfaces with PDN Gateway (PGW) <NUM> via S5 interface <NUM>.

A "local gateway" function (L-GW) <NUM> provides small cell LTE access, e.g., for Home eNB (HeNB) deployments. Similarly, a "HeNB Gateway" (HeNB GW) <NUM> may be used to concentrate control plane signaling for multiple HeNBs toward MME <NUM> and could also be used to handle HeNB user plane traffic toward SGW <NUM>. A HeNB Management System (HeMS) <NUM> provides "plug-and-play" auto configuration of HeNBs based on TR-<NUM> standards published by the broadband forum (BBF) and adopted by 3GPP. A security gateway (SeGW) <NUM> provides trusted access to EPC <NUM> via HeNB GW <NUM>.

WLAN AN <NUM> comprises one or more WLAN Access Points (APs). An AP (not shown) terminates UE <NUM> WLAN IEEE <NUM> link via SWw interface <NUM>. The APs may be deployed as standalone APs or as "thin" APs connected to a Wireless LAN Controller (WLC) using, for example, the IETF CAPWAP protocols.

TWAG <NUM> terminates the GTP-based S2a interface <NUM> with the PGW <NUM> and may act as the default IP router for UE <NUM> on its WLAN access link. It also may act as a DHCP server for UE <NUM>. TWAG <NUM> typically maintains a UE MAC address association for forwarding packets between UE <NUM> (via the WLAN AP) and the associated S2a interface <NUM> GTP-U tunnel (via the PGW <NUM>).

Trusted WLAN AAA Proxy (TWAP) <NUM> terminates the Diameter-based STa interface <NUM> with the 3GPP AAA Server <NUM>. TWAP <NUM> relays the AAA information between the WLAN AN <NUM> and 3GPP AAA Server <NUM> (or Proxy in case of roaming). TWAP <NUM> can inform TWAG <NUM> of the occurrence of layer <NUM> attach and detach events. TWAP <NUM> establishes the binding of UE subscription data (including IMSI) with UE MAC address and can provide such information to TWAG <NUM>.

In existing systems, UE <NUM> can leverage USIM features for both 3GPP and non-3GPP WLAN access. Processing for authentication and security is described in section <NUM>. <NUM> of 3GPP TS <NUM>, the contents of which are hereby incorporated by reference in their entirety. As described therein, non-3GPP access authentication, such as that which takes place via WLAN AN <NUM>, defines the process that is used for access control and thereby permits or denies a subscriber from attaching to and using the resources of a non-3GPP IP access which is interworked with the EPC <NUM>. Non-3GPP access authentication signaling is executed between UE <NUM> and the 3GPP AAA server <NUM> and HSS <NUM>. The authentication signaling may pass through AAA proxies.

Trusted 3GPP-based access authentication is executed across STa interface <NUM>. The 3GPP based access authentication signaling is based on IETF protocols, e.g., Extensible Authentication Protocol (EAP). STa interface <NUM> and Diameter application are used for authenticating and authorizing UE <NUM> for EPC <NUM> access via trusted non-3GPP accesses. 3GPP TS <NUM>, the contents of which are hereby incorporated by reference in its entirety, describes the standard TWAN procedures currently supported on STa interface <NUM>.

For EPC <NUM> access via GTP-based TWAN <NUM>, the IPv4 address and/or IPv6 prefix is allocated to UE <NUM> when a new PDN connection is established with EPC <NUM> over TWAN <NUM>. A separate IP address may also be allocated by the TWAN <NUM> for local network traffic and/or direct Internet offload.

For PDN connectivity through EPC <NUM> via TWAN <NUM>, TWAN <NUM> receives relevant PDN information via EAP/Diameter or WLCP signaling. TWAN <NUM> may request an IPv4 address for UE <NUM> from PGW <NUM> via the GTP Create Session Request. The IPv4 address is delivered to TWAN <NUM> during the GTP tunnel establishment via the GTP Create Session Response. When UE <NUM> requests an IPv4 address for PDN connectivity via DHCPv4, the TWAN <NUM> delivers the received IPv4 address to the UE <NUM> within DHCPv4 signaling. Corresponding procedures are also defined for IPv6.

For 3GPP LTE access, the UE <NUM> automatically triggers a PDN connection as part of its initial attachment to the EPC <NUM>. UE <NUM> may subsequently establish additional PDN connections as needed.

The primary purpose of the attach procedure is for UE <NUM> to register with the network in order to receive services for which it has subscribed to. The attach procedure confirms the user's identity, identifies the services it is allowed to receive, establishes the security parameters (e.g., for data encryption), and notifies the network of the UE <NUM> initial location (e.g., in case it needs to be paged). Also, to support the "always-on" network connectivity expected by today's users, the LTE standards specify establishment of a default PDN connection as part of the Attach procedure. The radio resources for this default connection may be released during periods of inactivity, however the rest of the connection remains intact and the end-to-end connection can be quickly re-established by reassigning the radio resources in response to UE <NUM> service requests.

When UE <NUM> attempts to attach to EPC <NUM> via an (H)eNB LTE network <NUM>, it first establishes an RRC connection with the (H)eNB LTE network <NUM> and encapsulates the Attach Request within the RRC signaling. (H)eNB LTE network <NUM> then forwards the attach request to MME <NUM> via S1-AP signaling on S1-MME interface <NUM>. MME <NUM> retrieves subscription information from HSS <NUM> via the S6a interface <NUM> in order to authenticate UE <NUM> and allow attachment to EPC <NUM>.

After successfully authenticating the UE <NUM>, MME <NUM> selects SGW <NUM> (e.g., based on proximity to the (H)eNB LTE network <NUM>), and also selects PGW <NUM> (e.g., based on the default APN retrieved from HSS <NUM> or a specific APN requested by UE <NUM>). MME <NUM> communicates with SGW <NUM> over S11 interface <NUM> and requests creation of the PDN connection. SGW <NUM> executes the signaling to establish a GTP user plane tunnel with the designated PGW <NUM> over the S5 interface <NUM>.

"GTP control" signaling takes place within the S1-AP protocol between the MME <NUM> and (H)eNB <NUM>. This ultimately leads to the establishment of a GTP user plane tunnel on the S1-U interface <NUM> between (H)eNB <NUM> and SGW <NUM>. The path for the PDN connection between the UE <NUM> and PGW <NUM> is thus completed through the (H)eNB <NUM> and SGW <NUM>.

The end-to-end path for the PDN connection between the UE <NUM> and PGW <NUM> is thus completed through (H)eNB <NUM> and SGW <NUM>.

In systems where communications take place via TWAN <NUM>, UE <NUM> authentication and EPC <NUM> attachment is accomplished via EAP signaling between UE <NUM> and 3GPP AAA Server <NUM>.

The PDN connectivity service is provided by the point-to-point connectivity between UE <NUM> and the TWAN <NUM>, concatenated with S2a bearer(s) <NUM> between TWAN <NUM> and PGW <NUM>. Unlike the LTE model, the WLAN radio resources are "always-on" from an EPC perspective. In other words, any power-saving optimizations are handled transparently using IEEE <NUM> procedures within the WLAN.

When UE <NUM> attempts to attach to EPC <NUM> via TWAN <NUM>, it first establishes a Layer <NUM> connection with the WLAN AN <NUM> and encapsulates EAP messages within EAPoL signaling. WLAN AN <NUM> forwards the EAP messages to TWAP <NUM> which encapsulates the messages within Diameter signaling and forwards the messages to 3GPP AAA Server <NUM> via the STa interface <NUM>. 3GPP AAA server <NUM> retrieves subscription information from the HSS <NUM> via the SWx interface <NUM> in order to authenticate UE <NUM> and allow attachment to EPC <NUM>.

For 3GPP Release <NUM>, 3GPP AAA Server <NUM> also provides TWAN <NUM> with information via STa interface <NUM> for establishing a PDN connection to the default PDN provisioned in the HSS <NUM>. TWAN <NUM> then exercises GTP control plane (GTP-C) and user plane (GTP-U) protocols over S2a interface <NUM> directly toward PGW <NUM>, thereby completing the PDN connection between UE <NUM> and PGW <NUM> through TWAN <NUM>.

For 3GPP Release <NUM>, the SaMOG phase-<NUM> work item defines additional procedures for UE-initiated PDN connectivity, multi-PDN connectivity, and seamless inter-system handover. For the case of single-PDN capable TWAN scenarios, EAP extensions are defined to support UE-initiated PDN requests and seamless inter-system handover requests. For the case of multi-PDN capable TWAN scenarios, a WLAN Control Protocol (WLCP) is defined between the UE and TWAN to enable one or more UE PDN connection requests and seamless handover procedures. However, separate procedures are still utilized between the UE and 3GPP AAA Server for UE authentication.

<FIG> is a system diagram of an example user equipment, such as UE <NUM>. Example user equipment (UE) includes, but is not limited to, a mobile station, a fixed or mobile subscriber unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, consumer electronics, wearable devices, or the like. As shown in <FIG>, UE <NUM> may include a processor <NUM>, a transceiver <NUM>, a transmit/receive element <NUM>, a speaker/microphone <NUM>, a keypad <NUM>, a display/touchpad <NUM>, non-removable memory <NUM>, removable memory <NUM>, a power source <NUM>, a global positioning system (GPS) chipset <NUM>, and other peripherals <NUM>. It will be appreciated that UE <NUM> may include any sub-combination of the foregoing elements while remaining consistent with an embodiment. UE <NUM> may be a device that uses the disclosed systems, devices, and methods for WLAN QoS via EAP/Diameter.

The processor <NUM> may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables the UE <NUM> to operate in a wireless environment. The processor <NUM> may perform application-layer programs (e.g., browsers) and/or radio access-layer (RAN) programs and/or communications. The processor <NUM> may perform security operations such as authentication, security key agreement, and/or cryptographic operations, such as at the access-layer and/or application layer for example.

The transmit/receive element <NUM> may be configured to transmit signals to, or receive signals from, WLAN AN <NUM> or (H)eNB <NUM>. For example, in an embodiment, the transmit/receive element <NUM> may be an antenna configured to transmit and/or receive RF signals. The transmit/receive element <NUM> may support various networks and air interfaces, such as WLAN, WPAN, cellular, and the like. It will be appreciated that the transmit/receive element <NUM> may be configured to transmit and/or receive any combination of wireless or wired signals.

In addition, although the transmit/receive element <NUM> is depicted in <FIG> as a single element, UE <NUM> may include any number of transmit/receive elements <NUM>. More specifically, the UE <NUM> may employ MIMO technology. Thus, in an embodiment, the UE <NUM> may include two or more transmit/receive elements <NUM> (e.g., multiple antennas) for transmitting and receiving wireless signals.

As noted above, UE <NUM> may have multi-mode capabilities. Thus, transceiver <NUM> may include multiple transceivers for enabling UE <NUM> to communicate via multiple RATs, such as UTRA and IEEE <NUM>, for example.

Processor <NUM> may access information from, and store data in, any type of suitable memory, such as non-removable memory <NUM> and/or removable memory <NUM>. Non-removable memory <NUM> may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. Removable memory <NUM> may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor <NUM> may access information from, and store data in, memory that is not physically located on UE <NUM>, such as on a server or a home computer. The processor <NUM> may be configured to control lighting patterns, images, or colors on the display or indicators <NUM> in response to whether the WLAN QoS via EAP/Diameter in some of the embodiments described herein are successful or unsuccessful, or otherwise indicate the status of QoS or the processes for implementing QoS (e.g., <FIG> with associated text).

The processor <NUM> may receive power from the power source <NUM>, and may be configured to distribute and/or control the power to the other components in UE <NUM>. The power source <NUM> may be any suitable device for powering UE <NUM>.

The processor <NUM> may also be coupled to the GPS chipset <NUM>, which is configured to provide location information (e.g., longitude and latitude) regarding the current location of UE <NUM>. It will be appreciated that UE <NUM> may acquire location information by way of any suitable locationdetermination method while remaining consistent with an embodiment.

For example, the peripherals <NUM> may include an accelerometer, an e-compass, a satellite transceiver, a sensor, a digital camera (for photographs or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, and the like.

<FIG> is a block diagram of an exemplary computing system <NUM> on which, for example, devices within or connected with the communication system <NUM> of <FIG> and <FIG> may be implemented. Computing system <NUM> may comprise a computer or server and may be controlled primarily by computer readable instructions, which may be in the form of software, wherever, or by whatever means such software is stored or accessed. Such computer readable instructions may be executed within central processing unit (CPU) <NUM> to cause computing system <NUM> to do work. In many known workstations, servers, and personal computers, central processing unit <NUM> is implemented by a single-chip CPU called a microprocessor. In other machines, the central processing unit <NUM> may comprise multiple processors. Coprocessor <NUM> is an optional processor, distinct from main CPU <NUM> that performs additional functions or assists CPU <NUM>. CPU <NUM> and/or coprocessor <NUM> may receive, generate, and process data related to the disclosed systems and methods for WLAN QoS via EAP/Diameter, such as receiving appropriate diameter messages or EAP response or request messages.

In operation, CPU <NUM> fetches, decodes, and executes instructions, and transfers information to and from other resources via the computer's main data-transfer path, system bus <NUM>. Such a system bus connects the components in computing system <NUM> and defines the medium for data exchange. System bus <NUM> typically includes data lines for sending data, address lines for sending addresses, and control lines for sending interrupts and for operating the system bus. An example of such a system bus <NUM> is the PCI (Peripheral Component Interconnect) bus.

Memory devices coupled to system bus <NUM> include random access memory (RAM) <NUM> and read only memory (ROM) <NUM>. Such memories include circuitry that allows information to be stored and retrieved. ROMs <NUM> generally contain stored data that cannot easily be modified. Data stored in RAM <NUM> can be read or changed by CPU <NUM> or other hardware devices. Access to RAM <NUM> and/or ROM <NUM> may be controlled by memory controller <NUM>. Memory controller <NUM> may provide an address translation function that translates virtual addresses into physical addresses as instructions are executed. Memory controller <NUM> may also provide a memory protection function that isolates processes within the system and isolates system processes from user processes. Thus, a program running in a first mode can access only memory mapped by its own process virtual address space; it cannot access memory within another process's virtual address space unless memory sharing between the processes has been set up.

In addition, computing system <NUM> may contain peripherals controller <NUM> responsible for communicating instructions from CPU <NUM> to peripherals, such as printer <NUM>, keyboard <NUM>, mouse <NUM>, and disk drive <NUM>.

Display <NUM>, which is controlled by display controller <NUM>, is used to display visual output generated by computing system <NUM>. Such visual output may include text, graphics, animated graphics, and video. Display <NUM> may be implemented with a CRT-based video display, an LCD-based flat-panel display, gas plasma-based flat-panel display, or a touch-panel. Display controller <NUM> includes electronic components required to generate a video signal that is sent to display <NUM>.

Further, computing system <NUM> may contain network adaptor <NUM> that may be used to connect computing system <NUM> to an external communications network <NUM>.

It is understood that any or all of the systems, methods and processes described herein may be embodied in the form of computer executable instructions (i.e., program code) stored on a computer-readable storage medium which instructions, when executed by a machine, such as a computer, server, UE, or the like, perform and/or implement the systems, methods and processes described herein. Specifically, any of the steps, operations or functions described above may be implemented in the form of such computer executable instructions. Computer readable storage media include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information, but such computer readable storage media do not includes signals. Computer readable storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other physical medium which can be used to store the desired information and which can be accessed by a computer.

Claim 1:
A server (<NUM>) comprising:
a processor; and
a memory coupled with the processor, the memory having stored thereon executable instructions that when executed by the processor cause the processor to effectuate operations comprising:
sending an authentication, authorization and accounting, AAA, protocol message to a 3GPP AAA server (<NUM>), the AAA protocol message indicative of an identity of a user equipment, UE (<NUM>);
monitoring 3GPP based access signaling messages between the UE and the 3GPP AAA server (<NUM>);
based on the monitored 3GPP based access signaling messages and the identity of the UE (<NUM>), identifying a wireless local area network, WLAN, quality of service, QoS, parameter associated with the UE (<NUM>);
sending, as an IEEE <NUM>.1X protocol request message, the identified WLAN QoS parameter to the UE (<NUM>);
applying the identified WLAN QoS parameter to downlink traffic flows destined for the UE (<NUM>); and
setting a user priority for WLAN downlink traffic flows destined for the UE (<NUM>) in accordance with the WLAN QoS parameter.