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

By determining control resource sets and search spaces through PBCH information, the method addresses inefficiencies in existing communication systems, improving data speeds, connectivity, and reliability in multi-RAT environments.

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

Patent Information

Application Number
PCT/KR2026/005753
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-07
Filing Date
2026-04-30
Publication Date
2026-11-12

Smart Images

  • Figure KR2026005753_12112026_PF_FP_ABST
    Figure KR2026005753_12112026_PF_FP_ABST
Patent Text Reader

Abstract

A UE may be configured to: detect a physical broadcast channel (PBCH); obtain first information related to a parameter set and second information related to a physical downlink control channel (PDCCH) configuration, based on the PBCH; and determine a control resource set (CORESET) for a search space (SS) set and a PDCCH monitoring period for the SS set, based on the first information and the second information.
Need to check novelty before this filing date? Find Prior Art

Description

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

[0001] This specification relates to a wireless communication system.

[0002] 5G mobile communication systems are a successor technology to LTE (long term evolution) and are new clean-slate type mobile communication systems with characteristics such as high performance, low latency, and high availability. In the case of 5G NR, all available spectrum resources can be utilized, ranging from low frequency bands below 1 GHz to intermediate frequency bands from 1 GHz to 10 GHz, and high frequency (millimeter wave) bands above 24 GHz.

[0003] However, there is a growing need to develop a new mobile communication system that goes beyond the limitations of 5G mobile communication and possesses (i) very high data speeds per device, (ii) a very large number of connected devices, (iii) global connectivity, (iv) very low latency, (v) reduced energy consumption of battery-free IoT (internet of things) devices, (vi) ultra-reliable connectivity, and (vii) machine learning capabilities.

[0004] One technical objective of this specification is to provide methods and devices for the efficient use of wireless resources in a spectrum where existing communication systems and new communication systems coexist.

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

[0006] In one aspect of the present specification, a method by user equipment (UE) is provided. In another aspect of the present specification, a UE is provided comprising at least one transceiver; at least one processor; and at least one computer memory operably connected to the at least one processor and, when executed, storing instructions that cause the at least one processor to perform operations. In yet another aspect of the present specification, a processing device is provided comprising at least one processor; and at least one computer memory operably connected to the at least one processor and, when executed, storing instructions that cause the at least one processor to perform operations. In yet another aspect of the present specification, a computer-readable non-transitory storage medium is provided that stores at least one program code including instructions that cause the at least one processor to perform operations when executed. The method or the operations include: detecting a physical broadcast channel (PBCH); Based on the above PBCH, it may include obtaining first information related to a parameter set and second information related to a physical downlink control channel (PDCCH) setting; determining a control resource set (CORESET) for a search space (SS) set and a PDCCH monitoring time for the SS set based on the first information and the second information; and receiving the PDCCH on the CORESET at the PDCCH monitoring time.

[0007] In one aspect of the present specification, a method by means of a base station (BS) is provided. In another aspect of the present specification, a BS 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 first information related to a parameter set and second information related to a physical downlink control channel (PDCCH) setting based on a physical broadcast channel (PBCH); and transmitting a PDCCH on a control resource set (CORESET) for a search space (SS) set at a time of PDCCH monitoring for said SS set based on said first information and said second information.

[0008] In each aspect of the specification, based on the first information including a first value, the CORESET and the SS set may be associated with a first parameter set, and based on the first information including a second value, the CORESET and the SS set may be associated with a second parameter set.

[0009] In each aspect of the specification, the first parameter set may be associated with the first RAT, and the second parameter set may be associated with the second RAT.

[0010] In each aspect of the specification, the first information may be included within a master information block (MIB) carried by the PBCH.

[0011] In each aspect of the specification, the first information may be obtained based on a demodulation reference signal (DMRS) sequence for the PBCH.

[0012] In each aspect of this specification, the second information may be obtained based on a field related to PDCCH settings within a master information block (MIB) carried by the PBCH. The field related to PDCCH settings may include N1 bits for information related to CORESET and N2 bits for information related to SS sets. The CORESET may be determined based on the information related to CORESET, and the timing of PDCCH monitoring may be determined based on the information related to SS.

[0013] In each aspect of the present specification, the method or operation may further include: omitting decoding or transmitting a physical downlink shared channel (PDSCH) scheduled by the DCI based on the fact that a specific field included in the downlink control information (DCI) within the PDCCH includes a first value; and acquiring or transmitting system information from or on the PDSCH scheduled by the DCI based on the fact that the specific field includes a second value.

[0014] In each aspect of the present specification, the method or operation may further include receiving or transmitting a physical downlink shared channel (PDSCH) based on downlink control information (DCI) within the PDCCH. The PDSCH may carry a first system information part and a second system information part, and the DCI may include a field containing a value associated with the first system information part or a value associated with the second system information part.

[0015] In each aspect of the present specification, the PDCCH may include downlink control information (DCI) comprising a field associated with a first physical downlink shared channel (PDSCH) carrying first system information and a field associated with a second PDSCH carrying second system information. The methods or operations may further include receiving or transmitting the first PDSCH and the second PDSCH based on the DCI.

[0016] The above-mentioned problem-solving methods are merely some of the examples of this specification, and various examples reflecting the technical features of this specification can be derived and understood by a person with ordinary knowledge in the relevant technical field based on the detailed description below.

[0017] According to some implementations of the present specification, methods and devices for the efficient use of wireless resources in a spectrum where existing communication systems and new communication systems coexist may be provided.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0031] FIG. 12 is an example of a signal transmission / reception flow between a BS and a UE according to some implementations of the present specification;

[0032] FIG. 13 illustrates the DM-RS position for PDCCH;

[0033] FIG. 14 is another example of a signal transmission / reception flow between a BS and a UE according to some implementations of the present specification;

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

[0035] FIG. 16 illustrates the flow of downlink (DL) signal transmission in BS according to some implementations of the present specification.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0056] In a UE where CA is configured and DC is not configured, a Pcell PUCCH group (also referred to as a primary PUCCH group) consisting of a Pcell and zero or more Scells, and an Scell ​​PUCCH group (also referred to as a secondary PUCCH group) consisting only of Scell(s) may be configured. In the case of an Scell, an Scell ​​(hereinafter referred to as a PUCCH Scell) to which a PUCCH associated with that cell is transmitted may be configured. An Scell ​​designated as a PUCCH Scell ​​belongs to the Scell ​​PUCCH group (i.e., secondary PUCCH group), and the PUCCH transmission of the associated UCI is performed on the said PUCCH Scell; an Scell ​​that is not designated as a PUCCH Scell, or an Scell ​​in which the cell designated as a PUCCH transmission cell is a Pcell, belongs to the Pcell PUCCH group (i.e., primary PUCCH group), and the PUCCH transmission of the associated UCI is performed on the said Pcell. In the following, if the UE is configured with an SCG and some implementations of this specification related to PUCCH apply to the SCG, the primary cell may refer to the PSCell of the SCG. If the UE is configured with a PUCCH Scell ​​and some implementations of this specification related to PUCCH apply to a secondary PUCCH group, the primary cell may refer to the PUCCH Scell ​​of the secondary PUCCH group.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0084] Referring to Fig. 4, uplink and downlink transmissions in an NR system are organized into frames. Each frame is T f = (△f max *N f / 100)*T c = It has a duration of 10 ms and is divided into two half-frames, each with a duration of 5 ms. Here, T is the basic time unit for NR. c = 1 / (△fmax *N f ) and, △f max = 480*10 3 It is Hz, and N f = 4096. For reference, T is the standard time unit for LTE. s = 1 / (△f ref *N f,ref ) and, △f ref = 15*10 3 It is Hz, and N f,ref =2048. T c Wow T s is a constant κ = T s / T c It has a relationship of = 64. Each half-frame consists of 5 subframes, and the period T of a single subframe (SF) sf is 1ms. Subframes are further divided into slots, and the number of slots within a subframe depends on the subcarrier spacing. Each slot consists of 14 or 12 OFDM symbols based on a cyclic prefix. For a normal cyclic prefix (CP), each slot consists of 14 OFDM symbols, while for an extended CP, each slot consists of 12 OFDM symbols. The above numerology is an exponentially scalable subcarrier spacing △f = 2 u It depends on 15 kHz. The following table shows the subcarrier spacing △f = 2 for a normalized CP. u *Number of OFDM symbols per slot according to 15 kHz (N slot symb ), number of slots per frame (N frame,u slot ) and the number of slots per subframe (N subframe,u slot It represents ).

[0085]

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

[0087]

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

[0089] FIG. 5 illustrates a resource grid of a slot. A slot contains multiple (e.g., 14 or 12) symbols in the time domain. For each numerator (e.g., subcarrier interval) and carrier, a common resource block (CRB) N indicated by upper-layer signaling (e.g., radio resource control (RRC) signaling) start,u grid Starting from,N size,u grid,x *N RB sc individual subcarriers and N subframe,u symb A resource grid of N OFDM symbols is defined. Here, N size,u grid,x is the number of resource blocks (RB) in the resource grid, and the subscript x is DL for downlinks and UL for uplinks. RB sc is the number of subcarriers per RB, and in 3GPP-based wireless communication systems, N RB scis typically 12. There is one resource grid for a given antenna port p, subcarrier spacing configuration u, and transmission direction (DL or UL). Carrier bandwidth N for subcarrier spacing configuration u. size,u grid This is given to the UE by upper-layer parameters (e.g., RRC parameters) from the network. Each element within the resource grid for antenna port p and subcarrier spacing u is referred to as a resource element (RE), and one complex symbol can be mapped to each resource element. Each resource element within the resource grid is uniquely identified by an index k in the frequency domain and an index l indicating the symbol position relative to a reference point in the time domain. In an NR system, RBs are defined by 12 consecutive subcarriers in the frequency domain. In an NR system, RBs can be classified into Common Resource Blocks (CRBs) and Physical Resource Blocks (PRBs). CRBs are numbered upwards from 0 in the frequency domain for subcarrier spacing u. The center of subcarrier 0 of CRB 0 for subcarrier spacing u coincides with 'Point A', which is the common reference point for the resource block grids. The PRBs for the subcarrier spacing setting u are defined within the bandwidth part (BWP), and range from 0 to N size,u BWP,i Numbered up to -1, where i is the number of the above bandwidth part. Common resource block n u CRB and physical resource block n within bandwidth part i PRB The relationships between them are as follows: n u PRB = n u CRB +N start,u BWP,i , here N start,u BWP,iis a common resource block where the above bandwidth part starts relative to CRB 0. A BWP contains multiple consecutive RBs in the frequency domain. For example, a BWP is a given numerator u within a BWP i on a given carrier. i It is a subset of contiguous CRBs defined for. A UE may be configured to have one or more BWPs on a given component carrier. On the downlink, the UE may be configured with, for example, up to four BWPs, and only one DL BWP is active at any given time. The UE does not expect to receive PDSCH, PDCCH, or CSI-RS (except for radio resource management) outside of the active BWP. On the uplink, the UE may be configured with, for example, up to four BWPs, and only one UL BWP is active at any given time. The UE does not transmit PUSCH or PUCCH outside of the active BWP.

