TECHNICAL FIELD

The present invention relates generally to wireless communication networks, and in particular to a system and method of simultaneously adjusting the active time of multiple User Equipment (UE) in Discontinuous Reception (DRX).

BACKGROUND

The cellular configuration is a popular architecture for modern wireless communication networks. A plurality of fixed network nodes, referred to herein as base stations (e.g. , NodeB, eNB, gNB), each provides wireless communication services to a large number of fixed and mobile wireless devices (also known as User Equipment or UE), over a geographical area known as a cell (note, the term cell is also used in Carrier Aggregation to refer to different carriers). The base stations communicate with other network nodes the core network (e.g., Evolved Packet Core or EPC), which handle various network functions such as mobility management, authentication, billing, location services, and the like. The Third Generation Partnership Project (3GPP) is an industry consortium that develops and promulgates technical standards, identified by numbered releases (e.g., Rel-15, Rel-16), that define successive generations (3G, 4G, 5G) of cellular wireless network structure and operation.

Data intended for transmission to a UE, such as a phone call, email message, or the like, may arrive at a base station at any time. The base station “pages” a UE by transmitting the UE’s network ID (e.g., Cell Radio Network Temporary Identifier, or C-RNTI), along with technical details of the forthcoming downlink transmission. The Physical Downlink Control Channel (PDCCH) carries such paging messages, along with other overhead collectively known as Downlink Control Information (DCI), and it is transmitted by the base station periodically (e.g., at the beginning of every downlink subframe).

Without coordination, in order for a UE to ascertain that downlink data is available, and the time-frequency resources on which to receive it, a UE must constantly receive and monitor at least the PDCCH network transmissions. Maintaining a Radio Frequency (RF) receiver in active mode to receive, demodulate, decode, and monitor every PDCCH occasion would quickly deplete the UE’s battery.

Discontinuous Reception (DRX) is a power saving mechanism introduced in the 3GPP fourth generation (4G) protocol, known as Long Term Evolution (LTE). DRX allows UEs to be active to receive only certain specified PDCCH transmissions, and to otherwise remain inactive, with most circuits powered down (also known as “sleep” mode). There is a trade-off between UE responsiveness and battery life - numerous and/or longer-duration active periods will detect a page more quickly, but consume more power, while fewer and/or shorter-duration active periods introduce greater latency, but the UE consumes less power. The network sets this trade-off for each UE via numerous DRX parameters, which are set (and reconfigured) via Radio Resource Control (RRC) signaling. Key connected-mode DRX (cDRX) parameters include cDRX cycle length (short and long), onDuration length, and InActivity Timer (IAT) value. cDRX cycle length refers to the number of subframes in a cDRX cycle. A cDRX cycle consist of an onDuration, during which the UE actively monitors PDCCH, and a DRX period, during which it may conserve battery power by skipping reception of PDCCH. When a scheduling message is received during an onDuration, the UE starts an IAT with a preconfigured value, and monitors PDCCH in every subsequent subframe until the IAT expires (during this time, the UE is in continuous reception mode). The IAT is restarted whenever a new transmission for the UE is received on PDCCH. Additional mechanisms are available for UE power savings in different phases of cDRX operation.

AWake Up Signal (WUS) for cDRX was specified in 3GPP Rel-16. The WUS is transmitted ahead of a PDCCH in the UE’s onDuration in which the network plans to schedule the UE. The WUS can be detected by use of a matched filter or correlation metric, which can be implemented in a limited, low-power receiver, and does not require the full demodulation and decoding that PDCCH reception does. If the UE does not detect a WUS, it may skip monitoring the following PDCCH transmission times, even though they are in the UE’s cDRX onDuration.

In 3GPP Rel-15, search space (SS) switching can be set to allow a UE to skip monitoring certain slots. This can be implemented using the Bandwidth Part (BWP) switching framework, where the UE can be switched between different BWPs with low latency and switching load. SS switching is implemented by configuring the different BWPs with different SSs. In 3GPP Rel-16, SS set group switching introduced additional implicit and explicit mechanisms for SS adaptation, based on data arrival patterns, using DCI signaling. UEs can be set to dense SS prior to data arrival, and switched to sparse SS after a period of no data arrival.

3GPP Rel-15 includes a Medium Access Control (MAC) Control Element (CE) mechanism for terminating the active time for a given UE, and returning it to sleep until the next cDRX onDuration.

All of these cDRX parameters, and other power savings control mechanisms, are specific to a particular UE, and most require RRC signaling to reconfigure. RRC is a higher- layer protocol that requires considerable air interface signaling (with concomitant delays and consumption of air interface resources) to make even simple changes.

Available 3GPP protocol features, such as those described above, provide multiple mechanisms for controlling PDCCH monitoring by individual UEs. If fully utilized, these mechanisms may allow for optimizing power consumption and performance trade-offs for individual UEs at a fairly detailed level. However, when numerous UEs are in cDRX active time simultaneously, the signaling load associated with individually controlling each UE may limit PDCCH capacity for data scheduling. Furthermore, the 3GPP 5G protocol, known as New Radio (NR), introduces new use cases and applications, such as multicasting/broadcasting, which utilize group common signaling to reduce the overhead, from the network perspective, of configuring UEs individually.

The Background section of this document is provided to place embodiments of the present invention in technological and operational context, to assist those of skill in the art in understanding their scope and utility. Approaches described in the Background section could be pursued, but are not necessarily approaches that have been previously conceived or pursued. Unless explicitly identified as such, no statement herein is admitted to be prior art merely by its inclusion in the Background section.

SUMMARY

The following presents a simplified summary of the disclosure in order to provide a basic understanding to those of skill in the art. This summary is not an extensive overview of the disclosure and is not intended to identify key/critical elements of embodiments of the invention or to delineate the scope of the invention. The sole purpose of this summary is to present some concepts disclosed herein in a simplified form as a prelude to the more detailed description that is presented later.

Embodiments described herein present a mechanism for active time modification (ATM) for multiple UEs currently monitoring PDCCH, e.g., UEs with the same or overlapping onDuration configurations, or with overlapping ongoing lATs. This is implemented by any of a variety of signaling options described herein, collectively referred to as ATM signaling.

In some embodiments, the network extends the onDuration length of a plurality of UEs in a cell that are currently monitoring some PDCCH configured by the network. For example, the network may have configured a short onDuration length (e.g., 2-4 ms) for UE power savings, but needs to extend the available time to provide scheduling opportunities due to a larger number of UEs having downlink data pending. Invocation of short DRX and using WUS for ATM signaling are utilized in other embodiments.

In some embodiments, the network directs the UEs to perform ATM on specific carriers when Carrier Aggregation (CA) is configured. That is, the ATM might be applicable to a Primary Cell (PCell), and/or one or more Secondary Cells (SCell), and/or a group of SCells belonging to a default or secondary DRX. In this manner, in a highly loaded cell, the network extends UE active time on carrier(s) on which there is a higher probability to schedule the UEs (e.g., a carrier on which fewer UEs reside).

In some embodiments, the network terminates active time for UEs currently monitoring PDCCH, either due to onDuration or IAT. This situation may arise, for example, if the network has configured a long onDuration length (e.g., 8-10 ms) to ensure sufficient scheduling opportunities, but no UEs in the current onDuration have data pending. In some embodiments, short DRX is terminated for a group of UEs, whereby the group of UEs is switched from short DRX to long DRX simultaneously.

The ATM signal may specify the duration of active time extension, or the delay until active time termination. Such duration may either be preconfigured or indicated in the ATM signal itself. In some embodiments, the ATM signaling is transmitted using a non-scheduling DCI using a new RNTI. In other embodiments, it is transmitted as a group MAC CE, or incorporated in a WUS.

In some embodiments, the ATM signaling is directed to a subset of UEs in active time. For example, only UEs with a certain capability, such as multicast/broadcast (MC/BC), enhanced Mobile BroadBand (eMBB), or Reduced Capability (Redcap) may be signaled. In other embodiments, the AT signaling is directed to UEs having other predetermined grouping (e.g., similar to WUS grouping).

In some embodiments, the network extends the onDuration length of UEs in a cell that are currently in connected mode, but not necessarily currently monitoring PDCCH or having overlapping onDurations. For example, during high load scenarios, the network may extend the active time for all (or a group of) UEs that are monitoring the same DCI instance and/or PDCCH time occasions in a common search space (CSS). In one embodiment, mechanisms similar to paging are used, as paging DCI is periodically decoded in connected mode (i.e., once per defaultPagingCycle). New periodical or periodical signals for this purpose may also be introduced.

One embodiment relates to a method, performed by a wireless device operative in a wireless communication network and participating in a connected mode Discontinuous Reception (cDRX), of dynamically altering an active time. A common Active Time Modification (ATM) indication that is sent to a plurality of wireless devices is received from the network. A previously determined active time is altered in response to the ATM indication.

