Techniques for network energy saving conditional handover

Abstract

The present application relates to apparatuses and components including devices, systems, and methods for network energy saving conditional handover.

Description

Technical Field

[0001] This application relates generally to cellular communication networks, and particularly to technologies for the transfer of network energy-saving conditions. Background Technology

[0002] Wireless mobile communication technologies use various standards and protocols to transmit data between base stations and wireless communication devices. Wireless communication system standards and protocols may include, but are not limited to, 3GPP Long Term Evolution (LTE); 5G 3GPP New Radio (NR); and technologies beyond 5G. In a 5G Radio Access Network (RAN), base stations may include RAN nodes, such as 5G nodes, NR nodes, or next-generation node B (gNB), which communicate with wireless communication devices (also known as user equipment (UE)). Attached Figure Description

[0003] Figure 1 Examples of network environments based on some implementation schemes are provided.

[0004] Figure 2 Examples of downlink control information based on some implementation schemes are shown.

[0005] Figure 3 Examples of downlink control information based on some implementation schemes are shown.

[0006] Figure 4 Examples of downlink control information and radio resource control configurations according to some implementation schemes are shown.

[0007] Figure 5 Examples of monitoring configurations based on some implementation schemes are shown.

[0008] Figure 6 The operational flow / algorithm structure according to some implementation schemes is illustrated.

[0009] Figure 7 Another operational flow / algorithm structure based on some implementation schemes is illustrated.

[0010] Figure 8 Examples of user equipment based on some implementation schemes are shown.

[0011] Figure 9 Examples of base stations based on some implementation schemes are shown. Detailed Implementation

[0012] The following detailed description refers to the accompanying drawings. The same reference numerals may be used to identify the same or similar elements in different drawings. In the following description, specific details, such as particular structures, architectures, interfaces, and / or techniques, are set forth for illustrative and non-limiting purposes to provide a thorough understanding of various aspects of some embodiments. However, it will be apparent to those skilled in the art that various aspects may be practiced in other examples departing from these specific details. In some cases, descriptions of well-known devices, circuits, and methods have been omitted so as not to obscure the description of the aspects with unnecessary detail. For the purposes of this document, the phrase “A or B” means (A), (B), or (A and B), and the phrase “based on A” means “at least partially based on A,” for example, it can be “based solely on A” or it can be “partially based on A.”

[0013] The following is a glossary of terms that may be used in this disclosure.

[0014] As used herein, the term "circuit" means, is part of, or includes the following: hardware components such as electronic circuits, logic circuits, processors (shared, dedicated, or grouped) or memories (shared, dedicated, or grouped), application-specific integrated circuits (ASICs), field-programmable devices (FPDs) (e.g., field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), structured ASICs, or programmable system-on-chips (SoCs)), and / or digital signal processors (DSPs) configured to provide the described functionality. In some aspects, a circuit may execute one or more software or firmware programs to provide at least some of the described functionality. The term "circuit" may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) and program code for executing the functionality of that program code. In these aspects, the combination of hardware elements and program code may be referred to as a particular type of circuit.

[0015] As used herein, the term "processor circuit" means, is part of, or includes the following: circuitry capable of sequentially and automatically performing a series of arithmetic or logical operations; or recording, storing, or transmitting digital data. The term "processor circuitry" may also refer to an application processor; a baseband processor; a central processing unit (CPU); a graphics processing unit; a single-core processor; a dual-core processor; a triple-core processor; a quad-core processor; or any other device capable of executing or otherwise operating computer-executable instructions (such as program code); a software module; or a functional process.

[0016] As used herein, the term "interface circuit" refers to, is part of, or includes a circuit that enables the exchange of information between two or more components or devices. The term "interface circuit" can refer to one or more hardware interfaces; for example, a bus, I / O interface, peripheral component interface, or network interface card.

[0017] As used herein, the term "user equipment" or "UE" refers to equipment of a remote user that has radio communication capabilities and can describe network resources in a communication network. The terms "user equipment" or "UE" may be considered synonymous and may refer to a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term "user equipment" or "UE" can include any type of wireless / wired equipment or any computing device that includes a wireless communication interface.

[0018] As used herein, the term "computer system" means any type of interconnected electronic device, computer device, or component thereof. Additionally, the term "computer system" or "system" may refer to various components of a computer that are communicatively coupled to each other. Furthermore, the term "computer system" or "system" may refer to multiple computer devices or multiple computing systems that are communicatively coupled to each other and configured to share computing resources or network resources.

[0019] As used herein, the term "resource" refers to physical or virtual devices, physical or virtual components within a computing environment, or physical or virtual components within a specific device, such as computer equipment, mechanical equipment, memory space, processor / CPU time, processor / CPU utilization, processor and accelerator load, hardware time or utilization, power supply, input / output operations, port or network sockets, channel / link allocation, throughput, memory utilization, storage, network, databases and applications, units of workload, etc. "Hardware resource" can refer to computer, storage, or network resources provided by physical hardware components. "Virtualized resource" can refer to computer, storage, or network resources provided by virtualization infrastructure to applications, devices, systems, etc. The terms "network resource" or "communication resource" can refer to resources that computer equipment / systems can access via a communication network. The term "system resource" can refer to any kind of shared entity providing services and can include computing or network resources. System resources can be considered as a coherent set of functions, network data objects, or services that can be accessed through a server, wherein such system resources reside on a single host or multiple hosts and can be clearly identified.

[0020] As used herein, the term "channel" refers to any tangible or intangible transmission medium used for transmitting data or data streams. The term "channel" may be synonymous or equivalent with "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," or any other similar term indicating a means or medium through which data is transmitted. Additionally, as used herein, the term "link" refers to a connection between two devices for the purpose of sending and receiving information.

[0021] As used in this article, the terms "instantiate" and "instantiate" refer to the creation of an instance. "Instance" also refers to the concrete occurrence of an object, which may occur, for example, during the execution of program code.

[0022] The term "connection" can refer to an established signaling relationship between two or more elements at a common communication protocol layer through a communication channel, link, interface, or reference point.

[0023] As used herein, the term "network element" refers to physical or virtualized equipment or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with or referred to as networked computers, network hardware, network equipment, network nodes, virtualized network functions, etc.

[0024] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to a single piece of content within an information element or a data element that contains content. An information element may include one or more additional information elements.

[0025] Figure 1 A network environment 100 according to some embodiments is illustrated. Network environment 100 may include a UE 104 coupled to a base station (BS) 108 of a radio access network (RAN) 112 providing one or more serving cells. In some embodiments, BS 108 is a gNB providing one or more 3GPP NR cells. The air interface through which UE 104 and BS 108 communicate may be compatible with 3GPP Technical Specifications (TS) (such as those defining 5G NR or later system standards, e.g., sixth-generation (6G) standards). Although RAN 112 is shown as having one base station (base station 108), it should be understood that RAN 112 may include multiple base stations or other access nodes providing services to various UEs via serving cells.

[0026] In some implementations, base station 108 may be one of a plurality of base stations providing service to UE 104 via dual connectivity (DC) operation. Base stations may be coupled to each other via an X2 interface through ideal or non-ideal backhaul. A base station may include a primary node (MN) to provide control plane connectivity to the core network. The MN may be associated with a group of serving cells referred to as a primary cell group (MCG), which includes a primary cell (SpCell) and optionally one or more secondary cells (SCells) in a carrier aggregation (CA) deployment. The SpCell of the MCG may also be referred to as a primary serving cell (PCell). A base station may also include a secondary node (SN), which may not have control plane connectivity to the core network. The SN may be used to provide additional resources to UE 104. The SN may be associated with a group of serving cells referred to as a secondary cell group (SCG), which includes a SpCell and one or more SCells in a CA deployment. The SpCell of the SCG may also be referred to as a primary-secondary serving cell (PSCell).

[0027] In some implementations, RAN 112 can provide CA deployment without DC operation, where one or more base stations provide PCell and one or more SCell.

