Method by user equipment, apparatus, storage medium, method by base station, and base station

Abstract

A UE may: receive a first parameter regarding a start bit position of a specific DCI format for a serving cell; detect the specific DCI format; and if i) a second parameter regarding a CHO-related bit is configured and ii) the serving cell is a primary cell (PCell) for the UE, determine whether or not to trigger a CHO procedure including evaluating a CHO condition, on the basis of a CHO-related field within an information block for the serving cell within the specific DCI format.

Description

Methods, devices and storage media by user devices, and methods and base stations by base stations

[0001] This specification relates to wireless communication systems.

[0002] Various devices and technologies, such as machine-to-machine (M2M) communication, machine-type communication (MTC), and smartphones and tablet PCs (personal computers) that require high data transmission rates, are emerging and becoming widespread. Consequently, the amount of data required to be processed on cellular networks is rapidly increasing. To meet this rapidly increasing data processing demand, technologies such as carrier aggregation and cognitive radio are being developed to efficiently utilize more frequency bands, while multi-antenna technology and multi-BS cooperation technology are being developed to increase the data capacity transmitted within a limited frequency range.

[0003] As more and more communication devices demand greater capacity, the need for enhanced mobile broadband (eMBB) communications is emerging, surpassing legacy radio access technology (RAT). Furthermore, massive machine type communication (mMTC), which connects multiple devices and objects to provide diverse services anytime, anywhere, is a key issue to be considered in next-generation communications.

[0004] Additionally, discussions are underway on communication systems designed to accommodate reliability- and latency-sensitive services and user equipment (UE). The introduction of next-generation wireless access technologies is being discussed, including enhanced mobile broadband (eMBB), mMTC, and ultra-reliable and low latency communication (URLLC).

[0005] As the number of services / UEs that a network must support rapidly increases, the need for energy conservation in the network as well as power conservation in the UE is also gradually increasing.

[0006] One technical task of this specification is to provide methods and procedures for network energy conservation.

[0007] Another technical challenge of this specification is to provide methods and procedures for efficiently triggering handover related procedures.

[0008] The technical tasks that this specification aims to achieve are not limited to the technical tasks mentioned above, and other technical tasks that are not mentioned will be clearly understood by those skilled in the art related to this specification from the detailed description below.

[0009] In one aspect of this specification, a method by a user equipment (UE) is provided.

[0010] In another aspect of the present disclosure, a device is provided. The device includes at least one processor; and at least one memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations for a user equipment (UE).

[0011] In another aspect of the present disclosure, a computer-readable, non-transitory storage medium is provided, wherein the storage medium stores at least one program code comprising instructions that, when executed, cause at least one processor to perform operations for a user equipment (UE).

[0012] The method by the UE, or the operations for the UE, may include: receiving a first parameter regarding a start bit position of a specific downlink control information (DCI) format for a serving cell; detecting the specific DCI format; and determining whether to trigger a CHO procedure, the CHO procedure including evaluating a CHO condition based on a CHO-related field in an information block for the serving cell within the specific DCI format, if i) a second parameter regarding a conditional handover (CHO)-related bit is set and ii) the serving cell is a primary cell (PCell) of the UE.

[0013] In another aspect of the present specification, a method by a base station (BS) is provided.

[0014] In another aspect of the present disclosure, a base station (BS) is provided. The BS includes at least one processor; and at least one memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations for the BS.

[0015] The method by the BS, or the operations for the BS, include: transmitting a first parameter regarding a start bit position of a specific downlink control information (DCI) format for a serving cell of a user equipment (UE); and transmitting the specific DCI format, wherein i) a second parameter regarding a conditional handover (CHO) related bit is set, and ii) based on the serving cell being a primary cell (PCell) of the UE, an information block for the serving cell in the specific DCI format may include a CHO related field.

[0016] In each aspect of the present specification, i) the second parameter is set and ii) based on the serving cell being the PCell of the UE, the CHO related field may be the last 1 bit of the information block.

[0017] In each aspect of the present specification, i) based on the second parameter being set and ii) based on the serving cell being the PCell of the UE, and ii) based on the cell discontinuous transmission (DTX) and cell discontinuous reception (DRX) being set for the serving cell, the information block is composed of three bits, and the first two bits of the information block can be used for activating or deactivating at least one of the cell DTX or the cell DRX.

[0018] In each aspect of the present specification, i) based on the second parameter being set and ii) based on the serving cell being the PCell of the UE, and ii) based on the cell discontinuous transmission (DTX) or cell discontinuous reception (DRX) being set for the serving cell, the information block is composed of two bits, and the first bit of the information block can be used to activate or deactivate the cell DTX or the cell DRX set for the serving cell.

[0019] In each aspect of this specification, the specific DCI format may be DCI format 2_9.

[0020] In each aspect of this specification, the method by the UE or the operations for the UE may include: monitoring the specific DCI format over a common search space.

[0021] In each aspect of this specification, the specific DCI format may be transmitted over a common search space.

[0022] In each aspect of this specification, the method by the UE or the operations for the UE may include: executing a handover to another cell based on the CHO-related field including a first value and the CHO condition being satisfied.

[0023] In each aspect of this specification, the CHO procedure may not be triggered based on the CHO-related field containing the second value.

[0024] In each aspect of the present specification, the method by the UE or the operations for the UE may include: i) the UE does not obtain the CHO related field from the information block based on whether the second parameter is not set or ii) the serving cell is a secondary cell of the UE.

[0025] In each aspect of this specification, the method by the UE or the operations for the UE may include: considering the information block to not include the CHO related field based on: i) the second parameter is not set, or ii) the serving cell is a secondary cell of the UE.

[0026] In each aspect of this specification, the information block may not include the CHO related field based on i) the second parameter is not set or ii) the serving cell is not a PCell for any UE.

[0027] In each aspect of this specification, the method by the UE or the operations for the UE may further include: receiving a setting regarding the CHO condition.

[0028] In each aspect of this specification, the method by the BS or the operations for the BS may further include: transmitting a setting regarding the CHO condition.

[0029] The above problem solving methods are only some of the examples of this specification, and various examples reflecting the technical features of this specification can be derived and understood by a person having ordinary knowledge in the relevant technical field based on the detailed description below.

[0030] According to some implementations of this specification, methods and procedures for energy saving of a network, BS and / or UE may be provided.

[0031] According to some implementations of this specification, handover related procedures can be triggered efficiently.

[0032] According to some implementations of this specification, UE power consumption may be reduced.

[0033] The effects according to this specification are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those skilled in the art related to this specification from the detailed description below.

[0034] To aid in understanding implementations of this specification, the accompanying drawings, which are included as part of the detailed description, provide examples of implementations of this specification and, together with the detailed description, illustrate implementations of this specification:

[0035] Figure 1 illustrates an example of a communication system 1 to which implementations of the present specification are applied;

[0036] FIG. 2 is a block diagram illustrating examples of communication devices capable of performing a method according to the present specification;

[0037] FIG. 3 illustrates another example of a wireless device capable of performing implementation(s) of the present specification;

[0038] FIG. 4 illustrates an example of a frame structure available in a 3rd generation partnership project (3GPP) based wireless communication system;

[0039] Figure 5 illustrates a resource grid of slots;

[0040] FIG. 6 illustrates a discontinuous reception (DRX) operation that may be applied to implementation(s) of the present specification;

[0041] Figure 7 illustrates a case where a Long DRX cycle and a Short DRX cycle are set;

[0042] Figure 8 illustrates the structure of a DCI format for activating / deactivating cell DTX / DRX settings;

[0043] FIGS. 9 and 10 illustrate structures of DCI format 2_9 according to some implementations of the present specification;

[0044] Figure 11 illustrates the flow of UE operation according to some implementations of this specification;

[0045] Figure 12 illustrates the flow of BS operation according to some implementations of this specification.

[0046] Hereinafter, implementations according to this specification will be described in detail with reference to the attached drawings. The detailed description provided below, together with the attached drawings, is intended to describe exemplary implementations of this specification and is not intended to represent the only possible implementations of this specification. The detailed description below includes specific details to provide a thorough understanding of this specification. However, one of ordinary skill in the art will appreciate that this specification may be practiced without these specific details.

[0047] In some cases, to avoid ambiguity in the concepts of this specification, known structures and devices may be omitted or illustrated in block diagram form focusing on the core functions of each structure and device. Furthermore, identical components are described using the same drawing reference numerals throughout this specification.

