Method performed by first device, first device, processing device and storage medium, and method performed by second device and second device
By employing DTX/DRX settings and SS adjustments, the method optimizes energy usage in cellular networks, addressing the challenges of network energy conservation and power conservation in user equipment.
Patent Information
- Application Number
- PCT/KR2026/096621
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2026-01-29
- Filing Date
- 2026-05-06
- Publication Date
- 2026-11-12
AI Technical Summary
The increasing demand for data processing in cellular networks due to emerging communication technologies like machine-to-machine communication and high data transmission rates, coupled with the need for enhanced mobile broadband, massive machine type communication, and ultra-reliable and low-latency communication, poses challenges in network energy conservation and power conservation in user equipment.
Implementing methods and processes for network energy saving by utilizing cell discontinuous transmission/reception (DTX/DRX) settings, including periodic patterns for active and inactive periods, and adjusting search space (SS) settings to optimize physical downlink control channel (PDCCH) monitoring, thereby reducing unnecessary energy consumption.
Enhances network energy efficiency by minimizing energy usage during inactive periods and optimizing signal transmission/reception, thus addressing the need for energy conservation in networks and user equipment.
Smart Images

Figure KR2026096621_12112026_PF_FP_ABST
Abstract
Description
A method performed by a first device, a first device, a processing device and a storage medium, and a method performed by a second device and a second device
[0001] This specification relates to a wireless communication system.
[0002] Various devices and technologies, such as machine-to-machine (M2M) communication, machine type communication (MTC), and devices requiring high data transmission rates like smartphones and tablet PCs (Personal Computers), are emerging and becoming widespread. Consequently, the amount of data required to be processed in cellular networks is increasing very rapidly. To satisfy this rapidly increasing demand for data processing, technologies such as carrier aggregation and cognitive radio are being developed to efficiently utilize more frequency bands, while technologies such as multi-antenna technology and multi-BS cooperation are being developed to increase the data capacity transmitted within a limited frequency range.
[0003] As more communication devices require greater communication capacity, the need for enhanced mobile broadband (eMBB) communication is emerging compared to legacy radio access technology (RAT). In addition, massive machine type communication (mMTC), which connects multiple devices and objects to provide various services anytime and anywhere, is one of the key issues to consider in next-generation communication.
[0004] In addition, discussions are underway regarding communication systems to be designed with user equipment (UE) in mind, which is sensitive to reliability and latency. The introduction of next-generation wireless access technologies is being discussed with consideration of eMBB communication, mMTC, and ultra-reliable and low-latency communication (URLLC).
[0005] As the number of services and UEs that the network must support increases rapidly, the need for energy conservation in the network, as well as power conservation in the UEs, is gradually growing.
[0006] One technical objective of this specification is to provide methods and processes for network energy saving.
[0007] Another technical objective of this specification is to provide methods and processes for transmitting or receiving downlink / uplink signals to enable network energy saving.
[0008] The technical problems that this specification aims to solve are not limited to those mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art related to this specification from the detailed description below.
[0009] In one aspect of the present specification, a method performed by a first device is provided. In another aspect of the present specification, a first device is provided comprising 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. In yet another aspect of the present specification, a processing device is provided comprising 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. In yet another aspect of the present specification, a computer-readable non-transitory storage medium is provided for storing at least one program code that includes instructions that, when executed, cause the at least one processor to perform operations. The above methods or operations may include: receiving cell discontinuous transmission (DTX) / discontinuous reception (DRX) settings for a cell, wherein the cell DTX / DRX settings include first information related to a periodic pattern of active, semi-static, and inactive periods; receiving second information for setting a search space (SS) set related to the periodic pattern; and performing physical downlink control channel (PDCCH) monitoring based on the first information and the second information.
[0010] In one aspect of the present specification, a method performed by a second device is provided. In another aspect of the present specification, a second device is provided comprising at least one transceiver; at least one processor; and at least one computer memory operably connectable to the at least one processor and, when executed, stores instructions that cause the at least one processor to perform operations. The method or the operations may include: transmitting a cell discontinuous transmission (DTX) / discontinuous reception (DRX) setting for a cell, wherein the cell DTX / DRX setting comprises first information relating to a periodic pattern of active, semi-static, and inactive periods; transmitting second information for setting a search space (SS) set relating to the periodic pattern; and performing a physical downlink control channel (PDCCH) transmission based on the first information and the second information.
[0011] In each aspect of this specification, downlink (DL) reception or transmission and uplink (UL) transmission or reception may not be performed within the inactive period.
[0012] In each aspect of the specification, the SS set setting may include a common search space (CSS) set setting for each of the active interval, the semi-active interval, and the inactive interval.
[0013] In each aspect of this specification, the CSS set configuration is related to the reception or transmission of system information (SI), the reception or transmission of paging, or the reception or transmission of a random access response (RAR).
[0014] In each aspect of the specification, the method or operation may further include determining that the PDCCH monitoring occasion (MO) is invalid based on whether the PDCCH monitoring occasion (MO) is associated with a set of common search spaces (CSS) within the inactive interval.
[0015] In each aspect of the specification, the method or operation may further include: omitting PDCCH monitoring or PDCCH transmission for the first device-specific downlink control information (DCI) on the SS set within at least one of the semi-active period or the inactive period.
[0016] The above-mentioned problem-solving methods are merely 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 with ordinary knowledge in the relevant technical field based on the detailed description below.
[0017] According to some implementations of this specification, methods and procedures for energy saving of networks, BS and / or UEs may be provided.
[0018] According to some implementations of this specification, methods and procedures for transmitting or receiving downlink / uplink signals may be provided to enable energy saving of the network, BS and / or UE.
[0019] The effects of this specification are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art related to this specification from the detailed description below.
[0020] The attached drawings, included as part of the detailed description to aid in understanding the implementations of this specification, provide examples of the implementations of this specification and describe the implementations of this specification together with the detailed description:
[0021] FIG. 1 illustrates an example of a communication system 1 to which the implementations of the present specification are applied;
[0022] FIG. 2 is a block diagram illustrating examples of communication devices capable of performing the method according to the present specification;
[0023] FIG. 3 illustrates another example of a wireless device capable of performing the implementation(s) of the present specification;
[0024] FIG. 4 illustrates an example of a frame structure available in a 3rd generation partnership project (3GPP)-based wireless communication system;
[0025] FIG. 5 illustrates a resource grid of slots;
[0026] 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 the signal transmission / reception process using them;
[0027] FIG. 7 illustrates synchronization signal (SS) / physical broadcast channel (PBCH) blocks (SSB) on a cell.
[0028] FIG. 8 is illustrated to explain the bitmaps used to indicate the SSBs actually being transmitted;
[0029] FIG. 9 illustrates the process of acquiring system information (SI);
[0030] FIG. 10 illustrates an arbitrary connection process that may be applied to the implementation(s) of the present specification;
[0031] FIG. 11 illustrates an example of time-domain resource allocation of a physical downlink shared channel (PDSCH) by a physical downlink control channel (PDCCH) and an example of time-domain resource allocation of a physical uplink shared channel (PUSCH) by a PDCCH;
[0032] FIG. 12 illustrates discontinuous reception (DRX) operation;
[0033] FIG. 13 illustrates an operation procedure in a BS that supports network energy saving (NES) technology;
[0034] FIG. 14 is an example of a procedure for carrier aggregation (CA) operation using an SSB-less secondary cell (SCell);
[0035] FIGS. 15 through 17 illustrate system information block 1 (SIB1) transmission scenarios related to some implementations of the present specification;
[0036] FIG. 18 illustrates paging times according to several scenarios;
[0037] FIG. 19 is an example of an operation related to cell discontinuous transmission (DTX) / discontinuous reception (DRX);
[0038] FIG. 20 is an example of cell DTX / DRX related operation according to some implementations;
[0039] FIG. 21 is an example of random access channel (RACH) slots and RACH occasions (RO) according to a physical random access channel (PRACH) setting;
[0040] FIG. 22 illustrates a signal transmission / reception flow between a first device and a second device according to some implementations of the present specification;
[0041] FIG. 23 is another example of the operation flow in the first device according to some implementations of the present specification;
[0042] FIG. 24 is another example of the operation flow in a second device according to some implementations of the present specification.
[0043] Implementations according to this specification are described below with reference to the accompanying drawings. The detailed description disclosed below, together with the accompanying drawings, is intended to describe exemplary implementations of this specification and is not intended to represent the only form in which this specification may be practiced. The detailed description below includes specific details to provide a complete understanding of this specification. However, a person skilled in the art will know that this specification may be practiced without such specific details.
[0044] In some cases, to avoid ambiguity regarding the concepts of this specification, known structures and devices may be omitted or depicted in the form of block diagrams focusing on the core functions of each structure and device. Additionally, the same reference numerals are used to describe identical components throughout this specification.
[0045] In this specification, "A or B" may mean "only A," "only B," or "both A and B." Alternatively, in this specification, "A or B" may be interpreted as "A and / or B." For example, in this specification, "A, B or C" may mean "only A," "only B," "only C," or "any combination of A, B and C."
[0046] A slash ( / ) or comma used in this specification may mean "and / or." For example, "A / B" may mean "A and / or B." Accordingly, "A / B" may mean "only A," "only B," or "both A and B." For example, "A, B, C" may mean "A, B or C."
[0047] In this specification, "at least one of A and B" may mean "only A," "only B," or "both A and B." Additionally, in this specification, the expressions "at least one of A or B" or "at least one of A and / or B" may be interpreted as synonymous with "at least one of A and B."
[0048] Additionally, in this specification, "at least one of A, B and C" may mean "only A," "only B," "only C," or "any combination of A, B and C." Also, "at least one of A, B or C" or "at least one of A, B and / or C" may mean "at least one of A, B and C."
[0049] In addition, terms such as "first," "second," etc. in this specification are used solely for the purpose of distinguishing one component from another and are not used to limit the components, nor do they limit the order or importance of the components unless specifically limited. Accordingly, the first component in one embodiment of this specification may be referred to as the second component in another embodiment, and likewise, the second component in one embodiment may be referred to as the first component in another embodiment.
[0050] In the following explanation, 'when, if, in case of' can be replaced with 'based on'.
[0051] In this specification, information / status / parameters being "configured or pre-configured" may be interpreted as information / status / parameters being provided or pre-provided to the UE through pre-defined signaling from the BS (e.g., system information block (SIB), medium access control (MAC), radio resource control (RRC)). In this specification, information / status / parameters being "defined or pre-defined" may be interpreted as information / status / parameters being known or stored in advance by the BS and the UE without signaling between the BS and the UE.
[0052] Technical features described individually within a single drawing in this specification may be implemented individually or simultaneously.
[0053] The techniques, devices, and systems described below can be applied to various wireless multiple access systems. Examples of multiple access systems include CDMA (code division multiple access) systems, FDMA (frequency division multiple access) systems, TDMA (time division multiple access) systems, OFDMA (orthogonal frequency division multiple access) systems, SC-FDMA (single carrier frequency division multiple access) systems, and MC-FDMA (multi carrier frequency division multiple access) systems. CDMA can be implemented in wireless technologies such as UTRA (Universal Terrestrial Radio Access) or CDMA2000. TDMA can be implemented in wireless technologies such as GSM (Global System for Mobile communication), GPRS (General Packet Radio Service), and EDGE (Enhanced Data Rates for GSM Evolution) (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 part of E-UMTS that utilizes 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.
[0054] For the 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 thereto. For example, even though the following detailed description is based on a mobile communication system corresponding to a 3GPP LTE / NR system, it may be applied to any other mobile communication system, except for matters specific to 3GPP LTE / NR.
[0055] For terms and technologies used in this specification that are not specifically described, reference may be made to 3GPP-based standard documents, e.g., 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.
[0056] In the examples of this specification described below, the expression that the device "assumes" may mean that the entity transmitting the channel transmits the channel in accordance with said "assume." It may mean that the entity receiving the channel receives or decodes the channel in a form that conforms to said "assume," under the premise that the channel was transmitted in accordance with said "assume."
[0057] In this specification, UEs may be fixed or mobile and include various devices that communicate with a base station (BS) to transmit and / or receive user data and / or various control information. A UE may be referred to as Terminal Equipment, Mobile Station (MS), Mobile Terminal (MT), User Terminal (UT), Subscribe Station (SS), wireless device, Personal Digital Assistant (PDA), wireless modem, handheld device, etc. Additionally, in this specification, a BS generally refers to a fixed station that communicates with a UE and / or other BSs and exchanges various data and control information by communicating with a UE and other BSs. A BS may be referred to by other terms such as Advanced Base Station (ABS), Node-B (NB), eNB (evolved-NodeB), Base Transceiver System (BTS), Access Point, Processing Server (PS), etc. In particular, BSs of UTRAN are called Node-Bs, BSs of E-UTRAN are called eNBs, and BSs of new radio access technology networks are called gNBs. For convenience of explanation, BSs will be collectively referred to as BSs regardless of the type or version of the communication technology.
[0058] In this specification, a node refers to a fixed point capable of transmitting or receiving wireless signals by communicating with a UE. Various types of BSs may be used as nodes regardless of their designation. For example, a BS, NB, eNB, pico-cell eNB (PeNB), home eNB (HeNB), relay, repeater, etc., may serve as a node. Additionally, a node does not have to be a BS. For example, it may be a radio remote head (RRH) or a radio remote unit (RRU). RRHs, RRUs, etc. generally have a power level lower than that of a BS. Since an RRH or RRU (or 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 compared to cooperative communication between BSs connected via wireless lines. At least one antenna is installed at a node. This antenna may refer to a physical antenna, an antenna port, a virtual antenna, or an antenna group. Nodes are also referred to as points.
[0059] In this specification, the term "cell" refers to a specific geographical area where one or more nodes provide communication services. Accordingly, in this specification, communicating with a specific cell may mean communicating with a BS or node that provides communication services to said specific cell. Furthermore, the downlink / uplink signals of a specific cell refer to downlink / uplink signals from to or to the BS or node that provides communication services to said specific cell. A cell that provides uplink / downlink communication services to a UE is specifically referred to as a serving cell. Additionally, the channel state / quality of a specific cell refers to the channel state / quality of the channel or communication link formed between the BS or node providing communication services to said specific cell and the UE. In a 3GPP-based communication system, a UE can measure the downlink channel state from a specific node using the CRS(s) transmitted by the antenna port(s) of the specific node over the CRS (Cell-specific Reference Signal) resource assigned to the specific node and / or the CSI-RS(s) transmitted over the CSI-RS (Channel State Information Reference Signal) resource.
[0060] Meanwhile, 3GPP-based communication systems use the concept of a cell to manage wireless resources, and a cell associated with wireless resources is distinguished from a cell in a geographical area.
[0061] A “cell” of a geographical area can be understood as the coverage over which a node can provide services using a carrier wave, and a “cell” of a wireless resource is associated with the bandwidth (BW), which is the frequency range configured by said carrier wave. 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 valid signal can be received from a UE, depend on the carrier wave carrying the signal, the coverage of a node is also associated with the coverage of the “cell” of the wireless resource used by said node. Therefore, the term “cell” can be used to refer sometimes to the coverage of a service by a node, sometimes to a wireless resource, and sometimes to the range over which a signal using said wireless resource can reach with effective strength.
[0062] Meanwhile, 3GPP communication standards use 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), that is, a combination of a DL component carrier (CC) and a UL CC. A cell can be configured as a DL resource alone or as a combination of a DL resource and a UL resource. Where carrier aggregation is supported, the linkage between the carrier frequency of a DL resource (or DL CC) and the carrier frequency of a UL resource (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 may be equal to 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 establishment / re-establishment / handover, and one serving cell provides security input during RRC re-establishment / handover. This cell is called a primary cell (Pcell). A Pcell is a cell operating on the primary frequency where the UE performs the initial connection establishment procedure or initiates the connection re-establishment procedure.Depending on the UE capability, secondary cells (Scells) can be configured to form a set of serving cells together with Pcells. Scells can be configured after a Radio Resource Control (RRC) connection is established and are cells that provide additional radio resources in addition to the resources of special cells (SpCells). The carrier corresponding to a Pcell in the downlink is called the Downlink Primary CC (DL PCC), and the carrier corresponding to a Pcell in the uplink is called the UL Primary CC (UL PCC). The carrier corresponding to an Scell in the downlink is called the DL Secondary CC (DL SCC), and the carrier corresponding to the Scell in the uplink is called the UL Secondary CC (UL SCC).
[0063] In a UE where CA is configured and DC is not configured, a Pcell PUCCH group (also referred to as a primary PUCCH group) consisting of a Pcell and zero or more Scells, and an Scell PUCCH group (also referred to as a secondary PUCCH group) consisting only of Scell(s) may be configured. In the case of an Scell, an Scell (hereinafter referred to as a PUCCH Scell) to which a PUCCH associated with that cell is transmitted may be configured. An Scell designated as a PUCCH Scell belongs to the Scell PUCCH group (i.e., secondary PUCCH group), and the PUCCH transmission of the associated UCI is performed on the said PUCCH Scell; an Scell that is not designated as a PUCCH Scell, or an Scell in which the cell designated as a PUCCH transmission cell is a Pcell, belongs to the Pcell PUCCH group (i.e., primary PUCCH group), and the PUCCH transmission of the associated UCI is performed on the said Pcell. In the following, if the UE is configured with an SCG and some implementations of this specification related to PUCCH apply to the SCG, the primary cell may refer to the PSCell of the SCG. If the UE is configured with a PUCCH Scell and some implementations of this specification related to PUCCH apply to a secondary PUCCH group, the primary cell may refer to the PUCCH Scell of the secondary PUCCH group.
[0064] In a wireless communication system, the UE receives information from the BS via the downlink (DL) and transmits information to the BS via the uplink (UL). The information transmitted and / or received by the BS and the 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.
[0065] 3GPP-based communication standards define downlink physical channels corresponding to resource elements that carry information originating from upper layers, and downlink physical signals corresponding to resource elements used by the physical layer but not carrying information originating from upper 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, while the reference signal and synchronization signal are defined as downlink physical signals. The reference signal (RS), also referred to as a pilot, refers to a signal of a specific, predefined waveform known to both the BS and the UE. For example, the demodulation reference signal (DMRS), channel state information RS (CSI-RS), and 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 upper layers, and uplink physical signals corresponding to resource elements that are used by the physical layer but do not carry information originating from upper layers.For example, the physical uplink shared channel (PUSCH), physical uplink control channel (PUCCH), and physical random access channel (PRACH) are defined as uplink physical channels, and the demodulation reference signal (DMRS) for uplink control / data signals and the sounding reference signal (SRS) used for uplink channel measurement are defined.
[0066] In this specification, PDCCH (Physical Downlink Control Channel) refers to a set of time-frequency resources (e.g., resource elements (REs)) carrying DCI (Downlink Control Information), and PDSCH (Physical Downlink Shared Channel) refers to a set of time-frequency resources carrying downlink data. Additionally, PUCCH (Physical Uplink Control Channel), PUSCH (Physical Uplink Shared Channel), and PRACH (Physical Random Access Channel) respectively refer to sets of time-frequency resources carrying UCI (Uplink Control Information), uplink data, and random access signals. In the following, the expression that a user device transmits / receives PUCCH / PUSCH / PRACH is used to mean that the user device transmits / receives uplink control information / uplink data / random access signals on or through PUCCH / PUSCH / PRACH, respectively. In addition, 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.
[0067] In this specification, radio resources (e.g., time-frequency resources) scheduled or set for a UE by a BS for the transmission or reception of PUCCH / PUSCH / PDSCH are also referred to as PUCCH / PUSCH / PDSCH resources.
[0068] 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 the cell, it is not possible to selectively receive only radio signals containing only a specific physical channel or a specific physical signal through the RF receiver, or to selectively receive only radio signals excluding only a specific physical channel or a specific physical signal through the RF receiver. In actual operation, the communication device first receives radio signals on the cell through the RF receiver, converts the radio signals, which are RF band signals, into baseband signals, and uses one or more processors to decode the physical signals and / or physical channels within the baseband signals. Accordingly, in some implementations of this specification, not receiving a physical signal and / or physical channel may actually mean that the communication device does not receive wireless signals containing the physical signal and / or physical channel at all, but rather does not attempt to recover the physical signal and / or physical channel from the wireless signals, for example, not attempt to decode the physical signal and / or physical channel.
[0069] As more communication devices require larger communication capacities, the need for improved mobile broadband communication compared to existing radio access technology (RAT) is emerging. Furthermore, Massive Mobile Telecommunications (MTC), which connects multiple devices and objects to provide various services anytime and anywhere, is also one of the key issues to be considered in next-generation communication. In addition, communication system designs that consider reliability and latency-sensitive services / UEs are being discussed. Accordingly, the introduction of next-generation RATs that incorporate advanced mobile broadband communication, Massive MTC, and Ultra-Reliable and Low Latency Communication (URLC) is being discussed. Currently, 3GPP is conducting studies on next-generation mobile communication systems following the EPC. For convenience, this specification refers to the technology as New RAT (NR) or 5G RAT, and systems that use or support NR are referred to as NR systems.
[0070] FIG. 1 illustrates an example of a communication system 1 to which the implementations of the present specification apply. Referring to FIG. 1, the communication system (1) to which the present specification applies includes a wireless device, a BS, and a network. Here, a wireless device refers to a device that performs communication using 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, a 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 Thing) device (100f), and an AI device / server (400). For example, a vehicle may include a vehicle equipped with wireless communication capabilities, an autonomous vehicle, a vehicle capable of performing inter-vehicle communication, etc. Here, vehicles may include UAVs (Unmanned Aerial Vehicles) (e.g., drones). XR devices include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices and may be implemented in the form of HMDs (Head-Mounted Devices), HUDs (Head-Up Displays) equipped in vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signage, vehicles, robots, etc. Portable devices may include smartphones, smartpads, wearable devices (e.g., smartwatches, smart glasses), computers (e.g., laptops, etc.). Home appliances may include TVs, refrigerators, washing machines, etc. IoT devices may include sensors, smart meters, etc. For example, BS and networks may be implemented as wireless devices, and specific wireless devices may operate as BS / network nodes to other wireless devices.
[0071] Wireless devices (100a to 100f) can be connected to a network (300) via a BS (200). Artificial Intelligence (AI) technology may 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 the network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. The wireless devices (100a to 100f) may communicate with each other via the BS (200) / network (300), but they may also communicate directly (e.g., sidelink communication) without using the BS / network. For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to everything) communication). Also, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).
[0072] Wireless communication / connection (150a, 150b) may be established between wireless devices (100a~100f) / BS (200) and BS (200) / wireless devices (100a~100f). Here, the wireless communication / connection may be established through uplink / downlink communication (150a) and sidelink communication (150b) (or D2D communication) using various wireless access technologies (e.g., 5G NR). Through the wireless communication / connection (150a, 150b), wireless devices and BS / wireless devices may transmit / receive wireless signals to / from each other. To this end, based on various proposals of the present specification, at least some of the following may be performed: a process for setting various configuration information for transmitting / receiving wireless signals, a process for various signal processing (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and a resource allocation process.
[0073] FIG. 2 is a block diagram illustrating examples of communication devices capable of performing the 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 through various wireless access technologies (e.g., LTE, NR). Here, {the first wireless device (100), the second wireless device (200)} may correspond to {wireless device (100x), BS (200)} and / or {wireless device (100x), wireless device (100x)} of FIG. 1.
[0074] The first wireless device (100) includes one or more processors (102) and one or more memories (104), and may additionally include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memory (104) and / or transceivers (106) and may be configured to implement the functions, procedures and / or methods described / suggested below. For example, the processor (102) may process information within the memory (104) to generate a first information / signal and then transmit a wireless signal containing the first information / signal through the transceiver (106). Additionally, the processor (102) may receive a wireless signal containing a second information / signal through the transceiver (106) and then store information obtained from the signal processing of the second information / signal in the memory (104). Memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, memory (104) may store software code containing instructions for performing some or all of the processes controlled by the processor (102) or for performing the procedures and / or methods described / suggested below. Here, the processor (102) and memory (104) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). A transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals through one or more antennas (108). The transceiver (106) may include a transmitter and / or receiver. The transceiver (106) may be interchangeably used with an RF (Radio Frequency) unit. In this specification, a wireless device may mean a communication modem / circuit / chip.
[0075] The second wireless device (200) includes one or more processors (202) and one or more memories (204), and may additionally include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memory (204) and / or 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 within the memory (204) to generate a third information / signal and then transmit a wireless signal containing the third information / signal through the transceiver (206). Additionally, the processor (202) may receive a wireless signal containing a fourth information / signal through the transceiver (206) and then store information obtained from the signal processing of the fourth information / signal in the memory (204). Memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, memory (204) may store software code containing instructions for performing some or all of the processes controlled by the processor (202) or for performing the procedures and / or methods described / suggested below. Here, the processor (202) and memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). A transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals through one or more antennas (208). The transceiver (206) may include a transmitter and / or receiver. The transceiver (206) may be interchangeably used with an RF unit. In this specification, a wireless device may mean a communication modem / circuit / chip.
[0076] The wireless communication technology implemented in the wireless device (100, 200) of this specification may include LTE, NR, and 6G, as well as Narrowband Internet of Things for low-power communication. In this case, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology and may be implemented according to standards such as LTE Cat NB1 and / or LTE Cat NB2, but is not limited to the names mentioned above. Additionally, or generally, the wireless communication technology implemented in the wireless device (XXX, YYY) of this specification may perform communication based on LTE-M technology. In this case, for example, LTE-M technology may be an example of LPWAN technology and may be referred to by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology may be implemented in 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 names mentioned above. Additionally or generally, wireless communication technology implemented in the wireless device (XXX, YYY) of this specification may include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) with consideration for low-power communication, and is not limited to the names mentioned above. As an example, ZigBee technology can create personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4 and may be referred to by various names.
[0077] 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 (PDU) and / or one or more service data units (SDU) according to the functions, procedures, proposals and / or methods disclosed in this specification. One or more processors (102, 202) may generate messages, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in this specification. One or more processors (102, 202) may generate a signal (e.g., baseband signal) containing a PDU, SDU, message, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in this specification and provide it to one or more transceivers (106, 206). One or more processors (102, 202) may receive a signal (e.g., baseband signal) from one or more transceivers (106, 206) and may obtain a PDU, SDU, message, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in this specification.
[0078] One or more processors (102, 202) may be referred to as a controller, microcontroller, microprocessor, or microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in one or more processors (102, 202). The functions, procedures, proposals, and / or methods disclosed in this specification may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. Firmware or software configured to perform the functions, procedures, proposals and / or methods disclosed in this specification may be included in one or more processors (102, 202) or stored in one or more memories (104, 204) and driven by one or more processors (102, 202). The functions, procedures, proposals and / or methods disclosed in this specification may be implemented using firmware or software in the form of code, instructions and / or sets of instructions.
[0079] One or more memories (104, 204) may be connected to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, code, instructions, and / or commands. One or more memories (104, 204) may be composed of ROM, RAM, EPROM, flash memory, hard drive, registers, cache memory, computer read storage media, and / or combinations thereof. One or more memories (104, 204) may be located inside and / or outside of one or more processors (102, 202). Additionally, one or more memories (104, 204) may be connected to one or more processors (102, 202) through various technologies such as wired or wireless connections.
[0080] One or more transceivers (106, 206) may transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or operation flowcharts, etc. of this specification to one or more other devices. One or more transceivers (106, 206) may receive user data, control information, wireless signals / channels, etc., as mentioned in the functions, procedures, proposals, methods and / or operation flowcharts, etc. disclosed in this specification from one or more other devices. For example, one or more transceivers (106, 206) may be connected to one or more processors (102, 202) and may transmit and / or receive wireless signals. For example, one or more processors (102, 202) may control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be connected 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, etc., as mentioned in the functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification through one or more antennas (108, 208). In this specification, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) can convert the received wireless signal / channel, etc. from an RF band signal to a baseband signal in order to process the received user data, control information, wireless signal / channel, etc. using one or more processors (102, 202).One or more transceivers (106, 206) can convert user data, control information, wireless signals / channels, etc. processed using one or more processors (102, 202) from baseband signals to RF band signals. To this end, one or more transceivers (106, 206) may include (analog) oscillators and / or filters.
[0081] 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 / parts, 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 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 additional elements (140) and controls the general operation of the wireless device. For example, the control unit (120) may control the electrical / mechanical operation of the wireless device based on a program / code / command / information stored in the memory unit (130). Additionally, the control unit (120) may transmit information stored in the memory unit (130) to the outside (e.g., another communication device) via a wireless / wired interface through the communication unit (110), or store information received from the outside (e.g., another communication device) via a wireless / wired interface through the communication unit (110) in the memory unit (130).
[0082] The additional element (140) may be configured in various ways depending on the type of wireless device. For example, the additional element (140) may include at least one of a power unit / battery, an input / output unit (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 holographic device, a public safety device, an MTC device, a medical device, a fintech device (or financial device), a security device, a climate / environment device, an AI server / device (Fig. 1, 400), a BS (Fig. 1, 200), a network node, etc. Depending on the use—e.g., service—the wireless device may be movable or used in a fixed location.
[0083] 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 a portion 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 the first unit (e.g., 130, 140) may be wirelessly connected via the communication unit (110). Additionally, each element, component, unit / part, and / or module within the wireless device (100, 200) may include one or more additional elements. For example, the control unit (120) may be composed of one or more sets of processors. 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, transitory memory, non-transitory memory and / or a combination thereof.
[0084] In this specification, at least one memory (e.g., 104 or 204) may store instructions or programs, and said instructions or programs may, when executed, cause at least one processor operablely connected to said at least one memory to perform operations according to some embodiments or implementations of this specification.
[0085] In this specification, a computer-readable (non-transient) storage medium may store at least one instruction or computer program, and when executed by at least one processor, said at least one instruction or computer program may cause said at least one processor to perform operations according to some embodiments or implementations of this specification.
[0086] In this specification, a processing device or apparatus may include at least one processor and at least one computer memory connectable to said at least one processor. said at least one computer memory may store instructions or programs, and said instructions or programs, when executed, may cause at least one processor operablely connected to said at least one memory to perform operations according to some embodiments or implementations of this specification.
[0087] In this specification, a computer program may include program code stored on at least one computer-readable (non-transient) storage medium and, when executed, perform operations according to some implementations of this specification or cause at least one processor to perform operations according to some implementations of this 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-transient) storage medium.
[0088] A communication device of this 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 examples(s) of this specification described below.
[0089] Figure 4 illustrates an example of a frame structure available in a 3GPP-based wireless communication system.
[0090] The structure of the frame in Fig. 4 is merely an example, and the number of subframes, slots, and symbols in the frame can be varied. In an NR system, OFDM numerology (e.g., subcarrier spacing (SCS)) may be configured differently among multiple cells aggregated to a single UE. Accordingly, the (absolute time) duration of a time resource (e.g., subframe, slot, or transmission time interval (TTI)) consisting of the same number of symbols may be configured differently among the aggregated cells. Here, symbols may include OFDM symbols (or cyclic prefix-orthogonal frequency division multiplexing (CP-OFDM) symbols) and SC-FDMA symbols (or discrete Fourier transform-spread-OFDM (DFT-s-OFDM) symbols). In this specification, symbols, OFDM-based symbols, OFDM symbols, CP-OFDM symbols, and DFT-s-OFDM Symbols can be substituted for each other.
[0091] Referring to Fig. 4, uplink and downlink transmissions in an NR system are organized into frames. Each frame is T f = (△f max *N f / 100)*T c = It has a duration of 10 ms and is divided into two half-frames, each with a duration of 5 ms. Here, T is the basic time unit for NR. c = 1 / (△fmax *N f ) and, △f max = 480*10 3 It is Hz, and N f = 4096. For reference, T is the standard time unit for LTE. s = 1 / (△f ref *N f,ref ) and, △f ref = 15*10 3 It is Hz, and N f,ref =2048. T c Wow T s is a constant κ = T s / T c It has a relationship of = 64. Each half-frame consists of 5 subframes, and the period T of a single subframe (SF) sf is 1ms. Subframes are further divided into slots, and the number of slots within a subframe depends on the subcarrier spacing. Each slot consists of 14 or 12 OFDM symbols based on a cyclic prefix. For a normal cyclic prefix (CP), each slot consists of 14 OFDM symbols, while for an extended CP, each slot consists of 12 OFDM symbols. The above numerology is an exponentially scalable subcarrier spacing △f = 2 u It depends on 15 kHz. The following table shows the subcarrier spacing △f = 2 for a normalized CP. u *Number of OFDM symbols per slot according to 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 It represents ).
[0092]
[0093] The following table shows the subcarrier spacing △f = 2 for extended CP.u This shows the number of OFDM symbols per slot, the number of slots per frame, and the number of slots per subframe according to *15 kHz.
[0094]
[0095] For a subcarrier interval setting u, the slots are arranged in increasing order n within the subframe. u s ∈ {0, ..., nsubframe,u slot - 1} and n in increasing order within the frame u s,f ∈ {0, ..., n frame,u slot - 1} is numbered.
[0096] FIG. 5 illustrates a resource grid of a slot. A slot contains multiple (e.g., 14 or 12) symbols in the time domain. For each numerator (e.g., subcarrier interval) and carrier, a common resource block (CRB) N indicated by upper-layer signaling (e.g., radio resource control (RRC) signaling) start,u grid Starting from,N size,u grid,x *N RB sc individual subcarriers and N subframe,u symb A resource grid of N OFDM symbols is defined. Here, N size,u grid,x is the number of resource blocks (RB) in the resource grid, and the subscript x is DL for downlinks and UL for uplinks. RB sc is the number of subcarriers per RB, and in 3GPP-based wireless communication systems, N RB scis typically 12. There is one resource grid for a given antenna port p, subcarrier spacing configuration u, and transmission direction (DL or UL). Carrier bandwidth N for subcarrier spacing configuration u. size,u grid This is given to the UE by upper-layer parameters (e.g., RRC parameters) from the network. Each element within the resource grid for antenna port p and subcarrier spacing u is referred to as a resource element (RE), and one complex symbol can be mapped to each resource element. Each resource element within 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, RBs are 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 subcarrier spacing u. The center of subcarrier 0 of CRB 0 for subcarrier spacing u coincides with 'Point A', which is the common reference point for the resource block grids. The PRBs for the subcarrier spacing setting u are defined within the bandwidth part (BWP), and range from 0 to N size,u BWP,i Numbered up to -1, where i is the number of the above bandwidth part. Common resource block n u CRB and physical resource block n within bandwidth part i PRB The relationships between them are as follows: n u PRB = n u CRB +N start,u BWP,i , here N start,u BWP,iis a common resource block where the above bandwidth part starts relative to CRB 0. A BWP contains multiple consecutive RBs in the frequency domain. For example, a BWP is a given numerator u within a BWP i on a given carrier. i It is a subset of contiguous CRBs defined for. A UE may be configured to have one or more BWPs on a given component carrier. On the downlink, the UE may be configured with, for example, up to four BWPs, and only one DL BWP is active at any given time. The UE does not expect to receive PDSCH, PDCCH, or CSI-RS (except for radio resource management) outside of the active BWP. On the uplink, the UE may be configured with, for example, up to four BWPs, and only one UL BWP is active at any given time. The UE does not transmit PUSCH or PUCCH outside of the active BWP.
[0097] For each serving cell within a set of DL BWPs or UL BWPs, the network establishes at least an initial DL BWP and one initial UL BWP (if the serving cell is configured with an uplink) or two initial UL BWPs (if using a supplementary uplink). The network may also establish additional ULs 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) circular prefix, iii) N start BWP Assuming = 275, offset RB set and length L RB CRBN provided by the RRC parameter locationAndBandwidth, which indicates as the resource indicator value (RIV). start BWP =O carrier +RBstart and the number of contiguous RBs N size BWP =L RB , and O provided by the RRC parameter offsetToCarrier for the subcarrier spacing carrier ; Index within the set of the above DL BWPs or UL BWPs; set of BWP-common parameters and set of BWP-exclusive parameters.
[0098] Switching between configured BWPs may occur using RRC signaling, DCI, an inactivity timer, or upon the initiation of a random connection. If an inactivity timer is configured for a serving cell, the expiration of the inactivity timer associated with said serving cell switches the active BWP to the default BWP configured by the network.
[0099] Virtual resource blocks (VRBs) are defined within the bandwidth part and range from 0 to N size,u BWP,i Numbered up to -1, where i is the number of the above 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 can be mapped to PRB n.
[0100] NR frequency bands are defined as two types of frequency ranges, FR1 and FR2, where FR2 is also referred to as millimeter wave (mmW). The following table illustrates the frequency ranges in which NR can operate.
[0101]
[0102] Figure 6 illustrates physical channels used in a 3GPP-based communication system, which is an example of a wireless communication system, and the signal transmission / reception process using them.
[0103] A UE that has been powered off and then turned back on or disconnected from a wireless communication system first performs an initial cell search process, such as searching for a suitable cell to camp on and synchronizing with said cell or the BS of said cell (S11). During the initial cell search process, the UE receives a synchronization signal block (SSB) (also called an SS / 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 the cell identifier (ID). For example, the UE can obtain DL synchronization by detecting the SSB. The UE can identify the structure of the SSB burst based on the detected SSB index and, accordingly, detect the symbol / slot / half-frame boundary. The frame / half-frame number to which the detected SSB belongs can be identified using system frame number (SFN) information and half-frame indication information. Specifically, in a 5G-based system, a UE can obtain 10-bit SFN information from a PBCH. Of the 10-bit SFN information, 6 bits are obtained from a master information block (MIB), and the remaining 4 bits are obtained from a transport block (TB) (also called a PBCH payload) carried by the PBCH. The UE can obtain 1-bit half-frame indication information.When the carrier frequency is 3 GHz or less, half-frame indication information can be implicitly signaled using DM-RS for PBCH (hereinafter, PBCH DM-RS). PBCH DM-RS indicates 3-bit information by using one of eight PBCH DMRS sequences. Therefore, the maximum number of SSBs L within an SSB burst. max In the case of = 4, of the 3 bits that can be indicated using the 8 PBCH DM-RS sequences, the SSB index is indicated, and the remaining 1 bit can be used for half-frame indication. The UE can obtain the SSB index based on the PBCH DM-RS sequences and the PBCH payload. SSB candidates are 0 to L in chronological order within the SSB burst (or half-frame). max - Indexed to 1. L max When = 8 or 64, the three least significant bits (LSBs) of the SSB index can be indicated using eight different PBCH DM-RS sequences. max When = 64, the three most significant bits (MSBs) of the SSB index are indicated via the PBCH. L max When = 2, the two LSBs of the SSB index can be indicated using four different PBCH DM-RS sequences. L max In the case where = 4, the remaining 1 bit of the 3 bits that can be indicated using 8 PBCH DM-RS sequences can be used to indicate the SSB index and for half-frame indication.
[0104] In addition, the UE can obtain in-cell broadcast information based on the PBCH. Meanwhile, during the initial cell search process, the UE can receive a downlink reference signal (DL RS) to check the downlink channel status.
[0105] After completing the initial cell search, the UE can camp on the cell. After camping on the cell, the UE monitors the PDCCH on the cell and receives the PDSCH according to the downlink control information (DCI) carried by the PDCCH to obtain more specific system information (S12).
[0106] Subsequently, the UE may perform a random access procedure to complete access to the BS (S13 to S16). For example, during 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) for the preamble through a PDCCH and a corresponding PDSCH (S14). If the reception of the RAR for the UE fails, the UE may attempt to re-transmit the preamble. In the case of contention-based random access (CBRA), a contention resolution procedure (S16) may be performed, which includes transmitting a PUSCH based on the UL resource allocation included in the RAR (S15) and receiving a PDCCH and a corresponding PDSCH.
[0107] A UE that has performed the procedure described above may subsequently perform the reception of PDCCH / PDSCH (S17) and the transmission of PUSCH / PUCCH (S18) as part of a general uplink / downlink signal transmission process. The control information transmitted by the UE 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 called HARQ-ACK), scheduling request (SR), channel state information (CSI), etc. CSI may include channel quality indicator (CQI), precoding matrix indicator (PMI), and / or rank indicator, etc. UCI is generally transmitted via PUCCH, but may be transmitted via PUSCH if control information and traffic data need to be transmitted simultaneously. In addition, the UE can transmit UCI atypically via PUSCH based on network requests / instructions.
[0108] Figure 7 illustrates SS / PBCH blocks (SSB) on a cell.
[0109] In 3GPP-based systems, each SSB is associated with each beam. For example, during a half-frame, different SSBs may be transmitted in different spatial directions (using different beams that span the cell's coverage area). The possible time positions of SSBs within a half-frame are determined by the subcarriers, and the periododicity of the half-frames in which the SSBs are transmitted is set by the network. Multiple SSBs may be transmitted within the carrier frequency span. Different indices of SSBs transmitted / detected on a single cell may correspond to different BS (wide) Tx beams. Multiple SSBs may be transmitted within the carrier frequency span. The physical (layer) cell identifiers (PCIs) of SSBs transmitted at different frequency locations do not need to be unique, and different SSBs in the frequency domain may have different PCIs. If the SSB is associated with remaining minimum system information (RMSI), the SSB is referred to as a cell-defining SSB (CD-SSB), and the PCell is always associated with the CD-SSB located on the synchronization raster (sync raster). If the SSB is not associated with the RMSI, the SSB is referred to as a non-cell defining SSB (NCD-SSB), which can be used to perform RLM, BFD, and RRM measurements, and measurements for random access resource selection within the active DL BWP if the active DL BWP does not include the CD-SSB.In 3GPP-based systems, multi-beam operation is based on beam switching / beam scanning, which transmits / receives signals while changing the beam direction over time. Beam sweeping refers to the transmission and reception point (TRP) (e.g., BS / cell) changing the beam (direction) of the radio signal over time. In this specification, beam and beam direction may be used interchangeably. SSBs may be transmitted periodically using beam sweeping. In this case, the SSB index is implicitly linked to the SSB beam. The SSB beam may change on an SSB (index) basis or on an SSB (index) group basis. In the latter case, the SSB beam remains the same within the SSB (index) group. For example, referring to Fig. 7, the transmission beam direction of an SSB may be repeated across multiple consecutive SSBs. A set of SSBs is transmitted within a 5 ms half-frame. A set of SSB transmissions within a 5 ms half-frame is called an SSB burst. L is the maximum number of SSB transmissions within an SSB burst. max has a value of 4, 8, or 64 depending on the frequency band to which the carrier belongs. For example, L is the maximum number of SSBs in an SSB burst. max It can be given as follows.
[0110] - For frequency range up to 3 GHz, L max = 4
[0111] - For frequency range from 3GHz to 6 GHz, L max = 8
[0112] - For frequency range from 6 GHz to 52.6 GHz, L max = 64
[0113] The actual number of transmitted SSBs can be configured, with a maximum number L maxIt can be smaller.
[0114] When multi-beam transmission is not applied, the number of SSB beams is 1.
[0115] Figure 8 is illustrated to explain the bitmaps used to indicate the SSBs actually being transmitted.
[0116] Maximum L within SSB burst max SSBs may be transmitted, and the number / locations of the SSBs actually transmitted may vary depending on the BS / cell. The number / locations of the SSBs actually transmitted are used for rate-matching and measurement, and information regarding the SSBs actually transmitted (e.g., RRC setting ssb-PositionsInBurst) may be indicated as follows.
[0117] - In cases related to rate-matching: This may be indicated via UE-specific RRC signaling or RMSI. UE-specific RRC signaling is full (e.g., length L) in both below 6 GHz and above 6 GHz frequency ranges. max ) includes a bitmap. On the other hand, the remaining minimum system information (RMSI) (i.e., SIB1) includes a full bitmap below 6 GHz and, above 6 GHz, includes a bitmap in a compressed form as illustrated. Specifically, information regarding the SSB actually transmitted can be indicated using a group-bitmap (8-bit) and a group-in-bitmap (8-bit). Here, resources indicated by UE-specific RRC signaling or RMSI (e.g., resource elements (REs)) are reserved for SSB transmission, and PDSCH / PUSCH, etc., can be rate-matched considering the SSB resources.
[0118] - In relation to measurement: When in RRC_CONNECTED mode, the network (e.g., BS) can specify the set of SSBs to be measured within the measurement interval. The set of SSBs can be specified by frequency layer. If no specification is given for the set of SSBs, the default set of SSBs is used. The default set of SSBs includes all SSBs within the measurement interval. The set of SSBs is the full of RRC signaling (e.g., length L max It can be specified using a bitmap. If in RRC_IDLE mode, the default SSB set is used.
[0119] Figure 9 illustrates the system information (SI) acquisition process. A UE can acquire AS- / NAS- information through the SI acquisition process. The SI acquisition process can be applied to UEs in the RRC_IDLE, RRC_INACTIVE, and RRC_CONNECTED states. RRC_CONNECTED is a state in which the UE has established an RRC connection with the network. RRC_IDLE is a state in which the UE is not registered with a specific cell and has not received the access stratum (AS) context and other information received from the network. RRC_INACTIVE is a state in which the UE remains in CM-CONNECTED, a state in which it has a signaling connection with the core network for connection management (CM), and can move within an area set by the RAN (e.g., BS(s)) without notifying the radio access network (RAN). CM_CONNECTED is a state in which the UE has a non-access stratum (NAS) signaling connection with the core network, and CM_IDLE is a state in which the UE has no NAS signaling.
[0120] In 3GPP-based systems, SI can be divided into a master information block (MIB) and multiple system information blocks (SIBs). The MIB and multiple SIBs can be further divided into minimum SI and other SI. Here, the minimum SI may consist of an MIB and SystemInformationBlock1 (SIB1), and includes basic information required for initial connection and information for obtaining other SI. Here, SIB1 may be referred to as remaining minimum system information (RMSI). For details, refer to the following.
[0121] - The MIB is always transmitted over a BCH with a periodicity of 80 ms and repetitions created within 80 ms. The MIB contains information / parameters related to the reception of SIB1 and is transmitted via the SSB's PBCH. During initial cell selection, the UE assumes that half-frames containing the SSB(s) repeat at a period of 20 ms. Based on the MIB, the UE can check whether a control resource set (CORESET) exists for the Type0-PDCCH common search space. The Type0-PDCCH common search space is a type of PDCCH search space and is used to transmit the PDCCH that schedules SI messages. If a Type0-PDCCH common seek space exists, the UE can determine (i) multiple consecutive RBs and one or more consecutive symbols that constitute a CORESET and (ii) the PDCCH time (i.e., the time domain location for receiving the PDCCH) based on information within the MIB (e.g., pdcch-ConfigSIB1). If a Type0-PDCCH common seek space does not exist, pdcch-ConfigSIB1 provides information regarding frequency locations where SSB / SIB1 exists and frequency ranges where SSB / SIB1 does not exist.
[0122] - SIB1 is transmitted over a downlink shared channel (DL-SCH) with a periododicity of 160 ms and a variable transmission repetition period within 160 ms. The default transmission repetition period of SIB1 is 20 ms, but the actual transmission repetition period may vary depending on the network implementation. SIB1 contains information regarding the availability and scheduling (e.g., transmission period, SI-window size) of the remaining SIBs (hereinafter SIBx, where x is an integer greater than or equal to 2). For example, SIB1 can indicate whether SIBx is broadcast periodically or provided on-demand by a UE's request. If SIBx is provided on-demand, SIB1 may contain information necessary for the UE to perform an SI request. SIB1 is a cell-specific SIB. The PDCCH scheduling SIB1 is transmitted through the Type0-PDCCH common seek space, and SIB1 is transmitted through the PDSCH directed by the said PDCCH.
[0123] - SIBx is included in SI messages and transmitted via PDSCH. Each SI message is transmitted within a time window (i.e., SI window) that occurs periodically according to SI scheduling information provided by SIB1.
[0124] FIG. 10 illustrates a random connection process that can be applied to the implementation(s) of the present specification. In particular, FIG. 10(a) illustrates a four-step random connection process, and FIG. 10(b) illustrates a two-step random connection process.
[0125] The random access process can be used for various purposes, such as initial access, uplink adjustment, resource allocation, handover, reconfiguration after a wireless link failure, and location measurement. Random access processes are classified into contention-based and dedicated (i.e., non-contention-based) processes. Contention-based random access processes are generally used for initial access, while dedicated random access processes are used for handover, when downlink data reaches the network, and when reconfiguring uplink synchronization for location measurement. In a contention-based random access process, the UE randomly selects a random access (RA) preamble. Therefore, it is possible for multiple UEs to transmit the same RA preamble simultaneously, which necessitates a subsequent contention resolution process. In contrast, in a dedicated random access process, the UE uses an RA preamble uniquely assigned to it by the BS. Consequently, the UE can perform the random access process without conflicts with other UEs.
[0126] Referring to FIG. 10(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.
[0127] - Step 1: The UE transmits the RA preamble via PRACH.
[0128] - Step 2: The UE receives a random access response (RAR) from the BS via PDSCH.
[0129] - Step 3: The UE transmits UL data to the BS via PUSCH based on RAR. Here, the UL data includes Layer 2 and / or Layer 3 messages.
[0130] - Step 4: The UE receives a contention resolution message from the BS via PDSCH.
[0131] The UE can receive information regarding random access from the BS through system information. For example, information regarding random access channel (RACH) times associated with SSBs on the cell may be provided through system information. The UE can select an SSB among those received on the cell for which the reference signal received power (RSRP) measured based on the SSB exceeds a threshold, and transmit an RA preamble through the 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 (e.g., RACH time) at which the random access preamble was transmitted and the random access 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 a L1 / L2 control channel (PDCCH) masked with a cyclic redundancy check (CRC) by a Random Access-RnTI (RA-RNTI) containing scheduling information for the RAR message within a preset time window (e.g., ra-ResponseWindow). If scheduling information is received through the PDCCH masked with the RA-RNTI, the UE may receive a RAR message from the PDCCH indicated by the scheduling information. Subsequently, the UE determines whether there is a RAR for itself in the RAR message. Whether a RAR for itself exists can be determined by whether a Random Access preamble ID (RAPID) exists for the preamble transmitted by the UE. The index of the preamble transmitted by the UE and the RAPID may be the same.A RAR includes a corresponding random access preamble index, timing offset information for UL synchronization (e.g., a timing advance command (TAC)), UL scheduling information for sending Msg3 (e.g., a UL grant), and temporary UE identification information (e.g., Temporary-C-RNTI, TC-RNTI). Upon receiving the RAR, the UE sends Msg3 via PUSCH according to the UL scheduling information and timing offset values within the RAR. Msg3 may include the UE's ID (or the UE's global ID). Additionally, 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 sends Msg4, a contention resolution message, to the UE. If the UE receives the contention resolution message and the contention is successfully resolved, TC-RNTI is changed to C-RNTI. Msg4 includes the UE's ID and / or It may include information related to the RRC connection (e.g., RRCSetup message). 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 report that the contention resolution failed and retransmit Msg3.
[0132] 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 by the UE by the BS using a PDCCH (hereinafter referred to as the PDCCH order) for commanding the transmission of an RA preamble.
[0133] - Step 0: BS assigns the RA preamble to the UE via dedicated signaling.
[0134] - Step 1: The UE transmits the RA preamble via PRACH.
[0135] - Step 2: The UE receives the RAR via the PDSCH from the BS.
[0136] The operations of steps 1 to 2 of a dedicated random access process may be the same as steps 1 to 2 of a contention-based random access process.
[0137] In NR systems, lower latency than in existing systems may be required. Additionally, a four-stage random access process may not be desirable, particularly for latency-sensitive services such as URLLC. A low-latency random access process may be required within various scenarios of NR systems. When the implementation(s) of this specification are performed with a random access process, to reduce latency in the random access process, the implementation(s) of this specification may be performed with the following two-stage random access process.
[0138] Referring to FIG. 10(b), the two-stage random access process may consist of two stages: the transmission of MsgA from the UE to the BS and the transmission of MsgB from the BS to the UE. The transmission of MsgA may include the transmission of an RA preamble via PRACH and the transmission of a UL payload via PUSCH. In the transmission of MsgA, PRACH and PUSCH may be transmitted using time division multiplexing (TDM). Alternatively, in the transmission of MsgA, PRACH and PUSCH may be transmitted using frequency division multiplexing (FDM).
[0139] A BS that receives MsgA may send MsgB to a UE. MsgB may include a RAR for said UE.
[0140] A message related to an RRC connection request (e.g., RRCSetupRequest message) requesting to establish a connection between the RRC layer of the BS and the RRC layer of the UE may be transmitted by being included in the payload of MsgA. In this case, MsgB may be used to transmit RRC connection-related information (e.g., RRCSetup message). Alternatively, the RRC connection request message (e.g., RRCSetupRequest message) may be transmitted via PUSCH transmitted based on a UL grant within MsgB. In this case, the RRC connection-related information (e.g., RRCSetup message) related to the RRC connection request may be transmitted via PDSCH associated with said PUSCH transmission after the PUSCH transmission based on MsgB.
[0141] The current standard document 3GPP TS 38.213 discloses the random access process and PRACH configuration as follows. For a more detailed description of the RRC parameters mentioned below, refer to 3GPP TS 38.331.
[0142] Prior to the initiation of the physical random access process, Layer 1 receives a set of SS / PBCH block indices from the upper layers and provides the corresponding set of RSRP measurements to the upper layers.
[0143] Prior to the initiation of the physical random access process, Layer 1 may receive an indication from the upper layers to perform a Type-1 random access process or a Type-2 random access process.
[0144] Prior to the initiation of the physical random access process, Layer 1 receives the following information from the upper layers:
[0145] - Physical Random Access Channel (PRACH) transmission parameters (PRACH preamble format, time resources, and frequency resources for PRACH transmission).
[0146] - Parameters for determining the root sequences within the PRACH preamble sequence set and their cylic shifts (index to logical root sequence table, cylic shifts (N CS ), and set type (unrestricted, restricted set A, or restricted set B)).
[0147] From a physical layer perspective, the type-1 L1 random access process includes the transmission of a random access preamble (Msg1) in a PRACH, a random access response (RAR) with a PDCCH / PDSCH (Msg2), and, when applicable, a PUSCH scheduled by a RAR UL grant, and a transmission of a PDSCH for contention resolution.
[0148] From a physical layer perspective, the above-mentioned type-2 L1 random access process includes a random access preamble in a PRACH and the transmission of a PUSCH (MsgA), the reception of a RAR message with a PDCCH / PDSCH (MsgB), and, if applicable, the transmission of a PDSCH for contention resolution with a PUSCH scheduled by a fallback RAR UL grant.
[0149] When a random access process for a UE is initiated by a PDCCH order, the PRACH transmission has the same subcarrier spacing (SCS) as the PRACH transmission initiated by the upper layers.
[0150] When a UE is configured to have two UL carriers for a serving cell and the UE detects a PDCCH command, the UE determines the UL carrier for the corresponding PRACH transmission using the UL / supplementary (supplementary UL, SUL) indicator field value from the detected PDCCH command.
[0151] The physical random access process for the UE is triggered upon a request for a PRACH transmission by upper layers or by a PDCCH command to the cell. Configuration by upper layers for a PRACH transmission includes the following:
[0152] - Settings for PRACH transmission on the above cell.
[0153] - Preamble Index, Preamble SCS, PRACH Target Reception Power P PRACH,target , when applicable, the corresponding RA-RNTI, PRACH resource for the above cell.
[0154] - If the UE would transmit the PRACH with repetitions, N for transmitting the PRACH rep preamble >1 Number of preamble iterations.
[0155] The UE, on the designated PRACH resource or N rep preamble For preamble iterations, use the same spatial filter to N rep preamble On a determined set of resources, transmission power P as described in Section 7.4 of 3GPP TS 38.214 PRACH,b,f,c(i) A UE transmits a PRACH on a cell using the selected PRACH format with transmission power P PRACH,b,f,c (i), as described in section 7.4 of 3GPP TS 38.214, on the indicated PRACH resource or on a determined set of N rep preamble resources using a same spatial filter in case of N rep preamble preamble repetitions.)
[0156] For a Type-1 random access process, the UE is provided by the RRC parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB with the number N of SS / PBCH block indexes associated with a single PRACH occasion and the number R of contention-based preambles per SS / PBCH block index per valid PRACH occasion.
[0157] In the case of a Type-1 random access process having a common configuration of PRACH times, the UE is provided with the number of SS / PBCH block indices N associated with one PRACH time by the RRC parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB and the number of contention-based preambles Q per SS / PBCH block index per valid PRACH time by the RRC parameter msgA-CB-PreamblesPerSSB-PerSharedRO. PRACH transmission may take place on a subset of PRACH times associated with the same SS / PBCH block index within an SSB-RO mapping cycle for a UE provided with a PRACH mask index by the RRC parameter msgA-SSB-SharedRO-MaskIndex in accordance with 3GPP TS 38.321.
[0158] For a Type-2 random access procedure with a separate configuration of PRACH occasions with a Type-1 random access procedure, the UE is provided with the number of SS / PBCH block indices N associated with one PRACH occasion and the number of contention-based preambles R per SS / PBCH block index per valid PRACH occasion, the number of SS / PBCH block indices N associated with one PRACH occation, by the RRC parameter msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB when provided, and otherwise by ssb-perRACH-OccasionAndCB-PreamblesPerSSB.
[0159] For a random access process associated with a feature combination indicated by the RRC information element FeatureCombinationPreambles (which associates a set of feature combinations with preambles), the UE is provided with the number of SS / PBCH block indices N associated with one PRACH time by the RRC parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB or, if provided, msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB, and the number of contention-based preambles S per SS / PBCH block index per valid PRACH time by the RRC parameter startPreambleForThisPartition and the RRC parameter numberOfPreamblesPerSSB-ForThisPartition. PRACH transmission is a PRACH associated with the same SS / PBCH block index within an SSB-RO mapping cycle for a UE provided with a PRACH mask index by ssb-SharedRO-MaskIndex in accordance with 3GPP TS 38.321. It can be done on subsets of periods.
[0160] For a Type-1 random access process, or for a Type-2 random access process having a separate configuration of PRACH periods from the Type-1 random access process, if N < 1, one SS / PBCH block index is mapped to 1 / N consecutive valid PRACH periods, and per valid PRACH period, R contention-based preambles with consecutive indices associated with the said SS / PBCH block index start from preamble index 0. If N ≥ 1, per valid PRACH period, R contention-based preambles with consecutive indices associated with the SS / PBCH block index n start from preamble index n*N total preamble Starting from / N, 0≤n≤N-1, and Ntotal preamble is provided by totalNumberOfRA-Preambles for a type-1 random connection process, or by msgA-TotalNumberOfRA-Preambles for a type-2 random connection process that has a separate configuration of PRACH times from the type-1 random connection process, and is an integer multiple of N.
[0161] For a Type-2 random access process having common settings for PRACH periods with a Type-1 random access process, if N < 1, a single SS / PBCH block index is mapped to 1 / N consecutive valid PRACH periods, and Q contention-based preambles having consecutive indices associated with the said SS / PBCH block index per valid PRACH period start from preamble index R. If N ≥ 1, Q contention-based preambles having consecutive indices associated with the SS / PBCH block index n per valid PRACH period start from preamble index n*N total preamble Starting from / N + R, where 0≤n≤N-1 and N total preamble The type-1 random connection process is provided by totalNumberOfRA-Preambles.
[0162] In the case of link recovery, the UE is provided with N SS / PBCH block indices associated with a single PRACH time by the RRC parameter ssb-perRACH-Occasion in the RRC configuration BeamFailureRecoveryConfig. In the case of a dedicated RACH configuration provided by the RRC configuration RACH-ConfigDedicated, if parameters cfra for contention-free random access (CFRA) to a given target cell are provided, the UE is provided with N SS / PBCH block indices associated with a single PRACH time by the parameter ssb-perRACH-Occasion regarding random access times for contention-free random access. If N < 1, a single SS / PBCH block index is mapped to 1 / N consecutive valid PRACH times. If N ≥ 1, all N consecutive SS / PBCH block indices are associated with a single PRACH time.
[0163] The SS / PBCH block indices provided by ssb-PositionsInBurst in SIB1 or RRC configuration ServingCellConfigCommon are mapped to valid PRACH times in the following order, and the parameters are described in 3GPP TS 38.211.
[0164] First, in the increasing order of preamble indices within a single PRACH period
[0165] Second, in increasing order of frequency resource indices for frequency-multiplexed PRACH periods
[0166] Third, in increasing order of time resource indices for time-multiplexed PRACH periods within the PRACH slot
[0167] Fourth, in increasing order of the indices for the PRACH slots
[0168] The association period, starting from frame 0, for mapping SS / PBCH block indexes to PRACH periods is N SSB Tx an association period, starting from frame 0, for mapping SS / PBCH block indexes to PRACH occasions is the smallest integer number in the set determined by the PRACH configuration period according to the following table such that N SSB Tx SS / PBCH block indexes are mapped at least once to the PRACH occasions within the association period), where UE is N from the value of ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon SSB Tx Gets.
[0169] The following table illustrates the mapping between the PRACH setting period and the association period between the SS / PBCH block and the PRACH occasion.
[0170]
[0171] In the case of a PRACH transmission by a UE triggered by a PDCCH command, if the value of the Random Connection Preamble Index field is not zero, the PRACH Mask Index field indicates the PRACH timing for said PRACH transmission, wherein the PRACH timings are associated with the SS / PBCH block index indicated by the SS / PBCH Block Index field of said PDCCH command, and if any, the Cell Indicator field indicates the cell for the PRACH transmission (see 3GPP TS 38.212). The UE K by the RRC parameter cellSpecificKoffset cell,offset If provided, the above PRACH time is slot n + 2 u ·K cell,offset After, and here n is T TA Assuming = 0, it is a slot in the UL BWP for a PRACH transmission that overlaps with the end of the PDCCH command reception, and u is the SCS setting for said PRACH transmission. If the PDCCH reception for a PDCCH command contains two PDCCH candidates from two linked sets of searchspaces based on the RRC parameter searchSpaceLinkingId used to link two searchspaces of the same type within the same BWP, the last symbol of said PDCCH reception is the last symbol of the PDCCH candidate that ends later, as described in Section 10.1 of 3GPP TS 38.213. said PDCCH reception contains said two PDCCH candidates even when the UE is not required to monitor one of said two PDCCH candidates, as described in Section 10 (excluding Section 10.4), 11.1, 11.1.1, and 17.2 of 3GPP 38.213.
[0172] In the case of a PRACH transmission triggered by upper layers, if the RRC parameter ssb-ResourceList is provided, the PRACH mask index is indicated by the RRC parameter ra-ssb-OccasionMaskIndex, which indicates the PRACH timing for the PRACH transmission.
[0173] PRACH periods are mapped consecutively per corresponding SS / PBCH block index. The indexing of the PRACH periods indicated by the mask index value is reset per mapping cycle of consecutive PRACH periods per SS / PBCH block index. Within the first available mapping cycle, the UE selects the PRACH period indicated by the PRACH mask index value for the indicated SS / PBCH block index for PRACH transmission.
[0174] For the preamble index indicated above, the ordering of the PRACH periods is
[0175] First, regarding the frequency-multiplexed PRACH periods, in increasing order of frequency resource indices
[0176] Second, regarding the time-multiplexed PRACH periods within the PRACH slot, in increasing order of time resource indices
[0177] Third, for the PRACH slots, in increasing order of the indices
[0178] N rep preamble For a PRACH transmission with multiple preamble repetitions, the set is continuous in time and uses the same frequency resources, and is associated with one or more identical SS / PBCH block index(s), N rep preambleIt consists of valid PRACH periods, and each SS / PBCH block index is associated with the same preamble index within all valid PRACH periods in the set.
[0179] In the case of a PRACH transmission with preamble repetitions, the time interval starting from frame 0 is the above N SSB Tx For a PRACH transmission with preamble repetitions, a time period, starting from frame 0, is the smallest integer number of association pattern periods such that at least one set of valid PRACH occasions for each of the N SS / PBCH block indices can be determined within the time period for all set number of preamble repetitions. SSB Tx SS / PBCH block indexes can be determined within the time period for all configured number of preamble repetitions. The set(s) of valid PRACH occasions for each configured number of preamble repetitions repeat every time period.
[0180] Within the time interval, N rep preamble N for PRACH transmission with dog preamble iterations rep preamble For a set of valid preamble iterations
[0181] The first valid PRACH time of the first set is the first valid PRACH time.
[0182] If any, the first valid PRACH time of the subsequent sets is determined according to the ordering of the valid PRACH times.
[0183] First, in increasing order of frequency resource indices for frequency-multiplexed PRACH periods
[0184] Second, in increasing order of the time resource indices of the time multiplexing PRACH periods
[0185] Here, for each frequency resource index for the frequency-multiplexed PRACH periods
[0186] The first valid PRACH time of the first set is the first valid PRACH time.
[0187] If any, the first valid PRACH time of the subsequent sets is
[0188] If the RRC parameter msg1-RepetitionTimeOffsetROGroup is provided, it is msg1-RepetitionTimeOffsetROGroup consecutive valid PRACH periods after the first valid PRACH period of the previous set, where each PRACH period is associated with the same SS / PBCH block index(s) and each SS / PBCH block index is associated with the same preambles.
[0189] If the RRC parameter msg1-RepetitionTimeOffsetROGroup is not provided, it is after the PRACH time of the previous set mentioned above.
[0190] In the case of a PRACH transmission triggered by a request from upper layers, if the RRC parameter csirs-ResourceList is provided, the value of the RRC parameter ra-OccasionList indicates a list of PRACH times for the PRACH transmission, wherein the PRACH times are associated with a selected CSI-RS index indicated by the RRC parameter csi-RS. The indexing of the PRACH times indicated by ra-OccasionList is reset for each associated pattern interval.
[0191] Below, physical channels that can be used in 3GPP-based wireless communication systems are described in more detail.
[0192] A PDCCH carries a DCI. For example, a PDCCH (i.e., a 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 the layer above the physical layer (hereinafter referred to as the upper layer) among the protocol stacks of the UE / BS, such as random access response (RAR) transmitted on the PDSCH, transmission power control commands, and the activation / deactivation of configured scheduling (CS). A DCI containing resource allocation information for the DL-SCH is also called a PDSCH scheduling DCI, and a DCI containing resource allocation information for the UL-SCH is also called a 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 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).
[0193] The scheduling of a PDCCH on one serving cell to a PDSCH or PUSCH on another serving cell is called cross-carrier scheduling. Cross-carrier scheduling using a carrier indicator field (CIF) may allow a PDCCH on a serving cell to schedule resources on another serving cell. Meanwhile, the scheduling of a PDSCH or PUSCH on a serving cell to a serving cell is called self-carrier scheduling. When cross-carrier scheduling is used in a cell, the BS may provide the UE with information regarding the cell scheduling said cell. For example, the BS may provide the UE with whether the serving cell is scheduled by a PDCCH on another (scheduling) cell or by said serving cell, and if said serving cell is scheduled by another (scheduling) cell, which cell signals downlink assignments and uplink grants for said serving cell. In this specification, a cell carrying a PDCCH is referred to as a scheduling cell, and a cell in which the transmission of a PUSCH or PDSCH is scheduled by a DCI included in the PDCCH, that is, a cell carrying a PUSCH or PDSCH scheduled by the PDCCH, is referred to as a scheduled cell.
[0194] PDSCH is a physical layer DL channel for DL data transport. PDSCH carries downlink data (e.g., DL-SCH transport blocks) and applies modulation methods such as QPSK (Quadrature Phase Shift Keying), 16 QAM (Quadrature Amplitude Modulation), 64 QAM, and 256 QAM. Codewords are generated by encoding transport blocks (TB). 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 a radio resource along with DMRS to generate an OFDM symbol signal, which is then transmitted through the corresponding antenna port.
[0195] The 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 resources 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. Uplink grant is dynamically received by the UE on the PDCCH or within the RAR, or is semi-persistently set to the UE by RRC signaling from the BS. Downlink assignment is dynamically received by the UE on the PDCCH, or is semi-persistently set to the UE by RRC signaling from the BS.
[0196] 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 available uplink grant(s) for UL transmission. Additionally, the BS can allocate uplink resources to the UE using configured grants. Two types of configured grants, Type 1 and Type 2, may be used. In the case of Type 1, the BS directly provides the configured uplink grant (including periodicity) via RRC signaling. In the case of Type 2, the BS sets the period of the RRC-configured uplink grant via RRC signaling and can signal and activate or deactivate the configured uplink grant via a PDCCH addressed to a configured scheduling RNTI (CS-RNTI). For example, in the case of Type 2, the PDCCH addressed by CS-RNTI indicates that the corresponding uplink grant may be implicitly reused according to the period set by RRC signaling until it is deactivated.
[0197] In DL, the BS can dynamically allocate downlink resources to the UE via PDCCH(s) addressed by C-RNTI. The UE monitors the PDCCH(s) to identify potential downlink assignments. Additionally, the BS can allocate downlink resources to the UE using semi-persistent scheduling (SPS). The BS can set the period of the configured downlink assignments via RRC signaling and signal, enable, or disable the configured downlink assignments via PDCCHs addressed by CS-RNTI. For example, a PDCCH addressed by CS-RNTI indicates that the corresponding downlink assignment may be implicitly reused according to the period set by RRC signaling until it is disabled.
[0198] In this specification, a PDSCH based on DL SPS is referred to as SPS PDSCH, a PUSCH based on a UL configured grant (CG) is referred to as CG PUSCH, a PDSCH dynamically scheduled by a DCI carried by a PDCCH is referred to as DG PDSCH, and a PUSCH dynamically scheduled by a DCI carried by a PDCCH is referred to as DG PUSCH.
[0199] Figure 11 illustrates an example of PDSCH time domain resource allocation by PDCCH and an example of PUSCH time domain resource allocation by PDCCH.
[0200] The DCI carried by PDCCH to schedule PDSCH or PUSCH includes a time domain resource assignment (TDRA) field, said TDRA field provides a value m for row index m+1 to the allocation table for PDSCH or PUSCH. A predefined default PDSCH time domain assignment is applied as the allocation table for PDSCH, or a PDSCH time domain resource assignment table set by BS via RRC signaling pdsch-TimeDomainAllocationList is applied as the allocation table for PDSCH. A predefined default PUSCH time domain assignment is applied as the allocation table for PUSCH, or a PUSCH time domain resource assignment table set by BS via RRC signaling pdsch-TimeDomainAllocationList is applied as the allocation table for 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).
[0201] In the PDSCH time domain resource settings, each indexed row defines the DL allocation-to-PDSCH slot offset K0, the start and length indicator value SLIV (or directly the starting position of the PDSCH within the slot (e.g., start symbol index S) and the allocation length (e.g., number of symbols L)), and the PDSCH mapping type. In the PUSCH time domain resource settings, each indexed row defines the UL grant-to-PUSCH slot offset K2, the starting position of the PUSCH within the slot (e.g., start symbol index S) and the allocation length (e.g., number of symbols L), and the PUSCH mapping type. K0 for PDSCH or K2 for PUSCH indicates the difference between the slot containing the PDSCH and the slot containing the PDSCH or PUSCH corresponding to said PDSCH. SLIV is a joint indicator of the starting symbol S relative to the start of the slot containing the PDSCH or PUSCH and the number of consecutive symbols L counted from said symbol S. For PDSCH / PUSCH mapping types, there are two mapping types: one is mapping type A and the other is mapping type B. In the case of PDSCH / PUSCH mapping type A, the demodulation reference signal (DMRS) is mapped to the PDSCH / PUSCH resource based on the start of the slot, and depending on other DMRS parameters, one or two symbols from the PDSCH / PUSCH resource may be used as DMRS symbol(s). For example, in the case of PDSCH / PUSCH mapping type A, the DMRS is located at the third symbol (symbol #2) or the fourth symbol (symbol #3) in the slot according to RRC signaling. In the case of PDSCH / PUSCH mapping type B, the DMRS is mapped based on the first OFDM symbol of the PDSCH / PUSCH resource, and depending on other DMRS parameters, one or two symbols starting from the first symbol of the PDSCH / PUSCH resource may be used as DMRS symbol(s).For example, in the case of PDSCH / PUSCH mapping type B, DMRS is located at the first symbol allocated for PDSCH / PUSCH. In this specification, PDSCH / PUSCH mapping types may be referred to as mapping types or DMRS mapping types. 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.
[0202] The above scheduling DCI includes a frequency domain resource assignment (FDRA) field that provides assignment information regarding resource blocks used for PDSCH or PUSCH. For example, the FDRA field provides the UE with information regarding a cell for PDSCH or PUSCH transmission, information regarding a BWP for PDSCH or PUSCH transmission, and information regarding resource blocks for PDSCH or PUSCH transmission.
[0203] A control resource set (CORESET), which is a set of time-frequency resources that allows the UE to monitor a PDCCH, may be defined and / or configured. The 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 upper-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 (also known as blind decoding) each PDCCH candidate according to the monitored DCI formats. The master information block (MIB) on the PBCH provides the UE with parameters for monitoring the PDCCH (e.g., CORESET#0 configuration) to schedule the PDCCH carrying the system information block (SIB1). The PBCH may also indicate that there is no associated SIB1; in this case, the UE may be instructed on a frequency range where it can assume there is no SSB associated with SSB1, as well as other frequencies to search for the SSB associated with SIB1. At least CORESET#0, which is the CORESET for scheduling SIB1, can be set via MIB or dedicated RRC signaling.
[0204] One or more CORESETs can be configured for the UE, and multiple CORESETs can overlap in the time / frequency domain.
[0205] The set of PDCCH candidates monitored by the UE is defined in terms of PDCCH search space sets. A search space set can be a common search space (CSS) set or a UE-specific search space (USS) set. Each CORESET setting is associated with one or more search space sets, and each search space set is associated with one CORESET setting.
[0206] A set of PDCCH candidates can be monitored in one or more CORESETs on an active DL BWP on each active serving cell where PDCCH monitoring is configured, wherein monitoring implies receiving each PDCCH candidate and decoding it according to the monitored DCI formats.
[0207] SS sets can be configured via system information (e.g., MIB) or UE-specific upper layer (e.g., RRC) signaling. Each DL BWP in a serving cell may have up to S (e.g., 10) SS sets configured. For example, the following parameters / information may be provided for each SS set. Each SS set is associated with one CORESET, and each CORESET configuration may be associated with one or more SS sets.
[0208] -searchSpaceId: Represents the ID of the SS set.
[0209] -controlResourceSetId: Represents the CORESET associated with the SS set.
[0210] -monitoringSlotPeriodicityAndOffset: Represents the PDCCH monitoring period interval (in slots) and the PDCCH monitoring interval offset (in slots).
[0211] -monitoringSymbolsWithinSlot: Represents the first OFDMA symbol(s) for PDCCH monitoring within the slot where PDCCH monitoring is enabled. It is indicated by a bitmap, where each bit corresponds to each OFDMA symbol within the slot. The MSB of the bitmap corresponds to the first OFDMA symbol within the slot. The OFDMA symbol(s) corresponding to bit(s) with a bit value of 1 correspond to the first symbol(s) of the CORESET within the slot.
[0212] -nrofCandidates: AL={1, 2, 4, 8, 16} represents the number of star PDCCH candidates (e.g., one of 0, 1, 2, 3, 4, 5, 6, 8).
[0213] -searchSpaceType: Indicates whether the SS type is CSS or USS.
[0214] - DCI Format: Indicates the DCI format of the PDCCH candidate.
[0215] Based on the CORESET / SS set configuration, the UE can monitor PDCCH candidates from one or more SS sets within the slot. The occasion (e.g., time / frequency resources) when PDCCH candidates must be monitored is defined as a PDCCH (monitoring) time. One or more PDCCH (monitoring) times can be configured within the slot.
[0216] The UE uses DRX to reduce power consumption. A UE operating based on DRX repeatedly switches ON / OFF for receiving operations. The characteristics of DRX, which is utilized for the purpose of reducing unnecessary power consumption of the UE, are as follows. DRX is defined with a structure for a UE in the RRC_IDLE state where an RRC connection between the UE and the BS is not set up (hereinafter referred to as I-DRX) and a structure for a UE in the RRC_CONNECTED state where an RRC connection between the UE and the BS is set up (hereinafter referred to as C-DRX). Both DRX structures are designed to reduce unnecessary power consumption in periods other than those defined by defining a period during which the UE can expect to receive a DL signal (e.g., an active time period or an on-duration period) to occur periodically. For reference, in the case of C-DRX, the Rel-16 standard states that the on-duration start position occurs periodically, and the size of the period that can be configured at this time (i.e., DRX cycle) can be determined / set through higher-level signaling, such as RRC signaling provided by the BS to the UE.
[0217] FIG. 12 illustrates a discontinuous reception (DRX) operation. In particular, FIG. 12 illustrates a DRX cycle for a UE in the RRC_CONNECTED state.
[0218] Referring to FIG. 12, the DRX cycle consists of an ON period and an Opportunity for DRX. The DRX cycle defines a time interval in which the ON period is periodically repeated, followed by a possible period of inactivity. The ON period represents the time interval during which the UE performs PDCCH monitoring to receive PDCCHs. When the DRX is set, the UE performs PDCCH monitoring during the ON period. If a PDCCH is successfully detected during the PDCCH monitoring, the UE activates the inactivity timer and remains awake. Conversely, if no PDCCH is successfully detected during the PDCCH monitoring, the UE enters a sleep state after the ON period ends. Thus, when the DRX is set, the UE may perform PDCCH monitoring / reception discontinuously in the time domain when performing the process and / or method according to the implementation(s) of this specification. For example, if DRX is set, the PDCCH reception occasion (e.g., a slot with a PDCCH seek space) in this specification may be set discontinuously according to the DRX setting. On the other hand, if DRX is not set, the UE may perform PDCCH monitoring / reception continuously in the time domain. For example, if DRX is not set, the PDCCH reception occasion (e.g., a slot with a PDCCH seek space) may be set continuously. Meanwhile, regardless of whether DRX is set, PDCCH monitoring may be restricted in time intervals set as measurement gaps. DRX setting information is received through upper layer (e.g., RRC) signaling, and whether DRX is ON / OFF is controlled by the DRX command of the MAC layer. When DRX is set, the UE may perform PDCCH monitoring discontinuously, as exemplified in FIG. 12.
[0219] The following table illustrates the UE process related to DRX. Referring to the table, DRX configuration information is received via upper layer (e.g., RRC) signaling, and whether DRX is ON / OFF is controlled by DRX commands at the MAC layer. When DRX is configured, the UE can perform discontinuous PDCCH monitoring, as illustrated in FIG. 12.
[0220]
[0221] Here, MAC-CellGroupConfig includes configuration information necessary to set MAC parameters for a cell group. MAC-CellGroupConfig may also include configuration information regarding DRX. For example, MAC-CellGroupConfig may include information related to DRX as follows.
[0222] - Value ofdrx-onDurationTimer: Sets the duration at the start of the DRX cycle.
[0223] - Value ofdrx-SlotOffset: Sets the delay before starting drx-onDurationTimer.
[0224] - Value ofdrx-InactivityTimer: Sets a period after the PDCCH time when there is a PDCCH that directs a new UL or DL transmission for the MAC entity.
[0225] - Value ofdrxRetransmissionTimerDL(per DL HARQ process except for the broadcast process): Sets the maximum duration until a DL retransmission is received.
[0226] - Value ofdrxRetransmissionTimerUL(per UL HARQ process): Sets the maximum duration until a grant for UL retransmission is received.
[0227] - Value ofdrx-HARQ-RTT-TimerDL(per DL HARQ process except for the broadcast process): Sets the maximum period from when the initial DL transmission is received until a DL assignment for HARQ retransmission is received.
[0228] - Value ofdrx-HARQ-RTT-TimerUL(per UL HARQ process): Sets the maximum period from when a grant for an initial UL transmission is received until a grant for a UL retransmission is received.
[0229] -drx-LongCycleStartOffset: Sets the Long DRX cycle and drx-StartOffset, defining the subframe where the Long and Short DRX cycles start.
[0230] -drx-ShortCycle(optional): Sets Short DRX cycle.
[0231] -drx-ShortCycleTimer(optional): Sets the duration for which the UE must follow the Short DRX cycle. For example, a value in multiples of the Short DRX cycle can be set by drx-CycleTimer. For example, the value of n can correspond to n*drx-ShortCycle.
[0232] The UE may perform PDCCH monitoring on serving cells within the DRX group if the DRX group is within the active time. Here, the DRX group is a group of serving cells configured by the RRC and having the same DRX active time. Here, the active time is the total duration during which the UE monitors the PDCCH, and may include the ON period of the DRX cycle, the time during which the UE performs continuous reception while the inactivity timer has not expired, and the time during which the UE performs continuous reception while waiting for a retransmission opportunity. For example, when the DRX is configured, the active time for serving cells within the DRX group is i) when the drx-onDurationTimer or drx-InactivityTimer configured for the DRX group is running; or ii) when the drx-RetransmissionTimerDL or drx-RetransmissionTimerUL is running on any serving cell within the DRX group; or ra-ContentionResolutionTimer or msgB-RsponseWindow is running; or may include a time when a PDCCH directing a new transmission addressed to a C-RNTI addressed to the UE's MAC entity is not received after the successful reception of a random access response for a random access preamble that was not selected by the MAC entity among the contention-based random access preambles.
[0233] The UE may receive one or more DRX groups through RRC signaling from the BS. For example, if two DRX groups are set, each serving cell is uniquely assigned to one of the two DRX groups. The DRX parameters drx-onDurationTimer and drx-InactivityTimer are set 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 the serving cell is associated with only one set of DRX parameters.
[0234] Energy conservation in BSs is considered important in wireless communication systems, including 3GPP, because it can contribute to building eco-friendly networks by reducing carbon emissions and lowering the operational expenditure (OPEX) of telecommunication operators. In particular, as the introduction of 5G communication requires high transmission rates, BSs must equip a larger number of antennas and provide services through wider bandwidths and frequency bands. As a result, energy costs for BSs have reportedly reached 20% of total OPEX, according to recent studies. Due to this increased interest in BS energy conservation, a new study item titled "study on network energy savings" was approved in 3GPP NR release 18. For example, to improve energy saving capabilities in terms of transmission and reception of BS, this study investigates how to achieve more efficient operation of transmission and / or reception with one or more network energy saving techniques in time, frequency, space, and power domains, dynamically and / or semi-statically, and with finer granularity adaptation, using potential support / feedback and potential UE support information of the UE.
[0235] The following enhancement techniques may be considered.
[0236] Specify SSB-less SCell operation for inter-band CA for FR1 and co-located cells, where a UE measures SSB transmitted on PCell or another SCell for an SCell's time / frequency synchronization (including downlink AGC), and L1 / L3 measurements, including potential enhancement on SCell activation procedures if necessary.
[0237] Specify enhancement on cell DTX / DRX mechanism including the alignment of cell DTX / DRX and UE DRX in RRC_CONNECTED mode, and inter-node information exchange on cell DTX / DRX
[0238] Specify the following techniques in spatial and power domains
[0239] Specify necessary enhancements on CSI and beam management related procedures, including measurement and report, and signaling, to enable efficient adaptation of spatial elements (e.g., antenna ports, active transceiver chains).
[0240] Specify necessary enhancements on CSI-related procedures, including measurement and report, and signaling, to enable efficient adaptation of power offset values between PDSCH and CSI-RS.
[0241] Specify mechanism(s) to prevent legacy UEs camping on cells adopting the Rel-18 NES techniques, if necessary.
[0242] Specify conditional handover (CHO) procedure enhancement(s) in case source / target cell is in NES mode.
[0243] Specify inter-node beam activation and enhancements on restricting paging in a limited area.
[0244] If necessary, specify the corresponding radio resource management / radio frequency (RRM / RF) core requirements for the above features.
[0245] BS can apply techniques such as adjusting the on / off duration in the time axis for NES purposes, adjusting transmit / receive resources for UE-common or UE-specific signals / channels, changing the amount of resources in the frequency axis, adjusting the transmission power, or turning on / off antenna port(s) or TRP(s), etc. in the spatial domain. The state in which such techniques(s) (hereinafter referred to as NES_tech for convenience) are applied is called NES mode or NES state.
[0246] Figure 13 illustrates the operation procedure in a BS that supports network energy saving (NES) technology.
[0247] Referring to FIG. 13, the BS identifies or determines the NES solution(s) to be applied (S1301). The NES solution(s) may be related to the control of signal transmission / reception (e.g., on / off), beam operation, handover procedures, channel measurement and reporting, etc. Which NES solution(s) to apply may be adaptedly selected based on the current situation (e.g., cell load level, characteristics of connected UEs, etc.) or may be predefined. The BS that has identified (or determined) the NES solution(s) may perform signaling for the NES (S1303). The specific signaling procedure may vary depending on the identified NES solution(s). For example, the BS may transmit common information regarding the NES solution(s), transmit configuration information necessary for NES operation to at least one UE, or transmit control information regarding the progress of NES operation to at least one UE. Additionally, the BS may receive capability information related to the NES from at least one UE. Afterward, BS can perform operations for NES (S1305). At this time, BS can perform operations for NES based on the signaling performed earlier. For example, depending on the system information, configuration information, and control information transmitted through the signaling, BS can turn on or off the transmission / reception of a specific signal, turn on / off elements of the spatial domain, or adjust resources for the transmission / reception of a measurement signal.
[0248] NES technology can be performed through a procedure as shown in Fig. 13. Examples of NES solutions that can be performed by a procedure as shown in Fig. 13 are as follows.
[0249] Intra-system energy saving solution: A radio access network (RAN) node may request a neighbor RAN node to switch at least one SSB beam into its deactivated cell, or perform paging using a limited set of beams to an inactive UE (e.g., stationary UE).
[0250] Inter-system energy saving solution: An NG-RAN node owning a capacity booster cell can autonomously switch the cell to an inactive state.
[0251] > SSB-less SCell solution: If an SSB measurement timing configuration (SMTC), which is an SSB-based radio resource management (RRM) measurement timing configuration, is not provided for the SCell, the UE can obtain timing reference and automatic gain control (AGC) sources from other serving cells. In FR1 or FR2, the BS can set up intra-band carrier aggregation (CA) or inter-band CA including the SCell without SSB transmission, in which case SSB / SIB transmission can be triggered by the UE's wake-up signal (WUS). Accordingly, as the periododicity of common channels / signals such as SSB increases, the BS can remain in a sleep state for a longer time.
[0252] Cell DTX / DRX Solution: To reduce the downlink transmission / uplink reception active time of a BS, periodic cell DTX / DRX patterns (e.g., active and inactive periods) may be configured commonly for UEs within a cell having the corresponding feature. Here, the cell DTX pattern and the cell DRX pattern may be configured and activated separately, and up to two cell DTX / DRX patterns may be configured per MAC entity. When cell DTX is configured and activated, at least one of monitoring for semi-persistent scheduling (SPS) occasions or PDCCH monitoring may be suspended during the cell DTX inactive period. When cell DRX is configured and activated, at least one of transmission or scheduling request (SR) transmission from a configured grant (CG) resource may be suspended during the cell DRX inactive period. Cell DTX / DRX can be enabled / disabled via RRC signaling or L1 group common signaling (e.g., PDCCH over CSS). Parameters such as active duration and cycle can be set for Cell DTX / DRX. The active duration is the period during which the UE waits to transmit an SR or CG after receiving a PDCCH or SPS occasion, and the cycle specifies the periodic repetition of the active and inactive periods. When both Cell DTX and Cell DRX are enabled, parameters such as the active duration and cycle are common.If the BS detects an emergency call or a public safety-related service (e.g., multimedia priority service (MPS) or mission critical service (MCS)), the network may release or deactivate the cell DTX / DRX settings so as not to affect the service. Additionally, at least some overlap is required between the active period of the UE's connected mode DRX and the active period of the cell DTX / DRX. For example, the UE's connected mode DRX periododicity may be a multiple of the cell DTX / DRX periododicity, or vice versa.
[0253] Conditional Handover (CHO) Solution: A CHO procedure, performed in such a way that the execution of a handover is determined by the UE, is used while NES technology is applied (e.g., when a cell enables or disables Cell DTX / DRX). In this case, the UE may use NES-specific CHO events to execute a CHO for a candidate cell, and as an additional triggering condition for this, the reception of a DCI that enables CHO condition(s) set as NES event indications may be applied.
[0254] Spatial and power domain adaptation solution: To support BS for transceiver muting and / or transmission power adaptation, the UE can be configured to report multiple CSI entries in CSI reporting based on multiple sub-configurations. Each sub-configuration can correspond to a spatial domain adaptation pattern (e.g., a subset of available spatial elements) and / or a data channel (e.g., PDSCH) and power offset between CSI-RS. Depending on the application of the spatial and power domain adaptation solution, CSI configuration, measurement, and / or reporting behavior may be affected.
[0255] Figure 14 is an example of a process for carrier aggregation (CA) operation using an SSB-less secondary cell (SCell).
[0256] Referring to FIG. 14, the BS can transmit configuration information for SCells to be aggregated through a SCell already configured to the PCell or UE (S1401). For example, the BS can transmit configuration information for CA to provide services to the UE through a CA operation. Here, the CA operation may be an intra-band CA or an inter-band CA. For example, the configuration information for a SCell may include information containing information for adding a SCell (e.g., sCellToAddModList), and specifically, may include a cell index, a physical cell identifier, information related to DL-UL configuration, information related to BWP, information related to cell DTX / DRX, information related to downlink frequency (e.g., FrequencyInfoDL), etc. Subsequently, the UE determines the configuration for the CA operation (S1403) and can perform communication using the BS's PCell and SCell (S1405a, S1405b). In some implementations, the UE can determine that the SCell is an SSB-less SCell based on information related to the downlink frequency included in the configuration information and can check the relevant parameters. For example, the UE can determine that the SCell is an SSB-less SCell by checking for the presence of a parameter indicating that it is an SSB-less SCell (e.g., SSBlessSCell) and can determine the timing reference and AGC source for the SCell based on information about the reference cell (e.g., referenceCell). In the example of FIG. 14, the reference cell may be a PCell. In this case, the UE can use the PCell as the timing reference and AGC source for communication in the SCell.
[0257] The following table illustrates a portion of the RRC information element (IE) FrequencyInfoDL, which provides the downlink carrier and the basic parameters of transmission on said downlink carrier.
[0258]
[0259] The above IEFrequencyInfoDL may be included in the RRC configuration DownlinkConfigCommon or DownlinkConfigCommonSIB, which provides common downlink parameters for the cell.
[0260] In the table above, the field absoluteFrequencySSB indicates the frequency of the SSB to be used for this serving cell, and SSB-related parameters provided for the serving cell (e.g., SSB index) refer to this SSB frequency unless otherwise noted. The cell-defining SSB (CD-SSB) of the PCell is always on the sync raster. If frequencies are identifiable by their GSCN values, they are considered to be on the sync raster. If the field absoluteFrequencySSB is absent in the IEFrequencyInfoDL, the SSB-related parameters (e.g., ssb-PositionsInBurst, ssb-periodicityServingCell, and subcarrierSpacing in ServingCellConfigCommonIE) are absent. If the above field absoluteFrequencySSB is absent, the UE may obtain a timing reference from an applicable SpCell or SCell, from the SpCell or SCell indicated by the referenceCell, or from a default cell. This is supported when the SCell from which the UE obtains the timing reference is within the same or different frequency band as the cell from which the UE obtains the timing reference (e.g., the respective SpCell or SCell).
[0261] In the table above, the field referenceCell can indicate a reference cell, which is a cell that provides timing references and AGC sources for SCells without SSB. If the reference cell is an SCell or PSCell, it is an active SCell or active PSCell. If this field is absent, the default cell is the reference cell.
[0262] On-demand SSB
[0263] In some implementations, a method to reduce energy consumption may be considered in which the BS transmits an SSB on a specific cell through an on-demand SSB process, and does not transmit an SSB on said specific cell when there is no on-demand SSB process. For convenience, SSBs transmitted for a certain period or interval upon request by a UE are referred to as on-demand SSBs below. In existing NR systems, it was difficult to reduce energy consumption even when the BS had no data to receive or send, as SSBs had to be transmitted periodically at all times for purposes such as time / frequency synchronization or RRM measurement. Considering this, in some implementations, BS energy consumption can be reduced by allowing the BS to refrain from transmitting SSBs and only transmit them when an on-demand SSB process is involved. The above on-demand SSB process can be triggered through one of the following methods.
[0264] 1) The UE requests the BS's SSB transmission by transmitting an uplink signal / channel (e.g., PRACH, PUCCH, PUSCH, SRS, etc. in 3GPP-based systems);
[0265] 2) Requesting the transmission of the SSB from BS (or TRP) #1 to BS (or TRP) #2 via an interface between BSs (e.g., Xn interface in NR-based systems) or backhaul signaling; or
[0266] 3) Signal whether SSB is transmitted for the corresponding SCell through SCell enable / disable (enable / disable) signaling.
[0267] Considering coexistence with UEs according to existing NR standards, some scenarios (e.g., 3GPP Release 19) may be limited to on-demand SSB operations for connected mode UEs and SCells. However, in future releases or next-generation communication systems, on-demand SSB operations (for SSB transmission on a PCell) may be defined for inactive or idle mode UEs or initial connection UEs. Additionally, CA including the SCell may be applied to both intra-band CA and inter-band CA, and the SSB on the SCell transmitted through the on-demand SSB process may be utilized for at least time / frequency synchronization, layer 1 (L1) / layer 3 (L3) measurement, and SCell activation.
[0268] SIB1 transmission on demand
[0269] Some implementations of this specification related to on-demand SIB1 are described in more detail below. Hereinafter, a PDCCH carrying a DCI that schedules a SIB1 transmission (e.g., a PDSCH transmission carrying SIB1) is referred to as a SIB1 PDCCH or a SIB1-related PDCCH, and a PDSCH carrying SIB1 is referred to as a SIB1 PDSCH or a SIB1-related PDSCH.
[0270] In some implementations, a method to reduce energy consumption may be considered in which the BS transmits an on-demand SIB1 for a specific cell through an on-demand SIB1 process, and does not transmit the SIB1 for that cell when there is no on-demand SIB1 process. For convenience, the SIB1 transmitted for a certain period or interval upon request by a UE is referred to as an on-demand SIB1 below. In existing NR systems, it was difficult to reduce energy consumption even when the BS had no data to receive or send, because it was always necessary to periodically provide SIB1s containing system information and random connection information for UEs in initial connection or idle mode to connect to a cell. Considering this, some implementations allow the BS to refrain from transmitting SIB1s and only perform transmissions when an on-demand SIB1 process is involved, thereby reducing BS energy consumption. During this on-demand SIB1 process, the BS's SIB1 transmission can be triggered by the UE transmitting an uplink signal / channel (e.g., PRACH in 3GPP-based systems).
[0271] FIGS. 15 through 17 illustrate custom SIB1 transmission scenarios related to some implementations of the present specification.
[0272] The following scenarios may be considered in relation to custom SIB1 transmission according to some implementations of this specification, but some implementations of this specification may not be limited to the following scenarios.
[0273] 1) Scenario 1: As illustrated in FIG. 15, a UE that receives an SSB (and / or other downlink signal / channel) at Cell #1 and recognizes that SIB1 is not being transmitted on Cell #1 can trigger the transmission of SIB1 by transmitting a signal requesting SIB1 (hereinafter, for convenience, a wake-up signal (WUS)) based on information provided by the SSB (and / or other downlink signal / channel) and / or predetermined information. A BS that receives the WUS can transmit a specific DL signal / channel on Cell #1 (corresponding to an ACK for the WUS) in response, or transmit SIB1 on Cell #1 (or without transmitting the DL signal / channel).
[0274] 2) Scenario 2: As illustrated in FIG. 16, a UE that receives an SSB (and / or other downlink signal / channel such as SIB1) at Cell #1 and realizes that SIB1 is not being transmitted on Cell #2 may attempt to camp-on through Cell #2. The UE may trigger the transmission of SIB1 to Cell #2 by transmitting a signal (e.g., WUS) requesting SIB1 on Cell #1 based on the information provided by the received SSB (and / or other downlink signal / channel such as SIB1) and / or predetermined information. A BS that receives the WUS may, in response, transmit a specific DL signal / channel (corresponding to an ACK for the WUS) on Cell #1 or Cell #2, or transmit SIB1 to Cell #2 on Cell #1 or Cell #2 (or without transmitting the DL signal / channel).
[0275] 3) Scenario 3: As illustrated in FIG. 17, a UE that receives an SSB (and / or other downlink signal / channel such as SIB1) at Cell #1 and realizes that SIB1 is not being transmitted on Cell #2 may attempt to camp-on through Cell #2. The UE may trigger the transmission of SIB1 for Cell #2 by transmitting a signal (e.g., WUS) requesting SIB1 on Cell #2 based on the information provided in the received SSB (and / or other downlink signal / channel such as SIB1) and / or predetermined information. A BS that receives the WUS may, in response, transmit a specific DL signal / channel (corresponding to an ACK for the WUS) on Cell #1 or Cell #2, or transmit SIB1 for Cell #2 on Cell #1 or Cell #2 (or without transmitting the DL signal / channel).
[0276] In cases where multiple cells are involved for on-demand SIB1 operation, as in the above scenarios 2 or 3, Cell #1 and Cell #2 can be defined as follows.
[0277] - Cell A (= Cell#1): A cell that is periodically transmitting at least its own SIB1.
[0278] - NES cell (= Cell#2): A cell that may transmit SIB1 in response to UL WUS from a UE.
[0279] For example, Cell A may refer to a cell where SIB1 information for that cell is periodically transmitted over that cell, and may also be expressed as Cell #1 or an anchor cell. Additionally, NES cell may refer to a cell where SIB1 is provided in response to an uplink WUS from the UE, and may also be expressed as Cell #2 or a non-anchor cell.
[0280] The UE can discover a cell and recognize that the cell is an NES cell (requiring on-demand SIB1 operation) through at least one or a combination of the following methods.
[0281] - The UE can recognize that it is an NES cell through the SIB and / or WUS configuration information (provided by Cell A).
[0282] - The UE can identify that it is an NES cell through information such as the center frequency of the PBCH / MIB / SSB (received from the NES cell).
[0283] - The UE can identify an NES cell through the DCI (received from the NES cell). The DCI can be received in the CORESET / scan space configured via the PBCH, MIB, or SSB (received from the NES cell). Additionally, a separate RNTI value for the DCI can be pre-configured / defined.
[0284] - If the UE attempts to receive SIB1 of the cell but fails to receive SIB1 for a certain period of time or longer, it can recognize that it is an NES cell.
[0285] Meanwhile, the UE may receive configuration for an uplink WUS requesting SIB1 for an NES cell through at least one of the following methods or a combination thereof.
[0286] - RRC messages transmitted from Cell A (e.g., SIB1 or other system information block, RRC release message),
[0287] - DCI transmitted over Cell A or NES cell,
[0288] - Msg2 / Msg4 (via the 4-stage random access process) or MsgB (via the 2-stage random access process) transmitted from Cell A
[0289] - The center frequency of the PBCH / MIB / SSB transmitted over the NES cell, or
[0290] - Information that is pre-defined / pre-configured in the specification.
[0291] In the description of some implementations of this specification, "frequency band" may be replaced with band, carrier, serving cell, BWP, etc.
[0292] Paging
[0293] Figure 18 illustrates paging times according to several scenarios. In particular, Figure 18 illustrates paging times according to the current NR standard.
[0294] If the UE does not have any data transmissions / receptions in progress, the UE enters RRC_IDLE or RRC_INACTIVE to save power. When DL data for the UE arrives at the network, the network sends a paging message (e.g., paging DCI) at a paging occasion (PO) to trigger the RRC setup procedure, RRC Connection Resume procedure, etc. A PO is a set of PDCCH monitoring occasions and may consist of multiple time slots (e.g., subframes or OFDM symbols), and a DCI with a CRC scrambled from the PO to the P-RNTI may be transmitted. For example, PO is a set of 'S*X' consecutive PDCCH monitoring times, where 'S' is the number of actually transmitted SSBs determined by the parameter ssb-PositionsInBurst in SIB1, and 'X' is nrofPDCCH-MonitoringOccasionPerSSB-InPO if set and equal to 1 otherwise. The parameter ssb-PositionsInBurst indicates the time domain indications of SSBs transmitted within a half frame containing SS / PBCH blocks, and the parameter nrofPDCCH-MonitoringOccasionPerSSB-InPO indicates the number of PDCCH monitoring times corresponding to SSBs within the paging time.
[0295] Qausi Co-Location (QCL)
[0296] QCL refers to the relationship established between two antenna ports when the large-scale channel properties experienced by a symbol transmitted to one antenna port can be inferred from the channel properties experienced by a symbol transmitted to the other antenna port. QCL is introduced to enable the UE to infer the large-scale channel properties of a signal received at a specific antenna port from the channel properties of the other antenna port that have already been measured. The large-scale channel properties that two antenna ports can share may include one or more of the following: delay spread, Doppler spread, Doppler shift, average delay, and spatial Rx parameter. The QCL types corresponding to each DL RS can be provided by the RRC parameter qcl-Type within the RRC setting QCL-Info and can take one of the following four values.
[0297] > 'typeA': {Doppler shift, Doppler spread, average delay, delay spread},
[0298] > 'typeB': {Doppler shift, Doppler spread},
[0299] > 'typeC': {Doppler shift, average delay},
[0300] > 'typeD': {Spatial Rx parameter}
[0301] For any DL RS antenna port(s), a first DL RS may be set as a reference to QCL type X (X = A, B, C, or D), and additionally, a second DL RS may be set as a reference to QCL type Y (Y = A, B, C, or D but X).
[0302] The BS can indicate the QCL type between the DL RS and the DM-RS port of the PDSCH or PDCCH through the transmission configuration indicator (TCI) state setting, and based on this, the UE can determine which Doppler and delay characteristics or receive beam to apply when receiving a DL signal. A single TCI state includes the QCL relationship between one or more DL RSs, such as the DM-RS port(s) of the PDSCH, the DM-RS port(s) of the PDCCH, and the CSI-RS port(s) of the CSI-RS resource. For 'Transmission Configuration Indication' among the fields within the DCI that schedules the PDSCH, the TCI state index corresponding to each code point constituting that field is activated by the MAC CE. The TCI state setting for each TCI state index is configured via RRC signaling. In Release-16 NR systems, the corresponding TCI state is configured between DL RSs, but in future releases, configuration between a DL RS and a UL RS, or between UL RSs and UL RSs, may be permitted. For example, SRS, PUSCH DM-RS, or PUCCH DM-RS, etc., may be UL RS related to the TCI state.
[0303] Cell DTX / DRX
[0304] To reduce the BS downlink transmission / uplink reception active time, the UE may be configured with periodic cell DTX / DRX patterns (e.g., active and inactive intervals). For example, the BS may perform cell DTX / DRX operations and transmit configuration information related to said cell DTX / DRX operations to the UE. For example, the BS may provide the BS with an RRC information element (IE) CellDTXDRX-Config containing the following cell DTX / DRX related parameters.
[0305]
[0306] Additionally, the cell DTX / DRX related configuration information may further include information for receiving and interpreting control information related to the cell DRX / DRX (e.g., DCI related information). For example, the following parameters may be provided to the UE by the BS through IEPhysicalCellGroupConfig, which is used to set cell-group specific layer 1 (L1) parameters.
[0307]
[0308] IECellDTXDRX-Config may be provided through IEServingCellConfig, which is used to set the UE as a serving cell, and may be provided with a parameter positionInDCI-cellDTRX regarding the position of the start bit of the information block of DCI format 2_0 for said serving cell.
[0309]
[0310] Subsequently, the BS may transmit control information related to cell DTX / DRX to the UE. The control information related to cell DTX / DRX may be transmitted via a specified format (e.g., DCI format 2_9). If the operation for a serving cell according to at least one of the cell DTX operation and cell DRX operation is configured by the configuration information (e.g., IEcellDTXDRX-Config), the UE may identify a set of search spaces (e.g., Type3-PDCCH CSS set) for monitoring the PDCCH that transmits control information in the specified format during the active time via a UE upper-level parameter (e.g., IESearchSpace), and obtain the location of information regarding the serving cell within the control information via an upper-level parameter (e.g., positionInDCI-cellDTRX). Then, the UE may obtain the control information based on the identified set of search spaces and location. Control information related to cell DTX / DRX may be used to indicate the activation or deactivation of cell DTX and / or cell DRX, and / or to provide an NES-mode indicator, and may include, for example, at least one block including a cell DTX / DRX indicator and an NES-mode indicator. In this case, if the serving cell is set as a supplementary uplink (SUL) carrier, the indication of activation or deactivation of cell DRX by the cell DTX / DRX indicator may be applied to both the UL carrier and the SUL carrier.
[0311] Referring to 3GPP TS 38.212, DCI format 2_9 is used to enable or disable cell DTX and / or DRX settings of one or more serving cells for one or more UEs and / or to provide NES-mode indications of the primary cell for one or more UEs. The following information may be transmitted via DCI format 2_0 with a CRC scrambled by cellDTRX-RNTI:
[0312] - Block number 1, Block number 2, ..., Block number N
[0313] Here, the starting position of the block associated with the serving cell is determined by the RRC parameter positionInDCI-cellDTRX provided by the upper layer.
[0314] When the UE is configured to monitor DCI format 2_9 with a CRC scrambled by cellDTRX-RNTI, one or more blocks are configured for the UE via upper-layer signaling for DCI format 2_9 with a CRC scrambled by cellDTRX-RNTI, and for each block, the following fields are defined: i) a cell DTX / DRX instruction field used to indicate the activation (or deactivation) of the cell DTX and / or cell DRX if the upper-layer (e.g., RRC) parameter cellDTX-DRX-L1activation is configured; ii) an NES-mode instruction field used to indicate NES-specific CHO execution conditions if the upper-layer parameter nesEvent is configured and the associated serving cell of the block is a primary cell. The cell DTX / DRX indicator field is: i) 2 bits having the most significant bit (MSB) corresponding to the cell DTX setting and the least significant bit (LSB) corresponding to the cell DRX setting, if the upper layer parameter cellDTX-DRX-L1activation is set and cellDTXDRXconfigType is set to dtxdrx for the associated serving cell of that block; ii) 1 bit if the upper layer parameter cellDTX-DRX-L1activation is set and cellDTXDRXconfigType is set to dtx or drx for the associated serving cell of that block; and if the upper layer parameter nesEvent is set and the associated serving cell of that block is a primary cell, the NES-mode indicator field is 1 bit.
[0315] When the cell DTX / DRX setting is enabled for a cell, the UE and BS can communicate on the cell based on the cell DTX / DRX.
[0316] Existing cell DTX and / or cell DRX operations are composed of a repetitive pattern of active / inactive periods, and were introduced for the purpose of improving the energy saving effect of BS by not performing transmission of BS (e.g., transmission in a specific DCI format, periodic / semi-persistent CSI-RS transmission, etc.) or receiving of BS (e.g., periodic / semi-persistent CSI reporting, scheduling request (SR), etc.) during the inactive period. However, in the case of existing cell DTX / DRX operations, in order to support UE IDLE / INACTIVE state operations (e.g., initial access, random access procedure, paging, etc.) without problems, the BS must still support transmission / reception operations (e.g., SSB transmission, system information (SI) transmission, paging transmission, PRACH reception, etc.) to support UEs in the IDLE / INACTIVE state even during inactive periods. This has the disadvantage that it is difficult to maximize the energy saving effect of the BS.
[0317] Therefore, some implementations of this specification to address these issues are described below. In some implementations of this specification, cell DTX and / or cell DRX operations may consist of repeating patterns of the following three states. The names of each of the following three intervals are merely examples, and the names of the three intervals may not be identical to those below.
[0318] Active section
[0319] semi-active section
[0320] inactive section
[0321] For example, in some implementations of this specification, operations to support UEs in an idle / inactive state during the semi-active period may be supported to the maximum extent, while operations to support UEs in that state during the inactive period may be minimized or not supported. Alternatively, in some implementations of this specification, broadcast signals / channels or common signals / channels may be aggregated and transmitted along the time axis (e.g., clustered transmission) during the semi-active period, thereby minimizing the time for the BS to wake up and transmit / receive signals / channels. As a result, the BS can improve energy savings from the transition to a deep sleep state by concentrating such operations during the semi-active period (instead of periodically waking up and performing transmit / receive operations to support UEs in an idle / inactive state even when not in an active state) and not performing such operations during the inactive state.
[0322] For the purpose of saving energy in the BS, operation of the BS in an energy efficient (EE) mode or in a low power (LP) mode may be considered. Compared to the normal mode of the BS, the BS in EE / LP mode may have at least the following operational differences.
[0323] The number of transmitting and / or receiving (active) antenna elements (or antenna ports or TxRUs) utilized in the EE / LP mode of the BS may be smaller than the number of transmitting and / or receiving (active) antenna elements (or antenna ports or TxRUs) utilized in the general mode of the BS.
[0324] Compared to the normal mode operation of BS, radio frequency (RF) and / or baseband processing may be relaxed during EE / LP mode operation. For example, frequency domain processing such as fast Fourier transform (FFT) / inverse fast Fourier transform (IFFT) may not be performed.
[0325] If, as assumed above, the EE / LP mode BS utilizes relatively fewer (active) antennas or has relaxed processing, the coverage may be reduced compared to normal mode operation. To minimize this difference in coverage depending on the BS mode (or to maintain cell coverage at a similar level regardless of which mode the BS operates in), the method of transmitting or receiving the channel may differ depending on the operating mode of the BS.
[0326] In addition, even if the BS operates in EE / LP mode, it can be assumed that the BS is capable of transmitting and / or receiving specific signals (e.g., predefined sequences, synchronization signals such as PSS / SSS, PBCH, PRACH, etc.).
[0327] The section where the above BS is operating in normal mode may be replaced with an active section according to some implementations of this specification, or the section where the BS is operating in EE / LP mode may be replaced with a semi-active section according to some implementations of this specification.
[0328] In some implementations of this specification, “cell DTX and / or DRX operation” may mean an operation in which a time pattern consisting of one or more periods, such as an active period, an inactive period, or a semi-active period, is repeated periodically. Such operation may be configured cell-specifically (or as UE-common or UE-group common).
[0329] FIG. 19 is an example of a cell DTX / DRX related operation. Referring to FIG. 19, the existing cell DTX and / or cell DRX operation consists of a pattern consisting of {active period, inactive period} forming a cycle, and DL and / or UL data transmission is performed during the active period, and SSB / system information (SI) / paging transmission and PRACH reception, etc., can be performed periodically by the BS regardless of whether it is an active period or an inactive period.
[0330] FIG. 20 is an example of cell DTX / DRX related operations according to some implementations. When a semi-active period is introduced according to some implementations of the present specification, cell DTX and / or cell DRX operations such as the example in FIG. 20 form a cycle consisting of a pattern of {active period, semi-active period, inactive period}, and (compared to FIG. 19) SSB / SI / paging transmission and PRACH reception, etc. are not performed during the inactive period, thereby improving the energy saving effect of the BS.
[0331] Some implementations of this specification related to cell DTX and / or cell DRX operations composed of {active interval, semi-active interval, inactive interval}, and some implementations of this specification related to methods for setting / defining each interval and / or methods for transmitting / receiving common signals / channels (e.g., SSB, SI, paging, PRACH, etc.) for each interval are described below.
[0332] <Method #1> Method for defining semi-active intervals
[0333] The positions of the three sections that make up a cycle can be set by at least one of the following options. Additionally, which of these options to use can be set in advance.
[0334] Opt 1: Within a cycle, the offset / duration of the active and semi-active periods may be set separately, and the remaining period may be considered as an inactive period. For example, when the cycle is 256 ms, the active period may be set to a 40 ms period from 10 ms to 50 ms from the start of the cycle, the semi-active period may be set to an 80 ms period from 100 ms to 180 ms from the start of the cycle, and the remaining period may be determined as an inactive period.
[0335] Opt 2: Within a cycle, the offsets / periods of the active and inactive periods are set separately, and the remaining period may be considered as a semi-active period. For example, when the cycle is 256 ms, the active period is set to a 40 ms period from 10 ms to 50 ms from the start of the cycle, the inactive period is set to a 100 ms period from 50 ms to 150 ms from the start of the cycle, and the remaining period may be determined as a semi-active period.
[0336] Opt 3: An offset / period of the active interval is set within a cycle, a semi-active interval is set based on its relative position from the active interval, and the remaining interval may be considered an inactive interval. For example, when the cycle is 256 ms, the active interval is set to a 40 ms period from 10 ms to 50 ms from the start of the cycle, the semi-active interval is set to an 80 ms period starting from a point obtained by applying a 50 ms offset from the end (or start) of the active interval, and the remaining interval may be determined as an inactive interval. In other words, when based on the end of the active interval, the interval-specific settings are identical to those of Opt 1.
[0337] Opt 4: An offset / period of the active interval is set within a cycle, an inactive interval is set based on its relative position from the active interval, and the remaining interval may be considered a semi-active interval. For example, when the cycle is 256 ms, the active interval is set to a 40 ms period from 10 ms to 50 ms from the start of the cycle, the inactive interval is set to a 100 ms period starting from a point offset of 0 ms from the end (or start) of the active interval, and the remaining interval may be determined as a semi-active interval. In other words, when based on the end of the active interval, the interval-specific settings are identical to those of Opt 2.
[0338] In some implementations, if a semi-active interval is not separately configured, all intervals excluding the active interval may be determined as semi-active intervals (or inactive intervals, or whichever is configured separately). Additionally, the method(s) described below (e.g., Method #2, Method #3, Method #4, and / or Method #5) may be applied to the "intervals excluding the active interval."
[0339] One or more inactive and / or semi-active intervals may exist within a cycle, and in such cases, the above options can be easily extended (by setting one or more values such as interval offsets / periods). Alternatively, when one or more inactive and / or semi-active intervals exist within a cycle, additional periods may be set for each interval (within a single cycle).
[0340] From the perspective of the UE, the semi-active state may apply only to specific (one or more) serving cell(s) / carrier(s) (e.g., PCell, PSCell, pre-configured / defined serving cell / carrier, serving cell / carrier with the lowest / highest cell / carrier index, the anchor-carrier in the case where multiple DL / UL carriers are configured within a single serving cell and there is a specific carrier on which SSB / SI / paging / PRACH is operated, etc.). The remaining serving cell(s) / carrier(s), excluding the specific (one or more) serving cell / carrier, may be considered as inactive rather than semi-active. As another example, from the perspective of a UE configured with multiple serving cells / carriers (within the same cell group), an active state may mean that all serving cells / carriers are active, an inactive state means that all serving cells / carriers are inactive, and a semi-active state means that only a specific serving cell / carrier (e.g., an anchor carrier) is active (e.g., the remaining serving cells / carriers excluding the specific serving cell / carrier are inactive).
[0341] Below, some implementations of this specification related to the transmission / reception of signals / channels are described in more detail for each of the three intervals (e.g., active interval, semi-active interval, and inactive interval).
[0342] Method for BS to transmit SSB and UE to receive SSB
[0343] Method of BS's SI transmission and UE's SI reception
[0344] Method for BS to transmit paging and UE to receive paging
[0345] Method for BS receiving PRACH and UE transmitting PRACH
[0346] <Method #2> Method for BS SSB transmission and UE SSB reception for each segment
[0347] In the first method, the SSB period to be transmitted in all or part of the three intervals may be defined / determined or set / instructed differently. For example, the SSB period corresponding to the active interval may be P1 ms, the SSB period corresponding to the semi-active interval may be P2 ms, and no SSB may be transmitted during the inactive interval, or the SSB period corresponding to the inactive interval may be P3 ms. When there are two half-frames constituting a single frame and one SSB can be transmitted within one half-frame (e.g., at most one SSB for one SSB index is transmitted within one half-frame), SSBs associated with different SSB periods transmitted within one cell DTX (and / or cell DRX) cycle may be transmitted in the same half-frame (i.e., the P1 ms period SSB, P2 ms period SSB, and P3 ms period SSB may all be transmitted in the first half-frame or all in the second half-frame). This may have the advantage of reducing the reception complexity of the UE. The values of P1, P2, and P3 (if an SSB with a period of P3 ms is transmitted) may all be equal, or the relationship P1 ≥ P2 (or P1 ≤ P2, or if an SSB with a period of P3 ms is transmitted, P1 ≤ P2 ≤ P3) may hold. The UE may receive an SSB with a period of P1 ms during the active period, receive an SSB with a period of P2 ms during the semi-active period, and receive an SSB with a period of P3 ms during the inactive period (if an SSB with a period of P3 ms is transmitted). By setting the period of the SSB transmitted during the semi-active period to be relatively short, the BS may be able to transmit SSBs densely during the semi-active period and omit SSB transmission during the inactive period. In this case, the SSB periods corresponding to long periods may be a subset of the SSB periods corresponding to relatively short periods.
[0348] As a second method, at least one of the following SSB setting parameters may be defined / determined or set / instructed differently for each interval.
[0349] SSB cycle
[0350] Frequency location of the SSB (e.g., center frequency)
[0351] SSB time resource information (e.g., SFN index, half-frame index, etc.)
[0352] SSB index information constituting the SSB (e.g., position information per SSB index within the SSB burst, such as the ssb-PositionsInBurst parameter)
[0353] Physical cell ID of the SSB
[0354] SSB transmission power
[0355] SSB subcarrier spacing
[0356] For example, in the active period, the SSB period is set to P1 ms and the SSB frequency position to F1; in the semi-active period, the SSB period is set to P2 ms and the SSB frequency position to F2; and in the inactive period, no SSB information is set, or the SSB period is set to P3 ms and the frequency position to F3. The UE can perform reception of the SSB based on the SSB period and SSB frequency position set for each period. Alternatively, default SSB parameter(s) are set / defined, and SSBs with the applied default SSB parameter(s) are transmitted in the active / semi-active period (plus the inactive period); additionally, if a specific SSB parameter is set / indicated / activated, an SSB corresponding to that parameter can be additionally transmitted in the active or semi-active period.
[0357] In a third method, one or more SSB settings may be configured, and different or identical SSB settings may be applied, set, or directed for each segment. An SSB setting may include one or more of the SSB setting parameters listed above. For example, multiple SSB settings may exist and be indexed by each setting, with SSB setting indices #0 / 1 / 2... set; SSB setting #0 may be linked to the active segment, SSB setting #1 to the semi-active segment, and SSB setting #2 to the inactive segment (if transmitted). SSBs may be transmitted by parameters belonging to the SSB settings linked for each segment. Alternatively, a default SSB setting (or default SSB parameters) may be set or defined, and SSBs to which the default setting (or default SSB parameters) is applied may be transmitted in the active / semi-active segment (and additionally inactive segment); additionally, if a specific SSB setting index is set, directed, or activated, an SSB corresponding to that SSB setting index may be additionally transmitted to the active or semi-active segment.
[0358] The methods described above can be extended and applied to tracking reference signals (TRS) (or tracking CSI-RS). TRS is utilized for time / frequency tracking (for receiving high-order modulation) and requires periodic transmission to be guaranteed for stable data reception. Similar to the first method described above, the period of the TRS is determined / defined or set / instructed for each interval, and the UE can receive the TRS based on the TRS period determined / set according to each interval. Similar to the second method described above, the configuration parameters of the TRS (e.g., TRS period, index(s) of the symbol(s) transmitted by the TRS, frequency resource information of the TRS, transmission power of the TRS, QCL information of the TRS, etc.) are determined / defined or set / instructed for each interval, and the UE can receive the TRS based on the TRS parameters determined / set according to each interval. Similar to the third method above, when there are TRS settings composed of one or more TRS parameters, a TRS setting index can be applied / set / instructed for each segment, and the UE can receive TRS based on the TRS setting determined / set according to each segment.
[0359] <Method #3> Method for transmitting system information (SI) from the BS and receiving SI from the UE for each segment
[0360] The UE identifies the location of the CORESET based on the common search space (CSS) set configuration information for receiving SI, and monitors the PDCCH that schedules the PDSCH containing SI information in the corresponding CORESET. The 5G NR UE can monitor the PDCCH that schedules SIB1 or a non-SIB based on searchSpaceZero regarding parameters of common search space #0, searchSpaceSIB1 regarding the ID of the search space for SIB1 messages, and searchSpaceOtherSystemInformation regarding the ID of other system information (OSI). For convenience, in this specification, the CSS set configuration information for the PDCCH that schedules SIB1 or a non-SI (or any SI) is referred to as the SI-CSS set (configuration information).
[0361] The BS can adjust the UE's PDCCH monitoring frequency by providing separate SI-CSS set settings for each period. For example, SI-CSS set #0 can be set for the active period, SI-CSS set #1 for the semi-active period, and SI-CSS set #2 for the inactive period. Alternatively, SI-CSS set #0 can be set for the active period, SI-CSS set #1 for the semi-active period, and no SI-CSS set can be set for the inactive period. By not setting SI-CSS set information for the inactive period, the UE may not perform monitoring of the PDCCH scheduling SI information during that period. If one CORESET is located for every two slots in SI-CSS set #0 and two CORESETs are located for every one slot in SI-CSS set #1, then (if the number of SSB indices being transmitted is N), PDSCH containing CORESET and SI information can be transmitted for at least 2*N slots during the active period and PDSCH containing CORESET and SI information can be transmitted for at least N / 2 slot(s) during the semi-active period. As a result, the BS can transmit SI information compressively, so it may not be necessary for the BS to perform the conventional operation of periodically transmitting SI during the inactive period (even though there is no DL / UL data).
[0362] The method of adjusting the interval-by-interval PDCCH monitoring frequency for CSS sets, as described above, can be extended and applied not only to SI-CSS sets but also to other CSS sets. For example, when a CSS set configured to receive a random access response (RAR) DCI (e.g., a DCI that schedules a RAR MAC CE) (or a DCI scrambled by RA-RNTI) is called an RA-CSS set (e.g., a CSS set configured by the RRC parameter ra-SearchSpace regarding the ID of the search space for the random access process in a 5G NR system), RA-CSS sets can be configured for each interval. For example, RA-CSS set #0 can be configured for the active interval, RA-CSS set #1 for the semi-active interval, and RA-CSS set #2 for the inactive interval. Alternatively, RA-CSS set #0 may be set during the active period, RA-CSS set #1 may be set during the semi-active period, and no RA-CSS set may be set during the inactive period. In this way, by not setting RA-CSS set information during the inactive period, the UE may not perform monitoring of the RAR DCI during that period.
[0363] Meanwhile, when the UE receives SI information, period and window information (e.g., information set through RRC parameters si-Periodicity regarding the period of SI messages in wireless frame units and si-WindowLength regarding the length of the SI scheduling window) may be configured. The UE may attempt to receive SI messages or SI information within the window interval starting at each corresponding period. Period / window information associated with such SI message reception may be configured for each interval. For example, a P1 period and a W1 window length may be configured for the active interval, and a P2 period and a W2 window length may be configured for the semi-active interval. The UE may receive SI messages during a W1-length window starting at every P1 period in the active interval, receive SI messages during a W2-length window starting at every P2 period in the semi-active interval, and not perform SI message reception during the inactive interval. In this case, by establishing the relationships P1 ≤ P2 (or P1 ≥ P2) and / or W1 ≥ W2, SI message transmission can be performed more compressibly from a BS perspective during the semi-active period compared to the active period. Misalignment between the window and the period can be minimized by aligning the starting point of the window associated with SI message reception with the starting point of a specific period (e.g., active and / or semi-active and / or inactive period). Additionally, if a partial overlap occurs between the SI window and the period of the specific period (e.g., active and / or semi-active and / or inactive period), the UE may 1) prioritize the SI window and continue to perform SI monitoring even outside the period of the specific period, or 2) prioritize the period of the specific period and not perform SI monitoring if it is outside the period of that specific period.At this time, which of the operations in 1) or 2) the UE applies may vary depending on the interval (e.g., active and / or semi-active and / or inactive interval).
[0364] The UE can expect that UE-specific DCIs (hereinafter referred to as UE-specific DL / UL scheduling DCIs) (e.g., fallback DL / UL DCIs) that schedule DL reception / UL transmission via CSS sets transmitted / existing during semi-active / inactive periods will not be transmitted. This may have the advantage of maximizing common signaling / channel transmission / reception resources such as SSB / SI / paging / PRACH by minimizing DL / UL UE-specific data transmission during the period. Alternatively, the transmission of UE-specific DL / UL scheduling DCIs via CSS sets transmitted during semi-active / inactive periods may be configured by the BS, and a UE that is configured to transmit may expect to receive UE-specific DL / UL scheduling DCIs via said CSS set. The UE may not perform PDCCH monitoring in a UE-specific search space (USS) set during semi-active / inactive periods, or the performance of PDCCH monitoring may be configured by the BS.
[0365] <Method #4> Method for BS paging transmission and UE paging reception for each segment
[0366] Referring to Section 7.1 of 3GPP TS 38.304, the paging frame (PF) and paging occasion (PO) for paging are determined by the following formulas.
[0367] The SFN for the above PF is determined by the following: (SFN + PF_offset) mod T = (T div N)*(UE_ID mod N).
[0368] The index (i_s) representing the index of the above PO is determined by the following: i_s = floor(UE_ID / N) mod Ns.
[0369] The PDCCH monitoring time for paging is determined by the parameter pagingSearchSpace, which is the ID of the search space for paging as specified in 3GPP TS 38.213; the parameter firstPDCCH-MonitoringOccasionOfPO, which indicates the first PDCCH monitoring time for paging for each PO of the PF when configured as specified in 3GPP TS 38.331; and the parameter nrofPDCCH-MonitoringOccasionPerSSB-InPO, which is the number of PDCCH monitoring times corresponding to SSBs within the paging time. If SearchSpaceId=0 is set for pagingSearchSpace, the PDCCH monitoring time for paging is the same as for remaining minimum system information (RMSI) as defined in Section 13 of 3GPP TS 38.213.
[0370] If SearchSpaceId=0 is set for pagingSearchSpace, Ns is either 1 or 2. For Ns = 1, there is only one PO starting from the time of the first PDCCH monitoring for paging within the PF. For Ns = 2, the PO is within the first half-frame (i_s = 0) or the second half-frame (i_s = 1) of the PF.
[0371] If a non-zero SearchSpaceId is set for pagingSearchSpace, the UE monitors the (i_s + 1)-th PO. A single PO is a set of 'S*X' consecutive PDCCH monitoring times, where 'S' is the number of actual transmitted SSBs determined by ssb-PositionsInBurst in SIB1, and X is nrofPDCCH-MonitoringOccasionPerSSB-InPO if set, and equal to 1 otherwise. The [x*S + K]-th PDCCH monitoring time for paging within the PO corresponds to the K-th transmitted SSB, where x = 0, 1, ..., X-1 and K = 1, 2, ..., S. Paging PDCCH monitoring times that do not overlap with UL symbols (determined by tdd-UL-DL-ConfigurationCommon) are numbered sequentially starting from 0, beginning with the first PDCCH monitoring time for paging within the PF. If firstPDCCH-MonitoringOccasionOfPO exists, the starting PDCCH monitoring time number of the (i_s + 1)th PO is the (i_s + 1)th value of the firstPDCCH-MonitoringOccasionOfPO parameter; otherwise, it is equal to i_s*S*X. If X > 1, when a UE detects a PDCCH transmission addressed by P-RNTI within its PO, the UE is not required to monitor subsequent PDCCH monitoring times for this PO.
[0372] A PO associated with a PF can start within the PF or after the PF. The PDCCH monitoring period for a PO can span multiple wireless frames. If a SearchSpaceId other than 0 is set for pagingSearchSpace, the PDCCH monitoring periods for a PO can span multiple periods of the paging search space.
[0373] The following parameters are used in the calculation of PF and i_s above:
[0374] T: UE's DRX cycle.
[0375] N: Total number of paging frames in T.
[0376] Ns: Number of paging times for PF.
[0377] PF_offset: Offset used for PF determination.
[0378] If UE_ID:UE operates as eDRX as specified in Section 7.4 of 3GPP TS 38.304, it is 5G-S-TMSI mod 4096; otherwise, it is 5G-S-TMSI mod 1024.
[0379] In this way, one or more of the following parameters may be involved for a UE to determine the paging frame (PF) and paging occasion (PO) corresponding to its UE ID.
[0380] pagingSearchSpace: Information regarding a CSS set to which a DCI with CRC scrambled with P-RNTI (hereinafter referred to as Paging DCI) is transmitted, which may be identical to or different from an SI-CSS set. For convenience, in this specification, a CSS set to which a Paging DCI can be transmitted is referred to as a paging-CSS set.
[0381] T: DRX cycle of the above UE.
[0382] N: Number of total paging frames in T
[0383] Ns: Number of paging occasions for a PF
[0384] PF_offset: Offset used for PF determination
[0385] firstPDCCH-MonitoringOccasionOfPO: Starting symbol index of the first PDCCH monitoring occasion (MO) for each PO within T
[0386] >nrofPDCCH-MonitoringOccasionPerSSB-InPO: Number of PDCCH MOs corresponding to a single SSB index
[0387] When there are PF / PO determination parameters as described above or others, all or part of these parameters can be configured differently for the active and semi-active periods. For example, the paging-CSS set applied to the active period can be configured differently from the paging-CSS set applied to the semi-active period. Through this, the paging PDCCH MO in the semi-active period can be configured to be denser than the paging PDCCH MO in the active period. The UE may perform monitoring of the paging DCI based on the paging-CSS set configured for that period in the active period, monitor the paging DCI based on the paging-CSS set configured for that period in the semi-active period, and not monitor the paging DCI in the inactive period. As another example, the PF / PO interval / number in the active period can be configured differently from the PF / PO interval / number in the semi-active period. Specifically, the PF / PO interval can be set / determined / defined as N1 in the active period and as N2 in the semi-active period. In this case, since the relationship N1 ≥ N2 holds, paging DCI / message transmission can be performed more compactly from a BS perspective during the semi-active period compared to the active period. Alternatively, default paging parameters are set / defined, and PF / POs with the applied default paging parameters are determined in the active / semi-active period (plus the inactive period), and if a specific paging parameter is additionally set / instructed / activated, additional PF / POs corresponding to that paging parameter may be created in the active period or semi-active period.
[0388] Alternatively, one or more paging settings may be configured, and different or identical paging settings may be applied / set / instructed for each segment. A paging setting may include one or more of the parameters for determining the PF and PO listed above. For example, multiple paging settings may exist and be indexed for each setting, with paging setting indices #0 / 1 / 2... set, and paging setting #0 may be linked to the active segment, paging setting #1 to the semi-active segment, and paging setting #2 to the inactive segment (if transmitted). The PF / PO may be determined by the parameters belonging to the paging settings linked for each segment. Alternatively, default paging settings (or default paging parameters) are set / defined, and PF / POs to which the default paging settings (or default paging parameters) are applied are transmitted to active / semi-active intervals (in addition to inactive intervals), and additionally, if a specific paging setting index is set / indicated / activated, the PF / PO determined by the parameter may additionally be located in the active interval or semi-active interval.
[0389] Frequency domain multiplexing (FDM) can be considered as a method to position PF / PO more compactly or densely (in the time axis) during the semi-active period. For example, at a given time, there may be one or more POs (or PDCCH MOs) within a single serving cell / carrier BWP, and each PO (or PDCCH MO) may occupy a different frequency resource. As another example, at a given time, there may be one or more POs (or PDCCH MOs), and the serving cell / carrier BWP may differ between the POs (or PDCCH MOs).
[0390] Even if resources for SSB / SI / paging are determined / defined or configured / directed within the inactive period (and / or semi-active period) in the aforementioned Method #2, Method #3, or Method #4, the UE may not attempt to receive SSB and / or monitor SI and / or receive paging DCI / messages within said inactive period (and / or semi-active period). Alternatively, the UE may consider the PDCCH MO and / or paging MO associated with the SSB timing and / or CSS set during said inactive period (and / or semi-active period) to be invalid.
[0391] <Method #5> Method for BS PRACH reception and UE PRACH transmission for each segment
[0392] To aid in understanding some implementations of this specification, PRACH configurations according to the current standard document are first described with reference to the following table and Figure 21. The following table provides examples of arbitrary connection configurations. In particular, the following table is part of Table 6.3.3.2-4, which defines arbitrary connection configurations for FR2 and unpaired spectrum as described in 3GPP TS 38.211.
[0393]
[0394] The table above is a mother table for indicating the PRACH configuration index in 3GPP TS 38.211, and the UE can determine the appropriate table from SIB1 based on the frequency range and whether it is frequency division duplex (FDD) or time division duplex (TDD), and receive a row index within the determined table to configure the RACH slots and ROs. Based on the PRACH configuration index (also called the RACH configuration index), the UE can determine the available set of PRACH times for transmitting the random access preamble for Msg1.
[0395] FIG. 21 is an example of random access channel (RACH) slots and RACH occasions (RO) according to a physical random access channel (PRACH) setting. In particular, FIG. 21 illustrates RACH slots and ROs when PRACH setting index 9 is provided through a RACH setting for FR2 and a cell on an unpaired spectrum.
[0396] In some implementations of this specification, a RACH configuration may refer to one or more of RACH-ConfigCommon, RACH-ConfigCommonTwoStepRA, RACH-ConfigDedicated, RACH-ConfigGeneric, RACH-ConfigGenericTwoStepRA, and RACH-ConfigTwoTA from the standard document 3GPP TS 38.331, and is referred to for convenience as abbreviated as RACH configuration. Through such RACH configuration, RACH occasions (ROs) on a specific time / frequency can be configured. In some implementations of this specification, a RACH configuration may also be used as an RO. In addition, BS can set the PRACH preamble format, the time axis position of the RO (e.g., the period / offset of the RO or the "RACH slot containing the RO" (i.e., the period / offset of the RO or the period / offset of the RACH slot containing the RO), the frame / subframe / slot / symbol index where the RO or the "RACH slot containing the RO" starts or is included), and the duration of the RO or the "RACH slot containing the RO" by setting / instructing the UE to set the RACH configuration index (RCI) value. For example, a specific RCI value may be set / indicated by the parameter prach-ConfigurationIndex (set by RRC signaling and can be a value from 0 to 255), and the tables in Section 6.3.3.2 of the standard document 3GPP TS 38.211 (e.g., Table 6.3.3.2-2, Table 6.3.3.2-3, Table 6.3.3 of 3GPP TS 38.211).As in 2-4), for each index, one or more of the following may be mapped: a preamble format, x and / or y values of n_f mod x = y (where x is the frame unit period of the RACH slot containing the RO, y is the frame unit offset of the RACH slot containing the RO, and n_f may represent the system frame number), a slot number, a starting symbol, the number of PRACH slots within a 60 kHz slot, the number of time domain PRACH occasions within a PRACH slot, and PRACH duration values.
[0397] In the first method, the period of the RO or "RACH slot containing RO" to be transmitted in all or part of the three intervals (referred to as the RO or "RACH slot" period for convenience) may be defined / determined or set / instructed differently. For example, the RO or RACH slot period corresponding to the active interval may be P1 ms, the RO or RACH slot period corresponding to the semi-active interval may be P2 ms, and RACH may not be set in the inactive interval, or the RO or RACH slot period corresponding to the inactive interval may be P3 ms. The values of P1, P2, and P3 (if RO or RACH slots with a period of P3 ms are set) may all be the same, or the relationship P1 ≥ P2 (or P1 ≤ P2, or if RO or RACH slots with a period of P3 ms are transmitted, P1 ≤ P2 ≤ P3) may hold. The UE can perform PRACH transmission using the determined RO by determining the RO based on the P1 ms RO or RACH slot period during the active period, determining the RO based on the P2 ms RO or RACH slot period during the semi-active period, and determining the RO based on the P3 ms RO or RACH slot period during the inactive period (if RACH is set during the inactive period). By setting the period of the RO or RACH slot set during the semi-active period to a relatively short length, it is possible to densely position the RO during the semi-active period and omit the RO setting during the inactive period.
[0398] As a second method, at least one of the following RACH-related configuration parameters may be defined / determined or set / instructed differently for each interval.
[0399] PRACH preamble format
[0400] Time axis position of the RO (e.g., period / offset of the RO or RACH slot, frame / subframe / slot / symbol index where the RO or RACH slot starts or is included, duration of the RO or RACH slot, etc.)
[0401] Frequency location information of ROs and the number of ROs undergoing FDM at the same time
[0402] Number of linked SSB indexes per RO
[0403] PRACH's subcarrier spacing
[0404] For example, in the active period, the RO or RACH slot period is set to P1 ms and the number of ROs FDMed at the same time is set to R1; in the semi-active period, the RO or RACH slot period is set to P2 ms and the number of ROs FDMed is set to R2; and in the inactive period, RACH-related information may not be set, or the RO or RACH slot period may be set to P3 ms and the number of ROs FDMed is set to R3. The UE can perform PRACH transmission based on the RO or RACH slot period and the number of ROs FDMed set for each period. Alternatively, default RACH parameters may be set / defined, and ROs to which the default RACH parameters are applied may be determined in the active / semi-active period (plus the inactive period); and if a specific RACH parameter is additionally set / indicated / activated, ROs corresponding to that RACH parameter may additionally appear in the active or semi-active period.
[0405] In a third method, different or identical RCIs may be applied / configured / instructed for each segment. A single RCI may include one or more of the RACH configuration parameters listed above. For example, there may be multiple RCI values, and RCI #n1 may be linked to the active segment, RCI #n2 to the semi-active segment, and RCI #n3 to the inactive segment (if configured). The RO location may be determined by the parameters belonging to the RCI values linked to each segment. Alternatively, a default RACH setting (or default RCI value or default RACH parameters) may be configured / defined, and ROs to which that default RACH setting (or default RCI value or default RACH parameters) is applied may be determined within the active / semi-active segment (plus the inactive segment); additionally, if a specific RACH setting (or RCI value) is configured / instructed / activated, an RO corresponding to that specific RACH setting (or RCI value) may be additionally located in the active or semi-active segment.
[0406] When the method of performing mapping between specific SSB index(s) and RO is referred to as SSB-to-RO mapping, such SSB-to-RO mapping can be performed independently for each interval. SSB-to-RO mapping can be performed individually for ROs included in the active interval, SSB-to-RO mapping can be performed individually for ROs included in the semi-active interval, and SSB-to-RO mapping can be performed individually for ROs included in the inactive interval (if configured). Here, RO may distinguish between ROs to which the default RACH setting is applied or ROs corresponding to specific RACH settings to be additionally configured or directed, or it may refer collectively to both types of ROs.
[0407] Even if an RO or RACH slot is determined / defined or set / instructed within the inactive period (and / or semi-active period) in the above-described method #5, the UE may not attempt to send a PRACH within the said inactive period (and / or semi-active period). Alternatively, the UE may consider the RO in the said inactive period (and / or semi-active period) to be invalid.
[0408] In some implementations, the BS may have degrees of freedom for each interval by setting a list of signals / channels that can be enabled for each interval to the UE. For example, the BS may set which of the three intervals at least one of the signals / channels in the list below is enabled and which is not enabled.
[0409] SSB
[0410] CSS sets (e.g., SI-CSS set, RA-CSS set, paging-CSS set, etc.)
[0411] USS Set
[0412] SI Monitoring Window
[0413] PF / PO
[0414] > RO
[0415] For example, it can be configured so that the SSB is enabled during the active period and the semi-active period, and other signals / channels in the list are enabled only during the active period. The UE can receive the SSB during the semi-active period to perform measurement and / or time / frequency synchronization, and perform SI / paging reception or RACH transmission operations during the active period.
[0416] When setting the activation intervals for each signal / channel in the list above, it is also possible to set where the corresponding signal / channel can be transmitted among the serving cell / carrier / BWP / TRP(s).
[0417] FIG. 22 illustrates a signal transmission / reception flow between a first device and a second device in some implementations of the present specification. As in Method #1 described above, the BS can set a cell DTX and / or cell DRX in which a pattern consisting of {active period, semi-active period, inactive period} constitutes one cycle (S2201). Additionally, the BS can set transmission / reception parameters for a common signal / channel (e.g., SSB, SI, paging, PRACH) for each period (by applying Methods #2, #3, #4, and / or Method #5 described above) (S2203). Based on the received settings (by applying Methods #2, #3, #4, and / or Method #5 described above), the UE and / or BS can receive or transmit the common signal / channel by applying different reception / transmission parameters depending on which period they are located in (S2205).
[0418] According to some implementations of this specification, cell DTX and / or cell DRX operations may be performed in which a pattern consisting of {active period, semi-active period, inactive period} constitutes one cycle. Accordingly, network energy saving (NES) gains can be maximized because the BS can perform the minimum necessary operations for UE services during the semi-active period while the BS can sleep deeply during the inactive period.
[0419] The above-described method #1 may be applied independently or together with at least one of methods #2 to #5.
[0420] FIG. 23 illustrates the flow of operation in a first device according to some implementations of the present specification. The first device may perform operations according to some implementations of the present specification. The first device 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, when executed, storing instructions that cause the at least one processor to perform operations according to some implementations of the present specification. A processing device for the first device may include at least one processor; and at least one computer memory operably connected to the at least one processor and, when executed, storing instructions that cause the at least one processor to perform operations according to some implementations of the present specification. A computer-readable (non-transient) storage medium may store at least one computer program including instructions that cause the at least one processor to perform operations according to some implementations of the present specification when executed by the at least one processor. A computer program or computer program product is written on at least one computer-readable (non-transient) storage medium and may include instructions that, when executed, cause (at least one processor) to perform operations according to some implementations of this specification.In a method performed by the first device, or in the first device, the processing device, the computer-readable (non-transient) storage medium, and / or the computer program product, the operations may include: receiving a cell discontinuous transmission (DTX) / discontinuous reception (DRX) setting for a cell (S2301), wherein the cell DTX / DRX setting includes first information related to a periodic pattern of active, semi-static, and inactive periods; receiving second information for setting a search space (SS) set related to the periodic pattern (S2303); and performing physical downlink control channel (PDCCH) monitoring based on the first information and the second information (S2305).
[0421] FIG. 24 illustrates the flow of operation in a second device according to some implementations of the present specification. The second device may perform operations according to some implementations of the present specification. The second device may perform operations according to some implementations of the present specification in relation to receiving a UL signal. The second device may include at least one transceiver; at least one processor; and at least one computer memory operably connectable to said at least one processor and, when executed, stores instructions that cause said at least one processor to perform operations according to some implementations of the present specification. A processing device for the second device may include at least one processor; and at least one computer memory operably connectable to said at least one processor and, when executed, stores instructions that cause said at least one processor to perform operations according to some implementations of the present specification. A computer-readable (non-transient) storage medium may store at least one computer program including instructions that cause said at least one processor to perform operations according to some implementations of the present specification when executed by said at least one processor. A computer program or computer program product is written on at least one computer-readable (non-transient) storage medium and may include instructions that, when executed, cause (at least one processor) to perform operations according to some implementations of this specification.In a method performed by the second device, or in the second device, the processing device, the computer-readable (non-transitive) storage medium, and / or the computer program product, the operations may include: transmitting a cell discontinuous transmission (DTX) / discontinuous reception (DRX) setting for a cell (S2401), wherein the cell DTX / DRX setting includes first information related to a periodic pattern of active, semi-static, and inactive periods; transmitting second information for setting a search space (SS) set related to the periodic pattern (S2403); and performing a physical downlink control channel (PDCCH) transmission based on the first information and the second information (S2405).
[0422] In some implementations of the present specification related to FIG. 22, FIG. 23, or FIG. 24, downlink (DL) reception or transmission and uplink (UL) transmission or reception may not be performed within the inactive period.
[0423] In some implementations of the present specification related to FIG. 22, FIG. 23, or FIG. 24, the SS set setting may include a common search space (CSS) set setting for each of the active interval, the semi-active interval, and the inactive interval.
[0424] In some implementations of the present specification related to FIG. 22, FIG. 23, or FIG. 24, the CSS set configuration is related to receiving or transmitting system information (SI), receiving or transmitting paging, or receiving or transmitting a random access response (RAR).
[0425] In some implementations of the present specification related to FIG. 22, FIG. 23, or FIG. 24, the method or operation may further include determining that the PDCCH monitoring occasion (MO) is invalid based on the fact that the PDCCH monitoring occasion (MO) is associated with a set of common search spaces (CSS) within the inactive interval.
[0426] In some implementations of the present specification related to FIG. 22, FIG. 23, or FIG. 24, the method or operation may further include: omitting PDCCH monitoring or PDCCH transmission for the first device-specific downlink control information (DCI) on the SS set within at least one of the semi-active period or the inactive period.
[0427] As described above, the examples of this specification disclosed are provided to enable a person skilled in the art related to this specification to implement and practice this specification. Although the foregoing has been described by reference to the examples of this specification, a person skilled in the art may modify and change the examples of this specification in various ways. Accordingly, this specification is not intended to be limited to the examples described herein, but to be given the broadest possible scope consistent with the principles and novel features disclosed herein.
[0428] Implementations of this specification may be used in wireless communication systems, BS or UE, or other equipment.
Claims
1. In a method performed by the first device, Receiving cell discontinuous transmission (DTX) / discontinuous reception (DRX) settings for a cell, said cell DTX / DRX settings including first information related to a periodic pattern of active, semi-static, and inactive periods; Receiving second information for setting a search space (SS) set related to the above periodic pattern; and A method comprising performing physical downlink control channel (PDCCH) monitoring based on the first information and the second information. method.
2. In Paragraph 1, Downlink (DL) reception and uplink (UL) transmission are not performed within the above inactive period, method.
3. In Paragraph 1, The above SS set setting includes a common search space (CSS) set setting for each of the active section, the semi-active section, and the inactive section, method.
4. In Paragraph 3, The above CSS set configuration is related to receiving system information (SI), pagination, or random access response (RAR), method.
5. In Paragraph 1, Further comprising determining that the PDCCH monitoring occasion (MO) is invalid based on whether the PDCCH monitoring occasion (MO) is related to a common search space (CSS) set within the inactive interval, method.
6. In Paragraph 1, The method further comprises omitting PDCCH monitoring related to the reception of first device-specific downlink control information (DCI) on an SS set within at least one of the above semi-active period or the above inactive period. method.
7. At least one transmitter / receiver; At least one processor; and It includes at least one computer memory operablely connectable to the at least one processor and, when executed, stores instructions that cause the at least one processor to perform operations, wherein the operations are: Receiving cell discontinuous transmission (DTX) / discontinuous reception (DRX) settings for a cell, said cell DTX / DRX settings including first information related to a periodic pattern of active, semi-static, and inactive periods; Receiving second information for setting a search space (SS) set related to the above periodic pattern; and A method comprising performing physical downlink control channel (PDCCH) monitoring based on the first information and the second information. First device.
8. At least one processor; and It includes at least one computer memory operablely connectable to the at least one processor and, when executed, stores instructions that cause the at least one processor to perform operations, wherein the operations are: Receiving cell discontinuous transmission (DTX) / discontinuous reception (DRX) settings for a cell, said cell DTX / DRX settings including first information related to a periodic pattern of active, semi-static, and inactive periods; Receiving second information for setting a search space (SS) set related to the above periodic pattern; and A method comprising performing physical downlink control channel (PDCCH) monitoring based on the first information and the second information. Processing unit.
9. In a computer-readable non-transitory storage medium, The above storage medium stores at least one program code including instructions that cause at least one processor to perform operations when executed, and said operations are: Receiving cell discontinuous transmission (DTX) / discontinuous reception (DRX) settings for a cell, said cell DTX / DRX settings including first information related to a periodic pattern of active, semi-static, and inactive periods; Receiving second information for setting a search space (SS) set related to the above periodic pattern; and A method comprising performing physical downlink control channel (PDCCH) monitoring based on the first information and the second information. Storage medium.
10. In a method performed by the second device, Transmitting cell discontinuous transmission (DTX) / discontinuous reception (DRX) settings for a cell, said cell DTX / DRX settings including first information related to a periodic pattern of active, semi-static, and inactive periods; Transmitting second information for setting a search space (SS) set related to the above periodic pattern; and Based on the first information and the second information, including performing a physical downlink control channel (PDCCH) transmission. method.
11. At least one transmitter / receiver; At least one processor; and It includes at least one computer memory operablely connectable to the at least one processor and, when executed, stores instructions that cause the at least one processor to perform operations, wherein the operations are: Transmitting cell discontinuous transmission (DTX) / discontinuous reception (DRX) settings for a cell, said cell DTX / DRX settings including first information related to a periodic pattern of active, semi-static, and inactive periods; Transmitting second information for setting a search space (SS) set related to the above periodic pattern; and Based on the first information and the second information, including performing a physical downlink control channel (PDCCH) transmission. Second device.