[0028] In some implementations, the network can utilize Conditional Handover (CHO) to improve mobility robustness and reliability. This may involve base station 108 configuring UE 104 using handover assistance information relative to one or more candidate cells and providing information about UE 104 to one or more candidate cells. UE 104 can then monitor link quality for various handover conditions and execute a stored "handover" command if / when the condition becomes true. If more than one candidate cell meets the condition, UE 104 can select the cell for which it will perform the handover.

[0029] In some implementations, the configured handover conditions may include events A3 or A5. An A3 event may indicate that the serving cell is worse in decibels (dB) than the target cell. An A5 event may indicate that the serving cell is worse than a first threshold and the target cell is better than a second threshold. The signal metric used to measure the serving / target cell may be one or more of Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), or Signal-to-Noise Ratio (SINR). The decibel threshold / dB value may be configured by handover assistance information (another configuration message) or predefined by 3GPP TS.

[0030] CHOs may only be supported for PCell or PSCell in the UE. CHOs may not be supported for SCell in the UE.

[0031] To implement CHO relative to non-terrestrial networks (NTNs), additional handover conditions (A4 events) are introduced, and new conditional triggering conditions related to location and time are defined. An A4 event can refer to a neighboring cell transition falling within a predefined threshold range. Unless otherwise described herein, the CHO procedure may resemble that described in Section 9.2.3.4 of 3GPP TS 38.300 v17.6.0 (2023-09).

[0032] In some instances, the serving cell may be able to enter Network Energy Saving (NES) mode to conserve power. The CHO process can be enhanced to address situations where the source / target cell is in NES mode. This allows, for example, a relaxed CHO condition to be applied starting at a fixed time after the NES UE enters NES mode from the source cell. This can be beneficial in both scenarios. In the first scenario, the source cell entering NES mode may plan to disable some or all of its services. In this case, the source cell may not be able to adequately serve UE 104 after its switch to NES mode. In the second scenario, the source cell entering NES mode may plan to activate a Cell Discontinuous Transmission (DTX) / Discontinuous Reception (DRX) configuration with a long inactivity duration. In this case, the Quality of Service (QoS) of UE 104 may be degraded in the source cell.

[0033] In some implementations, RAN 112 may send downlink control information (DCI) to indicate that the serving cell is entering NES mode and UE 104 will trigger a CHO enhancement for NES (e.g., using relaxed CHO conditions). This indication may be referred to as an NES CHO indication. The transmission of DCI with an NES CHO indication may also be referred to as Layer 1 (L1) triggered signaling to indicate that the serving cell is entering NES mode.

[0034] In some implementations, the DCI used to send the NES CHO indication may be the same DCI used to indicate the activation or deactivation of the cell DTX / DRX configuration for the serving cell. The DCI may be a group common DCI format 2_X applicable to multiple UEs, where X is an integer. In some implementations, DCI format 2_X may be DCI format 2_9 sent using a Cyclic Redundancy Check (CRC) scrambled with the NES Radio Network Temporary Identifier (RNTI).

[0035] This disclosure provides details of DCI design for signaling NES CHO indications and details of UE operation upon receiving the information. Some embodiments describe the NES CHO bit applied to each serving cell, while others describe the NES CHO bit applied to each cell group. Further embodiments address the difficulty of signaling NES CHO indications to the serving cell in a group common DCI when the application of the NES CHO depends on whether the serving cell is the UE's PCell, PSCell, or SCell. As discussed above, CHOs apply only to the UE's PCell or PSCell, and not to the UE's SCell. However, a specific serving cell can be the PCell of a first UE and the SCell of a second UE. Therefore, the embodiments describe how various UEs will interpret the NES CHO indication based on their own serving cell configuration.

[0036] Figure 2 An example of DCI 200 according to some implementation schemes is illustrated. DCI 200 represents the first DCI signaling aspect, in which a single NES CHO indication is provided within a DCI block having cell DTX / DRX indications. This eliminates the need to introduce a new NES CHO indication. positionInDCI Completed under the given parameters.

