Techniques for enabling quality of service (QoS) on WLAN for traffic related to a bearer on cellular networks

Techniques are described for managing QoS parameters of a bearer for which at least a portion of bearer data is served over a WLAN radio access technology. According to these techniques, a first device may identify a first set of one or more QoS parameters for serving a bearer over a wireless wide area network (WWAN). The first device may also determine a second set of one or more QoS parameters for serving the bearer over the WLAN based on an association between the first set of QoS parameters and the second set of one or more QoS parameters.

FIELD OF THE DISCLOSURE

The present disclosure is related to wireless communications. More specifically, the present disclosure is directed to techniques for enabling Quality of Service (QoS) on WLAN for traffic related to a bearer on cellular networks.

BACKGROUND

Generally, a wireless multiple-access communications system may include a number of base stations, each simultaneously supporting communication for multiple mobile devices. Base stations may communicate with mobile devices on downstream and upstream links. The downlink (or forward link) refers to the communication link from an eNodeB or other base station to a user equipment (UE), and the uplink (or reverse link) refers to the communication link from the UE to the eNodeB or other base station. Each base station has a coverage range, which may be referred to as the coverage area of the cell.

Traffic between a UE and the core network may be conveyed over a bearer having a defined minimum Quality of Service (QoS), which is enforced by a cellular radio access network. However, in certain networks, bearer traffic to or from a multi-mode UE may be steered over a wireless local area network (WLAN) rather than the traditional cellular radio access network. In such cases, the cellular radio access network may not be able to enforce the QoS of the bearer over WLAN, which may cause the QoS to fall below the established minimum for the bearer.

SUMMARY

The described features generally relate to techniques for maintaining the QoS defined for a bearer while transmitting at least a portion of the data for the bearer over a WLAN connection. Further scope of the applicability of the described methods and apparatuses will become apparent from the following detailed description, claims, and drawings. The detailed description and specific examples are given by way of illustration only, as various changes and modifications within the spirit and scope of the description will become apparent to those skilled in the art.

In accordance with a first set of illustrative embodiments, a method of wireless communication may include identifying, at a first device, a first set of one or more quality-of-service (QoS) parameters for serving a bearer over a wireless wide area network (WWAN); and determining, at the first device, a second set of one or more QoS parameters for serving the bearer over a wireless local area network (WLAN) based on an association between the first set of QoS parameters and the second set of one or more QoS parameters.

In certain examples, determining the second set of one or more QoS parameters may include mapping the first set of one or more QoS parameters to the second set of one or more QoS parameters. The mapping may include a static mapping configured according to the association between the first set of one or more QoS parameters and the second set of one or more QoS parameters. Additionally or alternatively, the mapping may include a semi-static mapping. In certain examples, the mapping may be based at least in part on an operations, administration and maintenance (OAM) configuration of the WWAN. Additionally or alternatively, the mapping may include receiving the second set of one or more QoS parameters from a server in an Open Mobile Alliance Device Management (OMA DM) message, or retrieving the second set of one or more QoS parameters from a Universal Subscriber Identity Module (USIM). The mapping may be dynamically adjusted based on individual WWAN-WLAN pairs, network conditions or signaling received from the network.

In certain embodiments, the second set of one or more QoS parameters may be transmitted from the first device to a second device in connection with establishing the bearer.

In one example, the bearer may include an evolved packet system (EPS) bearer for a mobile device, the second device may include the mobile device, and the second set of one or more QoS parameters may be transmitted via a non-access stratum (NAS) layer of the WWAN. In additional or alternative examples, the bearer may include an evolved packet system (EPS) bearer for a mobile device, the second device may include the mobile device, and the second set of one or more QoS parameters may be transmitted via a radio resource control (RRC) layer of the WWAN.

In additional or alternative examples, the bearer may include an EPS bearer, the first device may include a mobility management entity, the second device may include an eNodeB, and the second set of one or more QoS parameters may be transmitted over a S1 interface of the WWAN.

In additional or alternative examples, the bearer may include an evolved packet system (EPS) bearer and the second set of one or more QoS parameters may be transmitted over a core network interface.

In additional or alternative examples, the bearer may include a radio bearer, the first device may include a serving general packet radio service support node, the second device may include a radio network controller, and the second set of one or more QoS parameters may be transmitted over an Iu interface of the WWAN.

In certain embodiments, the first set of one or more QoS parameters may be received at the first device in connection with establishing the bearer.

In one example, the bearer may include an evolved packet system (EPS) bearer, the first device may include a user equipment (UE), and the first set of one or more QoS parameters may include a QoS class identifier (QCI) that is received over a non-access stratum (NAS) layer.

In additional or alternative examples, the bearer may include a radio bearer, the first device may include a user equipment (UE), and the first set of one or more QoS parameters may include a logical channel priority that is received over a radio resource control (RRC) layer.

In certain embodiments, the first device may include a user equipment (UE), and a requested second set of QoS parameters may be transmitted to the WWAN in connection with one or more of a packet data network connectivity request message, an attach request message, a bearer resource allocation message, or a modify bearer context request message.

In certain embodiments, data associated with the bearer may be transmitted over the WLAN according to the identified second set of one or more QoS parameters.

In certain embodiments, the first set of one or more QoS parameters may include one or more of: a QoS class identifier (QCI), an access class priority, a logical channel priority, a traffic class, or a traffic handling priority.

In certain embodiments, the second set of one or more QoS parameters may include one or more of: an access category (AC), a maximum buffer size, a bit rate, or a latency.

According to at least a second set of illustrative embodiments, an apparatus for managing wireless communication, may include at least one processor and a memory communicatively coupled with the at least one processor. The processor may be configured to execute code stored on the memory to: identify a first set of one or more quality-of-service (QoS) parameters for serving a bearer over a wireless wide area network (WWAN); and determine a second set of one or more QoS parameters for serving the bearer over a wireless local area network (WLAN) based on an association between the first set of QoS parameters and the second set of one or more QoS parameters.

The processor may be further configured to execute code causing the processor to perform one or more aspects of the functionality described above with respect to the illustrative method of the first set of illustrative embodiments.

According to at least a third set of illustrative embodiments, an apparatus for managing wireless communication, may include means for identifying a first set of one or more quality-of-service (QoS) parameters for serving a bearer over a wireless wide area network (WWAN); and means for determining a second set of one or more QoS parameters for serving the bearer over a wireless local area network (WLAN) based on an association between the first set of QoS parameters and the second set of one or more QoS parameters.

The apparatus may further include means for performing one or more aspects of the functionality described above with respect to the illustrative method of the first set of illustrative embodiments.

According to at least a fourth set of illustrative embodiments, a computer program product may include a non-transitory computer-readable medium comprising computer-readable code configured to cause at least one processor to identify a first set of one or more quality-of-service (QoS) parameters for serving a bearer over a wireless wide area network (WWAN); and determine a second set of one or more QoS parameters for serving the bearer over a wireless local area network (WLAN) based on an association between the first set of QoS parameters and the second set of one or more QoS parameters.

The non-transitory computer-readable medium may further include computer-readable code configured to cause the at least one processor to perform one or more aspects of the functionality described above with respect to the illustrative method of the first set of illustrative embodiments.

DETAILED DESCRIPTION

The present disclosure describes techniques for managing QoS parameters of a bearer for which at least a portion of bearer data is served over a WLAN radio access technology. According to these techniques, a first device may identify a first set of one or more QoS parameters for serving a bearer over a wireless wide area network (WWAN). The first device may also determine a second set of one or more QoS parameters for serving the bearer over the WLAN based on an association between the first set of QoS parameters and the second set of one or more QoS parameters. In certain examples, the first device may map the first set of one or more QoS parameters to a second set of one or more QoS parameters according to a predetermined relationship. Data for the bearer may then be served over the WLAN using the second set of QoS parameters.

As used in the present description and the appended claims, the term “bearer” refers to a link between two nodes in a communication network.

As used in the present description and the appended claims, the term “wireless wide area network” or “WWAN” refers to a cellular wireless network. Examples of WWANs include, for example, LTE networks, UMTS networks, CDMA2000 networks, GSM/EDGE networks, 1×/EV-DO networks, and the like. In certain examples, a WWAN may be referred to as a “radio access network.”

