Method executed by user equipment and user equipment

Abstract

The present disclosure provides a method executed by a user equipment (UE) and a UE. The method comprises: determining the size of a bitmap for a UE in a low-power wake-up signal (LP-WUS); determining the sequence number corresponding to each serving cell in the bitmap; and for each serving cell, on the basis of the sequence number and from a received LP-WUS, detecting an indication for the serving cell to determine whether PDCCH detection should be performed in the serving cell.

Description

Methods executed by user equipment and user equipment Technical Field

[0001] This disclosure relates to the field of wireless communication technology, and more specifically to a method for determining downlink resources performed by a user equipment and a corresponding user equipment. Background Technology

[0002] The introduction in this section can help to better understand the various aspects of this disclosure. Therefore, the statements in this section should be read in this context and should not be construed as an admission of what is prior art or what is not prior art.

[0003] In 5G systems, besides latency, reliability, and availability, the energy efficiency of user equipment (UEs) is also a key factor. Typically, UEs consume tens of milliwatts in RRC idle or inactive states and hundreds of milliwatts in RRC connected states. Depending on the application scenario, UEs may need to be charged weekly or daily. Therefore, further reducing UE power consumption and extending battery life are essential for improving energy efficiency and achieving a better user experience. For devices using micro-batteries or those where charging is inconvenient, such as sensors, automatic controllers, and wearable devices, where standby time may be 1-2 weeks or longer, improving their energy efficiency is even more critical.

[0004] User equipment (UE) can typically save power using Discontinuous Reception (DRX). To ensure connectivity, UE needs to periodically wake up in each DRX cycle to detect the control channel. Even when there is no data transmission for the UE, there is periodic power consumption. If the UE could only wake up when there is a service transmission requirement, its power consumption would be significantly reduced. Therefore, the UE can be configured with a low-power secondary receiver to detect the wake-up signal (LP-WUS) sent by the base station. The UE's primary receiver can remain in a low-power state (e.g., sleep mode) until the low-power receiver receives the LP-WUS signal and wakes up the primary receiver to perform the corresponding data processing. This allows the UE's service processing requirements to be met with lower power consumption. To achieve this design goal, several problems need to be solved in the system, such as how to determine the magnitude of relevant indication information and its correspondence to each serving cell when the UE supports multiple serving cells, and how to perform corresponding processing in each serving cell according to the relevant indications. Summary of the Invention

[0005] To address at least some of the aforementioned problems, this disclosure provides a method and a user equipment performed by a user equipment, enabling the UE to correctly determine an indication for whether to perform PDCCH detection for each serving cell.

[0006] According to this disclosure, a method performed by a user equipment (UE) is proposed, comprising: determining the size of a bitmap for the UE in a low-power wake-up signal LP-WUS; determining the sequence number of each serving cell in the bitmap; and for each serving cell, detecting an indication for that serving cell from the received LP-WUS based on the sequence number to determine whether to perform PDCCH detection in that serving cell.

[0007] Preferably, the size of the bitmap is determined according to at least one of the following:

[0008] - The number of serving cells configured with the enable flag;

[0009] - The number of serving cells where BWP / CORESET / Search Space / PDCCH / PDSCH / PUSCH are configured with the enable flag;

[0010] - The number of serving cells indicated by LP-WUS, based on the serving cell bit map;

[0011] - The number of serving cells indicated by LP-WUS, based on the list of serving cell numbers;

[0012] - The number of packets in the serving cell indicated by LP-WUS, based on the serving cell packet sequence number; and

[0013] -Based on the serving cell packet number, use the maximum packet number of the serving cell indicated by LP-WUS.

[0014] Preferably, the sequence number of each serving cell in the bitmap is determined according to at least one of the following:

[0015] - The service cell number of the service cell configured with the enable flag;

[0016] - The BWP / CORESET / serving cell number of the serving cell with the enable flag configured;

[0017] -Based on the bit map of the serving cell, use the serving cell number of the serving cell indicated by LP-WUS;

[0018] - Based on the serving cell sequence list, use the sequence number of the serving cell in the list indicated by LP-WUS; and

[0019] - Use the serving cell's packet number indicated by LP-WUS, based on the serving cell's packet number.

[0020] Additionally, according to this disclosure, a method performed by a user equipment (UE) is proposed, comprising: determining a serving cell indicated by a bit in an application low-power wake-up signal (LP-WUS) for the UE; and determining, based on the received bit in the LP-WUS for the UE, whether to perform PDCCH detection in the determined serving cell.

[0021] Preferably, the serving cell indicated in the application LP-WUS is determined according to at least one of the following:

[0022] - Serving cells configured with enable flags;

[0023] - The serving cell where the BWP / CORESET / Search Space / PDCCH / PDSCH / PUSCH is configured with the enable flag;

[0024] -Based on the serving cell bit map, use the serving cell indicated by LP-WUS;

[0025] - Based on the list of serving cell numbers, use the serving cell indicated by LP-WUS; and

[0026] - Use the serving cell indicated by LP-WUS based on the serving cell group number.

[0027] Furthermore, according to this disclosure, a method executed by a user equipment (UE) is proposed, comprising: determining the size of the number of bits occupied by the code point for the UE in the low-power wake-up signal LP-WUS; determining the code point value corresponding to each serving cell; and for each serving cell, detecting an indication for that serving cell from the received LP-WUS based on the code point value to determine whether to perform PDCCH detection in that serving cell.

[0028] Preferably, the size of the bits occupied by the code point is determined according to at least one of the following:

[0029] - The number of serving cells configured with the enable flag;

[0030] - The number of serving cells where BWP / CORESET / Search Space / PDCCH / PDSCH / PUSCH are configured with the enable flag;

[0031] - The number of serving cells indicated by LP-WUS, based on the serving cell bit map;

[0032] - The number of serving cells indicated by LP-WUS, based on the list of serving cell numbers;

[0033] - The number of serving cell packets indicated by LP-WUS, based on the serving cell packet sequence number;

[0034] - Based on the serving cell's packet sequence number, use the maximum packet sequence number of the serving cell indicated by LP-WUS; and

[0035] -Based on the number of different service cell combinations.

[0036] Preferably, the code point value corresponding to each serving cell is determined according to at least one of the following:

[0037] - The service cell number of the service cell configured with the enable flag;

[0038] - The BWP / CORESET / serving cell number of the serving cell with the enable flag configured;

[0039] -Based on the bit map of the serving cell, use the serving cell number of the serving cell indicated by LP-WUS;

[0040] - Based on the serving cell sequence list, use the sequence number of the serving cell in the list indicated by LP-WUS; and

[0041] - Use the serving cell's packet number indicated by LP-WUS, based on the serving cell's packet number.

[0042] Furthermore, according to this disclosure, a user equipment is proposed, comprising: a processor; and a memory storing instructions, wherein the instructions, when executed by the processor, perform the methods described above.

[0043] Invention Effects

[0044] According to this disclosure, the UE can correctly determine the indication for whether to perform PDCCH detection for each serving cell. Attached Figure Description

[0045] The above and other features of this disclosure will become more apparent from the following detailed description taken in conjunction with the accompanying drawings, wherein:

[0046] Figure 1 is a flowchart illustrating a method performed by a user equipment according to an embodiment of the present disclosure.

[0047] Figure 2 is a flowchart illustrating a second method performed by a user equipment according to an embodiment of the present disclosure.

[0048] Figure 3 is a flowchart illustrating method three performed by a user equipment according to an embodiment of the present disclosure.

[0049] Figure 4 is a block diagram illustrating the user equipment (UE) involved in this disclosure. Detailed Implementation

[0050] The present disclosure will now be described in detail with reference to the accompanying drawings and specific embodiments. It should be noted that the present disclosure should not be limited to the specific embodiments described below, which are provided merely as examples to convey the scope of the subject matter to those skilled in the art. Furthermore, for the sake of simplicity, detailed descriptions of well-known technologies not directly related to the present disclosure have been omitted to prevent confusion in understanding the present disclosure.