[0048] The techniques, devices, and systems described below can be applied to various wireless multiple access systems. Examples of multiple access systems include code division multiple access (CDMA) systems, frequency division multiple access (FDMA) systems, time division multiple access (TDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and multi-carrier frequency division multiple access (MC-FDMA) systems. CDMA can be implemented in wireless technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented in wireless technologies such as Global System for Mobile communication (GSM), General Packet Radio Service (GPRS), and Enhanced Data Rates for GSM Evolution (EDGE) (i.e., GERAN). OFDMA can be implemented in wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (WiFi), IEEE 802.16 (WiMAX), IEEE 802-20, and E-UTRA (evolved-UTRA). UTRA is part of UMTS (Universal Mobile Telecommunication System), and 3GPP (3rd Generation Partnership Project) LTE (Long Term Evolution) is a part of E-UMTS that uses E-UTRA.3GPP LTE adopts OFDMA for the downlink (DL) and SC-FDMA for the uplink (UL). LTE-A (LTE-advanced) is an evolved form of 3GPP LTE.

[0049] For convenience of explanation, the following description assumes that this specification applies to 3GPP-based communication systems, such as LTE and NR. However, the technical features of this specification are not limited to this. For example, although the detailed description below is based on a mobile communication system corresponding to a 3GPP LTE / NR system, it can also be applied to any other mobile communication system, except for features specific to 3GPP LTE / NR.

[0050] For terms and technologies used in this specification that are not specifically explained, reference may be made to 3GPP-based standard documents, such as 3GPP TS 36.211, 3GPP TS 36.212, 3GPP TS 36.213, 3GPP TS 36.321, 3GPP TS 36.300 and 3GPP TS 36.331, 3GPP TS 37.213, 3GPP TS 38.211, 3GPP TS 38.212, 3GPP TS 38.213, 3GPP TS 38.214, 3GPP TS 38.300, 3GPP TS 38.304, 3GPP TS 38.331, etc.

[0051] In the examples of this specification described below, the expression "assumes" that a device "assumes" that the entity transmitting the channel transmits the channel in a manner consistent with the "assume." The entity receiving the channel may mean that, under the assumption that the channel was transmitted in a manner consistent with the "assume," the entity receiving the channel receives or decodes the channel in a manner consistent with the "assume."

[0052] In this specification, ' / ' may mean 'and / or'. For example, cell DTX / DRX may mean cell DTX and / or cell DRX.

[0053] In this specification, UE may be fixed or mobile, and includes various devices that communicate with a BS (base station) to transmit and / or receive user data and / or various control information. UE may be called (Terminal Equipment), MS (Mobile Station), MT (Mobile Terminal), UT (User Terminal), SS (Subscribe Station), wireless device, PDA (Personal Digital Assistant), wireless modem, handheld device, etc. In addition, in this specification, BS generally refers to a fixed station that communicates with UE and / or other BS, and exchanges various data and control information with UE and other BS. BS may be called by other terms such as ABS (Advanced Base Station), NB (Node-B), eNB (evolved-NodeB), BTS (Base Transceiver System), Access Point, PS (Processing Server), etc. In particular, the BS in UTRAN is called a Node-B, the BS in E-UTRAN is called an eNB, and the BS in a new radio access technology network is called a gNB. For convenience of explanation, BSs are collectively referred to as BSs below, regardless of the type or version of communication technology.

[0054] In this specification, a node refers to a fixed point that can transmit / receive radio signals by communicating with a UE. Various types of BSs can be used as nodes regardless of their names. For example, BSs, NBs, eNBs, pico-cell eNBs (PeNBs), home eNBs (HeNBs), relays, and repeaters can be nodes. Furthermore, a node may not be a BS. For example, it can be a radio remote head (RRH) or a radio remote unit (RRU). RRHs, RRUs, etc. generally have a lower power level than the BS. Since an RRH or RRU (hereinafter referred to as RRH / RRU) is generally connected to a BS via a dedicated line such as an optical cable, cooperative communication between an RRH / RRU and a BS can be performed more smoothly than cooperative communication between BSs that are generally connected via a wireless line. Each node is equipped with at least one antenna. The antenna may be a physical antenna, an antenna port, a virtual antenna, or an antenna group. A node is also called a point.

[0055] In this specification, a cell refers to a certain geographical area where one or more nodes provide communication services. Therefore, in this specification, communicating with a specific cell may mean communicating with a BS or node that provides communication services to the specific cell. In addition, the downlink / uplink signal of a specific cell refers to a downlink / uplink signal from / to a BS or node that provides communication services to the specific cell. A cell that provides uplink / downlink communication services to a UE is specifically referred to as a serving cell. In addition, the channel state / quality of a specific cell refers to the channel state / quality of a channel or communication link formed between a BS or node that provides communication services to the specific cell and the UE. In a 3GPP-based communication system, a UE can measure a downlink channel state from a specific node using CRS (Cell-specific Reference Signal) resources transmitted by antenna port(s) of the specific node on CRS resources allocated to the specific node and / or CSI-RS (Channel State Information Reference Signal) resources transmitted.

[0056] Meanwhile, 3GPP-based communication systems use the concept of cells to manage radio resources, and cells associated with radio resources are distinguished from cells in geographical areas.

[0057] A "cell" in a geographical area can be understood as the coverage over which a node can provide a service using a carrier, and a "cell" in a radio resource is associated with a bandwidth (BW), which is a frequency range configured by the carrier. Since downlink coverage, which is the range over which a node can transmit a valid signal, and uplink coverage, which is the range over which a node can receive a valid signal from a UE, depend on the carrier carrying the signal, the coverage of a node is also associated with the coverage of the "cell" of the radio resource used by the node. Therefore, the term "cell" can sometimes be used to mean the coverage of a service by a node, sometimes a radio resource, and sometimes the range over which a signal using the radio resource can reach with a valid intensity.

[0058] Meanwhile, the 3GPP communication standard uses the concept of a cell to manage radio resources. A "cell" associated with radio resources is defined as a combination of downlink resources (DL resources) and uplink resources (UL resources), i.e., a combination of a DL component carrier (CC) and an UL CC. A cell can be configured with DL resources alone or a combination of DL resources and UL resources. If carrier aggregation is supported, the linkage between the carrier frequency of the DL resources (or DL ​​CC) and the carrier frequency of the UL resources (or UL CC) can be indicated by system information. For example, the combination of DL resources and UL resources can be indicated by a System Information Block Type 2 (SIB2) linkage. Here, the carrier frequency can be the same as or different from the center frequency of each cell or CC. When carrier aggregation (CA) is established, the UE has only one radio resource control (RRC) connection with the network. One serving cell provides non-access stratum (NAS) mobility information during RRC connection establishment / re-establishment / handover, and one serving cell provides security input during RRC connection re-establishment / handover. Such a cell is called a primary cell (Pcell). A Pcell is a cell operating on the primary frequency where the UE performs initial connection establishment procedures or initiates connection re-establishment procedures.Depending on the UE capability, secondary cells (Scells) can be configured to form a set of serving cells together with Pcells. An Scell ​​can be configured after an RRC (Radio Resource Control) connection establishment has been made, and is a cell that provides additional radio resources in addition to the resources of a special cell (SpCell). The carrier corresponding to a Pcell in downlink is called a downlink primary CC (DL PCC), and the carrier corresponding to a Pcell in uplink is called an UL primary CC (UL PCC). The carrier corresponding to an Scell ​​in downlink is called a DL secondary CC (DL SCC), and the carrier corresponding to the Scell ​​in uplink is called an UL secondary CC (UL SCC).

[0059] For dual connectivity (DC) operation, the term special cell (SpCell) refers to a Pcell of a master cell group (MCG) or a primary secondary cell (PSCell) of a secondary cell group (SCG). A SpCell supports PUCCH transmission and contention-based random access and is always activated. An MCG is a group of serving cells associated with a master node (e.g., BS) and consists of a SpCell (Pcell) and optionally one or more Scells. For a UE configured for DC, an SCG is a subset of serving cells associated with a secondary node and consists of a primary secondary cell (PSCell) and zero or more Scells. A PSCell is a primary Scell ​​of an SCG. For a UE in RRC_CONNECTED state that is not configured for CA or DC, there is only one serving cell consisting of Pcells. For a UE in RRC_CONNECTED state that is configured for CA or DC, the term serving cells refers to the set of cells consisting of SpCell(s) and all Scell(s). In DC, two medium access control (MAC) entities are configured in the UE: one for the MCG and one for the SCG.

[0060] For a UE for which CA is set and DC is not set, a Pcell PUCCH group (also referred to as a primary PUCCH group) consisting of a Pcell and zero or more Scells and a Scell ​​PUCCH group (also referred to as a secondary PUCCH group) consisting of only Scell(s) may be set. In the case of an Scell, an Scell ​​(hereinafter referred to as a PUCCH Scell) on which a PUCCH associated with the cell is transmitted may be set. An Scell ​​for which a PUCCH Scell ​​is indicated belongs to an Scell ​​PUCCH group (i.e., a secondary PUCCH group), and PUCCH transmission of the relevant UCI is performed on the PUCCH Scell, and an Scell ​​for which a PUCCH Scell ​​is not indicated or which is a Pcell and is indicated as a cell for PUCCH transmission belongs to a Pcell PUCCH group (i.e., a primary PUCCH group), and PUCCH transmission of the relevant UCI is performed on the Pcell. Hereinafter, if a UE is configured with an SCG and some implementations of this specification related to PUCCH are applied to the SCG, the primary cell may refer to a PSCell of the SCG. If a UE is configured with a PUCCH Scell ​​and some implementations of this specification related to PUCCH are applied to a secondary PUCCH group, the primary cell may refer to a PUCCH Scell ​​of the secondary PUCCH group.

[0061] In a wireless communication system, a UE receives information from a base station (BS) via the downlink (DL), and the UE transmits information to the base station via the uplink (UL). The information transmitted and / or received by the BS and UE includes data and various control information, and various physical channels exist depending on the type and purpose of the information they transmit and / or receive.

[0062] 3GPP-based communication standards define downlink physical channels corresponding to resource elements that carry information originating from higher layers, and downlink physical signals corresponding to resource elements that are used by the physical layer but do not carry information originating from higher layers. For example, the physical downlink shared channel (PDSCH), physical broadcast channel (PBCH), and physical downlink control channel (PDCCH) are defined as downlink physical channels, and reference signals and synchronization signals are defined as downlink physical signals. A reference signal (RS), also referred to as a pilot, refers to a signal with a predefined, special waveform that is known to the BS and the UE. For example, the demodulation reference signal (DMRS), the channel state information RS (CSI-RS), and the positioning reference signal (PRS) are defined as downlink reference signals. 3GPP-based communication standards define uplink physical channels corresponding to resource elements that carry information originating from higher layers, and uplink physical signals corresponding to resource elements that are used by the physical layer but do not carry information originating from higher layers.For example, a physical uplink shared channel (PUSCH), a physical uplink control channel (PUCCH), and a physical random access channel (PRACH) are defined as uplink physical channels, and a demodulation reference signal (DMRS) for uplink control / data signals and a sounding reference signal (SRS) used for uplink channel measurement are defined.

[0063] In this specification, PDCCH (Physical Downlink Control CHannel) refers to a set of time-frequency resources (e.g., resource elements (REs)) that carry DCI (Downlink Control Information), and PDSCH (Physical Downlink Shared CHannel) refers to a set of time-frequency resources that carry downlink data. In addition, PUCCH (Physical Uplink Control CHannel), PUSCH (Physical Uplink Shared CHannel), and PRACH (Physical Random Access CHannel) refer to sets of time-frequency resources that carry UCI (Uplink Control Information), uplink data, and random access signals, respectively (respectively). Hereinafter, the expression that a user equipment transmits / receives a PUCCH / PUSCH / PRACH is used with the same meaning as that uplink control information / uplink data / random access signals are transmitted / received on or through the PUCCH / PUSCH / PRACH, respectively. Additionally, the expression that BS transmits / receives PBCH / PDCCH / PDSCH is used with the same meaning as transmitting broadcast information / downlink control information / downlink data on or through PBCH / PDCCH / PDSCH, respectively.

[0064] In this specification, radio resources (e.g., time-frequency resources) scheduled or configured by the BS to the UE for transmission or reception of PUCCH / PUSCH / PDSCH are also referred to as PUCCH / PUSCH / PDSCH resources.

[0065] Since the communication device receives a synchronization signal (SS), DMRS, CSI-RS, PRS, PBCH, PDCCH, PDSCH, PUSCH, and / or PUCCH in the form of radio signals on a cell, it cannot selectively receive through an RF receiver only radio signals including only a specific physical channel or only a specific physical signal, or selectively receive through an RF receiver only radio signals excluding only a specific physical channel or only a physical signal. In actual operation, the communication device first receives radio signals on a cell through an RF receiver, converts the radio signals, which are RF band signals, into baseband signals, and decodes a physical signal and / or a physical channel within the baseband signals using one or more processors. Thus, in some implementations of the present specification, not receiving a physical signal and / or a physical channel may not actually mean that the communication device does not receive wireless signals containing the physical signal and / or physical channel at all, but rather that it does not attempt to recover the physical signal and / or physical channel from the wireless signals, e.g., does not attempt to decode the physical signal and / or the physical channel.

[0066] As more and more communication devices demand greater communication capacity, the need for improved mobile broadband communication over existing radio access technology (RAT) is emerging. Furthermore, massive MTC, which connects numerous devices and objects to provide diverse services anytime, anywhere, is also a key issue to be considered in next-generation communications. Furthermore, communication system design that considers reliability and latency-sensitive services / UEs is being discussed. The introduction of next-generation RATs that take advanced mobile broadband communication, massive MTC, and URLLC (Ultra-Reliable and Low Latency Communication) into account is currently under discussion. 3GPP is currently conducting studies on next-generation mobile communication systems beyond EPC. For convenience, this technology is referred to as new RAT (NR) or 5G RAT, and a system that uses or supports NR is referred to as an NR system.

[0067] FIG. 1 illustrates an example of a communication system 1 to which implementations of the present specification are applied. Referring to FIG. 1, the communication system (1) applied to the present specification includes a wireless device, a BS, and a network. Here, the wireless device refers to a device that performs communication using a wireless access technology (e.g., 5G NR (New RAT), LTE (e.g., E-UTRA)) and may be referred to as a communication / wireless / 5G device. Although not limited thereto, the wireless device may include a robot (100a), a vehicle (100b-1, 100b-2), an XR (eXtended Reality) device (100c), a hand-held device (100d), a home appliance (100e), an IoT (Internet of Things) device (100f), and an AI device / server (400). For example, the vehicle may include a vehicle equipped with a wireless communication function, an autonomous vehicle, a vehicle capable of performing vehicle-to-vehicle communication, etc. Here, the vehicle may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone). XR devices include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices, and may be implemented in the form of a Head-Mounted Device (HMD), a Head-Up Display (HUD) installed in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, digital signage, a vehicle, a robot, etc. Mobile devices may include a smartphone, a smart pad, a wearable device (e.g., a smart watch, smart glasses), a computer (e.g., a laptop, etc.), etc. Home appliances may include a TV, a refrigerator, a washing machine, etc. IoT devices may include sensors, smart meters, etc. For example, a BS or network may also be implemented as a wireless device, and a specific wireless device may act as a BS / network node to other wireless devices.

[0068] Wireless devices (100a to 100f) can be connected to a network (300) via a BS (200). Artificial Intelligence (AI) technology can be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) via a network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, etc. The wireless devices (100a to 100f) can communicate with each other via the BS (200) / network (300), but can also communicate directly (e.g., sidelink communication) without going through the BS / network. For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to Everything) communication). In addition, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

[0069] Wireless communication / connection (150a, 150b) can be performed between wireless devices (100a~100f) / BS (200) - BS (200) / wireless devices (100a~100f). Here, the wireless communication / connection can be performed through various wireless access technologies (e.g., 5G NR) for uplink / downlink communication (150a) and sidelink communication (150b) (or D2D communication). Through the wireless communication / connection (150a, 150b), the wireless device and the BS / wireless device can transmit / receive wireless signals to / from each other. To this end, at least some of various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and resource allocation processes can be performed based on various proposals of this specification.

[0070] FIG. 2 is a block diagram illustrating examples of communication devices capable of performing a method according to the present specification. Referring to FIG. 2, a first wireless device (100) and a second wireless device (200) can transmit and / or receive wireless signals via various wireless access technologies (e.g., LTE, NR). Here, {the first wireless device (100), the second wireless device (200)} can correspond to {the wireless device (100x), the BS (200)} and / or {the wireless device (100x), the wireless device (100x)} of FIG. 1.