Another embodiment relates to a wireless device operative in a wireless communication network and participating in a connected mode Discontinuous Reception (cDRX). The wireless device includes communication circuitry configured for wireless communication and processing circuitry operatively connected to the communication circuitry. The processing circuitry is configured to receive, from the network, a common Active Time Modification (ATM) indication that is sent to a plurality of wireless devices; and alter a previously determined active time in response to the ATM indication.

Yet another embodiment relates to a method, performed by a base station operative in a wireless communication network, of dynamically altering an active time of a plurality of wireless devices via common signaling. A common Active Time Modification (ATM) indication, configured to alter a previously determined active time of a plurality of wireless devices, is prepared. The ATM indication is sent to a plurality of wireless devices.

Still another embodiment relates to a base station operative in a wireless communication network. The base station includes communication circuitry configured for wireless communication and processing circuitry operatively connected to the communication circuitry. The processing circuitry is configured to prepare a common Active Time Modification (ATM) indication configured to alter a previously determined active time of a plurality of wireless devices; and send the ATM indication to a plurality of wireless devices.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will now be described more fully hereinafter with reference to the accompanying drawings, in which embodiments of the invention are shown. However, this invention should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Like numbers refer to like elements throughout.

Figure 1 is a diagram of a showing network activity and UE power consumption during various ATM scenarios.

Figure 2 is a flow diagram of a method of dynamically altering an active time by a wireless device operative in a wireless communication network and participating in a connected mode Discontinuous Reception (cDRX).

Figure 3 is a flow diagram of a method of dynamically altering an active time of two or more wireless devices via common signaling by a base station operative in a wireless communication network.

Figure 4 is a hardware block diagram of a wireless device.

Figure 5 is a functional block diagram of a wireless device.

Figure 6 is a hardware block diagram of a base station.

Figure 7 is a functional block diagram of a base station.

Figure 8 is a block diagram of a wireless communication network.

Figure 9 is a block diagram of a UE.

Figure 10 is a schematic block diagram illustrating a virtualization environment.

Figure 10 illustrates host computer communicating via a base station with a user equipment over a partially wireless connection.

Figure 11 illustrates a telecommunication network connected via an intermediate network to a host computer

Figure 12 illustrates a host computer communicating via a base station with a user equipment over a partially wireless connection.

Figure 13 is a flowchart illustrating a method implemented in a communication system.

Figure 14 is a flowchart illustrating another method implemented in a communication system.

Figure 15 is a flowchart illustrating yet another method implemented in a communication system. Figure 16 is a flowchart illustrating still another method implemented in a communication system.

DETAILED DESCRIPTION

For simplicity and illustrative purposes, the present invention is described by referring mainly to an exemplary embodiment thereof. In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. However, it will be readily apparent to one of ordinary skill in the art that the present invention may be practiced without limitation to these specific details. In this description, well known methods and structures have not been described in detail so as not to unnecessarily obscure the present invention.

Embodiments described herein present mechanisms for ATM for multiple UEs currently monitoring PDCCH, e.g., UEs with the same or overlapping onDuration configurations, or with overlapping ongoing lATs. Embodiments further present ATM mechanisms for UEs currently in connected mode but not necessarily currently monitoring PDCCH associated with connected mode DRX (cDRX). For example, UEs monitoring PDCCH activity for the sake of paging monitoring or the like (referred to herein as non-cDRX related PDCCH monitoring).

In general, the network determines a necessity for network operation improvements (e.g., creating additional scheduling opportunities) or opportunities for additional UE power savings (e.g., avoiding unnecessary PDCCH monitoring in the absence of data). It also determines that all UEs in a cell, or groups of UEs, must contribute to or can benefit from such necessity or opportunity. Upon such determination, the network sends a common indication to a plurality of UEs (up to all UEs in the cell) to modify their active times, e.g., change settings related to drx- In Activity Timer or onDuration settings. In the case of Carrier Aggregation, the active time modification may apply to the PCell only, or may include extension of scheduling opportunities on other component carrier(s) as well. As used herein, the term “network” refers individually and collectively to wireless communication network nodes, whether in the Radio Access Network (e.g., eNB, gNB), or the core network.

Extension of active time (onDuration or IAT): ATM-e

In one embodiment, the network may extend the onDuration length (i.e., active time or AT) of a plurality of UEs in the cell that are currently monitoring the PDCCH (i.e., whether cDRX or non-cDRX related PDCCH monitoring) by transmitting an ATM indication.

In one embodiment, the ATM indication adds a predetermined or embedded duration to a currently remaining AT duration for all UEs (e.g., their remaining onDuration duration or remaining IAT length). The additional length can be chosen from discrete values (or abstract values or discrete abstract values; see Abstract Syntax Notation One, ASN.1), or based on a fraction or multiple of onDuration or IAT.

In one embodiment, the ATM indication specifies a predetermined or embedded time duration as the remaining AT duration for a plurality of UEs, replacing the remaining onDuration duration or remaining IAT length.

In one embodiment, the ATM indication specifies a predetermined or embedded carrier on which the extension applies. For example, the network may extend the active time on one or more SCells but not the PCell.

One example of the advantageous use of this feature is if the network has configured a short onDuration length (e.g., 2-4 ms) to save UE energy, and a larger number of UEs have data pending than can be scheduled during that window on a particular carrier. At any time during the onDuration, if the network determines that additional scheduling time is required, it may indicate this by transmitting the ATM indication. Similarly, if download data for one or more UEs is arriving in a download buffer but it cannot be immediately served before the relevant lATs expire (e.g., due to other high-priority transfers ongoing, PDCCH blocking, PDSCH resource limitations, PUSCH and PUCCH resource limitations, or the like), the network may extend the AT segments for UEs with currently unexpired lATs.

In one embodiment, the network does not change the active time duration, but rather changes the cDRX mode for all UEs addressed by the ATM signal. In one embodiment, all these UEs are switched to short DRX, optionally including a temporary reconfiguration for this occurrence. Furthermore, the network may indicate to these UEs that the DRX mode switch is only applicable to a specified DRX group. For example, the network may command these UEs to extend the active time on the default DRX group, but not a secondary DRX group (e.g., with FR2 cells). This enables effectively extending the monitoring phase, while reducing the power savings impact. In another embodiment, all (or a group of) UEs are switched to a sparse SS, e.g., in a SS in the CSS set.

In another embodiment, the network indicates to the UEs to perform such extensions on specific carriers when CA is configured. That is, the active time extension may apply to PCell, and/or SCell(s), and/or a group of SCells belong to a default or secondary DRX. As such, in a highly loaded cell, the network can extend activity on carrier(s) on which there is a higher probability to schedule the UEs (e.g., a carrier on which fewer UEs reside).

In one embodiment, the ATM applies only to the current cell or cell group (CG) and not other ones. In another embodiment, the ATM indicates to a plurality of UEs to extend the active times in the current cell and other cells, and nevertheless change the SS configuration of the UEs in one or more other cells to a sparser one with respect to the default mode, or one or more of the other cells go to the dormancy state (e.g., dormant SCell, BWP, etc.). That is, these UEs do not monitor PDCCH but may or may not perform the configured activities, such as periodic measurements and reports (e.g., CSI report), depending on their pre-configuration.

In another embodiment, the network transmits an ATM indication if the PDCCH blocking probability grows above a specific threshold. For example, based on the current download buffer (as indicated by a buffer status report, or BSR), the remaining UEs’ active times, and available PDCCH resources, the network may conclude that the PDCCH blocking probability is above an acceptable level, and thus indicate ATM for some or all UEs in the cell.

In one embodiment, if Rel-16 WUS is configured, the indication to extend the onDuration may be included in the WUS before the beginning of an active time. The indication may apply to the imminent onDuration, or alternatively to multiple onDurations. The following onDurations (after expiration of the ATM) then resume their previous cDRX configuration.

In one embodiment, the network may extend the onDuration length of UEs in the cell that are currently in connected mode, but not necessarily currently monitoring PDCCH or having overlapping onDurations. For example, during high load scenarios, the network may wish to extend the active time for all UEs, or a group of UEs, that are decoding the same DCI instance in CSS. In one embodiment, an ATM indication is added to a DCI in common search space (CSS) that the UEs in any event decode during connected mode, such as the paging DCI (i.e., P-RNTI encoded DCI periodically decoded in connected mode once per defaultPagingCycle).

Or a new signal format or DCI in CSS can be defined for this purpose, optionally with a new type of RNTI or other identifiers. Instead of CSS, other commonly monitored time/frequency occasions can also be considered. Reduction or Termination of active time: ATM-t