[0051] Generally, unless a different meaning is clearly given and / or implied in the context of its use, all terms used in this disclosure shall be interpreted according to their ordinary meaning in the relevant art. Unless expressly stated otherwise, all references to an element, device, apparatus, component, part, step, etc., shall be publicly interpreted as referring to at least one instance of that element, device, apparatus, component, part, step, etc. Unless it must be explicitly described that a step follows or precedes another step and / or implicitly imply that a step must follow or precede another step, the steps of any method in the embodiments of this disclosure need not be performed in the exact order disclosed. Where appropriate, any feature of any embodiment of this disclosure may be applied to any other embodiment. Similarly, any advantage of any embodiment may be applied to any other embodiment, and vice versa.

[0052] The following description uses 5G / NR mobile communication systems and their subsequent evolutions as example application environments to specifically describe several implementations according to this disclosure. However, it should be noted that this disclosure is not limited to the following implementations, but is applicable to many other wireless communication systems, such as communication systems after 5G and 4G and 3G mobile communication systems before 5G, 802.11 wireless networks, etc.

[0053] The following describes some of the terms used in this disclosure. Unless otherwise specified, the terms used in this disclosure are as defined herein. The terms given in this disclosure may be named differently in LTE, LTE-Advanced, LTE-Advanced Pro, NR and later or other communication systems, but a uniform terminology is used in this disclosure. When applied to a specific system, the terms used in the corresponding system can be substituted.

[0054] 3GPP: 3rd Generation Partnership Project

[0055] LTE: Long Term Evolution

[0056] NR: New Radio, New Wireless, New Air Interface

[0057] UE: User Equipment

[0058] gNB: NR base station

[0059] BWP: Bandwidth Part

[0060] SFN: System frame number

[0061] OFDM: Orthogonal Frequency Division Multiplexing

[0062] SCS: Sub-carrier spacing

[0063] RB: Resource Block

[0064] TDD: Time Division Duplexing

[0065] FDD: Frequency Division Duplexing

[0066] CSI: Channel State Information

[0067] DCI: Downlink Control Information

[0068] CRC: Cyclic Redundancy Check

[0069] QCL: Quasi-co-location

[0070] HARQ: Hybrid Automatic Repeat Request.

[0071] CORESET: Control resource set.

[0072] MIB: Master Information Block

[0073] SIB: System Information Block

[0074] SSB: SS / PBCH block, Synchronization Signal / Physical Broadcast Channel Block

[0075] SRS: Sounding Reference Signal

[0076] DMRS: Demodulation Reference Signal

[0077] CSI-RS: Channel State Information Reference Signal

[0078] RACH: Random-access channel

[0079] PBCH: Physical broadcast channel

[0080] PUCCH: Physical Uplink Control Channel

[0081] PUSCH: Physical Uplink Shared Channel

[0082] PRACH: Physical random-access channel

[0083] PDSCH: Physical downlink shared channel

[0084] PDCCH: Physical downlink control channel

[0085] UL-SCH: Uplink Shared Channel

[0086] DL-SCH: Downlink Shared Channel

[0087] C-RNTI: Cell Radio Network Temporary Identifier

[0088] P-RNTI: Paging RNTI, Temporary Identifier for Paging Wireless Network

[0089] RA-RNTI: Random Access RNTI, Temporary Identifier for Random Access Wireless Networks

[0090] CS-RNTI: Configured Scheduling RNTI, a temporary identifier for configuring and scheduling wireless networks.

[0091] SI-RNTI: System Information RNTI, Temporary Identifier for Wireless Networks

[0092] TC-RNTI: Temporary C-RNTI, Temporary Cell Radio Network Identifier

[0093] LP-WUS: Low Power Wake-Up Signal

[0094] RRM: Radio Resource Management

[0095] RRC: Radio Resource Control

[0096] TCI: Transmission Configuration Indicator

[0097] MSB: Most Significant Bit

[0098] LSB: Least Significant Bit

[0099] The following is a description of the technologies associated with this disclosure. Unless otherwise specified, the same terms in the specific embodiments have the same meaning as in the associated technologies.

[0100] It is worth noting that the User Equipment (UE) involved in this disclosure refers to any end device that accesses a communication network and receives services from it, such as a smartphone, mobile phone, tablet computer, mobile station, access terminal, sensor, wearable device, etc. This disclosure may also use terms such as "user" and "terminal" to describe the methods used by the user equipment, without specifically distinguishing or limiting these terms from the user equipment (UE). Network equipment refers to devices that communicate with the user equipment, including but not limited to wireless base stations, gNBs, eNBs, wireless access points, wireless repeaters, and user equipment with repeater capabilities. This disclosure may use a wireless base station as one form of network equipment implementation, but other forms of network equipment can be easily used in specific implementations.

[0101] When using carrier aggregation (CA), two or more component carriers (CCs) are aggregated together. Depending on the UE's capabilities, a UE can simultaneously receive or transmit on one or more CCs. For example, a UE without CA capability can only receive on one CC associated with a serving cell and transmit on one CC; a UE with single TA (timing advance) capability can simultaneously receive / transmit on multiple CCs associated with serving cells using the same TA; a UE with multi-TA capability can simultaneously receive / transmit on multiple CCs, which can be associated with serving cells using different TAs, and so on.

[0102] When CA is configured, the UE has only one RRC connection with the network. During RRC connection establishment / re-establishment / handover, one serving cell provides NAS (Non-Access Stratum Service) mobility information, and during RRC connection re-establishment / handover, another serving cell provides security input. This serving cell can be called the primary cell (PCell). Depending on the UE's capabilities, secondary cells (SCells) can be configured simultaneously with the PCell, forming a serving cell group (or serving cell set). A configured serving cell group always contains one PCell and one or more SCells. The base station can add / delete / reconfigure SCells via RRC signaling. Additionally, UEs that do not support CA can have only one PCell.

[0103] Each serving cell uses a serving cell number. For example, the serving cell number of a PCell is always 0, while other SCells use an integer value to uniquely identify the serving cell.

[0104] The base station can configure the parameters of PCell and SCell for the UE through the serving cell parameters. For example, the uplink and downlink CC parameters used by the serving cell can be configured through ServingCellConfigCommon, and one or more uplink and downlink BWP parameters used by the serving cell can be configured through ServingCellConfig. The parameters used on the BWP, such as CORESET, search space, PDCCH, PDSCH, PUSCH, etc., are used by the UE to perform service transmission on the relevant serving cell.

[0105] When a UE supports Dual Connectivity (DC), it can be configured with two serving cell groups: a master cell group (MCG) and a secondary cell group (SCG). Each cell group contains a MAC entity, a set of logical channels, a primary cell, and one or more SCells. The primary cell of an SCG is also called a Pscell (Primary SCG Cell).

[0106] Spcell (Special Cell) is also used to represent the PCell when the UE is configured with DC. That is, when the UE is configured with DC, Spcell refers to the PCell of MCG or the Pscell of SCG; otherwise, Spcell is the PCell.

[0107] If a MAC entity has configured one or more SCells, the base station can activate and deactivate these configured SCells. The UE can determine the activation or deactivation of a SCell using the following methods:

[0108] - Receive SCell activation / deactivation MAC CE (MAC control element), and determine the activation / deactivation of SCell according to the instructions in it;

[0109] - Receive enhanced SCell activation / deactivation MAC CE and determine the activation / deactivation of the SCell according to the instructions therein;

[0110] - The base station configures a timer sCellDeactivationTimer for a SCell (unless the SCell is configured with PUCCH), and the associated SCell is deactivated when the timer expires.

[0111] - The base station configures a SCell with a parameter sCellState. If this parameter is configured, the associated SCell will be active once the SCell is configured.

