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

Abstract

This UE may: receive an on-demand system information block 1 (OD-SIB1)-related configuration for a first cell, wherein the OD-SIB1-related configuration includes a configuration for one or more SSB groups each including one or more SSBs; transmit, on the basis of the OD-SIB1-related configuration for the first cell, an SIB1 request related to a selected SSB; and perform, on the basis of the SIB1 request, PDCCH monitoring for SIB1 reception in at least one PDCCH monitoring occasion corresponding to each transmitted SSB in an SSB group to which the selected SSB belongs.

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 conservation.

[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 by means of 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 storing instructions that, when executed, cause the at least one processor to perform operations. In yet another aspect of the present specification, a processing device is provided comprising at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations. In yet another aspect of the present specification, a computer-readable non-transitory storage medium is provided for storing at least one program code that includes instructions that, when executed, cause the at least one processor to perform operations. The above method or above operations may include: receiving a setting related to an on-demand system information block 1 (OD-SIB1) for a cell, wherein the setting related to the OD-SIB1 includes a setting related to one or more groups of SSBs, each comprising one or more synchronization signal blocks (SSBs); selecting an SSB of the first cell; transmitting a SIB1 request related to the selected SSB based on the setting related to the OD-SIB1 for the first cell; and performing PDCCH monitoring for receiving the SIB1 at a time of at least one physical downlink control channel (PDCCH) monitoring corresponding to each transmitted SSB within the SSB group to which the selected SSB belongs, based on the SIB1 request.

[0010] In one aspect of the present specification, a method by means of 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, stores instructions that cause the at least one processor to perform operations. The above method or above operations may include: transmitting settings related to an on-demand system information block 1 (OD-SIB1) for a first cell, wherein each of the OD-SIB1 related settings includes settings related to one or more groups of SSBs, each including one or more synchronization signal blocks (SSBs); transmitting an SSB of the first cell; receiving a SIB1 request related to the transmitted SSB based on the OD-SIB1 related settings for the first cell; and performing a PDCCH transmission for SIB1 transmission at a time of monitoring at least one physical downlink control channel (PDCCH) corresponding to each transmitted SSB within the SSB group to which the SSB related to the SIB1 request belongs.

[0011] In each aspect of the present specification, PDCCH monitoring for receiving the SIB1 or PDCCH transmission for transmitting the SIB1 may be performed within the OD-SIB1 window.

[0012] In each aspect of the present specification, the OD-SIB1 window may be for a certain period after a predetermined offset from the start of the random connection response window.

[0013] In each aspect of this specification, the predetermined offset may be provided through a system information block.

[0014] In each aspect of this specification, PDCCH monitoring for receiving SIB1 may be omitted during the PDCCH monitoring period when the selected SSB does not correspond to an SSB within the SSB group to which the selected SSB belongs.

[0015] In each aspect of this specification, during a PDCCH monitoring period that does not correspond to an SSB within the SSB group to which the SSB associated with the SIB1 request belongs, a PDCCH transmission for the SIB1 transmission may not be performed.

[0016] In each aspect of the present specification, the OD-SIB1 setting for the first cell may be provided on the second cell.

[0017] In each aspect of the specification, the SIB1 request may be transmitted to a first power at a random access channel occasion (RO) associated with the selected SSB.

[0018] In each aspect of the present specification, the method by the UE or the operation for the UE may include: performing power ramping based on not receiving a response to the SIB1 request; and retransmitting the SIB1 request with the ramped power.

[0019] In each aspect of the present specification, the method by the UE or the operation for the UE may include: performing another on-demand downlink signaling request based on the ramped power based on receiving a response to the retransmission of the SIB1 request.

[0020] In each aspect of the present specification, the OD-SIB1 setting for the first cell may include broadcast information regarding whether the SIB1 of the first cell is being broadcast.

[0021] In each aspect of the present specification, based on the fact that the SIB1 of the first cell is broadcasting, the OD-SIB1 setting for the first cell may include information regarding the SIB1 window in which the PDCCH for scheduling the SIB1 is transmitted.

[0022] In each aspect of the present specification, based on the fact that the SIB1 of the first cell is being broadcast, the OD-SIB1 setting for the first cell may include information regarding whether the SIB1 of the first cell is being transmitted to (i) all beams of the first cell, (ii) being transmitted by a beam corresponding to an SSB associated with the SIB1 of the first cell, or (iii) being transmitted by beams corresponding to an SSB group to which the SSB associated with the SIB1 of the first cell belongs.

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

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

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

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

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

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

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

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

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

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

[0033] FIG. 6 illustrates physical channels used in a 3rd generation partnership project (3GPP)-based communication system, which is an example of a wireless communication system, and the signal transmission / reception process using them;

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

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

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

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

[0038] FIG. 11 illustrates an example of time-domain resource allocation of a physical downlink shared channel (PDSCH) by a physical downlink control channel (PDCCH) and an example of time-domain resource allocation of a physical uplink shared channel (PUSCH) by a PDCCH;

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

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

[0041] FIGS. 14 through 16 illustrate custom SIB1 transmission scenarios related to some implementations of the present specification;

[0042] FIG. 17 illustrates an example of SSB transmission by a BS operating multiple frequency bands;

[0043] FIG. 18 illustrates the flow of downlink (DL) signal reception in a UE according to some implementations of the present specification;

[0044] FIG. 19 illustrates the flow of downlink (DL) signal transmission in a BS according to some implementations of the present specification;

[0045] FIG. 20 illustrates the signal transmission / reception flow between a UE and a network according to some implementations of the present specification.

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

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

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

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

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

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

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

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

[0054] 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 base station and the UE.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0068] 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 the upper layer, and uplink physical signals corresponding to resource elements that are used by the physical layer but do not carry information originating from the upper layer.For example, the physical uplink shared channel (PUSCH), physical uplink control channel (PCCH), 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0095]

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

[0097]

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

[0099] 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. The carrier may contain up to N (e.g., 5) BWPs. A UE may be configured to have one or more BWPs on a given component carrier. Data communication is performed through the enabled BWPs, and only a predetermined number (e.g., 1) of the BWPs configured for the UE may be enabled on the carrier.

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

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

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

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

[0104]

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

[0106] A UE that has been turned on again after being turned off or has lost connection with 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 SSB / PBCH block) from the BS. The SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH). Based on the PSS / SSS, the UE synchronizes with the BS and obtains information such as the cell identifier (ID). Additionally, the UE can obtain broadcast information within the cell 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.

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

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

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

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

[0111] 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. The set transmitted within a 5 ms half-frame of SSB transmission is called an SSB burst set. The maximum number of SSB transmissions L within an SSB burst set. 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 set. max It can be given as follows.

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

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

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

[0115] The actual number of transmitted SSBs can be configured, with a maximum number Lmax It can be smaller.

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

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

[0118] Up to L SSBs can be transmitted within an SSB burst set, 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.

[0119] - In the case of rate-matching: This may be indicated via UE-specific RRC signaling or RMSI. UE-specific RRC signaling includes a full (e.g., length L) bitmap in both the below 6 GHz and above 6 GHz frequency ranges. On the other hand, the remaining minimum system information (RMSI) (i.e., SIB1) includes a full bitmap in the below 6 GHz range and a bitmap in a compressed form as described above 6 GHz. Specifically, information regarding the SSB actually transmitted may be indicated using a group-bitmap (8-bit) and an in-group bitmap (8-bit). Here, the resources indicated via UE-specific RRC signaling or RMSI (e.g., resource elements (REs)) are reserved for SSB transmission, and PDSCH / PUSCH, etc., may be rate-matched with respect to the SSB resources.

[0120] - 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 can be specified using a full (e.g., length L) bitmap of the RRC signaling. When in RRC_IDLE mode, the default set of SSBs is used.

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

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

[0123] - The MIB is always transmitted over a BCH with a periododicity of 80 ms and repetitions created within 80 ms. The MIB contains information / parameters related to SIB1 reception and is transmitted via the SSB's PBCH. During initial cell selection, the UE assumes that half-frames containing the SSB(s) repeat with a period of 20 ms. Based on the MIB, the UE can determine whether a control resource set (CORESET) exists for the Type0-PDCCH common search space. For example, the field ssb-SubcarrierOffset within the MIB is k, which is a frequency domain offset in units of the number of subcarriers between the SSB and the overall resource block grid. SSB Corresponds to. Upon detection of an SS / PBCH block, the UE, in the case of FR1, k SSB If < 24, or in the case of FR2, k SSBIf < 12, it can be determined that a CORESET exists for the Type-0 PDCCH common search space (CSS) set, and for FR1, k SSB If > 23, or in the case of FR2, k SSB If > 11, it can be determined that a Type-0 PDCCH CSS set does not exist. The Type-0 PDCCH common seek space is a type of PDCCH seek space and is used to transmit PDCCHs that schedule SI messages. If a Type-0 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 Type-0 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.

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

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

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

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

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

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

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

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

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

[0133] The UE can receive information regarding random access from the BS through system information. For example, information regarding 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 (RA Occasion, RO) and the random access preamble index (Preamble Index, PI). When the BS receives a random access preamble from the UE, the BS transmits a RAR message to the UE on the PDSCH. To receive a RAR message, the UE monitors 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0149] 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 and 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0186] For a Type-1 random access process, or for a Type-2 random access process having a separate configuration of PRACH periods from the Type-1 random access process, if N < 1, one SS / PBCH block index is mapped to 1 / N consecutive valid PRACH periods, and per valid PRACH period, R contention-based preambles with consecutive indices associated with the said SS / PBCH block index start from preamble index 0. If N ≥ 1, per valid PRACH period, R contention-based preambles with consecutive indices associated with the SS / PBCH block index n start from preamble index n*N total preamble Starting from / N, 0≤n≤N-1, and Ntotal preamble is provided by totalNumberOfRA-Preambles for a type-1 random connection process, or by msgA-TotalNumberOfRA-Preambles for a type-2 random connection process that has a separate configuration of PRACH times from the type-1 random connection process, and is an integer multiple of N.

