Method performed by user equipment, user equipment, processing device and storage medium, and method performed by base station and base station

By determining valid ROs based on SSB settings, including on-demand SSBs, the patent addresses network energy efficiency and power conservation challenges in cellular networks, optimizing signal transmission and reception.

WO2026235337A1PCT designated stage Publication Date: 2026-11-12LG ELECTRONICS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2026/005828
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-11-03
Filing Date
2026-05-06
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

The increasing demand for data processing in cellular networks due to emerging communication technologies like M2M, MTC, smartphones, and tablets, along with the need for enhanced mobile broadband, massive machine type communication, and ultra-reliable low-latency communication, poses challenges in network energy efficiency and power conservation.

Method used

Implementing methods and procedures for determining valid random access channel occasions (ROs) based on synchronization signal blocks (SSBs) settings, including on-demand SSBs, to optimize network energy usage and signal transmission/reception.

Benefits of technology

Enhances network energy saving by optimizing the use of SSBs, reducing unnecessary power consumption, and improving signal transmission efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2026005828_12112026_PF_FP_ABST
    Figure KR2026005828_12112026_PF_FP_ABST
Patent Text Reader

Abstract

According to the present invention, a UE may: receive a random access channel occasion (RO)-related configuration, a first synchronization signal block (SSB)-related configuration, and a second SSB-related configuration; determine valid ROs on the basis of the RO-related configuration; and perform PRACH transmission on the basis of the valid ROs. The second SSB-related configuration may be an OD SSB configuration, and the valid ROs may be determined on the basis of a union of SSBs provided by the first SSB-related configuration and SSBs provided by the second SSB-related configuration.
Need to check novelty before this filing date? Find Prior Art

Description

A method performed by a user device, a user device, a processing device and a storage medium, and a method performed by a base station and a base station

[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 user device is provided. In another aspect of the present specification, a user 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, when executed, storing instructions that 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, when executed, storing instructions that 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 cause the at least one processor to perform operations when executed. The method or operations include: receiving a random access channel occasion (RO) related setting, a first synchronization signal block (SSB) related setting, and a second related SSB setting; It may include determining valid ROs based on the above RO-related settings; and performing physical random access channel (PRACH) transmission based on the above valid ROs. At least the above second SSB-related settings may be on-demand (OD) SSB settings.

[0010] In one aspect of the present specification, a method performed by a base station is provided. In another aspect of the present specification, a base station 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, storing instructions that cause the at least one processor to perform operations. The method or the operations may include: transmitting a random access channel occasion (RO) related setting, a first synchronization signal block (SSB) related setting, and a second related SSB setting; and attempting to receive a physical random access channel (PRACH) on valid ROs associated with the RO related setting. At least the second SSB related setting may be an on-demand (OD) SSB setting.

[0011] In each aspect of the specification, the valid ROs may be determined based on the union of the SSBs provided by the first SSB-related setting and the SSBs provided by the second SSB-related setting.

[0012] In each aspect of the specification, the association between ROs and SSB indexes can be determined based on the union of the SSB indexes provided by the first SSB-related setting and the SSB indexes provided by the second SSB-related setting.

[0013] In each aspect of this specification, the RO in the PRACH slot may be determined to be valid based on starting at least N_gap symbols after the SSB.

[0014] In each aspect of the present specification, the first SSB-related setting may be provided by the radio resource control (RRC) information element ServingCellConfigCommon.

[0015] In each aspect of the present specification, the first SSB-related setting may include the first RRC parameter ssb-PositionsInBurst.

[0016] The above second SSB related setting may include the second RRC parameter od-ssb-PositionsInBurst.

[0017] In each aspect of the specification, the SSBs provided by the first SSB-related setting may be always-on SSBs provided without an activation command from the BS.

[0018] In each aspect of the specification, the SSBs provided by the second SSB-related setting may be determined based on at least one of the SSB period for OD-SSB, the system frame number (SFN) offset, the half-frame index, or the SSB locations within the burst.

[0019] 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.

[0020] According to some implementations of this specification, methods and procedures for energy saving of networks, BS and / or UEs may be provided.

[0021] 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.

[0022] 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.

[0023] 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:

[0024] FIG. 1 illustrates an example of a communication system 1 to which the implementations of the present specification are applied;

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

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

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

[0028] FIG. 5 illustrates a resource grid of slots;

[0029] 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;

[0030] FIG. 7 illustrates synchronization signal (SS) / physical broadcast channel (PBCH) blocks (SSB) on a cell.

[0031] FIG. 8 is illustrated to explain the bitmaps used to indicate the SSBs actually being transmitted;

[0032] FIG. 9 illustrates the process of acquiring system information (SI);

[0033] FIG. 10 illustrates an arbitrary connection process that may be applied to the implementation(s) of the present specification;

[0034] FIG. 11 is an example of random access channel (RACH) slots and RACH occasions (RO) according to a physical random access channel (PRACH) setting;

[0035] FIG. 12 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;

[0036] FIG. 13 illustrates an operation procedure in a BS that supports network energy saving (NES) technology;

[0037] FIG. 14 is an example of a procedure for carrier aggregation (CA) operation using an SSB-less secondary cell (SCell);

[0038] FIGS. 15 through 17 illustrate system information block 1 (SIB1) transmission scenarios related to some implementations of the present specification;

[0039] FIG. 18 is part of the RRC configuration used to provide on-demand SSB configuration;

[0040] FIG. 19 is an example of a signal transmission / reception flow between a first device (e.g., UE) and a second device (e.g., BS) according to some implementations of the present specification;

[0041] FIG. 20 is another example of a signal transmission / reception flow between a first device (e.g., UE) and a second device (e.g., BS) according to some implementations of the present specification;

[0042] FIG. 21 is another example of a signal transmission / reception flow between a first device (e.g., UE) and a second device (e.g., BS) according to some implementations of the present specification;

[0043] FIG. 22 is an example of an operation flow in a UE according to some implementations of the present specification;

[0044] FIG. 23 is an example of an operation flow in BS according to some implementations of the present specification;

[0045] FIG. 24 is another example of an operation flow in a UE according to some implementations of the present specification;

[0046] FIG. 25 is another example of the operation flow in BS according to some implementations of the present specification.

[0047] 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.

[0048] 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.

[0049] 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."

[0050] 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."

[0051] 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."

[0052] 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."

[0053] 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.

[0054] In the following explanation, 'when, if, in case of' can be replaced with 'based on'.

[0055] 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.

[0056] Technical features described individually within a single drawing in this specification may be implemented individually or simultaneously.

[0057] 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.

[0058] 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.

[0059] 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.

[0060] 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."

[0061] 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.

[0062] 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.

[0063] 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.

[0064] 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.

[0065] 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.

[0066] 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).

[0067] 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.

[0068] 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.

[0069] 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.

[0070] 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.

[0071] 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.

[0072] 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.

[0073] 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.

[0074] 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.

[0075] 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).

[0076] 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.

[0077] 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.

[0078] 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.

[0079] 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.

[0080] 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.

[0081] 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.

[0082] 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.

[0083] 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.

[0084] 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.

[0085] 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).

[0086] 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.

[0087] 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.

[0088] 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.

[0089] 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.

[0090] 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.

[0091] 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.

[0092] 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.

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

[0094] 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.

[0095] 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 ).

[0096]

[0097] 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.

[0098]

[0099] 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.

[0100] 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.

[0101] 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.

[0102] 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.

[0103] 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.

[0104] 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.

[0105]

[0106] 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.

[0107] 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.

[0108] 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.

[0109] 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).

[0110] 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.

[0111] 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.

[0112] Figure 7 illustrates SS / PBCH blocks (SSB) on a cell.

[0113] 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.

[0114] - For frequency range up to 3 GHz, L max = 4

[0115] - For frequency range from 3GHz to 6 GHz, L max = 8

[0116] - For frequency range from 6 GHz to 52.6 GHz, L max = 64

[0117] The actual number of transmitted SSBs can be configured, with a maximum number L maxIt can be smaller.

[0118] When multi-beam transmission is not applied, the number of SSB beams is 1.

[0119] Figure 8 is illustrated to explain the bitmaps used to indicate the SSBs actually being transmitted.

[0120] 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.

[0121] - 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.

[0122] - 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.

[0123] 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.

[0124] 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.

[0125] - 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.

[0126] - 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.

[0127] - 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.

[0128] 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.

[0129] 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.

[0130] 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.

[0131] - Step 1: The UE transmits the RA preamble via PRACH.

[0132] - Step 2: The UE receives a random access response (RAR) from the BS via PDSCH.

[0133] - 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.

[0134] - Step 4: The UE receives a contention resolution message from the BS via PDSCH.

[0135] 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.

[0136] 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.

[0137] - Step 0: BS assigns the RA preamble to the UE via dedicated signaling.

[0138] - Step 1: The UE transmits the RA preamble via PRACH.

[0139] - Step 2: The UE receives the RAR via the PDSCH from the BS.

[0140] 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.

[0141] 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.

[0142] 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).

[0143] A BS that receives MsgA may send MsgB to a UE. MsgB may include a RAR for said UE.

[0144] 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.

[0145] 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.

[0146] 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.

[0147] 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.

[0148] Prior to the initiation of the physical random access process, Layer 1 receives the following information from the upper layers:

[0149] - Physical Random Access Channel (PRACH) transmission parameters (PRACH preamble format, time resources, and frequency resources for PRACH transmission).

[0150] - 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)).

[0151] 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.

[0152] 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.

[0153] 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.

[0154] 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.

[0155] 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:

[0156] - Settings for PRACH transmission on the above cell.

[0157] - Preamble Index, Preamble SCS, PRACH Target Reception Power P PRACH,target , when applicable, the corresponding RA-RNTI, PRACH resource for the above cell.

[0158] - If the UE would transmit the PRACH with repetitions, N for transmitting the PRACH rep preamble >1 Number of preamble iterations.

[0159] 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.)

[0160] 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.

[0161] 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.

[0162] 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.

[0163] 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.

[0164] 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 11. 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.

[0165]

[0166] 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.

[0167] FIG. 11 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. 11 illustrates a RACH slot and RO when a PRACH setting index 9 is provided through a RACH setting for a cell on FR2 and an unpaired spectrum.

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

[0169] 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).

[0170] 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.

[0171] 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.

[0172] 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.

[0173] 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.

[0174] 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.

[0175] 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.

[0176] Figure 12 illustrates an example of PDSCH time domain resource allocation by PDCCH and an example of PUSCH time domain resource allocation by PDCCH.

[0177] 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).

[0178] 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.

[0179] 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.

[0180] 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.

[0181] One or more CORESETs can be configured for the UE, and multiple CORESETs can overlap in the time / frequency domain.

[0182] 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.

[0183] 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.

[0184] 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.

[0185] -searchSpaceId: Represents the ID of the SS set.

[0186] -controlResourceSetId: Represents the CORESET associated with the SS set.

[0187] -monitoringSlotPeriodicityAndOffset: Represents the PDCCH monitoring period interval (in slots) and the PDCCH monitoring interval offset (in slots).

[0188] -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.

[0189] -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).

[0190] -searchSpaceType: Indicates whether the SS type is CSS or USS.

[0191] - DCI Format: Indicates the DCI format of the PDCCH candidate.

[0192] 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.

[0193] 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.

[0194] 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.

[0195] The following enhancement techniques may be considered.

[0196] 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.

[0197] 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

[0198] Specify the following techniques in spatial and power domains

[0199] 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).

[0200] 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.

[0201] Specify mechanism(s) to prevent legacy UEs camping on cells adopting the Rel-18 NES techniques, if necessary.

[0202] Specify conditional handover (CHO) procedure enhancement(s) in case source / target cell is in NES mode.

[0203] Specify inter-node beam activation and enhancements on restricting paging in a limited area.