[0112] - Receives scg-State, where the SCell of SCG is deactivated.

[0113] For a single SCell, a dormant BWP can be configured using the dormantBWP-Id parameter in RRC signaling. A UE entering or leaving a dormant BWP on a SCell can be achieved through BWP handover based on indications in the PDCCH. The base station can use the PDCCH to send a dormancy indication to indicate whether a SCell is dormant or not. For example, a "0" in the DCI bitmap indicates that the active BWP of the SCell is set as a dormant BWP, and a "1" indicates that the SCell uses the current BWP as the active BWP if the current BWP is not a dormant BWP; or the first active BWP configured by the higher layer is set as the active BWP if the current BWP is a dormant BWP. If the active BWP of a SCell is a dormant BWP, the UE can stop certain processes on that SCell, such as not detecting the PDCCH on that BWP, not detecting the PDCCH scheduling that BWP, not receiving the DL-SCH on that BWP, etc. Spcells or SCells configured with PUCCH do not use the hibernation BWP configuration (that is, they do not determine the hibernation of the SCell based on the hibernation instruction of the DCI).

[0114] In NR networks, after a User Equipment (UE) establishes a radio connection with a base station, it can enter connected state (RRC_CONNECTED) and transmit data according to the base station's configuration or scheduling. The base station can configure the DRX (Discontinuous Receive) function via RRC signaling to control the detection of PDCCHs using RNTIs of certain MAC entities by the connected-state UE. For example, it can control the UE to only detect relevant PDCCHs when certain timers are running. These RNTIs include, but are not limited to, C-RNTI, CI-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI, AI-RNTI, SL-RNTI, SL-CS-RNTI, SL Semi-Persistent Scheduling V-RNTI, cellDTRX-RNTI, etc. The DRX used for connected-state UEs can also be called C-DRX. When a connected UE is configured with DRX by the base station, the MAC entity can perform discontinuous PDCCH detection according to the relevant DRX procedure for all active serving cells. The UE can determine the scheduling of relevant PDSCH or PUSCH, or the activation or deactivation of relevant PDSCH or PUSCH transmissions, etc., based on the DCI in the detected PDCCH.

[0115] A UE's MAC entity can configure up to two DRX groups for multiple serving cells. Each DRX group uses some independent parameters and some common parameters. When two DRX groups are configured, the UE can determine that each serving cell belongs to one of the two DRX groups. When the RRC does not configure a second DRX group, the UE has only one DRX group, and all serving cells belong to this DRX group.

[0116] When a UE uses DRX, the parameters configured / used independently by each DRX group include drx-onDurationTimer and drx-InactivityTimer. DRX groups also use several shared parameters, such as drx-SlotOffset, which determines the starting position of drx-onDurationTimer in a DRX cycle; drx-LongCycleStartOffset, which determines the cycle period and starting offset of a long DRX cycle; and downlink and uplink retransmission timers drx-RetransmissionTimerDL and drx-RetransmissionTimerUL, etc.

[0117] The base station configures the drx-onDurationTimer parameter to determine the timing duration of the drx-onDurationTimer. The UE can start the drx-onDurationTimer in each DRX cycle, and the timing length is the value indicated by the drx-onDurationTimer parameter. For ease of description, the first time slot in each DRX cycle where the UE can start the drx-onDurationTimer is referred to as the C-DRX time slot, or simply the DRX time slot.

[0118] When a base station configures DRX for a UE, the cells in the DRX group are considered active when the following conditions are met:

[0119] - The drx-onDurationTimer or drx-InactivityTimer configured for this DRX group is running; or

[0120] -drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, or drx-RetransmissionTimerSL are running on any serving cell in the DRX group; or

[0121] - The timer ra-ContentionResolutionTimer or msgB-ResponseWindow for Random Access (RA) is running; or

[0122] - A scheduling request has been sent via PUCCH and is pending.

[0123] - A PDCCH indicating that a new transmission related to C-RNTI has not yet been received, after successful reception of RAR, and that RAR is related to a preamble not based on contention; etc.

[0124] If a DRX group is active, the UE can detect the PDCCH on the serving cell of that DRX group and perform related processing based on the information in the detected PDCCH, such as downlink / uplink data transmission, HARQ feedback, HARQ retransmission, etc.

[0125] According to the relevant DRX operation procedures, the UE needs to perform PDCCH detection during the DRX activation time. If the activation time, determined by the relevant parameters configured by the base station, is long, the UE will need to detect the PDCCH even if there is no data transmission, resulting in unnecessary power consumption. If the activation time is short, the UE has fewer opportunities to transmit data, leading to increased data transmission latency. In addition, some SCells may not support or be suitable for using sleep or deactivation methods to reduce power consumption.

[0126] To further reduce UE power consumption and latency, a feasible method is for the user equipment to use a low-power auxiliary receiver (LR) to detect the wake-up signal (low-power WUS, LP-WUS) sent by the base station. When there is no data transmission, the user equipment's main radio (MR) remains in sleep mode to minimize power consumption. When data needs to be transmitted, the base station notifies the user equipment via LP-WUS. When the user equipment detects the indication carried in LP-WUS, the UE wakes up the MR and performs corresponding data processing. LP-WUS may also be referred to as WUS in the following text, without further elaboration. In UE implementation, different or shared components may be used to perform related processing for LR and MR; for example, LR may be used to detect LP-WUS, and MR may be used to detect PDCCH. For ease of description, this disclosure uses UE to uniformly describe the relevant LR or MR usage methods and processing procedures. In specific implementations, the UE can call the relevant LR or MR components for execution according to specific requirements.

[0127] A single LP-WUS signal may contain indication information related to multiple or multiple groups of user equipment (UEs), such as different UE IDs, indication bits for multiple UEs or UE groups, or sequences of different UEs or UE groups. UEs within a UE group may partially or completely share indications for that UE group. UEs can determine the indication information in the LP-WUS corresponding to their own UE or UE group using a certain method. For example, when LP-WUS provides indication information using a bitmap method, the UE can determine the bit positions of the indication information for its own UE or UE group based on relevant parameters, and use a bit "1" to indicate that the UE detects the PDCCH or starts a relevant timer in the relevant process; and use a bit "0" to indicate that the UE does not detect the PDCCH or start a relevant timer in the relevant process. As another example, when LP-WUS provides indication information using a sequence method, the LP-WUS contains a specific sequence related to the UE, used to indicate that the UE detects the PDCCH or starts a relevant timer in the relevant process; the LP-WUS does not contain a specific sequence related to the UE, used to indicate that the UE does not detect the PDCCH or start a relevant timer in the relevant process. In actual systems, there may be other methods for determining the indication information of the user equipment or user group, which are not specifically limited here. In this disclosure, for the sake of simplicity, the indication of the UE according to the LP-WUS is the same as the indication of the UE or UE group in the LP-WUS.

[0128] LP-WUS signals can be transmitted using OOK (On-Offkeying) waveforms to reduce receiver complexity. For compatibility with existing NR equipment, LP-WUS signals can be generated using methods compatible with OFDM symbols, such as multi-carrier OOK. In this case, the bandwidth of the LP-WUS signal can contain an integer number of OOK symbols within the length of an OFDM symbol, such as 1 / 2 / 4 / 8 / 16, making it easy for the base station to transmit signals with different waveforms. Therefore, the time-domain length of the time-domain resources used by LP-WUS can also be described using parameters such as the number of OFDM symbols, time slots, and frames.

