Method and apparatus for transmitting msg3 pusch in a wireless communication system

Abstract

The disclosure provides a random access method in a wireless communication system. Specifically, a method performed by a terminal in a wireless communication system, comprising 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 a physical uplink shared channel (PUSCH) transmission; determining a frequency domain resource allocation for the PUSCH transmission based on the UL grant; and transmitting a message 3 (Msg3) on the PUSCH based on the frequency domain resource allocation, wherein if the PUSCH transmission is scheduled in an UL frequency sub-band within a downlink symbol, a resource block (RB) number starts from a first RB of the UL frequency sub-band, and a maximum number of RBs for the frequency domain resource allocation can be determined based on a number of RBs in an initial UL bandwidth part (BWP).

Description

Technical Field

[0001] This disclosure relates to the operation of terminals and base stations in wireless communication systems. Specifically, this disclosure relates to methods and apparatus for performing message 3 (Msg3) Physical Uplink Shared Channel (PUSCH) transmission. Background Technology

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

[0003] At the outset of 5G mobile communication technology development, standardization was underway regarding beamforming and massive MIMO to support services and meet performance requirements associated with enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC). This standardization aimed to mitigate radio wave path loss in millimeter waves and increase radio wave transmission distance; support parameter sets for dynamic operation (e.g., operating multiple subcarrier spacings) to efficiently utilize millimeter wave resources and time slot formats; initial access technologies to support multi-beam transmission and broadband; the definition and operation of bandwidth portions (BWP); new channel decoding methods (such as low-density parity-check (LDPC) codes for large data transmissions and polar codes for highly reliable transmission of control information); L2 preprocessing; and network slicing for providing dedicated networks for specific services.

[0004] Currently, given the services supported by 5G mobile communication technology, discussions are underway regarding improvements and performance enhancements to the initial 5G mobile communication technology. Physical layer standardization for technologies such as Vehicle-to-Everything (V2X) is also in place, designed to assist autonomous vehicle driving decisions based on information about the vehicle's location and status transmitted by the vehicle, and to enhance user convenience. This includes NR-U (New Radio Unlicensed) and NR UE Energy Saving (NTN), which are UE-satellite direct communication technologies used to provide coverage and positioning in areas where communication with terrestrial networks is unavailable.

[0005] Furthermore, standardization is ongoing for technologies within the air interface architecture / protocol, such as the Industrial Internet of Things (IIoT) for supporting new services through interoperability and convergence with other industries, Integrated Access and Backhaul (IAB) for providing nodes for network service area extension by supporting wireless backhaul and access links in an integrated manner, mobility enhancements including conditional handover and Dual Active Protocol Stack (DAPS) handover, and two-step random access (two-step RACH for NR) for simplifying the random access process. Standardization is also underway for 5G baseline architectures (e.g., service-based architectures or service-based interfaces) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, as well as system architectures / services for Mobile Edge Computing (MEC) based on UE location reception services.

[0006] With the commercialization of 5G mobile communication systems, the already exponentially growing number of connected devices will be connected to the communication network, thus necessitating enhanced functionality and performance of 5G mobile communication systems as well as integrated operation of connected devices. To this end, new research related to extended reality (XR) has been arranged to effectively support augmented reality (AR), virtual reality (VR), mixed reality (MR), etc., by leveraging artificial intelligence (AI) and machine learning (ML), AI service support, metaspace service support, and drone communication to improve 5G performance and reduce complexity.

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

[0008] With the development of wireless communication systems as described above, various services can be provided; therefore, solutions are needed to smoothly deliver these services. Summary of the Invention

[0009] [Technical Issues]

[0010] The embodiments of this disclosure are intended to provide an apparatus and method capable of effectively providing services in a mobile communication system.

[0011] Specifically, embodiments of this disclosure aim to provide a method and apparatus for performing a random access procedure in subband non-overlapping full duplex (SBFD).

[0012] Furthermore, embodiments of this disclosure are intended to provide a method and apparatus for determining resources for transmitting the Physical Uplink Control Channel (PUCCH) in an SBFD uplink (UL) subband.

[0013] [Technical Solution]

[0014] According to one aspect of this disclosure, a method performed by a terminal in a wireless communication system may include: 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 transmission of the Physical Uplink Shared Channel (PUSCH); determining a frequency domain resource allocation for PUSCH transmission based on the UL grant; and transmitting message 3 (Msg3) in the PUSCH based on the frequency domain resource allocation, wherein, if the PUSCH transmission is scheduled in a UL frequency subband within a downlink symbol, the resource block (RB) number may start from the first RB of the UL frequency subband, and the maximum number of RBs for frequency domain resource allocation may be determined based on the number of RBs within the initial UL bandwidth portion (BWP).

[0015] According to another aspect of this disclosure, a method performed by a base station in a wireless communication system may include: receiving a random access preamble from a terminal; sending a random access response (RAR) to the terminal in response to the random access preamble, wherein the RAR includes an uplink (UL) grant for scheduling transmissions of the Physical Uplink Shared Channel (PUSCH); and receiving message 3 (Msg3) from the terminal in the PUSCH, wherein frequency domain resource allocation for the PUSCH may be based on the UL grant, and if the PUSCH transmission is scheduled in a UL frequency subband within a downlink symbol, the resource block (RB) number may start from the first RB of the UL frequency subband, and the maximum number of RBs for frequency domain resource allocation may be determined based on the number of RBs within the initial UL bandwidth portion (BWP).

[0016] In a wireless communication system according to another aspect of this disclosure, a terminal may include a transceiver and a processor operatively connected to the transceiver, and the processor may be configured to: transmit a random access preamble; receive a random access response (RAR) in response to the random access preamble, wherein the RAR includes an uplink (UL) grant for scheduling transmission of the Physical Uplink Shared Channel (PUSCH); determine a frequency domain resource allocation for PUSCH transmission based on the UL grant; and transmit message 3 (Msg3) in the PUSCH based on the frequency domain resource allocation, wherein, if the PUSCH transmission is scheduled in a UL frequency subband within a downlink symbol, the resource block (RB) number may start from the first RB of the UL frequency subband, and the maximum number of RBs for frequency domain resource allocation may be determined based on the number of RBs within the initial UL bandwidth portion (BWP).

[0017] In a wireless communication system according to another aspect of this disclosure, the base station may include a transceiver and a processor operatively connected to the transceiver, and the processor may be configured to: receive a random access preamble from a terminal; send a random access response (RAR) to the terminal in response to the random access preamble, wherein the RAR includes an uplink (UL) grant for scheduling transmission of the Physical Uplink Shared Channel (PUSCH); and receive message 3 (Msg3) from the terminal in the PUSCH, wherein frequency domain resource allocation for the PUSCH may be based on UL grant, and if the PUSCH transmission is scheduled in a UL frequency subband within a downlink symbol, the resource block (RB) number may start from the first RB of the UL frequency subband, and the maximum number of RBs for frequency domain resource allocation may be determined based on the number of RBs within the initial UL bandwidth portion (BWP).

[0018] [Beneficial Effects]

[0019] According to embodiments of this disclosure, services can be effectively provided in a mobile communication system.

[0020] Furthermore, according to embodiments of this disclosure, resources for performing a random access procedure in an SBFD are determined, and the random access procedure can be performed based on the determined resources.

[0021] Furthermore, according to embodiments of this disclosure, the resources for PUCCH transmission in the UL subband for SBFD can be determined. Attached Figure Description

[0022] Figure 1 This is a diagram illustrating the basic structure of the time-frequency domain according to an embodiment of the present disclosure, which is a radio resource region in a wireless communication system for transmitting data or control channels.

[0023] Figure 2This is a diagram illustrating the structure of frames, subframes, and time slots in a wireless communication system according to an embodiment of the present disclosure.

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

[0025] Figure 4 This is a diagram illustrating an example of a control resource set for transmitting a downlink control channel in a wireless communication system according to an embodiment of the present disclosure.

[0026] Figure 5 This is a diagram illustrating an example of a basic unit for configuring the time and frequency resources of a downlink control channel in a wireless communication system according to an embodiment of the present disclosure.

[0027] Figure 6 This is a diagram used to explain a method for a base station and a UE to transmit and receive data in a wireless communication system, taking into account downlink data channel and rate matching resources, according to embodiments of the present disclosure.

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

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

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

[0031] Figure 10 This is a diagram illustrating the radio protocol structure of a base station and a UE in a wireless communication system under single-cell, carrier aggregation, and dual connectivity scenarios according to embodiments of the present disclosure.

[0032] Figure 11 A random access procedure in a wireless communication system according to an embodiment of the present disclosure is illustrated.

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

[0034] Figure 13 This is a diagram illustrating the effective RACH timing in TDD and SBFD configurations according to embodiments of the present disclosure.

[0035] Figure 14 This is a diagram illustrating a reference UL BWP according to an embodiment of the present disclosure.

[0036] Figure 15 This illustrates a scenario where an SBFD resource or UL subband according to an embodiment of the present disclosure is not included in the reference UL BWP.

[0037] Figure 16 This is a flowchart illustrating the operation of a UE according to an embodiment of the present disclosure.

[0038] Figure 17 This is a flowchart illustrating the operation of a UE according to an embodiment of the present disclosure.

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

[0040] Figure 19 This is a diagram illustrating the structure of a base station in a wireless communication system according to an embodiment of the present disclosure. Detailed Implementation

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

[0042] In describing the embodiments, descriptions of technical content that is well-known in the art to which this disclosure pertains but is not directly related to this disclosure will be omitted. This is to more clearly describe the subject matter of this disclosure without obscuring the subject matter by omitting any unnecessary descriptions.

[0043] For the same reason, some elements may be exaggerated, omitted, or shown schematically in the accompanying drawings. Furthermore, the size of each element does not perfectly reflect its actual size. In the drawings, identical or corresponding elements have the same reference numerals.

[0044] The advantages and features of this disclosure, as well as methods for achieving these advantages and features, will become clear from the exemplary embodiments described in detail below with reference to the accompanying drawings. However, this disclosure is not limited to the exemplary embodiments disclosed herein, but will be implemented in various forms. Exemplary embodiments of this disclosure are provided to fully disclose the disclosure, and those skilled in the art will fully understand the scope of the disclosure. This disclosure will be defined only by the scope of the appended claims. Throughout the specification, the same reference numerals denote the same components. Furthermore, in the description of this disclosure, specific descriptions of relevant functions or configurations are omitted where it is determined that a particular description might unnecessarily obscure the subject matter of the disclosure. Additionally, the terminology used herein is defined in consideration of the functions in this disclosure and may vary depending on the intent of the user or operator or common practice. Therefore, definitions should be based on the entirety of this specification.

[0045] In the following description, a base station is an entity that performs resource allocation for a UE and can be at least one of a gNode B, eNode B, Node B, base station (BS), radio access unit, base station controller, or node on a network. A terminal can include a user equipment (UE), mobile station (MS), cellular phone, smartphone, computer, or multimedia system capable of performing communication functions. In this disclosure, the downlink (DL) is the radio transmission path of signals sent from the base station to the UE, while the uplink (UL) is the signal sent from the UE to the base station. In the following description, embodiments of this disclosure are illustrated using a 5G system as an example, but the embodiments of this disclosure can be applied to other communication systems with similar technical backgrounds or channel configurations. For example, LTE or LTE-A mobile communications and mobile communication technologies developed after 5G can be included therein. Furthermore, this disclosure can be applied to other communication systems with modifications without substantially departing from the scope of this disclosure as determined by those skilled in the art. The content of this disclosure applies to frequency division duplex (FDD) and time division duplex (TDD) systems.

[0046] Here, it should be understood that each block in the flowchart illustration, and combinations of blocks in the flowchart illustration, can be executed by computer program instructions. These computer program instructions can be loaded onto the processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create components for performing the functions specified in the flowchart block(s). These computer program instructions can also be stored in a non-transitory computer-usable or computer-readable storage medium that can instruct the computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-usable or computer-readable storage medium produce an article of art comprising instruction components that perform the functions specified in the flowchart block(s). The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable data processing apparatus, thereby producing a process executed by the computer, such that the instructions, which execute on the computer or other programmable data processing apparatus, provide steps for performing the functions specified in the flowchart block(s).

[0047] Furthermore, each block may represent a module, segment, or section of code, comprising one or more executable instructions for performing a specified logical function(s). It should also be noted that in some alternative implementations, the functions described in a block may not occur in this order. For example, depending on the functions involved, two consecutively shown blocks may actually be executed substantially simultaneously, or sometimes they may be executed in reverse order.

[0048] As used in embodiments of this disclosure, "~unit" can refer to a software element or hardware element that performs a predetermined function, such as a field-programmable gate array (FPGA) or an application-specific integrated circuit (ASIC). However, the term including "~unit" does not always have a meaning limited to software or hardware. A "~unit" can be configured to be stored in an addressable storage medium or can execute one or more processors. Therefore, "~unit" includes, for example, software elements, object-oriented software elements, components such as class elements and task elements, processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and parameters. The components and functions provided by "~units" can be combined into a smaller number of components and "~units," or can be classified as additional components and "~units." Furthermore, components and "~units" can be implemented as one or more central processing units (CPUs) within a playback device or a secure multimedia card. Additionally, in embodiments, "unit" can include one or more processors.

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

[0050] As a representative example of a broadband wireless communication system, the LTE system employs Orthogonal Frequency Division Multiplexing (OFDM) in the downlink (DL) and Single-Carrier Frequency Division Multiple Access (SC-FDMA) in the uplink (UL). The uplink refers to the radio link through 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)), while the downlink refers to the radio link through which the base station transmits data or control signals to the UE. As described above, the multiple access schemes can distinguish each user's data or control information by allocating and operating time-frequency resources for carrying data or control information to each user in a way that avoids overlap, i.e., establishing orthogonality.

[0051] As the future communication system following LTE, 5G communication systems should be able to freely reflect the diverse needs of users and service providers, and therefore should support services that simultaneously meet various requirements. Services considered for 5G communication systems include enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC).

[0052] eMBB aims to provide data transmission rates that are further enhanced than those supported by existing LTE, LTE-a, or LTE-Pro systems. For example, in a 5G communication system, from the perspective of a base station, eMBB should be able to provide a peak data rate of 20Gbps in the downlink and 10Gbps in the uplink. Furthermore, 5G communication systems should improve the user-perceived data rate for the UE while providing peak data rates. To meet these requirements, various transmission and reception technologies need to be improved, including further refined multiple-input multiple-output (MIMO) transmission techniques. Moreover, while LTE uses a maximum transmission bandwidth of 20MHz in the 2GHz band, 5G communication systems can meet the required data transmission rates by using wider frequency bandwidths than 20MHz in the 3 to 6GHz or 6GHz or higher frequency bands.

[0053] Meanwhile, mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. mMTC needs to support large-scale UE access within a cell, improve UE coverage, improve battery life, and reduce UE costs to effectively deliver IoT. Since IoT will be attached to various sensors and devices to provide communication functions, a large number of UEs (e.g., 1,000,000 UEs / km) needs to be supported within the cell. 2 Furthermore, due to the nature of the service, UEs supporting mMTC are likely to be located in shadow areas not covered by the cell, such as the basement of a building. Therefore, UEs may require a wider coverage area compared to other services offered in 5G communication systems. UEs supporting mMTC should be configured as low-cost UEs, and due to the difficulty in frequently replacing the UE's battery, they may require very long battery life, such as 10 to 15 years.

[0054] Finally, in the case of URLLC, it is a cellular-based wireless communication service for a specific purpose (mission-critical). For example, services such as remote control of robots or machinery, industrial automation, unmanned aerial vehicles, remote healthcare, and emergency alerts could be considered. Therefore, the communication provided by URLLC should offer very low latency and very high reliability. For example, services supporting URLLC should meet an air interface latency of less than 0.5 milliseconds while requiring a packet error rate of 10-1. -5 Or even lower. Therefore, for services that support URLLC, 5G systems should provide shorter transmission time intervals (TTIs) than other services, and may require design requirements to allocate wide resources in the frequency band to ensure the reliability of the communication link.

[0055] 5G's three services—eMBB, URLLC, and mMTC—can be multiplexed and transmitted within a single system. In this case, different transmission and reception technologies and parameters can be used between the services to meet their varying requirements. Of course, 5G is not limited to these three services.