[0187] For a Type-2 random access process having common settings for PRACH periods with a Type-1 random access process, if N < 1, a single SS / PBCH block index is mapped to 1 / N consecutive valid PRACH periods, and Q contention-based preambles having consecutive indices associated with the said SS / PBCH block index per valid PRACH period start from preamble index R. If N ≥ 1, Q contention-based preambles having consecutive indices associated with the SS / PBCH block index n per valid PRACH period start from preamble index n*N total preamble Starting from / N + R, where 0≤n≤N-1 and N total preamble The type-1 random connection process is provided by totalNumberOfRA-Preambles.

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

[0189] The SS / PBCH block indices provided by ssb-PositionsInBurst in SIB1 or RRC configuration ServingCellConfigCommon are mapped to valid PRACH times in the following order, and the parameters are described in 3GPP TS 38.211.

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

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

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

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

[0194] The association period, starting from frame 0, for mapping SS / PBCH block indexes to PRACH periods is N SSB Tx an association period, starting from frame 0, for mapping SS / PBCH block indexes to PRACH occasions is the smallest integer number in the set determined by the PRACH configuration period according to the following table such that N SSB Tx SS / PBCH block indexes are mapped at least once to the PRACH occasions within the association period), where UE is N from the value of ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon SSB Tx Gets.

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

[0196]

[0197] In the case of a PRACH transmission by a UE triggered by a PDCCH command, if the value of the Random Connection Preamble Index field is not zero, the PRACH Mask Index field indicates the PRACH timing for said PRACH transmission, wherein the PRACH timings are associated with the SS / PBCH block index indicated by the SS / PBCH Block Index field of said PDCCH command, and if any, the Cell Indicator field indicates the cell for the PRACH transmission (see 3GPP TS 38.212). The UE K by the RRC parameter cellSpecificKoffset cell,offset If provided, the above PRACH time is slot n + 2 u ·K cell,offset After, and here n is T TA Assuming = 0, it is a slot in the UL BWP for a PRACH transmission that overlaps with the end of the PDCCH command reception, and u is the SCS setting for said PRACH transmission. If the PDCCH reception for a PDCCH command contains two PDCCH candidates from two linked sets of searchspaces based on the RRC parameter searchSpaceLinkingId used to link two searchspaces of the same type within the same BWP, the last symbol of said PDCCH reception is the last symbol of the PDCCH candidate that ends later, as described in Section 10.1 of 3GPP TS 38.213. said PDCCH reception contains said two PDCCH candidates even when the UE is not required to monitor one of said two PDCCH candidates, as described in Section 10 (excluding Section 10.4), 11.1, 11.1.1, and 17.2 of 3GPP 38.213.

[0198] In the case of a PRACH transmission triggered by upper layers, if the RRC parameter ssb-ResourceList is provided, the PRACH mask index is indicated by the RRC parameter ra-ssb-OccasionMaskIndex, which indicates the PRACH timing for the PRACH transmission.

[0199] PRACH periods are mapped consecutively per corresponding SS / PBCH block index. The indexing of the PRACH periods indicated by the mask index value is reset per mapping cycle of consecutive PRACH periods per SS / PBCH block index. Within the first available mapping cycle, the UE selects the PRACH period indicated by the PRACH mask index value for the indicated SS / PBCH block index for PRACH transmission.

[0200] For the preamble index indicated above, the ordering of the PRACH periods is

[0201] First, regarding the frequency-multiplexed PRACH periods, in increasing order of frequency resource indices

[0202] Second, regarding the time-multiplexed PRACH periods within the PRACH slot, in increasing order of time resource indices

[0203] Third, for the PRACH slots, in increasing order of the indices

[0204] N rep preamble For a PRACH transmission with multiple preamble repetitions, the set is continuous in time and uses the same frequency resources, and is associated with one or more identical SS / PBCH block index(s), N rep preambleIt consists of valid PRACH periods, and each SS / PBCH block index is associated with the same preamble index within all valid PRACH periods in the set.

[0205] In the case of a PRACH transmission with preamble repetitions, the time interval starting from frame 0 is the above N SSB Tx For a PRACH transmission with preamble repetitions, a time period, starting from frame 0, is the smallest integer number of association pattern periods such that at least one set of valid PRACH occasions for each of the N SS / PBCH block indices can be determined within the time period for all set number of preamble repetitions. SSB Tx SS / PBCH block indexes can be determined within the time period for all configured number of preamble repetitions. The set(s) of valid PRACH occasions for each configured number of preamble repetitions repeat every time period.

[0206] Within the time interval, N rep preamble N for PRACH transmission with dog preamble iterations rep preamble For a set of valid preamble iterations

[0207] The first valid PRACH time of the first set is the first valid PRACH time.

[0208] If any, the first valid PRACH time of the subsequent sets is determined according to the ordering of the valid PRACH times.

[0209] First, in increasing order of frequency resource indices for frequency-multiplexed PRACH periods

[0210] Second, in increasing order of the time resource indices of the time multiplexing PRACH periods

[0211] Here, for each frequency resource index for the frequency-multiplexed PRACH periods

[0212] The first valid PRACH time of the first set is the first valid PRACH time.

[0213] If any, the first valid PRACH time of subsequent sets is

[0214] If the RRC parameter msg1-RepetitionTimeOffsetROGroup is provided, it is msg1-RepetitionTimeOffsetROGroup consecutive valid PRACH periods after the first valid PRACH period of the previous set, where each PRACH period is associated with the same SS / PBCH block index(s) and each SS / PBCH block index is associated with the same preambles.

[0215] If the RRC parameter msg1-RepetitionTimeOffsetROGroup is not provided, it is after the PRACH time of the previous set mentioned above.

[0216] In the case of a PRACH transmission triggered by a request from upper layers, if the RRC parameter csiirs-ResourceList is provided, the value of the RRC parameter ra-OccasionList indicates a list of PRACH times for said PRACH transmission, wherein said PRACH times are associated with a selected CSI-RS index indicated by the RRC parameter csi-RS. The indexing of the PRACH times indicated by ra-OccasionList is reset for each associated pattern interval.

[0217] For paired spectra or supplementary uplink bands, all PRACH periods are valid.

[0218] In the case of an unpaired spectrum,

[0219] If the UE is not provided with the RRC configuration tdd-UL-DL-ConfigurationCommon, the PRACH time within the PRACH slot does not precede the SS / PBCH block within the said PRACH slot, and at least N after the last SS / PBCH block received symbol. gap If it starts after the dog symbols, it is valid, where N gap It is provided in the following table, and if the RRC parameter channelAccessMode ="semiStatic" is provided, it does not overlap with the set of consecutive symbols before the start of the next channel occupancy time (see 3GPP TS 37.213) that the UE does not transmit.

[0220] >> The candidate SS / PBCH block index for the SS / PBCH block corresponds to the SS / PBCH block index provided by ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon as described in Section 4.1 of 3GPP TS 38.213.

[0221] If the UE is provided with tdd-UL-DL-ConfigurationCommon, the PRACH timing within the PRACH slot is valid in the following cases.

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

[0223] >> 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 the following table, 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_gap is provided in Table 8.1-2, 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.

[0224] >>> The candidate SS / PBCH block index of the above SS / PBCH block corresponds to the SS / PBCH block index provided by ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon as described in Section 4.1 of 3GPP TS 38.213.

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

[0226]

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

[0228] The following enhancement techniques may be considered.

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

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

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

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

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

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

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

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

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

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

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

[0240] Referring to FIG. 12, the BS identifies or determines the NES solution(s) to be applied (S1201). 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 (S1203). 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 (S1205). 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.

[0241] NES technology can be performed through a procedure as shown in Fig. 12. Examples of NES solutions that can be performed by a procedure as shown in Fig. 12 are as follows.

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

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

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

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

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

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

[0248] SSB-less SCell

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

[0250] Referring to FIG. 13, the BS can transmit configuration information for SCells to be aggregated through a SCell already configured to the PCell or UE (S1301). 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 SCells may include information containing information for adding SCells (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 (S1303) and can perform communication using the BS's PCell and SCell (S1305a, S1305b). 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. 15, 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.

[0251] The following table illustrates a portion of the RRC information element (IE) FrequencyInfoDL, which provides the downlink carrier and the basic parameters of transmission on said downlink carrier.

[0252]

[0253] The above IEFrequencyInfoDL may be included in the RRC configuration DownlinkConfigCommon or DownlinkConfigCommonSIB, which provides common downlink parameters for the cell.

[0254] In the table above, the field absoluteFrequencySSB indicates the frequency of the SSB to be used for this serving cell, and SSB-related parameters provided for the serving cell (e.g., SSB index) refer to this SSB frequency unless otherwise noted. The cell-defining SSB (CD-SSB) of the PCell is always on the sync raster. If frequencies are identifiable by their GSCN values, they are considered to be on the sync raster. If the field absoluteFrequencySSB is absent in the IEFrequencyInfoDL, the SSB-related parameters (e.g., ssb-PositionsInBurst, ssb-periodicityServingCell, and subcarrierSpacing in ServingCellConfigCommonIE) are absent. If the above field absoluteFrequencySSB is absent, the UE may obtain a timing reference from an applicable SpCell or SCell, from the SpCell or SCell indicated by the referenceCell, or from a default cell. This is supported when the SCell from which the UE obtains the timing reference is within the same or different frequency band as the cell from which the UE obtains the timing reference (e.g., the respective SpCell or SCell).

[0255] In the table above, the field referenceCell can indicate a reference cell, which is a cell that provides timing references and AGC sources for SCells without SSB. If the reference cell is an SCell or PSCell, it is an active SCell or active PSCell. If this field is absent, the default cell is the reference cell.

[0256] The UE may receive the periododicity of half frames for receiving SSBs for the corresponding serving cell per serving cell via the RRC parameter ssb-perodicitiyServingCell. If the UE is not set the periododicity of half frames for receiving SSBs, the UE assumes a periododicity of half frames. The UE may assume that the periododicity is the same for all SSBs within the serving cell. For initial cell selection, the UE may assume that half frames containing SSBs occur at a period of two frames.

[0257] On-demand SSB

[0258] In some implementations, a method to reduce energy consumption may be considered in which the BS transmits an SSB on a specific cell through an on-demand SSB process, and does not transmit an SSB on said specific cell when there is no on-demand SSB process. For convenience, SSBs transmitted for a certain period or interval upon request by a UE are referred to as on-demand SSBs below. In existing NR systems, it was difficult to reduce energy consumption even when the BS had no data to receive or send, as SSBs had to be transmitted periodically at all times for purposes such as time / frequency synchronization or RRM measurement. Considering this, in some implementations, BS energy consumption can be reduced by allowing the BS to refrain from transmitting SSBs and only transmit them when an on-demand SSB process is involved. The above on-demand SSB process can be triggered through one of the following methods.

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

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

[0261] 3) Signal whether SSB is transmitted for the corresponding SCell through SCell activation / deactivation signaling.

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

