Power saving mechanism in nr

Abstract

The invention relates to a power saving mechanism in NR. Methods, systems, and devices may help power savings in new radios. For example, power savings are enabled during a connected mode discontinuous reception period of the RRCCONNECTED state of the user equipment.

Description

[0001] This application is a divisional application of the invention patent application with application date of July 17, 2019, application number 201980063605.6, and titled “Power Saving Mechanism in NR”.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This application claims the benefit of U.S. Provisional Patent Application No. 62 / 737,266, filed on September 27, 2018, entitled “Power Saving Mechanisms In NR,” and U.S. Provisional Patent Application No. 62 / 825,226, filed on March 28, 2019, entitled “Power Saving Mechanisms In NR,” the contents of each of which are incorporated herein by reference in their entirety. Background Art

[0004] Connected Mode Discontinuous Reception (CDRX) Cycle in 3GPP LTE Release 15 and 3GPP NR Release 15: In 3GPP LTE, the UE wakes up and resynchronizes to the signal before the ON Duration of the CDRX cycle to be ready to receive the grant. The OnDuration is configured to the UE through RRC. The UE monitors the PDCCH in each time slot. If no grant is received during the time slot or no transmission is necessary, the UE can sleep during the remaining codewords of the time slot. Similarly, in 3GPP NR Release 15, the UE monitors the PDCCH at the configured monitoring occasions in the DRX ON state. It can go to sleep during other codewords. But in both systems, the UE must monitor the PDCCH at the next opportunity within the ON Duration and the duration of the DrxInactivityTimer; therefore, the micro-sleep is short.

[0005] Power saving mechanisms in 3GPP NR Release 15: 3GPP NR Release 15 introduces some tools for improving power utilization at the UE. For example, adaptation of UE operation between narrow and wide BWP enables the UE to receive PDCCH in narrow CORESET and save power, but dynamically receive PDSCH / PUSCH in wide BWP and return to narrow BWP when it does not have a grant.

[0006] Another feature called cross-slot scheduling allows a UE to receive a PDCCH grant in one slot but have granted resources in another slot; this allows the UE more processing time and can reduce its power usage compared to same-slot scheduling. Summary of the invention

[0007] In the following discussion, a signal for sending a UE to micro-sleep may be referred to as a go to sleep (GTS) signal. A signal for waking up a UE in sleep mode is referred to as a wake-up signal. In the remaining discussion, the wake-up and GTS signals are referred to as power saving signals. Although specific examples may apply to either the wake-up signal or the GTS, a solution applicable to one signal may also apply to the other signal.

[0008] This article discloses methods, systems and devices that can assist power saving in NR. The system enables power saving during the CDRX period of the UE's RRC_CONNECTED state and when monitoring paging occasions during RRC_IDLE and INACTIVE states. The following is an example:

[0009] The UE may enter a micro-sleep state for an extended duration in a CDRX cycle. In the micro-sleep state, the UE may not monitor the PDCCH during the OnDuration. In the micro-sleep state, when the DrxInactivityTimer has not expired, the UE may not monitor the PDCCH.

[0010] Micro-sleep may mean a low power state with minimal monitoring on a narrow BWP. The UE may monitor PDCCH or triggers on a narrow BWP. The UE may process granted resources (receive PDSCH / transmit PUSCH) on a wide BWP. After processing granted resources, the UE may default back to the narrow BWP.

[0011] The UE may set a microsleepTimer and decrement it during its microsleep. When the timer expires, the UE may return to a wide BWP.

[0012] The UE may have a semi-static configuration of a micro-sleep duration during which the UE does not need to monitor its PDCCH monitoring opportunities. The UE has a valid monitoring window when it monitors the PDCCH. The UE has a micro-sleep window when it is in micro-sleep. The UE has alternating valid monitoring windows and micro-sleep windows. Sleep / wake-up does not require explicit indication.

[0013] The UE may be configured through RRC to micro-sleep for the duration between the DCI giving the grant and its granted resources.

[0014] The UE may be configured through RRC to micro-sleep for a fixed duration after granted resources (for PDSCH / PUSCH).

[0015] The UE receives a dynamic indication of the micro-sleep duration via the power signal PDCCH (such as via RNTI or PDCCH resource location).

[0016] The UE is activated by a micro-sleep BWP, in which the UE can micro-sleep until the bwpInactivitytimer expires.

[0017] A UE may have multiple micro-sleep BWPs to support different sleep durations.

[0018] The UE may enter a micro-sleep BWP in one of the following ways: 1) through an activation DCI for the micro-sleep BWP; 2) upon expiration of the BWPInactivityTimer for a wider BWP; or 3) upon completion of processing the granted resources (PUSCH / PDSCH).

[0019] If the PDCCH position or aggregation level in a CORESET is fixed for a certain duration, the UE can reduce blind decoding.

[0020] Micro-sleep can be indicated as a time slot format through DCI. It can be indicated through a group-common PDCCH or a UE-specific DCI.

[0021] Power saving signals, such as go to sleep (GTS) signals or wake-up signals, may be indicated via GC-PDCCH or UE-specific PDCCH. Depending on the content of its payload, a single DCI may be used to indicate either wake-up or GTS status. Alternatively, a DCI with one format may be used to signal GTS and another format may be used to indicate wake-up status.

[0022] The wake-up signal may occur before the OnDuration of the DRX cycle in the Pre-OnDuration Window (POW) whose monitoring period is configured to the UE.

[0023] The wake-up signal may occur during the OnDuration period of the DRX cycle or during the active time of the DRX cycle.

[0024] The UE may perform aperiodic reporting or synchronization between POW and DRX OnDuration.

[0025] The power saving signal may provide activation or deactivation of certain CORESET or search space or dynamic DRX parameters.

[0026] The DMRS in the grant may be used as a GTS signal. The change in DMRS configuration may indicate the last grant after which the UE may micro-sleep during the DRXInactivtyTimer.

[0027] The power saving signal may indicate the BWP that the UE must wake up and perform monitoring during the OnDuration period.

[0028] Multiple power saving states (PSCs) may be configured for a UE. The active PSC may be indicated to the UE via RRC or MAC CE or L1 signaling (such as a wake-up signal). The PSC may define a set of BWPs, may be a DRX parameter according to the BWP, may be a TDRA table according to the BWP, etc.

[0029] If different minimum K0 values ​​are configured for BWP1 and BWP2 and the UE has to switch from one BWP1 to BWP2, it uses the K0 value defined according to the TDRA for BWP1 for the first grant in BWP2.

[0030] A default PSCD may be defined for the UE. After the timer expires, the UE switches from the non-default PSC PSC1 to the PSCD.

[0031] For power saving, the UE may monitor the SCell in a "sleep state" with minimal or no PDCCH monitoring. The UE may transition its monitoring of the SCell to an activated state or a deactivated state using RRC or MAC CE based commands or L1 signaling, which may be received on the SCell or another cell (such as a PCell or PSCell or another SCell).

[0032] When the timer set in the active state expires, the UE may transition from the active state to the dormant state.

[0033] When a timer set in the dormant state expires, the UE may transition from the dormant state to the deactivated state.

[0034] When the UE sends an SR, the UE autonomously activates dormant state cells. The number of cells activated and the identities of the activated cells may depend on the type of services that the UE must support and the BSR of the UE.

[0035] The UE may report autonomously activated cells to the gNB. Alternatively, the gNB may pre-configure the S SCells to be activated for a given BSR value.

[0036] The UE can bundle S cells together so that a certain behavior on one cell triggers a certain behavior on another cell in the bundle. For example, a power saving signal can cause the PCell to enter micro-sleep. This triggers the SCell in the bundle (with the PCell) to also enter micro-sleep.

[0037] A wake-up signal on one cell may trigger a dormant-to-active transition on the bundled cells.

[0038] A wake-up signal on one cell may trigger a deactivation-to-dormant state transition on the bundled cells.

[0039] A GTS on one cell may trigger a dormant to deactivated state transition on the bundled cells.

[0040] GTS on one cell can trigger micro-sleep on the bundled cells.

[0041] A GTS on one cell may trigger an active-to-dormant state transition on the bundled cells.

[0042] BWP switching on one cell can trigger corresponding BWP switching on the bundled cells.

[0043] The activation of a PSC on one cell may trigger the activation of the corresponding PSC on the bundled cell.

[0044] UE-specific paging DCI may be used to reduce false paging alarms, where the DCI payload carries some bits of the UE ID and the DCI is scrambled with other bits of the UE ID.

[0045] A wake-up or signal GTS such as OOK may be used to indicate whether the UE must wake up or go to sleep at the start of a paging occasion.

[0046] Multiple paging RNTIs may be introduced so that a UE ID is mapped to one or more paging RNTIs. If a UE receives a paging DCI scrambled with one of the paging RNTIs, it monitors the paging PDSCH.

[0047] This article discloses methods, systems and devices that can help deactivate and activate SCells from a dormant state.

[0048] Disclosed herein are methods, systems, and devices that can help achieve bundling operations across multiple cells.

[0049] Disclosed herein are methods, systems, and devices that can help achieve power savings in IDLE and INACTIVE states.

[0050] This summary is provided to introduce some concepts in a simplified form, which will be further described in the detailed description below. This summary is neither intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. Furthermore, the claimed subject matter is not limited to limitations that address any or all disadvantages noted in any part of this disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] A more detailed understanding may be obtained from the following description, which is given by way of example in conjunction with the accompanying drawings, in which:

[0052] Figure 1Aillustrates an exemplary micro sleep mode in a UE - legacy system;

[0053] Figure 1B illustrates an exemplary micro-sleep mode in a UE - the disclosed extended sleep by skipping certain monitoring opportunities;

[0054] Figure 2A An exemplary microsleep with minimal monitoring is shown - in BWP D Upper monitoring for BWP W activation;

[0055] Figure 2B illustrates an exemplary micro-sleep with minimal monitoring - sleep and wakeup via aperiodic CSI-RS trigger;

[0056] Figure 2C illustrates an exemplary microsleep with minimal monitoring - waking up when microSleepTimer expires;

[0057] Figure 3A illustrates an exemplary monitoring periodicity for an NR Release 15 UE;

[0058] Figure 3B illustrates exemplary disclosed monitoring utilizing a micro-sleep window and an active monitoring window;

[0059] Figure 4A illustrates an exemplary micro-sleep-DCI based on the reception of a grant and no PDCCH monitoring between the granted resources;

[0060] Figure 4B An exemplary micro-sleep for grant-based reception is illustrated - no PDCCH monitoring in 2 slots after the granted resource;

[0061] Figure 4C An exemplary micro-sleep for grant-based reception is illustrated - no PDCCH monitoring for C opportunities after the DCI providing the grant;

[0062] Figure 4D illustrates an exemplary micro-sleep for grant-based reception - no PDCCH monitoring in a DRX cycle after the indication of the last PDSCH in the DRX cycle;

[0063] Figure 5 An exemplary dynamic indication of microsleep duration is illustrated;

[0064] Fig. 6A An exemplary indication of micro-sleep duration - offset from PDCCH monitoring opportunity is illustrated;

[0065] Figure 6BAn exemplary indication of micro-sleep duration is illustrated - offset from the start of the granted resource;

[0066] Fig. 7A Diagram showing micro sleep BWP, BWP through DCI MS,m Example activation of the UE when exiting the BWP MS,m Switch to BWP D ;

[0067] Figure 7B Diagram showing micro sleep BWP, BWP through DCI MS,m Example activation of the UE when exiting the BWP MS,m Return to BWP W ;

[0068] Figure 8 The diagram shows the W The BWPInactivityTimer expires when the BWP microsleeps. MS,m Exemplary activation of; UE exits BWP MS,m Return to BWP D ;

[0069] Fig. 9 The diagram shows the micro-sleep BWP when completing the processing of the granted resources (PDSCH / PUSCH), BWP MS,m Exemplary activation of; UE exits BWP MS,m Return to BWP W ;

[0070] Fig.10 An example of reducing blind decoding assumptions by having the same PDCCH AL and PDCCH position L within time Δt is illustrated;

[0071] Fig.11 illustrates an exemplary display that may be generated based on methods, systems, and devices for power conservation in NR;

[0072] Fig. 12A illustrates an exemplary PDCCH as a wake-up signal for the first monitoring occasion in OnDuration - behavior of the UE upon receiving the PDCCH;

[0073] Fig. 12B illustrates an exemplary PDCCH as a wake-up signal for the first monitoring occasion in OnDuration - behavior of the UE when no PDCCH is received;

[0074] Fig.13A illustrates an exemplary monitoring of power saving signals in POW - monitoring default BWP and switching to active BWP;

[0075] Fig. 13B illustrates an exemplary monitoring of power saving signals in POW - monitoring in active BWP;

[0076] Fig.14A The diagram shows that the UE performs aperiodic CSI reporting after receiving a wake-up signal;

[0077] Fig. 14B An exemplary method associated with a UE performing aperiodic CSI reporting is illustrated;

[0078] Fig. 14C Another exemplary method associated with a UE performing aperiodic CSI reporting is illustrated;

[0079] Fig.15A illustrates an exemplary power saving signal triggering a CSI report before ONDuration - CSI report after POW;

[0080] Fig. 15B illustrates an exemplary power saving signal triggering a CSI report before ONDuration - CSI reporting within POW;

[0081] Fig.16 An exemplary default PSC, PSC D and PSC1 is the PSC configured for the UE;

[0082] Fig.17 An exemplary cross-slot schedule is illustrated;

[0083] Fig.18 An exemplary same-slot scheduling is illustrated, where the PUSCH start position starts after PDCCH decoding is completed;

[0084] Fig.19A An exemplary PSC indication is shown - from the PSC D Switch to PSC1;

[0085] Fig.19B Illustrated example PSC indication - switch to PSC after pscValidTimer expires D ;

[0086] Fig. 20 An exemplary BWP-based PSC switching is illustrated;

[0087] Fig.21A An exemplary switch to a default BWP in an active state is illustrated;

[0088] Fig. 21B illustrates an exemplary SCell activation from a dormant state - (B) switching to an active BWP in an active state;

[0089] Fig. 22 illustrates an exemplary UE procedure for switching a cell from active to dormant using activeTodormancyTimer;

[0090] Fig.23 An exemplary process of switching a UE from a dormant state to a deactivated state is illustrated;

[0091] Fig.24 An exemplary UE is illustrated with two bundles of configured cells - one bundle with a PCell and with a PSCell;

[0092] Fig.25 An exemplary correspondence relationship between the PSCs of the PCell and the bundled SCell is shown;

[0093] Fig.26 It is illustrated that an exemplary cell may be included in multiple bundles;

[0094] Fig. 27 An exemplary BWP switching in PCell triggers BWP switching in SCell is illustrated;

[0095] Fig.28 An exemplary process for a UE to activate bundling of cells is illustrated;

[0096] Fig.29 An exemplary UE-specific paging DCI without PDSCH is illustrated. The DCI is scrambled with part of the UE's ID, and the rest of the UE ID is in the payload of the DCI;

[0097] Fig.30 illustrates an exemplary UE-specific paging DCI that also provides a PDSCH grant to the UE;

[0098] Fig.31 illustrates an exemplary UE monitoring R1-RNTI, P2-RNTI and P4-RNTI in a pool of paging RNTIs;

[0099] Fig.32A An exemplary communication system is illustrated;

[0100] Fig.32B An exemplary system including a RAN and a core network is illustrated;

[0101] Fig.32C An exemplary system including a RAN and a core network is illustrated;

[0102] Fig.32D An exemplary system including a RAN and a core network is illustrated;

[0103] Fig.32E Another example communication system is illustrated;

[0104] Fig.32F is a block diagram of an example apparatus or device, such as a WTRU;

[0105] Figure 32G is a block diagram of an exemplary computing system;

[0106] Fig.33 illustrates exemplary displays that may be generated based on the methods, systems, and devices herein;

[0107] Fig.34A An exemplary method for sleeping or waking up after monitoring the OnDuration front window is illustrated, such as the UE waking up after detecting a wake-up signal and otherwise sleeping;

[0108] Fig.34B An exemplary method for sleeping or waking up after monitoring the OnDuration front window is illustrated, such as the UE sleeping after detecting a GTS signal; otherwise waking up for onduration;

[0109] Fig.34C An exemplary method for sleeping or waking up after monitoring the OnDuration front window is illustrated, such as the UE waking up if neither a GTS nor a wake-up signal is detected, or using a default power saving configuration;

[0110] Fig.35 illustrates an exemplary DRXInactivityTimer running during the OnDuration pre-window duration;

[0111] Fig.36A An exemplary method for running the activity period to a window before monitoring OnDuration is illustrated, such as even if DRXInactivityTimer expires before OnDuration, the UE monitors the next OnDuration;

[0112] Fig.36B An exemplary method for running an activity time period to monitor the window before OnDuration is illustrated, such as if DRXInactivityTimer expires before OnDuration, the UE sleeps at the beginning of the next OnDuration;

[0113] Fig.37 An exemplary method is illustrated for when an activity period enters a monitoring OnDuration pre-window, such as when a UE receives a power save signal during an activity duration;

[0114] Fig.38AAn exemplary method for receiving a GTS during an activity duration is illustrated, such as when the UE sleeps for a period of time and wakes up during an active session to continue monitoring;

