Methods, apparatus and systems for energy saving in wireless networks

Abstract

This disclosure generally relates to methods, apparatus, and systems for saving power consumption of a UE in wireless communication. A method performed by a UE includes: receiving a configuration message from a wireless communication node, the configuration message including configuration information associated with a set of Physical Downlink Control Channel (PDCCH) monitoring actions; receiving a control message from the wireless communication node, the control message indicating PDCCH monitoring actions from or associated with the set of PDCCH monitoring actions; and determining the PDCCH monitoring actions based on the control message.

Description

[0001] This divisional application is a divisional application of Chinese Patent Application No. 202180098728.0, filed on September 29, 2021, entitled "Method, Apparatus and System for Energy Saving in Wireless Networks". Technical Field

[0002] This disclosure relates generally to wireless communications, and more particularly to methods, apparatus and systems for saving power consumption of user equipment (UE). Background Technology

[0003] Energy efficiency is a key performance indicator in wireless communication networks. Controlling power consumption and reducing energy costs are crucial for the development and deployment of wireless communication networks. Energy-saving technologies play a vital role in achieving this goal. From the user's (UE) perspective, UE battery life has a significant impact on user experience. The ability to dynamically control UE power consumption while still meeting performance requirements is beneficial. Summary of the Invention

[0004] The present invention relates to a method, apparatus and system for saving power consumption of a user interface (UE) in wireless communication.

[0005] In some embodiments, a method performed by a UE in a wireless network is disclosed. The method may include: receiving a configuration message from a wireless communication node, the configuration message including configuration information associated with a set of Physical Downlink Control Channel (PDCCH) monitoring behaviors; receiving a control message from the wireless communication node, the control message indicating a PDCCH monitoring behavior from the PDCCH monitoring behavior set, or a PDCCH monitoring behavior associated with the PDCCH monitoring behavior set; and determining a PDCCH monitoring behavior based on the control message. In some embodiments, a method performed by a wireless communication node in a wireless network is disclosed. The method may include: sending a configuration message to a user equipment (UE) in the wireless network, the configuration message including configuration information associated with a set of Physical Downlink Control Channel (PDCCH) monitoring behaviors; and sending a control message to the UE, the control message indicating a PDCCH monitoring behavior from the PDCCH monitoring behavior set, or a PDCCH monitoring behavior associated with the PDCCH monitoring behavior set.

[0006] In some embodiments, there is a UE and / or a wireless communication node including a processor and a memory, wherein the processor is configured to read code from the memory and implement any of the methods described in any embodiment.

[0007] In some embodiments, a computer program product includes computer-readable program medium code stored thereon, which, when executed by a processor, causes the processor to implement any of the methods described in any embodiment.

[0008] The above embodiments and other aspects and alternatives to their implementation are described in more detail in the following drawings, description and claims. Attached Figure Description

[0009] Figure 1 An example wireless communication network is shown.

[0010] Figure 2 An example wireless network node is shown.

[0011] Figure 3 An example user device is shown.

[0012] Figure 4 Exemplary steps for controlling UE PDCCH monitoring behavior in a wireless communication network are shown.

[0013] Figure 5 An exemplary mapping of code points to PDCCH monitoring behavior is shown. Detailed Implementation

[0014] Wireless communication network

[0015] Figure 1 An exemplary wireless communication network 100 is illustrated, which includes a core network 110 and a radio access network (RAN) 120. The core network 110 also includes at least one mobility management entity (MME) 112 and / or at least one access and mobility management entity function (AMF). Figure 1 Other functions that may be included in the core network 110 are not shown. RAN 120 also includes multiple base stations, such as base stations 122 and 124. Base stations may include at least one evolved Node B (eNB) for 4G LTE, or a next-generation Node B (gNB) for 5G New Radio (NR), or any other type of signaling / receiving equipment, such as a UMTS Node B. eNB 122 communicates with MME 112 via the S1 interface. Both eNB 122 and gNB 124 may be connected to AMF 114 via the Ng interface. Each base station manages and supports at least one cell. For example, base station gNB 124 may be configured to manage and support cells 1, 2, and 3.

[0016] The gNB 124 may include a central unit (CU) and at least one distributed unit (DU). The CU and DU may coexist in the same location or may be located separately in different locations. The CU and DU may be connected via an F1 interface. Alternatively, for an eNB capable of connecting to a 5G network, it may similarly be divided into one CU and at least one DU, referred to as ng-eNB-CU and ng-eNB-DU, respectively. The ng-eNB-CU and ng-eNB-DU may be connected via a W1 interface.

[0017] The wireless communication network 100 may include one or more tracking areas. A tracking area may include a set of cells managed by at least one base station. For example, tracking area 1, labeled 140, includes cells 1, 2, and 3, and may also include more cells managed by other base stations. Figure 1 Cells not shown in the diagram. The wireless communication network 100 may also include at least one UE 160. The UE may select one of a plurality of cells supported by the base station to communicate with the base station via an over-the-air (OTA) wireless communication interface and resources, and may reselect a cell for communication as the UE 160 travels within the wireless communication network 100. For example, the UE 160 may initially select cell 1 to communicate with the base station 124, and then may reselect cell 2 at a later time. The cell selection or reselection by the UE 160 may be based on the wireless signal strength / quality in each cell and other factors.

[0018] The wireless communication network 100 can be implemented as, for example, a 2G, 3G, 4G / LTE, or 5G cellular communication network. Correspondingly, base stations 122 and 124 can be implemented as 2G base stations, 3G node Bs, LTE eNBs, or 5G NR gNBs. The UE 160 can be implemented as a mobile or fixed communication device capable of accessing the wireless communication network 100. The UE 160 can include, but is not limited to, mobile phones, laptops, tablets, personal digital assistants, wearable devices, Internet of Things (IoT) devices, MTC / eMTC devices, distributed remote sensor devices, roadside assistance devices, XR devices, and desktop computers. The UE 160 can also generally be referred to as a wireless communication device or a wireless terminal. The UE 160 can support sidelink communication to another UE via a PC5 interface.

[0019] Although the following description focuses on, Figure 1 The cellular wireless communication system shown is based on principles applicable to other types of wireless communication systems used for paging devices. These other wireless systems may include, but are not limited to, Wi-Fi, Bluetooth, ZigBee, and WiMax networks.

[0020] Figure 2An example of an electronic device 200 for implementing a network base station (e.g., a radio access network node), core network (CN), and / or operation and maintenance (OAM) is shown. Optionally, in one implementation, the example electronic device 200 may include wireless transmit / receive (Tx / Rx) circuitry 208 for transmitting / receiving communications with a UE and / or other base stations. Optionally, in one implementation, the electronic device 200 may also include network interface circuitry 209 for enabling the base station to communicate with other base stations and / or the core network, such as optical or wired interconnects, Ethernet, and / or other data transmission media / protocols. The electronic device 200 may optionally include an input / output (I / O) interface 206 for communicating with an operator, etc.

