Methods and apparatus for a generic design to support pdcch skipping and search space set group switching

Abstract

A method performed by a user equipment (UE) is provided. In the method, at least one of a first configuration associated with a first operation of a switching search space set group and a second configuration associated with a second operation of a physical downlink control channel skipping is received. Downlink control information including a particular field associated with at least one of the first configuration or the second configuration is also received. One of the first operation and the second operation is performed based on a value in the particular field.

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit and priority of U.S. Provisional Application Serial No. 63 / 172,558, filed April 8, 2021, entitled “METHOD AND APPARATUS TO SUPPORT COMMON DESIGN FOR PDCCHSKIPPING AND SEARCH SPACE SET SWITCHING”, the contents of which are incorporated herein by reference in their entirety. Technical Field

[0003] This application generally relates to wireless communications, and more particularly to methods for a general design to support physical downlink control channel (PDCCH) skipping and search space trunking group handover, and to user equipment (UE) using the method. Background Technology

[0004] With the massive growth in the number of connected devices and the rapid increase in user / network traffic, various efforts have been made to improve all aspects of next-generation wireless communication systems, such as fifth-generation (5G) New Radio (NR) systems, through efforts to improve data rates, latency, reliability, and mobility.

[0005] 5G NR systems are designed to provide flexibility and configurability to optimize network services and types to adapt to various use cases, such as enhanced mobile broadband (eMBB), massive machine-type communication (mMTC), and ultra-reliable and low-latency communication (URLLC).

[0006] However, with the continued increase in demand for radio access, there is a need to further improve wireless communication in next-generation wireless communication systems. Summary of the Invention

[0007] This application relates to a method for supporting Physical Downlink Control Signal (PDCCH) skipping and Search Space Cluster Group (SSSG) handover, and to a User Equipment (UE) configured to use the method.

[0008] In a first aspect of this application, a method performed by a UE is provided. The method includes: receiving at least one of a first configuration associated with a first operation of a handover search space cluster group (SSSG) and a second configuration associated with a second operation of skipping a physical downlink control channel (PDCCH); receiving downlink control information (DCI), the DCI including a specific field associated with at least one of the first configuration or the second configuration. Additionally, the method further includes: performing the first operation or the second operation based on a value in the specific field.

[0009] In one embodiment of the first aspect, the specific field is a 2-bit field, and the value in the specific field is one of 00, 01, 10, and 11.

[0010] In another embodiment of the first aspect, the specific field indicates at least one of the SSSG index or the PDCCH skip duration.

[0011] In another embodiment of the first aspect, a first portion of the specific field includes first information indicating at least one of the first operation and the second operation, and a second portion of the specific field includes second information indicating the SSSG index or PDCCH skip duration.

[0012] In another embodiment of the first aspect, a first subvalue in a first portion of the specific field indicates the first operation, and a second subvalue in a first portion of the specific field indicates the second operation.

[0013] In another embodiment of the first aspect, when the first information indicates the first operation, a first sub-value in the second part of the specific field indicates a first SSSG index, and a second sub-value in the second part of the specific field indicates a second SSSG index; and when the first information indicates the second operation, a first sub-value in the second part of the specific field indicates a first PDCCH skip duration, and a second sub-value in the second part of the specific field indicates a second PDCCH skip duration.

[0014] In another embodiment of the first aspect, the first portion of the particular field includes the most significant bit of the particular field, and the second portion of the particular field includes the least significant bit of the particular field.

[0015] In another embodiment of the first aspect, the DCI includes one of DCI format 0_1, DCI format 0_2, DCI format 1_1, and DCI format 1_2.

[0016] In another embodiment of the first aspect, the method further includes: performing the first operation with an SSSG index when the value of the specific field is 01; and performing the second operation with a PDCCH skip duration when the value of the specific field is 10.

[0017] In a second aspect of this application, a UE is provided, the UE including processing circuitry; a transceiver coupled to the processing circuitry; and a memory coupled to the processing circuitry, the memory storing computer-executable instructions that, when executed by the processing circuitry, cause the UE to perform the method described in the first aspect.

[0018] In a third aspect of this application, a base station (BS) is provided. The BS includes processing circuitry; a transceiver coupled to the processing circuitry; and a memory coupled to the processing circuitry. The memory stores at least one computer-executable instruction that, when executed by the processing circuitry, causes the BS to: send to a user equipment (UE) at least one of a first configuration associated with a first operation of a handover search space cluster group (SSSG) and a second configuration associated with a second operation of skipping a physical downlink control channel (PDCCH); and send to the UE downlink control information (DCI), the DCI including a specific field associated with at least one of the first configuration or the second configuration. The DCI instructs the UE to: perform the first operation or the second operation based on a value in the specific field.

[0019] In one embodiment of the third aspect, the specific field is a 2-bit field, and the value in the specific field is one of 00, 01, 10, and 11.

[0020] In another embodiment of the third aspect, the specific field indicates at least one of the SSSG index or the PDCCH skip duration.

[0021] In another embodiment of the third aspect, the first portion of the specific field includes first information indicating at least one of the first operation and the second operation, and the second portion of the specific field includes second information indicating the SSSG index or PDCCH skip duration.

[0022] In another embodiment of the third aspect, a first subvalue in the first portion of the specific field indicates the first operation, and a second subvalue in the first portion of the specific field indicates the second operation.

[0023] In another embodiment of the third aspect, when the first information indicates the first operation, a first sub-value in the second part of the specific field indicates a first SSSG index, and a second sub-value in the second part of the specific field indicates a second SSSG index; and when the first information indicates the second operation, a first sub-value in the second part of the specific field indicates a first PDCCH skip duration, and a second sub-value in the second part of the specific field indicates a second PDCCH skip duration.

[0024] In another embodiment of the third aspect, the first portion of the particular field includes the most significant bit of the particular field, and the second portion of the particular field includes the least significant bit of the particular field.

[0025] In another embodiment of the third aspect, the DCI includes one of DCI format 0_1, DCI format 0_2, DCI format 1_1, and DCI format 1_2.

[0026] In another embodiment of the third aspect, the DCI is further configured such that the UE: performs the first operation with the SSSG index when the value of the specific field is 01; and performs the second operation with the PDCCH skip duration when the value of the specific field is 10. Attached Figure Description

[0027] The various aspects of this exemplary disclosure are best understood from the following detailed description when read in conjunction with the accompanying drawings. For clarity of discussion, the various features are not drawn to scale, and the dimensions of the various features may be arbitrarily increased or decreased.

[0028] Figure 1 A timing diagram of a discontinuous reception (DRX) cycle according to one of the exemplary embodiments of this application is shown.

[0029] Figure 2A and Figure 2B A state diagram illustrating the switching mechanism of a searchspace set group (SSSG) according to one of the exemplary embodiments of this application is shown.

[0030] Figure 3 A timing diagram is shown illustrating the timing of physical downlink control channel (PDCCH) monitoring according to one of the exemplary embodiments of this application.

[0031] Figure 4A timing diagram of a PDCCH skipping scheme according to one of the exemplary embodiments of this application is shown.

[0032] Figure 5 A timing diagram is shown for downlink control information (DCI) with cyclic redundancy check (CRC) scrambled by a power-saving-radio network temporary identifier (PS-RNTI) (DCP) mechanism, according to one of the exemplary embodiments of this application.

[0033] Figures 6A to 6E A timing diagram is shown illustrating user equipment (UE) operation when different parameters are provided for PDCCH skipping and SSSG handover, according to an exemplary embodiment of this application.

[0034] Figure 7A and Figure 7B A flowchart illustrating a method performed by a UE to support a general design for PDCCH skipping and SSSG handover, according to one of the exemplary embodiments of this application.

[0035] Figure 8 A block diagram of a node for wireless communication according to one of the exemplary embodiments of this application is shown. Detailed Implementation

[0036] The abbreviations used in this application are defined as follows, and unless otherwise stated, the abbreviations have the following meanings:

[0037] full name of abbreviation

[0038] Bandwidth Adaptation (BA)

[0039] Buffer Status Report (BSR)

[0040] Bandwidth Part (BWP)

[0041] Carrier aggregation (CA)

[0042] Common Control Channel (CCCH)

[0043] Control Element (CE)

[0044] Channel (CH)

[0045] Control Resource Set (CORESET)

[0046] Channel State Information (CSI)

[0047] Common Search Space (CSS)

[0048] Downlink Control Information (DCI)

[0049] DCI with CRC scrambled by PS-RNTI (DCP)

[0050] Downlink (DL)

[0051] Discontinuous Reception (DRX)

[0052] Identification (ID)

[0053] Listen Before Talk (LBT)

[0054] Least Significant Bit (LSB)

[0055] Medium Access Control (MAC)

[0056] Master Cell Group (MCG)

[0057] Multiple-In-Multiple-Out (MIMO)

[0058] Most Significant Bit (MSB)

[0059] New Radio Unlicensed (NR-U)

[0060] Network (NW)

[0061] Physical Downlink Control Channel (PDCCH)

[0062] Physical Downlink Shared Channel (PDSCH)

[0063] Power Headroom Report (PHR)

[0064] Physical Uplink Control Channel (PUCCH)

[0065] Physical Uplink Shared Channel (PUSCH)

[0066] Random Access Response (RAR)

[0067] Release (Rel)

[0068] Radio Resource Control (RRC)

[0069] Radio Resource Management (RRM)

[0070] Subcarrier Spacing (SCS)

[0071] Sidelink (SL)

[0072] Semi-Persistent Scheduling (SPS)

[0073] Scheduling Request (SR)

[0074] Search Space (SS)

[0075] Search Space Set Group (SSSG)

[0076] User Equipment (UE)

[0077] Uplink (UL)

[0078] UE-specific search space (USS)

