CN112788717A - Terminal energy saving method and device corresponding to secondary cell and computer readable medium - Google Patents

Abstract

In an aspect of the invention, a method, computer-readable medium, and apparatus are provided. The apparatus may be a UE. The UE receives a dormant BWP configuration indicating a first BWP on which the UE operates in dormant behavior, the first BWP being a first SCell established between the UE and a base station. On a PCell established between a UE and a base station, the UE receives a first indication to indicate a transition to operate in a dormant behavior. In accordance with the first indication, the UE operates in a dormant behavior on the first BWP.

Description

Terminal energy saving method and device corresponding to secondary cell and computer readable medium

Cross-referencing

The present invention claims priority as follows: us provisional patent application No. 62/932,577 filed on 8/11/2019 entitled "EFFICIENT AND LOW LATENCY SCELL DATA transport semiconductor FOR NR CA" and us patent application No. 17/069,002 filed on 13/10/2020, which are hereby incorporated by reference.

Technical Field

The present invention relates generally to communication systems, and more particularly, to techniques for operating a secondary cell (SCell) at a User Equipment (UE).

Background

The statements in this section merely provide background information related to the present disclosure and may not constitute prior art.

Wireless communication systems may be widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasting. A typical wireless communication system may employ multiple-access (multiple-access) techniques that are capable of supporting communication with multiple users by sharing the available system resources. Examples of such Multiple Access techniques include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, single-carrier Frequency Division Multiple Access (SC-FDMA) systems, and time Division synchronous Code Division Multiple Access (TD-SCDMA) systems.

These multiple access techniques have been applied in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at the city level, the country level, the region level, and even the global level. One example telecommunications standard is the fifth generation (5G) New Radio (NR). The 5G NR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3 GPP), and can meet new requirements related to latency, reliability, security, scalability (e.g., Internet of things (IoT)), and other requirements. Some aspects of 5G NR may be based on the fourth Generation (4th Generation, 4G) Long Term Evolution (LTE) standard. Further improvements are needed in the 5G NR technology. These improvements may also be applicable to other multiple access techniques and telecommunications standards employing these techniques.

Disclosure of Invention

The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

In an aspect of the invention, a method, computer-readable medium, and apparatus are provided. The apparatus may be a UE. The UE receives a sleep (dormant) BWP configuration indicating a first bandwidth part (BWP) on which the UE operates in a sleep behavior, the first BWP being a first secondary cell (SCell) established between the UE and a base station. On a primary cell (PCell) established between a UE and a base station, the UE receives a first indication for indicating a transition to operate in a dormant behavior. In accordance with the first indication, the UE operates in a dormant behavior on the first BWP.

The terminal energy-saving method corresponding to the SCell provided by the invention can save the electric energy of the UE by configuring the UE to switch between the dormant behavior and the non-dormant behavior.

To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The embodiments and figures describe in detail certain illustrative features of one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed and the described description is intended to include all such aspects and their equivalents.

Drawings

Fig. 1 is a schematic diagram illustrating an example of a wireless communication system and an access network.

Fig. 2 illustrates a schematic diagram of a base station communicating with a UE in an access network.

Fig. 3 illustrates an example logical structure of a distributed access network.

Fig. 4 illustrates an example physical structure of a distributed access network.

Fig. 5 is a diagram showing an example of a Downlink (DL) -centered subframe.

Fig. 6 is a diagram illustrating an example of a subframe centered on an Uplink (UL).

Fig. 7 is a diagram illustrating communication between a base station and a UE.

Fig. 8 is a schematic diagram illustrating a UE transitioning between operating in a non-dormant behavior and operating in a dormant behavior.

Fig. 9 is a flowchart of a method (process) of operating on an SCell.

FIG. 10 is a conceptual data flow diagram illustrating the data flow between different components/instrumentalities in an exemplary device.

Fig. 11 is a schematic diagram illustrating an example of a hardware implementation for an apparatus employing a processing system.

Detailed Description

The embodiments set forth below in connection with the appended drawings are intended as a description of various configurations and are not intended to represent the only configurations in which the concepts described herein may be implemented. The present embodiments include specific details for the purpose of providing a thorough understanding of various concepts. It will be apparent, however, to one skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

Several aspects of a telecommunications system will now be presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to herein as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

By way of example, an element, or any portion of an element, or any combination of elements, may be implemented as a "processing system" that includes one or more processors. Examples of processors include microprocessors, microcontrollers, Graphics Processing Units (GPUs), Central Processing Units (CPUs), application processors, Digital Signal Processors (DSPs), Reduced Instruction Set Computing (RISC) processors, system on a chip (SoC), baseband processors, Field Programmable Gate Arrays (FPGAs), Programmable Logic Devices (PLDs), state machines, gating logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions of all aspects of the invention. One or more processors in the processing system may execute software. Software is to be construed broadly as instructions, instruction sets, code segments, program code, programs, subroutines, software components, applications, software packages, routines, subroutines, objects, executables, threads of execution, programs, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

Thus, in one or more example embodiments, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium. Computer readable media includes computer storage media. A storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, computer-readable media may comprise random-access memory (RAM), read-only memory (ROM), Electrically Erasable Programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, and combinations of the above computer-readable media types, or any other medium that may be used to store computer-executable code in the form of computer-accessible instructions or data structures.

Fig. 1 is a schematic diagram illustrating an example of a wireless communication system and an access network 100. A wireless communication system, which may also be referred to as a Wireless Wide Area Network (WWAN), includes a base station 102, a UE104, and an Evolved Packet Core (EPC) 160. The base station 102 includes a macro cell (high power cellular base station) and/or a small cell (small cell) (low power cellular base station). The macro cell includes a base station. Small cells include femto cells (femtocells), pico cells (picocells), and micro cells (microcells).

The base stations 102 (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) terrestrial radio access network (E-UTRAN)) are connected to the EPC160 via backhaul links 132 (e.g., S1 interfaces). Base station 102 may perform, among other functions, one or more of the following functions: user data delivery, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, Radio Access Network (RAN) sharing, Multimedia Broadcast Multicast Service (MBMS), user (subscriber) and device tracking, RAN Information Management (RIM), paging, positioning, and warning messaging. The base stations 102 may communicate with each other directly or indirectly (e.g., through the EPC 160) through a backhaul link 134 (e.g., an X2 interface). The backhaul link 134 may be wired or wireless.

