Patent Description:
An example of a cellular communication system is an architecture that is being standardized by the <NUM>rd Generation Partnership Project, 3GPP. A recent development in this field is often referred to as the long-term evolution, LTE, of the Universal Mobile Telecommunications System, UMTS, radio-access technology. E-UTRA (evolved UMTS Terrestrial Radio Access) is the air interface of 3GPP's LTE upgrade path for mobile networks. In LTE, base stations or access points, APs, which are referred to as enhanced Node AP, eNBs, provide wireless access within a coverage area or cell. In LTE, mobile devices, or mobile stations are referred to as user equipment, UE. LTE has included a number of improvements or developments.

A global bandwidth shortage facing wireless carriers has motivated the consideration of the underutilized millimeter wave, mmWave, frequency spectrum for future broadband cellular communication networks, for example. mmWave (or extremely high frequency) may, for example, include the frequency range between <NUM> and <NUM> gigahertz (GHz). Radio waves in this band may, for example, have wavelengths from ten to one millimeter, giving it the name millimeter band or millimeter wave. The amount of wireless data will likely significantly increase in the coming years. Various techniques have been used in attempt to address this challenge including obtaining more spectrum, having smaller cell sizes, and using improved technologies enabling more bits/s/Hz. One element that may be used to obtain more spectrum is to move to higher frequencies, e.g., above <NUM>. For fifth generation wireless systems (<NUM>), an access architecture for deployment of cellular radio equipment employing mmWave radio spectrum has been proposed. Other example spectrums may also be used, such as cmWave radio spectrum (e.g., <NUM>-<NUM>).

<CIT> discloses Discontinuous reception (DRX) operations for wireless communications implementing carrier aggregation are disclosed. Physical downlink control channel implementation for carrier aggregation is also disclosed. DRX methods are disclosed including a common DRX protocol that may be applied across all component carriers, an individual/independent DRX protocol that is applied on each component carrier, and hybrid approaches that are applied across affected component carriers. Methods for addressing the effects of loss of synchronization on DRX, impact of scheduling request on DRX, uplink power control during DRX, and DRX operation in measurement gaps are disclosed.

<CIT> discloses systems, apparatuses, and methods to enable coupling between a power states and a beam management states. A method is provided for jointly performing beam management and power management in a wireless transmit/receive unit (WTRU), where the WTRU is configured to operate according to a plurality of power states and a plurality of beam management states that are linked to the plurality of power states such that each power state corresponds to a different beam management state. The method includes detecting a trigger condition; transitioning the WTRU between a first power state to a second power state based on the detected trigger condition; and transitioning the WTRU between a first beam management state to a second beam management state responsive to the transition to the second power state to which the second beam management state is linked.

<CIT> discloses DRX operations that address impacts of beamforming to current DRX operations. The new NR-PDCCH may affect the downlink control channel monitoring in DRX operations. DRX embodiments are disclosed addressing the impact of new NR-PDCCH to DRX operations. In NR, multiple DRX configurations may be supported, and Ll/<NUM> signaling (such as MAC CE based) can be used for dynamic DRX configuration switching. Signaling and other mechanisms are disclosed to support multiple DRX configurations, and switching between multiple configurations. DRX operations are disclosed addressing the impact of HARQ design in NR to DRX operations. Further DRX operations are disclosed addressing the impact of multiple SR configurations in NR to DRX operation.

According to a first aspect, there is provided a method as defined by appended claim <NUM>.

The method may further comprise, prior to receiving configuration data, capability data may be transmitted to a base station (gNB), the capability data representing lengths of time required for the UE to perform specified adaptation operations.

The plurality of windows may include a first window having an end that is a first number of time slots from the on portion of the DRX cycle and a second window having an end that is a second number of time slots from the on portion of the DRX cycle, the first number being larger than the second number.

The subset of the plurality of triggering commands with which the first window is associated may include at least one of a bandwidth portion (BWP) adaptation, channel state information reference signal (CSI-RS) measurement and reporting, tracking reference signal (TRS) triggering, and triggering to start monitoring of PDCCHs during the on portion of the DRX cycle.

The subset of the plurality of triggering commands with which the second window is associated may include at least triggering to start monitoring of PDCCHs during the on portion of the DRX cycle.

A beginning of the first window and a beginning of the second window may include the same time slot or produces an overlap duration.

The plurality of windows may further include a third window having an end. The end may be a third number of time slots from the on portion of the DRX cycle. The third number may be larger than the second number. The third number may be smaller than the first number. The subset of the plurality of triggering commands with which the third window is associated may include at least TRS triggering and triggering to start monitoring of PDCCHs during the on portion of the DRX cycle.