[0079] The following description contains specific information relating to exemplary embodiments in this application. The accompanying drawings and detailed description are merely exemplary embodiments. However, this application is not limited to these exemplary embodiments. Other variations and embodiments of this application will occur to those skilled in the art. Unless otherwise stated, identical or corresponding parts in the drawings may be indicated by identical or corresponding reference numerals. Furthermore, the drawings and illustrations in this application are generally not drawn to scale and are not intended to correspond to actual relative dimensions.

[0080] For the purposes of consistency and ease of understanding, the same reference numerals are used to designate the same features in the exemplary drawings (although this is not the case in some examples). However, features in different embodiments may differ in other respects, and therefore should not be narrowly limited to the features shown in the drawings.

[0081] The terms "one embodiment," "an embodiment," "an exemplary embodiment," "various embodiments," "some embodiments," and "embodiments of this application" may indicate that the embodiments of this application described herein may include specific features, structures, or characteristics, but not every possible embodiment of this application necessarily includes that specific feature, structure, or characteristic. Furthermore, the repeated use of the phrases "in one embodiment," "in an exemplary embodiment," or "an embodiment" does not necessarily refer to the same embodiment, although they may refer to the same embodiment. Additionally, any phrase used in conjunction with "this application," such as "embodiment," is not intended to imply that all embodiments of this application must include a specific feature, structure, or characteristic, but should be understood to mean that "at least some embodiments of this application" include the stated specific feature, structure, or characteristic. The term "coupled" is defined as a connection, whether direct or indirect through intermediate components, and is not necessarily limited to physical connections. The term "comprising" as used means "including but not necessarily limited to"; in particular, it refers to an open inclusion or member in the disclosed combinations, groups, series, and equivalents. The terms "system" and "network" in this application are used interchangeably.

[0082] The term "and / or" describes the relationship between related objects only, indicating that there may be three relationships. For example, "A and / or B" can mean: A exists alone, A and B exist simultaneously, or B exists alone. "A and / or B and / or C" can mean that at least one of A, B, and C exists. Furthermore, the character " / " usually indicates that the preceding and following related objects are in an "or" relationship.

[0083] Furthermore, for the purpose of non-limiting interpretation, specific details such as functional entities, technologies, protocols, and standards are described to provide an understanding of the described technologies. In other examples, detailed descriptions of well-known methods, technologies, systems, architectures, etc., are omitted to avoid unnecessary ambiguity in this application.

[0084] Those skilled in the art will readily recognize that any NW function or algorithm of this application can be implemented by hardware, software, or a combination of software and hardware. The described functions may correspond to modules, which can be software, hardware, firmware, or any combination thereof. Software implementations may include computer-executable instructions stored on a computer-readable medium such as memory or other types of storage devices. For example, one or more microprocessors or general-purpose computers with communication processing capabilities may be programmed using the corresponding executable instructions to execute the described NW function or algorithm. These microprocessors or general-purpose computers may be formed using application-specific integrated circuits (ASICs), programmable logic arrays, and / or using one or more digital signal processors (DSPs). While several exemplary embodiments described in this application are directed to software installed and executed on computer hardware, alternative exemplary embodiments implemented as firmware, hardware, or a combination of hardware and software are also within the scope of this application.

[0085] Computer-readable media include, but are not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, compact disc read-only memory (CD-ROM), cassette tape, magnetic tape, disk storage, or any other equivalent medium capable of storing computer-readable instructions.

[0086] Wireless communication network architectures (e.g., Long Term Evolution (LTE) systems, LTE-A systems, LTE-Pro systems, or 5G NR Radio Access Networks (RANs)) typically include at least one base station, at least one UE, and one or more optional network components that provide connectivity to the network. The UE communicates with the network (e.g., Core Network (CN), Evolved Packet Core (EPC) network, Evolved Universal Terrestrial Radio Access network (E-UTRAN), 5G Core (5GC), or the Internet) through the RAN established by one or more base stations.

[0087] In this application, the UE may include, but is not limited to, a mobile station, mobile terminal, device, or user communication radio terminal. For example, the UE may be a portable wireless device, including but not limited to mobile phones, tablet computers, wearable devices, sensors, vehicles, or personal digital assistants (PDAs) with wireless communication capabilities. In some embodiments, the UE may be referred to as a PHY / MAC / RLC / PDCP / SDAP / RRC entity. Similarly, a PHY / MAC / RLC / PDCP / SDAP / RRC entity may be referred to as a UE. The UE may be configured to receive and transmit signals to one or more cells in a radio access network via an air interface.

[0088] Base stations may include, but are not limited to, node Bs (NBs) in UMTS, evolved node Bs (eNBs) in LTE or LTE-A, radio network controllers (RNCs) in UMTS, base station controllers (BSCs) in GSM / GSM Enhanced Data Rates for GSM Evolution (EDGE) radio access networks (GERAN), next-generation eNBs (ng-eNBs) in evolved global terrestrial radio access (E-UTRA) BSs connected to 5GC, next-generation node Bs (gNBs) in 5G access networks (5G-AN), and any other devices capable of controlling radio communications and managing radio resources within the cell. A BS can connect to the network via a radio interface to serve one or more UEs.

[0089] The BS can be configured to provide communication services based on at least one Radio Access Technology (RAT), such as Worldwide Interoperability for Microwave Access (WiMAX), GSM (typically 2G), GERAN, General Packet Radio Service (GPRS), UMTS (typically 3G) based on Basic Wideband Code Division Multiple Access (W-CDMA), High-speed Packet Access (HSPA), LTE, LTE-A, evolved LTE (eLTE), NR (typically 5G), and LTE-A Pro. However, the scope of this application is not limited to these protocols.

[0090] A base station can be operated to provide radio coverage to a specific geographic area using multiple cells included in the RAN. The BS can support cell operation. Each cell can be operated to provide service to at least one UE within its radio coverage area. Specifically, each cell (often referred to as the serving cell) can provide service to one or more UEs within its radio coverage area (e.g., each cell schedules downlink (DL) resources and optional uplink (UL) resources to at least one UE within its radio coverage area for DL ​​and optional UL packet transmissions). The BS can communicate with one or more UEs in a radio communication system through multiple cells. Cells can allocate sidelink (SL) resources to support Proximity Service (ProSe) or Vehicle to Everything (V2X) services. Each cell can have coverage areas overlapping with other cells. In the case of Multi-RAT Dual Connectivity (MR-DC), the master cell of a Master Cell Group (MCG) or Secondary Cell Group (SCG) can be referred to as a SpCell. A cell or serving cell can include a primary cell (Pcell), a primary SCG cell (PSCell), or a secondary cell (Scell). A serving cell can be active or inactive. For dual-connectivity operations, the term Special Cell (SpCell) refers to a Pcell in the Master Cell Group (MCG) or a PSCell in the Secondary Cell Group (SCG), depending on whether the MAC entity is associated with the MCG or SCG respectively. Otherwise, a Special Cell refers to a Pcell. A Pcell can be an SpCell in the MCG. A PSCell can be an SpCell in the SCG. An MCG can be a group of serving cells associated with a Master Node (MN), including SpCells and optionally one or more Scells. An SCG can be a group of serving cells associated with a Secondary Node (SN), including SpCells and optionally one or more Scells.

[0091] As mentioned above, the NR frame structure supports flexible configuration to adapt to various next-generation (e.g., 5G) communication requirements, such as enhanced mobile broadband (eMBB), massive machine-type communication (mMTC), ultra-reliable and low-latency communication (URLLC), while meeting the requirements of high reliability, high data rate, and low latency. As agreed in 3GPP, orthogonal frequency division multiplexing (OFDM) technology can be used as the baseline for NR waveforms. An extended set of OFDM parameters, such as adaptive subcarrier spacing, channel bandwidth, and cyclic prefix (CP), can also be used. In addition, two coding schemes for NR are considered: (1) low-density parity-check (LDPC) codes and (2) polar codes. The adaptability of the coding scheme can be configured based on channel conditions and / or service applications.

[0092] Furthermore, it is also considered that the transmission time interval TX of a single NR frame should include at least downlink (DL) transmission data, guard interval, and uplink (UL) transmission data. The individual components of the DL transmission data, guard interval, and UL transmission data should also be configurable, for example, based on NR-based network dynamics. Additionally, sidelink resources can also be provided in the NR frame to support ProSe services.

[0093] The UE power saving work item document has been agreed upon in RAN#86, and the power saving range given therein is as follows:

[0094] (1) Enhancements to UE power saving in idle / inactive mode are specified by taking into account various system performance aspects.

[0095] (a) Several paging enhancements were studied and specified to reduce unnecessary UE paging reception without affecting legacy UEs.

[0096] (b) Several methods are specified for providing idle / inactive mode UEs with the timing of potential tracking reference signal (TRS) / channel-state information reference signal (CSI-RS) available in connected mode, thereby minimizing system overhead. It should be noted that always-on TRS / CSI-RS transmission via the gNodeB is not required.

[0097] (2) Research and specifications were developed for enhanced energy-saving technologies for connected UEs to minimize the impact on system performance.

[0098] (a) Researched and specified an adaptive extension based on Rel-16DCI for power saving during DRX activity time for active BWP, including reducing PDCCH eavesdropping when connected DRX (C-DRX) is configured.

[0099] (b) The feasibility and performance impact of relaxing UE measurements for radio link monitoring (RLM) and / or beam failure detection (BFD) were investigated, particularly for low-mobility UEs with short DRX cycles. Furthermore, relaxations to the corresponding requirements were specified.

[0100] In the following description, the scope (2)(a) mentioned above is discussed, which can reduce PDCCH listening work in connection mode.

[0101] In RRC connection mode, the UE's PDCCH listening activity can be managed by DRX, BA, and DCP, etc.

