Method and apparatus for random access in wireless communication system

Abstract

The present disclosure relates to a communication technology and a system for combining an Internet of Things (IoT, industrial Internet of Things) technology with a 5G communication system to support a higher data transmission rate than a 4G system. According to an embodiment of the present invention, a method of a terminal supporting sub-band non-overlapping full duplex (SBFD) in a wireless communication system may comprise the steps of: receiving time division duplex (TDD) resource configuration information and SBFD resource configuration information from a base station; determining a corresponding index of a common valid first random access channel (RACH) opportunity in the TDD resource configuration information and the SBFD resource configuration information, and determining a corresponding index of a common valid second random access channel (RACH) opportunity in the TDD resource configuration information and the SBFD resource configuration information; and determining a respective index of a second RACH occasion that is invalid in the TDD resource configuration information and valid in the SBFD resource configuration information.

Description

Technical Field

[0001] The present disclosure relates to operations of a terminal and a base station in a wireless communication system. In particular, the present disclosure relates to a method for a terminal to perform random access and a device capable of performing the method. Background Art

[0002] The fifth generation (5 th The sixth generation (5G) mobile communication technology defines a wide frequency band so that high transmission rates and new services are possible, and can be realized not only in the "below 6 GHz" frequency band such as 3.5 GHz, but also in the "above 6 GHz" frequency band called millimeter wave (mmWave) including 28 GHz and 39 GHz. In addition, the sixth generation (6G) in the terahertz frequency band (for example, the 95 GHz to 3 THz frequency band) has been considered. th The new 5G mobile communication technology will be called the super 5G system, in order to achieve a transmission rate that is fifty times faster than 5G mobile communication technology and an ultra-low latency that is one-tenth of 5G mobile communication technology.

[0003] At the beginning of the development of 5G mobile communication technology, in order to support services and meet performance requirements related to enhanced Mobile BroadBand (eMBB), Ultra-Reliable Low-Latency Communications (URLLC) and massive Machine-Type Communications (mMTC), there is ongoing standardization on the following items: beamforming and massive multiple-input multiple-output (MIMO) for mitigating radio wave path loss and increasing radio wave transmission distance in millimeter waves, supporting parameter sets for dynamic operation of millimeter wave resources and time slot formats for efficient utilization (for example, operating multiple subcarrier spacings), initial access technology for supporting multi-beam transmission and broadband, definition and operation of bandwidth parts (Band-Width Part, BWP), new channel coding methods (such as Low Density Parity Check (LDPC) codes for large-scale data transmission and polarization codes for highly reliable transmission of control information), L2 preprocessing, and network slicing for providing dedicated networks dedicated to specific services.

[0004] Currently, in view of the services to be supported by 5G mobile communication technology, discussions are ongoing on improvements and performance enhancements of initial 5G mobile communication technology, and there is already physical layer standardization on technologies such as: Vehicle-to-Everything (V2X) for assisting driving determination of autonomous vehicles based on information about the location and status of the vehicle sent by the vehicle and for enhancing user convenience, New Radio Unlicensed (NR-U) for system operation intended to comply with various regulatory requirements in unlicensed bands, NR UE power saving, Non-Terrestrial Network (NTN) (which is UE satellite direct communication for providing coverage in areas where communication with terrestrial networks is unavailable), and positioning.

[0005] In addition, there is ongoing standardization in the air interface architecture / protocol on technologies such as the Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, Integrated Access and Backhaul (IAB) for providing nodes for network service area expansion by supporting wireless backhaul links and access links in an integrated manner, mobility enhancements including conditional switching and dual-active protocol stack (DAPS) switching, and two-step random access (i.e., 2-step random access channel (RACH) for NR) for simplifying the random access process. There is also ongoing standardization on 5G baseline architecture (e.g., service-based architecture or service-based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies and system architecture / services for Mobile Edge Computing (MEC) for receiving services based on UE location.

[0006] With the commercialization of 5G mobile communication systems, the already exponentially growing number of connected devices will be connected to the communication network, and it is accordingly expected that enhanced functionality and performance of the 5G mobile communication system and integrated operation of connected devices will be necessary. To this end, new research related to extended reality (eXtended Reality, XR) is arranged to effectively support augmented reality (Augmented Reality, AR), virtual reality (Virtual Reality, VR), mixed reality (Mixed Reality, MR), etc., by utilizing artificial intelligence (Artificial Intelligence, AI) and machine learning (Machine Learning, ML), AI service support, meta-service support, and drone communication for 5G performance improvement and complexity reduction.

[0007] In addition, such development of 5G mobile communication systems will serve as a foundation for developing not only 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 antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional spatial multiplexing technology using orbital angular momentum (OAM), and reconfigurable intelligent surfaces (RIS), but also full-duplex technology for improving the frequency efficiency of 6G mobile communication technology and improving system networks, AI-based communication technology for achieving system optimization by utilizing satellites and AI from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at a complexity level that exceeds the limits of UE operating capabilities by utilizing ultra-high performance communication and computing resources.

[0008] With the development of wireless communication systems and the like, various services have become available, and a scheme for smoothly providing these services is required. Summary of the invention

[0009]

Technical issues

[0010] The embodiments of the present disclosure are intended to provide a device and method capable of effectively providing services in a mobile communication system. Specifically, a method for determining the validity of a PRACH transmission time is provided when a subband non-overlapping full-duplex (SBFD) terminal supporting the SBFD function performs random access.

[0011] The SBFD UE can be configured with an SBFD UL subband and can perform PRACH transmission for random access in the SBFD UL subband. Here, the SBFD UE can determine a valid RACH opportunity for random access in the SBFD UL subband, and because the non-SBFD UE (legacy terminal) cannot use the SBFD UL subband, it can determine the RACH opportunity overlapping with the SBFD UL subband as invalid. Therefore, the SBFD UE and the legacy terminal can have different valid RACH opportunities.

[0012] The effective RACH opportunity is connected to the SSB. With this information, the base station is able to use the downlink beamforming information of the SSB corresponding to the PRACH sent by the terminal to send the PDCCH scheduling Msg2, or the PDSCH including Msg2. However, since SBFD UE and traditional terminals have different effective RACH opportunities, the connected SSBs may also be different. Therefore, the base station may be ambiguous about which SSB downlink beamforming information to use.

[0013]

Technical solution

[0014] The present disclosure proposes a random access method in Sub-Band Non-Overlapping Full-Duplex (SBFD).

[0015] According to an embodiment of the present disclosure, a method for a terminal supporting sub-band non-overlapping full-duplex (SBFD) in a wireless communication system may include: receiving time division duplex division (TDD) resource configuration information and SBFD resource configuration information from a base station; determining a corresponding index of a first random access channel (RACH) opportunity that is commonly valid in the TDD resource configuration information and the SBFD resource configuration information; and determining a corresponding index of a second RACH opportunity that is invalid in the TDD resource configuration information and valid in the SBFD resource configuration information, wherein the TDD resource configuration information may include format information of each time slot, and the SBFD resource configuration information may include information about an uplink subband.

[0016]

Beneficial effects

[0017] The embodiments of the present disclosure provide a device and method capable of effectively providing services in a mobile communication system. Therefore, the accuracy of the SBFD UE in determining the validity of the PRACH transmission time is improved, and the SBFD UE can utilize more RACH opportunities in the process of performing random access. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0019] Figure 2 is a diagram illustrating the structure of a frame, a subframe, and a time slot in a wireless communication system according to an embodiment of the present disclosure.

[0020] Figure 3 is a diagram illustrating an example of a configuration of a bandwidth part (BWP) in a wireless communication system according to an embodiment of the present disclosure.

[0021] Figure 4 is a diagram showing an example of configuration of a control resource set of a downlink control channel in a wireless communication system according to an embodiment of the present disclosure.

[0022] Figure 5 is a diagram showing a structure of a downlink control channel in a wireless communication system according to an embodiment of the present disclosure.

[0023] Figure 6 is a diagram illustrating a method in which a base station and a UE perform data transmission / reception by considering a downlink data channel and a rate matching resource according to an embodiment of the present disclosure.

[0024] Figure 7 is a diagram illustrating an example of frequency domain resource allocation of a PDSCH in a wireless communication system according to an embodiment of the present disclosure.

[0025] Figure 8 is a diagram illustrating an example of time domain resource allocation of a PDSCH in a wireless communication system according to an embodiment of the present disclosure.

[0026] Fig. 9 is a diagram illustrating an example of time domain resource allocation based on subcarrier spacing of a data channel and a control channel in a wireless communication system according to an embodiment of the present disclosure.

[0027] Fig.10 is a diagram illustrating a radio protocol structure of a base station and a UE in cases of a single cell, carrier aggregation, and dual connectivity in a wireless communication system according to an embodiment of the present disclosure.

[0028] Fig.11 is a diagram illustrating a random access procedure in an embodiment of the present disclosure.

[0029] Fig.12 is a diagram illustrating a TDD configuration and a SBFD configuration according to an embodiment of the present disclosure.

[0030] Fig.13 is a diagram illustrating valid RACH opportunities in a TDD configuration and a SBFD configuration according to an embodiment of the present disclosure.

[0031] Fig.14is a diagram illustrating indexes of valid RACH opportunities in a TDD configuration and a SBFD configuration according to an embodiment of the present disclosure.

[0032] Fig.15 is a diagram illustrating a method for determining an index of a valid RACH opportunity in a TDD configuration and a SBFD configuration according to an embodiment of the present disclosure.

[0033] Fig.16 is a diagram illustrating a method for determining an index of a valid RACH opportunity in a TDD configuration and a SBFD configuration according to an embodiment of the present disclosure.

[0034] Fig.17 is a diagram illustrating a method for determining an index of a valid RACH opportunity in a TDD configuration and a SBFD configuration according to an embodiment of the present disclosure.

[0035] Fig.18 is a diagram illustrating a method for determining an index of a valid RACH opportunity in a TDD configuration and a SBFD configuration according to an embodiment of the present disclosure.

[0036] Fig.19 is a diagram illustrating a structure of a UE in a wireless communication system according to an embodiment of the present disclosure.

[0037] Fig. 20 is a diagram illustrating a structure of a base station in a wireless communication system according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0038] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.

[0039] When describing the embodiments of the present disclosure, descriptions of technical contents that are well known in the art and not directly related to the present disclosure will be omitted. This is to convey the subject matter of the present disclosure more clearly by omitting unnecessary descriptions without obscuring it.

[0040] For the same reason, some elements are exaggerated, omitted or schematically shown in the drawings. In addition, the size of each element depicted does not fully reflect the actual size. In the drawings, the same reference numerals are assigned to the same or corresponding elements.

[0041] By referring to the embodiments described in detail below in conjunction with the accompanying drawings, the advantages and features of the present disclosure and the ways to achieve them will be apparent. However, the present disclosure is not limited to the embodiments set forth below, but can be implemented in various different forms. The following embodiments are provided to inform those skilled in the art of the scope of the present disclosure, and the present disclosure is limited only by the scope of the appended claims. Throughout the description herein, the same or similar reference numerals represent the same or similar elements. In addition, when describing the present disclosure, when it is determined that the description may make the subject matter of the present disclosure unnecessarily unclear, the detailed description of the known functions or configurations incorporated herein will be omitted. The terms to be described below are terms defined in view of the functions in the present disclosure, and may be different according to the user, the user's intention or custom. Therefore, the definition of the terms should be based on the entire description of this article.

[0042] In the following description, a base station is an entity that allocates resources to a terminal, and may be at least one of a gNode B, an eNode B, a node B, a base station (BS), a wireless access unit, a BS controller, and a node on a network. The terminal may include a UE, a mobile station (MS), a cellular phone, a smart phone, a computer, or a multimedia system capable of performing a communication function. A downlink (DL) indicates a radio link via which a base station sends a signal to a terminal, and an uplink (UL) indicates a radio link via which a terminal sends a signal to a base station. In addition, in the following description, an LTE or LTE-A system may be described by way of example, but the embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. Examples of such communication systems may include 5th generation mobile communication technologies (5G, new radio, and NR) developed beyond LTE-A, and in the following description, 5G covers existing LTE, LTE-A, or other similar services. In addition, based on determinations made by those skilled in the art, the embodiments of the present disclosure may also be applied to other communication systems with some modifications without significantly departing from the scope of the present disclosure.

[0043] It will be understood that each box of the flowchart diagram and the combination of boxes in the flowchart diagram 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 device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate components for implementing the functions specified in the flowchart box (or multiple). These computer program instructions can also be stored in a computer-usable or computer-readable memory, which can instruct the computer or other programmable data processing device to act in a specific manner, so that the instructions stored in the computer-usable or computer-readable memory produce an article of instruction components including the functions specified in the flowchart box (or multiple). The computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are performed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in the flowchart box (or multiple).

[0044] In addition, each frame of the flowchart diagram can represent a module, a fragment or a part of a code, which includes one or more executable instructions for implementing a specified logical function (or multiple). It should also be noted that in some alternative embodiments, the functions mentioned in the frame may not occur in order. For example, two frames shown in succession can actually be performed substantially simultaneously, or frames can sometimes be performed in reverse order, depending on the functions involved.

[0045] As used herein, the term "unit" indicates a software element or hardware element that performs a predetermined function, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC). However, the term "unit" does not always have a meaning limited to software or hardware. "Unit" can be constructed to be stored in an addressable storage medium or to execute one or more processors. Therefore, "unit" includes, for example, software elements, object-oriented software elements, class elements or task elements, processes, functions, attributes, processes, subroutines, program code segments, drivers, firmware, microcodes, circuits, data, databases, data structures, tables, arrays and variables. The functions provided by elements and units can be combined into the functions of a smaller number of elements and units, or separated into the functions of a larger number of elements and units. In addition, elements and units can be implemented as one or more central processing units (CPU) in an operating device or a secure multimedia card. Moreover, in an embodiment, "unit" can include one or more processors.

[0046] Wireless communication systems have expanded beyond their original role of providing voice-oriented services and have evolved into broadband wireless communication systems that provide high-speed and high-quality packet data services according to communication standards such as High Speed ​​Packet Access (HSPA) in 3GPP, Long Term Evolution (LTE or Evolved Universal Terrestrial Radio Access (E-UTRA)), Advanced LTE (LTE-Advanced, LTE-A) or LTE-Pro in 3GPP, High Rate Packet Data (HRPD) or Ultra Mobile Broadband (UMB) in 3GPP2, and 802.16e in IEEE.

[0047] As a typical example of a broadband wireless communication system, the LTE system adopts an Orthogonal Frequency Division Multiplexing (OFDM) scheme in a downlink (DL) and a Single Carrier Frequency Division Multiple Access (SC-FDMA) scheme in an uplink (UL). The uplink indicates a radio link through which a user equipment (UE) or a mobile station (MS) sends data or a control signal to a base station (BS or eNodeB), and the downlink indicates a radio link through which a base station sends data or a control signal to a UE. The above-mentioned multiple access scheme can separate the data or control information of the corresponding users by allocating and operating time-frequency resources for sending data or control information to each user so as to avoid overlapping with each other, that is, so as to establish orthogonality.

[0048] Since the 5G communication system, which is a communication system after LTE, must freely reflect various requirements of users, service providers, etc., it is necessary to support services that meet various requirements. Services considered in the 5G communication system include enhanced mobile broadband (eMBB) communication, massive machine type communication (mMTC), ultra-reliable low latency communication (URLLC), etc.

[0049] eMBB aims to provide higher data rates than those supported by existing LTE, LTE-A or LTE-Pro. For example, in a 5G communication system, eMBB must provide a peak data rate of 20Gbps in the downlink and a peak data rate of 10Gbps in the uplink for a single base station. In addition, the 5G communication system must provide an increased user-perceived data rate to the UE, as well as a maximum data rate. In order to meet such requirements, it is necessary to improve the transmission / reception technology including further enhanced multiple-input multiple-output (MIMO) transmission technology. In addition, a frequency bandwidth greater than 20MHz can be used in a frequency band of 3 to 6GHz or 6GHz or higher to obtain the data rate required by the 5G communication system, instead of using a transmission bandwidth of up to 20MHz to send signals in the 2GHz frequency band used in LTE.

