METHODS RELATING TO CROSS-CARRIER/CELL SCHEDULING FOR DUAL-DRX AND RELATED WIRELESS DEVICES

A method is disclosed to operate a wireless device configured for communication with a wireless network using first and second sets of cells. The first set of cells is associated with a first inactivity timer duration, the second set of cells is associated with a second inactivity timer duration, and the first and second inactivity timer durations are different. A scheduling grant is received for a cell of the second set of cells using a cell of the first set of cells. Responsive to receiving the scheduling grant, the cell of the first set of cells is monitored for subsequent grants for the cell of the second set of cells for a period following the scheduling grant defined by the first inactivity timer duration or defined by the second inactivity timer duration. Related wireless devices are also discussed.

TECHNICAL FIELD

The present disclosure relates generally to communications, and more particularly to communication methods and related devices and nodes supporting wireless communications.

BACKGROUND

A UE (User Equipment, and referred to as a wireless device) may be configured with a DRX (discontinuous reception) configuration in connected mode to save battery. When DRX is configured the UE is only required to monitor PDCCH (Physical Downlink Control Channel) when the UE is in “Active Time,” but when the UE is not in Active Time, the UE can skip PDCCH monitoring and hence save power (reduce battery usage).

Below is an excerpt from 3GPP TS 38.321 v15.6.0 section 5.7 which defines when the UE is considered to be in Active Time.

When a DRX cycle is configured, the Active Time includes the time while:drx-onDurationTimer or drx-InactivityTimer or drx-RetransmissionTimerDL or drx-RetransmissionTimerUL or ra-ContentionResolutionTimer (as described in clause 5.1.5) is running; ora Scheduling Request is sent on PUCCH and is pending (as described in clause 5.4.4); ora PDCCH indicating a new transmission addressed to the C-RNTI of the MAC entity has not been received after successful reception of a Random Access Response for the Random Access Preamble not selected by the MAC entity among the contention-based Random Access Preamble (as described in clause 5.1.4).
In this section, PUCCH is an acronym for Physical Uplink Control Channel, MAC is an acronym for Medium Access Control, and C-RNTI is an acronym for Cell Radio Network Temporary Identifier.

The UE starts the drx-onDurationTimer (sometimes referred to only as onDuration or similar) periodically and the period is referred to as the DRX cycle. Or in other words, the UE will once every DRX cycle start the onDuration timer and hence be in Active Time and monitor PDCCH. The longer the DRX cycle is the longer the UE can be “asleep” between OnDurations. And the longer the onDuration is, the longer time the UE will stay awake each DRX cycle.

However, since it is likely that if the network schedules the UE, the network would want to continue to schedule the UE for a while. Consider for example that the UE is downloading a file. The network would then have to wait until the UE wakes up (i.e., until the next onDuration) and then the network can start sending data to the UE. But if the onDuration is short, the network may not be able to complete the data transfer to the UE. To address this, the drx-InactivityTimer (or just “inactivity timer” or similar) is used. The inactivity timer is started by the UE each time the UE is scheduled (i.e. the UE receives a grant to send UL data after it sends a Scheduling Request, or UE receives downlink assignment because NW (Network) wants to send DL (DownLink) data). So even if the onDuration would be short, the UE starts the inactivity timer if it gets schedule and hence the UE will stay in Active Time as long as the UE keeps on getting scheduled.

The period between OnDurations is called “DRX cycle”. In other words, the UE will once per DRX cycle start the onDuration time which means that the UE will be in Active time

DRX cycles and the drx-InactivityTimer are discussed below.

A UE configured with the DRX can be configured with both long and short DRX cycles. The intention with the long DRX cycle is that the UE should be able to sleep a long time between waking up, while in short DRX cycle the UE wakes up more frequently. These time periods that the UE is awake to listen for scheduling requests is called OnDuration periods, and is configured for a certain time duration that the UE shall be awake. The UE first drops into a short DRX cycle, where the UE is still relatively quickly reachable, but if there is not traffic for some time, the UE drops into the long DRX cycle.

When the UE is scheduled the drx-InactivityTimer is started, and while this timer is running, the UE is in Active Time and hence monitors PDCCH. When the drx-InactivityTimer expires, the UE will go to short DRX sleep, if configured, otherwise the UE will go to long DRX sleep.

If the UE has not been scheduled for a configured number of short DRX cycles the UE will start applying long DRX cycles.

Dual DRX is discussed below.

It has been proposed to introduce, a so called, dual DRX. In one version of dual DRX, the UE has two different values for the drx-InactivityTimer and two different values for the onDuration timers. The UE would for one set of cells apply a first drx-InactivityTimer value and a first onDuration timer value, while for another set of cells apply a second drx-InactivityTimer value and a first onDuration timer value.

Note that in Dual Connectivity scenarios, the UE has two MAC (Medium Access Control) entities and each MAC entity has its own DRX operation. However, with dual DRX the UE would have two DRX processes per MAC entity, i.e. in total four DRX processes/procedures.

Cross-carrier/cell scheduling and self-scheduling is discussed below.

There is a feature called cross-carrier scheduling in NR (New Radio). The opposite of cross-carrier scheduling is, so-called, self-scheduling. Note that in the 3GPP specifications the terms “carrier” and “cell” are used interchangeably, so “cross-carrier scheduling” could be seen as “cross-cell scheduling”, i.e. one cell scheduling another cell. Here it is described how self-scheduling and cross carrier scheduling works by using an example with a cell A and a cell B.

In self-scheduling the scheduling for a cell is provided on the PDCCH of that cell itself. An uplink grant received on the PDCCH of cell A is valid for a transmission on cell A; and a downlink assignment received on the PDCCH of cell A is for a downlink transmission on cell A.

In cross-carrier scheduling the scheduling for a cell is provided on the PDCCH of another cell. An uplink grant is received on the PDCCH of cell A but that grant is valid for an uplink transmission on cell B; and a downlink assignment is received on the PDCCH of cell A but it is for a downlink transmission on cell B.

The term “scheduling cell” is used for a cell which schedules cells (schedule itself, or schedule other cells) while the term “scheduled” cell is used for a cell which gets scheduled. “To schedule” comprises providing uplink grants/downlink assignments. Basically, if a scheduling is “for” a cell then the scheduled transmission/reception will happen on/using that cell. But if scheduling is “on” a cell, that just means that the DL-assignment/UL-grant is sent on/using that cell, and in cross-carrier scheduling the cells are different, while for self-scheduling the cells are the same.

Problems may occur, however, when cross-carrier/cross-cell scheduling in dual-DRX is performed with different inactivity timer durations associated with the scheduling and scheduled cells.

SUMMARY

It may be an object of the invention to provide measures with which monitoring of a cell in cross-carrier scheduling scenarios can be performed in an energy efficient way.

According to some embodiments of inventive concepts, a method of operating a wireless device configured for communication with a wireless network using first and second sets of cells is provided. The first set of cells is associated with a first inactivity timer duration, the second set of cells is associated with a second inactivity timer duration, and the first and second inactivity timer durations are different. A scheduling grant for a cell of the second set of cells is received using a cell of the first set of cells. Responsive to receiving the scheduling grant, the cell of the first set of cells is monitored for subsequent grants for the cell of the second set of cells for a period following the scheduling grant defined by the first inactivity timer duration or defined by the second inactivity timer duration.

According to some embodiments of inventive concepts, a wireless device includes processing circuitry, and memory coupled with the processing circuitry. The memory includes instructions that when executed by the processing circuitry causes the wireless device to receive a scheduling grant for a cell of a second set of cells using a cell of a first set of cells. The first set of cells is associated with a first inactivity timer duration, the second set of cells is associated with a second inactivity timer duration, and the first and second inactivity timer durations are different. The memory also includes instructions that when executed by the processing circuitry causes the wireless device to, responsive to receiving the scheduling grant, monitor the cell of the first set of cells for subsequent grants for the cell of the second set of cells for a period following the scheduling grant defined by the first inactivity timer duration or defined by the second inactivity timer duration.

According to some embodiments of inventive concepts, a wireless device is adapted to receive a scheduling grant for a cell of a second set of cells using a cell of a first set of cells. The first set of cells is associated with a first inactivity timer duration, the second set of cells is associated with a second inactivity timer duration, and the first and second inactivity timer durations are different. The wireless device is also adapted to, responsive to receiving the scheduling grant, monitor the cell of the first set of cells for subsequent grants for the cell of the second set of cells for a period following the scheduling grant defined by the first inactivity timer duration or defined by the second inactivity timer duration.

According to some embodiments, by monitoring the scheduling cell (i.e., the cell of the first set of cells associated with the first inactivity timer duration) for subsequent grants for the scheduled cell (i.e., the cell of the second set of cells associated with the second inactivity timer duration) for the period following the scheduling grant, the wireless device may stay awake for a sufficient time to efficiently receive subsequent grants for the scheduled cell. Moreover, use of the first or second inactivity timer duration may reduce power consumption.

DETAILED DESCRIPTION