[0115] Fig.38B An exemplary method for receiving a GTS in an Active Duration is illustrated, such as when the Active Duration of the UE terminates and the UE sleeps and the UE wakes up to monitor the next POW at the next OnDuration;

[0116] Fig.39 Exemplary fields and locations of fields within a DCI are illustrated. DETAILED DESCRIPTION

[0117] Micro-sleep extension issue in RRC_CONNECTED state. It has been determined that consecutive UL grants, consecutive DL grants and consecutive UL-DL or consecutive DL-UL grants usually occur sparsely. The average duration between 2 UL grants is 10ms, the average duration between 2 DL grants is 14ms and the average duration between UL-DL grants is 6ms. NR should consider ways to extend the micro-sleep duration during CDRX in the RRC-CONNECTED state of the UE by utilizing the duration between consecutive scheduling. It is well known that PDCCH monitoring contributes significantly to baseband power consumption. The frequency of monitoring, the number of assumptions for blind decoding and the bandwidth of the CORESET are all contributing factors. NR should consider ways to quickly adapt PDCCH monitoring to the traffic conditions to enable efficient micro-sleep.

[0118] Power saving problem on SCell. Under normal circumstances, the power consumption of UE on SCell can be significant in the state of SCell activation. Since the activation and deactivation of SCell occurs through MAC CE, it is not dynamic and is a relatively slow process, taking tens of milliseconds. It is desirable to make the activation and deactivation more dynamic so that the UE can quickly adapt its power consumption to the traffic load. Therefore, any method to address the power consumption during monitoring on SCell is disclosed herein.

[0119] Power consumption issues during paging. Conventionally, in IDLE and INACTIVE states, the UE can perform cell measurements and monitor paging DCI. When monitoring paging DCI, the UE can monitor multiple beams (if it can receive multiple beams). If there is no paging DCI, it can go to sleep. If there is a paging DCI, it decodes the PDSCH to see if it has been paged. If it has not been paged, for example it is a false paging alarm, it can go to sleep. In heavily loaded cells, the false paging alarm rate can be high and can contribute to significant power consumption of the UE. Monitoring paging DCI during paging occasions is also a factor in UE power consumption in the IDLE state.

[0120] This document discloses a micro-sleep extension in the RRC_CONNECTED state. The gNB may introduce a "micro-sleep" state in the CDRX cycle of the RRC_CONNECTED state; micro-sleep may occur during the OnDuration period or when the DrxInactivityTimer has not expired. The UE may micro-sleep during the time when no grant is received. For example, the UE may micro-sleep in the last few slots of the DrxInactivityTimer duration or during the PDCCH monitoring opportunity between two consecutive grants. Micro-sleep enables the UE to shut down various components of its modem (RF, baseband, and various power islands) and achieve power savings.

[0121] Unlike legacy systems such as LTE and NR Release 15, the present disclosure enables the UE to skip monitoring of certain configured monitoring occasions during CDRX. Figure 1A An example of micro-sleep in LTE and NR Release 15 is shown; the UE has a CDRXOnDuration during which the UE receives a grant and sets a DrxInactivtyTimer on it and starts decrementing. If the DrxInactivtyTimer has not expired, the UE monitors each monitoring opportunity configured for it. After receiving the grant, it resets the timer. If the UE is not granted or does not have to transmit PUCCH / SRS or process CSI-RS, it can micro-sleep during those symbols of the timeslot. The power profile of the UE is shown in the figure; the UE monitors the PDCCH on every timeslot for the duration of OnDuration and DrxInactivtyTimer. Even if there is no traffic on several timeslots during the OnDuration or DrxInactivtyTimer duration, the UE must wake up to monitor the PDCCH.

[0122] Figure 1BAn example of a timeline and power consumption of a UE in micro-sleep disclosed herein is shown; during the duration of DrxInactivtyTimer, the UE has an extended micro-sleep across multiple time slots, for example, it skips some monitoring opportunities. By waking up at each monitoring opportunity that is not within the CRDX duration, the UE saves more power. The degree of power savings in micro-sleep can vary depending on the duration of the micro-sleep, the frequency of ramp-up, the functions performed during ramp-up (such as resynchronization), etc.

[0123] Micro-sleep with minimal monitoring: A micro-sleep state may be defined to support minimal monitoring, e.g., the UE monitors some signals in a low power state. The UE may be equipped with dedicated low power state hardware for low power state signal monitoring. The lower power state signal (or equivalent micro-sleep indication) may be a binary state signal that indicates to the UE whether it is in a micro-sleep state; the frequency resource used for this signal may be a "thin" BWP, which may be significantly narrower than the initial BWP or the default BWP.

[0124] Alternatively, minimal monitoring may occur in the form of PDCCH monitoring over a narrow BWP. Furthermore, the PDCCH monitoring period may be long to keep power consumption low. The UE may be configured to use specific PDCCH locations or specific aggregation levels (ALs) of the PDCCH to significantly reduce the number of blind decoding assumptions – this may be supported in low traffic mode if ample resources are available.

[0125] The UE may receive a DCI with a grant on a narrow BWP and switch to a wide BWP to receive / transmit on the granted resources, e.g., the DCI activates the wide BWP. After processing the granted resources (PUSCH / PDSCH), the UE may return to the narrow BWP to continue monitoring the PDCCH.

[0126] The concept is Figure 2A Here, microsleep occurs on a narrow BWP, which may be a default BWP and is referred to as BWP D The UE can monitor the PDCCH at a rate of once every two slots. When it receives a grant from the DCI, it switches to a mode called BWP. W The width of BWP. It is in BWP W After completion, the UE returns to the BWP. D Therefore, when the UE switches back to BWP D It can not wait to deactivate DCI or wait for bwpInactivitytimer in BWP W On expiration.

[0127] Alternatively, the UE may monitor the DL preamble or aperiodic CSI-RS or aperiodic TRS triggered by DCI. Upon receiving this signal or trigger, the UE may enter micro-sleep or wake up. If a trigger based on aperiodic CSI-RS is used, the following process may be applied: First, the sequence of aperiodic CSI-RS indicates that the UE should sleep and the duration of the sleep. Second, the sequence of CSI-RS indicates that the UE should wake up in a specific BWP. Third, upon receiving a DCI trigger for aperiodic CSI-RS, the UE may sleep; it does not need to receive an aperiodic CSI-RS signal. In fact, the gNB may transmit only the triggering DCI without transmitting the aperiodic CSI-RS. In addition, the UE may not need to transmit an aperiodic CSI-RS report for this trigger. Fourth, the trigger for waking up the UE may be in the form of an aperiodic tracking reference signal (TRS). Upon waking up, the UE may use the aperiodic TRS to regain fine timing and frequency.

[0128] The gNB can configure the UE through RRC to indicate the sequence for micro-sleep and sleep duration, the sequence for wake-up, or the corresponding transmission resources. However, the indication of micro-sleep or wake-up can be dynamically generated by a non-periodic CSI-RS trigger or other (one or more) physical layer control signals. This concept is Figure 2B UE can be in BWP W The UE receives an aperiodic CSI-RS trigger indicating that it has micro-slept for a period of time. Therefore, the UE can switch to BWP with minimal monitoring D It periodically monitors the PDCCH for a wake-up trigger that provides an aperiodic TRS. When the UE receives a trigger, it can switch back to BWP. W And use aperiodic TRS to fine-tune its timing and frequency. In this scenario, the UE can rely on explicit wake-up signals to wake up.

[0129] As an alternative, the UE may run a timer microSleepTimer for a specific duration. It sets the timer to the value configured via RRC, and the function of the triggered aperiodic CSI-RS. It may decrement the timer until it expires. At expiration, the UE may wake up. The UE may monitor the BWP while awake W or BWP D This concept is Figure 2C Here, the aperiodic CSI-RS sequence is tied to a certain microSleepTimer duration, which is configured to the UE via RRC. Depending on the indicated CSI-RS, the UE sets the microSleepTimer. It can wake up to monitor the BWP W.

[0130] Alternatively, the UE uses dedicated low power state hardware to monitor the micro-sleep signal in each PDCCH monitoring opportunity during the time including the time when the on duration timer is running or the inactivity timer is running or other active time period. If the micro-sleep signal bit is set to micro-sleep, the UE can perform micro-sleep between PDCCH monitoring opportunities.

[0131] Adapting micro-sleep by changing the monitoring period: One way to adapt micro-sleep to traffic patterns is by adapting the PDCCH monitoring occasions, e.g. the UE does not need to monitor certain occasions where it will not receive grants. The search space monitoring periodicity can be updated based on traffic; it can be configured to be more sparse, but this reduces the scheduling flexibility of the gNB. Alternatively, if the UE supports normal monitoring periodicity when grants may occur, the gNB has more flexibility and therefore the opportunity for finer granularity for the gNB to transmit DCI.

[0132] Semi-static configuration of micro-sleep: The gNB can semi-statically configure micro-sleep parameters for the UE. Micro-sleep for Mms is supported, called sleep window. The UE can enter micro-sleep in the sleep window. This is followed by PDCCH monitoring within a monitoring window of Wms, called valid monitoring window, for example, the UE can expect to receive PDCCH if a grant is provided within the valid monitoring window. The sleep window and the valid monitoring window are alternated for the UE. This operation can be applied especially in light traffic conditions, when resources are not scarce and the gNB has the flexibility to manage the occurrence of the next PDCCH for the UE. This concept is discussed in Figure 3A and Figure 3B UE not configured for micro-sleep has Figure 3A For example, the UE monitors each configured PDCCH monitoring opportunity with a periodicity of 1 time slot. The UE configured with a sleep window and an effective monitoring window has the following Figure 3B The micro-sleep window is a mask applied to the monitoring opportunities in the search space; it masks certain opportunities from being monitored, allowing the UE to micro-sleep and save power.

[0133] Grant-based micro-sleep behavior: In addition, UE behavior can be defined to support micro-sleep between the PDCCH giving the grant and the occurrence time of the granted resources. This can be applied to the scenario of cross-slot grants with K0>0. This concept is in Figure 4A , where the UE receives a grant with K0 = 2. The UE does not monitor the PDCCH opportunities between the DCI and the granted resources.

[0134] Figure 4BAnother UE behavior is shown, where the UE may micro-sleep for a duration of Mms immediately following the granted resources. Here M=2ms; the UE does not monitor the PDCCH opportunity in the 2 slots following the granted resources. After Mms, the UE wakes up without an additional wake-up indication and continues to monitor the PDCCH. These behaviors may be configured to the UE via RRC using a flag (or other indicator) indicating whether the UE must follow such a micro-sleep procedure.

[0135] As Figure 4A As another alternative to the situation described in , the UE may skip monitoring C PDCCH monitoring opportunities after detecting a DCI carrying a valid non-zero grant for it, or may skip monitoring PDCCH opportunities in S time slots after detecting a DCI carrying a valid non-zero grant for it. The value of C or S may be configured to the UE by RRC. This concept is described in Figure 4C , where the UE receives a cross-slot grant with K0=3 and C=2; therefore, the UE is not required to monitor the PDCCH in 2 slots after the DCI. This allows the UE to wake up from micro-sleep just in time to receive the PDCCH and PDSCH that appear together in slot #3.

[0136] The DMRS in the PDSCH can be used to indicate the potential last transmission in the C-DRX cycle so that the UE can sleep if it successfully decodes it; in this case, the UE can micro-sleep for the remainder of the DRX cycle even if the DRXInactivityTimer has not expired. The UE can wake up to start monitoring on the next DRX cycle. The DMRS can indicate the last transmission in the following ways. In the first way, the maximum number of front-loaded DM-RS codewords for PDSCH can be configured for the UE as maxLength=2. The scheduling DCI dynamically indicates the number of front-loaded DMRS codewords through the DCI field. Disclosed herein is a UE process so that when the DCI indicates the value of the number of front-loaded DMRS codewords as "numFLDMRS", the UE can assume that it is the last transmission in this C-DRX cycle. The parameter numFLDMRS can be configured to the UE via RRC signaling. For example, this operating mode can only be used when the UE configures the RRC parameter powerSavingsThroughDMRS through RRC signaling. In another way, if the number of front-loaded DMRS symbols changes between two consecutive grants, the UE may read the indication of sleeping until the start of the next DRX cycle, e.g. Figure 4D shown.

[0137] Dynamic micro-sleep indication: The gNB can dynamically indicate the micro-sleep duration to the UE. The dynamic indication can be derived from the following signal examples. In the first example, the RNTI of the PDCCH can be masked with a sequence indicating the micro-sleep window duration. The UE can decode the DCI with a candidate mask. If the DCI is successfully decoded, the candidate mask is used to determine the micro-sleep duration. The mask and the corresponding micro-sleep duration can be configured to the UE through RRC. This configuration can be cell-specific as all UEs can be configured simultaneously with the same set of masks. In the second example, the starting position of the resources of the PDCCH can indicate the micro-sleep window parameters. The gNB can have more flexibility to support this in light traffic conditions.

[0138] The process for dynamic indication is described below and in Figure 5 The UE dynamically receives an indication of a microsleep for a certain duration. The UE then wakes up and continues to monitor the PDCCH. If the UE misses the opportunity to decode the PDCCH, it may not enter the microsleep. In addition to the microsleep duration, the parameters associated with the indication may be as follows: Fig. 6A or Figure 6B First, the offset from the PDCCH monitoring opportunity to the micro-sleep duration is as follows: Fig. 6A The offset can be with respect to a time slot or a mini-time slot. Secondly, the offset from the start of the authorized resource is as follows Figure 6B The offset can be with respect to a time slot or a mini-time slot.

[0139] The dynamic indication of wake-up or micro-sleep may also provide activation or deactivation of a CORESET or search space for a certain duration. If a CORESET is activated, the UE may need to wake up to monitor it. If a CORESET is disabled, the UE may micro-sleep; then the UE does not need to monitor the CORESET and may micro-sleep when possible during the duration of the CORESET. There may be a field in the power saving signal (if it is a DCI) indicating the affected CORESET and its activation, deactivation status. If the UE has a single CORESET configured in the C-DRX ONDuration, one bit is sufficient to indicate its activation and deactivation.

[0140] If the UE supports both eMBB and URLLC services, it can be configured with a high periodicity search space to allow frequent monitoring of URLLC grants. If the gNB determines that the UE has no URLLC service in the short term, it can signal the UE to deactivate the search space. The CORESET and search space can be activated and deactivated by a wake-up signal or GTS on L1. UL or DL ​​grants can also be used to indicate the activation or deactivation of the CORESET or search space.

[0141] A field may be introduced in the DCI to provide authorization to indicate activation and deactivation of a CORESET or search space.

[0142] CORESET activation / deactivation and search space activation / deactivation may also be enabled through MAC CE.

[0143] Micro-sleep activation via "micro-sleep BWP": The UE can micro-sleep in a BWP with no resources - such a BWP is called a micro-sleep BWP. Activation of a micro-sleep BWP can be done via a DCI with a format such as 0_0 or 0_1 or 1_0 or 1_1 and scrambled with the UE's C-RNTI and by indicating the BWP ID (bwp-ID). Existing procedures for BWP can be used to put the UE into a micro-sleep state for the duration that the micro-sleep BWP is active. Upon switching to a micro-sleep BWP, the UE may set the timer BWPInactivityTimer to a value configured by the RRC and decrement the timer. Since this BWP does not allow any resources, there may be no CORESET to monitor; therefore, the UE may have extended micro-sleep for the duration of this timer. Note that a micro-sleep BWP may not be deactivated via DCI since there may be no resources in this BWP.

[0144] Multiple micro-sleep BWPs: M micro-sleep BWPs can be configured for a UE via RRC, each with a different value of BWPInactivityTimer; this can give the gNB the flexibility to schedule micro-sleeps of different durations for the UE based on traffic conditions, UE power sensitivity, user load, etc. Currently in NR, a single value of bwp-InactivityTimer is configured for all BWPs of a UE via RRC. However, different bwp-InactivityTimer values ​​are supported for the M micro-sleep BWPs. Therefore, the BWP information element can be given by the following, such as in Table 1.

[0145] Table 1 BWP information elements

[0146]

[0147]

[0148] The bwp-InactivityTimer parameter is configured in BWP-Uplink or BWP-Downlink for the BWP-Id corresponding to the micro-sleep BWP. This value may override the value used for the micro-sleep BWP in the ServingCellConfig information element.

[0149] UE procedures for operating in micro-sleep BWP: The switch to micro-sleep can be triggered by one of the following mechanisms, each of which is described in further detail herein: 1) By activating the BWP of the DCI MS,m Microsleep in BWP W When the BWPInactivityTimer on the BWP expires MS,m or 3) in the BWP after processing the authorized resources MS,m Microsleep in.

[0150] The term BWPg may be used to refer to the generic BWP of a UE. BWPg may be the default BWP D or wide BWP BWP W .