[0263] SIB1 transmission on demand

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

[0265] FIGS. 14 through 16 illustrate custom SIB1 transmission scenarios related to some implementations of the present specification.

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

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

[0268] 2) Scenario 2: As illustrated in FIG. 15, a UE that receives an SSB (and / or other downlink signal / channel such as SIB1) at Cell #1 and realizes that SIB1 is not being transmitted on Cell #2 may attempt to camp-on through Cell #2. The UE may trigger the transmission of SIB1 to Cell #2 by transmitting a signal (e.g., WUS) requesting SIB1 on Cell #1 based on the information provided by the received SSB (and / or other downlink signal / channel such as SIB1) and / or predetermined information. A BS that receives the WUS may, in response, transmit a specific DL signal / channel (corresponding to an ACK for the WUS) on Cell #1 or Cell #2, or transmit SIB1 to Cell #2 on Cell #1 or Cell #2 (or without transmitting the DL signal / channel).

[0269] 3) Scenario 3: 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 for Cell #2 by transmitting a signal (e.g., WUS) requesting SIB1 on Cell #2 based on the information provided in the received SSB (and / or other downlink signal / channel such as SIB1) and / or predetermined information. A BS that receives the WUS may, in response, transmit a specific DL signal / channel (corresponding to an ACK for the WUS) on Cell #1 or Cell #2, or transmit SIB1 for Cell #2 on Cell #1 or Cell #2 (or without transmitting the DL signal / channel).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0285] Since there are technologies found to be useful through research that are not yet specified in the 3GPP communication standard document, some implementations of this specification are provided below that can obtain network energy saving benefits based on beneficial techniques that have not yet been adopted.

[0286] For example, in some implementations of this specification described below, when a UE successfully requests a DL transmission to a BS via a preset UL signal (e.g., WUS) in a cell where a specific signal / channel is operated on demand for energy saving, the corresponding UL signal power may be utilized for other UL transmission procedures.

[0287] As another example, in some implementations of this specification described below, the BS may operate the cell in an on-demand manner, omitting periodic SIB1 transmission to save energy and transmitting it only when requested by the UE. In this case, in some implementations of this specification described below, the BS may provide information on whether the cell is currently broadcasting SIB1 and in which beam direction SIB1 is being transmitted. Some implementations of this specification are described below in which, based on the information received from the BS, the UE determines whether to request SIB1 via the UL WUS and determines from which SIB1 PDCCH monitoring occasion (MO) reception of SIB1 can be expected. In this specification, SIB1 PDCCH refers to a PDCCH carrying a DCI that schedules a PDSCH carrying SIB1, and SIB1 PDSCH refers to a PDSCH carrying SIB1.

[0288] A BS operating multiple frequency bands may consume a large amount of energy by periodically sending SSB and / or system information, even when the number of UEs being served is small or the traffic load is relatively low.

[0289] Figure 17 illustrates an example of SSB transmission by a BS operating multiple frequency bands.

[0290] Referring to FIG. 17, a BS operating in three frequency bands can save energy by periodically sending (legacy) SSB and / or SIB1 only in some frequency bands (e.g., F1), transmitting simplified (or modified) SSB (hereinafter S-SSB) in the remaining frequency bands (e.g., F2), or not transmitting SSB in other frequency bands (e.g., F3). For example, in some implementations, the S-SSB may consist only of PSS and SSS. Referring to FIG. 17, in some implementations of this specification, a UE operating in F2 or F3 may request the transmission of SSB from the BS in the corresponding frequency band. After moving from F1 or to F2 / F3 and performing the on-demand SIB1 process, the UE receives the SSB and / or SIB1 for the corresponding F2 or F3 frequency band, performs the RACH process (also called the random connection process), enters connected mode, and can perform DL and / or UL data through F2 or F3. Additionally, for convenience, the frequency band where S-SSB can be transmitted, such as F2, and the frequency band where SSB cannot be transmitted, such as F3, or the frequency band where SIB1 can be transmitted through the on-demand SIB1 process, are collectively referred to as the F2 frequency band, but some implementations of this specification may be applied to F2 and F3.

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

[0292] In some implementations of this specification, as in F1 of FIG. 17, the frequency band where an SSB and / or SIB1 is transmitted and information about another frequency band (e.g., whether the current SIB1 is being transmitted periodically, if it is being transmitted, information on the transmission time pattern of the SIB1 on that other frequency band, if it is not being transmitted, configuration information for UE WUS resources for the on-demand SIB1 process, etc.) is provided is referred to for convenience as the anchor cell, and the other frequency band provided through the SSB and / or SIB1 on the anchor cell is referred to for convenience as the non-anchor cell. Additionally, the UE may assume that there is an association or quasi-co-location (QCL) relationship between the anchor cell and the non-anchor cell. The existence of a QCL relationship between an anchor cell and a non-anchor cell implies that QCL parameters, such as Doppler shift, Doppler spread, average delay, delay spread, and spatial Rx parameters, obtained from either the anchor cell or the non-anchor cell (or the reference signal of that cell) and from the non-anchor cell (or the reference signal of the non-anchor cell), can also be applied to other cells (or the reference signal of said other cells or the antenna port(s) of said reference signal). In an NR system, four QCL types are defined as follows:

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

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

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

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

[0297] QCL types corresponding to each DL RS can be provided by the RRC parameter qcl-Type in the RRC setting QCL-Info, and can take one of the four values ​​above.

[0298] 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≠Y).

[0299] For convenience, below, a cell that periodically transmits its own SIB1 (e.g., anchor cell) is referred to as Cell A, and a cell that transmits SIB1 only when the UE requests SIB1 through UL WUS for energy saving (e.g., non-anchor cell) is referred to as NES Cell.

[0300] A UE may receive UL WUS configuration from Cell A or an NES Cell to request an SSB / SIB1 (hereinafter referred to as SSB / SIB1) from an NES Cell operating an on-demand SSB and / or SIB1. If PRACH and / or MsgA PRACH are used as the UL WUS, the UL WUS configuration may be configured similarly to the PRACH configuration. Although some implementations of this specification are described below using PRACH / MsgA PRACH as an example of the UL WUS, other UL signals (e.g., semi-persistent (SP)-)PUCCH, and / or sounding reference signal (SRS), and / or configured grant (CG)-)PUSCH) may also be used as the UL WUS for the SIB1 request. The following table is an example of parameters that may be included in the UL WUS configuration.

[0301]

[0302] In the table above, parameter NES-CellId represents the physical cell ID of the cell to which the corresponding UL WUS configuration is applied, SIB1-RequestConfig is a configuration related to the SIB1 request, frequencyInfoU provides basic parameters for the uplink carrier and transmission over it, pdcch-ConfigSIB1 is a configuration used to determine the common control resource set (CORESET), common seek space, and necessary PDCCH parameters, and pdcch-ConfigOD-SIB1-RAR is a PDCCH configuration used to receive the RAR for the said SIB1 request after the UE has sent the SIB1 request.SIB1-RequestConfig contains ss-PBCH-BlockPower, which concerns the average energy per resource element (EPRE) in dBm of resource elements (REs) carrying the secondary synchronization signal (SSS) used by the network for SSB transmission; rach-OccasionSIB1, which concerns the setting of (dedicated) RACH times for SIB1; sib1-RequestPeriod, which concerns the periododicity of the above SIB1-RequestConfig; sib1-RequestResource, which defines which preamble and time resources the UE must use at the physical layer to request SIB1 transmission from the network; rsrp-ThresholdSSB, which concerns the L1-RSRP threshold used to determine whether a candidate beam can be used for the transmission attempt of the SIB1 request by the UE; and the PRACH root sequence index to be used for the SIB1 transmission request. It may include prah-RootSequenceIndex, msg1-SubcarrierSpacing, which is the subcarrier spacing of PRACH used for SIB1 transmission requests, restrictedSetConfig, which is a setting of one of two types of restricted sets or an unrestricted set, and tdd-UL-DL-ConfigurationCommon, which is a cell-specific TDD UL / DL setting.ConfigurationFrequencyInfoUL may include frequencyBandList, a list of one or more frequency bands to which this carrier(s) belong; absoluteFrequencyPointA, an absolute frequency of a reference resource block (e.g., common resource block 0); offsetToCarrier, a frequency domain offset between Point A (the lowest subcarrier of common RB 0) and the lowest available subcarrier in that carrier; p-Max, a maximum strategy value in dBm applicable to the cell; and frequencyShift7p5khz, which indicates whether to enable NR UL transmission with a 7.5 kHz shift for LTE raster. pdcch-ConfigSIB1 may include ssb-SubcarrierOffset, a frequency domain offset between the SSB and the overall resource block grid; controlResourceSetZero, used to determine the common CORESET with ID #0; and the common It may include searchSpaceZero regarding the parameters of search space #0. pdcch-ConfigOD-SIB1-RAR may include controlResourceSet, monitoringSlotPeriodicityAndOffset, Duration, monitoringSymbolsWithinSlot, and aggregationLevels.