[0050] In addition, mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. mMTC has requirements such as supporting the connection of a large number of UEs in a cell, enhancing the coverage of UEs, improving battery time, reducing the cost of UEs, etc., in order to effectively provide IoT. Since IoT provides a communication function while being provided to various sensors and various devices, it must support a large number of UEs in a cell (e.g., 1,000,000 UE / km 2 ). In addition, a UE supporting mMTC may require wider coverage than the coverage of other services provided by the 5G communication system because the UE may be located in a shadow area (such as a basement of a building) that is not covered by a cell due to the nature of the service. A UE supporting mMTC must be configured to be cheap and may require a very long battery life, such as 10 to 15 years, because it is difficult to frequently replace the battery of the UE.

[0051] Finally, URLLC, as a cell-based mission-critical wireless communication service, can be used for remote control of robots or machines, industrial automation, unmanned aerial vehicles, remote healthcare, emergency alerts, etc. Therefore, URLLC must provide communications with ultra-low latency and ultra-high reliability. For example, URLLC-enabled services must meet an air interface latency of less than 0.5 ms and also require 10 -5 Or a smaller packet error rate. Therefore, for services supporting URLLC, the 5G system must provide a shorter transmit time interval (TTI) than other services, and may also require a design for allocating a large amount of resources in the frequency band to ensure the reliability of the communication link.

[0052] The three services in 5G, namely eMBB, URLLC and mMTC, can be multiplexed and transmitted in a single system. In this case, different transmission / reception technologies and transmission / reception parameters can be used between services to meet the different requirements of the corresponding services. Of course, 5G is not limited to the three services described above.

[0053] [NR time-frequency resources]

[0054] Hereinafter, the frame structure of the 5G system will be described in more detail with reference to the accompanying drawings.

[0055] Figure 1 is a diagram showing a basic structure of a time-frequency domain, wherein the time-frequency domain is a radio resource domain for sending data or a control channel in a 5G system.

[0056] exist Figure 1In the , 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. A resource element 101 can be defined as one OFDM symbol 102 in the time domain and one subcarrier 103 in the frequency domain. In the frequency domain, (For example, 12) consecutive REs may configure a resource block (RB) 104 .

[0057] exist Figure 2 , an example of the structure of a frame 200, a subframe 201, and a time slot 202 is shown. One frame 200 may be defined as 10 ms. One subframe 201 may be defined as 1 ms, so one frame 200 may consist of a total of ten subframes 201. One time slot 202 or 203 may be defined as fourteen OFDM symbols (i.e., the number of symbols in one time slot). A subframe 201 may include one or more time slots 202 and 203, and the number of time slots 202 and 203 of each subframe 201 may be different according to the configured value μ 204 or 205 of the subcarrier spacing. Figure 2 In the example of FIG. 2 , the subcarrier spacing configuration values ​​are μ=0 (204) and μ=1 (205). If μ=0 (204), one subframe 201 may consist of one time slot 202, and if μ=1 (205), one subframe 201 may consist of two time slots 203. That is, the number of time slots in each subframe is The number of time slots per frame can be different depending on the subcarrier spacing configuration value μ. can be different. μ is configured according to each subcarrier spacing, and and It can be defined as in Table 1 below.

[0058] [Table 1]

[0059]

[0060] [Bandwidth Part (BWP)]

[0061] Next, the BWP configuration in the 5G communication system will be described in detail with reference to the accompanying drawings.

[0062] Figure 3 is a diagram illustrating an example of a configuration of a BWP in a wireless communication system according to an embodiment of the present disclosure.

[0063] exist Figure 3In FIG. 3 , an example is provided in which a UE bandwidth 300 is configured with two BWPs, namely BWP#1 301 and BWP#2 302. The base station may configure one or more BWPs for the UE, and may configure each BWP with information as shown in Table 2 below.

[0064] [Table 2]

[0065]

[0066] The above examples are not limiting, and in addition to the above configuration information, various parameters related to BWP may be configured in the UE. The above information may be sent by the base station to the UE via higher layer signaling (e.g., radio resource control (RRC) signaling). At least one of the configured one or more BWPs may be activated. Whether to activate the configured BWP may be semi-statically sent from the base station to the UE via RRC signaling or may be dynamically sent via downlink control information (DCI).

[0067] According to some embodiments, the UE may be configured with an initial BWP for initial access from a base station through a master information block (MIB) before RRC connection. Specifically, through the MIB in the initial access step, the UE may receive configuration information about the search space and the control resource set (CORESET), through which the PDCCH for receiving the system information required for initial access (which may correspond to the remaining system information (RMSI) or system information block 1 (SIB 1)) can be sent. The CORESET and search space configured through the MIB may be regarded as identity (ID) 0, respectively. The base station may notify the UE of the configuration information of the control resource set #0, such as frequency allocation information, time allocation information, and parameter set, through the MIB. In addition, the base station may notify the UE of the configuration information about the monitoring period and timing of the control resource set #0, that is, the configuration information about the search space #0, through the MIB. The UE may regard the frequency domain configured as the control resource set #0 obtained from the MIB as the initial BWP for initial access. Here, the ID of the initial BWP may be considered as zero.

[0068] Configuration of the BWP supported by 5G can be used for various purposes.

[0069] According to some embodiments, when the bandwidth supported by the UE is less than the system bandwidth, this can be supported by BWP configuration. For example, the base station configures the frequency position of the BWP in the UE (configuration information 2) so that the UE can send or receive data at a specific frequency position within the system bandwidth.

[0070] In addition, according to some embodiments, the base station may configure multiple BWPs in the UE for the purpose of supporting different parameter sets. For example, in order to support both data transmission / reception using a subcarrier spacing of 15 kHz and a subcarrier spacing of 30 kHz in a certain UE, two BWPs may be configured with a subcarrier spacing of 15 kHz and a subcarrier spacing of 30 kHz, respectively. Different BWPs may be frequency-division multiplexed, and when attempting to transmit or receive data with a specific subcarrier spacing, the BWP configured with the subcarrier spacing may be activated.

[0071] In addition, according to some embodiments, for the purpose of reducing the power consumption of the UE, the base station may configure a BWP with bandwidths of different sizes for the UE. For example, when the UE supports a very large bandwidth (e.g., a bandwidth of 100 MHz) and always sends or receives data at this bandwidth, the sending or receiving may cause very high power consumption in the UE. In particular, when the UE performs monitoring on an unnecessary downlink control channel with a large bandwidth of 100 MHz even when there is no business, the monitoring may be very inefficient in terms of power consumption. Therefore, in order to reduce the power consumption of the UE, the base station may configure a BWP with a relatively small bandwidth for the UE, for example, a BWP of 20 MHz. In the absence of business, the UE can perform monitoring operations on a BWP of 20 MHz, and when data has occurred, the UE can send or receive data in a BWP of 100 MHz according to the instructions of the base station.

[0072] In the method for configuring BWP, the UE may receive configuration information about the initial BWP through the MIB in the initial connection step before the RRC connection. Specifically, from the MIB of the physical broadcast channel (PBCH), the UE may be configured with a CORESET for a downlink control channel, through which a DCI for scheduling SIBs may be sent. The bandwidth of the control resource set configured through the MIB may be regarded as the initial BWP, and the UE may receive the PDSCH through which the SIBs are sent through the configured initial BWP. The initial BWP may be used for reception of other system information (OSI), paging and random access, and SIBs.

[0073] [Bandwidth Part (BWP) Switch]

[0074] When one or more BWPs have been configured for a UE, the base station may instruct the UE to change (or switch, transform) the BWP by using the bandwidth part indicator field in the DCI. Figure 3 In the present invention, when the currently activated BWP of the UE is BWP#1 301, the base station may indicate BWP#2 302 to the UE by using the BWP indicator in the DCI, and the UE may perform BWP switching to the BWP#2 302 indicated by the BWP indicator in the received DCI.

[0075] As described above, since the DCI-based BWP switching can be indicated by the DCI scheduling PDSCH or PUSCH, when receiving a request to switch BWP, the UE should be able to receive or send the PDSCH or PUSCH scheduled by DCI in the switched BWP without difficulty. To this end, the standard specifies the delay time (T BWP ) requirements, and it can be defined as in Table 3 below.

[0076] [Table 3]

[0077]

[0078] Depending on the UE capability, the requirement for BWP switching delay time supports type 1 or type 2. The UE can report the supportable BWP delay time type to the base station.

[0079] When the UE receives a DCI including a BWP switching indicator in time slot n according to the requirement for the BWP switching delay time, the UE can complete the switching to the new BWP indicated by the BWP switching indicator at a time no later than time slot n+TBWP, and can perform transmission and reception of the data channel scheduled by the corresponding DCI in the switched new BWP. When the base station intends to schedule the data channel to the new BWP, the base station can consider the BWP switching delay time (TBWP) of the UE. BWP ) to determine the time domain resource allocation for the data channel. That is, when scheduling the data channel to the new BWP, the base station may schedule the data channel after the BWP switching delay time in the method for determining the time domain resource allocation for the data channel. Therefore, the UE may not expect the DCI indicating the BWP switching to be less than T BWP The time slot offset (K0 or K2) value.

[0080] If the UE receives a DCI indicating a BWP switch (e.g., DCI format 1_1 or 0_1), the UE may not perform transmission or reception during a time interval from the third symbol of the slot in which the PDCCH including the DCI is received to the start time of the slot indicated by the slot offset (K0 or K2) value indicated by the time domain resource allocation indicator field in the DCI. For example, if the UE has received a DCI indicating a BWP switch in slot n and the slot offset value indicated by the DCI is K, the UE may not perform transmission or reception from the third symbol of slot n to the symbol before slot n+K (i.e., the last symbol of slot n+k-1).

[0081] [SS / PBCH block]

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

[0083] The SS / PBCH block may indicate a physical layer channel block consisting of a primary SS (PSS), a secondary SS (SSS) and a PBCH. Specifically, they are as follows:

[0084] -PSS: It is a signal used as a reference for downlink time / frequency synchronization and provides some information of cell ID.

[0085] -SSS: It is a signal used as a reference for downlink time / frequency synchronization and provides the remaining cell ID information not provided by PSS. In addition, it can be used as a reference signal for demodulating PBCH.

[0086] -PBCH: It provides necessary system information required for transmitting or receiving data channels and control channels of UEs. Necessary system information may include search space-related control information indicating radio resource mapping information of control channels, scheduling control information of a separate data channel for transmitting system information, etc.

[0087] -SS / PBCH block: It consists of a combination of PSS, SSS and PBCH. One or more SS / PBCH blocks can be sent within 5ms, and each SS / PBCH block sent can be distinguished by an index.

[0088] The UE may detect the PSS and SSS in the initial access step and may decode the PBCH. The UE may obtain the MIB from the PBCH and may be configured with CORESET#0 (which may correspond to a control resource set with CORESET index 0) therefrom. The UE may monitor control resource set #0 assuming that the demodulation reference signal (DMRS) sent in the selected SS / PBCH block and the control resource set #0 are quasi-co-located (QCLed). The UE may receive system information with downlink control information sent from control resource set #0. The UE may obtain configuration information related to the RACH required for initial access from the received system information. The UE may send a physical RACH (PRACH) to the base station by considering the selected SS / PBCH index, and the base station having received the PRACH may obtain information about the SS / PBCH block index selected by the UE. The base station may know which block the UE selects among the SS / PBCH blocks and may know that the control resource set #0 associated therewith is monitored.

[0089] [PDCCH: DCI related]

[0090] Next, DCI in the 5G system will be described in detail.

[0091] In the 5G system, scheduling information about uplink data (or physical uplink shared channel (PUSCH)) or downlink data (or physical downlink shared channel (PDSCH)) is sent from the base station to the UE via DCI. For PUSCH or PDSCH, the UE can monitor the fallback DCI format and the non-fallback DCI format. The fallback DCI format may include a fixed field predefined between the base station and the UE, and the non-fallback DCI format may include a configurable field.

[0092] The DCI may be sent via a physical downlink control channel (PDCCH) after channel coding and modulation are performed on it. A cyclic redundancy check (CRC) may be attached to the DCI message payload, and the CRC may be scrambled by a radio network temporary identifier (RNTI) corresponding to the identity of the UE. Different RNTIs may be used depending on the purpose of the DCI message (e.g., UE-specific data transmission, power adjustment commands, or random access responses). That is, the RNTI is not sent explicitly, but is included in the CRC calculation process and then sent. Upon receiving a DCI message sent via the PDCCH, the UE may check the CRC by using the assigned RNTI. When the CRC check result is correct, the UE may know that the corresponding message has been sent to the UE.

[0093] For example, the DCI used to schedule PDSCH for system information (SI) can be scrambled by SI-RNTI. The DCI used to schedule PDSCH for random access response (RAR) message can be scrambled by RA-RNTI. The DCI used to schedule PDSCH for paging message can be scrambled by P-RNTI. The DCI used to notify the slot format indicator (SFI) can be scrambled by SFI-RNTI. The DCI used to notify transmit power control (TPC) can be scrambled by TPC-RNTI. The DCI used to schedule UE-specific PDSCH or PUSCH can be scrambled by cell RNTI (cell RNTI, C-RNTI).

[0094] DCI format 0_0 may be used as a fallback DCI for scheduling PUSCH. Here, CRC may be scrambled by C-RNTI. DCI format 0_0 in which CRC is scrambled by C-RNTI may include the following information, for example, in Table 4.

[0095] [Table 4]

[0096]

[0097]

[0098] DCI format 0_1 ​​may be used as a non-fallback DCI for scheduling PUSCH. Here, CRC may be scrambled by C-RNTI. DCI format 0_1 ​​in which CRC is scrambled by C-RNTI may include the following information, for example, in Table 5.

[0099] [Table 5]

[0100]

[0101]

[0102] DCI format 1_0 may be used as a fallback DCI for scheduling PDSCH. Here, CRC may be scrambled by C-RNTI. DCI format 1_0 in which CRC is scrambled by C-RNTI may include the following information, for example, in Table 6.

[0103] [Table 6]

[0104]

[0105]

[0106] DCI format 1_1 may be used as a non-fallback DC for scheduling PDSCH. Here, CRC may be scrambled by C-RNTI. DCI format 1_1 in which CRC is scrambled by C-RNTI may include, for example, the following information.

[0107] [Table 7]

[0108]

[0109]

[0110] [PDCCH: CORESET, REG, CCE, search space]

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