[0021] Electronic device 200 may also include system circuitry 204. System circuitry 204 may include processor(s) 221 and / or memory 222. Memory 222 may include operating system 224, instructions 226, and parameters 228. Instructions 226 may be configured for one or more processors 221 to perform functions of the network node. Parameters 228 may include parameters that support the execution of instructions 226. For example, parameters may include network protocol settings, bandwidth parameters, radio frequency mapping allocation, and / or other parameters.

[0022] Figure 3An example of an electronic device implementing a terminal device 300 (e.g., a user equipment (UE)) is shown. The UE 300 may be a mobile device, such as a smartphone or a mobile communication module located in a vehicle. The UE 300 may include some or all of the following: a communication interface 302, system circuitry 304, input / output interface (I / O) 306, display circuitry 308, and storage device 309. The display circuitry may include a user interface 310. The system circuitry 304 may include any combination of hardware, software, firmware, or other logic / circuit. The system circuitry 304 may be implemented, for example, using one or more system-on-chip (SoC), application-specific integrated circuit (ASIC), discrete analog and digital circuits, and other circuits. The system circuitry 304 may be part of an implementation of any desired functionality within the UE 300. In this regard, system circuitry 304 may include logic that, for example, facilitates the decoding and playback of music and video (e.g., MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV decoding and playback); runs applications; accepts user input; saves and retrieves application data; establishes, maintains, and terminates cellular phone calls or data connections for example, internet connections; establishes, maintains, and terminates wireless network connections, Bluetooth connections, or other connections; and displays relevant information on user interface 310. User interface 310 and input / output (I / O) interface 306 may include a graphical user interface, a touch-sensitive display, haptic feedback or other haptic outputs, voice or facial recognition inputs, buttons, switches, speakers, and other user interface elements. Additional examples of I / O interface 306 may include a microphone, video and still image camera, temperature sensor, vibration sensor, rotation and orientation sensor, headphone and microphone input / output jacks, universal serial bus (USB) connector, memory card slot, radiation sensor (e.g., infrared sensor), and other types of inputs.

[0023] See Figure 3The communication interface 302 may include radio frequency (RF) transmitting (Tx) and receiving (Rx) circuitry 316 that processes the transmission and reception of signals via one or more antennas 314. The communication interface 302 may include one or more transceivers. The transceiver may be a wireless transceiver that includes modulation / demodulation circuitry, a digital-to-analog converter (DAC), a shaping table, an analog-to-digital converter (ADC), filters, waveform shapers, filters, preamplifiers, power amplifiers, and / or other logic for transmission and reception via one or more antennas or (for some devices) via a physical (e.g., wired) medium. The transmitted and received signals may follow any of a variety of formats, protocols, modulations (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM), channels, bit rates, and encodings. As a specific example, the communication interface 302 may include a transceiver supporting transmission and reception under 2G, 3G, BT, WiFi, Universal Mobile Telecommunications System (UMTS), High-Speed ​​Packet Access (HSPA)+, 4G / LTE, and 5G standards. However, the techniques described below are applicable to other wireless communication technologies, whether from the 3rd Generation Partnership Project (3GPP), the GSM Association, 3GPP2, IEEE, or other partners or standards bodies.

[0024] See Figure 3 The system circuitry 304 may include one or more processors 321 and a memory 322. The memory 322 stores, for example, an operating system 324, instructions 326, and parameters 328. The processor 321 is configured to execute instructions 326 to perform the functionality desired by the UE 300. Parameters 328 can be provided and specify configuration and operational options for instructions 326. The memory 322 may also store any BT, WiFi, 3G, 4G, 5G, or other data that the UE 300 will send or has received via the communication interface 302. In various implementations, the system power of the UE 300 may be supplied by a power storage device such as a battery or transformer.

[0025] Physical Downlink Control Channel (PDCCH) Monitoring

[0026] The PDCCH supports data and signaling messages in wireless communication networks and plays a crucial role in various aspects, including downlink (DL) scheduling allocation, uplink (UL) scheduling authorization, power control, and paging indication. UEs need to continuously monitor the PDCCH in various ways. For example, a connected UE may periodically monitor the PDCCH based on Discontinuous Receive Mode (DRX). Alternatively, an idle or inactive UE may need to monitor the PDCCH for paging DCI, paging messages, system information updates, etc.

[0027] When monitoring the PDCCH, the UE needs to activate certain hardware, such as its RF chain, which increases power consumption. Therefore, reducing the frequency of PDCCH monitoring may help reduce power consumption. The base station can coordinate with the UE to achieve this goal. For example, the base station may be able to predict or estimate that the UE will have no downlink data / signals to monitor for a certain period of time. The base station can then notify the UE, so the UE can skip PDCCH monitoring for a certain period of time without increasing latency too much.

[0028] Search Space Group (SSSG) Switching

[0029] In a wireless communication network, a UE can be configured with one or more Search Space Groups (SSSGs). Each SSSG can include zero or more search space (SS) sets and can have its own characteristics. For example, each SSSG can be associated with different PDCCH monitoring periodicities and can have different numbers of search space sets. The UE can monitor the PDCCH based on one of the SSSGs. If the SSSG is configured with more search space sets and / or a shorter PDCCH monitoring periodicity, the UE may consume more power.

[0030] Based on the UE's service characteristics, the base station can instruct the UE to switch from one SSSG to another in order to meet specific performance requirements and minimize UE power consumption.

[0031] UE PDCCH monitoring behavior

[0032] This disclosure describes various UE PDCCH monitoring behaviors. These behaviors can be classified into two types: the first type involves UE PDCCH monitoring skipping (for a specific duration), and the second type involves UE SSSG handover.

[0033] Type 1 PDCCH monitoring behavior may include:

[0034] ● Deactivate PDCCH monitoring skip (i.e., deactivate the PDCCH monitoring skip feature), or monitor PDCCH according to the search space set configuration.

[0035] ●Skip PDCCH monitoring for a certain period of time.

[0036] In one implementation, deactivating PDCCH monitoring skipping can mean not triggering or activating the PDCCH monitoring skipping behavior. In another implementation, deactivating PDCCH monitoring skipping can mean that the UE monitors the PDCCH according to the search space set configuration.

[0037] There can be multiple durations for which a UE can skip PDCCH monitoring. Each duration corresponds to a UE PDCCH monitoring action. For example, multiple durations could include 5 milliseconds and 10 milliseconds. Each duration represents an action. For example, one action could be "skip PDCCH monitoring for 5 milliseconds," and another action could be "skip PDCCH monitoring for 10 milliseconds." Thus, a UE can be configured with a list of PDCCH monitoring actions to skip, each action corresponding to a specific duration.

[0038] The second type of PDCCH monitoring behavior may include:

[0039] ●Stop monitoring and searching the search space (SS) sets associated with SSSG#1 and SSSG#2 (if configured) as well as the SS set associated with SSSG#0.

[0040] ●Stop monitoring and searching the search space (SS) sets associated with SSSG#0 and SSSG#2 (if configured) as well as the SS set associated with SSSG#1.