The second window may have a duration substantially equal to the offset.

The offset may be based on a duration of the DRX cycle.

The offset may be based on the plurality of triggering commands for adaptation operations.

A common DCI format for triggering commands for adaptation operations may include fields for triggering the monitoring operation over PDCCHs and commands for UE adaptations requiring a processing time specific to the UE.

In response to the configured DRX cycle being below a threshold duration, the corresponding window of the plurality of windows and the offset may have different durations.

A triggering command of the plurality of triggering commands may include the UE determining whether the UE is in a default bandwidth portion, BWP.

The triggering command may further include changing the BWP to a portion that is not the default BWP.

The configuration data may further include a configuration timer such that the UE does not expect to receive specified triggering commands until the configuration timer has expired, the configuration timer starting upon reception of the triggering command,.

According to an aspect, there is provided a method as defined by appended claim <NUM>.

The details of one or more examples of implementations are set forth in the accompanying drawings and the description below.

<FIG> is a block diagram of a digital communications system such as a wireless network <NUM> according to an example implementation. In the wireless network <NUM> of <FIG>, user devices <NUM>, <NUM>, <NUM> and <NUM>, which may also be referred to as mobile stations (MSs) or user equipment (UEs), may be connected (and in communication) with a base station (BS) <NUM>, which may also be referred to as an access point (AP), an enhanced Node B (eNB), a gNB (which may be a <NUM> base station) or a network node. At least part of the functionalities of an access point (AP), base station (BS) or (e)Node B (eNB) may be also be carried out by any node, server or host which may be operably coupled to a transceiver, such as a remote radio head. BS (or AP) <NUM> provides wireless coverage within a cell <NUM>, including to user devices <NUM>, <NUM>, <NUM> and <NUM>. Although only four user devices are shown as being connected or attached to BS <NUM>, any number of user devices may be provided. BS <NUM> is also connected to a core network <NUM> via an interface <NUM>. This is merely one simple example of a wireless network, and others may be used.

A user device (user terminal, user equipment (UE)) may refer to a portable computing device that includes wireless mobile communication devices operating with or without a subscriber identification module (SIM), including, but not limited to, the following types of devices: a mobile station (MS), a mobile phone, a cell phone, a smartphone, a personal digital assistant (PDA), a handset, a device using a wireless modem (alarm or measurement device, etc.), a laptop and/or touch screen computer, a tablet, a phablet, a game console, a notebook, and a multimedia device, as examples.

The various example implementations may be applied to a wide variety of wireless technologies, wireless networks, such as LTE, LTE-A, <NUM> (New Radio, or NR), cmWave, and/or mmWave band networks, or any other wireless network or use case. LTE, <NUM>, cmWave and mmWave band networks are provided only as illustrative examples, and the various example implementations may be applied to any wireless technology/wireless network. The various example implementations may also be applied to a variety of different applications, services or use cases, such as, for example, ultra-reliability low latency communications (URLLC), Internet of Things (IoT), enhanced mobile broadband, massive machine type communications (MMTC), vehicle-to-vehicle (V2V), vehicle-to-device, etc. Each of these use cases, or types of UEs, may have its own set of requirements.

A UE's battery life is an important aspect of a user's experience, which will influence the adoption of <NUM> NR handsets and/or services. Accordingly, UE power consumption is designed to ensure that UE power efficiency for <NUM> NR UEs are improved over that of LTE. Power efficiency can relate to efficiency during data transmission as well as a low consumption of energy when no data is transmitted or received.

Because <NUM> NR supports high speed data transport, the resulting bursts of user data would be served by a network in very short durations. Power saving in a UE involves triggering the UE for network access from a power efficient mode, such as micro sleep or OFF period in the long DRX cycle. In such an approach, the UE would remain in the power efficient mode unless the UE receives an indication of network access through a UE power saving framework. The indication may be part of a wake-up procedure in an RRC CONNECTED state where the UE is configured to receive a power saving signal/channel before a DRX onDuration window, that is, an on portion of a DRX cycle, to trigger the UE waking only when DL data has arrived. The UE is not required to wake up at the DRX on portion for at least PDCCH monitoring, if the power saving signal is not detected.

In conventional approaches to power saving in a UE, the UE could be triggered to wake-up to monitor PDCCH in the next onDuration window. The wake-up indication may also trigger aperiodic CSI-RS transmission and measurement.