As used in the present description and the appended claims, the term “wireless local area network” or “WLAN” refers to a non-cellular wireless network. Examples of WLANs include, for example, wireless networks conforming to the IEEE 802.11 (“Wi-Fi”) family of standards.

Referring first toFIG. 1, a diagram illustrates an example of a wireless communications system100, in accordance with an aspect of the present disclosure. The wireless communications system100includes WWAN base stations (or cells)105, user equipment (UEs)115, and a core network130. The WWAN base stations105may communicate with the UEs115under the control of a base station controller (not shown), which may be part of the core network130or the WWAN base stations105in various embodiments. WWAN base stations105may communicate control information and/or user data with the core network130through core network backhaul links132. In embodiments, the WWAN base stations105may communicate, either directly or indirectly, with each other over inter-base station backhaul links134, which may be wired or wireless communication links. The wireless communications system100may support operation on multiple carriers (waveform signals of different frequencies). Multi-carrier transmitters can transmit modulated signals simultaneously on the multiple carriers. For example, each communication link125may be a multi-carrier signal modulated according to the various radio technologies described elsewhere in this specification. Each modulated signal may be sent on a different carrier and may carry control information (e.g., reference signals, control channels, etc.), overhead information, data, etc.

The WWAN base stations105may wirelessly communicate with the UEs115via one or more base station antennas. Each of the WWAN base stations105sites may provide communication coverage for a respective coverage area110. In some embodiments, a WWAN base station105may be referred to as a base transceiver station, a radio base station, an access point, a radio transceiver, a basic service set (BSS), an extended service set (ESS), a NodeB, eNodeB, Home NodeB, a Home eNodeB, or some other suitable terminology. The coverage area110for a base station may be divided into sectors making up only a portion of the coverage area (not shown). The wireless communications system100may include WWAN base stations105of different types (e.g., macro, micro, and/or pico base stations). There may be overlapping coverage areas for different technologies.

In embodiments, the wireless communications system100is an LTE/LTE-A network communication system. In LTE/LTE-A network communication systems, the terms evolved Node B (eNodeB) may be generally used to describe the WWAN base stations105. The wireless communications system100may be a Heterogeneous LTE/LTE-A network in which different types of eNodeBs provide coverage for various geographical regions. For example, each WWAN base station105may provide communication coverage for a macro cell, a pico cell, a femto cell, and/or other types of cell. A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscriptions with the network provider. A pico cell would generally cover a relatively smaller geographic area (e.g., buildings) and may allow unrestricted access by UEs with service subscriptions with the network provider. A femto cell would also generally cover a relatively small geographic area (e.g., a home) and, in addition to unrestricted access, may also provide restricted access by UEs having an association with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs for users in the home, and the like). An eNodeB for a macro cell may be referred to as a macro eNodeB. An eNodeB for a pico cell may be referred to as a pico eNodeB. And, an eNodeB for a femto cell may be referred to as a femto eNodeB or a home eNodeB. An eNodeB may support one or multiple (e.g., two, three, four, and the like) cells.

The core network130may communicate with the eNodeBs or other WWAN base stations105via a core network backhaul link132(e.g., S1 interface, etc.). The WWAN base stations105may also communicate with one another, e.g., directly or indirectly via inter-base station backhaul links134(e.g., X2 interface, etc.) and/or via core network backhaul links132(e.g., through core network130). The system100may support synchronous or asynchronous operation. For synchronous operation, the WWAN base stations may have similar frame timing, and transmissions from different WWAN base stations may be approximately aligned in time. For asynchronous operation, the WWAN base stations may have different frame timing, and transmissions from different eNodeBs may not be aligned in time. The techniques described herein may be used for either synchronous or asynchronous operations.

The UEs115may be dispersed throughout the wireless communications system100, and each UE may be stationary or mobile. A UE115may also be referred to by those skilled in the art as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. A UE115may be a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless phone, a wireless local loop (WLL) station, or the like. A UE115may be able to communicate with macro eNodeBs, pico eNodeBs, femto eNodeBs, relays, and the like.

The communication links125shown in the wireless communications system100may include uplink (UL) transmissions from a UE115to a WWAN base station105, and/or downlink (DL) transmissions, from a WWAN base station105to a UE115. The downlink transmissions may also be called forward link transmissions while the uplink transmissions may also be called reverse link transmissions.

In certain examples, a UE115may be capable of simultaneously communicating with a WWAN base station105and a WLAN access point107. In such examples, the WWAN base station105or the UE115may steer or divert data transmissions between the UE115and the WWAN base station105over to WLAN (e.g., through communication with the WLAN access point107) to increase bandwidth, manage loading, or optimize resource utilization of the WWAN base station105. Nevertheless, some or all of the traffic steered from the WWAN network to the WLAN may relate to bearers associated with minimum QoS requirements.

The UE115and/or the WWAN base station105may be configured to, for one or more of the affected bearers, identify a first set of one or more QoS parameters associated with serving the bearer over WWAN (i.e., the LTE network), then map the first set of one or more QoS parameters to a second set of one or more parameters associated with serving the bearer over WLAN. Once the mapped second set of one or more QoS parameters has been determined, the UE115may communicate with the WLAN access point107to configure the bearer over WLAN using the second set of QoS parameters, thereby maintaining at least the minimum QoS specified for the bearer at the WLAN (e.g., Wi-Fi network). The WLAN access point107may configure one or more data bearers between the UE115and the core network130.

FIG. 2is a block diagram conceptually illustrating an example of a bearer architecture in a telecommunications system, in accordance with an aspect of the present disclosure used to provide an end-to-end service235between UE215and a peer entity230addressable over a network. The peer entity230may be a server, another UE, or another type of network-addressable device. The end-to-end service235may forward data between UE215and the peer entity230according to a set of QoS characteristics associated with the end-to-end service. The end-to-end service235may be implemented by at least the UE215, an eNodeB205, a serving gateway (SGW)220, a packet data network (PDN) gateway (PGW)225, and the peer entity230. The UE215and eNodeB205may be components of an evolved UMTS terrestrial radio access network (E-UTRAN)208, the air interface of the LTE wireless communication standard. Serving gateway220and PDN gateway225may be components of an evolved Packet Core (EPC)209, the core network architecture of the LTE wireless communication standard. The peer entity230may be an addressable node on a packet data network (PDN)210communicatively coupled with the PDN gateway225.

The end-to-end service235may be implemented by an evolved packet system (EPS) bearer240between the UE215and the PDN gateway225, and by an external bearer245between the PDN gateway225and the peer entity230over an SGi interface. The SGi interface may expose an internet protocol (IP) or other network-layer address of the UE215to the PDN210.

The EPS bearer240may be an end-to-end tunnel defined to a specific QoS. Each EPS bearer240may be associated with a plurality of parameters, for example, a QoS class identifier (QCI), an allocation and retention priority (ARP), a guaranteed bit rate (GBR), and an aggregate maximum bit rate (AMBR). The QCI may be an integer indicative of a QoS class associated with a predefined packet forwarding treatment in terms of latency, packet loss, GBR, and priority. In certain examples, the QCI may be an integer from 1 to 9. The ARP may be used by a scheduler of an eNodeB205to provide preemption priority in the case of contention between two different bearers for the same resources. The GBR may specify separate downlink and uplink guaranteed bit rates. Certain QoS classes may be non-GBR such that no guaranteed bit rate is defined for bearers of those classes.

The EPS bearer240may be implemented by an E-UTRAN radio access bearer (E-RAB)250between the UE215and the serving gateway220, and an S5/S8 bearer255between the serving gateway220and the PDN gateway over an S5 or S8 interface. S5 refers to the signaling interface between the serving gateway220and the PDN gateway225in a non-roaming scenario, and S8 refers to an analogous signaling interface between the serving gateway220and the PDN gateway225in a roaming scenario. The E-RAB250may be implemented by a radio bearer260between the UE215and the eNodeB205over an LTE-Uu air interface, and by an S1 bearer265between the eNodeB and the serving gateway220over an S1 interface.

