Method and apparatus for transmitting uplink channels and signals in a wireless communication system

Abstract

With the development of communication systems, there is a need for an efficient method for transmitting an uplink channel or signal. The present disclosure relates to a fifth generation (5G) or sixth generation (6G) communication system for supporting a higher data rate. More specifically, the present disclosure relates to an apparatus capable of Msg3 physical uplink shared channel (PUSCH) transmission by a terminal.

Description

Technical Field

[0001] This disclosure relates to the operation of terminals and base stations in wireless communication systems. More specifically, this disclosure relates to a device capable of enabling a terminal to perform Msg3 Physical Uplink Shared Channel (PUSCH) transmission. Background Technology

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

[0003] In the early stages of 5G mobile communication technology development, to support services and meet performance requirements for enhanced mobile broadband (eMBB), ultra-reliable and low-latency communication (URLLC), and massive machine-type communication (mMTC), the following technologies have been standardized: beamforming and massive multiple-input multiple-output (MIMO) for reducing radio wave path loss and increasing radio wave transmission distance in millimeter waves (mmWave); support parameters for dynamic operation (e.g., operating multiple subcarrier spacings) for efficient utilization of millimeter wave resources and time slot formats; initial access technologies to support multi-beam transmission and wideband; definition and operation of bandwidth portions (BWP); new channel coding methods such as low-density parity-check (LDPC) codes for large data transmissions and polar codes for highly reliable transmission of control information; layer 2 (L2) preprocessing; and network slicing for providing dedicated networks for specific services.

[0004] Currently, regarding the services supported by 5G mobile communication technology, the industry is continuously discussing improvements and performance enhancements to the initial 5G mobile communication technology, and physical layer standardization has been completed for technologies such as: Vehicle-to-Everything (V2X) for assisting driving decisions and improving user convenience based on information sent by the vehicle about its location and status; New Radio Unlicensed Band (NR-U) designed to comply with various regulatory requirements in unlicensed frequency bands; NR User Equipment (UE) power saving; Non-Terrestrial Networks (NTNs) for direct satellite communication between UEs to ensure coverage in areas where they cannot communicate with terrestrial networks; and positioning.

[0005] Furthermore, standardization of air interface architectures / protocols for technologies such as: Industrial Internet of Things (IIoT) for supporting new services through interoperability and integration 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 (RACH for NR) for simplifying the random access process. Simultaneously, standardization of system architectures / services for technologies such as: 5G baseline architectures (e.g., service-based architectures or service-based interfaces) for combining Virtual Network Functions (NFV) and Software-Defined Networking (SDN) technologies; and Mobile Edge Computing (MEC) for receiving services based on UE location.

[0006] With the commercialization of 5G mobile communication systems, an exponential increase in connected devices will be added to communication networks, thus necessitating enhanced functionality and performance of 5G mobile communication systems and the integrated operation of connected devices. To this end, new research is underway on the following technologies: Extended Reality (XR) for efficient support of Augmented Reality (AR), Virtual Reality (VR), Mixed Reality (MR), etc.; 5G performance improvements and complexity reductions through the utilization of Artificial Intelligence (AI) and Machine Learning (ML); AI service support; Metaverse service support; and drone communication.

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

[0008] With all the technological activity worldwide surrounding a variety of candidate technologies from industry and academia, the momentum for 5G or New Radio (NR) mobile communications is currently growing rapidly. Candidate technologies driving 5G / NR mobile communications include massive MIMO technologies ranging from traditional cellular bands to higher frequencies to provide beamforming gain and support increased capacity, new waveforms for flexible adaptation to various services / applications with different requirements (e.g., NR Access Technologies (RAT)), new multiple access schemes for supporting massive connectivity, and more.

[0009] The above information is presented as background information only to aid in understanding this disclosure. No determination or assertion has been made as to whether any of the above content can be considered as prior art application of this disclosure. Summary of the Invention

[0010] Technical issues

[0011] With the development of communication systems, there is a need for an effective method for transmitting uplink channels or signals.

[0012] The technical subject matter claimed in this disclosure may not be limited to the above-mentioned technical subject matter, and other technical subject matter not mentioned will be clearly understood by those skilled in the art through the following description.

[0013] Technical solutions

[0014] The present disclosure is intended to at least address the aforementioned problems and / or disadvantages, and to provide at least the following advantages. Therefore, one aspect of the present disclosure is to provide an apparatus and method capable of effectively providing services in a mobile communication system.

[0015] Additional aspects will be set forth in part in the description which follows, and in part will be apparent from the description, or may be learned by practice of the presented embodiments.

[0016] A method is provided performed by a terminal in a wireless communication system. The method includes: receiving configuration information associated with subband non-overlapping full-duplex (SBFD) symbols from a base station; identifying whether one or more symbols allocated for a Physical Uplink Shared Channel (PUSCH) associated with Random Access (RA) are all SBFD symbols and do not include symbols of a Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) block; and transmitting the PUSCH to the base station if the one or more symbols allocated for the PUSCH are all SBFD symbols and do not include symbols of an SS / PBCH block, wherein the SBFD symbols are for uplink transmission using at least one of downlink symbols or flexible symbols.

[0017] According to one aspect of this disclosure, a method performed by a terminal in a wireless communication system is provided. The method includes: receiving configuration information associated with subband non-overlapping full-duplex (SBFD) symbols from a base station; identifying whether one or more symbols allocated for a Physical Uplink Shared Channel (PUSCH) associated with Random Access (RA) are all SBFD symbols and do not include symbols of a Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) block; and, if the one or more symbols allocated for the PUSCH are all SBFD symbols and do not include symbols of an SS / PBCH block, transmitting the PUSCH to the base station, wherein the SBFD symbols are for uplink transmission using at least one of downlink symbols or flexible symbols.

[0018] According to another aspect of this disclosure, a terminal for transmitting uplink channels and channels in a wireless communication system is provided. The terminal includes: a transceiver configured to receive and transmit signals; a memory including one or more storage media and storing instructions; and one or more processors communicatively connected to the transceiver and the memory, wherein the instructions, when executed individually or jointly by the one or more processors, cause the terminal to: receive configuration information associated with subband non-overlapping full-duplex (SBFD) symbols from a base station; identify whether one or more symbols allocated for a Physical Uplink Shared Channel (PUSCH) associated with Random Access (RA) are all SBFD symbols and do not include symbols of a Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) block; and, if one or more symbols allocated for the PUSCH are all SBFD symbols and do not include symbols of an SS / PBCH block, transmit the PUSCH to the base station, wherein the SBFD symbols are for uplink transmissions using at least one of downlink symbols or flexible symbols.

[0019] According to one aspect of this disclosure, a method performed by a base station in a wireless communication system is provided. The method includes: transmitting configuration information associated with subband non-overlapping full-duplex (SBFD) symbols to a terminal; and receiving a PUSCH from the terminal in the case that one or more symbols allocated for a Physical Uplink Shared Channel (PUSCH) associated with Random Access (RA) are SBFD symbols and do not include symbols of a Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) block, wherein the SBFD symbols are for uplink transmission using at least one of downlink symbols or flexible symbols.

[0020] According to one aspect of this disclosure, a base station in a wireless communication system is provided. The base station includes: a transceiver; and at least one processor connected to the transceiver and configured to: transmit configuration information associated with subband non-overlapping full-duplex (SBFD) symbols to a terminal; and receive PUSCH from the terminal in the case that one or more symbols allocated for a Physical Uplink Shared Channel (PUSCH) associated with Random Access (RA) are SBFD symbols and do not include symbols of a Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) block, wherein the SBFD symbols are for uplink transmission using at least one of downlink symbols or flexible symbols.

[0021] Other aspects, advantages, and salient features of this disclosure will become apparent to those skilled in the art from the following detailed description of various embodiments disclosed in conjunction with the accompanying drawings.

[0022] Beneficial effects

[0023] This disclosure provides an effective and efficient method for transmitting uplink channels or signals. The beneficial effects obtainable from this disclosure are not limited to those described above, and other effects not mentioned will be clearly understood by those skilled in the art from the following description. Attached Figure Description

[0024] The above and other aspects, features, and advantages of certain embodiments of the present disclosure will become more apparent from the following description taken in conjunction with the accompanying drawings, in which: Figure 1 This is a diagram illustrating the basic structure of the time-frequency domain in a wireless communication system according to an embodiment of the present disclosure; Figure 2 This is a diagram illustrating the frame, subframe, and time slot structure in a wireless communication system according to an embodiment of the present disclosure; 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; Figure 4 This is a diagram illustrating an example of the configuration of the control resource set of a downlink control channel in a wireless communication system according to an embodiment of the present disclosure; Figure 5 This is a diagram illustrating the structure of a downlink control channel in a wireless communication system according to an embodiment of the present disclosure; Figure 6 This is a diagram illustrating a method for a base station and a terminal (UE) to transmit and receive data in a wireless communication system, taking into account downlink data channel and rate matching resources, according to an embodiment of the present disclosure; Figure 7This 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; 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; Figure 9 This is a diagram illustrating an example of time-domain resource allocation in a wireless communication system according to the subcarrier spacing of the data channel and the control channel, according to an embodiment of the present disclosure; Figure 10 This is a diagram illustrating the wireless protocol structure of a base station and a UE in a wireless communication system according to embodiments of the present disclosure, under single-cell, carrier aggregation, and dual-connectivity scenarios; Figure 11 This is a diagram illustrating a random access process according to an embodiment of the present disclosure; Figure 12 This is a diagram illustrating a time division duplex (TDD) configuration and a subband non-overlapping full-duplex (SBFD) configuration according to embodiments of the present disclosure; Figure 13a and Figure 13b This is a diagram illustrating PUSCH-transferable symbols in TDD and SBFD configurations according to various embodiments of the present disclosure; Figure 14 This is a diagram illustrating a flowchart of Msg3 PUSCH transmission according to an embodiment of the present disclosure; Figure 15 This is a diagram illustrating a flowchart for determining the Msg PUSCH frequency hopping offset value according to an embodiment of the present disclosure; Figure 16 This is a diagram illustrating the structure of a UE in a wireless communication system according to an embodiment of the present disclosure; and Figure 17 This is a diagram illustrating the structure of a base station in a wireless communication system according to an embodiment of the present disclosure.

[0025] In all the accompanying drawings, the same reference numerals are always used to denote the same elements. Detailed Implementation

[0026] The following description, provided with reference to the accompanying drawings, is intended to aid in a comprehensive understanding of the various embodiments of the present disclosure as defined by the claims and their equivalents. The following description includes various specific details to aid understanding, but these are merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the various embodiments described herein without departing from the scope and spirit of the present disclosure. Furthermore, for clarity and brevity, descriptions of well-known functions and structures may be omitted.

[0027] The terms and words used in the following description and claims are not limited to their literal meaning, but are used by the inventors only to enable a clear and consistent understanding of this disclosure. Therefore, it will be apparent to those skilled in the art that the following description of various embodiments of this disclosure is provided for illustrative purposes only and is not intended to limit the disclosure as defined by the appended claims and their equivalents.

[0028] It should be understood that, unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” include plural indicators. Thus, for example, referring to “the surface of a component” includes referring to one or more such surfaces.

[0029] Various advantages and features of this disclosure, as well as its implementation methods, will become apparent from the following detailed description of embodiments with reference to the accompanying drawings. However, this disclosure is not limited to the various embodiments described below, but can be implemented in various different forms. The embodiments provided are merely intended to complete this disclosure and allow those skilled in the art to fully appreciate its scope, and this disclosure is defined by the scope of the claims. Throughout this specification, the same components will be indicated by the same reference numerals. Furthermore, in describing this disclosure, detailed descriptions of related functions or configurations that are determined to be relevant to this disclosure may unnecessarily obscure its essence, and such detailed descriptions will be omitted. Additionally, the following terms are defined in consideration of the functions in this disclosure, and these terms may be interpreted in different ways depending on the intent, practice, etc., of the user and operator. Therefore, the definitions of the terms should be interpreted based on the content of this specification.

[0030] In the following description, a base station is an entity that performs resource allocation for a terminal and can be at least one of a gNodeB, eNodeB, 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, downlink (DL) refers to the radio transmission path of a signal transmitted from the base station to the UE, and uplink (UL) refers to the radio transmission path of a signal transmitted from the UE to the base station. Furthermore, although LTE or LTE-A systems may be described below as examples, embodiments of this disclosure can be applied to other communication systems with similar technical backgrounds or channel types. For example, 5G fifth-generation mobile communication technology (New Radio (NR)) developed after LTE-A can be included in such systems, and 5G below can be a concept encompassing existing LTE, LTE-A, and other similar services. Moreover, this disclosure can be applied to other communication systems with modifications that do not significantly depart from the scope of this disclosure, as determined by a person skilled in the art.

[0031] In this context, it will be understood that each block in a flowchart and a combination of flowcharts can be executed by computer program instructions. Since these computer program instructions can be mounted on the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus, the execution of these computer program instructions by the processing of the computer or other programmable data processing apparatus creates means for performing the functions described in the blocks of the flowchart. Since these computer program instructions can also be stored in a computer-usable or computer-readable storage device of a computer or other programmable data processing apparatus to implement the functions in a particular manner, the computer program instructions stored in the computer-usable or computer-readable storage device can also produce an article of writing, including instruction means for performing the functions described in the blocks of the flowchart. Since the computer program instructions can also be mounted on a computer or other programmable data processing apparatus, performing a series of operational steps on the computer or other programmable data processing apparatus to create a process executed by the computer, thereby executing the instructions of the computer or other programmable data processing apparatus, can also provide steps for performing the functions described in the blocks of the flowchart.

[0032] Additionally, each box may indicate some of a module, section, or code, which includes one or more executable instructions for performing a specified logical function. Furthermore, it should be noted that in some alternative embodiments, the functions mentioned in the boxes occur regardless of the order. For example, two boxes shown consecutively may actually be executed simultaneously, or in reverse order depending on their corresponding functions.

[0033] In this context, the term "unit" as used in the embodiments refers to a software component or hardware component, such as a field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC), and the "unit" plays a specific role. However, the "unit" is not limited to software or hardware. A "unit" may be configured to be stored in an addressable storage medium or may be configured to reproduce one or more processors. Thus, as an example, a "unit" includes components such as software components, object-oriented software components, class components and task components, processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functionality provided in components and "units" may be combined into a smaller number of components and / or "units," or may be divided into additional components and "units." Additionally, components and "units" may be implemented as one or more central processing units (CPUs) in a playback device or secure multimedia card. Furthermore, in the embodiments, a "unit" may include one or more processors.

[0034] Wireless communication systems have evolved from providing voice-directed services in their early stages to broadband wireless communication systems that provide high-speed, high-quality packet data services, as exemplified by communication standards such as: 3GPP High-Speed ​​Packet Access (HSPA), Long Term Evolution (LTE) or Evolved Universal Terrestrial Radio Access (E-UTRA), LTE-Advanced (LTE-A) and LTE-Pro, 3GPP2 High-Rate Packet Data (HRPD) and Ultra Mobile Broadband (UMB), and IEEE 802.16e.

[0035] 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, multiple access schemes typically allocate and manipulate time-frequency resources to carry data or control information and transmit that information to each user, ensuring that the time-frequency resources do not overlap, i.e., achieving orthogonality, thereby distinguishing the data or control information for each user.

[0036] As the future communication system following LTE, 5G communication systems should support services that simultaneously meet various requirements, as they need to flexibly reflect diverse demands from users, service providers, and others. Examples of services considered for 5G communication systems include enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC).

[0037] eMBB aims to provide higher data rates than those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, from the perspective of a single base station, eMBB should be able to provide a peak data rate of 20 Gbps in the downlink and 10 Gbps in the uplink. Additionally, 5G communication systems should provide increased user-perceived UE data rates while delivering peak data rates. To meet these requirements, various transmit and receive technologies are needed, including further improved multiple-input multiple-output (MIMO) transmission technologies. Furthermore, while LTE uses a maximum transmission bandwidth of 20 MHz in the 2 GHz band to transmit signals, 5G communication systems can meet the data transmission rates required by 5G communication systems by using a wider frequency bandwidth than 20 MHz in the 3 GHz to 6 GHz band, or 6 GHz or higher.

[0038] Meanwhile, in 5G communication systems, mMTC is considered to support application services such as the Internet of Things (IoT). To efficiently deliver IoT, mMTC needs to support large-scale UE access within a cell, improve UE coverage, improve battery life, and reduce UE costs. Since IoT is attached to various sensors and devices to provide communication functions, it should be able to support a large number of UEs within a cell (e.g., 1,000,000 UEs / km²). Furthermore, due to the nature of their service, mMTC-enabled UEs may be located in shadow areas not covered by the cell, such as building basements, thus requiring wider coverage than other services provided by 5G communication systems. Because mMTC-enabled UEs should consist of low-cost UEs and their batteries are difficult to replace frequently, they may require very long battery lives, such as 10 to 15 years.

[0039] Finally, URLLC is for mission-critical cellular-based wireless communication services. Examples include remote control of robots or machines, industrial automation, unmanned aerial vehicles, telemedicine, and emergency alerts. Therefore, communication provided by URLLC should offer very low latency and very high reliability. For example, services supporting URLLC should have an air interface latency of less than 0.5 milliseconds and simultaneously have 10... -5 Or a lower packet error rate is required. Therefore, for services that support URLLC, 5G communication systems should provide shorter transmission time intervals (TTIs) than other services, and the design also needs to allocate wide resources in the frequency band to ensure the reliability of the communication link.

[0040] The three 5G 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 the different requirements of each. Of course, 5G is not limited to the three services described above.

[0041] [NR Time and Frequency Resources]

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