[0303] For convenience, some implementations of this specification are described below assuming that the UL WUS is transmitted over Cell A (or over an NES Cell) and a 4-stage RACH process, but some implementations of this specification may be extended without limitation to cases where the UL WUS is transmitted over an NES Cell (or over Cell A) and a 2-stage RACH process (and contention-based random access (CBRA) and contention-free random access (CFRA)). Additionally, the UE may be provided with UL WUS configurations to request SIB1 from the SIBx (e.g., SIB1) of Cell A or from the NES Cell, and may also be configured with information on whether to transmit the UL WUS to Cell A or to the NES Cell.

[0304] Meanwhile, when the UE requests the BS to transmit an on-demand SIB1 (OD-SIB1) via the UL WUS, the starting time of the time window in which the OD-SIB1 PDCCH and / or OD-SIB1 PDSCH (hereinafter referred to as OD-SIB1 PDCCH / PDSCH) is transmitted may be after a semi-static or dynamically indicated offset (via the UL WUS configuration or the NES Cell's MIB / SIBx / RAR), with the time of receiving the response RAR to the UL WUS as the reference time, or the start or end of the RAR window as the reference time. Alternatively, in some implementations, the time window of the OD-SIB1 PDCCH MO may start from the first / last symbol of the earliest CORESET configured for the UE to receive the Type0 PDCCH after adding the offset to the reference time. In this specification, Type0 PDCCH may be a PDCCH received from a Type0 PDCCH CSS set configured for the DCI format with a CRC scrambled by SI-RNTI.

[0305] <Method #0> A method for utilizing power control parameters of a UL signal / channel used in a specific on-demand procedure in another on-demand procedure or UL transmission procedure when a UE requests an on-demand DL signal transmission from a BS via a pre-configured UL resource (e.g., WUS).

[0306] The BS can operate the transmission of common signal / channel(s), such as the SSB / SIB1 of a specific cell, on-demand to save energy. The UE can transmit a UL signal (e.g., WUS) pre-configured by the BS to receive a DL signal from these cells. Depending on the configuration / instruction, the UL WUS may be PRACH, and / or (CG-)PUSCH, and / or SRS, and / or (SR-)PUCCH, etc.

[0307] For example, a BS operating OD-SIB1 for energy saving may configure PRACH resources (e.g., RO / preamble, etc.) as UL WUS resources for UEs that are not yet connected to a cell or UEs in IDLE or INACTIVE mode, and may not normally transmit SIB1 periodically, but transmit SIB1 only for a specific time period (e.g., time window) when a UE requests SIB1 transmission via UL WUS. When a UE transmits PRACH to receive SIB1, the BS may transmit RAR (or a separate PDCCH) as a response acknowledging successful reception of the UL WUS. In this case, if the UE does not receive a response to PRACH within a specific time period (e.g., RAR window), the BS may retransmit PRACH by ramping the PRACH power by a specific step size according to a predefined / configured power control procedure. In some implementations of this specification, if a UE attempts a retransmission and successfully receives a RAR, the power control parameter(s) used for the successful PRACH (re)transmission may be utilized for other on-demand procedures or UL transmission procedures. For example, if a UE performs a PRACH retransmission after performing two PRACH power ramps in the OD-SIB1 procedure and succeeds in receiving a response from the BS, the PRACH power used for the PRACH retransmission may subsequently be used when performing a PRACH transmission for an on-demand other system information (OD-SI) request. Thus, for a PRACH transmission to request OD-SI, the UE may use the PRACH power ramped twice by the retransmission in the OD-SIB1 procedure as the initial power, rather than the PRACH power set for the first OD-SI procedure.Here, "utilization" may mean using specific power control parameters defined in a standard document or pre-set / instructed as they are, or it may mean applying pre-set / instructed offset values ​​and / or scaling values ​​to said specific power control parameters.

[0308] In some implementations of this specification, the above method is further generalized so that power control parameters of UL signals / channels used in specific on-demand procedures, as well as OD-SIB1, may be utilized in other on-demand procedures or UL transmission procedures. For example, the UE may reuse PRACH power used in an on-demand SSB (OD-SSB) procedure in the OD-SIB1 procedure or in the OD-SI procedure, and conversely, may reuse PRACH power used in the OD-SIB1 procedure in the OD-SSB procedure. Additionally, if the UL signal / channel configured for the SIB1 transmission request in the OD-SIB1 procedure is configured as (CG-)PUSCH rather than PRACH, the UE may utilize the power control parameter(s) of the (CG-)PUSCH used when receiving a response from the BS indicating successful reception of (CG-)PUSCH (e.g., PDCCH or PDSCH scrambled to a specific RNTI) or when successfully receiving SIB1 for the subsequent (CG-)PUSCH transmission. Alternatively, the power control parameters of the UL signal / channel used by the UE in a specific procedure may also be utilized for the power control of the UL signal / channel used in another procedure. For example, some of the PRACH power control parameters used by the UE in the OD-SIB1 procedure may be utilized when determining the transmission power of other UL signals / channels (e.g., PUSCH and / or PUCCH and / or SRS).

[0309] The power control parameters mentioned above may refer to the parameters within the UL signal / channel-specific power control formulas defined in Section 7 of the standard document 3GPP TS 38.213. For example, referring to 3GPP TS 38.213, the UE [determines] the transmission power P for a physical random access channel (PRACH) on an active UL BWP b of carrier f of cell c, based on DL RS for cell c within transmission time i. PRACH,b,f,c (i) can be determined according to the following.

[0310] > P PRACH,b,f,c (i) = min{P CMAX,f,c (i), P PRACH,target,f,c + PL b,f,c} [dBm].

[0311] Here, P CMAX,f,c (i) is the UE configured maximum output power defined in 3GPP TS 38.101-1, 3GPP TS 38.101-2, 3GPP TS 38.101-3, and 3GPP TS 38.101-5 for carrier f of cell c during transmission time i. P PRACH,target,f,c is the PRACH target received power PREAMBLE_RECEIVED_TARGET_POWER provided by the upper layers for the active UL BWP b of the carrier f of cell c. PL b,f,cis the path loss for the active BWP b of carrier f, calculated in dB by the UE as 'referenceSignalPower - higher layer filtered RSRP' in dBm, based on the DL RS associated with the PRACH transmission on the active DL BWP b of cell c, where RSRP is defined in 3GPP TS 38.15 and the higher layer filter setting is defined in 3GPP TS 38.331. If the active DL BWP is an initial DL BWP and is for an SS / PBCH block and CORESET multiplexing pattern 2 or 3, or for a non-serving cell, the UE calculates PL based on the SS / PBCH block associated with the PRACH transmission. b,f,c Determines.

[0312] For example, the UE can determine the PRACH transmission power by the above formula. In the above formula, PREAMBLE_RECEIVED_TARGET_POWER can be determined as follows, as defined in 3GPP TS 38.321: PREAMBLE_RECEIVED_TARGET_POWER=preambleReceivedTargetPower+DELTA_PREAMBLE+ (PREAMBLE_POWER_RAMPING_COUNTER- 1) ×PREAMBLE_POWER_RAMPING_STEP+POWER_OFFSET_2STEP_RA. Here, preambleReceivedTargetPower and PREAMBLE_POWER_RAMPING_STEP are set by the RRC parameter(s) within the RRC configuration RACH-ConfigGeneric. PREAMBLE_POWER_RAMPING_STEP is set to msgA-PreamblePowerRampingStep provided by RACH-ConfigGenericTwoStepRA if the random access type is a 2-stage random access type, and to powerRampingStep provided by RACH-ConfigGeneric if the random access type is a 4-stage random access type. DELTA_PREAMBLE is predefined according to the preamble format, and for example, it can be 0 dB for preamble format 0, -3 dB for preamble format 1, -6 dB for preamble format 0, and 0 dB for preamble format 1. PREAMBLE_POWER_RAMPING_COUNTER is the preamble when the UE fails to transmit the preamble As a variable that counts the number of power ramping cycles to gradually increase the power for retransmission, it is set to 1 when the random connection procedure starts in the serving cell and increases by 1 each time the conditions are met.POWER_OFFSET_2STEP_RA is a variable used to compensate for transmission power when switching from a 2-step random access type to a 4-step random access type. It is set to 0 dB when the random access procedure starts, and when switching from 2-step to 4-step in the currently ongoing random access procedure, it is set to a value calculated as follows: (PREAMBLE_POWER_RAMPING_COUNTER - 1) × MSGA_PREAMBLE_POWER_RAMPING_STEP - PREAMBLE_POWER_RAMPING_STEP), where MSGA_PREAMBLE_POWER_RAMPING_STEP can be set to msgA-PreamblePowerRampingStep provided by RACH-ConfigGenericTwoStepRA.

[0313] In the previously mentioned example of the OD-SIB1 procedure, if preambleReceivedTargetPower is set to -110 and powerRampingStep is set to 4dB, and the UE successfully receives RAR by retransmitting PRACH twice for the SIB1 request, the power control parameters used in the OD-SIB1 procedure can be used when performing the OD-SI procedure after the OD-SIB1 procedure. For example, if preambleReceivedTargetPower is set to -110 and powerRampingStep is set to 4dB in the example of the OD-SIB1 procedure, and the UE successfully receives RAR by retransmitting PRACH twice for the SIB1 request, the UE may use the PRACH power increased twice by 4dB as the initial power for the PRACH transmission for the OD-SI procedure, or may use the value obtained by applying the powerRampingStep of the PRACH setting configured for the OD-SI procedure twice as the initial power for the PRACH transmission for the OD-SI procedure.

