Method and apparatus for transmitting msg3 pusch in wireless communication system

Abstract

The present disclosure provides a random access method in a wireless communication system. Specifically, a method performed by a terminal in a wireless communication system comprises the steps of: transmitting a random access preamble; receiving a random access response (RAR) in response to the random access preamble, wherein the RAR includes an uplink (UL) grant for scheduling physical uplink shared channel (PUSCH) transmission; determining frequency domain resource allocation for the PUSCH transmission on the basis of the UL grant; and transmitting a message 3 (Msg3) on a PUSCH on the basis of the frequency domain resource allocation, wherein if the PUSCH transmission is scheduled in a UL frequency subband within a downlink symbol, resource block (RB) numbering starts from the first RB of the UL frequency subband, and the maximum number of RBs for the frequency domain resource allocation may be determined on the basis of the number of RBs in an initial UL bandwidth part (BWP).

Description

Method and device for MSG3 PUSCH transmission in a wireless communication system

[0001] The present disclosure relates to the operation of a terminal and a base station in a wireless communication system. Specifically, the present disclosure relates to a method and device for performing message 3 (Msg3) PUSCH (physical uplink shared channel) transmission.

[0002] 5G (5th generation) mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz band (for example, 3 terahertz (3THz) band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.

[0003] In the early stages of 5G mobile communication technology, the goal is to support services and satisfy performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.

[0004] Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, and physical layer standardization is in progress for technologies such as V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience based on their own location and status information transmitted by vehicles, NR-U (New Radio Unlicensed) for the purpose of system operation that complies with various regulatory requirements in unlicensed bands, NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, and Positioning.

[0005] In addition, standardization of wireless interface architecture / protocols is in progress for technologies such as intelligent factories (Industrial Internet of Things, IIoT) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) that provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement technology including Conditional Handover and Dual Active Protocol Stack (DAPS) handover, and 2-step random access (2-step RACH for NR) that simplifies random access procedures. Standardization is also in progress for system architecture / services such as 5G baseline architecture (e.g., Service-based Architecture, Service-based Interface) for grafting Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) that provides services based on the location of the terminal.

[0006] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.

[0008] As described above and with the development of wireless communication systems, various services have become available, and methods for providing these services smoothly are required.

[0009] An embodiment of the present disclosure seeks to provide a device and method capable of effectively providing a service in a mobile communication system.

[0010] Specifically, embodiments of the present disclosure provide a method for performing a random access procedure in SBFD (Subband non-overlapping full duplex) and a device therefor.

[0011] In addition, embodiments of the present disclosure provide a method for determining resources for physical uplink control channel (PUCCH) transmission in a SBFD uplink (UL) sub-band and a device therefor.

[0012] A method performed by a terminal in a wireless communication system according to one aspect of the present disclosure comprises the steps of transmitting a random access preamble, receiving a random access response (RAR) in response to the random access preamble, the RAR including an uplink (UL) grant for scheduling a physical uplink shared channel (PUSCH) transmission, determining a frequency domain resource allocation for the PUSCH transmission based on the UL grant, and transmitting message 3 (Msg3) in the PUSCH based on the frequency domain resource allocation, wherein when the PUSCH transmission is scheduled in a UL frequency subband within a downlink symbol, resource block (RB) numbering starts from a first RB of the UL frequency subband, and a maximum number of RBs for the frequency domain resource allocation is determined based on the number of RBs within an initial UL bandwidth part (BWP). Can be.

[0013] According to another aspect of the present disclosure, a method performed by a base station in a wireless communication system includes the steps of: receiving a random access preamble from a terminal; transmitting a random access response (RAR) to the terminal in response to the random access preamble, the RAR including an uplink (UL) grant scheduling a physical uplink shared channel (PUSCH) transmission; and receiving a message 3 (Msg3) on the PUSCH from the terminal, wherein frequency domain resource allocation for the PUSCH is based on the UL grant, and when the PUSCH transmission is scheduled in a UL frequency subband within a downlink symbol, resource block (RB) numbering starts from a first RB of the UL frequency subband, and a maximum number of RBs for the frequency domain resource allocation can be determined based on a number of RBs within an initial UL bandwidth portion (BWP).

[0014] In another aspect of the present disclosure, a wireless communication system includes a terminal including a transceiver and a processor operably connected to the transceiver, the processor configured to transmit a random access preamble and receive a random access response (RAR) in response to the random access preamble, the RAR including an uplink (UL) grant scheduling a physical uplink shared channel (PUSCH) transmission, determine a frequency domain resource allocation for the PUSCH transmission based on the UL grant, and transmit a message 3 (Msg3) on the PUSCH based on the frequency domain resource allocation, wherein when the PUSCH transmission is scheduled in a UL frequency subband within a downlink symbol, resource block (RB) numbering starts from a first RB of the UL frequency subband, and a maximum number of RBs for the frequency domain resource allocation may be determined based on a number of RBs within an initial UL bandwidth portion (BWP).

[0015] In another aspect of the present disclosure, in a wireless communication system, a base station includes a transceiver and a processor operably connected to the transceiver, the processor receiving a random access preamble from a terminal and transmitting a random access response (RAR) to the terminal in response to the random access preamble, the RAR including an uplink (UL) grant scheduling a physical uplink shared channel (PUSCH) transmission, and configured to receive a message 3 (Msg3) on the PUSCH from the terminal, a frequency domain resource allocation for the PUSCH being based on the UL grant, and when the PUSCH transmission is scheduled in a UL frequency subband within a downlink symbol, resource block (RB) numbering starting from a first RB of the UL frequency subband, and a maximum number of RBs for the frequency domain resource allocation being determined based on a number of RBs within an initial UL bandwidth portion (BWP).

[0016] According to one embodiment of the present disclosure, a service can be effectively provided in a mobile communication system.

[0017] Additionally, according to one embodiment of the present disclosure, resources for performing a random access procedure in SBFD can be determined, and the random access procedure can be performed according to the determined resources.

[0018] Additionally, according to one embodiment of the present disclosure, resources for PUCCH transmission can be determined in the UL subband of SBFD.

[0019] FIG. 1 is a diagram illustrating the basic structure of a time-frequency domain, which is a wireless resource domain in which data or control channels are transmitted, in a wireless communication system according to an embodiment of the present disclosure.

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

[0021] FIG. 3 is a diagram illustrating an example of bandwidth portion settings in a wireless communication system according to an embodiment of the present disclosure.

[0022] FIG. 4 is a diagram illustrating an example of a control region in which a downlink control channel is transmitted in a wireless communication system according to an embodiment of the present disclosure.

[0023] FIG. 5 is a diagram showing an example of a basic unit of time and frequency resources that constitute a downlink control channel in a wireless communication system according to an embodiment of the present disclosure.

[0024] FIG. 6 is a diagram for explaining a method for a base station and a terminal to transmit and receive data in consideration of a downlink data channel and rate matching resources in a wireless communication system according to an embodiment of the present disclosure.

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

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

[0027] FIG. 9 is a diagram illustrating an example of time axis resource allocation according to subcarrier spacing of a data channel and a control channel in a wireless communication system according to an embodiment of the present disclosure.

[0028] FIG. 10 is a diagram illustrating a wireless protocol structure of a base station and a terminal in a single cell, carrier aggregation, and dual connectivity situation in a wireless communication system according to an embodiment of the present disclosure.

[0029] FIG. 11 illustrates a random access procedure in a wireless communication system according to an embodiment of the present disclosure.

[0030] FIG. 12 is a diagram illustrating an example of SBFD operation in a TDD band of a wireless communication system according to an embodiment of the present disclosure.

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

[0032] FIG. 14 is a diagram illustrating a reference UL BWP according to one embodiment of the present disclosure.

[0033] FIG. 15 illustrates a case where an SBFD resource or UL subband is not included in a reference UL BWP according to an embodiment of the present disclosure.

[0034] FIG. 16 is a diagram illustrating an operation flow chart of a terminal according to an embodiment of the present disclosure.

[0035] FIG. 17 is a diagram illustrating an operation flow chart of a terminal according to an embodiment of the present disclosure.

[0036] FIG. 18 is a diagram illustrating the structure of a terminal in a wireless communication system according to an embodiment of the present disclosure.

[0037] FIG. 19 is a diagram illustrating the structure of a base station in a wireless communication system according to an embodiment of the present disclosure.

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

[0039] In describing the embodiments, descriptions of technical details that are well known in the technical field to which the present disclosure pertains and are not directly related to the present disclosure will be omitted. This is to more clearly convey the gist of the present disclosure without obscuring it by omitting unnecessary explanations.

[0040] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference numbers.

[0041] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided only to ensure that the disclosure of the present disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Like reference numerals designate like elements throughout the specification. In addition, when describing the present disclosure, if a specific description of a related function or configuration is determined to unnecessarily obscure the gist of the present disclosure, a detailed description thereof will be omitted. In addition, the terms described below are terms defined in consideration of the functions of the present disclosure, and may vary depending on the intention or custom of the user or operator. Therefore, their definitions should be made based on the contents throughout the specification.

[0042] Hereinafter, the base station is an entity that performs resource allocation of the terminal, and may be at least one of a gNode B, an eNode B, a Node B, a BS (Base Station), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In the present disclosure, downlink (DL) refers to a wireless transmission path of a signal transmitted from a base station to a terminal, and uplink (UL) refers to a wireless transmission path of a signal transmitted from a terminal to a base station. Hereinafter, embodiments of the present disclosure will be described using a 5G system as an example, but embodiments of the present disclosure may also be applied to other communication systems having a similar technical background or channel type. For example, this may include LTE or LTE-A mobile communication and mobile communication technologies developed after 5G. Furthermore, the present disclosure may be applied to other communication systems with some modifications, as determined by a person skilled in the art, without significantly departing from the scope of the present disclosure. The contents of the present disclosure are applicable to FDD (frequency division duplex) and TDD (time division duplex) systems.

[0043] At this time, it will be understood that each block of the processing flowchart drawings and combinations of the flowchart drawings can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flowchart block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce a manufactured item that includes an instruction means for performing the functions described in the flowchart block(s). Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, and the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also provide steps for performing the functions described in the flowchart block(s).

[0044] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.

[0045] Here, the term '~ part' used in the present embodiment means software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and the '~ part' performs certain roles. However, the '~ part' is not limited to software or hardware. The '~ part' may be configured to be on an addressable storage medium or may be configured to play one or more processors. Therefore, as an example, the '~ part' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and '~ parts' may be combined into a smaller number of components and '~ parts' or further separated into additional components and '~ parts'. Additionally, the components and '~parts' may be implemented to activate one or more CPUs within a device or secure multimedia card. Furthermore, in an embodiment, the '~part' may include one or more processors.

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

[0047] As a representative example of the above broadband wireless communication system, the LTE system adopts the OFDM (Orthogonal Frequency Division Multiplexing) method in the downlink (DL) and the SC-FDMA (Single Carrier Frequency Division Multiple Access) method in the uplink (UL). The uplink refers to a wireless link in which a terminal (User Equipment (UE) or Mobile Station (MS)) transmits data or control signals to a base station (eNode B or base station (BS)), and the downlink refers to a wireless link in which a base station transmits data or control signals to a terminal. The above multiple access method can distinguish the data or control information of each user by allocating and operating the time-frequency resources for transmitting data or control information to each user so that they do not overlap, that is, so as to achieve orthogonality.

[0048] As a future communications system beyond LTE, 5G communication systems must be able to freely reflect the diverse needs of users and service providers. Therefore, they must support services that simultaneously satisfy these diverse requirements. Services being considered for 5G communication systems include enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), and Ultra Reliability Low Latency Communication (URLLC).

[0049] eMBB aims to provide data transmission rates that are significantly higher than those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, eMBB must be able to support a peak data rate of 20 Gbps in the downlink and a peak data rate of 10 Gbps in the uplink from the perspective of a single base station. Furthermore, 5G communication systems must simultaneously provide the peak data rate and an increased user-perceived data rate for terminals. To meet these requirements, improvements in various transmission and reception technologies, including improved multi-input, multi-output (MIMO) transmission technology, are required. Furthermore, while LTE transmits signals using a maximum transmission bandwidth of 20 MHz in the 2 GHz band, 5G communication systems can meet the data transmission rates required by 5G communication systems by using a wider frequency bandwidth than 20 MHz in the 3-6 GHz or higher 6 GHz band.

[0050] At the same time, mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To efficiently provide the IoT, mMTC requires supporting large-scale terminal connections within a cell, improved terminal coverage, enhanced battery life, and reduced terminal costs. The IoT requires the ability to support a large number of terminals (e.g., 1,000,000 terminals / km2) within a cell, as it provides communication capabilities through the attachment of various sensors and devices. Furthermore, due to the nature of the service, terminals supporting mMTC are likely to be located in shadow areas, such as basements, beyond cell coverage. This may require broader coverage compared to other services provided by 5G communication systems. Terminals supporting mMTC must be inexpensive, and since frequent battery replacement is unlikely, they may require extremely long battery lifespans, such as 10 to 15 years.

[0051] Finally, URLLC refers to a cellular-based wireless communication service used for a specific purpose (mission-critical). For example, services such as remote control of robots or machinery, industrial automation, unmanned aerial vehicles, remote health care, and emergency alerts can be considered. Therefore, the communication provided by URLLC must provide very low latency and very high reliability. For example, a service supporting URLLC must satisfy an air interface latency of less than 0.5 milliseconds and, at the same time, must have a 10 -5The following packet error rate (PER) requirements apply. Therefore, for services supporting URLLC, 5G systems must provide a smaller Transmit Time Interval (TTI) than other services. Simultaneously, design considerations may require the allocation of extensive resources in the frequency band to ensure communication link reliability.

[0052] The three 5G services—eMBB, URLLC, and mMTC—can be multiplexed and transmitted within a single system. To meet the differing requirements of each service, different transmission and reception techniques and parameters can be used. Of course, 5G is not limited to the three services described above.

[0053] [NR time-frequency resources]

[0054] Below, the frame structure of the 5G system is described in more detail with reference to drawings.

[0055] FIG. 1 is a diagram illustrating the basic structure of a time-frequency domain, which is a wireless resource domain in which data or control channels are transmitted, in a wireless communication system according to an embodiment of the present disclosure.

[0056] Referring to Figure 1, the horizontal axis represents the time domain and the vertical axis represents the frequency domain. The basic unit of resources in the time and frequency domains is a resource element (RE, 101), which can be defined as 1 OFDM (Orthogonal Frequency Division Multiplexing) symbol (102) in the time axis and 1 subcarrier (103) in the frequency axis. In the frequency domain (For example, 12) consecutive REs can form one resource block (RB, 104). In the time domain, one subframe (110) can be composed of one or more slots.

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

[0058] Figure 2 illustrates an example of a structure of a frame (Frame, 200), a subframe (Subframe, 201), and a slot (Slot, 202, 203). One frame (200) can be defined as 10ms. One subframe (201) can be defined as 1ms, and therefore one frame (200) can be composed of a total of 10 subframes (201). One slot (202, 203) can be defined as 14 OFDM symbols (i.e., the number of symbols per slot ( )=14). 1 subframe (201) may be composed of one or more slots (202, 203), and the number of slots (202, 203) per 1 subframe (201) may vary depending on the setting value μ (204, 205) for the subcarrier spacing. In an example of FIG. 2, the cases where μ = 0 (204) and μ = 1 (205) as the subcarrier spacing setting value are illustrated. When μ = 0 (204), 1 subframe (201) may be composed of 1 slot (202), and when μ = 1 (205), 1 subframe (201) may be composed of 2 slots (203). That is, the number of slots per 1 subframe ( ) may vary, and accordingly the number of slots per frame ( ) may vary. Depending on the subcarrier spacing setting μ and can be defined as shown in Table 1 below.

[0059]

[0060] [Bandwidth Part (BWP)]

[0061] Next, the bandwidth part (BWP) setting in the 5G communication system will be explained in detail with reference to the drawing.

[0062] FIG. 3 is a diagram illustrating an example of bandwidth portion settings in a wireless communication system according to an embodiment of the present disclosure.

[0063] Figure 3 shows an example in which the UE bandwidth (300) is set to two bandwidth portions, namely, bandwidth portion #1 (BWP#1) (301) and bandwidth portion #2 (BWP#2) (302). The base station can set one or more bandwidth portions to the UE, and can set information such as Table 2 below for each bandwidth portion.

[0064]

[0065] Of course, the above example is not limited, and in addition to the above configuration information, various parameters related to the bandwidth portion can be configured for the terminal. The above information can be transmitted from the base station to the terminal via upper layer signaling, for example, RRC (Radio Resource Control) signaling. At least one bandwidth portion among the configured one or more bandwidth portions can be activated. Whether or not the configured bandwidth portion is activated can be semi-statically transmitted from the base station to the terminal via RRC signaling or dynamically transmitted via DCI (Downlink Control Information).

