Method and apparatus for determining resources for a random access procedure in a wireless communication system

By identifying the mapping relationship between synchronization signal blocks and random access channel timing in a wireless communication system, the random access process is optimized, solving the problem of insufficient resource utilization in existing technologies and achieving more efficient random access and service continuity.

CN123126013APending Publication Date: 2026-11-17SAMSUNG ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202580026656.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2024-05-08
Filing Date
2025-03-18
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

Existing wireless communication systems, when supporting subband non-overlapping full-duplex communication, suffer from low efficiency in random access procedures, making it difficult to effectively identify and utilize multiple random access channel opportunities, resulting in insufficient resource utilization.

Method used

In a wireless communication system, the user equipment and the base station exchange System Information Block 1 (SIB1) to identify the mapping relationship between the Synchronization Signal Block (SSB) and the effective random access channel timing (RO), thereby selecting the appropriate physical random access channel (PRACH) transmission timing.

Benefits of technology

It improves the efficiency of random access procedures in wireless communication systems, optimizes resource utilization, and enhances service reliability and continuity.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123126013A_ABST
    Figure CN123126013A_ABST
Patent Text Reader

Abstract

This disclosure relates to 5G or 6G communication systems for supporting higher data transmission rates. More specifically, according to various embodiments of this disclosure, in a wireless communication system, a user equipment (UE) may include a transceiver and a controller coupled to the transceiver, wherein the controller may be configured to: receive from a base station a system information block 1 (SIB1) including information relating to a plurality of additional random access channel (RACH) timings (ROs); identify, based on the information, an SSB-RO mapping between a synchronization signal block (SSB) and an effective random access channel (RACH) timing (RO); and, based on the information, identify at least one RO from the plurality of additional ROs for physical RACH (PRACH) transmission.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure generally relates to wireless communication systems, and more specifically, to a method and apparatus for determining resources for a random access procedure in a wireless communication system. Background Technology

[0002] 5G mobile communication technology defines a wide frequency band, enabling high transmission rates and new services. It can be implemented not only in the "sub-6GHz" band, such as 3.5GHz, but also in the "above 6GHz" band (including 28GHz and 39GHz), known as millimeter wave (mmWave). Furthermore, to achieve transmission rates fifty times faster than 5G and ultra-low latency one-tenth that of 5G, 6G mobile communication technology (called Beyond 5G) has been considered in the terahertz (THz) band (e.g., the 95GHz to 3THz band).

[0003] In the early stages of 5G mobile communication technology development, to support and meet the performance requirements of services related to enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC), standardization has been continuously carried out in the following aspects: beamforming and massive MIMO for mitigating radio wave path loss and increasing radio wave transmission distance in millimeter waves; support for parameter sets (e.g., operating multiple subcarrier spacings) and dynamic operation of time slot formats for efficient utilization of millimeter wave resources; initial access technologies for supporting multi-beam transmission and broadband; definition and operation of BWP (bandwidth portion); new channel coding methods such as LDPC (low-density parity-check) codes for large data transmissions and polar codes for high-reliability transmission of control information; L2 preprocessing; and network slicing for providing specific networks for specific services.

[0004] Currently, given the services that 5G mobile communication technology needs to support, there is ongoing discussion about improvements and performance enhancements to the initial 5G mobile communication technology, and physical layer standardization has been carried out for the following technologies: V2X (Vehicle-to-Everything), which is used to assist autonomous vehicles in making driving decisions and improve user convenience based on information about the vehicle's location and status sent by the vehicle; NR-U (New Radio Unlicensed), which aims to enable system operation that complies with various regulatory requirements in unlicensed frequency bands; NR UE power saving; Non-Terrestrial Network (NTN), which is UE-satellite direct communication used to provide coverage in areas where communication with terrestrial networks is not possible; and positioning.

[0005] Furthermore, standardization of air interface architecture / protocols has been ongoing, involving technologies such as: Industrial Internet of Things (IIoT), which supports new services through interoperability and convergence with other industries; IAB (Integrated Access and Backhaul), which provides nodes for extending network service areas by supporting radio backhaul links and access links in an integrated manner; mobility enhancements including conditional handover and DAPS (Dual Active Stack) handover; and two-step random access (two-step RACH for NR) to simplify the random access process. Standardization of system architecture / services has also been ongoing, involving technologies such as: 5G baseline architectures (e.g., service-based architectures or service-based interfaces) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies; and mobile edge computing (MEC) for UE location-based reception services.

[0006] With the commercialization of 5G mobile communication systems, the number of connected devices will increase exponentially, necessitating enhancements to the functionality and performance of 5G mobile communication systems and the integration of connected devices. To this end, new research is planned in the following areas: Extended Reality (XR) for efficient support of AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality), etc.; 5G performance improvements and complexity reductions using Artificial Intelligence (AI) and Machine Learning (ML); AI service support; Metaverse service support; and drone communication.

[0007] Furthermore, this development of 5G mobile communication systems will lay the foundation for the development of technologies including: new waveforms for providing coverage in the terahertz band of 6G mobile communication technology; multi-antenna transmission technologies such as full-dimensional MIMO (FD-MIMO), array antennas, and massive MIMO; metamaterial-based lenses and antennas for improving terahertz band signal coverage; high-dimensional spatial multiplexing technologies using OAM (orbital angular momentum); and RIS (reconfigurable smart surfaces); full-duplex technologies for improving the frequency efficiency of 6G mobile communication technology and improving system networks; AI-based communication technologies for system optimization by leveraging satellites and AI (artificial intelligence) from the design phase and incorporating end-to-end AI support; and next-generation distributed computing technologies for enabling services with complexity levels exceeding the operational limits of UEs by utilizing ultra-high-performance communication and computing resources.

[0008] As mentioned above, advancements in wireless communication systems have enabled the provision of a wide variety of services, creating a need for methods that can seamlessly deliver these services. Summary of the Invention

[0009] Technical issues

[0010] Based on the above discussion, this disclosure aims to provide an apparatus and method for performing random access of a UE supporting subband non-overlapping full duplex (SBFD) communication in a wireless communication system.

[0011] Solution

[0012] According to various embodiments of this disclosure, a user equipment (UE) in a wireless communication system may include: a transceiver; and a controller coupled to the transceiver, wherein the controller may be configured to: receive from a base station a system information block 1 (SIB1) including information about a plurality of additional random access channel (RACH) timings (ROs); identify, based on the information, a synchronization signal block (SSB)-RACH timing (RO) mapping between a synchronization signal block (SSB) and a valid RO; and identify, based on the information, at least one RO from the plurality of additional ROs for physical RACH (PRACH) transmission.

[0013] According to various embodiments of the present disclosure, a base station in a wireless communication system may include: a transceiver; and a controller coupled to the transceiver, wherein the controller may be configured to: transmit a system information block 1 (SIB1) to a user equipment (UE) including information about a plurality of additional random access channel (RACH) timings (ROs); and receive a physical RACH (PRACH) from the UE on at least one of the plurality of additional ROs according to a synchronization signal block (SSB)-RACH timing (RO) mapping between a synchronization signal block (SSB) and a valid RO based on the information.

[0014] According to various embodiments of this disclosure, a method performed by a user equipment (UE) in a wireless communication system may include: receiving from a base station a system information block 1 (SIB1) including information about a plurality of additional random access channel (RACH) timings (ROs); identifying, based on the information, a synchronization signal block (SSB)-RACH timing (RO) mapping between a synchronization signal block (SSB) and a valid RO; and identifying, based on the information, at least one RO from the plurality of additional ROs for physical RACH (PRACH) transmission.

[0015] According to various embodiments of the present disclosure, a method performed by a base station in a wireless communication system may include: sending a system information block 1 (SIB1) to a user equipment (UE) including information about a plurality of additional random access channel (RACH) timings (ROs); and receiving a physical RACH (PRACH) from the UE on at least one of the plurality of additional ROs according to a synchronization signal block (SSB)-RACH timing (RO) mapping between a synchronization signal block (SSB) and a valid RO based on the information.

[0016] Beneficial effects of the invention

[0017] The embodiments of this disclosure provide apparatus and methods for effectively providing services in wireless communication systems.

[0018] The beneficial effects that can be obtained from this disclosure are not limited to those described above, and other effects not mentioned herein can be clearly understood by those skilled in the art from the following description. Attached Figure Description

[0019] Figure 1 The basic structure of the time-frequency domain in a wireless communication system according to an embodiment of the present disclosure is shown.

[0020] Figure 2 The structure of frames, subframes, and time slots in a wireless communication system according to embodiments of the present disclosure is shown.

[0021] Figure 3 An example of bandwidth configuration in a wireless communication system according to an embodiment of the present disclosure is shown.

[0022] Figure 4 An example of the configuration of the control resource set for a downlink (DL) control channel in a wireless communication system according to an embodiment of the present disclosure is shown.

[0023] Figure 5 The structure of a downlink control channel in a wireless communication system according to an embodiment of the present disclosure is shown.

[0024] Figure 6 An example of a method for a base station and a UE to transmit / receive data in a wireless communication system according to embodiments of the present disclosure, taking into account downlink data channel and rate matching resources.

[0025] Figure 7 An example of frequency domain resource allocation for a Physical Downlink Shared Channel (PDSCH) in a wireless communication system according to an embodiment of the present disclosure is shown.

[0026] Figure 8An example of time-domain resource allocation for a PDSCH in a wireless communication system according to an embodiment of the present disclosure is shown.

[0027] Figure 9 An example of time-domain resource allocation of data channels and control channels according to subcarrier spacing is shown in a wireless communication system according to an embodiment of the present disclosure.

[0028] Figure 10 The radio protocol structures of a base station and a UE in single-cell, carrier aggregation, and dual connectivity scenarios in a wireless communication system according to embodiments of the present disclosure are illustrated.

[0029] Figure 11 An example of a random access procedure according to an embodiment of this disclosure is shown.

[0030] Figure 12 Examples of time-division duplex (TDD) configurations and subband non-overlapping full-duplex (SBFD) configurations according to embodiments of the present disclosure are shown.

[0031] Figure 13 Examples of effective RACH timing in TDD and SBFD configurations according to embodiments of this disclosure are shown.

[0032] Figure 14 An example of RACH timing according to an embodiment of this disclosure is shown.

[0033] Figure 15 Examples of RACH timing in TDD and SBFD configurations according to embodiments of this disclosure are shown.

[0034] Figure 16 An example of RACH timing using a RACH configuration table for the FDD band or the Supplemental Uplink (SUL) band, according to an embodiment of this disclosure, is shown.

[0035] Figure 17 The operation flow of a UE transmitting signals during a RACH timing according to an embodiment of the present disclosure is illustrated.

[0036] Figure 18 An example of RACH timing based on SBFD configuration shift according to an embodiment of this disclosure is shown.

[0037] Figure 19 Another operational flow for a UE to transmit signals during a RACH timing is illustrated according to an embodiment of this disclosure.

[0038] Figure 20 An example of RACH timing shifted according to an embodiment of the present disclosure is shown.

[0039] Figure 21Examples of some SSBs excluded from SSB-RO mapping according to embodiments of this disclosure are shown.

[0040] Figure 22 Examples are shown where some SSBs of an RO according to embodiments of this disclosure are excluded from the SSB-RO mapping.

[0041] Figure 23 An example of RO deactivation based on SSB index value is shown according to an embodiment of this disclosure.

[0042] Figure 24 An example of RO deactivation based on the index value of RO according to an embodiment of this disclosure is shown.

[0043] Figure 25 The structure of a UE in a wireless communication system according to an embodiment of the present disclosure is shown.

[0044] Figure 26 The structure of a base station in a wireless communication system according to an embodiment of the present disclosure is shown. Detailed Implementation

[0045] In the following, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.

[0046] In describing the embodiments, descriptions of technical topics well-known in the art to which this disclosure pertains and not directly related to this disclosure will be omitted. This is intended to avoid obscuring the main points of this disclosure due to unnecessary descriptions, thereby conveying the main points of this disclosure more clearly.

[0047] For the same reason, some components in the accompanying drawings may be exaggerated, omitted, or shown schematically. Furthermore, the dimensions of individual components do not necessarily reflect their actual dimensions. In all the drawings, the same reference numerals are assigned to the same or corresponding components.

[0048] The advantages and features of this disclosure, as well as methods for achieving these advantages and features, will become apparent from the following embodiments described in detail with reference to the accompanying drawings. However, this disclosure is not limited to the embodiments disclosed below and can be implemented in various different forms. These embodiments are provided only to make this disclosure sufficient and complete, and to fully convey the scope of this disclosure to those skilled in the art. This disclosure is defined only by the scope of the claims. Throughout the specification, the same reference numerals refer to the same parts. Furthermore, detailed descriptions of related functions or configurations will be omitted when it is determined that such detailed descriptions may unnecessarily obscure the gist of the disclosure. The terms used below are defined in consideration of their function in this disclosure and may vary depending on the intent or customary practice of the user or operator. Therefore, these terms should be interpreted in light of the entirety of this specification.

[0049] In the following description, a base station is an entity that allocates resources to a terminal and can be at least one of a gNode B, eNode B, Node B, base station (BS), radio access unit, base station controller, or node on a network. A terminal can include a user equipment (UE), mobile station (MS), cellular phone, smartphone, computer, or multimedia system capable of performing communication functions. As used herein, "downlink (DL)" refers to a radio link through which a base station transmits signals to a terminal, and "uplink (UL)" refers to a radio link through which a terminal transmits signals to a base station. Furthermore, while LTE or LTE-A systems may be described exemplarily below, embodiments of this disclosure can also be applied to other communication systems with similar technical backgrounds or channel types. Examples of such communication systems may include fifth-generation mobile communication technologies developed after LTE-A (e.g., 5G New Radio (NR)), and in the following description, "5G" can be a concept encompassing existing LTE, LTE-A, and other similar services. Moreover, based on the judgment of those skilled in the art, this disclosure can be applied to other communication systems with modifications without significantly departing from its scope.

[0050] It should be understood that each box in the flowchart illustration, and combinations of boxes in the flowchart illustration, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of said computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more boxes of the flowchart. These computer program instructions can also be stored in a computer-usable or computer-readable storage medium capable of directing a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in said computer-usable or computer-readable storage medium produce an article of writing including instruction means for implementing the functions specified in one or more boxes of the flowchart. The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on said computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on said computer or other programmable apparatus, provide steps for implementing the functions specified in one or more boxes of the flowchart.

[0051] Furthermore, each box in the flowchart diagram may represent a module, segment, or code section that includes one or more executable instructions for implementing one or more specified logical functions. It should also be noted that in some alternative implementations, the functions marked in the boxes may not occur in the order shown. For example, two boxes shown consecutively may actually execute substantially simultaneously, or these boxes may sometimes execute in reverse order depending on the functions involved.

[0052] As used in embodiments of this disclosure, the term "unit" refers to a software element or a hardware element such as a field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC), and said "unit" can perform certain functions. However, "unit" does not always have a meaning limited to software or hardware. A "unit" can be configured to be stored in an addressable storage medium or configured to execute one or more processors. Thus, a "unit" includes, for example, software elements, object-oriented software elements, class elements or task elements, processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and parameters. Elements and functions provided by a "unit" can be combined into a smaller number of elements or "units," or can be divided into a larger number of elements or "units." Furthermore, said elements and "units" can be implemented to reproduce one or more CPUs within a device or secure multimedia card. Additionally, a "unit" in the embodiments may include one or more processors.

[0053] Wireless communication systems are evolving into broadband wireless communication systems that, in addition to typical voice-based services, utilize communication standards such as 3GPP High-Speed ​​Packet Access (HSPA), LTE (Long Term Evolution or Evolved Universal Terrestrial Radio Access (E-UTRA)), LTE-Advanced (LTE-A), LTE-Pro, 3GPP2 High-Rate Packet Data (HRPD), Ultra Mobile Broadband (UMB), and IEEE 802.16e to provide high-speed and high-quality packet data services.

[0054] As a typical example of a broadband wireless communication system, the LTE system employs an Orthogonal Frequency Division Multiplexing (OFDM) scheme in the downlink (DL) and a Single-Carrier Frequency Division Multiple Access (SC-FDMA) scheme in the uplink (UL). The uplink refers to the radio link through which a User Equipment (UE) or Mobile Station (MS) transmits data or control signals to a Base Station (BS) (or eNode B), and the downlink refers to the radio link through which the Base Station transmits data or control signals to the UE. These multiple access schemes can separate the data or control information of each user by allocating and manipulating the time-frequency resources used to transmit data or control information for each user, ensuring that the data or control information of each user does not overlap, i.e., establishing orthogonality.

[0055] As a post-LTE communication system, 5G communication systems must flexibly respond to the various requirements of users, service providers, and others, and therefore must support services that meet diverse needs. Services considered in 5G communication systems include enhanced mobile broadband (eMBB) communication, massive machine-type communication (mMTC), and ultra-reliable low-latency communication (URLLC).

[0056] eMBB aims to provide higher data rates than those supported by existing LTE, LTE-A, or LTE-Pro systems. For example, in 5G communication systems, eMBB must provide a peak downlink data rate of 20Gbps and an uplink peak data rate of 10Gbps for a single base station. Furthermore, in addition to the maximum data rate, 5G communication systems must also provide improved user-aware data rates to the UE. To meet these requirements, improved transmit / receive technologies, including further enhanced multiple-input multiple-output (MIMO) transmission techniques, are needed. Moreover, the data rates required by 5G communication systems can be achieved by using a frequency bandwidth greater than 20MHz in the 3GHz to 6GHz band or above, instead of using a maximum transmission bandwidth of 20MHz in the 2GHz band as in LTE.

[0057] Furthermore, mMTC is being considered in 5G communication systems to support application services such as the Internet of Things (IoT). To effectively deliver IoT, mMTC has requirements such as supporting a large number of UEs within a cell, enhancing UE coverage, extending battery life, and reducing UE costs. Since IoT provides communication capabilities by being provided to various sensors and devices, it must support a large number of UEs within a cell (e.g., 1,000,000 UEs / km²). Moreover, due to the nature of the service, UEs supporting mMTC are likely to be located in shadow areas not covered by the cell (such as building basements), thus potentially requiring wider coverage than UEs for other services provided by 5G communication systems. UEs supporting mMTC must be configured for low cost, and due to the difficulty in frequently replacing UE batteries, long battery lives such as 10 to 15 years may be required.

[0058] Finally, URLLC is a mission-critical wireless communication service based on cellular networks. For example, URLLC can be used for services such as remote control of robots or machines, industrial automation, unmanned aerial vehicles, remote healthcare, and emergency alerts. Therefore, URLLC must provide communication with ultra-low latency and ultra-high reliability. For example, services supporting URLLC must meet an air interface latency of less than 0.5 ms, and may also require 10 -5 Or even lower packet error rates. Therefore, for services that support URLLC, 5G systems must provide shorter transmission time intervals (TTIs) than other services, and may also require designs that allocate significant resources in the frequency band to ensure the reliability of the communication link.

[0059] The three services in 5G—eMBB, URLLC, and mMTC—can be multiplexed and transmitted within a single system. In this case, different transmit / receive technologies and parameters can be used across the services to meet their varying requirements. Of course, 5G is not limited to these three services.

[0060] [NR Time and Frequency Resources]

[0061] The frame structure of the 5G system will be described in more detail below with reference to the accompanying drawings.

[0062] Figure 1 The basic time-frequency domain structure of a wireless communication system according to embodiments of the present disclosure is shown. More specifically, Figure 1 The basic structure of the radio resource domain, or instantaneous frequency domain, used for transmitting data or control channels in a 5G system is shown.

[0063] exist Figure 1 In the diagram, the horizontal axis represents the time domain, and the vertical axis represents the frequency domain. The basic unit of resources in the time-frequency domain is a resource element (RE) 101, which can be defined as an orthogonal frequency division multiplexing (OFDM) symbol 102 on the time axis and a subcarrier 103 on the frequency axis. In the frequency domain, N SC RB One (e.g., 12) consecutive REs can constitute a resource block (RB) 104.

[0064] Figure 2 The structure of frames, subframes, and time slots in a wireless communication system according to embodiments of the present disclosure is shown.

[0065] Figure 2 An example of the structure of frame 200, subframe 201, and time slot 202 is shown. A frame 200 can be defined as 10 ms. A subframe 201 can be defined as 1 ms, therefore a frame 200 can include a total of ten subframes 201. A time slot 202 or 203 can be defined as 14 OFDM symbols (i.e., the number of symbols per time slot). =14). A subframe 201 may include one or more time slots 202 and 203, and the number of time slots 202 and 203 in each subframe 201 may vary depending on the configuration value μ of the subcarrier spacing 204 or 205.

[0066] Reference Figure 2 , Figure 2The diagram illustrates the cases where the subcarrier spacing configuration value is μ=0 (204) and μ=1 (205). In the case of μ=0 (204), a subframe 201 may include one time slot 202; and in the case of μ=1 (205), a subframe 201 may include two time slots 203. That is, the number of time slots in each subframe... The number of time slots per frame can vary depending on the subcarrier spacing configuration value μ. They can be different accordingly. and μ can be defined according to the configuration of each subcarrier spacing as shown in Table a below.

[0067] [Table a]

[0068] [Bandwidth Component (BWP)]

[0069] Next, the bandwidth portion (BWP) configuration in a 5G communication system will be described in detail with reference to the accompanying drawings.

[0070] Figure 3 An example of bandwidth configuration in a wireless communication system according to an embodiment of the present disclosure is shown.

[0071] Figure 3 An example is shown where UE bandwidth 300 is configured to include two bandwidth portions, namely bandwidth portion #1 (BWP#1) 301 and bandwidth portion #2 (BWP#2) 302. The base station can configure one or more bandwidth portions for the UE, and can configure the following information given in Table b for each bandwidth portion.

[0072] [Table b]

[0073] Of course, the configuration information is not limited to the examples above, and in addition to the configuration information mentioned above, various parameters related to the bandwidth portion can also be configured for the UE. The base station can transmit configuration information to the UE via upper-layer signaling (e.g., Radio Resource Control (RRC) signaling). At least one of the configured bandwidth portions can be activated. Whether the configured bandwidth portion is activated can be semi-statically transmitted to the UE from the base station via RRC signaling, or dynamically transmitted to the UE via downlink control information (DCI).