[0041] ●Stop monitoring the search space (SS) set associated with SSSG#0 and SSSG#1, and stop monitoring the SS set associated with SSSG#2.

[0042] In this disclosure, the first type of PDCCH monitoring behavior may also be referred to as PDCCH monitoring skip behavior, and the second type of PDCCH monitoring behavior may also be referred to as SSSG switching behavior.

[0043] In this disclosure, there may be a first subset of PDCCH monitoring behaviors including a first type of PDCCH monitoring behavior and a second subset of PDCCH monitoring behaviors including a second type of PDCCH monitoring behavior. The PDCCH monitoring behavior set includes these two subsets of behaviors. In one implementation, when the UE begins monitoring the search space (SS) set associated with a specific SSSG, the UE may choose to stop monitoring the SS set associated with other SSSGs. Control UE PDCCH monitoring behavior

[0044] This disclosure describes various embodiments for controlling the monitoring behavior of the UE PDCCH. Figure 4 The illustration shows exemplary steps for a control process used in a high-level environment.

[0045] Step 401a: The UE may send its UE capability information related to PDCCH monitoring to the base station. The UE capability information can be used as a reference for the base station. The base station can refer to the UE capability information when configuring the UE's PDCCH monitoring behavior in step 401 and when instructing the UE to select a PDCCH monitoring behavior in step 402. For example, the UE capability information may indicate the maximum number of PDCCH monitoring behaviors that the UE can support, or the maximum number of bits that the UE can process to target / select a PDCCH monitoring behavior. For example, a low-end UE may only be able to process one bit for PDCCH monitoring behavior selection, while other UEs can process two or more bits. This step can be performed before or after step 401. Further details about this step will be described in later sections.

[0046] Step 401: The base station sends a configuration message to the UE to configure PDCCH monitoring behavior. The configuration message may include a list of PDCCH monitoring behaviors that need to be configured for the UE. This configuration method is called explicit configuration. The configuration message may also include a list of parameters related to the PDCCH monitoring behavior, and this parameter list implicitly indicates the PDCCH monitoring behavior. For example, the parameter list may include a list of PDCCH monitoring skip durations, such as 2 milliseconds, 5 milliseconds, and 10 milliseconds. Each duration corresponds to a PDCCH monitoring behavior that skips PDCCH monitoring within that duration. That is, these three PDCCH monitoring behaviors will be configured: skip PDCCH monitoring for 2 milliseconds, skip PDCCH monitoring for 5 milliseconds, and skip PDCCH monitoring for 10 milliseconds. SSSG handover behavior may be indicated by a list of parameters such as SSSG number / index. This configuration method is called implicit configuration because the PDCCH monitoring behavior is derived from these parameters. The list of PDCCH monitoring skip durations and the list of SSSG numbers / indexes can be sent to the UE in various ways. For example, they can be sent together in a single signaling message, or they can be sent separately in separate signaling messages.

[0047] Step 402: The UE has a list of PDCCH monitoring behaviors configured according to the configuration message in step 401. To trigger a change in PDCCH monitoring behavior, the base station sends a control message to the UE to indicate the specific PDCCH monitoring behavior that the UE needs to apply (or activate). The control message may take the form of a downlink control information (DCI) message. The PDCCH monitoring behavior indication information may be carried in the DCI field of the DCI message.

[0048] Step 403: The UE decodes the control message (e.g., the DCI field) to obtain the indicated PDCCH monitoring behavior. To decode the DCI field, the UE may first need to determine the bit width of the DCI field. In one implementation, the UE may determine the indicated PDCCH monitoring behavior based on the mapping between the code points of the DCI field and the PDCCH monitoring behavior. In this disclosure, the DCI field may include at least one bit, and the code point is the value represented by that at least one bit. The DCI field may represent multiple code points using different combinations of bits.

[0049] Step 404: The UE applies the indicated PDCCH monitoring action. For example, the UE may skip PDCCH monitoring associated with or for a duration specified in the indicated PDCCH monitoring action. For example, the UE may skip PDCCH monitoring for 5 milliseconds or 10 milliseconds, as determined by the indicated PDCCH monitoring action. As another example, the UE may begin monitoring the search space set associated with SSSG#2 and stop monitoring the search space sets associated with SSSG#0 and SSSG#1.

[0050] Further details are described below.

[0051] PDCCH monitoring behavior configuration

[0052] In one implementation, the base station can determine a list of UE PDCCH monitoring behaviors and send that list to the UE. Alternatively, the base station can determine a list of parameters related to the UE PDCCH monitoring behaviors. Several factors are involved in determining the list. These factors may include: ● UE capabilities;

[0053] ●Pre-defined values / rules; and

[0054] ● Bit width of the DCI field carrying an indicator for selecting PDCCH monitoring behavior.

[0055] These factors can be considered individually or in combination.

[0056] In one implementation, UE capabilities include a maximum number of indication bits for indicating the selection of PDCCH monitoring actions supported by the UE, or a number of indication bits (denoted as M) for indicating the selection of PDCCH monitoring actions supported by the UE. In one implementation, the number of PDCCH monitoring actions supported by the UE is no greater than 2. M Alternatively, the total number of configured SSSGs and / or the total PDCCH skip duration should not exceed 2. M .

[0057] In one implementation, the UE capability or predetermined value includes at least one of the following: ● The maximum number of PDCCH monitoring actions supported by the UE;

[0058] ● The maximum number of PDCCH skip durations supported by the UE; or ● The maximum number of SSSGs supported by the UE.

[0059] ● The number of PDCCH monitoring behaviors supported by the UE;

[0060] ● The number of PDCCH skip durations supported by the UE; or ● The number of SSSGs supported by the UE.

[0061] In one implementation, the number of configured UE PDCCH monitoring actions should be less than or equal to: the maximum number of PDCCH monitoring actions supported by the UE; or, the sum of the maximum number of PDCCH skip durations supported by the UE and the maximum number of SSSGs supported by the UE. In one implementation, the number of configured UE PDCCH monitoring skip actions should be less than or equal to the maximum number of PDCCH skip durations supported by the UE. In one implementation, the number of configured UESSSG handover actions should be less than or equal to the maximum number of SSSGs supported by the UE. In one implementation, the number of configured UE PDCCH monitoring actions should be less than or equal to: the number of PDCCH monitoring actions supported by the UE, or the sum of the number of PDCCH skip durations supported by the UE and the number of SSSGs supported by the UE. In one implementation, the number of configured UE PDCCH monitoring skip actions should be less than or equal to the number of PDCCH skip durations supported by the UE. In one implementation, the number of configured UE SSSG handover actions should be less than or equal to the number of SSSGs supported by the UE.