[0102] Figure 1 A timing diagram of a DRX cycle according to one of the exemplary embodiments of this application is shown.

[0103] refer to Figure 1 When DRX is configured in the UE, the UE does not need to continuously listen to the PDCCH. Specifically, the DRX period includes the duration and timing of DRX activation. The UE listens to the PDCCH during the activation duration, but does not listen to the PDCCH during the DRX timing period. DRX has the following characteristics:

[0104] DRX Enable Duration: The duration for which the UE waits to receive the PDCCH after being woken up (e.g., enable duration). If the UE successfully decodes the PDCCH, the UE remains awake and starts an inactive timer.

[0105] DRX Inactivity Timer: The UE waits for the duration of a successful PDCCH decoding, starting from the last successful decoding. If decoding fails, the UE can return to sleep. The UE can restart the inactivity timer after a single successful decoding of the PDCCH for a new transmission (e.g., not for retransmissions).

[0106] DRX retransmission timer: The duration to wait for the expected retransmission.

[0107] DRX cycle: A cycle (e.g., DRX cycle) specifically refers to the periodic repetition of an on-duration period following a possible period of inactivity.

[0108] DRX Activation Time: The total duration for which the UE listens to the PDCCH. This total duration includes the "on duration" of the DRX cycle, the time the UE performs continuous reception while the inactive timer has not expired, and the time the UE performs continuous reception while waiting for a retransmission opportunity.

[0109] When a BA is configured in the UE, the UE only listens to the PDCCH on one active BWP. That is, the UE does not need to listen to the PDCCH on the entire DL frequency of the cell. The BWP inactivity timer (independent of the aforementioned DRX inactivity timer) is used to switch the active BWP to the default BWP when the BWP inactivity timer expires. Furthermore, the BWP inactivity timer is restarted when PDCCH decoding is successful.

[0110] Additionally, when configured accordingly, the UE can indicate whether it needs to listen to the PDCCH during the next DRX on-duration period by listening to the DCP on the active BWP. If the UE does not detect the DCP on the active BWP, the UE will not listen to the PDCCH during the next DRX on-duration period unless it is explicitly configured (by other means) to do so in this case. The UE can be configured to listen to the DCP when connected mode DRX is configured and with an offset configured before the DRX on-duration period. Multiple listening opportunities can be configured before the DRX on-duration period. The UE does not listen to the DCP when it occurs during DRX activity time, measurement gaps, or BWP handover; in this case, the UE listens to the PDCCH during the next on-duration period. If the DCP is not configured in the active BWP, the UE follows normal DRX operation. When CA is configured, the DCP is configured only on the PCell. A DCP can be configured to control PDCCH listening during a single DRX on-duration period for one or more UEs.

[0111] When a UE meets the criteria for determining that it is in low mobility and / or not at the cell edge, power savings in the RRC_IDLE and RRC_INACTIVE states can be achieved by relaxing the radio resource management (RRM) measurements of neighboring cells. Power saving can also be enabled during activity via cross-slot scheduling, which helps the UE achieve energy savings, provided that the UE is not scheduled to receive PDSCH, nor is it triggered to receive aperiodic CSI (A-CSI), or send PUSCH scheduled by PDCCH, until the minimum scheduling offsets K0 and K2 are dynamically adaptively controlled by PDCCH.

[0112] In Rel-16 NR-U, a Search Space (SS) Cluster Group (SSSG) handover feature was introduced, which allows the UE to be configured to switch between sparse PDCCH listening and frequent PDCCH listening. SSSG handover has at least two handover mechanisms. For example, SSSG handover can be performed at least through explicit indication, implicit indication, and timer.

[0113] Figure 2A and Figure 2B A state diagram illustrating the switching mechanism of an SSSG according to one of the exemplary embodiments of this application is shown.

[0114] like Figure 2A As shown, explicit SS handover between two SSSGs is accomplished by detecting DCI format 2_0. For example, the UE can configure the RRC parameter searchSpaceSwitchTrigger-r16, and each SearchSpaceSwitchingTrigger object provides a position in the DCI format 2_0 field indicating the SS handover flag for the serving cell, or, if CellGroupsForSwitching-r16 is configured, the position indicating the serving cell group. A bit value of zero (i.e., 0) in the SS handover flag indicates the first SS group to be listened to (e.g., SS group 0), and a bit value of one (i.e., 1) in the SS handover flag indicates the second SS group to be listened to (e.g., SS group 1). For example, the first SS group (e.g., SS group 0) has fewer PDCCH listening opportunities than the second SS group (e.g., SS group 1), or the first SS group may have a larger sparse search space set than the second SS group, so listening to the second SS group (e.g., SS group 1) requires more power than listening to the first SS group (e.g., SS group 0).

[0115] For example, the UE is configured with the RRC parameter `searchSpaceSwitchTrigger-r16`. When the UE is listening to the first SS group (e.g., SS group 0) and detects that the SS handover flag carried in DCI format 2_0 has a bit value of 1, the UE can stop listening to the first SS group (e.g., SS group 0) and switch to listening to the second SS group (e.g., SS group 1). Conversely, when the UE is listening to the second SS group (e.g., SS group 1) and detects that the SS handover flag carried in DCI format 2_0 has a bit value of 0, the UE can stop listening to the second SS group (e.g., SS group 1) and switch to listening to the first SS group (e.g., SS group 0). It should be noted that more details on explicit SS handover can be found in 3GPP TS 38.331.

[0116] refer to Figure 2B Implicit SS handover occurs when the UE is not configured with the RRC parameter searchSpaceSwitchTrigger-r16. Implicit SS handover can be implemented using any DCI, not limited to DCI format 2_0.

[0117] For example, the UE is not configured with the RRC parameter `searchSpaceSwitchTrigger-r16`. If a UE listening to the first SS group (e.g., SS group 0) detects any DCI on an SS associated with the first SS group (e.g., SS group 0), the UE can stop listening to the first SS group (e.g., SS group 0) and switch to listening to the second SS group (e.g., SS group 1). In some implementations, if a UE listening to the second SS group (e.g., SS group 1) detects any DCI on any SS, the UE can continue listening to the second SS group (e.g., SS group 1) without switching back to the first SS group (e.g., SS group 0). It should be noted that more details about implicit SS switching can be found in 3GPP TS 38.331.

[0118] refer to Figure 2A and Figure 2BTimer-based SS handover can be implemented by configuring a specific timer. Specifically, a timer for SS handover (e.g., `searchSpaceSwitchingTimer`) can be configured. For example, when the UE detects a DCI format 2_0 with the SS handover flag set to 1, detects any DCI on an SS associated with SS group 0, and / or detects any DCI on any SS, the UE can (re)start the timer. When the timer expires, the UE can stop listening to the second SS group (e.g., SS group 1) and switch to listening to the first SS group (e.g., SS group 0). It is important to note that timer-based SS handover can be applied to both explicit and implicit SS handover. Further details on timer-based SS handover can be found in 3GPP TS 38.331.

[0119] In NR, basically, the `monitoringSlotPeriodicityAndOffset` and `duration` in `SearchSpace` determine the location of the time slot for monitoring PDCCH. Then, `monitoringSymbolsWithinSlot` in `SearchSpace` and `duration` in `ControlResourceSet` determine the PDCCH monitoring timing pattern within the time slot.

[0120] Figure 3 A timing diagram showing the PDCCH listening timing according to one of the exemplary embodiments of this application is shown.

[0121] refer to Figure 3 As shown, `monitoringSlotPeriodicityAndOffset` indicates a period of 6, an offset of 0, and a duration of 2 in the SearchSpace. Therefore, PDCCH is monitored in slots SL0, SL1, SL6, and SL7. Additionally, `monitoringSymbolsWithinSlot` is set to "1000010000", and the duration in the ControlResourceSet is set to 3. Therefore, for each of slots SL0, SL1, SL6, and SL7, PDCCH is monitored in symbols SB0, SB1, SB2, SB5, SB6, and SB7.

[0122] Figure 4 A timing diagram of a PDCCH skipping scheme according to one of the exemplary embodiments of this application is shown.

[0123] refer to Figure 4As shown, the UE can receive a PDCCH skip indication (included in a specific DCI format) from the network (NW) at, for example, time point T1. The PDCCH skip indication can be used to indicate the duration DR for which the UE can stop listening to the PDCCH. The UE can begin applying PDCCH skipping (i.e., stopping PDCCH listening) at time point T2 after the application delay DL from the time point T1 when the UE receives the PDCCH skip indication. After the duration DR for stopping PDCCH listening, the UE can resume listening to the PDCCH as usual (e.g., when the UE is in DRX active time). In some implementations, the NW can pre-configure one or more durations for the UE via higher-layer parameters (e.g., RRC configuration), and the PDCCH skip indication can indicate which duration should be applied for PDCCH skipping (i.e., for stopping PDCCH listening). In this application, the duration DR for which the UE stops listening to the PDCCH can be referred to as the PDCCH skip duration.

[0124] Rel-16 introduces a new physical layer signaling scheme that can be used to further control PDCCH listening behavior during the DRX on-duration based on the configured DRX mechanism. This means that the NW can send new physical layer signaling to the UE to inquire whether the UE should wake up during the DRX on-duration. The new physical layer signaling is called DCI and is scrambled with CRC using PS-RNTI (DCP).

[0125] Figure 5 A timing diagram of a DCP mechanism according to one of the exemplary embodiments of this application is shown.