FIG. 1is a block diagram illustrating elements of a wireless device UE300(also referred to as a mobile terminal, a mobile communication terminal, a wireless communication device, a wireless terminal, mobile device, a wireless communication terminal, user equipment, UE, a user equipment node/terminal/device, etc.) configured to provide wireless communication according to embodiments of inventive concepts. (Wireless device300may be provided, for example, as discussed below with respect to wireless device QQ110ofFIG. 8.) As shown, wireless device UE may include an antenna307(e.g., corresponding to antenna QQ111ofFIG. 8), and transceiver circuitry301(also referred to as a transceiver, e.g., corresponding to interface QQ114ofFIG. 8) including a transmitter and a receiver configured to provide uplink and downlink radio communications with a base station(s) (e.g., corresponding to network node QQ160ofFIG. 8, also referred to as a RAN node) of a radio access network. Wireless device UE may also include processing circuitry303(also referred to as a processor, e.g., corresponding to processing circuitry QQ120ofFIG. 8) coupled to the transceiver circuitry, and memory circuitry305(also referred to as memory, e.g., corresponding to device readable medium QQ130ofFIG. 8) coupled to the processing circuitry. The memory circuitry305may include computer readable program code that when executed by the processing circuitry303causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry303may be defined to include memory so that separate memory circuitry is not required. Wireless device UE may also include an interface (such as a user interface) coupled with processing circuitry303, and/or wireless device UE may be incorporated in a vehicle.

As discussed herein, operations of wireless device UE may be performed by processing circuitry303and/or transceiver circuitry301. For example, processing circuitry303may control transceiver circuitry301to transmit communications through transceiver circuitry301over a radio interface to a radio access network node (also referred to as a base station) and/or to receive communications through transceiver circuitry301from a RAN node over a radio interface. Moreover, modules may be stored in memory circuitry305, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry303, processing circuitry303performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to wireless devices).

FIG. 2is a block diagram illustrating elements of a radio access network RAN node400(also referred to as a network node, base station, eNodeB/eNB, gNodeB/gNB, etc.) of a Radio Access Network (RAN) configured to provide cellular communication according to embodiments of inventive concepts. (RAN node400may be provided, for example, as discussed below with respect to network node QQ160ofFIG. 8.) As shown, the RAN node may include transceiver circuitry401(also referred to as a transceiver, e.g., corresponding to portions of interface QQ190ofFIG. 8) including a transmitter and a receiver configured to provide uplink and downlink radio communications with mobile terminals. The RAN node may include network interface circuitry407(also referred to as a network interface, e.g., corresponding to portions of interface QQ190ofFIG. 8) configured to provide communications with other nodes (e.g., with other base stations) of the RAN and/or core network CN. The network node may also include processing circuitry403(also referred to as a processor, e.g., corresponding to processing circuitry QQ170) coupled to the transceiver circuitry, and memory circuitry405(also referred to as memory, e.g., corresponding to device readable medium QQ180ofFIG. 8) coupled to the processing circuitry. The memory circuitry405may include computer readable program code that when executed by the processing circuitry403causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry403may be defined to include memory so that a separate memory circuitry is not required.

As discussed herein, operations of the RAN node may be performed by processing circuitry403, network interface407, and/or transceiver401. For example, processing circuitry403may control transceiver401to transmit downlink communications through transceiver401over a radio interface to one or more mobile terminals UEs and/or to receive uplink communications through transceiver401from one or more mobile terminals UEs over a radio interface. Similarly, processing circuitry403may control network interface407to transmit communications through network interface407to one or more other network nodes and/or to receive communications through network interface from one or more other network nodes. Moreover, modules may be stored in memory405, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry403, processing circuitry403performs respective operations.

According to some other embodiments, a network node may be implemented as a core network CN node without a transceiver. In such embodiments, transmission to a wireless device UE may be initiated by the network node so that transmission to the wireless device is provided through a network node including a transceiver (e.g., through a base station or RAN node). According to embodiments where the network node is a RAN node including a transceiver, initiating transmission may include transmitting through the transceiver.

FIG. 3is a block diagram illustrating elements of a core network CN node (e.g., an SMF node, an AMF node, etc.) of a communication network configured to provide cellular communication according to embodiments of inventive concepts. As shown, the CN node may include network interface circuitry507(also referred to as a network interface) configured to provide communications with other nodes of the core network and/or the radio access network RAN. The CN node may also include a processing circuitry503(also referred to as a processor) coupled to the network interface circuitry, and memory circuitry505(also referred to as memory) coupled to the processing circuitry. The memory circuitry505may include computer readable program code that when executed by the processing circuitry503causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry503may be defined to include memory so that a separate memory circuitry is not required.

As discussed herein, operations of the CN node may be performed by processing circuitry503and/or network interface circuitry507. For example, processing circuitry503may control network interface circuitry507to transmit communications through network interface circuitry507to one or more other network nodes and/or to receive communications through network interface circuitry from one or more other network nodes. Moreover, modules may be stored in memory505, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry503, processing circuitry503performs respective operations.

For dual-DRX there may be two inactivity timers, one for each group of cells. In case of self-scheduling it is clear which timer the UE shall start; namely if cell X schedules cell X the timer of cell X shall be started and when that inactivity timer is running the UE shall monitor PDCCH of cell X.

However in case of cross-carrier scheduling there may be some problems. For example, if a scheduling cell X is associated with a different inactivity timer than the scheduled cell Y, the UE may not stay awake and monitor for further scheduling on cell X if the UE starts the inactivity timer of cell Y upon being scheduled.

And further, it may in some scenarios cause unnecessary power consumption if the UE starts the inactivity timer of the scheduling cell X with the duration of the inactivity timer duration for scheduling cell X and during that time the UE monitors the scheduling cell X. An example scenario where this may be the case is where the UE is configured with cells on FR1 and cells on FR2 where, if the UE has to monitor for a long time after each scheduling (i.e., the inactivity timer is long), significant UE power may be wasted.

According to some embodiments of inventive concepts (Example A), the UE may maintain a first inactivity timer and a second inactivity timer where: the UE monitors for scheduling on a first set of cells if the first timer is running, and the UE monitors for scheduling on a second set of cells if the second timer is running. If the first cell schedules the second cell (cross carrier scheduling), the UE starts the first inactivity timer in response to scheduling of the second cell, and if the second cell schedules the second cell (self-scheduling), the UE starts the second inactivity timer in response to scheduling of the second cell.

Such embodiments may allow, for example, that if an FR1 cell schedules the FR2 cell, the UE will keep on monitoring PDCCH on the FR1 cell.

According to some other embodiments of inventive concepts (Example B), the UE maintains a first inactivity timer and a second inactivity timer where: the UE monitors for scheduling on a first set of cells if the first timer is running, and the UE monitors for scheduling on a second set of cells if the second timer is running. If the first cell schedules the second cell (cross carrier scheduling), the UE starts the first inactivity timer in response to scheduling of the second cell and the duration used to start the timer is a value associated with the second cell. If the second cell schedules the second cell (self-scheduling), the UE starts the second inactivity timer in response to scheduling of the second cell and the duration used to start the timer is a value associated with the first cell.

According to still other embodiments of inventive concepts (Example C), the UE maintains a first inactivity timer and a second inactivity timer where: the UE monitors scheduling for a first set of cells if the first inactivity timer is running, and the UE monitors scheduling for a second set of cells if the second inactivity timer is running. The UE starts the first inactivity timer in response to a first cell scheduling a cell in the first set of cells. The UE starts the second inactivity timer in response to a second cell scheduling a cell in the second set of cells. The UE starts the second inactivity timer in response to a first cell scheduling a cell in the second set of cells. Such embodiments may allow, for example, that if an FR1 cell schedules an FR2 cell, that the UE applies a shorter inactivity timer, and also that the UE actually monitors PDCCH for the FR2 cell when this happens.

Methods according to some embodiments may use as an example dual-DRX, but the methods could be applied also in scenarios where more than two DRX are used.

It is herein described how the UE starts timers, and in particular inactivity timers. It shall be appreciated that even if a timer is running, the timer can be started (which may be referred to as that the timer is restarted) but the timer would then be started with a new duration. For example, if the initial timer duration is 10 milliseconds but the timer has been running 2 milliseconds, and if the timer is then started/restarted, the timer duration would reset so that 10 milliseconds remain.

It will herein be used as examples that there are cells in a low frequency range (denoted as Frequency Range 1 (FR1)) and cells in a high frequency range (denoted as Frequency Range 2 (FR2)) and the UE has been configured in a way such that the UE shall monitor FR2 cells less often/shorter durations than FR1 cells. This may be a likely configuration since it consumes more power to monitor cells in a higher frequency and hence the amount of monitoring should be lower for FR2 cells. In the embodiments, it is sometimes used as examples that cells in a first group are FR1 cells and cells in a second group are FR2 cells, however this is just used as an example and the embodiments can be applied in a more general situations where cells are not necessarily grouped based on FR1/FR2.

According to some embodiments (Example A), a UE keeps on monitoring on the scheduling cell(s). In these embodiments the UE monitors: a first set of PDCCHs when a first inactivity timer is running, and a second set of PDCCHs when a second timer is running.

An inactivity timer could then be seen to be associated to certain set of PDCCHs and the UE monitors all PDCCHs in that set, when the associated inactivity timer is running.

The UE starts the timer associated to a set of PDCCHs whenever any PDCCH in that set schedules a cell.