[0062] In one implementation, the configuration of UE PDCCH monitoring behavior is based on the bit width of the DCI field carrying an indicator for selecting PDCCH monitoring behavior (see [link]). Figure 2 (Step 402 in the example). For example, if the bit width of the DCI field is configured to 1 bit, and the UE capability indication supports two PDCCH monitoring skip behaviors, then only one or two PDCCH skip monitoring durations can be configured. As another example, if the bit width of the DCI field is configured to 1 bit, then even if the UE capability indication supports three SSSG handover behaviors, only two SSSGs can be configured. For example, two SSSGs can be configured as "switching to" SSSGs. In one implementation, the UE can be configured with different types of SSSGs. For example, a first type of SSSG can exist. The first type of SSSG can include at least one of the following:

[0063] ● SSSGs that do not have a search space set configured (e.g., empty SSSG);

[0064] ● Dormant SSSG;

[0065] ● The UE can stop monitoring the SSSG associated with the PDCCH for a certain period of time, or before the timer expires; or

[0066] ● SSSG associated with an index greater than or equal to 2 (indicating that there are more than 2 SSSGs in the SSSG set, with SSSG indices starting from 0).

[0067] In one implementation, it is not expected that both the first type SSSG and PDCCH skip durations will be configured for the UE.

[0068] In one implementation, it is not expected that the first type of SSSG will be configured with the same timer value as the PDCCH skip duration.

[0069] In one implementation, if the first condition is met, it is not expected to configure a certain type of PDCCH monitoring behavior:

[0070] This specific type of PDCCH monitoring behavior includes deactivating PDCCH monitoring skipping.

[0071] The first condition can be associated with at least one of the following: higher-layer signaling, or UE capability. The first condition is satisfied if the following conditions are met:

[0072] ● At least two SSSGs must be configured;

[0073] ● PDCCH skip duration not configured;

[0074] ● Configure at least one default SSSG. In some embodiments, the default SSSG means the SSSG in which the UE monitors the PDCCH if no PDCCH monitoring behavior indication is received; or

[0075] ● Configure the first type of SSSG.

[0076] In one implementation, if the bit width of the DCI field is 1, then only one type of PDCCH monitoring behavior can be configured for the UE.

[0077] In one implementation, if the DCI field has a bit width of 1 and the UE capability indicator supports SSSG handover behavior, then two SSSG handover behaviors can be configured for the UE.

[0078] Control signal mapping

[0079] like Figure 4As shown, in step 403, the UE needs to determine the indicated PDCCH monitoring action based on a control message (e.g., a DCI message). In one implementation, the DCI field of the DCI message may carry indication information. The UE can map the value of the DCI field (e.g., code point (CP)) to a specific PDCCH monitoring action. In one implementation, mapping can also be based on a bitmap formed by the bits of the DCI field.

[0080] Figure 5 An example of using code points to map UE PDCCH monitoring behavior is shown. In this example, the DCI field has 2 bits (i.e., the bit width is 2 bits) and there are 4 code points based on these 2 bits. The UE is configured with 6 PDCCH monitoring behaviors. Each duration represents a PDCCH monitoring skip duration, and each SSSG represents an SSSG handover behavior. Figure 5 As shown, four of the six PDCCH monitoring actions are mapped to code points. Various embodiments for mapping are disclosed in this disclosure.

[0081] In some embodiments, each SSSG may be associated with or indicated by an SSSG index. For example... Figure 5 As shown, index 2 can indicate SSSG 2. Furthermore, the maximum SSSG index can also indicate, for example, the number of SSSGs configured in the SSSG list or in the second PDCCH monitoring behavior subset.

[0082] Several factors are involved when a UE maps indications in a control message to specific PDCCH monitoring behaviors. These factors include:

[0083] ● Bit width of the DCI field;

[0084] ●High-level signaling;

[0085] ● Multiple PDCCH monitoring behaviors configured for the UE (e.g., configured via RRC signaling from the base station);

[0086] ● Multiple PDCCH monitoring behavior types configured for the UE.

[0087] ●UE capabilities;

[0088] ●Predefined rules; or

[0089] ●Predefined conditions.

[0090] These factors can be considered individually or in combination.

[0091] In order to decode the DCI field, the UE may first need to obtain the bit width of the DCI field.

[0092] In one implementation, if the number of PDCCH monitoring actions configured for the UE is M, then the bit width of the DCI field can be determined as follows: A is an integer greater than 0.

[0093] In one implementation, if the number of first-type PDCCH monitoring actions configured for the UE is M, and the number of second-type PDCCH monitoring actions configured for the UE is N, then the bit width of the DCI field can be determined as follows: A is an integer greater than 0.

[0094] In one implementation, if only one type of PDCCH monitoring behavior is configured for the UE, the bit width can be determined to be 1. If two types of PDCCH monitoring behavior are configured for the UE, the bit width can be determined to be 2.

[0095] In one implementation, the bit width of the DCI field can be determined by the UE capabilities. UE capabilities include the maximum number of indication bits (i.e., DCI bits) used to indicate the selection of PDCCH monitoring behaviors supported by the UE. For example, the bit width of the DCI field is determined by... To determine: where A is the total number of configured PDCCH monitoring actions, and B is the maximum number of indicator bits used to indicate the selection of PDCCH monitoring actions supported by the UE.

[0096] DCI can have different formats. The first type of DCI can include DCI with DCI format 0-2, or DCI with DCI format 1-2. The second type of DCI can include DCI with DCI format 1-1, or DCI with DCI format 0-1.

[0097] In one implementation, if the DCI is a Type 1 DCI, the bit width of the DCI field can be A bits. If the DCI is a Type 2 DCI, the bit width of the DCI field can be B bits. A and B are predetermined values, or determined based on higher-layer signaling and the UE's UE capabilities.

[0098] In one implementation, if the DCI is a Type 1 DCI, the bit width of the DCI field can be 1 bit. If the DCI is a Type 2 DCI, the bit width of the DCI field can be max(2,B) bits, where B is the maximum number of indication bits used to indicate the selection of PDCCH monitoring behavior supported by the UE, which can be indicated or reported by the UE capability.

[0099] In one implementation, if the DCI is a Type 1 DCI, the bit width of the DCI field can be 1 bit. If the DCI is a Type 2 DCI, the bit width of the DCI field can be min(A,B) bits, where A is the bit width configured by higher-layer signaling, and B is the maximum number of indication bits used to indicate the selection of PDCCH monitoring behavior supported by the UE.

[0100] In one implementation, DCI code points can be mapped to PDCCH monitoring actions based on the order of the parameter list in the configuration message. For example, if the configuration message specifies a parameter list related to UE PDCCH monitoring actions, DCI code points can be mapped to PDCCH monitoring actions based on the order of the elements in the list. For instance, code point value m is mapped to the m-th PDCCH monitoring action in the list.