[0090] For each serving cell within a set of DL BWPs or UL BWPs, the network establishes at least an initial DL BWP and one initial UL BWP (if the serving cell is configured with an uplink) or two initial UL BWPs (if using a supplementary uplink). The network may also establish additional ULs and DL BWPs for the serving cell. For each DL BWP or UL BWP, the UE is provided with the following parameters for the serving cell: i) subcarrier spacing, ii) circular prefix, iii) N start BWP Assuming = 275, offset RB set and length L RB CRBN provided by the RRC parameter locationAndBandwidth, which indicates as the resource indicator value (RIV). start BWP =O carrier +RBstart and the number of contiguous RBs N size BWP =L RB , and O provided by the RRC parameter offsetToCarrier for the subcarrier spacing carrier ; Index within the set of the above DL BWPs or UL BWPs; set of BWP-common parameters and set of BWP-exclusive parameters.

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

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

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

[0094]

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

[0096] A UE that has been powered off and then turned back on or disconnected from a wireless communication system first performs an initial cell search process, such as searching for a suitable cell to camp on and synchronizing with said cell or the BS of said cell (S11). During the initial cell search process, the UE receives a synchronization signal block (SSB) (also called an SS / PBCH block) from the BS. The SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH). The UE synchronizes with the BS based on the PSS / SSS and obtains information such as the cell identifier (ID). For example, the UE can obtain DL synchronization by detecting the SSB. The UE can identify the structure of the SSB burst based on the detected SSB index and, accordingly, detect the symbol / slot / half-frame boundary. The frame / half-frame number to which the detected SSB belongs can be identified using system frame number (SFN) information and half-frame indication information. Specifically, in a 5G-based system, a UE can obtain 10-bit SFN information from a PBCH. Of the 10-bit SFN information, 6 bits are obtained from a master information block (MIB), and the remaining 4 bits are obtained from a transport block (TB) (also called a PBCH payload) carried by the PBCH. The UE can obtain 1-bit half-frame indication information.When the carrier frequency is 3 GHz or less, half-frame indication information can be implicitly signaled using DM-RS for PBCH (hereinafter, PBCH DM-RS). PBCH DM-RS indicates 3-bit information by using one of eight PBCH DMRS sequences. Therefore, the maximum number of SSBs L within an SSB burst. max In the case of = 4, of the 3 bits that can be indicated using the 8 PBCH DM-RS sequences, the SSB index is indicated, and the remaining 1 bit can be used for half-frame indication. The UE can obtain the SSB index based on the PBCH DM-RS sequences and the PBCH payload. SSB candidates are 0 to L in chronological order within the SSB burst (or half-frame). max - Indexed to 1. L max When = 8 or 64, the three least significant bits (LSBs) of the SSB index can be indicated using eight different PBCH DM-RS sequences. max When = 64, the three most significant bits (MSBs) of the SSB index are indicated via the PBCH. L max When = 2, the two LSBs of the SSB index can be indicated using four different PBCH DM-RS sequences. L max In the case where = 4, the remaining 1 bit of the 3 bits that can be indicated using 8 PBCH DM-RS sequences can be used to indicate the SSB index and for half-frame indication.

[0097] In addition, the UE can obtain in-cell broadcast information based on the PBCH. Meanwhile, during the initial cell search process, the UE can receive a downlink reference signal (DL RS) to check the downlink channel status.

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

[0099] Subsequently, the UE may perform a random access procedure to complete access to the BS (S13 to S16). For example, during the random access procedure, the UE may transmit a preamble through a physical random access channel (PRACH) (S13) and receive a random access response (RAR) for the preamble through a PDCCH and a corresponding PDSCH (S14). If the reception of the RAR for the UE fails, the UE may attempt to re-transmit the preamble. In the case of contention-based random access (CBRA), a contention resolution procedure (S16) may be performed, which includes transmitting a PUSCH based on the UL resource allocation included in the RAR (S15) and receiving a PDCCH and a corresponding PDSCH.

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

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