[0204] If necessary, specify the corresponding radio resource management / radio frequency (RRM / RF) core requirements for the above features.

[0205] 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.

[0206] Figure 13 illustrates the operation procedure in a BS that supports network energy saving (NES) technology.

[0207] 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.

[0208] 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.

[0209] 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).

[0210] Inter-system energy saving solution: An NG-RAN node owning a capacity booster cell can autonomously switch the cell to an inactive state.

[0211] > 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.

[0212] 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.

[0213] 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.

[0214] 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.

[0215] Figure 14 is an example of a process for carrier aggregation (CA) operation using an SSB-less secondary cell (SCell).

[0216] 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.

[0217] On-demand SSB

[0218] 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 perform transmissions when an on-demand SSB process is involved. The above on-demand SSB process can be triggered through one of the following methods.

[0219] 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);

[0220] 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

[0221] 3) Signal whether SSB is transmitted for the corresponding SCell through SCell enable / disable (enable / disable) signaling.

[0222] 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.

[0223] SIB1 transmission on demand

[0224] 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.

[0225] 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).

[0226] FIGS. 15 through 17 illustrate custom SIB1 transmission scenarios related to some implementations of the present specification.

[0227] 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.

[0228] 1) Scenario 1: As illustrated in FIG. 14, 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).

[0229] 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) on Cell #1 requesting SIB1 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).

[0230] 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) on Cell #2 requesting SIB1 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 for Cell #2 on Cell #1 or Cell #2 (or without transmitting the DL signal / channel).

[0231] 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.

[0232] - Cell A (= Cell#1): A cell that is periodically transmitting at least its own SIB1.

[0233] - NES cell (= Cell#2): A cell that may transmit SIB1 in response to UL WUS from a UE.

[0234] 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.

[0235] 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.

[0236] - The UE can recognize that it is an NES cell through the SIB and / or WUS configuration information (provided by Cell A).

[0237] - 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).

[0238] - 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.

[0239] - 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.

[0240] 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.

[0241] - RRC messages transmitted from Cell A (e.g., SIB1 or other system information block, RRC release message),

[0242] - DCI transmitted over Cell A or NES cell,

[0243] - Msg2 / Msg4 (via the 4-stage random access process) or MsgB (via the 2-stage random access process) transmitted from Cell A

[0244] - The center frequency of the PBCH / MIB / SSB transmitted over the NES cell, or

[0245] - Information that is pre-defined / pre-configured in the specifications.

[0246] In the description of some implementations of this specification, "frequency band" may be replaced with band, carrier, serving cell, BWP, etc.

[0247] Qausi Co-Location (QCL)

[0248] 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.

[0249] > 'typeA': {Doppler shift, Doppler spread, average delay, delay spread},

[0250] > 'typeB': {Doppler shift, Doppler spread},

[0251] > 'typeC': {Doppler shift, average delay},

[0252] > 'typeD': {Spatial Rx parameter}

[0253] 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).

[0254] 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. Each 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 the 'Transmission Configuration Indication' among the fields within the DCI that schedule the PDSCH, the TCI state index corresponding to each code point constituting the field is activated by the medium access control (MAC) control element (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 DL RSs and UL RSs, or between UL RSs and UL RSs, may be permitted. For example, SRS, PUSCH DM-RS, or PUCCH DM-RS may be UL RSs associated with the TCI state. The following is part of the RRC information element (IE) TCI-State, where the IETCI-State associates one or two DL RSs with the corresponding QCL type.

[0255]

[0256] In the table above, the bwp-Id in the QCL-Info field indicates the DL BWP where the RS is located, and if the bwp-Id field is absent, the RS is located in the DL BWP to which the TCI-State is applied by the UE. The cell in the QCL-Info field is the serving cell of the UE where the referenceSignal is set, and if the cell field is absent, the referenceSignal is set to the serving cell to which the TCI-State is applied by the UE. The referenceSignal in the QCL-Info field is a reference signal that provides quasi-co-location information as specified in Section 5.1.5 of 3GPP TS 38.214. The qcl-Type in the QCL-Info field is the QCL type specified in Section 5.1.5 of 3GPP TS 38.214, and is set to typeA, typeB, typeC, or typeD.

[0257] In the table above, additionalPCI in the TCI-State field represents the physical cell IDs (PCIs) of the SSBs when the referenceSignal is set as an SSB for both QCL-Type1 and QCL-Type2. If the field cell exists, additionalPCI refers to the PCI value in the list set using additionalPCI-ToAddModList in the serving cell indicated by the field cell; otherwise, it refers to the PCI value set in the list additionalPCI-ToAddModList in the serving cell to which the TCI-State is applied by the UE. When the field additionalPCI exists, the field cell for qcl-Type1 and qcl-Type2 is set to the same value if it exists. pathlossReferenceRS-Id is the ID of the reference signal (e.g., CSI-RS or SSB) used for PUSCH, PUCCH, and SRS path loss estimation. This field pathlossReferenceRS-Id refers to an element within the list set using pathlossReferenceRSToAddModList in the serving cell and UL BWP to which the TCI state is applied by the UE. qcl-Type1 and qcl-Type2 are QCL information for the TCI state as specified in Section 5.1.5 of 3GPP TS 38.214. The tag-Id-ptr within the TCI-State field indicates the timing advance group (TAG) associated with this TCI state. Value n0 represents the TCI state associated with the TAG indicated by tag-Id, and value n1 represents the TCI state associated with the TAG indicated by tag2-Id, and tag-Id-ptr refers to the TAG of the serving cell to which the state TCI state is applied. tci-StateId is the ID number of the TCI state.The ul-PowerControl within the TCI-State field sets the power control parameters for PUCCH, PUSCH, and SRS for this TCI state. This field TCI-State exists only if ul-powerControl is not set in any BWP-Uplink-Dedicated of the corresponding serving cell. This field TCI-State references the elements of the list set using uplink-PowerControlToAddModList in the serving cell where dl-OrJointTCI-StateToAddModList is set. For each serving cell, ul-powerControl is set in each TCI-State that is set or referenced in each DL BWP's dl-OrJointTCI-StateList, or is not set in any TCI-State that is set or referenced in any DL BWP's dl-OrJointTCI-StateList.

[0258] Adaptation of common signal / channel transmissions

[0259] It may be considered that the BS reduce energy consumption by controlling common signal / channel transmissions such as SSB, PRACH, and paging. While completely turning off the SSB can significantly reduce the energy consumption of the BS, the absence of an SSB that performs functions such as time / frequency synchronization or radio resource management (RRM) measurement may result in unstable operation of the cell from the UE's perspective. Considering this, the energy saving effect of the BS can be achieved by changing the transmission pattern of the SSB (e.g., transmission periodicity, periodicity per SSB candidate index(s), SSB candidate index(s) transmitted within one transmission period, transmission power, etc.) depending on the situation.

[0260] In the case of PRACH resources, for contention-based random access (CBRA), energy consumption can increase because the BS always attempts to receive from the configured PRACH resources, as it is unknown when the UE will transmit PRACH. Considering this, the BS can save energy by applying methods to adjust the amount of PRACH resources (e.g., adjusting the periodicity of the PRACH resources, pre-configuring PRACH resource set #1 and PRACH resource set #2 and adjusting the amount of resources through instructions such as whether to turn on only one set or both sets, or providing the corresponding amount of PRACH resources for each SSB index uniformly or non-uniformly).

[0261] In the case of paging, conventionally, paging frames (PF) and / or paging occasions (PO) were distributed along the time axis within a DRX cycle (or paging cycle), and UEs attempted to receive paging at specific PF / POs derived from their ID-based formulas. From a BS perspective, if paging was to be transmitted to multiple UEs simultaneously, it could be necessary to transmit paging while frequently breaking the system. To reduce the resulting BS energy consumption, one can consider placing the PF and / or PO for paging reception as close to the time axis as possible, or distributing frequency axis resources differently within the same timeframe.

[0262] With respect to SSB adaptation, two types of SSBs may be considered in this specification according to Example 1, Example 2, or Example 3. The Type 1 SSB and Type 2 SSB mentioned in some implementations of this specification described below may be SSBs according to Example 1, Example 2, or Example 3.

[0263] * Example 1) On-demand SSB on the first cell, transmission initiated by a BS instruction or a request from the UE

[0264] Type 1 SSB (or always-on SSB (AO-SSB)): This may refer to an SSB that is periodically transmitted on a first cell or a second cell. If the periodicity, etc., for the SSB is determined / defined / set, the SSB may be continuously transmitted at that period (without an ON period or OFF period, or without activation or deactivation). If Type 1 SSB refers to an SSB transmitted on a first cell, the first cell may be a timing reference cell. If Type 1 SSB refers to an SSB transmitted on a second cell, the second cell may be in an intra-band or inter-band carrier aggregation (CA) relationship with the first cell, and (particularly in an inter-band CA environment) the second cell may be set as a timing reference cell for the first cell, or (particularly in an intra-band CA environment) the second cell may be determined / defined as a timing reference cell for the first cell (e.g., any cell, PCell, or PSCell within the same timing advance group (TAG). Additionally, only the following Type 2 SSB may be transmitted on the first cell without a Type 1 SSB.

[0265] Type 2 SSB (or on-demand SSB (OD-SSB)): As described below with reference to 3GPP TS 38.331, an od-ssb configuration may be set / provided for a serving cell. It may refer to an SSB in which transmission on the first cell is enabled by instructions from the BS (via RRC / MAC-CE / DCI, etc.). Or it may refer to an SSB in which transmission is enabled by a request from the UE. For the activated SSB, deactivation of the SSB may be explicitly indicated through RRC / MAC-CE / DCI, etc., or the number of transmissions or transmission period may be set / instructed through RRC / MAC-CE / DCI that indicates SSB activation, and the SSB may be deactivated after the number of transmissions or transmission period has passed, or there may be a pre-set / defined number of transmissions or transmission period, and the SSB may be deactivated after the number of transmissions or transmission period has passed after the SSB is activated, or (if the first cell is SCell) the SSB may be deactivated when the activation of the first cell is completed (or when the CSI report for the first cell is successfully reported), or (if the first cell is SCell) the SSB may be deactivated when the first cell is deactivated, or (if the first cell is PCell) the SSB may be deactivated after a handover is performed, or the SSB may be deactivated at the request of the UE.

[0266] In Example 1, the case where only OD-SSB can be transmitted and AO-SSB cannot be transmitted for one cell is named Case #1, and the case where both AO-SSB and OD-SSB can be transmitted is named Case #2.

[0267] In addition, when the OD-SSB of Example 1 can have the following SSB parameters set within the od-ssb-config information element (IE), multiple od-ssb-configs can be set, or it can be set in the form of a list having multiple values ​​of one or more of the SSB parameters below. When multiple od-ssb-configs are set, each od-ssb-config has an index value, and one of the index values ​​can be indicated via RRC / MAC-CE / DCI to enable / disable it. Alternatively, when it can be set in the form of a list having one or more of the SSB parameters, the OD-SSB can be enabled / disabled by indicating via RRC / MAC-CE / DCI which value within the list is actually applied.

[0268] The physical cell identity of the SS / PBCH blocks is indicated by od-ssb-physCellId if provided; otherwise, it is indicated by the physCellId in ServingCellConfigCommon.

[0269] The indices of the SS / PBCH blocks being transmitted are indicated by the RRC / MAC CE / DCI from the candidate values ​​provided by od-ssb-PositionsInBurst if provided; otherwise, they are indicated by ssb-PositionsInBurst.

[0270] The frequency positions of the SS / PBCH blocks are indicated by the od-absoluteFrequencySSB if provided; otherwise, they are indicated by the absoluteFrequencySSB.

[0271] The subcarrier spacing (SCS) setting for SS / PBCH blocks is indicated by od-ssbSubcarrierSpacing if provided, otherwise by ssbSubcarrierSpacing.

[0272] The power of the SS / PBCH blocks is determined by od-ss-PBCH-BlockPower if provided, otherwise by ss-PBCH-BlockPower.

[0273] The transmission periodicity of SS / PBCH blocks is indicated by RRC / MAC CE / DCI from candidate values ​​determined by od-ssb-Periodicity.

[0274] Half frames for the transmission of SS / PBCH blocks are determined based on the instructions of the RRC / MAC CE / DCI. The transmission of SS / PBCH blocks is within frames containing an SFN determined by (SFN + SFN_offset)*10 mod P = 0, where P is the periododicity of the transmission of SS / PBCH blocks, and SFN_offset is the SFN offset indicated by the RRC / MAC CE / DCI from the candidate values ​​provided by od-ssb-sfn-Offset if provided, otherwise SFN_offset = 0. Within the frame, the index of the half frame containing the transmission of SS / PBCH blocks is indicated by the RRC / MAC CE / DCI from the candidate values ​​provided by od-ssb-halfFrameIndex if provided, otherwise the index is 0.

[0275] Among the SSB-related parameters mentioned in this specification, physCellId, ssb-PositionsInBurst, absoluteFrequencySSB, ssbSubcarrierSpacing, ss-PBCH-BlockPower, and ssb-PeriodicityServingCell, which are provided through ServingCellConfigCommon for the cell (and are not provided through OD-SSB-related settings), may be SSB-related parameters provided for AO-SSB and may be used as parameters for OD-SSB depending on the od-ssb settings. Among the SSB-related parameters mentioned in this specification, it may refer to parameters provided through OD-SSB-related settings (e.g., od-physCellId, od-ssb-PositionsInBurst, od-absoluteFrequencySSB, od-ssbSubcarrierSpacing, od-ss-PBCH-BlockPower, od-ssb-Periodicity, od-ssb-sfn-Offset, od-ssb-halfFrameIndex).

[0276] FIG. 18 is part of an RRC configuration used to provide on-demand SSB configuration. In particular, FIG. 18 is part of the RRC information element (IE) CellGroupConfig defined in 3GPP TS 38.331 V19.0.0. IECellGroupConfig is used to configure a master cell group (MCG) or a secondary cell group (SCG). A cell group consists of one MAC entity, logical channels with associated RLC entities, a primary cell (SpCell), and one or more secondary cells (SCell). OD-SSB related configuration can be provided through the SCellConfig field within IECellGroupConfig. Referring to FIG. 18, the parameter od-ssb-absoluteFrequency indicates the frequency when the OD-SSB frequency is different from the absoluteFrequencySSB set in the IEFrequencyInfoDL for the corresponding serving cell, and additional restrictions described in Section 4.4 of 3GPP TS 38.213 apply. The parameter od-ssb-ConfigToAddModList is a list of OD-SSB configurations for the corresponding serving cell, and the network sets up to one OD-SSB frequency different from the serving cell SSB frequency for said OD-SSB configurations. The parameter od-ssb-halfFrameIndex indicates whether the OD-SSB is within the first half frame or the second half frame of the frame, and if the od-ssb-halfFrameIndex field is absent, the UE applies a value of 0.The parameter od-ssb-PBCH-BlockPower indicates the average energy per resource element (EPRE) in dBm of the resource elements that carry secondary synchronization signals used by the network for OD-SSB transmission, and if this field is absent, the UE applies the value ss-PBCH-BlockPower configured in IEServingCellConfigCommon. IEServingCellConfigCommon is used to configure cell-specific parameters of a UE's serving cell, and this IE includes parameters typically obtained from SSBs, MIBs, or SIBs when the UE connects to that cell from the IDLE. Through IEServingCellConfigCommon, the network provides this information via dedicated signaling when configuring the UE with SCells or additional cell groups (e.g., SCG).ss-PBCH-BlockPower in IEServingCellConfigCommon is the average EPRE of the resource elements that carry secondary synchronization signals in dBm that the network used for SSB transmission. The parameter od-ssb-SFN-Offset is the SFN offset from the SFN satisfying (SFN index * 10) modulo (OD-SSB periodicity) = 0, and the network sets this field according to the field od-ssb-Periodicity so that the indicated system frame does not exceed the OD-SSB period. If the field od-ssb-SFN-Offset is non-existent, the UE applies a value of 0. The parameter od-ssb-SubcarrierSpacing indicates the subcarrier spacing of the OD-SSB, and only the following values ​​are applicable depending on the frequency used: 15 or 30 kHz for FR1, 120 or 240 kHz for FR2-1 or FR2-NTN, and 120, 480, or 960 kHz for FR2-2. If the field od-ssb-SubcarrierSpacing is absent, the UE applies the value subcarrierSpacing set in the IEBWP. The IEBWP is used to set general parameters for the bandwidth part. Among the fields within the OD-SSB, the field labeled ODssbAOssb is mandatory if the absoluteFrequencySSB of the corresponding serving cell is absent, and optional otherwise. Among the fields in OD-SSB, the field marked as ODssbOnly exists optionally if the absoluteFrequencySSB of the corresponding serving cell does not exist, and does not exist otherwise.

[0277] * Example 2) A method in which one or more SSB settings are set and an SSB corresponding to one of the SSB settings can be transmitted by a BS instruction or a request from a UE. In this case, at least the SSB periodicity values ​​may differ between the different SSB settings, and adaptation to the SSB periodicity may be performed by changing the activated SSB setting.

[0278] Type 1 SSB: This may refer to a reference configuration among the configured SSB configurations, or an SSB configuration with the largest SSB period value set. An SSB corresponding to that reference configuration may be called a Type 1 SSB. If an SSB configuration corresponding to a Type 2 SSB is not enabled, an SSB configuration corresponding to a Type 1 SSB may be enabled. Conversely, if an SSB configuration corresponding to a Type 2 SSB (or an SSB configuration not corresponding to a Type 1 SSB) is enabled, an SSB configuration corresponding to a Type 1 SSB may be disabled. Or, if the SSB occasions set based on a specific (reference) setting among the set SSB settings (referred to as “reference SSB occasions” for convenience) are a subset of the SSB occasions set based on another setting (referred to as “extended SSB occasions” for convenience), the reference SSB occasions may be defined as Type 1 SSB (regardless of the actual active SSB setting), and in this case, Type 2 SSB may be defined as the remaining SSB occasions among the extended SSB occasions (included in the actual active setting) excluding the reference SSB occasions.

[0279] Type 2 SSB: In addition to the SSB settings corresponding to Type 1 SSB, one or more SSB settings for Type 2 SSB may be set, and when the SSB settings corresponding to Type 2 SSB are activated, all SSBs belonging to the activated SSB settings may be defined as Type 2 SSBs. Alternatively, if the SSB periods set based on a specific (reference) setting among the configured SSB settings (referred to as “reference SSB periods for convenience”) are a subset of the SSB periods set based on another setting (referred to as “extended SSB periods for convenience”), the reference SSB periods may be defined as Type 1 SSBs (regardless of the actual activated SSB settings), and in this case, Type 2 SSBs may be defined as the remaining SSB periods among the extended SSB periods (included in the actual activated settings) excluding the reference SSB periods. One or more of the corresponding SSB settings may be enabled by a directive from the BS (via RRC / MAC-CE / DCI) or by a request from the UE. For the enabled SSB setting, the SSB may be disabled if the disablement is explicitly instructed via RRC / MAC-CE / DCI, etc., or if the number of transmissions or transmission intervals are set / instructed in the RRC / MAC-CE / DCI that instructs the SSB activation and the SSB is disabled after the number of transmissions or transmission intervals are set / instructed, or if there is a pre-set / defined number of transmissions or transmission intervals and the SSB is disabled after the number of transmissions or transmission intervals are set / instructed, or if the SSB is disabled when the activation for the first cell is completed (or when the CSI report for the first cell is successfully reported) (if the first cell is SCell), or if the SSB is disabled when the first cell is disabled (if the first cell is SCell), or if the SSB is disabled after a handover is performed (if the first cell is PCell), or if the SSB is disabled at the request of the UE.

[0280] * Example 3) A method in which one or more SSB settings are configured and an SSB corresponding to one of the SSB settings can be transmitted by a BS instruction or a request from a UE. In this case, there exists an SSB (i.e., Type 1 SSB) that is continuously and periodically transmitted regardless of the activation (deactivation) of the SSB setting(s), and the settings of an additional SSB to be transmitted to the SSB can be activated (deactivated). At least the SSB period value or SSB time pattern may differ between different SSB settings, and adaptation to the SSB period may be performed by changing the activated SSB setting.