[0074] According to some embodiments, before establishing a Radio Resource Control (RRC) connection, the base station can configure an Initial Bandwidth Part (BWP) for initial access for the UE via the Master Information Block (MIB). More specifically, during the initial access step, the UE can receive configuration information related to a Control Resource Set (CORESET) and a search space via the MIB, which can be used to transmit a PDCCH for receiving system information required for initial access (which may correspond to Residual System Information (RMSI) or System Information Block 1 (SIB1)). Each of the Control Resource Set and search space configured via the MIB can be considered as ID 0. The base station can notify the UE of configuration information related to CORESET #0 via the MIB, such as frequency allocation information, time allocation information, and parameter sets. Furthermore, the base station can notify the UE of configuration information related to the monitoring period and timing of Control Resource Set #0 via the MIB, i.e., configuration information related to search space #0. The UE can consider the frequency domain configured by Control Resource Set #0 obtained from the MIB as the Initial Bandwidth Part for initial access. The ID of the Initial Bandwidth Part can be considered as 0.

[0075] The bandwidth-related configurations supported by the 5G system can be used for various purposes.

[0076] According to some embodiments, if the bandwidth supported by the UE is less than the system bandwidth, this can be supported through bandwidth portion configuration. For example, the base station can configure the frequency position of the bandwidth portion for the UE (configuration information 2), enabling the UE to send / receive data at a specific frequency position within the system bandwidth.

[0077] Furthermore, according to some embodiments, to support different parameter sets, the base station can configure multiple bandwidth portions for the UE. For example, to support the UE using both 15kHz and 30kHz subcarrier spacings for data transmission / reception, the two bandwidth portions can be configured with 15kHz and 30kHz subcarrier spacings respectively. Different bandwidth portions can undergo frequency division multiplexing (FDM), and if data is to be transmitted / received at a specific subcarrier spacing, the bandwidth portion configured for that subcarrier spacing can be activated.

[0078] Furthermore, according to some embodiments, to reduce the power consumption of the UE, the base station can configure bandwidth portions with different bandwidth sizes for the UE. For example, if the UE supports a fairly large bandwidth (e.g., 100MHz) and always utilizes that bandwidth to send / receive data, it may result in considerable power consumption. In particular, unnecessarily utilizing a large bandwidth of 100MHz to monitor the downlink control channel in the absence of service may be quite inefficient from a power consumption perspective. To reduce the power consumption of the UE, the base station can configure a bandwidth portion with a relatively small bandwidth (e.g., a 20MHz bandwidth portion). In the absence of service, the UE can perform monitoring operations in the 20MHz bandwidth portion, and if data is generated, it can send / receive data using the 100MHz bandwidth portion as instructed by the base station.

[0079] In conjunction with the bandwidth portion configuration method, before establishing an RRC connection, the UE can receive configuration information related to the initial bandwidth portion via the MIB during the initial access step. More specifically, the UE can have a control resource set (CORESET) configured for a downlink control channel that can be used to transmit downlink control information (DCI), which is used to schedule system information blocks (SIBs) according to the MIB of the physical broadcast channel (PBCH). The bandwidth of the control resource set configured by the MIB can be regarded as the initial bandwidth portion, and the UE can receive the physical downlink shared channel (PDSCH) used for transmitting SIBs through the configured initial bandwidth portion. In addition to receiving SIBs, the initial bandwidth portion can also be used for other system information (OSI), paging, and random access.

[0080] [Bandwidth Component (BWP) Change]

[0081] If the UE has one or more bandwidth portions configured for it, the base station can indicate to the UE to change (or switch or transform) the bandwidth portion by using the bandwidth portion indicator field within the DCI. For example, if Figure 3 If the UE's currently active bandwidth is bandwidth #1 301, the base station can use the bandwidth portion indicator in the DCI to indicate bandwidth #2 302. The UE can then change its bandwidth to bandwidth #2 302 as indicated by the received bandwidth portion indicator in the DCI.

[0082] As mentioned above, DCI-based bandwidth portion changes can be indicated using the DCI used to schedule PDSCH or PUSCH. Therefore, upon receiving a bandwidth portion change request, the UE needs to be able to receive or transmit PDSCH or PUSCH scheduled by the corresponding DCI without problems within the changed bandwidth portion. To this end, the standard specifies the required delay time (T) during the bandwidth portion change. BWPThe requirements of ) can be defined, for example, as given in Table c below.

[0083] [Table c]

[0084] Note 1: Depends on UE capabilities.

[0085] Note 2: If the BWP handover involves a change in the SCS, the BWP handover delay is determined by the larger of the SCS before the BWP handover and the SCS after the BWP handover.

[0086] Depending on the UE's capabilities, the requirement for bandwidth portion change delay time supports either Type 1 or Type 2. The UE can report the supported bandwidth portion change delay time types to the base station.

[0087] If the UE receives a DCI including a bandwidth partial change indicator in time slot n, then according to the above requirements regarding the bandwidth partial change delay time, the UE can proceed no later than time slot n+T. BWP The change to the new bandwidth portion indicated by the bandwidth portion change indicator is completed at the specified time, and the UE can transmit / receive data channels scheduled by the corresponding DCI within the newly changed bandwidth portion. Furthermore, the UE can transmit / receive data channels scheduled by the corresponding DCI within the newly changed bandwidth portion. If the base station wants to use the new bandwidth portion to schedule data channels, the base station can consider the UE's bandwidth portion change delay time (T). BWP This method determines the temporal resource allocation for the data channel. For example, when scheduling a data channel using a new bandwidth portion, combined with the method for determining the temporal resource allocation for the data channel, the base station can schedule the corresponding data channel after the bandwidth portion change delay time. Therefore, the UE can expect the DCI indicating the bandwidth portion change to indicate a delay time less than the bandwidth portion change delay time (T). BWP The time slot offset (K0 or K2) value.

[0088] If the UE receives a DCI indicating a partial change in bandwidth (e.g., DCI format 1_1 or 0_1), the UE may refrain from transmitting or receiving during the time interval from the third symbol of the slot used to receive the PDCCH including the corresponding DCI to the start point of the slot indicated by the slot offset (K0 or K2) value indicated by the time domain resource allocation indicator field in the corresponding DCI. For example, if the UE receives a DCI indicating a partial change in bandwidth in slot n, and the slot offset value indicated by the corresponding DCI is K, the UE may refrain from transmitting or receiving from the third symbol of slot n until the symbols preceding slot n+K (e.g., the last symbol of slot n+K-1).

[0089] [SS / PBCH block]

[0090] Next, the synchronization signal (SS) / PBCH block in 5G will be described.

[0091] The SS / PBCH block can refer to a physical layer channel block that includes the primary synchronization signal (PSS), secondary synchronization signal (SSS), and PBCH. Details are as follows.

[0092] - PSS: PSS is a signal that serves as a reference for downlink time / frequency synchronization and provides information about a portion of the cell ID.

[0093] - SSS: The SSS serves as the reference for downlink time / frequency synchronization and provides additional information about the cell ID not provided by the PSS. Furthermore, the SSS can be used as a reference signal for PBCH demodulation.

[0094] - PBCH: The PBCH provides the necessary system information required by the UE to transmit / receive data and control channels. This necessary system information may include search space-related control information indicating radio resource mapping information for control channels, scheduling control information related to separate data channels used for transmitting system information, etc.

[0095] - SS / PBCH Blocks: SS / PBCH blocks consist of a combination of PSS, SSS, and PBCH. One or more SS / PBCH blocks can be sent within a 5ms time period, and each sent SS / PBCH block can be distinguished by an index.

[0096] The UE can detect the PSS and SSS during the initial access procedure and can decode the PBCH. The UE can obtain the MIB from the PBCH, and this can be used to configure the control resource set (CORESET) #0 (which may, for example, correspond to a control resource set with control resource set index 0). The UE can monitor the control resource set #0 by assuming that the demodulation reference signal (DMRS) transmitted in the selected SS / PBCH block is quasi-co-located (QCL) with control resource set #0. The UE can receive system information using downlink control information transmitted in control resource set #0. The UE can obtain the random access channel (RACH) configuration information required for initial access from the received system information. The UE can send a physical RACH (PRACH) to the base station considering the selected SS / PBCH index, and the base station can obtain information related to the SS / PBCH block index selected by the UE upon receiving the PRACH. The base station can know which SS / PBCH block the UE selected from and the fact that the associated control resource set #0 is being monitored.

[0097] [PDCCH: About DCI]

[0098] Next, we will describe downlink control information (DCI) in a 5G system in detail.

[0099] In 5G systems, scheduling information related to uplink data (or Physical Uplink Shared Channel (PUSCH)) or downlink data (or Physical Downlink Shared Channel (PDSCH)) is included in the DCI and transmitted from the base station to the UE via the DCI. The UE can monitor the fallback DCI format and the non-fallback DCI format for either the PUSCH or PDSCH. The fallback DCI format may include predefined fixed fields between the base station and the UE, while the non-fallback DCI format may include configurable fields.

[0100] The DCI message undergoes channel coding and modulation before being transmitted via the Physical Downlink Control Channel (PDCCH). Cyclic Redundancy Check (CRC) can be appended to the DCI message payload, and the CRC can be scrambled by a Radio Network Temporary Identifier (RNTI) corresponding to the UE's identifier. Different RNTIs can be used depending on the purpose of the DCI message (e.g., UE-specific data transmission, power control command, or random access response). The RNTI may not be explicitly transmitted, but can be included in the CRC calculation process. Upon receiving a DCI message transmitted via the PDCCH, the UE can use the assigned RNTI to identify the CRC, and if the CRC identification is correct, the UE knows that the corresponding message has been sent to it.

[0101] For example, the DCI used for scheduling PDSCH related to System Information (SI) can be scrambled by SI-RNTI. The DCI used for scheduling PDSCH related to Random Access Response (RAR) messages can be scrambled by RA-RNTI. The DCI used for scheduling PDSCH related to paging messages can be scrambled by P-RNTI. The DCI used for notifying Slot Format Indicator (SFI) can be scrambled by SFI-RNTI. The DCI used for notifying Transmit Power Control (TPC) can be scrambled by TPC-RNTI. The DCI used for scheduling UE-specific PDSCH or PUSCH can be scrambled by Cell RNTI (C-RNTI).

[0102] DCI format 0_0 can be used as a fallback DCI for scheduling PUSCH, and in this case, CRC can be scrambled by C-RNTI. The DCI format 0_0 with CRC scrambled by C-RNTI can include, for example, the information given in Table d below.

[0103] [Table d]

[0104] The English translations in the table above are as follows: Identifier for DCI formats: identifier of DCI format

[0105] Bit: bit

[0106] Frequency domain resource assignment: frequency domain resource assignment

[0107] Time domain resource assignment: time domain resource assignment

[0108] Frequency hopping flag: frequency hopping flag

[0109] Modulation and coding scheme: modulation and coding scheme

[0110] New data indicator: new data indicator

[0111] Redundancy version: redundancy version

[0112] HARQ process number: HARQ process number

[0113] TPC command for scheduled PUSCH: TPC command for the scheduled PUSCH

[0114] UL / SUL indicator: UL / SUL indicator

[0115] DCI format 0_1 ​​can be used as a non-back-off DCI for scheduling PUSCH, and in this case, CRC can be scrambled by C-RNTI. The DCI format 0_1 ​​with CRC scrambled by C-RNTI can include, for example, the information given in Table e below.

[0116] [Table e]

[0117]

[0118] The English translations in the table above are as follows: Carrier indicator: carrier indicator

[0119] Bit: bit

[0120] UL / SUL indicator: UL / SUL indicator

[0121] Identifier for DCI formats: identifier of DCI format

[0122] Bandwidth part indicator: bandwidth part indicator

[0123] Frequency domain resource assignment: frequency domain resource assignment

[0124] For resource allocation type 0: for resource allocation type 0

[0125] For resource allocation type 1: for resource allocation type 1

[0126] Time domain resource assignment: time domain resource assignment

[0127] VRB-to-PRB mapping-0 or 1 bit, only for resource allocation type: VRB to PRB mapping - 0 or 1 bit, only for resource allocation type 1

[0128] 0 bit if only resource allocation type 0 is configured: if only resource allocation type 0 is configured, it is 0 bit; 1 bit otherwise: it is 1 bit otherwise

[0129] Frequency hopping flag-0 or 1 bit, only for resource allocation type1: frequency hopping flag - 0 or 1 bit, only for resource allocation type 1

[0130] 0 bit if only resource allocation type 0 is configured: If the allocation type is 0, then it is 0 bits.

[0131] 1 bit otherwise: Otherwise, it is 1 bit

[0132] Modulation and coding scheme

[0133] New data indicator: New data indicator

[0134] Redundancy version:

[0135] HARQ process number: HARQ process number

[0136] 1 st downlink assignment index: First downlink assignment index

[0137] Or:

[0138] Bit: Bit

[0139] 1 bit for semi-static HARQ-ACK codebook:

[0140] 2 bits for dynamic HARQ-ACK codebook with single HARQ-ACK codebook: Yes For a dynamic HARQ-ACK codebook with a single HARQ-ACK codebook, it is 2 bits.

[0141] 2 nd downlink assignment index: Second downlink assignment index

[0142] 2 bits for dynamic HARQ-ACK codebook with two HARQ-ACK sub-codebooks: For a dynamic HARQ-ACK codebook with two HARQ-ACK subcodebooks, it is 2 bits.

[0143] 0 bit otherwise: Otherwise, it is 0 bits.

[0144] TPC command for scheduled PUSCH: The TPC command used for scheduled PUSCH.

[0145] SRS resource indicator: SRS resource indicator

[0146] Bits for non-codebook based PUSCH transmission: For non-codebook based PUSCH... Transmission, for log 2 (∑_(k=1)^(L_max) C(N_SRS,k)) 1 bit; Bits for codebook-based PUSCH transmission: For codebook-based PUSCH transmission, log 2 (N_SRS) bits

[0147] Precoding information and number of layers:

[0148] Up to 6 bits: up to 6 bits

[0149] Antenna ports: Antenna ports

[0150] Up to 5 bits: a maximum of 5 bits

[0151] SRS request: SRS request

[0152] CSI request: CSI request

[0153] CBG transmission information: CBG transmission information

[0154] PTRS-DMRS association: PTRS-DMRS association

[0155] Beta_offset: beta_offset indicator

[0156] DMRS sequence initialization: DMRS sequence initialization

[0157] DCI format 1_0 can be used as a fallback DCI for scheduling PDSCH, and in this case, CRC can be scrambled by C-RNTI. The DCI format 1_0 with CRC scrambled by C-RNTI can include, for example, the information given in Table f below.

[0158] [Table f]

[0159] The English translations in the table above are as follows: Identifier for DCI formats.

[0160] bit

[0161] Frequency domain resource assignment:

[0162] Time domain resource assignment:

[0163] VRB-to-PRB mapping: VRB to PRB mapping

[0164] Modulation and coding scheme

[0165] New data indicator: New data indicator

[0166] Redundancy version:

[0167] HARQ process number: HARQ process number

[0168] Downlink assignment index: Downlink assignment index

[0169] TPC command for scheduled PUCCH: The TPC command used for scheduled PUCCHs.

[0170] PUCCH resource indicator: PUCCH resource indicator

[0171] PDSCH-to-HARQ feedback timing indicator: PDSCH to HARQ feedback timing indicator

[0172] DCI format 1_1 can be used as a non-back-off DCI for scheduling PDSCH, and in this case, CRC can be scrambled by C-RNTI. The DCI format 1_1 with CRC scrambled by C-RNTI can include, for example, the information given in Table g below.

[0173] [Table g]

[0174]

[0175] The English translations in the table above are as follows: Carrier indicator: Carrier indicator

[0176] Bit: Bit

[0177] Identifier for DCI format: Identifier for DCI format

[0178] Bandwidth part indicator: Bandwidth part indicator

[0179] Frequency domain resource assignment:

[0180] For resource allocation type 0:

[0181] For resource allocation type 1:

[0182] Time domain resource assignment

[0183] VRB-to-PRB mapping: VRB to PRB mapping

[0184] 0 or 1 bit, only for resource allocation type 1: 0 or 1 bit, used only for resource allocation Matching type 1

[0185] 0 bit if only resource allocation type 0 is configured: If the allocation type is 0, then it is 0 bits.

[0186] 1 bit otherwise: Otherwise, it is 1 bit

[0187] PRB bundling size indicator: PRB bundling size indicator

[0188] Rate matching indicator:

[0189] ZP CSI-RS trigger: ZP CSI-RS trigger

[0190] For transport block:

[0191] Bit: Bit

[0192] Modulation and coding scheme

[0193] New data indicator: New data indicator

[0194] Redundancy version:

[0195] For transport block 1:

[0196] For transport block 2:

[0197] Modulation and coding scheme

[0198] New data indicator: New data indicator

[0199] Redundancy version:

[0200] HARQ process number: HARQ process number

[0201] Downlink assignment index: Downlink assignment index

[0202] TPC command for scheduled PUCCH: The TPC command used for scheduled PUCCHs.

[0203] PUCCH resource indicator: PUCCH resource indicator

[0204] PDSCH-to-HARQ_feedback timing indicator: PDSCH to HARQ feedback timing indicator

[0205] Antenna ports: Antenna ports

[0206] Transmission configuration indication

[0207] SRS request: SRS request

[0208] CBG transmission information: CBG transmission information

[0209] CBG flushing out information: CBG flushing information

[0210] DMRS sequence initialization: DMRS sequence initialization

[0211] [PDCCH: CORESET, REG, CCE, and Search Space]

[0212] The downlink control channel in a 5G communication system will be described in more detail below with reference to the accompanying drawings.