[0101] In one implementation, DCI code points can be mapped to PDCCH monitoring behaviors. For example, a UE can be configured with M PDCCH skip durations and no SSSG. If M is less than 4, then the first code point in the DCI (e.g., the minimum code point or a code point with all zeros) signifies the behavior of "deactivating PDCCH monitoring skip". Other code point values ​​can be mapped to PDCCH skip durations. For example, each configured PDCCH skip duration can be associated with an index. The code point value m can indicate the PDCCH skip duration with index m-1. If M = 4, then the code point value m indicates the PDCCH skip duration with index m. The index associated with the PDCCH skip duration can be indicated by higher-layer signaling (e.g., RRC signaling configuring PDCCH monitoring behavior to the UE).

[0102] Table 1 below shows an example PDCCH monitoring behavior mapping where the UE is configured with only one PDCCH monitoring skip duration. It should be understood that the "Deactivate PDCCH monitoring skip" behavior does not need to be explicitly configured in the UE PDCCH monitoring behavior list.

[0103] Table 1: PDCCH Monitoring Behavior Mapping

[0104] Code Point PDCCH monitoring behavior 0 Deactivate PDCCH monitoring (skip) 1 Skip PDCCH monitoring during the first duration

[0105] Table 2 below shows another example of PDCCH monitoring behavior mapping, where the UE is configured with four PDCCH monitoring skip durations. Not shown in Table 5, each duration can be associated with an index, and code points can be mapped to the index.

[0106] Table 2: PDCCH Monitoring Behavior Mapping

[0107]

[0108]

[0109] In one implementation, the UE is configured with M (M is an integer) PDCCH skip durations, and the UE may or may not be configured with SSSG handover behavior. If one code point remains after indicating all PDCCH monitoring behaviors, the remaining code point can be mapped to "deactivate PDCCH monitoring skip". Table 3 below shows an example with two remaining code points.

[0110] Table 3: PDCCH Monitoring Behavior Mapping

[0111] Code Point PDCCH monitoring behavior 00 (Remaining CP) Deactivate PDCCH monitoring (skip) 01 Skip PDCCH monitoring during duration 1 10 Skip PDCCH monitoring during duration 2 11 (Remaining CP) Deactivate PDCCH monitoring (skip)

[0112] Table 4 below shows an example with one remaining code point.

[0113] Table 4: PDCCH Monitoring Behavior Mapping

[0114] Code Point PDCCH monitoring behavior 00 Switch SSSG to SSSG 0 01 Switch from SSSG to SSSG 1 10 Skip PDCCH monitoring during duration 1 11 (Remaining CP) Deactivate PDCCH monitoring (skip)

[0115] In one implementation, the UE is configured with M PDCCH monitoring skip durations and N SSSG handover actions, where M and N are integers. The "Deactivate PDCCH monitoring skip" action is not mapped. That is, no code points in the DCI field are mapped to this action. Alternatively, if at least one SSSG handover action is configured, and the total number of configured PDCCH monitoring actions is greater than 4, the "Deactivate PDCCH monitoring skip" action is not mapped.

[0116] In one implementation, when mapping PDCCH monitoring behaviors, one type of UE PDCCH monitoring behavior is mapped first, followed by another type. For example, the first type of PDCCH monitoring behavior is mapped first, and then the second type is mapped. The mapping order can be predetermined or configured by higher-layer signaling. Table 5 below shows an example of mapping the second type of PDCCH monitoring behavior first, and then mapping the first type of PDCCH monitoring behavior.

[0117] Table 5: PDCCH Monitoring Behavior Mapping

[0118] Code Point PDCCH monitoring behavior 00 Switch SSSG to SSSG 0 01 Switch from SSSG to SSSG 1 10 Skip PDCCH monitoring during duration 1 11 (Remaining CP) Skip PDCCH monitoring without mapping / or deactivate it

[0119] In one implementation, the UE is configured with M PDCCH skip durations and N SSSG handover actions, and the bit width of the DCI field is 2. The first two code points (i.e., "00" and "01") can be mapped to one or two PDCCH monitoring skip actions, while the remaining two code points (i.e., "10" and "11") can be mapped to one or two SSSG handover actions.

[0120] In one implementation, the UE is configured with M PDCCH skip durations and N SSSG handover actions, and the DCI field has a bit width of 2 (i.e., supports 4 code points). The first I code points (e.g., I=3) can be mapped to one type of PDCCH monitoring action, and the remaining code points (e.g., I=1) can be mapped to another type of PDCCH monitoring action.

[0121] In one implementation, the mapping method can be configured by higher-layer signaling. For example, Media Access Control-Control Unit (MACCE) signaling can indicate mapping information, such as methods for mapping DCI code points to PDCCH monitoring actions. As another example, each PDCCH monitoring action can be associated with an index. This index can be assigned by the base station for the corresponding PDCCH monitoring action when configuring the PDCCH monitoring action for the UE. Code points in the DCI field can indicate the corresponding PDCCH monitoring action based on the index. For example, the code point value m can indicate the PDCCH monitoring action with index m, where m is a non-negative integer. Indexes can also be assigned according to predetermined rules. As yet another example, RRC signaling can indicate mapping information, such as methods for mapping DCI code points to PDCCH monitoring actions.

[0122] In one implementation, if the total number of PDCCH monitoring actions configured for the UE exceeds the maximum number of mappings that the DCI field can support (e.g., due to the limited number of bits in the DCI field), some PDCCH monitoring actions may not be mapped.

[0123] In some embodiments, the mapping method may be based on at least one of the following: higher-layer signaling, UE capabilities, or predefined information.

[0124] In one implementation, the maximum number of bit widths supported by the UE capability indication (i.e., the bit width of the DCI field used for mapping the indication) is 1. The code point can indicate two Type 1 PDCCH monitoring actions, such as a "deactivate PDCCH monitoring skip" action and a "skip PDCCH monitoring for a certain duration" action. The code point can also indicate two Type 2 PDCCH monitoring actions.

[0125] In one implementation, if the maximum number of bit widths supported by the UE capability indication (i.e., the bit width of the DCI field used for mapping the indication) is 1, then at most one of two specific SSSG handover actions can be mapped. These two specific SSSG handover actions can be predetermined or configured via higher-layer signaling or an SSSG other than the default SSSG. Alternatively, a skip PDCCH monitoring action and an SSSG handover action may not be mapped.

[0126] In one implementation, more than one type of DCI can be used to indicate PDCCH monitoring behavior. For example, a first type of DCI can be used to indicate a mapping to a first type of PDCCH monitoring behavior, and a second type of DCI can be used to indicate a mapping to a second type of PDCCH monitoring behavior. The type of DCI can be determined by its DCI format.

[0127] In one implementation, multiple PDCCH monitoring behavior sets can be configured for the UE. For example, the configuration information may include information for two PDCCH monitoring behavior sets, and the configuration information may be sent to the UE in the same message or in different messages. Different types of DCIs can be used to indicate PDCCH monitoring behaviors in different PDCCH monitoring behavior sets. The type of DCI can be based on the DCI format. For example, a first type of DCI can be used to indicate the mapping of PDCCH monitoring behaviors in one PDCCH monitoring behavior set, and a second type of DCI can be used to indicate the mapping of PDCCH monitoring behaviors in another PDCCH monitoring behavior set.