[0281] Type 1 SSB: May refer to an SSB corresponding to the default SSB setting. The Type 1 SSB can be guaranteed to transmit continuously and periodically regardless of the activation (or deactivation) of the SSB setting(s) corresponding to the Type 2 SSB.

[0282] Type 2 SSB: One or more SSB settings for Type 2 SSB may be configured. One of these one or more SSB settings may be enabled by a directive from the BS (via RRC / MAC-CE / DCI) or by a request from the UE. For the enabled SSB setting, the SSB may be disabled if the disablement is explicitly instructed via RRC / MAC-CE / DCI, etc., or if the number of transmissions or transmission interval is set / instructed in the RRC / MAC-CE / DCI that instructs the SSB activation and the SSB is disabled after the number of transmissions or transmission interval has elapsed, or if there is a pre-set / defined number of transmissions or transmission interval and the SSB is disabled after the number of transmissions or transmission interval has elapsed following the SSB activation, or if the first cell is SCell and the SSB is disabled when the activation for the first cell is completed (or when a CSI report for the first cell is successfully reported), or if the first cell is SCell and the SSB is disabled when the first cell is disabled, or if the first cell is PCell and the SSB is disabled after a handover is performed, or if the SSB is disabled at the request of the UE. When one of the SSB settings for a Type 2 SSB is enabled, the SSB with the corresponding SSB setting applied is transmitted. When a default SSB setting for a Type 1 SSB is enabled, an SSB with that default SSB setting applied is transmitted (instead of an SSB setting corresponding to a Type 2 SSB). The SSB setting at this time may include only an SSB period, and this behavior is called SSB period adaptation.

[0283] As in the above embodiments, a type 2 SSB may mean an SSB that cannot assume continuous periodic transmission.

[0284] ■ Method #1. SSB adaptation for NES