It will be understood that, whileFIG. 2illustrates the bearer hierarchy in the context of an example of end-to-end service235between the UE215and the peer entity230, certain bearers may be used to convey data unrelated to end-to-end service235. For example, radio bearers260or other types of bearers may be established to transmit control data between two or more entities where the control data is unrelated to the data of the end-to-end service235.

As discussed above with respect toFIG. 1, data related to one or more EPS bearers240or may be offloaded from the LTE air interface to a WLAN interface between the UE215and a WLAN access point107(not shown). Depending on the system configuration, the WLAN access point107may then forward the bearer data to the eNodeB205, the serving gateway220, and the PDN gateway225, or directly to the peer entity230over the PDN210. Steering bearer traffic from the LTE air interface to the WLAN interface may improve overall bandwidth and resource utilization of the LTE network. However, because the eNodeB205typically controls the scheduling of traffic only over the LTE air interface and not the WLAN interface, steering bearer data traffic to the WLAN interface may prevent the eNodeB205from enforcing QoS parameters associated with the EPS bearers240.

To address this issue, the UE215, eNodeB205, serving gateway220, PDN gateway225, and/or other nodes may determine a first set of one or more QoS parameters (e.g., a QCI) associated with serving the bearer slated for WWAN steering, and map the first set of one or more QoS parameters to a second set of one or more QoS parameters (e.g., a WLAN access category (AC)) associated with serving the bearer over WLAN. The WLAN may then transmit the offloaded bearer traffic using the second set of one or more QoS parameters identified for the bearer traffic. In this way, the QoS of bearer traffic offloaded to the WLAN may be managed by such that the WLAN provides the bearer traffic at a QoS that meets or exceeds the QoS defined for the bearer on the WWAN to maintain the quality of the end-to-end service235.

FIG. 3Ais a block diagram conceptually illustrating an example of downlink channels in a telecommunications system, in accordance with an aspect of the present disclosure, andFIG. 3Bis a block diagram conceptually illustrating an example of uplink channels in a telecommunications system, in accordance with an aspect of the present disclosure. The channelization hierarchy may be implemented by, for example, the wireless communications system100ofFIG. 1. Downlink channelization hierarchy300may illustrate, for example, channel mapping between downlink logical channels310, downlink transport channels320, and downlink physical channels330of an LTE/LTE-A network.

Downlink logical channels310may be classified into Control Channels and Traffic Channels. Each downlink logical channel310may be associated with a separate radio bearer260(shown inFIG. 2); that is, there may be a one-to-one correlation between downlink logical channels310and radio bearers260. The radio bearers260conveying data (e.g., for EPS bearers240) may be referred to as data radio bearers (DRBs), while radio bearers260conveying control data (e.g., for control channels) may be referred to as control radio bearers (CRBs).

Logical control channels may include a paging control channel (PCCH)311, which is the downlink channel that transfers paging information, a broadcast control channel (BCCH)312, which is the downlink channel for broadcasting system control information, and a multicast control channel (MCCH)316, which is a point-to-multipoint downlink channel used for transmitting multimedia broadcast and multicast service (MBMS) scheduling and control information for one or several multicast traffic channels (MTCHs)317.

Generally, after establishing radio resource control (RRC) connection, MCCH316may only be used by the user equipments that receive MBMS. Dedicated control channel (DCCH)314is another logical control channel that is a point-to-point bi-directional channel transmitting dedicated control information, such as user-specific control information used by the user equipment having an RRC connection. Common control channel (CCCH)313is also a logical control channel that may be used for random access information. Logical traffic channels may include a dedicated traffic channel (DTCH)315, which is a point-to-point bi-directional channel dedicated to one user equipment for the transfer of user information and a MTCH317, which may be used for point-to-multipoint downlink transmission of traffic data.

The communication networks that accommodate some of the various embodiments may additionally include logical transport channels that are classified into downlink (DL) and uplink (UL). The downlink transport channels320may include a Paging Channel (PCH)321, a broadcast channel (BCH)322, a downlink shared data channel (DL-SCH)323, and a multicast channel (MCH)324.

The physical channels may also include a set of downlink physical channels330and uplink physical channels370. In some disclosed embodiments, the downlink physical channels330may include a physical broadcast channel (PBCH)332, a physical control format indicator channel (PCFICH)331, a physical downlink control channel (PDCCH)335, a physical hybrid ARQ indicator channel (PHICH)333, a physical downlink shared channel (PDSCH)334and a physical multicast channel (PMCH)336.

The uplink channelization hierarchy340ofFIG. 3Bmay illustrate, for example, channel mapping between uplink logical channels350, uplink transport channels360, and uplink physical channels370for an LTE/LTE-A network. The uplink transport channels360may include a random access channel (RACH)361, and an uplink shared data channel (UL-SCH)362. The uplink physical channels370may include at least one of a physical random access channel (PRACH)371, a physical uplink control channel (PUCCH)372, and a physical uplink shared channel (PUSCH)373.

FIG. 4is a block diagram conceptually illustrating a design of a WWAN base station405and a UE415, in accordance with an aspect of the present disclosure. The eNodeB and UE may be part of a wireless communications system400. This wireless communications system400may illustrate aspects of the wireless communications system100ofFIG. 1and/or WWAN bearer hierarchy200ofFIG. 2. For example, the WWAN base station405may be an example of one or more of the WWAN base stations and/or eNodeBs described in other Figures, and the UE415may be an example of one or more of the UEs described with respect to other Figures.

The WWAN base station405may be equipped with base station antennas4341through434x, where x is a positive integer, and the UE415may be equipped with UE antennas4521through452n. In the wireless communications system400, the WWAN base station405may be able to send data over multiple communication links at the same time. Each communication link may be called a “layer” and the “rank” of the communication link may indicate the number of layers used for communication. For example, in a 2×2 MIMO system where the WWAN base station405transmits two “layers,” the rank of the communication link between the WWAN base station405and the UE415is two.

At the WWAN base station405, a base station transmit processor420may receive data from a base station data source and control information from a base station processor440. The control information may be for the PBCH, PCFICH, PHICH, PDCCH, etc. The data may be for the PDSCH, etc. The base station transmit processor420may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. The base station transmit processor420may also generate reference symbols, e.g., for the PSS, SSS, and cell-specific reference signal. A base station transmit (TX) MIMO processor430may perform spatial processing (e.g., precoding) on data symbols, control symbols, and/or reference symbols, if applicable, and may provide output symbol streams to the base station modulator/demodulators4321through432x. Each base station modulator/demodulator432may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each base station modulator/demodulator432may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink (DL) signal. In one example, DL signals from base station modulator/demodulators4321through432xmay be transmitted via the base station antennas4341through434x, respectively.

At the UE415, the UE antennas4521through452nmay receive the DL signals from the WWAN base station405and may provide the received signals to the UE modulator/demodulators4541through454n, respectively. Each UE modulator/demodulator454may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each UE modulator/demodulator454may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A UE MIMO detector456may obtain received symbols from all the UE modulator/demodulators4541through454n, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A UE receive (Rx) processor458may process (e.g., demodulate, deinterleave, and decode) the detected symbols, providing decoded data for the UE415to a data output, and provide decoded control information to a UE processor480, or UE memory482.

On the uplink (UL), at the UE415, a UE transmit processor464may receive and process data from a UE data source. The UE transmit processor464may also generate reference symbols for a reference signal. The symbols from the UE transmit processor464may be precoded by a UE transmit MIMO processor466if applicable, further processed by the UE modulator/demodulators4541through454n(e.g., for SC-FDMA, etc.), and be transmitted to the WWAN base station405in accordance with the transmission parameters received from the WWAN base station405. At the WWAN base station405, the UL signals from the UE415may be received by the base station antennas434, processed by the base station modulator/demodulators432, detected by a base station MIMO detector436if applicable, and further processed by a base station receive processor. The base station receive processor438may provide decoded data to a base station data output and to the base station processor440. The components of the UE415may, individually or collectively, be implemented with one or more Application Specific Integrated Circuits (ASICs) adapted to perform some or all of the applicable functions in hardware. Each of the noted modules may be a means for performing one or more functions related to operation of the wireless communications system400. Similarly, the components of the WWAN base station405may, individually or collectively, be implemented with one or more Application Specific Integrated Circuits (ASICs) adapted to perform some or all of the applicable functions in hardware. Each of the noted components may be a means for performing one or more functions related to operation of the wireless communications system400.