[0112] Figure 4 is a diagram showing an example of a control resource set (CORESET) in which a downlink control channel is transmitted in a 5G wireless communication system. Figure 4An example is shown in which a UE BWP 410 is configured in the frequency domain and two CORESETs (CORESET #1 401 and CORESET #2 402) are configured in the time domain within a time slot 420. CORESETs 401 and 402 may be configured in specific frequency resources 403 within the entire UE BWP 410 in the frequency domain. One or more OFDM symbols may be configured in the time domain and defined as a control resource set duration 404. Figure 4 In the example shown, CORESET#1 401 is configured with a control resource set duration of two symbols, and CORESET#2 402 is configured with a control resource set duration of one symbol.

[0113] The CORESET described above in 5G can be configured for the UE by the base station via higher layer signaling (e.g., system information (SI), master information block (MIB), radio resource control (RRC) signaling). Configuring the CORESET for the UE means providing information such as the CORESET identity, the frequency position of the CORESET, the symbol length of the CORESET, etc. For example, it may include the following information in Table 8.

[0114] [Table 8]

[0115]

[0116] In Table 8, the tci-StatesPDCCH (abbreviated as transmission configuration indication (TCI) state) configuration information may include information about one or more synchronization signal / physical broadcast channel (SS / PBCH) block indices or channel state information reference signal (CSI-RS) indices that have a QCL relationship with the DMRS sent in the corresponding CORESET.

[0117] Figure 5 : is a diagram showing an example of a basic unit for configuring time and frequency resources of a downlink control channel that can be used in 5G. Figure 5 The basic unit for configuring the time and frequency resources of the control channel may be referred to as a resource element group (REG) 503, which may be defined as one OFDM symbol 501 in the time domain and one physical resource block (PRB) 502 in the frequency domain, i.e., 12 subcarriers. The base station may cascade REGs 503 to configure a downlink control channel allocation unit.

[0118] like Figure 5As shown, when the basic unit for allocating downlink control channels in 5G is called a control channel element (CCE) 504, a CCE 504 can be composed of multiple REGs 503. Figure 5 In the example shown, REG 503 may include 12 REs, and when one CCE 504 is composed of six REGs 503, one CCE 504 may include 72 REs. When a downlink CORESET is configured, it may include multiple CCEs 504. A specific downlink control channel may be transmitted after being mapped to one or more CCEs 504 according to an aggregation level (AL) in the CORESET. The CCEs 504 in the CORESET are distinguished by numbering. Here, the numbers of the CCEs 504 may be assigned according to a logical mapping scheme.

[0119] Figure 5 The basic unit of the downlink control channel shown in FIG. 5 , that is, REG 503 may include both REs to which DCI is mapped and regions to which DMRS 505 as a reference signal for decoding DCI is mapped. Figure 5 As shown, three DMRS 505 can be sent in one REG 503. Depending on the AL, the number of CCEs required for the transmission of the PDCCH can be 1, 2, 4, 8 or 16. Different numbers of CCEs can be used to achieve link adaptation of the downlink control channel. For example, if AL=L, one downlink control channel can be sent by L CCEs. The UE needs to detect the signal in a state where the UE does not know information about the downlink control channel, and a search space representing a set of CCEs has been provided for blind decoding. The search space is a set of downlink control channel candidates including CCEs that the UE must attempt to decode with a given AL. Since there are various ALs that constitute a bundle of 1, 2, 4, 8 or 16 CCEs, the UE can have multiple search spaces. A search space set can be defined as a set of search spaces with all configured ALs.

[0120] The search space can be classified into a common search space and a UE-specific search space. A predetermined group of UEs or all UEs can check the common search space of the PDCCH in order to receive cell common control information, such as dynamic scheduling of system information or paging messages. For example, PDSCH scheduling allocation information for the transmission of SIBs including cell operator information, etc. can be received by checking the common search space of the PDCCH. In the case of a common search space, since a predetermined group of UEs or all UEs need to receive the PDCCH, the common search space can be provided as a set of previously specified CCEs. Scheduling allocation information about UE-specific PDSCH or PUSCH can be received by checking the UE-specific search space of the PDCCH. The UE-specific search space can be provided UE-specifically as a function of the UE identity and various system parameters.

[0121] In 5G, the parameters of the search space for PDCCH can be configured for the UE by the base station via higher layer signaling (e.g., SIB, MIB, RRC signaling, etc.). For example, the base station can configure the number of PDCCH candidates per aggregation level L, the monitoring period of the search space, the monitoring timing of the symbol unit in the time slot of the search space, the search space type (common search space or UE-specific search space), the combination of RNTI and DCI format to be monitored in the search space, the control resource set index of the monitoring search space, etc. For example, it can include the following information in Table 9.

[0122] [Table 9]

[0123]

[0124]

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

[0126] According to the configuration information, one or more search space sets may exist in a common search space or a UE-specific search space. For example, search space set #1 and search space set #2 may be configured as common search spaces, and search space set #3 and search space set #4 may be configured as UE-specific search spaces.

[0127] In the common search space, the following combinations of DCI formats and RNTIs may be monitored. However, the present disclosure is not limited to the following.

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

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

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

[0131] -DCI format 2_2 with CRC scrambled by TPC-PUSCH-RNTI, TPC-PUCCH-RNTI

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

[0133] In the UE-specific search space, the following combinations of DCI formats and RNTIs may be monitored. However, the present disclosure is not limited to the following.

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

[0135] -DCI format 1_0 / 1_1 with CRC scrambled by C-RNTI, CS-RNTI, TC-RNTI specifies that the RNTI may follow the definition and usage described below.

[0136] -Cell RNTI (C-RNTI): used for UE-specific PDSCH scheduling

[0137] -Temporary Cell RNTI (TC-RNTI): used for UE-specific PDSCH scheduling

[0138] -Configured Scheduling RNTI (CS-RNTI): used for semi-statically configured UE-specific PDSCH scheduling

[0139] - Random Access RNTI (RA-RNTI): used for PDSCH scheduling in random access operation

[0140] - Paging RNTI (P-RNTI): used to schedule the PDSCH through which paging is sent

[0141] - System Information RNTI (SI-RNTI): used for PDSCH scheduling where system information is sent

[0142] -Interruption RNTI (INT-RNTI): used to notify whether to puncture the PDSCH.

[0143] - Transmit Power Control for PUSCH RNTI (TPC-PUSCH-RNTI): Indication of power control commands for PUSCH

[0144] - Transmit Power Control for PUCCH RNTI (TPC-PUCCH-RNTI): Indication of power control commands for PUCCH

[0145] - Transmit Power Control for SRS RNTI (TPC-SRS-RNTI): Indication of power control command for SRS

[0146] The specified DCI format described above may follow the definition in Table 10.

[0147] [Table 10]

[0148]

[0149] In 5G, the search space of aggregation level L in CORESET p and search space set s can be expressed by the following Equation 1.

[0150] [Equation 1]

[0151]

[0152] –L: aggregation level

[0153] –n Cl : Carrier index

[0154] –N CCE,p : The total number of CCEs present in CORESET p

[0155] –n s,f μ : Time slot index

[0156] –Ms,max (L) : The number of PDCCH candidates at aggregation level L

[0157] –m s,nCl =0, ..., M s,max (L) -1: PDCCH candidate group index of aggregation level L

[0158] –i=0,…,L-1

[0159] –Y p,ns,fμ =(A p ·Y p,ns,fμ-1 )mod D,Y p,-1 =n RNTI ≠0, A 0 =39827, A 1 =39829, A 2 =39839, D=65537

[0160] –n RNTI : UE identifier

[0161] In the case of a public search space, Y p,ns,fμ The value may correspond to zero.

[0162] In the case of UE-specific search space, Y p,ns,fμ The value may correspond to a value that changes according to the UE identity (C-RNTI or ID configured by the base station for the UE) and the time index.

[0163] In 5G, multiple search space sets can be configured with different parameters (e.g., the parameters in Table 9), so the set of search space sets monitored by the UE can be different at each time point. For example, if search space set #1 is configured with an X time slot period, search space set #2 is configured with a Y time slot period, and X and Y are different, the UE can monitor both search space set #1 and space set #2 in a specific time slot, and can monitor one of search space set #1 and search space set #2 in a specific time slot.

[0164] Figure 6 is a diagram illustrating a method in which a base station and a UE perform data transmission / reception by considering a downlink data channel and a rate matching resource according to an embodiment of the present disclosure.

[0165] exist Figure 6In the embodiment of the present invention, a downlink data channel (PDSCH) 601 and a rate matching resource 602 are provided. The base station may configure one or more rate matching resources 602 in the UE through higher layer signaling (e.g., RRC signaling). The configuration information of the rate matching resource 602 may include time domain resource allocation information 603, frequency domain resource allocation information 604, and periodicity information 605. In the following description, the bit mapping corresponding to the frequency domain resource allocation information 604 is referred to as "first bit mapping", the bit mapping corresponding to the time domain resource allocation information 603 is referred to as "second bit mapping", and the bit mapping corresponding to the periodicity information 605 is referred to as "third bit mapping". If some or all of the time and frequency resources of the scheduled data channel 601 overlap with the configured rate matching resource 602, the base station may rate match the data channel 601 in the rate matching resource 602 and transmit the data channel 601. The UE may perform data reception and decoding after assuming that the data channel 601 has been rate matched in the rate matching resource 602.

[0166] The base station can dynamically notify the UE via DCI whether the data channel will be rate matched in the configured rate matching resources by additional configuration (corresponding to the "rate matching indicator" in the DCI format described above). Specifically, the base station can select some of the configured rate matching resources, group the selected resources into rate matching resource groups, and use a bit mapping method to indicate to the UE via DCI whether the data channel has been rate matched with each rate matching resource group. For example, when four rate matching resources RMR#1, RMR#2, RMR#3 and RMR#4 have been configured, the base station can configure RMG#1={RMR#1, RMR#2} and RMG#2={RMR#3, RMR#4} as rate matching groups, and can indicate to the UE in the form of bit mapping whether rate matching in each of RMG#1 and RMG#2 has been performed using 2 bits of the DCI field. For example, if rate matching needs to be performed, the base station can indicate "1", and if rate matching does not need to be performed, it can indicate "0".

[0167] 5G supports the granularity of "RB symbol level" and "RE level" as a method of configuring the rate matching resources described above in the UE. Specifically, the following configuration method can be followed.

[0168] RB symbol level

[0169] The UE may be configured with up to four RateMatchPatterns for each BWP via higher layer signaling, and one RateMatchPatterns may include the following.

[0170] - The reserved resources in the BWP may include resources, wherein the time and frequency resource regions corresponding to the reserved resources are configured as a combination of RB level bitmap and symbol level bitmap on the frequency axis. The reserved resources may span one or two time slots. The UE may additionally be configured with a time domain pattern (periodicityAndPattern), wherein the time-frequency domain including a pair of RB level and symbol level bitmaps is repeated.

[0171] - may include a time-frequency domain resource region configured as CONRESET in the BWP and a resource region corresponding to a time domain pattern configured as a search space configuration in which the resource region is repeated.

[0172] RE Level

[0173] The UE may be configured with the following information through higher layer signaling.

[0174] - may include the number of LTE CRS ports (nrofCRS-Ports) and LTE-CRS-vshift (or multiple) values ​​(v-shift) as configuration information (lte-CRS-ToMatchAround) of REs corresponding to an LTE cell-specific reference signal or a common reference signal (CRS) pattern, center subcarrier position information (carrierFreqDL) of an LTE carrier from a reference frequency point (e.g., reference point A), bandwidth size (carrierBandwidthDL) information of an LTE carrier, subframe configuration information (mbsfn-SubframConfigList) corresponding to a multicast-broadcast single-frequency network (MBSFN), etc. The UE may determine the position of the CRS in the NR time slot corresponding to the LTE subframe based on the above-described information.

[0175] - May include configuration information for resource sets corresponding to one or more zero-power (ZP) CSI-RS in a bandwidth portion.

[0176] [PDSCH: frequency domain resource allocation related]

[0177] Figure 7 is a diagram illustrating an example of frequency domain resource allocation of a physical downlink shared channel (PDSCH) in a wireless communication system according to an embodiment of the present disclosure.

[0178] Figure 7Three frequency domain resource allocation methods of type 0 (7-00), type 1 (7-05), and dynamic switch (7-10) configurable by a higher layer in an NR wireless communication system are shown.

[0179] refer to Figure 7 , if the UE is configured to use only resource type 0 (7-00) via higher layer signaling, some downlink control information (DCI) for allocating PDSCH to the corresponding UE includes a bitmap formed by NRBG bits. Its conditions will be described again later. Here, NRBG represents the number of resource block groups (RBGs) determined according to the BWP size allocated by the BWP indicator and the higher layer parameter rbg-Size, as shown in Table 11 below, and data is sent to the RBG indicated as "1" in the bitmap.

[0180] [Table 11]

[0181] Bandwidth portion size Configuration 1 Configuration 2 1-36 2 4 37-72 4 8 73-144 8 16 145-275 16 16

[0182] If the UE is configured via higher layer signaling to use only resource type 1 (7-05), some DCI for allocating PDSCH to the UE includes The frequency domain resource allocation information configured with bits. The conditions will be described again later. Thus, the base station can configure the length of the starting VRB 7-20 and the frequency domain resources 7-25 continuously allocated therefrom.

[0183] If the UE is configured to use both resource type 0 and resource type 1 (7-10) via higher layer signaling, some DCI for allocating PDSCH to the UE includes frequency domain resource allocation information configured by a payload 7-15 for configuring resource type 0 and a bit 7-35 of a larger value of a payload 7-20 and 7-25 for configuring resource type 1. Its conditions will be described again later. Here, one bit is added to the most significant bit (MSB) of the frequency domain resource allocation information in the DCI, and if the corresponding bit has a value of "0", it indicates that resource type 0 is used, and if the corresponding bit has a value of "1", it indicates that resource type 1 is used.

[0184] [PDSCH / PUSCH: Time domain resource allocation related]

[0185] Hereinafter, a method of allocating time domain resources to a data channel in a next-generation mobile communication system (5G or NR system) will be described.

[0186] The base station may configure a table of time domain resource allocation information for a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH) for the UE via higher layer signaling (e.g., RRC signaling). For PDSCH, a table including maxNrofDL-Allocations=16 entries may be configured, and for PUSCH, a table including maxNrofUL-Allocations=16 entries may be configured. In an embodiment, the time domain resource allocation information may include PDCCH to PDSCH slot timing (corresponding to the time interval in time slots between the time point of receiving the PDCCH and the time point of sending the PDSCH scheduled by the received PDCCH, and represented by K0), PDCCH to PUSCH slot timing (corresponding to the time interval in time slots between the time point of receiving the PDCCH and the time point of sending the PUSCH scheduled by the received PDCCH, and represented by K2), information about the position and length of the starting symbol scheduled for PDSCH or PUSCH in the time slot, the mapping type of PDSCH or PUSCH, etc. For example, information such as the following Table 12 or Table 13 may be sent from the base station to the UE.

[0187] [Table 12]

[0188]

[0189] [Table 13]

[0190]

[0191]

[0192] The base station may notify the UE via L1 signaling (e.g., DCI) of one of the entries in the table described above that represents the time domain resource allocation information (e.g., may be indicated by the "time domain resource allocation" field in the DCI). The UE may acquire the time domain resource allocation information for the PDSCH or PUSCH based on the DCI received from the base station.

[0193] Figure 8 is a diagram illustrating an example of time domain resource allocation of a PDSCH in a wireless communication system according to an embodiment of the present disclosure.

[0194] refer to Figure 8 , the base station can use the subcarrier spacing (SCS) (μ PDSCH ,μ PDCCH) and a scheduling offset (K0) value configured by a higher layer to indicate the time domain position of the PDSCH resource, as well as the starting position 8-00 and length 8-05 of an OFDM symbol in a time slot dynamically indicated via DCI.

[0195] Fig. 9 is a diagram illustrating an example of time domain resource allocation based on subcarrier spacing of a data channel and a control channel in a wireless communication system according to an embodiment of the present disclosure.

[0196] refer to Fig. 9 , the data channel and the control channel have the same subcarrier spacing (μ PDSCH =μ PDCCH ), the timeslot numbers for data and control are the same, so that the base station and the UE can generate a scheduling offset according to the predetermined timeslot offset K0. On the other hand, when the data channel and the control channel have different subcarrier spacings (μ PDSCH ≠μ PDCCH ) in case 9-05, the time slot numbers used for data and control are different, so that the base station and UE can generate a scheduling offset according to a predetermined time slot offset K0 based on the subcarrier spacing of the PDCCH.

[0197] [PUSCH: Transmission scheme related]

[0198] Next, the scheduling scheme for PUSCH transmission will be described. PUSCH transmission may be dynamically scheduled by UL grant in DCI, or may be operated by configured grant type 1 or type 2. Dynamic scheduling indication for PUSCH transmission is possible using DCI format 0_0 or 0_1.

[0199] A configured grant type 1 PUSCH transmission does not receive an UL grant in the DCI and may be semi-statically configured by receiving a configuredGrantConfig including rrc-ConfiguredUplinkGrant of Table 14 via higher layer signaling. A configured grant type 2 PUSCH transmission may be semi-persistently scheduled by an UL grant in the DCI after receiving a configuredGrantConfig not including rrc-ConfiguredUplinkGrant of Table 14 via higher layer signaling. When a PUSCH transmission is operated by a configured grant, the parameters applied to the PUSCH transmission are applied by configuredGrantConfig as higher layer signaling, in addition to the scaling of dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, and UCI-OnPUSCH provided by pusch-Config of Table 15 as higher layer signaling. If the UE is provided with transformPrecoder in configuredGrantConfig as higher layer signaling of Table 14, the UE applies tp-pi2BPSK in pusch-Config of Table 15 for PUSCH transmission operated by the configured grant.

[0200] [Table 14]

[0201]

[0202]

[0203]

[0204]

[0205] Next, the PUSCH transmission method will be described. The DMRS antenna port used for PUSCH transmission is the same as the antenna port used for SRS transmission. PUSCH transmission can be based on a codebook-based transmission method and a non-codebook-based transmission method, respectively, depending on whether the value of txConfig in pusch-Config of Table 15 as higher layer signaling is "codebook" or "nonCodebook".

[0206] As above, PUSCH transmission can be dynamically scheduled through DCI format 0_0 or 0_1, and can be semi-statically configured through the configured grant. If the UE is instructed to schedule PUSCH transmission through DCI format 0_0, the UE performs beam configuration of PUSCH transmission by using the pucch-spatialRelationInfoID corresponding to the UE-specific PUCCH resource corresponding to the minimum ID in the uplink BWP activated in the serving cell, and here, the PUSCH transmission is based on a single antenna port. The UE does not expect to schedule PUSCH transmission through DCI format 0_0 within a BWP in which a PUCCH resource including pucch-spatialRelationInfo is not configured. If the UE is not configured with txConfig in pusch-Config of Table 15, the UE does not expect to be scheduled with DCI format 0_1.