In one embodiment, the network may terminate active times for a plurality of UEs currently monitoring PDCCH, either awaiting data in an onDuration or due to an unexpired IAT.

In one embodiment, the ATM indication terminates a currently ongoing AT phase for a plurality of UEs (e.g., their remaining onDuration segments or remaining IAT segments). In another embodiment, the ATM indication includes a delay value before AT is ended.

One example of the advantageous use of this feature is if the network has configured a long onDuration length (e.g., 8-10 ms) to ensure sufficient scheduling opportunities, but no UEs in the current onDuration have data pending to be scheduled during the window, or if multiple UEs have ongoing IAT segments but have no more data to be served in the buffers and the probability of new data arrival during the IAT is estimated as low.

In one embodiment, if a plurality of UEs are in short DRX, ATM signaling may indicate to the UEs to switch to long DRX. Alternatively, the network may shorten the short DRX cycle timer, so the UEs goes into long DRX.

Similar to ATM-e, the ATM-t signaling may address a subset of the SCells in the case of carrier aggregation.

ATM-e and ATM-t in Operation

The operations of both ATM-e and ATM-t actions are demonstrated, for a representative UE, in the timing diagrams of Figure 1 . The upper timeline indicates network monitoring or data reception activity by the UE, and the lower timeline indicates the concomitant UE power consumption.

Case A (at the left of the diagram) demonstrates normal c-DRX operation. During its onDuration, the UE monitors at least PDCCH for its C-RNTI, as indicated by the upper timeline, and consumes a moderate amount of power in doing so, as indicated by the lower timeline. Following the termination of its onDuration, the UE receiver goes into sleep mode, as indicated by the cross-hatched area, in which it consumes minimal power.

Case B (second from left) demonstrates ATM extension (ATM-e) according to embodiments described herein. As per normal c-DRX, the UE monitors at least PDCCH during its onDuration, consuming a moderate amount of power doing so. Due to, e.g., a high traffic load in the cell, the network indicates to the UE to extend its AT by a specified duration. The ATM indication may be transmitted, in one embodiment, in one of the PDCCH transmissions during the UE onDuration. In response to the ATM-e indication, the UE extends its active time beyond its specified onDuration, as indicated in the upper timeline by the diagonally hatched area. As indicated by the lower timeline, the UE power consumption continues at the PDCCH monitoring level throughout the extended AT, after which the UE enters sleep mode.

Case C (second from right) demonstrates normal c-DRX operation when the UE receives download data. One PDCCH, received during the UE’s onDuration, pages the UE and schedules the downlink transmission. At the scheduled time, the UE receives the data, as indicated in the upper timeline by the shaded area. The data reception increases the UE power consumption, as indicated by the shaded area in the lower timeline. The data reception starts the UE’s IAT, and the UE monitors at least PDCCH until the IAT expires, consuming the PDCCH monitoring level of power for the IAT duration.

Case D (at the right of the diagram) demonstrates ATM termination (ATM-t) according to embodiments described herein. As per normal data reception during c-DRX, the UE initially monitors at least PDCCH during its onDuration, consuming a moderate amount of power doing so. Upon detecting a page in a PDCCH monitored during its onDuration, the UE receives downlink data, increasing its power consumption while doing so, as indicated by the shaded area in the lower timeline. Following the data reception, the UE starts its IAT, and monitors at least PDCCH continuously, consuming a moderate amount of power. If the network is aware that no further downlink data is scheduled for the UE, or is likely to arrive soon, it transmits to the UE an lAT-e indication prior to the expiration of the UE’s IAT. This terminates the UE PDCCH monitoring for the remaining IAT duration, as indicated by the diagonally hatched area. This allows the UE to enter sleep mode earlier, saving the power associated with PDCCH monitoring throughout the remainder of its erstwhile IAT duration, as indicated by the cross hatched area in the lower timeline.

Although Figure 1 demonstrates the effects of ATM-e and ATM-t signaling for one UE, those of skill in the art will readily understand that the UE depicted is a representative UE in a plurality of UEs to which the ATM-e and/or ATM-t signaling is directed. The plurality may be defined according to any known method of identifying groups of UEs, or it may include all of the UEs in a cell. As described herein, the ATM may apply only to specified cells in the case of CA.

ATM Signaling Design

In one embodiment, the ATM signaling is transmitted using a non-scheduling DCI and using a non-UE-specific RNTI or a group common RNTI. In one embodiment, the new DCI is similar to DCI format (2_6). In one embodiment, an RNTI approach similar to the Rel-16 group- WUS is used, with specified bits indicating that the message is an ATM and whether it is an ATM-e or ATM-t. The underlying DCI can be further associated with a PS-RNTI, as in the case of DCI format 2-6 (or Rel-16 WUS), or a new group common RNTI specifically designed for ATM, referred to herein as ATM-RNTI.

In one embodiment, the underlying DCI payload may be 0-bit and upon the reception of ATM DCI associated with the ATM-RNTI, the UE applies a pre-configured setting of ATM, e.g., the additional extension time, cell applicability, dormancy behavior, and the like. In another embodiment, when ATM-t is applied, reception of the PDCCH associated with ATM-RNTI with 0- bit indicates to the UEs that they should terminate their active times, or apply a procedure as configured by the network, e.g., switch to short or long DRX. The ATM-RNTI can be configured through higher layer signaling, e.g., RRC signaling for the UEs.

In one embodiment, the underlying DCI payload further includes indicator bits associated with different operations. For example, in one embodiment a bitfield is associated with each UE in the addressed group; if the bit associated with UE n is set to 1 , it indicates that UE n should apply preconfigured ATM operations. Alternatively, the desired ATM operations (e.g., extension time, switch to a different SS group, switch to short/long DRX, etc.) are indicated in the same DCI. In this case, an additional bitfield, either exactly following the UE ATM bit indicator, or in a different place in the payload, includes the additional ATM commands. In one embodiment, the additional commands bitfield is only activated for a particular UE if the indicator bit is toggled Ί” for ATM-e, or alternatively, only if it is toggled “0” for ATM-t, or in either case it is activated. The number of bits within the DCI payload, the location of the UE bit indicator, as well as the other associated bits, is configured by the network through higher layer signaling, such as RRC signaling. For example, the DCI payload may be configured to have K bits in total, of which N bits are associated with each UE within the same group associated with the ATM-RNTI, and K-N bits are either reserved or considered for potentially additional commands as described herein.

In another embodiment, an additional bitfield is defined in the current scheduling or nonscheduling DCIs, indicating ATM. The corresponding PDCCH candidate is configured, for example, with association of a CSS and a common Coreset for the UEs, such that all the plurality of UEs can be addressed with the same PDCCH. The PDCCH can be associated again with ATM-RNTI such that the UEs can distinguish the ATM PDCCH from the current ones associated with other types of RNTI, e.g., Cell RNTI (C-RNTI), Configured Scheduling RNTI (CS-RNTI), Modulation Coding Scheme RNTI (MCS-RNTI), etc. In this case, in one embodiment, reserved bits of fallback DCIs such as DCI formats 1-0 or 0-0 are used to indicate ATM. In another embodiment, an additional bitfield is included in the other DCI formats which is associated with a CSS.

In one embodiment, ATM signaling is transmitted a using a MAC CE approach, where the PDCCH is scrambled with a non-UE-specific RNTI. Bits in the MAC-CE payload may specify whether the message is an ATM, and whether it is an ATM-e or ATM-t.

In one embodiment, the ATM signal contains the duration of AT extension, or delay until AT termination, in units of symbols, slots, or ms. In another embodiment, the ATM signal includes an index to a table of such values configured by the network, or provided in a specification document. Furthermore, in some embodiments, as discussed above, the ATM signal also contains information about whether the ATM command is applicable to: SCells only, specific SCells, SCells and PCell, SCells of default or secondary DRX group(s) (or both), and/or cells belonging to specific frequency ranges (e.g., FR1 , FR2, or both). Other types of additional commands can also be included in the ATM signaling, as described throughput this disclosure, within the broad scope of the embodiments described herein.

In one embodiment, in which ATM signaling is implemented via group common MAC CE, the UEs associated to the same group to be addressed by the common MAC CE are configured with a specific group common PDCCH indicating a group MAC CE. The underlying PDCCH is based on the current scheduling PDCCHs, associated with a group common MAC CE RNTI, e.g., a gMAC-RNTI. In one embodiment, the underlying DCI payload includes the time/frequency resource allocation to the location of the group common MAC CE PDSCH, where the details of the MAC CE are located. In one embodiment, the DCI is designed similarly to a paging DCI or system information (SI) update DCI, where the UE decodes the DCI and then reads the PDSCH message to see if it is paged or has to enquire about an updated SI. In this case, when the UE decodes the DCI associated with the gMAC-RNTI, it receives an indication of the location of the PDSCH, and ascertains whether or not the content is related to the UE.