In case a cell X is configured to schedule itself (i.e. self-scheduling) but also configured to schedule other cells (i.e. cross-carrier scheduling): if cell X (e.g. FR1 cell) schedules itself the timer associated with cell X will be started, and if cell X schedules a cell Y (e.g. FR2 cell) the UE will (also in this case) start the timer associated with cell X.

In an example illustrating embodiment A, the UE has five cells, A, B, C, D and E. The cells are schedules as follows: cell A (FR1) schedules itself; cell B (FR1) is scheduled by cell A; cell C (FR2) schedules itself; cell D (FR2) schedules itself; and cell E (FR2) is scheduled by cell A.

Further, Cell A and Cell B are associated with a first, e.g. long, timer value. While cell C, D and E are associated with a second, e.g. short, timer value (where timer values are also referred to as inactivity timer durations). In such embodiments, the UE would:when cell A is scheduled, start the first/long timer and for the duration of this timer the UE will monitor PDCCH on cell A.when cell B is scheduled, start the first/long timer and for the duration of this timer the UE will monitor PDCCH on cell A (which is the cell which schedules cell B).when cell C is scheduled, start the second/short timer and for the duration of this timer the UE will monitor PDCCH on cell C and D.when cell D is scheduled, start the second/short timer and for the duration of this timer the UE will monitor PDCCH on cell C and D.when cell E is scheduled, start the first/long timer and for the duration of this timer the UE will monitor PDCCH on cell A.

According to some other embodiments (Example B), the UE keeps on monitoring on the scheduling cell(s)—duration depends on which is the scheduled cell. In this embodiment the UE monitors: a first set of PDCCHs when a first inactivity timer is running, and a second set of PDCCHs when a second timer is running.

An inactivity timer could then be seen to be associated to certain set of PDCCHs and the UE monitors all PDCCHs in that set, when the associated inactivity timer is running.

The UE starts the timer associated with a set of PDCCHs whenever any PDCCH in that set schedules a cell. The value with which a timer is started depends on which cell was scheduled. If the cell which is scheduled is associated with a long timer duration, the inactivity timer would be started with a long timer duration, but if the cell which is scheduled is associated with a short timer duration, the inactivity timer would be started with a short timer duration.

In case both a cell associated with a long inactivity timer duration and a cell associated with a short inactivity timer duration is scheduled, the above dictates that the UE shall start the timer with both a long and a short duration, but in this scenario the UE may apply the longer timer duration when starting the timer.

In case an inactivity timer is already running and, based on the above, the UE shall start the inactivity timer and the value with which the inactivity timer shall be started with is shorter than the remaining duration of the timer at this moment, the UE may refrain from starting/restarting the timer with the shorter value, or in other words, the UE would let the timer continue to run with the (currently) longer remaining duration rather than shortening the timer duration.

In case a cell X is configured to schedule itself (i.e. self-scheduling) but also configured to schedule other cells (i.e. cross-carrier scheduling): if cell X (e.g. FR1 cell) schedules itself, the timer associated with cell X will be started but in this case with the value associated with cell X; and if cell X schedules a cell Y (e.g. FR2 cell), the UE will (also in this case) start the timer associated with cell X, but in this case with the value associated with cell Y.

An example illustrating this embodiment is discussed below. The UE has five cells, A, B, C, D and E. The cells are schedules as follows: cell A (FR1) schedules itself; cell B (FR1) is scheduled by cell A; cell C (FR2) schedules itself; cell D (FR2) schedules itself; and cell E (FR2) is scheduled by cell A.

Further, Cell A and Cell B are associated with a first, e.g. long, timer value (a long inactivity timer duration), while cell C, D and E are associated with a second, e.g. short, timer value (a short inactivity timer duration). In such embodiments, the UE would:when cell A is scheduled, start a first timer with a first/long value and for the duration of this timer the UE will monitor PDCCH on cell A.when cell B is scheduled, start a first timer with a first/long value and for the duration of this timer the UE will monitor PDCCH on cell A (which is the cell which schedules cell B).when cell C is scheduled, start a second timer with a second/short value and for the duration of this timer the UE will monitor PDCCH on cell C and D.when cell D is scheduled, start a second timer with a second/short value and for the duration of this timer the UE will monitor PDCCH on cell C and D.when cell E is scheduled, start a first timer with a second/short value and for the duration of this timer the UE will monitor PDCCH on cell A.

According to some other embodiments (Example C), the UE keeps on monitoring for the scheduled cell. In this embodiment the UE monitors: all PDCCH which can schedule a first set of cells (e.g. FR1 cells) if an inactivity timer associated with that set is running; and all PDCCH which can schedule a second group of cells (e.g. FR2 cells) if an inactivity timer associated with that set is running.

An inactivity timer could then be seen to be associated to certain set of cells and the UE monitors all PDCCHs which can schedule a cell in that set, when the associated inactivity timer is running.

The UE starts the inactivity timer for a set of cells whenever a cell in the set gets scheduled.

In case of cross-carrier scheduling, if a cell X (e.g. FR1 cell) schedules itself it will start the timer associated with the cell X (i.e. a timer associated with FR1 cells). While if the cell X schedules a cell Y (e.g. FR2 cell) the UE will start the timer associated with cell Y.

This may provide/ensure that if a cell in a certain group is scheduled, the UE will keep on monitoring all PDCCHs which may contain further scheduling for the cells in this group. For example, scheduling of an FR2 cell would start a timer associated with monitoring for FR2 cells and the UE will then continue to monitor all PDCCHs which can schedule FR2 cells.

An example illustrating such embodiments is discussed below. The UE has five cells, A, B, C, D and E. The cells are scheduled as follows: cell A (e.g. on FR1) schedules itself; cell B (e.g. on FR1) is scheduled by cell A; cell C (e.g. on FR2) schedules itself; cell D (e.g. on FR2) schedules itself; and cell E (e.g. on FR2) is scheduled by cell A.

Further, FR1 cells are associated with a long timer (a longer inactivity timer duration) while FR2 cells are associated with a short timer (a shorter inactivity timer duration). In such embodiments, the UE would:when cell A is scheduled, start the long timer and for the duration of this timer the UE will monitor PDCCH for cell A and cell B (namely PDCCH on cell A).when cell B is scheduled, start the long timer and for the duration of this timer the UE will monitor PDCCH for cell A and cell B (namely PDCCH on cell A).when cell C is scheduled, start the short timer and for the duration of this timer the UE will monitor PDCCH for cell C, D and E (namely PDCCH on cell C, D and A).when cell D is scheduled, start the short timer and for the duration of this timer the UE will monitor PDCCH for cell C, D and E (namely PDCCH on cell C, D and A).when cell E is scheduled, start the short timer and for the duration of this timer the UE will monitor PDCCH for cell C, D and E (namely PDCCH on cell C, D and A).

When it in this embodiment says that the UE monitors PDCCH “for” a group of cells it may mean one of the following approaches:1. the UE will only monitor and/or act on scheduling of cells in that group, but the UE may ignore scheduling for other cells even if those other cells are scheduled on the same PDCCH. Or in other words by referring to the example above: When cell A or cell B has been scheduled and the UE monitors PDCCH on cell A, the UE would according to this approach act on scheduling for cell A and cell B, but not act on scheduling for cell E. Note that the UE may monitor PDCCH for the “other cells” for other reasons, e.g. there may be some other DRX-related timer which is running which makes the UE monitor for scheduling for other cells than those within the group of cells. Back to the example above: even if the UE, according to this approach, would ignore scheduling for cell E since the UE is monitoring PDCCH “for” cell A and cell B, the UE may anyway act on scheduling for cell E if the UE should monitor PDCCH for cell E for some other reason (e.g. the short timer is running).2. the UE will when monitoring scheduling for cells in a group act on any scheduling for that cell, i.e. also on cells which are not in the group for which the UE monitors PDCCH. Or in other words by referring to the example above: When cell A or cell B has been scheduled and the UE monitors PDCCH on cell A, the UE would according to this approach act on scheduling for any cell which cell A schedules, namely scheduling for any of cell A, B and E.

When it here says that there is a timer associated with a group of cells, it could comprise either that there is an actual timer associated with the group of cells, or that there is a timer duration (also referred to as an inactivity timer duration) which is associated with the group of cells. And a timer for monitoring a certain set of PDCCHs is started with different duration depending on which group of cells the timer is started for.

Operations of the wireless device300(implemented using the structure of the block diagram ofFIG. 1) will now be discussed with reference to the flow chart ofFIG. 4according to some embodiments of inventive concepts. For example, modules may be stored in memory305ofFIG. 1, and these modules may provide instructions so that when the instructions of a module are executed by respective communication device processing circuitry303, processing circuitry303performs respective operations of the flow chart.

According to some embodiments ofFIG. 4, wireless device300is configured for communication with a wireless network using first and second sets of cells. The first set of cells is associated with a first inactivity timer duration, the second set of cells is associated with a second inactivity timer duration, and the first and second inactivity timer durations are different.

According to some embodiments at block1405, processing circuitry303receives (through transceiver301) a first scheduling grant for a cell of the second set of cells using a first cell of the first set of cells (e.g., receiving the first scheduling grant on the first cell of the first set of cells).