[0126] refer to Figure 5 As shown, the DCP, indicated by DCI format 2_6, is used to notify one or more UEs of power-saving information outside of DRX activity time. DCI format 2_6 includes two indicators. One is a "wake-up indicator" (1 bit), and the other is a "sleep indicator" (bits 0-5). The "wake-up indicator" controls the PDCCH listening behavior for the DRX on-duration period. Specifically, the DCP's "wake-up indicator" indicates whether the UE activates the drx-onDurationTimer or remains in sleep mode. On the other hand, the "sleep indicator" controls the BWP handover for a sleep SCell group (i.e., entering or leaving a sleep BWP).

[0127] When a BWP handover occurs involving a serving cell within a dormancy group, the NW can group one or more serving cells (e.g., SCells) into dormancy groups and can configure one or more dormancy groups. The dormancy group configuration can be indicated by `IEdormancyGroupWithinActiveTime` and / or `dormancyGroupOutsideActiveTime` (in `ServingCellConfig`). `IEdormancyGroupWithinActiveTime` / `dormancyGroupOutsideActiveTime` contain the IDs of the dormancy groups to which the serving cell belongs during / outside the active time. Additionally, `IE maxNrofDormancyGroups` determines how many groups can be configured for a cell group. After configuring the dormancy group, the NW can switch the BWPs of all serving cells entering / leaving the dormancy BWP group via signaling (e.g., DCI format 2_6, DCI format 0_1, DCI format 1_1, etc.).

[0128] Based on the discussion of power saving in Rel-17, a general design for DCI-based PDCCH listening adaptation in the active time of an active BWP can be determined to support features including SSSG handover and PDCCH skipping for a certain duration. Furthermore, features including SSSG handover, PDCCH skipping duration, and SCell sleep can be considered.

[0129] In some implementations, one or more DCI fields may be added (and / or reused) to support at least one of the functions of SSSG handover, PDCCH skipping, and SCell sleep. When the UE receives / decodes / detects a DCI including one or more DCI fields, the UE may perform at least one of SSSG handover, PDCCH skipping, and SCell sleep based on the one or more DCI fields. One or more pieces of information or configuration related to at least one of SSSG handover, PDCCH skipping, and SCell sleep can be configured via RRC messages. One or more DCI fields are associated with one or more pieces of information or configuration.

[0130] In some implementations, one or more pieces of information or configuration in the received RRC message may indicate the presence of one or more DCI fields. In some implementations, one or more pieces of information or configuration in the received RRC message may indicate the presence of one or more DCI fields and the field size of each DCI field.

[0131] In some implementations, the UE can perform at least one of SSSG handover, PDCCH skipping, and SCell sleep based on one or more values ​​in one or more DCI fields. In some implementations, the UE can perform at least one of SSSG handover, PDCCH skipping, and SCell sleep based on one or more values ​​in one or more DCI fields and one or more pieces of information or configuration associated with those one or more DCI fields.

[0132] In some implementations, one or more values ​​in one or more DCI fields may indicate one or more indices of information or configuration that are associated with at least one of SSSG switching, PDCCH skipping, and SCell hibernation configurations (e.g., via received RRC messages).

[0133] In some implementations, one or more pieces of information or configuration may include a table associated with at least one of SSSG switching, PDCCH skipping, and SCell hibernation. One or more values ​​in one or more DCI fields may provide a row index (e.g., m or m+1) for the table.

[0134] In some implementations, the row index defines the activation / deactivation (or enable / disable) of PDCCH skipping, and / or the activation / deactivation (or enable / disable) of SSSG switching, and / or the activation / deactivation (or enable / disable) of SCell hibernation, and / or parameters for PDCCH skipping (e.g., PDCCH skipping duration), and / or parameters for SSSG switching (e.g., SSSG ID), and / or parameters for SCell hibernation (e.g., SCell group ID for SCell hibernation).

[0135] In some implementations, the UE may perform at least one of SSSG handover, PDCCH skipping, and SCell hibernation based on row indexes (e.g., m) in one or more DCI fields and a table associated with at least one of SSSG handover, PDCCH skipping, and SCell hibernation.

[0136] In some implementations, one or more DCI fields may include information or indications related to at least one of the following:

[0137] --Activation / deactivation (or enabling / disabling) related to PDCCH skipping (for a period of time), and / or

[0138] - Activation / deactivation (or enabling / disabling) related to SSSG switching, and / or

[0139] - Activation / deactivation (or enabling / disabling) related to SCell hibernation, and / or

[0140] - Parameters related to PDCCH skipping (e.g., PDCCH skipping duration), and / or

[0141] - Parameters related to SSSG switching (e.g., SSSG ID), and / or

[0142] - Parameters related to SCell hibernation (e.g., SCell group ID, and / or the cell ID in the SCell hibernation SCell group), and / or

[0143] - Skip the associated SCell group with PDCCH, and / or

[0144] -SCell groups associated with SSSG switching, and / or

[0145] - SCell groups associated with SCell hibernation.

[0146] In some implementations, the parameters associated with PDCCH skipping may include at least one of the following:

[0147] -PDCCH skip duration (e.g., Tskip, in milliseconds (msec), and / or slot, and / or DRX period, and / or symbol, and / or listen timing and / or subframe), and / or

[0148] -CORESET ID, and / or

[0149] -SSID, and / or

[0150] - Multiple symbols (e.g., Pskip, in milliseconds, and / or slots, and / or DRX periods, and / or symbols, and / or listening times and / or subframes), and / or

[0151] -Offset.

[0152] Specifically, Pskip refers to the delay for applying PDCCH skipping. For example, PDCCH skipping can be applied in the first time slot after at least Pskip symbols from the last symbol of the PDCCH with DCI. As another example, PDCCH skipping can be applied after at least Pskip symbols from the last symbol of the PDCCH with DCI.

[0153] Specifically, the offset can be used to indicate when the UE should begin performing PDCCH skipping. For example, the offset can be used to indicate the time period starting from the receipt of the DCI indication for PDCCH skipping, and / or the time period starting from the subframe / slot / DRX period, which includes the DCI indication for PDCCH skipping.

[0154] In some implementations, the parameters associated with SSSG switching may include at least one of the following:

[0155] -SSSG ID, and / or

[0156] - The number of SSSGs, and / or

[0157] -SSSG switching duration (e.g., searchSpaceSwitchingTimer, which can be the duration for which SSSG switching is applied), and / or

[0158] - Multiple symbols (e.g., Pswitch, in milliseconds, and / or slots, and / or DRX cycles, and / or symbols, and / or listening times and / or subframes), and / or

[0159] -Offset.

[0160] Specifically, Pswitch is the delay for applying SSSG handover. For example, SSSG handover can be applied in the first time slot after at least Pswitch symbols following the last symbol of the PDCCH with DCI. Alternatively, SSSG handover can be applied after at least Pswitch symbols following the last symbol of the PDCCH with DCI.

[0161] Specifically, the offset can be used to indicate when the UE should begin performing SSSG handover. For example, the offset can be used to indicate a time period from the receipt of the DCI indication for SSSG handover, and / or a time period from the start of a subframe / slot / DRX period that includes a DCI indication for PDCCH skipping.

[0162] In some implementations, one or more reused DCI fields may include at least one of the following:

[0163] -SCell hibernation indicator field, and / or

[0164] - Carrier indicator field, and / or

[0165] - Wake-up indicator, and / or

[0166] - DCI field associated with SSSG switching.

[0167] In some implementations, a DCI that includes one or more DCI fields can be:

[0168] DCI format 0_0, and / or

[0169] DCI format 0_1, and / or

[0170] DCI format 0_2, and / or

[0171] DCI format 1_0, and / or

[0172] DCI format 1_1, and / or

[0173] DCI format 1_2, and / or

[0174] DCI format 2_0, and / or

[0175] DCI format 2_1, and / or

[0176] DCI format 2_2, and / or

[0177] DCI format 2_3, and / or

[0178] DCI format 2_4, and / or

[0179] DCI format 2_5, and / or

[0180] DCI format 2_6 (during and / or outside of the event period), and / or

[0181] DCI format 3_0, and / or

[0182] DCI format 3_1.

[0183] In some implementations, the UE can receive / decode / detect control information (e.g., DCI) including an n-bit carrier indication field and an m-bit SCell sleep indication field. If the value in the n-bit carrier indication field is 0, the UE can determine that the value in the m-bit SCell sleep indication field indicates the RRC parameters associated with SCell sleep. If the value in the n-bit carrier indication field is 1, the UE can determine that the value in the m-bit SCell sleep indication field joint indication indicates the RRC parameters associated with PDCCH skipping and SSSG handover.

[0184] For example, the value x (e.g., x = 001, or x = 1) in an m-bit DCI field (e.g., an m-bit SCell sleep indication field) provides a row index (e.g., x or x+1) to a table that corresponds to one or more pieces of information or configurations related to at least one of SSSG switching and / or PDCCH skipping (for a period of time) configured in the RRC message. Table 1 below provides an example of an (RRC) table corresponding to one or more pieces of information or configurations related to at least one of SSSG switching and / or PDCCH skipping duration. Taking row index "1" as an example, the row of row index "1" defines the activation / enable PDCCH skipping duration and the activation / enable SSSG switching, where the PDCCH skipping duration is 6 and the SSSG ID is 1.

[0185] Table 1

[0186]

[0187] As shown in Table 1, when the DCI field related to SSSG switching and PDCCH skipping is a 3-bit field, the first bit (e.g., MSB) indicates the activation / deactivation of SSSG switching, the second bit (e.g., the middle bit of the 3-bit field) indicates the activation / deactivation of PDCCH skipping, and the other bits (e.g., LSB) indicate the parameters related to SSSG switching and PDCCH skipping.

[0188] However, it should be noted that those skilled in the art can change the values ​​in the table according to different designs. Therefore, each bit in the DCI field can indicate information different from that in Table 1. For example, the MSB of the DCI field can be used to indicate the activation / deactivation of the SSSG switch, and the LSB of the DCI field can be used to indicate the activation / deactivation of the PDCCH skip.