[0102] In 3GPP-based systems, each SSB is associated with each beam. For example, during a half-frame, different SSBs may be transmitted in different spatial directions (using different beams that span the cell's coverage area). The possible time positions of SSBs within a half-frame are determined by the subcarriers, and the periododicity of the half-frames in which the SSBs are transmitted is set by the network. Multiple SSBs may be transmitted within the carrier frequency span. Different indices of SSBs transmitted / detected on a single cell may correspond to different BS (wide) Tx beams. Multiple SSBs may be transmitted within the carrier frequency span. The physical (layer) cell identifiers (PCIs) of SSBs transmitted at different frequency locations do not need to be unique, and different SSBs in the frequency domain may have different PCIs. If the SSB is associated with remaining minimum system information (RMSI), the SSB is referred to as a cell-defining SSB (CD-SSB), and the PCell is always associated with the CD-SSB located on the synchronization raster (sync raster). If the SSB is not associated with the RMSI, the SSB is referred to as a non-cell defining SSB (NCD-SSB), which can be used to perform RLM, BFD, and RRM measurements, and measurements for random access resource selection within the active DL BWP if the active DL BWP does not include the CD-SSB.In 3GPP-based systems, multi-beam operation is based on beam switching / beam scanning, which transmits / receives signals while changing the beam direction over time. Beam sweeping refers to the transmission and reception point (TRP) (e.g., BS / cell) changing the beam (direction) of the radio signal over time. In this specification, beam and beam direction may be used interchangeably. SSBs may be transmitted periodically using beam sweeping. In this case, the SSB index is implicitly linked to the SSB beam. The SSB beam may change on an SSB (index) basis or on an SSB (index) group basis. In the latter case, the SSB beam remains the same within the SSB (index) group. For example, referring to Fig. 7, the transmission beam direction of an SSB may be repeated across multiple consecutive SSBs. A set of SSBs is transmitted within a 5 ms half-frame. A set of SSB transmissions within a 5 ms half-frame is called an SSB burst. L is the maximum number of SSB transmissions within an SSB burst. max has a value of 4, 8, or 64 depending on the frequency band to which the carrier belongs. For example, L is the maximum number of SSBs in an SSB burst. max It can be given as follows.

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

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

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

[0106] The actual number of transmitted SSBs can be configured, with a maximum number L maxIt can be smaller. If multi-beam transmission is not applied, the number of SSB beams is 1.

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

[0108] Maximum L within SSB burst max SSBs may be transmitted, and the number / locations of the SSBs actually transmitted may vary depending on the BS / cell. The number / locations of the SSBs actually transmitted are used for rate-matching and measurement, and information regarding the SSBs actually transmitted (e.g., RRC setting ssb-PositionsInBurst) may be indicated as follows.

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

[0110] - In relation to measurement: When in RRC_CONNECTED mode, the network (e.g., BS) can specify the set of SSBs to be measured within the measurement interval. The set of SSBs can be specified by frequency layer. If no specification is given for the set of SSBs, the default set of SSBs is used. The default set of SSBs includes all SSBs within the measurement interval. The set of SSBs is the full of RRC signaling (e.g., length L max It can be specified using a bitmap. If in RRC_IDLE mode, the default SSB set is used.

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

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

[0113] - The MIB is always transmitted over a BCH with a periododicity of 80 ms and repetitions created within 80 ms. The MIB contains information / parameters related to SIB1 reception and is transmitted via the SSB's PBCH. During initial cell selection, the UE assumes that half-frames containing the SSB(s) are repeated with a period of 20 ms. In a 5G system, the MIB contains the common control resource set (CORESET), the pdcch-ConfigSIB1 field used to determine the common search space and necessary PDCCH parameters, and k, which represents the frequency domain offset between the SSB and the overall resource block grid in units of the number of subcarriers. SSBIt may include the ssb-SubcarrierOffset field corresponding to, SIB1, Msg2 / Msg4 for initial connection, the subCarrierSpacingCommon field regarding the subcarrier spacing for paging and broadcast system information messages, and the dmrs-TypeA-Position field regarding the position of the (first) DM-RS for the downlink (e.g., PDSCH) and uplink (e.g., PUSCH). Based on the MIB, the UE can determine whether a control resource set (CORESET) (e.g., CORESET#0) exists for the Type0-PDSCH common search space. For example, k SSB <= 23 (for FR1) or k SSB If <= 11 (for FR2), the UE can determine that a CORESET exists for the Type0-PDCCH common search space. If, k SSB > 23 (for FR1) or k SSB If > 11 (for FR2), the UE may determine that there is no CORESET for the Type0-PDCCH common seek space. The Type0-PDCCH common seek space is a type of PDCCH seek space used to transmit PDCCHs that schedule SI messages. If a Type0-PDCCH common seek space exists, the UE can determine (i) multiple consecutive RBs and one or more consecutive symbol(s) that constitute the 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 the frequency locations where SSB / SIB1 exists and the frequency ranges where SSB / SIB1 does not exist.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0153] -monitoringSymbolsWithinSlot: Represents the first OFDMA symbol(s) for PDCCH monitoring within the slot where PDCCH monitoring is enabled. It is indicated by a bitmap, where each bit corresponds to each OFDMA symbol within the slot. The MSB of the bitmap corresponds to the first OFDMA symbol within the slot. The OFDMA symbol(s) corresponding to bit(s) with a bit value of 1 correspond to the first symbol(s) of the CORESET within the slot.

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

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

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

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

[0158] In order for a UE to initially connect to a network through a cell, it must acquire the SIB1 of said cell. In 3GPP-based systems, the SIB1 is provided via a PDSCH. In 5G systems, the PDCCH (hereinafter referred to as SIB1 PDCCH) that schedules the PDSCH carrying the SIB1 (hereinafter referred to as SIB1 PDSCH) is provided via a set of Type0-PDCCH common search spaces (CSS). Referring to Section 13 of 3GPP TS 38.213, in 5G systems, a UE can monitor the Type0-PDCCH CSS set through the following process. If, during cell search, the UE determines from the MIB that a CORESET exists for a Type-0 PDCCH CSS set, the UE determines the number of consecutive resource blocks and the number of consecutive symbols for the CORESET for the Type-0 PDCCH CSS set from controlResourceSetZero in pdcch-ConfigSIB1, as described in Tables 13-0 through 13-10 of 3GPP TS 38.213 for operations without shared spectrum channel access in FR1, FR2-1, and FR2-NTN, as described in Tables 13-1A and 13-4A of 3GPP TS 38.213 for operations with shared spectrum channel access in FR1, or as described in Table 13-10A of 3GPP TS 38.213 for FR2-2, and 3GPP TS As described in Tables 13-11 through 13-15A of 38.213, determine the PDCCH monitoring times from searchSpaceZero within pdcch-ConfigSIB1 contained in the MIB. SFN c and n cis the system frame number (SFN) and slot index within the frame of the above CORESET based on the subcarrier spacing (SCS) of the above CORESET, and SFN SSB,i and n SSB,i are respectively the SFN and slot index based on the SCS of the above CORESET, where the SS / PBCH block at index i is the system frame SFN SSB,i and slot n SSB,i Overlap with time. The symbol of CORESET associated with pdcch-ConfigSIB1 in MIB or searchSpaceSIB1 in PDCCH-ConfigCommon has a normal cyclic prefix. In Table 13-0, the settings for indices 0 through 9 apply when the associated SS / PBCH block is located according to Table 5.4.3.3-2 of 3GPP TS 38.101-1, the settings for indices 10 through 11 apply when the associated SS / PBCH block is located according to NOTE 12 in Table 5.4.3.3-1 of 3GPP TS 38.101-1, and for the settings for indices 6 through 9, non-interleaved CCE-to-REG mapping applies. In Table 13-1, the associated SS / PBCH block is not located according to NOTE 12 in Table 5.4.3.3-1 of 3GPP TS 38.101-1.

[0159] For operations with and without shared spectrum channel access in FR2-2, the UE assumes that the offsets in Tables 13-0 through 13-10A of 3GPP TS 38.213 are defined relative to the SCS of the CORESET for the Type0-PDCCH CSS set, which is the offset from the index of the smallest resource block (RB) of the CORESET for the Type0-PDCCH CSS set to the index of the smallest RB of the common RB that overlaps with the first RB of the corresponding SS / PBCH block (after puncturing if any). The SCS of the CORESET for the Type0-PDCCH CSS set is provided by subCarrierSpacingCommon for FR1, FR2-1, and FR2-NTN, and is identical to the SCS of the corresponding SS / PBCH block for FR2-2. In Tables 13-7, 13-8, and 13-10, k SSB is defined in 3GPP TS 38.211. Referring to 3GPP TS 38.211, the quantity k SSB is common resource block N SSB CRB The subcarrier offset from my subcarrier 0 to the lowest-numbered subcarrier of the SS / PBCH block, or if applicable, the SS / PBCH block after puncturing, where N SSB CRB is obtained from the upper-level parameter offsetToPointA, which represents the offset to point A, and offsetToPointA can be provided through SIB1.

[0160] For operations with shared spectrum channel access in FR1, the UE has an offset from the smallest RB index of the CORESET for the Type0-PDCCH CSS set to the smallest RB index of the common RB that overlaps with the first RB of the corresponding SS / PBCH block.

[0161] If the frequency position of the SS / PBCH block corresponds to the global synchronization channel number (GSCN) of the synchronization raster entry defined in 3GPP TS 38.101-1, it is determined according to the offset in Table 13-1A or Table 13-4A of 3GPP TS 38.213, and

[0162] If the frequency location of the SS / PBCH block is provided by the ssbFrequency within the measurement configuration associated with the reporting configuration providing reportCGI and does not correspond to the GSCN of the synchronization raster entry defined in 3GPP TS 38.101-1, it is determined by the sum of the first offset and the second offset, where the first offset is provided in Table 13-1A or Table 13-4A of 3GPP TS 38.213, and the second offset is determined as the offset from the smallest RB index of the common RB overlapping with the first RB of the SS / PBCH block indicated in the measurement configuration to the smallest RB index of the common RB overlapping with the first RB of the SS / PBCH block hypothetically located in the GSCN of the synchronization raster entry, wherein the single synchronization raster entry is the SS / PBCH used in the shared spectrum channel access process as described in 3GPP TS 37.213 Located in the same channel as the block,

[0163] Here, the above offsets are defined based on the SCS of the CORESET for the Type0-PDCCH CSS set, which is identical to the SCS of the corresponding SS / PBCH block.

[0164] For operation without shared spectrum channel access and for SS / PBCH blocks and CORESET multiplexing pattern 1, the UE monitors the PDCCH in the Type0-PDCCH CSS set across two slots. For the SS / PBCH block at index i, the UE sets the index of slot n0 as n0 = {O*2 u + floor(i*M)} mod N frame,u slot It is determined as floor{(O*2 u + floor(i*M)) / N frame,u slot SFN when mod 2 = 0 c System frame number (SFN) satisfying mod 2 = 0 c In a frame that has, or floor{(O*2 u + floor(i*M)) / N frame,u slot SFN when} mod 2 = 1 cA frame containing an SFN satisfying mod 2 = 1, where u ∈ {0,1,2,3,5,6} is based on an SCS for PDCCH receptions within a CORESET. For u ∈ {0,1,2,3} and SS / PBCH block index i, the two slots containing the associated Type0-PDCCH monitoring times are slots n0 and n0+1, and the indices of M, O, and the first symbol of the CORESET in slots n0 and n0+1 are provided by Tables 13-11 and 13-12 of 3GPP TS 38.213. For u ∈ {5} and SS / PBCH block index i, the two slots containing the associated Type0-PDCCH monitoring periods are slots n0 and n0+4, and the indices of M, O, and the first symbol of the CORESET in slots n0 and n0+4 are provided by Table 13-12A of 3GPP TS 38.213, where X = 1.25. For u ∈ {6} and SS / PBCH block index i, the two slots containing the associated Type0-PDCCH monitoring periods are slots n0 and n0+8, and the indices of M, O, and the first symbol of the CORESET in slots n0 and n0+8 are provided by Table 13-12A of 3GPP TS 38.213, where X = 0.625.

[0165] For operations with shared spectrum channel access and for SS / PBCH block and CORESET multiplexing pattern 1, the UE monitors PDCCH on slots including Type0-PDCCH monitoring times associated with SS / PBCH blocks and pseudo-co-located SS / PBCH blocks that provide a CORESET for a Type0-PDCCH CSS set with respect to average gain, quasi-co-location 'typeA', and 'typeD' characteristics where applicable. For candidate SS / PBCH block index i', where 0 ≤ i' ≤ L' max - 1, two slots include the aforementioned associated Type0-PDCCH monitoring times. The UE has the index of slot n0 as n0= {O*2 u + floor(i'*M)} mod N frame,u slot It is determined as floor{(O*2 u + floor(i'*M)) / N frame,u slot SFN when mod 2 = 0 c System frame number (SFN) satisfying mod 2 = 0 c In a frame that has, or floor{(O*2 u + floor(i'*M)) / N frame,u slot SFN when} mod 2 = 1 cIt is within a frame having an SFN satisfying mod 2 = 1, where u ∈ {0,1,2,3,5,6} is based on the SCS for PDCCH receptions within the CORESET. For u ∈ {0,1} and SS / PBCH block index i', the two slots containing the associated Type0-PDCCH monitoring times are slots n0 and n0+1, and the indices of M, O in slots n0 and n0+1, and the first symbol of the CORESET are provided by Table 13-11 of 3GPP TS 38.213, and the UE is N QCL SSB When = 1, it is not expected that M = 1 / 2 or M = 2. For u ∈ {3} and SS / PBCH block index i', the two slots containing the associated Type0-PDCCH monitoring periods are slots n0 and n0+1, and the indices of M, O, and the first symbol of the CORESET in slots n0 and n0+1 are provided by Table 13-12 of 3GPP TS 38.213. For u ∈ {5} and SS / PBCH block index i', the two slots containing the associated Type0-PDCCH monitoring periods are slots n0 and n0+4, and the indices of M, O, and the first symbol of the CORESET in slots n0 and n0+4 are provided by Table 13-12 of 3GPP TS 38.213, where X = 1.25. For u ∈ {6} and SS / PBCH block index i', the two slots containing the associated Type0-PDCCH monitoring times are slots n0 and n0+8, and the indices of M, O, and the first symbol of the CORESET in slots n0 and n0+8 are provided by Table 13-12A of 3GPP TS 38.213, where X = 0.625.

[0166] For operation without shared spectrum channel access, and for the SS / PBCH block and CORESET multiplexing patterns 2 and 3, the UE monitors the PDCCH within the Type0-PDCCH CSS set on a single slot having a Type0-PDCCH CSS set periodocity equal to the periodocity of the SS / PBCH block. For the SS / PBCH block at index i, the UE [monitors] slot index n based on the parameters provided by Tables 13-13 through 13-15A. c and SFN c Determines.

[0167] For operations with shared spectrum channel access and for SS / PBCH blocks and CORESET multiplexing pattern 3, the UE monitors the PDCCH within the Type0-PDCCH CSS set on slots including Type0-PDCCH monitoring times associated with SS / PBCH blocks and pseudo-co-located SS / PBCH blocks that provide a CORESET for the Type0-PDCCH CSS set with respect to average gain, pseudo-co-located 'typeA' and 'typeD' characteristics, where applicable. For a candidate SS / PBCH block index i', where 0 ≤ i' ≤ L' max - 1, the period of the slot including the aforementioned associated Type0-PDCCH monitoring periods is equal to the period of the aforementioned candidate SS / PBCH block, and the UE is based on the slot index n based on the parameters provided by Tables 13-15 and 13-15A. c and SFN c It determines, where i is replaced by i' for operations with shared spectrum channel access in FR2-2.

[0168] For SS / PBCH blocks and CORESET multiplexing patterns 2 and 3, when the active DL BWP is the initial DL BWP, the UE is expected to be able to perform wireless link monitoring and wireless resource management measurements using the SS / PBCH block that provides the CORESET for the Type0-PDCCH CSS set.

[0169] The following table is Table 13-1 of 3GPP TS 38.213, regarding the set of resource blocks and slot symbols of CORESET for the Type0-PDCCH common search space (CSS) set when the SCS of {SS / PBCH block, PDCCH} is {15, 15} kHz for frequency bands with a minimum channel bandwidth of 5 MHz or 10 MHz, or a minimum channel bandwidth of 3 MHz and a channel bandwidth greater than 3 MHz.

[0170]

[0171] Table 13-0 and Tables 13-2 through 13-10 of the previously mentioned 3GPP TS 38.213 are omitted in this specification as reference can be made to 3GPP 38.213.

[0172] The following table is Table 13-11 of 3GPP TS 38.213 regarding parameters for PDCCH monitoring times for Type 0-PDCCH CSS sets related to SS / PBCH blocks and CORESET multiplexing patterns 1 and FR1.

[0173]

[0174] Tables 13-12 and Table 15 of the previously mentioned 3GPP TS 38.213 are omitted in this specification as reference can be made to 3GPP 38.213.

[0175] If the UE detects the first SS / PBCH block and determines that a CORESET for the Type0-PDCCH CSS set does not exist, and for FR1, 24 ≤ k SSB≤ 29 or for FR2, 12 ≤ k SSB If ≤ 13, the UE [identifies] the nearest GSCN (in the corresponding frequency direction) of the second SS / PBCH block having a CORESET for the associated Type0-PDCCH CSS set as N Reference GSCN + N Size GSCN *N Offset GSCN It can be determined as. Here, N Reference GSCN is the GSCN of the first SS / PBCH block, and N in FR1, FR2-1, and FR2-NTN Size GSCN = 1, N in FR2-2 Size GSCN = 3, and N Offset GSCN is the GSCN offset provided by Table 13-16 of 3GPP TS 38.213 for FR1 and Table 13-17 of 3GPP TS 38.213 for FR2. If the UE detects the second SS / PBCH block and the second SS / PBCH block does not provide a CORESET for the Type0-PDCCH CSS set, the UE may ignore the GSCN and related information of the SS / PBCH block locations for performing cell search.

[0176] If the UE detects an SS / PBCH block and determines that a CORESET for the Type0-PDCCH CSS set does not exist, and for FR1 k SSB = 31 or k for FR2 SSB If = 15, the above UE is in the GSCN range [N Reference GSCN - N Start GSCN , N Reference GSCN + N End GSCNDetermines that there are no SS / PBCH blocks with an associated Type0-PDCCH CSS set within ]. N Start GSCN and N End GSCN is determined respectively by controlResourceSetZero and searchSpaceZero within pdcch-ConfigSIB1. The above GSCN range is [N Reference GSCN , N Reference GSCN In the case where ], the UE determines that there is no information about a second SS / PBCH block having a CORESET for a Type0-PDCCH CSS set associated with the detected SS / PBCH block.

[0177] If the UE does not detect any SS / PBCH block providing a CORESET for a Type0-PDCCH CSS set within a time period determined by the UE, the UE may ignore information related to the GSCN of the SS / PBCH locations when performing cell search.

[0178] The following table shows k for FR1 SSB The combination of controlResourceSetZero and searchSpaceZero within pdcch-ConfigSIB1 and N Offset GSCN Mapping between the combination of k SSB andcontrolResourceSetZeroandsearchSpaceZeroinpdcch-ConfigSIB1to N Offset GSCN Table 13-16 of 3GPP TS 38.213 regarding for FR1).