Targeting a subset of active UEs

The ATM signaling may further include an indication that it is directed to a subset of UEs in active time. This avoids impacting a large number of connected UEs in high-load conditions. Grouping may be based on various factors, such as:

• UEs with a certain capability, such as multicast/broadcast (MC/BC), enhanced Mobile BroadBand (eMBB), Reduced capabilities (Redcap), Ultra-Reliable, Low-Latency Communications (URLLC), or the like.

• Related to predetermined grouping (e.g. similar to WUS grouping).

• UEs whose active time is to end within a predetermined or signaled time duration, or after a predetermined or signaled time duration.

• UEs currently running a specific service, such as voice, mission critical service, or the like.

The grouping indication may be conveyed via separate RNTIs or group bitmaps in the payload.

Preferably, if group RNTIs are used, the set of RNTIs includes one RNTI monitored by all UEs in the cell. Network Aspects

One way to accommodate ATM is by introducing a new DCI, which may imply an additional SS that needs to be monitored. In some cases, it might not be beneficial for the UE.

In one embodiment, the network configures the periodicity of the SS based on the number of UE currently served by the network. That is, with a larger number of UEs to be served by the network, the probability that the network needs to extend the active time might be larger (e.g., as the blocking probability or the network load may be higher). Therefore, if the number of the UEs is relatively large, the network configures the SS containing this DCI with a shorter period. Contrarily, if the number of UEs is relatively small, the network configures the SS containing this DCI with a longer period. In another embodiment, for the case that the ATM indication is set for a plurality of UEs less than all UEs in the cell, the periodicity of the SS is set depending on the number of UEs in the plurality.

In receiving the active time modification indication, the UE may require time to decode the indication itself, i.e., there is an application delay associated with the ATM signaling. The application delay can depend on the numerology of the BWP, the UE capability, and the inherit application delay of other features, such as cross-slot scheduling. The application delay may be specified as part of a 3GPP standard, or it can be left as a proprietary network implementation detail, but in either case it must be ensured that this delay does not cause misalignment of the network and the UE.

This application delay can cause a problem in particular for the ATM-e command, as the UE may enter sleep mode before it ascertains that it should remain active. To avoid this problem, in one embodiment the network avoids ATM to the UE if part of or all of the application delay duration falls in the UE’s configured sleep opportunity. In another embodiment, the network avoids this problem by not sending the ATM-e indication later than X slots before the UE’s active time ends, where X is ceiling function of the required application delay. In yet another embodiment, if an ATM-e indication is transmitted, the network does not schedule any data to the UE before the end of the application delay duration, but the UE is expected to rapidly awaken from a sleep mode it may have started to initiate during the X first slots. A UE capability may indicate such ability for a given UE.

UE aspects

In one embodiment, the UE is configured by the network with ATM as described in this disclosure, e.g., either by configuring a DCI based ATM and its variants, configuring a MAC CE based ATM and its variants, or configuring a WUS.

The UE receives the ATM indication and adjusts its active time accordingly, e.g., a longer onDuration or a terminated IAT on the specified carriers, or potentially additional commands as described in this disclosure. The UE then reassesses sleep opportunities and selects an appropriate sleep mode at the end of the current active time.

Methods and Apparatuses

Figure 2 depicts a method 100 of dynamically altering an active time, in accordance with particular embodiments. The method is performed by a wireless device operative in a wireless communication network and participating in a connected mode Discontinuous Reception (cDRX). A common ATM indication that is sent to a plurality of wireless devices is received from the network (block 102). A previously determined active time is altered in response to the ATM indication (block 104).

Figure 3 depicts a method 200 of dynamically altering an active time of a plurality of wireless devices via common signaling, in accordance with other particular embodiments. The method is performed by a base station operative in a wireless communication network. A common ATM indication, configured to alter a previously determined active time of a plurality of wireless devices, is prepared (block 202). The ATM indication is simultaneously sent to a plurality of wireless devices (block 204).

Apparatuses described herein may perform the methods 100, 200 herein and any other processing by implementing any functional means, modules, units, or circuitry. In one embodiment, for example, the apparatuses comprise respective circuits or circuitry configured to perform the steps shown in the method figures. The circuits or circuitry in this regard may comprise circuits dedicated to performing certain functional processing and/or one or more microprocessors in conjunction with memory. For instance, the circuitry may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory may include program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In embodiments that employ memory, the memory stores program code that, when executed by the one or more processors, carries out the techniques described herein.

Figure 4 for example illustrates a hardware block diagram of a wireless device, e.g., a UE, 10 as implemented in accordance with one or more embodiments. As shown, the UE 10 includes processing circuitry 12 and communication circuitry 16. The communication circuitry 16 (e.g., radio circuitry) is configured to transmit and/or receive information to and/or from one or more other nodes, e.g., via any communication technology. Such communication may occur via one or more antennas 18 that may be either internal or external to the UE 10, as indicated by the dashed lines in Figure 4. The processing circuitry 12 is configured to perform processing described above, such as by executing instructions stored in memory 14. The processing circuitry 12 in this regard may implement certain functional means, units, or modules.

Figure 5 illustrates a functional block diagram of a wireless device, e.g., a UE, 20 in a wireless network according to still other embodiments (for example, the wireless network shown in Figure 8). As shown, the UE 20 implements various functional means, units, or modules, e.g., via the processing circuitry 12 in Figure 4 and/or via software code. These functional means, units, or modules, e.g., for implementing the method 100 herein, include for instance: ATM indication receiving unit 22, and active time altering unit 24. ATM indication receiving unit 22 is configured to receive, from the network, a common ATM indication that is sent to a plurality of wireless devices. Activity time altering unit 24 is configured to alter a previously determined active time in response to the ATM indication.

Figure 6 illustrates a hardware block diagram of a network node 30, e.g., a base station, as implemented in accordance with one or more embodiments. As shown, the network node 30 includes processing circuitry 32 and communication circuitry 36. The communication circuitry 36 is configured to transmit and/or receive information to and/or from one or more other nodes, e.g., via any communication technology, via antenna(s) 38. As indicated by the broken line, antenna(s) 38 may be located remotely from the base station 30, such as on a tower or building. The processing circuitry 32 is configured to perform processing described above, such as by executing instructions stored in memory 34. The processing circuitry 32 in this regard may implement certain functional means, units, or modules. Those of skill in the art understand that virtualization technology may enable processing ostensibly performed by processing circuitry 32 to be performed remotely, such as in the so-called “cloud.”

Figure 7 illustrates a functional block diagram of a network node 40, e.g., a base station, in a wireless network according to still other embodiments (for example, the wireless network shown in Figure 8). As shown, the network node 40 implements various functional means, units, or modules, e.g., via the processing circuitry 32 in Figure 6 and/or via software code. These functional means, units, or modules, e.g., for implementing the method 200 herein, include for instance: ATM indication preparing unit 42 and ATM indication sending unit 44. ATM indication preparing unit 42 is configured to prepare a common ATM indication configured to alter a previously determined active time of a plurality of wireless devices. ATM indication sending unit 44 is configured to simultaneously send the ATM indication to a plurality of wireless devices.

Those skilled in the art will also appreciate that embodiments herein further include corresponding computer programs.

A computer program comprises instructions which, when executed on at least one processor of an apparatus, cause the apparatus to carry out any of the respective processing described above. A computer program in this regard may comprise one or more code modules corresponding to the means or units described above.

Embodiments further include a carrier containing such a computer program. This carrier may comprise one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

In this regard, embodiments herein also include a computer program product stored on a non-transitory computer readable (storage or recording) medium and comprising instructions that, when executed by a processor of an apparatus, cause the apparatus to perform as described above.

Embodiments further include a computer program product comprising program code portions for performing the steps of any of the embodiments herein when the computer program product is executed by a computing device. This computer program product may be stored on a computer readable recording medium.

Network Description and Over the Top (OTT) Implementations

Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in Figure 8. For simplicity, the wireless network of Figure 8 only depicts network 1106, network nodes 1160 and 1160b, and wireless devices (WD) 1110, 1110b, and 1110c. In practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node 1160 and WD 1110 are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and/or use of the services provided by, or via, the wireless network.

The wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system. In some embodiments, the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), Narrowband Internet of Things (NB-loT), and/or other suitable 2G, 3G,

4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.

Network 1106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

Network node 1160 and WD 1110 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.

As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Yet further examples of network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. As another example, a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.

In Figure 8, network node 1160 includes processing circuitry 1170, device readable medium 1180, interface 1190, auxiliary equipment 1184, power source 1186, power circuitry 1187, and antenna 1162. Although network node 1160 illustrated in the example wireless network of Figure 8 may 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 1160 are 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 1180 may comprise multiple separate hard drives as well as multiple RAM modules).