The communication networks that may accommodate some of the various disclosed embodiments may be packet-based networks that operate according to a layered protocol stack. For example, communications at the bearer or Packet Data Convergence Protocol (PDCP) layer may be IP-based. A Radio Link Control (RLC) layer may perform packet segmentation and reassembly to communicate over logical channels. A Medium Access Control (MAC) layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer may also use Hybrid ARQ (HARM) to provide retransmission at the MAC layer to improve link efficiency. At the Physical layer, the transport channels may be mapped to Physical channels.

In one configuration, the WWAN base station405and/or the UE415includes means for identifying a first set of one or more QoS parameters for serving a bearer over a wireless wide area network (WWAN), and means for determining a second set of one or more QoS parameters for serving the bearer over a WLAN based on an association between the first set of QoS parameters and the second set of QoS parameters. In one aspect, the aforementioned means may be the base station processor440, the base station memory442, the base station transmit processor420, base station receive processor438, the base station modulator/demodulators432, and the base station antennas434of the WWAN base station405configured to perform the functions recited by the aforementioned means. In another aspect, the aforementioned means may be the UE processor480, the UE memory482, the UE transmit processor464, UE receive processor458, the UE modulator/demodulators454, and the UE antennas452of the UE415configured to perform the functions recited by the aforementioned means.

FIG. 5illustrates a block diagram conceptually illustrating an aggregation of LTE and WLAN radio access technologies at a user equipment (UE), in accordance with an aspect of the present disclosure. The aggregation may occur in a system500including a UE515, which can communicate with an eNodeB505using one or more component carriers 1 through N (CC1-CCN), and with a WLAN access point (AP)507using WLAN carrier540. The UE515may be an example of one or more of the UEs described with reference to other Figures. The eNodeB505may be an example of one or more of the WWAN base stations and/or eNodeBs described with reference to other Figures. While only one UE515, one eNodeB505, and one WLAN access point507are illustrated inFIG. 5, it will be appreciated that the system500can include any number of UEs515, eNodeBs505, and/or WLAN access points507.

The eNodeB505can transmit information to the UE515over forward (downlink) channels5321through532Non LTE component carriers5301through530n. In addition, the UE515can transmit information to the eNodeB505over reverse (uplink) channels5341through534-N on LTE component carriers CC1though CCN. Similarly, the WLAN access point507may transmit information to the UE515over forward (downlink) channel552on WLAN carrier540. In addition, the UE515may transmit information to the WLAN access point507over reverse (uplink) channel554of WLAN carrier540.

In describing the various entities ofFIG. 5, as well as other figures associated with some of the disclosed embodiments, for the purposes of explanation, the nomenclature associated with a 3GPP LTE or LTE-A wireless network is used. However, it is to be appreciated that the system500can operate in other networks such as, but not limited to, an OFDMA wireless network, a CDMA network, a 3GPP2 CDMA2000 network and the like.

In multi-carrier operations, the downlink control information (DCI) messages associated with different UEs515can be carried on a plurality of component carriers. For example, the DCI on a PDCCH can be included on the same component carrier that is configured to be used by a UE515for PDSCH transmissions (i.e., same-carrier signaling). Alternatively, or additionally, the DCI may be carried on a component carrier different from the target component carrier used for PDSCH transmissions (i.e., cross-carrier signaling). In some embodiments, a carrier indicator field (CIF), which may be semi-statically enabled, may be included in some or all DCI formats to facilitate the transmission of PDCCH control signaling from a carrier other than the target carrier for PDSCH transmissions (cross-carrier signaling).

In the present example, the UE515may receive data from one eNodeB505. However, users on a cell edge may experience high inter-cell interference which may limit the data rates. Multiflow allows UEs to receive data from two eNodeBs505simultaneously. Multiflow works by sending and receiving data from the two eNodeBs505in two totally separate streams when a UE115is in range of two cell towers in two adjacent cells at the same time. The UE115talks to two eNodeB505simultaneously when the device is on the edge of either eNodeBs' reach. By scheduling two independent data streams to the mobile device from two different eNodeBs at the same time, multiflow exploits uneven loading in HSPA networks. This helps improve the cell edge user experience while increasing network capacity. In one example, throughput data speeds for users at a cell edge may double. “Multiflow” is a feature of LTE/LTE-A that is similar to dual-carrier HSPA, however, there are differences. For example, dual-carrier HSPA doesn't allow for connectivity to multiple towers to connect simultaneously to a device.

Previously, LTE-A standardization, LTE component carriers530have been backward-compatible, which enabled a smooth transition to new releases. However, this feature caused the LTE component carriers530to continuously transmit common reference signals (CRS, also referred to as cell-specific reference signals) in every subframe across the bandwidth. Most cell site energy consumption is caused by the power amplifier, as the cell remains on even when only limited control signaling is being transmitted, causing the amplifier to continue to consume energy. CRS were introduced in release 8 of LTE and are LTE's most basic downlink reference signal. The CRSs are transmitted in every resource block in the frequency domain and in every downlink subframe. CRS in a cell can be for one, two, or four corresponding antenna ports. CRS may be used by remote terminals to estimate channels for coherent demodulation. A New Carrier Type (NCT) allows temporarily switching off of cells by removing transmission of CRS in four out of five sub frames. This feature reduces power consumed by the power amplifier, as well as the overhead and interference from CRS, as the CRS is no longer continuously transmitted in every subframe across the bandwidth. In addition, the New Carrier Type allows the downlink control channels to be operated using UE-specific Demodulation Reference Symbols. The New Carrier Type might be operated as a kind of extension carrier along with another LTE/LTE-A carrier or alternatively as standalone non-backward compatible carrier.

FIGS. 6A and 6Bare block diagrams conceptually illustrating examples of data paths between a UE615and a peer entity630over a PDN610(e.g., the Internet), in accordance with an aspect of the present disclosure. The data paths include an LTE link path645and a WLAN link path650are shown within the context of a wireless communications system600,665aggregating WLAN and LTE radio access technologies. In each example, the wireless communications system600and665, shown inFIGS. 6A and 6B, respectively, may include a UE615, an eNodeB605, a WLAN access point607, an evolved packet core (EPC)609, a PDN610, and a peer entity630. The evolved packet core609of each example may include a mobility management entity (MME)635, a serving gateway (SGW)620, and a PDN gateway (PGW)625. A home subscriber system (HSS)640may be communicatively coupled with the MME635. The UE615of each example may include an LTE radio655and a WLAN radio660. These elements may represent aspects of one or more of their counterparts described with reference to other Figures.

Referring specifically toFIG. 6A, the eNodeB605and WLAN access point607may be capable of providing the UE615with access to the PDN610using the aggregation of one or more LTE component carriers or one or more WLAN component carriers. Using this access to the PDN610, the UE615may communicate with the peer entity630. The eNodeB605may provide access to the PDN610through the evolved packet core609(e.g., through the LTE link path645), and the WLAN access point607may provide direct access to the PDN610(e.g., through the WLAN link path650).

The MME635may be the control node that processes the signaling between the UE615and the evolved packet core609. Generally, the MME635may provide bearer and connection management. The MME635may, therefore, be responsible for idle mode UE tracking and paging, bearer activation and deactivation, and SGW selection for the UE615. The MME635may communicate with the eNodeB605over an S1-MME interface. The MME635may additionally authenticate the UE615and implement Non-Access Stratum (NAS) signaling with the UE615.

The HSS640may, among other functions, store subscriber data, manage roaming restrictions, manage accessible access point names (APNs) for a subscriber, and associate subscribers with MMEs635. The HSS640may communicate with the MME635over an S6a interface defined by the Evolved Packet System (EPS) architecture standardized by the 3GPP organization.