According to some embodiments at block1409, responsive to receiving the first scheduling grant, processing circuitry303monitors the first cell of the first set of cells for subsequent grants for a period following the first scheduling grant defined by the first inactivity timer duration or defined by the second inactivity timer duration. For example, processing circuitry303may monitor the first cell of the first set of cells for subsequent grants for the cell of the second set of cells for a period following the scheduling grant defined by the first inactivity timer duration or defined by the second inactivity timer duration.

According to some embodiments at block1411, processing circuitry303provides communication (through transceiver301) between the wireless device and the wireless network using a communication resource on the cell of the second set of cells defined by the first scheduling grant.

According to some embodiments at block1415, processing circuitry303receives (through transceiver301) a second scheduling grant for a second cell of the first set of cells using the first cell of the first set of cells (e.g., receiving the second scheduling grant on the first cell of the first set of cells).

According to some embodiments at block1419, responsive to receiving the second scheduling grant, processing circuitry303monitors the first cell of the first set of cells for subsequent grants for a period following the second scheduling grant defined by the first inactivity timer duration. For example, processing circuitry303monitors the first cell of the first set of cells for subsequent grants for the second cell of the first set of cells for the period following the second scheduling grant defined by the first inactivity timer duration.

According to some embodiments at block1425, processing circuitry303provides communication (through transceiver301) between the wireless device and the wireless network using a communication resource on the second cell of the first set of cells defined by the second scheduling grant.

According to some embodiments ofFIG. 4, the first set of cells are included in a first frequency range, and the second set of cells are included in a second frequency range. Moreover, the first and second frequency ranges may be non-overlapping. For example, the first frequency range may be lower than the second frequency range, and/or the first inactivity timer duration may be greater than the second inactivity timer duration.

Various operations from the flow chart ofFIG. 4may be optional with respect to some embodiments of wireless devices and related methods. Regarding methods of some embodiments, for example, operations of blocks1411,1415,1419, and/or1425ofFIG. 4may be optional.

Operations of the wireless device300(implemented using the structure of the block diagram ofFIG. 1) will now be discussed with reference to the flow chart ofFIG. 5according to some embodiments of inventive concepts. For example, modules may be stored in memory305ofFIG. 1, and these modules may provide instructions so that when the instructions of a module are executed by respective communication device processing circuitry303, processing circuitry303performs respective operations of the flow chart.

According to some embodiments ofFIG. 5, wireless device300is configured for communication with a wireless network using first and second sets of cells. The first set of cells is associated with a first inactivity timer duration, the second set of cells is associated with a second inactivity timer duration, and the first and second inactivity timer durations are different.

According to some embodiments at block1605, processing circuitry303receives (through transceiver301) a first scheduling grant for a first cell of the second set of cells using a first cell of the first set of cells (e.g., receiving the first scheduling grant for the first cell of the second set of cells on the first cell of the first set of cells).

According to some embodiments at block1609, responsive to receiving the first scheduling grant, processing circuitry303monitors the first cell of the first set of cells for subsequent grants for a period following the first scheduling grant defined by the first inactivity timer duration or defined by the second inactivity timer duration. For example, processing circuitry303may monitor the first cell of the first set of cells for subsequent grants for the first cell of the second set of cells for a period following the scheduling grant defined by the first inactivity timer duration or defined by the second inactivity timer duration.

According to some embodiments at block1611, processing circuitry303provides communication (through transceiver301) between the wireless device and the wireless network using a communication resource on the first cell of the second set of cells defined by the first scheduling grant.

According to some embodiments at block1615, processing circuitry303receives (through transceiver301) a second scheduling grant for a second cell of the second set of cells using the second cell of the second set of cells (e.g., receiving the second scheduling grant on the second cell of the second set of cells).

According to some embodiments at block1619, responsive to receiving the second scheduling grant, processing circuitry303monitors the second cell of the second set of cells for subsequent scheduling grants for a period following the second scheduling grant defined by the second inactivity timer duration. For example, processing circuitry303monitors the second cell of the second set of cells for subsequent scheduling grants for the second cell of the second set of cells for a period following the second scheduling grant defined by the second inactivity timer duration.

According to some embodiments at block1621, responsive to receiving the second scheduling grant, processing circuitry303monitors a third cell of the second set of cells for subsequent scheduling grants for the period following the second scheduling grant defined by the second inactivity timer duration. For example, processing circuitry303monitors a third cell of the second set of cells for subsequent scheduling grants for the third cell of the second set of cells for the period following the second scheduling grant defined by the second inactivity timer duration.

According to some embodiments at block1625, processing circuitry303provides communication (through transceiver301) between the wireless device and the wireless network using a communication resource on the second cell of the second set of cells defined by the second scheduling grant.

According to some embodiments ofFIG. 5, the first set of cells are included in a first frequency range, and the second set of cells are included in a second frequency range. Moreover, the first and second frequency ranges may be non-overlapping. For example, the first frequency range may be lower than the second frequency range, and/or the first inactivity timer duration may be greater than the second inactivity timer duration.

Various operations from the flow chart ofFIG. 5may be optional with respect to some embodiments of wireless devices and related methods. Regarding methods of some embodiments, for example, operations of blocks1611,1615,1619,1621, and/or1625ofFIG. 5may be optional.

Operations of the wireless device300(implemented using the structure of the block diagram ofFIG. 1) will now be discussed with reference to the flow chart ofFIG. 6according to some embodiments of inventive concepts. For example, modules may be stored in memory305ofFIG. 1, and these modules may provide instructions so that when the instructions of a module are executed by respective communication device processing circuitry303, processing circuitry303performs respective operations of the flow chart.

According to some embodiments ofFIG. 6, wireless device300is configured for communication with a wireless network using first and second sets of cells. The first set of cells is associated with a first inactivity timer duration, the second set of cells is associated with a second inactivity timer duration, and the first and second inactivity timer durations are different.

According to some embodiments at block1805, processing circuitry303receives (through transceiver301) a first scheduling grant for a first cell of the second set of cells using a first cell of the first set of cells (e.g., receiving the first scheduling grant on the first cell of the first set of cells).

According to some embodiments at block1809, responsive to receiving the first scheduling grant, processing circuitry303monitors the first cell of the first set of cells for subsequent grants for a period following the first scheduling grant defined by the first inactivity timer duration or defined by the second inactivity timer duration. For example, processing circuitry303may monitor the first cell of the first set of cells for subsequent grants for the first cell of the second set of cells for a period following the scheduling grant defined by the first inactivity timer duration or defined by the second inactivity timer duration.

According to some embodiments at block1810, responsive to receiving the first scheduling grant, processing circuitry303monitors a second cell of the second set of cells for subsequent grants. For example, processing circuitry303may monitor a second cell of the second set of cells for subsequent grants for the second set of cells.

According to some embodiments at block1811, responsive to receiving the first scheduling grant, processing circuitry303monitors a third cell of the second set of cells for subsequent grants for the second set of cells. For example, processing circuitry303may monitor a third cell of the second set of cells for subsequent grants for the second set of cells.

According to some embodiments at block1813, processing circuitry303provides communication (through transceiver301) between the wireless device and the wireless network using a communication resource on the first cell of the second set of cells defined by the first scheduling grant.

According to some embodiments at block1815, processing circuitry303receives (through transceiver301) a second scheduling grant for a second cell of the first set of cells using the first cell of the first set of cells (e.g., receiving the second scheduling grant on the first cell of the first set of cells).

According to some embodiments at block1819, responsive to receiving the second scheduling grant, processing circuitry303monitors the first cell of the first set of cells for subsequent grants for the first set of cells for a period following the second scheduling grant defined by the first inactivity timer duration. For example, processing circuitry303may monitor the first cell of the first set of cells for subsequent grants for the first set of cells for a period following the second scheduling grant defined by the first inactivity timer duration.

According to some embodiments at block1825, processing circuitry303provides communication (through transceiver301) between the wireless device and the wireless network using a communication resource on the second cell of the first set of cells defined by the second scheduling grant.

According to some embodiments, monitoring the first cell of the first set of cells at block1809may include monitoring the first cell of the first set of cells for subsequent grants for the first cell of the second set of cells for a period following the first scheduling grant defined by the second inactivity timer duration, and monitoring the second cell of the second set of cells at block1810may include monitoring the second cell of the second set of cells for subsequent grants for the second set of cells for the period following the first scheduling grant defined by the second inactivity timer duration.

According to some embodiments ofFIG. 6, the first set of cells are included in a first frequency range, and the second set of cells are included in a second frequency range. Moreover, the first and second frequency ranges may be non-overlapping. For example, the first frequency range may be lower than the second frequency range, and/or the first inactivity timer duration may be greater than the second inactivity timer duration.

Various operations from the flow chart ofFIG. 6may be optional with respect to some embodiments of wireless devices and related methods. Regarding methods of some embodiments, for example, operations of blocks1810,1811,1813,1815,1819, and/or1825ofFIG. 6may be optional.

Operations of the wireless device300(implemented using the structure of the block diagram ofFIG. 1) will now be discussed with reference to the flow chart ofFIG. 7according to some embodiments of inventive concepts. For example, modules may be stored in memory305ofFIG. 1, and these modules may provide instructions so that when the instructions of a module are executed by respective communication device processing circuitry303, processing circuitry303performs respective operations of the flow chart.