The base station 102 may communicate wirelessly with the UE 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102 ' may have a coverage area 110 ', the coverage area 110 ' overlapping with the coverage area 110 of one or more macro base stations 102. A network that includes both small cells and macro cells may be referred to as a heterogeneous network. The heterogeneous network may also include home evolved node bs (henbs), which may provide services to a restricted group called a Closed Subscriber Group (CSG). The communication link 120 between the base station 102 and the UE104 may include UL (also may be referred to as reverse link) transmissions from the UE104 to the base station 102 and/or DL (also may be referred to as forward link) transmissions from the base station 102 to the UE 104. Communication link 120 may use Multiple-Input Multiple-Output (MIMO) antenna techniques including spatial multiplexing, beamforming, and/or transmit diversity. The communication link may be through one or more carriers. The base station 102/UE 104 may use a spectrum of up to Y megahertz (e.g., 5, 10, 15, 20, 100 megahertz) bandwidth per carrier, where the spectrum is allocated in a carrier aggregation of up to Yx megahertz (x component carriers) for transmission in each direction. The carriers may or may not be adjacent to each other. The allocation of carriers for DL and UL may be asymmetric (e.g., more or fewer carriers may be allocated for DL than for UL). The component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a PCell and the secondary component carrier may be referred to as an SCell.

The wireless communication system further includes a wireless fidelity (Wi-Fi) Access Point (AP) 150 that communicates with a Wi-Fi Station (STA) 152 via a communication link 154 in a 5 gigahertz unlicensed spectrum. When communicating in the unlicensed spectrum, the STA 152/AP 150 may perform a Clear Channel Assessment (CCA) prior to communicating to determine whether the channel is available.

The small cell 102' may operate in licensed and/or unlicensed spectrum. When operating in unlicensed spectrum, small cell 102' may employ NR and use the same 5 gigahertz unlicensed spectrum as Wi-Fi AP 150. Small cells 102' employing NR in unlicensed spectrum may improve coverage and/or increase capacity of the access network.

The next generation Node B (gNB) 180 may operate at a millimeter wave (mmW) frequency and/or a near mmW frequency to communicate with the UE 104. When gNB 180 operates at mmW or near mmW frequencies, gNB 180 may be referred to as a mmW base station. An Extremely High Frequency (EHF) is a portion of the Radio Frequency (RF) spectrum of the electromagnetic spectrum. The EHF has a range of 30 gigahertz to 300 gigahertz and a wavelength between 1 millimeter and 10 millimeters. The radio waves in the frequency band may be referred to as millimeter waves. Near mmW may extend down to 3 gigahertz frequencies with a wavelength of 100 millimeters. The ultra high frequency (SHF) band ranges from 3 gigahertz to 30 gigahertz, also known as centimeter waves. Communications using the mmW/near mmW RF band have extremely high path loss and short range. Beamforming 184 may be used between the gNB 180 and the UE104 to compensate for extremely high path loss and short range.

The EPC160 includes a Mobility Management Entity (MME) 162, other MMEs 164, a serving gateway (serving gateway)166, a MBMS Gateway (GW) 168, a broadcast multicast service center (BM-SC) 170, and a Packet Data Network (PDN) gateway 172. The MME 162 may communicate with a Home Subscriber Server (HSS) 174. MME 162 is a control node that handles signaling between UE104 and EPC 160. Generally, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are passed through the serving gateway 166, which serving gateway 166 itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation and other functions. The PDN gateway 172 and BM-SC 170 are connected to the PDN 176. The PDN 176 may include the internet, an intranet, an IP Multimedia Subsystem (IMS), a packet-switched streaming service (PSS), and/or other IP services. The BM-SC 170 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 170 may be used as an entry point for content provider MBMS transmissions, may be used to authorize and initiate MBMS bearer services in a Public Land Mobile Network (PLMN), and may be used to schedule MBMS transmissions. The MBMS GW 168 may be used to allocate an MBMS service (traffic) to base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a specific service, and is responsible for session management (start/stop) and collection of evolved MBMS (eMBMS) -related payment information.

A base station may also be referred to as a gbb, a Node B (Node B), an evolved Node B (eNB), an AP, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a Basic Service Set (BSS), an Extended Service Set (ESS), or other suitable terminology. Base station 102 provides an AP to EPC160 for UE 104. Examples of UEs 104 include a mobile phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a Personal Digital Assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, an automobile, an electricity meter, a gas pump, an oven, or any other similarly functioning device. Some UEs 104 may also be referred to as IoT devices (e.g., parking timers, gas pumps, ovens, automobiles, etc.). UE104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, or other suitable terminology.

Fig. 2 is a block diagram illustrating a base station 210 in an access network communicating with a UE 250. In the DL, IP packets from EPC160 may be provided to controller/processor 275. The controller/processor 275 performs layer 3 and layer 2 functions. Layer 3 includes a Radio Resource Control (RRC) layer, and layer 2 includes a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, and a Medium Access Control (MAC) layer. The controller/processor 275 provides RRC layer functions associated with system information (e.g., Master Information Block (MIB), System Information Block (SIB)) broadcasts, RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting; wherein PDCP layer functions are associated with header compression/decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; wherein the RLC layer functions are associated with delivery of upper layer Packet Data Units (PDUs), error correction by automatic repeat request (ARQ), concatenation, segmentation and reassembly of RLC Service Data Units (SDUs), re-segmentation of RLC data PDUs and re-ordering of RLC data PDUs; wherein the MAC layer functions are associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs into Transport Blocks (TBs), demultiplexing of TBs into MAC SDUs, scheduling information reporting, error correction by hybrid automatic repeat request (HARQ), prioritization, and logical channel priority.

A Transmit (TX) processor 216 and a Receive (RX) processor 270 implement layer 1 functions associated with various signal processing functions. Layer 1 (including the Physical (PHY) layer) may include error detection on transport channels, Forward Error Correction (FEC) encoding/decoding of transport channels, interleaving (interleaving), rate matching, mapping on physical channels, modulation/demodulation of physical channels, and MIMO antenna processing. TX processor 216 processes a mapping to a signal constellation (constellation) based on various modulation schemes, such as binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM). The encoded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to Orthogonal Frequency Division Multiplexing (OFDM) subcarriers, multiplexed with reference signals (e.g., pilots) in the time and/or Frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to generate a physical channel carrying a time-domain OFDM symbol stream. The OFDM streams are spatially precoded to produce a plurality of spatial streams. The channel estimates from channel estimator 274 may be used to determine the coding and modulation schemes, as well as for spatial processing. The channel estimates may be derived from reference signals and/or channel state feedback transmitted by the UE 250. Each spatial stream may then be provided to a different antenna 220 via a separate transceiver 218 (transceiver 218 including RX and TX). Each transceiver 218 may modulate an RF carrier with a respective spatial stream for transmission.