All user IP packets transmitted over LTE may be transferred through eNodeB605to the serving gateway620, which may be connected to the PDN gateway625over an S5 signaling interface and the MME635over an S11 signaling interface. The serving gateway620may reside in the user plane and act as a mobility anchor for inter-eNodeB handovers and handovers between different access technologies. The PDN gateway625may provide UE IP address allocation as well as other functions.

The PDN gateway625may provide connectivity to one or more external packet data networks, such as PDN610, over an SGi signaling interface. The PDN610may include the Internet, an Intranet, an IP Multimedia Subsystem (IMS), a Packet-Switched (PS) Streaming Service (PSS), and/or other types of PDNs.

In the present example, user plane data between the UE615and the evolved packet core609may traverse the same set of one or more EPS bearers, irrespective of whether the traffic flows over the LTE link path645or the WLAN link path650. Signaling or control plane data related to the set of one or more EPS bearers may be transmitted between the LTE radio655of the UE615and the MME635of the evolved packet core609, by way of the eNodeB605.

FIG. 6Billustrates an example wireless communications system665in which the eNodeB605and WLAN access point607are collocated or otherwise in high-speed communication with each other. In this example, EPS bearer-related data between the UE615and the WLAN access point607may be routed to the eNodeB605, and then to the evolved packet core609. In this way, all EPS bearer-related data may be forwarded along the same path between the eNodeB605, the evolved packet core609, the PDN610, and the peer entity630.

FIGS. 7A and 7Bare block diagrams conceptually illustrating examples of QoS implementation, in accordance with an aspect of the present disclosure. The QoS implementation is described within the context of wireless communications systems700,750for managing WLAN QoS for bearer traffic. Each wireless communications system700,750includes a UE715, an eNodeB705, and a WLAN access point707. The wireless communications systems700,750may implement one or more aspects described with reference to the systems and devices of other Figures.

The UE715ofFIGS. 7A and 7Bmay be configured to transmit and receive bearer traffic over an LTE air interface with eNodeB705. The bearer traffic may relate to, for example, an EPS bearer. In addition, it may be permissible to transmit and receive data for certain EPS bearers over a WLAN interface between the UE715and the WLAN access point707. To satisfy the QoS specifications of a bearer that is partially or entirely handled by the WLAN interface between the UE715and the WLAN access point707, a first set of one or more QoS parameters associated with serving the bearer over the LTE air interface may be mapped to a second set of one or more QoS parameters associated with serving the bearer over the WLAN access point707.

In the example ofFIG. 7A, this mapping may occur at the eNodeB705. The mapping may take place when traffic related to one or more bearers of the eNodeB705is offloaded from the eNodeB705to the WLAN access point707. A WLAN QoS determining module720of the eNodeB705may identify a set of WWAN QoS parameters associated with the bearer for which partial or entire WLAN steering is possible and permissible. The WWAN QoS parameters may be represented by, for example, a QCI assigned to the bearer at the core network (i.e., the evolved packet core) when the bearer is set up or modified. The WLAN QoS determining module720may determine, based on QoS mapping data725, a mapping between the WWAN QoS parameters of the bearer and a set of WLAN QoS parameters that provide an equal or better QoS than what is defined by the WWAN QoS parameters. In certain examples, the WLAN QoS parameters may include an access category (AC) or priority code point (PCP). In certain examples, the QoS mapping data810may include a table of static or semi-static mappings defined by a standard or specific to an implementation of the principles described herein. Additionally or alternatively, the eNodeB705may dynamically and/or periodically determine or receive the mapping data or the set of WLAN QoS parameters from another device in or associated with the core network.

In the example ofFIG. 7B, the mapping of WWAN QoS parameters for the EPS bearer to WLAN QoS parameters for the EPS bearer may occur at the UE715. A WLAN QoS determining module720of the UE715may identify a set of WWAN QoS parameters associated with the EPS bearer for which partial or entire WLAN steering is possible and permissible. The WWAN QoS parameters may be represented by, for example, a QCI assigned to the EPS bearer at the core network (i.e., the evolved packet core) when the EPS bearer is set up or modified. The WLAN QoS determining module720may determine, based on QoS mapping data725, a mapping between the WWAN QoS parameters of the EPS bearer and a set of WLAN QoS parameters that provide an equal or better QoS than what is defined by the WWAN QoS parameters.

In certain examples, the WLAN QoS parameters may include an access category (AC) or priority code point (PCP) to be assigned to traffic of the EPS bearer. In certain examples, the QoS mapping data725may include a table of static or semi-static mappings defined by a standard or based on another implementation of the principles described herein. In certain examples, the QoS mapping data725at the UE715may be configured by an Open Mobile Alliance (OMA) server using an OMA Device Management (DM) message. Additionally or alternatively, the QoS mapping data725at the UE715may be configured using a universal subscriber module (USIM) or other device.

FIGS. 8A-8Care block diagrams conceptually illustrating examples of predetermined associations between WWAN and WLAN QoS parameters, in accordance with an aspect of the present disclosure. Specifically,FIGS. 8A-8Cshow diagrams of example tables of QoS mapping data810,815,820(corresponding toFIG. 8A,FIG. 8B, andFIG. 8C, respectively) that may be stored at or received by a UE115, eNodeB, or other device to map a first set of QoS parameters associated with serving an bearer over a WWAN with a second set of QoS parameters associated with transmitting the bearer over WLAN. The QoS mapping data810,815,820may be static or semi-static, as described elsewhere in this specification. The QoS mapping data810,815,820may be examples of the QoS mapping data725described with reference toFIGS. 7A and 7B, and may be used by a UE715or an eNodeB705to determine a mapping of WWAN QoS parameters to WLAN QoS parameters for use when bearer traffic is offloaded from WWAN to WLAN. In the present example, the first set of QoS parameters may be represented by the QCI of the EPS bearer in question, as defined by 3GPP TS 23.203 and similar standards. The second set of QoS parameters in this example may be represented by a WLAN access category (AC) and/or a priority code point (PCP), as defined by the IEEE 802.11 family of standards. In additional or alternative examples, the first set of QoS parameters may include one or more of: an access class (not to be confused with access category) priority, a logical channel priority, a traffic class, or a traffic handling priority. Additionally or alternatively, the second set of QoS parameters may include one or more of: a maximum buffer size, a bit rate, or a packet latency.

FIG. 8Ashows a table of QoS mapping data810associating each possible QCI of an EPS bearer with WLAN AC that supports the QoS requirements of that QCI. As discussed earlier, QoS support for EPS bearers in LTE and other 3GPP WWANs is based on the QCI determined by the MME when the EPS bearer is established. LTE Release 10 defines nine possible QCI classes, each of which is associated with a different set of QoS requirements for packet latencies, packet error loss rates, priority, and guaranteed bit rate. WLAN, on the other hand, defines levels of QoS support known as access categories (ACs). WLAN supports the different ACs by defining a shorter contention window and shorter arbitration inter-frame space for higher priority packets. For WLANs implementing the IEEE 802.11 standard, four basic ACs are possible: Background (AC_BK), Best Effort (AC_BE), Video (AC_VI), and Voice (AC_VO).

In the example ofFIG. 8A, each possible QCI is mapped to a corresponding WLAN AC. Thus, when the QCI of an EPS bearer is known, the WLAN AC to associate with traffic for that EPS bearer may be derived from the QoS mapping data810.

Additionally or alternatively, the QoS mapping data810may associate each possible logical channel priority or other QoS parameter(s) configured for a radio bearer serving the EPS bearer (e.g., seeFIG. 2) with a WLAN AC to determine the WLAN QoS for serving the packets of the EPS bearer over WLAN.

The QoS mapping data810may be determined as a function of an individual WWAN or class of WWANs, an individual WLAN or class of WLANs, or combinations thereof. The QoS parameters for the WWAN and/or the WLAN may conform to standardized formats (e.g., 3GPP LTE, IEEE 802.11) or be proprietary to an individual operator or manufacturer. In certain examples, the QoS mapping data810may be separately configured for different WWAN-WLAN pairs. For example, the same QCI or radio bearer QoS parameter of one WWAN may map to different ACs in different WLANs. Conversely, the same AC of a WLAN may map to different QCIs or radio bearer QoS parameters for different WWANs. Thus, different QoS mapping data810may be stored by or provided to the UE for different WWAN-WLAN pairs.