[0207] [Table 15]

[0208]

[0209]

[0210]

[0211] Next, codebook-based PUSCH transmission will be described. Codebook-based PUSCH transmission can be dynamically scheduled by DCI format 0_0 or 0_1, and can be semi-statically operated by a configured grant. When codebook-based PUSCH is dynamically scheduled by DCI format 0_1 ​​or semi-statically configured by a configured grant, the UE determines the precoder for PUSCH transmission based on the SRS resource indicator (SRSresource indicator, SRI), the transmission precoding matrix indicator (transmission precoding matrixindicator, TPMI) and the transmission rank (the number of PUSCH transmission layers).

[0212] Here, the SRI may be given by the field SRS resource indicator in the DCI, or may be configured by srs-ResourceIndicator as a higher layer signaling. The UE is configured with at least one SRS resource when sending a codebook-based PUSCH, and may be configured with up to two SRS resources. When the UE is provided with SRI through DCI, the SRS resource indicated by the corresponding SRI represents the SRS resource corresponding to the SRI among the SRS resources sent before the PDCCH including the corresponding SRI. In addition, the TPMI and the transmission rank may be given by the field precoding information and the number of layers in the DCI, or may be configured by precodingAndNumberOfLayers as a higher layer signaling. The TPMI is used to indicate the precoder applied to the PUSCH transmission. If the UE is configured with one SRS resource, the TPMI is used to indicate the precoder to be applied in one configured SRS resource. If the UE is configured with multiple SRS resources, the TPMI is used to indicate the precoder to be applied in the SRS resource indicated by the SRI.

[0213] A precoder to be used for PUSCH transmission is selected from an uplink codebook having the same number of antenna ports as the value of nrofSRS-Ports in SRS-Config as higher layer signaling. In codebook-based PUSCH transmission, the UE determines the codebook subset based on the TPMI and codebookSubset in pusch-Config as higher layer signaling. CodebookSubset in pusch-Config as higher layer signaling can be configured with 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 the UE capability, the UE does not expect the value of codebookSubset as higher layer signaling to be configured as "fullyAndPartialAndNonCoherent". In addition, if the UE reports "nonCoherent" as the UE capability, the UE does not expect the value of codebookSubset as higher layer signaling to be configured as "fullyAndPartialAndNonCoherent" or "partialAndNonCoherent". When nrofSRS-Ports in SRS-ResourceSet as higher layer signaling indicates two SRS antenna ports, the UE does not expect the value of codebookSubset as higher layer signaling to be configured as "partialAndNonCoherent".

[0214] The UE may be configured with one SRS resource set (wherein the used value in SRS-ResourceSet as higher layer signaling is configured as "codebook"), and one SRS resource in the corresponding SRS resource set may be indicated by SRI. If multiple SRS resources are configured in an SRS resource set in which the used value in SRS-ResourceSet as higher layer signaling is configured as "codebook", the UE expects that the value of nrofSRS-Ports in SRS-Resource as higher layer signaling is configured as the same value relative to all SRS resources.

[0215] The UE sends one or more SRS resources included in the SRS resource set to the base station (wherein the value used is configured as a "codebook" according to higher layer signaling), and the base station instructs the UE to perform PUSCH transmission by selecting one of the SRS resources sent by the UE and using the transmit beam information of the corresponding SRS resource. Here, in the codebook-based PUSCH transmission, SRI is used as information for selecting an index of an SRS resource and is included in the DCI. In addition, the base station includes information indicating the rank and TPMI to be used by the UE for PUSCH transmission in the DCI. The UE performs PUSCH transmission by using the SRS resource indicated by the SRI and applying the rank indicated by the transmission beam of the SRS resource and the precoder indicated by the TPMI.

[0216] Next, non-codebook based PUSCH transmission will be described. Non-codebook based PUSCH transmission can be dynamically scheduled through DCI format 0_0 or 0_1, and can be semi-statically operated by the configured grant. When at least one SRS resource is configured in the SRS resource set in which the used value in the SRS-ResourceSet as higher layer signaling is configured as "nonCodebook", the UE can be scheduled using non-codebook based PUSCH transmission through DCI format 0_1.

[0217] For an SRS resource set in which the used value in the SRS-ResourceSet as higher layer signaling is configured as "nonCodebook", the UE may be configured with a connected non-zero power CSI-RS (NZP CSI-RS) resource. The UE may perform calculation of 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 aperiodic NZP CSI-RS resource connected to the SRS resource set and the first symbol of the aperiodic SRS transmission in the UE is less than 42 symbols, the UE does not expect the information about the precoder for SRS transmission to be updated.

[0218] When the value of resourceType in SRS-ResourceSet as higher layer signaling is configured as "non-periodic", the connected NZP CSI-RS is indicated by an SRS request, where the SRS request is a field in DCI format 0_1 ​​or 1_1. Here, if the connected NZP CSI-RS resource is a non-periodic NZP CSI-RS resource, the connected NZP CSI-RS exists when the value of the SRS request field in DCI format 0_1 ​​or 1_1 is not "00". In this case, the DCI should not indicate cross-carrier or cross-BWP scheduling. In addition, if the value of the SRS request indicates the presence of NZP CSI-RS, the corresponding NZP CSI-RS is located in the time slot in which the PDCCH including the SRS request field is sent. Here, the TCI state configured via the scheduled subcarrier is not configured as QCL-TypeD.

[0219] If a periodic or semi-persistent SRS resource set is configured, the connected NZP CSI-RS can be indicated by the associated CSI-RS in the SRS-ResourceSet as higher layer signaling. For non-codebook based transmission, the UE does not expect the spatialRelation information (which is higher layer signaling for SRS resources) to be configured together with the associated CSI-RS in the SRS-ResourceSet (which is higher layer signaling).

[0220] When the UE is configured with multiple SRS resources, the UE can determine the precoder and transmission rank to be applied to the PUSCH transmission based on the SRI indicated by the base station. Here, the SRI can be indicated by the field SRS resource indicator in the DCI, or can be configured by the srs-ResourceIndicator as a higher layer signaling. As in the codebook-based PUSCH transmission described above, when the UE is provided with SRI through DCI, the SRS resource indicated by the SRI represents the SRS resource corresponding to the SRI among the SRS resources sent before the PDCCH including the SRI. The UE can use one or more SRS resources for SRS transmission, and the maximum number of SRS resources that can be sent simultaneously in the same symbol in one SRS resource set is determined by the UE capability reported by the UE to the base station. Here, the SRS resources sent simultaneously by the UE occupy the same RB. The UE configures an SRS port for each SRS resource. Only one SRS resource set in which a used value in SRS-ResourceSet as higher layer signaling is configured as "nonCodebook" can be configured, and up to four SRS resources for non-codebook based PUSCH transmission can be configured.

[0221] The base station sends an NZP-CSI-RS connected to the SRS resource set to the UE, and the UE performs calculation of the precoder to be used for the transmission of one or more SRS resources in the corresponding SRS resource set based on the measurement result when receiving the NZP-CSI-RS. When sending one or more SRS resources in the SRS resource set configured as "nonCodebook" is used, the UE applies the calculated precoder to the base station, and the base station selects one or more SRS resources from the received one or more SRS resources. In this case, in the non-codebook based PUSCH transmission, the SRI indication is able to represent an index of one or a combination of multiple SRS resources, and the SRI is included in the DCI. Here, the number of SRS resources indicated by the SRI sent by the base station can be the number of transmission layers of the PUSCH, and the UE performs PUSCH transmission by applying the precoder applied to the SRS resource transmission to each layer.

[0222] [CA / DC related]

[0223] Fig.10 is a diagram illustrating a radio protocol structure of a base station and a UE in cases of a single cell, carrier aggregation, and dual connectivity in a wireless communication system according to an embodiment of the present disclosure.

[0224] refer to Fig.10 For each of the UE and the NR base station, the radio protocols of the next-generation mobile communication system include NR service data adaptation protocol (NR SDAP) S25 and S70, NR packet data convergence protocol (NR PDCP) S30 and S65, NR radio link control (NR radio link control, NR RLC) S35 and S60, and NR medium access control (NR MAC) S40 and S55.

[0225] The features of NRSPAP S25 and S70 may include some of the following features

[0226] -Transmission of user plane data

[0227] - Mapping between quality of service (QoS) flows and data bearers (DRBs) for both DL and UL

[0228] - Mark QoS flow ID in both DL and UL packets

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

[0230] For SDAP layer devices, the UE can be configured via an RRC message regarding whether to use the header of the SDAP layer device or whether to use the function of the SDAP layer device according to each PDCP layer device, each bearer or each logical channel. If the SDAP header is configured, the UE can be instructed by a one-bit NAS reflective QoS indicator (NAS reflective QoS) and a one-bit AS reflective QoS indicator (AS reflective QoS) of the SDAP header to update or reconfigure the mapping information between the data bearers and QoS flows of the uplink and downlink. The SDAP header may include QoS flow ID information indicating QoS. QoS information can be used as data processing priority for supporting smooth services or scheduling information, etc.

[0231] The functions of NRPDCP S30 and S65 may include some of the following functions:

[0232] -Header compression and decompression: only robust header compression (ROHC)

[0233] -Transmission of user data

[0234] - In-sequence delivery of higher layer PDUs

[0235] - Out-of-sequence delivery of higher layer PDUs

[0236] - Reordering of received PDCP PDUs

[0237] - Duplicate detection of lower layer service data units (SDUs)

[0238] -Retransmission of PDCP SDU

[0239] -Encryption and decryption

[0240] - Timer-based SDU discard in uplink

[0241] In the above, the reordering function of the NR PDCP device indicates a function of sequentially reordering PDCP PDUs received from a lower layer based on a PDCP sequence number (SN), and may include a function of transmitting data to a higher layer in a reordered order. Alternatively, the reordering function of the NR PDCP device may include a function of transmitting data without considering a sequence, a function of reordering a sequence and recording lost PDCP PDUs, a function of providing a status report on lost PDCP PDUs to a transmitting side, and a function of requesting retransmission of lost PDCP PDUs.

[0242] The functions of NR RLC S35 and S60 may include some of the following functions:

[0243] -Transmission of upper layer PDUs

[0244] - In-sequence delivery of higher layer PDUs

[0245] - Out-of-sequence delivery of higher layer PDUs

[0246] - Error correction via ARQ

[0247] - Concatenation, segmentation and reassembly of RLC SDU

[0248] - Re-segmentation of RLC data PDUs

[0249] - Reordering of RLC data PDUs

[0250] - Duplicate detection

[0251] -Protocol error detection

[0252] -RLC SDU discarded

[0253] -RLC re-establishment

[0254] The in-sequence delivery function of the NR RLC device indicates a function of sending the RLC SDU received from the lower layer to the higher layer in the order of reception. The in-sequence delivery function of the NR RLC device may include: a function of reassembling and sending multiple RLC SDUs (if initially one RLC SDU is segmented into multiple RLC SDUs and received), a function of reordering the received RLC PDUs based on the RLC SN or PDCP SN, a function of reordering the sequence and recording the lost RLC PDUs, a function of providing a status report on the lost RLC PDUs to the transmitting side, and a function of requesting retransmission of the lost RLC PDUs. If a lost RLC SDU occurs, the in-sequence delivery function of the NR RLC device may include the following functions: only the RLC SDUs before the lost RLC SDU are sent to the higher layer in sequence, or if a predetermined timer expires despite the existence of a lost RLC SDU, all RLC SDUs received before the start of the timer are sent to the higher layer in sequence. Alternatively, the in-sequence delivery function of the NR RLC device may include the following functions: if a predetermined timer expires despite the existence of a lost RLC SDU, all RLC SDUs received so far are sent to the higher layer in sequence. In addition, the RLC PDUs may be processed in the order in which the RLC PDUs are received (in the order of arrival, regardless of the order of the sequence number and the sequence number) and may be sent to the PDCP device without in-sequence delivery. In the case of segmentation, the in-sequence delivery function may include the following functions: receiving segments stored in a buffer or segments to be received later, reconfiguring the segments in a complete RLC PDU, processing the RLC PDU, and sending the RLC PDU to the PDCP device. The NR RLC layer may not include a cascading function, and the cascading function may be performed by the NR MAC layer or may be replaced by a multiplexing function of the NR MAC layer.

[0255] In the above, the out-of-sequence delivery function of the NRR LC device indicates a function of directly sending the RLC SDU received from the lower layer to the higher layer regardless of the order, and may include a function of reassembling multiple RLC SDUs and sending them (if originally one RLC SDU was segmented into multiple RLC SDUs and received), and a function of storing the RLC SN or PDCP SN of the received RLC PDU, reordering the sequence and recording the lost RLC PDU.

[0256] NR MAC S40 and S55 may be connected to multiple NR RLC layer devices configured in one UE, and the functions of NR MAC may include some of the following functions:

[0257] - Mapping between logical channels and transport channels

[0258] -Multiplexing / demultiplexing of MAC SDU

[0259] -Dispatch information report

[0260] - Error correction through HARQ

[0261] - Priority handling between logical channels of a UE

[0262] - Prioritization between UEs with the help of dynamic scheduling

[0263] -Multimedia broadcast service (MBMS) logo

[0264] -Transmission format selection

[0265] -filling

[0266] The NRPHY layers S45 and S50 may perform the following operations: channel coding and modulating higher layer data, generating higher layer data into OFDM symbols, transmitting the OFDM symbols via a radio channel, or demodulating and channel decoding OFDM symbols received via a radio channel, and transmitting the OFDM symbols to a higher layer.

[0267] The detailed structure of the radio protocol structure described above may be changed differently depending on the carrier (or cell) management method. For example, when the base station performs data transmission based on a single carrier (or cell) to the UE, the base station and the UE use a protocol structure having a single structure for each layer, such as S00. On the other hand, when the base station sends data to the UE based on carrier aggregation (CA) using multiple carriers in a single TRP, the base station and the UE have a single structure up to the RLC but use a protocol structure that multiplexes the PHY layer through the MAC layer, such as S10. As another example, when the base station sends data to the UE based on dual connectivity (DC) using multiple carriers in multiple TRPs, the base station and the UE have a single structure up to the RLC, but use a protocol structure that multiplexes the PHY layer through the MAC layer, such as S20.

[0268] Referring to the above description related to PDCCH and beam configuration, since PDCCH repetition transmission is not currently supported in Rel-15 and Rel-16 NR, it is difficult to achieve the required reliability in scenarios requiring high reliability (such as URLLC). The present disclosure proposes a method for improving the PDCCH reception reliability of a UE by providing a PDCCH repetition transmission method through multiple transmission points (TRP). The specific method is described in detail in the following embodiments.

[0269] Now, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The present disclosure is applicable to both FDD (frequency division duplex) and TDD systems. Hereinafter, in the present disclosure, higher signaling (or higher layer signaling) is a signal transmission method for sending data from a base station to a UE using a downlink data channel of a physical layer or sending data from a UE to a base station using an uplink data channel of a physical layer, and may be referred to as RRC signaling, PDCP signaling, or a medium access control (MAC) control element (CE) (MAC CE).

[0270] In determining whether coordinated communication is applied, the UE may use various methods, such as a method in which a PDCCH (or multiple) for allocating a PDSCH to which coordinated communication is applied has a specific format, a method in which a PDCCH (or multiple) for allocating a PDSCH to which coordinated communication is applied includes a specific indicator for notifying whether coordinated communication is applied, a method in which a PDCCH (or multiple) for allocating a PDSCH to which coordinated communication is applied is scrambled by a specific RNTI, or a method in which it is assumed that coordinated communication is applied in a specific segment indicated by a higher layer. Hereinafter, for ease of description, a case in which the UE receives a PDSCH to which coordinated communication is applied based on conditions similar to those described above will be referred to as an NC-JT case.

[0271] Hereinafter, determining the priority between A and B refers to selecting one with a higher priority to perform an operation corresponding thereto, or omitting (or discarding) the operation of the other with a lower priority according to a predetermined priority rule.

[0272] The above examples will be described below through multiple embodiments, but they are not independent, and such implementation methods can be applied simultaneously or in combination.