[0213] Figure 4 An example of the configuration of the control resource set of the downlink control channel in a wireless communication system according to an embodiment of the present disclosure is shown. Figure 4 An example is shown where the UE bandwidth portion 410 is configured along the frequency axis and two control resource sets (control resource set #1 401 and control resource set #2 402) are configured along the time axis within a timeslot 420. Control resource sets 401 and 402 can be configured along the frequency axis within a specific frequency resource 403 throughout the entire UE bandwidth portion 410. Each control resource set can be configured along the time domain as one or more OFDM symbols, and the number of OFDM symbols can be defined as the control resource set duration 404. (Refer to...) Figure 4 In the example shown, control resource set #1 401 is configured to have a control resource set duration of 2 symbols, and control resource set #2 402 is configured to have a control resource set duration of 1 symbol.

[0214] The base station can configure the control resource set in 5G for the UE via upper-layer signaling (e.g., system information, master information block (MIB), radio resource control (RRC) signaling). Configuring the control resource set for the UE may mean providing information such as the control resource set identifier, the frequency location of the control resource set, and the symbol duration of the control resource set. For example, the information used to configure the control resource set may include the following information in Table h below.

[0215] [Table h]

[0216]

[0217] The English translations in the table above are as follows: Corresponds to L1 parameter: Corresponds to L1 parameter

[0218] Sequence: a sequence

[0219] Duration: Duration

[0220] Bit string:

[0221] Integer: Integer

[0222] Interleaved: Interlaced

[0223] Choice: Select

[0224] Enumerated: the enumerated set

[0225] Optional: optional

[0226] nonInterleaved: Non-interleaved

[0227] Null: Empty value

[0228] Size: Size

[0229] Enabled: Enabled

[0230] Need: required

[0231] In table h, the tci-StatesPDCCH (transmission configuration indication, TCI) configuration information may include information related to one or more synchronization signal (SS) / physical broadcast channel (PBCH) block indices or channel state information reference signal (CSI-RS) indices of the DMRS quasi-co-located (QCL) transmitted in the corresponding control resource set.

[0232] Figure 5 The structure of a downlink control channel in a wireless communication system according to an embodiment of the present disclosure is shown. More specifically, Figure 5 An example of the basic unit that constitutes the time and frequency resources available in the downlink control channel in 5G is shown.

[0233] according to Figure 5 The basic unit constituting the time and frequency resources of the control channel can be called a resource element group (REG) 503, and REG 503 can be defined by an OFDM symbol 501 on the time axis and a physical resource block (PRB) 502 (e.g., 12 subcarriers) on the frequency axis. The base station can configure the downlink control channel allocation unit by cascading REG 503.

[0234] Assuming Figure 5 As shown, the basic unit for downlink control channel allocation in 5G is a control channel element (CCE) 504, and one CCE 504 can include multiple REG 503s. For example, to describe Figure 5The REG 503 shown can include 12 REs, and if a CCE 504 includes six REG 503s, then a CCE 504 can include 72 REs. Once configured, a downlink control resource set can include multiple CCE 504s, and a specific downlink control channel can be mapped to one or more CCE 504s and then transmitted according to the aggregation level (AL) in the control resource set. CCE 504s in the control resource set are distinguished by numbers, and these numbers can be assigned according to a logical mapping scheme.

[0235] Figure 5 The basic unit of the downlink control channel shown, REG 503, can include both the RE to which the DCI is mapped and the region to which the reference signal (DMRS 505) used for decoding the DCI is mapped. Figure 5 As shown, three DMRS 503s can be transmitted within one REG 505. Depending on the aggregation level (AL), the number of CCEs required to transmit the PDCCH can be 1, 2, 4, 8, or 16, and different numbers of CCEs can be used to achieve link adaptation of the downlink control channel. For example, in the case of AL=L, one downlink control channel can be transmitted using L CCEs.

[0236] The UE needs to detect signals without information about the downlink control channels, therefore a search space can be defined to indicate the set of CCEs for blind decoding. The search space can be a set of downlink control channel candidates that the UE must attempt to decode at a given aggregation level. Since there are various aggregation levels that group 1, 2, 4, 8, or 16 CCEs into a bundle, the UE can have multiple search spaces. The search space set can be defined as the set of search spaces under all configured aggregation levels.

[0237] The search space can be categorized into a common search space and a UE-specific search space. A UE group or all UEs can search the common search space of the PDCCH to receive cell common control information, such as dynamic scheduling related to system information or paging messages. For example, searching the common search space of the PDCCH can be used to receive PDSCH scheduling allocation information for transmitting SIBs, including cell operator information. In the case of the common search space, the UE group or all UEs need to receive the PDCCH; therefore, the common search space can be defined as a predefined set of CCEs. Searching the UE-specific search space of the PDCCH can be used to receive scheduling allocation information related to UE-specific PDSCHs or PUSCHs. UE-specific search spaces can be defined in a UE-specific manner based on functions of various system parameters and the UE's identifier.

[0238] In 5G, base stations can configure search space parameters related to PDCCH for the UE via upper-layer signaling (e.g., SIB, MIB, or RRC signaling). For example, the base station can provide the UE with the following configurations: the number of PDCCH candidates under each aggregation level L; the monitoring period related to the search space; the monitoring timing related to each symbol in the time slot of the search space; the search space type (public search space or UE-specific search space); the combination of RNTI and DCI formats to be monitored in the corresponding search space; the control resource set index used for monitoring the search space; and so on. For example, the parameters for the search space of PDCCH may include the following information given in Table i.

[0239] [Table i]

[0240]

[0241] The English translations in the table above are as follows: Sequence: a sequence

[0242] Identity of the search space:

[0243] 0 identifies the searchspace: 0 identifies the search space.

[0244] Configured via PBCH (MIB) or servingCellconfigcommon: via PBCH (MIB) or servingCellconfigcommon configuration

[0245] Choice: Select

[0246] Null: Empty value

[0247] Integer: Integer

[0248] Optional: optional

[0249] Duration: Duration

[0250] Bit string: Bit string

[0251] Enumerated: the enumerated set

[0252] Configures this search space as common search space (CSS) and DCIformats to monitor: Configure the search space as a common search space (CSS) and the DCI formats to be monitored.

[0253] UE-specific: UE-specific

[0254] Indicates whether the UE monitors in this USS for DCI formats 0-0and 1-0 or formats 0-1 and 1-1: Indicates whether the UE is monitoring DCI formats 0-0 and 1-0 or format 0-1 in this USS. and 1-1

[0255] Formats:

[0256] Based on the configuration information, the base station can configure one or more search space sets for the UE. According to some embodiments, the base station can configure search space set 1 and search space set 2 for the UE. The base station can configure search space set 1 for the UE to monitor DCI format A scrambled by X-RNTI in a common search space, and can configure search space set 2 for the UE to monitor DCI format B scrambled by Y-RNTI in a UE-specific search space.

[0257] Depending on the configuration information, one or more search space sets can exist in a public search space or a UE-specific search space. For example, search space set #1 and search space set #2 can be configured as a public search space, and search space set #3 and search space set #4 can be configured as UE-specific search spaces.

[0258] The following combinations of DCI formats and RNTI can be monitored in the public search space, but these are merely examples, and this disclosure is not limited to these examples.

[0259] DCI format 0_0 / 1_0 with CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI, RA-RNTI, TC-RNTI, P-RNTI, and SI-RNTI.

[0260] DCI format 2_0 with CRC scrambled by SFI-RNTI

[0261] DCI format 2_1 with CRC scrambled by INT-RNTI

[0262] DCI format 2_2 with CRC scrambled by TPC-PUSCH-RNTI and TPC-PUCCH-RNTI

[0263] DCI format 2_3 with CRC scrambled by TPC-SRS-RNTI

[0264] The following combinations of DCI formats and RNTI can be monitored in a UE-specific search space, but these are merely examples, and this disclosure is not limited to these examples.

[0265] DCI format 0_0 / 1_0 with CRC scrambled by C-RNTI, CS-RNTI, and TC-RNTI

[0266] It has a CRC DCI format 1_0 / 1_1 scrambled by C-RNTI, CS-RNTI, and TC-RNTI.

[0267] The listed RNTIs can be followed according to the definitions and uses given below.

[0268] Cell RNTI (C-RNTI): Used for scheduling UE-specific PDSCH

[0269] Temporary Cell RNTI (TC-RNTI): Used for scheduling UE-specific PDSCH

[0270] Configured Scheduling RNTI (CS-RNTI): Used to schedule UE-specific PDSCHs with semi-static configuration.

[0271] Random Access RNTI (RA-RNTI): Used to schedule PDSCH during the random access step.

[0272] Paging RNTI (P-RNTI): Used to schedule the PDSCH for sending paging requests.

[0273] System Information RNTI (SI-RNTI): Used to schedule the transmission of system information via PDSCH.

[0274] Interrupt RNTI (INT-RNTI): Used to indicate whether the PDSCH has been punched.

[0275] Transmit Power Control RNTI for PUSCH (TPC-PUSCH-RNTI): Used to indicate power control commands related to PUSCH.

[0276] Transmit Power Control RNTI for PUCCH (TPC-PUCCH-RNTI): Used to indicate power control commands related to PUCCH.

[0277] Transmit Power Control RNTI for SRS (TPC-SRS-RNTI): Used to indicate power control commands related to SRS.

[0278] The DCI formats listed above can, for example, follow the definitions given in Table j below.

[0279] [Table j]

[0280] In 5G, the search space under the aggregation level L associated with the control resource set p and the search space set s can be represented by the following Equation 1.

[0281] [Equation 1]

[0282] - L: Aggregation Level

[0283] - n CI Carrier index

[0284] - N CCE,p : The total number of CCEs existing in the control resource set p

[0285] - n (s,f) μ Time slot index

[0286] - M s,max (L) Number of PDCCH candidates under aggregation level L

[0287] - PDCCH candidate indexes under aggregation level L

[0288] - i = 0, ..., L -1

[0289] - , , , , ,

[0290] - n RNTI UE identifier

[0291] In the context of a public search space, the The value can correspond to 0.

[0292] In the case of a UE-specific search space, the The value can correspond to a value that changes based on the UE's identifier (C-RNTI or the ID configured by the base station for the UE) and time index.

[0293] In 5G, multiple search space sets can be configured with different parameters (e.g., the parameters in Table i), and the groups of search space sets monitored by the UE at each time point can be different accordingly. For example, if search space set #1 is configured for time slot X and search space set #2 is configured for time slot Y, and X and Y are different, then the UE can monitor search space set #1 and search space set #2 simultaneously in a specific time slot, and can monitor one of search space set #1 and search space set #2 in another specific time slot.

[0294] Figure 6 An example of a method for a base station and a UE to transmit / receive data in a wireless communication system according to embodiments of the present disclosure, taking into account downlink data channel and rate matching resources.

[0295] Reference Figure 6 , Figure 6The diagram illustrates a downlink data channel (PDSCH) 601 and rate matching resources 602. The base station can configure one or more rate matching resources 602 for the UE via upper-layer signaling (e.g., RRC signaling). The configuration information for rate matching resources 602 may include time-domain resource allocation information 603, frequency-domain resource allocation information 604, and periodicity information 605. In the following text, the bitmap corresponding to the frequency-domain resource allocation information 604 will be referred to as the "first bitmap," the bitmap corresponding to the time-domain resource allocation information 603 will be referred to as the "second bitmap," and the bitmap corresponding to the periodicity information 605 will be referred to as the "third bitmap." If all or some of the time and frequency resources of the scheduled PDSCH 601 overlap with the configured rate matching resources 602, the base station can rate match PDSCH 602 within the rate matching resource 601 portion and transmit PDSCH 602, and the UE can perform reception and decoding after assuming that PDSCH 602 has been rate matched within the rate matching resource 601 portion.

[0296] The base station can dynamically notify the UE via DCI, through additional configuration (e.g., corresponding to the "rate matching indicator" in the DCI format described above), whether rate matching will be performed on the PDSCH in the configured rate matching resource portion. Specifically, the base station can select some rate matching resources from the configured rate matching resources and group the selected rate matching resources into rate matching resource groups. The base station can use a bitmap scheme in the DCI to indicate to the UE whether the data channel is rate matched to the corresponding rate matching group. For example, if four rate matching resources RMR#1, RMR#2, RMR#3, and RMR#4 are configured, the base station can configure rate matching groups RMG#1={RMR#1, RMR#2} and RMG#2={RMR#3, RMR#4}, and can use two bits in the DCI field to indicate to the UE, respectively, via a bitmap whether rate matching has occurred in RMG#1 and RMG#2. For example, if rate matching is to be performed, the base station can indicate this with "1"; and if rate matching is not performed, the base station can indicate this with "0".

[0297] As a method for configuring the aforementioned rate matching resources for the UE, 5G supports both "RB symbol level" and "RE level" granularity. More specifically, the following configuration methods can be used.

[0298] RB symbol level

[0299] The UE has up to four rate match patterns that can be configured for each bandwidth segment via upper-layer signaling, and a rate match pattern can include the following. Obviously, the examples given below are not limiting.

[0300] - This may include resources associated with reserved resources within a bandwidth portion (BWP), where the time and frequency domains of the corresponding reserved resource are configured as a combination of an RB-level bitmap and a symbol-level bitmap in the frequency domain. The reserved resource may span one or more time slots (e.g., it may span one or two time slots). A periodicity pattern can also be configured, where the time and frequency domains, including the corresponding RB-level and symbol-level bitmap pairs, are repeated.

[0301] - It may include resource regions corresponding to the following time-domain pattern: the time-domain pattern is configured by the time-domain and frequency-domain resource regions configured by the CORESET within the bandwidth portion and the search space configuration in which the corresponding resource regions are repeated.

[0302] RE Level

[0303] The UE can have the following features configured via upper-layer signaling. Clearly, the examples given below are not limiting.

[0304] - Configuration information (lte-CRS-ToMatchAround) related to the RE corresponding to the LTE CRS (Cell-Specific Reference Signal or Common Reference Signal) pattern. This information may include the number of LTE CRS ports (nrofCRS-Ports) and the LTE-CRS-vshift(s) value (v-shift), the position information of the center subcarrier of the LTE carrier relative to the reference frequency point (e.g., reference point A) (carrierFreqDL), the bandwidth of the LTE carrier (carrierBandwidthDL), and the subframe configuration information (mbsfn-SubframConfigList) corresponding to the Multicast-Broadcast Single Frequency Network (MBSFN). The UE can determine the position of the CRS within the NR slot corresponding to the LTE subframe based on the above information.

[0305] - It may include configuration information related to the resource set corresponding to one or more zero-power (ZP) CSI-RS within the bandwidth portion.

[0306] [PDSCH: Regarding Frequency Resource Allocation]

[0307] Figure 7 An example of frequency domain resource allocation for a Physical Downlink Shared Channel (PDSCH) in a wireless communication system according to an embodiment of the present disclosure is shown.

[0308] Figure 7Three frequency domain resource allocation methods are shown, which can be configured by the upper layer in the NR wireless communication system: resource allocation type-0 700, type-1 705, and dynamic switching 710.

[0309] Reference Figure 7 If the UE is configured to use only resource allocation type -0 (700) via upper-layer signaling, then the portion of downlink control information (DCI) used to schedule PDSCH or PUSCH for the UE includes N RBG A bitmap configured with N bits. As used in this article, N RBG It can refer to the number of resource block groups (RBGs) determined according to the size of the bandwidth portion indicated by the bandwidth portion indicator and the upper-layer parameter rbg-Size, as shown in Table k below, and data can be sent in the RBG marked as 1 by the bitmap.

[0310] [Table k]

[0311] If the UE is configured to use only resource allocation type 1 (705) via upper-layer signaling, the DCI used to allocate PDSCH or PUSCH to the UE includes... Frequency domain resource allocation (FDRA) information consists of the same number of bits. Thus, the base station can configure the starting VRB 720 and the length 725 of the frequency domain resources continuously allocated from it.

[0312] If the UE is configured to use both resource allocation type -0 and resource allocation type -1 (710) via upper-layer signaling, the portion of the DCI used to allocate the PDSCH to the corresponding UE includes frequency domain resource allocation information. This frequency domain resource allocation information includes the same number of bits as the larger of the payload 715 used to configure resource allocation type -0 and the payloads 720 and 725 used to configure resource allocation type 1, which is 735. Its conditions will be described again later. A bit can be added to the beginning (MSB) of the frequency domain resource allocation information within the DCI, and if the value of this bit is "0", it indicates the use of resource type -0; and if the value of this bit is "1", it indicates the use of resource type -1.

[0313] [PDSCH / PUSCH: Regarding Time Resource Allocation]

[0314] The following section describes the time-domain resource allocation method for data channels in next-generation mobile communication systems (5G or NR systems).

[0315] The base station can configure time-domain resource allocation information tables related to the Physical Downlink Shared Channel (PDSCH) and Physical Uplink Shared Channel (PUSCH) for the UE via upper-layer signaling (e.g., RRC signaling). A table with a maximum of maxNrofDL-Allocations=16 entries can be configured for the PDSCH, and a table with a maximum of maxNrofUL-Allocations=16 entries can be configured for the PUSCH. In an embodiment, time-domain resource allocation information may include PDCCH to PDSCH time slot timing (e.g., the time interval in units of time slots corresponding to the time point between receiving the PDCCH and sending the PDSCH scheduled by the received PDCCH; denoted as K0), PDCCH to PUSCH time slot timing (e.g., the time interval in units of time slots corresponding to the time point between receiving the PDCCH and sending the PUSCH scheduled by the received PDCCH; denoted as K2 hereinafter), information related to the position and length of the starting symbol on which the PDSCH or PUSCH is scheduled within a time slot, the mapping type of the PDSCH or PUSCH, etc. For example, the information in Table 1 or Table m below can be sent from the base station to the UE.

[0316] [Table 1]

[0317] The English translations in the table above are as follows: PDSCH-TimeDomainResourceAllocationList information element PDSCH-Time domain Resource allocation list information elements

[0318] Sequence: a sequence

[0319] Integer: Integer

[0320] Optional: optional

[0321] Need: required

[0322] [Table m]

[0323] The English translations in the table above are as follows: PUSCH-TimeDomainResourceAllocationList information element PUSCH-Time domain Resource allocation list information elements

[0324] Sequence: a sequence

[0325] Integer: Integer

[0326] Optional: optional

[0327] Enumerated: Enumeration

[0328] Need: required

[0329] The base station can notify the UE of one of the entries in the aforementioned time-domain resource allocation information table via L1 signaling (e.g., DCI) (e.g., indicated by the "Time Domain Resource Allocation" field in the DCI). The UE can obtain time-domain resource allocation information related to PDSCH or PUSCH based on the DCI obtained from the base station.

[0330] Figure 8 An example of time-domain resource allocation for a PDSCH in a wireless communication system according to an embodiment of the present disclosure is shown.

[0331] Reference Figure 8 The base station can determine the subcarrier spacing (SCS) (μ) of the data and control channels configured through higher layers. PDSCH μ PDCCH The time-domain location of the PDSCH resource is indicated by the scheduling offset (K0) value and the OFDM symbol start position 1000 and length 1005 within a time slot dynamically indicated by DCI.

[0332] Figure 9 An example of time-domain resource allocation of data channels and control channels according to subcarrier spacing is shown in a wireless communication system according to an embodiment of the present disclosure.

[0333] Reference Figure 9 If the data channel and control channel have the same subcarrier spacing (900, μPDSCH=μPDCCH), then the data slot number is the same as the control slot number, and the base station and UE can generate a scheduling offset accordingly according to the predetermined slot offset K0. On the other hand, if the data channel and control channel have different subcarrier spacings (905, μPDSCH=μPDCCH), then the data slot number is the same as the control slot number, and the base station and UE can generate a scheduling offset accordingly according to the predetermined slot offset K0. PDSCH ≠μ PDCCH If the data slot number is different from the control slot number, the base station and UE can generate a scheduling offset based on the subcarrier spacing of the PDCCH according to the predetermined slot offset K0.

[0334] [PUSCH: Regarding the transmission scheme]

[0335] The PUSCH transmission scheduling scheme will be described below. PUSCH transmissions can be dynamically scheduled by UL authorization within the DCI, or operated by configuring authorization type 1 or type 2. Dynamic scheduling instructions related to PUSCH transmissions can be made via DCI format 0_0 or 0_1.

[0336] Configuration grant type 1 PUSCH transmissions can be semi-statically configured by receiving a configuredGrantConfig from table n that includes rrc-ConfiguredUplinkGrant via upper-layer signaling, without receiving UL grants within the DCI. Configuration grant type 2 PUSCH transmissions can be semi-persistently scheduled by UL grants within the DCI after receiving a configuredGrantConfig from table n that does not include rrc-ConfiguredUplinkGrant via upper-layer signaling. If PUSCH transmissions are performed via configuration granting, the parameters applied to the PUSCH transmissions are applied via the configuredGrantConfig (upper-layer signaling) in table n, except for dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, and UCI-OnPUSCH scaling provided by push-Config (upper-layer signaling) in table o. If transformPrecoder is provided within the configuredGrantConfig (upper-layer signaling) in table n, the UE applies tp-pi2BPSK from push-Config in table o to PUSCH transmissions performed via configuration granting.

[0337] [Table n]

[0338]

[0339] The English translations in the table above are as follows: Sequence: a sequence

[0340] Enumerated: Enumeration

[0341] Optional: optional

[0342] Need: required

[0343] Integer: Integer

[0344] Periodicity: periodicity

[0345] The PUSCH transmission method will be described below. The DMRS antenna port used for PUSCH transmission is the same as the antenna port used for SRS transmission. Depending on whether the value of txConfig in pusch-Config in table o, which serves as upper-layer signaling, is "codebook" or "nonCodebook", PUSCH transmission can follow a codebook-based transmission method or a non-codebook-based transmission method.

[0346] As described above, PUSCH transmissions can be dynamically scheduled via DCI format 0_0 or 0_1, and can be configured semi-statically via configuration authorization. Upon receiving a scheduling instruction related to PUSCH transmission via DCI format 0_0, the UE can perform beam configuration for PUSCH transmission using the pucch-spatialRelationInfoID corresponding to the UE-specific PUCCH resource with the smallest ID within the active uplink BWP in the serving cell. PUSCH transmissions can be based on a single antenna port. The UE may not expect PUSCH transmissions to be scheduled via DCI format 0_0 within a BWP that does not have a configured PUCCH resource including pucch-spatialRelationInfo. If the UE does not have a configured txConfig in pusch-Config in Table o, the UE may not expect scheduling via DCI format 0_1.

[0347] [Table o]

[0348]

[0349] The English translations in the table above are as follows: Sequence: a sequence

[0350] Integer: Integer

[0351] Optional: optional

[0352] Enumerated: Enumeration

[0353] Need: required

[0354] Enabled: Enabled

[0355] The codebook-based PUSCH transmission will be described below. Codebook-based PUSCH transmission can be dynamically scheduled using DCI format 0_0 or 0_1, and can be operated semi-statically using configuration authorization. If codebook-based PUSCH is dynamically scheduled using DCI format 0_1, or configured semi-statically using configuration authorization, the UE determines the precoder used for PUSCH transmission based on the SRS Resource Indicator (SRI), the Transmit Precoding Matrix Indicator (TPMI), and the transmission rank (the number of PUSCH transport layers).

[0356] SRIs can be indicated via SRS resource indicators (fields within the DCI) or configured via srs-ResourceIndicator (upper-layer signaling). When transmitting codebook-based PUSCH, at least one SRS resource can be configured for the UE, and up to two SRS resources can be configured for the UE. If an SRI is provided to the UE via the DCI, the SRS resource indicated by the corresponding SRI refers to the SRS resource corresponding to that SRI among the SRS resources transmitted prior to the PDCCH including the corresponding SRI. TPMIs and transmission rank can be given via "Precoding Information and Number of Layers" (fields within the DCI) or configured via precodingAndNumberOfLayers (upper-layer signaling). TPMIs can be used to indicate the precoder to be applied to PUSCH transmissions. If one SRS resource is configured for the UE, the TPMI can be used to indicate the precoder to be applied to the configured SRS resource. If multiple SRS resources are configured for the UE, the TPMI is used to indicate the precoder to be applied to the SRS resource indicated by the SRI.

[0357] The precoder used for PUSCH transmission can be selected from an uplink codebook with the same number of antenna ports as the value of nrofSRS-Ports in the SRS-Config (higher-layer signaling). Regarding codebook-based PUSCH transmission, the UE can determine the codebook subset based on the codebookSubset and TPMI in the push-Config (higher-layer signaling). The codebookSubset in the push-Config, as upper-layer signaling, can be configured as one of "fullyAndPartialAndNonCoherent", "partialAndNonCoherent", or "nonCoherent" based on the UE capabilities reported by the UE to the base station. If the UE reports "partialAndNonCoherent" as a UE capability, the UE may not expect to configure the value of codebookSubset (upper-layer signaling) as "fullyAndPartialAndNonCoherent". If the UE reports "nonCoherent" as a UE capability, the UE may not expect to configure the value of codebookSubset (upper-layer signaling) as either "fullyAndPartialAndNonCoherent" or "partialAndNonCoherent". If nrofSRS-Ports in SRS-ResourceSet (upper-layer signaling) indicates two SRS antenna ports, the UE may not expect to configure the value of codebookSubset (upper-layer signaling) to "partialAndNonCoherent".

[0358] - An SRS resource set can be configured for the UE, where the usage value in the SRS-ResourceSet (upper-layer signaling) is "codebook". An SRS resource can be indicated by the SRI in the corresponding SRS resource set. If multiple SRS resources are configured in the SRS resource set with the usage value of "codebook" in the SRS-ResourceSet (upper-layer signaling), the UE expects the value of nrofSRS-Ports in the SRS-Resource (upper-layer signaling) to be the same for all SRS resources.

[0359] The UE can send one or more SRS resources, including those in an SRS resource set whose usage value is configured as "codebook", to the base station based on upper-layer signaling. The base station can select one SRS resource from the SRS resources sent by the UE and instruct the UE to use the transmission beam information of the corresponding SRS resource to transmit PUSCH. Regarding codebook-based PUSCH transmission, the SRI can be used as an index for selecting an SRS resource and can be included in the DCI. Furthermore, the base station can add information indicating the rank and TPMI used by the UE for PUSCH transmission to the DCI. Using the SRS resource indicated by the SRI, the UE can apply a precoder indicated by the rank and TPMI based on the transmission beam of the corresponding SRS resource when performing PUSCH transmission, thereby performing PUSCH transmission.

[0360] The following section describes non-codebook-based PUSCH transport. Non-codebook-based PUSCH transport can be dynamically scheduled using DCI format 0_0 or 0_1, and can also be operated semi-statically with configuration authorization. If at least one SRS resource is configured in the SRS resource set with a usage value of "nonCodebook" in the SRS-ResourceSet (higher-layer signaling), non-codebook-based PUSCH transport can be scheduled for the UE using DCI format 0_1.

[0361] For SRS resource sets with a usage value of "nonCodebook" within the SRS-ResourceSet (upper-layer signaling), a connected NZP CSI-RS resource (non-zero power CSI-RS) can be configured for the UE. The UE can calculate the precoder for SRS transmission by measuring the NZP CSI-RS resource connected to the SRS resource set. If the difference between the last received symbol of the non-periodic NZP CSI-RS resource connected to the SRS resource set and the first symbol of the non-periodic SRS transmission in the UE is less than 42 symbols, the UE does not expect to update information related to the precoder for SRS transmission.

[0362] If the resourceType configuration value in the SRS-ResourceSet (upper-layer signaling) is "aperiodic", the connected NZP CSI-RS can be indicated by the SRS request as a field in DCI format 0_1 ​​or 1_1. If the connected NZP CSI-RS resource is an aperiodic NZP CSI-RS resource, the presence of the connected NZP CSI-RS can be indicated by the value of the SRS request (a field in DCI format 0_1 ​​or 1_1) not being "00". The corresponding DCI may not indicate cross-carrier scheduling or cross-BWP scheduling. If the SRS request value indicates the presence of an NZP CSI-RS, the NZP CSI-RS can be located in the time slot used to transmit the PDCCH including the SRS request field. In this case, the TCI state configured for the scheduled subcarrier may not be configured as QCL-TypeD.

[0363] If a periodic or semi-persistent SRS resource set is configured, the associated CSI-RS within the SRS-ResourceSet (upper-layer signaling) can indicate the connected NZP CSI-RS. Regarding non-codebook-based transmissions, the UE may not expect that the spatialRelationInfo (upper-layer signaling) related to SRS resources and the associated CSI-RS within the SRS-ResourceSet (higher-layer signaling) will be configured together.

[0364] If multiple SRS resources are configured for the UE, the UE can determine the precoder and transmission rank to be applied to PUSCH transmission based on the SRI indicated by the base station. The SRI can be indicated by an SRS resource indicator (a field within the DCI) or configured via the srs-ResourceIndicator (upper-layer signaling). Similar to the codebook-based PUSCH transmission described above, if the SRI is provided to the UE via the DCI, the SRS resource indicated by the corresponding SRI can refer to the SRS resource corresponding to that SRI among those transmitted before the PDCCH including the corresponding SRI. The UE can use one or more SRS resources for SRS transmission. The maximum number of SRS resources that can be transmitted simultaneously within the same symbol in an SRS resource set, and the maximum number of SRS resources, are determined by the UE capabilities reported by the UE to the base station. SRS resources transmitted simultaneously by the UE can occupy the same RB. The UE can configure one SRS port for each SRS resource. You can configure only one SRS resource set (upper-layer signaling) with the usage value of "nonCodebook", and you can configure up to four SRS resources for non-codebook-based PUSCH transports.

[0365] The base station can send an NZP-CSI-RS connected to an SRS resource set to the UE. The UE can calculate the precoder to use when sending one or more SRS resources within the corresponding SRS resource set based on the measurement results received when the corresponding NZP-CSI-RS is received. The UE can apply the calculated precoder when sending one or more SRS resources within an SRS resource set configured with usage "nonCodebook" to the base station. The base station can select one or more SRS resources from the received one or more SRS resources. Regarding non-codebook-based PUSCH transmission, the SRI can indicate an index that can represent one SRS resource or a combination of multiple SRS resources. The SRI can be included in the DCI. The number of SRS resources indicated by the SRI sent by the base station can be the number of transport layers of the PUSCH. The UE can send PUSCH by applying the precoder used for SRS resource transmission to each layer.

[0366] [About CA / DC]

[0367] Figure 10 Radio protocol structures for base stations and UEs in single-cell, carrier aggregation, and dual connectivity scenarios according to embodiments of this disclosure are shown.

[0368] Reference Figure 10The radio protocols of the next-generation mobile communication system include NR Service Data Adaptation Protocol (SDAP) 1025 or 1070, NR Packet Data Convergence Protocol (PDCP) 1030 or 1065, NR Radio Link Control (RLC) 1035 or 1060 and NR Media Access Control (MAC) 1040 or 1055 on each side, on the UE side and the NR base station side.

[0369] The main functions of NR SDAP 1025 or 1070 may include some of the following functions.

[0370] - Transfer of user plane data

[0371] - For both UL and DL, the mapping between QoS flows and DRB

[0372] - Mark QoS flow IDs in both DL and UL groups

[0373] - Reflective QoS flow to DRB mapping for UL SDAP PDU

[0374] Regarding SDAP layer devices, the UE can be configured via RRC messages to use either the SDAP layer device header or its functionality, depending on the PDCP layer device, the bearer, or the logical channel. If an SDAP header is configured, the 1-bit Non-Access Stratum (NAS) Quality of Service (QoS) Reflective Configuration Indicator and the 1-bit Access Stratum (AS) QoS Reflective Configuration Indicator in the SDAP header can instruct the UE to update or reconfigure mapping information related to uplink and downlink QoS flows and data bearers. The SDAP header may include QoS flow ID information indicating QoS. QoS information can be used for data processing priority, scheduling information, etc., to smoothly support service.

[0375] The main functions of NR PDCP 1030 or 1065 may include some of the following: - Header compression and decompression: Robust header compression only (ROHC) - Transfer of user data - Ordered delivery of upper-layer PDUs - Out-of-order delivery of upper-layer PDUs - PDCP PDU reordering for received PDUs - Duplicate detection of lower-level SDUs - PDCP SDU retransmission - Encryption and decryption - Timer-based SDU dropping in the uplink Referring to the functions described above, reordering in an NR PDCP device can refer to the function of reordering PDCP PDUs received from the lower layer in sequence based on the PDCP sequence number (SN). The reordering may include the function of transmitting data to the upper layer according to the reordered sequence. Reordering in an NR PDCP device may include the function of transmitting data immediately regardless of order, and may include the function of recording PDCP PDUs lost due to reordering. The reordering may include the function of reporting the status of lost PDCP PDUs to the transmitting side, and may include the function of requesting retransmission of lost PDCP PDUs.

[0376] The main functions of the NR RLC 1035 or 1060 may include some of the following: - Transfer of upper-layer PDUs - Ordered delivery of upper-layer PDUs - Out-of-order delivery of upper-layer PDUs - ARQ function (error correction via ARQ) - Cascading, segmentation, and reassembly of RLC SDUs - Resegmentation of RLC data PDUs - Reordering of RLC data PDUs - Duplicate Detection - Protocol error detection - RLC SDU discard - RLC Reconstruction The sequential delivery of NR RLC devices can refer to the function of sequentially delivering RLC SDUs received from lower layers to upper layers. Sequential delivery of NR RLC devices may include the following functions: if an original RLC SDU is segmented into multiple RLCSDUs and the segmented RLC SDUs are received, then the RLC SDUs are reassembled and the reassembled RLC SDUs are delivered. Sequential delivery of NR RLC devices may include the function of reordering received RLC PDUs with reference to the RLC sequence number (SN) or PDCP sequence number (SN), and the function of recording RLC PDUs lost due to reordering. Sequential delivery of NR RLC devices may include the function of reporting the status of lost RLC PDUs to the transmitting side, and may include the function of requesting retransmission of lost RLC PDUs. The sequential delivery function of NR RLC devices may include the following function: if there are lost RLC SDUs, then only the RLC SDUs preceding the lost RLC SDU are sequentially delivered to the upper layer. The in-order delivery function of an NR RLC device may include the following functionality: if a scheduled timer has expired despite the existence of a lost RLC SDU, all RLC SDUs received before the timer started are delivered sequentially to the upper layer. Alternatively, the in-order delivery function of an NR RLC device may include the following functionality: if a scheduled timer has expired despite the existence of a lost RLC SDU, all RLC SDUs received up to that time are delivered sequentially to the upper layer. Furthermore, the in-order delivery function of an NR RLC device may process RLC PDUs in the order of receipt (arrival order regardless of sequence number order) and deliver them to the PDCP device regardless of the order (out-of-order delivery). In the case of segmentation, the in-order delivery function of an NR RLC device may receive segments stored in a buffer or to be received later, reconfigure them into a complete RLC PDU, process the complete RLC PDU, and deliver it to the PDCP device. The NR RLC layer may not include a cascading function, which may be performed in the NR MAC layer or replaced by a multiplexing function of the NR MAC layer.

[0377] The out-of-order delivery of the aforementioned NR RLC device can refer to the function of directly delivering RLC SDUs received from the lower layer to the upper layer regardless of the order. Out-of-order delivery of the NR RLC device may include the function of reassembling and delivering multiple received RLC SDUs, where one original RLC SDU has been segmented into the multiple RLC SDUs; and may include the function of storing the RLC SN or PDCP SN of the received RLCPDUs and recording RLC PDUs lost due to reordering.

[0378] The NR MAC 1040 or 1055 can connect to multiple NR RLC layer devices configured in a single UE, and the main functions of the NR MAC can include some of the following features.

[0379] - Mapping between logical channels and transport channels

[0380] - MAC SDU multiplexing / demultiplexing

[0381] - Scheduling Information Report

[0382] - Error correction via HARQ

[0383] Priority handling between logical channels of a UE

[0384] - Prioritize UEs through dynamic scheduling

[0385] - MBMS service identification

[0386] - Transmission format selection

[0387] - Fill

[0388] The NR PHY layer 1045 or 1050 can perform channel coding and modulation operations on upper-layer data to obtain OFDM symbols, and then transmit the OFDM symbols via a radio channel. The NR PHY layer can also perform demodulation, channel decoding, and transmission of OFDM symbols received via the radio channel to the upper layer.

[0389] The detailed structure of the radio protocol architecture can be varied in various ways depending on the carrier (or cell) operation scheme. According to an embodiment, when the base station transmits data to the UE based on a single carrier (or cell), the base station and the UE can use a protocol architecture with a single structure for each layer (1010). When the base station transmits data to the UE based on carrier aggregation (CA) using multiple carriers in a single TRP, the base station and the UE can use a protocol architecture with a single structure up to the RLC, but multiplexing the PHY layer through the MAC layer (1020). According to another embodiment, when the base station transmits data to the UE based on carrier aggregation (CA) using multiple carriers in a single TRP, the base station and the UE can use a protocol architecture with a single structure up to the RLC, but multiplexing the PHY layer through the MAC layer (1030).

[0390] Referring to the above description related to PDCCH and beam configuration, since current Rel-15 and Rel-16 NR do not support PDCCH retransmission, it is difficult to achieve the required reliability in scenarios requiring high reliability, such as URLLC. This disclosure can improve the PDCCH reception reliability of the UE by providing a PDCCH retransmission method via multiple transmission points (TRPs). Specific methods will be described below through the following embodiments.

[0391] In the following, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The content of this disclosure can be applied to frequency division duplex (FDD) systems and time division duplex (TDD) systems. As used herein, upper-layer signaling (or upper-layer signaling) is a method of transmitting signals from a base station to a UE using downlink data channels of the physical layer, or transmitting signals from a UE to a base station using uplink data channels of the physical layer, and may also be referred to as "RRC signaling," "PDCP signaling," or "MAC control element (MAC CE)."

[0392] In the following, within this disclosure, the UE may use various methods to determine whether cooperative communication is applied. For example, the PDCCH to which cooperative communication is applied has a specific format, or the PDCCH to which cooperative communication is applied includes a specific indicator indicating whether cooperative communication is applied, or the PDCCH to which cooperative communication is applied is scrambled by a specific RNTI, or cooperative communication is assumed to be applied within a specific range indicated by the upper layer. In the following, for ease of description, it will be assumed that the NC-JT case refers to the case where the UE receives a PDSCH to which cooperative communication is applied under conditions similar to those described above.

[0393] The determination of priority between A and B as used below can refer to various operations, such as selecting the one with higher priority according to a predetermined priority rule and executing the operation corresponding to the selected one, as well as omitting or discarding the operation corresponding to the one with lower priority.

[0394] The above examples can be described below through several embodiments, but these embodiments are not independent of each other, and one or more embodiments can be applied simultaneously or in combination.

[0395] In the following, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The base station used herein is an entity that allocates resources to terminals and may be at least one of a gNode B, gNB, eNode B, Node B, base station (BS), radio access unit, base station controller, or node on a network. Terminals may include user equipment (UE), mobile station (MS), cellular phone, smartphone, computer, or multimedia system capable of performing communication functions. In the following description of embodiments of the present disclosure, a 5G system will be used as an example, but embodiments of the present disclosure can also be applied to other communication systems with similar technical backgrounds or channel types. Examples of such communication systems may include LTE or LTE-A mobile communication systems and mobile communication technologies developed after 5G. Therefore, based on the judgment of those skilled in the art, embodiments of the present disclosure can also be applied to other communication systems with some modifications without departing from the scope of the present disclosure. The details of this disclosure apply to both FDD and TDD systems.

[0396] Furthermore, detailed descriptions of related functions or configurations will be omitted when it is determined that such descriptions may unnecessarily obscure the main points of this disclosure. The terms used below are defined in consideration of their function in this disclosure and may vary depending on the intent or customary practice of the user or operator. Therefore, these terms should be interpreted in light of the entirety of this specification.

[0397] In the following description of this disclosure, the term "higher-level signaling" may include at least one or any combination of the following types of signaling.

[0398] - Master Message Block (MIB)

[0399] - System Information Block (SIB) or SIB X (X=1, 2, ...)

[0400] - Radio Resource Control (RRC)

[0401] - Media Access Control (MAC) Control Element (CE)

[0402] In addition, L1 signaling can refer to signaling corresponding to at least one signaling method or a combination of one or more of the following physical layer channels or signaling methods.

[0403] - Physical Downlink Control Channel (PDCCH)

[0404] Downlink Control Information (DCI)

[0405] - UE-specific DCI

[0406] - Group Public DCI

[0407] - Public DCI

[0408] - Scheduling DCI (e.g., DCI used to schedule downlink or uplink data)

[0409] - Non-scheduled DCI (e.g., DCI not used for scheduling downlink or uplink data)

[0410] - Physical Uplink Control Channel (PUCCH)

[0411] - Uplink Control Information (UCI)

[0412] The determination of priority between A and B as used below can refer to various operations, such as selecting the one with higher priority according to a predetermined priority rule and executing the operation corresponding to the selected one, as well as omitting or discarding the operation corresponding to the one with lower priority.

[0413] The above examples can be described below through several embodiments, but these embodiments are not independent of each other, and one or more embodiments can be applied simultaneously or in combination.

[0414] [Random Access Procedure in SBFD]

[0415] In 3GPP, Subband Non-overlapping Full-Duplex (SBFD) has been continuously discussed as a new duplexing scheme based on NR. SBFD refers to the technique of using a portion of downlink resources as uplink resources in the TDD spectrum at 6 GHz or lower, or 6 GHz or higher, so that the UE receives uplink transmissions corresponding to the increased uplink resources, thereby extending the UE's uplink coverage and receiving feedback from the UE regarding downlink transmissions in the extended uplink resources, thereby reducing feedback latency. For ease of description, as used herein, a UE that can receive information from the base station regarding whether it supports SBFD and can perform uplink transmissions in a portion of downlink resources can be referred to as an SBFD-supporting UE. To define SBFD schemes in the specification and determine which SBFD-supporting UEs support SBFD in a specific cell (or frequency / band), the following schemes can be considered: In the first scheme, in addition to the existing frame structure types for unpaired spectrum (or Time Division Duplex (TDD)) or paired spectrum (or Frequency Division Duplex (FDD)), a different frame structure type (e.g., frame structure type 2) can be introduced to define the aforementioned SBFD. This can be defined as supporting frame structure type 2 at a specific frequency or band. Alternatively, the base station can indicate to the UE whether SBFD is supported via system information. A UE supporting SBFD can receive the system information indicating whether SBFD is supported, and thereby determine whether SBFD is supported in a specific cell (or frequency / band).

[0416] - In the second scheme, without defining a new frame structure type, it can be indicated whether SBFD is additionally supported at a specific frequency or band of the existing unpaired spectrum (or TDD). According to the second scheme, it can be defined whether SBFD is additionally supported at a specific frequency or band of the existing unpaired spectrum, or the base station can indicate to the UE whether SBFD is supported via system information. A UE supporting SBFD can receive system information indicating whether SBFD is supported, and thereby determine whether SBFD is supported in a specific cell (or frequency / band).

[0417] In addition to the configuration related to the TDD uplink (UL)-downlink (DL) resource configuration information indicating the downlink slot (or symbol) resources and uplink slot (or symbol) resources of TDD, the information indicating whether SBFD is supported in the first and second schemes described above may also include configuring a portion of the downlink resources as uplink resources (e.g., see later). Figure 12 A to Figure 12 The information described in D (SBFD resource configuration information) can be used to indirectly indicate whether SBFD is supported, or it can include information that directly indicates whether SBFD is supported.

[0418] In this disclosure, a UE supporting SBFD can obtain cell synchronization by receiving a synchronization signal block during the initial cell access phase for accessing a cell (or base station). The process of obtaining cell synchronization can be applied equally to SBFD-enabled UEs and existing TDD terminals. Subsequently, the SBFD-enabled UE can determine whether the cell supports SBFD through obtaining the MIB, obtaining the SIB, or a random access procedure.

[0419] According to an embodiment, the system information used to transmit information related to whether SBFD is supported can be distinguished from the system information used to support different specification versions of UEs in the cell (e.g., existing TDD UEs) and transmitted separately. A UE supporting SBFD can obtain all or part of the system information transmitted separately from the system information used for existing TDD UEs, thereby determining whether it supports SBFD. If a UE supporting SBFD only obtains the system information used for existing TDD UEs, or if a UE supporting SBFD obtains system information indicating that SBFD is not supported, the UE supporting SBFD can determine that the cell (or base station) only supports TDD.

[0420] According to an embodiment, if information related to whether SBFD is supported is included in the system information for UEs supporting different specification versions (e.g., existing TDD UEs), the information related to whether SBFD is supported can be inserted at the end to avoid affecting the existing TDD UE's access to the system information. If a UE supporting SBFD fails to obtain the information related to whether SBFD is supported inserted at the end, or if a UE supporting SBFD obtains information indicating that SBFD is not supported, the UE supporting SBFD can determine that the cell (or base station) only supports TDD.

[0421] According to an embodiment, when information related to whether SBFD is supported is included in the system information for UEs supporting different specification versions (e.g., existing TDD UEs), the information related to whether SBFD is supported can be transmitted via a separate PDSCH to avoid affecting the existing TDD UE's access to system information. For example, a UE that does not support SBFD can receive a first SIB (or SIB1) including existing TDD-related system information in the first PDSCH. A UE that supports SBFD can receive a first SIB (or SIB) including traditional TDD-related system information via the first PDSCH, and can receive a second SIB including SBFD-related system information via the second PDSCH. The first PDSCH and the second PDSCH can be scheduled by the first PDCCH and the second PDCCH, and the cyclic redundancy code (CRC) of the first PDCCH and the second PDCCH can be scrambled by the same RNTI (e.g., SI-RNTI). The search space for monitoring the second PDCCH can be obtained from the system information of the first PDCCH, and if the search space is not obtained (e.g., if the system information of the first PDCCH does not include information related to the search space), the second PDCCH can be received in the same search space as the first PDCCH.

[0422] If a UE supporting SBFD determines, as described above, that the cell (or base station) only supports TDD, the UE supporting SBFD can perform the same random access procedure and data / control signal transmission / reception as an existing TDD UE.

[0423] According to various embodiments, the base station can configure separate random access resources for each of the existing TDD UEs or SBFD-enabled UEs (e.g., including both SBFD-enabled UEs supporting full-duplex communication and SBFD-enabled UEs supporting half-duplex communication), and can send configuration information related to random access resources (indicating configuration information or control information for time-frequency resources that can be used for PRACH) to SBFD-enabled UEs via system information. The system information used to send information related to random access resources may include system information that is distinguished from and sent separately from system information for UEs supporting different specification versions in the cell (e.g., existing TDD UEs).

[0424] According to various embodiments of this disclosure, a base station can configure random access resources for a TDD UE and can additionally configure separate random access resources for a SBFD-enabled UE. A SBFD-enabled UE may be able to use the random access resources for a TDD UE, or it may not be able to use the random access resources for a TDD UE. In the latter case, the SBFD UE may always use only the separate random access resources for the SBFD UE.

[0425] According to an embodiment, a UE supporting SBFD can receive from a base station an indication regarding the availability of random access resources for a TDD UE. This indication can be included in and received by the SIB. For example, the SIB can configure separate random access resources for the SBFD-supporting UE and can indicate the availability of random access resources for the TDD UE along with this configuration. This indication can be made using a single bit of information. According to an embodiment, if the single bit of information is "0" (or FALSE), the SBFD-supporting UE may not use the random access resources for the TDD UE; or, if the single bit of information is "1" (or TRUE), the SBFD-supporting UE may use the random access resources for the TDD UE. This is merely an example according to various embodiments, and obviously, the opposite situation may also be included.

[0426] According to an embodiment, the base station can determine the type of UE attempting to access the cell based on the random access resources used by the UE. For example, a UE supporting SBFD can transmit a PRACH through a separate random access resource for SBFD-supporting UEs. The base station can receive the PRACH transmitted by the SBFD-supporting UE and determine that the SBFD-supporting UE is attempting cell access. For example, if a TDD UE transmits a PRACH through random access resources for TDD UEs, the base station can receive the PRACH and determine that the TDD UE is attempting cell access. When SBFD-supporting UEs are allowed to transmit PRACH through random access resources for TDD UEs, the base station may not be certain whether the type of the UE that transmitted the PRACH is a TDD UE or an SBFD-supporting UE. In this case, the base station can assume that the type of the aforementioned UE is always a TDD UE.

[0427] According to an embodiment, when the base station has determined that the relevant UE is a UE supporting SBFD, the base station can configure itself to schedule msg2, msg3, msg4, etc., for the UE based on the uplink subband. For example, when the base station schedules the reception of msg2 and msg4 for the UE, the base station can schedule msg2 and msg4 so that they are not received in the uplink subband (e.g., when the UE receives a PDSCH including msg2 and msg4, the UE receives the PDSCH in frequency resources outside the uplink subband). Alternatively, when the base station schedules msg3 PUSCH, the base station can schedule msg3 PUSCH so that it is transmitted in the uplink subband.

[0428] According to the embodiment, when the base station has determined that the relevant UE is a TDD UE, the base station may not be able to use the uplink subband configuration when scheduling msg2, msg3, msg4, etc. for the UE. For example, even if the uplink subband is configured for the downlink symbol or flexible symbol, the base station may assume that the UE cannot obtain the configured uplink subband configuration information. When scheduling msg3 PUSCH for the UE, the base station can schedule msg3 PUSCH for either the flexible symbol or the uplink symbol. In other words, msg3 PUSCH cannot be scheduled for the uplink subband.

[0429] According to various embodiments of this disclosure, the base station may not configure separate random access resources for SBFD-enabled UEs, but may configure common random access resources for all UEs in the cell. In this case, configuration information related to the random access resources can be sent to all UEs in the cell via system information, and upon receiving such system information, the SBFD-enabled UE can perform random access for the configured random access resources. Subsequently, the SBFD-enabled UE can complete the random access procedure and enter RRC connection mode for transmitting / receiving data with the cell. After entering RRC connection mode, the SBFD-enabled UE can receive upper-layer signals or physical signals from the base station, thereby determining that a portion of the downlink time resources is configured as uplink resources, and can accordingly perform SBFD operations (e.g., transmitting uplink signals in the configured uplink resources).

[0430] According to an embodiment, when it is determined that the cell supports SBFD, the SBFD-enabled UE can send capability information to the base station. This capability information includes at least one of the following: information related to whether the UE supports SBFD; information related to whether it supports full-duplex or half-duplex communication; or the number of transmit or receive antennas that the UE has (or supports), thereby notifying the base station that the UE attempting to access the network is an SBFD-enabled UE. According to an embodiment, when an SBFD-enabled UE is required to perform half-duplex communication, the capability information may obviously not include information related to whether it supports half-duplex communication. The SBFD-enabled UE can report the capability information to the base station through a random access procedure, report the capability information separately to the base station after completing the random access procedure, or report the capability information to the base station after entering an RRD connection mode for transmitting / receiving data with the cell.

[0431] According to embodiments, a UE supporting SBFD can support half-duplex communication, enabling it to perform only uplink transmission or downlink reception at a specific time, similar to an existing TDD UE; or it can support full-duplex communication, enabling it to perform both uplink transmission and downlink reception at a specific time. Therefore, a UE supporting SBFD can report whether it supports half-duplex or full-duplex communication through capability information, and after such reporting, the base station can configure the UE supporting SBFD to perform transmission / reception using either half-duplex or full-duplex communication. When an UE supporting SBFD reports its half-duplex communication capability to the base station, during FDD operation according to TDD, since a duplexer is typically absent, a switching gap may be necessary to change the RF between transmission and reception.

[0432] According to embodiments, a UE can typically establish a radio link with the network through a random access procedure based on system information obtained during cell search and synchronization with the network. Random access can use either a contention-based or contention-free scheme. A contention-based random access scheme can be used when the UE performs cell selection and reselection during the initial cell access phase (e.g., when the UE transitions from RRC_IDLE state to RRC_CONNECTED state), or for other purposes. Contention-free random access can be used to reconfigure uplink synchronization when downlink data has arrived, during handover, or during location measurement.

[0433] Figure 11 An example of a random access procedure according to an embodiment of the present disclosure is shown. More specifically, refer to Figure 11 . Figure 11 The random access procedure in a wireless communication system is illustrated.

[0434] Figure 11 A contention-based random access procedure according to an embodiment is illustrated. Furthermore, although... Figure 11 Not shown, but the base station (gNB) can transmit synchronization signal blocks as described above. In this case, the gNB can periodically transmit synchronization signal blocks by using beam scanning. For example, the gNB can use up to 64 different beams within 5 ms to transmit synchronization signal blocks (e.g., SS / PBCH (SSB) blocks) including primary synchronization signal (PSS) / secondary synchronization signal (SSS) and physical broadcast channel (PBCH) signals, and can transmit multiple synchronization signal blocks using different beams. The UE can detect (select) the synchronization signal block with the optimal beam direction (e.g., the beam direction with the highest received signal strength or above a predetermined threshold), and can use the physical random access channel (PRACH) resources associated with the detected synchronization signal block to transmit a preamble. For example, in the first step 1110 of the random access procedure, the UE can send a random access preamble (or message 1) to the gNB. Upon receiving the random access preamble, the gNB can measure the transmission delay value between the UE and the gNB, and can perform uplink synchronization. Specifically, the UE can arbitrarily select a random access preamble from a set of random access preambles pre-provided by system information and transmit that random access preamble. The initial transmission power of the random access preamble can be determined based on the path loss between the gNB and the UE measured by the UE. Furthermore, the UE can determine the transmission beam direction (or transmission beam or beam) of the random access preamble based on the synchronization signal block received from the base station, and transmit the random access preamble by applying the determined transmission beam direction.

[0435] In the second step 1120, the gNB may send a Random Access Response (RAR) or Message 2 (msg2) to the UE in response to the detected random access attempt. The gNB may send an uplink transmission timing control command to the UE based on the transmission delay value measured using the random access preamble received in the first step. The base station may also send commands as scheduling information to control the power and uplink resources to be used by the UE. The scheduling information sent by the gNB may include control information related to the UE's uplink transmission beam. The RAR can be sent via the PDSCH and may include at least one of the following: - Index of random access preamble sequence detected by the network (or gNB) - Temporary Cell Radio Network Temporary Identifier (TC-RNTI) - Uplink scheduling authorization - Timing advance value According to an embodiment, in the second step 1120, if the UE fails to receive scheduling information (RAR) related to message 3 from the gNB within a predetermined time, the UE can return to the first step 1110. Upon returning to the first step, the UE can transmit a random access preamble using a transmission power that increases by a predetermined step size (e.g., power ramp-up), thereby increasing the probability that the gNB receives the random access preamble.

[0436] In the third step 1130, the UE can use the uplink resources allocated in the second step 1120 to send uplink information (e.g., scheduled transmission or message 3) to the gNB via the Physical Uplink Shared Channel (PUSCH), including its UE identifier (e.g., UE contention resolution identifier) ​​(or, if the UE already has a valid UE identifier (C-RNTI) in the cell before initiating the random access procedure). This PUSCH may be referred to as msg3 PUSCH. The transmission timing of the PUSCH used to send message 3 may follow the uplink transmission timing control command received from the gNB in ​​the second step 1120. Furthermore, the transmission power of the PUSCH used to send message 3 may be determined by considering the power ramp-up value of the random access preamble and the power control command received from the gNB in ​​the second step 1120. The PUSCH used to send message 3 may include a first uplink data signal sent from the UE to the gNB after the UE sends the random access preamble.

[0437] In step 1140, upon determining that the UE has performed random access without competing with other UEs, the gNB may send a message (e.g., a contention resolution (CR) message or message 4) including the identifier of the UE that sent uplink data in step 1130. In this regard, if multiple UEs receive the same TC-RNTI in step 1120, each of the multiple UEs receiving the same TC-RNTI may send message 3 including its UE identifier (UE contention resolution identifier) ​​to the gNB in ​​step 1130, and the gNB may send message 4 (CR message) including one of the identifiers of the multiple UEs to resolve the contention. If the UE receives message 4 (CR message) including its UE identifier from the gNB in ​​step 1140 (or, if the UE sends message 3 including the C-RNTI in step 1130 and receives UE-specific control information including cyclic redundancy check (CRC) based on the C-RNTI via the PDCCH in step 1140), the UE can determine that random access was successful. Therefore, among multiple UEs receiving the same TC-RNTI from the gNB, the UE whose UE identifier is included in message 4 (CR message) can be identified as having successfully contested the contention. The UE can send HARQ-ACK / NACK to the gNB via the Physical Uplink Control Channel (PUCCH) to indicate whether message 4 was successfully received.

[0438] According to an embodiment, if in the third step 1130, data transmitted by the UE competes with data from another UE, and the gNB therefore fails to receive a data signal from the UE, the gNB may stop transmitting data to the UE. Therefore, if the UE fails to receive data transmitted from the gNB during the predetermined time interval in the fourth step 1140, the UE may determine that the random access procedure has failed and may restart from the first step 1110.

[0439] As described above, in the first step 1110 of the random access procedure, the UE can transmit a random access preamble via PRACH. Each cell has 64 available preamble sequences, and four long preamble formats and nine short preamble formats can be used depending on the transmission type. The UE can generate the 64 preamble sequences using the cyclic shift value and root sequence index notified by the system information signal, and can randomly select a sequence to use as the preamble.

[0440] According to an embodiment, the gNB can provide the UE with configuration information related to random access resources (e.g., control information (or configuration information) indicating time and frequency resources that can be used for PRACH) using at least one of SIB, upper-layer signaling (Radio Resource Control (RRC) information), or downlink control information (DCI). Frequency resources for PRACH transmission can indicate the RB point at which transmission begins to the UE, and the number of RBs used can be determined based on the applied subcarrier spacing and the preamble format transmitted via PRACH. Time resources for PRACH transmission can be notified via the PRACH configuration index (e.g., 0 to 255) in Table 1 below, including the pre-configured PRACH configuration period, the subframe index including PRACH transmission time points (which can be interchanged with PRACH timing, transmission time points, etc.), the number of PRACH transmission time points in the start symbol or time slot, etc. The UE can determine the validity of the PRACH transmission time point indicated by the PRACH configuration index, and can determine that a valid PRACH transmission time point is only a PRACH transmission time point at which a random access preamble can be transmitted. By using the PRACH configuration index, the random access configuration information included in the SIB, and the index of the SSB selected by the UE, the UE can identify the time and frequency resources to be used to send the random access preamble, and can send the selected sequence as a preamble to the gNB.

[0441] Meanwhile, according to the embodiments of this disclosure, the following scheme is required: the UE supporting SBFD determines the validity of the PRACH transmission time point through SBFD configuration and PRACH configuration index for performing PRACH transmission, and performs PRACH transmission through the PRACH transmission time point that is considered valid; or, in the case where the valid PRACH transmission time point overlaps with downlink reception, the process is performed by the UE supporting SBFD.

[0442] [Table 1]

[0443]

[0444]

[0445]

[0446]

[0447]

[0448]

[0449] Figure 12Examples of time-division duplex (TDD) and sub-band non-overlapping full-duplex (SBFD) configurations according to embodiments of the present disclosure are shown. More specifically, Figure 12 An example of operating SBFD in the TDD band of a wireless communication system to which this disclosure is applied is shown; Figure 12 A illustrates the scenario of TDD operation in a specific frequency band. In a cell operating TDD, a gNB can, based on the TDD UL-DL resource configuration information that follows the downlink (or symbol) and uplink (or symbol) resource instructions for TDD, transmit / receive signals, including data / control information, with an existing TDD UE or a SBFD-enabled UE in downlink (or symbol), uplink (or symbol) 1201, or flexible (or symbol) slots (or symbols).

[0450] According to the embodiments, it can be assumed that according to Figure 12 The TDD UL-DL resource configuration information configures the DDDSU time slot format. In this context, "D" can refer to a time slot configured entirely by downlink symbols, "U" can refer to a time slot configured entirely by uplink symbols, and "S" can refer to a time slot that is neither "D" nor "U" (e.g., a time slot including downlink symbols, uplink symbols, or flexible symbols). For convenience, it can be assumed that "S" is configured with 12 downlink symbols and 2 flexible symbols, but this is merely an example and not a limitation. The DDDSU time slot format can be repeated according to the TDD UL-DL resource configuration information. For example, the repetition period of the TDD configuration can include 5 time slots (e.g., 5ms in the case of 15kHz SCS and 2.5ms in the case of 30kHz SCS).

[0451] Next, Figure 12 B Figure 12 C and Figure 12 D illustrates the case where TDD and SBFD operate together in a specific frequency band.

[0452] Reference Figure 12 B. A portion of the cell's frequency band can be allocated to the UE as frequency band 1210 capable of uplink transmission. This frequency band can be referred to as the UL subband. The UL subband can be applied to all symbols in all time slots. The UE can transmit scheduled uplink channels or signals at all symbols 1212 in the UL subband. However, the UE cannot transmit uplink channels or signals in frequency bands outside the UL subband.

[0453] Reference Figure 12C. A portion of the cell's frequency band can be allocated to the UE as frequency band 1220 for uplink transmission, and a time zone can be configured for the UE to activate this frequency band. This frequency band can be referred to as the UL sub-band. (See reference...) Figure 12 C. The UL subband in the first time slot can be deactivated, and the UL subband in the remaining time slots can be activated. Therefore, the UE can transmit uplink channels or signals on the UL subband 1222 in the remaining time slots. That is to say, Figure 12 C shows an example of activating the UL subband for each time slot, but this is just an example, and it is obvious that activation / deactivation can be configured for each symbol.

[0454] Reference Figure 12 D. Time-frequency resources capable of uplink transmission can be configured for the UE. One or more time-frequency resources can be configured for the UE as time-frequency resources capable of uplink transmission. For example, a portion of the frequency band 1232 of the first and second time slots can be configured for the UE as time-frequency resources capable of uplink transmission. Furthermore, a portion of the frequency band 1233 of the third time slot and a portion of the frequency band 1234 of the fourth time slot can be configured for the UE as time-frequency resources capable of uplink transmission.

[0455] In the following description, time-frequency resources capable of uplink transmission at downlink symbols or flexible symbols may be referred to as SBFD resources / UL subbands.

[0456] According to various embodiments of this disclosure, the gNB can send a first PRACH configuration to the UE via system information and can configure RACH timing based on the first PRACH configuration. The UE can determine that all or some RACH timings are valid. The first PRACH configuration can be a PRACH configuration for a TDD UE. Therefore, when a valid RACH timing is determined based on the first PRACH configuration, the TDD UE may not be able to use configuration information related to SBFD resources or UL subbands.

[0457] According to an embodiment, in an FDD cell, all RACH timings that follow the configured first PRACH configuration can be defined as valid. A valid RACH timing can be defined as the first valid RACH timing (RO).

[0458] According to an embodiment, in a TDD cell, in the configured first PRACH configuration, a RACH timing can be valid only if the following conditions are met. A valid RACH timing can be defined as a first valid RACH timing (RO).

[0459] According to the embodiment, if the UE does not receive TDD DL / UL configuration information through system information, and in the PRACH slot, the RACH timing is not earlier than SS / PBCH, and starts after Ngap symbols from the last received symbol of SS / PBCH, the UE can determine that the RACH timing is valid.

[0460] According to the embodiment, when the UE has received TDD DL / UL configuration information through system information, in the RACH timing or PRACH slot located within the UL symbol, if the RACH timing is not earlier than SS / PBCH and starts after Ngap symbols from the last received symbol of SS / PBCH, and if Ngap symbols start from the last DL symbol, the UE can determine that the RACH timing is valid.

[0461] According to an embodiment, the value of Ngap can be determined based on the subcarrier spacing of the preamble and the PRACH preamble format. For example, in the case of preamble format B4, Ngap=0. In other preamble formats, if the subcarrier spacing is 1.25kHz or 5kHz, then Ngap=0; or if the subcarrier spacing is 15kHz, 30kHz, 60kHz, or 120kHz, then Ngap=2. If the subcarrier spacing is 480kHz, then Ngap=8; or if the subcarrier spacing is 960kHz, then Ngap=16.

[0462] Figure 13 Examples of effective RACH timing in TDD and SBFD configurations according to embodiments of the present disclosure are shown. More specifically, Figure 13 The effective RACH timing in a TDD cell is shown.

[0463] According to various embodiments of this disclosure, reference is made to Figure 13A. It can be assumed that DDDSU is configured for the UE via TDD DL / UL configuration information, and the RACH timing for each time slot is configured according to the first PRACH configuration. The UE can determine that the RACH timings overlapping with UL symbols among those determined according to the first PRACH configuration are valid RACH timings. The fifth time slot (e.g., the last time slot of the TDD cycle configured as DDDSU) is an uplink time slot, and RACH timing 1301 can be valid. However, the RACH timings for the first, second, third, and fourth time slots (e.g., the first four time slots of the TDD cycle configured as DDDSU) do not start after Ngap symbols from the last downlink symbol, and therefore can be invalid. Therefore, the UE can determine that the RACH timings for four uplink time slots out of the 20 time slots (e.g., time slots 5, 10, 15, and 20) are valid, and the RACH timings for the remaining 16 time slots are invalid.

[0464] According to various embodiments of this disclosure, a UE supporting SBFD can determine the validity of a RACH timing based on a second PRACH configuration. The second PRACH configuration can be a PRACH configuration for a UE supporting SBFD. SBFD-supporting UEs may include UEs capable of obtaining resource configuration information related to SBFD resource / UL subbands and TDD DL / UL configurations. Therefore, when determining a RACH timing based on the second PRACH configuration, the UE can use the resource configuration information related to SBFD resource / UL subbands and the TDD DL / UL configuration format. A RACH timing determined to be valid based on the second PRACH configuration can be referred to as a second RACH timing.

[0465] According to an embodiment, the first RACH configuration can determine the effective RACH timing based on the TDD DL / UL configuration and the SSB configuration. The first effective RACH timing based on the first RACH configuration can be located in the uplink symbol or flexible symbol of the TDD DL / UL configuration.

[0466] According to an embodiment, the second RACH configuration can determine the effective RACH timing based on the TDD DL / UL configuration, SSB configuration, and SBFD configuration. The effective RACH timing determined according to the second RACH configuration can be located on the symbols in the downlink symbols of the TDD DL / UL configuration that have the SBFD UL subband configured.

[0467] According to another embodiment, the effective RACH timing determined according to the second RACH configuration can be located on a symbol configured with an SBFD UL subband in the downlink or flexible symbols of the TDD DL / UL configuration. Alternatively, the effective RACH timing determined according to the second RACH configuration can be located on a symbol configured with an SBFD UL subband in the downlink or flexible symbols of the TDD DL / UL configuration, or on an uplink symbol of the TDD DL / UL configuration. Alternatively, the effective RACH timing determined according to the second RACH configuration can be located on a symbol configured with an SBFD UL subband in the downlink or flexible symbols of the TDD DL / UL configuration, or on a flexible or uplink symbol of the TDD DL / UL configuration.

[0468] Figure 14 An example of RACH timing according to an embodiment of this disclosure is shown. More specifically, Figure 14 The RACH timing based on preamble format 0 in Table 1 is shown.

[0469] Reference Figure 14 When configuring RACH with index 0 for the UE, index 16 can be assigned to the UE. The RACH timing in subframe 9 of frame n+1 (n=0, 1, ...).

[0470] Reference Figure 14 When configuring RACH with index 1 for a UE, an index of 8 can be assigned to the UE. The RACH timing in subframe 9 of frame n+1 (n=0, 1, ...).

[0471] Reference Figure 14 When configuring RACH with index 2 for the UE, index 4 can be assigned to the UE. The RACH timing in subframe 9 of frame n+1 (n=0, 1, ...).

[0472] The RACH timing in subframe 9 can be allocated to the UE according to the RACH configuration index, but the SBFD UL subband may not be configured in that subframe.

[0473] More specifically, Table 1 includes the RACH timings corresponding to the positions of uplink symbols (or uplink time slots) in the TDD DL / UL configuration. For example, the TDD DL / UL configuration may include a DDDSU structure. Here, D may represent a downlink time slot, S may represent a special time slot, and U may represent an uplink time slot. A downlink time slot may include all downlink symbols in that time slot, an uplink time slot may include all uplink symbols in that time slot, and a special time slot may include downlink symbols, uplink symbols, and flexible symbols in that time slot.

[0474] According to an embodiment, when the TDD DL / UL configuration includes a 15kHz subcarrier spacing, each slot of DDDSU can be 1ms, and subframe 9 can be a U slot. Therefore, a first RACH opportunity on the U slot can be allocated to the UE according to the RACH configuration index. However, when the SBFD UL subband is configured in the DL slot, a second RACH opportunity on the SBFD UL subband may not be available for allocation to the UE according to the RACH configuration index.

[0475] Figure 15 Examples of RACH timing in TDD and SBFD configurations according to embodiments of the present disclosure are shown. More specifically, Figure 15 An example of a TDD DL / UL configuration including a 30kHz subcarrier spacing and DDDSU, and an SBFD UL subband configured in all downlink symbols and flexible symbols, is shown. Figure 15 An example is shown where the RACH configuration index is configured to 2.

[0476] According to an embodiment, when the RACH configuration index is 2, a RACH timing can be configured on subframe 1500 with subframe index (n_sf) 9 in frames with frame indices (n_f) of 1, 5, 9, etc. Subframe 9 (n_sf=9) can include a time slot containing an SBFD symbol and a time slot containing a UL symbol. In this way, when a RACH timing is configured to span two time slots, the RACH timing may not be a valid RACH timing. When RACH configuration index 2 is indicated in the first PRACH configuration, the first valid RACH timing needs to be located on a flexible symbol or a UL symbol, so the RACH timing may not be the first valid RACH timing. When RACH configuration index 2 is indicated in the second PRACH configuration, the second valid RACH timing needs to be located on a flexible symbol or a UL symbol, so the RACH timing may not be the second valid RACH timing. Therefore, it may be difficult to configure a second valid RACH timing on an SBFD symbol using the RACH configuration in Table 1.

[0477] This disclosure discloses a method for configuring a second RACH timing on a DL time slot (or special time slot) configured with an SBFD UL subband.

[0478] [Method 1] Using FDD / SUL RACH configuration table

[0479] According to the method of this disclosure, the UE can apply a first RACH configuration table to a first PRACH configuration, and can apply a second RACH configuration table to a second PRACH configuration. The first RACH configuration table can be a RACH configuration table for the TDD band as shown in Table 1. The second RACH configuration table can be a RACH configuration table for the FDD band or the supplementary UL (SUL) band as shown in Table 2 below.

[0480] According to the method of this disclosure, the UE can obtain a first RACH configuration index based on a first PRACH configuration. The UE can obtain the RACH configuration corresponding to the first RACH configuration index from a first RACH configuration table (e.g., a RACH configuration table for TDD bands as shown in Table 1). The UE can obtain the first RACH timing from the obtained RACH configuration.

[0481] According to the method of this disclosure, the UE can obtain a second RACH configuration index based on the second PRACH configuration. The UE can obtain the RACH configuration corresponding to the second RACH configuration index from the second RACH configuration table (e.g., the RACH configuration table for FDD band or SUL band as shown in Table 2). The UE can obtain the second RACH timing from the obtained RACH configuration.

[0482] According to the method of this disclosure, even if the UE is operating in the TDD band, the UE can use the RACH configuration table for the FDD band or the SUL band to be allocated a second RACH opportunity in the SBFD UL subband.

[0483] Figure 16 An example of RACH timing using a RACH configuration table for the FDD band or Supplemental Uplink (SUL) band, according to embodiments of this disclosure, is shown. More specifically, Figure 16 An example is shown where the second RACH configuration index is configured to 8 according to the method of this disclosure, based on the second PRACH configuration.

[0484] Referring to Table 2, based on the RACH configuration corresponding to RACH configuration index = 8, a second RACH timing can be configured on subframe 1600, where subframe index (n_sf) is 1, 5, 9, etc., and frame index (n_f) is 1, 5, 9, etc. The second RACH timing can overlap with the third and fourth time slots in the "DDDSU" time slot of the TDDDL / UL configuration. Since the SBFD UL subband is configured on the third and fourth time slots, the second RACH timing can be valid.

[0485] Table 2

[0486]

[0487]

[0488]

[0489]

[0490]

[0491]

[0492] Figure 17 The operation flow of a UE transmitting signals during a RACH timing according to an embodiment of the present disclosure is illustrated.

[0493] In Operation 1700, the UE can receive a first PRACH configuration including a first RACH configuration index and a second PRACH configuration including a second RACH configuration index from the base station via higher-layer signals (e.g., System Information Block (SIB) or RRC).

[0494] In operation 1710, the UE may determine the first RACH timing based on the row corresponding to the first RACH configuration index in the first RACH configuration table. The determined first RACH timing may include at least one of the preamble format, frame index, subframe index, or slot index, or the index of the start symbol. The first RACH configuration table may be a RACH configuration table for the TDD band.

[0495] In operation 1711, the UE can identify the validity of the determined first RACH timing. This validity can be determined based on TDD configuration or SSB reception configuration.

[0496] In operation 1720, the UE can determine the second RACH timing based on the row corresponding to the second RACH configuration index in the second RACH configuration table. The determined second RACH timing may include at least one of the preamble format, frame index, subframe index, or slot index, or start symbol index. The second RACH configuration table may be a RACH configuration table for the FDD band or the SUL band.

[0497] In operation 1721, the UE can identify the validity of the determined second RACH timing. This validity can be determined based on TDD configuration, SSB receive configuration, or SBFD configuration.

[0498] In operation 1730, the UE may send the PRACH preamble during either the first valid RACH timing or the second valid RACH timing.

[0499] [Method 2] Shift the second RACH timing according to the SBFD configuration.

[0500] According to the method of this disclosure, the UE can determine the RACH timing based on a second PRACH configuration. For convenience, the determined RACH timing can be referred to as the nominal RACH timing. The nominal RACH timing can be shifted to an adjacent SBFD symbol (or SBFD time slot). The RACH timing determined by shifting the nominal RACH timing can be referred to as the actual RACH timing. The UE can perform PRACH transmissions within the actual RACH timing.

[0501] According to an embodiment, adjacent SBFD symbols can be determined within a frame configured with nominal RACH timing. For example, the nominal RACH timing and the actual RACH timing can be located in the same frame. It is also possible to disallow the nominal RACH timing and the actual RACH timing to be in different frames.

[0502] According to an embodiment, the SBFD symbol closest to the nominal RACH timing can be one of the adjacent SBFD symbols determined above. The closest SBFD symbol can be the closest SBFD symbol after the nominal RACH timing. The time period after the nominal RACH timing can be applied based on "wrap-around" or "cyclic shift" within the frame. For example, when the nominal RACH timing is located in subframe 9, the time period after the nominal RACH timing can be subframe 0.

[0503] According to embodiments, adjacent SBFD symbols can be determined in a frame where the nominal RACH timing is configured or in adjacent frames. For example, the nominal RACH timing and the actual RACH timing can be located in the same frame or adjacent frames. For example, it is permissible for the nominal RACH timing and the actual RACH timing to be located in different frames.

[0504] According to the embodiment, the SBFD symbol closest to the nominal RACH timing can be one of the adjacent SBFD symbols determined above. The closest SBFD symbol can be the closest SBFD symbol after the nominal RACH timing. When the nominal RACH timing is located in subframe 9 of frame n_f, the subframe after the nominal RACH timing can be subframe 0 of frame n_f+1.

[0505] According to various embodiments of this disclosure, the nominal RACH timing of subframe n_sf can be shifted to the adjacent subframe n_sf', and the RACH timing shifted to subframe n_sf' can be referred to as the actual RACH timing. The RACH timing can be shifted on a subframe basis.

[0506] According to an embodiment, a method for determining the actual RACH timing subframe n_sf' based on the nominal RACH timing subframe n_sf may include at least one of the following.

[0507] According to various embodiments of this disclosure, the initial condition may be m_sf = n_sf.

[0508] According to an embodiment, the UE can sequentially increment the subframe index m_sf by 1. When a subframe (e.g., with index m_sf+1) meets the termination condition, the UE can determine the index of that subframe as n_sf' (e.g., n_sf'=m_sf). When the subframe does not meet the termination condition, the UE can change m_sf to m_sf=m_sf+1 and repeat the above process.