[0043] It should be understood that the boxes in each flowchart and combination of flowcharts can be executed by one or more computer programs including instructions. The entirety of one or more computer programs can be stored in a single memory device, or one or more computer programs can be divided into different parts and stored in multiple different memory devices.

[0044] Any of the functions or operations described herein can be processed by one processor or a combination of processors. A processor or combination of processors is a circuit system that performs processing and includes, for example, an application processor (AP, e.g., a central processing unit (CPU)), a communication processor (CP, e.g., a modem), a graphics processing unit (GPU), a neural processing unit (NPU) (e.g., an artificial intelligence (AI) chip), a Wi-Fi chip, Bluetooth, etc. ® Chips, Global Positioning System (GPS) chips, Near Field Communication (NFC) chips, connectivity chips, sensor controllers, touch controllers, fingerprint sensor controllers, display driver integrated circuits (ICs), audio codec chips, Universal Serial Bus (USB) controllers, camera controllers, image processing ICs, microprocessor units (MPUs), system-on-a-chip (SoCs), ICs, and other circuit systems.

[0045] Figure 1 This is a diagram illustrating the basic structure of the time-frequency domain in a 5G communication system according to an embodiment of the present disclosure, which is a radio resource domain in which data or control channels are transmitted.

[0046] 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 one orthogonal frequency division multiplexing (OFDM) symbol 102 in the time and one subcarrier 103 in the frequency domain. In the frequency domain, (For example, 12) consecutive REs can constitute a resource block (RB) 104. The above can be applied to a subframe 110.

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

[0048] Figure 2 An example of the structure of frame 200, subframe 201, and time slot 202 is shown. One frame 200 can be defined as 10 ms. One subframe 201 can be defined as 1 ms, so one frame 200 can consist of a total of 10 subframes 201. One time slot 202 and 203 can be defined as 14 OFDM symbols (i.e., the number of symbols per time slot). =14). A subframe 201 can consist of one or more time slots 202 and 203, and the number of time slots 202 and 203 in each subframe 201 can be determined according to the set value of the subcarrier spacing. It varies between 204 and 205. (See reference) Figure 2 , showed = 0 204 and = 1 205 is used as the setting value for the subcarrier spacing. When When =0 204, one subframe 201 can be composed of one time slot 202, and when When =1205, one subframe 201 can be composed of two time slots 203. That is, the number of time slots in each subframe... It can be based on the set value of the subcarrier spacing. And this changes, and therefore, the number of time slots per frame. It can be changed. It depends on the setting value of each subcarrier interval. of and It can be defined as shown in Table 1 below.

[0049] Table 1

[0050] [Bandwidth Component (BWP)]

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

[0052] 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.