[0071] A first wireless device (100) includes one or more processors (102) and one or more memories (104), and may further include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memories (104) and / or the transceivers (106), and may be configured to implement functions, procedures, and / or methods described / suggested below. For example, the processor (102) may process information in the memory (104) to generate first information / signals, and then transmit a wireless signal including the first information / signals via the transceivers (106). In addition, the processor (102) may receive a wireless signal including second information / signals via the transceivers (106), and then store information obtained from signal processing of the second information / signals in the memory (104). The memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, the memory (104) may perform some or all of the processes controlled by the processor (102), or may store software code including commands for performing the procedures and / or methods described / proposed below. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals via one or more antennas (108). The transceiver (106) may include a transmitter and / or a receiver. The transceiver (106) may be used interchangeably with an RF (Radio Frequency) unit. In this specification, a wireless device may also mean a communication modem / circuit / chip.

[0072] The second wireless device (200) includes one or more processors (202), one or more memories (204), and may further include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memories (204) and / or the transceivers (206), and may be configured to implement the functions, procedures, and / or methods described / suggested below. For example, the processor (202) may process information in the memory (204) to generate third information / signals, and then transmit a wireless signal including the third information / signals via the transceivers (206). In addition, the processor (202) may receive a wireless signal including fourth information / signals via the transceivers (206), and then store information obtained from signal processing of the fourth information / signals in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, the memory (204) may perform some or all of the processes controlled by the processor (202), or may store software code including commands for performing the procedures and / or methods described / proposed below. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via one or more antennas (208). The transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with an RF unit. In this specification, a wireless device may also mean a communication modem / circuit / chip.

[0073] The wireless communication technology implemented in the wireless device (100, 200) of the present specification may include not only LTE, NR, and 6G, but also Narrowband Internet of Things for low-power communication. At this time, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology, and may be implemented with standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device (XXX, YYY) of the present specification may perform communication based on LTE-M technology. At this time, for example, LTE-M technology may be an example of LPWAN technology, and may be called by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology can be implemented by at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device (XXX, YYY) of the present specification can include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) considering low-power communication, and is not limited to the above-described names. For example, ZigBee technology can create personal area networks (PAN) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and can be called by various names.

[0074] Hereinafter, hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as a physical (PHY) layer, a medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) layer, and a service data adaptation protocol (SDAP) layer). One or more processors (102, 202) may generate one or more protocol data units (PDUs) and / or one or more service data units (SDUs) according to the functions, procedures, proposals, and / or methods disclosed in this specification. One or more processors (102, 202) may generate messages, control information, data or information according to the functions, procedures, proposals and / or methods disclosed in this specification. One or more processors (102, 202) may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the functions, procedures, proposals and / or methods disclosed in this specification, and provide the signals to one or more transceivers (106, 206). One or more processors (102, 202) may receive signals (e.g., baseband signals) from one or more transceivers (106, 206) and obtain PDUs, SDUs, messages, control information, data or information according to the functions, procedures, proposals and / or methods disclosed in this specification.

[0075] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in one or more processors (102, 202). The functions, procedures, proposals, and / or methods disclosed in this specification may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. Firmware or software configured to perform the functions, procedures, suggestions and / or methods disclosed in this specification may be included in one or more processors (102, 202) or stored in one or more memories (104, 204) and executed by one or more processors (102, 202). The functions, procedures, suggestions and / or methods disclosed in this specification may be implemented using firmware or software in the form of codes, instructions and / or sets of instructions.

[0076] One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories (104, 204) may be configured as ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories (104, 204) may be located internally and / or externally to the one or more processors (102, 202). Additionally, the one or more memories (104, 204) may be coupled to the one or more processors (102, 202) via various technologies, such as wired or wireless connections.

[0077] One or more transceivers (106, 206) may transmit user data, control information, wireless signals / channels, etc., as described in the methods and / or flowcharts of this specification, to one or more other devices. One or more transceivers (106, 206) may receive user data, control information, wireless signals / channels, etc., as described in the functions, procedures, proposals, methods and / or flowcharts of this specification, from one or more other devices. For example, one or more transceivers (106, 206) may be coupled to one or more processors (102, 202) and may transmit and / or receive wireless signals. For example, one or more processors (102, 202) may control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be coupled to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and / or receive user data, control information, wireless signals / channels, or the like, as referred to in the functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this specification, via one or more antennas (108, 208). In this specification, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) may convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals for processing using one or more processors (102, 202).One or more transceivers (106, 206) may convert user data, control information, wireless signals / channels, etc. processed by one or more processors (102, 202) from baseband signals to RF band signals. For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or filter.

[0078] FIG. 3 illustrates another example of a wireless device capable of performing implementation(s) of the present specification. Referring to FIG. 3, the wireless device (100, 200) corresponds to the wireless device (100, 200) of FIG. 2 and may be composed of various elements, components, units / units, and / or modules. For example, the wireless device (100, 200) may include a communication unit (110), a control unit (120), a memory unit (130), and additional elements (140). The communication unit may include a communication circuit (112) and a transceiver(s) (114). For example, the communication circuit (112) may include one or more processors (102, 202) and / or one or more memories (104, 204) of FIG. 2. For example, the transceiver(s) (114) may include one or more transceivers (106, 206) and / or one or more antennas (108, 208) of FIG. 2. The control unit (120) is electrically connected to the communication unit (110), the memory unit (130), and the additional elements (140) and controls the overall operation of the wireless device. For example, the control unit (120) may control the electrical / mechanical operation of the wireless device based on the program / code / command / information stored in the memory unit (130). In addition, the control unit (120) may transmit information stored in the memory unit (130) to an external device (e.g., another communication device) via a wireless / wired interface through the communication unit (110), or store information received from an external device (e.g., another communication device) via a wireless / wired interface in the memory unit (130).

[0079] The additional element (140) may be configured in various ways depending on the type of the wireless device. For example, the additional element (140) may include at least one of a power unit / battery, an input / output (I / O) unit, a driving unit, and a computing unit. Although not limited thereto, the wireless device may be implemented in the form of a robot (Fig. 1, 100a), a vehicle (Fig. 1, 100b-1, 100b-2), an XR device (Fig. 1, 100c), a portable device (Fig. 1, 100d), a home appliance (Fig. 1, 100e), an IoT device (Fig. 1, 100f), a UE for digital broadcasting, a hologram device, a public safety device, an MTC device, a medical device, a fintech device (or a financial device), a security device, a climate / environmental device, an AI server / device (Fig. 1, 400), a BS (Fig. 1, 200), a network node, etc. Wireless devices may be mobile or stationary depending on the use / service.

[0080] In FIG. 3, various elements, components, units / parts, and / or modules within the wireless device (100, 200) may be entirely interconnected via a wired interface, or at least some may be wirelessly connected via a communication unit (110). For example, within the wireless device (100, 200), the control unit (120) and the communication unit (110) may be wired, and the control unit (120) and a first unit (e.g., 130, 140) may be wirelessly connected via the communication unit (110). In addition, each element, component, unit / part, and / or module within the wireless device (100, 200) may further include one or more elements. For example, the control unit (120) may be composed of one or more processor sets. For example, the control unit (120) may be composed of a set of a communication control processor, an application processor, an electronic control unit (ECU), a graphics processing processor, a memory control processor, etc. As another example, the memory unit (130) may be composed of RAM (Random Access Memory), DRAM (Dynamic RAM), ROM (Read Only Memory), flash memory, volatile memory, non-volatile memory, transitory memory, non-transitory memory, and / or a combination thereof.

[0081] In this specification, at least one memory (e.g., 104 or 204) can store instructions or programs that, when executed, cause at least one processor operably connected to the at least one memory to perform operations according to some embodiments or implementations of the present specification.

[0082] In this specification, a computer-readable (non-volatile or non-transitory) storage medium can store at least one instruction or computer program, which when executed by at least one processor causes the at least one processor to perform operations according to some embodiments or implementations of this specification.

[0083] In this specification, a processing device or apparatus may include at least one processor and at least one computer memory operatively connected to the at least one processor. The at least one computer memory may store instructions or programs, which, when executed, cause at least one processor operatively connected to the at least one memory to perform operations according to some embodiments or implementations of the present specification.

[0084] In this specification, a computer program may be stored in at least one computer-readable (non-volatile) storage medium and may include program code that, when executed, performs operations according to some implementations of the present specification or causes at least one processor to perform operations according to some implementations of the present specification. The computer program may be provided in the form of a computer program product. The computer program product may include at least one computer-readable (non-volatile) storage medium.

[0085] A communications device of the present specification comprises at least one processor; and at least one computer memory operably connected to said at least one processor and storing instructions that, when executed, cause said at least one processor to perform operations according to the example(s) of the present specification described below.

[0086] Figure 4 illustrates an example of a frame structure available in a 3GPP-based wireless communication system.

[0087] The structure of the frame in Fig. 4 is merely an example, and the number of subframes, the number of slots, and the number of symbols in the frame can be varied. In an NR system, OFDM numerology (e.g., subcarrier spacing (SCS)) may be set differently between multiple cells aggregated to a single UE. Accordingly, the (absolute time) duration of a time resource (e.g., a subframe, a slot, or a transmission time interval (TTI)) consisting of the same number of symbols may be set differently between the aggregated cells. Here, the symbol may include an OFDM symbol (or a cyclic prefix - orthogonal frequency division multiplexing (CP-OFDM) symbol), an SC-FDMA symbol (or a discrete Fourier transform-spread-OFDM (DFT-s-OFDM) symbol). In this specification, the terms symbol, OFDM-based symbol, OFDM symbol, CP-OFDM symbol, and DFT-s-OFDM symbols are interchangeable.

[0088] Referring to Figure 4, in the NR system, uplink and downlink transmissions are organized into frames. Each frame is T f= (△f max *N f / 100)*T c = 10 ms duration, divided into two half-frames of 5 ms each. Here, T is the basic time unit for NR. c = 1 / (△f max *N f ) and △f max = 480*10 3 Hz, and N f =4096. For reference, T is the basic time unit for LTE. s = 1 / (△f ref *N f,ref ) and △f ref = 15*10 3 Hz, and N f,ref =2048. T s Wow T c is a constant κ = T s / T c = 64 relationship. Each half-frame consists of 5 subframes, and the duration of a single subframe is T. sf is 1ms. Subframes are further divided into slots, and the number of slots in a subframe depends on the subcarrier spacing. Each slot consists of 14 or 12 OFDM symbols based on the cyclic prefix. For a normal cyclic prefix (CP), each slot consists of 14 OFDM symbols, and for an extended CP, each slot consists of 12 OFDM symbols. The numerology is exponentially scalable with a subcarrier spacing △f = 2. u *Depends on 15 kHz. The following table shows the subcarrier spacing for regular CP △f = 2. u *Number of OFDM symbols per slot at 15 kHz (N) slot symb ), number of slots per frame (N frame,uslot ) and the number of slots per subframe (N subframe,u slot ) is shown.

[0089]

[0090] The following table shows the subcarrier spacing for extended CP △f = 2. u *Indicates the number of OFDM symbols per slot, the number of slots per frame, and the number of slots per subframe at 15 kHz.

[0091]

[0092] For a subcarrier spacing setting u, slots are n in increasing order within a subframe. u s ∈ {0, ..., nsubframe,u slot - 1} and n in increasing order within the frame u s,f ∈ {0, ..., n frame,u slot - Numbered as 1}.