[0314] Meanwhile, when power control parameters of a UL signal / channel that has been successfully requested in a specific on-demand procedure as described above are utilized in another on-demand procedure or UL transmission procedure, whether to maintain or reset the power control parameter values ​​used in the other procedure may be defined in the standard document or pre-set / instructed by the BS, and if the same power control parameters are applied to multiple cells (e.g., in a scenario where UL WUS for multiple NES cells can be transmitted from a single UL BWP), the same power control parameters may be applied to said multiple cells. Alternatively, the UE may inherit and use the power control parameters used in a specific cell for other cells as well, or use them by applying an offset.

[0315] In some implementations, constraints can be defined or set to allow power control parameters used in a specific procedure to be applied to other procedures or other cells. For example, in the OD-SIB1 procedure, if a specific DL signal (e.g., RAR or DCI scrambled with a specific RNTI) is received in response to a specific UL signal transmitted by the UE itself (e.g., PRACH (UL WUS / Preamble)), the corresponding last ramped power value is used; however, if a response to its own UL signal is not received but a specific DL signal (e.g., DCI scrambled with RAR or a specific RNTI, SIB1, etc.) is successfully received (by a UL signal transmitted by another UE), a 1-step ramp is applied to the last ramped power and applied to another procedure, or the power value (e.g., dB value) calculated by ramping up by 1 step based on the power control parameters of the previous on-demand procedure is applied directly to the next on-demand procedure, or the ramping step value is increased by 1 (i.e., by adding 1 to the latest ramping count of the previous on-demand procedure) and that increased value is applied to the power control of the next on-demand procedure. The final UL power value can also be calculated based on parameters.In other words, if the UE did not receive a response to its own UL signal transmission (hereinafter, the first UL signal transmission) in the first on-demand procedure but succeeded in receiving a specific DL signal (e.g., RAR or DCI scrambled with a specific RNTI, SIB1, etc.) (by a UL signal transmitted by another UE), and the transmission power of the first UL signal transmission (hereinafter, the first transmission power) is determined through m-step ramping up based on the power control parameter of the first on-demand procedure, the initial power for the UL transmission of the second on-demand procedure is i) calculated by applying a 1-step ramping up based on the power control parameter of the second on-demand procedure to the first transmission power, or ii) calculated through (m+1)-step ramping up based on the power control parameter of the first on-demand procedure (i.e., calculated by additionally applying a 1-step ramping up based on the power control parameter of the first on-demand procedure to the first transmission power), or iii) the It can be calculated through (m+1)-step ramping up based on power control parameters of the second on-demand procedure.

[0316] As in the previous example, when ramping up one step or maintaining the ramping step value, if the setting of the power control parameter of the previous order procedure and the setting of the power control parameter of the next order procedure are different for the maximum value of the ramping counter (e.g., preambleTransMax, regarding the maximum number of RA preamble transmissions performed before declaring failure of the RA process, provided through RACH-ConfigCommon or RACH-ConfigDedicated in SIB1), for example, if the maximum step value (e.g., preambleTransMax) in the previous order procedure was 5 and the maximum step value (e.g., preambleTransMax) in the next order procedure is 3, the corresponding maximum step value (e.g., preambleTransMax) can be reduced to 3 and applied.

[0317] As another example, if the UE successfully receives SIB1 by transmitting PRACH in the beam direction corresponding to SSB index #0 during the OD-SIB1 procedure, the PRACH power control parameter may be applied only when transmitting PRACH in the same beam direction during the OD-SI procedure thereafter, or it may be used commonly for all beam directions.

[0318] In some implementations of this specification, the use of power control parameters of UL signals transmitted by the UE while performing a specific on-demand procedure, or the utilization of such power control parameters in subsequent on-demand procedures, is applicable not only between on-demand procedures but also to combinations between a previous on-demand procedure and a 2-stage / 4-stage random connection procedure. Additionally, the UE may apply the value Y set for the next on-demand or 2-stage / 4-stage random connection procedure (or conversely, apply the value X set for the previous on-demand procedure) if the power ramping stage size value X set for the previous on-demand procedure is different (or identical) from the power ramping stage size value Y set for the next on-demand procedure or the 2-stage / 4-stage random connection procedure according to a setting / instruction from the BS.

[0319] At this time, whether power control parameters are referenced / utilized between on-demand procedures or between on-demand procedures and UL transmission procedures, such as 2-stage / 4-stage random access procedures, may be defined in advance (in standard documents, etc.) or set / instructed by the BS. Since reference / utilization may be inefficient when the time difference between the previous procedure / transmission and the next procedure / transmission is large, in some implementations of this specification, it may be stipulated that power control parameters used in the previous UL transmission are considered valid only when the time difference between the previous and subsequent procedures / transmissions is less than or equal to a value T set / instructed in advance, or a valid duration and / or timer for power control parameters used in a specific procedure / transmission may be set together. In some implementations of this specification, how much the SSB receive quality (e.g., RSRP) or the consequent path loss level has changed compared to the receive quality / path loss level of the previous on-demand procedure may be set / instructed to the UE as a condition for maintaining power control parameters. For example, the UE may operate to refer to / utilize the power control parameters of the previous procedure only when the RSRP or path loss value between the preceding on-demand procedure and the subsequent on-demand or 2-stage / 4-stage RACH procedure is less than or equal to a predefined / set value T, and to initialize otherwise.

[0320] According to some implementations of this specification, the transmission power or power control parameters used in a successful on-demand downlink signaling procedure may be utilized in other on-demand downlink signaling procedures. Accordingly, the power ramping procedure may be omitted, and the on-demand downlink signaling procedure may succeed faster.

[0321] <Method #1> Method for determining whether a UE transmits UL WUS and method for receiving SIB1 PDCCH / PDSCH associated with specific beam direction(s) when information regarding the current SIB1 broadcast status of an NES Cell operating OD-SIB1 and / or the direction of the beam through which SIB1 is transmitted (e.g., SSB index) is provided / configured to the UE

[0322] The UE can receive information regarding the SIB1 broadcast status of a specific NES Cell from the UL WUS configuration provided by Cell A (or the NES Cell's SIBx / RAR). In this case, the NES Cell's SIB1 broadcast status may be one of the following.

[0323] 1) The NES Cell is currently periodically transmitting SIB1.

[0324] 2) The current state where the NES Cell is transmitting OD-SIB1 within the transmission (Tx) window (e.g., sib1-BroadcastStatus = broadcast)

[0325] 3) The NES Cell is currently not transmitting OD-SIB1 (e.g., sib1-BroadcastStatus = not broadcast)

[0326] 1) is a state where the NES Cell switches to a normal cell and periodically transmits SIB1, and K within the MIB transmitted from the NES Cell SSB The value may be less than 24 for FR1 and less than 12 for FR2. In this case, the UE can ignore the configured UL WUS settings and receive SIB1 according to the legacy mechanism without transmitting UL WUS.

[0327] 2) is a state in which SIB1 is being transmitted within the OD-SIB1 Tx window after another UE in the NES Cell requests OD-SIB1 from the BS via the UL WUS, and SIB1 is being transmitted within a Tx window with a duration set through the UL WUS settings. The UE may attempt to receive from the OD-SIB1 PDCCH MO (e.g., Type-0 PDCCH MO) according to the searchSpaceZero and / or controlResourceSetZero set from the UL WUS settings.

[0328] 3) is a state where the NES Cell is not transmitting OD-SIB1, and in order for a UE that has moved to the NES Cell to make an initial connection and / or camp on, it must transmit UL WUS to request the BS to transmit SIB1, and then SIB1 is transmitted in the Tx window.

[0329] Additionally, the UL WUS configuration provided by Cell A may include information related to the beam direction of the SIB1 transmitted from the NES Cell (e.g., SSB index). In the case of conventional on-demand SI, when a UE requests the transmission of specific SI(s) from the BS via PRACH from the RO resource corresponding to a specific SSB, the OD-SI is transmitted by sweeping the beam in all SSB beam directions operating in that cell. However, in some implementations, the NES Cell operating the OD-SIB1 transmits the OD-SIB1 only in the direction corresponding to at least the beam direction in which the UE transmitted the UL WUS, rather than in all beam directions, in order to save energy, and additionally, information regarding the beam direction in which the OD-SIB1 is transmitted can be configured through the UL WUS configuration (or the NES Cell's SIBx and / or RAR).

[0330] Accordingly, in some implementations, the UL WUS configuration provided in Cell A may include information regarding the beam direction of the SIB1 PDCCH / PDSCH currently being broadcast (by request from another UE, etc.) within the OD-SIB1 Tx window in the NES Cell, as in state 2) above. The UE can utilize the broadcast status of the NES Cell and the beam direction information of the SIB1 being transmitted to attempt to receive SIB1 (e.g., attempt to detect SIB1 PDCCH) from the OD-SIB1 PDCCH MO(s) corresponding to that beam direction without transmitting the UL WUS if there is a preferred beam direction selected by the UE based on SSB among the beam direction(s) of the SIB1 PDCCH currently being broadcast. Additionally, through the UL WUS settings, information regarding when the OD-SIB1 Tx window started or ended for the currently broadcasting SIB1 PDCCH beam direction(s) (e.g., the start and / or end point of the OD-SIB1 Tx window) may be configured for each beam direction (e.g., by SSB index). Here, the preferred beam direction refers to a beam corresponding to an SSB index that satisfies the condition that the received strength (e.g., RSRP) and / or quality is above a certain threshold (defined in a pre-configured and / or standard, etc.). If there are multiple beams that satisfy the condition, it may refer to a beam corresponding to an SSB index selected by the UE arbitrarily or according to the conditions defined in the pre-configured and / or standard, or all SSB indices that satisfy the condition.