[0066] According to some embodiments, a terminal before RRC connection can receive the initial bandwidth portion (Initial BWP) for initial access from a base station through a Master Information Block (MIB). More specifically, the terminal can receive, through the MIB, configuration information about a control region (Control Resource Set, CORESET) and a search space where a PDCCH for receiving system information (which may correspond to Remaining System Information (RMSI) or System Information Block 1 (SIB1)) required for initial access and a PDCCH can be transmitted during the initial access phase. The control region and search space configured by the MIB may each be regarded as identifier (ID) 0. The base station can notify the terminal of configuration information such as frequency allocation information, time allocation information, and numerology for control region #0 through the MIB. In addition, the base station can notify the terminal of configuration information about the monitoring cycle and occasion for control region #0, i.e., configuration information for search space #0, through the MIB. The terminal may consider the frequency range set as control area #0 obtained from the MIB as the initial bandwidth portion for initial connection. At this time, the identifier (ID) of the initial bandwidth portion may be considered as 0.

[0067] The settings for the bandwidth supported by the above 5G can be used for various purposes.

[0068] In some embodiments, when the bandwidth supported by a terminal is smaller than the system bandwidth, this can be supported through bandwidth portion configuration. For example, the base station can configure the bandwidth portion frequency location (configuration information 2) for the terminal, thereby allowing the terminal to transmit and receive data at a specific frequency location within the system bandwidth.

[0069] Additionally, in some embodiments, a base station may configure multiple bandwidth segments for a terminal to support different numerologies. For example, to support data transmission and reception using both 15 kHz and 30 kHz subcarrier spacing for a given terminal, two bandwidth segments may be configured with subcarrier spacings of 15 kHz and 30 kHz, respectively. The different bandwidth segments may be frequency-division multiplexed, and when data is to be transmitted and received using a specific subcarrier spacing, the bandwidth segment configured for that subcarrier spacing may be activated.

[0070] Furthermore, in some embodiments, the base station may configure bandwidth portions with different bandwidth sizes for the terminal to reduce power consumption. For example, if the terminal supports a very large bandwidth, such as 100 MHz, and constantly transmits and receives data using that bandwidth, this may result in very high power consumption. In particular, monitoring unnecessary downlink control channels using a large bandwidth of 100 MHz in a traffic-free environment may be very inefficient in terms of power consumption. To reduce power consumption, the base station may configure a bandwidth portion with a relatively small bandwidth, such as 20 MHz, for the terminal. In a traffic-free environment, the terminal may perform monitoring operations in the 20 MHz bandwidth portion, and when data is generated, it may transmit and receive data using the 100 MHz bandwidth portion according to the instructions of the base station.

[0071] In the method for setting the bandwidth part, terminals before RRC connection (Connected) can receive setting information for the initial bandwidth part through the MIB (Master Information Block) in the initial access stage. More specifically, the terminal can set a control region (Control Resource Set, CORESET) for a downlink control channel on which DCI (Downlink Control Information) for scheduling a SIB (System Information Block) can be transmitted from the MIB of the PBCH (Physical Broadcast Channel). The bandwidth of the control region set by the MIB can be regarded as the initial bandwidth part, and the terminal can receive the PDSCH (Physical Downlink Shared Channel) on which the SIB is transmitted through the set initial bandwidth part. In addition to the purpose of receiving the SIB, the initial bandwidth part can also be utilized for other system information (Other System Information, OSI), paging, and random access.

[0072] [Bandwidth Part (BWP) Change]

[0073] When one or more bandwidth part values ​​are set for a terminal, the base station can instruct the terminal to change (or switch, transition) the bandwidth part value using the bandwidth part indicator field in the DCI. For example, in FIG. 3, when the currently activated bandwidth part of the terminal is bandwidth part #1 (301), the base station can instruct the terminal to bandwidth part #2 (302) using the bandwidth part indicator in the DCI, and the terminal can perform a bandwidth part change to bandwidth part #2 (302) indicated by the bandwidth part indicator in the received DCI.

[0074] As described above, since DCI-based bandwidth part change can be indicated by DCI scheduling PDSCH or PUSCH, when a terminal receives a bandwidth part change request, it must be able to receive or transmit PDSCH or PUSCH scheduled by the corresponding DCI without difficulty in the changed bandwidth part. To this end, the standard stipulates the delay time (T) required when changing the bandwidth part. BWP ) and can be defined as in Table 3, for example.

[0075]

[0076] The bandwidth-partial change delay time requirement supports Type 1 or Type 2 depending on the terminal's capability. The terminal can report the supported bandwidth-partial delay time type to the base station.

[0077] According to the requirement for bandwidth part change delay time mentioned above, when the terminal receives DCI including bandwidth part change indicator in slot n, the terminal changes to the new bandwidth part indicated by the bandwidth part change indicator in slot n+T. BWP The completion can be done at a later time, and transmission and reception for the data channel scheduled by the DCI can be performed in the new bandwidth portion that has been changed. When the base station wants to schedule a data channel in the new bandwidth portion, the terminal's bandwidth portion change delay time (T BWP ), time domain resource allocation for the data channel can be determined. That is, when the base station schedules the data channel with a new bandwidth portion, the data channel can be scheduled after the bandwidth portion change delay time in the method of determining the time domain resource allocation for the data channel. Accordingly, the terminal can determine whether the DCI instructing the bandwidth portion change is after the bandwidth portion change delay time (T BWP) may not be expected to indicate a slot offset (K0 or K2) value smaller than that.

[0078] If the terminal receives DCI (e.g., DCI format 1_1 or 0_1) indicating a bandwidth change, the terminal may not perform any transmission or reception during the time period from the third symbol of the slot in which the PDCCH including the DCI is received to the start point of the slot indicated by the slot offset (K0 or K2) value indicated by the time domain resource allocation indicator field in the DCI. For example, if the terminal receives DCI indicating a bandwidth change in slot n and the slot offset value indicated by the DCI is K, the terminal may not perform any 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).

[0079] [SS / PBCH block]

[0080] Next, we will explain the SS (Synchronization Signal) / PBCH block in 5G.

[0081] An SS / PBCH block may refer to a physical layer channel block consisting of a PSS (Primary SS), SSS (Secondary SS), and PBCH. Specifically, it is as follows.

[0082] - PSS: A signal that serves as a reference for downlink time / frequency synchronization and provides some information about the cell ID.

[0083] - SSS: It serves as a reference for downlink time / frequency synchronization and provides the remaining cell ID information not provided by PSS. Additionally, it can serve as a reference signal for PBCH demodulation.

[0084] - PBCH: Provides essential system information required for the terminal's data channel and control channel transmission and reception. Essential system information may include search space-related control information indicating radio resource mapping information for the control channel, and scheduling control information for a separate data channel that transmits system information.

[0085] - SS / PBCH Block: An SS / PBCH block is composed of a combination of PSS, SSS, and PBCH. One or more SS / PBCH blocks can be transmitted within a 5ms period, and each transmitted SS / PBCH block can be distinguished by an index.

[0086] The terminal can detect PSS and SSS in the initial access stage, and decode PBCH. The terminal can obtain MIB from PBCH, and can set control region (Control Resource Set; CORESET) #0 (which may correspond to a control region with a control region index of 0) therefrom. The terminal can monitor control region #0, assuming that the selected SS / PBCH block and the DMRS (Demodulation Reference Signal) transmitted in control region #0 are QCL (Quasi Co Location). The terminal can receive system information through downlink control information transmitted in control region #0. The terminal can obtain RACH (Random Access Channel) related configuration information required for initial access from the received system information. The terminal can transmit PRACH (Physical RACH) to the base station considering the selected SS / PBCH index, and the base station receiving the PRACH can obtain information on the SS / PBCH block index selected by the terminal. The base station can know that the terminal has selected a block among each SS / PBCH block and monitors the control region #0 associated with it.

[0087] [PDCCH: DCI related]

[0088] Next, we will specifically explain downlink control information (DCI) in the 5G system.

[0089] In a 5G system, scheduling information for uplink data (or physical uplink shared channel (PUSCH)) or downlink data (or physical downlink shared channel (PDSCH)) is transmitted from a base station to a terminal via DCI. The terminal can monitor a DCI format for fallback and a DCI format for non-fallback for the PUSCH or PDSCH. The fallback DCI format can be composed of fixed fields defined between the base station and the terminal, and the non-fallback DCI format can include configurable fields.

[0090] DCI can be transmitted through the Physical Downlink Control Channel (PDCCH) after going through the channel coding and modulation process. A Cyclic Redundancy Check (CRC) is attached to the DCI message payload, and the CRC can be scrambled with a Radio Network Temporary Identifier (RNTI) corresponding to the identity of the UE. Different RNTIs can be used depending on the purpose of the DCI message, such as UE-specific data transmission, power control command, or random access response. That is, the RNTI is not transmitted explicitly, but is included in the CRC calculation process. When the UE receives a DCI message transmitted on the PDCCH, it verifies the CRC using the assigned RNTI. If the CRC verification result is correct, the UE can determine that the message was transmitted to the UE.

[0091] For example, a DCI scheduling a PDSCH for System Information (SI) may be scrambled with SI-RNTI. A DCI scheduling a PDSCH for a Random Access Response (RAR) message may be scrambled with RA-RNTI. A DCI scheduling a PDSCH for a Paging message may be scrambled with P-RNTI. A DCI notifying a Slot Format Indicator (SFI) may be scrambled with SFI-RNTI. A DCI notifying a Transmit Power Control (TPC) may be scrambled with TPC-RNTI. A DCI scheduling a UE-specific PDSCH or PUSCH may be scrambled with C-RNTI (Cell RNTI).

[0092] DCI format 0_0 can be used as a fallback DCI for scheduling PUSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 0_0 with the CRC scrambled with C-RNTI can include, for example, the information in Table 4.

[0093]

[0094] DCI format 0_1 ​​can be used as a fallback DCI for scheduling PUSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 0_1 ​​with the CRC scrambled with C-RNTI can include, for example, the information in Table 5.

[0095]

[0096]

[0097] DCI format 1_0 can be used as a fallback DCI for scheduling PDSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 1_0 with the CRC scrambled with C-RNTI can include, for example, the information in Table 6.

[0098]

[0099] DCI format 1_1 can be used as a fallback DCI for scheduling PDSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 1_1 with the CRC scrambled with C-RNTI can include, for example, the information in Table 7.

[0100]

[0101] [PDCCH: CORESET, REG, CCE, Search Space]

[0102] Below, the downlink control channel in a 5G communication system will be described in more detail with reference to drawings.

[0103] FIG. 4 is a diagram illustrating an example of a control region (Control Resource Set, CORESET) in which a downlink control channel is transmitted in a wireless communication system according to an embodiment of the present disclosure.