[0509] According to an embodiment, when the UE increments the subframe index by 1 (e.g., from m_sf to m_sf+1), the UE can apply modulo operations. For example, when m_sf is incremented by 1, the subframe index can be... This restricts the nominal RACH timing and the actual RACH timing to 10 subframes within the same frame.

[0510] According to an embodiment, when the subframe index increases by 1 (e.g., from m_sf to m_sf+1), the UE can apply modulo operation and increase the frame index. When m_sf increases by 1, the subframe index can be... Furthermore, the frame index can be n_f + floor((m_sf + 1) / 10). For example, the subframe corresponding to m_sf = 9 is the last subframe of the frame (index n_f). According to this method, the subframe obtained by incrementing the subframe index by 1 can be the first subframe of the next frame (index n_f + 1).

[0511] According to various embodiments of this disclosure, a termination condition can be determined based on whether an SBFD symbol is configured on the subframe. For example, a termination condition can be determined based on whether at least one SBFD symbol is configured on the subframe. For example, a termination condition can be determined based on whether all SBFD symbols are configured on the subframe.

[0512] According to an embodiment, the termination condition may further include the following conditions. Additional conditions may be... For example, when the UE determines the subframe (index n_sf') where the actual RACH timing occurs by incrementing the subframe index from the subframe of the nominal RACH timing (index n_sf), the subframe of the actual RACH timing needs to be located within a predetermined window starting from the subframe of the nominal RACH timing.

[0513] According to an embodiment, the termination condition may further include the following condition. As an additional condition, the subframe index may be increased up to M times. M may be a value configured by the base station for the UE via higher-layer signals (e.g., RRC signals), or a fixed value. For example, M may be 10. Alternatively, M may be the number of subframes included in the TDD period.

[0514] Figure 18 An example of RACH timing based on SBFD configuration shift according to an embodiment of this disclosure is shown.

[0515] According to an embodiment, Figure 18 An example of a TDD DL / UL configuration is shown, which includes a 30kHz subcarrier spacing and a DDDSU, and SBFD UL subbands are configured on symbols in the second and third time slots of the DDDSU. Figure 18 The case where the second RACH configuration index is configured as 2 is illustrated. When the second RACH configuration index is 2, based on Table 1, the second nominal RACH timing can be configured on subframe 1800, where the subframe index (n_sf) is 9, within frames with frame indices (n_f) of 1, 5, 9, etc. Subframe 9 (n_sf=9) can include a time slot containing SBFD symbols and a time slot containing UL symbols. According to this disclosure, the second nominal RACH timing can be shifted on a subframe basis.

[0516] For example, the UE can determine a subframe whose index has increased by 1 (index is...). Does the termination condition in subframe 1810 meet? When assuming all symbols on the subframe are SBFD symbols as the termination condition, in subframe (index 1810)... In 1810, the termination condition may not be met.

[0517] According to the embodiment, the UE can determine the subframe whose index has increased by 1 (index is...). Does the termination condition in subframe 1811 satisfy? When assuming all symbols on the subframe are SBFD symbols as the termination condition, in subframe (index 1811)... In step 1811, the termination condition may not be met.

[0518] According to the embodiment, the UE can determine the subframe whose index has increased by 1 (index is...). Does the termination condition in subframe 1812 meet? When assuming all symbols on the subframe are SBFD symbols as the termination condition, in subframe (index 1812)... In 1812, the termination condition may not be met.

[0519] According to the embodiment, the UE can determine the subframe whose index has increased by 1 (index is...). Does the termination condition in subframe 1813 meet? When assuming all symbols on the subframe are SBFD symbols as the termination condition, in subframe (index 1813)... The termination condition can be met in subframe 1813. Therefore, the UE can use subframe (indexed as...) This was determined as the second actual RACH timing.

[0520] In the above method, the UE can determine the actual RACH timing by shifting on a subframe basis. The UE can also determine the shift on a time slot basis. Methods for this purpose are described according to various embodiments of this disclosure.

[0521] According to the method of this disclosure, when the index of the first time slot (e.g., the earliest time slot in chronological order) that overlaps with the nominal RACH timing is assumed to be n_slot, the nominal RACH timing can be shifted to the adjacent time slot n_slot'. The RACH timing shifted to time slot n_slot' can be referred to as the actual RACH timing. When the nominal RACH timing overlaps with N consecutive time slots, the actual RACH timing can overlap with N consecutive time slots starting from time slot n_slot' (e.g., including time slot n_slot').