[0053] Figure 3 An example is shown in which the UE bandwidth 300 is configured as two bandwidth portions (i.e., bandwidth portion #1 (BWP #1) 301 and bandwidth portion #2 (BWP #2) 302). The base station can configure one or more bandwidth portions for the UE, and can configure the information shown in Table 2 for each bandwidth portion.

[0054] Table 2

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

[0056] According to some embodiments, before Radio Resource Control (RRC) connection, the UE can be configured with an initial bandwidth portion (initial BWP) by the base station via the Master Information Block (MIB) for initial access. More specifically, during the initial access phase, the UE can receive configuration information of the Control Resource Set (CORESET) and a search space via the MIB, in which the Physical Downlink Control Channel (PDCCH) for receiving system information required for initial access (which may correspond to Residual System Information (RMSI) or System Information Block 1 (SIB1)) can be transmitted. The Control Resource Set and search space configured via the MIB can each be considered as identifier (ID) 0. The base station can 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 can notify the UE of the configuration information regarding the monitoring period and timing of Control Resource Set #0, i.e., the configuration information of search space #0, via the MIB. The UE can regard 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.

[0057] The bandwidth portion supported by 5G can be configured for a variety of purposes.

[0058] According to some embodiments, situations where the bandwidth supported by the UE is less than the system bandwidth can be supported through bandwidth 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 specific frequency positions within the system bandwidth.

[0059] 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 data transmission and reception using a 15 kHz subcarrier spacing and a 30 kHz subcarrier spacing for a specific UE, the two bandwidth portions can be configured as 15 kHz and 30 kHz subcarrier spacings, respectively. Different bandwidth portions can be frequency-division multiplexed, and when data is transmitted and received using a specific subcarrier spacing, the bandwidth portion configured for the corresponding subcarrier spacing can be activated.

[0060] Additionally, according to some embodiments, to reduce UE power consumption, the base station can configure bandwidth portions with different bandwidth sizes for the UE. For example, when the UE supports a very large bandwidth, such as 100 MHz, and always uses the corresponding bandwidth to send and receive data, very high power consumption may occur. In particular, using a large bandwidth of 100 MHz to monitor unnecessary downlink control channels when there is no service can be very inefficient in terms of power consumption. To reduce UE power consumption, the base station can configure a relatively small bandwidth portion for the UE, such as a 20 MHz bandwidth portion. When there is no service, the UE can perform monitoring operations in the 20 MHz bandwidth portion, and when data is generated, the UE can send and receive data in the 100 MHz bandwidth portion according to the base station's instructions.

[0061] 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, on which downlink control information (DCI) for scheduling System Information Blocks (SIBs) can be transmitted from the MIB of the Physical Broadcast Channel (PBCH). The bandwidth of the Control Resource Set configured via the MIB can be considered as the initial bandwidth portion, and the UE can receive the Physical Downlink Shared Channel (PDSCH) on which SIBs are transmitted via the configured initial bandwidth portion. Besides receiving SIBs, the initial bandwidth portion can also be used for other System Information (OSI), paging, and random access purposes.

[0062] [Bandwidth Component (BWP) Change]

[0063] When one or more bandwidth portions are configured for a UE, the base station can use the bandwidth portion indicator field in the DCI to indicate to the UE that the bandwidth portion should be changed (or switched, transformed). (See reference) Figure 3 When the currently active bandwidth portion of the UE is bandwidth portion #1 301, the base station can use the bandwidth portion indicator in the DCI to indicate bandwidth portion #2 302 to the UE, and the UE can perform a bandwidth portion change to the bandwidth portion #2 302 indicated by the bandwidth portion indicator in the received DCI.

[0064] As described above, since DCI-based bandwidth portion changes can be indicated by the DCI scheduling PDSCH or PUSCH, when the UE receives a bandwidth portion change request, the UE should be able to easily receive or transmit the PDSCH or PUSCH scheduled by the corresponding DCI within the changed bandwidth portion. To this end, the standard specifies the delay time T required when changing the bandwidth portion.BWP The requirements, for example, can be defined as shown in Table 3.

[0065] Table 3

[0066] Requests for bandwidth portion delay time can be either Type 1 or Type 2, depending on the UE's capabilities. The UE can report the supported bandwidth portion delay time types to the base station.

[0067] Based on the aforementioned requirements for bandwidth partial change delay time, when the UE receives the DCI including the bandwidth partial change indicator in time slot n, the UE can proceed no later than time slot n+T. BWP The time required for the UE to complete the change to the new bandwidth portion indicated by the bandwidth portion change indicator is reached, and data channels scheduled by the corresponding DCI can be transmitted and received in the changed new bandwidth portion. When the base station wants to use the new bandwidth portion to schedule data channels, the base station can consider the UE's bandwidth portion change delay time T. BWP This is used to determine the temporal resource allocation for the data channel. In other words, when the base station uses a new bandwidth portion to schedule the data channel, the method for determining the temporal resource allocation for the data channel can schedule the corresponding data channel after the bandwidth portion change delay time. Therefore, the UE may not expect the DCI indication indicating the bandwidth portion change to be less than the bandwidth portion change delay time T. BWP The time slot offset (K0 or K2) value.

[0068] When a UE receives a DCI indicating a partial change in bandwidth (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 UE receives the PDCCH containing the corresponding DCI to the start point of the slot indicated by the slot offset (K0 or K2) value indicated by the time domain resource allocation indicator field in the corresponding DCI. For example, when the UE receives a DCI indicating a partial change in bandwidth in slot n and the slot offset value indicated by the corresponding DCI is K, the UE may refrain from 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).

[0069] [SS / PBCH block]

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

[0071] An SS / PBCH block can represent a physical layer channel block consisting of a primary SS (PSS), a secondary SS (SSS), and a PBCH. Specifically, the PSS, SSS, and PBCH are as follows.

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

[0073] - SSS: SSS is a signal used as a reference for downlink time / frequency synchronization and provides residual cell ID information not provided by PSS. Additionally, SSS can be used as a reference signal for demodulating PBCH.

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

[0075] - 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 5 ms, and each sent SS / PBCH block can be distinguished by an index.

[0076] The UE can detect the PSS and SSS and decode the PBCH during the initial access phase. The UE can obtain the MIB from the PBCH, and based on the obtained MIB, it can be configured with a Control Resource Set (CORESET) #0 (which can correspond to the Control Resource Set index 0). Assuming the selected SS / PBCH block and the Quasi-Common Bit (QCL) of the Demodulation Reference Signal (DMRS) transmitted in Control Resource Set #0, the UE can monitor Control Resource Set #0. The UE can receive system information transmitted in Control Resource Set #0 as downlink control information. The UE can obtain the Random Access Channel (RACH) configuration information required for initial access from the received system information. Considering the selected SS / PBCH block index, the UE can send a Physical RACH (PRACH) to the base station, 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 in each SS / PBCH block the UE has selected and the Control Resource Set #0 associated with the selected block that the UE is monitoring.

[0077] [PCHC: DCI related]

[0078] Next, we will describe downlink control information (DCI) in 5G communication systems in detail.

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

[0080] DCI messages can be transmitted via the Physical Downlink Control Channel (PDCCH) through channel coding and modulation processes. The Cyclic Redundancy Check (CRC) appended to the DCI message payload can be scrambled by a Radio Network Temporary Identifier (RNTI) corresponding to the UE 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 by including it in the CRC calculation process. When a DCI message is received on the PDCCH, the UE can use the assigned RNTI to identify the CRC, and if the CRC identification result is correct, it knows that the corresponding message has been sent to the UE.

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

[0082] DCI format 0_0 can be used as a fallback DCI for scheduling PUSCH. In this case, the CRC can be scrambled by C-RNTI. DCI format 0_0 with a CRC scrambled by C-RNTI can include information such as that in Table 4.

[0083] Table 4

[0084] DCI format 0_1 ​​can be used as a non-back-off DCI for scheduling PUSCH. In this case, the CRC can be scrambled by C-RNTI. DCI format 0_1 ​​with a CRC scrambled by C-RNTI can include information such as that in Table 5.

[0085] Table 5

[0086] DCI format 1_0 can be used as a fallback DCI for scheduling PDSCH. In this case, the CRC can be scrambled by C-RNTI. DCI format 1_0 with a CRC scrambled by C-RNTI can include information such as that in Table 6.

[0087] Table 6

[0088] DCI format 1_1 can be used as a non-back-off DCI for scheduling PDSCH. In this case, the CRC can be scrambled by C-RNTI. DCI format 1_1 with a CRC scrambled by C-RNTI can include information such as that in Table 7.

[0089] Table 7

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

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

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

[0093] Figure 4 An example is shown where two control resource sets (control resource set #1 401 and control resource set #2 402) are configured in the frequency domain within a UE bandwidth portion 410 and in a time slot 420 in the time domain. Control resource sets 401 and 402 can be configured as specific frequency resources 403 within the entire UE bandwidth portion 410 in the frequency domain. One or more OFDM symbols can be configured in the time domain, which can be defined as the control resource set duration 404. Reference Figure 4 In the example shown, control resource set #1 401 is configured for a control resource set duration of 2 symbols, and control resource set #2 402 is configured for a control resource set duration of 1 symbol.

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

[0095] Table 8

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

[0097] Figure 5 This is a diagram illustrating examples of basic units constituting time and frequency resources of a downlink control channel that can be used in 5G according to embodiments of the present disclosure.

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

[0099] refer to Figure 5 In 5G, when the basic unit for allocating downlink control channels is called a Control Channel Element (CCE) 504, one CCE 504 can be composed of multiple REG 503s. Figure 5 The REG 503 shown is described as an example. A REG 503 can consist of 12 REs, and when one CCE 504 consists of 6 REG 503s, one CCE 504 can consist of 72 REs. When a downlink control resource set is configured, the corresponding area can consist of multiple CCE 504s, and a specific downlink control channel can be mapped and sent to one or more CCE 504s according to the aggregation level (AL) in the control resource set. CCE 504s in the control resource set are distinguished by numbering. In this case, the CCE 504 numbers can be assigned according to a logical mapping method.

[0100] The basic unit of the downlink control channel (i.e.) Figure 5 The REG 503 shown may include both the RE mapped to by the DCI and the region mapped to by the DMRS 505 (the reference signal used to decode the RE). Figure 5As shown, three DMRS 505s can be transmitted within one 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 for the downlink control channel. For example, when AL=L, one downlink control channel can be transmitted using L CCEs. The UE should detect the signal without knowing information about the downlink control channel and define a search space representing a set of CCEs for blind decoding. The search space is a 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 single bundle with 1, 2, 4, 8, or 16 CCEs, the UE can have multiple search spaces. The search space set can be defined as a set of search spaces under all configured aggregation levels.

[0101] 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 search the common search space of the PDCCH to receive cell common control information, such as dynamic scheduling or paging messages for system information. For example, searching the common search space of the PDCCH can be used to receive PDSCH scheduling allocation information for transmitting SIBs, including cell operator information. For 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 set of pre-committed CCEs. Searching the UE-specific search space of the PDCCH can be used to receive scheduling allocation information for UE-specific PDSCHs or PUSCHs. The UE-specific search space can be defined specifically for the UE based on the UE identifier and various system parameters.

[0102] In 5G, the base station can configure parameters for the search space used for PDCCH by the UE using higher-layer signaling (e.g., SIB, MIB, and RRC signaling). For example, the base station can configure the number of PDCCH candidates under each aggregation level L, the monitoring periodicity of the search space, the monitoring timing of each symbol in the search space's time slots, the search space type (public 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 to monitor the search space. For example, the search space may include the information in Table 9.

[0103] Table 9

[0104] 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 by X-RNTI in search space set 1 to be monitored in a common search space and DCI format B scrambled by Y-RNTI in search space set 2 to be monitored in a specific search space of the UE.

[0105] 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.

[0106] In the public search space, the following combinations of DCI format and RNTI can be monitored. Of course, the combinations are not limited to the examples below.

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

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

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

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

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

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

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

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

[0115] The specified RNTI can follow the following definitions and uses.

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

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

[0118] Configured Scheduling RNTI (CS-RNTI): UE-specific PDSCH scheduling for semi-static configuration.

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

[0120] Paging RNTI (P-RNTI): PDSCH scheduling used for sending paging requests.

[0121] System Information RNTI (SI-RNTI): PDSCH scheduling used to send system information.

[0122] Interrupt RNTI (INT-RNTI): Used to notify whether puncturing should be performed on PDSCH.

[0123] Transmit power control of PUSCH RNTI (TPC-PUSCH-RNTI): Power control command indication for PUSCH.

[0124] Transmit power control for PUCCH RNTI (TPC-PUCCH-RNTI): Power control command indication for PUCCH.

[0125] Transmit Power Control of SRS RNTI (TPC-SRS-RNTI): Power control command indication for SRS.

[0126] The DCI format specified above can follow the definitions in the examples in Table 10.

[0127] Table 10

[0128] 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 can be different. For example, when search space set #1 is configured with an X-time slot period and search space set #2 is configured with a Y-time slot period, and X and Y are different, the UE can monitor both search space set #1 and search space set #2 in a specific time slot, or monitor only search space set #1 or search space set #2 in a specific time slot.

[0129] [Rate matching / Pruning related]

[0130] The rate matching operation and the pruning operation will be described in detail below.

[0131] When the time and frequency resources A intended to transmit a random symbol sequence A overlap with random time and frequency resources B, rate matching or culling operations can be viewed as transmission and reception operations of channel A, taking into account the region where resources A and B overlap. The specific operations can follow the following steps.

[0132] Rate matching operation

[0133] The base station can map channel A only to the remaining resource area of ​​the entire resource A, excluding resource C corresponding to the area overlapping with resource B, where it wants to transmit the symbol sequence A to the UE, and then transmit channel A. For example, when symbol sequence A consists of {symbol #1, symbol #2, symbol #3, symbol #4}, resource A consists of {resource #1, resource #2, resource #3, resource #4}, and resource B consists of {resource #3, resource #5}, the base station can map symbol sequence A sequentially to {resource #1, resource #2, resource #4}, which are the remaining resources of resource A excluding {resource #3} corresponding to resource C, and then transmit symbol sequence A. Therefore, the base station can map the symbol sequence {symbol #1, symbol #2, symbol #3} to {resource #1, resource #2, resource #4} respectively, and can transmit the symbol sequence {symbol #1, symbol #2, symbol #3}.

[0134] The UE can determine resources A and B based on the base station's scheduling information for symbol sequence A, and therefore determine resource C, i.e., the area where resources A and B overlap. Assuming symbol sequence A is mapped to the remaining area of ​​resource A excluding resource C and transmitted, the UE can receive symbol sequence A. For example, when symbol sequence A consists of {symbol #1, symbol #2, symbol #3, symbol #4}, resource A consists of {resource #1, resource #2, resource #3, resource #4}, and resource B consists of {resource #3, resource #5}, assuming symbol sequence A is mapped sequentially to {resource #1, resource #2, resource #4}, which are the remaining resources of resource A excluding {resource #3} corresponding to resource C, the UE can receive symbol sequence A. Therefore, assuming symbol sequence {symbol #1, symbol #2, symbol #3} is mapped to {resource #1, resource #2, resource #4} and transmitted, the UE can perform a series of subsequent reception operations.

[0135] Delete operation

[0136] When there exists a resource C within the entire resource A that overlaps with resource B, and the base station wants to transmit symbol sequence A to the UE, the base station maps symbol sequence A to the entire resource A, but does not perform transmission in the resource area corresponding to resource C. Furthermore, it can perform transmission only for the remaining resource areas of resource A excluding resource C. For example, when symbol sequence A consists of {symbol #1, symbol #2, symbol #3, symbol #4}, resource A consists of {resource #1, resource #2, resource #3, resource #4}, and resource B consists of {resource #3, resource #5}, the base station can map symbol sequence A {symbol #1, symbol #2, symbol #3, symbol #4} to resource A {resource #1, resource #2, resource #3, resource #4} respectively, and only transmits the symbol sequence {symbol #1, symbol #2, symbol #4} corresponding to the remaining resources {resource #1#, resource #2#, resource #4} of the entire resource A excluding {resource #3} corresponding to resource C. It can omit transmitting {symbol #3} mapped to {resource #3} corresponding to resource C. Therefore, the base station can map the symbol sequence {symbol #1, symbol #2, symbol #4} to {resource #1, resource #2, resource #4} respectively, and can send the symbol sequence {symbol #1, symbol #2, symbol #4}.

[0137] The UE can determine resources A and B based on the base station's scheduling information for symbol sequence A, and therefore can determine resource C, i.e., the area where resources A and B overlap. Assuming symbol sequence A is mapped to the entire resource A but is only transmitted in the remaining area of ​​resource A excluding resource C, the UE can receive symbol sequence A. For example, when symbol sequence A consists of {symbol #1, symbol #2, symbol #3, symbol #4}, resource A consists of {resource #1, resource #2, resource #3, resource #4}, and resource B consists of {resource #3, resource #5}, the terminal can assume that symbol sequence A {symbol #1, symbol #2, symbol #3, symbol #4} is mapped to resource A {resource #1, resource #2, resource #3, resource #4} respectively, but does not send {symbol #3} mapped to {resource #3} corresponding to resource C, and assumes that symbol sequence {symbol #1, symbol #2, symbol #4} corresponding to the remaining resources {resource #1, resource #2, resource #4} in resource A excluding {resource #3} corresponding to resource C is mapped and sent, then the terminal can receive symbol sequence A {symbol #1, symbol #2, symbol #3, symbol #4}. Therefore, assuming that the symbol sequence {symbol #1, symbol #2, symbol #4} is mapped to {resource #1, resource #2, resource #4} and sent, the UE can perform a series of subsequent receiving operations.

[0138] The following describes a method for configuring rate matching resources for rate matching in a communication system. Rate matching means adjusting the signal size by taking into account the amount of resources available for signal transmission. For example, rate matching of a data channel could mean adjusting the data size without mapping the data channel to a specific time and frequency resource region and transmitting the data channel.

[0139] Figure 6 This is a diagram illustrating a method for a base station and a UE to transmit and receive data, taking into account downlink data channel and rate matching resources, according to embodiments of the present disclosure.

[0140] Figure 6 A downlink data channel (PDSCH) 601 and rate matching resource 602 are illustrated. The base station can configure one or more rate matching resources 602 for the UE via higher-layer signaling (e.g., RRC signaling). The configuration information for the rate matching resource 602 may include time-domain resource allocation information 603, frequency-domain resource allocation information 604, and periodicity information 605. Hereinafter, the bitmap corresponding to the frequency-domain resource allocation information 604 is named "First Bitmap," the bitmap corresponding to the time-domain resource allocation information 603 is named "Second Bitmap," and the bitmap corresponding to the periodicity information 605 is named "Third Bitmap." When all or part of the time and frequency resources of the scheduled data channel 601 overlap with the configured rate matching resource 602, the base station can rate match the data channel 601 with a portion of the rate matching resource 602 and transmit the data channel 601. After assuming that the data channel 601 has been rate matched with a portion of the rate matching resource 602, the UE can receive and decode the data channel 601.

[0141] The base station can use DCI to dynamically notify the UE whether to perform rate matching of the data channel with the configured rate matching resources through additional configuration (corresponding to the "rate matching indicator" in the DCI format above). Specifically, the base station can select some of the configured rate matching resources, group the selected rate matching resources into rate matching resource groups, and use a bitmap scheme to indicate to the UE via DCI whether to perform rate matching of the data channel for each rate matching resource group. 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 two bits in the DCI field to indicate to the UE via a bitmap whether to perform rate matching in RMG #1 and RMG #2 respectively. For example, the need to perform rate matching can be indicated by "1", and the need not to perform rate matching can be indicated by "0".

[0142] The methods described above for configuring rate matching resources for the UE support both "RB symbol level" and "RE level" granularity. More specifically, the following configuration methods can be followed.

[0143] RB symbol level

[0144] Up to four ratematchpatterns can be configured for each bandwidth segment for the UE via higher-level signaling, and a ratematchpattern can include the following.

[0145] Examples of reserved resources in the bandwidth portion may include resources in which the time and frequency resource regions corresponding to the reserved resources are configured by combining RB-level bitmaps and symbol-level bitmaps in the frequency domain. Reserved resources may span one or two time slots. The following periodicity and pattern can also be configured, where the time and frequency regions consisting of each RB-level and symbol-level bitmap pair are repeated.

[0146] It may include a resource region corresponding to a time-frequency domain resource region configured as a control resource set in the bandwidth portion, and a time-domain mode configured for the search space where the corresponding resource region is repeated.

[0147] RE Level

[0148] The following can be configured for the UE via higher-level signaling.

[0149] Examples of RE configuration information (lte-CRS-ToMatchAround) corresponding to LTE CRS (Cell-Specific Reference Signal or Common Reference Signal) mode may include the number of LTE CRS ports (nrofCRS-Ports) and the value of LTE-CRS-vshift (v-shift), the location information (carrierfreqDL) of the center subcarrier of the LTE carrier as a 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 Multicast Broadcast Single Frequency Network (MBSFN), etc. The UE can determine the CRS location within the NR slot corresponding to the LTE subframe based on the above information.

[0150] It may include configuration information for resource sets corresponding to one or more zero-power (ZP) CSI-RS in the bandwidth portion.

[0151] [PDSCH: Related to Frequency Domain Resource Allocation]

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

[0153] Figure 7 This is a diagram illustrating three frequency domain resource allocation methods (Type 0 7-00, Type 1 7-05, and dynamic switching (7-10)) that can be configured at higher levels in an NR wireless communication system.

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

[0155] Table 11

[0156] When a UE is configured to use only resource type 1 7-05 via higher-layer signaling, some DCIs allocated to the corresponding UE for PDSCH include those from... Frequency domain resource allocation information consisting of bits. Its conditions will be described again later. Thus, the base station can configure the starting VRB 7-20 and the length of the continuously allocated frequency domain resources from it 7-25.

[0157] When a UE is configured to use both resource type 0 and resource type 1 (7-10) via higher-layer signaling, some DCIs that allocate PDSCH to the corresponding UE include frequency domain resource allocation information. This frequency domain resource allocation information consists of bits (7-35) having the larger value of the payload for configuring resource type 0 (7-15) and the payload for configuring resource type 1 (7-20 and 7-25). The conditions will be described again later. In this case, a bit (7-30) can be added to the first part (MSB) of the frequency domain resource allocation information in the DCI, and when the corresponding bit has a value of "0", it indicates the use of resource type 0, and when the corresponding bit has a value of "1", it indicates the use of resource type 1.

[0158] [PDSCH / PUSCH: Related to time-domain resource allocation]

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

[0160] The base station can configure tables for the UE using higher-layer signaling (e.g., RRC signaling) to provide time-domain resource allocation information for downlink data channels (Physical Downlink Shared Channel (PDSCH)) and uplink data channels (Physical Uplink Shared Channel (PUSCH)). 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 (corresponding to the time interval in units of time slots between the time point of receiving the PDCCH and the time point of sending the PDSCH scheduled by the received PDCCH, denoted by K0), PDCCH-to-PUSCH time slot timing (corresponding to the time interval in units of time slots between the time point of receiving the PDCCH and the time point of sending the PUSCH scheduled by the received PDCCH, denoted by K2), information regarding the position and length of the starting 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.

[0161] Table 12

[0162] Table 13

[0163] 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., the entry can be indicated by the "Time-domain Resource Allocation" field in the DCI). The UE can obtain the time-domain resource allocation information for PDSCH or PUSCH based on the DCI received from the base station.

[0164] 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.

[0165] refer to Figure 8 The base station can indicate the temporal location of PDSCH resources by using the subcarrier spacing (SCS) (μPDSCH, μPDCCH) and scheduling offset (K0) values ​​of the data and control channels configured by higher layers, as well as the OFDM symbol start position 8-00 and length 8-05 within a time slot dynamically indicated by DCI.

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

[0167] refer to Figure 9 When the subcarrier spacing of the data channel and the control channel is the same (9-00, μPDSCH=μPDCCH), the time slot numbers used for data and control are the same. Therefore, the base station and the 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 (9-05, ... PDSCH = When using PDCCH, the time slot numbers used for data and control are different, so the base station and UE can generate a scheduling offset based on the subcarrier spacing of PDCCH according to the predetermined time slot offset K0.

[0168] [PUSCH: Transmission Scheme Related]

[0169] Next, the scheduling scheme for PUSCH transmissions will be described. PUSCH transmissions can be dynamically scheduled using DCI with UL authorization, or operated using configured authorization type 1 or type 2. Dynamic scheduling instructions for PUSCH transmissions can be implemented using DCI format 0_0 or 0_1.

[0170] A configured license type 1 PUSCH transfer can be semi-statically configured via higher-layer signaling by receiving a configuredGrantConfig that includes the rrc-ConfiguredUplinkGrant from Table 14, without receiving the UL grant in the DCI. After receiving a configuredGrantConfig via higher-layer signaling that does not include the rrc-ConfiguredUplinkGrant from Table 14, a configured license type 2 PUSCH transfer can be semi-persistently scheduled via the UL grant in the DCI. When a PUSCH transfer operates with the configured grant, the parameters applied to the PUSCH transfer are applied via the configuredGrantConfig, which is the higher-layer signaling from Table 14, except for the scaling of dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, and UCI-OnPUSCH provided by the higher-layer signaling pusch-Config from Table 15. When the transformPrecoder is provided to the UE in the configuredGrantConfig, which is the higher-layer signaling in Table 14, the UE applies tp-pi2BPSK in the pusch-Config in Table 15 for PUSCH transmissions via the configured permitted operation.

[0171]

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

[0173] As described above, PUSCH transmissions can be dynamically scheduled via DCI format 0_0 or 0_1, and semi-statically configured with the configured permissions. If the UE is instructed to schedule a PUSCH transmission via DCI format 0_0, the UE performs beam configuration for the PUSCH transmission using the pucch-spatialRelationInfoID corresponding to the UE-specific PUCCH resource corresponding to the smallest ID within the uplink BWP active in the serving cell. In this case, the PUSCH transmission is based on a single antenna port. The UE does not expect to schedule PUSCH transmissions via DCI format 0_0 within a BWP in which PUCCH resources including pucch-spatialRelationInfo are not configured. If the UE is not configured with txConfig in pusch-Config of Table 15, the UE does not expect scheduling via DCI format 0_1.

[0174] Table 15

[0175] Next, codebook-based PUSCH transmission will be described. Codebook-based PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1 and operated semi-statically with configured permissions. When codebook-based PUSCH is dynamically scheduled via DCI format 0_1 ​​or semi-statically configured with configured permissions, the UE determines the precoder for PUSCH transmission based on the SRS Resource Indicator (SRI), Transport Precoding Matrix Indicator (TPMI), and transport rank (number of PUSCH transport layers).

[0176] In this scenario, the SRI can be indicated via the SRS Resource Indicator field in the DCI, or configured via srs-ResourceIndicator as higher-layer signaling. When transmitting codebook-based PUSCH, the UE can be configured with at least one SRS resource and up to two SRS resources. When providing an 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 before the PDCCH including the corresponding SRI. Additionally, the TPMI and transport rank can be given via the precoding information and layer number fields in the DCI, or configured via precodingAndNumberOfLayers as higher-layer signaling. TPMI is used to indicate the precoder applied to the PUSCH transmission. When the UE is configured with one SRS resource, TPMI indicates the precoder to be applied to the configured SRS resource. When the UE is configured with multiple SRS resources, TPMI indicates the precoder to be applied to the SRS resource indicated by the SRI.

[0177] The precoder to be used for PUSCH transmission is selected from the uplink codebook having the same number of antenna ports as the nrofSRS-Ports value in the SRS-Config, which serves as higher-layer signaling. In codebook-based PUSCH transmission, the UE determines the codebook subset based on TPMI and the codebookSubset in the pusch-Config, which serves as higher-layer signaling. The codebookSubset in the pusch-Config, which serves as higher-layer signaling, can be configured as one of "fullAndPartialAndNonCoherent", "partialAndNonCoherent", or "nonCoherent" based on the UE capabilities reported by the UE to the base station. When the UE reports "partialAndNonCoherent" as a UE capability, the UE does not expect the value of the codebookSubset, which serves as higher-layer signaling, to be configured as "fullyAndPartialAndNonCoherent". Conversely, when the UE reports "nonCoherent" as a UE capability, the UE does not expect the value of the codebookSubset, which serves as higher-layer signaling, to be configured as either "fullyAndPartialAndNonCoherent" or "partialAndNonCoherent". When nrofSRS-Ports in SRS-ResourceSet, used as higher-layer signaling, indicates two SRS antenna ports, the UE does not expect the value of codebookSubset, used as higher-layer signaling, to be configured as "partialAndNonCoherent".

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

[0179] The UE can send one or more SRS resources included in an SRS resource set whose usage value is set to a "codebook" according to higher-layer signaling to the base station. The base station can select one of the SRS resources sent by the UE and use the transmission beam information of the corresponding SRS resource to instruct the UE to perform PUSCH transmission. In this case, in codebook-based PUSCH transmission, the SRI is used as information for selecting an SRS resource and is included in the DCI. Additionally, the base station includes information in the DCI indicating the TPMI and rank to be used by the UE for PUSCH transmission. The UE performs PUSCH transmission using the SRS resource indicated by the SRI by applying a precoder indicated by the indicated rank and the TPMI based on the transmission beam of the corresponding SRS resource.

[0180] Next, non-codebook-based PUSCH transport will be described. Non-codebook-based PUSCH transport can be dynamically scheduled using DCI format 0_0 or 0_1, and can be operated semi-statically with configured permissions. When at least one SRS resource is configured in an SRS resource set whose usage value in the SRS-ResourceSet (as higher-layer signaling) is configured as "nonCodebook", the UE can be scheduled using non-codebook-based PUSCH transport via DCI format 0_1.

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

[0182] If the value of resourceType in the SRS-ResourceSet, used as higher-layer signaling, is configured as "aperiodic," the associated NZP CSI-RS is indicated by the SRS request as 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 when 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. Additionally, when the value of the SRS request indicates the presence of an NZP CSI-RS, the corresponding NZP CSI-RS is located in a time slot in which a PDCCH including the SRS request field was transmitted. In this case, the TCI state configured for the scheduled subcarrier is not configured as QCL-TypeD.

[0183] 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 SRS-ResourceSet as higher-layer signaling. For non-codebook-based transmissions, the UE does not expect to configure the spatialRelationInfo as an SRS resource and the associated CSI-RS in the SRS-ResourceSet as higher-layer signaling together.

[0184] When multiple SRS resources are configured, the UE can determine the precoder and transmission rank to be applied to PUSCH transmission based on the SRI indicated by the base station. In this case, the SRI can be indicated by the SRS resource indicator field in the DCI, or configured by the srs-ResourceIndicator as higher-layer signaling. Similar to the codebook-based PUSCH transmission described above, when the SRI is provided to the UE 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 that can be transmitted simultaneously in the same symbol within an SRS resource set is determined by the UE capability 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 SRS-ResourceSet as higher-layer signaling is configured as "nonCodebook", and up to four SRS resources can be configured for non-codebook-based PUSCH transmission.

[0185] 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 sending one or more SRS resources in the corresponding SRS resource set based on measurements taken upon receiving the corresponding NZP-CSI-RS. When the UE sends one or more SRS resources in an SRS resource set where usage is configured as "nonCodebook", the UE applies the calculated precoder, 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 express a combination of one or more SRS resources, and the SRI is included in the DCI. In this case, the number of SRS resources indicated by the SRI sent by the base station can be the number of transport layers of the PUSCH, and the UE sends the PUSCH by applying the precoder used for SRS resource transmission to each layer.

[0186] [CA / DC related]

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

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

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

[0190] - User data transmission function (transmission of user plane data)

[0191] - Mapping function between QoS flows and data radio bearers (DRBs) for both uplink and downlink (Mapping between QoS flows and DRBs for both DL and UL)

[0192] - The function of marking QoS flow IDs in both uplink and downlink (marking QoS flow IDs in both DL packets and UL packets)

[0193] - For the uplink SDAP protocol data unit (PDU) function of mapping reflective QoS streams to data bearers (UL SDAP PDU reflective QoS stream to DRB mapping)

[0194] For SDAP layer entities, RRC messages can be used to configure whether the UE uses the SDAP layer entity header or whether to use the SDAP layer entity's functionality for each PDCP layer entity, each bearer, or each logical channel. When the SDAP header is configured, the UE can indicate the NAS QoS reflection configuration 1-bit indicator (NAS reflective QoS) and AS QoS reflection configuration 1-bit indicator (AS reflective QoS) in the SDAP header to update or reset the uplink and downlink QoS flow and data bearer mapping information. The SDAP header can include QoS flow ID information indicating QoS. QoS information can be used for data processing priority, scheduling information, etc., to support smooth service.

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

[0196] - Header compression and decompression functions (Header compression and decompression: Robust header compression (ROHC) only)

[0197] - User data transfer function (transfer of user data)

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

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

[0200] - Reordering function (PDCP PDU reordering for reception)

[0201] - Duplicate detection function (duplicate detection of lower-level service data units (SDUs))

[0202] - Retransmission function (PDCP SDU retransmission)

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

[0204] - Timer-based SDU discarding function (timer-based SDU discarding in the uplink)

[0205] The reordering function of the aforementioned NR PDCP entity refers to the function of reordering PDCPPDUs received from the lower layer based on the PDCP sequence number (SN), and may include the function of delivering data to the higher layer in the reordered order. Alternatively, the reordering of the NR PDCP entity may include the function of delivering data directly regardless of order, the function of recording lost PDCP PDUs by reordering PDCPPDUs, the function of reporting the status of lost PDCP PDUs to the transmitting side, and the function of requesting retransmission of lost PDCP PDUs.

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

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

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

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

[0210] - Automatic Repeat Request (ARQ) function (error correction via ARQ)

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

[0212] - Re-segmentation function (re-segmentation of RLC data PDUs)

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

[0214] - Duplicate detection function (duplicate detection)

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

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

[0217] -RLC Reconstruction Function (RLC Reconstruction)

[0218] The sequential delivery function of the aforementioned NR RLC entity refers to the function of delivering RLC SDUs received from the lower layer to the higher layer in sequence. When a single original RLC SDU is segmented into multiple RLC SDUs and received, the sequential delivery function of the NR RLC entity can include the function of reassembling and delivering these RLC SDUs, the function of reordering received RLC PDUs based on the RLC SN or PDCP SN, the function of recording lost RLC PDUs through reordering, 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 the NR RLC entity can include the function of delivering only the RLCSDUs up to the lost RLC SDU in sequence to the higher layer when a lost RLC SDU exists, or the function of delivering all RLC SDUs received before the timer started in sequence to the higher layer even if a lost RLCSDU exists, if a predetermined timer has expired. Alternatively, the sequential delivery function of the NR RLC entity may include the ability to sequentially deliver all received RLC SDUs to the higher layer, even if lost RLC SDUs exist, if a pre-defined timer has expired. Additionally, RLC PDUs may be processed in the order they were received (arrival order, regardless of sequence number) and delivered to the PDCP entity regardless of the order (out-of-order delivery), or, in the case of segmentation, they may be reconstructed into a single complete RLC PDU by receiving segments stored in a buffer or to be received later, processed, and delivered to the PDCP entity. The NR RLC layer may not include concatenation functionality, and concatenation may be performed in the NR MAC layer or replaced by multiplexing functionality in the NR MAC layer.

[0219] The out-of-order delivery function of the aforementioned NR RLC entity refers to the function of directly delivering RLC SDUs received from lower layers to higher layers regardless of their order. When a single original RLC SDU is segmented into multiple RLC SDUs and received, the in-order delivery function of the NR RLC entity may include the function of reassembling and delivering these RLC SDUs, and may also include the function of storing the RLC SN or PDCP SN of the received RLCPDUs and sorting them to record any lost RLC PDUs.

[0220] NR MAC S40 and S55 can be associated with multiple NR RLC layer entities configured in a UE, and the main functions of NR MAC can include some of the following functions.

[0221] - Mapping function (mapping between logical channels and transmission channels)

[0222] - Multiplexing / demultiplexing function (MAC SDU multiplexing / demultiplexing)

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

[0224] - Hybrid ARQ (HARQ) functionality (error correction via HARQ).

[0225] - Priority processing function between logical channels (priority processing between logical channels of a UE)

[0226] - Priority handling function between UEs (with the help of dynamically scheduled priority handling between UEs)

[0227] - Multimedia Broadcast Multicast Service (MBMS) Service Identification Function (MBMS Service Identifier)

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

[0229] - Fill function (Fill)

[0230] The NR PHY layers S45 and S50 can perform the following operations: channel coding and modulation of higher-layer data, conversion of higher-layer data into OFDM symbols and transmission of OFDM symbols via a wireless channel, or demodulation and channel decoding of OFDM symbols received via a wireless channel and delivery of OFDM symbols to higher layers.

[0231] The wireless protocol architecture can have various detailed structures that vary depending on the carrier (or cell) operation scheme. For example, when the base station transmits data to the UE based on a single carrier (or cell), the base station and the UE use a protocol architecture with a single structure at each layer, as in S00. On the other hand, when the base station transmits data to the UE based on carrier aggregation (CA) using multiple carriers in a single transmit and receive point (TRP), the base station and the UE use a protocol architecture with a single structure up to RLC, as in S10, but the PHY layer is multiplexed through the MAC layer. As another example, when the base station transmits data to the UE based on dual connectivity (DC) using multiple carriers in multiple TRPs, the base station and the UE use a protocol architecture with a single structure up to RLC, as in S20, but the PHY layer is multiplexed through the MAC layer.

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

[0233] In the following, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The content of this disclosure is applicable to frequency division duplex (FDD) and TDD systems. In the present disclosure below, higher-layer signaling (or upper-layer signaling) is a signal transmission method in which the base station uses the downlink data channel of the physical layer to send signals to the UE or the UE uses the uplink data channel of the physical layer to send signals to the base station, and may also be referred to as RRC signaling, PDCP signaling, or Media Access Control (MAC) control element (CE) (MAC control element (MAC CE)).

[0234] In the following disclosure, when determining whether cooperative communication has been applied, the UE may use various methods, such as assigning a PDCCH with a specific format to a PDSCH with cooperative communication applied, assigning a PDCCH with a specific indicator to a PDSCH with cooperative communication applied including a specific indicator indicating whether cooperative communication has been applied, assigning a PDCCH with a PDSCH with cooperative communication applied being scrambled by a specific RNTI, or assuming that cooperative communication has been applied in a specific interval indicated by a higher layer. In the following, for ease of description, the case where the UE receives a PDSCH with cooperative communication applied under conditions similar to those described above will be referred to as the NC-JT case.

[0235] In the following, in this disclosure, determining the priority between A and B can be mentioned in a variety of ways, such as selecting the one with higher priority to perform the operation corresponding to the selected priority according to a predetermined priority rule, or omitting or discarding the operation of the one with lower priority.

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

[0237] In the following, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In this context, a base station is an entity that performs resource allocation for a terminal and may be at least one of a gNodeB, gNB, eNodeB, Node B, base station (BS), radio access unit, base station controller, or node on a network. A terminal may include a user equipment (UE), mobile station (MS), cellular phone, smartphone, computer, or multimedia system capable of performing communication functions. In the following, a 5G communication system will be used as an example to describe embodiments of the present disclosure, but embodiments of the present disclosure can be applied to other communication systems with similar technical backgrounds or channel types. For example, LTE or LTE-A mobile communications and mobile communication technologies developed after 5G may be included therein. Furthermore, embodiments of the present disclosure can be applied to other communication systems with modifications that do not significantly depart from the scope of the present disclosure, as determined by a person skilled in the art. The content of this disclosure can be applied to FDD and TDD systems.

[0238] Furthermore, in describing this disclosure, detailed descriptions of relevant functions or configurations related to this disclosure will be omitted where it is determined that such detailed descriptions might unnecessarily obscure the essence of this disclosure. Additionally, the following terms are defined in consideration of the functions in this disclosure, and these terms may be interpreted in different ways depending on the intent and practice of the user and operator. Therefore, the definitions of the terms should be interpreted based on the content of this specification.

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

[0240] -MIB (Master Information Block)

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

[0242] -RRC (Radio Resource Control)

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

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

[0245] -PDCCH (Physical Downlink Control Channel)

[0246] -DCI (Downlink Control Information)

[0247] -UE-specific DCI

[0248] -Group Public DCI

[0249] -Public DCI

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

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

[0252] -PUCCH (Physical Uplink Control Channel)

[0253] -UCI (Uplink Control Information)

[0254] In the following, in this disclosure, determining the priority between A and B can be mentioned in a variety of ways, such as selecting the one with higher priority to perform the operation corresponding to the selected priority according to a predetermined priority rule, or omitting or discarding the operation of the one with lower priority.

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

[0256] [Random Access Procedure in SBFD]

[0257] Meanwhile, Subband Non-overlapping Full-Duplex (SBFD) has been introduced in 3GPP as a new duplexing method based on NR. SBFD is a technique that utilizes some downlink resources as uplink resources in TDD frequency bands (spectrums) at frequencies of 6 GHz or lower, or frequencies of 6 GHz or higher. SBFD receives as many uplink transmissions from the UE as the increased uplink resources, thereby expanding the UE's uplink coverage, and receives feedback from the UE regarding downlink transmissions in the expanded uplink resources, thereby reducing feedback latency. In this disclosure, for convenience, a UE that receives information from the base station regarding whether SBFD is supported and performs uplink transmissions in some downlink resources can be referred to as an SBFD UE (a UE supporting SBFD). To define SBFD schemes in the specification and allow SBFD UEs to determine whether SBFD is supported in a specific cell (or frequency, band), the following schemes can be considered.

[0258] According to an embodiment, as a first approach, in order to define SFFD in addition to the existing unpaired spectrum (or time division duplex (TDD)) or paired spectrum (or frequency division duplex (FDD)) frame structure types, another frame structure type (e.g., frame structure type 2) can be introduced. Frame structure type 2 can be defined as being supported in a specific frequency or band, or the base station can indicate to the UE whether SBFD is supported through system information. The SBFD UE can receive system information from the base station, including whether SBFD is supported, to determine whether SBFD is supported in a specific cell (or frequency, band).

[0259] In the second embodiment, it can be indicated 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 the second embodiment, it can be defined whether SBFD is additionally supported in a specific frequency or band of existing unpaired spectrum, or the base station can indicate to the UE whether SBFD is supported via system information. The UE can receive system information from the base station, including whether SBFD is supported, to determine whether SBFD is supported in a specific cell (or frequency, band).

[0260] In the first and second schemes described above, information regarding whether SBFD is supported can be information that indirectly indicates whether SBFD is supported in the following ways (e.g., as described below). Figure 12 SBFD resource configuration information in: In addition to the TDD uplink (UL)-downlink (DL) resource configuration information that configures the downlink slot (or symbol) resources and uplink slot (or symbol) resources of TDD, some configurations in the downlink resources are also treated as uplink resources; or it may be information that directly indicates whether SBFD is supported.

[0261] In this disclosure, the SBFD UE can receive a Synchronization Signal Block (SSB) for accessing the cell (or base station) during initial cell access to obtain cell synchronization. The process for obtaining 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.

[0262] The system information used to send information about whether SBFD is supported can be system information that is distinct from and sent separately from the system information of UEs within the cell that support different versions of the specification (e.g., existing TDD UEs). The SBFD UE can obtain all or part of the system information sent separately from the existing TDD UE's system information to determine whether SBFD is supported. When the SBFD UE only obtains the system information of the existing TDD UE or obtains system information indicating that SBFD is not supported, the SBFD UE can determine that the cell (or base station) only supports TDD.

[0263] When the system information of a UE supporting different versions of the specification (e.g., an existing TDD UE) includes information about whether it supports SBFD, this information can be inserted at the end to avoid affecting the existing TDD UE's acquisition of system information. If the SBFD UE does not obtain the inserted information about whether it supports SBFD or obtains information indicating that it does not support SBFD, the SBFD UE can determine that the cell (or base station) only supports TDD.

[0264] When the system information of a UE supporting different versions of the specification (e.g., an existing TDD UE) includes information about whether it supports SBFD, this information can be transmitted via PDSCH to avoid affecting the existing TDD UE's acquisition of system information. That is, a UE that does not support SBFD can receive a first SIB (or SIB1) containing existing TDD-related system information via a first PDSCH. A UE that supports SBFD can receive a first SIB (or SIB) containing existing TDD-related system information via a first PDSCH and a second SIB containing SBFD-related system information via a second PDSCH. Here, the first and second PDSCHs can be scheduled by the first and second PDCCHs, and the cyclic redundancy check (CRC) codes of the first and second PDCCHs can be scrambled using the same RNTI (e.g., SI-RNTI). A search space for monitoring the second PDCCH can be obtained from the system information of the first PDSCH, and if no search space is obtained (i.e., if the system information in the first PDSCH does not include information about the search space), the second PDCCH can be received in the same search space as the first PDCCH.

[0265] As described above, when the SBFD UE determines that the cell (or base station) only supports TDD, the SBFD UE can perform a random access procedure and send and receive data / control signals in the same manner as existing TDD UEs.

[0266] The base station can configure separate random access resources for each of the existing TDD UEs or SBFD UEs (e.g., SBFD UEs supporting full-duplex communication and SBCD UEs supporting half-duplex communication), and send the configuration information of the random access resources (control information or time-frequency resource configuration information indicating that it can be used for PRACH) to the SBFD UEs via system information. The system information used to send information about the random access resources can be system information that is different from and sent separately from the system information of UEs supporting different versions of specifications within the cell (e.g., existing TDD UEs).

[0267] The base station can configure random access resources for the TDD UE and separately configure random access resources for the SBFD UE. Here, the SBFD UE can use the random access resources of the TDD UE, or it can choose not 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 of the SBFD UE.

[0268] The base station can indicate to the SBFD UE whether the SBFD UE can use the random access resources of the TDD UE. This indication can be made by including the random access resources in the SIB. That is, the SIB can configure the individual random access resources for the SBFD UE, and along with this configuration, it can indicate whether the random access resources for the TDD UE can be used. The random access resources can be indicated by a single bit. If the single bit is "0" (or FALSE), it indicates to the SBFD UE that the random access resources for the TDD UE cannot be used. If the single bit is "1" (or TRUE), it indicates to the SBFD UE that the random access resources for the TDD UE can be used.

[0269] The base station can determine the type of UE attempting to access the cell based on the random access resources used by the UE. For example, an SBFD UE can transmit PRACH using its own random access resources, and the base station can determine that the SBFD UE is attempting to access the cell upon receiving the PRACH. Similarly, a TDD UE can transmit PRACH using its own random access resources, and the base station can determine that the TDD UE is attempting to access the cell upon receiving the PRACH. For reference, when an SBFD UE is allowed to transmit PRACH using its own random access resources, it is unclear whether the type of the UE transmitting the PRACH is a TDD UE or an SBFD UE. In this case, the base station can assume that the UE type is always a TDD UE.

[0270] When the base station determines that the UE is an SBFD UE, the base station can schedule Msg2, Msg3, Msg4, etc., for the UE based on the uplink subband configuration. That is, when the base station schedules the reception of Msg2 and Msg4 for the UE, it can schedule Msg2 and Msg4 to be received outside the uplink subband (when the UE receives a PDSCH including Msg2 and Msg4, the PDSCH is received in frequency resources outside the uplink subband). When the base station schedules Msg3 PUSCH for the UE, Msg3PUSH can be scheduled to be transmitted within the uplink subband.

[0271] When the base station determines that the UE is a TDD UE, it can choose not to use the uplink subband configuration when scheduling Msg2, Msg3, and Msg4. In other words, even if the uplink subband is configured in the downlink symbol or flexible symbol, the base station can assume that the UE may not obtain the uplink subband configuration information. When the base station schedules Msg3 PUSCH for the UE, Msg3 PUSCH can be scheduled in the flexible symbol or uplink symbol. In other words, when the base station determines that the UE is a TDD UE, Msg3 PUSCH may not be scheduled in the uplink subband.

[0272] Alternatively, instead of configuring a separate random access resource for the SBFD UE, the base station can configure a common random access resource for all UEs in the cell. In this case, the configuration information of the random access resource can be sent to all UEs in the cell via system information, and the SBFD UE that has received the system information can perform random access on the random access resource. Afterward, the SBFD UE can complete the random access procedure and enter RRC connection mode to send and receive data to and from the cell. After entering RRC connection mode, the SBFD UE can receive higher-layer signals or physical signals from the base station, which can determine that some frequency resources in the downlink time resources have been configured as uplink resources, and can perform SBFD operations, such as sending uplink signals in the uplink resources.

[0273] When an SBFD UE determines that the cell supports SBFD, it can notify the base station that the UE attempting to access the cell is an SBFD UE by sending capability information to the base station. This capability information includes at least one of the following: whether the UE supports SBFD, whether the UE supports full-duplex or half-duplex communication, and the number of transmit or receive antennas that the UE has (or supports). Alternatively, if half-duplex communication support is the basic implementation of the SBFD UE, the support for half-duplex communication can be omitted from the capability information. The SBFD UE's report on capability information can be submitted to the base station through the random access procedure, after the random access procedure is completed, or after entering RRC connection mode to send and receive data from the cell.

[0274] SBFD UEs can support immediate execution of half-duplex communication (either uplink transmission or downlink reception only), like existing TDD UEs, or support immediate execution of full-duplex communication (both uplink transmission and downlink reception). Therefore, SBFD UEs can report their capability to the base station whether they support half-duplex or full-duplex communication. Following this report, the base station can configure the SBFD UE to use either half-duplex or full-duplex communication for transmitting and receiving data. When an SBFD UE reports its half-duplex communication capability to the base station, since it typically lacks a duplexer, it may need to switch between transmission and reception intervals to change the radio frequency (RF) when operating in FDD or TDD mode.

[0275] Typically, a UE can establish a radio link with the network through a random access procedure based on synchronization and system information acquired during the cell search process. Random access can use either contention-based or contention-free schemes. A contention-based random access scheme can be used when the UE performs cell selection and reselection during the initial access phase of a cell, for example, when moving from an RRC_IDLE state to an RRC_CONNECTED state. In the case of handover or location measurement, a contention-free random access scheme can be used to rebuild uplink synchronization when downlink data arrives.

[0276] Figure 11 This is a diagram illustrating a random access procedure in a wireless communication system according to an embodiment of the present disclosure.

[0277] refer to Figure 11The example illustrates a contention-based random access procedure. Additionally, although not shown, the base station can transmit synchronization blocks as described in the above embodiments. In this case, the base station can use beam scanning to periodically transmit synchronization blocks. For example, the base station can use up to 64 different beams to transmit synchronization blocks including PSS / SSS (synchronization signals) and broadcast channel (PBCH) signals for up to 5 ms, and use different beams to transmit multiple synchronization blocks. The UE can detect (select) the synchronization block with the optimal beam direction (e.g., the beam direction with the strongest received signal strength or greater than a predetermined threshold) and use the Physical Random Access Channel (PRACH) resource associated with the detected synchronization 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, Msg1) to the base station. The base station receiving the random access preamble can measure the transmission delay value between the UE and the base station and adjust uplink synchronization.

[0278] Specifically, the UE can transmit a random access preamble randomly selected from a set of random access preambles previously provided by the system information. The initial transmission power of the random access preamble can be determined based on the path loss between the base station and the UE as measured by the UE. Furthermore, the UE can determine the transmission beam direction (or transmission beam or beam) of the random access preamble based on the synchronization signal block received from the base station, and transmit the random access preamble by applying the determined transmission beam direction.

[0279] In the second step 1102, the base station may send a response (Random Access Response RAR, or message 2 (Msg2)) to the UE in response to the detected random access attempt. The base station may send an uplink transmission timing control command to the UE based on the transmission delay value measured from the random access preamble received in the first step. Additionally, the base station may send uplink resource and power control commands to be used by the UE as scheduling information. The scheduling information may include control information for the uplink transmission beam for the UE. The RAR is transmitted via the PSBCH and may include at least one of the following information.

[0280] - Index of random access preamble sequence detected by the network (or base station)

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

[0282] -Uplink scheduling permission

[0283] -Timing Advance Value

[0284] If, in the second step 1102, the UE does not receive the RAR (Rate Information) as message 3 from the base station within a predetermined time, the first step 1101 can be executed again. When the first step is executed again, the UE can increase the transmission power (e.g., power ramp) of the random access preamble by a predetermined step and transmit the random access preamble, thereby increasing the probability that the base station receives the random access preamble.

[0285] In step 1103, the UE can use the uplink resources allocated in step 1102 to send uplink information (scheduled transmissions, message 3, etc.) to the base station via an uplink data channel (Physical Uplink Shared Channel (PUSCH)). This uplink information includes its UE identifier (e.g., UE contention resolution identifier) ​​(or, if the UE already has a valid UE identifier (C-RNTI) in the cell before the random access procedure begins, a valid UE identifier). The PUSCH can be referred to as Message 3 PUSCH (Msg3 PUSCH). The transmission timing of the uplink data channel used to send Message 3 can follow the uplink transmission timing control command received from the base station in step 1102. Additionally, the transmission power of the uplink data channel used to send Message 3 can be determined by considering the power control command received from the base station in step 1102 and the power ramp value of the random access preamble. The uplink data channel used to send Message 3 can be the initial uplink data signal sent by the UE to the base station after the UE sends the random access preamble.

[0286] Finally, in step 1104, if the base station determines that the UE has performed random access without conflicting with another UE, the base station may send a message (contention resolution message (CR message) or message 4) to the corresponding UE, which includes the UE identifier that has already sent uplink data in step 1103.

[0287] In this regard, when multiple UEs receive the same TC-RNTI in step 1102, in step 1103, each of the multiple UEs that received the same TC-RNTI can send message 3, which includes its own UE identifier (UE contention resolution identifier), to the base station. The base station can then send message 4 (CR message), which includes one of the multiple UE identifiers, for contention resolution. When a UE receives message 4 (CR message), which includes its own UE identifier, from the base station in step 1104 (or when message 3, which includes the UE identifier (C-RNTI), is sent in step 1103 and UE-specific control information, including a CRC based on the UE identifier (C-RNTI), is received via PDCCH in step 1104), the UE can determine that random access was successful. Therefore, among the multiple UEs that have received the same TC-RNTI from the base station, the UE whose UE identifier is included in message 4 (CR message) can recognize that contention has been successful. Then, the UE can send an indication message 4, indicating whether it has been successfully received, to the base station via the uplink control channel (physical uplink control channel, PUCCH) to indicate whether it has been successfully received.

[0288] If, in step 1103, the data transmitted by the UE conflicts with data from another UE and the base station fails to receive a data signal from the UE, the base station may cease transmitting data to the UE. Therefore, if, in step 1104, the UE fails to receive data transmitted from the base station within a specific time interval, it can be determined that the random access procedure has failed and can restart from step 1101.

[0289] As described above, in the first step 1101 of the random access procedure, the UE can transmit a random access preamble on the PRACH. Each cell has 64 available preamble sequences, and depending on the transmission format, four long preamble formats and nine short preamble formats can be used. The UE can generate the 64 preamble sequences using the root sequence index and cyclic shift value, which are used as system information signaling, and can randomly select one sequence to use as the preamble.

[0290] The base station 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 random access resource configuration information, such as control information (or configuration information) indicating the time and frequency resources that can be used for PRACH. The frequency resources for PRACH transmission can indicate the starting RB point for transmission to the UE, and the number of RBs used can be determined based on the preamble format transmitted via PRACH and the applied subcarrier spacing. The time resources for PRACH transmission can be notified via PRACH configuration indices 0 to 255, such as the predetermined PRACH configuration period, the subframe index and start symbol including the PRACH timing (which can be used interchangeably with timing), and the number of PRACH timings in the time slot, as shown in Table 16 below. The UE can determine the validity of the PRACH timing indicated by the PRACH configuration index and only determine valid PRACH timings as those that can transmit random access preambles. By using the PRACH configuration index, the random access configuration information included in the SIB, and the index of the SSB selected by the UE, the UE can identify the time and frequency resources used to send the random access preamble, and send the selected sequence as a preamble to the base station.

[0291] Table 16

[0292] According to embodiments of this disclosure, when an SBFD UE determines the validity of a PRACH timing through a PRACH configuration index and an SBFD configuration for performing PRACH transmissions, and performs PRACH transmissions through a PRACH timing determined to be valid, a process may be required for the SBFD UE when the valid PRACH timing and downlink reception overlap.

[0293] Therefore, reference Figure 8 , Figure 9 and Figure 10 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 valid PRACH timing and downlink reception are configured or scheduled to occur simultaneously.

[0294] Figure 12 This is a diagram illustrating an example of a wireless communication system according to an embodiment of the present disclosure, wherein the SBFD operates in the TDD spectrum.

[0295] refer to Figure 12Part (a) illustrates the operation of TDD in a specific frequency band. In a TDD-operating cell, 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 the existing TDD UE or SBFD UE and TDD.

[0296] 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 consisting entirely of downlink symbols, "U" represents a time slot consisting entirely of uplink symbols, and "S" represents a time slot that is neither "D" nor "U," meaning a time slot that includes downlink symbols, uplink symbols, or flexible symbols. For convenience, it can be assumed that S consists of 12 downlink symbols and 2 flexible symbols. The DDDSU time slot format can be repeated based on the TDD UL-DL resource configuration information. (See reference...) Figure 12 The repetition period of the TDD configuration can be exemplified as 5 time slots (5 ms for 15kHz SCS, 2.5 ms for 30kHz SCS, etc.).

[0297] Next, in Figure 12 Parts (b), (c), and (d) show cases where SBFD works with TDD in a specific frequency band.

[0298] refer to Figure 12 In part (b), the UE may be configured with some frequency bands of the cell as frequency band 1210 in which uplink transmission may be performed. This frequency band may be referred to as the uplink sub-band (UL sub-band). The UL sub-band may be applied to all symbols of all time slots. The UE may transmit uplink channels or signals scheduled in all symbols 1212 within the sub-band (UL sub-band). However, the UE may not transmit uplink channels or signals in frequency bands other than the sub-band (UL sub-band) and uplink time slot 1211.

[0299] refer to Figure 12 In part (c), the UE can be configured with some frequency bands within the cell as frequency bands 1220 in which uplink transmission may occur, and can be configured with the time domain in which the frequency bands are activated. Here, the frequency bands can be referred to as uplink sub-bands (UL sub-bands). Figure 12In part (c), the UL subband is deactivated in the first time slot and can be activated in the remaining time slots. Therefore, the UE can transmit uplink channels or signals in the UL subband 1222 of the remaining time slots (including uplink time slot 1221).

[0300] According to an embodiment, the UL subband is activated slot-by-slot, but it can also be configured to be activated symbol-by-symbol.

[0301] refer to Figure 12 In part (d), the UE can be configured with time-frequency resources associated with the UL subband that may be used for uplink transmission. The UE can be configured with one or more time-frequency resources as possible uplink transmission resources. For example, a portion of band 1232 in the first and second time slots can be configured as possible uplink transmission resources. Additionally, a portion of band 1233 in the third time slot and a portion of band 1234 in the fourth time slot can be configured as possible uplink transmission resources. Furthermore, the UE can transmit uplink channels or signals in uplink time slot 1231.

[0302] According to an embodiment, the frequency resources of the uplink subbands can be configured to be the same or different on a time-slot basis, or on a symbol-by-symbol basis. Additionally, the activated time domains can be combined and configured by taking time resources into account.

[0303] In the following description, the time-frequency resources in the downlink symbol or flexible symbol that may be used for uplink transmission may be referred to as SBFD resources, uplink subbands, or UL subbands.

[0304] [PUSCH repeats on SBFD UL sub-band]

[0305] The UE can receive scheduling information for the Msg3 PUSCH from the base station. The scheduling information for the Msg3 PUSCH can be included in the RAR UL license.

[0306] A RAR UL license may include at least one of the following information, but is not limited to the examples below: -Frequency hopping flag- 1 bit -PUSCH Frequency Resource Allocation- 14-bit -PUSCH time resource allocation- 4 bits -MCS - 4-bit - TPC commands for PUSCH - 3 bits -CSI Request- 1 bit The UE can obtain the time-domain scheduling information (scheduled time slots and symbols within the time slots) of the Msg3 PUSCH through the PUSCH time resource allocation field. For example, the PUSCH time resource allocation field is 4 bits and can indicate one of the 16 rows of a table. The field (table) may include the time slot offset, the starting symbol index within the time slot, the number of consecutive symbols, the PUSCH mapping type, etc.

[0307] The UE can transmit Msg3 PUSCH in the symbol of the time slot indicated in the time-domain scheduling information. In this case, the UE does not need to transmit Msg3 PUSCH repeatedly. For example, the UE can transmit Msg3PUSCH only once in the symbol of the indicated time slot.

[0308] The UE may additionally request the retransmission of Msg3 PUSCH from the base station to extend uplink coverage. The UE can indicate or include this request by sending a specific PRACH to the base station. Here, the specific PRACH may correspond to a specific RACH timing, a specific preamble (e.g., a preamble corresponding to a specific index), etc. When the UE requests the retransmission of Msg3 PUSCH, the UE's PUSCH transmission may be as follows.

[0309] According to an embodiment, the UE can obtain the 4-bit Modulation and Coding Scheme (MCS) field from the RAR UL license. The most significant two bits (MSB) of the 4-bit MCS field can indicate the PUSCH retransmission count. The two least significant bits (LSB) of the MCS field can indicate the MCS value of the PUSCH.

[0310] According to an embodiment, when there is no separate configuration, the MSB 2 bits can be interpreted as a value of {R1, R2, R3, R4} as the Msg3 PUSCH repetition count. The base station can configure the R1, R2, R3, and R4 values ​​to the UE. In this case, the UE can apply the values ​​configured by the base station. For example, when the MSB 2 bit is "00", the Msg3 PUSCH repetition count can be R1; if the MSB 2 bit is "01", the Msg3 PUSCH repetition count can be R2; if the MSB 2 bit is "10", the Msg3 PUSCH repetition count can be R3; and if the MSB 2 bit is "11", the Msg3 PUSCH repetition count can be R4. According to an embodiment, a repetition count of 1 can be the same as a non-repetitive transmission.

[0311] According to an embodiment, Msg3 PUSCH can be retransmitted in DCI format 0_0. For example, DCI format 0_0 may include a 5-bit MCS field, and the MSB 2 bits of the 5 bits can be used to indicate the Msg3 PUSCH retransmission count to the UE.

[0312] According to an embodiment, when instructing the UE to perform R repeated transmissions, the UE can repeatedly transmit the Msg3 PUSCH as follows. The UE can determine R time slots (including the time slot for transmitting the first Msg3 PUSCH) starting from the time slot for transmitting the first Msg3 PUSCH. Here, a time slot can be included in the R time slots when any time slot includes symbols scheduled for the Msg3 PUSCH that are neither symbols configured for downlink according to the cell common TDD configuration nor symbols overlapping with the SS / PBCH block.

[0313] According to an embodiment, in addition to the cell common TDD configuration, the SBFD UE can also receive SBFD configuration. Here, the SBFD configuration can be a cell common configuration. For example, the cell common configuration can indicate a configuration that applies equally to all UEs accessing the cell (cell-specific). According to an embodiment, the cell common configuration can be transmitted via a System Information Block (SIB). Based on the SBFD configuration, an SBFD UL subband can be configured for the downlink symbols or flexible symbols configured in the cell common TDD configuration. In the SBFD UL subband, the UE can transmit uplink channels or signals.

[0314] According to an embodiment, a non-SBFD symbol can refer to a symbol in which SBFD subbands are not configured according to an SBFD configuration. Additionally, DL-only symbols or UL-only symbols can indicate DL and UL symbols among non-SBFD symbols. An SBFD symbol can be a symbol in which SBFD subbands are configured according to an SBFD configuration. According to an embodiment, an SBFD configuration can be configured for DL ​​symbols and flexible symbols, and may not be configured for UL symbols (or, even if configured, may not be applied to UL symbols).

[0315] Figure 13a and Figure 13b This is a diagram illustrating a specific symbol type for determining the time slot in which Msg3PUSCH is repeatedly transmitted, according to various embodiments of the present disclosure.

[0316] refer to Figure 13a and Figure 13b The cell common TDD configuration received by the UE can be DDDSU. Here, "D" indicates that all 14 symbols in the time slot (D time slot) represent downlink, "U" indicates that all 14 symbols in the time slot (U time slot) represent uplink, and "S" indicates that 14 symbols in the time slot (S time slot) are, in order, 10 symbols are downlink symbols, 2 symbols are flexible symbols, and 2 symbols are uplink symbols. Figure 13a In the remaining portion of the graph, excluding parts (c) and (e), Msg3 PUSCH can include all symbols in the time slot (i.e., 14 symbols). Figure 13a In parts (c) and (e), the Msg3 PUSCH may include the first 12 symbols in the time slot. The SS / PBCH block (SSB) can be configured in time slots n+5 and n+6. Figure 13a and Figure 13b In this configuration, the SBFD UL subband can be configured from the first symbol of the second D slot to the 12th symbol of the S slot.

[0317] According to an embodiment, the SBFD UL subband can be configured in the downlink symbols (10 symbols) and flexible symbols (2 symbols) in the S-slot, but the SBFD UL subband may not be configured in the uplink symbols (2 symbols).

[0318] According to an embodiment, the SBFD UE may consider at least the following options to determine the time slot in which Msg3 PUSCH is repeatedly transmitted.

[0319] The base station can configure the SBFD UE to repeatedly transmit the Msg3 PUSCH in a specific symbol type. The base station can also configure the SBFD UE to repeat the Msg3 PUSCH only in a specific symbol type.

[0320] According to an embodiment, the first specific symbol type can be a symbol configured for downlink according to the cell's common TDD configuration, or a symbol other than a symbol overlapping with the SS / PBCH block. That is, the SBFD UE can identify the same symbol as a symbol in which an existing UE can repeatedly transmit Msg3 PUSCH as the specific type. Additionally, the SBFD UE can be configured with an SBFD UL subband for downlink symbols, but may not repeat Msg3 PUSCH in the SBFD UL subband.

[0321] When instructing the SBFD UE to perform R repeated transmissions, the SBFD UE can repeatedly transmit Msg3PUSCH as follows. The SBFD UE can determine R time slots (including the time slot for transmitting the first Msg3PUSCH) starting from the time slot for transmitting the first Msg3PUSCH. Here, a time slot can be included in the R time slots when any time slot includes symbols scheduled for Msg3PUSCH that are neither configured as downlink symbols according to the cell common TDD configuration nor symbols overlapping with the SS / PBCH block.

[0322] refer to Figure 13aIn part (a), since Msg3 PUSCH overlaps with downlink symbols in slots n, n+1, n+2, n+3, n+5, n+6, n+7 and n+8, the UE does not send Msg3 PUSH and can repeatedly send Msg3 PUSCH in slots n+4 and n+9.

[0323] According to an embodiment, the second specific symbol type can be a downlink symbol in which an SBFD UL subband is configured. For example, Msg3 PUSCH can be repeatedly transmitted only in the SBFD UL subband within the downlink symbol. Msg3 PUSCH can be excluded from being repeatedly transmitted in downlink symbols, flexible symbols, and uplink symbols in which no SBFD UL subband is configured.

[0324] When instructing the SBFD UE to perform R repeated transmissions, the SBFD UE can repeatedly transmit Msg3PUSCH as follows. The SBFD UE can determine R time slots (including the time slot for transmitting the first Msg3PUSCH) starting from the time slot for transmitting the first Msg3PUSCH. For example, a time slot can be included in R time slots when any time slot only includes symbols scheduled for Msg3PUSCH, and these symbols are downlink symbols configured according to the cell common TDD and symbols configured for the SBFD UL subband according to the SBFD configuration.

[0325] According to an embodiment, the frequency domain allocation information of Msg3 PUSCH received by the UE can be scheduled within the frequency width of the SBFD UL subband.

[0326] refer to Figure 13a In part (b), since Msg3 PUSCH overlaps with downlink symbols configured with SBFD UL subbands in time slots n+1, n+2, n+6, and n+7, the UE may transmit Msg3 PUSH. However, since Msg3 PUSCH overlaps with flexible or uplink symbols in time slots n+3, n+4, n+8, and n+9, the UE may not transmit Msg3 PUSCH in these time slots. Furthermore, since Msg3 PUSCH overlaps with downlink symbols not configured with SBFD UL subbands in time slots n and n+5, the UE may not transmit Msg3 PUSCH in these time slots.

[0327] According to an embodiment, the third specific symbol type can be a symbol in which an SBFD UL subband is configured. For example, Msg3 PUSCH can be repeatedly transmitted only within the SBFD UL subband. Msg3 PUSCH can be not repeatedly transmitted in symbols in which no SBFD UL subband is configured.

[0328] When instructing the SBFD UE to perform R repeated transmissions, the SBFD UE can repeatedly transmit Msg3PUSCH as follows. The SBFD UE can determine R time slots (including the time slot for transmitting the first Msg3PUSCH) starting from the time slot for transmitting the first Msg3PUSCH. For example, when any time slot includes only symbols scheduled for Msg3PUSCH, including symbols configured for the SBFD UL subband according to the SBFD configuration, that time slot can be included in the R time slots.

[0329] According to an embodiment, the frequency domain allocation information of Msg3 PUSCH received by the UE can be scheduled within the frequency width of the SBFD UL subband.

[0330] refer to Figure 13a In part (c), since Msg3 PUSCH overlaps with downlink symbols in slots n+1, n+2, n+3, n+6, n+7, and n+8 that are configured with SBFD UL subbands, the UE may send Msg3 PUSH. And since Msg3 PUSCH overlaps with symbols in slots n, n+4, n+5, and n+9 that are not configured with SBFD UL subbands, the UE may not send Msg3 PUSCH in these slots.

[0331] According to an embodiment, the fourth specific symbol type can be a downlink symbol in which an SBFD UL subband is configured that does not overlap with the SS / PBCH block. For example, Msg3 PUSCH can be repeatedly transmitted only within the SBFD UL subband of a downlink symbol that does not overlap with the SS / PBCH block. Additionally, Msg3 PUSCH can be excluded from being repeatedly transmitted in downlink symbols where an SBFD UL subband is not configured, in downlink symbols where an SBFD UL subband is configured but that SBFD UL subband overlaps with the SS / PBCH block, in flexible symbols, and in uplink symbols.

[0332] When instructing the SBFD UE to perform R repeated transmissions, the SBFD UE can repeatedly transmit Msg3PUSCH as follows. The SBFD UE can determine R time slots (including the time slot for transmitting the first Msg3PUSCH) starting from the time slot for transmitting the first Msg3PUSCH. For example, a time slot can be included in R time slots when any time slot only includes symbols scheduled for Msg3PUSCH, and these symbols are downlink symbols configured according to the cell common TDD and symbols of non-SS / PBCH blocks among the symbols configured according to the SBFD UL subband.

[0333] According to an embodiment, the frequency domain allocation information of Msg3 PUSCH received by the UE can be scheduled within the frequency width of the SBFD UL subband.

[0334] refer to Figure 13a In part (d), the UE may transmit Msg3 PUSCH because it overlaps with downlink symbols configured with SBFDUL subbands in time slots n+1, n+2, and n+7, but not with SS / PBCH blocks. The UE may not transmit Msg3 PUSCH because it overlaps with SS / PBCH blocks in time slot n+6. The UE may not transmit Msg3 PUSCH in time slots n+3, n+4, n+8, and n+9 because flexible symbols or uplink symbols overlap with Msg3 PUSCH. The UE may not transmit Msg3 PUSCH in time slots n and n+5 because it overlaps with downlink symbols not configured with SBFDUL subbands.

[0335] According to an embodiment, the fifth specific symbol type can be a symbol in which an SBFD UL subband is configured that does not overlap with the SS / PBCH block. For example, Msg3PUSCH can be repeatedly transmitted only within the SBFD UL subband of symbols that do not overlap with the SS / PBCH block. Msg3PUSCH can be not repeatedly transmitted in symbols in which no SBFD UL subband is configured or in symbols that overlap with the SS / PBCH block.

[0336] When instructing the SBFD UE to perform R repeated transmissions, the SBFD UE can repeatedly transmit Msg3PUSCH as follows. The SBFD UE can determine R time slots (including the time slot for transmitting the first Msg3PUSCH) starting from the time slot for transmitting the first Msg3PUSCH. For example, a time slot may be included in the R time slots if it does not include symbols scheduled only for Msg3PUSCH, symbols overlapping with the SS / PBCH block, and symbols configured for the SBFD UL subband according to the SBFD configuration.

[0337] According to an embodiment, the frequency domain allocation information of Msg3 PUSCH received by the UE can be scheduled within the frequency width of the SBFD UL subband.

[0338] refer to Figure 13aIn part (e), since Msg3 PUSCH overlaps with symbols configured with SBFD UL subbands in time slots n+1, n+2, n+3, n+7, and n+8, but not with SS / PBCH blocks, the UE may transmit Msg3 PUSCH. Since Msg3 PUSCH overlaps with SS / PBCH blocks in time slot S+6, the UE may not transmit Msg3 PUSCH. Since Msg3 PUSCH overlaps with symbols not configured with SBFD UL subbands in time slots n, n+4, n+5, and n+9, the UE may not transmit Msg3 PUSCH in these time slots.

[0339] According to an embodiment, the sixth specific symbol type can be a symbol configured with an SBFD UL subband, as well as flexible symbols and uplink symbols configured according to the cell's common TDD. For example, in the sixth specific symbol type, Msg3 PUSCH can be repeatedly transmitted across SBFD symbols and non-SBFD symbols. In the sixth specific symbol type, each Msg3 PUSCH repetition can overlap with only one type of symbol. For example, in SBFD symbols, Msg3 PUSCH should be included in the SBFD UL subband, and in non-SBFD symbols, Msg3 PUSCH should be included in the UL BWP.

[0340] When instructing the SBFD UE to perform R repeated transmissions, the SBFD UE can repeatedly transmit Msg3PUSCH as follows. The SBFD UE can determine R time slots (including the time slot for transmitting the first Msg3PUSCH) starting from the time slot for transmitting the first Msg3PUSCH. For example, according to an embodiment, a time slot can be included in the R time slots when any time slot includes a symbol scheduled for Msg3PUSCH that meets the following conditions.

[0341] -Msg3 PUSCH includes only one symbol type: SBFD symbols and non-SBFD symbols. - When Msg3 PUSCH only includes SBFD symbols, the frequency band occupied by Msg3 PUSCH should be fully included in the SBFDUL subband. - When Msg3 PUSCH only includes non-SBFD symbols, the frequency band occupied by Msg3 PUSCH should be fully included in ULBWP.

[0342] refer to Figure 13bIn part (f), since the Msg3 PUSCH overlaps with symbols or uplink symbols configured with SBFD UL subbands in time slots n+1, n+2, n+4, n+6, n+7, and n+9, the UE can transmit the Msg3 PUSCH (i.e., the conditions listed above can be considered satisfied). Since a Msg3 PUSCH overlaps with two symbol types in time slots n+3 and n+8, the UE may not transmit the Msg3 PUSH in these time slots. Since the Msg3 PUSCH overlaps with downlink symbols in time slots n and n+5, the UE may not transmit the Msg3 PUSCH in these time slots.

[0343] According to an embodiment, the seventh specific symbol type can be a symbol configured with an SBFD UL subband among symbols that do not overlap with the SS / PBCH block, as well as flexible symbols and uplink symbols configured according to the cell common TDD. For example, in the seventh specific symbol type, Msg3 PUSCH can be repeatedly transmitted across SBFD symbols and non-SBFD symbols among symbols that do not overlap with the SS / PBCH block. In the seventh specific symbol type, each Msg3 PUSCH repetition can overlap with only one type of symbol. For example, in SBFD symbols, Msg3 PUSCH should be included in the SBFD UL subband, and in non-SBFD symbols, Msg3 PUSCH should be included in the UL BWP.

[0344] When instructing the SBFD UE to perform R repeated transmissions, the SBFD UE can repeatedly transmit Msg3PUSCH as follows. The SBFD UE can determine R time slots (including the time slot for transmitting the first Msg3PUSCH) starting from the time slot for transmitting the first Msg3PUSCH. For example, according to an embodiment, a time slot can be included in the R time slots when any time slot includes a symbol scheduled for Msg3PUSCH that meets the following conditions.

[0345] -Msg3 PUSCH includes only symbols that do not overlap with SS / PBCH blocks. -Msg3 PUSCH includes only one symbol type: SBFD symbols and non-SBFD symbols. - When Msg3 PUSCH only includes SBFD symbols, the frequency band occupied by Msg3 PUSCH should be fully included in the SBFDUL subband. - When Msg3 PUSCH only includes non-SBFD symbols, the frequency band occupied by Msg3 PUSCH should be fully included in ULBWP.

[0346] refer to Figure 13bIn part (g), since Msg3 PUSCH overlaps with symbols or uplink symbols configured with SBFD UL subbands in slots n+1, n+2, n+4, n+7, and n+9 but not with SS / PBCH blocks, the UE may transmit Msg3 PUSCH (i.e., the conditions listed above can be considered satisfied). Since Msg3 PUSCH overlaps with SS / PBCH blocks in slot n+6, the UE may not transmit Msg3 PUSCH. Since a Msg3 PUSCH overlaps with two symbol types in slots n+3 and n+8, the UE may not transmit Msg3 PUSH in these slots. Since Msg3 PUSCH overlaps with downlink symbols in slots n and n+5, the UE may not transmit Msg3 PUSCH in these slots.

[0347] According to an embodiment, the eighth specific symbol type can be a symbol configured with an SBFD UL subband, as well as a flexible symbol and uplink symbol configured according to the cell's common TDD. For example, in the eighth specific symbol type, Msg3 PUSCH can be repeatedly transmitted across SBFD symbols and non-SBFD symbols. In the eighth specific symbol type, a Msg3 PUSCH can include two symbol types. For example, in SBFD symbols, Msg3 PUSCH should be included in the SBFD UL subband, and in non-SBFD symbols, Msg3 PUSCH should be included in the UL BWP.

[0348] When instructing the SBFD UE to perform R repeated transmissions, the SBFD UE can repeatedly transmit Msg3PUSCH as follows. The SBFD UE can determine R time slots (including the time slot for transmitting the first Msg3PUSCH) starting from the time slot for transmitting the first Msg3PUSCH. For example, according to an embodiment, a time slot can be included in the R time slots when any time slot includes a symbol scheduled for Msg3PUSCH that meets the following conditions.

[0349] - When Msg3 PUSCH includes the SBFD symbol, the frequency band occupied by Msg3 PUSCH should be fully included in the SBFD UL subband. - When Msg3 PUSCH only includes non-SBFD symbols, the frequency band occupied by Msg3 PUSCH should be fully included in ULBWP.

[0350] refer to Figure 13bIn part (h), since Msg3 PUSCH overlaps with symbols or flexible symbols configured with SBFD UL subbands and uplink symbols in time slots n+1, n+2, n+3, n+4, n+6, n+7, n+8, and n+9 (i.e., the conditions listed above can be considered satisfied), the UE can transmit Msg3 PUSCH. Since Msg3 PUSCH overlaps with downlink symbols in time slots n and n+5, the UE may not transmit Msg3 PUSCH in these time slots.

[0351] According to an embodiment, the ninth specific symbol type can be a symbol configured with an SBFD UL subband among symbols that do not overlap with the SS / PBCH block, as well as flexible symbols and uplink symbols configured according to the cell common TDD. For example, in the ninth specific symbol type, Msg3 PUSCH can be repeatedly transmitted across SBFD symbols and non-SBFD symbols among symbols that do not overlap with the SS / PBCH block. In the ninth specific symbol type, a Msg3 PUSCH can include two symbol types.

[0352] For example, in SBFD symbols, Msg3 PUSCH should be included in the SBFD UL sub-band, and in non-SBFD symbols, Msg3 PUSCH should be included in the UL BWP.

[0353] When instructing the SBFD UE to perform R repeated transmissions, the SBFD UE can repeatedly transmit Msg3PUSCH as follows. The SBFD UE can determine R time slots (including the time slot for transmitting the first Msg3PUSCH) starting from the time slot for transmitting the first Msg3PUSCH. For example, according to an embodiment, a time slot can be included in the R time slots when any time slot includes a symbol scheduled for Msg3PUSCH that meets the following conditions.

[0354] -Msg3 PUSCH includes only symbols that do not overlap with SS / PBCH blocks. - When Msg3 PUSCH includes the SBFD symbol, the frequency band occupied by Msg3 PUSCH should be fully included in the SBFD UL subband. - When Msg3 PUSCH only includes non-SBFD symbols, the frequency band occupied by Msg3 PUSCH should be fully included in ULBWP.

[0355] refer to Figure 13bIn part (i), since Msg3 PUSCH overlaps with symbols or flexible symbols and uplink symbols configured with SBFD UL subbands in slots n+1, n+2, n+3, n+4, n+7, n+8, and n+9 (i.e., the conditions listed above can be considered satisfied), the UE can transmit Msg3 PUSCH. Since Msg3 PUSCH overlaps with the SS / PBCH block in slot n+6, the UE can choose not to transmit Msg3 PUSCH. Since Msg3 PUSCH overlaps with downlink symbols in slots n and n+5, the UE can choose not to transmit Msg3 PUSCH in these slots.

[0356] The base station may indicate at least one of a first to a ninth specific symbol type to the UE. This indication may be transmitted by including it in a System Information Block (SIB) sent by the base station. According to an embodiment, the indication may be included in SIB1.

[0357] According to an embodiment, the UE can receive at least one of the following indications from the base station and can determine, based on these indications, the symbol on which Msg3 PUSCH can be transmitted.

[0358] - Whether Msg3 PUSCH transmission is possible in the SBFD UL subband. For example, this information can be indicated by 1 bit. When Msg3 PUSCH transmission is possible in the SBFD UL subband, Msg3 PUSH can be sent in at least one of the second, third, fourth, fifth, sixth, seventh, eighth, and ninth specific symbol types. When Msg3 PUSCH transmission is not possible in the SBFD UL subband, Msg3 PUSCH can be sent in the first specific symbol type.

[0359] - Whether Msg3 PUSCH transmission is possible in a symbol overlapping with an SS / PBCH block. For example, this information can be indicated by 1 bit. When Msg3 PUSCH transmission is possible in a symbol overlapping with an SS / PBCH block, Msg3 PUSCH can be transmitted in at least one of the first specific symbol type, the second specific symbol type, the third specific symbol type, the sixth specific symbol type, and the eighth specific symbol type.

[0360] - Whether Msg3 PUSCH transmission is possible across SBFD and non-SBFD symbols. For example, this information could be indicated by 1 bit. When Msg3 PUSCH can be transmitted across SBFD and non-SBFD symbols, it can be transmitted in at least one of the sixth, seventh, eighth, and ninth specific symbol types. When Msg3 PUSCH transmission is not possible in the SBFD UL subband, it can be transmitted in the first specific symbol type. When Msg3 PUSCH transmission is not possible across SBFD and non-SBFD symbols, it can be transmitted in at least one of the second, third, fourth, and fifth specific symbol types.

[0361] - Whether a Msg3 PUSCH retransmission is possible across SBFD and non-SBFD symbols. This information may be additionally indicated when indicating the possibility of a Msg3 PUSCH retransmission across SBFD and non-SBFD symbols. For example, this information may be indicated by 1 bit. When a Msg3 PUSCH retransmission is possible across SBFD and non-SBFD symbols, the Msg3 PUSCH may be transmitted in at least one of the eighth and ninth specific symbol types. When a Msg3 PUSCH retransmission is not possible across SBFD and non-SBFD symbols, the Msg3 PUSCH may be transmitted in at least one of the sixth and seventh specific symbol types.

[0362] Table 17 may represent the symbol types determined by the UE based on the instructions received from the base station. Table 17 and the first to ninth specific symbol types are examples, and the base station may not send all instructions to the UE, and may not indicate some specific symbols.

[0363] The specific symbol type determined according to the embodiments of this disclosure can be applied not only to Msg3 PUSCH transmission, but also to PUCCHs that send Msg4 PDSCH HARQ-ACKs or PUSCHs sent by UEs connected by RRC.

[0364] This disclosure describes how a base station configures a specific symbol type for a UE, but a specific symbol type can be defined as a standard document specification. For example, Msg3 PUSCH transmission may always be possible only in a first specific symbol type.

[0365] Table 17

[0366] According to embodiments of the present invention, the UE can obtain an indication via RAR UL authorization. For example, the UE can obtain the repetition count of Msg3 PUSCH from the MSB 2 bits of the MCS field of the base station's RAR UL authorization. The UE can also obtain an indication from the MSB 2 bits. When the base station configures the repetition count {R1, R2, R3, R4} corresponding to the MSB 2 bits, the base station can configure a specific symbol type to be used with the repetition count value. For example, R2 can be set to 4, and a first specific symbol type can be configured. In this case, if the MSB 2 bits of the MCS field of the RAR UL authorization are "01", the UE can repeat Msg3PUSCH 4 times, and the symbol type that can be used for repeated transmission can be the first specific symbol type. The base station can configure the UE to have different symbol types at different 2-bit MSB code points {R1, R2, R3, R4}. Therefore, the UE can obtain information about the Msg3 PUSCH repetition count and the transmittable symbol type from the 2-bit MSB. In the case of a PUCCH with HARQ-ACK sent as Msg4 PDSCH, the PUCCH can be sent with the same symbol type as Msg3 PUSCH.

[0367] Figure 14 This is a diagram illustrating a sequence diagram of Msg3 PUSCH for transmitting a UE according to an embodiment of the present disclosure.

[0368] In operation 1400, the UE can receive configuration information, including information about symbols capable of transmitting Msg3PUSCH, from system information sent by the base station. According to an embodiment, the UE can determine, based on this information, which symbols can be used to transmit Msg3PUSCH. According to embodiments of this disclosure, this information may include an indication.

[0369] In operation 1410, the UE may receive a RAR UL grant for scheduling the Msg3 PUSCH. The UE may obtain from the PAR UL grant the symbol in which the Msg3 PUSCH is scheduled or the Msg3 PUSCH repetition count.

[0370] In operation 1420, the UE can determine the transmittable time slots so as to repeatedly transmit Msg3PUSCH based on the repetition count. According to an embodiment, the transmittable time slots can be determined based on information obtained in operation 1400. For example, the UE can transmit Msg3PUSCH in symbols that can be used to transmit Msg3PUSCH in operation 1400, and can also avoid transmitting Msg3PUSCH in symbols that cannot be used to transmit Msg3PUSCH.

[0371] [PUSCH frequency hopping bit determined]

[0372] The UE can obtain the scheduling information of Msg3 PUSCH from the RAR UL license. According to an embodiment, the frequency hopping flag field can be used to indicate to the UE whether to perform frequency hopping on Msg3 PUSCH, and the UE can obtain the frequency domain allocation information of Msg3 PUSCH through the PUSCH frequency resource allocation field.

[0373] According to an embodiment, the MSB 1 bit or MSB 2 bit of the PUSCH frequency resource allocation field can be used to indicate the frequency hopping offset value.

[0374] Referring to Table 18, the UE can determine the number of bits indicating the frequency hopping offset value based on the size of the initial UL BWP. According to an embodiment, if the initial UL BWP includes a certain number of RBs... If the number is less than a certain amount, the number of bits indicating the frequency hopping offset value can be 1, and if the number of RBs included in the initial UL BWP is... If the number is greater than or equal to a certain number, the number of bits indicating the frequency hopping offset value can be 2. For example, the specific number could be 50 RBs.

[0375] According to an embodiment, when the number of bits indicating the frequency hopping offset value is 1, if the MSB1 bit of the PUSCH frequency resource allocation field is "0", then the frequency hopping offset value can be... Furthermore, if MSB bit 1 is "1", the frequency hopping offset value can be... .

[0376] According to an embodiment, when the number of bits indicating the frequency hopping offset value is 2, if the MSB2 bit of the PUSCH frequency resource allocation field is "00", then the frequency hopping offset value can be... If the MSB 2 bits are "01", then the frequency hopping offset value can be... And if MSB bit 2 is "10", then the frequency hopping offset value can be - Additionally, if the MSB2 bit is "11", the frequency hopping offset value does not need to be defined. For example, "11" could be an unused code point.

[0377] Table 18

[0378] The SBFD UE can obtain the Msg3 PUSCH scheduling information from the SBFD UL subband from the RAR UL license. In this case, the UE's frequency hopping offset value can be determined as follows. According to an embodiment, the SBFD UL subband can be defined as the SBFD UL subband included in the initial UL BWP.

[0379] According to Table 19, if the number of RBs included in the SBFD UL subband If the number is less than a certain amount, the number of bits indicating the frequency hopping offset value of the SBFDUE can be 1, and if the number of RBs included in the initial UL BWP is... If the number is greater than or equal to a certain number, the number of bits indicating the frequency hopping offset value of the SBFD UE can be 2. For example, the specific number could be 50 RBs.

[0380] According to an embodiment, when the number of bits indicating the frequency hopping offset value is 1, if the MSB1 bit of the PUSCH frequency resource allocation field is "0", then the frequency hopping offset value can be... Furthermore, if MSB bit 1 is "1", the frequency hopping offset value can be... .

[0381] According to an embodiment, when the number of bits indicating the frequency hopping offset value is 2, if the MSB2 bit of the PUSCH frequency resource allocation field is "00", then the frequency hopping offset value can be... If the MSB 2 bits are "01", then the frequency hopping offset value can be... And if MSB bit 2 is "10", then the frequency hopping offset value can be - For reference, if the MSB 2 bits are "11", then a frequency hopping offset value does not need to be defined. For example, "11" could be an unused code point.

[0382] Table 19

[0383] Table 19 is used for description in this disclosure, but this disclosure can also be applied to other methods for determining frequency hopping offset values.

[0384] According to an embodiment, Msg3 PUSCH can be repeatedly transmitted in both SBFD and non-SBFD symbols. According to an embodiment, Msg3 PUSCH transmitted in SBFD symbols can be referred to as SBFD Msg3 PUSCH, and Msg3 PUSCH transmitted in non-SBFD symbols can be referred to as non-SBFD Msg3 PUSCH or conventional Msg3 PUSCH, and is not limited to the above expressions.

[0385] The problem to be solved in this disclosure corresponds to a method for determining whether frequency hopping is performed in each SBFD symbol and non-SBFD symbol when the UE transmits Msg3 PUSCH.

[0386] According to an embodiment, the UE can obtain a 1-bit frequency hopping flag from the RAR UL license. The UE can typically apply the frequency hopping flag to both SBFD Msg3 PUSCH and non-SBFD Msg3 PUSCH. For example, if the frequency hopping flag value is "0", neither SBFD Msg3 PUSCH nor non-SBFD Msg3 PUSCH can use frequency hopping. If the frequency hopping flag value is "1", both SBFD Msg3 PUSCH and non-SBFD Msg3 PUSCH can use frequency hopping.

[0387] According to an embodiment, the frequency band in which non-SBFD Msg3 PUSCH can be transmitted (determined by the initial UL BWP) can be larger than the frequency band in which SBFD Msg3 PUSCH can be transmitted (determined by the SBFD UL subband). According to an embodiment, since frequency hopping can be used to indicate both non-SBFD Msg3 PUSCH and SBFD Msg3 PUSCH simultaneously, unnecessary frequency hopping for SBFD Msg3 PUSCH may be indicated.

[0388] According to an embodiment, the UE can obtain a frequency hopping flag bit from the RAR UL license. The UE can apply the frequency hopping flag only to non-SBFD Msg3 PUSCH. Whether SBFD Msg3 PUSCH is frequency hopping can be determined as follows.

[0389] In the first method, SBFD Msg3 PUSCH may not always perform frequency hopping. For example, the bandwidth of the SBFD UL subband may typically be small, and the frequency diversity gain that can be obtained through frequency hopping may be small in terms of bandwidth. Therefore, SBFD Msg3 PUSCH transmitted in the SBFD UL subband may not always perform frequency hopping.

[0390] In the second method, the base station can configure whether to perform frequency hopping for the SBFD Msg3 PUSCH. For example, this configuration can be included in the System Information Block (SIB) for transmitting system information and can be applied collectively to all UEs in the cell. Depending on the configuration, the UE can determine whether to transmit the SBFD Msg3 PUSCH with or without frequency hopping.

[0391] In the third method, frequency hopping of SBFD Msg3 PUSCH can be determined based on the bandwidth of the SBFD UL subband. For example, the UE does not perform frequency hopping when the number of RBs included in the SBFD UL subband is less than a certain number, and the UE can always perform frequency hopping when the number of RBs included in the SBFD UL subband is greater than or equal to the certain number.

[0392] The fourth method can determine whether to perform SBFD Msg3PUSCH frequency hopping based on the number of RBs scheduled for Msg3 PUSCH. For example, the UE can perform frequency hopping when the number of RBs scheduled for Msg3 PUSCH is less than a certain number, and the UE can choose not to perform frequency hopping when the number of RBs scheduled for Msg3 PUSCH is greater than a certain number.

[0393] The fifth method can indicate SBFD Msg3 PUSCH frequency hopping through certain fields permitted by RAR UL. For example, the MSB 2 bits of the MCS field permitted by RAR UL can indicate the Msg3 PUSCH repetition count. For example, the MSB 2 bits can indicate one of the values ​​{R1, R2, R3, R4}. The base station can configure the UE to perform frequency hopping, and for each repetition count value. For example, when the MSB 2 bits are “01”, the Msg3 PUSCH repetition count indicates R2, and can also indicate whether frequency hopping is possible, and the repetition count value. For example, other fields permitted by RAR UL in the MCS field can be used to indicate to the UE whether to perform SBFD Msg3 PUSCH frequency hopping.

[0394] According to the embodiment, the second to fifth methods can only be used when bit 1 of the frequency hopping flag permitted by the RAR UL is "1". That is, the second to fifth methods can determine whether to perform SBFD Msg3 PUSCH frequency hopping only when the frequency hopping flag indicates a non-SBFD Msg3 PUSCH frequency hopping.

[0395] According to an embodiment, the UE can avoid applying frequency hopping because it is instructed to use "0" as the frequency hopping offset value. According to an embodiment, the UE can be configured with the frequency hopping offset value for SBFD Msg3 PUSCH, as shown in Table 20. Referring to Table 20, "0" can be indicated to the UE as the frequency hopping offset value. In this case, the UE can send SBFD Msg3PUSCH without applying the frequency hopping offset.

[0396] Table 20

[0397] Referring to Tables 18 and 19, the UE can independently determine the number of hopping bits for the SBFD Msg3 PUSCH and the number of hopping bits for the non-SBFD Msg3 PUSCH. For example, when the initial UL BWP size is 50 RB or greater and the SBFD UL subband size is less than 50 RB, the hopping bits for the non-SBFD Msg3 PUSCH can be determined to be 2 bits, and the hopping bits for the SBFD Msg3 PUSCH can be determined to be 1 bit. In such an example, the UE may encounter the following ambiguity when interpreting the PUSCH frequency resource allocation field. For example, when interpreting the PUSCH frequency resource allocation field, the UE may obtain frequency domain allocation information by using the remaining bits from the MSB other than the bits corresponding to the determined hopping bits. The UE may use the bits obtained from the MSB corresponding to the number of determined hopping bits to obtain the hopping offset value. Since the number of determined hopping bits is different, the UE may not know how many hopping bits to exclude from the MSB to interpret the remaining bits other than the hopping bits as frequency domain allocation information. A method for resolving this problem is disclosed.

[0398] In the first method, the UE can determine the frequency hopping bits based on one symbol type and use the same number of frequency hopping bits for other symbol types.

[0399] For example, the UE can always determine the frequency hopping bit for non-SBFD Msg3 PUSCH and set that value as the frequency hopping bit for SBFDMsg3 PUSCH. If the initial UL BWP size is 50 RB or greater, the UE can treat the frequency hopping bit for non-SBFD Msg3 PUSCH and the frequency hopping bit for SBFD Msg3 PUSCH as two bits. If the initial UL BWP size is less than 50 RB, the UE can treat the frequency hopping bit for non-SBFD Msg3 PUSCH and the frequency hopping bit for SBFD Msg3 PUSCH as one bit. In this case, the frequency hopping bit can be determined regardless of the size of the SBFD UL subband.

[0400] For example, the UE can always determine the frequency hopping bit for SBFD Msg3 PUSCH and treat it as the frequency hopping bit for non-SBFD Msg3 PUSCH. If the SBFD UL subband size is 50 RB or greater, the UE can treat both the non-SBFD Msg3 PUSCH and SBFD Msg3 PUSCH frequency hopping bits as two bits. If the SBFD UL subband size is less than 50 RB, the UE can treat both the non-SBFD Msg3 PUSCH and SBFD Msg3 PUSCH frequency hopping bits as one bit. In this case, the frequency hopping bit can be determined regardless of the initial UL BWP size.

[0401] For example, the UE can determine a symbol type based on scheduling information. For instance, the frequency hopping bit can be determined based on the symbol type of the first Msg3 PUSCH scheduled for the UE. Here, the first transmitted symbol type could be the earliest time-ordered Msg3 PUSCH repetition.

[0402] In the second method, the UE can determine the frequency hopping bit for the SBFD Msg3 PUSCH and the non-SBFD Msg3 PUSCH separately, and use one of these two values ​​to determine the frequency hopping bit. For example, the frequency hopping bit can be determined based on the larger of the two values. Alternatively, the frequency hopping bit can be determined based on the smaller of the two values.

[0403] According to an embodiment, when determining the frequency hopping bit based on a larger value, the UE can use the remaining bits other than the MSB corresponding to that value to obtain frequency domain allocation information.

[0404] According to the embodiment, when determining the frequency hopping bit based on a larger value, the frequency hopping offset value can be obtained based on the same larger value even in sign types where a smaller value is used as the value of the frequency hopping bit. For example, when the frequency hopping bit of a non-SBFD Msg3 PUSCH is 2 bits and the frequency hopping bit of SBFD Msg3 PUSCH is 1 bit, the 2 bits can be determined as the final frequency hopping bit. The MSB 2 bits of the PUSCH frequency resource allocation field can be used to determine the frequency hopping offset value. Referring to Tables 18 and 19, when the MSB 2 bits are "00", the frequency hopping offset value of a non-SBFD Msg3 PUSCH can be... Furthermore, the frequency hopping offset value of SBFD Msg3 PUSCH can be When MSB bit 2 is "01", the frequency hopping offset value for non-SBFD Msg3 PUSCH can be... Furthermore, the frequency hopping offset value of SBFD Msg3 PUSCH can be Furthermore, when MSB bit 2 is "10", the frequency hopping offset value for non-SBFD Msg3 PUSCH can be - Furthermore, the frequency hopping offset value of SBFD Msg3 PUSCH can be - .

[0405] According to an embodiment, when determining the frequency hopping bit based on the larger value, in the sign type where the smaller value is used as the value of the frequency hopping bit, only some of the larger values ​​can be used to determine the frequency hopping offset value. For example, if the larger value is 2 bits and the smaller value is 1 bit, then 1 bit of the 2 bits (the least significant bit (LSB)) can be used to determine the frequency hopping offset value. Referring to Tables 18 and 19, when MSB 2 bits are "00", the frequency hopping offset value for non-SBFD Msg3 PUSCH is... And when MSB bit 2 is "01", the frequency hopping offset value for non-SBFD Msg3 PUSCH is When one of the two bits (LSB) is "0", the frequency hopping offset value of SBFD Msg3 PUSCH can be... Furthermore, when one of the two bits (LSB) is "1", the frequency hopping offset value of SBFD Msg3 PUSCH can be... .

[0406] Although this disclosure is described based on Msg3 PUSCH, it can also be applied to PUSCH scheduled in DCI format. According to an embodiment, for a PUSCH scheduled in DCI format, the base station can configure up to four frequency hopping offsets for the UE. According to an embodiment, when the UE is configured to have four offset values ​​in non-SBFD symbols and two offset values ​​in SBFD symbols, the UE can determine the frequency hopping offset values ​​using the 2-bit MSB of the Frequency Domain Resource Allocation (FDRA) field in the DCI format. According to an embodiment, in non-SBFD symbols, 2 bits can be used to indicate one of the four offset values, and in SBFD symbols, 1 bit of the MSB of the FDRA field can be used to indicate one of the two offset values. When scheduling a PUSCH scheduled in DCI format across SBFD and non-SBFD symbols, the UE can determine the duration of the frequency hopping offset indicator based on the maximum value of the number of bits required in the non-SBFD symbols and the number of bits required in the SBFD symbols. Additionally, the duration of the frequency hopping offset indicator in the MSB of the FDRA field can be determined as the frequency hopping offset indicator. According to the embodiment, in a non-SBFD symbol, two bits of the frequency hopping offset indicator can be used to indicate one of the four offset values, and in an SBFD symbol, one bit (LSB) of the two bits of the frequency hopping offset indicator can be used to indicate one of the two offset values.

[0407] Figure 15 This is a flowchart illustrating the Msg3 PUSCH frequency hopping according to an embodiment of the present disclosure.

[0408] In Operation 1500, the UE can determine the number of first frequency hopping bits for Msg3 PUSCH (SBFD Msg3PUSCH) to be transmitted in SBFD symbols, and the number of second frequency hopping bits for Msg3 PUSCH (non-SBFD Msg3PUSCH) to be transmitted in non-SBFD symbols. For example, the number of first frequency hopping bits can be determined based on the number of RBs included in the SBFD UL subband, and the number of second frequency hopping bits can be determined based on the number of RBs included in the non-SBFD UL subband.

[0409] In operation 1510, the number of first frequency hopping bits and the number of second frequency hopping bits determined by the UE can be the same or different. For example, if the number of first frequency hopping bits and the number of second frequency hopping bits are the same, this value can be determined as the final number of frequency hopping bits. If the number of first frequency hopping bits and the number of second frequency hopping bits are different, the final number of frequency hopping bits can be determined based on the larger of the two values.

[0410] In Operation 1520, the UE can obtain the PUSCH frequency resource allocation field from the RAR UL license. For example, the UE can obtain frequency domain allocation information by interpreting the remaining bits in the field, excluding the MSB bits corresponding to the final number of frequency hopping bits.

[0411] In Operation 1530, the UE can obtain the PUSCH frequency resource allocation field from the RAR UL license. The UE can obtain the frequency hopping offset value from the MSB bits corresponding to the final number of frequency hopping bits in the field. For example, the first frequency hopping offset value for SBFD Msg3PUSCH can be determined, and the second frequency hopping offset value for non-SBFD Msg3 PUSCH can be determined. The first and second frequency hopping offset values ​​can be the same or different.

[0412] In Operation 1540, the UE can use a first frequency hopping offset value to transmit Msg3 PUSCH in SBFD symbols and can use a second frequency hopping offset value to transmit Msg3 PUSCH in non-SBFD symbols.

[0413] According to the embodiments, the above steps and each configuration can be omitted or combined.

[0414] [PUSCH frequency hopping disabled]

[0415] According to embodiments of this disclosure, even if the UE is instructed to transmit PUSCH by applying frequency hopping, the UE can also transmit PUSCH without applying frequency hopping. For example, PUSCH can be repeatedly transmitted in both non-SBFD symbols and SBFD symbols. In this case, PUSCH can be transmitted within the UL BWP in non-SBFD symbols and within the SBFD UL subband in SBFD symbols. The bandwidth of the UL BWP can be greater than the bandwidth of the SBFD UL subband. Therefore, frequency diversity can be obtained through frequency hopping-based transmission within the bandwidth of the UL BWP, but the frequency diversity gain obtainable through frequency hopping-based transmission in the SBFD UL subband may be very small. Therefore, frequency hopping-based transmission may not be performed in the SBFD UL subband.

[0416] For example, whether to perform frequency hopping can be determined based on the frequency interval between the first and second hops of the scheduled PUSCH. For example, when the first hop is a low-frequency hop in the frequency domain and the second hop is a high-frequency hop in the frequency domain, the UE can determine the frequency interval between the first and second hops as at least one of the following: -Lowest RB index of the second hop- Lowest RB index of the first hop -Highest RB index of the second hop-Highest RB index of the first hop -Highest RB index of the second hop-Lowest RB index of the first hop According to an embodiment, the UE can determine whether to perform frequency hopping based on the frequency interval. When the frequency interval is less than a certain size, the UE may not perform frequency hopping. In this case, PUSCH can be transmitted at the frequency of the first hop. That is, when the two hops are separated by a certain size or more in the frequency domain, frequency diversity can be obtained for these two hops.

[0417] [PUSCH Transmit Power Control]

[0418] According to an embodiment, the UE can apply different transmit powers to PUSCH transmitted in SBFD symbols and PUSCH transmitted in non-SBFD symbols. The UE can dynamically change the transmit power of PUSCH via signaling from the base station. According to an embodiment, the signaling may include a DCI format for scheduling PUSCH, or a DCI format that does not schedule PUSCH and only provides power information to one or more UEs.

[0419] According to an embodiment, the base station can use 2 bits to dynamically control the power of the UE's PUSCH. These 2 bits can be included in a TPC command for the scheduled PUSCH field, and the field can be included in the DCI format used for scheduling pushes. The UE can determine the transmission power of the scheduled PUSCH based on the value corresponding to the TPC command for the scheduled PUSCH field.

[0420] For example, if the value of the 2-bit TPC command for the scheduled PUSCH field is “00”, the PUSCH power can be changed by -1 dB; if the value of the 2-bit TPC command for the scheduled PUSCH field is “01”, it changes by 0 dB; if the value of the 2-bit TPC command for the scheduled PUSCH field is “10”, it changes by 1 dB; and if the value of the 2-bit TPC command for the scheduled PUSCH field is “11”, it changes by 3 dB.

[0421] The problem to be solved in this disclosure is a method for dynamically changing the transmit power when scheduling repeated transmissions of PUSCH across SBFD symbols and non-SBFD symbols.

[0422] According to embodiments of this disclosure, the DCI format for scheduling PUSCH may include two TPC commands for the scheduled PUSCH field. The first TPC command for the scheduled PUSCH may correspond to the transmit power of the PUSCH transmitted in a non-SBFD symbol, and the second TPC command for the scheduled PUSCH may correspond to the transmit power of the PUSH transmitted in an SBFD symbol.

[0423] According to an embodiment, the first TPC command and the second TPC command for the scheduled PUSCH field can each consist of 2 bits. For example, if the 2-bit value of the first TPC command for the scheduled PUSCH field is "00", the transmission power of the PUSCH transmitted in a non-SBFD symbol can be changed by -1 dB; if the 2-bit value of the first TPC command for the scheduled PUSCH field is "01", the change is 0 dB; if the 2-bit value of the first TPC command for the scheduled PUSCH field is "10", the change is 1 dB; and if the 2-bit value of the first TPC command for the scheduled PUSCH field is "11", the change is 3 dB. For example, if the two-bit value of the second TPC command for the scheduled PUSCH field is “00”, the transmit power of the PUSCH transmitted in the SBFD symbol can be changed by -1 dB; if the two-bit value of the second TPC command for the scheduled PUSCH field is “01”, it changes by 0 dB; if the two-bit value of the second TPC command for the scheduled PUSCH field is “10”, it changes by 1 dB; and if the two-bit value of the second TPC command for the scheduled PUSCH field is “11”, it changes by 3 dB.

[0424] According to an embodiment, the DCI format used for scheduling PUSCH may include a TPC command for the scheduled PUSCH field. For example, the TPC command for the scheduled PUSCH may correspond to the transmission power of either a PUSCH transmitted in a non-SBFD symbol or a PUSH transmitted in an SBFD symbol.

[0425] For example, when scheduling repeated PUSCH transmissions across SBFD and non-SBFD symbols, the UE can apply the value of the TPC command for the scheduled PUSCH field to only one of these two symbol types. For PUSCHs transmitted with a non-corresponding symbol type, the transmit power may not change dynamically.

[0426] For example, a symbol type could be a symbol scheduled for the first repetition of a PUSCH repetition transmission. Alternatively, a symbol type could be a symbol configured by the base station. Alternatively, a symbol type could be indicated in the DCI format. For example, a 1-bit indicator field could be introduced, where a "0" indicates a non-SBFD symbol, and a "1" indicates an SBFD symbol. Alternatively, a symbol type could be determined based on the type of symbol in which the DCI format is received. When the DCI format is received in an SBFD symbol, a symbol type could be an SBFD symbol. When the DCI format is received in a non-SBFD symbol, a symbol type could be a non-SBFD symbol.

[0427] According to an embodiment, the DCI format used for scheduling PUSCH may include a TPC command for the scheduled PUSCH field. The TPC command for the scheduled PUSCH can generally be applied to both PUSCH transmitted in non-SBFD symbols and PUSCH transmitted in SBFD symbols.

[0428] According to an embodiment, when a DCI format is included that provides power information only to one or more UEs without scheduling PUSCH, the above method can be applied to the UE. For example, two TPC commands can be configured for the scheduled PUSCH field.

[0429] According to an embodiment, the base station can configure the start bit index of the TPC command (2 bits) for the scheduled PUSCH of a non-SBFD symbol for the UE in the DCI format. The UE can determine the transmission power of the PUSCH to be transmitted in the non-SBFD symbol based on the bit index.

[0430] According to an embodiment, the base station can configure the start bit index of the TPC command (2 bits) for the scheduled PUSCH of the SBFD symbol for the UE in the DCI format. The UE can determine the transmission power of the PUSCH to be transmitted in the SBFD symbol based on the bit index.

[0431] According to an embodiment, the UE can always assume that the TPC command (2 bits) for the scheduled PUSCH in a non-SBFD symbol and the TPC command (2 bits) for the scheduled PUSCH in an SBFD symbol are adjacent. The base station can configure the index of the start bit in the DCI format. The UE can determine the transmission power of the PUSCH transmitted in the non-SBFD symbol based on the bit index. Furthermore, the UE can determine the transmission power of the PUSCH transmitted in the SBFD symbol based on the next 2 bits. For example, the UE can obtain 4 bits based on the bit index, apply the first 2 bits to the PUSCH transmitted in the non-SBFD symbol, and apply the last 2 bits to the PUSCH transmitted in the SBFD symbol.

[0432] Figure 16 This is a diagram illustrating the structure of a UE in a wireless communication system according to an embodiment of the present disclosure.

[0433] refer to Figure 16 The UE may include: a transceiver (representing terminal receiving unit 1600 and terminal transmitting unit 1610), a memory (not shown), and a terminal processing unit 1605 (or terminal control unit or processor). The transceiver 1600 and 1610, the memory, and the terminal processing unit 1605 of the UE can operate according to the UE communication method described above. The terminal processing unit 1605 (or processor) can control the operation of the UE according to each of the above embodiments and at least one combination of the embodiments. However, the components of the UE are not limited to the examples described above. For example, the UE may include more or fewer components than those described above. Furthermore, the transceiver, memory, and processor may be implemented as a single chip.

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

[0435] In addition, the transceiver can receive signals via a wireless channel and output the received signals to the processor, and also transmit signals output from the processor via a wireless channel.

[0436] The memory can store programs and data necessary for the operation of the UE. Additionally, the memory can store control information or data included in signals sent and received by the UE. The memory can be configured as a storage medium or a combination of storage media such as read-only memory (ROM), random access memory (RAM), hard disk, optical disc (CD)-ROM, and digital versatile disc (DVD). Furthermore, multiple memories can exist.

[0437] Furthermore, the processor can control a series of processes, enabling the UE to operate according to the above embodiments. For example, the processor can receive a DCI consisting of two layers and control the UE's components to simultaneously receive multiple PDSCHs. Multiple processors can exist, and each processor can execute UE component control operations by executing programs stored in memory.

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

[0439] refer to Figure 17 The base station may include: a transceiver (representing the base station receiving unit 1700 and the base station transmitting unit 1710), a memory (not shown), and a base station processing unit 1705 (or a base station control unit or processor). The base station transceivers 1700 and 1710, the memory, and the base station processing unit 1705 can operate according to the base station communication method described above. The base station processing unit 1705 (or processor) can control the operation of the base station according to each of the above embodiments and at least one combination of the embodiments. However, the components of the base station are not limited to the examples described above. For example, the base station may include more or fewer components than those described above. Furthermore, the transceiver, memory, and processor may be implemented as a single chip.

[0440] A transceiver can transmit signals to and receive signals from a UE. These signals may include control information and data. For this purpose, the transceiver may consist of an RF transmitter that up-converts and amplifies the frequency of the transmitted signal, and an RF receiver that amplifies the received signal with low noise and down-converts the frequency of the received signal. However, this is only one embodiment of the transceiver, and the components of the transceiver are not limited to an RF transmitter and an RF receiver.

[0441] In addition, the transceiver can receive signals via a wireless channel and output the received signals to the processor, and also transmit signals output from the processor via a wireless channel.

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

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

[0444] The methods described in the embodiments of the claims or this disclosure may be implemented in hardware, software, or a combination of hardware and software.

[0445] When implemented in software, a computer-readable storage medium may be provided to store one or more programs (software modules). The one or more programs stored in the computer-readable storage medium are configured to be executable by one or more processors within 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.

[0446] Such programs (software modules, 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), disk storage devices, optical disc-ROM (CD-ROM), digital versatile optical disc (DVD), or any other form of optical storage device, as well as magnetic tape cassettes. Alternatively, programs can be stored in a memory consisting of some or all of the memories. Furthermore, each configuration memory may include multiple such memories.

[0447] Furthermore, the program can be stored in an attachable storage device that can be accessed via a communication network, such as the Internet, intranet, local area network (LAN), wide area network (WLAN), or storage area network (SAN) or a combination thereof. This storage device can be connected to an apparatus implementing embodiments of this disclosure via an external port. Additionally, a separate storage device on the communication network can be connected to an apparatus implementing embodiments of this disclosure.

[0448] In the specific embodiments of this disclosure described above, elements included in this disclosure are expressed in a singular or plural form according to the specific embodiments presented. However, for ease of description, singular or plural expressions are appropriately chosen for the presented context, and this disclosure is not limited to singular or plural components, and even if a component is expressed in the plural, the component may be configured in the singular, or even if a component is expressed in the singular, the element may be configured in the plural.

[0449] Furthermore, each embodiment can be combined with each other as needed. For example, portions of one embodiment of this disclosure and portions of another embodiment can be combined to operate a base station and a UE. 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 UE. In addition, although the above embodiments have been proposed based on an FDD LTE system, other modifications based on the technical concepts of the above embodiments can also be implemented in other systems such as TDD LTE systems and 5G or NR systems.

[0450] Furthermore, the order of description in the accompanying drawings illustrating the methods of this disclosure does not necessarily correspond to the order of execution, and the priority order can be changed or the methods can be executed in parallel.

[0451] Alternatively, without prejudice to the nature of this disclosure, the accompanying drawings describing the methods of this disclosure may omit some components and include only some components.

[0452] Furthermore, without prejudice to the nature of this disclosure, the methods of this disclosure can be performed by combining some or all of the elements included in each embodiment.

[0453] It should be understood that, according to the claims and description in the specification, various embodiments of this disclosure may be implemented in hardware, software, or a combination of hardware and software.

[0454] Any such software may be stored in a non-transitory computer-readable storage medium. The non-transitory computer-readable storage medium stores one or more computer programs (software modules) that include computer-executable instructions that, when executed individually or jointly by one or more processors of an electronic device, cause the electronic device to perform the methods of this disclosure.

[0455] Any such software can be stored in the form of volatile or non-volatile storage devices, such as storage devices like read-only memory (ROM), whether erasable or rewritable; or in the form of memory, such as random access memory (RAM), memory chips, devices, or integrated circuits; or stored on optically or magnetically readable media, such as discs (CDs), digital versatile discs (DVDs), magnetic disks, or magnetic tapes. It should be understood that the storage devices and storage media are various embodiments of non-transitory machine-readable storage devices suitable for storing one or more computer programs comprising instructions that, when executed, implement various embodiments of this disclosure. Therefore, various embodiments provide a program comprising code for implementing the apparatus or method claimed as any one of the claims of this specification, and a non-transitory machine-readable storage device for storing such a program.

[0456] While this disclosure has been shown and described with reference to various embodiments thereof, those skilled in the art will understand that various changes in form and detail may be made in this disclosure without departing from the spirit and scope of this disclosure as defined by the appended claims and their equivalents.

Claims

1. A method performed by a terminal in a wireless communication system, the method comprising: Receive configuration information associated with subband non-overlapping full-duplex SBFD symbols from the base station; Identify whether one or more symbols assigned to the Physical Uplink Shared Channel (PUSCH) associated with Random Access (RA) are all SBFD symbols and do not include symbols of the Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) block; as well as If the one or more symbols allocated for the PUSCH are all SBFD symbols and do not include the symbols of the SS / PBCH block, the PUSCH is sent to the base station. The SBFD symbol is used for uplink transmission using at least one of downlink symbols or flexible symbols.

2. The method according to claim 1, further comprising: Identify whether the symbol type used for PUSCH repetition is associated with SBFD.

3. The method according to claim 1, in, The configuration information includes cell-specific configurations. The configuration information is received via the System Information Block (SIB), and The PUSCH includes message 3 PUSCH repetition associated with the RA.

4. The method according to claim 1, further comprising: The frequency offset of the second hop (second hop) is identified based on the uplink subband size associated with the physical resource block (PRB).

5. A method performed by a base station in a wireless communication system, the method comprising: Send configuration information associated with the subband non-overlapping full-duplex SBFD symbol to the terminal; as well as If one or more symbols allocated for the Physical Uplink Shared Channel (PUSCH) associated with Random Access (RA) are SBFD symbols and do not include symbols of the Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) block, the PUSCH is received from the terminal. The SBFD symbol is used for uplink transmission using at least one of downlink symbols or flexible symbols.

6. The method according to claim 5, in, The symbol type used for PUSCH repetition is identified by the terminal, and The frequency offset of the second hop (the second hop) is identified by the terminal based on the uplink subband size associated with the Physical Resource Block (PRB).

7. The method according to claim 5, in, The configuration information includes cell-specific configurations. The configuration information is sent via the System Information Block (SIB), and The PUSCH includes message 3 PUSCH repetition associated with the RA.

8. A terminal in a wireless communication system, the terminal comprising: transceiver; as well as At least one processor, connected to the transceiver and configured to: Receive configuration information associated with sub-band non-overlapping full-duplex (SBFD) symbols from the base station. Identify whether one or more symbols assigned to the Physical Uplink Shared Channel (PUSCH) associated with Random Access (RA) are all SBFD symbols and do not include symbols of the Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) block, and If the one or more symbols allocated for the PUSCH are all SBFD symbols and do not include the symbols of the SS / PBCH block, the PUSCH is sent to the base station. The SBFD symbol is used for uplink transmission using at least one of downlink symbols or flexible symbols.