[0104] FIG. 4 illustrates an example in which two control regions (Control Region #1 (401), Control Region #2 (402)) are set within a UE bandwidth part (410) in the frequency axis and within one slot (420) in the time axis. The control regions (401, 402) can be set to specific frequency resources (403) within the entire UE bandwidth part (410) in the frequency axis. The time axis can be set to one or more OFDM symbols, which can be defined as the control region length (Control Resource Set Duration, 404). Referring to the example illustrated in FIG. 4, Control Region #1 (401) is set to a control region length of two symbols, and Control Region #2 (402) is set to a control region length of one symbol.

[0105] In the aforementioned 5G, the control region can be established by the base station to the terminal via higher-layer signaling (e.g., system information, Master Information Block (MIB), Radio Resource Control (RRC) signaling). Establishing a control region for the terminal means providing information such as the control region identifier, the frequency location of the control region, and the symbol length of the control region. For example, this information may include the information in Table 8.

[0106]

[0107] In Table 8, the tci-StatesPDCCH (simply named TCI (Transmission Configuration Indication) state) configuration information may include information on one or more SS (Synchronization Signal) / PBCH (Physical Broadcast Channel) block indices or CSI-RS (Channel State Information Reference Signal) indices that are in a QCL (Quasi Co Located) relationship with the DMRS transmitted in the corresponding control region.

[0108] FIG. 5 is a diagram showing an example of a basic unit of time and frequency resources that constitute a downlink control channel in a wireless communication system according to an embodiment of the present disclosure.

[0109] Referring to FIG. 5, the basic unit of time and frequency resources constituting the control channel can be referred to as a REG (Resource Element Group, 503), and the REG (503) can be defined as 1 OFDM symbol (501) on the time axis and 1 PRB (Physical Resource Block, 502) on the frequency axis, i.e., 12 subcarriers. The base station can concatenate REGs (503) to form a downlink control channel allocation unit.

[0110] As illustrated in FIG. 5, if the basic unit to which a downlink control channel is allocated in 5G is called a CCE (Control Channel Element, 504), 1 CCE (504) can be composed of multiple REGs (503). Taking the REG (503) illustrated in FIG. 5 as an example, the REG (503) can be composed of 12 REs, and if 1 CCE (504) is composed of 6 REGs (503), 1 CCE (504) can be composed of 72 REs. When a downlink control region is set, the region can be composed of multiple CCEs (504), and a specific downlink control channel can be mapped to one or multiple CCEs (504) and transmitted according to the aggregation level (AL) within the control region. CCEs (504) within the control area are distinguished by numbers, and the numbers of the CCEs (504) can be assigned according to a logical mapping method.

[0111] The basic unit of the downlink control channel illustrated in FIG. 5, that is, the REG (503), may include both the REs to which the DCI is mapped and the areas to which the DMRS (505), which is a reference signal for decoding the REs, is mapped. As shown in FIG. 5, three DMRSs (505) may be transmitted within one REG (503). The number of CCEs required to transmit the PDCCH may be 1, 2, 4, 8, or 16 depending on the aggregation level (AL), and different numbers of CCEs may be used to implement link adaptation of the downlink control channel. For example, when AL = L, one downlink control channel may be transmitted through L CCEs. The terminal must detect a signal without knowing information about the downlink control channel, and a search space representing a set of CCEs is defined for blind decoding. A search space is a set of downlink control channel candidates (CCEs) that a terminal must attempt to decode at a given aggregation level. Since there are multiple aggregation levels, each of which can be a set of 1, 2, 4, 8, or 16 CCEs, a terminal can have multiple search spaces. A search space set can be defined as the set of search spaces at all configured aggregation levels.

[0112] Search spaces can be categorized into common search spaces and UE-specific search spaces. A certain group of UEs, or all UEs, can search the common search space of the PDCCH to receive cell-common control information, such as dynamic scheduling of system information or paging messages. For example, PDSCH scheduling allocation information for transmitting SIBs, including cell operator information, can be received by searching the common search space of the PDCCH. In the case of the common search space, since a certain group of UEs, or all UEs, must receive the PDCCH, it can be defined as a set of pre-arranged CCEs. Scheduling allocation information for UE-specific PDSCH or PUSCH can be received by searching the UE-specific search space of the PDCCH. The UE-specific search space can be defined UE-specifically as a function of the UE's identity and various system parameters.

[0113] In 5G, parameters for the search space for PDCCH can be configured from the base station to the terminal via higher-layer signaling (e.g., SIB, MIB, RRC signaling). For example, the base station can configure the number of PDCCH candidates at each aggregation level L, the monitoring period for the search space, the monitoring occasion for each symbol within the slot for the search space, the search space type (common search space or terminal-specific search space), the combination of DCI format and RNTI to be monitored in the corresponding search space, the control region index to be monitored for the search space, etc. to the terminal. For example, the information in Table 9 can be included.

[0114]

[0115] Depending on the configuration information, the base station may configure one or more search space sets for the terminal. In some embodiments, the base station may configure search space set 1 and search space set 2 for the terminal, and configure the terminal to monitor DCI format A scrambled with X-RNTI in search space set 1 in a common search space, and configure the terminal to monitor DCI format B scrambled with Y-RNTI in search space set 2 in a terminal-specific search space.

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

[0117] In the common search space, the following combinations of DCI formats and RNTIs can be monitored. Of course, the examples below are not limited to these.

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

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

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

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

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

[0123] In a terminal-specific search space, the following combinations of DCI formats and RNTIs can be monitored. Of course, the examples below are not limited to these examples.

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

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

[0126] The RNTIs specified may follow the definitions and uses below.

[0127] C-RNTI (Cell RNTI): For terminal-specific PDSCH scheduling purposes

[0128] TC-RNTI (Temporary Cell RNTI): For terminal-specific PDSCH scheduling purposes

[0129] CS-RNTI (Configured Scheduling RNTI): Used for terminal-specific PDSCH scheduling that is set semi-statically.

[0130] RA-RNTI (Random Access RNTI): Used for PDSCH scheduling in the random access phase.

[0131] P-RNTI (Paging RNTI): Used for scheduling PDSCH where paging is transmitted.

[0132] SI-RNTI (System Information RNTI): Used for scheduling PDSCH where system information is transmitted.

[0133] INT-RNTI (Interruption RNTI): Used to indicate whether PDSCH is punctured.

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

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

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

[0137] The aforementioned specified DCI formats may follow definitions such as the examples in Table 10.

[0138]

[0139] In 5G, the search space of aggregation level L in the control region p and search space set s can be expressed as in the following mathematical expression 1.

[0140] [Mathematical Formula 1]

[0141]

[0142] - L: Integration level

[0143] - : Carrier Index

[0144] - : Total number of CCEs existing within the control region p

[0145] - : slot index

[0146] - : Number of PDCCH candidates for aggregation level L

[0147] - = 0,..., -1: PDCCH candidate index of aggregation level L

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

[0149] - , , , , , D=65537.

[0150] - : Terminal identifier

[0151] The value can be 0 for a common search space.

[0152] In the case of a terminal-specific search space, the value may correspond to a value that changes depending on the terminal's identity (C-RNTI or ID set to the terminal by the base station) and the time index.

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

[0154] FIG. 6 is a diagram for explaining a method for a base station and a terminal to transmit and receive data in consideration of a downlink data channel and rate matching resources in a wireless communication system according to an embodiment of the present disclosure.

[0155] FIG. 6 illustrates a downlink data channel (PDSCH, 601) and a rate matching resource (602). A base station can configure one or more rate matching resources (602) to a terminal through upper layer signaling (e.g., RRC signaling). Rate matching resource (602) configuration information may include time-domain resource allocation information (603), frequency-domain resource allocation information (604), and period information (605). In the following, the bitmap corresponding to the frequency-domain resource allocation information (604) is named "the first bitmap", the bitmap corresponding to the time-domain resource allocation information (603) is named "the second bitmap", and the bitmap corresponding to the period information (605) is named "the third bitmap". If all or part of the time and frequency resources of the scheduled data channel (601) overlap with the set rate matching resources (602), the base station can rate-match and transmit the data channel (601) in the rate matching resource (602) portion, and the terminal can perform reception and decoding after assuming that the data channel (601) is rate-matched in the rate matching resource (602) portion.

[0156] The base station can dynamically notify the terminal via DCI whether to rate-match the data channel in the set rate-matching resource portion through additional configuration (corresponding to the "rate-matching indicator" in the DCI format described above). Specifically, the base station can select some of the set rate-matching resources and group them into rate-matching resource groups, and can use a bitmap to indicate to the terminal via DCI whether the data channel for each rate-matching resource group is rate-matched. For example, if four rate-matching resources, RMR#1, RMR#2, RMR#3, and RMR#4, are set, the base station can set RMG#1={RMR#1, RMR#2}, RMG#2={RMR#3, RMR#4} as the rate-matching groups, and can use two bits in the DCI field to indicate to the terminal whether to rate-match in RMG#1 and RMG#2, respectively, using a bitmap. For example, if rate matching is required, it can be indicated as "1", and if rate matching is not required, it can be indicated as "0".

[0157] 5G supports granularity at the "RB symbol level" and "RE level" by setting the aforementioned rate matching resources on the terminal. More specifically, the following setting method can be followed.

[0158] RB symbol level

[0159] A terminal can receive up to four RateMatchPatterns for each bandwidth section through upper layer signaling, and one RateMatchPattern can include the following contents.

[0160] - As a reserved resource within the bandwidth section, a resource in which the time and frequency resource domains of the reserved resource are set by combining a bitmap at the RB level and a bitmap at the symbol level along the frequency axis may be included. The reserved resource may span one or two slots. A time domain pattern (periodicityAndPattern) in which the time and frequency domains composed of each RB level and symbol level bitmap pair are repeated may additionally be set.

[0161] - It may include a time and frequency domain resource area set as a control resource set within the bandwidth section and a resource area corresponding to a time domain pattern set as a search space setting in which the resource area is repeated.

[0162] RE level

[0163] The terminal can be configured with the following contents through upper layer signaling.

[0164] - The configuration information (lte-CRS-ToMatchAround) for RE corresponding to the LTE CRS (Cell-specific Reference Signal or Common Reference Signal) pattern may include the number of LTE CRS ports (nrofCRS-Ports) and the LTE-CRS-vshift(s) value (v-shift), the location information (carrierFreqDL) of the center subcarrier of the LTE carrier from the reference frequency point (e.g., reference point A), the bandwidth size (carrierBandwidthDL) information of the LTE carrier, and the subframe configuration information (mbsfn-SubframConfigList) corresponding to the MBSFN (Multicast-broadcast single-frequency network). Based on the above-described information, the terminal can determine the location of the CRS within the NR slot corresponding to the LTE subframe.

[0165] - It may include configuration information for a set of resources corresponding to one or more ZP (Zero Power) CSI-RSs within the bandwidth section.

[0166] [PDSCH: Frequency Resource Allocation Related]

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

[0168] FIG. 7 is a diagram illustrating three frequency axis resource allocation methods, type 0 (7-00), type 1 (7-05), and dynamic switch (7-10), which can be set through an upper layer in an NR wireless communication system.

[0169] Referring to FIG. 7, if a terminal is configured to use only resource type 0 through upper layer signaling (7-00), some downlink control information (DCI) that allocates PDSCH to the terminal includes a bitmap consisting of NRBG bits. The conditions for this will be explained later. At this time, NRBG means the number of RBGs (resource block groups) determined according to the BWP size allocated by the BWP indicator and the upper layer parameter rbg-Size as shown in [Table 11] below, and data is transmitted to the RBG indicated as 1 by the bitmap.

[0170]

[0171] If the terminal is configured to use only resource type 1 through upper layer signaling (7-05), some DCIs that allocate PDSCH to the terminal It contains frequency axis resource allocation information consisting of bits. The conditions for this will be explained later. Through this, the base station can set the starting VRB (7-20) and the length of frequency axis resources (7-25) allocated continuously therefrom.

[0172] If a terminal is configured to use both resource type 0 and resource type 1 through upper layer signaling (7-10), some DCIs that allocate PDSCH to the terminal include frequency-axis resource allocation information consisting of bits of the larger value (7-35) among the payload (7-15) for configuring resource type 0 and the payload (7-20, 7-25) for configuring resource type 1. The conditions for this will be explained later. At this time, one bit may be added to the first part (MSB) of the frequency-axis resource allocation information in the DCI, and if the bit has a value of '0', it may indicate that resource type 0 is used, and if the bit has a value of '1', it may indicate that resource type 1 is used.

[0173] [PDSCH / PUSCH: Time Resource Allocation Related]

[0174] Below, a time domain resource allocation method for data channels in next-generation mobile communication systems (5G or NR systems) is described.

[0175] A base station can set up a table for time domain resource allocation information for a downlink data channel (Physical Downlink Shared Channel, PDSCH) and an uplink data channel (Physical Uplink Shared Channel, PUSCH) to a terminal through higher layer signaling (e.g., RRC signaling). A table with up to maxNrofDL-Allocations=16 entries can be set up for PDSCH, and a table with up to maxNrofUL-Allocations=16 entries can be set up for PUSCH. In one embodiment, the time domain resource allocation information may include PDCCH-to-PDSCH slot timing (corresponding to the time interval in slot units between the time point of receiving a PDCCH and the time point of transmitting a PDSCH scheduled by the received PDCCH, denoted as K0), PDCCH-to-PUSCH slot timing (corresponding to the time interval in slot units between the time point of receiving a PDCCH and the time point of transmitting a PUSCH scheduled by the received PDCCH, denoted as K2), information on the position and length of the start symbol for which a PDSCH or PUSCH is scheduled within a slot, a mapping type of the PDSCH or PUSCH, etc. For example, information such as [Table 12] or [Table 13] below may be transmitted from the base station to the terminal.

[0176]

[0177]

[0178] The base station may notify the terminal of one of the entries in the table for the time domain resource allocation information described above via L1 signaling (e.g., DCI) (e.g., indicated by the 'Time Domain Resource Allocation' field in the DCI). The terminal may obtain the time domain resource allocation information for the PDSCH or PUSCH based on the DCI received from the base station.

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

[0180] Referring to FIG. 8, the base station uses the upper layer to set the subcarrier spacing (SCS) (μ) of the data channel and the control channel. PDSCH ,μ PDCCH ), scheduling offset (K0) value, and the time axis position of the PDSCH resource can be indicated according to the OFDM symbol start position (8-00) and length (8-05) within a slot (8-10) dynamically indicated through DCI.

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

[0182] Referring to Figure 9, when the subcarrier spacing of the data channel and the control channel is the same (9-00,μ PDSCH = μ PDCCH), since the slot numbers for data and control are the same, the base station and the terminal can generate a scheduling offset according to the predetermined slot offset K0. On the other hand, if the subcarrier spacing of the data channel and the control channel are different (9-05,μ PDSCH ≠ μ PDCCH ), since the slot numbers for data and control are different, the base station and the terminal can generate a scheduling offset according to a predetermined slot offset K0 based on the subcarrier interval of the PDCCH.

[0183] [PUSCH: Transmission method related]

[0184] Next, we describe the scheduling method for PUSCH transmission. PUSCH transmission can be dynamically scheduled by the UL grant within the DCI or can operate by configured grant Type 1 or Type 2. Dynamic scheduling instructions for PUSCH transmission are possible using DCI formats 0_0 or 0_1.

[0185] Configured grant Type 1 PUSCH transmission can be semi-statically configured by receiving configuredGrantConfig including rrc-ConfiguredUplinkGrant of [Table 14] through higher-level signaling, without receiving UL grant in DCI. Configured grant Type 2 PUSCH transmission can be semi-persistently scheduled by UL grant in DCI after receiving configuredGrantConfig not including rrc-ConfiguredUplinkGrant of [Table 14] through higher-level signaling. When PUSCH transmission operates by configured grant, parameters applied to PUSCH transmission are applied through configuredGrantConfig of [Table 14], which is higher-level signaling, except for dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, and scaling of UCI-OnPUSCH provided by pusch-Config of [Table 15]. If the terminal has been provided with transformPrecoder in configuredGrantConfig, which is the upper signaling of [Table 14], the terminal applies tp-pi2BPSK in pusch-Config of [Table 15] to PUSCH transmission operated by the configured grant.

[0186]

[0187] Next, the PUSCH transmission method is described. The DMRS antenna port for PUSCH transmission is the same as the antenna port for SRS transmission. PUSCH transmission can follow a codebook-based or non-codebook-based transmission method, respectively, depending on whether the value of txConfig in the upper signaling, pusch-Config in [Table 15], is 'codebook' or 'nonCodebook'.

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

[0189]

[0190] Next, we describe codebook-based PUSCH transmission. Codebook-based PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1, and can operate semi-statically based on a configured grant. When codebook-based PUSCH is dynamically scheduled via DCI format 0_1 ​​or semi-statically configured via a configured grant, the UE determines a precoder for PUSCH transmission based on the SRS Resource Indicator (SRI), Transmission Precoding Matrix Indicator (TPMI), and transmission rank (the number of PUSCH transmission layers).

[0191] At this time, the SRI can be given through the SRS resource indicator field in the DCI or configured through the srs-ResourceIndicator higher-level signaling. The UE is configured with at least one SRS resource when transmitting a codebook-based PUSCH, and can be configured with up to two. When the UE receives an SRI through the DCI, the SRS resource indicated by the SRI refers to the SRS resource corresponding to the SRI among the SRS resources transmitted before the PDCCH containing the SRI. In addition, the TPMI and transmission rank can be given through the precoding information and number of layers fields in the DCI or configured through the precodingAndNumberOfLayers higher-level 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 to the configured one SRS resource. When a terminal is configured with multiple SRS resources, TPMI is used to indicate the precoder to be applied in the SRS resource indicated through SRI.

[0192] The precoder to be used for PUSCH transmission is selected from an uplink codebook having the same number of antenna ports as the nrofSRS-Ports value in the upper layer signaling, SRS-Config. In codebook-based PUSCH transmission, the UE determines the codebook subset based on the TPMI and codebookSubset in the upper layer signaling, pusch-Config. The codebookSubset in the upper layer signaling, pusch-Config, can be set to one of 'fullyAndPartialAndNonCoherent', 'partialAndNonCoherent', or 'nonCoherent' based on the UE capability reported by the UE to the base station. If the UE reported 'partialAndNonCoherent' as the UE capability, the UE does not expect the value of codebookSubset in the upper layer signaling to be set to 'fullyAndPartialAndNonCoherent'. Additionally, if the UE reports 'nonCoherent' as the UE capability, the UE does not expect the value of the upper signaling codebookSubset to be set to 'fullyAndPartialAndNonCoherent' or 'partialAndNonCoherent'. If nrofSRS-Ports in the upper signaling SRS-ResourceSet points to two SRS antenna ports, the UE does not expect the value of the upper signaling codebookSubset to be set to 'partialAndNonCoherent'.

[0193] The terminal can be configured with one SRS resource set in which the usage value in the upper signaling SRS-ResourceSet is set to 'codebook', and one SRS resource in the SRS resource set can be indicated via SRI. If multiple SRS resources are configured in the SRS resource set in which the usage value in the upper signaling SRS-ResourceSet is set to 'codebook', the terminal expects that the value of nrofSRS-Ports in the upper signaling SRS-Resource is set to the same value for all SRS resources.

[0194] The terminal transmits to the base station one or more SRS resources included in the SRS resource set in which the usage value is set to 'codebook' according to upper signaling, and the base station selects one of the SRS resources transmitted by the terminal and instructs the terminal to perform PUSCH transmission using transmission beam information of the corresponding SRS resource. At this time, in codebook-based PUSCH transmission, the SRI is used as information for selecting an index of one SRS resource and is included in the DCI. Additionally, the base station includes in the DCI information indicating the TPMI and rank to be used by the terminal for PUSCH transmission. The terminal performs PUSCH transmission by applying the indicated rank and the precoder indicated by the TPMI based on the transmission beam of the corresponding SRS resource using the SRS resource indicated by the SRI.

[0195] Next, we describe non-codebook-based PUSCH transmission. Non-codebook-based PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1, and can operate semi-statically based on a configured grant. If at least one SRS resource is configured within an SRS resource set in which the usage value in the upper signaling SRS-ResourceSet is set to 'nonCodebook', the UE can be scheduled for non-codebook-based PUSCH transmission via DCI format 0_1.

[0196] For an SRS resource set in which the usage value in the upper signaling SRS-ResourceSet is set to 'nonCodebook', the UE can be configured with one connected NZP CSI-RS resource (non-zero power CSI-RS). The UE can perform calculations for a 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 at the UE is less than 42 symbols, the UE does not expect information about the precoder for SRS transmission to be updated.

[0197] If the value of resourceType in the upper signaling SRS-ResourceSet is set to 'aperiodic', the connected NZP CSI-RS is indicated by the SRS request field in DCI format 0_1 ​​or 1_1. At this time, if the connected NZP CSI-RS resource is an aperiodic NZP CSI-RS resource, the presence of the connected NZP CSI-RS is indicated when the value of the SRS request field in DCI format 0_1 ​​or 1_1 is not '00'. At this time, the DCI must not indicate cross-carrier or cross BWP scheduling. In addition, if the value of the SRS request indicates the presence of an NZP CSI-RS, the NZP CSI-RS is located in the slot in which the PDCCH including the SRS request field is transmitted. At this time, the TCI states set for the scheduled subcarriers are not set to QCL-TypeD.

[0198] If a periodic or semi-persistent SRS resource set is configured, the associated NZP CSI-RS can be indicated through the associatedCSI-RS in the upper-level signaling SRS-ResourceSet. For non-codebook-based transmission, the UE does not expect the upper-level signaling spatialRelationInfo for the SRS resource and the associatedCSI-RS in the upper-level signaling SRS-ResourceSet to be configured together.

[0199] When multiple SRS resources are configured, the UE can determine the precoder and transmission rank to be applied to PUSCH transmission based on the SRI indicated by the base station. At this time, the SRI can be indicated through the SRS resource indicator field in the DCI or can be set through the srs-ResourceIndicator, which is a higher-level signaling. Similar to the codebook-based PUSCH transmission described above, when the UE receives an SRI through the DCI, the SRS resource indicated by the SRI refers to the SRS resource corresponding to the SRI among the SRS resources transmitted before the PDCCH containing the SRI. The UE can use one or more SRS resources for SRS transmission, and the maximum number of SRS resources that can be simultaneously transmitted in the same symbol within one SRS resource set and the maximum number of SRS resources are determined by the UE capability reported by the UE to the base station. At this time, the SRS resources that the UE simultaneously transmits occupy the same RB. The UE configures one SRS port for each SRS resource. Only one SRS resource set with the usage value set to 'nonCodebook' in the upper signaling SRS-ResourceSet can be set, and up to four SRS resources for non-codebook based PUSCH transmission can be set.