According to some embodiments ofFIG. 7, wireless device300is configured for communication with a wireless network using first and second sets of cells. The first set of cells is associated with a first inactivity timer duration, the second set of cells is associated with a second inactivity timer duration, and the first and second inactivity timer durations are different.

According to some embodiments at block2005, processing circuitry303receives (through transceiver301) a first scheduling grant for a first cell of the second set of cells using a first cell of the first set of cells (e.g., receiving the first scheduling grant on the first cell of the first set of cells).

According to some embodiments at block2009, responsive to receiving the first scheduling grant, processing circuitry303monitors the first cell of the first set of cells for subsequent grants for a period following the first scheduling grant defined by the first inactivity timer duration or defined by the second inactivity timer duration. For example, processing circuitry303may monitor the first cell of the first set of cells for subsequent grants for the first cell of the second set of cells for a period following the scheduling grant defined by the first inactivity timer duration or defined by the second inactivity timer duration.

According to some embodiments at block2010, responsive to receiving the first scheduling grant, processing circuitry303monitors a second cell of the second set of cells for subsequent grants. For example, processing circuitry303may monitor a second cell of the second set of cells for subsequent grants for the second set of cells.

According to some embodiments at block2011, responsive to receiving the first scheduling grant, processing circuitry303monitors a third cell of the second set of cells for subsequent grants. For example, processing circuitry303may monitor a third cell of the second set of cells for subsequent grants for the second set of cells.

According to some embodiments at block2013, processing circuitry303provides communication (through transceiver301) between the wireless device and the wireless network using a communication resource on the first cell of the second set of cells defined by the first scheduling grant.

According to some embodiments at block2015, processing circuitry303receives (through transceiver301) a second scheduling grant for the second cell of the second set of cells using the second cell of the second set of cells (e.g., receiving the second scheduling grant on the second cell of the second set of cells).

According to some embodiments at block2019, responsive to receiving the second scheduling grant, processing circuitry303monitors the second cell of the second set of cells for subsequent scheduling grants. For example, processing circuitry303may monitor the second cell of the second set of cells for subsequent scheduling grants for the second cell of the second set of cells.

According to some embodiments at block2021, responsive to receiving the second scheduling grant, processing circuitry303monitors the cell of the first set of cells for subsequent grants. For example, processing circuitry303may monitor the cell of the first set of cells for subsequent grants for the first cell of the second set of cells.

According to some embodiments at block2025, processing circuitry303provides communication (through transceiver301) between the wireless device and the wireless network using a communication resource on the second cell of the second set of cells defined by the second scheduling grant.

According to some embodiments, monitoring the first cell of the first set of cells at block2009may include monitoring the first cell of the first set of cells for subsequent grants for the first cell of the second set of cells for a period following the first scheduling grant defined by the second inactivity timer duration, and monitoring the second cell of the second set of cells at block2010may include monitoring the second cell of the second set of cells for subsequent grants for the second set of cells for the period following the first scheduling grant defined by the second inactivity timer duration.

According to some embodiments, monitoring the second cell of the second set of cells responsive to receiving the second scheduling grant at block2019may include monitoring the second cell of the second set of cells for subsequent scheduling grants for the second cell of the second set of cells for a period following the second scheduling grant defined by the second inactivity timer duration, and monitoring the first cell of the first set of cells responsive to receiving the second scheduling grant at block2021may include monitoring the first cell of the first set of cells for subsequent grants for the first cell of the second set of cells for a period following the second scheduling grant defined by the second inactivity timer duration.

According to some embodiments ofFIG. 7, the first set of cells are included in a first frequency range, and the second set of cells are included in a second frequency range. Moreover, the first and second frequency ranges may be non-overlapping. For example, the first frequency range may be lower than the second frequency range, and/or the first inactivity timer duration may be greater than the second inactivity timer duration.

Various operations from the flow chart ofFIG. 7may be optional with respect to some embodiments of wireless devices and related methods. Regarding methods of some embodiments, for example, operations of blocks2010,2011,2013,2015,2019,2021, and/or2025ofFIG. 7may be optional.

Example embodiments are discussed below.

1. A method of operating a wireless device configured for communication with a wireless network using first and second sets of cells, wherein the first set of cells is associated with a first inactivity timer duration, wherein the second set of cells is associated with a second inactivity timer duration, and wherein the first and second inactivity timer durations are different, the method comprising: receiving a scheduling grant for a cell of the second set of cells using a cell of the first set of cells; and responsive to receiving the scheduling grant, monitoring the cell of the first set of cells for subsequent grants for the cell of the second set of cells for a period following the scheduling grant defined by the first inactivity timer duration.

2. The method of Embodiment 1, wherein the cell of the first set of cells is a first cell of the first set of cells, and wherein the scheduling grant is a first scheduling grant, the method further comprising: receiving a second scheduling grant for a second cell of the first set of cells using the first cell of the first set of cells; and responsive to receiving the second scheduling grant, monitoring the first cell of the first set of cells for subsequent grants for the second cell of the first set of cells for a period following the second scheduling grant defined by the first inactivity timer duration.

3. The method of Embodiment 2 further comprising: providing communication between the wireless device and the wireless network using a communication resource on the second cell of the first set of cells defined by the second scheduling grant.

4. The method of Embodiment 1, where the cell of the second set of cells is a first cell of the second set of cells, and wherein the scheduling grant is a first scheduling grant, the method further comprising: receiving a second scheduling grant for a second cell of the second set of cells using the second cell of the second set of cells; and responsive to receiving the second scheduling grant, monitoring the second cell of the second set of cells for subsequent scheduling grants for the second cell of the second set of cells for a period following the second scheduling grant defined by the second inactivity timer.

5. The method of Embodiment 4 further comprising: responsive to receiving the second scheduling grant, monitoring a third cell of the second set of cells for subsequent scheduling grants for the third cell of the second set of cells for the period following the second scheduling grant defined by the second inactivity timer.

6. The method of any of Embodiments 4-5 further comprising: providing communication between the wireless device and the wireless network using a communication resource on the second cell of the second set of cells defined by the second scheduling grant.

7. The method of any of Embodiments 1-6 further comprising: providing communication between the wireless device and the wireless network using a communication resource on the cell of the second set of cells defined by the scheduling grant.

8. The method of any of Embodiments 1-7, wherein the first set of cells are included in a first frequency range, wherein the second set of cells are included in a second frequency range, and wherein the first and second frequency ranges are non-overlapping.

9. The method of Embodiment 8, wherein the first frequency range is lower than the second frequency range.

10. The method of any of Embodiments 1-9, wherein the first inactivity timer duration is greater than the second inactivity timer duration.

11. A method of operating a wireless device configured for communication with a wireless network using first and second sets of cells, wherein the first set of cells is associated with a first inactivity timer duration, wherein the second set of cells is associated with a second inactivity timer duration, and wherein the first and second inactivity timer durations are different, the method comprising: receiving a scheduling grant for a cell of the second set of cells using a cell of the first set of cells; and responsive to receiving the scheduling grant, monitoring the cell of the first set of cells for subsequent grants for the cell of the second set of cells for a period following the scheduling grant defined by the second inactivity timer duration.

12. The method of Embodiment 11, wherein the cell of the first set of cells is a first cell of the first set of cells, and wherein the scheduling grant is a first scheduling grant, the method further comprising: receiving a second scheduling grant for a second cell of the first set of cells using the first cell of the first set of cells; and responsive to receiving the second scheduling grant, monitoring the first cell of the first set of cells for subsequent grants for the second cell of the first set of cells for a period following the second scheduling grant defined by the first inactivity timer duration.

13. The method of Embodiment 12 further comprising: providing communication between the wireless device and the wireless network using a communication resource on the second cell of the first set of cells defined by the second scheduling grant.

14. The method of Embodiment 11, where the cell of the second set of cells is a first cell of the second set of cells, and wherein the scheduling grant is a first scheduling grant, the method further comprising: receiving a second scheduling grant for a second cell of the second set of cells using the second cell of the second set of cells; and responsive to receiving the second scheduling grant, monitoring the second cell of the second set of cells for subsequent scheduling grants for the second cell of the second set of cells for a period following the second scheduling grant defined by the second inactivity timer.

15. The method of Embodiment 14 further comprising: responsive to receiving the second scheduling grant, monitoring a third cell of the second set of cells for subsequent scheduling grants for the third cell of the second set of cells for the period following the second scheduling grant defined by the second inactivity timer.

16. The method of any of Embodiments 14-15 further comprising: providing communication between the wireless device and the wireless network using a communication resource on the second cell of the second set of cells defined by the second scheduling grant.

17. The method of any of Embodiments 11-16 further comprising: providing communication between the wireless device and the wireless network using a communication resource on the cell of the second set of cells defined by the scheduling grant.

18. The method of any of Embodiments 11-17, wherein the first set of cells are included in a first frequency range, wherein the second set of cells are included in a second frequency range, and wherein the first and second frequency ranges are non-overlapping.

19. The method of Embodiment 18, wherein the first frequency range is lower than the second frequency range.

20. The method of any of Embodiments 11-19, wherein the first inactivity timer duration is greater than the second inactivity timer duration.