[0128] In one implementation, predefined information or UE capabilities can indicate the maximum number of PDCCH skip durations that can be mapped, and / or the maximum number of SSSG handover actions that can be mapped. For example, the UE is configured with 2 PDCCH skip durations and 3 SSSG handover actions. According to the predefined information, the maximum number of PDCCH skip durations that can be mapped is 1, and the maximum number of SSSG handover actions that can be mapped is 3. It is possible to map only one PDCCH skip duration (e.g., the first one) and all 3 SSSG handover actions.

[0129] In one implementation, the bit width of the DCI field can be indicated to the UE via RRC signaling. The RRC signaling may include the same RRC signaling that configures the UE's PDCCH monitoring behavior, or other RRC signaling.

[0130] In one implementation, the method for mapping DCI code points to PDCCH monitoring behavior is through predefined rules (e.g., predefined by the protocol).

[0131] In one implementation, RRC signaling can indicate that the DCI field has a bit width of 1. The code point of the DCI field can indicate two Type 1 PDCCH monitoring actions, such as "deactivate PDCCH monitoring skip" and "skip PDCCH monitoring for a period of time" (if they are configured to the UE). The code point can also indicate two Type 2 PDCCH monitoring actions, if they are configured to the UE.

[0132] In one implementation, if the RRC signaling indicates that the bit width of the DCI field is 1, then two specific SSSG handover actions may not be mapped. These two specific SSSG handover actions can be predetermined, configured via higher-layer signaling, or be SSSGs other than the default SSSG. Alternatively, a skip PDCCH monitoring action and an SSSG handover action may not be mapped.

[0133] In one implementation, it is not possible to simultaneously support the mapping of the first type of PDCCH monitoring behavior and the first type of SSSG.

[0134] In one implementation, if the total number of PDCCH monitoring behaviors is greater than 4, it is not possible to simultaneously support the mapping of the first type of PDCCH monitoring behavior and the first type of SSSG.

[0135] In one implementation, if the total number of PDCCH monitored behaviors is greater than 4, then the first type of SSSG may not be mapped.

[0136] In one implementation, a subset of bits in the DCI field indicates a subset of PDCCH monitoring behaviors, while another subset of bits indicates the PDCCH monitoring behaviors within that subset. Table 6 below shows an example with 2 bits in the DCI field.

[0137] Table 6: PDCCH Monitoring Behavior Mapping

[0138]

[0139] Mapping Example

[0140] In this disclosure, various examples of PDCCH monitoring behavior mapping are described below.

[0141] Example 1

[0142] In this example, the UE is configured with 3 monitoring skip durations (corresponding to 3 actions) and 3 SSSGs (for switching to the 3 actions of the 3 SSSGs). The bit width of the DCI field is 2. Among the 3 SSSGs, SSSG 2 is the first type SSSG. The first type SSSG was described in the previous section.

[0143] Table 6 below illustrates the two mapping methods. Since SSSG 2 is a first-type SSSG, neither method involves a mapping switch to SSSG 2.

[0144] Table 7: PDCCH Monitoring Behavior Mapping

[0145]

[0146] Example 2

[0147] Example 2 is similar to Example 1, except that SSSG 2 is not a first-type SSSG. Table 7 below shows the three mapping methods.

[0148] Table 8: PDCCH Monitoring Behavior Mapping

[0149]

[0150] In method 3, SSSG is switched to SSSG 2, which is mapped to binary code point 10.

[0151] Example 3

[0152] In this example, the UE is configured with 4 PDCCH monitoring skip durations (corresponding to 4 actions) and 2 SSSGs (for switching to 2 actions using 2 SSSGs). The DCI field has a bit width of 2. The mapping method maps the 2 SSSGs and 2 PDCCH monitoring skip durations as shown in Table 8 below.

[0153] Table 9: PDCCH Monitoring Behavior Mapping

[0154] Code Point Mapping 00 Switch SSSG to SSSG 0 01 Switch from SSSG to SSSG 1 10 PDCCH monitoring skipped within duration 1 11 PDCCH monitoring skipped during duration 2

[0155] UE capability signaling

[0156] See Figure 4 In step 4a, the UE can send its UE capabilities to the base station via a message (e.g., UE capability signaling).

[0157] This signaling can be used with various conditions of DCI to instruct PDCCH monitoring behavior.

[0158] For example, the condition includes the DCI format. This signaling can indicate whether the UE supports a specific DCI format for instructing PDCCH monitoring behavior. The DCI format can include:

[0159] ●DCI 0_1;

[0160] ●DCI 1_1;

[0161] ●DCI 0_2; or

[0162] ●DCI 1_2;

[0163] This signaling can indicate whether the UE supports using a DCI with format DCI 0_1 or DCI 1_1, or a DCI with format DCI 0_2 or DCI 1_2, to indicate the second type of PDCCH monitoring behavior.

[0164] For example, the condition may include a specific field in the DCI, such as the Scell ​​sleep indication field. This signaling can indicate whether the Scell ​​sleep indication field in the DCI can be used for indication.

[0165] For example, the conditions include the functionality of the DCI. For instance, the signaling could also indicate whether a DCI excluding a data scheduling indication can be used for that indication.

[0166] The above conditions can be used individually or in combination. Furthermore, the above conditions can be used for Type I PDCCH monitoring activities and / or Type II PDCCH monitoring activities.

[0167] Example UE capability signaling

[0168] The following list shows various examples of what UE capability signaling can indicate:

[0169] ●Does the UE support the selection of PDCCH monitoring actions from the second subset of PDCCH monitoring actions indicated by DCI 0_1 or / and DCI 1_1?

[0170] ●Does the UE support the selection of PDCCH monitoring actions from the second subset of PDCCH monitoring actions indicated by DCI 0_2 or / and DCI 1_2?

[0171] ●Does the UE support the use of the Scell ​​sleep indication field to select PDCCH monitoring behavior from the second subset of PDCCH monitoring behaviors?

[0172] ●Does the UE support the selection of PDCCH monitoring behavior from the second subset of PDCCH monitoring behavior using a DCI that includes an Scell ​​sleep indication field but does not have a data scheduling indication? ●Does the UE support the selection of PDCCH monitoring behavior from the first subset of PDCCH monitoring behavior indicated by DCI 0_1 or / and DCI 1_1?

[0173] ●Does the UE support the selection of PDCCH monitoring actions from the first subset of PDCCH monitoring actions indicated by DCI 0_2 or / and DCI 1_2?

[0174] ●Does the UE support the use of the Scell ​​sleep indication field to select PDCCH monitoring behavior from the first subset of PDCCH monitoring behaviors?

[0175] ●Does the UE support the selection of PDCCH monitoring behavior from the first PDCCH monitoring behavior subset using a DCI that includes an Scell ​​sleep indication field but does not have a data scheduling indication? ●Does the UE support the selection of PDCCH monitoring behavior from the first and second PDCCH monitoring behavior subsets indicated by DCI 0_1 and / or DCI 1_1?