At the UE250, each transceiver 254 (transceiver 254 includes RX and TX) receives signals through its respective antenna 252. Each transceiver 254 recovers information modulated onto an RF carrier and provides the information to an RX processor 256. The TX processor 268 and the RX processor 256 implement layer 1 functions associated with various signal processing functions. RX processor 256 may perform spatial processing on the information to recover any spatial streams to be transmitted to UE 250. If there are multiple spatial streams to send to the UE250, the RX processor 256 combines the multiple spatial streams into a single OFDM symbol stream. The RX processor 256 then transforms the OFDM symbol stream from the time-domain to the frequency-domain using a Fast Fourier Transform (FFT). The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the most likely signal constellation transmitted by the base station 210. These soft decisions may be based on channel estimates computed by the channel estimator 258. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 210 on the physical channel. The data and control signals are then provided to a controller/processor 259, which performs layer 3 and layer 2 functions.

Controller/processor 259 may be associated with a memory 260 that stores program codes and data. Memory 260 may be referred to as a computer-readable medium. In the UL, the controller/processor 259 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression and control signal processing to recover IP packets from the EPC 160. The controller/processor 259 is also responsible for error detection using an Acknowledgement (ACK) and/or Negative Acknowledgement (NACK) protocol to support HARQ operations.

Similar to the functional description of DL transmissions by the base station 210, the controller/processor 259 provides RRC layer functions, PDCP layer functions, RLC layer functions, and MAC layer functions, wherein the RRC layer functions are associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functions are associated with header compression/decompression, and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functions are associated with delivery of upper layer PDUs, error correction by ARQ, concatenation, segmentation and reassembly of RLC SDUs, and reordering of RLC data PDUs; the MAC layer function is associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs to TBs, demultiplexing of TBs to MAC SDUs, scheduling information reporting, error correction by HARQ, priority handling, and logical channel priority.

The channel estimates derived by channel estimator 258, which may be derived from a reference signal or feedback transmitted by base station 210, may be used by TX processor 268 to select the appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by TX processor 268 may be provided to different antennas 252 via separate transceivers 254. Each transceiver 254 may modulate an RF carrier with a respective spatial stream for transmission. The base station 210 processes the UL transmissions in a manner similar to that described for the receiver function at the UE 250. Each transceiver 218 receives signals through a respective antenna 220. Each transceiver 218 recovers information modulated onto an RF carrier and provides the information to RX processor 270.

The controller/processor 275 can be associated with a memory 276 that stores program codes and data. Memory 276 may be referred to as a computer-readable medium. In the UL, the controller/processor 275 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from the UE 250. IP packets from the controller/processor 275 may be provided to the EPC 160. The controller/processor 275 is also responsible for error detection using ACK and/or NACK protocols to support HARQ operations.

NR refers to a radio configured to operate according to a new air interface (e.g., in addition to an OFDMA-based air interface) or a fixed transport layer (e.g., other than IP)). NR may use OFDM with Cyclic Prefix (CP) in UL and DL and includes support for half duplex operation using Time Division Duplex (TDD). NR may include enhanced mobile broadband (eMBB) service for wide bandwidths (e.g., over 80 mhz), mmW for high carrier frequencies (e.g., 60 ghz), a large number of MTC (MTC) for non-backward compatible Machine Type Communication (MTC) technologies, and/or critical tasks for Ultra-Reliable Low delay Communication (URLLC) service.

A single component carrier with a bandwidth of 100 mhz may be supported. In one example, an NR Resource Block (RB) may span 12 subcarriers having a bandwidth of 60 khz and a duration of 0.125 msec, or a bandwidth of 15 khz and a duration of 0.5 msec. Each radio frame may include 20 or 80 subframes (or NR slots) having a length of 10 msec. Each subframe may indicate a link direction (i.e., DL or UL) for data transmission, and the link direction of each subframe may be dynamically switched. Each subframe may include DL/UL data as well as DL/UL control data. The UL and DL subframes of the NR may be described in detail in fig. 5 and 6 below.

The NR RAN may include a Central Unit (CU) and a Distributed Unit (DU). An NR Base Station (BS) (e.g., a gNB, a 5G Node B, a Transmission Reception Point (TRP), an AP) may correspond to one or more BSs. The NR cell may be configured as an access cell (ACell) or a data only cell (DCell). For example, the RAN (e.g., CU or DU) may configure a cell. The DCell may be a cell for carrier aggregation or dual connectivity and is not used for initial access, cell selection/reselection, or handover. In some cases, Dcell does not send a Synchronization Signal (SS). In some cases, the DCell transmits the SS. The NR BS may transmit a DL signal indicating a cell type to the UE. Based on the cell type indication, the UE may communicate with the NR BS. For example, the UE may determine an NR BS based on the indicated cell type to consider for cell selection, access, handover, and/or measurement.

Fig. 3 illustrates an example logical structure of a distributed RAN300 in accordance with aspects of the present invention. 5G access node 306 includes an Access Node Controller (ANC) 302. ANC may be a CU of the distributed RAN 300. The backhaul interface to the next generation core network (NG-CN) 304 may terminate at the ANC. The backhaul interface to the neighboring next generation access node (NG-AN) may terminate at the ANC. An ANC includes one or more TRPs 308 (also may be referred to as a BS, NR BS, Node B, 5G NB, AP, or some other terminology). As described above, TRP may be used interchangeably with "cell".

TRP 308 may be a DU. The TRP may be connected to one ANC (ANC 302) or more than one ANC (not shown). For example, for RAN sharing, radio as a service (RaaS), and service specific ANC deployments, a TRP may be connected to more than one ANC. The TRP includes one or more antenna ports. The TRP may be configured to serve traffic to the UE independently (e.g., dynamic selection) or jointly (e.g., joint transmission).