[0273] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In the present disclosure, the base station as the subject of resource allocation for executing the terminal may be at least one of a gNode B, a gNB, an eNode B, a Node B, a BS, a radio access unit, a base station controller, or a node on a network. The terminal may include a UE, an MS, a cellular phone, a smart phone, a computer, or a multimedia system capable of performing a communication function. Hereinafter, the 5G system will be used as an example to describe the embodiments, but the embodiments may be applied to other communication systems with similar technical backgrounds or channel types. For example, LTE or LTE-A mobile communications and mobile communication technologies developed after 5G may be included therein. Therefore, the embodiments may be applied to other communication systems with some modifications within the scope of the present disclosure determined by a person of ordinary skill in the art without significantly departing from the scope of the present disclosure. The contents of the present disclosure are applicable to FDD and TDD systems.

[0274] In addition, in the description of the present disclosure, if it is determined that the detailed description of the relevant function or configuration may unnecessarily obscure the subject matter of the present disclosure, its detailed description will be omitted. In addition, the terms to be described later are terms defined in consideration of the functions in the present disclosure, which may vary according to the intentions or habits of users and operators. Therefore, they should be defined based on the entire description of this article.

[0275] Hereinafter, the higher layer signaling may be signaling corresponding to at least one or a combination of one or more of the following signalings.

[0276] -Master Information Block (MIB)

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

[0278] -Radio Resource Control (RRC)

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

[0280] In addition, the L1 signaling may be signaling corresponding to at least one or a combination of one or more of signaling methods using the following physical layer channels or signaling.

[0281] - Physical Downlink Control Channel (PDCCH)

[0282] - Downlink Control Information (DCI)

[0283] -UE-specific DCI

[0284] -Group Common DCI

[0285] - Public DCI

[0286] - Scheduling DCI (e.g., DCI for scheduling downlink or uplink data)

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

[0288] -Physical Uplink Control Channel (PUCCH)

[0289] - Uplink Control Information (UCI)

[0290] In the present disclosure, determining the priority between A and B means selecting one with a higher priority to perform an operation corresponding thereto, or omitting (or discarding) the operation of the other with a lower priority according to a predetermined priority rule.

[0291] In the following description, the above-mentioned examples will be described through a plurality of embodiments, but they are not independent, and such embodiments can be applied simultaneously or in combination.

[0292] [Random access process in SBFD]

[0293] Meanwhile, 3GPP is discussing sub-band non-overlapping full-duplex (SBFD) as a new duplex scheme based on NR. SBFD is a technology that utilizes a portion of downlink resources as uplink resources in a TDD band (spectrum) at a frequency below 6 GHz or above 6 GHz, extends the uplink coverage of the UE by allowing uplink transmissions from the UE to be received as much as the increased uplink resources, and reduces feedback delay by allowing feedback on downlink transmissions from the UE to be received in the extended uplink resources. In the present disclosure, a UE that receives information from a base station about whether SBFD is supported and is able to perform uplink transmission in a portion of the downlink resources may be conveniently referred to as an SBFD UE (SBFD-capable UE). In order to define the SBFD scheme in the standard and allow the SBFD UE to determine whether SBFD is supported in a specific cell (or frequency, band), the following scheme may be considered.

[0294] The first solution. In addition to the existing frame structure type of unpaired spectrum (or time division duplex, TDD) or paired spectrum (or frequency division duplex, FDD), another frame structure type (for example, frame structure type 2) can be introduced to define the above-mentioned SBFD. Frame structure type 2 can be defined as supported in a specific frequency or frequency band, or the base station can indicate to the UE whether SBFD is supported via system information. SBFD UE can receive system information including whether SBFD is supported, and determine whether SBFD is supported in a specific cell (or frequency, frequency band).

[0295] Second solution. Without defining a new frame structure type, it may be indicated whether SBFD is additionally supported in a specific frequency or frequency band of an existing unpaired spectrum (or TDD). In the second solution, it may be defined whether SBFD is additionally supported in a specific frequency or frequency band of an existing unpaired spectrum, or the base station may indicate to the UE via system information whether SBFD is supported. An SBFD UE may receive system information including whether SBFD is supported, and determine whether SBFD is supported in a specific cell (or frequency, frequency band).

[0296] In the first and second schemes, the information on whether SBFD is supported may be information that indirectly indicates whether SBFD is supported by further configuring a portion of downlink resources as uplink resources in addition to TDD uplink (UL)-downlink (DL) resource configuration information indicating downlink time slot (or symbol) resources and uplink time slot (or symbol) resources of TDD (for example, the information described below). Fig.12 SBFD resource configuration information in the SBFD resource configuration information), or may be information directly indicating whether SBFD is supported.

[0297] In the present disclosure, the SBFD UE may obtain cell synchronization by receiving a synchronization signal block in the initial cell access for accessing a cell (or base station). For the SBFD UE and the existing TDD UE, the process of obtaining cell synchronization may be the same. Thereafter, through the MIB acquisition process, the SIB acquisition process, or the random access process, the SBFD UE may determine whether the cell supports SBFD.

[0298] The system information for transmitting information about whether SBFD is supported may be system information transmitted separately from system information for UEs supporting different versions of standards in the cell (e.g., existing TDD UEs), and the SBFD UE may determine whether SBFD is supported by obtaining all or part of the system information transmitted separately from the system information of the existing TDD UE. If the SBFD UE obtains only the system information for the existing TDD UE or obtains the system information about SBFD not being supported, it may determine that the cell (or base station) supports only TDD.

[0299] If the information about whether SBFD is supported is included in the system information of a UE supporting a different version of the standard (e.g., an existing TDD UE), the information about whether SBFD is supported may be inserted at the end so as not to affect the acquisition of the system information by the existing TDD UE. If the SBFD UE fails to obtain the inserted information about whether SBFD is supported, or obtains information that SBFD is not supported, the SBFD UE may determine that the cell (or base station) supports only TDD.

[0300] If information about whether SBFD is supported is included in the system information of a UE supporting a different version of the standard (e.g., an existing TDD UE), the information about whether SBFD is supported can be sent via a separate PDSCH so as not to affect the acquisition of system information by the existing TDD UE. That is, a UE that does not support SBFD can receive a first SIB (or SIB1) including existing TDD-related system information in a first PDSCH. A UE that supports SBFD can receive a first SIB (or SIB1) including existing TDD-related system information in a first PDSCH, and can receive a second SIB including SBFD-related system information in a second PDSCH. Here, 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 using the same RNTI (e.g., SI-RNTI). The search space for monitoring the second PDCCH may be acquired from the system information of the first PDSCH, and if not acquired (ie, if the system information of the first PDSCH does not include information about the search space), the second PDCCH may be received in the same search space as that of the first PDCCH.

[0301] When the SBFD UE determines that the cell (or base station) supports only TDD as described above, the SBFD UE may perform a random access procedure and transmission / reception of data / control signals in the same manner as an existing TDD UE.

[0302] The base station may configure a separate random access resource for each of the existing TDD UE and the SBFD UE (e.g., the SBFD UE supporting duplex communication and the SBFD UE supporting half-duplex communication), and send the configuration information of the random access resource (control information or configuration information indicating the time-frequency resources that can be used for the PRACH) to the SBFD UE through the system information. The system information for sending information of the random access resource may be system information that is sent separately and distinguished from the system information of the UE supporting a different version of the standard (e.g., the existing TDD UE) in the cell.

[0303] The base station can configure separate random access resources for TDD UEs and SBFD UEs supporting different versions of standards, thereby distinguishing whether TDD UEs supporting different versions of standards perform random access or SBFD UEs perform random access. For example, the random access resources separately configured for SBFD UEs can be resources determined as downlink time resources by existing TDD UEs, and the SBFD UE can perform random access through uplink resources (or separate random access resources) configured in a certain frequency of the downlink time resources, so that the base station can determine that the UE attempting random access through the uplink resources is a SBFD UE.

[0304] Alternatively, instead of configuring a separate random access resource for the SBFD UE, the base station may configure a common random access resource for all UEs in the cell. In this case, the configuration information of the random access resource may be sent to all UEs in the cell through system information, and the SBFD UE that has received the system information may perform random access to the random access resource. Thereafter, the SBFD UE may complete the random access procedure and proceed to an RRC connection mode for sending and receiving data with the cell. After the RRC connection mode, the SBFD UE may receive an upper layer or physical signal from the base station indicating that some frequency resources of the downlink time resources are configured as uplink resources, and then perform an SBFD operation, for example, an operation of sending an uplink signal in the uplink resource.

[0305] In the case of determining that the cell supports SBFD, the SBFD UE may send capability information to the base station, the capability information including at least one or more of whether the UE supports SBFD, whether full-duplex communication or half-duplex communication is supported, and the number of transmitting or receiving antennas equipped (or supported), thereby notifying the base station that the UE attempting to access is a SBFD UE. Alternatively, if half-duplex communication support is a mandatory implementation of the SBFD UE, whether half-duplex communication is supported may be omitted from the capability information. The report of the SBFD UE on the capability information may be sent to the base station through a random access procedure, after the random access procedure is completed, or after switching to an RRC connection mode for sending and receiving data with the cell.

[0306] The SBFD UE may support half-duplex communication that performs only uplink transmission or downlink reception at a time like an existing TDD UE, or may support full-duplex communication that performs both uplink transmission and downlink reception at a time. Therefore, the SBFD UE may report to the base station through a capability report whether half-duplex communication or full-duplex communication is supported, and after the report, the base station may configure the SBFD UE as to whether the SBFD UE will use half-duplex communication or full-duplex communication to perform transmission / reception. In the case where the SBFD UE reports the capability of half-duplex communication to the base station, since a duplexer is generally not present, a switching gap may be required to change the RF between transmission and reception when operating in FDD or TDD.

[0307] Typically, the UE can form a wireless link with the network through a random access procedure based on synchronization with the network and system information acquired during the cell search process. Random access can use a contention-based or non-contention-based (non-contention) scheme. When the UE performs cell selection and reselection during the initial access step of the cell, for example, when moving from the RRC_IDLE (RRC idle) state to the RRC_CONNECTED (RRC connected) state, contention-based random access can be used. Non-contention random access can be used to reestablish uplink synchronization when downlink data arrives, in the case of handover, or in the case of position measurement.

[0308] Fig.11 is a diagram illustrating a random access procedure in an embodiment of the present disclosure.

[0309] exist Fig.11In the embodiment, a contention-based random access process is shown as an example. In addition, although not shown, the base station may send a synchronization signal block as described in the above embodiment. In this case, the base station may use beam scanning to periodically send a synchronization signal block. For example, the base station may use up to 64 different beams within 5ms to send a synchronization signal block including a PSS / SSS (synchronization signal) and a PBCH (broadcast channel) signal, and multiple synchronization signal blocks may be sent using different beams. The UE may detect (select) a synchronization signal block with the best beam direction (e.g., a beam direction with the strongest received signal strength or greater than a predetermined threshold), and use a physical random access channel (PRACH) resource associated with the detected synchronization signal block to send a preamble. For example, in the first step 1101 of the random access process, the UE may send a random access preamble (or message 1) to the base station. The base station receiving the random access preamble may measure the transmission delay value between the UE and the base station and synchronize the uplink. Specifically, the UE may send a random access preamble randomly selected from a set of random access preambles pre-given by system information. The initial transmission power of the random access preamble can be determined based on the path loss between the base station and the UE measured by the UE. In addition, the UE can determine the transmission beam direction (or transmission beam or beams) of the random access preamble based on the synchronization signal block received from the base station, and send the random access preamble by applying the determined transmission beam direction.

[0310] In a second step 1102, the base station may send a response (Random Access Response (RAR) or Message 2) to the UE for the detected random access attempt. The base station may send an uplink transmission timing control command to the UE based on the transmission delay value measured from the random access preamble received in the first step. In addition, the base station may send uplink resources and power control commands to be used by the UE as scheduling information. The scheduling information may include control information for an uplink transmission beam for the UE. The RAR may be sent over the PDSCH and may include at least one of the following information.

[0311] - Random access preamble sequence index detected by the network (or base station)

[0312] -TC-RNTI (temporary cell radio network temporary identifier)

[0313] - Uplink Scheduling Grant

[0314] -Timing advance value

[0315] If the UE fails to receive the RAR (which is scheduling information for message 3) from the base station within a predetermined time period in the second step 1102, the UE may again perform the first step 1101. In this case, the UE increases the transmission power of the random access preamble by a predetermined step size and transmits it (this is called power ramping), thereby increasing the probability that the base station receives the random access preamble.

[0316] In the third step 1103, the UE may send uplink information (scheduled transmission or message 3) including a UE identifier (which may be referred to as a UE contention resolution identifier) ​​(or a valid UE identifier (C-RNTI) if the UE already has the UE identifier in the cell before initiating the random access procedure) to the base station through a physical uplink shared channel (PUSCH) using the uplink resources allocated in the second step 1102. The transmission timing of the uplink data channel used to send message 3 may follow the uplink transmission timing control command received from the base station in the second step 1102. In addition, the transmission power of the uplink data channel used to send message 3 may be determined by considering the power control command received from the base station in the second step 1102 and the power ramp value of the random access preamble. The uplink data channel used to send the above-mentioned message 3 may be the first uplink data signal sent by the UE to the base station after sending the random access preamble.

[0317] Finally, in the fourth step 1104, if the base station determines that the UE has performed random access without conflict with other UEs, the base station may send a message (contention resolution (CR) message or message 4) including an identifier of the UE that sent uplink data in the third step 1103 to the UE. In this regard, if a plurality of UEs receive the same TC-RNTI in the second step 1102, each of the plurality of UEs receiving the same TC-RNTI may include its own UE identifier (UE contention resolution identifier) ​​in message 3 in the third step 1103 and send it to the base station, and then, for contention resolution, the base station may send message 4 (CR message) including one UE identifier among the identifiers of the plurality of UEs. When the UE receives message 4 (CR message) including its own UE identifier from the base station in the fourth step 1104 (or sends message 3 including the UE identifier (C-RNTI) in the third step 1103 and then receives UE-specific control information including CRC based on the UE identifier (C-RNTI) through the PDCCH in the fourth step 1104), the UE may determine that the random access is successful. Therefore, among multiple UEs that have received the same TC-RNTI from the base station, the UE that confirms that its UE identifier is included in message 4 (CR message) can know that the competition is successful. In addition, the UE can send a HARQ-ACK / NACK signal indicating whether message 4 has been successfully received to the base station through a physical uplink control channel (PUCCH).

[0318] If the data transmitted by the UE in the third step 1103 collides with the data from another UE and thus the base station fails to receive the data signal from the UE, the base station may no longer perform data transmission to the UE. Therefore, if the UE fails to receive the data transmitted from the base station in the fourth step 1104 within a certain period of time, the UE may determine that the random access procedure has failed and may restart from the first step 1101.

[0319] As described above, in the first step 1101 of the random access procedure, the UE may send a random access preamble on the PRACH. There are 64 available preamble sequences in each cell, and four long preamble formats and nine short preamble formats may be used depending on the transmission form. The UE generates 64 preamble sequences using the root sequence index and cyclic shift value signaled using system information, and may randomly select a sequence to be used as a preamble.

[0320] The base station may notify the UE of the configuration information for random access resources, for example, control information (or configuration information) indicating the time-frequency resources that can be used for PRACH, by using at least one of SIB, higher layer signaling (RRC information), or DCI. The frequency resources used for PRACH transmission may indicate the starting RB point of the transmission to the UE, and the number of RBs used may be determined according to the preamble format sent through PRACH and the applied subcarrier spacing. The time resources used for PRACH transmission may indicate the preconfigured PRACH configuration period, the subframe index and the starting symbol including the PRACH transmission time point (which may be used interchangeably with the PRACH opportunity or transmission time), the number of PRACH opportunities in the time slot, etc., through a PRACH configuration index (0 to 255), as shown in Table 16 below. The UE may determine the validity of the PRACH opportunity indicated by the PRACH configuration index, and determine only the valid PRACH opportunity as the PRACH opportunity at which the random access preamble can be sent. Through 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 check the time and frequency resources for sending the random access preamble code, and send the selected sequence as the preamble code to the base station.

[0321] [Table 16]

[0322]

[0323]

[0324]

[0325] At the same time, according to an embodiment of the present disclosure, in a scheme in which the SBFD UE determines the validity of the PRACH timing through the PRACH configuration index of the PRACH transmission and the SBFD configuration and performs PRACH transmission through the PRACH timing determined to be valid, a process of the SBFD UE is required when the valid PRACH timing overlaps with the downlink reception.