[0056] [NR Time and Frequency Resources]

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

[0058] Figure 1 This is a diagram illustrating the basic structure of the time-frequency domain according to an embodiment of the present disclosure, which is a radio resource region in a wireless communication system for transmitting data or control channels.

[0059] refer to Figure 1 The horizontal axis represents the time domain, and the vertical axis represents the frequency domain. The basic unit of resources in both the time and frequency domains is a resource element (RE) 101, which can be defined as an orthogonal frequency division multiplexing (OFDM) symbol 102 on the time axis and a subcarrier 103 on the frequency axis. In the frequency domain, One (e.g., 12) consecutive REs can be configured into a resource block (RB) 104. In the time domain, a subframe 110 can be configured with one or more time slots.

[0060] Figure 2 This is a diagram illustrating the structure of frames, subframes, and time slots in a wireless communication system according to an embodiment of the present disclosure.

[0061] exist Figure 2 The diagram illustrates a structural example of frame 200, subframe 201, and time slots 202 and 203. A frame 200 can be defined as 10 ms. A subframe 201 can be defined as 1 ms; therefore, a frame 200 can be configured with a total of 10 subframes 201. A time slot 202 or 203 can be defined as 14 OFDM symbols (i.e., the number of symbols per time slot is...). (=14). A subframe 201 can be configured with one or more time slots 202 and 203, and the number of time slots 202 and 203 in each subframe 201 can be different depending on the configuration values ​​μ204 and μ205 of the subcarrier spacing. Figure 2 The example shows the subcarrier spacing configuration values ​​of μ=0 204 and μ=1 205. With μ=0 204, a subframe 201 can be configured with one time slot 202, while with μ=1 205, two time slots 203 can be configured. That is, the number of time slots per subframe ( The number of time slots per frame can vary depending on the configuration value μ of the subcarrier spacing. The value of μ can also be varied. The value of μ is configured according to the subcarrier spacing. and It can be defined according to Table 1 below.

[0062] Table 1

[0063]

[0064] [Bandwidth Component (BWP)]

[0065] The following section will describe in detail the configuration of the bandwidth portion (BWP) in a 5G communication system with reference to the accompanying drawings.

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

[0067] Figure 3 An example of a UE bandwidth 300 configuration with two bandwidth sections is shown, namely bandwidth section #1 (BWP#1) 301 and bandwidth section #2 (BWP#2) 302. The base station can configure one or more bandwidth sections for the UE, and can configure the information shown in Table 2 below for each bandwidth section.

[0068] Table 2

[0069]

[0070] Of course, this disclosure is not limited to the examples above. In addition to configuration information, various parameters related to bandwidth portions can be configured for the UE. The base station can deliver information to the UE via higher-layer signaling (e.g., Radio Resource Control (RRC) signaling). At least one of the configured bandwidth portions can be activated. Whether a configured bandwidth portion is activated can be semi-statically delivered to the UE from the base station via RRC signaling or dynamically delivered via downlink control information (DCI).

[0071] According to some embodiments, prior to RRC connection, the UE may be configured with an initial bandwidth portion (initial BWP) for initial access from the base station via the main information block (MIB). More specifically, during the initial access phase, the UE may receive configuration information for the control resource set (CORESET) and the search space, wherein the PDCCH for receiving system information required for initial access (which may correspond to the residual system information (RMSI) or system information block 1 (SIB1)) can be transmitted via the MIB. The control resource set and search space configured by the MIB can be considered as identifier (ID) 0, respectively. The base station may notify the UE of the configuration information of control resource set #0 via the MIB, such as frequency allocation information, time allocation information, and parameter set. In addition, the base station may notify the UE of the configuration information for the monitoring period and timing of control resource set #0 via the MIB, i.e., the configuration information for search space #0. The UE may consider the frequency domain configured as control resource set #0 obtained from the MIB as the initial bandwidth portion for initial access. In this case, the identifier (ID) of the initial bandwidth portion can be considered as 0.

[0072] The bandwidth configuration supported in 5G can be used for a variety of purposes.

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

[0074] Furthermore, according to some embodiments, the base station can configure multiple bandwidth portions for the UE to support different parameter sets. For example, to support a UE using subcarrier spacings of 15 kHz and 30 kHz for data transmission and reception, the two bandwidth portions can be configured with subcarrier spacings of 15 kHz and 30 kmz, respectively. Different bandwidth portions can be frequency-division multiplexed, and when data is intended to be transmitted and received at a specific subcarrier spacing, the bandwidth portion configured with the corresponding subcarrier spacing can be activated.

[0075] Furthermore, according to some embodiments, the base station can configure bandwidth portions with different bandwidth sizes for the UE to reduce UE power consumption. For example, if the UE supports a very large bandwidth (e.g., 100MHz) and always transmits and receives data at that bandwidth, very high power consumption may occur. In particular, from a power consumption perspective, monitoring an unnecessary downlink control channel with a large 100MHz bandwidth may be very inefficient when there is no service. To reduce UE power consumption, the base station can configure a bandwidth portion with a relatively small bandwidth for the UE, such as a 20MHz bandwidth portion. When there is no service, the UE can perform monitoring operations in the 20MHz bandwidth portion, and when data is received, the UE can transmit and receive data using the 100MHz bandwidth portion according to the base station's instructions.

[0076] In the method for configuring the bandwidth portion, the UE, prior to RRC connection, can receive configuration information for the initial bandwidth portion via the Master Information Block (MIB) during the initial access phase. More specifically, the UE can be configured with a Control Resource Set (CORESET) for the downlink control channel, through which downlink control information (DCI) of the Scheduling System Information Block (SIB) can be transmitted from the MIB of the Physical Broadcast Channel (PBCH). The bandwidth of the Control Resource Set configured by the MIB can be considered as the initial bandwidth portion, and through the configured initial bandwidth portion, the UE can receive the Physical Downlink Shared Channel (PDSCH) through which the SIB is transmitted. In addition to receiving the SIB, the initial bandwidth portion can also be used for other System Information (OSI), paging, and random access.

[0077] [Bandwidth Partial (BWP) Switching]

[0078] When one or more bandwidth portions are configured for a UE, the base station can use the bandwidth portion indicator field within the DCI to indicate the switching (or change, conversion) of the bandwidth portion used for the UE. For example, in Figure 3 In the case where the currently active bandwidth portion of the UE is bandwidth portion #1 301, the base station can indicate bandwidth portion #2 302 to the UE using a bandwidth portion indicator in the DCI, and the UE can perform a bandwidth portion switch to the bandwidth portion #2 302 indicated by the bandwidth portion indicator in the received DCI.

[0079] As mentioned above, since DCI-based bandwidth handover can be indicated by DCI-scheduled PDSCH or PUSCH, when a UE receives a bandwidth handover request, the UE should be able to easily perform reception or transmission of the PDSCH or PUSCH scheduled by the corresponding DCI within the switched bandwidth portion. To this end, the standard specifies the delay time (T) required for bandwidth handover.BWP Requirements, for example, can be defined as shown in Table 3.

[0080] Table 3

[0081]

[0082] The requirement for bandwidth portion handover latency depends on whether the UE supports Type 1 or Type 2. The UE can report the supported bandwidth portion latency type to the base station.

[0083] Based on the aforementioned requirements regarding bandwidth partial handover delay time, if the UE receives the DCI including the bandwidth partial handover indicator in time slot n, the UE can proceed no later than time slot n+T. BWP The handover to the new bandwidth portion indicated by the bandwidth portion handover indicator is completed at the designated time, and transmission and reception can proceed within the new bandwidth portion for data channels scheduled by the corresponding DCI. When the base station intends to schedule data channels with the new bandwidth portion, it can consider the UE's bandwidth portion handover delay time (T). BWP This is used to determine the temporal resource allocation for data channels. In other words, in the method for determining the temporal resource allocation for data channels when scheduling data channels with new bandwidth portions, the base station can schedule the corresponding data channel after the bandwidth portion handover delay time. Therefore, the UE may not expect the DCI indication indicating bandwidth portion handover to be less than the bandwidth portion handover delay time (T). BWP The time slot offset (K0 or K2) value.

[0084] If the UE receives a DCI indicating a partial bandwidth switch (e.g., DCI format 1_1 or 0_1), the UE may refrain from any transmission or reception for the time interval from the third symbol of the slot in which the PDCCH containing the corresponding 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 within the corresponding DCI. For example, if the UE receives a DCI indicating a partial bandwidth switch in slot n, and the slot offset value indicated by the corresponding DCI is K, the UE may refrain from any transmission or reception from the third symbol of slot n to the symbols preceding slot n+K (i.e., the last symbol of slot n+K-1).

[0085] [SS / PBCH block]

[0086] Next, the SS (Synchronization Signal) / PBCH block in 5G will be described.

[0087] The SS / PBCH block can refer to a physical layer channel block consisting of the primary SS (PSS), secondary SS (SSS), and PBCH. A detailed description follows.

[0088] -PSS: As a reference signal for downlink time / frequency synchronization, it provides some information about the cell ID.

[0089] -SSS: It serves as a reference for downlink time / frequency synchronization and provides residual cell ID information not available in PSS. Additionally, it can be used as a reference signal for PBCH demodulation.

[0090] -PBCH: It provides the basic system information required for the UE to transmit and receive data and control channels. This basic system information may include search space-related control information representing radio resource mapping information for control channels, scheduling control information for separate data channels used to transmit system information, etc.

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

[0092] The UE can detect the PSS and SSS during the initial access phase and can decode the PBCH. It can obtain the MIB from the PBCH and configure the control resource set (CORESET) #0 (which may correspond to the control resource set index 0). Assuming the selected SS / PBCH block and the demodulation reference signal (DMRS) transmitted in control resource set #0 are quasi-co-located (QCL), the UE can perform monitoring of control resource set #0. The UE can receive system information as downlink control information transmitted in control resource set #0. The UE can obtain the random access channel (RACH) configuration information required for initial access from the received system information. The UE can send the physical RACH (PRACH) to the base station considering the selected SS / PBCH index, and the base station receiving the PRACH can obtain information about the SS / PBCH block index selected by the UE. The base station can know which block the UE selected in each SS / PBCH block and monitor the associated control resource set #0.

[0093] [PDCCH: DCI related]

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

[0095] In 5G systems, scheduling information for uplink data (or Physical Uplink Shared Channel (PUSCH)) or downlink data (or Physical Downlink Shared Channel (PDSCH)) is delivered from the base station to the UE via DCI. The UE can monitor the backoff DCI format and the non-backoff DCI format of the PUSCH or PDSCH. The backoff DCI format can be configured with predefined fixed fields between the base station and the UE, while the non-backoff DCI format can include configurable fields.

[0096] DCI messages are transmitted via the Physical Downlink Control Channel (PDCCH) through channel decoding and modulation processes. Cyclic Redundancy Check (CRC) is appended to the DCI message payload and can be scrambled using a Radio Network Temporary Identifier (RNTI) corresponding to the UE's identifier. Different RNTIs can be used depending on the purpose of the DCI message, such as UE-specific data transmission, power control commands, or random access responses. That is, the RNTI is not explicitly transmitted but is sent within the CRC calculation process. Upon receiving a DCI message transmitted on the PDCCH, the UE uses the assigned RNTI to check the CRC, and if the CRC check result is correct, the UE knows that a corresponding message has been sent.

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

[0098] DCI format 0_0 can be used as a fallback DCI for scheduling PUSCH, and in this case, CRC can be scrambled using C-RNTI. The DCI format 0_0 with its CRC scrambled using C-RNTI can include, for example, information from Table 4.

[0099] Table 4

[0100]

[0101] DCI format 0_1 ​​can be used as a non-back-off DCI for scheduling PUSCH, and in this case, CRC can be scrambled using C-RNTI. The DCI format 0_1 ​​with CRC scrambled using C-RNTI can include, for example, information from Table 5.

[0102] Table 5

[0103]

[0104] DCI format 1_0 can be used as a fallback DCI for scheduling PDSCH, and in this case, CRC can be scrambled using C-RNTI. DCI format 1_0 with CRC scrambled using C-RNTI can include, for example, information from Table 6.

[0105] Table 6

[0106]

[0107] DCI format 1_1 can be used as a non-back-off DCI for scheduling PDSCH, and in this case, CRC can be scrambled using C-RNTI. DCI format 1_1 with CRC scrambled using C-RNTI can include, for example, information from Table 7.

[0108] Table 7

[0109]

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

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

[0112] Figure 4 This is a diagram illustrating an example of a control resource set (CORESET) according to an embodiment of the present disclosure, wherein a downlink control channel is transmitted in a wireless communication system.

[0113] Figure 4 An example is shown where two control resource sets (control resource set #1 401 and control resource set #2 402) are configured within a time slot 420 on the time axis and within a UE bandwidth portion 410 on the frequency axis. Control resource sets 401 and 402 can be configured within a specific frequency resource 403 within the total UE bandwidth portion 410 on the frequency axis. On the time axis, it can be configured with one or more OFDM symbols, and this can be defined as a control resource set duration 404. Reference Figure 4In the example shown, control resource set #1 401 is configured to have a control resource set duration of 2 symbols, while control resource set #2 402 is configured to have a control resource set duration of 1 symbol.

[0114] The control resource set in 5G described above can be configured from the base station to the UE via higher-layer signaling (e.g., system information, master information block (MIB), or radio resource control (RRC) signaling). Configuring the control resource set for the UE means providing information such as the control resource set identifier (identifier), the frequency location of the control resource set, and the control resource set symbol length. For example, the information in Table 8 may be included.

[0115] Table 8

[0116]

[0117] In Table 8, the tci-StatesPDCCH (Transmission Configuration Indication (TCI) status) configuration information may include information on one or more Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) block indices or Channel State Information Reference Signal (CSI-RS) indices that have a quasi-co-located (QCL) relationship with the DMRS transmitted in the corresponding control resource set.

[0118] Figure 5 This is a diagram illustrating an example of a basic unit for configuring the time and frequency resources of a downlink control channel in a wireless communication system according to an embodiment of the present disclosure.

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

[0120] like Figure 5 As shown, in 5G, where the basic unit for allocating downlink control channels is called a Control Channel Element (CCE) 504, one CCE 504 can be configured with multiple REG 503s. Figure 5Taking REG 503 as an example, a REG 503 can be configured with 12 REs, and if a CCE 504 is configured with 6 REG 503s, then a CCE 504 can be configured with 72 REs. If a downlink control resource set is configured, the corresponding area can be configured with multiple CCE 504s, and a specific downlink control channel can be mapped to one or more CCE 504s and transmitted according to the aggregation level (AL) within the control resource set. CCE 504s within the control resource set are distinguished by numbers, and in this case, the CCE 504 numbers can be given according to a logical mapping scheme.

[0121] exist Figure 5 The basic unit of the downlink control channel shown, namely REG 503, can include the RE mapped to by the DCI and the region mapped to by DMRS 505, which serves as a reference signal for decoding the DCI. For example... Figure 5 As shown, three DMRS505s can be transmitted within a single REG 503. Depending on the aggregation level (AL), the number of CCEs required to transmit the PDCCH can be 1, 2, 4, 8, or 16, and different numbers of CCEs can be used to achieve link adaptation of the downlink control channel. For example, in the case of AL=L, a downlink control channel can be transmitted using L CCEs. The UE should detect the signal without knowing the downlink control channel information, and for blind decoding, a search space representing the set of CCEs is defined. The search space is the set of downlink control channel candidates consisting of CCEs that the UE should attempt to decode at a given aggregation level, and because there are various aggregation levels that form a bundle with 1, 2, 4, 8, or 16 CCEs, the UE can have multiple search spaces. The search space set can be defined as the search space set across all configured aggregation levels.

[0122] The search space can be categorized into a common search space and a UE-specific search space. A specific group of UEs or all UEs can check the common search space of the PDCCH to receive dynamic scheduling of cell common control information, such as paging messages or system information. For example, the PDSCH scheduling allocation information for transmitting SIBs, including cell operator information, can be received by checking the common search space of the PDCCH. In the case of the common search space, since a specific group of UEs or all UEs should receive the PDCCH, the common search space can be defined as a pre-agreed set of CCEs. UE-specific PDSCH or PUSCH scheduling allocation information can be received by checking the UE-specific search space of the PDCCH. The UE-specific search space can be defined as the UE's identifier and various system parameters.

[0123] In 5G, the parameters of the PDCCH search space can be configured from the base station to the UE using higher-layer signaling (such as SIB, MIB, or RRC signaling). For example, the base station can configure the number of PDCCH candidates for each aggregation level L, the monitoring period of the search space, the monitoring timing in symbol units within the time slot of the search space, the search space type (common search space or UE-specific search space), the combination of DCI format and RNTI to be monitored in the corresponding search space, and the control resource set index used for monitoring the search space, etc. For example, the information in Table 9 can be included.

[0124] Table 9

[0125]

[0126]

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

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

[0129] In the public search space, the following combinations of DCI format and RNTI can be monitored. Of course, this disclosure is not limited to the following examples.

[0130] -DCI format 0_0 / 1_0, where CRC is scrambled using C-RNTI, CS-RNTI, SP-CSI-RNTI, RA-RNTI, TC-RNTI, P-RNTI, and SI-RNTI.

[0131] -DCI format 2_0, where CRC is scrambled via SFI-RNTI.

[0132] -DCI format 2_1, where CRC is scrambled via INT-RNTI

[0133] -DCI format 2_2, where CRC is scrambled using TPC-PUSCH-RNTI and TPC-PUCCH-RNTI.

[0134] -DCI format 2_3, where CRC is scrambled via TPC-SRS-RNTI.

[0135] Within a UE-specific search space, the following combinations of DCI format and RNTI can be monitored. Of course, this disclosure is not limited to the following examples.

[0136] -DCI format 0_0 / 1_0, where CRC is scrambled using C-RNTI, CS-RNTI, and TC-RNTI.

[0137] -DCI format 1_0 / 1_1, where CRC is scrambled using C-RNTI, CS-RNTI, and TC-RNTI.

[0138] The specified RNTI can follow the following definitions and purposes.

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

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

[0141] CS-RNTI (Configured Scheduling RNTI): Uses of semi-statically configured UE-specific PDSCH scheduling

[0142] RA-RNTI (Random Access RNTI): The use of PDSCH scheduling in the random access phase.

[0143] P-RNTI (Paging RNTI): The purpose of PDSCH scheduling for sending paging messages.

[0144] SI-RNTI (System Information RNTI): The purpose of PDSCH scheduling for sending system information.

[0145] INT-RNTI (Interrupt RNTI): Used to notify whether to perform puncturing on the PDSCH.

[0146] TPC-PUSCH-RNTI (Transmit Power Control for PUSCH RNTI): Used to indicate the power adjustment commands of the PUSCH.

[0147] TPC-PUCCH-RNTI (PUCCH RNTI Transmit Power Control): Used to indicate the power adjustment commands of the PUCCH.

[0148] TPC-SRS-RNTI (Transmit Power Control of SRS RNTI): Used to indicate the power adjustment commands of the SRS.

[0149] The DCI format specified above can follow a definition similar to the example in Table 10.

[0150] Table 10

[0151]

[0152] In 5G, the search space of the aggregation level L in the search space set s and the control resource set p can be represented by the following equation 1.

[0153] [Equation 1]

[0154]

[0155] - L: Aggregation Level

[0156] - Carrier index

[0157] - : Control the total number of CCEs existing in resource set p

[0158] - Time slot index

[0159] - Number of PDCCH candidates at aggregation level L

[0160] - = 0,..., -1: Index of PDCCH candidates at aggregation level L

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

[0162] - , For , For , For , D=65537.

[0163] - UE identifier

[0164] In the context of public search spaces, The value can correspond to 0.

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

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

[0167] Figure 6 This is a diagram used to explain a method for a base station and a UE to transmit and receive data in a wireless communication system, taking into account downlink data channel and rate matching resources, according to embodiments of the present disclosure.

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

[0169] The base station can dynamically notify the UE via DCI whether to perform rate matching on the data channels in the configured rate matching resource portion through additional configuration (this corresponds to the "rate matching indicator" in the DCI format mentioned above). Specifically, the base station can select a portion of packets from the configured rate matching resources into rate matching resource groups, and can use a bitmap method via DCI to indicate to the UE whether the data channels in each rate matching resource group have been rate matched. For example, when four rate matching resources RMR#1, RMR#2, RMR#3, and RMR#4 are configured, the base station can configure RMG #1 = {RMR #1, RMR #2} and RMG #2 = {RMR #3, RMR #4} as rate matching groups, and can use 2 bits in the DCI field as a bitmap to indicate to the UE whether rate matching is performed in each of RMG#1 and RMG#2. For example, indicating "1" if rate matching should be performed, and indicating "0" if rate matching should not be performed.

[0170] In 5G, as a method for configuring the aforementioned rate matching resources in the UE, both "RB symbol level" and "RE level" granularity are supported. More specifically, the following configuration method is followed.

[0171] RB symbol level

[0172] The UE can configure up to four RateMatchPatterns for each bandwidth segment via higher-layer signaling, and a RateMatchPattern can include the following.

[0173] - Reserved resources within a bandwidth portion can include resources in which the time and frequency resource regions of the respective reserved resources are configured through a combination of bitmaps at the RB level and bitmaps at the symbol level on the frequency axis. Reserved resources can span one or two time slots. A time-domain pattern (periodicityAndPattern) can also be configured, in which the time and frequency domains are repeated by each pair of bitmaps at the RB level and symbol level.

[0174] - May include resource regions corresponding to time-domain and frequency-domain resource regions of the control resource set configured within the bandwidth portion, and time-domain patterns configured to repeat the search space configuration of the corresponding resource regions.

[0175] RE Level

[0176] The UE can configure the following via higher-level signaling.

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

[0178] - This may include configuration information for resource sets corresponding to one or more ZP (Zero Power) CSI-RS within the bandwidth portion.

[0179] [PDSCH: Frequency Resource Allocation Related]

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

[0181] Figure 7 This diagram illustrates three frequency domain resource allocation methods in an NR wireless communication system: Type 0 7-00, Type 1 7-05, and Dynamic Switching 7-10, all configured by higher layers.

[0182] refer to Figure 7 When the UE is configured to use only resource types 0-7-00 via higher-layer signaling, some downlink control information (DCI) allocated to the corresponding UE for PDSCH includes a bitmap consisting of NRBG bits. The conditions for this situation will be described again later. In this case, NRBG refers to multiple resource block groups (RBGs) determined according to the BWP size allocated by the BWP indicator and the higher-layer parameter rbg-Size, as shown in Table 11 below, and data is sent to the RBG with the bitmap indicator set to 1.

[0183] Table 11

[0184]

[0185] If the UE is configured to use only resource type 1 7-05 via higher-layer signaling, then some DCIs allocated to the corresponding UE for PDSCH include those from... Frequency domain resource allocation information consisting of bits. The conditions for this situation will be described again later. The base station can use this configuration to start VRB 7-20 and the length of the frequency domain resources continuously allocated from it 7-25.

[0186] If the UE is configured to use both resource type 0 and resource type 1 (7-10) via higher-layer signaling, some DCIs allocating PDSCH to the corresponding UE include frequency domain resource allocation information consisting of bits 7-15 for configuring the payload of resource type 0 and bits 7-20 and 7-35, which are the larger of these two values. The conditions for this situation will be described again later. In this case, a bit can be added to the first part (MSB) of the frequency domain resource allocation information within the DCI; a value of "0" indicates the use of resource type 0, and a value of "1" indicates the use of resource type 1.

[0187] [PDSCH / PUSCH: Related to Time Resource Allocation]

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

[0189] The base station can configure time-domain resource allocation information tables for the UE for the Physical Downlink Shared Channel (PDSCH) and Physical Uplink Shared Channel (PUSCH) via higher-layer signaling (e.g., RRC signaling). For PDSCH, a table consisting of up to maxNrofDL-Allocations = 16 entries can be configured, and for PUSCH, a table consisting of up to maxNrofUL-Allocations = 16 entries can be configured. In an embodiment, time-domain resource allocation information may include PDCCH to PDSCH time slot timing (the time interval in units of time slots, denoted as K0, between the time point when the PDCCH is received and the time point when the PDSCH scheduled by the received PDCCH is transmitted), PDCCH to PUSCH time slot timing (the time interval in units of time slots, denoted as K2, between the time point when the PDCCH is received and the time point when the PUSCH scheduled by the received PDCCH is transmitted), information on the position and length of the start symbol of the PDSCH or PUSCH scheduled within the time slot, the mapping type of the PDSCH or PUSCH, etc. For example, information such as [Table 12] or [Table 13] below can be sent from the base station to the UE.

[0190] Table 12

[0191]

[0192] Table 13

[0193]

[0194] The base station can notify the UE of one of the entries in the aforementioned time domain resource allocation information table via L1 signaling (e.g., DCI) (e.g., indicated by the "time domain resource allocation" field within the DCI). The UE can obtain the time domain resource allocation information for the PDSCH or PUSCH based on the DCI received from the base station.

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

[0196] refer to Figure 8 The base station can determine the subcarrier spacing (SCS) of the data and control channels based on the configuration of the higher layers. μ PDSCH μ PDCCH The time-domain location of the PDSCH resource is indicated by the scheduling offset (K0) value and the OFDM symbol start position 8-00 and length 8-05 within a time slot 8-10 dynamically indicated by DCI.

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

[0198] refer to Figure 9 The subcarrier spacing is the same in the data channel and the control channel. μ PDSCH = μ PDCCH In the case of 9-00, since the data and control time slot numbers are the same, the base station and UE can generate a scheduling offset based on the predetermined time slot offset K0. On the other hand, when the subcarrier spacing of the data channel and the control channel is different ( μ PDSCH ≠ μ PDCCH In the case of 9-05, since the time slot numbers for data and control are different, the base station and UE can generate a scheduling offset based on the predetermined time slot offset K0 of the subcarrier interval based on PDCCH.

[0199] [PUSCH: Sending Method Related]

[0200] Next, the scheduling method for PUSCH transmission is described. PUSCH transmission can be dynamically scheduled by UL authorization within the DCI, or it can be operated through the configured authorization type 1 or type 2. The dynamic scheduling indication for PUSCH transmission may be DCI format 0_0 or 0_1.

[0201] Configuration type 1 PUSCH transmissions can be semi-statically configured via higher-layer signaling by receiving configuredGrantConfig (including rrc-ConfiguredUplinkGrant in [Table 14]) without receiving UL authorization within the DCI. Configuration type 2 PUSCH transmissions can be semi-persistently scheduled by UL authorization within the DCI after receiving configuredGrantConfig (excluding rrc-ConfiguredUplinkGrant in [Table 14]) via higher-layer signaling. When PUSCH transmissions operate with configured authorizations, the parameters applied to the PUSCH transmissions are applied via configuredGrantConfig (which is higher-layer signaling in [Table 14]), except for dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, and scaling provided as UCI-OnPUSCH in pusch-Config (which is higher-layer signaling in [Table 15]). If the UE provides a transformPrecoder in configuredGrantConfig (which is the higher-layer signaling in [Table 14]), then the UE is given tp-pi2BPSK in pusch-Config in [Table 15] for sending PUSCH with the configured grant.

[0202] Table 14

[0203]

[0204] Next, the PUSCH transmission method is described. The DMRS antenna port used for PUSCH transmission is the same as the antenna port used for SRS transmission. Depending on whether the value of txConfig in the pusch-Config (which is higher-layer signaling) in [Table 15] is "codebook" or "nonCodebook", PUSCH transmission can follow either a codebook-based transmission method or a non-codebook-based transmission method.

[0205] As described above, PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1, and can be semi-statically configured via configured authorization. If the UE is instructed to schedule PUSCH transmission via DCI format 0_0, the UE uses the pucch-spatialRelationInfoID corresponding to the UE-specific PUCCH resource, which corresponds to the smallest ID within the active uplink BWP in the serving cell, and in this case, PUSCH transmission is based on a single antenna port. The UE does not expect PUSCH transmission to be scheduled via DCI format 0_0 within BWPs where PUCCH resources including pucch-spatialRelationInfo are not configured. If the UE has not configured txConfig in the pusch-Config in [Table 15], the UE does not expect to use DCI format 0_1 ​​for scheduling.

[0206] Table 15

[0207]

[0208] Next, codebook-based PUSCH transmission is described. Codebook-based PUSCH transmission can be dynamically scheduled using DCI format 0_0 or 0_1, and can be semi-statically configured with configured grants. If codebook-based PUSCH is dynamically scheduled using DCI format 0_1, or semi-statically configured with configured grants, the UE determines the precoder for PUSCH transmission based on the SRS Resource Indicator (SRI), the Transmit Precoding Matrix Indicator (TPMI), and the transmission rank (the number of PUSCH transmission layers).

[0209] In this scenario, the SRI can be provided via the SRS Resource Indicator field within the DCI, or configured via the higher-layer signaling srs-ResourceIndicator. The UE is configured with at least one SRS resource during codebook-based PUSCH transmission, and can be configured with up to two. When providing the SRI to the UE via the DCI, the SRS resource indicated by the corresponding SRI refers to the SRS resource corresponding to the SRI among those transmitted prior to the PDCCH including the corresponding SRI. Furthermore, the TPMI and transport rank can be provided via the precoding information and layer number fields within the DCI, or configured via the higher-layer signaling precodingAndNumberOfLayers. The TPMI is used to indicate the precoder applied to PUSCH transmission. If the UE is configured with one SRS resource, the TPMI indicates the precoder to be applied to that configured SRS resource. If the UE is configured with multiple SRS resources, the TPMI indicates the precoder to be applied to the SRS resources indicated by the SRI.

[0210] The precoder used for PUSCH transmission is selected from the uplink codebook, which has the same number of antenna ports as the nrofSRS-Ports value in the higher-layer signaling SRS-ConFIG. In codebook-based PUSCH transmission, the UE determines a subset of the codebook based on TPMI and the codebookSubset in the higher-layer signaling pusch-ConFIG. Based on the UE capabilities reported to the base station, the codebookSubset in the higher-layer signaling pusch-Config can be configured as one of "fullyAndPartialAndNonCoherent", "partialAndNonCoherent", or "nonCoherent". If the UE reports "partialAndNonCoherent" as a UE capability, the UE does not expect the higher-layer signaling codebookSubset to be configured as "fullyAndPartialAndNonCoherent". Furthermore, if the UE reports "nonCoherent" as a UE capability, the UE does not expect the value of the higher-layer signaling codebookSubset to be configured as "fullyAndPartialAndNonCoherent" or "partialAndNonCoherent". When nrofSRS-Ports in the higher-layer signaling SRS-ResourceSet points to two SRS antenna ports, the UE does not expect the value of the higher-layer signaling codebookSubset to be configured as "partialAndNonCoherent".

[0211] A UE can be configured with an SRS resource set, where the purpose value in the higher-layer signaling SRS-ResourceSet is configured as "codebook", and an SRS resource can be indicated via the SRI in the corresponding SRS resource set. If multiple SRS resources are configured within an SRS resource set, and the purpose value in the higher-layer signaling SRS-ResourceSet is configured as "codebook", the UE expects the value of nrofSRS-Ports in the higher-layer signaling SRS-Resource to be configured to the same value for all SRS resources.

[0212] The UE transmits one or more SRS resources, whose usage value is configured as "codebook," to the base station according to higher-layer signaling. The base station selects an SRS resource from the SRS resources transmitted by the UE and instructs the UE to perform PUSCH transmission using the transmission beam information of the corresponding SRS resource. In this codebook-based PUSCH transmission, the SRI is used as an index for selecting an SRS resource and is included in the DCI. Furthermore, the base station includes information in the DCI indicating the TPMI and rank used by the UE for PUSCH transmission. The UE performs PUSCH transmission by using the SRS resource indicated by the SRI, based on the transmission beam of the corresponding SRS resource, and applying the rank and precoder indicated by the TPMI.

[0213] Next, non-codebook-based PUSCH transmission is described. Non-codebook-based PUSCH transmission can be dynamically scheduled using DCI format 0_0 or 0_1, and can be semi-statically operated using configured authorization. When at least one SRS resource is configured within an SRS resource set whose usage value in the higher-layer signaling SRS-ResourceSet is configured as "nonCodebook", the UE can schedule non-codebook-based PUSCH transmission using DCI format 0_1.

[0214] For an SRS resource set in which the usage value in the higher-layer signaling SRS-ResourceSet is configured as "nonCodebook", the UE can be configured with an associated NZP CSI-RS resource (non-zero power CSI-RS). The UE can perform precoder calculations for SRS transmission by measuring the NZP CSI-RS resource associated with the SRS resource set. If the difference between the last received symbol of the aperiodic NZP CSI-RS resource associated with the SRS resource set and the first symbol of the aperiodic SRS transmission in the UE is less than 42 symbols, the UE does not expect the precoder information for SRS transmission to be updated.

[0215] If the resourceType value in the higher-layer signaling SRS-ResourceSet is configured as "aperiodic", the associated NZP CSI-RS is indicated by an SRS request, which is a field in DCI format 0_1 ​​or 1_1. In this case, if the associated NZP CSI-RS resource is an aperiodic NZP CSI-RS resource, the presence of the associated NZP CSI-RS is indicated if the value of the SRS request field in DCI format 0_1 ​​or 1_1 is not "00". In this case, the corresponding DCI should not indicate cross-carrier or cross-BWP scheduling. Furthermore, if the SRS request value indicates the presence of an NZPCSI-RS, the corresponding NZP CSI-RS is located in the time slot where the PDCCH including the SRS request field is transmitted. In this case, the TCI state configured in the scheduled subcarrier is not configured as QCL-TypeD.

[0216] If a periodic or semi-persistent SRS resource set is configured, the associated NZP CSI-RS can be indicated by the associated CSI-RS in the higher-layer signaling SRS-ResourceSet. For non-codebook-based transmissions, the UE does not expect the spatialRelationInfo of the higher-layer signaling as an SRS resource and the associated CSI-RS in the higher-layer signaling SRS-ResourceSet to be configured together.

[0217] When a UE is configured with multiple SRS resources, the UE can determine the precoder and transmission rank to be applied to PUSCH transmission based on the SRI indicated by the base station. In this case, the SRI is indicated by the SRS Resource Indicator field within the DCI, or configured via the higher-layer signaling srs-ResourceIndicator. Similar to the codebook-based PUSCH transmission described above, when the UE is provided with an SRI via the DCI, the SRS resource indicated by the corresponding SRI refers to the SRS resource corresponding to the SRI among the SRS resources transmitted before the PDCCH including the corresponding SRI. The UE can use one or more SRS resources for SRS transmission, and the maximum number of SRS resources within an SRS resource set and the maximum number of SRS resources that can be transmitted simultaneously in the same symbol are determined by the UE capabilities reported by the UE to the base station. In this case, the SRS resources transmitted simultaneously by the UE occupy the same RB. The UE configures one SRS port for each SRS resource. Only one SRS resource set can be configured, where the usage value in the higher-layer signaling SRS-ResourceSet is configured as "nonCodebook", and a maximum of four SRS resources can be configured for non-codebook-based PUSCH transmission.

[0218] The base station sends an NZP-CSI-RS associated with an SRS resource set to the UE, and the UE calculates the precoder to be used when transmitting one or more SRS resources within the corresponding SRS resource set based on measurements taken upon receiving the corresponding NZP-CSI-RS. The UE applies the calculated precoder when transmitting one or more SRS resources within an SRS resource set whose purpose is configured as "nonCodebook," and the base station selects one or more SRS resources from the received SRS resources. In this case, in nonCodebook-based PUSCH transmission, the SRI represents an index that can represent a combination of one or more SRS resources, and the SRI is included within the DCI. In this case, 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 UE transmits the PUSCH by applying the precoder used for SRS resource transmission to each layer.

[0219] [CA / DC related]

[0220] Figure 10 This is a diagram illustrating the radio protocol structure of a gNB and a UE in single-cell, carrier aggregation, and dual-connectivity scenarios according to embodiments of the present disclosure.

[0221] refer to Figure 10 The radio protocols of the next-generation mobile communication system consist of NR Service Data Adaptation Protocol (SDAP) S25 and S70, NR Packet Data Convergence Protocol (PDCP) S30 and S65, NR Radio Link Control (RLC) S35 and S60, and NR Media Access Control (MAC) S40 and S55 in the UE and NR gNB, respectively.

[0222] The main functions of NR SDAP S25 and S70 may include some of the following functions.

[0223] - User plane data transfer function (transfer of user plane data)

[0224] - Mapping function between uplink and downlink QoS flows and data bearers (mapping between QoS flows and DRBs for DL ​​and UL)

[0225] - QoS flow ID tagging function in uplink and downlink (tag QoS flow ID in DL and UL packets)

[0226] - The function of mapping reflected QoS flows to uplink SDAP PDU data bearers (UL SDAP PDU mapping from reflected QoS flows to DRB).

[0227] For SDAP layer entities, the UE can be configured via RRC messages to determine whether to use the SDAP layer entity header or the functionality of the SDAP layer entity for each PDCP layer entity, each bearer, or each logical channel. When the SDAP header is configured, the NAS reflection QoS configuration 1-bit indicator and the AS reflection QoS configuration 1-bit indicator in the SDAP header can instruct the UE to update or reconfigure the uplink and downlink QoS flow and data bearer mapping information. The SDAP header may include QoS flow ID information representing QoS. QoS information can be used for data processing priorities, scheduling information, etc., to support smooth service.

[0228] The main functions of NR PDCP S30 and S65 may include some of the following functions.

[0229] - Header compression and decompression functions (Header compression and decompression: ROHC only)

[0230] - User data transfer function (user data transfer)

[0231] - Sequential delivery function (sequential delivery of upper-layer PDUs)

[0232] - Out-of-order delivery function (out-of-order delivery of upper-layer PDUs)

[0233] - Reordering function (reordering received PDCP PDUs)

[0234] - Duplicate detection function (duplicate detection of lower-level SDUs)

[0235] - Retransmission function (PDCP SDU retransmission)

[0236] - Encryption and decryption functions (encryption and decryption)

[0237] - Timer-based SDU dropping function (timer-based SDU dropping in the uplink).

[0238] In the preceding text, the reordering function of the NR PDCP entity refers to the function of reordering PDCP PDUs received from the lower layer in sequence based on the PDCP sequence number (SN), and may include the function of delivering data to the upper layer in the reordered order. Alternatively, the reordering function of the NR PDCP entity may include the function of immediate delivery regardless of order, the function of recording lost PDCP PDUs by reordering the order, the function of reporting the status of lost PDCP PDUs to the sending side, and the function of requesting retransmission of lost PDCP PDUs.

[0239] The main functions of NR RLC S35 and S60 may include some of the following functions.

[0240] - Data transmission function (transmission of upper-layer PDUs)

[0241] - Sequential delivery function (sequential delivery of upper-layer PDUs)

[0242] - Out-of-order delivery function (out-of-order delivery of upper-layer PDUs)

[0243] - ARQ functionality (error correction via ARQ)

[0244] - Cascading, segmentation, and reassembly functions (cascading, segmentation, and reassembly of RLC SDU)

[0245] - Resegmentation function (resegmentation of RLC data PDUs)

[0246] - Reordering function (reordering RLC data PDUs)

[0247] - Duplicate detection function (duplicate detection)

[0248] - Error detection function (protocol error detection)

[0249] - RLC SDU discard function (RLC SDU discard)

[0250] - RLC Reconstruction Function (RLC Reconstruction)

[0251] In the above text, the sequential delivery function of an NR RLC entity refers to the function of delivering RLC SDUs received from the lower layer to the upper layer in sequence. The sequential delivery function of an NR RLC entity may include the function of reassembling and delivering an original RLC SDU when it is received by being divided into several RLC SDUs; the function of reordering received RLC PDUs based on the RLC sequence number (SN) or PDCP sequence number (SN); the function of recording lost RLC PDUs by reordering them; the function of reporting the status of lost RLC PDUs to the transmitting side; and the function of requesting retransmission of lost RLC PDUs. The sequential delivery function of an NR RLC entity may include the function of delivering only RLC SDUs to the upper layer in sequence in the presence of lost RLC SDUs, or the function of delivering all RLCSDUs received before the timer starts in sequence to the upper layer even if lost RLC SDUs exist, if a predetermined timer expires. Alternatively, even in the event of lost RLC SDUs, the sequential delivery function of the NR RLC entity can include the ability to sequentially deliver all RLC SDUs received to date to the upper layer if the scheduled timer expires. Furthermore, as described above, RLC PDUs can be processed in the order of receipt (regardless of sequence number order, but in the order of arrival) and delivered to the PDCP entity regardless of the order (out-of-order delivery). In the case of fragmentation, segments stored in a buffer or received later can be received and reconstructed into a complete RLC PDU, then processed and delivered to the PDCP entity. The NR RLC layer may not include cascading functionality, and the corresponding functionality can be implemented in the NR MAC layer or replaced by multiplexing functions of the NRMAC layer.

[0252] In the above text, the out-of-order delivery function of NR RLC entities refers to the function of immediately transmitting RLC SDUs received from the lower layer to the upper layer regardless of the order, and may include the function of reassembling and delivering an original RLC SDU when it is received by segmenting it into several RLC SDUs, and may include the function of storing the RLC-SN or PDCP SN of the received RLC PDUs and recording the lost RLC PDUs by aligning the order.

[0253] NR MAC S40 and S55 can connect to several NR RLC layer entities configured in a UE, and the main functions of NR MAC can include some of the following functions.

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

[0255] - Multiplexing and demultiplexing functions (MAC SDU multiplexing / demultiplexing)

[0256] - Scheduling information reporting function (Scheduling Information Report)

[0257] - HARQ functionality (error correction via HARQ)

[0258] - Priority handling function between logical channels (priority handling between logical channels of a UE)

[0259] - Priority processing function between UEs (priority processing is performed between UEs through dynamic scheduling)

[0260] - MBMS service identification function (MBMS service identification)

[0261] - Transmission format selection function (Transmission format selection)

[0262] - Fill function (Fill)

[0263] The NR PHY layers S45 and S50 can perform channel decoding and modulation of upper-layer data, convert upper-layer data into OFDM symbols and send OFDM symbols to the radio channel, or demodulate and channel decode OFDM symbols received through the radio channel and deliver them to the upper layer.

[0264] The radio protocol structure can be modified in various ways in detail depending on the carrier (or cell) operation scheme. For example, when the gNB transmits data to the UE based on a single carrier (or cell), the gNB and UE use a protocol structure with a single structure at each layer, as shown in S00. On the other hand, when the gNB uses multiple carriers in a single TRP to transmit data to the UE based on carrier aggregation (CA), the gNB and UE use a protocol structure with a single structure up to RLC, but multiplex the PHY layer through the MAC layer, as shown in S10. As another example, when the gNB uses multiple carriers in multiple TRPs to transmit data to the UE based on dual connectivity (DC), the gNB and UE use a protocol structure with a single structure up to RLC, but multiplex the PHY layer through the MAC layer, as shown in S20.

[0265] Referring to the above description related to PDCCH and beam configuration, current Rel-15 and Rel-16 NR do not support PDCCH retransmission, making it difficult to achieve the required reliability in scenarios requiring high reliability (such as URLLC). This invention provides a PDCCH retransmission method via multiple Transmitting Points (TRPs) to improve the reliability of UE PDCCH reception. Specific methods are described in detail in the following embodiments.

[0266] In the following, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The content of this disclosure applies to FDD and TDD systems. In the present disclosure, higher-layer signaling is a signal delivery method that uses the downlink data channel of the physical layer to deliver signals from the gNB to the UE, or uses the uplink data channel of the physical layer to deliver signals from the UE to the gNB, and may also be referred to as RRC signaling, PDCP signaling, or Media Access Control (MAC) control element (MAC CE).

[0267] In the description of this disclosure below, higher-level signaling may be signaling corresponding to a combination of at least one or more of the following signaling.

[0268] -MIB (Master Information Block)

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

[0270] -RRC (Radio Resource Control)

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

[0272] In addition, L1 signaling can be signaling corresponding to at least one or a combination of one or more of the following signaling methods that use physical layer channels or signaling.

[0273] -PDCCH (Physical Downlink Control Channel)

[0274] -DCI (Downlink Control Information)

[0275] -UE-specific DCI

[0276] -Public DCI Group

[0277] -Public DCI

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

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

[0280] -PUCCH (Physical Uplink Control Channel)

[0281] -UCI (Uplink Control Information)

[0282] In the following, in this disclosure, the determination of priority between A and B may be referred to in various ways, such as performing an operation corresponding to the operation with higher priority according to a predetermined priority rule, or omitting (deleting) operations with lower priority.

[0283] In this disclosure below, the above examples are described by way of multiple embodiments, but these embodiments are not independent and one or more embodiments may be applied simultaneously or in combination.

[0284] [Random Access Procedure in SBFD]

[0285] Meanwhile, 3GPP introduced Subband Non-Overlapping Full-Duplex (SBFD) as a new NR-based duplexing scheme. SBFD is a technology that extends the UE's uplink coverage to the same extent as the increased uplink resources by utilizing a portion of downlink resources as uplink resources in TDD bands (spectrums) below or above 6 GHz, and receiving uplink transmissions from the UE via the gNB with the increased uplink resources. Feedback latency is reduced by receiving feedback from the UE in the extended uplink resources. In this disclosure, for convenience, a UE capable of receiving information from the gNB regarding whether SBFD is supported and performing uplink transmissions in a portion of the downlink resources can be referred to as an SBFD UE (a UE supporting SBFD). To define the SBFD scheme in the standard and determine whether an SBFD UE supports SBFD in a specific cell (or frequency, band), the following schemes can be considered.

[0286] Option 1. In addition to the existing frame structure types for unpaired spectrum (or TDD) or paired spectrum (or FDD), another frame structure type (e.g., frame structure type 2) can be introduced to define the aforementioned SBFD. Frame structure type 2 can be defined as being supported in a specific frequency or band, or the gNB can indicate to the UE whether SBFD is supported as system information. The UE can determine whether SBFD is supported in a specific cell (or frequency, band) by receiving system information including whether SBFD is supported.

[0287] The second approach involves instructing the UE whether SBFD is additionally supported in a specific frequency or band of existing unpaired spectrum (or TDD) without defining a new frame structure type. In this approach, it's possible to define whether SBFD is additionally supported in a specific frequency or band of existing unpaired spectrum, or the gNB can instruct the UE whether SBFD is supported as system information. The UE can determine whether SBFD is supported in a specific cell (or frequency, band) by receiving system information including whether SBFD is supported.

[0288] In both the first and second schemes, the information regarding whether SBFD is supported can be obtained by configuring an additional portion of downlink resources as uplink resources, in addition to the TDD UL (uplink)-DL (downlink) resource configuration information (indicating the downlink slot (or symbol) resources and uplink slot (or symbol) resources of TDD) configuration (e.g., as described later). Figure 12 The SBFD resource configuration information in the document can indirectly indicate whether SBFD is supported, or it can be information that directly indicates whether SBFD is supported.

[0289] In this disclosure, an SBFD UE can acquire cell synchronization by receiving a synchronization signal block during initial cell access for accessing the cell (or gNB). The process for acquiring cell synchronization can be the same for both SBFD UEs and existing TDD UEs. Subsequently, the SBFD UE can determine whether the cell supports SBFD through MIB acquisition, SIB acquisition, or a random access procedure.

[0290] The system information used to send information about whether SBFD is supported can be system information sent separately from the system information of UEs within the cell that support different versions of the standard (e.g., existing TDD UEs). An SBFD UE can determine whether it supports SBFD by obtaining all or part of the system information of an existing TDD UE, as well as the separately sent system information. If the SBFD UE only obtains the system information of an existing TDD UE, or obtains system information that does not support SBFD, the SBFD UE can determine that the cell (or gNB) only supports TDD.

[0291] When the system information of a UE supporting different versions of the standard (e.g., an existing TDD UE) includes information on whether it supports SBFD, this information can be inserted last to avoid affecting the acquisition of system information by the existing TDD UE. If the SBFD UE fails to obtain the last inserted information on whether it supports SBFD, or obtains information indicating that it does not support SBFD, the SBFD UE can determine that the cell (or gNB) only supports TDD.

[0292] Alternatively, if the system information of a UE supporting different versions of the standard (e.g., an existing TDD UE) includes information about whether SBFD is supported, this information can be transmitted via a separate PDSCH to avoid affecting the acquisition of system information by the existing TDD UE. That is, a UE that does not support SBFD can receive a first SIB (or SIB1) including existing TDD-related system information in the first PDSCH. A UE that supports SBFD can receive a first SIB (or SIB1) including existing TDD-related system information in the first PDSCH, and a second SIB including SBFD-related system information in the second PDSCH. Here, the first PDSCH and the second PDSCH can be scheduled by the first PDCCH and the second PDCCH, and the cyclic redundancy code (CRC) of the first PDCCH and the second PDCCH can be scrambled 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 the search space is not obtained (i.e., if the system information in the first PDSCH does not include information for the search space), the UE can receive the second PDCCH in the same search space as the first PDCCH.

[0293] As described above, if the SBFD UE determines that the cell (or gNB) only supports TDD, the SBFD UE can perform the random access procedure and transmit and receive data / control signals in the same way as existing TDD UEs.

[0294] The gNB configures separate random access resources for each of the existing TDD UEs and SBFD UEs (e.g., SBFD UEs supporting full-duplex communication and SBFD UEs supporting half-duplex communication), and can send configuration information for the random access resources (representing configuration information or control information for time-frequency resources available for PRACH) to the SBFD UEs via system information. The system information used to send the random access resource information can be sent separately, which is different from the system information for UEs within the cell that support different versions of the standard (e.g., existing TDD UEs).

[0295] The gNB configures random access resources for the TDD UE and can also configure separate random access resources for the SBFD UE. Here, the SBFD UE can use the random access resources of the TDD UE, while the SBFD UE may not be able to use the random access resources of the TDD UE. In the latter case, the SBFD UE can always use only the separate random access resources designated for the SBFD UE.

[0296] Whether an SBFD UE can use the random access resources for a TDD UE can be indicated from the gNB. This can be indicated by including it in the SIB. That is, a separate random access resource for the SBFD UE can be configured in the SIB, and along with the configuration, the availability of the random access resources for the TDD UE can be indicated. This can be represented by a 1-bit. If the 1-bit is "0" (or FALSE), the SBFD UE cannot use the random access resources for the TDD UE. If the 1-bit is "1" (or TRUE), the SBFD UE can use the random access resources for the TDD UE.

[0297] The gNB can determine the type of UE attempting to access a cell based on the random access resources used by the UE. For example, an SBFD UE can send a PRACH using a separate random access resource for SBFD UEs, and the gNB can determine that the SBFD UE is attempting cell access upon receiving the PRACH. Similarly, a TDD UE can send a PRACH using random access resources for TDD UEs, and the gNB can determine that the TDD UE is attempting cell access upon receiving the PRACH. For reference, if an SBFD UE is allowed to send a PRACH using the random access resources for TDD UEs, the gNB may not explicitly state whether the UE sending the PRACH is a TDD UE or an SBFD UE. In this case, the gNB can always assume that the UE is a TDD UE.

[0298] When the gNB determines that the UE is an SBFD UE, when scheduling messages 2 (Msg2), 3 (Msg3), and 4 (Msg4) for the UE, the gNB can perform scheduling based on the uplink subband configuration. That is, when the gNB schedules the reception of Msg2 and Msg4 for the UE, the gNB can schedule them so that Msg2 and Msg4 are not received in the uplink subband (when the UE receives a PDSCH including Msg2 and Msg4, it performs PDSCH reception in frequency resources other than the uplink subband). When the gNB schedules Msg3 PUSCH for the UE, the gNB can schedule it so that Msg3 PUSCH is transmitted within the uplink subband.

[0299] When the gNB determines that the UE is a TDD UE, it cannot use the uplink subband configuration when scheduling Msg2, Msg3, and Msg4 for the UE. In other words, even if the uplink subband is configured in the downlink symbol or flexible symbol, the gNB can assume that the UE cannot obtain the uplink subband configuration information. When the gNB schedules Msg3 PUSCH for the UE, it can schedule Msg3 PUSCH in either the flexible symbol or the uplink symbol. In other words, Msg3 PUSCH cannot be scheduled in the uplink subband.

[0300] Alternatively, the gNB can configure common random access resources for all UEs within the cell without configuring separate random access resources for SBFD UEs. In this case, the configuration information for the random access resources can be sent to all UEs within the cell via system information, and the SBFD UE receiving the system information can perform random access within the aforementioned random access resources. Afterward, the SBFD UE can complete the random access procedure and enter RRC connection mode for sending and receiving data with the cell. Following RRC connection mode, the SBFD UE can receive higher-layer signals or physical signals from the gNB, from which the UE can determine that some frequency resources in the downlink time resources have been configured as uplink resources and perform SBFD operations, such as sending uplink signals within the uplink resources.

[0301] If an SBFD UE determines that the cell supports SBFD, it can notify the gNB that the UE attempting to access the network is an SBFD UE by sending capability information to the gNB. This capability information includes at least one or more of the following: whether the UE supports SBFD, whether it supports full-duplex or half-duplex communication, and the number of transmit or receive antennas it is equipped with (or supports). Alternatively, if half-duplex communication support is the basic implementation for an SBFD UE, the support for half-duplex communication can be omitted from the capability information. The SBFD UE can report the capability information to the gNB through the random access procedure, after completing the random access procedure, or after entering RRC connection mode to send and receive data with the cell.

[0302] SBFD UEs can support half-duplex communication, performing only uplink transmission or downlink reception at any given time, similar to existing TDD UEs, or they can support full-duplex communication, performing both uplink transmission and downlink reception at any given time. Therefore, SBFD UEs can report their support for half-duplex or full-duplex communication to the gNB via a capability report. Following the report, the gNB can configure the SBFD UE to use either half-duplex or full-duplex communication for transmission and reception. When an SBFD UE reports its half-duplex communication capability to the gNB, since a duplexer is typically absent, a handover gap for changing the RF between transmission and reception may be necessary in FDD or TDD operations.

[0303] Typically, a UE establishes a radio link with the network through a random access procedure, based on synchronization with the network and system information acquired during cell search. Random access can use contention-based or contention-free schemes. During the initial access phase of a cell, when the UE performs cell selection and reselection, such as moving from RRC_IDLE to RRC_CONNECTED, a contention-based random access scheme can be used. Contention-free random access can be used to reconfigure uplink synchronization when downlink data has arrived, during handover, or in the case of location measurement.

[0304] Figure 11 A random access procedure in a wireless communication system according to an embodiment of the present disclosure is illustrated.

[0305] refer to Figure 11 This illustrates a competition-based random access process as an example. Furthermore, although... Figure 11Although not shown in the diagram, the gNB can transmit synchronization signal blocks as described in the above embodiments. In this case, the gNB can periodically transmit synchronization signal blocks using beam scanning. For example, the gNB can use up to 64 different beams within 5 ms to transmit synchronization signal blocks including PSS / SSS (synchronization signals) and PBCH (broadcast channel) signals, and can transmit multiple synchronization signal blocks using different beams. The UE detects (selects) a synchronization signal block with the optimal beam direction (e.g., the beam direction with the strongest received signal strength or greater than a predetermined threshold), and can use the Physical Random Access Channel (PRACH) resources associated with the detected synchronization signal block to transmit a preamble. For example, as the first step 1101 of the random access procedure, the UE can send a random access preamble (or message 1) to the gNB. Upon receiving the random access preamble, the gNB can measure the transmission delay value between the UE and the gNB and align the uplink synchronization. Specifically, the UE can send a random access preamble randomly selected from the set of random access preambles given in advance in the system information. Furthermore, the initial transmit power of the random access preamble can be determined based on the path loss between the gNB and the UE measured by the UE. Additionally, the UE can determine the transmit beam direction (or transmit beam or beam) of the random access preamble based on the synchronization signal block received from the gNB, and transmit the random access preamble by applying the determined transmit beam direction.

[0306] In the second step 1102, the gNB may send a response (Random Access Response (RAR) or Message 2 (Msg2)) to the UE in response to the detected random access attempt. The gNB may send an uplink transmission timing control command to the UE based on a transmission delay value measured according to the random access preamble received in the first step 1101. Furthermore, the gNB may send uplink resource and power control commands as scheduling information for the UE. This scheduling information may include control information for the uplink transmission beam for the UE. The RAR is transmitted via the PDSCH and may include at least one of the following:

[0307] - Index of the random access preamble sequence detected by the network (or gNB),

[0308] -TC-RNTI (Temporary Cell Radio Network Temporary Identifier).

[0309] -Uplink scheduling authorization, or

[0310] - Timing advance value.

[0311] If, in the second step 1102, the UE does not receive the RAR (message information 3, Msg3) from the gNB within a predetermined time, the UE can proceed to the first step 1101 again. If the first step is performed again, the UE increases the transmission power of the random access preamble by a predetermined step size and transmits the random access preamble (this is called a power ramp), thereby increasing the probability of receiving the random access preamble from the gNB.

[0312] In step 1103, the UE can use the uplink resources allocated in step 1102 to transmit uplink information (scheduled transmission or message 3) via an uplink data channel (Physical Uplink Shared Channel (PUSCH)), including its UE identifier (which may be referred to as the UE contention resolution identifier) ​​(or, if the UE already has a valid UE identifier (C-RNTI) in the cell before the random access procedure is initiated, a valid UE identifier). The PUSCH may be referred to as message 3 PUSCH (Msg3 PUSCH). The transmission timing of the uplink data channel used to transmit message 3 may follow the uplink transmission timing control command received from the gNB in ​​step 1102. Furthermore, the transmission power of the uplink data channel used to transmit message 3 can be determined by considering the power control command received from the gNB in ​​step 1102 and the power ramp value of the random access preamble. The uplink data channel used to transmit message 3 may be the first uplink data signal transmitted by the UE to the gNB after the transmission of the UE's random access preamble.

[0313] In step 1104, if the gNB determines that the UE performed random access without conflict with other UEs, the gNB may send a message (contention resolution message (CR message) or message 4) to the corresponding UE. This message includes the identifier of the UE that sent uplink data in step 1103. In this regard, if multiple UEs receive the same TC-RNTI in step 1102, in step 1103, each of the multiple UEs that received the same TC-RNTI includes its own UE identifier (UE contention resolution identifier) ​​in message 3 and sends message 3 to the gNB. The gNB may then send message 4 (CR message), which includes one of the UE identifiers among the multiple UEs, for contention resolution. When the UE receives message 4 (CR message) including its UE identifier from the gNB in ​​step 1104 (or when the UE sends message 3 including its UE identifier (C-RNTI) in step 1103 and receives UE-specific control information including a CRC based on the UE identifier (C-RNTI) via PDCCH in step 1104), the UE can determine that random access was successful. Therefore, among multiple UEs receiving the same TC-RNTI from the gNB, the UE whose UE identifier is included in message 4 (CR message) can confirm that the UE has succeeded in the contention. Furthermore, the UE can send a HARQ-ACK / NACK to the gNB via the uplink control channel (PUCCH) indicating whether message 4 was successfully received.

[0314] If the gNB fails to receive data signals from the UE due to a conflict between the data transmitted by the UE in step 3 1103 and the data of another UE, the gNB may stop transmitting data to the UE. Therefore, if the UE does not receive the data transmitted from the gNB in ​​step 4 1104 within a predetermined time interval, the UE determines that the random access procedure has failed and can restart from step 1 1101.

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

[0316] The gNB can use at least one of SIB, higher-layer signaling (Radio Resource Control (RRC) information), or downlink control information (DCI) to notify the UE of configuration information for random access resources, such as control information (or configuration information) indicating time and frequency resources available for PRACH. Frequency resources for PRACH transmission can indicate the starting RB point for the UE's transmission and the number of RBs used can be determined based on the preamble format transmitted via PRACH and the applied subcarrier spacing. Time resources for PRACH transmission can be indicated by the PRACH configuration index (0 to 255) including the predetermined PRACH configuration period, subframe index, and the start symbol including the PRACH timing (which can be interchanged with the transmission time point), as well as the number of PRACH timings within the time slot, as shown in Table 16 below. The UE determines the validity of the PRACH timings indicated in the PRACH configuration index and can determine only valid PRACH timings as those through which random access preambles can be transmitted. By using the PRACH configuration index, the random access configuration information included in the SIB, and the index of the SSB selected by the UE, the UE confirms the time and frequency resources used to send the random access preamble, and can send the selected sequence as a preamble to the gNB.

[0317] Table 16

[0318]

[0319] Meanwhile, according to embodiments of this disclosure, a scheme is required in which the SBFD UE determines the validity of the PRACH timing through the PRACH configuration index and SBFD configuration used to perform PRACH transmission, and performs PRACH transmission by determining the PRACH timing as valid as described above, and the process of the SBFD UE when the valid PRACH timing and downlink reception overlap is required.

[0320] Therefore, will be used Figure 12 and Figure 13 This describes the method by which the SBFD UE determines the validity of the PRACH timing and the operation of the SBFD UE when the SBFD UE is configured or scheduled to cause a valid PRACH timing and downlink reception to occur simultaneously.

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

[0322] exist Figure 12(a) illustrates the operation of TDD in a specific frequency band. In a cell operating TDD, the base station can transmit and receive signals including data / control information in downlink time slots (or symbols), uplink time slots (or symbols) 1201, and flexible time slots (or symbols) based on the configuration of TDD UL-DL resource configuration information, which indicates the downlink time slot (or symbol) resources and uplink time slot (or symbol) resources of TDD and existing TDD UEs or SBFD UEs.

[0323] exist Figure 12 In this context, it can be assumed that the DDDSU time slot format is configured based on the TDD UL-DL resource configuration information. Here, "D" represents a time slot configured with only downlink symbols, "U" represents a time slot configured with only uplink symbols, and "S" represents a time slot that is neither "D" nor "U," i.e., a time slot that includes downlink symbols passing through uplink symbols or a time slot that includes flexible symbols. For convenience, it can be assumed that S is configured with 12 downlink symbols and 2 flexible symbols. Furthermore, the DDDSU time slot format can be repeated based on the TDD UL-DL resource configuration information. That is, the repetition period of the TDD configuration is assumed to be 5 time slots (5ms in the case of 15kHz SCS, 2.5ms in the case of 30kHz SCS, etc.).

[0324] Next, in Figure 12 (b) through (d) show the case where SBFD operates together with TDD in a specific frequency band.

[0325] refer to Figure 12 (b) The UE can be configured with a frequency band within the cell frequency range as a frequency band 1210 for uplink transmission. This frequency band can be referred to as the uplink subband (UL subband). Furthermore, the uplink subband (UL subband) can be applied to all symbols in all time slots. The UE can transmit uplink channels or signals scheduled in uplink time slots (or symbols) 1211 and all symbols 1212 within the subband (UL subband). However, the UE cannot transmit uplink channels or signals in frequency bands other than the subband (UL subband) in downlink time slots (or symbols) and flexible time slots (or symbols).

[0326] refer to Figure 12 (c) The UE is configured with a specific frequency band within the cell frequency range as a frequency band 1220 for uplink transmission, and can be configured with the time domain in which this frequency band is activated. Here, this frequency band can be referred to as the uplink sub-band (UL sub-band). Figure 12In (c), the uplink subband (UL subband) is deactivated in the first time slot, and the uplink subband (UL subband) can be activated in the remaining time slots. Therefore, the UE can transmit uplink channels or signals in uplink time slot (or symbol) 1221 and the uplink subband (UL subband) 1222 of the remaining time slots. Thus, although the uplink subband (UL subband) is activated here on a time slot unit basis, its activation can be configured on a symbol unit basis.

[0327] refer to Figure 12 (d) The UE can be configured with time-frequency resources for uplink transmission. The UE can be configured with one or more time-frequency resources for uplink transmission. For example, some frequency bands 1232 of the first and second time slots can be configured as time-frequency resources for uplink transmission. Furthermore, some frequency bands 1233 of the third time slot and some frequency bands 1234 of the fourth time slot can be configured as time-frequency resources for uplink transmission. The UE can transmit uplink channels or signals in uplink time slots (or symbols) 1231, some frequency bands 1232 of the first and second time slots, some frequency bands 1233 of the third time slot, and some frequency bands 1234 of the fourth time slot.

[0328] In the following description, the time-frequency resources in which uplink transmission can be performed in the downlink symbol or flexible symbol can be referred to as SBFD resources / UL subbands.

[0329] Figure 13 This is a diagram illustrating the effective RACH timing in TDD and SBFD configurations according to embodiments of the present disclosure.

[0330] Simultaneously, the base station can send the PRACH configuration as system information to the UE, and can configure the RACH timing according to the PRACH configuration. The UE can determine that all or some of the RACH timings are valid. As one method disclosed herein, the UE can determine the valid RACH timings as follows.

[0331] The timing of the first valid RACH can be determined based on the first PRACH configuration (the PRACH configuration of the TDD UE).

[0332] In an FDD cell, it can be defined that all first RACH timings configured according to the first RACH are valid.

[0333] In a TDD cell, it can be said that in the configured second PRACH, only the second RACH timing that meets the following conditions is valid.

[0334] - If the UE does not receive the TDD DL / UL configuration information in the system information, and if the RACH timing in the PRACH slot is not before the SS / PBCH, and is in the N of the last received symbol of the SS / PBCH... gap If the RACH timing begins after a certain number of symbols, the UE can determine that the RACH timing is valid.

[0335] - If the UE receives TDD DL / UL configuration information from the system information, and the RACH timing within the UL symbol or the RACH timing in the PRACH slot is not before the SS / PBCH, then the N-terminal of the last received symbol of the SS / PBCH... gap If the RACH timing begins after a certain number of symbols and after the last DL symbol, the UE can determine that the RACH timing is valid.

[0336] The method described above is an example; the first effective RACH timing can be determined by other methods.

[0337] refer to Figure 13 In (a), assuming the UE receives DDDSU as TDD DL / UL configuration information and configures the first RACH timing for each slot according to the first PRACH configuration, the UE can determine that the first PRACH configuration overlapping with the UL symbol is the first valid RACH timing. In this case, the fifth slot (the last slot of the TDD cycle configured with DDDSU) is an uplink slot, and the first RACH timing 1301 can be valid. However, the first RACH timings of the first, second, third, and fourth slots (the first four slots of the TDD cycle configured with DDDSU) 1302 may be invalid because they do not start after the last downlink symbol. Therefore, the UE determines that the first RACH timings of four uplink slots (the fifth, tenth, fifteenth, and twentieth) within 20 slots are valid, and can determine that the first RACH timings of the remaining 16 slots are invalid.

[0338] When the SBFD UE is configured with time-frequency resources for uplink transmission, the second valid RACH timing can be determined based on the second PRACH configuration (the SBFD UE's PRACH configuration). The UE can determine the validity of the second RACH timing as follows.

[0339] - If the UE does not receive the TDD DL / UL configuration information in the system information, and if the second RACH timing in the PRACH slot is not before the SS / PBCH, and is in the N of the last received symbol of the SS / PBCH... gap If the second RACH timing begins after a certain number of symbols, the UE can determine that the second RACH timing is valid.

[0340] - If the UE receives TDD DL / UL configuration information from the system information, and the second RACH timing within the UL symbol or the RACH timing in the PRACH slot is not before the SS / PBCH, then the N-terminal of the last received symbol of the SS / PBCH... gap If the second RACH timing begins after a symbol and is within the SBFD uplink resources, then it can be determined to be valid.

[0341] In other words, compared to the first valid RACH opportunity, when TDD DL / UL configuration information is received in the system information, the RACH opportunity included in the SBFD uplink resource area within the DL symbol can be the second valid RACH opportunity. Therefore, the UE can obtain more RACH opportunities through this method.

[0342] Depending on the location of the SS / PBCH, the second RACH timing may be invalid. Furthermore, if the second RACH timing is configured in the SBFD uplink resources (resources where uplink transmissions can be performed), there may be issues with the resources where the second RACH timing is restricted.

[0343] As a method disclosed herein, when the SBFD UE is configured with time-frequency resources for uplink transmission and SBFD uplink resources, the UE can determine the validity of the second RACH timing as follows.

[0344] - If the UE does not receive the TDD DL / UL configuration information in the system information, and if the second RACH timing in the PRACH slot is not before the SS / PBCH, and is in the N of the last received symbol of the SS / PBCH... gap If the second RACH timing begins after a certain number of symbols, the UE can determine that the second RACH timing is valid.

[0345] - If the UE receives the TDD DL / UL configuration information in the system information, it can be determined that the second RACH timing is valid if it is within the UL symbol or the RACH timing is within the SBFD resource.

[0346] The above method is an example; the second effective RACH timing can be determined by other methods.

[0347] refer to Figure 13 From (b) to (d), the UE can determine whether the second RACH timing is valid based on the TDD UL-DL resource configuration information and the SBFD uplink resource information.

[0348] refer to Figure 13(b) The UE can be configured with an uplink subband (UL subband) 1310, and the resources of the uplink subband of the downlink symbol can be determined as SBFD uplink resources. Since the second RACH timing 1311 is included in the SBFD uplink resources of the first 4 slots of the TDD cycle, the UE can determine that the second RACH timing is valid.

[0349] For reference, Figure 13 In (b), if the uplink subband (UL subband) 1310 is configured, uplink transmission can be performed in the resources of the uplink subband (UL subband) in all symbols. Therefore, the above method can be briefly described as follows.

[0350] As a method disclosed herein, when the SBFD UE is configured with time-frequency resources (SBFD resources) for uplink transmission, the UE can determine the validity of the second RACH timing as follows.

[0351] - If the frequency band of the RACH timing configured according to the PRACH configuration is included in the uplink subband (UL subband), and if the second RACH timing in the PRACH slot is not before the SS / PBCH, and is in the N of the last received symbol of the SS / PBCH. gap Starting after a symbol, the validity of the second RACH timing can be determined.

[0352] As a method disclosed herein, when the SBFD UE is configured with time-frequency resources (SBFD resources) for uplink transmission, the UE can determine the validity of the RACH timing as follows.

[0353] - If the frequency band of the second RACH timing configured according to the PRACH configuration is included in the uplink subband (UL subband), then all RACH timings can be valid.

[0354] The above method is an example; the second effective RACH timing can be determined by other methods.

[0355] refer to Figure 13(c) The UE can be configured with an uplink subband (UL subband) 1320 and a time domain in which the uplink subband is activated, and the resources of the uplink subband of the downlink symbol in the activated time domain can be determined as SBFD uplink resources. Since the second RACH timing 1321 is included in the SBFD uplink resources of the second, third, and fourth time slots of the TDD cycle, the UE can determine that the second RACH timing 1321 is valid. For reference, the second RACH timing 1322 of the first time slot of the TDD cycle can be determined to be invalid because the second RACH timing 1322 is not included in the SBFD uplink resources.

[0356] refer to Figure 13 (d) The UE can be configured with a time-frequency region containing SBFD uplink resources, and the second RACH timing overlapping with the SBFD uplink resources can be determined to be valid. That is, the second RACH timing 1332 of the first and second time slots of the TDD cycle can be considered valid because the second RACH timing 1332 is included in the SBFD uplink resources. However, the second RACH timing 1331 of the third and fourth time slots may be invalid because the second RACH timing 1331 is not included in the SBFD uplink resources.

[0357] exist Figure 13 In (b) through (d), although not specifically mentioned, a second RACH timing that overlaps with a UL symbol can always be valid. However, the UE can be configured with SBFD downlink resources, where DL transmission can be performed within a UL symbol. In this case, if the SBFD downlink resources and the second RACH timing overlap, the RACH timing may be invalid. As an alternative, the second RACH timing can be valid even if the SBFD downlink resources and the RACH timing overlap. That is, when determining a valid second RACH timing, the SBFD downlink resources configured in the uplink symbol can be ignored.

[0358] The above method can be used when a PRACH configuration is configured for both a TDD UE (not an SBFD UE) and an SBFD UE. That is, based on a PRACH resource configuration, the TDD UE determines the first valid RACH timing according to the method used by the TDD cell. Figure 13 (a)), and the SBFD UE can determine the second effective RACH timing according to the first to second methods described above. Figure 13 (b) to (d)).

[0359] [Reference RB Index for Msg3 PUSCH Transmission on SBFD UL Subband]

[0360] The UE can receive Msg3 PUSCH scheduling information from the base station. The Msg3 PUSCH scheduling information can be included in the RARUL authorization.

[0361] RAR UL authorization may include the following information:

[0362] -Frequency hopping flag-1 bit,

[0363] -PUSCH frequency resource allocation -14 bits

[0364] -PUSCH time resource allocation -4 bits

[0365] -MCS (Modulation and Coding Scheme) - 4 bits,

[0366] - TPC commands for PUSCH - 3 bits, and / or

[0367] -CSI (Channel State Information) Request -1 bit.

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

[0369] The UE can obtain the frequency domain scheduling information (index of the starting RB and 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.

[0370] Table 17

[0371]

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

[0373] refer to Figure 14In (a), 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 can be included in the active UL BWP. In this case, the UE may assume that the reference UL BWP is the same as the initial UL BWP. That is, the reference UL BWP may include the N RBs included in the initial UL BWP.

[0374] refer to Figure 14 (b) The initial UL BWP includes 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 can be indexed as RB0, RB1, ..., RBM-1, arranged in ascending order starting from 0 based on the lowest position of the RBs on the frequency axis, and the UE may assume that the reference UL BWP is the same as the active UL BWP's RB0, RB1, ..., RBN-1. That is, the reference UL BWP may include the N lowest frequency RBs among the M RBs included in the active UL BWP.

[0375] The PUSCH frequency resource allocation field indicates the scheduling RB among the N RBs of the reference UL BWP. The PUSCH frequency resource allocation can include 14 bits. The UE can interpret the PUSCH frequency resource allocation field as follows.

[0376] - If N (the number of RBs included in the initial UL BWP) is less than or equal to 180, then the UE can use only ceil(log2(N) from the 14 bits. (N+1) / 2)) LSBs (least significant bits) are used to interpret the frequency domain information of the scheduling PUSCH.

[0377] Otherwise (if N (the number of RBs included in the initial UL BWP) is greater than 180), the UE can use ceil(log2(N)) with a value of 0. (N+1) / 2))-14 bits are added to the 14 bits. Here, we can add the bits from N... UL,hop The value after the units digit is 0. (N+1) / 2))-14 MSBs are added to the frequency domain resource allocation field. The UE can then add ceil(log2(N The units digit of (N+1) / 2)) is interpreted as the frequency domain information for scheduling PUSCH. If the frequency hopping flag of the RAR UL authorization is "0", then N UL,hop=0 bit, and if the frequency hopping flag of the RAR UL authorization is "1", then N can be determined according to Table 18. UL,hop .