In certain examples, the UE or the network may adjust the QoS mapping data810for a WWAN-WLAN pair over time according to changing network conditions, explicit signaling from the network, or other factors. For example,FIG. 8Ashows a mapping of QCI 3 of the WWAN to access category AC_VO of the WLAN. However, the UE may adjust the mapping of QCI 3 to AC_BE if the UE determines that the WLAN is congested (e.g., by detecting a threshold amount of collisions, detecting interference on the channel, etc.), or in response to signaling received from the WWAN or WLAN. This dynamic adjustment in the QoS mapping data810may alter the contention window associated with bearers having a QCI of 3, thereby improving traffic flow.

FIG. 8Bshows a table of QoS mapping data815associating WLAN PCPs, defined in IEEE 802.11q with WLAN ACs, defined in IEEE 802.11e. In certain examples, an IEEE 802.1q MAC header may be used to determine the WLAN QoS parameters of a packet to the WLAN. However, the IEEE 802.1q header may define the QoS parameters of the packet in terms of priority code point (PCP) rather than AC. The mapping of WLAN PCPs to WLAN ACs may be static, as shown inFIG. 8B.

FIG. 8Cshows a table of QoS mapping data820which combines the tables ofFIGS. 7A and 7Binto a single table mapping EPS bearer QCIs of WWAN to WLAN PCPs and WLAN ACs. The QCI to PCP mapping shown in the QoS mapping data820of the present example may define the PCP values associated with the closest class of service priority level to the equivalent QCI.

FIG. 9is a block diagram conceptually illustrating an example of communications between an eNodeB905and a UE915, in accordance with an aspect of the present disclosure. In particular,FIG. 9illustrates a process900for setting up a radio bearer at a UE. The radio bearer may be used to serve an EPS bearer. The process900may include mapping a first set of one or more QoS parameters for serving the EPS bearer over a WWAN to a second set of one or more QoS parameters for serving the EPS bearer over a WLAN. This mapping may occur to accommodate the offloading of bearer traffic from the WWAN to the WLAN (e.g., in load management scenarios). In cases where a radio resource control (RRC) layer is managing whether bearer traffic is sent over WLAN or WWAN, or even when the actual bearer selection management is not handled by RRC, signaling may be used to define the mapping between the WWAN QoS parameters and the WLAN QoS parameters for the bearer.

In the example ofFIG. 9, an RRC WWAN interworking radio bearer configuration procedure may be defined in connection with the transmission of an RRC Connection Reconfiguration message920(e.g., as defined in LTE) from the eNodeB905to the UE915. For example, the RRC Connection Reconfiguration message920may instruct the UE915to set up or modify radio bearers for serving EPS bearer data. The RRC Connection Reconfiguration message920may be adapted to enable the eNodeB905to configure the radio bearers of the UE915to be served as either WWAN (e.g., LTE network) only, WLAN only, or RLC aggregation of WWAN and WLAN. The RRC Connection Reconfiguration message920may be further adapted to provide a mapping of the WWAN QoS parameter(s) (e.g., a logical channel priority associated with the QCI of the EPS bearer) of the radio bearer to a WLAN AC class or other type of WLAN QoS parameter(s). Because each EPS bearer may be correlated one-to-one with a radio bearer of the UE915, by mapping the radio bearer to a WLAN AC class the eNodeB905may also map an associated EPS bearer to that WLAN AC class.

As shown inFIG. 9, the eNodeB905may transmit the RRC Connection Reconfiguration message920to the UE915over an air interface. Once the RRC connection reconfiguration has taken place at the UE915, the UE915may update925its bearers, perform930QCI to AC mapping in accordance with the received mapping data, and transmit a RRC Connection Reconfiguration Complete message935to the eNodeB905to indicate that reconfiguration of the bearers is complete.

FIG. 10is a block diagram conceptually illustrating an example of an RRC message transmitted from an eNodeB to a UE, in accordance with an aspect of the present disclosure. In particular,FIG. 10shows one example of the format of an RRC Connection Reconfiguration message920adapted to convey RRC WWAN interworking radio bearer configuration to the UE915. The RRC Connection Reconfiguration Message920may include a message type field1005identifying the message as a RRC Connection Reconfiguration message, an RRC transaction ID field1010, and a RRC Connection Reconfiguration field1015.

The RRC Connection Reconfiguration field1015may include a number of optional information elements, including a measConfig information element, a mobilityControlInfo information element, a dedicatedInfoNASList, a radioResourceConfigDedicated information element, a securityConfigHO information element, a noncriticalExtension information element, a lateNonCriticalExtension information element, a nonCriticalExtension information element, an otherConfig information element, a fullConfig information element, and/or other information elements.

For the sake of clarity of illustration, the RRC Connection Reconfiguration Message920is shown with only a RadioResourceConfigDedicated information element1020. The RadioResourceConfigDedicated information element1020may include a number of information elements related to configuring a radio bearer at the UE915. The radio bearer may serve an EPS bearer. When configuring a radio bearer to serve an EPS bearer as a data radio bearer (DRB), the RadioResourceConfigDedicated information element1020may include a drb-ToAddModList information element1025containing information about the DRB configuration.

The drb-ToAddModList information element1025may include, for example, an eps-BearerIdentity information element1030to identify the EPS bearer that the radio bearer is serving, a drb-Identity information element1035identifying and labeling the radio bearer, a pdcp-Config information element1040containing Packet Data Convergence Protocol (PDCP) information, an rlc-Config information element (not shown) containing RLC information for the radio bearer, a logicalChannelIdentity information element containing an identity of the logical channel associated with the radio bearer, and a logicalChannelConfig information element containing logical channel configuration information.

In additional to the above described parameters, the drb-ToAddModList information element1025ofFIG. 10may include, for each data radio bearer being set up, a bearer-Type information element1045and a wlan-AC information element1050that define the interworking between WWAN (e.g., LTE communication network) and WLAN access networks for the newly configured radio bearer or modifying existing radio bearer. Specifically, the bearer-Type information element1045may be an optional information element that is present when the bearer is capable of being transmitted over both WWAN and WLAN. The bearer-Type information element1045may select an enumerated option indicating whether traffic for the corresponding radio bearer is to be transmitted over WWAN only, WLAN only, or if the bearer traffic can be served over an aggregation of both LTE and WLAN.

If the bearer-type information element1045indicates the WLAN only or WWAN-WLAN split routing of the radio bearer, the wlan-AC information element1050may provide a WLAN AC to be associated with the radio bearer when the radio bearer is switched between WWAN and WLAN to maintain a level of QoS. Thus, the wlan-AC information element1050may specify one of AC_BK, AC_BE, AC_VI, or AC_VO that may be associated with a QCI of WWAN radio bearer according to the principles described elsewhere in this specification. Additionally or alternatively, the wlan-AC may specify a PCP or other WLAN QoS parameter that may be associated with a QCI of WWAN radio bearer to use for the bearer.

Returning to the example ofFIG. 9, upon receiving the RRC Connection Reconfiguration message920from the eNodeB905, the UE915may perform the procedures defined in 3GPP TS 36.331 to set up the dedicated radio bearer. In addition, the UE915may identify each drb-Identity value included in the drb-ToAddModList information element1025that is not a part of the current UE configuration. For any drb-Identity values not part of the current UE configuration, the UE915may determine whether the drb-ToAddModList information element1025includes the bearer-Type information element1045described with reference toFIG. 10. If the bearer-Type information element1045is present, the UE915may set the routing of the newly established bearer to WWAN only, WLAN only, or a split of WWAN and WLAN according to the contents of the bearer-Type information element1045. If the bearer-Type information element1045is set to WLAN only or to a split between WWAN and WLAN, the UE915may set the WLAN AC to use for sending the data for that bearer over WLAN according to the wlan-AC information element1050. If the bearer-Type information element1045is not present in the drb-ToAddModList information element1025or elsewhere in the RRC Connection Reconfiguration message920, the UE915may set the routing of the newly established bearer to LTE only.