[0037] DCI 200 may include support for multiple blocks (e.g., N One or more indications for blocks. Each block may correspond to a serving cell. For example, DCI 200 may include indications for block #1, block #j, and block #N. The starting location of each block may be determined by parameters. positionInDCI-cellDTRX This indicates that the parameter is provided by a higher layer for UE 104. For example, base station 108 may send cell group configurations via Radio Resource Control (RRC) signaling, which include serving cell configurations for various serving cells (e.g., PCell, PSCell, or SCell). Serving cell configurations may include... positionInDCI-cellDTRX The parameter is used by UE104 to determine which indications in the DCI correspond to that particular serving cell.

[0038] Each block may include a cell DTX / DRX indication and an NES CHO indication. The cell DTX / DRX indication indicates whether the configured cell DTX / DRX is active or deactivated. If both cell DTX and cell DRX are configured for the corresponding serving cell, the cell DTX / DRX indication may be two bits, where the most significant bit (MSB) corresponds to the cell DTX configuration and the least significant bit (LSB) corresponds to the cell DRX configuration. If either cell DTX or cell DRX, but not both, are configured for the cell, the cell DTX / DRX indication may include one bit.

[0039] As shown in the figure, serving cell #1 can be configured with both cell DTX and cell DRX, therefore its cell DTX / DRX indication includes two bits. Serving cell #j can only include cell DTX configuration, therefore its cell DTX / DRX indication includes one bit to activate / deactivate cell DTX configuration. Serving cell #N can only include cell DRX configuration, therefore its cell DTX / DRX indication includes one bit to activate / deactivate cell DRX configuration.

[0040] The NES CHO indication can be provided by a bit following the cell's DTX / DRX bit. The NES CHO bit can be set to "1" to indicate that the corresponding cell is entering NES mode. The NES CHO bit can be set to "0" to indicate that the corresponding cell is not entering NES mode. Optional bit settings can be used.

[0041] To accommodate the DCI signaling concept embodied in DCI 200, section 7.3.1.3.10 of 3GPP TS 38.212 v18.0.0 (2023-09) can be modified as follows: remove the crossed-out text and add underlined text. DCI format 2_9 is used for cell DTX / DRX configuration to activate or deactivate one or more serving cells for one or more UEs. Or notify the serving cell that it is entering NES mode to trigger NES CHO enhancement. .

[0042] The following information is transmitted using DCI format 2_9 with a CRC scrambled by NES-RNTI: - Block number 1, Block number 2, ..., Block number N The initial positioning of the block is determined by parameters. positionInDCI-cellDTRX Confirmed, this parameter is provided to the UE by a higher layer.

[0043] If the UE is configured with higher-level parameters XYZ cellDTRX-RNTI and dci-Format2-9 Then, a higher layer configures one or more blocks for the UE, where the following fields are defined for each block: - Community DTX / DRX indicator — If the UE does not support cell DTX / DRX operations triggered by DCI format 2_9 or the UE Not configured cellDTXConfig or cellDRXConfig If it is 0, then it is 0. If the UE is configured with XYZ The service area cellDTXConfig and cellDRXConfig Both If the value is positive, then it is 2 bits, where MSB corresponds to the cell DTX configuration and LSB corresponds to the cell DRX configuration; otherwise, it is 1 bit. - NES CHO indication - 1 bit if NES CHO is configured in the serving cell.

[0044] The size of DCI format 2_9 is determined by higher-level parameters. sizeDCI-2-9 instruct.

[0045] To accommodate the DCI signaling concept embodied in DCI 200, section 11.5 of 3GPP TS 38.213 v18.0.0 (2023-09) can be modified by adding the following underlined text: According to the service area cellDTXConfig Community DTX operation and cellDRXConfig A UE [11, TS 38.331] configured for operation on the serving cell in one or both of the cell DRX operations can be... dci-Format2- 9 Additionally, a Type3-PDCCH CSS set is provided to monitor PDCCHs used for detecting DCI format 2_9 (as described in Clause 10.1). And the cell DTX / DRX indicator field of the serving cell position-inDCI-NES DCI format 2_9 The location in the code (if the UE supports cell DTX and / or cell DRX triggered by DCI format 2_9). .

[0046] Figure 3 An example of DCI 300 according to some implementation schemes is shown. DCI 300 represents a second DCI signaling aspect, in which the network can signal new instructions dedicated to NES CHO. positionInDCI parameter.

[0047] DCI 300 may include a first block set (e.g., block #1-block #N) that provides cell DTX / DRX indications for a corresponding serving cell set (e.g., serving cell #1-serving cell #N). The starting location of each block in the first set may be determined by parameters. positionInDCI-cellDTRX This indicates that the parameter is provided by a higher layer for UE 104, similar to what was described above relative to DCI 200.

[0048] DCI 300 may also include a second set of blocks (e.g., block #N+1 to block #N+m) that provides NES CHO indications. The second set of blocks may begin after the last block in the first set. Each block in the second set may correspond to a serving cell configured with an NES CHO. The number of blocks in the second set may be equal to or different from (e.g., less than) the number of blocks in the first set. As shown, the second set of blocks may include block #N+1 with an NES CHO indication for serving cell #1, ..., block #N+m with an NES CHO indication for serving cell #m.

[0049] The starting position of each block in the second set can be determined by... positionInDCI-CHO The parameters are determined and provided to the UE by a higher layer, for example, via RRC signaling. For a UE, the network can configure this only for the UE in its PCell or PSCell. dci-Format2-9 Configure in ) positionInDCI-CHO .exist Figure 4Some examples are shown in more detail below.

[0050] To accommodate the DCI signaling concept embodied in DCI 200, section 7.3.1.3.10 of 3GPP TS 38.212 v18.0.0 (2023-09) can be modified as follows: remove the crossed-out text and add underlined text. DCI format 2_9 is used for cell DTX / DRX configuration to activate or deactivate one or more serving cells for one or more UEs. Or notify the serving cell that it is entering NES mode to trigger NES CHO enhancement. .

[0051] The following information is transmitted using DCI format 2_9 with a CRC scrambled by NES-RNTI: - Block number 1, Block number 2, ..., Block number N The initial positioning of the block is determined by parameters. positionInDCI-cellDTRX or positionInDCI-CHO Confirmed, this parameter is provided to the UE by a higher layer.

[0052] If the UE is configured with higher-level parameters XYZcellDTXR-RNTI , dci-Format2-9 and positionInDCI-cellDTRX Then, a higher layer configures one or more blocks for the UE, where the following fields are defined for each block: - Cellular DTX / DRX indicator—if XYZ Configure in this service cell cellDTXconfig and cellDRXconfig Both If the value is positive, then it is 2 bits, where MSB corresponds to the cell DTX configuration and LSB corresponds to the cell DRX configuration; otherwise, it is 1 bit. If the UE is configured with higher-level parameters cellDTRX-RNTI , dci-Format2-9 and positionInDCI- CHO Then, a higher layer will configure a block for the UE, where the following fields are defined for the block: - NES CHO indication - 1 bit if NES CHO is configured in the serving cell.

[0053] The size of DCI format 2_9 is determined by higher-level parameters. sizeDCI-2-9 instruct.

[0054] In some implementations, the RRC parameters can be modified to suit the NES CHO configuration. For example, cellDTRX-DCI- config It can be changed to cellES-DCI-config Furthermore, it can include configuration of the new DCI format 2_9 for activating / deactivating cell DTX / DRX configurations for one or more serving cells, or notify the serving cell that it is entering NES mode to trigger NES CHO enhancements. Similarly, cellDTRX-RNTI It can be changed to cellES-RNTIIt can also be used to configure RNTI values ​​to scramble the CRC of DCI format 2_9 used to activate and / or deactivate cell DTX / DRX, or to notify the serving cell that it is entering NES mode to trigger NES CHO enhancement.

[0055] Figure 4 The DCI 300 and specific RRC configurations according to some implementation schemes are shown.

[0056] The first UE (UE 1) can be configured with serving cell #1 as its PCell and serving cell #N as its SCell. Base station 108 can use RRC signaling to provide UE 1 with UE 1 RRC configuration 404. UE 1 RRC configuration 404 may include cell group configuration ( CellGroupConfig ) Information element (IE), which includes its PCell serving cell configuration ( ServingCellConfig(PCell) ) and its SCell serving cell configuration ( ServingCellConfig(SCell) ). ServingCellConfig(PCell) IE can include two positionInDCI parameters. The first parameter ( positionInDCI-cellDTRX This indicates the initial location of the cell DTX / DRX indication for UE 1's PCell within DCI 300. The second parameter ( positionInDCI-CHO This can indicate the starting location of the NES CHO indication for the PCell of UE1 within DCI 300. In this example, the NES CHO indication for block #N can be associated with the PCell of UE1. ServingCellConfig (SCell) IE can include only one positionInDCI parameter( positionInDCI-cellDTRX ), to indicate the starting location of the cell DTX / DRX indication of UE 1's SCell within DCI300.

[0057] The second UE (UE 2) can be configured with serving cell #N as its PCell and serving cell #1 as its SCell. Base station 108 can use RRC signaling to provide UE 2 RRC configuration 408 for UE 2. UE 2 RRC configuration 408 may include cell group configuration ( CellGroupConfig )IE, which includes its PCell serving cell configuration ( ServingCellConfig (PCell) ) and its SCell serving cell configuration ( ServingCellConfig(SCell) ). ServingCellConfig (PCell) IE can include two positionInDCI parameters. The first parameter ( positionInDCI-cellDTRXThis indicates the starting location of the cell DTX / DRX indication for UE 2's PCell within DCI 300. The second parameter ( positionInDCI- CHO This can indicate the starting location of the NES CHO indication for the PCell of UE2 within DCI 300. In this example, the NES CHO indication for block #N+m can be associated with the PCell of UE2. ServingCellConfig(SCell) IE can include only one positionInDCI parameter ( positionInDCI-cellDTRX ), to indicate the starting location of the cell DTX / DRX indication of UE 2's SCell within DCI 300.

[0058] For example, UE behavior when receiving NES CHO instructions via DCI 200 or 300 can be defined according to one or more of the following options.

[0059] In the first option, after UE 104 receives the NES CHO bit, UE 104 can identify which serving cell has entered NES mode. If the serving cell entering NES mode is UE 104's PCell or PSCell, UE 104 can trigger an NES CHO enhancement. This can include UE 104 performing the serving cell's NES CHO procedure by using relaxed CHO conditions, as described elsewhere in this document.

[0060] If UE 104 determines that its PCell or PSCell is not entering NES mode based on the NES CHO indication, the UE can perform the normal non-NES CHO procedure of the serving cell by using the normal non-relaxed CHO conditions.

[0061] If UE 104 determines that the serving cell for entering NES mode is UE 104's SCell based on the NES CHO indication, then UE 104 may not trigger the NES CHO enhancement.

[0062] In the second option, after UE 104 receives the NES CHO bit, UE 104 identifies which serving cell has entered NES mode. If the serving cell entering NES mode is within UE 104's MCG, UE 104 triggers an NES CHO enhancement in its PCell. This may also happen even if the serving cell entering NES mode is within the SCell of the MCG, as this could degrade the Quality of Service (QoS) experienced by UE 104.

[0063] If the serving cell entering NES mode is within the SCG of UE 104, UE 104 triggers a CHO enhancement for NES in its PSCell. This may also happen even if the serving cell entering NES mode is within the SCell of the SCG, as this could reduce the QoS experienced by UE 104.

[0064] As discussed above, the CHO procedure and the NES CHO procedure can be based on various Ax conditions, where "x" is an integer variable, which can be, for example, 3, 4, or 5. In some implementations, two Ax event conditions can be configured. The first Ax event condition can be associated with the normal CHO procedure, while the second Ax event condition can be associated with the NES CHO procedure.

[0065] In some implementations, two Ax event conditions are of the same type but have different thresholds. For example, both are A5 event conditions, but their (neighboring cell) thresholds are different. a5-Threshold2 They are different. In other implementations, the two Ax event conditions are of different types. For example, the first Ax event condition is an A5 event, and the second Ax event condition is an A4 event.

[0066] In some implementations, additional parameters can be added to the configuration signaling that indicates which of the two Ax event conditions is used for the NES CHO procedure. For example, the NES indication parameter ( NESecondExecutionCond Add underlined text to the RRC parameters. For example, you can add underlined text to the conditional reconfiguration of IE in TS38.331 v17.6.0 (2023-09) as follows. CondReconfigToAddMod ):

[0067]

[0068] In some implementation schemes, NEScondExecutionCond The Meas Id is used to indicate the application of its associated execution conditions after receiving the public L1 signaling DCI 2-9. This field only exists when two trigger events (MeasIds) condEventA3, condEventA4, or condEventA5 are configured for the candidate cell.

[0069] To achieve the UE behavior described above relative to option 1, the underlined text can be added to section 5.3.5.13.4 of TS38.331 as follows: 2> If an event within condTriggerConfig is configured with the NEScondExecutionCond of the target candidate cell in the stored condRRCReconfig: 3> If the L1 trigger signaling indicates that its PCell is entering NES mode and is configured with The event of NEScondExecutionCond is satisfied, or 3> If the L1 trigger signaling indicates that its PCell is not entering NES mode and the condTriggerConfig is in... Another event was satisfied : 4> Stored The target candidate cell associated with the condReconfigId in condRRCReconfig is considered the triggering cell; 4> Initiate conditional reconfiguration execution, as specified in 5.3.5.13.5.

[0070] To achieve the UE behavior described above relative to option 2, the underlined text can be added to section 5.3.5.13.4 of TS38.331 as follows: 2> If an event within condTriggerConfig is configured with the NEScondExecutionCond of the target candidate cell in the stored condRRCReconfig: 3> If L1 trigger signaling indicates that one of its MCG's serving cells is entering NES mode and is configured with The event of NEScondExecutionCond is satisfied, or 3> If L1 trigger signaling indicates that one of its SCG's serving cells is entering NES mode and is configured with The event of NEScondExecutionCond is satisfied, or 3> If L1 trigger signaling indicates that the serving cell is not entering NES mode and condTriggerConfig Another event within is satisfied: 4> The target candidate cell associated with the stored condRRCReconfigId is regarded as the triggering cell; 4> Initiate conditional reconfiguration execution, as specified in 5.3.5.13.5.

[0071] In some implementations, to limit the power consumption associated with UE 104 actively monitoring DCI over long periods, the network can configure a monitoring window. The monitoring window can be configured based on the cell DTX / DRX configuration.

[0072] Figure 5 An example of a monitoring configuration 500 based on some implementation schemes is shown.

[0073] Cell DTX / DRX configurations can be provided for each serving cell. In some implementations, to limit complexity, configurations can be restricted so that each MAC entity can configure a maximum of two cell DTX / DRX modes, and the two configured modes are aligned. Alignment of the two configured modes can be provided, wherein the start and slot offsets are common for both modes, and one periodicity is an integer multiple of the other periodicity.

[0074] Referring to monitoring configuration 500, UE 104 can be configured with a first DTX / DRX mode for serving cell 1 (serving cell 1 DTX / DRX mode) and a second DTX / DRX mode for serving cell 2 (serving cell 2 DTX / DRX mode). The serving cell 1 DTX / DRX mode can include a period (P1), an active duration (L1), and an inactive duration (P1-L1). The serving cell 2 DTX / DRX mode can include a period (P2), an active duration (L2), and an inactive duration (P2-L2).

[0075] To ensure alignment between the two patterns, P1 can be an integer multiple of P2 (e.g., P1 = n * P2, where n = 2, such as...). Figure 5 (as shown); and the start and slot offsets of the two modes can be the same.

[0076] The network (e.g., base station 108) can configure UE 104 with a monitoring window (in Figure 5 (Seen with crosshairs in the image) to monitor DCI (e.g., DCI format 2_9). The monitoring window can have a length of W time slots.

[0077] The network can be configured with a monitoring window featuring slot offset (Off) and period based on the maximum cell DTX / DRX cycle. The maximum cell DTX / DRX cycle can be configured as follows: N Integer multiple: The maximum cycle of two configured cell DTX / DRX modes (if two are configured) or the cycle of configured cell DTX / DRX modes (if only one is configured); or the maximum cycle of all cell DTX / DRX modes (e.g., two DTX / DRX modes can be configured for the UE for all serving cells) and all UE connectivity mode DRX (CDRX) modes.

[0078] The slot offset (Off) configures the number of slots between the end time of the monitoring window and the start time of the activity duration of the cell's DTX / DRX with the largest cycle. Therefore, a monitoring window that occurs between the activity durations of DTX / DRX modes with larger cycle periods may not exist during the activity duration of a DTX / DRX mode with smaller cycle periods. As shown in the figure, the slot offset can be configured relative to the start time of the activity duration of the serving cell 1 DTX / DRX mode, because it has a larger cycle period. A monitoring window may not exist before the second activity duration of the serving cell 2 DTX / DRX mode.

[0079] Figure 6 An operational flow / algorithm structure 600 according to some implementation schemes is illustrated. The operational flow / algorithm structure 600 may be executed or implemented by a network (e.g., base station 108, base station 900) or its components (e.g., processor 904).

[0080] The operation flow / algorithm structure 600 may include: at 604, sending RRC signaling with one or more positionInDCI indications. positionInDCI Instructions can be sent in the serving cell configuration to configure the UE with various serving cells (e.g., PCell, PSCell, or SCell), as discussed elsewhere in this document.

[0081] The operation procedure / algorithm structure 600 may further include: at 608, sending a DCI with a cell DTX / DRX indication and an NES CHO indication. The cell DTX / DRX indication can indicate whether the DTX / DRX configuration is activated or deactivated. The cell DTX / DRX indication may include one or two bits. The NES CHO indication may include one bit to indicate whether the serving cell is entering NES mode.

[0082] In some implementations, the cell DTX / DRX indication and the NES CHO indication are contained in a single block. This single block can be indicated by a positionInDCI indication sent in RRC signaling at position 604. The NES CHO indication may immediately follow the cell DTX / DRX indication.

[0083] In some implementations, the cell DTX / DRX indication and NES CHO indication are in different blocks. For example, the DTX / DRX indication can be sent by the first signal in the RRC signaling at 604. positionInDCI The instruction is in the first block indicated, and the NES CHO instruction can be sent in the second block by the RRC signaling at 604. positionInDCI The instruction refers to the second block. One or more blocks may be located between the first and second blocks.

[0084] In some implementations, the DCI may be a group common DCI with DCI format 2_9, and may include indications of multiple serving cells configured in the network.

[0085] In some implementations, RRC signaling can be used by the network to configure multiple event conditions. The RRC signaling may also include an NES indication to identify which of the multiple event conditions will be used to trigger an NES CHO procedure. For example, consider configuring two event conditions. A first event condition may be associated with a first type and a first threshold, and a second event condition may be associated with a second type and a second threshold. The first type may be equal to the second type, while the first threshold may be different from the second threshold; or the first type may be different from the second type, while the first threshold may be equal to (or different from) the second threshold. The NES indication may indicate that the first (or second) event condition will be used to trigger an NES CHO procedure, while the other event condition will be used to trigger a non-NES or normal CHO procedure.

[0086] In some implementations, RRC signaling may be used by the network to provide window configuration to instruct the UE to monitor the window in which DCI will be performed. Window configuration may include slot offsets to provide multiple slots between the end of the window and the start of the activity duration of the cell DTX / DRX mode. The window may be configured with an offset equal to... N * cellDTX / DRX The period of , where N is an integer, and cellDTX / DRX Yes: the maximum value of one or more cell DTX / DRX cycles of the serving cell; or the maximum value of one or more cell DTX / DRX cycles of the serving cell and the UE's connection mode DRX (CDRX) cycle.

[0087] It can be noted that the RRC signaling transmitting the various parameters described herein may include one or more RRC messages that can be transmitted together or at different times. For example, it may be transmitted in the first RRC message. positionInDCI The parameters can be transmitted in the second RRC message to provide configuration information for the event conditions, and in the third RRC message to provide window configuration.

[0088] Figure 7 An operational flow / algorithm structure 700 according to some implementation schemes is illustrated. The operational flow / algorithm structure 700 may be executed or implemented by a UE (e.g., UE 104 or UE 800) or its components (e.g., processor 804).

[0089] Operation flow / algorithm structure 700 may include: at 704, receiving a location in one or more DCIs ( positionInDCI ) indicates the RRC signaling. positionInDCIInstructions can be sent in the serving cell configuration to configure the UE with various serving cells (e.g., PCell, PSCell, or SCell), as discussed elsewhere in this document.

[0090] The operation procedure / algorithm structure 700 may further include: at 708, receiving a DCI with a cell DTX / DRX indication and an NES CHO indication. The cell DTX / DRX indication can indicate whether the DTX / DRX configuration is activated or deactivated. The cell DTX / DRX indication may include one or two bits. The NES CHO indication may include one bit to indicate whether the serving cell is entering NES mode.

[0091] In some implementations, the cell DTX / DRX indication and NES CHO indication are in one block. This single block can be received in RRC signaling at 704. positionInDCI The NES CHO instruction can follow immediately after the cell DTX / DRX instruction.

[0092] In some implementations, the cell DTX / DRX indication and NES CHO indication are in different blocks. For example, the DTX / DRX indication can be received by the first [block] in the RRC signaling at 704. positionInDCI The instruction is in the first block indicated, and the NES CHO instruction can be received in the second RRC signaling at 704. positionInDCI The instruction refers to the second block. One or more blocks may be located between the first and second blocks.

[0093] In some implementations, the DCI may be a group common DCI with DCI format 2_9, and may include indications of multiple serving cells configured in the network.

[0094] In some implementations, RRC signaling can be used by the network to configure multiple event conditions. The RRC signaling may also include an NES indication to identify which of the multiple event conditions will be used to trigger an NES CHO procedure. For example, consider configuring two event conditions. A first event condition may be associated with a first type and a first threshold, and a second event condition may be associated with a second type and a second threshold. The first type may be equal to the second type, while the first threshold may be different from the second threshold; or the first type may be different from the second type, while the first threshold may be equal to (or different from) the second threshold. The NES indication may indicate that the first (or second) event condition will be used to trigger an NES CHO procedure, while the other event condition will be used to trigger a non-NES or normal CHO procedure.

[0095] In some implementations, RRC signaling may be used by the network to provide window configuration to instruct the UE to monitor the window in which DCI will be performed. Window configuration may include slot offsets to provide multiple slots between the end of the window and the start of the activity duration of the cell DTX / DRX mode. The window may be configured with an offset equal to... N * cellDTX / DRX The period of , where N is an integer, and cellDTX / DRX Yes: the maximum value of one or more cell DTX / DRX cycles of the serving cell; or the maximum value of one or more cell DTX / DRX cycles of the serving cell and the UE's connection mode DRX (CDRX) cycle.

[0096] It can be noted that the RRC signaling transmitting the various parameters described herein may include one or more RRC messages that can be received together or at different times. For example, it may be received in the first RRC message. positionInDCI The parameters can receive event condition configuration information in the second RRC message and window configuration in the third RRC message.

[0097] The operation flow / algorithm structure 700 may also include: at 712, executing a CHO procedure or an NES CHO procedure. Depending on the implementation, which procedure can be executed may be based on whether the NES CHO indication indicates that the serving cell is entering NES mode and the nature of the serving cell itself (e.g., whether it is a PCell, PSCell, SCell, MCG cell, or SCG cell).

[0098] In some implementations, if the UE determines that the serving cell is the UE's PCell or PSCell and the NES CHO indication indicates that the serving cell is entering NES mode, the UE can perform the serving cell's NES CHO procedure.

[0099] In some implementations, if the UE determines that the serving cell is the UE's SCell and the NES CHO indication indicates that the serving cell is entering NES mode, the UE can perform a CHO procedure for the UE's PCell or PSCell.

[0100] In some implementations, if the UE determines that the serving cell is within the UE's MCG and the NES CHO indicates that the serving cell is entering NES mode, the UE can perform the NES CHO procedure of the UE's PCell based on the determination that the serving cell is within the MCG and is entering NES mode.

[0101] In some implementations, if the UE determines that the serving cell is within the UE's SCG and the NES CHO indicates that the serving cell is entering NES mode, the UE can perform the NES CHO procedure of the UE's PSCell based on the determination that the serving cell is within the SCG and is entering NES mode.

[0102] In some implementations, if the UE determines that the NES CHO indicator indicates the serving cell is entering NES mode and the NES indicator indicates that an event condition associated with NES has been met, the UE can perform the NES CHO procedure based on the determination that the serving cell is entering NES mode and the determination that the event condition has been met. In some implementations, if the serving cell is the UE's PCell, the NES CHO procedure can be performed for the PCell. In some implementations, if the serving cell is in an MCG, the NES CHO procedure can be performed for the UE's PCell. In some implementations, if the serving cell is in an SCG, the NES CHO procedure can be performed for the UE's PSCell.

[0103] Figure 8 An example of a UE 800 according to some implementation schemes is shown. UE 800 may be similar to... Figure 1 It is compatible with UE 84 and is essentially interchangeable with it.

[0104] UE 800 can be any mobile or non-mobile computing device, such as, for example, a mobile phone, computer, tablet, XR device, glasses, industrial wireless sensors (e.g., microphone, carbon dioxide sensor, pressure sensor, humidity sensor, thermometer, motion sensor, accelerometer, laser scanner, fluid level sensor, inventory sensor, voltmeter / ammeter, or actuator), video surveillance / monitoring device (e.g., camera or camcorder), wearable device (e.g., smartwatch), or Internet of Things device.

[0105] UE 800 may include a processor 804, RF interface circuitry 808, memory / storage device 812, user interface 816, sensor 820, drive circuitry 822, power management integrated circuit (PMIC) 824, antenna structure 826, and battery 828. The components of UE 800 may be implemented as integrated circuits (ICs), portions of integrated circuits, discrete electronic devices or other modules, logic components, hardware, software, firmware, or combinations thereof. Figure 8 The block diagram is intended to show a high-level view of some of the components of the UE 800. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other specific implementations.

[0106] The components of UE 800 can be coupled to a variety of other components via one or more interconnects 832, which can represent any type of interface, input / output, bus (local, system, or extension), transmit line, trace, or optical connector, allowing various circuit components (on common or different chips or chipsets) to interact with each other.

[0107] Processor 804 may include processor circuitry, such as, for example, baseband processor circuitry (BB) 804A, central processing unit circuitry (CPU) 804B, and graphics processing unit circuitry (GPU) 804C. Processor 804 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions (such as program code, software modules, or functional processes from memory / storage device 812) to cause UE 800 to perform the operations described herein.

[0108] Processor 804 can perform operations associated with receiving RRC signaling and DCI and accordingly executing NES CHO procedures, as described herein. For example, processor 804 can perform operation flow / algorithm structure 700 or another operation described herein.

[0109] In some implementations, the baseband processor circuit 804A can access the communication protocol stack 836 in the memory / storage device 812 to communicate over a 3GPP-compliant network. Generally, the baseband processor circuit 804A can access the communication protocol stack 836 to: perform user plane functions at the PHY layer, MAC layer, RLC sublayer, PDCP sublayer, SDAP sublayer, and upper layers; and perform control plane functions at the PHY layer, MAC layer, RLC sublayer, PDCP sublayer, RRC layer, and NAS layer. In some implementations, PHY layer operations may additionally / optionally be performed by components of the RF interface circuit 808.

[0110] The baseband processor circuit 804A can generate or process baseband signals or waveforms carrying information in a 3GPP-compliant network. In some implementations, the waveforms used for NR can be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and Discrete Fourier Transform Extended OFDM (DFT-S-OFDM) in the uplink.

[0111] Memory / storage device 812 may include one or more non-transitory computer-readable media, including instructions (e.g., communication protocol stack 836) that can be executed by one or more processors in processor 804 to cause UE 800 to perform the various operations described herein. Memory / storage device 812 includes any type of volatile or non-volatile memory that can be distributed throughout UE 800. In some embodiments, some memory / storage devices in memory / storage device 812 may be located on processor 804 itself (e.g., L1 cache and L2 cache), while other memory / storage devices 812 may be located external to processor 804 but accessible via a memory interface. Memory / storage device 812 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0112] RF interface circuitry 808 may include transceiver circuitry and a radio frequency front-end module (RFEM) that allows UE 800 to communicate with other devices via a radio access network. RF interface circuitry 808 may include various components arranged in the transmit or receive path. These components may include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, and control circuitry.

[0113] In the receiving path, the RFEM can receive the radiated signal from the air interface via antenna structure 826, and continue to filter and amplify the signal (using a low-noise amplifier). This signal can be provided to the receiver of the transceiver, which down-converts the RF signal into a baseband signal, which is then provided to the baseband processor of processor 804.

[0114] In the transmission path, the transceiver's transmitter up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM can then amplify the RF signal using a power amplifier before it is radiated across the air interface via antenna 826.

[0115] In various implementations, the RF interface circuit 808 can be configured to transmit / receive signals in a manner compatible with NR access technologies.

[0116] Antenna 826 may include antenna elements to convert electrical signals into radio waves for propagation through the air, and to convert received radio waves back into electrical signals. These antenna elements may be arranged in one or more antenna panels. Antenna 826 may have antenna panels that are omnidirectional, directional, or a combination thereof to enable beamforming and multiple-input multiple-output (MIMO) communication. Antenna 826 may include a microstrip antenna, patch antenna, phased array antenna, or a printed antenna fabricated on the surface of one or more printed circuit boards. Antenna 826 may have one or more panels designed for a specific frequency band, including bands in FR1 or FR2.

[0117] User interface circuitry 816 includes various input / output (I / O) devices designed to enable users to interact with UE 800. User interface 816 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual components for accepting input, particularly including one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touchscreen, a microphone, a scanner, a headset, etc. Output device circuitry includes any physical or virtual components for displaying information or otherwise conveying information, such as sensor readings, actuator positions, or other similar information. Output device circuitry may include any number or combination of audio or visual displays, particularly including one or more simple visual outputs / indicators (e.g., binary status indicators, such as light-emitting diodes (LEDs)) and multi-character visual outputs, or more complex outputs, such as display devices or touchscreens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, and projectors), wherein the output of characters, graphics, multimedia objects, etc., is generated or produced through the operation of UE 800.

[0118] Sensor 820 may include devices, modules, or subsystems designed to detect events or changes in their environment and transmit information about the detected events (sensor data) to other devices, modules, or subsystems. Examples of such sensors include: inertial measurement units including accelerometers, gyroscopes, or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEM) including 3-axis accelerometers, 3-axis gyroscopes, or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless aperture sensors); light detection and ranging sensors; proximity sensors (e.g., infrared radiation detectors); depth sensors; ambient light sensors; ultrasonic transceivers; and microphones or other similar audio capture devices.