[0378] Table 18

[0379]

[0380] Figure 15 This illustrates a scenario where an SBFD resource or UL subband according to an embodiment of the present disclosure is not included in the reference UL BWP.

[0381] refer to Figure 15 The initial UL BWP configured for the UE includes 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 can be indexed as RB0, RB1, ..., RBM-1, arranged in ascending order based on the lowest position of the RBs on the frequency axis, starting from 0, and the UE may assume that the reference UL BWP is the same as RB0, RB1, ..., RBN-1 of the active UL BWP. That is, the reference UL BWP may include the N lowest frequency RBs among the M RBs included in the active UL BWP.

[0382] An SBFD UE can be configured with SBFD resources or a UL subband. The symbols configured with SBFD resources or UL subbands can be downlink symbols. The UE can transmit uplink channels or signals in the SBFD resources or UL subbands. Uplink channels may include Msg3 PUSCH.

[0383] An SBFD UE can choose either a first valid RACH timing or a second valid RACH timing and send a PRACH preamble to the base station. When the base station receives a PRACH preamble belonging to the first valid RACH timing, the base station can consider the UE accessing the cell as a TDD UE (a UE that does not support SBFD operation). When the base station receives a PRACH preamble belonging to the second valid RACH timing, the base station can consider the UE accessing the cell as an SBFD UE. When the base station determines that the UE is an SBFD UE, the base station can schedule Msg3 PUSCH through the UL subband. When the UE sends a PRACH preamble belonging to the second valid RACH timing, the Msg3 PUSCH scheduled to the UE can be sent in the UL subband. In this disclosure, unless otherwise specified, SBFD resources or UL subbands may only include RBs included in the initial UL subband of the SBFD resources or the UL subband configured by the base station. That is, depending on the base station configuration, RBs included in the SBFD resources or UL subband that are not included in the initial UL subband can be excluded.