21. A method of operating a wireless device configured for communication with a wireless network using first and second sets of cells, wherein the first set of cells is associated with a first inactivity timer duration, wherein the second set of cells is associated with a second inactivity timer duration, and wherein the first and second inactivity timer durations are different, the method comprising: receiving a scheduling grant for a first cell of the second set of cells using a cell of the first set of cells; responsive to receiving the scheduling grant, monitoring the cell of the first set of cells for subsequent grants for the first cell of the second set of cells; and responsive to receiving the scheduling grant, monitoring a second cell of the second set of cells for subsequent grants for the second set of cells.

22. The method of Embodiment 21 further comprising: responsive to receiving the scheduling grant, monitoring a third cell of the second set of cells for subsequent grants for the second set of cells.

23. The method of any of any of Embodiments 21-22, wherein monitoring the cell of the first set of cells comprises monitoring the cell of the first set of cells for subsequent grants for the first cell of the second set of cells for a period following the scheduling grant defined by the second inactivity timer duration, and wherein monitoring the second cell of the second set of cells comprises monitoring the second cell of the second set of cells for subsequent grants for the second set of cells for the period following the scheduling grant defined by the second inactivity timer duration.

24. The method of any of Embodiments 21-23, wherein the cell of the first set of cells is a first cell of the first set of cells, and wherein the scheduling grant is a first scheduling grant, the method further comprising: receiving a second scheduling grant for a second cell of the first set of cells using the first cell of the first set of cells; and responsive to receiving the second scheduling grant, monitoring the first cell of the first set of cells for subsequent grants for the first set of cells for a period following the second scheduling grant defined by the first inactivity timer duration.

25. The method of Embodiment 24 further comprising: providing communication between the wireless device and the wireless network using a communication resource on the second cell of the first set of cells defined by the second scheduling grant.

26. The method of any of Embodiments 21-23, wherein the scheduling grant is a first scheduling grant, the method further comprising: receiving a second scheduling grant for the second cell of the second set of cells using the second cell of the second set of cells; responsive to receiving the second scheduling grant, monitoring the second cell of the second set of cells for subsequent scheduling grants for the second cell of the second set of cells; and responsive to receiving the second scheduling grant, monitoring the cell of the first set of cells for subsequent grants for the first cell of the second set of cells.

27. The method of Embodiment 26 wherein monitoring the second cell of the second set of cells responsive to receiving the second scheduling grant comprises monitoring the second cell of the second set of cells for subsequent scheduling grants for the second cell of the second set of cells for a period following the second scheduling grant defined by the second inactivity timer, and wherein monitoring the cell of the first set of cells responsive to receiving the second scheduling grant comprises monitoring the cell of the first set of cells for subsequent grants for the first cell of the second set of cells for a period following the second scheduling grant defined by the second inactivity timer.

28. The method of any of Embodiments 26-27 further comprising:

providing communication between the wireless device and the wireless network using a communication resource on the second cell of the second set of cells defined by the second scheduling grant.

29. The method of any of Embodiments 21-28 further comprising:

providing communication between the wireless device and the wireless network using a communication resource on the first cell of the second set of cells defined by the scheduling grant.

30. The method of any of Embodiments 21-29, wherein the first set of cells are included in a first frequency range, wherein the second set of cells are included in a second frequency range, and wherein the first and second frequency ranges are non-overlapping.

31. The method of Embodiment 30, wherein the first frequency range is lower than the second frequency range.

32. The method of any of Embodiments 21-31, wherein the first inactivity timer duration is greater than the second inactivity timer duration.

33. A wireless device (300) comprising: processing circuitry (303); and memory (305) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the wireless device to perform operations according to any of Embodiments 1-32.

34. A wireless device (300) adapted to perform according to any of Embodiments 1-32.

35. A computer program comprising program code to be executed by processing circuitry (303) of a wireless device (300), whereby execution of the program code causes the wireless device (300) to perform operations according to any of embodiments 1-32.

36. A computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (303) of a wireless device (300), whereby execution of the program code causes the wireless device (300) to perform operations according to any of embodiments 1-32.

Additional explanation is provided below.

FIG. 8illustrates a wireless network in accordance with some embodiments.

InFIG. 8, network node QQ160includes processing circuitry QQ170, device readable medium QQ180, interface QQ190, auxiliary equipment QQ184, power source QQ186, power circuitry QQ187, and antenna QQ162. Although network node QQ160illustrated in the example wireless network ofFIG. 8may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, while the components of network node QQ160are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium QQ180may comprise multiple separate hard drives as well as multiple RAM modules).

Processing circuitry QQ170is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry QQ170may include processing information obtained by processing circuitry QQ170by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Processing circuitry QQ170may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node QQ160components, such as device readable medium QQ180, network node QQ160functionality. For example, processing circuitry QQ170may execute instructions stored in device readable medium QQ180or in memory within processing circuitry QQ170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry QQ170may include a system on a chip (SOC).

In some embodiments, processing circuitry QQ170may include one or more of radio frequency (RF) transceiver circuitry QQ172and baseband processing circuitry QQ174. In some embodiments, radio frequency (RF) transceiver circuitry QQ172and baseband processing circuitry QQ174may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry QQ172and baseband processing circuitry QQ174may be on the same chip or set of chips, boards, or units

In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry QQ170executing instructions stored on device readable medium QQ180or memory within processing circuitry QQ170. In alternative embodiments, some or all of the functionality may be provided by processing circuitry QQ170without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry QQ170can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry QQ170alone or to other components of network node QQ160, but are enjoyed by network node QQ160as a whole, and/or by end users and the wireless network generally.

Interface QQ190is used in the wired or wireless communication of signalling and/or data between network node QQ160, network QQ106, and/or WDs QQ110. As illustrated, interface QQ190comprises port(s)/terminal(s) QQ194to send and receive data, for example to and from network QQ106over a wired connection. Interface QQ190also includes radio front end circuitry QQ192that may be coupled to, or in certain embodiments a part of, antenna QQ162. Radio front end circuitry QQ192comprises filters QQ198and amplifiers QQ196. Radio front end circuitry QQ192may be connected to antenna QQ162and processing circuitry QQ170. Radio front end circuitry may be configured to condition signals communicated between antenna QQ162and processing circuitry QQ170. Radio front end circuitry QQ192may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry QQ192may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ198and/or amplifiers QQ196. The radio signal may then be transmitted via antenna QQ162. Similarly, when receiving data, antenna QQ162may collect radio signals which are then converted into digital data by radio front end circuitry QQ192. The digital data may be passed to processing circuitry QQ170. In other embodiments, the interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, network node QQ160may not include separate radio front end circuitry QQ192, instead, processing circuitry QQ170may comprise radio front end circuitry and may be connected to antenna QQ162without separate radio front end circuitry QQ192. Similarly, in some embodiments, all or some of RF transceiver circuitry QQ172may be considered a part of interface QQ190. In still other embodiments, interface QQ190may include one or more ports or terminals QQ194, radio front end circuitry QQ192, and RF transceiver circuitry QQ172, as part of a radio unit (not shown), and interface QQ190may communicate with baseband processing circuitry QQ174, which is part of a digital unit (not shown).

Antenna QQ162, interface QQ190, and/or processing circuitry QQ170may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna QQ162, interface QQ190, and/or processing circuitry QQ170may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.

Power circuitry QQ187may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node QQ160with power for performing the functionality described herein. Power circuitry QQ187may receive power from power source QQ186. Power source QQ186and/or power circuitry QQ187may be configured to provide power to the various components of network node QQ160in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source QQ186may either be included in, or external to, power circuitry QQ187and/or network node QQ160. For example, network node QQ160may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry QQ187. As a further example, power source QQ186may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry QQ187. The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used.

Alternative embodiments of network node QQ160may include additional components beyond those shown inFIG. 8that may be responsible for providing certain aspects of the network node's functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, network node QQ160may include user interface equipment to allow input of information into network node QQ160and to allow output of information from network node QQ160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node QQ160.

As illustrated, wireless device QQ110includes antenna QQ111, interface QQ114, processing circuitry QQ120, device readable medium QQ130, user interface equipment QQ132, auxiliary equipment QQ134, power source QQ136and power circuitry QQ137. WD QQ110may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD QQ110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD QQ110.

Antenna QQ111may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface QQ114. In certain alternative embodiments, antenna QQ111may be separate from WD QQ110and be connectable to WD QQ110through an interface or port. Antenna QQ111, interface QQ114, and/or processing circuitry QQ120may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna QQ111may be considered an interface.

As illustrated, interface QQ114comprises radio front end circuitry QQ112and antenna QQ111. Radio front end circuitry QQ112comprise one or more filters QQ118and amplifiers QQ116. Radio front end circuitry QQ114is connected to antenna QQ111and processing circuitry QQ120, and is configured to condition signals communicated between antenna QQ111and processing circuitry QQ120. Radio front end circuitry QQ112may be coupled to or a part of antenna QQ111. In some embodiments, WD QQ110may not include separate radio front end circuitry QQ112; rather, processing circuitry QQ120may comprise radio front end circuitry and may be connected to antenna QQ111. Similarly, in some embodiments, some or all of RF transceiver circuitry QQ122may be considered a part of interface QQ114. Radio front end circuitry QQ112may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry QQ112may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ118and/or amplifiers QQ116. The radio signal may then be transmitted via antenna QQ111. Similarly, when receiving data, antenna QQ111may collect radio signals which are then converted into digital data by radio front end circuitry QQ112. The digital data may be passed to processing circuitry QQ120. In other embodiments, the interface may comprise different components and/or different combinations of components.