[0189] In some implementations, the UE may receive / decode / detect control information (e.g., DCI) including a 1-bit DCI field indicating activation / deactivation (or enable / disable) of PDCCH skipping. If the value in the bit field is a first value (e.g., 0 or 1), the UE may either not activate / disable or deactivate / disable PDCCH skipping. If the value in the bit field is a second value (e.g., 1 or 0) that differs from the first value, the UE may either activate / enable PDCCH skipping or not deactivate / disable PDCCH skipping.

[0190] In some cases, if the DCI instructs the UE to activate / enable PDCCH skipping, the UE can perform PDCCH skipping once after receiving the DCI.

[0191] In some cases, if the DCI instructs the UE to activate / enable PDCCH skipping (for a period of time), the UE can perform multiple PDCCH skips after receiving the DCI. The number of PDCCH skips performed can be configured by the DCI instruction and / or by the RRC message. For example, this number can be related to the DRX period.

[0192] In some cases, if the DCI instructs the UE to activate / enable PDCCH skipping, the UE can perform PDCCH skipping for a duration that can be determined by a timer associated with that duration. For example, the timer can be (re)started when the UE receives the DCI to activate / enable PDCCH skipping. While the timer is running, the UE can perform PDCCH skipping for each DRX cycle. When the timer expires, the UE stops performing PDCCH skipping.

[0193] In some implementations, the UE may receive / decode / detect control information (e.g., DCI) including a 1-bit DCI field indicating the activation / deactivation (or enable / disable) of SSSG switching. If the value in the bit field is a first value (e.g., 0 or 1), the UE may either not activate / disable SSSG switching, or may deactivate / disable SSSG switching. If the value in the bit field is a second value (e.g., 1 or 0), which is different from the first value, the UE may either activate / disable SSSG switching, or may either not deactivate / disable SSSG switching.

[0194] In some cases, if the DCI instructs the UE to activate / enable SSSG handover, the UE can perform SSSG handover after receiving the DCI.

[0195] In some cases, if the DCI instructs the UE to activate / enable SSSG handover, the UE can perform SSSG handover within a cycle, which can be determined by a timer associated with that cycle. For example, the timer can be (re)started when the UE receives the DCI to activate / enable SSSG handover. While the timer is running, the UE can perform SSSG handover. When the timer expires, the UE can switch the detected SSSG to a configured or default SSSG. For example, the default SSSG can be pre-configured by DL UE-specific control signaling via a given default SSSG ID.

[0196] Therefore, it should be understood that the 1-bit field in DCI can be used to jointly indicate the activation / deactivation (or enable / disable) of PDCCH skipping and SSSG switching.

[0197] In some implementations, a 1-bit field in the DCI can indicate the activation and / or deactivation of both PDCCH skipping and SSSG switching. For example, if the value in the bit field is a first value (e.g., 0 or 1), the UE can not activate / enable (or deactivate / disable) PDCCH skipping and SSSG switching; if the value in the bit field is a second value different from the first value (e.g., 1 or 0), the UE can activate / enable (or not deactivate / disable) PDCCH skipping and SSSG switching.

[0198] In some implementations, a 1-bit field in the DCI can indicate the activation / enablement of one of PDCCH skipping and SSSG handover, and the deactivation / disabling of the other. Specifically, the 1-bit field in the DCI can be used to select one of PDCCH skipping and SSSG handover. For example, if the value in the bit field is a first value (e.g., 0 or 1), the UE can either not activate / enable (or deactivate / disable) PDCCH skipping and activate / enable (or not deactivate / disable) SSSG handover; if the value in the bit field is a second value different from the first value (e.g., 1 or 0), the UE can either activate / enable (or not deactivate / disable) PDCCH skipping and not activate / enable (or deactivate / disable) SSSG handover.

[0199] Based on the foregoing description, the UE can receive / decode / detect control information (e.g., DCI) including a specific n-bit field associated with multiple functions or operations (e.g., PDCCH skipping and SSSG switching). More specifically, the n-bit field can include m bits for selecting one of the multiple functions or operations (e.g., one of PDCCH skipping and SSSG switching). More specifically, the n-bit field can include p (e.g., nm) bits for indicating information or configuration associated with the selected function or operation. For example, information or configuration associated with PDCCH skipping can include the PDCCH skip duration, and information or configuration associated with SSSG switching can include the SSSG index (e.g., SSSG ID). In other examples, the p (e.g., nm) bits can indicate other types of information or configuration.

[0200] Taking n=2 and m=1 as examples, the UE can be configured to perform both PDCCH skipping and SSSG handover, and can receive / decode / detect DCI including a specific 2-bit field associated with PDCCH skipping and SSSG handover. When the first bit indicates PDCCH skipping or when the first bit indicates the SSSG ID for SSSG handover, the value of the first bit (e.g., MSB) of the specific 2-bit field can indicate one of PDCCH skipping and SSSG handover, and the value of the second bit (e.g., LSB) of the specific 2-bit field can indicate the PDCCH skipping duration. For example, when the first bit is "0", the UE can perform SSSG handover; when the first bit is "1", the UE can perform PDCCH skipping. Furthermore, when both the first and second bits are "0", the UE can perform SSSG handover based on the first SSSG ID (e.g., refer to the aforementioned table). When both the first and second bits are "1", the UE can perform SSSG handover based on the second SSSG ID (e.g., refer to the aforementioned table). When the first bit is "1" and the second bit is "0", the UE can perform PDCCH skipping according to the first PDCCH skipping duration (e.g., refer to the aforementioned table). When the first bit is "1" and the second bit is "1", the UE can perform PDCCH skipping according to the second PDCCH skipping duration (e.g., refer to the aforementioned table).

[0201] In some implementations, the UE may be provided with multiple symbols (e.g., Pskip symbols) as a delay for applying PDCCH skipping. PDCCH skipping may be applied in a first time slot, which is the time slot following at least Pskip symbols from the last symbol of the PDCCH containing DCI. The PDCCH skipping duration (e.g., Tskip) is the skip duration for PDCCH skipping. The UE may be provided with multiple symbols (e.g., Pswitch symbols) as a delay for applying SSSG handover. SSSG handover (e.g., switching the monitored SSSG from SSSG1 to SSSG2) may be applied in a first time slot, which is the time slot following at least Pswitch symbols from the last symbol of the PDCCH including DCI.

[0202] Figures 6A to 6E A timing diagram is shown illustrating user equipment (UE) operation when different parameters are provided for PDCCH skipping and SSSG handover, according to an exemplary embodiment of this application.

[0203] refer to Figures 6A to 6EThe system can provide the UE with parameters including the delay for application PDCCH skipping (e.g., Pskip), the delay for application SSSG handover (e.g., Pswitch), the PDCCH skipping duration (e.g., Tskip), and parameters for activating / enabling PDCCH skipping and SSSG handover. The UE can perform PDCCH skipping and SSSG handover based on the provided parameters Pskip, Pswitch, and Tskip.

[0204] refer to Figure 6A In some cases, the Tskip duration begins after the UE starts applying the SSSG handover. In these cases, the UE may first apply the SSSG handover (e.g., switch the monitored SSSG from SSSG1 to SSSG2), apply PDCCH skip from the start of the Tskip duration (e.g., stop listening to any PDCCH timing), and then resume listening to the original SSSG (e.g., SSSG2) from the end of the Tskip duration, which listens to the original SSSG before the UE starts applying the PDCCH skip (i.e., before the Tskip duration).

[0205] In some implementations, where the UE provides both Pskip and Pswitch and both PDCCH skipping and SSSG handover are activated / enabled, the UE can apply PDCCH skipping before SSSG handover in some implementations. In other implementations, where the UE provides both Pskip and Pswitch and both PDCCH skipping and SSSG handover are activated / enabled, the UE can apply SSSG handover before PDCCH skipping.

[0206] In some implementations, when two (or more) functions (e.g., PDCCH skipping and SSSG handover) are activated / enabled, the UE can apply an activation / enablement function that is later than the other functions. In other implementations, when two (or more) functions (e.g., PDCCH skipping and SSSG handover) are activated / enabled, the UE can apply an activation / enablement function that is earlier than the other functions.

[0207] refer to Figure 6B and Figure 6C In some cases, the parameters Pskip, Pswitch, and Tskip can be provided to the UE, and the parameter Pswitch can indicate that an SSSG handover should be applied during the duration of Tskip. This applies when the SSSG handover occurs before the PDCCH skip, such as... Figure 6BAs shown, the UE can apply SSSG handover at a timing indicated by the parameter Pswitch during the Tskip duration. In cases where the SSSG handover does not occur earlier than the PDCCH skip, as... Figure 6C As shown, the UE can apply SSSG handover when the Tskip duration ends.

[0208] refer to Figure 6D and Figure 6E In some cases, the UE can be provided with parameters Pskip, Pswitch, and Tskip. The Tskip duration ends before the UE begins applying the SSSG handover, and the UE may not listen for PDCCH timings during the Tskip duration. Figure 6D In the scenario shown, the UE can listen to the original SSSG (i.e., SSSG1) that was listened to before the UE started applying PDCCH skip (i.e., before the Tskip duration) from the end of the Tskip duration until the UE begins applying the SSSG handover. In some other cases, such as... Figure 6E As shown, starting from the end of the Tskip duration, the UE can stop listening to the PDCCH timing until the UE starts applying the SSSG handover (i.e., the UE can continue applying the PDCCH skip until the UE starts applying the SSSG handover).