[0384] However, SBFD resources or UL subbands may not be included in the reference UL BWP determined by the UE. Therefore, even though SBFD resources or UL subbands are included in the active UL BWP, the UE cannot schedule using the Msg3 PUSCH with SBFD resources or UL subbands. Methods 1-1 to 1-3 of this disclosure provide methods to solve this problem. At least one of methods 1-1 and 1-3 of this disclosure can be performed in combination with at least one of methods 2-1 and 2-2 described later.

[0385] Method 1-1

[0386] When the Msg3 PUSCH is scheduled in an SBFD symbol, the UE can select the lowest RB of the SBFD resource or UL subband as the starting RB of the reference UL BWP. The UE can 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 index of the lowest RB of the SBFD resource or UL subband can be called P (P is an integer). This index can be the index of the Common Resource Block (CRB) or the index of the active UL BWP (the index of the lowest RB of the active UL BWP is 0, arranged in ascending order on the frequency axis). Furthermore, it can be said that the SBFD resource or UL subband includes K RBs (K is a natural number). RB P, RB P+1, RB P+2, ..., RB P+K-1 can be included in the SBFD resource or UL subband. The reference UL BWP can include RB P, RB P+1, RB P+2, ..., RB P+N-1. Here, 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 N RBs.

[0387] The UE can interpret the PUSCH frequency resource allocation field as follows.