[0326] Therefore, we will use Figures 12 to 18 A method for a SBFD UE to determine the validity of a PRACH opportunity and the operation of the SBFD UE when a valid PRACH opportunity and downlink reception are configured or scheduled to occur simultaneously is described.

[0327] Fig.12 : is a diagram showing an example of SBFD operation in a TDD band of a wireless communication system to which the present disclosure is applied.

[0328] exist Fig.12(a) shows a case where TDD is operated in a specific frequency band. In a cell where TDD is operated, the base station can send a signal including data / control information from an existing TDD UE or SBFD UE in a downlink time slot (or symbol), an uplink time slot (or symbol) 1201, and a flexible time slot (or symbol), and receive a signal including data / control information to an existing TDD UE or SBFD UE based on the configuration of TDD UL-DL resource configuration information for downlink time slot (or symbol) resources and uplink time slot (or symbol) resources indicating TDD.

[0329] exist Fig.12 It can be assumed that the DDDSU time slot format is configured according to the TDD UL-DL resource configuration information. Here, "D" is a time slot consisting entirely of downlink symbols, "U" is a time slot consisting entirely of uplink symbols, and "S" is a time slot that is neither "D" nor "U", that is, a time slot including downlink symbols or uplink symbols or flexible symbols. Here, for convenience, it can be assumed that S consists of 12 downlink symbols and 2 flexible symbols. In addition, the DDDSU time slot format can be repeated according to the TDD UL-DL resource configuration information. That is, the repetition period of the TDD configuration can be set to 5 time slots (5ms for 15kHz SCS, 2.5ms for 30kHz SCS, etc.).

[0330] Next, in Fig.12 (b), (c) and (d) of FIG. 5 show the case where SBFD operates together with TDD in a specific frequency band.

[0331] exist Fig.12 In (b), the UE may be configured with a portion of the frequency band of the cell as a frequency band 1210 in which uplink transmission is available. This frequency band may be referred to as a UL subband. The UL subband may be applied to all symbols of all time slots. The UE may send an uplink channel or signal scheduled for all symbols 1212 in the UL subband. However, the UE may not send an uplink channel or signal in a frequency band other than the UL subband.

[0332] exist Fig.12 In (c), the UE may be configured with a portion of the frequency band of the cell as a frequency band 1220 in which uplink transmission is available, and may be configured with a time region in which the frequency band is activated. Here, the frequency band may be referred to as a UL subband. Fig.12In (c), the UL subband is deactivated in the first time slot, and the UL subband may be activated in the remaining time slots. Therefore, the UE may transmit an uplink channel or signal in the UL subband 1222 of the remaining time slots. Although the UL subband is activated in units of time slots in this case, whether it is activated may be configured in units of symbols.

[0333] exist Fig.12 In (d), the UE may be configured with time-frequency resources in which uplink transmission is available. The UE may be configured with one or more time-frequency resources as time-frequency resources in which uplink transmission is available. For example, the partial frequency bands 1232 of the first and second time slots may be configured as time-frequency resources in which uplink transmission is available. In addition, the partial frequency bands 1233 of the third time slot and the partial frequency bands 1234 of the fourth time slot may be configured as time-frequency resources in which uplink transmission is available.

[0334] In the following description, time-frequency resources available for uplink transmission within a downlink symbol or time slot may be referred to as SBFD resources.

[0335] Meanwhile, the base station may send the PRACH configuration to the UE via system information, and the RACH occasions may be configured according to the PRACH configuration. The UE may determine that all or some of the RACH occasions are valid.

[0336] In an FDD cell, all RACH occasions according to the PRACH configuration may be defined as valid. Here, the valid RACH occasion may be referred to as a valid RACH occasion (RACH occasion, RO).

[0337] In a TDD cell, only RACH opportunities that satisfy the following conditions in the PRACH configuration can be considered valid.

[0338] - In case TDD DL / UL configuration information is not received in the system information, if the RACH opportunity in the PRACH slot is not before the SS / PBCH and is N from the last received symbol of the SS / PBCH gap symbols later, the RACH opportunity can be determined to be valid.

[0339] - In case TDD DL / UL configuration information is received in system information, if the RACH opportunity in the UL symbol or the RACH opportunity in the PRACH slot is not before the SS / PBCH, gap symbols and after the last DL symbol, the RACH opportunity can be determined to be valid.

[0340] Fig.13The effective RO in the TDD cell is shown.

[0341] exist Fig.13 In (a), it is assumed that the UE receives a DDDSU with TDD DL / UL configuration information, and the RACH opportunity is configured for each time slot according to the PRACH configuration. The UE can determine that the PRACH configuration overlapping the UL symbol is a valid RACH opportunity. Here, the fifth time slot (the last time slot of the TDD cycle configured with the DDDSU) is an uplink time slot, and the RACH opportunity 1301 can be valid. However, the RACH opportunities of the first, second, third and fourth time slots (the first 4 time slots of the TDD cycle configured with the DDDSU) may be invalid because they do not start after the last downlink symbol. Therefore, the UE can determine that the RACH opportunities of four uplink time slots (the fifth, tenth, fifteenth and twentieth) within 20 time slots are valid, and the RACH opportunities of the remaining 16 time slots are invalid.

[0342] In the first method of the present disclosure, when the SBFD UE is configured with time-frequency resources for uplink transmission and SBFD uplink resources, the UE may determine the validity of the RACH opportunity as follows.

[0343] - In case TDD DL / UL configuration information is not received in the system information, if the RACH opportunity in the PRACH slot is not before the SS / PBCH and is N from the last received symbol of the SS / PBCH gap symbols later, the RACH opportunity can be determined to be valid.

[0344] - In case TDD DL / UL configuration information is received in system information, if a RACH opportunity in a UL symbol or a RACH opportunity in a PRACH slot is not before the SS / PBCH and is within N seconds from the last received symbol of the SS / PBCH gap symbols later, and if the RACH opportunity is located within the SBFD uplink resources, the RACH opportunity may be determined to be valid.

[0345] That is, when comparing the validity of the RACH opportunities of TDD, in the case where TDD DL / UL configuration information is received in the system information, the RACH opportunities included in the SBFD uplink resource region within the DL symbol may be valid RACH opportunities. Therefore, the UE can obtain more RACH opportunities through the above method.

[0346] However, in the first method, depending on the location of SS / PBCH, the RACH opportunity may be invalid. In addition, if the RACH opportunity is configured in SBFD uplink resources (resources capable of uplink transmission), the problem of RACH opportunity being limited in resources may occur. This can be solved in the second method.

[0347] In the second method of the present disclosure, when the SBFD UE is configured with time-frequency resources for uplink transmission and SBFD uplink resources, the UE may determine the validity of the RACH opportunity as follows.

[0348] - In case TDD DL / UL configuration information is not received in the system information, if the RACH opportunity in the PRACH slot is not before the SS / PBCH and is N from the last received symbol of the SS / PBCH gap symbols later, the RACH opportunity can be determined to be valid.

[0349] - In case TDD DL / UL configuration information is received in system information, if the RACH opportunity in the UL symbol is located within the SBFD uplink resource, the RACH opportunity may be determined to be valid.

[0350] exist Fig.13 In (b), (c) and (d), the UE may determine whether the RACH opportunity is valid based on the TDD UL-DL resource configuration information and the SBFD uplink resource information.

[0351] exist Fig.13 In (b), the UE may be configured with a UL subband, and the resources of the UL subband of the downlink symbol may be determined as SBFD uplink resources. Fig.14 SS / PBCH is not shown in the figure, so there is no difference between the first method and the second method), the UE can determine that the RACH opportunity is valid because the SBFD uplink resources of the first 4 time slots in the TDD cycle include the RACH opportunity.

[0352] For reference, in Fig.13 In (b), when the UL subband is configured, uplink transmission is available in the resources of the UL subband in all symbols. Therefore, the first and second methods can be briefly described as follows.

[0353] In a modified first method of the present disclosure, when a SBFD UE is configured with time-frequency resources and SBFD resources for uplink transmission, the UE may determine the validity of a RACH opportunity as follows.

[0354] - If the frequency band of the RACH opportunity configured according to the PRACH configuration is included in the UL subband, and if the RACH opportunity in the PRACH slot is not before the SS / PBCH and is within N from the last received symbol of the SS / PBCH gap symbols later, the RACH opportunity can be determined to be valid.

[0355] In a modified second method of the present disclosure, when a SBFD UE is configured with time-frequency resources and SBFD resources for uplink transmission, the UE may determine the validity of a RACH opportunity as follows.

[0356] - If the frequency band of the RACH occasion configured according to the PRACH configuration is included in the UL subband, all RACH occasions may be valid.

[0357] exist Fig.13 In (c), the UE may be configured with a UL subband and a time region in which the uplink subband is activated, and the resources of the UL subband of the downlink symbol of the activated time region may be determined as SBFD uplink resources. Fig.13 SS / PBCH is not shown in the figure, so there is no difference between the first and second methods), the UE can determine that the RACH opportunity 1321 is valid because the RACH opportunity is included in the SBFD uplink resources of the second, third and fourth time slots in the TDD cycle. For reference, the RACH opportunity 1322 of the first time slot in the TDD cycle can be determined to be invalid because it is not included in the SBFD uplink resources.

[0358] exist Fig.13 In (d), the UE may be configured with the time-frequency domain of the SBFD uplink resource, and according to the first and second methods (due to Fig.13 SS / PBCH is not shown in the figure, so there is no difference between the first and second methods), the UE can determine that the RACH opportunity overlapping with the SBFD uplink resource is valid. That is, because the RACH opportunities 1331 of the first and second time slots in the TDD cycle can be valid, this is because they are included in the SBFD uplink resource. However, the RACH opportunities 1332 of the third and fourth time slots may not be valid because they are not included in the SBFD uplink resource.

[0359] Despite Fig.13Although not specifically mentioned in (b), (c) and (d) of , a RACH opportunity that overlaps with a UL symbol may always be valid. However, the UE may be configured with SBFD downlink resources that enable DL transmission within a UL symbol. In this case, if the SBFD downlink resources overlap with the RACH opportunity, the RACH opportunity may be invalid. In an alternative method, the RACH opportunity may be valid even if the SBFD downlink resources overlap with the RACH opportunity. That is, when determining a valid RACH opportunity, the SBFD downlink resources configured in the uplink symbol may be ignored.

[0360] When one PRACH is configured for TDD UE (UE other than SBFD UE) and SBFD UE, the first and second methods described above can be used. That is, based on one PRACH resource configuration, the TDD UE can use the method of the TDD cell (in Fig.13 (a) of the present invention) determines the effective RACH timing, and the SBFD UE may determine the effective RACH timing according to the first and second methods described above (in Fig.13 (b), (c) and (d) of FIG. 5 ) to determine the effective RACH timing.

[0361] In a 5G system, a UE may receive a synchronization signal block and be configured with a control resource set (CORESET) #0 (which may correspond to a control resource set having a control resource set index or identification (ID) of 0) and a search space #0 (which may correspond to a search space having a search space index or ID of 0) from the synchronization signal block. Assuming that the selected synchronization signal block and a demodulation reference signal (DMRS) transmitted in CORESET #0 are quasi co-located (QCL), the UE may perform monitoring of CORESET #0. In addition, the UE may receive system information based on the downlink control information transmitted in CORESET #0. The UE may obtain PRACH-related configuration information for random access from the received system information. The UE that obtains the PRACH-related configuration information can send a preamble code to the base station in the PRACH based on the index of the received synchronization signal block when performing random access (for example, when receiving a synchronization signal block with a corresponding index, the UE uses a transmission beam having a QCL relationship with the reception beam to send the preamble code in the PRACH), and the base station that receives the preamble code from the UE through the PRACH can obtain information about the index of the synchronization signal block selected (received) by the UE. When sending Msg2( Fig.111102), the base station may transmit the PDCCH or Msg2 PDSCH scheduling the Msg2 PDSCH using a transmission beam having the same QCL relationship as the synchronization signal block corresponding to the received PRACH. Therefore, the UE may receive the PDCCH or Msg2 PDSCH scheduling the Msg2 PDSCH using the reception beam used when receiving the synchronization signal block corresponding to the selected (transmitted) PRACH.

[0362] The UE may receive information about the mapping between valid RACH opportunities and synchronization signal blocks from the base station. At this time, from SIB1, the configuration information is configured as the same value for all UEs in the cell. Based on the configuration information, the UE may determine the mapping between valid RACH opportunities and synchronization signal blocks.

[0363] The indexes of valid RACH opportunities may be given (assigned) sequentially starting from 0. Each valid RACH opportunity is assigned a unique index, which may be mapped to the index of a synchronization signal block. In the present disclosure, for convenience, it is assumed that valid RACH opportunities are assigned indexes in time sequence. For reference, if valid RACH opportunities are configured in different frequency domains at the same time point, the indexes may be assigned first according to the frequency domain and then in time sequence. In the following, it is assumed that the meaning of "it may be given" may include the meaning of "it may be assigned".

[0364] Based on the information about the mapping between the valid RACH opportunities and the synchronization signal blocks, N valid RACH opportunities may be mapped to one synchronization signal block, where N is a value of 1 or greater than 1. In this case, valid RACH opportunities with indexes 0, 1, ..., N-1 may be mapped to a synchronization signal block with an index of 0. In general, valid RACH opportunities with indexes i*N, i*N+1, ..., (i+1)*N-1 may be mapped to a synchronization signal block with an index i (e.g., i=0, 1, 2 ...).

[0365] Based on the information about the mapping between the valid RACH opportunity and the synchronization signal block, one valid RACH opportunity may be mapped to M synchronization signal blocks, where M is a value of 1 or greater. In this case, a RACH opportunity with an index i may be mapped to a synchronization signal block with an index i*M, i*M+1, ..., (i+1)*M-1 (e.g., i=0, 1, 2 ...). In this case, the preamble of one RACH opportunity is divided into M sets, and each set may be mapped to one synchronization signal block.

[0366] The problem to be solved in the present disclosure is that the mapping between the valid RACH timings and synchronization signal blocks of TDD UEs (UEs other than SBFD UEs) may be different from the mapping between the valid RACH timings and synchronization signal blocks of SBFD UEs. Therefore, from the perspective of the base station, ambiguity may arise as to which synchronization signal block the received PRACH is mapped.

[0367] Fig.14 Valid RACH timings and indices for TDD UEs and valid RACH timings and indices for SBFD UEs are shown.

[0368] exist Fig.14 In (a), TDD UE (UE other than SBFD UE) cannot receive SBFD uplink resource configuration information for SBFD UE. Therefore, even if SBFD uplink resources are configured in the cell, TDD UE can determine the valid RACH opportunity according to the existing method of the TDD cell. Therefore, the RACH opportunity of the last uplink time slot in the TDD cycle may be valid, and the RACH opportunity of the remaining time slots may not be valid. The UE can determine that 4 RACH opportunities in 20 time slots are valid and assign a unique index to each RACH opportunity. As mentioned above, the index can be assigned in chronological order. The index of the valid RACH opportunity in the fifth time slot can be 0, the index of the valid RACH opportunity in the tenth time slot can be 1, the index of the valid RACH opportunity in the fifteenth time slot can be 2, and the index of the valid RACH opportunity in the twentieth time slot can be 3.

[0369] The UE may be configured with N=2 as information about the mapping between a valid RACH opportunity and a synchronization signal block from a base station. This may be common to both TDD UEs and SBFD UEs. That is, two valid RACH opportunities may be mapped to one synchronization signal block. Specifically, valid RACH opportunities with indexes 0 and 1 may be mapped to a synchronization signal block 1401 with index 0. Valid RACH opportunities with indexes 2 and 3 may be mapped to a synchronization signal block 1402 with index 1.

[0370] exist Fig.14(b), the SBFD UE may receive SBFD uplink resource configuration information for the SBFD UE. Therefore, the SBFD UE may determine a valid RACH opportunity according to the first or second method described above. Therefore, the RACH opportunities of the second, third, and fourth time slots in the TDD cycle may be valid, and the RACH opportunity of the first time slot may not be valid. In addition, the fifth time slot in the TDD cycle may be an uplink time slot, and the RACH opportunity may be valid. Here, the fifth time slot of the TDD cycle is a valid RACH opportunity for both the TDD UE and the SBFD UE. The UE may determine that 16 of the 20 time slots are valid and assign a unique index to each RACH opportunity. As mentioned above, the index may be assigned in chronological order. The index of the valid RACH opportunity in the second time slot may be 0, the index of the valid RACH opportunity in the third time slot may be 1, the index of the valid RACH opportunity in the fourth time slot may be 2, and the index of the valid RACH opportunity in the fifth time slot may be 3.