[0522] According to various embodiments of this disclosure, a method for determining the actual RACH timing slot n_slot' based on the nominal RACH timing slot n_slot may include at least one of the following.

[0523] According to various embodiments of this disclosure, the initial condition may be m_slot = n_slot.

[0524] According to an embodiment, the UE can sequentially increment the slot index m_slot by 1. When a slot (e.g., index m_slot+1) meets the termination condition, the UE can determine the index of that slot as n_slot' (e.g., n_slot'=m_slot). When the slot does not meet the termination condition, the UE can change m_slot to m_slot=m_slot+1 and repeat the above process.

[0525] According to an embodiment, when the time slot index increases by 1 (e.g., from m_slot to m_slot+1), the UE can apply modulo operations. For example, when m_slot increases by 1, the time slot index can be... This restricts the nominal RACH timing and the actual RACH timing to within the same frame. In each time slot.

[0526] here, It is the number of time slots included in a single subframe, and can be determined based on the subcarrier spacing.

[0527] here, Corresponding to the subcarrier spacing, and when the subcarrier spacing is 15kHz, It can be 0 when the subcarrier spacing is 30kHz. It can be 1 when the subcarrier spacing is 60kHz. It can be 2, when the subcarrier spacing is 120kHz. It can be 3, when the subcarrier spacing is 240kHz. It can be 4, when the subcarrier spacing is 480kHz. It can be 5, and when the subcarrier spacing is 960kHz. It can be 6.