Additionally or alternatively, the UE915may identify one or more drb-Identity values in the drb-ToAddModList information element1025which are already a part of the current UE configuration. The drb-ToAddModList information element1025may specify parameters for reconfiguring the radio bearers associated with these known drb-Identity values. Thus, for each radio bearer represented in the drb-ToAddModList information element1025that is part of the current UE configuration, the UE915may reconfigure the routing of that radio bearer to LTE only, WLAN only, or a LTE-WLAN split in accordance with the bearer-Type information element1045. In addition, for radio bearers reconfigured to route traffic over WLAN, the UE915may set the WLAN QoS parameters for transmitting traffic of that bearer over WLAN to the WLAN AC defined by the wlan-AC information element1050.

FIG. 11is a block diagram conceptually illustrating an example of communications between nodes of a telecommunications system, in accordance with an aspect of the present disclosure. In particular,FIG. 11shows an example of a process1100for UE-requested PDN connectivity during which a set of one or more WLAN QoS parameters for an EPS bearer is established and mapped at a non-access stratum (NAS) layer. The process1100may allow a UE1115to utilize NAS signaling to request connectivity to a PDN over a default EPS bearer. In certain examples, the process1100may trigger one or more multiple dedicated bearer establishment procedures for the UE1115.

The process1100may begin with the UE1115transmitting a NAS PDN connectivity request message1145to the MME1135via eNodeB1105. The NAS PDN connectivity request message1145may optionally include a set of one or more requested WLAN QoS parameters for the new PDN connection. For example, the NAS PDN connectivity request message1145may indicate the WLAN AC or other WLAN QoS parameters associated with the PDN connection in an information element of the NAS PDN connectivity request message1145. In one example, the UE1115may request an internet connection with a QCI of 6 for WWAN, determine that the QCI of 6 is mapped to AC-BE for WLAN, and include the requested AC-BE WLAN QoS parameters in the NAS PDN connectivity request message1145.

The MME1135may allocate an EPS bearer ID to the requested PDN connection and send a create session request message1150to a serving gateway1120. The create session request message1150may include information about the requested PDN connection, including the EPS bearer ID selected by the MME1135. The serving gateway1120may create a new entry in its EPS bearer table, transmit a create session request message1155to a PDN gateway1125to establish the new connection at the PDN (not shown). The serving gateway1120may receive a create session response message1160from the PDN gateway1125indicating that the PDN connection has been established, and transmit a create session response message1165to the MME1135.

Upon receiving the create session response message1165, the MME1135may determine1170a set of WLAN QoS parameters for the new EPS bearer. For example, the MME1135may select a WLAN AC and/or PCP for the new EPS bearer based on characteristics of the new PDN connection to be serviced by the EPS bearer. In certain examples, the MME1135may select the WLAN QoS parameters based on the set of WLAN QoS parameters included in the NAS PDN connectivity request message1145. In other examples, the MME1135may determine the WLAN QoS parameter(s) based on a static or semi-static mapping defined by a standard or implementation-specific feature. In still additional or alternative examples, the MME1135may determine the WLAN QoS parameters based on a communication from another device from within or outside of the evolved packet core. For example, a device outside of the evolved packet core may maintain a table mapping WWAN QoS parameters to WLAN QoS parameters and provide the mapping data to the MME1135as a service or update.

The MME1135may then transmit a bearer setup request message1175via an S1 interface or a PDN connectivity accept message1180via the NAS layer to an eNodeB1105. The bearer setup request message1175and/or the PDN connectivity accept message1180may include one or more WWAN QoS parameters determined for the EPS bearer (e.g., a QCI) and the WLAN QoS parameters determined for the EPS bearer associated with the WWAN QoS parameters. The UE1115may additionally or alternatively receive the QCI over the NAS layer from the MME. Alternatively, the MME1135may not provide the WLAN QoS parameters for the EPS bearer, and the eNodeB1105may determine the WLAN QoS parameters for the EPS bearer using an operations, administration, and management (OAM) service based on the QCI of the EPS bearer. For example, the eNodeB1105may utilize the WLAN QoS parameters received in the NAS PDN connectivity request message1145to determine WLAN QoS of the radio bearer for serving the EPS bearer.

Upon receiving the bearer setup request message1175and/or PDN connectivity accept1180, the eNodeB1105may transmit an RRC Connection Reconfiguration message1185to the UE1115to set up the radio bearer serving the EPS bearer. The RRC Connection Reconfiguration message1185may include the WLAN QoS parameters selected for the EPS bearer which correspond to the radio bearer serving the EPS bearer. Following the setup of the radio bearer, the UE1115may transmit an RRC Connection Reconfiguration Complete message1190to the eNodeB1105, which may in turn transmit a bearer setup response message1195to the MME1135. The NAS layer of the UE may build a PDN connectivity complete message including the EPS bearer identity, then send the PDN connectivity complete message to the eNodeB as a direct transfer1197message. The eNodeB1105may forward the received PDN connectivity complete1199message to the MME635.

It will be understood that the functionality of a UE1115indicating a requested set of WLAN QoS parameters for an EPS bearer may be performed using other types of NAS signaling. For example, the UE1115may request a set of WLAN QoS parameters for an EPS bearer using an attach request (e.g., indicating the requested WLAN QoS parameters in an ESM message container), a bearer resource allocation request message to activate a dedicated bearer (as opposed to the illustrated PDN connectivity request for activating a default bearer), or a modify bearer context request message. Similarly, the MME1135may set the WLAN QoS parameters for the EPS bearer using other types of NAS signaling. For example, the MME1135may set the WLAN AC or PDP for an EPS using an activate default EPS bearer context request message to activate the default bearer or a bearer resource modification request to modify a dedicated bearer.

In still other examples, a device other than the MME1135may perform the functionality of determining the WLAN QoS parameters for the EPS bearer. For example, during the process1100ofFIG. 11, the serving gateway1120or PDN gateway1125may perform the functionality of determining1170the WLAN QoS parameters and transmit the determined WLAN QoS parameters in its respective create session response message1160,1165. In still other examples, a device such as a serving GPRS support node (SGSN) for non-LTE general packet radio service (GPRS) devices may also perform the functionality of determining1170the WLAN QoS parameters for EPS bearers implemented over non-LTE air interfaces. In such examples, the SGSN may transmit the WLAN QoS parameters over an Iu interface to a radio network controller or other GPRS entity for use by a mobile GPRS device in transmitting evolved packet core bearer related traffic over WLAN.

It will be further understood that while the present example is given in the context of an LTE system, similar processes may be performed in other systems to set up and map WLAN QoS parameters to an EPS bearer. For example, a UMTS system may utilize a PDP context activation procedure in a similar manner to map the WLAN QoS parameters to a new EPS bearer (e.g., the UE may signal a requested set of WLAN QoS parameters for the new PDP context using a PDP context activation message).

FIG. 12is a block diagram conceptually illustrating an example of communications between nodes of a telecommunications system, in accordance with an aspect of the present disclosure. Specifically,FIG. 12illustrates a diagram of another example of a process1200for determining and signaling WLAN QoS parameters for a bearer. In the process1200, an Operations, Administration, and Management (OAM) server1210may determine1220a mapping between WWAN QoS parameters (e.g., QCI) and WLAN parameters (e.g., AC, PCP) for evolved packet core bearers. The OAM server1210may provide1225the new/updated WLAN QoS to an eNodeB1205. In certain examples, the OAM server1210may create and/or update a list or table stored or to be stored by the eNodeB1205. The list or table may include mappings between WWAN QoS parameters and WLAN QoS parameters for evolved packet core bearers. The download may occur periodically (e.g., every 24 hours) or in response to a trigger (e.g., a change to the table is detected at the OAM server1210). The eNodeB1205may then communicate with a UE1215, using the downloaded WLAN QoS parameters to configure the WLAN QoS parameters of radio bearers supporting the evolved packet core bearers. This communication may include the exchange of RRC Connection Reconfiguration1230and RRC Connection Reconfiguration Complete messages1235, or other RRC messages, consistent with the principles ofFIGS. 9-10.

