Method and device for reducing power consumption by carrier aggregation in wireless communication system
By using DCI format to indicate the sleep state of the cell in the wireless communication system, the UE and the network side jointly switch the cell, solving the problem of high power consumption during carrier aggregation, achieving the extension of the device battery life and improving the system energy efficiency.
Patent Information
- Application Number
- CN202110389988.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2020-04-15
- Filing Date
- 2021-04-12
- Publication Date
- 2024-11-05
- Estimated Expiration
- 2041-04-12
AI Technical Summary
In wireless communication systems, the prior art is difficult to effectively reduce power consumption during carrier aggregation, especially in cross-carrier scheduling and inter-cell spectrum sharing scenarios, resulting in a shortening of device battery life and an increase in power consumption.
By monitoring the dormant information of a specific cell on the user equipment (UE) and the network side, indicating the sleep state of the cell using the DCI format, the UE and the network side jointly switch the cell, thereby reducing unnecessary signal monitoring and transmission and realizing power saving.
Effectively reduces power consumption of wireless communication devices, extends battery life, and improves the overall energy efficiency of the system, especially during low data load periods.
Smart Images

Figure CN113543292B_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 010,223, filed on April 15, 2020, the entire disclosure of which is incorporated herein by reference in its entirety. Technical Field
[0003] The present disclosure relates generally to wireless communication networks, and more particularly to a method and apparatus for reducing power consumption by carrier aggregation in a wireless communication system. Background Art
[0004] With the rapid growth of the communication demand for large amounts of data to and from mobile communication devices, traditional mobile voice communication networks have evolved into networks that communicate with Internet Protocol (IP) data packets. Such IP data packet communications can provide IP-bearing voice, multimedia, multicast and on-demand communication services to users of mobile communication devices.
[0005] An exemplary network structure is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN). The E-UTRAN system can provide high data throughput to enable the above-mentioned IP-bearing voice and multimedia services. Currently, the 3GPP standards organization is discussing new next-generation (e.g., 5G) radio technologies. Therefore, changes to the current body of 3GPP standards are currently being submitted and considered to evolve and complete the 3GPP standards. Summary of the invention
[0006] According to the present disclosure, one or more devices and / or methods are provided. In an example from the perspective of a user equipment (UE), the UE is configured with one or more cells including a second cell. The UE is configured to monitor one or more first UE-specific physical downlink control channels (PDCCH) on the second cell. One or more first UE-specific PDCCHs schedule data transmission on the first cell. The UE receives downlink control information (DCI) indicating sleep information associated with one or more cells. The DCI indicates the sleep state of the second cell. In response to the DCI indicating the sleep state of the second cell, the UE switches the scheduling cell of the first cell from the second cell to the first cell, and the UE monitors one or more second UE-specific PDCCHs on the first cell. One or more second UE-specific PDCCHs schedule data transmission on the first cell.
[0007] In an example from the perspective of the first network, the first network configures the UE to include one or more cells of the second cell. The first network configures the UE to monitor one or more PDCCHs on the second cell. The one or more PDCCHs schedule data transmission on the first cell. The first network transmits a first DCI indicating sleep information associated with the one or more cells. The first DCI indicates a sleep state of a third cell in the one or more cells. The first network is not allowed to provide an indication of the sleep state corresponding to the second cell via the first DCI. In response to and / or after transmitting the first DCI or receiving a hybrid automatic repeat request confirmation (Hybrid Automatic Repeat Request-Acknowledgement, HARQ-ACK) associated with the first DCI, the first network does not transmit a second DCI on the third cell.
[0008] In an example from the perspective of a UE, the UE is configured with one or more cells including a second cell. The UE is configured to monitor one or more first UE-specific PDCCHs on the second cell. The one or more first UE-specific PDCCHs schedule data transmission on the first cell. The UE receives a DCI indicating sleep information associated with the one or more cells. If the DCI indicates a sleep state of the second cell, then in response to the DCI indicating the sleep state of the second cell, the UE switches the scheduling cell of the first cell from the second cell to the first cell, and the UE monitors one or more second UE-specific PDCCHs on the first cell, wherein the one or more second UE-specific PDCCHs schedule data transmission on the first cell. If the DCI indicates a non-sleep state of the second cell, then in response to the DCI indicating the non-sleep state of the second cell, the UE monitors one or more first UE-specific PDCCHs on the second cell. BRIEF DESCRIPTION OF THE DRAWINGS
[0009] Figure 1 A diagram of a wireless communication system is shown according to an exemplary embodiment.
[0010] Figure 2 is a block diagram of a transmitter system (also referred to as an access network) and a receiver system (also referred to as a user equipment or UE) according to an exemplary embodiment.
[0011] Figure 3 is a functional block diagram of a communication system according to an exemplary embodiment.
[0012] Figure 4 According to an exemplary embodiment Figure 3 Functional block diagram of the program code.
[0013] Figure 5 A table associated with a bitmap indicating sleep information according to an exemplary embodiment is described.
[0014] Figure 6 is a diagram illustrating an exemplary scenario associated with indicating sleep information according to an exemplary embodiment.
[0015] Figure 7 A table associated with a bitmap indicating sleep information according to an exemplary embodiment is described.
[0016] Figure 8 A table associated with a bitmap indicating sleep information according to an exemplary embodiment is described.
[0017] Fig. 9 is a flow chart according to an exemplary embodiment.
[0018] Fig.10is a flow chart according to an exemplary embodiment.
[0019] Fig.11 is a flow chart according to an exemplary embodiment.
[0020] Fig.12 is a flow chart according to an exemplary embodiment.
[0021] Fig.13 is a flow chart according to an exemplary embodiment. DETAILED DESCRIPTION
[0022] The exemplary wireless communication systems and devices described below employ wireless communication systems that support broadcast services. Wireless communication systems are widely deployed to provide various types of communications, such as voice, data, etc. These systems can be based on code division multiple access (CDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), third generation partnership project (3GPP) and other wireless communication systems. rd 3GPP) Long Term Evolution (LTE) radio access, 3GPP Long Term Evolution Advanced (LTE-A or LTE-Advanced), 3GPP2 Ultra Mobile Broadband (UMB), WiMax, 3GPP New Radio (NR) radio access for 5G, or some other modulation technology.
[0023] Specifically, the exemplary wireless communication system apparatus described below can be designed to support one or more standards, such as standards provided by a consortium named “3rd Generation Partnership Project”, referred to herein as 3GPP, including: RP-193260, “New WID on NR Dynamic spectrumsharing (DSS)”, Ericsson; 3GPP TS 38.211 V16.1.0 (2020-03), “3GPP TSG RAN; NR Physical channels and modulation (Release 16)”; 3GPP TS 38.212 V16.1.0 (2020-03), “3GPP TSG RAN; NR Physical channels and modulation (Release 16)”; 3GPP TS 38.213 V16.1.0 (2020-03), “3GPP TSG RAN; NR Physical channels and modulation (Release 16)”; 3GPP TS 38.214 V16.1.0 (2020-03), “3GPP TSG RAN; NR Physical channels and modulation (Release 16)”; 3GPP TS 38.215 V16.1.0 (2020-03), “3GPP TSG RAN; NR physical channels and modulation (Release 16)"; 3GPP TS 38.321 V16.0.0 Draft (2020-03), "3GPP TSG RAN; NR Medium Access Control (MAC) protocol specification (Release 16)"; R1-1909942, Project Summary Report of 3GPP TSG RAN WG1#98v1.0.0 (Prague, Czech Republic, August 26-30, 2019); R1-1913275, Project Summary Report of 3GPP TSG RAN WG1#98bisv2.0.0 (Chongqing, China, October 14-20, 2019); 3GPP TSG RAN Draft report of WG1#99v0.1.0 (Reno, USA, November 18-22, 2019); Draft report of 3GPP TSG RAN WG1#100-ev0.2.0 (online meeting, February 24-March 6, 2020); 3GPP TS 38.331V16.0.0(2020-03), “3GPP TSG RAN; NR Radio Resource Control (RRC) protocol specification (Release 16)”. The standards and documents listed above are hereby expressly incorporated by reference in their entirety.
[0024] Figure 1 A multiple access wireless communication system according to one or more embodiments of the present disclosure is presented. An access network 100 (AN) includes multiple antenna groups, one group includes 104 and 106, another group includes 108 and 110, and an additional group includes 112 and 114. Figure 1 1, only two antennas are shown for each antenna group, however, each antenna group may utilize more or fewer antennas. An access terminal 116 (AT) communicates with antennas 112 and 114, where antennas 112 and 114 transmit information to access terminal 116 via forward link 120 and receive information from access terminal 116 via reverse link 118. AT 122 communicates with antennas 106 and 108, where antennas 106 and 108 transmit information to AT 122 via forward link 126 and receive information from AT 122 via reverse link 124. In a frequency-division duplexing (FDD) system, communication links 118, 120, 124, and 126 may use different frequencies for communication. For example, forward link 120 may use a different frequency than the frequency used by reverse link 118.
[0025] Each antenna group and / or the area in which the antenna group is designed to communicate is often referred to as a sector of the access network. In an embodiment, the antenna groups can each be designed to communicate with access terminals in a sector of the area covered by the access network 100.
[0026] In communications on forward links 120 and 126, the transmit antennas of access network 100 may utilize beamforming in order to improve the signal-to-noise ratio of the forward links for the different access terminals 116 and 122. Additionally, an access network that transmits to access terminals randomly dispersed throughout its coverage area using beamforming may typically cause less interference to access terminals in neighboring cells than an access network that transmits to its access terminals via a single antenna.
[0027] An access network (AN) may be a fixed station or base station for communicating with a terminal, and may also be referred to as an access point, a Node B, a base station, an enhanced base station, an evolved Node B (evolved Node B, eNB), a next generation Node B (gNB), or some other term. An access terminal (AT) may also be referred to as a user equipment (UE), a wireless communication device, a terminal, an access terminal, or some other term.
[0028] Figure 2An embodiment of a transmitter system 210 (also referred to as an access network) and a receiver system 250 (also referred to as an access terminal (AT) or user equipment (UE)) in a multiple-input and multiple-output (MIMO) system 200 is presented. At the transmitter system 210, traffic data for a number of data streams may be provided from a data source 212 to a transmit (TX) data processor 214.
[0029] In one embodiment, each data stream is transmitted through a corresponding transmit antenna. TX data processor 214 formats, codes, and interleaves the traffic data for each data stream based on a particular coding scheme selected for that data stream to provide coded data.
[0030] The decoded data for each data stream may be multiplexed with pilot data using orthogonal frequency-division multiplexing (OFDM) techniques. The pilot data may typically be a known data pattern that is processed in a known manner and may be used at the receiver system to estimate the channel response. The multiplexed pilot and decoded data for the data stream may then be modulated (i.e., symbol mapped) based on a specific modulation scheme selected for each data stream (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-ary phase shift keying (M-PSK), or M-ary quadrature amplitude modulation (M-QAM)) to provide modulation symbols. The data rate, coding, and / or modulation for each data stream may be determined by instructions executed by the processor 230.
[0031] The modulation symbols for all data streams are then provided to a TX MIMO processor 220, which may further process the modulation symbols (e.g., for OFDM). The TX MIMO processor 220 then converts the N T The modulation symbol stream is provided to N T transmitters (TMTR) 222a through 222t. In certain embodiments, TX MIMO processor 220 may apply beamforming weights to the symbols of the data streams and to the antenna from which the symbol is being transmitted.
[0032] Each transmitter 222 receives and processes a respective symbol stream to provide one or more analog signals, and further conditions (e.g., amplifies, filters, and / or upconverts) the analog signals to provide a modulated signal suitable for transmission via a MIMO channel. T The antennas 224a to 224t transmit the N signals from the transmitters 222a to 222t. T a modulated signal.
[0033] At the receiver system 250, the transmitted modulated signal is transmitted via N R The signals are received by antennas 252a through 252r, and the received signal from each antenna 252 may be provided to a respective receiver (RCVR) 254a through 254r. Each receiver 254 may condition (e.g., filter, amplify, and downconvert) a respective received signal, digitize the conditioned signal to provide samples, and / or further process the samples to provide a corresponding “received” symbol stream.
[0034] RX data processor 260 then receives the N R The receiver 254 receives and / or processes N based on a particular receiver processing technique. R received symbol streams to provide N T The RX data processor 260 may then demodulate, deinterleave, and / or decode each detected symbol stream to recover the traffic data for the data stream. The processing by the RX processor 260 may be complementary to the processing performed by the TX MIMO processor 220 and the TX data processor 214 at the transmitter system 210.
[0035] Processor 270 may periodically determine which pre-coding matrix to use (discussed below). Processor 270 formulates a reverse link message comprising a matrix index portion and a rank value portion.
[0036] The reverse link message may include various types of information about the communication link and / or the received data stream. The reverse link message may then be processed by the TX data processor 238 (which also receives traffic data for a plurality of data streams from the data source 236), modulated by the modulator 280, conditioned by the transmitters 254a to 254r, and / or transmitted back to the transmitter system 210.
[0037] At transmitter system 210, the modulated signals from receiver system 250 are received by antenna 224, conditioned by receiver 222, demodulated by demodulator 240, and processed by RX data processor 242 to extract the reverse link message transmitted by receiver system 250. Processor 230 may then determine which precoding matrix to use to determine the beamforming weights and may then process the extracted message.
[0038] Figure 3 An alternative simplified functional block diagram of a communication device according to one embodiment of the disclosed subject matter is presented. Figure 3 As shown in FIG. , the communication device 300 in the wireless communication system can be used to implement Figure 1 UE (or AT) 116 and 122 in or Figure 1 The base station (or AN) 100 in the wireless communication system may be an LTE system or an NR system. The communication device 300 may include an input device 302, an output device 304, a control circuit 306, a central processing unit (CPU) 308, a memory 310, a program code 312, and a transceiver 314. The control circuit 306 executes the program code 312 in the memory 310 through the CPU 308, thereby controlling the operation of the communication device 300. The communication device 300 may receive a signal input by a user through the input device 302 (such as a keyboard or a keypad), and may output images and sounds through the output device 304 (such as a monitor or a speaker). The transceiver 314 is used to receive and transmit wireless signals, pass the received signals to the control circuit 306, and wirelessly output the signals generated by the control circuit 306. The communication device 300 in the wireless communication system may also be used to implement Figure 1 AN 100 in.
[0039] Figure 4 According to one embodiment of the disclosed subject matter Figure 3 4. In this embodiment, program code 312 includes application layer 400, layer 3 portion 402, and layer 2 portion 404, and is coupled to layer 1 portion 406. Layer 3 portion 402 may perform radio resource control. Layer 2 portion 404 may perform link control. Layer 1 portion 406 may perform and / or implement physical connectivity.
[0040] RP-193260 specifies and / or discusses one or more objectives for NR dynamic spectrum sharing (DSS). A portion of RP-193260 is quoted below:
[0041] This work item is limited to FR1 and contains the following objectives for NR Dynamic Spectrum Sharing (DSS):
[0042] ●PDCCH enhancement for cross-carrier scheduling including [RAN1,RAN2]
[0043] ○ PDCCH of SCell that schedules PDSCH or PUSCH on P(S)Cell
[0044] ○ Study, and if it is agreed to use a single DCI to specify the PDCCH of the P(S)Cell / SCell that schedules PDSCH on multiple cells, then
[0045] ■The number of cells that can be scheduled at one time is limited to 2
[0046] ■ Increase in DCI size should be minimized
[0047] • Note: The total PDCCH blind decoding budget should not change due to this work.
[0048] ● Note: These enhancements are not specific to DSS and are generally applicable to cross-carrier scheduling in carrier aggregation
[0049] 3GPP TS 38.211 V16.1.0 specifies and / or discusses the frame structure of the NR system. Part of 3GPP TS 38.211 V16.1.0 is quoted as follows:
[0050] 4 Frame structure and physical resources
[0051] …
[0052] Multiple OFDM basic parameters are supported as given in Table 4.2-1, where μ and the cyclic prefix used for the downlink or uplink bandwidth portion are obtained from the higher layer parameters subcarrierSpacing and cyclicPrefix respectively.
[0053] Table 4.2-1: Supported transport parameter sets.
[0054]
[0055]
[0056] …
[0057] 4.3.2 Time Slot
[0058] For the subcarrier spacing configuration μ, the time slots are numbered in increasing order within the subframe. and are numbered in increasing order within the frame. Existing in the time slot consecutive OFDM symbols, where Depends on the cyclic prefix as given in Tables 4.3.2-1 and 4.3.2-2. Slots in a subframe The beginning of the OFDM symbol in the same subframe is in time align the beginning of the
[0059] …
[0060] Table 4.3.2-1: Number of OFDM symbols per slot, slots per frame, and slots per subframe for normal cyclic prefix.
[0061]
[0062] 3GPP TS 38.212 V16.1.0 specifies and / or discusses DCI formats for power saving. A portion of 3GPP TS 38.212 V16.1.0 is quoted as follows:
[0063] 7.3.1.1.2 Format 0_1
[0064] DCI format 0_1 is used for scheduling one or more PUSCHs in a cell, or to indicate CG downlink feedback information (CG-DFI) to the UE.
[0065] The following information is transmitted via DCI format 0_1, where the CRC is scrambled by C-RNTI or CS-RNTI or SP-CSI-RNTI or MCS-C-RNTI:
[0066] -DCI format identifier - 1 bit
[0067] - The value of this bit field is always set to 0, indicating the UL DCI format
[0068] - Carrier indicator - 0 or 3 bits, as defined in clause 10.1 of [5, TS38.213].
[0069] -DFI flag - 0 or 1 bit
[0070] - 1 bit if the UE is configured to monitor DCI format 0_1 with CRC scrambled by CS-RNTI and for operation in a cell with shared spectrum channel access. For DCI format 0_1 with CRC scrambled by CS-RNTI, a bit value of 0 indicates activation of type 2 CG transmission, and a bit value of 1 indicates CG-DFI. For DCI format 0_1 with CRC scrambled by C-RNTI / SP-CSI-RNTI / MCS-C-RNTI and for operation in a cell with shared spectrum channel access, the bit is reserved.
[0071] - Otherwise, 0;
[0072] If DCI format 0_1 is used to indicate CG-DFI, then all remaining fields are set as follows:
[0073] - HARQ-ACK bitmap - 16 bits, where the order of the bitmap to HARQ process index mapping is such that the HARQ process index is mapped in ascending order from MSB to LSB of the bitmap. For each bit of the bitmap, a value of 1 indicates ACK, and a value of 0 indicates NACK.
[0074] - TPC command for scheduled PUSCH - 2 bits, as defined in clause 7.1.1 of [5, TS 38.213]
[0075] - All remaining bits in format 0_1 are set to zero.
[0076] Otherwise, set all remaining fields as follows:
[0077] -UL / SUL indicator - For UEs not configured with supplementaryUplink in ServingCellConfig in a cell or UEs configured with supplementaryUplink in ServingCellConfig in a cell, but only one carrier in the cell is configured for PUSCH transmission, 0 bit; otherwise, 1 bit, as defined in Table 7.3.1.1.1-1.
[0078] - Bandwidth Part Indicator - Number of UL BWPs n as configured by higher layers BWP,RRC The bit width of this field is determined to be 0, 1, or 2 bits, excluding the initial UL bandwidth part. bits, of which
[0079] -If n BWP,RRC ≤3, then n BWP =n BWP,RRC +1, in which case the bandwidth part indicator is equivalent to the ascending order of the higher layer parameter BWP-Id;
[0080] - Otherwise, n BWP =n BWP,RRC , in which case the bandwidth part indicator is defined in Table 7.3.1.1.2-1.
[0081] If the UE does not support active BWP change via DCI, the UE ignores this bit field.
[0082] …
[0083] -SCell dormancy indication - 0 bit if higher layer parameter Scell-groups-for-dormancy-within-active-time is not configured; otherwise a 1, 2, 3, 4 or 5 bitmap determined according to the higher layer parameter Scell-groups-for-dormancy-within-active-time, where each bit corresponds to one of the SCell groups configured by the higher layer parameter Scell-groups-for-dormancy-within-active-time, with the MSB to LSB of the bitmap corresponding to the first configured SCell group to the last configured SCell group. The field is present only if this format is carried by PDCCH on the primary cell during the DRX active time and the UE is configured with at least two DL BWPs for the SCell.
[0084] 7.3.1.2.2 Format 1_1
[0085] DCI format 1_1 is used for scheduling PDSCH in a cell.
[0086] The following information is transmitted via DCI format 1_1, where the CRC is scrambled by the C-RNTI or CS-RNTI or MCS-C-RNTI:
[0087] -DCI format identifier - 1 bit
[0088] - The value of this bit field is always set to 1, indicating the DL DCI format
[0089] - Carrier indicator - 0 or 3 bits, as defined in clause 10.1 of [5, TS 38.213].
[0090] - Bandwidth Part Indicator - Number n of DL BWPs as configured by higher layers BWP,RRC Determined as 0, 1, or 2 bits, excluding the initial DL bandwidth part. The bit width of this field is determined as bits, of which
[0091] -If n BWP,RRC ≤3, then n BWP =n BWP,RRC +1, in which case the bandwidth part indicator is equivalent to the ascending order of the higher layer parameter BWP-Id;
[0092] - Otherwise, n BWP =n BWP,RRC , in which case the bandwidth part indicator is defined in Table 7.3.1.1.2-1.
[0093] If the UE does not support active BWP change via DCI, the UE ignores this bit field.
[0094] - Frequency domain resource allocation - the number of bits determined by, where is the size of the active DL bandwidth portion:
[0095] - If only resource allocation type 0 is configured, then N RBG bits, where N RBG As defined in clause 5.1.2.2.1 of [6, TS38.214],
[0096] - If only resource allocation type 1 is configured, then bit, or
[0097] - If you configure both resource allocation types 0 and 1, then Bit.
[0098] - If both resource allocation types 0 and 1 are configured, then the MSB bit is used to indicate resource allocation type 0 or resource allocation type 1, where a bit value of 0 indicates resource allocation type 0 and a bit value of 1 indicates resource allocation type 1.
[0099] -For resource allocation type 0, N RBG The LSB provides resource allocation as defined in clause 5.1.2.2.1 of [6, TS 38.214].
[0100] -For resource allocation type 1, LSB provides resource allocation as defined in clause 5.1.2.2.2 of [6, TS38.214].
[0101] If the "Bandwidth Part Indicator" field indicates a bandwidth part other than the active bandwidth part, and if both resource allocation types 0 and 1 are configured for the indicated bandwidth part, then if the bit width of the "Frequency Domain Resource Allocation" field for the active bandwidth part is less than the bit width of the "Frequency Domain Resource Allocation" field for the indicated bandwidth part, the UE assumes resource allocation type 0 for the indicated bandwidth part.
[0102] - Time Domain Resource Assignment - 0, 1, 2, 3 or 4 bits, as defined in clause 5.1.2.1 of [6, TS 38.214]. The bit width used for this field is determined as bits, where I is the number of entries in the higher layer parameter pdsch-TimeDomainAllocationList if a higher layer parameter is configured; otherwise I is the number of entries in the default table.
[0103] - VRB to PRB mapping - 0 or 1 bit:
[0104] - 0 bit if only resource allocation type 0 is configured or if interleaved VRB to PRB mapping is not configured by higher layers;
[0105] - Otherwise, according to Table 7.3.1.2.2-5, 1 bit, applicable only to resource allocation type 1, as defined in clause 7.3.1.6 of [4, TS 38.211].
[0106] -PRB Bundling Size Indicator - According to clause 5.1.2.3 of [6, TS 38.214]], 0 bit if the higher layer parameter prb-BundlingType is not configured or set to 'staticBundling'; 1 bit if the higher layer parameter prb-BundlingType is set to 'dynamicBundling'.
[0107] - Rate Match Indicator - 0, 1 or 2 bits according to higher layer parameters rateMatchPatternGroup1 and rateMatchPatternGroup2, where when there are two groups, the MSB is used to indicate rateMatchPatternGroup1 and the LSB is used to indicate rateMatchPatternGroup2.
[0108] - ZP CSI-RS Trigger - 0, 1, or 2 bits, as defined in clause 5.1.4.2 of [6, TS 38.214]. The bit width used for this field is determined as bits, where n ZP is the number of aperiodic ZP CSI-RS resource sets configured by higher layers.
[0109] For transport block 1:
[0110] - Modulation Coding Scheme - 5 bits, as defined in clause 5.1.3.1 of [6, TS 38.214].
[0111] - New data indicator - 1 bit
[0112] - Redundancy version - 2 bits, as defined in Table 7.3.1.1.1-2
[0113] For transport block 2 (only present when maxNrofCodeWordsScheduledByDCI is equal to 2):
[0114] - Modulation Coding Scheme - 5 bits, as defined in clause 5.1.3.1 of [6, TS 38.214].
[0115] - New data indicator - 1 bit
[0116] - Redundancy version - 2 bits, as defined in Table 7.3.1.1.1-2
[0117] …
[0118] -HARQ process number - 4 bits
[0119] - Downlink Assignment Index
[0120] …
[0121] -SCell dormancy indication - 0 bit if higher layer parameter Scell-groups-for-dormancy-within-active-time is not configured; otherwise a 1, 2, 3, 4 or 5 bitmap determined according to the higher layer parameter Scell-groups-for-dormancy-within-active-time, where each bit corresponds to one of the SCell groups configured by the higher layer parameter Scell-groups-for-dormancy-within-active-time, with the MSB to LSB of the bitmap corresponding to the first configured SCell group to the last configured SCell group. The field is present only if this format is carried by PDCCH on the primary cell during the DRX active time and the UE is configured with at least two DL BWPs for the SCell.
[0122] If all bits of frequency domain resource allocation are set to 0 for resource allocation type 0 and to 1 for resource allocation type 1, then this field is retained and the following fields among the above fields are used for SCell sleep indication, where each bit corresponds to one of the configured SCells, where the MSB to LSB of the following fields cascaded in the order below correspond to the SCell with the lowest to highest SCell index.
[0123] - Modulation and coding scheme for transport block 1
[0124] - New data indicator for transport block 1
[0125] - Redundant version of transport block 1
[0126] -HARQ process number
[0127] - Antenna ports
[0128] [-DMRS sequence initialization]
[0129] If DCI format 1_1 is monitored in multiple search spaces associated with multiple CORESETs in a BWP for scheduling the same serving cell, zeros should be appended until the payload size of DCI format 1_1 monitored in the multiple search spaces is equal to the maximum payload size of DCI format 1_1 monitored in the multiple search spaces.
[0130] 7.3.1.3.7 Format 2_6
[0131] DCI format 2_6 is used to notify power saving information outside the DRX active time of one or more UEs.
[0132] The following information is transmitted via DCI format 2_6, where the CRC is scrambled by the PS-RNTI:
[0133] - Block number 1, block number 2...block number N
[0134] The starting position of the block is determined by the parameter PSPositionDCI2-6 provided by a higher layer for the UE configured with the block.
[0135] If the UE is configured with higher layer parameters PS-RNTI and DCI-Format 2-6, then one block is configured by higher layers for the UE, on which the following fields are defined for the block:
[0136] -Wake-up indication - 1 bit
[0137] -SCell dormancy indication - 0 bit if the higher layer parameter Scell-groups-for-dormancy-outside-active-time is not configured; otherwise a 1, 2, 3, 4 or 5-bit bitmap determined according to the higher layer parameter Scell-groups-for-dormancy-outside-active-time, where each bit corresponds to one of the SCell groups configured by the higher layer parameter Scell-groups-for-dormancy-outside-active-time, where the MSB to LSB of the bitmap corresponds to the first configured SCell group to the last configured SCell group.
[0138] According to clause 10.3 of [5, TS 38.213], the size of DCI format 2_6 is indicated by a higher layer parameter SizeDCI_2-6.
[0139] 3GPP TS 38.213 V16.1.0 specifies and / or discusses bandwidth part (BWP) and physical downlink control channel (PDCCH) related to power saving. A portion of 3GPP TS 38.213 V16.1.0 is quoted as follows:
[0140] 10.3 PDCCH monitoring of SCell indication and sleep / non-sleep behavior
[0141] A UE configured with DRX mode operates on a PCell [11, TS 38.321] or SpCell [12, TS 38.331]
[0142] - PS-RNTI for DCI format 2_6, provided by ps-RNTI
[0143] - Number of search space sets, provided by dci-Format2-6, used to monitor PDCCH according to the common search space as described in clause 10.1 for detecting DCI format 2_6 on the active DL BWP of PCell or SpCell
[0144] - Payload size of DCI format 2_6, provided by SizeDCI_2-6
[0145] -The position of the wake-up indication bit in DCI format 2_6, provided by PSPositionDCI2-6, where
[0146] - When the value of the wake-up indication bit is '0', the UE may not start the drx-onDurationTimer of the next long DRX cycle, and
[0147] -When the wake-up indication bit value is '1', the UE starts the drx-onDurationTimer of the next long DRX cycle
[0148] - Bitmap, when the number of groups configured with SCell is provided to the UE via Scell-groups-for-dormancy-outside-active-time,
[0149] - The bitmap position is immediately after the wake-up indication bit position
[0150] - The bitmap size is equal to the number of groups of configured SCells, where each bit of the bitmap corresponds to a group of configured SCells from the plurality of groups of configured SCells
[0151] - A value of '0' for a bit of the bitmap indicates an active DL BWP, provided by dormant-BWP for each UE with activated SCell in the corresponding group of configured SCells [11, TS 38.321]
[0152] - A '1' value for a bit in the bitmap indicates
[0153] - Active DL BWP, when the current active DL BWP is the sleeping DL BWP, for each UE in the corresponding group configured with SCell and activated SCell, provided by first-non-dormant-BWP-ID-for-DCI-outside-active-time
[0154] - Current active DL BWP, if the current active DL BWP is not a sleep DL BWP, for each activated SCell UE in the corresponding group of configured SCells
[0155] - ps-Offset indicating the time where the UE starts monitoring the PDCCH for detecting DCI format 2_6 according to multiple search space sets before the time slot at which drx-onDuarationTimer will start on the PCell or on the SpCell [11, TS 38.321]
[0156] - For each search space set, the PDCCH monitoring occasion is the first T indicated by the duration s The time slot of the time slots, or if no duration is provided, then T s = 1 time slot from the previous T s The first of the time slots starts and ends before the drx-onDurationTimer starts.
[0157] The UE does not monitor the PDCCH for detecting DCI format 2_6 during active time [11, TS38.321].
[0158] If the UE reports a requirement of X slots for an active DL BWP before the start of the slot in which the UE will start the drx-onDurationTimer, then the UE does not need to monitor the PDCCH for detecting DCI format 2_6 during X slots, where X corresponds to the requirement of the SCS of the active DL BWP.
[0159] If a UE is provided with a search space set to monitor PDCCH for detecting DCI format 2_6 in the active DL BWP of a PCell or SpCell and the UE does not detect DCI format 2_6
[0160] - If ps-WakeupOrNot is provided to the UE, the UE is informed by ps-WakeupOrNot whether the UE may not start or whether the UE should start the drx-onDurationTimer of the next DRX cycle
[0161] - If the UE does not provide ps-WakeupOrNot, the UE may not start the activity time indicated by drx-onDurationTimer of the next DRX cycle
[0162] If a UE is provided with a search space set to monitor the PDCCH for detecting DCI format 2_6 in the active DL BWP of a PCell or SpCell, and the UE
[0163] - For all corresponding PDCCH monitoring occasions other than the active time before the next DRX cycle, it is not necessary to monitor the PDCCH for detecting DCI format 2_6, as described in clauses 10, 11.1, 12 and clause 5.7 of [14, TS 38.321]
[0164] - There is no PDCCH monitoring opportunity for detecting DCI format 2_6 outside the active time of the next DRX cycle
[0165] The UE shall then start the drx-onDurationTimer for the next DRX cycle.
[0166] If a search space set is provided to a UE to monitor the PDCCH for detecting DCI format 0_1 and DCI format 1_1, and if one or both of DCI format 0_1 and DCI format 1_1 contain an SCell dormancy indication field, then
[0167] -SCell Dormancy Indication field is a bitmap with a size equal to the number of configured SCell groups, provided by Scell-groups-for-dormancy-within-active-time
[0168] - Each bit in the bitmap corresponds to a group of configured SCells from a plurality of groups of configured Scells
[0169] - If the UE detects a DCI format 0_1 or DCI format 1_1 that does not contain a carrier indicator field, or detects a DCI format 0_1 or DCI format 1_1 that contains a carrier indicator field having a value equal to 0, then
[0170] - A value of '0' for a bit of the bitmap indicates an active DL BWP, provided by the dormant-BWP for each UE in the corresponding group of configured SCells that has an activated SCell
[0171] - A '1' value for a bit in the bitmap indicates
[0172] - Active DLBWP, when the current active DL BWP is the sleeping DL BWP, for each UE in the corresponding group configured with SCell and activated SCell, provided by first-non-dormant-BWP-ID-for-DCI-inside-active-time
[0173] - Current active DL BWP, if the current active DL BWP is not a sleep DL BWP, for each activated SCell UE in the corresponding group of configured SCells
[0174] -UE sets the active DL BWP to the indicated active DL BWP
[0175] If a search space set is provided to the UE to monitor the PDCCH for detecting DCI format 1_1, and if
[0176] - The CRC of DCI format 1_1 is scrambled by C-RNTI or MCS-C-RNTI, and if
[0177] -resourceAllocation=resourceAllocationType0 and all bits of the frequency domain resource allocation field in DCI format 1_1 are equal to 0, or
[0178] -resourceAllocation=resourceAllocationType1 and all bits of the frequency domain resource allocation field in DCI format 1_1 are equal to 1
[0179] -resourceAllocation=dynamicSwitch and all bits of the frequency domain resource allocation field in DCI format 1_1 are equal to 0 or 1
[0180] The UE regards DCI format 1_1 as indicating SCell dormancy, not scheduling PDSCH reception or indicating SPS PDSCH release, and interprets the following sequence of fields for transport block 1:
[0181] - Modulation and coding scheme
[0182] - New data indicator
[0183] - Redundant version
[0184] and the following sequence of fields:
[0185] -HARQ process number
[0186] - Antenna ports
[0187] -DMRS sequence initialization
[0188] When the bitmap is provided to each configured SCell in ascending order of SCell index,
[0189] - A '0' in a bitmap indicates an active DL BWP, provided by dormant-BWP for the UE corresponding to the activated SCell
[0190] - A '1' value for a bit in the bitmap indicates
[0191] -Active DL BWP, when the current active DL BWP is a dormant DL BWP, for the UE corresponding to the activated SCell, provided by first-non-dormant-BWP-ID-for-DCI-inside-active-time
[0192] -Currently active DL BWP, if the currently active DL BWP is not the sleep DL BWP, for the UE corresponding to the activated SCell
[0193] -UE sets the active DL BWP to the indicated active DL BWP
[0194] If the active DL BWP provided by the dormant-BWP for the UE on the activated SCell is not the default DL BWP for the UE on the activated SCell, as described in clause 12, then the BWP inactivity timer is not used to transition from the active DL BWP provided by the dormant-BWP to the default DL BWP on the activated SCell.
[0195] In response to the detection of DCI format 1_1 indicating SCell dormancy N symbols after the last symbol from the PDCCH providing DCI format 1_1, the UE is expected to provide HARQ ACK information. If processingType2Enabled of PDSCH-ServingCellConfig is set to enabled for the serving cell with a PDCCH providing DCI format 1_1, then for μ=0, N=5, for μ=1, N=5.5 and for μ=2, N=11; otherwise, for μ=0, N=10, for μ=1, N=12, for μ=2, N=22 and for μ=3, N=25, where in response to the detection of DCI format 1_1, μ is the minimum SCS configuration between the SCS configuration of the PDCCH providing DCI format 1_1 and the SCS configuration of the PUCCH with HARQ-ACK information.
[0196] 12 Bandwidth Partial Operation
[0197] …
[0198] A UE configured for operation in a bandwidth part (BWP) of a serving cell is configured by higher layers of the serving cell, a set of up to four bandwidth parts (BWPs) for reception by the UE (DL BWP setting) in the DL bandwidth via parameters BWP-Downlink or via parameters initialDownlinkBWP with a parameter set configured by BWP-DownlinkCommon and BWP-DownlinkDedicated, and a set of up to four BWPs for transmission by the UE (UL BWP setting) in the UL bandwidth via parameters BWP-Uplink or via parameters initialUplinkBWP with a parameter set configured by BWP-UplinkCommon and BWP-UplinkDedicated.
[0199] If the UE does not provide initialDownlinkBWP, the initial DL BWP is defined by the position and number of consecutive PRBs, starting from the PRB with the lowest index and ending at the PRB with the highest index among the PRBs in the CORESET for the Type0-PDCCHCSS set, and the SCS and cyclic prefix for PDCCH reception in the CORESET for the Type0-PDCCHCSS set; otherwise, the initial DL BWP is provided by initialDownlinkBWP. For operation on a primary cell or a secondary cell, the initial UL BWP is provided to the UE by initialUplinkBWP. If the UE is configured with a supplementary UL carrier, the initial UL BWP may be provided to the UE by initialUplinkBWP on the supplementary UL carrier.
[0200] If the UE has a dedicated BWP configuration, then the first active DL BWP for reception may be provided to the UE via firstActiveUplinkBWP-Id, and the first active UL BWP for transmission on the carrier of the primary cell may be provided to the UE via firstActiveUplinkBWP-Id.
[0201] For each DL BWP or UL BWP in the set of DL BWPs or UL BWPs, respectively, the following parameters of the serving cell are provided to the UE, as defined in [4, TS 38.211] or [6, TS 38.214]:
[0202] -SCS, provided by subcarrierSpacing
[0203] -Cyclic prefix, provided by cyclicPrefix
[0204] -Common RB And several consecutive RB Provided by locationAndBandwidth, offset RB according to [6, TS 38.214] start and length L RB Indicates RIV, set And the value is O carrier Provided by offsetToCarrier for subcarrierSpacing
[0205] - Index in the set of DL BWP or UL BWP, provided by the corresponding BWP-Id
[0206] - A set of BWP common parameters and a set of BWP dedicated parameters, provided by BWP-DownlinkCommon and BWP-DownlinkDedicated for DL BWP, or by BWP-UplinkCommon and BWP-UplinkDedicated for UL BWP [12, TS 38.331]
[0207] For unpaired spectrum operation, when the DL BWP index is the same as the UL BWP index, a DL BWP from the set of configured DL BWPs with the index provided by the BWP-Id is associated with a UL BWP from the set of configured ULBWPs with the index provided by the BWP-Id. For unpaired spectrum operation, when the BWP-Id of the DL BWP is equal to the BWP-Id of the UL BWP, the UE may not expect to receive a configuration in which the center frequency of the DL BWP is different from the center frequency of the UL BWP.
[0208] For each DL BWP in the set of DL BWPs for PCell or PUCCH-SCell, the UE may be configured as a CORESET for each type of CSS set and USS as described in clause 10.1. In the case of a CSS set on the PCell or PUCCH-SCell of the MCG without an active DL BWP, no configuration is expected for the UE.
[0209] If controlResourceSetZero and searchSpaceZero are provided to the UE in PDCCH-ConfigSIB1 or PDCCH-ConfigCommon, the UE determines the CORESET of the search space set from controlResourcesetZero as described in clause 13 and for Tables 13-1 to 13-10, and determines the corresponding PDCCH monitoring occasions as described in clause 13 and for Tables 13-11 to 13-15. If the active DL BWP is not the initial DL BWP, the UE determines the PDCCH monitoring occasions of the search space set only if the CORESET bandwidth is within the active DL BWP and the active DL BWP has the same SCS configuration and the same cyclic prefix as the initial DL BWP.
[0210] For each UL BWP in the set of UL BWPs of a PCell or PUCCH-SCell, the UE is configured as a resource set for PUCCH transmission as described in clause 9.2.1.
[0211] The UE receives PDCCH and PDSCH in the DL BWP according to the SCS and CP length configured for the DL BWP. The UE transmits PUCCH and PUSCH in the UL BWP according to the SCS and CP length configured for the UL BWP.
[0212] If the Bandwidth Part Indicator field is configured in DCI format 1_1, then the Bandwidth Part Indicator field value indicates the active DL BWP for DL reception from the configured DL BWP set, as described in [5, TS 38.212]. If the Bandwidth Part Indicator field is configured in DCI format 0_1, then the Bandwidth Part Indicator field value indicates the active UL BWP for UL transmission from the configured UL BWP set, as described in [5, TS 38.212].
[0213] - Set the active UL BWP or DL BWP to the UL BWP or DL BWP indicated by the bandwidth part indicator in DCI format 0_1 or DCI format 1_1, respectively
[0214] …
[0215] The UE expects to detect DCI format 0_1 indicating an active UL BWP change, or DCI format 1_1 indicating an active DL BWP change, only when the corresponding PDCCH is received within the first 3 symbols of a slot.
[0216] For the serving cell, a default DL BWP among configured DL BWPs may be provided to the UE through defaultDownlinkBWP-Id. If a default DL BWP is not provided to the UE through defaultDownlinkBWP-Id, the default DL BWP is the initial DL BWP.
[0217] If the timer value of the serving cell [11, TS 38.321] is provided to the UE via bwp-InactivityTimer and the timer is running, then if the restart conditions in [11, TS 38.321] are not met during the interval of a subframe of FR1 or a half subframe of FR2, the UE decrements the timer at the end of a subframe of FR1 or at the end of a half subframe of FR2.
[0218] …
[0219] If the UE is provided with a first active DLBWP via firstActiveDownlinkBWP-Id and a first active UL BWP via firstActiveUplinkBWP-Id on the carrier of the secondary cell, the UE uses the indicated DLBWP and the indicated UL BWP as the respective first active DL BWP on the secondary cell and the first active UL BWP on the carrier of the secondary cell.
[0220] When the UE performs RRM measurements on a bandwidth that is not within the UE's active DL BWP [10, TS 38.133], the UE does not expect to monitor the PDCCH.
[0221] The draft 3GPP TS 38.321 v16.0.0 specifies and / or discusses the Medium Access Control (MAC) protocol specification in NR. A portion of the draft 3GPP TS 38.321 v16.0.0 is quoted as follows:
[0222] Sleep BWP: The sleep BWP is one of the downlink BWPs configured by the network via dedicated RRC signaling. In the sleep BWP, the UE stops monitoring PDCCH on / for the SCell, but continues to perform CSI measurements, Automatic Gain Control (AGC) and beam management if configured.
[0223] 5.9SCell Activation / Deactivation
[0224] If the MAC entity is configured with one or more SCells, the network can activate and deactivate the configured SCells. After the configuration of the SCell, the SCell is immediately deactivated unless the parameter sCellState is set to be activated for the SCell in the RRCReconfiguration message.
[0225] To activate and deactivate the configured SCell, perform the following operations:
[0226] - receive the SCell activation / deactivation MAC CE described in clause 6.1.3.10;
[0227] -Configure an sCellDeactivationTimer timer for each configured SCell (except the SCell configured with PUCCH (if any)): deactivate the associated SCell when the timer expires.
[0228] The MAC entity shall, for each configured SCell:
[0229] 1> If the SCell is configured with sCellState set to be activated immediately after SCell configuration, or an SCell activation / deactivation MAC CE is received to activate the SCell:
[0230] 2> If firstActiveDownlinkBWP-Id is not set to the sleeping BWP:
[0231] 3> Activate the SCell according to the timing defined in TS 38.213 [6]; that is, apply normal SCell operation, including:
[0232] 4>SRS transmission on SCell;
[0233] 4> CSI report for SCell;
[0234] 4>PDCCH monitoring on SCell;
[0235] 4>PDCCH monitoring for SCell;
[0236] 4>PUCCH transmission on SCell (if configured).
[0237] 3> If the SCell is deactivated before receiving this SCell activation / deactivation MAC CE:
[0238] 4> Activate the DL BWP and UL BWP indicated by firstActiveDownlinkBWP-Id and firstActiveUplinkBWP-Id respectively;
[0239] 3> Start or restart the sCellDeactivationTimer associated with the SCell according to the timing defined in TS 38.213[6];
[0240] 3> (Re)initialize any suspended configured uplink grants of configured grant type 1 associated with this SCell according to the stored configuration (if any), and starting in a symbol according to the rules in clause 5.8.2;
[0241] 3>Trigger PHR according to clause 5.4.6.
[0242] 2> Else if firstActiveDownlinkBWP-Id is set to sleepingBWP:
[0243] 3> If it is running, stop the bwp-InactivityTimer of this serving cell.
[0244] 3>Do not monitor PDCCH on BWP;
[0245] 3> PDCCH is not monitored for BWP;
[0246] 3> Do not receive DL-SCH on BWP;
[0247] 3> If configured, perform CSI measurement of BWP;
[0248] 3> Stop all UL behaviors, that is, stop any UL transmission, suspend any configured uplink grant type 1 associated with the SCell, and clear any configured uplink grant of the configured grant type 2 associated with the SCell;
[0249] 3> If configured, perform beam failure detection and beam failure recovery of SCell in case of beam failure detected;
[0250] 3> If the SCell is deactivated before receiving this SCell activation / deactivation MAC CE:
[0251] 4> Activate the DL BWP and UL BWP indicated by firstActiveDownlinkBWP-Id and firstActiveUplinkBWP-Id respectively;
[0252] 3> Otherwise if the SCell is configured with sCellState set to be activated immediately after SCell configuration:
[0253] 4> Activate the DL BWP and UL BWP indicated by firstActiveDownlinkBWP-Id and firstActiveUplinkBWP-Id respectively;
[0254] 3> Start or restart the sCellDeactivationTimer associated with the SCell according to the timing defined in TS 38.213 [6].
[0255] 1> Otherwise if a SCell activation / deactivation MAC CE is received to deactivate the SCell; or
[0256] 1> If the sCellDeactivationTimer associated with the activated SCell expires, then:
[0257] 2> Deactivate SCell according to the timer defined in TS 38.213[6];
[0258] 2> Stop the sCellDeactivationTimer associated with SCell;
[0259] 2>Stop the bwp-InactivityTimer associated with SCell;
[0260] 2> Deactivate any active BWP associated with the SCell;
[0261] 2> Clear any configured downlink assignments and any configured uplink grant type 2 associated with the SCell respectively;
[0262] 2> Clear any PUSCH resources used for semi-persistent CSI reporting associated with the SCell;
[0263] 2>Suspend any configured uplink grant type 1 associated with the SCell;
[0264] 2> Cancel all triggered BFRs for this serving cell (see clause 5.17);
[0265] 2>Flush all HARQ buffers associated with SCell;
[0266] 2> Cancel the triggered consistent LBT fault of SCell if any.
[0267] 1> If the PDCCH on the activated SCell indicates an uplink grant or a downlink assignment; or
[0268] 1> if the PDCCH on the serving cell scheduling the activated SCell indicates an uplink grant or downlink assignment for the activated SCell; or
[0269] 1> If a MAC PDU is transmitted in a configured uplink grant or received in a configured downlink assignment, then:
[0270] 2>Restart the sCellDeactivationTimer associated with the SCell.
[0271] 1> If SCell is disabled, then:
[0272] 2> Do not transmit SRS on SCell;
[0273] 2> Do not report CSI for SCell;
[0274] 2> Not transmitted on the UL-SCH on the SCell;
[0275] 2> Not transmitted on RACH on SCell;
[0276] 2>Do not monitor PDCCH on SCell;
[0277] 2> PDCCH is not monitored for SCell;
[0278] 2> PUCCH is not transmitted on SCell.
[0279] In TS 38.133
[11] , the HARQ feedback of the MAC PDU containing the SCell activation / deactivation MAC CE shall not be affected by the PCell, PSCell and PUCCH SCell outage caused by SCell activation / deactivation.
[0280] When an SCell is deactivated, the ongoing random access procedure (if any) on the SCell is aborted.
[0281] 5.15.1 Downlink and Uplink
[0282] In addition to clause 12 of TS 38.213 [6], this clause also specifies requirements for BWP operations.
[0283] A serving cell can be configured with one or more BWPs, and the maximum number of BWPs per serving cell is specified in TS 38.213 [6].
[0284] In an example, BWP switching for a serving cell is used to simultaneously activate an inactive BWP and deactivate an active BWP. BWP switching may be controlled by a PDCCH indicating a downlink assignment or uplink grant, by a bwp-InactivityTimer, by RRC signaling or by the MAC entity itself after the start of a random access procedure or after detection of a consistent LBT failure on the SpCell. After RRC (re)configuration of firstActiveDownlinkBWP-Id and / or firstActiveUplinkBWP-Id for the SpCell or activation of the SCell, the DL BWP and / or UL BWP indicated by firstActiveDownlinkBWP-Id and / or firstActiveUplinkBWP-Id, respectively (as specified in TS 38.331 [5]) are active without receiving a PDCCH indicating a downlink assignment or uplink grant. The active BWP of a serving cell is indicated by RRC or PDCCH (as specified in TS 38.213 [6]). For unpaired spectrum, the DL BWP is paired with the UL BWP, and BWP switching is common for both UL and DL.
[0285] Entering or leaving the sleep BWP is done by BWP switching. It is controlled by PDCCH per SCell or per sleep SCell group (as specified in TS 38.212 [9]). The sleep SCell group configuration indicated by dormancySCellGroups and the sleep BWP configuration for one SCell indicated by dormantDownlinkBWP-Id are configured by RRC signaling as described in TS38.331 [5]. After receiving a PDCCH indicating leaving the sleep BWP from the SpCell outside the active time, the DL BWP indicated by firstOutsideActiveTimeBWP-Id (as specified in TS 38.331 [5]) is activated. After receiving a PDCCH indicating leaving the sleep BWP from the SpCell within the active time, the DL BWP indicated by firstWithinActiveTimeBWP-Id (as specified in TS38.331 [5]) is activated. Upon receiving a PDCCH indicating entry into a sleep BWP, the DL BWP indicated by dormantDownlinkBWP-Id (as specified in TS 38.331 [5]) is activated. Sleep BWP configuration for SpCell or PUCCH SCell is not supported.
[0286] For each activated serving cell configured with a BWP, the MAC entity shall:
[0287] 1> If the BWP is activated and it is not a sleeping BWP, then:
[0288] 2>Transmitted on UL-SCH on BWP;
[0289] 2> If PRACH opportunity is configured, then transmit on RACH on BWP;
[0290] 2> Monitor PDCCH on BWP;
[0291] 2> If configured, PUCCH is transmitted on BWP;
[0292] 2> Report CSI for BWP;
[0293] 2> If configured, transmit SRS on BWP;
[0294] 2> Receive DL-SCH on BWP;
[0295] 2> (re)initialize any suspended configured uplink grants of configured grant type 1 on the active BWP according to the stored configuration (if any), and starting from symbol 1 according to the rules in clause 5.8.2;
[0296] 2> If consistent LBT failover is configured, then:
[0297] 3>Stop lbt-FailureDetectionTimer if it is running;
[0298] 3> Set LBT_COUNTER to 0;
[0299] 3> Monitor LBT fault indications from lower layers as specified in clause 5.21.2.
[0300] 1> If the BWP is activated and it is the sleeping BWP of the SCell, then:
[0301] 2> If it is running, stop the bwp-InactivityTimer of this service cell.
[0302] 2>Do not monitor PDCCH on BWP;
[0303] 2> PDCCH is not monitored for BWP;
[0304] 2> Do not receive DL-SCH on BWP;
[0305] 2> If configured, perform CSI measurement of BWP;
[0306] 2> Stop all UL behaviors, that is, stop any UL transmission, suspend any configured uplink grant type 1 associated with the SCell, and clear any configured uplink grant of configured grant type 2 associated with the SCell;
[0307] 2> If configured, beam failure detection and beam failure recovery of SCell are performed when beam failure is detected.
[0308] 1> If BWP is disabled, then:
[0309] 2> Not transmitted on UL-SCH on BWP;
[0310] 2> Not transmitted on RACH on BWP;
[0311] 2>Do not monitor PDCCH on BWP;
[0312] 2> PUCCH is not transmitted on BWP;
[0313] 2> CSI is not reported for BWP;
[0314] 2> Do not transmit SRS on BWP;
[0315] 2> Do not receive DL-SCH on BWP;
[0316] 2> Clear any configured downlink assignments and configured uplink grants of configured grant type 2 on the BWP;
[0317] 2> Suspend any configured uplink grants of configured grant type 1 on inactive BWPs.
[0318] Upon initiation of a random access procedure on a serving cell, after selecting a carrier for performing the random access procedure as specified in clause 5.1.1, the MAC entity shall, for the selected carrier of this serving cell:
[0319] 1> If the PRACH opportunity is not configured for active UL BWP, then:
[0320] 2> Switch the active UL BWP to the BWP not indicated by initialUplinkBWP;
[0321] 2> If the serving cell is SpCell, then:
[0322] 3> Switch the active DL BWP to the BWP indicated by initialDownlinkBWP.
[0323] 1> Otherwise:
[0324] 2> If the serving cell is SpCell, then:
[0325] 3> If the active DL BWP does not have the same bwp-Id as the active UL BWP, then:
[0326] 4> Switch the active DL BWP to a DL BWP with the same bwp-Id as the active UL BWP.
[0327] 1> Stop the bwp-InactivityTimer associated with the active DL BWP of this serving cell if running.
[0328] 1> If the serving cell is SCell, then:
[0329] 2> Stop the bwp-InactivityTimer associated with the active DL BWP of the SpCell if it is running.
[0330] 1> Perform a random access procedure on the active DL BWP of the SpCell and the active UL BWP of this serving cell.
[0331] If the MAC entity receives a PDCCH for BWP switching of a serving cell, the MAC entity shall:
[0332] 1> if there is no ongoing random access procedure associated with this serving cell; or
[0333] 1> If an ongoing random access procedure associated with this serving cell (as specified in clauses 5.1.4, 5.1.4a and 5.1.5) is successfully completed after reception of this PDCCH addressed to the C-RNTI, then:
[0334] 2> If it exists, cancel the triggered consistent LBT fault of this serving cell;
[0335] 2> Perform BWP switching to the BWP indicated by PDCCH.
[0336] If the MAC entity receives a PDCCH for BWP switching of a serving cell or a dormant SCell group while a random access procedure associated with a serving cell is ongoing in the MAC entity, it is up to the UE to implement whether to switch the BWP or ignore the PDCCH for BWP switching, except for PDCCH reception for BWP switching addressed to the C-RNTI to successfully complete the random access procedure (as specified in clauses 5.1.4, 5.1.4a and 5.1.5), in which case the UE will perform a BWP switch to the BWP indicated by the PDCCH. After receiving a PDCCH for BWP switching other than a successful contention resolution, if the MAC entity decides to perform a BWP switch, the MAC entity shall stop the ongoing random access procedure and start the random access procedure after performing the BWP switch; if the MAC decides to ignore the PDCCH for BWP switching, the MAC entity shall continue the ongoing random access procedure on the serving cell.
[0337] Upon receiving RRC (re)configuration for BWP switching of a serving cell while a random access procedure associated with the serving cell is ongoing in the MAC entity, the MAC entity shall stop the ongoing random access procedure and start the random access procedure after performing BWP switching.
[0338] After receiving the RRC (re)configuration for BWP handover of a serving cell, any triggered LBT failure in this serving cell is cancelled.
[0339] For each activated serving cell configured with bwp-InactivityTimer, the MAC entity shall:
[0340] 1> if defaultDownlinkBWP-Id is configured, and the active DL BWP is not the BWP indicated by defaultDownlinkBWP-Id, and the active DL BWP is not the BWP indicated by dormantDownlinkBWP-Id (if configured); or
[0341] 1> If defaultDownlinkBWP-Id is not configured, and the active DL BWP is not the BWP indicated by initialDownlinkBWP, and the active DL BWP is not the BWP indicated by dormantDownlinkBWP-Id (if configured), then:
[0342] 2> if a PDCCH addressed to a C-RNTI or CS-RNTI indicating a downlink assignment or uplink grant is received on an active BWP; or
[0343] 2> If a PDCCH addressed to a C-RNTI or CS-RNTI indicating a downlink assignment or uplink grant is received for an active BWP; or
[0344] 2> If a MAC PDU is transmitted in a configured uplink grant or received in a configured downlink assignment, then:
[0345] 3> if there is no ongoing random access procedure associated with this serving cell; or
[0346] 3> If an ongoing random access procedure associated with this serving cell (as specified in clauses 5.1.4, 5.1.4a and 5.1.5) is successfully completed after receiving this PDCCH addressed to the C-RNTI, then:
[0347] 4> Start or restart the bwp-InactivityTimer associated with the active DL BWP.
[0348] 2> If the bwp-InactivityTimer associated with the active DL BWP expires, then:
[0349] 3>If defaultDownlinkBWP-Id is configured, then:
[0350] 4> Perform BWP switching to the BWP indicated by defaultDownlinkBWP-Id.
[0351] 3> Otherwise:
[0352] 4>Execute BWP to switch to initialDownlinkBWP.
[0353] Note: If the random access procedure is initiated on an SCell, both the SCell and the SpCell are associated with the random access procedure.
[0354] 1> If PDCCH for BWP switching is received and the MAC entity switches the active DL BWP, then:
[0355] 2> if defaultDownlinkBWP-Id is configured and the MAC entity switches to a DL BWP that is not indicated by defaultDownlinkBWP-Id and not indicated by dormantDownlinkBWP-Id (if configured); or
[0356] 2> If defaultDownlinkBWP-Id is configured and the MAC entity switches to a DL BWP that is not indicated by initialDownlinkBWP and not indicated by dormantDownlinkBWP-Id (if configured), then:
[0357] 3> Start or restart the bwp-InactivityTimer associated with the active DL BWP.
[0358] 5.7 Discontinuous Reception (DRX)
[0359] The MAC entity may be configured by RRC with DRX functionality that controls the PDCCH of the UE, thereby monitoring the activity of the MAC entity's C-RNTI, CI-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI and TPC-SRS-RNTI. When using DRX operation, the MAC entity shall also monitor the PDCCH in accordance with the requirements present in other clauses of this specification. When in RRC_CONNECTED, if DRX is configured, then for all activated serving cells, the MAC entity may monitor the PDCCH discontinuously using the DRX operation specified in this clause; otherwise the MAC entity shall monitor the PDCCH as specified in TS 38.213 [6].
[0360] RRC controls DRX operation by configuring the following parameters:
[0361] -drx-onDurationTimer: duration when the DRX cycle starts;
[0362] -drx-SlotOffset: Delay before starting drx-onDurationTimer;
[0363] -drx-InactivityTimer: duration after the PDCCH opportunity where the PDCCH indicates a new UL or DL transmission by the MAC entity;
[0364] -drx-RetransmissionTimerDL (per DL HARQ process, except the broadcast process): maximum duration until a DL retransmission is received;
[0365] -drx-RetransmissionTimerUL (per UL HARQ process): maximum duration until a grant for UL retransmission is received;
[0366] -drx-LongCycleStartOffset: long DRX cycle and drx-StartOffset of the subframe that defines the start of long and short DRX cycles;
[0367] -drx-ShortCycle (optional): short DRX cycle;
[0368] -drx-ShortCycleTimer (optional): duration of the short DRX cycle that the UE will follow;
[0369] -drx-HARQ-RTT-TimerDL (per DL HARQ process, except broadcast process): minimum duration before the MAC entity expects a DL assignment of a HARQ retransmission;
[0370] -drx-HARQ-RTT-TimerUL (per UL HARQ process): minimum duration before the MAC entity expects a UL HARQ retransmission grant;
[0371] -ps-Wakeup (optional): starts the configuration of the associated drx-onDurationTimer when DCP is monitored but not detected;
[0372] -ps-Periodic_CSI_Transmit (optional): configuration to report periodic CSI during the duration indicated by drx-onDurationTimer if DCP is configured but the associated drx-onDurationTimer has not started;
[0373] -ps-TransmitPeriodicL1-RSRP (optional): Configuration to transmit periodic L1-RSRP reports during the duration indicated by drx-onDurationTimer if DCP is configured but the associated drx-onDurationTimer has not started.
[0374] When a DRX cycle is configured, the active time includes the time when:
[0375] - drx-onDurationTimer or drx-InactivityTimer or drx-RetransmissionTimerDL or drx-RetransmissionTimerUL or ra-ContentionResolutionTimer (as described in clause 5.1.5) is running; or
[0376] - a scheduling request is sent on the PUCCH and is pending (as described in clause 5.4.4); or
[0377] - Indicating that a newly transmitted PDCCH addressed to the C-RNTI of the MAC entity has not been received after successfully receiving a random access response of a random access preamble that was not selected by the MAC entity among contention-based random access preambles (as described in clause 5.1.4).
[0378] In the RAN1#98 meeting, RAN1 had some agreements on NR multi-radio access technology (Radio Access Technology, RAT) dual connectivity (Multi-Radio Access Technology Dual-Connectivity, MR-DC) and power saving. At least some of the agreements are quoted below from R1-1909942:
[0379] protocol:
[0380] ● From the RAN1 perspective, L1-based mechanisms for switching between 'sleeping' and 'non-sleeping' behaviors on activated Scells can be supported
[0381] ○'Sleeping'=>No PDCCH monitoring on sparse / activated SCells, while maintaining CSI measurement / reporting
[0382] In the RAN1#98b meeting, RAN1 had some agreements on NR MR-DC and power saving. At least some of the agreements are quoted below from R1-1913275:
[0383] protocol:
[0384] o An explicit information field for the UE is introduced into the PDCCH WUS for the L1 based mechanism on the activated Scell for transitioning from 'dormant' to 'non-dormant' behavior when the UE exceeds the active time
[0385] ○ The explicit information field is configurable in the range of 0 to X1 bits
[0386] ■X1<<15
[0387] o For L1 based mechanism on activated Scell for switching between 'dormant' and 'non-dormant' behavior when UE is in active time, explicit information field is newly introduced to at least DCI formats 0-1 and 1-1 of primary cell
[0388] ○ The explicit information field is configurable in the range of 0 to X2 bits
[0389] ■X2<<15
[0390] protocol:
[0391] ● For L1-based SCell dormancy indication sent on the primary cell during active time
[0392] ○ The UE is configured with at least two BWPs of the SCell
[0393] ■ Explicit information field in DCI indicating switching to / from a sleep BWP configured for SCell
[0394] ●FFS definition of sleep BWP
[0395] ●FFS same BWP whether to switch delay to non-sleep to sleep transition delay
[0396] protocol:
[0397] ● For L1-based SCell dormancy indication sent on the primary cell outside active time in WUS PDCCH
[0398] ○ The explicit information field in the DCI is a bitmap with a maximum of X1 bits and 1 bit per group of configured Scells
[0399] ■ Each SCell group may have one / multiple Scells and a maximum of X1 SCell groups may be configured via RRC.
[0400] ●SCell group configuration is independent of the SCell group configuration indicated by the sleep indicator during active time (if supported)
[0401] ■X1=[5]
[0402] ●Note: X1 is the upper limit.
[0403] ○ NOTE: The number of bits used for the Explicit Information field in the WUS PDCCH is based on the configuration
[0404] Working hypothesis
[0405] ● For L1-based SCell dormancy indication sent on the primary cell during active time
[0406] ○ For PDCCH with sleep indication, the following two cases are supported:
[0407] ■ Case 1: PDCCH schedules data for the primary cell and also indicates the dormancy of the SCell
[0408] ○X2=5 (Note: X2 is the upper limit)
[0409] ○ Discuss the detailed design of the explicit information field in DCI and the associated RRC signaling in RAN1#99
[0410] ■ Case 2: PDCCH indicates SCell sleep when there is no scheduling data
[0411] ○ Discuss the detailed design of the explicit information field in the DCI in RAN1#99
[0412] ○ The UE indicates whether the PDCCH with sleep indication is based on case 1 or case 2
[0413] ■FFS details: e.g. dedicated bits for differentiation, reserved combinations of DCI fields, etc.
[0414] ■ Note: No new RRC signaling introduced specifically for this indication
[0415] In the RAN1#99 meeting, RAN1 had some agreements on NR MR-DC and power saving. At least some of the agreements are quoted below from the draft report of 3GPPTSG RAN WG1#99v0.1.0:
[0416] protocol:
[0417] ● At least in the case when the PDCCH schedules data for the primary cell and also indicates dormancy of the SCell (ie, case 1),
[0418] ○N (0≤N≤X2) SCell groups are configured for the UE, where each SCell group may have one or more Scells
[0419] ■ Note: SCell group configuration is independent of the agreed SCell group configuration for sleep indication outside active time
[0420] ■ Note: X2=5 per RAN1#98b is a working assumption.
[0421] ○ The explicit information field for SCell dormancy indication is a bitmap of length N, where each bit corresponds to one SCell group.
[0422] o The bitmap is appended to the existing fields of DCI formats 0-1, 1-1 (ie, the size of DCI formats 0-1, 1-1 is increased by N (0≤N≤X2) bits).
[0423] protocol:
[0424] Fallback DCI formats (0_0 and 1_0) are not used for sleep indication
[0425] protocol:
[0426] ● When PDCCH with DCI format 1-1 is used to indicate the dormancy of SCell
[0427] ○UE expects PDCCH not to be used for PDSCH scheduling
[0428] ■ In the case where the FDRA fields in PDCCH DCI format 1-1 are all set to 1 (when Type 1 RA is used for UE), or
[0429] ■ In the case where the FDRA fields in PDCCH DCI format 1-1 are all set to 0 (when only type 0RA UE)
[0430] protocol:
[0431] ●For SCell sleep indication outside of active time, confirm X1=5
[0432] protocol:
[0433] ● In the case when the PDCCH with DCI format 1-1 is used to indicate the dormancy of the SCell and the UE indicates that the PDCCH is not used for PDSCH scheduling (i.e., case 2)
[0434] ■ The explicit information field for SCell dormancy indication is a bitmap of length N1, where N1 is the number of configured Scells of the UE, and each bit in the bitmap corresponds to a configured SCell
[0435] ■Re-deploy the following fields in the PDCCH for sleep indication: MCS (5), NDI (1), RV (2), HARQ process number (4), antenna port (at least 4), DMRS sequence initialization
[0436] ●Do not redeploy other fields
[0437] ○ Whether the FFS CIF (if present) can indicate SCell
[0438] ○ Note: The DCI format size is the same as that of case 1 (i.e., if RRC configures N (0≤N≤X2) SCell groups, then N bits are added to the DCI)
[0439] protocol:
[0440] ● When the UE is outside of active time, the same BWP framework as in active time is used for the L1 based mechanism for switching between 'dormant' and 'non-dormant' behavior
[0441] protocol:
[0442] ●At least for the case of sleep indication during active time
[0443] ○ If '0' is indicated by the DCI field
[0444] ■ If UE is in non-sleep BWP, then UE switches to sleep BWP
[0445] ■ If UE is in sleep BWP, then UE continues to sleep BWP
[0446] ○ If '1' is indicated by the DCI field
[0447] ■ If 'UE is in non-sleep BWP, then UE continues with the same non-sleep BWP
[0448] ■ If the UE is in a sleeping BWP, then switch to a specific non-sleeping BWP explicitly configured by RRC
[0449] protocol
[0450] For sleep indication beyond the active time, in order to interpret the '0' and '1' in the SCell sleep indication field,
[0451] ●Use the same method as during the event
[0452] protocol:
[0453] ●DCI formats 0-1 are not used for case 2 sleep indication
[0454] protocol:
[0455] ● For type 2 codebook, in response to detecting case 2 PDCCH with SCell sleep indication, ACK is transmitted by the UE
[0456] ● For type 1 codebook, in response to detecting case 2 PDCCH with SCell sleep indication, HARQ response is not supported
[0457] protocol:
[0458] If the default BWP is not a sleep BWP, then the BWP inactivity timer is not used to transition from a sleep BWP to another BWP
[0459] In the RAN1#100-e meeting, RAN1 had some agreements on NR MR-DC and power saving. At least some of the agreements are quoted below from the draft report of 3GPP TSG RAN WG1#100-e v0.2.0:
[0460] protocol:
[0461] ● When the UE is configured with CIF, 'DCI format 0-1 / 1-1 on primary cell with CIF≠0' is not used for case 1 SCell dormancy indication.
[0462] ● Case 2 sleep indication using DCI format 1-1 is not supported when DCI CRC is scrambled by CS-RNTI
[0463] In 3GPP TS 38.331 V16.0.0, some information elements are provided. For cross-carrier scheduling and / or cross-cell scheduling, the network may enable or configure cif-Presence for the configuration of the scheduling cell (e.g., primary cell (PCell), primary secondary cell (PSCell) and / or secondary cell (SCell)), and provide a scheduling cell ID and an associated carrier indicator field (CIF) value (e.g., in downlink control information (DCI)) for the configuration of the scheduled cell (e.g., SCell). A portion of 3GPP TS 38.331 V16.0.0 including at least some of the information elements is quoted as follows:
[0464] CellGroupConfig
[0465] The CellGroupConfig IE is used to configure a master cell group (MCG) or a secondary cell group (SCG). A cell group includes a MAC entity, a set of logical channels with an associated RLC entity, a primary cell (SpCell), and one or more secondary cells (SCells).
[0466] CellGroupConfig Information Element
[0467]
[0468]
[0469]
[0470]
[0471]
[0472]
[0473]
[0474]
[0475] …
[0476]
[0477]
[0478] SCellIndex
[0479] IE SCellIndex relates to a short identifier for identifying an SCell or PSCell. The value range is shared in a cell group.
[0480] SCellIndex Information Element
[0481]
[0482]
[0483]
[0484]
[0485] -ServCellIndex
[0486] The IE ServCellIndex relates to a short identifier for identifying a serving cell (ie, PCell, PSCell or SCell). A value of 0 applies to a PCell, while a previously assigned SCellIndex applies to a SCell.
[0487] ServCellIndex Information Element
[0488] --ASN1START
[0489] --TAG-SERVCELLINDEX-START
[0490] ServCellIndex::=INTEGER(0..maxNrofServingCells-1)
[0491] --TAG-SERVCELLINDEX-STOP
[0492] --ASN1STOP
[0493] Some and / or all of the following terms and / or assumptions may be used below:
[0494] ●BS: A network central unit and / or network node in the new radio access technology (NR), which is used to control one or more transmission and reception points (TRPs) associated with one or more cells. The BS communicates with the TRPs via the outbound route. The BS can be called a central unit (CU), eNB, gNB and / or NodeB.
[0495] ●TRP: TRP provides network coverage and communicates directly with UE. TRP can be called distributed unit (DU) and / or network node.
[0496] ● Cell: A cell is composed of one or more associated TRPs, i.e., the coverage of a cell includes the coverage of some and / or all associated TRPs. A cell is controlled by one BS. A cell can be called a TRP group (TRPG).
[0497] NR-Physical Downlink Control Channel (PDCCH): The channel carries downlink control signals used to control the communication between the UE and the network side. The network transmits the NR-PDCCH to the UE on the configured control resource set (CORESET).
[0498] ●Uplink control signal (UL control signal): The UL control signal can be at least one of a scheduling request (SR) for downlink transmission, channel state information (CSI), a hybrid automatic repeat request (HARQ-acknowledgement (HARQ-ACK), and / or a hybrid automatic repeat request negative acknowledgment (HARQ-NACK).
[0499] ●Slot: A scheduling unit in NR. The duration of a slot can be 14 OFDM symbols.
[0500] ● DL common signal: a data channel carrying common information targeted at multiple UEs in a cell and / or some and / or all UEs in a cell. Examples of DL common signals may be at least one of system information, paging, random access response (Random Access Response, RAR), etc.
[0501] For the network side:
[0502] ●Downlink timing synchronization of TRPs in the same cell.
[0503] • The Radio Resource Control (RRC) layer on the network side is in the BS.
[0504] On the UE side:
[0505] There are at least two UE (RRC) states: a connected state (or active state) and a non-connected state (or inactive state and / or idle state). The non-active state may be an additional state and / or may belong to the connected state and / or the non-connected state.
[0506] Power saving is an important feature of devices and / or UEs in wireless communication systems. Reducing power consumption can extend and / or save the battery life of devices and / or UEs and provide environmentally friendly devices and / or UEs. In LTE systems and / or NR Rel-15 systems, UEs may be configured with discontinuous reception (DRX). For example, the UE may perform PDCCH monitoring during the active time of the DRX cycle, and may not perform PDCCH monitoring outside the active time of the DRX cycle. Therefore, the power consumption of the UE may be reduced by performing PDCCH monitoring based on the active time of the DRX cycle. The amount of power consumption may be based on the proportion of the DRX cycle corresponding to the active time.
[0507] In NR Rel-16, additional power saving schemes have been introduced for reducing power consumption of UEs and / or devices. For example, one mechanism for reducing power consumption corresponds to configuring a sleeping bandwidth part (BWP) in a secondary cell (SCell). In some instances, configuring a sleeping BWP in a SCell provides a reduction in power consumption of the UE and / or network, such as when the UE and / or network has less than a threshold amount of data to transmit or receive. In some instances, when the UE is in a sleeping BWP in a SCell, the UE may be in a power saving state. For example, when the UE is in a sleeping BWP, the UE may not monitor a PDCCH associated with (e.g., on and / or for) the SCell.
[0508] SCell sleep information may be indicated using layer 1 (L1) signaling (e.g., downlink control information (DCI)). For example, L1 signaling (e.g., DCI) may be used to indicate SCell sleep information of a cell (e.g., SCell) to a UE. In some instances, L1 signaling may include DCI format 2_6, DCI format 1_1, and / or DCI format 0_1.
[0509] Throughout this disclosure, one, some and / or all examples of “sleep state” as used herein may correspond to and / or be replaced by “hibernate,” “sleep,” “sleep indication,” and / or “hibernate indication.”
[0510] Throughout this disclosure, one, some and / or all examples of “non-sleep state” as used herein may correspond to and / or be replaced by “non-sleep”, “non-sleep”, “non-sleep indication” and / or “non-sleep indication”.
[0511] Throughout the present disclosure, in a scenario where data (e.g., DCI, DCI format, one or more bit fields and / or a bitmap) indicates the dormant state of a cell, the data (e.g., DCI, DCI format, one or more bit fields and / or a bitmap) may include and / or indicate at least one of the following: an indication of whether the cell is dormant or non-dormant; an indication of whether the cell is dormant or non-dormant; an indication of whether the cell is sleeping or non-sleeping; an indication of whether the cell is sleeping or non-sleeping; an indication of whether the cell has switched to sleep, etc.
[0512] Throughout the present disclosure, in scenarios where data (e.g., DCI, DCI format, one or more bit fields and / or bitmap) indicates the sleep state of a cell, the data (e.g., DCI, DCI format, one or more bit fields and / or bitmap) may include and / or indicate at least one of: sleep of the cell; sleep indication of the cell; sleep indication of the cell; indication of cell sleep, etc.
[0513] Throughout the present disclosure, in scenarios where data (e.g., DCI, DCI format, one or more bit fields and / or bitmap) indicates a non-sleep state of a cell, the data (e.g., DCI, DCI format, one or more bit fields and / or bitmap) may include and / or indicate at least one of: non-sleep state of a cell; an indication of non-sleep state of a cell; an indication of non-sleep state of a cell; an indication of non-sleep state of a cell, etc.
[0514] In some instances, DCI format 2_6 may indicate SCell sleep information of the SCell and / or whether one or more UEs enter and / or switch to the sleep BWP of the SCell. For example, for one or more UEs, DCI format 2_6 and / or SCell sleep information may indicate the SCell sleep state of the SCell. The SCell sleep state may indicate a sleep state (e.g., a sleep SCell state and / or a sleep BWP state) or a non-sleep state (e.g., a non-sleep SCell state and / or a non-sleep BWP state). In some instances, the SCell sleep state of the SCell indicating the sleep state may correspond to an indication and / or instruction that one or more UEs use the sleep BWP of the SCell, continue to use the sleep BWP of the SCell, switch and / or enter the sleep BWP of the SCell, do not use the non-sleep BWP of the SCell, and / or switch from the active BWP of the SCell to the sleep BWP of the SCell. Alternatively and / or in addition, the SCell sleep state indicating the non-sleep state may correspond to an indication and / or instruction that one or more UEs use the non-sleep BWP of the SCell, continue to use the non-sleep BWP of the SCell, switch and / or enter the non-sleep BWP of the SCell, do not use the sleep BWP of the SCell, and / or switch from the sleep BWP of the SCell to the non-sleep BWP of the SCell. For example, a UE in one or more UEs may determine whether to enter and / or switch to the sleep BWP of the SCell based on DCI format 2_6. In some instances, in response to receiving DCI format 2_6, if DCI format 2_6 indicates entering and / or switching to the sleep BWP (e.g., if the SCell sleep state of the SCell indicates the sleep state), then the UE may enter and / or switch to the sleep BWP. Alternatively and / or in addition, DCI format 2_6 may indicate SCell sleep information associated with multiple SCells (e.g., SCell sleep state). Alternatively and / or in addition, for each SCell in the plurality of SCells, DCI format 2_6 may indicate a SCell sleep state associated with the SCell (and / or whether to direct and / or instruct one or more UEs to enter and / or switch to a sleep BWP of the SCell). In some instances, DCI format 2_6 may be received outside of an active time of one or more UEs (e.g., an active time of a DRX cycle). For example, DCI format 2_6 may be used to indicate SCell sleep information associated with one or more SCells to one or more UEs outside of an active time of one or more UEs (and / or to indicate other information).
[0515] In some instances, the UE may monitor DCI format 2_6 based on a search space configuration (e.g., a search space configuration with which the UE is configured) and / or a DRX configuration (e.g., a DRX configuration with which the UE is configured). In some instances, the UE monitors DCI format 2_6 outside of active time (e.g., the UE may monitor DCI format 2_6 only outside of the UE's active time and / or may not monitor DCI format 2_6 during the UE's active time). In some instances, DCI format 2_6 may be used for (and / or indicated as and / or transmitted to) a UE group including the UE (e.g., the UE group may monitor and / or receive DCI format 2_6, and / or the UE group may be the intended recipient of DCI format 2_6). The UE may receive DCI format 2_6 before the active time of a DRX cycle (e.g., the UE's DRX cycle), such as the most recent DRX cycle, the current DRX cycle, and / or the next DRX cycle. DCI format 2_6 may indicate (and / or guide) one or more SCell sleep states of one or more SCells applicable to an active time (e.g., a next active time, such as an upcoming active time of a current DRX cycle and / or an active time of a next DRX cycle after the current DRX cycle) to a UE and / or a UE group. For example, DCI format 2_6 may indicate (and / or guide) to a UE and / or a UE group whether to enter and / or switch to one or more sleep BWPs of one or more SCells in an active time (e.g., a next active time, such as an upcoming active time of a current DRX cycle and / or an active time of a next DRX cycle after the current DRX cycle). In some instances, a network (e.g., a gNB) may provide a search space configuration for (e.g., indicating) one or more monitoring opportunities of DCI format 2_6. In some instances, at least one DCI format 2_6 (e.g., at least one DCI format 2_6 monitoring opportunity and / or at least one DCI format 2_6 reception) may be associated with (and / or during) a DRX cycle. For example, the search space configuration may indicate one or more DCI format 2_6 monitoring opportunities for each of the multiple DRX cycles. Alternatively and / or in addition, the periodicity of DCI format 2_6 (e.g., the time period between DCI format 2_6 monitoring opportunities and / or the time period between DCI format 2_6 receptions) may be configured to be the same as the periodicity of the DRX cycle of the UE (e.g., the time period of the DRX cycle).
[0516] During the active time, there are multiple situations for indicating SCell sleep information. In the first situation (Situation 1) among the multiple situations, DCI with scheduling information may be used to indicate SCell sleep information to indicate SCell sleep information (e.g., DCI may indicate SCell sleep information and scheduling information). In the second situation (Situation 2) among the multiple situations, DCI without scheduling information may be used to indicate SCell sleep information to indicate SCell sleep information (e.g., DCI may indicate SCell sleep information and / or may not indicate scheduling information). For example, in the second situation, DCI may indicate SCell sleep information without scheduling PDSCH and / or without indicating a release of a semi-persistent scheduling (Semi-Persistent Scheduling, SPS) physical downlink shared channel (Physical Downlink Shared Channel; PDSCH). In some instances, the DCI of the second situation may indicate an invalid frequency resource allocation.
[0517] In some instances, in a first case, a DCI format including DCI format 0_1 and / or DCI format 1_1 may be used to indicate SCell sleep information, wherein a field (e.g., SCell sleep indication field, e.g., an explicit SCell sleep indication field) (e.g., a field) in a DCI format having a bitmap (e.g., in the form of a bitmap) indicates one or more SCell sleep states associated with one or more SCell groups (e.g., one or more groups of SCells) (e.g., the field and / or the bitmap indicates whether the one or more SCell groups are switched to a sleep BWP). The field (e.g., the SCell sleep indication field) may include a bitmap. In some instances, a bit of the bitmap is associated with an SCell group (e.g., one or more groups of SCells) in one or more SCell groups (e.g., the bit may indicate the SCell sleep state of the SCell group). Alternatively and / or in addition, each bit of the bitmap may be associated with an SCell group in one or more SCell groups (e.g., each bit of the bitmap may indicate the SCell sleep state of the SCell group in one or more SCell groups). In some instances, an SCell group in one or more SCell groups may be configured by a parameter (e.g., a higher layer parameter, such as a SCell-groups-for-dormancy-within-active-time parameter). In some instances, a bit of a bitmap having a value (e.g., 0 or 1) indicates a sleep state of a SCell in the SCell group associated with the bit (e.g., a bit having a value indicates a sleep state of all SCells in the SCell group associated with the bit). For example, a bit of a bitmap having a value indicates and / or directs the SCell group associated with the bit to enter and / or switch into a sleep BWP for each SCell in the SCell group. Alternatively and / or in addition, a bit of a bitmap having a value corresponds to an indication and / or instruction to enter and / or switch into a sleep BWP for each SCell in the SCell group associated with the bit. If DCI (having a DCI format, such as DCI format 0_1 and / or DCI format 1_1) is configured and / or transmitted in a primary cell (PCell) and / or a primary secondary cell (PSCell), the field (e.g., SCell sleep indication field) may be included in the DCI (and / or may be present in the DCI). Alternatively and / or in addition, the field (e.g., explicit SCell sleep indication field) may be included in the DCI (and / or may be present in the DCI) only when the DCI (having a DCI format, such as DCI format 0_1 and / or DCI format 1_1) is configured and / or transmitted in a PCell and / or a PSCell.
[0518] In some instances, in the second case, DCI format 1_1 may be used to indicate SCell sleep information, wherein one or more fields in DCI format 1_1 may be used to indicate one or more SCell sleep indications. For example, one or more fields may be redeployed for SCell sleep indication (e.g., indicating SCell sleep information). For example, one or more fields (e.g., one or more redeployed fields) may be used for one or more purposes other than SCell sleep indication (so as to indicate information other than SCell sleep information). In some instances, one or more fields in DCI format 1_1 (e.g., one or more redeployed fields) may include a modulation and coding scheme (MCS) field, a new data indicator (NDI) field, a redundancy version (rv) field of a transport block (TB) (e.g., rv of a transport block 1 (TB1) field), a HARQ process number field, one or more antenna port fields, and / or a demodulation reference signal (DMRS) sequence initialization field. One or more fields (e.g., one or more redeployed fields) may be in the form of a bitmap (and / or may include a bitmap). In some instances, a bit of the bitmap is associated with a SCell (e.g., a bit may indicate a SCell sleep state of the SCell). Alternatively and / or in addition, each bit of the bitmap may be associated with a SCell (e.g., a SCell in a cell group, such as a master cell group (MCG) and / or a secondary cell group (SCG)), wherein the association of the bit of the bitmap with the associated SCell associated with the bit may be based on an increasing (or decreasing) SCell index (e.g., SCellIndex). For example, each bit of the bitmap may indicate a sleep state of a SCell, such as wherein a first bit of the bitmap indicates a first sleep state of a first SCell in a cell group, a second bit of the bitmap indicates a second sleep state of a second SCell in the cell group, and the like. In some instances, for an MCG including one or more PCells and / or one or more SCells, there may be up to 15 SCells in the MCG. In some instances, for an SCG including one or more PSCells and / or one or more SCells, there may be up to 16 cells (e.g., 16 SCells) in the SCG. Therefore, one or more fields (e.g., one or more redeployed fields) that may include between about 15 bits and about 17 bits may be sufficient and / or adequate to indicate SCell dormancy information in a cell group (e.g., MCG and / or SCG).In some instances, whether DCI format 1_1 includes an explicit field (e.g., an explicit SCell sleep indication field) or one or more re-deployed fields for SCell sleep indication is determined and / or configured based on whether DCI with DCI format 1_1 is configured and / or transmitted in a PCell and / or PSCell (e.g., of a UE). For example, if the DCI is configured and / or transmitted in a PCell and / or PSCell, then the DCI with DCI format 1_1 may include an explicit field, and / or if the DCI is configured and / or transmitted in a cell other than a PCell and / or PSCell, then the DCI with DCI format 1_1 may include one or more re-deployed fields.
[0519] In RP-193260, the research objectives related to dynamic spectrum sharing (DSS) are to allow SCell to schedule (e.g., via cross-carrier scheduling and / or cross-cell scheduling) PCell and / or allow SCell to schedule (e.g., via cross-carrier scheduling and / or cross-cell scheduling) PSCell. In one possible scenario, the PCell or PSCell is in LTE-NR coexistence and / or control overhead in the PCell, or the PSCell can be transformed and / or switched to the SCell (e.g., scheduling the SCell). Although this DSS mechanism can provide flexibility for network providers to provide services via NR and / or LTE systems, the DSS mechanism can affect power saving (e.g., one or more power saving mechanisms introduced above). There are one or more problems with implementing the DSS mechanism to indicate SCell sleep information via L1 signaling (e.g., DCI), such as in Case 1 and Case 2. For Case 1, it is unclear whether the SCell group (and / or each SCell group in one or more SCell groups associated with a field such as the SCell sleep indication field) can include a scheduled SCell that schedules the PCell or PSCell. For case 2, when the UE receives DCI format 1_1 indicating SCell sleep information in a scheduled SCell that schedules a PCell, it is unclear how (and / or whether) to interpret the associated bit associated with the scheduled SCell (e.g., where the associated bit indicates the SCell sleep state of the scheduled SCell). If the associated bit has a value indicating a sleep state (e.g., 0 or 1), then there may be no UE-specific control signaling for the scheduled PCell or PSCell (e.g., due to the UE entering and / or switching to a sleep BWP of a scheduled SCell that schedules the PCell or PSCell based on the associated bit having a value).
[0520] Figures 5 to 6 The examples are described in . Figure 5A first table 502 representing a first bitmap and a second table 504 representing a second bitmap are illustrated. The first bitmap may be associated with an MCG, and / or the second bitmap may be associated with an SCG. For example, a field (e.g., an SCell sleep indication field associated with case 1 and / or one or more redeployed bit fields associated with case 2) of a DCI (e.g., a DCI having a DCI format 1_1) received by a UE may include the first bitmap in a context in which the field is associated with an MCG, and / or the field may include the second bitmap in a context in which the field is associated with an SCG. With respect to the first bitmap associated with the MCG, in an instance where the scheduling SCell (which schedules PCell) has SCell index 3 and the associated bit corresponding to bit position a_3 of the first bitmap indicates a sleep state, the DCI may result in the absence of UE-specific PDCCH scheduling for the PCell (e.g., due to the UE entering and / or switching into the sleep BWP of the scheduling SCell based on the associated bit indicating the sleep state of the scheduling SCell (which schedules PCell), which may result in the absence of PDCCH monitoring and / or reception for the scheduling SCell and / or on the scheduling SCell). Therefore, entering and / or switching into the sleep BWP of the scheduling SCell and / or the absence of UE-specific PDCCH scheduling for the PCell may affect the scheduling flexibility of the network scheduling PCell (e.g., the PCell will be scheduled using the scheduling SCell). Such problems may also occur in SCGs, for example, where the second bit field indicates the sleep state of the scheduling SCell of the scheduling PSCell, resulting in, for example, the absence of UE-specific PDCCH scheduling for the PSCell.
[0521] Figure 6 A scenario is illustrated in which a UE receives DCI 606 indicating SCell dormancy associated with one or more SCells of the UE. The DCI 606 may be received via a search space 608. The DCI 606 may have a DCI format 1_1 having a bitmap for indicating SCell dormancy. Figure 6 Table 602 represents a bitmap. In some instances, the bitmap indicates a sleep state of a first SCell having an SCell index of 31. For example, the UE may switch 610 from an active BWP of the first SCell to a sleep BWP of the first SCell based on the bitmap. At a bit position a_15 of the bitmap equal to a value (e.g., 0), the UE may switch 610 from an active BWP of the first SCell to a sleep BWP of the first SCell based on an associated bit, wherein the associated bit is associated with the first SCell having an SCell index of 31 (e.g., indicating a sleep state of the first SCell).
[0522] In some instances, a scheduled SCell of a UE that schedules 604 (e.g., cross-cell scheduling) a PCell of a UE may have an SCell index of 3. If the associated bit corresponding to bit position a_3 of the bitmap indicates a sleep state (e.g., if the associated bit associated with the scheduled SCell is equal to a value, such as 0), then the DCI may result in the absence of UE-specific PDCCH scheduling for the PCell (e.g., due to the UE entering and / or switching into a sleep BWP of the scheduled SCell based on the associated bit indicating the sleep state of the scheduled SCell (which schedules the PCell), which may result in the absence of PDCCH monitoring and / or reception for the scheduled SCell and / or on the scheduled SCell). The bitmap may be associated with the SCell of the MCG. Such issues may also occur in the SCG. In the SCG, Figure 6 The PCell of the instance scenario can be replaced by the PSCell.
[0523] One or more techniques are provided herein to address one or more of the aforementioned problems and / or to avoid the UE not having and / or receiving UE-specific control signaling for scheduling a PCell or PSCell (for example, if the UE enters and / or switches to the sleep BWP of a scheduled SCell that schedules a PCell or PSCell based on sleep information received by the UE, then the UE may not have and / or may not receive UE-specific control signaling for scheduling a PCell or PSCell).
[0524] Example 1
[0525] In embodiment 1 of the present disclosure, a field (eg, a field of DCI) may not indicate the sleep state of a scheduled SCell of a scheduled PCell or PSCell (eg, a field does not indicate the sleep state of a scheduled SCell).
[0526] In some instances, in a bitmap indicating SCell sleep information, a bit position associated with the first SCell (and / or addresses and / or indicates the first SCell) may not exist in the bitmap. Alternatively and / or in addition, the UE may ignore the value of the bit position associated with the first SCell (and / or addresses and / or indicates the first SCell) in the bitmap (e.g., the indication value indicated by the bit) (e.g., the UE may ignore the value of the bit indicating the SCell sleep state of the first SCell). In some instances, the first SCell is a scheduled SCell of a scheduled (e.g., cross-carrier scheduled and / or cross-cell scheduled) PCell (e.g., in a scenario where the SCell is in an MCG) or a PSCell (e.g., in a scenario where the SCell is in an SCG). Alternatively and / or in addition, the first SCell may be used to receive one or more DCIs indicating SCell sleep information (e.g., one or more DCIs indicating SCell sleep information may be received in the first SCell).
[0527] In some instances, in the context of a PCell or PSCell scheduling (e.g., cross-carrier scheduling and / or cross-cell scheduling) one or more SCells, the size and / or number of bits of the bitmap (indicating SCell sleep) may be a first size and / or a first number of bits. Alternatively and / or in addition, in the context of a SCell scheduling (e.g., cross-carrier scheduling and / or cross-cell scheduling) a PCell (e.g., if the SCell is in an MCG and / or the bitmap indicates sleep information associated with the SCell of the MCG) or a PSCell (e.g., if the SCell is in an SCG and / or the bitmap indicates sleep information associated with the SCell of the SCG), the size and / or number of bits of the bitmap may be a second size and / or a second number of bits. In some instances, the second size and / or the second number of bits may be less than and / or smaller than the first size and / or the first number of bits. In an example, the second number of bits may be equal to the first number of bits minus one.
[0528] In some instances, the size and / or number of bits of the bitmap may correspond to (e.g., be equal to) the number of configured SCells in the same cell group (e.g., an MCG or SCG includes an SCell whose sleep information is indicated by the bitmap), wherein the configured SCells may not include a PCell, a PSCell, an SCell that schedules a PCell or a PSCell (e.g., the SCell is scheduled across carriers and / or the PCell or PSCell is scheduled across cells), and / or an SCell that receives one or more DCIs indicating SCell sleep information (e.g., one or more DCIs indicating SCell sleep information may be received in the SCell, wherein the DCI in the one or more DCIs may indicate the bitmap). In an instance, the configured SCells (e.g., the number of which is equivalent to the number of bits of the bitmap) may include: configured SCells other than the PSCell in the same cell group (e.g., all configured SCells in the same cell group); an SCell that schedules a PCell or a PSCell (e.g., the SCell is scheduled across carriers and / or the PCell or PSCell is scheduled across cells); and / or an SCell that receives one or more DCIs indicating SCell sleep information. Alternatively and / or in addition, the bitmap may indicate the sleep state of the SCells in the configured SCells (and / or the bitmap may indicate the sleep state of each SCell in the configured SCells).
[0529] In some instances, the UE receives a DCI indicating SCell sleep information via a bitmap (e.g., the DCI may include a bitmap indicating SCell sleep information). Each bit position in the bitmap may be associated with a SCell group (e.g., a group of one or more SCells), wherein the SCell group associated with the bitmap may be in the same cell group, such as an MCG or an SCG. Each bit position in the bitmap may indicate, via a bit at the bit position, a SCell sleep state associated with the associated SCell group, the associated SCell group being associated with the bit position. For example, each bit position in the bitmap may indicate, via a bit at the bit position, whether the associated SCell group associated with the bit position is switched to (and / or enters and / or remains in) a sleep state, such as a state in which the SCells in the SCell group are each in a sleep state (e.g., for each SCell in the SCell, the UE switches and / or enters and / or remains in a sleep BWP for the SCell). If the bitmap indicates a sleep state of a first SCell group including a first SCell (e.g., if a bit of the bitmap having a bit position associated with the first SCell group indicates a sleep state), the UE may not consider the first SCell to have a sleep state (and / or the UE may not apply the sleep state to the first SCell and / or may not switch the first SCell from the active BWP of the first SCell to the sleep BWP), wherein the UE may consider one or more other SCells other than the first SCell in the first SCell group to have a sleep state based on the bitmap (and / or the UE may apply the sleep state to one or more other SCells in the first SCell group and / or for each of the one or more other SCells, the UE may switch from the active BWP of the SCell to the sleep BWP). The first SCell may be used for scheduling (e.g., cross-cell scheduling and / or cross-carrier scheduling) a PCell and / or a PSCell. For example, the UE may not consider that the first SCell has a sleep state based on the fact that the first SCell is being used for scheduling (e.g., cross-cell scheduling and / or cross-carrier scheduling) the PCell and / or PSCell (and / or the UE may not apply the sleep state to the first SCell, and / or may not switch the first SCell from a non-sleep BWP to a sleep BWP).
[0530] The bitmap includes (and / or is generated from and / or determined using) one or more bit fields in the DCI that indicate sleep information (eg, SCell sleep information).
[0531] The one or more bit fields may be SCell sleep indication fields.
[0532] Alternatively and / or in addition, the one or more bit fields may include at least one of an MCS field, an NDI field, an rv field of a TB (e.g., rv of a TB1 field), a HARQ process number field, one or more antenna port fields, a DMRS sequence initialization field, etc. in a DCI indicating sleep information and / or in a DCI format (e.g., of the DCI). Alternatively and / or in addition, the one or more bit fields may include one or more other fields in a DCI indicating sleep information and / or in a DCI format (e.g., of the DCI). In some instances, the one or more other fields may not be used for HARQ-ACK related feedback for confirming whether the DCI indicating sleep information is successfully received.
[0533] The DCI indicating the dormancy information may be used to schedule data (eg, for scheduling transmission and / or reception of data). Alternatively and / or additionally, the DCI indicating the dormancy information may not schedule data (eg, the DCI may not schedule transmission and / or reception of data).
[0534] In with Figure 7 and / or Figure 8 In an associated example scenario, the scheduled SCell of the scheduled PCell has SCell index 3 (wherein the scheduled SCell is in the MCG), and the SCells with SCell indices 1, 2, 3, 8, 10...31 are in the MCG. The UE receives a DCI with a bitmap for indicating SCell sleep information. The DCI is received in the scheduled SCell with SCell index 3. The bitmap comes from and / or is included in one or more bit fields (and / or is determined using one or more bit fields), and the one or more bit fields are in the DCI and / or in the DCI format of the DCI. The one or more bit fields may include at least one of an MCS field, an NDI field, an rv field of a TB (e.g., an rv of a TB1 field), a HARQ process number field, one or more antenna port fields, a DMRS sequence initialization field, etc. In some instances, the bits of the bitmap indicate the sleep state of the associated SCell (e.g., the SCell associated with the bit and / or the bit position of the bit). For example, each bit of the bitmap (and / or each bit portion of the bitmap, such as a portion of a bit of the bitmap) may indicate a sleep state of an associated SCell (e.g., an SCell associated with the bit and / or bit portion). Alternatively and / or in addition, a bit of the bitmap (and / or a bit portion) may be associated with (and / or may indicate a sleep state of) a configured SCell in an MCG that does not include an SCell with SCell index 3 (e.g., each configured SCell in the MCG). The association of a bit of the bitmap with an associated SCell associated with the bit may be based on an increasing or decreasing SCell index.
[0535] Figure 7 Table 702 associated with the bitmap is illustrated. Figure 7 In the example shown in , the bitmap may include 14 bits (e.g., there may be 14 bits for one or more bit fields), such as bits with bit positions a_1, a_2 ... a_14. Table 702 shows the bit positions of the bitmap and the SCell index of the SCell associated with the bit positions. Figure 7 In the example shown in , the association between the bits of the bitmap and the SCells may be based on an increasing SCell index starting with the most significant bit (MSB) (e.g., a high-order bit and / or a leftmost bit) of the bitmap, such as where bits at higher-order (e.g., further left) bit positions (e.g., bit position a_1) are associated with a SCell associated with a lower SCell index (e.g., SCell index 1) (e.g., indicating a sleep state of the SCell), and / or bits at lower-order (e.g., further right) bit positions (e.g., bit position a_14) are associated with a SCell associated with a higher SCell index (e.g., SCell index 31) (e.g., indicating a sleep state of the SCell). It will be appreciated that the association between the bits of the bitmap and the SCells may be different than Figure 7 For example, it is contemplated that the association between the bits of the bitmap and the SCell is based on an increasing SCell index (e.g., with respect to the SCell index) starting from the least significant bit (LSB) (e.g., low-order bit, and / or rightmost bit) of the bitmap. Figure 7 ) is an embodiment of the present invention (the arrangement of the associations shown in Table 702 is opposite to that of the arrangement of the associations shown in Table 702). In some instances, each bit of the 14 bits may indicate the sleep state of the associated SCell associated with the bit. For example, the UE may consider and / or interpret a bit of the 14 bits that is equal to a value (e.g., 0 or 1) as an indication of the sleep state of the associated SCell associated with the bit. For example, for each bit of the 14 bits that is equal to the value, the UE may consider and / or interpret the bit as an indication of the sleep state of the associated SCell associated with the bit. In the example relative to Table 702, if the bit corresponding to bit position a_2 is equal to the value, the UE may consider and / or interpret the bit as an indication of the sleep state of the SCell having SCell index 2 associated with bit position a_2 (and / or the UE may switch and / or enter into the sleep BWP of the SCell having SCell index 2 based on the bit). Figure 7In the example shown in , the bit corresponding to bit position a_3 is associated with the SCell having SCell index 8 rather than the bit being associated with the SCell having SCell index 3. For example, the bit corresponding to bit position a_3 may be associated with the SCell having SCell index 8 rather than the SCell having SCell index 3 because (e.g., based on a determination) the SCell having SCell index 3 is used to schedule the PCell and / or because (e.g., based on a determination) the SCell having SCell index 3 is used to receive DCI indicating SCell sleep information. In some examples, in a scenario where the SCell schedules the PCell and / or a DCI indicating SCell sleep information is received in the SCell, a first size and / or a first number of bits of one or more bit fields and / or bitmaps is less than and / or less than a second size and / or a second number of bits of one or more bit fields and / or bitmaps in a scenario where the PCell schedules one or more SCells and / or a DCI indicating SCell sleep information is received in the PCell. For example, the first size and / or the first number of bits being less than and / or smaller than the second size and / or the second number of bits may be due to the bitmap not including an SCell (e.g., an SCell associated with SCell index 3, e.g., Figure 7 Discussion) associated bits, the SCell scheduling the PCell and / or for receiving DCI for indicating SCell sleep information.
[0536] Figure 8 Table 802 associated with the bitmap is illustrated. Figure 8 In the example shown in , the bitmap may include 15 bits (e.g., there may be 15 bits for one or more bit fields), such as bits with bit positions a_1, a_2...a_15. Table 802 shows the bit positions of the bitmap. Table 802 shows the SCell index of the SCell associated with the 14-bit position of the bitmap. In some examples, each of the 14 bits associated with the 14-bit position may indicate the sleep state of the associated SCell associated with the bit. For example, the UE may regard and / or interpret a bit of the 14 bits that is equal to a value (e.g., 0 or 1) as an indication of the sleep state of the associated SCell associated with the bit. For example, for each bit of the 14 bits that is equal to the value, the UE may regard and / or interpret the bit as an indication of the sleep state of the associated SCell associated with the bit. In some examples, the bitmap may include a first bit other than the 14 bits that does not indicate the sleep state of the SCell. In some examples, the first bit may correspond to the MSB (e.g., the high-order bit and / or the leftmost bit) or the LSB (e.g., the low-order bit and / or the rightmost bit) of the bitmap. Figure 8As shown in , the first bit may have a bit position a_15 of the bitmap. In some instances, the bitmap includes a first bit (which does not indicate the sleep state of the SCell) based on the SCell (e.g., the SCell with SCell index 3) scheduling the PCell and / or based on receiving a DCI indicating SCell sleep information in the SCell (e.g., the SCell with SCell index 3). In some instances, in a scenario where the SCell (e.g., the SCell with SCell index 3) schedules the PCell and / or the DCI indicating SCell sleep information is received in the SCell (e.g., the SCell with SCell index 3), the first size and / or the first number of one or more bit fields and / or bitmaps are less than and / or less than the second size and / or the second number of bits of one or more bit fields and / or bitmaps in a scenario where the PCell schedules one or more SCells and / or the DCI indicating SCell sleep information is received in the PCell.
[0537] In some examples, the UE is configured with one or more cells (eg, one or more serving cells) including a second cell.
[0538] In some examples, the UE is configured to receive in the second cell DCI for scheduling data in the first cell.
[0539] Alternatively and / or in addition, the UE may be configured to receive in the second cell a DCI indicating sleep information (e.g., SCell sleep information) of one or more configured cells in a cell group (e.g., one or more configured cells in the same cell group, e.g., the same cell group including the second cell).
[0540] In some examples, the UE receives DCI having the DCI format in the second cell.
[0541] In some instances, the DCI and / or DCI format indicates sleep information (e.g., one or more sleep states) of one or more configured cells in a cell group (e.g., one or more configured cells in the same cell group, such as the same cell group including the second cell).
[0542] In some instances, the same cell group means and / or implies that the cell group includes the second cell.
[0543] In some instances, sleep information (e.g., SCell sleep information including one or more sleep states) is indicated by one or more bit fields in the DCI and / or DCI format. One or more bit fields may be redeployed for sleep indication (e.g., indicating sleep information). For example, sleep information may be indicated by redeploying one or more bit fields for SCell sleep indication. For example, one or more bit fields may include a bit field for indicating other information other than SCell sleep information in other receptions of a DCI format corresponding to the DCI format. One or more bit fields include one or more bits associated with one or more configured cells in a cell group (e.g., one or more configured cells in the same cell group, such as the same cell group including a second cell) (e.g., indicating the sleep state of the one or more configured cells). Each bit of the one or more bit fields (and / or each bit from the one or more bit fields and / or in the one or more bit fields) is associated with a configured cell in one or more configured cells (e.g., indicating the sleep state of the configured cell). In some instances, the one or more configured cells do not include the first cell and do not include the second cell. In some instances, the one or more configured cells include each cell in the cell group except the first cell and the second cell.
[0544] In some instances, the association (between one or more bits of the one or more bit fields and one or more configured cells excluding the first cell and the second cell) corresponds to a one-to-one mapping (e.g., a strictly one-to-one mapping), for example, where one bit of the one or more bit fields is associated with one of the one or more configured cells (e.g., indicating a dormant state of the configured cell). Alternatively and / or in addition, the association may be based on an ascending order of the SCell index (e.g., starting from the MSB or LSB of the one or more bit fields), as described herein Figure 7 Discuss its examples.
[0545] In some instances, the one or more bit fields do not include a bit and / or a bit position indicating the sleep state of the second cell (eg, a bit and / or a bit position indicating the sleep state of the second cell is not present in the one or more bit fields).
[0546] In some instances, the DCI indicates the sleep state of one or more cells. After receiving the DCI and / or in response to receiving the DCI, the UE switches from one or more active BWPs (e.g., active downlink and / or uplink BWPs) of one or more cells to one or more sleep BWPs of one or more cells, and / or the UE communicates with the network in the sleep BWP in one or more sleep BWPs of one or more cells. The one or more sleep BWPs may include the sleep BWP of one or more cells. Alternatively and / or in addition, the one or more sleep BWPs may include each sleep BWP of one or more cells. Alternatively and / or in addition, for each cell in one or more cells, the one or more sleep BWPs include the sleep BWP of the cell.
[0547] In some instances, when the UE is in a sleep BWP of a configured cell (e.g., a configured serving cell) (and / or after the UE switches from an active BWP of a configured cell to a sleep BWP of a configured cell), the UE skips monitoring the sleep BWP for the cell and / or DCI on the sleep BWP.
[0548] In some instances, the UE is configured with a sleep BWP for a cell (eg, a serving cell with which the UE is configured).
[0549] In some examples, for each cell other than the first cell (eg, each serving cell with which the UE is configured), the UE is configured with a sleep BWP.
[0550] In some examples, for each cell in the cell group except the first cell (eg, each serving cell with which the UE is configured), the UE is configured with a sleep BWP.
[0551] In some examples, for each cell other than the first cell and the second cell (eg, each serving cell with which the UE is configured), the UE is configured with a sleep BWP.
[0552] In some examples, for each cell in the cell group except the first cell and the second cell (eg, each serving cell with which the UE is configured), the UE is configured with a sleep BWP.
[0553] In some examples, for each SCell in a cell group (eg, each serving SCell with which the UE is configured), the UE is configured with a sleep BWP.
[0554] In some examples, for each SCell in the cell group except the second cell (eg, each serving SCell with which the UE is configured), the UE is configured with a sleep BWP.
[0555] In some examples, the UE is configured to receive DCI in the second cell, where the DCI may schedule the second cell (e.g., self-scheduling) and / or the first cell (e.g., cross-carrier scheduling and / or cross-cell scheduling). The DCI may be UE-specific and / or in a UE-specific search space. Alternatively and / or in addition, the DCI may be associated with a UE-specific search space in the first cell or the second cell.
[0556] In some instances, the UE camps on the NR system and / or accesses the NR system via the first cell.
[0557] In some instances, the UE receives a synchronization signal block (SSB) in a first cell for accessing the NR system (e.g., in idle mode).
[0558] In some examples, the UE enters the connected mode from the idle mode by accessing the first cell.
[0559] In some examples, in a first cell, the UE receives common control information (eg, group common control information and / or cell common control information), such as common DCI, and / or control information (eg, DCI) in a common search space.
[0560] In some instances, in the first cell, the UE only receives common control information (eg, group common control information and / or cell common control information), such as common DCI, and / or control information (eg, DCI) in a common search space.
[0561] In some examples, the UE does not receive UE-specific control information (eg, UE-specific DCI) in the first cell, and the UE does not receive control information (eg, DCI) in a UE-specific search space in the first cell.
[0562] In some examples, the first cell is a PSCell or a PCell.
[0563] In some examples, the second cell is a SCell.
[0564] In some instances, the second cell is not a PSCell.
[0565] In some examples, the first cell and the second cell are in the same cell group (eg, the first cell and the second cell are in an MCG, or the first cell and the second cell are in an SCG).
[0566] In some examples, the size and / or number of bits of the one or more bit fields used to indicate the dormancy information may be based on whether the first cell schedules the second cell or the second cell schedules the first cell.
[0567] In some examples, in the context of the second cell scheduling the first cell, the one or more bit fields for indicating the sleep information have a first size and / or a first bit number. In the context of the first cell scheduling the second cell, the one or more bit fields for indicating the sleep information have a second size and / or a second bit number. The first size and / or the first bit number may be less than and / or smaller than the second size and / or the second bit number.
[0568] In some examples, the size and / or number of bits of the one or more bit fields used to indicate the dormancy information may not be based on whether the first cell schedules the second cell or the second cell schedules the first cell.
[0569] In some instances, the size and / or number of bits of one or more bit fields used to indicate sleep information in the context of the second cell scheduling the first cell is the same as the size and / or number of bits of one or more bit fields used to indicate sleep information in the context of the first cell scheduling the second cell.
[0570] In some instances, in the context of the second cell scheduling the first cell, the UE uses the first bit of the one or more bit fields equivalent to the first bit number to determine the sleep information associated with one or more configured cells (for example, the UE determines the sleep information based on the first bit equivalent to the first bit number). Alternatively and / or in addition, in the context of the second cell scheduling the first cell, the network uses the first bit of the one or more bit fields equivalent to the first bit number to indicate the sleep information of the UE. In some instances, in the context of the first cell scheduling the second cell, the UE uses the second bit of the one or more bit fields equivalent to the second bit number to determine the sleep information associated with one or more configured cells (for example, the UE determines the sleep information based on the second bit equivalent to the second bit number). Alternatively and / or in addition, in the context of the second cell scheduling the first cell, the network uses the second bit of the one or more bit fields equivalent to the second bit number to indicate the sleep information of the UE. In some instances, the first bit number is less than the second bit number. In some instances, the first bit does not include a bit associated with the second cell (for example, one bit), and / or the first bit does not include a bit indicating the sleep state of the second cell (for example, one bit). The second bit includes a bit (e.g., one bit) associated with the second cell, and / or the second bit includes a bit (e.g., one bit) indicating a sleep state of the second cell. The first bit and / or the second bit do not include a bit (e.g., one bit) associated with the first cell, and / or the first bit and / or the second bit do not include a bit (e.g., one bit) indicating a sleep state of the first cell.
[0571] In some instances, cross-cell scheduling and / or cross-carrier scheduling may imply and / or mean that the scheduling control information and / or control channel is in a first cell and / or first carrier that is different from a second cell and / or second carrier associated with scheduled data (e.g., scheduled data scheduled for a second cell and / or second carrier via the scheduling control information and / or control channel).
[0572] In some instances, self-scheduling may imply and / or mean that the scheduling control information and / or control channel is in the same cell and / or the same carrier as the scheduled data (e.g., scheduled data scheduled for the same cell and / or the same carrier via the scheduling control information and / or control channel).
[0573] In order to enhance the 3GPP MAC specification for wireless communication according to some embodiments herein, enhancements 1-2 are provided herein. Enhancements 1-2 reflect implementations according to some embodiments herein and include additions to section 10.3 of 3GPP TS 38.213 V16.1.0. According to some embodiments, one and / or two of enhancements 1-2 may be implemented. A portion of section 10.3 of 3GPP TS 38.213 V16.1.0 is quoted below without any additions to enhancements 1-2:
[0574] If a search space set is provided to the UE to monitor the PDCCH for detecting DCI format 1_1, and if
[0575] - The CRC of DCI format 1_1 is scrambled by C-RNTI or MCS-C-RNTI, and if
[0576] -resourceAllocation=resourceAllocationType0, and all bits of the frequency domain resource allocation field in DCI format 1_1 are equal to 0, or
[0577] -resourceAllocation=resourceAllocationType1, and all bits of the frequency domain resource allocation field in DCI format 1_1 are equal to 1
[0578] -resourceAllocation=dynamicSwitch, and all bits of the frequency domain resource allocation field in DCI format 1_1 are equal to 0 or 1
[0579] The UE regards DCI format 1_1 as indicating SCell dormancy, not scheduling PDSCH reception or indicating SPS PDSCH release, and interprets the following sequence of fields for transport block 1:
[0580] - Modulation and coding scheme
[0581] - New data indicator
[0582] - Redundant version
[0583] and the following sequence of fields:
[0584] -HARQ process number
[0585] - Antenna ports
[0586] -DMRS sequence initialization
[0587] When the bitmap is provided to each configured SCell in ascending order of SCell index,
[0588] - A '0' in a bitmap indicates an active DL BWP, provided by dormant-BWP for the UE corresponding to the activated SCell
[0589] - A '1' value for a bit in the bitmap indicates
[0590] -Active DL BWP, when the current active DL BWP is a dormant DL BWP, for the UE corresponding to the activated SCell, provided by first-non-dormant-BWP-ID-for-DCI-inside-active-time
[0591] -Currently active DL BWP, if the currently active DL BWP is not the sleep DL BWP, for the UE corresponding to the activated SCell
[0592] -UE sets the active DL BWP to the indicated active DL BWP
[0593] In enhancement 1, according to some embodiments of the present disclosure (e.g., one or more embodiments described with respect to embodiment 1), addition 1 is made to a portion of section 10.3 of 3GPP TS 38.213 V16.1.0. Addition 1 assumes that, when a bitmap (e.g., indicating sleep information) is provided to a UE, the bitmap includes a bit associated with a configured SCell (e.g., indicating the sleep state of the configured SCell), and the configured SCell does not include a SCell that schedules a PCell and / or a PSCell, or does not include a SCell that receives DCI format 1_1 (e.g., including a bitmap). Without addition 1 to enhancement 1, section 10.3 of 3GPP TS 38.213 V16.1.0 assumes that the bitmap includes a bit associated with each configured SCell (e.g., indicating the sleep state of each configured SCell). Thus, by partially performing operations according to section 10.3 (as originally provided in 3GPP TS 38.213 V16.1.0), the bitmap may include bits indicating the sleep state of the SCell that schedules the PCell and / or PSCell, and therefore, there may be no UE-specific control signaling for scheduling the PCell or PSCell.
[0594] Addition 1 of Enhancement 1 is shown in bold and begins with the term "Start of Addition 1:" followed by the term "End of Addition 1" to distinguish Addition 1 from the content originally contained in section 10.3 of 3GPP TS 38.213 V16.1.0.
[0595] Enhancement 1
[0596] If a search space set is provided to the UE to monitor the PDCCH for detecting DCI format 1_1, and if
[0597] - The CRC of DCI format 1_1 is scrambled by C-RNTI or MCS-C-RNTI, and if
[0598] -resourceAllocation=resourceAllocationType0, and all bits of the frequency domain resource allocation field in DCI format 1_1 are equal to 0, or
[0599] -resourceAllocation=resourceAllocationType1, and all bits of the frequency domain resource allocation field in DCI format 1_1 are equal to 1
[0600] -resourceAllocation=dynamicSwitch, and all bits of the frequency domain resource allocation field in DCI format 1_1 are equal to 0 or 1
[0601] The UE regards DCI format 1_1 as indicating SCell dormancy, not scheduling PDSCH reception or indicating SPS PDSCH release, and interprets the following sequence of fields for transport block 1:
[0602] - Modulation and coding scheme
[0603] - New data indicator
[0604] - Redundant version
[0605] and the following sequence of fields:
[0606] -HARQ process number
[0607] - Antenna ports
[0608] -DMRS sequence initialization
[0609] When the bitmap is provided to each configured SCell in ascending order of SCell index, adding 1 starts: except for the SCell that schedules the PCell and / or PSCell or the SCell for receiving DCI format 1_1, adding 1 ends, where
[0610] - A '0' in a bitmap indicates an active DL BWP, provided by dormant-BWP for the UE corresponding to the activated SCell
[0611] - A '1' value for a bit in the bitmap indicates
[0612] -Active DL BWP, when the current active DL BWP is a dormant DL BWP, for the UE corresponding to the activated SCell, provided by first-non-dormant-BWP-ID-for-DCI-inside-active-time
[0613] -Currently active DL BWP, if the currently active DL BWP is not the sleep DL BWP, for the UE corresponding to the activated SCell
[0614] -UE sets the active DL BWP to the indicated active DL BWP
[0615] Example 2
[0616] In embodiment 2 of the present disclosure, a field (eg, a field of DCI) may indicate a sleep state of a scheduled SCell of a scheduled PCell or PSCell, wherein the network may set the field to indicate a non-sleep state of the scheduled SCell.
[0617] In some instances, there may be constraints and / or restrictions on the network regarding scheduling, indicating and / or configuring SCell sleep information. In an instance, for a bitmap indicating SCell sleep information, the network (e.g., gNB) shall set the first bit of the first bit position in the bitmap to indicate a non-sleep state and / or set the first bit of the first bit position to indicate a first value (e.g., 1). For example, the network may set the first bit to indicate a non-sleep state, and / or the network may set the first bit to the first value (e.g., the first bit set to the first value may indicate a non-sleep state of the SCell associated with the first bit and / or the first bit position). Alternatively and / or in addition, the network may not set the first bit of the first bit position in the bitmap (e.g., the network is not allowed to set and / or the network is not configured to set and / or prohibit the network setting and / or prevent the network setting) to indicate a sleep state, and the network may not set the first bit (e.g., the network is not allowed to set and / or the network is not configured to set and / or prohibit the network setting and / or prevent the network setting) to indicate a second value (e.g., 0). In some instances, the first bit set to the second value may indicate the sleep state of the SCell associated with the first bit and / or the first bit position. Alternatively and / or in addition, it is not expected and / or anticipated that the UE receives a bitmap having the first bit and / or the first bit position in the bitmap indicating the sleep state. In some instances, the first bit and / or the first bit position is associated with (and / or addresses and / or indicates) the first SCell. For example, the first bit and / or the first bit position indicates the sleep state of the first SCell. In some instances, the first SCell is a scheduled SCell of a scheduled (e.g., cross-carrier scheduled and / or cross-cell scheduled) PCell (e.g., in a scenario where the SCell is in an MCG) or a PSCell (e.g., in a scenario where the SCell is in an SCG). Alternatively and / or in addition, the first SCell may be used to receive one or more DCIs indicating SCell sleep information (e.g., one or more DCIs indicating SCell sleep information may be received in the first SCell, wherein the DCI in the one or more DCIs may include the first bit and / or the first bit position associated with the first SCell).
[0618] In some instances, a bitmap may indicate SCell sleep information, wherein a bit in the bitmap indicates a sleep state of an SCell group (e.g., a group of one or more SCells), and / or wherein each bit in the bitmap indicates a sleep state of an SCell group. In some instances, a network (e.g., a gNB) may not configure (e.g., not allow network configuration and / or the network is not configured to configure and / or prohibit network configuration and / or prevent network configuration) a first SCell as associated with any bit and / or bit position in the bitmap. The first SCell may be used for scheduling (e.g., cross-cell scheduling and / or cross-carrier scheduling) a PCell and / or a PSCell. For example, the UE may not expect the first SCell to be configured into (and / or be part of) an SCell group (e.g., any SCell group) associated with the bitmap. Alternatively and / or in addition, the UE may not expect the first SCell to be configured into (and / or be part of) an SCell group (e.g., any SCell group) whose sleep state is indicated by the bitmap (e.g., any SCell group). Alternatively and / or in addition, the UE may not consider the first SCell to be part of the SCell group (e.g., any SCell group) associated with the bitmap. Alternatively and / or in addition, the UE may not consider the first SCell to be part of the SCell group (e.g., any SCell group) whose sleep state is indicated by the bitmap. Alternatively and / or in addition, the first SCell may not be configured into the SCell group (e.g., any SCell group) associated with the bitmap (and / or may not be part of the SCell group). Alternatively and / or in addition, the first SCell may not be configured into the SCell group (e.g., any SCell group) whose sleep state is indicated by the bitmap (and / or may not be part of the SCell group). Alternatively and / or in addition, the bit of the bitmap indicating the sleep state of the SCell group may not be associated with the first SCell (and / or may not indicate the sleep state of the first SCell) (and / or the bitmap may not include a bit indicating the sleep state of the SCell group, i.e., indicating the sleep state of the first SCell).
[0619] In some instances, the size and / or number of bits of the bitmap may not be based on whether the SCell (in a cell group, e.g., an MCG or an SCG including SCells in which the bitmap indicates sleep information) schedules (e.g., cross-carrier scheduling and / or cross-cell scheduling) a PCell or PSCell (e.g., of the cell group), or whether the PCell or PSCell (e.g., in the cell group) schedules (e.g., cross-carrier scheduling and / or cross-cell scheduling) one or more SCells (e.g., in the cell group). Alternatively and / or in addition, the size and / or number of bits of the bitmap may be equal to the first size and / or the first number of bits regardless of whether the SCell in a cell group (e.g., an MCG or SCG including SCells in which the bitmap indicates sleep information) schedules (e.g., cross-carrier scheduling and / or cross-cell scheduling) a PCell or PSCell (e.g., of the cell group), or whether the PCell or PSCell (e.g., in the cell group) schedules (e.g., cross-carrier scheduling and / or cross-cell scheduling) one or more SCells (e.g., in the cell group).
[0620] In some instances, the size and / or number of bits of the bitmap may correspond to (e.g., be equal to) the number of configured SCells in the same cell group (e.g., an MCG or SCG includes an SCell whose sleep information is indicated by a bitmap), wherein the configured SCells may not include a PCell, a PSCell, an SCell scheduling a PCell or PSCell (e.g., an SCell is scheduled across carriers and / or a PCell or PSCell is scheduled across cells), and / or an SCell receiving one or more DCIs indicating SCell sleep information (e.g., one or more DCIs indicating SCell sleep information may be received in the SCell, wherein the DCI in the one or more DCIs may indicate a bitmap). In an example, configured SCells (e.g., the number of which is equivalent to the number of bits in the bitmap) may include: configured SCells other than PSCells in the same cell group (e.g., all configured SCells in the same cell group); SCells that schedule PCells or PSCells (e.g., the SCells schedule PCells or PSCells across carriers and / or schedule PCells or PSCells across cells); and / or SCells that receive one or more DCIs indicating SCell sleep information (e.g., one or more DCIs indicating SCell sleep information may be received in the SCell, wherein the DCIs in the one or more DCIs may indicate a bitmap). Alternatively and / or in addition, the bitmap may indicate the sleep state of the SCells in the configured SCells (and / or the bitmap may indicate the sleep state of each SCell in the configured SCells).
[0621] The bitmap includes (and / or is generated from and / or determined using) one or more bit fields in the DCI that indicate sleep information (eg, SCell sleep information).
[0622] The one or more bit fields may be SCell sleep indication fields.
[0623] Alternatively and / or in addition, the one or more bit fields may include at least one of an MCS field, an NDI field, an rv field of a TB (e.g., rv of a TB1 field), a HARQ process number field, one or more antenna port fields, a DMRS sequence initialization field, etc. in a DCI indicating sleep information and / or in a DCI format (e.g., of the DCI). Alternatively and / or in addition, the one or more bit fields may include one or more other fields in a DCI indicating sleep information and / or in a DCI format (e.g., of the DCI). In some instances, the one or more other fields may not be used for HARQ-ACK related feedback for confirming whether the DCI indicating sleep information is successfully received.
[0624] The DCI indicating the dormancy information may be used to schedule data (eg, for scheduling transmission and / or reception of data). Alternatively and / or additionally, the DCI indicating the dormancy information may not schedule data (eg, the DCI may not schedule transmission and / or reception of data).
[0625] In About Figure 5 In the instances of Table 502 and / or Table 504, if bit position a_3 of the bitmap is associated with an SCell of a scheduled (e.g., cross-carrier scheduled and / or cross-cell scheduled) PCell or PSCell, and / or if position a_3 of the bitmap is associated with an SCell of a received one or more DCIs indicating SCell sleep information, then the network may not set the bit at bit position a_3 (e.g., the network is not allowed to set and / or the network is not configured to set and / or prohibit network setting and / or prevent network setting) to indicate a sleep state, and the network may not set the bit at bit position a_3 (e.g., the network is not allowed to set and / or the network is not configured to set and / or prohibit network setting and / or prevent network setting) to indicate a second value (e.g., 0).
[0626] In some examples, the UE is configured with one or more cells (eg, one or more serving cells) including a second cell.
[0627] In some examples, the UE is configured to receive in the second cell DCI for scheduling data in the first cell.
[0628] Alternatively and / or in addition, the UE may be configured to receive in the second cell a DCI indicating sleep information (e.g., SCell sleep information) of one or more configured cells in a cell group (e.g., one or more configured cells in the same cell group, e.g., the same cell group including the second cell).
[0629] In some examples, the UE receives DCI having the DCI format in the second cell.
[0630] In some instances, the DCI and / or DCI format indicates sleep information (e.g., one or more sleep states) of one or more configured cells in a cell group (e.g., one or more configured cells in the same cell group, such as the same cell group including the second cell).
[0631] In some instances, the same cell group means and / or implies that the cell group includes the second cell.
[0632] In some instances, sleep information (e.g., SCell sleep information including one or more sleep states) is indicated by one or more bit fields in the DCI and / or DCI format. One or more bit fields may be redeployed for sleep indication (e.g., indicating sleep information). For example, sleep information may be indicated by redeploying one or more bit fields for SCell sleep indication. For example, one or more bit fields may include a bit field for indicating other information other than SCell sleep information in other receptions of a DCI format corresponding to the DCI format. One or more bit fields include one or more bits associated with one or more configured cells in a cell group (e.g., one or more configured cells in the same cell group, such as the same cell group including a second cell) (e.g., indicating the sleep state of the one or more configured cells). Each bit of the one or more bit fields (and / or each bit from the one or more bit fields and / or in the one or more bit fields) is associated with a configured cell in one or more configured cells (e.g., indicating the sleep state of the configured cell). In some instances, one or more configured cells include each cell in the cell group. Alternatively and / or additionally, the one or more configured cells may not include the first cell (eg, the one or more configured cells include each cell in the cell group except the first cell).
[0633] In some instances, the association (between one or more bits of the one or more bit fields and one or more configured cells including the second cell and excluding the first cell) corresponds to a one-to-one mapping (e.g., a strictly one-to-one mapping), for example, where one bit of the one or more bit fields is associated with one of the one or more configured cells (e.g., indicating a dormant state of the configured cell). Alternatively and / or in addition, the association may be based on an ascending order of the SCell index (e.g., starting from the MSB or LSB of the one or more bit fields).
[0634] In some instances, for one or more bit fields, the UE does not expect to receive and / or indicate a bitmap (e.g., via one or more bit fields) having a bit position and / or a bit indicating a sleep state and / or a second value (e.g., 0) associated with the second cell. For example, the UE does not expect the one or more bit fields and / or a bitmap of the one or more bit fields to indicate a sleep state of the second cell.
[0635] In some instances, the DCI indicates the sleep state of one or more cells. After receiving the DCI and / or in response to receiving the DCI, the UE switches from one or more active BWPs (e.g., active downlink and / or uplink BWPs) of one or more cells to one or more sleep BWPs of one or more cells, and / or the UE communicates with the network in the sleep BWP in one or more sleep BWPs of one or more cells. The one or more sleep BWPs may include the sleep BWP of one or more cells. Alternatively and / or in addition, the one or more sleep BWPs may include each sleep BWP of one or more cells. Alternatively and / or in addition, for each cell in one or more cells, the one or more sleep BWPs include the sleep BWP of the cell.
[0636] In some instances, when the UE is in a sleep BWP of a configured cell (e.g., a configured serving cell) (and / or after the UE switches from an active BWP of a configured cell to a sleep BWP of a configured cell), the UE skips monitoring the sleep BWP for the cell and / or DCI on the sleep BWP.
[0637] In some instances, the UE is configured with a sleep BWP for a cell (eg, a serving cell with which the UE is configured).
[0638] In some examples, for each cell other than the first cell (eg, each serving cell with which the UE is configured), the UE is configured with a sleep BWP.
[0639] In some examples, for each cell in the cell group except the first cell (eg, each serving cell with which the UE is configured), the UE is configured with a sleep BWP.
[0640] In some examples, for each cell other than the first cell and the second cell (eg, each serving cell with which the UE is configured), the UE is configured with a sleep BWP.
[0641] In some examples, for each cell in the cell group except the first cell and the second cell (eg, each serving cell with which the UE is configured), the UE is configured with a sleep BWP.
[0642] In some examples, for each SCell in a cell group (eg, each serving SCell with which the UE is configured), the UE is configured with a sleep BWP.
[0643] In some examples, for each SCell in the cell group except the second cell (eg, each serving SCell with which the UE is configured), the UE is configured with a sleep BWP.
[0644] In some examples, the UE is configured to receive DCI in the second cell, where the DCI may schedule the second cell (e.g., self-scheduling) and / or the first cell (e.g., cross-carrier scheduling and / or cross-cell scheduling). The DCI may be UE-specific and / or in a UE-specific search space. Alternatively and / or in addition, the DCI may be associated with a UE-specific search space in the first cell or the second cell.
[0645] In some instances, the UE camps on the NR system and / or accesses the NR system via the first cell.
[0646] In some instances, the UE receives an SSB in a first cell for accessing the NR system (e.g., in idle mode).
[0647] In some examples, the UE enters the connected mode from the idle mode by accessing the first cell.
[0648] In some examples, in a first cell, the UE receives common control information (eg, group common control information and / or cell common control information), such as common DCI, and / or control information (eg, DCI) in a common search space.
[0649] In some instances, in the first cell, the UE only receives common control information (eg, group common control information and / or cell common control information), such as common DCI, and / or control information (eg, DCI) in a common search space.
[0650] In some examples, the UE does not receive UE-specific control information (eg, UE-specific DCI) in the first cell, and the UE does not receive control information (eg, DCI) in a UE-specific search space in the first cell.
[0651] In some examples, the first cell is a PSCell or a PCell.
[0652] In some examples, the second cell is a SCell.
[0653] In some instances, the second cell is not a PSCell.
[0654] In some examples, the first cell and the second cell are in the same cell group (eg, the first cell and the second cell are in an MCG, or the first cell and the second cell are in an SCG).
[0655] In some examples, the size and / or number of bits of the one or more bit fields used to indicate the dormancy information may not be based on whether the first cell schedules the second cell or the second cell schedules the first cell.
[0656] In some instances, the size and / or number of bits of one or more bit fields used to indicate sleep information in the context of the second cell scheduling the first cell is the same as the size and / or number of bits of one or more bit fields used to indicate sleep information in the context of the first cell scheduling the second cell.
[0657] In some instances, cross-cell scheduling and / or cross-carrier scheduling may imply and / or mean that the scheduling control information and / or control channel is in a first cell and / or first carrier that is different from a second cell and / or second carrier associated with scheduled data (e.g., scheduled data scheduled for a second cell and / or second carrier via the scheduling control information and / or control channel).
[0658] In some instances, self-scheduling may imply and / or mean that the scheduling control information and / or control channel is in the same cell and / or the same carrier as the scheduled data (e.g., scheduled data scheduled for the same cell and / or the same carrier via the scheduling control information and / or control channel).
[0659] In some examples, the first network configures the UE to include one or more cells (eg, one or more serving cells) of the second cell.
[0660] In some examples, the first network configures the UE to receive in the second cell DCI for scheduling data in the first cell.
[0661] Alternatively and / or in addition, the first network may configure the UE to receive in the second cell a DCI indicating sleep information (e.g., SCell sleep information) of one or more configured cells in a cell group (e.g., one or more configured cells in the same cell group, e.g., the same cell group including the second cell).
[0662] In some examples, the first network transmits a DCI having a DCI format in the second cell.
[0663] In some instances, the DCI and / or DCI format indicates sleep information (e.g., one or more sleep states) of one or more configured cells in a cell group (e.g., one or more configured cells in the same cell group, such as the same cell group including the second cell), where the cell group may belong to the first network.
[0664] In some instances, the same cell group means and / or implies that the cell group includes the second cell.
[0665] In some instances, sleep information (e.g., SCell sleep information including one or more sleep states) is indicated by one or more bit fields in the DCI and / or DCI format. One or more bit fields may be redeployed for sleep indication (e.g., indicating sleep information). For example, sleep information may be indicated by redeploying one or more bit fields for SCell sleep indication. For example, one or more bit fields may include a bit field for indicating other information other than SCell sleep information in other transmissions of a DCI format corresponding to the DCI format. One or more bit fields include one or more bits associated with one or more configured cells in a cell group (e.g., one or more configured cells in the same cell group, such as the same cell group including a second cell) (e.g., indicating the sleep state of the one or more configured cells). Each bit of the one or more bit fields (and / or each bit from the one or more bit fields and / or in the one or more bit fields) is associated with a configured cell in one or more configured cells (e.g., indicating the sleep state of the configured cell). In some instances, one or more configured cells include each cell in the cell group. Alternatively and / or additionally, the one or more configured cells may not include the first cell (eg, the one or more configured cells include each cell in the cell group except the first cell). In some examples, the cell group (eg, the same cell group) belongs to the first network.
[0666] In some instances, the association (between one or more bits of the one or more bit fields and one or more configured cells including the second cell and excluding the first cell) corresponds to a one-to-one mapping (e.g., a strictly one-to-one mapping), for example, where one bit of the one or more bit fields is associated with one of the one or more configured cells (e.g., indicating a dormant state of the configured cell). Alternatively and / or in addition, the association may be based on an ascending order of the SCell index (e.g., starting from the MSB or LSB of the one or more bit fields).
[0667] In some instances, for one or more bit fields, the first network is not allowed and / or is not configured to transmit and / or indicate a bitmap having bit positions and / or bits indicating a sleep state and / or a second value (e.g., 0) associated with the second cell (e.g., via one or more bit fields for indicating sleep information).
[0668] In some instances, the first network is not allowed and / or configured to transmit a DCI indicating the sleep state of the second cell.
[0669] In some instances, the DCI indicates a sleep state of one or more cells. After transmitting the DCI and / or receiving a HARQ-ACK associated with the DCI and / or in response to transmitting the DCI and / or receiving a HARQ-ACK associated with the DCI, the first network may not transmit the DCI on and / or for the one or more cells.
[0670] In some examples, the first network may configure a sleep BWP for a UE cell (eg, a serving cell with which the UE is configured).
[0671] In some examples, for each cell other than the first cell (eg, each serving cell with which the UE is configured), the first network may configure the UE sleep BWP.
[0672] In some examples, for each cell in the cell group except the first cell (eg, each serving cell with which the UE is configured), the first network may configure the UE sleep BWP.
[0673] In some examples, for each cell other than the first cell and the second cell (eg, each serving cell with which the UE is configured), the first network may configure the UE sleep BWP.
[0674] In some examples, for each cell in the cell group other than the first cell and the second cell (eg, each serving cell with which the UE is configured), the first network may configure the UE sleep BWP.
[0675] In some examples, for each SCell in the cell group (eg, each serving SCell with which the UE is configured), the first network may configure the UE sleep BWP.
[0676] In some examples, for each cell in the cell group except the second cell (eg, each serving SCell with which the UE is configured), the first network may configure the UE sleep BWP.
[0677] In some instances, the first network may not configure (e.g., does not allow network configuration and / or the network is not configured to configure and / or prohibits network configuration and / or prevents network configuration) scheduling (e.g., cross-carrier scheduling and / or cross-cell scheduling) the sleep BWP of the SCell of the PCell or PSCell.
[0678] In some instances, if the SCell has a configured sleep BWP, the first network may not configure (e.g., not allow network configuration and / or the network is not configured to configure and / or prohibit network configuration and / or prevent network configuration) the SCell to schedule (e.g., cross-carrier scheduling and / or cross-cell scheduling) the PCell or PSCell.
[0679] In some instances, if the SCell has a configured sleep BWP, the first network may not indicate (e.g., network indication is not allowed and / or the network is not configured to indicate and / or prohibit network indication and / or prevent network indication) SCell scheduling (e.g., cross-carrier scheduling and / or cross-cell scheduling) of the PCell or PSCell.
[0680] In some examples, the first network configures the UE to receive DCI in the second cell, where the DCI may schedule the second cell (e.g., self-scheduling) and / or the first cell (e.g., cross-carrier scheduling and / or cross-cell scheduling). The DCI may be UE-specific and / or in a UE-specific search space. Alternatively and / or in addition, the DCI may be associated with a UE-specific search space in the first cell or the second cell.
[0681] In some instances, in a first cell, for one or more UEs including the UE, the first network transmits common control information (e.g., group common control information and / or cell common control information), such as common DCI, and / or control information in a common search space (e.g., DCI).
[0682] In some instances, in the first cell, for one or more UEs including the UE, the first network only transmits common control information (e.g., group common control information and / or cell common control information), such as common DCI, and / or control information in a common search space (e.g., DCI).
[0683] In some instances, for one or more UEs including the UE, the first network does not transmit UE-specific control information (e.g., UE-specific DCI) in the first cell, and for one or more UEs including the UE, the first network does not transmit control information (e.g., DCI) in a UE-specific search space in the first cell.
[0684] In some examples, the first cell is a PSCell or a PCell (eg, in view of a UE).
[0685] In some examples, the second cell is a SCell (eg, in view of a UE).
[0686] In some examples, the second cell is not a PSCell (eg, in view of the UE).
[0687] In some examples, the first network may configure the UE to communicate with the second network.
[0688] In some examples, the first network controls cells in the MCG.
[0689] In some instances, the second network controls cells in the SCG.
[0690] In some examples, the second cell is configured by the first network.
[0691] In some examples, the UE communicates with a first network and a second network (eg, via dual-connectivity (DC)).
[0692] In some examples, the first cell and the second cell are in the same cell group (eg, the first cell and the second cell are in an MCG, or the first cell and the second cell are in an SCG).
[0693] In some examples, the size and / or number of bits of the one or more bit fields used to indicate the dormancy information may not be based on whether the first cell schedules the second cell or the second cell schedules the first cell.
[0694] In some instances, the size and / or number of bits of one or more bit fields used to indicate sleep information in the context of the second cell scheduling the first cell is the same as the size and / or number of bits of one or more bit fields used to indicate sleep information in the context of the first cell scheduling the second cell.
[0695] In some instances, cross-cell scheduling and / or cross-carrier scheduling may imply and / or mean that the scheduling control information and / or control channel is in a first cell and / or first carrier that is different from a second cell and / or second carrier associated with scheduled data (e.g., scheduled data scheduled for a second cell and / or second carrier via the scheduling control information and / or control channel).
[0696] In some instances, self-scheduling may imply and / or mean that the scheduling control information and / or control channel is in the same cell and / or the same carrier as the scheduled data (e.g., scheduled data scheduled for the same cell and / or the same carrier via the scheduling control information and / or control channel).
[0697] In Enhancement 2, Addition 2 is made to a portion of Section 10.3 of 3GPP TS 38.213 V16.1.0 according to some embodiments of the present disclosure (e.g., one or more embodiments described with respect to Embodiment 2). Addition 2 assumes that the UE does not expect a bitmap (e.g., indicating sleep information) to include a bit equal to a value indicating a non-sleep state (e.g., 1), wherein the bit is associated with a SCell that schedules a PCell and / or a PSCell (e.g., indicating a sleep state of the SCell) or is associated with a SCell that receives DCI format 1_1 (e.g., including a bitmap). In the absence of Addition 2 of Enhancement 2, the bit may indicate the sleep state of the SCell that schedules the PCell and / or the PSCell (and / or the UE may expect the bit to indicate the sleep state of the SCell that schedules the PCell and / or the PSCell), and therefore, there may be no UE-specific control signaling for scheduling the PCell or the PSCell.
[0698] Addition 2 of Enhancement 2 is shown in bold and begins with the term "Start of Addition 2:" followed by the term "End of Addition 2" to distinguish Addition 2 from the content originally contained in section 10.3 of 3GPP TS 38.213 V16.1.0.
[0699] Enhancement 2
[0700] If a search space set is provided to the UE to monitor the PDCCH for detecting DCI format 1_1, and if
[0701] - The CRC of DCI format 1_1 is scrambled by C-RNTI or MCS-C-RNTI, and if
[0702] -resourceAllocation=resourceAllocationType0, and all bits of the frequency domain resource allocation field in DCI format 1_1 are equal to 0, or
[0703] -resourceAllocation=resourceAllocationType1, and all bits of the frequency domain resource allocation field in DCI format 1_1 are equal to 1
[0704] -resourceAllocation=dynamicSwitch, and all bits of the frequency domain resource allocation field in DCI format 1_1 are equal to 0 or 1
[0705] The UE regards DCI format 1_1 as indicating SCell dormancy, not scheduling PDSCH reception or indicating SPS PDSCH release, and interprets the following sequence of fields for transport block 1:
[0706] - Modulation and coding scheme
[0707] - New data indicator
[0708] - Redundant version
[0709] and the following sequence of fields:
[0710] -HARQ process number
[0711] - Antenna ports
[0712] -DMRS sequence initialization
[0713] When the bitmap is provided to each configured SCell in ascending order of SCell index,
[0714] - A '0' in a bitmap indicates an active DL BWP, provided by dormant-BWP for the UE corresponding to the activated SCell
[0715] - A '1' value for a bit in the bitmap indicates
[0716] -Active DL BWP, when the current active DL BWP is a dormant DL BWP, for the UE corresponding to the activated SCell, provided by first-non-dormant-BWP-ID-for-DCI-inside-active-time
[0717] -Currently active DL BWP, if the currently active DL BWP is not the sleep DL BWP, for the UE corresponding to the activated SCell
[0718] Add 2 to start:
[0719] - The UE does not expect a value of '1' for a bit of the bitmap associated with the SCell that schedules the PCell and / or PSCell or associated with the SCell for receiving DCI format 1_1
[0720] Add 2 to end
[0721] -UE sets the active DL BWP to the indicated active DL BWP
[0722] Example 3
[0723] In embodiment 3 of the present disclosure, a field (eg, a field of DCI) may indicate the sleep state of a scheduled SCell of a scheduled PCell or PSCell, wherein if the field indicates a non-sleep state of the scheduled SCell, the PCell or PSCell may switch to self-cell scheduling.
[0724] In some instances, for a bitmap indicating SCell sleep information, if the first bit of the first bit position in the bitmap indicates a sleep state, the UE may regard and / or interpret the first bit and / or the first bit position as an indication and / or instruction to switch to self-scheduling. Alternatively and / or in addition, if the scheduled cell is associated with a scheduling cell (e.g., where the scheduling cell schedules (e.g., cross-cell scheduling and / or cross-carrier scheduling) the scheduled cell), and if the scheduling cell is associated with the first bit position and / or the first bit (e.g., where the first bit position and / or the first bit indicates a sleep state of the scheduling cell), the UE may monitor the PDCCH (e.g., UE-specific PDCCH) on the scheduled cell for scheduling the scheduled cell, and / or the UE may not monitor the PDCCH (e.g., UE-specific PDCCH) on the scheduling cell for scheduling the scheduled cell. In some instances, the scheduling cell is an SCell, and / or the scheduled cell is a PCell or a PSCell (or other cell).
[0725] In some instances, if the first bit and / or the first bit position indicates a non-sleeping state, the UE may regard and / or interpret the first bit and / or the first bit position as an indication and / or instruction to switch to (and / or continue) cross-cell and / or cross-carrier scheduling. Alternatively and / or in addition, if the scheduled cell is associated with a scheduling cell (e.g., where the scheduling cell schedules (e.g., cross-cell scheduling and / or cross-carrier scheduling) the scheduled cell), and if the scheduling cell is associated with the first bit position and / or the first bit (e.g., where the first bit position and / or the first bit indicates a non-sleeping state of the scheduling cell), the UE may monitor the PDCCH on the scheduling cell (e.g., a UE-specific PDCCH) for scheduling the scheduled cell, and / or the UE may not monitor the PDCCH on the scheduled cell (e.g., a UE-specific PDCCH) for scheduling the scheduled cell. In some instances, the scheduling cell is an SCell, and / or the scheduled cell is a PCell or a PSCell (or other cell).
[0726] It can be understood that one or more techniques and / or embodiments of Example 3 of the present disclosure (e.g., UE switching to self-scheduling based on bits and / or bit positions of a bitmap) can enable the UE to switch to self-scheduling without RRC signaling, thereby producing benefits including but not limited to faster switching to self-scheduling and / or improved service continuity.
[0727] In some instances, in the context of a PCell or PSCell scheduling (e.g., cross-carrier scheduling and / or cross-cell scheduling) one or more SCells, the size and / or number of bits of the bitmap (indicating SCell sleep) may be a first size and / or a first number of bits. Alternatively and / or in addition, in the context of a SCell scheduling (e.g., cross-carrier scheduling and / or cross-cell scheduling) a PCell (e.g., if the SCell is in an MCG and / or the bitmap indicates sleep information associated with the SCell of the MCG) or a PSCell (e.g., if the SCell is in an SCG and / or the bitmap indicates sleep information associated with the SCell of the SCG), the size and / or number of bits of the bitmap may be a second size and / or a second number of bits. In some instances, the second size and / or the second number of bits are the same as the first size and / or the first number of bits.
[0728] In some instances, the size and / or number of bits of the bitmap may correspond to (e.g., be equal to) the number of configured SCells in the same cell group (e.g., an MCG or SCG includes an SCell whose sleep information is indicated by a bitmap), wherein the configured SCells may not include a PCell, a PSCell, an SCell scheduling a PCell or PSCell (e.g., an SCell is scheduled across carriers and / or a PCell or PSCell is scheduled across cells), and / or an SCell receiving one or more DCIs indicating SCell sleep information (e.g., one or more DCIs indicating SCell sleep information may be received in the SCell, wherein the DCI in the one or more DCIs may indicate a bitmap). In an example, configured SCells (e.g., the number of which is equivalent to the number of bits in the bitmap) may include: configured SCells other than PSCells in the same cell group (e.g., all configured SCells in the same cell group); SCells that schedule PCells or PSCells (e.g., the SCells schedule PCells or PSCells across carriers and / or schedule PCells or PSCells across cells); and / or SCells that receive one or more DCIs indicating SCell sleep information (e.g., one or more DCIs indicating SCell sleep information may be received in the SCell, wherein the DCIs in the one or more DCIs may indicate a bitmap). Alternatively and / or in addition, the bitmap may indicate the sleep state of the SCells in the configured SCells (and / or the bitmap may indicate the sleep state of each SCell in the configured SCells).
[0729] The bitmap includes (and / or is generated from and / or determined using) one or more bit fields in the DCI that indicate sleep information (eg, SCell sleep information).
[0730] Alternatively and / or in addition, the one or more bit fields may include at least one of an MCS field, an NDI field, an rv field of a TB (e.g., rv of a TB1 field), a HARQ process number field, one or more antenna port fields, a DMRS sequence initialization field, etc. in a DCI indicating sleep information and / or in a DCI format (e.g., of the DCI). Alternatively and / or in addition, the one or more bit fields may include one or more other fields in a DCI indicating sleep information and / or in a DCI format (e.g., of the DCI). In some instances, the one or more other fields may not be used for HARQ-ACK related feedback for confirming whether the DCI indicating sleep information is successfully received.
[0731] The DCI indicating the dormancy information may be used to schedule data (eg, for scheduling transmission and / or reception of data). Alternatively and / or additionally, the DCI indicating the dormancy information may not schedule data (eg, the DCI may not schedule transmission and / or reception of data).
[0732] In some examples, the UE is configured with one or more cells (eg, one or more serving cells) including a second cell.
[0733] In some examples, the UE is configured to receive in the second cell DCI for scheduling data in the first cell.
[0734] Alternatively and / or in addition, the UE may be configured to receive in the second cell a DCI indicating sleep information (e.g., SCell sleep information) of one or more configured cells in a cell group (e.g., one or more configured cells in the same cell group, e.g., the same cell group including the second cell).
[0735] In some examples, the UE receives a first DCI having a first DCI format in a second cell.
[0736] In some instances, the first DCI and / or the first DCI format indicates sleep information (e.g., one or more sleep states) of one or more configured cells in a cell group (e.g., one or more configured cells in the same cell group, such as the same cell group including the second cell).
[0737] In some instances, the same cell group means and / or implies that the cell group includes the second cell.
[0738] In some instances, sleep information (e.g., SCell sleep information including one or more sleep states) is indicated by one or more bit fields in the first DCI and / or the first DCI format. One or more bit fields may be redeployed for sleep indication (e.g., indicating sleep information). For example, sleep information may be indicated by redeploying one or more bit fields for SCell sleep indication. For example, one or more bit fields may include a bit field for indicating other information other than SCell sleep information in other receptions of the first DCI format corresponding to the first DCI format. One or more bit fields include one or more bits associated with one or more configured cells in a cell group (e.g., one or more configured cells in the same cell group, such as the same cell group including the second cell) (e.g., indicating the sleep state of the one or more configured cells). Each bit of the one or more bit fields (and / or each bit from the one or more bit fields and / or in the one or more bit fields) is associated with a configured cell in one or more configured cells (e.g., indicating the sleep state of the configured cell). In some instances, the one or more configured cells include each cell in the cell group. Alternatively and / or additionally, the one or more configured cells may not include the first cell (eg, the one or more configured cells include each cell in the cell group except the first cell).
[0739] In some instances, the association (between one or more bits of the one or more bit fields and one or more configured cells including the second cell and excluding the first cell) corresponds to a one-to-one mapping (e.g., a strictly one-to-one mapping), for example, where one bit of the one or more bit fields is associated with one of the one or more configured cells (e.g., indicating a dormant state of the configured cell). Alternatively and / or in addition, the association may be based on an ascending order of the SCell index (e.g., starting from the MSB or LSB of the one or more bit fields).
[0740] In some instances, when receiving the one or more bit fields and / or in response to receiving the one or more bit fields, if the bit of the bit position (in the bitmap) associated with the second cell indicates a sleep state and / or a second value (e.g., 0), the UE may switch the scheduling cell of the first cell from the second cell to the first cell. For example, in the absence of RRC signaling, the UE may switch the scheduling cell (of the first cell) from the second cell to the first cell based on the bit and / or bit position indicating the sleep state of the second cell. In some instances, before receiving the one or more bit fields (and / or before switching the scheduling cell (of the first cell) from the second cell to the first cell), the UE may receive DCI scheduling the first cell (e.g., DCI scheduling data transmission and / or reception of the first cell) on the second cell. Alternatively and / or in addition, after receiving the one or more bit fields and / or in response to receiving the one or more bit fields (and / or after switching the scheduling cell (of the first cell) from the second cell to the first cell and / or in response to switching the scheduling cell from the second cell to the first cell), the UE may receive the DCI scheduling the first cell (e.g., the DCI scheduling data transmission and / or reception of the first cell) on the first cell. In an example, the UE may receive the DCI scheduling the first cell on the first cell after at least one of a processing time from reception of the one or more bit fields (e.g., reception of the first DCI and / or the first DCI format), after transmitting HARQ associated with the first DCI and / or the first DCI format (e.g., HARQ-ACK), after a processing time from transmission of the HARQ of the first DCI, etc. Alternatively and / or in addition, after receiving one or more bit fields and / or in response to receiving one or more bit fields (and / or after switching the scheduling cell (of the first cell) from the second cell to the first cell and / or in response to switching the scheduling cell from the second cell to the first cell), the UE may switch from an active BWP of the second cell (e.g., an active downlink and / or uplink BWP) to a sleep BWP of the second cell, and / or the UE may communicate with the network in the sleep BWP.
[0741] In some instances, when receiving one or more bit fields and / or in response to receiving one or more bit fields, if the bit of the bit position (in the bitmap) associated with the second cell indicates a non-sleep state and / or a first value (e.g., 1), the UE may switch the scheduling cell of the first cell from the first cell to the second cell. For example, in the absence of RRC signaling, the UE may switch the scheduling cell (of the first cell) from the first cell to the second cell based on the bit and / or bit position indicating a non-sleep state of the second cell. In some instances, before receiving the one or more bit fields (and / or before switching the scheduling cell (of the first cell) from the first cell to the second cell), the UE may receive a DCI scheduling the first cell (e.g., a DCI scheduling data transmission and / or reception of the first cell) on the first cell. Alternatively and / or in addition, after receiving the one or more bit fields and / or in response to receiving the one or more bit fields (and / or after switching the scheduling cell (of the first cell) from the first cell to the second cell and / or in response to switching the scheduling cell from the first cell to the second cell), the UE may receive the DCI scheduling the first cell (e.g., the DCI scheduling data transmission and / or reception of the first cell) on the second cell. In an example, the UE may receive the DCI scheduling the first cell on the second cell after at least one of a processing time from reception of the one or more bit fields (e.g., reception of the first DCI and / or the first DCI format), after transmitting HARQ associated with the first DCI and / or the first DCI format (e.g., HARQ-ACK), after a processing time from transmission of the HARQ of the first DCI, etc.
[0742] Alternatively and / or additionally, when receiving the one or more bit fields and / or in response to receiving the one or more bit fields, if the bit of the bit position (in the bitmap) associated with the second cell indicates a non-sleep state and / or a first value (e.g., 1), the UE may maintain the current scheduling cell of the first cell to reserve the second cell. In some instances, before receiving the one or more bit fields (and / or before switching the scheduling cell (of the first cell) from the first cell to the second cell), the UE may receive a DCI scheduling the first cell (e.g., a DCI scheduling data transmission and / or reception of the first cell) on the second cell. Alternatively and / or additionally, after receiving the one or more bit fields and / or in response to receiving the one or more bit fields (and / or after switching the scheduling cell (of the first cell) from the first cell to the second cell and / or in response to switching the scheduling cell from the first cell to the second cell), the UE may receive a DCI scheduling the first cell (e.g., a DCI scheduling data transmission and / or reception of the first cell) on the second cell.
[0743] Alternatively and / or in addition, when receiving one or more bit fields and / or in response to receiving one or more bit fields, if the bit of the bit position (in the bitmap) associated with the second cell indicates a non-sleep state and / or a first value (e.g., 1), then the UE may switch the scheduling cell of the first cell from the second cell to the first cell. For example, in the absence of RRC signaling, the UE may switch the scheduling cell (of the first cell) from the second cell to the first cell based on the bit and / or bit position indicating the non-sleep state of the second cell. In some instances, before receiving the one or more bit fields (and / or before switching the scheduling cell (of the first cell) from the second cell to the first cell), the UE may receive a DCI scheduling the first cell (e.g., a DCI scheduling data transmission and / or reception of the first cell) on the second cell. Alternatively and / or in addition, after receiving the one or more bit fields and / or in response to receiving the one or more bit fields (and / or after switching the scheduling cell (of the first cell) from the second cell to the first cell and / or in response to switching the scheduling cell from the second cell to the first cell), the UE may receive the DCI scheduling the first cell (e.g., the DCI scheduling data transmission and / or reception of the first cell) on the first cell. In an example, the UE may receive the DCI scheduling the first cell on the first cell after at least one of a processing time from reception of the one or more bit fields (e.g., reception of the first DCI and / or the first DCI format), after transmitting HARQ associated with the first DCI and / or the first DCI format (e.g., HARQ-ACK), after a processing time from transmission of the HARQ of the first DCI, etc.
[0744] In some instances, the first DCI indicates a sleep state of one or more cells. After receiving the first DCI and / or in response to receiving the first DCI, the UE switches from one or more active BWPs (e.g., active downlink and / or uplink BWPs) of one or more cells to one or more sleep BWPs of one or more cells, and / or the UE communicates with the network in a sleep BWP in one or more sleep BWPs of one or more cells. The one or more sleep BWPs may include a sleep BWP of one or more cells. Alternatively and / or in addition, the one or more sleep BWPs may include each sleep BWP of one or more cells. Alternatively and / or in addition, for each cell in one or more cells, the one or more sleep BWPs include the sleep BWP of the cell.
[0745] In some instances, when the UE is in a sleep BWP of a configured cell (e.g., a configured serving cell) (and / or after the UE switches from an active BWP of a configured cell to a sleep BWP of a configured cell), the UE skips monitoring the sleep BWP for the cell and / or DCI on the sleep BWP.
[0746] In some instances, the UE is configured with a sleep BWP for a cell (eg, a serving cell with which the UE is configured).
[0747] In some examples, for each cell other than the first cell (eg, each serving cell with which the UE is configured), the UE is configured with a sleep BWP.
[0748] In some examples, for each cell in the cell group except the first cell (eg, each serving cell with which the UE is configured), the UE is configured with a sleep BWP.
[0749] In some examples, for each SCell in a cell group (eg, each serving SCell with which the UE is configured), the UE is configured with a sleep BWP.
[0750] In some examples, the UE is configured to receive DCI in the second cell, where the DCI may schedule the second cell (e.g., self-scheduling) and / or the first cell (e.g., cross-carrier scheduling and / or cross-cell scheduling). The DCI may be UE-specific and / or in a UE-specific search space. Alternatively and / or in addition, the DCI may be associated with a UE-specific search space in the first cell or the second cell.
[0751] In some instances, the UE camps on the NR system and / or accesses the NR system via the first cell.
[0752] In some instances, the UE receives an SSB in a first cell for accessing the NR system (e.g., in idle mode).
[0753] In some examples, the UE enters the connected mode from the idle mode by accessing the first cell.
[0754] In some examples, in a first cell, the UE receives common control information (eg, group common control information and / or cell common control information), such as common DCI, and / or control information (eg, DCI) in a common search space.
[0755] In some instances, in the first cell, the UE only receives common control information (eg, group common control information and / or cell common control information), such as common DCI, and / or control information (eg, DCI) in a common search space.
[0756] In some examples, the UE does not receive UE-specific control information (eg, UE-specific DCI) in the first cell, and the UE does not receive control information (eg, DCI) in a UE-specific search space in the first cell.
[0757] In some examples, the first cell is a PSCell or a PCell.
[0758] In some examples, the second cell is a SCell.
[0759] In some instances, the second cell is not a PSCell.
[0760] In some examples, the first cell and the second cell are in the same cell group (eg, the first cell and the second cell are in an MCG, or the first cell and the second cell are in an SCG).
[0761] In some examples, the size and / or number of bits of the one or more bit fields used to indicate the dormancy information may not be based on whether the first cell schedules the second cell or the second cell schedules the first cell.
[0762] In some instances, the size and / or number of bits of one or more bit fields used to indicate sleep information in the context of the second cell scheduling the first cell is the same as the size and / or number of bits of one or more bit fields used to indicate sleep information in the context of the first cell scheduling the second cell.
[0763] In some instances, cross-cell scheduling and / or cross-carrier scheduling may imply and / or mean that the scheduling control information and / or control channel is in a first cell and / or first carrier that is different from a second cell and / or second carrier associated with scheduled data (e.g., scheduled data scheduled for a second cell and / or second carrier via the scheduling control information and / or control channel).
[0764] In some instances, self-scheduling may imply and / or mean that the scheduling control information and / or control channel is in the same cell and / or the same carrier as the scheduled data (e.g., scheduled data scheduled for the same cell and / or the same carrier via the scheduling control information and / or control channel).
[0765] One, some and / or all of the aforementioned techniques and / or embodiments may be formed into new embodiments.
[0766] In some examples, the embodiments disclosed herein may be implemented independently and / or individually, such as the embodiments described with respect to Embodiment 1, Embodiment 2, and Embodiment 3. Alternatively and / or additionally, the embodiments described herein may be implemented, such as a combination of the embodiments described with respect to Embodiment 1, Embodiment 2, and / or Embodiment 3. Alternatively and / or additionally, the embodiments described herein may be implemented in parallel and / or simultaneously, such as a combination of the embodiments described with respect to Embodiment 1, Embodiment 2, and / or Embodiment 3.
[0767] The various techniques, embodiments, methods and / or alternatives of the present disclosure may be performed independently and / or separately from each other. Alternatively and / or in addition, the various techniques, embodiments, methods and / or alternatives of the present disclosure may be combined and / or implemented using a single system. Alternatively and / or in addition, the various techniques, embodiments, methods and / or alternatives of the present disclosure may be implemented in parallel and / or simultaneously.
[0768] Fig. 9900 is a flowchart according to an exemplary embodiment from the perspective of a UE. In step 905, the UE is configured with one or more cells (e.g., one or more serving cells) including a second cell. In an example, the UE is configured with the one or more cells via receiving a configuration and / or indication of the one or more cells from a network. In step 910, the UE is configured to receive a DCI for scheduling data in a first cell in the second cell. For example, the second cell may schedule (e.g., cross-carrier scheduling and / or cross-cell scheduling) the first cell. In an example, the UE is configured to schedule (e.g., cross-carrier scheduling and / or cross-cell scheduling) the first cell using the second cell via receiving (e.g., from a network) a configuration and / or indication that the second cell schedules (e.g., cross-carrier scheduling and / or cross-cell scheduling) the first cell. In step 915, the UE receives a first DCI having a first DCI format in the second cell, wherein the first DCI and / or the first DCI format indicates sleep information of a subset of one or more cells in the first cell group (e.g., one or more configured cells with which the UE is configured). In an example, the one or more cells include a subset of the one or more cells. In an example, a subset of one or more cells is the same as the one or more cells. The sleep information is indicated by using (e.g., re-deploying) one or more bit fields in the DCI format to indicate the sleep information. The one or more bit fields include one or more bits indicating the sleep state of a subset of one or more cells. Each bit of the one or more bit fields is associated with a cell in the subset of one or more cells. For example, each bit of the one or more bit fields may indicate the sleep state of a cell in the subset of one or more cells. The subset of one or more cells does not include the first cell and does not include the second cell. In an example, the subset of one or more cells indicated by the sleep state by the sleep information and / or the one or more bit fields includes cells other than the first cell and the second cell in the first cell group (e.g., the subset of one or more cells may include all cells other than the first cell and the second cell in the first cell group). For example, the sleep information and / or the one or more bit fields do not indicate the sleep state of the first cell and do not indicate the sleep state of the second cell. The sleep information and / or the one or more bit fields indicate the sleep state of one or more third cells in the subset of one or more cells. In step 920, after receiving the DCI and / or in response to receiving the DCI, for each of the one or more third cells, the UE switches the active BWP of the cell (e.g., active downlink and / or uplink BWP) to the sleep BWP of the cell. In an example, the UE may switch the active BWP of a cell in the one or more third cells to the sleep BWP of the cell based on the sleep information and / or one or more bit fields indicating the sleep state of the cell.
[0769] In one embodiment, the association (between one or more bits of the one or more bit fields and a subset of one or more cells excluding the first cell and the second cell) corresponds to a one-to-one mapping (e.g., a strictly one-to-one mapping), e.g., where one bit of the one or more bit fields is associated with one of the one or more configured cells (e.g., indicating a dormant state of the configured cell). The association is in ascending order of SCell index (e.g., starting from the MSB or LSB of the one or more bit fields).
[0770] In one embodiment, one or more bit fields in the DCI format do not include bits and / or bit positions associated with (and / or indicating) the sleep state of the second cell (e.g., bits and / or bit positions associated with (and / or indicating) the sleep state of the second cell do not exist in one or more bit fields in the DCI format).
[0771] In one embodiment, for each cell except the first cell (eg, each serving cell with which the UE is configured), the UE is configured with a sleep BWP.
[0772] In one embodiment, for each cell other than the first cell and the second cell (eg, each serving cell with which the UE is configured), the UE is configured with a sleep BWP.
[0773] In one embodiment, the UE is configured to receive DCI in the second cell, wherein the DCI may schedule the second cell (e.g., self-scheduling) and / or the first cell (e.g., cross-carrier scheduling and / or cross-cell scheduling). The DCI may be UE-specific and / or in a UE-specific search space. Alternatively and / or in addition, the DCI may be associated with a UE-specific search space in the first cell or the second cell.
[0774] In one embodiment, the UE camps on the NR system and / or accesses the NR system via the first cell.
[0775] In one embodiment, the UE receives an SSB for accessing the NR system (e.g., in idle mode) in a first cell.
[0776] In one embodiment, the UE enters the connected mode from the idle mode via accessing the first cell.
[0777] In one embodiment, in the first cell, the UE only receives common control information (eg, group common control information and / or cell common control information), such as common DCI, and / or control information (eg, DCI) in a common search space.
[0778] In one embodiment, the UE does not receive UE-specific control information (eg, UE-specific DCI) in the first cell, and the UE does not receive control information (eg, DCI) in a UE-specific search space in the first cell.
[0779] In one embodiment, the first cell is a PSCell or a PCell.
[0780] In one embodiment, the second cell is a SCell.
[0781] In one embodiment, the second cell is not a PSCell.
[0782] In one embodiment, the first cell and the second cell are in the same cell group (eg, the first cell group).
[0783] In one embodiment, the size and / or number of bits of the one or more bit fields for indicating the dormancy information may be based on whether the first cell schedules the second cell or the second cell schedules the first cell.
[0784] In one embodiment, in the context of the second cell scheduling the first cell, the one or more bit fields for indicating the sleep information have a first size and / or a first bit number. In the context of the first cell scheduling the second cell, the one or more bit fields for indicating the sleep information have a second size and / or a second bit number. The first size and / or the first bit number may be less than and / or smaller than the second size and / or the second bit number.
[0785] In one embodiment, the size and / or number of bits of the one or more bit fields for indicating the dormancy information may not be based on whether the first cell schedules the second cell or the second cell schedules the first cell.
[0786] In one embodiment, the size and / or number of bits of one or more bit fields used to indicate sleep information in the context of the second cell scheduling the first cell are the same as the size and / or number of bits of one or more bit fields used to indicate sleep information in the context of the first cell scheduling the second cell.
[0787] In one embodiment, in a scenario where the second cell schedules the first cell, the UE uses the first bit of the one or more bit fields that is equivalent to the number of the first bits (eg, the UE uses the first bit to determine the sleep information).
[0788] In one embodiment, in a scenario where the first cell schedules the second cell, the UE uses a second bit of the one or more bit fields that is equivalent to a second number of bits (eg, the UE uses the second bit to determine the sleep information).
[0789] In one embodiment, the first number of bits is less than the second number of bits, and / or the first number of bits does not include a bit (e.g., one bit) associated with the second cell, and / or the first number of bits does not include a bit (e.g., one bit) indicating a dormant state of the second cell.
[0790] In one embodiment, the second bit includes a bit (eg, one bit) associated with the second cell, and / or the second bit includes a bit (eg, one bit) indicating a dormant state of the second cell.
[0791] Return to reference Figure 3 and 4 In an exemplary embodiment of the UE, the apparatus 300 includes a program code 312 stored in the memory 310. The CPU 308 can execute the program code 312 to enable the UE to: (i) be configured with one or more cells (e.g., one or more serving cells) including a second cell, (ii) be configured to receive, in the second cell, a DCI for scheduling data in the first cell, (iii) receive, in the second cell, a first DCI having a first DCI format, wherein the first DCI and / or the first DCI format indicates sleep information of a subset of one or more cells in the first cell group (e.g., one or more configured cells with which the UE is configured), wherein the sleep information is indicated by using (e.g., re-deployment) one or more bit fields in the DCI format, to indicate sleep information, wherein each bit of the one or more bit fields may indicate a sleep state of a cell in a subset of the one or more cells, wherein the sleep information and / or the one or more bit fields indicate a sleep state of one or more third cells in the subset of the one or more cells, and wherein the sleep information and / or the one or more bit fields do not indicate a sleep state of the first cell and do not indicate a sleep state of the second cell, and (iv) after receiving the DCI and / or in response to receiving the DCI, for each of the one or more third cells, switching the active BWP of the cell (e.g., an active downlink and / or uplink BWP) to a sleep BWP of the cell. In addition, the CPU 308 may execute the program code 312 to perform one, some, and / or all of the above actions and steps and / or other actions and steps described herein.
[0792] Fig.101000 is a flowchart according to an exemplary embodiment from the perspective of a first network. In step 1005, the first network configures the UE to include one or more cells (e.g., one or more serving cells) of a second cell. In step 1010, the first network configures the UE to receive DCI for scheduling data in the first cell in the second cell. The first network is not configured to transmit (e.g., not allow the first network to transmit and / or prohibit the first network from transmitting and / or prevent the first network from transmitting) a DCI indicating a sleep state of the second cell to the UE. In step 1015, the first network transmits a first DCI indicating sleep information associated with one or more cells. The first DCI and / or the sleep information indicates a sleep state of a subset of one or more cells, wherein the subset of one or more cells does not include the second cell. In step 1020, after transmitting the first DCI and / or receiving a HARQ-ACK associated with the first DCI and / or in response to transmitting the first DCI and / or receiving a HARQ-ACK associated with the first DCI, the first network does not transmit DCI on and / or for a subset of one or more cells.
[0793] In one embodiment, the sleep information is indicated by one or more bit fields in the DCI and / or the DCI format of the DCI. One or more bit fields may be redeployed for a sleep indication (e.g., indicating sleep information). For example, sleep information may be indicated by redeploying one or more bit fields for an SCell sleep indication. For example, one or more bit fields may include a bit field for indicating other information other than sleep information in other transmissions of a DCI format corresponding to the DCI format. One or more bit fields include one or more bits associated with a subset of one or more cells (e.g., indicating the sleep state of a subset of the one or more cells). One or more cells may include a subset of one or more cells. A subset of one or more cells is in a cell group (e.g., belonging to a first network). A subset of one or more cells does not include the first cell. A subset of one or more cells may include a second cell. Each bit of the one or more bit fields is associated with a cell in a subset of one or more cells (e.g., indicating the sleep state of the cell).
[0794] In one embodiment, the association (between one or more bits of the one or more bit fields and a subset of one or more cells that may include the second cell and exclude the first cell) corresponds to a one-to-one mapping (e.g., a strictly one-to-one mapping), for example, where one bit of the one or more bit fields is associated with one of the one or more configured cells (e.g., indicating a dormant state of the configured cell). The association is in ascending order of the SCell index (e.g., starting from the MSB or LSB of the one or more bit fields).
[0795] In one embodiment, for each cell except the first cell (eg, each serving cell with which the UE is configured), the first network may configure the UE sleep BWP.
[0796] In one embodiment, for each cell other than the first cell and the second cell (eg, each serving cell with which the UE is configured), the first network may configure the UE sleep BWP.
[0797] In one embodiment, the first network does not configure a sleeping BWP of the second cell for scheduling (e.g., cross-cell scheduling and / or cross-carrier scheduling) the first cell (e.g., does not allow the first network to configure and / or prohibits the first network to configure and / or prevents the first network from configuring).
[0798] In one embodiment, the first network does not configure the second cell for scheduling (e.g., cross-cell scheduling and / or cross-carrier scheduling) the configured sleep BWP of the first cell (e.g., does not allow the first network to configure and / or prohibits the first network from configuring and / or prevents the first network from configuring).
[0799] In one embodiment, the first network is not configured to indicate (e.g., not allowing the first network to indicate and / or prohibiting the first network to indicate and / or preventing the first network to indicate) a configured sleep BWP for scheduling (e.g., cross-cell scheduling and / or cross-carrier scheduling) the first cell to the second cell.
[0800] In one embodiment, the first network configures the UE to receive DCI in the second cell, wherein the DCI may schedule the second cell (e.g., self-scheduling) and / or the first cell (e.g., cross-carrier scheduling and / or cross-cell scheduling). The DCI may be UE-specific and / or in a UE-specific search space. Alternatively and / or in addition, the DCI may be associated with a UE-specific search space in the first cell or the second cell.
[0801] In one embodiment, in the first cell, for one or more UEs including the UE, the first network only transmits common control information (e.g., group common control information and / or cell common control information), such as common DCI, and / or control information in a common search space (e.g., DCI).
[0802] In one embodiment, in the first cell, for one or more UEs including the UE, the first network does not transmit UE-specific control information (e.g., UE-specific DCI), nor does it transmit control information (e.g., DCI) in a UE-specific search space in the first cell.
[0803] In one embodiment, the first cell is a PSCell or a PCell (eg, in view of a UE).
[0804] In one embodiment, the second cell is a SCell (eg, in view of a UE).
[0805] In one embodiment, the second cell is not a PSCell (eg, in view of the UE).
[0806] In one embodiment, the first network may configure the UE to communicate with the second network.
[0807] In one embodiment, the first network controls cells in the MCG.
[0808] In one embodiment, the second network controls cells in the SCG.
[0809] In one embodiment, the second cell is configured by the first network.
[0810] In one embodiment, the UE communicates with a first network and a second network (eg, via dual connectivity (DC)).
[0811] In one embodiment, the first cell and the second cell are in the same cell group (eg, the first cell and the second cell are in an MCG, or the first cell and the second cell are in an SCG).
[0812] Return to reference Figure 3 and 4 In an exemplary embodiment of the first network, the apparatus 300 includes a program code 312 stored in the memory 310. The CPU 308 can execute the program code 312 to enable the first network to: (i) configure the UE to include one or more cells (e.g., one or more serving cells) of the second cell, (ii) configure the UE to receive DCI for scheduling data in the first cell in the second cell, wherein the first network is not configured to transmit (e.g., not allow the first network to transmit and / or prohibit the first network from transmitting and / or prevent the first network from transmitting) DCI indicating the sleep state of the second cell to the UE, (iii) transmit a first DCI indicating sleep information associated with one or more cells, wherein the first DCI and / or the sleep information indicates the sleep state of a subset of the one or more cells, and wherein the subset of the one or more cells does not include the second cell, and (iv) after transmitting the first DCI and / or receiving the HARQ-ACK associated with the first DCI and / or in response to transmitting the first DCI and / or receiving the HARQ-ACK associated with the first DCI, not transmit the DCI on and / or for the subset of the one or more cells. Furthermore, CPU 308 may execute program code 312 to perform one, some, and / or all of the actions and steps described above and / or other actions and steps described herein.
[0813] Fig.11 1100 is a flowchart according to an exemplary embodiment from the perspective of a UE. The UE is configured with one or more cells (e.g., one or more serving cells) including a second cell. The UE is configured to monitor one or more first UE-specific PDCCHs on the second cell. The one or more first UE-specific PDCCHs schedule a first data transmission on the first cell. The one or more first UE-specific PDCCHs may correspond to one or more PDCCHs for the UE (e.g., one or more PDCCHs only for the UE and / or not for other UEs) and / or one or more PDCCHs for which the UE is the intended recipient (e.g., one or more PDCCHs for which only the UE is the intended recipient). In step 1105, the UE receives a DCI indicating sleep information associated with one or more cells, wherein the DCI indicates a sleep state of the second cell. In step 1110, in response to the DCI indicating the sleep state of the second cell, the UE switches the scheduling cell of the first cell from the second cell to the first cell, and monitors one or more second UE-specific PDCCHs on the first cell, wherein the one or more second UE-specific PDCCHs schedule a second data transmission on the first cell. For example, the scheduling cell of the first cell may correspond to a cell that schedules data transmission of the first cell. Prior to receiving the DCI indicating the sleep state of the second cell, the scheduling cell of the first cell corresponds to the second cell (e.g., due to the UE being configured to monitor one or more first UE-specific PDCCHs on the second cell, wherein the one or more first UE-specific PDCCHs schedule the first data transmission on the first cell). The UE may switch the scheduling cell of the first cell from the second cell to the first cell based on the DCI indicating the sleep state of the second cell.
[0814] In one embodiment, in response to the DCI indicating a sleep state of the second cell, the UE monitors on the first cell, the UE does not monitor the PDCCH (e.g., any PDCCH) on the second cell and / or the UE switches the active downlink and / or uplink BWP of the second cell to the sleep BWP of the second cell. In some instances, when the UE is in the sleep BWP of the second cell, the UE does not monitor the PDCCH (e.g., any PDCCH) on the second cell.
[0815] In one embodiment, in response to the DCI indicating the sleep state of the second cell, the UE switches from cross-cell scheduling and / or cross-carrier scheduling for scheduling the first cell to self-cell scheduling and / or self-carrier scheduling for scheduling the first cell. For example, for the first cell, the UE switches from cross-cell scheduling and / or cross-carrier scheduling to self-cell scheduling and / or self-carrier scheduling. For example, the UE switches from scheduling the first cell via cross-cell scheduling and / or cross-carrier scheduling to scheduling the first cell via self-cell scheduling and / or self-carrier scheduling.
[0816] In one embodiment, the DCI schedules data transmission (eg, of a UE).
[0817] In one embodiment, the DCI does not schedule (eg, UE's) data transmission.
[0818] In one embodiment, one or more cells are in the same cell group.
[0819] In one embodiment, the first cell is a PCell and the second cell is a SCell.
[0820] In one embodiment, when the UE is in the sleep BWP of the second cell, the UE skips monitoring the sleep BWP for the second cell and / or the PDCCH on the sleep BWP.
[0821] In one embodiment, after receiving a DCI indicating a sleep state of a second cell, the UE is in a sleep BWP of the second cell based on the DCI indicating the sleep state of the second cell, wherein when the UE is in the sleep BWP of the second cell, the UE skips monitoring the PDCCH on the sleep BWP of the second cell.
[0822] In one embodiment, when the UE is in a non-sleep BWP of the second cell, the UE does not monitor the UE-specific PDCCH in the first cell, nor does it monitor the PDCCH in the UE-specific search space in the first cell. For example, based on the UE being configured to monitor one or more first UE-specific PDCCHs on the second cell, the UE may not monitor the UE-specific PDCCH in the first cell, nor the PDCCH in the UE-specific search space in the first cell, wherein the one or more first UE-specific PDCCHs schedule the first data transmission on the first cell (and / or the scheduling cell of the first cell is the second cell before receiving the DCI indicating the sleep state of the second cell). The UE-specific search space may correspond to a search space configured for the UE (e.g., a search space configured to be used only for the UE and / or not configured for other UEs).
[0823] In one embodiment, before receiving a DCI indicating a sleep state of the second cell, the UE is in a non-sleep BWP of the second cell, wherein when the UE is in the non-sleep BWP of the second cell, the UE does not monitor a UE-specific PDCCH in the first cell, nor does it monitor a PDCCH in a UE-specific search space in the first cell. For example, based on the UE being configured to monitor one or more first UE-specific PDCCHs on the second cell, the UE may not monitor a UE-specific PDCCH in the first cell, nor may it monitor a PDCCH in a UE-specific search space in the first cell, wherein the one or more first UE-specific PDCCHs schedule a first data transmission on the first cell (and / or based on the scheduling cell of the first cell being the second cell before receiving a DCI indicating a sleep state of the second cell).
[0824] In one embodiment, the UE receives the DCI on the first cell or on the second cell.
[0825] Return to reference Figure 3 and 4 In an exemplary embodiment of the UE, the apparatus 300 includes a program code 312 stored in the memory 310. The UE is configured with one or more cells (e.g., one or more serving cells) including a second cell. The UE is configured to monitor one or more first UE-specific PDCCHs on the second cell. The one or more first UE-specific PDCCHs schedule a first data transmission on the first cell. The CPU 308 may execute the program code 312 to enable the UE to: (i) receive a DCI indicating sleep information associated with one or more cells, wherein the DCI indicates a sleep state of the second cell, and (ii) in response to the DCI indicating a sleep state of the second cell, switch the scheduling cell of the first cell from the second cell to the first cell and monitor one or more second UE-specific PDCCHs on the first cell, wherein the one or more second UE-specific PDCCHs schedule a second data transmission on the first cell. In addition, the CPU 308 may execute the program code 312 to perform one, some, and / or all of the above actions and steps and / or other actions and steps described herein.
[0826] Fig.121200 is a flowchart according to an exemplary embodiment from the perspective of a first network. In step 1205, the first network configures the UE to include one or more cells (e.g., one or more serving cells) of a second cell. In step 1210, the first network configures the UE to monitor one or more PDCCHs on the second cell, wherein the one or more PDCCHs schedule data transmission on the first cell. In step 1215, the first network transmits a first DCI indicating sleep information associated with the one or more cells. The first DCI indicates a sleep state of a third cell in the one or more cells. The first network is not configured to provide (e.g., not allow the first network to provide and / or prohibit the first network from providing and / or prevent the first network from providing) an indication corresponding to the sleep state of the second cell via the first DCI. For example, the first network is not configured to schedule (e.g., cross-cell scheduling and / or cross-carrier scheduling) the first cell based on the second cell via the first DCI indication (e.g., not allow the first network to indicate and / or prohibit the first network from indicating and / or prevent the first network from indicating) the sleep state of the second cell. For example, when the second cell schedules (e.g., cross-carrier scheduling and / or cross-cell scheduling) the first cell (and / or when the UE is configured to monitor one or more PDCCHs on the second cell, wherein the one or more PDCCHs schedule data transmission on the first cell), the first network may not be configured to transmit (e.g., not allow the first network to transmit and / or prohibit the first network from transmitting and / or prevent the first network from transmitting) DCI (e.g., any DCI) indicating the sleep state of the second cell to the UE. In step 1220, after transmitting the first DCI and / or receiving the HARQ-ACK associated with the first DCI and / or in response to transmitting the first DCI and / or receiving the HARQ-ACK associated with the first DCI, the first network does not transmit the second DCI on and / or for the third cell. The HARQ-ACK may correspond to an indication that the UE received (e.g., successfully received) the first DCI. In some instances, the UE may switch from an active downlink and / or uplink BWP of the third cell to a sleep BWP of the third cell. When the UE is in the sleeping BWP of the third cell, the first network may not transmit the second DCI (and / or any DCI) to the UE on and / or for the third cell.
[0827] In one embodiment, one or more bit fields in the first DCI (e.g., one or more bit fields in the DCI format of the first DCI) indicate sleep information. Each bit of the one or more bit fields is associated with a cell (e.g., a configured cell) in the first cell group of the one or more cells (e.g., indicating a sleep state of the cell). In some examples, for each cell in the one or more cells, the one or more bit fields indicate the sleep state of the cell.
[0828] In one embodiment, the first network indicates the sleep information by redistributing one or more bit fields in the first DCI (e.g., one or more bit fields in the DCI format of the first DCI) to indicate the sleep information. For example, the one or more bit fields may include bit fields for indicating other types of information other than the sleep information in other transmissions of the DCI. Each bit of the one or more bit fields is associated with a cell (e.g., a configured cell) in the first cell group of the one or more cells (e.g., indicating the sleep state of the cell). In some instances, for each cell in the one or more cells, the one or more bit fields indicate the sleep state of the cell.
[0829] In one embodiment, the one or more bit fields include one or more bits associated with one or more cells. The one or more cells do not include the first cell. The one or more associations between the one or more bits and the one or more cells correspond to a one-to-one mapping and are based on an ascending order of one or more SCell indices associated with the one or more cells.
[0830] In one embodiment, the first network does not configure the sleep BWP of the second cell of the UE (eg, does not allow the first network to configure and / or prohibits the first network to configure and / or prevents the first network from configuring).
[0831] In one embodiment, the first network does not configure a configured sleeping BWP of the second cell for scheduling (e.g., cross-cell scheduling and / or cross-carrier scheduling) the first cell (e.g., does not allow the first network to configure and / or prohibits the first network to configure and / or prevents the first network from configuring).
[0832] In one embodiment, the first network is not configured to indicate (e.g., not allowing the first network to indicate and / or prohibiting the first network to indicate and / or preventing the first network to indicate) a configured sleep BWP for scheduling (e.g., cross-cell scheduling and / or cross-carrier scheduling) the first cell to the second cell.
[0833] In one embodiment, one or more PDCCHs are UE-specific.
[0834] In one embodiment, one or more PDCCHs are UE-specific search spaces.
[0835] In one embodiment, the one or more PDCCHs are associated with a UE-specific search space in the second cell.
[0836] In one embodiment, on the first cell, the first network does not transmit UE-specific control information (e.g., UE-specific DCI) to the UE, nor does it transmit control information (e.g., DCI) in a UE-specific search space to the UE. The UE-specific control information may correspond to control information (e.g., DCI) for the UE (e.g., control information only for the UE and / or not for other UEs), and / or control information (e.g., DCI) for which the UE is the intended recipient (e.g., control information for which only the UE is the intended recipient).
[0837] In one embodiment, when the second cell schedules (e.g., cross-carrier scheduling and / or cross-cell scheduling) the first cell (and / or when the UE is configured to monitor one or more PDCCHs on the second cell, where the one or more PDCCHs schedule data transmission on the first cell), the first network does not transmit UE-specific control information (e.g., UE-specific DCI) to the UE on the first cell, nor does it transmit control information (e.g., DCI) in a UE-specific search space to the UE.
[0838] In one embodiment, one or more cells are in the same cell group.
[0839] In one embodiment, the first cell is a PCell and the second cell is a SCell.
[0840] Return to reference Figure 3 and 4 In an exemplary embodiment of the first network, the apparatus 300 includes program code 312 stored in the memory 310. The CPU 308 can execute the program code 312 to enable the first network to (i) configure the UE to include one or more cells (e.g., one or more serving cells) of the second cell, (ii) configure the UE to monitor one or more PDCCHs on the second cell, wherein the one or more PDCCHs schedule data transmission on the first cell, (iii) transmit a first DCI indicating sleep information associated with the one or more cells, wherein the first DCI indicates a sleep state of a third cell in the one or more cells, and wherein the first network is not configured to provide (e.g., not allow the first network to provide and / or prohibit the first network from providing and / or prevent the first network from providing) an indication corresponding to the sleep state of the second cell via the first DCI, and (iv) after transmitting the first DCI and / or receiving the HARQ-ACK associated with the first DCI and / or in response to transmitting the first DCI and / or receiving the HARQ-ACK associated with the first DCI, not transmit the second DCI on and / or for the third cell. Furthermore, CPU 308 may execute program code 312 to perform one, some, and / or all of the actions and steps described above and / or other actions and steps described herein.
[0841] Fig.13 1300 is a flowchart according to an exemplary embodiment from the perspective of a UE. The UE is configured with one or more cells (e.g., one or more serving cells) including a second cell. The UE is configured to monitor one or more first UE-specific PDCCHs on the second cell. The one or more first UE-specific PDCCHs schedule a first data transmission on the first cell. In step 1305, the UE receives a DCI indicating sleep information associated with one or more cells, wherein the DCI indicates a sleep state of the second cell. In step 1310, if the DCI indicates a sleep state of the second cell, then in response to the DCI indicating the sleep state of the second cell, the UE switches the scheduling cell of the first cell from the second cell to the first cell, and the UE monitors one or more second UE-specific PDCCHs on the first cell, wherein the one or more second UE-specific PDCCHs schedule data transmission on the first cell. If the DCI indicates a non-sleep state of the second cell, then in response to the DCI indicating a non-sleep state of the second cell, the UE monitors one or more first UE-specific PDCCHs on the second cell.
[0842] Return to reference Figure 3 and 4 In an exemplary embodiment of the UE, the device 300 includes a program code 312 stored in the memory 310. The UE is configured with one or more cells (e.g., one or more serving cells) including a second cell. The UE is configured to monitor one or more first UE-specific PDCCHs on the second cell. The one or more first UE-specific PDCCHs schedule a first data transmission on the first cell. The CPU 308 can execute the program code 312 to enable the UE to (i) receive a DCI indicating sleep information associated with one or more cells, wherein the DCI indicates a sleep state of the second cell, and one of the following: (ii) if the DCI indicates a sleep state of the second cell, then in response to the DCI indicating the sleep state of the second cell, the UE switches the scheduling cell of the first cell from the second cell to the first cell, and the UE monitors one or more second UE-specific PDCCHs on the first cell, wherein the one or more second UE-specific PDCCHs schedule data transmission on the first cell, or (iii) if the DCI indicates a non-sleep state of the second cell, then in response to the DCI indicating the non-sleep state of the second cell, the UE monitors one or more first UE-specific PDCCHs on the second cell. Furthermore, CPU 308 may execute program code 312 to perform one, some, and / or all of the actions and steps described above and / or other actions and steps described herein.
[0843] A communication device (e.g., UE, network, base station, network node, etc.) may be provided, wherein the communication device may include a control circuit, a processor installed in the control circuit, and / or a memory installed in the control circuit and coupled to the processor. The processor may be configured to execute a program code stored in the memory to perform Figures 9 to 13 In addition, the processor may execute program code to perform one, some, and / or all of the above actions and steps and / or other actions and steps described herein.
[0844] A computer-readable medium may be provided. The computer-readable medium may be a non-transitory computer-readable medium. The computer-readable medium may include a flash memory device, a hard drive, a disk (e.g., a magnetic disk and / or an optical disk, such as at least one of a digital versatile disk (DVD), a compact disk (CD), etc.), and / or a memory semiconductor, such as at least one of a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), etc. The computer-readable medium may include processor-executable instructions that, when executed, cause execution of the processor-executable instructions. Figures 9 to 13 One, some and / or all of the method steps shown in and / or one, some and / or all of the actions and steps described above and / or other actions and steps described herein.
[0845] It can be appreciated that applying one or more of the techniques presented herein can produce one or more benefits, including but not limited to improved communication efficiency and service continuity improvements between devices (e.g., UEs and / or network nodes), such as in a scenario where a UE configured with an SCell schedules a PCell or a PSCell. The improved efficiency and / or improved service continuity can be the result of using one or more of the techniques herein to avoid a situation where the UE does not have and / or cannot receive UE-specific control signaling for scheduling a PCell or a PSCell. For example, using one or more of the techniques herein, if the SCell schedules a PCell or a PSCell, the UE may not switch to the sleep BWP of the SCell. Alternatively and / or in addition, using one or more of the techniques herein, if the UE switches to the sleep BWP of the SCell, the UE may switch the scheduling cell of the PCell or the PSCell from the SCell to the PCell or the PSCell (e.g., without RRC signaling), which may enable the UE to receive UE-specific control signaling for scheduling the PCell or the PSCell. However, in some systems, the UE may switch to the sleep BWP of the SCell to schedule the PCell or PSCell without switching the scheduling cell of the PCell or PSCell, which may cause the UE to be unable to receive UE-specific control signaling for scheduling the PCell or PSCell and / or may cause service interruption and / or communication delays.
[0846] Various aspects of the present disclosure have been described above. It should be understood that the teachings herein can be implemented in a variety of forms, and any specific structure, function, or both disclosed herein are only representative. Based on the teachings herein, it should be understood by those skilled in the art that the aspects disclosed herein can be implemented independently of any other aspects, and two or more of these aspects can be combined in various ways. For example, any number of aspects described herein can be used to implement a device or practice method. In addition, other structures, functions, or structures and functions other than one or more of the aspects described herein or different from one or more of the aspects described herein can be used to implement this device or practice this method. As an example of some of the above concepts, in some aspects, parallel channels can be established based on pulse repetition frequencies. In some aspects, parallel channels can be established based on pulse positions or offsets. In some aspects, parallel channels can be established based on time hopping sequences. In some aspects, parallel channels can be established based on pulse repetition frequencies, pulse positions or offsets, and time hopping sequences.
[0847] Those skilled in the art will understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
[0848] Those skilled in the art will further appreciate that the various illustrative logical blocks, modules, processors, components, circuits, and algorithm steps described in conjunction with the aspects disclosed herein may be implemented as electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of both, which may be designed using source decoding or some other technique), various forms of program or design code incorporating instructions (which may be referred to herein for convenience as "software" or "software modules"), or a combination of the two. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether this functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in different ways for each specific application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.
[0849] In addition, the various illustrative logical blocks, modules, and circuits described in conjunction with the aspects disclosed herein may be implemented within or performed by an integrated circuit ("IC"), an access terminal, or an access point. The IC may include a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, electrical components, optical components, mechanical components, or any combination thereof designed to perform the functions described herein, and may execute code or instructions residing within the IC, outside the IC, or both. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
[0850] It should be understood that any specific order or hierarchy of steps in any disclosed process is an example of a sample approach. Based on design preferences, it should be understood that the specific order or hierarchy of steps in a process can be rearranged while remaining within the scope of the present disclosure. The accompanying method claims present elements of the various steps in an example order, and are not meant to be limited to the specific order or hierarchy presented.
[0851] The steps of the method or algorithm described in conjunction with the aspects disclosed herein may be implemented directly in hardware, in software modules executed by a processor, or in a combination of the two. Software modules (e.g., containing executable instructions and associated data) and other data may reside in a data memory, such as a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or any other form of computer-readable storage medium known in the art. A sample storage medium may be coupled to a machine such as a computer / processor (for convenience, the machine may be referred to herein as a "processor") so that the processor may read information (e.g., code) from the storage medium and write information to the storage medium. A sample storage medium may be integrated with a processor. The processor and storage medium may reside in an ASIC. The ASIC may reside in a user device. In an alternative, the processor and storage medium may reside in a user device as discrete components. Alternatively and / or in addition, in some aspects any suitable computer program product may include a computer-readable medium, which includes code related to one or more of the aspects of the present disclosure. In some aspects, a computer program product may include packaging materials.
[0852] Although the disclosed subject matter has been described in conjunction with various aspects, it will be appreciated that the disclosed subject matter is capable of further modification. This application is intended to cover any changes, uses, or adaptations of the disclosed subject matter that generally follow the principles of the disclosed subject matter, including deviations from the disclosure that fall within known and customary practices in the field to which the disclosed subject matter relates.
Claims
1. A method for a user equipment, characterized in that: The user equipment is configured with one or more cells including a second cell, wherein the user equipment is configured to monitor one or more first user equipment-specific physical downlink control channels on the second cell, and wherein the one or more first user equipment-specific physical downlink control channels schedule data transmission on the first cell, the method comprising: Prior to receiving downlink control information indicating dormancy information associated with the one or more cells and the downlink control information indicating a dormancy state of the second cell: monitoring a cell common physical downlink control channel on said first cell; and not monitoring one or more second user equipment-specific physical downlink control channels on the first cell; receiving the downlink control information indicating dormancy information associated with the one or more cells, wherein the downlink control information indicates a dormancy state of the second cell; and In response to the downlink control information indicating the sleep state of the second cell, monitoring the one or more second user equipment-specific physical downlink control channels on the first cell, wherein the one or more second user equipment-specific physical downlink control channels schedule data transmission on the first cell.
2. The method according to claim 1, characterized in that include: In response to the downlink control information indicating the sleep state of the second cell, performing at least one of the following: not monitoring a physical downlink control channel on the second cell; or An active bandwidth portion of the second cell is switched to a sleep bandwidth portion of the second cell, wherein the active bandwidth portion is at least one of a downlink or an uplink.
3. The method according to claim 1, characterized in that include: In response to the downlink control information indicating the sleep state of the second cell, switching from cross-cell scheduling or cross-carrier scheduling for scheduling the first cell to self-cell scheduling or self-carrier scheduling for scheduling the first cell.
4. The method according to claim 1, characterized in that: The downlink control information schedules data transmission.
5. The method according to claim 1, characterized in that: The downlink control information does not schedule data transmission.
6. The method according to claim 1, characterized in that: The one or more cells are in the same cell group.
7. The method according to claim 1, characterized in that: The first cell is a primary cell and the second cell is a secondary cell.
8. The method according to claim 1, characterized in that After receiving the downlink control information indicating the sleep state of the second cell, based on the downlink control information indicating the sleep state of the second cell, the user equipment is in a sleep bandwidth part of the second cell, the method comprising: When the user equipment is in the sleep bandwidth portion of the second cell, monitoring a physical downlink control channel on the sleep bandwidth portion of the second cell is skipped.
9. The method according to claim 1, characterized in that: Receiving the downlink control information is on the first cell or on the second cell.
10. A user equipment, characterized in that: The user equipment is configured with one or more cells including a second cell, wherein the user equipment is configured to monitor one or more first user equipment-specific physical downlink control channels on the second cell, and wherein the one or more first user equipment-specific physical downlink control channels schedule data transmission on the first cell, the user equipment comprising: Control circuit; A processor installed in the control circuit; and a memory installed in the control circuit and operably coupled to the processor, wherein the processor is configured to execute program code stored in the memory to perform operations including: Prior to receiving downlink control information indicating dormancy information associated with the one or more cells and the downlink control information indicating a dormancy state of the second cell: monitoring a cell common physical downlink control channel on said first cell; and not monitoring one or more second user equipment-specific physical downlink control channels on the first cell; receiving downlink control information indicating dormancy information associated with the one or more cells; and One of the following: If the downlink control information indicates a sleep state of the second cell, then in response to the downlink control information indicating the sleep state of the second cell, monitoring the one or more second user equipment-specific physical downlink control channels on the first cell, wherein the one or more second user equipment-specific physical downlink control channels schedule data transmission on the first cell; or If the downlink control information indicates a non-sleeping state of the second cell, then in response to the downlink control information indicating the non-sleeping state of the second cell, monitoring the one or more first user equipment-specific physical downlink control channels on the second cell.