[0209] In some implementations, the UE can receive / decode / detect control information (e.g., DCI) including a 1-bit DCI field indicating activation and / or deactivation of PDCCH skipping and / or SSSG switching. The UE can activate / enable or deactivate / disable PDCCH skipping and / or SSSG switching based on information or configuration configured via RRC messages. For example, information or configuration configured via RRC messages can indicate which functions the DCI controls. In some cases, information or configuration configured via RRC messages can indicate that the DCI controls only PDCCH skipping. In some cases, information or configuration configured via RRC messages can indicate that the DCI controls only SSSG switching. In some cases, information or configuration configured via RRC messages can indicate that the DCI controls both PDCCH skipping and SSSG switching.

[0210] In some implementations, the UE can receive / decode / detect control information (e.g., DCI) including a 1-bit DCI field that jointly indicates the activation / enable or deactivation / disable of PDCCH skipping and SSSG switching. If the value in the bit field is a first value (e.g., 0 or 1), the UE can activate / enable PDCCH skipping and deactivate / disable (or may not activate / disable) SSSG switching. If the value in the bit field is a second value different from the first value (e.g., 1 or 0), the UE can activate / enable SSSG switching and deactivate / disable (or not activate / disable) PDCCH skipping.

[0211] In some implementations, the UE may receive / decode / detect control information (e.g., DCI) including a 2-bit DCI field that jointly indicates PDCCH skipping and SSSG handover activation / enable or deactivation / disable. The most significant bit (MSB) of the DCI field may be used to indicate PDCCH skipping activation / enable or deactivation / disable. The least significant bit (LSB) of the DCI field may be used to indicate SSSG handover activation / enable or deactivation / disable.

[0212] For example, when the DCI field value is 00, the UE can disable / inactivate (or deactivate / disable) PDCCH skipping and SSSG handover. When the DCI field value is 11, the UE can activate / enable PDCCH skipping and SSSG handover. When the DCI field value is 01, the UE can deactivate / disable (or disable / inactivate) PDCCH skipping and can activate / enable SSSG handover. When the DCI field value is 10, the UE can activate / enable PDCCH skipping and can deactivate / disable (or disable / inactivate) SSSG handover.

[0213] In another example, with a DCI field value of 11, the UE can disable / inactively disable (or deactivate / disable) PDCCH skipping and SSSG handover. With a DCI field value of 00, the UE can activate / enable PDCCH skipping and SSSG handover. With a DCI field value of 10, the UE can deactivate / disable (or disable / inactive) PDCCH skipping and can activate / enable SSSG handover. With a DCI field value of 01, the UE can activate / enable PDCCH skipping and can deactivate / disable (or disable / inactive) SSSG handover.

[0214] In some implementations, the UE can receive / decode / detect control information (e.g., DCI) including an n-bit (e.g., n=5) DCI field and values ​​in the n-bit DCI field (e.g., m=00110, or m=6) that can be used to provide a row index (e.g., m or m+1) to a table corresponding to one or more pieces of information or configuration related to at least one of SSSG handover, and / or PDCCH skipping, and / or SCell sleep configured in a received RRC message. For example, row index "6" defines the deactivation (for a period of time) of PDCCH skipping, and / or the activation of SSSG handover, and / or SSSG ID 2.

[0215] In some implementations, the UE can receive / decode / detect control information (e.g., DCI), which includes an n-bit (e.g., n=3) DCI field. The value m (e.g., m=001 or m=1) in the n-bit DCI field can be used to provide a row index (e.g., m or m+1) to a table corresponding to one or more pieces of information or configuration related to at least one of SSSG handover, and / or PDCCH skipping, and / or SCell sleep configured in a received RRC message. Table 1 above provides an example of an RRC table corresponding to one or more pieces of information or configuration related to at least one of SSSG handover, and / or PDCCH skipping duration, and / or SCell sleep. Taking row index "1" as an example, the row of row index "1" defines the activation / enablement of PDCCH skipping duration and the activation / enablement of SSSG handover, where the PDCCH skipping duration is 6 and the SSSG ID is 1.

[0216] In some implementations, the UE can receive / decode / detect control information (e.g., DCI) including an n-bit (e.g., n=3) DCI field. The value m in the n-bit DCI field (e.g., m=011, or m=3) can provide a row index (e.g., m or m+1) to a table corresponding to one or more pieces of information or configurations related to at least one of SSSG handover, and / or PDCCH skip (for a period of time), and / or SCell sleep configured in the received RRC message. Table 2 below provides an example of an RRC table corresponding to one or more pieces of information or configurations related to at least one of SSSG handover, and / or PDCCH skip duration, and / or SCell sleep. Taking row index "3" as an example, the row of row index "3" defines the deactivation / disabling of PDCCH skip (which also means that the configured PDCCH skip duration can be ignored) and the activation / enabling of SSSG. The SSSG handover duration (i.e., searchSpaceSwitchingTimer) is 8, and the SSSG ID is 1.

[0217] Table 2

[0218]

[0219]

[0220] In some implementations, the UE can receive / decode / detect control information (e.g., DCI), which includes an n-bit (e.g., n=3) DCI field, where the value m (e.g., m=001 or m=1) in the n-bit DCI field provides a row index (e.g., m or m+1) to a table corresponding to one or more pieces of information or configurations related to at least one of SSSG handover and / or PDCCH skip (for a period of time), and / or SCell sleep configured in a received RRC message. Table 3 below provides an example of an RRC table corresponding to one or more pieces of information or configurations related to at least one of SSSG handover, and / or PDCCH skip duration, and / or SCell sleep. Taking row index "1" as an example, the row of row index "1" defines the activation / enablement of PDCCH skip, where the PDCCH skip duration is 6, the SSSG handover duration (i.e., searchSpaceSwitchingTimer) is 3, and the SSSG ID is 0. In this case, if the indicated SSSG ID is the same as the SSSG ID currently being listened to by the UE, the UE may not change the SSSG ID. In other words, if the SSSG ID indicated by the received control information and / or (RRC) table is the same as the SSSG ID of the SSSG that the UE is currently listening to, the UE will not perform an SSSG handover. Therefore, if the UE does not perform an SSSG handover, or does not change the SSSG ID, the configuration duration for the SSSG handover (i.e., searchSpaceSwitchingTimer) can be ignored.

[0221] Table 3

[0222]

[0223] In some implementations, when the UE is instructed to activate / enable PDCCH skipping and / or SSG handover, the UE can perform PDCCH skipping and / or SSG handover on one or more serving cells or a group of serving cells. The serving cell can be a PCell and / or SCell. The UE can configure cell groups and / or lists for PDCCH skipping and / or SSSG handover, for example, through RRC configuration via at least one RRC message. The serving cell group can be a dormant SCell group. The UE can determine to perform PDCCH skipping and / or SSG handover on cells where PDCCH skipping and / or SSSG handover is already configured.

[0224] In some implementations, when the UE is instructed to activate / enable PDCCH skipping and / or SSSG handover, the UE can perform PDCCH skipping and / or SSSG handover only when the UE is in DRX active time.

[0225] When the UE fails to successfully receive / decode / detect a DCI indication indicating at least one of SSSG handover, PDCCH skip (duration), and SCell sleep, for example, on a specific CORESET / search space set, the UE's behavior during SSSG handover, PDCCH skip duration, and SCell sleep should be determined. Specifically, the search space set can be configured to listen to the PDCCH to detect a specific DCI format on the active DL BWP of the PCell or SpCell (e.g., based on a common search space). If the UE is provided with a search space set to listen to the PDCCH to detect a specific DCI format in the active DL BWP of the PCell or SpCell, and the UE does not detect the specific DCI format, then the UE's behavior during SSSG handover, PDCCH skip duration, and SCell sleep should be determined.

[0226] In some implementations, the UE may not listen to the PDCCH to detect a specific DC I format during the DRX activity period.

[0227] In some implementations, the UE may not listen to the PDCCH used for DCI detection during all corresponding PDCCH listening times outside of the DRX activity time before the next long DRX cycle.

[0228] In some implementations, the UE may not listen to the PDCCH used for DCI detection during the measurement interval.

[0229] In some implementations, when the MAC entity is listening for PDCCH transmissions in the search space indicated by the recoverySearchSpaceId of the SpCell identified by C-RNTI while the ra-ResponseWindow is running, the UE may not listen for the PDCCH used to detect DCI.

[0230] In some implementations, the UE may not listen to the PDCCH used for DCI detection when it is performing a BWP handover.

[0231] In some implementations, if the UE is configured to listen for DCIs associated with at least one of SSSG handover, PDCCH skip duration, and SCell sleep in one or more search space sets, and the UE fails to receive / decode / detect the DCI, the UE may perform SSSG handover, and / or PDCCH skip (duration), and / or SCell sleep operations according to one or more of the following.

[0232] - The UE may not perform an SSSG handover (i.e., the UE may not change / switch the (current) SSSG ID).

[0233] - The UE can configure a first timer (or first period) via an RRC message. The first timer (or first period) can, for example, be started when the UE begins applying the SSSG ID, and is used by the UE to indicate the (longest) period for which the SSSG ID can be applied. When the UE does not receive / decode / detect a DCI, the UE may not change / switch the (current) SSSG ID until the first timer or first period expires.

[0234] -After the first timer or the first time period expires, the UE cannot change / do not switch the (current) SSSG ID.

[0235] - After the first timer or first time period expires, the UE can switch to the default SSSG (configured via RRC message).

[0236] - The UE can skip PDCCH (i.e., the UE can always listen to the search space set, and / or the UE can skip any PDCCH listening).

[0237] -UE cannot change the (current) PDCCH skip duration.

[0238] - The UE can configure a second timer (or second period) via RRC messages. The second timer (or second period) can be started, for example, when the UE begins to apply the (current) PDCCH skip duration and when it indicates the (longest) period for which the PDCCH skip duration can be applied.

[0239] - The second timer (or second time period) is not shorter (or less) than the (current) PDCCH skip duration and / or the PDCCH skip duration indicated by the DCI.