[0093] Figure 5 illustrates the resource grid of a slot. A slot contains multiple symbols (e.g., 14 or 12) in the time domain. For each numeral (e.g., subcarrier spacing) and carrier, a common resource block (CRB) N is indicated by higher layer signaling (e.g., radio resource control (RRC) signaling). start,u grid Starting from,N size,u grid,x *N RB sc Dog subcarriers and N subframe,u symb A resource grid of OFDM symbols is defined, where N size,u grid,xis the number of resource blocks (RBs) in the resource grid, and the subscript x is DL for downlink and UL for uplink. N RB sc is the number of subcarriers per RB, and in 3GPP-based wireless communication systems, N RB sc is typically 12. For a given antenna port p, subcarrier spacing configuration u, and transmission direction (DL or UL), there is one resource grid. The carrier bandwidth N for subcarrier spacing configuration u size,u grid is given to the UE by higher layer parameters (e.g., RRC parameters) from the network. Each element in the resource grid for antenna port p and subcarrier spacing configuration u is called a resource element (RE), and one complex symbol can be mapped to each RE. Each RE in the resource grid is uniquely identified by an index k in the frequency domain and an index l indicating the symbol position relative to a reference point in the time domain. In an NR system, an RB is defined by 12 consecutive subcarriers in the frequency domain. In an NR system, RBs can be classified into common resource blocks (CRBs) and physical resource blocks (PRBs). CRBs are numbered upwards from 0 in the frequency domain for the subcarrier spacing configuration u. The center of subcarrier 0 of CRB 0 for the subcarrier spacing configuration u coincides with 'Point A', which is a common reference point for the resource block grids. PRBs for subcarrier spacing u are defined within the bandwidth part (BWP) and range from 0 to N. size,u BWP,i -1, where i is the number of the bandwidth part. Common resource block n u CRBand bandwidth part i within physical resource block n PRB The relationship between the two is as follows: n u PRB = n u CRB +N start,u BWP,i , here N start,u BWP,i is a common resource block (BRB) whose bandwidth part starts relative to CRB 0. A BWP comprises multiple consecutive RBs in the frequency domain. For example, a BWP may be a given numeral u within a BWP i on a given carrier. i A subset of contiguous CRBs defined for a carrier. A carrier may include up to N (e.g., 5) BWPs. A UE may be configured to have one or more BWPs on a given component carrier. Data communication is performed through the activated BWPs, and only a predetermined number (e.g., 1) of BWPs configured for the UE may be activated on the carrier.

[0094] For each serving cell in a set of DL BWPs or UL BWPs, the network configures at least an initial DL BWP and one (if the serving configuration is configured with uplink) or two (if supplementary uplink is used) initial UL BWPs. The network may also configure additional UL and DL BWPs for the serving cell. For each DL BWP or UL BWP, the UE is provided with the following parameters for the serving cell: i) subcarrier spacing, ii) cyclic prefix, and iii) N start BWP = Offset RB with the assumption of 275 set and length L RB CRBN provided by the RRC parameter locationAndBandwidth, which indicates the resource indicator value (RIV). start BWP=O carrier +RB start and the number of contiguous RBs N size BWP =L RB , and the subcarrier spacing is provided by the RRC parameter offsetToCarrierO carrier ; an index within the set of DL BWPs or UL BWPs; a set of BWP-common parameters and a set of BWP-specific parameters.

[0095] Virtual resource blocks (VRBs) are defined within the bandwidth part and are numbered from 0 to N. size,u BWP,i Numbered from -1, where i is the number of the bandwidth part. VRBs are mapped to physical resource blocks (PRBs) according to interleaved or non-interleaved mapping. In some implementations, for non-interleaved VRB-to-PRB mapping, VRB n may be mapped to PRB n.

[0096] NR frequency bands are defined by two types of frequency ranges, FR1 and FR2, with FR2 also referred to as millimeter wave (mmW). The following table lists the frequency ranges in which NR can operate.

[0097]

[0098] Below, the physical channels that can be used in 3GPP-based wireless communication systems are described in more detail.

[0099] The PDCCH carries DCI. For example, the PDCCH (i.e., DCI) carries the transmission format and resource allocation of the downlink shared channel (DL-SCH), resource allocation information for the uplink shared channel (UL-SCH), paging information for the paging channel (PCH), system information on the DL-SCH, resource allocation information for control messages of a layer (hereinafter, upper layer) located above the physical layer in the protocol stacks of the UE / BS, such as a random access response (RAR) transmitted on the PDSCH, transmission power control commands, activation / release of configured scheduling (CS), etc. The DCI that includes resource allocation information for the DL-SCH is also called PDSCH scheduling DCI, and the DCI that includes resource allocation information for the UL-SCH is also called PUSCH scheduling DCI. The DCI includes a cyclic redundancy check (CRC), and the CRC is masked / scrambled with various identifiers (e.g., radio network temporary identifier (RNTI)) depending on the owner or intended use of the PDCCH. For example, if the PDCCH is for a specific UE, the CRC is masked with the UE identifier (e.g., cell RNTI (C-RNTI)). If the PDCCH is for paging, the CRC is masked with the paging RNTI (P-RNTI). If the PDCCH is for system information (e.g., system information block (SIB)), the CRC is masked with the system information RNTI (SI-RNTI). If the PDCCH is for a random access response, the CRC is masked with the random access RNTI (RA-RATI).

[0100] When a PDCCH on one serving cell schedules a PDSCH or PUSCH on another serving cell, this is called cross-carrier scheduling. Cross-carrier scheduling using the carrier indicator field (CIF) can allow the PDCCH of a serving cell to schedule resources on another serving cell. On the other hand, when a PDSCH on a serving cell schedules a PDSCH or PUSCH on the serving cell, this is called self-carrier scheduling. When cross-carrier scheduling is used in a cell, the BS can provide the UE with information about the cell that schedules the cell. For example, the BS can provide the UE with information about whether the serving cell is scheduled by a PDCCH on another (scheduling) cell or by the serving cell, and if the serving cell is scheduled by another (scheduling) cell, which cell signals downlink assignments and uplink grants for the serving cell. In this specification, a cell that carries a PDCCH is called a scheduling cell, and a cell in which transmission of a PUSCH or PDSCH is scheduled by DCI included in the PDCCH, i.e., a cell that carries a PUSCH or PDSCH scheduled by the PDCCH, is called a scheduled cell.

[0101] The PDSCH is a physical layer DL channel for DL ​​data transport. PDSCH carries downlink data (e.g., DL-SCH transport blocks) and employs modulation methods such as Quadrature Phase Shift Keying (QPSK), 16 Quadrature Amplitude Modulation (QAM), 64 QAM, and 256 QAM. Transport blocks (TBs) are encoded to generate codewords. A PDSCH can carry up to two codewords. Scrambling and modulation mapping are performed for each codeword, and the modulation symbols generated from each codeword can be mapped to one or more layers. Each layer is mapped to radio resources along with the DMRS, generating an OFDM symbol signal and transmitting it through the corresponding antenna port.

[0102] A UE must have uplink resources available to it for UL-SCH data transmission, and downlink resources available to it for DL-SCH data reception. Uplink and downlink resources are assigned to the UE through resource allocation by the BS. Resource allocation may include time domain resource allocation (TDRA) and frequency domain resource allocation (FDRA). In this specification, uplink resource allocation is also referred to as uplink grant, and downlink resource allocation is also referred to as downlink assignment. An uplink grant is dynamically received by the UE on the PDCCH or within the RAR, or is semi-persistently configured to the UE by RRC signaling from the BS. A downlink assignment is dynamically received by the UE on the PDCCH, or is semi-persistently configured to the UE by RRC signaling from the BS.

[0103] In UL, the BS can dynamically allocate uplink resources to the UE via PDCCH(s) addressed to a cell radio network temporary identifier (C-RNTI). The UE monitors the PDCCH(s) to find possible uplink grant(s) for UL transmission. In addition, the BS can allocate uplink resources to the UE using a configured grant (CG). Two types of configured grants can be used: Type 1 and Type 2. In Type 1, the BS directly provides the configured uplink grant (including the periodicity) via RRC signaling. For Type 2, the BS can set the period of the RRC-configured uplink grant through RRC signaling, and can signal and activate or deactivate the configured uplink grant through a PDCCH addressed to CS-RNTI (PDCCH addressed to CS-RNTI) addressed to the configured scheduling RNTI (CS-RNTI). For example, for Type 2, a PDCCH addressed to CS-RNTI indicates that the corresponding uplink grant can be implicitly reused according to the period set by RRC signaling until it is deactivated.

[0104] In DL, the BS can dynamically allocate downlink resources to the UE via PDCCH(s) addressed with the C-RNTI. The UE monitors the PDCCH(s) to discover possible downlink assignments. Additionally, the BS can allocate downlink resources to the UE using semi-static scheduling (SPS). The BS can set the period of the configured downlink assignments via RRC signaling, and signal and activate or deactivate the configured downlink assignments via the PDCCH addressed with the CS-RNTI. For example, a PDCCH addressed with the CS-RNTI implicitly indicates that the corresponding downlink assignment can be reused according to the period set by the RRC signaling until it is deactivated.

[0105] A control resource set (CORESET), which is a set of time-frequency resources for which a UE can monitor PDCCH, may be defined and / or configured. A CORESET consists of a set of physical resource blocks (PRBs) with a duration of one to three OFDM symbols. The PRBs constituting the CORESET and the CORESET duration may be provided to the UE via higher layer (e.g., RRC) signaling. Within the configured CORESET(s), a set of PDCCH candidates is monitored according to the corresponding search space sets. In this specification, monitoring implies decoding (aka blind decoding) each PDCCH candidate according to the monitored DCI formats.

[0106] The set of PDCCH candidates monitored by the UE is defined in terms of PDCCH search space sets. The search space set may be a common search space (CSS) set or a UE-specific search space (USS) set. Each CORESET configuration is associated with one or more search space sets, and each search space set is associated with one CORESET configuration.

[0107] A set of PDCCH candidates may be monitored in one or more CORESETs on an active DL BWP on each activated serving cell for which PDCCH monitoring is configured, where monitoring implies receiving each PDCCH candidate and decoding it according to the monitored DCI formats.

[0108] Based on the CORESET / search space set configuration, the UE can monitor PDCCH candidates in one or more SS sets within a slot. The occasions (e.g., time / frequency resources) during which PDCCH candidates are monitored are defined as PDCCH (monitoring) occasions. One or more PDCCH (monitoring) occasions can be configured within a slot.

[0109] Conditional handover (CHO)

[0110] Handover is a procedure to ensure seamless connectivity when a UE moves within a network. Typically, a UE performs measurements on neighboring cells and reports these measurements to the network, which then determines whether the UE should be handed over. For example, the source BS to which the UE is connected may decide to disconnect the UE from the source BS and connect to another BS (i.e., a target BS), or to hand the UE over from the source cell to another cell (i.e., a target cell). The source BS may instruct the UE to perform the handover by sending a handover command to the UE. Upon receiving the handover command, the UE may disconnect from the source BS / cell and connect to the target BS / cell. A typical handover can be successfully performed only when the quality of the serving cell is adequate for the UE to receive the handover command, and the quality of the target cell is sufficiently good for the UE to access. However, for the millimeter frequency range, there is a possibility that a typical handover may not be possible due to rapid signal quality degradation and widespread BS deployment.

[0111] Unlike a typical handover, where a UE handover is executed upon a network command, a conditional handover (CHO) is a handover executed by the UE when one or more handover execution conditions are met. Because CHO does not require a network handover command and is performed when certain conditions are met, it can reduce the probability of a handover failure due to channel degradation, thereby reducing the likelihood of radio link failure.

[0112] The UE may begin evaluating the execution condition(s) upon receiving the CHO configuration and may stop evaluating the execution condition(s) once the handover is completed. The CHO configuration may include the configuration of the CHO candidate cell(s) generated by the candidate BS(es) and the execution condition(s) generated by the source BS. The execution condition(s) may consist of one or more trigger condition(s). For example, the following may be used as trigger condition(s) that may be included in the execution condition(s):

[0113] - CondEvent A3: Conditional reconfiguration candidate becomes offset better than PCell / PSCell by the amount of offset.

[0114] - CondEvent A4: A conditional reconfiguration candidate becomes better than an absolute threshold where condEvent A4 can also be used for the current PSCell (i.e., in case it is configured as a candidate PSCell for CondEvent A4 evaluation) for CHO with candidate SCG(s) case, and / or

[0115] - CondEvent A5: PCell / PSCell becomes worse than absolute threshold 1 and conditional reset candidate becomes better than another absolute threshold 2.

[0116] The above offset of CondEvent A3, the above absolute threshold of CondEvent A4, and the above absolute threshold 1 and the above absolute threshold 2 of CondEvent A5 can be provided through settings regarding the trigger condition when the corresponding event is set as the trigger condition(s) for CHO.

[0117] One or two trigger quantities (e.g., reference signal received power (RSRP), reference signal received quantity (RSRQ), signal to interference plus noise ratio (SINR), etc.) can be set for evaluating the CHO running conditions of a single candidate cell.

[0118] UE discontinuous reception (DRX)

[0119] UE uses DRX to reduce power consumption. UE operating based on DRX repeats ON / OFF for reception operation. The features of DRX utilized for the purpose of reducing unnecessary power consumption of UE are as follows. DRX defines a structure for UE in RRC_IDLE state where RRC connection between UE and BS is not established (hereinafter referred to as I-DRX) and a structure for UE in RRC_CONNECTED state where RRC connection between UE and BS is established (hereinafter referred to as C-DRX). Both DRX structures are designed to reduce unnecessary power consumption in other periods by defining a period (e.g., active time period or on-duration period) in which UE can expect reception of DL signals to occur periodically. For reference, in the case of C-DRX, the start position of On-duration occurs periodically in the Rel-16 standard, and the size of the cycle that can be configured at this time (i.e., DRX cycle) can be determined / set through upper layer signaling, such as RRC signaling, provided by the BS to the UE.