[0129] When a base station uses LP-WUS to instruct the UE on related processing, it can use the OOK signal to transmit the relevant LP-WUS, for example, using the ON and OFF states of the OOK signal to represent "1" and "0". Simultaneously, when the base station transmits the relevant OOK signal, it can also transmit some additional information on the resources used by the OOK signal. For example, when transmitting the symbol "1" of OOK, a specific sequence can be used, and the UE can determine different indication information based on different sequences. For simplicity, the information determined by the UE on an LP-WUS based on the ON / OFF state of the OOK symbol can be designated as first information, and the information determined based on the ON / OFF state of non-OOK symbols can be designated as second information. The UE can report its capabilities to the base station, for example, that it can detect the first information (referred to as capability 1) according to LP-WUS, or that it can detect both the first and second information simultaneously according to LP-WUS (referred to as capability 2). If this disclosure does not explicitly state whether it is based on the first or second information, the UE can determine the indication in the relevant LP-WUS based on the first and / or second information. Furthermore, the first and second information may transmit partially or entirely the same information.

[0130] When a connected UE uses LP-WUS, it may employ different procedures to coordinate with other channels and configurations, depending on network configuration and instructions. For example, when the UE is configured with DRX, it may detect LP-WUS before the C-DRX time slot and determine whether to initiate a DRX cycle's drx-onDurationTimer based on the indications in the LP-WUS; or it may detect LP-WUS outside the DRX activation time and determine whether to detect PDCCH based on the indications in the LP-WUS, thereby reducing data transmission latency while maintaining low UE power consumption; or it may detect LP-WUS during the DRX activation time and determine whether to detect PDCCH and receive PDSCH based on the indications in the LP-WUS, thereby more accurately indicating data arrival time and reducing UE power consumption. Furthermore, if a connected UE is not configured with DRX, it may also determine PDCCH detection based on LP-WUS indications. In summary, the base station can configure relevant LP-WUS resources for the UE, and the connected UE can reduce UE power consumption and improve user experience by detecting LP-WUS and determining relevant processing based on LP-WUS indications.

[0131] The UE detects LP-WUS on several time-frequency resources determined according to the LP-WUS parameters configured by the base station. These time-frequency resources used for LP-WUS detection are referred to as several LP-WUS monitoring occasions (LP-WUS MO, or LMO for short).

[0132] The base station may configure LP-WUS resources for different procedures or functions, instructing connected UEs to perform related processing. Different indication methods may be applied to these LP-WUS resources for different procedures or functions in this disclosure. For example, LP-WUS used to start a DRX timer uses 1 bit to indicate the detection of all serving cells. LP-WUS used during DRX activation time uses a bitmap approach, and so on. The UE can determine the appropriate indication method based on the relevant procedure definition or parameter configuration. The UE also determines the size of the information in the relevant LP-WUS used to indicate the UE based on other network configuration parameters, such as SCell configuration, and performs corresponding processing according to the indication, etc., to achieve coordinated processing between the network and the UE, thereby utilizing LP-WUS to reduce UE power consumption.

[0133] The following examples are provided to describe in more detail the implementation of this disclosure.

[0134] When a connected UE supports CA, the base station can configure one or more SCells for the UE. The UE can perform data transmission on these SCells. These SCells may handle different services with different transmission requirements. When the base station configures one or more SCells for the UE, it can use indication information for the UE or UE group in LP-WUS to indicate the UE's processing in these one or more SCells. For example, the UE can use one of the following indication information to determine the processing on the relevant PCell or SCell:

[0135] - The indication is a bit map, where each bit corresponds to the processing of a serving cell PCell or SCell;

[0136] - The indicator is a bit map, where each bit corresponds to a set of serving cell PCell or SCell processing;

[0137] - The indication is a single bit, corresponding to the processing of several serving cell PCells or SCells;

[0138] - The indication is a codepoint, which corresponds to the processing of several serving cell PCells or SCells.

[0139] The instructions listed here are just some examples; there may be other formats, which will not be listed here.

[0140] In addition, to enable the UE to correctly determine the processing on each PCell or SCell based on these indications, the UE can also determine the correspondence between these indications and each serving cell based on the base station configuration. For example, the base station can determine which serving cells are associated with a certain bit in the indication information through relevant configurations. These relevant configurations may be one or a combination of the following:

[0141] -Identifier in serving cell parameters

[0142] -Identifier in BWP parameters

[0143] The identifier in the -CORESET / Searchspace / PDCCH / PDSCH / PUSCH parameter

[0144] - Bit map indicating the serving cell

[0145] - List of service cell serial numbers indicating the serving cells

[0146] - List of service cell combinations

[0147] The identifier in the serving cell parameters may use different identifier methods. For example, in the RRC parameters of the serving cell configured at higher layers, a parameter X represents this identifier. When X is configured to be enabled (e.g., using "enabled" to indicate enable, which can also be referred to by other terms, such as "activated" or "effective"), it means that the UE determines the processing on the serving cell according to the instructions in LP-WUS. When parameter X is not configured or is configured to be disabled (e.g., using "disabled" to indicate disenabled, which can also be referred to by other terms, such as "not activated" or "not effective"), it means that the UE does not determine the processing on the serving cell according to the instructions in LP-WUS. The base station may also use a similar method to configure parameters with similar functions to parameter X in the BWP / CORESET / Search Space / PDCCH / PDSCH / PUSCH parameters, so that the UE can determine whether to perform related processing on the resources corresponding to the relevant BWP / CORESET / Search Space / PDCCH / PDSCH / PUSCH parameters according to the indication in LP-WUS. For example, PDCCH detection or PDSCH / PUSCH transmission on BWP, or detection using PDCCH on the resources corresponding to the relevant CORESET / Search Space / PDCCH parameters, or PDSCH or PUSCH transmission on the resources corresponding to the PDSCH or PUSCH parameters.

[0148] In another example, the identifier might also be a packet number. For instance, a base station configures a packet number for a serving cell to determine the relevant processing based on the indication in LP-WUS. In this case, these serving cells can be divided into several packets based on the packet number. When a serving cell parameter is configured with a packet number, the UE can determine the indication in the LP-WUS indication information for that serving cell or the packet to which the serving cell belongs based on that packet number.

[0149] In another optional example, the network may also use a serving cell bitmap to indicate which serving cells to process according to the instructions in LP-WUS. For example, a bitmap can be configured in the RRC parameters, the size of which is the number of serving cells configured by the base station for the UE. In this case, each serving cell is mapped to the bitmap according to its cell sequence number, for example, mapped from MSB to LSB in ascending order. When the bit in the bitmap corresponding to a serving cell is "1", it indicates that the UE determines the processing on that serving cell according to the instructions in LP-WUS; when the bit in the bitmap corresponding to a serving cell is "0", it indicates that the UE does not determine the processing on that serving cell according to the instructions in LP-WUS. Optionally, the base station may also configure or update this bitmap via MAC parameters (such as MAC-CE). The UE can determine which serving cells to process according to the instructions in LP-WUS based on the latest determined bitmap.

[0150] In another alternative example, the network may also use a list of serving cell numbers to configure which serving cells the UE determines to perform processing on the serving cell according to the instructions in LP-WUS. For example, a list of serving cell numbers can be configured in the RRC parameters. If a serving cell's serving cell number is in the list, it means the UE determines to perform processing on that serving cell according to the instructions in LP-WUS; otherwise, it means the UE does not determine to perform processing on that serving cell according to the instructions in LP-WUS.

[0151] When a connected UE determines the processing on the serving cell based on the base station configuration and the indications in the LP-WUS, it can determine the relevant indication method according to one or more of the examples above. At this time, the UE also needs to determine the size of the indication information in the relevant LP-WUS for its own UE or UE group (e.g., the size of the bitmap, the range of code point values, etc.), and how to determine the processing on the serving cell based on the relevant indications, etc. Furthermore, the identifiers / bitmaps / cell lists, etc., in the various examples here may be configured for a specific function of the LP-WUS, and different LP-WUS functions can have independent configurations. The UE can determine the relevant parameters and processing for a specific LP-WUS according to the relevant configuration and methods.

[0152] Figure 1 is a flowchart illustrating a method performed by a user equipment according to an embodiment of the present disclosure.