[0119] The driving circuitry 822 may include software and hardware elements that operate to control specific devices embedded in, attached to, or otherwise communicatively coupled to the UE 800. The driving circuitry 822 may include individual drivers that allow other components to interact with or control various I / O devices that may exist within or be connected to the UE 800. For example, the driving circuitry 822 may include circuitry for facilitating the coupling of a Universal Integrated Circuit Card (UICC) or a Universal Subscriber Identity Module (USIM) to the UE 800. Furthermore, the driving circuitry 822 may include: a display driver for controlling and allowing access to a display device; a touchscreen driver for controlling and allowing access to a touchscreen interface; a sensor driver for obtaining sensor readings from sensor circuitry 820 and controlling and allowing access to sensor circuitry 820; a driver for obtaining actuator positioning of electromechanical components or controlling and allowing access to electromechanical components; a camera driver for controlling and allowing access to an embedded image capture device; and an audio driver for controlling and allowing access to one or more audio devices.

[0120] The PMIC 824 manages the power supplied to various components of the UE 800. In particular, relative to the processor 804, the PMIC 824 controls power source selection, voltage scaling, battery charging, or DC-DC conversion.

[0121] In some implementations, the PMIC 824 may be controlled or otherwise incorporated into various power-saving mechanisms of the UE 800, including DRX, as discussed herein.