[0120] Figure 6 illustrates discontinuous reception (DRX) operation. In particular, Figure 6 illustrates a DRX cycle for a UE in RRC_CONNECTED state.

[0121] Referring to FIG. 6, a DRX cycle consists of an ON period and an Opportunity for DRX. A DRX cycle defines a time interval in which an ON period is periodically repeated, followed by a possible period of inactivity. The ON period represents a time interval during which the UE performs PDCCH monitoring to receive a PDCCH. When DRX is configured, the UE performs PDCCH monitoring during the ON period. If a PDCCH is successfully detected during PDCCH monitoring, the UE starts an inactivity timer and remains awake. On the other hand, if no PDCCH is successfully detected during PDCCH monitoring, the UE enters a sleep state after the ON period ends. Therefore, when DRX is configured, the UE may perform PDCCH monitoring / reception discontinuously in the time domain when performing a process and / or method according to the implementation(s) of this specification. For example, when DRX is configured, the PDCCH reception occasion (e.g., slot having PDCCH search space) in this specification may be configured discontinuously according to the DRX configuration. On the other hand, when DRX is not configured, the UE may perform PDCCH monitoring / reception continuously in the time domain. For example, when DRX is not configured, the PDCCH reception occasion (e.g., slot having PDCCH search space) may be configured continuously. On the other hand, regardless of whether DRX is configured, PDCCH monitoring may be restricted in the time period configured as the measurement gap. DRX configuration information is received via upper layer (e.g., RRC) signaling, and whether DRX is turned on / off is controlled by the DRX command of the MAC layer. When DRX is configured, the UE may perform PDCCH monitoring discontinuously, as illustrated in FIG. 6.

[0122] The following table illustrates the UE processes related to DRX. Referring to the following table, DRX configuration information is received via upper layer (e.g., RRC) signaling, and DRX ON / OFF is controlled by the DRX command of the MAC layer. When DRX is configured, the UE can perform PDCCH monitoring discontinuously, as illustrated in FIG. 6.

[0123]

[0124] Here, MAC-CellGroupConfig contains configuration information required to set MAC parameters for a cell group. MAC-CellGroupConfig may also contain configuration information related to DRX. For example, MAC-CellGroupConfig may contain DRX-related information as follows.

[0125] - Value of drx-onDurationTimer: Sets the duration at the start of the DRX cycle.

[0126] - Value of drx-SlotOffset: Sets the delay before starting drx-onDurationTimer.

[0127] - Value of drx-InactivityTimer: Sets the period after which a PDCCH epoch indicates a new UL or DL ​​transmission to the MAC entity.

[0128] - Value of drxRetransmissionTimerDL (per DL HARQ process except for the broadcast process): Sets the maximum duration until a DL retransmission is received.

[0129] - Value of drxRetransmissionTimerUL (per UL HARQ process): Sets the maximum duration until a grant for UL retransmission is received.

[0130] - Value of drx-HARQ-RTT-TimerDL (per DL HARQ process except for the broadcast process): Sets the maximum period of time after a DL initial transmission is received until a DL assignment for HARQ retransmission is received.

[0131] - Value of drx-HARQ-RTT-TimerUL (per UL HARQ process): Sets the maximum period from when a grant for UL initial transmission is received until a grant for UL retransmission is received.

[0132] - drx-LongCycleStartOffset: Sets the Long DRX cycle and drx-StartOffset, which defines the subframe where the Long and Short DRX cycles start.

[0133] - drx-ShortCycle (optional): Sets the short DRX cycle.

[0134] - drx-ShortCycleTimer (optional): Sets the duration for which the UE should follow the Short DRX cycle. For example, a value in multiples of the Short DRX cycle can be set by drx-CylceTimer. For example, the value of n can correspond to n*drx-ShortCycle.

[0135] A UE may perform PDCCH monitoring on serving cells within a DRX group when the DRX group is within its active time. Here, a DRX group is a group of serving cells configured by RRC and having the same DRX active time. Here, the active time is a total duration for which the UE monitors the PDCCH, and may include an ON period of a DRX cycle, a time for which the UE performs continuous reception while an inactivity timer has not expired, and a time for which the UE performs continuous reception while waiting for a retransmission opportunity. For example, when DRX is configured, the active time for serving cells within a DRX group is i) while drx-onDurationTimer or drx-InactivityTimer configured for the DRX group is running; or ii) while drx-RetransmissionTimerDL or drx-RetransmissionTimerUL is running on any serving cell within the DRX group; or ra-ContentionResoultionTimer or msgB-RsponseWindow is running; or a PDCCH indicating a new transmission addressed to a C-RNTI addressed to the MAC entity of the UE is not received after successful reception of a random access response to a random access preamble that is not selected by the MAC entity among the contention-based random access preambles.

[0136] A UE can be configured with one or more DRX groups via RRC signaling from a BS. For example, if two DRX groups are configured, each serving cell is uniquely assigned to one of the two DRX groups. The DRX parameters drx-onDurationTimer and drx-InactivityTimer are configured separately for each DRX group, and the DRX parameters drx-SlotOffset, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-LongCycleStartOffset, drx-ShortCycle (optional), drx-ShortCycleTimer (optional), drx-HARQ-RTT-TimerDL, and drx-HARQ-RTT-TimerUL are common to the DRX groups. Since each serving cell belongs to only one of the DRX groups, and the DRX parameters drx-onDurationTimer and drx-InactivityTimer are set for each DRX group, and the remaining DRX parameters are common to the DRX groups, it can be said that a serving cell is associated with only one set of DRX parameters.

[0137] Fig. 7 illustrates a case where a Long DRX cycle and a Short DRX cycle are set. In particular, Fig. 7 illustrates a case where drx-ShortCycleTimer is set to 2.

[0138] A BS can configure a Long DRX cycle and an additional Short DRX cycle that is shorter than the Long DRX cycle. If a Short DRX cycle is not configured, the UE follows the Long DRX cycle. When configuring a Short DRX cycle, the BS sets the duration of the Long DRX cycle to be a positive integer multiple of the Short DRX cycle. The same onDurationTimer value is configured for the Long DRX cycle and the Short DRX cycle. If there is no data activity during the ON period of the Long DRX cycle (e.g., no PDCCH reception), the UE follows the Long DRX cycle as if the Short DRX cycle is not configured. If there is data activity during the ON period of the Long DRX cycle, for example, while drx-onDurationTimer is running, the UE switches to the Short DRX cycle and follows the Short DRX cycle for a certain period of time (e.g., while drx-ShortCycleTimer is running). At this time, the start of the ON period in the Short DRX cycle is determined by drx-StartOffset and drx-SlotOffset, just like the Long DRX cycle. Referring to FIG. 7, if there is no data activity during the time following the Short DRX cycle, for example, if there is no data activity during the period defined by drx-ShortCycleTimer*drx-ShortCycle, the UE switches to the Long DRX cycle after drx-ShortCycleTimer Short DRX cycles.

[0139] Network energy saving and cell DRX / DTX

[0140] Energy conservation of base stations (BSs) is a key consideration in wireless communication systems, including 3GPP, as it can contribute to building eco-friendly networks by reducing carbon emissions and reducing the operational expenditure (OPEX) of telecommunications operators. In particular, the introduction of 5G communications will require higher transmission rates, necessitating BSs to be equipped with more antennas and provide services over wider bandwidths and frequency bands. Consequently, recent studies have shown that BS energy costs have reached up to 20% of total OPEX. This heightened interest in BS energy conservation led to the approval of a new study item, "Study on Network Energy Savings," in 3GPP NR Release 18. For example, to improve the energy saving capability of BS from the perspective of transmission and reception, the study investigates how to achieve dynamic and / or semi-static and finer granularity adaptation of transmission and / or reception to more efficient operation with one or more network energy saving techniques in time, frequency, space and power domains using potential assistance / feedback of UE and potential UE assistance information.

[0141] Hereinafter, when a BS operates in a network energy saving (NES) mode for energy saving (ES), it can mean, for example, that the BS sets multiple OFF intervals (i.e., discontinuous transmixxion (DTX) intervals of the BS) in advance to turn off transmission of a specific DL signal during a specific time interval, and dynamically indicates one of the OFF intervals to indicate that the corresponding DL signal will not be transmitted during the predefined time interval, thereby achieving power consumption savings of the BS and UE. Hereinafter, the NES mode can also mean an operation mode in which power consumption savings of the BS and UE are achieved not only in the domain but also in the frequency domain, such as BWP switching, dynamic resource block (RB) adaptation, etc., and in the spatial domain, for example, when a specific receive antenna port of the BS is turned off semi-statically or dynamically, by the BS not performing transmission and / or reception through the corresponding antenna port.

[0142] As explained above, after the UE initially accesses the BS and enters connected mode, it must continuously perform PDCCH monitoring to check if there is a transmission scheduled for it in each configured search space. However, if this scheduling is not always present, the UE may quickly drain its battery due to unnecessary PDCCH monitoring every time. Therefore, the BS can set the UE to an ON duration during which it must perform PDCCH monitoring and an OFF duration during which it does not need to perform PDCCH monitoring. In other words, the BS can set the UE to connected mode discontinuous reception (C-DRX) to save power. From the BS's perspective, the UE's C-DRX can also help save energy for the BS. For example, during the C-DRX OFF period of a specific UE, the BS does not need to transmit the PDCCH of the specific UE, so the BS can use its resources (e.g., radio resources during the C-DRX OFF period of the specific UE) for other purposes or obtain energy saving (ES) benefits through DTX / DRX. However, since the UE can transmit without restriction as needed on pre-configured resources (e.g., SR, PUCCH, CG PUSCH, etc.) even during the OFF period, the BS must wait for UL reception of the UE, which may be transmitted at any time. In addition, since C-DRX is configured UE-specifically, the DRX cycles or ON / OFF periods between UEs within a cell (or BS) are not aligned.Therefore, if the ON periods of UEs are set in a time division multiplexing (TDM) format, it may be difficult to expect ES gain because the BS cannot sleep for PDCCH transmission for each ON period of each UE within the cell (or BS).

[0143] Therefore, in some implementations of this specification, the BS can save energy by turning OFF transmission / reception of specific signals / channels during inactive periods through cell-specific DTX / DRX configuration with alternating active and inactive periods, similar to UE C-DRX. In order for a UE to transmit or receive data, it must establish a connection with the BS and enter RRC_CONNECTED mode / state. If there is no activity of the UE for a certain period of time, the BS can reduce the power consumption of the UE by transitioning the UE to RRC_IDLE mode / state. Since the UE must transition back to connected mode whenever transmission / reception is required, RRC signaling occurs during the process of the UE establishing an RRC connection, and latency is increased due to this RRC signaling. If a UE needs to transmit small data frequently, the transition between RRC_IDLE and RRC_CONNECTED will not only increase the delay but also increase the signaling overhead. To reduce the BS signaling overhead and the delay in data transmission / reception due to these frequent RRC state changes, a new state called RRC_INACTIVE is introduced. The INACTIVE mode (i.e., RRC_INACTIVE mode) can perform data transmission / reception operations quickly and with low signaling overhead by suspending the RRC connection. In some implementations of the present specification described below, a method for configuring parameters of cell DTX / DRX configuration, a method for activation, and a method(s) for transmission / reception of signals and channels affected by cell DTX / DRX operation are described to apply cell DTX / DRX operation not only to UEs in connected mode but also to UE(s) in IDLE mode and UE(s) in INACTIVE mode.