[0388] - If N (the number of RBs included in the initial UL BWP) is less than or equal to 180, then the UE can use only ceil(log2(N) from the 14 bits. (N+1) / 2)) LSBs (least significant bits) are used to interpret the frequency domain information of the scheduling PUSCH.

[0389] Otherwise (if N (the number of RBs included in the initial UL BWP) is greater than 180), the UE can ceil(log2(N) (N+1) / 2))-14 bits with a value of 0 are added to the 14 bits. Here, N in the 14 bits... UL,hop ceil(log2(N) with a value of 0 after the units digit (N+1) / 2))-14 MSBs are added to the frequency domain resource allocation field. The UE can then add ceil(log2(N The units digit of (N+1) / 2)) is interpreted as the frequency domain information for scheduling PUSCH. If the frequency hopping flag of the RAR UL authorization is "0", then N UL,hop =0 bit, and if the frequency hopping flag of the RAR UL authorization is "1", then N can be determined according to Table 19 or Table 20. UL,hop .

[0390] Table 19

[0391]

[0392] Table 20

[0393]

[0394] Method 1-2

[0395] When the Msg3 PUSCH is scheduled in an SBFD symbol, the UE can select the lowest RB of the SBFD resource or UL subband as the starting RB of the reference UL BWP. The UE can select the number of RBs included in the UL subband as the length of the reference UL BWP (i.e., the number of RBs included in the reference UL BWP). More specifically, the index of the lowest RB of the SBFD resource or UL subband can be referred to as P. This index can be an index of the Common Resource Block (CRB) or an index of the active UL BWP (the index of the lowest RB of the active UL BWP is 0, arranged in ascending order on the frequency axis). Furthermore, it can be said that the SBFD resource or UL subband includes K RBs. RB P, RBP+1, RB P+2, ..., RB P+K-1 can be included in the SBFD resource or UL subband. The UE can include RB P, RB P+1, RBP+2, ..., RB P+K-1 as the reference UL BWP. Here, K is the number of RBs included in the UL subband. The UE can interpret the scheduling information of the Msg3 PUSCH based on K RBs.