Processing circuitry QQ120may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD QQ110components, such as device readable medium QQ130, WD QQ110functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry QQ120may execute instructions stored in device readable medium QQ130or in memory within processing circuitry QQ120to provide the functionality disclosed herein.

As illustrated, processing circuitry QQ120includes one or more of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry QQ120of WD QQ110may comprise a SOC. In some embodiments, RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry QQ124and application processing circuitry QQ126may be combined into one chip or set of chips, and RF transceiver circuitry QQ122may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry QQ122and baseband processing circuitry QQ124may be on the same chip or set of chips, and application processing circuitry QQ126may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry QQ122may be a part of interface QQ114. RF transceiver circuitry QQ122may condition RF signals for processing circuitry QQ120.

In certain embodiments, some or all of the functionality described herein as being performed by a WD may be provided by processing circuitry QQ120executing instructions stored on device readable medium QQ130, which in certain embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry QQ120without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry QQ120can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry QQ120alone or to other components of WD QQ110, but are enjoyed by WD QQ110as a whole, and/or by end users and the wireless network generally.

Processing circuitry QQ120may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry QQ120, may include processing information obtained by processing circuitry QQ120by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD QQ110, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Device readable medium QQ130may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry QQ120. Device readable medium QQ130may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry QQ120. In some embodiments, processing circuitry QQ120and device readable medium QQ130may be considered to be integrated.

User interface equipment QQ132may provide components that allow for a human user to interact with WD QQ110. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment QQ132may be operable to produce output to the user and to allow the user to provide input to WD QQ110. The type of interaction may vary depending on the type of user interface equipment QQ132installed in WD QQ110. For example, if WD QQ110is a smart phone, the interaction may be via a touch screen; if WD QQ110is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface equipment QQ132may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment QQ132is configured to allow input of information into WD QQ110, and is connected to processing circuitry QQ120to allow processing circuitry QQ120to process the input information. User interface equipment QQ132may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment QQ132is also configured to allow output of information from WD QQ110, and to allow processing circuitry QQ120to output information from WD QQ110. User interface equipment QQ132may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment QQ132, WD QQ110may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.

Power source QQ136may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used. WD QQ110may further comprise power circuitry QQ137for delivering power from power source QQ136to the various parts of WD QQ110which need power from power source QQ136to carry out any functionality described or indicated herein. Power circuitry QQ137may in certain embodiments comprise power management circuitry. Power circuitry QQ137may additionally or alternatively be operable to receive power from an external power source; in which case WD QQ110may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry QQ137may also in certain embodiments be operable to deliver power from an external power source to power source QQ136. This may be, for example, for the charging of power source QQ136. Power circuitry QQ137may perform any formatting, converting, or other modification to the power from power source QQ136to make the power suitable for the respective components of WD QQ110to which power is supplied.

FIG. 9illustrates a user Equipment in accordance with some embodiments.

InFIG. 9, UE QQ200includes processing circuitry QQ201that is operatively coupled to input/output interface QQ205, radio frequency (RF) interface QQ209, network connection interface QQ211, memory QQ215including random access memory (RAM) QQ217, read-only memory (ROM) QQ219, and storage medium QQ221or the like, communication subsystem QQ231, power source QQ233, and/or any other component, or any combination thereof. Storage medium QQ221includes operating system QQ223, application program QQ225, and data QQ227. In other embodiments, storage medium QQ221may include other similar types of information. Certain UEs may utilize all of the components shown inFIG. 9, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

RAM QQ217may be configured to interface via bus QQ202to processing circuitry QQ201to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM QQ219may be configured to provide computer instructions or data to processing circuitry QQ201. For example, ROM QQ219may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory. Storage medium QQ221may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium QQ221may be configured to include operating system QQ223, application program QQ225such as a web browser application, a widget or gadget engine or another application, and data file QQ227. Storage medium QQ221may store, for use by UE QQ200, any of a variety of various operating systems or combinations of operating systems.

InFIG. 9, processing circuitry QQ201may be configured to communicate with network QQ243busing communication subsystem QQ231. Network QQ243aand network QQ243bmay be the same network or networks or different network or networks. Communication subsystem QQ231may be configured to include one or more transceivers used to communicate with network QQ243b. For example, communication subsystem QQ231may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.QQ2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter QQ233and/or receiver QQ235to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter QQ233and receiver QQ235of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

The features, benefits and/or functions described herein may be implemented in one of the components of UE QQ200or partitioned across multiple components of UE QQ200. Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem QQ231may be configured to include any of the components described herein. Further, processing circuitry QQ201may be configured to communicate with any of such components over bus QQ202. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry QQ201perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry QQ201and communication subsystem QQ231. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.

FIG. 10illustrates a virtualization environment in accordance with some embodiments.

In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments QQ300hosted by one or more of hardware nodes QQ330. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.

The functions may be implemented by one or more applications QQ320(which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Applications QQ320are run in virtualization environment QQ300which provides hardware QQ330comprising processing circuitry QQ360and memory QQ390. Memory QQ390contains instructions QQ395executable by processing circuitry QQ360whereby application QQ320is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

Virtualization environment QQ300, comprises general-purpose or special-purpose network hardware devices QQ330comprising a set of one or more processors or processing circuitry QQ360, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory QQ390-1which may be non-persistent memory for temporarily storing instructions QQ395or software executed by processing circuitry QQ360. Each hardware device may comprise one or more network interface controllers (NICs) QQ370, also known as network interface cards, which include physical network interface QQ380. Each hardware device may also include non-transitory, persistent, machine-readable storage media QQ390-2having stored therein software QQ395and/or instructions executable by processing circuitry QQ360. Software QQ395may include any type of software including software for instantiating one or more virtualization layers QQ350(also referred to as hypervisors), software to execute virtual machines QQ340as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

Virtual machines QQ340, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ350or hypervisor. Different embodiments of the instance of virtual appliance QQ320may be implemented on one or more of virtual machines QQ340, and the implementations may be made in different ways.

During operation, processing circuitry QQ360executes software QQ395to instantiate the hypervisor or virtualization layer QQ350, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer QQ350may present a virtual operating platform that appears like networking hardware to virtual machine QQ340.

As shown inFIG. 10, hardware QQ330may be a standalone network node with generic or specific components. Hardware QQ330may comprise antenna QQ3225and may implement some functions via virtualization. Alternatively, hardware QQ330may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) QQ3100, which, among others, oversees lifecycle management of applications QQ320.

In the context of NFV, virtual machine QQ340may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of virtual machines QQ340, and that part of hardware QQ330that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines QQ340, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines QQ340on top of hardware networking infrastructure QQ330and corresponds to application QQ320inFIG. 10.

In some embodiments, one or more radio units QQ3200that each include one or more transmitters QQ3220and one or more receivers QQ3210may be coupled to one or more antennas QQ3225. Radio units QQ3200may communicate directly with hardware nodes QQ330via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.

In some embodiments, some signalling can be effected with the use of control system QQ3230which may alternatively be used for communication between the hardware nodes QQ330and radio units QQ3200.

With reference toFIG. 11, in accordance with an embodiment, a communication system includes telecommunication network QQ410, such as a 3GPP-type cellular network, which comprises access network QQ411, such as a radio access network, and core network QQ414. Access network QQ411comprises a plurality of base stations QQ412a, QQ412b, QQ412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area QQ413a, QQ413b, QQ413c. Each base station QQ412a, QQ412b, QQ412cis connectable to core network QQ414over a wired or wireless connection QQ415. A first UE QQ491located in coverage area QQ413cis configured to wirelessly connect to, or be paged by, the corresponding base station QQ412c. A second UE QQ492in coverage area QQ413ais wirelessly connectable to the corresponding base station QQ412a. While a plurality of UEs QQ491, QQ492are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station QQ412.

Telecommunication network QQ410is itself connected to host computer QQ430, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. Host computer QQ430may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. Connections QQ421and QQ422between telecommunication network QQ410and host computer QQ430may extend directly from core network QQ414to host computer QQ430or may go via an optional intermediate network QQ420. Intermediate network QQ420may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network QQ420, if any, may be a backbone network or the Internet; in particular, intermediate network QQ420may comprise two or more sub-networks (not shown).