FIG. 13is a block diagram conceptually illustrating an example of communications between nodes of a telecommunications system, in accordance with an aspect of the present disclosure. Specifically,FIG. 13illustrates a process1300for determining and signaling WLAN QoS parameters for a bearer. In the process1300, an open mobile alliance device management (OMA DM) server1305may determine1310a mapping between WWAN QoS parameters (e.g., QCI) and WLAN parameters (e.g., AC, PCP) for bearers. The OMA DM server1305may provide1320the new or updated WLAN QoS parameters to a UE1315-1. For example, the new or updated WLAN QoS parameters may be in the form of a newly created list or table for storage by the UE1315. In certain examples, the OMA DM server1305may update a list or table stored by the UE1315of mappings between WWAN QoS parameters and WLAN QoS parameters for evolved packet core or radio bearers. The updated WLAN QoS parameters may be provided periodically (e.g., every 24 hours) or in response to a trigger (e.g., upon attaching to a new network). The UE1315may use the stored mapping data to determine and signal the WLAN QoS for bearer traffic transmitted by the UE1315over WLAN. In alternative embodiments, the UE1315may retrieve the stored mapping data from a universal subscriber identity module (USIM) or other device.

FIG. 14is a block diagram conceptually illustrating an example of a UE1415, in accordance with an aspect of the present disclosure. The UE1415may be an example of one or more of the UEs described with reference to other Figures. The UE1415may include a processor1405, a memory1410, a WLAN QoS determining module1420, a WLAN QoS signaling module1425, a WWAN radio1430, and a WLAN radio1435. Each of these components may be in communication, directly or indirectly.

The processor1405may be configured to execute code stored by memory1410to implement one or more aspects of the WLAN QoS determining module1420, the WLAN QoS signaling module1425, the WWAN radio1430, or the WLAN radio1435. The processor1405may also execute code stored by the memory1410to execute other applications1418.

The WLAN QoS determining module1420may be configured to identify a first set of one or more QoS parameters (e.g., a QCI) for serving a bearer over a wireless wide area network (WWAN). The first set of one or more QoS parameters may be received from another device (e.g., from or by way of an eNodeB). The WLAN QoS determining module1420may be further configured to determine a second set of one or more QoS parameters for serving the bearer over a wireless local area network (WLAN) based on an association between the first set of QoS parameters and the second set of QoS parameters. The association between the first set of QoS parameters and the second set of QoS parameters may be stored locally in the memory1410as the QoS mapping1419shown inFIG. 14, and/or received from an external device as described with reference to the previous Figures. Alternatively, the QoS mapping1419may be stored in a USIM module (not shown) communicatively coupled with or integrated into the UE1415. The WLAN QoS signaling module1425may be configured to receive the second set of QoS parameters from one or more external devices and/or signal the WLAN QoS parameters to a WLAN AP (as a PCP in an IEEE 802.11q header or an AC in an IP header).

The WWAN radio1430may be configured to communicate with WWAN base stations (e.g., one or more of the WWAN base stations and/or eNodeBs described in other Figures) over one or more carriers of a cellular WWAN (e.g., LTE/LTE-A, eHRPD, EV-DO, 1×/HRPD, etc.). The WLAN radio1435may be configured to communicate with WLAN access points (e.g., WLAN access points107) over one or more carriers of a WLAN. As discussed above, the WWAN radio1430may transmit and receive data related to one or more bearers of the WWAN using a set of one or more WLAN QoS parameters. The set of WLAN QoS parameters may be mapped to one or more WWAN QoS parameters according to the QoS mapping1419stored in the memory1410and/or received from an external network device.

FIG. 15is a block diagram illustrating an example of an eNodeB1505or other base station, in accordance with an aspect of the present disclosure. The eNodeB1505may be an example of one or more of the eNodeBs and/or other WWAN base stations described with reference to other Figures. The eNodeB1505may include a processor1501, a memory1510, a WLAN QoS determining module1520, a WLAN QoS signaling module1525, a WWAN radio1530, and a backhaul core network interface1535. Each of these components may be in communication, directly or indirectly.

The processor1501may be configured to execute code stored by memory1510to implement one or more aspects of the WLAN QoS determining module1520, the WLAN QoS signaling module1525, the WWAN radio1530, or the backhaul core network interface1535. The processor1501may also execute code stored by the memory1510to execute other applications1518.

The WLAN QoS determining module1520may be configured to identify a first set of one or more QoS parameters (e.g., a QCI) for serving a bearer over a wireless wide area network (WWAN). The first set of one or more QoS parameters may be received from another device (e.g., from or by way of a MME, a serving gateway, a UE, or another device). The WLAN QoS determining module1520may be further configured to determine a second set of one or more QoS parameters for serving the bearer over a wireless local area network (WLAN) based on an association between the first set of QoS parameters and the second set of QoS parameters. The association between the first set of QoS parameters and the second set of QoS parameters may be stored locally in the memory1510as the QoS mapping1519shown inFIG. 15, and/or received from an external device as described with reference to the other Figures. The WLAN QoS signaling module1525may be configured to receive the second set of QoS parameters from one or more external devices and/or signal the WLAN QoS parameters to a UE.

The WWAN radio1530may be configured to communicate with UEs over one or more carriers of a cellular WWAN (e.g., LTE/LTE-A, eHRPD, EV-DO, 1×/HRPD, etc.). The backhaul core network interface1535may be configured to other eNodeBs and an evolved packet core network.

FIG. 16is a flowchart conceptually illustrating an example of a method1600of wireless communication, in accordance with an aspect of the present disclosure. Specifically,FIG. 16illustrates a method1600of managing wireless communications in a wireless communication system. The method1600may be performed, for example, by one or more of the UEs, eNodeBs, MMEs, serving gateways, PDN gateways, or other devices described with reference to the other Figures.

At block1605, a first set of one or more QoS parameters for serving a bearer over a WWAN may be identified at a first device. At block1610, a second set of one or more QoS parameters for serving the bearer over a WLAN may be determined at the first device. The second set of QoS parameters may be determined based on an association between the first set of QoS parameter and the second set of QoS parameters.

FIG. 17is a flowchart conceptually illustrating an example of a method1700of wireless communication, in accordance with an aspect of the present disclosure. Specifically,FIG. 16illustrates a method1700of managing wireless communications in a wireless communication system. The method1700may be performed, for example, by one or more of the UEs described with reference to other Figures.

At block1705, a QCI parameter associated with serving a bearer over a WWAN may be received at the UE (e.g., in a RRC or NAS message). At block1710, the QCI parameter may be mapped to a WLAN AC based on an association between the QCI and the WLAN AC. At block1715, the UE may transmit traffic related to the bearer over WLAN according to the mapped WLAN AC.

FIG. 18is a flowchart conceptually illustrating an example of a method1800of wireless communication, in accordance with an aspect of the present disclosure. Specifically,FIG. 16illustrates a method1800of managing wireless communications in a wireless communication system. The method1800may be performed, for example, by one or more of the UEs described with reference to other Figures.

At block1805, a bearer establishment or modification procedure may be performed at the UE. At block1810, the UE may receive a QCI parameter of the bearer over a WWAN in connection with the establishment or modification of the bearer. At block1815, the UE may receive an RRC message containing a WLAN AC parameter based on a predetermined association between the QCI and the WLAN AC. At block1820, the UE may transmit traffic to the bearer over the WLAN according to the WLAN AC.

FIG. 19is a flowchart conceptually illustrating an example of a method1900of wireless communication, in accordance with an aspect of the present disclosure. Specifically,FIG. 19illustrates a method1900of managing wireless communications in a wireless communication system. The method1900may be performed, for example, by one or more of the eNodeBs described with reference to other Figures.

At block1905, a bearer establishment or modification procedure may be performed at the eNodeB. At block1910, the eNodeB may identify a QCI parameter of the bearer in connection with the bearer establishment or modification procedure. At block1915, the eNodeB may map the QCI parameter of the bearer to a WLAN AC parameter for the bearer based on a predetermined association between the QCI parameter and the WLAN AC. At block1920, the eNodeB may transmit (e.g., in a RRC or NAS message) the WLAN AC parameter for the bearer to a UE associated with the bearer.