[0153] As shown in Figure 1, in step 101, the size of the bitmap is determined.

[0154] According to one aspect of this disclosure, the indication in LP-WUS for whether to perform relevant processing for a UE / UE group is a bit map, and each bit of the bit map corresponds to the indication information of one or a group of serving cells.

[0155] Optionally, the UE determines the size of the bitmap according to one of the following methods:

[0156] - Number of serving cells with the enable flag configured

[0157] - The number of serving cells where BWP / CORESET / Search Space / PDCCH / PDSCH / PUSCH are configured with the enable flag.

[0158] - Based on the serving cell bitmap, use the number of serving cells indicated by LP-WUS.

[0159] - Based on the list of serving cell numbers, use the number of serving cells indicated by LP-WUS.

[0160] - The number of packets in the serving cell indicated by LP-WUS, based on the serving cell packet sequence number.

[0161] -Based on the serving cell packet number, use the maximum packet number of the serving cell indicated by LP-WUS.

[0162] In a specific example, when the UE determines whether to perform processing on the serving cell according to the instructions in LP-WUS based on the serving cell identifier configured by the higher layer, the size of the bit map in LP-WUS for whether to perform relevant processing for a UE / UE group is the number of serving cells with all serving cell identifiers configured to be enabled.

[0163] In another example, when the higher layers (e.g., in RRC signaling) use identifiers in the BWP / CORESET / Search Space / PDCCH / PDSCH / PUSCH parameters to determine whether the UE determines the processing on the serving cell according to the instructions in LP-WUS, the size of the bit map in LP-WUS indicating whether to perform relevant processing for a UE / UE group is equal to the number of serving cells where all BWP / CORESET / Search Space / PDCCH / PDSCH / PUSCH with all identifiers configured to be enabled reside.

[0164] In another example, when a higher layer (e.g. in RRC signaling) uses a bitmap to indicate whether a UE determines whether to perform processing on the serving cell according to the indication in the LP-WUS, the size of the bitmap in the LP-WUS for whether to perform relevant processing for a UE / UE group is the number of serving cells whose indication for the corresponding serving cell is "1" in the bitmap (in the RRC signaling).

[0165] In another example, when a higher layer (e.g., in RRC signaling) uses a serving cell sequence number list to indicate whether a UE should determine whether to perform processing on a serving cell according to the instructions in the LP-WUS, the size of the bit map in the LP-WUS indicating whether to perform relevant processing for a UE / UE group is the number of serving cells in that serving cell sequence number list.

[0166] In another example, when a higher layer (e.g., in RRC signaling) uses the serving cell packet number to determine whether a UE determines processing on the serving cell according to the instructions in the LP-WUS, the size of the bit map in the LP-WUS indicating whether a UE / UE group is subject to relevant processing is the number of different packet numbers used in that serving cell set, or the number of serving cells using different packet numbers.

[0167] In another example, when a higher layer (e.g., in RRC signaling) uses the serving cell packet sequence number to determine whether processing is to be performed on the serving cell according to the instructions in the LP-WUS, the size of the bit map in the LP-WUS indicating whether relevant processing is to be performed for a UE / UE group is the value of the maximum packet sequence number used in that serving cell set.

[0168] Optionally, when the PCell in the network applies the relevant LP-WUS indication by default, the PCell does not need to be configured in the RRC parameters to reduce signaling overhead. In this case, when the UE determines the size of the indication in LP-WUS according to the above method, it adds 1 to the size determined by one of the methods in the above example as the size of the bit map of the indication information for that UE / UE group in LP-WUS.

[0169] Optionally, when one or more SCells are configured to be inactive by higher-layer signaling (such as RRC signaling or MAC signaling), the UE determines the size of the bit map of the indication information for that UE / UE group in LP-WUS based on the remaining active SCells and the method described above.

[0170] In step 103, the sequence number of the serving cell in the bit map is determined.

[0171] Optionally, the UE also determines the sequence number of the indicator corresponding to the serving cell in the bit map. The UE can determine the relevant sequence number according to one of the following methods:

[0172] - The service cell serial number of the service cell with the enable flag configured.

[0173] - Configured with the enabled flag: BWP / CORESET / Serving Cell Number

[0174] -Based on the serving cell bitmap, use the serving cell number indicated by LP-WUS for the serving cell.

[0175] -Based on the serving cell sequence list, use the sequence number of the serving cell indicated by LP-WUS in that list.

[0176] -Based on the serving cell packet number, use the packet number of the serving cell indicated by LP-WUS.

[0177] In a specific example, when the UE determines whether to determine the processing on the serving cell according to the instructions in LP-WUS based on the serving cell identifier configured by the higher layer (e.g., in RRC signaling), the sequence number in the bit map of whether to perform relevant processing for a UE / UE group in LP-WUS corresponding to a serving cell is the sequence number of the serving cell sequence number configured to be enabled in the serving cell group among all serving cell sequence numbers configured to be enabled. For example, these serving cells are arranged in ascending order of their serving cell sequence number. At this time, the UE maps the serving cell sequence number from smallest to largest to the MSB to LSB of the bit map.

[0178] In another example, when a higher layer (e.g., in RRC signaling) configures BWP / CORESET / Search Space / PDCCH / PDSCH / PUSCH to use identifiers to determine whether the UE determines the processing on the serving cell according to the instructions in LP-WUS, the sequence number in the bitmap corresponding to a serving cell in LP-WUS for whether to perform relevant processing for a UE / UE group is the sequence number of the serving cell where all BWP / CORESET / Search Space / PDCCH / PDSCH / PUSCH with the identifiers configured to be enabled is located in the set of all enabled serving cell sequence numbers. For example, these serving cells are arranged in ascending order of their serving cell sequence number. In this case, the UE is mapped to the MSB to LSB of the bitmap in ascending order of serving cell sequence number.

[0179] In another example, when a higher layer (e.g., in RRC signaling) uses a bitmap to indicate whether the UE determines whether to perform processing on the serving cell according to the indication in LP-WUS, the sequence number of the serving cell in the bitmap corresponding to whether to perform relevant processing for a UE / UE group in LP-WUS is the sequence number of the serving cell whose indication is "1" in the bitmap (in RRC signaling) among all serving cells whose indication is "1" in the bitmap (in RRC signaling). For example, these serving cells are arranged in ascending order of their serving cell sequence number. In this case, the UE is mapped to the MSB to LSB of the bitmap in ascending order of serving cell sequence number.

[0180] In another example, when a higher layer (e.g., in RRC signaling) uses a serving cell sequence number list to indicate whether the UE determines whether to perform processing on the serving cell according to the indication in LP-WUS, the sequence number in the bit map of whether to perform relevant processing for a UE / UE group in LP-WUS corresponding to a serving cell is the sequence number of the serving cell in the list. In this case, the UE is mapped to the MSB to LSB of the bit map according to the order of the serving cells in the serving cell sequence number list.

[0181] In another example, when a higher layer (e.g. in RRC signaling) uses the packet sequence number to determine whether to determine processing on the serving cell according to the instructions in LP-WUS, the sequence number in the bit map of whether to perform relevant processing for a UE / UE group in LP-WUS is the different packet number used in the serving cell group. In this case, the UE is mapped to the MSB to LSB of the bit map in ascending order of the packet number used by the serving cell.

[0182] Optionally, when the PCell in the network applies the relevant LP-WUS indication by default, the PCell does not need to be configured in the RRC parameters to reduce signaling overhead. In this case, when the UE determines the indication size in LP-WUS according to the above method, it always uses the first bit (e.g., MSB) to determine the relevant indication information of the PCell, and other SCells use the relevant bits in sequence.

[0183] In step 105, the relevant processing is determined.