[0179]

[0180] As described above, during the initial connection process, the UE receives configuration information for the CORESET (or COREEST#0) and CSS set (or SS set#0) from the MIB, which is the PBCH payload. Based on this information, the UE performs PDCCH monitoring to receive the DCI (or SIB1 PDCCH) that schedules the PDSCH carrying System Information Block (SIB) information. For example, referring to Table 4, the multiplexing pattern between the SSB and CORESET (distinguishing whether it is TDM or FDM, and whether the SCS of the SSB and the SCS of the CORESET are identical), the number of RBs constituting the CORESET, the number of symbols constituting the CORESET, and Common Resource Block (CRB) 0 (where subcarrier 0 of CRB 0 is k from the lowest subcarrier of the SSB). SSB It is determined by the value of k SSBCORESET-related configuration information, such as an RB-level offset (e.g., the location of the starting frequency resource of CORESET) from the value signaled via PBCH, is signaled from the PBCH payload (e.g., controlResourceSetZero in pdcch-ConfigSIB1, where pdcch-ConfigSIB1 is a total of 8-bit information and controlResourceSetZero is 4-bit information). In addition, as exemplified in Table 5, information about the Type-0 PDCCH CSS set, such as the time axis offset from the frame boundary (e.g., the value of O in Table 5), the number of CORESETs per slot and the first symbol index, and the spacing between CORESETs (e.g., the value of M in Table 5, where M = 2 means one CORESET is located every two slots), is signaled from the PBCH payload (e.g., searchSpaceZero in pdcch-ConfigSIB1, where pdcch-ConfigSIB1 is a total of 8-bit information and searchSpaceZero is 4-bit information).

[0181] Typically, a specific spectrum is utilized exclusively for a specific radio access technology (RAT) (e.g., LTE spectrum, 5G spectrum, etc.). The non-access stratum (NAS) layer of a UE, which has been powered off and then turned back on or disconnected from the wireless communication system, selects a public land mobile network (PLMN) (or standalone non-public network (SNPN)) to access the network and transmits information regarding the selected PLMN (or SNPN) and its associated RAT (e.g., NR, LTE, etc.) to the access stratum (AS) layer to control which RAT is used for initial search during cell discovery. The AS layer of the UE scans specific frequency bands (e.g., all radio frequency (RF) channels in the NR band) suitable for the corresponding RAT according to its supported capabilities. The UE detects synchronization signals and broadcast channels suitable for the specific RAT and performs synchronization. A UE that has successfully synchronized with a cell can receive broadcast system information (e.g., SIB) transmitted by the cell, and the broadcast system information includes one or more PLMN identifiers or SNPN identifiers. The AS layer of the UE aggregates the list of PLMNs (or SNPNs) received via the broadcast channel and the RAT information associated with the corresponding network and reports it to the upper layer, the NAS. If the BS is shared by multiple operators, the cell broadcasts a list of core network operators that the UE(s) can select via the broadcast system information, and the UE decodes this system information to identify available network operators and RAT environments and utilizes a network selection procedure.A UE attempts to receive SIB1 limited to the RAT associated with the network it is attempting to connect to. As previously described, a UE attempting to connect to a cell according to 5G obtains a setting regarding CORESET#0 / SS Set#0 from the MIB, receives a SIB1 PDCCH from SS Set#0 on CORESET#0 based on the setting, and can receive a PDSCH carrying SIB1 based on the DCI carried by the SIB1 PDCCH.

[0182] As spectrum candidates for 6G communication, methods are being discussed to either refarm spectrum used by 5G systems or to utilize new spectrum not currently used by existing cellular networks. Considering that spectrum used by existing 5G systems offers benefits in terms of coverage, methods for 5G and 6G systems to coexist within that spectrum (particularly from a BS perspective) are receiving attention. This spectrum sharing method is referred to as multi-RAT spectrum sharing (MR-SS). In the following MR-SS environment, ensuring that UEs can stably receive SIB1 PDCCH and SIB1 PDSCH while minimizing interference between different RAT systems is critical to system performance. The following provides several implementations of this specification that enable the BS to stably provide SIB1 PDCCH and / or SIB1 PDSCH to UEs operating with different RATs in an MR-SS environment.

[0183] <1. PDCCH Configuration for Initial Connection Based on New RAT>

[0184] In order to maximize spectral efficiency, if a BS relocates legacy RAT spectrum (e.g., 5G spectrum) to simultaneously service legacy UEs (e.g., 5G UEs) and UEs connected to a new RAT (e.g., 6G UEs), it may be more efficient for the BS to use CORESET#0 / SS Set#0 for the new RAT UEs rather than using it only for legacy RAT UEs. For example, if there are few 5G UEs and many 6G UEs among UEs connected to or attempting to connect to a band that supports both 5G and 6G, and the BS utilizes 5G CORESET#0 / SS Set#0 for 6G SIB1 scheduling for 6G UEs as well, more UEs can be serviced in that band compared to configuring 5G CORESET#0 / SS Set#0 and 6G CORESET#0 / SS Set#0 separately.

[0185] As such, some implementations of this specification are described in which, in an MR-SS situation, for example, a situation where the BS services 5G UEs and 6G UEs simultaneously by reallocating 5G spectrum, the BS transmits SIB1 PDCCH, etc. to 5G UEs and 6G UEs by utilizing common CORESET#0 / SS Set#0 resources. In some implementations of this specification described below, when the BS services only 6G UEs, it may perform more efficient SIB1 PDCCH transmission by establishing a new 6G CORESET#0 / SS Set#0 that is more efficient than the existing 5G CORESET#0 / SS Set#0. Meanwhile, depending on the BS implementation, resources separate from the CORESET#0 / SS Set#0 for 5G UEs can be utilized by configuring the newly introduced 6G CORESET#0 / SS Set#0 for 6G UEs even in MR-SS situations, or the existing 5G BS implementation can be maintained by configuring the existing 5G CORESET#0 / SS Set#0 even if only 6G UEs are serviced. Below, some implementations of this specification related to a method for the BS to efficiently signal either the 5G CORESET#0 / SS Set#0 configuration or the 6G CORESET#0 / SS Set#0 configuration, and the UE's SIB1 PDCCH reception operation through said signaling are also described.

[0186] For convenience of explanation, some implementations of this specification are described using 5G and 6G respectively as examples of legacy RATs and new RATs, but some implementations of this specification may be applied between all different RATs and are not limited to 5G and 6G.

[0187] For convenience of explanation in this specification, CORESET#0 / SS Set#0 for 6G is referred to as 6G CORESET#0 / SS Set#0, and CORESET#0 / SS Set#0 for 5G is referred to as 5G CORESET#0 / SS Set#0.

[0188] In this specification, 6G CORESET#0 / SS Set#0 may be configured 1) through parameters (or a set of such parameters) separate from the parameters for configuring the existing 5G CORESET#0 / SS Set#0, or 2) in the form of applying offset values ​​from all or part of the parameters for configuring the existing 5G CORESET#0 / SS Set#0 (or in the form of a time / frequency domain replica). In the case of 1), for example, parameter(s) separate from the parameters related to the number of RBs and / or symbols for configuring the 5G CORESET#0 may be introduced for configuring the 6G CORESET#0. On the other hand, in case 2), for example, if there is an entry for configuring 5G CORESET#0 consisting of 24 physical resource blocks (PRBs) and 2 symbols, the entry for configuring 6G CORESET#0 associated with that entry can be configured as CORESET#0 by applying one of the following methods.

[0189] Opt A: 5G CORESET#0 is expanded to 6G CORESET#0 with 48 PRBs and 3 symbols by additionally signaling 24 PRBs and 1 symbol.

[0190] Opt B: By signaling a -2-symbol offset, 6G CORESET#0 or a replica of CORESET#0 consisting of 24 PRBs and 2 symbols is positioned at a location 2-symbol shifted (relative to 5G CORESET#0).

[0191] Opt C: With a 2-symbol offset and an additional 1 symbol signaled, 6G CORESET#0, consisting of 24 PRBs and 1 symbol, is located at the 2-symbol transition (relative to 5G CORESET#0).

[0192] To generalize further, if a specific "existing 5G CORESET#0 related entry" is configured with X PRBs, Y symbols, and other parameter values ​​= Z, in some implementations, the associated 6G CORESET#0 related entry may be configured as an additional CORESET (e.g., a replica of the 5G CORESET#0) consisting of X' PRBs and Y' symbols to be respectively added to the X PRBs and Y symbols provided by the 5G CORESET#0 related entry, and other parameters = Z'. Or, if a specific "existing 5G SS Set #0 related entry" is set to A slot offset, B symbol offset, and other parameter value = C, the associated 6G SS Set #0 related entry may be in the form of slot offset A' and symbol offset B' to be added respectively to slot offset A and symbol offset B provided by the 5G SS Set #0 related entry, and other parameter value = C'. In this case, when a UE receives a specific CORESET related entry and a specific SS Set #0 related entry, the UE can see that 6G CORESET #0 is set by (X + X') PRBs, (Y + Y') symbols, and other parameter = Z', and 6G SS Set #0 is set by (A + A') slot offsets, (B+B') symbol offset, and other parameter value = C'.

[0193] Or, if a specific "existing 5G CORESET#0 related entry" is set to X PRBs, Y symbols, and other parameter value = Z, in some implementations of this specification, the associated 6G CORESET#0 related entry may be linked to (X + X') PRBs, (Y + Y') symbols, and other parameter = Z'. If a specific "existing 5G SSSET#0 related entry" is set to A slot offset, B symbol offset, and other parameter value = C, the associated 6G SSSET#0 related entry may be linked to (A + A') slot offset, (B + B') symbol offset, and other parameter value = C'. In this case, the UE receives a specific CORESET related entry and a specific SS set #0 related entry, and the UE can see that 6G CORESET #0 is set by (X + X') PRBs, (Y + Y') symbols, and other parameters = Z', and 6G SS set #0 is set by (A + A') slot offsets, (B+B')-symbol offsets, and other parameter values ​​= C'.

[0194] <Method #1-1> Method to inform the UE whether the CORESET#0 / SS Set#0 related settings are the existing 5G CORESET#0 / SS Set#0 settings or 6G CORESET#0 / SS Set#0 settings using a separate indicator

[0195] BS can use a separate 1-bit indicator / flag within the PBCH payload to signal whether the corresponding CORESET#0 / SS Set#0 configuration is an existing 5G CORESET#0 / SS Set#0 configuration or a 6G CORESET#0 / SS Set#0 configuration. Additionally, within the PBCH payload, N1 bits (e.g., N1=4) can be used for CORESET#0 resource configuration, and N2 bits (e.g., N2=4) can be used for SS Set#0 resource configuration.

[0196] If the bit is '0' (or '1'), the UE recognizes that CORESET#0 is set through the N1 bits (or some 4 bits of N1) in the same manner as described above with reference to Section 13 of 3GPP TS 38.213, and if the bit is '1' (or '0'), the UE recognizes that 6G CORESET#0 is set through the N1 bits (or some 4 bits of N1). Additionally, based on the fact that the bit is '0' (or '1'), if the UE recognizes that CORESET#0 is set through the N1 bits (or some 4 bits of N1) in the same manner as described above with reference to Section 13 of 3GPP TS 38.213, the UE can know that the cell is a cell where MR-SS is operating. In addition, if the bit is '1' (or '0') and the UE recognizes that 6G CORESET#0 is configured through the N1 bits (or some 4 bits of N1), it can be known that the cell is a 6G-only cell and that MR-SS is not in operation. For example, if a specific bit in the MIB of a 6G-supported cell that the UE has camped on is set to 0, it can determine 5G CORESET#0 / SS Set#0 based on the PDCCH-ConfigSIB field in the said MIB and recognize that the cell supports MR-SS, and if it is set to 1, it can determine 6G CORESET#0 / SS Set#0 based on the PDCCH-ConfigSIB field in the said MIB and recognize that the cell is a 6G-only cell.

[0197] If the bit is '0' (or '1'), the UE recognizes that SS Set #0 is set through the N2 bits (or some 4 bits of N2) in the same manner as described above with reference to Section 13 of 3GPP TS 38.213, and if the bit is '1' (or '0'), the UE recognizes that 6G SS Set #0 is set through the N2 bits (or some 4 bits of N2). Additionally, if the UE recognizes that SS Set #0 is set through the N2 bits (or some 4 bits of N2) in the same manner as described above with reference to Section 13 of 3GPP TS 38.213 because the bit is '0' (or '1'), the UE can know that the cell is a cell in which MR-SS is operating. In addition, if the UE recognizes that 6G SS set #0 is set through the N2 bits (or some 4 bits of N2) because the bit is '1' (or '0'), it can know that the cell is not operating MR-SS and is a 6G only cell.

[0198] The indicator / flag bits for CORESET#0 and SSSET#0 may be a common 1 bit on the PBCH payload or separate 1 bits. For example, a 1 bit in the MIB may be used as the indicator / flag bit for CORESET#0 and SSSET#0, or a 1-bit indicator / flag for CORESET#0 and a 1-bit indicator / flag for SSSET#0 may be set separately within the MIB. Additionally, the indicator / flag bits (or some thereof) may be utilized in a specific sequence (e.g., PSS, SSS, or DM-RS for PBCH (hereinafter PBCH DM-RS)) or a synchronization raster, rather than in the PBCH payload. For example, when PBCH DM-RS sequence set 1 and PBCH DM-RS sequence set 2 are defined in a standard document, if a PBCH DM-RS belonging to sequence set 1 is detected, the UE recognizes that the indicator / flag bit is signaled as '0', and if a PBCH DM-RS belonging to sequence set 2 is detected, the UE recognizes that the indicator / flag bit is signaled as '1'.

[0199] <Method #1-2> Set some entries in the CORESET#0 / SS Set#0 configuration table(s) to 5G CORESET#0 / SS Set#0 and the remaining entries to 6G CORESET#0 / SS Set#0

[0200] As previously described with reference to Section 13 of 3GPP TS 38.213, N3 code-point / entry / index values ​​(where N3 can be 16 or less) may be used for 5G CORESET#0 configuration. When CORESET#0 is configured via 6G PBCH using N4 code-point / entry / index values, each of the N5 code-point / entry / index values ​​is defined by a configuration identical to the CORESET#0 configuration corresponding to one of the N3 code-point / entry / index values ​​defined for 5G CORESET#0 configuration, and the remaining (N4-N5) code-point / entry / index values ​​may be configured by 6G CORESET#0 configurations (different from 5G CORESET#0 configurations). For example, in the case where N5 = 8, in a table containing a total of 16 (i.e., N4 = 16) code-points / entries / indexes for CORESET#0 configuration via 6G PBCH, indices 0 through 7 are configured to be identical to indices 0 through 7 in 13-1 of 3GPP TS 38.213 (see Table 4), and indices 8 through 15 can be configured to be 6G CORESET#0 configurations. In this example, if the UE is instructed to index 0 by the PBCH, it can recognize that CORESET#0 is configured to be identical to a specific 5G CORESET#0 configuration defined in the 5G standard document, and if it is instructed to index 8 by the PBCH, it can recognize that CORESET#0 is configured to be a newly defined 6G CORESET#0 configuration in the 6G standard document.In addition, if the UE is instructed by the PBCH to index 0 (e.g., one of the N3 code-point / entry / index values ​​defined for 5G CORESET#0 configuration), it can be known that the cell is a cell where MR-SS is operating, or if the UE is instructed by the PBCH to index 8 (e.g., one of the (N4-N5) code-point / entry / index values ​​defined for 6G CORESET#0 configuration), it can be known that the cell is a 6G-only cell where MR-SS is not operating.

[0201] In this case, if the N4 value is 16 or less, in some implementations, there is an advantage that using only up to 4 bits for CORESET#0 allows for the use of a payload of the same size as that used to set CORESET#0 in a 5G PBCH. However, in this case, there is a disadvantage that not all of the N3 code-point / entry / index values ​​used in the existing 5G CORESET#0 are utilized. Considering this, using a value greater than 16 for N4 may be considered, and all (or some) of the N3 values ​​may be included in the N5 code-point / entry / index values. When the BS signals the Ceiling(log2(N4)) bits, the entire Ceiling(log2(N4)) bit may be carried in the PBCH payload, or some or all of them may be signaled through a specific sequence (e.g., PSS, SSS, PBCH DM-RS) or a synchronization raster.

[0202] As previously described with reference to Section 13 of 3GPP TS 38.213, N3' code-point / entry / index values ​​(where N3' can be 16 or less) may be used for 5G SS Set #0 configuration. When SS Set #0 is configured via 6G PBCH using N4' code-point / entry / index values, each of the N5' code-point / entry / index values ​​is defined by the same configuration as the SS Set #0 configuration corresponding to one of the N3' code-point / entry / index values ​​defined for 5G SS Set #0 configuration, and the remaining (N4'-N5') code-point / entry / index values ​​may be configured as 6G SS Set #0 configurations (different from the 5G SS Set #0 configuration). For example, when N5' = 8, in a table containing a total of 16 (i.e., N4' = 16) code-points / entries / indexes for SS Set #0 configuration via 6G PBCH, indices 0 through 7 are configured identically to indices 0 through 7 in Table 13-11 of 3GPP TS 38.213 (see Table 5), and indices 8 through 15 can be configured as 6G SS Set #0 configurations. In this example, if the UE is instructed by the PBCH to index 0, it can recognize that SS Set #0 is configured identically to a specific 5G SS Set #0 configuration defined in the 5G standard document, and if it is instructed by the PBCH to index 8, it can recognize that SS Set #0 is configured through a newly defined 6G SS Set #0 configuration in the 6G standard document.In addition, if the UE is instructed by the PBCH to index 0 (e.g., one of the N3' code-point / entry / index values ​​defined for 5G SS set #0 configuration), it can be known that the cell is a cell in which MR-SS is operating, or if the UE is instructed by the PBCH to index 8 (e.g., one of the (N4'-N5') code-point / entry / index values ​​defined for 6G SS set #0 configuration), it can be known that the cell is a 6G-only cell in which MR-SS is not operating.