[0122] Battery 828 can power UE 800, but in some examples, UE 800 may be installed and deployed in a fixed location and may have a power source coupled to the power grid. Battery 828 may be a lithium-ion battery, a metal-air battery (such as zinc-air batteries, aluminum-air batteries, lithium-air batteries, etc.). In some specific implementations, such as in vehicle-based applications, battery 828 may be a typical lead-acid automotive battery.

[0123] Figure 9 Base station 900 is illustrated according to some implementation schemes. Base station 900 may be similar to base station 108 and is substantially interchangeable with it.

[0124] The base station 900 may include a processor 904, an RF interface circuit 908, a core network (CN) interface circuit 912, a memory / storage circuit 916, and an antenna structure 926.

[0125] Processor 904 may perform operations associated with generating and transmitting RRC signaling and DCI, as described herein. For example, processor 904 may perform operation flow / algorithm structure 600 or another operation described herein.

[0126] The components of base station 900 can be coupled to various other components via one or more interconnects 928.

[0127] The processor 904, RF interface circuit 908, memory / storage device circuit 916 (including communication protocol stack 910), antenna structure 926, and interconnect 928 can be similar to those relative to... Figure 8 Similar named elements are shown and described.

[0128] The CN interface circuit 912 can provide connectivity to a core network (e.g., a 5GC using a 5G core network (5GC) compatible network interface protocol, such as carrier Ethernet or some other suitable protocol). Network connectivity can be provided to / from base station 900 via fiber optic or wireless backhaul. The CN interface circuit 912 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuit 912 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0129] In some implementations, base station 900 may be coupled to transmit-receive point (TRP) using antenna structure 926, CN interface circuitry or other interface circuitry.