[0144] A UE in connected mode monitors PDCCH during periodic ON periods to check if there is UL / DL to transmit / receive, and when a PDCCH is received, performs DL reception or UL transmission according to the instructions of the PDCCH. In the case of UL, the UE can wake up from sleep mode and transmit a scheduling request (SR) if there is data to be sent in the UL buffer, regardless of C-DRX. A UE in idle mode periodically performs paging monitoring, and if the UE is not the target UE of the paging, it can operate in idle mode (idle mode DRX (i.e., I-DRX)) which returns to sleep mode. Here, the UE operating in sleep mode can mean performing SR transmission “regardless of the active time determined by C-DRX” or “even in a period other than the active time determined by C-DRX.” In C-DRX operation, a time period consisting of an ON period and an OFF period is repeated, which is called a DRX cycle. The length of a DRX cycle can be defined as from the start of an ON period to before the next ON period, and a DRX cycle can be divided into a Long DRX cycle and a Short DRX cycle. If the length of the DRX cycle becomes longer, if the BS has a PDSCH to send immediately after the end of a specific ON period of the UE, it must wait until the next ON period of the UE, which may increase latency. From the BS's perspective, Since the UE does not transmit periodic CSI (P-CSI) or sounding reference signal (SRS) during the OFF period, the resource (i.e., the resource for P-CSI or SRS transmission) can be allocated to another UE to increase resource utilization.Additionally, the BS may also operate in energy saving mode to save power during the UE's OFF period.

[0145] In relation to C-DRX, the BS may instruct the UE to enter DRX sleep mode directly without operating in active mode until the end of the ON period via the DRX command MAC control element (CE). For example, the BS may instruct the UE to terminate the current active time and directly enter a DRX cycle. If only a Long DRX cycle is configured for the UE, the UE may operate in the Long DRX cycle (based on the DRX command MAC CE). If both a Long DRX cycle and a Short DRX cycle are configured, the UE will immediately enter the Short DRX cycle after receiving the DRX command MAC CE. In addition, if the BS provides a Long DRX command MAC CE, the UE may operate in the Long DRX cycle even if a Short DRX cycle is configured. Additionally, BS can control / change the starting point of the Long DRX cycle via the RRC parameter drx-LongCycleStartOffset, which is used to set the Long DRX cycle and the drx-StartOffset, which defines the subframe in which the Long and Short DRX cycles start. Here, the value of the RRC parameter drx-LongCycleStartOffset is defined in ms units so that the Long DRX cycle can start at the slot boundary. Additionally, the starting point of the ON period can be set at slot level granularity via another RRC parameter drx-SlotOffset. In this case, the relative position of the ON period is defined by applying the slot offset indicated (by drx-SlotOffset) with respect to the reference point indicated by drx-LongCycleStartOffset.

[0146] By waking up the UE only during the ON period and monitoring the presence of PDCCH transmitted to itself through C-DRX configuration, energy can be saved compared to continuously (e.g., at every slot) monitoring the PDCCH. In addition, if the BS has no data to transmit in the upcoming ON period of the UE, the BS can further save the battery of the UE by transmitting a wake-up signal (WUS) before the start of the ON period of the UE to inform the UE that there is no need to wake up in the ON period (i.e., there is no need to start the onDuration timer). Here, for the UE among the UEs configured with C-DRX and that there is no data to transmit / receive in the upcoming ON period, the BS can transmit a WUS that can be transmitted via DCI format 2_6, which is used to notify power saving information outside the DRX active time for one or more UEs, at a WUS occasion configured before the ON period, to indicate to the UE that there is no need to wake up in the current ON period. A UE that receives the above WUS (e.g., wake-up indication via DCI format 2_6) can save more energy because it can continue to sleep without switching to active mode.

[0147] In the following description, UE DRX or C-DRX, I-DRX may mean discontinuous reception from the UE's perspective, cell DRX may mean discontinuous reception from the BS's perspective, and cell DTX may mean discontinuous transmission from the BS's perspective. Cell DRX may mean UL transmission OFF from the UE's perspective, and cell DTX may mean DL reception OFF from the UE's perspective.

[0148] Cell DTX / DRX configuration can include parameters such as periodicity, slot / offset, and On period similar to the C-DRX configuration of the UE. Cell DTX configuration and cell DRX configuration can be independently configured and activated / deactivated to operate. That is, cell DTX can be configured and activated without cell DRX configuration to perform cell DTX operation, or conversely, cell DRX can be configured without cell DTX configuration to perform cell DRX operation. Even if both cell DTX and cell DRX are configured, only one of the two settings can be activated and operate. According to the cell DTX / DRX operation, as in a structure similar to the C-DRX of the UE, an active period (also called an ON period) can be set in which all signals and channels can be transmitted / received without restriction, and a non-active period, which is a time period outside the active period in which transmission / reception of all signals and channels is OFF or transmission / reception of only specific signals and channels is performed in a restricted manner (e.g., only transmission / reception of channels / signals such as PDCCH transmission or RACH / SR PUCCH reception is allowed). The cell DTX / DRX configuration can be set and activated only by RRC (i.e., only through RRC signaling), or all or part of the parameters for the cell DTX / DRX can be set by RRC and activated through L1 signaling such as PDCCH or DCI (e.g., (group-common) DCI). During the active period of cell DTX / DRX, transmission / reception of all signals and channels is possible without any special transmission / reception restrictions, just like normal operation of BS.The time interval outside the active interval is basically considered as a non-active interval, and transmission / reception may be restricted except for the preset signal(s) and channel(s), and since the BS can obtain ES gain through the operation of performing only this minimum transmission / reception, the operation when the NES state / mode is ON may be considered in the time interval outside the active interval.

[0149] For example, to reduce the BS downlink transmission / uplink reception active time, the UE can be configured with a periodic cell DTX / DRX pattern (i.e., active and non-active periods). The pattern configuration for cell DTX / DRX can be common to the UEs in the cell. Each serving cell can be configured with a periodic cell DTX pattern by RRC. The BS can configure only cell DTX, only cell DRX, or both for a cell. Cell DTX and cell DRX patterns can be configured and activated separately. Up to N cell DTX / DRX patterns per MAC entity can be configured for different serving cells, where N can be a predefined value. Cell DTX / DRX can be activated / deactivated by RRC signaling or L1 group common signaling (e.g., signaling via group-common PDCCH). The BS can control the cell DTX and cell DRX operation by providing the cell DTX / DRX configuration via RRC signaling. For example, the BS can provide RRC parameters in the cell DTX / DRX configuration regarding a timer for an active period at the beginning of a cell DTX / DRX cycle (e.g., a cell DTX / DRX ON duration timer), a subframe in which the cell DTX / DRX cycle starts, a delay before the active period starts, a cell DTX / DRX cycle period (i.e., a cell DTX / DRX cycle), etc. The active duration of the cell DTX / DRX can be a period of time during which the UE waits to receive PDCCHs or SPS occasions and to transmit an SR or CG. A cycle of the cell DTX / DRX specifies a periodic repetition of an active period followed by an inactive period. The active duration and cycle parameters can be common between the cell DTX and the cell DRX.The BS may configure the C-DRX and the cell DTX / DRX such that there is at least a partial overlap between the C-DRX ON period of the UE and the cell DTX / DRX active period. For example, the BS may configure the C-DRX periodicity of the UE to be an integer multiple of the cell DTX / DRX periodicity, or the cell DTX / DRX periodicity to be an integer multiple of the C-DRX periodicity of the UE.

[0150] In some implementations, cell DTX operation may affect the UE's monitoring activity for PDCCH and configured downlink assignments in RRC_CONNECTED. For a serving cell for which cell DTX is configured and active, a UE (e.g., the MAC entity of the UE) monitors PDCCH on the serving cell if the serving cell is within the cell DTX active period. The cell DTX active period of a serving cell may include the time that a cell DTX / DRX ON duration timer runs for the serving cell. For example, for a serving cell for which cell DTX is configured and active, a UE (e.g., the MAC entity of the UE) may not monitor PDCCH on the serving cell if the serving cell is not within the cell DTX active period or is within the UE C-DRX active period, and may not receive transport blocks on the serving cell according to the configured downlink assignment for SPS (i.e., perform SPS PDSCH reception). That is, when cell DTX is set and activated for a serving cell, the UE may not perform PDCCH monitoring on the serving cell or monitor SPS periods on the serving cell during the cell DTX inactivity period.

[0151] In some implementations, cell DRX operation may control SR and configured uplink grant transmission activity in RRC_CONNECTED. In some scenarios, when cell DRX is configured and activated for a serving cell, the UE (e.g., the MAC entity of the UE) may, in principle, perform CG PUSCH transmissions and (if the serving cell is a PUCCH cell) PUCCH transmissions on the serving cell only within the cell DRX active period. The cell DTX active period of a serving cell may include the time that the cell DTX / DRX ON duration timer runs for the serving cell. For example, if a serving cell for which cell DRX is configured and activated is within a cell DRX inactive period, the UE (e.g., the MAC entity of the UE) does not transmit SR on PUCCH resources for SR (even if the serving cell is a PUCCH cell), does not report periodic CSI on PUCCH (even if the serving cell is a PUCCH cell), and does not report semi-persistent CSI configured on PUSCH of the serving cell. In other words, if cell DRX is configured and activated for a serving cell, the UE may not transmit on CG resources of the serving cell or may not transmit SR on the serving cell during the DRX inactive period.

[0152] Meanwhile, in addition to the cell DTX / DRX configuration where a specific ON / OFF duration pattern is periodically repeated in advance, the BS may perform cell OFF to completely turn off a specific cell for a certain period of time to save more energy. When a cell is turned OFF, the UEs in that cell cannot transmit / receive data at all and may need to move to another turned-on cell. In particular, if the target cell for cell OFF is the PCell of specific UEs, it may be necessary to trigger a handover process for the UE to change the PCell.

[0153] The CHO described above refers to a process in which a UE performs / triggers a handover process on its own when a preset condition is satisfied, even if the BS does not directly issue a handover command. A UE for which CHO is set by a BS of a source cell evaluates whether one or more handover conditions (e.g., RSRP / RSRQ of a reference signal, SINR, etc.) are satisfied, and if the conditions are satisfied, performs a handover process of transmitting a RACH to a target cell. If a UE has a CHO setting, it starts evaluating the CHO execution conditions, and the UE may have to continuously evaluate the CHO execution conditions until it receives a handover command from the BS to perform a handover or performs a handover to a candidate cell that satisfies the CHO execution conditions. That is, if a CHO setting is provided, the UE may have to continue to perform measurements for evaluating the CHO execution conditions while unnecessarily consuming power even in a situation in which an RRC reconfiguration is not required. Meanwhile, if the CHO setting is provided to the UE and there is a cell DTX / DRX setting for the serving cell of the UE, there is a possibility that the CHO execution condition is determined to be satisfied due to an inactive period of the cell DTX / DRX, which may result in an unnecessary handover.

[0154] Taking this into account, in some implementations of the present specification described below, the BS can dynamically indicate to the UE that it will trigger the CHO procedure (e.g., use the CHO execution conditions). For example, the handover procedure trigger can be dynamically indicated via L1 (UE-specific or group-common) signaling. In particular, in some implementations of the present specification described below, the handover procedure trigger can be transmitted group-commonly to multiple UEs within a cell by utilizing the DCI format for activation / deactivation of cell DTX / DRX configuration. In this case, there may be a benefit in terms of signaling overhead. In addition, in some implementations of the present specification described below, since the DCI format for activation / deactivation of cell DTX / DRX configuration is composed of serving cell-specific information blocks, the BS can utilize the DCI format to trigger the handover procedure by adding a cell OFF indication bit to the information block for the PCell of a specific UE.

[0155] Below are described some implementations of this specification regarding an L1 signaling method that triggers handover of UEs within a cell to another cell when a BS wants to temporarily turn off the cell for a long period of time to save energy.

[0156] <Method #1> A method of adding a CHO triggering bit for cell OFF to DCI (e.g., DCI format 2_9) indicating activation / deactivation of cell DTX / DRX settings, and a method of determining the position of the CHO triggering bit and the bit position of the information block (i.e., the dispatcher field) for the UE.

[0157] (1) A method of setting an additional (start) position indication RRC parameter that indicates the bit position for CHO triggering purposes in addition to the RRC parameter that indicates the start bit position of the information block in DCI format 2_9.

[0158] (2) A method of setting the bit width of an information block in addition to the RRC parameter indicating the start position of the information block in DCI format 2_9.

[0159] (3) A method of implicitly notifying that a bit for the corresponding CHO triggering bit is added after the start bit position (for PCell) when the CHO triggering bit setting is set by a separate RRC parameter.

[0160] (4) A method of deactivating (or activating) the SCell when the CHO triggering bit set in the information block corresponding to the SCell from the perspective of a specific UE in DCI format 2_9 indicates cell OFF (or cell ON).

[0161] Figure 8 illustrates the structure of a DCI format for activating / deactivating cell DTX / DRX settings.

[0162] In some implementations of this specification, DCI format 2_9 may be used to activate or deactivate cell DTX and / or DRX configuration of one or more serving cells for one or more UEs.