[0331] If there is no preferred beam direction selected by the UE based on SSB among the beam direction(s) of the currently broadcasting SIB1 PDCCH, for example, if there is no SIB1 PDCCH beam being broadcast within the current OD-SIB1 Tx window or if it is different from the preferred beam direction selected by the UE based on SSB, the UE can send UL WUS to request the BS to transmit the SIB1 PDCCH in the corresponding beam direction and additionally attempt to receive the OD-SIB1 PDCCH in other beam directions broadcasting the OD-SIB1 PDCCH, including the corresponding OD-SIB1 PDCCH MO.

[0332] According to some implementations of this specification, a UE can perform the OD-SIB1 procedure only when necessary, and can obtain the cell's SIB1 without performing the OD-SIB1 procedure if the cell's SIB1 is broadcast (due to requests from other UEs, etc.). Thus, according to some implementations of this specification, benefits can be obtained for saving UE energy as well as network energy.

[0333] <Method #2> When information regarding a beam and / or beam group (e.g., SSB index group) in operation for OD-SIB1 transmission in an NES Cell is provided / configured to a UE, a method for the UE to attempt to receive an OD-SIB1 PDCCH / PDSCH in a beam direction corresponding to the entire SSB group containing the SSB corresponding to the UL WUS direction transmitted by the UE.

[0334] In the case of conventional on-demand SI, when a UE requests the BS to transmit specific SI(s) via PRACH from an RO resource corresponding to a specific SSB, the OD-SI is transmitted by sweeping the beam in all SSB beam directions operating in that cell. However, as explained earlier, from the BS's perspective, transmitting the OD-SIB1 only in the beam direction corresponding to the UL WUS transmitted by the UE may be advantageous in terms of energy saving compared to transmitting the OD-SIB1 by sweeping the beam in all (SSB) beam directions operating in that NES Cell. However, from the perspective of a UE attempting to connect to / camp on an NES Cell, if the OD-SIB1 in a specific beam direction transmitted by the BS is not the preferred beam selected based on the SSB, the UE cannot immediately attempt to receive the OD-SIB1 even if the OD-SIB1 is already being broadcast within the cell due to a request from another UE; instead, the UE must transmit the UL WUS to request the transmission of the OD-SIB1 in the corresponding beam direction.

[0335] Accordingly, in some implementations of this specification, in addition to the method of transmitting OD-SIB1 only in a specific beam direction, information regarding the beam and / or beam group in operation for OD-SIB1 transmission in the NES Cell may be configured to the UE through the UL WUS configuration (or the SIBx and / or RAR of the NES Cell) provided in advance by Cell A. Here, information regarding the beam / beam group may mean configuring a corresponding SSB beam group for each actually transmitted SSB index in operation in the NES Cell, and one or more such SSB beam groups may be configured. In this specification, an SSB beam group may also be referred to as an SSB index group or an SSB group. In some implementations, an SSB actually transmitted in the cell may belong to one or more SSB beam groups.

[0336] A UE may select one of the SSB(s) being transmitted from the NES Cell whose received strength is greater than a specific value (e.g., RSRP threshold) and transmit a UL WUS to the BS in the corresponding direction for an OD-SIB1 request. In this case, the SSB index corresponding to the beam direction of the UL WUS transmitted by the UE may be included in one of the SSB index groups previously configured by the UE. In this case, the UE may attempt to receive the OD-SIB1 PDCCH / PDSCH, expecting it to be transmitted in all beam directions corresponding to the beam group containing the beam, including the beam direction corresponding to the UL WUS transmitted by the UE. For example, if a UE has a preset SSB index group #0 consisting of SSB indices #0, #1, and #2, and the SSB selected for UL WUS transmission is an SSB with SSB index #0, the UE may attempt to receive an OD-SIB1 PDCCH / PDSCH, expecting it to be transmitted in the directions of SSB indices #0, #1, and #2 belonging to the SSB index group #0, including the direction of SSB index #0.

[0337] Meanwhile, as previously mentioned, when the UE requests the BS to transmit OD-SIB1 via the UL WUS, the starting time of the time window for transmitting the OD-SIB1 PDCCH / PDSCH may be set semi-statically or dynamically indicated after an offset (via the UL WUS configuration or the NES Cell's MIB and / or SIBx and / or RAR) with the time when the RAR is received as a response to the UL WUS as the reference time, or the start or end of the RAR window as the reference time. Alternatively, the time window for the OD-SIB1 PDCCH MO may start from the first / last symbol of the earliest CORESET set for Type-0 PDCCH reception after adding the offset to the reference time.

[0338] Within the OD-SIB1 Tx window, there may be multiple OD-SIB1 PDCCH MOs corresponding to a specific beam direction according to a pre-configured searchSpaceZero and / or controlResourceSetZero. In some implementations of this specification, the UE may start / perform OD-SIB1 PDCCH monitoring by assuming that the OD-SIB1 Tx window begins with the OD-SIB1 MO of the beam direction corresponding to the first SSB index within the SSB index group to which the SSB index transmitted by the UE belongs. For example, when the UE performs SIB1 PDCCH monitoring within the OD-SIB1 Tx window, it may perform SIB1 PDCCH monitoring on the (corresponding) SSB beam group associated with the UL WUS transmission direction and not perform monitoring on SIB1 PDCCH MOs that do not belong to the SSB beam group.

[0339] According to some implementations of this specification, one or more SSB beam group(s) (e.g., SSB index group(s)) are configured, and when OD-SIB1 is transmitted to the beam directions of SSB indices belonging to the SSB index group corresponding to the UL WUS transmitted by the UE, network energy saving benefits can be obtained compared to when OD-SIB1 is transmitted in all directions. In addition, compared to when OD-SIB1 is transmitted only to the beam direction of the SSB index corresponding to the UL WUS, the probability of obtaining the OD-SIB1 requested by the UE is increased even if the UE moves, and the probability of other UEs located in the beam directions of the SSB index group also obtaining the OD-SIB1 is increased, thereby preventing unnecessary OD-SIB1 procedures from being performed.

[0340] <Method #3> Method for UE to receive OD-SIB1 PDCCH / PDSCH based on setting / instructing via UL WUS whether the OD-SIB1 message is transmitted omnidirectionally or only in a specific beam direction

[0341] When the UE requests OD-SIB1 from the NES Cell through the UL WUS settings provided / configured from Cell A,

[0342] You can set / instruct whether 1) OD-SIB1 PDCCH / PDSCH is transmitted in all beam directions (i.e., actual transmitted SSB (direction)) operating in the NES Cell, or 2) SIB1 messages are transmitted only in a specific beam direction corresponding to the UL WUS transmitted by the UE (e.g., only at the PDCCH monitoring occasion (MO) corresponding to the SSB index associated with the PRACH transmitted by the UE as the UL WUS).

[0343] At this time, the UE can attempt to receive PDCCH from the OD-SIB1 PDCCH MO using one of the following methods.

[0344] Option 1) How to start monitoring from the first OD-SIB1 PDCCH MO within the RAR window and / or OD-SIB1 Tx window, or from the first OD-SIB1 PDCCH MO after the UL WUS transmission, when UL WUS settings are configured / instructed to always transmit forward-direction OD-SIB1.

[0345] Option 2) When UL WUS settings configure / instruct that OD-SIB1 transmits only in the beam direction corresponding to the UL WUS, how to start monitoring from the OD-SIB1 PDCCH MO (located after the RAR processing time) after receiving the RAR.

[0346] Here, RAR is a response to the UL WUS transmitted by the UE and transmitted by the BS (via the NES Cell), and the starting time of the time window for which OD-SIB1 PDCCH / PDSCH is transmitted can be set semi-statically or dynamically indicated by the RAR after the time offset (time) offset is set by the time the RAR is received as a response to the UL WUS, or the start / end of the RAR window, as the reference time. Alternatively, in some implementations, the time window for OD-SIB1 PDCCH MO can be started from the first / last symbol of the earliest CORESET set for Type0 PDCCH reception after adding the (time) offset to the reference time.

[0347] In this case, the reference time is valid only when the UE has successfully received the RAR, and if the UE fails to receive the RAR, it may skip (i.e., omit) OD-SIB1 PDCCH monitoring and retransmit the UL WUS. If the reference time is the start slot of the RAR window, the OD-SIB1 Tx window may partially or fully overlap with the RAR window depending on the set / indicated (time) offset value. Among the OD-SIB1 PDCCH MOs located within the OD-SIB1 Tx window that overlaps with the RAR window, the UE may not expect PDCCH reception from the OD-SIB1 PDCCH MO(s) located before the UE successfully receives the RAR (e.g., before the time of RAR reception). For example, among the OD-SIB1 PDCCH MOs located within the OD-SIB1 Tx window that overlaps with the RAR window, the UE may not perform PDCCH monitoring for OD-SIB1 reception at the OD-SIB1 PDCCH MO(s) located before the UE successfully receives the RAR. Additionally, even if the UE has received the RAR (regardless of whether the RAR window and the OD-SIB1 Tx window overlap), considering the processing time for the corresponding RAR PDCCH / PDSCH, the UE may expect to receive the PDCCH starting from the OD-SIB1 PDCCH MO located after the RAR PDCCH / PDSCH processing time. For example, even if the UE has received the RAR, the UE may perform PDCCH monitoring for OD-SIB1 reception starting from the OD-SIB1 PDCCH MO located after the RAR PDCCH / PDSCH processing time.

[0348] More specifically, the time point for receiving RAR can be determined by adding the processing time from the time of receiving RAR by applying the UE's PDCCH / PDSCH processing time defined in standard documents, etc., or the pre-set processing time per symbol / slot unit, based on the start / end symbol of the RAR CORESET (hereinafter, RAR CORESET) or the start / end of the slot where the RAR CORESET is located. For example, if the RAR CORESET is located in slot n and the processing time defined in standard documents or pre-set is defined / set to 6 symbols, the UE may attempt to receive PDCCH for receiving OD-SIB1 starting from the OD-SIB1 PDCCH MO located 6 symbols after the end of the slot where the RAR CORESET is located.