[0285] In this specification, 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 as RACH config for convenience. Through the RACH config, RACH occasions (RO) on a specific time / frequency can be configured. In this specification, RACH config may also be used as RO. Additionally, the BS can configure the PRACH preamble format, the time axis position of the RO (e.g., period / offset of the RO or "RACH slot containing the RO," frame / subframe / slot / symbol index where the RO or "RACH slot containing the RO" starts or is included), and the duration of the RO or "RACH slot containing the RO" by setting / instructing the UE a RACH configuration index (RCI) value. For example, a specific RCI value may be set / instructed by the parameter prach-ConfigurationIndex (set by RRC signaling and may be a value between 0 and 255), and the tables in Section 6.3.3.2 of the standard document 3GPP TS 38.211 (e.g., Tables 6.3.3.2-2, 6.3.3.2-3, and 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.

[0286] The ROs of the two categories assumed in this specification (for NES purposes) may be as follows.

[0287] Cat 1 RO: This is an RO configured for legacy UEs. In the present invention, a legacy UE (from an NES perspective) means a UE (Rel-19 UE and pre-Rel-19) that does not support RACH adaptation features (introduced in Rel-19 NES).

[0288] > Cat 2 RO: Cat 2 RO can be configured for NES purposes. For example, from the perspective of BS, energy of the BS can be saved by additionally controlling the enable / disable (or on / off) of Cat 2 RO while the BS pre-configures Cat 1 RO and Cat 2 RO and operates Cat 1 RO by default. It can be configured to have different time and / or frequency resources compared to Cat 1 RO. For example, one or more of values ​​such as frame-unit period(s) of a RACH slot containing Cat 2 RO, frame-unit offset(s) of a RACH slot containing Cat 2 RO, etc., may be additionally configured, and said period / offset value(s) may be values ​​configured separately and may be value(s) configured as delta values ​​from the period / offset value for Cat 1 RO. As another example, separate frequency-related parameter(s) for Cat 2 ROs may be additionally configured (e.g., the frequency axis RB-level offset between the lowest RO in the frequency domain and the UL BWP PRB index 0, which is set via the parameter msg1-FrequencyStart regarding the offset of the lowest PRACH transmission time in the frequency domain for a physical resource block (0), and the number of ROs being FDMed, which is set via the parameter msg1-FDM regarding the number of frequency domain multiplexed (FDM) PRACH transmission times in a single time instance). As yet another example, the preceding examples may be applied to further configure a (time axis) muting / masking pattern that invalidates some Cat 2 RO resources among virtual Cat 2 RO resources with different time and / or frequency resources from Cat 1 ROs. With such a muting / masking pattern applied, the remaining ROs, excluding the invalidated ROs, can be determined as Cat 2 ROs.Alternatively, a separate time resource parameter may not be applied. If Cat 1 ROs and Cat 2 ROs partially or fully overlap on the time / frequency axis, the UE may determine that the Cat 1 RO is valid and the Cat 2 RO is invalid. The UE performs SSB-to-RO mapping for the Cat 1 ROs (e.g., a method of mapping a corresponding SSB index for each RO or a preamble index within an RO, as described in Section 8 of 3GPP TS 38.213 as an example) and SSB-to-RO mapping for the Cat 2 ROs separately. In other words, the UE performs SSB-to-RO mapping for the Cat 1 ROs and separately performs SSB-to-RO mapping for the Cat 2 ROs.

[0289] A UE may receive a Cat 2 RO configured for a single serving cell (or a single BWP or a single TRP). The UE may receive a signal from the BS regarding whether the Cat 2 RO is valid, active, or deactivated. This signaling method may include higher-level signaling such as RRC signaling, MAC CE, DCI, etc. Alternatively, the UE may recognize that the Cat 2 RO is invalid or deactivated if a certain timer (where the timer value may be predefined or configured / instructed) expires after receiving a signal that the Cat 2 RO is valid or active.

[0290] Some implementations of this specification regarding SSB-to-RO mapping, beam failure, and / or path-loss estimation when SSB adaptation using Type 1 SSB and / or Type 2 SSB is applied are described below.

[0291] <Method #1-1> SSB-to-RO Mapping Method

[0292] Referring to Section 8 of Release 18 of 3GPP TS 38.213, for paired spectrum (e.g., in the case of Frequency Division Duplex (FDD)) or supplementary uplink bands, all PRACH times are valid. For unpaired spectrum (e.g., in the case of Time Division Duplex (TDD),

[0293] If the UE is not provided with the RRC configuration tdd-UL-DL-ConfigurationCommon for the cell, the PRACH timing for the cell within the PRACH slot does not precede the SS / PBCH block within the PRACH slot, and at least N after the last SS / PBCH block received symbol. gap It is valid if it starts after the dog symbols, where N gap is provided in Table 6, and if the RRC parameter channelAccessMode ="semiStatic" is provided, it does not overlap with the set of consecutive symbols prior to the start of the next channel occupancy time (see 3GPP TS 37.213) that the UE does not transmit (if a UE is not provided RRC configuration dd-UL-DL-ConfigurationCommon for a cell, a PRACH occasion for the cell in a PRACH slot is valid if it does not precede a SS / PBCH block in the PRACH slot and starts at least N gap symbols after a last SS / PBCH block reception symbol, where N gapis provided in Table 6 and, ifchannelAccessMode= "semiStatic" is provided, does not overlap with a set of consecutive symbols before the start of a next channel occupancy time where the UE does not transmit (see 3GPP TS 37.213)).

[0294] The candidate SS / PBCH block index of the SS / PBCH block corresponds to the SS / PBCH block index provided by ssb-PositionsInBurstin, SIB1 or inServingCellConfigCommon or inSSB-MTC-AdditionalPCI, corresponding to the cell, as described in section 4.1 of 3GPP TS 38.213.

[0295] For each candidate cell configured by LTM-Config, if the UE is not provided with ltm-tdd-UL-DL-ConfigurationCommon, the PRACH timing within the PRACH slot for the candidate cell does not precede the SS / PBCH block within the said PRACH slot, and is at least N from the last SS / PBCH block reception symbol. gap It is valid if it starts after the dog symbols, where N gap It is provided in Table 6.

[0296] The SS / PBCH block index of the SS / PBCH block corresponds to the SS / PBCH block index provided by ssb-PositionsInBurst within LTM-SSB-Config corresponding to the above candidate cell.

[0297] If the UE is provided with tdd-UL-DL-ConfigurationCommon in the cell, the above PRACH time within the PRACH slot is valid in the following cases:

[0298] If it is within the UL symbol, or

[0299] >> It does not precede the SS / PBCH block within the aforementioned PRACH slot, and at least N after the last downlink symbol gap After the dog symbols and after the last SS / PBCH block symbol, at least N gap If you start after the dog symbols, here N gap It is provided in Table 6, and if channelAccessMode = "semiStatic" is provided, it does not overlap with a set of consecutive symbols before the start of the next channel occupancy time, which must not have any transmissions, as described in 3GPP TS 37.213 (it does not precede a SS / PBCH block in the PRACH slot and starts at least N gap symbols after a last downlink symbol and at least N gap symbols after a last SS / PBCH block symbol, where N gapis provided in Table 6, and ifchannelAccessMode= "semiStatic" is provided, does not overlap with a set of consecutive symbols before the start of a next channel occupancy time where there shall not be any transmissions, as described in 3GPP TS 37.213).

[0300] The candidate SS / PBCH block index of the SS / PBCH block corresponds to the SS / PBCH block index provided by ssb-PositionsInBurstin, SIB1 or inServingCellConfigCommon or inSSB-MTC-AdditionalPCI, corresponding to the cell, as described in section 4.1 of 3GPP TS 38.213.

[0301] For each candidate cell configured by LTM-config, if the UE is provided with ltm-tdd-UL-DL-ConfigurationCommon, the PRACH timing within the PRACH slot for the candidate cell is valid in the following cases:

[0302] If it is within the UL symbol, or

[0303] >> It does not precede the SS / PBCH block within the PRACH slot, and at least N from the last DL symbol gap It starts after the last symbols, and at least N from the last SS / PBCH block symbol. gap Starting after the dog symbols. Here, N gap It is provided in Table 6 (it does not precede a SS / PBCH block in the PRACH slot and starts at least N gap symbols after a last downlink symbol and at least N gap symbols after a last SS / PBCH block symbol, where N gap is provided in Table 6).

[0304] The SS / PBCH block index of the SS / PBCH block corresponds to the SS / PBCH block index provided by ssb-PositionsInBurst within LTM-SSB-Config corresponding to the above candidate cell.

[0305] The following table shows N for different preamble SCS u. gap These are examples of values.

[0306]

[0307] Referring further to Section 8 of Release 18 of 3GPP TS 38.213, for a Type-1 random access process, or for a Type-2 random access process having a separate configuration of PRACH periods from that of a Type-1 random access process, if N < 1, one SS / PBCH block index is mapped to 1 / N consecutive effective PRACH periods, and R contention-based preambles with consecutive indices associated with said SS / PBCH block index per effective PRACH period start from preamble index 0. If N ≥ 1, R contention-based preambles with consecutive indices associated with SS / PBCH block index n per effective PRACH period start from preamble index n*N total preamble Starting from / N, 0 ≤ n ≤ N-1, and N total 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.

[0308] 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 totalpreamble The type-1 random connection process is provided by totalNumberOfRA-Preambles.

[0309] 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.

[0310] Referring further to Section 8 of Release 18 of 3GPP TS 38.213, the SS / PBCH block indices provided by ssb-PositionsInBurst within SIB1, ServingCellConfigCommon, SSB-MTC-AdditionalPCI, or LTM-SSB-Config are mapped to valid PRACH times in the following order, and the parameters are described in 3GPP TS 38.211.

[0311] First, in the increasing order of preamble indices within a single PRACH period

[0312] Second, in increasing order of frequency resource indices for frequency-multiplexed PRACH periods

[0313] Third, in increasing order of time resource indices for time-multiplexed PRACH periods within the PRACH slot

[0314] Fourth, in increasing order of the indices for the PRACH slots

[0315] 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, ServingCellConfigCommon, SSB-MTC-AdditionalPCI, or LTM-SSB-Config. SSB Tx Obtains. After mapping cycles of an integer number of SS / PBCH block indices versus PRACH times within the associated interval, N SSB TxIf there is a set of PRACH occasions or PRACH preambles that are not mapped to N SS / PBCH block indexes, then no SS / PBCH block indexes are mapped to said set of PRACH occasions or PRACH preambles. SSB Tx SS / PBCH block indexes, no SS / PBCH block indexes are mapped to the set of PRACH occasions or PRACH preambles). An association pattern period includes one or more association periods and is determined so that a pattern between PRACH occasions and SS / PBCH block indexes repeats at most every 160 ms. If any PRACH occasions not associated with SS / PBCH block indexes exist after an integer number of association periods, they are not used for PRACH transmissions.

[0316] The following table illustrates the mapping between the PRACH setting period and the association period between the SS / PBCH block and the PRACH occasion.

[0317]

[0318] In summary, as described above, an existing 5G NR UE (e.g., a UE without a Type 2 SSB configured according to Example 1, Example 2, or Example 3, or a UE that does not support RACH adaptation-related features) can perform SSB-to-RO mapping through the following steps.

[0319] * Step 1: Determination of the valid RO (i.e., the valid PRACH time). The UE may determine the valid RO based on whether it is a paired spectrum or an unpaired spectrum, as described in Section 8 of the standard document 3GPP TS 38.213, and / or whether it is a pre-set UL symbol, and / or whether it is an RO that starts after the DL symbol or after the SSB by at least N_gap symbols (hereinafter, the condition is referred to as the “N_gap condition”).

[0320] * Step 2: Perform SSB-to-RO mapping. When there are SSB index(s) (or actually transmitted SSB (ATSSB) index(s)) determined based on the ssb-PositionsInBurst parameter as described in Section 8 of the standard document 3GPP TS 38.213, the UE can determine the corresponding SSB index for each RO based on the ATSSB index(s) and determine the PRACH association (pattern) interval based on this.

[0321] In some implementations of this specification, the following may be considered in relation to Step 1 and Step 2 for SSB-to-RO mapping.

[0322] <Case #1 of Example 1, i.e., the case of a cell where only OD-SSB can be transmitted without AO-SSB>

[0323] When determining the valid RO in Step 1, it must be determined which SSB criterion will be used to determine the N_gap condition. To determine the valid RO, SSBs based on any one of the following may be considered or applied.

[0324] No OD-SSB may be considered. The UE can perform RO validation under the assumption that all configured OD-SSBs are deactivated. The BS can attempt to receive PRACH from the determined valid ROs under the assumption that all configured OD-SSBs for the cell are deactivated.

[0325] Alternatively, all OD-SSBs may be considered. The UE and / or BS may determine the N_gap condition and perform RO validity checks under the assumption that all configured OD-SSBs are enabled. The BS may attempt to receive PRACH from the valid ROs determined by assuming that all OD-SSBs configured for the cell are enabled. According to this method, since the valid ROs are determined under the assumption that all OD-SSBs are enabled, the UE and the BS assume the same ROs regardless of whether the UE successfully receives the OD-SSB enable (disable) instruction provided by the BS. Since SSB-to-RO mapping is performed on the valid ROs, this method reduces the risk that the SSB-to-RO mapping may differ depending on whether the OD-SSB is enabled (disabled).

[0326] Alternatively, a specific OD-SSB transmission may be considered. The UE and / or BS may determine the N_gap condition and perform RO validation with a specific od-ssb-config index or a specific OD-SSB-related parameter applied among the configured multiple od-ssb-configs or multiple OD-SSB-related parameters (or assuming that the OD-SSB is enabled). For example, if multiple od-ssb-configs are configured, the UE and / or BS may determine the N_gap condition and perform RO validation with the SSB parameters configured within the od-ssb-config having the lowest or highest index value (or a separately configured index value) applied (i.e., assuming that the OD-SSB is enabled). As another example, the UE can determine the N_gap condition and perform RO validation assuming that the OD-SSB is activated, where the UE and / or BS has the largest (or smallest) period value among the OD-SSBs, or where the OD-SSB has the most ATSSB indexes set among the OD-SSBs.

[0327] In the SSB-to-RO mapping of Step 2, it must be determined which od-ssb-PositionsInBurst parameter (e.g., a parameter representing the ATSSB indices of OD-SSB as a bitmap) will be used to perform the SSB-to-RO mapping. To determine the association between ROs and SSB indices, any one of the following may be considered or applied. For example, for SSB-to-RO mapping, ATSSB index(s) based on any one of the following may be used.

[0328] If multiple od-ssb-configs are configured, SSB-to-RO mapping can be performed based on the od-ssb-PositionsInBurst parameter configured within the od-ssb-config that has the lowest or highest index value (or a separately configured index value).

[0329] Alternatively, if multiple od-ssb-PositionsInBurst parameters are configured within a single od-ssb-config, SSB-to-RO mapping can be performed based on the od-ssb-PositionsInBurst parameter having the lowest or highest index value (or a separately configured index value).

[0330] Alternatively, SSB-to-RO mapping can be performed under the assumption that the OD-SSB with the most ATSSB indexes set among the OD-SSBs is activated.

[0331] Alternatively, SSB-to-RO mapping can be performed based on the union of ATSSB indexes configured in multiple OD-SSBs. For example, for a certain serving cell, if there is OD-SSB #1 with the od-ssb-PositionsInBurst parameter set to '11110000' and OD-SSB #2 with the od-ssb-PositionsInBurst parameter set to '11001100', SSB-to-RO mapping can be performed based on the ATSSB indexes corresponding to their union, '11111100'. The advantage of this method is that an RO corresponding to a specific ATSSB index exists regardless of which OD-SSB is active. In addition, according to this method, since ATSSB indices are determined by assuming that all OD-SSBs are enabled, the UE and the BS assume the same association between the ATSSB indices and the valid ROs, regardless of whether the UE successfully receives the OD-SSB enable (disable) instruction provided by the BS. Therefore, according to this method, the risk that the SSB-to-RO mapping will differ depending on whether the OD-SSB is enabled (disabled) can be reduced.

[0332] <Case #2 of Example 1, i.e., the case of a cell in which both AO-SSB and OD-SSB can be transmitted>

[0333] When determining the valid RO in Step 1, it must be decided which SSB criterion will be used to determine the N_gap condition. To determine the valid RO, SSBs based on any one of the following may be considered or applied.

[0334] No OD-SSB may be considered. The UE can perform RO validity checks under the assumption that all configured OD-SSBs are deactivated and under the assumption that only AO-SSB transmissions are made. The BS can attempt to receive PRACH from valid ROs determined based only on A-SSB transmissions, assuming that all configured OD-SSBs for the cell are deactivated.

[0335] Alternatively, all OD-SSBs may be considered. The UE and / or BS may determine the N_gap condition and perform RO validity checks under the assumption that all configured OD-SSBs are active and under the assumption that AO-SSB transmission is assumed. For example, an RO in a PRACH slot may be determined to be valid based on starting at least N_gap symbols after the last SSB received symbol, without preceding the SSB in the PRACH slot, wherein the last SSB received symbol may be determined based on the union of the SSBs provided by the Type 1 SSB configuration (i.e., AO-SSBs) and the SSBs provided by the Type 2 SSB configuration(s) (i.e., OD-SSBs). The BS may attempt to receive PRACH on valid ROs determined based on the union of all OD-SSBs provided by all OD-SSB settings configured for the cell and the AO-SSBs provided by the AO-SSB settings. According to this method, since valid ROs are determined based on all configured OD-SSBs and AO-SSBs assuming that all OD-SSBs are enabled, the UE and the BS assume the same ROs regardless of whether the UE successfully receives the OD-SSB enable (disable) instruction provided by the BS. Since SSB-to-RO mapping is performed on valid ROs, this method reduces the risk that the SSB-to-RO mapping may differ depending on whether the OD-SSB is enabled (disabled).

[0336] Alternatively, a specific OD-SSB transmission may be considered. The UE and / or BS may determine the N_gap condition and perform RO validation with a specific od-ssb-config index or a specific OD-SSB-related parameter applied among the configured multiple od-ssb-configs or multiple OD-SSB-related parameters (or assuming that the OD-SSB is enabled), and assuming AO-SSB transmission. For example, if multiple od-ssb-configs are configured, the UE and / or BS may determine the N_gap condition and perform RO validation with the SSB parameters configured within the od-ssb-config having the lowest or highest index value (or a separately configured index value) applied (i.e., assuming that the OD-SSB is enabled), and assuming AO-SSB transmission. As another example, the UE and / or BS can determine the N_gap condition and perform RO validity check under the assumption that the OD-SSB is activated, which has the largest (or smallest) period value among the OD-SSBs, or which has the most ATSSB indexes among the OD-SSBs, and under the assumption that AO-SSB transmission is enabled.

[0337] In the SSB-to-RO mapping of Step 2, it must be determined which od-ssb-PositionsInBurst parameter (e.g., a parameter representing the ATSSB indices of OD-SSB as a bitmap) will be used to perform the SSB-to-RO mapping. To determine the association between ROs and SSB indices, any one of the following may be considered or applied. For example, for SSB-to-RO mapping, ATSSB index(s) based on any one of the following may be used.

[0338] SSB-to-RO mapping can be performed based only on the ATSSB index set for AO-SSB (i.e., the ssb-PositionsInBurst parameter).

[0339] Alternatively, SSB-to-RO mapping can be performed based on the ATSSB indexes of the AO-SSB or OD-SSB that has the highest number of ATSSB indexes among the AO-SSB and OD-SSB. For example, if the number of ATSSB indexes set in the AO-SSB is 3 and the number of ATSSB indexes set in the OD-SSB is 4, SSB-to-RO mapping can be performed based on the ATSSB indexes set in the OD-SSB.

[0340] Alternatively, SSB-to-RO mapping can be performed based on the union of ATSSB indices set for AO-SSB and various OD-SSBs. For example, for a certain serving cell, if there is OD-SSB #1 with the od-ssb-PositionsInBurst parameter set to '11110000', OD-SSB #2 with the od-ssb-PositionsInBurst parameter set to '11001100', and AO-SSB with the ssb-PositionsInBurst parameter set to '11110011', SSB-to-RO mapping can be performed based on the ATSSB indices corresponding to the union '11111111'. The advantage of this method is that an RO corresponding to a specific ATSSB index exists even if any OD-SSB is enabled (disabled). In addition, according to this method, since the ATSSB indices set for the cell are determined by assuming that all OD-SSBs are enabled, the UE and the BS assume the same association between the ATSSB indices and the valid ROs, regardless of whether the UE successfully receives the OD-SSB enable (disable) instruction provided by the BS. Therefore, according to this method, the risk that the SSB-to-RO mapping will differ depending on whether the OD-SSB is enabled (disabled) can be reduced.

[0341] <In the case of SSB cycle adaptation as in Example 2 and / or Example 3>

[0342] When determining the valid RO in Step 1, it must be decided which SSB criterion will be used to determine the N_gap condition. The following may be considered or applied.

[0343] The UE and / or BS can determine the N_gap condition and perform RO validity check by assuming that the default SSB period is applied among multiple SSB periods (i.e., assuming that an SSB with a period set by the ssb-Periodicity parameter is transmitted).

[0344] Alternatively, the UE and / or BS may determine the N_gap condition and perform RO validation by assuming that an SSB of a specific period is transmitted among one or more additionally configured SSB periods (i.e., additional SSB period(s) configured by the addl-ssb-Periodicity parameter). The specific period may be a minimum (or maximum) period value or a specific period value pre-configured from the BS.

[0345] Alternatively, the UE and / or BS may determine the N_gap condition and perform RO validation by assuming that an SSB of a specific period is transmitted among the default SSB period (i.e., the period set by the ssb-Periodicity parameter) and one or more additionally set SSB periods (i.e., additional SSB period(s) set by the addl-ssb-Periodicity parameter). The specific period may be a minimum (or maximum) period value or a specific period value pre-set from the BS.

[0346] After performing SSB-to-RO mapping by applying the above methods (e.g., the methods of Example 1, Example 2, and / or Example 3), if an OD-SSB containing an ATSSB index not associated with a specific RO is activated, the UE may consider that there is no RO linked to that ATSSB index.

[0347] RO validation and SSB-to-RO mapping such as the above methods (e.g., methods of Example 1, Example 2, and / or Example 3) can be applied to Cat 1 RO (e.g., legacy RO) and Cat 2 RO (e.g., NES RO), respectively.

[0348] If RO validation and SSB-to-RO mapping are performed by applying the above methods (e.g., methods of Example 1, Example 2, and / or Example 3) by assuming a specific OD-SSB or an SSB of a specific period, but an "OD-SSB different from the assumed SSB or an SSB of a different period" is transmitted (wherein the "OD-SSB different from the assumed SSB or an SSB of a different period" is conveniently referred to as an "additional SSB"), the UE may not transmit an RO within a distance of N_gap symbols from the additional SSB (i.e., an RO within N_gap symbols after receiving / transmitting the additional SSB). Alternatively, an RO within a distance of N_gap symbols from the additional SSB (i.e., an RO within N_gap symbols after receiving / transmitting the additional SSB) may be considered invalid. Alternatively, for an RO where the N_gap symbol condition with an additional SSB is not satisfied (e.g., an RO within N_gap symbols after receiving / transmitting an additional SSB), the UE may not perform a PRACH transmission or may consider the RO invalid. Here, RO may refer to Cat 1 RO and Cat 2 RO.

[0349] <Method #1-2> OD-SSB Functionality

[0350] Specific SSB index values ​​may be set separately from BS or determined by rules for at least the following uses.

[0351] Radio link monitoring as described in Section 5 of the standard document 3GPP TS 38.213

[0352] Link recovery monitoring (or beam failure detection / recovery) as described in Section 6 of the standard document 3GPP TS 38.213

[0353] For path loss estimation for UL power control as described in Section 7 of the standard document 3GPP TS 38.213

[0354] Reference signals for setting TCI-State / QCL-Info, etc. in standard documents 3GPP TS 38.331 and 3GPP TS 38.214

[0355] In some implementations of this specification, the following may be considered in relation to OD-SSB functions.

[0356] <Case #1 of Example 1, i.e., the case of a cell where only OD-SSB can be transmitted without AO-SSB>

[0357] ATSSB index values ​​may differ between OD-SSB configurations. If a specific SSB index is configured / determined for at least one of the above uses, but the SSB index is not transmitted due to the activation (or deactivation) of OD-SSBs, a problem may occur in performing the function corresponding to that use. Therefore, to resolve this problem, in some implementations of this specification, one of the following methods may be applied.

[0358] A UE may not expect that transmission of a specific SSB index will not be disabled due to the activation (or deactivation) of OD-SSBs, provided that a specific SSB index is configured / determined for at least one of the above uses. In other words, if a specific SSB index is configured / determined for at least one of the above uses and the specific SSB index is an ATSSB index associated only with OD-SSB(s), the UE does not expect that transmission of the SSB corresponding to the specific SSB index will be disabled. For example, if SSB index #1 is configured / determined for at least one of the above uses and SSB index #1 is included in the list of ATSSB indices associated with the od-ssb-config(s) for the cell, the UE may not expect that transmission of the SSB corresponding to SSB index #1 will be disabled. As another example, if SSB index #1 is configured for beam failure recovery and SSB index #1 is not included in the list of ATSSB indexes linked to the od-ssb-config, the UE may not expect the OD-SSB corresponding to the list of ATSSB indexes to be activated in the cell (or the UE may expect that the OD-SSB corresponding to the list of ATSSB indexes will not be activated in the cell). In this case, other od-ssb-configs that include the SSB index #1 as an ATSSB index may be activated.

[0359] Alternatively, when a certain OD-SSB is activated and a specific SSB index n is transmitted, another OD-SSB may be activated in place of that OD-SSB and the SSB-related parameters (e.g., periodicity, SFN offset, ATSSB index, etc.) may be updated. In this case, the UE can expect that the newly activated OD-SSB will always transmit SSB index n (or that the ATSSB index of that OD-SSB is configured to transmit SSB index n). Even if a certain OD-SSB is activated and a specific SSB index n is transmitted for at least one of the above uses, and then another OD-SSB is activated in place of that OD-SSB, if the specific SSB index n is also included in the ATSSB index(s) of that other OD-SSB, the transmission of the SSB corresponding to the specific SSB index n is not deactivated.

[0360] This method may also be applied to Case #2 of Example 1, that is, to a cell where both AO-SSB and OD-SSB can be transmitted. For example, if SSB index #1 is set / determined for at least one of the above uses and SSB index #1 is included in a list of ATSSB indices associated with the od-ssb-config(s) for the cell, and SSB index #1 is not an ATSSB index associated with the AO-SSB configuration for the cell (e.g., if SSB index #1 does not correspond to an ATSSB index provided by ssb-PositionsInBurst for the cell), the UE may not expect the SSB transmission corresponding to SSB index #1 to be disabled.

[0361] According to this method, if a specific SSB index is set for at least one of the above uses and the specific SSB index is an ATSSB index associated only with the OD-SSB setting(s), then the SSB transmission corresponding to the specific SSB index will not be deactivated after it has been activated, so there will be no problem in performing the function corresponding to the use(s) based on the specific SSB index.

[0362] <Case #2 of Example 1, i.e., the case of a cell in which both AO-SSB and OD-SSB can be transmitted>

[0363] If one or more of the following conditions are satisfied, and a specific SSB index n of AO-SSB is set / determined for the above use, the same use may also be applied to the same SSB index n of OD-SSB.

[0364] When the center frequency of AO-SSB and the center frequency of OD-SSB are the same

[0365] If the list of ATSSB indexes configured in AO-SSB is the same as the list of ATSSB indexes configured in OD-SSB

[0366] When the combined pattern of AO-SSB and OD-SSB is regular.

[0367] In this case, the regularity of the pattern may mean that when the transmission occasions of Type 1 SSB and Type 2 SSB are combined, a pattern of periodicity is formed. For example, if a Type 1 SSB has a period of 20 msec and is transmitted in even index frames, and a Type 2 SSB has a period of 20 msec and is transmitted in odd index frames, and both Type 1 SSB and Type 2 SSB are transmitted in half frames of the same index (e.g., the first half frame), then when the transmission occasions of Type 1 SSB and Type 2 SSB(s) are combined, a pattern of periodicity of 10 msec is formed, so it can be considered a regular pattern. On the other hand, even if a type 1 SSB has a period of 20 msec and is transmitted in even-indexed frames and a type 2 SSB has a period of 20 msec and is transmitted in odd-indexed frames, if the type 1 SSB and the type 2 SSB are transmitted in half frames of different indices (e.g., the type 1 SSB in the first half frame and the type 2 SSB in the second half frame), the sum of the transmission times of the type 1 SSB and the type 2 SSB(s) does not form a pattern of constant intervals with an interval of 5 msec or 15 msec, so it may be considered not to be a regular pattern.

[0368] Referring to Section 11.1 of 3GPP TS 38.213, for single-carrier operation in unpaired spectrum, for a set of symbols in a slot instructed to the UE for receiving an SS / PBCH block by ssb-PositionsInBurst in SIB1 or ssb-PositionsInBurst in ServingCellConfigCommon, or by ssb-PositionsInBurst in SSB-MTCAdditionalPCI associated with a physical cell ID having an active TCI state for PDCCH or PDSCH where the UE is not provided with dl-OrJointTCI-StateList, or for a set of symbols in a slot corresponding to an SS / PBCH block set for layer 1 (L1) beam measurement / reporting, if a transmission overlaps with any symbol from said set of symbols, the UE does not transmit PUSCH, PUCCH, or PRACH in said slot, and the above of said slot The set of symbols does not transmit an SRS. The UE does not expect the set of symbols in the slot to be indicated as an uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated when provided to the UE.If the UE is i) configured with multiple serving cells and directionalCollisionHandling-r16= 'enabled' is provided for some set of serving cells among the multiple serving cells, ii) indicates support for half-DuplexTDD-CA-SameSCS-r16 capability, and iii) is not configured to monitor PDCCH for the detection of DCI format 2_0 on any cell among the multiple serving cells, then by ssb-PositionsInBurst of SystemInformationBlockType1 or ssb-PositionsInBurst of ServingCellConfigCommon on the first cell among the multiple serving cells, or by ssb-PositionsInBurst in SSB-MTCA additionalPCI associated with the physical cell ID having an active TCI state for PDCCH or PDSCH, if the UE is not provided with dl-OrJointTCI-StateList. For a set of symbols in a slot instructed to the UE for receiving an SS / PBCH block, or for a set of symbols in a slot corresponding to an SS / PBCH block set for L1 beam measurement / reporting, if a transmission overlaps with any symbol in the set of symbols, the UE does not transmit PUSCH, PUCCH, or PRACH in the slot, and the UE does not transmit SRS in the set of symbols in the slot i) in any cell among the multiple serving cells if the UE cannot perform simultaneous transmission and reception as instructed by simultaneousRxTxInterBandCA among the multiple serving cells, and ii) in any one of the cells corresponding to the same band as the first cell, regardless of any capability instructed by simultaneousRxTxInterBandCA.