[0200] The base station transmits one NZP-CSI-RS associated with an SRS resource set to the terminal, and the terminal calculates a precoder to be used when transmitting one or more SRS resources within the SRS resource set based on the result measured upon reception of the NZP-CSI-RS. When the terminal transmits one or more SRS resources within the SRS resource set with usage set to 'nonCodebook' to the base station, the terminal applies the calculated precoder, and the base station selects one or more SRS resources from the received one or more SRS resources. At this time, in non-codebook based PUSCH transmission, the SRI represents an index that can express a combination of one or more SRS resources, and the SRI is included in the DCI. At this time, the number of SRS resources indicated by the SRI transmitted by the base station can be the number of transmission layers of the PUSCH, and the terminal transmits the PUSCH by applying the precoder applied to SRS resource transmission to each layer.

[0201] [CA / DC related]

[0202] FIG. 10 is a diagram illustrating a wireless protocol structure of a base station and a terminal in a single cell, carrier aggregation, and dual connectivity situation according to an embodiment of the present disclosure.

[0203] Referring to FIG. 10, the wireless protocol of the next-generation mobile communication system is composed of NR SDAP (Service Data Adaptation Protocol S25, S70), NR PDCP (Packet Data Convergence Protocol S30, S65), NR RLC (Radio Link Control S35, S60), and NR MAC (Medium Access Control S40, S55) in the terminal and NR base station, respectively.

[0204] Key features of NR SDAP (S25, S70) may include some of the following:

[0205] - Transfer of user plane data

[0206] - Mapping function between QoS flow and data bearer for both DL and UL

[0207] - Marking function of QoS flow ID for both uplink and downlink (marking QoS flow ID in both DL and UL packets)

[0208] - Ability to map reflective QoS flow to data bearer for uplink SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).

[0209] For the above SDAP layer device, the terminal can be configured by RRC message for each PDCP layer device, each bearer, or each logical channel, whether to use the header of the SDAP layer device or whether to use the function of the SDAP layer device, and when the SDAP header is configured, the terminal can instruct the NAS QoS reflection configuration 1-bit indicator (NAS reflective QoS) and the AS QoS reflection configuration 1-bit indicator (AS reflective QoS) of the SDAP header to update or reset the mapping information for the QoS flow and data bearer of the uplink and downlink. The SDAP header can include QoS flow ID information indicating QoS. The QoS information can be used as data processing priority, scheduling information, etc. to support a smooth service.

[0210] The main functions of NR PDCP (S30, S65) may include some of the following functions:

[0211] - Header compression and decompression (ROHC only)

[0212] - User data transfer function

[0213] - In-sequence delivery of upper layer PDUs

[0214] - Out-of-sequence delivery of upper layer PDUs

[0215] - PDCP PDU reordering for reception

[0216] - Duplicate detection of lower layer SDUs

[0217] - Retransmission function (Retransmission of PDCP SDUs)

[0218] - Encryption and decryption functions (Ciphering and deciphering)

[0219] - Timer-based SDU discard in uplink.

[0220] The reordering function of the NR PDCP device above refers to a function of reordering PDCP PDUs received from a lower layer in order based on the PDCP SN (sequence number), and may include a function of transmitting data to an upper layer in the reordered order. Alternatively, the reordering function of the NR PDCP device may include a function of transmitting data directly without considering the order, a function of recording lost PDCP PDUs by reordering the order, a function of reporting a status of lost PDCP PDUs to the transmitting side, and a function of requesting retransmission of lost PDCP PDUs.

[0221] The main functions of NR RLC (S35, S60) may include some of the following functions:

[0222] - Data transfer function (Transfer of upper layer PDUs)

[0223] - In-sequence delivery of upper layer PDUs

[0224] - Out-of-sequence delivery of upper layer PDUs

[0225] - ARQ function (Error Correction through ARQ)

[0226] - Concatenation, segmentation and reassembly of RLC SDUs

[0227] - Re-segmentation of RLC data PDUs

[0228] - Reordering of RLC data PDUs

[0229] - Duplicate detection function

[0230] - Protocol error detection

[0231] - RLC SDU discard function

[0232] - RLC re-establishment function

[0233] In the above, the in-sequence delivery function of the NR RLC device refers to the function of sequentially delivering RLC SDUs received from a lower layer to an upper layer. The in-sequence delivery function of the NR RLC device may include a function of reassembling and delivering a single RLC SDU when it is received divided into multiple RLC SDUs, a function of rearranging received RLC PDUs based on the RLC SN (sequence number) or PDCP SN (sequence number), a function of recording lost RLC PDUs by rearranging the order, a function of reporting the status of lost RLC PDUs to the transmitting side, and a function of requesting retransmission of lost RLC PDUs. The in-sequence delivery function of an NR RLC device may include a function to sequentially deliver to the upper layer only the RLC SDUs up to the lost RLC SDU when there is a lost RLC SDU, or may include a function to sequentially deliver to the upper layer all RLC SDUs received before the timer starts if a predetermined timer has expired even if there is a lost RLC SDU. Alternatively, the in-sequence delivery function of an NR RLC device may include a function to sequentially deliver to the upper layer all RLC SDUs received up to the present if a predetermined timer has expired even if there is a lost RLC SDU.In addition, the RLC PDUs may be processed in the order in which they are received (in the order of arrival, regardless of the order of the sequence number) and delivered to the PDCP device out of order (out-of-sequence delivery). In the case of segments, the segments stored in the buffer or to be received later may be received, reconstructed into a complete RLC PDU, processed, and delivered to the PDCP device. The NR RLC layer may not include a concatenation function, and the function may be performed in the NR MAC layer or replaced with a multiplexing function of the NR MAC layer.

[0234] The out-of-sequence delivery function of the NR RLC device above refers to the function of directly delivering RLC SDUs received from a lower layer to an upper layer regardless of the order, and may include a function of reassembling and delivering RLC SDUs when an original RLC SDU is received divided into multiple RLC SDUs, and may include a function of storing the RLC SN or PDCP SN of received RLC PDUs and arranging the order to record lost RLC PDUs.

[0235] NR MAC (S40, S55) can be connected to multiple NR RLC layer devices configured in one terminal, and the main functions of NR MAC can include some of the following functions.

[0236] - Mapping function (Mapping between logical channels and transport channels)

[0237] - Multiplexing / demultiplexing of MAC SDUs

[0238] - Scheduling information reporting function

[0239] - HARQ function (Error correction through HARQ)

[0240] - Priority handling between logical channels of one UE

[0241] - Priority handling between UEs by means of dynamic scheduling

[0242] - MBMS service identification function

[0243] - Transport format selection function

[0244] - Padding function

[0245] The NR PHY layer (S45, S50) can perform operations such as channel coding and modulating upper layer data, converting it into OFDM symbols and transmitting it over a wireless channel, or demodulating and channel decoding OFDM symbols received over a wireless channel and transmitting them to a higher layer.

[0246] The above wireless protocol structure can have various detailed structures depending on the carrier (or cell) operation method. For example, when a base station transmits data to a terminal based on a single carrier (or cell), the base station and the terminal use a protocol structure that has a single structure for each layer, such as S00. On the other hand, when a base station transmits data to a terminal based on CA (carrier aggregation) that uses multiple carriers in a single TRP, the base station and the terminal use a protocol structure that has a single structure up to RLC, such as S10, but multiplexes the PHY layer through the MAC layer. As another example, when a base station transmits data to a terminal based on DC (dual connectivity) that uses multiple carriers in multiple TRPs, the base station and the terminal use a protocol structure that has a single structure up to RLC, such as S20, but multiplexes the PHY layer through the MAC layer.

[0247] Referring to the above-described PDCCH and beam configuration-related descriptions, the current Rel-15 and Rel-16 NR do not support repeated PDCCH transmission, making it difficult to achieve the required reliability in scenarios requiring high reliability, such as URLLC. The present invention provides a method for repeated PDCCH transmission through multiple transmission points (TRPs) to improve PDCCH reception reliability at a terminal. The specific method is described in detail in the following embodiments.

[0248] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings. The contents of the present disclosure can be applied to FDD and TDD systems. In the present disclosure below, upper signaling (or upper layer signaling) refers to a signal transmission method in which a base station transmits a signal to a terminal using a downlink data channel of a physical layer, or a terminal transmits a signal to a base station using an uplink data channel of a physical layer, and may also be referred to as RRC signaling, PDCP signaling, or MAC (medium access control) control element (MAC control element; MAC CE).

[0249] In the following description of the present disclosure, upper layer signaling may be signaling corresponding to at least one or a combination of one or more of the following signaling.

[0250] - MIB (Master Information Block)

[0251] - SIB (System Information Block) or SIB

[0252] - RRC (Radio Resource Control)

[0253] - MAC (Medium Access Control) CE (Control Element)

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

[0255] - PDCCH (Physical Downlink Control Channel)

[0256] - DCI (Downlink Control Information)

[0257] - UE-specific DCI

[0258] - Group common DCI

[0259] - Common DCI

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

[0261] - Non-scheduled DCI (e.g. DCI not intended for scheduling downlink or uplink data)

[0262] - PUCCH (Physical Uplink Control Channel)

[0263] - UCI (Uplink Control Information)

[0264] In the present disclosure, determining the priority between A and B may be referred to in various ways, such as selecting a higher priority according to a predetermined priority rule and performing an action corresponding to it, or omitting or dropping an action for a lower priority.

[0265] In the following disclosure, the above examples are described through a number of embodiments, but they are not independent, and one or more embodiments may be applied simultaneously or in combination.

[0266] [Random Access procedure in SBFD]

[0267] Meanwhile, 3GPP introduced SBFD (Subband Non-Overlapping Full Duplex) as a new NR-based duplex method. SBFD is a technology that allows a base station to receive uplink transmissions from terminals by increasing the uplink resources by utilizing a portion of downlink resources as uplink resources in a TDD band (spectrum) of 6 GHz or lower or 6 GHz or higher, thereby expanding the uplink coverage of the terminals, and receiving feedback from the terminals on downlink transmissions using the expanded uplink resources to reduce feedback delay. In the present disclosure, a terminal that receives information on whether SBFD is supported from a base station and can perform uplink transmissions using a portion of downlink resources may be conveniently referred to as an SBFD terminal (SBFD-capable UE). The following methods may be considered for defining the SBFD method in the standard and for an SBFD terminal to determine whether SBFD is supported in a specific cell (or frequency, frequency band).

[0268] First method. In addition to the existing unpaired spectrum (or TDD) or paired spectrum (or FDD) frame structure types, another frame structure type (e.g., frame structure type 2) may be introduced to define the above SBFD. The above frame structure type 2 may be defined to be supported in the specific frequency or frequency band, or the base station may indicate to the terminal whether SBFD is supported as system information. The SBFD terminal may receive the system information including the SBFD support status and determine whether SBFD is supported in the specific cell (or frequency, frequency band).

[0269] Second method. Whether SBFD is additionally supported in a specific frequency or frequency band of an existing unpaired spectrum (or TDD) can be indicated to the terminal without defining a new frame structure type. In the second method, whether SBFD is additionally supported in a specific frequency or frequency band of an existing unpaired spectrum can be defined, or the base station can indicate to the terminal whether SBFD is supported through system information. The SBFD terminal can receive system information including whether SBFD is supported and determine whether SBFD is supported in the specific cell (or frequency, frequency band).

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

[0271] In the present disclosure, the SBFD terminal can obtain cell synchronization by receiving a synchronization signal block during the initial cell access for connecting to a cell (or base station). The process for obtaining cell synchronization may be the same for the SBFD terminal and the existing TDD terminal. Thereafter, the SBFD terminal can determine whether the cell supports SBFD through a MIB acquisition process, a SIB acquisition process, or a random access process.

[0272] The system information for transmitting information on whether the above SBFD is supported may be system information transmitted separately from the system information for terminals supporting other versions of the standard within the cell (e.g., existing TDD terminals). The SBFD terminal may determine whether SBFD is supported by obtaining all or part of the system information for the existing TDD terminal and the separately transmitted system information. If the SBFD terminal obtains only the system information for the existing TDD terminal or obtains system information on non-support of SBFD, the cell (or base station) may determine that it supports only TDD.

[0273] If the information on whether the above SBFD is supported is included in the system information for a terminal that supports a different version of the standard (e.g., an existing TDD terminal), the information on whether the above SBFD is supported may be inserted at the very end so as not to affect the acquisition of system information by the existing TDD terminal. If the SBFD terminal does not obtain the information on whether the above SBFD is supported inserted at the very end, or obtains information that SBFD is not supported, the SBFD terminal can determine that the cell (or base station) only supports TDD.

[0274] Alternatively, if the information on whether the SBFD is supported is included in the system information for a terminal supporting a different version of the standard (e.g., an existing TDD terminal), the information on whether the SBFD is supported may be transmitted through a separate PDSCH so as not to affect the acquisition of system information by the existing TDD terminal. That is, a terminal that does not support SBFD can receive the first SIB (or SIB1) including the existing TDD-related system information from the first PDSCH. An SBFD-supporting terminal can receive the first SIB (or SIB) including the existing TDD-related system information from the first PDSCH, and can receive the second SIB including the SBFD-related system information from the second PDSCH. Here, the first PDSCH and the second PDSCH can be scheduled as the first PDCCH and the second PDCCH, and the CRC (cyclic redundancy code) of the first PDCCH and the second PDCCH can be scrambled with the same RNTI (e.g., SI-RNTI). The search space for monitoring the second PDCCH can be obtained from the system information of the first PDSCH, and if it is not obtained (i.e., the system information of the first PDSCH does not include information about the search space), the terminal can receive the second PDCCH in the same search space as the search space of the first PDCCH.

[0275] As described above, when the SBFD terminal determines that the cell (or base station) supports only TDD, the SBFD terminal can perform random access procedures and transmit and receive data / control signals in the same manner as a conventional TDD terminal.

[0276] The base station may configure separate random access resources for each of an existing TDD terminal or an SBFD terminal (e.g., an SBFD terminal supporting duplex communication and an SBFD terminal supporting half-duplex communication), and transmit configuration information (control information or configuration information indicating time-frequency resources that can be used for PRACH) for the random access resources to the SBFD terminal through system information. The system information for transmitting information for the random access resources may be separately transmitted system information that is distinct from system information for terminals supporting different versions of standards within a cell (e.g., an existing TDD terminal).

[0277] The base station may configure random access resources for TDD terminals and additionally configure separate random access resources for SBFD terminals. Here, SBFD terminals may use the random access resources for TDD terminals, or SBFD terminals may not use the random access resources for TDD terminals. In the latter case, SBFD terminals can only always use the separate random access resources for SBFD terminals.

[0278] The SBFD terminal can be instructed by the base station whether or not it can use random access resources for TDD terminals. This can be indicated by being included in the SIB. That is, separate random access resources for SBFD terminals can be configured in the SIB, and along with the configuration, the availability of random access resources for TDD terminals can be indicated. This can be indicated by 1 bit. If the 1 bit is '0' (or FALSE), the SBFD terminal cannot use random access resources for TDD terminals. If the 1 bit is '1' (or TRUE), the SBFD terminal can use random access resources for TDD terminals.

[0279] The base station can determine the type of terminal attempting to access the cell based on the random access resources used by the terminal. For example, an SBFD terminal can transmit a PRACH through a separate random access resource for SBFD terminals, and the base station can determine that the SBFD terminal is attempting to access the cell when receiving the PRACH. For example, a TDD terminal can transmit a PRACH through a random access resource for TDD terminals, and the base station can determine that the TDD terminal is attempting to access the cell when receiving the PRACH. Note that if an SBFD terminal is allowed to transmit a PRACH through a random access resource for a TDD terminal, the base station may be ambiguous as to whether the type of the terminal that transmitted the PRACH is a TDD terminal or an SBFD terminal. In this case, the base station can always assume that the type of the terminal is a TDD terminal.

[0280] When the base station determines that the terminal is an SBFD terminal, the base station may schedule messages 2 (Msg2), 3 (Msg3), 4 (Msg4), etc. to the terminal based on the uplink subband configuration. That is, when the base station schedules reception of Msg2 and Msg4 to the terminal, the base station may schedule Msg2 and Msg4 not to be received in the uplink subband (when the terminal receives a PDSCH including Msg2 and Msg4, the PDSCH is received in a frequency resource excluding the uplink subband). When the base station schedules Msg3 PUSCH to the terminal, the base station may schedule Msg3 PUSCH to be transmitted within the uplink subband.

[0281] If the base station determines that the terminal is a TDD terminal, the base station cannot use the uplink subband configuration when scheduling Msg2, Msg3, and Msg4 to the terminal. That is, even if the uplink subband is configured in the downlink symbol or the flexible symbol, the base station can assume that the terminal cannot obtain the uplink subband configuration information. When the base station schedules Msg3 PUSCH to the terminal, the Msg3 PUSCH can be scheduled in the flexible symbol or the uplink symbol. In other words, the Msg3 PUSCH cannot be scheduled in the uplink subband.

