EP3272154B1 - Techniken zur verwaltung der leistungsbetriebsarten eines benutzergeräts bei der kommunikation mit mehreren funkzugangstechnologien - Google Patents

Techniken zur verwaltung der leistungsbetriebsarten eines benutzergeräts bei der kommunikation mit mehreren funkzugangstechnologien Download PDF

Info

Publication number
EP3272154B1
EP3272154B1 EP16711491.7A EP16711491A EP3272154B1 EP 3272154 B1 EP3272154 B1 EP 3272154B1 EP 16711491 A EP16711491 A EP 16711491A EP 3272154 B1 EP3272154 B1 EP 3272154B1
Authority
EP
European Patent Office
Prior art keywords
connection
operation mode
power operation
over
wlan
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP16711491.7A
Other languages
English (en)
French (fr)
Other versions
EP3272154A1 (de
Inventor
Umang Sureshbhai Patel
Arnaud Meylan
Sivaramakrishna Veerepalli
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Inc filed Critical Qualcomm Inc
Publication of EP3272154A1 publication Critical patent/EP3272154A1/de
Application granted granted Critical
Publication of EP3272154B1 publication Critical patent/EP3272154B1/de
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0215—Traffic management, e.g. flow control or congestion control based on user or device properties, e.g. MTC-capable devices
    • H04W28/0221—Traffic management, e.g. flow control or congestion control based on user or device properties, e.g. MTC-capable devices power availability or consumption
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
    • H04W52/0216—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave using a pre-established activity schedule, e.g. traffic indication frame
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0229—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0251—Power saving arrangements in terminal devices using monitoring of local events, e.g. events related to user activity
    • H04W52/0258—Power saving arrangements in terminal devices using monitoring of local events, e.g. events related to user activity controlling an operation mode according to history or models of usage information, e.g. activity schedule or time of day
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H04W76/16—Involving different core network technologies, e.g. a packet-switched [PS] bearer in combination with a circuit-switched [CS] bearer
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present disclosure for example, relates to wireless communication systems, and more particularly to techniques for managing power operation modes of a user equipment (UE) communicating with a plurality of radio access technologies (RATs).
  • UE user equipment
  • RATs radio access technologies
  • Wireless communication networks are widely deployed to provide various communication services such as voice, video, packet data, messaging, broadcast, etc. These wireless networks may be multiple-access networks capable of supporting multiple users by sharing the available network resources. Examples of such multiple-access networks include Code Division Multiple Access (CDMA) networks, Time Division Multiple Access (TDMA) networks, Frequency Division Multiple Access (FDMA) networks, Orthogonal FDMA (OFDMA) networks, and Single-Carrier FDMA (SC-FDMA) networks.
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal FDMA
  • SC-FDMA Single-Carrier FDMA
  • a wireless communication network may include a number of base stations (e.g., eNodeBs) that can support communication for a number of user equipments (UEs).
  • UE user equipments
  • a UE may communicate with a base station via the downlink and uplink.
  • the downlink (or forward link) refers to the communication link from the base station to the UE
  • the uplink (or reverse link) refers to the communication link from the UE to the base station.
  • UEs can be equipped to communicate in wireless local area networks (WLAN) by accessing one or more hotspots using a wireless communication technology, such as 802.11 (Wi-Fi).
  • a UE can communicate with a radio access network (RAN) of a wireless wide area network (WWAN) (e.g., a cellular network) along with a RAN of one or more WLANs.
  • the UE can include a receiver operable for communicating with the RAN of the WWAN (e.g., a long term evolution (LTE), universal telecommunications mobile system (UMTS), or similar receiver) and another receiver operable for communicating with the RAN of the WLAN (e.g., an 802.11 Wi-Fi receiver).
  • LTE long term evolution
  • UMTS universal telecommunications mobile system
  • the UE may additionally or alternatively include a single receiver operable for communicating with both RANs (e.g., WWAN and WLAN).
  • RANs e.g., WWAN and WLAN
  • connections over the WWAN and WLAN can be aggregated (e.g., at a media access control (MAC), packet data convergence protocol (PDCP) or similar layers), which can be referred to as "RAN aggregation,” such to provide simultaneous access to one or more network nodes, to offload traffic from the WWAN to WLAN or vice versa, and/or the like.
  • MAC media access control
  • PDCP packet data convergence protocol
  • RAN aggregation such to provide simultaneous access to one or more network nodes, to offload traffic from the WWAN to WLAN or vice versa, and/or the like.
  • the WWAN access point schedules downlink communications over the WWAN and WLAN connections for a given UE, and the UE communicates with the WWAN RAN over the WWAN connection and the WLAN RAN over the WLAN connection.
  • the WLAN access point can then communicate data, scheduled by the WWAN, between the UE and the WWAN access point.
  • data packets from the WWAN and WLAN connections may be split and received out of order at the UE; thus, the UE can reorder out-of-order packets at the MAC, RLC or PDCP layer based on a sequence number associated with the data packets received over the independent WWAN and WLAN connections.
  • the UE may enter a power operation mode (e.g., idle mode) over one or more of the connections to save power consumption, scan other channels (e.g., to locate an access point with better radio conditions), etc.
  • a power operation mode e.g., idle mode
  • scan other channels e.g., to locate an access point with better radio conditions
  • the UE may not have sufficient time to switch to a different power operation mode (e.g., connected mode) to receive data packets over the one or more of the connections to properly perform reordering of the received data packets.
  • UE may request the data packets to be resent, which may cause unnecessary wasting of resources of the wireless networks.
  • US 2013/0242843 A1 describes a wireless communication system with a plurality of wireless interfaces and the possibility of link aggregation over the plurality of these interfaces according to the operational state of the interfaces and a preferability of link aggregation.
  • US 2015/0029917 A1 describes a wireless communication system with multi carrier and/or carrier aggregation support.
  • a terminal When predetermined conditions are satisfied, a terminal may be operated in mode, in which an otherwise necessary inter-frequency measurement is not performed .
  • the present disclosure provides a method for wireless communications according to independent claim 1.
  • the present disclosure also provides an apparatus for wireless communication according to independent claim 15.
  • a wireless device e.g., user equipment (UE)
  • UE user equipment
  • the second access point which may be a part of a different radio access network (RAN) than the first access point, can enable communication between the first network and a wireless device by communicating with the first access point (e.g., over a backhaul link).
  • RAN radio access network
  • the wireless device can connect to the first access point and the second access point, using the first and second RATs respectively, to access the first wireless network.
  • Packets may be concurrently communicated to the wireless device from the first and second access points, and may arrive and be processed by the wireless device out of order. Accordingly, the wireless device may reorder the packets based at least in part on a sequence number indicated for each packet received from the first and second access points.
  • the reordering of packets or other data units may occur at one or more network layers, such as a media access control (MAC) layer, radio link control (RLC) layer, packet data convergence protocol (PDCP) layer, internet protocol (IP) layer, transmission control protocol (TCP) or TCP/IP layer, user datagram protocol (UDP) or UDP/IP layer, an application layer, etc.
  • MAC media access control
  • RLC radio link control
  • PDCP packet data convergence protocol
  • IP internet protocol
  • TCP transmission control protocol
  • UDP user datagram protocol
  • UDP User Datagram protocol
  • the wireless device may enter a power operation mode over a connection with the first or second access point.
  • the power operation mode can relate to a power saving mode or other mode during which the wireless device may cease communicating.
  • the power operation mode can include suspending radio resources of the wireless device for the related connection during certain time periods, such that signals cannot be received or transmitted during the time period. This, however, may inhibit packet reordering at the wireless device because some packets may not be received over the connection in the power operation mode, and the first and/or second access point that has an active connection with the wireless device may not know the other connection is in the power operation mode.
  • the packet reordering may be interrupted, and packets may be dropped if the packets are not received and reordered within a certain time period.
  • a wireless device may decide to enter a power operation mode over a connection with an access point to save power (e.g., based at least in part on detecting data transmit/receive traffic inactivity over the connection, determining to scan to discover other access points on different channels during periods of time defined by the power operation mode, etc.).
  • the access point may buffer the packets destined to the wireless device until the packets are requested or the device otherwise exits the power operation mode.
  • the access point may keep a traffic indication map (TIM) bit set in beacons for the wireless device in the power operation mode to notify the wireless device about buffered data packets.
  • TIM traffic indication map
  • PS-Poll power save-poll
  • beacon transmission interval e.g., 100 milliseconds (ms) in Wi-Fi
  • data packet arrival time at the access point with respect to a next beacon transmission delayed beacon transmission due to the transmission medium being busy at the target beacon transmission time (TBTT) at the access point
  • wireless device behavior to skip some beacons when in the power operation mode e.g., some wireless devices may process beacons only at multiple of delivery traffic indication map (DTIM) intervals, missed/lost beacons (e.g., due to collision on the transmission medium), time taken for PS-Poll handshake or for an indication to exit the power operation mode indication from the wireless device to the access point, etc.
  • DTIM delivery traffic indication map
  • a reordering timeout on the wireless device may be a smaller value than the varying buffering duration on the access point when the wireless device is in the power operation mode (e.g., 65ms). This may cause frequent reorder timeouts on the wireless device when packets (e.g., PDCP packets) on the other aggregated connection are received, but packets sent over the connection in the power operation mode are delayed due to buffering at the access point and there are one or more packets in the reorder queue.
  • the reorder timeout may cause flushing of packets from reorder queue to upper layers (e.g., flushing of PDCP packets to UDP/IP, TCP/IP, etc.
  • flushing of packets may be triggered when the memory used by packets to be reordered becomes too large. Buffered PDCP packets from the access point may likely ultimately reach the wireless device, but this may be after the reorder timeout after which the wireless device's PDCP layer reorder window moves, and the delayed PDCP packets are no longer used and are dropped. In addition, any amount of reordering may increase processing burden at the wireless device, which may have a negative impact on device power, and/or may require additional memory to temporarily store out-of-order packets.
  • aspects described herein relate to avoiding such packet losses over aggregated connections that allow power operation modes.
  • Various mechanisms can be used at the wireless device and/or access point to handle power operation modes to receive packets transmitted over related connections. For example, a wireless device receiving communications over a first connection from a first access point can determine whether a second connection with a second access point is in a power operation mode.
  • the power operation mode can include substantially any full power or limited power operation mode, such as a connected mode where the second connection has active resources for communicating with the access point, an idle mode where the second connection may be limited to periodically receiving paging signals over certain resources, a sleep or powered off mode where a transceiver, or other radio frequency (RF) front end components, related to the second connection are powered down for a period of time, etc.
  • a connected mode where the second connection has active resources for communicating with the access point
  • an idle mode where the second connection may be limited to periodically receiving paging signals over certain resources
  • a sleep or powered off mode where a transceiver, or other radio frequency (RF) front end components, related to the second connection are powered down for a period of time, etc.
  • RF radio frequency
  • the wireless device may determine the power operation mode for the second connection by exiting or switching the power operation mode for the second connection (e.g., to a connected mode or other full power mode) based on one or more aspects of communications over the first and/or second connection (e.g., aspects related to receiving communications over the first connection, reordering of received packets, determining tolling or expiration of timers related to receiving communications over the first connection, receiving a control packet, etc.).
  • aspects of communications over the first and/or second connection e.g., aspects related to receiving communications over the first connection, reordering of received packets, determining tolling or expiration of timers related to receiving communications over the first connection, receiving a control packet, etc.
  • the one or more aspects of communication may correspond to an indication of a power consumption mode over the first and/or second connection
  • the indication of the power consumption mode may include substantially any indication that power is being used by the wireless device over the first and/or second connection, such as a reorder status related to reordering packets received over the first connection and/or the second connection, an indication or determination of a time remaining for a packet reorder timer, an indication or determination as to whether packets received over the first connection and/or the second connection are successfully reordered, an indication or determination as to whether a discontinuous receive (DRX) inactivity timer of the first RAT related to entering another power operation mode for the first RAT following expiration of the DRX inactivity timer is tolling, an indication or determination as to whether an on-duration timer of the first RAT related to exiting another power operation mode for the first RAT following expiration of the on-duration timer is expired, receiving a downlink transmission over the first connection, receiving a control packet over
  • DRX
  • the first access point can determine whether the second connection is in a power operation mode (e.g., based on information from the second access point) and can accordingly avoid providing data to the second access point for transmitting to the wireless device via the second connection.
  • the first access point can instruct the wireless device to exit the power operation mode over the second connection (e.g., by transmitting a control packet to the wireless device) and can accordingly provide data to the second access point for transmitting to the wireless device over the second connection.
  • a CDMA network may implement a radio technology such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc.
  • UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA.
  • cdma2000 covers IS-2000, IS-95 and IS-856 standards.
  • a TDMA network may implement a radio technology such as Global System for Mobile Communications (GSM).
  • GSM Global System for Mobile Communications
  • An OFDMA network may implement a radio technology such as Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, etc.
  • E-UTRA Evolved UTRA
  • UMB Ultra Mobile Broadband
  • IEEE 802.11 Wi-Fi
  • WiMAX IEEE 802.16
  • Flash-OFDMA Flash-OFDMA
  • UTRA and E-UTRA are part of UMTS.
  • 3GPP LTE and LTE-Advanced (LTE-A) are new releases of UMTS that use E-UTRA.
  • UTRA, E-UTRA, UMTS, LTE, LTE-A and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP).
  • cdma2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2).
  • the techniques described herein may be used for the
  • FIG. 1 is a block diagram conceptually illustrating an example of a wireless communications system 100, in accordance with aspects described herein.
  • the wireless communications system 100 includes base stations (or cells) 105, user equipment (UEs) 115, and a core network 130.
  • One or more of the base stations 105 can optionally include and/or can be coupled with a scheduling component 520, as described further herein, for determining when to schedule communications to one or more UEs 115 over multiple connections in traffic aggregation based on a power operation mode determined for at least one of the multiple connections.
  • One or more of the UEs 115 can optionally include and/or can be coupled with a communicating component 540, as described further herein, for managing a power operation mode over one or more of multiple connections in traffic aggregation to facilitate receiving communications over the one or more connections for reordering thereof.
  • the base stations 105 may communicate with the UEs 115 under the control of a base station controller (not shown), which may be part of the core network 130 or the base stations 105 in various embodiments.
  • the base stations 105 may communicate control information and/or user data with the core network 130 through first backhaul links 132.
  • the base stations 105 may communicate, either directly or indirectly, with each other over second backhaul links 134, which may be wired or wireless communication links.
  • the wireless communications system 100 may 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 link 125 may be a multi-carrier signal modulated according to the various radio technologies described above. 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 wireless communications system 100 may also support operation on multiple flows at the same time.
  • the multiple flows may correspond to multiple wireless wide area networks (WWANs) or cellular flows.
  • the multiple flows may correspond to a combination of WWANs or cellular flows and wireless local area networks (WLANs) or Wi-Fi flows.
  • WWANs wireless wide area networks
  • WLANs wireless local area networks
  • the base stations 105 may wirelessly communicate with the UEs 115 via one or more base station antennas. Each of the base stations 105 sites may provide communication coverage for a respective geographic coverage area 110.
  • base stations 105 may 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 geographic coverage area 110 for a base station 105 may be divided into sectors making up only a portion of the coverage area (not shown).
  • the wireless communications system 100 may include base stations 105 of different types (e.g., macro, micro, and/or pico base stations). There may be overlapping coverage areas for different technologies.
  • base stations 105-a may be base stations corresponding to a WWAN (e.g., LTE or UMTS macro cell, pico cell, femto cell, etc. base stations), and base stations 105-b may be base stations corresponding to a WLAN (e.g., Wi-Fi hotspot).
  • a single base station 105 can support communications over multiple RATs (e.g., LTE and Wi-Fi, LTE and UMTS, UMTS and Wi-Fi, etc.).
  • the wireless communications system 100 is an LTE/LTE-A network communication system.
  • the terms evolved Node B may be generally used to describe the base stations 105.
  • the wireless communications system 100 may be a Heterogeneous LTE/LTE-A network in which different types of eNodeBs provide coverage for various geographical regions.
  • each eNodeB 105 may provide communication coverage for a macro cell, a pico cell, a femto cell, and/or other types of cell.
  • a macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs 115 with service subscriptions with the network provider.
  • a pico cell may cover a relatively smaller geographic area (e.g., buildings) and may allow unrestricted access by UEs 115 with service subscriptions with the network provider.
  • a femto cell may cover a relatively small geographic area (e.g., a home) and, in addition to unrestricted access, may also provide restricted access by UEs 115 having an association with the femto cell (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 for users in the home, and the like).
  • An eNodeB 105 for a macro cell may be referred to as a macro eNodeB.
  • An eNodeB 105 for a pico cell may be referred to as a pico eNodeB.
  • an eNodeB 105 for a femto cell may be referred to as a femto eNodeB or a home eNodeB.
  • An eNodeB 105 may support one or multiple (e.g., two, three, four, and the like) cells.
  • the wireless communications system 100 may support use of LTE and WLAN or Wi-Fi by one or more of the UEs 115.
  • the core network 130 may communicate with the eNodeBs 105 or other base stations 105 via first backhaul links 132 (e.g., S1 interface, etc.).
  • the eNodeBs 105 may also communicate with one another, e.g., directly or indirectly via second backhaul links 134 (e.g., X2 interface, etc.) and/or via the first backhaul links 132 (e.g., through core network 130).
  • the wireless communications system 100 may support synchronous or asynchronous operation.
  • the eNodeBs 105 may have similar frame timing, and transmissions from different eNodeBs 105 may be approximately aligned in time.
  • the eNodeBs 105 may have different frame timing, and transmissions from different eNodeBs 105 may not be aligned in time.
  • the techniques described herein may be used for either synchronous or asynchronous operations.
  • the UEs 115 may be dispersed throughout the wireless communications system 100, and each UE 115 may be stationary or mobile.
  • a UE 115 may 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 UE 115 may 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.
  • PDA personal digital assistant
  • a UE 115 may be able to communicate with macro eNodeBs, pico eNodeBs, femto eNodeBs, relays, and the like.
  • the communication links 125 shown in the wireless communications system 100 may include uplink (UL) transmissions from a UE 115 to an eNodeB 105, and/or downlink (DL) transmissions, from an eNodeB 105 to a UE 115.
  • the downlink transmissions may also be called forward link transmissions while the uplink transmissions may also be called reverse link transmissions.
  • a UE 115 may be configured to support carrier aggregation (CA) with two or more eNodeBs 105.
  • CA carrier aggregation
  • the eNodeBs 105 that are used for carrier aggregation may be collocated or may be connected through fast connections. In either case, coordinating the aggregation of component carriers (CCs) for wireless communications between the UE 115 and the eNodeBs 105 may be carried out more easily because information can be readily shared between the various cells being used to perform the carrier aggregation.
  • CCs component carriers
  • coordinating the aggregation of component carriers may involve additional aspects.
  • some base stations 105 can support traffic aggregation such that base stations using different RATs can communicate to aggregate traffic from both base stations (e.g., for a given UE 115), which may be enabled based on carrier aggregation as described above.
  • UE 115-a can communicate with base station 105-a and base station 105-b
  • base station 105-b can communicate with base station 105-a to coordinate aggregation of traffic to/from UE 115-a from/to the base station 105-a for communicating to a related WWAN.
  • UE 115-a may support LTE and Wi-Fi communications using one or more transceivers.
  • traffic aggregation can be established for the UE 115-a such that UE 115-a communicates data for a first wireless network to base station 105-a and base station 105-b, which operate different RANs, using respective RATs.
  • Base station 105-b can provide the data to/from base station 105-a for communicating in the related first wireless network.
  • This configuration allows for increased throughput or other improved connectivity properties for the UE 115-a.
  • traffic aggregation in this regard may occur at one or more network layers having packets or data units with corresponding sequence numbers such that the packets or data units may be received out of order at the UE 115-a such that the UE 115-a can reorder the packets.
  • traffic aggregation may occur over a MAC layer, RLC layer, PDCP layer, IP layer, TCP or TCP/IP layer, UDP or UDP/IP layer, one or more application layers, etc.
  • FIG. 2 is a block diagram conceptually illustrating examples of an eNodeB 210 and a UE 250 configured in accordance with aspects described herein.
  • the base station/eNodeB 210 and the UE 250 of a system 200 may be one of the base stations/eNodeBs and one of the UEs in FIG. 1 , respectively.
  • base station/eNodeB 210 can optionally include and/or be coupled with a scheduling component 520, as described further herein, for determining when to schedule communications to one or more UEs 250 over multiple connections in traffic aggregation based on a power operation mode determined for at least one of the multiple connections.
  • the UE 250 can optionally include and/or be coupled with a communicating component 540, as described further herein, for managing a power operation mode over one or more of multiple connections in traffic aggregation to facilitate receiving communications over the one or more connections for reordering thereof.
  • the eNodeB 210 may support traffic aggregation, as described herein.
  • the UE 250 may also support traffic aggregation.
  • the UE 250 may receive configuration information for traffic aggregation from eNodeB 210 or other network entities.
  • the base station 210 may be equipped with antennas 234 1-t , and the UE 250 may be equipped with antennas 252 1-r , wherein t and r are integers greater than or equal to one.
  • a base station transmit processor 220 may receive data from a base station data source 212 and control information from a base station controller/processor 240.
  • the control information may be carried on the PBCH, PCFICH, physical hybrid automatic repeat/request (HARQ) indicator channel (PHICH), PDCCH, etc.
  • the data may be carried on the PDSCH, etc.
  • the base station transmit processor 220 may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively.
  • the base station transmit processor 220 may also generate reference symbols, e.g., for the PSS, SSS, and cell-specific reference signal (RS).
  • RS cell-specific reference signal
  • a base station transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, and/or the reference symbols, if applicable, and may provide output symbol streams to the base station modulators/demodulators (MODs/DEMODs) 232 1-t .
  • Each base station modulator/demodulator 232 may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream.
  • Each base station modulator/demodulator 232 may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal.
  • Downlink signals from modulators/demodulators 232 1-t may be transmitted via the antennas 234 1-t , respectively.
  • the UE antennas 252 1-r may receive the downlink signals from the base station 210 and may provide received signals to the UE modulators/demodulators (MODs/DEMODs) 254 1-r , respectively.
  • Each UE modulator/demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples.
  • Each UE modulator/demodulator 254 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols.
  • a UE MIMO detector 256 may obtain received symbols from all the UE modulators/demodulators 254 1-r , and perform MIMO detection on the received symbols if applicable, and provide detected symbols.
  • a UE reception processor 258 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 250 to a UE data sink 260, and provide decoded control information to a UE controller/processor 280.
  • a UE transmit processor 264 may receive and process data (e.g., for the PUSCH) from a UE data source 262 and control information (e.g., for the PUCCH) from the UE controller/processor 280.
  • the UE transmit processor 264 may also generate reference symbols for a reference signal.
  • the symbols from the UE transmit processor 264 may be precoded by a UE TX MIMO processor 266 if applicable, further processed by the UE modulator/demodulators 254 1-r (e.g., for SC-FDM, etc.), and transmitted to the base station 210.
  • the uplink signals from the UE 250 may be received by the base station antennas 234, processed by the base station modulators/demodulators 232, detected by a base station MIMO detector 236 if applicable, and further processed by a base station reception processor 238 to obtain decoded data and control information sent by the UE 250.
  • the base station reception processor 238 may provide the decoded data to a base station data sink 246 and the decoded control information to the base station controller/processor 240.
  • the base station controller/processor 240 and the UE controller/processor 280 may direct the operation at the base station 210 and the UE 250, respectively.
  • the UE controller/processor 280 and/or other processors and modules at the UE 250 may also perform or direct, e.g., the execution of the functional blocks illustrated in FIG. 5 , and/or other processes for the techniques described herein (e.g., flowcharts illustrated in FIGs. 6 and 8-10 ). In some aspects, at least a portion of the execution of these functional blocks and/or processes may be performed by block 281 in the UE controller/processor 280.
  • the base station memory 242 and the UE memory 282 may store data and program codes for the base station 210 and the UE 250, respectively. For example, the UE memory 282 may store configuration information for multiple connectivity provided by the base station 210 and/or another base station.
  • a scheduler 244 may be used to schedule UE 250 for data transmission on the downlink and/or uplink.
  • the UE 250 may include means for establishing a first connection with a first serving node using a first RAT, and establishing a second connection with a second serving node using a second RAT, means for receiving an indication of a power consumption mode for the first connection, and/or means for determining a power operation mode of the second connection based at least in part on the indication.
  • the aforementioned means may be (and/or may be coupled with) the UE controller/processor 280, the UE memory 282, the UE reception processor 258, the UE MIMO detector 256, the UE modulators/demodulators 254, and/or the UE antennas 252 configured to perform the functions recited by the aforementioned means.
  • the aforementioned means may be a module, component, or any apparatus configured to perform the functions recited by the aforementioned means. Examples of such modules, components, or apparatus may be described with respect to FIG. 5 .
  • the base station 210 may include means for serving a UE over a first connection using a first RAT, means for determining whether the UE is configured in a power operation mode associated with a second connection with an access point using a second RAT, means for scheduling data for the second connection during a first time interval based at least in part on the determination that the UE is configured in the power operation mode associated with the second connection, and/or means for scheduling data on the first connection and the second connection during a second time interval.
  • Base station 210 may also include means for communicating with the UE over a second connection via an access point that uses a second RAT, means for transmitting a control packet to the UE over the first connection or the second connection indicating to exit a power operation mode over the second connection, and/or means for scheduling data for transmission on the first connection and the second connection based at least in part on transmitting the control packet.
  • Base station 210 may further include means for determining whether the second connection is in a power operation mode based at least in part on receiving information from an access point indicating whether the second connection is in the power operation mode, and/or means for scheduling data for transmission on the first connection and the second connection based at least in part on whether the second connection is in the power operation mode.
  • the aforementioned means may be (and/or may be coupled with) the base station controller/processor 240, the base station memory 242, the base station reception processor 238, the base station MIMO detector 236, the base station modulators/demodulators 232, and/or the base station antennas 234 configured to perform the functions recited by the aforementioned means.
  • the aforementioned means may be a module, component, or any apparatus configured to perform the functions recited by the aforementioned means. Examples of such modules, components, or apparatus may be described with respect to FIG. 5 .
  • FIG. 3 is a block diagram conceptually illustrating an aggregation of radio access technologies at a UE, in accordance with aspects described herein.
  • the aggregation may occur in a system 300 including a multi-mode UE 315, which can communicate with an eNodeB 305-a using one or more component carriers 1 through N (CC 1 -CC N ), and/or with a WLAN access point (AP) 305-b using WLAN component carrier 340.
  • eNodeB 305-a can optionally include and/or be coupled with a scheduling component 520, as described further herein, for determining when to schedule communications to one or more UEs 315 over multiple connections in traffic aggregation based on a power operation mode determined for at least one of the multiple connections.
  • a multi-mode UE in this example may refer to a UE that supports more than one radio access technology (RAT).
  • RAT radio access technology
  • the UE 315 supports at least a WWAN radio access technology (e.g., LTE) and a WLAN radio access technology (e.g., Wi-Fi).
  • WWAN radio access technology e.g., LTE
  • WLAN radio access technology e.g., Wi-Fi
  • a multi-mode UE may also support carrier aggregation using one or more of the RATs.
  • the UE 315 may be an example of one of the UEs of FIG. 1 , FIG. 2 , FIG.
  • the eNodeB 305-a may be an example of one of the eNodeBs or base stations of FIG. 1 , FIG. 2 , FIG. 3 , FIG. 4 , and FIG. 5 . While only one UE 315, one eNodeB 305-a, and one AP 305-b are illustrated in FIG. 3 , it will be appreciated that the system 300 can include any number of UEs 315, eNodeBs 305-a, and/or APs 305-b. In one specific example, UE 315 can communicate with one eNB 305 over one LTE component carrier 330 while communicating with another eNB 305 over another component carrier 330.
  • the eNodeB 305-a can transmit information to the UE 315 over forward (downlink) channels 332-1 through 332-N on LTE component carriers CC 1 through CC N 330.
  • the UE 315 can transmit information to the eNodeB 305-a over reverse (uplink) channels 334-1 through 334-N on LTE component carriers CCi through CC N .
  • the AP 305-b may transmit information to the UE 315 over forward (downlink) channel 352 on WLAN component carrier 340.
  • the UE 315 may transmit information to the AP 305-b over reverse (uplink) channel 354 of WLAN component carrier 340.
  • eNB 305-a can configure UE 315 to utilize component carrier 330-1 (and/or component carriers 330-1 to 330-N) as well as WLAN component carrier 340 to communicate data to a network corresponding to eNB 305-a.
  • multiple WLAN component carriers 340 may be present.
  • traffic aggregation is provided by AP 305-b communicating traffic received over WLAN component carrier 340 to eNB 305-a and communicating traffic from eNB 305-a over WLAN component carrier 340 to UE 315.
  • eNB 305-a can utilize the various carriers (at least component carrier 330-1 and WLAN component carrier 340) to facilitate communication between UE 315 and a corresponding network.
  • UE 315 may also be configured to access another network related to AP 305-b or another WLAN AP. Because the described configuration may be agnostic to higher layers and/or a user of the UE 315, this may result in inconsistencies between expected and actual network discovery and selection for WLAN at the UE 315. Aspects described herein define operation of UE 315 where WLAN component carrier 340 supports traffic aggregation from UE 315 to eNB 305-a using the various component carriers 330-1 to 330-N and 340, where traffic aggregation can occur at one or more network layers, as described, to reorder packets or other data units that may be received out of sequence.
  • the nomenclature associated with a 3GPP LTE or LTE-A wireless network is used.
  • the system 300 can operate in other networks such as, but not limited to, an OFDMA wireless network, a CDMA network, a 3GPP2 CDMA2000 network and the like.
  • FIG. 4 is a block diagram conceptually illustrating an example of data paths 445-a and 445-b between the UE 415 and the EPC 480 in accordance with an aspect of the aspects described herein.
  • eNodeB 405 can optionally include and/or be coupled with a scheduling component 520, as described further herein, for determining when to schedule communications to one or more UEs 415 over multiple connections in traffic aggregation based on a power operation mode determined for at least one of the multiple connections.
  • UE 415 can optionally include and/or be coupled with a communicating component 540, as described further herein, for managing a power operation mode over one or more of multiple connections in traffic aggregation to facilitate receiving communications over the one or more connections for reordering thereof.
  • the data paths 445-a, 445-b are shown within the context of a wireless communications system 401 for aggregating traffic for transmitting using resources of eNodeBs 405 and WLAN AP 406.
  • This bearer configuration includes data path 445-a that traverses eNodeB 405, and a data path 445-b that traverses WLAN AP 406 and eNodeB 405 in traffic aggregation (e.g., RAN aggregation).
  • the system 200 of FIG. 2 may be an example of portions of the wireless communications system 401.
  • the wireless communications system 401 may include a UE 415, eNodeB 405, WLAN AP 406, an evolved packet core (EPC) 480, a PDN 440, and a peer entity 455.
  • the UE 415 may be configured to support traffic aggregation, as described herein, though the traffic aggregation can be controlled by eNodeB 405 and may be agnostic to upper layers of the UE 415.
  • the EPC 480 may include a mobility management entity (MME) 430, a serving gateway (SGW) 432, and a PDN gateway (PGW) 434.
  • a home subscriber system (HSS) 435 may be communicatively coupled with the MME 430.
  • the UE 415 may include an LTE radio 420 and a WLAN radio 425. It is to be appreciated that the UE 415 can include one or more such radios and/or the radios may be integrated. Thus, in an example, LTE radio 420 can also include a WLAN radio (or can be configured to process WLAN signals) in addition to the WLAN radio 425, and in this example, UE 415 includes two WLAN interfaces - one in the LTE radio 420 and one in the WLAN radio 425. These elements may represent aspects of one or more of their counterparts described above with reference to the previous or subsequent Figures. For example, the UE 415 may be an example of UEs in FIG. 1 , FIG. 2 , FIG. 3 , FIG.
  • the eNodeB 405-a may be an example of the eNodeBs/base stations of FIG. 1 , FIG. 2 , FIG. 3 , FIG. 5
  • WLAN AP 406 may be an example of the APs described in FIG. 1 , FIG. 3 , FIG. 5
  • the EPC 480 may be an example of the core network of FIG. 1 .
  • eNodeB 405-a may be capable of providing the UE 415 with access to the PDN 440, which may relate to one or more LTE component carriers, as described.
  • WLAN AP 406 may be capable of providing the UE 415 with access to the PDN 440 by traversing the eNodeB 405.
  • eNodeB 405 and WLAN AP 406 can communicate to aggregate traffic to/from UE 415.
  • the UE 415 may involve traffic aggregation where one connection is to a first access point (eNodeB 405) and the other connection is to a second access point (WLAN AP 406), where the second access point communicates with the first access point to aggregate traffic for the UE 415.
  • bearers and/or related component carriers (e.g., as in FIG. 3 ) established for the UE 415 with EPC 480 can be with the eNodeB 405 and/or the WLAN AP 406.
  • bearer selection can be configured where the UE 415 has separate bearers established between the EPC 408 and the eNodeB 405 and between the EPC 480 and the WLAN AP 406 (via eNodeB 405).
  • data traffic e.g., IP packets or other data units
  • bearers can map to carriers between the UE 415 and eNodeB 405/WLAN AP 406.
  • RLC/PDCP level aggregation can be configured where the UE 415 bearers are between the eNodeB 405 EPC 480 even for the WLAN AP 406 carriers.
  • data traffic e.g., IP packets
  • IP packets is aggregated at the RLC/PDCP level and communicated to UE 415 or respective carriers with the eNodeB 405 and WLAN AP 406.
  • downlink (DL) PDCP packets from eNodeB 405 to UE 415 can be split across LTE and WLAN connections for receipt by LTE radio 420 and WLAN radio 425.
  • eNodeB 405 can schedule DL PDCP packets over the WLAN (e.g. for traversing data path 445-b from eNodeB 405 to WLAN AP 406 to UE 415.
  • UE 415 may receive out-of-order PDCP packets as LTE and WLAN link layer transmissions happen independently.
  • UE 415 can be configured to reorder packets at PDCP layer (or other data units in other network layer in traffic aggregation, as described) based on sequence number, before sending packets to upper layers.
  • UE 415 can define a reordering timeout to flush out packets held in a reorder queue and move the reordering window, and if a missing sequence numbered packet creates reorder hole and UE 415 does not receive that packet before reorder timeout expires, this can create data loss at upper layers.
  • This scenario can be mitigated using aspects described herein to control power operation mode of one connection based on a power consumption mode of another connection.
  • FIG. 4 While aspects of FIG. 4 have been described with respect to LTE, similar aspects regarding aggregation and/or multiple connections may also be implemented with respect to UMTS or other similar system or network wireless communications radio technologies.
  • FIG. 5 is a block diagram 500 conceptually illustrating an example of an eNodeB 505, UE 515, and components configured in accordance with aspects described herein.
  • FIGs. 6 and 8 -10 which are described in conjunction with FIG. 5 herein, illustrate example methods 600, 800, 900, and 1000 in accordance with aspects described herein. Although the operations described below in FIGs. 6 and 8-10 are presented in a particular order and/or as being performed by an example component, it should be understood that the ordering of the actions and the components performing the actions may be varied, depending on the implementation.
  • a base station/eNodeB 505, a WLAN AP 506, and the UE 515 of block diagram 500 may be one of the base stations/eNodeBs, APs, and/or UEs as described in various Figures.
  • UE 515 can communicate with an eNB 505 to access a wireless network, examples of which are described in FIGs. 1-4 .
  • UE 515 may include a UE 115, UE 250, UE 315, UE 415, etc.
  • eNB 505 may include an access point 105, eNodeB 210, eNodeB 305-a, eNodeB 405, etc.
  • WLAN AP 506 may include an access point 105, AP 305-b, WLAN AP 406, etc.
  • eNB 505 and UE 515 may have established one or more downlink channels over which to communicate via downlink signals, which can be transmitted by eNB 505 (e.g., via transceiver 559) and received by UE 515 (e.g., via transceiver 509) for communicating control and/or data messages (e.g., in signaling) from the eNB 505 to the UE 515 over configured communication resources.
  • eNB 505 and UE 515 may have established one or more uplink channels over which to communicate via uplink signals, which can be transmitted by UE 515 (e.g., via transceiver 509) and received by eNB 505 (e.g., via transceiver 559) for communicating control and/or data messages (e.g., in signaling) from the UE 515 to the eNB 505 over configured communication resources.
  • uplink signals which can be transmitted by UE 515 (e.g., via transceiver 509) and received by eNB 505 (e.g., via transceiver 559) for communicating control and/or data messages (e.g., in signaling) from the UE 515 to the eNB 505 over configured communication resources.
  • eNodeB 505 and the UE 515 may communicate downlink and/or uplink communications over first communication link 525 using a first radio access technology (RAT) (e.g., WWAN RAT, such as LTE).
  • RAT radio access technology
  • the WLAN AP 506 and the UE 515 may also communicate over second communication link 526 using a second radio access technology (RAT) (e.g., WLAN RAT).
  • RAT radio access technology
  • WLAN AP 506 can also include a transceiver for communicating signals with the UE 515 using the second RAT.
  • Each of the communication links 525, 526 may be an example of the communication links 125 of FIG. 1 .
  • eNodeB 505 can communicate with WLAN AP 506 to configure and provide traffic aggregation, which also may be referred to as RAN aggregation, for the UE 515, such that traffic can be communicated between UE 515 and a network related to eNodeB 505 by using radio access via the eNodeB 505 and WLAN AP 506 (e.g., where the WLAN AP 506 can receive/provide traffic from/to the eNodeB 505 for communicating to/from the UE 515 over backhaul link 532 or other link between eNodeB 505 and WLAN AP 506).
  • traffic aggregation also may be referred to as RAN aggregation
  • connections can be aggregated for the UE 515 in addition or alternatively to one or more of the connection with eNodeB 505 and/or WLAN AP 506.
  • other connections can be aggregated for one or more additional or alternative RATs at the UE 515, and concepts described herein may be applied to handle power operation modes over one or more of the RATs to avoid packets loss in traffic aggregation.
  • UE 515 may include one or more processors 503 and/or a memory 504 that may be communicatively coupled, e.g., via one or more buses 507, and may operate in conjunction with or otherwise implement a communicating component 540 for communicating with eNodeB 505 as the first access point using a RAT of the eNodeB 505 (e.g., LTE, UMTS, etc.) to access a first wireless network (e.g., using first communication link 525, also referred to herein as a first connection), and communicating with WLAN AP 506 as the second access point using a RAT of the WLAN AP 506 (e.g., 802.11 Wi-Fi) to access a second wireless network (e.g., using second communication link 526, also referred to herein as a second connection).
  • a RAT of the eNodeB 505 e.g., LTE, UMTS, etc.
  • WLAN AP 506 e.g., 802.11 Wi-
  • eNodeB 505 can configure traffic aggregation for UE 515 such that UE 515 communicates with both eNodeB 505 and WLAN AP 506 over respective first communication link 525 and second communication link 526 to access a network related to the eNodeB 505, as described.
  • WLAN AP 506 can communicate UE 515 traffic with the eNodeB 505 over backhaul link 532 to provide the traffic aggregation for the UE 515 via second communication link 526.
  • the various operations related to communicating component 540 may be implemented or otherwise executed by one or more processors 503 and, in an aspect, can be executed by a single processor, while in other aspects, different ones of the operations may be executed by a combination of two or more different processors.
  • the one or more processors 503 may include any one or any combination of a modem processor, or a baseband processor, or a digital signal processor, or an application specific integrated circuit (ASIC), or a transmit processor, receive processor, or a transceiver processor associated with transceiver 509.
  • the memory 504 may be a non-transitory computer-readable medium that includes, but is not limited to, random access memory (RAM), read only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), a magnetic storage device (e.g., hard disk, floppy disk, magnetic strip), an optical disk (e.g., compact disk (CD), digital versatile disk (DVD)), a smart card, a flash memory device (e.g., card, stick, key drive), a register, a removable disk, and any other suitable medium for storing software and/or computer-readable code or instructions that may be accessed and read by a computer or one or more processors 503.
  • memory 504 or computer-readable storage medium may be resident in the one or more processors 503, external to the one or more processors 503, distributed across multiple entities including the one or more processors 503, etc.
  • the one or more processors 503 and/or memory 504 may execute actions or operations defined by communicating component 540 or its subcomponents.
  • the one or more processors 503 and/or memory 504 may execute actions or operations defined by an indicator receiving component 550 for receiving an indicator of a power consumption mode related to the first connection to eNodeB 505.
  • indicator receiving component 550 may include hardware (e.g., one or more processor modules of the one or more processors 503) and/or computer-readable code or instructions stored in memory 504 and executable by at least one of the one or more processors 503 to perform the specially configured indicator receiving operations described herein.
  • the one or more processors 503 and/or memory 504 may execute actions or operations defined by a power operation mode managing component 552 for managing the power operation mode over the second connection to WLAN AP 506.
  • power operation mode managing component 552 may include hardware (e.g., one or more processor modules of the one or more processors 503) and/or computer-readable code or instructions stored in memory 504 and executable by at least one of the one or more processors 503 to perform the specially configured power operation mode managing operations described herein.
  • the power consumption mode may relate to a mode where the UE 515 consumes power for transmitting and/or receiving wireless communications over a related connection.
  • the one or more processors 503 and/or memory 504 may optionally execute actions or operations defined by a packet reordering component 554 for reordering packets received over the first and second connections, where the packet reordering component 554 may include a packet reorder timer 556 after which packets within reorder window which are not received can be dropped.
  • packet reordering component 554 may include hardware (e.g., one or more processor modules of the one or more processors 503) and/or computer-readable code or instructions stored in memory 504 and executable by at least one of the one or more processors 503 to perform the specially configured packet reordering operations described herein.
  • the packet reorder timer 556 can be initialized based on a configured value (e.g., configured from memory 504 of UE 515, a network configuration received from one or more eNodeBs, such as eNodeB 505, or other network entities, etc.).
  • the packet reorder timer 556 can be tolled when it is detected that packets are received out-of-order, and based on expiration of the packet reorder timer 556, packet reordering component 554 may indicate that packet reordering is unsuccessful (and/or may drop out-of-order packets).
  • the one or more processors 503 and/or memory 504 may optionally execute actions or operations defined by a DRX inactivity timer 558 after which the first connection with eNodeB 505 may enter a power operation mode, and/or an on-duration timer 560 after expiration of which, the UE 515 can exit the power operation mode to allow the eNodeB 505 to initiate a downlink transmission to the UE 515 over the first connection.
  • a DRX inactivity timer 558 after which the first connection with eNodeB 505 may enter a power operation mode
  • an on-duration timer 560 after expiration of which, the UE 515 can exit the power operation mode to allow the eNodeB 505 to initiate a downlink transmission to the UE 515 over the first connection.
  • DRX inactivity timer 558 and/or an on-duration timer 560 may be implemented by, or otherwise managed by, hardware (e.g., one or more processor modules of the one or more processors 503) and/or computer-readable code or instructions stored in memory 504 and executable by at least one of the one or more processors 503, to be initialized, tolled, etc., as described further herein.
  • eNB 505 may include one or more processors 553 and/or a memory 555 that may be communicatively coupled, e.g., via one or more buses 557, and may operate in conjunction with or otherwise implement a scheduling component 520 for communicating with a UE 515 over first communication link 525, and for communicating with the UE 515 using RAN aggregation via WLAN AP 506 over second communication link 526.
  • processors 553 and/or a memory 555 may be communicatively coupled, e.g., via one or more buses 557, and may operate in conjunction with or otherwise implement a scheduling component 520 for communicating with a UE 515 over first communication link 525, and for communicating with the UE 515 using RAN aggregation via WLAN AP 506 over second communication link 526.
  • scheduling component 520 can communicate with WLAN AP 506 over backhaul link 532, for example, to provide data to WLAN AP 506 (e.g., packets or other data units at the application, TCP, UDP, IP, PDCP, RLC or MAC layer, as described above) in traffic aggregation for communicating to the UE 515, receive data from the WLAN AP 506 communicated thereto by the UE 515, etc.
  • the various functions related to scheduling component 520 may be implemented or otherwise executed by one or more processors 553 and, in an aspect, can be executed by a single processor, while in other aspects, different ones of the functions may be executed by a combination of two or more different processors, as described above. It is to be appreciated, in one example, that the one or more processors 553 and/or memory 555 may be configured as described in examples above with respect to the one or more processors 503 and/or memory 504 of UE 515.
  • the one or more processors 553 and/or memory 555 may execute actions or operations defined by scheduling component 520 or its subcomponents. For instance, the one or more processors 553 and/or memory 555 may execute actions or operations defined by a power operation mode determining component 522 for determining whether a connection between the WLAN AP 506 and the UE 515 (e.g., a connection over communication link 526) is in a power operation mode.
  • a power operation mode determining component 522 for determining whether a connection between the WLAN AP 506 and the UE 515 (e.g., a connection over communication link 526) is in a power operation mode.
  • power operation mode determining component 522 may include hardware (e.g., one or more processor modules of the one or more processors 553) and/or computer-readable code or instructions stored in memory 555 and executable by at least one of the one or more processors 553 to perform the specially configured power operation mode determining operations described herein.
  • the one or more processors 553 and/or memory 555 may execute actions or operations defined by a data scheduling component 524 for scheduling data over the connection between the WLAN AP 506 and the UE 515 and/or the eNodeB 505 and UE 515 based at least in part on whether the connection between the WLAN AP 506 and the UE 515 is in the power operation mode.
  • data scheduling component 524 may include hardware (e.g., one or more processor modules of the one or more processors 553) and/or computer-readable code or instructions stored in memory 555 and executable by at least one of the one or more processors 553 to perform the specially configured data scheduling operations described herein.
  • the one or more processors 553 and/or memory 555 may optionally execute actions or operations defined by a buffer size determining component 527 for determining a buffer size related to a buffer for communicating with the UE 515.
  • buffer size determining component 527 may include hardware (e.g., one or more processor modules of the one or more processors 553) and/or computer-readable code or instructions stored in memory 555 and executable by at least one of the one or more processors 553 to perform the specially configured buffer size determining operations described herein.
  • the one or more processors 553 and/or memory 555 may optionally execute actions or operations defined by an indicator transmitting component 528 for transmitting an indicator to exit the power operation mode to the UE 515.
  • indicator transmitting component 528 may include hardware (e.g., one or more processor modules of the one or more processors 553) and/or computer-readable code or instructions stored in memory 555 and executable by at least one of the one or more processors 553 to perform the specially configured indicator transmitting operations described herein.
  • the one or more processors 553 and/or memory 555 may optionally execute actions or operations defined by mode information receiving component 530 for receiving information of the power operation mode from the WLAN AP 506.
  • mode information receiving component 530 may include hardware (e.g., one or more processor modules of the one or more processors 553) and/or computer-readable code or instructions stored in memory 555 and executable by at least one of the one or more processors 553 to perform the specially configured mode information receiving operations described herein.
  • transceivers 509, 559 may be configured to transmit and receive wireless signals through one or more antennas, an RF front end, one or more transmitters, and one or more receivers.
  • transceivers 509, 559 may be tuned to operate at specified frequencies such that UE 515 and/or eNB 505 can communicate at a certain frequency.
  • the one or more processors 503 may configure transceiver 509 and/or one or more processors 553 may configure transceiver 559 to operate at a specified frequency and power level based on a configuration, a communication protocol, etc to communicate uplink signals and/or downlink signals, respectively, over related uplink or downlink communication channels.
  • transceivers 509, 559 can operate in multiple bands (e.g., using a multiband-multimode modem, not shown) such to process digital data sent and received using transceivers 509, 559.
  • transceivers 509, 559 can be multiband and be configured to support multiple frequency bands for a specific communications protocol.
  • transceivers 509, 559 can be configured to support multiple operating networks and communications protocols.
  • transceivers 509, 559 may enable transmission and/or reception of signals based on a specified modem configuration.
  • FIG. 6 illustrates a method 600 for determining (e.g., by a UE) a power operation mode for one or more traffic aggregated connections.
  • providing traffic aggregation can improve connectivity of the UE 515 with the network related to eNodeB 505 because eNodeB 505 can manage connection to eNodeB 505 and WLAN AP 506.
  • method 600 includes, at Block 610, establishing a first connection with a first serving node.
  • communicating component 540 e.g., in conjunction with one or more processors 503, memory 504, and/or transceiver 509, can establish the first connection (e.g., communication link 525) with the first serving node (e.g., eNodeB 505).
  • communicating component 540 can establish the first connection using a first RAT (e.g., LTE or other UMTS or cellular technology, etc.).
  • a first RAT e.g., LTE or other UMTS or cellular technology, etc.
  • communicating component 540 can perform a random access procedure with the eNodeB 505 or can otherwise request establishment of the connection therewith.
  • Method 600 also includes, at Block 612, establishing a second connection with a second serving node, where the second connection is configured for traffic aggregation with the first connection.
  • communicating component 540 e.g., in conjunction with one or more processors 503, memory 504, and/or transceiver 509, can establish the second connection (e.g., communication link 526) with the second serving node (e.g., WLAN AP 506, another eNodeB or cell, etc.), where the second connection is configured for traffic aggregation with the first connection.
  • communicating component 540 can establish the second connection using the first RAT or using a second RAT (e.g., Wi-Fi).
  • a second RAT e.g., Wi-Fi
  • Communicating component 540 can establish the second connection, for example, based on requesting connection with the WLAN AP 506 and performing any billing/authentication procedures therewith, etc.
  • eNodeB 505 can facilitate the connection between the UE 515 and WLAN AP 506 to provide traffic aggregation via the WLAN AP 506, as described.
  • eNodeB 505 may instruct the UE 515 to establish the second connection with WLAN AP 506, may provide instructions for establishing the second connection, etc.
  • UE 515 can communicate with WLAN AP 506 over the second connection, and the WLAN AP 506 may communicate UE 515 data to eNodeB 505 as described, where the first and second connections are configured to provide traffic aggregation.
  • communicating component 540 can receive data from the eNodeB 505 over communication link 525 and from WLAN AP 506 over communication link 526 in traffic aggregation, and packet reordering component 554 can reorder the packets, which may be received out-of-order due to concurrently receiving packets over the multiple links.
  • the data can be split over the links at the PDCP layer, and thus packet reordering component 554 can reorder the packets based at least in part on a PDCP sequence number associated therewith.
  • Method 600 may also include, at Block 614, receiving an indication of a power consumption mode for the first connection.
  • indicator receiving component 550 e.g., in conjunction with one or more processors 503, memory 504, and/or transceiver 509, can receive the indication of the power consumption mode for the first connection.
  • the indication of the power consumption mode can relate to substantially any indication from which a consumption of power to receive data can be inferred at the UE 515.
  • the indication can indicate, for example, that data is being received or is to be received over the first connection, and/or that the second connection may be used to aggregate transmission of the data to the UE 515.
  • method 600 also include, at Block 616, determining a power operation mode of the second connection based at least in part on the indication.
  • power operation mode managing component 552 e.g., in conjunction with one or more processors 503, memory 504, and/or transceiver 509, can determine the power operation mode of the second connection based at least in part on the indication.
  • power operation mode managing component 552 can determine to exit a power operation mode (e.g., enter an idle mode, a power save mode, or other mode related to saving power consumption at the UE 515) where the indication relates to receiving communications over the first connection and/or possibly the second connection.
  • the power operation mode over the second connection can be terminated such to receive communications over the second connection when desired for RAN aggregation.
  • receiving the indication of the power consumption mode at Block 614 may optionally include, at Block 618, determining a reorder status related to reordering packets received over the first and/or second connection.
  • indicator receiving component 550 e.g., in conjunction with one or more processors 503, memory 504, and/or transceiver 509, can determine the reorder status related to reordering the packets received over the first and/or second connection.
  • packet reordering component 554 can generate the reorder status, which can indicate whether a plurality of packets are successfully reordered (e.g., before expiration of the packet reorder timer 556), a value of the packet reorder timer 556, an indication of whether the packet reorder timer 556 has expired, etc.
  • power operation mode managing component 552 can determine to exit the power operation mode (e.g.
  • the indicator receiving component 550 at least one of determines that the reorder status is unsuccessful, determines that the packet reorder timer 556 has reached a threshold value (e.g., an expiration value, a difference from the expiration value, etc.) or has expired, or based on amount of traffic in memory waiting to be reordered, and/or the like, in an attempt to receive communications pending for the second connection at the WLAN AP 506 before reordering is deemed unsuccessful (e.g., before the packet reorder timer 556 expires).
  • a threshold value e.g., an expiration value, a difference from the expiration value, etc.
  • power operation mode managing component 552 can notify the packet reordering component 554 when an interface of communicating component 540 that communicates over communication link 526 enters the power operation mode for the second connection.
  • packet reordering component 554 operates at a PDCP or MAC layer to reorder packets received from eNodeB 505 and WLAN AP 506.
  • packet reorder timer 556 is tolling and packet reordering component 554 determines that the second connection is in the power operation mode (e.g., that the associated interface of communicating component 540 is in the power operation mode)
  • packet reordering component 554 can instruct the communicating component 540 to exit the power operation mode (e.g., transition to an active mode to receive communications) over the second connection, poll the WLAN AP 506 for buffered data (e.g., via the PS-Poll mechanism), etc.
  • exiting the power operation mode, polling for buffered data, etc. can allow the UE 515 to receive buffered PDCP packets from the WLAN AP 506 before expiry of the packet reorder timer 556 (and possible dropping of out-of-order packets), and hence can avoid data loss and in addition deliver the reordered stream earlier which minimizes memory consumption and improves the user experience.
  • the device may temporarily schedule data traffic on the WLAN uplink in order to exit the power save mode. This may be more efficient than using the PS-poll since the power save control indicating that power operation mode has been exited can be piggybacked onto user data.
  • FIG. 7 depicts an example system 700 for communicating packets between a UE 702, WLAN AP 706, and eNodeB 704.
  • the UE WLAN STA interface enters a power-save mode with the WLAN AP 706 at 710.
  • the WLAN AP 706 periodically transmits beacon TIM (e.g., at a beacon interval of 70ms and/or a DTIM interval of 280ms).
  • beacon TIM e.g., at a beacon interval of 70ms and/or a DTIM interval of 280ms.
  • WLAN AP transmits beacon TIM 712 indicating 0 (no traffic).
  • eNodeB 704 schedules various PDCP packets, including sequence numbers 7, 11, and 12 for transmitting by WLAN AP 706 and 12, 14, and 15 for transmitting by eNodeB 704.
  • packets 7, 11, and 12 are buffered at 716 until the power save mode is terminated.
  • eNodeB 704 transmits packets 13, 14, and 15 to UE 702 at 718.
  • UE 702 can transition to active mode (e.g., terminating the power save mode) at 722 with a time remaining before reorder timer expiry based on receiving out-of-order packets from the eNodeB 704 (e.g., and/or based on detecting that at least a threshold time remains at the reorder timer). Accordingly, at 724, the buffered packets 7, 11, and 12 are received and reorder holes are filled with no data loss.
  • receiving the indication of the power consumption mode at Block 614 may optionally include, at Block 620, determining whether packets received over the first and/or second connection are successfully reordered.
  • indicator receiving component 550 e.g., in conjunction with one or more processors 503, memory 504, and/or transceiver 509, can determine whether packets received over the first and/or second connection are successfully received (e.g., whether a gap in sequence number is filled).
  • indicator receiving component 550 can make this determination based at least in part on packet reordering component 554 attempting to reorder packets received over communication links 525 and 526, and notifying the indicator receiving component 550 when packets are successfully reordered and/or cannot be successfully reordered (e.g., based on expiration of the packet reorder timer 556).
  • indicator receiving component 550 can instruct power operation mode managing component 552 that the communicating component 540 may enter the power operation mode over the second connection (e.g., that an interface related to the second connection may enter a power operation mode), which may be subject to other considerations at the power operation mode managing component 552.
  • LTE can utilize DRX to enable a power operation mode (e.g., power saving mode) at the UE 515, where the eNodeB 505 and UE 515 maintain the same state machine for DRX, which enables the eNodeB 505 to transmit to the UE 515 at times when it is receiving, and the UE 515 to sleep (e.g., suspend radio resources) at other times.
  • power operation mode managing component 552 can manage the power operation mode for the second connection based at least in part on the power operation mode (e.g., DRX) for the first connection.
  • DRX defines various timers and when one of them is tolling, the UE 515 cannot sleep (e.g., suspend radio resources for the first connection).
  • These timers include the DRX inactivity timer 558, which starts when the UE 515 is scheduled by the eNodeB 505 (e.g., by scheduling component 520) to receive downlink transmissions, and the on-duration timer 560, which runs periodically every DRX cycle.
  • receiving the indication of the power consumption mode at Block 614 may optionally include, at Block 622, determining whether a DRX inactivity timer of the first RAT related to entering another power operation mode for the first RAT is tolling.
  • indicator receiving component 550 e.g., in conjunction with one or more processors 503, memory 504, and/or transceiver 509, can determine whether the DRX inactivity timer 558 of the first RAT relating to entering another power operation mode for the first RAT (e.g., over communication link 525) is tolling.
  • tolling can refer to a timer having been initialized to a value and being incremented/decremented based on a clock of a corresponding processor until the timer reaches zero as a lower bound (e.g., where the timer counts down and thus tolling decreases the timer value over time) or the timer value as an upper bound (e.g., where the timer counts up and thus tolling increases the timer value over time).
  • Communicating component 540 can start/re-start the DRX inactivity timer 558 when a downlink transmission is received from the eNodeB 505.
  • indicator receiving component 550 determines that the DRX inactivity timer is tolling, it can instruct power operation mode managing component 552 to exit a power operation mode over the second connection.
  • Power operation mode managing component 552 can cause communicating component 540 to exit the power operation mode (e.g., over an interface related to the second connection), perform a PS-Poll to the WLAN AP 506 over the second connection, etc. This can avoid unsuccessful reordering of packets as the receiving of downlink transmissions from eNodeB 505, which causes tolling of the DRX inactivity timer 558, results in exiting the power operation mode over the second connection.
  • indicator receiving component 550 may first determine that receiving a downlink transmission (as opposed to transmitting an uplink transmission) caused the DRX inactivity timer 558 in order to begin tolling before instructing power operation mode managing component 552 to exit the power operation mode.
  • receiving the indication of the power consumption mode at Block 614 may optionally include, at Block 624, determining whether an on-duration timer of the first RAT related to exiting another power operation mode for the first RAT is expired.
  • indicator receiving component 550 e.g., in conjunction with one or more processors 503, memory 504, and/or transceiver 509, can determine whether the on-duration timer 560 of the first RAT relating to exiting another power operation mode for the first RAT (e.g., over communication link 525) is expired.
  • the on-duration timer 560 can cause the UE 515 to exit a power operation mode over the first connection to allow the eNodeB 505 to initiate downlink transmissions to the UE 515 periodically every DRX cycle.
  • power operation mode managing component 552 exits the power operation mode for the first connection (e.g., by instructing the communicating component 540 to exit the power operation mode on a related interface).
  • indicator receiving component 550 determines expiration of the on-duration timer 560, it can instruct power operation mode managing component 552 to exit the power operation mode for the second connection (e.g., over an interface related to the second connection), perform a PS-Poll to the WLAN AP 506 over the second connection, etc. As described, this can avoid unsuccessful reordering of packets since the second connection is activated when the first connection is activated based on expiration of the on-duration timer 560.
  • the eNodeB 505 can manage similar DRX inactivity and on-duration timers (e.g., in providing a similar DRX state machine as the UE 515) for determining when to transmit communications to WLAN AP 506 for transmitting over the second connection.
  • receiving the indication of the power consumption mode at Block 614 may optionally include, at Block 626, determining whether one or more packets are received over the first connection.
  • indicator receiving component 550 e.g., in conjunction with one or more processors 503, memory 504, and/or transceiver 509, can determine whether one or more packets are received over the first connection, which can include determining such information from communicating component 540.
  • indicator receiving component 550 determines that one or more packets are received by the communicating component 540 over the first connection, for example, indicator receiving component 550 can instruct power operation mode managing component 552 to exit the power operation mode for the second connection (e.g., over an interface related to the second connection), perform a PS-Poll to the WLAN AP 506 over the second connection, etc. This can avoid unsuccessful reordering of packets since the second connection is activated when packets are received over the first connection, and thus packets can be received over the second connection as well likely before expiration of the packet reorder timer 556.
  • receiving the indication of the power consumption mode at Block 614 may optionally include, at Block 628, receiving the indication in a control packet over the first and/or second connection.
  • indicator receiving component 550 e.g., in conjunction with one or more processors 503, memory 504, and/or transceiver 509, can receive the indication in the control packet (e.g., PDCP control PDU) over the first and/or second connection.
  • eNodeB 505 (and/or WLAN AP 506) may transmit the indication in the control packet to the UE 515.
  • eNodeB 505 may transmit the control packet based on obtaining a data burst for transmitting the UE 515 (and/or along with transmitting the burst).
  • the beginning of the burst may include the control packet.
  • indicator receiving component 550 can instruct power operation mode managing component 552 to exit the power operation mode for the second connection (e.g., over an interface related to the second connection), perform a PS-Poll to the WLAN AP 506 over the second connection, etc.
  • control packet may specify a time to exit the power operation mode, a periodic pattern for entering/leaving the power operation mode, etc., and indicator receiving component 550 can accordingly instruct the power operation mode managing component 552 based on the indication.
  • this can avoid unsuccessful reordering of packets since the eNodeB 505 (and/or WLAN AP 506) can cause the UE 515 to exit the power operation mode over the second connection when it has data to be transmitted over the second connection.
  • power operation mode managing component 552 may manage the second connection to stay out of the power operation mode at least until another control packet is received indicating that the UE 515 is allowed to enter the power operation mode over the second connection.
  • FIG. 8 illustrates an example method 800 for determining (e.g., by an eNB) when to schedule data over a connection in traffic aggregation where the connection may be in a power operation mode.
  • Method 800 includes, at Block 810, serving a UE over a first connection using a first RAT.
  • scheduling component 520 e.g., in conjunction with one or more processors 553, memory 555, and/or transceiver 559, can serve the UE 515 over the first connection (e.g., communication link 525) using a first RAT (e.g., LTE or other UMTS or cellular technology).
  • a first RAT e.g., LTE or other UMTS or cellular technology
  • the UE 515 may perform a random access procedure or otherwise request resources for communicating with the eNodeB 505, and eNodeB 505 may accordingly grant resources to the UE 515 over communication link 525.
  • scheduling component 520 may aggregate traffic to the UE 515 over another communication link 526 established between the UE 515 and a WLAN AP 506 based at least in part on communicating data to/from the WLAN AP 506 over backhaul link 534.
  • Method 800 also includes, at Block 812, determining whether the UE is configured in a power operation mode associated with a second connection with an access point using a second RAT.
  • power operation mode determining component 522 e.g., in conjunction with one or more processors 553, memory 555, and/or transceiver 559, can determine whether the UE (e.g., UE 515) is configured in the power operation mode associated with the second connection (e.g., communication link 526) with the access point (e.g., WLAN AP 506) using a second RAT (e.g., Wi-Fi).
  • a second RAT e.g., Wi-Fi
  • power operation mode determining component 522 may receive an indication of whether the UE 515 is in the power operation mode from WLAN AP 506 and/or UE 515, which may be based on a request to the WLAN AP 506 and/or UE 515 or otherwise (e.g., a notification received from the WLAN AP 506 or UE 515 upon the UE 515 entering the power operation mode over the second connection), etc.
  • determining whether the UE 515 is configured in the power operation mode over the second connection at Block 812 nay include, at Block 814, determining a size of a data buffer available for transmitting to the UE.
  • buffer size determining component 527 e.g., in conjunction with one or more processors 553, memory 555, and/or transceiver 559, can determine the size of the data buffer available for transmitting the UE 515.
  • buffer size determining component 527 can determine an available capacity size of the buffer, from which a power operation mode can be inferred (e.g., if the available capacity size of the buffer is below a threshold or is trending lower over a time period, etc.).
  • the buffer may correspond to the second connection or to communications for the UE 515 generally.
  • Method 800 may also include, at Block 816, scheduling data for the second connection during a first time interval based at least in part on the determination that the UE is configured in the power operation mode associated with the second connection.
  • data scheduling component 524 e.g., in conjunction with one or more processors 553, memory 555, and/or transceiver 559, can schedule the data for the second connection (e.g., communication link 526) during the first time interval based at least in part on the determination that the UE (e.g., UE 515) is configured in the power operation mode associated with the second connection.
  • the data scheduling component 524 can assume the UE 515 entered the power operation mode for the second connection (e.g., based on the determination by power operation mode determining component 522 or otherwise) and can accordingly schedule data for sending over the communication link 526 during the time interval (so no data is sent over communication link 525).
  • the data can then be buffered by WLAN AP 506 until the UE 515 exits the power operation mode.
  • communicating component 540 may periodically receive signals in the power operation mode, and may check for the TIM (e.g., as described in FIG. 7 above).
  • the TIM bitmap can indicate data available for transmission by the WLAN AP, and power operation mode managing component 552 can accordingly exit the power operation mode with the second connection to receive the buffered data.
  • Method 800 can also include, at Block 818, scheduling data on the first connection and the second connection during a second time interval.
  • data scheduling component 524 e.g., in conjunction with one or more processors 553, memory 555, and/or transceiver 559, can schedule the data on the first connection and the second connection during the second time interval.
  • Scheduling data on the first connection and the second connection during a second time interval at Block 818 may optionally, include, at Block 820, determining that the UE exits the power operation mode over the second connection.
  • power operation mode determining component 522 may determine that the UE 515 has exited the power operation mode over the second connection (e.g., based on receiving an indication from the WLAN AP 506, UE 515, etc., determining that an available buffer capacity for the UE 515 has increased or is increasing, etc., as described above). Based on this determination, for example, data scheduling component 524 can determine the second time interval has begun where the second connection is no longer in power operation mode at the UE 515, and data can thus be sent over the second connection. Thus, data scheduling component 524 additionally schedules data over the first connection to implement traffic aggregation.
  • method 800 may optionally include, at Block 822, scheduling at least one packet on the second connection during an inactivity timer interval related to the second RAT to keep the second connection out of the power operation mode for a duration of the second time interval.
  • data scheduling component 524 e.g., in conjunction with one or more processors 553, memory 555, and/or transceiver 559, can schedule the at least one packet on the second connection (e.g., communication link 526 via backhaul link 534 communications to the WLAN AP 506) during an inactivity timer interval related to the second RAT to keep the second connection out of the power operation mode.
  • the inactivity timer value after which the UE 515 can enter the power operation mode for the second connection based on the second RAT, can be known by the eNodeB 505, and thus the at least one packet is scheduled inside of this inactivity time interval to avoid entering the power operation mode at the UE 515.
  • eNodeB 505 can configure the inactivity timer value for the UE 515 (e.g., via RRC signaling).
  • the inactivity timer value may be specifically used for determined inactivity over one or more connections in traffic aggregation.
  • the data scheduling component 524 may cease scheduling the at least one packet on the second connection after a period of time and/or based on an event (e.g., an available capacity of a buffer related to transmitting to the UE 515 achieving a threshold), to allow the UE 515 to once again enter the power operation mode (e.g., after expiration of the inactivity timer).
  • FIG. 9 illustrates an example method 900 for transmitting (e.g., by an eNB or eNodeB) a control packet to a UE to cause the UE to exit a power operation mode over a connection in traffic aggregation.
  • Method 900 includes, at Block 910, serving a UE over a first connection using a first RAT.
  • scheduling component 520 e.g., in conjunction with one or more processors 553, memory 555, and/or transceiver 559, can serve the UE 515 over the first connection (e.g., communication link 525) using a first RAT (e.g., LTE or other UMTS or cellular technology).
  • the UE 515 may perform a random access procedure or otherwise request resources for communicating with the eNodeB 505, and eNodeB 505 may accordingly grant resources to the UE 515 over communication link 525.
  • Method 900 may also include, at Block 912, communicating with the UE over a second connection via an access point that uses a second RAT.
  • scheduling component 520 e.g., in conjunction with one or more processors 553, memory 555, and/or transceiver 559, can communicate with the UE (e.g., UE 515) over the second connection (e.g., communication link 526) via an access point (e.g., WLAN AP 506) that uses a second RAT.
  • scheduling component 520 may aggregate traffic to the UE 515 over another communication link 526 established between the UE 515 and a WLAN AP 506 based at least in part on communicating data to/from the WLAN AP 506 over backhaul link 534.
  • scheduling component 520 may determine to use a reduced number of radio links when the data rate is determined to be below a threshold. This avoids or mitigates the issue of synchronizing the power save state across the plurality of radio links.
  • the threshold may depend on the link capacity achievable on one or more of the links, the load on a radio providing the one or more links, or similar radio quality metrics.
  • Method 900 also includes, at Block 914, transmitting a control packet to the UE over the first or second connection indicating to exit a power operation mode over the second connection.
  • indicator transmitting component 528 e.g., in conjunction with one or more processors 553, memory 555, and/or transceiver 559, can transmit the control packet to the UE (e.g., UE 515) over the first or second connection indicating to exit the power operation mode over the second connection (e.g., communication link 526).
  • the control packet may include a target time at which the device must exit the power save or it may include a duration of time for which the device stays out of the power save mode.
  • indicator transmitting component 528 can transmit the control packet at the beginning of a data burst for the UE 515, and indicator receiving component 550 can receive the control packet for determining to exit a power operation mode for the second connection.
  • Method 900 also includes, at Block 916, scheduling data for transmission on the first and second connection based at least in part on transmitting the control packet.
  • data scheduling component 524 e.g., in conjunction with one or more processors 553, memory 555, and/or transceiver 559, can schedule data for transmission on the first and second connection based at least in part on transmitting the control packet.
  • the control packet can cause the power operation mode to terminate for the second connection, data can be received over the second connection, which can likely avoid reorder errors otherwise caused by the second connection being in a power operation mode.
  • Method 900 may optionally include, at Block 918, transmitting another control packet to the UE over the first or second connection indicating that the power operation mode is allowed over the second connection.
  • indicator transmitting component 528 e.g., in conjunction with one or more processors 553, memory 555, and/or transceiver 559, can transmit the another control packet to the UE (e.g., UE 515) over the first or second connection indicating that the power operation mode is allowed over the second connection (e.g., communication link 526).
  • indicator receiving component 550 may receive this control packet, and power operation mode managing component 552 may cause the communicating component 540 to enter the power operation mode for the second connection based at least in part on the control packet and/or other considerations (e.g., expiration of a related inactivity timer for the second connection).
  • power operation mode managing component 552 may cause the communicating component 540 to enter the power operation mode for the second connection based at least in part on the control packet and/or other considerations (e.g., expiration of a related inactivity timer for the second connection).
  • FIG 10 illustrates an example method 1000 for determining (e.g., by an eNB or eNodeB) whether a UE is in a power operation mode over a connection in traffic aggregation.
  • Method 1000 includes, at Block 1010, serving a UE over a first connection using a first RAT.
  • scheduling component 520 e.g., in conjunction with one or more processors 553, memory 555, and/or transceiver 559, can serve the UE 515 over the first connection (e.g., communication link 525) using a first RAT (e.g., LTE or other UMTS or cellular technology).
  • the UE 515 may perform a random access procedure or otherwise request resources for communicating with the eNodeB 505, and eNodeB 505 may accordingly grant resources to the UE 515 over communication link 525.
  • Method 1000 may also include, at Block 1012, communicating with the UE over a second connection via an access point that uses a second RAT.
  • scheduling component 520 e.g., in conjunction with one or more processors 553, memory 555, and/or transceiver 559, can communicate with the UE (e.g., UE 515) over the second connection (e.g., communication link 526) via an access point (e.g., WLAN AP 506) that uses a second RAT.
  • scheduling component 520 may aggregate traffic to the UE 515 over another communication link 526 established between the UE 515 and a WLAN AP 506 based at least in part on communicating data to/from the WLAN AP 506 over backhaul link 534.
  • Method 1000 may also include, at Block 1014, determining whether the second connection is in a power operation mode based at least in part on receiving information from an access point indicating whether the second connection is in the power operation mode.
  • mode information receiving component 530 e.g., in conjunction with one or more processors 553, memory 555, and/or transceiver 559, can determine whether the second connection (e.g., communication link 526) is in the power operation mode based at least in part on receiving information from the access point (e.g., WLAN AP 506) indicating whether the second connection is in the power operation mode.
  • mode information receiving component 530 may receive the information from WLAN AP 506 over the backhaul link 534.
  • determining whether the second connection is in the power mode at Block 1014 may optionally include, at Block 1016, determining a duration for exiting the power operation mode as a function of a beacon interval, a DTIM interval, and/or a backhaul latency across the access point.
  • Mode information receiving component 530 can determine the duration for exiting the power operation mode as a function of the beacon interval, the DTIM interval, and/or the backhaul latency across the access point, which can be received by WLAN AP 506.
  • method 1000 may also include, at Block 1018, scheduling data for transmission on the first and second connection based at least in part on whether the second connection is in the power operation mode.
  • data scheduling component 524 e.g., in conjunction with one or more processors 553, memory 555, and/or transceiver 559, can schedule data for transmission on the first and second connection based at least in part on whether the second connection is in the power operation mode.
  • data scheduling component 524 can schedule data over both the first and second connections to provide traffic aggregation.
  • a general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine.
  • a processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
  • a software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium.
  • the storage medium may be integral to the processor.
  • the processor and the storage medium may reside in an ASIC.
  • the ASIC may reside in a user terminal.
  • the processor and the storage medium may reside as discrete components in a user terminal.
  • the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium.
  • Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a storage media may be any available media that can be accessed by a general purpose or special purpose computer.
  • such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium.
  • Disk and disc includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Claims (15)

  1. Ein Verfahren für drahtlose Kommunikationen, wobei das Verfahren umfasst:
    Einrichten (610), durch eine Benutzerausrüstung, UE, einer ersten Verbindung mit einem ersten bedienenden Knoten unter Verwendung einer
    Drahtlos-Wide-Area-Netzwerk-WWAN-Radio-Access-Technology-RAT;
    Einrichten (612), durch die UE, einer zweiten Verbindung mit einem zweiten bedienenden Knoten unter Verwendung einer Drahtlos-Local-Area-Netzwerk-WLAN-RAT, wobei die erste Verbindung und die zweite Verbindung zur Verkehrsaggregation bei einem Netzwerk-Layer konfiguriert sind;
    Empfangen (614), durch die UE, einer Anzeige eines Leistungsverbrauchsmodus für die erste Verbindung, wobei sich der Leistungsverbrauchsmodus auf die WWAN RAT bezieht;
    Bestimmen, aus der Anzeige, des Leistungsverbrauchsmodus für die erste Verbindung; und
    Umschalten (616), durch die UE und zumindest teilweise basierend auf dem Bestimmen eines Leistungsbetriebsmodus der zweiten Verbindung, um den zweiten bedienenden Knoten dazu zu veranlassen, eine oder mehrere Dateneinheiten, die auf dem Netzwerk-Layer gepuffert sind, an die UE und über die zweite Verbindung zu übertragen, wobei das Umschalten des Leistungsbetriebsmodus ein Übertragen, an den zweiten bedienenden Knoten und über die zweite Verbindung, von zumindest einer Leistungssparabfrage der WLAN-RAT oder einer Uplink-Dateneinheit unter Verwendung der WLAN-RAT umfasst.
  2. Verfahren nach Anspruch 1, wobei das Empfangen (614) der Anzeige des Leistungsverbrauchsmodus für die erste Verbindung ein Bestimmen (618) eines Neubestellungszustands mit Bezug zu einem Neubestellen von Paketen umfasst, die über zumindest eine von der ersten Verbindung oder der zweiten Verbindung empfangen werden.
  3. Verfahren nach Anspruch 2, wobei der Neubestellungszustand auf zumindest einem von einer zweiten Anzeige, dass das Neubestellen im Gange ist oder nicht im Gange ist, einer verbleibenden Zeit, die für einen Paketneubestellungstimer verbleibt, oder einer Zeit seit der Paketneubestellungstimer gestartet hat, basiert.
  4. Verfahren nach Anspruch 2, wobei das Umschalten des Leistungsbetriebsmodus der zweiten Verbindung ein Verlassen des Leistungsbetriebsmodus zumindest teilweise auf einem Bestimmen des Neubestellungsstatus basiert.
  5. Verfahren nach Anspruch 4, wobei das Verlassen des Leistungsbetriebsmodus ein Übertragen, über die zweite Verbindung, von zumindest einem von der Leistungssparabfrage oder von Uplink-Benutzerdaten mit einer huckepackunterstützten Leistungssparsteuerung umfasst, die das Verlassen des Leistungsbetriebsmodus anzeigen.
  6. Verfahren nach Anspruch 1, wobei das Empfangen der Anzeige des Leistungsverbrauchsmodus von der ersten Verbindung ein Bestimmen (620) umfasst, ob Pakete, die über zumindest eine von der ersten Verbindung oder der zweiten Verbindung empfangen wurden, erfolgreich neu bestellt werden, und wobei das Umschalten des Leistungsbetriebsmodus der zweiten Verbindung zumindest teilweise auf dem Bestimmen basiert, dass die Pakete erfolgreich neu bestellt wurden.
  7. Verfahren nach Anspruch 1, wobei das Empfangen der Anzeige des Leistungsverbrauchsmodus von der ersten Verbindung ein Bestimmen umfasst, ob ein diskontinuierlicher Empfangs-DRX-Inaktivitätstimer der ersten Verbindung mit Bezug auf ein Eintreten in einen anderen Leistungsbetriebsmodus für die erste Verbindung nach einem Ablauf des DRX-Inaktivitätstimers läutet.
  8. Verfahren nach Anspruch 7, wobei das Bestimmen, dass der DRX-Inaktivitätstimer läutet, ein Bestimmen umfasst, dass der DRX-Inaktivitätstimer basierend auf einem Empfangen einer Downlinkübertragung über die erste Verbindung läutet.
  9. Verfahren nach Anspruch 1, wobei das Empfangen der Anzeige des Leistungsverbrauchsmodus von der ersten Verbindung ein Bestimmen umfasst, ob ein Einschaltdauertimer der ersten Verbindung mit Bezug auf ein Verlassen eines anderen Leistungsbetriebsmodus für die erste Verbindung nach einem Ablauf des Einschaltdauertimers abgelaufen ist.
  10. Verfahren nach Anspruch 1, wobei das Empfangen der Anzeige zumindest teilweise auf einem Empfangen oder Übertragen eines Pakets über die erste Verbindung basiert.
  11. Verfahren nach Anspruch 1, wobei das Empfangen der Anzeige ein Empfangen eines Steuerpakets über die erste Verbindung oder die zweite Verbindung umfasst, das anzeigt, dass der Leistungsbetriebsmodus über die zweite Verbindung zu verlassen ist.
  12. Verfahren nach Anspruch 11, wobei das Umschalten des Leistungsbetriebsmodus ein Bestimmen umfasst, basierend auf dem Steuerpaket, außerhalb des Leistungsbetriebsmodus zu bleiben, bis ein anderes Steuerpaket über die erste Verbindung oder die zweite Verbindung empfangen wird, das anzeigt, dass der Leistungsbetriebsmodus für die zweite Verbindung zugelassen ist.
  13. Verfahren nach Anspruch 11, wobei das Steuerpaket eine Zeit anzeigt, zu der der Leistungsbetriebsmodus zu betreten und/oder verlassen ist.
  14. Verfahren nach Anspruch 11, wobei das Steuerpaket ein periodisches Muster zum Betreten und/oder Verlassen des Leistungsbetriebsmodus definiert.
  15. Eine Vorrichtung (500) für drahtlose Kommunikationen, wobei die Vorrichtung umfasst:
    einen Sendeempfänger (509);
    einen Speicher (504), der konfiguriert ist, um Anweisungen zu speichern; und
    zumindest einen Prozessor (503), der kommunikativ mit dem Sendeempfänger (509) und dem Speicher (504) gekoppelt ist, wobei der zumindest eine Prozessor (503) konfiguriert ist, um das Verfahren nach irgendeinem der Ansprüche 1 bis 14 durchzuführen.
EP16711491.7A 2015-03-19 2016-03-11 Techniken zur verwaltung der leistungsbetriebsarten eines benutzergeräts bei der kommunikation mit mehreren funkzugangstechnologien Active EP3272154B1 (de)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US201562135583P 2015-03-19 2015-03-19
US15/066,214 US10264481B2 (en) 2015-03-19 2016-03-10 Techniques for managing power operation modes of a user equipment (UE) communicating with a plurality of radio access technologies (RATs)
PCT/US2016/022202 WO2016149143A1 (en) 2015-03-19 2016-03-11 Techniques for managing power operation modes of a user equipment (ue) communicating with a plurality of radio access technologies (rats)

Publications (2)

Publication Number Publication Date
EP3272154A1 EP3272154A1 (de) 2018-01-24
EP3272154B1 true EP3272154B1 (de) 2020-02-12

Family

ID=55588637

Family Applications (1)

Application Number Title Priority Date Filing Date
EP16711491.7A Active EP3272154B1 (de) 2015-03-19 2016-03-11 Techniken zur verwaltung der leistungsbetriebsarten eines benutzergeräts bei der kommunikation mit mehreren funkzugangstechnologien

Country Status (7)

Country Link
US (1) US10264481B2 (de)
EP (1) EP3272154B1 (de)
JP (1) JP6605616B2 (de)
KR (1) KR102067884B1 (de)
CN (1) CN107409360A (de)
BR (1) BR112017020021A2 (de)
WO (1) WO2016149143A1 (de)

Families Citing this family (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9730271B2 (en) * 2013-06-03 2017-08-08 Avago Technologies General Ip (Singapore) Pte. Ltd. Systems and methods for splitting and recombining communications in multi-network environments
KR101870022B1 (ko) * 2015-04-02 2018-06-22 주식회사 케이티 무선 베어러 재구성 방법 및 그 장치
EP3180942B1 (de) * 2015-04-10 2018-01-17 Telefonaktiebolaget LM Ericsson (publ) Aktualisierung einer wlan-aggregationskonfiguration
CN106341907B (zh) * 2015-07-09 2021-03-16 中兴通讯股份有限公司 一种数据传输方法、装置和系统
US10117280B2 (en) * 2015-10-23 2018-10-30 Qualcomm Incorporated Techniques for receiving packets over aggregated connections in wireless communications
CN107889154A (zh) * 2016-09-30 2018-04-06 华为技术有限公司 一种通信方法及装置
EP3334237A1 (de) * 2016-12-06 2018-06-13 Gemalto M2M GmbH Verfahren zur zuverlässigen datenübertragung
US10142237B2 (en) 2016-12-21 2018-11-27 Intel IP Corporation Communication control method and system
US10812601B2 (en) * 2017-03-07 2020-10-20 Flash Networks Ltd. Method and system for signaling and radio connection optimization over a cellular network
US10237784B2 (en) 2017-03-24 2019-03-19 Motorola Mobility Llc Split bearer packet data converge protocol protocol data unit routing
US10993181B2 (en) * 2017-08-11 2021-04-27 Qualcomm Incorporated Techniques and apparatuses for power management via cross-rat signaling in a non-standalone configuration
US11388628B2 (en) 2018-07-26 2022-07-12 Apple Inc. In order packet delivery for compressed radio bearers
US10939371B2 (en) * 2018-09-28 2021-03-02 Nxp Usa, Inc. Power save optimization for wireless connectivity
CN111163019B (zh) * 2018-11-07 2022-10-28 中兴通讯股份有限公司 处理数据包的方法、装置和存储介质
CN111181697A (zh) * 2018-11-13 2020-05-19 三星电子株式会社 用于tcp ack包的传输的方法和系统
US10873986B1 (en) * 2019-06-04 2020-12-22 Sprint Spectrum L.P. Use of buffer occupancy as a basis to control configuration of dual-connectivity service
CN112118192B (zh) * 2019-06-20 2022-11-18 华为技术有限公司 一种数据量整形方法、网络设备以及计算机程序产品
WO2021092727A1 (zh) * 2019-11-11 2021-05-20 北京小米移动软件有限公司 设备省电方法及设备省电装置
US11617103B2 (en) * 2020-02-10 2023-03-28 Qualcomm Incorporated Adaptive accumulation triggers for enhanced throughput and performance
CN113316232B (zh) * 2021-05-18 2022-04-26 西安电子科技大学 基于省电多询的多链路省电方法
US11871284B1 (en) * 2021-06-23 2024-01-09 Amazon Technologies, Inc. Integrating multiple access technologies in a radio-based network
WO2024055147A1 (en) * 2022-09-13 2024-03-21 Qualcomm Incorporated Scheduling techniques for radio access technology coexistence

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015032056A1 (zh) * 2013-09-05 2015-03-12 华为技术有限公司 传输数据的方法及基站、用户设备

Family Cites Families (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7299009B2 (en) 2004-02-25 2007-11-20 Nokia Corporation Blue-tooth assisted wireless local area network (WLAN) home network systems
ATE332056T1 (de) 2004-03-17 2006-07-15 Cit Alcatel Verfahren zum steuern des schlafmodus eines endgerätes, dazugehöriges mobiles endgerät und funkzugriffsknoten
US20050249227A1 (en) * 2004-05-07 2005-11-10 Wang Huai Y Method for indicating buffer status in a WLAN access point
US8462693B2 (en) * 2007-02-20 2013-06-11 Research In Motion Limited System and method for enabling wireless data transfer
US9294926B2 (en) * 2011-10-07 2016-03-22 Interdigital Patent Holdings, Inc. Method and apparatus for integrating different radio access technologies using carrier aggregation
US9078201B2 (en) 2011-10-14 2015-07-07 Qualcomm Incorporated Idle mode operation in heterogeneous networks
JP5962096B2 (ja) 2012-03-16 2016-08-03 富士通株式会社 無線通信システム、端末、及び通信方法
US9345024B2 (en) 2012-04-13 2016-05-17 Intel Corporation Exchanging configuration data
US9144003B2 (en) * 2012-05-02 2015-09-22 Qualcomm Incorporated Apparatus and method for a connected mode with reduced signaling
WO2014056154A1 (en) * 2012-10-10 2014-04-17 Telefonaktiebolaget L M Ericsson (Publ) Discontinuous reception method and user equipment using the same
EP2995019B1 (de) 2013-05-09 2019-01-30 Intel IP Corporation Small-data-kommunikationen
JP6091995B2 (ja) 2013-05-17 2017-03-08 株式会社Ｎｔｔドコモ 無線基地局、ユーザ端末、間欠受信方法
KR20150012705A (ko) 2013-07-26 2015-02-04 주식회사 팬택 단말에서 전류 소모 감소를 위한 방법 및 장치
JP6191079B2 (ja) 2013-09-02 2017-09-06 シャープ株式会社 移動局装置、基地局装置、および通信システム
CN106063324B (zh) * 2014-01-28 2019-10-11 寰发股份有限公司 重排序pdcp封包的方法以及用户设备
US9408142B2 (en) * 2014-03-27 2016-08-02 Intel Corporation Power saving and device traffic offload

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015032056A1 (zh) * 2013-09-05 2015-03-12 华为技术有限公司 传输数据的方法及基站、用户设备
US20160192293A1 (en) * 2013-09-05 2016-06-30 Huawei Technologies Co., Ltd. Data transmission method, base station, and user equipment

Also Published As

Publication number Publication date
BR112017020021A2 (pt) 2018-06-05
WO2016149143A1 (en) 2016-09-22
US20160277957A1 (en) 2016-09-22
JP2018509102A (ja) 2018-03-29
EP3272154A1 (de) 2018-01-24
CN107409360A (zh) 2017-11-28
JP6605616B2 (ja) 2019-11-13
KR20170128340A (ko) 2017-11-22
US10264481B2 (en) 2019-04-16
KR102067884B1 (ko) 2020-01-17

Similar Documents

Publication Publication Date Title
EP3272154B1 (de) Techniken zur verwaltung der leistungsbetriebsarten eines benutzergeräts bei der kommunikation mit mehreren funkzugangstechnologien
JP6771628B2 (ja) 第２の受信機を用いた低電力不連続受信
US20210392658A1 (en) Method for reducing serving cell interruption due to prose operation
US9722731B2 (en) Techniques for aggregating data from WWAN and WLAN
US10973068B2 (en) Techniques for managing communication links of a plurality of radio access technologies (RATs)
EP3791623B1 (de) Verfahren und vorrichtung zur handhabung der konfiguration einer aktualisierung eines funkzugangsnetzwerkbenachrichtigungsbereichs (rna) nach der ablehnung
CN111316752B (zh) 无线电网络节点、无线设备以及其中执行的方法
US20190313475A1 (en) METHODS AND APPARATUS FOR CELL VERIFICATION UNDER UE eDRX
EP3949678B1 (de) Benutzergerät, funknetzwerkknoten, computerprogramm produkte, träger und darin ausgeführte verfahren zur kommunikationshandhabung
CN108353358B (zh) 延长高功率状态下的drx操作
US20160242182A1 (en) Techniques for selecting uplink transmit antenna in multiple connectivity wireless communications

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20170822

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 76/04 20181130ALI20160928BHEP

Ipc: H04W 52/02 20090101AFI20160928BHEP

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 76/04 20090101ALI20160928BHEP

Ipc: H04W 52/02 20090101AFI20160928BHEP

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 52/02 20090101AFI20190712BHEP

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20190823

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1233784

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200215

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602016029491

Country of ref document: DE

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20200304

Year of fee payment: 5

Ref country code: DE

Payment date: 20200309

Year of fee payment: 5

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20200306

Year of fee payment: 5

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200512

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200212

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200212

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20200212

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200512

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200612

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200513

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200212

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200212

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200212

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200212

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200212

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200705

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200212

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200212

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200212

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200212

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200212

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200212

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200212

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602016029491

Country of ref document: DE

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1233784

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200212

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200212

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20200331

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200311

26N No opposition filed

Effective date: 20201113

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200212

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200331

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200331

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200212

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200311

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200331

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200212

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200212

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602016029491

Country of ref document: DE

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20210311

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20211001

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210331

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210311

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200212

Ref country code: MT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200212

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200212

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200212

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200212