[0176] ●Whether the UE supports the selection of PDCCH monitoring actions from the first and second PDCCH monitoring action subsets indicated by DCI 0_2 and / or DCI 1_2;

[0177] ●Does the UE support the use of the Scell ​​sleep indication field to select PDCCH monitoring behavior from the first and second subsets of PDCCH monitoring behavior?

[0178] ●Does the UE support the selection of PDCCH monitoring behavior from the first and second PDCCH monitoring behavior subsets using DCI that includes the Scell ​​sleep indication field but does not have a data scheduling indication?

[0179] ●Does the UE support empty SSSG or dormant SSSG? Or

[0180] ● When the UE is instructed to skip PDCCH monitoring and / or switch to "sleep" / "empty" SSSG, does the UE support performing PDCCH monitoring for Hybrid Automatic Repeat Request (HARQ) retransmissions during the retransmission period?

[0181] The dormant SSSG includes the SSSG associated with the search space set. When associated with a dormant SSSG, the UE does not monitor the PDCCH for a certain period of time (or before the timer expires).

[0182] An empty SSSG means that the SSSG is not associated with any search space set.

[0183] In one implementation, in addition to using the Scell ​​sleep indication field to indicate Scell ​​sleep indication information, several other DCI fields may be used. These fields include at least one of the following: modulation and coding scheme field for transport block 1, new data indicator field for transport block 1, redundant version field for transport block 1, HARQ process number field, (multiple) antenna port field, and DMRS sequence initialization field. For example, if the DCI does not carry a data scheduling indication, these fields can be used for Scell ​​sleep indication.

[0184] Example of code point mapping with PDCCH monitoring behavior

[0185] This section describes various examples of code point mapping. A code point refers to a code point in the DCI field that carries information indicating PDCCH monitoring behavior.

[0186] In one implementation, if the bit width of the DCI field is 1 and SSSG 0 is configured, the code point can be mapped to at least the SSSG monitoring behavior associated with SSSG 0.

[0187] In one implementation, if the bit width of the DCI field is 1, then the code point can be mapped to a PDCCH monitoring action that belongs to the same subset of PDCCH monitoring actions.

[0188] In one implementation, if two types of PDCCH monitoring behaviors are configured, the code point can be mapped to at least the SSSG monitoring behavior associated with SSSG 0 and the SSSG monitoring behavior associated with SSSG 1.

[0189] In one implementation, if two types of PDCCH monitoring behaviors are configured, code points can be mapped to either the SSSG monitoring behavior associated with SSSG0 or the deactivation of the PDCCH monitoring skip behavior.

[0190] In one implementation, code points can be mapped to PDCCH monitoring behaviors that belong to a subset of PDCCH monitoring behaviors supported by the UE and indicated by the UE capabilities.

[0191] In one implementation, if at least one PDCCH is configured to monitor skip duration, the first type of SSSG may not be mapped.

[0192] In one implementation, code points can only be mapped to deactivate PDCCH monitoring skip behavior if a subset of the first type of PDCCH monitoring behavior is configured.

[0193] In one implementation, code points in the DCI field can be mapped to M PDCCH monitoring actions, where M is an integer and not greater than a predetermined value.

[0194] The foregoing description and accompanying drawings provide specific example embodiments and implementations. However, the described subject matter can be embodied in a variety of different forms, and therefore, the covered or claimed subject matter is intended to be construed as not being limited to any of the example embodiments set forth herein. A fairly broad scope of the subject matter is intended to be claimed or covered. For example, the subject matter can be specifically embodied as a method, apparatus, component, system, or non-transitory computer-readable medium for storing computer code. Therefore, embodiments can take the form, for example, hardware, software, firmware, storage medium, or any combination thereof. For example, the above-described method embodiments can be implemented by a component, apparatus, or system including a memory and a processor by executing computer code stored in the memory.

[0195] Throughout the specification and claims, terms may have nuanced meanings implied or implied in the context beyond their explicitly stated meanings. Similarly, the phrase "in one embodiment / implementation" as used herein does not necessarily refer to the same embodiment, and the phrase "in another embodiment / implementation" as used herein does not necessarily refer to a different embodiment. For example, the claimed subject matter is intended to include combinations of all or some of the exemplary embodiments.

[0196] Generally, terms can be understood, at least in part, based on their use in context. For example, terms such as “and,” “or,” or “and / or,” as used herein, can include a variety of meanings that can depend, at least in part, on the context in which they are used. Typically, “or,” when used to relate a list such as A, B, or C, is intended to mean A, B, and C (used herein in an inclusive sense) and A, B, or C (used herein in an exclusive sense). Additionally, the term “one or more,” as used herein, depends at least in part on the context and can be used to describe any feature, structure, or characteristic in a singular sense, or a combination of features, structures, or characteristics in a plural sense. Similarly, terms such as “a,” “an,” or “the” can be understood to convey either a singular or a plural usage, at least in part on the context. Furthermore, the term “based on” can be understood to not necessarily convey an exclusive set of factors, but may allow for additional factors that are not necessarily explicitly described, again at least in part on the context.

[0197] References to features, advantages, or similar language throughout this specification do not imply that all features and advantages achievable with this solution should be included or included in any single implementation thereof. Rather, references to features and advantages should be understood as indicating that a particular feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of this solution. Therefore, the discussion of features and advantages throughout this specification, as well as similar language, may, but do not necessarily, refer to the same embodiments.

[0198] Furthermore, the features, advantages, and characteristics described in this solution can be combined in any suitable manner in one or more embodiments. Based on the description herein, those skilled in the art will recognize that this solution can be practiced without one or more specific features or advantages of a particular embodiment. In other instances, additional features and advantages that may not be present in all embodiments of this solution may be recognized in certain embodiments.

Claims

1. A method executed by a user equipment (UE), comprising: A configuration message is received from a wireless communication node, the configuration message including configuration information associated with a set of physical downlink control channel (PDCCH) monitoring behaviors, wherein the configuration message includes radio resource control (RRC) messages; The wireless communication node receives a downlink control information (DCI) message, the DCI message including a DCI field, wherein the value of the DCI field is mapped to a PDCCH monitoring action associated with the set of PDCCH monitoring actions; The bit width of the DCI field is determined based on the configuration message and the DCI format of the DCI message. The DCI format includes one of the following: DCI 0_1, DCI 1_1, DCI 0_2, or DCI 1_2. The PDCCH monitoring behavior is determined based on the DCI message; as well as Apply the aforementioned PDCCH monitoring behavior, The set of PDCCH monitoring behaviors mentioned above includes: The first subset of PDCCH monitored behaviors includes at least one of the following: Do not skip PDCCH monitoring; or a list of PDCCH monitoring skip actions, where each PDCCH monitoring skip action is associated with a skip duration; and The second subset of PDCCH monitoring behaviors includes a list of SSSG monitoring behaviors for the search space set. And the configuration information mentioned therein includes at least one of the following: The set of durations associated with the first subset of PDCCH monitoring behaviors; or the set of SSSGs associated with the second subset of PDCCH monitoring behaviors.