[0371] The UE may be configured with N=2 as information about the mapping between a valid RACH opportunity and a synchronization signal block from a base station. This may be common to both TDD UEs and SBFD UEs. That is, two valid RACH opportunities may be mapped to one synchronization signal block. Specifically, valid RACH opportunities with indexes 0 and 1 may be mapped to a synchronization signal block 1411 with index 0. Valid RACH opportunities with indexes 2 and 3 may be mapped to a synchronization signal block 1412 with index 1.

[0372] The TDD UE and SBFD UE determine that the RACH opportunities of the uplink time slots in the TDD cycle are valid, but different indices may be assigned to them. Fig.14 As shown in (a) of FIG. 1 , in the case of a TDD UE, the index of the valid RACH opportunity in the fifth time slot is 0, but as Fig.14 As shown in (b), the index of the valid RACH opportunity in the fifth time slot in the case of SBFD UE is 3. Therefore, TDD UE and SBFD UE can assign different indices to the same valid RACH opportunity, and therefore, the index of the mapped synchronization signal block can be different. That is, Fig.14 As shown in (a) of FIG. 1 , the TDD UE maps the valid RACH opportunity of the fifth time slot to the synchronization signal block with index 0, but as shown in FIG. Fig.14As shown in (b), the SBFD UE can map the valid RACH opportunity of the fifth time slot to the synchronization signal block with index 1. In this case, even if the base station receives the PRACH preamble code in the valid RACH opportunity of the fifth time slot, the base station cannot determine the index of the synchronization signal block mapped to the valid RACH opportunity. A method for solving this problem is as follows.

[0373] Now, various embodiments of the present disclosure are described. Each embodiment relates to a method that satisfies at least the following. In the case where the SBFD UE and the TDD UE determine the same valid RACH opportunity, the index of the synchronization signal block mapped to the valid RACH opportunity may be the same. In addition, in the case where the SBFD UE and the TDD UE determine the same valid RACH opportunity, the index of the valid RACH opportunity may be the same in the SBFD UE and the TDD UE.

[0374] <First Embodiment> Definition of a New Valid RO Index Determination Method

[0375] In the first embodiment of the present disclosure, the SBFD UE may use a new valid RO index determination method. The new valid RO index determination method is a method of first allocating indices of valid RACH opportunities that both the TDD UE and the SBFD UE determine as valid RACH opportunities, and then allocating indices of valid RACH opportunities that only the SBFD UE determines as valid RACH opportunities.

[0376] Fig.15 A method for determining a new valid RO index is shown.

[0377] First, the SBFD UE may determine that the TDD UE and the SBFD UE are simultaneously determined as valid RACH opportunities. Here, the RACH opportunities of the fifth, tenth, fifteenth, and twentieth time slots may be determined as valid RACH opportunities. The UE may first assign indexes to the above four RACH opportunities. Here, the indexes start from 0 and may be assigned according to predefined rules. The predefined rules may be as follows.

[0378] - First, valid RACH opportunities simultaneously configured in different frequency domains may be indexed in ascending order of frequency.

[0379] - Then, the valid RACH opportunities configured to different times may be indexed in ascending order of time.

[0380] exist Fig.15In the example, it is assumed that there is only one valid RACH opportunity at the same time, so the index of the valid RACH opportunity in the fifth time slot is 0, the index of the valid RACH opportunity in the tenth time slot is 1, the index of the valid RACH opportunity in the fifteenth time slot is 2, and the index of the valid RACH opportunity in the fifth time slot is 3.

[0381] The SBFD UE may allocate the next index to only the valid RACH opportunities determined by the SBFD UE as valid. That is, since the indexes have been previously allocated up to 3, the next index may be allocated sequentially starting from 4. Although the indexes are allocated according to the previously determined rules, the indexes of the valid RACH opportunities that have already been allocated may remain as they are. Fig.15 , assuming that there is only one valid RACH opportunity at the same time, the index of the valid RACH opportunity in the second time slot that is the earliest in time among the valid RACH opportunities determined as valid by only the SBFD UE is 4, the index of the valid RACH opportunity in the third time slot is 5, and the index of the valid RACH opportunity in the fourth time slot is 6. In this way, the indices of the remaining valid RACH opportunities can also be allocated over time.

[0382] According to the first embodiment, the same index may be allocated to the TDD UE and the SBFD UE and simultaneously determined as valid valid RACH opportunities. Fig.15 As shown, for valid RACH opportunities in the fifth, tenth, fifteenth and twentieth time slots, TDD UE and SBFD UE can be equally allocated indexes 0, 1, 2 and 3, respectively. Therefore, the index of the same synchronization signal block can be mapped to the valid RACH opportunities that TDD UE and SBFD UE simultaneously determine to be valid.

[0383] <Second Embodiment> Reusing the existing valid RO index to determine and prioritize the valid RACH timing index of the TDD UE

[0384] In the second embodiment of the present disclosure, the SBFD UE may determine the indices of all valid RACH opportunities by using the existing index determination method of valid RACH opportunities, and newly allocate the indices to the valid RACH opportunities determined as equally valid by the SBFD UE and the TDD UE.

[0385] First, the SBFD UE may determine a valid RACH opportunity according to a method of the SBFD UE (eg, the first or second method described above) and assign a unique index to the valid RACH opportunity. Here, the index starts from 0 and may be assigned according to a predefined rule. The predefined rule may be as follows.

[0386] - First, valid RACH opportunities configured simultaneously in different frequency domains may be indexed in ascending order of frequency.

[0387] - Then, the valid RACH opportunities configured to different times may be indexed in ascending order of time.

[0388] Fig.16 is a diagram showing indexes of valid RACH opportunities according to the second embodiment.

[0389] like Fig.16 As shown, the SBFD UE may determine RACH opportunities of 16 time slots as valid RACH opportunities and may allocate indexes from 0 to 15 to the valid RACH opportunities.

[0390] The SBFD UE may determine that both the TDD UE and the SBFD UE are valid RACH opportunities. Here, the RACH opportunities of the fifth, tenth, fifteenth and twentieth time slots may be determined as valid RACH opportunities. These valid RACH opportunities may be newly allocated unique indexes. Here, the index may start from 0. Fig.16 , valid RACH opportunities of the fifth, tenth, fifteenth, and twentieth time slots may be assigned indexes 0, 1, 2, and 3. Previously, indexes 3, 7, 11, and 15 were assigned to the respective time slots. However, the indexes may be assigned to 0, 1, 2, and 3 again.

[0391] According to the second embodiment, the same index may be allocated to the TDD UE and the SBFD UE and simultaneously determined as valid valid RACH opportunities. Fig.16 As shown, for valid RACH opportunities in the fifth, tenth, fifteenth and twentieth time slots, TDD UE and SBFD UE can be equally allocated indexes 0, 1, 2 and 3, respectively. Therefore, the index of the same synchronization signal block can be mapped to the valid RACH opportunities that TDD UE and SBFD UE simultaneously determine to be valid.

[0392] However, in the case of the second embodiment, some indexes are not allocated to some valid RACH opportunities. For example, indexes 3, 7, 11, and 15 are unused indexes because new indexes are allocated. Therefore, the synchronization signal blocks connected to the above indexes may not have valid RACH opportunities corresponding to the indexes. Therefore, different numbers of valid RACH opportunities can be mapped to each synchronization signal block.

[0393] <Third Embodiment> Method for Individually Determining a Valid RO Index

[0394] In the third method of the present disclosure, a unique index may be assigned to valid RACH opportunities determined to be equally valid by both SBFD UEs and TDD UEs, and separately, a unique index may be assigned to valid RACH opportunities determined to be valid only by SBFD UEs. In this case, the unique index may start from 0 and may be assigned according to a predefined rule. The predefined rule may be as follows.

[0395] - First, valid RACH opportunities simultaneously configured in different frequency domains may be indexed in ascending order of frequency.

[0396] - Then, the valid RACH opportunities configured to different times may be indexed in ascending order of time.

[0397] Fig.17 : is a diagram showing the indexes of valid RACH opportunities determined according to the third embodiment.

[0398] First, the SBFD UE may determine that the TDD UE and the SBFD UE are simultaneously determined as valid RACH opportunities. Here, the RACH opportunities of the fifth, tenth, fifteenth, and twentieth time slots may be determined as valid RACH opportunities. The UE may assign indexes to the above four RACH opportunities. Here, the indexes start from 0 and may be assigned according to previously determined rules. Therefore, the indexes of the valid RACH opportunities of the fifth, tenth, fifteenth, and twentieth time slots may be assigned as 0, 1, 2, and 3.

[0399] In addition, the SBFD UE may determine that only valid RACH opportunities that the SBFD UE determines to be valid. Here, the valid RACH opportunities of the second, third, fourth, seventh, eighth, ninth, twelfth, thirteenth, fourteenth, seventeenth, eighteenth, and nineteenth time slots are valid RACH opportunities that only the SBFD UE determines to be valid. Indexes may be assigned to the above-mentioned valid RACH opportunities again. Here, the indexes start from 0 and may be assigned according to previously established rules. Therefore, the indexes of the valid RACH opportunities in the second, third, fourth, seventh, eighth, ninth, twelfth, thirteenth, fourteenth, seventeenth, eighteenth, and nineteenth time slots may be assigned as 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, and 11.

[0400] According to the third embodiment, the same index may be allocated to the TDD UE and the SBFD UE and simultaneously determined as valid valid RACH opportunities. Fig.17As shown, for valid RACH opportunities in the fifth, tenth, fifteenth and twentieth time slots, TDD UE and SBFD UE can be equally allocated indexes 0, 1, 2 and 3, respectively. Therefore, the index of the same synchronization signal block can be mapped to the valid RACH opportunities that TDD UE and SBFD UE simultaneously determine to be valid.

[0401] However, in the case of the third embodiment, there may be multiple valid RACH opportunities with the same index. Fig.17 As shown, a valid RACH opportunity with index 0 may be in the second slot and the fifth slot. This may be used as follows.

[0402] A TDD UE does not have valid RACH opportunities with the same index. Therefore, it always has one valid RACH opportunity with one index and can send a PRACH preamble in this RACH opportunity.

[0403] An SBFD UE may have multiple valid RACH opportunities with the same index. In this case, the SBFD UE may always send a PRACH preamble in a valid RACH opportunity that is not used by a TDD UE. Fig.17 As shown, the valid RACH opportunity with index 0 is in the second time slot and the fifth time slot, but the valid RACH opportunity of the fifth time slot is the valid RACH opportunity used by the TDD UE. Therefore, the SBFD UE may not send the PRACH preamble code in the valid RACH opportunity, but may send the PRACH preamble code in the valid RACH opportunity of the second time slot with the same index.

[0404] When the same valid RACH opportunity is shared and used by TDD UE and SBFD UE, the following advantages can be achieved. When a PRACH preamble is received in a specific valid RACH opportunity, the base station can determine whether the UE sending the PRACH preamble is a TDD UE or a SBFD UE. That is, because the SBFD UE always sends a PRACH preamble in a valid RACH opportunity that is not used by the TDD UE, it can be seen that the PRACH preamble received in the above-mentioned valid RACH opportunity is always a PRACH preamble sent by the SBFD UE. Therefore, the base station is able to schedule uplink signals (e.g., PUCCH of msg3 PUSCH or msg4 PDSCH, etc.) to the SBFD UE in the SBFD uplink resources.

[0405] For reference, when an SBFD UE wants to operate like a TDD UE, it can send a PRACH preamble in a valid RACH opportunity used by a TDD UE. In this case, although it is an SBFD UE, it can operate like a TDD UE. That is, it can be expected that uplink signals (e.g., PUCCH of msg3 PUSCH or msg4 PDSCH, etc.) will not be scheduled in SBFD uplink resources.

[0406] In the third embodiment, one PRACH configuration is commonly applied to TDD UE and SBFD UE. That is, the RACH timing is determined equally for TDD UE and SBFD UE according to one PRACH configuration, the TDD UE determines the validity of the RACH timing in the TDD cell method, and the SBFD UE determines the validity of the RACH timing in the SBFD UE method. However, the base station can configure different PRACH configurations for TDD UE and SBFD UE. Due to different PRACH configurations, the index of the valid RACH timing can be allocated separately for each configuration. Detailed embodiments related to this will be described below.

[0407] In the third-first embodiment of the present disclosure, the base station may send two PRACH configurations to the UE in the cell via system information. Here, the first PRACH configuration may be a configuration for a TDD UE, and the second PRACH configuration may be a configuration for a SBFD UE. The TDD UE may receive the first PRACH configuration and determine the RACH timing based on the first PRACH configuration. The TDD UE may determine a valid RACH timing among the RACH timings. At this point, the method of the TDD cell may be used to determine the valid RACH timing. The TDD UE may send a PRACH preamble in one of the valid RACH timings.

[0408] The SBFD UE may receive the second PRACH configuration and determine the RACH timing based on the second PRACH configuration. The SBFD UE may determine a valid RACH timing among the RACH timings. At this time, the SBFD UE method may be used to determine the valid RACH timing. The SBFD UE may send a PRACH preamble in one of the valid RACH timings.

[0409] In this case, when the SBFD UE determines a valid RACH opportunity, the following contents may be additionally considered.

[0410] -SBFD UE may determine that RACH opportunities included in UL symbols of TDD UL-DL configuration are invalid. That is, a region including UL symbols is determined not to be SBFD uplink resources, and it can be assumed that there is no valid RACH opportunity for SBFD UE in the region.

[0411] - The SBFD UE may determine that the RACH opportunity of the time slot in which the TDD UE determines the valid RACH opportunity is invalid. It can be assumed that the valid RACH opportunity of the SBFD UE and the valid RACH opportunity of the TDD UE do not overlap in one time slot.

[0412] In the third-second embodiment of the present disclosure, the base station may send two PRACH configurations to the UE in the cell via system information. Here, the first PRACH configuration may be a configuration for TDD UE and SBFD UE, and the second PRACH configuration may be a configuration for SBFD UE. The TDD UE may receive the first PRACH configuration and determine the RACH timing based on the first PRACH configuration. The TDD UE may determine a valid RACH timing among the RACH timings. At this point, the method of the TDD cell may be used to determine the valid RACH timing. The TDD UE may send a PRACH preamble in one of the valid RACH timings.

[0413] The SBFD UE receives the first PRACH configuration and the second PRACH configuration. The SBFD UE may determine the RACH timing based on the first PRACH configuration. The SBFD UE may determine the valid RACH timing among the RACH timings. At this time, the SBFD UE may use the method of the TDD cell to determine the valid RACH timing. The SBFD UE may determine the RACH timing based on the second PRACH configuration. The SBFD UE may determine the valid RACH timing among the RACH timings. At this time, the method of the SBFD UE may be used to determine the valid RACH timing. The SBFD UE may send a PRACH preamble in one of the valid RACH timing of the first PRACH configuration and the valid RACH timing of the second PRACH configuration.

[0414] If a SBFD UE sends a PRACH preamble in one of the valid RACH opportunities determined according to the first PRACH configuration, the UE may assume that uplink transmission is not possible in the SBFD uplink resources in the case of subsequent cell access. That is, the UE may expect that no PUCCH of Msg3 PUSCH or Msg4 PDSCH will be sent in the SBFD uplink resources thereafter. Therefore, upon receiving a PRACH preamble in one of the valid RACH opportunities determined according to the first PRACH configuration, the base station may not schedule an uplink in the SBFD uplink resources.

[0415] If the SBFD UE sends a PRACH preamble in one of the valid RACH opportunities determined according to the second PRACH configuration, the UE can assume that uplink transmission is possible in the SBFD uplink resources in the case of subsequent cell access. That is, the UE can expect that the PUCCH of Msg3 PUSCH or Msg4 PDSCH will be sent in the SBFD uplink resources thereafter. Therefore, when the PRACH preamble is received in one of the valid RACH opportunities determined according to the second PRACH configuration, the base station can schedule the uplink in the SBFD uplink resources.

[0416] The RACH timing may be determined according to the second PRACH configuration. The SBFD UE may determine a valid RACH timing among the RACH timings. At this time, the method of the SBFD UE may be used to determine the valid RACH timing. The SBFD UE may send a PRACH preamble in a RACH timing among the valid RACH timings.