[0203] In this case, if the N4' value is 16 or less, in some implementations, using only up to 4 bits for SS Set #0 has the advantage of allowing only a payload of the same size as that used to set SS Set #0 in 5G PBCH to be used for SS Set #0. However, in this case, there is a disadvantage that the N3' code-point / entry / index values ​​used in the existing 5G SS Set #0 cannot all be utilized. Considering this, using a value greater than 16 as the N4' value may be considered, and all (or some) of the N3' values ​​may be included in the N5' code-point / entry / index values. When the BS signals the Ceiling(log2(N4')) bits, the entire Ceiling(log2(N4')) bit may be carried in the PBCH payload, or some or all of them may be signaled through a specific sequence (e.g., PSS, SSS, PBCH DM-RS) or a synchronization raster.

[0204] Different methods may be applied to CORESET#0 and SSSET#0, respectively. For example, Method#1-1 (or Method#1-2) may be applied for CORESET#0, and Method#1-2 (or Method#1-1) may be applied for SSSET#0.

[0205] The CORESET#0 / SS Set#0 configuration information described in the aforementioned Methods #1-1 and #1-2 may be transmitted via Opt 1) 5G SSB or Opt 2) 6G SSB. In the case of Opt 1), considering coexistence with legacy 5G NR UEs, the existing 4 bits for CORESET#0 / SS Set#0 configuration are retained; however, if additional bits are required, the above methods may be applied by utilizing bit(s) not used by legacy 5G NR UEs, such as reserved bits (or bits used for SSB indices in FR2 that are not used in FR1). The maximum number L of SSB indices for FR2 in the current NR max is 64, the maximum number of SSB indexes for FR1 L max Since there are 8, 6 bits are required for SSB index indication in FR2 and 3 bits are required in FR1. The 3 bits for the SSB index are transmitted via PBCH DM-RS. Therefore, in the PBCH payload for FR2, the additional 3 bits within the PBCH payload are used to indicate the SSB index, and in the PBCH payload for FR1, there are no bits used to indicate the SSB index. Since 1 bit of the 3 bits in the PBCH payload for FR1 is used for another purpose, consequently, there are 2 remaining bits in the PBCH payload for FR1. In the case of Opt 1), considering coexistence with legacy 5G NR UEs, the existing 4 bits for CORESET#0 / SS Set#0 configuration are maintained, and if additional bits are needed, the above methods can be applied by utilizing the remaining bit(s) that are not used for FR1 among the 3 bits used for the SSB index for FR2 of the PBCH payload.