[0282] Alternatively, the base station may not set up separate random access resources for SBFD terminals, but may set up common random access resources for all terminals within the cell. In this case, configuration information for the random access resources may be transmitted to all terminals within the cell through system information, and the SBFD terminal that has received the system information may perform random access on the random access resources. Thereafter, the SBFD terminal may complete the random access process and proceed to an RRC connection mode for transmitting and receiving data with the cell. After the RRC connection mode, the SBFD terminal may receive a higher layer signal or a physical signal from the base station that can determine that some frequency resources of the downlink time resources are set uplink resources, and may perform an SBFD operation, for example, transmit an uplink signal on the uplink resources.

[0283] When the SBFD terminal determines that the cell supports SBFD, the terminal may transmit capability information including at least one or more of whether the terminal supports SBFD, whether full-duplex communication or half-duplex communication is supported, and the number of transmit or receive antennas provided (or supported) to the base station, thereby informing the base station that the terminal attempting to connect is an SBFD terminal. Alternatively, when half-duplex communication support is a mandatory implementation for the SBFD terminal, whether or not the half-duplex communication is supported may be omitted from the capability information. The SBFD terminal may report the capability information to the base station through a random access procedure, may report to the base station after completing the random access procedure, or may report to the base station after proceeding to an RRC connection mode for transmitting and receiving data with the cell.

[0284] The above SBFD terminal may support half-duplex communication, which performs only uplink transmission or downlink reception at a time, like a conventional TDD terminal, or may support full-duplex communication, which performs both uplink transmission and downlink reception at a time. Accordingly, whether the above half-duplex communication or full-duplex communication is supported can be reported to the base station by the SBFD terminal through a capability report, and after the report, the base station can configure the SBFD terminal to transmit and receive using half-duplex communication or full-duplex communication. When the SBFD terminal reports the capability for the above half-duplex communication to the base station, since a duplexer generally does not exist, a switching gap may be required to change the RF between transmission and reception when operating in FDD or TDD.

[0285] Typically, a terminal can establish a wireless link with a network through a random access procedure based on synchronization with the network and system information acquired during the cell search process. Random access can be either contention-based or contention-free. Contention-based random access can be used when a terminal performs cell selection and reselection during the initial cell access phase, for example, when moving from the RRC_IDLE state to the RRC_CONNECTED state. Contention-free random access can be used to reestablish uplink synchronization when downlink data arrives, in the case of a handover, or in the case of position measurement.

[0286] FIG. 11 illustrates a random access procedure in a wireless communication system according to an embodiment of the present disclosure.

[0287] Referring to FIG. 11, a contention-based random access procedure is illustrated as an example. In addition, although not illustrated in FIG. 11, the base station may transmit a synchronization signal block as described in the above-described embodiments. At this time, the base station may periodically transmit the synchronization signal block using beam sweeping. For example, the base station may transmit a synchronization signal block including a PSS / SSS (synchronization signal) and a PBCH (broadcast channel) signal using up to 64 different beams for 5 ms, and multiple synchronization signal blocks may be transmitted using different beams. The terminal may detect (select) a synchronization signal block having an optimal beam direction (e.g., a beam direction having the strongest received signal strength or greater than a predetermined threshold) and transmit a preamble using a PRACH (physical random access channel) resource associated with the detected synchronization signal block. For example, as a first step (1101) of a random access procedure, a terminal may transmit a random access preamble (or message 1) to a base station. The base station, which receives the random access preamble, may measure a transmission delay value between the terminal and the base station and synchronize uplink. Specifically, the terminal may transmit a random access preamble randomly selected from a random access preamble set given in advance by system information. In addition, the initial transmission power of the random access preamble may be determined according to the path loss between the terminal and the base station measured by the terminal. In addition, the terminal may determine a transmission beam direction (or transmission beam or beam) of the random access preamble based on a synchronization signal block received from the base station, and transmit the random access preamble by applying the determined transmission beam direction.

[0288] In the second step (1102), the base station can transmit a response (random access response, RAR, or message 2 (Msg2)) to the terminal for the detected random access attempt. The base station can transmit an uplink transmission timing control command to the terminal based on a transmission delay value measured from the random access preamble received in the first step (1101). In addition, the base station can transmit an uplink resource and power control command to be used by the terminal as scheduling information. The scheduling information can include control information for the uplink transmission beam of the terminal. The RAR is transmitted through the PDSCH and can include at least one of the following information:

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

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

[0291] - uplink scheduling grant, or

[0292] - Timing advance value.

[0293] If the terminal does not receive RAR, which is scheduling information for message 3 (Msg3), from the base station for a predetermined period of time in the second step (1102), the first step (1101) can be performed again. If the first step is performed again, the terminal increases the transmission power of the random access preamble by a predetermined step and transmits it (this is called power ramping), thereby increasing the probability of the base station receiving the random access preamble.

[0294] In the third step (1103), the terminal may transmit uplink information (scheduled transmission, or message 3) including its terminal identifier (which may be referred to as UE contention resolution identity) (or a valid terminal identifier (C-RNTI) if the terminal already has a valid terminal identifier within the cell before initiating the random access procedure) to the base station through an uplink data channel (physical uplink shared channel, PUSCH) using the uplink resources allocated in the second step (1102). The PUSCH may be referred to as message 3 PUSCH (Msg3 PUSCH). The transmission timing of the uplink data channel for transmitting 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 for transmitting message 3 may be determined in consideration of the power control command received from the base station in the second step (1102) and the power ramping value of the random access preamble. There is. The uplink data channel for transmitting the above message 3 may be the first uplink data signal transmitted by the terminal to the base station after the terminal transmits the random access preamble.