[0184] After the UE determines the indication number corresponding to the serving cell, it can determine the processing in each serving cell based on the indication when it detects an indication in LP-WUS. For example, when the indication corresponding to the serving cell is "1", the UE performs PDCCH detection in the relevant serving cell. When the indication corresponding to the serving cell is "0", the UE does not need to perform PDCCH detection in the relevant serving cell.

[0185] Optionally, the UE determines the processing of each BWP / CORESET / Search Space / PDCCH / PDSCH / PUSCH based on the identifiers in the BWP / CORESET / Search Space / PDCCH / PDSCH / PUSCH parameters when an indication is detected in LP-WUS. For example, when the indication corresponding to the serving cell is "1", the UE performs PDCCH detection on the relevant BWP, or performs PDCCH detection using the relevant CORESET / Search Space parameters, or receives or transmits the relevant PDSCH / PUSCH (e.g., PDSCH / PUSCH without dynamic scheduling). Conversely, when the indication corresponding to the serving cell is "0", the UE does not perform PDCCH detection on the relevant BWP, or does not perform PDCCH detection using the relevant CORESET / Search Space parameters, or does not receive or transmit the relevant PDSCH / PUSCH.

[0186] Optionally, the UE's PDCCH detection in the relevant serving cell may also depend on other configurations. For example, depending on the cell's active or inactive state, the UE may not perform PDCCH detection on inactive SCells, or the UE may not expect the indication for inactive SCells to be "1". Similarly, depending on the BWP's active or inactive state, the UE may not perform PDCCH / PDSCH / PUSCH detection, reception, or transmission on inactive BWPs.

[0187] Figure 2 is a flowchart illustrating a second method performed by a user equipment according to an embodiment of the present disclosure.

[0188] In step 201, the serving cell indicated in the LP-WUS is determined.

[0189] In another alternative example of this disclosure, the indication in the LP-WUS regarding whether relevant processing is performed for a user / user group is a single bit, and the UE can determine which serving cells perform relevant processing according to the indication in the LP-WUS in one of the following ways:

[0190] - Serving cell with enabled flag configured

[0191] - The serving cell where BWP / CORESET / Search Space / PDCCH / PDSCH / PUSCH is configured with the enable flag.

[0192] -Based on the serving cell's bitmap, use the LP-WUS-indicated serving cell.

[0193] -Based on the list of serving cell numbers, use the serving cell indicated by LP-WUS.

[0194] -Use the serving cell indicated by LP-WUS according to the serving cell group number.

[0195] In step 203, the relevant processing is determined.

[0196] The UE identifies the serving cell indicated in the LP-WUS. When an indication in the LP-WUS is detected, the UE can determine the processing in each serving cell based on the relevant indication. For example, when the indication is "1", the UE performs PDCCH detection in the relevant serving cell. When the indication is "0", the UE does not need to perform PDCCH detection in the relevant serving cell.

[0197] Optionally, the UE determines the processing of each BWP / CORESET / Search Space / PDCCH / PDSCH / PUSCH based on the identifiers in the BWP / CORESET / Search Space / PDCCH / PDSCH / PUSCH parameters when an indication is detected in LP-WUS. For example, when the indication corresponding to the serving cell is "1", the UE performs PDCCH detection on the relevant BWP, or performs PDCCH detection using the relevant CORESET / Search Space parameters, or receives or transmits the relevant PDSCH / PUSCH. Conversely, when the indication corresponding to the serving cell is "0", the UE does not perform PDCCH detection on the relevant BWP, or does not perform PDCCH detection using the relevant CORESET / Search Space parameters, or does not receive or transmit the relevant PDSCH / PUSCH (e.g., PDSCH / PUSCH without dynamic scheduling).

[0198] Optionally, the UE's PDCCH detection in the relevant serving cell may also depend on other configurations. For example, depending on whether the relevant cell is active or inactive, the UE may not perform PDCCH detection on inactive SCells, or the UE may not expect the indication for inactive SCells to be "1". Similarly, depending on whether the BWP is active or inactive, the UE may not perform PDCCH / PDSCH / PUSCH detection, reception, or transmission on inactive BWPs.

[0199] Figure 3 is a flowchart illustrating method three performed by a user equipment according to an embodiment of the present disclosure.

[0200] In step 301, the size of the bits occupied by the code point is determined.

[0201] In another optional example of this disclosure, the indication in LP-WUS regarding whether relevant processing is performed for a user / user group is a code point. These code points representing different indications may be represented using several bits or several sequences. A code point value may correspond to the indication information of a serving cell or the indication information of a group of serving cells. The length of these bits or the number of different sequences is the size of the code point. For ease of description, the size of the bits occupied by the code point is used here. When using other indication forms (e.g., different sequences), the relevant parameters (e.g., the total number corresponding to different code points) can be obtained in a similar way. Optionally, the UE determines the size of the bits occupied by the code point according to one of the following methods:

[0202] - Number of serving cells with the enable flag configured

[0203] - The number of serving cells where BWP / CORESET / Search Space / PDCCH / PDSCH / PUSCH are configured with the enable flag.

[0204] - Based on the serving cell bitmap, use the number of serving cells indicated by LP-WUS.

[0205] - Based on the list of serving cell numbers, use the number of serving cells indicated by LP-WUS.

[0206] - The number of packets in the serving cell indicated by LP-WUS, based on the serving cell packet sequence number.

[0207] -Based on the serving cell packet number, use the maximum packet number of the serving cell indicated by LP-WUS.

[0208] -Based on the number of different service cell combinations

[0209] In a specific example, when the UE determines whether to determine the processing on the serving cell according to the instructions in the LP-WUS based on the serving cell identifier configured by the higher layer (e.g. in RRC signaling), the number N used to determine whether to perform relevant processing for a UE / UE group in the LP-WUS is the number of serving cells with all serving cell identifiers configured to be enabled.

[0210] In another example, when a higher layer (e.g., in RRC signaling) configures BWP / CORESET / Search Space / PDCCH / PDSCH / PUSCH to use identifiers to determine whether a UE determines processing on the serving cell according to the instructions in LP-WUS, the number N used to determine whether to perform relevant processing for a UE / UE group in LP-WUS is the number of serving cells where all identifiers are configured to enable BWP / CORESET / Search Space / PDCCH / PDSCH / PUSCH.

[0211] In another example, when a higher layer (e.g., in RRC signaling) uses a bitmap to indicate whether a UE determines whether to perform processing on the serving cell according to the indication in the LP-WUS, the number N used to determine whether to perform relevant processing for a UE / UE group in the LP-WUS is the number of serving cells whose indication for the corresponding serving cell in the higher layer bitmap is "1".

[0212] In another example, when a higher layer (e.g., in RRC signaling) uses a serving cell sequence number list to indicate whether a UE should determine whether to perform processing on a serving cell according to the instructions in the LP-WUS, the number N used to determine whether to perform relevant processing for a UE / UE group in the LP-WUS is the number of serving cells in the serving cell sequence number list.

[0213] In another example, when a higher layer (e.g. in RRC signaling) uses a packet number to determine whether processing is to be performed on the serving cell according to the instructions in the LP-WUS, the number N used to determine whether relevant processing is to be performed for a UE / UE group in the LP-WUS is the number of different packet numbers used in the serving cell set, or the number of serving cells using different packet numbers.

[0214] In another example, when a higher layer (e.g., in RRC signaling) uses a packet number to determine whether processing is to be performed on the serving cell according to the instructions in the LP-WUS, the number N used to determine whether relevant processing is to be performed for a UE / UE group in the LP-WUS is the value of the maximum packet number used in that serving cell set.

[0215] In another example, when the list of different serving cell combinations configured in the RRC signaling determines whether to determine the processing on the serving cell according to the instructions in the LP-WUS, the number N used to determine whether to perform relevant processing for a UE / UE group in the LP-WUS is the number of different combinations in the list of different serving cell combinations.