[0130] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0131] For one or more aspects, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods as described in the Embodiments section below. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the embodiments described below. Similarly, circuitry associated with the UE, base station, network element, etc., described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the embodiments described below in the Embodiments section.

[0132] Example Further exemplary aspects are provided in the following sections.

[0133] Example 1 includes a method to be implemented by a base station, the method comprising: transmitting Radio Resource Control (RRC) signaling to provide a location indication in one or more Downlink Control Information (DCIs); and transmitting Downlink Control Information (DCIs) including a plurality of indications associated with a serving cell, the plurality of indications including a cell DTX / DRX indication for activating or deactivating discontinuous transmission (DTX) or discontinuous reception (DRX) of the serving cell, and an NES Conditional Handover (CHO) indication for indicating whether the serving cell is entering a Network Energy Saving (NES) mode, wherein: the cell DTX / DRX indication and the NES CHO indication are in a block indicated by a location indication in one of the one or more DCIs; or the cell DTX / DRX indication is in a first block indicated by a first location indication in one of the one or more DCIs, and the NES CHO indication is in a second block indicated by a second location indication in one of the one or more DCIs.

[0134] Example 2 includes the method according to Example 1 or some other embodiment herein, wherein the cell DTX / DRX indication and the NES CHO indication are in a block indicated by one of the one or more DCI location indications.