[0151] By activating the BWP of DCI MS,m Micro-sleep in: UE can be in the mth micro-sleep BWP, BWP MS,m BWP g The UE may enter a micro-sleep state and receive an activation DCI on the BWP. MS,m The BWPInactivityTimer can then be decremented. MS,m The UE receives a PDCCH to activate / deactivate the BWP, so the UE can remain in this state until the BWPInactivityTimer expires. Then, the UE can perform one of the following procedures. Fig. 7A In the first example process, when BWPInactivityTimer is in BWP MS,m When the time expires, the UE can switch to BWP D And the PDCCH on the default BWP can be monitored, which is like the minimum monitoring in micro-sleep. When the UE recognizes the bwp-ID as the ID of the micro-sleep BWP, the UE can ignore the resource allocation field in the activation DCI. This concept is Fig. 7A As shown in FIG. 1 , the UE monitors the BWP W PDCCH on and can be received with K0=0 for BWP MS,mTherefore, the UE can start micro-sleep in the same time slot, for example, switching to BWP MS,m and stays there until its BWPInactivityTimer expires. Upon expiration, the UE can switch to the BWP D In reference Figure 7B In the second example process, when BWPInactivityTimer is in BWP MS,m When the time expires, the UE can return to the BWP g The concept is Figure 7B As shown in FIG. 1 , the UE monitors the BWP W PDCCH on and receive with K0=0 for BWP MS,m Therefore, the UE can switch to BWP in the same time slot MS,m and may remain there until its BWPInactivityTimer expires. Upon expiration, the UE may return to the BWP W If the UE fails to decode the activation DCI, the consequences are not catastrophic; the UE may be stuck in the BWP rather than in a micro-sleep state. g In BWPInactivityTimer, the BWP MS,m Return to BWP after expiration g When , the UE may process the BWP in the following exemplary manner g In the first way, for BWP g Set BWPInactivityTimer and start it. In the second way, the UE can switch to BWP MS,m Save the value of BWPInactivityTimer at t g After a microsleep, when switching back to BWP g UE can set BWPInactivityTimer to t g In the third way, the UE can switch to BWP MS,m Save the value of BWPInactivityTimer at t g UE can switch back to BWP after micro-sleep g Set BWPInactivityTimer to t g -t elasped .t elasped Yes Switch to BWP MS,m and switch back to BWP g The total time that has passed between .

[0152] BWP WWhen the BWPInactivityTimer on the BWP expires MS,m Microsleep on: BWP W The UE's BWPInactivityTimer can trigger the UE to switch to BWP MS,m gNB can configure BWP MS,m For a given BWP W The concept is Figure 8 As shown in the figure, BWP W By BWP D The DCI on the BWP is activated to the UE. W When the UE's BWPInactivityTimer expires, the UE transitions to BWP MS,m Here, it is based on the MS,m The configuration sets the BWPInactivityTimer and starts it. When the timer expires, the UE can switch to the BWP D In this case, the dispatch can usually be done in BWP D but can occur at wider BWP W The resource that receives and processes authorization.

[0153] After processing the authorized resources BWP MS,m Micro-sleep in BWP: When the UE completes processing of PDSCH or PUSCH transmission, the UE can automatically switch to BWP MS,m gNB can configure BWP MS,m For a given BWP W The concept is Fig. 9 As shown in FIG. 1 , the UE completes the BWP W The UE can then automatically switch to the BWP MS,m When BWPInactivityTimer is in BWP MS,m When the previous value expires, the UE switches back to BWP W . Return to BWP W , the UE can handle BWPInactivityTimer in the following ways. In the first way, the UE can handle BWPInactivityTimer according to the W The configuration of the UE can set the BWPInactivityTimer and start it. In the second way, the UE can switch to BWP MS,m Save the value of BWPInactivityTimer at t g After a microsleep, when switching back to BWP W UE can set BWPInactivityTimer to t gIn the third way, the UE can switch to BWP MS,m Save the value of BWPInactivityTimer at t g After a microsleep, when switching back to BWP W UE can set BWPInactivityTimer to t g -t elapsed .t elapsed Yes Switch to BWP MS,m and switch back to BWP W The total time that has passed between .

[0154] BWP MS,m UE behavior during: In NR, when a specific BWP is activated, the UE must switch to it. However, this article discloses a process that may be more flexible for micro-sleep BWPs. The UE may consider the indication of switching as only a suggestion to switch to a micro-sleep BWP. MS,m When the UE switches to BWP, the UE may perform one of the following procedures. The first procedure may include: MS,m And keep micro sleep until its timer expires. The second process may include: UE in BWP MS,m Some or all of the duration of the timer remains in the current BWP (which may be the active BWP, such as BWP W or BWP D ). It can then continue execution if it has switched to BWP MS,m and exit BWP MS,m For example, even if the UE receives a request to switch to BWP MS,m The UE can also W The third process may include: the UE may switch to another BWP to perform CSI-RS measurement on the BWP. MS,m It can then continue to execute if it has switched to BWP MS,m and exit BWP MS,m The process that would have been executed.

[0155] It is not expected that the UE will be required to perform CSI-RS measurements or certain PUCCH transmissions, such as periodic CSI-RS reporting. MS,m During the micro-sleep period in BWP, the UE may not be expected to transmit SR. MS,m During the duration of certain BWPs (such as BWP D ) is configured with SR resources, the UE can remain awake and transmit SR on it.

[0156] Power saving by reducing blind decoding: Currently, NR Release 15 defines certain aggregation levels (AL) of the search space; the UE blindly decodes the candidates with the configured AL to detect DCI. What is supported in this article is the UE behavior where the UE can assume that the AL of the PDCCH at time "T" that was successfully decoded is applicable to the PDCCH until time T+Δt. Therefore, the UE does not need to try other AL assumptions for PDCCH monitoring within time Δt. Δt is configured to the UE through RRC. This functionality can be supported when there are sufficient resources available and low traffic in the system.

[0157] Similarly, if a UE detects a PDCCH candidate for a certain AL at a starting frequency resource position L (in the first symbol of a CORESET) at time T, it can assume the same position L and AL for duration Δt, so that each monitoring opportunity only needs to decode one candidate for duration Δt. Fig.10 , where AL and L detected in the PDCCH at time T apply to all PDCCHs within T+Δt.

[0158] Indicating micro-sleep as a slot format: This document supports indicating micro-sleep in the form of a slot format. The indication of micro-sleep can be achieved by format 2_0 DCI scrambled with SFI-RNTI. The slot format is defined by an index in the table of formats for DL, UL and flexible symbols (represented by "D", "U" and "X" respectively) in the 3GPP NR Release 15 specification. The SFI-RNTI provides a slot format for N slots by indicating the index of each of the N slots.

[0159] Introduced herein is a new type of symbol "M" in the slot format, which indicates that the UE can micro-sleep in this symbol. A DCI of format 2_0 with SFI-RNTI can use the "M" entry to indicate the index of the new slot format. Upon receiving the DCI, a UE configured with the SFI-RNTI can enter micro-sleep on the symbol indicated by the DCI. Since the SFI-RNTI is a group-shared PDCCH, the present disclosure allows micro-sleep indication in a multicast manner.

[0160] Some examples of slot formats with symbols marked with state "M" are given in Table 2. A whole slot may be indicated for a micro-sleep, or a mini-slot may be indicated for a micro-sleep.

[0161] In 3GPP Release 15, this index is currently 8 bits for slot format indication, but not all values ​​of this index are defined. Therefore, introducing a new slot format with status "M" can reuse the undefined entries for the slot format and no extra bits are required.

[0162] This type of indication helps manage micro-sleep with finer resolution. In particular, if a UE is configured with multiple monitoring opportunities in a slot, the micro-sleep of the UE cannot be long and deep because it must wake up multiple times in the duration of the slot to monitor the PDCCH. This approach provides the ability to set micro-sleep to a finer granularity at the symbol level, allowing micro-sleep to be managed at mini-slot resolution.

[0163] Table 2 Slot format with micro sleep state "M" for normal cyclic prefix.

[0164]

[0165] Alternatively, a new UE-specific DCI scrambled with C-RNTI can be introduced to indicate the slot format with a micro-sleep indication. For example, the UE can receive the SFI for micro-sleep in format 2_0 DCI using C-RNTI instead of SFI-RNTI. The DCI can be received in a common search space similar to SFI-RNTI. Alternatively, the DCI can be scrambled with another RNTI called micro-sleep RNTI "MS-RNTI", which is configured to the UE through RRC. MS-RNTI can be configured to be common to multiple UEs.

[0166] The gNB may transmit subsequent SFI-RNTIs whose states may conflict with those received by the UE via micro-sleep indications based on C-RNTI or MS-RNTI. Alternatively, the gNB may provide a UE-specific grant based on a previous indication that conflicts with the micro-sleep mode. In this case, the following predefined rules may be used to determine whether "M" can be covered by other states in the SFI-RNTI or by a grant. In the first rule, if the coverage occurs at least "R" codewords from the time the SFI-RNTI is received, the UE uses the coverage from the SFI-RNTI. This ensures that the UE has enough time to react to the coverage. In the second rule, if D covers M explicitly (via SFI-RNTI) or implicitly (via DL grant), the UE follows the latest control signaling and treats it as "D". In the third rule, if "U" covers "M" explicitly (via SFI-RNTI) or implicitly (via UL grant), the UE follows the latest control signaling and treats it as "U".

[0167] UE often needs to micro-sleep multiple symbols at a time. Disclosed herein is an indication through SFIDCI, which can be reinterpreted by the UE as a symbol in the hint table to indicate multiple adjacent symbols (mini-slots) or time slots to the UE. This allows the DCI to indicate the micro-sleep state of multiple mini-slots or time slots using a single index. Some examples are shown in Table 3. Here, half a time slot is represented by a single state. When the state is X, it implies that the SFI indication must be used for the half time slot. When the state is M, the UE can micro-sleep in the half time slot.

[0168] Table 3 Status indicates the time slot format of half time slot

[0169]

[0170] To minimize blind decoding, further disclosed herein is the DCI indicating micro-sleep in a time slot format, which can only be OnDuration K=1 may be a typical use case where the UE monitors this DCI only in the first K monitoring occasions within OnDuration.

[0171] Subsequently, when DrxInactivtyTimer has not expired, DCI may be transmitted outside of OnDuration. DCI may be transmitted periodically with a period P that may be smaller than the monitoring periodicity of its search space. The value of P is configured to the UE through RRC.

[0172] The DCI may provide a micro-sleep mode for the duration of the entire C-DRX cycle.

[0173] If the UE has a grant or has to make measurements or transmit SR or SRS or PRACH, the UE may stay awake to handle that function even if the SFI indicates "M" on those symbols.

[0174] UE-assisted micro-sleep: The UE may provide assistance information to the NB so that the NB can correctly configure the UE for micro-sleep. For example, the UE may signal the NB with its micro-sleep support capability information. Such information may indicate to the NB whether the UE supports the micro-sleep feature. In addition, such information may include support for one or more methods described herein. The UE may also signal to the NB its preference for micro-sleep. For example, a UE with a battery charge below a minimum threshold may indicate to the NB that it wishes to be placed in micro-sleep mode. Similarly, a UE with a battery charge above a certain maximum threshold or connected to a power source may indicate to the NB that it wants to exit micro-sleep mode or that it does not want to be placed in micro-sleep mode.

[0175] The UE may provide a graphical user interface (GUI) to the user, which allows the user to set preferences for controlling micro-sleep. For example, a lower power mode setting or battery saving setting by the user on the UE GUI may result in an exchange between the UE and the NB, and the NB commands the UE to perform micro-sleep.

[0176] Power saving signal based on on-off keying (OOK): A simple OOK signal can be used as a wake-up signal preamble. A simple receiver may be required to perform envelope detection of OOK, possibly in the time domain, and power consumption may be minimal to monitor such a signal. An analog-only receiver may be used to monitor the OOK signal and wake up part of the digital modem when it positively detects the OOK signal, such as when the detected power exceeds a certain threshold or the correlation exceeds a certain threshold. Alternatively, the OOK signal may be multiplexed with a channel in the time-frequency resource grid of an OFDM symbol. The sleep indication in the RRC CONNECTED state or the OOK signal for wake-up may be pre-configured to the UE via RRC signaling.

[0177] The OOK signal can be UE-specific or common to multiple UEs. The UE wakes up when it receives the wake-up OOK configured for it. When the UE receives the GTS-OOK configured for it, it micro-sleeps. UE-specific OOK signals can provide better power savings by reducing false wake-up alarms, but if the number of resources is limited, multiple UEs can share the same OOK.

[0178] The UE may also be configured with multiple wake-up OOKs. If it receives any one of the OOK signals, it may wake up. Alternatively, it may wake up only if it receives all wake-up OOKs within a predefined time period. Alternatively, it may wake up only if it receives at least W of the Z configurations.

[0179] OOK, then it wakes up. These methods provide different levels of robustness against false wake-up alarms, thereby optimizing power savings to different degrees.

[0180] When configuring the OOK signal, the gNB can provide the UE with the sequence, frequency resources and monitoring window.

[0181] For NR-U, in order to meet the OCB requirements, OOK can be mapped to enough REs that meet the frequency occupancy requirements.

[0182] DRX and wake-up signal - receiving a wake-up signal during the OnDuration of the DRX cycle: The UE can wake up and monitor the wake-up signal when its OnDuration occurs. Although other signals such as DMRS, CSI-RS, SSS, PSS or preamble codes can be used as power saving signals, it is specifically considered here that the wake-up signal can take the form of PDCCH. The first PDCCH monitoring opportunity can be used to indicate that the UE must stay awake to monitor the PDCCH in the remaining OnDuration. If the UE detects the wake-up signal PDCCH, it recognizes that it must wake up, otherwise the UE can enter a sleep state and not monitor other opportunities in the OnDuration. Therefore, the PDCCH in the first monitoring opportunity of the OnDuration can act as a wake-up signal for the UE.

[0183] This concept is illustrated in Figure 12. Fig. 12A In , the UE is given a PDSCH grant at the first PDCCH monitoring opportunity in OnDuration; therefore, the UE is implicitly aware that it must wake up and continue monitoring through opportunities when OnDuration and DrxInactivityTimer are running. Fig. 12B In the case of a UE not detecting a PDCCH at the first PDCCH monitoring opportunity, the UE will enter a sleep state until the next OnDuration.

[0184] This concept can be generalized such that the wake-up signal can appear in the form of PDCCH within N monitoring occasions within the OnDuration of the DRX cycle.

[0185] The PDCCH may provide a grant to the UE, so the UE recognizes that it must continue monitoring. Alternatively, the PDCCH may not be in the form of a grant, but may be another DCI, such as a DCI scrambled by the MS-RNTI and providing a micro-sleep state to the UE.

[0186] Described herein is a method for minimizing blind decoding during PDCCH decoding in the first monitoring opportunity of OnDuration; for the first monitoring opportunity in OnDuration, the position L or aggregation level (AL) can be pre-configured to the UE through RRC. Therefore, the UE can have minimal blind decoding overhead.

[0187] DRX and wake-up signal - receiving the wake-up signal before OnDuration: It may be beneficial to allow the wake-up signal to be received before OnDuration so that the UE can perform fine synchronization and beam training before OnDuration if necessary. Therefore, the wake-up signal may be transmitted in the Pre-OnDuration Window (POW) before OnDuration. This concept is illustrated in Figure 13.

[0188] If the wake-up signal is in the form of a PDCCH or a DMRS followed by a PDCCH, the UE may have a "WakeUp-CORESET" configured for the wake-up signal. The CORESET may have a wideband DMRS to enable better detection reliability of the DCI. However, the CORESET may be relatively narrowband within the default BWP or active BWP to minimize power consumption when monitoring the wake-up signal. New DCI formats may be introduced, such as for wake-up signaling, and the UE may be configured to receive the wake-up signal in a user-specific search space or a common search space. As contemplated by other optional considerations herein, it is contemplated that both the user-specific search space and the common search space may be configured to receive the wake-up signal.

[0189] The UE can have multiple monitoring opportunities within the POW, for example, the search space periodicity for DCI-based wake-up signals can be small enough that multiple opportunities can occur in the POW. This provides the gNB with flexibility to address a large number of UEs. Outside of the WakeUp-CORESET, the UE does not need to monitor the power saving signal.

[0190] Fig.13A shows where the UE monitors the default BWP D POW on and switches to active BWP BWP after receiving a wake-up signal in POW A Example of a wake-up signal including switching to BWP A command. Fig. 13B shows where the UE is in active BWPBWP A An example of monitoring the POW in FIG. 4 and then waking up to monitor the PDCCH on the DRX cycle of the same BWP.

[0191] The UE may micro-sleep between the duration of its reception of the wake-up signal and the start of the OnDuration. This may be applicable in cases where the UE does not see the need for resynchronization before the OnDuration, for example if no BWP switching is required on wake-up, or if the synchronization accuracy is sufficient to operate in the BWP to which the UE switches after receiving the wake-up signal.

[0192] Note that the periodicity of POW may allow the UE to monitor once every D DRX cycles.

[0193] If a wake-up signal is received within this window, the UE must wake up to monitor for at least the next OnDuration. If no wake-up signal is received within this window, the UE does not need to wake up until the next POW opportunity - this can be an implicit indication of sleep. This process is Fig.34A . At step 211, the UE (e.g., WTRU102a or UE 99) may monitor the POW. At step 212, a determination is made as to whether a wake-up signal is detected. For example, this determination may be made based on whether a DL control signal carrying a wake-up command is detected. If it is determined that a wake-up signal has not been detected, the UE may sleep until the next POW (step 215). The monitoring of step 212 may continue to occur at or near the next POW. At step 213, based on a determination that a wake-up signal is detected, the indicated parameters (e.g., parameters from the wake-up signal) may be used in the wake-up state. At step 214, the UE may wake up in the next OnDuration.