[0163] For example, a UE may be configured with cell DTX configuration and / or cell DRX configuration for a serving cell, and activation or deactivation of the configured cell DTX / DRX configuration may be set via higher layer signaling such as an RRC signal, and may also receive an activation / deactivation instruction dynamically in a group-common manner via DCI format 2_9. DCI format 2_9 can be used for multiple UEs. In addition, each UE may have one or multiple serving cells. Accordingly, as illustrated in FIG. 8, DCI format 2_9 may be configured with multiple information blocks for each of the serving cell(s) of multiple UEs, and each information block may be configured to include at least one bit for activation or deactivation of the configured cell DTX configuration for the corresponding serving cell and / or one bit for activation or deactivation of the configured cell DRX configuration. When a UE is configured to monitor DCI format 2_9 in a Type-3 common search space, the position of the information block that it must monitor within DCI format 2_9 can be set in advance as an RRC parameter (hereinafter, position-inDCI-NES). Referring to FIG. 8, for example, if cell #1, cell #2, and cell #3 among the cells that BS supports cell DTX / DRX operation are respectively configured as serving cell #a, serving cell #c, and serving cell #b of UE #1, cell #2 is configured as serving cell #a of UE #2, and cell #3 is configured as serving cell d of UE #3, the BS may provide cell DTX / DRX configuration for the serving cell to each UE having the serving cell(s) for which cell DTX / DRX operation is to be configured, and if the BS wishes to activate the cell DTX / DRX configuration by DCI format 2_9, it may provide the UE(s) with the start bit position of the information block of DCI format 2_9 for the serving cell having the cell DTX / DRX configuration.When the BS transmits DCI format 2_9 including block 1 to block N, each UE can monitor DCI format 2_9 on the Type-3 common search space, detect DCI format 2_9, read information block(s) for its serving cell(s) at the start bit position(s) corresponding to the serving cell(s), and activate or deactivate cell DTX / DRX set for the corresponding serving cell(s) based on the bit value(s) of the information block(s).

[0164] Each information block of DCI format 2_9 may have different bit widths depending on whether cell DTX / DRX is configured. For example, in the case of a serving cell in which only cell DTX or cell DRX is configured, the corresponding information block may consist of 1 bit, and the 1 bit may indicate activation or deactivation of cell DTX or cell DRX for the serving cell depending on whether its value is 0 or 1. As another example, in the case of a serving cell in which both cell DTX and cell DRX are configured, the corresponding information block may consist of 2 bits, and the first bit of the 2 bits may indicate activation or deactivation of cell DTX operation, and the second bit may indicate activation or deactivation of cell DRX operation.

[0165] Figures 9 and 10 illustrate structures of DCI format 2_9 according to some implementations of the present specification.

[0166] In some implementations of this specification, DCI format 2_9 may be used to provide cell OFF mode indication (i.e., NES mode indication) of the primary cell(s) for one or more UEs. For example, referring to FIG. 9, a cell OFF CHO triggering bit may be added within an information block for a specific serving cell (e.g., PCell) among the information blocks within DCI format 2_9. In this case, the information block corresponding to the serving cell may be composed of 1 bit, 2 bits, or n bits depending on whether cell DTX / DRX configuration is present. Assuming that the CHO triggering bit is 1 bit, for example, if there is no cell DTX / DRX setting for the serving cell but the CHO triggering bit is present, the information block for the serving cell can be composed of 1 bit, if only one of cell DTX and cell DRX is set for the serving cell and the CHO triggering bit is present, the information block for the serving cell can be composed of 2 bits, and if both cell DTX and cell DRX are set for the serving cell and the CHO triggering bit is present, the information block for the serving cell can be composed of 3 bits.

[0167] Alternatively, in some implementations of this specification, the CHO triggering bit may be set at a specific location separate from the information block(s) indicating activation or deactivation of the cell DTX / DRX configuration within DCI format 2_9. For example, the CHO triggering bit(s) may be set at the very beginning, the very end, or before or after a specific information block within DCI format 2_9.

[0168] When a bit for CHO triggering indication is added in DCI format 2_9, the UE must know the position of the bit within DCI format 2_9 in order to monitor the bit. As described above, when the UE is configured to monitor DCI format 2_9 in Type-3 CSS (i.e., Type3-PDCCH CSS), the position of the information block that it should monitor within DCI format 2_9 is preset by an RRC parameter (e.g., position-inDCI-NES). Similarly, in some implementations of the present specification, an additional (start) position indication RRC parameter may be configured to indicate the bit position for CHO triggering. In this case, in some implementations, the RRC parameter for CHO triggering bit position indication may be configured to indicate an offset value with respect to position-inDCI-NES (for PCell). For example, if the CHO triggering bit is 1 bit and is located at the very back of the blocks indicating activation (release) of cell DTX / DRX configuration for each serving cell in DCI format 2_9, then the UE can read the 1-bit indication field at that position to determine whether the PCell is instructed to turn off cell based on whether it is '0' or '1', and if the cell OFF is instructed, the UE can trigger a pre-configured conditional handover procedure to perform a handover to the target cell. For example, if the CHO triggering bit has a value indicating cell OFF, i.e., a value indicating that the CHO procedure is triggered, the UE can evaluate whether the CHO running condition is satisfied for the CHO candidate cell(s), and if at least one CHO candidate cell satisfies the CHO running condition, disconnect from the PCell and perform the CHO procedure to synchronize with the CHO candidate cell that satisfies the CHO running condition.

[0169] Alternatively, the BS can also set the addition and position of the CHO triggering bit by additionally setting the bit width of the information block in the RRC parameter (e.g., position-inDCI-NES) indicating the position of the information block. When the UE has multiple serving cells for which cell DTX / DRX is configured, the UE monitors multiple information blocks in the DCI format 2_9, and the bit width of the information block corresponding to the PCell is 1 bit when only cell DTX or cell DRX is configured, and 2 bits when both cell DTX and cell DRX are configured. However, if there is an additional setting related to the bit width, the setting related to the bit width can set to the UE that the CHO triggering bit is included in the corresponding information block in addition to the cell DTX / DRX activation (release) bit(s). For example, if only cell DTX is configured in the PCell of a specific UE and the bit width is set to 2 bits, the UE may be notified that 1 bit of the 2 bits is a bit for cell DTX activation (release) and the remaining 1 bit is a bit for CHO triggering. At this time, the position of the CHO triggering bit may be set before, after, or in the middle of the bit(s) for activation (release) of cell DTX / DRX configuration (i.e., between the bit for activation (release) of cell DTX configuration and the bit for activation (release) of cell DRX configuration), which may be defined / promised in the standard or may be set in advance by the base station.

[0170] Alternatively, in some implementations of the present specification, the CHO triggering bit configuration (i.e., the presence of a CHO triggering bit) may be configured by a separate RRC parameter. When the CHO triggering bit configuration is configured by a separate RRC parameter, it may implicitly indicate that a bit for the corresponding CHO triggering bit is added to the information block from position-inDCI-NES (for PCell). That is, instead of an RRC parameter indicating the position of the CHO triggering bit or an RRC parameter indicating the bit width, if a configuration indicating the presence of the CHO triggering bit is provided by a separate RRC parameter, the UE may implicitly know that the CHO triggering bit is included in the information block corresponding to the PCell in addition to the cell DTX / DRX activation (release) bit(s). For example, if only cell DTX is configured for the PCell of a specific UE, and an RRC parameter for setting a CHO triggering bit (for the UE) is configured, the UE can implicitly know that the corresponding information block consists of 2 bits, 1 bit of the 2 bits is for activating (deactivating) cell DTX, and the remaining 1 bit is for CHO triggering. As another example, if both cell DTX and cell DRX are configured for the PCell of the UE, and an RRC parameter for setting a CHO triggering bit (for the UE) is configured, the UE can implicitly know that the corresponding information block consists of 3 bits, and 2 bits of the 3 bits are for activating (deactivating) cell DTX, and the remaining 1 bit is for CHO triggering. At this time, the position of the CHO triggering bit can be set before, after, or in the middle of the bit(s) for activating (releasing) the cell DTX / DRX configuration (i.e., between the bit(s) for activating (releasing) the cell DTX configuration and the bit(s) for activating (releasing) the cell DRX configuration), and this can be defined / promised in the standard or set to the UE(s) by the BS in advance.For example, referring to block 1 in FIG. 10, if cell DTX / DRX configuration is provided for PCell of UE #1, and RRC parameters related to CHO triggering bit are set (or RRC parameters indicating the presence of CHO triggering bit are set) (to UE #1), UE #1 can read 2 bits if only cell DTX or cell DRX is set or 3 bits if both cell DTX and cell DRX are set, starting from the start bit position of information block (block 1 in the example of FIG. 10) for the corresponding serving cell (i.e., its own PCell), and can activate or deactivate cell DTX / DRX configuration based on the first 1 bit or 2 bits, and can decide whether to execute CHO procedure based on the last 1 bit. For example, if the last 1-bit of the information block for the PCell of UE #1 has a first value (e.g., '0'), the UE #1 may not execute the CHO procedure (e.g., not start evaluating whether the candidate cell(s) for CHO satisfy the CHO execution conditions), and if the last 1-bit has a second value (e.g., '1'), the UE #1 may execute the CHO procedure (e.g., start evaluating whether the candidate cell(s) for CHO satisfy the CHO execution conditions).As another example, referring to block 2 in FIG. 10, if cell DTX / DRX configuration is provided for PCell of UE #2 and RRC parameters related to CHO triggering bit are set (or RRC parameters indicating presence of CHO triggering bit are set) (to UE #2), UE #2 can read 2 bits if only cell DTX or cell DRX is set or 3 bits if both cell DTX and cell DRX are set, starting from the start bit position of information block for its PCell (block 2 in the example of FIG. 10), and can activate or deactivate cell DTX / DRX configuration based on the first 1 bit or 2 bits, and can decide whether to execute CHO procedure based on the last 1 bit. For example, if the last 1 bit of the information block for the PCell of UE #2 has a first value (e.g., '0'), then the UE #1 may not execute the CHO procedure (e.g., not start evaluating whether the candidate cell(s) for CHO satisfy the CHO execution conditions), and if the last 1 bit has a second value (e.g., '1'), then the UE #1 may execute the CHO procedure (e.g., start evaluating whether the candidate cell(s) for CHO satisfy the CHO execution conditions). However, in the example of FIG. 10, since block 2 is an information block for SCell #2 and not PCell for UE #1, UE #1 may start from the start bit position configured for SCell #2, and read 1 bit if only cell DTX or cell DRX is configured for SCell #2, or 2 bits if both cell DTX and cell DRX are configured, and activate or deactivate cell DTX / DRX configuration based on the corresponding bit value(s).As another example, in some implementations, if a cell DTX / DRX configuration is present for a PCell of a UE, but an RRC parameter related to a CHO triggering bit is absent or an RRC parameter indicating the absence of a CHO triggering bit is set, the UE (e.g., see UE #K of FIG. 10) may determine that the information block for its PCell does not include a CHO triggering bit, and may determine activation or deactivation of the cell DTX / DRX configuration for the PCell based on 1 or 2 bits constituting the information block for the PCell.

[0171] Meanwhile, for a UE with multiple serving cells configured, Cell#1 may be a PCell for UE #A but an SCell for another UE #B, and conversely, Cell#2 of UE #B may be a PCell but an SCell for UE #A. Information blocks corresponding to multiple serving cells are configured in DCI format 2_9, and the information block corresponding to the PCell may be different for each UE. In some implementations of this specification, if a UE can read the CHO triggering bit configured for an SCell as well as the CHO triggering bit configured for the PCell, it can perform SCell activation / deactivation (e.g., stop transmission and / or reception of signals / channels on the corresponding SCell and transmission and / or reception of signals / channels related to the corresponding SCell) without a separate MAC control element (CE) instruction through an SCell opening CHO triggering bit instruction. For example, even if UE #A's SCell becomes cell OFF, UE #A does not trigger a CHO procedure, but can deactivate the corresponding SCell. That is, based on the DCI in which the CHO triggering bit indicates SCell OFF for UE #A, UE #A can deactivate the corresponding SCell, and UE #B can trigger a PCell change, i.e., a CHO procedure. In this case, signaling overhead can be reduced since a separate SCell deactivation MAC CE indication is not required. Since DCI-based SCell activation (release) does not have HARQ-ACK (i.e., HARQ-ACK feedback specified for DCI-based SCell activation (release)), HARQ-ACK feedback such as NACK-only may be introduced to address potential reliability issues (e.g., misalignment between BS and UE regarding SCell activation (release).