In 3GPP NR, a UE in an RRC CONNECTED state can be configured with up to ten search space set configurations that are associated with up to three CORESETs. Each search space set configuration defines how and where the UE is to search PDCCH candidates associated with the search space set via the following higher layer parameters:.

The PDCCH monitoring activity of the UE in RRC connected mode is governed by DRX and bandwidth adaptation (via BWP framework). When DRX is configured, the UE does not have to continuously monitor PDCCH. DRX is characterized by the following parameters:.

<FIG> is a diagram illustrating a discontinuous reception (DRX) cycle <NUM> according to an example implementation. As shown in <FIG>, the DRX cycle includes an on portion <NUM> and an off portion <NUM>. The on portion <NUM> corresponds to the onDuration discussed above.

When bandwidth adaptation is configured, the UE only needs to monitor PDCCH on the one active BWP i.e., it does not have to monitor PDCCH on the entire DL frequency of the cell. A BWP inactivity timer (independent from the DRX inactivity-timer described above) is used to switch the active BWP to the default one: the timer is restarted upon successful PDCCH decoding and the switch to the default BWP takes place when it expires.

The wake-up signal may trigger a BWP adaptation, a CSI-RS measurement and reporting, a TRS triggering, and a triggering to start monitoring during the on portion. Each of these triggered processes uses UE processing resources and requires some time. The above-described conventional approaches to power saving in a UE makes no allowances for such processing times and may degrade the ability of the UE to save power.

In contrast to the above-described conventional approaches to power saving in a UE, improved techniques of power saving in a UE include providing a base station (gNB) with capability to determine validity of triggering mechanisms during an offset in time prior to the on portion of the DRX cycle. This capability includes a plurality of windows during which specified triggering mechanisms are valid. Along these lines, a UE provides capability information to the gNB), where the UE may indicate how long time it would take for the UE to perform certain adaptations in response to triggering commands (e.g., BWP switch, CSI-RS measurement and reporting, etc.). The gNB then generates DRX configuration data based on the capability information, including determining which triggering commands are active for the UE and sends the DRX configuration data to the UE. The UE then starts monitoring wake-up signals, e.g., configured DCI format(s) on PDCCH that are valid based on determined windows, associated DCI formats, and triggering commands. Upon detection of a configured DCI format, the UE performs an adaptation operation according to determined, valid triggering commands.

Advantageously, by determining whether triggering mechanisms are valid within certain windows, a UE can ignore those mechanisms that may interfere with its ability to save power.

In some implementations, a group common DCI format for UE adaptation triggering commands includes fields only for triggering PDCCH monitoring adaptation. In such implementations, triggering commands for UE adaptations requiring UE specific processing time are provided in UE-specific DCI format.

In some implementations, when a UE is configured with a short DRXcycle and a long DRXcycle, or when the configured DRX cycle is below a threshold (e.g., <NUM>), the corresponding window and related offsets for triggering commands may be different or restricted. For example, such as that for DRX cycle periods shorter than <NUM>, the UE does not expect to receive a triggering adaptation command for CSI reporting. In such implementations, when the configured/applied DRX cycle period is longer than a threshold (e.g., <NUM>), the UE may be provided with triggering command for a BWP switch.

In some implementations, when the UE determines that it is in a default BWP, then the UE may determine that the BWP switch is a possible adaptation operation to be triggered.

In some implementations, the UE is configured with a timer, e.g., in ms or in number of DRX cycles (for long and/or short DRX cycles). In such implementations, the UE does not expect to receive certain triggering adaption commands such as BWP change until the timer has expired.

<FIG> shows a flow chart illustrating an example method <NUM> of performing the improved techniques. Operation <NUM> includes receiving, by controlling circuitry of a user equipment (UE), configuration data representing (i) an offset from a start of an on portion of a discontinuous reception (DRX) cycle including the on portion and an off portion, the offset being a specified number of time slots, (ii) identifiers of a plurality of triggering commands for adaptation operations that are active for the UE, and (iii) a plurality of windows, each of the plurality of windows having a specified duration within the offset and being associated with a respective subset of the triggering commands and a respective downlink control information (DCI) format. Operation <NUM> includes performing a monitoring operation over physical downlink control channels (PDCCHs) to determine whether a PDCCH having a DCI format with which at least one of the plurality of windows is associated is present. Operation <NUM> includes, in response to detecting a PDCCH having the DCI format, performing an adaptation operation according to triggering commands of the plurality of triggering commands with which the at least one of the plurality of windows is associated.