[0295] In the fourth step (1104), if the base station determines that the terminal has performed random access without collision with other terminals, it can transmit a message (contention resolution message (CR message), or message 4)) including the identifier of the terminal that transmitted uplink data in the third step (1103) to the terminal. In this regard, if multiple terminals receive the same TC-RNTI in the second step (1102), each of the multiple terminals that received the same TC-RNTI can include its own terminal identifier (UE contention resolution identity) in message 3 in the third step (1103) and transmit it to the base station, and the base station can transmit message 4 (CR message) including the terminal identifier of one of the identifiers of the multiple terminals to resolve contention. When the terminal receives message 4 (CR message) including its terminal identifier from the base station in step 4 (1104) (or transmits message 3 including terminal identifier (C-RNTI) in step 3 (1103) and receives terminal-specific control information including CRC based on the terminal identifier (C-RNTI) through PDCCH in step 4 (1104), the terminal can determine that random access is successful. Accordingly, among multiple terminals that have received the same TC-RNTI from the base station, a terminal that confirms that its terminal identifier is included in message 4 (CR message) can confirm that the contention is successful. In addition, the terminal can transmit HARQ-ACK / NACK indicating whether message 4 was successfully received to the base station through the uplink control channel (PUCCH).

[0296] If the data transmitted by the terminal in step 3 (1103) collides with data from another terminal, causing the base station to fail to receive a data signal from the terminal, the base station may not transmit any more data to the terminal. Accordingly, if the terminal fails to receive data transmitted from the base station in step 4 (1104) for a certain period of time, the random access procedure may be determined to have failed, and the procedure may be restarted from step 1 (1101).

[0297] As described above, in the first step (1101) of the random access process, the terminal can transmit a random access preamble on the PRACH. Each cell has 64 available preamble sequences, and four long preamble formats and nine short preamble formats can be used depending on the transmission type. The terminal generates 64 preamble sequences using the root sequence index and cyclic shift value signaled as system information, and can randomly select one sequence to use as a preamble.

[0298] The base station can inform the terminal of the configuration information for random access resources, for example, the control information (or configuration information) indicating the time-frequency resources that can be used for PRACH, using at least one of SIB, higher layer signaling (RRC (Radio Resource Control) information), or DCI (Downlink Control Information). The frequency resource for PRACH transmission can indicate the start RB point of transmission to the terminal, and the number of RBs used can be determined according to the preamble format transmitted through PRACH and the applied subcarrier spacing. The time resource for PRACH transmission can inform the subframe index and start symbol including the preset PRACH configuration period, PRACH transmission time (PRACH occasion, which can be used interchangeably with transmission time), and the number of PRACH transmission time points in the slot, etc., through the PRACH configuration index (0 to 255), as shown in Table 16 below. The terminal can determine the validity of the PRACH transmission times indicated by the PRACH configuration index, and determine only the valid PRACH transmission times as PRACH transmission times at which the random access preamble can be transmitted. Through the PRACH configuration index, the random access configuration information included in the SIB, and the index of the SSB selected by the terminal, the terminal can check the time and frequency resources for transmitting the random access preamble, and transmit the selected sequence as a preamble to the base station.

[0299]

[0300] Meanwhile, according to an embodiment of the present disclosure, a method of determining the validity of a PRACH transmission time point through a PRACH configuration index and SBFD settings for an SBFD terminal to perform PRACH transmission, and performing PRACH transmission through the PRACH transmission time point determined to be valid, and a procedure of the SBFD terminal is required when the valid PRACH transmission time point and downlink reception overlap.

[0301] Accordingly, the method by which the SBFD terminal determines the validity of the PRACH transmission time and the operation of the SBFD terminal when the valid PRACH transmission time and downlink reception are set or scheduled to occur simultaneously will be described using FIGS. 12 and 13.

[0302] FIG. 12 is a diagram illustrating an example of SBFD operation in a TDD band of a wireless communication system according to an embodiment of the present disclosure.

[0303] In Fig. 12 (a), a case where TDD is operated in a specific frequency band is illustrated. In a cell where TDD is operated, a base station can transmit and receive signals including data / control information in downlink slots (or symbols), uplink slots (or symbols) (1201), and flexible slots (or symbols) based on settings for TDD UL-DL resource configuration information indicating downlink slot (or symbol) resources and uplink slot (or symbol) resources of an existing TDD terminal or an SBFD terminal.

[0304] In Fig. 12, it can be assumed that the DDDSU slot format is set according to the TDD UL-DL resource configuration information. Here, 'D' is a slot composed entirely of downlink symbols, 'U' is a slot composed entirely of uplink symbols, and 'S' is a slot that is not 'D' or 'U', that is, a slot that includes a downlink symbol or an uplink symbol or a flexible symbol. Here, for convenience, it can be assumed that S is composed of 12 downlink symbols and 2 flexible symbols. In addition, the DDDSU slot format can be repeated according to the TDD UL-DL resource configuration information. That is, the repetition period of the TDD configuration is assumed to be 5 slots (5 ms for 15 kHz SCS, 2.5 ms for 30 kHz SCS, etc.).

[0305] Next, in (b) to (d) of FIG. 12, a case is shown where SBFD is operated together with TDD in a specific frequency band.

[0306] Referring to (b) of FIG. 12, the terminal may set a portion of the frequency band of the cell as a frequency band (1210) capable of uplink transmission. This band may be referred to as an uplink subband (UL subband). And the uplink subband (UL subband) may be applied to all symbols of all slots. The terminal may transmit an uplink channel or signal scheduled in the uplink slot (or symbol) (1211) and all symbols (1212) within the subband (UL subband). However, the terminal may not transmit an uplink channel or signal in a band other than the subband (UL subband) in the downlink slot (or symbol) and the flexible slot (or symbol).

[0307] Referring to (c) of FIG. 12, the terminal may set a portion of the frequency band of the cell as a frequency band (1220) capable of uplink transmission, and may set a time region in which the frequency band is activated. Here, this frequency band may be called an uplink subband (UL subband). In (c) of FIG. 12, the uplink subband (UL subband) is deactivated in the first slot, and the uplink subband (UL subband) may be activated in the remaining slots. Accordingly, the terminal may transmit an uplink channel or signal in the uplink slot (or symbol) (1221) and the uplink subband (UL subband) (1222) of the remaining slots. Therefore, although the uplink subband (UL subband) is activated in units of slots here, whether it is activated or not may be set in units of symbols.

[0308] Referring to (d) of FIG. 12, a terminal may be configured with time-frequency resources capable of uplink transmission. The terminal may configure one or more time-frequency resources as time-frequency resources capable of uplink transmission. For example, some frequency bands (1232) of the first and second slots may be configured as time-frequency resources capable of uplink transmission. In addition, some frequency bands (1233) of the third slot and some frequency bands (1234) of the fourth slot may be configured as time-frequency resources capable of uplink transmission. The terminal may transmit an uplink channel or signal in an uplink slot (or symbol) (1231), some frequency bands (1232) of the first and second slots, some frequency bands (1233) of the third slot, and some frequency bands (1234) of the fourth slot.

[0309] In the following description, the time-frequency resources that enable uplink transmission in downlink symbols or flexible symbols may be referred to as SBFD resources / UL subbands.

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

[0311] Meanwhile, the base station can transmit PRACH settings to the terminal as system information, and RACH opportunities (Occasions) can be set based on the PRACH settings. The terminal can determine all or some of the RACH opportunities as valid. According to one method of the present disclosure, the terminal can determine valid RACH opportunities as follows.

[0312] The first valid RACH opportunities can be determined based on the first PRACH configuration (PRACH configuration for TDD terminal).

[0313] In an FDD cell, all first RACH opportunities according to the configured first PRACH configuration can be defined as valid.

[0314] In a TDD cell, only the second RACH opportunity that satisfies the following conditions among the configured second PRACH settings can be considered valid.

[0315] - If the terminal does not receive TDD DL / UL configuration information from the system information, the RACH opportunity in the PRACH slot does not precede the SS / PBCH, and N from the last received symbol of the SS / PBCH. gap If it starts after the symbol, the above RACH opportunity can be judged to be valid.

[0316] - When the terminal receives TDD DL / UL configuration information from the system information, the RACH opportunity in the UL symbol or the RACH opportunity in the PRACH slot does not precede the SS / PBCH, and the N from the last received symbol of the SS / PBCH gap A RACH opportunity can be considered valid if it starts after the symbol and after the last DL symbol.

[0317] The above method is an example, and first valid RACH opportunities may be determined in other ways.

[0318] Referring to (a) of FIG. 13, it is assumed that the terminal has received DDDSU with TDD DL / UL configuration information, and the first RACH opportunity is configured for each slot according to the first PRACH configuration. The terminal can determine that the first PRACH configuration overlapping with the UL symbol is the first valid RACH opportunity. At this time, the 5th slot (the last slot of the TDD period configured with DDDSU) is an uplink slot, and the first RACH opportunity (1301) may be valid. However, the first RACH opportunities of the 1st, 2nd, 3rd, and 4th slots (the first four slots of the TDD period configured with DDDSU) (1302) may not be valid because they do not start after the last downlink symbol. Accordingly, the terminal can determine that the first RACH opportunities of four uplink slots (the 5th, 10th, 15th, and 20th) within 20 slots are valid, and determine that the first RACH opportunities of the remaining 16 slots are invalid.

[0319] When an SBFD terminal is configured with time-frequency resources for uplink transmission, SBFD uplink resources, second valid RACH opportunities can be determined based on the second PRACH configuration (PRACH configuration for an SBFD terminal). The terminal can determine the validity of the second RACH opportunity as follows.

[0320] - If the terminal does not receive TDD DL / UL configuration information from the system information, the second RACH opportunity in the PRACH slot does not precede the SS / PBCH, and N from the last received symbol of the SS / PBCH. gap If it starts after the symbol, the second RACH opportunity can be considered valid.

[0321] - When the terminal receives TDD DL / UL configuration information from the system information, the RACH opportunity in the 2nd RACH opportunity or PRACH slot within the UL symbol does not precede the SS / PBCH, and from the last received symbol of the SS / PBCH, N gap It can be determined to be valid if it starts after the symbol and the second RACH opportunity is located within the SBFD uplink resource.

[0322] That is, compared to the first valid RACH opportunities, when TDD DL / UL configuration information is received from the system information, the RACH opportunities included in the SBFD uplink resource region within the DL symbol can become the second valid RACH opportunities. Therefore, the terminal can obtain more RACH opportunities through the above method.

[0323] Depending on the location of the SS / PBCH, the second RACH opportunity may not be valid. Furthermore, if the second RACH opportunity is set on a SBFD uplink resource (a resource capable of uplink transmission), the second RACH opportunity may be limited in the resource.

[0324] In one method of the present disclosure, when an SBFD terminal is configured with time-frequency resources for uplink transmission, SBFD uplink resources, the terminal can determine the validity of a second RACH opportunity as follows.

[0325] - If the terminal does not receive TDD DL / UL configuration information from the system information, the second RACH opportunity in the PRACH slot does not precede the SS / PBCH, and N from the last received symbol of the SS / PBCH. gap If it starts after the symbol, the second RACH opportunity can be judged to be valid.

[0326] - When the terminal receives TDD DL / UL configuration information from the system information, it can determine that the second RACH opportunity within the UL symbol or the RACH opportunity is valid if it is located within the SBFD resource.

[0327] The above method is an example, and second valid RACH opportunities may be determined in other ways.

[0328] Referring to (b) to (d) of FIG. 13, the terminal can determine whether the second RACH opportunity is valid based on TDD UL-DL resource configuration information and SBFD uplink resource information.

[0329] Referring to (b) of FIG. 13, the terminal may be configured with an uplink subband (UL subband) (1310), and the resource of the uplink subband of the downlink symbol may be determined as an SBFD uplink resource. Since the SBFD uplink resource of the preceding 4 slots of the TDD cycle includes a second RACH opportunity (1311), the terminal may determine that the second RACH opportunity is valid.

[0330] For reference, in (b) of Fig. 13, when an uplink subband (UL subband) (1310) is set, uplink transmission is possible in all symbols using the resources of the uplink subband (UL subband). Therefore, the above methods can be briefly described as follows.

[0331] In one method of the present disclosure, when an SBFD terminal is configured with time-frequency resources for uplink transmission, SBFD resources, the terminal can determine the validity of a second RACH opportunity as follows.

[0332] - If the frequency band of the RACH opportunity set according to the PRACH configuration is included in the uplink subband (UL subband), the second RACH opportunity in the PRACH slot does not precede the SS / PBCH, but is N from the last received symbol of the SS / PBCH. gapIf it starts after the symbol, the second RACH opportunity may be judged to be valid.

[0333] In one method of the present disclosure, when an SBFD terminal is configured with time-frequency resources for uplink transmission, SBFD resources, the terminal can determine the validity of a RACH opportunity as follows.

[0334] - If the frequency band of the second RACH opportunity set according to the PRACH setting is included in the uplink subband (UL subband), all RACH opportunities may be valid.

[0335] The above method is an example, and second valid RACH opportunities may be determined in other ways.

[0336] Referring to (c) of FIG. 13, the terminal may be configured with an uplink subband (UL subband) (1320) and a time domain in which the uplink subband is activated, and the resource of the uplink subband of the downlink symbol of the activated time domain may be determined as an SBFD uplink resource. Since the 2nd RACH opportunity (1321) is included in the SBFD uplink resource of the 2nd, 3rd, and 4th slots of the TDD period, the terminal may determine that the 2nd RACH opportunity (1321) is valid. For reference, the 2nd RACH opportunity (1322) of the 1st slot of the TDD period may be determined to be invalid since it is not included in the SBFD uplink resource.

[0337] Referring to (d) of FIG. 13, the terminal can be configured with a time-frequency domain of SBFD uplink resources, and can determine that the second RACH opportunity overlapping with the SBFD uplink resources is valid. That is, the second RACH opportunities (1332) of the first and second slots of the TDD cycle are included in the SBFD uplink resources and thus can be considered valid. However, the second RACH opportunities (1331) of the third and fourth slots may not be valid because they are not included in the SBFD uplink resources.

[0338] Although not specifically mentioned in (b) to (d) of FIG. 13, the second RACH opportunity overlapping with the UL symbol may always be valid. However, the UE may be configured with SBFD downlink resources capable of DL transmission within the UL symbol. In this case, if the SBFD downlink resources overlap with the second RACH opportunity, the RACH opportunity may be invalid. Alternatively, even if the SBFD downlink resources overlap with the RACH opportunity, the second RACH opportunity may be valid. That is, the SBFD downlink resources configured in the uplink symbol may be ignored when determining a valid second RACH opportunity.

[0339] The above methods can be used when a single PRACH configuration is configured for a TDD terminal (a terminal other than an SFBD terminal) and an SBFD terminal. That is, based on a single PRACH resource configuration, a TDD terminal can determine a first valid RACH opportunity according to the method of a TDD cell ((a) of FIG. 13), and an SFBD terminal can determine a second valid RACH opportunity according to the first or second method ((b) to (d) of FIG. 13).

[0340] [Reference RB indexing for Msg3 PUSCH transmission on SBFD UL subband]

[0341] The terminal can receive scheduling information for Msg3 PUSCH from the base station. The Msg3 PUSCH scheduling information can be included in the RAR UL grant.

[0342] A RAR UL grant may contain the following information:

[0343] - Frequency hopping flag - 1 bit,

[0344] - PUSCH frequency resource allocation - 14 bits,

[0345] - PUSCH time resource allocation - 4 bits,

[0346] - MCS (modulation and coding scheme) - 4 bits,

[0347] - TP command for PUSCH (TPC command for PUSCH) - 3 bits, and / or

[0348] - CSI (channel state information) request (CSI request) - 1 bit.

[0349] The terminal can obtain time-domain scheduling information (scheduled slots and symbols within the slot) of the Msg3 PUSCH through the PUSCH time resource allocation field. The PUSCH time resource allocation field can indicate one of 16 rows of a predefined 4-bit table. The table can include a slot offset, a starting symbol index within the slot, the number of consecutive symbols, and a PUSCH mapping type.

[0350] The terminal can obtain frequency domain scheduling information (the index of the starting RB and the number of consecutive RBs) of Msg 3 PUSCH through the PUSCH frequency resource allocation field. More specifically, the frequency domain scheduling information can be obtained as shown in Table 17.

[0351] The terminal can determine a reference UL BWP. The reference UL BWP may be a BWP used when interpreting the PUSCH frequency resource allocation field. The reference UL BWP may be determined based on the initial UL BWP configuration and the active UL BWP configuration as follows: - If the initial UL BWP and the active UL BWP have the same subcarrier spacing and the same cyclic prefix (CP) length, and the active UL BWP includes all RBs of the initial UL BWP, or the active UL BWP is the initial UL BWP, the initial UL BWP can be used as the reference UL BWP. - If the above conditions are not satisfied, RB numbering starts from the start RB of the active UL BWP, and the maximum number of RBs of the reference UL BWP can be the same as the number of RBs of the initial UL BWP. That is, the reference UL BWP can include RB 0, RB 1, ..., RB N-1 of the active UL BWP. Here, N is the number of RBs included in the initial UL BWP.

[0352] FIG. 14 is a diagram illustrating a reference UL BWP according to an embodiment of the present disclosure. Referring to FIG. 14 and Table 17, a method for determining a reference UL BWP is described. For convenience, it is assumed that the subcarrier spacing and CP length of the initial UL BWP and the active UL BWP are the same.

[0353] Referring to (a) of Fig. 14, the initial UL BWP may include N RBs, and the active UL BWP may include M RBs (N and M are natural numbers). All N RBs included in the initial UL BWP may be included in the active UL BWP. In this case, the terminal may assume that the reference UL BWP is identical to the initial UL BWP. That is, the reference UL BWP may include N RBs included in the initial UL BWP.

[0354] Referring to (b) of FIG. 14, the initial UL BWP may include N RBs, and the active UL BWP may include M RBs. Some of the N RBs included in the initial UL BWP may not be included in the active UL BWP (i.e., the initial UL BWP and the active UL BWP may partially overlap). In this case, the M RBs of the active UL BWP may be indexed in ascending order from 0, such as RB 0, RB 1, ..., RB M-1, based on the RB at the lowest position in the frequency axis, and the UE may assume that the reference UL BWP is identical to RB 0, RB 1, ..., RB N-1 of the active UL BWP. That is, the reference UL BWP may include the N lowest RBs in the frequency axis among the M RBs included in the active UL BWP.

[0355] The PUSCH frequency resource allocation field may indicate scheduled RBs among the N RBs of the reference UL BWP. The PUSCH frequency resource allocation may include 14 bits. The UE may interpret the PUSCH frequency resource allocation field as follows.

[0356] - If N (the number of RBs included in the initial UL BWP) is less than or equal to 180, the terminal can interpret the frequency domain information in which the PUSCH is scheduled using only ceil(log2(N*(N+1) / 2)) LSBs (least significant bits) out of 14 bits.

[0357] - Otherwise (if N (the number of RBs included in the initial UL BWP) is greater than 180), the terminal may add ceil(log2(N*(N+1) / 2))-14 bits with 0 value to the 14 bits, where N UL,hop After the bit, ceil(log2(N*(N+1) / 2))-14 MSBs with a value of 0 can be added to the frequency domain resource assignment field. The terminal can interpret ceil(log2(N*(N+1) / 2)) bits as frequency domain information in which the PUSCH is scheduled. If the Frequency hopping flag of the RAR UL grant is '0', N UL,hop = 0 bits, and if the Frequency hopping flag of the RAR UL grant is '1', then N UL,hop can be determined according to Table 18.

[0358]

[0359] FIG. 15 illustrates a case where an SBFD resource or UL subband is not included in a reference UL BWP according to an embodiment of the present disclosure.

[0360] Referring to FIG. 15, the initial UL BWP set for the terminal may include N RBs, and the active UL BWP may include M RBs. Some of the N RBs included in the initial UL BWP may not be included in the active UL BWP (i.e., the initial UL BWP and the active UL BWP may partially overlap). In this case, the M RBs of the active UL BWP may be indexed in ascending order from 0, such as RB 0, RB 1, ..., RB M-1, based on the RB at the lowest position in the frequency axis, and the terminal may assume that the reference UL BWP is identical to RB 0, RB 1, ..., RB N-1 of the active UL BWP. That is, the reference UL BWP may include the N lowest RBs in the frequency axis among the M RBs included in the active UL BWP.

[0361] An SBFD terminal can be configured with SBFD resources or an UL subband. The symbol configured with the SBFD resource or UL subband may be a downlink symbol. The terminal can transmit an uplink channel or signal on the SBFD resource or UL subband. The uplink channel may include Msg3 PUSCH.

[0362] An SBFD terminal can select one of the first valid RACH opportunity or the second valid RACH opportunity and transmit a PRACH preamble to the base station. When the base station receives a PRACH preamble belonging to the first valid RACH opportunity, the base station can regard the terminal connected to the cell as a TDD terminal (a terminal that does not support SBFD operation). When the base station receives a PRACH preamble belonging to the second valid RACH opportunity, the base station can regard the terminal connected to the cell as an SBFD terminal. If the base station determines that the terminal is an SBFD terminal, the base station can schedule Msg3 PUSCH through an UL subband. When the terminal transmits a PRACH preamble belonging to the second valid RACH opportunity, the Msg3 PUSCH scheduled by the terminal can be transmitted on the UL subband. Unless otherwise specified in this disclosure, the SBFD resource or UL subband may only include RBs included in the initial UL subband among the SBFD resources or UL subbands configured by the base station. That is, depending on the configuration of the base station, RBs included in the SBFD resource or UL subband that are not included in the initial UL subband may be excluded.

[0363] However, the reference UL BWP determined by the terminal may not include SBFD resources or UL subbands. Therefore, even though the SBFD resources or UL subbands are included in the active UL BWP, the terminal cannot schedule Msg3 PUSCH with the SBFD resources or UL subbands. Methods 1-1 to 1-3 of the present disclosure provide methods for resolving this issue. At least one of Methods 1-1 to 1-3 of the present disclosure may be performed in combination with at least one of Methods 2-1 to 2-2 described below.

[0364] Method 1-1

[0365] When Msg3 PUSCH is scheduled in an SBFD symbol, the UE may select the lowest RB of the SBFD resource or UL subband as the start RB of the Reference UL BWP. The UE may select N RBs as the length of the Reference UL BWP (i.e., the number of RBs included in the Reference UL BWP). More specifically, the lowest RB index of the SBFD resource or UL subband may be P (where P is an integer). The index may be an index of a common resource block (CRB) or an index of an active UL BWP (where the lowest RB index of the active UL BWP is 0 and is in ascending order in the frequency axis). In addition, the SBFD resource or UL subband may be said to include K RBs (where K is a natural number). The SBFD resource or UL subband may include RB P, RB P+1, RB P+2, ..., RB P+K-1. The reference UL BWP may include RB P, RB P+1, RB P+2, ..., RB P+N-1, where N is the number of RBs included in the initial UL BWP. The UE can interpret the scheduling information of Msg 3 PUSCH based on the N RBs.

[0366] The terminal can interpret the PUSCH frequency resource allocation field as follows.

[0367] - If N (the number of RBs included in the initial UL BWP) is less than or equal to 180, the terminal can interpret the frequency domain information in which the PUSCH is scheduled using only ceil(log2(N *(N+1) / 2)) LSBs (least significant bits) out of 14 bits.

[0368] - Otherwise (if N (the number of RBs included in the initial UL BWP) is greater than 180), the terminal can add ceil(log2(N*(N+1) / 2))-14 bits with a value of 0 to the 14 bits, where N is 14 bits. UL,hop After the bit, ceil(log2(N*(N+1) / 2))-14 MSBs with a value of 0 can be added to the frequency domain resource assignment field. The terminal can interpret ceil(log2(N*(N+1) / 2)) bits as frequency domain information in which the PUSCH is scheduled. If the Frequency hopping flag of the RAR UL grant is '0', N UL,hop = 0 bits, and if the Frequency hopping flag of the RAR UL grant is '1', then N UL,hop can be determined according to Table 19 or Table 20.

[0369]

[0370]

[0371] Method 1-2

[0372] When Msg3 PUSCH is scheduled in an SBFD symbol, the UE may select the lowest RB of the SBFD resource or UL subband as the start RB of the Reference UL BWP. The UE may select the number of RBs included in the UL subband based on the length of the Reference UL BWP (i.e., the number of RBs included in the Reference UL BWP). More specifically, the lowest RB index of the SBFD resource or UL subband may be P. The index may be an index of a common resource block (CRB) or an index of an active UL BWP (the index of the lowest RB of the active UL BWP is 0 and is in ascending order in the frequency axis). In addition, the SBFD resource or UL subband may include K RBs. The SBFD resource or UL subband may include RB P, RB P+1, RB P+2, ..., RB P+K-1. The terminal may include RB P, RB P+1, RB P+2, ..., RB P+K-1 as reference UL BWP, where K is the number of RBs included in the UL subband. The terminal may interpret the scheduling information of Msg 3 PUSCH based on the K RBs.

[0373] The terminal can interpret the PUSCH frequency resource allocation as follows.

[0374] - If K (the number of RBs included in the UL subband) is less than or equal to 180, the terminal can interpret the frequency domain information in which the PUSCH is scheduled using only ceil(log2(K*(K+1) / 2)) LSBs (least significant bits) out of 14 bits.

[0375] - Otherwise (if K (the number of RBs included in the UL subband) is greater than 180), the terminal may add ceil(log2(K*(K+1) / 2))-14 bits with a value of 0 to the 14 bits, where N UL,hop After the bit, ceil(log2(K*(K+1) / 2))-14 MSBs with a value of 0 can be added to the frequency domain resource assignment field. The terminal can interpret ceil(log2(K*(K+1) / 2)) bits as frequency domain information in which the PUSCH is scheduled. If the Frequency hopping flag of the RAR UL grant is '0', N UL,hop = 0 bits, and if the Frequency hopping flag of the RAR UL grant is '1', then N UL,hop can be determined according to Table 19.

[0376] Method 1-3

[0377] When Msg3 PUSCH is scheduled in an SBFD symbol, the UE may select the highest RB of the SBFD resource or UL subband as the last RB of the Reference UL BWP. The UE may select the number of RBs (i.e., N) included in the initial UL BWP as the length of the Reference UL BWP (i.e., the number of RBs included in the Reference UL BWP). More specifically, the lowest RB index of the SBFD resource or UL subband may be P. The index may be an index of a CRB (common resource block) or an index of an active UL BWP (the index of the lowest RB of the active UL BWP is 0 and is in ascending order in the frequency axis). In addition, it may be said that the SBFD resource or UL subband includes K RBs. The SBFD resource or UL subband may include RB P, RB P+1, RB P+2, ..., RB P+K-1. The terminal may include RB P+KN, RB P+K-N+1, ..., RB P+K-2, RB P+K-1 as reference UL BWP. Here, K is the number of RBs included in the UL subband, and N is the number of RBs included in the initial UL BWP. The terminal may interpret the scheduling information of Msg 3 PUSCH based on the N RBs.

[0378] The PUSCH frequency resource allocation field can be interpreted with reference to the description of the above-described method 1-1. In the present disclosure, an SBFD symbol may be a symbol in which an SBFD resource or UL subband is set.

[0379] Alternatively, in the present disclosure, the SBFD symbols may be downlink symbols among the symbols for which SBFD resources or UL subbands are set.

[0380] [RB allocation determination for Msg3 PUSCH transmission on SBFD UL subband]

[0381] In one embodiment of the present disclosure, the terminal may use an initial UL BWP or a truncated active UL BWP as a reference UL BWP, and may move an RB allocation (starting RB index and length of RBs) determined based on the reference UL BWP into a UL subband. This may be applied when the Msg3 PUSCH is scheduled in an SBFD symbol. Here, using a truncated active UL BWP may mean using the number of RBs equal to the initial UL BWP from the starting RB of the active UL BWP.

[0382] For reference, this embodiment can be used only in the following situations.

[0383] - When the determined reference UL BWP does not include RBs of the UL subband. For example, when the determined reference UL BWP is N consecutive RBs from the starting RB of the active UL BWP (N = number of RBs included in the initial UL BWP).

[0384] For reference, this embodiment may assume that the reference UL BWP is determined according to Table 17. This means that the disclosed methods can be applied even if the reference UL BWP is determined in one way or another.

[0385] At least one of methods 2-1 to 2-2 of the present disclosure may be performed in combination with at least one of methods 1-1 to 1-3 described above.

[0386] Method 2-1

[0387] When the terminal determines RB allocation based on the initial UL BWP, the index of the starting RB and the number of consecutive RBs are S initial , L initial can be expressed as S initial = 0 RB may be the same RB as the lowest RB in terms of frequency of the initial UL BWP. The terminal may change / move the RB allocation to the UL subband based on the UL subband configuration.

[0388] More specifically, the index of the starting RB of the UL subband is S ULSB , and the number of RBs included in the UL subband is L ULSB can be expressed as . Here, S ULSB =0 RB may be the same RB as the lowest RB in terms of frequency of the initial UL BWP. The terminal uses Equations 2 to 5 to determine the index (S) of the starting RB among RB allocations within the UL subband. mod ) can be determined. Here, the index of the starting RB (S mod ) may be the RB that is the same as the lowest RB in frequency of the initial UL BWP.