[0135] Example 3 includes the method according to Example 2 or some other embodiment herein, wherein the block includes one or more DTX / DRX indications, the one or more DTX / DRX indications include the DTX / DRX indications, and the NES CHO indication will immediately follow the one or more DTX / DRX indications in the block.

[0136] Example 4 includes the method according to Example 1 or some other embodiment herein, wherein the cell DTX / DRX indication is in a first block indicated by a first DCI location indication among the one or more DCI location indications, and the NES CHO indication is in a second block indicated by a second DCI location indication among the one or more DCI location indications.

[0137] Example 5 includes the method according to Example 1 or some other embodiment herein, wherein the serving cell is the UE’s primary serving cell (PCell) or primary and secondary serving cell (PSCell).

[0138] Example 6 includes the method according to Example 5 or some other embodiment herein, wherein the RRC signaling includes the serving cell configuration of the PCell or the PSCell, and the location indication in the first DCI and the location indication in the second DCI are in the serving cell configuration.

[0139] Example 7 includes the method according to Example 4 or some other embodiment herein, wherein the DCI includes one or more blocks between the first block and the second block.

[0140] Example 2 includes the method according to Example 1 or some other embodiment herein, wherein the RRC signaling further provides an NES indication for identifying event conditions from a plurality of configured event conditions that will be used to trigger the NES CHO process.

[0141] Example 9 includes the method according to Example 8 or some other embodiment of this document, wherein: the plurality of configured event conditions include a first event condition associated with a first type and a first threshold and a second event condition associated with a second type and a second threshold; and the first type is equal to the second type and the first threshold is different from the second threshold; the first type is different from the second type and the first threshold is equal to the second threshold; or the first type is different from the second type and the first threshold is different from the second threshold.

[0142] Example 10 includes the method according to Example 1 or some other embodiment herein, wherein the RRC signaling further provides: window configuration to indicate the window in which the UE will monitor the DCI.

[0143] Example 11 includes the method according to Example 10 or some other embodiment herein, wherein the window configuration includes a slot offset to provide multiple slots between the end of the window and the start of the activity duration of the cell DTX / DRX mode.

[0144] Example 12 includes the method according to Example 10 or 11 or some other embodiment herein, wherein the window has a period equal to N * cellDTX / DRX, where N is an integer, and cellDTX / DRX is: the maximum value of one or more cell DTX / DRX cycles of the serving cell; or the maximum value of one or more cell DTX / DRX cycles of the serving cell and the connection mode DRX (CDRX) cycle of the UE.

[0145] Example 13 includes a method to be implemented by a user equipment (UE), the method comprising: receiving radio resource control (RRC) signaling to provide a location indication in one or more downlink control information (DCIs); and receiving downlink control information (DCIs) including a plurality of indications associated with a serving cell, the plurality of indications including a cell DTX / DRX indication for activating or deactivating discontinuous transmission (DTX) or discontinuous reception (DRX) of the serving cell, and an NES CHO indication for indicating whether Network Energy Saving (NES) Conditional Handover (CHO) is configured for the serving cell, wherein: the cell DTX / DRX indication and the NES CHO indication are in a block indicated by a location indication in one of the one or more location indications in the DCIs; or the cell DTX / DRX indication is in a first block indicated by a first location indication in the one or more location indications in the DCIs, and the NES CHO indication is in a second block indicated by a second location indication in the one or more location indications in the DCIs.

[0146] Example 14 includes the method according to Example 13 or some other embodiment herein, wherein the serving cell is the UE's primary serving cell (PCell) or primary secondary cell (PSCell), and the method further includes: determining, based on the NES CHO indication, that the serving cell is entering NES mode; and performing the NES CHO procedure based on the determination that the serving cell is entering NES mode.

[0147] Example 15 includes the method according to Example 13 or some other embodiment herein, wherein the serving cell is the secondary serving cell (SCell) of the UE, and the method further includes: determining that the SCell is entering NES mode based on the NES CHO indication; and performing a CHO procedure for the primary serving cell (PCell) or primary-secondary cell (PSCell) of the UE.

[0148] Example 16 includes the method according to Example 13 or some other embodiment herein, the method further comprising: determining that the serving cell is within the primary cell group (MCG) of the UE; determining that the serving cell is entering NES mode based on the NES CHO indication; and performing an NES CHO procedure for the primary serving cell (PCell) of the UE based on the determination that the serving cell is within the MCG and is entering NES mode.

[0149] Example 17 includes the method according to Example 13 or some other embodiment herein, the method further comprising: determining that the serving cell is within the secondary cell group (SCG) of the UE; determining that the serving cell is entering NES mode based on the NES CHO indication; and performing an NES CHO procedure for the primary and secondary serving cells (PSCell) of the UE based on the determination that the serving cell is within the SCG and is entering NES mode.

[0150] Example 18 includes the method according to Example 13 or some other embodiment herein, wherein the RRC signaling further provides an NES indication for identifying an event condition from a plurality of configured event conditions that will be used to trigger an NES CHO procedure, and the method further includes: determining, based on the NES CHO indication, that the serving cell is entering NES mode; determining that the event condition is met; and performing the NES CHO procedure based on the determination that the serving cell is entering NES mode and the determination that the event condition is met.

[0151] Example 19 includes the method according to Example 18 or some other embodiment herein, wherein: the serving cell is the primary cell (PCell) of the UE, and the method includes: performing the NES CHO procedure for the PCell; the serving cell is in a primary cell group (MCG), and the method includes: performing the NES CHO procedure for the primary serving cell (PCell) of the UE; or the serving cell is in a secondary cell group (SCG), and the method includes: performing the NES CHO procedure for the primary and secondary serving cells (PSCell) of the UE.

[0152] Example 20 includes the method according to Example 13 or some other embodiment herein, wherein the RRC signaling further provides window configuration to indicate a window, and the method further includes: monitoring the DCI in the window.

[0153] Example 21 includes the method according to Example 20 or some other embodiment herein, wherein the window configuration includes a slot offset to provide multiple slots between the end of the window and the start of the cell DTX / DRX activity duration.

[0154] Example 22 includes the method according to Example 10 or 11 or some other embodiment herein, wherein the window has a period equal to N * cellDTX / DRX, where N is an integer, and cellDTX / DRX is: the maximum value of one or more cell DTX / DRX cycles of the serving cell; or the maximum value of one or more cell DTX / DRX cycles of the serving cell and the connection mode DRX (CDRX) cycle of the UE.

[0155] Another embodiment may include an apparatus comprising logic components, modules, or circuitry for performing one or more elements of the methods described or associated with any of the embodiments 1 to 22 or any other methods or processes described herein.

[0156] Another embodiment may include methods, techniques or processes as described or associated with any of the embodiments in or in any part of or in connection with them.

[0157] Another embodiment may include an apparatus comprising: one or more processors; and one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform the methods, techniques, or processes described or associated with any of the embodiments or portions thereof in Embodiments 1 to 22.

[0158] Another embodiment includes signals as described or associated with any of the embodiments 1 to 22, or with any part or component thereof.

[0159] Another embodiment may include datagrams, information elements, packets, frames, segments, PDUs, or messages as described or associated with any of the embodiments 1 to 22 or in part or in part of them or otherwise described in this disclosure.

[0160] Another embodiment may include a signal encoded with data as described or associated with any of the embodiments 1 to 22 or in part or in connection with them or otherwise described in this disclosure.

[0161] Another embodiment may include signals encoded as datagrams, IEs, packets, frames, segments, PDUs, or messages as described or associated with any of the embodiments 1 to 22 or in part or in connection with them or otherwise described in this disclosure.

