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

Abstract

This user equipment may: receive a paging occasion (PO)-related configuration for a cell; receive a first random access channel occasion (RO) configuration and a second RO configuration for the cell; and receive additional RO availability-related information at the earliest available PO from among POs based on the PO-related configuration, on the basis of the initiation of a random access procedure.

Description

A method performed by a device, a 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 performed by a user device (UE) is provided. In another aspect of the present specification, a device is provided comprising at least one transceiver; at least one processor; and at least one computer memory operably connected to the at least one processor and, when executed, storing instructions that cause the at least one processor to perform operations. In yet another aspect of the present specification, a processing device is provided comprising at least one processor; and at least one computer memory operably connected to the at least one processor and, when executed, storing instructions that cause the at least one processor to perform operations. In yet another aspect of the present specification, receiving a paging occasion (PO) related setting for a computer-readable cell, storing at least one program code containing instructions that cause the at least one processor to perform operations when executed; receiving a first random access channel occasion (RO) setting and a second RO setting for the cell; Based on the initiation of a random access process, it may include receiving additional RO availability information from the earliest available PO among the POs based on the above PO-related settings.

[0010] In one aspect of the present specification, a method performed by a base station (BS) 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 connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations. The method or the operations may include: transmitting a paging occasion (PO) related setting for a cell; transmitting a first random access channel occasion (RO) setting and a second RO setting for the cell; and transmitting additional RO availability information at each PO based on the PO related setting.

[0011] In each aspect of the present specification, the method or operations may include determining available ROs among the first ROs associated with the first RO setting or the second ROs associated with the second RO setting, based on the additional RO availability information.

[0012] In each aspect of the present specification, the method by the UE or the operation for the UE may include: performing a physical random access channel (PRACH) transmission in at least one of the available ROs.

[0013] In each aspect of the present specification, the method by the BS or the operations for the BS may include attempting to receive a physical random access channel (PRACH) at at least one of the available ROs.

[0014] In each aspect of this specification, the earliest PO may be determined regardless of the identifier of the user device.

[0015] In each aspect of the present specification, the available ROs may be determined from among the first ROs and the second ROs, based on the additional RO availability information including a value indicating that the additional RO is available.

[0016] In each aspect of the present specification, based on the fact that the information regarding the availability of additional ROs does not include a value indicating that additional ROs are available, the available ROs may be determined only from among the first ROs.

[0017] In each aspect of this specification, the additional RO availability information may be provided through downlink control information (DCI) having a cyclic redundancy check (CRC) scrambled with a paging radio network temporary identifier (P-RNTI).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0034] FIG. 12 illustrates a discontinuous reception (DRX) operation;

[0035] FIG. 13 illustrates a case where a Long DRX cycle and a Short DRX cycle are set;

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

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

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

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

[0040] FIG. 20 illustrates paging times according to several scenarios;

[0041] FIGS. 21 and 22 illustrate common channel adaptation / switching instruction monitoring times according to some implementations of the present specification;

[0042] FIG. 23 illustrates the flow of uplink (UL) signal transmission in a UE according to some implementations of the present specification;

[0043] FIG. 24 illustrates the flow of receiving a UL signal in a BS according to some implementations of the present specification;

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

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

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

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

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

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

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

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

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

[0053] In this specification, information / status / parameters being "configured or pre-configured" may be interpreted as information / status / parameters being provided or pre-provided to the UE through pre-defined signaling from the BS (e.g., system information block (SIB), medium access control (MAC), radio resource control (RRC)). In this specification, information / status / parameters being "defined or pre-defined" may be interpreted as information / status / parameters being known or stored in advance by the BS and the UE without signaling between the BS and the UE.

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

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

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

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

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

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

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

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

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

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

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

[0065] 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 primary SCell (primary SCell, 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.

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

[0067] 3GPP-based communication standards define downlink physical channels corresponding to resource elements that carry information originating from upper layers, and downlink physical signals corresponding to resource elements used by the physical layer but not carrying information originating from upper layers. For example, the physical downlink shared channel (PDSCH), physical broadcast channel (PBCH), and physical downlink control channel (PDCCH) are defined as downlink physical channels, while the reference signal and synchronization signal are defined as downlink physical signals. The reference signal (RS), also referred to as a pilot, refers to a signal of a specific, predefined waveform known to both the BS and the UE. For example, the demodulation reference signal (DMRS), channel state information RS (CSI-RS), and positioning reference signal (PRS) are defined as downlink reference signals. 3GPP-based communication standards define uplink physical channels corresponding to resource elements that carry information originating from upper layers, and uplink physical signals corresponding to resource elements that are used by the physical layer but do not carry information originating from upper layers.For example, the physical uplink shared channel (PUSCH), physical uplink control channel (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.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0081] One or more memories (104, 204) may be connected to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, code, instructions, and / or commands. One or more memories (104, 204) may be composed of ROM, RAM, EPROM, flash memory, hard drive, registers, cache memory, computer read storage media, and / or combinations thereof. One or more memories (104, 204) may be located inside and / or outside of one or more processors (102, 202). Additionally, one or more memories (104, 204) may be connected to one or more processors (102, 202) through various technologies such as wired or wireless connections.

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

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

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

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

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

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

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

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

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

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

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

[0093] 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 s Wow T c 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 ).

[0094]

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

[0096]

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

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

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

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

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

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

[0103]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0122] - 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 the reception of SIB1 and is transmitted via the SSB's PBCH. During initial cell selection, the UE assumes that half-frames containing the SSB(s) repeat at a period of 20 ms. Based on the MIB, the UE can check whether a control resource set (CORESET) exists for the Type0-PDCCH common search space. The Type0-PDCCH common search space is a type of PDCCH search space and is used to transmit the PDCCH that schedules SI messages. If a Type0-PDCCH common seek space exists, the UE can determine (i) multiple consecutive RBs and one or more consecutive symbols that constitute a CORESET and (ii) the PDCCH time (i.e., the time domain location for receiving the PDCCH) based on information within the MIB (e.g., pdcch-ConfigSIB1). If a Type0-PDCCH common seek space does not exist, pdcch-ConfigSIB1 provides information regarding frequency locations where SSB / SIB1 exists and frequency ranges where SSB / SIB1 does not exist.

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

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

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

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

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

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

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

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

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