[0389] [Equation 2]

[0390] S mod = (S initial mod L ULSB )+S ULSB

[0391] [Equation 3]

[0392] S mod = ((S initial -S ULSB ) mod L ULSB )+S ULSB

[0393] [Equation 4]

[0394] S mod= ((S initial +offset) mod L ULSB )+S ULSB

[0395] [Equation 5]

[0396] S mod = ((S initial +offset) mod L ULSB )+S ULSB +offset2

[0397] In mathematical expression 4, offset can be a value set or instructed by the base station to the terminal. In mathematical expression 3, offset = -S in mathematical expression 4. ULSB In this case, mathematical expression 2 may be a case where offset = 0 in mathematical expression 4.

[0398] In the mathematical expression 5, offset2 can be a value set or instructed by the base station to the terminal. Here, offset2 can be a number greater than or equal to 0.

[0399] As an example, the modular operation in Equations 2 to 5 may be omitted. That is, Equations 2 and 3 may be expressed as Equations 6 and 7.

[0400] [Equation 6]

[0401] S mod = S initial +S ULSB

[0402] [Equation 7]

[0403] S mod = S initial

[0404] The terminal starts from the determined starting RB index L initial The consecutive RBs of the dog can be determined as scheduled RBs within the UL subband.

[0405] S decided by the terminal mod is S ULSB Must be greater than or equal to S mod +L initial Silver S ULSB +LULSB It must be less than or equal to . If this condition is not satisfied, the UE may ignore the RAR UL grant scheduling Msg3 PUSCH. In other words, the UE may not transmit Msg3 PUSCH.

[0406] For reference, Equations 2 to 7 use the RB numbering of the initial UL BWP. That is, S mod =0 RB may be equal to the lowest RB in the frequency axis in the initial UL BWP. In one method of the present disclosure, Equations 2 to 7 may also utilize the RB numbering of the UL subband. That is, S mod =0 RB can be equal to the lowest RB in the frequency axis in the UL subband. For example, referring to Equation 7, S mod =S initial It can be, S mod An RB with =0 can be equal to the lowest RB in the frequency axis in the UL subband.

[0407] Method 2-2

[0408] When the terminal determines RB allocation based on the truncated active UL BWP, the index of the starting RB and the number of consecutive RBs are S active , L active can be expressed as S active = 0 RB may be the same RB as the lowest RB in frequency of the active UL BWP. The terminal may change / move the RB allocation to the UL subband based on the UL subband configuration.

[0409] More specifically, the index of the starting RB of the UL subband is S ULSB , and the number of RBs included in the UL subband is L ULSB can be expressed as . Here, S ULSB=0 RB may be the same RB as the lowest RB in frequency of the active UL BWP. The terminal uses Equations 8 to 11 to determine the index (S) of the starting RB among RB allocations within the UL subband. mod ) can be determined. Here, the index of the starting RB (S mod ) may be the same RB as the lowest RB in frequency of the active UL BWP.

[0410] [Equation 8]

[0411] S mod = (S active mod L ULSB )+S ULSB

[0412] [Equation 9]

[0413] S mod = ((S active -S ULSB ) mod L ULSB )+S ULSB

[0414] [Equation 10]

[0415] S mod = ((S active +offset) mod L ULSB )+S ULSB

[0416] [Equation 11]

[0417] S mod = ((S active +offset) mod L ULSB )+S ULSB +offset2

[0418] In mathematical expression 10, the offset may be a value set or instructed by the base station to the terminal. In mathematical expression 9, offset = -S in mathematical expression 10. ULSB In this case, mathematical expression 8 may be a case where offset = 0 in mathematical expression 10.

[0419] In mathematical expression 11, offset2 may be a value set or instructed by the base station to the terminal. Here, offset2 may be a number greater than or equal to 0.

[0420] As an example, the modular operation in Equations 8 to 11 may be omitted. That is, Equations 8 and 9 may be expressed as Equations 12 and 13.

[0421] [Equation 12]

[0422] S mod = S active +S ULSB

[0423] [Equation 13]

[0424] S mod = S active

[0425] The terminal starts from the determined starting RB index L active The consecutive RBs of the dog can be determined as scheduled RBs within the UL subband.

[0426] S decided by the terminal mod is S ULSB Must be greater than or equal to S mod +L active Silver S ULSB +L ULSB It must be less than or equal to . If this condition is not satisfied, the UE may ignore the RAR UL grant scheduling Msg3 PUSCH. In other words, the UE may not transmit Msg3 PUSCH.

[0427] For reference, Equations 8 to 13 use the RB numbering of the truncated active UL BWP. That is, S mod =0 RB may be equal to the lowest RB in the frequency axis in the active UL BWP. In one method of the present disclosure, Equations 8 to 13 may also utilize the RB numbering of the UL subband. That is, S mod=0 RB can be equal to the lowest RB in the frequency axis in the UL subband. For example, referring to Equation 13, S mod = S active It can be, S mod An RB with =0 can be equal to the lowest RB in the frequency axis in the UL subband.

[0428] S in the preceding methods 2-1 and 2-2 initial and S active can be determined based on the PUSCH frequency resource allocation field of the RAR UL grant. If the Frequency hopping flag of the RAR UL grant is '0' (disable), the scheduled Msg3 PUSCH is allocated to one S initial or one S active can have. If the Frequency hopping flag of the RAR UL grant is '1' (enable), the scheduled Msg3 PUSCH has two S initial or two S active can have. Here the first S initial or S active is the index of the starting RB of the first frequency hop, and the second S initial or S active is the index of the starting RB of the second frequency hop. For convenience, the first S initial or S active S initial (1) or S active (1) and the second S initial or S active S initial (2) or S active (2) is represented as follows. And, the starting RB index of the first frequency hop in the UL subband is S mod(1) and the starting RB index of the second frequency hop in the UL subband is S mod (2) is expressed as

[0429] In one embodiment of the present disclosure, the above-described method 2-1 or method 2-2 can be applied separately to each frequency hop. That is, in method 2-1 or method 2-2, S mod (1) is S initial (1) or S active (1) can be determined based on, S mod (2) is S initial (2) or S active (2) can be determined based on. Here, S initial (1) or S active (1) is the index of the starting RB determined based on the PUSCH frequency resource allocation field of the RAR UL grant, and S initial (2) or S active (2) may be the index of the starting RB determined as follows.

[0430] [Equation 14]

[0431] S initial (2) = ( S initial (1) + Offset ) mod N initial

[0432] [Equation 15]

[0433] S initial (2) = (S initial (1) + Offset ) mod N active

[0434] [Equation 16]

[0435] S active (2) = ( S active (1) + Offset ) mod N active

[0436] [Equation 17]

[0437] S active (2) = (Sactive (1) + Offset ) mod N initial

[0438] Here N initial is the number of RBs included in the initial UL BWP, and N active may be the number of RBs included in the active UL BWP. Here, the Offset may be determined as shown in Table 18.

[0439] FIG. 16 is a diagram illustrating an operation flow chart of a terminal according to an embodiment of the present disclosure.

[0440] The order of the operations in Fig. 16 may be changed, and some operations may be omitted.

[0441] Although not illustrated in FIG. 16, the random access procedure of a terminal may begin with transmitting a random access preamble. The terminal may receive a random access response (RAR) in response to the random access preamble. The RAR may include an UL grant that schedules PUSCH transmission. After the terminal receives the RAR UL grant, the procedure of FIG. 16 may be performed.

[0442] The UE can determine resources (e.g., frequency domain resource allocation and / or time domain resource allocation) for Msg3 PUSCH transmission based on the RAR UL grant. Specifically, referring to FIG. 16, in step 1600, the UE can determine the starting RB index and the number of consecutive RBs of the first hop of Msg3 PUSCH transmission based on the reference UL BWP through the PUSCH frequency resource allocation field of the RAR UL grant. For example, the reference UL BWP may be a truncated active UL BWP or an initial UL BWP. For example, the reference UL BWP may be determined according to Table 17.

[0443] For example, if Msg3 PUSCH transmission is scheduled within a SBFD symbol, i.e., scheduled within a UL frequency subband within a downlink symbol, RB numbering may start from the first RB of the UL frequency subband. In addition, the maximum number of RBs for frequency domain resource allocation of the Msg3 PUSCH transmission may be determined based on the number of RBs within the initial UL BWP. For example, the maximum number of RBs for frequency domain resource allocation of the Msg3 PUSCH transmission may be equal to the number of RBs within the initial UL BWP. For example, the starting RB index of the first hop of the Msg3 PUSCH transmission may be identified based on the RB numbering.

[0444] At step 1610, the UE can determine whether the Msg3 PUSCH is frequency hopping through the Frequency hopping flag field of the RAR UL grant. For example, if frequency hopping is applied to the Msg3 PUSCH transmission, the frequency offset for the second hop (second hop) of the frequency hopping can be determined based on the number of RBs in the UL frequency subband. For example, if frequency hopping is indicated for the Msg3 PUSCH transmission, the UE can determine the starting RB index of the second hop based on the reference UL BWP. For example, the UE can determine the starting RB index of the second hop using at least one of the methods in Equations 14 to 17.

[0445] At step 1620, the terminal can determine the starting RB index of the first hop within the UL subband based on the starting RB index of the first hop within the reference UL BWP. For example, the starting RB index of the first hop can be determined based on at least one of the methods in Equations 2 to 13.

[0446] At step 1630, the terminal may determine the starting RB index of the second hop within the UL subband based on the starting RB index of the second hop within the reference UL BWP. For example, the starting RB index of the second hop may be determined based on at least one of the methods in Equations 2 to 13.

[0447] In step 1640, the terminal can transmit the first hop based on the start RB index of the first hop determined in step 1620 in the UL subband, and can transmit the second hop based on the start RB index of the second hop determined in step 1630.

[0448] In one embodiment of the present disclosure, the above-described method 2-1 or method 2-2 may be applied only to the first frequency hop. That is, in method 2-1 or method 2-2, S mod (1) is S initial (1) or S active (1) can be determined based on. Here, S initial (1) or S active (1) is the index of the starting RB determined based on the PUSCH frequency resource allocation field of the RAR UL grant. The index of the starting RB of the second hop is S determined in Method 2-1 or Method 2-2. mod (1) can be determined based on. For example, S initial (2) or S active (2) is the index of the starting RB determined as follows.

[0449] [Equation 18]

[0450] S mod (2) = ( S mod (1) + Offset ) mod N ULSB

[0451] [Equation 19]

[0452] S mod (2) = ( S mod (1) + Offset - S ULSB ) mod N ULSB + S ULSB

[0453] N in Equations 18 and 19 ULSB is the number of RBs included in the UL subband, and S ULSB is the index of the starting RB of the UL subband. In case of method 2-1, S mod (1)=0, S mod (2)=0, S ULSB =0 RB is the lowest RB in the frequency axis in the initial UL BWP, and for method 2-2, S mod (1)=0, S mod (2)=0, S ULSB An RB with =0 may be the lowest RB in the frequency axis in the active UL BWP.

[0454] In mathematical expressions 18 and 19, the offset can be determined by at least one method among Tables 18 to 20.

[0455] FIG. 17 is a diagram illustrating a terminal operation flowchart according to an embodiment of the present disclosure. The operation order of FIG. 17 may be changed, and some operations may be omitted.

[0456] Referring to FIG. 17, at step 1700, the UE can determine the starting RB index of the first hop and the number of consecutive RBs through the PUSCH frequency resource allocation field of the RAR UL grant. Here, the reference UL BWP may be a truncated active UL BWP or an initial UL BWP. For example, the reference UL BWP may be determined according to Table 17.

[0457] At step 1710, the terminal can determine the starting RB index of the first hop within the UL subband based on the starting RB index of the first hop within the reference UL BWP. For example, the starting RB index of the first hop can be determined based on at least one of the methods in Equations 2 to 13.

[0458] In step 1720, the terminal can determine whether the Msg3 PUSCH is frequency hopping through the Frequency hopping flag field of the RAR UL grant. If frequency hopping is indicated for the Msg3 PUSCH transmission, the terminal can determine the starting RB index of the second hop. The starting RB index of the second hop can be determined based on the starting RB index of the first hop determined in step 1710. For example, the starting RB index of the second hop can be determined according to Equations 18 and 19.

[0459] At step 1730, the terminal can transmit the first hop of Msg3 PUSCH based on the start RB index of the first hop determined at step 1710 in the UL subband, and can transmit the second hop of Msg3 PUSCH based on the start RB index of the second hop determined at step 1720.

[0460] [(RB allocation determination for PUCCH transmission on SBFD UL subband)]

[0461] After establishing an RRC connection, a terminal can configure PUCCH resources. The PUCCH resource configuration information may include the following parameters.

[0462] - PUCCH resource index (or ID): A unique index (or ID) of a PUCCH resource that can be used to indicate or identify a PUCCH resource.

[0463] - StartingPRB: This can be the starting RB index of the first frequency hop of PUCCH.

[0464] - intraSlotFrequencyHopping: Can indicate whether PUCCH is transmitted in a frequency hopping manner.

[0465] - SecondHopPRB: This may be the starting RB index of the second frequency hop of PUCCH.

[0466] - format: It can be the format of PUCCH. Here, the format of PUCCH can be one of the values ​​of format0, format1, format2, format3, and format4.

[0467] In one embodiment of the present disclosure, the terminal can use the PUCCH resource configuration in uplink symbols and UL subbands. More specifically, the terminal can determine the starting RB indices of the first and second frequency hops for PUCCH transmission based on StartingPRB and SecondHopPRB. The determination method is as follows.

[0468] In one method, when the PUCCH is scheduled on an uplink symbol and a SBFD symbol (a symbol in which a UL subband is configured), the UE can determine StartingPRB and SecondHopPRB using the RB numbering of the active UL BWP. That is, the RB with StartingPRB = 0 and the RB with SecondHopPRB = 0 can be the same RB as the lowest RB of the active UL BWP. That is, the UE can always determine the index of the starting RB of the PUCCH using the numbering of the active UL BWP, regardless of the type of symbol on which the PUCCH is scheduled.

[0469] When a terminal receives a PUCCH scheduled on an SBFD symbol (a symbol configured for a UL subband), StartingPRB and SecondHopPRB may not be RBs within the UL subband. In this case, the terminal can convert StartingPRB and SecondHopPRB into RBs within the UL subband through a frequency hopping function. Here, the frequency hopping function may be as follows.

[0470] [Equation 20]

[0471] Starting PRB of 1 st frequency hop in UL subband =

[0472] ((StartingPRB-S ULSB ) mod L ULSB )+S ULSB

[0473] Starting PRB of 2 nd frequency hop in UL subband =

[0474] ((SecondHopPRB-S ULSB ) mod L ULSB )+S ULSB

[0475] In equation 20, S ULSBis the index of the RB where the UL subband starts, which can follow the numbering of the active UL BWP. That is, S ULSB =0 RB may be the lowest RB in the frequency axis of the active UL BWP. L ULSB may be the number of RBs included in the UL sub-band.

[0476] Note that Equation 20 is only applicable when StartingPRB and SecondHopPRB are not RBs within the UL subband. Alternatively, Equation 20 can be used at all times. That is, Equation 20 can be applied even when StartingPRB and SecondHopPRB are RBs within the UL subband.