[0369] Referring to Section 11.1 of 3GPP TS 38.213 described above, in the SSB transmission area, UL signals / channels (e.g., SRS, PUSCH, PUCCH, PRACH) may not be transmitted. In some implementations of this specification, for a cell where a Type 2 SSB can be transmitted, the UE may perform the corresponding operation based on a Type 2 SSB with transmission enabled via RRC / MAC CE / DCI. In other words, in some implementations of this specification, when a specific Type 2 SSB is transmitted via RRC / MAC CE / DCI (as currently described in Section 11.1 of 3GPP TS 38.213), the UE may not transmit UL signals / channels (e.g., SRS, PUSCH, PUCCH, PRACH) in the area where the Type 2 SSB is transmitted.

[0370] In some implementations of this specification, to minimize the impact of Type 2 SSB on PUCCH transmission, the setting of Type 2 SSB may be restricted for cells to which PUCCH can be transmitted. Here, a cell to which PUCCH can be transmitted may mean at least one of the following cells.

[0371] PCell

[0372] PSCell

[0373] PUCCH-SCell: The SCell used when PUCCH can be transmitted via SCell instead of PCell in a CA environment.

[0374] PUCCH-sSCell: A SCell in which PUCCH can be transmitted based on a pattern set by RRC signaling or DCI instructions, etc.