[0172] Method #1 described above described several implementations of this specification for adding a CHO triggering bit to DCI format 2_9 and setting its location. However, some implementations of this specification are not limited to CHO triggering bits, and the same methods can be applied when adding a bit or field for a specific purpose to DCI format 2_9 and setting its location. In addition, the implementations of this specification described above can also be applied when adding a CHO triggering bit to an information block corresponding to a cell other than a PCell (e.g., an SCell).

[0173] According to some implementations of this specification, when a BS wants to apply NES-mode to a cell, for example, to turn OFF the cell, the BS may trigger a CHO procedure for the UE(s) using the cell as a PCell through a DCI format used to activate or deactivate cell DTX and / or DTX configuration of the serving cell(s) for the UE(s), thereby enabling the UE(s) using the cell as a PCell to perform signal transmission / reception through other cells without interruption.

[0174] According to some implementations of this specification, a UE performs a CHO procedure when a specific bit for its PCell in DCI Format 2_9 has a value indicating that a CHO procedure is triggered, thereby eliminating the need to continuously evaluate CHO execution conditions for candidate cell(s) for CHO. Accordingly, according to some implementations of this specification, UE power consumption may be reduced.

[0175] According to some implementations of this specification, the CHO trigger bit can be provided simultaneously to multiple UEs using the cell to which the NES-mode is applied as a PCell, so that the signaling overhead related to the CHO procedure trigger can be reduced.

[0176] According to some implementations of this specification, energy of the BS and / or UE may be saved.

[0177] Figure 11 illustrates a UE operation flow according to some implementations of this specification.

[0178] A UE may perform operations according to some implementations of the present disclosure. The UE may include at least one transceiver; at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations according to some implementations of the present disclosure. A processing device for the UE may include at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations according to some implementations of the present disclosure. A computer-readable (non-volatile or non-transitory) storage medium may store at least one computer program comprising instructions that, when executed by at least one processor, cause the at least one processor to perform operations according to some implementations of the present disclosure. A computer program or computer program product may be recorded on at least one computer-readable (non-volatile or non-transitory) storage medium and may contain instructions that, when executed, cause (at least one processor) to perform operations according to some implementations of the present specification.

[0179] A method performed by the UE, or in the UE, the processing device, the computer-readable (non-volatile) storage medium, and / or the computer program product, the operations may include: receiving a first parameter regarding a start bit position of a specific downlink control information (DCI) format for a serving cell (S1101); detecting the specific DCI format (S1103); and determining whether to trigger a CHO procedure including evaluating a CHO condition based on a CHO-related field in an information block for the serving cell within the specific DCI format if i) a second parameter regarding a conditional handover (CHO)-related bit is set and ii) the serving cell is a primary cell (PCell) of the UE (S1105).

[0180] In some implementations, based on i) the second parameter being set and ii) the serving cell being the PCell of the UE, the CHO related field may be the last 1 bit of the information block.

[0181] In some implementations, based on i) the second parameter being set and ii) the serving cell being the PCell of the UE, and ii) cell discontinuous transmission (DTX) and cell discontinuous reception (DRX) being set for the serving cell, the information block is composed of three bits, and the first two bits of the information block can be used for activating or deactivating at least one of the cell DTX or the cell DRX.

[0182] In some implementations, based on i) that the second parameter is set and ii) that the serving cell is the PCell of the UE, and ii) that cell discontinuous transmission (DTX) or cell discontinuous reception (DRX) is set for the serving cell, the information block consists of two bits, and the first bit of the information block can be used to activate or deactivate the cell DTX or the cell DRX set for the serving cell.

[0183] In some implementations, the particular DCI format may be DCI format 2_9.

[0184] In some implementations, the method or operations may include: monitoring the particular DCI format over a common search space.

[0185] In some implementations, the method or the operations may include: executing a handover to another cell based on the CHO-related field including a first value and the CHO condition being met.

[0186] In some implementations, the CHO procedure may not be triggered based on the CHO-related field containing the second value.

[0187] In some implementations, the method or the operations may include: i) the second parameter is not set, or ii) the UE does not obtain the CHO-related field from the information block based on the serving cell being a secondary cell of the UE.

[0188] In some implementations, the method or the operations may include considering the information block to not include the CHO related field based on: i) the second parameter is not set, or ii) the serving cell is a secondary cell of the UE.

[0189] In some implementations, the method or the operations may further comprise: receiving a setting regarding the CHO condition.

[0190] Figure 12 illustrates a BS operation flow according to some implementations of this specification.

[0191] A BS may perform operations according to some implementations of the present disclosure. The BS may include at least one transceiver; at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations according to some implementations of the present disclosure. A processing device for the BS may include at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations according to some implementations of the present disclosure. A computer-readable (non-volatile or non-transitory) storage medium may store at least one computer program comprising instructions that, when executed by the at least one processor, cause the at least one processor to perform operations according to some implementations of the present disclosure. A computer program or computer program product may be recorded on at least one computer-readable (non-volatile or non-transitory) storage medium and may contain instructions that, when executed, cause (at least one processor) to perform operations according to some implementations of the present specification.

[0192] A method performed by the BS, or in the BS, the processing device, the computer-readable (non-volatile) storage medium, and / or the computer program product, the operations may include: transmitting (S1201) a first parameter regarding a start bit position of a specific downlink control information (DCI) format for a serving cell of a user equipment (UE); and transmitting (S1203) the specific DCI format. Based on i) a second parameter regarding a conditional handover (CHO) related bit being set and ii) the serving cell being a primary cell (PCell) of the UE, an information block for the serving cell in the specific DCI format may include a CHO related field.

[0193] In some implementations, based on i) the second parameter being set and ii) the serving cell being the PCell of the UE, the CHO related field may be the last 1 bit of the information block.

[0194] In some implementations, based on i) the second parameter being set and ii) the serving cell being the PCell of the UE, and ii) cell discontinuous transmission (DTX) and cell discontinuous reception (DRX) being set for the serving cell, the information block is composed of three bits, and the first two bits of the information block can be used for activating or deactivating at least one of the cell DTX or the cell DRX.

[0195] In some implementations, based on i) that the second parameter is set and ii) that the serving cell is the PCell of the UE, and ii) that cell discontinuous transmission (DTX) or cell discontinuous reception (DRX) is set for the serving cell, the information block consists of two bits, and the first bit of the information block can be used to activate or deactivate the cell DTX or the cell DRX set for the serving cell.

[0196] In some implementations, the particular DCI format may be DCI format 2_9.

[0197] In some implementations, the particular DCI format may be transmitted over a common search space.

[0198] In some implementations, the information block may not include the CHO related field based on i) the second parameter is not set or ii) the serving cell is not a PCell for any UE.

[0199] In some implementations, the method or the operations may further comprise: transmitting a setting regarding the CHO condition.

[0200] As described above, the examples disclosed herein are provided to enable those skilled in the art to implement and practice the present disclosure. While the examples have been described above with reference to the examples of the present disclosure, those skilled in the art will appreciate that various modifications and variations may be made to the examples of the present disclosure. Accordingly, the present disclosure is not intended to be limited to the examples described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

[0201] Implementations of this specification can be used in wireless communication systems, BSs, UEs, and other equipment.

Claims

1. In a method using a user equipment (UE), Receive a first parameter regarding the start bit position of a specific downlink control information (DCI) format for a serving cell; Detecting the above specific DCI format; i) a second parameter regarding a conditional handover (CHO) related bit is set, and ii) based on the serving cell being the primary cell (PCell) of the UE, Obtaining a CHO related field from an information block for the serving cell within the specific DCI format, and Based on the above CHO related fields, determining whether to trigger a CHO procedure including evaluating a CHO condition, method.

2. In paragraph 1, i) based on the second parameter being set and ii) the serving cell being the PCell of the UE, the CHO related field is the last 1 bit of the information block. method.

3. In paragraph 2, i) based on the second parameter being set and ii) based on the serving cell being the PCell of the UE, and ii) based on the cell discontinuous transmission (DTX) and cell discontinuous reception (DRX) being set for the serving cell, the information block is composed of three bits, and the first two bits of the information block are used for activating or deactivating at least one of the cell DTX or the cell DRX. method.

4. In paragraph 2, i) based on the second parameter being set and ii) based on the serving cell being the PCell of the UE, and ii) based on the cell discontinuous transmission (DTX) or cell discontinuous reception (DRX) being set for the serving cell, the information block is composed of two bits, and the first bit of the information block is used for activating or deactivating the cell DTX or the cell DRX set for the serving cell. method.

5. In paragraph 1, The above specific DCI format is DCI format 2_9, method.

6. In paragraph 1, Comprising monitoring the specific DCI format on a common search space, method.

7. In paragraph 1, The CHO related field includes a first value, and based on the CHO condition being satisfied, executing a handover to another cell. method.

8. In paragraph 1, The CHO procedure is not triggered based on the above CHO related field containing the second value, method.

9. In paragraph 1, i) the second parameter is not set or ii) the UE does not obtain the CHO related field from the information block based on the serving cell being a secondary cell of the UE. method.

10. In paragraph 1, i) the second parameter is not set or ii) the UE considers that the information block does not include the CHO related field based on the serving cell being a secondary cell of the UE. method.

11. At least one processor; and At least one computer memory operably connectable to said at least one processor and storing instructions that, when executed, cause said at least one processor to perform operations for a user equipment (UE), said operations comprising: Receive a first parameter regarding the start bit position of a specific downlink control information (DCI) format for a serving cell; Detecting the above specific DCI format; i) a second parameter regarding a conditional handover (CHO) related bit is set, and ii) based on the serving cell being the primary cell (PCell) of the UE, Obtaining a CHO related field from an information block for the serving cell within the specific DCI format, and Based on the above CHO related fields, determining whether to trigger a CHO procedure including evaluating a CHO condition, device.

12. In a computer-readable non-transitory storage medium, The storage medium stores at least one program code comprising instructions that, when executed, cause at least one processor to perform operations for a user equipment (UE), the operations comprising: Receive a first parameter regarding the start bit position of a specific downlink control information (DCI) format for a serving cell; Detecting the above specific DCI format; i) a second parameter regarding a conditional handover (CHO) related bit is set, and ii) based on the serving cell being the primary cell (PCell) of the UE, Obtaining a CHO related field from an information block for the serving cell within the specific DCI format, and Based on the above CHO related fields, determining whether to trigger a CHO procedure including evaluating a CHO condition, Storage media.

13. In the method using a base station (BS), Transmitting a first parameter regarding the start bit position of a specific downlink control information (DCI) format for a serving cell of a user equipment (UE); and Including transmitting the above specific DCI format, i) a second parameter regarding a conditional handover (CHO) related bit is set, and ii) based on the serving cell being a primary cell (PCell) of the UE, an information block for the serving cell within the specific DCI format includes a CHO related field. method.

14. At least one transmitter / receiver; at least one processor; and At least one computer memory operably connectable to said at least one processor and storing instructions that, when executed, cause said at least one processor to perform operations for a base station (BS), said operations comprising: Transmitting a first parameter regarding the start bit position of a specific downlink control information (DCI) format for a serving cell of a user equipment (UE); and Including transmitting the above specific DCI format, i) a second parameter regarding a conditional handover (CHO) related bit is set, and ii) based on the serving cell being a primary cell (PCell) of the UE, an information block for the serving cell within the specific DCI format includes a CHO related field. BS.

15. In paragraph 14, i) based on the second parameter being set and ii) the serving cell being the PCell of the UE, the CHO related field is the last 1 bit of the information block. BS.

16. In paragraph 15, i) based on the second parameter being set and ii) based on the serving cell being the PCell of the UE, and ii) based on the cell discontinuous transmission (DTX) and cell discontinuous reception (DRX) being set for the serving cell, the information block is composed of three bits, and the first two bits of the information block are used for activating or deactivating at least one of the cell DTX or the cell DRX. BS.

17. In paragraph 15, i) based on the second parameter being set and ii) based on the serving cell being the PCell of the UE, and ii) based on the cell discontinuous transmission (DTX) or cell discontinuous reception (DRX) being set for the serving cell, the information block is composed of two bits, and the first bit of the information block is used for activating or deactivating the cell DTX or the cell DRX set for the serving cell. BS.

18. In paragraph 14, The above specific DCI format is DCI format 2_9, BS.

19. In paragraph 14, The above specific DCI format is transmitted over a common search space, BS.

20. In paragraph 14, i) the second parameter is not set or ii) the serving cell is not a PCell for any UE, the information block does not include the CHO related field. BS.

Images