[0528] According to an embodiment, when the time slot index increases by 1 (e.g., from m_slot to m_slot+1), the UE can apply modulo operation and increase the frame index. When m_slot increases by 1, the time slot index can be... And the frame index can be For example, with The corresponding time slot can be the last time slot of the frame (index n_f). According to this method, the subframe obtained by incrementing the time slot index by 1 can be the first time slot of the next frame (index n_f+1).

[0529] According to various embodiments of this disclosure, a termination condition can be determined based on whether an SBFD symbol is configured on a time slot. For example, a termination condition can be determined based on whether at least one SBFD symbol is configured on a time slot. For example, a termination condition can be determined based on whether all SBFD symbols are configured on a time slot.

[0530] According to an embodiment, the termination condition may further include the following conditions. Additional conditions may be... For example, when a UE determines the actual RACH time slot (index n_slot') by incrementing the time slot index from the nominal RACH time slot (index n_slot), the actual RACH time slot needs to be within a predetermined window starting from the nominal RACH time slot.

[0531] According to an embodiment, the termination condition may further include the following condition. As an additional condition, the time slot index may be increased up to M times. M may be a value configured by the base station for the UE via higher-layer signals (e.g., RRC signals), or a fixed value. For example, M may be... Alternatively, M can be the number of time slots included in the TDD cycle.

[0532] [Method 3] Determining RACH timing based on overwrite

[0533] According to the method of this disclosure, the UE can obtain a first RACH configuration index from a first PRACH configuration and a second RACH configuration index from a second PRACH configuration. The UE can determine the first RACH timing by applying the first RACH configuration index to a RACH configuration table (e.g., Table 1). For convenience, the determined first RACH timing can be referred to as the first nominal RACH timing. The UE can determine the second RACH timing by applying the second RACH configuration index to the same RACH configuration table (e.g., Table 1). For convenience, the determined second RACH timing can be referred to as the second nominal RACH timing.

[0534] According to various embodiments of this disclosure, a base station can configure additional RACH information for a UE. The additional RACH information can be applied only to a second nominal RACH timing. For example, the additional RACH information may not be applied to a first nominal RACH timing. Therefore, the first actual RACH timing may be the same as the first nominal RACH timing.

[0535] According to an embodiment, based on a second RACH configuration index and a RACH configuration table (e.g., Table 1), the second nominal RACH timing may include at least one of the following: an index (n_f) of the frame including the RACH timing; an index (n_sf) of the subframe including the RACH timing; an index (n_slot) of the time slot including the RACH timing; and an index (n_symbol) of the start symbol. The UE can receive additional RACH information from the base station including at least one of the following information.

[0536] Including the frame index (n_f') for RACH timing.

[0537] Including the index (n_sf') of the subframe where the RACH timing occurs.

[0538] Including the index of the slot (n_slot') for RACH timing.

[0539] The index of the symbol at the start of the RACH timing (n_symbol')

[0540] According to an embodiment, the UE can apply additional RACH information to a second nominal RACH timing. The RACH timing determined by applying the additional RACH information can be referred to as the second actual RACH timing.

[0541] According to various embodiments, when the UE receives the index (n_f') of a frame including the RACH timing as additional RACH information, the UE can determine that the second actual RACH timing is included in the frame with index n_f'. The UE can maintain other configurations (index of subframe (n_sf) or index of start symbol (n_symbol)) determined according to the second RACH configuration index and the RACH configuration table (e.g., Table 1).

[0542] According to an embodiment, when the UE receives the index (n_sf') of a subframe including the RACH timing as additional RACH information, the UE can determine that the second actual RACH timing is included in the subframe with index n_sf'. The slot index of the second actual RACH timing can be... The UE can maintain other configurations (the index of the frame (n_f) or the index of the start symbol (n_symbol)) determined according to the second RACH configuration index and the RACH configuration table (e.g., Table 1).

[0543] According to an embodiment, the index (n_sf') of the subframe including the RACH timing can have a value of 0, 1, 2, ..., 9.

[0544] According to various embodiments, when the UE receives the index (n_slot') of the slot containing the RACH timing as additional RACH information, the UE can determine that the second actual RACH timing is included in the slot with index n_slot'. The subframe index of the second actual RACH timing can be... The UE can maintain other configurations (the index of the frame (n_f) or the index of the start symbol (n_symbol)) determined according to the second RACH configuration index and the RACH configuration table (e.g., Table 1).

[0545] According to an embodiment, the index (n_slot') of the slot including the RACH timing can have 0, 1, 2, ... The value in.

[0546] According to various embodiments, when the UE receives the index (n_symbol') of the symbol at the start of the RACH timing as additional RACH information, the UE can determine that the second actual RACH timing begins at the symbol with index n_symbol'. The UE can maintain other configurations (frame index (n_f), subframe index (n_sf), or slot index (n_slot)) determined according to the second RACH configuration index and the RACH configuration table (e.g., Table 1).

[0547] According to an embodiment, the index (n_symbol') of the symbol at the start of the RACH timing can have a value in the range of 0, 1, 2, ..., 13.

[0548] Although the various embodiments described above show that the additional RACH information includes only one piece of information, this is merely an example, and the additional RACH information may include two or more pieces of information. In this case, the actual RACH timing can be determined based on the included information.

[0549] According to an embodiment, the index (n_f') of the frame including the RACH timing in the above information can be configured as follows. For example, the frame index (n_f') can be configured using the frame period (P) and offset (O). The index (n_f') of the frame including the RACH timing can satisfy... O can be 0, 1, ... or P-1.

[0550] According to an embodiment, the index (n_f') of the frame including the RACH timing in the above information can be configured as follows. For example, the frame offset (O) can be used to configure the frame index (n_f'). The index (n_f') of the frame including the RACH timing can satisfy... O can be 0, 1, ..., or P-1. P can be a value determined based on the second RACH configuration index and the RACH configuration table (e.g., Table 1). For example, the x value in the RACH configuration table can be P.

[0551] According to an embodiment, the index (n_f') of the frame including the RACH timing in the above information can be configured as follows. For example, the frame period (P) can be used to configure the frame index (n_f'). The index (n_f') of the frame including the RACH timing can satisfy... O can be a value determined based on the second RACH configuration index and the RACH configuration table (e.g., Table 1). For example, the y value in the RACH configuration table can be 0.

[0552] Figure 19 Another operational flow for a UE to transmit signals during a RACH timing is illustrated according to an embodiment of this disclosure.

[0553] In Operation 1900, the UE can receive a first PRACH configuration including a first RACH configuration index and a second PRACH configuration including a second RACH configuration index from the base station via higher-layer signals (e.g., System Information Block (SIB) or RRC). Furthermore, the UE can receive additional RACH configurations. These additional RACH configurations can be configurations applicable only to the second RACH timing.

[0554] In Operation 1910, the UE may determine the first nominal RACH timing based on the row corresponding to the first RACH configuration index in the RACH configuration table (e.g., Table 1). The determined first nominal RACH timing may include at least one of the following: preamble format, frame index, subframe index, or slot index, or start symbol index. The first RACH configuration table may be a RACH configuration table for the TDD band.

[0555] In Operation 1911, the UE can determine that the first actual RACH timing is the same as the first nominal RACH timing.

[0556] In Operation 1912, the UE can identify the validity of the determined first actual RACH timing. This validity can be determined based on TDD configuration or SSB receive configuration.

[0557] In Operation 1920, the UE may determine the second nominal RACH timing based on the row corresponding to the second RACH configuration index in the RACH configuration table (e.g., Table 1). The determined second nominal RACH timing may include at least one of the preamble format, frame index, subframe index or slot index, and start symbol index.

[0558] In Operation 1921, the UE can determine the modified second actual RACH timing based on the additional RACH configuration, according to at least one of the frames, subframes, time slots, or start symbols of the second nominal RACH timing. When the UE does not receive the additional RACH configuration in Operation 1900, the UE can determine that the second actual RACH timing is the same as the second nominal RACH timing.

[0559] In Operation 1922, the UE can identify the validity of the determined second actual RACH timing. This validity can be determined based on TDD configuration, SSB receive configuration, or SBFD configuration.

[0560] In Operation 1930, the UE can send the PRACH preamble during either the first valid RACH timing or the second valid RACH timing.

[0561] [Method 4] Determining RACH timing based on time offset

[0562] According to the method of this disclosure, the UE can obtain a first RACH configuration index from a first PRACH configuration and a second RACH configuration index from a second PRACH configuration. The UE can determine the first RACH timing by applying the first RACH configuration index to a RACH configuration table (e.g., Table 1). For convenience, the determined first RACH timing can be referred to as the first nominal RACH timing. The UE can determine the second RACH timing by applying the second RACH configuration index to the same RACH configuration table (e.g., Table 1). For convenience, the determined second RACH timing can be referred to as the second nominal RACH timing.

[0563] According to various embodiments of this disclosure, a base station can configure additional RACH information for a UE. The additional RACH information can be applied only to a second nominal RACH timing. For example, the additional RACH information may not be applied to a first nominal RACH timing. Therefore, the first actual RACH timing may be the same as the first nominal RACH timing.

[0564] According to an embodiment, based on a second RACH configuration index and a RACH configuration table (e.g., Table 1), the second nominal RACH timing may include at least one of the following: an index (n_f) of the frame including the RACH timing; an index (n_sf) of the subframe including the RACH timing; an index (n_slot) of the time slot including the RACH timing; and an index (n_symbol) of the start symbol. The UE can receive additional RACH information from the base station including at least one of the following information.

[0565] The time offset of the index used for the frame index including the RACH timing ( )

[0566] The time offset of the index used for the subframe index including the RACH timing ( )

[0567] Time offset used for indexing time slots including RACH timing ( )

[0568] The time offset used for the index of the symbol at the start of the RACH timing ( )

[0569] According to an embodiment, the UE can apply additional RACH information to a second nominal RACH timing. The RACH timing determined by applying the additional RACH information can be referred to as the second actual RACH timing.

[0570] According to various embodiments, when the UE receives the time offset of the index used for the frame index including the RACH timing ( When used as supplementary RACH information, the UE can determine that the second actual RACH timing is included in the index. In another example, the UE can determine that the second actual RACH timing is included in the frame that satisfies the index. In the frame (n_f). Here, x and y can be values ​​determined according to the second RACH configuration index and the RACH configuration table (e.g., Table 1). The UE can maintain other configurations determined according to the second RACH configuration index and the RACH configuration table (e.g., Table 1) (index of subframe (n_sf), index of slot (n_slot), or index of start symbol (n_symbol)).

[0571] According to an embodiment, when the UE receives the time offset of the index used for the subframe index including the RACH timing ( When used as supplementary RACH information, the UE can determine that the second actual RACH timing is included in the index. In the subframe. In another example, the UE can determine that the second actual RACH timing is included in the index of In the subframe. The slot index of the second actual RACH timing can be The UE may retain other configurations (frame index (n_f), slot index (n_slot), or start symbol index (n_symbol)) determined according to the second RACH configuration index and RACH configuration table (e.g., Table 1).

[0572] According to an embodiment, It can have values ​​from 0, 1, 2, ..., 9. The 0 can be omitted.

[0573] Figure 20 An example of RACH timing shifted according to an embodiment of the present disclosure is shown.

[0574] According to various embodiments, refer to Figure 20 (a) The UE can determine that the second nominal RACH timing is located on subframe 9 (n_sf=9) 2000 of frame n_f (n_f=1, 5, 9, etc.). A time offset of 7 can be configured for the UE to use as the index of the subframe including the RACH timing. This information is included in the additional RACH configuration. According to embodiments of this disclosure, the UE can determine that the second actual RACH timing is included in the index... In subframe 2010, the frame index can remain unchanged.

[0575] According to an embodiment, when the UE receives the time offset for the index of the subframe including the RACH timing ( When used as supplementary RACH information, the UE can determine that the second actual RACH timing is included in the index. The frame index is In the subframe. The slot index of the second actual RACH timing can be The UE can maintain other configurations (slot index (n_slot) or start symbol index (n_symbol)) determined according to the second RACH configuration index and the RACH configuration table (e.g., Table 1).

[0576] here, It can have values ​​from 0, 1, 2, ..., 9. The 0 can be omitted.

[0577] According to various embodiments, refer to Figure 20 (b) The UE can determine that the second nominal RACH timing is located on subframe 9 (n_sf=9) 2020 of frame n_f (n_f=1, 5, 9, etc.). A time offset of 7 can be configured for the UE to include the index of the subframe containing the RACH timing. This information is included in the additional RACH configuration. According to embodiments of this disclosure, the UE can determine that the second actual RACH timing is included in the index... The frame index is In subframe 2030.

[0578] According to an embodiment, when the UE receives the time offset for the index of the subframe including the RACH timing ( When used as supplementary RACH information, the UE can determine that the second actual RACH timing is included in the index. The frame index is In the subframe. The slot index of the second actual RACH timing can be The UE can maintain other configurations (slot index (n_slot) or start symbol index (n_symbol)) determined according to the second RACH configuration index and the RACH configuration table (e.g., Table 1).

[0579] According to an embodiment, when When the value is between 0 and 9, It can be ;when When the value is between 10 and 19, ; and when 10 i+0 to 10 When i+9 is the value Here, i can be 0, 1, 2, etc. For example, according to... The UE can index the subframe according to the offset. The shift on the frame, or the shift of the subframe in the next frame based on the offset.

[0580] According to various embodiments, refer to Figure 20 (c) The UE can determine that the second nominal RACH timing is located on subframe 9 (n_sf=9) 2040 of frame n_f (n_f=1, 5, 9, etc.). A time offset of 7 can be configured for the UE to be used for the index of the subframe including the RACH timing. This information is included in the additional RACH configuration. According to embodiments of this disclosure, the UE can determine that the second actual RACH timing is included in the index... The frame index is In subframe 2050, a time offset of 17 can be configured for the UE to use the index of the subframe that includes the RACH timing. This information is included in the additional RACH configuration. According to embodiments of this disclosure, the UE can determine that the second actual RACH timing is included in the index... The frame index is In subframe 2060.

[0581] According to the embodiment, when the UE receives the time offset of the index of the symbol used for the start of the RACH timing (( When used as supplementary RACH information, the UE can determine that the second actual RACH timing is included in the index. In another example, the UE can determine that the second actual RACH timing is included in the index. In the time slot. For the normal cyclic prefix (CO). It is 14; and for the extended cyclic prefix (C), it is 12. The UE may maintain other configurations (the index of the frame (n_f), the index of the subframe (n_sf), or the index of the slot (n_slot)) determined according to the second RACH configuration index and the RACH configuration table (e.g., Table 1).

[0582] According to an embodiment, It can have 0, 1, 2, ... The value in.

[0583] [Method 5] Additional determination of SBFD UL sub-band

[0584] According to the method of this disclosure, the UE can obtain a second RACH configuration index from a second PRACH configuration. The UE can determine the second RACH timing by applying the second RACH configuration index to a RACH configuration table (e.g., Table 1). The UE can identify the symbol configured with the second RACH timing as an SBFD symbol without separate signaling from the base station for the SBFD UL subband. An SBFD symbol can refer to a symbol configured with an SBFD UL subband. Therefore, the UE can always determine the SBFD UL subband corresponding to the second RACH timing.

[0585] In the above method, separate signaling for the SBFD UL subband may not be required. In another method, a separate SBFD UL subband can be configured for the UE for a second RACH timing. According to embodiments of this disclosure, the presence of an SBFD UL subband corresponding to each RACH timing can be configured for the UE. When the presence of an SBFD UL subband corresponding to a single RACH timing is configured for the UE, the UE can additionally determine the SBFD UL subband on the symbols occupied by that single RACH timing.

[0586] [Additional Method 1] Include only some SSBs in the SSB-RO mapping

[0587] According to various embodiments of this disclosure, the UE can apply SSB-RO mapping to only some SSBs during the SSB-RO mapping process. More specifically, the UE can receive SSB configuration from the base station, and the SSB configuration can be included in SIB1 or the UE's RRC signal. The UE can receive SIB1 during initial cell access. The UE can receive RRC signals during the cell access procedure. The UE can determine the SSBs included in the SSB-RO mapping process based on SIB1 or the RRC signal. The signaling method used for the above SSB determination is described in detail below.

[0588] According to various embodiments, the following discloses signaling methods for SSB determination.

[0589] According to an embodiment, the UE can receive bits corresponding to each SSB from the base station. When the bit received by the UE is "0" (or "1"), the UE can determine that the SSB corresponding to that bit is not included in the SSB-RO mapping. When the bit is "1" (or "0"), the UE can determine that the SSB corresponding to that bit is included in the SSB-RO mapping.

[0590] According to an embodiment, when a base station configures N SSBs for a UE (e.g., the SSB can be an SSB within a single period; alternatively, the SSB can be an SSB included in a single half-frame (e.g., 5ms in length), bits can be generated in the form of a single bit sequence or bitmap, and the UE can receive the bit sequence or bitmap from the base station. According to an embodiment, the bit sequence or bitmap can include N bits. Each bit of the bit sequence or bitmap can correspond to a single SSB. For example, starting from the MSB, the first bit of the bit sequence or bitmap (e.g., the most significant bit (MSB)) can correspond to the SSB with index 0. Starting from the most significant bit (MSB), the second bit of the bit sequence or bitmap can correspond to the SSB with index 1. Starting from the most significant bit (MSB), the (i+1)th bit of the bit sequence or bitmap can correspond to the SSB with index i. According to an embodiment, the N SSBs can be indexed sequentially from 0 to N-1 in chronological order.

[0591] According to an embodiment, the UE can receive bits corresponding to each SSB set from the base station. When the bit received by the UE is "0" (or "1"), the UE can determine that all SSBs included in the SSB set corresponding to that bit are not included in the SSB-RO mapping. When the bit received by the UE is "1" (or "0"), the UE can determine that all SSBs included in the SSB set corresponding to that bit are included in the SSB-RO mapping. The method for generating SSB sets is described in detail below.

[0592] According to an embodiment, when a base station configures N SSBs for a UE (wherein, the SSB can be an SSB within a single period; alternatively, the SSB can be an SSB included in a single half-frame (e.g., 5ms in length), bits can be generated in the form of a single bit sequence or bitmap, and the UE can receive the bit sequence or bitmap from the base station. The bit sequence or bitmap can include M bits (e.g., a natural number less than N). Each bit of the bit sequence or bitmap can correspond to a set of SSBs. A unique index can be assigned to the SSB set. The index of the SSB set can be a value in the range 0, 1, ..., M-1. Starting from the MSB, the first bit of the bit sequence or bitmap (e.g., the most significant bit (MSB)) can correspond to the SSB set with index 0. Starting from the most significant bit (MSB), the second bit of the bit sequence or bitmap can correspond to the SSB set with index 1. Starting from the most significant bit (MSB), the (i+1)th bit of the bit sequence or bitmap can correspond to the SSB set with index i.

[0593] According to the various embodiments of this disclosure described above, the UE can determine that some SSBs configured by the base station are always included in the SSB-RO mapping regardless of the bit values. Therefore, the UE can expect that the bit value corresponding to the SSB will always be a specific value (e.g., a value indicating that the SSB is included in the SSB-RO mapping). Alternatively, the UE can determine that the SSB is always included in the SSB-RO mapping regardless of the bit value corresponding to it. Alternatively, the UE can expect not to receive the bit corresponding to the SSB from the base station. For example, the bit corresponding to the SSB can be excluded from an N-bit sequence or bitmap of N SSBs configured by the base station for the UE. When K out of the N SSBs are always included in the SSB-RO mapping, the length of the bit sequence or bitmap can be NK bits.

[0594] In the embodiments of this disclosure described above, the UE can determine that some SSBs configured by the base station are always excluded from the SSB-RO mapping regardless of the bit values. Therefore, the UE can expect the bit value corresponding to the SSB to always be a specific value (e.g., a value indicating that the SSB is excluded from the SSB-RO mapping). Alternatively, the UE can determine that the SSB is always excluded from the SSB-RO mapping regardless of the bit value corresponding to it. Alternatively, the UE can expect not to receive the bit corresponding to the SSB from the base station. For example, the bit corresponding to the SSB can be excluded from an N-bit sequence or bitmap of N SSBs configured by the base station for the UE. When K out of the N SSBs are always excluded from the SSB-RO mapping, the length of the bit sequence or bitmap can be NK bits.

[0595] According to an embodiment, the SSB always included in the SSB-RO mapping can be an SSB that overlaps with a specific symbol type. The specific symbol type can include symbols determined based on information configured by the base station. For example, the specific symbol type can be determined based on SBFD symbol configuration information.

[0596] - For example, a specific symbol type can be a non-SBFD symbol. Non-SBFD symbols can include downlink symbols or flexible symbols that are not configured with SBFD subbands.

[0597] - For example, a specific symbol type can be an SBFD symbol. SBFD symbols can include downlink symbols configured with SBFD subbands or flexible symbols.

[0598] Figure 21 Examples of some SSBs excluded from SSB-RO mapping according to embodiments of this disclosure are shown.

[0599] Reference Figure 21The base station can configure X SSBs for the UE. These X SSBs may include SSBs configured within a single SSB period (e.g., 20ms). The UE can receive these SSBs to obtain downlink synchronization information and cell information.

[0600] Reference Figure 21 The UE can receive bits corresponding to each SSB from the base station. The bits received by the UE can be represented as a bitmap. The number of bits included in the bitmap can be the same as the number of SSBs. The UE can determine whether an SSB is used for SSB-RO mapping based on this bit. According to an embodiment, when the bit is "0", the corresponding SSB can be included in the SSB-RO mapping; and when the bit is "1", the corresponding SSB can be excluded from the SSB-RO mapping. (See also...) Figure 21 Since the bit corresponding to SSB#1 (SSB with index 1) 2100 is "1", SSB#1 can be excluded from the SSB-RO mapping. For example, the UE can determine that there is no RO associated with SSB#1. Since the bits corresponding to other SSBs (such as SSB#0 and SSB#2 to SSB#(X-1)) are "0", these SSBs can be included in the SSB-RO mapping.

[0601] although Figure 21 A one-to-one mapping between SSB and RO is shown, but this disclosure is not limited thereto and can also be applied to one-to-many or many-to-one mappings between SSB and RO.

[0602] [Additional Method 2] Method for generating RO sets

[0603] According to various embodiments of this disclosure, ROs can be included in a set of ROs in order of their RO indices. For example, N ROs can be included in a set of M ROs in order of their RO indices. For example, among the N ROs, the N / M ROs with the lowest index can be included in the set of ROs with the lowest index (e.g., index 0). The indices of the N / M ROs with the lowest index can be 0, 1, ..., and N / M-1. Typically, the index starts from N / M... k to N / M A RO of (k+1)-1 can be included in the set of ROs with index k. N is divisible by M. For example, N can be an integer multiple of M.

[0604] When N is not divisible by M, the number of ROs included in a single RO set can be floor(N / M) or ceil(N / M). More specifically, in M ​​RO sets, the first RO set can include ceil(N / M) ROs, and the remaining second RO set can include floor(N / M) ROs. The number of ROs in the first RO set can be... And the number of sets in the second RO can be .

[0605] According to an embodiment, two sets of Returns (ROs) may exist. Here, ROs that overlap with SBFD symbols can be included in the first RO set, and ROs that do not overlap with SBFD symbols can be included in the second RO set. For example, the RO sets can be generated based on the SBFD symbol configuration. According to the example above, the UE can receive a first bit from the base station indicating whether all ROs that overlap with SBFD symbols should be used for SSB-RO mapping. The UE can receive a second bit from the base station indicating whether all ROs that do not overlap with SBFD symbols should be used for SSB-RO mapping.

[0606] In the example above, the UE can receive bits from the base station corresponding to ROs or RO sets included in the SSB-RO mapping. In another example, the UE can receive an index of an RO or RO set included in the SSB-RO mapping from the base station. For example, the UE can receive an index instead of bits, and when receiving the index, the RO or RO set corresponding to that index can be included in the SSB-RO mapping (or, when receiving the index, the RO or RO set corresponding to that index can be excluded from the SSB-RO mapping).

[0607] For example, when a base station configures N Return Entities (ROs) for a UE, the indices of the N ROs can be 0, 1, ..., N-1. The UE can receive from the base station the indices of the ROs included in the SSB-RO mapping from among the N ROs. When the UE receives indices {2, 3, 4, 5, 6, 7} from the base station, the ROs with indices 2, 3, 4, 5, 6, and 7 can be included in the SSB-RO mapping. However, ROs with indices different from the above indices may not be included in the SSB-RO mapping.

[0608] For example, when a base station configures N Return Entities (ROs) for a UE, the indices of the N ROs can be 0, 1, ..., N-1. The UE can receive from the base station the indices of the ROs included in the SSB-RO mapping from among the N ROs. When the UE receives indices {2, 3, 4, 5, 6, 7} from the base station, the ROs with indices 2, 3, 4, 5, 6, and 7 can be excluded from the SSB-RO mapping. However, ROs with indices different from the above indices can be included in the SSB-RO mapping.

[0609] [Additional Method 3] Include only some ROs in the SSB-RO mapping

[0610] According to various embodiments of this disclosure, the UE can apply SSB-RO mapping to only some ROs during the SSB-RO mapping process. More specifically, the UE can receive RACH configuration from the base station. The RACH configuration received by the UE can be included in SIB1 or the UE's RRC signal. The RACH configuration can include the format of the PRACH preamble, configuration related to the index of the frame and subframe used to transmit the PRACH preamble, and configuration related to the index of the symbol in the subframe where the PRACH preamble can begin. The UE can receive SIB1 during initial cell access. The UE can receive RRC signals through the cell access procedure. The UE can determine the ROs included in the SSB-RO mapping process based on SIB1 or RRC signals. The signaling method used for the above SSB determination is described below.

[0611] In the following text, unless otherwise stated, RO may refer to a valid RO. However, according to embodiments of this disclosure, a RO configured before its validity is determined may also be applicable.

[0612] [Additional Method 4] Signaling used for RO determination

[0613] According to various embodiments of this disclosure, the UE can receive bits corresponding to each RO from the base station. When the bit received by the UE is "0" (or "1"), the UE can determine that the RO corresponding to that bit is not included in the SSB-RO mapping. When the bit is "1" (or "0"), the UE can determine that the RO corresponding to that bit is included in the SSB-RO mapping.

[0614] According to an embodiment, when a base station configures N Returning Objects (ROs) for a UE (where the ROs can be the number of ROs within a single associated period), bits can be generated in the form of a single bit sequence or bitmap, and the UE can receive the bit sequence or bitmap from the base station. The bit sequence or bitmap can include N bits. Each bit of the bit sequence or bitmap can correspond to a single RO. For example, starting from the Most Significant Bit (MSB), the first bit of the bit sequence or bitmap (e.g., the most significant bit (MSB)) can correspond to the RO with index 0. Starting from the most significant bit (MSB), the second bit of the bit sequence or bitmap can correspond to the RO with index 1. Starting from the most significant bit (MSB), the (i+1)th bit of the bit sequence or bitmap can correspond to the RO with index i. According to an embodiment, the N ROs can be indexed sequentially from 0 to N-1 in chronological order.

[0615] According to an embodiment, the UE can receive bits corresponding to each RO set from the base station. When the bit received by the UE is "0" (or "1"), the UE can determine that all ROs included in the RO set corresponding to that bit are not included in the SSB-RO mapping. When the bit is "1" (or "0"), the UE can determine that all ROs included in the RO set corresponding to that bit are included in the SSB-RO mapping. The method for generating RO sets is described in detail below.

[0616] According to an embodiment, when a base station configures N Returning Objects (ROs) for a UE (e.g., the ROs may be ROs within a single associated period), bits can be generated in the form of a single bit sequence or bitmap, and the UE can receive the bit sequence or bitmap from the base station. The bit sequence or bitmap may include M bits (e.g., a natural number less than N). Each bit of the bit sequence or bitmap may correspond to a set of ROs. A unique index can be assigned to the RO set. The index of the RO set can be a value in the range 0, 1, ..., M-1. Starting from the MSB, the first bit of the bit sequence or bitmap (e.g., the most significant bit (MSB)) may correspond to the RO set with index 0. Starting from the most significant bit (MSB), the second bit of the bit sequence or bitmap may correspond to the RO set with index 1. Starting from the most significant bit (MSB), the (i+1)th bit of the bit sequence or bitmap may correspond to the RO set with index i.

[0617] According to the various embodiments of this disclosure described above, the UE can determine that certain Returns (ROs) configured by the base station are always included in the SSB-RO mapping regardless of the bit values. Therefore, the UE can expect that the bit value corresponding to the RO is always a specific value (e.g., a value indicating that the RO is included in the SSB-RO mapping). Alternatively, the UE can determine that the RO is always included in the SSB-RO mapping regardless of the bit value corresponding to it. Alternatively, the UE can expect not to receive the bit corresponding to the RO from the base station. For example, the bit corresponding to the RO can be excluded from an N-bit sequence or bitmap of N ROs configured by the base station for the UE. When K out of the N ROs are always included in the SSB-RO mapping, the length of the bit sequence or bitmap can be NK bits.

[0618] According to the various embodiments of this disclosure described above, the UE can determine that some ROs configured by the base station are always excluded from the SSB-RO mapping regardless of the bit values. Therefore, the UE can expect the bit value corresponding to the RO to always be a specific value (e.g., a value indicating that the RO is excluded from the SSB-RO mapping). Alternatively, the UE can determine that the RO is always excluded from the SSB-RO mapping regardless of the bit value corresponding to it. Alternatively, the UE can expect not to receive the bit corresponding to the RO from the base station. For example, the bit corresponding to the RO can be excluded from an N-bit sequence or bitmap of N ROs configured by the base station for the UE. When K out of the N ROs are always excluded from the SSB-RO mapping, the length of the bit sequence or bitmap can be NK bits.

[0619] According to an embodiment, the RO always included in the SSB-RO mapping can be an RO that overlaps with a specific symbol type. The specific symbol type can include symbols determined based on information configured by the base station. For example, the specific symbol type can be determined based on SBFD symbol configuration information.

[0620] - For example, a specific symbol type can include non-SBFD symbols. Non-SBFD symbols can include symbols that are not configured with SBFD subbands.

[0621] For example, a specific symbol type can include SBFD symbols. SBFD symbols can include symbols configured with SBFD subbands.

[0622] Figure 22 Examples are shown where some SSBs of an RO according to embodiments of this disclosure are excluded from the SSB-RO mapping.

[0623] Reference Figure 22 The base station can configure an SSB for the UE. According to an embodiment, the SSB may include an SSB configured within a single SSB period (e.g., 20ms). The UE can receive the SSB to obtain downlink synchronization information and cell information.

[0624] Reference Figure 22 The UE can receive bits corresponding to each RO from the base station. The bits received by the UE can be represented as a bitmap. The number of bits included in the bitmap can be the same as the number of ROs within the RACH association period. The UE can determine whether an RO is used for SSB-RO mapping based on this bit. According to an embodiment, when the bit is "0", the corresponding RO can be included in the SSB-RO mapping; and when the bit is "1", the corresponding RO can be excluded from the SSB-RO mapping. (See also...) Figure 22Since the bit corresponding to RO#3 (e.g., RO with index 3) 2200 is "1", RO#3 can be excluded from the SSB-RO mapping. For example, the UE can determine that there is no SSB associated with RO#3. Since the bits corresponding to other ROs (such as RO#0, RO#1, RO#2, and RO#4) are "0", these ROs can be included in the SSB-RO mapping.

[0625] although Figure 22 A one-to-many mapping between SSB and RO is shown, but this disclosure is not limited thereto and can also be applied to a one-to-one mapping or a many-to-one mapping between SSB and RO.

[0626] According to various embodiments of this disclosure, specific methods for generating SSB sets are described.

[0627] According to an embodiment, SSBs can be included in the SSB set in the order of their SSB indices. For example, N SSBs can be included in the M SSB set in the order of their SSB indices. For example, among the N SSBs, the N / M SSBs with the lowest index can be included in the SSB set with the lowest index (e.g., index 0). The indices of the N / M SSBs with the lowest index can be 0, 1, ..., and N / M-1. Typically, the index starts from N / M. k to N / M The SSB with index (k+1)-1 can be included in the set of SSBs with index k. N is divisible by M. For example, N can be an integer multiple of M.

[0628] According to an embodiment, when N is not divisible by M, the number of SSBs included in a single SSB set can be floor(N / M) or ceil(N / M). More specifically, in M ​​SSB sets, the first SSB set may include ceil(N / M) SSBs, and the remaining second SSB set may include floor(N / M) SSBs. The number of SSBs in the first SSB set can be... And the number of sets in the second SSB can be .

[0629] According to an embodiment, two SSB sets may exist. Here, SSBs that overlap with SBFD symbols can be included in the first SSB set, and SSBs that do not overlap with SBFD symbols can be included in the second SSB set. For example, the SSB sets can be generated based on the SBFD symbol configuration. According to the example above, the UE can receive a first bit from the base station indicating whether all SSBs that overlap with SBFD symbols should be used for SSB-RO mapping. The UE can receive a second bit from the base station indicating whether all SSBs that do not overlap with SBFD symbols should be used for SSB-RO mapping.

[0630] In the example above, the UE can receive bits from the base station corresponding to an SSB or SSB set included in the SSB-RO mapping. In another example, the UE can receive an index of an SSB or SSB set included in the SSB-RO mapping from the base station. For example, the UE can receive the index instead of bits. When the UE receives the index, the SSB or SSB set corresponding to that index can be included in the SSB-RO mapping (or, when the UE receives the index, the SSB or SSB set corresponding to that index can be excluded from the SSB-RO mapping).

[0631] For example, when a base station configures N SSBs for a UE, the indices of the N SSBs can be 0, 1, ..., N-1. The UE can receive from the base station the indices of the SSBs included in the SSB-RO mapping from among the N SSBs. When the UE receives indices {2, 3, 4, 5, 6, 7} from the base station, the SSBs with indices 2, 3, 4, 5, 6, and 7 can be included in the SSB-RO mapping. However, SSBs with indices different from the above indices may not be included in the SSB-RO mapping.

[0632] For example, when a base station configures N SSBs for a UE, the indices of the N SSBs can be 0, 1, ..., N-1. The UE can receive from the base station the indices of the SSBs included in the SSB-RO mapping from among the N SSBs. When the UE receives indices {2, 3, 4, 5, 6, 7} from the base station, the SSBs with indices 2, 3, 4, 5, 6, and 7 can be excluded from the SSB-RO mapping. However, SSBs with indices different from the above indices can be included in the SSB-RO mapping.

[0633] According to various embodiments of this disclosure, methods for deactivating some ROs after SSB-RO mapping are described.

[0634] According to various embodiments of this disclosure, the UE can deactivate some ROs after SSB-RO mapping. Here, deactivation can indicate that the UE cannot send PRACH in the RO. The UE can receive information from the base station about the ROs to be deactivated. The information received by the UE can be transmitted to the UE's RRC signal via SIB1. The information received by the UE can be based on the SSB index or the RO index.

[0635] In the first method, the UE can receive information from the base station about the index of the SSB corresponding to the RO to be deactivated. The UE can determine that the RO associated with the SSB corresponding to the index is the RO to be deactivated. The information about the SSB index may include at least one of the following.

[0636] - The UE can receive bits corresponding to each configured SSB. When the bit received by the UE is a first value, the RO associated with the SSB corresponding to that bit can be deactivated. When the bit is a second value, the RO associated with the SSB corresponding to that bit may not be deactivated. For example, the RO can be activated, and the UE can send PRACH in the activated RO.

[0637] - The UE can receive the index value of the configured SSB. For example, when the base station configures N SSBs for the UE, each SSB can have a unique index. The index can be a value in the range 0, 1, ..., N-1. The UE can receive the SSB index from the base station. For example, when the index {4, 8} is received, the UE can determine that the RO associated with the SSB with index 4 and the RO associated with the SSB with index 8 are deactivated ROs. The UE can determine ROs other than the above-mentioned ROs as active ROs.

[0638] Figure 23 An example of RO deactivation based on SSB index value is shown according to an embodiment of this disclosure.

[0639] Reference Figure 23 The base station can configure an SSB for the UE. The SSB may include an SSB configured within a single SSB period (e.g., 20ms). The UE can receive the SSB to obtain downlink synchronization information and cell information.

[0640] Reference Figure 23 The UE can receive bits corresponding to each SSB from the base station. The bits received by the UE can be represented as a bitmap. The number of bits included in the bitmap can be the same as the number of SSBs. The UE can determine whether to use the RO associated with the SSB for PRACH transmission based on this bit. When the bit is "0", PRACH transmission can be performed in the RO associated with the corresponding SSB (e.g., the active RO); and when the bit is "1", PRACH transmission may not be performed in the RO associated with the corresponding SSB (e.g., the deactivated RO). (See reference...) Figure 23 Because the bit corresponding to SSB#1 (e.g., SSB with index 1) 2300 is "1", PRACH transmissions cannot be performed in RO#2 and RO#3 (e.g., deactivated ROs) associated with SSB#1. Because the bits corresponding to other SSBs (such as SSB#0 and SSB#2 to SSB#(X-1)) are "0", PRACH transmissions can be performed in ROs (e.g., active ROs) associated with said SSBs.

[0641] although Figure 23A one-to-many mapping between SSB and RO is shown, but this disclosure is not limited thereto and can also be applied to a one-to-one mapping or a many-to-one mapping between SSB and RO.

[0642] In the second method, the UE can receive information from the base station about the index of the RO to be deactivated. The UE can determine that the RO with the received index is the deactivated RO. The information about the SSB index may include at least one of the following.

[0643] - The UE can receive bits corresponding to each configured RO. When the bit received by the UE is a first value, the RO corresponding to that bit can be deactivated. When the bit is a second value, the RO corresponding to that bit may not be deactivated. For example, the RO can be activated, and the UE can send PRACH in the activated RO.

[0644] - The UE can receive the index values ​​of the configured ROs. For example, when the base station configures N ROs for the UE, each RO can have a unique index. The index of an RO can be a value in the range 0, 1, ..., N-1. The UE can receive the RO index from the base station. For example, when it receives the index {4, 8}, the UE can determine that the RO with index 4 and the RO with index 8 are deactivated ROs. The UE can determine ROs other than the above-mentioned ROs as active ROs.

[0645] Figure 24 An example of RO deactivation based on the index value of RO according to an embodiment of this disclosure is shown.

[0646] Reference Figure 24 The base station can configure an SSB for the UE. The SSB may include an SSB configured within a single SSB period (e.g., 20ms). The UE can receive the SSB to obtain downlink synchronization information and cell information.

[0647] Reference Figure 24 The UE can receive bits corresponding to each RO from the base station. The bits received by the UE can be represented as a bitmap. The number of bits included in the bitmap can be the same as the number of ROs within the RACH association period. The UE can determine whether to use an RO for PRACH transmission based on this bit. According to an embodiment, when the bit is "0", PRACH transmission can be performed in the corresponding RO (e.g., an active RO); and when the bit is "1", PRACH transmission may not be performed in the corresponding RO (e.g., a deactivated RO). See reference. Figure 24Since the bit corresponding to RO#3 (e.g., RO with index 3) 2400 is "1", PRACH transmission is not possible in RO#3 (e.g., the deactivated RO). Since the bits corresponding to other ROs (such as RO#0, RO#1, RO#2, RO#3, and RO#5) are "0", PRACH transmission is possible in the RO (e.g., the activated RO).

[0648] although Figure 24 A one-to-many mapping between SSB and RO is shown, but this disclosure is not limited thereto and can also be applied to a one-to-one mapping or a many-to-one mapping between SSB and RO.

[0649] [Additional Method 5] SSB Cycle Change for SSB-RO Mapping

[0650] According to various embodiments of this disclosure, a base station can configure a period for an SSB (hereinafter referred to as an SSB mapping period) for the UE to apply SSB-RO mapping.

[0651] More specifically, the base station can configure the SSB period (SSB period) for the UE. The UE can receive SSBs according to the configured period. For example, the SSB period can be 20ms. In this case, the UE can receive SSBs with the same index every 20ms. N SSBs can be included in a single period. The N SSBs configured in a single period can be called an SSB burst.

[0652] According to an embodiment, the base station can additionally configure the SSB mapping period for the UE. The SSB mapping period can be longer than the SSB period. For example, when the SSB period is X ms, the SSB mapping period can be Y ms, where Y can be greater than X or an integer multiple of X. For example, when the SSB period is X=20ms, the SSB mapping period can be Y=40ms. According to an embodiment, the UE can apply an SSB to the SSB-RO mapping every SSB mapping period. For example, when the SSB period is X=20ms and the SSB mapping period is Y=40ms, the UE can receive an SSB burst (e.g., N SSBs) every X=20ms, but can not always use the N SSBs of the SSB burst for SSB-RO mapping. The UE can use the SSB burst (e.g., N SSBs) corresponding to Y=40ms for SSB-RO mapping.

[0653] More specifically, when X=20ms, it can be done in frame 2. Configure the SSB burst for the UE in a single half-frame of k. Here, k is a non-negative integer. When Y=40ms, the UE can use it in frame 4. SSB bursts (e.g., N SSBs) configured in a single half-frame of frame k are used to perform SSB-RO mapping. Furthermore, SSB bursts (e.g., N SSBs) configured in a single half-frame of frame 4k+2 can be excluded from SSB-RO mapping.

[0654] According to various embodiments of this disclosure, the UE can transmit PRACH via an SSB associated with an SSB burst determined according to the SSB mapping period. However, the RO corresponding to an SSB burst other than this SSB burst (e.g., an SSB burst configured in a single half-frame of frame 4k+2 in the example above) can be deactivated.

[0655] [Additional Method 6] PRACH Period Change for SSB-RO Mapping

[0656] According to various embodiments of this disclosure, the base station can configure a period for applying SSB-RO mapping (hereinafter referred to as RACH mapping period) for the UE.

[0657] More specifically, a PRACH association period can be configured for the UE. The UE can use the ROs within the configured association period for SSB-RO mapping. For example, when the association period is 20ms, the UE can assign a unique index to each RO within 20ms (e.g., index each RO). According to an embodiment, the index can start from 0. The UE can associate ROs with SSBs. According to an embodiment, the above process can be repeated every 20ms.

[0658] According to an embodiment, the base station can additionally configure the RACH mapping period for the UE. The RACH mapping period configured for the UE can be longer than the PRACH association period. For example, when the PRACH association period is X ms, the RACH mapping period can be Y ms, where Y can be greater than X or an integer multiple of X. For example, when the PRACH association period is X=20ms, the RACH mapping period can be Y=40ms. According to an embodiment, the UE can apply RO to SSB-RO mapping in each RACH mapping period. For example, when the PRACH association period is X=20ms and the RACH mapping period is Y=40ms, the UE can determine the RO every 20ms, but may not always use the RO for SSB-RO mapping. The UE can use the RO corresponding to Y=40ms for SSB-RO mapping. For example, among the ROs within Y=40ms, only the RO in a single time interval (X ms) can be used for SSB-RO mapping.

[0659] According to an embodiment, the interval of Y ms can include multiple time intervals of X ms. For example, when Y = 40 ms and X = 20 ms, Y = 40 ms can include two time intervals (X = 20 ms). According to an embodiment, only the RO included in the first of the two time intervals can always be used for SSB-RO mapping.

[0660] More specifically, when X=20ms, the UE can determine frame 2 k and frame 2 RO in k+1. Here, k is a non-negative integer. When Y=40ms, the UE can use it in frame 4. k and frame 4 The RO configured in frame k+1 is used to perform SSB-RO mapping. Furthermore, ROs configured in frames 4k+2 and 4k+3 can be excluded from SSB-RO mapping.

[0661] According to various embodiments of this disclosure, the UE can transmit PRACH via ROs determined according to the PRACH mapping period. However, ROs other than those ROs can be deactivated.

[0662] According to an embodiment, the interval of Y ms can include multiple time intervals of X ms. For example, when Y = 40 ms and X = 20 ms, Y = 40 ms can include two time intervals (X = 20 ms). According to an embodiment, only the RO included in a specific time interval of the two time intervals can be used for SSB-RO mapping. Here, the UE can receive an indication of a specific time interval from the base station. For example, the UE can receive a bitmap corresponding to Y / X from the base station, and each bit of the bitmap can correspond to a time interval of X ms. When the bit is a specific value, the time interval of X ms can be included in the specific time interval.

[0663] According to an embodiment, the interval of Y ms can include multiple time intervals of X ms. For example, when Y = 40 ms and X = 20 ms, Y = 40 ms can include two time intervals (X = 20 ms). According to an embodiment, only the RO included in a single specific time interval of the two time intervals can be used for SSB-RO mapping. Here, the UE can receive an indication of this single specific time interval from the base station. For example, the base station can configure an index corresponding to Y / X for the UE, and the UE can receive an indication of a value in the index. The index can be a value among 0, 1, ... and Y / X-1.

[0664] According to embodiments, the UE can receive multiple PRACH configurations from the base station. For example, the first PRACH configuration may be a PRACH configuration for a TDD UE, and the second PRACH configuration may be a PRACH configuration for an SBFD UE. According to various embodiments of this disclosure, the above-described embodiments indicating the SSB or RO for SSB-RO mapping can be applied only to the second PRACH configuration. For example, in the first PRACH configuration, the UE can use all the SSBs configured for the UE and the ROs determined according to the first PRACH configuration to perform SSB-RO mapping. However, in the second PRACH configuration, the UE can use some of the SSBs configured for the UE and some of the ROs determined according to the second PRACH configuration to perform SSB-RO mapping.

[0665] Figure 25 The structure of a UE in a wireless communication system according to an embodiment of the present disclosure is shown.

[0666] Reference Figure 25 The UE may include a transceiver collectively referred to as UE receiver 2500 and UE transmitter 2510, a memory (not shown), and a UE processor 2505 (or UE controller, controller, or processor). The UE transceiver 2500 and 2510, the memory, and the UE processor 2505 can operate according to the communication method of the UE described above. The UE processor 2505 (or processor) can control the operation of the UE according to the corresponding embodiments described above and combinations of at least one of the embodiments. However, the components of the UE are not limited to the examples described above. For example, the UE may also include more or fewer components than those described above. Furthermore, the transceiver, memory, and processor may be implemented as a single chip.

[0667] A transceiver can transmit / receive signals with a base station. These signals may include control information and data. For this purpose, a transceiver may include an RF transmitter configured to amplify and up-convert the frequency of the transmitted signal, an RF receiver configured to perform low-noise amplification and down-conversion of the received signal, etc. However, this is only one embodiment of a transceiver, and the components of the transceiver are not limited to RF transmitters and RF receivers.

[0668] In addition, the transceiver can receive signals via a radio channel, output them to the processor, and transmit signals output from the processor via a radio channel.

[0669] The memory can store the programs and data required for the operation of the UE. In addition, the memory can store control information or data included in the signals transmitted / received by the UE. The memory can include storage media such as ROM, RAM, hard disk, CD-ROM, or DVD, or a combination of storage media. Furthermore, the memory can include multiple memories.

[0670] The processor can control a series of processes enabling the UE to operate according to the embodiments described above. For example, the processor can control the UE's components to receive DCI configured in a two-layer manner so as to receive multiple PDSCHs simultaneously. The processor may include multiple processors, and the processors can perform control operations on the UE's components by executing programs stored in memory.

[0671] Figure 26 The structure of a base station in a wireless communication system according to an embodiment of the present disclosure is shown.

[0672] Reference Figure 26 The base station may include a transceiver collectively referred to as base station receiver 2600 and base station transmitter 2610, a memory (not shown), and a base station processor 2605 (or base station controller, controller, or processor). The base station transceivers 2600 and 2610, the memory, and the base station processor 2605 may operate according to the communication method of the base station described above. The base station processor 2605 (or processor) may control the operation of the base station according to the corresponding embodiments described above and combinations of at least one of the embodiments. However, the components of the base station are not limited to the examples described above. For example, the base station may include more or fewer components than those described above. Furthermore, the transceiver, memory, and processor may be implemented as a single chip.

[0673] A transceiver can transmit / receive signals with a UE. These signals may include control information and data. For this purpose, the transceiver may include an RF transmitter configured to amplify and up-convert the frequency of the transmitted signal, an RF receiver configured to perform low-noise amplification and down-conversion of the received signal, etc. However, this is only one embodiment of a transceiver, and the components of the transceiver are not limited to RF transmitters and RF receivers.

[0674] In addition, the transceiver can receive signals via a radio channel, output them to the processor, and transmit signals output from the processor via a radio channel.

[0675] The memory can store the programs and data required for the operation of the base station. In addition, the memory can store control information or data included in the signals transmitted / received by the base station. The memory can include storage media such as ROM, RAM, hard disk, CD-ROM, and DVD, or combinations of storage media. Furthermore, the memory can include multiple memories.

[0676] The processor can control a series of processes that enable the base station to operate according to the embodiments of this disclosure described above. For example, the processor can control each component of the base station to configure a two-layer DCI including allocation information for multiple PDSCHs and to transmit the DCI. The processor may include multiple processors, and the processors can perform control operations on the components of the base station by executing programs stored in memory.

[0677] The methods disclosed in the claims or the methods of the embodiments described in this disclosure can be implemented by hardware, software, or a combination of hardware and software.

[0678] When implemented in software, a computer-readable storage medium may be provided for storing one or more programs (software modules). The one or more programs stored in the computer-readable storage medium may be configured to be executed by one or more processors within an electronic device. The at least one program includes instructions to cause the electronic device to perform methods as defined by the appended claims and / or as disclosed herein according to various embodiments of this disclosure.

[0679] These programs (software modules or software) can be stored in non-volatile memory including random access memory and flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), disk storage devices, compact disc read-only memory (CD-ROM), digital versatile disc (DVD), or other types of optical storage devices or magnetic tape. Alternatively, the programs can be stored in a combination of some or all of these memories. Furthermore, multiple such memories may be included.

[0680] Furthermore, the program can be stored in an attachable storage device that can be accessed by the electronic device via a communication network such as the Internet, intranet, local area network (LAN), wide area network (WLAN), and storage area network (SAN), or a combination thereof. Such a storage device can access the electronic device via an external port. Additionally, a separate storage device on the communication network can access the device used to execute embodiments of this disclosure.

[0681] In the detailed embodiments described above, the elements included in this disclosure are expressed in a singular or plural form according to the proposed detailed embodiments. However, for ease of description, the singular or plural form is appropriately chosen for the proposed situation, and this disclosure is not limited to elements expressed in a singular or plural form. Therefore, an element expressed in a plural form may also include a single element, or an element expressed in a singular form may include multiple elements.

[0682] The embodiments of this disclosure described and illustrated in the specification and drawings are merely specific examples provided to facilitate the explanation of the technical content of this disclosure and to aid in understanding it, and are not intended to limit the scope of this disclosure. That is, it will be apparent to those skilled in the art that other variations based on the technical concept of this disclosure can be implemented. Furthermore, the corresponding embodiments described above can be combined as needed. For example, a portion of one embodiment of this disclosure can be combined with a portion of another embodiment to operate a base station and a terminal. For example, a portion of a first embodiment of this disclosure can be combined with a portion of a second embodiment to operate a base station and a terminal. Moreover, although the above embodiments have been described based on an FDD LTE system, other variations based on the technical concept of the described embodiments can also be implemented in other communication systems such as TDD LTE and 5G or NR systems.

[0683] In the accompanying drawings describing the methods of this disclosure, the order of description does not always correspond to the order in which the steps of each method are performed, and the order between the steps may be changed, or the steps may be performed in parallel.

[0684] In the accompanying drawings describing the methods of this disclosure, the order of description does not always correspond to the order of the steps to be performed, and the order between the steps may be changed, or the steps may be performed in parallel.

[0685] Furthermore, in the methods of this disclosure, some or all of the contents of each embodiment may be combined to implement them without departing from the essential spirit and scope of this disclosure.

Claims

1. A user equipment (UE) in a wireless communication system, the UE comprising: transceiver; as well as A controller coupled to the transceiver The controller is configured as follows: Receive system information block 1 SIB1 from the base station, which includes information about the timing of multiple Additional Random Access Channels (RACH). Based on the information, identify the synchronization signal block SSB-random access channel RACH timing RO mapping between the synchronization signal block SSB and the valid RO; as well as Based on the information, at least one RO for physical RACH PRACH transmission is identified from the plurality of additional ROs.

2. The UE according to claim 1, wherein, The information includes the index value of the at least one RO or at least one bitmap corresponding to the at least one RO, and The at least one RO includes an activated RO or a deactivated RO identified based on the information.

3. The UE according to claim 1, wherein, The information is based on the RACH correlation period, and The additional ROs are used for sub-band full-duplex SBFD.

4. The UE according to claim 1, wherein, The controller is also configured to: Receive information from the base station for configuring the first period of the first SSB burst; as well as Receive from the base station information for configuring the second period of the second SSB burst according to the SSB-RO mapping, and The second period is longer than the first period.

5. A base station in a wireless communication system, the base station comprising: transceiver; as well as A controller coupled to the transceiver The controller is configured as follows: System information block 1SIB1, which includes information about the timing of multiple Additional Random Access Channels (RACH), is sent to the User Equipment (UE); and Based on the synchronization signal block SSB-random access channel RACH timing RO mapping between the synchronization signal block SSB and the effective RO, the UE receives the physical RACH PRACH on at least one of the plurality of additional ROs.

6. The base station according to claim 5, wherein, The information includes the index value of the at least one RO or at least one bitmap corresponding to the at least one RO, and The at least one RO includes an activated RO or a deactivated RO identified based on the information.

7. The base station according to claim 5, wherein, The information is based on the RACH correlation period, and The additional ROs are used for sub-band full-duplex SBFD.

8. The base station according to claim 5, wherein, The controller is also configured to: Send information for configuring the first period of the first SSB burst to the UE; as well as Send information to the UE for configuring the second period of the second SSB burst according to the SSB-RO mapping, and The second period is longer than the first period.

9. A method performed by a user equipment (UE) in a wireless communication system, the method comprising: Receive system information block 1 SIB1 from the base station, which includes information about the timing of multiple Additional Random Access Channels (RACH). Based on the information, identify the synchronization signal block SSB-random access channel RACH timing RO mapping between the synchronization signal block SSB and the valid RO; as well as Based on the information, at least one RO for physical RACH PRACH transmission is identified from the plurality of additional ROs.

10. The method according to claim 9, wherein, The information includes the index value of the at least one RO or at least one bitmap corresponding to the at least one RO, and The at least one RO includes an activated RO or a deactivated RO identified based on the information.

11. The method according to claim 9, wherein, The information is based on the RACH correlation period, and The additional ROs are used for sub-band full-duplex SBFD.

12. The method according to claim 9, further comprising: Receive information from the base station for configuring the first period of the first SSB burst; as well as Receive from the base station information for configuring the second period of the second SSB burst according to the SSB-RO mapping. The second period is longer than the first period.

13. A method performed by a base station in a wireless communication system, the method comprising: System information block 1SIB1 is sent to the user equipment (UE) including information about the timing of multiple additional random access channels (RACH). as well as Based on the synchronization signal block SSB-random access channel RACH timing RO mapping between the synchronization signal block SSB and the effective RO, the UE receives physical RACH PRACH on at least one of the plurality of additional ROs.

14. The method according to claim 13, wherein, The information includes the index value of the at least one RO or at least one bitmap corresponding to the at least one RO, and The at least one RO includes an activated RO or a deactivated RO identified based on the information.

15. The method according to claim 13, wherein, The information is based on the RACH correlation period, and The additional ROs are used for sub-band full-duplex SBFD.