[0240] - The UE can always listen to the search space set, and / or the UE can not skip any PDCCH listening after the second timer (or second period) expires.

[0241] - After the second timer (or second time period) expires, the UE can change to the default PDCCH skip duration (configured via RRC message).

[0242] - After the second timer (or second time period) expires, the UE may not listen to any search space settings.

[0243] - The first timer (or first time period) can be the same timer (or the same time period) as the second timer (or second time period) in the received RRC message.

[0244] In some implementations, if the UE is configured to listen for DCIs associated with at least one of SSSG handover, PDCCH skip duration, and SCell sleep in one or more search space sets, and the UE fails to receive / decode / detect the DCI, the UE can determine whether to perform SSSG handover, and / or PDCCH skip (duration), and / or SCell sleep operations based on a specific configuration. For example, if the specific configuration indicates a first value (e.g., 0 or 1), the UE may need to perform SSSG handover and / or PDCCH skip (for a period of time), and / or SCell sleep operations once the UE fails to receive / decode / detect the DCI. On the other hand, if the configuration indicates a second value different from the first value (e.g., 1 or 0), the UE may not need to perform SSSG handover, and / or PDCCH skip (for a period of time), and / or SCell sleep operations once the UE fails to receive / decode / detect the DCI.

[0245] In some implementations, the DCI associated with at least one of SSSG switching, PDCCH skip duration, and SCell sleep can be DCI format 2_0 during DRX active time, and / or DCI format 2_6 during DRX active time, and / or DCI format 2_6 outside of DRX active time.

[0246] In some implementations, the DCI associated with at least one of SSSG switching, PDCCH skip duration, and SCell sleep can be a DCI format that does not require scheduling PDSCH 1_1.

[0247] In some implementations, the UE may configure a specific timer (or a specific duration) in the RRC message. The specific timer (or specific duration) may be used to indicate the (maximum) period during which one or more parameters related to PDCCH skipping, and / or SSSG handover, and / or SCell sleep can be applied.

[0248] In some implementations, the UE is configured to listen for DCI format 2_0 related to SSSG handover, and the UE fails to successfully receive / decode / detect DCI format 2_0. A default SSSG ID is configured in the RRC message. A timer related to SSSG handover is also configured in the RRC message. In this case, the UE can switch the SSSG ID to the default SSSG ID until the timer related to SSSG handover expires.

[0249] In some implementations, when the UE fails to successfully receive / decode / detect DCI format 2_6, the UE is configured to listen for DCI format 2_6 related to PDCCH skipping and SCell sleep during the DRX active period outside of the DRX active period. In this case, the UE can refrain from performing PDCCH skipping and SCell sleep during the active period.

[0250] Without needing to schedule PDSCH or PDSCH, DCI indication information can be configured to be associated with at least one of SSSG switching, PDCCH skipping (duration), and SCell hibernation.

[0251] In some implementations, if the UE receives / decodes / detects a DCI (e.g., DCI format 1_1 and / or DCI format 0_1), the DCI indicates that a PDCCH skip (duration) for scheduling PDSCH (or PUSCH) is not required, and two PDCCH skip durations are configured, the UE can perform a PDCCH skip using the first PDCCH skip duration of the two configured PDCCH skip durations. If the UE receives / decodes / detects a DCI (e.g., DCI format 1_1 and / or DCI format 0_1), the DCI indicates that a PDCCH skip (duration) for scheduling PDSCH (or PUSCH) is required, and two PDCCH skip durations are configured, the UE can perform a PDCCH skip using the second PDCCH skip duration of the two configured PDCCH skip durations. The first PDCCH skip duration may, for example, be longer than the second PDCCH skip duration.

[0252] In some implementations, if the UE receives / decodes / detects a DCI (e.g., DCI format 1_1 and / or DCI format 0_1) indicating at least one of SSSG handover, PDCCH skip duration, and SCell sleep function without PDSCH scheduling, and provides parameters related to the HARQ-ACK codebook, the UE generates a HARQ-ACK information bit for the DCI (e.g., DCI format 1_1 and / or DCI format 0_1), the HARQ-ACK information bit indicating at least one of the following: SSSG handover, PDCCH skip duration, SCell sleep function, and the value of the HARQ-ACK information bit is ACK.

[0253] In some cases, if the UE receives / decodes / detects a DCI format 1_1 indicating SSSG switching without scheduling a PDSCH, and provides parameters related to the HARQ-ACK codebook (e.g., pdsch-HARQ-ACK-Codebook=dynamic or enhancedDynamic-r16), the UE can generate HARQ-ACK information bits for the DCI format 1_1 indicating SSSG switching, and the value of the HARQ-ACK information bits is ACK.

[0254] In some cases, if the UE receives / decodes / detects a DCI format 1_1 indicating SSSG switching and PDCCH skipping for a period of time without needing to schedule PDSCH, and provides parameters related to the HARQ-ACK codebook (e.g., pdsch-HARQ-ACK-Codebook = dynamic or enhancedDynamic-r16), the UE can generate HARQ-ACK information bits for DCI format 1_1 and the value of the HARQ-ACK information bits is ACK.

[0255] Figure 7A and Figure 7B A flowchart illustrating a method performed by a UE to support a general design for PDCCH skipping and SSSG handover, according to one of the exemplary embodiments of this application.

[0256] Please see Figure 7A and Figure 7B In action S710, the UE may receive at least one of a first configuration associated with a first operation of SSSG handover and a second configuration associated with a second operation of PDCCH skipping. It should be noted that the operations (e.g., the first and second operations) are not limited to SSSG handover and PDCCH skipping. Those skilled in the art can provide different operational designs (e.g., different types of operations and / or different numbers of operations) based on similar concepts provided in this application.

[0257] In some implementations, the first configuration may be parameters related to SSSG handover, and the second configuration may be parameters related to PDCCH skipping. Specifically, parameters related to SSSG handover may include at least one of the following: one or more SSSG IDs, one or more SSSG numbers, one or more SSSG handover durations, one or more symbol numbers, and one or more offsets; and parameters related to PDCCH skipping may include at least one of the following: one or more PDCCH skipping durations, one or more CORESET IDs, one or more SSIDs, one or more symbol numbers, and one or more offsets. For example, the first configuration may include a first SSSG ID and a second SSSG ID. For example, the second configuration may include a first PDCCH skipping duration and a second PDCCH skipping duration.

[0258] In some implementations, at least one of the first configuration associated with the first operation (e.g., SSSG switching) and the second configuration associated with the second operation (e.g., PDCCH skipping) can be a table associated with the first and second operations. For example, the table can be Table 4 as shown below.

[0259] Table 4

[0260] index PDCCH skip duration SSSG ID 00(0) 3 2 01(1) 6 0 10(2) 4 0 11(3) 2 1

[0261] In some implementations, at least one of the first configuration and the second configuration may be received via one or more RRC messages, but this document is not limited to such messages.

[0262] Please see Figure 7A and Figure 7B In action S720, the UE may receive a DCI that includes a specific field associated with at least one of the first configuration and the second configuration.

[0263] In some implementations, the DCI can be one of DCI format 0_1, DCI format 0_2, DCI format 1_1, and DCI format 1_2. In some implementations, the UE can receive DCI format 2_0 after receiving the first configuration and the second configuration via RRC messages.

[0264] In some implementations, a specific field may be a newly added field or a reused field in the received DCI. This application does not limit the field size. In some cases, the field size may be related to the received first and second configurations. For example, the first and second configurations are provided by a table with 4 rows or entries (e.g., Table 4), and the field size may be at least 2 to cover all entries of the table. As another example, the first and second configurations are provided by a table with 8 rows or entries, and the field size may be at least 3 to cover all entries of the table. However, this application is not limited to this approach. In some other cases, the field size may be independent of the received first and second configurations.

[0265] Once the DCI is received and successfully decoded in action S720, the UE can perform the corresponding operation based on the value of a specific field of the DCI and the corresponding configuration.

[0266] If the value of a specific field is one of the values ​​in the first group, action S730 is entered, and the UE can therefore perform a first operation based on the value of the specific field and the first configuration; and if the value of a specific field is one of the values ​​in the second group, action S740 is entered, and the UE can therefore perform a second operation based on the value of the specific field and the second configuration.

[0267] For example, if the value of a specific field is “00” or “01”, action S730 is entered, and the UE can therefore perform SSSG handover based on the value of the specific field and the first configuration (e.g., the “SSSG ID” column in Table 4) (e.g., the first two rows of Table 4); and if the value of a specific field is “10” or “11”, action S740 is entered, and the UE can therefore perform PDCCH skipping based on the value of that specific field and the second configuration (e.g., the “PDCCH Skip Duration” column in Table 4) (e.g., the last two rows of Table 4).

[0268] In some implementations, a specific field may consist of a first part and a second part. The first part includes first information indicating at least one of a first operation and a second operation, and the second part includes second information indicating parameters of at least one of the first and second operations indicated in the first information. When the first information indicates a first operation, the second information indicates parameters related to SSSG switching; when the first information indicates a second operation, the second information indicates parameters related to PDCCH skipping; when the first information indicates both a first operation and a second operation, the second information indicates parameters related to both SSSG switching and PDCCH skipping.

[0269] In some implementations, a first sub-value (e.g., 0) in the first portion (e.g., MSB) of a specific field (e.g., a 2-bit field) indicates a first operation (e.g., SSSG switching), and a second sub-value (e.g., 1) in the first portion of the specific field indicates a second operation (e.g., PDCCH skipping). Thus, when the first portion of the specific field (i.e., the value in the first portion is the first sub-value) indicates an SSSG switching, the first sub-value (e.g., LSB) in the second portion of the specific field indicates a first SSSG ID, and the second sub-value in the second portion of the specific field indicates a second SSSG ID; when the first portion of the specific field (i.e., the value in the first portion is the second sub-value) indicates a PDCCH skipping, the first sub-value in the second portion of the specific field indicates the first PDCCH skipping duration, and the second sub-value in the second portion of the specific field indicates the second PDCCH skipping duration.