[0162] Another embodiment may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform the methods, techniques, or processes described or associated with any of the embodiments or parts thereof in Embodiments 1 to 22.

[0163] Another embodiment may include a computer program comprising instructions, wherein execution of the program by a processing element will cause the processing element to perform the methods, techniques, or processes described or associated with any of the embodiments or portions thereof in Embodiments 1 to 22.

[0164] Another embodiment may include signals in a wireless network as shown and described herein.

[0165] Another embodiment may include a method for communicating in a wireless network as shown and described herein.

[0166] Another embodiment may include a system for providing wireless communication as shown and described herein.

[0167] Another embodiment may include a device for providing wireless communication as shown and described herein.

[0168] Unless otherwise expressly stated, any of the embodiments described above may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific embodiments provides illustration and description, but is not intended to be exhaustive or to limit the scope of the aspects to the precise forms disclosed. In view of the teachings above, modifications and variations are possible, or modifications and variations may be obtained from practice in various aspects.

[0169] Although the foregoing aspects have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the foregoing disclosure is fully understood. It is intended that the following claims be construed as encompassing all such variations and modifications.

Claims

1. One or more computer-readable media, the one or more computer-readable media having instructions that, when executed, cause a base station to: Send Radio Resource Control (RRC) signaling to provide a location indication in one or more downlink control information (DCI); and The system transmits downlink control information (DCI) that includes multiple indications associated with the serving cell, including a cell DTX / DRX indication for activating or deactivating discontinuous transmission (DTX) or discontinuous reception (DRX) of the serving cell, and an NES conditional handover (CHO) indication for indicating whether the serving cell is entering network power saving (NES) mode. in: The cell DTX / DRX indication and the NES CHO indication are in a block indicated by one of the location indications in one of the one or more DCIs; or The cell DTX / DRX indication is in a first block indicated by a first DCI location indication among the one or more DCI location indications, and the NES CHO indication is in a second block indicated by a second DCI location indication among the one or more DCI location indications.

2. The computer-readable medium of claim 1, wherein the cell DTX / DRX indication and the NES CHO indication are in a block indicated by one of the DCI positioning indications of the one or more DCIs.

3. The computer-readable medium of claim 2, wherein the block includes one or more DTX / DRX indicators, the one or more DTX / DRX indicators including the DTX / DRX indicators, and the NES CHO indicator immediately follows the one or more DTX / DRX indicators in the block.

4. The computer-readable medium of claim 1, wherein the cell DTX / DRX indication is in a first block indicated by a first DCI positioning indication among the one or more DCI positioning indications, and the NES CHO indication is in a second block indicated by a second DCI positioning indication among the one or more DCI positioning indications.

5. The computer-readable medium according to claim 4, wherein the serving cell is the UE's primary serving cell (PCell) or primary-secondary serving cell (PSCell).

6. The computer-readable medium of claim 5, wherein the RRC signaling includes the serving cell configuration of the PCell or the PSCell, and the location indication in the first DCI and the location indication in the second DCI are in the serving cell configuration.

7. The computer-readable medium of claim 4, wherein the DCI comprises one or more blocks between the first block and the second block.

8. The computer-readable medium of claim 1, wherein the RRC signaling further provides: The NES indicator is used to identify the event conditions from multiple configured event conditions that will be used to trigger the NES CHO process.

9. The computer-readable medium according to claim 8, wherein: The multiple configured event conditions include a first event condition associated with a first type and a first threshold, and a second event condition associated with a second type and a second threshold; and The first type is equal to the second type, and the first threshold is different from the second threshold; the first type is different from the second type, and the first threshold is equal to the second threshold; or the first type is different from the second type, and the first threshold is different from the second threshold.

10. The computer-readable medium of claim 1, wherein the RRC signaling further provides: Window configuration to indicate the window in which the UE will monitor the DCI.

11. The computer-readable medium of claim 10, wherein the window configuration includes a time slot offset to provide a plurality of time slots between the end of the window and the start of the activity duration of the cell DTX / DRX mode.

12. The computer-readable medium of claim 10 or 11, wherein the window has an area equal to N * cellDTX / DRX The cycle, in which N It is an integer, and cellDTX / DRX Yes: the maximum value of one or more cell DTX / DRX cycles of the serving cell; or the maximum value of one or more cell DTX / DRX cycles of the serving cell and the connection mode DRX (CDRX) cycle of the UE.

13. A method implemented by a user equipment (UE), the method comprising: Receive Radio Resource Control (RRC) signaling to provide location indications in one or more downlink control information (DCI); as well as Receive downlink control information (DCI) including multiple indications associated with the serving cell, such as a cell DTX / DRX indication for activating or deactivating discontinuous transmission (DTX) or discontinuous reception (DRX) of the serving cell, and an NES CHO indication for indicating whether Network Energy Saving (NES) Conditional Handover (CHO) is configured for the serving cell. in: The cell DTX / DRX indication and the NES CHO indication are in a block indicated by one of the location indications in one of the one or more DCIs; or The cell DTX / DRX indication is in a first block indicated by a first DCI location indication among the one or more DCI location indications, and the NES CHO indication is in a second block indicated by a second DCI location indication among the one or more DCI location indications.

14. The method of claim 13, wherein the serving cell is the primary serving cell (PCell) or primary secondary cell (PSCell) of the UE, and the method further comprises: The serving cell is determined to be entering NES mode based on the NES CHO instruction. as well as Based on the determination that the serving cell is entering NES mode, the NES CHO process is executed.

15. The method of claim 13, wherein the serving cell is a secondary serving cell (SCell) of the UE, and the method further comprises: The NES CHO instruction is used to determine that the SCell is entering NES mode; as well as The CHO procedure is performed for the UE's primary serving cell (PCell) or primary secondary cell (PSCell).

16. The method according to claim 13, further comprising: The serving cell is determined to be within the primary cell group (MCG) of the UE; The serving cell is determined to be entering NES mode based on the NES CHO instruction. as well as Based on the determination that the serving cell is within the MCG and is entering the NES mode, an NES CHO procedure is performed for the UE's primary serving cell (PCell).

17. The method according to claim 13, further comprising: The serving cell is determined to be within the UE's secondary cell group (SCG); The serving cell is determined to be entering NES mode based on the NES CHO instruction. as well as Based on the determination that the serving cell is within the SCG and is entering the NES mode, an NES CHO procedure is performed for the UE's primary and secondary serving cells (PSCell).

18. The method of claim 13, wherein the RRC signaling further provides an NES indication for identifying event conditions from a plurality of configured event conditions that will be used to trigger the NES CHO procedure, and the method further comprises: The serving cell is determined to be entering NES mode based on the NES CHO instruction. It is determined that the event condition is met; as well as The NES CHO process is executed based on the determination that the serving cell is entering the NES mode and the determination that the event condition is met.

19. The method of claim 18, wherein: The serving cell is the primary cell (PCell) of the UE, and the method includes performing the NES CHO procedure for the PCell; The serving cell is in the primary cell group (MCG), and the method includes performing the NES CHO procedure for the primary serving cell (PCell) of the UE; or The serving cell is in a secondary cell group (SCG), and the method includes performing the NES CHO procedure for the primary and secondary serving cells (PSCell) of the UE.

20. The method of claim 13, wherein the RRC signaling further provides window configuration to indicate the window, and the method further comprises: The DCI is monitored within the window.

21. The method of claim 20, wherein the window configuration includes a time slot offset to provide a plurality of time slots between the end of the window and the start of the cell DTX / DRX activity duration.

22. The method of claim 10 or 11, wherein the window has an area equal to N * cellDTX / DRX The cycle, in which N It is an integer, and cellDTX / DRX Yes: the maximum value of one or more cell DTX / DRX cycles of the serving cell; or the maximum value of one or more cell DTX / DRX cycles of the serving cell and the connection mode DRX (CDRX) cycle of the UE.

Images