[0194] Alternatively, a GTS signal may be transmitted in the POW; upon receiving it, the UE sleeps for the next OnDuration. If no GTS is detected, the UE must wake up for the next OnDuration of the DRX cycle. This process is described in Fig.34B . At step 221, the UE (e.g., WTRU 102a) may monitor the POW. At step 222, a determination is made as to whether a GTS signal is detected. For example, this determination may be made based on whether a DL control signal carrying a GTS command is detected. If it is determined that a GTS signal has been detected, the UE may sleep until the next POW (step 224). The monitoring of step 221 may occur at or near the next POW. At step 223, based on determining that a GTS signal is detected, the UE may wake up at the next OnDuration.

[0195] In another example, Fig.34CAs shown in the process in , the UE must receive a wake-up signal or GTS to determine its behavior during the OnDuration of the next DRX cycle. At step 231, the UE (e.g., WTRU 102a) may monitor the POW. At step 232, it is determined whether a GTS signal is detected. For example, this determination may be made based on whether a DL control signal carrying a wake-up command or a GTS command is detected. If it is determined that a GTS signal has been detected, the UE may sleep until the next POW (step 236). At or near the next POW, the monitoring of step 231 may occur. At step 233, it is determined whether a wake-up signal is detected. For example, this determination may be made based on whether a DL control signal carrying a wake-up command is detected. If it is determined that a wake-up signal has not been detected, then based on this determination, at step 237, default parameters may be used in the wake-up state. At step 234, based on the determination that a wake-up signal has been detected, the indicated parameters (e.g., parameters from the wake-up signal) may be used in the wake-up state. At step 235, the UE may then wake up for the subsequent OnDuration.

[0196] Continue to refer Fig.34C And additional aspects, if a GTS signal is received, and the GTS indicates the duration of sleep, the UE sleeps for one or more DRX cycles. Alternatively, if the UE receives a wake-up signal, it can wake up for the next OnDuration. If the wake-up signal provides certain power saving parameters (such as search space monitoring period, etc.), the UE can use those parameters to determine its operation after waking up. If it does not detect a wake-up signal or GTS, it can still wake up for the next OnDuration, but operates using a set of default values, otherwise these values ​​will be provided by the wake-up signal (if received). The default values ​​can be configured to the UE through RRC signaling.

[0197] Without in any way unduly limiting the scope, interpretation, or application of the claims appearing herein, the technical effect of one or more of the examples disclosed herein is to provide adjustments to how power is managed. While conventional DRX mechanisms allow UEs to sleep and save power when not required to monitor a cell, DRX parameters cannot be dynamically adjusted based on network traffic or applications. The methods described herein allow for dynamic adaptation of the UE's wake-up and sleep states—these states can be adapted to suit the network's traffic and the UE's applications.

[0198] exist Fig.35In FIG, another scenario is shown in which the active DRX time may extend into the duration of the next POW. The following operational procedures may then be considered for the UE. If the UE is in the DRXInactivityTimer period during the POW opportunity, the UE may assume that the gNB will not transmit a wake-up signal on the POW. Therefore, the UE does not need to monitor the wake-up CORESET during its DRXInactivityTimer period, for example, the UE may not monitor the wake-up signal during its active DRX time. Therefore, the UE may not explicitly receive a wake-up signal for the next OnDuration in the POW. In this case, one of the following procedures may occur. In the first example procedure, by default, the UE may monitor the next OnDuration without receiving an explicit wake-up signal. This procedure Fig.36A The UE may receive a GTS from the gNB that instructs it to sleep and end the active DRX time. In the second example, the UE may sleep after the DRXInactivityTimer expires. It does not wake up to monitor the next OnDuration because it did not monitor the previous POW. It may monitor the next available POW for an explicit wake-up signal. This process is shown in Fig.36B The following shows Fig.36A and Fig.36B Further description of the steps.

[0199] Fig.36A An exemplary method for extending the active period into the window before monitoring OnDuration is illustrated, such as the UE monitoring the next OnDuration even if the DRXInactivityTimer expires before the OnDuration. At step 241, it is determined whether the POW has reached a threshold. Based on the POW duration threshold being met, at step 242, it is determined whether the DRXInactivityTimer is running. At step 243, based on the running DRXInactivityTimer, the UE may determine not to monitor the POW for a power saving signal, and then at step 244, wake up for the next DRX OnDuration even if the DRXInactivityTimer has expired. It should also be noted that if it is determined at step 242 that the DRXInactivityTimer is not running, then at step 245, the UE may monitor the POW for a power saving signal.

[0200] Fig.36BAn exemplary method for extending the active period into the window before monitoring OnDuration is illustrated, such as if the DRXInactivityTimer expires before the OnDuration, the UE sleeps at the beginning of the next OnDuration. At step 251, it is determined whether the POW has reached a threshold. Based on the POW duration threshold being met, at step 252, it is determined whether the DRXInactivityTimer is running. At step 253, based on the running DRXInactivityTimer, the UE may determine not to monitor the POW for power saving signals, and then at step 254, if the DRXInactivityTimer expires, sleep at the next DRX OnDuration. It should also be noted that if it is determined at step 252 that the DRXInactivityTimer is not running, the UE may monitor the POW for power saving signals at step 255.

[0201] Fig.37 An exemplary method is illustrated when the active period extends to monitor the OnDuration front window, such as when the UE receives a power saving signal in the active duration. If the UE is in the active DRX time, it can monitor the wake-up signal on the CORESET that it is configured to monitor during its active time. If the wake-up signal is received, the UE can ensure that it is awake to monitor the next OnDuration, such as in Fig.37 As shown in the process of FIG. 261, it is determined whether the POW has reached a threshold. Based on the POW duration threshold being met, it is determined at step 262 whether the DRXInactivityTimer is running. At step 263, based on the running DRXInactivityTimer, the UE can monitor the power saving signal during the active time. It should also be noted that if it is determined at step 262 that the DRXInactivityTimer is not running, the UE can monitor the POW for a power saving signal at step 264.

[0202] Continue to refer Fig.37 In the example, if the UE is in the active DRX time, it can monitor the wake-up signal on the CORESET that it is configured to monitor during its active time. If a wake-up signal is received, the UE can ensure that it is awake to monitor the next OnDuration, such as Fig.37As shown in the process of . The UE may monitor the wake-up signal in its active time only during certain monitoring occasions, because it is expected that the wake-up signal will not be received soon after the UE sets its DRXInactivityTimer. The appropriate time to signal the wake-up signal may be close to the end of the expiration of the DRXInactivityTimer. Thus, the UE may monitor the wake-up signal only over K monitoring periods before the expiration of the DRXInactivityTimer. In an example alternative, the GTS may be signaled in the active time to indicate that the UE sleeps during the DRX cycle, but the GTS may indicate that the UE wakes up for the next ONDuration. In another example alternative, the UE may monitor the power saving signal during the duration of the POW but on the CORESET corresponding to the active duration (for example, these CORESETs may be different from the WakeUp-CORESET). During the active time, the power saving signal may be signaled in a UE-specific search space, and in the inactive time, the power saving signal may be signaled in a common search space (such as a common search space for a group-common PDCCH). The UE may reset its DRXInactivityTimer when receiving the wake-up signal.

[0203] Fig.38A An exemplary method for receiving a GTS in an Active Duration is illustrated. There may be a scenario where the Active DRX Active Time extends into the following OnDuration period. In this case, the Active Time overlaps with the OnDuration and the UE has woken up during the OnDuration of this DRX cycle. The UE relies on the DRXInactivityTimer expiration or the GTS signal to go to sleep during this cycle.

[0204] refer to Fig.38A , at step 271, the UE may receive the GTS at any time during its active time. At step 272, the UE may determine that the GTS may indicate that the UE is micro-sleeping for a certain duration, and at step 273, the UE wakes up during the active time to continue monitoring the PDCCH. In this case, the DRXInactivityTimer may be decremented during the micro-sleep - this behavior of the timer leaves the current operating process of the UE unchanged. Alternatively, the DRXInactivityTimer may be suspended or frozen for the duration of the micro-sleep - this process may be useful for target use cases where grants are sparse and the UE can save power between grants without the DRXInactivityTimer expiring early. The duration of the sleep may be indicated by the GTS signal, or may be pre-configured to the UE by RRC signaling.

[0205] Fig.38B An exemplary method for receiving a GTS in an active duration is illustrated, such as when the UE's active duration ends and the UE sleeps and the UE wakes up to monitor the next POW on the next OnDuration. Fig.38B At step 281, the UE may receive a GTS during its active time, but based on the received GTS, at step 282, the UE may end the active time of the DRX cycle and go to sleep. The GTS may instruct the UE to sleep until the next OnDuration opportunity or the next POW opportunity. Therefore, the DRXInactivityTimer of the UE may expire and the UE may go to sleep when its active time in the DRX cycle ends.

[0206] At step 283, the UE's behavior in response to reception of a GTS in an active time (whether waking up in the same active time or waking up only at the start of the next POW or OnDuration) may be configured by RRC signaling or indicated by the GTS signal.

[0207] The duration of the POW and the periodicity for monitoring the POW may be configured to the UE via RRC signaling from the gNB. The start time of the POW may be indicated as an offset relative to the start of the OnDuration of the DRX cycle (e.g., in terms of symbols, minislots, or slots, or a combination thereof). Alternatively, the start time of the POW may be indicated as an offset relative to the frame timing. The monitoring timing of the power saving signal in the POW is configured via a search space associated with a CORESET (e.g., WakeUp-CORESET). The configuration of the POW may be per cell per BWP and provided via RRC signaling from the gNB.

[0208] In general, a power save signal received on BWP1 may indicate that the UE must wake up in BWP2. Or it may indicate that the UE must micro-sleep on BWP2, e.g. the UE micro-sleeps and if it does not return to BWP D , then can be woken up on BWP2.

[0209] Upon receiving the wake-up signal, before the OnDuration in BWP2 starts, the UE can prepare to receive and transmit in BWP2, and thus can perform one or more of the following on BWP2 in the time gap between receiving the wake-up signal and the OnDuration on BWP2: 1) fine synchronization using TRS or PT-RS or other RS ​​(such as CSI-RS, DMRS, SSB); 2) beam training; or non-periodic CSI measurement and reporting - the wake-up signal can provide a UL authorization that triggers non-periodic CSI measurement, which can be a DCI, such as a format of 0_1.

[0210] Alternatively, the UE may be configured to treat the wake-up signal itself as a trigger for non-periodic CSI measurement or reporting in BWP2. Thus, the wake-up signal may implicitly trigger the measurement or reporting. The CSI-RS resources for measurement and the PUCCH or PUSCH resources for reporting are pre-configured to the UE; for example, this configuration may indicate the resource PUSCH start slot or symbol relative to the slot or symbol start of the POW or the slot or symbol of the wake-up signal or the slot or symbol of the DRX OnDuration. In this example, the wake-up signal itself may appear as a group-common signal or a UE-specific signal.

[0211] The concept of triggering aperiodic reports is Fig.14A As shown in Fig. 14B As shown in FIG. 3 , the process is summarized in the following steps. At step 301, the UE may monitor the BWP in the POW opportunity. D At step 302, if the signal is received by the UE, it may trigger a power saving signal to the BWP. A At step 303, the UE measures the CSI-RS for aperiodic reporting. At step 304, the UE reports the CSI-RS during OnDuration. At step 305, the UE receives a grant from the gNB during the C-DRX cycle.

[0212] like Fig. 14C As shown in FIG. 1 , another example described in the following process can also be considered to trigger a non-periodic report. At step 311, the UE monitors the BWP in the POW opportunity. D At step 312, if the signal is received by the UE, it may trigger a power saving signal to the BWP. A At step 313, the UE measures the CSI-RS for aperiodic reporting. At step 314, the UE reports the CSI-RS before OnDuration. At step 315, the UE receives a grant from the gNB during the OnDuration of the C-DRX cycle.

[0213] The concept is Fig.15A The CSI-RS may appear inside or outside the POW.

[0214] CSI-RS reporting can also happen within the POW. This concept is Fig. 15B Here, the measured CSI-RS is also within the POW.

[0215] Switching between power saving states: A UE may be configured with multiple "power saving configurations" (PSCs). Depending on the capabilities of the UE or the traffic conditions or the application or feedback from the UE, a specific PSC may be applied, providing a certain amount of power saving. Layer 1 or MAC CE or RRC may indicate the PSC to be used in the UE.

[0216] PSC can consist of one or more of the following parameters: 1) multiple BWPs, different DRX parameters, or time domain resource allocation (TDRA) parameters. Fig.16 Shown in. Fig.16 The default PSC is shown. D and PSC1 is the PSC configured for the UE. The PSC may be selected using RRC signaling-based or MAC CE-based configuration or L1 signaling.

[0217] Multiple BWPs - In a PSC, multiple BWPs can be configured with different parameters. Based on the number of PRBs in a BWP, different degrees of power savings can be obtained. Also, the K0, K1, K2 values ​​can be configured appropriately to enable cross-slot scheduling and delayed scheduling within a slot to reduce buffering requirements immediately following PDCCH monitoring. The default BWP can be different for each PSC. The BWPInactivityTimer can be configured differently for each BWP. Also, the CORESET configured for each BWP can support different bandwidths and search space periodicities.

[0218] Different DRX parameters - Depending on the application, the PSC may have different durations for DRX parameters such as DRXInactivtyTimer or OnDuration. Furthermore, DRX parameters may be BWP specific.

[0219] Time Domain Resource Allocation (TDRA) parameters - PDSCH duration, start time, etc. can affect the UE's buffering capacity and thus affect power consumption.

[0220] When a specific PSC is indicated, the UE uses certain BWP, associated DRX parameters, TDRA configuration. A default PSC "PSC D ”.

[0221] If the application changes or the traffic situation changes, it is desirable to switch the UE to operate in the appropriate PSC configuration. For example, one PSC configuration may allow higher capacity and lower latency, but less power savings. While another PSC may trade off between capacity and latency to save more power.

[0222] For micro-sleep, the UE can utilize a priori knowledge of parameters such as K0. If K>0, the UE can micro-sleep between PDCCH reception or processing and PDSCH reception or processing, such as Fig.17 As shown in . By not having to buffer the PDSCH while processing the PDCCH, the UE can save power.

[0223] In the prior art, multiple K0 values ​​are configured through RRC signaling. The DCI providing a PDSCH grant indicates a specific K0 value for that grant. The UE can assume a worst-case value for K0, such as the minimum K0 value in the TDRA table, to plan PDSCH buffering and processing while optimizing its micro-sleep duration. Note that power savings can be achieved through a priori knowledge of K0; if K0 is only known at the end of DCI decoding, the UE may not have enough time to react to PDSCH buffering in a power-efficient manner. In other words, the UE should prepare a minimum value for K0.

[0224] Similarly, if there is enough time between PDCCH reception and scheduled PDSCH reception (K0=0), the same time slot scheduling can also reduce the constraints on buffering and provide power savings. Fig.18 This type of scheduling is shown in . However, the UE needs to know the CORESET duration and position within the timeslot and the starting point of the PDSCH, which can be scheduled by the PDCCH in this CORESET. The start and length indicator value (SLIV) for the grant can be configured based on the position of the CORESET in the timeslot and the number of symbols within the CORESET.

[0225] Consider a use case where the UE supports URLLC and eMBB traffic. eMBB traffic using a relaxed K0 value can provide power savings, while URLLC traffic using a smaller K0 value for latency has limited power savings. Therefore, the minimum K0 value for eMBB can be greater than the minimum K0 value for URLLC traffic. As another example, a gNB can support different levels of power savings for a given UE depending on its load; when the load is low, it can operate at a relaxed K0 value and can save a lot of power, while when the load is high, it can use a smaller K0 value, saving less power. Therefore, the minimum K0 value for low load cases can be greater than the minimum K0 value for high load cases.

[0226] To support different PSCs, multiple TDRA tables may be configured for UEs supporting different sets of K0 values ​​and different SLIVs.

[0227] The following example scenarios can enable L1-based handover between PSCs. In the absence of any indication, the UE can use the default PSC PSC D . In the first scenario, the wake-up signal may indicate the PSC to be applied in this DRX ON cycle. For example, the wake-up signal may indicate that only eMBB traffic is expected; in this case, the UE uses PSC1. Or it may indicate that both eMBB and URLLC traffic are expected, so the UE uses PSC2. The wake-up signal may be a GC-PDCCH or a UE-specific PDCCH with a field indicating the PSC to be used for the next D DRX cycles. If the wake-up signal is received in POW, the UE may have sufficient time to switch PSC. Fig.19A It shows that the UE receives the wake-up signal from the PSC D Example of switching to PSC1. If a wake-up signal is received in the OnDuration of a DRX cycle, the UE may also monitor the CORESET simultaneously to find authorization and may use the default PSC for BWP at least for the duration for which it can receive an indication for a PSC. Alternatively, it may use the PSC configured by the wake-up signal in the past DRX cycle P Alternatively, a pscValidTimer timer may be configured for the UE, with its value configured by RRC. The UE sets the timer upon receiving a PSC indication for PSCp. When the timer expires, the UE switches to PSC D ,like Fig.19B as shown in .