Similarly, network node 1160 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which network node 1160 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeB’s. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, network node 1160 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium 1180 for the different RATs) and some components may be reused (e.g., the same antenna 1162 may be shared by the RATs).

Network node 1160 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1160.

Processing circuitry 1170 is 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 1170 may include processing information obtained by processing circuitry 1170 by, 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 1170 may 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 1160 components, such as device readable medium 1180, network node 1160 functionality. For example, processing circuitry 1170 may execute instructions stored in device readable medium 1180 or in memory within processing circuitry 1170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 1170 may include a system on a chip (SOC).

In some embodiments, processing circuitry 1170 may include one or more of radio frequency (RF) transceiver circuitry 1172 and baseband processing circuitry 1174. In some embodiments, radio frequency (RF) transceiver circuitry 1172 and baseband processing circuitry 1174 may 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 1172 and baseband processing circuitry 1174 may 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 1170 executing instructions stored on device readable medium 1180 or memory within processing circuitry 1170. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 1170 without 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 1170 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 1170 alone or to other components of network node 1160, but are enjoyed by network node 1160 as a whole, and/or by end users and the wireless network generally.

Device readable medium 1180 may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, 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 1170. Device readable medium 1180 may store any suitable instructions, data or information, including 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 1170 and, utilized by network node 1160. Device readable medium 1180 may be used to store any calculations made by processing circuitry 1170 and/or any data received via interface 1190. In some embodiments, processing circuitry 1170 and device readable medium 1180 may be considered to be integrated.

Interface 1190 is used in the wired or wireless communication of signalling and/or data between network node 1160, network 1106, and/or WDs 1110. As illustrated, interface 1190 comprises port(s)/terminal(s) 1194 to send and receive data, for example to and from network 1106 over a wired connection. Interface 1190 also includes radio front end circuitry 1192 that may be coupled to, or in certain embodiments a part of, antenna 1162. Radio front end circuitry 1192 comprises filters 1198 and amplifiers 1196. Radio front end circuitry 1192 may be connected to antenna 1162 and processing circuitry 1170. Radio front end circuitry may be configured to condition signals communicated between antenna 1162 and processing circuitry 1170. Radio front end circuitry 1192 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 1192 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1198 and/or amplifiers 1196. The radio signal may then be transmitted via antenna 1162. Similarly, when receiving data, antenna 1162 may collect radio signals which are then converted into digital data by radio front end circuitry 1192. The digital data may be passed to processing circuitry 1170. In other embodiments, the interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, network node 1160 may not include separate radio front end circuitry 1192, instead, processing circuitry 1170 may comprise radio front end circuitry and may be connected to antenna 1162 without separate radio front end circuitry 1192.

Similarly, in some embodiments, all or some of RF transceiver circuitry 1172 may be considered a part of interface 1190. In still other embodiments, interface 1190 may include one or more ports or terminals 1194, radio front end circuitry 1192, and RF transceiver circuitry 1172, as part of a radio unit (not shown), and interface 1190 may communicate with baseband processing circuitry 1174, which is part of a digital unit (not shown).

Antenna 1162 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 1162 may be coupled to radio front end circuitry 1190 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 1162 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna 1162 may be separate from network node 1160 and may be connectable to network node 1160 through an interface or port.

Antenna 1162, interface 1190, and/or processing circuitry 1170 may 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 1162, interface 1190, and/or processing circuitry 1170 may 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 1187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 1160 with power for performing the functionality described herein. Power circuitry 1187 may receive power from power source 1186. Power source 1186 and/or power circuitry 1187 may be configured to provide power to the various components of network node 1160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 1186 may either be included in, or external to, power circuitry 1187 and/or network node 1160. For example, network node 1160 may 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 1187. As a further example, power source 1186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 1187. 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 1160 may include additional components beyond those shown in Figure 8 that 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 1160 may include user interface equipment to allow input of information into network node 1160 and to allow output of information from network node 1160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 1160.

As used herein, wireless device (WD) refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. In some embodiments, a WD may be configured to transmit and/or receive information without direct human interaction. For instance, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE) a vehicle-mounted wireless terminal device, etc.. A WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (loT) scenario, a WD may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another WD and/or a network node. The WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the WD may be a UE implementing the 3GPP narrow band internet of things (NB-loT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

As illustrated, wireless device 1110 includes antenna 1111 , interface 1114, processing circuitry 1120, device readable medium 1130, user interface equipment 1132, auxiliary equipment 1134, power source 1136 and power circuitry 1137. WD 1110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 1110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, NB-loT, 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 1110.

Antenna 1111 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 1114. In certain alternative embodiments, antenna 1111 may be separate from WD 1110 and be connectable to WD 1110 through an interface or port. Antenna 1111 , interface 1114, and/or processing circuitry 1120 may 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 1111 may be considered an interface.

As illustrated, interface 1114 comprises radio front end circuitry 1112 and antenna 1111. Radio front end circuitry 1112 comprise one or more filters 1118 and amplifiers 1116. Radio front end circuitry 1114 is connected to antenna 1111 and processing circuitry 1120, and is configured to condition signals communicated between antenna 1111 and processing circuitry 1120. Radio front end circuitry 1112 may be coupled to or a part of antenna 1111. In some embodiments, WD 1110 may not include separate radio front end circuitry 1112; rather, processing circuitry 1120 may comprise radio front end circuitry and may be connected to antenna 1111. Similarly, in some embodiments, some or all of RF transceiver circuitry 1122 may be considered a part of interface 1114. Radio front end circuitry 1112 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 1112 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1118 and/or amplifiers 1116. The radio signal may then be transmitted via antenna 1111. Similarly, when receiving data, antenna 1111 may collect radio signals which are then converted into digital data by radio front end circuitry 1112. The digital data may be passed to processing circuitry 1120. In other embodiments, the interface may comprise different components and/or different combinations of components.

Processing circuitry 1120 may 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 1110 components, such as device readable medium 1130, WD 1110 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 1120 may execute instructions stored in device readable medium 1130 or in memory within processing circuitry 1120 to provide the functionality disclosed herein.

As illustrated, processing circuitry 1120 includes one or more of RF transceiver circuitry 1122, baseband processing circuitry 1124, and application processing circuitry 1126. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry 1120 of WD 1110 may comprise a SOC. In some embodiments, RF transceiver circuitry 1122, baseband processing circuitry 1124, and application processing circuitry 1126 may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry 1124 and application processing circuitry 1126 may be combined into one chip or set of chips, and RF transceiver circuitry 1122 may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry 1122 and baseband processing circuitry 1124 may be on the same chip or set of chips, and application processing circuitry 1126 may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry 1122, baseband processing circuitry 1124, and application processing circuitry 1126 may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry 1122 may be a part of interface 1114. RF transceiver circuitry 1122 may condition RF signals for processing circuitry 1120.

In certain embodiments, some or all of the functionality described herein as being performed by a WD may be provided by processing circuitry 1120 executing instructions stored on device readable medium 1130, 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 1120 without 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 1120 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 1120 alone or to other components of WD 1110, but are enjoyed by WD 1110 as a whole, and/or by end users and the wireless network generally.

Processing circuitry 1120 may 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 1120, may include processing information obtained by processing circuitry 1120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 1110, 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 1130 may 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 1120. Device readable medium 1130 may 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 1120. In some embodiments, processing circuitry 1120 and device readable medium 1130 may be considered to be integrated.

User interface equipment 1132 may provide components that allow for a human user to interact with WD 1110. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment 1132 may be operable to produce output to the user and to allow the user to provide input to WD 1110. The type of interaction may vary depending on the type of user interface equipment 1132 installed in WD 1110. For example, if WD 1110 is a smart phone, the interaction may be via a touch screen; if WD 1110 is 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 1132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 1132 is configured to allow input of information into WD 1110, and is connected to processing circuitry 1120 to allow processing circuitry 1120 to process the input information. User interface equipment 1132 may 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 1132 is also configured to allow output of information from WD 1110, and to allow processing circuitry 1120 to output information from WD 1110. User interface equipment 1132 may 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 1132, WD 1110 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.

Auxiliary equipment 1134 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment 1134 may vary depending on the embodiment and/or scenario.

Power source 1136 may, 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 1110 may further comprise power circuitry 1137 for delivering power from power source 1136 to the various parts of WD 1110 which need power from power source 1136 to carry out any functionality described or indicated herein. Power circuitry 1137 may in certain embodiments comprise power management circuitry. Power circuitry 1137 may additionally or alternatively be operable to receive power from an external power source; in which case WD 1110 may 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 1137 may also in certain embodiments be operable to deliver power from an external power source to power source 1136. This may be, for example, for the charging of power source 1136. Power circuitry 1137 may perform any formatting, converting, or other modification to the power from power source 1136 to make the power suitable for the respective components of WD 1110 to which power is supplied.

Figure 9 illustrates one embodiment of a UE in accordance with various aspects described herein. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). UE 1200 may be any UE identified by the 3rd Generation Partnership Project (3GPP), including a NB-loT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE 1200, as illustrated in Figure 9, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, the term WD and UE may be used interchangeable. Accordingly, although Figure 9 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.