[0206] FIG. 12 is an example of a signal transmission / reception flow between a BS and a UE according to some implementations of the present specification. Referring to FIG. 12, the BS can set one of a first RAT-based CORESET#0 / SS Set#0 related setting (e.g., 5G CORESET#0 / SS Set#0 setting) or a second RAT-based CORESET#0 / SS Set#0 related setting (e.g., 6G CORESET#0 / SS Set#0 setting) through a 1-bit indicator / flag in the PBCH (S1201). The BS can perform SIB1 PDCCH transmission based on the 5G CORESET#0 / SS Set#0 setting and / or SIB1 PDCCH transmission based on the 6G CORESET#0 / SS Set#0 setting. A UE that receives a setting related to CORESET#0 / SS Set#0 can recognize that it is 5G CORESET#0 / SS Set#0 if the indicator / flag value is '0', and recognize that it is 6G CORESET#0 / SS Set#0 if it is '1'. Subsequently, the UE can perform SIB1 PDCCH monitoring based on the signaled CORESET#0 / SS Set#0 (S1205). For example, if the 1-bit indicator / flag is '0', the UE can determine resource blocks and symbol periods for CORESET#0 and PDCCH monitoring times based on the entry value(s) of the setting related to CORESET#0 received from among the table(s) or entries defined for 5G CORESET#0 / SS Set#0. If the above 1-bit indicator / flag is '1', the UE can determine resource blocks and symbol durations for CORESET#0 and PDCCH monitoring times based on the entry value(s) of the CORESET#0 / SS Set#0 related configuration received from among the table(s) or entries defined for 6G CORESET#0 / SS Set#0.

[0207] According to some implementations of this specification, a BS may provide an existing RAT-based CORESET#0 / SS Set#0 configuration (e.g., 5G CORESET#0 / SS Set#0 configuration) or a new RAT-based CORESET#0 / SS Set#0 configuration (e.g., 6G CORESET#0 / SS Set#0 configuration) through an SSB / PBCH. In an MR-SS environment where an existing RAT UE (e.g., 5G UE) and a new RAT UE (e.g., 6G UE) coexist, the BS may efficiently transmit UE-common signals / channels and perform UE-specific signals / channel transmissions using the remaining resources by allowing the existing RAT UE and the new RAT UE to share the same CORESET#0 / SS Set#0. Alternatively, since new resources may allow for more flexible resource allocation, BS can utilize resources more flexibly than CORESET#0 / SS Set#0 for existing RATs (e.g., 5G) by configuring a new RAT-based CORESET#0 / SS Set#0 (e.g., 6G CORESET#0 / SS Set#0) in an environment where only new RAT UEs (e.g., 6G UEs) exist.

[0208] <2. Transmission / Reception of System Information for New RATs>

[0209] In some implementations of this specification, a common CORESET#0 / SS Set#0 for receiving SIB1 may be established for existing RAT UEs (e.g., 5G UEs) and new RAT UEs (e.g., 6G UEs) to support efficient operation in MR-SS carriers / cells / BWPs / TRPs or to reduce the burden of implementing new RATs (e.g., 6G) in the BS. In this case, it is necessary to distinguish the SIB1 to be received by the 5G UE and the 6G UE in the common CORESET#0 / SS Set#0 for receiving SIB1. Below, some implementations of this specification regarding method(s) for a 6G UE to receive SIB1 when a SIB1 PDSCH is scheduled through the 5G / 6G UE common CORESET#0 / SS Set#0 are described. For convenience, some implementations of this specification are described by distinguishing between two cases as follows.

[0210] Case #1: When CORESET#0 / SS Set#0 is shared between 5G UE and 6G UE

[0211] Case #2: When a separate CORESET#0 / SS Set#0 is configured for the 6G UE

[0212] The 6G UE can distinguish between Case #1 and Case #2 through at least one of the following methods.

[0213] Opt A: Case #1 or Case #2 can be distinguished by the PBCH payload, synchronous raster, PSS / SSS / PBCH DM-RS sequence, etc.

[0214] Opt B: If the CORESET#0 / SS set#0 information configured through the PBCH information acquired by the 6G UE is the same as the 5G CORESET#0 / SS set#0 configuration information, the UE assumes Case #1; otherwise, the UE assumes Case #2.

[0215] Opt C: Case #1 is assumed if the 6G UE recognizes that the cell / carrier / BWP / TRP is in operation with MR-SS by means of the PBCH payload, synchronous raster, PSS / SSS / PBCH DM-RS sequence, etc., and Case #2 is assumed otherwise.

[0216] Although some implementations of this specification are described with respect to SIB1, some implementations of this specification may also be generally applied to the transmission / reception of system information in new RATs (e.g., 6G radio).

[0217] For example, a 6G UE can obtain SIB1 information (for 6G wireless) by utilizing one or a combination of the following methods.

[0218] <Method #2-1> Differentiation via RNTI Values

[0219] A 6G UE may attempt to receive a 6G SIB1 PDCCH by assuming an RNTI value different from the 5G SI-RNTI value (e.g., 0xFFFF as defined in 3GPP TS 38.321). This behavior applies only to Case #1 above, and in Case #2, the 6G UE may assume the 5G SI-RNTI value, or regardless of Case #1 or #2, the 6G UE may attempt to receive a 6G SIB1 PDCCH by assuming a separate RNTI value (different from the 5G SI-RNTI value). The separate RNTI value may be a value defined in advance (in a standard document).

[0220] <Method #2-2> Differentiation via DCI Format (or DCI Payload Size)

