Method performed by first device, first device, processing device and storage medium, and method performed by second device, second device, processing device and storage medium
The introduction of a full duplex frame structure and resource configuration methods addresses 5G limitations, enhancing data speeds, connectivity, latency, and energy efficiency in communication systems.
Patent Information
- Application Number
- PCT/KR2026/006003
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-12
- Filing Date
- 2026-05-12
- Publication Date
- 2026-11-19
AI Technical Summary
Existing 5G mobile communication systems face limitations in achieving very high data speeds, large numbers of connected devices, global connectivity, low latency, reduced energy consumption for IoT devices, ultra-reliable connectivity, and machine learning capabilities.
A forward frame structure for full duplex (FD) communication, such as subband-wise full duplex (SBFD) or spectrum sharing full duplex (SSFD), is introduced, along with methods for configuring resources to avoid complexity in communication technology standards, and user devices or base stations operating in full duplex mode.
Enhances communication systems to support very high data speeds, large device connectivity, low latency, reduced energy consumption, and ultra-reliable connectivity, while enabling machine learning capabilities.
Smart Images

Figure KR2026006003_19112026_PF_FP_ABST
Abstract
Description
A method performed by a first device, a first device, a processing device and a storage medium, and a method performed by a second device and a second device, a processing device and a storage medium
[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 task of this specification is to provide a forward frame structure for the introduction of full duplex (FD), such as subband-wise full duplex (SBFD) or spectrum sharing full duplex (SSFD).
[0005] Another technical objective of this specification is to provide a method for configuring resources or resource types that can avoid communication technology standards or implementation complexity.
[0006] Another technical objective of this specification is to provide a user device or base station that operates in full duplex mode.
[0007] 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.
[0008] In one aspect of the present specification, a method by a first device is provided. In another aspect of the present specification, a first device is provided comprising at least one transceiver; at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations. In yet another aspect of the present specification, a processing device is provided comprising at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations. In yet another aspect of the present specification, a computer-readable non-transitory storage medium is provided for storing at least one program code that includes instructions that, when executed, cause the at least one processor to perform operations. The method or the operations include: receiving a first random access channel (RACH) setting for a first subband and a second RACH setting for a second subband; Determining a first RACH occasion (RO) set for the first subband based on the first RACH setting and a second RO set for the second subband based on the second RACH setting; transmitting a random access (RA) preamble within the first RO set on the first subband; and performing switching from the first RO set to the second RO set based on the fact that the RA preamble based on the first RO set has been transmitted a predetermined maximum number of times.
[0009] In another aspect of the present specification, a method by means of a second device is provided. In another aspect of the present specification, a second device is provided comprising at least one transceiver; at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations. In yet another aspect of the present specification, a processing device is provided comprising at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations. In yet another aspect of the present specification, a computer-readable non-transitory storage medium is provided for storing at least one program code that includes instructions that, when executed, cause the at least one processor to perform operations. The above method or above operations may include: transmitting a first RACH setting associated with a first set of random access channel (RACH) occasions for a first subband and a second RACH setting associated with a second set of RACH occasions (RO) for a second subband; attempting to receive a random access (RA) preamble within the first set of ROs on the first subband; and performing switching from the first set of ROs to the second set of ROs based on the failure of receiving the RA preamble based on the first set of ROs a predetermined maximum number of times.
[0010] In each aspect of the present specification, performing the switching to the second RO set may include: performing the RA preamble transmission or the PA preamble reception within the second RO set on the second subband.
[0011] In each aspect of the specification, the first RO set may be associated with a short preamble, and the second RO set may be associated with a long preamble.
[0012] In each aspect of the present specification, the first RACH setting and the second RACH setting may each include a RACH setting index.
[0013] In each aspect of the present specification, the first RACH setting and the second RACH setting may each include a frequency offset related parameter.
[0014] In each aspect of the present specification, the first RACH setting and the second RACH setting may be related to frequency offset related parameters. The frequency position of the first RO set may be determined based on the lowest resource block (RB) of the first subband and the frequency offset related parameters, and the frequency position of the second RO set may be determined based on the lowest RB of the second subband and the frequency offset related parameters.
[0015] In each aspect of the present specification, the first RACH setting and the second RACH setting may be associated with the same RACH setting index.
[0016] In each aspect of the present specification, synchronization signal blocks (SSBs) of the cell may be mapped to valid ROs in the first RO set, and the SSBs may be mapped to valid ROs in the second RO set.
[0017] In each aspect of the present specification, the method or operation may further include determining the valid ROs in the first RO set and the valid ROs in the second RO set.
[0018] In each aspect of this specification, an RO that overlaps with a non-SBFD symbol in which the wireless link type of all subbands within the cell is uplink may be determined to be invalid.
[0019] In each aspect of the present specification, the method or operation may further include detecting or transmitting a synchronization signal block (SSB).
[0020] In each aspect of the specification, the RA preamble transmission or the RA preamble reception may be performed in the RO among the ROs in the first RO set to which the detected SSB is mapped.
[0021] 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.
[0022] According to some implementations of the present specification, a forward frame structure for introducing full duplex (FD), such as subband-wise full duplex (SBFD) or spectrum sharing full duplex (SSFD), may be provided.
[0023] According to some implementations of this specification, a method for configuring resources or a method for configuring resource types can be provided to avoid communication technology standards or implementation complexity.
[0024] Another technical challenge of this specification is that a user device or base station operating in full duplex mode may be provided.
[0025] 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.
[0026] 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:
[0027] FIG. 1 illustrates an example of a communication system 1 to which the implementations of the present specification are applied;
[0028] FIG. 2 is a block diagram illustrating examples of communication devices capable of performing the method according to the present specification;
[0029] FIG. 3 illustrates another example of a wireless device capable of performing implementation(s) of the present specification;
[0030] FIG. 4 illustrates an example of a frame structure available in a 3rd generation partnership project (3GPP)-based wireless communication system;
[0031] FIG. 5 illustrates a resource grid of slots;
[0032] FIG. 6 illustrates slot structures that can be used in 3GPP-based systems;
[0033] FIG. 7 illustrates various slot formats;
[0034] FIG. 8 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;
[0035] FIG. 9 illustrates the process of acquiring system information (SI);
[0036] FIG. 10 illustrates an arbitrary connection process that may be applied to the implementation(s) of the present specification;
[0037] FIG. 11 is an example of random access channel (RACH) slots and RACH occasions (RO) according to a physical random access channel (PRACH) setting;
[0038] FIG. 12 shows examples of applying full duplex in the intra-carrier;
[0039] FIG. 13 is an example in which a time resource operating in half duplex (HD) and a time resource operating in full duplex (FD), such as subband-wise full duplex (SBFD) or spectrum sharing full duplex (SSFD), coexist;
[0040] FIG. 14 is a diagram illustrating frequency resource types according to some implementations of the present specification;
[0041] FIG. 15 illustrates frequency resource types for different time resources;
[0042] FIGS. 16 and 17 illustrate frequency resource types according to some implementations of the present specification;
[0043] FIGS. 18 to 20 illustrate examples in which frequency resource types according to time intervals are applied according to some implementations of the present specification;
[0044] FIGS. 21 through 25 illustrate RO positions according to some implementations of the present specification related to Method 1-1 of the present specification;
[0045] FIGS. 26 through 31 illustrate RO positions according to some implementations of the present specification related to Method 1-2 of the present specification;
[0046] FIGS. 32 through 34 illustrate SSB to RO mapping according to some implementations of the present specification;
[0047] FIGS. 35 through 38 illustrate RO positions according to some implementations of the present specification related to Method 2 of the present specification;
[0048] FIG. 39 illustrates a signal transmission / reception flow between a first device (e.g., UE) and a second device (e.g., BS) according to some implementations of the present specification;
[0049] FIG. 40 illustrates the flow of operation in a first device according to some implementations of the present specification;
[0050] FIG. 41 illustrates the flow of operation in a second device according to some implementations of the present specification.
[0051] 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.
[0052] 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.
[0053] 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."
[0054] 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".
[0055] 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."
[0056] 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."
[0057] 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.
[0058] In the following explanation, 'when, if, in case of' can be replaced with 'based on'.
[0059] In this specification, information / status / parameters being "configured or pre-configured" may be interpreted as information / status / parameters being provided or pre-provided to the UE through pre-defined signaling from the BS (e.g., system information block (SIB), medium access control (MAC), radio resource control (RRC)). In this specification, information / status / parameters being "defined or pre-defined" may be interpreted as information / status / parameters being known or stored in advance by the BS and the UE without signaling between the base station and the UE.
[0060] Technical features described individually within a single drawing in this specification may be implemented individually or simultaneously.
[0061] 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.
[0062] 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.
[0063] 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.321, 3GPP TS 38.331, etc.
[0064] 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."
[0065] 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.
[0066] 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.
[0067] 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.
[0068] 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.
[0069] 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.
[0070] 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).
[0071] 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.
[0072] 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.
[0073] 3GPP-based communication standards define downlink physical channels corresponding to resource elements that carry information originating from upper layers, and downlink physical signals corresponding to resource elements used by the physical layer but not carrying information originating from upper layers. For example, the physical downlink shared channel (PDSCH), physical broadcast channel (PBCH), and physical downlink control channel (PDCCH) are defined as downlink physical channels, while the reference signal and synchronization signal are defined as downlink physical signals. The reference signal (RS), also referred to as a pilot, refers to a signal of a specific, predefined waveform known to both the BS and the UE. For example, the demodulation reference signal (DMRS), channel state information RS (CSI-RS), and positioning reference signal (PRS) are defined as downlink reference signals. 3GPP-based communication standards define uplink physical channels corresponding to resource elements that carry information originating from upper layers, and uplink physical signals corresponding to resource elements that are used by the physical layer but do not carry information originating from upper layers.For example, the physical uplink shared channel (PUSCH), physical uplink control channel (PCCH), and physical random access channel (PRACH) are defined as uplink physical channels, and the demodulation reference signal (DMRS) for uplink control / data signals and the sounding reference signal (SRS) used for uplink channel measurement are defined.
[0074] 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.
[0075] 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.
[0076] Since the communication device receives the synchronization signal (SS), demodulation reference signal (DMRS), channel state information reference signal (CSI-RS), positioning reference signal (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.
[0077] 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.
[0078] 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.
[0079] 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).
[0080] 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.
[0081] 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.
[0082] 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.
[0083] 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.
[0084] 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.
[0085] 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.
[0086] 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.
[0087] 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.
[0088] 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.
[0089] 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).
[0090] 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.
[0091] 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.
[0092] 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.
[0093] 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.
[0094] 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.
[0095] 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.
[0096] 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.
[0097] Figure 4 illustrates an example of a frame structure available in a 3GPP-based wireless communication system.
[0098] 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.
[0099] Referring to Fig. 4, uplink and downlink transmissions in an NR system are organized into frames. Each frame is T f = (△f max *N f / 100)*T c = It has a duration of 10 ms and is divided into two half-frames, each with a duration of 5 ms. Here, T is the basic time unit for NR. c = 1 / (△fmax *N f ) and, △f max = 480*10 3 It is Hz, and N f = 4096. For reference, T is the standard time unit for LTE. s = 1 / (△f ref *N f,ref ) and, △f ref = 15*10 3 It is Hz, and N f,ref =2048. T c Wow T s is a constant κ = T s / T c It has a relationship of = 64. Each half-frame consists of 5 subframes, and the period T of a single subframe (SF) sf is 1ms. Subframes are further divided into slots, and the number of slots within a subframe depends on the subcarrier spacing. Each slot consists of 14 or 12 OFDM symbols based on a cyclic prefix. For a normal cyclic prefix (CP), each slot consists of 14 OFDM symbols, while for an extended CP, each slot consists of 12 OFDM symbols. The above numerology is an exponentially scalable subcarrier spacing △f = 2 u It depends on 15 kHz. The following table shows the subcarrier spacing △f = 2 for normalized CP. u *Number of OFDM symbols per slot according to 15 kHz (N slot symb ), number of slots per frame (N frame,u slot ) and the number of slots per subframe (N subframe,u slot It represents ).
[0100]
[0101] 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.
[0102]
[0103] 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.
[0104] FIG. 5 illustrates a resource grid of a slot. A slot contains multiple (e.g., 14 or 12) symbols in the time domain. For each numerator (e.g., subcarrier interval) and carrier, a common resource block (CRB) N indicated by upper-layer signaling (e.g., radio resource control (RRC) signaling) start,u grid Starting from,N size,u grid,x *N RB sc individual subcarriers and N subframe,u symb A resource grid of N OFDM symbols is defined. Here, N size,u grid,x is the number of resource blocks (RB) in the resource grid, and the subscript x is DL for downlinks and UL for uplinks. RB sc is the number of subcarriers per RB, and in 3GPP-based wireless communication systems, N RB scis typically 12. There is one resource grid for a given antenna port p, subcarrier spacing configuration u, and transmission direction (DL or UL). Carrier bandwidth N for subcarrier spacing configuration u. size,u grid This is given to the UE by upper-layer parameters (e.g., RRC parameters) from the network. Each element within the resource grid for antenna port p and subcarrier spacing u is referred to as a resource element (RE), and one complex symbol can be mapped to each resource element. Each resource element within the resource grid is uniquely identified by an index k in the frequency domain and an index l indicating the symbol position relative to a reference point in the time domain. In an NR system, RBs are defined by 12 consecutive subcarriers in the frequency domain. In an NR system, RBs can be classified into Common Resource Blocks (CRBs) and Physical Resource Blocks (PRBs). CRBs are numbered upwards from 0 in the frequency domain for subcarrier spacing u. The center of subcarrier 0 of CRB 0 for subcarrier spacing u coincides with 'Point A', which is the common reference point for the resource block grids. The PRBs for the subcarrier spacing setting u are defined within the bandwidth part (BWP), and range from 0 to N size,u BWP,i Numbered up to -1, where i is the number of the above bandwidth part. Common resource block n u CRB and physical resource block n within bandwidth part i PRB The relationships between them are as follows: n u PRB = n u CRB +N start,u BWP,i , here N start,u BWP,iis a common resource block where the above bandwidth part starts relative to CRB 0. A BWP contains multiple consecutive RBs in the frequency domain. For example, a BWP is a given numerator u within a BWP i on a given carrier. i It is a subset of contiguous CRBs defined for. The carrier may contain up to N (e.g., 5) BWPs. A UE may be configured to have one or more BWPs on a given component carrier. Data communication is performed through the enabled BWPs, and only a predetermined number (e.g., 1) of the BWPs configured for the UE may be enabled on the carrier.
[0105] For each serving cell within a set of DL BWPs or UL BWPs, the network establishes at least an initial DL BWP and one initial UL BWP (if the serving cell is configured with an uplink) or two initial UL BWPs (if using a supplementary uplink). The network may also establish additional ULs and DL BWPs for the serving cell. For each DL BWP or UL BWP, the UE is provided with the following parameters for the serving cell: i) subcarrier spacing, ii) circular prefix, iii) N start BWP Assuming = 275, offset RB set and length L RB CRBN provided by the RRC parameter locationAndBandwidth, which indicates as the resource indicator value (RIV). start BWP =O carrier +RB start and the number of contiguous RBs N size BWP =L RB , and O provided by the RRC parameter offsetToCarrier for the subcarrier spacing carrier; Index within the set of the above DL BWPs or UL BWPs; set of BWP-common parameters and set of BWP-exclusive parameters.
[0106] 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.
[0107] 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.
[0108] 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.
[0109]
[0110] FIG. 6 illustrates slot structures that can be used in 3GPP-based systems. In all 3GPP-based systems, e.g., NR systems, each slot may have a self-contained structure that includes i) a DL control channel, ii) DL or UL data, and / or iii) a UL control channel. For example, the first N symbols within a slot may be used to transmit a DL control channel (hereinafter referred to as the DL control area), and the last M symbols within a slot may be used to transmit a UL control channel (hereinafter referred to as the UL control area). N and M are each non-negative integers. The resource area (hereinafter referred to as the data area) located between the DL control area and the UL control area may be used for transmitting DL data or for transmitting UL data. The symbols of a single slot may be divided into DL, UL, or group(s) of consecutive symbols that can be used flexibly. Hereinafter, information indicating how each of the symbols in a slot is used is referred to as the slot format. For example, a slot format can define which symbols within the slot are used for UL and which symbols are used for DL. Information regarding the slot format can be transmitted via one or more of the following signals:
[0111] Static or semi-static slot format indications (SFIs) via upper-layer signaling (e.g., TDD-UL-DL-ConfigurationCommon and / or TDD-UL-DL-ConfigDedicated, etc.), and / or
[0112] Measurement-related scheduling signals (e.g., measurement-related signals set by UE-specific RRC signaling), and / or
[0113] Dynamic SFI (e.g., signals transmitted via DCI format 2_0), and / or
[0114] UE-specific data transmission scheduling signal (e.g., UE-specific DCI).
[0115] Static or semi-static SFIs may be indicated via cell-specific RRC signaling (e.g., TDD-UL-DL-ConfigurationCommon) or UE-specific RRC signaling (e.g., TDD-UL-DL-ConfigDedicated). Measurement-related signals are indicated via UE-specific RRC signaling, and such signals may indicate periodic / semi-persistent CSI-RS for CSI reporting, periodic CSI reporting, periodic / semi-persistent SRS, etc. UE-specific data transmission-related signals may include a DCI that triggers non-periodic measurement-related signals, such as a PDSCH, PUSCH, a PUCCH with ACK / NACK for PDSCH, a UE-specific DCI that triggers non-periodic CSI-RS, a non-periodic SRS, etc.
[0116] If a serving cell is to be operated in time division duplex (TDD) mode, the BS can set patterns for UL and DL allocation for said serving cell through upper-layer (e.g., RRC) signaling. For example, the following parameters can be used to set the TDD DL-UL pattern:
[0117] - dl-UL-TransmissionPeriodicity providing a DL-UL pattern period;
[0118] - nrofDownlinkSlots providing the number of consecutive full DL slots at the beginning of each DL-UL pattern, wherein a full DL slot is a slot having only downlink symbols;
[0119] - nrofDownlinkSymbols providing the number of consecutive DL symbols at the beginning of the slot immediately following the last complete DL slot;
[0120] - nrofUplinkSlots providing the number of consecutive full UL slots within the end of each DL-UL pattern, wherein a full UL slot is a slot having only uplink symbols; and
[0121] - nrofUplinkSymbols provides the number of consecutive UL symbols at the end of the slot immediately preceding the first complete UL slot.
[0122] Among the symbols in the above DL-UL pattern, the remaining symbols that are not set as either DL symbols or UL symbols are fluid symbols.
[0123] A UE that receives a configuration regarding the TDD DL-UL pattern, that is, a TDD UL-DL configuration (e.g., tdd-UL-DL-ConfigurationCommon, or tdd-UL-DLConfigurationDedicated), through upper layer signaling sets a slot-specific slot format across the slots based on the above configuration.
[0124] A slot format may include a format for 0, 1, or 2 switching points. FIG. 7 illustrates various slot formats. Specifically, FIG. 7(a) illustrates a slot format for zero switching points, FIG. 7(b) illustrates a slot format for one switching point, and FIG. 7(c) illustrates a slot format for two switching points. A slot format for zero switching points consists of 14 DL symbols, 14 flexible symbols, or 14 UL symbols. A slot format for one switching point is configured to start with zero or more DL symbols and end with zero or more UL symbols, including one or more flexible symbols and DL / UL symbols in between. The slot format for two switching points consists of a first set of 7 symbols starting with zero or more DL symbols and ending with one or more UL symbols at the 7th symbol, and a second set of 7 symbols starting with one or more DL symbols and ending with zero or more UL symbols. The first set of 7 symbols and the second set of 7 symbols may each contain zero or more fluid symbols.
[0125] Meanwhile, regarding symbols, various combinations of DL symbols, UL symbols, and flexible symbols are possible, but a predetermined number of combinations can be predefined as slot formats, and the predefined slot formats can each be identified by slot format indices. The following table provides examples of some of the predefined slot formats. In the following table, D represents a DL symbol, U represents a UL symbol, and F represents a flexible symbol (denote). The horizontal axis ranges from 0 to 13, representing slot numbers within the slot, and the vertical axis ranges from 0 to 255, representing slot format indices.
[0126]
[0127] Up to 256 such slot formats may be defined. Based on up to 256 slot formats, a UE-specific SFI table may be set for the UE via upper-level signaling, and specific index values of the UE-specific SFI table may be provided to the UE via DCI format 2_0 (or group common PDCCH). For example, to indicate which of the predefined slot formats is used in a specific slot, the BS may set a set of slot format combinations applicable to a corresponding serving cell on a cell-by-cell basis via upper-level (e.g., RRC) signaling for a set of serving cells, and may configure the UE to monitor the group common PDCCH for slot format indicators (SFIs) via upper-level (e.g., RRC) signaling. Hereinafter, the DCI carried by the group common PDCCH for SFIs is referred to as the SFI DCI. DCI format 2_0 may be used as the SFI DCI. For example, for each serving cell within a set of serving cells, the BS may provide the UE with the (start) position of the slot format combination ID (i.e., SFI-index) for the corresponding serving cell within the SFI DCI, the set of slot format combinations applicable to the corresponding serving cell, and the reference subcarrier interval setting for each slot format within the slot format combination indicated by the SFI-index value within the SFI DCI. For each slot format combination within the set of slot format combinations, one or more slot formats are set and a slot format combination ID (i.e., SFI-index) is assigned. For example, if the BS intends to set a slot format combination with N slot formats, it may indicate N slot format indices among the slot format indices for the predefined slot formats (e.g., see Table 4) for the corresponding slot format combination.BS informs the UE of the total length of the DCI payload scrambled with the SFI-RNTI, which is a Radio Network Temporary Identifier (RNTI) used for SFIs, and the SFI-RNTI, in order to configure the UE to monitor a group-common PDCCH for SFIs. When the UE detects the PDCCH based on the SFI-RNTI, the UE can determine the slot format(s) for the corresponding serving cell from the SFI-index for the serving cell among the SFI-indexes within the DCI payload in the PDCCH.
[0128] Symbols designated as fluid by the TDD DL-UL pattern setting may be designated as uplink, downlink, or fluid by the SFI DCI. Symbols designated as downlink / uplink by the TDD DL-UL pattern setting are not overridden as uplink / downlink or fluid by the SFI DCI.
[0129] If the TDD DL-UL pattern is not set, the UE can determine whether each slot is an uplink or a downlink and the symbol allocation within each slot based on the SFI DCI and / or the DCI that schedules or triggers the transmission of the downlink or uplink signal (e.g., DCI format 1_0, DCI format 1_1, DCI format 1_2, DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 2_3).
[0130] The UE can determine the slot format based on predefined or pre-set priorities for the signals providing slot format-related information described above. For example, if the UE receives information related to slot format through multiple signals, the UE considers the instruction information of the next-highest priority signal only to verify the use of the symbol indicated by the fluid symbol by the higher-priority signal.
[0131] Slot format information via cell-specific upper-layer signaling (e.g., TDD-UL-DL-ConfigurationCommon) > Slot format information via UE-specific upper-layer signaling (e.g., TDD-UL-DL-ConfigDedicated) > Slot format information via group-common PDCCH (e.g., DCI Format 2_0) > UE-specific data transfer scheduling information > Measurement-related scheduling information
[0132] Therefore, when a specific symbol in a slot is indicated to the UE as downlink / uplink via cell-specific RRC signaling or UE-specific RRC signaling, the UE does not expect DCI format 2_0 (or group-specific PDCCH containing DCI format 2_0) to indicate that the specific symbol is uplink / downlink or flexible. When a specific symbol in a slot is indicated to the UE as a flexible symbol via DCI format 2_0 (or group-specific PDCCH containing DCI format 2_0), the UE transmits / receives the relevant signal on the specific symbol only when separate scheduling information (e.g., UE-specific scheduling DCI) is received, and does not transmit / receive the signal on the specific symbol if separate scheduling information is not received.
[0133] Additionally, DCI format 2_0 (or a group-specific PDCCH containing DCI format 2_0) may further include information regarding available RB set(s), channel occupancy time (COT) duration, and seek space set group switching. For example, DCI format 2_0 may include one or more of the following information. The cyclic redundancy check (CRC) of DCI format 2_0 may be scrambled with a UE group common identifier (e.g., SFI-RNTI). The size of DCI format 2_0 can be set up to 128 bits by the upper layer (e.g., RRC).
[0134] Slot Format Indicator 1, Slot Format Indicator 2, ..., Slot Format Indicator N.
[0135] When the upper layer parameter availableRB-SetPerCell is set
[0136] Available RB set Indicator 1, Available RB set Indicator 2, ..., Available RB set Indicator N1,
[0137] When the upper layer parameter CO-DurationPerCell is set
[0138] >> COT duration indicator 1, COT duration indicator 2, ..., COT duration indicator N2.
[0139] When the upper layer parameter searchSpaceSwitchTrigger is set
[0140] >> Monitoring group flag 1, Monitoring group flag 2, ..., Monitoring group flag M.
[0141] Here, an RB set corresponds to a frequency resource in which a channel access procedure (CAP) is performed individually in the shared spectrum and may consist of multiple contiguous (P)RBs. The available RB set indicator indicates the index of the RB set available for DL reception within the cell. The COT duration indicator represents the channel occupancy time shared between the BS and the UE in the shared spectrum. The monitoring group flag indicates the search space group that the UE must monitor among multiple search space groups set for the same cell. DCI format 2_0 is group common control information, and the location of the information for each UE (e.g., start point) may be set by a higher layer (e.g., RRC) signal. For example, availableRB-SetPerCell is a UE-specific signal and may contain information regarding the location (e.g., start point) of the available RB set indicator for the corresponding UE within DCI format 2_0. Likewise, CO-DurationPerCell and searchSpaceSwitchTrigger are also UE-specific signals and may each contain information regarding the location (e.g., starting point) of information about the corresponding UE within DCI format 2_0.
[0142] FIG. 8 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.
[0143] A UE that has been turned on again after being turned off or has lost connection with a wireless communication system first performs an initial cell search process, such as searching for a suitable cell to camp on and synchronizing with said cell or the BS of said cell (S11). During the initial cell search process, the UE receives a synchronization signal block (SSB) (also called an 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). Based on the PSS / SSS, the UE synchronizes with the BS and obtains information such as the cell identifier (ID). Additionally, the UE can obtain broadcast information within the cell based on the PBCH. Meanwhile, during the initial cell search process, the UE can receive a downlink reference signal (DL RS) to check the downlink channel status.
[0144] 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).
[0145] Subsequently, the UE may perform a random access procedure to complete access to the BS (S13 to S16). For example, during the random access procedure, the UE may transmit a preamble through a physical random access channel (PRACH) (S13) and receive a random access response (RAR) for the preamble through a PDCCH and a corresponding PDSCH (S14). If the reception of the RAR for the UE fails, the UE may attempt to re-transmit the preamble. In the case of contention-based random access, a contention resolution procedure (S16) may be performed, which includes transmitting a PUSCH based on the UL resource allocation included in the RAR (S15) and receiving a PDCCH and a corresponding PDSCH.
[0146] 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.
[0147] Figure 9 illustrates the process of acquiring system information (SI). Through the SI acquisition process, the UE can acquire access stratum (AS) / non-access stratum (NAS) information. 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.
[0148] 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.
[0149] - The MIB is always transmitted over a BCH with a periododicity of 80 ms and repetitions created within 80 ms. The MIB contains information / parameters related to SIB1 reception and is transmitted via the SSB's PBCH. During initial cell selection, the UE assumes that half-frames containing the SSB(s) repeat with a period of 20 ms. Based on the MIB, the UE can determine whether a control resource set (CORESET) exists for the Type0-PDCCH common search space. For example, the field ssb-SubcarrierOffset within the MIB is k, which is a frequency domain offset in units of the number of subcarriers between the SSB and the overall resource block grid. SSB Corresponds to. Upon detection of an SS / PBCH block, the UE, in the case of FR1, k SSB If < 24, or in the case of FR2, k SSBIf < 12, it can be determined that a CORESET exists for the Type-0 PDCCH common search space (CSS) set, and for FR1, k SSB If > 23, or in the case of FR2, k SSB If > 11, it can be determined that a Type-0 PDCCH CSS set does not exist. The Type-0 PDCCH common seek space is a type of PDCCH seek space and is used to transmit PDCCHs that schedule SI messages. If a Type-0 PDCCH common seek space exists, the UE can determine (i) multiple consecutive RBs and one or more consecutive symbols that constitute a CORESET and (ii) the PDCCH time (i.e., the time domain location for receiving the PDCCH) based on information within the MIB (e.g., pdcch-ConfigSIB1). If a Type-0 PDCCH common seek space does not exist, pdcch-ConfigSIB1 provides information regarding frequency locations where SSB / SIB1 exists and frequency ranges where SSB / SIB1 does not exist.
[0150] - 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.
[0151] - 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.
[0152] 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.
[0153] 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.
[0154] 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.
[0155] - Step 1: The UE transmits the RA preamble via PRACH.
[0156] - Step 2: The UE receives a random access response (RAR) from the BS via PDSCH.
[0157] - 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.
[0158] - Step 4: The UE receives a contention resolution message from the BS via PDSCH.
[0159] The UE can receive information regarding random access from the BS through system information. For example, information regarding RACH times associated with SSBs on the cell may be provided through system information. The UE can select an SSB among those received on the cell for which the reference signal received power (RSRP) measured based on the SSB exceeds a threshold, and transmit an RA preamble through the PRACH associated with the selected SSB. For example, if random access is required, the UE transmits Msg1 (e.g., preamble) to the BS on the PRACH. The BS can distinguish each random access preamble through the time / frequency resource (RA Occasion, RO) and the random access preamble index (Preamble Index, PI). When the BS receives a random access preamble from the UE, the BS transmits a RAR message to the UE on the PDSCH. To receive a RAR message, the UE monitors a L1 / L2 control channel (PDCCH) masked with a cyclic redundancy check (CRC) by a Random Access-RnTI (RA-RNTI) containing scheduling information for the RAR message within a preset time window (e.g., ra-ResponseWindow). If scheduling information is received through the PDCCH masked with the RA-RNTI, the UE may receive a RAR message from the PDCCH indicated by the scheduling information. Subsequently, the UE determines whether there is a RAR for itself in the RAR message. Whether a RAR for itself exists can be determined by whether a Random Access preamble ID (RAPID) exists for the preamble transmitted by the UE. The index of the preamble transmitted by the UE and the RAPID may be the same.A RAR includes a corresponding random access preamble index, timing offset information for UL synchronization (e.g., a timing advance command (TAC)), UL scheduling information for sending Msg3 (e.g., a UL grant), and temporary UE identification information (e.g., Temporary-C-RNTI, TC-RNTI). Upon receiving the RAR, the UE sends Msg3 via PUSCH according to the UL scheduling information and timing offset values within the RAR. Msg3 may include the UE's ID (or the UE's global ID). Additionally, Msg3 may include information related to an RRC connection request for initial access to the network (e.g., an RRCSetupRequest message). After receiving Msg3, the BS sends Msg4, a contention resolution message, to the UE. If the UE receives the contention resolution message and the contention is successfully resolved, TC-RNTI is changed to C-RNTI. Msg4 includes the UE's ID and / or It may include information related to the RRC connection (e.g., RRCSetup message). If the information transmitted via Msg3 does not match the information received via Msg4, or if Msg4 is not received for a certain period of time, the UE may report that the contention resolution failed and retransmit Msg3.
[0160] 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.
[0161] - Step 0: BS assigns the RA preamble to the UE via dedicated signaling.
[0162] - Step 1: The UE transmits the RA preamble via PRACH.
[0163] - Step 2: The UE receives the RAR via the PDSCH from the BS.
[0164] 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.
[0165] 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.
[0166] 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).
[0167] A BS that receives MsgA may send MsgB to a UE. MsgB may include a RAR for said UE.
[0168] A message related to an RRC connection request (e.g., RRCSetupRequest message) requesting the establishment of 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.
[0169] The current standard document 3GPP TS 38.213 discloses the random access process and PRACH configuration as follows. For a more detailed description of the RRC parameters mentioned below, refer to 3GPP TS 38.331.
[0170] Prior to the initiation of the physical random access process, Layer 1 receives a set of SS / PBCH block indices from the upper layers and provides the corresponding set of RSRP measurements to the upper layers.
[0171] Prior to the initiation of the physical random access process, Layer 1 may receive an indication from the upper layers to perform a Type-1 random access process or a Type-2 random access process.
[0172] Prior to the initiation of the physical random access process, Layer 1 receives the following information from the upper layers:
[0173] - Physical Random Access Channel (PRACH) transmission parameters (PRACH preamble format, time resources, and frequency resources for PRACH transmission).
[0174] - Parameters for determining the root sequences within the PRACH preamble sequence set and their cylic shifts (index to logical root sequence table, cylic shifts (N CS ), and set type (unrestricted, restricted set A, or restricted set B)).
[0175] From a physical layer perspective, the type-1 L1 random access process includes the transmission of a random access preamble (Msg1) in a PRACH, a random access response (RAR) with a PDCCH / PDSCH (Msg2), and, when applicable, a PUSCH scheduled by a RAR UL grant, and a transmission of a PDSCH for contention resolution.
[0176] From a physical layer perspective, the above-mentioned type-2 L1 random access process includes a random access preamble in a PRACH and the transmission of a PUSCH (MsgA), the reception of a RAR message with a PDCCH / PDSCH (MsgB), and, if applicable, the transmission of a PDSCH for contention resolution with a PUSCH scheduled by a fallback RAR UL grant.
[0177] When a random access process for a UE is initiated by a PDCCH order, the PRACH transmission has the same subcarrier spacing (SCS) as the PRACH transmission initiated by the upper layers.
[0178] When a UE is configured to have two UL carriers for a serving cell and the UE detects a PDCCH command, the UE determines the UL carrier for the corresponding PRACH transmission using the UL / supplementary (supplementary UL, SUL) indicator field value from the detected PDCCH command.
[0179] The physical random access process for the UE is triggered upon a request for a PRACH transmission by upper layers or by a PDCCH command to the cell. Configuration by upper layers for a PRACH transmission includes the following:
[0180] - Settings for PRACH transmission on the above cell.
[0181] - Preamble Index, Preamble SCS, PRACH Target Reception Power P PRACH,target , when applicable, the corresponding RA-RNTI, PRACH resource for the above cell.
[0182] - If the UE would transmit the PRACH with repetitions, N for transmitting the PRACH rep preamble >1 Number of preamble iterations.
[0183] To aid in understanding some implementations of this specification, PRACH configurations according to the current standard document are first described with reference to the following table and Figure 11. The following table provides examples of arbitrary connection configurations. In particular, the following table is part of Table 6.3.3.2-4, which defines arbitrary connection configurations for FR2 and unpaired spectrum as described in 3GPP TS 38.211.
[0184]
[0185] The table above is a mother table for indicating the PRACH configuration index in 3GPP TS 38.211, and the UE can determine the appropriate table from SIB1 based on the frequency range and whether it is frequency division duplex (FDD) or time division duplex (TDD), and receive a row index within the determined table to configure the RACH slots and ROs. Based on the PRACH configuration index (also called the RACH configuration index), the UE can determine the available set of PRACH times for transmitting the random access preamble for Msg1.
[0186] RA preambles may be transmitted only within time resources obtained based on a provided PRACH setting index from the PRACH setting table associated with the corresponding spectrum type and frequency range among PRACH setting tables containing multiple PRACH settings. RA preambles may be transmitted only within frequency resources given by the upper-level parameter msg1-FrequencyStart or msgA-RO-FrequencyStart regarding the offset of the lowest PRACH transmission time in the frequency domain for PRB 0. PRACH frequency resources n RA ∈ {0,1,..., M - 1} is numbered in increasing order starting from the lowest frequency within the initial UL BWP during initial connection, where M may be equal to the upper layer parameter msg1-FDM or msgA-RO-FDM regarding the number of PRACH transmission times FDMed within a single time instance. Otherwise, n RA They are numbered in increasing order within the active UL BWP, starting from the lowest frequency.
[0187] FIG. 11 is an example of random access channel (RACH) slots and RACH occasions (ROs) according to a physical random access channel (PRACH) setting. In particular, FIG. 11 illustrates RACH slots and ROs when a PRACH setting index 28 is provided through the RACH setting for FR2 and a cell on the unpaired spectrum. Referring to FIG. 11, when the PRACH setting index is 28, the ROs are assigned to each frame consisting of 40 slots when viewed along the time axis, and there are 3 ROs in each slot.
[0188] The UE, on the designated PRACH resource or N rep preamble For preamble iterations, use the same spatial filter to N rep preamble On a determined set of resources, transmission power P as described in Section 7.4 of 3GPP TS 38.214 PRACH,b,f,c (i) A UE transmits a PRACH on a cell using the selected PRACH format with transmission power P PRACH,b,f,c (i), as described in section 7.4 of 3GPP TS 38.214, on the indicated PRACH resource or on a determined set of N rep preamble resources using a same spatial filter in case of N rep preamble preamble repetitions.)
[0189] For a Type-1 random access process, the UE is provided by the RRC parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB with the number N of SS / PBCH block indexes associated with a single PRACH occasion and the number R of contention-based preambles per SS / PBCH block index per valid PRACH occasion.
[0190] In the case of a Type-1 random access process having a common configuration of PRACH times, the UE is provided with the number of SS / PBCH block indices N associated with one PRACH time by the RRC parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB and the number of contention-based preambles Q per SS / PBCH block index per valid PRACH time by the RRC parameter msgA-CB-PreamblesPerSSB-PerSharedRO. PRACH transmission may take place on a subset of PRACH times associated with the same SS / PBCH block index within an SSB-RO mapping cycle for a UE provided with a PRACH mask index by the RRC parameter msgA-SSB-SharedRO-MaskIndex in accordance with 3GPP TS 38.321.
[0191] For a Type-2 random access procedure with a separate configuration of PRACH occasions with a Type-1 random access procedure, the UE is provided with the number of SS / PBCH block indices N associated with one PRACH occasion and the number of contention-based preambles R per SS / PBCH block index per valid PRACH occasion, the number of SS / PBCH block indices N associated with one PRACH occation, by the RRC parameter msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB when provided, and otherwise by ssb-perRACH-OccasionAndCB-PreamblesPerSSB.
[0192] For a random access process associated with a feature combination indicated by the RRC information element FeatureCombinationPreambles (which associates a set of feature combinations with preambles), the UE is provided with the number of SS / PBCH block indices N associated with one PRACH time by the RRC parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB or, if provided, msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB, and the number of contention-based preambles S per SS / PBCH block index per valid PRACH time by the RRC parameter startPreambleForThisPartition and the RRC parameter numberOfPreamblesPerSSB-ForThisPartition. PRACH transmission is a PRACH associated with the same SS / PBCH block index within an SSB-RO mapping cycle for a UE provided with a PRACH mask index by ssb-SharedRO-MaskIndex in accordance with 3GPP TS 38.321. It can be done on a subset of periods.
[0193] For a Type-1 random access process, or for a Type-2 random access process having a separate configuration of PRACH periods from the Type-1 random access process, if N < 1, one SS / PBCH block index is mapped to 1 / N consecutive valid PRACH periods, and per valid PRACH period, R contention-based preambles with consecutive indices associated with the said SS / PBCH block index start from preamble index 0. If N ≥ 1, per valid PRACH period, R contention-based preambles with consecutive indices associated with the SS / PBCH block index n start from preamble index n*N total preambleStarting from / N, 0 ≤ n ≤ N-1, and N total preamble is provided by totalNumberOfRA-Preambles for a type-1 random connection process, or by msgA-TotalNumberOfRA-Preambles for a type-2 random connection process that has a separate configuration of PRACH times from the type-1 random connection process, and is an integer multiple of N.
[0194] For a Type-2 random access process having common settings for PRACH periods with a Type-1 random access process, if N < 1, a single SS / PBCH block index is mapped to 1 / N consecutive valid PRACH periods, and Q contention-based preambles having consecutive indices associated with the said SS / PBCH block index per valid PRACH period start from preamble index R. If N ≥ 1, Q contention-based preambles having consecutive indices associated with the SS / PBCH block index n per valid PRACH period start from preamble index n*N total preamble Starting from / N + R, where 0 ≤ n ≤ N-1 and N total preamble The type-1 random connection process is provided by totalNumberOfRA-Preambles.
[0195] In the case of link recovery, the UE is provided with N SS / PBCH block indices associated with a single PRACH time by the RRC parameter ssb-perRACH-Occasion in the RRC configuration BeamFailureRecoveryConfig. In the case of a dedicated RACH configuration provided by the RRC configuration RACH-ConfigDedicated, if parameters cfra for contention-free random access (CFRA) to a given target cell are provided, the UE is provided with N SS / PBCH block indices associated with a single PRACH time by the parameter ssb-perRACH-Occasion regarding random access times for contention-free random access. If N < 1, a single SS / PBCH block index is mapped to 1 / N consecutive valid PRACH times. If N ≥ 1, all N consecutive SS / PBCH block indices are associated with a single PRACH time.
[0196] The SS / PBCH block indices provided by ssb-PositionsInBurst within SIB1, ServingCellConfigCommon, SSB-MTC-AdditionalPCI, or LTM-SSB-Config are mapped to valid PRACH times in the following order, and the parameters are described in 3GPP TS 38.211.
[0197] First, in the increasing order of preamble indices within a single PRACH period
[0198] Second, in increasing order of frequency resource indices for frequency-multiplexed PRACH periods
[0199] Third, in increasing order of time resource indices for time-multiplexed PRACH periods within the PRACH slot
[0200] Fourth, in increasing order of the indices for the PRACH slots
[0201] The association period, starting from frame 0, for mapping SS / PBCH block indexes to PRACH periods is N SSB Tx an association period, starting from frame 0, for mapping SS / PBCH block indexes to PRACH occasions is the smallest integer number in the set determined by the PRACH configuration period according to the following table such that N SSB Tx SS / PBCH block indexes are mapped at least once to the PRACH occasions within the association period), where UE is N from the value of ssb-PositionsInBurst in SIB1, ServingCellConfigCommon, SSB-MTC-AdditionalPCI, or LTM-SSB-Config. SSB Tx Obtains. After mapping cycles of an integer number of SS / PBCH block indices versus PRACH times within the associated interval, N SSB TxIf there is a set of PRACH occasions or PRACH preambles that are not mapped to N SS / PBCH block indexes, then no SS / PBCH block indexes are mapped to said set of PRACH occasions or PRACH preambles. SSB Tx SS / PBCH block indexes, no SS / PBCH block indexes are mapped to the set of PRACH occasions or PRACH preambles). An association pattern period includes one or more association periods and is determined so that a pattern between PRACH occasions and SS / PBCH block indexes repeats at most every 160 ms. If any PRACH occasions not associated with SS / PBCH block indexes exist after an integer number of association periods, they are not used for PRACH transmissions.
[0202] The following table illustrates the mapping between the PRACH setting period and the association period between the SS / PBCH block and the PRACH occasion.
[0203]
[0204] In the case of a PRACH transmission by a UE triggered by a PDCCH command, if the value of the Random Connection Preamble Index field is not zero, the PRACH Mask Index field indicates the PRACH timing for said PRACH transmission, wherein the PRACH timings are associated with the SS / PBCH block index indicated by the SS / PBCH Block Index field of said PDCCH command, and if any, the Cell Indicator field indicates the cell for the PRACH transmission (see 3GPP TS 38.212). The UE K by the RRC parameter cellSpecificKoffset cell,offset If provided, the above PRACH time is slot n + 2 u ·K cell,offset After, and here n is T TA Assuming = 0, it is a slot in the UL BWP for a PRACH transmission that overlaps with the end of the PDCCH command reception, and u is the SCS setting for said PRACH transmission. If the PDCCH reception for a PDCCH command contains two PDCCH candidates from two linked sets of searchspaces based on the RRC parameter searchSpaceLinkingId used to link two searchspaces of the same type within the same BWP, the last symbol of said PDCCH reception is the last symbol of the PDCCH candidate that ends later, as described in Section 10.1 of 3GPP TS 38.213. said PDCCH reception contains said two PDCCH candidates even when the UE is not required to monitor one of said two PDCCH candidates, as described in Section 10 (excluding Section 10.4), 11.1, 11.1.1, and 17.2 of 3GPP 38.213.
[0205] In the case of a PRACH transmission triggered by upper layers, if the RRC parameter ssb-ResourceList is provided, the PRACH mask index is indicated by the RRC parameter ra-ssb-OccasionMaskIndex, which indicates the PRACH timing for the PRACH transmission.
[0206] PRACH periods are mapped consecutively per corresponding SS / PBCH block index. The indexing of the PRACH periods indicated by the mask index value is reset per mapping cycle of consecutive PRACH periods per SS / PBCH block index. Within the first available mapping cycle, the UE selects the PRACH period indicated by the PRACH mask index value for the indicated SS / PBCH block index for PRACH transmission.
[0207] For the preamble index indicated above, the ordering of the PRACH periods is
[0208] First, regarding the frequency-multiplexed PRACH periods, in increasing order of frequency resource indices
[0209] Second, regarding the time-multiplexed PRACH periods within the PRACH slot, in increasing order of time resource indices
[0210] Third, for the PRACH slots, in increasing order of the indices
[0211] N rep preamble For a PRACH transmission with multiple preamble repetitions, the set is continuous in time and uses the same frequency resources, and is associated with one or more identical SS / PBCH block index(s), N rep preambleIt consists of valid PRACH periods, and each SS / PBCH block index is associated with the same preamble index within all valid PRACH periods in the set.
[0212] In the case of a PRACH transmission with preamble repetitions, the time interval starting from frame 0 is the above N SSB Tx For a PRACH transmission with preamble repetitions, a time period, starting from frame 0, is the smallest integer number of association pattern periods such that at least one set of valid PRACH occasions for each of the N SS / PBCH block indices can be determined within the time period for all set number of preamble repetitions. SSB Tx SS / PBCH block indexes can be determined within the time period for all configured number of preamble repetitions. The set(s) of valid PRACH occasions for each configured number of preamble repetitions repeat every time period.
[0213] Within the time interval, N rep preamble N for PRACH transmission with dog preamble iterations rep preamble For a set of valid preamble iterations
[0214] The first valid PRACH time of the first set is the first valid PRACH time.
[0215] If any, the first valid PRACH time of the subsequent sets is determined according to the ordering of the valid PRACH times.
[0216] First, in increasing order of frequency resource indices for frequency-multiplexed PRACH periods
[0217] Second, in increasing order of the time resource indices of the time multiplexing PRACH periods
[0218] Here, for each frequency resource index for the frequency-multiplexed PRACH periods
[0219] The first valid PRACH time of the first set is the first valid PRACH time.
[0220] If any, the first valid PRACH time of subsequent sets is
[0221] If the RRC parameter msg1-RepetitionTimeOffsetROGroup is provided, it is msg1-RepetitionTimeOffsetROGroup consecutive valid PRACH periods after the first valid PRACH period of the previous set, where each PRACH period is associated with the same SS / PBCH block index(s) and each SS / PBCH block index is associated with the same preambles.
[0222] If the RRC parameter msg1-RepetitionTimeOffsetROGroup is not provided, it is after the PRACH time of the previous set mentioned above.
[0223] In the case of a PRACH transmission triggered by a request from upper layers, if the RRC parameter csi-ResourceList is provided, the value of the RRC parameter ra-OccasionList indicates a list of PRACH times for the PRACH transmission, wherein the PRACH times are associated with a selected CSI-RS index indicated by the RRC parameter csi-RS. The indexing of the PRACH times indicated by ra-OccasionList is reset for each associated pattern interval.
[0224] For paired spectra (e.g., in the case of frequency division duplex (FDD)) or supplementary uplink bands, all PRACH times are valid. For unpaired spectra (e.g., in the case of time division duplex (TDD)),
[0225] If the UE is not provided with the RRC configuration tdd-UL-DL-ConfigurationCommon for the cell, the PRACH timing for the cell within the PRACH slot does not precede the SS / PBCH block within the PRACH slot, and at least N after the last SS / PBCH block received symbol. gap It is valid if it starts after the dog symbols, where N gapis provided in Table 7, and if the RRC parameter channelAccessMode ="semiStatic" is provided, it does not overlap with the set of consecutive symbols prior to the start of the next channel occupancy time (see 3GPP TS 37.213) that the UE does not transmit (if a UE is not provided RRC configuration tdd-UL-DL-ConfigurationCommon for a cell, a PRACH occasion for the cell in a PRACH slot is valid if it does not precede a SS / PBCH block in the PRACH slot and starts at least N gap symbols after a last SS / PBCH block reception symbol, where N gap is provided in Table 7 and, ifchannelAccessMode= "semiStatic" is provided, does not overlap with a set of consecutive symbols before the start of a next channel occupancy time where the UE does not transmit (see 3GPP TS 37.213)).
[0226] The candidate SS / PBCH block index of the SS / PBCH block corresponds to the SS / PBCH block index provided by ssb-PositionsInBurstin, SIB1 or inServingCellConfigCommon or inSSB-MTC-AdditionalPCI, corresponding to the cell, as described in section 4.1 of 3GPP TS 38.213.
[0227] For each candidate cell configured by LTM-Config, if the UE is not provided with ltm-tdd-UL-DL-ConfigurationCommon, the PRACH timing within the PRACH slot for the candidate cell does not precede the SS / PBCH block within the said PRACH slot, and is at least N from the last SS / PBCH block reception symbol. gap It is valid if it starts after the dog symbols, where N gap It is provided in Table 7.
[0228] The SS / PBCH block index of the SS / PBCH block corresponds to the SS / PBCH block index provided by ssb-PositionsInBurst within LTM-SSB-Config corresponding to the above candidate cell.
[0229] If the UE is provided with tdd-UL-DL-ConfigurationCommon in the cell, the above PRACH time within the PRACH slot is valid in the following cases:
[0230] If it is within the UL symbol, or
[0231] >> It does not precede the SS / PBCH block within the aforementioned PRACH slot, and at least N after the last downlink symbol gap After the dog symbols and after the last SS / PBCH block symbol, at least N gap If you start after the dog symbols, here N gap It is provided in Table 7, and if channelAccessMode = "semiStatic" is provided, it does not overlap with a set of consecutive symbols before the start of the next channel occupancy time, which must not have any transmissions, as described in 3GPP TS 37.213 (it does not precede a SS / PBCH block in the PRACH slot and starts at least N gap symbols after a last downlink symbol and at least N gap symbols after a last SS / PBCH block symbol, where N gap is provided in Table 7, and ifchannelAccessMode= "semiStatic" is provided, does not overlap with a set of consecutive symbols before the start of a next channel occupancy time where there shall not be any transmissions, as described in 3GPP TS 37.213).
[0232] The candidate SS / PBCH block index of the SS / PBCH block corresponds to the SS / PBCH block index provided by ssb-PositionsInBurstin, SIB1 or inServingCellConfigCommon or inSSB-MTC-AdditionalPCI, corresponding to the cell, as described in section 4.1 of 3GPP TS 38.213.
[0233] For each candidate cell configured by LTM-config, if the UE is provided with ltm-tdd-UL-DL-ConfigurationCommon, the PRACH timing within the PRACH slot for the candidate cell is valid in the following cases:
[0234] If it is within the UL symbol, or
[0235] >> It does not precede the SS / PBCH block within the PRACH slot, and at least N from the last DL symbol gap It starts after the last symbols, and at least N from the last SS / PBCH block symbol. gap Starting after the dog symbols. Here, N gap It is provided in Table 7 (it does not precede a SS / PBCH block in the PRACH slot and starts at least N gap symbols after a last downlink symbol and at least N gapsymbols after a last SS / PBCH block symbol, where N gap is provided in Table 7).
[0236] The SS / PBCH block index of the SS / PBCH block corresponds to the SS / PBCH block index provided by ssb-PositionsInBurst within LTM-SSB-Config corresponding to the above candidate cell.
[0237] The following table shows N for different preamble SCS u. gap These are examples of values.
[0238]
[0239] For the preamble format B4 described in 3GPP TS 38.211, N gap = 0.
[0240] When a UE receives a RACH-related setting for CFRA, a system information (SI) request, and / or a beam failure recovery (BFR), etc., it may receive a parameter ra-ssb-OccasionMaskIndex that sets a PRACH mask index (e.g., through said RACH-related setting). Referring to Section 8.1 of 3GPP TS 38.213, for a PRACH transmission triggered by the upper layer(s), if ssb-ResourceList is provided, a PRACH mask index is indicated in ra-ssb-OccasionMaskIndex, which indicates PRACH times for said PRACH transmission, said PRACH times are associated with an SS / PBCH block index selected (by said UE). As described in Section 8.1 of 3GPP TS 38.213, the parameter ra-ssb-OccasionMaskIndex is a parameter that sets the PRACH mask index for a RACH occasion (RO) and is used by the UE to select a resource for random access (RA). It can be applied to all SSB beams (e.g., all SSB resources) used in the cell via ssb-ResourceList and can be set by including in at least one of the following information elements (IE). Here, ssb-ResourceList is a list of SSB resource indices used in the cell.
[0241] BeamFailureRecoveryConfig. IEBBeamFailureRecoveryConfig is used to configure the UE with RACH resources and candidate beams for beam failure recovery in case of beam failure detection.
[0242] IERACH-ConfigDedicated. IERACH-ConfigDedicated is used to specify the dedicated random access parameters.
[0243] >SI-RequestConfig. IESI-RequestConfig contains configuration for Msg1-based SI requests without Msg1 repetition. For arbitrary connection parameters not configured in SI-RequestConfig (e.g., prach-RootSequenceIndex, msg1-SubcarrierSpacing, etc.), unless otherwise specified, the UE applies the parameters configured in the RRC configuration prach-ConfigCommon corresponding to the selected set of RACH resources during the initial RACH initialization of the uplink BWP.
[0244] >SI-RequestConfigRepetition. IESI-RequestConfigRepetition contains configuration for Msg1 based SI request with Msg1 repetition. For arbitrary connection parameters not configured in SI-RequestConfigRepetition (e.g., prach-RootSequenceIndex, msg1-SubcarrierSpacing, msg1-RepetitionTimeOffsetROGroup, etc.), unless otherwise specified, the UE applies the parameters configured in prach-ConfigCommon corresponding to the selected set of RACH resources during the initial uplink BWP RACH initialization.
[0245] If the RACH configuration for the 2-step random access process is referred to as the 2-step RACH configuration, then for the 2-step random access process, a parameter msgA-SSB-SharedRO-MaskIndex that sets the PRACH mask index of the RO within the said 2-step RACH configuration may be provided. The said 2-step RACH configuration may be, for example, RACH-ConfigCommonTwoStepRA, where IERACH-ConfigCommonTwoStepRA is a configuration of cell-specific random access parameters used by the UE for contention-based and contention-free 2-step random access type processes.
[0246] A parameter ssb-SharedRO-MaskIndex may be provided to the UE, indicating a subset of 4-stage random access type ROs shared with 2-stage random access type ROs for each SSB. The parameter ssb-SharedRO-MaskIndex is set only when more than one RO is allocated per SSB, and if this field is absent, it is interpreted that all ROs are shared. The parameter ssb-SharedRO-MaskIndex may be set by including it in at least one of the following IEs.
[0247] >FeatureCombinationPreambles. IEFeatureCombinationPreambles indicates a feature or a combination of features to be associated with a set of random access resources.
[0248] >RACH-ConfigCommonTwoStepRA.
[0249] In some implementations, the UE may dynamically be indicated by one of the PRACH mask indices in Table 7.4-1 of 3GPP TS 38.321 via a 4-bit field in DCI format 1_0, and these parameters (e.g., PRACH mask index) indicate one of the indices in Table 7.4-1 of 3GPP TS 38.321 as an integer value from 0 to 15, and the PRACH timing index is determined by the SSB-to-RO mapping. Referring to 3GPP TS 38.213, for example, PRACH timings are mapped consequentially by the corresponding SS / PBCH block index (also called the SSB index). The indexing of the PRACH occasion indicated by the mask index value is reset per mapping cycle of consecutive PRACH occasions per SS / PBCH block index. The UE selects for a PRACH transmission the PRACH occasion indicated by the PRACH mask index for the SS / PBCH block index indicated by the PDCCH order in the first available mapping cycle.
[0250] For example, the PRACH time index is indexed as described in 3GPP TS 38.213, determined by the parameter ssb-perRACH-Occasion value N, which is related to the number of SSBs mapped per RO. If N is greater than 1, all ROs have the same PRACH time index, and if N is less than 1, N PRACH time indices mapped to the same SSB index in the frequency domain can be indexed sequentially starting from the lowest frequency RO.
[0251] The following table is Table 7.4-1 of 3GPP TS 38.321 and illustrates PRACH mask index values. Referring to the following table, as an example of how a PRACH mask index is set / indicated, if the PRACH mask index value (PIV) = 0, it indicates that the RO for all PRACH occasion indexes (POI) is available; if PIV = 1 to PIV = 8, it means that one of the ROs among POIs 1 to 8 is available depending on the PIV value; if PIV = 9, it means that the ROs for even POIs are available; and if PIV = 10, it means that the ROs for odd POIs are available. The UE can perform RA by selecting an available RO within the first (available) mapping cycle after receiving the PIV.
[0252]
[0253] Below, physical channels that can be used in 3GPP-based wireless communication systems are described in more detail.
[0254] 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).
[0255] 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.
[0256] 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.
[0257] 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.
[0258] 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.
[0259] 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.
[0260] 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).
[0261] 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.
[0262] 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.
[0263] A control resource set (CORESET), which is a set of time-frequency resources that allows the UE to monitor 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. A set of PDCCH candidates may 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 (also known as blind decoding) each PDCCH candidate according to the monitored DCI formats. For example, the following DCI formats may be supported.
[0264]
[0265] The master information block (MIB) on the PBCH provides the UE with parameters (e.g., setting CORESET#0) for monitoring the PDCCH to schedule the PDSCH carrying the system information block 1 (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 SIB1, 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 the MIB or dedicated RRC signaling.
[0266] One or more CORESETs can be configured for the UE, and multiple CORESETs can overlap in the time / frequency domain.
[0267] 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.
[0268] 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.
[0269] -searchSpaceId: Represents the ID of the SS set.
[0270] -controlResourceSetId: Represents the CORESET associated with the SS set.
[0271] -monitoringSlotPeriodicityAndOffset: Represents the PDCCH monitoring period interval (in slots) and the PDCCH monitoring interval offset (in slots).
[0272] -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.
[0273] -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).
[0274] -searchSpaceType: Indicates whether the SS type is CSS or USS.
[0275] - DCI Format: Indicates the DCI format of the PDCCH candidate.
[0276] 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.
[0277] The UE can detect a PDCCH in slot n. Subsequently, the UE can receive a PDSCH in slot n+K0 according to the scheduling information received via the PDCCH in slot n, and then transmit a UCI via a PUCCH in slot n+K1. Here, the UCI includes a HARQ-ACK response to the PDSCH. In some scenarios, PUCCH feedback based on a slot consisting of 14 OFDM symbols may be performed, as well as PUCCH feedback based on a subslot consisting of fewer than 14 OFDM symbols (e.g., 2 to 7).
[0278] The DCI carried by the PDCCH scheduling the PDSCH (e.g., DCI format 1_0, DCI format 1_1) may contain the following information.
[0279] - Frequency Domain Resource Assignment (FDRA): Represents the set of RBs assigned to PDSCH.
[0280] - Time Domain Resource Assignment (TDRA): Indicates the DL assignment-to-PDSCH slot offset K0, the starting position (e.g., symbol index S) and length (e.g., number of symbols L) of the PDSCH within the slot, and the PDSCH mapping type. PDSCH mapping type A or PDSCH mapping type B may be specified by TDRA. For PDSCH mapping type A, the DMRS is located at the third symbol (symbol #2) or fourth symbol (symbol #3) in the slot. For PDSCH mapping type B, the DMRS is located at the first symbol allocated for the PDSCH.
[0281] - PDSCH-to-HARQ_feedback timing indicator: Represents K1.
[0282] If the PDSCH is configured to transmit up to 1 TB, the HARQ-ACK response may consist of 1 bit. If the PDSCH is configured to transmit up to 2 transport blocks (TB), the HARQ-ACK response may consist of 2 bits if spatial bundling is not configured, and 1 bit if spatial bundling is configured. If the time for transmitting HARQ-ACKs for multiple PDSCHs is specified as slot n+K1, the UCI transmitted in slot n+K1 includes HARQ-ACK responses for multiple PDSCHs.
[0283] PUCCH refers to a physical layer UL channel for UCI transmission. PUCCH carries uplink control information (UCI). The UCI types transmitted in PUCCH may include hybrid automatic repeat request (HARQ)-acknowledgement (ACK) information, scheduling request (SR), link recovery request (LRR), and channel state information (CSI). UCI bits include HARQ-ACK information bits, SR information bits, LRR information bits, and CSI bits, if present. In this specification, the HARQ-ACK information bits correspond to the HARQ-ACK codebook. In particular, a bit sequence in which HARQ-ACK information bits are arranged according to a defined rule is referred to as the HARQ-ACK codebook.
[0284] New service types are emerging, such as Extended Reality (XR), artificial intelligence-based services, and self-driving cars. These services are characterized by dynamic traffic in both DL and UL directions and require low latency for packet transmission. In 6G services, traffic load is expected to increase explosively to support these diverse new use cases. Conversely, existing semi-static or dynamic TDD UL / DL configurations face limitations in terms of transmission time delays and interference issues between operators. The existing Frequency Division Duplex (FDD) method has limitations in terms of efficient frequency resource utilization for the DL / UL direction. Therefore, the introduction of full duplex operation within a single carrier is being discussed to achieve low latency and efficient resource utilization.
[0285] In the case of full duplex, the device can perform transmission and reception simultaneously whenever necessary. For example, a full duplex UE can perform uplink transmission and downlink reception simultaneously, and a full duplex BS can perform uplink reception and downlink transmission simultaneously.
[0286] Figure 12 shows examples of applying full duplex within the carrier. As examples of methods for applying full duplex within the carrier, subband-wise full duplex (SBFD) and spectrum-sharing full duplex (SSFD) can be considered, as illustrated in Figure 12. In the case of SBFD, DL transmission / reception and UL reception / transmission can be performed through different frequency resources on the same carrier. For example, in the case of SBFD, DL and UL can have different frequency resources for the same time resource. In some implementations, SBFD may mean subband non-overlapping full duplex, where subbands within the same symbol do not overlap each other. In the case of SSFD, transmission / reception of DL and UL can be performed through frequency resources that overlap with the same frequency resources or some of the total frequency resources on the same carrier. For example, in the case of SSFD, DL and UL may have the same or overlapping frequency resources for the same time resources.
[0287] This full duplex operation can be used in combination with existing half duplex (HD) operation. In the case of half duplex, the UE or BS cannot simultaneously transmit and receive in the paired spectrum. In existing half duplex-based TDD operations, some time resources may be used for full duplex operation. SBFD or SSFD operations may be performed on the time resources used for full duplex operation.
[0288] 5G standard documents (e.g., Section 11.1 of 3GPP TS 38.213) describe operations related to half duplex (HD). Some of the HD-related operations described in the 5G standard documents are as follows. The general concept of HD-related operations described in the 5G standard documents can be extended to full duplex-related operations according to some implementations of this specification to be described later. Referring to 3GPP TS 38.213, regarding slot configuration, the slot format may include downlink symbols, uplink symbols, and fluid symbols. The following is applicable to each serving cell. When a UE is provided with tdd-UL-DL-ConfigurationCommon, the UE sets the slot-specific slot format for the number of slots specified by tdd-UL-DL-ConfigurationCommon. The tdd-UL-DL-ConfigurationCommon is i) reference SCS configuration u by referenceSubcarrierSpacing ref and ii) provide pattern1. The pattern1 provides the following:
[0289] a slot configuration period of P msec by dl-UL-TransmissionPeriodicity
[0290] The number of slots containing only downlink symbols, d, determined by -nrofDownlinkSlots slot (a number of slots d slot with only downlink symbols bynrofDownlinkSlots)
[0291] The number of downlink symbols d by -nrofDownlinkSymbols sym (a number of downlink symbols d symbynrofDownlinkSymbols)
[0292] -nrofUplinkSlots, the number of slots containing only uplink symbols u slot (a number of slots u slot with only uplink symbols bynrofUplinkSlots)
[0293] The number of uplink symbols u by -nrofUplinkSymbols sym (a number of uplink symbols u sym bynrofUplinkSymbols)
[0294] The value P = 0.625 msec is valid only for u_ref = 3, u_ref = 5, or u_ref = 6. The value P = 1.25 msec is valid only for u_ref = 2, u_ref = 3, u_ref = 5, or u_ref = 6. The value P = 2.5 msec is valid only for u_ref = 1, u_ref = 2, u_ref = 3, u_ref = 5, or u_ref = 6. The value P = 10 msec is valid only for u_ref = 0, u_ref = 1, u_ref = 2, u_ref = 3, or u_ref = 5. The slot setting interval of P msec is S = P*2, which is the SCS setting u_ref. u_ref Includes slots. Starting from the S slots, the first d slot The slots contain only downlink symbols, and the last u slot The slots contain only uplink symbols. The first d above slot Dog slots slots after d sym The dog symbols are downward leak symbols. The last u mentioned above slot Dog slots after u sym The dog symbols are uplink symbols. The remaining (S - d slot - u slot )*N slot symb- d sym - u sym These are fluid symbols. The first symbol of every 20 / P period is the first symbol within an even frame.
[0295] If tdd-UL-DL-ConfigurationCommon provides both pattern1 and pattern2, the UE sets a slot-by-slot format for a first number of slots specified by pattern1 and sets a slot-by-slot format for a second number of slots specified by pattern2. The pattern2 provides the following:
[0296] a slot configuration period of P2msec by dl-UL-TransmissionPeriodicity
[0297] The number of slots containing only downlink symbols, d, determined by -nrofDownlinkSlots slot,2 (a number of slots d slot,2 with only downlink symbols bynrofDownlinkSlots)
[0298] The number of downlink symbols d by -nrofDownlinkSymbols sym,2 (a number of downlink symbols d sym,2 bynrofDownlinkSymbols)
[0299] -nrofUplinkSlots, the number of slots containing only uplink symbols u slot,2 (a number of slots u slot,2 with only uplink symbols bynrofUplinkSlots)
[0300] The number of uplink symbols u by -nrofUplinkSymbols sym,2(a number of uplink symbols u sym,2 bynrofUplinkSymbols)
[0301] The applicable values for P2 are the same as the applicable values for P. The slot setting interval of P+P2 msec is S = P*2 u_ref 1st slots (first S = P*2 u_ref slots) and S2 = P2*2 u_ref 2nd slots (second S2 = P2*2 u_ref Includes slots). Starting from the above S2 slots, the first d slot,2 The slots contain only downlink symbols, and the last u slot,2 The slots contain only uplink symbols. The first d above slot,2 Dog slots slots after d sym,2 The dog symbols are downward leak symbols. The last u mentioned above slot,2 Dog slots after u sym,2 The dog symbols are uplink symbols. The remaining (S2- d slot,2 - u slot,2 )*N slot symb - d sym,2 - u sym,2 These are fluid symbols. A UE expects that P+P2 divides 20 msec. The first symbol of every 20 / (P+P2) period is the first symbol in an even frame.
[0302] The UE expects that the above reference SCS setting u_ref is less than or equal to the SCS setting u for any configured DL BWP or UL BWP. Each slot provided by pattern1 or pattern2 is 2 within an active DL BWP or active UL BWP. (u-u_ref)It is applicable to consecutive slots, wherein the first slot starts at the same time as the first slot for the reference SCS setting u_ref, and each downlink, fluid, or uplink symbol for the reference SCS setting u_ref is 2 for the SCS setting u (u-u_ref) Corresponds to consecutive downlink, fluid, or uplink symbols.
[0303] If the above UE is additionally provided with tdd-UL-DL-ConfigurationDedicated, the parameter tdd-UL-DL-ConfigurationDedicated overrides only the fluid symbols per slot for the number of slots provided by tdd-UL-DL-ConfigurationCommon.
[0304] FIG. 13 illustrates an example where time resources operating in half duplex (HD) and time resources operating in full duplex (FD), such as SBFD or SSFD, coexist. In the time resources where HD operation is performed, DL operation or UL operation is performed on frequency resources that constitute the entire system bandwidth (or entire BWP). The time resources where the UE or network (e.g., BS) performs DL operation and the time resources where the UL operation is performed do not overlap. For the time resources where the UE or network (e.g., BS) performs FD operation, the network performs DL operation through a DL subband that occupies the entire or a portion of the entire frequency resources among the frequency resources constituting the cell's system bandwidth (or entire BWP), or through frequency resources included in both the DL subband and the active DL BWP, and performs UL operation through a UL subband that occupies the entire or a portion of the entire frequency resources among the frequency resources constituting the cell's system bandwidth (or entire BWP), or through frequency resources included in both the UL subband and the active UL BWP. For example, referring to FIG. 13(a), some time resources may operate as SBFD and the remaining time resources may operate as HD. As another example, referring to FIG. 13(b), some time resources may operate as SSFD and the remaining time resources may operate as HD. In this case, for the time resources of the SSFD slot / symbol, the frequency resources operating as DL are set by the total system bandwidth (or total BWP) resources, and the frequency resources operating as UL may be set by the UL subband resources that occupy a portion of the total among the frequency resources constituting the cell's system bandwidth (or total BWP).
[0305] In time resources operating as SBFD, some frequency resources are used as DL resources, and some frequency resources are used as UL resources. Between the DL frequency resources and the UL frequency resources, there may exist a guard band (or guard frequency resource or guard subcarrier(s)) that is left empty and unused for both DL and UL. In time resources operating as SSFD, the entire frequency resource may be used for both DL and UL. Alternatively, to reduce the effects of interference from other adjacent carriers (e.g., adjacent carrier interference (ACI)), some frequency resources at one or both ends of the carrier may not be used for DL and / or UL. For example, one or both ends of the carrier may be used as a guard band that is not used for both DL and UL. Alternatively, to reduce ACI affecting UL reception, one or both ends of the carrier may be used for DL transmission only.
[0306] In this specification, slot / symbol resources operating in HD are referred to as HD slots / symbols, and slot / symbol resources operating in SBFD and SSFD are referred to as SBFD slots / symbols and SSFD slots / symbols, respectively. Additionally, SBFD slots / symbols and SSFD slots / symbols are collectively referred to as FD slots / symbols. In time resources configured as HD slots / symbols, the UE may perform DL reception using the entire frequency resources configured to operate in DL. Alternatively, in time resources configured as HD slots / symbols, the UE may perform UL transmission using the entire frequency resources configured to operate in UL. In this specification, in time resources operating in FD, the UE may perform DL reception or UL transmission using only some of the frequency resources among the entire frequency resources constituting the DL BWP or UL BWP. In this case, the frequency resources among the entire frequency resources that operate in DL are referred to as DL subbands, and in time resources operating in FD, the frequency resources among the entire frequency resources that operate in UL are referred to as UL subbands. For time resources where SBFD slot / symbol and / or SSFD slot / symbol are configured, the UE performs DL reception through DL subband frequency resources that are more limited than the frequency resources where the UE performs DL reception in HD slot / symbol time resources. For time resources where SBFD slot / symbol and / or SSFD slot / symbol are configured, the UE performs UL transmission through UL subband frequency resources that are more limited than the frequency resources where the UE performs UL transmission in HD slot / symbol time resources. For example, DL operation may be performed through frequency resources included in both the DL subband and the active DL BWP, and UL operation may be performed through frequency resources included in both the UL subband and the active UL BWP. In this case, additionally, even if the UE is configured to perform DL reception with a frequency resource that does not correspond to the DL subband, it may not perform DL reception on the frequency resources that do not correspond to the DL subband.Even if the UE is configured to transmit to a frequency resource that does not correspond to the UL subband, it may not transmit to the frequency resource that does not correspond to the UL subband.
[0307] In the case of full duplex operation as described above, full duplex operation can be performed from both the perspective of the BS and the relationship with the UE. For example, both the BS and the UE can simultaneously perform the transmission / reception of DL and UL using the same or different frequency resources within the same time resource. On the other hand, only the BS may perform full duplex operation, while the UE may perform semi-duplex operation. For example, the BS may simultaneously perform the transmission / reception of DL and UL using the same or different frequency resources within the same time resource, but the UE performs only DL reception or UL transmission within a specific time resource. In this case, the BS can perform full duplex operation by performing DL transmission and UL reception for different UEs at the same time.
[0308] Some implementations of the present specification described below are described based on NR, but can be extended to 6G. In some implementations of the present specification described below, it is assumed that a slot or symbol can be extended to a unit related to a slot, a symbol, or a time interval (wherein the time interval may be set in slot and / or symbol units) or a time interval set periodically and / or based on a predefined pattern.
[0309] In 5G NR, UEs receive UL / DL resource configurations for a specific cell from the BS. The BS provides information on whether the frequency resources of a specific time resource are used for DL or UL, and this information can be transmitted via semi-static configuration. TDD slot / symbol configuration can be achieved through the following two operations. In the first operation, all UEs in the cell receive cell-specific DL / UL patterns via tdd-UL-DL-ConfigurationCommon. In the second operation, all or part of the time resources remaining as flexible (F) slots / symbols are configured specifically for UEs via the dedicated RRC signal tdd-UL-DL-ConfigurationDedicated. tdd-UL-DL-ConfigurationCommon can be transmitted via SIB1 or dedicated RRC signaling. It can be determined to be a dynamic slot / symbol only if both UE- and cell-specific slot settings are configured to be dynamic. Since tdd-UL-DL-ConfigurationDedicated is optional, the network is not obligated to perform the second operation, and in this case, the DL / UP pattern configured by tdd-UL-DL-ConfigurationCommon is used. Additionally, for time resources configured as F by the above-mentioned semi-static settings, they can be used as a DL or UL through dynamic scheduling via DL assignment / UL grant or slot format indication via DCI format 2_0. If SlotFormatIndicator is configured, an additional DL / UL pattern is indicated based on the slot format indication information included in DCI format 2_0.At this time, if the UE does not receive the SlotFormatIndicator, the UE may receive PDSCH or CSI-RS in some / all symbols of the slot according to the instructions of DCI format 1_0, DCI format 1_1, and DCI format 0_1. If the UE does not receive the SlotFormatIndicator, the UE may transmit PUSCH, PUCCH, PRACH, and SRS in some / all symbols of the slot according to the instructions of DCI format 0_0, DCI format 0_1, DCI format 1_0, DCI format 1_1, and DCI format 2_3.
[0310] In a TDD environment based on semi-static or dynamic configuration / instruction, various symbol types may be supported for SBFD operations depending on the time resource. These include DL symbols where DL can be performed across the entire frequency resource band, UL symbols where UL can be performed across the entire frequency resource band, dynamic symbols (e.g., F symbols) where DL or UL can be performed across the entire frequency resource band, and SBFD symbols where DL or UL can be performed on a subband that is part of the entire frequency resource. Furthermore, if SSFD operations are supported in the TDD environment, there may be SSFD symbols where DL and UL can be performed across the entire frequency resource, SSFD symbols where DL and UL can be performed on a subband that is part of the entire frequency resource, SSFD symbols where DL can be performed across the entire frequency resource and UL can be performed on a subband, and SSFD symbols where UL can be performed across the entire frequency resource and DL can be performed on a subband. In some implementations, when viewing SBFD and SSFD from the perspectives of BS and UE, specific symbol types may support the following operations. In the case of SBFD, from the BS perspective, flexible symbols are resources capable of DL transmission or UL reception across the entire frequency band, and SBFD symbols are resources capable of simultaneous DL transmission and UL reception within each subband (or carrier, including cases where the subband is composed of a carrier). From the HD UE perspective, flexible symbols are resources capable of DL reception or UL transmission across the entire frequency band, and SBFD symbols are resources capable of DL reception or UL transmission within a subband (or carrier). From the FD UE perspective, flexible symbols are resources capable of DL reception or UL transmission across the entire frequency band, and SBFD symbols are resources capable of simultaneous DL reception and UL transmission within a subband (or carrier).In the case of SSFD, from the BS perspective, flexible symbols are resources that can perform DL transmission or UL reception across the entire band, and FD symbols are resources that can perform DL transmission and UL reception simultaneously within a given frequency resource. From the HD UE perspective, flexible symbols and FD symbols are resources that can perform DL reception or UL transmission across the entire frequency resource. From the FD UE perspective, flexible symbols are resources that can perform DL reception or UL transmission across the entire frequency band, and FD symbols are resources that can perform DL reception and UL transmission within a given frequency resource (the entire frequency resource or a subband that is a part of the entire frequency resource).
[0311] Some implementations of this specification are generally described under the assumption that the BS performs full duplex operations and the UE performs half duplex operations. However, implementations of this specification may also apply even when both the BS and the UE perform full duplex operations.
[0312] In future wireless access technology (e.g., 6G) environments, semi-static TDD, dynamic TDD, HD-TDD, semi-static SBFD, dynamic SBFD, and SSFD (if further extensible) may be supported. In recent NR, a new symbol type called SBFD symbol, intended exclusively for SBFD-aware UEs, has been added to the existing resource configurations classified as D / F / U. As a result, TDD configurations and SBFD time resource configurations can exist independently. For example, a resource configuration (e.g., SBFD time resource configuration) may be provided to configure / indicate SBFD symbols to symbol resources that are not designated as UL by the RRC configuration TDD-UL-DL-ConfigCommon. Symbols that are not configured as SBFD symbols by the SBFD time resource configuration may be determined to be non-SBFD symbols. In contrast, since SBFD may be introduced from the outset in future wireless access technologies (e.g., 6G), the introduction of resource configurations that can configure / instruct TDD and SBFD (and SSFD) together from the outset may be considered. When DL / UL resource configurations are configured semi-statically, a unified UL / DL resource configuration applicable to the various duplex operations mentioned in this specification may be considered based on time resource configuration information, subband frequency resource information according to the time resource, and link direction information per subband according to the time resource. Some implementations of this specification are described below in which the BS configures / instructs the UE with the information so that the UE can determine the location of the time resource operating as HD and / or FD, the location information of the frequency resource of the said time resource, and the link direction of each subband constituting the frequency resource of the said time resource.
[0313] In some implementations of this specification, a duplex structure operating per time resource can be configured / instructed using a frequency resource type, wherein the frequency resource type can be configured as one or more frequency resources. For each frequency resource for the said frequency resource type, the resource type can be configured / instructed to be the same or different from one another, and accordingly, a duplex mode per time resource can be determined.
[0314] In some implementations of this specification, a duplex structure is assumed to operate based on frequency resources according to time resources set by BS. In some implementations, the frequency resources may consist of one or more frequency resources S subband(s), and each subband constituting the frequency resources may be set / instructed with the same or different resource types.
[0315] FIG. 14 is a diagram illustrating frequency resource types according to some implementations of the present specification. As illustrated in FIG. 14, in some implementations of the present specification, a resource type may mean resource usage information for a single frequency resource (e.g., D, U, F, or X, etc.), and a frequency resource type may mean a combination of S resource types for S frequency resources, where S is an integer greater than 1. In the present specification, a resource type may mean a (wireless) link type. Resource usage information (D, U, F, or X, etc.) will be described in more detail later (see Section 1.1). For example, referring to FIG. 14, when a frequency resource type is configured for a specific cell / carrier, the frequency resource type may mean resource type information per frequency resource when the frequency resources forming the cell / carrier are divided into S frequency resources (e.g., S subbands). When a frequency resource type is configured for multiple carriers, the frequency resource type may refer to resource type information for each frequency resource when the total frequency resource formed by the multiple carriers is divided into S (sub)frequency resources. For example, when a frequency resource type is configured for S carriers, frequency resource type information may be provided that includes information regarding S resource types corresponding one-to-one to the S carriers. In some implementations, the frequency resource constituting a single carrier may be divided into multiple subbands, and link (direction) information may be configured for each subband. In some implementations, when a cell is composed of resources from multiple carriers, each carrier may be configured as each subband. In this case, the frequency resource constituting a single cell is divided into multiple carriers, and link (direction) information may be configured for each carrier. At this time, the carrier(s) constituting the cell may be a carrier group in which all or part of the carriers are selected from among the multiple carriers.For specific frequency resources such as cells, carriers, and carrier groups, the UE can receive resource setting information applied to the corresponding frequency resources from the BS. This resource setting may include information regarding the frequency resource types applied per time resource. Based on this, the UE can determine the frequency resource types applied to the corresponding time resources for each time resource. For specific frequency resources such as cells, carriers, and carrier groups, the BS can determine the resource settings applied to the corresponding frequency resources and set information regarding this to the UE. The BS can perform transmission / reception operations with the corresponding UE(s) assuming that the UE can determine the frequency resource types applied to the corresponding time resources for each time resource based on the set information.
[0316] For convenience, the term "subband" is used as a representative term in the following description to denote the unit of frequency resources used to configure a single frequency resource type. A subband is a region of resources in the frequency domain that does not overlap with one another, and the subbands configuring a single frequency resource type may be arranged contiguously or have discontinuous relative positions relative to one another. The methods / implementations described in this specification are not limited in their application by the term "subband" and may be applied to various units of frequency resources expressed by other terms. A frequency resource type may be configured for one or more cells, even if not depicted in the drawings(s). Even if described as a subband for convenience, the methods / implementations of this specification may be applied to various frequency units. A frequency resource type may be configured by one or more BWPs, even if not depicted in the drawings(s). In some methods / implements of this specification, the frequency resource type may be set by one or more usable PRBs (e.g., the area where the subband and the initial / active BWP intersect).
[0317] One method of setting / indicating frequency resource types is to set / indicate the resource type applied to each given subband when the location and length of each subband are set / indicated separately, for example, when the frequency starting point (e.g., starting RB) and the length of the frequency domain of each subband are given by a TDD setting. Another method is to set a TDD setting that allows the resource type to be set / indicated simultaneously while the location and length of the frequency domain of each subband constituting the frequency resource type are set / indicated.
[0318] Although not directly illustrated in FIG. 14, when a frequency resource type is set by multiple carriers, the carriers on which the frequency resource type is set may not be consecutive in the frequency axis. Even if the boundaries of the multiple carriers are not aligned in the frequency axis, the frequency resource type may be set / indicated according to some implementations of this specification.
[0319] <1. Frequency resource configuration to support different duplex features>
[0320] <1.1. Subband-wise Resource Configuration Method>
[0321] In some methods / implements of this specification, information on frequency resource types within a single frequency resource type, e.g., resource types for each subband, may be set / indicated. The UE may receive frequency resource type information, e.g., setting information for resource types for each subband, from the BS. The BS may determine frequency resource type information, e.g., setting for resource types for each subband, for the frequency resource area where the frequency resource type is set, and set / provide such information to the UE. In this case, the frequency resource type information may include information on resource types applied to each subband area for multiple subband areas. Different / independent resource types may be set for each subband area. In some implementations, resource types may include the following D, U, F, X, and N.
[0322] DL or D: A resource type (RT) in which downlink transmission / reception operations can be performed during a specific time unit.
[0323] UL or U: A resource type in which uplink transmission / reception operations can be performed during a specific time unit.
[0324] Flexible or F: A resource type in which downlink transmission / reception or uplink transmission / reception operations can be performed during a specific time unit.
[0325] X: A resource type in which downlink transmission / reception and uplink transmission / reception operations can occur simultaneously during a specific time unit.
[0326] N: A resource type where no transmission or reception operations are performed in any direction during a specific time unit. If a guard band is not defined or configured, N can be configured or instructed to take the place of the guard band.
[0327] In some implementations of this specification, resource types are not limited to DL and / or UL transmission / reception operations and may also be applied to transmission and reception point (TRP) / beam transmission / reception operations.
[0328] For the configuration of such resources, in some implementations of this specification, information regarding the frequency resource type applied per time resource may be provided, wherein the time resource may correspond to a symbol, a slot, or a time interval signifying a specific duration. In some implementations, such time intervals may be configured in slot and / or symbol units. The time resource may include periodic (or predefined) patterns, etc.
[0329] FIG. 15 illustrates frequency resource types for different time resources. Referring to FIG. 15, for example, when S = 3 and multiple frequency resource types exist, a specific frequency resource type may be applied to a specific time resource. In this case, different frequency resource types may be applied to different time resources. To apply different frequency resource types to different time resources, the following methods may be considered.
[0330] First method: Frequency resource type patterns applied per time resource may be provided. Frequency resource type patterns that set / indicate frequency resource type information for resources consisting of one or more subbands / carriers may be set / indicated, and time resource information to which the pattern applies may be indicated. If multiple frequency resource type patterns are set / indicated, time resource information corresponding to each frequency resource type pattern may be provided through separate parameters. A time resource may refer to a time interval set by a symbol(s), slot(s), or a combination of symbols and slots by a higher layer (e.g., RRC) signaling in a semi-static manner. Such time intervals may be defined / set periodically or based on a predefined pattern. A given frequency resource type pattern is maintained during a given time interval unless additional settings / indications are made. A frequency resource type pattern for a specific time resource may be dynamically indicated. For example, a field related to the frequency resource type pattern may be included within a MAC control element (CE) or DCI format. Fields related to time domain resource allocation within the MAC CE or DCI format may indicate resource settings regarding frequency resource type patterns for a specific time interval.
[0331] Second method: TDD settings can be provided for each subband (or carrier). Assuming there is a resource consisting of one or more subbands / carriers, resource type information regarding the time resource applied to each subband / carrier can be configured / instructed.
[0332] As described above, when settings and instructions regarding frequency resource types according to time resources are used, the UE can receive related settings / instructions information from the BS and expect that frequency resource types for each time resource will be applied based thereon, and the BS can determine frequency resource types for each time resource and perform signaling to set / instruct information about them to the UE.
[0333] <1.2. Method for Changing / Switching Frequency Resource Types>
[0334] In some implementations of this specification, change / switching of resource configuration information for each subband may be performed. To this end, the BS may determine the change / switching of resource configuration for each subband and set it for the UE, and the UE may receive the change / switching information for resource configuration information for each subband from the BS. In this case, through this change information of resource configuration information, the frequency resource type applied to a specific time resource may be changed to a different frequency resource type. In some implementations, the frequency resource type being changed may have the following characteristics.
[0335] If a specific subband has a resource type of D or U, the changing frequency resource type has the same resource type for that subband.
[0336] When SBFD is supported, some resource types of D can be changed to resource types of U.
[0337] For example, if the frequency resource type is (DFD), resource type D can be set / indicated as the same resource type as resource type D in other time resources. This takes into account the frequency resource type of SBFD introduced in existing NR, and can reduce signaling overhead associated with switching unnecessary resource types.
[0338] If a specific subband has a resource type of F, the changing frequency resource type may have a resource type of D or U for that subband.
[0339] When two or more subbands, not all of them, are composed of resource type F, the frequency resource type that changes with respect to resource type F can be resource type D or U, and in this case, all subbands whose resource type changes from resource type F can be changed to the same resource type.
[0340] For example, the fact that F needs to be changed to a resource type of D or U may mean that there is a special environment or situation during the corresponding time resource interval, such as when more DL information is transmitted / received or more UL information is received / transmitted from the perspective of BS / UE.
[0341] If a specific subband has a resource type of X, the changing frequency resource type may have a resource type of D, U, or F in that subband.
[0342] If all subbands have a resource type of F, the changing frequency resource type can be set to a resource type of D or U for all subbands, and the same resource type can be set for all subbands.
[0343] For example, the fact that F needs to be changed to a resource type of D or U may mean that there is a special environment or situation during the corresponding time resource interval, such as when more DL information is transmitted / received or more UL information is received / transmitted from the perspective of BS / UE.
[0344] This may apply in cases where a fluid symbol is changed to a DL symbol or UL symbol in 5G.
[0345] If all subbands have a resource type of F, the frequency resource type to be changed may be a frequency resource type that sets a resource type of D or U for at least one subband.
[0346] This is a case where, if a frequency resource type with high flexibility is supported in a 6G environment, it is changed to a mixed resource.
[0347] Additionally, in some implementations of this specification, when resource configuration is provided, specific combinations of frequency resource types may be supported by considering the switching of resource types as described above. For example,
[0348] - (RT1... RT S When frequency resource types are composed of S (where S is 2 or more) sub-frequency resource types, and different resource types are applied to different sub-frequency resources, at least one resource type must be D. This is because it may be considered to design the 6G frame structure based on a structure that applies SBFD to D / F symbols in TDD settings.
[0349] - (RT1... RT S When frequency resource types are composed of S (where S is 2 or more) sub-frequency resource types, such as ), and D and U / X / F resources exist together, UL is located in only one sub-frequency resource. This is because expansion to 6G can be considered based on applying SBFD when more opportunities for UL transmission are needed.
[0350] - (RT1... RT SWhen a frequency resource type is composed of S (where S is 2 or more) sub-frequency resource types, such as (XDD), (DFD), and (DDU), to prevent the combined use of frequency resource types such as (XDD), (DFD), and (DDU), if two or more types exist together in frequency resource type A and frequency resource type B, the position of the resource D in pattern A and pattern B is the same. This allows for the exclusion of unnecessary frequency resource type patterns when considering the change / switching of X and F, thereby reducing signaling overhead related to frequency resource types.
[0351] - (RT1... RT S When frequency resource types are composed of S (where S is 2 or more) sub-frequency resource types, and different types are applied to different sub-frequency resources, if multiple Fs are included, they are changed / switched in the same transmission direction. For example, all Fs can be changed / switched to D, or all Fs can be changed / switched to U.
[0352] - (RT1... RT S When frequency resource types are composed of S (where S is 2 or more) sub-frequency resource types, and different types are applied to different sub-frequency resources, if multiple Xs are included, they are changed / switched in the same transmission direction. For example, all Xs may be changed / switched to F, all Xs may be changed / switched to D, or all Xs may be changed / switched to U.
[0353] Some of the rules or limitations given in this specification assume that the SBFD operation proposed in NR is included in the 6G duplex operation, thereby reducing unnecessary flexibility in setting frequency resource types, which can reduce signaling overhead and reflect a realistic BS implementation.
[0354] <1.3. Behavior of BS and UE Based on Configured / Instructed Resource Configuration Information>
[0355] The UE can determine the resource type applied to each subband area in the specific time resource based on information regarding the frequency resource type applied to the specific time resource.
[0356] BS can perform DL transmission within a resource determined as D or UL reception within a resource determined as U. In a resource determined as F, DL transmission or UL reception can be performed. If SBFD is supported, UL reception on the UL subband and UL transmission on the DL subband can be performed simultaneously. DL transmission and UL reception can be performed simultaneously within a resource determined as X.
[0357] When the UE operates in semi-duplex mode, it may perform DL reception within a subband resource determined to be D, F, or X, or perform UL transmission within a subband resource determined to be U, F, or X.
[0358] The UE cannot perform UL reception on a subband resource determined to be D or DL reception on a subband resource determined to be U.
[0359] FIGS. 16 and 17 illustrate frequency resource types according to some implementations of the present specification. For example, in FIGS. 16 and 17, (RT1... RT S ) is a notation used to simply indicate the type of each frequency resource when S frequency resources (e.g., S = 3) are set.
[0360] In FIG. 16, (DDD), (UUU), and (FFF) are examples of frequency resource types based on TDD supported by NR. (DDD) may represent a DL symbol that can perform DL across the entire band, where the BS can perform DL transmission and the UE can perform DL reception. (UUU) may represent a UL symbol that can perform UL across the entire band, where the BS can perform UL reception and the UE can perform UL transmission. (FFF) may represent a flexible symbol (e.g., F symbol) that can perform DL or UL across the entire band, where the BS can set / instruct DL or UL transmission through UE-specific signaling, scheduling DCI and / or dedicated DCI (e.g., group common DCI), and the UE can perform DL reception or UL transmission in accordance with the transmission direction set / instructed based on the BS's signaling.
[0361] In Fig. 16, (DUD) and (DDU) are examples of frequency resource types based on SBFD supported by NR. The resource type for some resource areas can be switched via RRC signaling (e.g., common / UE-specific TDD configuration), UE-specific signaling, and / or dedicated / scheduled DCI. For example, a BS supporting SBFD can switch DDD to DUD if it needs to increase the amount of UL transmission. Alternatively, the BS can switch DUD to DDD if immediate DL transmission is required, or if it wants to block UL transmission in another subband when SSB transmission occurs. For frequency resource types configured / directed as (DUD), (DDU), or (UDD), the BS can perform DL transmission on the DL frequency resource and simultaneously perform UL reception on the UL frequency resource. The HD UE can perform DL reception within the DL frequency resource or perform UL transmission within the UL frequency resource. When operating in full duplex mode, the FD UE can perform DL reception within the DL frequency resources and simultaneously perform UL transmission within the UL frequency resources. When operating in fallback mode, the FD UE can perform DL reception within the DL frequency resources or perform UL transmission within the UL frequency resources.
[0362] In FIG. 17, (DFD) and (DDF) are frequency resource types that support dynamic SBFD, which considers switching operations to SBFD and DL symbols depending on whether F operates as UL or DL. For example, if the frequency resource F in the frequency resource type (DFD) and the frequency resource type (DDF) is set / instructed to change to UL through signaling such as UE-specific signaling or scheduling DCI, it can be changed respectively to the frequency resource type (DUD) and the frequency resource type (DDU). For example, if F is set / instructed to DL through signaling such as UE-specific signaling or scheduling DCI, it may mean the DL symbol set as (DDD).
[0363] For frequency resource types configured / directed as (DFD), (DDF), or (FDD), the BS can perform DL transmission on the DL frequency resource and simultaneously perform UL reception on the UL frequency resource. The BS can direct DL or UL transmission for the F frequency resource through UE-specific signaling DCI, scheduling DCI, and / or dedicated DCI (e.g., group-common DCI). The HD UE can perform DL reception within the DL frequency resource or UL transmission within the UL frequency resource. The HD UE can perform DL reception or UL transmission in accordance with the transmission direction configured / directed based on the BS's signaling. The HD UE can perform DL reception or UL transmission in accordance with the transmission direction configured / directed based on the BS's signaling on the F frequency resource. When operating in full duplex mode, the FD UE can perform DL reception within the DL frequency resource and simultaneously perform UL transmission within the UL frequency resource. When operating as a fallback, the FD UE can perform DL reception within the DL frequency resources or UL transmission within the UL frequency resources. The FD UE can perform DL reception or UL transmission in accordance with the transmission direction set / instructed based on the signaling of the BS in the frequency resources of F.
[0364] The resources of D / U are not switched to other types, but the resources of F may be changed due to additional signaling or certain conditions. If changed, F may be able to switch to D or U. For example, a BS supporting SBFD may switch (DFD) to (DUD) if the amount of UL transmission needs to be increased. Alternatively, if immediate DL transmission is required, or if one wants to block UL transmission in another subband when SSB transmission occurs, the BS may switch (DFD) to (DDD). (DFD) can be changed / switched to (DDD) and (DUD). (DDF) can be changed / switched to (DDD) and (DDU). (FDD) can be changed / switched to (DDD) and (UDD).
[0365] When SBFD is supported as a basic feature in a 6G environment, frequency resource types such as (UFU), (UUF), or (FUU), which are extended forms of SBFD according to Release 19 of the 5G standard, may also be considered.
[0366] In FIG. 17, the frequency resource type (XXX) is a frequency resource type that supports SSFD, where DL and UL can be performed simultaneously across the entire symbol. The resource set to (XXX) is a resource where DL transmission and UL reception can occur simultaneously on the entire symbol resource for the BS. The resource set to (XXX) can be interpreted as F across the entire symbol for the HD UE. For example, for the resource set to (XXX), the UE performs DL reception or UL transmission according to the instructions of UE-specific signaling and / or scheduling DCI. The resource set to (XXX) can be interpreted as F across the entire symbol for an SBFD-aware UE. For example, for the resource set to (XXX), the UE performs DL reception or UL transmission according to the instructions of UE-specific signaling and / or scheduling DCI. Resources configured as (XXX) are resources where DL reception and UL transmission can occur simultaneously across the entire symbol for SSFD-aware UEs.
[0367] When SBFD is supported as a basic feature in a 6G environment, frequency resource types extended from SBFD according to Release 19 of the 5G standard can be expected. Among the subbands configured as (XXX), the resource type for a specific subband can be configured / indicated as the resource type of F. For example, frequency resource types of (FXF), (FFX), (XFF), (XFX), (FXX), or (XXF) can be configured / indicated. If certain conditions are not met (e.g., in the case of excessive cross-link interference (CLI), X can be interpreted as F. In this case, the UE performs DL reception or UL transmission on the frequency resource of X according to the instructions of the UE-specific signaling and / or scheduling DCI. Alternatively, assuming a fallback, X may be interpreted as DL or UL. Or X may be interpreted as N. A UE does not perform DL or UL on a resource that is set / directed as X but interpreted as N, and if it receives a scheduling that includes the resource, it may ignore the scheduling or follow the scheduling excluding the resource.
[0368] In FIG. 16, (DXD) and (DDX) are frequency resource types that support SSFDs, which enable simultaneous transmission of DL and UL in the frequency resource of X. The frequency resource types of (DXD) or (DDX) are examples where SSFDs can be applied at the location of X by considering resources that can be set / indicated as UL in SBFDs, under the assumption that UL is possible only in some subbands considering adjacent carrier CLIs. Resource types in some resource areas can be switched via RRC signaling (e.g., common / UE-specific TDD settings), UE-specific signaling, and / or dedicated / scheduled DCIs. The BS can perform DL transmission in the frequency resource of D and simultaneously perform UL reception in the frequency resource of U. To the BS, X is a resource type where DL transmission and UL reception can occur simultaneously within a specific resource (e.g., the frequency resource of X). To the HD UE, X can be interpreted as F. For example, in accordance with instructions from UE-specific signaling and / or scheduling DCI, the UE performs a DL receive or a UL transfer on a resource set / directed to X. To an SBFD-aware UE, X may be interpreted as F. For example, in accordance with instructions from UE-specific signaling and / or scheduling DCI, the UE performs a DL receive or a UL transfer on a resource set / directed to X. A resource set / directed to X is a resource where DL receive and UL transfer can occur simultaneously to an SSFD-aware UE. Resources of D / U are not switched to other types, but resources of X may be changed to other types by additional signaling or certain conditions. If changed, F may be capable of switching to F, D, or U. If certain conditions are not satisfied (e.g., if there is an excessive CLI), X may be interpreted as F. In this case, according to the instructions of the UE-specific signaling and / or scheduling DCI, the UE may perform DL reception or UL transmission on the resources of X.Alternatively, assuming a fallback, X may be interpreted as DL or UL. Or X may be interpreted as N. In this case, the UE does not perform DL or UL on the corresponding resource set / directed by X, and if it receives a scheduling that includes the resource, it may ignore the scheduling or follow the scheduling excluding the resource. (DXD) may be changed / switched to (DFD), (DDD), or (DUD). (DDX) may be changed / switched to (DDF), (DDD), or (DDU). (XDD) may be changed / switched to (FDD), (DDD), or (UDD).
[0369] When SBFD is supported as a basic feature in a 6G environment, frequency resource types such as (UXU), (UUX), and (XUU), which are extended forms of SBFD according to Release 19 of the 5G standard, may also be considered.
[0370] If specific conditions are satisfied or not satisfied, X may be switched to other resource types such as F, U, or D based on rules or all at once. Specific conditions may be determined based on parameter values given by BS. Alternatively, BS may directly direct the switching. For example, if interference (e.g., CLI or self-interference) occurring in the resource set / directed by X is high, preventing UL transmission and DL transmission from occurring simultaneously, some frequency ranges may be switched to other resource types. For example, switching to dynamic SBFD (e.g., (DFD), (DDF)), semi-static SBFD (e.g., (DUD), (DDU)), or TDD (e.g., (DDD)) is possible so that only DL transmission or UL transmission can be performed in a specific subband.
[0371] (DND) and (NUN) are resource settings that can be used when only some frequency resources of a specific symbol are permitted to be used. Symbols set / indicated as (DND), (NDD), or (DDN) are symbols that can only perform DL transmission in a specific frequency range, and symbols set / indicated as (NUN), (NNU), or (UNN) are symbols that can only perform UL transmission in a specific frequency range, and are examples based on the resource settings of SBFD.
[0372] Additionally, the resource type is set / instructed by the BS, but in cases where UEs with various capabilities coexist, or where a UE with a specific capability does not satisfy a specific condition (or does satisfy one), the BS or UE may operate differently depending on the given resource type.
[0373] For example, to BS, X is a resource where DL and UL transmissions can occur simultaneously on a specific resource of a frequency resource type within a specific time resource. To an HD UE, X can be interpreted as F. For example, according to instructions from UE-specific signaling and / or scheduling DCI, the UE performs a DL receive or UL transmission on the resource set / directed as X. X can be interpreted as F to an SBFD-aware UE. For example, according to instructions from specific signaling and / or scheduling DCI, the UE performs a DL receive or UL transmission on the resource set / directed as X. To an FD UE, the resource set / directed as X is a resource where DL / UL can occur simultaneously. However, if certain conditions are not met (e.g., when there is an excessive CLI), X can be interpreted as F. In this case, according to instructions from UE-specific signaling and / or scheduling DCI, the UE performs a DL receive or UL transmission on the resource X. Alternatively, assuming a fallback, X may be interpreted as DL or UL. Or X may be interpreted as N. In this case, the UE does not perform DL or UL on the resource set / directed by X, and if it receives a scheduling that includes the resource, it may ignore the scheduling or follow the scheduling excluding the resource.
[0374] For example, assuming dynamic SBFD is supported, for the BS, F is a resource type where DL or UL transmission can occur on a specific resource (e.g., entire band or subband). If DL and UL are included in the frequency resource types for a subband within a specific time resource, DL transmission and UL transmission can be performed simultaneously within said subband. For an HD SBFD-aware UE, a resource set / designated as F is a resource (entire band or subband) where DL or UL transmission can occur. For example, according to instructions from UE-specific signaling and / or scheduling DCI, the UE performs DL reception or UL transmission on the resource set / designated as F. For an FD SBFD-aware UE, if the entire band is set as F, said entire band is a resource where DL or UL transmission can occur. For example, according to instructions from UE-specific signaling and / or scheduling DCI, the UE decides whether to perform DL reception or UL transmission on the resource set / designated as F. If DL and UL are included in the frequency resource types for a subband in a specific time resource, DL transmission and UL transmission can be performed simultaneously within the subband.
[0375] <2. RO Configuration Based on Resource Configuration for Full Duplex>
[0376] A unified UL-DL resource configuration applicable to the various duplex operations mentioned above can be considered, as in the examples in Section 1. When frequency resource types are configured in this way, appropriate RO configuration methods, related parameters, rules, and associated SSB-RO mapping rules must be considered together. For convenience, some implementations of this specification are described below using SBFD as an example, but some implementations of this specification can be applied to various duplex features, including SSFD.
[0377] This specification assumes that the frequency resource type is structured to be configured and operated by a pattern based on the time resource by the BS, and that full duplex is supported based on this. This frequency resource type is structured to be configured using one or more sub-frequency resources (e.g., subbands), and the resource types (D, L, F, X, N, etc.) of each subband constituting the frequency resource type may be the same or different from one another. When frequency / time resources are configured in this manner, appropriate RO configuration methods, related parameters, RO validity rules, and related SSB-RO mapping rules must be considered together.
[0378] In 6G systems, SBFD-related features can be configured as basic capabilities, in which case a 6G-enabled UE can understand frequency resource types related to SBFD, changes in related resource types, and the signaling of the associated BS. Even 6G-enabled UEs can be classified into UE types that understand all SBFD-related features (e.g., UE Type 1) or UE types that understand only some of them (e.g., UE Type 2). For example, if UE Type 2 is defined to operate only with frequency resource types configured semi-statically, it may fail to perform the expected operation if additional frequency resource types or resource types in certain subbands are dynamically changed. UEs of this type can be free from the constraints of tight processing time requirements. Alternatively, even among UEs that support 6G, there may be UE types capable of understanding and executing SBFD-related characteristics (e.g., UE Type 3), UE types capable of understanding but not executing SBFD-related characteristics (e.g., UE Type 4), or UE types capable of executing only under specific conditions (e.g., UE Type 3 variation). For example, UE Type 4 cannot perform SBFD-related operations but can understand SBFD-related settings / instructions configured by the BS in the same way as UE Type 3. UEs of this type can contribute to minimizing UE complexity and the impact on standard documentation, such as the need to reinterpret the same parameters. A 6G UE can operate with one or more of the characteristics of the types mentioned above.Unless otherwise noted, SBFD UEs are assumed to be UE types capable of understanding and executing SBFD-related characteristics, while non-SBFD UEs are assumed to be UE types capable of understanding SBFD-related settings / instructions set by BS, although they cannot perform SBFD-related operations (or can perform some SBFD-related operations under specific conditions or assumptions). Such UE types may behave differently in interpreting ROs set by BS in the same way.
[0379] A 6G UE can select a set of RO resources to transmit single or multiple PRACH(s), and RO resources may be valid for frequency resources configured / indicated as U resource type and / or F resource type. The U resource type may be indicated within a frequency resource through initial configuration or resource type change. For example, a specific subband may be initially configured as a U resource type, but may be configured / indicated to enable PRACH transmission by changing from an F resource type or X resource type to a U resource type via semi-static / dynamic signaling. The RACH configuration (also referred to as PRACH configuration, RO configuration, or RO-related configuration) may be configured / indicated independently of the TDD configuration that configures / indicates the frequency resource type. Alternatively, the RACH configuration may be configured in whole or in part when the TDD configuration that configures / indicates the frequency resource type is configured. For example, parameters related to the PRACH setting index, parameters related to the number of frequency division multiplexed (FDMed) ROs, etc., can be set together when the resource type for some or all subband(s) of the frequency resource type is set.
[0380] Regarding RO configuration (or PRACH configuration), an RO configured in an SBFD symbol or a section containing an SBFD symbol is referred to as an SBFD RO for convenience. An RO configured in a non-SBFD symbol section is referred to as a non-SBFD RO. A non-SBFD symbol may refer to a symbol with frequency resource types such as (DDD), (UUU), or (FFF), and even if resource types are indicated separately by subband, frequency resource types can be viewed as referring to a single continuous series of frequency resources, as in 5G NR. When the subband(s) constituting a frequency resource type are configured / instructed to an SBFD UE as a U resource type, both the SBFD RO and the non-SBFD RO included in these subband(s) may be valid. When some subband(s) of an SBFD symbol configured with a frequency resource type are configured / instructed to an SBFD UE as a U resource type, only the SBFD RO included in the relevant subband(s) may be valid. For a non-SBFD UE, the non-SBFD RO included in the corresponding subband(s) configured / directed as U resource type is valid for the non-SBFD symbol configured with a frequency resource type, and depending on the type of the non-SBFD UE, when some subband(s) of the SBFD symbol configured with a frequency resource type are configured / directed as U resource type, the SBFD RO included in the relevant subband(s) may also be valid.
[0381] When an RO that can only be used by SBFD UEs (hereinafter, RO Set 1) and an RO that can be used by both non-SBFD UEs and SBFD UEs (hereinafter, RO Set 2) are simultaneously configured through a single RO configuration (or PRACH configuration), SSB-to-RO mapping can be performed based on all ROs that combine RO Set 1 and RO Set 2. At this time, since SBFD UEs and / or non-SBFD UEs can also interpret all configuration information, SSB-to-RO mapping for all ROs can be performed normally. However, since the ROs that non-SBFD UEs can actually use are limited to RO Set 2, RO Set 1 may be defined to be treated as an invalid RO from the perspective of non-SBFD UEs after SSB-to-RO mapping. Consequently, BS needs to provide RO configurations so that all beam directions of the SSB can be properly mapped to the ROs included in RO Set 2 as well.
[0382] In the following, several implementations of this specification regarding a method for a UE to determine a RACH occasion (RACH occasion, RO) resource are described, taking into account an environment where resource types may differ at the subband level.
[0383] RO configuration (or RACH configuration) information is provided to the UE from the BS, and based on this information, resources configuring the RO(s) may be indicated, and additionally, some of the indicated RO(s) may be determined to be valid RO(s).
[0384] By applying operations according to some implementations of this specification, the UE may receive information necessary to determine RO resources from the BS through RO settings (or RACH settings), etc. Based on said information, the UE may determine the resource(s) constituting the RO(s). Additionally, the UE may determine valid RO(s) among said RO(s) by applying operations according to some implementations of this specification. The UE may determine said valid RO(s) as resources capable of transmitting PRACH and transmit PRACH to the BS within said resources.
[0385] By applying operations according to some implementations of this specification, the BS may set RO resource(s) and provide information necessary for the UE to determine the RO resource(s) through the RO setting (or RACH setting), etc. The BS may determine the valid RO(s) among the RO(s) determined by the UE through said information and expect the UE to transmit PRACH using said valid RO(s). The BS may attempt to receive / perform PRACH from the UE through said valid RO resources.
[0386] The two types of RACH configuration options supported in existing 5G NR systems had many limitations because legacy UEs could not resolve ROs located in flexible and / or downlink SBFD symbols that were additionally configured to support SBFD. For example, if a flexible symbol is configured as an SBFD symbol, an SBFD UE can recognize it, but a legacy UE would not; therefore, there were limitations such as restricting flexible SBFD symbols to legacy ROs out of consideration for legacy UEs, even though they are SBFD symbols. According to some implementations of this specification described below, it is assumed that both SBFD UEs and non-SBFD UEs can resolve ROs configured in SBFD symbols, which offers the advantage of securing greater configuration flexibility. The following describes some implementations of this specification in which RO configurations are set so that a UE can determine RO resources, and from this, the UE determines RO resources.
[0387] FIGS. 18 to 20 illustrate examples in which frequency resource types are applied according to time intervals in some implementations of the present specification. As in the examples of FIGS. 18 to 20, the position of the U resource type applied to the frequency resources constituting the frequency resource type may differ depending on the time interval. For convenience of explanation, unless otherwise specified, it is assumed below that the positions of subbands 1, 2, and 3 follow the order exemplified in FIG. 18. The three cases exemplified in FIGS. 18 to 20 are assumed to be representative examples in which frequency resource types are set / indicated, and may be used below as examples when RO settings (i.e., RACH settings) are applied according to some implementations of the present specification.
[0388] FIG. 18 illustrates a case where a subband set / indicated as a U resource type is fixed as one in a resource configuration consisting of frequency resource types to support SBFD. For example, referring to FIG. 18, subband 2 is set / indicated as a U resource type based on the SBFD symbol.
[0389] FIG. 19 illustrates a case in which, in a resource configuration consisting of frequency resource types to support SBFD, multiple subbands are set / indicated as U resource types and the multiple subbands do not overlap with each other on the time axis. For example, referring to FIG. 19, based on the SBFD symbol, the frequency resource type is set / indicated as DUD or DDU, so that subband 2 or subband 3 is set / indicated as U resource types and does not overlap with each other on the time axis.
[0390] FIG. 20 illustrates a case in which, in a resource configuration consisting of frequency resource types to support SBFD, multiple subbands are configured / designated as U resource types and UL transmissions on the multiple subbands (e.g., subband 1 and subband 2) are allowed to overlap with each other in the time axis. For example, referring to FIG. 20, based on the SBFD symbol, the frequency resource type is configured as DUD or UUD so that subband 2 or subbands 1 and 2 are configured / designated as U resource types.
[0391] In some implementations of this specification, the following methods are considered for BS to provide RO settings.
[0392] * Method 1-1) A method defined (in the standard) such that when a BS provides a single RACH setting and sets an RO based thereon, the RO is located within a subband of a frequency resource type set / indicated as a U resource type among the frequency resources constituting the SBFD symbol. The BS receives a PRACH from the UE through the RO thus set. The UE receives a single RACH setting from the BS and can select a set of ROs based thereon. At this time, the UE checks the location of the set RO resource. Such an RO is set within a subband of a frequency resource set / indicated as a U resource type among the frequency resources constituting the SBFD symbol, and the UE transmits a PRACH through the RO resource thus set.
[0393] * Method 1-2) A method defined (in the standard) such that when a BS provides a single RACH setting and sets an RO based thereon, the RO is located within a subband of a frequency resource type that is set / indicated as a U resource type among the frequency resources. The BS receives a PRACH from the UE through the RO thus set. The UE receives a single RACH setting from the BS and can select a set of ROs based thereon. At this time, the UE checks the location of the set RO resource. Such an RO is set within a subband of a frequency resource type that is set / indicated as a U resource type among the frequency resources, and the UE transmits a PRACH through the RO resource thus set.
[0394] * Method 2) A method defined (in the standard) whereby the BS provides a single RACH configuration and configures the RO based thereon, causing the SBFD UE to interpret the same parameter differently in non-SBFD symbols and SBFD symbols. The BS receives RRACH from the UE through the RO configured in this way. The UE receives a single RACH configuration from the BS and can select a set of ROs based on it. At this time, the location of the configured RO resources is identified. The UE interprets the same parameter differently in non-SBFD symbols and SBFD symbols. The UE transmits PRACH through the RO resources configured in this way.
[0395] <2.1. Method 1-1) A method in which a BS provides a single RACH setting and sets an RO based thereon, said RO is defined to be located within a subband of a frequency resource type set / indicated as a U resource type among the frequency resources constituting the SBFD symbol>
[0396] FIGS. 21 through 25 illustrate RO locations according to some implementations of the present specification related to Method 1-1 of the present specification.
[0397] In some implementations of this specification, one or more subband(s) may be set / indicated as U resource types by the frequency resource type. Cases in which the position of the U resource type applied to the frequency resources constituting the frequency resource type according to the time interval is fixed as one (e.g., see FIG. 18) and cases in which it is set / indicated as multiple (e.g., see FIG. 19 and / or FIG. 20) may be considered.
[0398] According to this method, since SBFD UEs and non-SBFD UEs can understand the parameter(s) in common, the standard impact of having to reinterpret specific parameters and the increase in implementation complexity can be avoided.
[0399] * Alt 1) BS provides a single RACH setting, and through this, common parameter values can be provided so that the RO configured can be located within a subband configured / indicated as a U resource type in an SBFD symbol configured with a frequency resource type. For example, the RO can be configured based on common PRACH setting index parameters, common frequency offset parameters, etc.
[0400] In 6G, since the number of U subbands constituting the SBFD symbol can be configured to be multiple, the number of configured RO resources may be excessive. According to some implementations of this specification, if the number of U subbands where RO is configured is fixed to one, there is an advantage that unnecessary RO configuration can be prevented.
[0401] As exemplified in FIG. 21, when the location of a subband configured as a U resource type by the frequency resource type (DUD) for the frequency resources constituting the SBFD symbol is fixed as one, and as exemplified in FIG. 19 and / or FIG. 20 when multiple subbands are configured as U resource types, relevant parameters may be provided so that the RO can be located within the subband configured / indicated as a U resource type in the SBFD symbol configured with a frequency resource type. If SBFD UEs and non-SBFD UEs coexist in 6G and SBFD UEs and non-SBFD UEs can understand the parameters related to SBFD in common, then SBFD UEs and non-SBFD UEs interpret the PRACH setting index value and frequency offset value in the same way, and thereby the location of the RO defined (e.g., the location of the RO configured on the premise that SBFD UEs and non-SBFD UEs interpret the PRACH setting index value and frequency offset value provided by BS in the same way) may be provided in alignment with the U subband. The BS can set the frequency offset value by using the physical resource block (PRB) located at the lowest frequency relative to the full bandwidth as a reference. Alternatively, the BS can set the frequency offset value by using the PRB located at the lowest frequency relative to the U subband where the RO is set as a reference. When parameters related to the frequency offset are set, the UE can interpret the frequency offset value by using the PRB located at the lowest frequency relative to the full bandwidth as a reference. Alternatively, the UE can interpret the frequency offset value by using the PRB located at the lowest frequency relative to the U subband where the RO is set as a reference.When considering cases where the subband size is relatively small, overhead in frequency resource units can be reduced when setting / indicating the frequency offset by considering the PRB located at the lowest frequency relative to the U subband as a reference.
[0402] Referring to FIG. 21, parameter values may be provided such that an RO is set in the U subband of an SBFD symbol, for example, where the frequency resource type for three subbands is set to (DUD). All set ROs are valid because they are all within the same frequency resource as the associated subbands. In this case, the validity of a non-SBFD RO set in a non-SBFD symbol depends on how the SBFD UE uses the associated RO. For a non-SBFD UE, the non-SBFD RO is valid.
[0403] Referring to FIG. 22, for example, parameter values can be provided to set an RO in the U subband among three subbands where the frequency resource type is set to (DUD). Among the set ROs, only the ROs within the same frequency resource as the U subband of (DUD) are valid. In this case, the validity of the non-SBFD RO set in the non-SBFD symbol depends on how the SBFD UE uses the relevant RO. The non-SBFD RO is valid for the non-SBFD UE.
[0404] Referring to FIG. 23, parameter values may be provided to set ROs in two U subbands among three subbands where the frequency resource type is set to (UUD), for example. Any RO set outside the set U subbands among the set ROs is invalid. Although not shown in FIG. 23, if the BS needs to set ROs without considering subbands 1 and 2 associated with the (UUD) frequency resource type as continuous frequency resources, parameter values may be provided to set ROs within subband 1. In this way, whether ROs can be set in multiple subbands at once based on SBFD symbols can be determined through upper-layer signaling. In this case, the validity of a non-SBFD RO set in a non-SBFD symbol depends on how the SBFD UE uses the relevant RO. For a non-SBFD UE, the non-SBFD RO is valid.
[0405] In this case, for non-SBFD symbols set to (UUU), ROs set based on SBFD symbols may be invalid. This prevents resource fragmentation of UL frequency resources. It may support RACH settings or separate parameters to set ROs separately for non-SBFD symbols.
[0406] In this case, for non-SBFD symbols configured as (UUU), resource fragmentation may occur in the UL frequency resources due to the position of the RO configured for the U subband. To prevent this, ROs located in all or part of the non-SBFD symbols may be disabled if specific settings / instructions or specific conditions are satisfied. Such settings / instructions may be provided dynamically via semi-static common / UE-specific signaling and / or MAC CE or DCI. Relevant parameters may be supported so that the BS can directly prioritize SBFD ROs (or non-SBFD ROs). Relevant parameters may be supported so that the conditions under which SBFD ROs (or non-SBFD ROs) can be used are set by threshold values related to the SSB.
[0407] * Alt 2) The BS may provide a single RACH setting and, through this, provide separate parameters for each subband so that an RO can be set within each subband configured / indicated as a U resource type in an SBFD symbol configured as a frequency resource type. For example, the RO configured through (a single RACH setting containing) parameter value(s such as multiple PRACH setting indices and frequency offset(s)) can be located within each U subband. If there are two U subbands, two parameter values are provided through a single RACH setting, and each parameter value can represent a PRACH setting index, frequency offset, etc. Alternatively, the BS may provide multiple RACH settings, and each RACH setting may provide parameters so that an RO can be set within each subband configured / indicated as a U resource type in an SBFD symbol configured as a frequency resource type. For example, each RACH setting allows the RO configured through parameter values such as a PRACH setting index and frequency offset to be located within each U subband.
[0408] In 6G, since multiple U subbands can be configured for an SBFD symbol, a separate RO can be configured for each UL subband (e.g., a separate PRACH configuration index and a separate RACH configuration can be provided for each U subband). In this case, different types of RO formats can be configured for each UL subband. For example, a long preamble format and a short preamble format can be configured. In this case, the UE can select one of the configured multiple RO sets. The BS can directly configure / instruct a specific RO set, or it can set values such as an RSRP threshold to allow the UE to select an RO set.
[0409] Referring to FIG. 24, when SBFD is configured for frequency resources configured with frequency resource types (DUD) and (DDU) according to time intervals, BS may provide separate parameters (e.g., separate PRACH configuration index, separate frequency offset) so that ROs (e.g., RO1 for U subband in (DUD) and RO2 for U subband in (DDU)) can be configured within each U subband configured / indicated as a U resource type. Here, U indicates a specific U subband where ROs are configured, and is used with the same meaning in this specification unless otherwise specified. For example, in FIG. 24, for RO1, parameter values provided to configure ROs in the U subband in (DUD) may be provided, and any RO configured outside the U subband among the configured ROs is invalid. In the case of RO2, parameter values may be provided in (DDU) to set the RO in the U subband, and among the set ROs, any RO set outside the U subband is invalid. At this time, the validity of the non-SBFD RO set in the non-SBFD symbol depends on how the SBFD UE uses the relevant RO. The non-SBFD RO is valid for the non-SBFD UE.
[0410] Referring to FIG. 25, when SBFD is configured for frequency resources set with frequency resource types (DUD) and (UUD) according to time intervals, BS may provide separate parameters (e.g., separate PRACH setting index, separate frequency offset) so that ROs (e.g., RO1 for U subband in (DUD) and RO2 for U subband in (UUD)) can be configured within each U subband configured / indicated as a U resource type. For example, in FIG. 25, for RO1, parameter values may be provided so that ROs are configured in the U subband in (DUD) and (UUD), and any RO configured outside the U subband among the configured ROs is invalid. For RO2, parameter values may be provided so that ROs are configured in the U subband in (UUD), and any RO configured outside the U subband among the configured ROs is invalid. At this time, the validity of the non-SBFD RO set in the non-SBFD symbol depends on how the SBFD UE uses the related RO. The non-SBFD RO is valid for the non-SBFD UE.
[0411] If SBFD UEs and non-SBFD UEs coexist in 6G and can understand the parameters related to SBFD in common, then SBFD UEs and non-SBFD UEs interpret the values of the PRACH setting index and frequency offset values identically, and the position of the RO defined thereby (e.g., the position of the RO set on the premise that SBFD UEs and non-SBFD UEs interpret the PRACH setting index values and frequency offset values provided by the BS identically) can be provided in alignment with the U subband. The BS can set the frequency offset value by referencing the PRB located at the lowest frequency across the entire bandwidth. Alternatively, the BS can set the frequency offset value by referencing the PRB located at the lowest frequency across each U subband. The UE can interpret the value set by referencing the PRB located at the lowest frequency across the entire bandwidth. Alternatively, the UE may interpret the set frequency offset value by referencing the PRB located at the lowest frequency relative to each U subband. In this case, there may be an advantage in terms of overhead because fewer frequency resources are required to set the offset.
[0412] In this case, for non-SBFD symbols set to (UUU), ROs set based on SBFD symbols may be disabled. This prevents resource fragmentation of UL frequency resources. A RACH setting or separate parameter to set ROs separately for non-SBFD symbols may be supported.
[0413] In this case, for non-SBFD symbols configured as (UUU), resource fragmentation may occur in the UL frequency resources due to the position of the RO configured for the U subband. To prevent this, ROs located in all or part of the non-SBFD symbols may be disabled if specific settings / instructions or specific conditions are satisfied. Such settings / instructions may be provided dynamically via semi-static common / UE-specific signaling and / or MAC CE or DCI. Relevant parameters may be supported so that the BS can directly prioritize the SBFD RO (or non-SBFD RO). Relevant parameters may be supported so that the conditions under which the SBFD RO (or non-SBFD RO) can be used are set by threshold values related to the SSB.
[0414] <2.2. Method 1-2) A method in which a BS provides a single RACH setting and sets an RO based thereon, wherein the RO is defined to be located within a subband of a frequency resource type set / indicated as a U resource type among frequency resources. Or a method in which a BS provides multiple RACH settings, and each RACH setting provides parameters such that an RO can be set within each subband set / indicated as a U resource type by a frequency resource type.>
[0415] FIGS. 26 through 31 illustrate RO locations according to some implementations of the present specification related to method 1-2 of the present specification.
[0416] Unlike Method 1-1, Method 1-2 has the advantage that a separate RO can be configured for non-SBFD symbols. If the U subband is configured to be in the middle of the frequency domain for SBFD symbols, the RO can also be located in the middle of non-SBFD symbols. In this case, if the RO is located in the middle of the frequency domain of non-SBFD symbols, inefficiency may arise where UL / DL channels or signals that can be transmitted using the wide frequency range of said non-SBFD symbols are fragmented due to said RO. Below, several implementations of this specification are described that allow for the efficient utilization of resources of non-SBFD symbols by additionally defining an RO validation rule.
[0417] According to Method 1-2, since SBFD UEs and non-SBFD UEs can understand parameters in common, the standard impact of having to reinterpret specific parameters and the increase in implementation complexity can be avoided.
[0418] One or more subband(s) may be configured / indicated as U resource types by the frequency resource type. For example, as shown in FIGS. 26, 27, and 28, when the frequency resource type is configured with multiple subband frequencies, an RO may be configured for each subband. This configuration has the advantage of ensuring configuration flexibility of the BS so that an appropriate RO can be configured for each U subband regardless of the presence of SBFD symbols. In the case of FIG. 26, the BS may not configure an RO for either of the two so that RO overlap does not occur between subband 1 and subband 3. In this case, the relevant PRACH configuration index may be defined to have an index value indicating that an RO is not configured, or to have the same meaning when the parameter is configured as not present or absent. FIGS. 26 to 28 illustrate cases where the basic operation is similar to Alt 2 of Section 2.1, but because a non-SBFD RO can be separately set for a non-SBFD symbol, the RO set for the non-SBFD symbol is treated as invalid when the RO is set for the U subband based on the SBFD symbol.
[0419] Referring to FIG. 29, FIG. 30, or FIG. 31, the BS may provide a single RACH setting and, through this, provide separate parameters for each subband so that an RO can be set within each subband that is set / indicated as a U resource type by the frequency resource type. For example, the RO set through a single RACH setting (including parameter values such as multiple PRACH setting indices and frequency offsets) may be located within each U subband. If there are two U subbands, two parameter values are provided through a single RACH setting, and each parameter value may represent a PRACH setting index, frequency offset, etc. Alternatively, the BS may provide multiple RACH settings, and each RACH setting may provide parameters so that an RO can be set within each subband that is set / indicated as a U resource type in the SBFD symbol set as the frequency resource type. If SBFD UEs and non-SBFD UEs coexist in 6G and can understand the parameters related to SBFD in common, then SBFD UEs and non-SBFD UEs interpret the PRACH setting index value and frequency offset value identically, and the position of the RO defined therein (e.g., the position of the RO set on the premise that SBFD UEs and non-SBFD UEs interpret the PRACH setting index value and frequency offset value provided by the BS identically) can be provided in alignment with the U subband. The BS can set the frequency offset values 1, 2, and 3 by referencing the PRB located at the lowest frequency across the entire bandwidth. Alternatively, the BS can set the frequency offset values 1, 2, and 3 by referencing the PRB located at the lowest frequency across each U subband. The UE can interpret the values set by referencing the PRB located at the lowest frequency across the entire bandwidth for the frequency offset values 1, 2, and 3.Alternatively, the UE can interpret the set values for frequency offsets 1, 2, and 3 by referencing the PRB located at the lowest frequency relative to each U subband. In this case, there may be a gain in terms of overhead because the number of frequency resources required to set the offset is small.
[0420] For example, each RACH setting includes parameter values such as a PRACH setting index and a frequency offset, thereby enabling the BS to position the set RO within each U subband. In other words, each RACH setting includes parameter values such as a PRACH setting index and a frequency offset, and the BS can position the set RO within each U subband through respective RACH settings for the U subbands. Referring to FIG. 29, for frequency resources set with frequency resource types (DUD) and (UUU) according to the time interval, the BS may provide separate parameters so that an RO (e.g., RO3 for the U subband within (UUU), RO3 for the U subband within (DUD) and (UUU), RO1 for the U subband within (UUU)) can be set within each U subband set / indicated as a U resource type. Referring to FIG. 30, when SBFD is configured for a frequency resource in which frequency resource types (DUD), (DDU), and (UUU) are configured according to a time interval, BS may provide a separate parameter so that ROs (e.g., RO1 for the U subband within (DDU) and (UUU), RO2 for the U subband within (DUD) and (UUU), and RO3 for the U subband within (UUU)) can be configured within each U subband configured / instructed as a U resource type. The same rule may be applied to FIG. 31.
[0421] For example, in FIG. 29, for RO1, parameter values may be provided so that RO is set in the U subband at (UUU), and among the set ROs, any RO set outside the U subband is invalid. For RO2, parameter values may be provided so that RO is set in the U subband at (DUD) and (UUU), and among the set ROs, any RO set outside the U subband is invalid. For RO3, parameter values may be provided so that RO is set in the U subband at (UUU), and among the set ROs, any RO set outside the U subband is invalid.
[0422] For example, in FIG. 30, for RO1, parameter values may be provided so that RO is set in the U subband at (DDU) and (UUU), and among the set ROs, any RO set outside the U subband is invalid. For RO2, parameter values may be provided so that RO is set in the U subband at (DUD) and (UUU), and among the set ROs, any RO set outside the U subband is invalid. For RO3, parameter values may be provided so that RO is set in the U subband at (UUU), and among the set ROs, any RO set outside the U subband is invalid.
[0423] For example, in FIG. 31, for RO1, parameter values may be provided so that RO is set in the U subband at (UUU), and among the set ROs, any RO set outside the U subband is invalid. For RO2, parameter values may be provided so that RO is set in the U subband at (DUD), (UUD), and (UUU), and among the set ROs, any RO set outside the U subband is invalid. For RO3, parameter values may be provided so that RO is set in the U subband at (UUD) and (UUU), and among the set ROs, any RO set outside the U subband is invalid.
[0424] In this case, for non-SBFD symbols set to (UUU), ROs set based on SBFD symbols may be disabled. This prevents resource fragmentation of UL frequency resources. A RACH setting or separate parameter to set ROs separately for non-SBFD symbols may be supported.
[0425] In this case, for non-SBFD symbols configured as (UUU), resource fragmentation may occur in the UL frequency resources due to the position of the RO configured for the U subband. To prevent this, ROs located in all or part of the non-SBFD symbols may be disabled if specific settings / instructions or specific conditions are satisfied. Such settings / instructions may be provided dynamically via semi-static common / UE-specific signaling and / or MAC CE or DCI. Relevant parameters may be supported so that the BS can directly prioritize SBFD ROs (or non-SBFD ROs). Relevant parameters may be supported so that the conditions under which SBFD ROs (or non-SBFD ROs) can be used are set by threshold values related to the SSB.
[0426] <2.3. SSB-RO Mapping Order and SSB-RO Mapping Rules>
[0427] FIGS. 32 through 34 illustrate SSB to RO mapping according to some implementations of the present specification.
[0428] Some implementations of this specification regarding the SSB-RO mapping order and SSB-RO mapping rules when an RO is set according to Method 1-1) or Method 1-2) are described below.
[0429] In some implementations, the SSB-RO mapping order of 6G may follow the SSB-RO mapping order of 5G as follows.
[0430] Preamble Indexes: Start with the lowest preamble index within each RACH occasion.
[0431] Frequency Resources: Increase the frequency index if multiple RACH occasions exist in the frequency domain.
[0432] Time Resources: Proceed with time indexing for RACH occasions within the same slot.
[0433] PRACH Slots: Increase the slot index in case of multiple PRACH slots.
[0434] Based on the above rules, the following SSB-RO mapping can be performed on the frequency resource axis.
[0435] * Alt 1) As shown in Fig. 32, SSB-RO mapping can be applied to all U subbands that constitute the frequency resource type. Assuming that all resources are available to the SBFD UE, this method has the advantage of allowing existing implementations to be reused as it maximizes the reuse of rules applied to 5G.
[0436] * Alt 2) As shown in Fig. 33, SSB-RO mapping can be applied to each U subband constituting the frequency resource type. (If a PRACH setting index is provided for each subband,) it can be performed independently for each PRACH setting index set / instructed to each subband. Since the channel environments may differ between subbands, this method may be advantageous when a suitable SSB index is set separately within each UL subband.
[0437] * Alt 3) As shown in FIG. 34, U subband(s) constituting frequency resource types can be grouped, and SSB-RO mapping can be applied to the U subband(s) belonging to each group obtained. According to this method, when there are multiple U subbands and the UE cannot use all UL subbands, RO resources can be utilized efficiently. In FIG. 34, the RO located in subband 3 can be invalidated and excluded from SSB-RO mapping.
[0438] In this case, the symbol (UUU) may be treated as a UL symbol consisting of a single wideband (e.g., the entire frequency resource of the symbol, or the entire frequency resource divided into subbands) and SSB-RO mapping may be performed. In this case, separate SSB-RO mapping parameters may be provided so that different SSB-RO mappings are performed between the RO of the UL symbol and the RO of the U subband.
[0439] <2.4. Overlapping RO Handling>
[0440] As observed in the last slot of Fig. 33, when SSB-RO mapping is applied to each subband constituting the frequency resource type (e.g., in subband 1 and subband 3), parts of the respective ROs may overlap in time. An overlapping RO means that it is Alt 1 over a part or the entire time interval. The method for handling this may be as follows.
[0441] * Alt 1) Through the PRACH configuration index provided by the BS in U subband units, it is possible to configure / instruct the configured ROs so that they do not overlap. However, this may reduce the flexibility of the BS in configuring ROs. For example, in 5G NR, there are high constraints on resource types capable of UL transmission via TDD configuration and the locations of ROs configured via the PRACH configuration index, and environments where UEs cannot simultaneously receive different SSB indices depending on the network implementation had to be considered. This may apply similarly in a 6G environment. To solve this problem, the following Alt 2 may be considered.
[0442] * Alt 2) When ROs configured based on the PRACH setting index values set / instructed for each subband overlap in part or all of the time resources, ROs configured based on a specific PRACH setting index, all ROs in that slot, or all ROs configured with a specific PRACH setting index are invalidated. The ROs that are validated may be as follows.
[0443] ** Alt 2-1) If an RO is set in a high (or low) frequency subband based on subband order, for example, if an RO set in subband 1 and an RO set in subband 2 overlap, the RO set in subband 2 is invalidated. In particular, if this method is applied to non-SBFD symbols, UL resource fragmentation can be prevented.
[0444] ** Alt 2-2) ROs that come after the time resource are invalidated. This takes latency into account and is valid if the RO resource starts first based on the time resource.
[0445] ** Alt 2-3) ROs with lower priority are invalidated based on priority. For example, ROs with lower priority are invalidated based on priority, depending on whether the environment requires consideration of random access capacity or coverage. For example, assuming it is an environment requiring consideration of coverage, if ROs overlap when PRACH configuration index 1 consists of a long preamble and the remaining PRACH configuration indices consist of short preambles, the RO configured based on PRACH configuration index 1, which sets the long preamble, is valid. For example, assuming it is an environment with high cross-link interference (CLI), if PRACH configuration index 1 sets ROs located on SBFD symbols and non-SBFD symbols, and the remaining PRACH configuration indices set ROs located on non-SBFD symbols, and these ROs overlap, the RO configured with PRACH configuration index 1 may be invalidated. Higher-level signaling that sets / indicates priority may be provided.
[0446] <2.6. Fallback between ROs assigned by different PRACH setting indexes>
[0447] In the preceding sections, various RO configuration methods based on resource settings configured / directed by frequency resource types were described. A PRACH configuration index is applied to one or more subband(s) constituting the frequency resource type, allowing different RO configurations to be configured / directed for given frequency-time resources. In this case, it is assumed that the RO configured by one PRACH configuration index 1 is a set of RO1, and the RO configured by another PRACH configuration index 2 is a set of RO2, and so on. The UE can select an RO from among all ROs within the set of RO1 and the set of RO2 to transmit a PRACH. Alternatively, to adjust the number of ROs configured by the BS or to satisfy specific purposes or conditions, the UE can select either the set of RO1 or the set of RO2 to transmit a PRACH. In this case, if specific conditions are satisfied, a fallback between the set of RO1 and the set of RO2 may be possible. Regarding the specific conditions mentioned above, the BS may directly set / instruct a fallback (e.g., via MAC CE, DCI) or set / instruct the conditions under which a fallback must be performed. When performing a PRACH transmission through the first selected set of ROs, a fallback may be performed if the UE fails to perform the PRACH transmission even after performing it a specific number of times. Alternatively, if the UE fails to satisfy a specific threshold criterion based on the measured RSRP, a fallback to another set of ROs may be performed.
[0448] For example, when the set of RO1 is configured as a non-SBFD RO and the set of RO2 is configured as an SBFD RO, a fallback may occur between the set of RO1 and the set of RO2 if certain conditions are met (e.g., if a certain number of PRACH transmissions fail). This is suitable for cases where CLI handling or load balancing is required.
[0449] For example, if the RO1 set is set to a short preamble and the RO2 set is set to a long preamble, a fallback can occur between the RO1 and RO2 sets if certain conditions are met (e.g., if a certain number of PRACH transmissions fail). This is suitable for coverage-limited environments.
[0450] For example, when ROs are overlapping, the first RO(s) (e.g., legacy RO(s) or SBFD RO(s)) set by a specific RO, an RO included in a specific slot, or a specific PRACH setting index may be invalidated by the rule through overlapping RO handling. As another example, the second RO(s) (e.g., SBFD RO(s) or legacy RO(s)) may be set to be invalidated if a specific condition is met (e.g., if a certain number of PRACH transfers fail), and a fallback may occur between the first RO(s) and the second RO(s).
[0451] For example, when there are multiple subband groups, if certain conditions are met, fallback may occur between subband group 1 and subband group 2, or between a subband group and a non-subband group.
[0452] <2.7. Method 2) A method in which, when BS provides a single RACH setting and sets RO based thereon, the SBFD UE is defined to interpret the same parameter differently in non-SBFD symbols and SBFD symbols>
[0453] FIGS. 35 through 38 illustrate RO locations according to some implementations of the present specification related to Method 2 of the present specification.
[0454] One or more subband(s) may be set / designated as U resource type by the frequency resource type. When BS provides a single RACH setting and sets RO based on it, it is a method defined so as to be located within the subband of the frequency resource set / designated as U resource type among the frequency resources constituting the SBFD symbol. According to this method, the wideband frequency resources of the non-SBFD symbol can be efficiently utilized without applying separate RO validation rules to the SBFD symbol and the non-SBFD symbol.
[0455] <2.7.1. Method 2-2) Case where only one PRACH setting index is provided>
[0456] Since a large number of ROs can affect the transmission of UL of resources other than PRACH, ROs can be configured to transmit PRACH to only one U subband regardless of the number of U subbands.
[0457] In 6G, multiple U subbands can be configured for SBFD symbols, and in this case, the number of configured RO resources may be excessive. According to some implementations of this specification, if the U subband where RO is configured is fixed to one, there is an advantage that unnecessary RO configuration can be prevented.
[0458] * Alt 1-1) As shown in FIG. 35, when an RO is set by a single PRACH setting index, the BS can set the position of the RO to be set to the lowest frequency resource included in the SBFD symbol by providing a frequency offset based on the lowest frequency of the corresponding U subband (e.g., lowest PRB). In this case, for the corresponding RO set to a non-SBFD symbol, the BS can set a frequency offset based on the lowest frequency of the wideband. In this case, the frequency offset values applied to the non-SBFD symbol and the SBFD symbol are the same. The UE can determine the position of the RO to be set to the lowest frequency resource included in the SBFD symbol by interpreting the frequency offset based on the lowest frequency of the corresponding U subband. The UE can determine the corresponding RO set to a non-SBFD symbol by interpreting the frequency offset based on the lowest frequency of the wideband.
[0459] * Alt 1-2) As shown in FIG. 36, when an RO is set with a single PRACH setting index, the BS can set the position of the RO, which is set at the lowest frequency included in the SBFD symbol, by providing a frequency offset based on the lowest frequency of the corresponding U subband. In this case, for the corresponding RO set in a non-SBFD symbol, the BS can set a frequency offset based on the lowest frequency of the wideband. In this case, the frequency offset values applied to the non-SBFD symbol and the SBFD symbol can be given as independent parameter values. The UE can determine the position of the RO set in the lowest frequency resource included in the SBFD symbol by interpreting the frequency offset based on the lowest frequency of the corresponding U subband. The UE can determine the corresponding RO set in a non-SBFD symbol by interpreting the frequency offset based on the lowest frequency of the wideband.
[0460] <2.7.2. Method 2-2) Case where multiple PRACH configuration indexes are given>
[0461] In environments where latency is critical for PRACH transmission, the PRACH setting index can be set / instructed for each of one or multiple U subbands.
[0462] In 6G, multiple U subbands can be configured for an SBFD symbol, and in this case, a separate RO can be configured for each UL subband (e.g., a separate PRACH configuration index and a separate RACH configuration can be provided for each U subband). At this time, different types of RO formats can be configured for each UL subband. For example, a long preamble format and a short preamble format can be configured. In this case, the UE can select one of the configured multiple RO sets. The BS can directly configure / instruct a specific RO set in this regard, and can also set values such as RSRP thresholds to allow the UE to select.
[0463] * Alt 1-1) Apply a single frequency start offset value to the RO set for multiple U subbands
[0464] As shown in FIG. 37, when ROs are set with respective PRACH setting indices for multiple U subbands, the BS can set the position of the RO set at the lowest frequency included in the SBFD symbol through a frequency offset based on the lowest frequency of each U subband (e.g., lowest PRB). In this case, for the corresponding RO set in the non-SBFD symbol, the BS can set the frequency offset based on the lowest frequency of the wideband. In the example of FIG. 37, the frequency offset values applied to the non-SBFD symbol and the SBFD symbol are the same as the values applied to the corresponding U subband. However, in another example, the frequency offset values applied to the non-SBFD symbol and the SBFD symbol may be given as independent parameter values. The UE can determine the position of the RO included in the SBFD symbol by interpreting the same frequency offset based on the lowest frequency of each corresponding subband. The UE can determine the position of the RO set at the lowest frequency resource included in the SBFD symbol by interpreting the frequency offset based on the lowest frequency of the corresponding subband. The UE can determine the corresponding RO set on the non-SBFD symbol by interpreting the frequency offset based on the lowest frequency of the wideband. If RO overlap occurs, the method described in Section 2.4 may be applied.
[0465] * Alt 1-2) Set / instruct the corresponding frequency offset value to apply to the RO set for each U subband
[0466] As shown in FIG. 38, when ROs are set with respective PRACH setting indices for multiple U subbands, BS can set the position of the RO set at the lowest frequency included in the SBFD symbol by reflecting the respective frequency offset based on the lowest frequency of each U subband (e.g., lowest PRB). In this case, for the corresponding RO set in the non-SBFD symbol, BS can set the frequency offset based on the lowest frequency of the wideband. In the example of FIG. 38, the frequency offset values applied to the non-SBFD symbol and the SBFD symbol are the same as the values applied to the corresponding U subband. However, in another example, the frequency offset values applied to the non-SBFD symbol and the SBFD symbol can be given as independent parameter values. UE can determine the position of the RO set at the lowest frequency resource included in the SBFD symbol by interpreting the frequency offset based on the lowest frequency of the corresponding subband. UE can determine the corresponding RO set in the non-SBFD symbol by interpreting the frequency offset based on the lowest frequency of the wideband. If RO overlap occurs at this time, the method described in Section 2.4 can be applied.
[0467] According to some implementations of the aforementioned specification, a forward compatible frame structure can be provided that takes into account various duplex feature(s) that may be newly introduced during the development of future wireless communication technologies (e.g., 6G). Accordingly, according to some implementations of the present specification, a new duplex structure can be provided that is free from backward compatibility issues and avoids the complexity of the UE / standard.
[0468] According to some implementations of this specification, RACH configuration, validation rules, SSB-RO mapping, and overlapping RO handling free from backward compatibility issues can be provided. Based on this, the UE can avoid unnecessarily complex implementations and perform efficient RO selection and PRACH transmission according to various environments in the 6G environment.
[0469] FIG. 39 illustrates a signal transmission / reception flow between a first device (e.g., UE) and a second device (e.g., BS) according to some implementations of the present specification. Referring to FIG. 39, the second device may provide the first device with a first random access channel (RACH) setting for a first subband and a second RACH setting for a second subband (S3901). The first device may determine a first RACH occasion (RO) set for the first subband based on the first RACH setting and a second RO set for the second subband based on the second RACH setting. The first device may transmit a random access (RA) preamble on an RO within the first RO set on the first subband (S3903), and the second device may attempt to receive an RA preamble within the first RO set on the first subband. If the transmission of the RA preamble based on the first RO set satisfies a predetermined condition, for example, if the RA preamble based on the first RO set is transmitted a predetermined maximum number of times, the first device can perform switching from the first RO set to the second RO set (S3905).
[0470] FIG. 40 illustrates the flow of operation in a first device according to some implementations of the present specification.
[0471] The first device may perform operations according to some implementations of the present specification. The first device may include at least one transceiver; at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations according to some implementations of the present specification. A processing device for the first device may include at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations according to some implementations of the present specification. A computer-readable (non-transient) storage medium may store at least one computer program including instructions that, when executed by at least one processor, cause the at least one processor to perform operations according to some implementations of the present specification. A computer program or computer program product is written on at least one computer-readable (non-transient) storage medium and may include instructions that, when executed, cause (at least one processor) to perform operations according to some implementations of this specification.
[0472] In a method performed by the first device, or in the first device, the processing device, the computer-readable (non-transient) storage medium, and / or the computer program product, the operations may include: receiving a first random access channel (RACH) setting for a first subband and a second RACH setting for a second subband (S4001); determining a first RACH occasion (RO) set for the first subband based on the first RACH setting and a second RO set for the second subband based on the second RACH setting; transmitting a random access (RA) preamble within the first RO set on the first subband (S4003); and performing switching from the first RO set to the second RO set based on the fact that the RA preamble based on the first RO set has been transmitted a predetermined maximum number of times (S4005).
[0473] FIG. 41 illustrates the flow of operation in a second device according to some implementations of the present specification.
[0474] A second device may perform operations according to some implementations of this specification. The second device may include at least one transceiver; at least one processor; and at least one computer memory operably connected to said at least one processor and, when executed, storing instructions that cause said at least one processor to perform operations according to some implementations of this specification. A processing device for the second device may include at least one processor; and at least one computer memory operably connected to said at least one processor and, when executed, storing instructions that cause said at least one processor to perform operations according to some implementations of this specification. A computer-readable (non-transient) storage medium may store at least one computer program including instructions that cause said at least one processor to perform operations according to some implementations of this specification when executed by said at least one processor. A computer program or computer program product is written on at least one computer-readable (non-transient) storage medium and may include instructions that, when executed, cause (at least one processor) to perform operations according to some implementations of this specification.
[0475] In a method performed by the second device, or in the second device, the processing device, the computer-readable (non-transient) storage medium, and / or the computer program product, the operations may include: transmitting a first RACH setting associated with a first random access channel (RACH) occasion set for a first subband and a second RACH setting associated with a second RACH occasion (RO) set for a second subband (S4101); attempting to receive a random access (RA) preamble within the first RO set on the first subband (S4103); and performing switching from the first RO set to the second RO set based on the failure of receiving the RA preamble based on the first RO set a predetermined maximum number of times (S4105).
[0476] In some implementations related to FIG. 39, FIG. 40, or FIG. 41, performing the switching to the second RO set may include: performing the RA preamble transmission or the PA preamble reception within the second RO set on the second subband.
[0477] In some implementations related to FIG. 39, FIG. 40, or FIG. 41, the first RO set may be related to a short preamble, and the second RO set may be related to a long preamble.
[0478] In some implementations related to FIG. 39, FIG. 40, or FIG. 41, the first RACH setting and the second RACH setting, respectively, may each include a RACH setting index.
[0479] In some implementations related to FIG. 39, FIG. 40, or FIG. 41, the first RACH setting and the second RACH setting may each include a frequency offset related parameter.
[0480] In some implementations related to FIG. 39, FIG. 40, or FIG. 41, the first RACH setting and the second RACH setting may be related to frequency offset related parameters. The frequency position of the first RO set may be determined based on the lowest resource block (RB) of the first subband and the frequency offset related parameters, and the frequency position of the second RO set may be determined based on the lowest RB of the second subband and the frequency offset related parameters.
[0481] In some implementations related to FIG. 39, FIG. 40, or FIG. 41, the first RACH setting and the second RACH setting may be associated with the same RACH setting index.
[0482] In some implementations related to FIG. 39, FIG. 40, or FIG. 41, synchronization signal blocks (SSBs) of the cell may be mapped to valid ROs in the first RO set, and the SSBs may be mapped to valid ROs in the second RO set.
[0483] In some implementations related to FIG. 39, FIG. 40, or FIG. 41, the method or operation may further include determining the valid ROs in the first RO set and the valid ROs in the second RO set.
[0484] In some implementations related to FIG. 39, FIG. 40, or FIG. 41, an RO that overlaps with a non-SBFD symbol where the wireless link type of all subbands within the cell is uplink can be determined to be invalid.
[0485] In some implementations related to FIG. 39, FIG. 40, or FIG. 41, the method or operation may further include detecting or transmitting a synchronization signal block (SSB).
[0486] In some implementations related to FIG. 39, FIG. 40, or FIG. 41, the RA preamble transmission or the RA preamble reception may be performed on the RO among the ROs in the first RO set to which the detected SSB is mapped.
[0487] 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.
[0488] Implementations of this specification may be used in wireless communication systems, BS or user devices, and other equipment.
Claims
In a method performed by a first device, Receive a first random access channel (RACH) setting for a first subband and a second RACH setting for a second subband; Determining a first RACH occasion (RO) set for the first subband based on the first RACH setting and a second RO set for the second subband based on the second RACH setting; Performing a random access (RA) preamble transmission within the first RO set on the first subband; and Based on the fact that the RA preamble transmission based on the first RO set has been performed a predetermined maximum number of times, the method includes performing a switching from the first RO set to the second RO set. method. In paragraph 1, Switching to the above 2nd RO set is: Further comprising performing the RA preamble transmission within the second RO set on the second subband, method. In paragraph 1, The first RO set is associated with a short preamble, and the second RO set is associated with a long preamble, method. In paragraph 1, Each of the above-mentioned first RACH setting and the above-mentioned second RACH setting includes a RACH setting index, method. In paragraph 4, Each of the above-mentioned first RACH setting and the above-mentioned second RACH setting includes a frequency offset-related parameter, method. In paragraph 4, The above first RACH setting and the above second RACH setting are related to frequency offset related parameters, and The frequency position of the first RO set is determined based on the lowest resource block (RB) of the first subband and the frequency offset-related parameters, and The frequency position of the second RO set is determined based on the lowest RB of the second subband and the frequency offset-related parameters, method. In paragraph 1, Each of the above-mentioned first RACH setting and the above-mentioned second RACH setting includes a frequency offset-related parameter, method. In Paragraph 7, The above first RACH setting and the above second RACH setting are related to the same RACH setting index, method. In paragraph 1, The synchronization signal blocks (SSBs) of the cell are mapped to valid ROs within the first RO set, and The above SSBs are mapped to the valid ROs within the above second RO set, method. In paragraph 1, It further includes determining the effective ROs in the first RO set and the effective ROs in the second RO set, and ROs that overlap with non-SBFD symbols where the wireless link type of all subbands within the cell is uplink are determined to be invalid, method. In paragraph 1, It further includes detecting a synchronization signal block (SSB), and The above RA preamble transmission is performed in the RO among the ROs in the first RO set where the detected SSB is mapped, method. At least one transmitter / receiver; At least one processor; and It includes at least one computer memory operablely connectable to the at least one processor and, when executed, stores instructions that cause the at least one processor to perform operations, wherein the operations are: Receive a first random access channel (RACH) setting for a first subband and a second RACH setting for a second subband; Determining a first RACH occasion (RO) set for the first subband based on the first RACH setting and a second RO set for the second subband based on the second RACH setting; Performing a random access (RA) preamble transmission within the first RO set on the first subband; and Based on the fact that the RA preamble transmission based on the first RO set has been performed a predetermined maximum number of times, the method includes performing a switching from the first RO set to the second RO set. First device. At least one processor; and It includes at least one computer memory operablely connectable to the at least one processor and, when executed, stores instructions that cause the at least one processor to perform operations, wherein the operations are: Receive a first random access channel (RACH) setting for a first subband and a second RACH setting for a second subband; Determining a first RACH occasion (RO) set for the first subband based on the first RACH setting and a second RO set for the second subband based on the second RACH setting; Performing a random access (RA) preamble transmission within the first RO set on the first subband; and Based on the fact that the RA preamble transmission based on the first RO set has been performed a predetermined maximum number of times, the method includes performing a switching from the first RO set to the second RO set. Processing unit. In a computer-readable non-transitory storage medium, the storage medium stores at least one program code including instructions that cause at least one processor to perform operations when executed, and said operations are: Receive a first random access channel (RACH) setting for a first subband and a second RACH setting for a second subband; Determining a first RACH occasion (RO) set for the first subband based on the first RACH setting and a second RO set for the second subband based on the second RACH setting; Performing a random access (RA) preamble transmission within the first RO set on the first subband; and Based on the fact that the RA preamble transmission based on the first RO set has been performed a predetermined maximum number of times, the method includes performing a switching from the first RO set to the second RO set. Storage medium. In a method performed by a second device, Transmitting a first RACH setting associated with a first random access channel (RACH) occasion set for a first subband and a second RACH setting associated with a second RACH occasion (RO) set for a second subband; Attempting to receive a random access (RA) preamble within the first RO set on the first subband; and Based on the fact that the reception of the RA preamble based on the first RO set has failed a predetermined maximum number of times, the method includes performing a switching from the first RO set to the second RO set. method. At least one transmitter / receiver; At least one processor; and It includes at least one computer memory operablely connectable to the at least one processor and, when executed, stores instructions that cause the at least one processor to perform operations, wherein the operations are: Transmitting a first RACH setting associated with a first random access channel (RACH) occasion set for a first subband and a second RACH setting associated with a second RACH occasion (RO) set for a second subband; Attempting to receive a random access (RA) preamble within the first RO set on the first subband; and Based on the fact that the reception of the RA preamble based on the first RO set has failed a predetermined maximum number of times, the method includes performing a switching from the first RO set to the second RO set. Second device. At least one processor; and It includes at least one computer memory operablely connectable to the at least one processor and, when executed, stores instructions that cause the at least one processor to perform operations, wherein the operations are: Transmitting a first RACH setting associated with a first random access channel (RACH) occasion set for a first subband and a second RACH setting associated with a second RACH occasion (RO) set for a second subband; Attempting to receive a random access (RA) preamble within the first RO set on the first subband; and Based on the fact that the reception of the RA preamble based on the first RO set has failed a predetermined maximum number of times, the method includes performing a switching from the first RO set to the second RO set. Processing unit. In a computer-readable non-transitory storage medium, the 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: Transmitting a first RACH setting associated with a first random access channel (RACH) occasion set for a first subband and a second RACH setting associated with a second RACH occasion (RO) set for a second subband; Attempting to receive a random access (RA) preamble within the first RO set on the first subband; and Based on the fact that the reception of the RA preamble based on the first RO set has failed a predetermined maximum number of times, the method includes performing a switching from the first RO set to the second RO set. Storage medium.