9. The terminal according to claim 8, wherein, The at least one processor is further configured to: Identify whether the symbol type used for PUSCH repetition is associated with SBFD.

10. The terminal according to claim 8, in, The configuration information includes cell-specific configurations. The configuration information is received via the System Information Block (SIB), and The PUSCH includes message 3 PUSCH repetition associated with the RA.

11. The terminal according to claim 8, wherein, The at least one processor is further configured to: The frequency offset of the second hop (second hop) is identified based on the uplink subband size associated with the physical resource block (PRB).

12. A base station in a wireless communication system, the base station comprising: transceiver; as well as At least one processor, connected to the transceiver and configured to: Send configuration information associated with the sub-band non-overlapping full-duplex SBFD symbol to the terminal, and If one or more symbols allocated for the Physical Uplink Shared Channel (PUSCH) associated with Random Access (RA) are SBFD symbols and do not include symbols of the Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) block, the PUSCH is received from the terminal. The SBFD symbol is used for uplink transmission using at least one of downlink symbols or flexible symbols.

13. The base station according to claim 12, in, The symbol type used for PUSCH repetition is recognized by the terminal.

14. The base station according to claim 12, in, The configuration information includes cell-specific configurations. The configuration information is sent via the System Information Block (SIB), and The PUSCH includes message 3 PUSCH repetition associated with the RA.

15. The base station according to claim 12, in, The frequency offset of the second hop (2nd hop) is identified by the terminal based on the uplink subband size associated with the Physical Resource Block (PRB).

Images