<FIG> is a flow chart illustrating an example method <NUM> of performing the improved techniques. Operation <NUM> includes receiving, by processing circuitry of a base station (gNB), capability data from a user equipment (UE), the capability data representing lengths of time required for the UE to perform specified adaptation operations. Operation <NUM> includes, in response to receiving the capability data, generating configuration data representing (i) an offset from a start of an on portion of a discontinuous reception (DRX) cycle including the on portion and an off portion, the offset being a specified number of time slots, (ii) identifiers of a plurality of triggering commands for adaptation operations that are active for the UE, and (iii) a plurality of windows, each of the plurality of windows having a specified duration within the offset and being associated with a respective subset of the triggering commands and a respective downlink control information (DCI) format. Operation <NUM> includes transmitting the capability data to the UE.

Further example implementations and/or example details will now be provided.

<FIG> is a diagram illustrating various windows <NUM> associated with triggering commands and preceding an on portion <NUM> of a DRX cycle according to an example implementation. As shown in <FIG>, the windows <NUM> include a Window A, Window B, and Window C. In some implementations, there may be more windows or simply one or two windows. Also as shown in <FIG>, there is an X offset that corresponds to a full window preceding the on portion <NUM> of the DRX cycle. Each window is defined such that the end of that window and the start of the on portion <NUM> of the DRX cycle is equal to or greater than a minimum time needed for an adaptation operation associated with that window, requiring a maximum application latency.

As shown in <FIG>, Window A is associated with a UE-specific DCI format which may trigger BWP switching, CSI-RS measurement and reporting, TRS triggering, and a trigger to start monitoring during the on portion <NUM> of the DRX cycle. Window A has a shorter duration than the full window and there would be time gap between end of Window A and start of the on portion <NUM> of the DRX cycle according to the longest application latency among associated triggering commands.

As shown in <FIG>, Window B is associated with the TRS triggering and the trigger to start monitoring during the on portion <NUM> of the DRX cycle. Window B has a shorter duration than the full window and there would be time gap between end of Window B and start of the on portion <NUM> of the DRX cycle according to the longest application latency among associated triggering commands. Further, Window B has a duration longer than that of Window A. Accordingly, some trigger command such as those for BWP switching and CSI-RS measurement and reporting may not be valid in time slots within Window B because the time outside of Window B within the X offset may not be sufficient to perform the adaptation operations corresponding to those trigger commands.

As shown in <FIG>, Window C is associated with the trigger to start monitoring during the on portion <NUM> of the DRX cycle. Window C is associated with the full window such that there are no time slots between Window C and the on portion <NUM> of the DRX cycle. Accordingly, all trigger commands except the trigger to start monitoring during the on portion <NUM> of the DRX cycle may not be valid in Window C.

In some implementations, there are other windows corresponding to other trigger commands for adaptation operations.

In some implementations, if the UE receives a triggering command (e.g., DCI format) including fields that are associated with a window has already ended before the next on portion of the DRX cycle, the UE ignores those fields and assume that those parameters values describing the DRX are unchanged or have some predefined value.

In some implementations, there is an overlap duration (e.g., a number of time slots) between a beginning of a first window (e.g., Window A) and a beginning of a second window (e.g., Window C).

In some implementations, there is a common full window. Based on a detected triggering command time, it can be determined when the UE is assumed to be ready to monitor PDCCHs within the on portion <NUM> of the DRX cycle.

In some implementations, a window duration and/or possible triggering commands is based on the applied DRX cycle. In other words, while in a short DRX cycle there may only be a short Window C just before the on portion <NUM> of the DRX cycle (i.e., to be able to trigger only PDCCH monitoring for the on portion <NUM>). Alternatively, in a long DRX cycle, all trigger commands may be valid.

In some implementations, a window duration and/or possible triggering commands is based on events that may occur before the start of the on portion <NUM> of the DRX cycle. For example, an offset X1 and window duration W1 may be used for a long DRX cycle' that is, the offset X1 is far away from the on portion <NUM> of the DRX cycle to allow all adaptation operations be ready before the on portion <NUM>. The adaptation operations may include the BWP switch, an A-CSI trigger, an A-TRS trigger, and PDCCH monitoring within the on portion <NUM> of the DRX cycle. In another example, an offset X2 and window duration W2 may be used for short DRX cycle, e.g., very close to the on portion <NUM> of the DRX cycle. The adaptation operations allowed here may include the A-TRS trigger and PDCCH monitoring within the on portion <NUM> of the DRX cycle.