2. The method according to claim 1, wherein if the bit width of the DCI field is 1, then one or more values ​​in the DCI field are mapped to PDCCH monitoring behaviors belonging to the same subset of PDCCH monitoring behaviors.

3. The method according to claim 1, wherein, When both types of PDCCH monitoring behaviors are configured, the value in the DCI field is mapped to at least the SSSG monitoring behavior associated with SSSG 0 and the SSSG monitoring behavior associated with SSSG 1.

4. The method according to claim 1, wherein, When M PDCCH skip durations are configured and no SSSG is configured, all zero values ​​in the DCI field indicate that PDCCH monitoring is not skipped, where M is an integer less than 4.

5. The method according to claim 1, further comprising: In response to the configuration of two types of PDCCH monitoring behavior to the UE, the bit width of the DCI field is determined to be 2.

6. The method according to claim 1, wherein: When the value is 00, the value indicates that monitoring of the search space set SSS associated with the second SSSG is stopped, and monitoring of the search space set SSS associated with the first SSSG is stopped. When the value is 01, the value indicates that monitoring of the SSS associated with the first SSSG is stopped, and monitoring of the SSS associated with the second SSSG is started. When the value is 10, the value indicates that PDCCH monitoring for a pre-configured duration should be skipped; as well as When the value is 11, the value is not mapped to any PDCCH monitoring behavior.

7. A method performed by a wireless communication node in a wireless network, comprising: A configuration message is sent to the user equipment (UE) in the wireless network. The configuration message includes configuration information associated with the physical downlink control channel (PDCCH) monitoring behavior set and includes radio resource control (RRC) messages. as well as A downlink control information (DCI) message is sent to the UE. The DCI message includes a DCI field, the value of which is mapped to a PDCCH monitoring action associated with the PDCCH monitoring action set. The configuration message and the DCI format of the DCI message are used to determine the bit width of the DCI field. The DCI format includes one of the following: DCI0_1, DCI1_1, DCI0_2, or DCI1_2. The DCI message triggers the UE to determine and apply the PDCCH monitoring action. The set of PDCCH monitoring behaviors mentioned above includes: The first subset of PDCCH monitored behaviors includes at least one of the following: Do not skip PDCCH monitoring; or A list of PDCCH monitoring skip behaviors, where each PDCCH monitoring skip behavior is associated with a skip duration; and The second subset of PDCCH monitoring behaviors includes a list of SSSG monitoring behaviors for the search space set. And the configuration information mentioned therein includes at least one of the following: The set of durations associated with the first subset of PDCCH monitoring behaviors; or The set of SSSGs associated with the second subset of PDCCH monitoring behaviors.

8. The method of claim 7, wherein if the bit width of the DCI field is 1, then one or more values ​​in the DCI field are mapped to PDCCH monitoring behaviors belonging to the same subset of PDCCH monitoring behaviors.

9. The method according to claim 7, wherein, When both types of PDCCH monitoring behaviors are configured, the value in the DCI field is mapped to at least the SSSG monitoring behavior associated with SSSG 0 and the SSSG monitoring behavior associated with SSSG 1.

10. The method according to claim 7, wherein, When M PDCCH skip durations are configured and no SSSG is configured, all zero values ​​in the DCI field indicate that PDCCH monitoring is not skipped, where M is an integer less than 4.

11. The method of claim 7, further comprising: In response to the configuration of two types of PDCCH monitoring behavior to the UE, the bit width of the DCI field is determined to be 2.

12. The method according to claim 7, wherein: When the value is 00, the value indicates that monitoring of the search space set SSS associated with the second SSSG is stopped, and monitoring of the search space set SSS associated with the first SSSG is stopped. When the value is 01, the value indicates that monitoring of the SSS associated with the first SSSG is stopped, and monitoring of the SSS associated with the second SSSG is started. When the value is 10, the value indicates that PDCCH monitoring for a pre-configured duration should be skipped; as well as When the value is 11, the value is not mapped to any PDCCH monitoring behavior.

13. A user equipment (UE) comprising a memory for storing computer instructions and a processor in communication with the memory, wherein when the processor executes the computer instructions, the processor is configured to cause the UE to: Receive configuration messages from wireless communication nodes in a wireless network. The configuration messages include configuration information associated with a set of physical downlink control channel (PDCCH) monitoring behaviors, wherein the configuration messages include radio resource control (RRC) messages. The wireless communication node receives a downlink control information (DCI) message, the DCI message including a DCI field, wherein the value of the DCI field is mapped to a PDCCH monitoring action associated with the set of PDCCH monitoring actions; The bit width of the DCI field is determined based on the configuration message and the DCI format of the DCI message. The DCI format includes one of the following: DCI 0_1, DCI 1_1, DCI 0_2, or DCI 1_2. The PDCCH monitoring behavior is determined based on the DCI message; as well as Apply the aforementioned PDCCH monitoring behavior, The set of PDCCH monitoring behaviors mentioned above includes: The first subset of PDCCH monitored behaviors includes at least one of the following: Do not skip PDCCH monitoring; or a list of PDCCH monitoring skip actions, where each PDCCH monitoring skip action is associated with a skip duration; and The second subset of PDCCH monitoring behaviors includes a list of SSSG monitoring behaviors for the search space set. And the configuration information mentioned therein includes at least one of the following: The set of durations associated with the first subset of PDCCH monitoring behaviors; or The set of SSSGs associated with the second subset of PDCCH monitoring behaviors.

14. A wireless communication node comprising a memory for storing computer instructions and a processor in communication with the memory, wherein when the processor executes the computer instructions, the processor is configured to cause the wireless communication node to: Send a configuration message to a user equipment (UE) in a wireless network. The configuration message includes configuration information associated with a set of physical downlink control channel (PDCCH) monitoring behaviors and includes radio resource control (RRC) messages. as well as A downlink control information (DCI) message is sent to the UE. The DCI message includes a DCI field, the value of which is mapped to a PDCCH monitoring action associated with the PDCCH monitoring action set. The configuration message and the DCI format of the DCI message are used to determine the bit width of the DCI field. The DCI format includes one of the following: DCI0_1, DCI1_1, DCI0_2, or DCI1_2. The DCI message triggers the UE to determine and apply the PDCCH monitoring action. The set of PDCCH monitoring behaviors mentioned above includes: The first subset of PDCCH monitored behaviors includes at least one of the following: Do not skip PDCCH monitoring; or A list of PDCCH monitoring skip behaviors, where each PDCCH monitoring skip behavior is associated with a skip duration; and The second subset of PDCCH monitoring behaviors includes a list of SSSG monitoring behaviors for the search space set. And the configuration information mentioned therein includes at least one of the following: The set of durations associated with the first subset of PDCCH monitoring behaviors; or The set of SSSGs associated with the second subset of PDCCH monitoring behaviors.

Images