[0221] Existing 5G UEs can schedule SIB1 PDCCH via DCI format 1_0 scrambled with SI-RNTI. 6G UEs may attempt to receive 6G SIB1 PDCCH by assuming a DCI format or a different DCI payload size than the DCI format / payload size. This operation applies only to Case #1 above, and for Case #2, the 6G UE may assume the same DCI format / payload size as the 5G SIB1 PDCCH, or, regardless of Case #1 or #2, the 6G UE may attempt to receive 6G SIB1 PDCCH by assuming a separate DCI format / payload size (different from the 5G SIB1 PDCCH). The separate DCI format / payload size may be defined in advance (in a standard document) or derived based on specific parameters.

[0222] <Method #2-3> Differentiation via PDCCH DM-RS

[0223] FIG. 13 illustrates the DM-RS location for a PDCCH. In FIG. 13, the resource element (RE) labeled R is the RE for the DM-RS for the PDCCH (hereinafter referred to as PDCCH DM-RS). In a 5G system, a PDCCH consists of one or more control channel elements (CCEs) as indicated in the following table. The following table illustrates the supported PDCCH aggregation levels.

[0224]

[0225] A CCE consists of six resource element groups (REGs), and a REG is equivalent to one resource block during one OFDM symbol. The REGs in a CORESET are numbered starting from 0 for the first OFDM symbol and the lowest numbered resource block in the CORESET, in increasing order in a time-first manner.

[0226] Referring to Fig. 13, it is assumed that within a single PRB composed of 12 resource elements (REs), the existing 5G UE has the PDCCH DM-RS located at the second, sixth, and tenth RE positions (from the lowest RE), and the applicable sequence is defined by the 3GPP TS 38.211 document. Referring to 3GPP TS 38.211, the UE has a reference signal sequence r for the OFDM symbol l. l It can be assumed that (m) is defined by the following.

[0227]

[0228] Here, the pseudo-random sequence c(i) is defined by the length -31 Gold sequence. Length M PN The output sequence c(n) is defined by the following, where n = 0, 1, ..., M PN It is -1.

[0229]

[0230] Here, N C = 1600, the first m-sequence x1(n) is initialized with x1(0)=1, x1(n)=0, n=1,2,...,30, and the initialization of the second m-sequence x2(n) is It is indicated by and its value depends on the application of the above sequence. In the case of Equation 1, the pseudo-random sequence generator is c init = (217 (N slot symb n u s,f +l+ 1)(2N ID + 1) + 2N ID ) mod 2 31 It is initialized to, where l is the OFDM symbol number within the slot, and n u s,f is the slot number within the frame. N ID ∈{0,1,...,65535}, if provided, is given by the upper layer parameter pdcch-DMRS-ScramblingID; N ID ∈{0,1,...,65535} is given by the upper layer parameter pdcch-DMRS-ScramblingID if set for a common search space within a common MBS frequency resource; otherwise, N ID = N cell ID am.

[0231] A 6G UE may assume a sequence generation different from the corresponding 5G PDCCH DM-RS, or assume that the DM-RS is mapped to a different RE location. In this case, the DM-RS sequence generation and / or RE location may be defined in advance (in a standard document) or derived based on specific parameters. For convenience, this specification refers to such a PDCCH DM-RS as 6G PDCCH DM-RS. A 6G UE may attempt to receive a 6G SIB1 PDCCH by assuming a 6G PDCCH DM-RS. This operation applies only to Case #1 above, and in Case #2, the 6G UE may assume a 5G PDCCH DM-RS, or regardless of Case #1 or #2, the 6G UE may attempt to receive a 6G SIB1 PDCCH by assuming a 6G PDCCH DM-RS.

[0232] <Method #2-4> Differentiation via PDCCH candidate locations

[0233] Existing 5G UEs determine PDCCH candidate locations for the SIB1 PDCCH according to each aggregation level (AL) by applying a hashing function to CORESET#0 as follows. For the search space set s associated with CORESET p, the carrier indicator field value n CI For the active DL BWP of the serving cell corresponding to slot n u s,f PDCCH candidates of the search space set in The CCE indices for the aggregation level L corresponding to can be given by the following.

[0234]

[0235] For arbitrary CSS here and; regarding the USS is, and Y p,-1 = n RNTI For ≠ 0, p mod 3 = 0, A p For = 39827, p mod 3 = 1, A p For = 39829, p mod 3 = 2, A p = 39839, and D = 65537; i = 0, ...,L-1; N CCE,p is from 0 to N within CORESET p CCE,p - This is the number of CCEs numbered up to 1. n when the UE has the Carrier Indicator field set by CrossCarrierSchedulingConfig for the serving cell where the PDCCH is monitored. CI is the carrier indicator field value; otherwise, including any CSS, n CI = 0. and, here is UE is n CIIt is the number of PDCCH candidates set to monitor for the aggregation level L of the search space set s for the serving cell corresponding to . For any CSS, M (L) s,max = M (L) s,0 Igo; regarding the USS, M (L) s,max is all set n for CCE aggregation level L of search space set s. CI Across the values It is the maximum value of n. RNTI The RNTI value used for is C-RNTI.