The local structure of the distributed RAN300 can be used to describe the fronthaul (frontaul) definition. A structure supporting a fronthaul solution across different deployment types may be defined. For example, the structure may be based on the transmission network performance (e.g., bandwidth, delay, and/or jitter). The structure may share features and/or components with LTE. According to various aspects, the NG-AN 310 may support dual connectivity with NRs. The NG-ANs may share the common fronthaul of LTE and NR.

The structure may enable cooperation between TRPs 308. For example, collaboration may be pre-set within the TRP and/or across the TRP via ANC 302. According to various aspects, the interface between TRPs may not be needed/present.

According to various aspects, dynamic configuration of the split logical functions may exist within the distributed RAN300 architecture. PDCP, RLC, MAC protocols may be placed adaptively in ANC or TRP.

Fig. 4 illustrates an example physical structure of a distributed RAN 400 in accordance with aspects of the present invention. A centralized core network unit (C-CU) 402 may assume core network functions. The C-CU can be deployed centrally. The C-CU function may be removed (e.g., removed to Advanced Wireless Service (AWS)) to handle peak capacity. A centralized RAN unit (C-RU) 404 may assume one or more ANC functions. Alternatively, the C-RU may assume the core network functions locally. The C-RUs may be deployed in a distributed manner. The C-RU may be closer to the network edge. DU 406 may assume one or more TRPs. The DUs may be located at the edge of the network with RF functionality.

Fig. 5 is a diagram 500 illustrating an example of a DL-centric subframe. The DL-centric subframe includes a control portion 502. The control portion 502 may exist at an initial or beginning portion of a subframe centered on the DL. The control section 502 includes various scheduling information and/or control information corresponding to portions of a subframe centered on DL. In some configurations, the control portion 502 may be a Physical DL Control Channel (PDCCH), as shown in fig. 5. The DL-centric subframe also includes a DL data portion 504. The DL data portion 504 is sometimes referred to as the payload of a DL-centric subframe. The DL data portion 504 includes communication resources for communicating from a scheduling entity (e.g., a UE or BS) to a subordinate entity (e.g., a UE). In some configurations, the DL data portion 504 may be a Physical DL Shared Channel (PDSCH).

The DL-centric sub-frame also includes a general UL section 506. Generic UL portion 506 is sometimes referred to as a UL burst, a generic UL burst, and/or various other suitable terms. The generic UL portion 506 includes feedback information corresponding to various other portions of the DL-centric sub-frame. For example, generic UL portion 506 includes feedback information corresponding to control portion 502. Non-limiting examples of feedback information include ACK signals, NACK signals, HARQ indications, and/or various other suitable types of information. The generic UL portion 506 includes additional or alternative information such as information related to Random Access Channel (RACH) procedures, Scheduling Requests (SRs), and various other suitable types of information.

As shown in fig. 5, the end of the DL data portion 504 may be separated in time from the beginning of the generic UL portion 506. The temporal separation may sometimes be referred to as a gap (gap), guard period (guard period), guard interval (guard interval), and/or other suitable terminology. The separation provides time for a handover from DL communication (e.g., a receive operation of a subordinate entity (e.g., a UE)) to UL communication (e.g., a transmission of a subordinate entity (e.g., a UE)). Those skilled in the art will appreciate that the above is merely an example of a DL-centric subframe, and that there may be alternative structures with similar features without necessarily offsetting the aspects described herein.

Fig. 6 is a diagram 600 illustrating an example of a UL-centric subframe. The UL-centric sub-frame includes a control portion 602. The control portion 602 may exist at an initial or beginning portion of a UL-centric sub-frame. The control portion 602 of fig. 6 may be similar to the control portion 502 described with reference to fig. 5. The UL-centric sub-frame also includes a UL data portion 604. The UL data portion 604 may sometimes be referred to as the payload of a UL-centric sub-frame. The UL section may refer to communication resources for communicating from a subordinate entity (e.g., a UE) to a scheduling entity (e.g., a UE or a BS). In some configurations, the control portion 602 may be a PDCCH.

As shown in fig. 6, the end of the control portion 602 may be separated in time from the beginning of the generic UL data portion 604. The temporal separation may sometimes be referred to as an interval, a guard period, a guard interval, and/or other suitable terminology. The separation provides time for a handover from DL communication (e.g., a receive operation of a scheduling entity) to UL communication (e.g., a transmission of the scheduling entity). The UL centric sub-frame also includes a general UL portion 606. The generic UL portion 606 of fig. 6 may be similar to the generic UL portion 606 described with reference to fig. 6. The general UL section 606 may additionally or additionally include information regarding Channel Quality Indicators (CQIs), Sounding Reference Signals (SRSs), and various other suitable types of information. Those skilled in the art will appreciate that the above is merely an example of a DL-centric subframe, and that there may be alternative structures with similar features without necessarily offsetting the aspects described herein.

In some cases, two or more subordinate entities (e.g., UEs) may communicate with each other using sidelink (sidelink) signals. Practical applications of such sidelink communications include public safety, proximity services, UE-To-network relay, Vehicle-To-Vehicle (V2V) communications, Internet of Everything (IoE) communications, IoT communications, mission-critical mesh (mission-critical mesh), and/or various other suitable applications. Generally, a sidelink signal may refer to a signal for communication from one subordinate entity (e.g., UE 1) to another subordinate entity (e.g., UE 2) without relaying the communication through a scheduling entity (e.g., UE or BS), even though the scheduling entity may be used for scheduling and/or control purposes. In some examples, sidelink signals may communicate using licensed spectrum (as opposed to wireless local area networks that typically use unlicensed spectrum).

In the present invention, in "3 GPP TS 38.212V15.7.0 (2019-09); technical Specification; 3rd Generation Partnership Project; technical Specification Group Radio Access Network; NR; one or more terms or features are defined or described in Physical layer procedures for control (Release 15) "(3 GPP TS 38.213), and are known to those skilled in the art.

Fig. 7 is a diagram 700 illustrating a base station 702 and a UE704 communicating. The base station 702 and the UE704 establish multiple component carriers between them. In this example, the UE704 and the base station 702 establish 7 component carriers 772-0 to 772-6. Further, the base station 702 may configure the primary component carrier 772-0 as the primary component carrier and the secondary component carriers 772-1 through 772-6 as the secondary component carriers. The primary component carrier may also be referred to as PCell and the secondary component carrier may also be referred to as SCell.