In Figure 9, UE 1200 includes processing circuitry 1201 that is operatively coupled to input/output interface 1205, radio frequency (RF) interface 1209, network connection interface 1211, memory 1215 including random access memory (RAM) 1217, read-only memory (ROM) 1219, and storage medium 1221 or the like, communication subsystem 1231 , power source 1233, and/or any other component, or any combination thereof. Storage medium 1221 includes operating system 1223, application program 1225, and data 1227. In other embodiments, storage medium 1221 may include other similar types of information. Certain UEs may utilize all of the components shown in Figure 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.

In Figure 9, processing circuitry 1201 may be configured to process computer instructions and data. Processing circuitry 1201 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 1201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

In the depicted embodiment, input/output interface 1205 may be configured to provide a communication interface to an input device, output device, or input and output device. UE 1200 may be configured to use an output device via input/output interface 1205. An output device may use the same type of interface port as an input device. For example, a USB port may be used to provide input to and output from UE 1200. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. UE 1200 may be configured to use an input device via input/output interface 1205 to allow a user to capture information into UE 1200. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence- sensitive display may include a capacitive or resistive touch sensor to sense input from a user.

A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

In Figure 9, RF interface 1209 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface 1211 may be configured to provide a communication interface to network 1243a. Network 1243a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 1243a may comprise a Wi-Fi network. Network connection interface 1211 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like. Network connection interface 1211 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.

RAM 1217 may be configured to interface via bus 1202 to processing circuitry 1201 to 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 1219 may be configured to provide computer instructions or data to processing circuitry 1201. For example, ROM 1219 may 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 1221 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable readonly memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium 1221 may be configured to include operating system 1223, application program 1225 such as a web browser application, a widget or gadget engine or another application, and data file 1227. Storage medium 1221 may store, for use by UE 1200, any of a variety of various operating systems or combinations of operating systems.

Storage medium 1221 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof. Storage medium 1221 may allow UE 1200 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium 1221 , which may comprise a device readable medium. In Figure 9, processing circuitry 1201 may be configured to communicate with network 1243b using communication subsystem 1231. Network 1243a and network 1243b may be the same network or networks or different network or networks. Communication subsystem 1231 may be configured to include one or more transceivers used to communicate with network 1243b. For example, communication subsystem 1231 may 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.11 ,

CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter 1233 and/or receiver 1235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 1233 and receiver 1235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions of communication subsystem 1231 may include data communication, voice communication, multimedia communication, short- range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. For example, communication subsystem 1231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network 1243b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 1243b may be a cellular network, a Wi-Fi network, and/or a near-field network. Power source 1213 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE 1200.

The features, benefits and/or functions described herein may be implemented in one of the components of UE 1200 or partitioned across multiple components of UE 1200. 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 1231 may be configured to include any of the components described herein. Further, processing circuitry 1201 may be configured to communicate with any of such components over bus 1202. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 1201 perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry 1201 and communication subsystem 1231. 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.

Figure 10 is a schematic block diagram illustrating a virtualization environment 1300 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks). 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 1300 hosted by one or more of hardware nodes 1330.

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 1320 (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 1320 are run in virtualization environment 1300 which provides hardware 1330 comprising processing circuitry 1360 and memory 1390. Memory 1390 contains instructions 1395 executable by processing circuitry 1360 whereby application 1320 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

Virtualization environment 1300, comprises general-purpose or special-purpose network hardware devices 1330 comprising a set of one or more processors or processing circuitry 1360, 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 1390-1 which may be non-persistent memory for temporarily storing instructions 1395 or software executed by processing circuitry 1360. Each hardware device may comprise one or more network interface controllers (NICs) 1370, also known as network interface cards, which include physical network interface 1380. Each hardware device may also include non-transitory, persistent, machine-readable storage media 1390-2 having stored therein software 1395 and/or instructions executable by processing circuitry 1360. Software 1395 may include any type of software including software for instantiating one or more virtualization layers 1350 (also referred to as hypervisors), software to execute virtual machines 1340 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

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

During operation, processing circuitry 1360 executes software 1395 to instantiate the hypervisor or virtualization layer 1350, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 1350 may present a virtual operating platform that appears like networking hardware to virtual machine 1340.

As shown in Figure 10, hardware 1330 may be a standalone network node with generic or specific components. Hardware 1330 may comprise antenna 13225 and may implement some functions via virtualization. Alternatively, hardware 1330 may 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) 13100, which, among others, oversees lifecycle management of applications 1320.

Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment. In the context of NFV, virtual machine 1340 may 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 1340, and that part of hardware 1330 that 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 1340, 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 1340 on top of hardware networking infrastructure 1330 and corresponds to application 1320 in Figure 10.

In some embodiments, one or more radio units 13200 that each include one or more transmitters 13220 and one or more receivers 13210 may be coupled to one or more antennas 13225. Radio units 13200 may communicate directly with hardware nodes 1330 via 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 signaling can be effected with the use of control system 13230 which may alternatively be used for communication between the hardware nodes 1330 and radio units 13200.

Figure 11 illustrates a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments. In particular, with reference to FIGURE 11 , in accordance with an embodiment, a communication system includes telecommunication network 1410, such as a 3GPP-type cellular network, which comprises access network 1411 , such as a radio access network, and core network 1414. Access network 1411 comprises a plurality of base stations 1412a, 1412b, 1412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 1413a, 1413b, 1413c. Each base station 1412a, 1412b, 1412c is connectable to core network 1414 over a wired or wireless connection 1415. A first UE 1491 located in coverage area 1413c is configured to wirelessly connect to, or be paged by, the corresponding base station 1412c. A second UE 1492 in coverage area 1413a is wirelessly connectable to the corresponding base station 1412a. While a plurality of UEs 1491 , 1492 are 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 1412.

Telecommunication network 1410 is itself connected to host computer 1430, 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 1430 may 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 1421 and 1422 between telecommunication network 1410 and host computer 1430 may extend directly from core network 1414 to host computer 1430 or may go via an optional intermediate network 1420. Intermediate network 1420 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 1420, if any, may be a backbone network or the Internet; in particular, intermediate network 1420 may comprise two or more sub-networks (not shown).

The communication system of Figure 11 as a whole enables connectivity between the connected UEs 1491 , 1492 and host computer 1430. The connectivity may be described as an over-the-top (OTT) connection 1450. Host computer 1430 and the connected UEs 1491 , 1492 are configured to communicate data and/or signaling via OTT connection 1450, using access network 1411 , core network 1414, any intermediate network 1420 and possible further infrastructure (not shown) as intermediaries. OTT connection 1450 may be transparent in the sense that the participating communication devices through which OTT connection 1450 passes are unaware of routing of uplink and downlink communications. For example, base station 1412 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 1430 to be forwarded (e.g., handed over) to a connected UE 1491. Similarly, base station 1412 need not be aware of the future routing of an outgoing uplink communication originating from the UE 1491 towards the host computer 1430.

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 to Figure 12. Figure 12 illustrates host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments In communication system 1500, host computer 1510 comprises hardware 1515 including communication interface 1516 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 1500. Host computer 1510 further comprises processing circuitry 1518, which may have storage and/or processing capabilities. In particular, processing circuitry 1518 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. Host computer 1510 further comprises software 1511 , which is stored in or accessible by host computer 1510 and executable by processing circuitry 1518. Software 1511 includes host application 1512. Host application 1512 may be operable to provide a service to a remote user, such as UE 1530 connecting via OTT connection 1550 terminating at UE 1530 and host computer 1510. In providing the service to the remote user, host application 1512 may provide user data which is transmitted using OTT connection 1550.

Communication system 1500 further includes base station 1520 provided in a telecommunication system and comprising hardware 1525 enabling it to communicate with host computer 1510 and with UE 1530. Hardware 1525 may include communication interface 1526 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 1500, as well as radio interface 1527 for setting up and maintaining at least wireless connection 1570 with UE 1530 located in a coverage area (not shown in Figure 12) served by base station 1520. Communication interface 1526 may be configured to facilitate connection 1560 to host computer 1510. Connection 1560 may be direct or it may pass through a core network (not shown in Figure 12) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware 1525 of base station 1520 further includes processing circuitry 1528, 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 1520 further has software 1521 stored internally or accessible via an external connection.