[0228] In the second scenario where L1-based switching between PSCs can be enabled, multiple BWPs are configured for the UE and each BWP can have its own TDRA table. A PSC is associated with a BWP. The UE can activate BWP switching to change the PSC. For example, BWP1 can be configured with a relaxed K0 value to support power saving for eMBB services. BWP2 can be configured with a small minimum K0 value to support URLLC and eMBB. When URLLC services are authorized, the gNB switches the UE from BWP1 to BWP2. Except for the TDRA table, BWP1 and BWP2 can be exactly the same. Therefore, the UE does not need to perform resynchronization or tuning and can start operating on the new BWP without lag. The UL or DL ​​grant on BWP1 provides an indication of the switch. However, the UE can use the definition of TDRA, K0 and SLIV values ​​for this grant based on BWP1. Subsequent grants in BWP2 can use the TDRA, K0 and SLIV values ​​configured for BWP2. This concept is described in detail in the GNB documentation. Fig. 20 Shown in. Fig. 20 An exemplary BWP-based PSC switching is illustrated. K0=1 is used for the grant received from BWP1 for the PDSCH in BWP2.

[0229] A third scenario where L1-based handover between PSCs can be enabled, a PSC switch DCI can be used to change the PSC configuration on the BWP. It can be signaled as a GC-PDCCH or a UE-specific PDCCH. It carries a field indicating the new PSC to be used, and a field indicating the time when the handover must be applied.

[0230] In general, multiple PSCs can be activated for a UE at a given timer if the parameters affected by the PSCs do not overlap with each other. For example, one PSC can affect DRX and BWP. Another PSC can affect the TDRA table. Both PSCs can be activated to the UE. This provides greater flexibility for the gNB to support different traffic types and provide finer resolution power savings with minimal configuration overhead.

[0231] SCell procedures for power saving - Low power operation in SCell: Compared to the nominal operation of the UE switching between active and deactivated states, a new state called "dormant state" can be introduced to enable the UE to save power. Due to the high latency of deactivation and reactivation, the UE is often in the active state. The dormant state is an operating state with an operating load between the active state and the deactivated state, and therefore has lower power consumption than the active state. Fast transitions between states can save power by quickly responding to dynamic changes in traffic.

[0232] When the UE is in RRC connected mode, the UE may have one or more SCells in a dormant state. The UE may perform one or more of the following operations in the dormant cell. Regarding the first operation, measurement, tracking, and reporting may occur through the PCell or PSCell.

[0233] Regarding the second operation in the dormant cell, there is minimal or no PDCCH monitoring on the SCell. In the dormant state, no grant is received on the SCell. The UE may not even monitor the PDCCH on the SCell. When the SCell must be activated, the activation can be indicated on the PCell or PSCell through higher layer signaling or L1 signaling. Alternatively, the UE can monitor the PDCCH or activation RS on the SCell in the dormant state; when it receives an activation DCI or activation RS, it activates the SCell and switches to active state monitoring.

[0234] This document discloses a sleep BWP, a sleep CORESET, or a sleep search space that can be configured for a UE to monitor a PDCCH in a sleep state. Power savings can be achieved in the sleep CORESET monitoring phase by limiting the number of blind decodings and limiting the length and format of the expected DCI. For example, a UE can monitor only one DCI format for SCell activation or deactivation in a sleep state. The DCI can be an UL grant that triggers a non-periodic CSI measurement report. Or it can be a DL grant or a PDCCH command to enable the timing advance of the UE. Alternatively, it can be a GC-PDCCH that provides an activation or deactivation command to a group of UEs.

[0235] When switching a cell from dormant state to active state, the UE performs the following procedure. Figure 21A-21B UE 99 monitors the dormant-BWP for indications of cell activation. For example, UE 99 may also monitor the PCell or PSCell to obtain cell activation indications from gNB 98. When the UE receives the cell activation indication (at step 321 or step 331), it switches to the activated state, which may imply the following.

[0236] refer to Fig.21A , UE 99 may start monitoring the default BWP of the SCell (step 322). Note that the default BWP in the active cell state and the dormant BWP in the dormant cell state may represent the same BWP.

[0237] refer to Fig. 21B The cell activation DCI may indicate the BWP to be monitored in the cell. Therefore, once the UE switches to the active cell state, the UE starts monitoring the active BWP (the message sent in step 331 includes the active BWP), such as Fig. 21BWhen it switches to the active cell state, it stops monitoring the dormant CORESET and monitors the nominal CORESET configured for its active state. Fig.21A and Fig. 21B As shown in FIG, after performing appropriate switching to activate the cell state and monitoring the appropriate BWP, a grant is then received on the activated SCell (for Fig.21A and Fig. 21B Step 323 and step 333 of each of them).

[0238] Similarly, the UE may switch a cell from a dormant state to a deactivated state using the following procedure. Cell deactivation indication via L1 signaling or higher layer signaling. First, the UE may monitor the dormant-BWP for a cell deactivation indication, where the indication occurs via L1 signaling such as deactivation-RS or DCI. The UE may also monitor the PCell or PSCell for a cell deactivation indication; here, the deactivation indication may occur via L1 or higher layer signaling. Second, when the UE receives a cell deactivation indication, it may switch to a deactivated state. The UE stops monitoring the RS and PDCCH in the dormant BWP and deactivates the cell.

[0239] A single activation indication or deactivation indication can affect multiple SCells. For example, S SCells can be activated or deactivated by a single DCI or MAC CE. The gNB configures these S cell IDs to the UE via RRC signaling. The UE can respond to the activation or deactivation command received on the DCI with a MAC CE-based confirmation, which can be sent on an active cell such as a PCell or PSCell.

[0240] When the UE receives an indication (which can be through RRC signaling or MACE or DCI) on the cell itself or on the PCell or PSCell, the UE can change its monitoring of the cell from active to dormant. Alternatively, a timer "activeTodormancyTimer" can be used to determine when the cell must switch from active to dormant. When the SCell is active for the UE, the UE can set the "activeTodormancyTimer" under one or more of the following conditions, which indicate potential resource requirements on the cell: 1) UE transmits RACH; 2) UE transmits SR; 3) UE transmits scheduled PUSCH; 4) UE transmits CG PUSCH; 5) UE transmits PUCCH; 6) UE transmits SRS; 7) UE receives UE-specific authorization; or 8) UE receives PDSCH.

[0241] When the timer expires, the UE can switch to the dormant state. Fig. 22As shown in . In step 341, the active BWP of the active SCell can be monitored. At step 342, it is determined whether there is an authorization for the SCell from the gNB. If there is no authorization, proceed to step 341 (B), and if there is authorization, proceed to step 343. At step 343, activetoDorancyTimer can be set. At step 344, it is determined whether the activeToDormancyTimer has expired. If not expired, proceed to step 346, and if expired, proceed to step 345. At step 345, based on the expiration of the timer, the SCell can be moved to a dormant state. Alternatively, at step 346, if the timer has not expired, decrement and return to step 344.

[0242] The timer "dormantToDeactiveTimer" may be used to determine when a cell must be switched from dormant to deactivated state. The UE may set this timer when entering dormant state. Alternatively, the UE may receive an indication from the gNB to start a timer on the same SCell or PCell or PSCell. Upon receiving the indication, the UE starts the timer. When the timer expires, the UE may deactivate the cell. This procedure is described in Fig.23 At step 351, a dormant state is entered and dormantToDeactivateTimer may be set. At step 353, it is determined whether dormantToDeactivateTimer has expired. If so, the SCell is moved to a deactivated state as provided in step 353. If not, dormantToDeactivateTimer is decremented as provided in step 354. After decrementing, the UE may return to step 352.

[0243] If the UE receives a cell activation indication during the dormant state, the UE may suspend (eg, freeze) the dormantToDeactiveTimer and activate the cell.

[0244] SCell procedures for power saving - Bundled behavior on PCell / PSCell and SCell: If a UE sleeps on SCell while sleeping on PCell, its power saving can be optimized by ramping down various Rx-Tx and digital operations in the modem. Therefore, it may be advantageous to synchronize the power state of the UE between PCell and SCell to the extent possible.

[0245] Moreover, for use cases with bursty traffic, the SCell supplements the PCell or PSCell with more resources. If a UE is less likely to receive or transmit on a PCell or PSCell, it is less likely to receive or transmit on a SCell. Therefore, the SCells can be bundled in such a way that if a power saving signal is received in one cell, it can affect the behavior on S SCells. Alternatively, a certain UE behavior on one cell affects the UE behavior on the cells in the bundle.

[0246] The concept of bundling Fig.24 As shown in FIG, the PCell of the UE is bundled with some SCells, and the PSCell is bundled with some SCells.

[0247] The correspondence between the PSCs of the bundled cells can define the behavior of the bundled cells. Fig.25 As shown in , the PSC on the PCell can correspond to the PSC in the SCell. P,1 , the PSC of SCell will be automatically activated S,1 .

[0248] like Fig.26 A single cell can also exist in multiple bundles as shown in the example in . Here, the PCell is part of two bundles. One bundle can be active at a time - therefore, the SCells in that bundle are affected by signaling or behavior in the PCell. For example, if bundle #1 is active, the UE can microsleep in SCell1 and SCell2 while the UE is microsleeping in the PCell.

[0249] Active bundling may be configured through RRC signaling or may be configured through MACCE through L1 signaling such as power saving signaling.

[0250] Any PSC activation or PSC deactivation or micro-sleep behavior in a cell can trigger corresponding activation, deactivation or micro-sleep behavior in all cells in the active bundle. Optionally, a leader can be defined for the bundle; therefore, only activation or deactivation or micro-sleep behavior on the leader cell automatically triggers PSC activation, PSC deactivation or micro-sleep behavior in the active bundle.

[0251] A wake-up signal or sleep signal on one cell may instruct the UE to wake up or sleep on another cell. For example, a wake-up on a PCell may instruct the UE to wake up on S of its N configured SCells and its PCell. Alternatively, a wake-up signal on a PCell may instruct the UE to wake up from micro-sleep on its PCell and activate S of its N configured SCells from a dormant state.

[0252] The enter sleep signal on the PCell may instruct the UE to micro-sleep on S of its N SCells and micro-sleep on its PCell for a specific duration, such as D DRX cycles. Alternatively, the enter sleep signal on the PCell may instruct the UE to micro-sleep on the PCell for a specific duration, such as D DRX cycles, and switch to a dormant state on S of its N SCells.

[0253] The wake-up signal or the go-to-sleep signal may also indicate a specific bundle of the (S) SCells that must react to the power saving procedure. The bundles indexed in the table may be configured by RRC. An index to the table may be provided by the power saving signal to indicate the activated bundles.

[0254] If the power saving signal is in the form of a BWP activation DCI, then a BWP switch in one cell can automatically trigger a BWP switch on the bundled cell. P,1 or BWP P,2 The BWP switching can trigger the bundled SCell from the BWP S,1 or BWP S,2 The BWP switch, such as Fig. 27 as shown in .

[0255] If the UE's BWPInactivityTimer expires on the PCell, the UE switches to the default BWP on the PCell. This switching triggers the UE to switch to the default BWP on the bundled SCell after completing the scheduled transmission on the SCell, even if the BWPInactivityTimer of the SCell has not expired.

[0256] Alternatively, when the UE may switch to the default BWP in a cell such as a PCell, the UE may enter a dormant state in the bundled SCell.

[0257] If a CORESET or search space is activated or deactivated for one cell, the corresponding CORESET or search space may be activated or deactivated for the bundled cells.

[0258] Generally speaking, the power saving signal received on the SCell will also affect the micro-sleep behavior on the PCell or PSCell or another SCell, and the solutions discussed above can also be applied to this scenario.

[0259] SCell Procedure for Power Saving - UE Assisted SCell Activation: When a UE has data to send, it can activate S SCells. An example procedure is described below and is Fig.28 . At step 361, when the UE 99 sends an SR (which can be on a PCell or SCell), it activates a bundle that may have been in a dormant state. The bundle can be selected autonomously by the UE 99, or configured by the gNB 98. At step 362, the gNB 98 can provide an UL grant. At step 363, the UE 99 can feed back the activated bundle to the gNB 98. This indication can be sent along with the UE's BSR. If the gNB 98 does not schedule the UE 99 on a cell (from an activated bundle) within the expiration of the activeTodormancyTimer, the UE 99 can return the cell to a dormant state. At step 364, the gNB 98 can provide scheduling for the UL.

[0260] If the UE 99 has the option to select from multiple bundles, it may select a bundle based on the amount of data to be transmitted (e.g., its BSR). A larger BSR may mean activating a bundle with more cells or cells with larger bandwidth.

[0261] The PDCCH-based power saving signal may include one or more of the following fields in its DCI, as shown in Table 4.

[0262] Table 4

[0263] Fields describe Wake-up indicator Wake-up Indicator GTS-indicator Sleep Indicator BWP-indicator The BWP to switch to when receiving a wakeup or GTS indication PSC-indicator Power saving configuration for PCell, PSCell and SCell TDRA-indicator TDRA table to be used SCell-activation Activate / deactivate one or more SCells Search-space-indication Indicates parameters to change monitoring periodicity

[0264] Fig.39 The figure shows exemplary fields and the location of the fields within the DCI. For each UE, not all fields may be present. The applicable fields in the DCI may be configured to the UE via RRC signaling. It is contemplated that a single DCI may carry power saving instructions to multiple UEs. In this case, the location of the fields within the DCI for the UE may also be indicated via RRC signaling, such as Fig.39 As shown in the example in . Here, UE1 and UE2 have a common "field1", and only UE1 is configured to receive "field2". For example, a UE with SCell does not need to receive fields related to SCell activation.

[0265] As a special case, the GTS PDCCH may be a signal that provides only a single bit of information to each UE via the common DCI. Here, each bit in the DCI payload may correspond to one UE. The position of the bit in the bitmap may be configured to the UE; thus the UE may look for the bit at that position to decide whether it has received a sleep instruction.

[0266] Power saving in IDLE or INACTIVE state - UE-specific paging DCI. To avoid false alarms, the UE may be paged via UE-specific DCI. In IDLE or INACTIVE state, the DCI may use the IDLE / INACTIVE-ID "II-ID" to scramble the DCI. The II-ID may be derived from the UE's ID (such as the IMSI or TMSI) by masking some bits in the IMSI or TMSI. This reduces false paging alarms, but does not completely eliminate them since multiple UEs may have the same II-ID even if their IMSI / TMSI are unique. The DCI may carry the masked bits of the UE's identity in the payload, such as Fig.29 As shown in . Together with the II-ID and DCI payload, the UE can identify whether it has been paged. The UE does not need to decode the PDSCH to determine whether it has been paged. This provides some power savings.

[0267] Because the paging DCI is UE-specific, the resources used for control signaling can be significant for the gNB and block other PDCCHs in the CORESET. Therefore, this approach may be suitable for cells with few UEs and low traffic load. For example, sensor deployment in small cells can be configured for such operation. However, for flexibility, the gNB can switch the type of paging to adapt to the ongoing traffic. The gNB can indicate the type of paging used, for example, UE-specific paging or legacy (broadcast) paging method through SI such as MIB or RMSI.

[0268] For certain use cases, the gNB can also support specific paging methods. For example, for URLLC UEs, the gNB can provide UE-specific paging to enable low-latency operation. For mMTC UEs, the gNB can provide UE-specific paging to avoid false paging alerts. While for eMBB UEs, the gNB can still use legacy paging. Sufficient context about the UE can be stored in the network to enable the appropriate paging method for a given UE.

[0269] UE-specific paging DCI is not required to provide PDSCH allocation. However, for some cases, it is advantageous to support grant provision through UE-specific paging DCI. For example, Fig.30 As shown in , a URLLC UE can receive DL or UL grant in a UE-specific paging DCI.

[0270] For some use cases, it may be beneficial to support both broadcast and UE-specific paging. If a UE supports both URLLC and eMBB services, it may be paged by one method or the other. UE-specific DCI with authorization may be provided for URLLC services. Legacy paging may be used for eMBB services. Thus, the UE may monitor both types of paging DCI. Monitoring timing may be configured independently for each paging type.

[0271] Power saving in IDLE or INACTIVE state - configure multiple paging RNTIs (P-RNTIs). The gNB can configure multiple P-RNTIs in the network. They can be obtained through SI (such as RMSI or OSI). The hash function can map the UE ID (such as IMSI or TMSI) to N paging RNTIs (consisting of P1-RNTI, P2-RNTI, ... P-RNTI). N -RNTI representation). The UE can then monitor for paging indications only on the paging RNTI corresponding to its ID. As the gNB splits UEs across different RNTIs, the number of false paging alerts per UE can be reduced. The UE still has to decode the paging PDSCH to detect if its UE ID is retransmitted to determine if it has been paged. Fig.31 The UE may monitor P1-RNTI, P2-RNTI or P4-RNTI in the paging RNTI pool.