The communication system ofFIG. 11as a whole enables connectivity between the connected UEs QQ491, QQ492and host computer QQ430. The connectivity may be described as an over-the-top (OTT) connection QQ450. Host computer QQ430and the connected UEs QQ491, QQ492are configured to communicate data and/or signaling via OTT connection QQ450, using access network QQ411, core network QQ414, any intermediate network QQ420and possible further infrastructure (not shown) as intermediaries. OTT connection QQ450may be transparent in the sense that the participating communication devices through which OTT connection QQ450passes are unaware of routing of uplink and downlink communications. For example, base station QQ412may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer QQ430to be forwarded (e.g., handed over) to a connected UE QQ491. Similarly, base station QQ412need not be aware of the future routing of an outgoing uplink communication originating from the UE QQ491towards the host computer QQ430.

Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference toFIG. 12. In communication system QQ500, host computer QQ510comprises hardware QQ515including communication interface QQ516configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system QQ500. Host computer QQ510further comprises processing circuitry QQ518, which may have storage and/or processing capabilities. In particular, processing circuitry QQ518may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer QQ510further comprises software QQ511, which is stored in or accessible by host computer QQ510and executable by processing circuitry QQ518. Software QQ511includes host application QQ512. Host application QQ512may be operable to provide a service to a remote user, such as UE QQ530connecting via OTT connection QQ550terminating at UE QQ530and host computer QQ510. In providing the service to the remote user, host application QQ512may provide user data which is transmitted using OTT connection QQ550.

Communication system QQ500further includes base station QQ520provided in a telecommunication system and comprising hardware QQ525enabling it to communicate with host computer QQ510and with UE QQ530. Hardware QQ525may include communication interface QQ526for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system QQ500, as well as radio interface QQ527for setting up and maintaining at least wireless connection QQ570with UE QQ530located in a coverage area (not shown inFIG. 12) served by base station QQ520. Communication interface QQ526may be configured to facilitate connection QQ560to host computer QQ510. Connection QQ560may be direct or it may pass through a core network (not shown inFIG. 12) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware QQ525of base station QQ520further includes processing circuitry QQ528, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Base station QQ520further has software QQ521stored internally or accessible via an external connection.

Communication system QQ500further includes UE QQ530already referred to. Its hardware QQ535may include radio interface QQ537configured to set up and maintain wireless connection QQ570with a base station serving a coverage area in which UE QQ530is currently located. Hardware QQ535of UE QQ530further includes processing circuitry QQ538, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE QQ530further comprises software QQ531, which is stored in or accessible by UE QQ530and executable by processing circuitry QQ538. Software QQ531includes client application QQ532. Client application QQ532may be operable to provide a service to a human or non-human user via UE QQ530, with the support of host computer QQ510. In host computer QQ510, an executing host application QQ512may communicate with the executing client application QQ532via OTT connection QQ550terminating at UE QQ530and host computer QQ510. In providing the service to the user, client application QQ532may receive request data from host application QQ512and provide user data in response to the request data. OTT connection QQ550may transfer both the request data and the user data. Client application QQ532may interact with the user to generate the user data that it provides.

It is noted that host computer QQ510, base station QQ520and UE QQ530illustrated inFIG. 12may be similar or identical to host computer QQ430, one of base stations QQ412a, QQ412b, QQ412cand one of UEs QQ491, QQ492ofFIG. 11, respectively. This is to say, the inner workings of these entities may be as shown inFIG. 12and independently, the surrounding network topology may be that ofFIG. 11.

InFIG. 12, OTT connection QQ550has been drawn abstractly to illustrate the communication between host computer QQ510and UE QQ530via base station QQ520, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from UE QQ530or from the service provider operating host computer QQ510, or both. While OTT connection QQ550is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

Wireless connection QQ570between UE QQ530and base station QQ520is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments may improve the performance of OTT services provided to UE QQ530using OTT connection QQ550, in which wireless connection QQ570forms the last segment. More precisely, the teachings of these embodiments may improve the random access speed and/or reduce random access failure rates and thereby provide benefits such as faster and/or more reliable random access.

A measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring OTT connection QQ550between host computer QQ510and UE QQ530, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection QQ550may be implemented in software QQ511and hardware QQ515of host computer QQ510or in software QQ531and hardware QQ535of UE QQ530, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection QQ550passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software QQ511, QQ531may compute or estimate the monitored quantities. The reconfiguring of OTT connection QQ550may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station QQ520, and it may be unknown or imperceptible to base station QQ520. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer QQ510's measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software QQ511and QQ531causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection QQ550while it monitors propagation times, errors etc.

FIG. 13is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference toFIGS. 11 and 12. For simplicity of the present disclosure, only drawing references toFIG. 13will be included in this section. In step QQ610, the host computer provides user data. In substep QQ611(which may be optional) of step QQ610, the host computer provides the user data by executing a host application. In step QQ620, the host computer initiates a transmission carrying the user data to the UE. In step QQ630(which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ640(which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

FIG. 15is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference toFIGS. 11 and 12. For simplicity of the present disclosure, only drawing references toFIG. 15will be included in this section. In step QQ810(which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step QQ820, the UE provides user data. In substep QQ821(which may be optional) of step QQ820, the UE provides the user data by executing a client application. In substep QQ811(which may be optional) of step QQ810, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep QQ830(which may be optional), transmission of the user data to the host computer. In step QQ840of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

Abbreviations

At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s).1×RTT CDMA2000 1× Radio Transmission Technology3GPP 3rd Generation Partnership Project5G 5th GenerationABS Almost Blank SubframeARQ Automatic Repeat RequestAWGN Additive White Gaussian NoiseBCCH Broadcast Control ChannelBCH Broadcast ChannelCA Carrier AggregationCC Carrier ComponentCCCH SDU Common Control Channel SDUCDMA Code Division Multiplexing AccessCGI Cell Global IdentifierCIR Channel Impulse ResponseCP Cyclic PrefixCPICH Common Pilot ChannelCPICH Ec/No CPICH Received energy per chip divided by the power density in the bandCQI Channel Quality informationC-RNTI Cell RNTICSI Channel State InformationDCCH Dedicated Control ChannelDL DownlinkDM DemodulationDMRS Demodulation Reference SignalDRX Discontinuous ReceptionDTX Discontinuous TransmissionDTCH Dedicated Traffic ChannelDUT Device Under TestE-CID Enhanced Cell-ID (positioning method)E-SMLC Evolved-Serving Mobile Location CentreECGI Evolved CGIeNB E-UTRAN NodeBePDCCH enhanced Physical Downlink Control ChannelE-SMLC evolved Serving Mobile Location CenterE-UTRA Evolved UTRAE-UTRAN Evolved UTRANFDD Frequency Division DuplexFFS For Further StudyGERAN GSM EDGE Radio Access NetworkgNB Base station in NRGNSS Global Navigation Satellite SystemGSM Global System for Mobile communicationHARQ Hybrid Automatic Repeat RequestHO HandoverHSPA High Speed Packet AccessHRPD High Rate Packet DataLOS Line of SightLPP LTE Positioning ProtocolLTE Long-Term EvolutionMAC Medium Access ControlMBMS Multimedia Broadcast Multicast ServicesMBSFN Multimedia Broadcast multicast service Single Frequency NetworkMBSFN ABS MBSFN Almost Blank SubframeMDT Minimization of Drive TestsMIB Master Information BlockMME Mobility Management EntityMSC Mobile Switching CenterNPDCCH Narrowband Physical Downlink Control ChannelNR New RadioOCNG OFDMA Channel Noise GeneratorOFDM Orthogonal Frequency Division MultiplexingOFDMA Orthogonal Frequency Division Multiple AccessOSS Operations Support SystemOTDOA Observed Time Difference of ArrivalO&M Operation and MaintenancePBCH Physical Broadcast ChannelP-CCPCH Primary Common Control Physical ChannelPCell Primary CellPCFICH Physical Control Format Indicator ChannelPDCCH Physical Downlink Control ChannelPDP Profile Delay ProfilePDSCH Physical Downlink Shared ChannelPGW Packet GatewayPHICH Physical Hybrid-ARQ Indicator ChannelPLMN Public Land Mobile NetworkPMI Precoder Matrix IndicatorPRACH Physical Random Access ChannelPRS Positioning Reference SignalPSS Primary Synchronization SignalPUCCH Physical Uplink Control ChannelPUSCH Physical Uplink Shared ChannelRACH Random Access ChannelQAM Quadrature Amplitude ModulationRAN Radio Access NetworkRAT Radio Access TechnologyRLM Radio Link ManagementRNC Radio Network ControllerRNTI Radio Network Temporary IdentifierRRC Radio Resource ControlRRM Radio Resource ManagementRS Reference SignalRSCP Received Signal Code PowerRSRP Reference Symbol Received Power OR Reference Signal Received PowerRSRQ Reference Signal Received Quality OR Reference Symbol Received QualityRSSI Received Signal Strength IndicatorRSTD Reference Signal Time DifferenceSCH Synchronization ChannelSCell Secondary CellSDU Service Data UnitSFN System Frame NumberSGW Serving GatewaySI System InformationSIB System Information BlockSNR Signal to Noise RatioSON Self Optimized NetworkSS Synchronization SignalSSS Secondary Synchronization SignalTDD Time Division DuplexTDOA Time Difference of ArrivalTOA Time of ArrivalTSS Tertiary Synchronization SignalTTI Transmission Time IntervalUE User EquipmentUL UplinkUMTS Universal Mobile Telecommunication SystemUSIM Universal Subscriber Identity ModuleUTDOA Uplink Time Difference of ArrivalUTRA Universal Terrestrial Radio AccessUTRAN Universal Terrestrial Radio Access NetworkWCDMA Wide CDMAWLAN Wide Local Area Network

Further definitions and embodiments are discussed below.