Method, user equipment, processing device, and storage medium for receiving downlink signal, and method and base station for transmitting downlink signal
By configuring DRX for user equipment to manage active and non-active periods, the method addresses the challenge of network energy efficiency in cellular networks, optimizing signal transmission and reception to meet the growing data processing demands in cellular networks.
Patent Information
- Application Number
- PCT/KR2024/006445
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-08-11
- Filing Date
- 2024-05-13
- Publication Date
- 2024-11-21
AI Technical Summary
The increasing demand for data processing in cellular networks due to emerging technologies like M2M communication, smartphones, and the need for enhanced mobile broadband and massive machine-type communication poses challenges in network energy efficiency, particularly in transmitting and receiving downlink and uplink signals effectively.
Implementing a method that includes configuring cell discontinuous reception (DRX) for user equipment (UE) to manage active and non-active periods for uplink transmissions, allowing for efficient monitoring of physical downlink control channels (PDCCH) and scheduling of physical downlink shared channels (PDSCH) based on DRX configurations, which helps in reducing network energy consumption.
This approach enhances network energy saving by optimizing signal transmission and reception periods, thereby improving the overall energy efficiency of both the network and user equipment while supporting increased communication demands.
Smart Images

Figure KR2024006445_21112024_PF_FP_ABST
Abstract
Description
Method for receiving a downlink signal, user device, processing device and storage medium, and method for transmitting a downlink signal and base station
[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 transmitting / receiving downlink signals to enable network energy saving.
[0008] Another technical challenge of this specification is to provide methods and procedures for transmitting / receiving uplink signals to enable network energy saving.
[0009] 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.
[0010] In one aspect of the present disclosure, a method for a user equipment to receive a downlink signal in a wireless communication system is provided. The method may include: receiving a cell discontinuous reception (DRX) configuration for a first cell having physical uplink control channel (PUCCH) resources configured; determining an active period in which uplink transmissions of the first cell are not restricted and a non-active period in which uplink transmissions of the first cell are restricted based on the cell DRX configuration for the first cell; and performing physical downlink control channel (PDCCH) monitoring for a second cell that uses the first cell for PUCCH transmissions based on the first cell being within the active period.
[0011] In another aspect of the present disclosure, a user equipment for receiving a downlink signal in a wireless communication system is provided. The user equipment includes: at least one transceiver; at least one processor; and at least one computer memory operably connectable to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations. The operations may include: receiving a cell discontinuous reception (DRX) configuration for a first cell having physical uplink control channel (PUCCH) resources configured; determining an active period in which uplink transmissions of the first cell are not restricted and a non-active period in which uplink transmissions of the first cell are restricted based on the cell DRX configuration for the first cell; and performing physical downlink control channel (PDCCH) monitoring for a second cell that uses the first cell for PUCCH transmissions based on the first cell being within the active period.
[0012] In another aspect of the present disclosure, a processing device is provided in a wireless communication system. The processing device includes: at least one processor; and at least one computer memory operably connectable to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations. The operations may include: receiving a cell discontinuous reception (DRX) configuration for a first cell having physical uplink control channel (PUCCH) resources configured; determining an active period in which uplink transmissions of the first cell are not restricted and a non-active period in which uplink transmissions of the first cell are restricted based on the cell DRX configuration for the first cell; and performing physical downlink control channel (PDCCH) monitoring for a second cell that uses the first cell for PUCCH transmissions based on the first cell being within the active period.
[0013] In another aspect of the present disclosure, a computer-readable storage medium is provided. The storage medium stores at least one program code comprising instructions that, when executed, cause at least one processor to perform operations, the operations including: receiving a cell discontinuous reception (DRX) configuration for a first cell having physical uplink control channel (PUCCH) resources configured; determining an active period in which uplink transmissions of the first cell are not restricted and a non-active period in which uplink transmissions of the first cell are restricted based on the cell DRX configuration for the first cell; and performing physical downlink control channel (PDCCH) monitoring for a second cell that uses the first cell for PUCCH transmissions based on the first cell being within the active period.
[0014] In another aspect of the present disclosure, a method for transmitting a downlink signal from a base station to a user equipment in a wireless communication system is provided. The method may include: transmitting a cell discontinuous reception (DRX) configuration for a first cell having physical uplink control channel (PUCCH) resources configured; determining an active period in which uplink receptions of the first cell are not restricted and a non-active period in which uplink receptions of the first cell are restricted based on the cell DRX configuration for the first cell; and performing a physical downlink control channel (PDCCH) transmission for a second cell that uses the first cell for PUCCH receptions based on the first cell being within the active period.
[0015] In another aspect of the present disclosure, a base station for transmitting a downlink signal to a user equipment (UE) in a wireless communication system is provided. The base station includes: at least one transceiver; at least one processor; and at least one computer memory operably connectable to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations. The operations may include: transmitting a cell discontinuous reception (DRX) configuration for a first cell having configured physical uplink control channel (PUCCH) resources; determining an active period in which uplink receptions of the first cell are not restricted and a non-active period in which uplink receptions of the first cell are restricted based on the cell DRX configuration for the first cell; and performing a physical downlink control channel (PDCCH) transmission for a second cell that uses the first cell for PUCCH receptions based on the first cell being within the active period.
[0016] In each aspect of the present specification, the method in the user equipment, or the operations in the user equipment, the processing device, or the storage medium may include: performing scheduled PDSCH reception in the second cell based on the first cell being within the active period. In each aspect of the present specification, the method in the base station, or the operations in the base station may include: performing scheduled PDSCH transmission in the second cell based on the first cell being within the active period.
[0017] In each aspect of the present specification, the user equipment, or the method in the user equipment, or the operations may include: not performing PDCCH monitoring for the second cell based on the first cell being within the inactive period. In each aspect of the present specification, the method in the base station, or the operations in the base station may include: not performing PDCCH transmission for the second cell based on the first cell being within the inactive period.
[0018] In each aspect of the present specification, the method in the user equipment, or the operations in the user equipment, the processing device, or the storage medium may include: not performing scheduled PDSCH reception in the second cell based on the first cell being within the non-active period. In each aspect of the present specification, the method in the base station, or the operations in the base station may include: not performing scheduled PDSCH transmission in the second cell based on the first cell being within the non-active period.
[0019] In each aspect of the present specification, in the method in the user equipment, or in the operations in the user equipment, the processing device, or the storage medium: PDCCH monitoring for the second cell may not be performed within the non-active period of the first cell, regardless of whether there is a cell DRX configuration for the second cell. In each aspect of the present specification, in the method in the base station, or in the operations in the base station: PDCCH transmission for the second cell may not be performed within the non-active period of the first cell, regardless of whether there is a cell DRX configuration for the second cell.
[0020] In each aspect of the present specification, the method in the user equipment, or the operations in the user equipment, the processing device, or the storage medium may include: postponing a first PUCCH transmission scheduled within the non-active interval of the first cell to after the non-active interval. In each aspect of the present specification, the method in the base station, or the operations in the base station may include: postponing a first PUCCH reception scheduled within the non-active interval of the first cell to after the non-active interval.
[0021] In each aspect of the present specification, in the method at the user equipment, or in the operations at the user equipment, the processing device, or the storage medium: postponing the first PUCCH transmission to the non-active interval may include: transmitting a HARQ-ACK codebook within the first PUCCH transmission in addition to another HARQ-ACK codebook scheduled after the non-active interval of the first cell. In each aspect of the present specification, in the method at the base station, or in the operations at the base station: postponing the first PUCCH reception to the non-active interval may include: receiving HARQ-ACK information in which a HARQ-ACK codebook within the first PUCCH reception is prepended to another HARQ-ACK codebook scheduled after the non-active interval of the first cell.
[0022] 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.
[0023] According to some implementation(s) of this specification, methods and procedures for energy saving of a network, BS and / or UE may be provided.
[0024] According to some implementation(s) of this specification, methods and procedures for transmitting / receiving downlink signals to enable energy saving of a network, a BS and / or a UE may be provided.
[0025] According to some implementation(s) of this specification, methods and procedures for receiving / transmitting uplink signals to enable energy saving of a network, BS and / or UE may be provided.
[0026] 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.
[0027] 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:
[0028] Figure 1 illustrates an example of a communication system 1 to which implementations of the present specification are applied;
[0029] FIG. 2 is a block diagram illustrating examples of communication devices capable of performing a method according to the present specification;
[0030] FIG. 3 illustrates another example of a wireless device capable of performing implementation(s) of the present specification;
[0031] FIG. 4 illustrates an example of a frame structure available in a 3rd generation partnership project (3GPP) based wireless communication system;
[0032] Figure 5 illustrates a resource grid of slots;
[0033] FIG. 6 illustrates physical channels used in a 3rd generation partnership project (3GPP)-based communication system, which is an example of a wireless communication system, and a signal transmission / reception process using the channels;
[0034] Figure 7 illustrates a random access process that may be applied to implementation(s) of this specification;
[0035] FIG. 8 illustrates an example of PDSCH time domain resource allocation by PDCCH and an example of PUSCH time domain resource allocation by PDCCH;
[0036] Figure 9 illustrates the HARQ-ACK transmission / reception process;
[0037] FIG. 10 illustrates a discontinuous reception (DRX) operation that may be applied to implementation(s) of the present specification;
[0038] Figure 11 illustrates a case where a Long DRX cycle and a Short DRX cycle are set;
[0039] Figures 12 and 13 illustrate UE operating sections according to some implementations of the present specification;
[0040] FIG. 14 illustrates the flow of DL / UL signal reception / transmission in a UE according to some implementations of the present specification;
[0041] Figure 15 illustrates the flow of DL / UL signal transmission / reception in BS according to some implementations of the present specification.
[0042] 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.
[0043] 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.
[0044] 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.
[0045] 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.
[0046] 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.
[0047] 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."
[0048] 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.
[0049] 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.
[0050] 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.
[0051] 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.
[0052] 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.
[0053] 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).
[0054] 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.
[0055] 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.
[0056] In addition to the Pcell and PUCCH Scell, the UE can be configured with a PUCCH-sSCell, which is an Scell for PUCCH cell switching. For example, the UE can be provided with a PUCCH-sSCell by the RRC parameter pucch-sSCell. The UE can be provided with a periodic cell switching pattern for PUCCH transmissions by the RRC parameter pucch-sSCellPattern. Each bit of pucch-sSCellPattern corresponds to a slot according to a reference subcarrier spacing (SCS) configuration, and can designate a primary cell (PCell) or PUCCH-sSCell as a cell for PUCCH transmissions during the slot of the reference SCS configuration. The UE does not transmit a PUCCH on a cell among the PCell and the PUCCH-sSCell that is not designated as a cell for PUCCH transmission by the periodic cell switching pattern. When a UE is configured for PUCCH cell switching based on a dynamic indication by a DCI format, the corresponding DCI format associated with the generation of HARQ-ACK information by the UE may include a PUCCH cell indicator field indicating whether the PUCCH transmission with the HARQ-ACK information by the UE is on the PCell or the PUCCH-sSCell.
[0057] In this specification, the term "PUCCH cell" is used to refer to a cell in which PUCCH resources are configured. A PUCCH cell may be a PCell, a PUCCH Scell, or a PUCCH-sSCell.
[0058] 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.
[0059] 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.
[0060] 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.
[0061] 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.
[0062] 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.
[0063] 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.
[0064] 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.
[0065] 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).
[0066] 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.
[0067] 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.
[0068] 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.
[0069] 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.
[0070] 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.
[0071] 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 document. One or more processors (102, 202) may generate messages, control information, data or information according to the functions, procedures, proposals and / or methods disclosed herein. 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 herein 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 herein.
[0072] 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 document 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 document 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 document may be implemented using firmware or software in the form of codes, instructions and / or sets of instructions.
[0073] 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.
[0074] One or more transceivers (106, 206) can transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or flowcharts of this document, to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals / channels, etc., as mentioned in the functions, procedures, proposals, methods and / or flowcharts of this document, from one or more other devices. For example, one or more transceivers (106, 206) can be coupled to one or more processors (102, 202) and can transmit and / or receive wireless signals. For example, one or more processors (102, 202) can 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 document, via one or more antennas (108, 208). In this document, 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.
[0075] 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).
[0076] 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.
[0077] 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, and / or a combination thereof.
[0078] 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.
[0079] In this specification, a computer-readable (non-volatile) 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.
[0080] 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.
[0081] 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.
[0082] 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.
[0083] Figure 4 illustrates an example of a frame structure available in a 3GPP-based wireless communication system.
[0084] 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.
[0085] 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 / (△fmax *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,u slot ) and the number of slots per subframe (N subframe,u slot ) is shown.
[0086]
[0087] 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.
[0088]
[0089] 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}.
[0090] 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,x is 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 scis 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 CRB and 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,iis 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.
[0091] 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.
[0092] 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.
[0093] 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.
[0094]
[0095] Figure 6 illustrates physical channels used in a 3GPP-based communication system, which is an example of a wireless communication system, and a signal transmission / reception process using the channels.
[0096] When a UE is powered on again after being powered off or has been disconnected from a wireless communication system, it first searches for a suitable cell to camp on (search cell) and performs an initial cell search process, such as synchronizing with the cell or the BS of the cell (S11). During the initial cell search process, the UE receives a synchronization signal block (SSB) (also called an SSB / PBCH block) from the BS. The SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH). The UE synchronizes with the BS based on the PSS / SSS and obtains information such as a cell identity (ID). In addition, the UE can obtain broadcast information within the cell based on the PBCH. Meanwhile, the UE can check the downlink channel status by receiving a downlink reference signal (DL RS) during the initial cell search process.
[0097] A UE that has completed initial cell search can camp on the cell. After camping on the cell, the UE monitors the PDCCH on the cell and receives the PDSCH based on the downlink control information (DCI) carried by the PDCCH to obtain more specific system information (S12).
[0098] Thereafter, the UE may perform a random access procedure to complete access to the BS (S13 to S16). For example, in the random access procedure, the UE may transmit a preamble through a physical random access channel (PRACH) (S13) and receive a random access response (RAR) to the preamble through a PDCCH and a corresponding PDSCH (S14). If reception of the RAR for the UE fails, the UE may retry transmitting the preamble. In the case of contention-based random access, a contention resolution procedure (S16) may be performed, including transmission of a PUSCH based on UL resource allocation included in the RAR (S15) and reception of a PDCCH and a corresponding PDSCH.
[0099] The UE, which has performed the procedure described above, can then perform reception of PDCCH / PDSCH (S17) and transmission of PUSCH / PUCCH (S18) as a general uplink / downlink signal transmission process. The control information that the UE transmits to the BS is collectively referred to as uplink control information (UCI). UCI includes HARQ ACK / NACK (Hybrid Automatic Repeat and reQuest Acknowledgement / Negative-ACK) (also referred to as HARQ-ACK), scheduling request (SR), channel state information (CSI), etc. CSI may include a channel quality indicator (CQI), a precoding matrix indicator (PMI), and / or a rank indicator. UCI is generally transmitted through PUCCH, but may be transmitted through PUSCH when control information and traffic data must be transmitted simultaneously. Additionally, based on a request / instruction from the network, the UE can transmit UCI aperiodically via PUSCH.
[0100] Figure 7 illustrates a random access process that may be applied to implementation(s) of the present specification. In particular, Figure 7(a) illustrates a four-step random access process, and Figure 7(b) illustrates a two-step random access process.
[0101] The random access procedure can be used for various purposes, such as initial access, uplink synchronization adjustment, resource allocation, handover, reconfiguration of radio links after radio link failure, and position measurement. The random access procedure is classified into a contention-based procedure and a dedicated (i.e., non-contention-based) procedure. The contention-based random access procedure is commonly used, including initial access, while the dedicated random access procedure is used for handovers, when downlink data arrives at the network, and to reestablish uplink synchronization in the case of position measurement. In the contention-based random access procedure, the UE randomly selects a random access (RA) preamble. Therefore, multiple UEs can transmit the same RA preamble simultaneously, necessitating subsequent contention resolution. In contrast, in the dedicated random access procedure, the UE uses an RA preamble uniquely assigned to the UE by the BS. Therefore, the UE can perform the random access procedure without collisions with other UEs.
[0102] Referring to Fig. 7(a), the contention-based random access process includes the following four steps. Hereinafter, the messages transmitted in steps 1 through 4 may be referred to as Msg1 through Msg4, respectively.
[0103] - Step 1: The UE transmits an RA preamble via PRACH.
[0104] - Step 2: The UE receives a random access response (RAR) from the BS via PDSCH.
[0105] - Step 3: The UE transmits UL data to the BS via PUSCH based on the RAR. Here, the UL data includes layer 2 and / or layer 3 messages.
[0106] - Step 4: The UE receives a contention resolution message from the BS via PDSCH.
[0107] A UE can receive information about random access from a BS through system information. For example, information about RACH occasions associated with SSBs on a cell can be provided through the system information. The UE can select an SSB among the SSBs received on the cell whose reference signal received power (RSRP) measured based on the SSB exceeds a threshold, and transmit an RA preamble through a PRACH associated with the selected SSB. For example, if random access is required, the UE transmits Msg1 (e.g., preamble) to the BS on the PRACH. The BS can distinguish each random access preamble through the time / frequency resource (RA Occasion, RO) on which the random access preamble was transmitted and the random access preamble index (Preamble Index, PI). When the BS receives a random access preamble from the UE, the BS transmits a RAR message to the UE on the PDSCH. To receive a RAR message, the UE monitors an L1 / L2 control channel (PDCCH) CRC-masked with a Random Access-RNTI (RA-RNTI), which contains scheduling information for the RAR message, within a preset time window, i.e., an RAR window (e.g., ra-ResponseWindow). The length of the RAR window can be set by higher layer signaling, and the RAR window can start at a specific timing after a PRACH transmission (e.g., a first symbol of an earliest control resource set (CORESET) of a type-1 PDCCH common search space starting at least one symbol after a PRACH time corresponding to the PRACH transmission). When the UE receives scheduling information through a PDCCH masked with an RA-RNTI, the UE can receive the RAR message from a PDSCH indicated by the scheduling information.Afterwards, the UE determines whether the RAR message contains an RAR for itself. Whether an RAR for itself exists can be determined by checking whether a RAPID (Random Access Preamble ID) exists in the preamble transmitted by the UE. The index and RAPID of the preamble transmitted by the UE may be identical. The RAR includes a corresponding random access preamble index, timing offset information for UL synchronization (e.g., timing advance command (TAC), UL scheduling information for Msg3 transmission (e.g., UL grant), and UE temporary identification information (e.g., Temporary-C-RNTI, TC-RNTI). The UE receiving the RAR transmits Msg3 through the PUSCH according to the UL scheduling information and timing offset value in the RAR. Msg3 may include the ID of the UE (or the global ID of the UE). In addition, Msg3 may include information related to an RRC connection request for initial access to the network (e.g., an RRCSetupRequest message). After receiving Msg3, the BS transmits Msg4, which is a contention resolution message, to the UE. If the UE receives the contention resolution message and the contention is successfully resolved, the TC-RNTI is changed to the C-RNTI. Msg4 includes the ID of the UE. And / or RRC connection related information (e.g., RRCSetup message) may be included. If the information transmitted via Msg3 does not match the information received via Msg4, or if Msg4 is not received for a certain period of time, the UE may consider contention resolution to have failed and retransmit Msg3.
[0108] Meanwhile, the dedicated random access process includes the following three steps. Hereinafter, the messages transmitted in steps 0 to 2 may be referred to as Msg0 to Msg2, respectively. The dedicated random access process may be triggered in the UE by the BS using a PDCCH (hereinafter, PDCCH order) for commanding the transmission of an RA preamble.
[0109] - Step 0: BS allocates RA preamble to UE through dedicated signaling.
[0110] - Step 1: The UE transmits an RA preamble via PRACH.
[0111] - Step 2: The UE receives RAR via PDSCH from the BS.
[0112] The operation of steps 1 and 2 of the dedicated random access process may be identical to steps 1 and 2 of the contention-based random access process.
[0113] NR systems may require lower latency than traditional systems. Furthermore, a four-step random access process may not be desirable, especially for latency-sensitive services such as URLLC. A low-latency random access process may be required in various scenarios in NR systems. When implementing implementations of this specification in conjunction with a random access process, implementations of this specification may be implemented in conjunction with the following two-step random access process to reduce the latency of the random access process.
[0114] Referring to Fig. 7(b), the two-step random access process may be composed of two steps: transmission of MsgA from a UE to a BS and transmission of MsgB from the BS to the UE. The MsgA transmission may include transmission of an RA preamble via a PRACH and transmission of an UL payload via a PUSCH. In the MsgA transmission, the PRACH and PUSCH may be transmitted using time division multiplexing (TDM). Alternatively, in the MsgA transmission, the PRACH and PUSCH may be transmitted using frequency division multiplexing (FDM).
[0115] A BS that receives MsgA may transmit MsgB to the UE. MsgB may include an RAR for the UE. After transmitting MsgA, the UE monitors a response from the network within a time window for monitoring the RAR for a two-step random access procedure. The length of the time window may be set by higher layer signaling, and the time window may start at a specific timing after the MsgA transmission (e.g., the first symbol of the earliest CORESET of the Type-1 PDCCH common search space that starts at least one symbol after the last symbol of the PUCCH epoch corresponding to the PRACH transmission of the MsgA transmission).
[0116] An RRC connection request related message (e.g., an RRCSetupRequest message) requesting to establish a connection between the RRC layer of the BS and the RRC layer of the UE may be transmitted in the payload of MsgA. In this case, MsgB may be used to transmit RRC connection related information (e.g., an RRCSetup message). Alternatively, the RRC connection request related message (e.g., an RRCSetupRequest message) may be transmitted via a PUSCH transmitted based on a UL grant in MsgB. In this case, the RRC connection related information (e.g., an RRCSetup message) related to the RRC connection request may be transmitted via a PDSCH associated with the PUSCH transmission after the PUSCH transmission based on MsgB.
[0117] Below, the physical channels that can be used in 3GPP-based wireless communication systems are described in more detail.
[0118] 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).
[0119] 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.
[0120] 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.
[0121] 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.
[0122] 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.
[0123] 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.
[0124] In this specification, a PDSCH based on DL SPS is referred to as an SPS PDSCH, a PUSCH based on UL CG is referred to as a CG PUSCH, a PDSCH dynamically scheduled by DCI carried by a PDCCH is referred to as a DG PDSCH, and a PUSCH dynamically scheduled by DCI carried by a PDCCH is referred to as a DG PUSCH.
[0125] Figure 8 illustrates an example of PDSCH time domain resource allocation by PDCCH and an example of PUSCH time domain resource allocation by PDCCH.
[0126] The DCI carried by the PDCCH for scheduling the PDSCH or PUSCH includes a time domain resource assignment (TDRA) field, which provides a value m for a row index m+1 of an allocation table for the PDSCH or PUSCH. A predefined default PDSCH time domain allocation is applied as the allocation table for the PDSCH, or a PDSCH time domain resource allocation table configured by the BS through RRC signaling pdsch-TimeDomainAllocationList is applied as the allocation table for the PDSCH. A predefined default PUSCH time domain allocation is applied as the allocation table for the PUSCH, or a PUSCH time domain resource allocation table configured by the BS through RRC signaling pushch-TimeDomainAllocationList is applied as the allocation table for the PUSCH. The PDSCH time domain resource allocation table to be applied and / or the PUSCH time domain resource allocation table to be applied may be determined according to fixed / predefined rules (e.g., see 3GPP TS 38.214).
[0127] In the PDSCH time domain resource configurations, each indexed row defines a DL allocation-to-PDSCH slot offset K0, a start and length indicator value SLIV (or directly a starting position (e.g., a starting symbol index S) and an allocation length (e.g., a number of symbols L) of a PDSCH within a slot), and a PDSCH mapping type. In the PUSCH time domain resource configurations, each indexed row defines a UL grant-to-PUSCH slot offset K2, a starting position (e.g., a starting symbol index S) and an allocation length (e.g., a number of symbols L) of a PUSCH within a slot, and a PUSCH mapping type. K0 for PDSCH or K2 for PUSCH indicates the difference between a slot with a PDCCH and a slot with a PDSCH or PUSCH corresponding to the PDCCH. SLIV is a joint indication of a starting symbol S relative to the start of a slot with a PDSCH or PUSCH and the number L of consecutive symbols counted from the symbol S. For PDSCH / PUSCH mapping type, there are two mapping types: one is mapping type A and the other is mapping type B. For PDSCH / PUSCH mapping type A, a demodulation reference signal (DMRS) is mapped to a PDSCH / PUSCH resource at the beginning of a slot, and one or two symbols of the PDSCH / PUSCH resource can be used as DMRS symbol(s) depending on other DMRS parameters. For example, for PDSCH / PUSCH mapping type A, the DMRS is located at the third symbol (symbol #2) or the fourth symbol (symbol #3) in a slot depending on RRC signaling. For PDSCH / PUSCH mapping type B, the DMRS is mapped based on the first OFDM symbol of the PDSCH / PUSCH resource, and one or two symbols from the first symbol of the PDSCH / PUSCH resource can be used as DMRS symbol(s) depending on other DMRS parameters.For example, in the case of PDSCH / PUSCH mapping type B, DMRS is located in the first symbol allocated for PDSCH / PUSCH. In this specification, PDSCH / PUSCH mapping type may be referred to as mapping type or DMRS mapping type. For example, in this specification, PUSCH mapping type A may be referred to as mapping type A or DMRS mapping type A, and PUSCH mapping type B may be referred to as mapping type B or DMRS mapping type B.
[0128] The above scheduling DCI includes a frequency domain resource assignment (FDRA) field that provides allocation information regarding resource blocks used for PDSCH or PUSCH. For example, the FDRA field provides the UE with information regarding the cell for PDSCH or PUSCH transmission, information regarding the BWP for PDSCH or PUSCH transmission, and information regarding resource blocks for PDSCH or PUSCH transmission.
[0129] PUCCH refers to a physical layer UL channel for UCI transmission. PUCCH carries UCI (Uplink Control Information). The types of UCI transmitted on PUCCH include hybrid automatic repeat request (HARQ)-acknowledgement (ACK) information, scheduling request (SR), and channel state information (CSI). UCI bits include HARQ-ACK information bits, SR information bits, LRR information bits, and CSI bits, if any. In this specification, the HARQ-ACK information bits correspond to a HARQ-ACK codebook. In particular, a bit sequence in which HARQ-ACK information bits are listed according to a predetermined rule is called a HARQ-ACK codebook.
[0130] PUCCH resources can be determined by UCI type (e.g., A / N, SR, CSI). PUCCH resources used for UCI transmission can be determined based on the UCI (payload) size. For example, the BS configures multiple PUCCH resource sets for the UE, and the UE can select a specific PUCCH resource set corresponding to a specific range based on the range of the UCI (payload) size (e.g., the number of UCI bits).
[0131] The configuration for each PUCCH resource may include a PUCCH resource index, an index of a starting PRB, and a configuration for one of PUCCH formats 0 to 4. A code rate for multiplexing HARQ-ACK, SR, and CSI report(s) within a PUCCH transmission using PUCCH format 2, PUCCH format 3, or PUCCH format 4 is configured by the BS to the UE via a higher layer parameter maxCodeRate. The higher layer parameter maxCodeRate is used to determine how to feed back UCI on the PUCCH resource for PUCCH format 2, 3, or 4.
[0132] When the UCI type is SR or CSI, the PUCCH resources to be used for UCI transmission within the PUCCH resource set can be configured to the UE by the network via higher layer signaling (e.g., RRC signaling). When the UCI type is HARQ-ACK for SPS (Semi-Persistent Scheduling) PDSCH, the PUCCH resources to be used for UCI transmission within the PUCCH resource set can be configured to the UE by the network via higher layer signaling (e.g., RRC signaling). On the other hand, when the UCI type is HARQ-ACK for PDSCH scheduled by DCI, the PUCCH resources to be used for UCI transmission within the PUCCH resource set can be scheduled based on the DCI.
[0133] In case of DCI-based PUCCH resource scheduling, the BS transmits DCI to the UE via PDCCH, and can indicate PUCCH resources to be used for UCI transmission within a specific PUCCH resource set via an ACK / NACK resource indicator (ARI) in the DCI. The ARI is used to indicate PUCCH resources for ACK / NACK transmission and may also be referred to as a PUCCH resource indicator (PRI). Here, the DCI is a DCI used for PDSCH scheduling, and the UCI may include HARQ-ACK for the PDSCH. Meanwhile, the BS can configure a PUCCH resource set consisting of more PUCCH resources than the number of states that the ARI can express, to the UE, using (UE-specific) higher layer (e.g., RRC) signaling. At this time, the ARI indicates a PUCCH resource subset within the PUCCH resource set, and which PUCCH resource to use within the indicated PUCCH resource subset can be determined according to an implicit rule based on transmission resource information for the PDCCH (e.g., a start control channel element (CCE) index of the PDCCH, etc.).
[0134] Figure 9 illustrates the HARQ-ACK transmission / reception process.
[0135] Referring to FIG. 9, the UE can detect a PDCCH in slot n. Thereafter, the UE can receive a PDSCH in slot n+K0 based on scheduling information received via the PDCCH in slot n, and then transmit a UCI via a PUCCH in slot n+K1. Here, the UCI includes a HARQ-ACK response to the PDSCH.
[0136] DCI (e.g., DCI format 1_0, DCI format 1_1) carried by the PDCCH scheduling the PDSCH may include the following information:
[0137] - Frequency domain resource assignment (FDRA): Indicates the set of RBs allocated to the PDSCH.
[0138] - Time domain resource assignment (TDRA): Indicates the DL assignment-to-PDSCH slot offset K0, the starting position (e.g., symbol index S) and length (e.g., number of symbols L) of the PDSCH within the slot, and the PDSCH mapping type. PDSCH mapping type A or PDSCH mapping type B can be indicated by the TDRA. For PDSCH mapping type A, the DMRS is located in the third symbol (symbol #2) or the fourth symbol (symbol #3) in the slot. For PDSCH mapping type B, the DMRS is located in the first symbol allocated for the PDSCH.
[0139] - PDSCH-to-HARQ_Feedback Timing Indicator: Indicates K1.
[0140] When the PDSCH is configured to transmit at most 1 TB, the HARQ-ACK response may consist of 1 bit. When the PDSCH is configured to transmit at most 2 transport blocks (TB), the HARQ-ACK response may consist of 2 bits when spatial bundling is not configured, and may consist of 1 bit when spatial bundling is configured. When the HARQ-ACK transmission time for multiple PDSCHs is designated as slot n+K1, the UCI transmitted in slot n+K1 includes HARQ-ACK responses for multiple PDSCHs.
[0141] In this specification, a HARQ-ACK payload consisting of HARQ-ACK bit(s) for one or more PDSCHs may be referred to as a HARQ-ACK codebook. Depending on how the HARQ-ACK payload is determined, the HARQ-ACK codebook may be distinguished into i) a semi-static HARQ-ACK codebook, ii) a dynamic HARQ-ACK codebook, and iii) a HARQ process-based HARQ-ACK codebook.
[0142] In the case of a semi-static HARQ-ACK codebook, parameters related to the HARQ-ACK payload size to be reported by the UE are semi-statically set by (UE-specific) higher layer (e.g., RRC) signaling. For example, the HARQ-ACK payload size of the semi-static HARQ-ACK codebook may be determined based on the number of HARQ-ACK bits corresponding to a combination (hereinafter, bundling window) of all DL carriers (i.e., DL serving cells) configured for the UE and all DL scheduling slots (or PDSCH transmission slots or PDCCH monitoring slots) in which the HARQ-ACK transmission timing can be indicated, whereby the size of the HARQ-ACK codebook is fixed (to a maximum value) regardless of the number of actually scheduled DL data. For example, DL grant DCI (PDCCH) includes PDSCH to HARQ-ACK timing information, and the PDSCH-to-HARQ-ACK timing information may have one of a plurality of values (e.g., k). For example, if a PDSCH is received in slot #m and the PDSCH to HARQ-ACK timing information in the DL grant DCI (PDCCH) scheduling the PDSCH indicates k, HARQ-ACK information for the PDSCH may be transmitted in slot #(m+k). For example, k ∈ {1, 2, 3, 4, 5, 6, 7, 8} may be given. Meanwhile, if HARQ-ACK information is transmitted in slot #n, the HARQ-ACK information may include the maximum possible HARQ-ACK based on the bundling window. That is, the HARQ-ACK information of slot #n may include the HARQ-ACK corresponding to slot #(nk).For example, if k ∈ {1, 2, 3, 4, 5, 6, 7, 8}, the HARQ-ACK information of slot #n includes HARQ-ACKs corresponding to slot #(n-8) to slot #(n-1) (i.e., the maximum number of HARQ-ACKs) regardless of actual DL data reception. Here, the HARQ-ACK information can be replaced with the HARQ-ACK codebook and HARQ-ACK payload. In addition, the slot can be understood / replaced as a candidate occasion for DL data reception. As an example, the bundling window is determined based on the PDSCH-to-HARQ-ACK timing with respect to the HARQ-ACK slot, and the PDSCH-to-HARQ-ACK timing set can have a predefined value (e.g., {1, 2, 3, 4, 5, 6, 7, 8}) or can be set by higher layer (RRC) signaling. Semi-static HARQ-ACK codebooks are also referred to as Type-1 HARQ-ACK codebooks. In Type-1 HARQ-ACK codebooks, the number of bits to be sent in a HARQ-ACK report is fixed and can be large. When many cells are configured but only a small number are scheduled, Type-1 HARQ-ACK codebooks can be inefficient.
[0143] Meanwhile, in the case of a dynamic HARQ-ACK codebook, the HARQ-ACK payload size to be reported by the UE can be dynamically changed by DCI, etc. The dynamic HARQ-ACK codebook is also referred to as a Type-2 HARQ-ACK codebook. The Type-2 HARQ-ACK codebook can be considered a more optimized HARQ-ACK feedback because the UE sends feedback only for the scheduled serving cells. However, in bad channel conditions, the UE may misunderstand the number of scheduled serving cells, and to address this, the DAI is included as part of the DCI. For example, in the dynamic HARQ-ACK codebook scheme, the DL scheduling DCI may include a counter-DAI (i.e., c-DAI) and / or a total-DAI (i.e., t-DAI). Here, the DAI stands for a downlink assignment index, and is used by the BS to inform the UE of the transmitted or scheduled PDSCH(s) to be included in one HARQ-ACK transmission. In particular, c-DAI is an index indicating the order among PDCCHs carrying DL scheduling DCI (hereinafter, DL scheduling PDCCHs), and t-DAI is an index indicating the total number of DL scheduling PDCCHs up to the current slot in which there is a PDCCH having t-DAI.
[0144] Meanwhile, in the case of a HARQ process-based HARQ-ACK codebook, the HARQ-ACK payload is determined based on all HARQ processes of all serving cells configured (or activated) within a PUCCH group. For example, the HARQ-ACK payload size that a UE will report through a HARQ process-based HARQ-ACK codebook is determined by the number of all serving cells configured or activated within a PUCCH group configured for the UE and the number of HARQ processes for the serving cells. A HARQ process-based HARQ-ACK codebook is also referred to as a Type-3 HARQ-ACK codebook. A Type-3 HARQ-ACK codebook can be applied to one-shot feedback.
[0145] 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.
[0146] 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.
[0147] 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.
[0148] 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.
[0149] UE discontinuous reception (DRX)
[0150] 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.
[0151] Figure 10 illustrates a discontinuous reception (DRX) operation. In particular, Figure 10 illustrates a DRX cycle for a UE in RRC_CONNECTED state.
[0152] Referring to FIG. 10, a DRX cycle consists of an ON duration and an Opportunity for DRX. A DRX cycle defines a time interval during which an ON duration is periodically repeated, followed by a possible period of inactivity. The ON duration 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 duration. 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 duration 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. 10.
[0153] 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. 10.
[0154]
[0155] 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.
[0156] - Value of drx-onDurationTimer: Sets the duration at the start of the DRX cycle.
[0157] - Value of drx-SlotOffset: Sets the delay before starting drx-onDurationTimer.
[0158] - Value of drx-InactivityTimer: Sets the period after which a PDCCH epoch indicates a new UL or DL transmission for the MAC entity.
[0159] - Value of drxRetransmissionTimerDL (per DL HARQ process except for the broadcast process): Sets the maximum duration until a DL retransmission is received.
[0160] - Value of drxRetransmissionTimerUL (per UL HARQ process): Sets the maximum duration until a grant for UL retransmission is received.
[0161] - 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.
[0162] - 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.
[0163] - drx-LongCycleStartOffset: Sets the Long DRX cycle and drx-StartOffset, which defines the subframe where the Long and Short DRX cycles start.
[0164] - drx-ShortCycle (optional): Sets the short DRX cycle.
[0165] - 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.
[0166] 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.
[0167] 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.
[0168] The UE monitors the 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 given by 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 utilization can be improved by allocating the resource (i.e., the resource for P-CSI or SRS transmission) to another UE.Additionally, the BS may also operate in energy saving mode to save power during the UE's OFF period.
[0169] Figure 11 illustrates a case where a Long DRX cycle and a Short DRX cycle are set. In particular, Figure 11 illustrates a case where drx-ShortCycleTimer is set to 2.
[0170] 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. 11, 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.
[0171] 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 to enter the DRX cycle directly. If only the 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 the Long DRX cycle and the Short DRX cycle are configured, the UE may enter the Short DRX cycle directly after receiving the DRX command MAC CE. In addition, if the BS provides the Long DRX command MAC CE, the UE may operate in the Long DRX cycle even if the Short DRX cycle is configured.
[0172] 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.
[0173] 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.
[0174] Network energy saving and cell DRX / DTX
[0175] 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.
[0176] 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.
[0177] 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).
[0178] Accordingly, in some implementations of the present specification, the BS can save energy by turning OFF transmission / reception of specific signals / channels in inactive periods through cell-specific DTX / DRX configuration in which active and inactive periods repeat similarly to UE C-DRX. However, in this case, when a specific cell (e.g., a PCell transmitting a PUCCH) enters the inactive period due to the cell DTX / DRX configuration, the transmission / reception behavior of other cell(s) (e.g., SCell) connected to the cell via CA (or DC) may be different from when there is no cell DTX / DRX configuration. Hereinafter, some implementations of the present specification regarding the transmission / reception behavior on other cell(s) associated with a specific cell when the specific cell performs the cell DTX / DRX operation (i.e., when the BS performs the cell DTX / DRX operation for the specific cell) are described.
[0179] 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.
[0180] To reduce the BS downlink transmission / uplink reception active time, the UE can be configured with periodic cell DTX / DRX patterns (i.e., active and non-active periods). The pattern configuration for cell DTX / DRX can be common to UEs within 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).
[0181] 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.
[0182] Cell DTX operation affects 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 activated, the 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 the serving cell may include the time that the cell DTX / DRX ON duration timer runs for the serving cell. For example, for a serving cell for which cell DTX is configured and activated, the 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, regardless of whether it is the active period of UE C-DRX, 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.
[0183] Cell DRX operation controls SR and configured uplink grant transmission activities 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.
[0184] <Implementation #1> When cell DTX / DRX is set and operated (e.g., activated) in a cell unit or a set of cells, and cell DTX / DRX is set in a PUCCH cell and the PUCCH cell enters an inactive period, a transmission / reception operation method of other cells (e.g., SCell)(s) associated with the PUCCH cell (wherein the PUCCH cell may be i) a PCell in a CA situation, or ii) a PSCell in a DC situation, or iii) a PUCCH-SCell in a CA situation, or iv) a PUCCH cell switching (an SCell on which a PUCCH can be transmitted other than a PCell or PSCell in a switching situation)
[0185] (1) When the PUCCH cell enters the cell DTX / DRX inactive period,
[0186] - (1)-A. A method of not performing PDSCH reception and corresponding PDCCH monitoring for the remaining cell(s) belonging to the same PUCCH group as the PUCCH cell (regardless of whether cell DTX / DRX settings are present for the remaining cell(s))
[0187] - (1)-B. Or, a method of performing PDCCH monitoring and PDSCH reception as is but not transmitting PUCCH (i.e., disabling or dropping HARQ-ACK PUCCH transmission)
[0188] - (1)-C. Or, a method of postponing PUCCH transmission or performing PUCCH transmission in another PUCCH cell in the active section, but additionally attaching it to the HARQ-ACK codebook configured for the PUCCH (by creating a new codebook) as a sub-codebook and transmitting it (depending on the capability of the UE, there may be UEs that can apply this method and UEs that cannot).
[0189] (2) When a scheduling cell in charge of scheduling enters a cell DTX / DRX inactive period, a method of not performing PDCCH monitoring on the scheduling cell for all scheduled cells that can be scheduled from the scheduling cell (regardless of whether cell DTX / DRX is set for the corresponding scheduled cell(s))
[0190] (3) When the cell DTX / DRX of a PCell or PUCCH cell is set and operated, the same cell DTX / DRX setting (e.g., active / inactive pattern) is applied to the remaining cell(s) belonging to the same PUCCH group or cell group as the corresponding cell.
[0191] BS can set and operate cell DTX / DRX on a cell-by-cell or cell-group basis to save energy. As described above, cell DTX setting and cell DRX setting can be set and operated separately, and parameters such as periodicity, start slot / offset, and ON period are set in cell DTX / DRX setting similarly to UE C-DRX, so that active time intervals and inactive time intervals can be periodically repeated in the cell(s) where the cell DTX / DRX is set. At this time, general BS transmission / reception can all be possible during the active time interval, and during the inactive time interval, transmission / reception of a specific signal / channel may be turned OFF or all DL / UL transmission / reception may be turned OFF depending on the cell DTX / DRX setting. For example, based on the cell DTX configuration, the BS may not perform scheduling via UE-specific dynamic grants / assignments in the inactive period, and the UE may not perform PDCCH monitoring for dynamic grants / assignments. When such cell DTX / DRX is configured and operated in a specific cell, it may affect not only the transmission / reception operation of the specific cell and the UE, but also the transmission / reception of other cell(s) (e.g., SCell) that are correlated with the specific cell through CA or DC, etc., and the UEs belonging to the other cell(s).
[0192] In the case of CA, there may be a PCell that can handle initial access, PUCCH transmission, and scheduling to other cells, and one or more SCells configured with the PCell as CA. Scheduling here can be divided into self-carrier scheduling and cross-carrier scheduling. As explained above, self-carrier scheduling means that the scheduling cell and scheduled cell are the same, while cross-carrier scheduling means that the scheduling cell and scheduled cell are different. Since self-carrier scheduling is the default in a CA environment unless otherwise configured, even an SCell schedules itself by default. In the case of cross-carrier scheduling, the scheduling cell may be either a PCell or an SCell. That is, in the case of cross-carrier scheduling, a PCell can schedule another SCell, or an SCell can schedule another SCell. Therefore, in some implementations of this specification, the scheduling cell and the scheduled cell may not necessarily mean the PCell and the SCell, respectively, and literally, the scheduling cell and the scheduled cell may mean the cell in charge of scheduling and the cell to be scheduled, respectively, in a cross-carrier scheduling situation. In addition, in the case of DC, the cell group to which the UE initially accessed belongs is the MCG, and the other cell group connected to the DC is the SCG. Within each MCG and SCG, there may exist a PSCell in charge of scheduling PUCCH and other cell(s) within the cell group, and one or more SCells connected to the PSCell via CA.
[0193] When cell DTX / DRX is set and operated per cell or per set of cells, and cell DTX / DRX is set for a PUCCH cell and the PUCCH cell enters an inactive period, the transmission / reception operation method of other cell(s) (e.g., SCell)(s) associated with the PUCCH cell in the inactive period of the PUCCH cell needs to be considered. This is because when the PUCCH cell is in the inactive period, the PUCCH for other cells set to perform PUCCH transmission in the PUCCH cell cannot be transmitted on the PUCCH cell in the inactive period. In the present specification, the PUCCH cell may mean one of i) PCell in a CA situation, or ii) PSCell in a DC situation, or iii) PUCCH SCell in a CA situation, or 4) PUCCH-sSCell which is an SCell on which a PUCCH other than the PCell or PSCell can be transmitted in a PUCCH cell switching situation. Hereinafter, PCell, PSCell, PUCCH SCell, and PUCCH-sSCell are collectively referred to as PUCCH cells for convenience.
[0194] Figures 12 and 13 illustrate UE operating periods according to some implementations of the present specification. In the example of Figure 12, it is assumed that cell DRX is configured for cell A, which is a PUCCH cell, and cell DRX is not configured for cell B, which uses cell A for PUCCH transmissions, so that cell B is active in all of its cell DRX active / inactive periods. In the example of Figure 13, it is assumed that cell DRX is configured for each of cell A, which is a PUCCH cell, and cell B, which uses cell A for PUCCH transmissions.
[0195] In some implementations of the present specification, when a PUCCH cell enters a cell DTX / DRX inactive period (e.g., when cell DRX is configured for a PUCCH cell and the PUCCH cell enters a cell DRX period), a method may be considered in which the UE does not perform PDSCH reception and corresponding PDCCH monitoring for the remaining cell(s) belonging to the same PUCCH group as the PUCCH cell. PDSCH reception and corresponding PDCCH monitoring may also be restricted for the PUCCH cell. This method may be applied regardless of whether cell DTX / DRX is configured for the remaining cell(s). Referring to FIGS. 12 and 13 , even when cell B is in an active period, if cell A is in a cell DRX inactive period, the UE may not perform PDSCH reception and PDCCH monitoring for cell B, and may perform PDCCH monitoring and PDSCH reception for cell B within a period in which the active period of cell B and the DRX active period of cell A overlap. The UE may not perform PDCCH monitoring and PDSCH reception for the cell B within a period in which the active period of the cell B and the DRX active period of the cell A do not overlap, and the BS may perform PDCCH transmission and / or PDSCH scheduling for the cell B in consideration of this. A restriction on PDCCH monitoring for the cell B may be applied on a scheduling cell for the cell B, and a restriction on reception of a PDSCH scheduled for the cell B may be applied on the cell B. For example, if there is a cell C which is a scheduling cell for the cell B and HARQ-ACK feedback for a PDSCH scheduled for the cell B by the scheduling cell must be transmitted from the cell A, PDCCH monitoring and PDSCH reception may be performed on the cell C within a period in which the active period of the cell B and the DRX active period of the cell A overlap.If a PUCCH cell enters an inactive period due to cell DTX / DRX configuration (in particular, a DRX inactive period in which the BS turns off reception on the cell), even if the UE transmits a PUCCH on the PUCCH cell, the BS may not receive it, or the PUCCH transmission itself may be set to OFF in the inactive period. In addition, if the PUCCH cell is unable to perform PUCCH transmission due to the cell DTX / DRX inactive period (i.e., if the PUCCH cell cannot carry the PUCCH), even if the UE receives a PDSCH on cells included in a PUCCH group including the PUCCH cell or receives a PDCCH that schedules a PDSCH in a cell of the PUCCH group, the PDSCH or the PUCCH (carrying HARQ-ACK information) related to the PDCCH may not be transmitted, or the BS may not receive the PUCCH. Therefore, when a PUCCH cell enters a cell DTX / DRX inactive period (especially, a cell DRX inactive period), it may be efficient in terms of energy saving of the remaining cell(s) belonging to the PUCCH group and the UEs belonging to the remaining cell(s) for the UE not to perform PDSCH reception and corresponding PDCCH monitoring for other cells associated with the PUCCH cell.
[0196] Alternatively, in some implementations of the present specification, if a PUCCH cell enters a cell DTX / DRX inactive period (e.g., cell DRX is configured for a PUCCH cell and the PUCCH cell enters a cell DRX period), the UE may continue to monitor PDCCH and receive PDSCH for the remaining cell(s) belonging to the same PUCCH group as the PUCCH cell, but may not transmit PUCCH. This may mean that HARQ-ACK PUCCH transmission is disabled or dropped.
[0197] Alternatively, the UE may postpone the PUCCH transmission, or perform the PUCCH transmission on another PUCCH cell in the active period, but may attach (create a new) the HARQ-ACK information bit(s) that cannot be transmitted on the PUCCH cell due to the PUCCH cell being in the inactive period to the HARQ-ACK codebook configured on the PUCCH (i.e., the HARQ-ACK codebook originally scheduled / triggered to be transmitted on the PUCCH of the other PUCCH cell) as a sub-codebook and transmit the same. Here, postponing the PUCCH transmission means that the original timing at which the PUCCH should be transmitted falls within the inactive period or overlaps therewith, and thus the PUCCH is postponed and not transmitted at the original timing. In addition, when a UE transmits a PUCCH on a PUCCH cell other than the original PUCCH cell on which the PUCCH transmission should have been performed, this may mean that the HARQ-ACK codebook that could not be transmitted due to the cell DTX / DRX inactivity period is added in the form of a sub-codebook and transmitted together with the original HARQ-ACK codebook configured on the other PUCCH cell (i.e., the HARQ-ACK codebook whose first transmission timing is scheduled on the other PUCCH). However, this method may be supported or applicable to some UEs and not to some UEs, depending on the capabilities of the UE.
[0198] Meanwhile, in the case of cross-carrier scheduling in a CA situation, there may be a scheduling cell (e.g., PCell or PSCell) in charge of scheduling and a scheduled cell (e.g., SCell) that receives scheduling. If a scheduling cell enters a cell DTX / DRX inactive period, PDCCH monitoring may not be performed for all scheduled cells that receive scheduling from the scheduling cell, regardless of whether cell DTX / DRX is configured for the corresponding scheduled cell(s).
[0199] In some implementations of this specification, when cell DTX / DRX is configured and operated on a PCell or PUCCH cell, the BS and UE may also apply the same cell DTX / DRX configuration to the remaining cell(s) belonging to the same PUCCH group or cell group as the corresponding cell. In this case, the ES gain can be maximized by having cells belonging to the same PUCCH group or cell group operate with the same active / inactive time interval pattern.
[0200] <Implementation #2> A method for setting a RAR window when the cell DTX (or DRX) setting for a cell where a RACH process (i.e., a random access process) can occur is activated and a specific signal / channel ON / OFF pattern is periodically repeated on the cell.
[0201] When the cell DTX / DRX setting is activated, the BS repeats the active and inactive periods previously configured. If PDCCH transmission is set to OFF in the DTX inactive period, the BS does not transmit the PDCCH during the DTX inactive period, and the UE does not expect to receive the PDCCH. However, if the UE transmits the RACH in the active period, and the RAR window for the RACH partially or completely overlaps with the inactive period of the BS, the UE cannot receive the RAR, and thus the procedure when the RAR is not received may be performed as defined in the standard.
[0202] In this case, since the BS normally received the RACH but was unable to transmit the RAR due to the inactive period according to the cell DTX / DRX configuration, it may not be desirable for the UE or the BS to unnecessarily perform the procedure that should be performed when the UE did not actually receive the RAR, in terms of energy saving and delay. Therefore, in some implementations of the present specification, the RAR window that partially or completely overlaps the cell DTX inactive period may be temporarily extended to include the next active period. This provides the BS with an opportunity to transmit the RAR when the BS normally receives the RACH, and allows the UE to continue the remaining RACH procedure without receiving the RAR. In some implementations, the extension of the RAR window may be performed by adding a preset / promised length to the basic RAR basic length, or may be extended by the basic RAR window length from the start of the next active period (i.e., the RAR window of the basic RAR window length may be restarted from the start of the next active period).
[0203] The above-described implementations #1 and #2 can be applied alone or in combination of two or more.
[0204] When cell DTX / DRX is set and activated on a cell or cell group basis and the related PUCCH / scheduling cell enters the cell DTX / DRX inactive period, the BS and the UE can maximize the ES gain by performing transmission / reception operations on other cell(s) (e.g., SCell(s)) associated with the PUCCH / scheduling cell according to some implementations of the present specification.
[0205] Figure 14 illustrates the flow of DL / UL signal reception / transmission in a UE according to some implementations of the present specification.
[0206] A UE may perform operations according to some implementations of the present disclosure in connection with DL / UL signal reception / transmission. 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) 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) 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.
[0207] 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 cell DRX configuration for a first cell for which PUCCH resources are configured (S1401); determining an active period in which uplink transmissions of the first cell are not restricted and a non-active period in which uplink transmissions of the first cell are restricted based on the cell DRX configuration for the first cell; and performing PDCCH monitoring for a second cell (e.g., a cell belonging to the same PUCCH or cell group as the first cell) that uses the first cell for PUCCH transmissions based on the first cell being within the active period (S1403).
[0208] In some implementations, the method, or the operations, may include: performing scheduled PDSCH reception on the second cell based on the first cell being within the active period.
[0209] In some implementations, the method, or the operations, may include: not performing PDCCH monitoring for the second cell based on the first cell being within the inactive period.
[0210] In some implementations, the method, or the operations, may include: not performing scheduled PDSCH reception on the second cell based on the first cell being within the inactive period.
[0211] In some implementations, PDCCH monitoring for the second cell may not be performed within the non-active period of the first cell, regardless of whether there is a cell DRX configuration for the second cell.
[0212] In some implementations, the method, or the operations, may include: postponing a first PUCCH transmission scheduled within the non-active interval of the first cell to after the non-active interval.
[0213] In some implementations, postponing the first PUCCH transmission to the non-active interval may include: transmitting the HARQ-ACK codebook in the first PUCCH transmission in addition to another HARQ-ACK codebook scheduled after the non-active interval of the first cell.
[0214] Figure 15 illustrates the flow of DL / UL signal transmission / reception in BS according to some implementations of the present specification.
[0215] A BS may perform operations according to some implementations of the present disclosure in connection with DL / UL signal transmission / reception. 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) 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) 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.
[0216] 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 a cell DRX configuration for a first cell for which PUCCH resources are configured (S1501); determining an active period in which uplink transmissions of the first cell are not restricted and a non-active period in which uplink transmissions of the first cell are restricted based on the cell DRX configuration for the first cell; and performing a PDCCH transmission for a second cell (e.g., a cell belonging to the same PUCCH or cell group as the first cell) that uses the first cell for PUCCH receptions based on the first cell being within the active period (S1503).
[0217] In some implementations, the method, or the operations, may include: performing a scheduled PDSCH transmission to the second cell based on the first cell being within the active period.
[0218] In some implementations, the method, or the operations, may include: not performing a PDCCH transmission to the second cell based on the first cell being within the inactive period.
[0219] In some implementations, the method, or the operations, may include: not performing a scheduled PDSCH transmission to the second cell based on the first cell being within the inactive period.
[0220] In some implementations, the PDCCH transmission for the second cell may not be performed within the non-active period of the first cell, regardless of whether there is a cell DRX configuration for the second cell.
[0221] In some implementations, the method, or the operations, may include: postponing reception of a first PUCCH scheduled within the non-active interval of the first cell to after the non-active interval.
[0222] In some implementations, postponing the first PUCCH reception to the non-active interval may include: receiving HARQ-ACK information in which the HARQ-ACK codebook within the first PUCCH reception is appended to another HARQ-ACK codebook scheduled after the non-active interval of the first cell.
[0223] 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.
[0224] Implementations of this specification can be used in wireless communication systems, BSs, user equipment, and other equipment.
Claims
1. When a user device receives a downlink signal in a wireless communication system, Receive cell discontinuous reception (DRX) settings for a first cell for which physical uplink control channel (PUCCH) resources are configured; Based on the cell DRX setting for the first cell, determining an active period in which uplink transmissions of the first cell are not restricted and a non-active period in which uplink transmissions of the first cell are restricted; and Comprising: performing physical downlink control channel (PDCCH) monitoring for a second cell that uses the first cell for PUCCH transmissions based on the first cell being within the active period; Method for receiving downlink signals.
2. In paragraph 1, Including performing reception of a physical downlink shared channel (PDSCH) scheduled to the second cell based on the first cell being within the active period, Method for receiving downlink signals.
3. In paragraph 1, Including not performing PDCCH monitoring for the second cell based on the first cell being within the inactive period, Method for receiving downlink signals.
4. In paragraph 1, Including not performing physical downlink shared channel (PDSCH) reception scheduled for the second cell based on the first cell being within the inactive period, Method for receiving downlink signals.
5. In paragraph 3, PDCCH monitoring for the second cell is not performed within the non-active period of the first cell, regardless of whether there is a cell DRX setting for the second cell. Method for receiving downlink signals.
6. In paragraph 1, Including postponing a first PUCCH transmission scheduled within the non-active period of the first cell to after the non-active period, Method for receiving downlink signals.
7. In paragraph 6, Postponing the above first PUCCH transmission to the inactive period: Including transmitting the HARQ-ACK codebook in the first PUCCH transmission in addition to another HARQ-ACK codebook scheduled after the non-active period of the first cell, Method for receiving downlink signals.
8. When a user device receives a downlink signal in a wireless communication system, 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, said operations comprising: Receive cell discontinuous reception (DRX) settings for a first cell for which physical uplink control channel (PUCCH) resources are configured; Based on the cell DRX setting for the first cell, determining an active period in which uplink transmissions of the first cell are not restricted and a non-active period in which uplink transmissions of the first cell are restricted; and Comprising: performing physical downlink control channel (PDCCH) monitoring for a second cell that uses the first cell for PUCCH transmissions based on the first cell being within the active period; User device.
9. In a processing device in a wireless communication system, 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, said operations comprising: Receive cell discontinuous reception (DRX) settings for a first cell for which physical uplink control channel (PUCCH) resources are configured; Based on the cell DRX setting for the first cell, determining an active period in which uplink transmissions of the first cell are not restricted and a non-active period in which uplink transmissions of the first cell are restricted; and Comprising: performing physical downlink control channel (PDCCH) monitoring for a second cell that uses the first cell for PUCCH transmissions based on the first cell being within the active period; Processing unit.
10. In a computer-readable storage medium, The storage medium stores at least one program code comprising instructions that, when executed, cause at least one processor to perform operations, the operations comprising: Receive cell discontinuous reception (DRX) settings for a first cell for which physical uplink control channel (PUCCH) resources are configured; Based on the cell DRX setting for the first cell, determining an active period in which uplink transmissions of the first cell are not restricted and a non-active period in which uplink transmissions of the first cell are restricted; and Comprising: performing physical downlink control channel (PDCCH) monitoring for a second cell that uses the first cell for PUCCH transmissions based on the first cell being within the active period; Storage medium.
11. In a wireless communication system, when a base station transmits a downlink signal to a user device, Transmit cell discontinuous reception (DRX) settings for a first cell for which physical uplink control channel (PUCCH) resources are configured; Based on the cell DRX setting for the first cell, determining an active period in which uplink receptions of the first cell are not restricted and a non-active period in which uplink receptions of the first cell are restricted; and Including performing a physical downlink control channel (PDCCH) transmission for a second cell that uses the first cell for PUCCH reception based on the first cell being within the active period. Downlink signal transmission method.
12. In a wireless communication system, when a base station transmits a downlink signal to a user device, 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, said operations comprising: Transmit cell discontinuous reception (DRX) settings for a first cell for which physical uplink control channel (PUCCH) resources are configured; Based on the cell DRX setting for the first cell, determining an active period in which uplink receptions of the first cell are not restricted and a non-active period in which uplink receptions of the first cell are restricted; and Including performing a physical downlink control channel (PDCCH) transmission for a second cell that uses the first cell for PUCCH reception based on the first cell being within the active period. Base station.
13. In paragraph 12, Including performing a physical downlink shared channel (PDSCH) transmission scheduled to the second cell based on the first cell being within the active period, Base station.
14. In paragraph 12, Including not performing PDCCH transmission to the second cell based on the first cell being within the inactive period, Base station.
15. In paragraph 12, Including not performing a physical downlink shared channel (PDSCH) transmission scheduled to the second cell based on the first cell being within the inactive period, Base station.
16. In paragraph 14, The PDCCH transmission for the second cell is not performed within the non-active period of the first cell, regardless of whether there is a cell DRX setting for the second cell. Base station.
17. In paragraph 12, Including postponing reception of a first PUCCH scheduled within the non-active period of the first cell to after the non-active period, Base station.
18. In paragraph 17, Postponing the reception of the first PUCCH to the non-active period: Including receiving HARQ-ACK information appended to another HARQ-ACK codebook scheduled after the non-active period of the first cell in the HARQ-ACK codebook within the first PUCCH reception, Base station.
Citation Information
Patent Citations
Sterilized type cleaning, washing, blasting, coating, painting, treatment equipment and method
KR1020210146257A
Cyclic type juvenile fish water tank
KR1020220131577A
Cross-carrier scheduling across different DRX groups
US20220394734A1
Cited By
Uplink transmission using low power radio
US12764667B2
Uplink transmission using low power radio
US20250351078A1