In some configurations, base station 702 may divide the Secondary component carriers into different Secondary Cell Groups (SCGs). In this example, the secondary component carriers 772-1 to 772-6 are split into 3 SCGs 776-0 to 776-2. More specifically, SCG 776-0 includes secondary component carrier 772-1; SCG 776-1 includes secondary component carrier 772-1 and secondary component carrier 772-3; SCG 776-2 includes secondary component carrier 772-4, secondary component carrier 772-5, and secondary component carrier 772-6.

In certain configurations, the UE704 may determine the best grouping of the secondary component carriers 772-1 to 772-6. For example, the grouping may be decided based on whether certain scells share the same RF chain. As such, the UE704 may determine that the secondary component carriers 772-1 to 772-3 should be in one SCG and that the secondary component carriers 772-4 to 772-6 should be in another SCG. In view of base station 702, UE704 may send an indication to base station 702 to group as such.

Further, in some configurations, the UE704 may implement a Discontinuous Reception (DRX) mechanism. The basic mechanism of DRX is a configurable DRX cycle in the UE 704. The DRX cycle is configured with an ON (ON) duration and an OFF (OFF) duration, and the device monitors downlink control signaling only when active (e.g., for the ON duration) and sleeps for the remainder of the time that the processing circuitry is OFF (e.g., for the OFF duration). This allows a significant reduction in power consumption: the longer the period, the lower the power consumption. Naturally, this implies a limitation of the scheduler, since the device can only be addressed when it is active according to the DRX cycle.

In this example, the UE704 activates the DRX mechanism and operates according to DRX cycles 720-1, 720-2 … 720-N. Fig. 7 shows that the DRX cycles 720-1, 720-2 … 720-N are on the primary component carrier 772-0, and these DRX cycles 720-1, 720-2 … 720-N are equally applicable to the secondary component carriers 772-1 to 772-6. Each DRX cycle includes an on duration and an off duration. For example, DRX cycle 720-1 includes an on duration 722-1 and an off duration 726-1. Alternatively, DRX cycle 720-2 includes an on duration 722-2, a duration due to starting of the inactivity timer 728-2, and so on.

Further, the base station 702 may send a wake-up signal in a set of resource elements at a configured location prior to a corresponding DRX cycle of the UE704 to indicate whether there is data directed (addressed) to the UE704 to send for an on duration of the corresponding DRX cycle. For example, the base station 702 sends a wake-up signal 710-1 to the UE704 before the DRX cycle 720-1 to inform the UE704 to send data directed to the UE704 for the on-duration 722-1. When the UE704 does not detect the wake-up signal 710-1 corresponding to the on-duration 722-1, the UE704 may assume that no data directed to the UE704 is transmitted for the on-duration 722-1. Accordingly, the UE704 may refrain from monitoring (selecting not to monitor) the PDCCH for the on-duration 722-1. In this way, the UE704 may save power when PDCCH detection in the on-duration is not needed.

Further, in some configurations, the wake-up signal is located in a resource element that is a predetermined duration (e.g., a number of OFDM symbols, slots, or milliseconds) before the on-duration of the DRX cycle, the wake-up signal including an indication of traffic.

The secondary component carriers 772-1 and 772-6 may be activated or deactivated. When there is less data to transmit to the UE, base station 702 may deactivate the already activated SCell to reduce power consumption of the UE. Activation and deactivation may be accomplished by a MAC Control Element (CE).

Further, the UE704 may operate in a non-dormant behavior or in a dormant behavior when the SCell is in an active state. The UE704 may transition between the two behaviors. When operating in a non-dormant behavior, the UE704 may perform Channel State Information (CSI) measurement, Automatic Gain Control (AGC), and beam management, and monitor the PDCCH, etc. When the UE704 operates in the sleep behavior, the UE704 does not monitor the PDCCH to reduce power consumption; the UE704 still performs CSI measurement, AGC, and beam management.

A particular BWP may be set at the UE704 by setting a particular value for a particular combination of BWP parameters. In this example, the base station 702 may configure a respective particular BWP on each active SCell of the secondary component carriers 772-1 to 772-6 on which the UE704 operates in a dormant behavior. Such a specific BWP is called a dormant BWP. Base station 702 may configure values for a set of BWP parameters for dormant BWP, based on which values UE704 does not monitor PDCCH but still performs periodic CSI measurements and reports to maintain downlink channel quality.

Fig. 8 is a diagram 800 illustrating a transition of a UE704 between operating in non-dormant behavior and dormant behavior on a secondary component carrier 772-1. Similar switching may occur on other secondary component carriers 772-1 to 772-6.

The base station 702 may send a corresponding BWP Identification (ID) to the UE704 to identify the corresponding dormant BWP for each active SCell of the secondary component carriers 772-1 to 772-6. The BWP ID (or other indication) may be carried in an RRC IE (e.g., Scell-BWP-ID-with-downlink) sent from base station 702 to UE 704. In other words, through the base station 702, the network may explicitly configure a dormant BWP associated with one BWP ID via RRC, and may explicitly indicate the dormant BWP in the serving cell configuration. In the example of secondary component carrier 772-1, dormant one dormant BWP812 and one or more non-dormant BWPs 814 may be configured on secondary component carrier 772-1. Base station 702 may transmit a bitmap corresponding to a series of BWPs configured for secondary component carrier 772-1. Bit 0 in the bitmap indicates that the corresponding BWP (e.g., dormant BWP812) is a dormant BWP. Bit 1 in the bitmap indicates that the corresponding BWP (e.g., non-dormant BWP814) is a non-dormant BWP.

UE704 may receive sleep transition indication 822 from base station 702, and sleep transition indication 822 may indicate that UE704 switches from non-sleeping BWP814 to sleeping BWP812 on secondary component carrier 772-1. After switching to dormant BWP812, the UE704 may operate in dormant behavior on the secondary component carrier. In particular, the UE704 does not monitor (or attempt to decode) the PDCCH sent on the secondary component carrier 772-1. However, the UE704 may detect for CSI-RS 738 sent on secondary component carrier 772-1 (as shown in fig. 7) and perform periodic or semi-persistent CSI measurements on CSI-RS 738. The UE704 also generates a CSI report based on the CSI measurements. The UE704 may send the CSI report to the base station 702 on the primary component carrier 772-0.