[0349] In some implementations, when the RAR window and the OD-SIB1 Tx window partially or completely overlap, the UE starts monitoring from the OD-SIB1 PDCCH MO located within the OD-SIB1 Tx window regardless of whether the UE has received the RAR or before receiving the RAR, and when they overlap (e.g., when the OD-SIB1 TX window starts after the RAR window ends), the UE starts monitoring from the OD-SIB1 PDCCH MO located within the OD-SIB1 Tx window only if the UE has successfully received the RAR. Alternatively, in some implementations, the OD-SIB1 PDCCH MO monitoring behavior may vary depending on the (time) offset value. For example, if the time offset value is 0, a negative value, or less than or equal to a specific value set / defined in advance, the UE starts monitoring from the OD-SIB1 PDCCH MO located within the OD-SIB1 Tx window regardless of whether the UE receives the RAR or before receiving the RAR, and if the time offset value is a positive value or greater than or equal to a specific value set / defined in advance, monitoring starts from the OD-SIB1 PDCCH MO located within the OD-SIB1 Tx window only when the RAR is successfully received.

[0350] <Method #4> How to configure additional information regarding the beam direction of OD-SIB1 transmitted by the BS for the UE via UL WUS settings, and how the UE monitors RAR using the RA-RNTI of the RO corresponding to the SSB group

[0351] The UE can receive information regarding the OD-SIB1 transmission beam of the NES Cell currently operating OD-SIB1 as follows, through UL WUS settings from Cell A (e.g., in the form of a bitmap).

[0352] (1) OD-SIB1 is being transmitted in all directions.

[0353] (2) OD-SIB1 is being transmitted only in a specific beam direction corresponding to the UL WUS transmitted by the UE

[0354] (3) OD-SIB1 is being transmitted to the beam direction(s) corresponding to the pre-set SSB group.

[0355] For example, an information element (IE) containing information related to the OD-SIB1 beam within the UL WUS configuration may be configured / indicated in the form of a 2-bit bitmap as the OD-SIB1 transmission mode of the NES Cell, whichever is (1), (2), and / or (3). If '00' is configured / indicated, the UE can expect that the OD-SIB1 will be transmitted at least once in all SSB beam directions being transmitted on the NES Cell, similar to legacy on-demand system information, and if '01' is configured / indicated, the UE can expect that the OD-SIB1 will be transmitted only in the beam direction corresponding to the UL WUS it transmitted. If '10' is indicated, the UE can know that the OD-SIB1 is being transmitted in the beam direction(s) corresponding to one or more SSB group(s) that are pre-configured in the UL WUS configuration.

[0356] For example, if an SSB group consisting of SSB indices #0, #1, and #2 is configured / directed through the UL WUS setting, and a UE transmits the UL WUS in a direction corresponding to one of SSB index #0, SSB index #1, or SSB index #2, reception of OD-SIB1 can be expected from the direction(s) of the SSB index belonging to the SSB group.

[0357] One or multiple SSB groups may be configured for a cell. When multiple SSB groups are configured for a cell, the SSB group associated with the OD-SIB1 being transmitted on the cell may be configured / indicated separately within the UL WUS configuration, or may be indicated by joint encoding with the remaining state or specific state of the bitmap indicating the OD-SIB1 transmission mode. For example, if SSB group #0 is configured with SSB indices #0, #1, #2, and SSB group #1 is configured with SSB indices #2, #3, #4, then in the above example, if '10' is the OD-SIB1 transmission mode (3) and SSB group #0, and if '11' is the OD-SIB1 transmission mode (3) and SSB group #1, then it may be configured / indicated.