[0132] The UE can receive information regarding random access from the BS through system information. For example, information regarding random access channel (RACH) times associated with SSBs on the cell may be provided through system information. The UE can select an SSB among those received on the cell for which the reference signal received power (RSRP) measured based on the SSB exceeds a threshold, and transmit an RA preamble through the PRACH associated with the selected SSB. For example, if random access is required, the UE transmits Msg1 (e.g., preamble) to the BS on the PRACH. The BS can distinguish each random access preamble through the time / frequency resource (e.g., RACH time) at which the random access preamble was transmitted and the random access preamble index (PI). When the BS receives a random access preamble from the UE, the BS transmits a RAR message to the UE on the PDSCH. To receive a RAR message, the UE monitors a L1 / L2 control channel (PDCCH) masked with a cyclic redundancy check (CRC) by a Random Access-RnTI (RA-RNTI) containing scheduling information for the RAR message within a preset time window (e.g., ra-ResponseWindow). If scheduling information is received through the PDCCH masked with the RA-RNTI, the UE may receive a RAR message from the PDCCH indicated by the scheduling information. Subsequently, the UE determines whether there is a RAR for itself in the RAR message. Whether a RAR for itself exists can be determined by whether a Random Access preamble ID (RAPID) exists for the preamble transmitted by the UE. The index of the preamble transmitted by the UE and the RAPID may be the same.A RAR includes a corresponding random access preamble index, timing offset information for UL synchronization (e.g., a timing advance command (TAC)), UL scheduling information for sending Msg3 (e.g., a UL grant), and temporary UE identification information (e.g., Temporary-C-RNTI, TC-RNTI). Upon receiving the RAR, the UE sends Msg3 via PUSCH according to the UL scheduling information and timing offset values ​​within the RAR. Msg3 may include the UE's ID (or the UE's global ID). Additionally, Msg3 may include information related to an RRC connection request for initial access to the network (e.g., an RRCSetupRequest message). After receiving Msg3, the BS sends Msg4, a contention resolution message, to the UE. If the UE receives the contention resolution message and the contention is successfully resolved, TC-RNTI is changed to C-RNTI. Msg4 includes the UE's ID and / or It may include information related to the RRC connection (e.g., RRCSetup message). If the information transmitted via Msg3 does not match the information received via Msg4, or if Msg4 is not received for a certain period of time, the UE may report that the contention resolution failed and retransmit Msg3.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0149] Referring to Section 10.2 of 3GPP TS 38.213, the UE can perform PDCCH validation for DL ​​SPS and UL Grant Type 2. For example, the cyclic redundancy check (CRC) of the corresponding DCI format is scrambled with the CS-RNTI provided by the RRC parameter cs-RNTI or the G-CS-RNTI provided by the RRC parameter g-cs-RNTI, the new data indicator field within the DCI format for the enabled transport block is set to 0, and if present within the DCI format, the DFI flag field is set to 0, the time domain resource assignment field within the DCI format points to a row with a single SLIV, the validation is for scheduling activation, and if the PDSCH-to-HARQ_feedback timing indicator field exists within the DCI format, the RRC regarding the list of timing for the given PDSCH to the DL ACK. If no inapplicable value is provided from parameter dl-DataToUL-ACK-r16 or dl-DataToUL-ACK-r17, the UE validates the DL SPS assigned PDCCH or the configured UL grant type 2 PDCCH for scheduling enable or disable scheduling. If the UE is provided with a single configuration for the UL grant type 2 PUSCH or the SPS PDSCH, validation of the DCI format is achieved if all fields for the DCI format are set according to Table 4 or Table 5.Table 4 provides examples of special fields for verifying the validity of a single DL SPS or single UL Grant Type 2 scheduling enable PDCCH when the UE is provided with a single SPS PDSCH or UL Grant Type 2 setting within the DL / UL BWP of the scheduling cell, and Table 5 provides examples of special fields for verifying the validity of a single DL SPS or single UL Grant Type 2 scheduling disable PDCCH when the UE is provided with a single SPS PDSCH or UL Grant Type 2 setting within the DL / UL BWP of the scheduling cell.

[0150]

[0151]

[0152] If the UE is provided with one or more configurations for UL Grant Type 2 PUSCH or SPS PDSCH, the value of the HARQ process number field in the DCI format indicates, respectively, the activation of the corresponding UL Grant Type 2 PUSCH or SPS PDSCH configuration having the same value as provided by the RRC parameter ConfiguredGrantConfigIndex or the RRC parameter sps-ConfigIndex. Validation of the above DCI format is achieved if the redundancy version (RV) field for the above DCI format is set as shown in the following table. The following table exemplifies special fields for validating a single DL SPS or single UL Grant Type 2 scheduling-enabled PDCCH when the UE is provided with multiple SPS PDSCH or UL Grant Type 2 configurations within the DL / UL BWP of the scheduling cell.

[0153]

[0154] If the UE is provided with one or more settings for UL Grant Type 2 PUSCH or SPS PDSCH,

[0155] - If the above UE is provided with the RRC parameter ConfiguredGrantConfigType2DeactivationStateList or sps-ConfigDeactivationStateList, the value of the HARQ process number field in the DCI format points to the corresponding entry for the descheduling of one or more UL Grant Type 2 PUSCH or SPS PDSCH configurations, and

[0156] - If the above UE is not provided with the RRC parameter ConfiguredGrantConfigType2DeactivationStateList or sps-ConfigDeactivationStateList, the value of the HARQ process number field value in the DCI format indicates, respectively, the activation for the corresponding UL Grant Type 2 PUSCH or SPS PDSCH configuration that has the same value as provided by the RRC parameter ConfiguredGrantConfigIndex or the RRC parameter sps-ConfigIndex.

[0157] Validation of the DCI format is achieved when all fields for the DCI format are set according to the following table. The following table exemplifies special fields for validating a single or multiple DL SPS and UL Grant Type 2 scheduling release PDCCH when the UE is provided with multiple SPS PDSCH or UL Grant Type 2 settings within the DL / UL BWP of the scheduling cell.

[0158]

[0159] The actual DL allocation or UL grant for DL ​​SPS or UL grant type 2, and the corresponding modulation and coding scheme, are provided by the resource allocation fields within the DCI format carried by the corresponding DL SPS or UL grant type 2 scheduling enable PDCCH (e.g., the TDRA field providing the TDRA value m, the FDRA field providing the frequency resource block allocation, and the modulation and coding scheme field). When a valid confirmation is achieved, the UE considers the information within the DCI format to be a valid activation or valid release of the DL SPS or configured UL grant type 2.

[0160] The UE is expected to provide HARQ-ACK information in response to the SPS PDSCH release N symbols after the last symbol of the PDCCH providing the SPS PDSCH release. For the serving cell containing the PDCCH providing the SPS PDSCH release, if the parameter processingType2Enabled of the RRC configuration PDSCH-ServingCellConfig is set to enabled, N=5 for u=0, N=5.5 for u=1, and N=11 for u=2; Otherwise, N=10 for u=0, N=12 for u=1, N=22 for u=2, N=25 for u=3, N=100 for u=5, and N=200 for u=6, where u corresponds to the smallest SCS setting among the SCS setting of the PDCCH providing SPS PDSCH release and the SCS setting of the PUCCH carrying HARQ-ACK information in response to SPS PDSCH release.

[0161] In this specification, a PDSCH based on DL SPS is referred to as SPS PDSCH, a PUSCH based on a UL configured grant (CG) is referred to as CG PUSCH, a PDSCH dynamically scheduled by a DCI carried by a PDCCH is referred to as DG PDSCH, and a PUSCH dynamically scheduled by a DCI carried by a PDCCH is referred to as DG PUSCH.

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

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

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

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

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

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

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

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

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

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

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

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

[0174] - monitoringSymbolsWithinSlot: Represents the first OFDMA symbol(s) for PDCCH monitoring within the slot where PDCCH monitoring is configured. 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.

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

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

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

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

[0179] The UE uses DRX to reduce power consumption. A UE operating based on DRX repeatedly switches ON / OFF for receiving operations. The characteristics of DRX, which is utilized for the purpose of reducing unnecessary power consumption of the UE, are as follows. DRX is defined with a structure for a UE in the RRC_IDLE state where an RRC connection between the UE and the BS is not set up (hereinafter referred to as I-DRX) and a structure for a UE in the RRC_CONNECTED state where an RRC connection between the UE and the BS is set up (hereinafter referred to as C-DRX). Both DRX structures are designed to reduce unnecessary power consumption in periods other than those defined by defining a period during which the UE can expect to receive a DL signal (e.g., an active time period or an on-duration period) to occur periodically. For reference, in the case of C-DRX, the Rel-16 standard states that the on-duration start position occurs periodically, and the size of the period that can be configured at this time (i.e., DRX cycle) can be determined / set through higher-level signaling, such as RRC signaling provided by the BS to the UE.