[0236] In some implementations of this specification, the PDCCH candidate for 6G SIB1 may be determined differently from the SIB1 PDCCH assumed by the 5G UE, thereby allowing 6G SIB1 to be identified. In one way, the 5G UE (since SS Set #0 is also one of the CSSs) for SS Set #0 Considering that the value is assumed to be 0, for SS Set #0 of the 6G UE, the corresponding The value may be a non-zero value (e.g., a predefined non-zero value or a value to which the same / different rules as USS are applied). Alternatively, the 5G UE (since SS Set #0 is also one of the CSSs) for SS Set #0 n CI Considering that the value is assumed to be 0, for SS Set #0 of the 6G UE, n CI The value is a non-zero value (e.g., a predefined non-zero value, e.g., n). CI = 1) This can be applied. The operation is applied only to Case #1 above, and in Case #2, the 6G UE can determine the PDCCH candidate in the same way as the 5G UE assumes, or the 6G UE can determine the PDCCH candidate by applying the method regardless of Case #1 / #2.

[0237] <Method #2-5> Differentiation via PDCCH Payload

[0238] A 1-bit indicator / flag within the SIB1 PDCCH can signal whether a 6G SIB1 PDSCH is scheduled. If the indicator / flag is '0' (or '1'), the 6G UE recognizes that the PDSCH scheduled through the SIB1 PDCCH does not contain 6G SIB1 information and may not perform decoding on the PDSCH. Additionally, if the indicator / flag is '1' (or '0'), the 6G UE recognizes that the PDSCH scheduled through the SIB1 PDCCH contains 6G SIB1 information and may perform decoding on the PDSCH. In this case, the PDSCH can carry both 5G SIB1 and 6G SIB1 information, and the 6G UE can identify that the information excluding the 5G SIB1 part is 6G SIB1. Alternatively, the 6G UE may assume that the corresponding SIB1 PDSCH contains extensions for 5G SIB1 and 6G SIB1 (at the RRC SIB1 message level). For example, the UE may obtain the common part between 5G SIB1 and 6G SIB1 through 5G SIB1, and obtain the "uncommon part for 6G" not included in 5G SIB1 through the extension part for 6G SIB1. Here, the "uncommon part for 6G" may include 6G-specific SIB1 information and / or parameter values ​​among 5G SIB1 information that are applied differently (or overridden) for 6G cells.

[0239] Alternatively, if the corresponding indicator / flag is '1' (or '0'), the 6G UE can assume that the PDSCH scheduled through the corresponding SIB1 PDCCH contains only 6G SIB1 and not 5G SIB1. In this case, since the 5G UE may obtain incorrect SIB1 information if it succeeds in decoding the PDSCH, at least one of the following methods may be applied to prevent this problem.

[0240] Opt 1: Change PDSCH DM-RS location (unlike 5G PDSCH)

[0241] Opt 2: Change the PDSCH DM-RS sequence (unlike 5G PDSCH).

[0242] Opt 3: Changes PDSCH data (or PDSCH DM-RS sequence) scrambling (unlike 5G PDSCH)

[0243] Opt 4: Change PDSCH data CRC (unlike 5G PDSCH)

[0244] Here, one of the reserved bits in the 5G SIB1 PDCCH can be used for a 1-bit indicator / flag.

[0245] This method can be applied to Case #1 or to both Case #1 and #2.

[0246] Alternatively, the 6G UE may receive a scheduled SIB1 PDSCH via the SIB1 PDCCH without applying Method #2-5. In this case, the 6G UE may assume that the SIB1 PDSCH contains extensions for 5G SIB1 and 6G SIB1 (at the RRC SIB1 message level). For example, the UE may obtain the common part between 5G SIB1 and 6G SIB1 via the 5G SIB1, and obtain the "6G-oriented non-common part" not included in the 5G SIB1 via the extension part for 6G SIB1. Here, the "6G-oriented non-common part" may include 6G-specific SIB1 information and / or parameter values ​​among the 5G SIB1 information that are applied differently (or overridden) for the 6G cell.

[0247] <Method #2-6> Scheduling 5G SIB1 PDSCH and 6G SIB1 PDSCH as separate resources through a single SIB1 PDSCH

[0248] According to 3GPP TS 38.212, DCI format 1_0 scrambled with SI-RNTI has 17 or 15 reserved bits. These reserved bits can be used to schedule a separate 6G SIB1 PDSCH. For example, all or part of information such as FDRA / TDRA / VRB-to-PRB mapping / modulation and coding scheme (MCS) / redundancy version (RV) can be signaled using all or part of these reserved bits.

[0249] FDRA: (As before) through 1-RB granularity ceil{log2(N DL,BWP RB (N DL,BWP RB + 1) / 2)} bits (here N DL,BWP RBmay be signaled as many times as the number of RBs constituting CORESET#0), or N through X-RB granularity (where X can be a predefined or set value) considering signaling overhead. DL,BWP RB Instead, {N DL,BWP RB Only the bits for which the value / X} is assigned can be signaled. Alternatively, the Y PRB offset value may be signaled so that the UE can recognize that the 6G SIB1 PDSCH is scheduled at a position transitioned by Y RB(s) from the 5G SIB1 PDSCH.

[0250] TDRA: A separate TDRA table is defined for the 6G SIB1 PDSCH, and one index value belonging to that TDRA table may be signaled. Alternatively, a Z-symbol / slot offset value may be signaled so that the UE can recognize that the 6G SIB1 PDSCH is scheduled at a position shifted by Z-symbol / slot(s) from the 5G SIB1 PDSCH.

[0251] > MCS: A separate MCS table is defined for the 6G SIB1 PDSCH, and one index value belonging to that MCS table may be signaled. Alternatively, a W offset value may be signaled, so that an MCS value that is W added to or subtracted from the MCS of the indicated 5G SIB1 PDSCH may be applied to the 6G SIB1 PDSCH.

[0252] Alternatively, the 6G UE may receive the 5G SIB1 PDSCH and the 6G SIB1 PDSCH separately and combine the information to finally obtain 6G SIB1 information. For example, the 6G UE may obtain the common parts between 5G SIB1 and 6G SIB1 through the 5G SIB1 PDSCH and obtain the "6G-oriented non-common parts" not included in 5G SIB1 through the 6G SIB1 PDSCH. Here, the "6G-oriented non-common parts" may include 6G-specific SIB1 information and / or parameter values ​​among the 5G SIB1 information that are applied differently (or overridden) for the 6G cell.

[0253] This method can be applied to Case #1 or to both Case #1 and #2.

[0254] A UE capable of both 5G and 6G, in Case 1, monitors / detects / decodes both 5G SIB1 and 6G SIB1, and if it acquires both 5G SIB1 and 6G SIB1, it may attempt to connect to one or both radios. If a choice must be made, the UE may prioritize 6G or select one according to a predetermined rule. Alternatively, a UE capable of both 5G and 6G, in Case 1, may select one without monitoring / detecting / decoding both 5G SIB1 and 6G SIB1. For example, the UE may prioritize 6G or select one according to a predetermined rule.

[0255] FIG. 14 is another example of a signal transmission / reception flow between a BS and a UE according to some implementations of the present specification. Referring to FIG. 14, the BS can set a common CORESET#0 / SS set#0 for UEs operating with different RATs (e.g., 5G UE and 6G UE) (S1401) and transmit a SIB1 PDCCH (S1403). The 6G UE receives the SIB1 PDCCH and, if a specific indicator / flag bit is '1' (or '0'), can receive 6G SIB1 information from the PDSCH scheduled by the PDCCH. Alternatively, the 6G UE can perform 6G SIB1 PDCCH decoding under the assumption of RNTI / DCI format / DCI payload size / PDCCH DM-RS different from the 5G SIB1 PDCCH, and if the decoding is successful, it can receive 6G SIB1 information from the PDSCH scheduled by the PDCCH (S1405).

[0256] According to some implementations of this specification, when 5G UEs and 6G UEs coexist in an MR-SS environment, BS can enable SIB1 transmission common to UEs by setting the same CORESET#0 / SS set#0, thereby enabling efficient resource utilization.

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

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

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

[0260] 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: detecting a physical broadcast channel (PBCH) (S1501); obtaining first information related to a parameter set and second information related to a physical downlink control channel (PDCCH) setting based on the PBCH (S1503); determining a control resource set (CORESET) for a search space (SS) set and a time for monitoring the PDCCH for the SS set based on the first information and the second information; and receiving the PDCCH on the CORESET at the time for monitoring the PDCCH (S1505).

[0261] FIG. 16 illustrates the flow of downlink (DL) signal transmission in BS according to some implementations of the present specification.

[0262] A BS may perform operations according to some implementations of this specification. 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.

[0263] 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 first information related to a parameter set and second information related to a physical downlink control channel (PDCCH) setting based on a physical broadcast channel (PBCH) (S1601); and transmitting a PDCCH on a control resource set (CORESET) for a search space (SS) set at a time of PDCCH monitoring for the SS set based on the first information and the second information (S1605).

[0264] In some implementations related to FIG. 15 or FIG. 16, the CORESET and the SS set may be associated with a first parameter set based on the first information including a first value, and the CORESET and the SS set may be associated with a second parameter set based on the first information including a second value.

[0265] In some implementations related to FIG. 15 or FIG. 16, the first parameter set may be related to the first RAT, and the second parameter set may be related to the second RAT.

[0266] In some implementations related to FIG. 15 or FIG. 16, the first information may be contained within a master information block (MIB) carried by the PBCH.

[0267] In some implementations related to FIG. 15 or FIG. 16, the first information may be obtained based on a demodulation reference signal (DMRS) sequence for the PBCH.

[0268] In some implementations related to FIG. 15 or FIG. 16, the second information may be obtained based on a PDCCH setting related field within a master information block (MIB) carried by the PBCH. The PDCCH setting related field may include N1 bits for CORESET related information and N2 bits for SS set related information. The CORESET may be determined based on the CORESET related information, and the PDCCH monitoring time may be determined based on the SS related information.

[0269] In some implementations related to FIG. 15 or FIG. 16, the method or operation may further include: omitting decoding or transmitting a physical downlink shared channel (PDSCH) scheduled by the DCI based on the fact that a specific field included in the downlink control information (DCI) within the PDCCH includes a first value; and acquiring or transmitting system information from or on the PDSCH scheduled by the DCI based on the fact that the specific field includes a second value.

[0270] In some implementations related to FIG. 15 or FIG. 16, the method or operation may further include receiving or transmitting a physical downlink shared channel (PDSCH) based on downlink control information (DCI) within the PDCCH. The PDSCH may carry a first system information part and a second system information part, and the DCI may include a field containing a value associated with the first system information part or a value associated with the second system information part.

[0271] In some implementations related to FIG. 15 or FIG. 16, the PDCCH may include downlink control information (DCI) comprising a field associated with a first physical downlink shared channel (PDSCH) carrying first system information and a field associated with a second PDSCH carrying second system information. The methods or operations may further include receiving or transmitting the first PDSCH and the second PDSCH based on the DCI.

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

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

Claims

1. A method performed by user equipment (UE), Detect physical broadcast channel (PBCH); Based on the above PBCH, obtain first information related to a parameter set and second information related to the setting of a physical downlink control channel (PDCCH); Based on the first information and the second information, determine the control resource set (CORESET) for the search space (SS) set and the PDCCH monitoring timing for the SS set; and Includes receiving PDCCH on the CORESET during the above PDCCH monitoring period, method.

2. In Paragraph 1, Based on the fact that the above first information includes a first value, the CORESET and the SS set are associated with a first parameter set, and Based on the fact that the above first information includes a second value, the above CORESET and the above SS set are related to the second parameter set, method.

3. In Paragraph 2, The above first parameter set is related to the first RAT, and The above second parameter set is related to the second RAT, method.

4. In Paragraph 1, The above first information is included within the master information block (MIB) carried by the above PBCH, method.

5. In Paragraph 1, The first information above is obtained based on a demodulation reference signal (DMRS) sequence for the PBCH, method.

6. In Paragraph 1, The above second information is obtained based on fields related to PDCCH settings within the master information block (MIB) carried by the above PBCH, and The above PDCCH setting related field includes N1 bits for CORESET related information and N2 bits for SS set related information, and The above CORESET is determined based on the above CORESET-related information, and the above PDCCH monitoring timing is determined based on the above SS-related information, method.

7. In Paragraph 1, Omitting the decoding of a physical downlink shared channel (PDSCH) scheduled by the DCI based on the fact that a specific field included in the downlink control information (DCI) within the PDCCH includes a first value; and Based on the fact that the above specific field includes a second value, further comprising obtaining system information from the PDSCH scheduled by the DCI, method.

8. In Paragraph 1, It further includes receiving a physical downlink shared channel (PDSCH) based on downlink control information (DCI) within the above PDCCH, and The above PDSCH carries a first system information part and a second system information part, and The above DCI includes a field containing a value related to the first system information part or a value related to the second system information part, method.

9. In Paragraph 1, The above PDCCH includes downlink control information (DCI) comprising a field associated with a first physical downlink shared channel (PDSCH) carrying first system information and a field associated with a second PDSCH carrying second system information, and the method comprises: Further comprising receiving the first PDSCH and the second PDSCH based on the above DCI, method.

10. 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: Detect physical broadcast channel (PBCH); Based on the above PBCH, obtain first information related to a parameter set and second information related to the setting of a physical downlink control channel (PDCCH); Based on the first information and the second information, determine the control resource set (CORESET) for the search space (SS) set and the PDCCH monitoring timing for the SS set; and Includes receiving PDCCH on the CORESET during the above PDCCH monitoring period, User device.

11. 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: Detect physical broadcast channel (PBCH); Based on the above PBCH, obtain first information related to a parameter set and second information related to the setting of a physical downlink control channel (PDCCH); Based on the first information and the second information, determine the control resource set (CORESET) for the search space (SS) set and the PDCCH monitoring timing for the SS set; and Includes receiving PDCCH on the CORESET during the above PDCCH monitoring period, Processing unit.

12. 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: Detect physical broadcast channel (PBCH); Based on the above PBCH, obtain first information related to a parameter set and second information related to the setting of a physical downlink control channel (PDCCH); Based on the first information and the second information, determine the control resource set (CORESET) for the search space (SS) set and the PDCCH monitoring timing for the SS set; and Includes receiving PDCCH on the CORESET during the above PDCCH monitoring period, Storage medium.

13. In a method performed by a base station (BS), Transmitting first information related to a parameter set and second information related to a physical downlink control channel (PDCCH) setting based on a physical broadcast channel (PBCH); and Based on the first information and the second information, including transmitting a PDCCH on a control resource set (CORESET) for a search space (SS) set at a time for PDCCH monitoring for the SS set, method.

14. At least one transmitter / receiver; At least one processor; and It includes at least one computer memory operablely connectable to the at least one processor and, when executed, stores instructions that cause the at least one processor to perform operations, wherein the operations are: Transmitting first information related to a parameter set and second information related to a physical downlink control channel (PDCCH) setting based on a physical broadcast channel (PBCH); and Based on the first information and the second information, including transmitting a PDCCH on a control resource set (CORESET) for a search space (SS) set at a time for PDCCH monitoring for the SS set, Base station.