[0272] Power saving in IDLE or INACTIVE state - using wake-up signal for paging: The wake-up signal can be used to indicate whether the UE should monitor during the paging occasion. This can reduce excessive monitoring during the paging occasion. In the common search space, the wake-up signal can be in the form of an OOK signal or RS or DCI. When the UE detects the wake-up signal, it monitors the paging DCI in the next paging occasion. If the wake-up signal is not detected, there is no need to monitor the next paging occasion.

[0273] The wake-up signal configuration may be provided via RMSI or OSI. For example, multiple OOK configurations may be broadcast. The UE's ID may be mapped to one or more OOK signals. The UE may then monitor those specific OOK signals to find indications of wake-up signaling for paging.

[0274] It should be understood that the entities that perform the steps described herein may be logical entities. These steps may be stored in the memory of a device, server, or computer system and executed on their processors, such as FIG. Fig.23 or Fig.28 It is contemplated that steps may be skipped, combined, or added between the exemplary methods disclosed herein. Table 4 provides example abbreviations and definitions.

[0275] Table 5 - Abbreviations and definitions

[0276]

[0277]

[0278]

[0279] Fig.11 and Fig.33 An exemplary display (e.g., a graphical user interface) that can be generated based on the methods, systems, and devices for power saving in NR as discussed herein is illustrated. A display interface 901 (e.g., a touch screen display) can provide text associated with power saving in NR in box 902, including, among other things, RRC-related parameters, monitoring of PDCCH for wake-up triggers, and other power saving method flows. The progress of any step discussed herein (e.g., a message sent or the success of a step) can be displayed with output 902 or output 903. In addition, graphical output 902 or output 903 can be displayed on display interface 901. The graphical output can be a device topology of methods, systems, and devices for implementing power saving in NR, a graphical output of the progress of any method or system discussed herein, etc.

[0280] The Third Generation Partnership Project (3GPP) develops technical standards for cellular telecommunications network technologies, including radio access, core transport networks, and service capabilities - including work on codecs, security, and quality of service. Recent radio access technology (RAT) standards include WCDMA (commonly referred to as 3G), LTE (commonly referred to as 4G), LTE-Advanced standards, and New Radio (NR), also referred to as "5G". Development of the 3GPP NR standards is expected to continue and include the definition of next generation radio access technologies (new RATs), which are expected to include the provision of new flexible radio access below 7 GHz, and the provision of new ultra-mobile broadband radio access above 7 GHz. Flexible radio access is expected to include new, non-backwards compatible radio access in new spectrum below 6 GHz, and is expected to include different operating modes that can be multiplexed together in the same spectrum to address a wide set of 3GPP NR use cases with different requirements. Ultra-mobile broadband is expected to include cmWave and mmWave spectrum, which will provide opportunities for ultra-mobile broadband access for, for example, indoor applications and hotspots. In particular, ultra-mobile broadband is expected to share a common design framework with sub-7 GHz flexible radio access, with cmWave- and mmWave-specific design optimizations.

[0281] 3GPP has identified a variety of use cases that NR is expected to support, resulting in a wide variety of user experience requirements for data rates, latency, and mobility. Use cases include the following general categories: enhanced mobile broadband (eMBB) ultra-reliable low-latency communications (URLLC), massive machine-type communications (mMTC), network operations (e.g., network slicing, routing, migration and interworking, energy saving), and enhanced vehicle-to-everything (eV2X) communications (which may include vehicle-to-vehicle communications (V2V), vehicle-to-infrastructure communications (V2I), vehicle-to-network communications (V2N), vehicle-to-pedestrian communications (V2P), and vehicle communications with other entities). Specific services and applications in these categories include, for example, monitoring sensor networks, device remote control, two-way remote control, personal cloud computing, video streaming, wireless cloud-based offices, first responder connectivity, car emergency calls, disaster alerts, real-time gaming, multi-person video calls, autonomous driving, augmented reality, tactile Internet, virtual reality, home automation, robotics, and aerial drones, among others. All of these use cases and others are contemplated herein.

[0282] Fig.32A An example communication system 100 is illustrated in which the methods and apparatus for power saving in NR described and claimed herein may be used. The communication system 100 may include a wireless transmit / receive unit (WTRU) 102a, 102b, 102c, 102d, 102e, 102f, or 102g (generally or collectively referred to as WTRU 102 or WTRU 102). The communication system 100 may include a radio access network (RAN) 103 / 104 / 105 / 103b / 104b / 105b, a core network 106 / 107 / 109, a public switched telephone network (PSTN) 108, the Internet 110, other networks 112, and network services 113. The network services 113 may include, for example, a V2X server, a V2X function, a ProSe server, a ProSe function, an IoT service, video streaming, or edge computing, etc.

[0283] It will be appreciated that the concepts disclosed herein may be used with any number of WTRUs, base stations, networks, or network elements. Each of the WTRUs 102a, 102b, 102c, 102d, 102e, 102f, or 102g may be any type of device or apparatus configured to operate or communicate in a wireless environment. Fig.32A , Fig.32B , Fig.32C , Fig.32D , Fig.32E or Fig.32FEach WTRU 102a, 102b, 102c, 102d, 102e, 102f or 102g is depicted as a handheld wireless communication device, but it should be understood that for the various use cases expected for 5G wireless communications, each WTRU may include or be implemented in any type of device or apparatus configured to transmit or receive wireless signals, and by way of example only, the device or apparatus includes a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a pager, a cellular phone, a personal digital assistant (PDA), a smart phone, a laptop, a tablet, a netbook, a notebook computer, a personal computer, a wireless sensor, a consumer electronic product, a wearable device (such as a smart watch or smart clothing), a medical or e-health device, a robot, an industrial equipment, a drone, a vehicle (such as a car, bus, truck, train or airplane, etc.).

[0284] The communication system 100 may also include a base station 114a and a base station 114b. Fig.32A In the example of , each base station 114a and 114b is depicted as a single element. In practice, the base stations 114a and 114b may include any number of interconnected base stations or network elements. The base station 114a may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, and 102c to facilitate access to one or more communication networks (e.g., the core network 106 / 107 / 109, the Internet 110, the network service 113, or other networks 112). Similarly, the base station 114b may be any type of device configured to wirelessly interface with at least one of the remote radio heads (RRHs) 118a, 118b, the transmission and reception points (TRPs) 119a, 119b, or the roadside units (RSUs) 120a and 120b to facilitate access to one or more communication networks (such as the core network 106 / 107 / 109, the Internet 110, the other networks 112, or the network services 113). The RRHs 118a, 118b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102 (e.g., WTRU 102c) to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, network services 113, or other networks 112.

[0285] The TRPs 119a, 119b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102d to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, network services 113, or other networks 112. The RSUs 120a and 120b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102e or 102f to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, network services 113, or other networks 112. By way of example, the base stations 114a, 114b may be base transceiver stations (BTSs), Node Bs, eNode Bs, Home Node Bs, Home eNode Bs, next generation Node Bs (gNodeBs), satellites, site controllers, access points (APs), wireless routers, and the like.

[0286] The base station 114a may be part of the RAN 103 / 104 / 105, which may also include other base stations or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), a relay node, etc. Similarly, the base station 114b may be part of the RAN 103b / 104b / 105b, which may also include other base stations or network elements (not shown), such as a BSC, an RNC, a relay node, etc. The base station 114a may be configured to transmit or receive wireless signals within a specific geographic area, which may be referred to as a cell (not shown). Similarly, the base station 114b may be configured to transmit or receive wired or wireless signals within a specific geographic area, which may be referred to as a cell (not shown) for methods, systems, and devices for power saving in NR, as disclosed herein. Similarly, the base station 114b may be configured to transmit or receive wired or wireless signals within a specific geographic area, which may be referred to as a cell (not shown). The cell may be further divided into cell sectors. For example, a cell associated with the base station 114a may be divided into three sectors. Thus, in an example, the base station 114a may include three transceivers, e.g., one transceiver for each sector of the cell. In an example, the base station 114a may employ multiple-input multiple-output (MIMO) technology and may therefore utilize multiple transceivers for each sector of the cell.

[0287] The base station 114a may communicate with one or more of the WTRUs 102a, 102b, 102c, or 102g over an air interface 115 / 116 / 117, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). The air interface 115 / 116 / 117 may be established using any suitable radio access technology (RAT).

[0288] The base station 114b may communicate with one or more of the RRHs 118a, 118b, TRPs 119a, 119b, or RSUs 120a, 120b via a wired or air interface 115b / 116b / 117b, which may be any suitable wired (e.g., cable, fiber optic, etc.) or wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). The air interface 115b / 116b / 117b may be established using any suitable radio access technology (RAT).

[0289] The RRH 118a, 118b, TRP 119a, 119b or RSU 120a, 120b may communicate with one or more of the WTRUs 102c, 102d, 102e, 102f via an air interface 115c / 116c / 117c, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). The air interface 115c / 116c / 117c may be established using any suitable radio access technology (RAT).

[0290] The WTRUs 102a, 102b, 102c, 102d, 102e, or 102f may communicate with each other, such as sidelink communications, via an air interface 115d / 116d / 117d, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). The air interface 115d / 116d / 117d may be established using any suitable radio access technology (RAT).

[0291] The communication system 100 may be a multiple-access system and may employ one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base station 114a in the RAN 103 / 104 / 105 and the WTRUs 102a, 102b, 102c or the RRHs 118a, 118b, TRPs 119a, 119b and RSUs 120a, 120b and the WTRUs 102c, 102d, 102e, 102f in the RAN 103b / 104b / 105b may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use Wideband CDMA (WCDMA) to establish the air interface 115 / 116 / 117 or 115c / 116c / 117c, respectively. WCDMA may include communication protocols such as High Speed ​​Packet Access (HSPA) or Evolved HSPA (HSPA+). HSPA may include High Speed ​​Downlink Packet Access (HSDPA) or High Speed ​​Uplink Packet Access (HSUPA).

[0292] In an example, the base station 114a and the WTRU 102a, 102b, 102c or the RRH 118a, 118b, TRP 119a, 119b or RSU 120a, 120b and the WTRU 102c, 102d in the RAN 103b / 104b / 105b may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish an air interface 115 / 116 / 117 or 115c / 116c / 117c using Long Term Evolution (LTE) or LTE-Advance (LTE-A), respectively. In the future, the air interface 115 / 116 / 117 or 115c / 116c / 117c may implement 3GPP NR technology. LTE and LTE-A technologies may include LTE D2D and V2X technologies and interfaces (such as sidelink communications, etc.). Similarly, 3GPP NR technology includes NR V2X technology and interfaces (such as sidelink communication, etc.).

[0293] The base station 114a in the RAN 103 / 104 / 105 and the WTRUs 102a, 102b, 102c and 102g or the RRHs 118a, 118b, TRPs 119a, 119b or RSUs 120a, 120b and the WTRUs 102c, 102d, 102e, 102f in the RAN 103b / 104b / 105b may implement a radio technology such as IEEE 802.16 (e.g., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 IX, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rates for GSM Evolution (EDGE), GSM EDGE(GERAN) etc.

[0294] For example, Fig.32A The base station 114c in may be a wireless router, a Home Node B, a Home eNode B, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in a localized area (such as a business place, a house, a vehicle, a train, an antenna, a satellite, a factory, a campus, etc.), for implementing methods, systems, and devices for power saving in NR as disclosed herein. In an example, the base station 114c and the WTRU 102 (e.g., WTRU 102e) may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). Similarly, the base station 114c and the WTRU 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another example, the base station 114c and the WTRU 102 (e.g., WTRU 102e) may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, NR, etc.) to establish a microcell or a femtocell. As Fig.32A As shown in FIG, the base station 114c may have a direct connection to the Internet 110. Therefore, the base station 114c may not be required to access the Internet 110 via the core network 106 / 107 / 109.

[0295] The RAN 103 / 104 / 105 or RAN 103b / 104b / 105b may be in communication with a core network 106 / 107 / 109, which may be any type of network configured to provide voice, data, messaging, authorization and authentication, applications, or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. For example, the core network 106 / 107 / 109 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, packet data network connectivity, Ethernet connectivity, video distribution, etc., or perform high-level security functions (such as user authentication).

[0296] Although not in Fig.32A 103 / 104 / 105 or RAN 103b / 104b / 105b or the core network 106 / 107 / 109 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 103 / 104 / 105 or RAN 103b / 104b / 105b or a different RAT. For example, in addition to being connected to the RAN 103 / 104 / 105 or RAN 103b / 104b / 105b, which may utilize E-UTRA radio technology, the core network 106 / 107 / 109 may also be in communication with another RAN (not shown) that employs GSM or NR radio technology.

[0297] The core network 106 / 107 / 109 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d, 102e to access the PSTN 108, the Internet 110, or other networks 112. The PSTN 108 may include a circuit-switched telephone network that provides plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and the Internet Protocol (IP) in the TCP / IP Internet Protocol suite. The networks 112 may include wired or wireless communication networks owned or operated by other service providers. For example, the networks 112 may include any type of packet data network (e.g., an IEEE 802.3 Ethernet network) or another core network connected to one or more RANs, which may employ the same RAT as the RAN 103 / 104 / 105 or the RAN 103b / 104b / 105b or a different RAT.

[0298] Some or all of the WTRUs 102a, 102b, 102c, 102d, 102e, and 102f in the communication system 100 may include multi-mode capabilities, for example, the WTRUs 102a, 102b, 102c, 102d, 102e, and 102f may include multiple transceivers for communicating with different wireless networks via different wireless links to implement methods, systems, and devices for power conservation in NR as disclosed herein. For example, Fig.32A The WTRU 102g shown in FIG. 1 may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114c, which may employ an IEEE 802 radio technology.

[0299] Although in Fig.32A 106 / 107 / 109. It will be appreciated that many of the concepts included herein may be equally applicable to UEs of WTRUs and UEs that use wired connections to connect to the network. For example, concepts applicable to wireless interfaces 115, 116, 117, and 115c / 116c / 117c may be equally applicable to wired connections.

[0300] Fig.32B 1 is a system diagram of an example RAN 103 and a core network 106 that may implement the methods, systems, and devices for power saving in NR as disclosed herein. As described above, the RAN 103 may employ a UTRA radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 115. The RAN 103 may also communicate with the core network 106. Fig.32B As shown in FIG. 1 , the RAN 103 may include Node-Bs 140a, 140b, and 140c, which may each include one or more transceivers for communicating with the WTRUs 102a, 102b, and 102c over the air interface 115. The Node-Bs 140a, 140b, and 140c may each be associated with a particular cell (not shown) within the RAN 103. The RAN 103 may also include RNCs 142a, 142b. It will be appreciated that the RAN 103 may include any number of Node-Bs and Radio Network Controllers (RNCs).

[0301] like Fig.32BAs shown in , Node B 140a, 140b can communicate with RNC 142a. In addition, Node B 140c can communicate with RNC 142b. Node B 140a, 140b and 140c can communicate with corresponding RNC 142a and 142b via Iub interface. RNC 142a and 142b can communicate with each other via Iur interface. Each of RNC 142a and 142b can be configured to control the corresponding Node B 140a, 140b and 140c to which it is connected. In addition, each of RNC 142a and 142b can be configured to perform or support other functions, such as outer loop power control, load control, admission control, packet scheduling, handover control, macro diversity, security function, data encryption, etc.

[0302] Fig.32B The core network 106 shown in FIG. 1 may include a media gateway (MGW) 144, a mobile switching center (MSC) 146, a serving GPRS support node (SGSN) 148, or a gateway GPRS support node (GGSN) 150. Although each of the aforementioned elements is depicted as part of the core network 106, it will be appreciated that any of these elements may be owned or operated by an entity other than the core network operator.

[0303] The RNC 142a in the RAN 103 may be connected to the MSC 146 in the core network 106 via an IuCS interface. The MSC 146 may be connected to the MGW 144. The MSC 146 and the MGW 144 may provide the WTRUs 102a, 102b, and 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, and 102c and traditional land-line communications devices.

[0304] The RNC 142a in the RAN 103 may also be connected to the SGSN 148 in the core network 106 via an IuPS interface. The SGSN 148 may be connected to the GGSN 150. The SGSN 148 and the GGSN 150 may provide the WTRUs 102a, 102b, and 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, and 102c and IP-enabled devices.

[0305] The core network 106 may also be connected to other networks 112, which may include other wired or wireless networks owned or operated by other service providers.

[0306] Fig.32C1 is a system diagram of an example RAN 104 and a core network 107 that may implement the methods, systems, and apparatus for power saving in NR as disclosed herein. As described above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 116. The RAN 104 may also be in communication with the core network 107.

[0307] The RAN 104 may include eNode-Bs 160a, 160b, and 160c, although it will be appreciated that the RAN 104 may include any number of eNode-Bs. The eNode-Bs 160a, 160b, and 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, and 102c over the air interface 116. For example, the eNode-Bs 160a, 160b, and 160c may implement MIMO technology. Thus, for example, the eNode-B 160a may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a.

[0308] Each of the eNode-Bs 160a, 160b, and 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, user scheduling in uplink or downlink, etc. Fig.32C As shown in FIG, eNode-Bs 160a, 160b, and 160c may communicate with each other via an X2 interface.

[0309] Fig.32C The core network 107 shown in FIG. 1 may include a mobility management gateway (MME) 162, a serving gateway 164, and a packet data network (PDN) gateway 166. While each of the aforementioned elements is depicted as part of the core network 107, it should be appreciated that any of these elements may be owned or operated by an entity other than the core network operator.