[0396] The UE can interpret the PUSCH frequency resource allocation as follows.

[0397] - If K (the number of RBs included in the UL subband) is less than or equal to 180, then the UE can use only ceil(log2(K) in 14 bits. (K+1) / 2)) LSBs (least significant bits) are used to interpret the frequency domain information of the scheduling PUSCH.

[0398] Otherwise (if K (the number of RBs included in the UL subband) is greater than 180), the UE can ceil(log2(K) (K+1) / 2))-14 bits with a value of 0 are added to the 14 bits. Here, it can be done in N UL,hop ceil(log2(K) with a value of 0 after the units digit (K+1) / 2))-14 MSBs are added to the frequency domain resource allocation field. The UE can then add ceil(log2(K (K+1) / 2)) The units digit is interpreted as the frequency domain information for scheduling PUSCH. If the frequency hopping flag of the RAR UL authorization is "0", then N UL,hop =0 bit, and if the frequency hopping flag of the RAR UL authorization is "1", then N can be determined according to Table 19.UL,hop .

[0399] Methods 1-3

[0400] When Msg3 PUSCH is scheduled in an SBFD symbol, the UE can select the highest RB of the SBFD resource or UL subband as the last RB of the reference UL BWP. The UE can select the number of RBs included in the initial UL BWP (i.e., N) 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 can be referred to as P. This index can be an index of the Common Resource Block (CRB) or an index of the active UL BWP (the index of the lowest RB of the active UL BWP is 0, arranged in ascending order on the frequency axis). Furthermore, it can be said that the SBFD resource or UL subband includes K RBs. RB P, RB P+1, RB P+2, ..., RB P+K-1 can be included in the SBFD resource or UL subband. The UE can include RBP+KN, RB P+K-N+1, ..., RB P+K-2, RB P+K-1 as the 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 UE can interpret the scheduling information of Msg 3 PUSCH based on N RBs.