Further, UE704 may receive non-dormant transition indication 824, and non-dormant transition indication 824 may indicate that UE704 switches from dormant BWP812 to non-dormant BWP814 on secondary component carrier 772-1. Multiple non-dormant BWPs 814 are configured on secondary component carrier 772-1. Base station 702 may send a BWP ID identifying a default non-dormant BWP 814. For example, a default non-dormant BWP814 may be configured on secondary component carrier 772-1 during link setup via RRC IEs designated to indicate the default non-dormant BWP 814. The designated RRC IE is different from the firstActictiveDownlinkBWP-Id defined in 3GPP TS 38.213. Thus, upon receiving non-dormant transition indication 824, UE704 may switch from operating on dormant BWP812 to operating on default non-dormant BWP 814.

As described above with reference to fig. 7, the UE704 may operate according to a DRX cycle. In some configurations, base station 702 may configure one default non-sleeping BWP814 for the active time and another non-sleeping BWP different from non-sleeping BWP814 for the off-active time. To configure the active time on secondary component carrier 772-1, base station 702 may send a corresponding special bitmap via an RRC message to allocate a corresponding non-dormant BWP for either inside or outside the active time. Each respective bitmap corresponds to a configured BWP on secondary component carrier 772-1. Bit "1" indicates that the corresponding non-hibernating BWP is designated as the default non-hibernating BWP. Bit "0" indicates that the corresponding non-hibernating BWP is not designated as the default non-hibernating BWP.

Further, when the UE704 is in an off duration (outside of the active time) before the DRX cycle 720-1, the base station 702 may send a non-sleep transition indication 824 or a sleep transition indication 822 in the wake signal 710-1 on the primary component carrier 772-0, thereby indicating that the UE704 is operating in the sleep BWP812 or the non-sleep BWP814 after waking up for the on duration 722-1. The non-sleep transition indication 824 and the sleep transition indication 822 may be included in Downlink Control Information (DCI) carried by the wake-up signal 710-1. When UE704 is within the active time of DRX cycle 720-1, base station 702 may send non-dormant transition indication 824 or dormant transition indication 822 in PDCCH 732-1 (e.g., via DCI) or PDSCH (including MAC CE) on primary component carrier 772-0, thereby instructing UE704 to operate as intended in dormant BWP812 or in non-dormant BWP 814.

In one example, base station 702 sends non-sleep transition indication 824 to UE704 in wake-up signal 710-1 or PDCCH 732-1. After receiving non-dormant transition indication 824, while in on duration 722-1, UE704 may remain operating in non-dormant behavior in the current BWP if UE704 is already operating in non-dormant behavior in non-dormant BWP 814. If UE704 is operating in dormant behavior in dormant BWP812, UE704 switches to non-dormant BWP814 (e.g., default non-dormant BWP814) and begins operating in non-dormant behavior.

In another example, base station 702 sends sleep transition indication 822 to UE704 in wake-up signal 710-1 or PDCCH 732-1. After receiving the non-dormant transition indication 822, while in the on duration 722-1, the UE704 may remain operating in dormant behavior in the current BWP if the UE704 is already operating in dormant behavior in the dormant BWP 812. If UE704 is operating in non-dormant behavior in non-dormant BWP814, UE704 switches to dormant BWP812 and begins operating in dormant behavior.