[0310] The MME 162 may be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, and 102c, bearer activation / deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, and 102c, etc. The MME 162 may also provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM or WCDMA.

[0311] The serving gateway 164 may be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN 104 via an S1 interface. The serving gateway 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, and 102c. The serving gateway 164 may also perform other functions, such as anchoring a user plane during an inter-eNode B handover, triggering paging when downlink data is available for the WTRUs 102a, 102b, and 102c, managing and storing contexts of the WTRUs 102a, 102b, and 102c, and the like.

[0312] The serving gateway 164 may also be connected to the PDN gateway 166, which may provide the WTRUs 102a, 102b, and 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0313] The core network 107 may facilitate communications with other networks. For example, the core network 107 may provide the WTRUs 102a, 102b, and 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, and 102c and traditional land-line communications devices. For example, the core network 107 may include or may communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the core network 107 and the PSTN 108. In addition, the core network 107 may provide the WTRUs 102a, 102b, and 102c with access to the networks 112, which may include other wired or wireless networks owned or operated by other service providers.

[0314] Fig.32D 1 is a system diagram of an example RAN 105 and a core network 109 that may implement the methods, systems, and devices for power saving in NR as disclosed herein. The RAN 105 may employ NR radio technology to communicate with the WTRUs 102a and 102b over the air interface 117. The RAN 105 may also be in communication with the core network 109. A non-3GPP interworking function (N3IWF) 199 may employ non-3GPP radio technology to communicate with the WTRU 102c over the air interface 198. The N3IWF 199 may also be in communication with the core network 109.

[0315] The RAN 105 may include gNode-Bs 180a and 180b. It will be appreciated that the RAN 105 may include any number of gNode-Bs. The gNode-Bs 180a and 180b may each include one or more transceivers for communicating with the WTRUs 102a and 102b over the air interface 117. When an integrated access and backhaul connection is used, the same air interface may be used between the WTRUs and the gNode-Bs, which may be a core network 109 via one or more gNBs. The gNode-Bs 180a and 180b may implement MIMO, MU-MIMO, or digital beamforming techniques. Thus, for example, the gNode-B 180a may use multiple antennas to transmit wireless signals to and receive wireless signals from the WTRU 102a. It should be appreciated that the RAN 105 may employ other types of base stations, such as an eNode-B. It should also be appreciated that the RAN 105 may employ more than one type of base station. For example, RAN may employ eNode-B and gNode-B.

[0316] The N3IWF 199 may include a non-3GPP access point 180c. It will be appreciated that the N3IWF 199 may include any number of non-3GPP access points. The non-3GPP access point 180c may include one or more transceivers for communicating with the WTRU 102c over the air interface 198. The non-3GPP access point 180c may communicate with the WTRU 102c over the air interface 198 using the 802.11 protocol.

[0317] Each of the gNode-Bs 180a and 180b may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, user scheduling in uplink or downlink, etc. Fig.32D As shown in , for example, gNode-Bs 180a and 180b may communicate with each other via an Xn interface.

[0318] Fig.32D The core network 109 shown in the figure may be a 5G core network (5GC). The core network 109 may provide a variety of communication services to customers interconnected by a radio access network. The core network 109 includes multiple entities that perform the functions of the core network. As used herein, the term "core network entity" or "network function" refers to any entity that performs one or more functions of the core network. It should be understood that such a core network entity may be a device or computer system (such as a 5G core network) stored in a device or computer system configured for wireless or network communications. Figure 32G A logical entity implemented in the form of computer-executable instructions (software) stored in a memory of the system 90 shown in FIG. 1 and executed on a processor thereof.

[0319] exist Fig.32D In the example of , the 5G core network 109 may include access and mobility management function (AMF) 172, session management function (SMF) 174, user plane function (UPF) 176a and 176b, user data management function (UDM) 197, authentication server function (AUSF) 190, network exposure function (NEF) 196, policy control function (PCF) 184, non-3GPP interworking function (N3IWF) 199, user data repository (UDR) 178. Although each of the aforementioned elements is depicted as part of the 5G core network 109, it should be recognized that any of these elements may be owned or operated by an entity other than the core network operator. It will also be recognized that the 5G core network may not consist of all of these elements, may consist of additional elements, and may consist of multiple instances of each of these elements. Fig.32D The network functions are shown connected directly to each other, however, it should be appreciated that they may communicate via a routing agent such as a diameter routing agent or a message bus.

[0320] exist Fig.32D In the example of , the connectivity between network functions is realized via a set of interfaces or reference points. It will be appreciated that a network function can be modeled, described or realized as a set of services that are invoked or called by other network functions or services. The invocation of network function services can be realized via direct connections between network functions, exchange of message passing on a message bus, calling software functions, etc.

[0321] The AMF 172 may be connected to the RAN 105 via an N2 interface and may serve as a control node. For example, the AMF 172 may be responsible for registration management, connection management, reachability management, access authentication, access authorization. The AMF may be responsible for forwarding user plane tunnel configuration information to the RAN 105 via the N2 interface. The AMF 172 may receive user plane tunnel configuration information from the SMF via the N11 interface. The AMF 172 may generally route and forward NAS packets to / from the WTRUs 102a, 102b, and 102c via the N1 interface. The N1 interface is not used in Fig.32D Shown in.

[0322] The SMF 174 may be connected to the AMF 172 via an N11 interface. Similarly, the SMF may be connected to the PCF 184 via an N7 interface and to the UPFs 176a and 176b via an N4 interface. The SMF 174 may serve as a control node. For example, the SMF 174 may be responsible for session management, IP address allocation for the WTRUs 102a, 102b, and 102c, management and configuration of traffic steering rules in the UPFs 176a and 176b, and generation of downlink data notifications to the AMF 172.

[0323] The UPF 176a and UPF 176b may provide the WTRUs 102a, 102b, and 102c with access to a packet data network (PDN), such as the Internet 110, to facilitate communication between the WTRUs 102a, 102b, and 102c and other devices. The UPF 176a and UPF 176b may also provide the WTRUs 102a, 102b, and 102c with access to other types of packet data networks. For example, the other network 112 may be an Ethernet network or any type of network that exchanges packets of data. The UPF 176a and UPF 176b may receive traffic steering rules from the SMF 174 via an N4 interface. The UPF 176a and UPF 176b may provide access to a packet data network by connecting the packet data network to an N6 interface or by connecting to each other and to other UPFs via an N9 interface. In addition to providing access to the packet data network, UPF 176 may also be responsible for packet routing and forwarding, policy rule enforcement, quality of service handling of user plane traffic, and downlink packet buffering.

[0324] The AMF 172 may also be connected to the N3IWF 199, for example, via an N2 interface. The N3IWF facilitates connectivity between the WTRU 102c and the 5G core network 170, for example, via a 3GPP undefined radio interface technology. The AMF may interact with the N3IWF 199 in the same or similar manner as it interacts with the RAN 105.

[0325] PCF 184 may be connected to SMF 174 via an N7 interface, may be connected to AMF 172 via an N15 interface, and may be connected to application function (AF) 188 via an N5 interface. The N15 and N5 interfaces are not Fig.32D1. The PCF 184 may provide policy rules to control plane nodes such as the AMF 172 and the SMF 174, thereby allowing the control plane nodes to enforce these rules. The PCF 184 may send policies for the WTRUs 102a, 102b, and 102c to the AMF 172 so that the AMF may deliver the policies to the WTRUs 102a, 102b, and 102c via the N1 interface. The policies may then be enforced or applied at the WTRUs 102a, 102b, and 102c.

[0326] The UDR 178 may act as a repository for authentication credentials and subscription information. The UDR may be connected to network functions so that the network functions may add to, read, and modify data in the repository. For example, the UDR 178 may be connected to the PCF 184 via an N36 interface. Similarly, the UDR 178 may be connected to the NEF 196 via an N37 interface, and the UDR 178 may be connected to the UDM 197 via an N35 interface.

[0327] The UDM 197 may serve as an interface between the UDR 178 and other network functions. The UDM 197 may authorize network functions to access the UDR 178. For example, the UDM 197 may be connected to the AMF 172 via the N8 interface, and the UDM 197 may be connected to the SMF 174 via the N10 interface. Similarly, the UDM 197 may be connected to the AUSF 190 via the N13 interface. The UDR 178 and the UDM 197 may be tightly integrated.

[0328] The AUSF 190 performs operations related to authentication and is connected to the UDM 178 via the N13 interface and to the AMF 172 via the N12 interface.

[0329] NEF 196 exposes the capabilities and services in the 5G core network 109 to the application function (AF) 188. The exposure can occur on the N33 API interface. NEF can be connected to AF 188 via the N33 interface and it can be connected to other network functions to expose the capabilities and services of the 5G core network 109.

[0330] The application function 188 may interact with the network function in the 5G core network 109. The interaction between the application function 188 and the network function may occur via a direct interface or may occur via the NEF 196. The application function 188 may be considered part of the 5G core network 109 or may be external to the 5G core network 109 and deployed by an enterprise having a business relationship with a mobile network operator.

[0331] Network slicing is a mechanism that mobile network operators can use to support one or more "virtual" core networks behind the operator's air interface. This involves "slicing" the core network into one or more virtual networks to support different RANs or different service types running across a single RAN. Network slicing enables operators to create networks that are customized to provide optimized solutions for different market scenarios that require different requirements (for example, in terms of functionality, performance and isolation).

[0332] 3GPP has designed the 5G core network to support network slicing. Network slicing is a great tool that network operators can use to support a diverse set of 5G use cases (e.g., massive IoT, critical communications, V2X, and enhanced mobile broadband) that have very diverse and sometimes extreme requirements. Without using network slicing technology, the network architecture may not be flexible and scalable enough to efficiently support a wide range of use case requirements when each use case has its own specific set of performance, scalability, and availability requirements. In addition, the introduction of new network services should be made more efficient.

[0333] Reference again Fig.32D In a network slicing scenario, the WTRU 102a, 102b, or 102c may be connected to the AMF 172 via the N1 interface. The AMF may be logically part of one or more slices. The AMF may coordinate the connection or communication of the WTRU 102a, 102b, or 102c with one or more UPFs 176a and 176b, SMF 174, and other network functions. Each of the UPFs 176a and 176b, the SMF 174, and other network functions may be part of the same slice or different slices. When they are part of different slices, they may be isolated from each other in the sense that they may utilize different computing resources, security credentials, etc.

[0334] The core network 109 may facilitate communications with other networks. For example, the core network 109 may include or may communicate with an IP gateway (such as an IP Multimedia Subsystem (IMS) server) that serves as an interface between the 5G core network 109 and the PSTN 108. For example, the core network 109 may include or communicate with a short message service (SMS) service center, which facilitates communication via short message service. For example, the 5G core network 109 may facilitate the exchange of non-IP data packets between the WTRUs 102a, 102b, and 102c and a server or application function 188. In addition, the core network 170 may provide the WTRUs 102a, 102b, and 102c with access to the networks 112, which may include other wired or wireless networks owned or operated by other service providers.

[0335] This article describes and Fig.32A , Fig.32C , Fig.32D or Fig.32E The core network entities shown in the figure are identified by the names given to those entities in certain existing 3GPP specifications, but it will be appreciated that those entities and functions may be identified by other names in the future, and that certain entities or functions may be combined in future specifications published by 3GPP (including future 3GPP NR specifications). Fig.32A , Fig.32B , Fig.32C , Fig.32D or Fig.32E Although specific network entities and functionality are described and illustrated in the specification, it should be understood that the subject matter disclosed and claimed herein may be implemented or realized in any similar communication system, whether currently defined or defined in the future.

[0336] Fig.32E An example communication system 111 is illustrated in which the systems, methods, and apparatus described herein for implementing power savings in NR may be used. The communication system 111 may include wireless transmit / receive units (WTRUs) A, B, C, D, E, F, a base station gNB 121, a V2X server 124, and roadside units (RSUs) 123a and 123b. In practice, the concepts presented herein may be applied to any number of WTRUs, base stations gNBs, V2X networks, or other network elements. One or several or all of the WTRUs A, B, C, D, E, and F may be outside the range of the access network coverage 131. WTRUs A, B, and C form a V2X group, where WTRU A is the group leader and WTRUs B and C are group members.

[0337] If WTRUs A, B, C, D, E, and F are within access network coverage 131, they may communicate with each other via gNB 121 over the Uu interface 129. Fig.32E In the example of FIG. 1 , WTRUs B and F are shown within access network coverage 131. WTRUs A, B, C, D, E, and F may communicate to each other directly via a sidelink interface (e.g., PC5 or NR PC5) such as interface 125a, 125b, or 128 whether they are within access network coverage 131 or outside access network coverage 131. For example, in Fig.32E In the example of , WTRU D outside the access network coverage 131 communicates with WTRU F inside the coverage 131.

[0338] WTRUs A, B, C, D, E, and F may communicate with the RSU 123a or 123b via the vehicle-to-network (V2N) 133 or the sidelink interface 125b. WTRUs A, B, C, D, E, and F may communicate with the V2X server 124 via the vehicle-to-infrastructure (V2I) interface 127. WTRUs A, B, C, D, E, and F may communicate with another UE via the vehicle-to-person (V2P) interface 128.

[0339] Fig.32F is a block diagram of an example apparatus or device WTRU 102 that may be configured for wireless communication and operation in accordance with the systems, methods, and apparatus for implementing power savings in NR described herein, such as Fig.32A , Fig.32B , Fig.32C , Fig.32D or Fig.32E , Figure 21 or Fig.28 WTRU 102 (e.g., UE 99 or gNB 98). Fig.32F As shown in , the example WTRU 102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad / indicator 128, a non-removable memory 130, a removable memory 132, a power supply 134, a global positioning system (GPS) chipset 136, and other peripherals 138. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements. Moreover, the base stations 114a and 114b or the nodes that the base stations 114a and 114b may represent (such as, but not limited to, a transceiver station (BTS), a Node B, a site controller, an access point (AP), a Home Node B, an evolved Home Node B (eNodeB), a Home Evolved Node B (HeNB), a Home Evolved Node B gateway, a Next Generation Node B (gNode-B), and a proxy node, among others) may include Fig.32F Some or all of the elements depicted in and may be exemplary embodiments of performing the disclosed method for power saving in NR described herein.

[0340] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal coding, data processing, power control, input / output processing, or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although Fig.32F The processor 118 and the transceiver 120 are depicted as separate components, but it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

[0341] The transmit / receive element 122 of the UE may be configured to transmit data to a base station (eg, Fig.32A The transmit / receive element 122 may be a base station 114a) of a wireless communication network, or may transmit or receive signals to or from another UE via an air interface 115d / 116d / 117d. For example, the transmit / receive element 122 may be an antenna configured to transmit or receive RF signals. The transmit / receive element 122 may be a transmitter / detector configured to transmit or receive IR, UV, or visible light signals, for example. The transmit / receive element 122 may be configured to transmit and receive both RF and optical signals. It will be appreciated that the transmit / receive element 122 may be configured to transmit or receive any combination of wireless or wired signals.

[0342] In addition, although the transmit / receive element 122 is Fig.32F Although depicted as a single element in the figure, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 115 / 116 / 117.

[0343] The transceiver 120 may be configured to modulate signals to be transmitted by the transmit / receive element 122 and demodulate signals received by the transmit / receive element 122. As described above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs (e.g., NR and IEEE 802.11 or NR and E-UTRA) or to communicate with the same RAT via multiple beams to different RRHs, TRPs, RSUs, or nodes.

[0344] The processor 118 of the WTRU 102 may be coupled to a speaker / microphone 124, a keypad 126, or a display / touchpad / indicator 128 (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit), and may receive user input data therefrom. The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, or the display / touchpad / indicator 128. In addition, the processor 118 may access information from and store data in any type of suitable memory, such as a non-removable memory 130 or a removable memory 132. The non-removable memory 130 may include a random access memory (RAM), a read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, etc. The processor 118 may access information from and store data in a memory that is not physically located on the WTRU 102, such as on a server hosted in a cloud or edge computing platform or in a home computer (not shown). The processor 118 may be configured to control a lighting pattern, image, or color on the display or indicator 128 in response to whether the setting of power savings in NR in some examples described herein is successful or unsuccessful, or otherwise indicate the status of power savings in NR and associated components. The control lighting pattern, image, or color on the display or indicator 128 may reflect the diagrams illustrated or discussed herein (e.g., FIGS. 1 to 3). Fig.31 124, keypad 126, or display / touchpad / indicator 128), and among other things, request, configure, or query information related to power saving in NR, which can be displayed on the display 128.

[0345] The processor 118 may receive power from the power source 134 and may be configured to distribute or control the power to other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries, solar cells, fuel cells, etc.

[0346] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to or in lieu of the information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) over the air interface 115 / 116 / 117 or determine its location based on the timing of signals received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by any suitable location-determination method.

[0347] The processor 118 may also be coupled to other peripherals 138, which may include one or more software or hardware modules that provide additional features, functionality, or wired or wireless connectivity. For example, the peripherals 138 may include various sensors such as accelerometers, biometric (e.g., fingerprint) sensors, electronic compasses, satellite transceivers, digital cameras (for photos or videos), universal serial bus (USB) ports or other interconnect interfaces, vibration devices, television transceivers, hands-free headsets, modules, FM radio units, digital music players, media players, video game player modules, internet browsers, etc.