[0358] Characteristically, regarding additional information related to the OD-SIB1 transmission beam direction set / instructed through the UL WUS setting, it is also possible to update and / or override the information through the UL WUS response RAR. For example, the BS may set '01' in the UL WUS setting to set / instruct that the OD-SIB1 is being transmitted in all directions as in (1), but the OD-SIB1 actually transmitted through the UL WUS response RAR can be updated / overridden by information regarding a partial beam (e.g., SSB group #0).

[0359] The RA-RNTI used by the UE for PDCCH detection to schedule the PDSCH carrying the RAR can be determined based on the RO used by the UE to transmit the PRACH. For example, the UE can calculate the RA-RNTI associated with the PRACH time when the random access preamble was transmitted according to the following: RA-RNTI = 1 + s_id + 14*t_id + 14*80*f_id + 14*80*8*ul_carrier_id, where s_id is the index of the first OFDM symbol of the PRACH time (0 ≤ s_id < 14), t_id is the index of the first slot of the PRACH time within the system frame (0 ≤ t_id < 80), where the subcarrier interval for determining t_id is determined based on the value of the subcarrier interval setting u for u = {0, 1, 2, 3}, and for u = {5, 6}, t_id is the index of the 120 kHz slot within the system frame containing the PRACH time, and f_id is the index of the PRACH time in the frequency domain (0 ≤ f_id < 8), ul_carrier_id is the UL carrier used for random access preamble transmission, which is 0 for normal uplink (NUL) carriers and 1 for supplementary uplink (SUL) carriers.

[0360] When BS is transmitting OD-SIB1 to (3), the UE transmits UL WUS from a specific RO through the RACH setting configured from the UL WUS setting, and then monitors all RA-RNTIs associated with the RO that transmitted PRACH, as well as RA-RNTIs of multiple ROs corresponding to SSBs in the SSB group, to check if there is a UE that has already transmitted UL WUS in the beam direction corresponding to another SSB index in the SSB group. If RAR is received, the UE considers the OD-SIB1 procedure successful even if it does not correspond to the RO that transmitted it, and attempts to receive OD-SIB1 immediately (regardless of whether RAR corresponding to the PRACH transmitted it is received).

[0361] In some implementations of this specification, "Cell A" and "NES cell" may correspond to Cell A and NES cell when there are multiple carriers and / or (active) BWPs in a single serving cell, where one carrier / (active) BWP corresponds to Cell A and the other carrier / (active) BWP corresponds to NES cell.

[0362] The methods or implementations of the aforementioned specification may be applied independently, but may also be applied in the form of a combination (or merger) of some proposed methods. For example, Methods #0 through #4 may each be applied independently, or two or more may be applied together. Information regarding the application of the methods / implements of the aforementioned specification (or information regarding the rules of the methods / implements of the aforementioned specification) may be provided by the BS to the UE via a predefined signal (e.g., a physical layer signal or an upper layer signal). In the aforementioned specification, the upper layer may include one or more of functional layers such as MAC, RLC, PDCP, RRC, and SDAP.

[0363] According to the transmission power determination method according to some implementations of this specification, the on-demand downlink signaling procedure can succeed more quickly.

[0364] According to some implementations of the present specification, a UE can perform the OD-SIB1 procedure only when necessary, and can obtain the cell's SIB1 without performing the OD-SIB1 procedure if the cell's SIB1 is broadcast (due to requests from other UEs, etc.), thereby obtaining benefits for saving not only network energy but also UE energy.

[0365] According to some implementations of this specification, network energy saving benefits can be obtained compared to existing SIB1 transmission procedures that are always transmitted or OD-SIB1 procedures that are transmitted only forward when there is a request from a UE. According to some implementations of this specification, since the OD-SIB1 PDCCH is transmitted not only from the SSB associated with the UL WUS but also from the PDCCH MO corresponding to each (actually transmitted) SSB within the SSB group to which the SSB belongs, the probability that the UE that transmitted the UL WUS will successfully obtain the OD-SIB1 can be increased.

[0366] According to some implementations of this specification, other UEs located in a similar beam direction to the UE that transmitted the UL WUS can avoid unnecessarily performing the SIB1 request procedure of the OD-SIB NES cell even if they do not perform the SIB1 request, thereby reducing UE energy savings.

[0367] FIG. 18 illustrates the flow of receiving a downlink (DL) signal in a UE according to some implementations of the present specification.

[0368] A UE may perform operations according to some implementations of this specification in relation to DL signal transmission. A 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 storing instructions that, when executed, cause said at least one processor to perform operations according to some implementations of this specification. A processing device for a UE may include 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 some implementations of this specification. A computer-readable (non-transient) storage medium may store at least one computer program including instructions that, when executed by said at least one processor, cause said at least one processor to perform operations according to some implementations of this 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.

[0369] 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 an on-demand system information block 1 (OD-SIB1) for a first cell (S1801), wherein the setting related to the OD-SIB1 includes a setting related to one or more groups of SSBs, each comprising one or more synchronization signal blocks (SSBs); selecting an SSB of the first cell (S1803); transmitting a SIB1 request related to the selected SSB based on the setting related to the OD-SIB1 for the first cell (S1805); and performing PDCCH monitoring for receiving SIB1 at a time of at least one physical downlink control channel (PDCCH) monitoring corresponding to each transmitted SSB within the SSB group to which the selected SSB belongs, based on the SIB1 request (S1807).

[0370] FIG. 19 illustrates the flow of downlink (DL) signal transmission in a UE according to some implementations of the present specification.

[0371] A BS may perform operations according to some implementations of this specification in relation to DL signal transmission. A BS 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 storing instructions that, when executed, cause said at least one processor to perform operations according to some implementations of this specification. A processing device for a BS may include 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 some implementations of this specification. A computer-readable (non-transient) storage medium may store at least one computer program including instructions that, when executed by said at least one processor, cause said at least one processor to perform operations according to some implementations of this 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.

[0372] 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 an on-demand system information block 1 (OD-SIB1) for a first cell (S1901), wherein the setting related to the OD-SIB1 each includes a setting related to one or more groups of SSBs including one or more synchronization signal blocks (SSBs); transmitting an SSB of the first cell (S1903); receiving a SIB1 request related to the transmitted SSB based on the setting related to the OD-SIB1 for the first cell (S1905); and performing a PDCCH transmission for SIB1 transmission at a time of monitoring at least one physical downlink control channel (PDCCH) corresponding to each transmitted SSB within the SSB group to which the SSB related to the SIB1 request belongs (S1907).

[0373] FIG. 20 illustrates the signal transmission / reception flow between a UE and a network according to some implementations of the present specification.

[0374] A network (e.g., BS) can transmit settings related to an on-demand system information block 1 (OD-SIB1) for a first cell (S2001), and a UE can receive the settings related to the OD-SIB1 for the first cell (S2001). The network can transmit SSB(s) having different SSB index(s) on the first cell (S2002). The UE can attempt to detect an SSB on the first cell and select an SSB that satisfies certain conditions among the SSB(s) detected on the first cell (S2003). The UE can transmit a SIB1 request for the first cell based on the selected SSB (S2004). The network can receive an S1B1 request associated with at least one SSB transmitted on the first cell (S2004). When the above SIB1 request is received, the network may transmit the SIB1 of the first cell to the beam of each transmitted SSB belonging to the SSB group associated with the above SIB1 request. For example, when the above SIB1 request is received, the network may perform PDCCH transmission for SIB1 transmission at at least one PDCCH MO corresponding to each transmitted SSB belonging to the SSB group associated with the received SIB1 request (S2005). When the above SIB1 request is transmitted, the UE may perform PDCCH monitoring for SIB1 reception at at least one PDCCH MO corresponding to each transmitted SSB within the SSB group associated with the above SIB1 request (S2006).

[0375] In some implementations related to FIG. 18, FIG. 19, or FIG. 20, the BS may perform PDCCH transmission for the SIB1 transmission within the OD-SIB1 window. In some implementations related to FIG. 18, FIG. 19, or FIG. 20, the UE may perform PDCCH monitoring for the SIB1 reception within the OD-SIB1 window.

[0376] In some implementations related to FIG. 18, FIG. 19, or FIG. 20, the OD-SIB1 window may be for a certain period after a predetermined offset from the start of the random connection response window.

[0377] In some implementations related to FIG. 18, FIG. 19, or FIG. 20, the predetermined offset may be provided through a system information block.

[0378] In some implementations related to FIG. 18, FIG. 19, or FIG. 20, the UE may omit PDCCH monitoring for receiving the SIB1 during a PDCCH monitoring period that does not correspond to an SSB within the SSB group to which the selected SSB belongs. In some implementations related to FIG. 18, FIG. 19, or FIG. 20, the BS may not perform PDCCH transmission for transmitting the SIB1 during a PDCCH monitoring period that does not correspond to an SSB within the SSB group to which the SSB associated with the SIB1 request belongs.

[0379] In some implementations related to FIG. 18, FIG. 19, or FIG. 20, the OD-SIB1 setting for the first cell may be provided on the second cell.

[0380] In some implementations related to FIG. 18, FIG. 19, or FIG. 20, the SIB1 request may be transmitted at a first power during a random access channel occasion (RO) associated with the selected SSB. In some implementations related to FIG. 18, FIG. 19, or FIG. 20, the method by the UE or the operation for the UE may include: performing power ramping based on not receiving a response to the SIB1 request; and performing a retransmission of the SIB1 request at the ramped power. In some implementations related to FIG. 18, FIG. 19, or FIG. 20, the method by the UE or the operation for the UE may include: performing another on-demand downlink signaling request based on the ramped power based on receiving a response to the retransmission of the SIB1 request.

[0381] In some implementations related to FIG. 18, FIG. 19, or FIG. 20, the OD-SIB1 setting for the first cell may include broadcast information regarding whether the SIB1 of the first cell is being broadcast.

[0382] In some implementations related to FIG. 18, FIG. 19, or FIG. 20, based on the fact that the SIB1 of the first cell is broadcasting, the OD-SIB1 setting for the first cell may include information regarding the SIB1 window to which the PDCCH scheduling the SIB1 is transmitted.

[0383] In some implementations related to FIG. 18, FIG. 19, or FIG. 20, based on the fact that the SIB1 of the first cell is being broadcast, the OD-SIB1 setting for the first cell may include information regarding whether the SIB1 of the first cell is being transmitted to (i) all beams of the first cell, (ii) being transmitted by a beam corresponding to an SSB associated with the SIB1 of the first cell, or (iii) being transmitted by beams corresponding to an SSB group to which the SSB associated with the SIB1 of the first cell belongs.

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

[0385] Implementations of this specification may be used in wireless communication systems, BS or user devices, and other equipment.

Claims

In a method performed by a user device, Receives settings related to an on-demand system information block 1 (OD-SIB1) for a first cell, wherein the settings related to OD-SIB1 each include settings related to one or more groups of SSBs, each including one or more synchronization signal blocks (SSBs); Select the SSB of the first cell above; Based on the OD-SIB1 related settings for the first cell, transmit a SIB1 request associated with the selected SSB; and Based on the above SIB1 request, the method comprises performing PDCCH monitoring for SIB1 reception at a time when at least one physical downlink control channel (PDCCH) corresponding to each transmitted SSB within the SSB group to which the selected SSB belongs is monitoring. method. In paragraph 1, The above user device includes performing PDCCH monitoring for receiving the SIB1 within the OD-SIB1 window, method. In paragraph 2, The above OD-SIB1 window is for a certain period after a predetermined offset from the start of the random connection response window, method. In paragraph 3, The above-mentioned predetermined offset is provided through the system information block, method. In paragraph 1, The above user device does not perform PDCCH monitoring for receiving SIB1 during the PDCCH monitoring period when the selected SSB does not correspond to an SSB within the SSB group to which the selected SSB belongs. method. In paragraph 1, The OD-SIB1 setting for the first cell is received on the second cell, method. In paragraph 1, The above SIB1 request is transmitted to a first power at a random access channel occasion (RO) associated with the selected SSB, and the method is: Perform power ramping based on the fact that a response to the above SIB1 request was not received; It includes performing the retransmission of the above SIB1 request with ramped power, and Based on receiving a response to the retransmission of the above SIB1 request, the user device performs another on-demand downlink signal request based on the ramped power, method. In paragraph 1, The OD-SIB1 setting for the first cell includes broadcast information regarding whether the SIB1 of the first cell is being broadcast. method. In paragraph 8, Based on the fact that the SIB1 of the first cell is broadcasting, the OD-SIB1 setting for the first cell includes information regarding the SIB1 window to which a PDCCH scheduling the SIB1 is transmitted. method. In paragraph 1, Based on the fact that the SIB1 of the first cell is being broadcast, the OD-SIB1 setting for the first cell includes information regarding whether the SIB1 of the first cell is (i) being transmitted to all beams of the first cell, (ii) being transmitted by a beam corresponding to an SSB associated with the SIB1 of the first cell, or (iii) being transmitted by beams corresponding to an SSB group to which an SSB associated with the SIB1 of the first cell belongs. 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: Receives settings related to an on-demand system information block 1 (OD-SIB1) for a first cell, wherein the settings related to OD-SIB1 each include settings related to one or more groups of SSBs, each including one or more synchronization signal blocks (SSBs); Select the SSB of the first cell above; Based on the OD-SIB1 related settings for the first cell, transmit a SIB1 request associated with the selected SSB; and Based on the above SIB1 request, the method comprises performing PDCCH monitoring for SIB1 reception at a time when at least one physical downlink control channel (PDCCH) corresponding to each transmitted SSB within the SSB group to which the selected SSB belongs is monitoring. 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: Receives settings related to an on-demand system information block 1 (OD-SIB1) for a first cell, wherein the settings related to OD-SIB1 each include settings related to one or more groups of SSBs, each including one or more synchronization signal blocks (SSBs); Select the SSB of the first cell above; Based on the OD-SIB1 related settings for the first cell, transmit a SIB1 request associated with the selected SSB; and Based on the above SIB1 request, the method comprises performing PDCCH monitoring for SIB1 reception at a time when at least one physical downlink control channel (PDCCH) corresponding to each transmitted SSB within the SSB group to which the selected SSB belongs is monitoring. 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: Receives settings related to an on-demand system information block 1 (OD-SIB1) for a first cell, wherein the settings related to OD-SIB1 each include settings related to one or more groups of SSBs, each including one or more synchronization signal blocks (SSBs); Select the SSB of the first cell above; Based on the OD-SIB1 related settings for the first cell, transmit a SIB1 request associated with the selected SSB; and Based on the above SIB1 request, the method comprises performing PDCCH monitoring for SIB1 reception at a time when at least one physical downlink control channel (PDCCH) corresponding to each transmitted SSB within the SSB group to which the selected SSB belongs is monitoring. Storage medium. In a method performed by a base station, Transmitting settings related to an on-demand system information block 1 (OD-SIB1) for a first cell, wherein each of the settings related to OD-SIB1 includes settings related to one or more groups of SSBs, each including one or more synchronization signal blocks (SSBs); Transmit the SSB of the first cell above; Based on the OD-SIB1 related settings for the first cell, receiving a SIB1 request related to the transmitted SSB; and The method comprises performing a PDCCH transmission for SIB1 transmission during a monitoring period of at least one physical downlink control channel (PDCCH) corresponding to each transmitted SSB within the SSB group to which the SSB associated with the SIB1 request belongs. 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 an on-demand system information block 1 (OD-SIB1) for a first cell, wherein each of the settings related to OD-SIB1 includes settings related to one or more groups of SSBs, each including one or more synchronization signal blocks (SSBs); Transmit the SSB of the first cell above; Based on the OD-SIB1 related settings for the first cell, receiving a SIB1 request related to the transmitted SSB; and The method comprises performing a PDCCH transmission for SIB1 transmission during a monitoring period of at least one physical downlink control channel (PDCCH) corresponding to each transmitted SSB within the SSB group to which the SSB associated with the SIB1 request belongs. Base station.

Images