Communication system 1500 further includes UE 1530 already referred to. Its hardware 1535 may include radio interface 1537 configured to set up and maintain wireless connection 1570 with a base station serving a coverage area in which UE 1530 is currently located. Hardware 1535 of UE 1530 further includes processing circuitry 1538, 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 1530 further comprises software 1531 , which is stored in or accessible by UE 1530 and executable by processing circuitry 1538. Software 1531 includes client application 1532. Client application 1532 may be operable to provide a service to a human or non-human user via UE 1530, with the support of host computer 1510. In host computer 1510, an executing host application 1512 may communicate with the executing client application 1532 via OTT connection 1550 terminating at UE 1530 and host computer 1510. In providing the service to the user, client application 1532 may receive request data from host application 1512 and provide user data in response to the request data. OTT connection 1550 may transfer both the request data and the user data. Client application 1532 may interact with the user to generate the user data that it provides.

It is noted that host computer 1510, base station 1520 and UE 1530 illustrated in Figure 12 may be similar or identical to host computer 1430, one of base stations 1412a, 1412b, 1412c and one of UEs 1491 , 1492 of Figure 11 , respectively. This is to say, the inner workings of these entities may be as shown in Figure 12 and independently, the surrounding network topology may be that of Figure 11 .

In Figure 12, OTT connection 1550 has been drawn abstractly to illustrate the communication between host computer 1510 and UE 1530 via base station 1520, 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 1530 or from the service provider operating host computer 1510, or both. While OTT connection 1550 is 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 1570 between UE 1530 and base station 1520 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE 1530 using OTT connection 1550, in which wireless connection 1570 forms the last segment. More precisely, the teachings of these embodiments may allow the network to efficiently adjust the responseness/power-consumption tradeoff of multiple wireless devices, and thereby provide benefits such as reduced latency and hence user waiting time, better responsiveness, and extended battery lifetime.

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 1550 between host computer 1510 and UE 1530, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection 1550 may be implemented in software 1511 and hardware 1515 of host computer 1510 or in software 1531 and hardware 1535 of UE 1530, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection 1550 passes; 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 1511 , 1531 may compute or estimate the monitored quantities. The reconfiguring of OTT connection 1550 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 1520, and it may be unknown or imperceptible to base station 1520. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer 1510’s measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software 1511 and 1531 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 1550 while it monitors propagation times, errors etc. Figure 13 is 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 to Figure 11 and Figure 12. For simplicity of the present disclosure, only drawing references to Figure 13 will be included in this section. In step 1610, the host computer provides user data. In substep 1611 (which may be optional) of step 1610, the host computer provides the user data by executing a host application. In step 1620, the host computer initiates a transmission carrying the user data to the UE. In step 1630 (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 1640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

Figure 14 is 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 to Figure 11 and Figure 12. For simplicity of the present disclosure, only drawing references to Figure 14 will be included in this section. In step 1710 of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application.

In step 1720, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1730 (which may be optional), the UE receives the user data carried in the transmission.

Figure 15 is 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 to Figure 11 and Figure 12. For simplicity of the present disclosure, only drawing references to Figure 15 will be included in this section. In step 1810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 1820, the UE provides user data. In substep 1821 (which may be optional) of step 1820, the UE provides the user data by executing a client application. In substep 1811 (which may be optional) of step 1810, 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 1830 (which may be optional), transmission of the user data to the host computer. In step 1840 of 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.

Figure 16 is 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 to Figure 11 and Figure 12. For simplicity of the present disclosure, only drawing references to Figure 16 will be included in this section. In step 1910 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 1920 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 1930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the description.

The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.

Some of the embodiments contemplated herein are described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein. The disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. Representative embodiments are presented below:

Group A Embodiments

1 . A method (100), performed by a wireless device (10) operative in a wireless communication network and participating in a connected mode Discontinuous Reception, cDRX, of dynamically altering an active time, the method (100) comprising: receiving (102), from the network, a common Active Time Modification, ATM, indication that is sent to a plurality of wireless devices; and altering (104) a previously determined active time in response to the ATM indication.

2. The method (100) of embodiment 1 wherein the common ATM indication is in one Downlink Control Information message sent to a plurality of wireless devices at the same time, and the Downlink Control Information message is associated with a Radio Network Temporary Identifier dedicated to ATM signalling.

3. The method (100) of embodiment 2 wherein the Radio Network Temporary Identifier dedicated to ATM signalling is a group Radio Network Temporary Identifier dedicated to ATM signalling.

4. The method (100) of embodiment 2 wherein the Downlink Control Information message conforms to format 2-6.

5. The method (100) of embodiment 1 wherein the common ATM indication is incorporated into a Wake Up Signal sent to the plurality of wireless devices (10).

6. The method (100) of embodiment 1 wherein the Downlink Control Information Message is used for wake-up indication and notifying the power saving information for two or more UEs, and one or more bits in the Downlink Control Information Message are used to indicate whether to extend or reduce the active time.

7. The method (100) of any preceding embodiment wherein altering (104) a previously determined active time in response to the ATM indication comprises extending a previously determined active time in response to the ATM indication.

8. The method (100) of embodiment 7 wherein extending a previously determined active time in response to the ATM indication comprises adding a specified duration to the wireless device’s onDuration. 9. The method (100) of embodiment 7 wherein extending a previously determined active time in response to the ATM indication comprises increasing the wireless device’s InActivity Timer value.

10. The method (100) of any of embodiments 1 -6 wherein altering (104) a previously determined active time in response to the ATM indication comprises decreasing a previously determined active time in response to the ATM indication.

11. The method (100) of embodiment 10 wherein decreasing a previously determined active time in response to the ATM indication comprises one of decreasing the wireless device’s onDuration and decreasing the wireless device’s InActivity Timer value.

12. The method (100) of any of embodiments 7-11 , wherein the duration of active time extension or delay until active time termination is in units of symbols, slots, or milliseconds.

13. The method (100) of embodiment 12, wherein the ATM indication includes an index to a table of the values configured by the network or specified by a wireless network operating protocol.

14. The method (100) of any preceding embodiment wherein the wireless device (10) is configured for Carrier Aggregation and wherein altering (104) a previously determined active time in response to the ATM indication comprises altering the previously determined active time only on one or more specified carriers and/or specified frequency ranges.

15. The method (100) of any of embodiments 1-13 wherein the wireless device (10) is configured for Carrier Aggregation and wherein altering a previously determined active time in response to the ATM indication comprises altering the previously determined active time only on the cell on which the ATM indication is received, but not any other configured cell.

16. The method (100) of any preceding embodiment wherein the wireless device (10) is in connected mode but not monitoring a Physical Downlink Control Channel, and wherein the ATM indication is an ATM command added to a Downlink Control Information in common search space that the wireless device periodically decodes.

17. The method (100) of embodiment 2 wherein the Downlink Control Information message is a non-scheduling Downlink Control Information message. 18. The method (100) of embodiment 2 wherein the Downlink Control Information message is a scheduling Downlink Control Information message other than format 1-0 or 0-0.

19. The method (100) of embodiment 2, wherein the Downlink Control Information message includes a first bitfield associated with the plurality of wireless devices (10), and wherein altering (104) a previously determined active time in response to the ATM indication comprises, in response to a bit in the first bitfield corresponding to this wireless device (10), applying preconfigured ATM operations.

20. The method (100) of embodiment 19, wherein the Downlink Control Information message further includes a second bitfield associated with ATM, and wherein the wireless device (10) performs an operation indicated by the second bitfield in response to a bit in the first bitfield corresponding to this wireless device (10).

21 . The method (100) of any of embodiments 19-20, wherein the mapping of the first and/or second bitfield is configured by higher layer signaling.

22. The method (100) of embodiment 1 wherein the ATM indication is an ATM bitfield in a scheduling or non-scheduling Downlink Control Information message, wherein the corresponding Physical Downlink Control Channel candidate is configured with an association of a Common Search Space and a common Coreset for the plurality wireless devices (10), such that the plurality of wireless devices (10) are addressed with the same Physical Downlink Control Channel.

23. The method (100) of embodiment 22 wherein the Physical Downlink Control Channel is associated with a Radio Network Temporary Identifier dedicated to ATM signaling.

24. The method (100) of embodiment 23 wherein the ATM bitfield comprises reserved bits of Downlink Control Information messages of format 1-0 or 0-0.

25. The method (100) of embodiment 23 wherein the ATM bitfield in included in Downlink Control Information messages of format other than 1-0 or 0-0 which is associated with a common search space.

AA. The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host computer via the transmission to the base station. Group B Embodiments [ numbering intentionally skipped to 511

51. A method (200), performed by a base station (30) operative in a wireless communication network, of dynamically altering an active time of a plurality of wireless devices (10) via common signaling, the method (200) comprising: preparing (202) a common Active Time Modification, ATM, indication configured to alter a previously determined active time of a plurality of wireless devices (10); and sending (204) the ATM indication to a plurality of wireless devices (10).

52. The method (200) of embodiment 51 wherein the common ATM indication is a Downlink Control Information message using a Radio Network Temporary Identifier dedicated to ATM signalling.

53. The method (200) of embodiment 53 wherein the Radio Network Temporary Identifier dedicated to ATM signalling is a group Radio Network Temporary Identifier dedicated to ATM signalling.

54. The method (200) of embodiment 52 wherein the Downlink Control Information message conforms to format 2-6.

55. The method (200) of embodiment 51 wherein the common ATM indication is incorporated into a Wake Up Signal sent to a plurality of wireless devices (10).

56. The method (200) of embodiment 51 wherein the Downlink Control Information Message is used for wake-up indication and notifying the power saving information for one or more UEs, and one or more bits in the Downlink Control Information Message are used to indicate whether to extend or reduce the active time.

57. The method (200) of any of embodiments 51-56 wherein the ATM indication is configured to alter (104) a previously determined active time of a plurality of wireless devices (10) by extending a previously determined active time of the wireless devices (10) in response to the ATM indication.

58. The method (200) of embodiment 57 wherein extending a previously determined active time in response to the ATM indication comprises adding a specified duration to the wireless device’s onDuration. 59. The method (200) of embodiment 57 wherein extending a previously determined active time of the wireless devices in response to the ATM indication comprises increasing the wireless devices’ InActivity Timer values.

60. The method (200) of any of embodiments 51-56 wherein the ATM indication is configured to alter (104) a previously determined active time of a plurality of wireless devices (10) by decreasing a previously determined active time of the wireless devices (10) in response to the ATM indication.

61. The method (200) of embodiment 60 wherein decreasing a previously determined active time of the wireless devices (10) in response to the ATM indication comprises one of decreasing the wireless devices’ onDuration and decreasing the wireless devices’ InActivity Timer values.

62. The method (200) of any of embodiments 57-61 , wherein the duration of active time extension or delay until active time termination is in units of symbols, slots, or milliseconds.

63. The method (200) of embodiment 62, wherein the ATM indication includes an index to a table of the values configured by the network or specified by a wireless network operating protocol.

64. The method (200) of any of embodiments 51-63 wherein the wireless devices (10) are configured for Carrier Aggregation and wherein the ATM indication is configured to alter (104) a previously determined active time of the wireless devices (10) in response to the ATM indication by altering the previously determined active time of the wireless devices (10) only on one or more specified carriers and/or specified frequency ranges.

65. The method (200) of any of embodiments 51-64 wherein the wireless devices (10) are configured for Carrier Aggregation and wherein the ATM indication is configured to alter (104) a previously determined active time of the wireless devices (10) in response to the ATM indication by altering the previously determined active time of the wireless devices (10) only on the cell on which the ATM indication is transmitted, but not any other configured cell.

66. The method (200) of embodiment 52 wherein the Downlink Control Information message is a non-scheduling Downlink Control Information message.

67. The method (200) of embodiment 52 wherein the Downlink Control Information message is a scheduling Downlink Control Information message other than format 1-0 or 0-0. 68. The method (200) of embodiment 52 wherein a first bitfield in the DCI identifies wireless devices (10) in the plurality.

69. The method (200) of embodiment 68 wherein a second bitfield in the DCI indicates ATM operations for wireless devices (10) identified by the first bitfield.

70. The method (200) of any of embodiments 51-69 wherein the ATM indication includes an index to a table specifying one of a duration of ATM-e and delay until ATM-t.

71. The method (200) of any of embodiments 51-70 wherein the ATM indication includes an indicator identifying the plurality of wireless devices (10) to which it is directed.

72. The method (200) of embodiment 71 wherein the indicator identifies wireless devices (10) by wireless devices (10) capability.

73. The method (200) of embodiment 71 wherein the indicator identifies wireless devices (10) by reference to a predetermined grouping.

74. The method (200) of embodiment 71 wherein the indicator identifies wireless devices (10) by their current AT status relative to a predetermined AT-related duration.

75. The method (200) of embodiment 71 wherein the indicator identifies wireless devices (10) by a network service currently running on the wireless devices (10).

76. The method (200) of any of embodiments 51-69 wherein simultaneously sending (204) the ATM indication to a plurality of wireless devices (10) comprises simultaneously sending the ATM indication only to wireless devices (10) having sufficient remaining onDuration or InActivity Timer to account for an application delay by the wireless devices (10) in interpreting and activating the ATM indication.

77. The method (200) of any of embodiments 51-76 wherein the common ATM indication comprises a bitfield indicating ATM in a current scheduling or non-scheduling Downlink Control Information message. 78. The method (200) of embodiment 77 wherein a Physical Downlink Control Channel transmission corresponding to the Downlink Control Information is configured with association of a Common Search Space and a common Coreset for the wireless devices (10), such that all the plurality of wireless devices (10) can be addressed with the same Physical Downlink Control Channel transmission.

79. The method (200) of embodiment 78 wherein the corresponding Physical Downlink Control Channel transmission is associated with a Radio Network Temporary Identifier dedicated to ATM signalling, such that the plurality of wireless devices (10) can distinguish the ATM PDCCH transmission from PDCCH transmissions associated with other Radio Network Temporary Identifiers.

80. The method (200) of embodiment 77 wherein the bitfield indicating ATM comprises one of reserved bits of fallback Downlink Control Information, or an additional bitfield in other Downlink Control Information formats.

81 . The method (200) of embodiment 80 wherein the fallback Downlink Control Information comprise Downlink Control Information formats 1-0 and 0-0.

82. The method (200) of embodiment 52 wherein the DCI message is a non-scheduling DCI message.

83. The method (200) of embodiment 52 wherein the DCI message is a scheduling DCI message other than format 1-0 or 0-0.

BB. The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host computer or a wireless device.

Group C Embodiments

C1. A UE configured to perform any of the steps of any of the Group A embodiments.

C2. A UE comprising: processing circuitry configured to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the UE.

C3. A UE comprising: processing circuitry and memory, the memory containing instructions executable by the processing circuitry whereby the UE is configured to perform any of the steps of any of the Group A embodiments.

C4. A user equipment (UE) comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.

C5. A computer program comprising instructions which, when executed by at least one processor of a UE, causes the UE to carry out the steps of any of the Group A embodiments.

C6. A carrier containing the computer program of embodiment C5, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

C7. A base station configured to perform any of the steps of any of the Group B embodiments.

C8. A base station comprising: processing circuitry configured to perform any of the steps of any of the Group B embodiments; power supply circuitry configured to supply power to the base station.

C9. A base station comprising: processing circuitry and memory, the memory containing instructions executable by the processing circuitry whereby the base station is configured to perform any of the steps of any of the Group B embodiments.

C10. A computer program comprising instructions which, when executed by at least one processor of a base station, causes the base station to carry out the steps of any of the Group B embodiments.

C11 . A carrier containing the computer program of embodiment C10, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium. Group D Embodiments

D1. A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE), wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.

D2. The communication system of the pervious embodiment further including the base station.

D3. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.

D4. The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application.

D5. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of the Group B embodiments.

D6. The method of the previous embodiment, further comprising, at the base station, transmitting the user data.

D7. The method of the previous 2 embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application.

D8. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to perform any of the previous 3 embodiments.

D9. A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform any of the steps of any of the Group A embodiments. D10. The communication system of the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE.

D11. The communication system of the previous 2 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE’s processing circuitry is configured to execute a client application associated with the host application.

D12. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of the Group A embodiments.

D13. The method of the previous embodiment, further comprising at the UE, receiving the user data from the base station.

D14. A communication system including a host computer comprising: communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform any of the steps of any of the Group A embodiments.

D15. The communication system of the previous embodiment, further including the UE.

D16. The communication system of the previous 2 embodiments, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.

D17. The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.

D18. The communication system of the previous 4 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data. D19. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.

D20. The method of the previous embodiment, further comprising, at the UE, providing the user data to the base station.

D21. The method of the previous 2 embodiments, further comprising: at the UE, executing a client application, thereby providing the user data to be transmitted; and at the host computer, executing a host application associated with the client application.

D22. The method of the previous 3 embodiments, further comprising: at the UE, executing a client application; and at the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application, wherein the user data to be transmitted is provided by the client application in response to the input data.

D23. A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.

D24. The communication system of the previous embodiment further including the base station.

D25. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.

D26. The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.

D27. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.

D28. The method of the previous embodiment, further comprising at the base station, receiving the user data from the UE. D29. The method of the previous 2 embodiments, further comprising at the base station, initiating a transmission of the received user data to the host computer.