Fig. 9 is a flow diagram 900 of a method (process) of operating on an SCell. The method may be performed by a UE (e.g., UE704, apparatus 1002, and apparatus 1002').

At operation 902, the UE receives a dormant BWP configuration (e.g., bitmap) indicating a first BWP (e.g., dormant BWP812) on which the UE operates in dormant behavior. The first BWP is located on a first secondary cell (e.g., secondary component carrier 722-1) established between the UE and the base station. In some configurations, the dormant BWP configuration is received via an RRC message. In certain configurations, the UE is configured to operate in non-dormant behavior on each of a plurality of BWPs (e.g., non-dormant BWP 814). At operation 904, the UE receives an non-dormant BWP configuration (e.g., bitmap) indicating a default BWP (e.g., default non-dormant BWP814) of the plurality of BWPs on which to operate in non-dormant behavior. At operation 906, the UE receives a first indication (e.g., a sleep transition indication 822) on a primary cell (e.g., primary component carrier 772-0) established between the UE and the base station to transition to operate in sleep behavior.

At operation 908, the UE operates in a sleep behavior on the first BWP in accordance with the first indication. In certain configurations, the UE makes periodic CSI measurements for the first secondary cell while operating in a dormant behavior on the first BWP. The UE reports CSI of the first secondary cell on another cell (the UE operates in a non-dormant behavior). The UE refrains from monitoring each PDCCH transmitted on the first secondary cell.

At operation 910, the UE receives a second indication on the primary cell to transition to operating in non-dormant behavior on the first secondary cell. At operation 912, the UE transitions to operate in non-dormant behavior on a default BWP (e.g., default non-dormant BWP814) of the first secondary cell in accordance with the second indication.

In some configurations, the UE receives the PDCCH on the primary cell for the active time of the DRX cycle. The first indication is carried in the PDCCH. And performing the operation of the sleep behavior in the active time.

In some configurations, the UE receives a first wake-up signal (e.g., wake-up signal 710-1) on the primary cell prior to an active time of a first DRX cycle (e.g., DRX cycle 720-1). The first indication is carried in the first wake-up signal. The operation of the sleep behavior is performed during the active time of the first DRX cycle. The UE receives a second wake-up signal (e.g., wake-up signal 710-2) on the primary cell prior to an active time of a second DRX cycle (e.g., DRX cycle 720-2). The second wake-up signal carries a second indication for transitioning to operate in a non-sleep behavior. The UE performs an operation of non-sleep behavior during the active time of the second DRX cycle.

In some configurations, a UE establishes a plurality of secondary cells with a base station, the plurality of secondary cells including a first secondary cell. The UE determines to partition one or more groups of secondary cells. Each group includes one or more of the plurality of secondary cells operating together in a dormant behavior or in a non-dormant behavior. The UE sends an indication of the one or more groups to the base station.

FIG. 10 is a conceptual data flow diagram 1000 illustrating the data flow between different components/means in an exemplary apparatus 1002. The apparatus 1002 may be a UE. The apparatus 1002 includes a receiving component 1004, a BWP configuring component 1006, a BWP converting component 1008, and a sending component 1010.

BWP configuring component 1006 receives a dormant BWP configuration (e.g., bitmap) indicating a first BWP (e.g., dormant BWP812) on which the UE is operating in dormant behavior. The first BWP is located on a first secondary cell (e.g., secondary component carrier 722-1) established between the UE and the base station. In some configurations, the dormant BWP configuration is received via an RRC message. In certain configurations, the UE is configured to operate in non-dormant behavior on each of a plurality of BWPs (e.g., non-dormant BWP 814). BWP configuration component 1006 receives a non-dormant BWP configuration (e.g., bitmap) indicating a default BWP of the plurality of BWPs (e.g., default non-dormant BWP814) on which to operate in non-dormant behavior. .

BWP transition component 1008 receives a first indication (e.g., dormant transition indication 822) on a primary cell (e.g., primary component carrier 772-0) established between the UE and base station 1050 to transition to operate in dormant behavior. The UE operates in a sleep behavior on the first BWP in accordance with the first indication. In certain configurations, the UE makes periodic CSI measurements for the first secondary cell while operating in a dormant behavior on the first BWP. The UE reports CSI of the first secondary cell on another cell (the UE operates in a non-dormant behavior). The UE refrains from monitoring each PDCCH transmitted on the first secondary cell.

BWP switching component 1008 receives a second indication on the primary cell to switch to operating in non-dormant behavior on the first secondary cell. BWP configuring component 1006 transitions to operate in non-dormant behavior on a default BWP (e.g., default non-dormant BWP814) of the first secondary cell in accordance with the second indication.

In some configurations, receiving component 1004 receives PDCCH on the primary cell for the active time of the DRX cycle. The first indication is carried in the PDCCH. And performing the operation of the sleep behavior in the active time.

In some configurations, the receiving component 1004 receives a first wake-up signal (e.g., wake-up signal 710-1) on the primary cell prior to an active time of a first DRX cycle (e.g., DRX cycle 720-1). The first indication is carried in the first wake-up signal. The operation of the sleep behavior is performed during the active time of the first DRX cycle. The receiving component 1004 receives a second wake-up signal (e.g., wake-up signal 710-2) on the primary cell prior to an active time of a second DRX cycle (e.g., DRX cycle 720-2). The second wake-up signal carries a second indication for transitioning to operate in a non-sleep behavior. The UE performs an operation of non-sleep behavior during the active time of the second DRX cycle.

In certain configurations, the UE establishes a plurality of secondary cells with the base station 1050, including the first secondary cell. The UE determines to partition one or more groups of secondary cells. Each group includes one or more of the plurality of secondary cells operating together in a dormant behavior or in a non-dormant behavior. The UE sends an indication of the one or more groups to base station 1050.

Fig. 11 is a diagram 1100 illustrating an example of a hardware implementation for an apparatus 1002' employing a processing system 1114. The apparatus 1002' may be a UE. The processing system 1114 may implement a bus (bus) architecture, represented generally by the bus 1124. The bus 1124 includes any number of interconnecting buses and bridges depending on the specific application of the processing system 1114 and the overall design constraints. The bus 1124 links together various circuits including one or more processors and/or hardware components, represented by the one or more processors 1104, the receiving component 1004, the BWP configuring component 1006, the BWP converting component 1008, the sending component 1010, and the computer-readable medium/memory 1106. The bus 1124 may also link various other circuits such as timing sources, peripherals, voltage regulators, power management circuits, and the like.

The processing system 1114 may be coupled with the transceivers 1110, where the transceivers 1110 may be one or more of the transceivers 254. The transceiver 1110 may be coupled with one or more antennas 1120, where the antennas 1120 may be the communication antennas 252.

The transceiver 1110 provides a means for communicating with various other apparatus over a transmission medium. The transceiver 1110 receives signals from the one or more antennas 1120, extracts information from the received signals, and provides the extracted information to the processing system 1114 (and in particular to the receiving component 1004). In addition, the transceiver 1110 receives information from the processing system 1114 (and in particular the transmission component 1010) and generates a signal based on the received information for application to the one or more antennas 1120.

The processing system 1114 includes one or more processors 1104 coupled to a computer-readable medium/memory 1106. The one or more processors 1104 are responsible for overall processing, including the execution of software stored on the computer-readable medium/memory 1106. The software, when executed by the one or more processors 1104, causes the processing system 1114 to perform the various functions of any particular apparatus described above. The computer-readable medium/memory 1106 may also be used for storing data that is manipulated by the one or more processors 1104 when executing software. The processing system 1114 also includes at least one of a receiving component 1004, a BWP configuration component 1006, a BWP conversion component 1008, and a sending component 1010. The components described above may be software components running in one or more processors 1104, resident/stored in a computer readable medium/memory 1106, one or more hardware components coupled to the one or more processors 1104, or a combination thereof. The processing system 1114 may be a component of the UE250 and include the memory 260 and/or at least one of the TX processor 268, the RX processor 256, and the controller/processor 259.

In one configuration, the apparatus 1002/apparatus 1002' for wireless communication includes means for performing each of the operations of fig. 9. The aforementioned means may be one or more components of the processing system 1114 of the apparatus 1002 and/or the apparatus 1002' configured to perform the functions recited by the aforementioned means.

As described supra, the processing system 1114 includes the TX processor 268, the RX processor 256, and the controller/processor 259. Likewise, in one configuration, the above means may be the TX processor 268, the RX processor 256, and the controller/processor 259 configured to perform the functions recited by the above means.

It is to be understood that the specific order or hierarchy of steps in the processes/flow diagrams disclosed are illustrative of exemplary approaches. It should be understood that the specific order or hierarchy of steps in the processes/flow diagrams may be rearranged based on design preferences. In addition, some steps may be further combined or omitted. The accompanying method claims present elements of the various steps in a sample order, and are not meant to limit the invention to the specific order or hierarchy presented.

The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean "one and only one" unless specifically so stated, but rather "one or more. The term "exemplary" is intended to mean "serving as an example, instance, or illustration" in the present disclosure. Any aspect described as "exemplary" is not necessarily preferred or advantageous over other aspects. The term "some" means one or more unless otherwise specified. Combinations such as "A, B or at least one of C", "A, B or one or more of C", "at least one of A, B and C", "one or more of A, B and C", and "A, B, C or any combination thereof" include any combination of A, B and/or C, and may include a plurality of a, B or C. In particular, combinations such as "at least one of A, B or C", "one or more of A, B or C", "at least one of A, B and C", "one or more of A, B and C", and "A, B, C or any combination thereof" may be a only, B only, C, A and B, A and C, B and C or a and B and C, wherein any such combination may include one or more members of A, B or C. All structural and functional equivalents to the elements of the various aspects described in this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Furthermore, nothing disclosed herein is intended to be dedicated to the public regardless of whether the invention is explicitly recited in the claims. The words "module," mechanism, "" component, "" device, "and the like may not be a substitute for the term" means. Thus, unless the phrase "means for …" is used to specifically state an element in a claim, the element should not be construed as a functional limitation.

Claims (17)

1. A terminal energy saving method corresponding to a secondary cell is characterized by comprising the following steps:

receiving, at a user equipment, a dormant bandwidth part configuration indicating a first bandwidth part over which the user equipment operates in dormant behavior, the first bandwidth part being a first secondary cell established between the user equipment and a base station;

receiving a first indication on a primary cell established between the user equipment and the base station to transition to operating in the dormant behavior; and

operating on the first bandwidth portion in the sleep behavior in accordance with the first indication.

2. The method for saving power of a terminal corresponding to a secondary cell in claim 1, further comprising:

when operating in the sleep behavior on the first bandwidth portion:

performing periodic channel state information measurements on the first secondary cell;

reporting channel state information of the first secondary cell on another cell in which the user equipment operates in a non-dormant behavior; and

refraining from monitoring each physical downlink control channel transmitted on the first secondary cell.

3. The terminal power saving method for a secondary cell of claim 1, wherein the dormant bandwidth part configuration is received through a radio resource control message.

4. The method of terminal power saving for a secondary cell of claim 1, wherein the user equipment is configured to operate in non-dormant behavior on each of a plurality of bandwidth parts, the method further comprising:

receiving a non-sleep bandwidth part configuration indicating a default bandwidth part of the plurality of bandwidth parts on which to operate in the non-sleep behavior; and

when operating in the sleep behavior on the first bandwidth portion:

receiving a second indication on the primary cell to transition to operating in the non-dormant behavior on the first secondary cell; and

transitioning to operate in the non-dormant behavior on the default bandwidth portion of the first secondary cell in accordance with the second indication.

5. The method for saving power of a terminal corresponding to a secondary cell in claim 1, further comprising:

receiving a physical downlink control channel on the primary cell for an active time of a discontinuous reception cycle, wherein the first indication is carried in the physical downlink control channel, operating in the dormant behavior for the active time.

6. The method for saving power of a terminal corresponding to a secondary cell in claim 1, further comprising:

receiving a first wake-up signal on the primary cell prior to an active time of a first discontinuous reception cycle, wherein the first indication is carried in the first wake-up signal, operating in the dormant behavior for the active time of the first discontinuous reception cycle.

7. The method for saving power of terminal of secondary cell as claimed in claim 6, further comprising:

receiving a second wake-up signal on the primary cell prior to an active time of a second discontinuous reception cycle, the second wake-up signal carrying a second indication to indicate a transition to operate in non-dormant behavior; and

operating in a non-sleep behavior during the active time of the second discontinuous reception cycle.

8. The method for saving power of a terminal corresponding to a secondary cell in claim 1, further comprising:

establishing a plurality of secondary cells with the base station, the plurality of secondary cells including the first secondary cell;

determining to divide the plurality of secondary cells into one or more groups, each group comprising one or more of the plurality of secondary cells operating together in the dormant behavior or in the non-dormant behavior; and

transmitting an indication of the one or more groups to the base station.

9. An apparatus for wireless communication, for saving power for a terminal corresponding to a secondary cell, the apparatus being a user equipment, comprising:

a memory; and

at least one processor coupled to the memory and configured to:

receiving, at the user equipment, a sleep bandwidth part configuration indicating a first bandwidth part on which the user equipment operates in a sleep behavior, the first bandwidth part being a first secondary cell established between the user equipment and a base station;

receiving a first indication on a primary cell established between the user equipment and the base station to transition to operating in the dormant behavior; and

operating on the first bandwidth portion in the sleep behavior in accordance with the first indication.

10. The apparatus of claim 9, the at least one processor further configured to:

when operating in the sleep behavior on the first bandwidth portion:

performing periodic channel state information measurements on the first secondary cell;

reporting channel state information of the first secondary cell on another cell in which the user equipment operates in a non-dormant behavior; and

refraining from monitoring each physical downlink control channel transmitted on the first secondary cell.

11. The apparatus of claim 9, wherein the dormant bandwidth part configuration is received via a radio resource control message.

12. The apparatus of claim 9, the at least one processor further configured to:

configuring the user equipment to operate in a non-sleep behavior on each of a plurality of bandwidth portions;

receiving a non-dormant bandwidth segment configuration indicating a default bandwidth segment of the plurality of bandwidth segments to transition to operate in the non-dormant behavior; and is

When operating in sleep behavior on the first bandwidth portion:

receiving a second indication on the primary cell to transition to operating in the non-dormant behavior on the first secondary cell; and

transitioning to operate in the non-dormant behavior on the default bandwidth portion of the first secondary cell in accordance with the second indication.

13. The apparatus of claim 9, the at least one processor further configured to:

receiving a physical downlink control channel on the primary cell for an active time of a discontinuous reception cycle, wherein the first indication is carried in the physical downlink control channel, operating in the dormant behavior for the active time.

14. The apparatus of claim 9, the at least one processor further configured to:

receiving a first wake-up signal on the primary cell prior to an active time of a first discontinuous reception cycle, wherein the first indication is carried in the first wake-up signal, operating in the dormant behavior for the active time of the first discontinuous reception cycle.

15. The apparatus of claim 14, the at least one processor further configured to:

receiving a second wake-up signal on the primary cell prior to an active time of a second discontinuous reception cycle, the second wake-up signal carrying a second indication to indicate a transition to operate in non-dormant behavior; and

operating in a non-sleep behavior during the active time of the second discontinuous reception cycle.

16. The apparatus of claim 9, the at least one processor further configured to:

establishing a plurality of secondary cells with the base station, the plurality of secondary cells including the first secondary cell;

determining to divide the plurality of secondary cells into one or more groups, each group comprising one or more of the plurality of secondary cells operating together in the dormant behavior or in the non-dormant behavior; and

transmitting an indication of the one or more groups to the base station.

17. A computer-readable medium storing computer-executable code for a user equipment for wireless communication, wherein the computer-executable code is configured to perform the steps of the terminal power saving method for a corresponding secondary cell of any of claims 1-8.

Images