[0417] In this case, when the SBFD UE determines a valid RACH opportunity, the following contents may be additionally considered.

[0418] -SBFD UE may determine that RACH opportunities included in UL symbols of TDD UL-DL configuration are invalid. That is, a region including UL symbols is determined not to be SBFD uplink resources, and it can be assumed that there is no valid RACH opportunity for SBFD UE in the region.

[0419] - The SBFD UE may determine that the RACH opportunity of the time slot in which the TDD UE determines the valid RACH opportunity is invalid. It can be assumed that the valid RACH opportunity of the SBFD UE and the valid RACH opportunity of the TDD UE do not overlap in one time slot.

[0420] In the third-first or third-second embodiment described above, the UE receives different PRACH configurations and sends a PRACH of a PRACH configuration. In this case, the UE may not be able to send PRACH, and RACHP retransmission may be required. For reference, if the UE fails to receive the PDCCH for scheduling msg2 within a certain interval after sending PRACH, it can determine that the PRACH transmission has failed. For retransmission, the UE can use the following method.

[0421] In the first method, the UE may retransmit the PRACH preamble included in the previously transmitted PRACH configuration. At this time, the PRACH preamble may be retransmitted with a new transmission power. The new transmission power may be a certain level higher than the previous transmission power. The UE may transmit a PRACH preamble of a PRACH configuration other than the previously transmitted PRACH configuration. Even in this case, the UE may perform transmission by increasing the transmission power by a certain level compared to the transmission power of the previously transmitted PRACH preamble. That is, the UE may determine the power used for transmission without distinguishing between different PRACH configurations.

[0422] In the second method, the UE may retransmit the PRACH preamble included in the previously transmitted PRACH configuration. At this time, the PRACH preamble may be retransmitted with a new transmission power. The new transmission power may be a certain level higher than the previous transmission power. The UE may send a PRACH preamble of a PRACH configuration other than the previously transmitted PRACH configuration. In this case, the new transmission power may be determined regardless of the transmission power of the previously transmitted PRACH preamble. That is, different transmission powers may be used for the corresponding PRACH configuration and determined independently. In the second method, each of the multiple PRACH configurations may have a configuration value for the transmission power of the PRACH preamble.

[0423] <Fourth Embodiment> Using the Effective RACH Opportunities of SBFD Uplink Resources for PRACH Repeated Transmission

[0424] In the fourth embodiment of the present disclosure, the SBFD UE may assign an index to a valid RACH opportunity determined to be valid in the same manner as the TDD UE. In this case, the unique index may start from 0 and may be assigned according to a predefined rule. The predefined rule may be as follows.

[0425] - First, valid RACH opportunities configured simultaneously in different frequency domains may be indexed in ascending order of frequency.

[0426] - Then, the valid RACH opportunities configured to different times may be indexed in ascending order of time.

[0427] The SBFD UE may allocate one of the previously allocated unique indexes to a valid RACH opportunity determined only by the SBFD UE as valid. That is, instead of individually allocating a unique index to a valid RACH opportunity determined only by the SBFD UE as valid, the index of a valid RACH opportunity determined by both the SBFD UE and the TDD UE as valid may be allocated again. In addition, the SBFD UE may repeatedly transmit the same PRACH preamble in a valid RACH opportunity allocated with the same index.

[0428] Fig.18 1 shows the indexes of valid RACH opportunities according to the fourth embodiment.

[0429] like Fig.18 As shown, the index of the valid RACH opportunity determined as valid only by the SBFD UE may be the same as the index of the valid RACH opportunity determined as valid by both the SBFD UE and the TDD UE in the same TDD cycle. That is, the index of the valid RACH opportunity in the second, third and fourth time slots may be the same as the index of the valid RACH opportunity in the fifth time slot. The SBFD UE may repeatedly send the PRACH preamble in the valid RACH opportunities with the same index. That is, because the indexes of the valid RACH opportunities in the second, third, fourth and fifth time slots are the same, the same PRACH preamble may be repeatedly sent in these four valid RACH opportunities.

[0430] According to the fourth embodiment, the SBFD UE may repeatedly send the PRACH preamble code in the SBFD configuration resources, thereby obtaining wider coverage.

[0431] <Fifth Embodiment> Non-use of PRACH resources of SBFD uplink resources before RRC connection

[0432] In the first to fifth embodiments, the SBFD UE determines the validity of the RACH opportunity differently from the TDD UE. Therefore, different indexes are assigned to the same RACH opportunity. As another method to solve this problem, the SBFD UE can only determine the same valid RACH opportunity as the TDD UE as valid. That is, the SBFD UE can be configured with SBFD uplink resources, but the SBFD uplink resources may not be used to determine the validity of the RACH opportunity. In other words, the SBFD UE also uses the method of the TDD cell to determine the validity of the RACH opportunity.

[0433] If the SBFD UE is connected to the cell (i.e., in RRC connected mode), the SBFD UE may receive a PRACH configuration through the SBFD uplink resources so as to send PRACH in the SBFD uplink resources. The SBFD UE may then determine the validity of the RACH opportunity in the SBFD uplink resources based on the PRACH configuration. A new unique index may be assigned to a valid RACH opportunity.

[0434] Such a unique index may start from 0 and may be assigned according to a predefined rule. The predefined rule may be as follows.

[0435] - First, valid RACH opportunities configured simultaneously in different frequency domains may be indexed in ascending order of frequency.

[0436] - Then, the valid RACH opportunities configured to different times may be indexed in ascending order of time.

[0437] The UE may send a valid RACH opportunity on the SBFD uplink resources in certain circumstances. For example, a valid RACH opportunity may be used for contention-free PRACH transmission. Therefore, when contention-free PRACH transmission is indicated (e.g., PDCCH command), the SBFD UE may send a PRACH preamble of the valid RACH opportunity.

[0438] Fig.19 is a diagram illustrating a structure of a UE in a wireless communication system according to an embodiment of the present disclosure.

[0439] refer to Fig.19 , the UE may include a transceiver (which indicates a UE receiver 1900 and a UE transmitter 1910), a memory (not shown) and a UE processor 1905 (or a UE controller or processor). Based on the communication method of the UE described above, the UE transceivers 1900 and 1910, the memory and the UE processor 1905 may operate. However, the elements of the UE are not limited to the examples described above. For example, the UE may include more or fewer elements than the aforementioned elements. In addition, the transceiver, the memory and the processor may be implemented in the form of a single chip.

[0440] The transceiver can send / receive signals to / from a base station. Here, the signal may include control information and data. To this end, the transceiver may include an RF transmitter for up-converting and amplifying the frequency of the transmitted signal, and an RF receiver for low-noise amplifying the received signal and down-converting the frequency of the received signal. However, this is only an embodiment of the transceiver, and the elements of the transceiver are not limited to the RF transmitter and the RF receiver.

[0441] In addition, the transceiver may receive a signal through a wireless channel and output the received signal to the processor, and may transmit a signal output from the processor through the wireless channel.

[0442] The memory may store programs and data required for the operation of the UE. In addition, the memory may store control information or data included in the signals sent and received by the UE. The memory may include a storage medium such as ROM, RAM, hard disk, CD-ROM and DVD, or a combination of storage media. In addition, there may be multiple memories.

[0443] In addition, the processor may control a series of processes so that the UE may operate according to the embodiments described above. For example, the processor may control the elements of the UE to receive a DCI consisting of two layers and simultaneously receive multiple PDSCHs. There may be multiple processors, and the processor may perform operations to control the elements of the UE by executing a program stored in a memory.

[0444] Fig. 20 is a diagram illustrating a structure of a base station in a wireless communication system according to an embodiment of the present disclosure.

[0445] refer to Fig. 20 , the base station may include a transceiver (which indicates a base station receiver 2000 and a base station transmitter 2010), a memory (not shown) and a base station processor 2005 (or a base station controller or processor). Based on the communication method of the base station described above, the base station transceivers 2000 and 2010, the memory and the base station processor 2005 can operate. However, the elements of the base station are not limited to the above examples. For example, the base station may include more or fewer elements than the aforementioned elements. In addition, the transceiver, the memory and the processor may be implemented in the form of a single chip.

[0446] The transceiver can send signals to / receive signals from the UE. Here, the signal may include control information and data. To this end, the transceiver may include an RF transmitter for up-converting and amplifying the frequency of the transmitted signal, and an RF receiver for low-noise amplifying the received signal and down-converting the frequency of the received signal. However, this is only an embodiment of the transceiver, and the elements of the transceiver are not limited to the RF transmitter and the RF receiver.

[0447] In addition, the transceiver may receive a signal through a wireless channel and output the signal to the processor, and may transmit a signal output from the processor through the wireless channel.

[0448] The memory may store programs and data necessary for the operation of the base station. In addition, the memory may store control information or data included in the signals sent and received by the base station. The memory may include a storage medium such as ROM, RAM, hard disk, CD-ROM and DVD, or a combination of storage media. In addition, there may be multiple memories.

[0449] The processor may control a series of processes so that the base station may operate according to the embodiments described above. For example, the processor may control the elements of the base station to compose a two-layer DCI including allocation information about a plurality of PDSCHs and transmit the configured DCI. There may be multiple processors, and the processor may perform operations to control the elements of the base station by executing a program stored in a memory.

[0450] The methods according to the embodiments described herein may be implemented by hardware, software, or a combination of hardware and software.

[0451] When the method is implemented by software, a computer-readable storage medium for storing one or more programs (software modules) may be provided. One or more programs stored in the computer-readable storage medium may be configured to be executed by one or more processors in an electronic device. At least one program may include instructions that cause an electronic device to perform a method according to the various embodiments defined by the appended claims and / or disclosed herein.

[0452] The program (software module or software) may be stored in a non-volatile memory, including random access memory and flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disk storage device, compact disc-ROM (CD-ROM), digital versatile disc (DVD) or other type of optical storage device or tape cassette. Alternatively, any combination of some or all of them may form the memory in which the program is stored. In addition, a plurality of such memories may be included in the electronic device.

[0453] In addition, the program can be stored in an attachable storage device, wherein the attachable storage device can access the electronic device through a communication network such as the Internet, an intranet, a local area network (LAN), a wide LAN (WLAN), and a storage area network (SAN) or a combination thereof. Such a storage device can access the electronic device via an external port. In addition, a separate storage device on a communication network can access the portable electronic device.

[0454] In the detailed embodiments described above, the elements included in the present disclosure are expressed in the singular or plural, depending on the detailed embodiments presented. However, for ease of description, the singular form or plural form is appropriately selected for the presented situation, and the present disclosure is not limited to the elements expressed in the singular or plural. Therefore, an element expressed in the plural may also include a single element, or an element expressed in the singular may also include multiple elements.

[0455] The embodiments described herein are merely specific examples that have been presented to easily explain the technical content of the present disclosure and to help understand the present disclosure, and are not intended to limit the scope of the present disclosure. That is, it is obvious to those skilled in the art that other variations based on the technical concept of the present disclosure can be implemented. In addition, as needed, the above-mentioned various embodiments can be adopted in combination. For example, an embodiment of the present disclosure can be partially combined with another embodiment to operate a base station and a terminal. For example, the first embodiment and the embodiment of the present disclosure can be partially combined to operate a base station and a terminal. In addition, although the above-mentioned embodiments have been described by an FDD LTE system, other variations based on the technical concept of the embodiments can be implemented in other systems such as TDD LTE and 5G or NR systems.

[0456] In the drawings describing the methods of the present disclosure, the order of description does not always correspond to the order of performing the steps of each method, and the sequential relationship between the steps may be changed or the steps may be performed in parallel.

[0457] Alternatively, in the drawings describing the method of the present disclosure, some elements may be omitted, and only some elements may be included therein without departing from the basic spirit and scope of the present disclosure.

[0458] Furthermore, in the method of the present disclosure, some or all of the contents of each embodiment may be implemented in combination without departing from the basic spirit and scope of the present disclosure.

[0459] Various embodiments of the present disclosure have been described. The above description of the present disclosure is for illustrative purposes only and is not intended to limit the embodiments of the present disclosure to the embodiments set forth herein. Those skilled in the art will appreciate that other specific modifications and changes can be easily made to the present disclosure without changing the technical concept or basic features of the present disclosure. The scope of the present disclosure should not be determined by the above description, but by the appended claims, and all changes and modifications derived from the meaning and scope of the claims and their equivalent concepts should be interpreted as falling within the scope of the present disclosure.

Claims

1. A method for a terminal supporting sub-band non-overlapping full-duplex (SBFD) in a wireless communication system, the method include: receiving time division duplex (TDD) resource configuration information and SBFD resource configuration information from a base station; Determine a corresponding index of a first random access channel (RACH) opportunity that is commonly valid in the TDD resource configuration information and the SBFD resource configuration information; as well as determining a corresponding index of a second RACH opportunity that is invalid in the TDD resource configuration information and valid in the SBFD resource configuration information, The TDD resource configuration information includes format information of each time slot, and the SBFD resource configuration information includes information about uplink subbands.

2. The method according to claim 1, in, Determining the index of the second RACH opportunity is to allocate an index other than the index allocated to the first RACH opportunity to the second RACH opportunity.

3. The method according to claim 1, in, Determining the index of the second RACH opportunity sequentially allocates indexes to valid RACH opportunities in the SBFD resource configuration information based on a time order, and does not use an index to be allocated to the first RACH opportunity.

4. The method according to claim 1, further comprising: include: A RACH opportunity included in an uplink (UL) symbol indicated by the TDD resource configuration information is determined as an invalid RACH opportunity.

5. The method according to claim 1, further comprising: include: The RACH opportunities in the time slot including the valid RACH opportunities determined by the TDD resource configuration information are determined as invalid RACH opportunities.

6. The method according to claim 1, in, When a physical random access channel (PRACH) preamble is transmitted in a RACH opportunity determined by the TDD resource configuration information, message 3 (Msg3) is configured not to be transmitted in an uplink subband indicated by the SBFD resource configuration information; When the PRACH preamble is transmitted in the RACH opportunity of the UL subband indicated by the SBFD resource configuration information, the message 3 is configured to allow transmission in the UL subband.

7. The method according to claim 1, in, Determining the index of the second RACH opportunity sequentially allocates indexes to valid RACH opportunities in the SBFD resource configuration information based on a time order, and skips an index to be allocated to the first RACH opportunity to allocate an index to a RACH opportunity later in time.

8. The method according to claim 1, in, Determining the index of the second RACH opportunity is based on the TDD resource configuration information, and allocating the index of the second RACH opportunity in the TDD cycle identically to the index allocated to the first RACH opportunity in the TDD cycle.

9. The method according to claim 1, further comprising: include: A physical random access channel (PRACH) preamble is transmitted only in the second RACH opportunity excluding the first RACH opportunity.

10. A terminal supporting sub-band non-overlapping full-duplex (SBFD) operating in a wireless communication system, the terminal include: Transceiver; as well as The controller is configured as: receiving time division duplex (TDD) resource configuration information and SBFD resource configuration information from a base station, Determine a corresponding index of a first random access channel (RACH) opportunity that is commonly valid in the TDD resource configuration information and the SBFD resource configuration information; as well as determining a corresponding index of a second RACH opportunity that is invalid in the TDD resource configuration information and valid in the SBFD resource configuration information, The TDD resource configuration information includes format information of each time slot, and the SBFD resource configuration information includes information about uplink subbands.

11. The terminal according to claim 10, in, When determining the index of the second RACH opportunity, the controller assigns an index other than the index assigned to the first RACH opportunity to the second RACH opportunity.

12. The terminal according to claim 10, in, In determining the index of the second RACH opportunity, the controller sequentially allocates the indexes to the valid RACH opportunities in the SBFD resource configuration information based on a time order, and does not use the index to be allocated to the first RACH opportunity.

13. The terminal according to claim 10, in, When determining the index of the second RACH opportunity, the controller sequentially allocates the indexes to the valid RACH opportunities in the SBFD resource configuration information based on the time order and skips the index to be allocated to the first RACH opportunity to allocate the index to the RACH opportunity later in time.

14. The terminal according to claim 10, in, When determining the index of the second RACH opportunity, the controller allocates the index of the second RACH opportunity in the TDD cycle identically to the index allocated to the first RACH opportunity in the TDD cycle based on the TDD resource configuration information.

15. The terminal according to claim 10, in, The controller is further configured to transmit a physical random access channel (PRACH) preamble only in a second RACH opportunity excluding the first RACH opportunity.

Images