<FIG> is a block diagram of a wireless station (e.g., AP, BS, eNB, UE or user device) <NUM> according to an example implementation. The wireless station <NUM> may include, for example, one or two RF (radio frequency) or wireless transceivers 602A, 602B, where each wireless transceiver includes a transmitter to transmit signals and a receiver to receive signals. The wireless station also includes a processor or control unit/entity (controller) <NUM> to execute instructions or software and control transmission and receptions of signals, and a memory <NUM> to store data and/or instructions.

Processor <NUM> may also make decisions or determinations, generate frames, packets or messages for transmission, decode received frames or messages for further processing, and other tasks or functions described herein. Processor <NUM>, which may be a baseband processor, for example, may generate messages, packets, frames or other signals for transmission via wireless transceiver <NUM> (602A or 602B). Processor <NUM> may control transmission of signals or messages over a wireless network, and may control the reception of signals or messages, etc., via a wireless network (e.g., after being down-converted by wireless transceiver <NUM>, for example). Processor <NUM> may be programmable and capable of executing software or other instructions stored in memory or on other computer media to perform the various tasks and functions described above, such as one or more of the tasks or methods described above. Processor <NUM> may be (or may include), for example, hardware, programmable logic, a programmable processor that executes software or firmware, and/or any combination of these. Using other terminology, processor <NUM> and transceiver <NUM> together may be considered as a wireless transmitter/receiver system, for example.

According to another example implementation, RF or wireless transceiver(s) 602A/602B may receive signals or data and/or transmit or send signals or data. Processor <NUM> (and possibly transceivers 602A/602B) may control the RF or wireless transceiver 602A or 602B to receive, send, broadcast or transmit signals or data.

The embodiments are not, however, restricted to the system that is given as an example, but a person skilled in the art may apply the solution to other communication systems. Another example of a suitable communications system is the <NUM> concept. It is assumed that network architecture in <NUM> will be quite similar to that of the LTE-advanced. <NUM> is likely to use multiple input - multiple output (MIMO) antennas, many more base stations or nodes than the LTE (a so-called small cell concept), including macro sites operating in co-operation with smaller stations and perhaps also employing a variety of radio technologies for better coverage and enhanced data rates.

It should be appreciated that future networks will most probably utilise network functions virtualization (NFV) which is a network architecture concept that proposes virtualizing network node functions into "building blocks" or entities that may be operationally connected or linked together to provide services. A virtualized network function (VNF) may comprise one or more virtual machines running computer program codes using standard or general type servers instead of customized hardware. Cloud computing or data storage may also be utilized. In radio communications this may mean node operations may be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head.

Implementations of the various techniques described herein may be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. Implementations may be implemented as a computer program product, i.e., a computer program tangibly embodied in an information carrier, e.g., in a machine-readable storage device or in a propagated signal, for execution by, or to control the operation of, a data processing apparatus, e.g., a programmable processor, a computer, or multiple computers. Implementations may also be provided on a computer readable medium or computer readable storage medium, which may be a non-transitory medium. Implementations of the various techniques may also include implementations provided via transitory signals or media, and/or programs and/or software implementations that are downloadable via the Internet or other network(s), either wired networks and/or wireless networks. In addition, implementations may be provided via machine type communications (MTC), and also via an Internet of Things (IoT).

Furthermore, implementations of the various techniques described herein may use a cyber-physical system (CPS) (a system of collaborating computational elements controlling physical entities). CPS may enable the implementation and exploitation of massive amounts of interconnected ICT devices (sensors, actuators, processors, microcontrollers,. ) embedded in physical objects at different locations. The rise in popularity of smartphones has increased interest in the area of mobile cyber-physical systems. Therefore, various implementations of techniques described herein may be provided via one or more of these technologies.

To provide for interaction with a user, implementations may be implemented on a computer having a display device, e.g., a cathode ray tube (CRT) or liquid crystal display (LCD) monitor, for displaying information to the user and a user interface, such as a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer.

Claim 1:
A method, comprising:
receiving, by controlling circuitry of a user equipment, configuration data representing (i) an offset from a start of an on portion of a discontinuous reception cycle including the on portion and an off portion, the offset being a specified number of time slots, (ii) identifiers of a plurality of triggering commands for adaptation operations that are active for the user equipment, and (iii) a plurality of windows, each of the plurality of windows having a specified duration within the offset and being associated with a respective subset of the triggering commands and a respective downlink control information format;
performing a monitoring operation over physical downlink control channels to determine whether a physical downlink control channel having a downlink control information format with which at least one of the plurality of windows is associated is present; and
in response to detecting a physical downlink control channel having the downlink control information format, performing an adaptation operation according to triggering commands of the plurality of triggering commands with which the at least one of the plurality of windows is associated.