[0270] refer to Figure 7B According to Table 4, when the value in a specific field is "00" or "01", the process moves to the left into action S730, meaning that the value is the first value (e.g., "00" or "01") or the first part of the specific field (e.g., MSB) is the first sub-value (e.g., "0"). Therefore, only the first two rows in Table 4 are useful. When the value in a specific field is "00", action S731 is entered, meaning that the second part of the specific field (e.g., LSB) is the first sub-value (e.g., "0"), and the UE performs a first operation (e.g., SSSG switching) based on the first SSSG ID (e.g., 2) by referring to the first configuration (e.g., the "SSSG ID" column in Table 4). When the value in a specific field is "01", action S732 is entered, meaning that the second part of the specific field (e.g., LSB) is the second sub-value (e.g., "1"), and the UE performs a first operation (e.g., SSSG switching) based on the second SSSG ID (e.g., 0) by referring to the first configuration (e.g., the "SSSG ID" column in Table 4).

[0271] On the other hand, if the value in a specific field is "10" or "11", the process proceeds directly to action S740, meaning that the value is the first value (e.g., "10" or "11") or the first part of the specific field (e.g., MSB) is the first sub-value (e.g., "1"). Therefore, only the last two rows in Table 4 are useful. When the value in a specific field is "10", action S741 is initiated, meaning that the second part of the specific field (e.g., LSB) is the first sub-value (e.g., "0"), and the UE can perform a second operation (e.g., PDCCH skip) based on the first PDCCH skip duration (e.g., 4) by referring to the second configuration (e.g., the "PDCCH skip duration" column in Table 4). When the value in a specific field is “11”, action S742 is entered, which means that the second part (e.g., LSB) of the specific field is a second sub-value (e.g., “1”), and the UE can perform a second operation (e.g., PDCCH skip) based on the second PDCCH skip duration (e.g., 2) by referring to the second configuration (e.g., the “PDCCH skip duration” column in Table 4).

[0272] Therefore, the method described in this application can support a general design for two or more operations (e.g., SSSG switching, PDCCH skipping, etc.).

[0273] Figure 8 A block diagram of a node for wireless communication according to one of the exemplary embodiments of this application is shown. Figure 8 As shown, node 800 may include a transceiver 820, a processor 828, a memory 834, one or more presentation elements 838, and at least one antenna 836. Node 800 may also include a radio frequency (RF) band module, a base station communication module, a network communication module, a system communication management module, input / output (I / O) ports, I / O components, and a power supply. Figure 8 (Not explicitly shown). The components described herein can communicate directly or indirectly with each other via one or more buses 840. In some embodiments, node 800 may be an execution unit of the present application. Figure 1 The various functions of the UE or BS are shown in Figure 7.

[0274] Transceiver 820 has a transmitter 822 (e.g., transmit circuitry / transmit circuit) and a receiver 824 (e.g., receive circuitry / receive circuit). Transceiver 820 can be configured to transmit and / or receive time and / or frequency resource allocation information. In some embodiments, transceiver 820 can be configured to transmit in different types of subframes and time slots, including but not limited to usable, unusable, and flexibly usable subframe and time slot formats. Transceiver 820 can be configured to receive data and control channels.

[0275] Node 800 may include a variety of computer-readable media. Computer-readable media can be any available media accessible by Node 800, and includes both volatile (and non-volatile) media and removable (and non-removable) media. By way of example and not limitation, computer-readable media may include computer storage media and communication media. Computer storage media may include volatile (and / or non-volatile) and removable (and / or non-removable) media implemented using any method or technology for storing information such as computer-readable instructions, data structures, program modules, or data.

[0276] Computer storage media include RAM, ROM, EEPROM, flash memory (or other storage technologies), CD-ROM, Digital Versatile Disk (DVD) (or other optical disc storage devices), magnetic tape cartridges, magnetic tape, disk storage (or other magnetic storage devices), etc. Computer storage media do not include the transmission of data signals. Communication media may typically contain computer-readable instructions, data structures, program modules, or other data in modulated data signals (such as carrier waves or other transmission mechanisms), and include any information transmission medium. The term "modulated data signal" can refer to a signal having one or more characteristics set or altered in a manner that encodes information in the signal. By way of example, and not limitation, communication media include wired media (such as wired NW or direct wired connections) and wireless media (such as acoustic, RF, infrared, and other wireless media). Any previously disclosed combinations should also be included within the scope of computer-readable media.

[0277] Memory 834 may include a computer storage medium in the form of volatile and / or non-volatile memory. Memory 834 may be removable, non-removable, or a combination thereof. For example, memory 834 may include solid-state memory, hard disk drive, optical disk drive, etc. As shown in Figure 8, memory 834 may store computer-readable and / or computer-executable instructions 832 (e.g., software code or computer-executable program) configured to, when executed, cause processor 828 to perform the various functions described herein, for example, reference... Figure 1 See Figure 7. Alternatively, the computer-executable instructions 832 may not be executed directly by the processor 828, but may be configured to cause the node 800 (e.g., when compiled and executed) to perform the various functions described in this application.

[0278] Processor 828 (e.g., having processing circuitry) may include intelligent hardware devices, such as a central processing unit (CPU), microcontroller, ASIC, etc. Processor 828 may include memory. Processor 828 can process data 830 and instructions 832 received from memory 834, and information transmitted via transceiver 820, baseband communication module, and / or network communication module. Processor 828 can also process information to be transmitted to transceiver 820 for transmission via antenna 836, and to network communication module for transmission to CN.

[0279] One or more presentation components 838 may present data indications to a person or other device. Exemplary one or more presentation components 838 include display devices, speakers, printing components, vibrating components, etc.

[0280] Based on the above description, various techniques can be used to implement the concepts described in this application without departing from the scope of these concepts. Furthermore, although these concepts have been specifically described with reference to certain embodiments, those skilled in the art will recognize that changes in form and detail can be made without departing from the scope of these concepts. Therefore, the described embodiments should be considered illustrative rather than restrictive in all respects. It should be understood that this application is not limited to the specific embodiments described above, and many rearrangements, modifications, and substitutions of these embodiments are possible without departing from the scope of this disclosure.

Claims

1. A method executed by a user equipment (UE), characterized in that, The method includes: The first configuration associated with the first operation of receiving and switching the Search Space Cluster Group (SSSG) and the second configuration associated with the second operation of skipping the Physical Downlink Control Channel (PDCCH); Receive downlink control information (DCI), the DCI including a specific field associated with the first configuration or the second configuration, wherein the specific field is a 2-bit field and the value in the specific field is one of 00, 01, 10, and 11; and The first operation or the second operation is performed based on the value in the specific field, wherein... The first part of the specific field includes first information indicating at least one of the first operation and the second operation, and the second part of the specific field includes second information indicating the SSSG index or PDCCH skip duration. The first portion of the specific field includes the most significant bit of the specific field, and the second portion of the specific field includes the least significant bit of the specific field. The first sub-value in the first part of the specific field indicates the first operation, and the second sub-value in the first part of the specific field indicates the second operation.

2. The method as described in claim 1, characterized in that, The specific field indicates at least one of the SSSG index or the PDCCH skip duration.

3. The method as described in claim 1, characterized in that, The DCI includes one of DCI format 0_1, DCI format 0_2, DCI format 1_1, and DCI format 1_2.

4. The method as described in claim 1, characterized in that, The method further includes: When the value of the specific field is 01, the first operation is performed using the SSSG index; and If the value of the specific field is 10, the second operation is performed with the PDCCH skip duration.

5. A user equipment (UE), characterized in that, The UE includes: Processing circuitry; A transceiver coupled to the processing circuit; and A memory coupled to the processing circuit, the memory storing computer-executable instructions, which, when executed by the processing circuit, cause the UE to perform the method as described in any one of claims 1 to 4.

6. A base station (BS), characterized in that, The BS includes: Processing circuitry; A transceiver coupled to the processing circuit; and A memory coupled to the processing circuitry stores computer-executable instructions that, when executed by the processing circuitry, cause the BS to: Send a first configuration associated with a first operation of the handover search space cluster group (SSSG) and a second configuration associated with a second operation of skipping the physical downlink control channel (PDCCH) to the user equipment (UE); Send downlink control information (DCI) to the UE, the DCI including specific fields associated with the first configuration or the second configuration, wherein the DCI instructs the UE to: Perform the first operation or the second operation based on the value in the specific field. in, The specific field is a 2-bit field, and the value in the specific field is one of 00, 01, 10, and 11. The first part of the specific field includes first information indicating at least one of the first operation and the second operation, and the second part of the specific field includes second information indicating the SSSG index or PDCCH skip duration. The first portion of the specific field includes the most significant bit of the specific field, and the second portion of the specific field includes the least significant bit of the specific field. The first sub-value in the first part of the specific field indicates the first operation, and the second sub-value in the first part of the specific field indicates the second operation.

7. The BS as described in claim 6, characterized in that, The specific field indicates at least one of the SSSG index or the PDCCH skip duration.

8. The BS as described in claim 6, characterized in that, The DCI includes one of DCI format 0_1, DCI format 0_2, DCI format 1_1, and DCI format 1_2.

9. The BS as claimed in claim 6, characterized in that, The DCI is further configured such that the UE: When the value of the specific field is 01, the first operation is performed using the SSSG index; and If the value of the specific field is 10, the second operation is performed with the PDCCH skip duration.

Images