[0180] FIG. 12 illustrates a discontinuous reception (DRX) operation. In particular, FIG. 12 illustrates a DRX cycle for a UE in the RRC_CONNECTED state.

[0181] Referring to FIG. 12, the DRX cycle consists of an ON period and an Opportunity for DRX. The DRX cycle defines a time interval in which the ON period is periodically repeated, followed by a possible period of inactivity. The ON period represents the time interval during which the UE performs PDCCH monitoring to receive PDCCHs. When the DRX is set, the UE performs PDCCH monitoring during the ON period. If a PDCCH is successfully detected during the PDCCH monitoring, the UE activates the inactivity timer and remains awake. Conversely, if no PDCCH is successfully detected during the PDCCH monitoring, the UE enters a sleep state after the ON period ends. Thus, when the DRX is set, the UE may perform PDCCH monitoring / reception discontinuously in the time domain when performing the process and / or method according to the implementation(s) of this specification. For example, if DRX is set, the PDCCH reception occasion (e.g., a slot with a PDCCH seek space) in this specification may be set discontinuously according to the DRX setting. On the other hand, if DRX is not set, the UE may perform PDCCH monitoring / reception continuously in the time domain. For example, if DRX is not set, the PDCCH reception occasion (e.g., a slot with a PDCCH seek space) may be set continuously. Meanwhile, regardless of whether DRX is set, PDCCH monitoring may be restricted in time intervals set as measurement gaps. DRX setting information is received through upper layer (e.g., RRC) signaling, and whether DRX is ON / OFF is controlled by the DRX command of the MAC layer. When DRX is set, the UE may perform PDCCH monitoring discontinuously, as exemplified in FIG. 12.

[0182] The following table illustrates the UE process related to DRX. Referring to the table, DRX configuration information is received via upper layer (e.g., RRC) signaling, and whether DRX is ON / OFF is controlled by DRX commands at the MAC layer. When DRX is configured, the UE can perform discontinuous PDCCH monitoring, as illustrated in FIG. 12.

[0183]

[0184] Here, MAC-CellGroupConfig includes configuration information necessary to set MAC parameters for a cell group. MAC-CellGroupConfig may also include configuration information regarding DRX. For example, MAC-CellGroupConfig may include information related to DRX as follows.

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

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

[0187] - Value of drx-InactivityTimer: Sets the period after the PDCCH that contains a PDCCH directing a new UL or DL ​​transfer for the MAC entity.

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

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

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

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

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

[0193] - drx-ShortCycle (optional): Sets the Short DRX cycle.

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

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

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

[0197] FIG. 13 illustrates the case where Long DRX cycle and Short DRX cycle are set. In particular, FIG. 13 illustrates the case where drx-ShortCycleTimer is set to 2.

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

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

[0200] The following enhancement techniques may be considered.

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

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

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

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

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

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

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

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

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

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

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

[0212] Referring to FIG. 14, the BS identifies or determines the NES solution(s) to be applied (S1401). 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 (S1403). 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 (S1405). 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.

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

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

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

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

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

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

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

[0220] Some implementations of this specification are described below that save energy by configuring UL WUS resources differently depending on the purpose / scenario of the UE requesting an on-demand SIB1, or by changing the operation of the BS after the transmission of the SIB1 by providing an early indication of the purpose of the SIB1 request to the BS.

[0221] FIG. 15 is an example of a process for carrier aggregation (CA) operation using an SSB-less secondary cell (SCell).

[0222] Referring to FIG. 15, the BS can transmit configuration information for SCells to be aggregated through a SCell already configured to the PCell or UE (S1501). For example, the BS can transmit configuration information for CA to provide services to the UE through a CA operation. Here, the CA operation may be an intra-band CA or an inter-band CA. For example, the configuration information for a SCell may include information containing information for adding a SCell (e.g., sCellToAddModList), and specifically, may include a cell index, a physical cell identifier, information related to DL-UL configuration, information related to BWP, information related to cell DTX / DRX, information related to downlink frequency (e.g., FrequencyInfoDL), etc. Subsequently, the UE determines the configuration for the CA operation (S1503) and can perform communication using the BS's PCell and SCell (S1505a, S1505b). 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.

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

[0224]

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

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

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

[0228] On-demand SSB

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

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

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

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

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

[0234] SIB1 transmission on demand

[0235] Some implementations of this specification related to on-demand SIB1 are described in more detail below. Hereinafter, a PDCCH carrying a DCI that schedules a SIB1 transmission (e.g., a PDSCH transmission carrying SIB1) is referred to as a SIB1 PDCCH or a SIB1-related PDCCH, and a PDSCH carrying SIB1 is referred to as a SIB1 PDSCH or a SIB1-related PDSCH.

[0236] In some implementations, a method to reduce energy consumption may be considered in which the BS transmits a SIB1 for a specific cell through an on-demand SIB1 process, and does not transmit a SIB1 for that cell when there is no on-demand SIB1 process. For convenience, SIB1s transmitted for a certain period or interval upon request by a UE are referred to as on-demand SIB1s 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).

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

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

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

[0240] 2) Scenario 2: As illustrated in FIG. 17, a UE that receives an SSB (and / or other downlink signal / channel such as SIB1) at Cell #1 and realizes that SIB1 is not being transmitted on Cell #2 may attempt to camp-on through Cell #2. The UE may trigger the transmission of SIB1 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).

[0241] 3) Scenario 3: As illustrated in FIG. 18, a UE that receives an SSB (and / or other downlink signal / channel such as SIB1) at Cell #1 and realizes that SIB1 is not being transmitted on Cell #2 may attempt to camp-on through Cell #2. The UE may trigger the transmission of SIB1 for Cell #2 by transmitting a signal (e.g., WUS) on Cell #2 requesting SIB1 based on the information provided 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).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0258] FIG. 19 illustrates an example of SSB transmission by a BS operating multiple frequency bands.

[0259] Referring to FIG. 19, a BS operating in three frequency bands can achieve energy savings 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. 19, 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.

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

[0261] In some implementations of this specification, as in F1 of FIG. 19, the frequency band where an SSB and / or SIB1 is transmitted to provide 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 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:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0286] 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 carried out on subsets of periods.

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

[0288] For a Type-2 random access process having common settings for PRACH periods with a Type-1 random access process, if N < 1, one 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.

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

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

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

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

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

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

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

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

[0297]

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

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

[0300] PRACH periods are mapped consequently per corresponding SS / PBCH block index. The indexing of the PRACH period indicated by the mask index value is reset per mapping cycle of consequent 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0318] Adaptation of common signal / channel transmission

[0319] A method to reduce energy consumption by controlling common signal / channel transmissions such as SSB, PRACH, and paging can be considered for the BS. However, while completely turning off the SSB on a cell can significantly reduce energy consumption, stable operation of the cell from the UE's perspective may not be guaranteed without an SSB that performs functions such as time / frequency synchronization or radio resource management (RRM) measurement. Considering this, energy saving effects of the BS can be achieved by changing the transmission pattern of the SSB (e.g., transmission period, periodicity per SSB candidate index(s), SSB candidate index(s) transmitted within one transmission period, transmission power, etc.) depending on the situation.