[0216] Optionally, the UE determines the bit size occupied by the code point as ceil(log2(N+K)). Here, ceil is the floor function, log2 is the logarithm with base 2, and K is a fixed number. In a typical example, K is 2, allowing the method in Table 1 to indicate the processing for each serving cell. Alternatively, in another example, K is 1. This allows the UE to determine whether to perform processing on a serving cell based on the instructions in LP-WUS when using a list of different serving cell combinations configured in the RRC signaling. A code point value of "0" can indicate no processing for any serving cells, while the code point value corresponding to a specific serving cell combination within the combination can be used to instruct the serving cells in that combination to perform relevant processing.

[0217] Optionally, when the PCell in the network applies the relevant LP-WUS indication by default, the PCell does not need to be configured in the RRC parameters to reduce signaling overhead. In this case, when the UE determines the indication size in LP-WUS according to the above method, N plus 1 determined by the above method is used as the size of the number N of indication information for that UE / UE group in LP-WUS, that is, the number of bits occupied by the code point determined by the UE is ceil(log2(N+K+1)).

[0218] In step 303, the code point value corresponding to the serving cell is determined.

[0219] Optionally, the UE may also determine the code point value corresponding to the serving cell. The UE may determine the relevant code point value according to one of the following methods:

[0220] - The service cell serial number of the service cell with the enable flag configured.

[0221] - The BWP / CORESET / serving cell number of the serving cell with the enabled flag configured - The serving cell number of the serving cell indicated by LP-WUS, based on the serving cell bitmap.

[0222] -Based on the serving cell sequence list, use the sequence number of the serving cell indicated by LP-WUS in that list.

[0223] -Based on the serving cell packet number, use the packet number of the serving cell indicated by LP-WUS.

[0224] In a specific example, when the UE determines whether to determine processing on the serving cell according to the instructions in LP-WUS based on the serving cell identifier configured by higher layers (e.g., in RRC signaling), the code point value corresponding to a serving cell in LP-WUS for whether to perform relevant processing for a UE / UE group is the sequence number of the serving cell number configured to be enabled within the set of all enabled serving cell numbers in the serving cell group. For example, these serving cells are arranged in ascending order of their serving cell numbers, and the sequence number of a serving cell within that set is represented. Optionally, the sequence number can start counting from 1 depending on the processing corresponding to the code point value.

[0225] In another example, when a higher layer (e.g., in RRC signaling) configures the BWP / CORESET / Search Space / PDCCH / PDSCH / PUSCH to use identifiers to determine whether a UE determines processing on the serving cell according to the instructions in LP-WUS, the code point corresponding to a serving cell that determines whether relevant processing is performed for a UE / UE group in LP-WUS is the sequence number of the serving cell containing all enabled BWP / CORESET / Search Space / PDCCH / PDSCH / PUSCH identifiers. For example, these serving cells are arranged in ascending order of their serving cell numbers, and the sequence number of a serving cell within that set is used. Optionally, the sequence number can start counting from 1, depending on the processing corresponding to the code point value.

[0226] In another example, when a higher layer (e.g., in RRC signaling) uses a bitmap to indicate whether a UE determines processing on a serving cell according to the indication in LP-WUS, the code point corresponding to a serving cell and whether relevant processing is performed for a UE / UE group in LP-WUS is the sequence number of the serving cell with an indication of "1" in the bitmap (in RRC signaling) and the number of serving cells with an indication of "1" in all bitmaps (in RRC signaling). For example, these serving cells are arranged in ascending order of their serving cell numbers, and the sequence number of a serving cell is within that arrangement. Optionally, the sequence number can start counting from 1 depending on the processing corresponding to the code point value.

[0227] In another example, when a higher layer (e.g., in RRC signaling) uses a serving cell sequence number list to indicate whether a UE should determine processing on a serving cell according to the indication in the LP-WUS, the code point corresponding to a serving cell that indicates whether relevant processing is performed for a UE / UE group in the LP-WUS is the sequence number of that serving cell in the list. Optionally, the sequence number can be counted starting from 1, depending on the processing corresponding to the code point value.

[0228] In another example, when a higher layer (e.g., in RRC signaling) uses a packet sequence number to determine whether processing is required on the serving cell according to the indication in the LP-WUS, the code point in the LP-WUS indicating whether relevant processing is required for a UE / UE group is the packet sequence number used by that serving cell. Optionally, the sequence number can be counted starting from 1, depending on the processing corresponding to the code point value.

[0229] In step 305, the relevant processing is determined.

[0230] After the UE determines the code point value corresponding to the serving cell, it can determine the processing for each serving cell based on the indication detected in the LP-WUS. For example, based on the code point value for the UE in the received LP-WUS and the methods in Table 1 corresponding to the code point value, the UE can perform the relevant processing in each column of Example 1, Example 2, or Example 3. As another example, when the UE determines the processing for BWP / PDSCH / PUSCH based on the LP-WUS, it can refer to the processing method for PDCCH in Table 1.

[0231] Table 1

[0232] Optionally, the UE may also combine the above methods to obtain indication information for the UE and determine related processing. For example, when the UE has the capability to detect the first and second information according to LP-WUS (Capability 2), it can determine the relevant processing based on the 1-bit indication for the UE or UE group in the first information and the bit map or code point for the UE or UE group in the second information. Specifically, when the 1-bit indication detected by the UE in the first information is "0", the UE does not detect PDCCH on the relevant serving cell; when the 1-bit indication detected by the UE in the first information is "1", the UE further determines on which serving cells to detect PDCCH based on the bit map or code point indicated in the second information.

[0233] Optionally, the UE can also determine the magnitude of the relevant indication information for the UE and the relevant processing based on the configuration of the DRX group. For example, when the base station configures one DRX group for the UE, the UE uses the above method to confirm the magnitude of the indication related to the serving cell in the DRX group and the processing on each serving cell according to the indication. When the base station configures two DRX groups for the UE, the UE confirms the magnitude of the indication in the relevant LP-WUS for the serving cells in the two DRX groups respectively, and the processing on each serving cell according to the indication respectively. In a specific example, the base station configures two DRX groups for the UE; when some serving cells in each of the two DRX groups use the indication in the LP-WUS to determine the relevant processing, and the indication in the LP-WUS is a 1-bit indication, then there are two bits in the LP-WUS for the UE, corresponding to the indication information of the serving cells in the two DRX groups respectively; when only some serving cells in a certain DRX group use the indication in the LP-WUS to determine the relevant processing, and the indication in the LP-WUS is a 1-bit indication, then there is 1 bit in the LP-WUS for the UE, corresponding to the indication information of the serving cell in the corresponding DRX group. When the indication in LP-WUS is a bitmap or code point, a similar method can be used to confirm the indication information for the serving cell in the two DRX groups respectively.

[0234] The following description uses FIG4 to illustrate a user equipment that can perform the methods described in detail above in this disclosure as an embodiment.

[0235] Figure 4 is a block diagram illustrating the user equipment (UE) involved in this disclosure.

[0236] As shown in Figure 4, the user equipment UE400 includes a processor 401 and a memory 402. The processor 401 may include, for example, a microprocessor, a microcontroller, an embedded processor, etc. The memory 402 may include, for example, volatile memory (such as random access memory, RAM), a hard disk drive (HDD), non-volatile memory (such as flash memory), or other memory. Program instructions are stored on the memory 402. When executed by the processor 401, these instructions can perform the methods described in detail herein, executed by the user equipment.