[0375] FIG. 19 is an example of a signal transmission / reception flow between a first device (e.g., UE) and a second device (e.g., BS) according to some implementations of the present specification. Referring to FIG. 19, when multiple OD-SSB settings exist (Case #1) or when an AO-SSB setting and at least one OD-SSB setting exist (Case #2) (S1901), as in Method #1-1, the UE and BS may perform RO validity checks (e.g., determine whether the N_gap condition is satisfied) by assuming that a specific OD-SSB is activated (or assuming that all OD-SSBs are activated (deactivated)) (S1903). Additionally, the UE and BS perform SSB-to-RO mapping based on the union of the ATSSB indices of the specific OD-SSB setting or multiple OD-SSB settings (S1903). For example, when a specific OD-SSB is activated, the N_gap condition with the specific OD-SSB is determined (or, assuming all OD-SSBs are activated, the N_gap condition with all configured SSBs including all OD-SSB(s) is determined) to determine an effective RO, and the UE can transmit PRACH within the effective RO, and the BS can attempt to receive PRACH within the effective RO (S1905).

[0376] FIG. 20 is another example of a signal transmission / reception flow between a first device (e.g., UE) and a second device (e.g., BS) according to some implementations of the present specification. In particular, FIG. 20 illustrates a signal transmission / reception flow between a UE and a BS according to some parts of the present specification related to a TCI state among uses related to SSB functions. In the example of FIG. 20, a step indicated by a dotted arrow may be omitted, or it may mean a step whose execution or order does not affect the operation of the UE. Referring to FIG. 20, at least one OD-SSB setting may be provided for a cell without an AO-SSB setting (Case #1), or an AO-SSB setting and at least one OD-SSB setting may be provided for a cell (Case #2) (S2001). The BS may provide the UE with a setting regarding a TCI state (e.g., IETCI-state) containing reference signal information related to an SSB index (S2003). The reference signal information within the setting regarding the above TCI state may include the SSB index or the non-zero power (NZP) CSI-RS resource ID. In some implementations, the BS may provide the UE with an enable (disable) instruction regarding SSB transmission(s) associated with the OD-SSB setting(s) based on the above TCI state (S2005). For example, the BS may not disable the transmission of the SSB corresponding to the SSB index if the SSB index within the TCI state, or the reference signal of the NZP CSI-RS resource ID within the TCI state, and the QCLed SSB index are ATSSB indices associated only with the OD-SSB setting(s). The UE may apply the above TCI state (S2007).In some implementations, if the SSB index in the TCI state, or the SSB index QCLed with the reference signal of the NZP CSI-RS resource ID in the TCI state, is an ATSSB index associated only with the OD-SSB setting(s), the UE may apply the TCI state assuming that the transmission of the SSB corresponding to the SSB index is not deactivated.

[0377] The UE and BS can perform RO validity checks by assuming that a specific OD-SSB is activated (or assuming that all OD-SSBs are activated (deactivated)) (e.g., determining whether the N_gap condition is satisfied) (S1903). Additionally, the UE and BS perform SSB-to-RO mapping based on a specific OD-SSB setting or the union of ATSSB indices of multiple OD-SSB settings (S1903). For example, if a specific OD-SSB is activated, they determine whether the N_gap condition with the specific OD-SSB is satisfied (or determine whether the N_gap condition with all configured SSBs including all OD-SSB(s) is satisfied by assuming that all OD-SSBs are activated) and determine a valid RO, and the UE can transmit PRACH within the valid RO, and the BS can attempt to receive PRACH within the valid RO (S1905).

[0378] According to some implementations of the aforementioned specification, efficient RO validation and SSB-to-RO mapping operations can be performed for cells configured with a Type 2 SSB. Additionally, according to some implementations of the aforementioned specification, if an SSB index configured for a specific use corresponds only to an ATSSB index for OD-SSB(s), the SSB transmission corresponding to said SSB index is not deactivated, so no problem will occur in performing the function corresponding to said specific use.

[0379] ■ Method #2. Timing reference cell for a serving cell configured with on-demand SSB

[0380] The following table is an example of a portion of the RRC information element (IE) FrequencyInfoDL, extracted from 3GPP TS 38.331 V19.0.0. The IEFrequencyInfoDL provides the basic parameters of the downlink carrier and the transmission on said downlink carrier.

[0381]

[0382] The above IEFrequencyInfoDL may be included in the RRC configuration DownlinkConfigCommon or DownlinkConfigCommonSIB, which provides the cell's common downlink parameters. In the table above, the field absoluteFrequencyPointA indicates the absolute frequency position of the reference resource block (common resource block 0), and its lowest subcarrier is also known as Point A. The lower edge of the actual carrier is not defined by the field absoluteFrequencyPointA but is defined in the field scs-SpecificCarrierList. 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 PCell's cell-defining SSB (CD-SSB) is always on the sync raster. If frequencies are identifiable by their GSCN values, the frequencies are considered to be on the sink 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 field absoluteFrequencySSB is absent, the UE may obtain a timing reference from the SpCell or SCell, from the SpCell or SCell indicated by the referenceCell, or from the default cell, if applicable.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 SpCell or the SCell, respectively). The field frequencyBandList is a list containing only one frequency band to which this carrier(s) belong. The field referenceCell may indicate a reference cell, which is the cell that provides the timing reference and automatic gain control (AGC) source for the SSB-less SCell. If the reference cell is an SCell or a PSCell, it is an active SCell or an active PSCell. If this field is absent, the default cell is the reference cell. The field scs-SpecificCarrierList is a set of carriers for different subcarrier intervals (numerographies), defined in relation to point A, and the network sets scs-SpecificCarrier for at least each numerograph (subcarrier interval) used within the BWP.

[0383] The following table is a portion of IESSB-MTC, excerpted from 3GPP TS 38.331 V19.0.0. IESSB-MTC is used to set measurement timing settings, e.g., when the UE measures SSBs.

[0384]

[0385] In the table above, the duration in the SSB-MTC or SSB-MTC3 field is the duration of the measurement window in which to receive SS / PBCH blocks, and is given in units of the number of subframes. The periododicityAndOffset in the SSB-MTC or SSB-MTC3 field is the periododicity and offset of the said measurement window for receiving SS / PBCH blocks (see Section 5.5.2.10 of 3GPP TS 38.331), and the period and offset are given in units of the number of subframes. The pci-List in the SSB-MTC2, SSB-MTC4, or SSB-MTC5 field is the physical cell IDs that follow this SSB measurement timing configuration (SMTC). The pci-List in the SSB-MTC3 field is the integrated access and backhaul (IAB)-node These are PCIs that follow this SMTC and are used for discovery. The ssb-ToMeasure field within SSB-MTC3 is a bitmap regarding the set of SS blocks to be measured within the SMTC measurement period, such that the first / leftmost bit corresponds to SS block index 0 and the second bit corresponds to SS block index 1. In the bitmap of ssb-ToMeasure, a value of 0 indicates that the corresponding SS block is not measured, and a value of 1 indicates that the corresponding SS block is not measured (see 3GPP TS 38.215). If this field ssb-ToMeasure is not set, IAB mobile termination (IAB-MT) measures all SS blocks. Regardless of the value of this field ssb-ToMeasure, SS blocks outside the applicable SMTC are not measured.The offset in the SSB-MTC4 or SSB-MTC5 field is the offset of the measurement window for receiving SS / PBCH blocks (see Section 5.5.2.10 of 3GPP TS 38.331) and is given in units of the number of subframes. The periododicity in the SSB-MTC5 or SSB-MTC-AdditionalPCI field is the period of the measurement window for receiving SS / PBCH blocks (see Section 5.5.2.10 of 3GPP TS 38.331) and is given in units of the number of subframes. The ssb-PositionsInBurst in the SSB-MTC-AdditionalPCI field is a bitmap representing the time-domain positions of SS blocks transmitted within a half frame containing SS / PBCH blocks as defined in Section 4.1 of 3GPP TS 38.213, where the first / leftmost bit corresponds to SS / PBCH block index 0, and the second The bit corresponds to the expression for SS / PBCH block index 1. In the bitmap of ssb-PositionsInBurst, a value of 0 indicates that the corresponding SS / PBCH block is not transmitted, and a value of 1 indicates that the corresponding SS / PBCH block is transmitted. The ss-PBCH-BlockPower in the SSB-MTC-AdditionalPCI field is the average EPRE (in dBm) of the resource elements carrying the secondary synchronization signals used by the network for SSB transmission (see Section 7 of 3GPP TS 38.213).

[0386] As described above, if there is a cell in an existing NR system for which the SSB setting (e.g., the absoluteFrequencySSB parameter in IEFrequencyInfoDL in Table 8) is not set and the SSB measurement timing configuration (SMTC) setting (e.g., IESSB-MTC in Table 9) is not provided, the UE considers that cell to be an SSB-less cell. For example, referring to Table 8, the absoluteFrequencySSB parameter signals the frequency position where the SSB to be used for that serving cell is transmitted. However, if the absoluteFrequencySSB parameter is absent, the SSB-related parameters (e.g., ssb-PositionsInBurst, ssb-periodicityServingCell, and subcarrierSpacing in ServingCellConfigCommonIE) may also be absent for that serving cell. Additionally, if the absoluteFrequencySSB parameter is absent, the timing reference cell for the corresponding serving cell (or the target cell for which synchronization with time / frequency and / or AGC gain is obtained) may be determined by one of the following rules.

[0387] Rule #1: One of PCell, PSCell, or SCell is determined as the timing reference cell without separate signaling. In the case of SCell, the condition that it belongs to the same TAG as the corresponding serving cell and belongs to the same cell group may be satisfied.

[0388] Rule #2: A PCell, PSCell, or SCell set as the timing reference cell by a separate parameter (e.g., referenceCell) is determined as the timing reference cell. If no separate parameter is set, the default cell for the timing reference cell may be determined by a separate rule (e.g., the source cell of QCL type C) or by following Rule #1.

[0389] Rule #1 above may be applied to intra-band CA situations between an SSB-less cell and a timing reference cell, and Rule #2 may be applied to inter-band CA situations between an SSB-less cell and a timing reference cell (where they are in a co-location relationship).

[0390] In the following, several implementations of this specification regarding the method for determining the timing reference cell in Case #1 are described, where Case #1 is designated as the case in which AO-SSB is not transmitted for a single cell as previously defined. In this specification, OD-SSB may be replaced with the above-mentioned Type 2 SSB, and several implementations of this specification may be applied.

[0391] Section 4.1 of the standard document 3GPP TS 38.213 describes the determination of timing reference cells as follows:

[0392] In the case of a serving cell that does not transmit SS / PBCH blocks, the UE obtains time and frequency synchronization with the serving cell based on receptions of SS / PBCH blocks on the PCell or PSCell of the cell group for the serving cell, or on the SCell if applicable as described in 3GPP TS 38.133.

[0393] In some implementations of this specification, according to the following Alt 1 or Alt 2, a timing search cell for a cell where OD-SSB is set may be determined or time / frequency synchronization may be obtained.

[0394] * Alt 1: A separate upper-level parameter (e.g., absenceofTimingRefCell) is introduced.

[0395] If the above upper layer parameter is not set, in Case #1 for a cell with an OD-SSB set (e.g., when the absoluteFrequencySSB parameter is absent for a cell with an OD-SSB set), the UE obtains time / frequency synchronization (or timing reference) from the OD-SSB if the OD-SSB is active (or not deactivated) and is transmitting, and may not need to obtain time / frequency synchronization (or timing reference) for the serving cell if the OD-SSB is not active (or deactivated) and is not transmitting. Alternatively, if the OD-SSB is not active (or deactivated) and is not transmitting, the UE may not obtain time / frequency synchronization (or timing reference) for the serving cell.

[0396] Alternatively, if the above upper layer parameter is not set, in Case #1 for a cell where the OD-SSB is set (e.g., when the absoluteFrequencySSB parameter does not exist for a cell where the OD-SSB is set), the UE can obtain time / frequency synchronization (or timing reference) from the OD-SSB if the OD-SSB is active (or not deactivated) and is transmitting, and if the OD-SSB is not active (or deactivated) and is not transmitting, the UE can obtain time / frequency synchronization (or timing reference) from the serving cell (or the SSB of the serving cell determined by the above rule #1 or rule #2).

[0397] For example, if a separate higher-level parameter (absenceofTimingRefCell) is introduced according to Alt 1, the determination of the timing reference cell for a serving cell where OD-SSB is set can be defined in the standard document as follows:

[0398] If a UE is provided with an od-ssband absence of TimingRefCell for a serving cell, without transmission of SS / PBCH blocks on the serving cell, the UE is not required to acquire time and frequency synchronization with the serving cell. Otherwise, for a serving cell without transmission of SS / PBCH blocks, a UE acquires time and frequency synchronization with the serving cell based on receptions of SS / PBCH blocks on the PCell, or on the PSCell, or on an SCell if applicable as described in 3GPP TS 38.133, of the cell group for the serving cell.

[0399] * Alt 2: The timing reference cell is determined based on whether the timing reference cell is determined by the existing rule #1 and rule #2 without introducing a separate upper layer parameter.

[0400] If the timing reference cell is not determined by the existing rules #1 and #2, in Case #1 for a cell with an OD-SSB set (e.g., when the absoluteFrequencySSB parameter is absent for a cell with an OD-SSB set), the UE obtains time / frequency synchronization (or timing reference) from the OD-SSB if the OD-SSB is active (or not deactivated) and is transmitting, and may not need to obtain time / frequency synchronization (or timing reference) for the serving cell if the OD-SSB is not active (or deactivated) and is not transmitting. Alternatively, if the OD-SSB is not active (or deactivated) and is not transmitting, the UE may not obtain time / frequency synchronization (or timing reference) for the serving cell.

[0401] If the timing reference cell is determined by the existing Rule #1 and Rule #2, when Case #1 is true for a cell where the OD-SSB is set (e.g., when the absoluteFrequencySSB parameter is absent for a cell where the OD-SSB is set), the UE can obtain time / frequency synchronization (or timing reference) from the OD-SSB if the OD-SSB is active (or not deactivated) and is transmitting, and if the OD-SSB is not active (or deactivated) and is not transmitting, the UE can obtain time / frequency synchronization (or timing reference) from the serving cell (or the SSB of the serving cell determined by the above Rule #1 or Rule #2).

[0402] The meaning that the timing reference cell is not determined by the existing rule #1 above may mean that there is no cell (e.g., PCell or PSCell) that has an intra-band CA relationship with the cell where OD-SSB is set.

[0403] The meaning that the timing reference cell is not determined by the existing rule #2 above may mean at least one of the following.

[0404] There are no cells (e.g., PCell or PSCell) that have an inter-band CA relationship with the cell where OD-SSB is configured.

[0405] There are cells in an inter-band CA relationship, but the timing reference cell is not set by a separate parameter (e.g., referenceCell).

[0406] There are cells in an inter-band CA relationship, but the timing reference cell is not set by a separate parameter (e.g., referenceCell), nor is the timing reference cell determined by a separate rule (e.g., source cell of QCL type C).

[0407] For example, in the case of a timing reference cell without introducing separate upper-level parameters according to Alt 2, the determination of the timing reference cell for a serving cell with OD-SSB set can be defined in the standard document as follows:

[0408] For a serving cell without transmission of SS / PBCH blocks, a UE acquires time and frequency synchronization with the serving cell based on receptions of SS / PBCH blocks on the PCell, or on the PSCell, or on an SCell if applicable as described in 3GPP TS 38.133, of the cell group for the serving cell. Otherwise, for a serving cell configured without transmission of SS / PBCH blocks, the UE is not required to acquire time and frequency synchronization with the serving cell.

[0409] Alt 2 has the advantage of having less impact on the standard and reduced signaling overhead because it does not require the introduction of separate upper-layer parameters. On the other hand, Alt 1 introduces additional upper-layer parameters, but the existence of a timing reference cell can be specified regardless of specific conditions (e.g., whether the existing Rule 1 and Rule 2 in Alt 2 are satisfied), thus increasing the freedom of BS implementation, and if there is no timing reference cell, there is no need for a separate SSB transmission other than OD-SSB, which is advantageous in terms of NES gain.

[0410] FIG. 21 is another example of a signal transmission / reception flow between a first device (e.g., UE) and a second device (e.g., BS) according to some implementations of the present specification. In the example of FIG. 21, the step indicated by the dotted arrow may be omitted. Referring to FIG. 21, the BS may set an on-demand SSB for a serving cell for the UE, but may not set a separate timing reference cell or provide information about the timing reference cell (S2101). Before the OD-SSB is transmitted by BS signaling (at the request of the UE or by BS signaling), the UE may not need to perform time / frequency synchronization for the serving cell. On the other hand, if the OD-SSB is transmitted by the BS's OD-SSB enable signaling (at the request of the UE (S2103) or by BS signaling (S2105), the UE may perform time / frequency synchronization for the serving cell based on the OD-SSB (S2107).

[0411] According to some implementations of this specification, a timing reference cell can be determined for a cell in which a type 2 SSB is set, even if the type 2 SSB is not transmitted.

[0412] The aforementioned methods #1-1, #1-2, and #2 may be applied independently or in combination.

[0413] FIG. 22 is an example of a flow of operation in a UE according to some implementations of the present specification. The UE may perform operations according to some implementations of the present specification. The UE may include at least one transceiver; at least one processor; and at least one computer memory operably connected to said at least one processor and, when executed, storing instructions that cause said at least one processor to perform operations according to some implementations of the present specification. A processing device for the UE may include at least one processor; and at least one computer memory operably connected to said at least one processor and, when executed, storing 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 above UE, or in the above UE, the processing device, the computer-readable (non-transient) storage medium, and / or the computer program product, the operations may include: receiving a random access channel occasion (RO) related setting, a first synchronization signal block (SSB) related setting, and a second related SSB setting (S2201); determining valid ROs based on the RO related setting (S2203); and performing a physical random access channel (PRACH) transmission based on the valid ROs (S2205). At least the second SSB related setting may be an on-demand (OD) SSB setting.

[0414] FIG. 23 is an example of the flow of operations in a BS according to some implementations of the present specification. The BS may perform operations according to some implementations of the present specification. The BS may include at least one transceiver; at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations according to some implementations of the present specification. A processing device for the BS may include at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations according to some implementations of the present specification. A computer-readable (non-transient) storage medium may store at least one computer program including instructions that, when executed by at least one processor, cause the at least one processor to perform operations according to some implementations of the present specification. 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 above BS, or in the BS, the processing device, the computer-readable (non-transient) storage medium, and / or the computer program product, the operations may include: transmitting a random access channel occasion (RO) related setting, a first synchronization signal block (SSB) related setting, and a second related SSB setting (S2301); and attempting to receive a physical random access channel (PRACH) on valid ROs related to the RO related setting (S2305). At least the second SSB related setting may be an on-demand (OD) SSB setting.

[0415] In some implementations related to FIG. 19, FIG. 22, or FIG. 23, the valid ROs may be determined based on the union of the SSBs provided by the first SSB-related setting and the SSBs provided by the second SSB-related setting.

[0416] In some implementations related to FIG. 19, FIG. 22, or FIG. 23, the association between ROs and SSB indexes can be determined based on the union of SSB indexes provided by the first SSB related setting and SSB indexes provided by the second SSB related setting.

[0417] In some implementations related to FIG. 19, FIG. 22, or FIG. 23, the RO in the PRACH slot may be determined to be valid based on starting at least N_gap symbols after the SSB.

[0418] In some implementations related to FIG. 19, FIG. 22, or FIG. 23, the first SSB-related configuration may be provided by the radio resource control (RRC) information element ServingCellConfigCommon.

[0419] In some implementations related to FIG. 19, FIG. 22, or FIG. 23, the first SSB related setting may include the first RRC parameter ssb-PositionsInBurst.

[0420] The above second SSB related setting may include the second RRC parameter od-ssb-PositionsInBurst.

[0421] In some implementations related to FIG. 19, FIG. 22, or FIG. 23, the SSBs provided by the first SSB-related setting may be always-on SSBs provided without an activation command from the BS.

[0422] In some implementations related to FIG. 19, FIG. 22, or FIG. 23, the SSBs provided by the second SSB related setting may be determined based on at least one of the SSB period for OD-SSB, system frame number (SFN) offset, half frame index, or SSB locations within the burst.

[0423] FIG. 24 is another example of the flow of operations in a UE according to some implementations of the present specification. The UE may perform operations according to some implementations of the present specification. The UE may include at least one transceiver; at least one processor; and at least one computer memory operably connected to said at least one processor and, when executed, storing instructions that cause said at least one processor to perform operations according to some implementations of the present specification. A processing device for the UE may include at least one processor; and at least one computer memory operably connected to said at least one processor and, when executed, storing 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 above UE, or in the above UE, the processing device, the computer-readable (non-transient) storage medium, and / or the computer program product, the operations may include: receiving a setting related to a TCI state (S2401); determining that the transmission of an SSB associated with said SSB index is not deactivated based on the fact that the SSB index in said TCI state corresponds only to the actual transmitted SSB index provided by the OD-SSB related setting (S2403); and applying said TCI state (S2405) (based on said determination). For example, if the SSB index in said TCI state or the SSB index QCLed with the reference signal in said TCI state corresponds only to the ATSSB index provided by the OD-SSB setting (if no AD-SSB setting is provided or does not correspond to the ATSSB index provided by the AD-SSB setting), the UE may apply said TCI state assuming that the transmission of an SSB corresponding to said SSB index is not deactivated. For example, if the SSB index provided by the TCI state is an ATSSB index associated only with the OD-SSB, the UE can set a receive beam (e.g., a receive spatial filter) by assuming that the DM-RS for the PDSCH or PDCCH is in a QCL relationship with the SSB corresponding to the SSB index provided by the TCI state, under the assumption that the SSB corresponding to the SSB index is not deactivated.

[0424] FIG. 25 is another example of the flow of operations in a BS according to some implementations of the present specification. The BS may perform operations according to some implementations of the present specification. The BS may include at least one transceiver; at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations according to some implementations of the present specification. A processing device for the BS may include at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations according to some implementations of the present specification. A computer-readable (non-transient) storage medium may store at least one computer program including instructions that, when executed by at least one processor, cause the at least one processor to perform operations according to some implementations of the present specification. 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 above BS, or in the above BS, the processing device, the computer-readable (non-transient) storage medium, and / or the computer program product, the operations may include: transmitting a setting related to a TCI state (S2501); determining or assuming that the transmission of an SSB associated with the SSB index is not deactivated based on the fact that the SSB index within the above TCI state corresponds only to the actual transmitted SSB index provided by the OD-SSB related setting (S2503); and transmitting an SSB corresponding to the SSB index related to the above TCI state (S2505) (under the determination / assumption). The above BS determines that if the SSB index associated with the above TCI state corresponds only to the ATSSB index provided by the OD-SSB related setting, the transmission of the SSB corresponding to the above SSB index cannot be deactivated, and the OD-SSB setting providing the above SSB index as an ATSSB index is not deactivated (in situations where the above TCI state must be applied), or when deactivating the above OD-SSB setting, the SSB corresponding to the above SSB index can be transmitted by activating another OD-SSB setting providing the above SSB index as an ATSSB index.

[0425] 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.

[0426] Implementations of this specification may be used in wireless communication systems, BS or UE, or other equipment.

Claims

In a method performed by user equipment (UE), Receive a setting related to a random access channel occasion (RO), a setting related to a first synchronization signal block (SSB), and a second related SSB setting; Determine valid ROs based on the above RO-related settings; and Based on the above valid ROs, it includes performing physical random access channel (PRACH) transmission, and The above second SSB-related settings are on-demand (OD) SSB settings, and The above valid ROs are determined based on the union of the SSBs provided by the first SSB-related setting and the SSBs provided by the second SSB-related setting, method. In paragraph 1, Further comprising determining the association between ROs and SSB indexes based on the union of the SSB indexes provided by the first SSB-related setting and the SSB indexes provided by the second SSB-related setting. method. In paragraph 1, RO within the PRACH slot is determined to be valid based on starting at least N_gap symbols after the SSB, method. In paragraph 1, The above first SSB-related settings are provided by the radio resource control (RRC) information element ServingCellConfigCommon, method. In paragraph 4, The above first SSB-related setting includes the first RRC parameter ssb-PositionsInBurst, method. In paragraph 5, The above second SSB-related setting includes the second RRC parameter od-ssb-PositionsInBurst, method. In paragraph 1, The SSBs provided by the above-mentioned first SSB-related settings are always-on SSBs provided without an activation command from the BS, method. In paragraph 1, The SSBs provided by the above-mentioned second SSB-related settings are determined based on at least one of the SSB period for OD-SSB, system frame number (SFN) offset, half frame index, or SSB positions within an SSB burst, method. 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: Receive a setting related to a random access channel occasion (RO), a setting related to a first synchronization signal block (SSB), and a second related SSB setting; Determine valid ROs based on the above RO-related settings; and Based on the above valid ROs, it includes performing physical random access channel (PRACH) transmission, and The above second SSB-related settings are on-demand (OD) SSB settings, and The above valid ROs are determined based on the union of the SSBs provided by the first SSB-related setting and the SSBs provided by the second SSB-related setting, User device. 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: Receive a setting related to a random access channel occasion (RO), a setting related to a first synchronization signal block (SSB), and a second related SSB setting; Determine valid ROs based on the above RO-related settings; and Based on the above valid ROs, it includes performing physical random access channel (PRACH) transmission, and The above second SSB-related settings are on-demand (OD) SSB settings, and The above valid ROs are determined based on the union of the SSBs provided by the first SSB-related setting and the SSBs provided by the second SSB-related setting, Processing unit. 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: Receive a setting related to a random access channel occasion (RO), a setting related to a first synchronization signal block (SSB), and a second related SSB setting; Determine valid ROs based on the above RO-related settings; and Based on the above valid ROs, it includes performing physical random access channel (PRACH) transmission, and The above second SSB-related settings are on-demand (OD) SSB settings, and The above valid ROs are determined based on the union of the SSBs provided by the first SSB-related setting and the SSBs provided by the second SSB-related setting, Storage medium. In a method performed by a base station, Transmitting settings related to a random access channel occasion (RO), settings related to a first synchronization signal block (SSB), and settings related to a second SSB; and It includes attempting to receive a physical random access channel (PRACH) on valid ROs related to the above RO-related settings, and The above second SSB-related settings are on-demand (OD) SSB settings, and The above valid ROs are determined based on the union of the SSBs provided by the first SSB-related setting and the SSBs provided by the second SSB-related setting, method. 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 settings related to a random access channel occasion (RO), settings related to a first synchronization signal block (SSB), and settings related to a second SSB; and It includes attempting to receive a physical random access channel (PRACH) on valid ROs related to the above RO-related settings, and The above second SSB-related settings are on-demand (OD) SSB settings, and The above valid ROs are determined based on the union of the SSBs provided by the first SSB-related setting and the SSBs provided by the second SSB-related setting, Base station.