Methods and apparatus for transmitting signals in a wireless communication system
By employing a sub-band full-duplex symbol set and non-SBFD symbol set configuration method in wireless communication systems, the timing of random access channels is optimized, solving the problem of low resource utilization in existing technologies and achieving more efficient signal transmission and resource management.
Patent Information
- Application Number
- CN202580026222.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2025-02-19
- Filing Date
- 2025-04-07
- Publication Date
- 2026-11-10
AI Technical Summary
Existing wireless communication systems are inadequate in terms of resource allocation and signal transmission efficiency, especially in the inefficient use of random access channel timing (RO) configuration, resulting in resource waste and poor signal transmission.
By employing a sub-band full-duplex (SBFD) symbol set and a non-SBFD symbol set configuration method, and by rationally arranging the random access channel timing (RO) in the radio frame, the continuous configuration of effective ROs is ensured, and the use of ROs is optimized to improve signal transmission efficiency.
It improves signal transmission efficiency and resource utilization in wireless communication systems, optimizes RO configuration, reduces resource waste, and enhances system performance.
Smart Images

Figure CN123077233A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to a wireless communication system. More specifically, this disclosure relates to a method for transmitting signals in a wireless communication system and an apparatus for using the method. Background Technology
[0002] Following the commercialization of fourth-generation (4G) communication systems, efforts are underway to develop new fifth-generation (5G) communication systems to meet the increasing demand for wireless data services. 5G communication systems are also referred to as post-4G network communication systems, post-LTE systems, or new radio (NR) systems. To achieve high data transmission rates, 5G communication systems include systems operating in millimeter-wave (mmWave) frequency bands of 6 GHz or higher, and systems operating in frequency bands of 6 GHz or lower are also considered to ensure coverage. The implementation methods in base stations and terminals are being considered.
[0003] The 3GPP (3rd Generation Partnership Project) NR system improves network spectrum efficiency and enables communication providers to offer more data and voice services on a given bandwidth. Therefore, the 3GPP NR system is designed to meet the demand for high-speed data and media transmission in addition to supporting a large volume of voice calls. The advantages of the NR system include higher throughput and lower latency on the same platform, support for both Frequency Division Duplex (FDD) and Time Division Duplex (TDD), and lower operating costs due to the enhanced end-user environment and simpler architecture.
[0004] For more efficient data processing, the dynamic TDD of the NR system can use methods to change the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols that can be used in the uplink and downlink based on the data service direction of cell users. For example, when downlink traffic in a cell is greater than uplink traffic, the base station can allocate multiple downlink OFDM symbols to time slots (or subframes). Information about the time slot configuration should be sent to the terminal.
[0005] To mitigate path loss and increase transmission distance in the mmWave band, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, hybrid beamforming combining analog and digital beamforming, and massive MIMO technologies are discussed in 5G communication systems. Furthermore, for network improvements, technologies related to evolved small cells, advanced small cells, cloud radio access networks (cloud RAN), ultra-dense networks, device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, wireless backhaul, non-terrestrial network communication (NTN), mobile networks, cooperative communication, coordinated multipoint (CoMP), and interference cancellation are being developed in 5G communication systems. Additionally, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) are being developed as advanced coding and modulation (ACM) schemes, while filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA) are being developed as advanced connectivity technologies.
[0006] Simultaneously, within the human-centric network of information generation and consumption, the Internet has evolved into the Internet of Things (IoT) network, which exchanges information between distributed components such as objects. The Internet of Everything (IoE) technology, combining IoT with big data processing through connections to cloud servers, is also emerging. Realizing IoT requires technological elements such as sensing technology, wired / wireless communication and network infrastructure, service interface technology, and security technology. This has led to the research in recent years into technologies such as sensor networks, machine-to-machine (M2M), and machine-type communication (MTC) to connect objects. In the IoT environment, intelligent Internet of Things (IT) services can be provided, collecting and analyzing data generated from connected objects to create new value in human life. Through the integration and hybridization of existing information technology (IT) with various industries, IoT can be applied to areas such as smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart appliances, and advanced medical services.
[0007] Therefore, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine-to-machine (M2M), and machine-type communication (MTC) are implemented using techniques such as beamforming, MIMO, and array antennas. The application of cloud RAN, as a big data processing technology, is an example of the convergence of 5G and IoT technologies. Typically, mobile communication systems are developed to provide voice services while ensuring user activity.
[0008] However, mobile communication systems are not only expanding their voice services but also their data services, and have now evolved to the point of providing high-speed data services. However, due to resource shortages and users' demands for high-speed services, more advanced mobile communication systems are needed within the current mobile communication systems providing services. Summary of the Invention
[0009] Technical issues
[0010] One aspect of this disclosure is to provide a method for efficiently transmitting signals in a wireless communication system and an apparatus for using the method. Specifically, the purpose of this disclosure is to provide a method for configuring RACH timing (RO) in a wireless communication system and an apparatus for using the method. Furthermore, the purpose of this disclosure is to provide a method for transmitting and receiving signals based on RO and an apparatus for using the method.
[0011] Technical solution
[0012] In one aspect of the invention, a terminal configured to operate in a wireless communication system is provided, the terminal comprising: a communication module; and a processor configured to control the communication module, wherein the processor is configured to: receive configurations for non-overlapping subband full-duplex (SBFD) symbol sets and non-SBFD symbol sets in a radio frame, wherein the SBFD symbol set includes non-UL symbols in which UL (uplink) subbands are configured; receive configurations for a plurality of random access channel timings (ROs) for SBFD operation on a plurality of symbols in a radio frame; and determine at least one valid RO among the plurality of ROs, wherein the at least one valid RO includes ROs among the plurality of ROs that are consecutively configured across the SBFD symbol set and non-SBFD symbol set.
[0013] In another aspect of the invention, a base station configured to operate in a wireless communication system is provided, the base station comprising: a communication module; and a processor that controls the communication module, wherein the processor is configured to: configure non-overlapping subband full-duplex (SBFD) symbol sets and non-SBFD symbol sets in a radio frame, wherein the SBFD symbol set includes non-UL symbols in which UL (uplink) subbands are configured; configure a plurality of random access channel opportunities (ROs) for SBFD operation on a plurality of symbols in the radio frame; and determine at least one valid RO among the plurality of ROs, wherein the at least one valid RO includes ROs that are consecutively configured across the SBFD symbol set and non-SBFD symbol set among the plurality of ROs.
[0014] In another aspect of the invention, a method performed by a terminal in a wireless communication system is provided, the method comprising: receiving a configuration for a non-overlapping subband full-duplex (SBFD) symbol set and a non-SBFD symbol set in a radio frame, wherein the SBFD symbol set includes non-UL symbols in which a UL (uplink) subband is configured; receiving a configuration for a plurality of random access channel timings (ROs) for SBFD operation on a plurality of symbols in the radio frame; and determining at least one valid RO among the plurality of ROs, wherein the at least one valid RO includes ROs among the plurality of ROs that are consecutively configured across the SBFD symbol set and the non-SBFD symbol set.
[0015] In another aspect of the invention, a method performed by a base station in a wireless communication system is provided, the method comprising: configuring non-overlapping subband full-duplex (SBFD) symbol sets and non-SBFD symbol sets in a radio frame, wherein the SBFD symbol set includes non-UL symbols in which UL (uplink) subbands are configured; configuring a plurality of random access channel opportunities (ROs) for SBFD operations on a plurality of symbols in the radio frame; and determining at least one valid RO among the plurality of ROs, wherein the at least one valid RO includes ROs that are consecutively configured across the SBFD symbol set and non-SBFD symbol set among the plurality of ROs.
[0016] Preferably, among multiple ROs, only ROs configured outside the SBFD symbol set can be identified as invalid ROs.
[0017] Preferably, at least one valid RO may include one of a plurality of ROs configured within a UL subband of the SBFD symbol set.
[0018] Preferably, at least one valid RO may comprise at least N of the multiple ROs located after the last DL non-SBFD symbol. gap N symbols and located after the last synchronization signal / physical broadcast channel (SSB) symbol. gap RO of symbols.
[0019] Preferably, when at least one of the multiple ROs overlaps with a legacy RO in the time domain, the same SSB index as the SSB associated with the legacy RO can be mapped to the synchronization signal / physical broadcast channel block (SSB) associated with at least one RO.
[0020] Preferably, the Physical Random Access Channel (PRACH) can be transmitted / received within at least one valid RO.
[0021] Beneficial effects of the invention
[0022] This disclosure provides a method for efficiently transmitting signals in a wireless communication system and an apparatus for using the method. Furthermore, this disclosure provides a method for configuring an RO (Redirect Array) in a wireless communication system and an apparatus for using the method. Additionally, this disclosure aims to provide a method for transmitting and receiving signals based on an RO and an apparatus for using the method.
[0023] The effects that can be obtained from this disclosure are not limited to those mentioned above, and other effects not mentioned will be clearly understood by those skilled in the art to which this disclosure pertains from the following description. Attached Figure Description
[0024] Figure 1 This diagram illustrates an example of a wireless frame structure used in a wireless communication system.
[0025] Figure 2 This diagram illustrates an example of a downlink (DL) / uplink (UL) timeslot structure in a wireless communication system.
[0026] Figure 3 This is a diagram used to illustrate the physical channels used in 3GPP systems and typical signal transmission methods using those physical channels.
[0027] Figure 4a and Figure 4b The diagram illustrates the SS / PBCH block used for initial cell access in a 3GPP NR system.
[0028] Figure 5a and Figure 5b The diagram illustrates the process of transmitting control information and control channels in a 3GPP NR system.
[0029] Figure 6 The diagram shows a control resource set (CORESET) in a 3GPP NR system that can transmit the Physical Downlink Control Channel (PDCCH).
[0030] Figure 7 The diagram illustrates a method for configuring the PDCCH search space in a 3GPP NR system.
[0031] Figure 8 This is a conceptual diagram illustrating carrier aggregation.
[0032] Figure 9 This is a diagram used to explain single-carrier communication and multi-carrier communication.
[0033] Figure 10 This is a diagram illustrating an example of the application of cross-carrier scheduling technology.
[0034] Figure 11 This is a block diagram illustrating the configuration of a UE and a base station according to an embodiment of the present disclosure.
[0035] Figure 12 and Figure 13 The diagram illustrates the sub-band configuration method.
[0036] Figure 14 The diagram illustrates the Random Access Channel (RACH) process.
[0037] Figures 15 to 16 The diagram shows the legacy RACH configuration information.
[0038] Figure 17 The diagram illustrates the RACH timing (RO) within a time slot.
[0039] Figure 18 The diagram illustrates the scheme for determining the effectiveness of legacy RO systems.
[0040] Figures 19 to 22 The illustration shows an example of an RO configuration method according to the present invention.
[0041] Figures 23 to 32 The illustration shows an example of RO configuration and RO effectiveness determination method according to the present invention.
[0042] Figures 33 to 36 The illustration shows signal transmission and reception according to an example of the present invention. Detailed Implementation
[0043] The terminology used in this specification adopts, as far as possible, commonly used terms that are widely used in light of the functions of this invention; however, these terms may be modified according to the intent, practice, and emergence of new technologies of those skilled in the art. Furthermore, in certain cases, there are terms arbitrarily chosen by the applicant, and in such cases, their meaning will be described in the corresponding descriptive section of this invention. Therefore, it is intended to reveal that the terminology used in this specification should not be analyzed solely based on its name, but rather on its substantive meaning within the entire specification.
[0044] Throughout the specification and subsequent claims, when an element is described as being “connected” to another element, that element may be “directly connected” to the other element or “electrically connected” to the other element via a third element. Furthermore, unless explicitly stated otherwise, the word “comprising” will be understood to imply the inclusion of the stated element without implying the exclusion of any other elements. Additionally, in some exemplary embodiments, limitations such as “greater than or equal to” or “less than or equal to” based on a specific threshold may be appropriately replaced with “greater than” or “less than”, respectively.
[0045] The following technologies can be used in various wireless access systems: such as Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Orthogonal Frequency Division Multiple Access (OFDMA), and Single Carrier-FDMA (SC-FDMA). CDMA can be implemented using wireless technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented using wireless technologies such as Global System for Mobile Communications (GSM), Universal Packet Radio Service (GPRS), and Enhanced Data Rate GSM Evolution (EDGE). OFDMA can be implemented using wireless technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and Evolved UTRA (E-UTRA). UTRA is part of the Universal Mobile Telecommunications System (UMTS). The 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is part of Evolved UMTS (E-UMTS) using Evolved UMTS Terrestrial Radio Access (E-UTRA), and LTE Advanced (A) is an evolved version of 3GPP LTE. 3GPP New Radio (NR) is a system designed separately from LTE / LTE-A and is intended to support Enhanced Mobile Broadband (eMBB), Ultra-Reliable Low Latency Communication (URLLC), and Massive Machine-Type Communication (mMTC) services as required by IMT-2020. For clarity, 3GPP NR is described primarily, but the technical concept of this invention is not limited thereto.
[0046] Unless otherwise specified in this specification, a base station may refer to a next-generation node B (gNB) as defined in 3GPP NR. Furthermore, unless otherwise stated, a terminal may refer to a user equipment (UE). In the following description, for the purpose of facilitating understanding, each element is separately divided into embodiments and described, but each embodiment may be used in conjunction with each other. In this disclosure, the configuration of the UE may be instructive of the configuration by the base station. Specifically, the base station may transmit channels or signals to the UE to configure parameter values used in the UE's operation or wireless communication system.
[0047] Figure 1 This diagram illustrates an example of a wireless frame structure used in a wireless communication system.
[0048] refer to Figure 1 The radio frames (or radio frames) used in 3GPP NR systems can have a duration of 10 ms (Δf). max N f / 100) T c The length of the radio frame is Δf. Furthermore, a radio frame consists of 10 equal-sized subframes (SF). Here, Δf... max=480 10 3 Hz, N f =4096, T c =1 / (Δf ref N f,ref ), Δf ref =15 10 3 Hz, and N f,ref =2048. Numbers from 0 to 9 can be assigned to the 10 subframes within a single radio frame. Each subframe is 1 ms long and can include one or more time slots depending on the subcarrier spacing. More specifically, in 3GPP NR systems, a subcarrier spacing of 15 can be used. 2 μ The subcarrier spacing can be configured as μ = 0, 1, 2, 3, or 4. That is, 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz can be used for the subcarrier spacing. A subframe of 1 ms length can include 2... μ There are 2 time slots. In this case, the length of each time slot is 2. -μ ms. This can range from 0 to 2. μ The number -1 is assigned to 2 within a subframe. μ Each time slot. Furthermore, slots from 0 to 10 can be... 2 μ The number -1 is assigned to a time slot within a radio frame. Time resources can be distinguished by at least one of the radio frame number (also known as the radio frame index), subframe number (also known as the subframe index), and time slot number (or time slot index).
[0049] Figure 2 This diagram illustrates an example of a downlink (DL) / uplink (UL) timeslot structure in a wireless communication system. Specifically, Figure 2 The structure of the resource grid of the 3GPP NR system is shown.
[0050] Each online port has a resource grid. (See reference) Figure 2 A time slot comprises multiple Orthogonal Frequency Division Multiplexing (OFDM) symbols in the time domain and multiple Resource Blocks (RBs) in the frequency domain. An OFDM symbol also refers to a symbol interval. Unless otherwise specified, an OFDM symbol may be simply referred to as a symbol. An RB comprises 12 consecutive subcarriers in the frequency domain. (See reference) Figure 2 The signal transmitted from each time slot can be composed of N size,μ grid,x N RB scSubcarriers and N slot symb The resource grid of OFDM symbols is used for representation. Here, x = DL when the signal is a DL signal, and x = UL when the signal is a UL signal. N size,μ grid,x This represents the number of resource blocks (RBs) based on the subcarrier spacing component μ (x is either DL or UL), and N slot symb Indicates the number of OFDM symbols in the time slot. N RB sc It is the number of subcarriers that make up an RB and N RB sc = 12. OFDM symbols can be referred to as cyclic shift OFDM (CP-OFDM) symbols or discrete Fourier transform extended OFDM (DFT-s-OFDM) symbols according to the multiple access scheme.
[0051] The number of OFDM symbols included in a time slot can vary depending on the length of the cyclic prefix (CP). For example, with normal CP, a time slot includes 14 OFDM symbols, but with extended CP, a time slot can include 12 OFDM symbols. In certain embodiments, extended CP can only be used with a 60 kHz subcarrier spacing. Figure 2 For ease of description, as an example, a time slot is configured with 14 OFDM symbols; however, embodiments of this disclosure can be applied in a similar manner to time slots with different numbers of OFDM symbols. References Figure 2 Each OFDM symbol includes N in the frequency domain. size,μ grid,x N RB sc Subcarriers can be categorized into data subcarriers for data transmission, reference signal subcarriers for reference signal transmission, and guard bands. The carrier frequency is also known as the center frequency (fc).
[0052] An RB can be composed of N in the frequency domain RB sc (For example, 12) consecutive subcarriers are defined. For reference, a resource configured with one OFDM symbol and one subcarrier can be called a resource element (RE) or tone. Therefore, an RB can be configured with N slot symb N RB sc Each resource element in the resource grid can be uniquely defined by a pair of indices (k, l) in a time slot. k can be from 0 to N in the frequency domain. size,μgrid, x N RB sc – 1 is the index assigned, and l can be from 0 to N in the time domain. slot symb – 1 The index assigned.
[0053] To enable the UE to receive or transmit signals from the base station, the UE's time / frequency can be synchronized with the base station's time / frequency. This is because when the base station and the UE are synchronized, the UE can determine the necessary time and frequency parameters to demodulate the DL signal and transmit the UL signal at the correct time.
[0054] Each symbol of a radio frame used in Time Division Duplex (TDD) or unpaired spectrum can be configured with at least one of DL symbol, UL symbol, and flexible symbol. Radio frames used as DL carriers in Frequency Division Duplex (FDD) or paired spectrum can be configured with either DL symbol or flexible symbol, while radio frames used as UL carriers can be configured with either UL symbol or flexible symbol. In a DL symbol, DL transmission is possible, but UL transmission is not. In a UL symbol, UL transmission is possible, but DL transmission is not. A flexible symbol can be determined as being used as either DL or UL based on the signal.
[0055] Information regarding the type of each symbol—that is, information indicating any of DL symbols, UL symbols, and flexible symbols—can be configured using cell-specific or public Radio Resource Control (RRC) signals. Furthermore, information regarding the type of each symbol can be additionally configured using UE-specific or dedicated RRC signals. The base station uses cell-specific RRC signals to inform i) the period of the cell-specific time slot configuration, ii) the number of time slots containing only DL symbols from the beginning of the cell-specific time slot configuration period, iii) the number of DL symbols starting from the first symbol of the time slot immediately following a time slot containing only DL symbols, iv) the number of time slots containing only UL symbols from the end of the cell-specific time slot configuration period, and v) the number of UL symbols starting from the last symbol of the time slot immediately preceding a time slot containing only UL symbols. Here, a symbol not configured with either UL or DL symbols is a flexible symbol.
[0056] When information about symbol type is configured using UE-specific RRC signals, the base station can use cell-specific RRC signals to signal whether a flexible symbol is a DL symbol or a UL symbol. In this case, the UE-specific RRC signals cannot change a DL symbol or UL symbol configured using cell-specific RRC signals to another symbol type. The UE-specific RRC signals can signal the corresponding N of each time slot. slot symbthe number of DL symbols among the symbols and N of the corresponding slot slot symb the number of UL symbols among the symbols. In this case, the DL symbols of the slot may be configured consecutively as the first symbol to the i-th symbol of the slot. In addition, the UL symbols of the slot may be configured consecutively as the j-th symbol to the last symbol of the slot (where i<j). In the slot, a symbol that is not configured with any of the UL symbols and the DL symbols is a flexible symbol.
[0057] Figure 3 is a diagram for explaining physical channels used in a 3GPP system (e.g., NR) and a typical signal transmission method using the physical channels.
[0058] If the power of a UE is turned on or the UE camps on a new cell, the UE performs initial cell search (S101). Specifically, the UE may synchronize with a BS in the initial cell search. To this end, the UE may receive a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) from a base station to synchronize with the base station, and obtain information such as a cell ID. Thereafter, the UE can receive a physical broadcast channel from the base station and obtain broadcast information in the cell.
[0059] When the initial cell search is completed, the UE receives a physical downlink shared channel (PDSCH) according to a physical downlink control channel (PDCCH) and information in the PDCCH, so that the UE can obtain more specific system information than the system information obtained through the initial cell search (S102). Here, the system information received by the UE is cell common system information in radio resource control (RRC) for the UE to properly operate at the physical layer, and is referred to as remaining system information (RSMI) or system information block (SIB) 1.
[0060] When a UE initially accesses a base station or does not have radio resources for signal transmission (when the UE is in RRC_IDLE mode), the UE can perform a random access procedure to the base station (operations S103 to S106). First, the UE can send a preamble via the Physical Random Access Channel (PRACH) (S103) and receive a response message for the preamble from the base station via the PDCCH and the corresponding PDSCH (S104). When the UE receives a valid random access response message, the UE sends data including the UE's identifier to the base station via the Physical Uplink Shared Channel (PUSCH) indicated by the UL permission sent from the base station via the PDCCH (S105). Next, the UE waits for the reception of the PDCCH as an indication from the base station for conflict resolution. If the UE successfully receives the PDCCH via the UE's identifier (S106), the random access procedure is terminated. During the random access procedure, the UE can obtain UE-specific system information necessary for proper operation at the physical layer at the RRC layer. When the UE obtains the UE-specific system information from the RRC layer, the UE enters RRC_CONNECTED mode.
[0061] The RRC layer is used for message generation and management to control communication between the UE and the Radio Access Network (RAN). More specifically, in the RRC layer, the base station and UE can perform broadcasting of cell system information, management of paging message delivery, mobility management and handover, measurement reporting and its control, UE capability management, and storage management, including necessary management of existing data for all UEs in the cell. Typically, because the updates of signals transmitted from the RRC layer (hereinafter referred to as RRC signals) are longer than the transmission / reception period (i.e., transmission time interval, TTI) in the physical layer, RRC signals can remain unchanged for extended periods.
[0062] Following the above process, the UE receives the PDCCH / PDSCH (S107) and transmits the Physical Uplink Shared Channel (PUSCH) / Physical Uplink Control Channel (PUCCH) (S108) as a general UL / DL signal transmission process. Specifically, the UE can receive downlink control information (DCI) via the PDCCH. The DCI may include control information for the UE, such as resource allocation information. Furthermore, the format of the DCI can vary depending on the intended purpose. The uplink control information (UCI) transmitted by the UE to the base station via the UL includes DL / UL ACK / NACK signals, Channel Quality Indicator (CQI), Precoding Matrix Index (PMI), Rank Indicator (RI), etc. Here, CQI, PMI, and RI can be included in the Channel State Information (CSI). In a 3GPP NR system, the UE can transmit control information such as the aforementioned HARQ-ACK and CSI via the PUSCH and / or PUCCH.
[0063] Figure 4a and Figure 4b The diagram illustrates the SS / PBCH block used for initial cell access in a 3GPP NR system.
[0064] When power is on or when the UE wants to connect to a new cell, it can obtain time and frequency synchronization with that cell and perform an initial cell search procedure. The UE can detect the physical cell identifier N of the cell during the cell search procedure. cell ID Therefore, the UE can receive synchronization signals from the base station, such as the primary synchronization signal (PSS) and secondary synchronization signal (SSS), and synchronize with the base station. In this case, the UE can obtain information such as the cell identifier (ID).
[0065] refer to Figure 4a This section will describe synchronization signals (SS) in more detail. Synchronization signals can be classified into PSS and SSS. PSS can be used to obtain time-domain synchronization and / or frequency-domain synchronization, such as OFDM symbol synchronization and slot synchronization. SSS can be used to obtain frame synchronization and cell group ID. (Reference) Figure 4a As per Table 1, the SS / PBCH block can be configured with 20 consecutive RBs (=240 subcarriers) on the frequency axis and 4 consecutive OFDM symbols on the time axis. In this case, within the SS / PBCH block, the PSS is transmitted in the first OFDM symbol via subcarriers 56 to 182, and the SSS is transmitted in the third OFDM symbol. Here, the lowest subcarrier index of the SS / PBCH block is numbered starting from 0. In the first OFDM symbol for transmitting the PSS, the base station does not transmit signals via the remaining subcarriers, i.e., subcarriers 0 to 55 and subcarriers 183 to 239. Furthermore, in the third OFDM symbol for transmitting the SSS, the base station does not transmit signals via subcarriers 48 to 55 and subcarriers 183 to 191. The base station transmits the Physical Broadcast Channel (PBCH) via the remaining REs in the SS / PBCH block, excluding the signals mentioned above.
[0066] [Table 1]
[0067] The SS allows a total of 1008 unique physical layer cell IDs to be divided into 336 physical layer cell identifier groups through a combination of three PSSs and SSSs. Each group includes three unique identifiers, specifically ensuring that each physical layer cell ID is only a part of one physical layer cell identifier group. Therefore, the physical layer cell ID N cell ID = 3N (1) ID + N(2) ID An index N, ranging from 0 to 335, can be used to indicate the physical layer cell identifier group. (1) ID and an index N indicating the range of physical layer identifiers in the physical layer cell identifier group from 0 to 2. (2) ID Uniquely defined. The UE can detect the PSS and identify one of three unique physical layer identifiers. Furthermore, the UE can detect the SSS and identify one of 336 physical layer cell IDs associated with the physical layer identifier. In this case, the sequence d of the PSS... PSS (n) is as follows.
[0068]
[0069] here, And was given as .
[0070] In addition, the sequence d of SSS SSS (n) is as follows.
[0071]
[0072] here, And was given as
[0073] A radio frame with a length of 10 ms can be divided into two half-frames with a length of 5 ms. (Reference) Figure 4b This will describe the time slots for transmitting SS / PBCH blocks in each half-frame. The time slots for transmitting SS / PBCH blocks can be any of cases A, B, C, D, and E. In case A, the subcarrier spacing is 15 kHz and the start time of the SS / PBCH block is ({2, 8} + 14). (n) symbols. In this case, at carrier frequencies of 3 GHz or lower, n = 0 or 1. Furthermore, at carrier frequencies above 3 GHz but below 6 GHz, n can be 0, 1, 2, or 3. In case B, the subcarrier spacing is 30 kHz and the start time of the SS / PBCH block is {4, 8, 16, 20} + 28. n. In this case, at carrier frequencies of 3 GHz or lower, n = 0. Furthermore, at carrier frequencies above 3 GHz and below 6 GHz, n can be 0 or 1. In case C, the subcarrier spacing is 30 kHz and the start time of the SS / PBCH block is ({2, 8} + 14). (n) symbols. In this case, at carrier frequencies of 3 GHz or lower, n = 0 or 1. Furthermore, at carrier frequencies above 3 GHz but below 6 GHz, n can be 0, 1, 2, or 3. In case D, the subcarrier spacing is 120 kHz and the start time of the SS / PBCH block is the ({4, 8, 16, 20} + 28)th symbol. (n) symbols. In this case, at a carrier frequency of 6 GHz or higher, n = 0, 1, 2, 3, 5, 6, 7, 8, 10, 11, 12, 13, 15, 16, 17, 18. In case E, the subcarrier spacing is 240 kHz and the start time of the SS / PBCH block is the ({8, 12, 16, 20, 32, 36, 40, 44} + 56)th symbol. (n) symbols. In this case, at a carrier frequency of 6 GHz or higher, n = 0, 1, 2, 3, 5, 6, 7, 8.
[0074] Figure 5a and Figure 5b The diagram illustrates the process of transmitting control information and using the control channel in a 3GPP NR system. (Reference) Figure 5aThe base station can add a Cyclic Redundancy Check (CRC) masked with a Radio Network Temporary Identifier (RNTI) (e.g., XOR operation) to the control information (e.g., downlink control information (DCI)) (S202). The base station can scramble the CRC with an RNTI value determined according to the purpose / objective of each control information. The common RNTI used by one or more UEs can include at least one of System Information RNTI (SI-RNTI), Paging RNTI (P-RNTI), Random Access RNTI (RA-RNTI), and Transmit Power Control RNTI (TPC-RNTI). In addition, UE-specific RNTIs can include at least one of Cell Temporary RNTI (C-RNTI) and CS-RNTI. Thereafter, the base station can perform rate matching according to the amount of resources used for PDCCH transmission after performing channel coding (e.g., polarity compilation) (S204) (S206). Thereafter, the base station can multiplex the DCI based on the PDCCH structure based on Control Channel Elements (CCE) (S208). Furthermore, the base station can apply additional processes such as scrambling, modulation (e.g., QPSK), interleaving, etc., to the multiplexed DCI (S210), and then map the DCI to the resources to be transmitted. CCE is the basic resource unit used for PDCCH, and a CCE can include multiple (e.g., six) Resource Element Groups (REGs). A REG can be configured with multiple (e.g., 12) REs. The number of CCEs used for a PDCCH can be defined as the aggregation level. In 3GPPNR systems, aggregation levels of 1, 2, 4, 8, or 16 can be used. Figure 5b This is a diagram relating to CCE aggregation levels and PDCCH multiplexing, illustrating the type of CCE aggregation level used for a PDCCH and the CCEs sent in the control area accordingly.
[0075] Figure 6 The diagram shows a control resource set (CORESET) in a 3GPP NR system that can transmit the Physical Downlink Control Channel (PDCCH).
[0076] A CORESET is a time-frequency resource in which PDCCH (i.e., control signals for the UE) is transmitted. Furthermore, a search space, described later, can be mapped to a CORESET. Therefore, the UE can monitor the time-frequency domain designated as a CORESET instead of all frequency bands used for PDCCH reception and decode the PDCCH mapped to the CORESET. The base station can configure one or more CORESETs for each cell for the UE. A CORESET can be configured with up to three consecutive symbols on the time axis. Additionally, a CORESET can be configured in units of six consecutive PRBs on the frequency axis. In the embodiment of Figure 5, CORESET #1 is configured with consecutive PRBs, while CORESET #2 and CORESET #3 are configured with discontinuous PRBs. A CORESET can be located in any symbol of a time slot. For example, in the embodiment of Figure 5, CORESET #1 begins at the first symbol of the time slot, CORESET #2 begins at the fifth symbol of the time slot, and CORESET #9 begins at the ninth symbol of the time slot.
[0077] Figure 7 The diagram illustrates a method for setting up the PUCCH search space in a 3GPP NR system.
[0078] To transmit PDCCH to a UE, each CORESET may have at least one search space. In embodiments of this disclosure, the search space is the set of all time-frequency resources (hereinafter referred to as PDCCH candidates) capable of being used to transmit the UE's PDCCH. The search space may include a common search space that requires UEs of 3GPP NR to search together and a terminal-specific search space or UE-specific search space that requires a specific UE to search. In the common search space, the UE may monitor PDCCHs that are configured to be searched together by all UEs belonging to the same base station cell. Furthermore, a UE-specific search space may be set for each UE, such that the UE monitors the PDCCHs allocated to each UE at search space locations that differ depending on the UE. In the case of a UE-specific search space, the search spaces between UEs may partially overlap and be allocated due to the limited control area that can be allocated PDCCHs. Monitoring the PDCCH includes blind decoding of PDCCH candidates in the search space. When blind decoding is successful, it can be expressed as (successfully) detecting / receiving the PDCCH, and when blind decoding fails, it can be expressed as not detecting / receiving or not successfully detecting / receiving the PDCCH.
[0079] For ease of explanation, a PDCCH scrambled with a Group Common (GC) RNTI previously known to one or more UEs to transmit DL control information to one or more UEs is called a Group Common (GC) PDCCH or a common PDCCH. Furthermore, a PDCCH scrambled with a RNTI of a specific terminal already known to a specific UE to transmit UL scheduling information or DL scheduling information to that specific UE is called a UE-specific PDCCH. Common PDCCHs can be included in the common search space, and UE-specific PDCCHs can be included in either the common search space or the UE-specific PDCCH.
[0080] The base station can signal to each UE or group of UEs via the PDSCH information regarding resource allocation for the Paging Channel (PCH) and Downlink Shared Channel (DL-SCH) as transport channels (i.e., DL clearance) or resource allocation for the Uplink Shared Channel (UL-SCH) and Hybrid Automatic Repeat Request (HARQ) (i.e., UL clearance). The base station can transmit PCH transport blocks and DL-SCH transport blocks via the PDSCH. The base station can also transmit data excluding specific control information or specific service data via the PDSCH. Furthermore, the UE can receive data excluding specific control information or specific service data via the PDSCH.
[0081] The base station can include information in the PDCCH about which UE (one or more UEs) the PDSCH data is sent to and how the PDSCH data will be received and decoded by the corresponding UE, and then send the PDCCH. For example, suppose the DCI sent on a particular PDCCH is CRC masked with RNTI "A", and the DCI indicates that the PDSCH is allocated to radio resource "B" (e.g., frequency location) and indicates transmission format information "C" (e.g., transport block size, modulation scheme, coding information, etc.). The UE uses the RNTI information it possesses to monitor the PDCCH. In this case, if there is a UE performing blind decoding of the PDCCH using RNTI "A", then that UE receives the PDCCH and, based on the information in the received PDCCH, receives the PDSCH indicated by "B" and "C".
[0082] Table 2 shows an example of the Physical Uplink Control Channel (PUCCH) used in a wireless communication system.
[0083] [Table 2]
[0084] PUCCH can be used to send the following UL control information (UCI).
[0085] - Scheduling Request (SR): Information used to request UL UL-SCH resources.
[0086] - HARQ-ACK: A response to the PDCCH (indicating DL SPS release) and / or to a DL transport block (TB) on the PDSCH. HARQ-ACK indicates whether information transmitted on the PDCCH or PDSCH has been received. HARQ-ACK responses include positive ACK (simply ACK), negative ACK (NACK hereinafter), discontinuous transmission (DTX), or NACK / DTX. Here, the terms HARQ-ACK are used interchangeably with HARQ-ACK / NACK and ACK / NACK. Typically, ACK can be represented by a bit value of 1, while NACK can be represented by a bit value of 0.
[0087] - Channel State Information (CSI): Feedback information about the DL channel. The UE generates it based on the CSI-reference signal (RS) transmitted by the base station. MIMO-related feedback information includes the Rank Indicator (RI) and the Precoding Matrix Indicator (PMI). The CSI can be divided into CSI Part 1 and CSI Part 2 based on the information indicated by the CSI.
[0088] In the 3GPP NR system, five PUCCH formats can be used to support various service scenarios, channel environments, and frame structures.
[0089] PUCCH format 0 is a format capable of transmitting 1 or 2 bits of HARQ-ACK information or SR. PUCCH format 0 can be transmitted using one or two OFDM symbols on the time axis and one PRB on the frequency axis. When transmitting PUCCH format 0 in two OFDM symbols, the same sequence on both symbols can be transmitted using different RBs. In this case, the sequence can be a cyclically shifted (CS) sequence from the base sequence used for PUCCH format 0. This allows the UE to obtain frequency diversity gain. Specifically, the UE can, according to M... bit Bit UCI (M) bit = 1 or 2) to determine the cyclic shift (CS) value m cs Furthermore, the 12-length base sequence is based on a predetermined CS value m. cs The cyclically shifted sequence can be mapped to one OFDM symbol of one RB and 12 REs and transmitted. When the number of cyclic shifts available to the UE is 12 and M... bit When M = 1, 1 bit UCI0 and 1 can be mapped to two cyclic shift sequences with a difference of 6, respectively. Furthermore, when M... bitWhen = 2, the 2-bit UCI 00, 01, 11 and 10 can be mapped to four cyclic shift sequences with a difference of 3 in their cyclic shift values.
[0090] PUCCH format 1 can deliver 1 or 2 bits of HARQ-ACK information or SR. PUCCH format 1 can be transmitted using consecutive OFDM symbols on the time axis and one PRB on the frequency axis. Here, the number of OFDM symbols occupied by PUCCH format 1 can be one of 4 to 14. More specifically, it can be used for M... bit BPSK modulation is performed using a UCI of 1. The UE can then utilize Quadrature Phase Shift Keying (QPSK) to modulate the M... bit The signal is modulated using a UCI of 2. The signal is obtained by multiplying the modulated complex-valued symbol d(0) by a sequence of length 12. In this case, the sequence can be the base sequence used for PUCCH format 0. The UE transmits the obtained signal by extending the even-numbered OFDM symbols assigned to PUCCH format 1 with a time-axis orthogonal overlay code (OCC). PUCCH format 1 determines the maximum number of different UEs multiplexed in an RB based on the length of the OCC to be used. The demodulation reference signal (DMRS) can be extended with the OCC and mapped to the odd-numbered OFDM symbols of PUCCH format 1.
[0091] PUCCH Format 2 can deliver more than 2 bits of UCI. PUCCH Format 2 can be transmitted via one or two OFDM symbols on the time axis and one or more RBs on the frequency axis. When transmitting PUCCH Format 2 in two OFDM symbols, the sequences transmitted in different RBs through the two OFDM symbols can be identical to each other. Here, the sequence can be multiple modulated complex-valued symbols d(0), ..., d(M). symbol -1). Here, M symbol It can be M bit / 2. Through this, the UE can obtain frequency diversity gain. More specifically, for M... bit Bit UCI (M) bit >2) Perform bit-level scrambling, QPSK modulation, and map it to one or two OFDM symbols' RBs. Here, the number of RBs can be one from 1 to 16.
[0092] PUCCH format 3 or PUCCH format 4 can deliver more than 2 bits of UCI. PUCCH format 3 or PUCCH format 4 can be transmitted via consecutive OFDM symbols on the time axis and one PRB on the frequency axis. The number of OFDM symbols occupied by PUCCH format 3 or PUCCH format 4 can be one of 4 to 14. Specifically, the UE utilizes 2 / 3 binary phase shift keying (BPSK) or QPSK to transmit M... bit Bit UCI (M) bit >2) Modulate to generate complex numerical symbols d(0) to d(M) symb -1). Here, when using π / 2-BPSK, M symb = M bit However, when using QPSK, M symb = M bit / 2. The UE may not apply block unit extension to PUCCH format 3. However, the UE may use a 12-length PreDFT-OCC to apply block unit extension to one RB (i.e., 12 subcarriers), allowing PUCCH format 4 to have two or four multiplexing capabilities. The UE performs transmit precoding (or DFT precoding) on the extended signal and maps it to each RE to transmit the extended signal.
[0093] In this scenario, the number of Restricted Blocks (RBs) occupied by PUCCH format 2, PUCCH format 3, or PUCCH format 4 can be determined based on the length of the UCI sent by the UE and the maximum coding rate. When the UE uses PUCCH format 2, it can send HARQ-ACK and CSI information together via PUCCH. When the number of RBs that the UE can send exceeds the maximum number of RBs that can be used with PUCCH format 2, PUCCH format 3, or PUCCH format 4, the UE can send only the remaining UCI information without sending some UCI information, based on the priority of the UCI information.
[0094] PUCCH format 1, PUCCH format 3, or PUCCH format 4 can be configured using the RRC signal to indicate frequency hopping in the time slot. When frequency hopping is configured, the index of the RB to be hopped can be configured using the RRC signal. When PUCCH format 1, PUCCH format 3, or PUCCH format 4 is transmitted via N OFDM symbols on the time axis, the first transition can have floor (N / 2) OFDM symbols and the second transition can have ceiling (N / 2) OFDM symbols.
[0095] PUCCH format 1, PUCCH format 3, or PUCCH format 4 can be configured to be repeatedly transmitted in multiple time slots. In this case, the number K of time slots in which the PUCCH is repeatedly transmitted can be configured via an RRC signal. The repeatedly transmitted PUCCH must begin at a constant position in the OFDM symbol within each time slot and have a constant length. When one of the OFDM symbols in the time slot where the UE should transmit the PUCCH is indicated as a DL symbol via an RRC signal, the UE can choose not to transmit the PUCCH in the corresponding time slot and delay the transmission of the PUCCH to the next time slot.
[0096] In 3GPP NR systems, a UE can perform transmission / reception using a bandwidth less than or equal to the carrier (or cell) bandwidth. For this purpose, the UE can be configured with a bandwidth portion (BWP) consisting of a continuous bandwidth comprising a portion of the carrier's bandwidth. A UE operating under TDD or in unpaired spectrum can receive up to four DL / UL BWP pairs for one carrier (or cell). Furthermore, a UE can activate one DL / UL BWP pair. A UE operating under FDD or in paired spectrum can receive up to four DL BWPs on a downlink carrier (or cell) and up to four UL BWPs on an uplink carrier (or cell). For each carrier (or cell), the UE can activate one DL BWP and one UL BWP. The UE may not receive or transmit in time-frequency resources other than the activated BWP. The activated BWP can be referred to as the active BWP.
[0097] The base station can indicate the active BWP among the BWPs configured by the UE via downlink control information (DCI). The BWP indicated by the DCI is activated, while other configured BWPs are deactivated. In a TDD-operated carrier (or cell), the base station can include a Bandwidth Part Indicator (BPI) indicating the active BWP in the DCI of the scheduling PDSCH or PUSCH to change the UE's DL / UL BWP pair. The UE can receive the DCI of the scheduling PDSCH or PUSCH and can identify the active DL / UL BWP pair based on the BPI. In the case of a downlink carrier (or cell) operating in FDD, the base station can include a BPI indicating the active BWP in the DCI of the scheduling PDSCH to change the UE's DL BWP. In the case of an uplink carrier (or cell) operating in FDD, the base station can include a BPI indicating the active BWP in the DCI of the scheduling PUSCH to change the UE's UL BWP.
[0098] Figure 8 This is a conceptual diagram illustrating carrier aggregation.
[0099] Carrier aggregation is a method in which a UE uses multiple frequency blocks or (in a logical sense) cells configured with UL resources (or component carriers) and / or DL resources (or component carriers) as a large logical band so that the wireless communication system can use a wider bandwidth. A component carrier can also be referred to by the terms primary cell (PCell), secondary cell (SCell), or primary SCell (PScell). However, for convenience of description, the term "component carrier" will be used below.
[0100] refer to Figure 8 As an example of a 3GPP NR system, the entire system bandwidth can include up to 16 component carriers, and each component carrier can have a bandwidth of up to 400 MHz. Component carriers can include one or more physically contiguous subcarriers. Although in Figure 8 The diagram shows each component carrier with the same bandwidth, but this is merely an example, and each component carrier can have a different bandwidth. Furthermore, although each component carrier is shown as adjacent to each other on the frequency axis, the diagram is shown conceptually, and each component carrier can be physically adjacent to each other or spaced apart.
[0101] Different center frequencies can be used for each component carrier. Alternatively, a common center frequency can be used for physically adjacent component carriers. Assuming in Figure 8 In one embodiment, all component carriers are physically adjacent, so center frequency A can be used in all component carriers. Alternatively, assuming that the component carriers are not physically adjacent to each other, then center frequency A and center frequency B can be used in each component carrier.
[0102] When extending the total system bandwidth through carrier aggregation, the bandwidth used for communication with each UE can be defined on a component carrier basis. UE A can use 100 MHz as the total system bandwidth and perform communication using all five component carriers. UEs B1-B5 can perform communication using only 20 MHz bandwidth and one component carrier. UEs C1 and C2 can each use 40 MHz bandwidth and two component carriers for communication. These two component carriers can be logically / physically adjacent or non-adjacent. UE C1 represents the case of using two non-adjacent component carriers, while UE C2 represents the case of using two adjacent component carriers.
[0103] Figure 9 This is a diagram used to illustrate single-carrier and multi-carrier communication. Specifically, Figure 9 (a) shows the single-carrier subframe structure and Figure 9 (b) shows the multi-carrier subframe structure.
[0104] refer to Figure 9 (a) In FDD mode, a typical wireless communication system can perform data transmission or reception using a DL band and a corresponding UL band. In another specific embodiment, in TDD mode, the wireless communication system can divide radio frames into UL time units and DL time units in the time domain, and perform data transmission or reception using the UL / DL time units. (See reference...) Figure 9 (b) It is possible to aggregate three 20 MHz component carriers (CCs) into each of the UL and DL, enabling a bandwidth of 60 MHz. Each CC can be adjacent to or not adjacent to each other in the frequency domain. Figure 9 (b) illustrates a case where the bandwidth of the UL CC and the DL CC are the same and symmetrical, but the bandwidth of each CC can be determined independently. Furthermore, asymmetric carrier aggregation with different numbers of UL CCs and DL CCs is possible. The DL / UL CCs allocated / configured to a specific UE via RRC can be referred to as the serving DL / UL CCs for that specific UE.
[0105] A base station can communicate with a UE by activating some or all of the UE's serving CCs or by deactivating some CCs. The base station can change the CCs to be activated / deactivated, and can change the number of CCs to be activated / deactivated. If the base station allocates CCs available to the UE as cell-specific or UE-specific, at least one of the allocated CCs will not be deactivated unless the CC allocation for the UE is completely reconfigured or the UE is handed over. A CC that is not deactivated by the UE is called the primary CC (PCC) or primary cell (PCell), while CCs that the base station can freely activate / deactivate are called secondary CCs (SCCs) or secondary cells (SCells).
[0106] Meanwhile, 3GPP NR uses the concept of cells to manage radio resources. A cell is defined as a combination of DL resources and UL resources, i.e., a combination of DL CC and UL CC. A cell can be configured with DL resources alone, or it can be configured with a combination of DL resources and UL resources. When carrier aggregation is supported, the link between the carrier frequencies of DL resources (or DL CC) and UL resources (or UL CC) can be indicated by system information. The carrier frequency refers to the center frequency of each cell or CC. The cell corresponding to a PCC is called a PCell, and the cell corresponding to an SCC is called an SCell. The carrier corresponding to a PCell in DL is the DL PCC, and the carrier corresponding to a PCell in UL is the UL PCC. Similarly, the carrier corresponding to an SCell in DL is the DL SCC, and the carrier corresponding to an SCell in UL is the UL SCC. Depending on the UE's capabilities, a serving cell can be configured with one PCell and zero or more SCells. In the case of a UE in the RRC_CONNECTED state but not configured for carrier aggregation or not supporting carrier aggregation, only one serving cell is configured with only a PCell.
[0107] As mentioned above, the term "cell" used in carrier aggregation is distinguished from the term "cell" referring to a geographical area that provides communication services through a base station or an antenna array. That is, a component carrier can also be referred to as a scheduled cell, a scheduled cell, a primary cell (PCell), a secondary cell (SCell), or a primary SCell (PScell). However, to distinguish between cells representing a geographical area and cells in carrier aggregation, in this disclosure, cells in carrier aggregation are referred to as CCs, and cells representing a geographical area are referred to as cells.
[0108] Figure 10 This diagram illustrates an example of cross-carrier scheduling technology. When cross-carrier scheduling is set up, the control channel transmitted via the first CC can use the Carrier Indicator Field (CIF) to schedule the data channel transmitted via either the first CC or the second CC. The CIF is included in the DCI. In other words, a scheduling cell is set up, and the DL license / UL license transmitted in the PDCCH area of that scheduling cell schedules the PDSCH / PUSCH of the scheduled cell. That is, there is a search area for multiple component carriers in the PDCCH area of the scheduling cell. A PCell can essentially be a scheduling cell, and a specific SCell can be designated as a scheduling cell by a higher layer.
[0109] exist Figure 10In the embodiment, it is assumed that three DL CCs are combined. Here, it is assumed that DL component carrier #0 is a DLPCC (or PCell), and DL component carriers #1 and #2 are DL SCCs (or SCells). Furthermore, it is assumed that the DLPCC is set as a PDCCH monitoring CC. When cross-carrier scheduling is not configured via UE-specific (or UE group-specific or cell-specific) higher-layer signaling, CIF is disabled, and each DL CC can transmit only the PDCCH for scheduling its PDSCH according to the NR PDCCH rules without CIF (non-cross-carrier scheduling, self-carrier scheduling). Meanwhile, if cross-carrier scheduling is configured via UE-specific (or UE group-specific or cell-specific) higher-layer signaling, CIF is enabled, and a specific CC (e.g., DL PCC) can use CIF to transmit not only the PDCCH for scheduling DL CC A but also the PDCCH for scheduling another CC (cross-carrier scheduling). On the other hand, no PDCCH is transmitted in another DL CC. Therefore, the UE monitors the PDCCH excluding CIF to receive the PDSCH of self-carrier scheduling depending on whether cross-carrier scheduling is configured for the UE, or monitors the PDCCH including CIF to receive the PDSCH of cross-carrier scheduling.
[0110] on the other hand, Figure 9 and Figure 10 The diagram illustrates the subframe structure of a 3GPP LTE-A system, and the same or similar configuration can be applied to a 3GPP NR system. However, in a 3GPP NR system, Figure 9 and Figure 10 Subframes can be replaced with time slots.
[0111] Figure 11 This is a block diagram illustrating the configuration of a UE and a base station according to an embodiment of the present disclosure.
[0112] In embodiments of this disclosure, the UE can be implemented using various types of wireless communication devices or computing devices that are guaranteed to be portable and mobile. The UE can be referred to as User Equipment (UE), Station (STA), Mobile Subscriber (MS), etc. Furthermore, in embodiments of this disclosure, the base station controls and manages cells (e.g., macro cells, femtocells, picocells, etc.) corresponding to the service area, and performs functions such as signal transmission, channel designation, channel monitoring, self-diagnosis, and relaying. The base station can be referred to as Next Generation Node B (gNB) or Access Point (AP).
[0113] As shown in the accompanying drawings, the UE 100 according to an embodiment of the present disclosure may include a processor 110, a communication module 120, a memory 130, a user interface 140, and a display unit 150.
[0114] First, the processor 110 can execute various instructions or procedures and process data within the UE 100. Furthermore, the processor 110 can control the overall operation of each unit including the UE 100 and can control the transmission / reception of data between the units. Here, the processor 110 can be configured to perform operations according to the embodiments described in this disclosure. For example, the processor 110 can receive time slot configuration information, determine a time slot configuration based on the time slot configuration information, and perform communication according to the determined time slot configuration.
[0115] Next, the communication module 120 can be an integrated module that uses a wireless communication network to perform wireless communication and uses a wireless LAN to perform wireless LAN access. For this purpose, the communication module 120 can include multiple network interface cards (NICs), such as cellular communication interface cards 121 and 122 and an unlicensed band communication interface card 123, either internally or externally. In the accompanying drawings, the communication module 120 is shown as an integral integrated module; however, unlike the drawings, each network interface card can be arranged independently depending on the circuit configuration or usage.
[0116] Cellular communication interface card 121 can transmit or receive radio signals with at least one of base station 200, external device, and server using a mobile communication network and provide cellular communication services in a first frequency band based on instructions from processor 110. According to an embodiment, cellular communication interface card 121 may include at least one NIC module using a frequency band less than 6 GHz. At least one NIC module of cellular communication interface card 121 can independently perform cellular communication with at least one of base station 200, external device, and server in accordance with cellular communication standards or protocols in the sub-6 GHz frequency band supported by the corresponding NIC module.
[0117] Cellular communication interface card 122 can transmit or receive radio signals with at least one of base station 200, external device, and server using a mobile communication network and provide cellular communication services in a second frequency band based on instructions from processor 110. According to an embodiment, cellular communication interface card 122 may include at least one NIC module using a frequency band greater than 6 GHz. At least one NIC module of cellular communication interface card 122 can independently perform cellular communication with at least one of base station 200, external device, and server in accordance with cellular communication standards or protocols in a frequency band above 6 GHz supported by the corresponding NIC module.
[0118] The unlicensed frequency band communication interface card 123 transmits or receives radio signals with at least one of the base station 200, external devices, and servers by using a third frequency band that is an unlicensed frequency band, and provides unlicensed frequency band communication services based on instructions from the processor 110. The unlicensed frequency band communication interface card 123 may include at least one NIC module using an unlicensed frequency band. For example, the unlicensed frequency band may be a band of 2.4 GHz, 5 GHz, 6 GHz, 7 GHz, or a band higher than 52.6 GHz. At least one NIC module of the unlicensed frequency band communication interface card 123 can independently or dependently perform wireless communication with at least one of the base station 200, external devices, and servers according to the unlicensed frequency band communication standards or protocols supported by the corresponding NIC module.
[0119] The memory 130 stores the control program used in the UE 100 and various data used therein. Such a control program may include a prescribed program required to perform wireless communication with at least one of the base station 200, external devices, and servers.
[0120] Next, the user interface 140 includes various input / output means provided in the UE 100. In other words, the user interface 140 can use various input means to receive user input, and the processor 110 can control the UE 100 based on the received user input. Furthermore, the user interface 140 can use various output means to execute output based on instructions from the processor 110.
[0121] Next, the display unit 150 outputs various images on the display screen. The display unit 150 can output various display objects, such as content executed by the processor 110 or a user interface, based on control instructions from the processor 110.
[0122] Furthermore, the base station 200 according to embodiments of the present disclosure may include a processor 210, a communication module 220, and a memory 230.
[0123] First, the processor 210 can execute various instructions or programs and process the internal data of the base station 200. Furthermore, the processor 210 can control the overall operation of each unit in the base station 200 and control the transmission and reception of data between the units. Here, the processor 210 can be configured to perform operations according to the embodiments described in this disclosure. For example, the processor 210 can notify time slot configurations with signals and perform communication based on the time slot configurations notified by the used signals.
[0124] Next, the communication module 220 can be an integrated module that uses a wireless communication network to perform wireless communication and uses a wireless LAN to perform wireless LAN access. For this purpose, the communication module 220 can include multiple network interface cards, such as cellular communication interface cards 221 and 222 and an unlicensed band communication interface card 223, either internally or externally. In the accompanying drawings, the communication module 220 is shown as an integral integrated module; however, unlike the drawings, each network interface card can be arranged independently depending on the circuit configuration or usage.
[0125] Cellular communication interface card 221 can transmit or receive radio signals with at least one of base station 100, external device, and server using a mobile communication network and provide cellular communication services in a first frequency band based on instructions from processor 210. According to an embodiment, cellular communication interface card 221 may include at least one NIC module using a frequency band less than 6 GHz. At least one NIC module of cellular communication interface card 221 can independently perform cellular communication with at least one of base station 100, external device, and server in accordance with cellular communication standards or protocols in a frequency band less than 6 GHz supported by the corresponding NIC module.
[0126] Cellular communication interface card 222 can transmit or receive radio signals with at least one of base station 100, external device, and server using a mobile communication network and provide cellular communication services in a second frequency band based on instructions from processor 210. According to an embodiment, cellular communication interface card 222 may include at least one NIC module using a 6 GHz or higher frequency band. At least one NIC module of cellular communication interface card 222 can independently perform cellular communication with at least one of UE 100, external device, and server in accordance with cellular communication standards or protocols in a 6 GHz or higher frequency band supported by the corresponding NIC module.
[0127] The unlicensed frequency band communication interface card 223 transmits or receives radio signals with at least one of the UE 100, external devices, and servers using a third frequency band that is an unlicensed frequency band, and provides unlicensed frequency band communication services based on instructions from the processor 210. The unlicensed frequency band communication interface card 223 may include at least one NIC module using an unlicensed frequency band. For example, the unlicensed frequency band may be a band of 2.4 GHz, 5 GHz, 6 GHz, 7 GHz, or a band higher than 52.6 GHz. At least one NIC module of the unlicensed frequency band communication interface card 223 can independently or dependently perform wireless communication with at least one of the base station 100, external devices, and servers in accordance with the unlicensed frequency band communication standards or protocols supported by the corresponding NIC module.
[0128] Figure 11This is a block diagram illustrating a UE 100 and a base station 200 according to an embodiment of the present disclosure, and the blocks shown individually are logically divided elements of the device. Therefore, the aforementioned elements of the device can be installed in a single chip or multiple chips depending on the device design. Furthermore, a portion of the configuration of the UE 100, such as a user interface 140, a display unit 150, etc., may be selectively provided in the UE 100. Additionally, the user interface 140, display unit 150, etc., may be additionally provided in the base station 200 if necessary.
[0129] In TDD or unpaired spectrum systems, the base station can configure the time slot format for the UE. The time slot format can refer to the symbol type within the time slot. The symbol type can be at least one of downlink symbols (DL symbols), uplink symbols (UL symbols), or flexible symbols. The base station can configure the symbol type of the time slots in a radio frame for the UE. Flexible symbols can refer to symbols that are not configured as downlink or uplink symbols.
[0130] The UE can be semi-statically configured with information about the type of each symbol in a time slot by receiving information about the type of each symbol in the time slot from the base station via cell-specific or cell-common Radio Resource Control (RRC) signals. Here, cell-specific (or, cell-common or UE-common) RRC signals include tdd-UL-DL-ConfigurationCommon. Furthermore, the UE can be semi-statically configured with information about the type of each symbol in the time slot by receiving information about the type of each symbol in the time slot from the base station via SIB1. Additionally, the UE can be semi-statically configured with information about the type of each symbol in the time slot by receiving information about the type of each symbol in the time slot from the base station via UE-specific or UE-specific RRC signals. The base station can configure / set the type of each symbol in the time slot for the UE using this information.
[0131] When the UE receives type information for each symbol in a time slot from the base station via a cell-specific RRC signal, the information configured by the cell-specific RRC signal may include at least one of the following: 1) the cell-specific time slot configuration period, 2) the number of time slots containing only DL symbols starting from the beginning time slot of the period, 3) the number of DL symbols starting from the first symbol of the time slot immediately following the last time slot containing only DL symbols, 4) the number of time slots containing only UL symbols starting from the last time slot of the period, and 5) the number of UL symbols in the time slot immediately preceding the last time slot containing only uplink symbols (in the direction backward from the last time slot of the period). Here, symbols not configured as DL symbols or UL symbols are flexible symbols. Additionally, when the UE receives information about the type of each symbol in a time slot from the base station via a cell-specific RRC signal, the information about the type of each symbol may include up to two time slot patterns. In such cases, the two patterns can be applied sequentially to symbols in the time domain. DL symbols, UL symbols, and flexible symbols based on cell-specific RRC signals or SIB1 configurations can be referred to as cell-specific DL symbols, cell-specific UL symbols, and cell-specific flexible symbols, respectively.
[0132] When the UE receives information about the type of each symbol in a time slot from the base station via a UE-specific RRC signal, cell-specific flexible symbols can be configured as DL symbols or UL symbols via the UE-specific RRC signal. Here, the UE-specific RRC signal includes tdd-UL-DL-ConfigurationDedicated. In this case, the information configured by the UE-specific RRC signal can include at least one of the following: 1) the index of the time slot within the time slot configuration period, 2) the number of DL symbols starting from the first symbol of the time slot indicated by the index, and 3) the number of UL symbols starting from the last symbol of the time slot indicated by the index. Here, symbols not configured as DL symbols or UL symbols are flexible symbols. Additionally, the UE can be configured such that all symbols in a time slot are DL symbols, or it can be configured such that all symbols in a time slot are UL symbols. The DL symbols, UL symbols, and flexible symbols configured based on the UE-specific RRC signal can be referred to as UE-specific DL symbols, UE-specific UL symbols, and UE-specific flexible symbols, respectively.
[0133] The base station can send information about the time slot format to the UE via the Time Slot Format Indicator (SFI) in DCI format 2_0 contained in the Group Common (GC)-PDCCH. For the UE receiving the information about the time slot format, the GC-PDCCH can be CRC scrambled using the SFI-RNTI. In the following text, the SFI sent via the GC-PDCCH can be described as a dynamic SFI.
[0134] The UE can receive a dynamic SFI via the GC-PDCCH to receive an indication of whether a symbol in a time slot is a cell-specific flexible symbol or a UE-specific flexible symbol, downlink symbol, uplink symbol, or flexible symbol. In other words, only flexible symbols semi-statically configured by the UE can be indicated as one of downlink symbols, uplink symbols, and flexible symbols via the dynamic SFI. The UE may not expect that a semi-statically configured downlink or uplink symbol will be indicated as a different type of symbol by the dynamic SFI. The UE can perform blind decoding in each monitoring cycle configured by the base station to receive the GC-PDCCH in DCI format 2_0 that includes the dynamic SFI. When the UE successfully receives the GC-PDCCH by performing blind decoding, the UE can begin applying information about the time slot format indicated by the dynamic SFI from the time slot in which the GC-PDCCH has been received.
[0135] The base station can configure the UE with combinations of time slot formats that can be indicated by a dynamic SFI. These time slot format combinations can be used for each of 1 to 256 time slots, and the UE can be configured with a time slot format combination for one of these 1 to 256 time slots via a dynamic SFI. The dynamic SFI can include an index indicating the time slot to which the time slot format combination is applied. Table 3 shows the time slot format combinations for each time slot (see 3GPP TS38.213).
[0136] [Table 3]
[0137] In Table 3, D represents the downlink symbol, U represents the uplink symbol, and F represents the flexible symbol. As shown in Table 3, up to two DL / UL handovers are allowed within a time slot.
[0138] In this specification, the terms “configuration,” “setting,” and “instruction” are used interchangeably. That is, the terms “configured,” “set,” and “instructed” can have the same meaning, and similarly, the terms “configured,” “set,” and “instructed” can have the same meaning.
[0139] Subband-based full-duplex: spectrum partitioning
[0140] Figures 12 to 13 The illustration shows a sub-band configuration method according to an embodiment of the present disclosure.
[0141] In TDD or unpaired spectrum, when configuring or indicating time slot formats for a UE, only a limited number of time-domain resources can be allocated as UL resources, leading to problems such as reduced uplink coverage, increased latency, and reduced capacity. To address this issue, solutions are being discussed that divide specific time-domain resources within a cell into multiple sub-bands in the frequency domain and use them for both downlink reception and uplink transmission.
[0142] refer to Figure 12 The UE can receive TDD configuration information to be semi-statically configured with a time slot format, or it can receive SFI to dynamically indicate the time slot format. Here, the TDD configuration information can include cell-specific (or cell-common) TDD configuration information (e.g., tdd-UL-DL-ConfigurationCommon) or UE-specific TDD configuration information (e.g., tdd-UL-DL-ConfigurationDedicated). D (or DL) represents downlink, U (or UL) represents uplink, F represents flexible, and D / F (or DL / F) represents D (or DL) or F. The UE can then be configured with multiple subbands in the frequency domain for a specific time-domain resource (e.g., at least one time slot / symbol) (n2 to n3) via subband configuration / indication from the base station. The subband configuration / indication information can include information about a set of consecutive RBs (e.g., starting RB, number of RBs, etc.). Multiple subbands can have the same or different formats. The subband format can include downlink (D or DL) subbands and uplink (U or UL) subbands. The D (or DL) subband may include one or more downlink RBs, and the U (or UL) subband may include one or more uplink RBs. A downlink RB may refer to a resource available for downlink reception, and an uplink RB may refer to a resource available for uplink transmission.
[0143] refer to Figure 13Multiple subbands can be (dynamically) indicated to the UE in the frequency domain relative to downlink (D or DL) slots or symbols configured semi-statically (e.g., TDD configuration) or dynamically indicated from the base station (e.g., SFI). In the figure, multiple subbands include two D (or DL) subbands and one U (or UL) subband. In such a case, resources configured or indicated for receiving downlink signals or channels in the same symbol may overlap in the time domain with resources configured or indicated for transmitting uplink signals or channels. For example, when downlink reception (e.g., CSI-RS) is scheduled in the D (or DL) subband and uplink transmission (e.g., PUSCH) is scheduled in the U (or UL) subband, reception and transmission may overlap in at least one symbol (the 5th or 6th symbol). Simultaneously, when configuring subbands, the base station can perform both downlink transmission and uplink reception (full-duplex) in the same subband symbol, while a UE that only supports half-duplex can only perform either downlink reception or uplink transmission in the same subband symbol. Here, a subband symbol refers to the symbol used to configure a subband. Therefore, when downlink reception and uplink transmission overlap in the same subband symbol (see the circled area in the figure), the UE and the base station can operate as follows.
[0144] 1) When the downlink reception and uplink transmission belong to different UEs, - Each UE is able to perform downlink reception or uplink transmission without restrictions.
[0145] - The base station can perform downlink transmission and uplink reception simultaneously.
[0146] 2) When the downlink reception and uplink transmission belong to the same UE, - A UE cannot perform downlink reception and uplink transmission simultaneously. Therefore, to resolve the conflict between downlink reception and uplink transmission, the UE's downlink reception and / or uplink transmission can be restricted.
[0147] The base station is capable of performing downlink transmission and uplink reception simultaneously. However, because the UE's downlink reception and / or uplink transmission are restricted, the same restrictions can be applied to the base station.
[0148] Here, the conflict situation may not be limited to the case where multiple subbands in the frequency domain are dynamically assigned to the UE for base station semi-static configuration or dynamic assignment of downlink time slots or symbols. That is to say, the conflict situation can also include the case where multiple subbands in the frequency domain are semi-statically assigned to the UE for base station semi-static configuration or dynamic assignment of downlink time slots or symbols.
[0149] Furthermore, conflict scenarios may not be limited to situations where multiple subbands in the frequency domain are dynamically assigned to flexible time slots or symbols for the UE's semi-static or dynamic base station configuration. In other words, conflict scenarios can also include situations where multiple subbands in the frequency domain are semi-statically assigned to flexible time slots or symbols for the UE's semi-static or dynamic base station configuration.
[0150] Random Access Channel Procedure (RACH)
[0151] Figure 14 The diagram illustrates the random access process. Figure 15 and Figure 16 The diagram shows the RACH configuration information. Figure 17 The image shows a RACH resource.
[0152] Reference Figure 14 The UE can receive RACH configuration information from the base station (S1402). RACH configuration information can be received through the RACHConfigCommon information in the SIB. RACHConfigCommon can include rach-ConfigGeneric information. Figure 15 and Figure 16 The diagram illustrates the RACH-ConfigCommon and rach-ConfigGeneric information used in legacy NR systems. Based on the PRACH configuration index in the rach-ConfigGeneric information, PRACH slots can be periodically configured within radio frame units (see 3GPP TS38.211 V16.9.0 (2022-06), Tables 6.3.3.2-2 to 6.3.3.2-4). Within a PRACH slot, one or more ROs (RACH timings or PRACH timings) can be configured in the time domain and one or more ROs can be configured in the frequency domain. Depending on the PRACH / preamble format, the number of symbols occupied by an RO and the number of RBs can be defined differently. The frequency resource information for ROs configured within a PRACH slot can be determined based on msg1-FDM and msg1-FrequencyStart in the rach-ConfigGeneric information. msg1-FDM indicates the number of ROs in the frequency domain. msg1-FrequencyStart indicates the starting position of the RO in the frequency domain (e.g., the PRB index). msg1FrequencyStart indicates the offset (e.g., the number of RBs) from the minimum RB (e.g., PRB#0) of the UL BWP to the starting RO. Figure 17 The diagram illustrates multiple Remote Routers (ROs) configured within a PRACH time slot. It shows a scenario where two ROs are configured in the time domain (TDM) and two ROs are configured in the frequency domain (FDM) within a PRACH time slot. Figure 17The illustration shows a case where the symbol set of an RO consists of seven symbols in the time domain. The RO start position in the frequency domain (e.g., PRB#2) is configured based on msg1-FrequencyStart. The value of msg1-FrequencyStart can be 0 to (the number of RBs within the frequency band of UL BWP-1).
[0153] Subsequently, the terminal can send a PRACH (S1404) via the RO. Here, the RO can be selected from the set of ROs within the PRACH slot. Specifically, the RO can be selected from the valid ROs in the set of ROs within the PRACH slot. For information on valid ROs, please refer to the section given later. Figure 18 The description continues. Afterward, the terminal may receive a Random Access Response (RAR) (S1406).
[0154] Signal transmission and reception based on RO effectiveness
[0155] The validity of an RO can be determined based on the PRACH slot format configuration. The terminal can perform uplink transmission (e.g., PRACH) or downlink reception (e.g., PDSCH, CSI-RS) based on the validity of the RO. Specifically, the terminal can perform PRACH transmission within a valid RO. Furthermore, when a valid RO (including gap symbols) and downlink reception (e.g., PDSCH reception or CSI-RS reception) overlap in the time domain, the terminal can skip downlink reception. Conversely, when an RO is invalid, the terminal cannot perform PRACH transmission for the corresponding RO. Moreover, even if an RO (including gap symbols) and downlink reception overlap in the time domain, the terminal can still perform downlink reception normally when the RO is invalid. In existing NR systems, the terminal can determine the valid RO in the TDD or unpaired spectrum as follows. Specifically, the valid RO can be determined as follows, depending on whether the terminal is configured with tdd-UL-DL-ConfigurationCommon as information about symbol type. The tdd-UL-DL-ConfigurationCommon can be received via cell-specific (or cell-common) RRC signals or System Information Block 1 (SIB1).
[0156] - When the terminal is not configured with tdd-UL-DL-ConfigurationCommon: When the RO in the PRACH slot is not earlier in the time domain than the SS / PBCH block in the same PRACH slot and at least N after the received symbol of the last SS / PBCH block. gap When a symbol begins, the corresponding RO can be valid. Here, the last received symbol of the last SS / PBCH block refers to the last received symbol of the last SS / PBCH block preceding the corresponding RO.
[0157] - When the terminal is configured with tdd-UL-DL-ConfigurationCommon ( Figure 18 ): When the RO in a PRACH slot is on a UL symbol, the corresponding RO is valid. Furthermore, (when at least a portion of the RO is outside the UL symbol) when the RO in a PRACH slot is not before the SS / PBCH block of the same PRACH slot in the time domain and is at least N after the last DL symbol. gap The first symbol ( Figure 18 (a) and at least N after the last SS / PBCH block receive symbol gap The first symbol ( Figure 18 (b) In this case, the corresponding RO can be valid. Here, the last DL symbol refers to the last DL symbol before the corresponding RO on the DL symbol set configured by tdd-UL-DL-ConfigurationCommon. In the figure, the D symbol refers to the cell-common (or cell-specific) DL symbol, the F symbol refers to the cell-common (or cell-specific) flexible symbol, and the U symbol refers to the cell-common (or cell-specific) UL symbol.
[0158] Table 4 shows N gap In the case of PRACH preamble format B4, N gap =0 is true.
[0159] [Table 4]
[0160] Example: Subband-based full-duplex and signal / channel transmission and reception
[0161] First, let's summarize the terminology used in this disclosure.
[0162] - Subband-based full-duplex: This refers to a method that supports simultaneous transmission and reception using subbands within a cell / BWP. This can be called Subband Non-overlapping Full-Duplex (SBFD). Here, a subband refers to the frequency band configured / indicated within a cell / BWP for SBFD operation. A subband can consist of a set of consecutive (P)RBs. For example, a UL subband can consist of a set of (P)RBs where UL transmission is possible (i.e., UL-available RBs). Similarly, a DL subband can consist of a set of (P)RBs where DL transmission is possible (i.e., DL-available RBs). Examples of subband configurations / formats can be found in [reference needed]. Figures 12 to 13For example, in the case of unpaired spectrum (i.e., TDD cell / BWP), DL and UL subbands can be configured on DL slots / symbols, or DL and UL subbands can be configured on flexible slots / symbols. Here, the DL subbands on the DL slots / symbols can be explicitly configured or implicitly configured outside the UL subbands. A slot / symbol configured with subbands for SBFD operation in the frequency domain can be referred to as an SBFD slot / symbol. When subbands are configured in a cell / BWP, the cell / BWP can include the SBFD slot / symbol duration where TDM is configured in the time domain and the duration of non-SBFD slots or symbols where no subbands are configured.
[0163] - SBFD Slot / Symbol Duration: This refers to the duration for which a subband is configured / indicated in the cell / BWP. For example, the SBFD slot / symbol duration includes the duration for which a subband (e.g., DL and / or UL subband) is configured / indicated in the frequency domain. Here, the duration can include slots and / or symbols (or symbol sets). The SBFD slot / symbol duration can include one or more subbands in the frequency domain. When multiple subbands are configured within the SBFD slot / symbol duration, the subbands are FDMed. Within the SBFD slot / symbol duration, multiple subbands (DL subbands or UL subbands) can be configured to not overlap in the frequency domain. The SBFD slot / symbol duration can simply be referred to as the SBFD duration.
[0164] - Non-SBFD Time Slot / Symbol Duration: This refers to the duration during which a subband is not configured / indicated in a cell / BWP. Non-SBFD time slot / symbol duration includes the duration during which a DL or UL subband is not configured / indicated. Here, duration can include time slots and / or symbols (or symbol sets). Non-SBFD time slot / symbol duration refers to legacy duration or normal duration. Depending on the time slot format, non-SBFD time slot / symbol duration includes at least one of DL symbols, flexible symbols, and UL symbols. For example, when a subband is not configured / indicated in a UL BWP, non-SBFD time slot / symbol duration includes UL time slots / symbols. Non-SBFD time slot / symbol duration can simply be referred to as non-SBFD duration.
[0165] - Legacy NR systems: These are systems that operate using traditional NR methods because they do not support or are configured for SBFD operations.
[0166] - SBFD-aware UE: Refers to a terminal that is aware of SBFD operations. An SBFD-aware UE can perform the various SBFD operations described in this specification. It can be simply referred to as an SBFD UE.
[0167] - SBFD-unaware UE: Refers to a terminal that is unaware of SBFD operations. This includes terminals operating in legacy NR systems (e.g., existing NR terminals). It can be simply referred to as a non-SBFD UE or a legacy UE.
[0168] - SBFD-DL symbol: Indicates a subband configuration for performing SBFD operations on symbols configured as DL by tdd-UL-DL-ConfigurationCommon. The subband may include UL subbands and / or DL subbands.
[0169] - SBFD-FL symbol: Indicates the configuration of subbands so that SBFD operation can be performed for symbols configured as flexible (F) by tdd-UL-DL-ConfigurationCommon. Subbands may include UL subbands and / or DL subbands.
[0170] - SBFD RO: Indicates the RO configured for a terminal that supports SBFD operation (i.e., an SBFD-aware UE). An SBFD RO can be configured using either a legacy (P)RACH configuration or a new (P)RACH configuration. An SBFD-aware UE can perform PRACH transmissions within a valid SBFD RO. Legacy UEs cannot recognize SBFD ROs. Legacy ROs and SBFD ROs coexist in the system. To distinguish it from a legacy RO, an SBFD RO can be simply referred to as a new RO.
[0171] The problem to be solved in this invention relates to a situation where a terminal is semi-statically configured or dynamically indicated with multiple subbands in the frequency domain for downlink time slots or symbols (simply put, downlink spacing), and / or flexible time slots or symbols (simply put, flexible spacing) semi-statically configured or dynamically indicated by the base station. This relates to the schemes of existing legacy NR systems (see...). Figure 18 Even if an uplink subband is configured in the downlink interval, a Remote Router (RO) cannot be configured in the downlink interval, or even if an RO is configured, the RO in the downlink interval is considered invalid. Furthermore, according to the scheme of existing legacy NR systems (see...),... Figure 18 When a RO is configured in a flexible interval, the validity of the RO is determined in a limited manner, for example, by considering the gap after the DL symbol or the gap after the symbol allocated for the SS / PBCH block. As described above, when following a legacy NR system, if the terminal is configured with an uplink subband for the downlink interval and / or a flexible interval semi-statically configured or dynamically indicated by the base station, then the RO is configured in the corresponding uplink subband and a PRACH preamble is transmitted.
[0172] - Methods for configuring RO in idle / inactive mode or RRC connected mode, and methods for configuring RO in the UE.
[0173] In this disclosure, a method for configuring RO for a UE in idle mode, inactive mode, or RRC connection mode is proposed when the UE is semi-statically configured or dynamically indicated in the frequency domain with multiple subbands during downlink duration and / or when the UE is semi-statically configured or dynamically indicated from the base station for a flexible duration, or when the uplink subband is semi-statically configured or dynamically indicated.
[0174] As a first embodiment, when a UE utilizes multiple subbands in the frequency domain that are semi-statically or dynamically configured in the downlink or flexible duration, or when uplink subbands are semi-statically or dynamically configured, a method for configuring RO configuration for UEs supporting subband operation with the same (common) RO configuration can be considered through higher-layer (e.g., RRC) parameters configured in legacy NR systems. Here, a UE supporting subband operation can support multiple subband operations in the frequency domain. Figure 15 and 16 The diagram illustrates the configuration of higher-level (e.g., RRC) information for RO in a legacy NR system. Figure 15 and 16 The Rach-ConfigCommon and Rach-ConfigGeneric information are illustrated separately, and more detailed information can be found in 3GPP TS 38.331 Rel-16. For convenience, the RRC information of legacy NR systems is referred to as legacy RRC information (e.g., legacy Rach-ConfigCommon, legacy Rach-ConfigGeneric).
[0175] In this scenario, the ROs of a UE supporting subband operation can be configured using RO configurations for flexible or uplink durations in legacy NR systems without additional processing. In this case, all ROs that fully or partially overlap with downlink subbands configured in the downlink duration on the frequency axis can be considered invalid. That is, ROs configured outside the UL subband in SBFD symbols (i.e., UL-available RBs) can be identified as invalid ROs. However, RO configurations in uplink subbands configured in the downlink duration may be inefficient in this scenario. To compensate for this, the following options can be considered.
[0176] As an example, this invention proposes a method for configuring ROs from the starting RB index of an uplink subband within a flexible interval configured with uplink (U) subbands in a downlink interval; that is, in the downlink interval configured with uplink subbands, the starting position of the RO on the frequency axis is such that, regardless of the configuration of msg-1-FrequencyStart in the legacy Rach-ConfigGeneric, the offset of the lowest PRACH transmission timing on the frequency is configured with reference to the starting RB index (e.g., the lowest RB index, RB#0) at the allocated uplink subband (hereinafter referred to as msg-1-FrequencyStart_SBFD), so that as many corresponding RACH resources as possible are configured within the BW of the uplink subband. Here, msg-1-FrequencyStart_SBFD is determined based on the legacy RO configuration information. Therefore, in the SBFD slot / symbol, msg-1-FrequencyStart can be interpreted as configuring the offset value with reference to the starting RB index of the U subband. In other words, msg-1-FrequencyStart can be interpreted differently depending on the type of symbol configured for RO. Furthermore, when a guard band is required to account for inter-subband interference between downlink and uplink subbands in the frequency domain, at least one PRB spaced apart from the downlink subband can be set as an offset, and the RO can be configured starting from the RB index of the uplink subband after the corresponding offset, thus allocating RACH resources.
[0177] Figure 19 The illustration shows an example of configuring the RO from the starting RB index of the uplink (U) subband during the downlink duration and / or the flexible duration configured using the uplink (U) subband, according to this embodiment. When in Figure 18 When a guard band is required between subbands, at least one PRB separated from the downlink (D) subband can be configured as an offset, and the RO can be configured from the RB index of the U subband starting from the offset. Simultaneously, the starting position of the RO configured for legacy UEs (i.e., UEs that do not recognize SBFD operation) on the frequency axis is configured according to msg-1-FrequencyStart in the legacy Rach-ConfigGeneric. That is, in the flexible duration and / or UL duration without subband configuration, the RO is configured after msg-1-FrequencyStart starting from the start position of the UL BWP (e.g., PRB#0). Furthermore, on the time axis, by allowing the configuration of PRACH slots based on the start time of the U subband configuration, a method can be used to configure the PRACH slots and RO in the downlink / flexible duration on the time axis of the U subband configuration. In the figure, the PRACH slots can be configured discontinuously within a radio frame based on the RACH configuration information.
[0178] according to Figure 19 The starting position of RO on the frequency axis is as follows.
[0179] [Table 5]
[0180] As another embodiment, Figure 20 This paper illustrates an RO configuration method typically configured for terminals that are unaware of SBFD operations (hereinafter referred to as legacy terminals) and terminals that are aware of SBFD operations (hereinafter referred to as SBFD terminals). Figure 20 This illustrates a method for configuring the starting position of the RO on the frequency axis for an SBFD terminal based on the BW ratio between the ULBWP and the UL subband. The starting position of the RO on the frequency axis for the SBFD terminal can be configured based on msg-1-FrequencyStart in the legacy NR system's Rach ConfigGeneric, the BW size of the UL BWP, and the BW size of the UL subband. For example, the RO offset (RO_offset_SBFD) for the SBFD terminal can be configured using the following equation: RO_offset_SBFD is calculated based on the starting RB index of the UL subband.
[0181] - RO_offset_SBFD = floor (RO_offset UL subband_size / UL BWP_size)
[0182] Here, RO_offset represents msg1-FrequencyStart, UL BWP_size represents the BW size of the UL BWP, and UL subband_size represents the BW size of the UL subband.
[0183] Reference Figure 20An RO with a starting RB index can be configured from an RB spaced RO_offset_SBFD from the starting RB index of the uplink subband. For example, suppose the BW size (UL BWP_size) of the UL BWP is 100 RBs and msg1-FrequencyStart (i.e., RO_offset) is 10 RBs. In this case, when the BW size (ULsubband_size) of the uplink subband is 20 RBs, the offset (RO_offset_SBFD) of the RO for the SBFD termination can be configured to 2 RBs. Therefore, an RO with a starting RB index can be configured from an RB spaced 2 RBs from the starting RB index of the uplink subband. When a guard band is required considering inter-subband interference between the downlink and uplink subbands in the frequency domain, at least one PRB spaced from the downlink subband can be set as an offset, and the RO can be configured starting from the RB index of the uplink subband after the corresponding offset, thus allocating RACH resources.
[0184] Reference Figure 21 When adjusting the starting position of the RO using the above method so that the position of the RO for the SBFD terminal can be allocated within the uplink subband, legacy ROs can be configured in both flexible time slots / symbols and UL time slots / symbols. In this case, even if the uplink subband is configured in a flexible time slot / symbol, the adjustment of the starting position of the RO for the SBFD terminal can be performed outside the flexible time slot / symbol where the legacy RO is configured. This is because, since the ROs configured in the flexible time slot / symbol differ between legacy terminals and SBFD terminals, when the terminal sends a PRACH preamble in a valid RO according to the SSB-to-RO mapping (or association), ambiguity may arise at the base station in the mapping of the SSB associated with the RO, and problems may occur during initial access or uplink synchronization.
[0185] In addition, refer to Figure 22 When adjusting the starting position of the RO using the above method to allow for the allocation of the RO position for the SBFD terminal within the uplink subband, the legacy RO can be configured only in the UL timeslot / symbol. If the uplink subband is configured in a flexible timeslot / symbol, the adjustment of the starting position of the RO for the SBFD terminal can be performed in the flexible timeslot / symbol. However, the adjustment of the starting position of the RO for the SBFD terminal can be performed assuming that the RO is configured in the corresponding timeslot / symbol in the time domain according to the PRACH configuration information. That is, Figure 22An example of this could be the case where ROs are configured according to PRACH configuration information in all time slots. Accordingly, since the ROs configured in flexible time slots / symbols cannot be different between legacy terminals and SBFD terminals, when a terminal sends a PRACH preamble in a valid RO according to the SSB-to-RO mapping (or association), no ambiguity appears at the base station in the SSB mapping associated with the RO, and therefore no problems arise during initial access or uplink synchronization.
[0186] As a second embodiment, when the UE utilizes multiple subbands that are semi-statically configured or dynamically indicated in the frequency domain within a downlink / flexible time slot or a symbol that is semi-statically configured or dynamically indicated from the base station, or when an uplink subband is semi-statically configured or dynamically indicated, in addition to Rach-ConfigCommon or Rach-ConfigGeneric configured in legacy NR systems for configuring ROs in flexible / uplink time slots or symbols, a method can be considered to independently configure Rach-ConfigCommon-r19 or Rach-ConfigGeneric-r19 for UEs supporting subband operation in the frequency domain to configure ROs within the uplink subband. However, when the UE receives two independent RO configuration messages (e.g., legacy Rach-ConfigCommon and Rach-ConfigCommon-r19) and needs to configure ROs, the following method can be considered.
[0187] First, legacy Rach-ConfigCommon or Rach-ConfigGeneric can be used for RO configuration in flexible / uplink slots or symbols without uplink subbands configured, and RO configuration for downlink / flexible slots or symbols with uplink subbands configured can use Rach-ConfigCommon-r19 or Rach-ConfigGeneric-r19.
[0188] When a new RACH configuration (e.g., Rach-ConfigCommon-r19, Rach-ConfigGeneric-r19) is used to configure an RO in a downlink / flexible slot or symbol (i.e., SBFD slot / symbol interval) with an uplink subband configured as described above, the RO can also be configured in a flexible / uplink slot or symbol without an uplink subband configured (i.e., non-SBFD slot / symbol interval) using the new RACH configuration. For convenience, the RO configured by the new RACH configuration is referred to as the new RO (or SBFD RO). In this case, in a flexible / uplink slot or symbol without an uplink subband configured, the corresponding RO (new RO) can be set as an invalid RO, and the validity of the RO configured based on the legacy RO can be determined only (see...). Figure 18 This is because the RO configuration configured by the new RACH is only used for RO configurations of downlink / flexible slots or symbols where uplink subbands are configured, and therefore, in flexible / uplink slots or symbols where no uplink subbands are configured, the legacy RO configuration is used equally for both legacy terminals and SBFD terminals. In summary, based on the RACH configuration, ROs for terminals supporting SBFD operation can be configured in both SBFD and non-SBFD intervals in the time domain. In this case, SBFD ROs configured in non-SBFD intervals are determined to be invalid ROs, and the validity of SBFD ROs configured in SBFD intervals can be determined. In non-SBFD intervals, the validity of ROs configured according to legacy ROs can be determined.
[0189] Second, legacy Rach-ConfigCommon or Rach-ConfigGeneric can be used for RO configuration in uplink slots or symbols that are not affected by uplink subband configuration, and RO configuration in downlink / flexible slots or symbols with configured uplink subband can use Rach-ConfigCommon-r19 or Rach-ConfigGeneric-r19.
[0190] When an RO is configured using a new RACH configuration (e.g., Rach-ConfigCommon-r19 or Rach-ConfigGeneric-r19) in a downlink / flexible slot or symbol (i.e., SBFD slot / symbol interval) with an uplink subband configured as described above, the RO can also be configured using the new RACH configuration in a flexible / uplink slot or symbol without an uplink subband configured (i.e., non-SBFD slot / symbol interval). For convenience, the RO configured by the new RACH configuration is referred to as the new RO (or SBFD RO). In this case, in a flexible / uplink slot or symbol without an uplink subband configured, the corresponding RO (new RO) can be set as an invalid RO, and the validity of the RO configured based on the legacy RO can be determined only (see...). Figure 18 This is because the RO configuration through the new RACH is only used for RO configurations of downlink / flexible slots or symbols where uplink subbands are configured, and therefore, in flexible / uplink slots or symbols where no uplink subbands are configured, the legacy RO configuration is used equally for both legacy terminals and SBFD terminals. In summary, based on the RACH configuration, ROs for terminals supporting SBFD operation can be configured in both SBFD and non-SBFD intervals in the time domain. In this case, SBFD ROs configured in non-SBFD intervals are determined to be invalid ROs, and the validity of SBFD ROs configured in SBFD intervals can be determined. In non-SBFD intervals, the validity of ROs configured according to legacy ROs can be determined.
[0191] Figure 23 This illustrates a scheme where, in an uplink / flexible slot or symbol without configured uplink subbands, the RO configured by the PRACH configuration index of the new RACH is set to an invalid RO. Figure 23 (a) shows that in an uplink slot or symbol without configured subband, the RO configured according to the new RACH is set to an invalid RO (see RO#3). Figure 23 (b) shows that in a flexible / uplink slot or symbol without configured subbands, the RO configured according to the new RACH is set to an invalid RO (see RO#2 / #3). In the figure, D represents a downlink slot / symbol, S represents a flexible slot / symbol, and U represents an uplink slot / symbol.
[0192] Third, legacy Rach-ConfigCommon or Rach-ConfigGeneric can be used for RO configuration in flexible / uplink slots or symbols in existing legacy schemes, regardless of the uplink subband configuration, and Rach-ConfigCommon-r19 or Rach-ConfigGeneric-r19 can be used to configure RO configuration in downlink slots or symbols of uplink subbands. In other words, legacy RACH configuration can be used for RO configuration in flexible / uplink slots or symbols, and new RACH configuration can be used for RO configuration during SBFD time intervals.
[0193] When a new RACH configuration (e.g., Rach-ConfigCommon-r19, Rach-ConfigGeneric-r19) is used to configure an RO in a downlink slot or symbol configured as described in the above scheme for an uplink subband, the RO (i.e., the new RO) can also be configured by the new RACH configuration within the flexible / uplink slot or symbol, regardless of the uplink subband configuration. In this case, the new RO can be set as an invalid RO in the flexible / uplink slot or symbol, so that only the validity of the RO configured according to the legacy RO is determined. This is because the RO configuration configured via the new RACH is only used for the RO configuration of the downlink slot or symbol in which the uplink subband is configured, and therefore, the legacy RO configuration set in the flexible / uplink slot or symbol is used equally for both legacy terminals and SBFD terminals, regardless of the uplink subband configuration.
[0194] As a third embodiment, for downlink / flexible slots or symbols configured semi-statically or dynamically by the base station, the terminal can be semi-statically configured with multiple subbands or dynamically indicated with multiple subbands in the frequency domain, or it can be semi-statically configured with uplink subbands or dynamically indicated with uplink subbands. In this case, a method can be considered in which, in addition to Rach-ConfigCommon or Rach-ConfigGeneric used to configure ROs in flexible / uplink slots or symbols in existing legacy NR systems, a new RACH configuration (e.g., Rach-ConfigCommon-r19, Rach-ConfigGeneric-r19) for terminals supporting SBFD operation can be independently configured to configure ROs within uplink subbands. To enable the terminal to receive two independent configurations and set the configured ROs and valid ROs, the following method can be considered.
[0195] In addition to legacy ROs, terminals capable of recognizing SBFD operations (i.e., SBFD-aware UEs, or SBFD terminals for short) can independently configure new RACH configurations (e.g., RACH-ConfigCommon-r19, RACH-ConfigGeneric-r19) to configure ROs within downlink / flexible slots or symbols with uplink subbands configured, and thereby configure ROs (i.e., SBFD ROs). In this case, ROs can be configured in non-SBFD intervals (e.g., flexible / uplink slots or symbols) via new RACH configuration information (e.g., PRACH configuration index). When ROs are also configured by new RACH configurations in flexible / uplink slots or symbols without configured subbands, a method for terminals to determine the validity of the corresponding RO (i.e., SBFD ROs) based on legacy schemes can be considered (see...). Figure 18 This can be advantageous because terminals capable of performing SBFD operations can increase PRACH transmission coverage. However, when a new RO (RO) is additionally configured by a new RACH configuration in the same time slot or symbol as a valid RO (legacy RO) configured by a legacy RACH configuration, and the new RO is determined to be valid according to the existing legacy scheme, the same SSB index can be configured as mapped to the valid legacy RO when mapping the SSB index to the new valid RO. In this way, for valid ROs configured in the same time slot or symbol, the base station can configure and receive the Rx beam corresponding to the same SSB index when configuring the Rx beam. Furthermore, legacy terminals and SBFD-aware terminals can be distinguished depending on which resource the base station receives PRACH in which the valid RO is configured. Additionally, a new RO can be additionally configured by a new RACH configuration in the same time slot or symbol as a valid legacy RO, the new RO can be determined to be valid according to the existing legacy scheme, and separate SSB index-to-RO mappings can be configured for legacy ROs and new ROs. In this scenario, when the SSB index mapped to a legacy valid RO and the SSB index mapped to a new RO are different from each other, the terminal can consider the new RO as an invalid RO. Conversely, when the SSB index mapped to a legacy valid RO and the SSB index mapped to a new RO are the same, the terminal can consider the new RO as a valid RO.
[0196] Figure 24 This illustrates a scheme, according to the above scheme, to set the RO of a new RACH configuration in an uplink (U) slot or symbol, or a flexible (S) slot or symbol configuration in which no uplink subband is configured, as a valid RO. Figure 24 (a) shows that after the validity check, the RO configured according to the new RACH configuration in the uplink slot or symbol without configured subbands is set as a valid RO (see RO#3). For the validity check, see [reference needed]. Figure 18 . Figure 24 (b) shows that after the validity check, the RO configured according to the new RACH configuration in a flexible / uplink slot or symbol without configured subbands is set as a valid RO (see RO#2 / #3). In the figure, D represents downlink slot / symbol, S represents flexible slot / symbol and U represents uplink slot / symbol.
[0197] As a fourth embodiment, in addition to the legacy-configured RO, a terminal capable of recognizing SBFD operations (i.e., an SBFD-aware UE) can also independently configure a new RACH configuration (e.g., RACH-ConfigCommon-r19, RACH-ConfigGeneric-r19) to configure the RO within the downlink slot / symbol or flexible slot / symbol of the uplink subband. In this case, the RO can be configured in a non-SBFD interval (e.g., a flexible / uplink slot or symbol) via new RACH configuration information (e.g., a PRACH configuration index). When the RO is configured via a new RACH configuration in a flexible / uplink slot or symbol without a configuration subband (i.e., an SBFD RO), a method can be considered for the terminal to determine the validity of the RO configured in the corresponding slot or symbol (i.e., a non-SBFD interval) based on the legacy scheme (see [link to documentation]). Figure 18 In addition, a scheme to transmit (long) PRACH format on consecutive time slots during SBFD operations can be considered to increase coverage, which is one of the main purposes of SBFD operations. For this purpose, a RO can only be determined as a valid RO, enabling the transmission of (long) PRACH format, when it is configured (continuously) across SBFD time slots / symbols and non-SBFD time slots / symbols in the time domain via a new RACH configuration (e.g., PRACH configuration index). That is, when an RO is configured in a non-SBFD time slot / symbol via a new RACH configuration, it can only be determined as a valid RO (besides predefined RO validity conditions) if it is configured (continuously) across / on both SBFD time slots / symbols and non-SBFD time slots / symbols in the time domain. Here, predefined RO validity conditions can include gap-based validity conditions, such as validity conditions based on gap intervals with a specific symbol. A specific symbol can include the last DL symbol and / or the last symbol of the SSB. Predefined RO validity conditions can include legacy RO validity states (see...). Figure 18 Furthermore, the validity determination of ROs configured in SBFD slots / symbols can be performed based on the SBFD RO validity conditions outlined in this specification. For example, for the SBFD RO validity conditions, please refer to... Figures 29 to 32Since the validity conditions based on the starting symbol position of the RO are used to determine the gap-based validity conditions, the validity determination of ROs that are continuously configured on SBFD slots / symbols and non-SBFD slots or symbols can be performed based on the SBFD RO validity conditions.
[0198] However, when an RO (new RO) is additionally configured according to the new RACH configuration and the corresponding RO is determined to be valid according to the existing legacy scheme (new valid RO), the new valid RO may partially or completely overlap with the time slots / symbols occupied by the valid RO configured by the legacy RACH (legacy valid RO). In this case, when the SSB index is mapped to the new valid RO, the SSB index mapped to the legacy RO can be configured the same for the new RO. Thus, for ROs configured in the same or partially overlapping time slots / symbols, the base station can configure and receive the Rx beam corresponding to the same SSB index when configuring the Rx beam. Furthermore, legacy terminals and SBFD sensing terminals can be distinguished depending on the resources in which the base station receives PRACH for the ROs configured therein. Additionally, an RO (new RO) can be additionally configured through a new RACH configuration in the same time slot or symbol as the legacy valid RO, the new RO can be determined to be valid according to the existing legacy scheme, and separate SSB index-to-RO mappings can be configured for the legacy RO and the new RO. In this scenario, when the SSB index mapped to a legacy valid RO and the SSB index mapped to a new RO are different from each other, the terminal can consider the new RO as an invalid RO. Conversely, when the SSB index mapped to a legacy valid RO and the SSB index mapped to a new RO are the same, the terminal can consider the new RO as a valid RO.
[0199] Figure 25 This diagram illustrates a scheme where, according to the above approach, the RO (new RO) configured by the new RACH configuration (e.g., PRACH configuration index) is set as the effective RO in a flexible / uplink slot or symbol without configured uplink subbands. In the diagram, D represents a downlink slot / symbol, S represents a flexible slot / symbol, and U represents an uplink slot / symbol. Figure 25 (a) shows that for an RO configured according to the new RACH configuration in an uplink slot / symbol without configured subbands, validity checks (e.g., legacy validity checks; see...) are performed. Figure 18 After determining whether ROs are configured consecutively on the timeline, the corresponding ROs are set as invalid ROs. Specifically, refer to... Figure 25 (a) A new RACH-configured RO (RO#3) can be configured in the uplink slot / symbol. In this case, since RO#3 is only configured in non-SBFD symbols (U), it is determined to be an invalid RO. Figure 25(b) illustrates that after a validity check and determination of whether ROs are continuously configured on the timeline, ROs configured by the new RACH configuration in a flexible / uplink slot or symbol of an unconfigured subband are set as valid ROs. Specifically, see [reference]. Figure 25 (a) A new RACH configuration RO (RO#3) can be configured in the uplink slot / symbol. In this case, since RO#3 is configured consecutively on SBFD symbols (S) and non-SBFD symbols (U), it can be determined as a valid RO (based on the results of the RO validity check).
[0200] Figure 26 This diagram illustrates a scheme where, according to the above approach, the RO (new RO) configured by the new RACH configuration (e.g., PRACH configuration index) is set as the effective RO in a flexible / uplink slot or symbol without configured uplink subbands. In the diagram, D represents a downlink slot / symbol, S represents a flexible slot / symbol, and U represents an uplink slot / symbol. Figure 26 (a) illustrates a situation where, according to the new RACH configuration, part or all of the RO configured from the downlink slot / symbol with UL subband to the flexible slot / symbol without subband overlaps with the symbol occupied by the legacy RO. Figure 26 (b) illustrates a situation where, according to the new RACH configuration, the ROs configured from the downlink / flexible slots or symbols with UL subbands to the uplink slots or symbols without subbands partially or wholly overlap with the symbols occupied by legacy ROs.
[0201] exist Figure 26 In this context, validity checks can be performed (e.g., legacy validity checks; see...). Figure 18 The validity of the RO configured by the new RACH configuration is determined by whether the ROs are configured continuously on the timeline. Specifically, refer to... Figure 26 (a) The RO configured by the new RACH is configured in both SBFD slots / symbols (second D, third D) and non-SBFD slots / symbols (S). Here, since the RO on slot / symbol S (i.e., RO#2) is configured consecutively in both SBFD slot / symbol (third D) and non-SBFD slot / symbol (S), it can be determined as a valid RO (based on the results of the RO validity check). See reference. Figure 26 (b) The RO configured by the new RACH is configured in both SBFD slots / symbols (second D, third D, S) and non-SBFD slots / symbols (U). Here, since the RO on the U slot / symbol (i.e., RO#3) is configured consecutively on both SBFD slots / symbols (S) and non-SBFD slots / symbols (U), it can be determined as a valid RO (based on the results of the RO validity check).
[0202] exist Figure 26 In this context, when an additional RO is configured according to the new RACH configuration (new RO) and the corresponding RO is determined to be valid according to the existing legacy scheme (new valid RO), the new valid RO may partially or completely overlap the time slots / symbols occupied by the valid RO configured by the legacy RACH (legacy valid RO) (see [link to documentation]). Figure 26 (a) RO#2 and Figure 26 (b) RO#3). In this case, separate SSB index-to-RO mappings can be configured for the legacy RO and the new RO. When configuring separate SSB index-to-RO mappings, the SSB indices mapped to valid ROs that overlap in the time domain may be different or the same. In this case, when the SSB indices mapped to the legacy valid RO and the SSB indices mapped to the new RO are different, the terminal can consider the new RO as an invalid RO, and when the SSB indices mapped to the legacy valid RO and the SSB indices mapped to the new RO are the same, the terminal can consider the new RO as a valid RO.
[0203] Figure 27 This illustrates a situation where, in a downlink slot or symbol or flexible slot or symbol configured with an uplink subband, a PRACH timing (i.e., RO) is assigned to a frequency resource different from the frequency resource of the SSB and they partially overlap in the time domain. Figure 27 (a) shows the case where the SSB and RO overlap in the time domain on the downlink symbol where the uplink subband is configured, when the uplink subband is configured in the downlink slot or symbol. Figure 27 (b) shows the case where the SSB and RO overlap in the time domain on the flexible symbol where the uplink subband is configured, when the uplink subband is configured in the downlink slot or symbol or the flexible slot or symbol.
[0204] like Figure 27As shown, a new RO (RO) can be configured through a new RACH configuration in a downlink slot or symbol or flexible slot or symbol where an uplink subband is configured. In this case, although the configured RO and SSB are allocated in different frequency resources, they may partially or completely overlap in the time domain. In this case, the following scheme can be considered to check the validity of the configured RO. First, from the perspective of the terminal performing half-duplex operation, SSB reception and PRACH transmission cannot be performed simultaneously, and therefore the terminal can perform SSB reception and set the RO that partially or completely overlaps with the SSB reception in the time domain as an invalid RO. Here, SSB reception can be limited to SSB reception that is essential from the perspective of the corresponding terminal. For example, it is necessary for all terminals to receive the SSB indicated by the RRC parameter ssb-PositionsInBurst in ServingCellConfigCommonSIB or ServingCellConfigCommon, which is a cell common signal. Therefore, for an SSB indicated by ssb-PositionsInBurst, the terminal can perform SSB reception and set the ROs that partially or completely overlap with the SSB reception in the time domain as invalid ROs. However, if the RO partially or completely overlaps with the SSB reception in the time domain at a location other than the reception location of the SSB indicated by ssb-PositionsInBurst, the terminal can (after a validity check) set the RO as a valid RO. In this case, the terminal can skip the reception of the SSBs that overlap with the ROs. This is to prioritize the reception of SSBs that the base station has configured for all terminals belonging to the cell, as such reception may be necessary for all terminals to perform synchronization and Radio Resource Management (RRM) measurements via SSBs.
[0205] As an example of SSB reception, there may be symbols where SSB reception is configured within an SMTC (Segment-Based Measurement Timing Configuration) specifically configured for the terminal. In addition to initial cell access and cell information acquisition, the terminal can be configured to additionally receive SSBs within an SMTC window configured by the base station specifically for the UE, in order to measure downlink channel states received from the serving cell and neighboring cells. In this case, the terminal can set ROs that partially or completely overlap with the corresponding SSB reception in the time domain as valid ROs.
[0206] As another example of SSB reception, when configuring SSB reception from multiple transmit and receive points (TRPs), the terminal can set the RO that partially or completely overlaps with the corresponding SSB reception in the time domain as the valid RO.
[0207] As another example of SSB reception, when symbols are provided in which SSB reception from multiple TRPs are configured, if the terminal is configured to receive SSBs from the TRP of the serving cell or a neighboring cell, the terminal can set the RO that partially or completely overlaps with the corresponding SSB reception in the time domain as the valid RO.
[0208] As another example of SSB reception, when symbols are provided in which SSB reception from multiple TRPs are configured, if the SSB received by the terminal has the same PCI as the serving cell, the terminal can set ROs that partially or completely overlap with the corresponding SSB reception in the time domain as invalid ROs, thereby prioritizing SSB reception. In other cases, i.e., when the terminal is configured to receive SSBs with PCIs different from the serving cell's PCI from the TRP of the serving / neighboring cell, the terminal can set ROs that partially or completely overlap with the corresponding SSB reception in the time domain as valid ROs.
[0209] The methods for checking the effectiveness of RO will be further described below.
[0210] 1. This relates to a method in which, as in the case of an SBFD-DL symbol (configured as DL by tdd-UL-DL-ConfigurationCommon), the terminal also considers the gap symbol following the SBFD-DL symbol and performs a validity check of the RO in the PRACH slot configured for the terminal. Assuming that the RO is configured consecutively after the SBFD-DL symbol, a method for determining the validity of the configured RO is proposed as follows.
[0211] As a first embodiment, a configuration RO starting at least after a gap following the SBFD-DL symbol can be defined as a valid RO. This is because when the transmission of the DL channel / signal from the base station to the terminal occurs in the DL subband on the SBFD-DL symbol, the terminal performs half-duplex operation and may therefore require a gap for UL transmission after DL reception so that UL transmission can be performed in the RO after DL reception in the DL subband on the SBFD-DL symbol. Therefore, a configuration RO starting at least after a gap following the SBFD-DL symbol can be set as a valid RO.
[0212] As another embodiment, since reception of DL channels / signals in the DL subband of an SBFD-DL symbol may not always occur from the perspective of a terminal, when the corresponding terminal is not scheduled or configured to receive a DL channel or signal in the DL subband of an SBFD-DL symbol preceding the start symbol of the RO configured for that terminal, the terminal can determine the configured RO as a valid RO regardless of the gap. In other words, when the terminal is scheduled or configured with a DL channel / signal to receive in the DL subband of an SBFD-DL symbol preceding the start symbol of the configured RO, the corresponding terminal can set the configured RO starting at least after the gap as a valid RO. That is, in the case of a terminal performing half-duplex operation, when DL reception is present, a gap may be needed for performing UL transmission after DL reception, but when DL reception is not needed, UL transmission can be performed regardless of the corresponding gap.
[0213] As another embodiment, from the perspective of a terminal, the terminal can be scheduled or configured to transmit a UL channel / signal to the base station immediately before the start symbol of the configured RO in the UL subband configured on the SBFD-DL symbol. In this case, from the perspective of the terminal performing half-duplex operation, since the UL transmission is performed continuously through the UL transmission in the UL subband on the SBFD-DL symbol preceding the start symbol of the configured RO for the terminal, a gap may not be needed for performing the UL transmission after DL reception. Therefore, in this case, the configured RO can be determined as a valid RO regardless of the gap.
[0214] 1-1. This relates to a method in which, as an SBFD-DL symbol (configured as DL via tdd-UL-DL-ConfigurationCommon), when an additional SSB is configured on the SBFD-DL symbol, the terminal considers the gap between DL reception and UL transmission and performs a validity check of the RO in the PRACH slot configured for the terminal. Assuming that the RO is configured consecutively after the SBFD-DL symbol, a method for determining the validity of the configured RO is proposed.
[0215] Figure 27 This illustrates a scenario where, in the downlink slots or symbols or flexible slots or symbols configured for the UL subband, the PRACH timings (ROs) of the SBFD sensing terminal and the SSB are allocated to different frequency resources and do not overlap in the time domain.
[0216] As a first embodiment, such as Figure 28As shown in (a), the configured RO starting after the gap following the last symbol of the SSB configured on at least the SBFD-DL symbol can be determined as a valid RO. This is because when the SSB transmission from the base station to the terminal occurs in the DL subband on the SBFD-DL symbol, the terminal performs half-duplex operation, and therefore, for UL transmission in the RO following SSB reception, a gap may be needed to perform UL transmission after SSB reception. Therefore, the configured RO starting after the gap following the last symbol of the SSB configured on at least the SBFD-DL symbol can be set as a valid RO.
[0217] As another embodiment, such as Figure 28 As shown in (a), from the perspective of a terminal, the reception of an SSB configured on an SBFD-DL symbol may not always occur for the corresponding terminal. Therefore, when an SSB configured in an SBFD-DL symbol preceding the start symbol of the RO configured for the terminal does not need to be received by the corresponding terminal on the DL subband, the terminal can designate the configured RO as a valid RO regardless of the gap. On the other hand, when the corresponding terminal is configured to receive an SSB on the DL subband of an SBFD-DL symbol preceding the start symbol of the configured RO, the configured RO starting at least after the gap can be set as a valid RO. That is, when the terminal is performing half-duplex operation, when there is an SSB reception, a gap may be needed for performing UL transmission after the SSB reception, but when there is no SSB reception, UL transmission can be performed regardless of the corresponding gap.
[0218] As another embodiment, such as Figure 28As shown in (a), a method can be used in which, from the perspective of a terminal, the terminal determines the validity of subsequently configured ROs differently based on the reception type of the SSB configured on the SBFD-DL symbol. For example, a method can be considered to determine the validity of configured ROs differently based on the SSB reception type of the cell common configuration and the SSB reception type of the UE specific configuration. For SSB reception of the cell common configuration, as described in the first embodiment above, configured ROs starting at least after a gap from the last symbol of the SSB can be determined as valid ROs. Otherwise, that is, when the gap between the preceding SSB and the configured RO is not guaranteed, the terminal can determine the configured RO as an invalid RO. In the case of SSB reception of the UE specific configuration, the priority of SSB reception can be considered low, and configured ROs can be determined as valid ROs regardless of the gap between the preceding SSB and the configured RO. SSBs of the cell common configuration include SSBs indicated by the RRC parameter ssb-PositionsInBurst configured in ServingCellConfigCommonSIB or ServingCellConfigCommon. The UE-specific SSB configuration may include the SSB indicated by the RRC parameter ssb-PositionsInBurst-r17 configured in SSB-MTC-AdditionalPCI-r17 and the SSB indicated by the RRC parameter SSB-ToMeasure.
[0219] As another embodiment, such as Figure 28 As shown in (b), when an SSB receiver is configured after a configured RO on an SBFD-DL symbol, the configured RO can be set as an active RO at least if the configured RO does not overlap with the SSB on the time and frequency axes. Figure 28 In case (b), since there is usually no gap for performing UL transmission and DL reception, the terminal can determine the corresponding configuration RO as the valid RO.
[0220] As another embodiment, such as Figure 28 As shown in (b), when SSB reception is configured after a configured RO on an SBFD-DL symbol, a Tx-Rx transition time defined in the legacy NR may still be required even if the configured RO does not overlap with the SSB on the time and frequency axes. Therefore, the gap can be set to the minimum number of symbols longer than the transition time, and the validity of the configured RO can be determined by whether the last symbol of the configured RO precedes the start symbol of the SSB by that gap in the time domain. For example, if the last symbol of the configured RO precedes the start symbol of the SSB by that gap in the time domain, the terminal can set the configured RO as an invalid RO; otherwise, the terminal can set it as a valid RO.
[0221] Table 6 shows the conversion time for Tx-Rx as defined in legacy NR. Here, the unit of conversion time is Tc.
[0222] [Table 6]
[0223] As another embodiment, such as Figure 28 As shown in (b), when SSB reception is configured after the RO configured on the SBFD-DL symbol, the SSB for applying the scheme of the above embodiments may be limited to the SSBs of the cell common configuration. That is, the scheme of the above embodiments may not be applicable to the SSBs of the UE-specific configuration. For example, when Figure 28 (b) When the SSB is a cell-common SSB, the terminal can consider the gap between the configured RO and SSB reception to determine the validity of the configured RO. On the other hand, when Figure 28 (b) When the SSB is a UE-specific SSB, the terminal can determine the configured RO as a valid RO, regardless of the gap with the SSB reception.
[0224] 2. This relates to a method in which, as an SBFD-FL symbol (configured flexibly by tdd-UL-DL-ConfigurationCommon), the terminal considers the gap symbol following the SBFD-FL symbol and performs a validity check of the RO in the PRACH slot configured for the terminal. A method for determining the validity of configured ROs is proposed when ROs are configured consecutively after the SBFD-FL symbol.
[0225] As a first embodiment, a configured RO that begins at least after a gap following the SBFD-FL symbol can be defined as a valid RO. This is because when the transmission of the DL channel / signal from the base station to the terminal occurs in the DL subband on the SBFD-FL symbol, the terminal performs half-duplex operation and may therefore require a gap for performing UL transmission after DL reception, so that UL transmission can be performed in the RO after DL reception in the DL subband on the SBFD-FL symbol from the base station. Therefore, a configured RO that begins at least after a gap following the SBFD-FL symbol can be set as a valid RO.
[0226] As another embodiment, since reception of DL channels / signals in the DL subband on an SBFD-FL symbol may not always occur from the perspective of a terminal, when the corresponding terminal is not scheduled or configured to receive a DL channel or signal in the DL subband on an SBFD-FL symbol preceding the start symbol of the RO configured for that terminal, the terminal can determine the configured RO as a valid RO regardless of the gap. In other words, when the terminal is scheduled or configured to receive a DL channel / signal in the DL subband on an SBFD-FL symbol preceding the start symbol of the configured RO, the corresponding terminal can set the configured RO starting at least after the gap as a valid RO. That is, in the case of a terminal performing half-duplex operation, when DL reception is present, a gap may be needed for performing UL transmission after DL reception, but when DL reception is not needed, UL transmission can be performed regardless of the corresponding gap.
[0227] As another embodiment, from the perspective of a terminal, the terminal can be scheduled or configured to transmit a UL channel / signal to the base station immediately before the start symbol of the configured RO in the UL subband configured on the SBFD-FL symbol. In this case, from the perspective of the terminal performing half-duplex operation, since the UL transmission is performed continuously through the UL transmission in the UL subband on the SBFD-FL symbol preceding the start symbol of the RO configured for the terminal, a gap in UL transmission after DL reception may not be necessary. Therefore, in this case, the configured RO can be determined as a valid RO regardless of the gap.
[0228] 2-1. This relates to a method in which, as in the case of an SBFD-FL symbol (configured flexibly via tdd-UL-DL-ConfigurationCommon), when an additional SSB is configured on the SBFD-FL symbol, the terminal considers the gap between DL reception and UL transmission and performs a validity check of the RO in the PRACH time slot configured for the terminal. Assuming that the RO is configured consecutively after the SBFD-FL symbol, a method for determining the validity of the configured RO is proposed.
[0229] As a first embodiment, such as Figure 28As shown in (a), a valid RO can be defined as the RO that begins after the gap following the last symbol of an SSB configured on at least the SBFD-FL symbol. This is because when an SSB transmission from the base station to the terminal occurs in the DL subband on the SBFD-FL symbol, the terminal performs half-duplex operation, and therefore a gap following SSB reception may be required for UL transmission in the RO following SSB reception. Therefore, a valid RO can be defined as the RO that begins after the gap following the last symbol of an SSB configured on at least the SBFD-FL symbol.
[0230] As another embodiment, such as Figure 28 As shown in (a), from the perspective of a terminal, the reception of an SSB configured on an SBFD-FL symbol may not always occur for the corresponding terminal. Therefore, when an SSB configured in an SBFD-FL symbol preceding the start symbol of the RO configured for the terminal does not need to be received by the corresponding terminal on the DL subband, the terminal can designate the configured RO as a valid RO regardless of the gap. On the other hand, when the corresponding terminal is configured to receive an SSB on the DL subband of an SBFD-FL symbol preceding the start symbol of the configured RO, the configured RO starting at least after the gap can be set as a valid RO. That is, when the terminal is performing half-duplex operation, when there is an SSB reception, a gap may be needed to perform UL transmission after the SSB reception, but when there is no SSB reception, UL transmission can be performed regardless of the corresponding gap.
[0231] As another embodiment, such as Figure 28As shown in (a), a method can be used in which, from the perspective of a terminal, the terminal determines the validity of subsequently configured ROs differently based on the reception type of the SSB configured on the SBFD-FL symbol. For example, a method can be considered to determine the validity of configured ROs differently based on the SSB reception type of the cell common configuration and the SSB reception type of the UE specific configuration. For SSB reception of the cell common configuration, as described in the first embodiment above, configured ROs starting at least after the gap with the last symbol of the SSB can be determined as valid ROs. Otherwise, that is, when the gap between the preceding SSB and the configured RO is not guaranteed, the terminal can determine the configured RO as an invalid RO. In the case of SSB reception of the UE specific configuration, the priority of SSB reception can be considered low, and configured ROs can be determined as valid ROs regardless of the gap between the preceding SSB and the configured RO. SSBs of the cell common configuration include SSBs indicated by the RRC parameter ssb-PositionsInBurst configured in ServingCellConfigCommonSIB or ServingCellConfigCommon. The UE-specific SSB configuration may include the SSB indicated by the RRC parameter ssb-PositionsInBurst-r17 configured in SSB-MTC-AdditionalPCI-r17 and the SSB indicated by the RRC parameter SSB-ToMeasure.
[0232] As another embodiment, such as Figure 28 As shown in (b), when an SSB receiver is configured after a configured RO on an SBFD-FL symbol, the configured RO can be set as an active RO at least if the configured RO does not overlap with the SSB on the time and frequency axes. Figure 28 In case (b), since there is usually no need for a gap to perform UL transmission and DL reception, the terminal can determine the corresponding configured RO as the valid RO.
[0233] As another embodiment, such as Figure 28As shown in (b), when SSB reception is configured after a configured RO on an SBFD-FL symbol, even if the configured RO does not overlap with the SSB on the time and frequency axes, a Tx-Rx transition time defined in the legacy NR may still be required. For the Tx-Rx transition time defined in the legacy NR, refer to Table 6. Therefore, the gap can be set to the minimum number of symbols longer than the transition time, and the validity of the configured RO can be determined by whether the last symbol of the configured RO is at least that gap earlier in the time domain than the start symbol of the SSB. For example, if the last symbol of the configured RO is at least that gap earlier in the time domain than the start symbol of the SSB, the terminal can set the configured RO as an invalid RO; otherwise, the terminal can set it as a valid RO.
[0234] As another embodiment, such as Figure 28 As shown in (b), when SSB reception is configured after the RO configured on the SBFD-FL symbol, the SSB for applying the above embodiment can be limited to the SSB of the cell common configuration. Meanwhile, the scheme of the above embodiment may not be applicable to UE-specific SSB configurations. For example, when Figure 28 (b) When the SSB is a cell-common SSB, the terminal can consider the gap between the configured RO and SSB reception to determine the validity of the configured RO. On the other hand, when Figure 28 (b) When the SSB is a UE-specific SSB, the terminal can determine the configured RO as a valid RO, regardless of the gap with the SSB reception.
[0235] Furthermore, as another embodiment of the present invention, for an RO configured on an SBFD-DL symbol or SBFD-FL symbol that is configured as DL by tdd-UL-DL-ConfigurationCommon and is a non-SBFD symbol (or legacy symbol) of a DL / UL subband in which no SBFD operation is configured, at least N can be started after the last (non-SBFD) DL symbol. gap The configured RO is determined to be a valid RO, and otherwise it can be determined to be an invalid RO (see...). Figures 29 to 31 Furthermore, when at least a portion of the SSB's symbols are configured in symbols that are configured as flexible by tdd-UL-DL-ConfigurationCommon, for ROs configured on SBFD-DL or SBFD-FL symbols following the SSB's symbols, at least N must begin after the last symbol of the SSB. gap The configured RO can be determined as a valid RO, and otherwise can be determined as an invalid RO (see...). Figure 32 ).
[0236] As one embodiment, according to Table 4 defined in the legacy NR standard, the specific value of the gap in this embodiment can be set to Ngap, so that the operation is consistent with the operation of the legacy terminal. As another embodiment, according to Table 6 used in the legacy terminal (e.g., N... Rx-Tx T c The gap symbols used to perform UL transmission after DL reception for SBFD operation can be set to a minimum number of symbols longer than the conversion time.
[0237] In addition to the methods described above, when a terminal is semi-statically configured or dynamically indicated in the frequency domain for multiple subbands of downlink / flexible time slots or symbols that are semi-statically configured or dynamically indicated by the base station, the terminal can determine the effective RO in the corresponding time slot or symbol as follows.
[0238] - When tdd-UL-DL-ConfigurationCommon is not configured for the UE: When the RO within a PRACH slot is not earlier in the time domain than the SS / PBCH block within the same PRACH slot and is at least N after the received symbol of the last SS / PBCH block. gap The RO can be valid at the start of a symbol. Here, the last received symbol of the last SS / PBCH block refers to the last received symbol of the last SS / PBCH block before the RO.
[0239] - When the terminal is configured with tdd-UL-DL-ConfigurationCommon ( Figures 29 to 32 )hour: When the RO in the PRACH slot is on the UL symbol, the corresponding RO is valid. Figure 29 Furthermore, when the RO in the PRACH time slot is within the UL subband ( Figure 29 When RO is not before the SS / PBCH block in the same PRACH time slot in the time domain, RO is at least N after the last DL symbol. gap The first symbol ( Figures 30 to 31 ), and RO is at least N after the last SS / PBCH block receive symbol. gap The first symbol ( Figure 32 When this is the case, the corresponding RO may be valid. Since UL transmission is allowed in the UL subband, the final DL symbol is limited to DL symbols that do not contain configurations or indications of the UL subband (i.e., non-subband (SBFD) symbols). In other words, subband (SBFD) symbols are not included in the final DL symbol. See reference... Figures 30 to 31The last DL symbol refers to the last DL symbol before the corresponding RO on the DL symbol set configured by tdd-UL-DL-ConfigurationCommon (i.e., the DL non-SBFD symbol set), excluding the symbols configured for the UL subband (the last symbol of slot #p-1 and the last symbol of slot #m-1).
[0240] exist Figures 29 to 32 In this context, m, p, and q represent slot indices. m, p, and q are defined according to the PRACH slot configuration and can be configured contiguously or discontinuously.
[0241] The terminal can perform UL transmission or DL reception based on a valid RO (or based on whether the RO is valid). For example, the terminal can perform PRACH transmission within a valid RO. Furthermore, according to the disclosure of the present invention, when a valid RO (including gap symbols) and downlink reception (e.g., PDSCH reception) overlap in the time domain, PRACH transmission or DL reception can be restricted. Reference will be made below. Figures 33 to 36 This is described in detail. Furthermore, the terminal cannot perform PRACH transmissions within invalid ROs. However, the terminal's downlink reception is not limited by invalid ROs.
[0242] For downlink / flexible time slots or symbols with semi-static configuration or dynamic indication by the base station, multiple subbands can be semi-statically configured or dynamically indicated to the UE in the frequency domain. In this case, the resources configured or indicated for receiving DL signals / channels and the effective ROs may overlap in the same symbol. A UE that only supports half-duplex may only be able to perform DL reception or UL transmission in the same symbol, and the UE cannot perform N before (i) the effective RO and (ii) the effective RO. gap DL signals / channels (e.g., PDCCH, PDSCH, or CSI-RS) are received (e.g., skipped reception) within a symbol. On the other hand, DL signals / channels can be received normally when the RO of overlapping DL signals / channels is invalid.
[0243] For example, refer to Figure 33 The terminal can be configured or instructed to receive a PDSCH, which includes N corresponding to (i) valid RO and (ii) valid RO. gap Six symbols overlapping. In this case, to protect PRACH transmissions in the valid RO, the terminal may choose not to receive PDSCH. However, when there is no actual PRACH transmission in the valid RO, even if resources configured or indicated for receiving PDSCH in the corresponding time slot are available, the terminal that has not received PDSCH may reduce downlink coverage by not receiving it. The following terminal operation is proposed to address this problem. In the following, the valid RO may include N gapSymbol. That is, a valid RO might mean {N} gap A symbol + RO}. Regarding N gap For symbols, please refer to Table 4.
[0244] 1) PDSCH (or SPS PDSCH) and effective RO ( Figures 33 to 36 )
[0245] In the frequency domain, multiple subbands can be configured or indicated to the UE for semi-static configuration or dynamic indication of downlink / flexible time slots or symbols. Furthermore, the UE can be instructed to receive PDSCH via DCI format (e.g., DCI format 1_0, 1_1, or 1_2) for DL scheduling in the corresponding time slot or symbol (i.e., subband time slot / symbol). Additionally, the UE can be configured to receive semi-persistent scheduling (SPS) PDSCH via a higher layer (e.g., RRC) in the corresponding time slot or symbol (i.e., subband time slot / symbol). When the PDSCH (or SPS PDSCH) and the valid RO overlap in the same symbol within the corresponding time slot or symbol, the UE operates as follows.
[0246] According to the first embodiment, (a) when there is no actual PRACH transmission, PDSCH (or SPSPDSCH) can be received, and (b) when there is actual PRACH transmission, PRACH can be sent and PDSCH can be not received. In the first embodiment, in order to solve the above problem, PDSCH (or SPSPDSCH) can be received at least when there is no actual PRACH transmission, thereby preventing a reduction in downlink coverage.
[0247] According to the second embodiment, (a) when there is no actual PRACH transmission, the terminal receives PDSCH (or SPS PDSCH), and (b) when there is an actual PRACH transmission, the terminal can send a PRACH and receive a PDSCH (or SPS PDSCH) with rate matching. For example, see reference. Figure 33 It can instruct the terminal to use 14 symbols With 20 RBs receiving PDSCH (or SPSPDSCH), the effective RO can be determined as 6 symbols. Six RBs, indicating that the resources for receiving PDSCH (or SPS PDSCH) can fully cover the valid RO. In this case, the terminal can use the six symbols overlapping with the valid RO. Six RBs, in 14 symbols indicating PDSCH (or SPS PDSCH) reception. Among the 20 RBs, PDSCH (or SPSPDSCH) is received via rate matching. Rate matching is available in the resources where downlink reception is possible, and PRACH can be transmitted within valid ROs. In the second embodiment, even if actual PRACH transmission exists in overlapping symbols, the terminal can still receive PDSCH (or SPS PDSCH) in a rate-matched manner within the resources where downlink reception is possible. Therefore, downlink coverage reduction can be prevented.
[0248] The first or second embodiment may only be applied to PRACH transmissions configured / initiated by a higher layer (e.g., Media Access Control (MAC)). That is, the UE may not expect to detect both the DCI indicating PDSCH (or SPSPDSCH) reception and the DCI indicating PRACH transmission in the same symbol.
[0249] Reference Figure 34 The terminal can be configured or instructed by the base station to receive PDSCH in 8 symbols, and 6 symbols can be identified as valid ROs. In this case, the reception of valid ROs and PDSCH do not overlap in the frequency domain, but may overlap in the time domain (i.e., 2 symbols). In this case, the terminal may operate differently depending on whether the PDSCH reception is configured from a higher layer (e.g., Radio Resource Control, RRC) or indicated by DCI. Here, PDSCH reception configured by a higher layer includes SPS PDSCH reception.
[0250] According to an embodiment, when PDSCH reception is indicated via a DCI format used for DL scheduling (e.g., DCI format 1_0, 1_1, or 1_2), the terminal can receive the PDSCH (i.e., PDSCH reception is given priority). Reference Figure 35 The system can instruct the terminal to receive PDSCH in 8 symbols within the downlink subband, and can identify 6 symbols as valid ROs. In this case, the terminal can receive PDSCH in the 8 symbols indicated by the DCI, and can not transmit PRACH in the valid ROs. This is because, at least when the terminal is instructed to perform downlink reception by the base station via the DCI, the terminal can determine that downlink reception will prioritize downlink coverage and will not perform PRACH transmission. Meanwhile, unlike terminals supporting half-duplex communication schemes on subbands, the base station supports full-duplex communication schemes. Therefore, as... Figure 35 As shown, even if the PRACH transmission of a specific terminal in the effective RO within the subband is limited by the PDSCH reception of the corresponding terminal, a base station that supports full-duplex operation can send PDSCH to the corresponding terminal while receiving PRACH from another terminal in the effective RO.
[0251] According to another embodiment, when the terminal is configured to receive PDSCH from a higher layer (e.g., RRC), the terminal can receive rate-matched PDSCH and perform PRACH transmission within an effective RO. For example, the terminal can receive rate-matched PDSCH in symbols excluding those overlapping with the effective RO and symbols corresponding to the RxTxSwitchingGap, which are configured differently according to the subcarrier spacing (SCS), i.e., the gap (N) between downlink reception and uplink transmission. gap,Rx-Tx ) and / or the gap between uplink transmission and downlink reception (N) gap,Tx-Rx Here, N gap,Rx-Tx and N gap,Tx-Rx The values of can be defined independently of each other, or they can be defined as the same value. For convenience, the switching gap is generalized and referred to as N. gap N gap It can refer to N gap,Rx-Tx and / or N gap,Tx-Rx . refer to Figure 36 The terminal can be configured from a higher layer (e.g., RRC) to receive PDSCH within 8 symbols in the downlink subband, and can identify 6 symbols as valid ROs. In this case, for PDSCH reception, the terminal can determine the valid ROs by considering the 2 symbols overlapping with the valid ROs and the N symbols preceding the valid ROs. gap = 2 symbols for rate matching of PDSCH to receive PDSCH with a length of 4 symbols (this is the configuration N) gap,Rx-Tx (The case is 2, but not limited to this). Furthermore, the terminal can also send PRACH in a valid RO. This is a method that prevents downlink coverage reduction by receiving rate-matched PDSCH in at least one of the resources where downlink reception is possible, and also enables PRACH transmission when the terminal wishes to send in the RO.
[0252] 2) CSI-RS comparison of effective RO
[0253] In the frequency domain, multiple subbands can be configured or indicated to the UE for semi-static configuration or dynamic indication of downlink / flexible time slots or symbols. Furthermore, the UE can be instructed to receive CSI-RS via DCI format (e.g., DCI format 1_0, 1_1, or 1_2) for DL scheduling on the corresponding time slot or symbol (i.e., subband time slot / symbol). When the CSI-RS and the active RO overlap in the same symbol within the time slot or symbol, the UE operates as follows.
[0254] According to the first embodiment, (a) CSI-RS can be received when there is no actual PRACH transmission, and (b) when there is actual PRACH transmission, PRACH can be sent but CSI-RS cannot be received. In the first embodiment, in order to solve the above problem, CSI-RS can be received at least when there is no actual PRACH transmission, thereby preventing a reduction in downlink coverage.
[0255] The first embodiment can only be applied if the CSI-RS is received by the DCI and the PRACH transmission is configured from a higher layer (e.g., MAC). That is, the UE may not expect to receive the CSI-RS from a higher layer and transmit the PRACH in the same symbol.
[0256] 3) CORESET is effective for this RO
[0257] In the frequency domain, multiple subbands can be configured or indicated to the UE for semi-static configuration or dynamic indication of downlink / flexible slots or symbols. Furthermore, a CORESET can be configured for the UE to monitor the PDCCH on the corresponding slot or symbol (i.e., subband slot / symbol). When the CORESET and the active RO overlap in the same symbol within the corresponding slot or symbol, the UE operates as follows.
[0258] According to the first embodiment, (a) when there is no actual PRACH transmission, the PDCCH can be monitored, and (b) when there is actual PRACH transmission, PRACH can be sent without monitoring the PDCCH. In the first embodiment, to solve the above-mentioned problem, the PDCCH can be monitored at least when there is no actual PRACH transmission, thereby preventing a reduction in downlink coverage. Furthermore, the PDCCH contains control information, such as resource allocation for the UE, and can therefore be optimized.
[0259] The first embodiment can only be applied when PRACH transmission is configured from a higher layer (e.g., MAC). That is, when the UE is instructed by the DCI to transmit PRACH on a symbol configured with CORESET, the UE cannot monitor the PDCCH regardless of whether the PRACH is actually transmitted in that symbol.
[0260] When a UE is transmitting PRACH for initial cell access (i.e., before RRC connection), the aforementioned conflict conditions between valid RO and CORESET, PDSCH, or CSI-RS may not apply. In other words, in the event of a conflict, a UE prior to RRC connection may not monitor PDCCH or receive PDSCH or CSI-RS. For example, a UE prior to RRC connection may perform operations based on legacy NR systems.
[0261] The methods and systems disclosed herein are described with respect to specific embodiments, but some or all of the configuration elements and operations of this disclosure may be implemented using a computer system with a general hardware architecture.
[0262] The foregoing description of this disclosure is for illustrative purposes, and those skilled in the art to which this disclosure pertains will understand that modifications to other specific forms can be readily implemented without altering the technical spirit or essential features of this disclosure. Therefore, it should be understood that the above embodiments are illustrative in all respects and not restrictive. For example, each element described as being of one type may be implemented in a distributed manner, and similarly, elements described as being distributed may be implemented in a combined manner.
[0263] The scope of this disclosure is indicated by the claims described below rather than by the detailed specification, and all changes or modifications derived from the meaning and scope of the claims and their equivalents shall be construed as being included within the scope of this disclosure.
Claims
1. A user equipment (UE) configured to operate in a wireless communication system, the UE comprising: Communication module; as well as A processor configured to control the communication module. The processor is configured as follows: Receive configuration for non-overlapping subband full-duplex (SBFD) symbol sets and non-SBFD symbol sets in radio frames, wherein the SBFD symbol sets include non-UL symbols in which UL (uplink) subbands are configured; Receive configuration for multiple random access channel timings (ROs) for SBFD operation on multiple symbols in a radio frame; and Identify at least one effective RO among the plurality of ROs. Wherein, the at least one valid RO includes an RO that is continuously configured across the SBFD symbol set and the non-SBFD symbol set among the plurality of ROs.
2. The UE according to claim 1, wherein, Of the plurality of ROs, only those configured in the non-SBFD symbol set are identified as invalid ROs.
3. The UE according to claim 1, wherein, The at least one valid RO includes the RO among the plurality of ROs configured within the UL subband of the SBFD symbol set.
4. The UE according to claim 1, wherein, The at least one valid RO includes at least N of the plurality of ROs located after the last DL non-SBFD symbol. gap N symbols and located after the last synchronization signal / physical broadcast channel (SSB) symbol. gap RO of symbols.
5. The UE according to claim 1, wherein, When at least one of the plurality of ROs overlaps with a legacy RO in the time domain, the same SSB index as the SSB associated with the legacy RO is mapped to the synchronization signal / physical broadcast channel block (SSB) associated with the at least one RO.
6. A base station configured to operate in a wireless communication system, the base station comprising: Communication module; as well as A processor configured to control the communication module. The processor is configured as follows: Configure non-overlapping subband full-duplex (SBFD) symbol sets and non-SBFD symbol sets in radio frames, wherein the SBFD symbol sets include non-UL symbols in which UL (uplink) subbands are configured; Configure multiple random access channel timings (ROs) for SBFD operations on multiple symbols in the radio frame; and Identify at least one effective RO among the plurality of ROs. Wherein, the at least one valid RO includes an RO that is continuously configured across the SBFD symbol set and the non-SBFD symbol set among the plurality of ROs.
7. The base station according to claim 6, wherein, Of the plurality of ROs, only those configured in the non-SBFD symbol set are identified as invalid ROs.
8. The base station according to claim 6, wherein, The at least one valid RO includes the RO among the plurality of ROs configured within the UL subband of the SBFD symbol set.
9. The base station according to claim 6, wherein, The at least one valid RO includes at least N of the plurality of ROs located after the last DL non-SBFD symbol. gap N symbols and located after the last synchronization signal / physical broadcast channel (SSB) symbol. gap RO of symbols.
10. The base station according to claim 6, wherein, When at least one of the plurality of ROs overlaps with a legacy RO in the time domain, the same SSB index as the SSB associated with the legacy RO is mapped to the synchronization signal / physical broadcast channel block (SSB) associated with the at least one RO.
11. A method performed by a user equipment (UE) in a wireless communication system, the method comprising: Receive configuration for non-overlapping subband full-duplex (SBFD) symbol sets and non-SBFD symbol sets in radio frames, wherein the SBFD symbol sets include non-UL symbols in which UL (uplink) subbands are configured; Receive configuration for multiple random access channel timings (ROs) for SBFD operation on multiple symbols in a radio frame; and Identify at least one effective RO among the plurality of ROs. Wherein, the at least one valid RO includes an RO that is continuously configured across the SBFD symbol set and the non-SBFD symbol set among the plurality of ROs.
12. The method according to claim 11, wherein, Of the plurality of ROs, only those configured in the non-SBFD symbol set are identified as invalid ROs.
13. The method according to claim 11, wherein, The at least one valid RO includes the RO among the plurality of ROs configured within the UL subband of the SBFD symbol set.
14. The method according to claim 11, wherein, The at least one valid RO includes at least N of the plurality of ROs located after the last DL non-SBFD symbol. gap N symbols and located after the last synchronization signal / physical broadcast channel (SSB) symbol. gap RO of symbols.
15. The method according to claim 11, wherein, When at least one of the plurality of ROs overlaps with a legacy RO in the time domain, the same SSB index as the SSB associated with the legacy RO is mapped to the synchronization signal / physical broadcast channel block (SSB) associated with the at least one RO.
16. A method performed by a base station in a wireless communication system, the method comprising: Configure non-overlapping subband full-duplex (SBFD) symbol sets and non-SBFD symbol sets in radio frames, wherein the SBFD symbol sets include non-UL symbols in which UL (uplink) subbands are configured; Configure multiple random access channel timings (ROs) for SBFD operations on multiple symbols in the radio frame; and Identify at least one effective RO among the plurality of ROs. Wherein, the at least one valid RO includes an RO that is continuously configured across the SBFD symbol set and the non-SBFD symbol set among the plurality of ROs.
17. The method according to claim 16, wherein, Of the plurality of ROs, only those configured in the non-SBFD symbol set are identified as invalid ROs.
18. The method according to claim 16, wherein, The at least one valid RO includes the RO among the plurality of ROs configured within the UL subband of the SBFD symbol set.
19. The method of claim 16, wherein, The at least one valid RO includes at least N of the plurality of ROs located after the last DL non-SBFD symbol. gap N symbols and located after the last synchronization signal / physical broadcast channel (SSB) symbol. gap RO of symbols.
20. The method of claim 16, wherein, When at least one of the plurality of ROs overlaps with a legacy RO in the time domain, the same SSB index as the SSB associated with the legacy RO is mapped to the synchronization signal / physical broadcast channel block (SSB) associated with the at least one RO.