[0348] The WTRU 102 may be included in other devices or equipment, such as sensors, consumer electronics, wearable devices (such as smart watches or smart clothing), medical or e-health equipment, robots, industrial equipment, drones, vehicles (such as cars, trucks, trains or airplanes, etc.) The WTRU 102 may be connected to other components, modules or systems of such devices or equipment via one or more interconnect interfaces (such as an interconnect interface that may include one of the peripheral devices 138).

[0349] Figure 32G is a block diagram of an exemplary computing system 90 in which Fig.32A , Fig.32C , Fig.32D and Fig.32E One or more devices of a communication network shown in and power saving in NR, such as FIG. 21 or Fig.28The systems and methods shown in and other systems and methods described and claimed herein, such as certain nodes or functional entities in the RAN 103 / 104 / 105, the core network 106 / 107 / 109, the PSTN 108, the Internet 110, other networks 112, or network services 113. The computing system 90 may include a computer or a server and may be primarily controlled by computer-readable instructions, which may be in the form of software, wherever, whenever, or by any means to store or access such software. Such computer-readable instructions may be executed within the processor 91 to enable the computing system 90 to work. The processor 91 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 91 may perform signal encoding, data processing, power control, input / output processing, or any other function that enables the computing system 90 to operate in a communication network. The coprocessor 81 is an optional processor different from the main processor 91, which can perform additional functions or assist the processor 91. The processor 91 or the coprocessor 81 can receive, generate and process data related to the method and apparatus for power saving in NR disclosed herein.

[0350] In operation, processor 91 fetches, decodes and executes instructions, and transfers information to and from other resources via the computing system's main data transfer path, system bus 80. Such a system bus connects components in computing system 90 and defines a medium for data exchange. System bus 80 typically includes data lines for sending data, address lines for sending addresses, and control lines for sending interrupts and for operating the bus. An example of such a system bus 80 is a PCI (Peripheral Component Interconnect) bus.

[0351] The memory coupled to the system bus 80 includes a random access memory (RAM) 82 and a read-only memory (ROM) 93. Such memory includes a circuit system that allows information to be stored and retrieved. ROM 93 generally includes stored data that is not easily modified. The data stored in RAM 82 can be read or changed by a processor 91 or other hardware device. Access to RAM 82 or ROM 93 can be controlled by a memory controller 92. The memory controller 92 can provide an address translation function that translates a virtual address into a physical address when an instruction is executed. The memory controller 92 can also provide a memory protection function that isolates processes within the system and isolates system processes from user processes. Therefore, a program running in the first mode can only access memory mapped by its own process virtual address space; unless memory sharing between processes has been set up, it cannot access memory within the virtual address space of another process.

[0352] In addition, the computing system 90 may include a peripheral device controller 83 that is responsible for transmitting instructions from the processor 91 to peripheral devices, such as a printer 94 , a keyboard 84 , a mouse 95 , and a disk drive 85 .

[0353] The display 86 controlled by the display controller 96 is used to display the visual output generated by the computing system 90. Such visual output may include text, graphics, animated graphics, and video. The visual output may be provided in the form of a graphical user interface (GUI). The display 86 may be implemented with a CRT-based video display, an LCD-based flat panel display, a gas plasma-based flat panel display, or a touch pad. The display controller 96 includes the electronic components required to generate the video signal sent to the display 86.

[0354] In addition, the computing system 90 may include communication circuitry, such as, for example, a wireless or wired network adapter 97, which may be used to connect the computing system 90 to an external communication network or device (such as the RAN 103 / 104 / 105, the core network 106 / 107 / 109, the PSTN 108, the Internet 110, the WTRU 102, or Fig.32A , Fig.32B , Fig.32C , Fig.32D or Fig.32E Other networks 112) to enable computing system 90 to communicate with other nodes or functional entities of those networks. Alone or in combination with processor 91, the communication circuit system can be used to perform the transmission and reception steps of certain devices, nodes or functional entities described herein.

[0355] It should be understood that any or all of the devices, systems, methods, and processes described herein may be implemented in the form of computer executable instructions (e.g., program code) stored on a computer-readable storage medium, which, when executed by a processor (such as processor 118 or 91), causes the processor to perform or implement the systems, methods, and processes described herein. Specifically, any step, operation, or function described herein may be implemented in the form of such computer executable instructions executed on a processor of a device or computing system configured for wireless or wired network communication. Computer-readable storage media include volatile and non-volatile, removable and non-removable media implemented in any non-transient (e.g., tangible or physical) method or technology for storing information, but such computer-readable storage media do not include signals. Computer-readable storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, cassette, tape, disk storage or other magnetic storage device, or any other tangible or physical medium that can be used to store desired information and can be accessed by a computing system.

[0356] In describing the preferred methods, systems or apparatus of the subject matter of the present disclosure (Power Saving in NR) as shown in the figures, specific terminology is employed for the sake of clarity. However, the claimed subject matter is not intended to be limited to the specific terminology so selected, and it is to be understood that each specific element includes all technical equivalents that operate in a similar manner to accomplish a similar purpose.

[0357] The various techniques described herein can be implemented in combination with hardware, firmware, software or in combination thereof when appropriate. Such hardware, firmware and software can reside in the device at each node of the communication network. The device can be operated individually or in combination with each other to implement the method described herein. As used herein, the terms "device", "network device", "node", "equipment", "network node" etc. can be used interchangeably. In addition, unless otherwise provided herein, the use of the word "or" is generally used inclusively.

[0358] This written description uses examples to disclose the invention, including the best mode, and also enables any person skilled in the art to practice the invention, including making and using any device or system and performing any combined method. The patentable scope of the invention is defined by the claims, and may include other examples that occur to those skilled in the art (e.g., skipping steps, combining steps, or adding steps between the exemplary methods disclosed herein). If such other examples have structural elements that do not differ from the literal language of the claims, or if they include equivalent structural elements that do not differ substantially from the literal language of the claims, it is intended that these other examples be included within the scope of the claims.

[0359] In the discussion herein, a signal for sending a UE to micro-sleep may be referred to as a go to sleep (GTS) signal. A signal for waking up a UE in sleep mode may be referred to as a wake-up signal. In the remaining discussion, the wake-up and GTS signals are referred to as power saving signals. Although specific examples may apply to either the wake-up signal or the GTS, a solution applicable to one signal may also apply to the other signal.

[0360] The methods, systems, apparatus (e.g., user equipment), or computer-readable storage media, etc. described herein may provide a means for saving power in a new radio. The method, system, computer-readable storage medium, or apparatus has a means for: periodically monitoring the PDCCH to find a wake-up trigger that provides an aperiodic TRS; and when the UE receives the wake-up trigger, switching back to the BWP W, and uses aperiodic TRS to fine-tune its timing and frequency. The method, system, computer-readable storage medium or device has means for: waking up when OnDuraction occurs for the user equipment; during OnDuration, monitoring PDCCH at a first monitoring opportunity to find a wake-up trigger; and waking up when the UE receives a wake-up trigger of the PDCCH at the first monitoring opportunity; otherwise sleeping in OnDuration and not monitoring other opportunities. The method, system, computer-readable storage medium or device has means for: obtaining a message of multiple power saving configurations (PSCs) for the user equipment; and activating one of the PSCs based on the traffic conditions or application. The method, system, computer-readable storage medium or device has means for: operating in a dormant state when the user equipment is in RRC connected mode; and performing one or more of the following based on being in a dormant state: 1) reporting measurements or tracking through a PCell or PSCell; or 2) monitoring activations indicated on the PCell or PSCell through higher layer signaling or through L1 signaling, and limiting the number of blind decodings. The method, system, computer-readable storage medium or device has means for bundling an SCell that supplements a PCell or PSCell. The method, system, computer-readable storage medium or device has means for activating a bundling in a dormant state when sending an SR on a PCell or SCell. The method, system, computer-readable storage medium or device has means for: receiving a power saving signal indicating its sleep through DL control information during its DRX active time; and the UE sleeps when receiving it. The method, system, computer-readable storage medium or device enters sleep upon detection of a power saving signal based on receiving a power saving signal with a command to sleep during the active duration for DRX until the next monitoring opportunity of the power saving signal. The signal (e.g., a control signal) may be a UL or DL ​​authorization. The field indicating the control signal in the BWP for authorization may be reused to indicate a power saving state. All combinations (including removal or addition of steps) in this paragraph and subsequent paragraphs may be expected in a manner consistent with other parts of the detailed description.

[0361] The methods, systems, devices (e.g., user equipment) or computer-readable storage media, etc. described herein may provide means for power saving mechanisms in new radios. The methods, systems, computer-readable storage media or devices have means for: waking up before the device (e.g., UE) OnDuration to monitor a power saving signal in a monitoring opportunity that can be configured by RRC signaling; based on detecting the power saving signal, determining whether a subsequent OnDuration (e.g., the next onDuration, which may be the OnDuration immediately following the monitoring opportunity) must be monitored; if the power saving signal indicates that it is awakened, the device may monitor the subsequent OnDuration; and if the power saving signal indicates that the device enters a sleep state, the device cannot monitor the subsequent OnDuration, and the UE may sleep until the next monitoring period for the power saving signal. Since the monitoring opportunity for the power saving signal occurs before the onDuration, the next OnDuration may refer to the onDuration after (usually immediately following) the monitoring opportunity for the power saving signal. The power saving signal may be indicated by a DL control signal. The DL control signal can be configured in a UE-specific manner or in a multicast manner (e.g., a group-shared PDCCH) that can be received by multiple UEs. The UE-specific manner can be regarded as a UE-specific identifier that can be used for the control signal. Therefore, only the UE with the identifier can decode it. Regarding the multicast manner, multiple UEs are configured with the same identifier, so when a control signal with the identifier is signaled, they can decode it. If the device does not detect a power saving signal during the monitoring opportunity, it can wake up to monitor the next OnDuration. If the device does not detect a power saving signal during the monitoring opportunity, it can go to sleep and may not monitor the next OnDuration. The device can monitor the power saving signal in the first BWP and switch to the second BWP to monitor OnDuration. The first BWP may be different from the second BWP. The DL control signal can be identified by the identifier MS-RNTI configured to the UE via RRC. The power saving signal can be monitored on resources specifically allocated for the power saving signal. If the UE cannot detect the power saving signal, it wakes up to monitor OnDuration (just as if the power saving signal was detected).A method, system, computer-readable storage medium, or device has means for: waking up before the OnDuration of a discontinuous reception cycle on Cell1 (e.g., the first cell) to monitor a power saving signal (which may be in a monitoring opportunity configured by a radio resource control, etc.); based on the power saving signal, determining whether to monitor a subsequent OnDuration; and based on a command received on Cell1, determining the behavior of activating, deactivating, waking up, or sleeping on other cells monitored by the device. A method may monitor for an indication of sleeping during an active time of a discontinuous reception cycle (which may be during a reception authorization); and based on receiving an indication of sleeping during an active time that may be a discontinuous reception cycle, switching to a lower power operating state until the next monitoring opportunity of a power saving signal. The active time may be considered to be the OnDuration or a period when a drxInactivityTimer is running. The active time may represent the OnDuration+drxInactivitytimer. All combinations of this paragraph and the preceding paragraphs (including deletion or addition of steps) are contemplated.

Claims

1. An apparatus for performing wireless communication, the apparatus comprising: processor; as well as A memory coupled to the processor, the memory including executable instructions stored thereon, the executable instructions causing the processor to perform operations including the following when executed by the processor: monitoring a power saving signal in a monitoring opportunity before OnDuration of a discontinuous reception cycle on the first cell; detecting a power saving signal in the monitoring opportunity, wherein the apparatus is configured to monitor a Physical Downlink Control Channel (PDCCH) transmission during an OnDuration of the discontinuous reception period if the power saving signal is not detected; receiving an indication of sleeping during an active time of the discontinuous reception cycle; and Switch to a low power operating state until the next monitoring opportunity for a power save signal. 2 . The apparatus of claim 1 , the operations further comprising sleeping until a next monitoring period of the power save signal when the power save signal includes an indication to sleep.

3. The apparatus according to claim 1, wherein the operation further comprises: monitoring the first bandwidth portion for a power save signal; as well as Switch to the second bandwidth portion to monitor PDCCH transmission during the OnDuration of the discontinuous reception period. The apparatus according to claim 1 , wherein the power saving signal is indicated by a downlink control signal.

5. The apparatus of claim 1, wherein the power save signal is indicated by a downlink control signal, wherein the downlink control signal is configured in a device-specific manner, wherein the apparatus is a wireless transmit / receive unit (WTRU).

6. The apparatus of claim 1, wherein the power saving signal is indicated by a downlink control signal, wherein the downlink control signal is configured in a multicast manner and is received by a plurality of wireless transmit / receive units WTRU.

7. The apparatus according to claim 1, wherein the power saving signal is indicated by a downlink control signal, wherein the downlink control signal is identified by an identifier of a micro-sleep-radio network temporary identity, and the identifier is configured to the apparatus through radio resource control signaling.

8. The apparatus of claim 4, wherein the power save signal is monitored on resources specifically allocated for the power save signal by radio resource control signaling.

9. The apparatus of claim 1, wherein the operations further comprise: Based on the power saving signal, determining whether to monitor a subsequent OnDuration, wherein the determining comprises: When the power saving signal includes an indication of waking up, monitoring a subsequent OnDuration on the first cell, When the power save signal includes an indication of sleep, not monitoring a subsequent OnDuration on the first cell; and Based on the command received on the first cell, a behavior of activation, deactivation, wake-up or sleep on a second cell monitored by the device is determined.

10. A method of wireless communication performed by a wireless transmit / receive unit WTRU, the method comprising: monitoring the power saving signal in a monitoring opportunity configured by radio resource control before OnDuration of the discontinuous reception cycle on the first cell; determining whether a power save signal is detected during the monitoring opportunity; monitoring a physical downlink control channel (PDCCH) transmission during an OnDuration period of the discontinuous reception period if no power saving signal is detected in the monitoring opportunity; monitoring PDCCH transmission during OnDuration of the discontinuous reception cycle in a case where a power saving signal is detected in the monitoring opportunity and the power saving signal includes a wake-up indication; In case a power saving signal is detected in the monitoring opportunity and the power saving signal includes a sleep indication, avoiding monitoring PDCCH transmission during the OnDuration of the discontinuous reception cycle; receiving an indication of sleeping during an active time of at least one discontinuous reception cycle; and Switch to a lower power operating state until the next monitoring opportunity for a power save signal.

11. The method according to claim 10, further comprising: monitoring the first bandwidth portion for a power save signal; as well as Switch to the second bandwidth portion to monitor PDCCH transmission during the OnDuration of the discontinuous reception period.

12. The method according to claim 10, further comprising: Based on the command received on the first cell, a behavior of activation, deactivation, wake-up or sleep on a second cell monitored by the device is determined.

13. The method of claim 10, wherein the power save signal is indicated via a downlink control signal, wherein the downlink control signal is configured in a WTRU-specific manner.

14. The method of claim 10, wherein the power saving signal is indicated by a downlink control signal, wherein the downlink control signal is configured in a multicast manner and received by a plurality of WTRUs.

15. The method of claim 10, wherein the power saving signal is indicated by a downlink control signal, wherein the downlink control signal is identified by an identifier of a micro-sleep-radio network temporary identity, and the identifier is configured to the WTRU through radio resource control signaling.

16. The method of claim 10, wherein monitoring for power save signals is performed on resources specifically allocated for power save signals.

17. A wireless transmit / receive unit WTRU, comprising a processor and a memory, wherein the processor and the memory are configured to: monitoring the power saving signal in a monitoring opportunity before the OnDuration of the discontinuous reception period; determining whether a power save signal is detected during the monitoring opportunity; monitoring a physical downlink control channel (PDCCH) transmission during an OnDuration period of the discontinuous reception period if no power saving signal is detected in the monitoring opportunity; monitoring PDCCH transmission during OnDuration of the discontinuous reception cycle in a case where a power saving signal is detected in the monitoring opportunity and the power saving signal includes a wake-up indication; In case a power saving signal is detected in the monitoring opportunity and the power saving signal includes a sleep indication, avoiding monitoring PDCCH transmission during the OnDuration of the discontinuous reception cycle; receiving an indication of sleeping during an active time of at least one discontinuous reception cycle; and Switch to a lower power operating state until the next monitoring opportunity for a power save signal.

18. The WTRU of claim 17, wherein the indication of sleep is received while a discontinuous reception inactivity timer is running.

19. The WTRU of claim 17, wherein the power save signal corresponds to a downlink control channel message.

20. The WTRU of claim 17, wherein the power save signal corresponds to a downlink control channel message received in a common search space.

21. A wireless transmission / receiving unit WTRU, comprising: processor; and memory, wherein the processor is configured to: receiving downlink control information DCI, the DCI comprising a cell activation indication and an indication of a bandwidth part BWP to be monitored in the cell; switching from a dormant state to an active state based on receiving the cell activation indication; as well as The BWP is monitored in the cell in an active state.

Images