[0320] In the case of PRACH resources, in the case of contention-based random access (CBRA), the BS does not know when the UE will transmit PRACH, so the BS may consume a lot of energy by always attempting to receive from the configured PRACH resources. Considering this, the energy of the BS can be saved by applying a method to adjust the amount of PRACH resources (e.g., adjusting the cycle of the PRACH resources, pre-configuring PRACH resource set #1 and PRACH resource set #2 and adjusting the amount of resources through instructions such as turning on only one set or turning on both sets, or providing the corresponding amount of PRACH resources for each SSB index uniformly or non-uniformly).

[0321] In the case of paging, paging frames (PFs) and / or paging occasions (POs) were conventionally distributed along the time axis within a DRX cycle (or paging cycle), and the UE attempted to receive paging at a specific PF / PO derived from its ID-based formula. Therefore, conventionally, if the BS intended to transmit paging to multiple UEs simultaneously, it was necessary to transmit paging while frequently breaking the system. To reduce the resulting BS energy consumption, it may be considered to place the PFs and / or POs for paging reception as close to the time axis as possible, or to place them using different frequency axis resources within the same timeframe.

[0322] Low-power wake-up signal and receiver (LP-WUS / WUR)

[0323] Power consumption depends on the length of wake-up periods (e.g., paging cycles). Large eDRX cycles are expected to be used to meet battery life requirements, resulting in high latency; therefore, it may not be suitable for services requiring both long battery life and low latency. Since long eDRX cycles cannot meet latency requirements, eDRX may not be suitable for use cases where latency is critical.

[0324] Recently, candidate technologies to support low-power wake-up signals (LP-WUS) and low-power wake-up receivers (LP-WUR) are being discussed to reduce power consumption of UEs.

[0325] A UE in the RRC_IDLE / RRC_INACTIVE state must typically wake up and receive signals at least once every DRX cycle, and this operation accounts for a significant portion of power consumption during periods without signaling or data traffic. If the UE can receive signals (e.g., perform paging reception) for longer periods rather than every DRX cycle (e.g., the Nth DRX cycle rather than every DRX cycle), power consumption can be drastically reduced. This operation can be supported by the LP-WUR partially replacing the signal reception operations that the main radio (MR) would otherwise perform, and by the LP-WUR operating at ultra-low power consumption. The MR may be used for data transmission and reception and may be set to a hibernation mode that turns off or goes into a deep sleep unless turned on. The following terms may be used in this specification.

[0326] Main radio (MR): A transmit / receive module operating for signals / channels different from those associated with low-power wake-up.

[0327] LP-WUR (LR): A receiving module operating to receive / process signals / channels associated with low-power wake-up.

[0328] In RRC IDLE / INACTIVE mode, when sufficient relaxation is applied to MR radio resource management (RRM) measurements, significant UE power saving gains (up to 90% or more) compared to conventional I-DRX operation (with and without PEI) can be obtained by using LP-WUS / WUR to trigger UE MR paging monitoring. Additionally, compared to conventional eDRX operation, if LP-WUS monitoring and corresponding paging monitoring after MR wake-up are not limited within the existing paging time window (PTW) of eDRX, paging latency is significantly reduced and UE power saving effects are observed at a moderate level.

[0329] In RRC CONNECTED mode, it is observed that moderate UE power saving gains (up to 10% or more) are obtained with minimal impact on capacity by triggering UE MR PDCCH monitoring using LP-WUS / WUR compared to existing UE power saving techniques across various types of XR traffic and system load scenarios. Additionally, it is observed that significant UE power saving gains (up to 60% or more) and moderate Universal Personal Telecommunication (UPT) improvements (up to 10% or more) are achieved for File Transfer Protocol (FTP) and Instant Messaging (IM) traffic when UE MR enters a deep sleep state during LR LP-WUS monitoring. Furthermore, a 3GPP Rel-18 study validated the feasibility of offloading serving cell RRM measurements from UE MR to LP-WUR using a reasonable evaluation methodology.

[0330] The generation / transmission and reception of LP-WUS signals may be (for example) as follows, but are not limited thereto. In conventional NR systems, the BS generates and transmits OFDM signals for control / data signals, and the UE can receive these OFDM signals using a coherent detection / demodulation-based receiver that requires (relatively) accurate synchronization. For example, this requires radio frequency (RF) modules and baseband modules such as power-consuming band-pass filters, fast Fourier transform (FFT), and local oscillators. However, to receive signals at low power in LP-WUR, a non-coherent detection / demodulation-based receiver that does not require such power-consuming modules may be used. In addition, on-off keying (OOK) and frequency shift keying (FSK) may be used as LP-WUS signals for such receivers. Meanwhile, if an LP-WUS generated in a manner entirely different from conventional NR signal generation is introduced, network vendors may face the burden of having to build transmitters for generating new signals. As one method to transmit these OOK / FSK signals while making (maximum) use of the BS's OFDM transmitter, multi-carrier OOK (MC-OOK) or MC-FSK signals may be used. In this case, an MC-OOK (or MC-FSK) signal may refer to a signal generated using only some of the OFDM subcarriers to create a time-domain waveform similar in shape to, for example, an OOK (or FSK) waveform.Through this, it is possible to utilize the OFDM transmitter (to the fullest extent) while enabling non-coherent detection / demodulation-based reception at the receiver.

[0331] FIG. 20 illustrates paging times according to several scenarios. In particular, FIG. 20 illustrates paging times according to the current NR standard.

[0332] If the UE does not have any data transmissions / receptions in progress, the UE enters RRC_IDLE or RRC_INACTIVE to save power. When DL data for the UE arrives at the network, the network sends a paging message (e.g., paging DCI) at a paging occasion (PO) to trigger the RRC setup procedure, RRC Connection Resume procedure, etc. A PO is a set of PDCCH monitoring occasions and may consist of multiple time slots (e.g., subframes or OFDM symbols), and a DCI with a CRC scrambled from the PO to the P-RNTI may be transmitted. For example, PO is a set of 'S*X' consecutive PDCCH monitoring times, where 'S' is the number of actually transmitted SSBs determined by the parameter ssb-PositionsInBurst in SIB1, and 'X' is nrofPDCCH-MonitoringOccasionPerSSB-InPO if set and equal to 1 otherwise. The parameter ssb-PositionsInBurst indicates the time domain indications of SSBs transmitted within a half frame containing SS / PBCH blocks, and the parameter nrofPDCCH-MonitoringOccasionPerSSB-InPO indicates the number of PDCCH monitoring times corresponding to SSBs within the paging time.

[0333] Referring to Section 7.2.1.2.1 of 3GPP TS 38.212, the following information may be transmitted, for example, by a DCI format (e.g., DCI format 1_0) having a CRC scrambled with P-RNTI:

[0334] Short Messages Indicator - 2 bits according to Table 11

[0335] Short Messages - 8 bits according to Table 12. Short messages may be transmitted on PDCCH using P-RNTI with or without associated Paging message using the Short Message field in DCI format 1_0. In Table 12, bit 1 is the most significant bit (MSB). If only the scheduling information for paging, and tracking reference signal (TRS) availability indication if RRC configuration trs-ResourceSetConfig is configured, are carried, this bit field is reserved.

[0336] Frequency domain resource allocation - 4 bits as defined in Section 5.1.2.1 of 3GPP TS 38.213. Ceil{log2(N DL,BWPRB (N DL,BWP RB + 1) / 2)} bits. If only the short message, and TRS availability indication iftrs-ResourceSetConfigis configured, are carried, this bit field is reserved.

[0337] >> N DL,BWP RB is the size of CORESET 0.

[0338] Time domain resource allocation - 4 bits as defined in Section 5.1.2.1 of 3GPP TS 38.214. This bit field is reserved if a short message, and if trs-ResourceSetConfig is configured, carries a TRS availability indication.

[0339] VRB-to-PRB mapping - 1 bit according to Table 13. This bit field is reserved only for short messages, and if trs-ResourceSetConfig is set, only TRS availability indications are carried.

[0340] Modulation and coding scheme (MCS) - 5 bits as defined in Section 5.1.3 of 3GPP TS 38.214, using Table 5.1.3.1-1 of 3GPP TS 38.214. This bit field is reserved only for short messages, and if trs-ResourceSetConfig is set, only TRS availability indications are carried.

[0341] Transport Block (TB) Scaling - 2 bits as defined in Section 5.1.3.2 of 3GPP TS 38.214. This bit field is reserved only for short messages, and if trs-ResourceSetConfig is configured, only TRS availability indications are carried.

[0342] Tracking reference signal (TRS) availability indicator - 1, 2, 3, 4, 5, or 5 bits, where the number of bits is 1 plus the highest value of all the indBitID(s) provided by trs-ResourceSetConfig if set; otherwise, 0 bits.

[0343] > Reserved bits - (8 - M) bits for cell operations with shared spectrum channel access within frequency range 1 or cell operations within frequency range 2-2; (6 - M) bits for cell operations without shared spectrum channel access, where the value of M is the number of bits for the field of 'TRS availability indication' as defined above.

[0344] The above RRC configuration trs-ResourceSetConfig provides reference signal (RS) settings for TRS time(s) for idle or inactive UE(s) in terms of a list of N>=1 non-zero power (NZP) TRS resource set(s).

[0345]

[0346]

[0347]

[0348] In this specification, a PDCCH carrying a DCI format with a CRC scrambled in P-RNTI is referred to as a Paging PDCCH, and a PDSCH scheduled by said Paging PDCCH is referred to as a Paging PDSCH. A UE can decode said Paging PDSCH based on scheduling information within said Paging PDCCH (e.g., frequency domain resource allocation, modulation and coding scheme, etc.). A Paging PDSCH carries paging messages, which are used for notification to one or more UEs and may include one or more UE identifiers (IDs). The following tables illustrate descriptions of paging messages and fields within paging messages.

[0349]

[0350]

[0351] In multi-beam operations, the UE assumes that the same paging message is repeated in all transmitted beams. The paging message is the same for both radio access network (RAN) initiation paging and core network (CN) initiation paging.

[0352] In each DRX cycle, the UE remains in sleep mode during the OFF period but is expected to wake up during the paging period to monitor the PDCCH for paging. The UE monitors one PO per DRX cycle. A paging DRX (also called an idle mode DRX) is defined in which a UE that is RRC_IDLE or RRC_INACTIVE is required to monitor paging channels for only one PO per DRX cycle. In each idle mode DRX (IDRX) cycle, the UE monitors only one PO within a specific PO. When a PDCCH for paging is received in a PO, the UE decodes the PDCCH to receive a paging message. If the paging is not for the UE, the UE goes back to sleep until the next PO. FIG. 17 illustrates paging frames and paging periods that can be monitored by a UE with a specific UE identifier.

[0353] A paging frame (PF) is a radio frame and may contain one or more PO(s) or a starting point of PO. The PF and PO for paging can be determined by predefined formulas. For example, in some implementations, the system frame number (SFN) for the PF can be determined by (SFN + PF_offset) mod T = (T div N) * (UE_ID mod N), and the index i_s indicating the index of the PO can be determined by i_s = floor(UE_ID) mod Ns, where T is the DRX cycle of the UE determined by the minimum value of the default DRX value broadcast as UE-specific DRX value(s) and / or system information, N is the total number of paging frames in T, Ns is the number of paging times for the PF, PF_offset is the offset used for determining the PF, and UE_ID is a value determined based on 5G-S-TMSI. A parameter Ns regarding the number of paging occurrences per paging frame, a parameter nAndPagingFrameOffset used to derive the total number of paging frames in T, a parameter nrofPDCCH-MonitoringOccasionsPerSSB-InPO regarding the number of PDCCH monitoring occurrences corresponding to SSBs within a paging occurrence, and the length of the default DRX cycle can be signaled by SIB1, and the values ​​of N and PF_offset are derived from the parameter nAndPagingFrameOffset. The PDCCH monitoring occurrences for paging can be determined based on the parameter firstPDCCH-MonitoringOccasionOfPO, which indicates the first PDCCH monitoring occurrence for paging of each PO in PF, and the parameter nrofPDCCH-MonitoringOccasionsPerSSB-InPO.The above parameter firstPDCCH-MonitoringOccasionOfPO is signaled by SIB1 for paging in the initial downlink BWP, and can be signaled by the corresponding BWP setting for paging in DL BWPs other than the initial downlink BWP.

[0354] To reduce power consumption, the UE may use Paging Early Indication (PEI) in the RRC_IDLE and RRC_INACTIVE states. PEI informs the UE whether to receive the next PO, and the UE may be notified whether to monitor the PO ahead of its own PO. If PEI settings are provided in the system information, a UE in the RRC_IDLE or RRC_INACTIVE state that supports PEI may monitor PEI using the PEI parameters within the system information. The UE monitors one PEI per DRX cycle. A PEI time (PEI-O) is a set of PDCCH monitoring times and may consist of multiple time slots (e.g., subframes or OFDM symbols) during which the PEI can be sent. In multi-beam operations, the UE assumes that the same PEI is repeated in all transmitted beams. The temporal position of a PEI-O relative to a PO of a UE is determined by a reference point and an offset, said reference point is the start of a reference frame determined by a frame-level offset from the start of the first PF(s) associated with said PEI-O, provided by pei-FrameOffset in SIB1, and said offset is a symbol-level offset from said reference point to the start of the first PDCCH monitoring time of said PEI-O, provided by firstPDCCH-MonitoringOccasionOfPEI-O in SIB1. If a PEI-O is associated with POs of two PFs, said two PFs are consecutive PFs calculated by the parameters PF_offset, T, Ns, and N. When a UE detects a PEI (e.g., a DCI with a CRC scrambled with PEI-RNTI) and said PEI indicates a subgroup to which the UE belongs, said UE monitors the associated PO.If the UE fails to detect a PEI during the monitored PEI period, or if the PEI does not indicate the subgroup to which the UE belongs, the UE is not required to monitor the associated PO. When a PEI and subgrouping are established, UEs monitoring the same PO may be divided into one or more subgroups. With subgrouping, the UE may monitor the associated PO if the corresponding bit for the subgroup to which the UE belongs is indicated as 1 due to the PEI corresponding to its PO. For more details regarding PEIs, refer to 3GPP TS 38.304 and 3GPP TS 38.213.

[0355] For convenience, some implementations of this specification are described below using the case where UL WUS is transmitted over cell A (or over an NES cell) and the 4-stage RACH process as examples, but some implementations of this specification may also apply to the case where UL WUS is transmitted over an NES cell (or over cell A) and the 2-stage RACH process (and contention-based random access (CBRA) and contention-free random access (CFRA)). Additionally, in some implementations of this specification, the UE may receive UL WUS configurations for requesting SIB1 for said NES cell from the SIBx (e.g., SIB1) of cell A or from the NES cell, and may also receive information on whether to transmit UL WUS over cell A or over the NES cell.

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

[0357] For example, some implementations of this specification are described below that instruct UEs in IDLE and / or INACTIVE and / or CONNECTED modes to adapt and / or switch based on DCI when the network intends to dynamically adapt and / or switch the periodicity and / or density and / or settings of a common channel (e.g., SSB and / or PRACH) for energy saving of the BS.

[0358] The UE receives the information necessary to transmit a PRACH (e.g., information regarding time / frequency resources) through the BS's SIB1 or UE-specific RRC signaling, and can transmit a PRACH at determined / set RACH occasions (ROs) based on the said information. The BS must wake up at each RO to receive the PRACH that the UE may transmit and wait for PRACH reception. Therefore, if the RO period set for the UE is short, the energy consumption of the BS may be relatively higher compared to when the RO period is set long. However, if ROs are set with too long a period to save energy for the BS, if there is no RO resource near the time when the UE needs to transmit a PRACH for cell connection, it may have to wait until the next RO resource becomes available before transmission, which can increase connection delay. This leads to scheduling delays and may result in performance degradation of the UE. In addition, the BS can save energy by switching to sleep mode when there are few UEs in connected mode or periods of temporary lack of data activity depending on the situation within the cell. However, since it must frequently wake up to receive and check for PRACH transmitted by UEs in the RO configured in the cell, it cannot remain in sleep mode for a long time, making it difficult to expect significant energy saving benefits. Therefore, in such cases, setting a long RO periodicity can be advantageous in terms of BS energy saving. However, according to current standards, only semi-static methods (such as SI modification) are allowed to change settings such as the cell's RO periodicity, which takes a relatively long time and may make it difficult to quickly respond to opportunities for energy saving.

[0359] In some implementations, a method may be considered to receive a default RO (default RO, D-RO) setting for legacy UEs (setting relatively sparse ROs) and an additional RO (e.g., A-RO) setting for NES UEs (e.g., UEs supporting R19 NES features) so that the connection delay of the UE is not too long and some energy saving benefits of the BS can be expected. In this case, the A-RO setting may be included within the D-RO setting and provided with a time / frequency offset or a masking / muting pattern, or may be provided by a separate PRACH (e.g., Msg1 and / or MsgA) setting, and the PRACH (Msg1 / MsgA) setting index for D-RO and the PRACH (Msg1 / MsgA) setting index for A-RO may be the same or different. Here, RO for legacy UEs may refer to RO resources for 4-phase RACH under Release-15 of the 3GPP standard, RO resources for 2-phase RACH under Release-16, RO resources for reduced capability (Redcap) UEs under Release-17, or RO resources for coverage enhancement (CE) under Release-18. There may be one or more A-RO configurations, and the RO pattern / period may be configured differently for each A-RO configuration. The activation of an A-RO configuration may be instructed to NES-capable UE(s) via a pre-configured / defined index, or switching between A-RO configurations may be instructed if an A-RO configuration is already activated. One or more A-RO configurations may be configured via SIB1, similar to D-RO configurations, or they may be configured via separate RRC signaling.

[0360] An NES-enabled UE can receive settings from the BS regarding whether only A-RO is available or if both D-RO and A-RO are available among the configured ROs, as well as the priority for which one to use first. If there is no separate setting for this, it can be interpreted that the NES-enabled UE is configured to have both D-RO and A-RO available. Even when the NES-enabled UE is configured to use both D-RO and A-RO, A-RO is normally disabled, allowing all UEs (e.g., both legacy UEs and NES-enabled UEs) to use only D-RO, and A-RO can be enabled by a dynamic instruction from the BS (at the request of a UE). Alternatively, when the activation (disabling) of A-RO is instructed, the activation (disabling) status of D-RO may be instructed together or separately.

[0361] In some implementations of this specification, BS may pre-configure multiple common channel configurations for common channel adaptation / switching (e.g., SSB / PRACH (Msg1 / MsgA)). For example, BS may set up multiple SSB configurations (e.g., SSB_config#1, SSB_config#2, etc.) with different SSB-related parameters such as SSB cycles (group common (GC)-) and direct the activation / deactivation of a specific configuration or switching from a specific configuration to another configuration through DCI. Additionally, in some implementations of this specification, a method of instructing adaptation / switching based on (GC-)DCI may be considered to dynamically instruct UEs in IDLE / INACTIVE / CONNECTED mode whether to enable (or disable) A-RO, and said (GC-)DCI may be scrambled into a specific RNTI (e.g., P-RNTI, and / or SI-RNTI, and / or C-RNTI, and / or PEI-RNTI) and transmitted to all UEs in the cell.

[0362] <Method #1> A method in which common channel adaptation / switching is instructed to UEs in CONNECTED mode or UEs in IDLE / INACTIVE mode via a specific (GC-)DCI (e.g., a DCI scrambled with P-RNTI or SI-RNTI).

[0363] FIGS. 21 and 22 illustrate common channel adaptation / switching instruction monitoring times according to some implementations of the present specification.

[0364] If BS intends to instruct common channel adaptation / switching to UEs in all RRC states (e.g., IDLE / INACTIVE / CONNECTED mode) through a DCI scrambled with P-RNTI or SI-RNTI (e.g., a DCI with a CRC scrambled with P-RNTI or S-RNTI), particularly for UEs in CONNECTED mode, it may be necessary to monitor the DCI at a specific period or at a specific monitoring time in addition to the UE actions defined in the current standard. For example, if the BS indicates that the A-RO is available, the BS must attempt to receive PRACH from the A-RO as well, and if it does not, it will attempt to receive PRACH only from the D-RO. Therefore, if the UE does not receive information indicating the availability of the A-RO even though the BS has indicated that the A-RO is available, the BS will unnecessarily perform PRACH monitoring on the A-RO even though no PRACH is transmitted from the A-RO, or if the UE determines that the A-RO is available even though the BS has indicated that the A-RO is unavailable, the BS will fail to receive the PRACH transmitted from the A-RO.

[0365] For example, in the case of a paging DCI (e.g., a DCI with a CRC scrambled with P-RNTI), the default behavior for a UE in IDLE / INACTIVE mode is to monitor the paging occasion (PO) corresponding to its UE ID once every DRX cycle, whereas UEs in CONNECTED mode only need to monitor the PO once during each modification period to check for changes in system information (SI), and it is also possible to monitor POs that are not linked to its UE ID. However, in the case of an earthquake and tsunami warning system (ETWS) / commercial mobile alert service (CMAS) capable UE, the UE reads the paging at least once every default paging cycle to check for the presence of ETWS / CMAS notifications, even when in CONNECTED mode.

[0366] In some implementations of this specification, similar to the ETWS / CMAS-enabled UE operation described in the example above, for an NES-enabled connected UE, the UE needs to verify whether the A-RO is valid when it intends to transmit PRACH (Msg1 or MsgA) from the A-RO. Therefore, in some implementations of this specification, the UE may be defined (in standard documents, etc.) to monitor the PO every DRX cycle to check the adaptation / switching status (e.g., enabled or disabled) of the common channel (e.g., SSB / PRACH (Msg1 / MsgA)), or may be configured / instructed in advance by the BS. Alternatively, for an NES-enabled connected UE, the UE may be configured to monitor the PO at a certain frequency (or at a certain frequency to check for PRACH adaptation via the PO). For example, in the case of an NES-enabled UE, even if the UE is in CONNECTED mode, it may be configured to perform PO monitoring at a frequency that is the same as or different from the default DRX cycle set for PO monitoring by an IDLE / INACTIVE mode UE or the DRX cycle set through separate RRC signaling. Alternatively, if there is no separate PO monitoring setting for CONNECTED mode, the DRX cycle to be applied in this case may be defined in a standard document, etc., or the UE may be defined or configured to always perform PO monitoring at a frequency identical to the DRX cycle of IDLE / INACTIVE mode.

[0367] In addition, in cases where a UE in CONNECTED mode can initiate (e.g., trigger) PRACH (Msg1 / MsgA) on its own, such as a scheduling request (SR), or where a UE in IDEL / INACTIVE mode initiates PRACH (Msg1 / MsgA) on its own, such as a system information (SI) request, random access based small data transmission (RA-SDT), or mobile originated (MO) initial access, the UE can initiate PRACH (Msg1 / MsgA) transmission on its own without instructions from paging. Therefore, when a UE transmits PRACH (Msg1 / MsgA) without PO confirmation in this way, it may be defined (in standard documents, etc.) to always use only D-RO regardless of whether A-RO is enabled or disabled (i.e., whether A-RO is valid), or it may be configured or instructed by BS in advance. Alternatively, if the length of the time gap between the time when the activation of A-RO is instructed and the A-RO to transmit PRACH (Msg1 / MsgA) is defined in a standard document, etc., or if it is below a threshold set in advance for the UE, PRACH may be transmitted using A-RO, and if it is above the threshold, PRACH may be transmitted using D-RO.

[0368] Alternatively, a UE in IDLE / INACTIVE / CONNECTED mode may be defined (in standard documents, etc.) or instructed in advance by the BS to always check the adaptation / switching status of the common channel through the nearest PO among the POs configured for the UE (even if it is not the PO that it needs to monitor) before performing a self-initiated PRACH (Msg1 / MsgA) transmission, and then transmit the PRACH (Msg1 / MsgA). For example, a UE with UE ID i may attempt to receive the Paging DCI from the nearest PO that can be monitored among all POs, including the PO for its UE ID i, as well as other POs, and among the POs within each PO, not just the PO for its UE ID i, and may check whether the A-RO is available based on the A-RO availability field within the Paging DCI. When a PRACH transmission is initiated or triggered (without receiving paging from the network), referring to FIG. 21, the UE with UE ID i can check the DCI containing common channel adaptation / switching instruction information in the most available PO within the nearest available PF regardless of UE ID i, and check whether an A-RO is available based on the common channel adaptation / switching instruction information. Alternatively, the adaptation / switching status can be checked through the PO located at the front or back among the POs (which the UE can monitor) set before a specific duration from the A-RO that intends to transmit PRACH (Msg1 / MsgA), and if there is no PO (which the UE can monitor) set before the specific duration, it may be defined (in standard documents, etc.) to always use a D-RO or configured in advance from the BS.For example, referring to FIG. 22, when a PRACH transmission is initiated or triggered (without receiving paging from the network), the UE can check whether common channel adaptation / switching is possible through the PO located at the foremost (see PO #a in FIG. 22) or the furthest (see PO #b in FIG. 22) among the POs located at a specific time Toffset before the A-RO intended for use in the PRACH transmission. This method, described with reference to FIG. 21 and FIG. 22, allows the BS to indicate A-RO availability in all POs of the cell regardless of the UE ID when an A-RO is set for the cell, since the A-DO will be available or unavailable when an A-RO is set for the cell, and allows the UE to quickly determine A-RO availability by monitoring POs not associated with its UE ID. Through this, RO congestion problems within the cell can be quickly managed, and the BS's energy saving opportunities can be increased.

[0369] Meanwhile, in some implementations of this specification, UEs in IDLE / INACTIVE / CONNECTED mode configured to monitor PEI may receive some of the configured PEI times (PEI-O) / POs as common channel adaptation / switching instructions. In this case, legacy PEI / paging information in the corresponding PEI-O / PO is retained, and additional common channel adaptation / switching instructions may be included. Furthermore, in some implementations of this specification, common channel adaptation / switching may be indicated via Msg2 and / or PO and / or PEI-O. It may be defined (in standard documents, etc.) or pre-configured that if the UE fails to obtain common channel adaptation / switching instruction information via Msg2 / PO / PEI-O, it must always utilize only D-RO, and conversely, if successful, it must always use A-RO (or which RO to use).

[0370] For convenience, common channel adaptation / switching instruction methods according to some implementations of this specification have been described above using P-RNTI as an example, but the methods described above can be applied in the same way to legacy RNTIs such as SI-RNTI or new RNTIs defined / configured for common channel adaptation / switching.

[0371] Characteristically, in some implementations of this specification, it is also possible to replace (GC-)DCI with LP-WUS to indicate common channel adaptation / switching. Similar to PEI DCI, information regarding whether to indicate common channel adaptation / switching in P-RNTI DCI may be provided via a 1-bit flag within LP-WUS, or the common channel adaptation / switching may be indicated directly in LP-WUS. Additionally, for a UE with eDRX configured, since it can check SI updates by checking another's PO, it may be defined in standard documents, etc., or configured in advance from BS to check its own PO or another's PO to check and transmit whether to indicate common channel adaptation / switching before initiating PRACH (Msg1 / MsgA).

[0372] <Method #2> Method for instructing common channel adaptation / switching via Random Access Response (RAR) DCI / PDSCH (MAC-CE) considering PRACH (Msg1 / MsgA) retransmission

[0373] A NES-enabled UE can select either D-RO or A-RO to transmit PRACH (Msg1 / MsgA), and if the BS receives it successfully, it can transmit RAR (Msg2) as a response. If the UE does not receive the RAR within the RAR window, it considers the PRACH (Msg1 / MsgA) to have failed and performs a retransmission; however, if a retransmission is required after the initial PRACH (Msg1 / MsgA) has been transmitted via A-RO, it is necessary to decide whether to use D-RO or A-RO. Alternatively, if common channel adaptation / switching can be indicated via the RAR message, the UE may be instructed which RO to use to attempt retransmission upon failure to receive Msg4.

[0374] When common channel adaptation / switching is instructed through a RAR DCI (e.g., a DCI scheduling a PDSCH carrying a RAR) or a medium access control (MAC) control element (CE) (carried by a PDSCH) and the A-RO that was previously in an inactive state is activated,

[0375] Opt 1: The UE does not apply common channel adaptation / switching until the current RACH process is complete, or

[0376] Opt 2: If Msg2 does not contain the UE's RAPID, maintain the current RACH process and retransmit Msg1 using common channel adaptation / switching. Or, if Msg2 contains the UE's RAPID and UL grant, transmit Msg3, and if Msg3 / Msg4 fails, maintain the current RACH process and retransmit Msg1 using common channel adaptation / switching.

[0377] Opt 3: If Msg2 does not include the UE's RAPID, abort the current RACH process and restart the RACH process by applying common channel adaptation / switching. Alternatively, if Msg2 includes the UE's RAPID and UL grant, send Msg3; if Msg3 / Msg4 fails, abort the current RACH process and restart RACH by applying RO adaptation.

[0378] When common channel adaptation / switching is instructed via RAR DCI or MAC-CE and the previously active A-RO is deactivated,

[0379] Opt 1: The UE applies common channel adaptive / switching until the current RACH process ends, or

[0380] Opt 2: If Msg2 does not contain the UE's RAPID, maintain the current RACH process and retransmit Msg1 without applying common channel adaptation / switching. Or, if Msg2 contains the UE's RAPID and UL grant, transmit Msg3, and if Msg3 / Msg4 fails, maintain the current RACH process and retransmit Msg1 without applying common channel adaptation / switching.

[0381] Opt 3: If Msg2 does not include the UE's RAPID, stop the current RACH process and restart RACH without applying common channel adaptation / switching. Alternatively, if Msg2 includes the UE's RAPID and UL grant, send Msg3, and if Msg3 / Msg4 fails, stop the current RACH process and restart RACH without applying common channel adaptation / switching.

[0382] According to some implementations of the present specification, the BS can adjust the density of ROs as needed by providing the UE with a PRACH setting in which ROs are sparsely distributed or have a long period, an additional PRACH setting in which ROs are different from the ROs of the PRACH setting or ROs are densely distributed or have a short period, and by enabling / disabling the additional PRACH setting or switching between different PRACH settings, thereby efficiently obtaining energy saving benefits.

[0383] FIG. 23 illustrates the flow of uplink (UL) signal transmission in a UE according to some implementations of the present specification.

[0384] A UE may perform operations according to some implementations of this specification in relation to UL 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.

[0385] 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 paging occasion (PO) related setting for a cell (S2301); receiving a first random access channel occasion (RO) setting and a second RO setting for the cell (S2303); and receiving additional RO availability information at the earliest available PO among the POs based on the PO related setting, based on the initiation of a random access process (S2305).

[0386] FIG. 24 illustrates the flow of receiving an uplink (UL) signal in a BS according to some implementations of the present specification.

[0387] A BS may perform operations according to some implementations of this specification in relation to receiving a UL signal. 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.

[0388] 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 paging occasion (PO) related setting for a cell (S2401); transmitting a first random access channel occasion (RO) setting and a second RO setting for the cell (S2403); and transmitting additional RO availability information for each PO based on the PO related setting (S2405).

[0389] FIG. 25 illustrates a signal transmission / reception flow between a UE and a network according to some implementations of the present specification. A network (BS) can transmit PO-related settings for a cell (S2501), and a UE can receive the PO-related settings (S2501). The network can provide a first RO setting and a second RO setting for the cell (S2502), and a UE can receive the first RO setting and the second RO setting for the cell (S2502). The network can provide information regarding additional RO availability at each PO based on the PO-related settings (S2503). When a random access process is initiated, the UE can obtain the information regarding additional RO availability by performing PDCCH monitoring based on P-RNTI at the earliest available PO among the POs based on the PO-related settings (S2504).

[0390] In some implementations related to FIG. 23, FIG. 24 or FIG. 25, the method or operations may include determining available ROs among the first ROs associated with the first RO setting or the second ROs associated with the second RO setting, based on the additional RO availability information.

[0391] In some implementations related to FIG. 23 or FIG. 25, the method by the UE or the operation for the UE may include: performing a physical random access channel (PRACH) transmission in at least one of the available ROs.

[0392] In some implementations related to FIG. 24 or FIG. 25, the method by the BS or the operations for the BS may include attempting to receive a physical random access channel (PRACH) at at least one of the available ROs.

[0393] In some implementations related to FIG. 23 or FIG. 25, the earliest PO may be determined regardless of the identifier of the user device.

[0394] In some implementations related to FIG. 23, FIG. 24, or FIG. 25, the available ROs may be determined from among the first ROs and the second ROs based on the additional RO availability information including a value indicating that the additional RO is available.

[0395] In some implementations related to FIG. 23, FIG. 24, or FIG. 25, the available ROs may be determined only from among the first ROs, based on the fact that the additional RO availability information does not include a value indicating that the additional RO is available.

[0396] In some implementations related to FIG. 23, FIG. 24 or FIG. 25, the additional RO availability information may be provided through downlink control information (DCI) with a cyclic redundancy check (CRC) scrambled with a paging radio network temporary identifier (P-RNTI).

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

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

Claims

1. In a method performed by a user device, Receive settings related to the paging occasion (PO) for the cell; Receiving a first random access channel occasion (RO) setting and a second RO setting for the above cell; Based on the initiation of a random access process, receiving additional RO availability information from the earliest available PO among the POs based on the above PO-related settings; Based on the information regarding the additional RO availability mentioned above, determine the available ROs among the first ROs associated with the first RO setting or the second ROs associated with the second RO setting; and Comprising performing a physical random access channel (PRACH) transmission in at least one of the above available ROs, method.

2. In Paragraph 1, The earliest PO mentioned above is determined regardless of the identifier of the user device, method.

3. In Paragraph 1, Based on the fact that the information regarding the availability of additional ROs includes a value indicating that additional ROs are available, the available ROs are determined among the first ROs and the second ROs. method.

4. In Paragraph 1, Based on the fact that the information regarding the availability of additional ROs above does not include a value indicating that additional ROs are available, the available ROs are determined only from among the first ROs, method.

5. In Paragraph 1, The above additional RO availability information is received via downlink control information (DCI) having a cyclic redundancy check (CRC) scrambled with a paging radio network temporary identifier (P-RNTI), method.

6. At least one transmitter / receiver; At least one processor; and It includes at least one computer memory operablely connectable to the at least one processor and, when executed, stores instructions that cause the at least one processor to perform operations, wherein the operations are: Receive settings related to the paging occasion (PO) for the cell; Receiving a first random access channel occasion (RO) setting and a second RO setting for the above cell; Based on the initiation of a random access process, receiving additional RO availability information from the earliest available PO among the POs based on the above PO-related settings; Based on the information regarding the additional RO availability mentioned above, determine the available ROs among the first ROs associated with the first RO setting or the second ROs associated with the second RO setting; and Comprising performing a physical random access channel (PRACH) transmission in at least one of the above available ROs, User device.

7. At least one processor; and It includes at least one computer memory operablely connectable to the at least one processor and, when executed, stores instructions that cause the at least one processor to perform operations, wherein the operations are: Receive settings related to the paging occasion (PO) for the cell; Receiving a first random access channel occasion (RO) setting and a second RO setting for the above cell; Based on the initiation of a random access process, receiving additional RO availability information from the earliest available PO among the POs based on the above PO-related settings; Based on the information regarding the additional RO availability mentioned above, determine the available ROs among the first ROs associated with the first RO setting or the second ROs associated with the second RO setting; and Comprising performing a physical random access channel (PRACH) transmission in at least one of the above available ROs, Processing unit.

8. In a computer-readable non-transitory storage medium, The above storage medium stores at least one program code including instructions that cause at least one processor to perform operations when executed, and said operations are: Receive settings related to the paging occasion (PO) for the cell; Receiving a first random access channel occasion (RO) setting and a second RO setting for the above cell; Based on the initiation of a random access process, receiving additional RO availability information from the earliest available PO among the POs based on the above PO-related settings; Based on the information regarding the additional RO availability mentioned above, determine the available ROs among the first ROs associated with the first RO setting or the second ROs associated with the second RO setting; and Comprising performing a physical random access channel (PRACH) transmission in at least one of the above available ROs, Storage medium.

9. In a method performed by a base station, Transmit paging occasion (PO) related settings for the cell; Transmit a first random access channel occasion (RO) setting and a second RO setting for the above cell; Transmit additional RO availability information from each PO based on the above PO-related settings; Based on the information regarding the additional RO availability mentioned above, determine the available ROs among the first ROs associated with the first RO setting or the second ROs associated with the second RO setting; and A method comprising attempting to receive a physical random access channel (PRACH) at least one of the above available ROs, method.

10. In Paragraph 9, Based on the fact that the information regarding the availability of additional ROs includes a value indicating that additional ROs are available, the available ROs are determined among the first ROs and the second ROs. method.

11. In Paragraph 9, Based on the fact that the information regarding the availability of additional ROs above does not include a value indicating that additional ROs are available, the available ROs are determined only from among the first ROs, method.

12. In Paragraph 9, The above additional RO availability information is transmitted via downlink control information (DCI) having a cyclic redundancy check (CRC) scrambled with a paging radio network temporary identifier (P-RNTI), method.

13. 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: Transmit paging occasion (PO) related settings for the cell; Transmit a first random access channel occasion (RO) setting and a second RO setting for the above cell; Transmit additional RO availability information from each PO based on the above PO-related settings; Based on the information regarding the additional RO availability mentioned above, determine the available ROs among the first ROs associated with the first RO setting or the second ROs associated with the second RO setting; and A method comprising attempting to receive a physical random access channel (PRACH) at least one of the above available ROs, Base station.

Images