[0237] The methods and related devices of this disclosure have been described above in conjunction with preferred embodiments. Those skilled in the art will understand that the methods shown above are merely exemplary, and the various embodiments described above can be combined with each other without contradiction. The methods of this disclosure are not limited to the steps and sequence shown above. The network nodes and user equipment shown above may include more modules, such as modules that can be developed or will be developed in the future for use with base stations, MMEs, or UEs, etc. The various identifiers shown above are merely exemplary and not limiting, and this disclosure is not limited to the specific information elements that are examples of these identifiers. Those skilled in the art can make many variations and modifications based on the teachings of the illustrated embodiments. For example, in this disclosure, "1" and "0" are used to represent related indication information, and they can be interchanged without contradiction; that is, "0" is used to indicate information indicated by "1" in this disclosure, and "1" is used to indicate information indicated by "0" in this disclosure. As another example, in the examples of this disclosure, some sequence numbers are arranged from smallest to largest to correspond to bits from MSB to LSB; without contradiction, they may also be arranged from largest to smallest to correspond to bits from MSB to LSB. These changes do not affect the UE's ability to determine the relevant procedures according to the relevant instructions.

[0238] It should be understood that the above embodiments of this disclosure can be implemented by software, hardware, or a combination of both. For example, the various components inside the base station and user equipment in the above embodiments can be implemented by a variety of devices, including but not limited to: analog circuit devices, digital circuit devices, digital signal processing (DSP) circuits, programmable processors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), programmable logic devices (CPLDs), and so on.

[0239] In this disclosure, "base station" can refer to a mobile communication data and control switching center with high transmission power and wide coverage, including functions such as resource allocation and scheduling, and data reception and transmission. "User equipment" can refer to user mobile user equipment, such as mobile phones, laptops, and other user equipment that can wirelessly communicate with base stations or micro base stations.

[0240] Furthermore, the embodiments of this disclosure disclosed herein can be implemented on a computer program product. More specifically, the computer program product is one that has a computer-readable medium on which computer program logic is encoded, which, when executed on a computing device, provides related operations to implement the above-described technical solutions of this disclosure. When executed on at least one processor of a computing system, the computer program logic causes the processor to perform the operations (methods) described in the embodiments of this disclosure. This configuration of the disclosure is typically provided as software, code, and / or other data structures set or encoded on a computer-readable medium such as an optical medium (e.g., CD-ROM), floppy disk, or hard disk, or other media such as firmware or microcode on one or more ROM, RAM, or PROM chips, or downloadable software images, shared databases, etc., in one or more modules. The software or firmware or such configuration can be installed on a computing device to cause one or more processors in the computing device to perform the technical solutions described in the embodiments of this disclosure.

[0241] Furthermore, each functional module or feature of the base station equipment and user equipment used in each of the above embodiments can be implemented or executed by circuitry, which is typically one or more integrated circuits. Circuitry designed to perform the various functions described in this specification may include general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs) or general-purpose integrated circuits, field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic, or discrete hardware components, or any combination of the above devices. The general-purpose processor may be a microprocessor, or the processor may be an existing processor, controller, microcontroller, or state machine. The aforementioned general-purpose processor or each circuit may be configured by digital circuitry or by logic circuitry. Furthermore, when advancements in semiconductor technology lead to advanced technologies that can replace current integrated circuits, this disclosure may also utilize integrated circuits obtained using such advanced technologies.

[0242] Although the present disclosure has been illustrated above in conjunction with preferred embodiments, those skilled in the art will understand that various modifications, substitutions, and changes can be made to the disclosure without departing from its spirit and scope. Therefore, the disclosure should not be limited by the above embodiments, but rather by the appended claims and their equivalents.

Claims

1. A method performed by a user equipment (UE), comprising: determining a size of a bit map for the UE in a low power wake up signal (LP-WUS) ; determining a sequence number of each serving cell in the bit map; and detecting, for each serving cell, an indication for the serving cell from the received LP-WUS according to the sequence number to determine whether to perform PDCCH detection in the serving cell; the size of the bit map is a number N of bits of indication information for the UE / UE group in the LP-WUS. 2.The method of claim 1, wherein the size of the bit map is determined according to at least one of: a number N of serving cells with enabled identification configured for the UE; a number N of serving cells where BWP / CORESET / search space / PDCCH / PDSCH / PUSCH is configured with enabled identification for the UE; a number N of serving cells indicated by the bit map of serving cells; a number N of serving cells indicated by a sequence number list of serving cells; a number N of groups of serving cells indicated by a group sequence number of serving cells; and a maximum group sequence number N of serving cells indicated by the group sequence number of serving cells. 3.The method of claim 1, wherein the sequence number of each serving cell in the bit map is determined according to at least one of: a serving cell sequence number of a serving cell with enabled identification configured; a serving cell sequence number of a serving cell where BWP / CORESET is configured with enabled identification; a serving cell sequence number of a serving cell indicated by the bit map of serving cells; a sequence number of a serving cell in a sequence number list of serving cells indicated by the LP-WUS; and a group sequence number of a group of serving cells indicated by the LP-WUS. 4.A method performed by a user equipment (UE), comprising: determining a serving cell to which an indication of one bit for the UE in a low power wake up signal (LP-WUS) is applied; and determining whether to perform PDCCH detection in the determined serving cell according to the one bit for the UE and an active or inactive state of the related serving cell in the received LP-WUS. 5.The method of claim 4, wherein the serving cell to which the indication in the LP-WUS is applied is determined according to at least one of: a serving cell with enabled identification configured; a serving cell where BWP / CORESET / search space / PDCCH / PDSCH / PUSCH is configured with enabled identification; a serving cell indicated by the bit map of serving cells; and a serving cell in a sequence number list of serving cells indicated by the LP-WUS. ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ - a number of serving cells indicated by the LP-WUS according to a bitmap of serving cells; - a number of serving cells indicated by the LP-WUS according to a list of serving cell indices; and - a number of serving cell groups indicated by the LP-WUS according to a list of serving cell group indices.

6. A method performed by a user equipment (UE), comprising: determining a size of a bit field occupied by a codepoint for the UE in a low power wake-up signal (LP-WUS); determining a codepoint value corresponding to each serving cell; and for each serving cell, detecting an indication for the serving cell from the received LP-WUS according to the codepoint value to determine whether to perform PDCCH detection on the serving cell.

7. The method of claim 6, wherein, a number of bits N of indication information for the UE / UE group is determined according to at least one of: - a number of serving cells configured with enablement indication; - a number of serving cells where BWP / CORESET / search space / PDCCH / PDSCH / PUSCH are configured with enablement indication; - a number of serving cells indicated by the LP-WUS according to a bitmap of serving cells; - a number of serving cells indicated by the LP-WUS according to a list of serving cell indices; - a number of serving cell groups indicated by the LP-WUS according to a list of serving cell group indices; - a maximum serving cell group index indicated by the LP-WUS according to a list of serving cell group indices; - a number of different serving cell combinations, and a size of a bit field occupied by a codepoint for the UE is determined according to ceil(log2(N+K)) or ceil(log2(N+K+1)), where K is a predefined number, ceil is a ceiling operation, and log2 is a logarithm operation with base 2.

8. The method of claim 6, wherein, the codepoint value corresponding to each serving cell is determined according to at least one of: - a serving cell index of a serving cell configured with enablement indication; - a serving cell index of a serving cell where BWP / CORESET are configured with enablement indication; - a serving cell index of a serving cell indicated by the LP-WUS according to a bitmap of serving cells; - a serving cell index of a serving cell indicated by the LP-WUS according to a list of serving cell indices; and - a serving cell group index of a serving cell group indicated by the LP-WUS according to a list of serving cell group indices.

9. The method of claim 7 or 8, wherein, when the UE is configured with two DRX groups, the UE determines a size of a bit field occupied by a codepoint for each DRX group of the UE according to a configuration of serving cells in each DRX group, determines a codepoint value corresponding to each serving cell in each DRX group, and for each serving cell in each DRX group, detects an indication for the serving cell from the received LP-WUS according to the codepoint value to determine whether to perform PDCCH detection on the serving cell.

10. A user equipment (UE), comprising: a processor; and a memory storing instructions, wherein the instructions, when executed by the processor, perform the method of any one of claims 1 to 9. ​ ​

Images