[0401] The PUSCH frequency resource allocation field can be explained with reference to the description in Method 1-1 above. In this disclosure, the SBFD symbol can be a symbol in which SBFD resources or UL subbands are configured.

[0402] Alternatively, in this disclosure, an SBFD symbol may be a downlink symbol among symbols in which SBFD resources or UL subbands are configured.

[0403] [RB allocation determined by Msg3 PUSCH transmitted on SBFD UL subband]

[0404] As an embodiment of this disclosure, the UE uses the initial UL BWP or a truncated active UL BWP as a reference UL BWP, and the RB allocation (starting RB index and RB length) determined based on the reference UL BWP can be moved into the UL subband. This applies to the case of scheduling Msg3 PUSCH in SBFD symbols. Here, using a truncated active UL BWP can mean that the number of RBs used starting from the starting RB of the active UL BWP is the same as the number used by the initial UL BWP.

[0405] For reference, this embodiment may be used in a limited manner in the following situations.

[0406] - In the case where the determined reference UL BWP does not include the RBs of the UL sub-band. For example, the determined reference UL BWP may correspond to the case where the determined reference UL BWP consists of N consecutive RBs starting from the initial RB of the active UL BWP (N = the number of RBs included in the initial UL BWP).

[0407] For reference, in this embodiment, it can be assumed that the reference UL BWP is determined according to Table 17. This is one approach, and the disclosed method can be applied even if the reference UL BWP is determined by another method.

[0408] At least one of the methods 2-1 and 2-2 of this disclosure can be performed in combination with at least one of the methods 1-1 and 1-3 described above.

[0409] Method 2-1

[0410] When the UE determines the RB allocation based on the initial UL BWP, the index of the starting RB and the number of consecutive RBs can be expressed as S, respectively. initial and L initial Among them, S initial An RB with a value of 0 can be the same RB as the lowest RB on the initial UL BWP frequency. The UE can change / move RB allocations into the UL subband based on the UL subband configuration.

[0411] More specifically, the index of the starting RB of the UL subband is called S. ULSB Furthermore, the number of RBs included in the UL subband can be expressed as L. ULSB Here, S ULSB The RB with a value of 0 can be the same as the lowest RB at the initial UL BWP frequency. The UE can use Equations 2 through 5 to determine the index (S) of the starting RB in the UL subband RB allocation. mod Here, the index of the starting RB (S) mod An RB with a value of 0 can be the same RB as the lowest RB at the frequency of the initial UL BWP.

[0412] [Equation 2]

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

[0414] [Equation 3]

[0415] S mod = ((S initial -S ULSB ) mod LULSB )+S ULSB

[0416] [Equation 4]

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

[0418] [Equation 5]

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

[0420] In Equation 4, the offset can be a value configured or indicated by the base station to the UE. Equation 3 can be equivalent to offset = -S in Equation 4. ULSB In this case, Equation 2 can be the case where offset = 0 in Equation 4.

[0421] In Equation 5, offset2 can be a value configured or indicated by the base station to the UE. Here, offset2 can be a number greater than or equal to 0.

[0422] As an example, the modular operations in equations 2 through 5 can be omitted. That is, equations 2 and 3 can be represented as equations 6 and 7.

[0423] [Equation 6]

[0424] S mod = S initial +S ULSB

[0425] [Equation 7]

[0426] S mod = S initial

[0427] The UE can use the determined starting RB index to set L initial A consecutive RB is identified as a scheduling RB within the UL subband.

[0428] S determined by UE mod It should be greater than or equal to S ULSB And S mod +L initial It should be less than or equal to S ULSB +L ULSBIf this condition is not met, the UE can ignore the RAR UL authorization used to schedule the Msg3 PUSCH. In other words, the UE can choose not to send the Msg3 PUSCH.

[0429] For reference, Equations 2 through 7 use the RB number of the initial UL BWP. That is, where S mod The RB with =0 can be the same as the lowest RB on the frequency axis in the initial UL BWP. As one method of this disclosure, Equations 2 through 7 can utilize the RB numbering of the UL sub-band. That is, where S mod The RB with =0 can be the same as the lowest RB on the frequency axis in the UL subband. For example, refer to Equation 7, S mod =S initial It is possible, and S is among them. mod An RB with a value of 0 can be the same as the lowest RB on the frequency axis in the UL subband.

[0430] Method 2-2

[0431] When the UE determines the RB allocation based on the truncated active UL BWP, the index of the starting RB and the number of consecutive RBs can be expressed as S, respectively. active and L active Among them, S active An RB with a value of 0 can be the same as the lowest RB on the active UL BWP frequency. The UE can change / move RB assignments to UL subbands based on the UL subband configuration.

[0432] More specifically, the index of the starting RB of the UL subband is called S. ULSB Furthermore, the number of RBs included in the UL subband can be expressed as L. ULSB Here, S ULSB An RB with a value of 0 can be the same RB as the lowest RB at the frequency of the active UL BWP. The UE can use Equations 8 to 11 to determine the index (S) of the starting RB in the RB allocation within the UL subband. mod Here, at the index (S) of the starting RB. mod When ) is 0, the RB can be the same as the lowest RB at the frequency of the active UL BWP.

[0433] [Equation 8]

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

[0435] [Equation 9]

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

[0437] [Equation 10]

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

[0439] [Equation 11]

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

[0441] In Equation 10, the offset can be a value configured or indicated by the base station to the UE. Equation 9 can be offset = -S in Equation 10. ULSB In this case, Equation 8 can be the case where offset = 0 in Equation 10.

[0442] In Equation 11, offset2 can be a value configured or indicated by the base station to the UE. Here, offset2 can be a number greater than or equal to 0.

[0443] As an example, the modular operations in equations 8 to 11 can be omitted. That is, equations 8 and 9 can be represented as equations 12 and 13.

[0444] [Equation 12]

[0445] S mod = S active +S ULSB

[0446] [Equation 13]

[0447] S mod = S active

[0448] The UE can use the determined starting RB index to set L active A consecutive RB is identified as a scheduling RB within the UL subband.

[0449] S determined by UE mod It should be greater than or equal to S ULSB And S mod +Lactive It should be less than or equal to S ULSB +L ULSB If this condition is not met, the UE can ignore the RAR UL authorization used to schedule the Msg3 PUSCH. In other words, the UE can choose not to send the Msg3 PUSCH.

[0450] For reference, Equations 8 through 13 use the RB number of the truncated valid UL BWP. That is, where S mod The RB with =0 can be the same as the lowest RB on the frequency axis in the active UL BWP. As one method of this disclosure, Equations 8 to 13 can utilize the RB numbering of the UL sub-band. That is, where S mod The RB with =0 can be the same as the lowest RB on the frequency axis in the UL subband. For example, referring to Equation 13, S mod = S active It is possible, and in S mod In the case of 0, RB can be the same as the lowest RB on the frequency axis in the UL subband.

[0451] In methods 2-1 and 2-2 above, S can be determined based on the PUSCH frequency resource allocation field of the RAR UL license. initial and S active If the frequency hopping flag of the RAR UL authorization is "0" (disabled), the scheduled Msg3 PUSCH can have an S initial Or an S active If the frequency hopping flag of the RAR UL license is "1" (enabled), the scheduled Msg3PUSCH can have two S initial Or two S active Here, the first S initial or S active It is the index of the starting RB of the first frequency hopping, and the second S initial Or S active This is the index of the starting RB of the second frequency hopping. For convenience, the first S... initial or S active Represented as S initial (1) or S active (1), the second S initial or S active Then it is represented as S initial (2) or S active (2). Furthermore, the starting RB index of the first frequency hopping within the UL subband is denoted as S. mod (1) The starting RB index of the second frequency hopping within the UL subband is represented as S. mod (2).

[0452] As an embodiment of this disclosure, method 2-1 or method 2-2 described above can be applied individually to each frequency hopping. That is, in method 2-1 or method 2-2, S mod (1) Can be based on S initial (1) or S active (1) to determine, and S mod (2) Can be based on S initial (2) or S active (2) To determine. Here, S initial (1) or S active (1) is the index of the starting RB determined by the PUSCH frequency resource allocation field authorized by RAR UL, while S initial (2) or S active (2) can be the index of the starting RB as determined below.

[0453] [Equation 14]

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

[0455] [Equation 15]

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

[0457] [Equation 16]

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

[0459] [Equation 17]

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

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

[0462] Figure 16 This is a flowchart illustrating the operation of a UE according to an embodiment of the present disclosure.

[0463] Figure 16 The order of operations can be changed, and some operations can be omitted.

[0464] although Figure 16 Although not shown, the UE's random access procedure can begin with the transmission of a random access preamble. The UE can receive a Random Access Response (RAR) in response to the random access preamble. The RAR may include a UL grant for scheduling PUSCH transmission. After receiving the RAR UL grant, the UE can perform... Figure 16 The process.

[0465] The UE can determine the resources (e.g., frequency domain resource allocation and / or time domain resource allocation) for Msg3 PUSCH transmission based on the RAR UL authorization. Specifically, refer to... Figure 16 In step 1600, the UE can determine the starting RB index and the number of consecutive RBs for the first hop of the Msg3 PUSCH transmission based on the reference UL BWP using the PUSCH frequency resource allocation field of the RAR UL authorized. For example, the reference UL BWP can be a truncated valid UL BWP or an initial UL BWP. For example, the reference UL BWP can be determined according to Table 17.

[0466] For example, if the Msg3 PUSCH transmission is scheduled within an SBFD symbol, i.e., if the Msg3 PUSCH transmission is scheduled within a UL frequency subband within a downlink symbol, the RB number can start from the first RB of the UL frequency subband. Furthermore, the maximum number of RBs allocated for frequency domain resources for the Msg3 PUSCH transmission can be determined based on the number of RBs within the initial UL BWP. For example, the maximum number of RBs allocated for frequency domain resources for the Msg3 PUSCH transmission can be the same as the number of RBs within the initial UL BWP. For example, the starting RB index of the first hop for the Msg3 PUSCH transmission can be determined based on the RB number.

[0467] In step 1610, the UE can determine whether to perform frequency hopping for Msg3 PUSCH using the frequency hopping flag field of the RAR UL authorization. For example, if frequency hopping is applied to Msg3 PUSCH transmission, the frequency offset of the second hop can be determined based on the number of RBs within the UL frequency subband. For example, if frequency hopping is indicated for Msg3 PUSCH transmission, the UE can determine the starting RB index of the second hop based on a reference UL BWP. For example, the UE can determine the starting RB index of the second hop using at least one of Equations 14 to 17.

[0468] In step 1620, the UE 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 Equations 2 to 13.

[0469] In step 1630, the UE can 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 can be determined based on at least one of Equations 2 to 13.

[0470] In step 1640, the UE may transmit the first hop in the UL subband based on the starting RB index of the first hop determined in step 1620, and transmit the second hop based on the starting RB index of the second hop determined in step 1630.

[0471] As an embodiment of this disclosure, method 2-1 or method 2-2 described above can be applied only to the first frequency hopping. That is, in method 2-1 or method 2-2, S mod (1) Can be based on S initial (1) or S active (1) Determine. Here, S initial (1) or S active (1) is the index of the starting RB determined based on the PUSCH frequency resource allocation field authorized by RAR UL. This can be based on the S determined in method 2-1 or method 2-2. mod (1) Determine the index of the starting RB for the second hop. For example, S initial (2) or S active (2) is the index of the starting RB as determined below.

[0472] [Equation 18]

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

[0474] [Equation 19]

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

[0476] In equations 18 and 19, N ULSB It is the number of RBs included in the UL subband, and S ULSBIt is the index of the starting RB of the UL subband. In the case of method 2-1, where S mod (1) = 0, S mod (2) = 0 and S ULSB The RB with =0 is the lowest RB on the frequency axis in the initial UL BWP, while in the case of method 2-2, where S mod (1) = 0, S mod (2) = 0 and S ULSB The RB with a value of 0 can be the lowest RB on the frequency axis in an active UL BWP.

[0477] In Equations 18 and 19, the Offset can be determined by at least one of the methods in Tables 18 to 20.

[0478] Figure 17 This is a flowchart illustrating the operation of a UE according to an embodiment of the present disclosure. Figure 17 The order of operations can be changed, and some operations can be omitted.

[0479] refer to Figure 17 In step 1700, the UE can determine the starting RB index and the number of consecutive RBs for the first hop through the PUSCH frequency resource allocation field of the RAR UL authorization. Here, the reference UL BWP can be a truncated valid UL BWP or an initial UL BWP. For example, the reference UL BWP can be determined according to Table 17.

[0480] In step 1710, the UE 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 Equations 2 to 13.

[0481] In step 1720, the UE can determine whether to perform frequency hopping for Msg3 PUSCH using the frequency hopping flag field of the RAR UL authorization. If frequency hopping is indicated for Msg3 PUSCH, the UE 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 to 19.

[0482] In step 1730, the UE may transmit the first hop of Msg3 PUSCH in the UL subband based on the starting RB index of the first hop determined in step 1710, and transmit the second hop of Msg3 PUSCH based on the starting RB index of the second hop determined in step 1720.

[0483] [RB allocation determination for PUCCH transmission on SBFD UL subband]

[0484] A UE can be configured with PUCCH resources after an RRC connection is established. The configuration information for PUCCH resources may include the following parameters.

[0485] -PUCCH Resource Index (or ID): This can be used to indicate or identify a PUCCH resource as a unique index (or ID).

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

[0487] -intraSlotFrequencyHopping: This indicates whether PUCCH is transmitted using a frequency hopping scheme.

[0488] -SecondHopPRB: This can be the starting RB index of the second frequency hopping of PUCCH.

[0489] -format: This can be the format of PUCCH. Here, the format of PUCCH can be one of the following values: format0, format1, format2, format3, and format4.

[0490] As an embodiment of this disclosure, the UE can use PUCCH resource configuration in the uplink symbol and UL subband. More specifically, the UE can determine the starting RB index of the first and second frequency hopping for PUCCH transmission based on the StartingPRB and SecondHopPRB. Here, the determination method is as follows.

[0491] As a method, when the PUCCH is scheduled in an uplink symbol and in an SBFD symbol (where a UL subband is configured), the UE can use the RB number of the active UL BWP to determine the StartingPRB and SecondHopPRB. That is, the RB where StartingPRB=0 and the RB where SecondHopPRB=0 can be the same as the lowest RB of the active UL BWP. In other words, regardless of the symbol type in which the PUCCH is scheduled, the UE can use the active UL BWP number to determine the index of the starting RB of the PUCCH.

[0492] When the UE is scheduled to use PUCCH in an SBFD symbol (where the UL subband is configured), the StartingPRB and SecondHopPRB may not be RBs included in the UL subband. In this case, the UE can convert the StartingPRB and SecondHopPRB into RBs within the UL subband using a frequency hopping function. Here, the frequency hopping function can be as follows.

[0493] [Equation 20]

[0494] The starting PRB of the first frequency hopping in the UL subband =

[0495] (( Starting PRB -S ULSB ) mod L ULSB )+S ULSB