[0477] When a terminal is scheduled for a PUCCH in an SBFD symbol (a symbol configured for an UL subband), StartingPRB and SecondHopPRB may not be RBs included in the UL subband. In this case, the terminal may expect that the PUCCH resource will not be scheduled in the UL subband. That is, when the PUCCH resource is scheduled in the UL subband, the terminal may not transmit the PUCCH in the PUCCH resource.

[0478] In one method, when PUCCH is scheduled to the UE in an uplink symbol, StartingPRB and SecondHopPRB can be determined using the RB numbering of the active UL BWP. That is, the RB with StartingPRB = 0 and the RB with SecondHopPRB = 0 can be the same RB as the lowest RB of the active UL BWP. When scheduled in an SBFD symbol (a symbol in which a UL subband is configured), StartingPRB and SecondHopPRB can be determined using the RB numbering of the UL subband. That is, the RB with StartingPRB = 0 and the RB with SecondHopPRB = 0 can be the same RB as the lowest RB of the UL subband. That is, although StartingPRB and SecondHopPRB are configured by a higher layer signal, the interpretation of StartingPRB and SecondHopPRB can be determined by the UE depending on the type of symbol in which the PUCCH is scheduled.

[0479] In one embodiment of the present disclosure, a terminal may additionally set the following parameters for a UL sub-band to a PUCCH resource.

[0480] - StartingPRBonSBFD: This can be the starting RB index of the first frequency hop of PUCCH in the SBFD symbol.

[0481] - SecondHopPRBonSBFD: This may be the starting RB index of the second frequency hop of PUCCH in the SBFD symbol.

[0482] For reference, other parameters of the PUCCH resource, such as PUCCH resource index (or ID), intraSlotFrequencyHopping, and format, can be commonly used in UL symbols and UL subbands.

[0483] The UE can determine the index of the RB on which the PUCCH is transmitted in the UL subband through StartingPRBonSBFD and SecondHopPRBonSBFD. More specifically, when the UE is scheduled for a PUCCH in an SBFD symbol (a symbol on which a UL subband is configured), the UE can determine the index of the RB on which the PUCCH is transmitted in the UL subband through StartingPRBonSBFD and SecondHopPRBonSBFD, and when the UE is scheduled for a PUCCH in an UL symbol, the UE can determine the index of the RB on which the PUCCH is transmitted in the UL symbol through StartingPRB and SecondHopPRB.

[0484] When determining the index of the RB where the PUCCH is transmitted within the UL sub-band through StartingPRBonSBFD and SecondHopPRBonSBFD, the terminal may use one of the following methods.

[0485] In one method, StartingPRBonSBFD and SecondHopPRBonSBFD can be determined using the RB numbering of the active UL BWP. That is, the RB with StartingPRB = 0 and the RB with SecondHopPRB = 0 can be the same RB as the lowest RB of the active UL BWP. That is, the UE can always determine the index of the starting RB of the PUCCH using the numbering of the active UL BWP, regardless of the type of symbol on which the PUCCH is scheduled.

[0486] The UE may not have RBs in the UL subband, StartingPRBonSBFD and SecondHopPRBonSBFD . In this case, the UE may use a frequency hopping function to convert StartingPRBonSBFD and SecondHopPRBonSBFD to RBs in the UL subband. The frequency hopping function may be as follows.

[0487] [Equation 21]

[0488] Starting PRB of 1 st frequency hop in UL subband =

[0489] ((StartingPRBonSBFD -S ULSB ) mod L ULSB )+S ULSB

[0490] Starting PRB of 2 nd frequency hop in UL subband =

[0491] ((SecondHopPRBonSBFD -S ULSB ) mod L ULSB )+S ULSB

[0492] S in Equation 21 ULSB is the index of the RB where the UL subband starts, which can follow the numbering of the active UL BWP. That is, S ULSB =0 RB may be the lowest RB in the frequency axis of the active UL BWP. L ULSB may be the number of RBs included in the UL sub-band.

[0493] Note that Equation 21 is only applicable when StartingPRBonSBFD and SecondHopPRBonSBFD are not RBs included in the UL subband. Alternatively, Equation 21 can always be used. That is, Equation 21 can be applied even when StartingPRBonSBFD and SecondHopPRBonSBFD are RBs included in the UL subband.

[0494] When the terminal receives a PUCCH scheduled on an SBFD symbol (a symbol configured for a UL subband), StartingPRBonSBFD and SecondHopPRBonSBFD may not be RBs included in the UL subband. In this case, the terminal may expect that the PUCCH resource will not be scheduled on the UL subband. That is, when the PUCCH resource is scheduled on a UL subband, the terminal may not transmit the PUCCH on the PUCCH resource.

[0495] In one method, when a terminal is scheduled for a PUCCH in an SBFD symbol (a symbol in which a UL subband is configured), StartingPRBonSBFD and SecondHopPRBonSBFD can be determined using the RB numbering of the UL subband. That is, the RB with StartingPRBonSBFD = 0 and the RB with SecondHopPRBonSBFD = 0 can be the same RB as the lowest RB of the UL subband.

[0496] The embodiments of the present disclosure described above can be performed by the terminal of FIG. 18 and the base station of FIG. 19.

[0497] FIG. 18 is a diagram illustrating the structure of a terminal in a wireless communication system according to an embodiment of the present disclosure.

[0498] Referring to FIG. 18, the terminal may include a transceiver, which refers to a terminal receiving unit (1800) and a terminal transmitting unit (1810), a memory (not shown), and a terminal processing unit (1805, or a terminal control unit or processor). Depending on the communication method of the terminal described above, the transceiver units (1800, 1810), the memory, and the terminal processing unit (1805) of the terminal may operate. The terminal processing unit (1805, or processor) may control the operation of the terminal according to each of the above-described embodiments as well as a combination of at least one embodiment. However, the components of the terminal are not limited to the above-described examples. For example, the terminal may include more or fewer components than the above-described components. In addition, the transceiver, the memory, and the processor may be implemented in the form of a single chip.

[0499] A transceiver unit can transmit and receive signals to and from a base station. The signals may include control information and data. To this end, the transceiver unit may include an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and down-converts the frequency of a received signal. However, this is only one embodiment of the transceiver unit, and the components of the transceiver unit are not limited to the RF transmitter and RF receiver.

[0500] Additionally, the transceiver can receive a signal through a wireless channel and output it to the processor, and transmit a signal output from the processor through the wireless channel.

[0501] Memory can store programs and data necessary for the terminal's operation. Furthermore, memory can store control information or data included in signals transmitted and received by the terminal. Memory can be comprised of a storage medium, such as ROM, RAM, a hard disk, CD-ROM, or DVD, or a combination of such storage media. Furthermore, there can be multiple memories.

[0502] In addition, the processor may control a series of processes so that the terminal can operate according to the above-described embodiment. For example, the processor may be configured to transmit a random access preamble and receive an RAR in response to the random access preamble. In this case, the RAR may include an UL grant that schedules PUSCH transmission. In addition, the processor may be configured to determine frequency domain resource allocation for the PUSCH transmission based on the UL grant, and transmit message 3 (Msg3) on the PUSCH based on the frequency domain resource allocation. When the PUSCH transmission is scheduled in a UL frequency subband within a downlink symbol, RB numbering may start from the first RB of the UL frequency subband, and the maximum number of RBs for the frequency domain resource allocation may be determined based on the number of RBs in the initial UL BWP. There may be a plurality of processors, and the processors may perform component control operations of the terminal by executing a program stored in a memory.

[0503] FIG. 19 is a diagram illustrating the structure of a base station in a wireless communication system according to an embodiment of the present disclosure.

[0504] Referring to FIG. 19, the base station may include a transceiver, which refers to a base station receiver (1900) and a base station transmitter (1910), a memory (not shown), and a base station processor (1905, or base station control unit or processor). According to the communication method of the base station described above, the transceiver (1900, 1910), the memory, and the base station processor (1905) of the base station may operate. The base station processor (1905, or processor) may control the operation of the base station according to each of the above-described embodiments as well as a combination of at least one embodiment. However, the components of the base station are not limited to the above-described examples. For example, the base station may include more or fewer components than the above-described components. In addition, the transceiver, the memory, and the processor may be implemented in the form of a single chip.

[0505] The transceiver can transmit and receive signals with the terminal. Here, the signals may include control information and data. To this end, the transceiver may be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and down-converts the frequency of a received signal. However, this is only one embodiment of the transceiver, and the components of the transceiver are not limited to the RF transmitter and RF receiver.

[0506] Additionally, the transceiver can receive a signal through a wireless channel and output it to the processor, and transmit the signal output from the processor through the wireless channel.

[0507] The memory can store programs and data necessary for the operation of the base station. Furthermore, the memory can store control information or data included in signals transmitted and received by the base station. The memory can be comprised of a storage medium, such as ROM, RAM, a hard disk, CD-ROM, or DVD, or a combination of such storage media. Furthermore, there can be multiple memories.

[0508] The processor may control a series of processes so that the base station can operate according to the embodiments of the present disclosure described above. For example, the processor may be configured to receive a random access preamble from a terminal, transmit a random access request (RAR) to the terminal in response to the random access preamble, and receive message 3 (Msg3) on a PUSCH from the terminal. In this case, the RAR may include an UL grant for scheduling PUSCH transmission, and frequency domain resource allocation for the PUSCH may be based on the UL grant. When the PUSCH transmission is scheduled in a UL frequency subband within a downlink symbol, RB numbering may start from the first RB of the UL frequency subband, and the maximum number of RBs for the frequency domain resource allocation may be determined based on the number of RBs in the initial UL BWP. There may be a plurality of processors, and the processors may perform component control operations of the base station by executing a program stored in a memory.

[0509] The methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

[0510] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. The one or more programs include instructions that cause the electronic device to execute methods according to the embodiments described in the claims or specification of the present disclosure.

[0511] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage device, compact disc ROM (CD-ROM), digital versatile discs (DVDs) or other forms of optical storage device, magnetic cassette. Or, they may be stored in a memory configured as a combination of some or all of these. In addition, each configuration memory may be included in multiple numbers.

[0512] Additionally, the program may be stored on an attachable storage device that is accessible via a communication network, such as the Internet, an intranet, a local area network (LAN), a wide local area network (WLAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device performing an embodiment of the present disclosure.

[0513] In the specific embodiments of the present disclosure described above, components included in the invention are expressed in the singular or plural form, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in the plural form may be composed of singular elements, or components expressed in the singular form may be composed of plural elements.

[0514] Meanwhile, the embodiments of the present disclosure disclosed in this specification and drawings are only specific examples to easily explain the technical contents of the present disclosure and help understand the present disclosure, and are not intended to limit the scope of the present disclosure. In other words, it will be apparent to those skilled in the art that other modifications based on the technical idea of ​​the present disclosure are possible. In addition, the above-mentioned embodiments can be combined and operated with each other as needed. For example, parts of one embodiment of the present disclosure and parts of another embodiment can be combined with each other to operate a base station and a terminal. For example, parts of the first embodiment and the second embodiment of the present disclosure can be combined with each other to operate a base station and a terminal. In addition, although the above-mentioned embodiments have been presented based on an FDD LTE system, other modifications based on the technical idea of ​​the above-mentioned embodiments can be implemented with other systems such as a TDD LTE system, 5G, or NR system.

[0515] Meanwhile, the order of description in the drawings explaining the method of the present invention does not necessarily correspond to the order of execution, and the order of precedence may be changed or executed in parallel.

[0516] Alternatively, the drawings illustrating the method of the present invention may omit some components and include only some components within a scope that does not harm the essence of the present invention.

[0517] In addition, the method of the present invention may be implemented by combining some or all of the contents included in each embodiment within a scope that does not harm the essence of the invention.

Claims

1. In a method performed by a terminal in a wireless communication system, Step of transmitting a random access preamble; A step of receiving a random access response (RAR) in response to the random access preamble, the RAR including an uplink (UL) grant for scheduling a physical uplink shared channel (PUSCH) transmission; A step of determining frequency domain resource allocation for the PUSCH transmission based on the UL grant; and A step of transmitting message 3 (Msg3) on a PUSCH based on the frequency domain resource allocation, A method in which, when the PUSCH transmission is scheduled in a UL frequency subband within a downlink symbol, resource block (RB) numbering starts from the first RB of the UL frequency subband, and the maximum number of RBs for frequency domain resource allocation is determined based on the number of RBs in an initial UL bandwidth part (BWP).

2. In paragraph 1, A method characterized in that the maximum number of RBs for the above frequency domain resource allocation is equal to the number of RBs in the initial UL BWP.

3. In paragraph 1, Further comprising a step of confirming that frequency hopping is applied to the above PUSCH transmission, A method characterized in that the frequency offset for the second hop of the frequency hopping is determined based on the number of RBs in the UL frequency subband.

4. In paragraph 1, A method characterized in that the hopping bits associated with the frequency hopping are determined based on the number of RBs in the initial UL BWP.

5. In a method performed by a base station in a wireless communication system, A step of receiving a random access preamble from a terminal; A step of transmitting a random access response (RAR) to the terminal in response to the random access preamble, wherein the RAR includes an uplink (UL) grant that schedules physical uplink shared channel (PUSCH) transmission; and A step of receiving message 3 (message 3, Msg3) from the terminal in PUSCH, Frequency domain resource allocation for the above PUSCH is based on the above UL grant, and A method in which, when the PUSCH transmission is scheduled in a UL frequency subband within a downlink symbol, resource block (RB) numbering starts from the first RB of the UL frequency subband, and the maximum number of RBs for frequency domain resource allocation is determined based on the number of RBs in an initial UL bandwidth part (BWP).

6. In paragraph 5, A method characterized in that the maximum number of RBs for the above frequency domain resource allocation is equal to the number of RBs in the initial UL BWP.

7. In paragraph 5, Further comprising a step of setting the value of the frequency hopping flag included in the UL grant to indicate that frequency hopping is applied to the PUSCH transmission, A method characterized in that the frequency offset for the second hop of the frequency hopping is determined based on the number of RBs in the UL frequency subband.

8. In paragraph 5, A method characterized in that the hopping bits associated with the frequency hopping are determined based on the number of RBs in the initial UL BWP.

9. In a wireless communication system, at the terminal, transceiver; and A processor operatively connected to the transceiver, the processor comprising: Transmit a random access preamble, In response to the random access preamble, a random access response (RAR) is received, wherein the RAR includes an uplink (UL) grant that schedules a physical uplink shared channel (PUSCH) transmission, Determine frequency domain resource allocation for the PUSCH transmission based on the UL grant, and Based on the above frequency domain resource allocation, message 3 (Msg3) is set to be transmitted on PUSCH, A terminal, wherein when the PUSCH transmission is scheduled in a UL frequency subband within a downlink symbol, resource block (RB) numbering starts from the first RB of the UL frequency subband, and the maximum number of RBs for frequency domain resource allocation is determined based on the number of RBs within an initial UL bandwidth part (BWP).

10. In paragraph 9, A terminal characterized in that the maximum number of RBs for the above frequency domain resource allocation is equal to the number of RBs in the initial UL BWP.

11. In paragraph 9, The processor is further configured to verify that frequency hopping is applied to the PUSCH transmission, and A terminal characterized in that the frequency offset for the second hop of the frequency hopping is determined based on the number of RBs in the UL frequency subband.

12. In paragraph 9, A terminal characterized in that the hopping bits associated with the frequency hopping are determined based on the number of RBs in the initial UL BWP.

13. In a wireless communication system, at a base station, transceiver; and A processor operatively connected to the transceiver, the processor comprising: Receive a random access preamble from the terminal, Transmitting a random access response (RAR) to the terminal in response to the random access preamble, wherein the RAR includes an uplink (UL) grant that schedules physical uplink shared channel (PUSCH) transmission, and It is set to receive message 3 (message 3, Msg3) from the above terminal in PUSCH, Frequency domain resource allocation for the above PUSCH is based on the above UL grant, and A base station, wherein when the PUSCH transmission is scheduled in a UL frequency subband within a downlink symbol, resource block (RB) numbering starts from the first RB of the UL frequency subband, and the maximum number of RBs for frequency domain resource allocation is determined based on the number of RBs within an initial UL bandwidth part (BWP).

14. In paragraph 13, A base station, characterized in that the maximum number of RBs for the above frequency domain resource allocation is equal to the number of RBs in the initial UL BWP.

15. In paragraph 13, The processor is further configured to set a value of a frequency hopping flag included in the UL grant to indicate that frequency hopping is applied to the PUSCH transmission, The frequency offset for the second hop of the above frequency hopping is determined based on the number of RBs in the above UL frequency subband, and A base station, characterized in that the hopping bits associated with the frequency hopping are determined based on the number of RBs in the initial UL BWP.

Images