[0496] The starting PRB of the second frequency hopping in the UL subband =

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

[0498] In equation 20, S ULSB It is the index of the RB that begins in the UL sub-band, which can follow the numbering of the active UL BWP. That is, where S... ULSB A RB of 0 can be the lowest RB on the frequency axis of the active UL BWP. ULSB This can be the number of RBs included in the UL sub-band.

[0499] For reference, Equation 20 can be applied to a limited extent when StartingPRB and SecondHopPRB are not RBs included in the UL subband. Alternatively, Equation 20 can always be used. That is, Equation 20 can be applied even if StartingPRB and SecondHopPRB are RBs included in the UL subband.

[0500] When a UE has PUCCH scheduled in an SBFD symbol (where the UL subband is configured), the StartingPRB and SecondHopPRB may not be RBs included in the UL subband. In this case, the UE may expect that the PUCCH resource will not be scheduled in the UL subband. That is, if the PUCCH resource is scheduled in the UL subband, the UE may not send PUCCH in the PUCCH resource.

[0501] As one approach, when the PUCCH is scheduled to the UE in an uplink symbol, the RB number of the active ULBWP can be used to determine the StartingPRB and SecondHopPRB. That is, the RB where StartingPRB=0 and the RB where SecondHopPRB=0 can be the same as the lowest RB of the active UL BWP. When the PUCCH is scheduled in an SBFD symbol (where the UL subband is configured), the RB number of the UL subband can be used to determine the StartingPRB and SecondHopPRB. That is, the RB where StartingPRB=0 and the RB where SecondHopPRB=0 can be the same as the lowest RB of the UL subband. In other words, the StartingPRB and SecondHopPRB are configured as higher-layer signals, but the UE's interpretation of the StartingPRB and SecondHopPRB can be determined based on the type of symbol in which the PUCCH is scheduled.

[0502] As an embodiment of this disclosure, the UE may be additionally configured with the following parameters for the UL subband in the PUCCH resource.

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

[0504] -SecondHopPRBonSBFD: It can be the starting RB index of the second frequency hopping in the PUCCH of the SBFD symbol.

[0505] For reference, other parameters of the PUCCH resource, the PUCCH resource index (or ID), intraSlotFrequencyHopping, and format can be used together in the UL symbol and UL sub-band.

[0506] The UE can determine the index of the RB in the UL subband where the PUCCH is transmitted via StartingPRBonSBFD and SecondHopPRBonSBFD. More specifically, when the UE schedules the PUCCH in an SBFD symbol (where the UL subband is configured), the index of the RB in the UL subband where the PUCCH is transmitted can be determined via StartingPRBonSBFD and SecondHopPRBonSBFD; and when the UE schedules the PUCCH in a UL symbol, the index of the RB in the UL symbol where the PUCCH is transmitted can be determined via StartingPRB and SecondHopPRB.

[0507] When determining the index of the RB in which the PUCCH is transmitted within the UL subband via StartingPRBonSBFD and SecondHopPRBonSBFD, the UE can use one of the following methods.

[0508] As one approach, the RB number of the active UL BWP can be used to determine StartingPRBonSBFD and SecondHopPRBonSBFD. That is, the RB where StartingPRB=0 and the RB where SecondHopPRB=0 can be the same as the lowest RB of the active UL BWP. In other words, regardless of the symbol type in which the PUCCH is scheduled, the UE can use the active UL BWP number to determine the index of the starting RB of the PUCCH.

[0509] For the UE, StartingPRBonSBFD and SecondHopPRBonSBFD may not be RBs included in the UL subband. In this case, the UE can convert StartingPRBonSBFD and SecondHopPRBonSBFD into RBs within the UL subband using a frequency hopping function. Here, the frequency hopping function can be as follows.

[0510] [Equation 21]

[0511] The starting PRB of the first frequency hopping in the UL subband =

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

[0513] The starting PRB of the second frequency hopping in the UL subband =

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

[0515] In equation 21, S ULSB It is the index of the RB that begins the UL sub-band, which can follow the numbering of the active UL BWP. That is, where S ULSB A RB of 0 can be the lowest RB on the frequency axis of the active UL BWP. ULSB This can be the number of RBs included in the UL sub-band.

[0516] For reference, Equation 21 can be applied to a limited extent 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 if StartingPRBonSBFD and SecondHopPRBonSBFD are RBs included in the UL subband.

[0517] If the UE has scheduled a PUCCH in an SBFD symbol (where the UL subband is configured), StartingPRBonSBFD and SecondHopPRBonSBFD may not be RBs included in the UL subband. In this case, the UE may expect the PUCCH resource not to be scheduled in the UL subband. That is, if the PUCCH resource is scheduled in the UL subband, the UE may not send the PUCCH in the PUCCH resource.

[0518] As a method, when the UE is scheduled using PUCCH in an SBFD symbol (where the UL subband is configured), the RB number of the UL subband can be used to determine StartingPRBonSBFD and SecondHopPRBonSBFD. That is, the RB where StartingPRBonSBFD=0 and the RB where SecondHopPRBonSBFD=0 can be the same as the lowest RB of the UL subband.

[0519] The above embodiments of this disclosure can be derived from... Figure 18 Terminals and Figure 19 The base station performs the operation.

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

[0521] refer to Figure 18 The terminal may include a transceiver for the terminal receiver 1800 and the terminal transmitter 1810, a memory (not shown), and a terminal processor 1805 (or a terminal controller or processor). According to the communication method described above, the transceivers 1800 and 1810, the memory, and the terminal processor 1805 can operate. The terminal processor 1805 (or processor) can control the operation of the terminal according to at least one embodiment and combinations of each of the above embodiments. However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more components or fewer components than those described above. Furthermore, the transceiver, memory, and processor may be implemented as a single chip.

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

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

[0524] The memory can store the programs and data required for terminal operation. Furthermore, the memory can store control information or data included in the signals sent and received by the terminal. The memory can be configured with storage media such as ROM, RAM, hard disk, CD-ROM, and DVD, or combinations of storage media. In addition, multiple memories can exist.

[0525] Furthermore, the processor can control a series of processes, enabling the terminal to operate according to the above embodiments. For example, the processor can be configured to send a random access preamble and receive a Receipt Arrangement (RAR) in response to the random access preamble. In this case, the RAR may include a UL grant for scheduling PUSCH transmission. Additionally, the processor can be configured to determine the frequency domain resource allocation for PUSCH transmission based on the UL grant and to send message 3 (Msg3) in the PUSCH based on the frequency domain resource allocation. When PUSCH transmission is scheduled within a UL frequency subband within a downlink symbol, the RB numbering starts from the first RB of the UL frequency subband, and the maximum number of RBs for frequency domain resource allocation can be determined based on the number of RBs within the initial UL BWP. Multiple processors can exist, and each processor can perform component control operations of the terminal by executing programs stored in memory.

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

[0527] refer to Figure 19The base station may include transceivers, a memory (not shown), and a base station processor 1905 (or a base station controller or processor) relating to the base station receiver 1900 and the base station transmitter 1910. According to the communication method of the base station described above, the transceivers 1900 and 1910, the memory, and the base station processor 1905 can operate. The base station processor 1905 (or processor) can control the operation of the base station according to at least one embodiment and combinations of each of the above embodiments. However, the components of the base station are not limited to the examples described above. For example, the base station may include more or fewer components than those described above. Furthermore, the transceiver, memory, and processor may be implemented as a single chip.

[0528] A transceiver can send and receive signals with a terminal. These signals can include control information and data. For this purpose, the transceiver can be configured with an RF transmitter that up-converts and amplifies the frequency of the transmitted signal, and an RF receiver that performs low-noise amplification and down-conversion of the frequency of the received signal. However, this is only one embodiment of a transceiver, and the components of the transceiver are not limited to RF transmitters and RF receivers.

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

[0530] The memory can store the programs and data required for base station operation. In addition, the memory can store control information or data included in the signals transmitted and received by the base station. The memory can be configured with storage media such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media. Furthermore, multiple memories can exist.

[0531] The processor can control a series of processes that enable the base station to operate according to the embodiments described above. For example, the processor can be configured to receive a random access preamble from a terminal, send a RAR in response to the random access preamble to the terminal, and receive message 3 (Msg3) from the terminal in the PUSCH. In this case, the RAR includes a UL grant for scheduling PUSCH transmission, and the frequency domain resource allocation for the PUSCH can be based on the UL grant. When PUSCH transmission is scheduled in a UL frequency subband within a downlink symbol, the RB numbering starts from the first RB in the UL frequency subband, and the maximum number of RBs for frequency domain resource allocation can be determined based on the number of RBs within the initial UL BWP. Multiple processors can exist, and each processor can perform component control operations of the base station by executing programs stored in memory.

[0532] The methods described in the claims or specification of this disclosure can be implemented in hardware, software, or a combination of hardware and software.

[0533] When implemented as software, a computer-readable storage medium may be provided storing one or more programs (software modules). The one or more programs stored in the computer-readable storage medium are configured to be executed by one or more processors in an electronic device. The one or more programs include instructions to cause the electronic device to perform a method according to an embodiment described in the claims or specification of this disclosure.

[0534] Programs (e.g., software modules or software) can be stored in random access memory, non-volatile memory including flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk storage devices, optical disc ROM (CD-ROM), digital versatile disc (DVD), another optical storage device, or magnetic tape. Alternatively, programs can be stored in a memory comprising some or all of the above-described storage media. Furthermore, each memory can be provided in multiples.

[0535] Furthermore, the program can be stored on an attachable storage device accessible via any communication network, or a combination thereof, such as the Internet, intranet, local area network (LAN), wide area network (WLAN), and storage area network (SAN). Such a storage device can be accessed via an external port to the device executing embodiments of this disclosure. Additionally, a separate storage device on the communication network can be connected to the device executing embodiments of this disclosure.

[0536] In the specific embodiments described above, one or more components included in the present invention are represented in singular or plural form according to the described embodiments. However, for ease of description, singular or plural expressions have been suitably chosen for the proposed cases, and this disclosure is not limited to singular or plural expressions. Therefore, components represented in plural terms may be configured in singular form, or components represented in singular terms may be configured in plural form.

[0537] Furthermore, the embodiments disclosed in this specification and accompanying drawings are provided only as specific examples, intended to readily explain the technical content and aid in understanding this disclosure, and are not intended to limit the scope of the technology disclosed herein. That is, it will be apparent to those skilled in the art that other modified embodiments can be implemented based on the technical spirit of this disclosure. Moreover, the various embodiments described above can be combined with each other as needed. For example, a base station and a UE can operate in a manner combining portions of embodiments of this disclosure with portions of another embodiment of this disclosure. For example, portions of the first and second embodiments of this disclosure can be combined with each other to operate a base station and a terminal. Furthermore, although these embodiments are based on an FDD LTE system, other modifications based on the technical concepts of these embodiments can also be implemented in other systems, such as TDD LTE systems, 5G, or NR systems.

[0538] Meanwhile, in the accompanying drawings explaining the method of the present invention, the order of description does not necessarily correspond to the order of execution, and the order relationship can be changed, or these steps can be executed in parallel.

[0539] Alternatively, the accompanying drawings illustrating the method of the present invention may omit some components and include only some components without prejudice to the nature of the invention.

[0540] Furthermore, the method of the present invention can be performed by combining some or all of the contents included in each embodiment without prejudice to the nature of the present invention.

Claims

1. A method performed by a terminal in a wireless communication system, the method comprising: Send a random access preamble; Receive a random access response (RAR) in response to a random access preamble, wherein the RAR includes an uplink (UL) grant for scheduling transmission of the Physical Uplink Shared Channel (PUSCH); The frequency domain resource allocation for PUSCH transmission is determined based on the UL authorization; and Message 3 (Msg3) is sent in the PUSCH based on frequency domain resource allocation. In the case where PUSCH transmission is scheduled in the UL frequency subband within the downlink symbol, the resource block (RB) number starts from the first RB of the UL frequency subband, and the maximum number of RBs used for frequency domain resource allocation is determined based on the number of RBs within the initial UL bandwidth portion (BWP).

2. The method according to claim 1, wherein, The maximum number of RBs used for frequency domain resource allocation is the same as the number of RBs within the initial UL BWP.

3. The method according to claim 1, further comprising: Frequency hopping identification is applied to PUSCH transmission. The frequency offset of the second hop in frequency hopping is determined based on the number of RBs within the UL frequency subband.

4. The method according to claim 1, wherein, The frequency hopping bits associated with frequency hopping are determined based on the number of RBs within the initial UL BWP.

5. A method performed by a base station in a wireless communication system, the method comprising: Receive random access preamble from the terminal; Send a Random Access Response (RAR) to the terminal in response to the random access preamble, wherein the RAR includes an uplink (UL) grant for scheduling transmission of the Physical Uplink Shared Channel (PUSCH); and Receive message 3 (Msg3) from the terminal in PUSCH. The frequency domain resource allocation for PUSCH is based on UL authorization, and In the case where PUSCH transmission is scheduled in the UL frequency subband within the downlink symbol, the resource block (RB) number starts from the first RB of the UL frequency subband, and the maximum number of RBs used for frequency domain resource allocation is determined based on the number of RBs within the initial UL bandwidth portion (BWP).

6. The method according to claim 5, wherein, The maximum number of RBs used for frequency domain resource allocation is the same as the number of RBs within the initial UL BWP.

7. The method according to claim 5, further comprising: Configure the value of the frequency hopping flag included in the UL authorization to indicate that frequency hopping is applied to PUSCH transmission. The frequency offset of the second hop in frequency hopping is determined based on the number of RBs within the UL frequency subband.

8. The method according to claim 5, wherein, The frequency hopping bits associated with frequency hopping are determined based on the number of RBs within the initial UL BWP.

9. A terminal in a wireless communication system, the terminal comprising: transceiver; and The processor is operatively connected to the transceiver. The processor is configured as follows: Send a random access preamble; Receive a random access response (RAR) in response to a random access preamble, wherein the RAR includes an uplink (UL) grant for scheduling transmission of the Physical Uplink Shared Channel (PUSCH); The frequency domain resource allocation for PUSCH transmission is determined based on the UL authorization; and Message 3 (Msg3) is sent in the PUSCH based on frequency domain resource allocation. In the case where PUSCH transmission is scheduled in the UL frequency subband within the downlink symbol, the resource block (RB) number starts from the first RB of the UL frequency subband, and the maximum number of RBs used for frequency domain resource allocation is determined based on the number of RBs within the initial UL bandwidth portion (BWP).

10. The terminal according to claim 9, wherein, The maximum number of RBs used for frequency domain resource allocation is the same as the number of RBs within the initial UL BWP.

11. The terminal according to claim 9, wherein, The processor is also configured to recognize frequency hopping applied to PUSCH transmissions, and The frequency offset of the second hop in frequency hopping is determined based on the number of RBs within the UL frequency subband.

12. The terminal according to claim 9, wherein, The frequency hopping bits associated with frequency hopping are determined based on the number of RBs within the initial UL BWP.

13. A base station in a wireless communication system, the base station comprising: transceiver; and The processor is operatively connected to the transceiver. The processor is configured as follows: Receive random access preamble from the terminal; Send a Random Access Response (RAR) to the terminal in response to the random access preamble, wherein the RAR includes an uplink (UL) grant for scheduling transmission of the Physical Uplink Shared Channel (PUSCH); and Receive message 3 (Msg3) from the terminal in PUSCH. The frequency domain resource allocation for PUSCH is based on UL authorization, and In the case where PUSCH transmission is scheduled in the UL frequency subband within the downlink symbol, the resource block (RB) number starts from the first RB of the UL frequency subband, and the maximum number of RBs used for frequency domain resource allocation is determined based on the number of RBs within the initial UL bandwidth portion (BWP).

14. The base station according to claim 13, wherein, The maximum number of RBs used for frequency domain resource allocation is the same as the number of RBs within the initial UL BWP.

15. The base station according to claim 13, wherein, The processor is also configured to configure the value of the frequency hopping flag included in the UL license to indicate that frequency hopping is applied to PUSCH transmissions. The frequency offset of the second hop in the frequency hopping is determined based on the number of RBs within the UL frequency sub-band, and The frequency hopping bits associated with frequency hopping are determined based on the number of RBs within the initial UL BWP.

Images